Frame Relay Manager User s Guide

Transcription

1 Titlepage Frame Relay Manager User s Guide Document Device Management

2 Copyright Notice Document Copyright February 2001 Aprisma Management Technologies, Inc., 121 Technology Drive, Durham, NH USA. 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., 121 Technology Drive, Durham, NH 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 anti-virus system is 100 percent effective, we strongly recommend that you write-protect the licensed software and verify (with an anti-virus system in which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc. 121 Technology Drive Durham, NH Phone: U.S. toll-free: Web site: Frame Relay Manager User s Guide Page 3

4 Contents Introduction 7 Terminology...7 Frame Relay Networks...8 SPECTRUM and Wide Area Networks...9 SPECTRUM and Frame Relay...10 The Management Information Base (MIB)...10 SpectroGRAPH Models...12 Modeling Frame Relay Networks 13 Previous SPECTRUM Modeling Scheme...13 New SPECTRUM Modeling Scheme...15 Modeling Topologies...16 AutoDiscovery of Frame Relay Connections...18 Unresolved Connections...19 Reading a Frame Relay Map...19 Resolving the Connections...23 Importing Connectivity Information 27 Creating a Comma-Delimited Input File...27 Using the wanimport Tool...28 Managing Frame Relay Networks 30 Configuring and Monitoring DLCI_Port Models...30 Accessing the DLCI_Port Models...31 Information View...35 Setting Polling Intervals...35 DLCI_Port Performance View...37 DLCI_Port Configuration View...38 Port Information...38 External Port Management...39 Internal Port Management...39 Address Information...40 Frame Relay Manager User s Guide Page 4

5 Contents Contents DLCI_Port Threshold View...41 Setting Up Thresholds...42 DLCI_Port Service Information View...44 Virtual Circuit Status Changes...45 Determining Network Congestion...45 FECN and BECN Rates...46 Excessive Discards...49 Determining the Need for Greater Bandwidth...51 fr1315 Application 53 fr1315app Views...53 Trap Configuration View...54 DLCI Connection View...55 fr1315app Error Table View...57 Data Link Connection Management Table View...58 Frame Relay Circuit Table View...61 rfc2115app 64 rfc2115app Views...64 Frame Relay Trap Configuration View...64 Frame Relay DLCI Connection View...66 Frame Relay Circuit Table...68 Frame Relay Data Link Connection Management Table...71 Frame Relay Error Table...74 CiscoFRApp 77 CiscoFRApp Views...77 Frame Relay Trap Configuration View...77 Frame Relay DLCI Connection View...78 Frame Relay Circuit Table...80 Frame Relay Data Link Connection Management Table...83 Frame Relay Error Table...85 Cisco Frame Relay LMI Table...88 Cisco Frame Relay Circuit Table...90 Cisco Frame Relay Extended Circuit Table...92 Cisco Frame Relay Map Table...93 Frame Relay Manager User s Guide Page 5

6 Contents Contents wffrrlyapp 96 wffrrlyapp Views...96 Interface Information View...96 Interface DLCMI Info Interface DLCMI Info FR Service Record View Virtual Circuit Table Circuit Table Circuit Table Virtual Circuit Detail View Circuit Error Table Lapf Table Lapf Info Lapf Info FRF4 Signalling Table FRF4 SVC Signalling Table SVC Options Table SVC Options Table Active Call Table Active Call Table Active Call Table PVC Passthru Interface Table PVC Passthru Mapping Table Frame Relay DLCI Connection View Alarms 136 Prob01b Prob01b Prob01b Prob01b8001e Prob01b Prob01b Prob01b Index 142 Frame Relay Manager User s Guide Page 6

7 Introduction The section provides an overview of Frame Relay networks and SPECTRUM s approach to modeling them. Common Frame Relay terminology is also defined. This document describes how SPECTRUM s Frame Relay Manager component is designed to provide more effective management of Frame Relay networks by letting you model and simultaneously monitor multiple virtual circuits for each Frame Relay interface. Terminology The following Frame Relay terms are used in this document: Committed Information Rate (CIR) is a guaranteed amount of bandwidth that is leased by a customer from a service provider. Burst Excess (BE) is additional bandwidth that may be used by the customer but, depending on the amount of network traffic, may not always be available. Discard Eligible (DE) refers to packets in excess of the Committed Information Rate. If total network traffic exceeds the maximum bandwidth, these excess packets are discarded. Permanent Virtual Circuits (PVCs) are permanently established virtual circuits between two devices. Switched Virtual Circuits (SVCs) are temporarily established virtual circuits between two devices. Data Link Connection Index (DLCI) is a value that identifies a particular PVC or SVC in a Frame Relay network. Forward Explicit Congestion Notification (FECN) is a bit set on a frame in a Frame Relay network to inform the device receiving the frame that network congestion was experienced along the network path. Frame Relay Manager User s Guide Page 7

8 Introduction Frame Relay Networks Backward Explicit Congestion Notification (BECN) is a bit set on a frame in a Frame Relay network. This frame is returned to the transmitting device to inform the device that network congestion was experienced along the network path and the frame may not be transmitted. 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. Permanent virtual circuits (PVCs) are the most common in today s networking industry while switched virtual circuits (SVCs) are not widely used. 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. Frame Relay Manager User s Guide Page 8

9 Introduction SPECTRUM and Wide Area Networks SPECTRUM and Wide Area Networks In previous versions of SPECTRUM, all wide area network connections have been modeled with the same modeling scheme. The WA_Link and WA_Segment SpectroGRAPH models have provided the abstraction of these connections. This is in contrast to how SPECTRUM models other connection types, such as Ethernet or Token Ring, where there is no connection model. Wide area networks can consist of many devices, miles of cable, and even satellite links between two wide area routers. Modeling these complex connections is much more involved than modeling a single twisted-pair cable that connects two Ethernet devices. The development of a new modeling scheme to represent a Frame Relay network has become necessary due to the following limitations: The WA_Link and WA_Segment modeling concepts are not adequate for modeling wide area connections and need to be replaced with a simpler and more useful design. Several wide area protocols, including X.25 and Frame Relay, are time multiplexed, meaning that they allow multiple virtual circuits for each interface. Until now, SPECTRUM has only been able to model one connection for each wide area interface. Frame Relay Manager User s Guide Page 9

10 Introduction SPECTRUM and Frame Relay SPECTRUM and Frame Relay SPECTRUM s Frame Relay Manager component represents a new modeling approach that introduces the concept of sub-interface. Through a click zone on the Frame Relay interface icon, you can access all of the sub-interface models for that Frame Relay interface. This allows each virtual circuit to have an established, active connection in SPECTRUM at the same time, which means SPECTRUM can effectively monitor all virtual circuits and let you perform the following management tasks: 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. The Management Information Base (MIB) SPECTRUM s Frame Relay Manager supports all of the following Frame Relay MIBs: rfc1315, rfc2115, Cisco-Frame-Relay MIB, and Wellfleet FR2 MIB. An application model representing the appropriate MIB is created when a device that supports that MIB is modeled. The table below shows the MIB and the application model type that is created to support that MIB: MIB rfc1315 rfc2115 Cisco-Frame-Relay Wellfleet FR2 Application Model fr1315app rfc2115app CiscoFrApp wffrmrlyapp Frame Relay Manager User s Guide Page 10

11 Introduction SPECTRUM and Frame Relay Each of these application models have various views available. These views are explained in the sections of this guide that detail the application model types (see fr1315 Application on Page 53, rfc2115app on Page 64, CiscoFRApp on Page 77, and wffrrlyapp on Page 96). 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. Application Icons Frame Relay Manager User s Guide Page 11

12 Introduction SpectroGRAPH Models SPECTRUM and Frame Relay This section provides descriptions of the models and corresponding icons that have been developed to manage a Frame Relay network in SPECTRUM. For detailed information on using these models to manage your Frame Relay network, see Managing Frame Relay Networks on Page 30. FrameRelayPort Icon The FrameRelayPort icon allows you to access DLCI_Port models associated with a Frame Relay interface. The FrameRelayPort icon is located in both the Interface Device and Device Topology views. DLCI_Port Icon DLCI_Port models represent the connections on Frame Relay devices. One of these models is created for each distinct virtual circuit on a Frame Relay interface. These models are accessed through the double-click zone on the FrameRelayPort icon. A comprehensive performance graph is available from the DLCI_Port model. Also, a Port Threshold view allows the user to establish thresholds for FECN rates, BECN rates, Bits In, and Bits Out. When one of these rates exceeds the predetermined threshold value, an alarm is generated to alert the user. Frame Relay Manager User s Guide Page 12

13 Modeling Frame Relay Networks Previous SPECTRUM Modeling Scheme Modeling Frame Relay Networks This section describes how Frame Relay Manager s new modeling scheme works with AutoDiscovery and explains how to manually resolve any unresolved connections in the network model AutoDiscovery creator. The challenge inherent in modeling WAN connections is that several WAN protocols, including X.25 and Frame Relay, are time-multiplexed, and as such they allow multiple virtual channels per interface. In previous versions of SPECTRUM, only one connection per interface has been supported. This issue has been addressed by the new modeling design to support Frame Relay. Most aspects of this design should be applicable to other WAN protocols, including X.25 and ISDN. Previous SPECTRUM Modeling Scheme The previous SPECTRUM modeling scheme for Frame Relay only allowed for a single device model to be connected to a single interface model. SPECTRUM could only model multiple Frame Relay connections in the following manner: one WA_Link model would be created to represent each Frame Relay connection each WA_Link would collect a WA_Segment model one of the WA_Segment models (on a first come-first served basis) would be connected to the Frame Relay interface model all other WA_Links models, representing the other Frame Relay connections, would only be adjacent to the Frame Relay device Most Frame Relay connections were not resolved to the interface, and a user could only get information about these Frame Relay circuits by viewing tables from the rfc1315app model in the Application view. Frame Relay Manager User s Guide Page 13

14 Modeling Frame Relay Networks Figure 1 shows the model types and relations used in the modeling of Frame Relay circuits with this method. Frame Relay is not modeled any differently than other wide area connections and there are no practical ways to represent multiple Frame Relay circuits on a single interface. Figure 1: Previous SPECTRUM Modeling of Frame Relay WA_Link Collects WA_Segment WA_Segment Device Model Is_Adjacent_to Is_Adjacent_to Is_Adjacent_to Collects WA_Link WA_Link HASPART Monitors Collects Connects_to Connects_to WA_Segment Frame Relay Manager User s Guide Page 14

15 Modeling Frame Relay Networks New SPECTRUM Modeling Scheme New SPECTRUM Modeling Scheme The problem of modeling multiple Frame Relay circuits on a single interface has been solved through the introduction of a sub-interface model, which is created using the DLCI_Port model type. DLCI_Port models have a HASPART relation to the Frame Relay interface model. The DLCI_Port models represent a distinct Frame Relay circuit (or DLCI) on that interface. Each DLCI_Port model calculates statistics for the circuit that it represents. To further improve the modeling scheme, the WA_Link and WA_Segment models have been removed. Figure 2 illustrates the new modeling scheme. Each DLCI_Port model gets status and performance information independently of the Frame Relay interface model. This way each of the DLCI_Port models that may be associated with a particular interface can generate separate alarms. Figure 2: New SPECTRUM Modeling of Frame Relay Device Model HASPART Device Model Connects_to HASPART FrameRelayPort Connects_to Device Model Frame Relay Manager User s Guide Page 15

16 Modeling Frame Relay Networks Modeling Topologies Modeling Topologies This section provides two examples of modeling topologies that can be used to model a Frame Relay network with SPECTRUM. Each modeling topology can easily be customized to better suit the needs of the network administrator. Figure 3 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 4 shows the possible modeling of a large and complex Frame Relay network. Figure 3: Basic Frame Relay Modeling BOSTON NEW YORK Frame Relay Manager User s Guide Page 16

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

18 Modeling Frame Relay Networks AutoDiscovery of Frame Relay Connections AutoDiscovery of Frame Relay Connections The major challenge that modeling a Frame Relay network presents to the AutoDiscovery process is that there is no correlation of 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 DLCI-to-DLCI connections. This level of connectivity is necessary to get statistics for each circuit and to take full advantage of other SPECTRUM functionality like fault isolation. The AutoDiscovery process has been modified to support SPECTRUM s new way of modeling Frame Relay connections. Now, when a connection between two Frame Relay interface models is inferred, the models are associated through the Virtual_Links_With relation. When the Virtual_Links_With association is created between two interfaces, the AutoDiscovery intelligence attempts to determine which DLCI models are connected. If the Cisco Frame Relay MIB is supported, 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 will sample the traffic going over each DLCI associated with both interfaces over a pre-determined time period. At the end of this Frame Relay Manager User s Guide Page 18

19 Modeling Frame Relay Networks 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 of a DLCI on the other interface. For this method to be successful, there must be traffic going over the Frame Relay circuits. If any of these methods succeed, connections are made between the corresponding DLCI_Port models and their connected device models. A Links_with association is created between the two DLCI_Port models. If these methods fail, the DLCI-to-DLCI connectivity must be modeled by hand. 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 you do not have live pipes enabled), or if there are no pipes connecting devices that you know should be connected, then there are unresolved connections that you will need to resolve manually. 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 27. 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. Reading a Frame Relay Map Before you can resolve DLCI_Port connections in your network model, you must determine what the connections are. You can do this by examining a Frame Relay map as in the following example, which assumes these facts: There is a Cisco Frame Relay router (Router A) with an IP Address of that has two interfaces (Serial0/0 and Serial1/1). Frame Relay Manager User s Guide Page 19

