Transactions And Rollback; Authorization - Alcatel-Lucent 7450 Basic System Configuration Manual

Transactional Configuration
Error messages that will help the operator to take necessary actions to correct the candidate
are provided for commit failures.
Standard line-by-line (immediate operational effect upon pushing the enter/return key) non-
transactional CLI and SNMP commands are not blocked during the creation/editing of a
candidate or the processing of a commit. These commands take immediate effect as normal.

Transactions and Rollback

By default, the SR OS will automatically create a new rollback checkpoint after a commit
operation. The rollback checkpoint will include 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. If the commit fails then no new rollback checkpoint is
created.
When the commit confirmed option is used then a rollback checkpoint is created after the
processing of the commit and will exist whether the commit is automatically reverted or not.
Transactional configuration relies on the rollback mechanism to operate. Any commands and
configurations that are not supported in a rollback revert are also not supported in edit-cfg
mode; for example, changes to chassis-mode.

Authorization

Authorization works transparently in edit-cfg mode and no unique/new local profile or
TACACS+ permissions rules are required (other than allowing access to the candidate
branch). For example: if an operator has permissions to access the configure filter context
then they will automatically also have access to the configure filter context when in edit-cfg
mode.
The candidate load and save operations (if the operator's profile allows access to the
candidate load and save commands) will load and save only those items that the user is
authorized to access.
The candidate view will only display the items that the user is authorized to access.
The various candidate editing commands (such as adding lines, removing lines, delete, etc)
only allow operations on items that the user is authorized to access.
The candidate commit and discard operations (along with rollback revert) operate on the
entire candidate and impact all items (authorization does not apply).
56 Basic System Configuration Guide