Setup Guide

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]:

Enabling Secured CLI Mode

The secured CLI mode prevents the users from enhancing the permissions or promoting the privilege levels.

• Enter the following command to enable the secured CLI mode:

CONFIGURATION Mode

secure-cli enable

After entering the command, save the running-conguration. Once you save the running-conguration, the secured CLI mode is enabled.

If you do not want to enter the secured mode, do not save the running-conguration. Once saved, to disable the secured CLI mode, you

need to manually edit the startup-conguration le and reboot the system.

Log Messages in the Internal Buer

All error messages, except those beginning with %BOOTUP (Message), are log in the internal buer.

For example, %BOOTUP:RPM0:CP %PORTPIPE-INIT-SUCCESS: Portpipe 0 enabled

Conguration Task List for System Log Management

There are two conguration tasks for system log management:

• Disable System Logging

• Send System Messages to a Syslog Server

Disabling System Logging

By default, logging is enabled and log messages are sent to the logging buer, all terminal lines, the console, and the syslog servers.

To disable system logging, use the following commands.

• Disable all logging except on the console.

CONFIGURATION mode

no logging on

• Disable logging to the logging buer.

CONFIGURATION mode

Management