Alcatel-Lucent 7450 Basic System Configuration Manual page 49

Basic System Configuration Guide
• Rollbacks to a checkpoint created in a more recent release is not supported (for
example, node running in 9.0r5 cannot rollback to a checkpoint created in 9.0r7).
• The following list captures some side effects and specific behaviors of a Rollback
revert. Some of these side effects are not related purely to configuration (that is, in
the CLI config branch) and may have interactions with tools commands, RADIUS,
etc.
→ SAA jobs that are running when a rollback revert is initiated, and need
configuration changes due to the rollback, will be stopped. If the SAA job is a
continuous type then it will be re-started as part of the rollback revert after the
config changes have been applied (just as if the operator had typed "no
shutdown" for the continuous SAA job). Non-continuous SAA jobs that were
modified by the rollback would need to be manually restarted if they need to be
run again.
→ If max-nbr-mac-addr is reduced as part of the revert and the number of mac
addresses in the forwarding database is greater than the max-nbr-mac-addr, then
the rollback is aborted (before any actions are taken) and an informative error
message is provided. The operator must take actions to remove the mac addresses
if they wish to proceed with the rollback.
→ If active subscribers and/or subscriber hosts and/or DHCP lease state are present
then some associated configuration changes may be blocked (just as those same
changes would be blocked if an operator tried to make them via CLI – trying to
delete an sla-profile being used by active subscriber hosts, or trying to change a
nat-policy in a sub-profile). If certain configuration changes associated with the
hosts or lease states are required as part of the rollback but those changes are
blocked, then for each blocked configuration item a warning will be printed, that
particular configuration item will not be changed and the rollback will continue.
This is supported on the 7450 ESS and 7750 SR.
→ After multi-chassis peer shutdown or configuration changes that affect the
contents of the distributed database (for example, sync tag creation or deletion),
further configuration changes related to that peer may be temporarily refused.
The duration of the temporary configuration freeze will depend on the size of the
distributed database. A rollback attempting to make those refused configuration
changes will fail and an error message will be provided to the CLI user.
→ If a force-switchover command (for example, tools perform service id 1
endpoint "x" force-switchover spoke-sdp-fec 1) has been applied to a spoke-
sdp-fec of a dynamic multi-segment pseudo wire, and a rollback revert needs to
change the admin state of the spoke-sdp-fec (for example, to modify spoke-sdp-
fec parameters that may be dependent on admin state), then the rollback revert
will automatically remove the force-switchover and the node will revert to
whatever is the best spoke-sdp in the redundant set.
CLI Usage
49