Alcatel-Lucent 7750 Configuration Manual page 56

Feature Behavior
•
•
•
•
•
•
•
•
•
•
•
Page 56
A Rollback will undo any SNMP sets or direct CLI config commands that occurred since
the last checkpoint creation.
During the period when an SR-OS 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 in 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 then referenced for a
rollback revert operation. Only rollback checkpoint files generated with rollback save can
be used to rollback revert.
If a hardware change is made after a rollback-save then:
−
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:
−
chassis-mode
−
mixed-mode
−
the SR | SS capability of a card (configure card capability sr|ess)
−
configure isa application-assurance-group minimum-isa-generation
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).
Lawful Intercept configuration under the config>li branch is not affected by a rollback or
rescue. LI configuration is not saved in the rollback checkpoint or rescue file, and a
rollback revert does not touch any config under the config>li branch.
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 (for example,
node running in 9.0r5 cannot rollback to a checkpoint created in 9.0r7).
7750 SR Basic System Configuration Guide