FrameSaver SLV 9664 USER’S GUIDE Document No.
Copyright E 2000 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Ave. N.
Contents About This Guide H Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii H Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii H Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix H Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3 Configuration H Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Configuration Option Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Accessing and Displaying Configuration Options . . . . . . . . . . . . . . . . 3-5 Changing Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Saving Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4 Security and Logins H Limiting Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 H Controlling Asynchronous Terminal Access . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 H Controlling External COM Port Device Access . . . . . . . . . . . . . . . . . . . . . . 4-4 H Controlling Telnet or FTP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Limiting Telnet Access . . . . . . . . . . . . . . . . . . .
Contents 6 Troubleshooting H Problem Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 H Resetting the Unit and Restoring Communication . . . . . . . . . . . . . . . . . . . 6-3 Resetting the Unit from the Control Menu . . . . . . . . . . . . . . . . . . . . . . . 6-3 Resetting the Unit By Cycling the Power . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Restoring Communication with a Misconfigured Unit . . . . . . . . . . . . .
Contents 8 Setting Up NetScout Manager Plus for FrameSaver Devices H Before Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 H Configuring NetScout Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Adding FrameSaver SLV Units to the NetScout Manager Plus Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Verifying Domains and Groups . . . . . . . . . . . . . . . . .
Contents B SNMP MIBs and Traps, and RMON Alarm Defaults H MIB Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H Downloading MIBs and SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H System Group (mib-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FrameSaver Unit’s sysDescr (system 1) . . . . . . . . . . . . . . . . . . . . . . . . FrameSaver Unit’s sysObjectID (system 2) . . .
About This Guide Purpose and Intended Audience This document contains information needed to properly set up, configure, and verify operation of FrameSaver SLV 9664 units with Service Level Verifier (SLV) functionality designed for ISDN leased line applications. The unit is intended for use at sites where access is at either 64 kbps or 128 kbps. This guide is intended for system designers, engineers, administrators, and operators.
About This Guide Section Description Chapter 7 Setting Up OpenLane for FrameSaver Devices. Identifies where installation and setup information is located and how FrameSaver units are supported. Chapter 8 Setting Up NetScout Manager Plus for FrameSaver Devices. Describes setup of the NetScout Manager Plus application so it supports FrameSaver units. Chapter 9 Setting Up Network Health for FrameSaver Devices.
About This Guide Product-Related Documents Document Number Document Title Paradyne FrameSaver Documentation: 9664-A2-GL10 FrameSaver SLV 9664 Quick Reference 9664-A2-GN10 FrameSaver SLV 9664 Installation Instructions Paradyne OpenLane NMS Documentation: 7800-A2-GZ41 OpenLane 5.x Service Level Management for UNIX Quick Start Installation Instructions 7800-A2-GZ42 OpenLane 5.
About This Guide Conventions Used Convention Used When Used Menu selection sequence To provide an abbreviated method for indicating the selections to be made from a menu or selections from within a menu before performing a procedural step. For example, Main Menu → Status → System and Test Status indicates that you should select Status from the Main Menu, then select System and Test Status. x ( Path:) To provide a check point that coincides with the menu path shown at the top of the screen.
About the FrameSaver SLV 9664 1 This chapter includes the following: H SLM Overview H FrameSaver SLV 9664 Features SLM Overview The Service Level Management (SLM) Solution consists of: H FrameSaverr SLV units H OpenLaner SLM system H NetScout Manager Plus application H Standalone NetScout Probes, if needed This solution provides increased manageability, monitoring, and diagnostics so customers can identify problems more efficiently, troubleshoot those problems faster, and maximize their network
About the FrameSaver SLV 9664 FrameSaver SLV 9664 Features The FrameSaver SLV unit provides the following features: H Intelligent Service Level Verification. Provides accurate throughput, latency, and availability measurements to determine network performance and whether service level agreements (SLAs) are being met, along with SLA reporting. SLA parameter thresholds can be configured to provide proactive notification of a developing network problem. H Security.
About the FrameSaver SLV 9664 H RMON-Based User History Statistics Gathering. Provides everything needed to monitor network service levels, plus throughput with accurate data delivery, network latency, and LMI and PVC availability. In addition, port bursting statistics are kept for all frame relay links. These statistics are available real-time via the Enterprise MIB and historically as an RMON2 User History object.
About the FrameSaver SLV 9664 H ATM VPI/VCI and DLCI Correlation. For networks with both ATM and frame relay-access endpoints, allows the FrameSaver unit to report the originating Virtual Path or Channel Identifier (VPI/VCI) in the far-end ATM-access endpoint where the local DLCI is mapped so they can be correlated for OpenLane SLV reports. H Back-to-Back Operation. Allows two FrameSaver devices to be connected via a leased-line network or simulation so a point-to-point configuration can be implemented.
About the FrameSaver SLV 9664 — Firmware downloading provides an easy-to-use tool for downloading to an entire network or a portion of the network. — On-demand polling of FrameSaver devices, and SNMP polling and reporting are available. H NetScout Manager Plus and NetScout Probe Support. Provides complete LAN and WAN traffic analysis and monitoring functions for FrameSaver SLV devices.
About the FrameSaver SLV 9664 This page intentionally left blank.
User Interface and Basic Operation 2 This chapter tells you how to access, use, and navigate the menu-driven user interface. It includes the following: H Logging On H Main Menu H Screen Work Areas H Navigating the Screens — Keyboard Keys — Function Keys — Selecting from a Menu — Switching Between Screen Areas — Selecting a Field — Entering Information What appears on the screens depends on: 9664-A2-GB20-00 H Current configuration – How your network is currently configured.
User Interface and Basic Operation Logging On Start a session using one of the following methods: H Telnet session via: — An in-band management channel through the frame relay network. — A local in-band management channel configured on the DTE port between the FrameSaver unit and the router. H Direct terminal connection over the COM port. When logging on, the User Interface Idle screen appears. H If no security was set up or security was disabled, the Main Menu screen appears (see page 2-4).
User Interface and Basic Operation If two sessions are already active, wait and try again. H If attempting to access the unit through Telnet, the local Telnet client process returns a Connection refused: message at the bottom of the screen. H If attempting to access the unit over the COM port, not via Telnet, the User Interface Already In Use screen is redisplayed.
User Interface and Basic Operation Main Menu Entry to all of the FrameSaver unit’s tasks begins at the Main Menu, which has five menus or branches. The Access Level at the top of the screen only appears when security has been set up.
User Interface and Basic Operation Screen Work Areas There are two user work areas: H Screen area – Where you input information into fields. H Function keys area – Where you perform specific screen functions. Below is a sample configuration screen.
User Interface and Basic Operation Navigating the Screens You can navigate the screens by: H Using keyboard keys. H Switching between the two screen work areas using function keys. Keyboard Keys Use the following keyboard keys to navigate within the screen area: 2-6 Press . . . To . . . Ctrl-a Move cursor between the screen area and the screen function keys area. Esc Return to the previous screen. Right Arrow (on same screen row), or Tab (on any screen row) Move cursor to the next field.
User Interface and Basic Operation Function Keys All function keys (located in the lower part of the screen; see the example on page 2-5) operate the same way throughout the screens. They are not case-sensitive, so upper- or lowercase letters can be used interchangeably. These keys use the following conventions: Select . . . For the screen And press Enter to . . . function . . . M or m MainMenu Return to the Main Menu screen. E or e Exit Terminate the asynchronous terminal session.
User Interface and Basic Operation Selecting from a Menu " Procedure To select from a menu: 1. Tab or press the down arrow key to position the cursor on a menu selection, or press the up arrow key to move the cursor to the bottom of the menu list. Each menu selection is highlighted as you press the key to move the cursor from position to position. 2. Press Enter. The selected menu or screen appears. " Procedure To return to a previous screen, press the Escape (Esc) key until you reach the desired screen.
User Interface and Basic Operation Selecting a Field Once you reach the desired menu or screen, select a field to view or change, or issue a command. Press the Tab or right arrow key to move the cursor from one field to another. The current setting or value appears to the right of the field. Entering Information You can enter information in one of three ways. Select the field, then: H Manually type in (enter) the field value or command.
User Interface and Basic Operation This page intentionally left blank.
Configuration 3 This chapter includes the following: H Basic Configuration — Configuration Option Areas — Accessing and Displaying Configuration Options — Changing Configuration Options — Saving Configuration Options — Minimal Configuration Before Deploying Remote Units H Entering System Information and Setting the System Clock H Setting Up for Trap Dial-Out — Setting Up Call Directories for Trap Dial-Out H Setting Up Auto-Configuration — Selecting a Frame Relay Discovery Mode — Automatically Removi
Configuration H Configuring the Overall System — Configuring Frame Relay and LMI for the System — Configuring Service Level Verification Options — Configuring General System Options H Configuring the Physical Interfaces — Configuring the User Data Port H Configuring Frame Relay for an Interface H Manually Configuring DLCI Records H Configuring PVC Connections H Setting Up Management and Communication Options — Configuring Node IP Information — Configuring Management PVCs — Configuring General SN
Configuration Basic Configuration Configuration option settings determine how the FrameSaver unit operates. Use the FrameSaver unit’s Configuration Edit/Display menu to display or change configuration option settings.
Configuration Configuration Option Areas The FrameSaver unit arrives with configured factory default settings, which are located in the Factory Default Configuration option area. You can find the default settings for configuration options in the: H FrameSaver SLV 9664 Quick Reference H Configuration Option Tables If the factory default settings do not support your network’s configuration, you can customize the configuration options to better suit your application.
Configuration Accessing and Displaying Configuration Options To access and display configuration options, load (copy) the applicable configuration option set into the edit area. " Procedure To load a set of configuration options for editing: 1. From the Main Menu, press the down arrow key so the cursor is on Configuration. 2. Press Enter to display the Configuration menu. The Load Configuration From: menu appears.
Configuration Changing Configuration Options " Procedure To change configuration option settings: 1. From the Configuration Edit/Display menu, select a set of configuration options and press Enter. For example: Configuration → PVC Connections 2. Select the configuration options that are applicable to your network, and make appropriate changes to the setting(s). See Chapter 2, User Interface and Basic Operation, for additional information.
Configuration Saving Configuration Options When changes to the configuration options are complete, use the Save function key to save your changes to either the Current, Customer 1, or Customer 2 configuration areas. NOTE: When changing settings, you must Save for changes to take effect. " Procedure To save the configuration option changes: 1. Press Ctrl-a to switch to the function key area at the bottom of the screen. 2. Type s or S to select the Save function and press Enter.
Configuration Minimal Configuration Before Deploying Remote Units At a minimum, the following configuration options must be set before deploying a a FrameSaver unit to a remote site: H Node IP Address H Node Subnet Mask See Table 3-9, Node IP Options, for a description of these options. Entering System Information and Setting the System Clock Select System Information to set up or display the general SNMP name for the unit, its location, and a contact for the unit, as well as to set the system clock.
Configuration Setting Up for Trap Dial-Out An external modem can be attached to the COM port for dialing out when an SNMP trap is generated. To set up an external modem, you need to: 1. Set up SNMP trap managers. 2. Set up an external modem. 3. Set up Modem Directory phone numbers. 4. Configure trap dial-out. See Configuring SNMP NMS Security Options to set up SNMP trap managers. See Setting Up Call Directories for Trap Dial-Out when trap dial-out is desired.
Configuration Setting Up Auto-Configuration The auto-configuration feature allows you to select a method of automatic configuration and connection of DLCIs within the FrameSaver unit, as well as to automatically remove DLCIs and connections that are no longer supported by the network service provider. Auto-configuration also maintains associated DLCI option settings when Standard LMI is used on the network interface.
Configuration Selecting a Frame Relay Discovery Mode When a Frame Relay Discovery Mode is active, the FrameSaver unit “discovers” network DLCIs from the network LMI status response message. It configures a network DLCI, a user data port DLCI, and automatically connects them to create a PVC.
Configuration NOTE: If 1MPort (the default) is not the setting required for your application, change the Frame Relay Discovery Mode before connecting the network cable or editing discovered option settings. Otherwise, the FrameSaver unit will start “discovering” DLCIs as soon as it powers up. To recover from this problem, edit a selected “discovered” DLCI or PVC connection manually if any DLCIs or PVC Connections have been configured manually.
Configuration When a Frame Relay Discovery Mode is changed and saved, the Saving will cause Auto-Configuration to update and Restart. Are you sure? prompt appears. No is the default for this prompt. H If Yes (y) is entered, the Delete All DLCIs and PVC Connections? prompt appears. No is the default for this prompt.
Configuration Setting Up Management FrameSaver units are already set up for SNMP management, with Community Name 1 set to Public and Name 1 Access set to Read/Write. For remote sites, other than the IP Address, this is all that is required. Configuration → Management and Communication → General SNMP Management See Table 3-11, General SNMP Management, for configuration information.
Configuration Setting Up So the Router Can Receive RIP Using the system’s standard Routing Information Protocol (RIP) feature, routing information is passed to the router over the management PVC, so the router can learn routes to FrameSaver SLV devices. Node IP information should be set up (see Configuring Node IP Information). " Procedure 1. Configure the router to receive RIP. For example, if using a Cisco router, configure config-t, router RIP, int serialx, IP RIP Receive version 1, then ctl-z WR. 2.
Configuration 5. Select the Delete EDLCI Connections and Make a Mgmt Only PVC option. PVC connections for the selected DLCI are broken, the Port-1 DLCI mapped to this network DLCI and the embedded management DLCI (EDLCI) are deleted, and the selected DLCI will be reconfigured as a management PVC using the Node IP Address. See Table 3-7, DLCI Record Options, for configuration information.
Configuration Configuration Option Tables Configuration option descriptions contained in this chapter are in menu order, even though this may not be the order in which you access each when configuring the unit. The following configuration option tables are included: H Table 3-1. System Frame Relay and LMI Options H Table 3-2. Service Level Verification Options H Table 3-3. General System Options H Table 3-4. Network Physical Interface Options H Table 3-5.
Configuration Configuring Frame Relay and LMI for the System Select Frame Relay and LMI from the System menu to display or change the Frame Relay and LMI options for the entire system (see Table 3-1). Main Menu → Configuration → System → Frame Relay and LMI See Configuring Frame Relay for an Interface to set an interface’s frame relay options. Table 3-1.
Configuration Table 3-1. System Frame Relay and LMI Options (2 of 2) LMI Clearing Event (N3) Possible Settings: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Default Setting: 1 Configures the LMI-defined N3 parameter, which sets the number of error-free messages that must be received before clearing an error event. Applies to both the user and network sides of a UNI. 1 – 10 – Specifies how many error-free messages it will take to clear the error event. LMI Status Enquiry (N1) Possible Settings: 1, 2, 3, 4, . . .
Configuration Configuring Service Level Verification Options SLV options are selected from the System menu (see Table 3-2). Main Menu → Configuration → System → Service Level Verification Table 3-2. Service Level Verification Options (1 of 2) SLV Sample Interval (secs) Possible Settings: 10 – 3600 Default Setting: 60 Sets the inband communications interval between FrameSaver SLV devices.
Configuration Table 3-2. Service Level Verification Options (2 of 2) SLV Timeout Clearing Event Threshold Available Settings: 1, 2, 3, 4 . . . 20 Default Setting: 1 Specifies the number of consecutive SLV messages that must be received before the DLCI Inactive status is cleared. 1 – 20 – Sets the limit for the clearing event. SLV Packet Size (bytes) Available Settings: 64 – 2048 Default Setting: 64 Sets the size of packets, in bytes, that will be used for SLV communications.
Configuration Configuring General System Options Select General from the System menu to configure the general system configuration options (see Table 3-3). Main Menu → Configuration → System → General Table 3-3. General System Options Test Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether or not loopback and pattern tests have a duration after which they are terminated automatically. Enable – All Loopback and Pattern tests have a timeout.
Configuration Configuring the Physical Interfaces Characteristics for the following physical interfaces can be configured: H Network Interface H User Data Port Configuring the Network Interface Select Physical to display or change the physical configuration options for the port being used as the network interface (see Table 3-4). Main Menu → Configuration → Network → Physical Table 3-4. Network Physical Interface Options Network Initiated DCLB Possible Settings: Disable, V.54 Default Setting: V.
Configuration Configuring the User Data Port Select Physical to display or change the physical characteristics of the user data port connected to the DTE (see Table 3-5). Main Menu → Configuration → Data Ports → Physical Table 3-5. User Data Port Physical Interface Options (1 of 2) Port Type Possible Settings: E530, V.35, X.21 Default Setting: V.35 Selects the type of port to be used for the user data port. E530 – The port is an EIA-530A-compatible DCE.
Configuration Table 3-5. User Data Port Physical Interface Options (2 of 2) Monitor DTR Possible Settings: Enable, Disable Default Setting: Enable Specifies whether the state of the DTE Ready (DTR) circuit on the user data port will be used to determine when valid data communication is possible with the DTE. When the DTR off condition is detected, an alarm is generated, LMI is declared down, and no further transfer of frame relay data can occur on this interface.
Configuration Configuring Frame Relay for an Interface Select Frame Relay from the interface’s menu to display or change the Frame Relay options for an individual interface (see Table 3-6). Main Menu → Configuration → [Network/Data Ports] → Frame Relay See Configuring Frame Relay and LMI for the System for additional information. Table 3-6.
Configuration Table 3-6. Interface Frame Relay Options (2 of 3) LMI Parameters Possible Settings: System, Custom Default Setting: System Allows you to use the system LMI options, or to set specific LMI options for this interface. System – Use system LMI options (see Table 3-1, System Frame Relay and LMI Options). Custom – Use the following options in this table to configure LMI parameters.
Configuration Table 3-6. Interface Frame Relay Options (3 of 3) LMI Inbound Heartbeat (T2) Possible Settings: 5, 10, 15, 20, 25, 30 Default Setting: 15 Configures the LMI-defined T2 parameter, which sets the number of seconds between the receipt of status enquiry messages on the network side of the LMI. Applies to the network side of a UNI only. 5 – 30 – Specifies the number of seconds between the receipt of status enquiry messages in increments of 5.
Configuration Table 3-7. DLCI Record Options (2 of 3) DLCI Type Possible Settings: Standard, Multiplexed Default Setting: For user data port DLCIs: Standard For network interface DLCIs: Multiplexed Specifies whether the DLCI is standard or multiplexed. This field is read-only when the selected DLCI is used in a PVC or Management link connection and the DLCI Type is Standard.
Configuration Table 3-7. DLCI Record Options (3 of 3) Bc Possible Settings: 0 – 128000 Default Setting: 64000 Allows you to display or change the DLCI’s committed burst size, in bits. Display Conditions – This option only appears when Committed Burst Size is set to Other. 0 – maximum burst size – Specifies the maximum amount of data that the network has agreed to deliver within the committed rate measurement interval (Tc).
Configuration Configuring PVC Connections The Auto-Configuration feature automatically configures PVC Connections and their DLCI Records. PVC Connections can also be created manually (see Table 3-8). Main Menu → Configuration → PVC Connections From this screen, you can go directly to the Management PVC screen by selecting the MgmtPVCs function key for easy movement between screens.
Configuration Table 3-8. PVC Connection Options (2 of 2) Primary Destination Link Possible Settings: Net1-FR1 Default Setting: Initially blank; no default. Specifies the frame relay interface used as the primary destination link; the to end of a from-to link. The only valid settings for this configuration option are frame relay interfaces that have at least one DLCI or EDLCI defined which are not part of a PVC connection or management link.
Configuration Setting Up Management and Communication Options The following options can be selected from the Management and Communication menu: H Node IP Options H Management PVC Options H General SNMP Management Options H Telnet and FTP Sessions Options H SNMP NMS Security Options H SNMP Traps and Trap Dial-Out Options H Communication Port Options H External Modem (COM Port) Options Configuring Node IP Information Select Node IP to display, add, or change the information necessary to suppo
Configuration Table 3-9. Node IP Options (1 of 2) Node IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address needed to access the node. Since an IP address is not bound to a particular port, it can be used for remote access via a management PVC. 001.000.000.000 – 223.255.255.255 – Shows the IP address for the node, which can be viewed or edited. Clear – Fills the node IP address with zeros.
Configuration Table 3-9. Node IP Options (2 of 2) TS Management Link Available Settings: None, PVCname Default Setting: None Specifies a troubleshooting management link for the special needs of network service providers. If the option is changed from the management PVC name to None, the Delete the Management PVC PVCname and the associated DLCI Record? prompt appears. If you select: H No – The link designation is removed and the option is set to None.
Configuration Configuring Management PVCs Select Management PVCs to define inband management links by adding or changing Management PVCs (see Table 3-10). First, DLCI records must have been configured for the interface where the Management PVC will reside. See Manually Configuring DLCI Records for additional information. Main Menu → Configuration → Management and Communication → Management PVCs Select New or M o dify to add or change Management PVCs.
Configuration Table 3-10. Management PVC Options (2 of 3) Intf Subnet Mask Possible Settings: Node-Subnet-Mask, Calculate, Special (nnn.nnn.nnn.nnn) Default Setting: Node-Subnet-Mask Specifies the subnet mask needed to access the unit when the management PVC is providing connectivity to an external IP network (through frame relay) that requires a specific subnet mask for the interface.
Configuration Table 3-10. Management PVC Options (3 of 3) Primary DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the DLCI number used for the management PVC after the frame relay interface is selected. The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be part of a PVC connection or already assigned as a management PVC. For multiplexed DLCIs, at least one EDLCI must be unconfigured for the DLCI.
Configuration Configuring General SNMP Management Select General SNMP Management to add, change, or delete the information needed to allow the FrameSaver unit to be managed as an SNMP agent by the NMS supporting the SNMP protocols (see Table 3-11). Main Menu → Configuration → Management and Communication → General SNMP Management Table 3-11.
Configuration Configuring Telnet and/or FTP Session Support Telnet and FTP options control whether a Telnet or FTP (File Transport Protocol) session is allowed through an interconnected IP network and the access security applicable to the session. Two Telnet sessions can be active at a time (see Table 3-12).
Configuration Table 3-12. Telnet and FTP Session Options (2 of 3) Session Access Level Possible Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies the highest security level allowed when accessing the menu-driven user interface via a Telnet session. If a login is required for the session, the effective access level is also determined by the user’s access level. When a login is not required, the effective access level is determined by this option.
Configuration Table 3-12. Telnet and FTP Session Options (3 of 3) FTP Login Required Possible Settings: Enable, Disable Default Setting: Disable Specifies whether a login ID and password are required for an FTP session. If required, the login used is the same login used for a menu-driven user interface session. This option does not affect the TS Management Link. Enable – User is prompted for a login ID and password. Disable – No login is required for an FTP session.
Configuration Configuring SNMP NMS Security Options Select SNMP NMS Security from the Management and Communication menu to display, add, or change SNMP security configuration options for the FrameSaver unit to set up trap managers (see Table 3-13). Main Menu → Configuration → Management and Communication → SNMP NMS Security A table is displayed consisting of the network management systems identified by IP address that are allowed to access the FrameSaver unit by SNMP. Table 3-13.
Configuration Configuring SNMP Traps and Trap Dial-Out Select SNMP Traps from the Management and Communication menu to configure SNMP traps and dial-out when a trap is generated (see Table 3-14). Main Menu → Configuration → Management and Communication → SNMP Traps See Appendix B, SNMP MIBs and Traps, and RMON Alarm Defaults, for trap format standards and special trap features, including RMON-specific traps, and the default settings that will generate RMON-specific SNMP traps. Table 3-14.
Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (2 of 5) Initial Route Destination Possible Settings: AutoRoute, COM, PVCname Default Setting: AutoRoute Specifies the initial route used to reach the specified Trap Manager. When proprietary RIP is active, only one unit in the network needs to specify an interface or management link as the initial destination. All other units can use the default setting.
Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (3 of 5) Link Traps Possible Settings: Disable, Up, Down, Both Default Setting: Both Determines whether SNMP linkDown or linkUp traps are sent to the currently configured trap manager(s). A linkDown trap indicates that the unit recognizes a failure in one of the interfaces. A linkUp trap indicates that the unit recognizes that one of its interfaces is active.
Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (4 of 5) Trap Dial-Out Possible Settings: Enable, Disable Default Setting: Disable Controls whether SNMP trap messages initiate a call automatically. If the call cannot be completed and the Call Retry option is set to Enable, the SNMP trap message is held (queued) until the call completes to either the Alarm or alternate directory.
Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (5 of 5) Alternate Dial-Out Directory Possible Settings: None, 1 – 5 Default Setting: None Specifies whether an incomplete call (busy, or no answer, etc.) resulting from an attempt to send an SNMP trap message is retried using an alternate telephone number. Up to 5 alternate call directories can be set up, but only one at a time can be used. When Call Retry is enabled, the alarm directory’s telephone number is called first.
Configuration Configuring the Communication Port Select Communication Port from the Management and Communication menu to display or change the communication port configuration options (see Table 3-15). Main Menu → Configuration → Management and Communication → Communication Port Table 3-15. Communication Port Options (1 of 4) Port Use Possible Settings: Terminal, Net Link Default Setting: Terminal Assigns a specific use to the COM port.
Configuration Table 3-15. Communication Port Options (2 of 4) Stop Bits Possible Settings: 1, 2 Default Setting: 1 Determines the number of stop bits used for the COM port. 1 – Provides one stop bit. 2 – Provides two stop bits. Ignore Control Leads Possible Settings: Disable, DTR Default Setting: Disable Specifies whether DTR is used. Disable – Treats control leads as standard operation. DTR – Ignores DTR. This may be necessary when connecting to some PAD devices.
Configuration Table 3-15. Communication Port Options (3 of 4) Inactivity Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether a user session is disconnected after a specified time of inactivity (no keyboard activity). Display Conditions – This option only appears when Port Use is set to Terminal. Enable – Disconnects user session after the specified time of inactivity. Disable – Does not disconnect user session.
Configuration Table 3-15. Communication Port Options (4 of 4) Link Protocol Possible Settings: PPP, SLIP Default Setting: PPP Specifies the link-layer protocol to be used. Only in effect when the COM port is configured as a network communication link (Port Use option is set to Net Link). Display Conditions – This option only appears when Port Use is set to Net Link. PPP – Point-to-Point Protocol. SLIP – Serial-Line Internet Protocol.
Configuration Configuring the COM Port to Support an External Modem Select External Modem (Com Port) to display or change the configuration options that control call processing for an external device attached to the COM port (see Table 3-16). Main Menu → Configuration → Management and Communication → External Modem (Com Port) NOTE: A standard EIA-232 crossover cable is required when connecting an external modem to the FrameSaver unit’s COM Port.
Configuration Table 3-16. External Modem (COM Port) Options (2 of 2) Alternate IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the Alternate IP Address for the COM port when the alternate phone directory is used. If this configuration option is not configured (i.e., it is zero), the COM port’s primary IP Address is used when the alternate telephone directory is used.
Security and Logins 4 This chapter includes the following: H Limiting Access H Controlling Asynchronous Terminal Access H Controlling External Device COM Port Device Access H Controlling Telnet or FTP Access — Limiting Telnet Access — Limiting FTP Access — Limiting Telnet or FTP Access Over the TS Management Link H Controlling SNMP Access — Disabling SNMP Access — Assigning SNMP Community Names and Access Levels — Limiting SNMP Access Through IP Addresses 9664-A2-GB20-00 H Creating a Login H
Security and Logins Limiting Access The FrameSaver unit provides access security on the following interfaces: H Asynchronous (async) terminal H Telnet H FTP H SNMP Up to two direct or Telnet sessions can be active at any given time; that is, you can have two simultaneous Telnet sessions, or one Telnet session and one active asynchronous terminal session, or two simultaneous asynchronous terminal sessions.
Security and Logins " Procedure To limit asynchronous terminal access to the menu-driven user interface: 1. Select the Communication Port options. Main Menu → Configuration → Management and Communication → Communication Port 2. Set the following configuration options, as appropriate. To . . . Set the configuration option . . . Require a login Login Required to Enable. NOTE: User ID and password combinations must be defined. See Creating a Login.
Security and Logins Controlling External COM Port Device Access Dial-in access can be controlled when an external device (modem) is connected to the unit’s communication (COM) port. The External Device Commands option must be set to AT. " Procedure To control dial-in access: 1. Select the External Modem options. Main Menu → Configuration → Management and Communication → External Modem (Com Port) 2. Enable the Dial-In Access configuration option.
Security and Logins Limiting Telnet Access Telnet access can be limited by: H Disabling Telnet access completely. H Requiring a login for Telnet sessions that are not on the TS Management Link. H Assigning an access level for Telnet sessions. H Disabling TS Management Link access. To limit Telnet access via a service provider’s troubleshooting management link, see Limiting Telnet or FTP Access Over the TS Management Link.
Security and Logins Limiting FTP Access FTP access can be limited by: H Disabling FTP access completely. H Requiring a user ID and password to login. H Limiting FTP bandwidth. " Procedure To limit FTP access when the session is not on the TS Management Link: 1. Select the Telnet and FTP Session options. Main Menu → Configuration → Management and Communication → Telnet and FTP Sessions 2. Set the following configuration options, as appropriate. To . . . Set the configuration option . . .
Security and Logins Limiting Telnet or FTP Access Over the TS Management Link " Procedure To limit Telnet or FTP access when the session is on the TS Management Link: 1. Select the Telnet and FTP Session options. Main Menu → Configuration → Management and Communication → Telnet and FTP Sessions 2. Disable Telnet Session and/or FTP Session, as appropriate. 3. Return to the Management and Communication menu, and select Node IP. 4. Set the following configuration options, as appropriate. To . . .
Security and Logins Controlling SNMP Access The FrameSaver unit supports SNMP Version 1, which provides limited security through the use of community names. There are three methods for limiting SNMP access: H Disabling SNMP access. H Assigning SNMP community names and the access type. H Assigning IP addresses of those NMSs that can access the unit. Disabling SNMP Access When the SNMP access is disabled, the FrameSaver unit will not respond to SNMP messages. " Procedure To disable SNMP access: 1.
Security and Logins Assigning SNMP Community Names and Access Levels The FrameSaver unit supports the SNMP protocol and can be managed by an SNMP manager. SNMP manager access can be limited by: H Assigning the SNMP community names that are allowed to access the FrameSaver unit’s Management Information Base (MIB). H Specifying the type of access allowed for each SNMP community name. Whenever an SNMP manager attempts to access an object in the MIB, the community name must be supplied.
Security and Logins Limiting SNMP Access Through IP Addresses An additional level of security is provided by: H Limiting the IP addresses of NMSs that can access the FrameSaver unit. H Performing validation checks on the IP address of SNMP management systems attempting to access the FrameSaver unit. H Specifying the access allowed for the authorized NMS when IP address validation is performed.
Security and Logins See Configuring SNMP NMS Security Options in Chapter 3, Configuration, for more information about SNMP NMS Security configuration options. Creating a Login A login is required if security is enabled.* Up to six login ID/password combinations can be created using ASCII text, and each login must have a specified access level. Logins must be unique and they are case-sensitive. " Procedure To create a login record: 1. Select Administer Logins. Main Menu → Control → Administer Logins 2.
Security and Logins See Configuring SNMP NMS Security in Chapter 3, Configuration, for more information about security configuration options. Modifying a Login Logins are modified by deleting the incorrect login and creating a new one. Deleting a Login " Procedure To delete a login record: 1. Select Administer Logins. Main Menu → Control → Administer Logins 2. Page through login pages / records using the PgUp or PgDn function keys until the login to be deleted is displayed. 3. Select De l ete. 4.
Operation and Maintenance 5 This chapter includes the following: H Displaying System Information H Viewing LEDs and Control Leads — LED Descriptions — Control Lead Descriptions H Device Messages H Status Information — System and Test Status Messages, which includes: Self-Test Results Messages Health and Status Messages Test Status Messages — Network LMI-Reported DLCIs Status — PVC Connection Status — Network Interface Status H Performance Statistics — Clearing Performance Statistics — Service Leve
Operation and Maintenance Displaying System Information Use the Identity screen to view identification information about the FrameSaver unit. This information is useful if you are purchasing additional or replacement units and/or making firmware upgrades. Main Menu → Status → Identity View this field . . . To find the . . . System Name Domain name for this SNMP-managed node (up to 255 ASCII characters). System Contact Contact person for this SNMP-managed node.
Operation and Maintenance Viewing LEDs and Control Leads The FrameSaver unit’s faceplate includes LEDs ( light-emitting diodes) that provide status on the FrameSaver unit, its network interface, and its user data port. O K O K TS T FrameSaver® SLV AL M O K 9664 NETWORK PORT TM 00-16654 The Display LEDs and Control Leads screen allows you to monitor a remote unit and is useful when troubleshooting control lead problems.
Operation and Maintenance LED Descriptions The following table identifies the alarms that cause the Alarm LED to light. See Table 5-2 and Table 5-3 for network interface and user data port LED information. Table 5-1. General Status LEDs Label Indication Color What It Means OK Power and Operational Status Green ON – FrameSaver unit has power and it is operational. Operational Alarm ( Fail ) Red ALM OFF – FrameSaver unit is in a power-on self-test, or there is a failure.
Operation and Maintenance Table 5-2. Network Interface LED Label Indication Color What It Means OK Operational Status Green ON – The interchange circuits for the interface are in the correct state to transmit and receive data. OFF – A Loss of Signal (LOS) condition has been detected on the leased line network interface when it is not transmitting INFO3 or receiving INFO4. Table 5-3.
Operation and Maintenance Device Messages These messages appear in the messages area at the bottom of the screens. All device messages are listed in alphabetical order. Table 5-5. Device Messages (1 of 5) Message What It Indicates What To Do Access level is n , Read-only. User’s access level is 2 or 3; user is not authorized to change configurations. No action needed. Already Active Test selected is already running. H Allow test to continue. H Select another test. H Stop the test.
Operation and Maintenance Table 5-5. Device Messages (2 of 5) Message What It Indicates What To Do File Transfer Failed – Invalid file A file transfer was attempted, but it was not successful. H Try again, making sure you (Seen at an FTP terminal.) type the filename correctly. H Exit the FTP session, or download another file. See Changing Software. Invalid Character (x ) A non-valid printable ASCII character has been entered. Reenter information using valid characters.
Operation and Maintenance Table 5-5. Device Messages (3 of 5) Message What It Indicates What To Do Limit of PVC Connections reached New was selected from the PVC Connection Table and the maximum number of PVCs has already been created. H Do not create the PVC Name Must be Unique Name entered for a management PVC has been used previously. Enter another 4-character name for the logical/management link.
Operation and Maintenance Table 5-5. Device Messages (4 of 5) Message What It Indicates What To Do No Primary Destination Link DLCIs Available New or Modify was selected from the PVC Connection Table, but even though DLCIs are available to form a connection, no DLCIs are available on the network link, which is a suitable Primary PVC Destination. Configure additional DLCIs for the network link and try again.
Operation and Maintenance Table 5-5. Device Messages (5 of 5) Message What It Indicates What To Do Test Active No higher priority health and status messages exist, and a test is running. H Contact service provider if test initiated by the network. H Wait until the test ends and message clears. H Cancel all tests from the Test screen ( Path: main/test ). H Stop the test from the same screen the test was started from.
Operation and Maintenance Status Information Status information is useful when monitoring the FrameSaver unit. The following illustration shows the Status menu for the FrameSaver unit.
Operation and Maintenance System and Test Status Messages System and test status information is selected from the Status menu. Main Menu → Status → System and Test Status The following information is included on this screen: H Self-Test Results Messages H Health and Status Messages H Test Status Messages Self-Test Results Messages These self-test result messages appear in the Self-Test Results field at the top of the System and Test Status screen. Table 5-6.
Operation and Maintenance Health and Status Messages The following table provides Health and Status messages that apply to the FrameSaver unit. Table 5-7. Health and Status Messages (1 of 2) Message What It Indicates Auto-Configuration Active Auto-Configuration feature is active, which allows automatic configuration and cross-connection of DLCIs as they are reported by the network LMI.
Operation and Maintenance Table 5-7. Health and Status Messages (2 of 2) Message What It Indicates LMI Discovery in Progress, frame relay link 2 Local Management Interface protocol discovery is in progress to determine which protocol will be used on the specified frame relay link. LMI Down, frame relay link 2 The Local Management Interface(s) has been declared down for the specified frame relay link.
Operation and Maintenance Test Status Messages These test messages appear in the right column of the System and Test Status screen. You have the option of allowing the test to continue or aborting the test. See Chapter 6, Troubleshooting, for more information on tests, including how to start and stop them. Table 5-8. Test Status Messages Message What It Indicates DCLB Active, Network 1 A Data Channel V.54 Loopback (DCLB) is active on the network interface.
Operation and Maintenance Network LMI-Reported DLCIs Status Network LMI-reported DLCI statuses are selected from the Status menu. Main Menu → Status → LMI Reported DLCIs The LMI Reported DLCIs screen displays the status and CIR (if supported by the switch) for each DLCI, whether the DLCI is configured or not.
Operation and Maintenance Table 5-9. Network LMI-Reported DLCIs Status Field Status What It Indicates DLCI 16 through 1007 Identifies the Local Management Interface-reported DLCI numbers assigned to the selected interface – the identifying number assigned to the path between two frame relay FrameSaver units’ ports. DLCI statuses are listed in ascending order ( i.e., lowest number first ).
Operation and Maintenance PVC Connection Status PVC connection statuses are selected from the Status menu. Main Menu → Status → PVC Connection Status Only PVC connections with Source DLCIs configured to be Active are shown.
Operation and Maintenance Table 5-10. PVC Connection Status (2 of 2) Field Status What It Indicates EDLCI 0 to 62 For multiplexed DLCIs only. Identifies an individual link/ connection embedded within a DLCI. Status Identifies whether the physical interfaces, LMIs, and DLCIs are all enabled and active for this PVC connection. Active 1 H The PVC is currently active.
Operation and Maintenance Network Interface Status The network interface status is selected from the Status menu. Main Menu → Status → Network Interface Status Table 5-11. Network Interface Status (1 of 2) Field Status Operating Rate (Kbps) What It Indicates The frame relay network’s operating rate as detected by the unit’s network interface. 64 H 64 kbps 128 H 128 kbps Disconnected H The line was disconnected. Interface State Shows the state of the leased line BRI S/T network interface.
Operation and Maintenance Table 5-11. Network Interface Status (2 of 2) Field Status Receive Signal What It Indicates Shows the signals being received on the leased line BRI S/T network interface from the attached DSU(NT1). INFO0 H No Signal Indication. No signal is present, or a continuous flow of binary ones is being received. INFO2 H Frames with all B-channel bits and unused bit positions set to binary zero are being received. N and L bits are set according to normal coding rules.
Operation and Maintenance Performance Statistics Use the Performance Statistics menu to display statistical information for a selected interface. Statistical information is useful when trying to determine the severity and frequency or duration of a condition. Main Menu → Status → Performance Statistics Physical and link layer statistics (Layers 1 and 2) are collected on the port. The following menu shows the performance statistics that can be selected.
Operation and Maintenance Clearing Performance Statistics Performance statistics counters can be reset to the baseline when using a directly-connected asynchronous terminal and your security Access Level is Level-1. This feature is useful when troubleshooting problems. Statistic counters are not actually cleared using this feature. True statistic counts are always maintained so SLAs can be verified, and they can be viewed from an SNMP NMS.
Operation and Maintenance Service Level Verification Performance Statistics These statistics appear when Service Level Verification (SLV) is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Service Level Verification They only appear for the network interface and only if DLCIs are multiplexed. Table 5-12.
Operation and Maintenance Table 5-12. Service Level Verification Performance Statistics (2 of 2) Statistic What It Indicates Inbound Dropped Characters Total number of bytes transmitted by the far-end device that were dropped in transit. The counts continue to increment until the maximum value is reached (232 –2), then the count starts over. The SLV Delivery Ratio option (see Table 3-2, Service Level Verification Options) must be enabled for these statistics to appear.
Operation and Maintenance The statistics collected by the unit depend upon the device at the far end of the connection. If the far-end device is a FrameSaver SLV unit, frame relay, latency, and FDR/DDR * performance statistics are collected. If the far-end device is a non-FrameSaver device, or a FrameSaver 9120 or 9620, only frame relay statistics are collected. DLCI Performance Statistics These statistics appear when DLCI is selected from the Performance Statistics menu.
Operation and Maintenance Table 5-13. DLCI Performance Statistics (2 of 2) Statistic What It Indicates H With BECN Set H The number of frames and octets sent on the selected DLCI of the frame relay link with backward explicit congestion notifications. BECNs are sent to notify users of data traffic congestion in the opposite direction of the frame carrying the BECN indicator.
Operation and Maintenance Frame Relay Performance Statistics The following statistics appear when Frame Relay is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Frame Relay All counts continue to increment until the maximum value is reached (232 –2), then the count starts over. The NextLink and PrevLink function keys only appear when multiple frame relay links have been configured. Table 5-14.
Operation and Maintenance Table 5-14. Frame Relay Performance Statistics (2 of 3) Statistic What It Indicates Frame Relay Errors (cont’d) Short Rx Frames The number of frames received over the Network or Port-1 interface that were less than 5-octets ( five 8-bit bytes) in length. There may be a non-frame relay device on the other end of the link. Long Rx Frames The number of frames received over the Network or Port-1 interface that were more than 8192-octets in length.
Operation and Maintenance Table 5-14. Frame Relay Performance Statistics (3 of 3) Statistic What It Indicates Frame Relay HDLC Errors Rx Total Errors The number of receiver errors on the interface.
Operation and Maintenance FTP File Transfers The FrameSaver unit supports a standard File Transfer Protocol (FTP) server over Transmission Control Protocol (TCP). A complete binary image of the configuration files can be copied to a host to provide a backup. To use this feature, the unit must be configured to support Telnet and FTP Sessions.
Operation and Maintenance " Procedure To initiate an FTP session: 1. Start the FTP client program on your host. For example, on a UNIX host, type ftp, followed by the FrameSaver unit’s IP address. 2. If a login and password are required (see Creating a Login in Chapter 4, Security and Logins), you are prompted to enter them. If not, press Enter. The FTP prompt appears. The starting directory is the root directory ( / ).
Operation and Maintenance Upgrading System Software If you need to upgrade the FrameSaver unit’s program code, you must transfer the upgrade of the nam.ocd file in the system memory directory using the put command. NOTE: Upgrades can be performed through the network using a Management PVC, or through the COM port if Port Use is set to Net Link (see Table 3-15, Communication Port Options). " Procedure To download software: 1. Initiate an FTP session to the device that you are upgrading. 2.
Operation and Maintenance Determining Whether a Download Is Completed To see whether a download has completed, check the Identity screen. Main Menu → Status → Identity Check Alternate Software Rev. under the NAM Identity column. H If a software revision number appears, the file transfer is complete. H If In Progress appears, the file is still being transferred. H If Invalid appears, no download has occurred or the download was not successful.
Operation and Maintenance Transferring Collected Data SLV user history statistics and LMI packet capture data can be uploaded to an NMS or a Network Associates Sniffer using FTP, which is faster than other methods. The rate at which the data file is transferred is the rate set by the FTP Max Receive Rate (Kbps) option (see Table 3-12, Telnet and FTP Session Options in Chapter 3, Configuration).
Operation and Maintenance This page intentionally left blank.
Troubleshooting 6 This chapter includes the following: H Problem Indicators H Resetting the Unit and Restoring Communication — Resetting the Unit from the Control Menu — Resetting the Unit By Cycling the Power — Restoring Communication with a Misconfigured Unit H Troubleshooting Management Link Feature H LMI Packet Capture Utility Feature — Viewing Captured Packets from the Menu-Driven User Interface H Alarms H Troubleshooting Tables — Device Problems — Frame Relay PVC Problems H Tests Availab
Troubleshooting H Physical Tests — DTE Loopback H IP Ping Test H Lamp Test Problem Indicators The unit provides a number of indicators to alert you to possible problems: Indicators . . . See . . . LEDs Viewing LEDs and Control Leads and LED Descriptions in Chapter 5, Operation and Maintenance, as well as the user interface screen. Main Menu → Status → Display LEDs and Control LEDs Health and Status Health and Status Messages in Chapter 5, Operation and Maintenance.
Troubleshooting Resetting the Unit and Restoring Communication You can reset the unit in one of four ways: H Reset it from the Control menu. H Cycle the power. H Reset the configuration options for the COM port, or reload the factory default settings. H Set the appropriate MIB object from NMS (see your NMS documentation). The unit performs a self-test when it is reset. Resetting the Unit from the Control Menu Use this procedure to initiate a reset and power-on self-test of the unit.
Troubleshooting Restoring Communication with a Misconfigured Unit Misconfiguring the unit could render the menu-driven user interface inaccessible. If this occurs, connectivity to the unit can be restored via a directly connected asynchronous terminal. " Procedure To reset COM port settings: 1. Configure the asynchronous terminal to operate at 19.2 kbps, using character length of 8 bits, with one stop-bit, and no parity. In addition, set Flow Control to None. 2.
Troubleshooting Troubleshooting Management Link Feature A dedicated troubleshooting management link is available to help service providers isolate device problems within their networks. This feature allows Telnet or FTP access to the unit on this link and troubleshooting over this link is essentially transparent to customer operations. No alarms or SNMP traps are generated to create nuisance alarms for the customer.
Troubleshooting Viewing Captured Packets from the Menu-Driven User Interface The twelve most recent LMI events are stored in the trace log. Once the capture buffer or trace log is full, the oldest packets are overwritten.
Troubleshooting Alarms The following table describes the alarm conditions that will generate an SNMP trap for a physical interface, and the frame relay LMIs and DLCIs. These alarm conditions also generate Health and Status messages seen on the System and Test Status screen. Main Menu → Status → System and Test Status Table 6-1. Alarm Conditions (1 of 3) Alarm Condition What It Indicates What To Do CTS down to Port-1 Device The CTS control lead on the device’s interface is off.
Troubleshooting Table 6-1. Alarm Conditions (2 of 3) Alarm Condition What It Indicates What To Do LMI Down, frame relay link 2 The Local Management Interface is down for the specified frame relay link. For the network data port: H If LMI was never up, verify that the LMI Protocol setting reflects the LMI type being used. H If LMI was never up: H Verify that Frame Relay Performance Statistics show LMI frames being transmitted.
Troubleshooting Table 6-1. Alarm Conditions (3 of 3) Alarm Condition What It Indicates What To Do Network Com Link Down The communication link for the COM port is down and the COM port is configured for Net Link. Check the router connected to the COM port. Self-Test Failure The unit did not pass its basic verification tests when it was powered on or reset. H Reset the unit. SLV Timeout, DLCI nnnn, frame relay link 1, 2 H Contact your service representative.
Troubleshooting Troubleshooting Tables The unit is designed to provide many years of trouble-free service. However, if a problem occurs, refer to the appropriate table in the following sections for possible solutions. Device Problems Table 6-2. Device Problems Symptom Possible Cause Solutions No power, or the LEDs are not lit. The power cord is not securely plugged into the wall receptacle to rear panel connection. Check that the power cord is securely attached at both ends.
Troubleshooting Frame Relay PVC Problems Table 6-3. Frame Relay PVC Problems Symptom Possible Cause Solutions No receipt or transmission of data. Cross Connection of the DLCIs are configured incorrectly. Verify the PVC connections and DLCIs by checking the network-discovered DLCIs on the LMI Reported DLCIs screen. DLCI is inactive on the frame relay network. H Verify that the DLCI(s) is active on the PVC Connection Status screen. If the DLCI(s) is not active, contact the service provider.
Troubleshooting Tests Available The following tests are available to a FrameSaver SLV 9664.
Troubleshooting Starting and Stopping a Test Use this procedure to start, monitor, or abort specific tests. To abort all active tests on all interfaces, see Aborting All Tests. When the status of a test is . . . The only command available is . . . Inactive Start Active Stop Start or stop an individual test using the same procedure. " Procedure To start and stop a test: 1. Select the Test menu. Main Menu → Test 2. Highlight the Start command for the test you want to start and press Enter.
Troubleshooting PVC Tests PVC tests can be run on a requested DLCI for a selected interface. H When PVC tests are on a multiplexed DLCI between FrameSaver devices, they are nondisruptive to data, so user data can continue to be sent during a test. H If the device at one end of the circuit is not a FrameSaver device, PVC tests are on a standard DLCI and are disruptive to data. Also, the Connectivity test would not appear.
Troubleshooting Network or Port (Internal) PVC Loopback The PVC Loopback loops frames back to the selected interface on a per-PVC basis. This test logically (not physically) loops back frames received from another FrameSaver device through the selected frame relay PVC to the same device.
Troubleshooting Monitor Pattern This test monitors packets filled with a hexadecimal 55 test pattern and sequence number over the selected interface and DLCI to another FrameSaver device. To monitor a pattern test on a link: Main Menu → Test → [Network PVC Tests/Data Port PVC Tests] → Monitor Pattern The current number of sequence and data errors are shown under the Result column when the FrameSaver unit is in sync. An Out of Sync message appears when 5 frames out of 25 are missing or out of sequence.
Troubleshooting Physical Tests Physical Tests can only be commanded for the user data port. DTE Loopback The DTE external Loopback (DTLB) test loops the received signal on a user data port back to the DTE. Use this test for isolating problems on the user data port. An attached device or test equipment must generate data to be looped back. User Data Port Network Port DTLB 99-16284 CAUTION: This test will affect the operation of the frame relay PVCs assigned to the user data port.
Troubleshooting IP Ping Test An IP Ping test can be run to test connectivity between the FrameSaver unit and any FrameSaver device, router, or NMS to which it has a route. Times when you might want to run an IP Ping test are: H To test connectivity between the FrameSaver unit and any FrameSaver device in the network to verify that the path is operational. Select Procedure 1 to Ping any far-end FrameSaver device.
Troubleshooting " Procedure 2 To Ping the NMS at the central site: 1. Verify that the central site NMS has the FrameSaver unit’s IP address in its routing table so it can communicate with the FrameSaver unit. 2. Verify that the central site NMS’s router has the FrameSaver unit’s IP address in its routing table so it can communicate with the FrameSaver unit. 3.
Troubleshooting This page intentionally left blank.
Setting Up OpenLane for FrameSaver Devices 7 This chapter includes: H OpenLane Support of FrameSaver Devices H Setting Up the OpenLane SLM System H Setting Up FrameSaver SLV Support OpenLane Support of FrameSaver Devices Paradyne’s OpenLane Service Level Management (SLM) system supports all FrameSaver and FrameSaver SLV devices with the following features: 9664-A2-GB20-00 H Web and database services H Web access to health and status information H Web access to real-time, as well as historical
Setting Up OpenLane for FrameSaver Devices Setting Up the OpenLane SLM System Instructions for installing Paradyne’s OpenLane Service Level Management (SLM) System can be found in the following documents: H OpenLane 5.x Service Level Management for UNIX Quick Start Installation Instructions H OpenLane 5.x Service Level Management for Windows NT Quick Start Installation Instructions See Product-Related Documents in About This Guide for document numbers. Select the appropriate document.
Setting Up NetScout Manager Plus for FrameSaver Devices 8 This chapter includes NetScout Manager Plus information as it relates to FrameSaver SLV devices.
Setting Up NetScout Manager Plus for FrameSaver Devices Before Getting Started Before getting started, you need to copy some OpenLane directories to a NetScout Manager Plus user directory. OpenLane provides these directories as a starting point for loading new alarms and creating history files. A template of alarms and values for configuring alarms and several templates for creating history files specific to the FrameSaver unit are available.
Setting Up NetScout Manager Plus for FrameSaver Devices Configuring NetScout Manager Plus For the NetScout Manager Plus main window to appear, make sure your environment is set up exactly as specified in your NetScout Readme file. You need to: H Copy the OpenLane directory to a user directory. H Add frame relay agents to the NetScout Manager. H Configure agent properties. H Verify and correct domains and groups. H Monitor the agent and DLCIs.
Setting Up NetScout Manager Plus for FrameSaver Devices Adding FrameSaver SLV Units to the NetScout Manager Plus Network " Procedure 1. Bring up the NetScout Manager Plus main window. 2. Select the FrameRelay radio button from the agent type selection bar (on the left side of the window). A list of configured frame relay agents appear in the list box below the Name and IP Address headings.
Setting Up NetScout Manager Plus for FrameSaver Devices Verifying Domains and Groups " Procedure 1. From the NetScout Manager Plus main window, with the FrameRelay and Admin radio buttons still selected, click on the Config Manager icon to open the Configuration Manager main window. 2. Verify that only FrameSaver SLV-supported domains appear listed in the Domain column. FrameSaver SLV-supported domains include: — ATALK — IPX — RMON — DECNET — NETB — SNA — IP — NET~ — VINES — IPV6 — OSI 3.
Setting Up NetScout Manager Plus for FrameSaver Devices Correcting Domains and Groups Properties need to be edited when not using the Paradyne-provided file and when: H An unsupported domain needs to be deleted. H A missing domain needs to be added. H Groups, Samples, Interval, and Logging are not configured as specified in Step 3 of Verifying Domains and Groups. " Procedure 1. Select the the Property... button (down the center of the Configuration Manager main window).
Setting Up NetScout Manager Plus for FrameSaver Devices 3. To add a FrameSaver SLV-supported domain or correct property settings, select the Edit... button (to the right of the Domain section of the Property Editor window). The Edit Domain window opens. 4. Click on the domain from the Domains list and configure the following: Property Description Setting Groups Stats (S) Statistics collection Enabled for all domains. Hosts (H) Level 3 information (network) Enabled for IP domain only.
Setting Up NetScout Manager Plus for FrameSaver Devices Adding SLV Alarms Using a Template Once DLCIs have been discovered, SLV alarms should be configured and assigned to each DLCI. OpenLane provides a template for configuring alarms. DLCI alarms can be configured manually, but using the Paradyne alarm defaults template greatly reduces configuration time.
Setting Up NetScout Manager Plus for FrameSaver Devices Editing Alarms " Procedure 1. From the NetScout Manager Plus main window, with the FrameRelay and Admin radio buttons still selected, click on the Config Manager icon to open the Configuration Manager main window. 2. Select the Custom radio button from the Properties File area (in the upper right of the window), then Property... (down the center of the screen). The Custom Property Editor window opens. 3.
Setting Up NetScout Manager Plus for FrameSaver Devices 4. Edit any trap defaults that may be required. See Step 4 of Adding SLV Alarms Manually for field settings you may want to change. 5. Select the OK button (at the bottom of the screen) to apply your changes. The window closes and the Configuration Manager main window reappears. 6. Select the Install button (down the center of the Configuration Manager main window) to apply your changes.
Setting Up NetScout Manager Plus for FrameSaver Devices Adding SLV Alarms Manually Once DLCIs have been discovered, SLV alarms should be defined and assigned to each DLCI. When configuring alarms manually, every alarm must be configured for each DLCI; that is, if there are eight alarms and 20 DLCIs, 160 trap configurations must be created (8 x 20). For this reason, it is recommended that the OpenLane defaults be used. Follow the procedure below to configure alarms manually.
Setting Up NetScout Manager Plus for FrameSaver Devices 4. Click on the ... button to the right of indicated fields for a drop-down list from which selections can be made. Minimally, configure the following fields: Field Select or Enter . . .
Setting Up NetScout Manager Plus for FrameSaver Devices Creating History Files Up to 14 additional user history tables can be created in the FrameSaver unit for each interface. An interface is a specific DLCI or the entire frame relay interface. A table must be created for each DLCI or frame relay link to be monitored. Additional user history tables are created using the command-line prompt in NetScout Manager Plus to load a file that contains the OIDs (Object IDs) to be monitored into the unit.
Setting Up NetScout Manager Plus for FrameSaver Devices " Procedure 1. Open a terminal window and go to $NSHOME/usr. 2. Copy an example or interface-specific file to a new file that contains the user history table number. 3. Open the new file using a text editor. The variables in the file are listed with their OIDs (Object IDs). The frame relay interface number 101022001 must replace @IFN, and the DLCI number to be monitored must replace @DLCI. Example: frCircuitSentFrames Change “1.3.6.1.2.1.10.32.2.1.6.
Setting Up NetScout Manager Plus for FrameSaver Devices Installing the User-Defined History Files Once the user-defined history files have been created, the files need to be installed. History files are installed from the command-line prompt in NetScout Manager Plus. Should the FrameSaver unit be reset, these files will need to be reinstalled. The command used to install a new user history table is located in $NSHOME/bin. CAUTION: Do not use user_history_table_1 or 2.
Setting Up NetScout Manager Plus for FrameSaver Devices Monitoring a DLCI’s History Data Once the monitoring variables have been defined, a problem DLCI can monitored. " Procedure To monitor user history data: 1. From the NetScout Manager Plus main window, with the FrameRelay radio button still selected, select the Traffic radio button. The appropriate icons appear. 2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI list box (under the agent list box). 3.
Setting Up NetScout Manager Plus for FrameSaver Devices 5. Select History List from the View menu. The History List window opens. The newly defined user history variables should appear on this list. 6. Highlight the desired set of user history variables, and select the OK button. Data is gathered based upon the configured user history variables. This may take some time, so please be patient. 7. Select 2D or 3D Bar from the Format menu, if desired (3D Bar is shown).
Setting Up NetScout Manager Plus for FrameSaver Devices Using the 2D or 3D Bar to view the user history data collected, you can click on a particular bar and get an expanded view of the data. 8. Click anywhere on this window to return to the previous window view (see Step 7 of this procedure). Refer to Launching User History and Understanding Custom History Display in Using Custom History of the NetScout Manager Plus User Guide for additional information.
Setting Up NetScout Manager Plus for FrameSaver Devices " Procedure 1. Select the Traffic radio button to monitor the newly added agent, or one of its DLCIs. 2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI list box (under the agent list box). 3. If you want to monitor one of the agent’s DLCIs, highlight the DLCI to be monitored. 4. Click on an applicable icon. The selected graphical report should open.
Setting Up NetScout Manager Plus for FrameSaver Devices Statistical Windows Supported Not all icons that appear on the NetScout Manager Plus main window are supported for FrameSaver units. For example, All Convs (conversations) and TopNConv icons appear when the Protocol radio button is selected, but conversations are not supported.
Setting Up Network Health for FrameSaver Devices 9 FrameSaver units are compatible with Concord Communication’s Network Health software. In addition, Network Health has released the first in a series of software modules that integrate FrameSaver SLV enhanced performance statistics into its reporting package (see the FrameSaver SLV report example on page 9-9). To get this report, you need Network Health R4.01 or higher.
Setting Up Network Health for FrameSaver Devices For additional information about installing, accessing, and managing FrameSaver SLV devices through Concord’s Network Health, and for information about applicable reports, refer to: H Network Health Installation Guide to help you install the application. H Network Health User Guide to help you get started using the application. H Network Health Reports Guide to help you understand and use Frame Relay reports.
Setting Up Network Health for FrameSaver Devices Discovering FrameSaver Elements Once licenses are entered and you have access to the applications, the Discover dialog box opens. Use this dialog box to search for SLV units in your network and discover their DLCIs. Saving the results of the search creates definitions in the Poller Configuration, which are used to poll the units.
Setting Up Network Health for FrameSaver Devices Configuring the Discovered Elements Network Health sets the speed for discovered elements when it polls the unit for the first time. For a FrameSaver SLV unit, the speed set would be the unit’s CIR. No additional configuration should be required. However, you should verify that all appropriate information has been retrieved. NOTE: If an SLV unit does not have CIR configured, or if it is not configured correctly, Network Health sets the unit’s CIR to 0 kbps.
Setting Up Network Health for FrameSaver Devices Grouping Elements for Reports Once the discovery process is completed and required changes are made, the newly discovered elements (DLCIs) should be organized into a group for Health reporting. Grouping makes for easier monitoring and management of similar node types (e.g., all SLV elements). Once grouped, you can then run reports on all DLCIs in the network, as well as reports on individual DLCIs. " Procedure To group elements: 1.
Setting Up Network Health for FrameSaver Devices Generating Reports for a Group Once Network Health has had sufficient time to gather data from the polled DLCIs and the DLCIs have been grouped, you can start generating reports. When selecting a report Section, select WAN from the drop-down list. See Running Reports from the Console in the Network Health Reports Guide for additional information. That section also tells you how to schedule automatic report generation.
Setting Up Network Health for FrameSaver Devices About Trend Reports By specifying specific variables like bandwidth, trend analysis can be performed and shown on Trend Reports. Up to ten variables for a DLCI, or ten DLCIs on one variable can be generated on a single trend report. Information can be presented in a line graph, pie chart, bar chart, or table format. Any amount of time can be specified for the reporting period.
Setting Up Network Health for FrameSaver Devices — Elements Summary Report – Compares DLCI traffic with volume and the baseline, bandwidth utilization, and errors. Use this report for DLCI detail information and comparison, to identify DLCIs with above or below average volume so they can be investigated when there are any significant changes. H Supplemental Report – Shows DLCI availability and latency. The information shown in this report is also on other Health reports.
Setting Up Network Health for FrameSaver Devices H Trend Reports – Perform trend analysis on up to ten specified variables for DLCIs. Variables other than bandwidth can be selected for a trend report (e.g., burst octets), but a bandwidth trend report should be generated when investigating problems that appear on Exceptions Reports, Supplemental Reports, and Health reports.
Setting Up Network Health for FrameSaver Devices This page intentionally left blank.
Menu Hierarchy A Menus The following is a graphical representation of the FrameSaver SLV unit’s menu organization.
Menu Hierarchy Menu Hierarchy MAIN MENU System and Test Status • Self-Test Results • Health and Status • Test Status Network LMI Reported DLCIs • DLCI • Status • CIR (bps) Status Status System and Test Status LMI Reported DLCIs PVC Connection Status Network Interface Status Performance Statistics Display LEDs and Control Leads Identity Test Configuration Auto-Configuration Control PVC Connection Status Network Interface Status Performance Statistics • Source Link, DLCI, EDLCI • Primary Destinati
Menu Hierarchy Configuration Edit/Display MAIN MENU Status Test Load Configuration from: Configuration Auto-Configuration Control System Network Data Ports PVC Connections Management and Communication System • Frame Relay and LMI • Service Level Verification • General Network and Data Ports PVC Connection Table Management and Communication Options • Physical • Frame Relay • Source Link, DLCI, • Node IP • Management PVCs • General SNMP Management • Telnet and FTP Session • SNMP NMS Security • SN
Menu Hierarchy This page intentionally left blank.
SNMP MIBs and Traps, and RMON Alarm Defaults B This appendix contains the following: H MIB Support H Downloading MIBs and SNMP Traps H System Group (mib-2) — FrameSaver Unit’s sysDescr (system 1) — FrameSaver Unit’s sysObjectID (system 2) H Interfaces Group (mib-2) — Paradyne Indexes to the Interface Table (ifTable) — NetScout Indexes to the Interface Table (ifTable) H Standards Compliance for SNMP Traps — Trap: warmStart — Trap: authenticationFailure — Traps: linkUp and linkDown — Traps: enterpri
SNMP MIBs and Traps, and RMON Alarm Defaults MIB Support The FrameSaver unit supports the SNMP Version 1, and has the capability of being managed by any industry-standard SNMP manager and accessed by external SNMP managers using the SNMP protocol.
SNMP MIBs and Traps, and RMON Alarm Defaults System Group (mib-2) This section provides the system description and system object identifier for the System Group for the FrameSaver 9664 unit, which is an SNMPv1 MIB. FrameSaver Unit’s sysDescr (system 1) The following is the system description (sysDescr [system 1] ) for the NMS subsystem in the FrameSaver 9664 unit: PARADYNE LL S/T FrameSaver SLV; Model: 9664; S/W Release: (MM.mm.bb [MM=Major.mm=minor.
SNMP MIBs and Traps, and RMON Alarm Defaults Interfaces Group (mib-2) Clarification for objects in the Interfaces Group, as defined in RFC 1573 and RFC 1213, which is an SNMPv1 MIB, is provided in this section. Paradyne Indexes to the Interface Table (ifTable) The following table provides the ifName for each interface type, the ifDescr, and the ifIndex that Paradyne has assigned to each. Table B-1.
SNMP MIBs and Traps, and RMON Alarm Defaults NetScout Indexes to the Interface Table (ifTable) For remote monitoring at sites where FrameSaver units are operating with NetScout Probes, use the following ifName, ifDescr, and ifIndex. Table B-2. NetScout Interface Objects Information ifName Description ifDescr (ifEntry 2) ifIndex For the user side: RMON (IN/OUT); Network ISDN S/T of FR DTE; Child Card: LL S/T FR NIM; S/W Release: MM.mm.
SNMP MIBs and Traps, and RMON Alarm Defaults Standards Compliance for SNMP Traps This section describes the FrameSaver unit’s compliance with SNMP format standards and with its special operational trap features. All traps have an associated string to help you decipher the meaning of the trap. Strings associated with an interface with a substring containing $ifString have the following format: ‘DLCI $dlciNumber “$circuitId” of $ifName frame relay link “$linkName”.’ — $dlciNumber is the DLCI number.
SNMP MIBs and Traps, and RMON Alarm Defaults Trap: warmStart This trap indicates that the FrameSaver unit has been reset and has stabilized. Table B-3. warmStart Trap Trap What It Indicates Possible Cause warmStart FrameSaver unit has just reinitialized and stabilized itself. H Reset command sent. Variable-Binding H Power disruption. String: ‘Unit reset.’ devLastTrapString (devHealthAndStatus.
SNMP MIBs and Traps, and RMON Alarm Defaults Traps: linkUp and linkDown These traps are supported on the following interfaces: H Network ISDN S/T interface – Physical sublayer interfaces H Synchronous data port – Physical sublayer interfaces H Frame relay logical link layer interfaces Table B-5. linkUp and linkDown Traps Trap What It Indicates Possible Cause linkDown A failure in one of the communication interfaces has occurred. A failure in one of the communication interfaces has occurred.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings(1 of 2) Interface Variable-Bindings Possible Cause H ifIndex (RFC 1573) H linkDown – One or more alarm Physical Sublayer Network ISDN S/T H ifAdminStatus (Supported by the media-specific RS232-like MIB.) (RFC 1573) H ifOperStatus (RFC 1573) H devLastTrapString (devHealthAndStatus.mib) conditions are active on the interface. The alarm condition for the ISDN S/T interface is Loss of Signal (LOS).
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings(2 of 2) Interface Variable-Bindings Possible Cause Frame Relay H ifIndex (RFC 1573) H linkDown – LMI is down for (Supported by the media-specific Frame Relay Services MIB.) H ifAdminStatus Logical Link Sublayer (RFC 1573) H ifOperStatus (RFC 1573) H devLastTrapString (devHealthAndStatus.mib) the LMI Protocol configured, 2 or Frame Relay link is disabled. Strings: ‘$ifString down.
SNMP MIBs and Traps, and RMON Alarm Defaults Traps: enterprise-Specific These traps indicate that an enterprise-specific event has occurred. Supported enterprise-specific traps are listed below. Table B-7. enterprise-Specific Traps and Variable-Bindings (1 of 2) Trap Variable-Bindings Possible Cause enterpriseCIRChange(15) H devFrExtDlciIfIndex CIR has changed due to the LMI report. LMI Protocol is set to Standard and the network’s CIR changed. (devFrExt.mib) H devFrExtDlciDlci (devFrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. enterprise-Specific Traps and Variable-Bindings (2 of 2) Trap Variable-Bindings Possible Cause enterpriseMissedSLVDown(16) H devFrExtDlciIfIndex SLV Timeout Error Event Threshold has been exceeded. (devFrExt.mib) H devFrExtDlciDlci (devFrExt.mib) H devFrExtDlciMissed- SLVs (devFrExt.mib) enterpriseMissedSLVUp(116) enterpriseRMONResetToDefault(13) H devLastTrapString (devHealthAndStatus.mib.) H devLastTrapString (devHealthAndStatus.
SNMP MIBs and Traps, and RMON Alarm Defaults Traps: RMON-Specific Two traps are defined to support the Alarm and Events Groups of RMON. See RMON Alarm and Event Defaults for the default values that will generate RMON-specific traps. Table B-8. RMON-Specific Traps and Variable-Bindings Trap Variable-Bindings Possible Cause risingAlarm H alarmIndex (RFC 1757) Object being monitored has risen above the set threshold.
SNMP MIBs and Traps, and RMON Alarm Defaults RMON Alarm and Event Defaults The FrameSaver unit supports automatic generation of RMON alarm and event information. Each alarm sets an SNMP variable to monitor. When the threshold set for the monitored variable is exceeded, an SNMP trap or a log event is sent.
SNMP MIBs and Traps, and RMON Alarm Defaults Network ISDN S/T Physical Interface Alarm Defaults These alarms only apply to the FrameSaver unit’s network ISDN S/T interface. They are created during RMON initialization and put into the Paradyne-defined alarm area. Table B-9. Network ISDN S/T Physical Interface Alarm Defaults Item Unavailable Seconds Sample Type 1 MIB/Tag/OID 2 D Interval MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Frame Relay Link Alarm Defaults These alarms apply to the FrameSaver unit’s frame relay link interfaces. They are created during RMON initialization. Table B-10.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-10. Frame Relay Link Alarm Defaults (2 of 2) Item Sample Type 1 MIB/Tag/OID 2 Rx Overruns D Event Type Rising Falling Threshold Threshold Default Default 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 Interval MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkRxOverruns OID: .1.3.6.1.4.1.1795.2.24.2. 6.9.4.7.1.28.
SNMP MIBs and Traps, and RMON Alarm Defaults DLCI Alarm Defaults – Paradyne Area These alarms apply to all DLCIs on the network interface and can be created during RMON initialization or when a DLCI is created. They are put into the Paradyne alarm area. Table B-11.
SNMP MIBs and Traps, and RMON Alarm Defaults DLCI Alarm Defaults – NetScout Area These alarms can be created during RMON initialization or when a DLCI is created. They are put into the NetScout alarm area. Table B-12 identifies alarm defaults that do not change, and Table B-13 identifies alarm defaults that change when the interface’s line speed changes. The thresholds for these alarms can be edited using NetScout Manager Plus so they match the values in the SLA between the customer and service provider.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-12. Static DLCI Alarm Defaults – NetScout Area (2 of 2) Item Sample Type 1 MIB/Tag/OID 2 Tx CIR Utilization D Interval MIB: FR DTE MIB (RFC 2115) 60 secs (1 min) Event Type None Rising Falling Threshold Threshold Default Default Must be 0 configured. Tag: frCircuitSentOctets OID: .1.3.6.1.2.1.10.32.2.1. 7.I.D 1 D = Delta. Indicates that the calculated difference between the current value and the previous value is contained in the MIB.
SNMP MIBs and Traps, and RMON Alarm Defaults Object ID Cross-References (Numeric Order) The FrameSaver unit supports automatic generation of RMON alarm and event information. Each alarm sets an SNMP variable to monitor. When the threshold set for the monitored variable is exceeded, an SNMP trap is sent and/or a log entry is made.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (1 of 4) Object ID (OID) 1 Item MIB/Tag Link Speed MIB: MIB II (RFC 1573) .1.3.6.1.2.1.2.2.1. . . .1.3.6.1.2.1.2.2.1.5.I Tag: ifSpeed .1.3.6.1.2.1.2.2.1.10.I All DLCI + LMI Rx Octets MIB: MIB II (RFC 1573) Tag: ifInOctets .1.3.6.1.2.1.2.2.1.16.I All DLCI + LMI Tx Octets MIB: MIB II (RFC 1573) Tag: ifOutOctets .1.3.6.1.2.1.2.10.32.2.1. . . .1.3.6.1.2.1.10.32.2.1.4.I.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (2 of 4) Object ID (OID) 1 Item MIB/Tag Unavailable Seconds MIB: pdn_ IfExtTotal.mib (E) .1.3.6.1.4.1.1795.2.24.2. . . .1.3.6.1.4.1.1795.2.24.2.6.12.1.1.1.4.I Tag: pdnIfExtTotalUASs .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.16.I Rx Non-octet Aligns MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkRxNonOctet .1.3.6.1.4.1.1795.2.24.2.13.1.2.1.4.H.T.N IP Top Listeners (1– 6) MIB: pdn_FrExt.mib (E) Tag: devRmonIPTopNDstIP .1.3.6.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (3 of 4) Object ID (OID) 1 Item MIB/Tag Network Frames Dropped In CIR MIB: pdn_FrExt.mib (E) Network Frames Offered Above CIR MIB: pdn_FrExt.mib (E) Network Frames Lost Above CIR MIB: pdn_FrExt.mib (E) Network Frames Offered Above CIR Within EIR MIB: pdn_FrExt.mib (E) Network Frames Dropped Above CIR Within EIR MIB: pdn_FrExt.mib (E) Network Frames Offered Above EIR MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (4 of 4) Object ID (OID) 1 Item MIB/Tag Burst Upper Limit (1– 5) MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1. . . .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.2.I.D.N Tag: devFrExtBurstUpLimit .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.3.I.D.N Burst Octets (1– 5) MIB: pdn_FrExt.mib (E) Tag: devFrExtBurstOctets .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.4.I.D.N Burst Frames (1– 5) MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. Alarm OID Cross-Reference (1 of 2) Object ID (OID) Item MIB/Tag Rx FECNs MIB: FR DTE MIB (RFC 2115) .1.3.6.1.2.1.10.32.2.1. . . .1.3.6.1.2.1.10.32.2.1.4.I.D Tag: frCircuitReceivedFECNs .1.3.6.1.2.1.10.32.2.1.5.I.D Rx BECNs MIB: FR DTE MIB (RFC 2115) Tag: frCircuitReceivedBECNs .1.3.6.1.2.1.10.32.2.1.6.I.D Frames Sent MIB: FR DTE MIB (RFC 2115) Tag: frCircuitSentFrames .1.3.6.1.2.1.10.32.2.1.7.I.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. Alarm OID Cross-Reference (2 of 2) Object ID (OID) Item MIB/Tag Current Latency MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4. . . .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.7.I.D Tag: devFrExtLatencyLatest .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.2.I.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.3.I.N Frame Size Upper Limits 1– 5 MIB: pdn_FrExt.mib (E) Frame Size Count 1– 5 MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults This page intentionally left blank.
Connectors, Cables, and Pin Assignments C This appendix shows the FrameSaver unit’s rear panel, and provides pin assignments for the connectors/interfaces and cables. NOTE: In the pin assignment tables of this appendix, if the pin number is not shown, it is not being used. Rear Panel The following illustration shows the rear panel of the FrameSaver unit.
Connectors, Cables, and Pin Assignments COM Port Connector The following table shows the signals and pin assignments for the DB25 communication port connector.
Connectors, Cables, and Pin Assignments LAN Adapter Converter and Cable The following shows the pin assignments for the: H DB25 plug-to-modular jack converter between the COM port and the 8-conductor LAN Adapter cable (Feature No. 3100-F1-920) H Custom 8-conductor cable (with modular plugs on both ends) between the converter and the LAN Adapter (Feature No.
Connectors, Cables, and Pin Assignments Standard EIA-232 Crossover Cable A standard EIA-232 crossover cable can be used to connect the COM port to an external modem. This is an EIA-232 plug-to EIA-232 plug (DB25-to-DB25) cable. The external modem must be configured so it is compatible with the FrameSaver unit. See page C-5 to configure an external modem.
Connectors, Cables, and Pin Assignments " Procedure To configure an external modem: 1. Disconnect the asynchronous terminal from the standard cable. See page C-4 for an illustration of the COM Port connection. 2. Reconnect the crossover cable to the external modem. 3. Enable auto-answer on the modem, and configure it to use the following LSD, DSR, CTS, RTS, and DTR control leads. See the table below for AT D0 command strings.
Connectors, Cables, and Pin Assignments Network Connector The network connection is through the ISDN BRI leased-line interface/connector, which is an 8-position unkeyed modular jack. The following table shows the pin assignments for the BRI network port and the purpose of each.
Connectors, Cables, and Pin Assignments User Data Port Connector The following table provides the pin assignments for the EIA-530A connector to a DTE.
Connectors, Cables, and Pin Assignments X.21 DTE Adapter Cable (Feature No. 3100-F1-571) This adapter is used to connect the user data port to a DTE with an X.21 cable. It is a 25-pin EIA-530A-to-15-pin X.21 (DB25-to-X.21) adapter cable. 98-15883 The following table provides the pin assignments for the DB25-to-X.21 adapter cable.
Connectors, Cables, and Pin Assignments V.35 DTE Adapter (Feature No. 3100-F1-570) This adapter is used to connect the user data port to a DTE with an V.35 cable. It is a 25-pin EIA-530A-to-34-position V.35 (DB25-to-V.35) adapter.
Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-V.35 adapter.
Connectors, Cables, and Pin Assignments EIA-530 Straight-through Cable (Feature No. 9008-F1-523) A standard straight-through cable is used to connect the user data port to a DTE when the Port Type is E530 (EIA-530A). It is a 25-pin EIA-530A-to-25-pin EIA-530A (DB25-to-DB25) cable.
Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-DB25 straight-through cable.
Technical Specifications D Table D-1. FrameSaver SLV 9664 Unit Technical Specifications (1 of 2) Specification Criteria Approvals EMC (Class A) CISPR22, VCCI Network CTR 3 CE 73/23/EEC, 89/336/EEC, 91/263/EEC Safety EN 60950 Physical Environment Operating temperature 32° F to 122° F ( 0° C to 50° C ) Storage temperature – 4° F to 158° F (– 20° C to 70° C ) Relative humidity 5% to 85% ( noncondensing ) Shock and vibration Withstands normal shipping and handling Weight 2.85 lbs. ( 1.
Technical Specifications Table D-1. FrameSaver SLV 9664 Unit Technical Specifications (2 of 2) D-2 Specification Criteria COM Port DB25 connector Data rates 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.2 kbps Network Interface 8-position unkeyed modular jack (per ISO 8877) Service supported ISDN Leased Line BRI S/T (ITU-T I.430) Data rates 64 kbps using the B1 channel 128 kbps using both B-channels User Data Port 25-position ( DB25 ) subminiature connector Selectable EIA-530A, V.35, X.
Equipment List E Equipment See page E-2 for cables you can order. Model/ Feature Number Description FrameSaver SLV Unit FrameSaver SLV 9664 unit for up to 16 PVCs Includes Standalone Housing, Universal 100 – 240 Vac Power Supply, Power Cord, Network (NT1) Cable, and Installation Instructions, and Quick Reference.
Equipment List Cables This table lists cables you can order. E-2 Description Part Number Feature Number Leased Line ISDN BRI Cable, 8-position unkeyed modular plug at each end (20 feet/6.1 meters) 035-0360-2031 — V.35 DTE Adapter, EIA-530A-to-V.35 002-0095-0131 3100-F1-570 X.21 DTE Adapter Cable, EIA-530A-to-X.21 (1 foot/.3 meters) 035-0302-0131 3100-F1-571 COM Port-to-Terminal Cable, 8-pin modular -to-DB25 (14 feet /4.
Index Numbers B 55 hexadecimal, test pattern, 6-16 back door access when locked out, 6-4 Back-to-Back Mode Active, 5-13 operation, setting up, 3-16 Backspace, 2-6 Bc, 3-30 Be, 3-30 blank, field value, 2-9 branches/menus, 2-4 BRI, network port, C-6 bursting, port, 1-3 A aborting tests, 6-13 Access Dial-In, 3-53 Name, 3-39 Type, 3-43 Access Level, 4-10, 4-11 assigning, 4-9 Port, 3-50 security, 2-1 Session, 3-41 adding, SLV units to network, 9-3 Alarm, 6-7 (Fail), 5-4 adding manually, 8-11 conditions, 6-2
Index Committed Burst Size Bc (Bits), 3-29 Committed Information Rate (CIR), 3-29 Communication, Port, user interface options, 3-49 Community Name, 3-39 assigning, 4-9 Concord Network Health, compatibility, 9-1 Concord’s Network Health, 1-1 Configuration Auto, Active, 5-13 displaying and changing options, 3-5 menu, 3-3 menu/branch, 2-4 option areas, 3-4 option tables, 3-17 saving options, 3-7 tables, 3-4 upload/download, 1-4 configuring added SLV units/elements, 9-4 DLCI records manually, 3-28 frame relay
Index Directory, Alternate Dial-Out, 3-48 disabling, SNMP access, 4-8 Discard Eligible (DE), 3-37 Disconnect, Time (Minutes), 3-41, 3-51 discovering elements/DLCIs, 9-3 Discovery frame relay (FR), 3-11 Frame Relay Mode, saving a mode change, 3-13 displaying configuration options, 3-5 identity information, 5-2 LEDs and control leads, 5-3 DLCI, 3-38 Destination, 3-32 Down, 5-13, 6-7 on SLV Timeout, 3-20 interface status, 5-17 monitoring user history, 8-16 Number, 3-28 Priority, 3-30 Records, 3-28 Source, 3-3
Index frames, 3-37 FTP, 1-4, 5-31 file transfers, 5-31 initiating a session, 5-31 limiting access, 4-4, 4-6 Login Required, 3-42 Max Receive Rate (kbps), 3-42 Session, 4-6 function keys, 2-5, 2-7 G General LEDs, 5-4 options, 3-22 SNMP management, options, 3-39 Traps, 3-45 generating reports, 9-6 glossary, viii grouping elements for reports, 9-5 interface, network status, 5-20 Internal, Transmit Clock, 3-24 Inverse ARP, 1-3 Invert Transmit Clock, 3-24 IP default destination, 3-34 node information, 3-33 Pi
Index LMI and PVC availability, 1-3 Behavior, 3-18 Clearing Event (N3), 3-19, 3-27 configuring frame relay and, 3-18 Down, 5-14, 6-8 Error Event (N2), 3-18, 3-27 frame relay statistics, 5-29 Heartbeat (T1), 3-19, 3-27 Inbound Heartbeat (T2), 3-19, 3-28 N4 Measurement Period (T3), 3-19, 3-28 packet utility, 6-5 Parameters, 3-27 pass-through, 3-18 Protocol, 3-26 Status Enquiry (N1), 3-19, 3-27 uploading packet capture data, 5-35 local external DTE loopback, 3-25 setting up management, 3-14 locked out, 4-3, 4
Index navigating the screens, 2-6 Net Link, Port Use, 3-49 NetOnly, 3-11 NetScout Manager Plus, NMS support, 1-5 NMS support, 1-1 Network Com Link Down, 5-14, 6-9 DLCI records, options, 3-28 Health (Concord) reports, 9-1 interface, C-6 LED, 5-5 latency, 1-3 physical interface options, 3-23 PVC Loopback, 6-15 reference time, 1-3 Network Health, installation and setup, 9-2 Network Initiated DCLB, 3-23 NIM, 5-2 NMS IP Address, 3-43, 3-44, 4-10 IP Validation, 3-43, 4-10 OpenLane management solution, 1-4 SNMP s
Index RMON alarm and event defaults, B-14 Specific Traps, B-13 Traps, 3-46 user history collection, 1-3 router, setting up to receive RIP, 3-15 router-independence, 1-3, 3-18 Routing, Information Protocol (RIP), 3-52 RTS, control lead, 5-5 running reports, 9-6 RXD, control lead, 5-5 Protocol address resolution, 1-3 Link, 3-52 LMI, 3-26 Point-to-Point (PPP), 3-52 Routing Information (RIP), 3-38, 3-52 Serial Line, IP (SLIP), 3-52 Simple Network Management (SNMP), 3-39 PVC availability, 1-3 connection status
Index setting up auto-configuration, 3-10 external modem, 3-9 local management, 3-14 service provider connectivity, 3-15 SNMP trap managers, 3-43 so router can receive RIP, 3-15 SLA, 1-2, 1-4 SLIP, 3-52 SLM, vii, 1-1 OpenLane, 7-1 SLV (service level verifier), 1-1 configuring, 3-20 Delivery Ratio, 3-20 DLCI Down on Timeout, 3-20 Packet Size, 3-21 performance statistics, 5-24 reports, 1-2 Sample Interval (secs), 3-20 Synchronization Role, 3-21 Timeout, Error Event Threshold, 3-20, 3-21 SNMP assigning commun
Index T T1, LMI Heartbeat, 3-19, 3-27 T2, LMI Inbound Heartbeat, 3-19, 3-28 T3, LMI N4 Measurement Period, 3-19, 3-28 Tab key, 2-6 Tc, 3-29 TCP, 5-31 technical specifications, D-1 Telnet limiting access, 4-4, 4-5 Session, 4-5 user interface options, 3-40 Terminal, Port Use, 3-49 Test menu/branch, 2-4 Mode, 5-4 Status messages, DBM, 5-15 Tests, 1-3 aborting, 6-13 available, 6-12 DTE Loopback, 6-17 Duration, 3-22 IP Ping, 6-18 Lamp, 6-19 physical, 6-17 PVC, 6-14 PVC Loopback, 6-15 starting or stopping, 6-13
Index V W V.
