Reference Guide

FTOS>exit

FTOS#telnet 2200:2200:2200:2200:2200::2201

Trying 2200:2200:2200:2200:2200::2201...

Connected to 2200:2200:2200:2200:2200::2201.

Exit character is '^]'.

FreeBSD/i386 (freebsd2.force10networks.com) (ttyp1)

FTOS#

Lock CONFIGURATION Mode

FTOS allows multiple users to make configurations at the same time. You can lock CONFIGURATION mode so that only

one user can be in CONFIGURATION mode at any time (Message 2).

You can set two types of lockst: auto and manual.

• Set auto-lock using the configuration mode exclusive auto command from CONFIGURATION

mode. When you set auto-lock, every time a user is in CONFIGURATION mode, all other users are denied

access. This means that you can exit to EXEC Privilege mode, and re-enter CONFIGURATION mode without

having to set the lock again.

• Set manual lock using the configure terminal lock command from CONFIGURATION mode. When you

configure a manual lock, which is the default, you must enter this command each time you want to enter

CONFIGURATION mode and deny access to others.

Viewing the Configuration Lock Status

If you attempt to enter CONFIGURATION mode when another user has locked it, you may view which user has control of

CONFIGURATION mode using the show configuration lock command from EXEC Privilege mode.

You can then send any user a message using the send command from EXEC Privilege mode. Alternatively, you can

clear any line using the

clear command from EXEC Privilege mode. If you clear a console session, the user is returned

to EXEC mode.

Example of Locking CONFIGURATION Mode for Single-User Access

FTOS(conf)#configuration mode exclusive auto

BATMAN(conf)#exit

3d23h35m: %RPM0-P:CP %SYS-5-CONFIG_I: Configured from console by console

FTOS#config

! Locks configuration mode exclusively.

FTOS(conf)#

If another user attempts to enter CONFIGURATION mode while a lock is in place, the following appears on their terminal

(message 1): % Error: User "" on line console0 is in exclusive configuration mode.

any

user is already in CONFIGURATION mode when while a lock is in place, the following appears on their terminal

(message 2): % Error: Can't lock configuration mode exclusively since the following

users are currently configuring the system: User "admin" on line vty1

( 10.1.1.1 ).

NOTE: The CONFIGURATION mode lock corresponds to a VTY session, not a user. Therefore, if you configure a lock

and then exit CONFIGURATION mode, and another user enters CONFIGURATION mode, when you attempt to re-

enter CONFIGURATION mode, you are denied access even though you are the one that configured the lock.

NOTE: If your session times out and you return to EXEC mode, the CONFIGURATION mode lock is unconfigured.