Manage Locks for Restricting Configuration Changes
You can use configuration locks to prevent
other administrators from changing the candidate configuration or
from committing configuration changes until you manually remove
the lock or the firewall automatically removes it (after a commit).
Locks ensure that administrators don’t make conflicting changes
to the same settings or interdependent settings during concurrent
login sessions.
For example, you can check whether other administrators
have set locks and read comments they entered to explain the locks.
Click
the lock
at the top of
the web interface. An adjacent number indicates the number of current
locks.
Lock a configuration.
Click the lock at the top of the web interface.
The lock image varies based on whether existing locks
are
or are not
set.
Take a Lock
and select the
lock
Type
:
Config
—Blocks other administrators
from changing the candidate configuration.
Commit
—Blocks other administrators
from committing changes made to the candidate configuration.
(
Firewall with multiple virtual systems only
)
Select a
Location
to lock the configuration
for a specific virtual system or the
Shared
location.
(
Optional
) As a best practice, enter a
Comment
so
that other administrators will understand the reason for the lock.
Click
OK
and
Close
.
Unlock a configuration.
Only a superuser or the administrator who locked the configuration
can manually unlock it. However, the firewall automatically removes
a lock after completing the commit operation.
Click the lock at the top of the web interface.
Select the lock entry in the list.
Click
Remove Lock
,
OK
,
and
Close
.
Configure the firewall to automatically apply a commit
lock when you change the candidate configuration. This setting applies
to all administrators.