FrameSaver SLV MODELS 9820, 9820-2M, 9820-8M, and 9820-45M USER’S GUIDE Document No.
Copyright E 2000 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Ave. N.
Contents About This Guide H Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix H Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix H Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi H Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4 Configuration Options H Configuring Using the Easy Install Screen (Model 9820-45M) . . . . . . . . . 4-3 H Entering System Information and Setting the System Clock . . . . . . . . . . . 4-4 H Setting Up for Trap Dial-Out (Models 9820, 9820-2M, 9820-8M) . . . . . . . 4-5 Setting Up an External Modem for Trap Dial-Out . . . . . . . . . . . . . . . . . 4-5 Setting Up Call Directories for Trap Dial-Out . . . . . . . . . . . . . . . . . . . . 4-5 H Setting Up Auto-Configuration . . . . . . . . . . .
Contents 5 Security and Logins H Limiting Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H Controlling Asynchronous Terminal Access . . . . . . . . . . . . . . . . . . . . . . . . . H Controlling External COM Port Device Access (Models 9820, 9820-2M, 9820-8M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H Controlling Modem Port Device Access (Model 9820-45M) . . . . . . . . . . .
Contents 7 FTP Operation H FTP File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Upgrading System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Determining Whether a Download Is Completed . . . . . . . . . . . . . . . . . 7-5 Changing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Transferring Collected Data . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 10 Setting Up NetScout Manager Plus for FrameSaver Devices H Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 H Configuring NetScout Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 Adding FrameSaver SLV Units to the NetScout Manager Plus Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents A Menu Hierarchy H Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 B SNMP MIBs and Traps, and RMON Alarm Defaults H MIB Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 H Downloading MIBs and SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 H System Group (mib-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents C Connectors, Cables, and Pin Assignments H Rear Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 H COM (Terminal) Port Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 LAN Adapter Converter and Cable (Models 9820, 9820-2M, 9820-8M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents viii June 2000 9820-A2-GB20-20
About This Guide Purpose and Intended Audience This document contains information needed to properly set up, configure, and verify operation of FrameSaver SLV in-line monitors. It is intended for system designers, engineers, administrators, and operators. Document Organization 9820-A2-GB20-20 Section Description Chapter 1 About FrameSaver SLV In-Line Monitors. Identifies how FrameSaver SLV in-line monitors fit into Paradyne’s SLM solution, and describes the features of these units.
About This Guide Section Description Chapter 9 Setting Up OpenLane for FrameSaver Devices. 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. Chapter 11 Setting Up Network Health for FrameSaver Devices.
About This Guide Product-Related Documents Document Number Document Title Paradyne FrameSaver Documentation: 9820-A2-GL10 FrameSaver SLV, Models 9820, 9820-2M, 9820-8M, and 9820-45M, Quick Reference 9820-A2-GN10 FrameSaver SLV, Models 9820, 9820-2M, and 9820-8M, Installation Instructions 9820-A2-GN11 FrameSaver SLV, Model 9820-45M, Installation Instructions Paradyne OpenLane NMS Documentation: 7800-A2-GZ41 OpenLane 5.
About This Guide Conventions Used Convention Used When Used Italic To indicate variable information (e.g., DLCI nnnn). Menu selection sequence To provide an abbreviated method for indicating the selections to be made from a menu or selections from within a menu before performing a procedural step. For example, Main Menu → Status → System and Test Status indicates that you should select Status from the Main Menu, then select System and Test Status.
About FrameSaver SLV In-Line Monitors 1 This chapter includes the following: H SLM Overview H FrameSaver SLV In-Line Monitor Features SLM Overview The Service Level Management (SLM) Solution consists of: H FrameSaverr SLV units H OpenLanet SLM system H Standalone NetScout Probes and NetScout Manager Plus application (optional) FrameSaver SLV (Service Level Verifier) in-line monitors add superior diagnostic capability, end-to-end visibility, accurate network performance reporting, and SLM intellig
About FrameSaver SLV In-Line Monitors The following illustration shows a network that includes FrameSaver units at the central site and remote sites. User data PVCs provide LAN-to-LAN connectivity between the central site and the remote sites.
About FrameSaver SLV In-Line Monitors FrameSaver SLV In-Line Monitor Features The FrameSaver SLV in-line monitor provides the following features: H Intelligent Service Level Verification. Provides accurate throughput, latency, and availability measurements to determine network performance and whether service level agreements (SLAs) are being met, along with SLA reporting. SLA parameter thresholds can be configured to provide proactive notification of a developing network problem. H Security.
About FrameSaver SLV In-Line Monitors H RMON-Based User History Statistics Gathering. Provides everything needed to monitor network service levels, plus throughput with accurate data delivery, network latency, and LMI and PVC availability. In addition, port bursting statistics are kept for all frame relay links. These statistics are available real-time via the Enterprise MIB and historically as an RMON2 User History object.
About FrameSaver SLV In-Line Monitors H ATM VPI/VCI and DLCI Correlation. For networks with both ATM and frame relay-access endpoints, allows the FrameSaver unit to report the originating Virtual Path or Channel Identifier (VPI/VCI) in the far-end ATM-access endpoint where the local DLCI is mapped so they can be correlated for OpenLane SLV reports. H Back-to-Back Operation.
About FrameSaver SLV In-Line Monitors H NetScout Manager Plus and NetScout Probe Support. Provides complete LAN and WAN traffic analysis and monitoring functions for FrameSaver SLV devices. The following features are supported using this application: — Thresholds for RMON 1 (Remote Monitoring, Version 1) alarms and events can be configured. — (Models 9820 and 9820-2M.) Performance monitoring can be performed using collected RMON 2 (Version 2) data.
User Interface and Basic Operation 2 This chapter tells you how to access, use, and navigate the menu-driven user interface. It includes the following: H Logging On H Main Menu H Screen Work Areas H Navigating the Screens — Keyboard Keys — Function Keys — Selecting from a Menu — Switching Between Screen Areas — Selecting a Field — Entering Information What appears on the screens depends on: 9820-A2-GB20-20 H Current configuration – How your network is currently configured.
User Interface and Basic Operation Logging On Start a session using one of the following methods: H Telnet session via: — An in-band management channel through the frame relay network. — A local in-band management channel configured on the DTE port between the FrameSaver unit and the router. H Dial-in connection using the internal modem (Model 9820-45M). H Direct terminal connection over the COM port (Terminal port on the Model 9820-45M). When logging on, the User Interface Idle screen appears.
User Interface and Basic Operation If your login was . . . Then the . . . Valid Main Menu appears. Begin your session. 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. – An external modem is disconnected. – An SNMP trap is generated. Access is denied.
User Interface and Basic Operation Main Menu Entry to all of the FrameSaver unit’s tasks begins at the Main Menu, which has five menus or branches. The Access Level at the top of the screen only appears when security has been set up.
User Interface and Basic Operation Screen Work Areas There are two user work areas: H Screen area – Where you input information into fields. H Function keys area – Where you perform specific screen functions. Below is a sample configuration screen showing a 2 Mbps unit.
User Interface and Basic Operation Navigating the Screens You can navigate the screens by: H Using keyboard keys. H Switching between the two screen work areas using function keys. Keyboard Keys Use the following keyboard keys to navigate within the screen area: 2-6 Press . . . To . . . Ctrl-a Move cursor between the screen area and the screen function keys area. Esc Return to the previous screen. Right Arrow (on same screen row), or Tab (on any screen row) Move cursor to the next field.
User Interface and Basic Operation Function Keys All function keys (located in the lower part of the screen) operate the same way throughout the screens. They are not case-sensitive, so upper- or lowercase letters can be used interchangeably. These keys use the following conventions: Select . . . For the screen And press Enter to . . . function . . . M or m MainMenu Return to the Main Menu screen. E or e Exit Terminate the asynchronous terminal session. N or n New Enter new data.
User Interface and Basic Operation Selecting from a Menu " Procedure To select from a menu: 1. Tab or press the down arrow key to position the cursor on a menu selection, or press the up arrow key to move the cursor to the bottom of the menu list. Each menu selection is highlighted as you press the key to move the cursor from position to position. 2. Press Enter. The selected menu or screen appears. " Procedure To return to a previous screen, press the Escape (Esc) key until you reach the desired screen.
User Interface and Basic Operation Selecting a Field Once you reach the desired menu or screen, select a field to view or change, or issue a command. Press the Tab or right arrow key to move the cursor from one field to another. The current setting or value appears to the right of the field. Entering Information You can enter information in one of three ways. Select the field, then: H Manually type in (enter) the field value or command.
User Interface and Basic Operation This page intentionally left blank.
Configuration Procedures 3 This chapter includes the following: H Basic Configuration — Configuration Option Areas — Accessing and Displaying Configuration Options — Changing Configuration Options — Saving Configuration Options — Minimal Configuration Before Deploying Remote Units 9820-A2-GB20-20 June 2000 3-1
Configuration Procedures 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. The Configuration Edit/Display menu of a FrameSaver SLV 9820-2M is shown below.
Configuration Procedures Configuration Option Areas The FrameSaver unit arrives with configured factory default settings, which are located in the Factory Default Configuration option area.
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.
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.
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 1, or Customer 2 configuration areas. NOTE: When changing settings, you must Save for changes to take effect. " Procedure To save the configuration option changes: 1. Press Ctrl-a to switch to the function key area at the bottom of the screen. 2. Type s or S to select the Save function and press Enter.
Configuration Options 4 This chapter includes the following: H Configuring Using the Easy Install Screen (Model 9820-45M) H Entering System Information and Setting the System Clock H Setting Up for Trap Dial-Out (Models 9820, 9820-2M, 9820-8M) — Setting Up an External Modem for Trap Dial-Out — Setting Up Call Directories for Trap Dial-Out H Setting Up Auto-Configuration — Selecting a Frame Relay Discovery Mode — Automatically Removing a Circuit H Setting Up Management — Setting Up Local Management
Configuration Options H Configuring Frame Relay for an Interface H Manually Configuring DLCI Records H Configuring PVC Connections H Setting Up Management and Communication Options — Configuring Node IP Information — Configuring Management PVCs — Configuring General SNMP Management — Configuring Telnet and/or FTP Session Support — Configuring SNMP NMS Security — Configuring SNMP Traps and Trap Dial-Out — Configuring the Ethernet Port (Model 9820-45M) — Configuring the Communication Port — Configurin
Configuration Options Configuring Using the Easy Install Screen (Model 9820-45M) The Easy Install screen provides direct access to the configuration options required to establish communication and prepare for Auto-Configuration. Main Menu → Easy Install Table 4-1. Easy Install Configuration Options (1 of 2) Node IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address needed to access the node.
Configuration Options Table 4-1. Easy Install Configuration Options (2 of 2) Ethernet Port Options Screen With the cursor on the Ethernet Port Options Screen field, press Enter. The Ethernet Port Options screen appears. See Configuring the Ethernet Port on page 4-50. After configuring the Ethernet port configuration options, save your changes. Then press ESC to return to the Easy Install screen.
Configuration Options Setting Up for Trap Dial-Out (Models 9820, 9820-2M, 9820-8M) An external modem can be attached to the COM port for dialing out when an SNMP trap is generated. To set up an external modem, you need to: 1. Set up SNMP trap managers. 2. Set up an external modem. 3. Set up Modem Directory phone numbers. 4. Configure trap dial-out. See Configuring SNMP NMS Security to set up SNMP trap managers. See Setting Up Call Directories for Trap Dial-Out when trap dial-out is desired.
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. Auto-configuration also maintains associated DLCI option settings when Standard LMI is used on the network data port.
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, a user data port DLCI, and automatically connects them to create a PVC.
Configuration Options NOTE: If 1MPort (the default) is not the setting required for your application, change the Frame Relay Discovery Mode before connecting the network cable or editing discovered option settings. Otherwise, the FrameSaver unit will start “discovering” DLCIs as soon as it powers up. To recover from this problem, edit a selected “discovered” DLCI or PVC connection manually if any DLCIs or PVC Connections have been configured manually.
Configuration 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. H If Yes (y) is entered, the Delete All DLCIs and PVC Connections? prompt appears. No is the default for this prompt.
Configuration Options Setting Up Management FrameSaver units are already set up for SNMP management, with Community Name 1 set to Public and Name 1 Access set to Read/Write. For remote sites, other than the IP Address, this is all that is required. Configuration → Management and Communication → General SNMP Management See Table 4-12, General SNMP Management Options, for configuration information.
Configuration Options Setting Up So the Router Can Receive RIP Using the system’s standard Routing Information Protocol (RIP) feature, routing information is passed to the router over the management PVC, so the router can learn routes to FrameSaver SLV devices. Node IP information should be set up (see Configuring Node IP Information). " Procedure 1. Configure the router to receive RIP.
Configuration Options 5. Select the Delete EDLCI Connections and Make a Mgmt Only PVC option. PVC connections for the selected DLCI are broken, the Port-1 DLCI mapped to this network DLCI and the embedded management DLCI (EDLCI) are deleted, and the selected DLCI will be reconfigured as a management PVC using the Node IP Address. See Table 4-8, DLCI Record Options, for configuration information.
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 them when configuring the unit. The following configuration option tables are included: H Table 4-2. System Frame Relay and LMI Options H Table 4-3. Service Level Verification Options H Table 4-4. General System Options H Table 4-5. Network Data Port Physical Interface Options H Table 4-6.
Configuration Options Configuring Frame Relay and LMI for the System Select Frame Relay and LMI from the System menu to display or change the Frame Relay and LMI options for the entire system (see Table 4-2). Main Menu → Configuration → System → Frame Relay and LMI See Configuring Frame Relay for an Interface to set an interface’s frame relay options. Table 4-2.
Configuration Options Table 4-2. System Frame Relay and LMI Options (2 of 2) 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.
Configuration Options Configuring Service Level Verification Options SLV options are selected from the System menu (see Table 4-3). Main Menu → Configuration → System → Service Level Verification Table 4-3. Service Level Verification Options (1 of 2) SLV Sample Interval (secs) Possible Settings: 10 – 3600 Default Setting: 60 Sets the inband communications interval between FrameSaver SLV devices.
Configuration Options Table 4-3. Service Level Verification Options (2 of 2) SLV Timeout Clearing Event Threshold Available Settings: 1, 2, 3, 4 . . . 20 Default Setting: 1 Specifies the number of consecutive SLV messages that must be received before the DLCI Inactive status is cleared. 1 – 20 – Sets the limit for the clearing event. SLV Packet Size (bytes) Available Settings: 64 – 2048 Default Setting: 64 Sets the size of packets, in bytes, that will be used for SLV communications.
Configuration Options Configuring General System Options Select General from the System menu to configure the general system configuration options (see Table 4-4). Main Menu → Configuration → System → General Table 4-4. General System Options Test Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether or not loopback and pattern tests have a duration after which they are terminated automatically. Enable – All Loopback and Pattern tests have a timeout.
Configuration Options Configuring the Physical Interfaces Characteristics for the following physical interfaces can be configured: H Network Data Port Physical Interface Options H User Data Port Physical Interface Options Configuring the Network Data Port Select Physical to display or change the physical configuration options for the port being used as the network interface (see Table 4-5). Main Menu → Configuration → Network → Physical The network data port physical interface acts as a DTE.
Configuration Options Table 4-5. Network Data Port Physical Interface Options (2 of 2) Monitor DSR Possible Settings: Enable, Disable Default Setting: Enable Specifies whether the state of the DCE Ready (DSR) circuit on the network data port will be used to determine when valid data communication is possible with the unit. When this condition is detected, an alarm is generated, LMI is declared down, and no further transfer of frame relay data can occur on this interface.
Configuration Options Configuring the User Data Port Select Physical to display or change the physical characteristics of the user data port connected to the DTE (see Table 4-6). Main Menu → Configuration → Data Ports → Physical The data rate of the user data port is automatically set to the rate of the network interface. Table 4-6. User Data Port Physical Interface Options (1 of 2) Port Type Possible Settings: E530, V.35, X.21 Default Setting: V.
Configuration Options Table 4-6. User Data Port Physical Interface Options (2 of 2) Invert Transmit Clock Possible Settings: Auto, Enable, Disable Default Setting: Auto Determines whether the clock supplied by the FrameSaver unit on interchange circuit DB (ITU 114) – Transmit Signal Element Timing (DCE Source) TXC is phase inverted with respect to the clock used to time the incoming Transmitted Data (TD). Display Conditions – This option does not appear for Model 9820-45M.
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-7). Main Menu → Configuration → [Network/Data Ports] → Frame Relay See Configuring Frame Relay and LMI for the System for additional information. Table 4-7.
Configuration Options Table 4-7. Interface Frame Relay Options (2 of 3) LMI Parameters Possible Settings: System, Custom Default Setting: System Allows you to use the system LMI options, or to set specific LMI options for this interface. System – Use system LMI options (see Table 4-2, System Frame Relay and LMI Options). Custom – Use the following options in this table to configure LMI parameters.
Configuration Options Table 4-7. Interface Frame Relay Options (3 of 3) LMI Heartbeat (T1) Possible Settings: 5, 10, 15, 20, 25, 30 Default Setting: 10 Configures the LMI-defined T1 parameter, which sets the number of seconds between the initiation of status enquiry messages on the user side of the LMI. Applies to the user side of a UNI only. 5 – 30 – Specifies the number of seconds between the initiation of status enquiry messages in increments of 5.
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-8). Main Menu→ Configuration→ [Network/Data Ports]→ DLCI Records Typically, DLCI Records only need to be configured when building Management PVCs between the NOC and the central site unit; the unit automatically configures non-management DLCI Records and PVC Connections. Table 4-8.
Configuration Options Table 4-8. DLCI Record Options (2 of 3) CIR (bps) Possible Settings: For FrameSaver SLV 9820: 0 – 128000 For FrameSaver SLV 9820-2M: 0 – 2048000 For FrameSaver SLV 9820-8M: 0 – 8128000 For FrameSaver SLV 9820-45M: 0 – 44210000 Default Setting: 64000 Determines the data rate for the DLCI that the network commits to accept and carry without discarding frames; the CIR in bits per second.
Configuration Options Table 4-8. DLCI Record Options (3 of 3) Excess Burst Size (Bits) Specifies the maximum amount of data in bits that the network may accept beyond the CIR without discarding frames.
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-9). Main Menu → Configuration → PVC Connections From this screen, you can go directly to the Management PVC screen by selecting the MgmtPVCs function key for easy movement between screens.
Configuration Options Table 4-9. PVC Connection Options (2 of 3) Primary Destination Link Possible Settings: Net1-FR1 Default Setting: Initially blank; no default. Specifies the frame relay interface used as the primary destination link; the to end of a from-to link. The only valid settings for this configuration option are frame relay interfaces that have at least one DLCI or EDLCI defined which are not part of a PVC connection or management link.
Configuration Options Table 4-9. PVC Connection Options (3 of 3) AlternateDestination DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the alternate destination DLCI for a frame relay interface. The DLCI must be defined and cannot be part of a PVC connection or management link. For multiplexed DLCIs, at least one EDLCI must be unconnected for the DLCI to be a valid selection.
Configuration Options Setting Up Management and Communication Options The following options can be selected from the Management and Communication menu: H Node IP Options H Management PVC Options H General SNMP Management Options H Telnet and FTP Sessions Options H SNMP NMS Security Options H SNMP Traps and Trap Dial-Out Options H Ethernet Port Options (Model 9820-45M) H Communication Port Options H External Modem (COM Port) Options (Models 9820, 9820-2M, 9820-8M) H Modem Port Options (Mo
Configuration Options Table 4-10. Node IP Options (1 of 3) Node IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address needed to access the node. Since an IP address is not bound to a particular port, it can be used for remote access via a management PVC. On the Model 9820-45M, this address may be shared only among management PVCs. On Models 9820, 9820-2M, and 9820-8M this address may also be used to access the COM port. 001.
Configuration Options Table 4-10. Node IP Options (2 of 3) Default IP Destination Possible Settings (Models 9820, 9820-2M, 9820-8M): None, COM, PVCname Possible Settings (Model 9820-45M): None, Modem, Ethernet, COM, PVCname Default Setting: None Specifies an IP destination to route data that does not have a specifically defined route. Examples: H If the default IP network is connected to the communications port, select COM.
Configuration Options Table 4-10. Node IP Options (3 of 3) TS Management Link Available Settings: None, PVCname Default Setting: None Specifies a troubleshooting management link for the special needs of network service providers. If the option is changed from the management PVC name to None, the Delete the Management PVC PVCname and the associated DLCI Record? prompt appears. If you select: H No – The link designation is removed and the option is set to None.
Configuration Options Configuring Management PVCs Select Management PVCs to define inband management links by adding or changing Management PVCs (see Table 4-11). First, DLCI records must have been configured for the interface where the Management PVC will reside. See Manually Configuring DLCI Records for additional information. Main Menu → Configuration → Management and Communication → Management PVCs Select New or M o dify to add or change Management PVCs.
Configuration Options Table 4-11. Management PVC Options (2 of 4) Intf Subnet Mask Possible Settings: Node-Subnet-Mask, Calculate, Special (nnn.nnn.nnn.nnn) Default Setting: Node-Subnet-Mask Specifies the subnet mask needed to access the unit when the management PVC is providing connectivity to an external IP network (through frame relay) that requires a specific subnet mask for the interface.
Configuration Options Table 4-11. Management PVC Options (3 of 4) Primary DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the DLCI number used for the management PVC after the frame relay interface is selected. The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be part of a PVC connection or already assigned as a management PVC. For multiplexed DLCIs, at least one EDLCI must be unconfigured for the DLCI.
Configuration Options Table 4-11. Management PVC Options (4 of 4) Alternate Link Possible Settings: Net1-FR1 Default Setting: Initially blank; no default. Specifies the alternate frame relay interface to use for this management PVC if the primary link has failed. 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. Display Conditions – This option appears only for Model 9820-45M.
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-12). Main Menu → Configuration → Management and Communication → General SNMP Management Table 4-12.
Configuration Options Configuring Telnet and/or FTP Session Support Telnet and FTP options control whether a Telnet or FTP (File Transport Protocol) session is allowed through an interconnected IP network and the access security applicable to the session. Two Telnet sessions can be active at a time (see Table 4-13).
Configuration Options Table 4-13. Telnet and FTP Session Options (2 of 3) Session Access Level Possible Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies the highest security level allowed when accessing the menu-driven user interface via a Telnet session. If a login is required for the session, the effective access level is also determined by the user’s access level. When a login is not required, the effective access level is determined by this option.
Configuration Options Table 4-13. Telnet and FTP Session Options (3 of 3) FTP Session Possible Settings: Enable, Disable Default Setting: Enable Determines whether the system responds as a server when an FTP (file transfer protocol) client on an interconnected IP network requests an FTP session. This option must be enabled when downloading files. Enable – Allows an FTP session between the system and an FTP client. Disable – Does not allow FTP sessions.
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-14). Main Menu → Configuration → Management and Communication → SNMP NMS Security A table is displayed consisting of the network management systems identified by IP address that are allowed to access the FrameSaver unit by SNMP. Table 4-14.
Configuration Options Configuring SNMP Traps and Trap Dial-Out Select SNMP Traps from the Management and Communication menu to configure SNMP traps and dial-out when a trap is generated (see Table 4-15). Dial-out is not available on the Model 9820-45M.
Configuration Options Table 4-15. SNMP Traps and Trap Dial-Out Options (2 of 5) Initial Route Destination Possible Settings: AutoRoute, COM, PVCname Default Setting: AutoRoute Specifies the initial route used to reach the specified Trap Manager. When proprietary RIP is active, only one unit in the network needs to specify an interface or management link as the initial destination. All other units can use the default setting.
Configuration Options Table 4-15. SNMP Traps and Trap Dial-Out Options (3 of 5) Link Traps Possible Settings: Disable, Up, Down, Both Default Setting: Both Determines whether SNMP linkDown or linkUp traps are sent to the currently configured trap manager(s). A linkDown trap indicates that the unit recognizes a failure in one of the interfaces. A linkUp trap indicates that the unit recognizes that one of its interfaces is active.
Configuration Options Table 4-15. SNMP Traps and Trap Dial-Out Options (4 of 5) Trap Dial-Out Possible Settings: Enable, Disable Default Setting: Disable Controls whether SNMP trap messages initiate a call automatically. If the call cannot be completed and the Call Retry option is set to Enable, the SNMP trap message is held (queued) until the call completes to either the Alarm or alternate directory. Display Conditions – This option does not appear for Model 9820-45M.
Configuration Options Table 4-15. SNMP Traps and Trap Dial-Out Options (5 of 5) Alternate Dial-Out Directory Possible Settings: None, 1 – 5 Default Setting: None Specifies whether an incomplete call (busy, or no answer, etc.) resulting from an attempt to send an SNMP trap message is retried using an alternate telephone number. Up to 5 alternate call directories can be set up, but only one at a time can be used. When Call Retry is enabled, the alarm directory’s telephone number is called first.
Configuration Options Configuring the Ethernet Port (Model 9820-45M) Select Ethernet Port from the Management and Communication menu to display or change the Ethernet port configuration options (see Table 4-16). Main Menu → Configuration → Management and Communication → Ethernet Port The Ethernet port is initially disabled. When Interface Status is changed to Enable, the message Would you like to set the Node’s Default IP Destination to Ethernet? appears.
Configuration Options Table 4-16. Ethernet Port Options (2 of 2) Default Gateway Address Possible Settings: 000.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies an address for packets sent out the Ethernet port that do not have a route. 000.000.000.000 – 223.255.255.255 – Shows the Default Gateway Address, which you can view or edit. The first three digits may not be 127. Clear – Clears the Default Gateway Address to 000.000.000.000.
Configuration Options Configuring the Communication Port Select Communication Port from the Management and Communication menu to display or change the COM port (Terminal port on the Model 9820-45M) configuration options (see Table 4-17). Main Menu → Configuration → Management and Communication → Communication Port Table 4-17. Communication Port Options (1 of 5) Port Use Possible Settings: Terminal, Net Link Default Setting: Terminal Assigns a specific use to the COM (Terminal) port.
Configuration Options Table 4-17. 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 (Terminal) 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.
Configuration Options Table 4-17. 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 (Terminal) 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.
Configuration Options Table 4-17. 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 (Terminal) port. Only in effect when the COM (Terminal) 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.
Configuration Options Table 4-17. Communication Port Options (5 of 5) RIP Possible Settings: None, Proprietary, Standard_out Default Setting: None Specifies which Routing Information Protocol (RIP) is used to enable routing of management data between devices. Display Conditions – This option only appears when Port Use is set to Net Link. None – No routing is used. Proprietary – (Models 9820, 9820-2M, 9820-8M.
Configuration Options Configuring the COM Port to Support an External Modem (Models 9820, 9820-2M, 9820-8M) For all models except Model 9820-45M, select External Modem (Com Port) to display or change the configuration options that control call processing for an external device attached to the COM port (see Table 4-18).
Configuration Options Table 4-18. External Modem (COM Port) Options (2 of 2) Alternate IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the Alternate IP Address for the COM port when the alternate phone directory is used. If this configuration option is not configured (i.e., it is zero), the COM port’s primary IP Address is used when the alternate telephone directory is used.
Configuration Options Configuring the Modem Port (Model 9820-45M) Select Modem Port from the Management and Communication menu to display or change the Modem port configuration options (see Table 4-19). Main Menu → Configuration → Management and Communication → Modem Port Table 4-19. Modem Port Options (1 of 3) Port Use Possible Settings: Terminal, Net Link Default Setting: Terminal Assigns a specific use to the Modem port.
Configuration Options Table 4-19. Modem Port Options (2 of 3) Port Access Level Possible Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies level of user access privilege for the asynchronous terminal interface accessed through the Modem 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.
Configuration Options Table 4-19. Modem Port Options (3 of 3) IP Address Possible Settings: 000.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 Modem port. Only in effect when the Modem 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.
Configuration Options This page intentionally left blank.
Security and Logins 5 This chapter includes the following: H Limiting Access H Controlling Asynchronous Terminal Access H Controlling External COM Port Device Access (Models 9820, 9820-2M, 9820-8M) H Controlling Modem Port Device Access (Model 9820-45M) H Controlling Telnet or FTP Access — Limiting Telnet Access — Limiting FTP Access — Limiting Telnet or FTP Access Over the TS Management Link H Controlling SNMP Access — Disabling SNMP Access — Assigning SNMP Community Names and Access Levels — L
Security and Logins Limiting Access The FrameSaver unit provides access security on the following interfaces: H Asynchronous (async) terminal H External devices H Telnet H FTP H SNMP Up to two direct or Telnet sessions can be active at any given time; that is, you can have two simultaneous Telnet sessions, or one Telnet session and one active asynchronous terminal session, or two simultaneous asynchronous terminal sessions.
Security and Logins Controlling Asynchronous Terminal Access Asynchronous terminal access to the menu-driven user interface can be limited by: H Requiring a login. H Assigning an access level to the port or interface. " Procedure To limit asynchronous terminal access to the menu-driven user interface: 1. Select the appropriate configuration options screen.
Security and Logins Controlling External COM Port Device Access (Models 9820, 9820-2M, 9820-8M) Dial-in access can be controlled on Models 9820, 9820-2M, and 9820-8M when an external device (modem) is connected to the unit’s communication (COM) port. The External Device Commands option must be set to AT or Other. " Procedure To control dial-in access: 1. Select the External Modem options. Main Menu → Configuration → Management and Communication → External Modem (Com Port) 2.
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: H Disabling Telnet access completely. H Requiring a login for Telnet sessions that are not on the TS Management Link. H Assigning an access level for Telnet sessions.
Security and Logins Limiting FTP Access FTP access can be limited by: H Disabling FTP access completely. H Requiring a user ID and password to login. H Limiting FTP bandwidth. (Models 9820, 9820-2M, 9820-8M.) " Procedure To limit FTP access when the session is not on the TS Management Link: 1. Select the Telnet and FTP Session options. Main Menu → Configuration → Management and Communication → Telnet and FTP Sessions 2. Set the following configuration options, as appropriate. To . . .
Security and Logins Limiting Telnet or FTP Access Over the TS Management Link " Procedure To limit Telnet or FTP access when the session is on the TS Management Link: 1. Select the Telnet and FTP Session options. Main Menu → Configuration → Management and Communication → Telnet and FTP Sessions 2. Disable Telnet Session and/or FTP Session, as appropriate. 3. Return to the Management and Communication menu, and select Node IP. 4. Set the following configuration options, as appropriate. To . . .
Security and Logins Controlling SNMP Access The FrameSaver unit supports SNMP Version 1, which provides limited security through the use of community names. There are three methods for limiting SNMP access: H Disabling SNMP access. H Assigning SNMP community names and the access type. H Assigning IP addresses of those NMSs that can access the unit. Disabling SNMP Access When the SNMP access is disabled, the FrameSaver unit will not respond to SNMP messages. " Procedure To disable SNMP access: 1.
Security and Logins Assigning SNMP Community Names and Access Levels The FrameSaver unit supports the SNMP protocol and can be managed by an SNMP manager. SNMP manager access can be limited by: H Assigning the SNMP community names that are allowed to access the FrameSaver unit’s Management Information Base (MIB). H Specifying the type of access allowed for each SNMP community name. Whenever an SNMP manager attempts to access an object in the MIB, the community name must be supplied.
Security and Logins Limiting SNMP Access Through IP Addresses An additional level of security is provided by: H Limiting the IP addresses of NMSs that can access the FrameSaver unit. H Performing validation checks on the IP address of SNMP management systems attempting to access the FrameSaver unit. H Specifying the access allowed for the authorized NMS when IP address validation is performed.
Security and Logins See Configuring SNMP NMS Security Options in Chapter 4, Configuration Options, for more information about SNMP NMS Security configuration options. Creating a Login A login is required if security is enabled. (Security is enabled by the configuration options Login Required for the communication port, and Telnet Login Required or FTP Login Required for a Telnet or FTP Session.
Security and Logins See Configuring SNMP NMS Security in Chapter 4, Configuration Options, for more information about security configuration options. Modifying a Login Logins are modified by deleting the incorrect login and creating a new one. Deleting a Login " Procedure To delete a login record: 1. Select Administer Logins. Main Menu → Control → Administer Logins 2. Page through login pages / records using the PgUp or PgDn function keys until the login to be deleted is displayed. 3. Select De l ete.
Monitoring 6 This chapter includes the following: H Displaying System Information H Front Panel LEDs — Front Panel Status LEDs H Displaying LEDs and Control Leads — Display LEDS and Control Leads Screen (Models 9820, 9820-2M, 9820-8M) — Display LEDs and Control Leads Screen (Model 9820-45M) H Power Module LEDs (Model 9820-45M) H Device Messages H Status Information H System and Test Status Messages, which includes: — Self-Test Results Messages — Health and Status Messages — Test Status Message
Monitoring 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.
Monitoring Front Panel LEDs The FrameSaver SLV 9820 unit’s faceplate includes LEDs ( light-emitting diodes) that provide status on the FrameSaver unit, its network data port, and its user data port. K PORT O K NETWORK O TS T FrameSaver® SLV AL M O K 9820-2M TM 00-16201a-01 Figure 6-1.
Monitoring Front Panel Status LEDs Table 6-1. System Status LEDs Label Indication Color What It Means OK Power and Operational Status Green ON – FrameSaver unit has power and it is operational. Operational Alarm ( Fail ) Red ALM OFF – FrameSaver unit is in a power-on self-test, or there is a failure. ON – FrameSaver unit has just been reset, or an error or fault has been detected.
Monitoring Table 6-2. NETWORK Status LEDs Label Indication Color What It Means OK Operational Status Green (Models 9820, 9820-2M, 9820-8M) ON – The interchange circuits for the port are in the correct state to transmit and receive data. OFF – The port is idle. Occurs if the port is configured to monitor DSR, CTS, or RLSD and the leads are not asserted, or TM is asserted on the DCE, or a valid clock signal cannot be detected on the port.
Monitoring Displaying LEDs and Control Leads The Display LEDs and Control Leads screen allows you to monitor a remote unit and is useful when troubleshooting control lead problems. The appropriate interfaces are shown on this screen, with the appropriate status highlighted. Main Menu → Status → Display LEDs and Control Leads Refresh the screen to view control lead transitions. LED and control lead descriptions are in the sections that follow.
Monitoring Table 6-5. Network and User Data Port LEDs and Control Leads Label Indication What It Means Both Network and User Data Ports OK Operational Status The data port is operational. TXD Transmit Data Data is being sent to the far-end device on the data port. RXD Receive Data Data is being received from the far-end device on the data port. Additional Network Data Port Control Leads RLSD Receiver Line Signal Detector If Port Type is set to V.
Monitoring Display LEDs and Control Leads Screen (Model 9820-45M) ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ Display LEDs & Control Leads
Monitoring Table 6-7. Network and User Data Port Control Leads Label Indication What It Means Both Network and User Data Ports TD Transmit Data Data is being transmitted on the circuit. RD Receive Data Data is being received on the circuit. DTR Data Terminal Ready Shows the current state of the DTR control lead. DSR Data Set Ready Shows the current state of the DSR control lead.
Monitoring Power Module LEDs (Model 9820-45M) Each power module has a green LED which remains lit while power is applied and the power module is functioning. When the yellow front panel System PWR LED is lit, one of the power modules has failed. The failed power module can be identified from the back of the DSU by its unlit LED. Table 6-8. Power Module Troubleshooting Configuration Symptom What to Do (in order, if problem persists) One Power Module 1. Verify that the receptacle in use provides 120 Vac.
Monitoring Device Messages These messages appear in the messages area at the bottom of the screens. All device messages are listed in alphabetical order. Table 6-9. Device Messages (1 of 5) Message What It Indicates What To Do Access level is n , Configuration is Read-only. The user’s access level is 2 or 3; the user is not authorized to change configurations. No action needed. Already Active The test selected is already running. H Allow test to continue. H Select another test. H Stop the test.
Monitoring Table 6-9. Device Messages (2 of 5) Message What It Indicates What To Do File Transfer Failed – Invalid file A file transfer was attempted, but it was not successful. H Try again, making sure you (Seen at an FTP terminal.) type the filename correctly. H Exit the FTP session, or download another file. See Changing Software in Chapter 7, FTP Operation. Invalid Character (x ) An invalid character was entered. Reenter information using valid printable ASCII characters.
Monitoring Table 6-9. Device Messages (3 of 5) 9820-A2-GB20-20 Message What It Indicates What To Do Limit of PVC Connections reached New was selected from the PVC Connection Table and the maximum number of PVCs has already been created. H Do not create the PVC Link Inactive You attempted to start a PVC test on an inactive link. Activate the link or test a different link. Name Must be Unique Name entered for a management PVC has been used previously.
Monitoring Table 6-9. Device Messages (4 of 5) Message What It Indicates What To Do Not enough circuits available A new TS Access DLCI was selected, but the maximum number of network DLCIs or management PVCs has already been created. Delete a DLCI, then create the new DLCI. Note: This PVC has been designated as the TS Management Link The Management PVC you displayed is defined as the TS Management Link. No action needed. The PVC cannot be modified.
Monitoring Table 6-9. Device Messages (5 of 5) Message What It Indicates What To Do Test Active No higher priority health and status messages exist, and a test is running. H Contact service provider if test initiated by the network. H Wait until the test ends and message clears. H Cancel all tests from the Test screen ( Path: main/test ). H Stop the test from the same screen the test was started from.
Monitoring Status Information Status information is useful when monitoring the FrameSaver unit. The following illustration shows the Status menu for the FrameSaver unit.
Monitoring System and Test Status Messages System and test status information is selected from the Status menu. Main Menu → Status → System and Test Status The following information is included on this screen: H Self-Test Results Messages H Health and Status Messages H Test Status Messages Self-Test Results Messages These self-test result messages appear in the Self-Test Results field at the top of the System and Test Status screen. Table 6-10.
Monitoring Health and Status Messages The following table provides Health and Status messages that apply to the FrameSaver unit. Table 6-11. Health and Status Messages (1 of 2) Message What It Indicates Auto-Configuration Active Auto-Configuration feature is active, which allows automatic configuration and cross-connection of DLCIs as they are reported by the network LMI.
Monitoring Table 6-11. Health and Status Messages (2 of 2) Message What It Indicates Ethernet Link Down (Model 9820-45M) The Ethernet port is administratively enabled, but communication is not possible. Fan Failure (Model 9820-45M) At least one fan has failed. Link Down Administratively, frame relay link 2 The specified frame relay link has been disabled by the unit due to LMI Behavior conditions or LMI Protocol on another link is in a failed state.
Monitoring 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 6-12. Test Status Messages Message What It Indicates DTE External LB Active, Port-1 An external DTE Loopback is running on the user data port. DTE Init.
Monitoring 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.
Monitoring Table 6-13. 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 ).
Monitoring PVC Connection Status PVC connection statuses are selected from the Status menu. Main Menu → Status → PVC Connection Status Only PVC connections with Source DLCIs configured to be Active are shown.
Monitoring Table 6-14. PVC Connection Status (2 of 2) Field Status What It Indicates DLCI 16 to 1007 For standard DLCIs. Identifies an individual link/ connection embedded within a DLCI. EDLCI 0 to 62 For multiplexed DLCIs only. Identifies an individual link/ connection embedded within a DLCI. Status Identifies whether the physical interfaces, LMIs, and DLCIs are all enabled and active for this PVC connection. Active 1 H The PVC is currently active.
Monitoring Network Interface Status Network Interface Status can be selected from the Status menu.
Monitoring IP Routing Table (Model 9820-45M) The IP Routing Table display is selected from the Status menu.
Monitoring Table 6-16. IP Routing Table (2 of 2) Field What It Indicates Interface The interface used to get to the destination: COM – The COM (Terminal) port is used. Modem – The Modem port is used. Ethernet – The Ethernet port is used. PVCname – The specified management PVC is used. Internal – An internal route is used (for loopbacks or internal functions). TTL 9820-A2-GB20-20 Time To Live, in seconds. TTL can have a value 1–999.
Monitoring 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.
Monitoring 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.
Monitoring Service Level Verification Performance Statistics These statistics appear when Service Level Verification (SLV) is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Service Level Verification They only appear for the network interface and only if DLCIs are multiplexed. Table 6-17.
Monitoring Table 6-17. Service Level Verification Performance Statistics (2 of 2) Statistic What It Indicates Inbound Dropped Characters Total number of bytes transmitted by the far-end device that were dropped in transit. The counts continue to increment until the maximum value is reached (232 –2), then the count starts over. The SLV Delivery Ratio option (see Table 4-3, Service Level Verification Options) must be enabled for these statistics to appear.
Monitoring The statistics collected by the unit depend upon the device at the far end of the connection. If the far-end device is a FrameSaver SLV unit, frame relay, latency, Frame Relay Delivery Ratio (FDR), and Data Delivery Ratio (DDR) performance statistics are collected. If the far-end device is a non-FrameSaver device, or a FrameSaver 9120 or 9620, only frame relay statistics are collected.
Monitoring Table 6-18. DLCI Performance Statistics (2 of 2) Statistic What It Indicates H With BECN Set H The number of frames and octets sent on the selected DLCI of the frame relay link with backward explicit congestion notifications. BECNs are sent to notify users of data traffic congestion in the opposite direction of the frame carrying the BECN indicator. 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.
Monitoring Frame Relay Performance Statistics The following statistics appear when Frame Relay is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Frame Relay All counts continue to increment until the maximum value is reached (232 –2), then the count starts over. The NextLink and PrevLink function keys only appear when multiple frame relay links have been configured. Table 6-19.
Monitoring Table 6-19. Frame Relay Performance Statistics (2 of 3) Statistic What It Indicates Frame Relay Errors (cont’d) Short Rx Frames The number of frames received over the Network or Port-1 interface that were less than 5-octets ( five 8-bit bytes) in length. There may be a non-frame relay device on the other end of the link. Long Rx Frames The number of frames received over the Network or Port-1 interface that were more than 8192-octets in length.
Monitoring Table 6-19. Frame Relay Performance Statistics (3 of 3) Statistic What It Indicates Frame Relay HDLC Errors Rx Total Errors The number of receiver errors on the interface. The following are included in this count: H Receive invalid frames (short frames, long frames, invalid DLCIs, unknown DLCIs, and unknown errors) H Rx Total Discards H Receive errors (non-octet aligned frames, frames with CRC errors, and Rx Overruns) Rx Total Discards The number of receiver discards on the interface.
Monitoring Ethernet Performance Statistics (Model 9820-45M) The following statistics appear when Ethernet is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Ethernet All counts continue to increment until the maximum value is reached (232 –2), then the count starts over. Table 6-20. Frame Relay Performance Statistics Field or Statistic What It Indicates Port Rate (Mbps) The operating rate detected on the Ethernet interface.
Monitoring Trap Event Log (Model 9820-45M) The Trap Event Log display is selected from the Status menu.
FTP Operation 7 This chapter includes the following: H FTP File Transfer — Upgrading System Software — Determining Whether a Download is Completed — Changing Software — Transferring Collected Data 9820-A2-GB20-20 June 2000 7-1
FTP Operation FTP File Transfer 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.
FTP Operation " 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 5, Security and Logins), you are prompted to enter them. If not, press Enter. The FTP prompt appears. The starting directory is the root directory ( / ). Use standard FTP commands during the FTP session, as well as the following remote FTP commands.
FTP Operation 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 (Terminal) port if Port Use is set to Net Link (see Table 4-17, Communication Port Options). " Procedure To download software: 1. Initiate an FTP session to the device that you are upgrading. 2.
FTP Operation Determining Whether a Download Is Completed To see whether a download has completed, check the Identity screen. Main Menu → Status → Identity Check Alternate Software Rev. under the NAM Identity column. H If a software revision number appears, the file transfer is complete. H If In Progress appears, the file is still being transferred. H If Invalid appears, no download has occurred or the download was not successful.
FTP Operation 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. For Models 9820, 9820-2M, and 9820-8M, the rate at which the data file is transferred is the rate set by the FTP Max Receive Rate (Kbps) option (see Table 4-13, Telnet and FTP Session Options in Chapter 4, Configuration Options). For Model 9820-45M, the rate is fixed.
Troubleshooting 8 This chapter includes the following: H Problem Indicators H Resetting the Unit and Restoring Communication — Resetting the Unit from the Control Menu — Resetting the Unit By Cycling the Power — Restoring Communication with an Improperly Configured Unit H Troubleshooting Management Link Feature H LMI Packet Capture Utility Feature — Viewing Captured Packets from the Menu-Driven User Interface H Alarms H Troubleshooting Tables — Device Problems — Frame Relay PVC Problems H Test
Troubleshooting H Physical Tests — DTE Loopback H IP Ping Test H Lamp Test Problem Indicators The unit provides a number of indicators to alert you to possible problems: Indicators . . . See . . . LEDs Displaying LEDs and Control Leads and Front Panel LEDs in Chapter 6, Monitoring, as well as the user interface screen. Main Menu → Status → Display LEDs and Control LEDs Health and Status Health and Status Messages in Chapter 6, Monitoring.
Troubleshooting Resetting the Unit and Restoring Communication You can reset the unit in one of four ways: H Reset it from the Control menu. H Cycle the power. H Reset the configuration options for the COM (Terminal) port, or reload the factory default settings. H Set the appropriate MIB object from NMS (see your NMS documentation). The unit performs a self-test when it is reset. Resetting the Unit from the Control Menu Use this procedure to initiate a reset and power-on self-test of the unit.
Troubleshooting Restoring Communication with an Improperly Configured Unit Configuring the unit improperly can 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 (Terminal) port settings: 1. Configure the asynchronous terminal to operate at 19.2 kbps, using character length of 8 bits, with one stop-bit, and no parity. In addition, set Flow Control to None. 2.
Troubleshooting Troubleshooting Management Link Feature A dedicated troubleshooting management link is available to help service providers isolate device problems within their networks. This feature allows Telnet or FTP access to the unit on this link and troubleshooting over this link is essentially transparent to customer operations. No alarms or SNMP traps are generated to create nuisance alarms for the customer.
Troubleshooting Viewing Captured Packets from the Menu-Driven User Interface The twelve most recent LMI events are stored in the trace log. Once the capture buffer or trace log is full, the oldest packets are overwritten.
Troubleshooting Alarms The following table describes the alarm conditions that will generate an SNMP trap for a physical interface, and the frame relay LMIs and DLCIs. These alarm conditions also generate Health and Status messages seen on the System and Test Status screen. Main Menu → Status → System and Test Status Table 8-1.
Troubleshooting Table 8-1. Alarm Conditions (2 of 4) Alarm Condition What It Indicates What To Do DTR Down from Port-1 Device The DTR control lead on the device connected to Port-n is off. Examine the attached DTE and cable connected to the FrameSaver unit’s port. H Check that the Port-1 cable is securely attached at both ends. H Check the status of the attached equipment. Fan Failure (9820-45M) 8-8 One of the fans has failed. June 2000 Notify your service representative.
Troubleshooting Table 8-1. Alarm Conditions (3 of 4) Alarm Condition What It Indicates What To Do LMI Down, frame relay link 2 The Local Management Interface is down for the specified frame relay link. For the network data port: H If LMI was never up, verify that the LMI Protocol setting reflects the LMI type being used. H If LMI was never up: – Verify that the proper time slots have been configured. – Verify that the LMI Protocol setting reflects the LMI type being used.
Troubleshooting Table 8-1. Alarm Conditions (4 of 4) Alarm Condition What It Indicates What To Do LOS at Network 1 A Loss of Signal (LOS) condition is detected. Either the control leads on the network data port are deasserted, the TM lead is asserted, or no clock is detected from the NTU. H Check that the network cable is securely attached at both ends. H Contact your network provider. H Network cable problem. H No signal is being transmitted at the far-end FrameSaver unit.
Troubleshooting Troubleshooting Tables The unit is designed to provide many years of trouble-free service. However, if a problem occurs, refer to the appropriate table in the following sections for possible solutions. Device Problems Table 8-2. Device Problems (1 of 2) Symptom Possible Cause Solutions No power, or the LEDs are not lit. The power cord is not securely plugged into the wall receptacle to rear panel connection. Check that the power cord is securely attached at both ends.
Troubleshooting Table 8-2. Device Problems (2 of 2) Symptom Possible Cause Solutions Failure xxxxxxxx appears at the top of the System and Test Status screen, at Self-Test Results. The unit detects an internal software failure. H Record the 8-digit code from the System and Test Status screen. H Reset the unit and try again. H Contact your service representative and provide the 8-digit failure code. An LED appears dysfunctional. LED is burned out. Run the Lamp Test.
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. H Verify that the DLCI(s) is active on the PVC Connection Status screen. If the DLCI(s) is not active, contact the service provider.
Troubleshooting Tests Available The following tests are available to a FrameSaver SLV 9820 model.
Troubleshooting Starting and Stopping a Test Use this procedure to start, monitor, or abort specific tests. To abort all active tests on all interfaces, see Aborting All Tests. When the status of a test is . . . The only command available is . . . Inactive Start Active Stop Start or stop an individual test using the same procedure. " Procedure To start and stop a test: 1. Follow this menu selection sequence: Main Menu → Test 2.
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. " 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.
Troubleshooting PVC Tests PVC tests can be run on a requested DLCI for a selected interface. H When PVC tests are on a multiplexed DLCI between FrameSaver devices, they are nondisruptive to data, so user data can continue to be sent during a test. H If the device at one end of the circuit is not a FrameSaver device, PVC tests are on a standard DLCI and are disruptive to data. Also, the Connectivity test would not appear.
Troubleshooting Network or Port (Internal) PVC Loopback The PVC Loopback loops frames back to the selected interface on a per-PVC basis. This test logically (not physically) loops back frames received from another FrameSaver device through the selected frame relay PVC to the same device.
Troubleshooting Monitor Pattern This test monitors packets filled with a hexadecimal 55 test pattern and sequence number over the selected interface and DLCI to another FrameSaver device. To monitor a pattern test on a link: Main Menu → Test → [Network PVC Tests/Data Port PVC Tests] → Monitor Pattern The current number of sequence and data errors are shown under the Result column when the FrameSaver unit is in sync. An Out of Sync message appears when 5 frames out of 25 are missing or out of sequence.
Troubleshooting Physical Tests Physical Tests can be commanded for the user data port. CAUTION: You should not run these tests with frame relay equipment attached; you must disconnect the frame relay equipment and use external test equipment. DTE Loopback The DTE external Loopback (DTLB) test loops the received signal on a user data port back to the DTE. Use this test for isolating problems on the user data port. An attached device or test equipment must generate data to be looped back.
Troubleshooting IP Ping Test An IP Ping test can be run to test connectivity between the FrameSaver unit and any FrameSaver device, router, or NMS to which it has a route. Times when you might want to run an IP Ping test are: H To test connectivity between the FrameSaver unit and any FrameSaver device in the network to verify that the path is operational. Select Procedure 1 to ping any far-end FrameSaver device.
Troubleshooting " Procedure 2 To ping the NMS at the central site: 1. Verify that the central site NMS has the FrameSaver unit’s IP address in its routing table so it can communicate with the FrameSaver unit. 2. Verify that the central site NMS’s router has the FrameSaver unit’s IP address in its routing table so it can communicate with the FrameSaver unit. 3.
Setting Up OpenLane for FrameSaver Devices 9 This chapter includes: H OpenLane Support of FrameSaver Devices H Setting Up the OpenLane SLM System H Setting Up FrameSaver SLV Support OpenLane Support of FrameSaver Devices Paradyne’s OpenLane Service Level Management (SLM) system supports all FrameSaver and FrameSaver SLV devices with the following features: 9820-A2-GB20-20 H Web and database services H Web access to health and status information H Web access to real-time, as well as historical
Setting Up OpenLane for FrameSaver Devices Setting Up the OpenLane SLM System Instructions for installing Paradyne’s OpenLane Service Level Management (SLM) System can be found in the following documents: H OpenLane 5.x Service Level Management for UNIX Quick Start Installation Instructions H OpenLane 5.x Service Level Management for Windows NT Quick Start Installation Instructions See Product-Related Documents in About This Guide for document numbers. Select the appropriate document.
Setting Up NetScout Manager Plus for FrameSaver Devices 10 This chapter includes NetScout Manager Plus information as it relates to FrameSaver SLV devices.
Setting Up NetScout Manager Plus for FrameSaver Devices Getting Started Before configuring NetScout Manager Plus, you need to copy some OpenLane directories to a NetScout Manager Plus user directory. OpenLane provides these directories as a starting point for loading new alarms and creating history files. A template of alarms and values for configuring alarms and several templates for creating history files specific to the FrameSaver unit are available.
Setting Up NetScout Manager Plus for FrameSaver Devices Configuring NetScout Manager Plus For the NetScout Manager Plus main window to appear, make sure your environment is set up exactly as specified in your NetScout Readme file. You need to: H Copy the OpenLane directory to a user directory. H Add frame relay agents to the NetScout Manager. In addition, for Models 9820 and 9820-2M you need to: H Configure agent properties. H Verify and correct domains and groups. H Monitor the agent and DLCIs.
Setting Up NetScout Manager Plus for FrameSaver Devices Adding FrameSaver SLV Units to the NetScout Manager Plus Network " Procedure 1. Bring up the NetScout Manager Plus main window. 2. Select the FrameRelay radio button from the agent type selection bar (on the left side of the window). A list of configured frame relay agents appear in the list box below the Name and IP Address headings.
Setting Up NetScout Manager Plus for FrameSaver Devices Verifying Domains and Groups (Models 9820 and 9820-2M) " 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.
Setting Up NetScout Manager Plus for FrameSaver Devices Correcting Domains and Groups (Models 9820 and 9820-2M) Properties need to be edited when not using the Paradyne-provided file and when: H An unsupported domain needs to be deleted. H A missing domain needs to be added. H Groups, Samples, Interval, and Logging are not configured as specified in Step 3 of Verifying Domains and Groups. " Procedure 1. Select the the Property... button (down the center of the Configuration Manager main window).
Setting Up NetScout Manager Plus for FrameSaver Devices 3. To add a FrameSaver SLV-supported domain or correct property settings, select the Edit... button (to the right of the Domain section of the Property Editor window). The Edit Domain window opens. 4. Click on the domain from the Domains list and configure the following: Property Description Setting Groups Stats (S) Statistics collection Enabled for all domains. Hosts (H) Level 3 information (network) Enabled for IP domain only.
Setting Up NetScout Manager Plus for FrameSaver Devices Adding SLV Alarms Using a Template Once DLCIs have been discovered, SLV alarms should be configured and assigned to each DLCI. OpenLane provides a template for configuring alarms. DLCI alarms can be configured manually, but using the Paradyne alarm defaults template greatly reduces configuration time.
Setting Up NetScout Manager Plus for FrameSaver Devices Editing Alarms " Procedure 1. From the NetScout Manager Plus main window, with the FrameRelay and Admin radio buttons still selected, click on the Config Manager icon to open the Configuration Manager main window. 2. Select the Custom radio button from the Properties File area (in the upper right of the window), then Property... (down the center of the screen). The Custom Property Editor window opens. 3.
Setting Up NetScout Manager Plus for FrameSaver Devices 4. Edit any trap defaults that may be required. See Step 4 of Adding SLV Alarms Manually for field settings you may want to change. 5. Select the OK button (at the bottom of the screen) to apply your changes. The window closes and the Configuration Manager main window reappears. 6. Select the Install button (down the center of the Configuration Manager main window) to apply your changes.
Setting Up NetScout Manager Plus for FrameSaver Devices Adding SLV Alarms Manually Once DLCIs have been discovered, SLV alarms should be defined and assigned to each DLCI. When configuring alarms manually, every alarm must be configured for each DLCI; that is, if there are eight alarms and 20 DLCIs, 160 trap configurations must be created (8 x 20). For this reason, it is recommended that the OpenLane defaults be used. Follow the procedure below to configure alarms manually.
Setting Up NetScout Manager Plus for FrameSaver Devices 4. Click on the ... button to the right of indicated fields for a drop-down list from which selections can be made. Minimally, configure the following fields: Field Select or Enter . . .
Setting Up NetScout Manager Plus for FrameSaver Devices Creating History Files Up to 14 additional user history tables can be created in the FrameSaver unit for each interface. An interface is a specific DLCI or the entire frame relay interface. A table must be created for each DLCI or frame relay link to be monitored. Additional user history tables are created using the command-line prompt in NetScout Manager Plus to load a file that contains the OIDs (Object IDs) to be monitored into the unit.
Setting Up NetScout Manager Plus for FrameSaver Devices " Procedure 1. Open a terminal window and go to $NSHOME/usr. 2. Copy an example or interface-specific file to a new file that contains the user history table number. 3. Open the new file using a text editor. The variables in the file are listed with their OIDs (Object IDs). The frame relay interface number 101016002 must replace @IFN, and the DLCI number to be monitored must replace @DLCI. Example: frCircuitSentFrames Change “1.3.6.1.2.1.10.32.2.1.6.
Setting Up NetScout Manager Plus for FrameSaver Devices Installing the User-Defined History Files Once the user-defined history files have been created, the files need to be installed. History files are installed from the command-line prompt in NetScout Manager Plus. Should the FrameSaver unit be reset, these files will need to be reinstalled. The command used to install a new user history table is located in $NSHOME/bin. CAUTION: Do not use user_history_table_1 or 2.
Setting Up NetScout Manager Plus for FrameSaver Devices Monitoring a DLCI’s History Data Once the monitoring variables have been defined, a problem DLCI can monitored. " Procedure To monitor user history data: 1. From the NetScout Manager Plus main window, with the FrameRelay radio button still selected, select the Traffic radio button. The appropriate icons appear. 2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI list box (under the agent list box). 3.
Setting Up NetScout Manager Plus for FrameSaver Devices 5. Select History List from the View menu. The History List window opens. The newly defined user history variables should appear on this list. 6. Highlight the desired set of user history variables, and select the OK button. Data is gathered based upon the configured user history variables. This may take some time, so please be patient. 7. Select 2D or 3D Bar from the Format menu, if desired (3D Bar is shown).
Setting Up NetScout Manager Plus for FrameSaver Devices Using the 2D or 3D Bar to view the user history data collected, you can click on a particular bar and get an expanded view of the data. 8. Click anywhere on this window to return to the previous window view (see Step 7 of this procedure). Refer to Launching User History and Understanding Custom History Display in Using Custom History of the NetScout Manager Plus User Guide for additional information.
Setting Up NetScout Manager Plus for FrameSaver Devices Monitoring the Agent Using NetScout Manager Plus (Models 9820 and 9820-2M) Once the FrameSaver SLV agent has been added to NetScout Manager Plus, select either the Traffic or Protocol radio button to monitor the newly added agent, or one of its DLCIs. NOTE: Only the Traffic and Protocol radio buttons on the application selection bar are supported for FrameSaver SLV agents. The procedure below describes how to monitor an agent’s traffic.
Setting Up NetScout Manager Plus for FrameSaver Devices NOTE: If Size Distribution is the selected View and distribution size has been changed via OpenLane, the values shown for the distribution will not be accurate. Only default size distributions are tracked. Statistical Windows Supported (Models 9820 and 9820-2M) Not all icons that appear on the NetScout Manager Plus main window are supported for FrameSaver units.
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 FrameSaver SLV report example on page 11-9). To get this report, you need Network Health R4.01 or higher.
Setting Up Network Health for FrameSaver Devices For additional information about installing, accessing, and managing FrameSaver SLV devices through Concord’s Network Health, and for information about applicable reports, refer to: H Network Health Installation Guide to help you install the application. H Network Health User Guide to help you get started using the application. H Network Health Reports Guide to help you understand and use Frame Relay reports.
Setting Up Network Health for FrameSaver Devices Discovering FrameSaver Elements Once licenses are entered and you have access to the applications, the Discover dialog box opens. Use this dialog box to search for SLV units in your network and discover their DLCIs. Saving the results of the search creates definitions in the Poller Configuration, which are used to poll the units.
Setting Up Network Health for FrameSaver Devices Configuring the Discovered Elements Network Health sets the speed for discovered elements when it polls the unit for the first time. For a FrameSaver SLV unit, the speed set would be the unit’s CIR. No additional configuration should be required. However, you should verify that all appropriate information has been retrieved. NOTE: If an SLV unit does not have CIR configured, or if it is not configured correctly, Network Health sets the unit’s CIR to 0 kbps.
Setting Up Network Health for FrameSaver Devices Grouping Elements for Reports Once the discovery process is completed and required changes are made, the newly discovered elements (DLCIs) should be organized into a group for Health reporting. Grouping makes for easier monitoring and management of similar node types (e.g., all SLV elements). Once grouped, you can then run reports on all DLCIs in the network, as well as reports on individual DLCIs. " Procedure To group elements: 1.
Setting Up Network Health for FrameSaver Devices Generating Reports for a Group Once Network Health has had sufficient time to gather data from the polled DLCIs and the DLCIs have been grouped, you can start generating reports. When selecting a report Section, select WAN from the drop-down list. See Running Reports from the Console in the Network Health Reports Guide for additional information. That section also tells you how to schedule automatic report generation.
Setting Up Network Health for FrameSaver Devices About Trend Reports By specifying specific variables like bandwidth, trend analysis can be performed and shown on Trend Reports. Up to ten variables for a DLCI, or ten DLCIs on one variable can be generated on a single trend report. Information can be presented in a line graph, pie chart, bar chart, or table format. Any amount of time can be specified for the reporting period.
Setting Up Network Health for FrameSaver Devices — Elements Summary Report – Compares DLCI traffic with volume and the baseline, bandwidth utilization, and errors. Use this report for DLCI detail information and comparison, to identify DLCIs with above or below average volume so they can be investigated when there are any significant changes. H Supplemental Report – Shows DLCI availability and latency. The information shown in this report is also on other Health reports.
Setting Up Network Health for FrameSaver Devices H Trend Reports – Perform trend analysis on up to ten specified variables for DLCIs. Variables other than bandwidth can be selected for a trend report (e.g., burst octets), but a bandwidth trend report should be generated when investigating problems that appear on Exceptions Reports, Supplemental Reports, and Health reports.
Setting Up Network Health for FrameSaver Devices This page intentionally left blank.
Hardware Maintenance (9820-45M) 12 Overview The FrameSaver SLV 9820-45M is designed for years of trouble-free service. There are actions you can take to further reduce the likelihood and amount of down time: Area of Concern Action Front Panel Assembly 1. Vacuum dust from air vents whenever a buildup is visible. See Cleaning the Front Panel Assembly on page 12-2. 2. Monitor LEDs for fan failures. Replace the front panel assembly immediately upon failure.
Hardware Maintenance (9820-45M) Cleaning the Front Panel Assembly The substantial airflow through the unit’s four fans may cause dust to collect on the outside of the front air vents. When dust becomes visible at the air vents, run the brush attachment of a vacuum cleaner gently over the front panel to remove it. In extremely dusty environments it may be necessary to remove the front panel assembly to clean the blades of the fans. Refer all service to qualified personnel.
Hardware Maintenance (9820-45M) Replacing the Front Panel Assembly The System FAN LED on the front panel turns on when one or more of the front panel fans has failed. Replace the front panel assembly as soon as possible after this occurs. Refer all service to qualified personnel. The procedure may be performed while the unit is running. " Procedure To replace the front panel: 1. Loosen the captive screws holding on the front panel. ! WARNING: The fans continue to run until the fan power cable is removed.
Hardware Maintenance (9820-45M) Replacing a Power Module A power module requires replacement in a FrameSaver SLV 9820-45M when: H The front panel System PWR LED is lit. This means that one of the power modules has failed. H Power is applied to a power module and it is switched on, but the power module LED does not light. Refer all service to qualified personnel. " Procedure To replace a power module: 1. For a system with redundant power, determine which power module still has its power LED lit.
Menu Hierarchy A Menus The following is a graphical representation of the FrameSaver SLV unit’s menu organization.
Menu Hierarchy Menu Hierarchy System and Test Status • Self-Test Results • Health and Status • Test Status • Last System Reset* Network LMI Reported DLCIs • DLCI • Status • CIR (bps) MAIN MENU PVC Connection Status • Source Link, DLCI, EDLCI • Primary Destination Link, DLCI, EDLCI, Status • Alternate Destination Link, DLCI, EDLCI, Status* Network Interface Status • Operating Rate Status Status System and Test Status LMI Reported DLCIs PVC Connection Status Network Interface Status IP Routing Table
Menu Hierarchy MAIN MENU Status Test Configuration Auto-Configuration Auto-Configuration • Frame Relay Discovery Mode • Automatic Circuit Removal Control Easy Install* MAIN MENU Status Test Configuration Auto-Configuration Control Modem Call Directories** System Information Administer Logins Change Operating Mode Select Software Release LMI Packet Capture Utility Disconnect Modem Reset Device Control Easy Install* System Information Administer Logins Select Software Release LMI Packet Capture Ut
Menu Hierarchy This page intentionally left blank.
SNMP MIBs and Traps, and RMON Alarm Defaults B This appendix contains the following: H MIB Support H Downloading MIBs and SNMP Traps H System Group (mib-2) — FrameSaver Unit’s sysDescr (system 1) — FrameSaver Unit’s sysObjectID (system 2) H Interfaces Group (mib-2) — Paradyne Indexes to the Interface Table (ifTable) — NetScout Indexes to the Interface Table (ifTable) H Standards Compliance for SNMP Traps — Trap: warmStart — Trap: authenticationFailure — Traps: linkUp and linkDown — Traps: enterpri
SNMP MIBs and Traps, and RMON Alarm Defaults MIB Support The FrameSaver unit supports the SNMP Version 1, and has the capability of being managed by any industry-standard SNMP manager and accessed by external SNMP managers using the SNMP protocol.
SNMP MIBs and Traps, and RMON Alarm Defaults System Group (mib-2) This section provides the system description and system object identifier for the System Group for a FrameSaver SLV 9820 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 SLV 9820 unit: PARADYNE DP FrameSaver SLV; Model: [9820, 9820-2M, 9820-8M, or 9820-45M]; S/W Release: (MM.mm.bb [MM=Major.mm=minor.
SNMP MIBs and Traps, and RMON Alarm Defaults Interfaces Group (mib-2) Clarification for objects in the Interfaces Group, as defined in RFC 1573 and RFC 1213, which is an SNMPv1 MIB, is provided in this section. Paradyne Indexes to the Interface Table (ifTable) The following table provides the ifName for each interface type, the ifDescr, and the ifIndex that Paradyne has assigned to each. Table B-1.
SNMP MIBs and Traps, and RMON Alarm Defaults NetScout Indexes to the Interface Table (ifTable) For remote monitoring at sites where FrameSaver units are operating with NetScout Probes, use the following ifName, ifDescr, and ifIndex. Table B-2. NetScout Interface Objects Information ifName Description ifDescr (ifEntry 2) ifIndex Frame Relay Logical Layer Frame Relay 4 Network V.35/ X.
SNMP MIBs and Traps, and RMON Alarm Defaults Standards Compliance for SNMP Traps This section describes the FrameSaver unit’s compliance with SNMP format standards and with its special operational trap features. All traps have an associated string to help you decipher the meaning of the trap. Strings associated with an interface with a substring containing $ifString have the following format: ‘DLCI $dlciNumber “$circuitId” of $ifName frame relay link “$linkName”.’ — $dlciNumber is the DLCI number.
SNMP MIBs and Traps, and RMON Alarm Defaults Trap: warmStart This trap indicates that the FrameSaver unit has been reset and has stabilized. Table B-3. warmStart Trap Trap What It Indicates Possible Cause warmStart FrameSaver unit has just reinitialized and stabilized itself. H Reset command sent. Variable-Binding H Power disruption. String: ‘Unit reset.’ devLastTrapString (devHealthAndStatus.
SNMP MIBs and Traps, and RMON Alarm Defaults Traps: linkUp and linkDown These traps are supported on the following interfaces: H Network and synchronous data ports – Physical sublayer interfaces H Frame relay logical link layer interfaces Table B-5. linkUp and linkDown Traps Trap What It Indicates Possible Cause linkDown A failure in one of the communication interfaces has occurred. A failure in one of the communication interfaces has occurred.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings (1 of 2) Interface Variable-Bindings Possible Cause H ifIndex (RFC 1573) H linkDown – One or more alarm Physical Sublayer Network Synchronous Data Port H ifAdminStatus (RFC 1573) (Supported by the media-specific RS232-like MIB.) H ifOperStatus (RFC 1573) H devLastTrapString (devHealthAndStatus.mib) conditions are active on the port.
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 Ethernet Port H ifIndex (RFC 1573) H ifAdminStatus (RFC 1573) H ifOperStatus (RFC 1573) H devLastTrapString (devHealthAndStatus.mib) H linkDown – Communications are not possible on the port. String: ‘Ethernet $alarmString down.’ H linkUp – Communications are now possible on the port. String: ‘Ethernet up.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. Input Control Leads That Generate linkDown and linkUp Traps V.35 and EIA-530-A X.
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-8. enterprise-Specific Traps and Variable-Bindings (1 of 2) Trap Variable-Bindings Possible Cause enterpriseCIRChange(15) H devFrExtDlciIfIndex CIR has changed due to the LMI report. LMI Protocol is set to Standard and the network’s CIR changed. (devFrExt.mib) H devFrExtDlciDlci (devFrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-8. enterprise-Specific Traps and Variable-Bindings (2 of 2) Trap Variable-Bindings Possible Cause enterpriseMissedSLVDown(16) H devFrExtDlciIfIndex SLV Timeout Error Event Threshold has been exceeded. (devFrExt.mib) H devFrExtDlciDlci (devFrExt.mib) H devFrExtDlciMissed- SLVs (devFrExt.mib) enterpriseMissedSLVUp(116) enterpriseRMONResetToDefault(13) H devLastTrapString (devHealthAndStatus.mib.) H devLastTrapString (devHealthAndStatus.
SNMP MIBs and Traps, and RMON Alarm Defaults Traps: RMON-Specific Two traps are defined to support the Alarm and Events Groups of RMON. See RMON Alarm and Event Defaults for the default values that will generate RMON-specific traps. Table B-9. RMON-Specific Traps and Variable-Bindings Trap Variable-Bindings Possible Cause risingAlarm H alarmIndex (RFC 1757) Object being monitored has risen above the set threshold.
SNMP MIBs and Traps, and RMON Alarm Defaults RMON Alarm and Event Defaults The FrameSaver unit supports automatic generation of RMON alarm and event information. Each alarm sets an SNMP variable to monitor. When the threshold set for the monitored variable is exceeded, an SNMP trap or a log event is sent.
SNMP MIBs and Traps, and RMON Alarm Defaults Network Synchronous Port Physical Interface Alarm Defaults These alarms only apply to the FrameSaver unit’s network data port interface. They are created during RMON initialization and put into the Paradyne-defined alarm area. Table B-10. Network Synchronous Port Physical Interface Alarm Defaults Item Unavailable Seconds Sample Type 1 MIB/Tag/OID 2 D Interval MIB: pdn_SyncPortStats.
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.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-11. Frame Relay Link Alarm Defaults (2 of 2) Item Sample Type 1 MIB/Tag/OID 2 Rx Overruns D Event Type Rising Falling Threshold Threshold Default Default 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 900 secs (15 mins) Rising 1 1 Interval MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkRxOverruns OID: .1.3.6.1.4.1.1795.2.24.2. 6.9.4.7.1.28.
SNMP MIBs and Traps, and RMON Alarm Defaults DLCI Alarm Defaults – Paradyne Area These alarms apply to all DLCIs on the network interface and can be created during RMON initialization or when a DLCI is created. They are put into the Paradyne alarm area. Table B-12.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-12. DLCI Alarm Defaults – Paradyne Area (2 of 2) Item Sample Type 1 MIB/Tag/OID 2 Maximum Latency D Interval MIB: pdn_FrExt.mib (E) Tag: devFrExtLatencyMax 60 secs (1 min) Event Type Rising Falling Threshold Threshold Default Default Rising 1 1 OID: .1.3.6.1.4.1.1795.2.24.2. 6.9.4.3.1.6.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.
SNMP MIBs and Traps, and RMON Alarm Defaults DLCI Alarm Defaults These alarms can be created during RMON initialization or when a DLCI is created. For Models 9820 and 9820-2M, they are put into the NetScout alarm area; for Models 9820-8M and 9820-45M they are grouped with the DLCI Alarm Defaults in the Paradyne area. Table B-13 identifies alarm defaults that do not change, and Table B-14 identifies alarm defaults that change when the interface’s line speed changes.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-13. Static DLCI Alarm Defaults (2 of 2) Item Sample Type 1 MIB/Tag/OID 2 Tx CIR Utilization D Interval MIB: FR DTE MIB (RFC 2115) 60 secs (1 min) Event Type None Rising Falling Threshold Threshold Default Default Must be 0 configured. Tag: frCircuitSentOctets OID: .1.3.6.1.2.1.10.32.2.1. 7.I.D 1 D = Delta. Indicates that the calculated difference between the current value and the previous value is contained in the MIB. A = Absolute.
SNMP MIBs and Traps, and RMON Alarm Defaults Object ID Cross-References (Numeric Order) The FrameSaver unit supports automatic generation of RMON alarm and event information. Each alarm sets an SNMP variable to monitor. When the threshold set for the monitored variable is exceeded, an SNMP trap is sent and/or a log entry is made.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (1 of 4) Object ID (OID) 1 Item MIB/Tag Link Speed MIB: MIB II (RFC 1573) .1.3.6.1.2.1.2.2.1. . . .1.3.6.1.2.1.2.2.1.5.I Tag: ifSpeed .1.3.6.1.2.1.2.2.1.10.I All DLCI + LMI Rx Octets MIB: MIB II (RFC 1573) Tag: ifInOctets .1.3.6.1.2.1.2.2.1.16.I All DLCI + LMI Tx Octets MIB: MIB II (RFC 1573) Tag: ifOutOctets .1.3.6.1.2.1.2.10.32.2.1. . . .1.3.6.1.2.1.10.32.2.1.4.I.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (2 of 4) Object ID (OID) 1 Item MIB/Tag Rx Non-octet Aligns 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.9.4.7.1.16.I 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.1795.2.24.2.13.1.2.1.6.H.T.N IP Top Talkers (1– 6) MIB: pdn_FrExt.mib (E) Tag: devRmonIPTopNSrcIP .1.3.6.1.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (3 of 4) Object ID (OID) 1 Item MIB/Tag Network Frames Dropped In CIR MIB: pdn_FrExt.mib (E) Network Frames Offered Above CIR MIB: pdn_FrExt.mib (E) Network Frames Lost Above CIR MIB: pdn_FrExt.mib (E) Network Frames Offered Above CIR Within EIR MIB: pdn_FrExt.mib (E) Network Frames Dropped Above CIR Within EIR MIB: pdn_FrExt.mib (E) Network Frames Offered Above EIR MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. History OID Cross-Reference (4 of 4) Object ID (OID) 1 Item MIB/Tag Burst Upper Limit (1– 5) MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1. . . .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.2.I.D.N Tag: devFrExtBurstUpLimit .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.3.I.D.N Burst Octets (1– 5) MIB: pdn_FrExt.mib (E) Tag: devFrExtBurstOctets .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.4.I.D.N Burst Frames (1– 5) MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-16. Alarm OID Cross-Reference (1 of 2) Object ID (OID) Item MIB/Tag Rx FECNs MIB: FR DTE MIB (RFC 2115) .1.3.6.1.2.1.10.32.2.1. . . .1.3.6.1.2.1.10.32.2.1.4.I.D Tag: frCircuitReceivedFECNs .1.3.6.1.2.1.10.32.2.1.5.I.D Rx BECNs MIB: FR DTE MIB (RFC 2115) Tag: frCircuitReceivedBECNs .1.3.6.1.2.1.10.32.2.1.6.I.D Frames Sent MIB: FR DTE MIB (RFC 2115) Tag: frCircuitSentFrames .1.3.6.1.2.1.10.32.2.1.7.I.
SNMP MIBs and Traps, and RMON Alarm Defaults Table B-16. Alarm OID Cross-Reference (2 of 2) Object ID (OID) Item MIB/Tag Current Latency MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4. . . .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.7.I.D Tag: devFrExtLatencyLatest .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.2.I.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.3.I.N Frame Size Upper Limits 1– 5 MIB: pdn_FrExt.mib (E) Frame Size Count 1– 5 MIB: pdn_FrExt.
SNMP MIBs and Traps, and RMON Alarm Defaults B-30 June 2000 9820-A2-GB20-20
Connectors, Cables, and Pin Assignments C This appendix shows the FrameSaver unit rear panels, and pin assignments for the connectors/interfaces and cables. NOTE: In the pin assignment tables of this appendix, if the pin number is not shown, it is not being used.
Connectors, Cables, and Pin Assignments Rear Panels The following illustration shows the rear panel of the FrameSaver 9820, 9820-2M, and 9820-8M models. 98-16189 The following illustration shows the rear panel of the FrameSaver 9820-45M.
Connectors, Cables, and Pin Assignments COM (Terminal) Port Connector The following table shows the signals and pin assignments for the DB25 communication port connector. The communication port is called the Terminal port on the Model 9820-45M.
Connectors, Cables, and Pin Assignments Standard EIA-232 Crossover Cable (Models 9820, 9820-2M, 9820-8M) A standard EIA-232 crossover cable can be used to connect the COM port to an external modem. This is an EIA-232 plug-to EIA-232 plug (DB25-to-DB25) cable. The external modem must be configured so it is compatible with the FrameSaver unit. See page C-5 to configure an external modem.
Connectors, Cables, and Pin Assignments " Procedure To configure an external modem: 1. Disconnect the asynchronous terminal from the standard cable. See page C-4 for an illustration of the COM Port connection. 2. Reconnect the crossover cable to the external modem. 3. Enable auto-answer on your modem, and configure it to use the following LSD, DSR, CTS, RTS, and DTR control leads. See the table below for AT D0 command strings.
Connectors, Cables, and Pin Assignments User and Network Data Port Connectors (Models 9820, 9820-2M, 9820-8M) The following table provides the pin assignments for the EIA-530-A connector to the DTE or NTU.
Connectors, Cables, and Pin Assignments X.21 Network Cable (Models 9820, 9820-2M, 9820-8M) This cable is used to connect the network data port to an NTU with an X.21 interface. It is a 25-position EIA-530A-to-15-pin X.21 (DB25-to-X.21) cable. This cable (Part No. 035-0384-1031) is part of the X.21 Cable Kit (Feature No. 9008-F1-521). 99-16303 The following table provides the pin assignments for the DB25-to-X.21 network cable.
Connectors, Cables, and Pin Assignments X.21 DTE Adapter Cable (Models 9820, 9820-2M, 9820-8M) This adapter is used to connect the user data port to a DTE with an X.21 cable. It is a 25-pin EIA-530A-to-15-pin X.21 (DB25-to-X.21) adapter cable. This cable (Part No. 035-0302-0131) is part of the X.21 Cable Kit (Feature No. 9008-F1-521). 98-15883 The following table provides the pin assignments for the DB25-to-X.21 adapter cable.
Connectors, Cables, and Pin Assignments V.35 Network Cable (Models 9820, 9820-2M, 9820-8M) This cable is used to connect the network data port to an NTU with a V.35 interface. It is a 25-position EIA-530A-to-34-pin V.35 (DB25-to-V.35) cable. This cable (Part No. 035-0383-1031) is part of the V.35 Cable Kit (Feature No. 9008-F1-522).
Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-V.35 network cable.
Connectors, Cables, and Pin Assignments V.35 DTE Adapter (Models 9820, 9820-2M, 9820-8M) This adapter is used to connect the user data port to a DTE with an V.35 cable. It is a 25-pin EIA-530A-to-34-position V.35 (DB25-to-V.35) adapter. This adapter (Part No. 002-0095-0031) is part of the V.35 Cable Kit (Feature No. 9008-F1-522).
Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-V.35 adapter.
Connectors, Cables, and Pin Assignments EIA-530-A Straight-through Cable (Models 9820, 9820-2M, 9820-8M) A standard straight-through cable (Feature No. 9008-F1-523) is used to connect the network data port to the NTU or the user data port to a DTE when the Port Type is E530 (EIA-530-A). It is a 25-pin EIA-530A-to-25-pin EIA-530-A (DB25-to-DB25) cable.
Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-DB25 straight-through cable.
Connectors, Cables, and Pin Assignments EIA-612/613 HSSI Connectors (Model 9820-45M) The 50-pin HSSI connectors on the Model 9820-45M use standard EIA-612/613 signaling.
Connectors, Cables, and Pin Assignments LAN Connector (Model 9820-45M) The LAN connector on the Model 9820-45M uses a standard IEEE 802.3 8-pin modular jack.
Technical Specifications D Table D-1.
Technical Specifications Table D-1. FrameSaver SLV Unit Technical Specifications (2 of 3) Specification Criteria Weight – Models 9820, 9820-2M, 9820-8M 2.6 lbs. ( 1.2 kg ) Weight – Model 9820-45M 19.0 lbs. (8.4 kg) Physical Dimension – Models 9820, 9820-2M, 9820-8M Height 2.9 inches (7.4 cm) Width 8.5 inches (21.6 cm) Depth 12.5 inches (31.8 cm) Physical Dimensions – Model 9820-45M Height 7 inches (18 cm) Width 17.
Technical Specifications Table D-1. FrameSaver SLV Unit Technical Specifications (3 of 3) Specification Criteria COM Port (9820, 9820-2M, 9820-8M) DB25 connector Data rates 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.2 kbps Terminal Port (9820-45M) DB25 connector Data rates 9.6, 14.4, 19.2, 28.8, 38.4 kbps LAN Port 8-pin modular socket Specifications Receive: Ethernet Version 2 and IEEE 802.
Technical Specifications D-4 June 2000 9820-A2-GB20-20
Equipment List E Equipment See page E-3 for cables you can order. Model/ Feature Number Description FrameSaver SLV In-Line Units FrameSaver SLV 9820 In-Line unit (128 Kbps) for up to 16 PVCs Includes Standalone Housing, Universal 100 – 240 VAC Power Supply, Power Cord, Installation Instructions, and Quick Reference.
Equipment List Model/ Feature Number Description Power Supply 100 – 240 VAC Power Supply (Models 9820, 9820-2M, 9820-8M) 9001-F1-040 120 VAC Power Module (Model 9820-45M) 9580-F1-020 NMS Products OpenLane Enterprise 7805-D1-001 OpenLane Workgroup 7805-D1-003 NetScout Manager Plus – For UNIX or Windows NT 9180 NetScout Server – For UNIX or Windows NT 9190 NetScout WebCast – For UNIX or Windows NT 9155 Optional Features E-2 Wall Mounting Kit for 1-Slot Housing 9001-F1-891 Shelf Mounting Ki
Equipment List Cables This table lists cables you can order. Part Number Description LAN Adapter, 002-0069-0031 DB25 plug-to-8-position modular receptacle 3100-F1-920 COM Port-to-LAN Adapter Cable (14 ft /4.3 m) 035-0315-1431 3100-F2-910 50-position to 50-position, 0.5-inch straight exit connector HSSI cable (10 ft/3 m) 035-0399-1031 9008-F1-514 X.21 Cable Kit, which includes a: 9008-F1-521 X.21 Network Cable (10 ft/3 m) 035-0384-1031 X.21 DTE Adapter Cable, EIA-530-A-to-X.21 (1 ft /.
Equipment List This page intentionally left blank.
Index Numbers 55 hexadecimal, test pattern, 8-19 A aborting tests, 8-16 Access Dial-In, 4-57 Name, 4-40 Type, 4-44 Access Level, 5-10, 5-11 assigning, 5-9 COM port, 4-54 Modem port, 4-60 security, 2-1 Session, 4-42 adding, SLV units to network, 11-3 Alarm, 8-7 (Fail), 6-4, 6-6, 6-8 adding manually, 10-11 conditions, 8-2, 8-7 editing, 10-9 LED is lit, 8-11 RMON defaults, B-15 using template, 10-8 ALM, LED, 6-4, 6-6, 6-8 Alternate Dial-Out Directory, 4-49 IP Address, 4-58 software revision, 6-2 Subnet Mask,
Index COM port, 4-46, 4-57 as default IP destination, 4-34 configuration options, 4-52 connector, C-3 set up for trap dial-out, 4-5 Committed Burst Size Bc (Bits), 4-27 Committed Information Rate (CIR), 4-27 Communication Port, configuration options, 4-52 Community Name, 4-40 assigning, 5-9 Concord Network Health, compatibility, 11-1 Configuration Auto, Active, 6-18 displaying and changing options, 3-4 menu, 3-2 menu/branch, 2-4 option areas, 3-3 option tables, 4-13 saving options, 3-6 tables, 3-3 upload/d
Index Device messages, 6-11 troubleshooting problems, 8-11 Dial-In Access external modem, 4-57 Modem port, 4-59 Dial-Out Delay Time (Min), 4-48 Directory, 4-49 options, 4-5, 4-45 Trap, 4-48 Directory, Alternate Dial-Out, 4-49 disabling, SNMP access, 5-8 Discard Eligible (DE), 4-37 Disconnect Time COM port, 4-54 Modem port, 4-60 Telnet session inactivity, 4-42 discovering elements/DLCIs, 11-3 Discovery frame relay (FR), 4-7 Frame Relay Mode, saving a mode change, 4-9 displaying configuration options, 3-4 id
Index Ethernet, statistics, 6-37 Ethernet port as default IP destination, 4-34 MAC address, 6-2 user interface options, 4-50 even parity, 4-53 Event Log, Traps, 6-38 exception points, 11-7 Excess Burst Size (Bits), 4-28 External Device, controlling access, 5-4 Modem (on Com Port) options, 4-57 Commands, 4-57 set up for trap dial-out, 4-5 Transmit Clock, 4-21 G General LEDs, 6-4 options, 4-18 SNMP management, options, 4-40 Traps, 4-46 generating reports, 11-6 glossary, x grouping elements for reports, 11-5
Index IP Address, 4-36, 4-58 for COM port, 4-55 for Ethernet port, 4-50 for Modem port, 4-61 limiting SNMP access through, 5-10 NMS number, 4-44, 4-45 Node, 4-3, 4-33 IP Routing Table, Status screen, 6-26 K keyboard keys, 2-6 keys keyboard, 2-6 screen function, 2-5, 2-7 L Lamp Test, 6-20, 8-22 LAN, adapter and cable, C-3 latency, 1-4 LEDs, 8-2, 8-11 and control leads, displaying, 6-6 descriptions, 6-4 front panel, 6-3 power supply, 6-10 lights, power supply, 6-10 limiting async terminal access, 5-3 FTP a
Index M MAC address, 6-2 Main Menu, screen/branch, 2-4 making input selections, 2-9 Management and Communication, options, 4-32 General SNMP, options, 4-40 OpenLane 5.
Index Node IP, configuration option tables, 4-32 NSP, 4-14 NTU, 1-1 Number of Managers, 4-44, 5-10 Trap Managers, 4-45 O odd parity, 4-53 OID (object identification), user history file, 10-13 cross-reference (numeric order), B-24, B-28 OK, LED, 6-4, 6-5 OpenLane SLM solution, 1-5 SLM support, 9-1 operating, changing mode for demos, 4-12 organization of this document, ix Out of Sync, message, 8-13, 8-19 Outbound Management Priority, 4-28 P packet capture uploading data, 7-6 utility, 8-5 packets, 4-37 Pari
Index Q S quality of service, 4-28 Quick Reference, 3-3 Sampling, SLV Inband and Interval, 4-16 saving configuration options, 3-6 screen area, 2-5 function keys area, 2-5 how to navigate, 2-6 scrolling through valid selections, 2-9 security, 1-3, 2-1, 2-2, 3-5, 5-1 SNMP NMS, options, 4-44 selecting a field, 2-9 from a menu, 2-8 Self-Test enable/disable, 4-18 results messages, 6-17 Send, test pattern, 8-18 serial number, NAM, 6-2 Service, A service level management, 1-1 reports, 11-6 verification configu
Index SLV (service level verifier), 1-1 configuring, 4-16 Delivery Ratio, 4-16 DLCI Down on Timeout, 4-16 Packet Size, 4-17 performance statistics, 6-30 reports, 1-3 Sample Interval (secs), 4-16 Synchronization Role, 4-17 Timeout, Error Event Threshold, 4-16, 4-17 SNMP assigning community names/access levels, 5-9 limiting access, 5-8, 5-10 Management, 4-40, 5-8 NMS security, options, 4-44 Number of Managers, 4-44 setting up Trap Managers, 4-44 Traps, 4-45 downloading, B-2 standards, B-6 supported, 8-2 soft
Index Terminal port as default IP destination, 4-34 configuration options, 4-52 connector, C-3 Port Use, 4-52 Test menu/branch, 2-4 Mode, 6-4, 6-6, 6-8 Status messages, DBM, 6-20 Tests, 1-4 aborting, 8-16 available, 8-14 DTE Loopback, 8-20 Duration, 4-18 IP Ping, 8-21 Lamp, 8-22 physical, 8-20 PVC, 8-17 PVC Loopback, 8-18 starting or stopping, 8-15 test pattern, 8-18 Timeout, 4-18, 8-14 through PVC connections, total number, 1-4 throughput, 1-4 time, setting, 4-4 Timeout Inactivity, 4-42, 4-54, 4-60 Test,
Index V W V.35, cable kit, C-9, C-11 Value Out of Range message, 4-26, 4-27 variable-bindings, B-9, B-14 VCI, 1-5 viewing, packet capture results, 8-6 virtual path or channel identifier, 1-5 VPI, 1-5 warmStart events, General Traps, 4-46 trap, B-7 warranty, A Web-site access to documentation, xi glossary, x X X.
