Effect Of Config Lock On Url Scripts - Cisco ASR 5000 Series Administration Manual

Config Mode Lock Mechanisms
A configure lock force command may not be successful because there is a very small chance that another
administrator may be in the middle of entering a password or performing a critical system operation that
cannot be interrupted. In this case a failure message will appear:
[local]
Failure: Another administrator could not release the configuration mode lock
- please enter 'show administrators' for more information
The configure lock warn command sends a warning message to all config mode users (if any) and then waits
up to 10 seconds to try and acquire the exclusive-lock. If any users are still in config mode, the config mode
remains in a shared-lock state.
[local]
please wait for this message to be sent to the other administrators......
[local]
The other administrators would eventually see this message in their session output:
[local]
Administrator <username> requires exclusive access to configuration mode
>>> You need to exit from configuration mode as soon as possible <<<
[local]
The configure lock warn command does not usually result in the exclusive-lock being acquired since the
other administrators would typically not anticipate seeing the message in their session output.
Important

Effect of Config Lock on URL Scripts

When attempting to load a config script file using the configure <url> command, you must acquire either
the shared-lock (default) or the exclusive-lock. Since the config script file typically contains the config
command, the lock is actually held before and after the config command is parsed and executed.
The lock is held throughout the execution of the entire config file. Since the same shared-lock is used as the
interactive config mode lock, a warning message is displayed followed by a confirmation prompt (if -noconfirm
is not enabled) as shown in the example below.
[local]
Warning: One or more other administrators may be configuring this system
Are you sure? [Y/N]:
With -noconfirm enabled, since all the commands are also echoed to the screen, the warning message will
likely scroll off the screen and may not be noticed.
Important
host_name configure lock force
#
host_name configure lock warn
#
host_name
(config)#
host_name
(config)#
host_name
#
StarOS logs all major config mode lock interactions to the event log and syslog facility (if configured).
You can access a record of what interactions transpired at any time.
host_name config /flash/myconfig.cfg
#
When StarOS first starts up, the Initial Boot Config File is always exclusively locked while loading.
Effect of Config Lock on URL Scripts
ASR 5500 System Administration Guide, StarOS Release 21.4
85