7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
CLI usage
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).
• 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.
• 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 configuration branch) and may
have interactions with tools commands, RADIUS, and so on:
– 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, it will be restarted as part of the
rollback revert after the configuration 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 need to be manually restarted if they need to be run again.
– If max-nbr-mac-addr is reduced as part of the revert but the number of MAC addresses in the
forwarding database is greater than the maximum number of MAC addresses, 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 to proceed with the rollback.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
47
SPACER TEXT
To Next Page
Loading...