Transactional Configuration - Alcatel-Lucent 7450 Basic System Configuration Manual

Transactional Configuration

Transactional configuration allows an operator to edit a candidate configuration (a set of
configuration changes) without actually causing operational changes in the router (the active
or operational configuration). Once the candidate configuration is complete the operator can
explicitly commit the changes and cause the entire new configuration to become active.
Transactional configuration gives the operator better control and visibility over their router
configurations and reduce operational risk while increasing flexibility.
Basic System Configuration Guide
• It is beneficial to create a rollback checkpoint before a rollback revert is initiated
(especially if there have been significant config changes since the last checkpoint was
created). If the rollback is especially significant (a lot of major changes) it is also a
good practice to do perform an admin save in case a full reboot is required to recover
from an issue.
• A rollback failure may occur in some limited cases where the node needs a long time
to complete one of the resulting configuration changes. Some examples include X
and Y. If a rollback (for example, rollback revert 5) fails during execution, it should
be attempted again. The second attempt will typically complete the remaining
configuration changes required to fully revert to the desired checkpoint.
• When a new backup CPM is commissioned, the user execute the admin redundancy
rollback-sync command to copy the entire set of rollback files from the active CPM
cf to the new standby CPM cf. If the operator wants the system to automatically copy
new rollback checkpoints to both cfs whenever a new checkpoint is created, then the
config redundancy rollback-sync should be configured.
• An HA CPM switchover during a rollback revert will cause the rollback operation to
abort. The newly active CPM will have an indeterminate configuration. A log event
is created in this case to warn the operator. When an HA switchover occurs during a
rollback (or within a few seconds of a rollback completing), the operator is advised
to repeat the rollback revert operation to the same checkpoint.
• A rollback checkpoint stores the rollback-location and the local/remote-max-
checkpoint values, and as such a rollback revert operation can change those values.
If an operator changes the local/remote-max-checkpoint values it is recommended to
delete all the existing checkpoints (otherwise a subsequent rollback revert could
change the max back to a previous value).
• If a warning prompt (y/n) is displayed when a rollback revert is initiated, it is highly
suggested to respond no to the warning prompt the first time, save a rollback
checkpoint before attempting this rollback revert, and then executing the revert again
and responding yes. If the rollback encounters problems then a revert to the saved
checkpoint can be used to go back to the initial configuration state.
CLI Usage
53