20 Modeling Frame Relay Networks Serial0/0 and Serial0/1provide an interface to the x subnet. AutoDiscovery was run on the range and modeled two routers that are associated with Router A: Routers B ( ) and C ( ). For one of the previously stated reasons, DLCI-level port resolution was not completed. The Router B and Router C each have one active DLCI_Port, but it needs to be determined which of the DLCI_Port models on Router A connect to which of the DLCI_Port models on Routers B and C. To determine which router connects to which DLCI_port, telnet to the cisco Router Issue the following commands (see note below): enable show frame-relay map Note: This example, uses a Cisco Router EXEC command to display the Frame Relay map. Other vendors may have similar functionality and procedures to display this type of map. Refer to your device s local management documentation for more information. Figure 5 shows what the Cisco Router Frame Relay map would look like for the network described above. The interface identifier, next hop IP address (which represents one of the previously mentioned routers on the other side of the link), and the corresponding DLCI_Port number (where the router on the other side of the link connects to our router) are highlighted. Frame Relay Manager User s Guide Page 20

21 Modeling Frame Relay Networks Figure 5: A Sample Cisco Router Frame Relay Map Interface Identifier Next Hop IP Address Corresponding DLCI Serial0/0 (up): ip dlci 26 (0x1A, 0x4A0),static, IETF Serial0/1 (up): ip dlci 28 (0x1C,0x4C0), static, IETF Figure 6 shows a correlation between the Frame Relay map and SPECTRUM s modeling of the same network. Frame Relay Manager User s Guide Page 21

22 Modeling Frame Relay Networks Figure 6: SPECTRUM Frame Relay Map dlci 26 Serial 0/0 Serial 0/ x Subnet dlci 28 The Frame Relay map shows that there are two Frame Relay interfaces on Router A: Serial0/0 and Serial0/1. The Frame Relay map also shows that Router B ( ) should be pasted onto DLCI_Port 26 and Router C ( ) onto DLCI_Port 28. Frame Relay Manager User s Guide Page 22

23 Modeling Frame Relay Networks If there is any question about which ifindex (or interface number) corresponds to the interface name (i.e., Serial0, Serial1), the Interface Configuration table in the Device Configuration view of the router provides this information. Resolving the Connections Figure 7 shows Router A s Device Topology view with an Off-Page Reference icon representing the unresolved connection for Router B. An unresolved connection will show as a blue pipe if you are using live pipes. It will show as silver if you are not using live pipes. Router B s Off-Page Reference icon must be resolved to the corresponding DLCI_Port model. In this example, the Frame Relay connection would be resolved with the following procedure: 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 7). 6 From Router A s Device Topology view, navigate into the FrameRelayPort model s own Device Topology (Figure 8) 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 23

24 Modeling Frame Relay Networks Figure 7: 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 24

25 Modeling Frame Relay Networks Figure 8: FrameRelayPort Device Topology View with Resolved Connection Router B Connection Resolved DLCI_Port Model Frame Relay Manager User s Guide Page 25

26 Modeling Frame Relay Networks Figure 8 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. 9 Paste the Router A model onto the correct DLCI_Port model. Frame Relay Manager User s Guide Page 26

27 Importing Connectivity Information This section describes using the wanimport tool to import Frame Relay connectivity information contained in an 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 27

28 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 s SS-Tools directory. The import tool command takes 4 arguments, two are required and two are optional. NT Syntax: wanimport.bat -vnm <vnm_name> -i <input_file> [-o <outputfile>] [-debug] Solaris Syntax: wanimport -vnm <vnm_name> -i <input_file> [-o <outputfile>] [-debug] Frame Relay Manager User s Guide Page 28

29 Importing Connectivity Information Using the wanimport Tool 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 29

30 Managing Frame Relay Networks Configuring and Monitoring DLCI_Port Models Managing Frame Relay Networks This section describes managing a Frame Relay network with SPECTRUM. It provides information on setting up thresholds, monitoring network performance, and diagnosing some common network problems. Configuring and Monitoring DLCI_Port Models DLCI_Port models are contained in the Sub-interface view of the FrameRelayPort model. You can access the FrameRelayPort model from the Frame Relay device s Device Topology or Interface Device view. DLCI_Port models allow you to: Monitor the quality of service through the Port Performance view Set external and internal attributes through the Port Configuration view. Set polling intervals through the Command Line Interface, the Information view, or the Internal Management view. Set threshold alarms for each DLCI_Port through the Port Threshold view. Frame Relay Manager User s Guide Page 30

