Page 1 FrameSaver SLV 9124 TECHNICAL REFERENCE Document No. 9124-A2-GH30-00 June 1999 PRELIMINARY DRAFT...
Page 2 Paradyne worldwide office locations, use one of the following methods: H Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty there. Select Service & Support → Warranty Registration.) H 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 H Purpose and Intended Audience ........H Document Organization .
Page 4 Contents Typical Applications H SLV Frame Relay Monitoring ........H Access to the Frame Relay Network .
Page 5 Contents Using the OpenLane NMS H The OpenLane Advantage ........Using an OpenLane NMS Application .
Page 6 Contents Concord’s Network Health H Installation and Setup of Network Health ......Discovering FrameSaver Elements .
Page 7 Contents H Setting Up for Back-to-Back Operation ......8-21 Changing Operating Mode .
Page 8 Contents 10 Operation and Maintenance H Displaying System Information ........10-2 H Viewing LEDs and Control Leads .
Page 9 Contents H PVC Tests ........... . . 11-18 PVC Loopback .
Page 10 ....C-16 DLCI Alarm Defaults – Paradyne Area ......
Page 11: About This Guide
About This Guide Purpose and Intended Audience This document contains information needed to properly set up, configure, and verify operation of the FrameSaver 9124, a T1 Frame Relay Service Level Verifier (SLV) unit. It is intended for system designers, engineers, administrators, and operators.
Page 12 Technical Specifications. Appendix F 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...
Page 13: H Conventions Used
About This Guide Conventions Used Convention Used When Used Italic To indicate variable information (e.g., DLCI nnnn) or model-specific information (e.g., 9124 only ). Menu sequence: To provide an abbreviated method for indicating the selections to be made from a menu or selections from within a menu before performing a procedural step.
Page 14: H Product-Related Documents
09-10070-001 Network Health Reports Guide 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 request 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 15: About The Framesaver Slv
1-7. — NetScout Probes on page 1-7. Overview The Paradyne r Service Level Management (SLM) Solution consists of: FrameSaver SLV 9124 units OpenLaner NMS applications for Unix or Windows — OpenLane 5 and/or — OpenLane DCE Manager NetScout Manager Plus application...
Page 16 About the FrameSaver SLV Features Summary The FrameSaver SLV product is a single, flexible, and standards-based frame relay monitoring solution that 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 17 NMS IP addresses and access type. Maximum PVCs, EDLCIs, and Management PVCs. The number of remote sites and PVCs that can be created for each FrameSaver SLV 9124 is summarized in the following table. Central Site...
Page 18 Protocol) manager or network device via the COM port or modem port. SNMP Management Capability. Provides network management via an external Simple Network Management Protocol management system using industry-standard and Paradyne-specific MIB (Management Information Base) objects. IP Management Connectivity. Supports management connectivity within an IP (Internet Protocol) network for up to 300 IP routes to provide IP routing for SNMP, Telnet, and FTP messages without requiring direct connections.
Page 19: Openlane 5 Service Level Management Solution
OpenLane 5 DCE Manager OpenLane 5 Service Level Management Solution The FrameSaver 9126 and 9128 units are managed by Paradyne’s OpenLane 5 NMS service level management solution, an advanced, standards-based performance monitoring and management application that provides unique network control and reporting mechanisms.
Page 20: Openlane Dce Manager
About the FrameSaver SLV Diagnostic Troubleshooting. Provides an extremely easy-to-use tool for performing tests, with loopback and PVC testing for FrameSaver devices, to maximize network availability, minimizing downtime. Automatic Topology Maps. Provides automatic device discovery and end-to-end PVC discovery and configuration to eliminate or minimize manual configuration and operator intervention.
Page 21: Netscout Probes
About the FrameSaver SLV NetScout Manager Plus This application supports FrameSaver SLV units and NetScout Probes with complete LAN and WAN traffic analysis and monitoring functions. NetScout Manager Plus provides the following features for FrameSaver SLV devices: Configurable thresholds for RMON 1 alarms and events. Performance monitoring using collected RMON 2 data.
Page 22 About the FrameSaver SLV This page intentionally left blank. June 1999 - Preliminary 9124-A2-GH30-00...
Page 23: Management Control
Management Control This chapter contains customer end user and service provider management overviews, followed by the steps needed to provide local and remote management connectivity to the FrameSaver unit. You need to select and configure: A method of local management connectivity for FrameSaver units. A method for end-to-end management connectivity across the network.
Page 24 Management Control Customer End User Management Overview The optimal method for managing an end-user network is shown in the example below. Using this method saves PVC charges because management data is multiplexed with customer data using a single PVC. By accessing the remote units in-band, the remote units are not router-dependent, so trouble isolation is easier when there are LAN outages.
Page 25 Management Control Service Provider Management Overview In the service provider example below, the service provider’s management data is multiplexed with the customer data using EDLCIs traveling between the customer’s central site and the customer branches. A dedicated DLCI is configured from the customer’s central site to the service provider’s network control center, so the customer’s entire network can be managed from the service provider’s network operation/control center using a single DLCI.
Page 26: Using The Ts Management Link Feature
Management Control Using the TS Management Link Feature Using the TS (troubleshooting) Management Link feature, a service provider can specify a management link on the FrameSaver unit’s network interface so he has the ability to troubleshoot device problems. Typically, this link is configured on an as needed basis.
Page 27 Management Control Managing the FrameSaver Unit Local management is accomplished through the following methods: DTE port configured with a frame relay management PVC, with the router providing RFC 1490 or Cisco encapsulation of the IP traffic. COM port configured as a terminal for access to the menu-driven async user interface using a VT-100 async terminal or compatible terminal or PC.
Page 28: Creating A Management Dlci Between The Router And Unit Via The Dte Port
Management Control Creating a Management DLCI Between the Router and Unit Via the DTE Port The following configuration shows the management connection using an RFC 1490-compliant or Cisco frame relay IP router connected to the FrameSaver unit’s user data port. As shown below, in-band management is accomplished through the dedicated PVC between the frame relay router or FRAD and the FrameSaver unit.
Page 29: Creating A Separate Management Link Via The Com Port
Management Control Creating a Separate Management Link Via the COM Port A dedicated PVC can be configured to carry customer data over the DTE port, while management data is carried over the COM port. The illustration below shows a management link connected to the COM port for local access to a non-RFC 1490 router.
Page 30: Management Control Using Pvc Multiplexing (Edlci)
Management Control Configuring End-to-End Management Control End-to-end management control methods are typically used for accessing remote site units that are not colocated with the NMS. When managing the FrameSaver unit remotely, you can establish a management link across the network in one of three ways.
Page 31: Management Control Using A Dedicated Dlci
Management Control Management Control Using a Dedicated DLCI Management control through a dedicated DLCI is typically used by service providers to provide a single point of access (i.e., a standard, nonmultiplexed DLCI), usually to the customer’s central site unit, to manage the customer’s network.
Page 32: Transparent Remote Management Control Using Rfc 1490 Routers
Management Control Transparent Remote Management Control Using RFC 1490 Routers FrameSaver unit A can be managed locally via in-band management channels using a frame relay PVC that is configured on its DTE port. When managing the FrameSaver unit B remotely, FrameSaver unit A does not route IP traffic to FrameSaver unit B.
Page 33: Typical Applications
Typical Applications This chapter includes the following information: SLV Frame Relay Monitoring on page 3-2. Access to the Frame Relay Network on page 3-5. Multinational FrameSaver Application on page 3-6. Mixing FrameSaver Units in Applications on page 3-7. — Using All 9624 FrameSaver Units at Remote Sites on page 3-8.
Page 34 Typical remote monitoring (RMON) applications include: FrameSaver SLV units with RMON capability at the central and remote sites using FrameSaver SLV 9124 and/or 9624 units, or Full NetScout RMON probes at the central sites and using FrameSaver 9124 units at regional and remote sites.
Page 35 SLV data. This is shown in the example below. Frame Remote SLV Reports Relay Sites Central Web Server Router Site Paradyne FrameSaver Frame OpenLane 9126 Relay and NetScout Unit Router NMS Applications Frame...
Page 36 Typical Applications If LAN probing, application layer probing, or packet capture capability is desired, a NetScout probe can be used in conjunction with a FrameSaver 9124 at the central site. In the example below, the FrameSaver 9124 is connected to NetScout’s probe, which is using NetScout’s NMS application to provide full probe capability at the central or regional site.
Page 37 Typical Applications Access to the Frame Relay Network The following configuration shows typical access to the frame relay service using FrameSaver SLV units or fractional T1, with each FrameSaver unit connected to a frame relay router. Token Ring Frame Relay FrameSaver Token Router...
Page 38 Typical Applications Multinational FrameSaver Application For multinational applications, North American FrameSaver SLV units can be teamed with FrameSaver 9820-C and 9820 units to provide a complete, end-to-end, global frame relay management solution for international companies. This solution benefits: North American-based companies with international locations that are used to intelligent diagnostic and service-level verification features in their frame relay networks International companies can expand globally...
Page 39 Typical Applications Mixing FrameSaver Units in Applications Deciding which frame relay FrameSaver unit is needed at a central or remote site is a matter of evaluating the site’s traffic volume to determine the amount of network access required – FT1/T1 or 56/64 kbps. A large central site’s requirement for high-speed and high-volume indicates the need for a FrameSaver 9124 unit at this site.
Page 40 Typical Applications Using All 9624 FrameSaver Units at Remote Sites One of the most common and practical applications for frame relay FrameSaver units is to use a FrameSaver 9124 unit at the central site and FrameSaver 9624 units at most remote sites. The example below shows this application.
Page 41: Mixing Framesaver Units At Remote Sites
Typical Applications Mixing FrameSaver Units at Remote Sites Not all remote sites need to be equipped the same. For example, there can be all FrameSaver 9624 units at the remote sites, or there can be a mix of FrameSaver products. The example that follows illustrates this.
Page 42: H Pvc Multiplexing Application
Typical Applications PVC Multiplexing Application When FrameSaver units are at each end of the circuit, the FrameSaver unit provides the ability to multiplex data of multiple DLCIs onto a single network DLCI. This feature is referred to as PVC multiplexing. PVC multiplexing allows PVC diagnostic tests to be run without disrupting data, and uses the following network configuration.
Page 43 If the unit at the other end is not a FrameSaver unit, PVC diagnostic tests and SLV communication between FrameSaver units are disruptive to user data. PVCs configured for non-Paradyne units should not be multiplexed. This is because only FrameSaver models currently support PVC multiplexing and PVC diagnostics.
Page 44 Typical Applications The following example shows the 1-port, nonmanagement configuration (1Port). FrameSaver Unit DLCI 201 DLCI 201 Frame Relay Port 1 Network NET Port Network Side User Side Contains 1 EDLCI: of LMI of LMI – Port-1 Physical Connection 98-15867 PVC Connection FR Discovery Source...
Page 45: User Interface And Basic Operation
User Interface and Basic Operation This chapter includes the following information: Logging On on page 4-2. Main Menu on page 4-4. Screen Work Areas on page 4-5. Navigating the Screens on page 4-6. — Keyboard Keys on page 4-6. — Function Keys on page 4-7.
Page 46 User Interface and Basic Operation Logging On Start a session using one of the following methods: Telnet session over the COM port 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 47 User Interface and Basic Operation If your login was . . . Then the . . . Valid Main Menu appears (see page 4-4). Begin your session. Invalid Message, Invalid Password, is displayed on line 24, and the Login screen is redisplayed. After three unsuccessful attempts: –...
Page 48 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main Access Level: 1 PARADYNE 9124 Device Name: Node A 04/26/1999 23:32 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
Page 49 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 50: Keyboard Keys
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 51: 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 4-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 52: 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 53: 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 to issue a command. Press the Tab or right arrow key to select a field within a menu. The current setting or value appears to the right of the field.
Page 54 User Interface and Basic Operation This page intentionally left blank. 4-10 June 1999 - Preliminary 9124-A2-GH30-00...
Page 55: Using The Openlane Nms
Using the OpenLane NMS This chapter includes: OpenLane Management features. Installation and Setup of the OpenLane DCE Manager and Performance Wizard on page 5-2. Viewing OpenLane Performance Wizard Graphs specific to FrameSaver SLV data collection and display on page 5-10. Creating OpenLane Service Level Management (SLM) Reports page 5-26.
Page 56: Using An Openlane Nms Application
Using the OpenLane NMS Using an OpenLane NMS Application For additional information about accessing and managing the FrameSaver SLV unit through OpenLane DCE Manager and OpenLane Performance Wizard, and for hardware and software requirements necessary to support these applications refer to the: OpenLane DCE Manager User’s Guide to help you set up and configure devices and their interfaces;...
Page 57: Installing And Starting Openlane Performance Wizard
Using the OpenLane NMS Installing and Starting OpenLane Performance Wizard Installation instructions are located in the OpenLane Performance Wizard User’s Guide. Open the application by following the instructions contained in Getting Started with the Performance Wizard. Depending upon your platform, see one of the following procedures: Installing on Solaris, HP-UX, and AIX Installing on Windows NT or Windows 95...
Page 58: Adding Framesaver Slv Units To Your Network
Using the OpenLane NMS Adding FrameSaver SLV Units to Your Network Use either one of these procedures to add FrameSaver SLV units to your network. " Procedure To add an SLV unit from HP OpenView or NetView: 1. Use the HP OpenView or NetView autodiscovery feature to create submaps and discover an SLV unit.
Page 59: Setting Up For Collection Of Historical Data
Using the OpenLane NMS Setting Up for Collection of Historical Data See the sample Device Explorer window on page 5-3. OK appears under the Historical Collection column. In this example, historical data is being collected for performance statistics on the T1 or Network Port interface of the 135.90.153.3 device.
Page 60: Accessing Netscout Manager Plus
Using the OpenLane NMS Accessing NetScout Manager Plus A direct link to the NetScout Manager Plus application is provided by OpenLane Performance Wizard. Use this feature to launch NetScout reports. " Procedure To access the NetScout Manager Plus main window: 1.
Page 61: Creating Pvc Connections
Using the OpenLane NMS Creating PVC Connections Port-1 PVC definitions need to be created between two endpoints in the network. Network PVCs were automatically created when the unit is discovered. " Procedure To create PVC definitions: 1. From Device Explorer, select a device’s DLCI so it is highlighted. 2.
Page 62: Setting Frame And Burst Ranges
Using the OpenLane NMS Setting Frame and Burst Ranges You can configure frame size and burst upper limits to: Match service level agreement parameters. Identify problem areas. Display the Frame Burst Breakdown graph. Assist in troubleshooting. Match the site’s traffic patterns. "...
Page 63: Getting Error Messages
Using the OpenLane NMS 4. Select a row in the box below the Frame Size Range Upper Limit (Octets) or Burst Range Upper Limit (Octets) heading so it is highlighted, and the selected value appears in the Edit box. NOTE: If you change frame size ranges, the frame size distribution cannot be displayed by the NetScout Manager.
Page 64: H Viewing Openlane Performance Wizard Graphs
Using the OpenLane NMS Viewing OpenLane Performance Wizard Graphs The following OpenLane Performance Wizard graphs support FrameSaver SLV units, integrating the new service level verifier capability provided by FrameSaver SLV units into Device Explorer: Frame Relay Access Channel Aggregated Summary –...
Page 65: Frame Relay Access Channel Aggregated Summary
Using the OpenLane NMS Frame Relay Access Channel Aggregated Summary For a complete view of an interface’s traffic, this graph summary brings together the information needed to determine how well an interface’s, or link’s, capability is being utilized. This set of graphs is provided for the network and data ports. For the FrameSaver 9124, it is also available for the T1 interface.
Page 66 Using the OpenLane NMS Heaviest Users – Output – Shows which DLCIs are generating the most traffic over the frame relay link. Up to three high-volume DLCIs can be shown. This information can be viewed in two forms: — Graph – The data shown for each DLCI is a percent of the line speed over time.
Page 67: Frame Relay Physical Link Integrity
Using the OpenLane NMS Frame Relay Physical Link Integrity Use this grouping of graphs to relate actual throughput on the frame relay link to the types of errors that are occurring. It can also be used to verify that the network is operational and traffic is flowing normally.
Page 68 Using the OpenLane NMS Correlate the time at which a problem occurred to the following graphs. Throughput – Shows the actual volume of data in frames per second for both incoming and outgoing data over a physical link. The line speed is also shown so you can easily see when the link’s physical capacity is about to be exceeded.
Page 69: Ds1 Physical Link Integrity (T1 Only)
Using the OpenLane NMS DS1 Physical Link Integrity (T1 Only) Use this grouping of graphs to compare actual throughput with T1 errors. With this window, you can determine the amount of time the link has been operating error free, and what types of errors are causing the greatest number of problems. 5-15 9124-A2-GH30-00 June 1999 - Preliminary...
Page 70 Using the OpenLane NMS Correlate the time at which a problem occurred to the following graphs. Throughput – Shows the actual volume of data in frames per second for both incoming and outgoing data over the T1 link. Errored Frames – Shows the number of frames per second during which a Severely Errored Seconds or Bursty Errored Seconds condition existed for both incoming and outgoing data over the T1 link, calculated on the percent of the time interval shown.
Page 71: Ds1 Physical Link Diagnostics (T1 Only)
Using the OpenLane NMS DS1 Physical Link Diagnostics (T1 Only) Use this summary graph when errors are detected on the T1 link. This window is only available to a FrameSaver unit with a T1 interface, when either T1 or Frame Relay on Network Port was the selected interface.
Page 72: Pvc Throughput
Using the OpenLane NMS Correlate the time at which a problem occurred to the following graphs. Error Free Seconds – Shows the amount of time during which no errored seconds occurred on the T1 link, counted as a percentage of the time interval shown.
Page 73 Using the OpenLane NMS Variables that could appear in the panes below each graph include: Variable Displayed Indication Frames Sent above CIR Number of transmitted frames that exceeded the contracted CIR. Frames Sent within CIR Number of transmitted frames that complied with CIR.
Page 74: Frame Relay Dlci Congestion
Using the OpenLane NMS Frame Relay DLCI Congestion Although used primarily for capacity planning and CIR negotiations, this group of graphs can be used to assess whether a DLCI is contributing to network congestion. 5-20 June 1999 - Preliminary 9124-A2-GH30-00...
Page 75 Using the OpenLane NMS Correlate the time at which a problem occurred to the following graphs. Capacity – Shows how a DLCI’s capacity is being used for both incoming and outgoing data. When the DLCI’s allocated bandwidth is underutilized, it is time to renegotiate CIR and excess burst size agreements.
Page 76: Pvc Data Delivery Analysis
Using the OpenLane NMS PVC Data Delivery Analysis For a more complete view of network traffic, this graph summary brings together the information needed to determine the cause of frame relay lost packets and/or excessive network latency. A patent is pending on this graphical report. Network service providers can use this screen to help determine whether their network or the customer’s data was the cause for a missed service level agreement (SLA).
Page 77 Using the OpenLane NMS In most cases, transmission characteristics of the customer’s data rather than the network is the cause of apparent network problems. This summary allows you to determine the following: Overutilization of the network, trying to deliver amounts of data well over CIR. Data frames that are too large or small.
Page 78 Using the OpenLane NMS Round Trip Network Latency – Shows how fast the network is moving traffic. Latency is the amount of time it takes a frame relay frame to travel from one CPE end point to another and back. The times at which an average of the frame relay frames are calculated is shown along the bottom, while the delay is shown in milliseconds.
Page 79 Using the OpenLane NMS Transmit Frame Size Distribution – Various service level agreement parameters may be based on frame size, which may contribute to latency and frames being lost. This graph shows the size of the packets being transmitted, so you can compare frame size to your service level agreement. Transmit Frame Size Distribution is measured over time in percent of all transmitted packets within each of the following ranges: Color...
Page 80: H Creating Openlane Service Level Management (Slm) Reports
(throughput) for accurate service level agreement verification. This measurement of throughput uses the Paradyne proprietary TruePut technology which precisely measures both within and above CIR, eliminating inaccuracies due to averaging. Reports are also available for physical inventory of the network’s device names, locations,...
Page 81: Installation And Setup Of Slm Reports
Using the OpenLane NMS Installation and Setup of SLM Reports Refer to the OpenLane Performance Wizard User’s Guide for installation and operation instructions for the Performance Wizard, and follow the instructions applicable to your network platform. All of these reports can be seen online as well as provided on printed reports. Displaying the Log-in Screen The SLM Reports package is available for both network administrators and customers via the Web.
Page 82: Viewing Reports
Using the OpenLane NMS Viewing Reports As a Web user with a customer profile defined by your network administrator, you have the ability to view reports for the FrameSaver SLV devices assigned to you. Upon entering your customer ID, your User ID and Password in the pop-up window, the FrameSaver SLV Reports window displays, giving you the opportunity to select one the reports.
Page 83: Using Netscout Manager Plus
Using NetScout Manager Plus This chapter includes: Significant features of NetScout Manager Plus. Installation and setup of NetScout Manager Plus software. Configuration of NetScout Manager Plus. Release 5.5 or higher of the NetScout Manager Plus software provides FrameSaver SLV-specific support. The NetScout Advantage NetScout Manager Plus features: Large central site location: Layers 2 through 7 monitoring...
Page 84: Using A Netscout Manager Plus Nms Application
Using NetScout Manager Plus Using a NetScout Manager Plus NMS Application For additional information about accessing and managing the FrameSaver SLV unit through NetScout Manager Plus, refer to the: NetScout Manager/Plus User Guide to help you install the application, monitor traffic, and diagnose emerging problems on network segments. NetScout Manager/Plus &...
Page 85: H Configuring Netscout Manager Plus
A template of alarms and values for configuring alarms and several templates for creating history files specific to the FrameSaver unit are available. The Performance Wizard paradyne directories include the following: Properties: paradyne.fsd file found in PerfWiz/netscout/alarms/directory Properties: paradyne.fst file found in PerfWiz/netscout/alarms/directory...
Page 86: Adding Framesaver Slv Units To The Netscout Manager Plus Network
— IP address — Enter 1 for the frame relay logical interface to be monitored. — 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 87: Verifying Domains And Groups
Using NetScout Manager Plus 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 88: Correcting Domains And Groups
Using NetScout Manager Plus 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 89 Using NetScout Manager Plus 4. Click on the domain from the Domains list and configure the following: Property Description Setting Groups Stats (S) Statistics collection Enabled for all domains. Hosts (H) Level 3 information Enabled for IP domain only. (network) Disabled for all other domains.
Page 90: Adding Slv Alarms Using A Template
DLCI. Paradyne 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 91: Editing Alarms
Using NetScout Manager Plus 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 (see the window on page 6-5).
Page 92 Using NetScout Manager Plus 4. Edit any trap defaults that may be required. See Step 4 on page 6-12 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 93: Adding Slv Alarms Manually
DLCI; that is, if there are eight alarms and 20 DLCIs, 160 trap configurations must be created (8 x 20). For this reason, it is recommended that the Paradyne defaults be used. Follow the procedure below to configure alarms manually.
Page 94 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 95: Creating History Files
Two user history table files are already configured and installed in the unit, UserHistory1 and UserHistory2. These files must not be modified. Paradyne uses these two tables to keep SLV data for reports. It is always a good idea to rediscover agents and their DLCIs before starting to be sure your agent and DLCI lists are current.
Page 96: Installing The User-Defined History Files
Using NetScout Manager Plus " 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.
Page 97 Using NetScout Manager Plus " Procedure 1. Type dvuhist -f agentname user_ history_table_number config number_of_buckets interval download_file.udh to load user-defined history files for the frame relay link. Example: dvuhist -f Dallas51 3 config 30 60 Dallas51k.udh The interval must be entered in seconds. 2.
Page 98: Monitoring A Dlci's History Data
Using NetScout Manager Plus 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 99 Using NetScout Manager Plus 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 100 Using NetScout Manager Plus Using the 2D or 3D Bar to view the user history data collected, you can click on a particular bar and get an expanded view of the data. 8. Click anywhere on this window to return to the previous window view (see Step 7 on page 6-17).
Page 101: Monitoring The Agent Using Netscout Manager Plus
Using NetScout Manager Plus Monitoring the Agent Using NetScout Manager Plus Once the FrameSaver SLV agent has been added to NetScout Manager Plus, select either the Traffic or Protocol radio button to monitor the newly added agent, or one of its DLCIs. NOTE: Only the Traffic and Protocol radio buttons on the application selection bar are supported for FrameSaver SLV agents.
Page 102: Statistical Windows Supported
Using NetScout Manager Plus NOTE: If Size Distribution is the selected View and distribution size has been changed via OpenLane Performance Wizard, the values shown for the distribution will not be accurate. Only default size distributions are tracked. Statistical Windows Supported Not all icons that appear on the NetScout Manager Plus main window are supported for FrameSaver units.
Page 103: Concord's Network Health
Concord’s Network Health 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 integrates FrameSaver SLV enhanced performance statistics into its reporting package (see the At-a-Glance report on page 7-19).
Page 104: H Installation And Setup Of Network Health
Concord’s Network Health Installation and Setup of Network Health Refer to the Network Health Installation Guide for installation instructions, and follow the instructions applicable to your network platform. Each Network Health application provides a different set of functions, called a module.
Page 105: Discovering Framesaver Elements
Concord’s Network Health Discovering FrameSaver Elements Once licenses are entered to provide 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 creates definitions in the Poller Configuration, which are used to poll the units.
Page 106: Configuring The Discovered Elements
Concord’s Network Health Configuring the Discovered Elements Network Health sets the speed for discovered elements when it polls the unit for the first time. For a FrameSaver SLV unit, the speed set would be the unit’s CIR. No additional configuration should be required. However, you should verify that all appropriate information has been retrieved.
Page 107: Grouping Elements For Reports
Concord’s Network Health 4. Apply your changes: — Select the Apply/Next button to save your change and bring up the next element to be edited. Continue until all newly discovered frame relay elements have been modified before selecting the OK button. —...
Page 108: Generating Reports For A Group
Concord’s Network Health 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. The following are defined when specifying a report: Report to be run Group Daily, a specific day(s) of the week, weekly, or monthly report...
Page 109: H Viewing Network Health Charts And Tables
7-18 events occurring over the reporting period, and availability and latency levels information. Consolidates transmit burst analysis, network 7-19 Paradyne SLV Plus latency, dropped frames, frame size distribution, At-a-Glance Report and availability information. Trend Reports Performs trend analysis on up to ten specified 7-20 variables for DLCIs.
Page 110: About Service Level Reports
Concord’s Network Health About Service Level Reports For long-term analysis and reporting, you will want to license the Service Level Reports application. This application analyzes data collected over months, or by quarters, and provides service level information about an enterprise, a region, department, or business process.
Page 111: H Reports Applicable To Slv Units
Concord’s Network Health Reports Applicable to SLV Units This section identifies the Network Health reports that apply to FrameSaver SLV products, summarizes relevant information, and tells you how to use the reports. NOTE: Network Health provides information with each chart or table, generally referred to as a report.
Page 112: Network Summary Report
Concord’s Network Health Network Summary Report This set of charts and the table provides a summary of the frame relay network. Use this report for planning and to predict when a DLCI might run into problems 7-10 June 1999 - Preliminary 9124-A2-GH30-00...
Page 113: Leaders Summary Report
Concord’s Network Health Leaders Summary Report The following chart and tables list the ten highest-volume DLCIs. High traffic volume may be increasing latency, and the high Health Index rating indicates problems. It is a good idea to run these reports daily so a norm can be established.
Page 114: Elements Summary Report
Concord’s Network Health Elements Summary Report Use this report for DLCI detail information and comparison. Several views of these charts are available. Use this chart to identify DLCIs with above or below average volume, and investigate. When there are any significant changes, investigate the cause.
Page 115: Supplemental Report
Concord’s Network Health Supplemental Report The information shown in this report is also on other Health reports. However, these charts show more than ten DLCIs at a time so you have a broader view of the service provided by the network. 7-13 9124-A2-GH30-00 June 1999 - Preliminary...
Page 116: Executive Service Level Report
Concord’s Network Health Executive Service Level Report This report summarizes service level performance for an enterprise on a single page. Use this report to assess whether IT service levels are meeting availability and service goals. 7-14 June 1999 - Preliminary 9124-A2-GH30-00...
Page 117: It Manager Service Level Report
Concord’s Network Health IT Manager Service Level Report Using this report, you can compare service level performance of various groups. The report summarizes service levels for a group of DLCIs, along with details on individual DLCIs within that group. 7-15 9124-A2-GH30-00 June 1999 - Preliminary...
Page 118: Customer Service Level Report
Concord’s Network Health Customer Service Level Report This report is used to provide service level information to service customers to help them determine optimum service levels needed based upon their own traffic data, as well as provide documented evidence for increasing CIR. It combines daily volume, daily Health exceptions, bandwidth distribution, average Health Index ratings and availability for each DLCI onto a single page.
Page 119 Concord’s Network Health See LAN/WAN Service Customer Report in the Network Health Reports Guide for information about this report. 7-17 9124-A2-GH30-00 June 1999 - Preliminary...
Page 120: At-A-Glance Reports
Concord’s Network Health At-a-Glance Reports These reports consolidate a frame relay circuit’s performance over a specified period onto single page summaries. Use this report to compare the DLCI’s volume and utilization to the network performance indicators. 7-18 June 1999 - Preliminary 9124-A2-GH30-00...
Page 121 Concord’s Network Health The At-a-Glance report below is the first Network Health report to integrate the FrameSaver SLV’s unique monitoring capabilities, using the unit’s SLV-enhanced network statistics. 7-19 9124-A2-GH30-00 June 1999 - Preliminary...
Page 122: Trend Reports
Concord’s Network Health Trend Reports Variables other than bandwidth can be selected for a trend report (e.g., burst octets); however, a bandwidth trend report (shown here) should be generated when investigating problems that appear on: Exceptions Reports (see page 7-9) Supplemental Report (see page 7-13) Health Reports...
Page 123: Configuration
Configuration Setup and configuration instructions are included in the FrameSaver SLV 9124 Installation Instructions. This chapter provides additional information about the FrameSaver unit’s features and a detailed description of the all the configuration options available. Setting Up the Unit on page 8-4.
Page 124 Configuration Assigning Time Slots/Cross Connections on page 8-35. — Assigning Frame Relay Time Slots to the Network Interface page 8-35. — Assigning DSX-1 Time Slots to the Network Interface on page 8-36. — DSX-1 Signaling Assignments and Trunk Conditioning on page 8-38. Configuring the System on page 8-22.
Page 125: H Setting Up The Unit
Configuration Setting Up the Unit When configuring the system: You need to . . . See . . . 1. Configure the overall system Configuring System Options on page 8-22. options. 2. Set up node IP information. Configuring Node IP Information on page 8-53.
Page 126: Considerations When Setting Up
Configuration Considerations When Setting Up We recommend that you decide how to configure the FrameSaver unit before actually configuring it. When setting up the FrameSaver unit, you need to: Arrange for T1 service. Determine where PVCs will be required in your network. Refer to Chapter 3, Typical Applications, for assistance.
Page 127: 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 Configuring Node IP Information in Chapter 8, Configuration Options, for these options.
Page 128: H Basic Configuration
Configuration Basic Configuration Configuration option settings determine how the FrameSaver unit operates. Use the FrameSaver unit’s Configuration menu to display or change configuration option settings. See Chapter 8, Configuration Options, when configuring the FrameSaver unit. It contains tables describing all configuration options and their possible settings. Changing the Auto-Configuration setting can also change the FrameSaver unit’s configuration.
Page 129 Configuration " Procedure To change configuration option settings: 1. Access and display configuration options and their settings. 2. Change the settings, as needed. 3. Save the changes to one of three configuration option areas. Four configuration option storage areas are available. Configuration Option Area Description Current Configuration...
Page 130: 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 configuration option set into the configuration edit area: 1. Follow this menu selection sequence: Main Menu →...
Page 131: Saving Configuration Options
Configuration Saving Configuration Options When all changes to the configuration options are complete, use the Save function key to save configuration option changes to either the Current, Customer 1, or Customer 2 Configuration areas. " Procedure To save the configuration options changes: 1.
Page 132: H Setting Up Auto-Configuration
Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/auto-configuration PARADYNE 9124 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
Page 133: Changing The Frame Relay Discovery Mode
Configuration Changing the Frame Relay Discovery Mode Configuration options set by discovery mode can be manually modified, refined, or deleted at any time using the Configuration menus. No previously discovered and configured DLCIs or cross-connections will be removed unless authorized. Additional discovered DLCIs will be configured according to the current Frame Relay Discovery mode setting.
Page 134 Configuration " Procedure To select a Frame Relay Discovery mode: 1. Follow this menu selection sequence: Main Menu → Auto-Configuration → Frame Relay Discovery Mode 2. Select a Frame Relay Discovery mode: Discovery Mode Application Description 1MPort Auto-configuration is enabled on Port-1. (default) A management DLCI is configured.
Page 135 Configuration 4. Respond yes or no to the Delete All DLCIs and PVC Connections? prompt (see page 8-11). — If Yes is selected, all discovered and manually configured DLCI records and PVC connections are cleared, except for the management PVC between a data port and router.
Page 136 Configuration Automatic Configuration for Selected Frame Relay Discovery Mode (2 of 4) If the mode selected is . . . Then setup configuration is . . . 1MPort Management PVCs: – Name is automatically created from the network (cont’d) DLCI as Mgmnnnn (nnnn being the discovered multiplexed network DLCI number).
Page 137 Configuration Automatic Configuration for Selected Frame Relay Discovery Mode (3 of 4) If the mode selected is . . . Then setup configuration is . . . No Management: DLCI Records : – Network: DLCI Number is automatically created 1Port from the LMI status response message.
Page 138: H Setting Up For Trap Dial-Out
Configuration Automatic Configuration for Selected Frame Relay Discovery Mode (4 of 4) If the mode selected is . . . Then setup configuration is . . . NetOnly Network DLCI Records: – DLCI Number is automatically created from the LMI status response message. (For DLCI Record information: –...
Page 139: Entering Modem Directory Phone Numbers
Configuration Entering Modem Directory Phone Numbers Phone numbers must be entered into the directories before the modem can dial out. " Procedure 1. Follow this menu selection sequence: Main Menu → Control → Modem Call Directories 2. Press the spacebar until the desired Directory Number appears (A or 1– 5). Set up the A (Alarm) directory as the primary directory.
Page 140: H Setting Up Management
Configuration Setting Up Management For remote sites, only SNMP management needs to be set up. For the central site, local management between the unit and the router must be set up along with SNMP management. " Procedure To set up SNMP management: 1.
Page 141: H Setting Up So The Router Can Receive Rip
Configuration Setting Up So the Router Can Receive RIP Using the FrameSaver unit’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 other FrameSaver SLV units and their routers. "...
Page 142: H Setting Up Service Provider Connectivity
Configuration Setting Up Service Provider Connectivity If management needs to be set up between a service provider’s customer and its network operations center (NOC), a non-multiplexed DLCI must be configured to carry management data between the customer’s central site and the NOC console.
Page 143: H Setting Up For Back-To-Back Operation
Configuration Setting Up for Back-to-Back Operation Using this special feature, you can set up two FrameSaver units that are connected back-to-back without frame relay switches between them, as in a test bench setup. This configuration is shown in the illustration below. T1 Crossover Cable Frame...
Page 144: H Configuring The System
Configuration Configuring the System Configuration option settings determine how the FrameSaver unit operates. The unit can be configured using: Menu-driven user interface via a direct connection or Telnet session. DCE Manager for partial configuration, based upon the following platforms: — HP OpenView Network Node Manager (Unix) —...
Page 145: Configuring System Frame Relay And Lmi Options
Configuration Configuring System Frame Relay and LMI Options Select Frame Relay and LMI to display or change the Frame Relay and LMI options for the system (see Table 8-1). Follow this menu selection sequence: Main Menu → Configuration → System→ Frame Relay and LMI Table 8-1.
Page 146 Configuration Table 8-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 147: Configuring Service Level Verification Options
Configuration Configuring Service Level Verification Options Select Service Level Verification to display or change the Service Level Verification (SLV) System configuration options (see Table 8-2). Follow this menu selection sequence: Main Menu → Configuration → System→ Service Level Verification Table 8-2. Service Level Verification Options (1 of 2) SLV Sample Interval (secs) Possible Settings: 15 –...
Page 148: Configuring General System Options
Configuration Table 8-2. Service Level Verification Options (2 of 2) SLV Timeout Error Event Threshold Available Settings: 1, 2, 3, 4 . . . 20 Default Setting: 3 Specifies the number of consecutive SLV commnications that must be received before an SLV Timeout Error Event is declared.
Page 149 Configuration Table 8-3. General System Options (2 of 2) Primary Clock Source Possible Settings: Net1, DSX, Internal Default Setting: Net1 Allows you to select the primary clock source for the unit. The source selected provides all of the timing within the FrameSaver unit and the clocks for all of the external interfaces.
Page 150: H Setting Up Each Physical Interface
Configuration Setting Up Each Physical Interface Configure physical characteristics using the following interface options: T1 Network Physical Options (below) DSX-1 Interface Physical Options on page 8-31. Data Port Physical Options on page 8-33. Configuring the FrameSaver T1 Network Interface Physical Options Select Physical to display or change the physical configuration options for the T1 Network interface (see Table 8-4) following this menu selection sequence: Main Menu →...
Page 151 Configuration Table 8-4. T1 Network Physical Options (2 of 3) Line Build Out (LBO) Possible Settings: 0.0, –7.5, –15, –22.5 Default Setting: 0.0 Specifies the line build out for the signal transmitted to the network. 0.0, –7.5, –15, –22.5 – Specifies line build out in dB. Bit Stuffing Possible Settings: 62411, Disable Default Setting: 62411...
Page 152 Configuration Table 8-4. T1 Network Physical Options (3 of 3) ANSI Performance Report Messages Possible Settings: Enable, Disable Default Setting: Disable Specifies whether ANSI T1.403 compliance performance report messages (PRMs) are generated and sent to the network over the ESF facility data link every second. Display Conditions –...
Page 153: Configuring The Dsx-1 Interface Physical Options
Configuration Configuring the DSX-1 Interface Physical Options Select DSX-1 to display or change the physical configuration options when a DSX-1 interface is installed (see Table 8-5). " Procedure 1. Follow this menu selection sequence: Main Menu →Configuration → DSX-1 2. Choose whether or not the DSX-1 interface will be provided by the port. Table 8-5.
Page 154 Configuration Table 8-5. DSX-1 Physical 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 155: Configuring Data Port Physical Options
Configuration Configuring Data Port Physical Options Select Physical to display or change the physical characteristics of the data port connected to the DTE (see Table 8-6). Main Menu → Configuration → Data Ports → Physical Table 8-6. Data Port Physical Options (1 of 2) Transmit Clock Source Possible Settings: Internal, External Default Setting: Internal...
Page 156 Configuration Table 8-6. Data Port Physical Options (2 of 2) Monitor DTR Possible Settings: Enable, Disable Default Setting: Enable Specifies the conditions on the data port that determine when valid data is not being sent from the DTE. When this condition is detected, all ones are sent to the network on the DS0 channels allocated to the port.
Page 157: H 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 Network Port interface is enabled, you can make the following cross connection assignments: Frame relay links to Network interface time slots DSX-1 to the Network interface time slots You can also clear cross-connection assignments for the system, or for a selected slot or interface (see...
Page 158: Assigning Dsx-1 Time Slots To The Network Interface
Configuration " Procedure 1. Follow this menu sequence: Main Menu → Configuration → Time Slot Assignment → Frame Relay Network Assignments 2. 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 159 Configuration Time Slot Assignment Rules: Valid Network time slots are either labeled as Available, or contain a DSX-1 time slot assignment Valid DSX-1 time slots are those that are unassigned, and the currently assigned time slot Order of display is as follows: —...
Page 160: Dsx-1 Signaling Assignments And Trunk Conditioning
Configuration DSX-1 Signaling Assignments and Trunk Conditioning The second page of the DSX-1 to Network Assignments screen enables you to define the signaling assignments and trunk conditioning for each time slot on the DSX-1 interface. You can specify whether robbed bit signaling information is being passed within a given DS0, and the value of the signaling bits that will be transmitted for that DS0 to the other cross-connected T1 interface if a Carrier Group Alarm (CGA) occurs on a T1 interface.
Page 161 Configuration Table 8-7. Signaling and Trunk Conditioning Values (2 of 3) DSX-1 Side Default Network Side Value Meaning Value The following values will configure the cross-connect for RBS, as well as perform the trunk conditioning, indicated when a CGA condition occurs. Although the ABCD signaling bits for each setting are described, only AB bits are transmitted when the cross-connected T1 interface is using D4 framing.
Page 162 Configuration Table 8-7. Signaling and Trunk Conditioning Values (3 of 3) DSX-1 Side Default Network Side Value Meaning Value FXSD-idle The signaling bits transmitted to the cross-connected T1 FXOD-idle interface during a CGA represent the idle state for an FXSDN interface (ABCD = 0000). FXSD-busy The signaling bits transmitted to the cross-connected T1 FXOD-busy...
Page 163: Clearing Assignments
Configuration Clearing Assignments Clearing assignments sets all time slots to unassigned. Follow this menu selection sequence: Main Menu → Configuration → Time Slot Assignment → Clear Assignments Configuring Frame Relay LMI for an Interface Select Frame Relay from the selected Network or Data Ports menu. Based upon the information about the local management interface (LMI ) and assigned line conditions supplied by the service provider, edit the Frame Relay configuration options (see Table 8-8).
Page 164 Configuration Table 8-8. Frame Relay and LMI Options (2 of 4) LMI Protocol Possible Settings: Initialize_From_Net1FR1, Initialize_From_Interface, Auto_On_LMI_Fail, Standard, Annex-A, Annex-D (Cont’d) Auto_On_LMI_Fail – The LMI type supported on this frame relay link will be configured to match the LMI protocol discovered from the attached Network line or the DTE device whenever an LMI Link Down failure occurs.
Page 165 Configuration Table 8-8. Frame Relay and LMI Options (3 of 4) LMI Status Enquiry (N1) Possible Settings: 1, 2, 3, 4, . . . 255 Default Setting: 6 Configures the LMI-defined N1 parameter which sets the number of status enquiry polling cycles that the user side of the LMI initiates before a full status enquiry is initiated.
Page 166 Configuration Table 8-8. Frame Relay and LMI Options (4 of 4) Frame Relay DS0s Base Rate Possible Settings: Nx64, Nx56 Default Setting: Nx64 Selects the base rate for the DS0s allocated to frame relay on the Network interface. Display Conditions – This option only appears for the network interface. Nx64 –...
Page 167: H Configuring Dlci Records For Each Interface
Configuration Configuring DLCI Records for Each Interface If Auto-Configuration is not used, it is necessary to create DLCI records manually for each interface. If you do use Auto-Configuration, then it may only be necessary to create a management DLCI between the FrameSaver unit and the router attached to the data port.
Page 168 Configuration " Procedure To change DLCI records: 1. Select the desired DLCI records. 2. Select Modify to change a DLCI record. The message Modify DLCI record for DLCI Number? appears. 3. Select the DLCI record to be modified from the list of all DLCIs on the frame relay link and interface displayed.
Page 169 Configuration Delete EDLCI Connections and Make a standard PVC to frame relay link, DLCI nnnn If you choose this selection, the following actions occur: — Removes this DLCI on all PVC Connections (see Table 8-10, Connection Options), and Management PVC Connections (see Table 8-12, Management PVC Options).
Page 170 Configuration Table 8-9. DLCI Record Options (1 of 2) DLCI Number Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the number for the DLCI in the DLCI record. The parameter determines which DLCI record is used for transferring data on a particular frame relay interface. DLCI numbers range from 0 to 1023.
Page 171 Configuration Table 8-9. DLCI Record Options (2 of 2) Possible Settings: 0 – maximum line rate on port Default Setting: CIR rate Allows you to display or change the committed burst size for the DLCI. Display Conditions – This option only appears when Committed Burst Size is set to Other.
Page 172: H Configuring Pvc Connections
Configuration Configuring PVC Connections Select PVC Connections to display or change the configuration options for the PVC connections (see Table 8-10). DLCI records must have been configured for the interface first. See Maximum PVCs, EDLCIs, and Management PVCs Chapter 1, About the FrameSaver SLV, for a table of the maximum number of PVCs that you can configure.
Page 173 Configuration Table 8-10. PVC Connection Options (1 of 2) Source Link Possible Settings: Port-1, Net1-FR1 Default Setting: Initially blank; no default. Specifies the frame relay interface that starts a PVC connection; the from 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 that are not part of a PVC connection or management link.
Page 174: H Setting Up Management And Communication Options
Configuration Table 8-10. PVC Connection Options (2 of 2) Destination DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the destination DLCI for a frame relay interface. The DLCI must be defined and cannot be part of a PVC connection or management link. For multiplexed DLCIs, at least one EDLCI must be unconnected for the DLCI to be a valid selection.
Page 175: Configuring Node Ip Information
Configuration Configuring Node IP Information Select Node IP to display, add, or change the information necessary to support general IP communications for the node (see Table 8-11). Main Menu → Configuration → Management and Communication → Node IP Table 8-11. Node IP Options (1 of 3) Node IP Address Possible Settings: 001.000.000.000 –...
Page 176 Configuration Table 8-11. Node IP Options (2 of 3) Default IP Destination Possible Settings: None, COM, PVCname Default Setting: None Specifies where a default IP destination or route is connected so that data without a specifically defined PVC will have a route. Examples: If the default IP network is connected to the communications port, you would select COM.
Page 177 Configuration Table 8-11. Node IP Options (3 of 3) TS Management Link Access Level Available Settings: Level-1, Level-2, Level-3 Default Setting: Level-1 Specifies the highest access level allowed when accessing the unit via a Telnet or FTP session when the service provider is using the TS Management Link. Display Conditions –...
Page 178: Configuring Management Pvcs
Configuration Configuring Management PVCs Select Management PVCs to define inband management links by adding or changing Management PVCs (see Table 8-12). First, DLCI records must have been configured for the interface where the Management PVC will reside. See Configuring DLCI Records for Each Interface on page 8-45.
Page 179 Configuration Table 8-12. Management PVC Options (2 of 4) Intf Subnet Mask Possible Settings: Node-Subnet-Mask, Calculate, Special (nnn.nnn.nnn.nnn) Default Setting: Node-Subnet-Mask Specifies the subnet mask needed to access the unit when the management PVC is providing connectivity to an external IP network (through frame relay) that requires a specific subnet mask for the interface.
Page 180 Configuration Table 8-12. Management PVC Options (3 of 4) Primary DLCI Possible Settings: 16 – 1007 Default Setting: Initially blank; no default. Specifies the DLCI number used for the management PVC after the frame relay interface is selected. The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be part of a PVC connection or already assigned as a management PVC.
Page 181 Configuration Table 8-12. Management PVC Options (4 of 4) Primary Link RIP Possible Settings: None, Proprietary, Standard_out Default Setting: Multiplexed DLCIs: Proprietary Nonmultiplexed DLCIs: Standard_out Specifies which Routing Information Protocol (RIP) is used to enable routing of management between FrameSaver units and attached equipment. None –...
Page 182: 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. Main Menu → Configuration → Management and Communication → General SNMP Management See Table 8-13 for General SNMP Management configuration options.
Page 183: Configuring Telnet And/Or Ftp Session Support
Configuration Table 8-13. General SNMP Management Options (2 of 2) Name 2 Access Possible Settings: Read, Read/Write Default Setting: Read Specifies the type of access allowed to the objects in the MIB. This is the type of access allowed for external SNMP managers accessing MIB objects using Community Name 2. Read –...
Page 184 Configuration Table 8-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 185 Configuration Table 8-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. NOTE: Changing this setting does not affect the current session;...
Page 186: Configuring Snmp Nms Security
Configuration Configuring SNMP NMS Security Select SNMP NMS Security to display, add, or change the SNMP security configuration options for the FrameSaver unit. 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 187: Configuring Snmp Traps And Trap Dial-Out
Configuration Table 8-15. SNMP NMS Security Options (2 of 2) Access Type Possible Settings: Read, Read/Write Default Setting: Read Specifies the type of access allowed for an authorized NMS when IP address validation is performed. Display Conditions – This option appears for each trap manager specified in the Number of Trap Managers configuration option.
Page 188 Configuration See Appendix C, SNMP MIBs and Trap, ands RMON Alarm Defaults, for trap format standards and special trap features, including RMON-specific traps, and the default settings that will generate RMON-specific SNMP traps. NOTE: Be sure to choose an operational link for the default. Should the default link become disabled, unrouteable traps will be discarded.
Page 189 Configuration Table 8-16. SNMP Traps and Trap Dial-Out Options (1 of 4) SNMP Traps Possible Settings: Enable, Disable Default Setting: Disable Determines whether the FrameSaver unit sends trap messages to the currently configured SNMP trap manager(s). Enable – Sends trap messages. Disable –...
Page 190 Configuration Table 8-16. SNMP Traps and Trap Dial-Out Options (2 of 4) General Traps Possible Settings: Disable, Warm, AuthFail, Both Default Setting: Both Determines whether SNMP trap messages for warmStart and/or authenticationFailure events are sent to the currently configured trap manager(s). Disable –...
Page 191 Configuration Table 8-16. SNMP Traps and Trap Dial-Out Options (3 of 4) DLCI Traps on Interfaces Possible Settings: Network, Ports, All Default Setting: All Specifies which interfaces will generate linkUp and linkDown trap messages for individual DLCIs. These traps are only supported on the frame relay interfaces. Network –...
Page 192 Configuration Table 8-16. SNMP Traps and Trap Dial-Out Options (4 of 4) Call Retry Possible Settings: Enable, Disable Default Setting: Disable Controls whether an incomplete call (busy, no answer, etc.) is retried when an SNMP trap message is sent to the COM port-connected external device. Enable –...
Page 193: Configuring The Communication Port
Configuration Configuring the Communication Port Select Communication Port to display or change the communication port configuration options (see Table 8-17). Main Menu → Configuration → Management and Communication → Communication Port Table 8-17. 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 194 Configuration Table 8-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 195 Configuration Table 8-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. NOTE: Changing this setting does not affect the current session;...
Page 196 Configuration Table 8-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, see Table 8-17, Communication Port Options).
Page 197: Configuring The Com Port To Support An External Modem
Configuration Configuring the COM Port to Support an External Modem Select External Modem (on Com Port) to display or change the configuration options that control call processing for an external device attached to the COM port (see Table 8-18). Main Menu → Configuration → Management and Communication → External Modem (on Com Port) NOTE: A standard EIA-232 crossover cable is required when connecting an external...
Page 198 Configuration Table 8-18. External Modem (on 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 199 Configuration Control Characters Sequence ASCII ^A or ^a 0x01 ^B or ^b 0x02 ^C or ^c 0x03 ^D or ^d 0x04 ^E or ^e 0x05 ^F or ^f 0x06 ^G or ^g 0x07 ^H or ^h 0x08 ^I or ^i 0x09 ^J or ^j LF or NL...
Page 200 Configuration This page intentionally left blank. 8-78 June 1999 - Preliminary 9124-A2-GH30-00...
Page 201: Security
Security This chapter provides information about the following: Limiting Access (see below). Controlling Asynchronous Terminal Access on page 9-2. Controlling Telnet or FTP Access on page 9-3. — Limiting Telnet Access on page 9-3. — Limiting FTP Access on page 9-4. —...
Page 202: H Controlling Asynchronous Terminal Access
Security 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 async terminal session, or two simultaneous async terminal sessions. Controlling Asynchronous Terminal Access The FrameSaver unit provides the following methods for limiting direct access to the menu-driven user interface on the communication (COM) port:...
Page 203: H Controlling Telnet Or Ftp Access
Security Controlling Telnet or FTP Access The FrameSaver unit provides several methods for limiting access via a Telnet or FTP session. Telnet or FTP access can be on a standard management link, or it can be on a service provider’s troubleshooting (TS) management link. Limiting Telnet Access Methods for limiting access through a Telnet session include the following: Disabling Telnet access completely.
Page 204: Limiting Ftp Access
Security Configuring Telnet and/or FTP Session Support in Chapter 8, Configuration Options, for more information about communication port configuration options. Limiting FTP Access The FrameSaver unit provides the following methods for limiting access through a FTP session: Disabling FTP access completely. Requiring a user ID or password to login.
Page 205: Limiting Telnet Or Ftp Access Over The Ts Management Link
Security 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. Go to the Telnet and FTP Session Options screen. Main Menu → Configuration → Management and Communication → Telnet and FTP Sessions 2.
Page 206: H Controlling Snmp Access
Security Controlling SNMP Access The FrameSaver unit supports SNMP Version 1, which only 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 access type. Assigning IP addresses of NMSs that can access the FrameSaver unit.
Page 207: Assigning Snmp Community Names And Access Levels
Security Assigning SNMP Community Names and Access Levels The General SNMP Options screen provides the configuration options that allow the FrameSaver unit to be managed by an SNMP manager supporting the SNMP protocol. Use this screen to: Assign the SNMP community names that are allowed to access the FrameSaver unit’s Management Information Base (MIB).
Page 208: Limiting Snmp Access Through Ip Addresses
Security Limiting SNMP Access Through IP Addresses The FrameSaver unit provides an additional level of security by: Limiting the IP addresses of the NMSs that can access the FrameSaver unit. Performing validation checks on the IP address of SNMP management systems attempting to access the FrameSaver unit.
Page 209 Security " Procedure To limit SNMP access through IP addresses: 1. Follow this menu selection sequence: Main Menu → Configuration → Management and Communication → SNMP NMS Security The SNMP NMS Security Options screen appears. 2. Select and set the following configuration options, as appropriate. To .
Page 210: H Controlling External Com Port Device Access
Security Controlling External COM Port Device Access The FrameSaver unit allows you to control whether dial-in access for an external device (modem) is allowed on the communication port. Use the External Device Options screen to set the necessary configuration options to allow dial-in access through the COM port.
Page 211: H Creating A Login
Security Creating a Login A login ID and password is required if security is enabled.* You can define a combination of six login/passwords. Each login must be unique and have a specified access level. " Procedure To create a login ID and password: 1.
Page 212: H Modifying A Login
Security Modifying a Login Logins are modified by deleting the incorrect login and creating a new one. Deleting a Login A login record can be deleted. " Procedure To delete a login record: 1. Follow this menu selection sequence: Main Menu → Control → Administer Logins 2.
Page 213: Operation And Maintenance
Operation and Maintenance This chapter includes the following information: Displaying System Information on page 10-2. Displaying LEDs and Control Leads on page 10-3. — LED Descriptions on page 10-4. Device Messages on page 10-6. Status Information on page 10-11. — Self-Test Results Messages on page 10-12.
Page 214 Operation and Maintenance Displaying System Information Use the Identity screen to view identification information about the FrameSaver unit. This information is useful if you are purchasing additional or replacement units and/or making firmware upgrades. Main Menu → Status → Identity View this field .
Page 215 Main Menu → Status → Display LEDs and Control Leads Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/status/leds PARADYNE 9124 Device Name: Node A 1/26/1998 23:32 Î...
Page 216 Operation and Maintenance LED Descriptions The following tables describe what these LEDs indicate. Table 10-1. General Status LEDs Label Indication Color What It Means Power and Green ON – FrameSaver unit has power and is Operational operational. Status OFF – FrameSaver unit is in a power-up self-test, or there is a failure.
Page 217 Operation and Maintenance Table 10-2. Network or DSX 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 218 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 10-4. Device Messages (1 of 6) Message What It Indicates What To Do Access level is n , User’s access level is 2 No action needed.
Page 219 Operation and Maintenance Table 10-4. Device Messages (2 of 6) Message What It Indicates What To Do File Transfer Complete A file transfer was Switch to the newly downloaded performed successfully. software. (Seen at an FTP terminal.) File Transfer Failed – A file transfer was Try again, making sure you type the filename correctly.
Page 220 Operation and Maintenance Table 10-4. Device Messages (3 of 6) Message What It Indicates What To Do Limit of six Login IDs An attempt to enter a new Delete another login/password reached login ID was made, and the combination. limit of six login/password Reenter the new login ID.
Page 221 Operation and Maintenance Table 10-4. Device Messages (4 of 6) Message What It Indicates What To Do No DLCIs Defined DLCI Records was selected Select New and create a DLCI from an interface’s record. Configuration Edit/Display menu, and no DLCI Records have been created for this interface.
Page 222 Operation and Maintenance Table 10-4. Device Messages (5 of 6) Message What It Indicates What To Do Permission Denied A file transfer was attempted, but the: (Seen at an FTP terminal.) User did not have See your system administrator Level 1 security. to get your security level changed.
Page 223 Operation and Maintenance Table 10-4. Device Messages (6 of 6) Message What It Indicates What To Do User Interface Idle Previously active session is Log onto the FrameSaver unit. now closed/ended, and access via the COM port or modem port is now available.
Page 224: 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 on page 10-12. Health and Status Messages on page 10-13.
Page 225: Health And Status Messages
Operation and Maintenance Health and Status Messages These messages appear in the left column of the System and Test Status screen, or the highest priority Health and Status message appears on the last line at the bottom of the screen (right corner). Table 10-6.
Page 226 Operation and Maintenance Table 10-6. Health and Status Messages (2 of 6) Message What It Indicates What To Do Device Fail yyyyyyyy An internal error has been 1. Provide the displayed 8-digit detected by the operating failure code (yyyyyyyy) to your software.
Page 227 Operation and Maintenance Table 10-6. Health and Status Messages (3 of 6) Message What It Indicates What To Do LMI Down, frame relay The Local Management For the Network interface: link Interface is down for the 1. If LMI was never up, verify specified frame relay link.
Page 228 Operation and Maintenance Table 10-6. Health and Status Messages (4 of 6) Message What It Indicates What To Do LOS at Network 1 A Loss of Signal (LOS) condition is detected on the network interface. Clears when the ratio of ones to zeros received is greater than or equal to 12.5%.
Page 229 Operation and Maintenance Table 10-6. Health and Status Messages (5 of 6) Message What It Indicates What To Do OOF at Network n An Out of Frame (OOF) Cleared when a reframe occurs. condition is detected on the 1. Check that the framing format network interface.
Page 230: Test Status Messages
Operation and Maintenance Table 10-6. Health and Status Messages (6 of 6) Message What It Indicates What To Do Yellow at Network n A yellow alarm signal is received on the specified network interface. 1. Network cable problem. 1. Check that your network cable is securely attached at both ends.
Page 231 Operation and Maintenance Table 10-7. Test Status Messages (2 of 2) Message What It Indicates DTPLB Active, Port-1 A Data Terminal Payload Loopback (DTPLB) is active for the specified port. This test can only be activated on Port 2 when Port Use is set to synchronous data.
Page 232: 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. An asterisk identifies each DLCI contained in the device configuration.
Page 233: Pvc Connection Status
Operation and Maintenance PVC Connection Status PVC connection statuses are selected from the Status menu. Only PVC connections with Source DLCIs configured to be Active are shown. See page 10-22 for an example of this screen. Main Menu → Status → PVC Connection Status Table 10-9.
Page 234: Time Slot Assignment Status
Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/status/connections PARADYNE 9124 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
Page 235 Operation and Maintenance Displaying Network Time Slot Assignments Use the Network Timeslot Assignment Status screen to display DS0 assignments for each DS0 on the network interface. Use the following menu sequence to display network channel information. Main Menu → Status → Timeslot Assignment Status → Network The Network Timeslot Assignment Status screen displays 24 two-field entries in three rows.
Page 236 Operation and Maintenance Displaying DSX-1 Time Slot Assignments Use the DSX-1 Timeslot Assignments Status screen to display all of the DS0 assignments for each DS0 on the DSX-1 interface. Use the following menu sequence to display DSX-1 channel information. Main Menu → Status → Timeslot Assignment Status → DSX-1 Select the desired DSX-1 slot and port.
Page 237: H 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 → Status → Performance Statistics The following performance statistics are collected: Service Level Verification Performance Statistics on page 10-27.
Page 238: Clearing Performance Statistics
Operation and Maintenance Clearing Performance Statistics Performance statistics counters can also 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 239: 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. These statistics only appear for the network interface and only if DLCIs are multiplexed (see DLCI Type option in Table 8-9, DLCI Records Options).
Page 240: Dlci Performance Statistics
Operation and Maintenance Table 10-10. Service Level Verification Performance Statistics Statistic What It Indicates Avg RdTrip Latency Average round trip latency, measured in milliseconds, between the FrameSaver unit and the unit at the other end of the multiplexed DLCI connection. Average round trip latency is measured every SLV sampling interval and the average is computed over the previous 15 sampling intervals.
Page 241 Operation and Maintenance Table 10-11. DLCI Performance Statistics (2 of 2) Statistic What It Indicates Tx / Rx Frames Number of frames sent/received for the DLCI on the interface. Tx / Rx Frames Number of frames sent/received for the DLCI on the interface Within CIR that are within the committed information rate that had been configured.
Page 242: Frame Relay Performance Statistics
Operation and Maintenance Frame Relay Performance Statistics These statistics appear when Frame Relay is selected from the Performance Statistics menu. Main Menu → Status → Performance Statistics → Frame Relay Table 10-12. Frame Relay Performance Statistics (1 of 4) Statistic What It Indicates Frame Relay Link Frames Sent...
Page 243 Operation and Maintenance Table 10-12. Frame Relay Performance Statistics (2 of 4) Statistic What It Indicates Frame Relay Errors Total Errors Number of total frame relay errors, excluding LMI errors. Short frames, long frames, invalid DLCIs, unknown DLCIs, and unknown errors are included in this total. Indicates that there may be a non-frame relay device on the other end of the link, or the units at either the far end or both ends of the link may be configured incorrectly.
Page 244 Operation and Maintenance Table 10-12. Frame Relay Performance Statistics (3 of 4) Statistic What It Indicates Frame Relay LMI LMI Protocol LMI protocol configured for the frame relay link. Normal condition. Status Msg Received Number of LMI status messages received over the interface. Normal condition.
Page 245: Esf Line Performance Statistics
Operation and Maintenance Table 10-12. Frame Relay Performance Statistics (4 of 4) Statistic What It Indicates Tx Total Errors Total number of transmit errors on the interface, including transmits discards and transmit overruns. Tx Total Discards Total number of transmit discards on the interface, including underrun flushes.
Page 246 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î main/status/performance/esf PARADYNE 9128 Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î Î...
Page 247 Operation and Maintenance You can collect the following metrics for the network interface. Table 10-13. ESF Line Performance Statistics 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...
Page 248: H 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 249 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 9, Security), you are prompted to enter them.
Page 250: 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 9-15, Communication Port Options).
Page 251: 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 (selected from the Status 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 252: 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 MaxReceive Rate (Kbps) option (see the FTP Max Receive Rate (Kbps) configuration option in Table 8-14, Telnet and FTP Session Options...
Page 253: Troubleshooting
Troubleshooting This chapter includes the following: Problem Indicators on page 11-2. Resetting the Unit on page 11-3. — Resetting the Unit from the Control Menu on page 11-3. — Resetting the Unit By Cycling Power on page 11-3. — Restoring Communication with a Misconfigured Unit on page 11-4.
Page 254 Troubleshooting Physical Tests on page 11-21. — Line Loopback on page 11-21. — Payload Loopback on page 11-22. — Repeater Loopback on page 11-23. — Send Line Loopback on page 11-24. — Send and Monitor Pattern Tests on page 11-25. —...
Page 255: Resetting The Unit From The Control Menu
Troubleshooting Resetting the Unit 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 256: 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.
Page 257 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 258 Troubleshooting Table 11-1. Alarm Conditions (2 of 6) Alarm Condition What It Indicates What To Do CTS down to The CTS control lead on Check DTR and RTS from Port-p Device the device’s interface is off. Port-1. DBM BRI Card Failed One or more of the unit’s 1.
Page 259 Troubleshooting Table 11-1. Alarm Conditions (3 of 6) Alarm Condition What It Indicates What To Do EER at Network 1 The error rate of the For the network interface: received network signal has 1. Verify that the cable is exceeded the currently securely attached at the configured threshold.
Page 260 Troubleshooting Table 11-1. Alarm Conditions (4 of 6) Alarm Condition What It Indicates What To Do LOS at ISDN PRI For an ISDN PRI DBM For the network or DSX-1 (Active/ Idle) interface, Active indicates interface: that a backup call was in 1.
Page 261 Troubleshooting Table 11-1. Alarm Conditions (5 of 6) Alarm Condition What It Indicates What To Do OOF at Network 1 An Out of Frame (OOF) For the network or DSX-1 condition has been interface: detected on the interface. 1. Check that the cable is An OOF condition is securely attached at both declared when two out of...
Page 262 Troubleshooting Table 11-1. Alarm Conditions (6 of 6) Alarm Condition What It Indicates What To Do Secondary Clock A failure of the configured 1. Check that the network cable Failed secondary clock source for is securely attached at both the unit was detected and ends.
Page 263: H Troubleshooting Tables
Troubleshooting Troubleshooting Tables The unit is designed to provide you with many years of trouble-free service. If a problem occurs, however, refer to the appropriate table in the following sections for possible solutions. Device Problems Table 11-2. Device Problems (1 of 2) Symptom Possible Cause Solutions...
Page 264 Troubleshooting Table 11-2. Device Problems (2 of 2) Symptom Possible Cause Solutions Device Fail appears The unit detects an internal Record the 8-digit code from on the System and hardware failure. the System and Test Status Test Status screen screen. under Self-Test Reset the unit and try again.
Page 265: Frame Relay Pvc Problems
Troubleshooting Frame Relay PVC Problems Table 11-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 DLCIs, and CIRs agree with incorrectly. those of the service provider by checking the network-discovered DLCIs.
Page 266: H Tests Available
Troubleshooting Tests Available The Test menu allows you to run loopbacks and test patterns on the FrameSaver unit, and to test the front panel LEDs. It is available to users with a security access level of 1 or 2. Select . . . To run the following tests .
Page 267: H Test Timeout
Troubleshooting Test Timeout A Test Timeout feature is available to automatically terminate a test (as opposed to manually terminating a test) after it has been running a specified period of time. It is recommended that this feature be used when the FrameSaver unit is remotely managed through an inband data stream (PVC).
Page 268: Changing The Test Timeout From Openlane Diagnostic Wizard
Troubleshooting Changing the Test Timeout from OpenLane Diagnostic Wizard The system default for tests is the system’s Test Timeout setting, but it can be overridden from Diagnostic Wizard. You can override the test duration for all tests or for a single test. Prior to running tests from Diagnostic Wizard, the test duration can be set from the Customize drop-down menu.
Page 269: H Starting And Stopping A Test
Troubleshooting Starting and Stopping a Test Use this procedure to start, monitor, or abort specific tests. To abort all active tests on all interfaces, see Aborting All Tests on page 11-18. When the status of a test is . . . The only command available is .
Page 270: 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 on page 11-17.
Page 271: Pvc Loopback
Troubleshooting PVC Loopback The PVC Loopback (Internal) loops frames back to the selected interface on a per-PVC basis. This test logically (not physically) loops back frames from one FrameSaver unit node through the frame relay PVC to the same FrameSaver unit node.
Page 272: Send Pattern
Troubleshooting Send Pattern This test sends frames filled with a hexadecimal 55 test pattern and sequence number over the selected interface on a per-DLCI basis. Main Menu → Test → [Network PVC Tests/Port-1 PVC Tests] → Send Pattern If the selected And the default DLCI is configured as .
Page 273: H Physical Tests
Troubleshooting Physical Tests Physical Tests can be commanded for any of the following interfaces: Network DSX-1 Port 1 Physical tests require the participation of your network service provider. CAUTION: You should not run these tests with frame relay equipment attached; you must disconnect the frame relay equipment and use external test equipment.
Page 274: 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 275: 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 276: 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 277: 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 278: 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 279: H 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 280 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 281: H Lamp Test
Troubleshooting Lamp Test The FrameSaver unit supports a Lamp Test to verify that all LEDs are lighting and functioning properly. All LEDs flash or blink on and off at the same time every 1/2 second during execution of the test. When the test is stopped, the LEDs are restored to their normal condition.
Page 282: H Lmi Packet Capture Utility
Troubleshooting LMI Packet Capture Utility A packet capture utility is provided to aid with problem isolation when LMI errors are detected. Using this utility, any enabled frame relay link that is having problems can be selected. The utility captures any LMI packets sent or received and writes them to a data file called lmitrace.syc in the system’s data directory.
Page 283: Menu Hierarchy
Menu Hierarchy Menus The following is a graphical representation of the FrameSaver SLV unit’s menu organization. 9124-A2-GH30-00 June 1999 - Preliminary...
Page 284 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 (Only if a DSX-1 Interface) Performance Statistics Display LEDs and Control Leads Identity System and PVC Connection Timeslot Identity –...
Page 285 Menu Hierarchy MAIN MENU Status Load Test Configuration Configuration Configuration Edit/Display from: Auto-Configuration System Control Network DSX-1 (Only if a DSX-1 Interface) Data Ports Time Slot Assignment (Only if a DSX-1 Interface) PVC Connections Management and Communication System Network and Time Slot PVC Connection Management and...
Page 286 Menu Hierarchy This page intentionally left blank. June 1999 - Preliminary 9124-A2-GH30-00...
Page 287: Ip Addressing
IP Addressing This appendix includes the following information: Selecting an IP Addressing Scheme on page B-2. Customer Management on page B-3. — Using Multiplexed PVCs on page B-4. Service Provider Management on page B-5. Joint Customer and Service Provider Management on page B-6.
Page 288 IP Addressing Selecting an IP Addressing Scheme You can select from many IP addressing schemes to provide SNMP NMS connectivity. When selecting a scheme, keep the following in mind: Because connection to remote devices is through PVCs, if desired, you can assign IP addresses and subnet masks to each PVC individually.
Page 289 IP Addressing Customer Management When customers are connected to the internet, IP addresses are limited to the number of IP addresses they own. Using FrameSaver units, private addressing can be used for the network without taking away from the customer’s pool of IP addresses.
Page 290 IP Addressing Using Multiplexed PVCs Instead of having one PVC for the router (DLCI 909) and another for the FrameSaver unit, management of the network can be accomplished using only the router PVC when the NOC uses a FrameSaver unit, which has its own IP address, as seen in the illustration below.
Page 291 IP Addressing Service Provider Management Total management can be performed by service providers using both private and public IP addressing. A standard CSU/DSU can be used by the NOC NMS. DLCI 200 Frame Relay Frame Network DLCI 200 Relay 135.18.2.2 DLCI 200/EDLCI 2 Router DLCI 210...
Page 292 IP Addressing Joint Customer and Service Provider Management FrameSaver units can be configured so they can be managed by the customer’s central site, as well as by the NOC. Separate IP addressing schemes for each, the central site and the NOC, are used, as shown in the illustration. Remote Sites Frame...
Page 293: Direct Pvcs To Remote Framesaver Units
IP Addressing IP Addressing Scheme Examples The following examples describe some typical network scenarios; they are not the only scenarios that can be used. The subnet mask shown for each FrameSaver unit is 255.255.255.0. Direct PVCs to Remote FrameSaver Units In this example, FrameSaver unit A is connected to: The NMS at the central site Each remote FrameSaver unit through a management PVC...
Page 294: Routing To Remote Framesaver Units On The Same Subnet
IP Addressing Routing to Remote FrameSaver Units on the Same Subnet In this example, FrameSaver unit A is connected to: The NMS at the central site Remote FrameSaver units through management PVCs The illustration below shows two management PVCs at the central site, and one management PVC between the remote-site devices B and C.
Page 295: Routing To Remote Framesaver Units Using Different Subnets
IP Addressing Routing to Remote FrameSaver Units Using Different Subnets In this example, FrameSaver unit A is connected to: The NMS at the central site Two remote FrameSaver units through management PVCs The illustration below shows two management PVCs, with FrameSaver units B and C connected through one management PVC.
Page 296: Routing To Remote Framesaver Units Using Routers
IP Addressing Routing to Remote FrameSaver Units Using Routers In the following examples, the FrameSaver unit at the central site is connected to: A router ( instead of a LAN connection) The router is connected to the NMS The router’s additional serial or AUX port connection is not used for management No additional network PVCs are required In the following examples, data is not routed by the FrameSaver units, and...
Page 297 IP Addressing The following illustration is a more complex example in which each FrameSaver unit is on its own subnet, having a subnet mask of 255.255.255.0. This subnet is independent of the subnet on the LAN supported by the local router. Subnet Subnet 135.18.1.0 Subnet 135.18.5.0...
Page 298: Assigning Ip Addresses And Subnet Masks
IP Addressing Assigning IP Addresses and Subnet Masks Once you select an IP scheme, assign an address (or addresses) to the access unit. If one IP address is wanted for the FrameSaver unit, set node IP address and subnet mask. If an IP address is wanted for each interface, assign a separate IP address and subnet mask to each interface.
Page 299: Snmp Mibs And Traps, And Rmon Alarm Defaults
Static Frame Relay Interface Alarm Defaults on page C-14. — Dynamic Frame Relay Interface Alarm Defaults on page C-16. — DLCI Alarm Defaults – Paradyne Area on page C-17. — Static DLCI Alarm Defaults – NetScout Area on page C-18. —...
Page 300 Frame Relay Service MIB (RFC 1604) 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.
Page 301 SNMP MIBs and Traps, and RMON Alarm Defaults Standards Compliance for SNMP Traps FrameSaver units, with their special operational trap features, comply with SNMP format standards. 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 of $ifName frame relay link “$linkName”.’...
Page 302: Trap: Authenticationfailure
SNMP MIBs and Traps, and RMON Alarm Defaults Trap: authenticationFailure Table C-2. authenticationFailure Trap Trap What It Indicates Possible Cause authenticationFailure Access to the FrameSaver SNMP protocol message not unit was attempted and properly authenticated. failed. Three unsuccessful attempts were made to enter a correct login user ID/password combination.
Page 303 SNMP MIBs and Traps, and RMON Alarm Defaults The following variable-bindings support the linkUp and linkDown traps. Table C-4. linkUp and linkDown Variable-Bindings (1 of 2) Interface Variable-Bindings Possible Cause Physical Sublayer – Represented by the entry in the MIB II Interfaces Table. (Supported by the ifIndex (RFC 1573) linkDown –...
Page 304 SNMP MIBs and Traps, and RMON Alarm Defaults Table C-4. linkUp and linkDown Variable-Bindings (2 of 2) Interface Variable-Bindings Possible Cause DTE Side of the ifIndex (RFC 1573) linkDown – LMI is down for the Frame Relay UNI LMI Protocol configured, ifAdminStatus Frame Relay link is disabled.
Page 305: 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 include the following, listed in alphabetical order: Table C-5. enterprise-Specific Traps (1 of 2) Trap What It Indicates Possible Cause enterpriseCIR- CIR has changed due to...
Page 306 SNMP MIBs and Traps, and RMON Alarm Defaults Table C-5. enterprise-Specific Traps (2 of 2) Trap What It Indicates Possible Cause enterpriseSelfTest- A hardware failure. Unit has completed Fail(2) (re)initialization and a hardware failure was detected. enterpriseTest- A test is running. At least one test has been Start(5) started on an interface or virtual...
Page 307 SNMP MIBs and Traps, and RMON Alarm Defaults Table C-6. enterprise-Specific Variable-Bindings (2 of 3) Trap Variable-Bindings Possible Cause enterpriseDLCI- devFrExtDlciIfIndex DLCI Status is set to Inactive; the (devFrExt.mib) Down(11) DLCI is down. devFrExtDlciDlci Strings: (devFrExt.mib) ‘$ifString down.’ (Due to LMI or physical failure.) devLastTrapString (devHealthAndStatus.-...
Page 308 SNMP MIBs and Traps, and RMON Alarm Defaults Table C-6. enterprise-Specific Variable-Bindings (3 of 3) Trap Variable-Bindings Possible Cause enterpriseSelfTest- devLastTrapString Unit has completed Fail(2) (devHealthAndStatus.- (re)initialization and a hardware mib) failure was detected. String: ‘Selftest failed: $s.’ ($s is the contents of devSelfTestResult.) For physical interfaces and enterpriseTest-...
Page 309: 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, which are shown below with their variable-bindings. RMON Alarm Defaults on page C-12 for the default values that will generate RMON-specific traps.
Page 310: H Rmon Alarm And Event Defaults
Static Frame Relay Interface Alarm Defaults on page C-14. Dynamic Frame Relay Interface Alarm Defaults on page C-16. DLCI Alarm Defaults – Paradyne Area on page C-17. Static DLCI Alarm Defaults – NetScout Area on page C-18. Dynamic DLCI Alarm Defaults – NetScout Area on page C-19.
Page 311: Rising Event Operation
SNMP MIBs and Traps, and RMON Alarm Defaults Rising Event Operation If a rising threshold is crossed during the interval shown in a table (e.g., frames dropped by the network), the event is armed and an alarm is generated at the end of the interval.
Page 312: Static Frame Relay Interface Alarm Defaults
SNMP MIBs and Traps, and RMON Alarm Defaults Static Frame Relay Interface Alarm Defaults These alarms apply to the FrameSaver unit’s frame relay interfaces. They are created during RMON initialization. Table D-2. Static Frame Relay Interface Alarm Defaults (1 of 2) Rising Falling Sample...
Page 313 SNMP MIBs and Traps, and RMON Alarm Defaults Table D-2. Static Frame Relay Interface Alarm Defaults (2 of 2) Rising Falling Sample Event Threshold Threshold Item MIB/Tag/OID Interval Default Default Type Type Rx Overruns MIB: devfrext.mib (E) 900 secs Rising (15 mins) Tag: devFrExtLinkRxOverruns OID: .1.3.6.1.4.1.1795.2.24.2.
Page 314: Dynamic Frame Relay Interface Alarm Defaults
SNMP MIBs and Traps, and RMON Alarm Defaults Dynamic Frame Relay Interface Alarm Defaults These alarms apply to the FrameSaver unit’s frame relay interfaces. They are created during RMON initialization, and will change if the interface’s line speed changes. Table D-3. Dynamic Frame Relay Interface Alarm Defaults Rising Falling Threshold...
Page 315: Dlci Alarm Defaults - Paradyne Area
These alarms apply to DLCIs on the network interface. They are created either during RMON initialization or when a DLCI is created, and put into the Paradyne-defined alarm area. Table D-4. DLCI Alarm Defaults – Paradyne Area Rising Falling Threshold...
Page 316: Static Dlci Alarm Defaults - Netscout Area
SNMP MIBs and Traps, and RMON Alarm Defaults Static DLCI Alarm Defaults – NetScout Area These alarms apply to DLCIs on the network interface. They are created either during RMON initialization or when a DLCI is created, and put into the NetScout-defined alarm area.
Page 317: Dynamic Dlci Alarm Defaults - Netscout Area
SNMP MIBs and Traps, and RMON Alarm Defaults Dynamic DLCI Alarm Defaults – NetScout Area These alarms apply to DLCIs on the network interface. They are created either during RMON initialization or when a DLCI is created, and put into the NetScout-defined alarm area.
Page 318: H Object Id Cross-Reference (Numeric Order
SNMP MIBs and Traps, and RMON Alarm Defaults Object ID Cross-Reference (Numeric Order) The FrameSaver system supports automatic generation of RMON alarm and event information. Each alarm sets an SNMP variable to monitor. When the threshold set for the monitored variable is exceeded, an SNMP trap or a log event is sent.
Page 319 SNMP MIBs and Traps, and RMON Alarm Defaults Table C-9. OID Cross-Reference (2 of 3) Object ID (OID) Item MIB/Tag .1.3.6.1.2.1.10.32.2.1..1.3.6.1.2.1.10.32.2.1.4.I .D Rx BECNs MIB: FT DTE MIB (RFC 2115) Tag: frCircuitReceivedBECNs .1.3.6.1.2.1.10.32.2.1.5.I .D Rx FECNs MIB: FT DTE MIB (RFC 2115) Tag: frCircuitReceivedFECNs .1.3.6.1.2.1.10.32.2.1.6.I .D Frames Sent...
Page 320 SNMP MIBs and Traps, and RMON Alarm Defaults Table C-9. OID Cross-Reference (3 of 3) 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.3.1.5.I .D Average Latency MIB: devfrext.mib (E) Tag: devFrExtLatencyAvg .1.3.6.1.4.1.1795.2.24.2.6.9. 4.3.1.7.I .D Current Latency MIB: devfrext.mib (E) Tag: devFrExtLatencyLatest .1.3.6.1.4.1.1795.2.24.2.6.9.
Page 321: Cables, Connectors, And Pin Assignments
Cables, Connectors, 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 322 Cables, Connectors, and Pin Assignments COM Port Connector The following table provides the pin assignments for the FrameSaver 9124 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 323: Lan Adapter Converter And Cable
Cables, Connectors, and Pin Assignments LAN Adapter Converter and 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 (3100-F1-920) and Custom 8-conductor cable (with modular plugs on both ends) between the converter and the LAN Adapter (3100-F2-910).
Page 324: Standard Eia-232-D Crossover Cable
Cables, Connectors, 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 D-5 to configure an external modem.
Page 325 Cables, Connectors, and Pin Assignments " Procedure To configure an external modem: 1. Disconnect the asynchronous terminal from the standard cable. See page D-4 for an illustration of the COM Port connection. 2. Reconnect the crossover cable to the external modem. 3.
Page 326 Cables, Connectors, 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 327: Standard V.35 Straight-Through Cable
Cables, Connectors, 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 328: Canadian T1 Line Interface Cable (3100-F1-510)
Cables, Connectors, and Pin Assignments T1 Network Cable (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 From Network Receive Tip...
Page 329: Adapter (9008-F1-560)
Cables, Connectors, 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 (see page D-9). Function Circuit Direction...
Page 330 Cables, Connectors, and Pin Assignments This page intentionally left blank. D-10 June 1999 - Preliminary 9124-A2-GH30-00...
Page 331: Technical Specifications
Technical Specifications Table E-1. 1-Slot FrameSaver Unit 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 332 Technical Specifications Table E-1. 1-Slot FrameSaver Unit 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 Services supported...
Page 333: Equipment List
FrameSaver SLV 9124 T1 Central Site with 120 PVCs 9124-A1-204 (Includes 1-Slot Housing, 120 Vac Power Supply, Network Cable, and Documentation) FrameSaver SLV 9124 T1 Japanese Central Site with 120 DLCIs 9124C with 100 – 240 Vac Power Supply, Network Cable, 9124-A2-404-002...
Page 334: H Cables
9001-F1-020 Optional Features Wall Mounting Kit for 1-Slot Housing 9001-F1-891 Shelf Mounting Kit for 1-Slot Housings 9001-F1-894 User Manual FrameSaver SLV 9124 User’s Guide (Paper Manual) 9124-M1-001 Cables This table lists cables you can order. Description Part Number Feature Number...
Page 335: Index
Index Annex A and D, LMI Protocol, 8-42 Numbers ANSI Performance Report Messages, 8-30 1MPort, auto configuration, 8-13 APM, card failure, 11-5 1Port, auto configuration, 8-15 application 55 hexadecimal, test pattern, 11-20 DDS access to frame relay, 3-5 using the unit in your network, 3-1 ARP, inverse, 1-4 Abnormal Station Code, 11-5 assign...
Page 336 Index congestion, 5-21 DLCI, 5-20 Call Retry, 8-70 Connectivity, IP, 1-4 capacity, 5-11, 5-21 connectivity, 11-20 CGA, 8-38 Control changing characters, 8-77 auto-configuration, 8-11 keys, 4-6 configuration options, 8-8 Leads, Ignore, 8-72 domains and groups, 6-6 menu/branch, 4-4 FR Discovery mode, 8-11 operating mode, 8-21 viewing leads, 10-3 software release, 10-39...
Page 337 Index Date & Time setting, 8-5 dedicated for management, 2-9 Destination, 8-52 BRI Card Failed, 11-6 Down, 10-14, 11-6 Download Required, 11-6 on SLV Timeout, 8-25 DCE Manager elements summary report, 7-12 installation and setup, 5-2 interface status, 10-20 NMS support, 1-6 monitoring user history, 6-16 DDR, 1-2 Number, 8-48...
Page 338 Index EDLCI, 3-11, 8-58 faceplates, 9124, 10-3 Destination, 8-52 FDR, 1-2 management using PVC multiplexing, 2-8 features, 1-2 Source, 8-51 FECN, 5-19 total number, 1-3 field is blank/empty, 4-9 file transfer, 10-36 alarm condition, 11-7 FTP (file transfer protocol), 8-63 at Network, 10-14 Session, 8-63 LED, 10-4, 10-5...
Page 339 Index hardware, requirements, 6-1 keys hardware revision, NAM, 10-2 keyboard, 4-6 HDLC errors, frame relay statistics, 10-32 screen function, 4-5, 4-7 Health and Status, messages, 10-13 heaviest users – output, 5-12 highlighted text, hyperlink to more information, xi history Lamp Test, 10-18, 11-29 adding files, 6-13 LAN, adapter and cable, D-3 installing files, 6-14...
Page 340 Index control and IP addressing, 2-1 and PVC availability, 1-3 creating a separate link, 2-7 Behavior, 8-23 customer, 2-2 Clearing Event (N3), 8-24, 8-42 General SNMP, options, 8-60 Down, 10-15, 11-7 IP connectivity, 1-4 Error Event (N2), 8-23, 8-42 OpenLane 5.0, 1-5 frame relay statistics, 10-32 PVCs, 8-56 Heartbeat (T1), 8-24, 8-43...
Page 341 Index Monitor RTS, 8-34 Network Health, installation and setup, 7-2 monitoring, 1-2 DLCI history data, 6-16 IP Address, 8-64, 8-67, 9-9 FrameSaver unit, 10-11 IP Validation, 8-64, 9-9 LEDs, 10-3 OpenLane management solution, 1-5 using NetScout Manager Plus, 6-19 SNMP security, options, 8-64 multinational, application, 3-6 support, 1-4 Multiplexed...
Page 342 Index availability, 1-3 packet capture, uploading data, 10-40 connection status, 10-21 packets, 8-57 connections, 8-50 Parity, 8-71 creating, 5-7 Password, 9-11 total number, 1-3 pattern data delivery analysis, 5-22 send/monitor, 11-20 Management, 8-56 tests, 11-25 total number dedicated, 1-3 Payload Loopback, 11-22 multiplexing, 2-8, 3-8, 3-10 performance statistics, 10-25 name, 8-54, 8-67...
Page 343 Index Return (Enter) key, 4-6 service level revision, software and hardware, 10-2 customer report, 7-16 RFC 1213 and 1573, C-2 executive report, 7-14 RFC 1315, C-2 IT manager report, 7-15 RFC 1406, C-2 management, 1-1 RFC 1490, routers, for transparent management, 2-10 reports, 7-8 RFC 1604, C-2 verification, statistics, 10-27...
Page 344 Index software System and test status messages, 10-12 changing, 10-39 download, 1-4 configuring options, 8-22 downloading, 10-36 displaying information, 10-2 requirements, 6-1 entering information, 8-5 revision, NAM, 10-2 Frame Relay and LMI, options, 8-23 Source messages, 4-5 DLCI, 8-51 Name, Contact, and Location, 10-2 EDLCI, 8-51 Link, 8-51 Spacebar, 4-6...
Page 345 Index throughput, 1-3, 5-11, 5-14, 5-16, 5-18, 5-21 time, setting, 8-5 UNI, 1-2, 8-23, 8-24 Timeout unit, managing, 2-5 Inactivity, 8-62, 8-73 unknown protocol frames, 5-16 Test, 11-15 upgrading, system software, 10-38 timeslot assignment, status, 10-22 upload/download capability, 1-4 timeslot assignments uploading data, 10-40 DSX-1, 10-24 user history...
Page 346 Index This page intentionally left blank. IN-12 June 1999 9124-A2-GH30-00...

Paradyne FrameSaver SLV 9124 Technical Reference

About this Guide

1 About the Framesaver SLV

2 Management Control

3 Typical Applications

4 User Interface and Basic Operation

5 Using the Openlane NMS

6 Using Netscout Manager Plus

7 Concord's Network Health

8 Configuration

9 Security

10 Operation and Maintenance

11 Troubleshooting

Menu Hierarchy

IP Addressing

SNMP Mibs and Traps, and RMON Alarm Defaults

Cables, Connectors, and Pin Assignments

Technical Specifications

Equipment List

Index

Quick Links

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Paradyne FrameSaver SLV 9124

Summary of Contents for Paradyne FrameSaver SLV 9124