7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
CLI usage
configuration using admin>save. This ensures that a good checkpoint fully compatible with the new
release is available shortly after the upgrade.
• A set of rollback checkpoints can be created to support busy/quiet days or weekend/weekdays and
CRON can be used to shift between them.
• It is recommended to create a rollback checkpoint before a rollback revert is initiated (especially if
there have been significant configuration changes since the last checkpoint was created). If the rollback
is especially significant (a lot of major changes) it is also a good practice to do an admin save just in
case a full reboot is required to recover from an issue.
• A rollback failure may occur in some limited cases where the node needs a long time to complete one
of the resulting configuration changes. If a rollback fails during execution, it should be attempted again.
The second attempt will typically complete the remaining configuration changes required to fully revert
to the desired checkpoint.
• On the 7210 SAS-R6 and 7210 SAS-R12, when a new backup CPM is commissioned, the user
should issue the admin>redundancy>rollback-sync to copy the entire set of rollback files from the
active CPM checkpoint file (CF) to the new standby CPM CF. If the operator needs the system to
automatically copy new rollback checkpoints to both CFs whenever a new checkpoint is created, the
config>redundancy>rollback-sync should be configured.
• On the 7210 SAS-R6 and 7210 SAS-R12, a high availability CPM switchover during a rollback
revert will cause the rollback operation to abort. The newly active CPM will have an indeterminate
configuration. A log event is created and the operator is advised to repeat the rollback revert operation
to the same checkpoint.
• A rollback checkpoint file stores the rollback location and the local and remote maximum checkpoint
values, and as such a rollback revert operation can change those values. If an operator changes the
local and remote maximum checkpoint values, it is recommended to delete all the existing checkpoints
otherwise a subsequent rollback revert could change the max values back to a previous value.
•
If a warning prompt (y/n) is displayed when a rollback revert is initiated, it is highly suggested to
respond ‛no’ to the warning prompt the first time, save a rollback checkpoint before attempting this
rollback revert, and execute the rollback>revert again and respond ‛yes’. If the rollback encounters
problems, a revert to the saved checkpoint can be used to return to the initial configuration state.
2.8.4 Configuration guidelines and restrictions
The following are the limitations of the configuration rollback feature for the 7210 SAS-R6, 7210 SAS-R12,
and 7210 SAS-Mxp:
• Resource profile policy changes cannot be rolled back. That is, if there is a change in resource policy/
parameters between active configuration and checkpoint, rollback will not proceed.
• PTP is not supported.
• For SAP ingress QoS, due to the slice information available in the .sdx file, whenever there is a change
in ingress QoS policy attached to a SAP, or if there are any additional SAPs in the checkpoint file, all
SAPs are torn down and rebuilt. The user will be prompted before this occurs.
• A SAP that has a change in egress QoS policy will be shut down and will do a no shutdown after a
delay.
• During rollback, all ports and SAPs are shut down and brought back up again. This brings down traffic
and control protocols that have been initiated or are transitioning through the node during rollback.
• Rollback is not permitted when there is a change to port-scheduler-mode.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
50
SPACER TEXT
To Next Page
Loading...