31 Managing Frame Relay Networks Accessing the DLCI_Port Models You access the DLCI_Port models from the Device Topology view of the associated FrameRelayPort model. The FrameRelayPort model is accessed through: the Frame Relay device s Device Topology view (Figure 9). or the Frame Relay device s Interface Device view (Figure 10). 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 11). Frame Relay Manager User s Guide Page 31

32 Managing Frame Relay Networks Figure 9: Device Topology View with FrameRelayPort Model BOSTON Frame Relay Manager User s Guide Page 32

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

34 Managing Frame Relay Networks Figure 11: DLCI_Port Models in a FrameRelayPort Device Topology View DLCI_Port Model Frame Relay Manager User s Guide Page 34

35 Managing Frame Relay Networks Information View This view allows you to change polling and logging information for the DLCI_Port model. 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. You can change the polling interval for each DLCI_Port model individually in the Information view of that model as follows: 1 Open the Information view for the DLCI_Port model. 2 Enter new polling interval (in seconds) in the Poll Interval field. 3 Select Save All Changes from the File menu. 4 Click OK in the Save Changes? dialog box. Setting Polling Intervals By default, DLCI_Port models have their polling intervals set to 0. You can change the polling interval for each individual DLCI_Port models through their Information views. You can also change the polling interval using the Search Manager s Global Attribute Editor. 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. 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. Frame Relay Manager User s Guide Page 35

36 Managing Frame Relay Networks 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 value. 12 Click the Apply button. For complete instructions on using the Search Manager, refer to the Search Manager User s Guide. There is also a Command Line Interface (CLI) script called update_mtype, which 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 guide. Frame Relay Manager User s Guide Page 36

37 Managing Frame Relay Networks DLCI_Port Performance View The Performance view of DLCI_Port models shows Load, Frame In Rate, Frame Out Rate, BECN Rate, FECN Rate and CIR percentages. All rates are in occurrences per second. Load is the percentage of Committed Burst plus Burst Excess that is currently being used. 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. The DLCI_Port Performance view s Detail button accesses the Port Detail view, which 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. This view can also be accessed by single-clicking the Port Detail button in the DLCI_Port Configuration view. 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 DLCI_Port Configuration View on Page 38. Frame Relay Manager User s Guide Page 37

38 Managing Frame Relay Networks DLCI_Port Configuration View The DLCI_Port Configuration view displays external rfc1315 MIB attributes corresponding to the DLCI that the port represents. For Frame Relay devices that support the frcircuitcommittedburst, frcircuitexcessburst, and frcircuitthroughput MIB objects, these values can be set in the External Port Management area of this view. For devices that do not support these MIB objects, you can use the Internal Port Management view to set these values. These values must be set for the Port Performance view to return accurate information. If the device you are working with supports the CiscoFrApp (see Page 77), the DLCI_Port Configuration view for each Cisco DLCI port displays the value of the Cisco cfrextcircuitifname MIB object in the Description field. This MIB object provides the ifdesc of the Frame Relay sub-interface associated with a particular DLCI. You can also use the DLCI_Port Configuration view to set the polling interval for the port. In order to generate reports from the DLCI_Port model, a polling interval must be specified. To access the DLCI_Port Configuration view, highlight the DLCI_Port model and select Port Configuration from the Icon Subviews menu. Port Information This area of the Port Configuration view provides the following information: Creation Time The system uptime value when this virtual circuit was created whether by the Data Link Connection Management Interface or by an SNMP SetRequest. Last Change The system uptime value when there was last a change in the state of this virtual circuit. Frame Relay Manager User s Guide Page 38

39 Managing Frame Relay Networks Rcvd FECNs The number of frames received from the network that indicate forward congestion since this virtual circuit was created. Rcvd BECNs The number of frames received from the network that indicate backward congestion since this virtual circuit was created. External Port Management For Frame Relay devices that support the Committed Burst, Excess Burst, and Throughput MIB objects, these values must be set in this area of the DLCI_Port Configuration view. To set these values, do the following: 1 Enter the value. 2 Select Save All Changes from the File menu. 3 Click OK. Internal Port Management For Frame Relay devices that do not support the Committed Burst, Excess Burst, and Throughput MIB objects, these values can be set in the Internal Management area of the DLCI_Port Configuration view. To set these values, do the following: 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. Frame Relay Manager User s Guide Page 39

40 Managing Frame Relay Networks Because you can override the Committed Burst rate and Burst Excess value, you can use the Performance view as a what if tool. For example, if you have a 128k PVC that rarely exceeds Committed Burst, and you wonder what effect reducing the service to 64k would have, you can 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 once when it is initially launched. If you make changes to the Committed Burst or Burst Excess values, you must close the Performance view and bring it up again for the changes to take effect. You also have the option of launching a second view with the new bandwidth values, and comparing the two graphs. Address Information This area of the DLCI_Port Configuration view provides network addressing information associated with this DLCI_Port. Although this IP information can be edited, SPECTRUM does attempt to determine this information from the ipaddrtable. IP Address The IP Address of this DLCI _Port. Frame Relay interfaces on some devices can be given multiple IP Addresses. Each IP Address can correspond to a different PVC running over a DLCI_Port. In such cases, the IP Address field can be filled in with the corresponding IP Address. Remote IP 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 the cfrmapaddress object of the cfrmaptable. IP Mask The mask of the IP subnet of which the circuit represented by this DLCI_Port is a part. The IP Mask indicates which portion of the destination address must match the address of the subnet to be delivered to that subnet. Frame Relay Manager User s Guide Page 40

41 Managing Frame Relay Networks 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 would get broken down into the subnet address The Frame Relay device would look through its IP route tables for that subnet address and its corresponding interface. All frames with an address within the range and would be transmitted from that interface to that subnet. DLCI_Port Threshold View DLCI_Port models have a Port Threshold view that allows the user to establish 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. The following thresholds can be set in this view: Bits Per Second Received The average number of bits received by the DLCI_Port since the last poll. Bits Per Second Transmitted The average number of bits transmitted by the DLCI_Port since the last poll. BECNs Per Frames Transmitted 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. FECNs Per Frames Received The percentage of frames with their FECN bits set that have been received over this DLCI_Port since the last poll. Frame Relay Manager User s Guide Page 41

42 Managing Frame Relay Networks 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. 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. Caution: 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 by the user, 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 Up 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. Figure 12 describes the functionality provided by the high and low threshold feature for DLCI_Port models. Frame Relay Manager User s Guide Page 42

43 Managing Frame Relay Networks Figure 12: 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 43

44 Managing Frame Relay Networks 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 by the user 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. The following information can be entered: Provider 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 which carriers provide service for which circuits. Customer Users who are Frame Relay providers and manage other companies Frame Relay networks can use this field to indicate who the Frame Relay customer is. Primary Contact The name, phone number, and/or address of the person to contact if there is a problem with this circuit. Secondary Contact The name, phone number, and/or address of a secondary person to contact if there is a problem with this circuit. Service Notes 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 44

45 Managing Frame Relay Networks Virtual Circuit Status Changes Virtual Circuit Status Changes Any change in the status of a virtual circuit generates the frdlcistatuschange trap (Prob01b80002, Prob01b80003, Prob01b refer to Alarms). This can be an indication of a virtual circuit being removed, becoming inactive, or a new circuit being added. In the case of a new circuit being added (Prob01b80004), the status change trap is received announcing the presence of the new circuit and the IfIndex.DLCI value of the trap is set to uniquely identify the new circuit. However, there are situations when the corresponding DLCI_Port model is not created in SPECTRUM and must be created 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 App 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. Determining Network Congestion A congested Frame Relay network will not provide good quality of service to a subscriber. Heavy data transmissions may have to be rescheduled, more traffic may need to be routed through uncongested virtual circuits, or better service needs to be established by the service provider. The following sections detail the warning signs of Frame Relay network congestion. Frame Relay Manager User s Guide Page 45

46 Managing Frame Relay Networks FECN and BECN Rates Determining Network Congestion 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. A Frame Relay device can receive frames with their FECN bits set, but this is not always guaranteed as many frames with their FECN bits set may be discarded before reaching the receiving Frame Relay device. Frames with their BECN bits set will be returned from the Frame Relay network to the transmitting Frame Relay device to alert that device of congestion on the network. Frame Relay Manager User s Guide Page 46

47 Managing Frame Relay Networks Determining Network Congestion 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. Frame Relay Manager User s Guide Page 47

48 Managing Frame Relay Networks Determining Network Congestion 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 (Prob01b8001e, Prob01b see Alarms on Page 136). 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 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. Frame Relay Manager User s Guide Page 48

49 Managing Frame Relay Networks Excessive Discards Determining Network Congestion Excessive discards can be an indication of network congestion or can indicate 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 13). 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 49

50 Managing Frame Relay Networks Determining Network Congestion Figure 13: The Link Information View Frame Relay Manager User s Guide Page 50

51 Managing Frame Relay Networks Determining the Need for Greater Bandwidth 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. 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 (Prob01b80022, Prob01b see Alarms on Page 136). 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. Frame Relay Manager User s Guide Page 51

