User's Manual
Table Of Contents
- Contents
- About This Guide
- About the FrameSaver DSL Unit
- User Interface and Basic Operation
- Configuration Procedures
- Configuration Options
- Overview
- Using the Easy Install Feature
- Setting Up So the Router Can Receive RIP
- Entering System Information and Setting the System Clock
- Configuration Option Tables
- Configuring the Overall System
- Configuring the Physical Interfaces
- Configuring Frame Relay for the Data Port
- Configuring ATM for the Network Interface
- Configuring Circuit and DLCI Records
- Configuring PVC Connections
- Setting Up Management and Communication Options
- Configuring Node IP Information
- Configuring Management PVCs
- Configuring General SNMP Management
- Configuring Telnet and/or FTP Session Support
- Configuring SNMP NMS Security
- Configuring SNMP Traps
- Configuring the Ethernet Port
- Configuring the Communication Port
- Configuring the COM Port to Support an External Modem
- Security and Logins
- Operation and Maintenance
- FTP Operation
- Troubleshooting
- Setting Up OpenLane for FrameSaver Devices
- Setting Up Network Health for FrameSaver Devices
- Menu Hierarchy
- SNMP MIBs and Traps, and RMON Alarm Defaults
- Connectors, Cables, and Pin Assignments
- Technical Specifications
- Equipment List
- Index
Troubleshooting
8-18
9783-A2-GB20-00
July 2000
PVC Tests
PVC tests can be run on a requested DLCI for a selected interface. The
FrameSaver unit must be operating in frame relay mode.
H When PVC tests are on a multiplexed DLCI between FrameSaver devices,
they are nondisruptive to data, so user data can continue to be sent during a
test.
H If the device at one end of the circuit is not a FrameSaver device, PVC tests
are on a standard DLCI and are disruptive to data. Also, the Connectivity test
would not appear.
Loopback, and send/monitor pattern tests are available for each interface on the
selected DLCI. FrameSaver devices should be at each end of the circuit. If a
PVC Loopback is started at one end of the circuit, the other end can send and
monitor pattern tests.
The example below shows a PVC Test screen for a FrameSaver unit with the
multiplexed DLCI 550 selected. If a standard DLCI was selected, (Disruptive),
rather than (Non-Disruptive), would be displayed after Test. Also, the
Connectivity test would not appear.
PVC Tests Screen Example
main/test/network_pvc 9783
Device Name: Node A 05/13/2000 08:03
NETWORK
PVC TESTS
DLCI Number: 550
Test (Non-Disruptive) Command Status Result
PVC Loopback: Start Inactive 0:00:00
Send Pattern: Start Inactive 0:00:00
Monitor Pattern: Start Inactive 0:00:00
Sequence Errors 99999+
Data Errors 99999+
Connectivity: Start Inactive RndTrip Time(ms) 99999
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Ctrl-a to access these functions, ESC for previous menu M
ainMenu Exit
NOTE:
Errors encountered during these tests may be caused by mismatched CIRs
in the two FrameSaver units. If errors are detected, verify the CIR
configuration and retest.