Paradyne FrameSaver SLV 9124 User Manual

Hide thumbs Also See for FrameSaver SLV 9124:
Table of Contents

Advertisement

Quick Links

FrameSaver SLV 9124
USER'S GUIDE
Document No. 9124-A2-GB20-00
March 2000

Advertisement

Table of Contents
loading

Summary of Contents for Paradyne FrameSaver SLV 9124

  • Page 1 FrameSaver SLV 9124 USER’S GUIDE Document No. 9124-A2-GB20-00 March 2000...
  • Page 2 Paradyne worldwide office locations, use one of the following methods: Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty at www.paradyne.com/warranty.) Telephone: Call our automated system to receive current information by fax or to speak with a company representative.
  • Page 3: Table Of Contents

    ..........About the FrameSaver SLV 9124 SLM Overview .
  • Page 4 Contents Setting Up Auto-Configuration ........3-10 Selecting a Frame Relay Discovery Mode .
  • Page 5 Contents Security and Logins Limiting Access ..........Controlling Asynchronous Terminal Access .
  • Page 6 Contents Troubleshooting Problem Indicators ..........Resetting the Unit and Restoring Communication .
  • Page 7 ......... Paradyne Indexes to the Interface Table (ifTable) .
  • Page 8 ......B-17 DLCI Alarm Defaults – Paradyne Area ......
  • Page 9: About This Guide

    Document Organization Section Description Chapter 1 About the FrameSaver SLV 9124. Identifies how the FrameSaver 9124 unit fits into Paradyne’s Service Level Management (SLM) solution, and describes the unit’s features. Chapter 2 User Interface and Basic Operation. Shows how to navigate the user interface.
  • Page 10 Appendix D Appendix E Equipment List. Index Lists key terms, acronyms, concepts, and sections. A master glossary of terms and acronyms used in Paradyne documents is available on the World Wide Web at www.paradyne.com. Select Library Technical Manuals Technical Glossary viii...
  • Page 11: Product-Related Documents

    09-10050-002 Network Health Reports Guide 09-10070-001 Contact your sales or service representative to order product documentation. Complete Paradyne documentation for this product is available at www.paradyne.com. Select Library Technical Manuals. To order a paper copy of this manual: Within the U.S.A., call 1-800-PARADYNE (1-800-727-2396) Outside the U.S.A., call 1-727-530-8623...
  • Page 12: Conventions Used

    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.
  • Page 13: About The Framesaver Slv 9124

    About the FrameSaver SLV 9124 This chapter includes the following: SLM Overview FrameSaver SLV 9124 Features SLM Overview The Service Level Management (SLM) Solution consists of: FrameSaver SLV units OpenLane SLM system NetScout Manager Plus application Standalone NetScout Probes, if needed...
  • Page 14: Framesaver Slv 9124 Features

    About the FrameSaver SLV 9124 FrameSaver SLV 9124 Features The FrameSaver SLV 9124 unit provides the following features: 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.
  • Page 15 About the FrameSaver SLV 9124 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.
  • Page 16 About the FrameSaver SLV 9124 Configuration Upload/Download and Software Download Capability. Provides quick transfer of configuration options to and from nodes and software downloads while the unit is running using the standard File Transfer Protocol (FTP). Two software images can be stored.
  • Page 17 About the FrameSaver SLV 9124 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.
  • Page 18 About the FrameSaver SLV 9124 This page intentionally left blank. March 2000 9124-A2-GB20-00...
  • Page 19: User Interface And Basic Operation

    User Interface and Basic Operation This chapter tells you how to access, use, and navigate the menu-driven user interface. It includes the following: Logging On Main Menu Screen Work Areas Navigating the Screens Keyboard Keys — Function Keys — Selecting from a Menu —...
  • Page 20: Logging On

    User Interface and Basic Operation Logging On Start a session using one of the following methods: Telnet session via: — An in-band management channel through the frame relay network. — A local in-band management channel configured on the DTE port between the FrameSaver unit and the router.
  • Page 21 User Interface and Basic Operation If your login was . . . Then the . . . Valid Main Menu appears (see page 2-4). Begin your session. Invalid Message, Invalid Password, appears on line 24, and the Login screen is redisplayed. After three unsuccessful attempts: –...
  • Page 22: Main Menu

    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. Î...
  • Page 23: Screen Work Areas

    User Interface and Basic Operation Screen Work Areas There are two user work areas: Screen area – Where you input information into fields. Function keys area – Where you perform specific screen functions. Below is a sample configuration screen. Model Number Date and Time Menu Path Î...
  • Page 24: Navigating The Screens

    User Interface and Basic Operation Navigating the Screens You can navigate the screens by: Using keyboard keys. Switching between the two screen work areas using function keys. Keyboard Keys Use the following keyboard keys to navigate within the screen area: Press .
  • Page 25: Function Keys

    User Interface and Basic Operation Function Keys All function keys (located in the lower part of the screen; see the example on page 2-5) operate the same way throughout the screens. They are not case-sensitive, so upper- or lowercase letters can be used interchangeably. These keys use the following conventions: For the screen Select .
  • Page 26: Selecting From A Menu

    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.
  • Page 27: Selecting A Field

    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.
  • Page 28 User Interface and Basic Operation This page intentionally left blank. 2-10 March 2000 9124-A2-GB20-00...
  • Page 29: Configuration

    Configuration This chapter includes the following: Basic Configuration — Configuration Option Areas — Accessing and Displaying Configuration Options — Changing Configuration Options — Saving Configuration Options — Minimal Configuration Before Deploying Remote Units Entering System Information and Setting the System Clock Setting Up for Trap Dial-Out —...
  • Page 30 Configuration Configuring the Overall System — Configuring Frame Relay and LMI for the System — Configuring Service Level Verification Options — Configuring General System Options Configuring the Physical Interfaces — Configuring the Network Interface — Configuring the User Data Port Configuring the DSX-1 Interface —...
  • Page 31: Basic Configuration

    Configuration Basic Configuration Configuration option settings determine how the FrameSaver unit operates. Use the FrameSaver unit’s Configuration Edit/Display menu to display or change configuration option settings. The Configuration Edit/Display menu of the FrameSaver 9124 is shown below. Configuration Menu Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/config 9124-II Î...
  • Page 32: Configuration Option Areas

    Factory Default Configuration option area. You can find the default settings for configuration options in the: FrameSaver SLV 9124 Quick Reference Configuration Option Tables If the factory default settings do not support your network’s configuration, you can customize the configuration options to better suit your application.
  • Page 33: Accessing And Displaying Configuration Options

    Configuration Accessing and Displaying Configuration Options To access and display configuration options, load (copy) the applicable configuration option set into the edit area. Procedure To load a set of configuration options for editing: 1. From the Main Menu, press the down arrow key so the cursor is on Configuration.
  • Page 34: Changing Configuration Options

    Configuration Changing Configuration Options Procedure To change configuration option settings: 1. From the Configuration Edit/Display menu, select a set of configuration options and press Enter. For example: Configuration PVC Connections 2. Select the configuration options that are applicable to your network, and User Interface make appropriate changes to the setting(s).
  • Page 35: Saving Configuration Options

    Configuration Saving Configuration Options When changes to the configuration options are complete, use the Save function key to save your changes to either the Current, Customer 1, or Customer 2 configuration areas. NOTE: When changing settings, you must Save for changes to take effect. Procedure To save the configuration option changes: 1.
  • Page 36: Minimal Configuration Before Deploying Remote Units

    Configuration Minimal Configuration Before Deploying Remote Units At a minimum, the following configuration options must be set before deploying a a FrameSaver unit to a remote site: Node IP Address Node Subnet Mask See Table 3-11, Node IP Options, for a description of these options. Entering System Information and Setting the System Clock Select System Information to set up or display the general SNMP name for the...
  • Page 37: Setting Up For Trap Dial-Out

    Configuration Setting Up for Trap Dial-Out An external modem can be attached to the COM port for dialing out when an SNMP trap is generated. To set up an external modem, you need to: 1. Set up SNMP trap managers. 2.
  • Page 38: Setting Up Auto-Configuration

    Configuration Setting Up Auto-Configuration The auto-configuration feature allows you to select a method of automatic configuration and connection of DLCIs within the FrameSaver unit, as well as to automatically remove DLCIs and connections that are no longer supported by the network service provider.
  • Page 39: Selecting A Frame Relay Discovery Mode

    Configuration Selecting a Frame Relay Discovery Mode When a Frame Relay Discovery Mode is active, the FrameSaver unit “discovers” network DLCIs from the network LMI status response message. It configures a network DLCI, a user data port DLCI, and automatically connects them to create a PVC.
  • Page 40 Configuration NOTE: If 1MPort (the default) is not the setting required for your application, change the Frame Relay Discovery Mode before connecting the network cable or editing discovered option settings. Otherwise, the FrameSaver unit will start “discovering” DLCIs as soon as it powers up. To recover from this problem, edit a selected “discovered”...
  • Page 41: Automatically Removing A Circuit

    Configuration When a Frame Relay Discovery Mode is changed and saved, the Saving will cause Auto-Configuration to update and Restart. Are you sure? prompt appears. No is the default for this prompt. If Yes (y) is entered, the Delete All DLCIs and PVC Connections? prompt appears.
  • Page 42: Setting Up Management

    Configuration Setting Up Management FrameSaver units are already set up for SNMP management, with Community Name 1 set to Public and Name 1 Access set to Read/Write. For remote sites, other than the IP Address, this is all that is required. Configuration Management and Communication General SNMP Management...
  • Page 43: Setting Up So The Router Can Receive Rip

    Configuration Setting Up So the Router Can Receive RIP Using the system’s standard Routing Information Protocol (RIP) feature, routing information is passed to the router over the management PVC, so the router can learn routes to FrameSaver SLV devices. Node IP information should be set up (see Configuring Node IP Information Procedure...
  • Page 44: Setting Up Back-To-Back Operation

    Configuration 5. Select the Delete EDLCI Connections and Make a Mgmt Only PVC option. PVC connections for the selected DLCI are broken, the Port-1 DLCI mapped to this network DLCI and the embedded management DLCI (EDLCI) are deleted, and the selected DLCI will be reconfigured as a management PVC using the Node IP Address.
  • Page 45: Configuration Option Tables

    Configuration Configuration Option Tables Configuration option descriptions contained in this chapter are in menu order, even though this may not be the order in which you access each when configuring the unit. The following configuration option tables are included: Table 3-1. System Frame Relay and LMI Options Table 3-2.
  • Page 46: Configuring Frame Relay And Lmi For The System

    Configuration Configuring Frame Relay and LMI for the System Select Frame Relay and LMI from the System menu to display or change the Frame Relay and LMI options for the entire system (see Table 3-1). Main Menu Configuration System Frame Relay and LMI Configuring Frame Relay for an Interface to set an interface’s frame relay options.
  • Page 47 Configuration Table 3-1. System Frame Relay and LMI Options (2 of 2) LMI Clearing Event (N3) Possible Settings: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Default Setting: 1 Configures the LMI-defined N3 parameter, which sets the number of error-free messages that must be received before clearing an error event.
  • Page 48: Configuring Service Level Verification Options

    Configuration Configuring Service Level Verification Options SLV options are selected from the System menu (see Table 3-2). Main Menu Configuration System Service Level Verification Table 3-2. Service Level Verification Options (1 of 2) SLV Sample Interval (secs) Possible Settings: 10 – 3600 Default Setting: 60 Sets the inband communications interval between FrameSaver SLV devices.
  • Page 49 Configuration Table 3-2. Service Level Verification Options (2 of 2) SLV Timeout Clearing Event Threshold Available Settings: 1, 2, 3, 4 . . . 20 Default Setting: 1 Specifies the number of consecutive SLV messages that must be received before the DLCI Inactive status is cleared.
  • Page 50: Configuring General System Options

    Configuration Configuring General System Options Select General from the System menu to configure the general system configuration options (see Table 3-3). Main Menu Configuration System General Table 3-3. General System Options (1 of 2) 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.
  • Page 51 Configuration Table 3-3. General System Options (2 of 2) Secondary Clock Source Possible Settings: Net1, DSX, Internal Default Setting: Internal Provides a secondary clock source when the primary clock source fails. The source selected for this configuration option provides all of the timing within the unit and the clocks for all of the external interfaces.
  • Page 52: Configuring The Physical Interfaces

    Configuration Configuring the Physical Interfaces Characteristics for the following physical interfaces can be configured: Network Interface User Data Port DSX-1 Interface Physical Options Configuring the Network Interface When configuring the physical characteristics for the network interface, select Physical from the Network menu (see Table 3-4). Main Menu Configuration Network...
  • Page 53 Configuration Table 3-4. Network Physical Interface Options (2 of 4) Bit Stuffing Possible Settings: 62411, Disable Default Setting: 62411 Determines the type of bit insertion to provide ones density requirements for data transmitted to the network. Display Conditions – This option does not appear when Line Coding Format is set to B8ZS.
  • Page 54 Configuration Table 3-4. Network Physical Interface Options (3 of 4) Network Initiated PLB Possible Settings: Enable, Disable Default Setting: Enable Allows the initiation and termination of the payload loopback (PLB) to be controlled by the receipt of PLB-Actuate and PLB-Release commands from the network. Display Conditions –...
  • Page 55 Configuration Table 3-4. Network Physical Interface Options (4 of 4) Excessive Error Rate Threshold Possible Settings: 10E-4, 10E-5, 10E-6, 10E-7, 10E-8, 10E-9 Default Setting: 10E-4 Sets the error rate threshold that determines when an EER condition is declared. The excessive error rate is determined by the ratio of the number of CRC6 errors to the total number of bits received over a set period of time.
  • Page 56: Configuring The User Data Port

    Configuration Configuring the User Data Port Select Physical from the Data Ports menu to configure the physical characteristics for the user data port (see Table 3-5). Main Menu Configuration Data Ports Physical Table 3-5. Data Port Physical Interface Options (1 of 2) Transmit Clock Source Possible Settings: Internal, External Default Setting: Internal...
  • Page 57 Configuration Table 3-5. Data Port Physical Interface Options (2 of 2) Monitor RTS (Control) Possible Settings: Enable, Disable Default Setting: Enable Specifies whether the state of the Request To Send (RTS) circuits on the user data port will be used to determine when valid data communication is possible with the DTE. When the RTS off condition is detected, CTS is deasserted, LMI is declared down, and no further transfer of frame relay data can occur on this interface.
  • Page 58: Configuring The Dsx-1 Interface

    Configuration Configuring the DSX-1 Interface Select DSX-1 to display or change the physical configuration options when a DSX-1 interface is installed (see Table 3-6). Main Menu Configuration DSX-1 Table 3-6. DSX-1 Physical Interface Options (1 of 2) Interface Status Possible Settings: Enable, Disable Default Setting: Disable Specifies whether the DSX-1 interface selected is available for use.
  • Page 59 Configuration Table 3-6. DSX-1 Physical Interface Options (2 of 2) Line Equalization Possible Settings: 0 –133, 133 – 266, 266 – 399, 399 – 533, 533 – 655 Default Setting: 0 –133 Permits a standard DSX signal to be delivered over a distance of up to 655 feet. 0 –133 –...
  • Page 60: Assigning Time Slots/Cross Connections

    Configuration Assigning Time Slots/Cross Connections The system allows you to assign data paths between the various interfaces to share the T1 network. Assuming that the DSX-1 interface is enabled, you can make the following cross connection assignments: Frame relay links to the network interface time slots DSX-1 time slots to the network interface time slots You can also clear cross-connection assignments for the system, or for a selected slot or interface.
  • Page 61 Configuration Frame Relay Network Time Slot Assignment Screen Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/config/tslot_assign/frame_relay 9124 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Device Name: Node A 5/26/1999 23:32 Î...
  • Page 62: Assigning Dsx-1 Time Slots To The Network Interface

    Configuration Procedure 1. Follow this menu selection sequence: Main Menu Configuration Time Slot Assignment Frame Relay Network Assignments The Frame Relay Network Assignments screen appears. This screen contains a matrix of the current assignment status of all time slots on the network interface.
  • Page 63 Configuration DSX-1 to Network Time Slot Assignment Screen Example (Page 1) Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/config/tslot_assign/dsx 9124 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Device Name: Node A 5/26/1999 23:32 Î...
  • Page 64 Configuration Procedure 1. Follow this menu selection sequence: Configuration Time Slot Assignment DSX-to-Network Assignments The DSX-1 to Network Assignments screen appears. This screen contains a matrix of the current cross-connect status of all time slots on the network interface. 2. Move the cursor to the next time slot that can be edited (underlined). Use the spacebar or type in the desired time slot to display its time slot assignment.
  • Page 65 Configuration When a CGA condition (LOS, OOF, or AIS) is declared for a T1 interface, the signaling bits being transmitted to the other T1 interface for the DS0 are forced to idle for two seconds (except for user-defined patterns which are transmitted immediately).
  • Page 66 Configuration Table 3-7. Signaling and Trunk Conditioning Values (2 of 3) Network Side Meaning DSX-1 Side E&M-idle The signaling bits transmitted to the cross-connected E&M idle T1 interface during a CGA represent the idle state for an E&M interface (ABCD = 0000). E&M-busy The signaling bits transmitted to the cross-connected E&M busy...
  • Page 67: Clearing Assignments

    Configuration Table 3-7. Signaling and Trunk Conditioning Values (3 of 3) Network Side Meaning DSX-1 Side FXSD-busy The signaling bits transmitted to the cross-connected FXOD-busy T1 interface during a CGA represent the busy state for an FXSDN interface (ABCD = 1111). PLAR3idle The signaling bits transmitted to the cross-connected PLAR3idle...
  • Page 68: Configuring Frame Relay For An Interface

    Configuration Configuring Frame Relay for an Interface Select Frame Relay from the interface’s menu to display or change the Frame Relay options for an individual interface (see Table 3-8). Main Menu Configuration [Network/Data Ports] Frame Relay Configuring Frame Relay and LMI for the System for additional information.
  • Page 69 Configuration Table 3-8. Interface Frame Relay Options (2 of 3) LMI Parameters Possible Settings: System, Custom Default Setting: System Allows you to use the system LMI options, or to set specific LMI options for this interface. System – Use system LMI options (see Table 3-1, System Frame Relay and LMI Options).
  • Page 70 Configuration Table 3-8. Interface Frame Relay Options (3 of 3) LMI Inbound Heartbeat (T2) Possible Settings: 5, 10, 15, 20, 25, 30 Default Setting: 15 Configures the LMI-defined T2 parameter, which sets the number of seconds between the receipt of status enquiry messages on the network side of the LMI. Applies to the network side of a UNI only.
  • Page 71: Manually Configuring Dlci Records

    Configuration 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 3-9). Main Menu Configuration [Network/Data Port] DLCI Records Typically, DLCI Records only need to be configured when building Management PVCs between the NOC and the central site unit;...
  • Page 72 Configuration Table 3-9. DLCI Record Options (2 of 3) CIR (bps) Possible Settings: 0 – 1536000 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. Entry of an invalid rate causes the error message Value Out of Range (0 –...
  • Page 73 Configuration Table 3-9. DLCI Record Options (3 of 3) DLCI Priority Possible Settings: Low, Medium, High Default Setting: High Specifies the relative priority for data received on the DLCI from an attached device (also known as quality of service ). All data on Port 1 is cut-through, as long as there is no higher-priority data queued from another user port.
  • Page 74: Configuring Pvc Connections

    Configuration Configuring PVC Connections The Auto-Configuration feature automatically configures PVC Connections and their DLCI Records. PVC Connections can also be created manually (see Table 3-10). 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.
  • Page 75 Configuration Table 3-10. PVC Connection Options (2 of 2) Primary Destination Link Possible Settings: Net1-FR1 Default Setting: Initially blank; no default. Specifies the frame relay interface used as the primary destination link; the to end of a from-to link. The only valid settings for this configuration option are frame relay interfaces that have at least one DLCI or EDLCI defined which are not part of a PVC connection or management link.
  • Page 76: Setting Up Management And Communication Options

    Configuration Setting Up Management and Communication Options The following options can be selected from the Management and Communication menu: Node IP Options Management PVC Options General SNMP Management Options Telnet and FTP Sessions Options SNMP NMS Security Options SNMP Traps and Trap Dial-Out Options Communication Port Options External Modem (COM Port) Options Configuring Node IP Information...
  • Page 77 Configuration Table 3-11. Node IP Options (1 of 2) Node IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address needed to access the node. Since an IP address is not bound to a particular port, it can be used for remote access via a management PVC. 001.000.000.000 –...
  • Page 78 Configuration Table 3-11. Node IP Options (2 of 2) TS Management Link Available Settings: None, PVCname Default Setting: None Specifies a troubleshooting management link for the special needs of network service providers. If the option is changed from the management PVC name to None, the Delete the Management PVC PVCname and the associated DLCI Record? prompt appears.
  • Page 79: Configuring Management Pvcs

    Configuration Configuring Management PVCs Select Management PVCs to define inband management links by adding or changing Management PVCs (see Table 3-12). First, DLCI records must have been configured for the interface where the Management PVC will reside. See Manually Configuring DLCI Records for additional information.
  • Page 80 Configuration Table 3-12. Management PVC Options (2 of 3) Intf Subnet Mask Possible Settings: Node-Subnet-Mask, Calculate, Special ( nnn . nnn . nnn . nnn ) Default Setting: Node-Subnet-Mask Specifies the subnet mask needed to access the unit when the management PVC is providing connectivity to an external IP network (through frame relay) that requires a specific subnet mask for the interface.
  • Page 81 Configuration Table 3-12. Management PVC Options (3 of 3) Primary DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the DLCI number used for the management PVC after the frame relay interface is selected. The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be part of a PVC connection or already assigned as a management PVC.
  • Page 82: Configuring General Snmp Management

    Configuration Configuring General SNMP Management Select General SNMP Management to add, change, or delete the information needed to allow the FrameSaver unit to be managed as an SNMP agent by the NMS supporting the SNMP protocols (see Table 3-13). Main Menu Configuration Management and Communication General SNMP Management...
  • Page 83: Configuring Telnet And/Or Ftp Session Support

    Configuration Configuring Telnet and/or FTP Session Support Telnet and FTP options control whether a Telnet or FTP (File Transport Protocol) session is allowed through an interconnected IP network and the access security applicable to the session. Two Telnet sessions can be active at a time (see Table 3-14).
  • Page 84 Configuration Table 3-14. 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.
  • Page 85 Configuration Table 3-14. Telnet and FTP Session Options (3 of 3) Disconnect Time (Minutes) Possible Settings: 1 – 60 Default Setting: 10 Sets the amount of keyboard inactive time allowed before a user session is disconnected. Display Conditions – This option does not appear when Inactivity Timeout is disabled. 1 –...
  • Page 86: Configuring Snmp Nms Security Options

    Configuration Configuring SNMP NMS Security Options Select SNMP NMS Security from the Management and Communication menu to display, add, or change SNMP security configuration options for the FrameSaver unit to set up trap managers (see Table 3-15). Main Menu Configuration Management and Communication SNMP NMS Security A table is displayed consisting of the network management systems identified by...
  • Page 87: Configuring Snmp Traps And Trap Dial-Out

    Configuration Configuring SNMP Traps and Trap Dial-Out Select SNMP Traps from the Management and Communication menu to configure SNMP traps and dial-out when a trap is generated (see Table 3-16). Main Menu Configuration Management and Communication SNMP Traps SNMP MIBs and Traps, and RMON Alarm Defaults See Appendix B, , for trap format standards and special trap features, including RMON-specific traps, and...
  • Page 88 Configuration Table 3-16. SNMP Traps and Trap Dial-Out Options (2 of 4) 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.
  • Page 89 Configuration Table 3-16. SNMP Traps and Trap Dial-Out Options (3 of 4) Link Traps Interfaces Possible Settings: Network, DSX-1, T1s, Ports, All Default Setting: All Specifies which interfaces will generate linkUp, linkDown, and enterpriseSpecific trap messages. These traps are not supported on the COM port. Network –...
  • Page 90 Configuration Table 3-16. SNMP Traps and Trap Dial-Out Options (4 of 4) Trap Disconnect Possible Settings: Enable, Disable Default Setting: Enable Determines whether the COM port-connected modem disconnects after the SNMP trap message has been sent. This configuration option only applies to modem connections initiated as a result of sending the SNMP trap message.
  • Page 91: Configuring The Communication Port

    Configuration Configuring the Communication Port Select Communication Port from the Management and Communication menu to display or change the communication port configuration options (see Table 3-17). Main Menu Configuration Management and Communication Communication Port Table 3-17. Communication Port Options (1 of 4) Port Use Possible Settings: Terminal, Net Link Default Setting: Terminal...
  • Page 92 Configuration Table 3-17. Communication Port Options (2 of 4) Stop Bits Possible Settings: 1, 2 Default Setting: 1 Determines the number of stop bits used for the COM port. 1 – Provides one stop bit. 2 – Provides two stop bits. Ignore Control Leads Possible Settings: Disable, DTR Default Setting: Disable...
  • Page 93 Configuration Table 3-17. Communication Port Options (3 of 4) Inactivity Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether a user session is disconnected after a specified time of inactivity (no keyboard activity). Display Conditions – This option only appears when Port Use is set to Terminal. Enable –...
  • Page 94 Configuration Table 3-17. Communication Port Options (4 of 4) Link Protocol Possible Settings: PPP, SLIP Default Setting: PPP Specifies the link-layer protocol to be used. Only in effect when the COM port is configured as a network communication link (Port Use option is set to Net Link). Display Conditions –...
  • Page 95: Configuring The Com Port To Support An External Modem

    Configuration Configuring the COM Port to Support an External Modem Select External Modem (Com Port) to display or change the configuration options that control call processing for an external device attached to the COM port (see Table 3-18). Main Menu Configuration Management and Communication External Modem (Com Port)
  • Page 96 Configuration Table 3-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.
  • Page 97: Security And Logins

    Security and Logins This chapter includes the following: Limiting Access Controlling Asynchronous Terminal Access Controlling External COM Port Device Access Controlling Telnet or FTP Access — Limiting Telnet Access — Limiting FTP Access — Limiting Telnet or FTP Access Over the TS Management Link Controlling SNMP Access —...
  • Page 98: Limiting Access

    Security and Logins Limiting Access The FrameSaver unit provides access security on the following interfaces: Asynchronous (async) terminal Telnet 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.
  • Page 99 Security and Logins Procedure To limit asynchronous terminal access to the menu-driven user interface: 1. Select the Communication Port options. Main Menu Configuration Management and Communication Communication Port 2. Set the following configuration options, as appropriate. To . . . Set the configuration option .
  • Page 100: Controlling External Com Port Device Access

    Security and Logins Controlling External COM Port Device Access Dial-in access can be controlled when an external device (modem) is connected to the unit’s communication (COM) port. The External Device Commands option must be set to AT or Other. Procedure To control dial-in access: 1.
  • Page 101: Limiting Telnet Access

    Security and Logins Limiting Telnet Access Telnet access can be limited by: Disabling Telnet access completely. Requiring a login for Telnet sessions that are not on the TS Management Link. Assigning an access level for Telnet sessions. Disabling TS Management Link access. To limit Telnet access via a service provider’s troubleshooting management link, Limiting Telnet or FTP Access Over the TS Management Link Procedure...
  • Page 102: Limiting Ftp Access

    Security and Logins Limiting FTP Access FTP access can be limited by: Disabling FTP access completely. Requiring a user ID and password to login. Limiting FTP bandwidth. Procedure To limit FTP access when the session is not on the TS Management Link: 1.
  • Page 103: Limiting Telnet Or Ftp Access Over The Ts Management Link

    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.
  • Page 104: Controlling Snmp Access

    Security and Logins Controlling SNMP Access The FrameSaver unit supports SNMP Version 1, which provides limited security through the use of community names. There are three methods for limiting SNMP access: Disabling SNMP access. Assigning SNMP community names and the access type. Assigning IP addresses of those NMSs that can access the unit.
  • Page 105: Assigning Snmp Community Names And Access Levels

    Security and Logins Assigning SNMP Community Names and Access Levels The FrameSaver unit supports the SNMP protocol and can be managed by an SNMP manager. SNMP manager access can be limited by: Assigning the SNMP community names that are allowed to access the FrameSaver unit’s Management Information Base (MIB).
  • Page 106: Limiting Snmp Access Through Ip Addresses

    Security and Logins Limiting SNMP Access Through IP Addresses An additional level of security is provided by: Limiting the IP addresses of NMSs that can access the FrameSaver unit. Performing validation checks on the IP address of SNMP management systems attempting to access the FrameSaver unit. Specifying the access allowed for the authorized NMS when IP address validation is performed.
  • Page 107: Creating A Login

    Security and Logins Configuring SNMP NMS Security Options in Chapter 3, Configuration, for more information about SNMP NMS Security configuration options. Creating a Login A login is required if security is enabled.* p to six login ID/password combinations can be created using ASCII text, and each login must have a specified access level.
  • Page 108: Modifying A Login

    Security and Logins Configuring SNMP NMS Security Options in Chapter 3, Configuration, for more information about security configuration options. Modifying a Login Logins are modified by deleting the incorrect login and creating a new one. Deleting a Login Procedure To delete a login record: 1.
  • Page 109: Operation And Maintenance

    Operation and Maintenance This chapter includes the following information: Displaying System Information Viewing LEDs and Control Leads — LED Descriptions — Control Lead Descriptions Device Messages Status Information — System and Test Status Messages , which includes: Self-Test Results Messages Health and Status Messages Test Status Messages —...
  • Page 110: Displaying System Information

    Operation and Maintenance FTP File Transfers — Upgrading System Software — Determining Whether a Download is Completed — Changing Software — Transferring Collected Data 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.
  • Page 111: Viewing Leds And Control Leads

    Operation and Maintenance Viewing LEDs and Control Leads The FrameSaver 9124 unit’s faceplate includes LEDs ( light-emitting diodes) that provide status on the unit and its interfaces. 9124 FrameSaver ® NETWORK PORT 99-15821-02 The Display LEDs and Control Leads screen allows you to monitor a remote unit and is useful when troubleshooting control lead problems.
  • Page 112: Led Descriptions

    Operation and Maintenance LED Descriptions The following table identifies the alarms that cause the Alarm LED to light. See Table 5-2 Table 5-3 for network, DSX-1, and user data port interface LED information. Table 5-1. General Status LEDs Label Indication Color What It Means Power and...
  • Page 113 Operation and Maintenance Table 5-2. Network and DSX-1 Interface LEDs Label Indication Color What It Means Signal Green ON – A recoverable signal is present on the Network/DSX interface. OFF – The signal cannot be recovered from the Network/DSX interface. An LOS condition exists.
  • Page 114: Control Lead Descriptions

    Operation and Maintenance Control Lead Descriptions For the network and DSX-1 interfaces, see Table 5-2, Network and DSX-1 Interface LEDs, for descriptions of these leads. The LED descriptions and control lead descriptions are the same. For Port-1, see Table 5-4, User Data Port LED. These indicators show the current state of each control lead and what they indicate when they are highlighted;...
  • Page 115: Device Messages

    Operation and Maintenance Device Messages These messages appear in the messages area at the bottom of the screens. All device messages are listed in alphabetical order. Table 5-5. Device Messages (1 of 5) Message What It Indicates What To Do Access level is n , User’s access level is 2 No action needed.
  • Page 116 Operation and Maintenance Table 5-5. Device Messages (2 of 5) Message What It Indicates What To Do File Transfer Failed – A file transfer was Try again, making sure you Invalid file attempted, but it was not type the filename correctly. successful.
  • Page 117 Operation and Maintenance Table 5-5. Device Messages (3 of 5) Message What It Indicates What To Do Limit of PVC New was selected from the Do not create the PVC Connections reached PVC Connection Table and connection. the maximum number of Delete another PVC PVCs has already been connection, and try again.
  • Page 118 Operation and Maintenance Table 5-5. Device Messages (4 of 5) Message What It Indicates What To Do No Primary New or Modify was Configure additional DLCIs for Destination Link selected from the PVC the network link and try again. DLCIs Available Connection Table, but even If a network DLCI has been though DLCIs are available...
  • Page 119 Operation and Maintenance Table 5-5. Device Messages (5 of 5) Message What It Indicates What To Do Test Active No higher priority health Contact service provider if test and status messages exist, initiated by the network. and a test is running. Wait until the test ends and message clears.
  • Page 120: Status Information

    Operation and Maintenance Status Information Status information is useful when monitoring the FrameSaver unit. The following illustration shows the Status menu for the FrameSaver 9124 unit. Status Menu Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
  • Page 121: System And Test Status Messages

    Operation and Maintenance System and Test Status Messages System and test status information is selected from the Status menu. Main Menu Status System and Test Status The following information is included on this screen: Self-Test Results Messages Health and Status Messages Test Status Messages Self-Test Results Messages These self-test result messages appear in the Self-Test Results field at the top of...
  • Page 122 Operation and Maintenance Health and Status Messages The following table provides Health and Status messages that apply to the FrameSaver 9124 unit. Table 5-7. Health and Status Messages (1 of 4) What It Indicates Message AIS at DSX-1 An Alarm Indication Signal (AIS) is received by the DSX-1 interface.
  • Page 123 Operation and Maintenance Table 5-7. Health and Status Messages (2 of 4) Message What It Indicates EER at Network 1 The error rate of the received network signal exceeds the currently configured threshold. This condition only occurs if the network interface is configured for ESF framing.
  • Page 124 Operation and Maintenance Table 5-7. Health and Status Messages (3 of 4) Message What It Indicates OOF at Network 1 An Out of Frame (OOF) condition is detected on the network interface. Possible reasons include: Incompatible framing format between the network and the FrameSaver unit.
  • Page 125 Operation and Maintenance Table 5-7. Health and Status Messages (4 of 4) Message What It Indicates Time Slot Discovery in Progress, Time slot discovery is currently taking place to Network 1 determine the time slots that will be used for frame relay traffic on the network interface.
  • Page 126 Operation and Maintenance Table 5-8. Test Status Messages (2 of 2) Message What It Indicates LLB Active, [Network 1/DSX-1] A network Line Loopback (LLB) is active on the specified interface. Monitor Pttn Active, DLCI nnnn , The unit is monitoring a test pattern on the 1, 2 frame_relay_link specified DLCI on the specified frame relay link.
  • Page 127: Network Lmi-Reported Dlcis Status

    Operation and Maintenance Network LMI-Reported DLCIs Status Network LMI-reported DLCI statuses are selected from the Status menu. Main Menu Status LMI Reported DLCIs The LMI Reported DLCIs screen displays the status and CIR (if supported by the switch) for each DLCI, whether the DLCI is configured or not. LMI-Reported DLCIs Status Screen Example Î...
  • Page 128 Operation and Maintenance Table 5-9. Network LMI-Reported DLCIs Status Field Status What It Indicates DLCI 16 through 1007 Identifies the Local Management Interface-reported DLCI numbers assigned to the selected interface – the identifying number assigned to the path between two frame relay FrameSaver units’...
  • Page 129: Pvc Connection Status

    Operation and Maintenance PVC Connection Status PVC connection statuses are selected from the Status menu. Main Menu Status PVC Connection Status Only PVC connections with Source DLCIs configured to be Active are shown. PVC Connection Status Screen Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/status/connections 9124-II Î...
  • Page 130 Operation and Maintenance Table 5-10. PVC Connection Status (2 of 2) Field Status What It Indicates EDLCI 0 to 62 For multiplexed DLCIs only. Identifies an individual link/ connection embedded within a DLCI. Status Identifies whether the physical interfaces, LMIs, and DLCIs are all enabled and active for this PVC connection.
  • Page 131: Time Slot Assignment Status

    Operation and Maintenance Time Slot Assignment Status Time Slot assignments are made using the Time Slot Assignment configuration option. See Assigning Time Slots/Cross Connections in Chapter 3, Configuration , for making time slot assignments. Use the Timeslot Assignment Status screen to display time slot assignments for the network channels and the DSX-1 channels.
  • Page 132 Operation and Maintenance The following information is available for network interface time slots (N01– N24): The Cross Connect Status Field Indicates . . . (bottom) . . . Unassgn The time slot is unassigned. FrameRly1 The time slot is assigned to the network frame relay link.
  • Page 133: Performance Statistics

    Operation and Maintenance The following information is available for DSX-1 interface time slots (D01– D24): The Cross Connect Status Field Indicates the . . . (bottom) . . . blank The time slot is unassigned. Net1 / tt Network interface 1, time slot (tt ) is assigned to DSX-1 time slot (01 to 24) using Clear Channel.
  • Page 134: Clearing Performance Statistics

    Operation and Maintenance Clearing Performance Statistics Performance statistics counters can be reset to the baseline when using a directly-connected asynchronous terminal and your security Access Level is Level-1. This feature is useful when troubleshooting problems. Statistic counters are not actually cleared using this feature. True statistic counts are always maintained so SLAs can be verified, and they can be viewed from an SNMP NMS.
  • Page 135: Service Level Verification Performance Statistics

    Operation and Maintenance Service Level Verification Performance Statistics These statistics appear when Service Level Verification (SLV) is selected from the Performance Statistics menu. Main Menu Status Performance Statistics Service Level Verification They only appear for the network interface and only if DLCIs are multiplexed. Table 5-11.
  • Page 136 Operation and Maintenance Table 5-11. Service Level Verification Performance Statistics (2 of 2) Statistic What It Indicates Inbound Dropped Total number of bytes transmitted by the far-end device that Characters were dropped in transit. The counts continue to increment until the maximum value is reached (2 –2), then the count starts over.
  • Page 137: Dlci Performance Statistics

    Operation and Maintenance The statistics collected by the unit depend upon the device at the far end of the connection. If the far-end device is a FrameSaver SLV unit, frame relay, latency, and FDR/DDR * performance statistics are collected. If the far-end device is a non-FrameSaver device, or a FrameSaver 9120 or 9620, only frame relay statistics are collected.
  • Page 138 Operation and Maintenance Table 5-12. DLCI Performance Statistics (2 of 2) Statistic What It Indicates With BECN Set 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.
  • Page 139: Frame Relay Performance Statistics

    Operation and Maintenance Frame Relay Performance Statistics The following statistics appear when Frame Relay is selected from the Performance Statistics menu. Main Menu Status Performance Statistics Frame Relay All counts continue to increment until the maximum value is reached (2 –2), then the count starts over.
  • Page 140 Operation and Maintenance Table 5-13. 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.
  • Page 141 Operation and Maintenance Table 5-13. 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: Receive invalid frames (short frames, long frames, invalid DLCIs, unknown DLCIs, and unknown errors) Rx Total Discards Receive errors (non-octet aligned frames, frames with CRC...
  • Page 142: Esf Line Performance Statistics

    Operation and Maintenance ESF Line Performance Statistics These statistics appear when ESF Line is selected from the Performance Statistics menu for the network interface. Main Menu Status Performance Statistics ESF Line Only seven T1 network statistical intervals appear on the screen at any one time. You can choose which intervals to display on your screen by entering: Interval Number (01–...
  • Page 143 Operation and Maintenance ESF Line Performance Statistics Screen Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/status/performance/esf 9124-II Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Device Name: Node A 05/26/1999 23:32 Î...
  • Page 144 Operation and Maintenance The following performance statistics are collected for ESF line conditions: Statistic What It Indicates Errored Seconds (ES) Any second with one or more ESF Error events. Unavailable Seconds Any second in which service is unavailable. Begins (UAS) incrementing at the onset of 10 consecutive seconds of severely errored seconds (SES), and stops incrementing after 10 consecutive seconds of no SESs.
  • Page 145: Ftp File Transfers

    Operation and Maintenance FTP File Transfers The FrameSaver unit supports a standard File Transfer Protocol (FTP) server over Transmission Control Protocol (TCP). A complete binary image of the configuration files can be copied to a host to provide a backup. To use this feature, the unit must be configured to support Telnet and FTP Sessions.
  • Page 146 Operation and Maintenance Procedure To initiate an FTP session: 1. Start the FTP client program on your host. For example, on a UNIX host, type ftp, followed by the FrameSaver unit’s IP address. 2. If a login and password are required (see Creating a Login in Chapter 4, Security and Logins ), you are prompted to enter them.
  • Page 147: Upgrading System Software

    Operation and Maintenance Upgrading System Software If you need to upgrade the FrameSaver unit’s program code, you must transfer the upgrade of the nam.ocd file in the system memory directory using the put command. NOTE: Upgrades can be performed through the network using a Management PVC, or through the COM port if Port Use is set to Net Link (see Table 3-17, Communication Port Options).
  • Page 148: Determining Whether A Download Is Completed

    Operation and Maintenance Determining Whether a Download Is Completed To see whether a download has completed, check the Identity screen. Main Menu Status Identity Check Alternate Software Rev. under the NAM Identity column. If a software revision number appears, the file transfer is complete. If In Progress appears, the file is still being transferred.
  • Page 149: Transferring Collected Data

    Operation and Maintenance Transferring Collected Data SLV user history statistics and LMI packet capture data can be uploaded to an NMS or a Network Associates Sniffer using FTP, which is faster than other methods. The rate at which the data file is transferred is the rate set by the FTP Max Receive Rate (Kbps) option (see Table 3-14, Telnet and FTP Session Options...
  • Page 150 Operation and Maintenance This page intentionally left blank. 5-42 March 2000 9124-A2-GB20-00...
  • Page 151: Troubleshooting

    Troubleshooting This chapter includes the following: Problem Indicators Resetting the Unit and Restoring Communication — Resetting the Unit from the Control Menu — Resetting the Unit By Cycling the Power — Restoring Communication with a Misconfigured Unit Troubleshooting Management Link Feature LMI Packet Capture Utility Feature —...
  • Page 152: Problem Indicators

    Troubleshooting Physical Tests — Line Loopback — Payload Loopback — Repeater Loopback — DTE Loopback — Send Line Loopback — Data Channel Loopbacks on a Frame Relay Link Send Remote Line Loopback — Send and Monitor Pattern Tests — IP Ping Test Lamp Test Problem Indicators The unit provides a number of indicators to alert you to possible problems:...
  • Page 153: Resetting The Unit And Restoring Communication

    Troubleshooting Resetting the Unit and Restoring Communication You can reset the unit in one of four ways: Reset it from the Control menu. Cycle the power. Reset the configuration options for the COM port, or reload the factory default settings. Set the appropriate MIB object from NMS (see your NMS documentation).
  • Page 154: Restoring Communication With A Misconfigured Unit

    Troubleshooting Restoring Communication with a Misconfigured Unit Misconfiguring the unit could render the menu-driven user interface inaccessible. If this occurs, connectivity to the unit can be restored via a directly connected asynchronous terminal. Procedure To reset COM port settings: 1. Configure the asynchronous terminal to operate at 19.2 kbps, using character length of 8 bits, with one stop-bit, and no parity.
  • Page 155: Troubleshooting Management Link Feature

    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.
  • Page 156: Viewing Captured Packets From The Menu-Driven User Interface

    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. To view the most recently captured packets using the menu-driven user interface: LMI Packet Capture Utility Display LMI Trace Log LMI Trace Log Example...
  • Page 157: Alarms

    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.
  • Page 158 Troubleshooting Table 6-1. Alarm Conditions (2 of 6) Alarm Condition What It Indicates What To Do DLCI nnnn Down, The DLCI for the specified Verify that the network LMI is up. 1, 2 frame relay link frame relay link is down. If it is, contact your network service provider.
  • Page 159 Troubleshooting Table 6-1. Alarm Conditions (3 of 6) Alarm Condition What It Indicates What To Do LMI Down, The Local Management For the network interface: frame relay link Interface is down for the If LMI was never up, verify specified frame relay link. that the LMI Protocol setting reflects the LMI type being used.
  • Page 160 Troubleshooting Table 6-1. Alarm Conditions (4 of 6) Alarm Condition What It Indicates What To Do LOS at DSX-1 A Loss of Signal (LOS) condition is detected on the DSX-1 interface. Clears when the ratio of ones to zeros received is greater than or equal to 12.5%.
  • Page 161 Troubleshooting Table 6-1. Alarm Conditions (5 of 6) Alarm Condition What It Indicates What To Do OOF at Network 1 An Out of Frame (OOF) condition is detected on the network interface. Incompatible framing Check that the framing format format between the for the network interface is network and the correct.
  • Page 162 Troubleshooting Table 6-1. Alarm Conditions (6 of 6) Alarm Condition What It Indicates What To Do Self-Test Failure The unit did not pass its Reset the unit. basic verification tests Contact your service when it was powered on or representative. reset.
  • Page 163: Troubleshooting Tables

    Troubleshooting Troubleshooting Tables The unit is designed to provide many years of trouble-free service. However, if a problem occurs, refer to the appropriate table in the following sections for possible solutions. Device Problems Table 6-2. Device Problems (1 of 2) Symptom Possible Cause Solutions...
  • Page 164 Troubleshooting Table 6-2. Device Problems (2 of 2) Symptom Possible Cause Solutions Cannot access the Login or password is Reset the unit (see Restoring Communication unit or the incorrect, COM port is menu-driven user misconfigured, or the unit is with a Misconfigured Unit interface.
  • Page 165: Frame Relay Pvc Problems

    Troubleshooting Frame Relay PVC Problems Table 6-3. Frame Relay PVC Problems Symptom Possible Cause Solutions No receipt or Cross Connection of the Verify the PVC connections transmission of data DLCIs are configured and DLCIs by checking the incorrectly. network-discovered DLCIs on the LMI Reported DLCIs screen.
  • Page 166: Tests Available

    Troubleshooting Tests Available The following tests are available to a FrameSaver SLV 9124. Test Menu Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
  • Page 167: Starting And Stopping A Test

    Troubleshooting NOTE: These configuration options do not pertain to tests commanded by the DTE, like a DTE-initiated External Loopback. 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 .
  • Page 168: Aborting All Tests

    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.
  • Page 169: Pvc Tests

    Troubleshooting PVC Tests PVC tests can be run on a requested DLCI for a selected interface. When PVC tests are on a multiplexed DLCI between FrameSaver devices, they are nondisruptive to data, so user data can continue to be sent during a test.
  • Page 170: Pvc Loopback

    Troubleshooting PVC Loopback The PVC Loopback loops frames back to the selected interface on a per-PVC basis. This test logically (not physically) loops back frames received from another FrameSaver device through the selected frame relay PVC to the same device. Main Menu Test Network PVC Tests...
  • Page 171: Monitor Pattern

    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.
  • Page 172: Physical Tests

    Troubleshooting Physical Tests A FrameSaver 9124 unit’s physical tests screen for the network interface is shown below. Main Menu Test [Network Physical Tests/Data Port Physical Tests/ DSX-1 Physical Tests] Physical Tests Screen Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
  • Page 173: Line Loopback

    Troubleshooting Line Loopback The Line Loopback (LLB) loops the information received on the selected interface back to the source of the loopback. When used with a pattern test at the remote node, LLB determines whether the problem is with the sending device or the T1 facility.
  • Page 174: Payload Loopback

    Troubleshooting Payload Loopback The Payload Loopback (PLB) loops the information received on the selected interface back to the network after it has passed through the receive and transmit framing section of the device. Use the PLB to determine whether the problem is with the T1 facility or in the circuitry of the remote device.
  • Page 175: Repeater Loopback

    Troubleshooting Repeater Loopback The Repeater Loopback (RLB) loops data received from the data ports and the DSX-1 interface after the signal has passed through the framing circuitry. Use RLB to ensure that all of the data is correct up to the point where it is sent over the interface.
  • Page 176: Dte Loopback

    Troubleshooting DTE Loopback The DTE external Loopback (DTLB) test loops the received signal on a DTE interface back to the DTE without affecting the operation of the remaining ports. Use this test for isolating problems on the DTE interface. An attached device or test equipment must generate data to be looped back. Network All 1s Interface...
  • Page 177: Send Line Loopback

    Troubleshooting Send Line Loopback The remote Line Loopback (LLB) up and down codes are in-band codes that allow control of a remote device. The LLB Up code invokes a line loopback in the remote unit while the LLB Down code terminates the remote line loopback. Network loopbacks are defined in AT&T TR 62411.
  • Page 178: Data Channel Loopbacks On A Frame Relay Link

    Troubleshooting Data Channel Loopbacks on a Frame Relay Link A network-initiated Data Channel Loopback (DCLB) that loops data over the frame relay link (DS0s) received on the network interface through the FrameSaver unit’s framing circuitry and back to the same interface. A DCLB can be controlled over the frame relay link using one of the following in-band methods: V.54 Loopback.
  • Page 179: Send Remote Line Loopback

    Troubleshooting Send Remote Line Loopback The remote Line Loopback (LLB) up and down codes are in-band codes that allow control of a remote device. The LLB Up code invokes a line loopback in the remote unit while the LLB Down code terminates the remote line loopback. Network loopbacks are defined in AT&T TR 62411.
  • Page 180: Send And Monitor Pattern Tests

    Troubleshooting Send and Monitor Pattern Tests The pattern tests enable a FrameSaver unit to either send or monitor a known bit pattern. These tests generate industry-standard bit patterns that can be used to determine whether information is being correctly transmitted across a circuit. The following test patterns are available: —...
  • Page 181: Ip Ping Test

    Troubleshooting IP Ping Test An IP Ping test can be run to test connectivity between the FrameSaver unit and any FrameSaver unit, router, or NMS to which it has a route. Times when you might want to run an IP Ping test are: To test connectivity between the FrameSaver unit and any FrameSaver unit in the network to verify that the path is operational.
  • Page 182: Lamp Test

    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.
  • Page 183: Setting Up Openlane For Framesaver Devices

    Setting Up the OpenLane SLM System 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: Web and database services Web access to health and status information...
  • Page 184: Setting Up The Openlane Slm System

    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: OpenLane 5.x Service Level Management for UNIX Quick Start Installation Instructions OpenLane 5.x Service Level Management for Windows NT...
  • Page 185: Setting Up Netscout Manager Plus For Framesaver Devices

    Setting Up NetScout Manager Plus for FrameSaver Devices This chapter includes NetScout Manager Plus information as it relates to FrameSaver SLV devices. It includes the following: Before Getting Started Configuring NetScout Manager Plus Adding FrameSaver SLV Units to the NetScout Manager Plus Network —...
  • Page 186: Before Getting Started

    A template of alarms and values for configuring alarms and several templates for creating history files specific to the FrameSaver unit are available. OpenLane paradyne directories include the following: Properties: paradyne.fsd file found in OpenLane/netscout/alarms/directory Properties: paradyne.fst file found in OpenLane/netscout/alarms/directory...
  • Page 187: Configuring Netscout Manager Plus

    Setting Up NetScout Manager Plus for FrameSaver Devices Configuring NetScout Manager Plus For the NetScout Manager Plus main window to appear, make sure your environment is set up exactly as specified in your NetScout Readme file. You need to: Copy the OpenLane directory to a user directory. Add frame relay agents to the NetScout Manager.
  • Page 188: Adding Framesaver Slv Units To The Netscout Manager Plus Network

    6. Minimally, enter the following: — Agent name — IP address — Properties File: Select paradyne. 7. Select the OK button at the bottom of the screen to add the agent, discover its DLCIs, and return to the Configuration Manager main window.
  • Page 189: Verifying Domains And Groups

    Setting Up NetScout Manager Plus for FrameSaver Devices Verifying Domains and Groups Procedure 1. From the NetScout Manager Plus main window, with the FrameRelay and Admin radio buttons still selected, click on the Config Manager icon to open the Configuration Manager main window. 2.
  • Page 190: Correcting Domains And Groups

    Setting Up NetScout Manager Plus for FrameSaver Devices Correcting Domains and Groups Properties need to be edited when not using the Paradyne-provided file and when: An unsupported domain needs to be deleted. A missing domain needs to be added. Groups, Samples, Interval, and Logging are not configured as specified in...
  • Page 191 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.
  • Page 192: Adding Slv Alarms Using A Template

    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. The following alarms are configured for each DLCI included in the Paradyne MIB: — Frames Sent (SLVFramesSnt) — Rx DLCI Utilization (SLVrxDLCIUtil) —...
  • Page 193: Editing Alarms

    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.
  • Page 194 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.
  • Page 195: Adding Slv Alarms Manually

    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).
  • Page 196 Select or Enter . . . Domain User Defined DLCI DLCI number for trap being assigned Stats Type PARADYNE Trap Variable Trap variable to be configured Key1 The ifIndex for the frame relay logical interface is 1 Key2 DLCI number (same as DLCI above)
  • Page 197: Creating History Files

    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.
  • Page 198 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).
  • Page 199: Installing The User-Defined History Files

    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.
  • Page 200: Monitoring A Dlci's History Data

    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.
  • Page 201 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.
  • Page 202: Monitoring The Agent Using Netscout Manager Plus

    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).
  • Page 203 Setting Up NetScout Manager Plus for FrameSaver Devices Procedure 1. Select the Traffic radio button to monitor the newly added agent, or one of its DLCIs. 2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI list box (under the agent list box).
  • Page 204: Statistical Windows Supported

    Setting Up NetScout Manager Plus for FrameSaver Devices Statistical Windows Supported Not all icons that appear on the NetScout Manager Plus main window are supported for FrameSaver units. For example, All Convs (conversations) and TopNConv icons appear when the Protocol radio button is selected, but conversations are not supported.
  • Page 205: Setting Up Network Health For Framesaver Devices

    Setting Up Network Health for FrameSaver Devices FrameSaver units are compatible with Concord Communication’s Network Health software. In addition, Network Health has released the first in a series of software modules that integrate FrameSaver SLV enhanced performance statistics into its reporting package (see the FrameSaver SLV report example on page 9-9).
  • Page 206: Installation And Setup Of Network Health

    Setting Up Network Health for FrameSaver Devices For additional information about installing, accessing, and managing FrameSaver SLV devices through Concord’s Network Health, and for information about applicable reports, refer to: Network Health Installation Guide to help you install the application. Network Health User Guide to help you get started using the application.
  • Page 207: Discovering Framesaver Elements

    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.
  • Page 208: Configuring The Discovered Elements

    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.
  • Page 209: Grouping Elements For Reports

    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).
  • Page 210: Generating Reports For A Group

    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.
  • Page 211: About Trend Reports

    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.
  • Page 212 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.
  • Page 213 Setting Up Network Health for FrameSaver Devices Trend Reports – Perform trend analysis on up to ten specified variables for DLCIs. Variables other than bandwidth can be selected for a trend report (e.g., burst octets), but a bandwidth trend report should be generated when investigating problems that appear on Exceptions Reports, Supplemental Reports, and Health reports.
  • Page 214 Setting Up Network Health for FrameSaver Devices This page intentionally left blank. 9-10 March 2000 9124-A2-GB20-00...
  • Page 215: Menu Hierarchy

    Menu Hierarchy Menus The following is a graphical representation of the FrameSaver SLV 9124 unit’s menu organization. 9124-A2-GB20-00 March 2000...
  • Page 216 Menu Hierarchy Menu Hierarchy MAIN MENU Status Status System and Test Status Test LMI Reported DLCIs Configuration PVC Connection Status Auto-Configuration Timeslot Assignment Status Control Performance Statistics Display LEDs and Control Leads Identity System and PVC Connection Timeslot Identity Performance Test Status Reported Status...
  • Page 217 Menu Hierarchy MAIN MENU Status Load Test Configuration Configuration Configuration Edit/Display from: Auto-Configuration System Control Network DSX-1 Data Ports Time Slot Assignment PVC Connections Management and Communication System Network and Time Slot PVC Connection Management and Data Ports Assignment Table Communication Options •...
  • Page 218 Menu Hierarchy This page intentionally left blank. March 2000 9124-A2-GB20-00...
  • Page 219: Bsnmp Mibs And Traps, And Rmon Alarm Defaults

    — FrameSaver Unit’s sysDescr (system 1) — FrameSaver Unit’s sysObjectID (system 2) Interfaces Group (mib-2) — Paradyne Indexes to the Interface Table (ifTable) — NetScout Indexes to the Interface Table (ifTable) Standards Compliance for SNMP Traps — Trap: warmStart —...
  • Page 220: Mib Support

    Enterprise MIB RMON Version 1 MIB (RFC 1757) RMON Version 2 MIB (RFC 2021) Downloading MIBs and SNMP Traps Paradyne standard and enterprise MIBs are available from the Paradyne World Wide Web site. Procedure To access Paradyne MIBs: 1. Access the Paradyne World Wide Web site at www.paradyne.com.
  • Page 221: System Group (Mib-2

    The following is the system description (sysDescr [system 1] ) for the NMS subsystem in the FrameSaver 9124 unit: PARADYNE T1 FrameSaver SLV; Model: 9124-II; S/W Release: (MM.mm.bb [MM=Major.mm=minor.bb=build] format) ; NAM CCA number: (hardware version in hhhh-hhh format) ; Serial number: sssssss FrameSaver Unit’s sysObjectID (system 2)
  • Page 222: Interfaces Group (Mib-2

    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. Paradyne Interface Objects Information ifName...
  • Page 223: Netscout Indexes To The Interface Table (Iftable

    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)
  • Page 224: Standards Compliance For Snmp Traps

    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”...
  • Page 225: Trap: Warmstart

    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 Reset command sent. reinitialized and stabilized Power disruption.
  • Page 226: Traps: Linkup And Linkdown

    SNMP MIBs and Traps, and RMON Alarm Defaults Traps: linkUp and linkDown These traps are supported on the following interfaces: Network, DSX-1, and synchronous data ports – Physical sublayer interfaces Frame relay logical link layer interfaces Table B-5. linkUp and linkDown Traps Trap What It Indicates Possible Cause...
  • Page 227 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings (1 of 2) Interface Variable-Bindings Possible Cause Physical Sublayer Network, ifIndex (RFC 1573) linkDown – One or more alarm DSX-1 conditions are active on the ifAdminStatus interface.
  • Page 228 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings (2 of 2) Interface Variable-Bindings Possible Cause Logical Link Sublayer Synchronous ifIndex (RFC 1573) linkDown – LMI is down for the Data Port LMI Protocol configured, ifAdminStatus Frame Relay link is disabled.
  • Page 229: Traps: Enterprise-Specific

    SNMP MIBs and Traps, and RMON Alarm Defaults Traps: enterprise-Specific These traps indicate that an enterprise-specific event has occurred. Supported enterprise-specific traps are listed below. Table B-7. enterprise-Specific Traps and Variable-Bindings (1 of 3) Trap Variable-Bindings Possible Cause enterpriseCIR- devFrExtDlciIfIndex CIR has changed due to the LMI Change(15) (devFrExt.mib)
  • Page 230 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. enterprise-Specific Traps and Variable-Bindings (2 of 3) Trap Variable-Bindings Possible Cause devFrExtDlciIfIndex enterpriseMissedSLV- SLV Timeout Error Event (devFrExt.mib) Down(16) Threshold has been exceeded. devFrExtDlciDlci String: (devFrExt.mib) ‘SLV down on $ifString due to excessive SLV packet loss.
  • Page 231 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. enterprise-Specific Traps and Variable-Bindings (3 of 3) Trap Variable-Bindings Possible Cause enterpriseSecondary- devLastTrapString Operating software has detected (devHealthAndStatus.- ClockFail(4) that the secondary clock source mib) has failed. String: ‘Secondary clock failed.’ enterpriseSecondary- Operating software has detected ClockFailClear(104)
  • Page 232: Traps: Rmon-Specific

    SNMP MIBs and Traps, and RMON Alarm Defaults Traps: RMON-Specific Two traps are defined to support the Alarm and Events Groups of RMON. See RMON Alarm and Event Defaults for the default values that will generate RMON-specific traps. Table B-8. RMON-Specific Traps and Variable-Bindings Trap Variable-Bindings Possible Cause...
  • Page 233: Rmon Alarm And Event Defaults

    FrameSaver unit, shows the alarm and event types, the interval used when generating alarms, and thresholds. Physical Interface Alarm Defaults Frame Relay Link Alarm Defaults DLCI Alarm Defaults – Paradyne Area DLCI Alarm Defaults – NetScout Area Standards Compliance for SNMP Traps for information about how traps...
  • Page 234: Physical Interface Alarm Defaults

    SNMP MIBs and Traps, and RMON Alarm Defaults Physical Interface Alarm Defaults This alarm only applies to the FrameSaver unit’s network interface. Table B-9. Network Physical Interface Alarm Defaults Rising Falling Threshold Threshold Sample Event Item Type MIB/Tag/OID Interval Type Default Default Unavailable...
  • Page 235: Frame Relay Link Alarm Defaults

    SNMP MIBs and Traps, and RMON Alarm Defaults Frame Relay Link Alarm Defaults These alarms apply to the FrameSaver unit’s frame relay link interfaces. They are created during RMON initialization. Table B-10. Frame Relay Link Alarm Defaults (1 of 2) Rising Falling Sample...
  • Page 236 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-10. Frame Relay Link Alarm Defaults (2 of 2) Rising Falling Threshold Threshold Sample Event Item Type MIB/Tag/OID Interval Type Default Default Tx Total Errors MIB: pdn_FrExt.mib (E) 900 secs Rising (15 mins) Tag: devFrExtLinkTotTxErrs OID: .1.3.6.1.4.1.1795.2.24.2.
  • Page 237: Dlci Alarm Defaults - Paradyne Area

    These alarms apply to all DLCIs on the network interface and can be created during RMON initialization or when a DLCI is created. They are put into the Paradyne alarm area. Table B-11. DLCI Alarm Defaults – Paradyne Area Rising Falling...
  • Page 238: Dlci Alarm Defaults - Netscout Area

    SLA between the customer and service provider. Up to eight alarms per interface are allowed. Any additional alarms are added to the Paradyne Area alarms and they cannot be changed using NetScout software. Editing Alarms in Chapter 8, Setting Up NetScout Manager Plus for FrameSaver Devices .
  • Page 239 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-12. Static DLCI Alarm Defaults – NetScout Area (2 of 2) Rising Falling Threshold Threshold Sample Event Item Type MIB/Tag/OID Interval Type Default Default Tx CIR Utilization MIB: FR DTE MIB 60 secs None Must be...
  • Page 240: Object Id Cross-References (Numeric Order

    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.
  • Page 241 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (1 of 4) Object ID (OID) Item MIB/Tag .1.3.6.1.2.1.2.2.1..1.3.6.1.2.1.2.2.1.5.I Link Speed MIB: MIB II (RFC 1573) Tag: ifSpeed All DLCI + LMI Rx Octets MIB: MIB II (RFC 1573) .1.3.6.1.2.1.2.2.1.10.I Tag: ifInOctets...
  • Page 242 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (2 of 4) Object ID (OID) Item MIB/Tag .1.3.6.1.4.1.1795.2.24.2. . . MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.5.4.8.1.2.I Unavailable Seconds Tag: devFreeRunUAS .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.16.I Rx Non-octet Aligns MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkRxNonOctet MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.13.1.2.1.4.H.T.N IP Top Listeners (1–...
  • Page 243 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (3 of 4) Object ID (OID) Item MIB/Tag .1.3.6.1.4.1.1795.2.24.2.6.9.4 ..1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.41.I.D Network Frames Dropped MIB: pdn_FrExt.mib (E) In CIR Tag: devFrExtDlciDropOffFrInCir .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.43.I.D Network Frames Offered MIB: pdn_FrExt.mib (E) Above CIR Tag: devFrExtDlciRmtOffFrOutCir...
  • Page 244 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (4 of 4) Object ID (OID) Item MIB/Tag .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1. . . MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.2.I.D.N Burst Upper Limit (1– 5) 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 MIB: pdn_FrExt.mib (E)
  • Page 245 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. Alarm OID Cross-Reference (1 of 2) Object ID (OID) Item MIB/Tag .1.3.6.1.2.1.10.18.9.1. . . MIB: DS1/E1 MIB (RFC 1406) .1.3.6.1.2.1.10.18.9.1.5.I Unavailable Seconds Tag: dsx1TotalUASs .1.3.6.1.2.1.10.32.2.1..1.3.6.1.2.1.10.32.2.1.4.I.D Rx FECNs MIB: FR DTE MIB (RFC 2115) Tag: frCircuitReceivedFECNs .1.3.6.1.2.1.10.32.2.1.5.I.D...
  • Page 246 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. Alarm OID Cross-Reference (2 of 2) Object ID (OID) Item MIB/Tag .1.3.6.1.4.1.1795.2.24.2.6.9.4. . . MIB: pdn_FrExt.mib (E) .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.7.I.D Current Latency Tag: devFrExtLatencyLatest .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.2.I.N Frame Size Upper Limits MIB: pdn_FrExt.mib (E) 1–...
  • Page 247: C Connectors, Cables, And Pin Assignments

    Connectors, Cables, and Pin Assignments This appendix shows the FrameSaver unit’s rear panel, and the pin assignments for the connectors/interfaces and cables. Rear Panel The following illustration shows the FrameSaver 9124 rear panel. POWER DSX-1 MDM 99-16353 The sections that follow provide pin assignments for each interface. NOTE: In the pin assignment tables of this appendix, if the pin number is not shown, it is not being used.
  • Page 248: Com Port Connector

    Connectors, Cables, and Pin Assignments COM Port Connector The following table provides the pin assignments for the FrameSaver 9626 unit’s 25-position EIA-232C communication port connector. Signal Direction Pin # Shield (GND) — DCE Transmit Data ( TXD ) From DTE ( In ) DCE Receive Data ( RXD ) To DTE ( Out ) DCE Request To Send ( RTS )
  • Page 249: Lan Adapter Converter And Cable

    Connectors, Cables, and Pin Assignments LAN Adapter Converter and Cable If connecting to a LAN, order a plug-to-modular jack converter and a LAN Adapter cable. The following shows the pin assignments for the: DB25 plug-to-8-position modular jack converter between the COM port and the 8-conductor LAN Adapter cable (Feature No.
  • Page 250: Standard Eia-232-D Crossover Cable

    Connectors, Cables, and Pin Assignments Standard EIA-232-D Crossover Cable A standard crossover cable can be used to connect the COM port to an external modem. The external modem must be configured so it is compatible with the FrameSaver unit. See page C-5 to configure an external modem.
  • Page 251 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.
  • Page 252: Port 1 Connector

    Connectors, Cables, and Pin Assignments Port 1 Connector The following table provides the pin assignments for the 34-position V.35 connector to the DTE. 34-Pin Signal ITU CT# Direction Socket Shield — Signal Ground/Common — Request to Send ( RTS ) To DSU (In) Clear to Send ( CTS ) From DSU (Out)
  • Page 253: Standard V.35 Straight-Through Cable

    Connectors, Cables, and Pin Assignments Standard V.35 Straight-through Cable A standard V.35 straight-through cable can be used to connect a DTE port to a DTE, where a 34-pin plug-type connector is needed for the data port and a 34-position socket-type connector is needed for the DTE. No special-order cables are required.
  • Page 254: T1 Network Cable (Feature No. 3100-F1-500)

    Connectors, Cables, and Pin Assignments T1 Network Cable (Feature No. 3100-F1-500) Network access is via a 20-foot cable with an RJ48C unkeyed plug-type connector on each end. The following table shows pin assignments and the purpose of each. Function Circuit Direction Pin Number Receive Ring...
  • Page 255: Dsx-1 Connector

    Connectors, Cables, and Pin Assignments DSX-1 Connector If your model includes a DSX-1 interface, the following table shows the signals and pin assignments for the 8-position modular DSX-1 interface. The DSX-1 Adapter is required for this interface. Function Circuit Direction Pin Number Receive Ring From DTE...
  • Page 256 Connectors, Cables, and Pin Assignments This page intentionally left blank. C-10 March 2000 9124-A2-GB20-00...
  • Page 257: Technical Specifications

    Technical Specifications Table D-1. FrameSaver SLV 9124 Technical Specifications (1 of 2) Specification Criteria Approvals FCC Part 15 Class A digital device FCC Part 68 Refer to the equipment’s label for the Registration Number. Industry Canada Refer to the equipment’s label for the Certification Number.
  • Page 258 Technical Specifications Table D-1. FrameSaver SLV 9124 Technical Specifications (2 of 2) Specification Criteria COM Port 25-position (DB25) connector Standard EIA-232/ ITU, V.24 (ISO 2110) Data rates 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.2 kbps T1 Network Interface 8-position modular unkeyed USOC RJ48C jack Data rates Up to 1.536 Mbps...
  • Page 259: Equipment List

    FrameSaver SLV 9124 T1 Remote Site with 64 PVCs 9124-A2-201 Includes 1-Slot Housing, 120 Vac Power Supply, Network Cable, Installation Instructions, and Quick Reference. FrameSaver SLV 9124 T1 Japanese Central Site with 120 PVCs 9124C Includes 1-Slot Housing, 100 – 240 Vac Power Supply, Network 9124-A2-404-002 Cable, Installation Instructions, and Quick Reference.
  • Page 260: Cables

    Equipment List Model/ Feature Description Number Optional Features Wall Mounting Kit for 1-Slot Housing 9001-F1-891 Shelf Mounting Kit for 1-Slot Housings 9001-F1-894 Cables This table lists cables you can order. Description Part Number Feature Number RJ48C T1 Network Cable, 035-0209-2031 3100-F1-500 unkeyed RJ48C-to-unkeyed RJ48C/RJ49C –...
  • Page 261: Index

    Index assigning, community names and access levels, 4-9 Numbers AT commands, 3-67 55 hexadecimal, test pattern, 6-20, 6-21 At-a-Glance report, 9-6 authentificationFailure trap, B-7 Auto-Configuration, 1-2, 2-4 Active, 5-14 aborting tests, 6-18 setting up, 3-10 Access availability, LMI and PVC, 1-3 Dial-In, 3-67 Name, 3-54 Type, 3-58...
  • Page 262 Index Clearing Control Leads and LEDs, displaying, 5-3 controlling cross connection assignments, 3-32 Event, LMI, 3-19, 3-41 async terminal access, 4-2 external device access, 4-4 existing information, 3-8 clearing statistics, 5-26 FTP access, 4-4 Clock SNMP access, 4-8 Invert Transmit, 3-28 Telnet access, 4-4 setting system, 3-8 conversation elements, 9-3...
  • Page 263 Index Dial-In Access, 3-67 Dial-Out Loopback, 6-26 Delay Time (Min), 3-62 port connector pin assignments, C-6 Directory, 3-62 port-initiated loopbacks, 3-29 options, 3-9, 3-59 DTLB, 6-26 Trap, 3-61 Directory, Alternate Dial-Out, 3-62 control lead, 5-6 disabling, SNMP access, 4-8 down, 6-8 Discard Eligible (DE), 3-52 down from Port-1 Device, 5-14 Disconnect, Time (Minutes), 3-57, 3-65...
  • Page 264 Index faceplate, 5-3 Identity, displaying, 5-2 FDR, 1-2 Ignore Control Leads, 3-64 features, 1-2 Inactivity Timeout, 3-56, 3-65 field is blank/empty, 2-9 Initial Route Destination, 3-60 file transfer, 5-37 installation and setup, Network Health, 9-2 FTP (file transfer protocol), 3-57 installing Session, 3-57 Network Health, 9-2...
  • Page 265 Index Line logins, 4-1 Loopback Build Out (LBO), 3-24 Coding Format, 3-24, 3-30 Data Channel, 6-28 DTE, 6-26 Equalization, 3-31 Framing Format, 3-24, 3-30 FT1, 6-28 Loopback, 6-23 Line, 6-23 Link Payload, 6-24 Destination, 3-47 Port (DTE) Initiated, 3-29 frame relay statistics, 5-31 PVC, 6-20 Protocol, 3-66 Remote, 6-27, 6-29...
  • Page 266 Index minimal remote configuration, 3-8 Network Health, installation and setup, 9-2 Network Initiated DCLB, 3-26 Mode changing Operating, demos, 3-16 IP Address, 3-58, 3-59, 4-10 Test, 5-4 model number, 2-5 IP Validation, 3-58, 4-10 modem OpenLane management solution, 1-4 Health and Status messages, 5-14 SNMP security, options, 3-58 setting up, 3-9 Node...
  • Page 267 Index Payload Loopback, 6-24 availability, 1-3 performance statistics, 5-25, 6-2 clearing, 5-26 connection status, 5-21 connections, 3-46 Performance Wizard, copying directory, 8-2 physical total number, 1-3 data port options, 3-28 Loopback, 6-20 DSX-1, 3-30 Management, 3-51 tests, 6-22 total number dedicated, 1-3 pin assignments name, 3-49, 3-50, 3-60 COM port, C-2...
  • Page 268 Index router, setting up to receive RIP, 3-15 setting up auto-configuration, 3-10 router-independence, 1-3, 3-18 Routing, Information Protocol (RIP), 3-66 external modem, 3-9 local management, 3-14 running reports, 9-6 RXD, control lead, 5-6 service provider connectivity, 3-15 SNMP trap managers, 3-58 so router can receive RIP, 3-15 SIG, LED, 5-5 Sampling, SLV Inband and Interval, 3-20...
  • Page 269 Index statistics, 1-3, 5-25 Terminal, Port Use, 3-63 Test elements, 9-3 selecting performance intervals for display, 5-34 menu/branch, 2-4 uploading to an NMS, 5-41 Mode, 5-4 Status Status messages, DBM, 5-17 DLCI, 5-19 Tests, 1-3 Enquiry, LMI, 3-19, 3-41 aborting, 6-18 Health and, 5-14 available, 6-16 information, 5-12...
  • Page 270 Index Traps authentificationFailure, B-7 V.35 DLCI, 3-61 connector, C-6 Enterprise Specific, 3-60, B-11 crossover cable, C-7 General, 3-60 straight-through cable, C-7 Link, 3-60 V.54 Loopback, 3-26, 5-17 Link Interfaces, 3-61 V.54 Loopback, 6-28 linkUp and linkDown, B-8 Value Out of Range message, 3-43, 3-44 RMON, 3-61 variable-bindings, B-9, B-14 RMON Specific, B-14...

Table of Contents