Idle Timeout: allows a security administrator to specify the maximum amount of minutes that a session can
remain in an idle state before the session is automatically disconnected.
The session timeout and idle timeout fields are not exclusive. If both are specified, then the idle timeout
should always be lower than the session timeout since a lower session timeout will always be reached
first.
Important
For additional information on configuring the maximum number of minutes that an interactive CLI session
can be in use, see the idle-sessions threshold command and the clear tacacs sessions CLI command in the
CLI Reference and the show tacacs summary and show tacacs session id in the Statistics and Counter
Reference.
Configuring the System for Remote Access
Configure the system for remote access. An administrative user may access the system from a remote location
over a local area network (LAN) or wide area network (WAN):
•
Telnet
•
Secure Shell (SSH)
•
File Transfer Protocol (FTP) (secured or unsecured)
•
Trivial File Transfer Protocol (TFTP)
If there are two simultaneous telnet sessions, and one administrator deletes the context into which the
other administrator is logged, the administrator in the deleted context will not be automatically kicked
into the local context. Although the deleted context will still appear in the CLI prompt, context specific
commands will generate errors.
Important
For maximum security, use SSH v2.Important
In release 20.0 and higher Trusted StarOS builds, FTP and telnet are not supported.Important
Step 1
Enter the context configuration mode by entering the following command:
[local]host_name(config)# context local
[local]host_name(config-ctx)#
Step 2
If desired, configure the system to allow Telnet access:
[local]host_name(config-ctx)# server telnetd
For maximum system security, you should not enable telnet.
ASR 5500 System Administration Guide, StarOS Release 21.4
27
Getting Started
Configuring the System for Remote Access
To Next Page
Loading...
Need help?
General
