Reference Guide

Example of Clearing Existing Sessions

When you try to log in, the following message appears with all your existing concurrent sessions,

providing an option to close any one of the existing sessions:

$ telnet 10.11.178.14

Trying 10.11.178.14...

Connected to 10.11.178.14.

Escape character is '^]'.

Password:

Current sessions for user admin:

Line Location

2 vty 0 10.14.1.97

3 vty 1 10.14.1.97

Clear existing session? [line number/Enter to cancel]:

When you try to create more than the permitted number of sessions, the following message appears,

prompting you to close one of the existing sessions. If you close any of the existing sessions, you are

allowed to login.

$ telnet 10.11.178.17

Trying 10.11.178.17...

Connected to 10.11.178.17.

Escape character is '^]'.

Password:

Maximum concurrent sessions for the user reached.

Current sessions for user admin:

Line Location

2 vty 0 10.14.1.97

3 vty 1 10.14.1.97

4 vty 2 10.14.1.97

5 vty 3 10.14.1.97

Kill existing session? [line number/Enter to cancel]:

Changing System Logging Settings

You can change the default settings of the system logging by changing the severity level and the storage

location.

The default is to log all messages up to debug level, that is, all system messages. By changing the severity

level in the logging commands, you control the number of system messages logged.

To specify the system logging settings, use the following commands.

• Specify the minimum severity level for logging to the logging buffer.

CONFIGURATION mode

logging buffered level

• Specify the minimum severity level for logging to the console.

CONFIGURATION mode

logging console level

• Specify the minimum severity level for logging to terminal lines.

CONFIGURATION mode

Management