Alcatel-Lucent 7210 SAS M Configuration Manual page 49

•
•
•
•
•
•
•
•
•
7210 SAS M, T, X, R6 Basic System Configuration Guide
Impacts to the running services are minimized during a rollback:
−
No impact in areas of configuration that did not change
−
Configuration parameters that changed (or items that changed config have
dependencies on) are first removed (revert to default) and the previous values are then
restored (can be briefly service impacting in changed areas). Some examples are as
follows:
−
If SAP ingress policy num-qos-resources value is different in the active config
and in comparison to the value in the rollback checkpoint then, all the SAPs are
deleted and created again. This is done to guarantee that configuration of all the
SAPs succeed when moving to the previous configuration.
−
Changing some of the parameters in the SAP egress policy requires the port to be
shutdown. Hence, when moving to a previous configuration results in change of
these values, the port is shutdown, the old sap egress policy is removed and then
the new SAP egress policy is applied.
A rollback will undo any SNMP sets or direct CLI config commands that occurred since
the last checkpoint creation.
During the period when a node is processing a rollback revert, both CLI commands (from
other users) and SNMP commands will continue to be processed. The only commands that
are blocked during a rollback revert are other rollback commands including revert, save,
and compare (only one rollback command can be executing at a time on one node).
Commands are available to view and compare the various rollback checkpoints to current
operating and candidate configurations.
−
Rollback checkpoint files are not guaranteed to be in any particular format. They are
not interchangeable with normal config files or exec scripts. A normal config file
(from an admin save) cannot be renamed as a rollback checkpoint and a rollback can
be executed as long as the hardware change was an addition of hardware to the node
(for example, added a new IOM into a previously empty slot).
−
a rollback is not guaranteed to work if hardware was removed or changed (for
example, IOM was removed, or MDA was swapped for a different MDA type).
Rollback across a change to the following parameters is not supported:
−
System resource profile commands.
Rollback is supported even after an admin reboot is performed (or changes the primary
config in the bof is changed and an admin reboot is performed). Admin reboot does not
"break the chain" for rollback.
The Configuration Rollback feature is incompatible with the use of Time Of Day (ToD)
policies and functionality. Rollback save and rollback revert operations are blocked if any
ToD policies are active (for example, assigned to objects such as a SAP).
Any configuration or state change performed under the debug branch of CLI is not saved
in the rollback checkpoint file nor impacted by a rollback.
Rollbacks to a checkpoint created in a more recent release is not supported.
CLI Usage
Page 49