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
7. Operation and Maintenance
9128-A2-GB20-80 September 2002
7-43
Facility Rejected 29 Requested facility is not
provided by the network.
No action is needed.
Incoming Calls
Barred
54 Called user is not permitted
to accept the call.
Turn off network call
screening.
Incompatible
Destination
88 Request to establish a call
has been received, but
low-layer, high-layer, or
another compatibility
attribute (e.g., data rate)
cannot be provided.
Incorrect format of the
destination link.
Arrange for the desired
capability.
Identified Channel
Does Not Exist
82 Channel requested for a call
is not activated on the
interface.
Make sure the network is
configured for 2B service, if
a BRI DBM. Contact your
service provider to verify
that your service is
provisioned for two
B-channels.
Info Element
Nonexistent or
Nonimplemented
99 Device sending this cause
has received a message it
does not recognize.
This cause will not prevent
the message from being
precessed.
1. Verify that the Inbound
Calling ID has been
defined.
2. Verify that the Inbound
Calling ID is part of your
service.
Interworking,
Unspecified
127 Precise cause of a
message cannot be
determined because the
interworking network does
not provide causes.
No action is needed.
Invalid Call
Reference Value
81 Call reference used is not
currently in use on the
user-network interface.
Contact your service
representative.
Invalid Info Element
Contents
100 Device sending this cause
has received and
implemented an information
element, but one or more
fields in the element cannot
be processed.
Contact your service
representative.
Invalid Message,
Unspecified
95 No other cause in the
invalid message class
applies for this invalid
message event.
Contact your service
representative.
Invalid Number
Format – Incomplete
Address
28 Call cannot be completed
because the phone number
is incorrect or incomplete.
Check your ISDN link
profile, and correct the
number.
Table 7-14. Most Recent and Previous Cause Value Messages (2 of 6)
Message
Cause
No. What It Indicates What To Do