For Locking the configuration file, that onle one can cahneg the config at once, you need to
set it to auto or manual:
evil-router(config)# configuration mode exclusive auto
and after setting this, you see if you enter in teh config mode:
evil-router#conf t
Configuration mode locked exclusively. The lock will be cleared once you exit out of configuration mode using end/exit
Enter configuration commands, one per line. End with CNTL/Z.
evil-router(config)#
and if someone other is trying, it see's
evil-router#conf t
Configuration mode locked exclusively by user 'trilobit' process '135' from terminal '7'. Please try later.Rollback confirmed change timer is cancelled due to configuration lock error.
for testing the Lock status, and you see, who ist locking the config
evil-router#show configuration lock
Parser Configure Lock
---------------------
Owner PID : 135
User : routeradmin
TTY : 7
Type : EXCLUSIVE
State : LOCKED
Class : EXPOSED
Count : 1
Pending Requests : 0
User debug info : configure terminal
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : 192.168.1.1
Lock active time (in Sec) : 140
Lock Expiration timer (in Sec) : 502
evil-router#
manual locking you set the config to
configuration mode exclusive manual
and for Locking, if you config
evil-router#configure terminal lock
Configuration mode locked exclusively. The lock will be cleared once you exit out of configuration mode using end/exit
Enter configuration commands, one per line. End with CNTL/Z.
evil-router(config)#
|