Configuring the Available Interfaces
How to Configure the Telnet Timeout
The SCE platform supports timeout of inactive Telnet sessions.
Options
The following options are available:
•
From the SCE(config-line)# prompt, type timeout timeout, and press Enter.
Step 1
Configuring the SSH Server
•
•
•
Information About the SSH Server
•
•
The SSH Server
A shortcoming of the standard telnet protocol is that it transfers password and data over the net
unencrypted, thus compromising security. Where security is a concern, using a Secure Shell (SSH)
server rather than telnet is recommended.
An SSH server is similar to a telnet server, but it uses cryptographic techniques that allow it to
communicate with any SSH client over an insecure network in a manner which ensures the privacy of
the communication. CLI commands are executed over SSH in exactly the same manner as over telnet.
The SSH server supports both the SSHv1 and SSHv2 protocols. You can disable SSHv1, so that only
SSHv2 is running.
An Access Control List (ACL) can be configured for SSH as for any other management protocol, limiting
SSH access to a specific set of IP addresses (see
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
5-30
timeout — The length of time in minutes before an inactive Telnet session will be timed-out.
–
Default — 30 minutes
Information About the SSH Server, page 5-30
Managing the SSH Server, page 5-31
How to Monitor the Status of the SSH Server, page 5-32
The SSH Server, page 5-30
Key Management, page 5-31
Chapter 5
Configuring the Management Interface and Security
Configuring Access Control Lists (ACLs), page
5-26).
OL-7827-12