Nokia 7210 Configuration Manual page 51

7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
3HE 17358 AAAB TQZZA
• Avoid repeatedly executing rollback save without also occasionally executing
admin save. If you really get into a bad situation, you may have to use one of
your admin save configurations as the primary configuration for an admin
reboot.
• After a software upgrade has occurred and the system is operating as expected,
it is recommended to create a rollback checkpoint file using the
admin>rollback>save command and to save the 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.
Use subject to Terms available at: www.nokia.com
© 2021 Nokia.
CLI Usage
51