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
6. Security and Logins
6-14
September 2002 9128-A2-GB20-80
Controlling Router CLI Access
The FrameSaver SLV 9126-II Router can be managed from an NMS using SNMP,
or from the router’s command line interface (CLI). There are two methods to
access the command line interface:
Local access at the router through the COM port, or
Access via a Telnet session.
Telnet access defaults to Administrator level. If the current login is at the
Operator level, only Operator level access is available for the session. Telnet
access is always enabled.
The router accepts one CLI login session at a time and is configured at the factory
without a default login ID and password. To provide login security to the system,
configure a login ID and password.
When a local console connection is first established, a login prompt appears. If the
Device Name field has been configured via the Control menu
(Control Menu
→
System Information)
, the login prompt displays the device name.
For example, a device name of Largo is shown as:
Largo>
See
Creating a Login
on page 6-12 for security information for each Login ID.
Access Levels (Command Modes)
There is one login ID and several levels of privileges for the router’s CLI. Your user
account can be configured with one user name and different passwords for:
Operator
. The Operator has read-only access to display device information
with no modification permission and limited access to diagnostic functions.
With a device name of Largo, the prompt appears as Largo>.
Administrator
. The Administrator has several levels of access to the router’s
CLI. The # sign in the following prompts indicates Administrator access level.
Refer to Appendix C,
Router CLI Commands, Codes, and Designations
, for
access level details for each command line entry.
Display Prompt with Device Name of Largo Administrator Access Levels
Largo #> Standard (same as Operator)
Largo(config) # Configuration
Largo(config-if) # Configuration Interface
Largo(config-subif) # Configuration Sub-Interface
Largo(config-dhcp) # Configuration DHCP Pool