FrameSaver® SLV 9126, 9126-II, and 9128-II CSU/DSU, and 9126-II Router User’s Guide Document No.
Copyright © 2002 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 1 xi Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv About the FrameSaver SLV 2 Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Overview . . . . . . . . . . . .
Contents 3 Configuration Procedures 4 3-1 Configuration Option Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Accessing and Displaying Configuration Options . . . . . . . . . . . . . 3-4 Changing Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Saving Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Configuration Options ii Basic Configuration . . . . . . . . . . . . . . . . . . . .
Contents 5 Assigning Time Slots/Cross Connections . . . . . . . . . . . . . . . . . . . . . . 4-51 Assigning Frame Relay Time Slots to the Network Interface . . . . 4-52 Assigning DSX-1 Time Slots to the Network Interface . . . . . . . . . 4-53 Assigning a Synchronous Data Port to Network or DSX-1 Time Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 Clearing Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6 IP Router Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Bridge Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 IP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Land Bug Prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Smurf Attack Prevention . . . . . . . . . . . . . . . . . . . . . . .
Contents 8 Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18 System and Test Status Messages . . . . . . . . . . . . . . . . . . . . . . . . 7-19 Network LMI-Reported DLCIs Status . . . . . . . . . . . . . . . . . . . . . . 7-29 IP Path Connection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31 PVC Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents LMI Packet Capture Utility Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 Viewing Captured Packets from the Menu-Driven User Interface . 8-6 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 Viewing the Trap Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14 8-14 Device Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Administering and Managing SLM Activations . . . . . . . . . . . . . . . . . . . 9-6 Entering an Activation Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Checking Activation Certificate Status. . . . . . . . . . . . . . . . . . . . . . 9-7 Scheduling Activations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Checking the Status of Scheduled Activations . . . . . . . . . . . . . . . 9-9 Canceling Scheduled Activations . . . . . . . . . . . .
Contents B SNMP MIBs and Traps, and RMON Alarm Defaults MIB Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Downloading MIBs and SNMP Traps. . . . . . . . . . . . . . . . . . . . . . . . . . B-2 System Group (mib-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 FrameSaver Unit’s sysDescr (system 1) . . . . . . . . . . . . . . . . . . . . B-3 FrameSaver Unit’s sysObjectID (system 2). . . . . . . .
Contents Protocol and Port Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31 ICMP Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31 TCP Port Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-33 UDP Port Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34 D Router Command Line Summaries and Shortcuts CLI Summaries . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents F Technical Specifications G Equipment List Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Guide Purpose and Intended Audience This document contains information needed to properly set up, configure, and verify operation of the FrameSaver SLV (Service Level Verifier) 9126, 9126-II, and 9128-II CSU/DSU, and 9126-II Router running firmware release 2.0.3 or above. It is intended for system designers, engineers, administrators, and operators. You must be familiar with the functional operation of digital data communications equipment and frame relay networks.
About This Guide Section Description Chapter 9, Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Identifies where installation and setup information is located and how FrameSaver units are supported. Chapter 10, Setting Up NetScout Manager Plus for FrameSaver Devices Describes setup of the NetScout Manager Plus application so it supports FrameSaver units, and so you can change alarm and history file defaults.
About This Guide Product-Related Documents Document Number Document Title Paradyne FrameSaver Documentation: 9000-A2-GN19 FrameSaver SLV ISDN Installation Instructions 9000-A2-GN1D 9000 Series Access Carrier Installation Instructions 9126-A2-GL10 FrameSaver SLV 9126 and 9126-II Quick Reference 9126-A2-GL12 FrameSaver SLV 9126-II Router Quick Reference 9126-A2-GN10 FrameSaver SLV 9126 1-Slot Unit Installation Instructions 9126-A2-GN11 FrameSaver SLV 9126-II 1-Slot Unit Installation Instructions
About This Guide Conventions Used Convention Used When Used Italic To indicate variable information (for example, DLCI nnnn, where nnnn denotes a 4-digit number). Menu 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.
About the FrameSaver SLV 1 This chapter includes the following: System Overview, below FrameSaver Diagnostic and SLM Feature Sets on page 1-4 FrameSaver Diagnostic Feature Set on page 1-5 FrameSaver SLM Feature Set on page 1-10 OpenLane SLM System on page 1-11 NetScout Manager Plus and NetScout Probes on page 1-12 System Overview Our system solution consists of: FrameSaver ® SLV (Service Level Verifier) units OpenLane® SLM (Service Level Management) system NetScout Manager Plus app
1. About the FrameSaver SLV CSU/DSU-Specific Features The following features only apply to the FrameSaver SLV 9126, 9126-II, and 9128-II CSU/DSUs: Two Interfaces. Provides two interfaces for traffic: — Synchronous DTE port for user data — Ethernet Interface for management data Upstream Pipelining.
1. About the FrameSaver SLV CLI Access and Configuration. Provides a router Command Line Interface (CLI), along with the menu-driven user interface, for configuring and managing the router. It is accessed from the Main Menu via a direct COM port connection or Telnet.
1. About the FrameSaver SLV FrameSaver Diagnostic and SLM Feature Sets Depending upon the model ordered, the FrameSaver unit has the basic FrameSaver frame relay and diagnostic capability, or it is enhanced with additional SLM (Service Level Management) reporting capability. These are referred to as feature sets, which provide different levels of intelligence for monitoring, managing, and reporting performance of the unit. The two feature sets include: Basic Diagnostic Feature Set.
1. About the FrameSaver SLV To obtain a Feature Activation Certificate, provide the model to be upgraded, your OpenLane system license key number, and the number of FrameSaver units to be upgraded to SLM capability. You can order the certificate for a single unit or for many units. Your Feature Activation Certificate will include an Activation Certificate Number, the Feature Group Number for the additional SLM features, your OpenLane license key number, and the number of device activations ordered.
1. About the FrameSaver SLV Auto-Configuration. Provides the following automatic configuration features: — Time Slot Discovery – For automatic configuration of all network DS0 assignments. — Frame Relay Discovery – For automatic discovery of network DLCIs and configuration of a user data port DLCI, the PVC connection, and a management PVC, which is multiplexed with user data DLCIs. — LMI Protocol Discovery – For automatic configuration of the protocol being used by the network.
1. About the FrameSaver SLV Integral Modem. Provides an internal 14.4 Kbps modem to support dialing in to the unit for out-of-band management and automatic dialing out of SNMP traps. Modem PassThru. Provides access to another device’s VT100-compatible user interface over a dial connection. When this feature is enabled, a logical connection between the unit’s modem and COM ports is created, allowing access to a collocated device’s serial port via the FrameSaver unit’s internal modem.
1. About the FrameSaver SLV DSX-1 Drop/Insert Port. Allows DTEs/PBXs that support the DS1 signal format to share the T1 network with other high-speed equipment so that voice traffic can share the same local access circuit as the frame relay data. 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. Enhanced Ping Operation.
1. About the FrameSaver SLV — When the SLV Sample Interval is set to 10 seconds, provides advance detection of network problems before a DLCI Down indication is received, to minimize data loss. — Provides customer premises equipment (CPE) with a Backward Explicit Congestion Notification (BECN) when backup bandwidth is not sufficient for the traffic, allowing the CPE time to slow traffic to the ISDN before the network starts discarding data.
1. About the FrameSaver SLV FrameSaver SLM Feature Set A FrameSaver SLV unit with the advanced SLM feature set provides the following features in addition to those provided with the basic set: TruePut™ Technology. Using Frame Delivery Ratios (FDR) and Data Delivery Ratios (DDR), throughput (within and above CIR, as well as between CIR and EIR, and above EIR) can be measured precisely, eliminating inaccuracies due to averaging. Intelligent Service Level Verification.
1. About the FrameSaver SLV OpenLane SLM System Being standards-based, the OpenLane SLM (Service Level Management) system can be used with other management applications like HP OpenView or IBM’s NetView. OpenLane includes HP OpenView adapters for integrating OpenLane features with the OpenView Web interface. Being Web-based, the OpenLane system provides Web access to the data contained in the database to provide anytime, anywhere access to this information via a Web browser.
1. About the FrameSaver SLV NetScout Manager Plus and NetScout Probes Provides complete LAN and WAN traffic analysis and monitoring functions for FrameSaver devices. The following features are supported using this application: 1-12 Thresholds for RMON 1 (Remote Monitoring, Version 1) alarms and events can be configured. Performance monitoring can be performed using collected RMON 2 (Version 2) data.
User Interface and Basic Operation 2 This chapter contains information about how to access, use, and navigate the menu-driven user interface and the Router’s Command Line Interface (CLI).
2. User Interface and Basic Operation Logging On Start a session using one of the following methods: 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. Dial-in connection using the internal modem. Direct terminal connection over the COM port. When logging on, the User Interface Idle screen appears.
2. User Interface and Basic Operation If your login was . . . Then the . . . Valid Main Menu appears. Begin your session. NOTE: If your login is valid, but access is denied, there are two currently active sessions. Invalid Message, Invalid Password, appears on line 24, and the Login screen is redisplayed. After three unsuccessful attempts: A Telnet session is closed. The User Interface Idle screen appears for a directly connected terminal. The internal modem connection is disconnected.
2. User Interface and Basic Operation Main Menu Entry to all of the FrameSaver unit’s tasks begins at the Main Menu, which has six menus or branches. The Access Level at the top of the screen only appears when security has been set up.
2. User Interface and Basic Operation Screen Work Areas There are two user work areas: Screen area – Where you input information into fields. Function keys area – Where you perform specific screen functions. Below is a sample configuration screen.
2. User Interface and Basic Operation Navigating the Screens You can navigate the screens by: Using keyboard keys. 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.
2. User Interface and Basic Operation Function Keys All function keys (located in the lower part of the screen; see the example in Screen Work Areas 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 function . . . And press Enter to . . . M or m MainMenu Return to the Main Menu screen.
2. 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.
2. 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: Manually type in (enter) the field value or command.
2. User Interface and Basic Operation Navigating the Router’s CLI Access the FrameSaver DSL Router’s Command Line Interface by pressing the Shift-r function key from the Main Menu. There is no need to press Ctrl-a first to access the function keys area of the screen. Once the CL I is accessed, you can use keyboard keys to navigate within the interface. Using the router’s CLI, you can display and edit router configuration settings, view router status, and access router tests.
Configuration Procedures 3 This chapter includes the following: Basic Configuration — Configuration Option Areas — Accessing and Displaying Configuration Options — Changing Configuration Options — Saving Configuration Options 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.
3. Configuration Procedures Configuration Menu main/config Device Name: Node A 9128-II 5/26/2000 23:32 CONFIGURATION EDIT/DISPLAY System Network DSX-1 Data Ports ISDN Time Slot Assignment PVC Connections Management and Communication Auto Backup Criteria -------------------------------------------------------------------------------Exit Ctrl-a to access these functions, ESC for previous menu MainMenu Save Changing an Auto-Configuration setting can also change the FrameSaver unit’s configuration.
3. Configuration Procedures Configuration Option Areas The FrameSaver unit arrives with configured factory default settings, which are located in the Factory Default Configuration option area.
3. Configuration Procedures 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.
3. Configuration Procedures 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.
3. Configuration Procedures 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, or Scratchpad 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 Options 4 This chapter includes the following: Using the Easy Install Feature on page 4-3 Using RIP with FrameSaver SLV CSU/DSUs on page 4-4 Entering System Information and Setting the System Clock on page 4-5 Setting Up the Modem on page 4-6 — Setting Up Call Directories for Trap Dial-Out — Setting Up to Use the Modem PassThru Feature Setting Up Auto-Configuration on page 4-8 — Selecting a Frame Relay Discovery Mode — Automatically Removing a Circuit Setting Up Dial Backup
4.
4. Configuration Options Using the Easy Install Feature The Easy Install feature provides a straight-forward installation menu that requires minimal configuration to get the FrameSaver unit up and running quickly, and to set up remote configuration and management via Telnet access from the NOC (Network Operations Center).
4. Configuration Options Using RIP with FrameSaver SLV CSU/DSUs 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 and FLEX devices. Node IP information should be set up (see Configuring Node IP Information on page 4-74). Procedure To set up your router and FrameSaver SLV CSU/DSU so that the router can learn routes to FrameSaver devices: 1.
4. Configuration 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. Main Menu → Control → System Information The following information is available for viewing. Save any entries or changes. If the selection is . . . Enter the . . . Device Name Unique name for device identification of up to 20 characters.
4. Configuration Options Setting Up the Modem The unit has an internal modem for dial-in access to the menu-driven user interface, as well as dial-out capability when an SNMP trap is generated. When the modem will be used to dial out, Modem Directory phone numbers need to be set up. Otherwise, simply configure or change dial-in access to the unit. The modem port is already configured for connection to an asynchronous terminal and dial-in access, with Port Use set to Terminal.
4. Configuration Options Setting Up to Use the Modem PassThru Feature Dial-in access to the router is possible via the Modem PassThru feature, also known as the Router Assist feature. The FrameSaver unit’s COM port must be connected to the router’s auxiliary (AUX) or console port, and the COM port must be configured for this use.
4. Configuration Options 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.
4. Configuration Options 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 and a user data port DLCI, and automatically connects them to create a PVC.
4. Configuration Options Discovery Mode Configuration Description NetOnly Disable Auto-configuration of a network DLCI only; no Port-1 or PVC connections are configured. No Port-1, PVC connection, or management DLCI is configured. No frame relay discovery or automatic configuration takes place. The FrameSaver unit will be configured manually.
4. Configuration Options 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. If Yes (y) is entered, the Delete All DLCIs and PVC Connections? prompt appears. No is the default for this prompt.
4. Configuration Options Setting Up Dial Backup When configuring units with ISDN backup capability, the following guidelines apply: Central site configuration guidelines: — Set up the ISDN DBM physical interface. — If a BRI DBM, change the Automatic Backup Configuration to Multi_Site_Backup. (A PRI DBM is already configured for multisite backup.) — Modify the Link Profile(s) that Automatic Backup Configuration created to add a phone number.
4. Configuration Options Setting Up Automatic Backup Configuration The Automatic Backup Configuration feature is used to automatically create alternate DLCI records and PVC connections on the ISDN DBM (backup) interface for current or newly discovered PVC Connections and Management PVCs. This feature is already set up, with Single_Site_Backup as the default for units with a BRI DBM and Multi_Site_Backup for units with a PRI DBM.
4. Configuration Options When the Automatic Backup Configuration setting is changed, the following prompts appear. No is the default for these prompts. The following prompt appears . . . When the . . . Automatic Backup Configuration setting was changed, and Save was selected Saving will cause Auto-Configuration to update and Restart. Are you sure? If you select . . .
4. Configuration Options When the . . . The following prompt appears . . . If you select . . .
4. Configuration Options Modifying ISDN Link Profiles Once an ISDN Link Profile is configured using the Automatic Backup Configuration feature, phone numbers and Calling IDs need to be entered. FrameSaver units with ISDN backup capability can originate or answer calls, as needed, so both phone numbers and Calling IDs are needed. Procedure 1. Select Link Profiles, then Modify. Main Menu → Configuration → ISDN → Link Profiles 2.
4. Configuration Options Restricting Automatic Backup and Configuring Backup Timers You can specify when auto backup is allowed to occur. If backup is restricted and a backup is active when the allowed time for backups is over, then the backup is terminated and the data is returned to the primary data path regardless of the primary path’s condition.
4.
4. Configuration Options PVC Backup Over the Network Interface Generally, backup can be performed on the network interface’s frame relay link using a backup PVC, as well on an ISDN link; the unit does not have to have the ISDN DBM feature. In this case, create a DLCI Record on the network interface that will be used for backup, then modify the PVC Connections or Management PVCs to add the alternate destination.
4. Configuration Options 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.
4. Configuration Options Configuring the Overall System The System menu options are explained in the following sections: Configuring Frame Relay and LMI for the System (CSU/DSUs) Configuring Service Level Verification Options Configuring General System Options Configuring Frame Relay and LMI for the System (CSU/DSUs) 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 4-1, System Frame Relay and LMI Options).
4. Configuration Options Table 4-1. System Frame Relay and LMI Options (2 of 4) LMI Behavior (continued) Net1-FR1_Follows_Port-1 – Brings LMI down on the network interface when LMI on Port-1 goes down, disabling the network interface and deasserting its control leads. When LMI on Port-1 comes back up, the network interface is reenabled. The LMI state on the network interface has no effect on the LMI state on Port-1. That is, the network interface’s LMI follows Port-1’s LMI.
4. Configuration Options Table 4-1. System Frame Relay and LMI Options (3 of 4) LMI Error Event (N2) Possible Settings: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Default Setting: 3 Configures the LMI-defined N2 parameter, which sets the number of errors that can occur on the LMI link before an error is reported. Applies to both the user and network sides of a UNI. 1 – 10 – Specifies the maximum number of errors.
4. Configuration Options Table 4-1. System Frame Relay and LMI Options (4 of 4) LMI N4 Measurement Period (T3) Possible Settings: 5, 10, 15, 20, 25, 30 Default Setting: 20 Configures the LMI-defined T3 parameter, which is the time interval (in seconds) that the network side of the LMI uses to measure the maximum number of status enquiry messages that have been received (N4) from the user side. 5 – 30 – Specifies the interval of time in increments of 5.
4. Configuration Options Configuring Class of Service Definitions Select Class of Service Definitions from the System menu to display or change the Class of Service definitions to be used with latency, availability, and throughput measurements of IP traffic on IP Enabled circuits. Main Menu → Configuration → System → Class of Service Definitions The Class of Service Definitions screen appears. Procedure To create a new Class of Service definition: 1.
4. Configuration Options 8. Select Save, then select PgDn or PgUp. The Class of Service Definitions page reappears. In the Code Points Assigned column next to your selected name there is now a Y for Yes. 9. If latency and availability should be measured for the selected name, change the N in the Measure Latency & Availability column to Y. 10. Select Save. To configure these options, Service Type on the Easy Install screen must be set to Frame Relay. Table 4-2.
4. Configuration Options Code Point Definitions Select Class of Service Definitions from the System menu, then PgDn or PgUp, to display or change the Code Point definitions for a Class of Service ID. See Configuring Class of Service Definitions on page 4-25 for instructions. Table 4-3. Code Point Definitions Code Pnt Possible Settings: 000000–111111 Default Setting: None. This read-only field shows the possible Code Points. Code Points are described in RFC 2474.
4. Configuration Options Configuring Service Level Verification Options SLV options are selected from the System menu (see Table 4-4, Service Level Verification Options). Main Menu → Configuration → System → Service Level Verification Table 4-4. Service Level Verification Options (1 of 3) SLV Sample Interval (secs) Possible Settings: 10 – 3600 Default Setting: 60 Sets the inband communications interval between FrameSaver SLV devices.
4. Configuration Options Table 4-4. Service Level Verification Options (2 of 3) SLV Delivery Ratio Possible Settings: Enable, Disable Default Setting: Disable Determines whether communication of Frame and Data Delivery Ratios (FDR/DDR) between FrameSaver SLV devices is enabled. To use this capability, both ends of all PVCs must be FrameSaver SLV devices. If some of the units are FrameSaver 9124s or 9624s, they must be running software version 1.2 or higher.
4. Configuration Options Table 4-4. Service Level Verification Options (3 of 3) SLV Round Trip Latency Error Threshold (ms) Available Settings: 50, 51, 52, . . . 10000 Default Setting: 10000 Specifies the number of milliseconds that must be exceeded before an SLV Latency Threshold alarm event is declared and backup, if configured, is initiated for a DLCI. If SLV Type is Standard, the latency applies to a multiplexed DLCI.
4. Configuration Options Configuring General System Options Select General from the System menu to configure the general system configuration options (see Table 4-5, General System Options). Main Menu → Configuration → System→ General Table 4-5. General System Options (1 of 3) 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.
4. Configuration Options Table 4-5. General System Options (2 of 3) Secondary Clock Source Possible Settings: Net1, DSX, Internal, DBM Default Setting: Internal Provides a secondary clock source when the primary clock source fails. The source selected for this configuration option provides all of the timing within the unit and the clocks for all of the external interfaces. The clock source will switch back to primary when the primary clock source returns and is stable for 10 seconds.
4. Configuration Options Table 4-5. General System Options (3 of 3) System Alarm Relay Possible Settings: Enable, Disable Default Setting: Disable Specifies whether an alarm condition for the unit will activate the system alarm relay. The alarm relay is deactivated when the condition causing the alarm is corrected. If more than one alarm condition is present, the alarm relay remains active until all alarm conditions are cleared.
4. Configuration Options Configuring Physical Interfaces Characteristics for physical interfaces are explained in the following sections: Configuring the Network Interface Configuring a User Data Port (CSU/DSUs) Configuring the DSX-1 Interface Configuring the ISDN DBM Interface Configuring the Network Interface When configuring the physical characteristics for the network interface, select Physical from the Network menu (see Table 4-6, Network Physical Interface Options).
4. Configuration Options Table 4-6. Network Physical Interface Options (2 of 4) Line Build Out (LBO) Possible Settings: 0.0, –7.5, –15, –22.5 Default Setting: 0.0 Specifies the line build out for the signal transmitted to the network. 0.0, –7.5, –15, –22.5 – Specifies line build out in dB. Bit Stuffing Possible Settings: 62411, Disable Default Setting: 62411 Determines the type of bit insertion to provide ones density requirements for data transmitted to the network.
4. Configuration Options Table 4-6. Network Physical Interface Options (3 of 4) Network Initiated PLB Possible Settings: Enable, Disable Default Setting: Enable Allows the initiation and termination of the payload loopback (PLB) to be controlled by the receipt of PLB-Actuate and PLB-Release commands from the network. Display Conditions – This option only appears when Line Framing Format is set to ESF. Enable – PLB is controlled by PLB-Actuate and PLB-Release commands.
4. Configuration Options Table 4-6. Network Physical Interface Options (4 of 4) Excessive Error Rate Threshold Possible Settings: 10E-4, 10E-5, 10E-6, 10E-7, 10E-8, 10E-9 Default Setting: 10E-4 Sets the error rate threshold that determines when an EER condition is declared. The excessive error rate is determined by the ratio of the number of CRC6 errors to the total number of bits received over a set period of time. Display Conditions – This option only appears when Line Framing Format is set to ESF.
4. Configuration Options Configuring a User Data Port (CSU/DSUs) Select Physical from the Data Ports menu to display or change the physical characteristics of the data port connected to the DTE (see Table 4-7, Data Port Physical Interface Options). Main Menu → Configuration → Data Ports → Physical Table 4-7. Data Port Physical Interface Options (1 of 5) Port Status Possible Settings: Enable, Disable Default Setting: Enable Determines whether the data port is being used and can be configured.
4. Configuration Options Table 4-7. Data Port Physical Interface Options (2 of 5) Max Port Rate (Kbps) Possible Settings: 1536, 2048 Default Setting: 1536 Specifies the maximum clock rate for a user data port. The data rate for this port is limited to the rate specified by this option so that the maximum rate supported by an attached DTE is not exceeded.
4. Configuration Options Table 4-7. Data Port Physical Interface Options (3 of 5) Monitor RTS (Control) Possible Settings: Enable, Disable Default Setting: Enable Specifies whether the state of the Request To Send (RTS) circuits on the user data port will be used to determine when valid data communication is possible with the DTE. When this condition is detected, CTS is deasserted, LMI is declared down, and no further transfer of frame relay data can occur on this interface.
4. Configuration Options Table 4-7.
4. Configuration Options Table 4-7. Data Port Physical Interface Options (5 of 5) Action on Network Yellow Alarm Possible Settings: None, Halt Default Setting: Halt Specifies the action to take on the synchronous data port when a yellow alarm is received on the network interface. (A yellow alarm indicates a problem with the signal being transmitted to the network.) Display Conditions – This option only appears for Port-2 on a FrameSaver SLV 9128-II, when Port Use is set to Synchronous Data.
4. Configuration Options Configuring the DSX-1 Interface Select DSX-1 to display or change the physical configuration options when a DSX-1 interface is installed (see Table 4-8, DSX-1 Physical Interface Options). Main Menu → Configuration → DSX-1 Table 4-8. DSX-1 Physical Interface Options (1 of 2) Interface Status Possible Settings: Enable, Disable Default Setting:Disable Specifies whether the DSX-1 interface selected is available for use. Enable – The interface is available.
4. Configuration Options Table 4-8. DSX-1 Physical Interface Options (2 of 2) Line Equalization Possible Settings: 0–133, 133–266, 266–399, 399–533, 533–655 Default Setting: 0–133 Permits a standard DSX signal to be delivered over a distance of up to 655 feet. 0–133 – Equalization on the DSX-1 side allows up to 133 feet of cable between the FrameSaver unit and the DTE. 133–266 – Equalization on the DSX-1 side allows up to 266 feet of cable between the FrameSaver unit and the DTE.
4. Configuration Options Configuring the ISDN DBM Interface For models with ISDN backup capability, select Physical from the ISDN menu to configure the physical characteristics for DBM Interface. Main Menu → Configuration → ISDN → Physical When configuring a BRI DBM, refer to Table 4-9, ISDN BRI DBM Physical Interface Options. When configuring a PRI DBM, refer to Table 4-10, ISDN PRI DBM Physical Interface Options. Table 4-9.
4. Configuration Options Refer to the Table 4-10 when configuring a PRI DBM. Table 4-10. ISDN PRI DBM Physical Interface Options (1 of 3) Interface Status Possible Settings: Enable, Disable Default Setting: Disable Determines whether the ISDN interface is available for use. Enable – The ISDN interface is enabled. Disable – The ISDN interface cannot be configured, nor can it transmit or receive data. No PVC connections or frame relay DLCIs will be deleted.
4. Configuration Options Table 4-10. ISDN PRI DBM Physical Interface Options (2 of 3) Line Build Out (LBO) Possible Settings: 0.0, –7.5, –15, –22.5 Default Setting: 0.0 Specifies the line build out for the signal transmitted to the ISDN. 0.0, –7.5, –15, –22.5 – Specifies line build out in dB.
4. Configuration Options Table 4-10. ISDN PRI DBM Physical Interface Options (3 of 3) Excessive Error Rate Threshold Possible Settings: 10E-4, 10E-5, 10E-6, 10E-7, 10E-8, 10E-9 Default Setting: 10E-4 Sets the error rate threshold that determines when an EER condition is declared. The excessive error rate is determined by the ratio of the number of CRC6 errors to the total number of bits received over a set period of time.
4. Configuration Options Setting Up ISDN Link Profiles For models with ISDN backup capability, select ISDN Link Profiles from the ISDN menu to set up the ISDN Link Profiles (see Table 4-11, ISDN Link Profile Options). Main Menu → Configuration → ISDN → ISDN Link Profiles Table 4-11. ISDN Link Profile Options (1 of 3) Link Name Possible Settings: ASCII Text Entry, HQ_Site Default Setting: HQ_Site for first link; blank for all others Assigns the name to the ISDN link profile.
4. Configuration Options Table 4-11. ISDN Link Profile Options (2 of 3) Outbound Phone Number Possible Settings: 0 – 9, *, #, space, _ , –, (, or ) Default Setting: none Specifies the primary phone number to call (the ISDN Called Party Identifier) for the Link Profile. Up to 18 valid characters can be entered. Each Outbound Phone Number must be unique. If not, the Outbound Phone Number is Not Unique message appears and you must enter another phone number.
4. Configuration Options Table 4-11. ISDN Link Profile Options (3 of 3) Caller Identification Method Possible Settings: Caller ID, Proprietary Default Setting: Caller ID Specifies the method used to identify callers. NOTE: The Caller Identification Method setting must be the same at both ends of the circuit.
4. Configuration Options Assigning Frame Relay Time Slots to the Network Interface Before assigning network time slots for use by frame relay traffic, configure the Network physical and Frame Relay options (if needed), then allow Time Slot Discovery to autodetect and assign the appropriate time slots to frame relay.
4. Configuration Options Time Slot Assignment Rule: Valid network time slots are either Available or contain a Frame Relay Link 1 assignment. Procedure 1. Follow this menu selection sequence: Main Menu → Configuration → Time Slot Assignment → Frame Relay Network Assignments The Frame Relay Network Assignments screen appears. This screen contains a matrix of the current assignment status of all time slots on the network interface. 2. Enable or disable Time Slot Discovery.
4.
4. Configuration Options Procedure 1. Follow this menu selection sequence: Configuration → Time Slot Assignment→ DSX-to-Network Assignments The DSX-1 to Network Assignments screen appears. This screen contains a matrix of the current cross-connect status of all time slots on the network interface. 2. Move the cursor to the next time slot that can be edited (underlined). Use the spacebar or type in the desired time slot to display its time slot assignment. 3.
4. Configuration Options Only those DSX-1-to-Network assignments from page 1 are displayed on this page, from left to right and top to bottom in ascending order, by network and time slot. When a CGA condition (LOS, OOF, or AIS) is declared for a T1 interface, the signaling bits being transmitted to the other T1 interface for the DS0 are forced to idle for two seconds (except for user-defined patterns which are transmitted immediately). This drops any call in progress.
4. Configuration Options Table 4-12. Signaling and Trunk Conditioning Values (2 of 3) 9128-A2-GB20-80 Network Side Meanings DSX-1 Side E&M-idle The signaling bits transmitted to the cross-connected T1 interface during a CGA represent the idle state for an E&M interface (ABCD = 0000). E&M idle E&M-busy The signaling bits transmitted to the cross-connected T1 interface during a CGA represent the busy state for an E&M interface (ABCD = 1111).
4. Configuration Options Table 4-12. Signaling and Trunk Conditioning Values (3 of 3) Network Side Meanings DSX-1 Side PLAR3idle The signaling bits transmitted to the cross-connected T1 interface during a CGA represent the idle state for a PLAR D3 interface (ABCD = 0000). PLAR3idle PLAR3busy The signaling bits transmitted to the cross-connected T1 interface during a CGA represent the busy state for an PLAR D3 interface (ABCD = 1111).
4. Configuration Options Assigning a Synchronous Data Port to Network or DSX-1 Time Slots For a FrameSaver SLV 9128-II, which has two data ports, another assignment screen is available.
4. Configuration Options For easy movement between screens, select the FrAssign function key to go directly to the Frame Relay Network Assignments screen or the DSXAssign function key to go to the DSX-1 to Network Assignments screen. Time Slot Assignment Rules: To assign a synchronous data port to network or DSX-1 time slots, Port-2’s Port Use option must be set for Synchronous Data (see Table 4-7, Data Port Physical Interface Options).
4. Configuration Options 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 4-13, Interface Frame Relay Options). Main Menu → Configuration → [Network/Data Ports] → Frame Relay See Configuring Frame Relay for an Interface on page 4-61 , for additional information. Table 4-13.
4. Configuration Options Table 4-13. Interface Frame Relay Options (2 of 3) Traffic Policing Possible Settings: Enable, Disable Default Setting: Disable Determines whether or not CIR (Committed Information Rate) and EIR (Excess Information Rate) will be enforced by the unit on frames being sent on network frame relay links. Enable – CIR and EIR are enforced. Frames that exceed CIR will be marked Discard Eligible (DE).
4. Configuration Options Table 4-13. Interface Frame Relay Options (3 of 3) 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, . . .
4. Configuration Options Manually Configuring DLCI Records The Auto-Configuration feature automatically configures DLCI Records and their PVC Connections. DLCI Records can also be created manually (see Table 4-14, DLCI Record Options).
4. Configuration Options Table 4-14. DLCI Record Options (2 of 4) DLCI Type Possible Settings: Standard, Multiplexed, IP Enabled 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.
4. Configuration Options Table 4-14. DLCI Record Options (3 of 4) Bc Possible Settings: 0 – 1536000 Default Setting: 0 Allows you to display or change the DLCI’s committed burst size. Display Conditions – This option only appears when Committed Burst Size is set to Other. 0 – 1536000 – Specifies the DLCI’s committed burst size. Excess Burst Size (Bits) Specifies the maximum amount of data in bits that the network may accept beyond the CIR without discarding frames.
4. Configuration Options Table 4-14. DLCI Record Options (4 of 4) Backup Group Possible Settings: A, B, C, . . . Z, None Default Setting: None Assigns DLCIs to a backup group so backup does not take place unless all DLCIs in the group are no longer operational or latency has been exceeded. Backup is terminated when one DLCI in the group is operational again. This feature reduces backup charges when redundant PVCs have been configured.
4. Configuration Options Configuring PVC Connections The Auto-Configuration feature automatically configures PVC Connections and their DLCI Records. PVC Connections can also be created manually (see Table 4-15, PVC Connection Options). 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.
4. Configuration Options Table 4-15. PVC Connection Options (2 of 4) Source EDLCI Possible Settings: 0 – 62 Default Setting: Initially blank; no default. Specifies the source Embedded Data Link Connection Identifier (EDLCI) for a frame relay interface when a multiplexed DLCI record is selected as one end of a connection. Display Conditions – This option only appears when Source DLCI contains a multiplexed DLCI record number. 0 – 62 – Specifies the EDLCI number.
4. Configuration Options Table 4-15. PVC Connection Options (3 of 4) Primary Destination EDLCI Possible Settings: 0 – 62 Default Setting: Initially blank; no default. Specifies the primary destination Embedded Data Link Connection Identifier (EDLCI) for a frame relay interface when a multiplexed DLCI record is selected as one end of a connection. Display Conditions – This option only appears when the Primary Destination DLCI contains a multiplexed DLCI record number.
4. Configuration Options Table 4-15. PVC Connection Options (4 of 4) Alternate Destination EDLCI Possible Settings: 0 – 62 Default Setting: Initially blank; no default. Specifies the alternate destination Embedded Data Link Connection Identifier (EDLCI) for a frame relay interface when a multiplexed DLCI record is selected as one end of a backup connection. Display Conditions – This option only appears when the Alternate Destination DLCI contains a multiplexed DLCI record number.
4. Configuration Options Configuring the IP Path List Select IP Path List (Static) from the Configuration Edit/Display menu to display or change the list of static path IP addresses explicitly defined in the unit. Main Menu → Configuration → IP Path List (Static) The IP Path List (Static) screen appears, showing any existing static paths. Paths discovered as SLV packets are received from other FrameSaver units are not shown.
4.
4. Configuration Options Configuring Node IP Information Select Node IP to display, add, or change the information necessary to support general IP communications for the node (see Table 4-17, Node IP Options). When deploying units to remote sites, minimally configure the Node IP Address and Subnet Mask.
4. Configuration Options Table 4-17. Node IP Options (2 of 3) Default IP Destination Possible Settings: None, Modem, COM, Ethernet, PVCname Default Setting: None Specifies an IP destination to route data that does not have a specifically defined route. Examples: If the default IP network is connected to the communications port, select COM.
4. Configuration Options Table 4-17. Node IP Options (3 of 3) TS Management Link Access Level Available Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies the highest access level allowed when accessing the unit via a Telnet or FTP session when the service provider is using the TS Access Management Link. Display Conditions – This option only appears when: Service Type on the Easy Install screen is set to Frame Relay. TS Access Management Link is set to a PVC name.
4. Configuration Options Configuring Management PVCs Select Management PVCs to define inband management links by adding or changing Management PVCs (see Table 4-18, Management PVC Options). First, DLCI records must have been configured for the interface where the Management PVC will reside. See Manually Configuring DLCI Records on page 4-64 for additional information. Main Menu → Configuration → Management and Communication → Management PVCs Select New or Mo dify to add or change Management PVCs.
4. Configuration Options Table 4-18. Management PVC Options (2 of 6) Payload Managed Possible Settings: Enable, Disable Default Setting: Disable Specifies whether the PVC is payload managed. Display Conditions – This is a read-only field set to Enabled if the PVC is IP Enabled. Enable – The network PVC created will be monitored for the presence of IP frames containing the IP address specified in the Intf IP Address field.
4. Configuration Options Table 4-18. Management PVC Options (3 of 6) Primary Link Possible Settings: Net1-FR1, Port-n, Rtr-S0, ISDN Link Name, Clear Default Setting: Initially blank; no default. Specifies the frame relay interface to use for this management PVC. The interface selected must have at least one DLCI (or DLCI with EDLCI) defined, which is not part of a PVC connection or already assigned as a management PVC.
4. Configuration Options Table 4-18. Management PVC Options (4 of 6) Primary EDLCI Possible Settings: 0 – 62 Default Setting: Initially blank; no default. Specifies the EDLCI number used for a management PVC when a multiplexed DLCI is selected. EDLCIs identify individual connections within multiplexed DLCIs that are unique to those DLCIs. Use a unique EDLCI to identify an individual connection within a multiplexed DLCI. Use 0 to identify the primary EDLCI. Use 1 – 62 to identify secondary EDLCIs.
4. Configuration Options Table 4-18. Management PVC Options (5 of 6) Alternate Link Possible Settings: Net1-FR1, Port-n, ISDN Link Name, Clear Default Setting: Initially blank; no default. Specifies the frame relay interface to use for this management PVC as the alternate link. The interface selected must have at least one DLCI (or DLCI with EDLCI) defined, which is not part of a PVC connection or already assigned as a management PVC.
4. Configuration Options Table 4-18. Management PVC Options (6 of 6) Encapsulation Possible Settings: Routed Default Setting: Routed This read-only field specifies that the IP encapsulation used is RFC 1490/RFC 2427 routed Network Level Protocol IDentifier (NLPID) encapsulation, and not SubNetwork Access Protocol (SNAP) encapsulation. Display Conditions – This option appears only if the PVC is IP Enabled or Payload Managed is enabled. Routed – IP encapsulation is routed NLPID.
4. Configuration Options 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 4-19, General SNMP Management Options). Main Menu → Configuration → Management and Communication → General SNMP Management You must have Level-1 access to display or configure these options. Table 4-19.
4. Configuration Options Table 4-19. General SNMP Management Options (2 of 2) Name 2 Access Possible Settings: Read, Read/Write Default Setting: Read Specifies the type of access allowed to the objects in the MIB. This is the type of access allowed for external SNMP managers accessing MIB objects using Community Name 2. Read – Allows read-only access (SNMP Get command). This includes all objects specified as either read-only or read/write in the MIB RFCs.
4. Configuration Options Table 4-20. Telnet and FTP Session Options (1 of 2) Telnet Session Possible Settings: Enable, Disable Default Setting: Enable Specifies whether the FrameSaver unit will respond to a session request from a Telnet client on an interconnected IP network. Enable – Allows Telnet sessions between the FrameSaver unit and Telnet client. Disable – Does not allow Telnet sessions.
4. Configuration Options Table 4-20. Telnet and FTP Session Options (2 of 2) Inactivity Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether a Telnet session is disconnected after a specified period of keyboard inactivity. Enable – Terminates the session after the Disconnect Time expires. Disable – Does not terminate Telnet session during inactivity.
4. Configuration Options Configuring SNMP NMS Security 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 4-21, SNMP NMS Security Options). 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.
4. Configuration Options Table 4-21. SNMP NMS Security Options (2 of 2) Access Type Possible Settings: Read, Read/Write Default Setting: Read Specifies the type of access allowed for an authorized NMS when IP address validation is performed. Display Conditions – This option appears for each trap manager specified in the Number of Trap Managers configuration option. Read – Allows read-only access (SNMP Get command) to the MIB objects.
4. Configuration Options Table 4-22. SNMP Traps and Trap Dial-Out Options (2 of 6) NMS n IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address that identifies the SNMP manager(s) to receive SNMP traps. Display Conditions – This option appears for each trap manager specified in the Number of Trap Managers configuration option. 001.000.000.000 – 223.255.255.255 – Adds to or changes the IP address for the trap manager.
4. Configuration Options Table 4-22. SNMP Traps and Trap Dial-Out Options (3 of 6) Enterprise Specific Traps Possible Settings: Enable, Disable Default Setting: Enable Determines whether trap messages for enterpriseSpecific events are sent to the currently configured trap manager(s). Enable – Sends trap messages for enterpriseSpecific events. Disable – Does not send trap messages for enterpriseSpecific events.
4. Configuration Options Table 4-22. SNMP Traps and Trap Dial-Out Options (4 of 6) DLCI Traps on Interfaces – Interface Selection Field Possible Settings: Network, Ports, DBM, All, None Default Setting: All Specifies which interfaces will generate linkUp and linkDown trap messages for individual DLCIs. These traps are only supported on the frame relay interfaces. Network – Generates these trap messages on DLCIs for the network interface only.
4. Configuration Options Table 4-22. SNMP Traps and Trap Dial-Out Options (5 of 6) 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.
4. Configuration Options Table 4-22. SNMP Traps and Trap Dial-Out Options (6 of 6) 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.
4. Configuration Options Configuring Ethernet Management For the FrameSaver SLV 9126-II or 9128-II, select Ethernet Management from the Management and Communication menu, or Ethernet Management Options Screen from the Easy Install screen, to configure the Ethernet port (see Table 4-23, Ethernet Management Options). Main Menu → Configuration → Management and Communication → Ethernet Management Main Menu → Easy Install → Ethernet Management Options Screen Table 4-23.
4. Configuration Options Table 4-23. Ethernet Management Options (2 of 2) Default Gateway Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address for the port’s default gateway. It is used for packets that do not have a route. 001.000.000.000 – 223.255.255.255 – Shows the IP address for the port, which can be viewed or edited (i.e., a router on the LAN). Clear – Fills the default gateway’s IP address with zeros.
4. Configuration Options Configuring the Communication Port Select Communication Port from the Management and Communication menu to display or change the communication port configuration options (see Table 4-24, Communication Port Options). Main Menu → Configuration → Management and Communication → Communication Port Table 4-24. Communication Port Options (1 of 5) Port Use Possible Settings: Terminal, Net Link, Modem PassThru Default Setting: Terminal Assigns a specific use to the COM port.
4. Configuration Options Table 4-24. Communication Port Options (2 of 5) Parity Possible Settings: None, Even, Odd Default Setting: None Provides a method of checking the accuracy of binary numbers for the COM port. A parity bit is added to the data to make the “1” bits of each character add up to either an odd or even number. Each character of transmitted data is approved as error-free if the “1” bits add up to an odd or even number as specified by this configuration option. None – Provides no parity.
4. Configuration Options Table 4-24. Communication Port Options (3 of 5) Port Access Level Possible Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies level of user access privilege for an asynchronous terminal connected to the COM port. If a login is required for the port, the effective access level is determined by the user’s access level. When a login is not required, the effective access level is determined by this option.
4. Configuration Options Table 4-24. Communication Port Options (4 of 5) IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies a unique IP address for accessing the unit via the COM port. 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. 001.000.000.000 – 223.255.255.
4. Configuration Options Table 4-24. Communication Port Options (5 of 5) 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.
4. Configuration Options Table 4-25. Modem Port Options (2 of 4) Login Required Possible Settings: Enable, Disable Default Setting: Disable Determines whether a user ID and password (referred to as the login) is required in order to log on to the asynchronous terminal connected to the modem port. Display Conditions – This option only appears when Port Use is set to Terminal. Enable – Requires a login to access the menu-driven user interface. Disable – Does not require a login.
4. Configuration Options Table 4-25. Modem Port Options (3 of 4) Disconnect Time (Minutes) Possible Settings: 1 – 60 Default Setting: 10 Determines the amount of lapsed time before disconnecting a user session in minutes. Display Conditions – This option only appears when: Port Use is set to Terminal. Inactivity Timeout is set to Enable. 1 – 60 – Sets the number of minutes allowed before the modem disconnects. IP Address Possible Settings: 001.000.000.000 – 223.255.255.
4. Configuration Options Table 4-25. Modem Port Options (4 of 4) 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 modem port. If this configuration option is not configured (i.e., it is zero), the modem port’s primary IP address is used when the alternate telephone directory is used for dial-out traps. Display Conditions – This option only appears when Port Use is set to Net Link. 001.000.
4. Configuration Options Configuring the Criteria for Automatic Backup For units with an ISDN DBM, follow this menu selection sequence to specify whether and when automatic backup is allowed, and to configure timers that will control and terminate backup, or set delays (see Table 4-26, Auto Backup Criteria Options). Main Menu → Configuration → Auto Backup Criteria Table 4-26.
4. Configuration Options Table 4-26. Auto Backup Criteria Options (2 of 2) When Auto Backup Allowed Possible Settings: Always, Restrict Default Setting: Always Determines when backup for the access unit is allowed to occur. Always – No restrictions on backup. Restrict – Backup is restricted to the day and time selected in the following configuration options. Use this selection when the importance of the data that you are backing up is day/time dependent.
4.
Configuring the FrameSaver SLV Router 5 This chapter includes the following: FrameSaver SLV Router Overview on page 5-2 IP Routing on page 5-3 Address Resolution Protocol on page 5-3 Proxy ARP on page 5-3 Interface Configuration on page 5-4 — IP Options Processing — Applications Supported by NAT — NAT Configuration Example Network Address Port Translation on page 5-8 — NAPT Configuration Example — NAT and NAPT Configuration Example Dynamic Host Configuration Protocol Server on page 5-11
5. Configuring the FrameSaver SLV Router FrameSaver SLV Router Overview The FrameSaver SLV Router supports locally attached hosts or subnets and various customer premises distribution networks that contain IP forwarding devices or routers. The router is shipped as an 802.1d bridge, and it can be configured to simultaneously support IP routing and bridging of all non-IP protocols. The router maintains two routing tables to keep customer data and management data separate.
5. Configuring the FrameSaver SLV Router IP Routing The router uses destination-based routing. IP routing tables are maintained for both the customer data and management data domains to specify how IP datagrams are forwarded. The router can support up to 32 entries in the data IP routing table, and up to 300 entries for the management IP routing table. When an IP address and subnet mask are assigned to an interface, an entry is automatically created in the IP routing table.
5. Configuring the FrameSaver SLV Router Interface Configuration The following examples require that IP addresses have been assigned to the Ethernet and Serial interfaces, and that a passthrough PVC connection exists to Rtr-S0. Optionally you might also disable bridging. In the following example, the Serial 0 sub-interface is shown as x. The valid range is 0–4,294,967,295. Procedure To set up the router’s interfaces: 1.
5. Configuring the FrameSaver SLV Router Network Address Translation Network Address Translation (NAT) is used when a private network’s internal IP addresses cannot be used outside the private network. IP addresses may be restricted for privacy reasons, or they may not be valid public IP addresses. The router provides NAT as described in RFC 1631, The IP Network Address Translator (NAT).
5. Configuring the FrameSaver SLV Router NAT Configuration Example NAT Example Server Public Network Public IP Addresses 10.1.3.1 10.1.1.1 FrameSaver SLV Router 02-17297 In this NAT example: 5-6 NAT is used for one-to-one mapping of addresses. The Ethernet interface is in the private address space and the network interface is in public address space. With NAT enabled, a single global PVC is used to access the public network.
5. Configuring the FrameSaver SLV Router Procedure To set up NAT: 1. From the Main Menu screen, press Ctrl-a then Shift-r to access the router’s Command Line Interface. Enter the following commands: en config ip nat ip nat ip nat ip nat t inside inside inside inside source source source source static static static static 10.1.3.2 10.1.3.3 10.1.3.4 10.1.3.5 192.128.22.28 192.128.22.29 192.128.22.30 192.128.22.31 2.
5. Configuring the FrameSaver SLV Router Network Address Port Translation Network Address Port Translation (NAPT) allows multiple clients in a local network to simultaneously access remote networks using a single IP address. This benefits telecommuters and SOHO (Small Office/Home Office) users that have multiple clients in an office running TCP/UDP applications. NAPT is sometimes referred to as PAT (Port Address Translation).
5. Configuring the FrameSaver SLV Router Procedure To set up NAPT: 1. From the Main Menu screen, press Ctrl-a then Shift-r to access the router’s Command Line Interface. 2. Set up an access list. The following command specifies a list that includes addresses 10.1.3.1 through 10.1.3.254: access-list 1 permit 10.1.3.0 0.0.0.255 3. Enable NAPT.
5. Configuring the FrameSaver SLV Router NAT and NAPT Configuration Example The router can be configured for NAT and NAPT simultaneously. NAT and NAPT Example Server Public Network Public IP Addresses 10.1.3.1 10.1.1.1 FrameSaver SLV Router 02-17299 In this NAT and NAPT example: Multiple workstations in the private address space can use NAPT, and the server in the private address space can use NAT.
5. Configuring the FrameSaver SLV Router Dynamic Host Configuration Protocol Server The router provides a Dynamic Host Configuration Protocol (DHCP) Server feature as specified in RFC 2131, Dynamic Host Configuration Protocol, and RFC 2132, DHCP Option and BOOTP Vendor Extensions. DHCP is the protocol used for automatic IP address assignment. DHCP setup considerations: 9128-A2-GB20-80 The range of IP addresses to be used by the DHCP server must be configured.
5. Configuring the FrameSaver SLV Router DHCP Server with NAT Configuration Example NAT with DHCP Server FrameSaver SLV Router Public Network Public IP Addresses NAT Private IP Address DHCP Pool Ethernet Private Network 02-17300 In this DHCP Server with NAT example: The clients are using dynamic IP address assignment and use the Ethernet interface of the router as the next hop router (default gateway).
5. Configuring the FrameSaver SLV Router DHCP Server at Remote Site Configuration Example DHCP Server at Remote Site Customer Premises Remote Site DHCP Clients LAN DHCP Server DSL Network FrameSaver SLV Router 02-17301 In this DHCP Server at the remote site example: The DHCP clients send IP address requests to the specified DHCP server. The router is the DHCP server and provides IP addresses to DHCP clients on the local Ethernet segment.
5. Configuring the FrameSaver SLV Router Router Security The router offers security via the following: Filtering can be enabled or disabled for inbound and/or outbound traffic: — Ethertype — ICMP Message Type, Code — IP Protocol Type: TCP, UDP, or ICMP — TCP/UDP Ports — IP Source/Destination IP Address Always enabled: — Land Bug Prevention — Smurf Attack Prevention IP Router Filtering Router filtering does not apply when the router is in bridge-only mode.
5. Configuring the FrameSaver SLV Router IP Filtering When NAT is enabled and the IP filters are active, filtering is done on the Ethernet port: upstream first, then downstream. Upstream: From the client to the server Downstream: From the server to the client Land Bug Prevention The router drops all packets received on a network PVC interface or the Ethernet interface when the Source IP address is the same as the Destination IP address.
5. Configuring the FrameSaver SLV Router Configuring the Router Using Terminal Emulation The CLI is available via a Telnet session or a direct connection over the router’s COM port to a VT100-compatible terminal or a PC running a terminal emulation program. You access the CLI through the router’s menu-driven user interface. From the Main Menu, press Shift-r to access the CLI. Verify the required terminal settings: Data rate is set to 19.2 Kbps (19200 bps). Character length is set to 8.
Security and Logins 6 This chapter includes the following: Limiting Access on page 6-2 Controlling Asynchronous Terminal Access on page 6-2 Limiting Dial-In Access via the Modem Port on page 6-4 Controlling ISDN Access on page 6-5 — ISDN Call Security — Disabling ISDN Access Controlling Telnet or FTP Access on page 6-6 — Limiting Telnet Access — Limiting FTP Access — Limiting Telnet or FTP Access Over the TS Access Management Link Controlling SNMP Access on page 6-9 — Disabling SNMP Acces
6. Security and Logins Limiting Access The FrameSaver unit provides access security on the following interfaces: Asynchronous terminal Telnet FTP 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.
6. Security and Logins Procedure To limit asynchronous terminal access to the menu-driven user interface: 1. Select the appropriate port options. Main Menu → Configuration → Management and Communication → Communication Port Main Menu → Configuration → Management and Communication → Modem 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.
6. Security and Logins Limiting Dial-In Access via the Modem Port The modem port is already configured for dial-in and asynchronous terminal access; these are the default settings. To limit dial-in access via the modem port, disable the Dial-In Access configuration option. Main Menu → Configuration → Management and Communication → Modem Port See Configuring the Modem Port in Chapter 4, Configuration Options, for more information about modem port options.
6. Security and Logins Controlling ISDN Access FrameSaver units with the built-in DBM limit access through the following methods: ISDN Call Security Disabling ISDN Access ISDN Call Security The FrameSaver unit uses the Caller Identification Method to screen calls and avoid accidental or intentional disruption of network traffic. The answering DBM only accepts calls with valid calling number identifiers or phone numbers.
6. Security and Logins Controlling Telnet or FTP Access The FrameSaver unit provides several methods for limiting access via a Telnet or FTP session. Telnet or FTP access can be on a standard management link or on a service provider’s troubleshooting (TS) management link. Limiting Telnet Access Telnet access can be limited by: Disabling Telnet access completely. Requiring a login for Telnet sessions that are not on the TS Access Management Link. Assigning an access level for Telnet sessions.
6. Security and Logins Limiting FTP Access FTP access can be limited by: Disabling FTP access completely. Requiring a user ID and password to login. Limiting FTP bandwidth. Procedure To limit FTP access when the session is not on the TS Access 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 . . .
6. Security and Logins Limiting Telnet or FTP Access Over the TS Access Management Link Procedure To limit Telnet or FTP access when the session is on the TS Access 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 .
6. 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: Disabling SNMP access. Assigning SNMP community names and the access type. 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.
6. 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: Assigning the SNMP community names that are allowed to access the FrameSaver unit’s Management Information Base (MIB). 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.
6. Security and Logins Limiting SNMP Access Through IP Addresses An additional level of security is provided by: Limiting the IP addresses of NMSs that can access the FrameSaver unit. Performing validation checks on the IP address of SNMP management systems attempting to access the FrameSaver unit. Specifying the access allowed for the authorized NMS when IP address validation is performed.
6. Security and Logins Creating a Login A login is required if security is enabled. Security is enabled by the configuration options Login Required for the communication port, modem port, and Telnet Login Required or FTP Login Required for a Telnet or FTP Session. 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.
6. Security and Logins 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 lete. 4. Save your deletion.
6. Security and Logins Controlling Router CLI Access The FrameSaver SLV 9126-II Router can be managed from an NMS using SNMP, or from the router’s command line interface (CLI). There are two methods to access the command line interface: Local access at the router through the COM port, or Access via a Telnet session. Telnet access defaults to Administrator level. If the current login is at the Operator level, only Operator level access is available for the session. Telnet access is always enabled.
6. Security and Logins Changing Access Levels The Operator and Administrator have the same Login ID with different passwords for their access level. To determine the level of access for a session, refer to Access Levels (Command Modes) on page 6-14. After accessing the router’s CLI: You can access the Administrator access level by entering: enable The router’s defaults to no password required.
6.
Operation and Maintenance 7 This chapter includes the following: Displaying System Information on page 7-3 Viewing LEDs and Control Leads on page 7-4 — FrameSaver SLV 9126 LEDs and Control Leads — FrameSaver SLV 9128-II LEDs and Control Leads — LED Descriptions — Control Lead Descriptions Device Messages on page 7-12 Status Information on page 7-18 — System and Test Status Messages — Network LMI-Reported DLCIs Status — IP Path Connection Status — PVC Connection Status — Time Slot Assignment Sta
7.
7. 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.
7. Operation and Maintenance View this field . . . To find the . . . ISDN DBM Card Type The type of dial backup module installed, ISDN-BRI or ISDN-PRI, if applicable. Software Revision If an unsupported DBM is installed, Unsupport displays. If the DBM has failed, Failed displays. Software version currently being used by the FrameSaver unit’s DBM. Format nn.nn.nn consists of a 6-digit number that represents the major and minor revision levels.
7. Operation and Maintenance FrameSaver SLV 9126 LEDs and Control Leads The FrameSaver SLV 9126-A1 unit’s faceplate includes LEDs (light-emitting diodes) that provide status on the FrameSaver unit, its network interface, DSX-1 interface, and DTE interface.
7.
7. Operation and Maintenance FrameSaver SLV 9128-II LEDs and Control Leads The FrameSaver SLV 9128-II faceplate includes 12 LEDs ( light-emitting diodes) that provide status on the FrameSaver unit, its network interface, DSX/PRI, and DTE interface. The FrameSaver SLV 9128-II, with an Ethernet port, faceplate is shown below.
7. Operation and Maintenance LED Descriptions Table 7-1, General Status LEDs, identifies the alarms that cause the Alarm LED to light. See Table 7-2, Network, DSX, or PRI Interface LEDs, for network, DSX-1, and PRI interface LED information, Table 7-3, User Data Port LED (CSU/DSUs Only), for user data port interface LED information, and Table 7-4, Ethernet Port LED (Routers Only) for Ethernet interface LED information. Table 7-1.
7. Operation and Maintenance Table 7-1. General Status LEDs (2 of 2) Label Indiction Color What It Means ALM Operational Alarm (Fail) Red ON – FrameSaver unit has just been reset, or an error or fault has been detected. (cont'd) Alarms appear on the System and Test Status screen. See Table 7-8, Health and Status Messages, for additional information. OFF – No failures have been detected.
7. Operation and Maintenance Table 7-2. Network, DSX, or PRI Interface LEDs Label Indication Color What It Means SIG Signal Green ON – A recoverable signal is present on the Network/DSX/PRI interface. OFF – The signal cannot be recovered from the Network/DSX/PRI interface. An LOS condition exists. OOF Out of Frame Yellow ON – At least one OOF was detected during the sampling period. OFF – No OOFs were detected during the sampling period.
7. Operation and Maintenance Control Lead Descriptions See Table 7-2, Network, DSX, or PRI Interface LEDs, for descriptions of these leads. See Table 7-3, User Data Port LED (CSU/DSUs Only), to interpret the user data port OK control lead. The LED descriptions and control lead descriptions are the same. In addition to these LEDs, additional control leads can be monitored through the Display LEDs and Control Leads screen.
7. 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 7-6. 7-12 Device Messages (1 of 6) 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. Allow test to continue. Select another test. Stop the test.
7. Operation and Maintenance Table 7-6. Device Messages (2 of 6) Message What It Indicates What To Do Duplicate DLCI Number DLCI number entered is not unique for the frame relay link. No action needed; previous contents of the DLCI number field is restored. File Transfer Complete A file transfer was performed successfully. Switch to the newly downloaded software. (Seen at an FTP terminal.) File Transfer Failed – Invalid file (Seen at an FTP terminal.) See Changing Software on page 7-79.
7. Operation and Maintenance Table 7-6. Device Messages (3 of 6) Message What It Indicates What To Do Invalid Password Login is required and an incorrect password was entered; access is denied. Invalid Test Combination Limit of six Login IDs reached Limit of Mgmt PVCs reached Limit of PVC Connections reached 7-14 A conflicting loopback or pattern test was in progress when Start was selected to start another test, or was active on the same or another interface when Start was selected.
7. Operation and Maintenance Table 7-6. Device Messages (4 of 6) Message What It Indicates What To Do No DLCIs Available for Mgmt PVC New was selected from the Management PVCs option screen, but all configured DLCIs have been connected. Configure more network and/or Port-1 DLCIs and try again. No DLCIs Defined DLCI Records was selected from an interface’s Configuration Edit/Display menu, and no DLCI Records have been created for this interface. Select New and create a DLCI record.
7. Operation and Maintenance Table 7-6. Device Messages (5 of 6) Message What It Indicates What To Do Please Wait Command takes longer than 5 seconds. Wait until message clears. Port Inactive The port is disabled, or it supports synchronous data when a DTE Loopback was started. No action is needed. Resetting Device, Please Wait ... Yes (or y) was entered in the Reset COM Port usage field of the System Paused menu. No action needed.
7. Operation and Maintenance Table 7-6. 9128-A2-GB20-80 Device Messages (6 of 6) Message What It Indicates What To Do Value Out of Range CIR entered for the DLCI is a number greater than the maximum allowed. Enter a valid CIR (0 – 64000). Excess Burst Size entered for the DLCI is a number greater than the maximum allowed. Enter a valid Excess Burst Size (0 – 1536000). DLCI Number entered is less than 16 or greater than 1007. Enter a valid number (16 – 1007).
7. Operation and Maintenance Status Information Status information is useful when monitoring the FrameSaver unit. The following illustration shows the Status menu for a FrameSaver SLV 9128-II with the ISDN DBM feature installed.
7. Operation and Maintenance System and Test Status Messages System and test status information is selected from the Status menu.
7. Operation and Maintenance Health and Status Messages The following table provides Health and Status messages that apply to the FrameSaver unit. Table 7-8. Health and Status Messages (1 of 7) Message What It Indicates AIS at DSX-1 An Alarm Indication Signal (AIS) is received by the DSX-1 interface. AIS is an unframed, all ones signal. AIS at ISDN PRI (Active/Idle) An Alarm Indication Signal (AIS) is received by the ISDN PRI interface. AIS is an unframed, all ones signal.
7. Operation and Maintenance Table 7-8. Health and Status Messages (2 of 7) Message What It Indicates DBM Download Required A download attempt was interrupted and failed to complete. (ISDN BRI DBM only) The NAM software and DBM software are incompatible. DCLB Active, [Interface] A V.54 Loopback is active on the specified interface. DLCI nnnn Down, frame relay link 1,2 The DLCI for the specified frame relay link is down.
7. Operation and Maintenance Table 7-8. Health and Status Messages (3 of 7) Message What It Indicates ISDN Link Profile Disabled ISDN Link Name An ISDN backup call could not be made because the ISDN link profile specified Link Name is disabled (Main Menu → Configuration → ISDN → Link Profiles). ISDN Link Profile Invalid, ISDN Link Name No phone numbers have been specified in the ISDN link profile (specified by ISDN Link Name).
7. Operation and Maintenance Table 7-8. Health and Status Messages (4 of 7) Message What It Indicates LOS at ISDN PRI (Active/Idle) A Loss of Signal (LOS) condition is detected on the ISDN PRI interface. Clears when the ratio of ones to zeros received is greater than or equal to 12.5%. (ISDN PRI DBM only) Active – Backup call was in progress. Idle – DBM was in Idle mode. Only appears when a dial backup module (DBM) is installed.
7. Operation and Maintenance Table 7-8. Health and Status Messages (5 of 7) Message What It Indicates OOF at ISDN PRI (Active/Idle) An Out of Frame (OOF) condition is detected on the ISDN PRI interface. An OOF is declared when two out of four frame synchronization bits are in error. (ISDN PRI DBM only) Active – Backup call was in progress. Idle – DBM was in Idle mode.
7. Operation and Maintenance Table 7-8. Health and Status Messages (6 of 7) Message What It Indicates RLB Active, [Interface] A network Repeater Loopback (RLB) is active on the specified interface. Secondary Clock Failed A failure of the secondary clock source configured for the unit is detected and the internal clock is providing the timing for the unit. The clock source will not automatically switch from internal until the primary clock source returns.
7. Operation and Maintenance Table 7-8. Health and Status Messages (7 of 7) Message What It Indicates Timeslot Discovery in Progress, Network 1 Time slot discovery is currently taking place to determine the time slots that will be used for frame relay traffic on the network interface.
7. 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 8, Troubleshooting, for more information on tests, including how to start and stop them. Table 7-9. Test Status Messages (1 of 2) Message What It Indicates DCLB Active, frame_relay_link 1 or A Data Channel V.54 Loopback (DCLB) is active on the specified frame relay link, or Port-2.
7. Operation and Maintenance Table 7-9. Test Status Messages (2 of 2) Message What It Indicates Monitor Pttn Active, Interface 2 A Monitor Pattern test is active on the specified interface. This test cannot be activated on user data ports that have Port Use set to Frame Relay. Network Initiated ISDN BRI Test Active An ISDN test has been started by the ISDN BRI network and it is currently active.
7. 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.
7. Operation and Maintenance Table 7-10. 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).
7. Operation and Maintenance IP Path Connection Status IP Path Connection Status is selected from the Status menu. Main Menu → Status → IP Path Connection Status The IP Path Connection Status screen displays the IP Path List, a list of devices that can be reached by their IP addresses for Service Level Management purposes.
7. Operation and Maintenance Table 7-11. IP Path Connection Status Field Status What It Indicates DLCI 16 through 1007 The IP Enabled DLCI. Device Name Up to 20 ASCII characters The name of the device configured using the System Information screen of the Control branch, or Unknown if the device is not a FrameSaver. IP Address 000.000.000.001 – 255.255.255.255 The IP address of the unit at the far end of the path. Status The status of the path: Active Inactive The path is operational.
7. Operation and Maintenance PVC Connection Status PVC connection statuses are selected from the Status menu. Main Menu → Status → PVC Connection Status The PVC Connection Status screen shows all PVC connections and management links configured for the unit. The source and primary destination are shown, along with an alternate destination for backup. When a primary destination DLCI was assigned to a Backup Group, the Backup Group designation appears next to the DLCI number.
7. Operation and Maintenance Table 7-12. PVC Connection Status (1 of 2) Field Status Link DLCI What It Indicates Identifies the cross-connection of DLCIs configured for the unit. Net1-FR1 Port-1, or Port-2 Mgmt PVCName 16 to 1007 For standard DLCIs.
7. Operation and Maintenance Table 7-12. PVC Connection Status (2 of 2) Field Status Status What It Indicates Identifies whether the physical interfaces, LMIs, and DLCIs are all enabled and active for this PVC connection. Active * The PVC is currently active. Inactive The PVC is inactive because: – Alarm conditions and network and SLV communication status indicate that data cannot be successfully passed.
7. Operation and Maintenance Time Slot Assignment Status Time slot assignments are made using the Time Slot Assignment configuration option. See Assigning Time Slots/Cross Connections in Chapter 4, Configuration Options, for making time slot assignments. Use the Timeslot Assignment Status screen to display time slot assignments for the network channels and the DSX-1 channels.
7. Operation and Maintenance The following information is available for network interface time slots (N01– N24). The Cross Connect Status Field (bottom) . . . Indicates . . . Unassgn The time slot is unassigned. FrameRly1 The time slot is assigned to the network frame relay link. Port-2 The synchronous data port (Port-2) is assigned to the network interface time slot (01 to 24). D s-p/tt The DSX-1 time slot tt is assigned to the network interface time slot (01 to 24).
7. Operation and Maintenance The following information is available for DSX-1 interface time slots (D01– D24): The Cross Connect Status Field (bottom) . . . Indicates the . . . blank The time slot is unassigned. Net1/tt Network interface 1, time slot (tt) is assigned to DSX-1 time slot (01 to 24) using Clear Channel. Net1/tt r Network interface 1, time slot (tt) is assigned to DSX-1 time slot (01 to 24) using Robbed Bit Signaling (r).
7. Operation and Maintenance Table 7-13. DBM Interface Status (1 of 3) Field Status Line Status What It Indicates The overall status of the ISDN line. Active Disabled The ISDN line is active and no error conditions exist. The ISDN interface has been disabled. Main Menu → Configuration → ISDN → Physical Inactive Invalid SPID Invalid Local Number Call Rejected – Invalid ID: Caller ID The ISDN line is disconnected or an ISDN network alarm condition exists.
7. Operation and Maintenance Table 7-13. DBM Interface Status (2 of 3) Field Status Line Status Call Rejected – ISDN Link Name: Disabled (continued) What It Indicates The incoming call was rejected because the enabled ISDN Link Name associated with the incoming Caller1 ID or local phone number was disabled. The ISDN Link Name associated with the incoming call is displayed. Link ISDN Link Name The selected ISDN backup link for which status will be displayed.
7. Operation and Maintenance Table 7-13. DBM Interface Status (3 of 3) Field Status Call Status Connected – Outbound Call 1 (continued) Most Recent Cause Value 3 An outbound call has been placed and is actively connected and available for data transfer on the selected multilink constituent link (when the Most Recent Cause Value is Call Awarded and Being Delivered In Est Chnl-7). Refer to Table 7-14, Most Recent and Previous Cause Value Messages, for additional information.
7. Operation and Maintenance Most Recent and Previous Cause Value Messages The following Cause Value Messages are presented in alphabetical order. The Cause Number is also provided if you need to convert the message to its corresponding ITU number for your service provider. Table 7-14. Most Recent and Previous Cause Value Messages (1 of 6) Message 7-42 Cause No.
7. Operation and Maintenance Table 7-14. Most Recent and Previous Cause Value Messages (2 of 6) Message Cause No. What It Indicates What To Do Facility Rejected 29 Requested facility is not provided by the network. No action is needed. Incoming Calls Barred 54 Called user is not permitted to accept the call. Turn off network call screening. Incompatible Destination 88 Request to establish a call has been received, but low-layer, high-layer, or another compatibility attribute (e.g.
7. Operation and Maintenance Table 7-14. Most Recent and Previous Cause Value Messages (3 of 6) Message Cause No. What It Indicates What To Do Invalid Transit Network Selection 91 Incorrect format of transit network identification. Contact your service representative. Mandatory Information Element Missing 96 Required data is missing from a mandatory information element. Contact your service representative.
7. Operation and Maintenance Table 7-14. Most Recent and Previous Cause Value Messages (4 of 6) Message Normal Call Clearing Cause No. What It Indicates What To Do 16 Call is being cleared because either the caller or receiver has requested that it be cleared. No action is needed. Remote user has sent a release message to the network. No action is needed. Normal, Unspecified 31 No other cause in the normal class applies for this normal event.
7. Operation and Maintenance Table 7-14. Most Recent and Previous Cause Value Messages (5 of 6) Message Cause No. What It Indicates What To Do Requested Channel Not Available 44 Circuit or channel requested cannot be provided by the other side of the interface. Allow the DBM to automatically call using the alternate link if Auto Backup is enabled, or manually select an alternate path for the call. Requested Facility Not Implemented 69 Supplemental service requested is not supported by this device.
7. Operation and Maintenance Table 7-14. Most Recent and Previous Cause Value Messages (6 of 6) Message Cause No. What It Indicates What To Do Unallocated Number 1 Destination requested cannot be reached because the Inbound Calling ID number is not assigned or allocated. Assign the Inbound Calling ID. User Access Information Discarded 43 Network was unable to deliver the access information when trying to establish the call. No action is needed.
7. Operation and Maintenance IP Routing Table The IP Routing Table shows all the routes configured in the FrameSaver unit. Main Menu → Status → IP Routing Table IP Routing Table Screen Example main/status/ip_route Device Name: Node A 9128-II 5/26/2000 23:32 Page 1 of 2 IP ROUTING TABLE Destination Mask Gateway Hop Type Interface TTL 135.001.001.000 135.001.002.111 135.001.220.000 135.001.221.000 135.001.220.000 135.001.222.111 135.001.222.113 135.001.002.111 135.001.002.111 135.001.002.111 255.
7. Operation and Maintenance Table 7-15. IP Routing Table Values (2 of 2) Column What It Indicates Type The method used to add the route to the table. RIP: The route was discovered through Routing Information Protocol. The route remains until its TTL (Time to Live) expires, a better route is provided via RIP, or there is a power reset. Loc: The route was added due to the FrameSaver unit’s local configuration; a Default IP Address or an SNMP Manager Initial Route Destination have been configured.
7. 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.
7. 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.
7. 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 or IP Enabled. Information displayed on the SLV Performance Statistics screen depends on DLCI type.
7. Operation and Maintenance Table 7-16. SLV Performance Statistics for Multiplexed DLCI (2 of 3) Statistic What It Indicates Inbound Dropped Frames * Total number of frames 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.
7. Operation and Maintenance Table 7-16. SLV Performance Statistics for Multiplexed DLCI (3 of 3) Statistic What It Indicates Latest RdTrip Latency Current round trip latency, measured in milliseconds, between the FrameSaver unit and the device at the other end of the multiplexed DLCI connection. “--” appears if communication with the far-end device is not successful.
7. Operation and Maintenance For an IP Enabled DLCI, statistics are shown for last, minimum, average, and maximum round trips, and for dropped SLV responses, for each of the seven classes of service. Table 7-17. SLV Performance Statistics for IP Enabled DLCI (1 of 2) Statistic What It Indicates Far End IP Addr IP Address of the device at the other end of the DLCI connection.
7. Operation and Maintenance Table 7-17. SLV Performance Statistics for IP Enabled DLCI (2 of 2) Statistic What It Indicates Avg RdTrip Average round trip latency between the FrameSaver unit and the device at the other end of the DLCI connection. Average round trip latency is measured every SLV sampling interval and the average is computed (using packets with the configured SLV Packet Size (bytes), Table 4-4, Service Level Verification Options) over the previous 15 samples.
7. Operation and Maintenance DLCI Performance Statistics These statistics appear when DLCI is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → DLCI Table 7-18. DLCI Performance Statistics (1 of 2) Statistic What It Indicates DLCI Up Since * Date and time that the DLCI was last declared Active after a period of inactivity. Down is displayed if the DLCI is inactive. If the DLCI was Down, this is the time that the DLCI recovered.
7. Operation and Maintenance Table 7-18. DLCI Performance Statistics (2 of 2) Statistic What It Indicates Total Rx Frames/ Rx Octets Total number of data frames and octets (8-bit bytes) received for the selected DLCI on the frame relay link. Within CIR Between CIR&EIR Above EIR With DE Set With BECN Set The number of frames and octets received on the selected DLCI of the frame relay link that were within the committed information rate.
7. Operation and Maintenance Additional Performance Statistics for IP Enabled DLCI If the selected DLCI is IP Enabled, the DLCI Performance Statistics screen has a second page listing statistics by Class of Service. On the first DLCI Performance Statistics page for an IP Enabled DLCI, PgUp and PgDn are shown as available commands in the function keys area of the screen. Select PgUp or PgDn to display the second page. Table 7-19.
7. 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.
7. Operation and Maintenance Table 7-20. Frame Relay Performance Statistics (2 of 4) Statistic What It Indicates Frame Relay Errors Total Errors The number of total frame relay errors, excluding LMI errors. Short frames, long frames, invalid DLCIs, unknown DLCIs, and unknown errors are included in this total. Indicates that there may be a non-frame relay device on the other end of the link, or the units at either the far end or both ends of the link may be configured incorrectly.
7. Operation and Maintenance Table 7-20. Frame Relay Performance Statistics (3 of 4) Statistic What It Indicates Frame Relay LMI LMI Protocol The LMI protocol configured for the frame relay link. Normal condition. Status Msg Received The number of LMI status messages received over the interface. Normal condition. Total LMI Errors The number of LMI errors. Reliability errors, protocol errors, unknown report types, unknown information elements, and sequence errors are included in this total.
7. Operation and Maintenance Table 7-20. Frame Relay Performance Statistics (4 of 4) Statistic What It Indicates Frame Relay HDLC Errors Rx Total Errors The number of receiver errors on the interface. The following are included in this count: Rx Total Discards Rx Total Discards Receive errors (non-octet aligned frames, frames with CRC errors, and Rx Overruns) The number of receiver discards on the interface.
7. Operation and Maintenance ESF Line Performance Statistics These statistics appear when ESF Line is selected from the Performance Statistics menu for the network interface. Main Menu → Status → Performance Statistics → ESF Line Only seven T1 network statistical intervals appear on the screen at any one time.
7.
7. Operation and Maintenance The following performance statistics are collected for ESF line conditions. Table 7-21. ESF Line Condition Performance Statistics Statistic What It Indicates Errored Seconds (ES) Any second with one or more ESF Error events. Unavailable Seconds (UAS) Any second in which service is unavailable. Begins incrementing at the onset of 10 consecutive seconds of severely errored seconds (SES), and stops incrementing after 10 consecutive seconds of no SESs.
7. Operation and Maintenance DBM Call Performance Statistics When an ISDN DBM is installed, these statistics are available for ISDN calls and call attempts. You can clear these statistics by selecting the ClrDBMStats function key, or you can clear all performance statistics for the system. Main Menu → Status → Performance Statistics → Clear All Statistics Clearing these statistics will not affect performance statistics stored in user history for the system. The statistics are only cleared locally.
7. Operation and Maintenance Ethernet Performance Statistics The following statistics appear when Ethernet is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Ethernet Table 7-23. Ethernet Performance Statistics Statistic What It Indicates Port Rate (Mbps) The operating rate as detected on the Ethernet port. One of the following may appear for this statistic: Duplex 10 Mbps or 100 Mbps – The Ethernet port is operating at this rate.
7. Operation and Maintenance Trap Event Log The Trap Event Log displays all traps stored in the SNMP trap event log. The following log example describes the alarm conditions that will generate an SNMP trap for a physical interface, and for the frame relay LMIs and DLCIs. These alarm conditions also generate Health and Status messages seen on the Health and Status Messages on page 7-20.
7. Operation and Maintenance Modem Operation This section includes the following: Activating the Modem PassThru Feature Canceling Modem PassThru Operationn Manually Disconnecting the Modem Verifying Modem Operation See Setting Up the Modem in Chapter 4, Configuration Options, for additional information. Activating the Modem PassThru Feature Access to the router’s VT100-compatible user interface is provided through the FrameSaver unit’s Modem PassThru feature, also known as Router Assist.
7. Operation and Maintenance Manually Disconnecting the Modem If Trap Disconnect is disabled, a modem connection remains until it is manually disconnected. Select Disconnect Modem from the Control menu. Main Menu → Control → Disconnect Modem Respond yes to the Are you sure? prompt. Verifying Modem Operation Procedure If Port Use is set to Terminal (dial-in access): 1. Dial the modem’s phone number using a remote VT100-compatible asynchronous terminal or PC. 2. Verify that the Main Menu appears.
7.
7. Operation and Maintenance Placing a Test Call (Nondisruptive) Use this procedure to test the ISDN path to each remote site. This procedure will not put the system into backup. Procedure 1. Make sure the ISDN Link Profiles and DLCIs are set up correctly for the DBMs at each end (see Modifying ISDN Link Profiles in Chapter 4, Configuration Options. Main Menu → Configuration → ISDN → Link Profiles Main Menu → Configuration → ISDN → DLCI Records 2. Place a Test Call from one of the devices.
7. Operation and Maintenance Verifying ISDN Lines Use either of the following methods to verify operation of the ISDN lines. Check the status of the DBM interface: Main Menu → Status → DBM Interface Status Line Status should display Active. If an invalid (Inv) status appears (e.g., Inv SPID for an ISDN BRI DBM) in the Line Status field, verify that you entered ISDN physical options correctly.
7. 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.
7. 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 6, Security and Logins), you are prompted to enter them. If not, press Enter. The FTP prompt appears. The starting directory is the root directory ( /).
7. 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 4-23, Ethernet Management Options, in Chapter 4, Configuration Options). Procedure To download software: 1.
7. Operation and Maintenance Upgrading ISDN BRI DBM Software A separate download to update PRI DBM functionality is not necessary; a PRI upgrade is incorporated in the unit’s program code. However, if the FrameSaver unit has a BRI DBM, the program code must be upgraded separately. To upgrade a FrameSaver unit’s BRI DBM program code, you must transfer the dbmprog.ocd file in the Dial Backup Module directory using the put command. Procedure To perform a BRI DBM upgrade: 1.
7. 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. If a software revision number appears, the file transfer is complete. If In Progress appears, the file is still being transferred. If Invalid appears, no download has occurred or the download was not successful.
7. 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 Transfer Rate (Kbps) option (see Table 4-20, Telnet and FTP Session Options, in Chapter 4, Configuration Options).
7. Operation and Maintenance Turning Off the System Alarm Relay For carrier-mounted FrameSaver units, an alarm system relay is provided by the 9000 Series Access Carrier. This relay activates a light or buzzer when an alarm condition is detected in one of the FrameSaver units. Once the alarm relay is connected, enabling the System Alarm Relay option activates this feature (see Table 4-5, General System Options, in Chapter 4, Configuration Options).
7.
Troubleshooting 8 This chapter includes the following: Problem Indicators on page 8-2 Resetting the Unit and Restoring Communication on page 8-3 — Resetting the Unit from the Control Menu — Resetting the Unit By Cycling the Power — Restoring Communication with an Improperly Configured Unit Troubleshooting Management Link Feature on page 8-5 LMI Packet Capture Utility Feature on page 8-5 — Viewing Captured Packets from the Menu-Driven User Interface Alarms on page 8-7 Viewing the Trap Ev
8. Troubleshooting Physical Tests on page 8-26 — Line Loopback — Payload Loopback — Repeater Loopback — DTE Loopback — Send Line Loopback — Data Channel Loopbacks on a Frame Relay Link — Send Remote Line Loopback — Send and Monitor Pattern Tests IP Ping Test on page 8-35 Lamp Test on page 8-40 Problem Indicators The unit provides a number of indicators to alert you to possible problems: Indicators . . . See . . .
8. Troubleshooting Resetting the Unit and Restoring Communication You can reset the unit in one of four ways: Reset it from the Control menu. Cycle the power. Reset the configuration options for the COM port, or reload the factory default settings. 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.
8. Troubleshooting Restoring Communication with an Improperly Configured Unit Configuring the unit improperly 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.
8. 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.
8. 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.
8. 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 8-1. Alarm Conditions (1 of 7) Alarm Condition What It Indicates What To Do AIS at DSX-1 For the DSX-1 interface, the attached DTE is transmitting an AIS.
8. Troubleshooting Table 8-1. Alarm Conditions (2 of 7) Alarm Condition What It Indicates EER at Network 1 The error rate of the received network signal exceeds the currently configured threshold. This condition only occurs if the network interface is configured for ESF framing. What To Do Verify that the network cable is securely attached at the network interface. Contact your network provider.
8. Troubleshooting Table 8-1. Alarm Conditions (3 of 7) Alarm Condition What It Indicates What To Do Link Profile Disabled, ISDN Link Name An ISDN backup call could not be made because the specified link profile was disabled. Change the ISDN Link Profile’s Link Status to Auto (Main Menu → Configuration → ISDN → Link Profiles). LMI Down, frame relay link 2 The Local Management Interface is down for the specified frame relay link.
8. Troubleshooting Table 8-1. Alarm Conditions (4 of 7) Alarm Condition What It Indicates LOS at DSX-1 A Loss of Signal (LOS) condition is detected on the DSX-1 interface. Clears when the ratio of ones to zeros received is greater than or equal to 12.5%. LOS at Network 1 No signal being transmitted from the DTE. Network cable problem. No signal is being transmitted at the far-end FrameSaver unit. T1 facility problem.
8. Troubleshooting Table 8-1. Alarm Conditions (5 of 7) Alarm Condition What It Indicates OOF at Network 1 An Out of Frame (OOF) condition is detected on the network interface. Incompatible framing format between the network and the FrameSaver unit. Network cabling problem. T1 facility problem. What To Do Check that the framing format for the network interface is correct. Check that the network cable is securely attached at both ends. Contact your network provider.
8. Troubleshooting Table 8-1. Alarm Conditions (6 of 7) Alarm Condition What It Indicates Secondary Clock Failed A failure of the configured secondary clock source for the unit was detected and the internal clock is providing the timing for the unit. What To Do The clock source will not automatically switch from internal until the primary clock source returns. Self-Test Failure The unit did not pass its basic verification tests when it was powered on or reset.
8. Troubleshooting Table 8-1. Alarm Conditions (7 of 7) Alarm Condition What It Indicates What To Do Suboptimal Link Rate, frame relay link 2 The specified frame relay multilink has failed to achieve the configured Maximum Link Rate for the link. No action required. This message appears for multilink aggregate frame relay links if LMI is down on any of its constituent links. Two Level-1 Users Accessing Device Another user with Level-1 security access is currently accessing the unit.
8. Troubleshooting Viewing the Trap Event Log The Trap Event Log displays all traps stored in the SNMP trap event log. ASCII trap strings used to describe trap events are provided in the tables contained in Standards Compliance for SNMP Traps (see Appendix B, SNMP MIBs and Traps, and RMON Alarm Defaults). See Trap Event Log in Chapter 7, Operation and Maintenance, for a screen example and additional information. Troubleshooting Tables The unit is designed to provide many years of trouble-free service.
8. Troubleshooting Table 8-2. Device Problems (2 of 2) Symptom Possible Cause Cannot access the unit or the menu-driven user interface. Login or password is incorrect, COM port is misconfigured, or the unit is otherwise configured so it prevents access. Failure xxxxxxxx appears at the top of the System and Test Status screen, at Self-Test Results. The unit detects an internal software failure. Solutions An LED appears dysfunctional. LED is burned out. Not receiving data.
8. Troubleshooting Frame Relay PVC Problems Table 8-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. Verify the LMI Reported DLCI field on the Interface Status screen. DTE is configured incorrectly. Check the DTE’s configuration.
8. Troubleshooting ISDN DBM Problems Table 8-4. ISDN DBM Problems Symptom Possible Cause Solutions Cannot connect to the remote unit Misconfiguration DBM LMI comes up, but no data is transferred Misconfiguration Verify that the link profiles are correct in both units, both the area codes and phone or ID numbers (see Setting Up ISDN Link Profiles in Chapter 4, Configuration Options).
8. Troubleshooting Tests Available The following tests are available to a FrameSaver SLV 9126, 9128, or 9128-II.
8. Troubleshooting Test Timeout Feature A Test Timeout feature is available to automatically terminate a test (as opposed to manually terminating a test) after it has been running a specified period of time. It is recommended that this feature be used when the FrameSaver unit is remotely managed through an inband data stream (PVC).
8. 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 on page 8-21. 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 loopback or a send-pattern test: 1. Follow this menu selection sequence: Main Menu → Test 2.
8. Troubleshooting Aborting All Tests Use the Abort All Tests selection from the Test menu to abort all tests running on all interfaces, with exception to DTE-initiated loopbacks. To abort individual tests that are active, see Starting and Stopping a Test on page 8-20. Procedure To abort all tests on all interfaces: 1. Follow this menu selection sequence: Main Menu → Test 2. Select Abort All Tests and press Enter. Command Complete appears when all tests on all interfaces have been stopped.
8. Troubleshooting PVC Tests PVC tests can be run on a requested DLCI for a selected interface. 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. 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.
8. Troubleshooting 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.
8. Troubleshooting Send Pattern This test sends packets filled with a hexadecimal 55 test pattern and sequence number over the selected interface and DLCI to another FrameSaver device. To send a pattern test on a link: Main Menu → Test → [Network PVC Tests/Data Port PVC Tests/ ISDN Call/PVC Tests] If the selected DLCI is configured as . . . Then . . . And the default Rate (Kbps) setting is . . .
8. Troubleshooting Connectivity Connectivity is a proprietary method that determines whether the FrameSaver device at the other end of the frame relay PVC is active. This test stops automatically and can only be executed for circuit multiplexed PVCs. To run a connectivity test on a link: Main Menu → Test → [Network PVC Tests/Data Port PVC Tests/ ISDN Call/PVC Tests] Selecting Connectivity sends a frame to the FrameSaver unit at the other end of the PVC.
8. Troubleshooting Physical Tests Physical tests require the participation of your network service provider. Main Menu → Test → [Network Physical Tests/Data Port Physical Tests/ DSX-1 Physical Tests/PRI Physical Tests] If the unit does not have the ISDN PRI DBM feature, PRI Physical Tests does not appear. A FrameSaver unit’s physical tests screen for the network interface is shown below.
8. Troubleshooting Line Loopback The Line Loopback (LLB) loops the information received on the selected interface back to the source of the loopback. When used with a pattern test at the remote node, LLB determines whether the problem is with the sending device or the T1 facility. Main Menu → Test → Network Physical Tests Framer Other T1 Interface LLB All 1s The T1 Interface 97-15336 CAUTION: This test may affect operation of frame relay PVCs assigned to the selected port.
8. Troubleshooting Payload Loopback The Payload Loopback (PLB) loops the information received on the selected interface back to the network after it has passed through the receive and transmit framing section of the device. Use the PLB to determine whether the problem is with the T1 facility or in the circuitry of the remote device.
8. Troubleshooting Repeater Loopback The Repeater Loopback (RLB) loops data received from the data ports and the DSX-1 interface after the signal has passed through the framing circuitry. Use RLB to ensure that all of the data is correct up to the point where it is sent over the interface. This helps to indicate that the FrameSaver unit is operational. Main Menu → Test → Network Physical Tests An attached device or test equipment should generate and monitor data to be looped back.
8. Troubleshooting DTE Loopback The DTE external Loopback (DTLB) test loops the received signal on a DTE interface back to the DTE without affecting the operation of the remaining ports. Use this test for isolating problems on the DTE interface. Main Menu → Test → Data Port Physical Tests An attached device or test equipment must generate data to be looped back.
8. Troubleshooting Send Line Loopback The remote Line Loopback (LLB) up and down codes are in-band codes that allow control of a remote device. The LLB Up code invokes a line loopback in the remote unit while the LLB Down code terminates the remote line loopback. Network loopbacks are defined in AT&T TR 62411. A remote LLB cannot be started when one of the following tests is active: Any Loopback on the same interface.
8. Troubleshooting Data Channel Loopbacks on a Frame Relay Link A network-initiated Data Channel Loopback (DCLB) loops data over the frame relay link (DS0s) received on the network interface through the FrameSaver unit’s framing circuitry and back to the same interface. A DCLB can be controlled over the frame relay link using one of the following in-band methods: V.54 Loopback. ANSI T1.403 Annex B Fractional T1 ( FT1) Channel Loopback.
8. Troubleshooting Send Remote Line Loopback The remote Line Loopback (LLB) up and down codes are in-band codes that allow control of a remote device. The LLB Up code invokes a line loopback in the remote unit while the LLB Down code terminates the remote line loopback. Network loopbacks are defined in AT&T TR 62411. A remote LLB cannot be started when one of the following tests is active: Any Loopback on the same interface.
8. Troubleshooting Send and Monitor Pattern Tests The pattern tests enable a FrameSaver unit to either send or monitor a known bit pattern. These tests generate industry-standard bit patterns that can be used to determine whether information is being correctly transmitted across a circuit.
8. Troubleshooting IP Ping Test An IP Ping test can be run to test connectivity between the FrameSaver unit and any FrameSaver unit, router, or NMS to which it has a route. Times when you might want to run an IP Ping test are: To test connectivity between the FrameSaver unit and any FrameSaver unit in the network to verify that the path is operational. Select IP Ping Test – Procedure 1 on page 8-39 to ping any far-end FrameSaver unit.
8. Troubleshooting Table 8-5. Ping Options (1 of 3) Target IP Address Possible Settings: 000.000.000.001–126.000.000.000, 128.000.000.000–223.255.255.255 Default Setting: 000.000.000.000 Specifies the IP address to which a ping will be sent. 000.000.000.001–126.000.000.000, 128.000.000.000–223.255.255.255 – Specifies the IP address.
8. Troubleshooting Table 8-5. Ping Options (2 of 3) Source IP Address Available Settings: Automatic, Special Default Setting: Automatic Specifies the source IP address to be identified with the ping. Display Conditions – This setting does not appear when Destination Interface is set to Use_Internal_Route.
8. Troubleshooting Table 8-5. Ping Options (3 of 3) Response Timeout Available Settings: 1–60 Default Setting: 2 Specifies the amount of time, in seconds, to wait before a host that has not responded to a ping is declared unreachable. 1–60 – The response timeout period. When the ping has completed normally, timed out, or been stopped using the Stop command, informational fields are displayed as shown in Table 8-6, Ping Responses. Table 8-6.
8. Troubleshooting IP Ping Test – Procedure 1 Procedure To ping any far-end FrameSaver unit: 1. Select the IP Ping test. Main Menu → Test → IP Ping 2. Enter the IP Address of the device the ping is being sent to, then select Start. NOTE: If the FrameSaver unit has just initialized, or the far-end unit has just initialized, it may take about a minute for the units to learn the routes via the proprietary RIP. 3. Verify the results of the IP Ping test. — While the test is running, In Progress...
8. Troubleshooting IP Ping Test – Procedure 2 Procedure 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.
Setting Up OpenLane for FrameSaver Devices and Activating SLM Features 9 This chapter includes: OpenLane Support of FrameSaver Devices on page 9-2 Setting Up the OpenLane SLM System on page 9-2 Setting Up FrameSaver Support on page 9-3 Ordering SLM Feature Set Activations on page 9-4 — To Find Your License Key Number — The Activation Certificate Administering and Managing SLM Activations on page 9-6 — Entering an Activation Certificate — Checking Activation Certificate Status — Scheduling Ac
9.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Setting Up FrameSaver Support With OpenLane SLM’s extensive online Help, the application is self-documenting and you have access to the most current system information. Procedure To set up FrameSaver support: 1. Start the OpenLane services, then access the application. 2. Log in as Admin for access to customer profiles, frame relay access facilities components, and PVC components. 3. Add FrameSaver devices. 4.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Ordering SLM Feature Set Activations When advanced SLM functionality is needed at a site, an Activation Certificate (Feature No.9126-C1-220 or 9128-C1-220) can be ordered, which will allow you to activate SLM features in FrameSaver devices with the diagnostic feature set. You must have the OpenLane SLM system, Release 5.3 or later, to activate SLM capability in FrameSaver devices and to manage your certificates.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features The Activation Certificate An Activation Certificate will be sent to you via Federal Express. NOTE: If you ordered an Activation Certificate via e-mail, Activation Certificate information will be e-mailed to you so you can start activating units immediately. The actual certificate will arrive the next day.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Administering and Managing SLM Activations The OpenLane SLM system provides the following features that allow you to administer and manage your Activation Certificates and SLM activations. From the Firmware/Feature Maintenance menu, you can: Add or view the status of activations, and see how many activations remain on each certificate.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Entering an Activation Certificate Once you receive an Activation Certificate, enter the Activation Certificate number into your OpenLane SLM system’s database. Procedure To enter the Activation Certificate number: 1. Open the OpenLane SLM application and provide your access level, which must be Admin. 2. Select Firmware/Feature Maintenance from the OpenLane Administration screen. 3.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Scheduling Activations You can activate one, many, or all FrameSaver devices at any time, until all the activations ordered for the certificate have been completed. NOTE: Once SLM capability is activated in a FrameSaver device, the unit cannot be returned to the diagnostic feature set. Procedure To schedule device activations: 1.
9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features Checking the Status of Scheduled Activations You can check the status of scheduled activations or cancel activations at any time prior to the activations taking place by selecting View/Abort scheduled task status from the Firmware/Feature Maintenance menu. You can select all tasks, or select tasks by model, device name, or IP address.
9.
Setting Up NetScout Manager Plus for FrameSaver Devices 10 This chapter includes NetScout Manager Plus information as it relates to FrameSaver SLV devices.
10. Setting Up NetScout Manager Plus for FrameSaver Devices Preparation 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.
10. 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: Copy the OpenLane directory to a user directory. Add frame relay agents to the NetScout Manager. Configure agent properties. Verify and correct domains and groups. Monitor the agent and DLCIs.
10. 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.
10. 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.
10. 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: An unsupported domain needs to be deleted. A missing domain needs to be added. Groups, Samples, Interval, and Logging are not configured as specified in Step 3 of Verifying Domains and Groups. Procedure 1. Select the Property... button (down the center of the Configuration Manager main window). The Property Editor window opens.
10. 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.
10. 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.
10. 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.
10. Setting Up NetScout Manager Plus for FrameSaver Devices 4. Edit any trap defaults that may be required. See Step 4 on page 10-12 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.
10. 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.
10. 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 . . .
10. 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.
10. 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 101015001 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.
10. 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.
10. 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.
10. 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).
10. 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 on page 10-17). Refer to Launching User History and Understanding Custom History Display in Using Custom History of the NetScout Manager Plus User Guide for additional information.
10. 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.
10. 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 11 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 example in FrameSaver SLV Plus At-a-Glance Report on page 11-9). To get this report, you need Network Health R4.01 or higher.
11. 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: Network Health Installation Guide to help you install the application. Network Health User Guide to help you get started using the application. Network Health Reports Guide to help you understand and use Frame Relay reports.
11. 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.
11. 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.
11. 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.
11. 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.
11. 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.
11. 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. Supplemental Report – Shows DLCI availability and latency. The information shown in this report is also on other Health reports.
11. Setting Up Network Health for FrameSaver Devices — FrameSaver SLV Plus At-a-Glance Report Performs trend analysis on up to ten specified variables for DLCIs. This is the first Network Health report to integrate the FrameSaver SLV’s unique monitoring capabilities, using the unit’s SLV-enhanced network statistics.
11. Setting Up Network Health for FrameSaver Devices 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.
Menu Hierarchy A Menus The Menu Hierarchy on the following pages shows a pictorial view of the organization of the FrameSaver CSU/DSU and Router’s screens, which can help you navigate the menus and access information. ISDN backup and Data Ports options do not apply to the router. The Virtual Router Ports option does not apply to the CSU/DSUs.
A.
A.
A.
SNMP MIBs and Traps, and RMON Alarm Defaults B This appendix contains the following: MIB Support on page B-2 Downloading MIBs and SNMP Traps on page B-2 System Group (mib-2) on page B-3 — FrameSaver Unit’s sysDescr (system 1) — FrameSaver Unit’s sysObjectID (system 2) Interfaces Group (mib-2) on page B-3 — Paradyne Indexes to the Interface Table (ifTable) — NetScout Indexes to the Interface Table (ifTable) Standards Compliance for SNMP Traps on page B-8 — Trap: warmStart — Trap: authentica
B. 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 SNMP protocol.
B. SNMP MIBs and Traps, and RMON Alarm Defaults System Group (mib-2) This section provides the system object identifier and system description for the System Group for the FrameSaver 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 unit: PARADYNE T1 FrameSaver SLV; Model: [9126/9126-II/9126-IIR/9128-II]; S/W Release: (MM.mm.bb [Major.minor.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-1.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-1.
B. 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.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-2. NetScout Interface Objects Information (2 of 2) ifName Description ifDescr (ifEntry 2) ifIndex IN – RMON (IN); [ifName of the interface] 17–48 RMON Logical Layer RMON Frame Relay Logical Interfaces These values are calculated. OUT – RMON (OUT); [ifName of the interface] For the DCE: DTE calculated value +1 RMON Virtual Interfaces These values are calculated based on the probe’s internal circuit index: circuit index +65.
B. 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.
B. 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. Variable-Binding devLastTrapString (devHealthAndStatus. mib) Reset command sent. Power disruption. String: ‘Unit reset.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Traps: linkUp and linkDown These traps are supported on the following interfaces: Network, DSX-1, and synchronous data ports – Physical sublayer interfaces 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.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings (1 of 2) Interface Variable-Bindings Possible Cause Physical Sublayer T1 Network, DSX-1, PRI (Supported by the media-specific DS1 MIB.) ifIndex (RFC 1573) ifAdminStatus (RFC 1573) linkDown – One or more alarm conditions are active on the interface. Alarm conditions include: ifOperStatus (RFC 1573) – Loss of Signal (LOS) or far-end loss of signal devLastTrapString (devHealthAndStatus.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings (2 of 2) Interface Variable-Bindings Possible Cause Physical Sublayer (continued) BRI (Supported through ifIndex – RFC 1573.) ifIndex (RFC 1573) ifAdminStatus (RFC 1573) linkDown – One or more alarm conditions are active on the interface. Strings: ‘$ifString down.’ No alarms exist on the link. ‘$ifString administratively shutdown.’ (Due to an intentional shutdown.
B. 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 3) Trap enterpriseCIRChange(15) Variable-Bindings enterpriseConfigChange(6) devFrExtDlciIfIndex (devFrExt.mib) devFrExtDlciDlci (devFrExt.mib) devFrExtDlciCIR (devFrExt.mib) Possible Cause CIR has changed due to the LMI report.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. enterprise-Specific Traps and Variable-Bindings (2 of 3) Trap enterpriseMissedSLVDown(16) Variable-Bindings enterpriseMissedSLVUp(116) devFrExtDlciIfIndex (devFrExt.mib) devFrExtDlciDlci (devFrExt.mib) devFrExtDlciMissedSLVs (devFrExt.mib) devLastTrapString (devHealthAndStatus.mib.) Possible Cause Received SLV communications have been missed; SLV Timeout Error Event Threshold has been exceeded.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. enterprise-Specific Traps and Variable-Bindings (3 of 3) Trap enterpriseSecondaryClockFail(4) Variable-Bindings devLastTrapString (devHealthAndStatus.mib) Possible Cause Operating software has detected that the secondary clock source has failed. String: ‘Secondary clock failed.’ enterpriseSecondaryClockFailClear(104) Operating software has detected that the secondary clock source is operational again. String: ‘Secondary clock restored.
B. 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 on page B-18 for the default values that will generate RMON-specific traps. Table B-8. Trap risingAlarm RMON-Specific Traps and Variable-Bindings Variable-Bindings Possible Cause Object being monitored has risen above the set threshold.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Trap: dialControl These traps indicate when an ISDN backup call is initiated or terminated, or when an outgoing call is rejected by the far end device. Table B-9. dialControl Traps (1 of 2) Trap Variable-Bindings Possible Cause Standard Dial Control MIB dialCtlPeerCallInformation dialCtlPeerCallSetup 9128-A2-GB20-80 callHistoryPeerId (RFC 2128) A peer-to-peer call has been ended.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-9. dialControl Traps (2 of 2) Trap Variable-Bindings Possible Cause Dial Control Extension MIB dialCtlPeerCallRejected callHistoryPeerId (RFC 2128) callHistoryPeerIfIndex (RFC 2128) callHistoryLogicalIfIndex (RFC 2128) A peer-to-peer call was not successful; the call was rejected by the far end. callHistoryPeerAddress (RFC 2128) devLastTrapString (devHealthAndStatus.mib) ISDN Call Profile has been disabled.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Rising Event Operation If a rising threshold is crossed during the interval shown in a table (e.g., frames dropped by the network), the event is armed and an alarm is generated at the end of the interval. Only one alarm per event per interval is generated. The alarm condition persists until the event has been disarmed (reset).
B. 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-11. Frame Relay Link Alarm Defaults (1 of 2) Item Sample Type 1 Invalid Frames D Event Type Rising Threshold Default Falling Threshold Default MIB/Tag/OID 2 Interval MIB: pdn_FrExt.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-11. Frame Relay Link Alarm Defaults (2 of 2) Item Sample Type 1 Tx Total Errors D Event Type Rising Threshold Default Falling Threshold Default MIB/Tag/OID 2 Interval MIB: pdn_FrExt.mib (E) 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 900 secs (15 mins) Rising 1 1 Tag: devFrExtLinkTotTxErrs OID: .1.3.6.1.4.1.1795.
B. 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-defined alarm area. Table B-12.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-12. DLCI Alarm Defaults – Paradyne Area (2 of 2) Item Maximum Latency Sample Type 1 MIB/Tag/OID 2 Interval A MIB: pdn_FrExt.mib (E) 60 secs (1 min) Tag: devFrExtLatencyMax Event Type Rising Threshold Default Falling Threshold Default Rising 0 0 OID: .1.3.6.1.4.1.1795.2.24.2. 6.9.4.3.1.I.D 1 D = Delta. Indicates that the calculated difference between the current value and the previous value is contained in the MIB. A = Absolute.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-13. Static DLCI Alarm Defaults – NetScout Area Rising Threshold Default Falling Threshold Default None Must be configured. 0 None Must be configured. 0 None Must be configured. 0 None Must be configured. 0 60 secs (1 min) None Must be configured. 0 MIB: FR DTE MIB (RFC 2115) 60 secs (1 min) Tag: frCircuitSentOctets None Must be configured. 0 Item Sample Type 1 MIB/Tag/OID 2 Interval Current Latency A MIB: pdn_FrExt.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. Dynamic DLCI Alarm Defaults – NetScout Area Item Rx DLCI Link Utilization Sample Type 1 MIB/Tag/OID 2 Interval D MIB: FR DTE MIB (RFC 2115) 60 secs. (1 min) 60 secs. (1 min) Tag: frCircuitReceivedOctets Rising Threshold Default Falling Threshold Default Rising 70% of link capability 65% of link capability Rising 70% of link capability 65% of link capability Event Type OID: .1.3.6.1.2.1.10.32.2.1.9.I.
B. 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 or a log event is sent. This table is helpful in identifying alarm conditions being tracked when viewing the NetScout Custom History screen (shown below), which provides the OID instead of the alarm condition.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (1 of 5) 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.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (2 of 5) Object ID (OID) 1 Item MIB/Tag Unavailable Seconds MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2. . . .1.3.6.1.4.1.1795.2.24.2.6.5.4.8.1.2.I Tag: devFreeRunUAS .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.1.4.1.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (3 of 5) 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) .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.1.1.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (4 of 5) Object ID (OID) 1 Item MIB/Tag Latency Packet Size 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.8.I.D Tag: devFrExtLatencyPacketSz .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2 . . . .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 Limit (1–5) MIB: pdn_FrExt.mib (E) Frame Size Count (1–5) MIB: pdn_FrExt.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (5 of 5) Object ID (OID) 1 Item MIB/Tag Rx Illegal Frames MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1. . . .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.18.I Tag: devFrExtLinkRxIlFrames .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.19.I Total Tx Errors MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkTotTxErrs .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.20.I Total Rx Errors MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkTotRxErrs .1.3.6.1.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-16. Alarm OID Cross-Reference (1 of 3) Object ID (OID) Item MIB/Tag Unavailable Seconds MIB: DS1/E1 MIB (RFC 1406) .1.3.6.1.2.1.10.18.9.1. . . .1.3.6.1.2.1.10.18.9.1.5.I Tag: dsx1TotalUASs .1.3.6.1.2.1.10.32.2.1. . . .1.3.6.1.2.1.10.32.2.1.4.I.D Rx FECNs MIB: FR DTE MIB (RFC 2115) 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.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-16. Alarm OID Cross-Reference (2 of 3) Object ID (OID) Item MIB/Tag Average 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.5.I.D Tag: devFrExtLatencyAvg .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.7.I.D Current Latency MIB: pdn_FrExt.mib (E) 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.
B. SNMP MIBs and Traps, and RMON Alarm Defaults Table B-16. Alarm OID Cross-Reference (3 of 3) Object ID (OID) Item MIB/Tag Tx Underruns 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.7.1.29.I Tag: devFrExtLinkTxUnderruns .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.32.I Total LMI Errors MIB: pdn_FrExt.
Router CLI Commands, Codes, and Designations C CLI Commands The FrameSaver SLV 9126-II Router is managed with text commands from the Command Line Interface (CLI). The CLI can be accessed: Locally via a PC or asynchronous terminal connected to the COM port. Remotely via a Telnet session. The conventions used in the command line syntax are shown below. Convention Meaning [] Brackets indicate an optional element. {} Braces indicate a required entry.
C.
C. Router CLI Commands, Codes, and Designations Pager Command The pager command allows you to enable or disable screen paging for a CLI session, and enter comments at the command line, which is useful when adding comments within scripts. Table C-1. Pager Command [no] pager Minimum Access Level modes: Operator Command Mode: All modes Allows you to control the flow of uninterrupted output to the screen. Information added after the ! at the command line is ignored. pager – Enables display paging.
C. Router CLI Commands, Codes, and Designations Configuration Commands Configuration control commands put the router in configuration mode and allows you to save configuration changes. To show a configuration, see Table C-13, Show Commands. Table C-3. Configuration Commands configure {terminal | factory} Minimum Access Level: Administrator Command Mode: config Causes the router to enter configuration mode. The router stays in configuration mode until the exit command is entered or the session times out.
C. Router CLI Commands, Codes, and Designations Interface Commands Interface commands allow you to configure the Ethernet and network interfaces, and their sub-interfaces. Table C-4. Interface Commands (1 of 3) interface intf-type intf-num no interface intf-type intf-num.sub-intf-num [ point-to-point] Minimum Access Level: Administrator Command Mode: config, config-if, config-subif Allows you to enter interface or sub-interface configuration mode and create sub-interfaces.
C. Router CLI Commands, Codes, and Designations Table C-4. Interface Commands (2 of 3) ip address ip-addr subnet-mask no ip address [ip-addr subnet-mask ] Minimum Access Level: Administrator Command Mode: config-if (Ethernet), config-subif (Serial) Assigns an IP address to the Ethernet interface or a Serial port sub-interface. No IP addresses are assigned to interfaces or sub-interfaces by default. Example: ip address 132.53.4.2 255.255.255.
C. Router CLI Commands, Codes, and Designations Table C-4. Interface Commands (3 of 3) [no] ip unnumbered [null 0] Minimum Access Level: Administrator Command Mode: config-subif Enables or disables IP processing on a serial sub-interface without assigning an explicit address. The no ip unnumbered command removes any IP address assigned to the interface and disables IP processing on the interface. The default is that IP processing is disabled.
C. Router CLI Commands, Codes, and Designations IP Routing Commands Internet Protocol (IP) routing commands are used to enable and disable IP routing, and to create or delete static routes in the routing table. To show IP routing and performance statistics, see Table C-13, Show Commands. Table C-5. IP Routing Commands ip route dest-ip dest-mask {next-hop-ip | intf-type intf-num [.sub-intf-num] } no ip route dest-ip dest-mask [next-hop-ip | intf-type intf-num [.
C. Router CLI Commands, Codes, and Designations Bridge Commands Bridge commands are used to enable or disable simultaneous bridging and routing, configuration of bridge groups and their attributes, and apply or remove bridge groups from an interface or sub-interface. To show the bridge database or spanning-tree topology, see Table C-13, Show Commands. Table C-6.
C. Router CLI Commands, Codes, and Designations Table C-6. Bridge Commands (2 of 2) [no] bridge-group bridge-group Minimum Access Level: Administrator Command Mode: config-if, config-subif Allows a user to apply or remove a set of bridge group parameters to/from an interface or sub-interface. When a set of bridge group parameters is applied or removed at the interface level, the command also applies to all sub-interfaces on the interface.
C. Router CLI Commands, Codes, and Designations ARP Commands Address Resolution Protocol (ARP) commands are used to create entries in the ARP table, specify how long the information will be retained, and remove dynamic entries in the table. Table C-7. ARP Commands arp ip-address mac-address arp-type no arp ip-address [mac-address arp-type ] Minimum Access Level: Administrator Command Mode: config Allows you to create or delete a single, static ARP table entry.
C. Router CLI Commands, Codes, and Designations NAT Commands Network Address Translation (NAT) commands are used to enable or disable NAT on an interface or sub-interface and specify whether IP addresses on the interface are public or private. Table C-8.
C. Router CLI Commands, Codes, and Designations Table C-8. NAT Commands (2 of 3) ip nat pool pool-name start-ip-addr end-ip-addr {netmask netmask | {prefix-length | / } prefix-length } no ip nat pool pool-name [start-ip-addr end-ip-addr {netmask netmask | {prefix-length | /} prefix-length } ] Minimum Access Level: Administrator Command Mode: config Defines a pool of addresses for Network Address Translation. Addresses can then be allocated from the pool as needed. Up to 30 NAT pools can be supported.
C. Router CLI Commands, Codes, and Designations Table C-8. NAT Commands (3 of 3) (Continued from previous page) pool – Specify the name of a pool of addresses available for dynamic address translation. For inside source translation, this is the pool of local addresses. pool-name – The name of a NAT pool comprised of 1–20 ASCII printable characters. interface – For dynamic address translation, specifies an interface or sub-interface that provides the address for the translation.
C. Router CLI Commands, Codes, and Designations DHCP Server Commands Dynamic Host Configuration Protocol (DHCP) server commands are used to enable or disable the DHCP server, and create or delete a DHCP pool. Table C-9. DHCP Server Commands (1 of 3) [no] service dhcp Minimum Access Level: Administrator Command Mode: config Allows you to enable or disable the DHCP server. The DHCP server is enabled by default but is not active until other DHCP server options are configured.
C. Router CLI Commands, Codes, and Designations Table C-9. DHCP Server Commands (2 of 3) lease {days [ hours ] [minutes ] | infinite} no lease [days [ hours ] [minutes ] |infinite] Minimum Access Level: Administrator Command Mode: config-dhcp Allows you to specify or clear the lease time for an IP address assigned to a DHCP client. After the lease time has expired, the address assignment is no longer valid. The default lease time is one day.
C. Router CLI Commands, Codes, and Designations Table C-9. DHCP Server Commands (3 of 3) network network-num [ [ netmask ] netmask | {prefix-length | /} prefix-length ] no network [network-num [ [netmask] netmask | {prefix-length | /} prefix-length ] ] Minimum Access Level: Administrator Command Mode: config-dhcp Allows you to specify or remove a subnet and subnet mask to a DHCP server pool.
C. Router CLI Commands, Codes, and Designations DHCP Relay Agent Commands Dynamic Host Configuration Protocol (DHCP) relay agent commands Table C-10. DHCP Relay Agent Commands ip dhcp relay max-clients max-dhcp-clients no ip dhcp relay max-clients [max-dhcp-clients ] Minimum Access Level: Administrator Command Mode: config Allows you to limit the number of DHCP clients supported. The no dhcp relay max-agents command resets the maximum number of DHCP clients supported to the default of 1.
C. Router CLI Commands, Codes, and Designations Filter (access-list) Commands Filter commands are used to create or delete Access Lists. Table C-11.
C. Router CLI Commands, Codes, and Designations Table C-11. Filter Commands (2 of 4) (Continued from previous page) For Extended IP Access Lists: Example: access-list 100 permit tcp 10.1.1.1 0.0.0.255 20.1.1.1 0.0.0.255 protocol – The IP protocol to which the filter will be applied. The following protocols are supported: ip – Filter applies to all IP packets (including but not limited to ICMP, TCP, and UDP). icmp – Internet Control Message Protocol. tcp – Transmission Control Protocol.
C. Router CLI Commands, Codes, and Designations Table C-11. Filter Commands (3 of 4) For Extended IP Access Lists: (continued) src-port – Specify a TCP or UDP port number to be filtered. Valid if the protocol specified is tcp or udp. Refer to Table C-16, TCP Port Designations, and Table C-17, UDP Port Designations. Valid port number range is 0–65535. src-end-port – Specifies last TCP or UDP port number in a range of port numbers to be filtered.
C. Router CLI Commands, Codes, and Designations Table C-11. Filter Commands (4 of 4) [no] ip access-group access-list-1-199num [in | out ] Minimum Access Level: Administrator Command Mode: config-if Allows you to control access to an interface by allowing you to designate (or delete) a set of access rules to be applied to either incoming or outgoing packets. By default, no access lists are applied to interfaces.
C. Router CLI Commands, Codes, and Designations Diagnostic Commands Diagnostic commands allow you to ping or trace the route to a specified destination. Table C-12. Diagnostic Commands (1 of 2) ping [ protocol ] dest-ip [source source-ip ] [length bytes ] [timeout time ] [interface intf-type intf-num [.sub-intf-num ] ] Minimum Access Level: Operator Command Mode: Standard Pings the specified destination address. For a successful ping, the results are shown as: Ping reply [x.x.x.
C. Router CLI Commands, Codes, and Designations Table C-12. Diagnostic Commands (2 of 2) traceroute [protocol ] dest-ip [source source-ip ] [length bytes ] [timeout time ] [hops hops ] [interface intf-type intf-num [.sub-intf-num]] Minimum Access Level: Operator Command Mode: Standard This command performs the TraceRoute test to the specified destination IP address. The general format of the TraceRoute results is seen as follows: Tracing route to x.x.x.
C. Router CLI Commands, Codes, and Designations Show Commands Show commands allow you to display information. Table C-13. Show Commands (1 of 4) show arp Minimum Access Level: Operator Command Mode: Standard Displays the devices in the ARP table. The general format of the show arp command is: IP Address Timeout (min) MAC address Type x.x.x.x STATIC xx:xx:xx:xx:xx:xx ARPA x.x.x.x time xx:xx:xx:xx:xx:xx ARPA Interface Interface The first column displays the IP address.
C. Router CLI Commands, Codes, and Designations Table C-13. Show Commands (2 of 4) show configuration {saved | unsaved} Minimum Access Level: Administrator Command Mode: All config modes Displays/outputs a sequence of commands in the form of ASCII strings that have the effect of setting all configurable parameters to the current values, either saved in memory or entered during a current configuration session. Passwords are write-only and not output.
C. Router CLI Commands, Codes, and Designations Table C-13. Show Commands (3 of 4) show ip dhcp binding [ ip-address ] Minimum Access Level: Operator Command Mode: Standard Allows users to display address bindings associated with the DHCP server. If the IP address is not specified, all DHCP server bindings are displayed. If an IP address is specified, only the DHCP server binding for the specified client is displayed. ip-address – Specifies the DHCP client’s IP address for the binding to be displayed.
C. Router CLI Commands, Codes, and Designations Table C-13. Show Commands (4 of 4) show ip traffic Minimum Access Level: Operator Command Mode: Standard Displays the IP statistics for the device. show spanning-tree Minimum Access Level: Operator Command Mode: Standard Displays the devices spanning-tree topology.
C. Router CLI Commands, Codes, and Designations Ethernet Type Codes Use Table C-14, Ethernet Type Codes (Hex), when specifying the filter applied to incoming Ethernet packets by Type Code. Many of the Type Codes listed below are distributed by Xerox Corporation. Table C-14. Ethernet Type Codes (Hex) (1 of 2) Type Code Description Type Code Description 0000–05DC IEEE802.
C. Router CLI Commands, Codes, and Designations Table C-14. Ethernet Type Codes (Hex) (2 of 2) Type Code Description Type Code Description 6004 DEC LAT 80A3 Nixdorf Computers 6005 DEC Diagnostic Protocol 80A4–80B3 Siemens Gammasonics Inc.
C. Router CLI Commands, Codes, and Designations Protocol and Port Designations The following tables are used for filtering. ICMP Designations Use the Internet Control Management Protocol (ICMP) designations in Table C-15, ICMP Designations, when specifying a specific ICMP message to be filtered. Table C-15.
C. Router CLI Commands, Codes, and Designations Table C-15.
C. Router CLI Commands, Codes, and Designations TCP Port Designations Use the Transmission Control Protocol (TCP) port designations in Table C-16, TCP Port Designations, when specifying a specific TCP port to be filtered. Table C-16.
C. Router CLI Commands, Codes, and Designations UDP Port Designations Use the User Datagram Protocol (UDP) port designations in Table C-17, UDP Port Designations, when specifying a specific UCP port to be filtered. Table C-17.
Router Command Line Summaries and Shortcuts D CLI Summaries For summaries of Command Line Interface commands, see: Table D-1, Show Commands Table D-2, Access Control and System Level Commands Table D-3, CLI Commands For default settings, see CLI Command Default Settings on page D-6. The minimal characters that must be typed when entering commands are shown in courier bold for these tables.
D. Router Command Line Summaries and Shortcuts Show Command Summary Table D-1, Show Commands, lists all of the show, or display, commands for the CLI. Table D-1. Show Commands Command Function show arp Displays all the devices in the router’s ARP table. show bridge Displays the router’s bridge forwarding database entries. show configuration Displays the router’s current configuration.
D. Router Command Line Summaries and Shortcuts Access Control and System Level Command Summary Table D-2, Access Control and System Level Commands, lists of all of the access control and system level commands for the CL I. Table D-2. 9128-A2-GB20-80 Access Control and System Level Commands Command Function ? Displays all valid commands for the current access level. ! Used to enter comments. Comments following the ! are ignored by the CLI.
D. Router Command Line Summaries and Shortcuts CLI Command Summary Table D-3, CLI Commands lists of all of the system-level commands for the CLI. For the default settings, see CLI Command Default Settings on page D-6. Table D-3.
D. Router Command Line Summaries and Shortcuts Table D-3. CLI Commands (2 of 2) Command encapsulation encapsulation-type encapsulation-protocol [no] frame-relay interface-dlci dlci-num interface intf-type intf-num [.sub-intf-num [point-to-point] ] no interface intf-type intf-num.
D. Router Command Line Summaries and Shortcuts CLI Command Default Settings The following list shows the default settings: !software version d1.06.
Connectors, Cables, and Pin Assignments E This appendix shows the FrameSaver unit rear panels, and pin assignments for the connectors/interfaces and cables. Standard interfaces are used on the unit, so most cables do not have to be specially ordered; they can be purchased anywhere. NOTE: In the pin assignment tables of this appendix, if the pin number is not shown, it is not being used. Rear Panels The following illustration shows the rear panel of the FrameSaver SLV 9126 (without Ethernet).
E. Connectors, Cables, and Pin Assignments The following illustration shows the rear panel of the FrameSaver SLV 9126-II (with Ethernet and DBM). POWER ENET DSX DSX-1 NET MDM DBM COM 02-17141 The following illustration shows the rear panel of a 1-slot FrameSaver SLV 9128-II.
E. Connectors, Cables, and Pin Assignments The following illustration shows the rear panel of the carrier-mounted, single T1, dual port FrameSaver SLV 9128-II. SINGLE T1 NAM N E T D B M M D M D S X E N E T P O R T 1 P O R T 2 C O M 00-16850 Model 9128-II The sections that follow provide pin assignments for each interface.
E. Connectors, Cables, and Pin Assignments COM Port Connector The type of COM port connector depends on the model. COM Port for 9126 and 9128-II (25-Position) The following table provides the pin assignments for the FrameSaver SLV 9126 and 9128-II units’ 25-position EIA-232C communication port connector.
E. Connectors, Cables, and Pin Assignments COM Port for 9128-II Carrier Mount The following table shows the signals and pin assignments for the carriermounted FrameSaver SLV 9128-II NAM’s 8-position communication port interface/connector.
E. Connectors, Cables, and Pin Assignments COM Port-to-Terminal/Printer Cable (Feature No. 3100-F2-540) Order this cable when connecting the 8-position COM port to a terminal or printer, rather than to a PC. The following shows the pin assignments from the COM port to the DTE interface.
E. Connectors, Cables, and Pin Assignments COM Port-to-Router Cables The following tables provide the pin assignments for connecting the 1-slot FrameSaver unit’s 25-position communication port to various router auxiliary (AUX) or console ports using standard cables.
E.
E.
E. Connectors, Cables, and Pin Assignments Gender Adapter/Changer When connecting the COM port to a router or Frame Relay Assembler/ Disassembler (FRAD), a gender adapter is required to convert the COM Port-to-Terminal/Printer cable’s plug-type interface to a socket-type interface for the router’s or FRAD’s AUX port. LAN Adapter Converter and Cable A LAN adapter converter and cable is not needed for the FrameSaver SLV 9128-II carrier-mounted unit, and cannot be used with the FrameSaver SLV 9126-II.
E. Connectors, Cables, and Pin Assignments DTE Port Connector The following table provides the pin assignments for the 34-position V.35 connector to the DTE.
E. Connectors, Cables, and Pin Assignments Standard V.35 Straight-through Cable A standard V.35 straight-through cable can be used to connect a DTE port to a DTE, where a 34-pin plug-type connector is needed for the data port and a 34-position socket-type connector is needed for the DTE. No special-order cables are required. Standard V.35 Crossover Cable A standard V.
E. Connectors, Cables, and Pin Assignments DSX-1 Connector The type of DSX-1 port connector depends on the model. DSX-1 Port for 9126, 9126-II, and Carrier Mounted 9128-II (8-Position) The following table shows the signals and pin assignments for the 8-position modular DSX-1 interface on the FrameSaver SLV 9126, 9126-II, and 9128-II carrier-mounted units. The DSX-1 Adapter is required for this interface.
E. Connectors, Cables, and Pin Assignments DSX-1 Port for 1-Slot 9128-II (15-Position) The following table shows the signals and pin assignments for the 15-position DSX-1 interface on the FrameSaver SLV 9128-II standalone units. A DSX-1 adapter is not required for this interface.
E. Connectors, Cables, and Pin Assignments T1 Network Cable (Feature No. 3100-F1-500) Network access is via a 20-foot cable with an RJ48C unkeyed plug-type connector on each end. The following table shows pin assignments and the purpose of each. Function Circuit Direction Pin Number Receive Ring R1 From Network 1 Receive Tip T1 From Network 2 Transmit Ring R To Network 4 Transmit Tip T To Network 5 T1 Mass Termination Cable (Feature No.
E. Connectors, Cables, and Pin Assignments Canadian T1 Line Interface Cable (Feature No. 3100-F1-510) The T1 line interface cable is used in Canada as an interface between the FrameSaver unit’s network connector and the T1 network interface. The following shows pin assignments and the purpose of each.
E. Connectors, Cables, and Pin Assignments Modem Connector The dial modem interface/connector that is integrated into the FrameSaver unit is an RJ11 6-position, 4-contact unkeyed modular jack. The following table shows pin assignments and the purpose of each. Function Circuit Direction Pin Number Ring R To Local Loop 2 Tip T To Local Loop 3 ISDN DBM Connector The backup connection is through the DBM interface/connector, which is an 8-position keyed modular jack.
E.
Technical Specifications F The following technical specifications are included: NAM Technical Specifications (Table F-1) 1-Slot CSU/DSUs and Router Technical Specifications (Table F-2) 14-Slot 9000 Series Access Carrier Technical Specifications (Table F-3) ISDN BRI DBM (Optional Feature) Technical Specifications (Table F-4) ISDN PRI DBM (Optional Feature) Technical Specifications (Table F-5) Table F-1.
F. Technical Specifications Table F-1. NAM Technical Specifications (2 of 3) Specification Criteria Weight F-2 NAM 1 lb. 2 oz. (.51 kg) I/O Card 6 oz. (.17 kg) Power Consumption and Dissipation 9.5 watts, 0.080A at 120 VAC Result: 32 Btu per hour COM Port/Interface – Communications/Management 8-position unkeyed modular jack Standard EIA-232/ITU, V.24 (ISO 2110) Data rates 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.
F. Technical Specifications Table F-1. NAM Technical Specifications (3 of 3) Specification Criteria ISDN PRI DBM Interface 8-position unkeyed modular USOC RJ48C jack Service supported PRI, NI-1 or NI-2 Data rates 1.536 Kbps Framing format D4, ESF Coding format B8ZS Line Build-Out (LBO) 0.0 dB, -7.5 dB, -15 dB, -22.5 dB ANSI PRM Selectable Ethernet Port 8-position modular unkeyed jack Standard ANSI/IEEE Standard 802.
F. Technical Specifications Table F-2. 1-Slot CSU/DSUs and Router Technical Specifications (2 of 3) Specification Criteria Power Consumption and Dissipation Built-in power cord NEMA 5-15P plug 100–240 VAC power supply: FrameSaver SLV 9126 9.1 watts, 60 Hz ±3, 0.151 A at 120 VAC ±12 Result: 31.05 BTU per hour 120 VAC power supply: FrameSaver SLV 9126-II and 9126-II Router 7.3 watts, 60 Hz ±3, 0.131 A at 120 VAC ±12 Result: 24.9 BTU per hour FrameSaver SLV 9128-II 10.3 watts, 60 Hz ±3, 0.
F. Technical Specifications Table F-2. 1-Slot CSU/DSUs and Router Technical Specifications (3 of 3) Specification Criteria Data Port 34-position V.35 connector Standard V.35/ITU (ISO 2593) Data rates Variations for T1 rates; automatically set to the network rate. Modem (MDM) Interface 6-position unkeyed modular USOC RJ11C jack Data rates Up to 14.
F. Technical Specifications Table F-3. 14-Slot 9000 Series Access Carrier Technical Specifications (2 of 2) Specification Criteria Physical Environment Operating temperature 35°F to 122°F (1.7°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 Physical Dimensions Height 10.5 inches (26.7 cm) or 6U Width 17.2 inches (43.7 cm) Depth 14.3 inches (36.
F. Technical Specifications Table F-4. ISDN BRI DBM (Optional Feature) Technical Specifications Specification Criteria Standards Compliance ANSI T1.601 – 1992 (physical layer) Bellcore SR-NWT-001937, Issue 1 – February 1991 ITU Q.921 – 1992 (link layer) ITU Q.931 – 1993 (network layer) TR-TSY-00860, ISDN Calling Number Identification Services – February 1989, and Supplement – June 1990 Power Consumption 60 mA at 15 VDC Average power .9 watt (3.07 Btu per hour) Weight 0.27 lbs. 4.3 oz. (0.
F. Technical Specifications Table F-5. ISDN PRI DBM (Optional Feature) Technical Specifications Specification Criteria Standards Compliance ANSI T1.403 – 1989 (physical layer) and AT&T 62411 Bellcore SR-NWT-002120, Issue 1 – May 1992 ITU Q.921 – 1992 (link layer) ITU Q.931 – 1993 (network layer) TR-TSY-00860, ISDN Calling Number Identification Services – February 1989, and Supplement – June 1990 F-8 Power Consumption 8 mA at 120 VAC Average power 1 watt (3.4 Btu per hour) Weight 0.15 lbs. 2.4 oz.
Equipment List G Equipment See Cables on page G-6 for cables you can order. Model/Feature Number Description FrameSaver SLV Units FrameSaver SLV 9126 T1 remote site unit with: 9126-A1-201 SLM Feature Set Integral modem Support for up to 16 PVCs Includes 1-Slot Housing, Universal 100–240 VAC Power Supply, Network Cable, Installation Instructions, and Quick Reference.
G. Equipment List Model/Feature Number Description FrameSaver SLV Units (continued) FrameSaver SLV 9126-II T1 remote site unit with: 9126-A2-202 SLM Feature Set Integral modem ISDN BRI DBM Support for up to 64 PVCs Ethernet port for management Includes 1-Slot Housing, 120 VAC Power Supply, Network Cable, RJ49C BRI ISDN-V Cable, Installation Instructions, and Quick Reference.
G. Equipment List Model/Feature Number Description FrameSaver SLV Units (continued) FrameSaver SLV 9128-II T1 central site 1-slot unit with: 9128-A2-202 SLM Feature Set Integral modem ISDN PRI DBM Support for up to 120 PVCs Ethernet port for management Includes 1-Slot Housing, 120 VAC Power Supply, Network Cable, RJ48C PRI ISDN Cable, Installation Instructions, and Quick Reference.
G. Equipment List Model/Feature Number Description FrameSaver SLV Units (continued) FrameSaver SLV 9128-II T1 central site carrier NAM with: 9128-B2-211 Diagnostic Feature Set Integral modem Support for up to 120 PVCs Ethernet port for management Includes Network Cable, Installation Instructions, and Quick Reference.
G. Equipment List Model/Feature Number Description 9000 Series Access Carrier (9128-II NAM only) 9128-A2-GB20-80 Access Carrier Includes 14-Slot Housing, Universal 90 – 250 VAC Power Supply, Power Supply Tray, Baffle, Fan Tray, Mounting Brackets, and Installation Instructions. 9007-B1-409 Access Carrier Includes 14-Slot Housing, Universal –48 VDC Power Supply, Power Supply Tray, Baffle, Fan Tray, Mounting Brackets, and Installation Instructions.
G. Equipment List Cables This table lists cables you can order. G-6 Description Part Number Feature Number RJ48C DSX-1 Network Cable, 8-pin modular-to-8-pin modular – 20 feet/6.1 meters 035-0209-2031 3100-F1-500 RJ48C T1 Network Cable, RJ48C-to-RJ48C – 20 feet/6.1 meters 035-0209-2031 3100-F1-500 T1 Line Interface Cable, RJ48C-to-CA81A – 20 feet/6.1 meters For use in Canada.
Index Numerics 1MPort mode auto-configuration, 1Port mode auto-configuration, 1PPort mode auto-configuration, 2MPorts mode auto-configuration, 55 hexadecimal test pattern, 8-24 4-9 4-9 4-9 4-9 A aborting tests, 8-21 Access CLI and configuration, 1-3 control commands, C-3 controlling CLI, 6-14 Easy, 4-3 Level Port, 4-101 limiting router CLI, 6-14 Name, 4-83 to another devices interface, 7-70 Type, 4-88 Access Dial-In, 6-4 Access Level, 6-11–6-12 assigning, 6-10 changing, 6-15 CLI command modes, 6-14 Port,
Index assign DSX-1 time slots, 4-53 frame relay time slots, 4-52 synchronous data port, 4-59 time slots and cross connections, 4-51 assigning community names and access levels, 6-10 DLCIs to a Backup Group, 4-18 At-a-Glance report, 11-6 authentificationFailure trap, B-9 Auto Backup Criteria, 4-104 restricting, 4-17 Auto-Configuration, 1-6, 2-4 Active, 7-20 setting up, 4-8 availability LMI and PVC, 1-10 B back door access when locked out, 8-4 Backspace, 2-6, 2-10 Back-to-Back Mode Active, 7-20 operation se
Index Clock Invert Transmit, 4-39 setting system, 4-5 Source, 4-31–4-32 Transmit, 4-39 ClrAllCodePoints, 4-25 CNIS, 6-5 Code Points, 4-27 codes, Ethernet type, C-29 COM port, 4-75, 4-89 connector, E-4 to-PC or terminal/printer cable, E-5 to-router cables, E-7 Command Line Interface (CLI) commands, C-1 commands ARP, C-11 bridge, C-9 CLI, C-1 CLI access control, C-3 CLI configuration, C-4 DHCP relay agent, C-18 server, C-15 diagnostic, C-23 filter (access-list), C-19 interface, C-5 IP routing, C-8 NAT, C-12
Index D Data Channel Loopback, 4-36, 7-21, 8-32 Delivery Ratio (DDR), 1-10 Inverse ARP for, 1-2 Link Control Identifier (DLCI), 4-79, 4-81 Port physical options, 4-38 port connector pin assignments, E-11 Rate (Kbps), 4-96 selection criteria, 2-9 uploading SLV and packet capture, 7-80 Date & Time setting, 4-5 DBM BRI Card Failed, 7-20 call performance statistics, 7-67 changing BRI software, 7-78 configuring interface, 4-45 configuring to send traps, 4-18 connector, E-17 Download Required, 7-21 forcing backu
Index DLCI (continued) Priority, 4-66 Records, 4-64 Source, 4-68 statistics, 7-57 status, 7-29 Traps on Interfaces, 4-91 Type, 4-65 DNS, 5-11 domains and groups correcting, 10-6 verifying, 10-5 download, 7-77 downloading current router configuration, 5-16 determining when completed, 7-79 MIBs and SNMP traps, B-2 SLV alarms, 10-8 software, 7-75 user history file, 10-13 DSX-1 adapter pin assignments, E-13 assigning data port to time slots, 4-59 assigning time slots, 4-53 connector pin assignments, E-13 inter
Index feature sets advanced FLEX SLV, 1-4 basic FLEX, 1-4 field is blank/empty, 2-9 file transfer, 7-75 filter (access-list) CLI commands, C-19 filtering bridge, 5-14 IP, with/without NAT, 5-15 router, 5-14 FR Mode LED, 7-9 Frame Delivery Ratio (FDR), 1-10 Frame Relay assigning time slots, 4-52 configuring interface, 4-61 configuring system, 4-21 Discovery, 4-9 saving a mode change, 4-11 DS0s Base Rate, 4-62 Mode LED, 7-9 statistics, 7-59 troubleshooting PVC problems, 8-16 frames, 4-78 FTP, 1-7, 7-75 file
Index IP Address, 4-103 default destination, 4-75 filtering, 5-15 node information, 4-74 options processing, 5-5 ping test, 8-35 routing, 5-3 CLI commands, C-8 Routing Table, 1-7, 7-48 Validation NMS, 4-87 IP Address, 4-78, 4-99, 4-102 distributing to other FrameSavers, 4-72 Ethernet port, 4-94 NMS number, 4-87, 4-89 Node, 4-74 IP address validation, 4-76 IP addressing limiting SNMP access, 6-11 IP Enabled DLCI performance statistics, 7-59 DLCI Type, 4-65 SLV performance statistics, 7-54 IP SLV availabilit
Index LMI and PVC availability, 1-10 Behavior, 4-21–4-22 Clearing Event (N3), 4-23, 4-63 configuring frame relay and, 4-21 Down, 7-22, 8-9 Error Event (N2), 4-23, 4-62 frame relay statistics, 7-62 Heartbeat (T1), 4-23, 4-63 Inbound Heartbeat (T2), 4-23, 4-63 N4 Measurement Period (T3), 4-24, 4-63 OK control lead, 7-11 packet utility, 8-5 Parameters, 4-62 pass-through, 4-21 Protocol, 1-2, 4-61 Status Enquiry (N1), 4-23, 4-63 trace log, 8-6 uploading packet capture data, 7-80 local external DTE loopback, 4-4
Index modem, 1-7 connector, E-17 Health and Status messages, 7-20 manually disconnecting, 7-71 operation, 7-70 PassThru, 4-96 PassThru feature, 1-7, 4-7, 7-70 port destination, 4-75, 4-89 port options, 4-100 setting up, 4-6 verifying setup and operation, 7-71 modifying a login, 6-13 Monitor DTR, 4-40 Pattern, 8-24 RTS, 4-40 monitoring DLCI history data, 10-16 FrameSaver unit, 7-18 LEDs, 7-5, 7-7 LEDs and control leads, 7-4 using NetScout Manager Plus, 10-18 most recent cause values, 7-42 Multilink Constitu
Index O odd parity, 4-97 OID (object identification) user history file, 10-13 cross-reference (numeric order), B-27, B-32 OK LED, 7-8, 7-10 OOF at DSX-1 or Network, 7-23, 8-10 at ISDN PRI, 7-24 LED, 7-8, 7-10 linkDown trap, B-11 OpenLane, 1-11 copying directory, 10-2 SLM support, 9-2 operating mode changing, 4-19 operation, 2-1, 7-1 Operator CLI Access Level, 6-14 ordering Activation Certificates, 9-4 organization of this document, xi Out of Frame, 7-8 linkDown trap, B-11 Out of Sync message, 8-16, 8-24 Ou
Index Port (continued) TCP designations, C-33 UDP designations, C-34 Use, 4-38, 4-96, 4-100 PPP, 4-100, 4-102 previous recent cause values, 7-42 Primary Clock Failed, 7-24, 8-11 Source, 4-31 Primary Destination DLCI, 4-69 EDLCI, 4-70 Link, 4-69 Primary Frame Relay Link, 4-79, 4-81 Primary Link RIP, 4-80 printed reports, 11-7 printer COM port cable, E-6 printing certificate report, 9-9 problem indicators, 8-2 product-related documents, xiii Profile ID (SPID), 4-45 profiles entering, 4-49 Proprietary Caller
Index Routing Information Protocol (RIP), 4-99 IP, 5-3 table, 7-48 table, 1-7, 5-3 RTS control lead, 7-11 running reports, 11-6 RXD control lead, 7-11 S Sampling SLV Inband and Interval, 4-28 saving configuration options, 3-6 scheduled activations, 9-8–9-9 Scratchpad Configuration, 3-3 screen area, 2-5 function keys area, 2-5 how to navigate, 2-6 scrolling through valid selections, 2-9 Secondary Clock Failed, 7-24–7-25, 8-12 Source, 4-32 security, 1-5, 2-2, 2-9, 3-5, 6-1 router, 5-14 SNMP NMS options, 4-8
Index software changing, 7-79 ISDN BRI DBM, 7-78 downloading, 7-75 revision DBM, 7-4 NAM, 7-3 Source DLCI, 4-68 EDLCI, 4-69 Link, 4-68 Spacebar, 2-6 specifications technical, F-1 SPID, 4-45, F-7 Standard_out RIP, 1-5 standards compliance for SNMP Traps, B-8 starting a session, 2-2 a test, 8-20 statistics, 1-10, 7-50 DBM call, 7-67 elements, 11-3 selecting performance intervals for display, 7-64 uploading to an NMS, 7-80 Status Activation Certificates, 9-7 Call, 7-40 checking scheduled activations, 9-9 DBM
Index Tests, 1-6 aborting, 8-21 available, 8-18 Connectivity, 8-25 Data Channel Loopback, 8-32 DBM, 8-19 DTE Loopback, 8-30 Duration, 4-31 IP Ping, 8-35 Lamp, 8-40 Line Loopback, 8-27 pattern, 8-34 Payload Loopback, 8-28 physical, 8-26 ping, 8-35 PVC, 8-22 PVC Loopback, 8-23 Remote Line Loopback, 8-31, 8-33 Repeater Loopback, 8-29 Send/Monitor Pattern, 8-24 starting or stopping, 8-20 Test Call, 8-25 Timeout, 4-31, 8-19 throughput, 1-10 time setting, 4-5 time slot assignments synchronous data port to networ
Index user history adding files, 10-13 installing files, 10-15 monitoring DLCI, 10-16 statistics gathering, 1-7, 1-10 user interface, 2-1 cannot be accessed, 8-15 communication port options, 4-96 resetting/restoring access, 8-4 Telnet session, 4-84 user-defined history, 10-13 V V.35 connector, E-11 crossover cable, E-12 straight-through cable, E-12 V.
Index IN-16 September 2002 9128-A2-GB20-80
