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-6
September 2002 9128-A2-GB20-80
Viewing Captured Packets from the Menu-Driven User Interface
The twelve most recent LMI events are stored in the trace log. Once the capture
buffer or trace log is full, the oldest packets are overwritten. To view the most
recently captured packets using the menu-driven user interface:
LMI Packet Capture Utility
→
Display LMI Trace Log
LMI Trace Log Example
Select R
efresh to update the screen with the twelve most recently collected LMI
messages.
The following information is provided:
The internal LMI record number assigned to the packet (1–8000), and the
amount of time the utility was running when the packet was captured.
The maximum amount of time displayed is 4,294,967 seconds (s), which is
reset to 1 second when this amount of time is exceeded.
The type of message, either Status or Status Enquiry, from the captured
packet, and the number of bytes in the packet.
The LMI Type identified in the Protocol Discriminator portion of the captured
packet, and the DLCI number for the packet.
The type of information contained in the captured packet, either Sequence
Number Exchange or Full Status Report.
The send and receive (rcv) sequence numbers from the captured packet
(0–255).
On the Packets Received side of the screen, PVC status for up to ten DLCIs
can be shown. It shows the DLCI number, its active bit status, and if Standard
LMI is running, the DLCI’s CIR value.
main/control/lmi_capture/display_log 9128-II
Device Name: Node A 5/26/2000 23:32
LMI TRACE LOG Page 1 of 3
Packets Transmitted to Net1-FR!
Packets Received from Net1-FR1
LMI Record #1 at 0 s
Status Enquiry Message, 13 bytes
LMI Type is Standard on DLCI 1023
Sequence Number Exchange
Send Seq #181, Rcv Seq #177
LMI Record #2 at 0 s
Status Enquiry Message, 13 bytes
LMI Type is Standard on DLCI 1023
Sequence Number Exchange
Send Seq #181, Rcv Seq #177
--------------------------------------------------------------------------------
Ctrl-a to access these functions, ESC for previous menu M
ainMenu Exit
R
efresh PgUp PgDn