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-22
9783-A2-GB20-00
July 2000
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. In addition, the test
can be run to access a remote unit for configuration purposes.
Times when you might want to run an IP Ping test are:
H To test connectivity between the FrameSaver unit and any FrameSaver unit
in the network to verify that the path is operational. Select Procedure 1 to
ping any far-end FrameSaver unit.
H To verify the entire path between a newly installed remote site FrameSaver
unit and the central site NMS. During a remote site installation, an IP Ping
test is typically run from the remote site to ping the NMS at the central site.
The remote FrameSaver unit must have SNMP trap managers configured,
and one of those trap managers must be the central site NMS. Select
Procedure 2 to ping the NMS at the central site.
H To test the path to the NMS trap managers during installation of the central
site FrameSaver unit. The remote FrameSaver unit must have configured the
SNMP trap managers to be sent the Ping. Select Procedure 2 to ping the
SNMP trap managers.
" Procedure 1
To ping any far-end FrameSaver unit:
1. Select the IP Ping test.
Main Menu
→
Test
→
IP Ping
2. Enter the IP Address of the device the Ping is being sent to, then select Start.
NOTE:
If the FrameSaver unit has just initialized, or the far-end unit has just
initialized, it may take about a minute for the units to learn the routes via
the proprietary RIP.
If accessing the unit remotely to enter or change frame relay parameters,
send the Ping five times in a row, in rapid succession; the unit will be
operating in frame relay mode.
3. Verify the results of the IP Ping test.
— While the test is running, In Progress... appears in the Status field.
— When the test is finished, Alive. Latency =
nn
ms should appear
as the Status (
nn
being the amount of time the test took in milliseconds).
If any other message is displayed, additional testing will be required.