52 Managing Frame Relay Networks Determining the Need for Greater Bandwidth 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 52

53 fr1315 Application This section provides descriptions of the fr1315app and the rfc1315 MIB objects. The rfc1315 Frame Relay MIB is composed of three groups, one describing errors, one defining the Data Link Connection Management Interface (DLCMI), and a third describing circuits. fr1315app Views This section describes the views available for the fr1315app application. There are three application-specific subviews available from the fr1315app Icon Subviews menu: Trap Configuration view (Figure 14) DLCI Connection view (Figure 15) Error Table view (Figure 16) Data Link Connection Management Table view (Figure 17) Frame Relay Circuit Table view (Figure 18) Frame Relay Manager User s Guide Page 53

54 fr1315 Application Trap Configuration View The Trap Configuration view allows a user to specify what happens if SPECTRUM receives a frdlcistatuschange trap. The options 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. Access: From the Icon Subviews menu for the fr1315app icon, select Trap Configuration. Figure 14: Trap Configuration View Frame Relay Manager User s Guide Page 54

55 fr1315 Application 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. Access: From the Icon Subviews menu for the fr1315app icon, select DLCI Connection. Figure 15: DLCI Connection View Frame Relay Manager User s Guide Page 55

56 fr1315 Application Local IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Local IP Address The IP address associated with a specific DLCI. Remote Device The model name of the Remote Device that a specific DLCI is connected to. Remote IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface on the remote device. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Remote IP Address The IP address associated with a specific DLCI on the remote device. Frame Relay Manager User s Guide Page 56

57 fr1315 Application fr1315app Error Table View This view provides information about error s 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. Access: From the Icon Subviews menu for the fr1315app icon, select Error Table. Figure 16: Error Table View Index The interface index value of the corresponding interface entry. Frame Relay Manager User s Guide Page 57

58 fr1315 Application Last Error The type of error that was last seen on this interface. Possible types are: Error Packet 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. Time Detected The system uptime value when the error was detected. 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: From the Icon Subviews menu for the fr1315app icon, select DLCMI Table. Frame Relay Manager User s Guide Page 58

59 fr1315 Application Figure 17: Data Link Connection Management Table View Index The interface index value of the corresponding interface entry. State The data link connection management scheme that is active on this Frame Relay interface. Address Format The address format in use on this Frame Relay interface. Address Length The address length in octets. Polling Interval The number of seconds between successive status enquiry messages. Frame Relay Manager User s Guide Page 59

60 fr1315 Application Enquiry Intrvl The number of status enquiry intervals that pass before a full status enquiry message is issued. Error Threshold The maximum number of unanswered status enquiries that the equipment accepts before declaring that the interface is not operational. Monitored Events The total number of status polling intervals including the error threshold. Max Supported VCs The maximum number of virtual circuits allowed for this Frame Relay interface. Multicast Indicates whether the Frame Relay interface is using a multicast service. Frame Relay Manager User s Guide Page 60

61 fr1315 Application 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: From the Icon Subviews menu for the fr1315app icon, select Circuit Table. Figure 18: Frame Relay Circuit Table View Frame Relay Manager User s Guide Page 61

62 fr1315 Application Index The index value of the interface entry that this virtual circuit is layered onto. DLCI The data link connection identifier for this virtual circuit. State The operational state of this particular virtual circuit. Rcvd FECNs The number of frames received from the network that indicate forward congestion since the virtual circuit was created. Rcvd BECNs The number of frames received from the network that indicate backward congestion since the virtual circuit was created. Frames Sent The number of frames transmitted from this virtual circuit since it was created. Octets Sent The number of octets transmitted from this virtual circuit since it was created. Frames Rcvd The number of frames received over this virtual circuit since it was created. Octets Rcvd The number of octets received over this virtual circuit since it was created. Creation Time The system uptime value when this virtual circuit was created whether by the Data Link Connection Management Interface or by an SNMP SetRequest. Frame Relay Manager User s Guide Page 62

63 fr1315 Application Last Change The system uptime value when there was last a change in the state of this virtual circuit. Committed Burst The maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval. Excess Burst The maximum amount of uncommitted data bits, that the network will attempt to deliver during the measurement interval. Throughput The average number of frame relay information field bits transferred per second, in one direction, across a network interface and measured over the measurement interval. Frame Relay Manager User s Guide Page 63

64 rfc2115app rfc2115app This section provides descriptions of the rfc2115app Views and the rfc2115app MIB objects. rfc2115app Views This section describes the views available for the rfc2115app application. There are five application-specific subviews available from the Icon Subviews menu: Trap Configuration View(Figure 19) DLCI Connection View(Figure 21) Frame Relay Circuit Table(Figure 21) Data Link Connection Management Table view (Figure 22) Error Table view (Figure 23) Frame Relay Trap Configuration View The Trap Configuration view allows a user to specify what happens if SPECTRUM receives a frdlcistatuschange trap. The options 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. Access: From the Icon Subviews menu for the rfc2115app icon, select Trap Configuration. Frame Relay Manager User s Guide Page 64

65 rfc2115app Figure 19: Frame Relay Trap Configuration View Frame Relay Manager User s Guide Page 65

66 rfc2115app Frame Relay 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. Access: From the Icon Subviews menu for the rfc2115app icon, select DLCI Connection. Figure 20: Frame Relay DLCI Connection View Frame Relay Manager User s Guide Page 66

67 rfc2115app Local IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Local IP Address The IP address associated with a specific DLCI. Remote Device The model name of the Remote Device that a specific DLCI is connected to. Remote IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface on the remote device. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Remote IP Address The IP address associated with a specific DLCI on the remote device. Frame Relay Manager User s Guide Page 67

68 rfc2115app Frame Relay Circuit Table This table contains information about specific Data Link Connections or virtual circuits.the data in this table comes from the frcircuittable object in the rfc2115 MIB. Access: From the Icon Subviews menu for the rfc2115app icon, select Circuit Table. Figure 21: Frame Relay Circuit Table Index The ifindex value of the corresponding ifentry. Frame Relay Manager User s Guide Page 68

69 rfc2115app DLCI The Data Link Connection Identifier for this virtual circuit. State This variable indicates whether the particular virtual circuit is operational. Received FECNs The number of frames received from the network indicating forward congestion since the virtual circuit was created. Received BECNs The number of frames received from the network indicating backward congestion since the virtual circuit was created. Frames Sent The number of frames sent from this virtual circuit since it was created. Octets Sent The number of octets sent from this virtual circuit since it was created. Frames Received The number of frames received over this virtual circuit since it was created. Octets Received The number of octets received over this virtual circuit since it was created. Creation Time The value of sysuptime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest. Last Change The value of sysuptime at the last change in the virtual circuit state. Frame Relay Manager User s Guide Page 69

70 rfc2115app Committed Burst This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval. Excess Burst This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval. Throughput Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. Multicast This indicates either that the VC is unicast(i.e. not multicast), or the type of multicast service subscribed to. Type Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface. Discards The number of inbound frames dropped because of format errors, or because the VC is inactive. Received DEs The number of inbound frames dropped because of format errors, or because the VC is inactive. Sent DEs The number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. Frame Relay Manager User s Guide Page 70

71 rfc2115app Logical Index This field normally has the same value as the IF Index. It has a different when an implementation associates a virtual ifentry with a DLC or set of DLCs, in order to associate higher layer objects. Row Status This object is used to create a new row or modify or destroy an existing row, in the manner described in the definition of the RowStatus textual convention. Frame Relay Data Link Connection Management Table 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 rfc2115 MIB. Access: From the Icon Subviews menu for the rfc2115app icon, select DLCMI Table. Frame Relay Manager User s Guide Page 71

72 rfc2115app Figure 22: Frame Relay Data Link Connection Management Table Index The ifindex value of the corresponding ifentry. State This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface. Address Format This variable states which address format is in use on the Frame Relay interface. Frame Relay Manager User s Guide Page 72

73 rfc2115app Address Length This variable states the address length in octets. Polling Interval This is the number of seconds between successive status enquiry messages. Enquiry Interval This is the number of status enquiry intervals that pass before issuance of a full status enquiry message. Error Threshold This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down. Monitored Events This is the number of status polling intervals over which the error threshold is counted. Max Supported VCs This is the maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. Multicast This indicates whether the Frame Relay interface is using a multicast service. Status This indicates the status of the Frame Relay interface as determined by the performance of the DLCMI. Row Status This is the SNMP Version 2 Row Status Variable. Frame Relay Manager User s Guide Page 73

74 rfc2115app Frame Relay Error Table This view provides information about errors encountered on each Frame Relay DLCI. The data in this table comes from the frerrtable object in the rfc2115 MIB.This table is dynamically updated as the connections change. Access: From the Icon Subviews menu for the rfc2115app icon, select Error Table. Figure 23: Frame Relay Error Table Index The ifindex value of the corresponding ifentry. Frame Relay Manager User s Guide Page 74

