Page 1 FrameSaver SLV 9664 USER’S GUIDE Document No. 9664-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
Contents About This Guide Purpose and Intended Audience Document Organization Product-Related Documents Conventions Used About the FrameSaver SLV 9664 SLM Overview FrameSaver SLV 9664 Features User Interface and Basic Operation Logging On Main Menu Screen Work Areas Navigating the Screens...
Page 4 Contents Configuration 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 Setting Up Call Directories for Trap Dial-Out Setting Up Auto-Configuration Selecting a Frame Relay Discovery Mode Automatically Removing a Circuit...
Page 5 Security and Logins 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 Disabling SNMP Access Assigning SNMP Community Names and Access Levels Limiting SNMP Access Through IP Addresses Creating a Login...
Page 6 Contents Troubleshooting 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 Viewing Captured Packets from the Menu-Driven User Interface Alarms Troubleshooting Tables Device Problems...
Page 7 Setting Up NetScout Manager Plus for FrameSaver Devices Before Getting Started Configuring NetScout Manager Plus Adding FrameSaver SLV Units to the NetScout Manager Plus Network Verifying Domains and Groups Correcting Domains and Groups Adding SLV Alarms Using a Template Editing Alarms Adding SLV Alarms Manually Creating History Files Installing the User-Defined History Files...
Page 8 Downloading MIBs and SNMP Traps System Group (mib-2) 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 Trap: authenticationFailure...
Page 9: About This Guide
Purpose and Intended Audience This document contains information needed to properly set up, configure, and verify operation of FrameSaver SLV 9664 units with Service Level Verifier (SLV) functionality designed for ISDN leased line applications. The unit is intended for use at sites where access is at either 64 kbps or 128 kbps.
Page 10 Appendix B Appendix C Appendix D Appendix E Index 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 viii Description Setting Up OpenLane for FrameSaver Devices. Identifies where installation and setup information is located and how FrameSaver units are supported.
Page 11: Product-Related Documents
09-10020-005 09-10050-002 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 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 Menu selection sequence ( Path:) Brackets [ ] Text highlighted in red When Used 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 9664
About the FrameSaver SLV 9664 This chapter includes the following: SLM Overview FrameSaver SLV 9664 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 9664 Features
About the FrameSaver SLV 9664 FrameSaver SLV 9664 Features The FrameSaver SLV 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 Network Associates Sniffer for analysis, or viewed via the menu-driven user interface. The 12 most recent LMI messages can be displayed from the menu-driven user interface. 9664-A2-GB20-00 About the FrameSaver SLV 9664 March 2000 FrameSaver SLV 9664...
Page 16 About the FrameSaver SLV 9664 ATM VPI/VCI and DLCI Correlation. For networks with both ATM and frame relay-access endpoints, allows the FrameSaver unit to report the originating Virtual Path or Channel Identifier (VPI/VCI) in the far-end ATM-access endpoint where the local DLCI is mapped so they can be correlated for OpenLane SLV reports.
Page 17 — Optional standalone NetScout Probes can be used with FrameSaver devices at sites where full 7-layer monitoring, an unlimited number of protocols, and advanced frame capture and decode capabilities are desired. 9664-A2-GB20-00 About the FrameSaver SLV 9664 March 2000...
Page 18 About the FrameSaver SLV 9664 This page intentionally left blank. March 2000 9664-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 If two sessions are already active, wait and try again. If attempting to access the unit through Telnet, the local Telnet client process returns a Connection refused: message at the bottom of the screen. If attempting to access the unit over the COM port, not via Telnet, the User Interface Already In Use screen is redisplayed.
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
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. 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
Function Keys All function keys (located in the lower part of the screen; see the page 2-5) operate the same way throughout the screens. They are not case-sensitive, so upper- or lowercase letters can be used interchangeably. These keys use the following conventions: Select .
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
Selecting a Field Once you reach the desired menu or screen, select a field to view or change, or issue a command. Press the Tab or right arrow key to move the cursor from one field to another. The current setting or value appears to the right of the field. Entering Information You can enter information in one of three ways.
Page 28 User Interface and Basic Operation This page intentionally left blank. 2-10 March 2000 9664-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 User Data Port Configuring Frame Relay for an Interface Manually Configuring DLCI Records Configuring PVC Connections Setting Up Management and Communication Options...
Page 31: Basic Configuration
Basic Configuration Configuration option settings determine how the FrameSaver unit operates. Use the FrameSaver unit’s Configuration Edit/Display menu to display or change configuration option settings. Configuration Menu Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/config Î...
Page 32: Configuration Option Areas
Factory Default Configuration option area. You can find the default settings for configuration options in the: FrameSaver SLV 9664 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
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 2. Select the configuration options that are applicable to your network, and make appropriate changes to the setting(s).
Page 35: Saving Configuration Options
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-9, Entering System Information and Setting the System Clock Select System Information to set up or display the general SNMP name for the unit, its location, and a contact for the unit, as well as to set the system clock.
Page 37: Setting Up For Trap Dial-Out
Setting Up for Trap Dial-Out An external modem can be attached to the COM port for dialing out when an SNMP trap is generated. To set up an external modem, you need to: 1. Set up SNMP trap managers. 2. Set up an external modem. 3.
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
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
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 General SNMP Management See Table 3-11,...
Page 43: Setting Up So The Router Can Receive Rip
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 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. 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 Configuring Frame Relay for an Interface 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 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 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 Table 3-3. General System Options Test Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether or not loopback and pattern tests have a duration after which they are terminated automatically.
Page 51: Configuring The Physical Interfaces
Configuring the Physical Interfaces Characteristics for the following physical interfaces can be configured: Network Interface User Data Port Configuring the Network Interface Select Physical to display or change the physical configuration options for the port being used as the network interface (see Table 3-4). Main Menu Table 3-4.
Page 52: Configuring The User Data Port
Configuration Configuring the User Data Port Select Physical to display or change the physical characteristics of the user data port connected to the DTE (see Table 3-5). Main Menu Table 3-5. User Data Port Physical Interface Options (1 of 2) Port Type Possible Settings: E530, V.35, X.21 Default Setting: V.35...
Page 53 Table 3-5. User Data Port Physical Interface Options (2 of 2) Monitor DTR Possible Settings: Enable, Disable Default Setting: Enable Specifies whether the state of the DTE Ready (DTR) circuit on the user data port will be used to determine when valid data communication is possible with the DTE. When the DTR off condition is detected, an alarm is generated, LMI is declared down, and no further transfer of frame relay data can occur on this interface.
Page 54: 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 Main Menu Configuring Frame Relay and LMI for the System Table 3-6. Interface Frame Relay Options (1 of 3) LMI Protocol Possible Settings: Initialize_From_Net1FR1, Initialize_From_Interface, Auto_On_LMI_Fail, Standard, Annex-A, Annex-D...
Page 55 Configuration Table 3-6. Interface Frame Relay Options (2 of 3) LMI Parameters Possible Settings: System, Custom Default Setting: System Allows you to use the system LMI options, or to set specific LMI options for this interface. System – Use system LMI options (see Table 3-1, System Frame Relay and LMI Options).
Page 56: Manually Configuring Dlci Records
Configuration Table 3-6. Interface Frame Relay Options (3 of 3) LMI Inbound Heartbeat (T2) Possible Settings: 5, 10, 15, 20, 25, 30 Default Setting: 15 Configures the LMI-defined T2 parameter, which sets the number of seconds between the receipt of status enquiry messages on the network side of the LMI. Applies to the network side of a UNI only.
Page 57 Table 3-7. DLCI Record Options (2 of 3) DLCI Type Possible Settings: Standard, Multiplexed Default Setting: For user data port DLCIs: Standard For network interface DLCIs: Multiplexed Specifies whether the DLCI is standard or multiplexed. This field is read-only when the selected DLCI is used in a PVC or Management link connection and the DLCI Type is Standard.
Page 58 Configuration Table 3-7. DLCI Record Options (3 of 3) Possible Settings: 0 – 128000 Default Setting: 64000 Allows you to display or change the DLCI’s committed burst size, in bits. Display Conditions – This option only appears when Committed Burst Size is set to Other.
Page 59: Configuring Pvc Connections
Configuring PVC Connections The Auto-Configuration feature automatically configures PVC Connections and their DLCI Records. PVC Connections can also be created manually (see Table 3-8). Main Menu From this screen, you can go directly to the Management PVC screen by selecting the MgmtPVCs function key for easy movement between screens. Quick removal of unused DLCIs included in an existing PVC Connection, except for HQ_Site, is also available when the De l ete function key is selected and you respond Yes to the Remove otherwise unused components associated...
Page 60 Configuration Table 3-8. PVC Connection Options (2 of 2) Primary Destination Link Possible Settings: Net1-FR1 Default Setting: Initially blank; no default. Specifies the frame relay interface used as the primary destination link; the to end of a from-to link. The only valid settings for this configuration option are frame relay interfaces that have at least one DLCI or EDLCI defined which are not part of a PVC connection or management link.
Page 61: Setting Up Management And Communication Options
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 62 Configuration Table 3-9. Node IP Options (1 of 2) Node IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the IP address needed to access the node. Since an IP address is not bound to a particular port, it can be used for remote access via a management PVC. 001.000.000.000 –...
Page 63 Table 3-9. Node IP Options (2 of 2) TS Management Link Available Settings: None, PVCname Default Setting: None Specifies a troubleshooting management link for the special needs of network service providers. If the option is changed from the management PVC name to None, the Delete the Management PVC PVCname and the associated DLCI Record? prompt appears.
Page 64: Configuring Management Pvcs
Configuration Configuring Management PVCs Select Management PVCs to define inband management links by adding or changing Management PVCs (see Table 3-10). First, DLCI records must have been configured for the interface where the Management PVC will reside. See Manually Configuring DLCI Records Main Menu Management PVCs Select New or M o dify to add or change Management PVCs.
Page 65 Configuration Table 3-10. Management PVC Options (2 of 3) Intf Subnet Mask Possible Settings: Node-Subnet-Mask, Calculate, Special ( nnn . nnn . nnn . nnn ) Default Setting: Node-Subnet-Mask Specifies the subnet mask needed to access the unit when the management PVC is providing connectivity to an external IP network (through frame relay) that requires a specific subnet mask for the interface.
Page 66 Configuration Table 3-10. Management PVC Options (3 of 3) Primary DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the DLCI number used for the management PVC after the frame relay interface is selected. The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be part of a PVC connection or already assigned as a management PVC.
Page 67: Configuring General Snmp Management
Configuring General SNMP Management Select General SNMP Management to add, change, or delete the information needed to allow the FrameSaver unit to be managed as an SNMP agent by the NMS supporting the SNMP protocols (see Table 3-11). Main Menu General SNMP Management Table 3-11.
Page 68: 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-12).
Page 69 Table 3-12. Telnet and FTP Session Options (2 of 3) Session Access Level Possible Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies the highest security level allowed when accessing the menu-driven user interface via a Telnet session. If a login is required for the session, the effective access level is also determined by the user’s access level.
Page 70 Configuration Table 3-12. Telnet and FTP Session Options (3 of 3) FTP Login Required Possible Settings: Enable, Disable Default Setting: Disable Specifies whether a login ID and password are required for an FTP session. If required, the login used is the same login used for a menu-driven user interface session. This option does not affect the TS Management Link.
Page 71: Configuring Snmp Nms Security Options
Configuring SNMP NMS Security Options Select SNMP NMS Security from the Management and Communication menu to display, add, or change SNMP security configuration options for the FrameSaver unit to set up trap managers (see Table 3-13). Main Menu SNMP NMS Security A table is displayed consisting of the network management systems identified by IP address that are allowed to access the FrameSaver unit by SNMP.
Page 72: 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-14). Main Menu SNMP Traps See Appendix B, format standards and special trap features, including RMON-specific traps, and the default settings that will generate RMON-specific SNMP traps.
Page 73 Table 3-14. SNMP Traps and Trap Dial-Out Options (2 of 5) Initial Route Destination Possible Settings: AutoRoute, COM, PVCname Default Setting: AutoRoute Specifies the initial route used to reach the specified Trap Manager. When proprietary RIP is active, only one unit in the network needs to specify an interface or management link as the initial destination.
Page 74 Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (3 of 5) Link Traps Possible Settings: Disable, Up, Down, Both Default Setting: Both Determines whether SNMP linkDown or linkUp traps are sent to the currently configured trap manager(s). A linkDown trap indicates that the unit recognizes a failure in one of the interfaces.
Page 75 Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (4 of 5) Trap Dial-Out Possible Settings: Enable, Disable Default Setting: Disable Controls whether SNMP trap messages initiate a call automatically. If the call cannot be completed and the Call Retry option is set to Enable, the SNMP trap message is held (queued) until the call completes to either the Alarm or alternate directory.
Page 76 Configuration Table 3-14. SNMP Traps and Trap Dial-Out Options (5 of 5) Alternate Dial-Out Directory Possible Settings: None, 1 – 5 Default Setting: None Specifies whether an incomplete call (busy, or no answer, etc.) resulting from an attempt to send an SNMP trap message is retried using an alternate telephone number. Up to 5 alternate call directories can be set up, but only one at a time can be used.
Page 77: Configuring The Communication Port
Configuring the Communication Port Select Communication Port from the Management and Communication menu to display or change the communication port configuration options (see Table 3-15). Main Menu Communication Port Table 3-15. Communication Port Options (1 of 4) Port Use Possible Settings: Terminal, Net Link Default Setting: Terminal Assigns a specific use to the COM port.
Page 78 Configuration Table 3-15. Communication Port Options (2 of 4) Stop Bits Possible Settings: 1, 2 Default Setting: 1 Determines the number of stop bits used for the COM port. 1 – Provides one stop bit. 2 – Provides two stop bits. Ignore Control Leads Possible Settings: Disable, DTR Default Setting: Disable...
Page 79 Table 3-15. Communication Port Options (3 of 4) Inactivity Timeout Possible Settings: Enable, Disable Default Setting: Enable Determines whether a user session is disconnected after a specified time of inactivity (no keyboard activity). Display Conditions – This option only appears when Port Use is set to Terminal. Enable –...
Page 80 Configuration Table 3-15. Communication Port Options (4 of 4) Link Protocol Possible Settings: PPP, SLIP Default Setting: PPP Specifies the link-layer protocol to be used. Only in effect when the COM port is configured as a network communication link (Port Use option is set to Net Link). Display Conditions –...
Page 81: Configuring The Com Port To Support An External Modem
Configuring the COM Port to Support an External Modem Select External Modem (Com Port) to display or change the configuration options that control call processing for an external device attached to the COM port (see Table 3-16). Main Menu External Modem (Com Port) NOTE: A standard EIA-232 crossover cable is required when connecting an external modem to the FrameSaver unit’s COM Port.
Page 82 Configuration Table 3-16. External Modem (COM Port) Options (2 of 2) Alternate IP Address Possible Settings: 001.000.000.000 – 223.255.255.255, Clear Default Setting: Clear (000.000.000.000) Specifies the Alternate IP Address for the COM port when the alternate phone directory is used. If this configuration option is not configured (i.e., it is zero), the COM port’s primary IP Address is used when the alternate telephone directory is used.
Page 83: Security And Logins
Security and Logins This chapter includes the following: Limiting Access Controlling Asynchronous Terminal Access Controlling External Device 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 84: 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 85 Procedure To limit asynchronous terminal access to the menu-driven user interface: 1. Select the Communication Port options. Main Menu Communication Port 2. Set the following configuration options, as appropriate. To . . . Require a login Limit the effective access level to Level-3 or Level-2 NOTE: Troubleshooting , should you be locked out inadvertently.
Page 86: 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. Procedure To control dial-in access: 1.
Page 87: Limiting Telnet Access
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 To limit Telnet access when the session is not on the TS Management Link:...
Page 88: 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 89: Limiting Telnet Or Ftp Access Over The Ts Management Link
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 Telnet and FTP Sessions 2.
Page 90: 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 91: Assigning Snmp Community Names And Access Levels
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 92: 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 93: Creating A Login
Configuring SNMP NMS Security Options more information about SNMP NMS Security configuration options. Creating a Login A login is required if security is enabled.* Up to six login ID/password combinations can be created using ASCII text, and each login must have a specified access level.
Page 94: Modifying A Login
Security and Logins Configuring SNMP NMS Security information about security configuration options. Modifying a Login Logins are modified by deleting the incorrect login and creating a new one. Deleting a Login Procedure To delete a login record: 1. Select Administer Logins. Main Menu 2.
Page 95: Operation And Maintenance
Operation and Maintenance This chapter includes the following: Displaying System Information Viewing LEDs and Control Leads — LED Descriptions — Control Lead Descriptions Device Messages Status Information — System and Test Status Messages Self-Test Results Messages Health and Status Messages Test Status Messages —...
Page 96: Displaying System Information
Operation and Maintenance Displaying System Information Use the Identity screen to view identification information about the FrameSaver unit. This information is useful if you are purchasing additional or replacement units and/or making firmware upgrades. Main Menu View this field . . . System Name System Contact System Location...
Page 97: Viewing Leds And Control Leads
Viewing LEDs and Control Leads The FrameSaver unit’s faceplate includes LEDs ( light-emitting diodes) that provide status on the FrameSaver unit, its network interface, and its user data port. FrameSaver FrameSaver The Display LEDs and Control Leads screen allows you to monitor a remote unit and is useful when troubleshooting control lead problems.
Page 98: 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-1. General Status LEDs Label Table 5-3 for network interface and user data port LED information. Indication Color What It Means Power and Green...
Page 99: Control Lead Descriptions
Table 5-2. Network Interface LED Label Table 5-3. User Data Port LED Label Control Lead Descriptions See Table 5-2, Table 5-3, The LED descriptions and control lead descriptions are the same. In addition to the OK LED for the user data port, additional control leads can be monitored through the Display LEDs and Control Leads screen.
Page 100: 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 Access level is n , Read-only. Already Active Blank Entries Removed...
Page 101 Table 5-5. Device Messages (2 of 5) Message File Transfer Failed – Invalid file (Seen at an FTP terminal.) Invalid Character ( x ) Invalid date: must be mm/dd/yyyy Invalid date and/or time Invalid time: must be hh:mm:ss Invalid – Already Active Invalid Password Invalid Test...
Page 102 Operation and Maintenance Table 5-5. Device Messages (3 of 5) Message Limit of PVC Connections reached Name Must be Unique No Destination Link DLCIs Available No DLCIs available for connection No DLCIs available for connection No DLCIs Available for Mgmt PVC No DLCIs Defined No more DLCIs allowed...
Page 103 Table 5-5. Device Messages (4 of 5) Message No Primary Destination Link DLCIs Available No Security Records to Delete Password Matching Error – Re-enter Password Permission Denied (Seen at an FTP terminal.) Please Wait Resetting Device, Please Wait ... 9664-A2-GB20-00 Operation and Maintenance What It Indicates What To Do...
Page 104 Operation and Maintenance Table 5-5. Device Messages (5 of 5) Message Test Active User Interface Already in Use User Interface Idle Value Out of Range 5-10 What It Indicates What To Do No higher priority health Contact service provider if test and status messages exist, initiated by the network.
Page 105: Status Information
Status Information Status information is useful when monitoring the FrameSaver unit. The following illustration shows the Status menu for the FrameSaver unit. Status Menu Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
Page 106: 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 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 the System and Test Status screen.
Page 107 Health and Status Messages The following table provides Health and Status messages that apply to the FrameSaver unit. Table 5-7. Health and Status Messages (1 of 2) Message Auto-Configuration Active Back-to-Back Mode Active CTS down to Port-1 Device DLCI nnnn Down, frame relay link DTR Down from Port-1 Device Link Down Administratively,...
Page 108 Operation and Maintenance Table 5-7. Health and Status Messages (2 of 2) Message LMI Discovery in Progress, frame relay link LMI Down, frame relay link LOS at Network 1 Network Com Link Down SLV Timeout, DLCI nnnn , frame relay link Two Level-1 Users Accessing Device nnnn indicates a DLCI number of 16 through 1007.
Page 109 Test Status Messages These test messages appear in the right column of the System and Test Status screen. You have the option of allowing the test to continue or aborting the test. See Chapter 6, start and stop them. Table 5-8. Test Status Messages Message DCLB Active, Network 1 DTE External LB Active, Port-1...
Page 110: 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 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 111 Table 5-9. Network LMI-Reported DLCIs Status Field DLCI Status CIR (bps) Appears for 10 seconds only, before the network changes Deleted to Inactive and New to Active. 9664-A2-GB20-00 Operation and Maintenance Status What It Indicates 16 through 1007 Identifies the Local Management Interface-reported DLCI numbers assigned to the selected interface –...
Page 112: Pvc Connection Status
Operation and Maintenance PVC Connection Status PVC connection statuses are selected from the Status menu. Main Menu Only PVC connections with Source DLCIs configured to be Active are shown. PVC Connection Status Screen Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/status/connections Î...
Page 113 Table 5-10. PVC Connection Status (2 of 2) Field EDLCI Status For the circuit to be active, both Source and Destination Statuses must be Active. 9664-A2-GB20-00 Operation and Maintenance Status What It Indicates 0 to 62 For multiplexed DLCIs only. Identifies an individual link/ connection embedded within a DLCI.
Page 114: Network Interface Status
Operation and Maintenance Network Interface Status The network interface status is selected from the Status menu. Main Menu Table 5-11. Network Interface Status (1 of 2) Field Operating Rate (Kbps) Interface State Transmit Signal 5-20 Status Network Interface Status Status What It Indicates The frame relay network’s operating rate as detected by the unit’s...
Page 115 Table 5-11. Network Interface Status (2 of 2) Field Receive Signal 9664-A2-GB20-00 Operation and Maintenance Status What It Indicates Shows the signals being received on the leased line BRI S/T network interface from the attached DSU(NT1). INFO0 No Signal Indication. No signal is present, or a continuous flow of binary ones is being received.
Page 116: Performance Statistics
Operation and Maintenance Performance Statistics Use the Performance Statistics menu to display statistical information for a selected interface. Statistical information is useful when trying to determine the severity and frequency or duration of a condition. Main Menu Physical and link layer statistics (Layers 1 and 2) are collected on the port. The following menu shows the performance statistics that can be selected.
Page 117: Clearing Performance Statistics
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 118: 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 They only appear for the network interface and only if DLCIs are multiplexed. Table 5-12. Service Level Verification Performance Statistics (1 of 2) Statistic Far End Circuit Far End IP Addr...
Page 119 Table 5-12. Service Level Verification Performance Statistics (2 of 2) Statistic Inbound Dropped Characters Above CIR Within CIR Between CIR&EIR Above EIR Latest RdTrip Latency Avg RdTrip Latency Max RdTrip Latency 9664-A2-GB20-00 Operation and Maintenance What It Indicates Total number of bytes transmitted by the far-end device that were dropped in transit.
Page 120: 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 121 Table 5-13. DLCI Performance Statistics (2 of 2) Statistic With BECN Set Total Rx Frames/ Rx Octets Within CIR Between CIR&EIR Above EIR With DE Set With BECN Set With FECN Set 9664-A2-GB20-00 Operation and Maintenance What It Indicates The number of frames and octets sent on the selected DLCI of the frame relay link with backward explicit congestion notifications.
Page 122: 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 All counts continue to increment until the maximum value is reached (2 then the count starts over. The NextLink and PrevLink function keys only appear when multiple frame relay links have been configured.
Page 123 Table 5-14. Frame Relay Performance Statistics (2 of 3) Statistic Frame Relay Errors (cont’d) Short Rx Frames Long Rx Frames Invalid DLCI Unknown DLCI Unknown Error Frame Relay LMI LMI Protocol Status Msg Received Total LMI Errors Number of Inactives 9664-A2-GB20-00 Operation and Maintenance What It Indicates...
Page 124 Operation and Maintenance Table 5-14. Frame Relay Performance Statistics (3 of 3) Statistic Frame Relay HDLC Errors Rx Total Errors Rx Total Discards Rx Overruns Rx Non-Octet Frames Rx CRC Errors Tx Total Errors Tx Total Discards Tx Underruns 5-30 What It Indicates The number of receiver errors on the interface.
Page 125: Ftp File Transfers
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 126 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 Security and Logins ), you are prompted to enter them.
Page 127: Upgrading System Software
Upgrading System Software If you need to upgrade the FrameSaver unit’s program code, you must transfer the upgrade of the nam.ocd file in the system memory directory using the put command. NOTE: Upgrades can be performed through the network using a Management PVC, or through the COM port if Port Use is set to Net Link (see Table 3-15, Communication Port Procedure...
Page 128: 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 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 129: Transferring Collected Data
Transferring Collected Data SLV user history statistics and LMI packet capture data can be uploaded to an NMS or a Network Associates Sniffer using FTP, which is faster than other methods. The rate at which the data file is transferred is the rate set by the FTP Max Receive Rate (Kbps) option (see Table 3-12, Options in Chapter 3, Configuration) .
Page 130 Operation and Maintenance This page intentionally left blank. 5-36 March 2000 9664-A2-GB20-00...
Page 131: 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 132: Problem Indicators
Troubleshooting Physical Tests — DTE Loopback IP Ping Test Lamp Test Problem Indicators The unit provides a number of indicators to alert you to possible problems: Indicators . . . LEDs Health and Status Performance statistics Alarm conditions that will generate an SNMP trap SNMP traps See .
Page 133: Resetting The Unit And Restoring Communication
Resetting the Unit and Restoring Communication You can reset the unit in one of four ways: Reset it from the Control menu. Cycle the power. Reset the configuration options for the COM port, or reload the factory default settings. Set the appropriate MIB object from NMS (see your NMS documentation). The unit performs a self-test when it is reset.
Page 134: 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 135: Troubleshooting Management Link Feature
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 136: 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 LMI Trace Log Example Î...
Page 137: Alarms
Alarms The following table describes the alarm conditions that will generate an SNMP trap for a physical interface, and the frame relay LMIs and DLCIs. These alarm conditions also generate Health and Status messages seen on the System and Test Status screen. Main Menu Table 6-1.
Page 138 Troubleshooting Table 6-1. Alarm Conditions (2 of 3) Alarm Condition LMI Down, frame relay link LOS at Network 1 frame relay link is one of the following: – Net1-FR1. The frame relay link specified for the network data port, Network 1. –...
Page 139 Table 6-1. Alarm Conditions (3 of 3) Alarm Condition Network Com Link Down Self-Test Failure SLV Timeout, DLCI nnnn , frame relay link nnnn indicates a DLCI number of 16 through 1007. frame relay link is one of the following: –...
Page 140: 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 Symptom No power, or the LEDs are not lit.
Page 141: Frame Relay Pvc Problems
Frame Relay PVC Problems Table 6-3. Frame Relay PVC Problems Symptom No receipt or transmission of data. Losing Data. Out of Sync message. 9664-A2-GB20-00 Possible Cause Solutions Cross Connection of the Verify the PVC connections DLCIs are configured and DLCIs by checking the incorrectly.
Page 142: Tests Available
Troubleshooting Tests Available The following tests are available to a FrameSaver SLV 9664. Test Menu Example Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
Page 143: Starting And Stopping A Test
Starting and Stopping a Test Use this procedure to start, monitor, or abort specific tests. To abort all active tests on all interfaces, see When the status of a test is . . . Inactive Active Start or stop an individual test using the same procedure. Procedure To start and stop a test: 1.
Page 144: 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 145: Network Or Port (Internal) Pvc Loopback
Network or Port (Internal) PVC Loopback The PVC Loopback loops frames back to the selected interface on a per-PVC basis. This test logically (not physically) loops back frames received from another FrameSaver device through the selected frame relay PVC to the same device. Main Menu Network PVC Loopback Main Menu...
Page 146: 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 Monitor Pattern The current number of sequence and data errors are shown under the Result column when the FrameSaver unit is in sync.
Page 147: Physical Tests
Physical Tests Physical Tests can only be commanded for the user data port. DTE Loopback The DTE external Loopback (DTLB) test loops the received signal on a user data port back to the DTE. Use this test for isolating problems on the user data port. An attached device or test equipment must generate data to be looped back.
Page 148: Ip Ping Test
Troubleshooting IP Ping Test An IP Ping test can be run to test connectivity between the FrameSaver unit and any FrameSaver device, router, or NMS to which it has a route. Times when you might want to run an IP Ping test are: To test connectivity between the FrameSaver unit and any FrameSaver device in the network to verify that the path is operational.
Page 149: Lamp Test
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 150 Troubleshooting This page intentionally left blank. 6-20 March 2000 9664-A2-GB20-00...
Page 151: 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 152: 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 153: 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 154: 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 155: Configuring Netscout Manager Plus
Configuring NetScout Manager Plus For the NetScout Manager Plus main window to appear, make sure your environment is set up exactly as specified in your NetScout Readme file. You need to: Copy the OpenLane directory to a user directory. Add frame relay agents to the NetScout Manager. Configure agent properties.
Page 156: 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 157: Verifying Domains And Groups
Verifying Domains and Groups Procedure 1. From the NetScout Manager Plus main window, with the FrameRelay and Admin radio buttons still selected, click on the Config Manager icon to open the Configuration Manager main window. 2. Verify that only FrameSaver SLV-supported domains appear listed in the Domain column.
Page 158: 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 159 3. To add a FrameSaver SLV-supported domain or correct property settings, select the Edit... button (to the right of the Domain section of the Property Editor window). The Edit Domain window opens. 4. Click on the domain from the Domains list and configure the following: Property Groups Stats (S) Logging...
Page 160: 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) — Tx CIR Utilization (SLVTxCIRUtil) —...
Page 161: Editing Alarms
Editing Alarms Procedure 1. From the NetScout Manager Plus main window, with the FrameRelay and Admin radio buttons still selected, click on the Config Manager icon to open the Configuration Manager main window. 2. Select the Custom radio button from the Properties File area (in the upper right of the window), then Property...
Page 162 Setting Up NetScout Manager Plus for FrameSaver Devices 4. Edit any trap defaults that may be required. See 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 163: Adding Slv Alarms Manually
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 164 8-12 Select or Enter . . . User Defined DLCI number for trap being assigned PARADYNE Trap variable to be configured The ifIndex for the frame relay logical interface is 1 DLCI number (same as DLCI above) Absolute or Delta radio button Rising, Falling, or Both radio button Value that will trigger a trap.
Page 165: Creating History Files
Creating History Files Up to 14 additional user history tables can be created in the FrameSaver unit for each interface. An interface is a specific DLCI or the entire frame relay interface. A table must be created for each DLCI or frame relay link to be monitored. Additional user history tables are created using the command-line prompt in NetScout Manager Plus to load a file that contains the OIDs (Object IDs) to be monitored into the unit.
Page 166 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 167: Installing The User-Defined History Files
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 168: 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 169 5. Select History List from the View menu. The History List window opens. The newly defined user history variables should appear on this list. 6. Highlight the desired set of user history variables, and select the OK button. Data is gathered based upon the configured user history variables. This may take some time, so please be patient.
Page 170: 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 Refer to Launching User History and Understanding Custom History Display in Using Custom History of the NetScout Manager Plus User Guide for additional...
Page 171 Procedure 1. Select the Traffic radio button to monitor the newly added agent, or one of its DLCIs. 2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI list box (under the agent list box). 3.
Page 172: 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 173: 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 get this report, you need Network Health R4.01 or higher.
Page 174: 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 175: Discovering Framesaver Elements
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 176: 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 177: Grouping Elements For Reports
Grouping Elements for Reports Once the discovery process is completed and required changes are made, the newly discovered elements (DLCIs) should be organized into a group for Health reporting. Grouping makes for easier monitoring and management of similar node types (e.g., all SLV elements). Once grouped, you can then run reports on all DLCIs in the network, as well as reports on individual DLCIs.
Page 178: 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 179: About Trend Reports
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 180 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 181 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 182 Setting Up Network Health for FrameSaver Devices This page intentionally left blank. 9-10 March 2000 9664-A2-GB20-00...
Page 183: Menu Hierarchy
Menu Hierarchy Menus The following is a graphical representation of the FrameSaver SLV unit’s menu organization. 9664-A2-GB20-00 March 2000...
Page 184 Menu Hierarchy Menu Hierarchy System and Network LMI Test Status Reported DLCIs • Self-Test Results • Health and • DLCI Status • Status • Test Status • CIR (bps) Status System and Test Status LMI Reported DLCIs PVC Connection Status Network Interface Status Performance Statistics Display LEDs and...
Page 185 System Frame Relay and LMI • Service Level • Verification • General Auto-Configuration Frame Relay • Discovery Mode Automatic Circuit Removal • System Information • Device Name • System Name, Location, Contact • Date • Time 9664-A2-GB20-00 Configuration Edit/Display System Network Data Ports PVC Connections...
Page 186 Menu Hierarchy This page intentionally left blank. March 2000 9664-A2-GB20-00...
Page 187: Snmp 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 188: 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 189: System Group (Mib-2
The following is the system description (sysDescr [system 1] ) for the NMS subsystem in the FrameSaver 9664 unit: PARADYNE LL S/T FrameSaver SLV; Model: 9664; S/W Release: (MM.mm.bb [MM=Major.mm=minor.bb=build] format) ; NAM CCA number: (hardware version in hhhh-hhh format) ; Serial number: sssssss FrameSaver Unit’s sysObjectID (system 2)
Page 190: 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 191: Netscout Indexes To The Interface Table (Iftable
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 Frame Relay Logical Layer Frame Relay 1 Network RMON Logical Layer RMON Frame...
Page 192: 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 193: Trap: Warmstart
Trap: warmStart This trap indicates that the FrameSaver unit has been reset and has stabilized. Table B-3. warmStart Trap Trap warmStart Trap: authenticationFailure This trap indicates that access to the FrameSaver unit was unsuccessful due to lack of authentication. Table B-4. authenticationFailure Trap Trap authenticationFailure 9664-A2-GB20-00...
Page 194: 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 ISDN S/T interface – Physical sublayer interfaces Synchronous data port – Physical sublayer interfaces Frame relay logical link layer interfaces Table B-5.
Page 195 Table B-6. linkUp and linkDown Variable-Bindings(1 of 2) Interface Physical Sublayer Network ISDN S/T (Supported by the media-specific RS232-like MIB.) User Synchronous Data Port (Supported by the media-specific RS232-like MIB.) This alarm condition only generates a linkUp/ linkDown trap if the DTE supports this lead state.
Page 196 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-6. linkUp and linkDown Variable-Bindings(2 of 2) Interface Logical Link Sublayer Frame Relay (Supported by the media-specific Frame Relay Services MIB.) If the LMI Protocol is not configured, a linkUp/ linkDown trap is based solely upon whether the interface is enabled or disabled.
Page 197: Traps: Enterprise-Specific
Traps: enterprise-Specific These traps indicate that an enterprise-specific event has occurred. Supported enterprise-specific traps are listed below. Table B-7. enterprise-Specific Traps and Variable-Bindings (1 of 2) Trap enterpriseCIR- Change(15) enterpriseConfig- Change(6) enterpriseDLCI- delete(17) enterpriseDLCI- Down(11) enterpriseDLCIUp(12) 9664-A2-GB20-00 SNMP MIBs and Traps, and RMON Alarm Defaults Variable-Bindings Possible Cause devFrExtDlciIfIndex...
Page 198 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-7. enterprise-Specific Traps and Variable-Bindings (2 of 2) Trap enterpriseMissedSLV- Down(16) enterpriseMissedSLV- Up(116) enterpriseRMON- ResetToDefault(13) enterpriseSelfTest- Fail(2) enterpriseTest- Start(5) enterpriseTest- Stop(105) B-12 Variable-Bindings Possible Cause devFrExtDlciIfIndex SLV Timeout Error Event (devFrExt.mib) Threshold has been exceeded.
Page 199: Traps: Rmon-Specific
Traps: RMON-Specific Two traps are defined to support the Alarm and Events Groups of RMON. See RMON Alarm and Event Defaults RMON-specific traps. Table B-8. RMON-Specific Traps and Variable-Bindings Trap risingAlarm fallingAlarm 9664-A2-GB20-00 SNMP MIBs and Traps, and RMON Alarm Defaults for the default values that will generate Variable-Bindings Possible Cause...
Page 200: 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 work, and Rising Event Operation If a rising threshold is crossed during the interval shown in a table (e.g., frames...
Page 201: Network Isdn S/T Physical Interface Alarm Defaults
Network ISDN S/T Physical Interface Alarm Defaults These alarms only apply to the FrameSaver unit’s network ISDN S/T interface. They are created during RMON initialization and put into the Paradyne-defined alarm area. Table B-9. Network ISDN S/T Physical Interface Alarm Defaults...
Page 202: 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) Sample Item MIB/Tag/OID...
Page 203 Table B-10. Frame Relay Link Alarm Defaults (2 of 2) Sample Item Type MIB/Tag/OID Rx Overruns MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkRxOverruns OID: .1.3.6.1.4.1.1795.2.24.2. 6.9.4.7.1.28.I MIB: pdn_FrExt.mib (E) Tx Underruns Tag: devFrExtLinkTx- Underruns OID: .1.3.6.1.4.1.1795.2.24.2. 6.9.4.7.1.29.I Rx Non-octet Aligns MIB: pdn_FrExt.mib (E) Tag: devFrExtLinkRx- NonOctet OID: .1.3.6.1.4.1.1795.2.24.2.
Page 204: 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 Sample Item...
Page 205: 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 FrameSaver Devices .
Page 206 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-12. Static DLCI Alarm Defaults – NetScout Area (2 of 2) Sample Item Type MIB/Tag/OID Tx CIR Utilization MIB: FR DTE MIB (RFC 2115) Tag: frCircuitSentOctets OID: .1.3.6.1.2.1.10.32.2.1. 7.I.D D = Delta. Indicates that the calculated difference between the current value and the previous value is contained in the MIB.
Page 207: 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 208 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (1 of 4) Object ID (OID) .1.3.6.1.2.1.2.2.1..1.3.6.1.2.1.2.2.1.5.I .1.3.6.1.2.1.2.2.1.10.I .1.3.6.1.2.1.2.2.1.16.I .1.3.6.1.2.1.2.10.32.2.1..1.3.6.1.2.1.10.32.2.1.4.I.D .1.3.6.1.2.1.10.32.2.1.5.I.D .1.3.6.1.2.1.10.32.2.1.6.I.D .1.3.6.1.2.1.10.32.2.1.7.I.D .1.3.6.1.2.1.10.32.2.1.8.I.D .1.3.6.1.2.1.10.32.2.1.9.I.D .1.3.6.1.2.1.16.12.2.1..1.3.6.1.2.1.16.12.2.1.2.P I = Interface ID of the frame relay link D = DLCI number N = Additional numeric index used by tables, like frame or burst size H = Host control index...
Page 209 Table B-14. History OID Cross-Reference (2 of 4) Object ID (OID) .1.3.6.1.4.1.1795.2.24.2..1.3.6.1.4.1.1795.2.24.2.6.12.1.1.1.4.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.16.I .1.3.6.1.4.1.1795.2.24.2.13.1.2.1.4.H.T.N .1.3.6.1.4.1.1795.2.24.2.13.1.2.1.6.H.T.N .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.3.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.7.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.8.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.17.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.18.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.20.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4 .1.1.22.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.37.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.39.I.D I = Interface ID of the frame relay link D = DLCI number N = Additional numeric index used by tables, like frame or burst size H = Host control index...
Page 210 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-14. History OID Cross-Reference (3 of 4) Object ID (OID) .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 .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.43.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.45.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4 .1.1.55.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.57.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.59.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.61.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.63.I .D .1.3.6.1.4.1.1795.2.24.2.6.9.4.2.1.2.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.5.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.6.I. D .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.8.I.D I = Interface ID of the frame relay link D = DLCI number...
Page 211 Table B-14. History OID Cross-Reference (4 of 4) Object ID (OID) .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1..1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.2.I.D.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.3.I.D.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.5.2.1.4.I.D.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1..1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.2.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.17.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.19.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.20.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.32.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.10.3.1..1.3.6.1.4.1.1795.2.24.2.6.9.4.10.3.1.2.I.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.10.3.1.3.I.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.10.3.1.4.I.N I = Interface ID of the frame relay link D = DLCI number N = Additional numeric index used by tables, like frame or burst size H = Host control index...
Page 212 SNMP MIBs and Traps, and RMON Alarm Defaults Table B-15. Alarm OID Cross-Reference (1 of 2) Object ID (OID) .1.3.6.1.2.1.10.32.2.1..1.3.6.1.2.1.10.32.2.1.4.I.D .1.3.6.1.2.1.10.32.2.1.5.I.D .1.3.6.1.2.1.10.32.2.1.6.I.D .1.3.6.1.2.1.10.32.2.1.7.I.D .1.3.6.1.2.1.10.32.2.1.7.I.D .1.3.6.1.2.1.10.32.2.1.8.I.D .1.3.6.1.2.1.10.32.2.1.9.I.D .1.3.6.1.4.1.1795.2.24.2..1.3.6.1.4.1.1795.2.24.2.6.12.1.1.1.4.I .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.17.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.20.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.1.1.23.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.2.1.6.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.2.1.2.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.5.I.D B-26...
Page 213 Table B-15. Alarm OID Cross-Reference (2 of 2) Object ID (OID) .1.3.6.1.4.1.1795.2.24.2.6.9.4..1.3.6.1.4.1.1795.2.24.2.6.9.4.3.1.7.I.D .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.2.I.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.4.2.1.3.I.N .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.6.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.7.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.11.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.14.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.15.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.16.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.17.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.18.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.19.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.20.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.28.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.29.I .1.3.6.1.4.1.1795.2.24.2.6.9.4.7.1.32.I 9664-A2-GB20-00 SNMP MIBs and Traps, and RMON Alarm Defaults Item MIB/Tag MIB: pdn_FrExt.mib (E) Current Latency...
Page 214 SNMP MIBs and Traps, and RMON Alarm Defaults This page intentionally left blank. B-28 March 2000 9664-A2-GB20-00...
Page 215: Connectors, Cables, And Pin Assignments
Connectors, Cables, and Pin Assignments This appendix shows the FrameSaver unit’s rear panel, and provides pin assignments for the connectors/interfaces and cables. NOTE: In the pin assignment tables of this appendix, if the pin number is not shown, it is not being used. Rear Panel The following illustration shows the rear panel of the FrameSaver unit.
Page 216: Com Port Connector
Connectors, Cables, and Pin Assignments COM Port Connector The following table shows the signals and pin assignments for the DB25 communication port connector. Signal Shield Transmit Data ( TXD ) Received Data ( RXD ) Request to Send ( RTS ) Carrier Detect ( CD ) Signal Ground ( SG ) Data Terminal Ready ( DTR )
Page 217: Lan Adapter Converter And Cable
LAN Adapter Converter and Cable The following shows the pin assignments for the: DB25 plug-to-modular jack converter between the COM port and the 8-conductor LAN Adapter cable (Feature No. 3100-F1-920) Custom 8-conductor cable (with modular plugs on both ends) between the converter and the LAN Adapter (Feature No.
Page 218: Standard Eia-232 Crossover Cable
Connectors, Cables, and Pin Assignments Standard EIA-232 Crossover Cable A standard EIA-232 crossover cable can be used to connect the COM port to an external modem. This is an EIA-232 plug-to EIA-232 plug (DB25-to-DB25) cable. The external modem must be configured so it is compatible with the FrameSaver unit.
Page 219 Procedure To configure an external modem: 1. Disconnect the asynchronous terminal from the standard cable. See page C-4 2. Reconnect the crossover cable to the external modem. 3. Enable auto-answer on the modem, and configure it to use the following LSD, DSR, CTS, RTS, and DTR control leads.
Page 220: Network Connector
Connectors, Cables, and Pin Assignments Network Connector The network connection is through the ISDN BRI leased-line interface/connector, which is an 8-position unkeyed modular jack. The following table shows the pin assignments for the BRI network port and the purpose of each. Function BRI Transmit Ring BRI Receive Ring...
Page 221: User Data Port Connector
User Data Port Connector The following table provides the pin assignments for the EIA-530A connector to a DTE. Signal Shield Transmit Data ( TXD ) Received Data ( RXD ) Request to Send ( RTS ) Clear to Send ( CTS ) Data Set (or DCE ) Ready ( DSR ) Signal Ground/Common ( SG )
Page 222: Dte Adapter Cable (Feature No. 3100-F1-571
Connectors, Cables, and Pin Assignments X.21 DTE Adapter Cable (Feature No. 3100-F1-571) This adapter is used to connect the user data port to a DTE with an X.21 cable. It is a 25-pin EIA-530A-to-15-pin X.21 (DB25-to-X.21) adapter cable. The following table provides the pin assignments for the DB25-to-X.21 adapter cable.
Page 223: Dte Adapter (Feature No. 3100-F1-570
Connectors, Cables, and Pin Assignments V.35 DTE Adapter (Feature No. 3100-F1-570) This adapter is used to connect the user data port to a DTE with an V.35 cable. It is a 25-pin EIA-530A-to-34-position V.35 (DB25-to-V.35) adapter. 99-16294 9664-A2-GB20-00 March 2000...
Page 224 Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-V.35 adapter. Signal Shield Transmit Data ( TXD ) Received Data ( RXD ) Transmit Signal Element Timing ( TXC ) — DCE Source Received Signal Element Timing ( RXC ) —...
Page 225: Straight-Through Cable (Feature No. 9008-F1-523
Connectors, Cables, and Pin Assignments EIA-530 Straight-through Cable (Feature No. 9008-F1-523) A standard straight-through cable is used to connect the user data port to a DTE when the Port Type is E530 (EIA-530A). It is a 25-pin EIA-530A-to-25-pin EIA-530A (DB25-to-DB25) cable. 99-16304 9664-A2-GB20-00 March 2000...
Page 226 Connectors, Cables, and Pin Assignments The following table provides the pin assignments for the DB25-to-DB25 straight-through cable. Signal Shield Transmit Data ( TXD ) Received Data ( RXD ) Request to Send ( RTS ) Clear to Send ( CTS ) Data Set (or DCE ) Ready ( DSR ) Data Terminal (or DTE ) Ready ( DTR )
Page 227: Technical Specifications
Technical Specifications Table D-1. FrameSaver SLV 9664 Unit Technical Specifications (1 of 2) Specification Approvals EMC (Class A) Network Safety Physical Environment Operating temperature Storage temperature Relative humidity Shock and vibration Weight Physical Dimensions Height Width Depth Power Input Output...
Page 228 Technical Specifications Table D-1. FrameSaver SLV 9664 Unit Technical Specifications (2 of 2) Specification COM Port Data rates Network Interface Service supported Data rates User Data Port Data rates Criteria DB25 connector 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.2 kbps 8-position unkeyed modular jack (per ISO 8877) ISDN Leased Line BRI S/T (ITU-T I.430)
Page 229: Equipment List
NetScout WebCast – For UNIX or Windows NT Optional Features Wall Mounting Kit for 1-Slot Housing Shelf Mounting Kit for 1-Slot Housings The country code is shown as nnn . Contact your Paradyne sales office for the correct number. 9664-A2-GB20-00 cables you can order.
Page 230: Cables
Equipment List Cables This table lists cables you can order. Description Leased Line ISDN BRI Cable, 8-position unkeyed modular plug at each end (20 feet/6.1 meters) V.35 DTE Adapter, EIA-530A-to-V.35 X.21 DTE Adapter Cable, EIA-530A-to-X.21 (1 foot/.3 meters) COM Port-to-Terminal Cable, 8-pin modular -to-DB25 (14 feet /4.3 meters) COM Port-to-LAN Adapter Cable...
Page 231: Index
Index Numbers 55 hexadecimal, test pattern, 6-16 aborting tests, 6-13 Access Dial-In, 3-53 Name, 3-39 Type, 3-43 Access Level, 4-10, 4-11 assigning, 4-9 Port, 3-50 security, 2-1 Session, 3-41 adding, SLV units to network, 9-3 Alarm, 6-7 (Fail), 5-4 adding manually, 8-11 conditions, 6-2, 6-7 editing, 8-9 LED is lit, 6-10...
Page 232 Index Committed Burst Size Bc (Bits), 3-29 Committed Information Rate (CIR), 3-29 Communication, Port, user interface options, 3-49 Community Name, 3-39 assigning, 4-9 Concord Network Health, compatibility, 9-1 Concord’s Network Health, 1-1 Configuration Auto, Active, 5-13 displaying and changing options, 3-5 menu, 3-3 menu/branch, 2-4 option areas, 3-4...
Page 233 Directory, Alternate Dial-Out, 3-48 disabling, SNMP access, 4-8 Discard Eligible (DE), 3-37 Disconnect, Time (Minutes), 3-41, 3-51 discovering elements/DLCIs, 9-3 Discovery frame relay (FR), 3-11 Frame Relay Mode, saving a mode change, 3-13 displaying configuration options, 3-5 identity information, 5-2 LEDs and control leads, 5-3 DLCI, 3-38 Destination, 3-32...
Page 234 Index frames, 3-37 FTP, 1-4, 5-31 file transfers, 5-31 initiating a session, 5-31 limiting access, 4-4, 4-6 Login Required, 3-42 Max Receive Rate (kbps), 3-42 Session, 4-6 function keys, 2-5, 2-7 General LEDs, 5-4 options, 3-22 SNMP management, options, 3-39 Traps, 3-45 generating reports, 9-6 glossary, viii...
Page 235 and PVC availability, 1-3 Behavior, 3-18 Clearing Event (N3), 3-19, 3-27 configuring frame relay and, 3-18 Down, 5-14, 6-8 Error Event (N2), 3-18, 3-27 frame relay statistics, 5-29 Heartbeat (T1), 3-19, 3-27 Inbound Heartbeat (T2), 3-19, 3-28 N4 Measurement Period (T3), 3-19, 3-28 packet utility, 6-5 Parameters, 3-27 pass-through, 3-18...
Page 236 Index navigating the screens, 2-6 Net Link, Port Use, 3-49 NetOnly, 3-11 NetScout Manager Plus, NMS support, 1-5 NMS support, 1-1 Network Com Link Down, 5-14, 6-9 DLCI records, options, 3-28 Health (Concord) reports, 9-1 interface, C-6 LED, 5-5 latency, 1-3 physical interface options, 3-23 PVC Loopback, 6-15 reference time, 1-3...
Page 237 Protocol address resolution, 1-3 Link, 3-52 LMI, 3-26 Point-to-Point (PPP), 3-52 Routing Information (RIP), 3-38, 3-52 Serial Line, IP (SLIP), 3-52 Simple Network Management (SNMP), 3-39 availability, 1-3 connection status, 5-18 connections, 3-31 total number, 1-3 Management, 3-36 total number dedicated, 1-3 name, 3-34, 3-35, 3-45 Network Loopback, 6-15 tests, 6-14...
Page 238 Index setting up auto-configuration, 3-10 external modem, 3-9 local management, 3-14 service provider connectivity, 3-15 SNMP trap managers, 3-43 so router can receive RIP, 3-15 SLA, 1-2, 1-4 SLIP, 3-52 SLM, vii, 1-1 OpenLane, 7-1 (service level verifier), 1-1 configuring, 3-20 Delivery Ratio, 3-20 DLCI Down on Timeout, 3-20 Packet Size, 3-21...
Page 239 T1, LMI Heartbeat, 3-19, 3-27 T2, LMI Inbound Heartbeat, 3-19, 3-28 T3, LMI N4 Measurement Period, 3-19, 3-28 Tab key, 2-6 Tc, 3-29 TCP, 5-31 technical specifications, D-1 Telnet limiting access, 4-4, 4-5 Session, 4-5 user interface options, 3-40 Terminal, Port Use, 3-49 Test menu/branch, 2-4 Mode, 5-4...
Page 240 Index V.54 Loopback, 3-23, 5-15 Value Out of Range message, 3-28, 3-29 variable-bindings, B-9, B-13 VCI, 1-4 viewing, packet capture results, 6-6 virtual path or channel identifier, 1-4 VPI, 1-4 IN-10 warmStart events, General Traps, 3-45 trap, B-7 warranty, A Web-site access to documentation, ix glossary, viii...

Paradyne FrameSaver SLV 9664 User Manual

About this Guide

1 About the Framesaver SLV 9664

2 User Interface and Basic Operation

3 Configuration

4 Security and Logins

5 Operation and Maintenance

6 Troubleshooting

7 Setting up Openlane for Framesaver Devices

8 Setting up Netscout Manager Plus for Framesaver Devices

9 Setting up Network Health for Framesaver Devices

Menu Hierarchy

SNMP Mibs and Traps, and RMON Alarm Defaults

Connectors, Cables, and Pin Assignments

Technical Specifications

Equipment List

Index

Quick Links

Troubleshooting

Related Manuals for Paradyne FrameSaver SLV 9664

Summary of Contents for Paradyne FrameSaver SLV 9664