Alcatel-Lucent 7450 Basic System Configuration Manual page 153

Parameters exclusive — Allows a user to exclusively create a candidate configuration by blocking other users
commit
Syntax commit [confirmed timeout] [comment comment]
commit no-checkpoint [confirmed timeout]
Context candidate
Description
This command applies the changes in the candidate configuration to the active running configuration.
The candidate changes will take operational effect.
If a commit operation is successful then all of the candidate changes will take operational effect and
the candidate is cleared. If there is an error in the processing of the commit, or a 'commit confirmed'
is not confirmed and an auto-revert occurs, then the router will return to a configuration state with none
of the candidate changes applied. The operator can then continue editing the candidate and try a
commit later.
By default, the SR OS will automatically create a new rollback checkpoint after a commit operation.
The rollback checkpoint will contain the new configuration changes made by the commit. An optional
no-checkpoint keyword can be used to avoid the auto-creation of a rollback checkpoint after a
commit.
A commit operation is blocked if a rollback revert is currently being processed.
Parameters confirmed — Specifies that the commit operation (if successful) should be automatically
Basic System Configuration Guide
(and other sessions of the same user) from entering edit-cfg mode. Exclusive edit-cfg mode
can only be entered if the candidate configuration is empty and no user is in edit-cfg mode.
Once a user is in exclusive edit-cfg mode no other users/sessions are allowed in edit-cfg
mode. The user must either commit or discard the exclusive candidate before leaving
exclusive edit-cfg mode. If the CLI session times out while a user is in exclusive edit-cfg
mode then the contents of the candidate are discarded. The admin disconnect command can
be used to force a user to disconnect (and to clear the contents of the candidate) if they have
the candidate locked.
reverted (undone) at the end of the timeout period unless the operator issues the confirm
command before the timeout period expires. A rollback checkpoint is created after the
commit operation (if successful) and will remain available whether the commit is auto-
reverted or not. The contents of the candidate will remain visible (candidate view) and
changes to the candidate are blocked until the timeout is completed or the candidate confirm
command is executed. If the timeout expires and an auto-revert occurs, then the original
candidate config will be available in edit-cfg mode.
Standard line-by-line non-transactional configuration commands (including via SNMP) are
not blocked during the countdown period and any changes made to the configuration during
the countdown period will be rolled back if the timeout expires. The confirmed option is
useful when changes are being made that could impact management reachability to the router.
A rollback revert is blocked during the countdown period until the commit has been
confirmed.
CLI Usage
153