Alcatel-Lucent 7450 Basic System Configuration Manual page 48

Configuration Rollback
48
cause a traffic interruption.
- Changing the neighbor of a MC-APS port will start with neighbor 1, then be
configured as no neighbor, and then will be configured with neighbor 2.
Moving through the no neighbor intermediate state requires the working
and protect circuits to be torn down and then rebuilt. This impacts the 7450
ESS and 7750 SR.
• 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 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 card or IOM into a previously
empty slot).
→ a rollback is not guaranteed to work if hardware was removed or changed (for
example, XCM/IOM was removed, or XMA/MDA was swapped for a different
XMA/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.
• 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.
Basic System Configuration Guide