08-04-2008 07:42 PM
I am looking to change the inactivity timeout using a parameter map. Was planning to apply policy-map for this globally and was wondering if I would affect existing connections or does it only apply to new connections??
-Lloyd
08-04-2008 09:28 PM
It only affects connections established after the service-policy is applied.
If you want to make sure only certain ports have a different timeout value combine the class map with an access-list.
Roble
08-05-2008 01:32 PM
Hi Andrew,
By default, the inactivity timeout value is 5 minutes. You can modify the length
of time that can occur before the ACE automatically logs off an inactive user by
using the login timeout command in configuration mode. This command
specifies the length of time that a user session can be idle before the ACE
terminates the console, Telnet, or SSH session.
Note The login timeout command setting overrides the terminal session-timeout
setting (see the âConfiguring Terminal Display Attributesâ section).
The syntax for the login timeout command is as follows:
login timeout minutes
The minutes argument specifies the length of time that a user can be idle before
the ACE terminates the session. Valid entries are from 0 to 60 minutes. A value
of 0 instructs the ACE never to timeout. The default is 5 minutes.
For example, to specify a timeout period of 10 minutes, enter the following
command:
host1/Admin(config)# login timeout 10
To restore the default timeout value of 5 minutes, enter the following command.
host1/Admin(config)# no login timeout
To display the configured login time value, use the show login timeout command
in Exec mode. For example, enter the following command:
host1/Admin# show login timeout
Login Timeout 10 minutes.
Kindly refer the following url:
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: