Router User's Guide
Table Of Contents
- Contents
- About This Guide
- 1. About the FrameSaver SLV
- 2. User Interface and Basic Operation
- 3. Configuration Procedures
- 4. Configuration Options
- Using the Easy Install Feature
- Using RIP with FrameSaver SLV CSU/DSUs
- Entering System Information and Setting the System Clock
- Setting Up the Modem
- Setting Up Auto-Configuration
- Setting Up Dial Backup
- PVC Backup Over the Network Interface
- Setting Up Back-to-Back Operation
- Configuration Option Tables
- Configuring the Overall System
- Configuring Physical Interfaces
- Assigning Time Slots/Cross Connections
- Configuring Frame Relay for an Interface
- Manually Configuring DLCI Records
- Configuring PVC Connections
- Configuring the IP Path List
- Setting Up Management and Communication Options
- Configuring the Criteria for Automatic Backup
- 5. Configuring the FrameSaver SLV Router
- FrameSaver SLV Router Overview
- IP Routing
- Address Resolution Protocol
- Proxy ARP
- Interface Configuration
- Network Address Translation
- Network Address Port Translation
- Dynamic Host Configuration Protocol Server
- DHCP Relay Agent
- Router Security
- Provisioning the Router Interface
- Configuring the Router Using Terminal Emulation
- 6. Security and Logins
- 7. Operation and Maintenance
- 8. Troubleshooting
- 9. Setting Up OpenLane for FrameSaver Devices and Activating SLM Features
- 10. Setting Up NetScout Manager Plus for FrameSaver Devices
- 11. Setting Up Network Health for FrameSaver Devices
- A. Menu Hierarchy
- B. SNMP MIBs and Traps, and RMON Alarm Defaults
- C. Router CLI Commands, Codes, and Designations
- D. Router Command Line Summaries and Shortcuts
- E. Connectors, Cables, and Pin Assignments
- F. Technical Specifications
- G. Equipment List
- Index
8. Troubleshooting
8-40
September 2002 9128-A2-GB20-80
IP Ping Test – Procedure 2
Procedure
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.
3. Verify that the central site NMS has been configured as an SNMP Trap
Manager if the router is to route data, so a route has been configured within
the FrameSaver unit.
Main Menu
→
Configuration
→
Management and Communication
→
SNMP Traps
Or, for a local DLCI between the central site FrameSaver unit and its router,
verify that a Default IP Destination route has been configured.
Main Menu
→
Configuration
→
Management and Communication
→
Node IP
→
Default IP Destination
Configure both SNMP Traps and a Default IP Destination when PVC
Multiplexing is used, as when using the Auto-Configuration feature.
4. Select the IP Ping test.
Main Menu
→
Test
→
IP Ping
5. Enter the IP Address of the central site NMS, then select Start.
6. 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
should appear as the Status. If any
other message is displayed, additional testing is required.
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.
Main Menu
→
Test
→
Lamp Test
If the Test Timeout configuration option is enabled and a Test Duration is set, the
Lamp Test stops when the test duration expires. See
Test Timeout Feature
on
page 8-19
,
for additional information.