Frame Relay Manager User s Guide

Transcription

1 Titlepage Frame Relay Manager User s Guide Document 2102 Device Management

2 Copyright Notice Document Copyright present by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR Liability Disclaimer Aprisma Management Technologies, Inc. ( Aprisma ) reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. Trademark, Service Mark, and Logo Information SPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go to All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns about trademark or copyright references, please send an to spectrum-docs@aprisma.com; we will do our best to help. Frame Relay Manager User s Guide Page 2

3 Restricted Rights Notice (Applicable to licenses to the United States government only.) This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR (June 1987) Alternate III(g)(3) (June 1987), FAR (June 1987), or DFARS (c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc. In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license. Virus Disclaimer Aprisma makes no representations or warranties to the effect that the licensed software is virusfree. Aprisma has tested its software with current virus-checking technologies. However, because no antivirus system is 100 percent effective, we strongly recommend that you write-protect the licensed software and verify (with an antivirus system in which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc. 273 Corporate Drive Portsmouth, NH Phone: U.S. toll-free: Web site: Frame Relay Manager User s Guide Page 3

4 Contents Preface 6 Intended Audience...6 Document Feedback...6 Online Documents...6 Introduction 7 Frame Relay Networks...7 Modeling a Frame Relay Network with SPECTRUM...8 FrameRelayPort Model...8 DLCI_Port Model...8 Application Models...8 Benefits of SPECTRUM s Frame Relay Manager...9 Modeling Frame Relay Networks 10 Modeling Topologies...10 Discovering Frame Relay Connections with AutoDiscovery...12 Unresolved Connections...13 Resolving DLCI_Port Connections...13 Updating the Network Model when a Virtual Circuit Changes State...18 Importing Connectivity Information 19 Creating a Comma-Delimited Input File...19 Using the wanimport Tool...20 Moving the wanimport Tool to the Third-Party Host...20 Running the wanimport Tool...22 Managing Frame Relay Networks 23 Accessing DLCI_Port Models...24 Setting Polling Specifications for DLCI_Port Models...27 Setting Polling and Logging Information the DLCI_Port Information View...27 Setting Polling Intervals and Log Ratios via the Search Manager...28 Setting Polling Intervals with CLI...29 Frame Relay Manager User s Guide Page 4

5 Contents Contents Monitoring Port Performance with the DLCI_Port Performance View...30 Graph Properties...30 Navigation Buttons...31 Setting Attribute Values in the DLCI_Port Configuration View...32 Banner Information...32 Navigation Buttons...33 Port Information...33 External Port Management...34 Internal Port Management...35 Address Information...36 Viewing Frame Traffic Information in the Frame Relay Detail View...37 Setting Thresholds to Generate Alarms...38 Setting Thresholds...39 High and Low Thresholds...40 DLCI_Port Service Information View...41 Analyzing Network Performance 42 FECN and BECN Rates...42 Excessive Discards...44 Determining the Need for Greater Bandwidth...46 Frame Relay Application Models 47 Trap Configuration View...49 DLCI Connection View...50 The fr1315app Application Model...53 Error Table View...53 Data Link Connection Management Table View...55 Frame Relay Circuit Table View...57 Appendix A: Modeling Comparison 60 Modeling a Frame Relay Network without Frame Relay Manager...60 Modeling a Frame Relay Network with Frame Relay Manager...61 Appendix B: Alarms 63 Appendix C: Terminology 64 Index 65 Frame Relay Manager User s Guide Page 5

6 Preface This preface provides an introduction to the Frame Relay Manager User s Guide, discusses who should read this guide, and describes how the guide is organized. Welcome to the Frame Relay Manger User s Guide. This document describes how SPECTRUM s Frame Relay Manager provides more effective management of Frame Relay networks by allowing you to model and monitor multiple virtual circuits for each Frame Relay interface. Intended Audience You must be familiar with Frame Relay network technology before using the Frame Relay Manager application and this document. This document is not meant to be an explanation of Frame Relay and networking. This guide also assumes that you are familiar with the SPECTRUM concepts covered in How to Manage Your Network with SPECTRUM. Document Feedback Please send feedback regarding SPECTRUM documents to the following address: spectrum-docs@aprisma.com Thank you for helping us improve our documentation. Online Documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. Frame Relay Manager User s Guide Page 6

7 Introduction This section provides an overview of frame relay networks and SPECTRUM s approach to managing them. Frame Relay Networks Frame relay is a packet-based interface standard that has been optimized for the transport of protocol-oriented data. The frame relay interface specification provides a signaling and data transfer mechanism. Frame relay s ability to statistically multiplex means that paths or virtual circuits are defined throughout the network, but no bandwidth is allocated to the paths until data needs to be transmitted. Frame relay provides multiple logical connections within a single physical connection. The Frame Relay protocol is a connection-based, variable-length packet protocol largely based on the X.25 protocol. Frame relay customers lease bandwidth from a service provider based on their anticipated bandwidth needs. Bandwidth allocation consists of a Committed Information Rate (CIR), which is guaranteed bandwidth, and Burst Excess (BE), which is additional bandwidth that may be used by the customer but may not always be available. All packets in excess of the CIR allocation are automatically flagged as Discard Eligible (DE), and, if total traffic on the network exceeds the maximum allocation, these excess packets are discarded. There are two types of connections available in a frame relay network; permanent and switched virtual circuits (PVCs and SVCs). Virtual circuits give a user the impression that they have a dedicated circuit between devices when, in fact, multiple users may be using the same circuit. Each virtual circuit is identified by a Data Link Control Identifier (DLCI) which is usually pre-mapped to a destination device. Pre-mapped DLCIs are PVCs. SVCs are a temporary virtual circuits that are set up and used only when data is being transmitted. Frame Relay Manager User s Guide Page 7

8 Introduction Modeling a Frame Relay Network with SPECTRUM Modeling a Frame Relay Network with SPECTRUM In order to effectively manage a frame relay network, SPECTRUM must model and monitor frame relay virtual circuits. This means that SPECTRUM must be able to represent and monitor multiple logical connections on a single physical connection. Frame Relay Manager uses FrameRelayPort and DLCI_Port models to do this. FrameRelayPort Model FrameRelayPort models are used to represent the physical frame relay connection on the device. DLCI_Port Model The concept of a sub-interface model, called a DLCI_Port model, is used to represent virtual circuit connections. One of these models is created for each virtual circuit on a frame relay interface. These models are accessed through the double-click zone on the FrameRelayPort icon. Application Models SPECTRUM s Frame Relay Manager supports the application models explained in the Frame Relay Application Models (Page 47) section. Frame Relay Manager User s Guide Page 8

9 Introduction Benefits of SPECTRUM s Frame Relay Manager Benefits of SPECTRUM s Frame Relay Manager Once the entire frame relay network has been successfully modeled, you can: Identify lost connections. Isolate network problems such as congestion on the network or excessive discards. Determine the need for greater bandwidth. Identify CIR in excess of current needs. Assess real time performance of a PVC. Without Frame Relay Manager, SPECTRUM cannot represent or monitor virtual circuit connections. Information to manage a frame relay network is only available from the application models generated by modeling a device that supports a frame relay MIB. Appendix A: Modeling Comparison on Page 60 shows the differences between a network modeled with and a network modeled without Frame Relay Manager. Frame Relay Manager User s Guide Page 9

10 Modeling Frame Relay Networks This section describes how SPECTRUM models a frame relay network. The following sections explain how to use SPECTRUM s AutoDiscovery and manual modeling capabilities to create an accurate modeling topology of your frame relay network. Modeling Topologies (Page 10) Discovering Frame Relay Connections with AutoDiscovery (Page 12) Unresolved Connections (Page 13) Updating the Network Model when a Virtual Circuit Changes State (Page 18) Modeling Topologies SPECTRUM can model and monitor frame relay networks of varying complexity. This section shows two examples of modeling topologies, one very simple and the other, large and complex. Each modeling topology can easily be customized to better suit the needs of the network administrator. Figure 1 on Page 10 shows the most basic frame relay modeling scheme. Two wide area routers, one in Boston and one in New York, are linked with a connection pipe. Figure 1: BOSTON Model of a Basic Frame Relay Network NEW YORK Frame Relay Manager User s Guide Page 10

11 Modeling Frame Relay Networks Modeling Topologies Figure 2 on Page 11 shows a model of a large and complex frame relay network. Frame Relay Manager User s Guide Page 11

12 Modeling Frame Relay Networks Modeling Topologies Figure 2: Complex Frame Relay Modeling Landscape Network LAN LAN WAN LAN LAN LAN Frame Relay Manager User s Guide Page 12

13 Modeling Frame Relay Networks Discovering Frame Relay Connections with AutoDiscovery Discovering Frame Relay Connections with AutoDiscovery There is no correlation between IP Routes to DLCIs in any standard SNMP MIB. This means that although AutoDiscovery may be able to determine the connections between two frame relay interfaces based on the layer three and layer two connectivity information available in standard and enterprise MIBs, it cannot, through conventional means, map the DLCIto-DLCI connections. However, this level of connectivity is necessary to get statistics for each circuit and to take full advantage of fault isolation. When a connection between two frame relay interface models is inferred, the AutoDiscovery intelligence attempts to determine which DLCI models are connected, using one of the following methods: If the device supports the Cisco Frame Relay MIB, SPECTRUM will attempt to use local and remote IP address information to determine if a connection has been statically mapped between a DLCI on a local interface and a DLCI on a remote interface. For this method to be successful, there can be no more than one remote DLCI with an IP address equal to the map IP Address. If this method fails or if the Cisco Frame Relay MIB is not supported, SPECTRUM attempts to use the IP address and subnet mask information associated with each DLCI to infer DLCI connectivity by common subnetting. For this method to be successful, exactly one pair of DLCI models between the local and remote frame relay interfaces must share a common subnet. If DLCI connectivity is not established using this method, SPECTRUM attempts to determine the connectivity using a statistical algorithm. This algorithm samples the traffic going over each DLCI associated with both interfaces within a pre-determined time period. At the end of this period, the statistics are analyzed, based on the assumption that the octets sent from a DLCI on one interface should be nearly equal to the octets received by a DLCI on the other interface. For this method to be successful, there must be traffic going over the frame relay circuits. Frame Relay Manager User s Guide Page 13

14 Modeling Frame Relay Networks Unresolved Connections If any of these methods succeeds, connections are made between the corresponding DLCI_Port models and their device models. If these methods fail, the DLCI-to-DLCI connectivity must be resolved manually. Unresolved Connections AutoDiscovery may not resolve all DLCI_Port connections. If the Topology view resulting from an AutoDiscovery session shows connection pipes that stay blue (or silver if live pipes are not enabled), or if there are no pipes connecting devices that should be connected, then there are unresolved connections. Unresolved connections can occur for any of the following reasons: A network link was down when AutoDiscovery was run so there was no entry for that link in the IP Route table. The amount of traffic going over a particular PVC was not sufficient for SPECTRUM's traffic pattern matching heuristic to determine DLCI-to- DLCI connectivity. To resolve these connections manually, examine the frame relay map to determine what connections are missing, and then create the appropriate connections in SpectroGRAPH. Note: You also have the option of importing connectivity information via a comma-delimited ASCII text file. For more information on how to do this, see Importing Connectivity Information on Page 19. Resolving DLCI_Port Connections Resolving DLCI_Port connections is similar to resolving standard port connections, however the DCLI_Port connection is resolved at the subinterface level. The following example illustrates how to resolve a DLCI_Port connection. Figure 3 on Page 15 shows Router A s Device Topology view with an Off- Page Reference icon representing the unresolved connection for Router B. Frame Relay Manager User s Guide Page 14

15 Modeling Frame Relay Networks Unresolved Connections Router B s Off-Page Reference icon must be resolved to the corresponding DLCI_Port model. 1 In the Universe Topology view, select Edit from the File menu. 2 Highlight the Router B model that needs to be resolved. 3 Select Copy from the Edit menu. 4 Select Close Edit from the File menu. 5 Navigate into Router A s Device Topology view (Figure 3 on Page 15). 6 From Router A s Device Topology view, navigate into the FrameRelayPort model s own Device Topology (Figure 4 on Page 17) view by double-clicking the down arrow on the interface icon. 7 Select Edit from the File menu. 8 Select Paste from the Edit menu. 9 Paste the Router B model onto the correct DLCI_Port model. Frame Relay Manager User s Guide Page 15

16 Modeling Frame Relay Networks Unresolved Connections Figure 3: Device Topology View with Off-Page Reference Icon Router B Router B Off-Page Reference icon Blue Connection Pipe Router B Router A Frame Relay Manager User s Guide Page 16

17 Modeling Frame Relay Networks Unresolved Connections Figure 4 on Page 17 shows the Device Topology view of a FrameRelayPort model associated with Router A. Router B s model has been resolved to the correct DLCI_Port model. This same procedure must now be repeated to resolve Router A s connection to Router B, as follows: 1 In the Universe Topology view, select Edit from the File menu. 2 Highlight the Router A model that needs to be resolved. 3 Select Copy from the Edit menu. 4 Select Close Edit from the File menu. 5 Navigate into Router B s Device Topology view. 6 From Router B s Device Topology view, navigate into the FrameRelayPort model s sub-interface view by double-clicking the down arrow on the interface. 7 Select Edit from the File menu. 8 Select Paste from the Edit menu. Paste the Router A model onto the correct DLCI_Port model. Frame Relay Manager User s Guide Page 17

18 Modeling Frame Relay Networks Unresolved Connections Figure 4: FrameRelayPort Device Topology View with Resolved Connection Router B Connection Resolved DLCI_Port Model Frame Relay Manager User s Guide Page 18

19 Modeling Frame Relay Networks Updating the Network Model when a Virtual Circuit Changes State Updating the Network Model when a Virtual Circuit Changes State The frdlcistatuschange trap is defined in rfc1315 and rfc2115. Devices that support these MIBs can be configured to send this trap when one of their virtual circuits changes state, i.e., is removed, becomes inactive, or is added. If an frdlcistatuschange trap is received and it identifies an ifindex.dlci which is not modeled in SPECTRUM, an automatic reconfiguration of the Frame Relay application model will be triggered if the Automatic Application Reconfiguration attribute is set to ENABLED. This attribute is found in the Trap Configuration View (Page 49) of the Frame Relay application model. A reconfiguration of the Frame Relay application will cause all of the device Frame Relay components to be rediscovered and remodeled. Creating a DLCI_Port Model Manually To create the new DLCI_Port model, do the following: 1 Navigate to the Application view of the frame relay device where the new circuit has been added. 2 Highlight the appropriate frame relay application icon. 3 Select Model Information from the Icon Subviews menu to access the frame relay Application Model Information view. 4 Click the Reconfigure button. The frame relay application re-reads the MIB, finds the new virtual circuit entry, and creates the DLCI_Port model. Frame Relay Manager User s Guide Page 19

20 Importing Connectivity Information This section describes using the wanimport tool to import frame relay connectivity information contained in a comma-delimited ASCII text file. Frame relay connectivity information can be imported into SPECTRUM using the wanimport tool. To use this tool, you must create a commadelimited ASCII text file that defines the connections you would like to create. The wanimport tool is then executed referencing this file, and the appropriate connections are created within the SpectroSERVER database. Creating a Comma-Delimited Input File A comma-delimited ASCII text file is used to define the connections that will be imported into SPECTRUM. This file can specify connections between two ATM circuits, two frame relay circuits, or an ATM and a frame relay circuit. You have the option to specify that a live pipe be created in the SpectroGRAPH to represent the connection. Multiple connections can be specified in the same input file. The device models involved in these connections must already exist in SPECTRUM. Following is the format for the input file: <Device_IP>, <OID>, <Device_IP>, <OID>, <CircuitName>, <CircuitID>, <Pipe> Device_IP is the IP address of each device involved in the connection. This parameter is required for each device. OID is the OID instance of frcircuittable, atmvcltable or atmvpltable to specify the circuit link on the device. This parameter is required for each device. CircuitName is an optional parameter specifying the name of the circuit involved. Frame Relay Manager User s Guide Page 20

21 Importing Connectivity Information Using the wanimport Tool CircuitID is an optional parameter specifying the ID of the circuit involved. Pipe is an optional parameter with two possible values, CREATE_PIPE or NO_CREATE_PIPE. If the value is set to CREATE_PIPE, live pipes will be created between the connections specified. If the value is set to NO_CREATE_PIPE, live pipes will not be created between the connections specified. If no value is specified for this parameter, a default value of CREATE_PIPE is assumed. The following example shows a line from an input file that specifies the connection between a frame relay circuit and an ATM circuit. In this example a pipe is created between the two ports , 4.161, , , FR<->ATM, 12345, CREATE_PIPE This example shows a line from an input file that specifies the connection between two frame relay circuits. In this example a pipe is not created , 2.161, , fr link, 909, NO_CREATE_PIPE Using the wanimport Tool Once you have created the input file, use the wanimport tool to send the connectivity data into the SpectroSERVER database. The wanimport tool is a command line utility that is located in <SPECTRUM>/SS-Tools. This tool can be run from the SpectroSERVER or from a third-party host. In order to run the tool from a third-party host, follow the instructions on moving the tool outlined below. Moving the wanimport Tool to the Third-Party Host To run the wanimport tool from the third-party host, you must move the wanimport tool and all of its support files to the third-party host. SPECTRUM provides a script that packs up the wanimport tool so that it can be sent via FTP to the third-party host. The script ensures that the Frame Relay Manager User s Guide Page 21

22 Importing Connectivity Information Using the wanimport Tool relative directory structure of the tool and its support files is retained when the files are moved. The following steps show how to move these files: 1 On the SpectroSERVER, check to make sure the environmental variable SPECROOT is set to the SPECTRUM installation directory path. 2 Run the script that packs up the tool and its support files. The script can be found in the SPECTRUM s SS-Tools directory and is called packtool.pl. To run the script from the Bash shell or other Unix shell, type: <Spectrum_Installation_Path>/SS-Tools/packtool.pl wanimport Where <Spectrum_Installation_Path> is the directory structure where Spectrum is installed on your SpectroSERVER. 3 The script generates an executable file called wanimport_bundle (Unix) or wanimport_bundle.exe (Windows) that contains the wanimport tool and all of its support files. 4 On the third-party host, create a new directory to unpack the wanimport tool and its support files, i.e. /disk/spectrum. 5 FTP the wanimport_bundle or wanimport_bundle.exe file from the SpectroSERVER to the third-party host, and place it in the directory created in step 4. Be sure to use binary mode during the FTP process. 6 Once the file is on the third-party host, execute the file from the DOS, Bash, or other Unix shell. The wanimport tool and its support files will unpack into the appropriate directory structure. The wanimport tool can now be run from this host machine. Note: Both servers involved in this process must be running the same operating system. You cannot pack the tool on a Windows server and unpack it on a Unix machine or vise versa. Frame Relay Manager User s Guide Page 22

23 Importing Connectivity Information Running the wanimport Tool Using the wanimport Tool In order to run the wanimport tool from a machine other than the SpectroSERVER, set the SPECROOT (Unix) or SPECPATH (Windows) environmental variable on this machine equal to the path to the directory where the wanimport_bundle or wanimport_bundle.exe file is located. For example, if you are working in the Unix environment and placed the wanimport_bundle file in /disk/spectrum as in step 4 in Moving the wanimport Tool to the Third-Party Host (Page 20), then set SPECROOT=/disk/Spectrum. If you are working in the Windows environment and placed the wanimport_bundle.exe file in C:\disk\Spectrum, then set SPECPATH=C:\disk\Spectrum. The import tool command takes 4 arguments, two are required and two are optional. Windows Syntax: wanimport.bat -vnm <vnm_name> -i <input_file> [-o <outputfile>] [-debug] Unix Syntax: wanimport -vnm <vnm_name> -i <input_file> [-o <outputfile>] [-debug] The vnm_name argument is the name of the SpectroSERVER host. This argument is required. The input_file is the name of the comma-delimited input file containing the connectivity information. This argument is required. The -o argument logs the error information to the file named in the outputfile parameter. If this option is not used, the error information is logged to a file named inputfile.log, where inputfile is the name of the comma-delimited input file. The debug argument indicates that you would like to create a debugging output file during the import process. This argument is optional. Frame Relay Manager User s Guide Page 23

24 Managing Frame Relay Networks This section provides instructions on accessing, configuring, and monitoring DLCI_Port models. SPECTRUM s Frame Relay Manager monitors the virtual circuits on your frame relay network. These virtual circuits are represented by connections between DLCI_Port models. From the appropriate DLCI_Port model (see Accessing DLCI_Port Models on Page 24), you have access to a series of DLCI_Port model views that allow you manage your frame relay network. The following sections describe the functionality of each of these views. Setting Polling Specifications for DLCI_Port Models on Page 27 describes using the DLCI_Port Information view, the Search Manager, or a CLI script to set polling specifications. Monitoring Port Performance with the DLCI_Port Performance View on Page 30 discusses monitoring the quality of service for each DLCI_Port. Setting Attribute Values in the DLCI_Port Configuration View on Page 32 describes setting the value of internal and external DLCI_Port model attributes. Viewing Frame Traffic Information in the Frame Relay Detail View on Page 37 describes accessing pie charts that illustrate frame and octet traffic. Setting Thresholds to Generate Alarms on Page 38 discusses how to use the Port Threshold view for generating alarms. DLCI_Port Service Information View on Page 41 discusses recording information concerning service providers associated with the frame relay network using the DLCI_Port Service Information view. Frame Relay Manager User s Guide Page 24

25 Managing Frame Relay Networks Accessing DLCI_Port Models Accessing DLCI_Port Models DLCI_Port models are contained in the sub-interface view of the FrameRelayPort model. The FrameRelayPort model is accessed through the frame relay device s Device Topology view (Figure 5 on Page 24) or the frame relay device s Interface Device view (Figure 6 on Page 25). Figure 5: Device Topology View with FrameRelayPort Model BOSTON Frame Relay Manager User s Guide Page 25

26 Managing Frame Relay Networks Figure 6: Interface Device View with FrameRelayPort Model BOSTON Frame Relay Manager User s Guide Page 26

27 Managing Frame Relay Networks To access the FrameRelayPort Device Topology view containing the DLCI_Port models, double-click on the down arrow of the FrameRelayPort model or highlight the FrameRelayPort model and select Sub-Interfaces from the Icon Subviews menu (Figure 7 on Page 26). Figure 7: DLCI_Port Models in a FrameRelayPort Device Topology View DLCI_Port Model Frame Relay Manager User s Guide Page 27

28 Managing Frame Relay Networks Setting Polling Specifications for DLCI_Port Models Setting Polling Specifications for DLCI_Port Models It is possible to configure SPECTRUM to poll DLCI ports at regular intervals. When SPECTRUM polls these ports it captures the values of various external MIB objects. You can choose to log these values and use them for monitoring and analyzing the performance of a port. To generate reports and statistics from the DLCI_Port model, you must specify a polling interval. There are three different methods to set the polling interval for DLCI_Ports. The following sections give instructions on these methods: Setting Polling and Logging Information the DLCI_Port Information View (Page 27) Setting Polling Intervals and Log Ratios via the Search Manager (Page 28) Setting Polling Intervals with CLI (Page 29) For more general information on SPECTRUM s polling and logging functions, refer to the Performance View User s Guide (3509) and the SPECTRUM Concepts Guide (0647). Setting Polling and Logging Information the DLCI_Port Information View To access the DLCI_Port Information view, highlight the DLCI_Port model and select Information from the Icon Subviews menu or single-click Port Polling/Logging button in the DLCI_Port Configuration view. This view contains the following fields: Field Last Successful Poll Description This field shows the date and time of the last successful poll to this DCLI_Port model. Frame Relay Manager User s Guide Page 28

29 Managing Frame Relay Networks Setting Polling Specifications for DLCI_Port Models Field Poll Interval Log Ratio Polling Status Significance Level Description This field determines how often, in seconds, an SNMP Get quest is sent to the port to obtain information. This field determines the frequency at which the polled data is written to the SPECTRUM database. For example, if a Poll Interval of 60 is defined, and the Log Ratio is set to 10, the attribute information is logged to the statistics file every tenth poll, or every 600 seconds. This field can be set to TRUE or FALSE. TRUE turns polling on, FALSE turns polling off. This section allows you to set the significance level for red, orange and yellow alarms. For more information on significance level, refer to How to Manage Your Network with SPECTRUM. The Poll Interval, Log Ratio, and Significance Level fields can be modified by entering the data in the appropriate field and then saving this change. Setting Polling Intervals and Log Ratios via the Search Manager When you use this option to set polling intervals and log ratios, you can modify the polling interval for a specific DLCI_Port model or for all DLCI_Port models. 1 To bring up the Search Manager, select Tools>Search Manager. 2 Click on the Editor button in the Search Manager s main window, and the Search Editor window appears. 3 Choose Modeltype_name as the attribute value. 4 Choose Equal-to as the matching type. Frame Relay Manager User s Guide Page 29

30 Managing Frame Relay Networks Setting Polling Specifications for DLCI_Port Models 5 Use the Browse button to select DLCI_Port as the attribute value. 6 Click the Add Line to Criteria Set button. 7 Click the Apply Search Button. 8 The main window of the Search Manager appears with a listing of DLCI_Port models. 9 Click on the DLCI_Port model to be modified or click the Select All button to select all of the DLCI_Port models. 10 Select Management>Set Attribute Values. 11 Enter the new polling interval and/or log ratio value. 12 Click the Apply button. For complete instructions on using the Search Manager, refer to the Search Manager User s Guide (2383). Setting Polling Intervals with CLI There is a Command Line Interface (CLI) script called update_mtype that lets you change polling intervals for a single DLCI_Port model or for all DLCI_Port models. For instructions on using this script, refer to the Command Line Interface (0664) guide. Frame Relay Manager User s Guide Page 30

31 Managing Frame Relay Networks Monitoring Port Performance with the DLCI_Port Performance View Monitoring Port Performance with the DLCI_Port Performance View To access the DLCI_Port Performance view, highlight the model and select Port Performance from the Icon Subviews menu or single-click the Port Performance button in the DLCI_Port Configuration view (see Page 32). This view shows graphs of two sets of statistics. The top graph shows Ingress Traffic vs. Bandwidth, and the bottom graph shows Egress Traffic vs. Bandwidth. The frcircuitcommittedburst, frcircuitexcessburst, and frcircuitthroughput MIB objects must be set in the DLCI_Port Configuration view (see Page 32) for the Port Performance view to return accurate information. Graph Properties The Graph Properties option button has three selections: Selection Scroll to Date-Time Change Time Scale Data Logging Explanation Use this to navigate to a specific period of time in the graph. Use this to select the number of hours that you would like the graph to cover. Use this to specify if the polled data used to create the graph is logged to the database. Frame Relay Manager User s Guide Page 31

32 Managing Frame Relay Networks Monitoring Port Performance with the DLCI_Port Performance View Navigation Buttons The navigation buttons at the bottom of the screen link to one of the three other performance views available or to other Frame Relay views. Button CIR Load Frame Traffic Detail Configuration Thresholds Help Explanation Click on the CIR button to access a performance view that shows graphs of % CIR in and % CIR out. Click on the Load button to access a performance view that shows graphs of Load % In and Load % Out. Click on the Frame Traffic button to access a performance view that shows graphs of Ingress and Egress Traffic vs. Bandwidth, and of Frame Traffic. Click on the Detail button to access the Frame Relay Detail view (see Page 37). Click on the Configuration button to access the DLCI_Port Configuration view (see Page 32). Click on the Thresholds button to access the DLCI_Thresholds view (see Page 38). Click on the Help button for a further Performance view information. Frame Relay Manager User s Guide Page 32

33 Managing Frame Relay Networks Setting Attribute Values in the DLCI_Port Configuration View Setting Attribute Values in the DLCI_Port Configuration View The DLCI_Port Configuration view displays external MIB objects corresponding to the DLCI that the port represents. To access the DLCI_Port Configuration view, highlight the DLCI_Port model and select Port Configuration from the Icon Subviews menu. Banner Information The banner portion of this view provides general information about the model. There are two fields in this section that are unique to this view and require further explanation. Field IfIndex.DLCI Description Explanation This field displays the ifindex value of the frame relay logical or physical interface associated with the DLCI port. If the device supports the CiscoFrApp, the DLCI_Port Configuration view for each Cisco DLCI port displays the value of the Cisco cfrextcircuitifname MIB object in this field. This MIB object provides the ifdesc of the frame relay sub-interface associated with a particular DLCI. This rest of this view is divided up into the following sections: Navigation Buttons (Page 33) Port Information (Page 33) External Port Management (Page 34) Internal Port Management (Page 35) Address Information (Page 36) Frame Relay Manager User s Guide Page 33

34 Managing Frame Relay Networks Setting Attribute Values in the DLCI_Port Configuration View Navigation Buttons At the bottom of this screen are several navigation buttons. Button Explanation Help Click this button to get further information about this view. Port Polling and Logging Click this button to go to the DLCI_Port Information view (see Page 27). Port Performance, CIR, and Load Port Detail Service Information Thresholds Click one of these buttons to go to a particular DLCI_Port Performance view (see Page 30). Click this button to go to the Frame Relay Detail view (see Page 37). Click this button to go to the Service Information view (see Page 41). Click this button to go to the DLCI_Port Thresholds view (see Page 38). Port Information This area of the Port Configuration view provides the following information: Field Creation Time Last Change Explanation The system uptime value when this virtual circuit was created by the Data Link Connection Management Interface as defined in the rfc1315 MIB or by an SNMP Set request. The system uptime value when there was last a change in the state of this virtual circuit. Frame Relay Manager User s Guide Page 34

35 Managing Frame Relay Networks Setting Attribute Values in the DLCI_Port Configuration View Field Rcvd FECNs Rcvd BECNs IF Speed Explanation The number of frames received from the network that indicate forward congestion since this virtual circuit was created. The number of frames received from the network that indicate backward congestion since this virtual circuit was created. An estimate of the DLCI_Port s current bandwidth in bits per second. External Port Management A full explanation of the fields available in this section can be accessed via the Help button at the bottom of the screen. To set the value of any of these fields: 1 Enter the value. 2 Select Save All Changes from the File menu. 3 Click OK. Note: For frame relay devices that support the frcircuitcommittedburst, frcircuitexcessburst, and frcircuitthroughput MIB objects, these values can be set in the External Port Management section of this view. For devices that do not support these MIB objects, use the Internal Port Management section of this view to set these values. These values must be set for the Port Performance view to return accurate information. Frame Relay Manager User s Guide Page 35

36 Managing Frame Relay Networks Setting Attribute Values in the DLCI_Port Configuration View Internal Port Management A full explanation of the fields available in this section can be accessed via the Help button at the bottom of the screen. To set the value of any of these fields: 1 Enter the value. 2 Select Save All Changes from the File menu. 3 Click OK. The following considerations apply to setting internal port management values: If neither the external or internal values are set, the ifspeed MIB object of the related interface is used as the value to indicate bandwidth. In order for these values to be logged for historical reporting purposes, a Polling Interval must be set and the Polling Status must be True (see Setting Polling Specifications for DLCI_Port Models on Page 27). Because you can override the Committed Burst rate and Burst Excess value, you can use the Performance view to predict what will happen when these values change. For example, if you have a 128k PVC that rarely exceeds Committed Burst, and you want to predict what effect reducing the service to 64k would have, change the values in the DLCI_Port's Internal Management view, and then view these changes in the Performance view. The bandwidth of the circuit is determined by the Performance view when it is initially launched. If you make changes to the Committed Burst or Burst Excess values, close the Performance view and bring it up again for the changes to take effect, or launch a second view with the new bandwidth values, and compare the two graphs. Frame Relay Manager User s Guide Page 36

37 Managing Frame Relay Networks Setting Attribute Values in the DLCI_Port Configuration View Address Information This area of the DLCI_Port Configuration view provides network addressing information associated with this DLCI_Port. SPECTRUM does attempt to determine this information from the ipaddrtable, however, this information can be edited. Field IP Address IP Mask Remote IP Explanation The IP Address of this DLCI _Port. Frame relay interfaces on some devices have multiple IP Addresses. Each IP Address can correspond to a different PVC running over a DLCI_Port. In such cases, the IP Address field is filled in with the corresponding IP Address. The IP Mask is used to break the destination address down into a network address and a host address. The network address shows the address boundary of a subnet that the frame relay device knows about. For example, an address of with a IP Mask of gets broken down into the subnet address The frame relay device looks through its IP route tables for that subnet address and its corresponding interface. All frames with an address within the range and are transmitted from that interface to that subnet. The IP Address at the remote end of the PVC. This field is only populated for Cisco statically mapped DLCIs. The value in this field is based on the cfrmapaddress object of the cfrmaptable. Frame Relay Manager User s Guide Page 37

38 Managing Frame Relay Networks Viewing Frame Traffic Information in the Frame Relay Detail View Viewing Frame Traffic Information in the Frame Relay Detail View This view can be accessed by single-clicking the Port Detail button in the DLCI_Port Configuration view (see Page 32) or on the Detail button in the DCLI_Port Performance View (see Page 41). The Port Detail view provides two color-coded pie charts. One pie chart provides a breakdown of frame traffic: frames in, frames out, FECNs, and BECNs. The other pie chart provides a breakdown of octet traffic: octets in and octets out. Note: For the Port Performance view to return accurate information, the Committed Burst, Excess Burst, and Throughput values must be set in the DLCI_Port Configuration view. See Setting Attribute Values in the DLCI_Port Configuration View on Page 32. Frame Relay Manager User s Guide Page 38

39 Managing Frame Relay Networks Setting Thresholds to Generate Alarms Setting Thresholds to Generate Alarms DLCI_Port models have a Port Threshold view that establishes levels of activity that will generate alarms. To access the DLCI_Port Threshold view, highlight the DLCI_Port model and select Port Thresholds from the Icon Subviews menu or single-click the Port Thresholds button in the DLCI_Port Configuration view (see Page 32). By default, all threshold values are set to 0 (disabled). The threshold values are recalculated at every poll cycle and represent the average number per poll. You can set a threshold value on any of the following fields. If this threshold is violated, an alarm will be generated on the DLCI_Port model. Field Bits Per Second Received Bits Per Second Transmitted BECNs Per Frames Transmitted FECNs Per Frames Received Load In % Explanation The average number of bits received by the DLCI_Port since the last poll. The average number of bits transmitted by the DLCI_Port since the last poll. The ratio of the number of frames received with their BECN bits set to the total number of frames transmitted. This ratio will give an indication of what percentage of frames transmitted experienced congestion on the network since the last poll. The percentage of frames with their FECN bits set that have been received over this DLCI_Port since the last poll. This field is calculated by dividing the bits received by the incoming Burst Committed plus the incoming Burst Excess (Bits received/bci+bei). Bursts committed is the minimum number of bits that a service provider guarantees for a PVC. Burst Excess in is the maximum number of bits that may be received in excess of BC. Frame Relay Manager User s Guide Page 39

40 Managing Frame Relay Networks Field Setting Thresholds to Generate Alarms Explanation Load Out % Set Reset This field is calculated by dividing the bits received by the outgoing Burst Committed plus the outgoing Burst Excess (Bits received/bco+beo). Bursts Committed (BC) is the minimum number of bits that a service provider guarantees for a PVC. Burst Excess (BE) in is the maximum number of bits that may be received in excess of BC. The Set field for each attribute is the high threshold that, if exceeded, will generate an alarm for that attribute. The Reset field for each attribute is the low threshold that, if gone below, automatically clears the alarm for that attribute. Do not set the Reset field to 0. If the Reset field is set to 0 and the Set (high threshold) field is crossed, the subsequent alarm will never be cleared automatically. If this alarm is cleared manually, the SPECTRUM threshold intelligence is not reset and the alarm for that model will not be generated again. To reset the threshold intelligence, the SpectroSERVER must be restarted. Setting Thresholds To set thresholds for a DLCI_Port model, do the following: 1 Highlight the DLCI_Port model 2 Select Port Thresholds from the Icon Subviews menu 3 In the Set field for the desired attribute, enter the high threshold. 4 In the Reset field for the desired attribute, enter the low threshold. 5 Select Save All Changes from the File menu. Frame Relay Manager User s Guide Page 40

41 Managing Frame Relay Networks High and Low Thresholds Setting Thresholds to Generate Alarms Figure 8 on Page 40 describes the functionality provided by the high and low threshold feature for DLCI_Port models. Figure 8: DCLI_Port Model Thresholding 100% Initial alarm is generated when high threshold value is exceeded. Without a low threshold, a new alarm would be generated every time the high threshold value is exceeded. With a low threshold,.only the initial alarm is generated. High Threshold Low Threshold 30% 25% Initial alarm is cleared when low threshold is crossed. Timeline Frame Relay Manager User s Guide Page 41

42 Managing Frame Relay Networks DLCI_Port Service Information View DLCI_Port Service Information View The DLCI_Port Service Information view provides information about service providers associated with the frame relay network. All service information is entered manually and is provided for reference purposes only. To access the DLCI_Port Service Information view either highlight the DLCI_Port model and select Information from the Icon Subviews menu or single-click the Service Information button in the DLCI_Port Configuration view (see Setting Polling and Logging Information the DLCI_Port Information View on Page 27). The following information can be entered: Provider Field Customer Primary Contact Secondary Contact Service Notes Explanation The name of the service provider associated with the frame relay network. frame relay customers who use multiple carriers can use this field to indicate the carriers provide service for specific circuits. Users who are frame relay providers and manage the frame relay networks of other companies can use this field to indicate who the frame relay customer is. The name, phone number, and/or address of the person to contact if there is a problem with this circuit. The name, phone number, and/or address of a secondary person to contact if there is a problem with this circuit. This area can be used to enter miscellaneous information about this circuit such as Circuit ID or monthly cost. Frame Relay Manager User s Guide Page 42

43 Analyzing Network Performance This section gives an overview of frame relay network performance issues. A congested frame relay network will not provide good quality of service to a subscriber. Heavy data transmissions may have to be rescheduled, traffic may need to be routed through uncongested virtual circuits, or better service must be established by the service provider. FECN and BECN Rates One indication of a congested frame relay network is the percentage of frames with their FECN or BECN bits set that have been received or transmitted by a frame relay device. Frame Relay Manager User s Guide Page 43

44 Analyzing Network Performance FECN and BECN Rates Some frames with their FECN bits set may reach the receiving frame relay device at the other end of the network link. Other frames with their FECN bits set will be discarded. F F F F F F F BOSTON NEW YORK WAN B B B B B B All frames with BECN bits set will be returned from the congested WAN network to the transmitting frame relay device. You can determine if the FECN and BECN rates are indicating a congested network with the following methods: Set thresholds for the FECNS Per Frames Received and BECNs Per Frames Transmitted attributes in the Port Thresholds view. If the high threshold for either attribute is exceeded, an alarm is generated ( see Appendix B: Alarms on Page 63). Monitor the DLCI_Port Performance views to determine FECN and BECN rates over a pre-determined time frame. A BECN or FECN frame rate of 5% or more of the total bandwidth indicates a congested network. This percentage can differ depending on the time sensitivity of the network traffic being transmitted or received. For example, SNA traffic is very time sensitive. If a frame relay circuit was Frame Relay Manager User s Guide Page 44

45 Analyzing Network Performance Excessive Discards transmitting or receiving SNA, a 2% BECN or FECN rate would indicate network congestion. If a frame relay circuit was transmitting or receiving IP, a 5% FECN or BECN rate would indicate network congestion. Excessive Discards Excessive discards can be an indication of network congestion or an indication that unrecognized packets are being received on the other end of the network link. One way to determine if excessive discards are occurring is through the Link Information view (Figure 9 on Page 45). You access the Link Information view with one of the following methods: Double-click on the connection pipe with the right mouse button. BOSTON NEW YORK Double-Click Highlight the connection pipe and select Link Information from the Icon Subviews menu. Frame Relay Manager User s Guide Page 45

46 Analyzing Network Performance Excessive Discards Figure 9: The Link Information View In the Link Information view, compare the Octets Transmitted total to the Octets Received total across the frame relay network link. If the Octets Transmitted total is greater than the Octets Received total, this may indicate that frames that are flagged as discard eligible are being discarded because there is too much network traffic to complete their transmission. Frame Relay Manager User s Guide Page 46

47 Analyzing Network Performance Determining the Need for Greater Bandwidth An Octets Transmitted total that is greater than the Octets Received total can also indicate that unrecognized packets are being received on the other end of the network link. Most routers support multiple protocols (IP, IPX, DECnet, AppleTalk, etc.) but each interface on a router needs to be configured to route a particular protocol. For example, if Router A is transmitting IPX packets to an interface on Router B and Router B doesn't have IPX configured for that interface, then the packets will be discarded. The solution is to either re-route Router A's IPX traffic to another router that is configured for IPX or configure an interface on Router B to support IPX. Determining the Need for Greater Bandwidth If data is being received on a DLCI_Port at a greater than expected rate, then the service provider may need to establish greater network bandwidth. You can determine if additional network bandwidth is needed by: Setting thresholds for the Bits Per Second Received and Bits Per Second Transmitted attributes in the Port Thresholds view. If the high threshold for either attribute is exceeded, an alarm is generated (see Appendix B: Alarms on Page 63). If threshold alarms for the Bits Per Second Received and Bits Per Second Transmitted attributes are continually being generated, then these attributes should be logged to start the data collection necessary to analyze bandwidth requirements. Monitoring the network traffic load through a DLCI_Port with the DLCI_Port Performance view. Load is the percentage of Committed Burst (BC) plus Burst Excess (BE) that is currently being used on the DLCI_Port. Frame Relay Manager User s Guide Page 47

48 Frame Relay Application Models This section gives an overview of the application model types that SPECTRUM supports for Frame Relay devices. When SPECTRUM creates a device model to represent a frame relay device, it also creates application models based on the MIBs that the device supports. Below are the MIBs that SPECTRUM supports and the corresponding application models that are created. The rfc1315app and rfc2115app application models are available with the core SPECTRUM product. The CiscoFRApp application model is available with the Cisco Router Common Applications (SM-CISAPP) management module, the StcomFRApp is available with the Cisco Stratacom BPX8600 and IGX8400 Series (SM- CIS1003) management module, the MotFRDTEApp and the MotFRDCEApp are available with the Motorola Vanguard (SM-MT1000) management module, and the wffrmrlyapp application model is available with the Wellfleet Router II (SM-WEL1003) management module. MIB Application rfc1315 rfc2115 Cisco-Frame-Relay MIB STRATACOM-MIB Motfrdte_Mib Motfrdce_Mib Wellfleet FR2 MIB rfc1315app rfc2115app CiscoFRApp StcomFRApp MotFRDTEApp MotFRDCEApp wffrmrlyapp When Frame Relay Manager is installed, the following application model functionality is added: Frame Relay Manager User s Guide Page 47

49 Frame Relay Application Models The Trap Configuration View (Page 49) is available for all of these application models except for the StComFRApp, the MofFRDTEApp, and the MotFRDCEApp. The DLCI Connection View (Page 50) is available for all of these application models except for the MofFRDTEApp and the MotFRDCEApp. The fr1315app Application Model (Page 53) is used in place of the rfc1315app application model. The following application icons represent the frame relay applications listed above. The appropriate model appears in the Application view of any frame relay device modeled in SPECTRUM. For complete information on the rfc2115app, see the Transmissions Applications (5064) guide. Frame Relay Manager User s Guide Page 48

50 Frame Relay Application Models For complete information on the CiscoFRApp, see the Cisco MC3810 (3287) guide. For complete information on the StComFRApp, see the Cisco Stratacom BPX8600 and IGX8400 Series (2787) guide. For complete information on the MotFRDTEApp and the MotFRDCEApp, see the Motorola Vanguard (3607) guide. For complete information on the wffrmrlyapp see the Wellfleet Router II (2259) guide. For complete information on the fr1315app, which replaces the rfc1315app when Frame Relay Manager is installed, see The fr1315app Application Model (Page 53). Trap Configuration View The Trap Configuration view allows a user to specify what happens if SPECTRUM receives a frdlcistatuschange trap. To access this view select Trap Configuration from the Icon Subviews menu for the application icon. Note: This view is available for all application models except for the StComFRApp, the MotFRDTEApp, and the MotFRDCEApp. The options that can be configured in this view are: Automatic Frame Relay Application reconfiguration. Suppress Alarms if the interface is down. Generate an alarm on an 'ACTIVE' trap. Clear previous alarm on 'ACTIVE' trap. Instructions for each of these options is provided on the right hand side of the view. Frame Relay Manager User s Guide Page 49

51 Frame Relay Application Models Figure 10: Trap Configuration View DLCI Connection View The DLCI Connection view displays connectivity information about each of the DLCIs managed by the Frame Relay application. The Local columns will have an entry for each DLCI on the Device. If the Local DLCI has a connection, then the Remote columns give information about the DLCI at the other end of the PVC. Note: This view is available for all application models except for the MotFRDTEApp and the MotFRDCEApp. Frame Relay Manager User s Guide Page 50

52 Frame Relay Application Models To access this view, select DLCI Connection from the Icon Subviews menu for the application icon. If you are working with the StComFRApp, choose Endpoint Connection from the Icon Subviews. Figure 11: DLCI Connection View Field Local IF.DLCI Explanation This shows the number of the interface and the number of the DLCI associated with that interface. For example, the number 2.26 would mean the ifindex is 2 and the DLCI is 26. Frame Relay Manager User s Guide Page 51

53 Frame Relay Application Models Field Local IP Address Remote Device Remote IF.DLCI Remote IP Address Explanation The IP address associated with a specific DLCI. The model name of the Remote Device that a specific DLCI is connected to. This shows the number of the interface and the number of the DLCI associated with that interface on the remote device. For example, the number 2.26 would mean the ifindex is 2 and the DLCI is 26. The IP address associated with a specific DLCI on the remote device. Frame Relay Manager User s Guide Page 52

54 Frame Relay Application Models The fr1315app Application Model The fr1315app Application Model The following views are available from the fr1315app Icon Subviews menu: Trap Configuration View (Page 49) DLCI Connection View (Page 50) Error Table View (Page 53) Data Link Connection Management Table View (Page 55) Frame Relay Circuit Table View (Page 57) Error Table View This view provides information about errors encountered on each Frame Relay DLCI. The data in this table comes from the frerrtable object in the rfc1315 MIB. This table is dynamically updated as the connections change. This view is accessed by selecting Error Table from the Icon Subviews menu of the fr1315app icon. Frame Relay Manager User s Guide Page 53

55 Frame Relay Application Models Figure 12: Error Table View Field Index Last Error Error Packet Time Detected Explanation The interface index value of the corresponding interface entry. The type of error that was last seen on this interface. An octet string containing as much of the error packet as possible. At a minimum, it must contain the Q.922 Address or as much of the address as was delivered. It is also desirable to have all header and demultiplexing information. The system uptime value when the error was detected. Frame Relay Manager User s Guide Page 54

56 Frame Relay Application Models Data Link Connection Management Table View This view provides information about the management configuration of each Frame Relay DLCI on a device. The data in this table comes from the frdlcmitable object in the rfc1315 MIB. Access this view by selecting DLCMI Table from the Icon Subviews menu for the fr1315app icon. Figure 13: Data Link Connection Management Table View Index Field Explanation The interface index value of the corresponding interface entry. Frame Relay Manager User s Guide Page 55

57 Frame Relay Application Models State Field Address Format Address Length Polling Interval Enquiry Intrvl Error Threshold Monitored Events Max Supported VCs Multicast The data link connection management scheme that is active on this Frame Relay interface. The address format in use on this Frame Relay interface. The address length in octets. Explanation The number of seconds between successive status enquiry messages. The number of status enquiry intervals that pass before a full status enquiry message is issued. The maximum number of unanswered status enquiries that the equipment accepts before declaring that the interface is not operational. The total number of status polling intervals including the error threshold. The maximum number of virtual circuits allowed for this Frame Relay interface. Indicates whether the Frame Relay interface is using a multicast service. Frame Relay Manager User s Guide Page 56

58 Frame Relay Application Models Frame Relay Circuit Table View The view provides information about each virtual circuit. The data in this table comes from the frcircuittable object in the rfc1315 MIB. Access the Circuit Table view by selecting Circuit Table from the Icon Subviews menu of the fr1315app icon. Figure 14: Frame Relay Circuit Table View Frame Relay Manager User s Guide Page 57