Table of Contents
Advertisement
Operational Guidelines
The following points offer some operational guidance on the usage of rollback.
•
•
•
•
•
•
•
•
•
•
7950 SR OS Basic System Configuration Guide
Both admin save and rollback save should be performed periodically:
Use admin save to backup a complete configuration 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 performed after any software upgrade.
Use rollback-save to create a rollback checkpoint.
Used for intermediate checkpoints that can be recovered with minimal impacts to
services.
Should be performed each time that a moderate amount configuration changes have
been made.
Should be performed after any h/w changes.
Should be performed 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 hardware is changed.
Rollback-checkpoint files are not editable nor compatible/interchangeable with config
files (generated with admin save).
Do not continue to repeat the rollback save, rollback save, rollback save over the course
of weeks/months without also doing executing an occasional admin save. In a serious
situation, use one of the saved configs to use 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 is beneficial 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 perform an admin save 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.
CLI Usage
Page 57
Advertisement
Table of Contents