75 rfc2115app Error Type The type of error that was last seen on this interface. The following table shows the possible error types. Table 1: Possible Error Types Error receiveshort receivelong illegaladdress unknownaddress dlcmiprotoerr dlcmiunknownie dlcmisequenceerr dlcmiunknownrpt Description Frame was not long enough to allow demultiplexing - the address field was incomplete, or for virtual circuits using Multiprotocol over Frame Relay, the protocol identifier was missing or incomplete. Frame exceeded the maximum length configured for this interface. Address field did not match configured format. Frame received on a virtual circuit that was not active or administratively disabled. Unspecified error occurred when attempting to interpret the link maintenance frame. Link maintenance frame contained an Information Element type which is not valid for the configured link maintenance protocol. Link maintenance frame contained a sequence number other than the expected value. Link maintenance frame contained a Report Type Information Element whose value was not valid for the configured link maintenance protocol. noerrorsincereset No errors have been detected since the last cold start or warm start. Frame Relay Manager User s Guide Page 75

76 rfc2115app Error Data This contains an octet string containing as much of the error packet as possible. Error Time This is the value of sysuptime at which the error was detected. Error Faults This is the number of times the interface has gone down since it was initialized. Fault Time This is the value of sysuptime at the time when the interface was taken down due to excessive errors. Frame Relay Manager User s Guide Page 76

77 CiscoFRApp This section provides descriptions of the CiscoFRApp Views and the CiscoFRApp MIB objects. CiscoFRApp Views This section describes the views available for the CiscoFRApp application. There are nine application-specific subviews available from the Icon Subviews menu: Trap Configuration View(Figure 24) DLCI Connection View(Figure 25) Frame Relay Circuit Table(Figure 26) Data Link Connection Management Table view (Figure 27) Error Table view (Figure 28) Cisco Frame Relay LMI Table (Figure 29) Cisco Frame Relay Circuit Table (Figure 30) Cisco Frame Relay Extended Circuit Table (Figure 31) Cisco Frame Relay Map Table (Figure 32) Frame Relay Trap Configuration View The Trap Configuration view allows a user to specify what happens if SPECTRUM receives a frdlcistatuschange trap. The options 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. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Trap Configuration. Frame Relay Manager User s Guide Page 77

78 CiscoFRApp Figure 24: Frame Relay Trap Configuration View Frame Relay 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. Frame Relay Manager User s Guide Page 78

79 CiscoFRApp Access: From the Icon Subviews menu for the CiscoFRApp icon, select DLCI Connection. Figure 25: Frame Relay DLCI Connection View Local IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Local IP Address The IP address associated with a specific DLCI. Frame Relay Manager User s Guide Page 79

80 CiscoFRApp Remote Device The model name of the remote device that a specific DLCI is connected to. Remote IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface on the remote device. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Remote IP Address The IP address associated with a specific DLCI on the remote device. Frame Relay Circuit Table This table contains information about specific Data Link Connections or virtual circuits. The values in this view come from the frcircuittable object in the rfc1315 MIB. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Circuit Table. Frame Relay Manager User s Guide Page 80

81 CiscoFRApp Figure 26: Frame Relay Circuit Table Index The ifindex value of the corresponding ifentry. DLCI The Data Link Connection Identifier for this virtual circuit. State This indicates whether the particular virtual circuit is operational. Received FECNs The number of frames received from the network indicating forward congestion since the virtual circuit was created. Frame Relay Manager User s Guide Page 81

82 CiscoFRApp Received BECNs The number of frames received from the network indicating backward congestion since the virtual circuit was created. Frames Sent The number of frames sent from this virtual circuit since it was created. Octets Sent The number of octets sent from this virtual circuit since it was created. Frames Received The number of frames received over this virtual circuit since it was created. Octets Received The number of octets received over this virtual circuit since it was created. Creation Time The value of sysuptime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest. Last Change The value of sysuptime when last there was a change in the virtual circuit state Committed Burst This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval. Excess Burst This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval. Frame Relay Manager User s Guide Page 82

83 CiscoFRApp Throughput Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. Frame Relay Data Link Connection Management Table This view provides information about the management configuration of each Frame Relay DLCI on a device. The values in this view come from the frdlcmitable object in the rfc1315 MIB. Access: From the Icon Subviews menu for the CiscoFRApp icon, select DLCMI Table. Frame Relay Manager User s Guide Page 83

84 CiscoFRApp Figure 27: Frame Relay Data Link Connection Management Table Index The ifindex value of the corresponding ifentry. State This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface. Address Format This variable states which address format is in use on the Frame Relay interface. Address Length This variable states the address length in octets. Frame Relay Manager User s Guide Page 84

85 CiscoFRApp Polling Interval This is the number of seconds between successive status enquiry messages. Enquiry Interval The number of status enquiry intervals that pass before issuance of a full status enquiry message. Error Threshold This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down. Monitored Events This is the number of status polling intervals over which the error threshold is counted. Max Supported VCs The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. Multicast This indicates whether the Frame Relay interface is using a multicast service. Frame Relay Error Table This view provides information about error s encountered on each Frame Relay DLCI. The values in this view come from the frerrtable object in the rfc1315 MIB. This table is dynamically updated as the connections change. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Error Table. Frame Relay Manager User s Guide Page 85

86 CiscoFRApp Figure 28: Frame Relay Error Table Index The ifindex Value of the corresponding ifentry. Error Type The type of error that was last seen on this interface. The following table shows the possible error types. Frame Relay Manager User s Guide Page 86

87 CiscoFRApp Table 2: Possible Error Types Error receiveshort receivelong illegaladdress unknownaddress dlcmiprotoerr dlcmiunknownie dlcmisequenceerr dlcmiunknownrpt Description Frame was not long enough to allow demultiplexing - the address field was incomplete, or for virtual circuits using Multiprotocol over Frame Relay, the protocol identifier was missing or incomplete. Frame exceeded the maximum length configured for this interface. Address field did not match configured format. Frame received on a virtual circuit that was not active or administratively disabled. Unspecified error occurred when attempting to interpret the link maintenance frame. Link maintenance frame contained an Information Element type which is not valid for the configured link maintenance protocol. Link maintenance frame contained a sequence number other than the expected value. Link maintenance frame contained a Report Type Information Element whose value was not valid for the configured link maintenance protocol. noerrorsincereset No errors have been detected since the last cold start or warm start. Frame Relay Manager User s Guide Page 87

88 CiscoFRApp Error Data An octet string containing as much of the error packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all header and demultiplexing information. Error Time The value of sysuptime at which the error was detected. Cisco Frame Relay LMI Table This table contains information for the Frame Relay Local Management Interface for a physical interface. The values in this view come from the cfrlmitable object in the Cisco Frame Relay MIB. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Cisco LMI Table. Frame Relay Manager User s Guide Page 88

89 CiscoFRApp Figure 29: Cisco Frame Relay LMI Table Link Status This is the data link status via LMI. Link Type This is the Frame Relay link type. Enquiry Ins This is the number of Status Enquiry messages received. Enquiry Outs This is the number of Status Enquiry messages sent. Status Ins This is the number of Status messages received. Frame Relay Manager User s Guide Page 89

90 CiscoFRApp Status Outs This is the number of Status messages sent. Update Ins This is the number of Update Status messages received. Update Outs This is the number of Update Status messages sent. Status TOs This is the number of times when timeout occurred on waiting for Status message. Status Enq TOs This is the number of times when timeout occurred on waiting for Status Enquiry message. N392 dce This is the LMI error threshold for a DCE interface. N393 dce This is the LMI monitored event count for a DCE interface. T392 dce This is the DCE polling verification timer for a DCE interface. Cisco Frame Relay Circuit Table This table contains information about specific Data Link Connections or virtual circuits. The values in this view come from the cfrcircuittable object in the Cisco Frame Relay MIB. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Cisco Circuit Table. Frame Relay Manager User s Guide Page 90

91 CiscoFRApp Figure 30: Cisco Frame Relay Circuit Table DE Ins This is the number of packets received with the Discarded Eligibility indictor set. DE Outs This is the number of packets transmitted with DE bit set. Drop Pkts Outs This is the number of discarded packets that were to be sent. Circuit Type This is the basic circuit type. Frame Relay Manager User s Guide Page 91

92 CiscoFRApp Cisco Frame Relay Extended Circuit Table This table contains information for Frame Relay virtual circuit that are specific to Cisco implementation.the values in this view come from the cfrextcircuittable object in the Cisco Frame Relay MIB. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Cisco Ext. Circuit Table. Figure 31: Cisco Frame Relay Extended Circuit Table IF Name The name of the main interface or the subinterface that this DLCI is associated with. IF Type The type of the subinterface this DLCI is associated with, if configured. Frame Relay Manager User s Guide Page 92

