Manual
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

B. SNMP MIBs and Traps, and RMON Alarm Defaults
9128-A2-GB20-80 September 2002
B-15
enterpriseSecondary-
ClockFail(4)
devLastTrapString
(devHealthAndStatus.-
mib)
Operating software has detected
that the secondary clock source
has failed.
String:
‘Secondary clock failed.’
enterpriseSecondary-
ClockFailClear(104)
Operating software has detected
that the secondary clock source is
operational again.
String:
‘Secondary clock restored.’
enterpriseSelfTest-
Fail(2)
devLastTrapString
(devHealthAndStatus.-
mib)
Unit has completed
(re)initialization and a hardware
failure was detected.
String:
‘Self test failed: $
s
.’ ($
s
is the
contents of devSelfTestResult.)
enterpriseTest-
Start(5)
For physical interfaces and
frame relay links:
ifIndex (RFC 1573)
.0.0 (placeholder)
devLastTrapString
(devHealthAndStatus.-
mib
For virtual circuits (DLCIs):
devFrExtDlciIfIndex
(devFrExt.mib)
devFrExtDlciDlci
(devFrExt.mib)
devLastTrapString
(devHealthAndStatus.-
mib
At least one test has been started
on an interface or virtual circuit.
String:
‘$testString test started on
$ifString.’ (e.g., ‘DTE Loopback
test started on Sync Data Port
S01P1.’)
enterpriseTest-
Stop(105)
All tests have been halted on an
interface or virtual circuit.
String:
‘$testString test stopped on
$ifString.’ (e.g., ‘Disruptive PVC
Loopback test stopped on DLCI
100 of Sync Data Port S01P1
frame relay.’)
Table B-7. enterprise-Specific Traps and Variable-Bindings (3 of 3)
Trap Variable-Bindings Possible Cause