Configuration Locks

Only one user can have Read/Write access to Gaia configuration database at a time. All other users can log in with Read-Only access to see configuration settings, as specified by their assigned roles.

When you log in and no other user has Read/Write access, you get an exclusive configuration lock with Read/Write access. If a different user already has the configuration lock, you have the option to override their lock. If you:

• Override the lock. The other user stays logged in with Read-Only access.
• Do not override the lock. You cannot modify the settings.

Use the database feature to obtain the configuration lock.

The commands do the same thing: obtain the configuration lock from another administrator.

Description

Use the lock database override and unlock database commands to get exclusive read-write access to the Gaia database by taking write privileges away from other administrators logged into the system.

Syntax

lock database override

unlock database

Comments

• Use these commands with caution. The administrator, whose write access is revoked, does not receive a notification.
• The lock database override command is identical to the set config-lock on override command.
• The unlock database command is identical to the set config-lock off command.

Configuring Lock Behavior

The behavior of the configuration lock command is configured using: config-lock.

Description

Configures and shows the state of the configuration lock on Gaia configuration database.

Syntax

set config-lock off on [timeout <5-900>] override

show config-lock config-state

Parameters

Parameter	Description
off	Turns off the configuration lock.
on	Turns on the configuration lock. The default timeout value is 300 seconds.
timeout <5-900>	Optional parameter. Turns on the configuration lock for the specified interval in seconds.

Comments:

• The set config-lock on override command is identical to the lock database override command.
• The set config-lock off command is identical to the unlock database command.