93 CiscoFRApp Sub IF Index This indicates the network management interface index for the subinterface associated with this DLCI. Map Status The mapping protocols (internally considered as the 'link type') applied on this circuit. The value ranges from 0 to Create Type This identifies the last source of the circuit's creation. Multicast This indicates if this DLCI is a multicast DLCI. Routed DLCI The routed DLCI to pair up with this DLCI for switching function. Routed IF The interface for the routed DLCI that pairs up with this DLCI for switching. Uncompress Ins The number of inbound octets of the data packets, accounted at Frame Relay level after FRF.9 payload decompression is applied. I Uncompress Outs The number of outbound octets of the data packets, accounted at Frame Relay level before FRF.9 payload compression is applied. Cisco Frame Relay Map Table This table contains mapping information for a Frame Relay virtual circuit.the values in this view come from the cfrmaptable object in the Cisco Frame Relay MIB. Access: From the Icon Subviews menu for the CiscoFRApp icon, select Cisco Map Table. Frame Relay Manager User s Guide Page 93

94 CiscoFRApp Figure 32: Cisco Frame Relay Map Table Index The number of the mapping information associated with a certain circuit. Protocol The mapping protocol for this circuit. Address The mapping protocol address at remote end for this DLCI. Type The type for the map creation. Encaps An indication of the encapsulation type for this mapping protocol. Frame Relay Manager User s Guide Page 94

95 CiscoFRApp Broadcast This indicates if broadcast is enabled or disabled. Payload Comp This indicates if payload compression is enabled. Tcp Hdr Comp The TCP header compression type, if applicable. Rtp Hdr Comp The RTP header compression type, if applicable. Payload Comp Type The FR payload compression type, if applicable. Frame Relay Manager User s Guide Page 95

96 wffrrlyapp wffrrlyapp wffrrlyapp Views This section provides descriptions of the wffrrlyapp views and the WellFleet Frame Relay MIB objects. wffrrlyapp Views This section describes the views available for the wffrrlyapp application. There are ten application-specific subviews available from the Icon Subviews menu: Interface Information FR Service Record Virtual Circuit Table Circuit Error Table Signalling Table Lapf Table FRF4 Signalling Table PVC Passthru Interface Table PVC Passthru Mapping Table DLCI Connection View Interface Information View The Interface Information view displays two tables: Interface DLCMI Info 1 and 2. Frame Relay Manager User s Guide Page 96

97 wffrrlyapp wffrrlyapp Views Figure 33: Interface Information View Interface DLCMI Info 1 This section of the Interface Information View displays the following information: Delete The create/delete parameter. Disable The enable/disable parameter. Line Number The line number on which this frame relay interface resides. Frame Relay Manager User s Guide Page 97

98 wffrrlyapp wffrrlyapp Views LL Index The lower layer index uniquely identifies the lower layer in cases where the lower layer may be something other than the physical layer. Circuit The circuit number of this entry. Mngmnt Type Indicates which Data Link Connection Management scheme is active (and by implication, that DLCI it uses). Status The state of the interface. Address States which address format is in use on the FR interface. Address Length States the address length in octets. VCs Configured The number of VCs that are presently configured on the interface. Multicast Indicates if the frame relay provider offers a multicast. Error Type The type of the last specific monitored error. Error Data Contains as much of the error packet as possible. Error Time The time the last error occurred. Error Faults The number of times that the interface has come down due to errors since the system started. The value is reset when a restart parameter is modified. Frame Relay Manager User s Guide Page 98

99 wffrrlyapp wffrrlyapp Views Err Fault Time The time at which the interface last went down. Interface DLCMI Info 2 This section of the Interface Information View displays the following information: Line Number The line number on which this frame relay interface resides. DialFailureDisable On a dial interface, this indicates whether to time out if a full status message is not received. A timeout will cause the connection to terminate. Interface Type The type of interface this is. A normal interface is not backed up, a primary interface is backed up, and a backup interface is used for backup. BackupFilter The circuit number that defines the ppq filters that the backup interface will use. If 0, the filters defined for the default/main circuit will be used. Debug Level For Bay Networks internal use only. Trace Level For Bay Networks internal use only. CongestionMethod Default congestion control method to use for all VCs on this interface. TrafficShapingInt The interval, in ticks (1/1024 of a second), that VCs are processed for traffic shaping. Frame Relay Manager User s Guide Page 99

100 wffrrlyapp wffrrlyapp Views HiQueueLimit The total number of buffers that the interface will allow VCs to queue into the Hi queue. Divided by the number of traffic shaped VCs to get the number of buffers allowed per VC. NormalQueueLimit The total number of buffers that the interface will allow VCs to queue into the Normal queue. Divided by the number of traffic shaped VCs to get the number of buffers allowed per VC. LoQueueLimit The total number of buffers that the interface will allow VCs to queue into the Lo queue. Divided by the number of traffic shaped VCs to get the number of buffers allowed per VC. XoffDelete Indicates whether to listen (enabled) or ignore (disabled) XOFF (R-bit) notification. FR Service Record View Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select FR Service Record. Frame Relay Manager User s Guide Page 100

101 wffrrlyapp Figure 34: wffrrlyapp Views Frame Relay Service Record Information View This view displays the following information: Delete Indicates that this frame relay service record should be deleted. Line Number The line number on which the associated Relay interface resides. Ckt Number The circuit number of this interface. Default Flag Identifies default service record for VCs added through the frame relay switch. Number VCs Number of virtual circuit associated with a service record. Name User name for circuit. Frame Relay Manager User s Guide Page 101

102 wffrrlyapp wffrrlyapp Views State Used to identify new service record instances. BackupCktNum The circuit number used by the backup interface to store/define the ppq filter configuration. BackupLineNum Indicates one of the backup interfaces for this primary interface. The circuit on this service record should be shared onto that backup interface. BackupLLIndex Indicates one of the backup interfaces for this primary interface. The circuit on this service record should be shared onto that backup interface. BackupMainCkt The main circuit of one of the backup interfaces for this primary interface. The circuit on this service record should be shared onto that backup interface. PrimLineNum The primary interface for this backup interface. This should be set only in the Default Service Record. PrimLLIndex The primary interface for this backup interface. This should be set only in the Default Service Record. PrimMainCkt The main circuit on the primary interface for this backup interface. This should be set only in the Default Service Record. SVCDisable Allow SVCs on this service record. Frame Relay Manager User s Guide Page 102

103 wffrrlyapp wffrrlyapp Views SVCLocNum Number associated with this service record. SVCSubAddr Subaddress of type NSAP further qualifies number. SVCLocPlan Supported Q / numbering plans. Each plan is represented by the 4 least significant bits to align with the values stated in Q.931. SVCLocTypeNum Supported Q / types of number. Each type is represented by a value of one greater than the values stated in Q.931. SVCCallBlock Allow all calls, block inbound, block outbound, block all calls. SVCCallScreening Enable SVC call screening. SVCScreeningType Type of SVC call screening. SVCInactTimer Inactivity Timer for SVCs. Zero disables timer. SVCInactMode Inactivity check mode. Virtual Circuit Table Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select Virtual Circuit Table. Frame Relay Manager User s Guide Page 103

104 wffrrlyapp Figure 35: Frame Relay Virtual Circuit Table View wffrrlyapp Views This view displays two tables: Circuit Table 1 and 2. Circuit Table 1 This section of the Virtual Circuit table displays the following information: Delete Indication to delete this frame relay interface. Line Number Instance identifier. This is the line number on which the associated Frame Relay interface resides. LL Index The Lower Layer index uniquely identifies the lower layer in cases where the lower layer may be something other than the physical layer. For Frame Relay Manager User s Guide Page 104

105 wffrrlyapp wffrrlyapp Views example, if Frame Relay is running over an ATM VC, the LLIndex identifies the ATM VC. Number The circuit number of this interface. DLCI One of three instance identifiers. This is the Frame Relay address of the virtual circuit. State The state of the particular virtual circuit. State Set User access for setting the state of a virtual circuit. Creation Time The value of sysuptime when the VC was created. Last Time change The value of sysuptime when last there was a change in VC state. Committed Burst The maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval. Excess Burst The maximum amount of uncommitted data bits that they will attempt to deliver over the measurement interval. Throughput The average number of Frame Relay Information Field bits transferred per second across a user network interface. Multicast Indicates whether this DLCI is used for multicast or single destination. Frame Relay Manager User s Guide Page 105

106 wffrrlyapp wffrrlyapp Views Type Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface. SubCircuit Circuit number to use for this VC when configured in hybrid (for bridging) or direct access (VC as a circuit) mode. Mode The mode of the given VC. The choices are: Group treats the VC as one of many VCs on a circuit; Hybrid treats the VC as one of many VCs on a circuit for protocol traffic, but as a separate circuit for bridging; Direct treats the VC as a separate circuit for all applications. Circuit Table 2 This section of the Virtual Circuit table displays the following information: Line Num Instance identifier. This is the line number on which the associated Frame Relay interface resides. DLCI One of three instance identifier. This is the Frame Relay address of the virtual circuit. Valid values are: twobyteminimum, twobytemaximum, threebyteminimum, threebytemaximum, fourbyteminimum, and fourbytemaximum. Compression Enable compression. PrimHoldTimer The maximum number of seconds that a Frame Relay PVC Primary will be kept inactive, ignoring status messages, when it is terminated because the backup has started. InactivityTimer Inactivity Time for SVCs. Zero disables timer. Frame Relay Manager User s Guide Page 106

