Nokia 7210 Configuration Manual page 47

7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
3HE 17358 AAAB TQZZA
- Configuration parameters that changed (or items that a changed
configuration has dependencies on) are first removed and the previous
values are restored (can be briefly service impacting in changed areas).
Some examples are as follows:
• If the SAP ingress policy num-qos-resources value is different in the
active configuration and in comparison to the value in the rollback
checkpoint, all the SAPs are deleted and created again. This is done to
guarantee that configuration of all the SAPs succeeds when moving to
the previous configuration.
• Changing some of the parameters in the SAP egress policy requires
the port to be shut down. Therefore, when moving to a previous
configuration results in change of these values, the port is shut down,
the old SAP egress policy is removed, and the new SAP egress policy
is applied.
• A rollback will undo any SNMP sets or direct CLI configuration commands that
occurred since the last checkpoint creation.
• During the period when a node is processing a rollback revert command, 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 configuration files or exec scripts.
A normal configuration 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, the IOM was removed or an MDA was swapped for a different
MDA type).
• Rollback across a change to the following parameters is not supported:
- system resource profile commands
- PTP commands
• Rollback is supported even after an admin reboot is performed (or the primary
configuration 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).
Use subject to Terms available at: www.nokia.com
© 2021 Nokia.
CLI Usage
47