Alcatel-Lucent 7210 SAS M Configuration Manual page 53

•
•
•
•
•
•
•
•
•
•
7210 SAS M, T, X, R6 Basic System Configuration Guide
"rollback-save" to create a rollback checkpoint.
−
used for intermediate checkpoints that can be recovered with minimal impacts to
services.
−
should be done each time that a moderate amount configuration changes have been
made.
−
should be done after any hardware changes.
−
should be done after any software upgrade.
−
could also be scheduled with cron (for example, once every 1 or 2 weeks).
A new rescue-save must be created when h/w is changed.
Rollback-checkpoint files are not editable nor compatible/interchangeable with config
files (generated with "admin save").
Don't just keep doing rollback save, rollback save, rollback save over the course of weeks/
months without also doing an occasional admin save. If you really get into a bad situation
you may have to use one of your admin save configs as the primary config for an admin
reboot.
Software Upgrade: It is recommended to create a Rollback Checkpoint (admin rollback
save), in addition to saving the configuration (admin save), after an upgrade has been
performed and the system is operating as expected. This will ensure a good checkpoint
fully compatible with the new release is available at a point shortly after the upgrade.
An operator could create a set of rollback checkpoints to support busy/quiet days or
weekend/weekday and use cron to shift between them.
It may be a good idea to create a rollback checkpoint before a rollback revert is initiated
(especially if there have been significant config 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. Some examples include X and Y. If a
rollback (for example, rollback revert 5) 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.
When a new backup CPM is commissioned, the user should do an "admin redundancy
rollback-sync" to copy the entire set of rollback files from the active CPM cf to the new
standby CPM cf. If the operator wants the system to automatically copy new rollback
checkpoints to both cfs whenever a new checkpoint is created, then the "config
redundancy rollback-sync" should be configured.
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 in this case to warn the operator. When a High Availability switchover
CLI Usage
Page 53