107 wffrrlyapp wffrrlyapp Views InactivityMode Specifies which packets will reset the SVC inactivity timer. CongestionMethod The congestion method to use on this VC. HiXmits High Xmits for this VC. NormalXmit Normal Xmits for this VC. LoXmits Low Xmits for this VC. HiClippedPkt High clipped packets for this VC. NormalClippedPkts Normal clipped packets for this VC. LoClippedPkt Low clipped packets for this VC. HiQHiWaterPkts High QHighWater packets for this VC. NormalQHiWatPkts Normal QHigh Water packets for this VC. LoQHiWaterPkts Low QHigh Water packets for this VC. DroppedPkts Dropped packets for this VC. LargePkts Large packets for this VC. Frame Relay Manager User s Guide Page 107

108 wffrrlyapp wffrrlyapp Views HiTotalOctets High Total Octets for this VC. NormalTotalOctets Normal Total Octets for this VC. LoTotalOctets Low Total Octets for this VC. PktsNotQueued Packets not queued for this VC. HiWaterPktsClear High Water packets clear for this VC. HiQueueLimit High Priority queue limit for this VC. NormalQueueLimit Normal Priority Queue Limit for this VC. If set to inherit, then the VC uses part of the global allocation of buffers in the DLCMI entry. LoQueueLimit Low Priority queue limit for this VC. If set to inherit, then the VC uses part of the global allocation of buffers in the DLCMI entry. StartupDelay Number of seconds the VC should wait before creating the circuit. Packet Statistics Opens the Virtual Circuit Detail View 2. Virtual Circuit Detail View 2 Access: From the Virtual Circuit Table view, select the Packet Statistics button. Frame Relay Manager User s Guide Page 108

109 wffrrlyapp wffrrlyapp Views Figure 36: Virtual Circuit Table Detail View 2 This view provides three color-coded pie charts. Table 3 through Table 5 provide the Virtual Circuit information displayed by the pie charts. Table 3: Statistic Received Transmitted Total Packet Breakdown Definition Number of packets received. Number of packets transmitted. Frame Relay Manager User s Guide Page 109

110 wffrrlyapp wffrrlyapp Views Table 4: Statistic In FECNs In BECNs In Octets Out Octets Specific Packet Breakdown Definition Number of frames received indicating forward congestion. Number of frames received indicating backward congestion. The number of octets received from this virtual circuit. The number of octets sent from this virtual circuit. Statistic Table 5: Error Breakdown Definition In Discards Out Discards The number of inbound frames discarded because of format errors, because a VC is inactive or because the protocol was not registered for this circuit. Indicates how many outbound frames were dropped. Usually these are dropped because a VC is not active. Circuit Error Table Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select Circuit Error Table. Frame Relay Manager User s Guide Page 110

111 wffrrlyapp Figure 37: Frame Relay Circuit Table Error View wffrrlyapp Views This table displays the following information: Circuit The instance identifier. Indicates the frame relay circuit number. Drops The number of frames that were dropped at the circuit level. Generally this is because the particular protocol (within the inbound frame) was not registered for this circuit. Discards The number of frames that were discarded at the circuit level. Generally this is because the outbound frame was too long, or too short. Signalling Table Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select Signalling Table. Frame Relay Manager User s Guide Page 111

112 wffrrlyapp wffrrlyapp Views Figure 38: Frame Relay Signalling Table This table displays the following information: Delete Delete Frame Relay Signalling on this interface. Disable Disable Frame Relay Signalling on this interface. LineNumber Logical line number. LLIndex Lower Layer Index. Status Frame Relay Signalling Status. CircuitNum Circuit number of the Frame Relay Signalling Stack. Conformance Q.933 Standard Conformance Selection. Frame Relay Manager User s Guide Page 112

113 wffrrlyapp wffrrlyapp Views SVC Idle Timer SVC Idle time-out value. Number of seconds in which SVCs are not passing data before considered idle. Max SVCs Maximum number of SVC allowed on this interface. Delete Policy SVC Deletion Policy. The three choices are: Always replaces an SVC of an equal or lower priority, Idle replaces an SVC of an equal or lower priority only if it is idle, Never never replaces an SVC. Replace Policy SVC Replacement Policy. The three choices are: Always replaces an SVC of an equal or lower priority, Idle replaces an SVC of an equal or lower priority only if it is idle, Never never replaces an SVC. Max SVCs Active Maximum number of SVCs currently in active state. Lapf Table Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select Lapf Table. Frame Relay Manager User s Guide Page 113

114 wffrrlyapp wffrrlyapp Views Figure 39: Lapf Table This view displays two tables: Lapf Info 1 and 2. Lapf Info 1 This section of the Lapf table displays the following information: Delete Delete LAPF on this interface. Disable Disable LAPF on this interface. Line Number Logical Line number. Frame Relay Manager User s Guide Page 114

115 wffrrlyapp wffrrlyapp Views LL Index Lower Layer Index. Status Status of LAPF Data Link Control. Station Type Identifies the desired station type of this interface. Action Initiate This identifies the action LAPF will take to initiate link set. Lapf T200 LAPF Base timer, in tenths of a second. Lapf T203 LAPF idle timer value, in seconds. Lapf N200 Maximum number of LAPF retransmissions. Lapf N201 Maximum number of octets in LAPF Information field. Lapf K Maximum number of outstanding I-frames. RxWinSize Current receive window size. TxWinSize Current transmit window size. Lapf Info 2 This section of the Lapf table displays the following information: Line Number Logical Line number. Frame Relay Manager User s Guide Page 115

116 wffrrlyapp wffrrlyapp Views SABME Sen Number of SABME sent. SABME Rcvd Number of SABME received. UA Sent Number of UA sent. UA Rcvd Number of UA received. DISC Sent Number of DISC sent. DISC Rcvd Number of DISC received. DM Sent Number of DM sent. DM Rcvd Number of DM received. FRMR Sent Number of FRMR sent. FRMR Rcvd Number of FRMR received. RNRs Sent Number of RNR frames sent since link is up. RNRs Rcvd Number of RNR frames received since link is up. REJs Sent Number of REJ frames sent since link is up. Frame Relay Manager User s Guide Page 116

117 wffrrlyapp wffrrlyapp Views REJs Rcvd Number of REJ frames received since link is up. IFrames Sent Number of I-frames sent since last link establishment. IFrames Rcvd Number of I-frames received since last link establishment. UI Sent Number of un-numbered I-frames sent since last link establishment. UI Rcvd Number of un-numbered I-frames received since last link establishment. RRs Sent Number of RR frames sent since link is up. RRs Rcvd Number of RR frames received since link is up. XID Sent Number of XID sent. XID Rcvd Number of XID received. T200 Timeouts Number of T200 Timeouts that occurred. T203 Timeouts Number of T203 Timeouts that occurred. N200 Exceed Number of N200 being exceeded. N201 Error Number of N201 errors that occurred. Frame Relay Manager User s Guide Page 117

118 wffrrlyapp FRF4 Signalling Table wffrrlyapp Views Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select FRF4 Signalling Table. Figure 40: Frame Relay FRF4 Signalling Table This table displays the following information: Delete Delete FRF4 SVC signalling on this interface. Disable Disable FRF4 SVS signalling on this interface. Line Number Logical Line number. LL Index Lower Layer Index. Frame Relay Manager User s Guide Page 118

119 wffrrlyapp wffrrlyapp Views Max Svcs Maximum number of SVCs for this interface. Sig T303 Setup message timer value in seconds. Valid values are: min, default, and max. Sig T305 Disconnect timer value. Valid values are: min, default, and max. Sig T308 Release timer value. Valid values are: min, default, and max. Sig T310 Call proceeding timer value Q.931 specifies a default of seconds for this timer. Valid values are: min, default, and max. Sig T322 Status enquiry timer value. Valid values are: min, default, and max. Sig N322 Number of times that the status enquiry is retransmitted. Frames Sent Number of frames transmitted. Octets Sent Number of octets transmitted. Frames Rcvd Number of frames received. Octets Rcvd Number of octets received. Frames Dropped Number of frames dropped. Frame Relay Manager User s Guide Page 119

120 wffrrlyapp wffrrlyapp Views Frames Discard Number of frames discarded. SVC Signalling Options Table Opens the FRF4 SVC Signalling Table. Active Call Table Opens the Active Call Table. FRF4 SVC Signalling Table Access: From the FRF4 Signalling Table, select the SVC Signalling Options Table button. Frame Relay Manager User s Guide Page 120

121 wffrrlyapp wffrrlyapp Views Figure 41: FRF4 SVC Signalling Table This view displays two tables: SVC Options Table 1 and 2. SVC Options Table 1 This section of the FRF4 SVC Signalling table displays the following information: Delete Delete SVC options record. Disable Disable use of SVC options record. Line Num Logical line number. Frame Relay Manager User s Guide Page 121

