22.10.2013 Views

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A two types of locks can be set: auto and manual.<br />

• Set an auto-lock using the command configuration mode exclusive auto from CONFIGURATION<br />

mode. When you set an auto-lock, every time a user is in CONFIGURATION mode all other users are<br />

denied access. This means that you can exit to EXEC Privilege mode, and re-enter<br />

CONFIGURATION mode without having to set the lock again.<br />

• Set a manual lock using the command configure terminal lock from CONFIGURATION mode. When<br />

you configure a manual lock, which is the default, you must enter this command time you want to enter<br />

CONFIGURATION mode and deny access to others.<br />

Figure 32<br />

Locking CONFIGURATION mode<br />

R1(conf)#configuration mode exclusive auto<br />

BATMAN(conf)#exit<br />

3d23h35m: %RPM0-P:CP %SYS-5-CONFIG_I: Configured from console by console<br />

R1#config<br />

! Locks configuration mode exclusively.<br />

R1(conf)#<br />

If another user attempts to enter CONFIGURATION mode while a lock is in place, Message 3 appears on<br />

their terminal.<br />

Message 3 CONFIGURATION mode Locked Error<br />

% Error: User "" on line console0 is in exclusive configuration mode<br />

If any user is already in CONFIGURATION mode when while a lock is in place, Message 4 appears on<br />

their terminal.<br />

Message 4 Cannot Lock CONFIGURATION mode Error<br />

% Error: Can't lock configuration mode exclusively since the following users are currently<br />

configuring the system:<br />

User "admin" on line vty1 ( 10.1.1.1 )<br />

Note: The CONFIGURATION mode lock corresponds to a VTY session, not a user. Therefore, if you<br />

configure a lock and then exit CONFIGURATION mode, and another user enters CONFIGURATION<br />

mode, when you attempt to re-enter CONFIGURATION mode, you are denied access even though you<br />

are the one that configured the lock.<br />

Note: If your session times out and you return to EXEC mode, the CONFIGURATION mode lock is<br />

unconfigured.<br />

Viewing the Configuration Lock Status<br />

If you attempt to enter CONFIGURATION mode when another user has locked it, you may view which<br />

user has control of CONFIGURATION mode using the command show configuration lock from EXEC<br />

Privilege mode.<br />

FTOS Configuration Guide, version <strong>7.8.1.0</strong> 75

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!