Operational Guidelines - Alcatel-Lucent 7450 ESS-12 Configuration Manual

Operational Guidelines

The following points offer some operational guidance on the usage of rollback.
•
•
•
•
•
•
•
•
•
•
Page 62
Both "admin save" and "rollback save" should be done periodically:
"admin save" to backup a complete config file that can be used during router reboot.

Used with a reboot as a last resort.

Do an admin save after any major h/w changes or major service changes.

should be done after any s/w upgrade.
"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 h/w changes.

should be done after any s/w 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
7450 ESS OS Basic System Configuration Guide