122 wffrrlyapp wffrrlyapp Views LL Index Lower Layer Index. Circuit Num Circuit number. Instance Index Instance index assigned by Site Manager. Rem Num Configured options apply to this number. Rem SubAddr Subaddress of type NSAP (Q.931) further qualifies number. Rem Plan Supported Q / numbering plans. Each plan is represented by the 4 least significant bits to align with the values stated in Q.931. Rem TypeNum Supported Q / types of number. Each type is represented by a value one greater than the values stated in Q.931. Bcast Disable Add this number to the SVC broadcast domain. Inact Timer Amount of time (in seconds) to wait for packets before disconnecting the SVC. Inact Mode Inactivity check mode. Wcp Enable Enable compression. User Name User name for the SVC options. Frame Relay Manager User s Guide Page 122

123 wffrrlyapp wffrrlyapp Views SVC Options Table 2 This section of the FRF4 SVC Signalling table displays the following information: Circuit Num Circuit number. X213DataLQAPriority The lowest quality acceptable (LQA) priority of data on the network connection as defined in Q.933 and X.213. Each priority is the numerical value associated with said priority in Q.933. X213GainPriority The priority to gain a network connection as defined in Q.933 and X.213. Each priority is the numerical value associated with said priority in Q.933. X213GainLQAPriority The lowest quality acceptable (LQA) priority to gain a network connection as defined in Q.933 and X.213. Each priority is the numerical value associated with said priority in Q.933. X213KeepPriority The priority to keep a network connection as defined in Q.933 and X.213. Each priority is the numerical value associated with said priority in Q.933. X213KeepLQAPriority The lowest quality acceptable (LQA) priority to keep a network connection as defined in Q.933 and X.213. Each priority is the numerical value associated with said priority in Q.933. LLCoreOut Requested outgoing throughput. Throughput is the average number of frame mode information field bits transferred per second across a usernetwork interface in one direction, measured over an interval of duration T. Frame Relay Manager User s Guide Page 123

124 wffrrlyapp wffrrlyapp Views LLCoreIn Requested incoming throughput. Throughput is the average number of frame mode information field bits transferred per second across a usernetwork interface in one direction, measured over an interval of duration T. LLCoreMinOut Minimum acceptable outgoing throughput. Throughput is the average number of frame mode information field bits transferred per second across a user-network interface in one direction, measured over an interval of duration T. LLCoreMinIn Minimum acceptable incoming throughput. Throughput is the average number of frame mode information field bits transferred per second across a user-network interface in one direction, measured over an interval of duration T. LLCoreOutBc Outgoing committed burst size in bytes. Committed burst is the maximum amount of data (in bits) that the network agrees to transfer, under normal conditions, over a measurement interval T. LLCoreInBc Incoming committed burst size in bytes. Committed burst is the maximum amount of data (in bits) that the network agrees to transfer, under normal conditions, over a measurement interval T. LLCoreOutBe Outgoing excess burst size in bytes. Excess burst is the maximum amount of uncommitted data (in bits) that the network will attempt to deliver over a measurement interval T. LLCoreInBe Incoming excess burst size in bytes. Excess burst is the maximum amount of uncommitted date (in bits) that the network will attempt to deliver over a measurement interval T. Frame Relay Manager User s Guide Page 124

125 wffrrlyapp wffrrlyapp Views CongestDisable This indicates whether the congestion algorithm should be used for this VC. If this is not set, the value is inherited from the DLCMI record. CongestTimer The time period over which congestion notifications are counted. It is also the period during which the VC will cease sending information before resuming transmission if no congestion notifications are received. CongestCtr The number of congestion notifications, when received within Congestion Timer time, that will result in the VC ceasing transmissions. CongestMethod Action when VC congestion occurs. TrafficShaping Enable VC traffic shaping. Active Call Table Access: From the FRF4 Signalling Table, select the Active Call Table button. Frame Relay Manager User s Guide Page 125

126 wffrrlyapp wffrrlyapp Views Figure 42: FRF4 Active Call Table This view displays two tables: Active Call Table 1 and 2. Active Call Table 1 This section of the Active Call table displays the following information: Delete Delete SVC active call record. Line Num Logical Line number. LL Index Lower Layer Index. DLCI DLCI number. Frame Relay Manager User s Guide Page 126

127 wffrrlyapp wffrrlyapp Views Direction Direction of call relative to router. Circuit Num Circuit number associated with this call. Called Num Number from called party number information element. Called SubAddr Subaddress from called party subaddress information element. Called Plan Numbering plan from called party number. Called TypeNum Type of number from called party number information element. Calling Num Number from calling party number information element. Calling SubAddr Subaddress from calling party subaddress information element. Calling Plan Numbering plan from calling party number information element. Calling TypeNum Type of number from calling party number information element. Connect Time Time connect message was sent or received. Active Call Table 2 This section of the Active Call table displays the following information: Circuit Num Circuit number associated with this call. Frame Relay Manager User s Guide Page 127

128 wffrrlyapp wffrrlyapp Views X213DataPriority The priority of data on the network connection, from the X.213 information element. X213DataLQAPriority The lowest quality acceptable (LQA) priority of data on the network connection, from the X.213 information element. X213GainPriority The priority to gain a network connection, from the X.213 information element. X213GainLQAPriority The lowest quality acceptable (LQA) priority to gain a network connection, from the X.213 information element. X213KeepPriority The priority to keep a network connection, from the X.213 information element. X213KeepLQAPriority The lowest quality acceptable (LQA) priority to keep a network connection, from the X.213 information element. LLCoreOut Requested outgoing throughput, from the link layer core information element. LLCoreIn Requested incoming throughput, from the link layer core information element. LLCoreMinOut Minimum acceptable outgoing throughput, from the link layer core information element. Frame Relay Manager User s Guide Page 128

129 wffrrlyapp wffrrlyapp Views LLCoreMinIn Minimum acceptable incoming throughput, from the link layer core information element. LLCoreOutBc Outgoing committed burst size in bytes, from the link layer core information element. LLCoreInBc Incoming committed burst size in bytes, from the link layer core information element. LLCoreOutBe Outgoing excess burst size in bytes, from the link layer core information element. LLCoreInBe Incoming excess burst size in bytes, from the link layer core information element. PVC Passthru Interface Table Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select PVC Passthru Interface Table. Frame Relay Manager User s Guide Page 129

130 wffrrlyapp Figure 43: wffrrlyapp Views Frame Relay PVC PassThru Interface Table The PVC Passthru interface table contains the list of interface circuits. There will be one entry for each direct mode PVC configured for PVC Passthru. Intf Circuit The DP circuit on which this interface resides. This attribute is the first component of the Instance ID for this field. Intf Delete The create/delete indicator for the PVC Passthru Interface entry. The default value is created. Intf Disable The enable/disable indicator for the PVC Passthru Interface entry. The default value is enabled. Intf Discards The number of inbound frames discarded, either because this passthru interface is disabled or it has no partner. Frame Relay Manager User s Guide Page 130

131 wffrrlyapp wffrrlyapp Views Intf Dlci The Dlci associated with this circuit. This attribute is the second component of the Instance ID for this field. Intf Drops The number of outbound frames dropped, because this passthru interface is disabled or inactive. Rx Frames The number of frames received on this interface. Intf State Interface state indicator. The state is active if the circuit is up. Valid values are: active, inactive, invalid and nonpresent. Tx Frames The number of frames transmitted on this interface. PVC Passthru Mapping Table Access: From the Icon Subviews menu for the wffrrlyapp Application icon, select PVC Passthru Mapping Table. Frame Relay Manager User s Guide Page 131

132 wffrrlyapp Figure 44: wffrrlyapp Views Frame Relay PVC PassThru Mapping Table The PVC Passthru mapping table contains the static routes between PVCs. It displays the following information: Mapping Circuit A The first circuit (i.e., hybrid mode PVC) for this mapping. All data received on this circuit is delivered to circuit B. This attribute is the 1st of 2 components of the Instance ID for this field. Mapping Circuit B The second circuit (i.e., hybrid mode PVC) for this mapping. All data received on this circuit is delivered to circuit A. This attribute is the 2nd of 2 components of the Instance ID for this field. Mapping Delete The create/delete indicator for the PVC Passthru Mapping entry. The default value is created. Mapping Disable The enable/disable indicator for the PVC Passthru Mapping entry. The default value is enabled. Frame Relay Manager User s Guide Page 132

133 wffrrlyapp wffrrlyapp Views Mapping Dlci A The Dlci associated with circuit A. Mapping Dlci B The Dlci associated with circuit B. Mapping State Mapping state indicator. The state is active if both circuits are up, inactive if one or both are down. The state is invalid if this mapping conflicts with another, or is misconfigured. Valid values are: active, inactive, invalid and nonpresent. Frame Relay 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. Access: From the Icon Subviews menu for the wffrrly icon, select DLCI Connection. Frame Relay Manager User s Guide Page 133

134 wffrrlyapp wffrrlyapp Views Figure 45: DCLI Connection View Local IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface. Example:The number 2.26 would mean the ifindex is 2 and the DLCI is 26. Local IP Address The IP address associated with a specific DLCI. Remote Device The model name of the remote device that a specific DLCI is connected to. Remote IF.DLCI This shows the number of the interface and the number of the DLCI associated with that interface on the remote device. Frame Relay Manager User s Guide Page 134