7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
CLI usage
rollback processing may have been in the middle of tearing things down or rebuilding configurations. A
strong warning is issued in this case to indicate that the operator must examine the configuration and
potentially issue another rollback revert to return to a known (and coherent) configuration.
• 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. When an HA switchover occurs during
a rollback (or within a few seconds of a rollback completing), the operator is advised to repeat the
rollback revert operation to the same checkpoint.
2.8.2 Rescue configuration
A special rescue configuration checkpoint can be created that an operator can rollback revert to at
any time. The rescue configuration has its own keyword (rescue) and does not use the same rolling
suffix indexes as the normal rollback checkpoints. This allows the operator to easily return to the rescue
configuration state without having to consider a checkpoint index, and ensures that the rescue checkpoint
is always available (does not roll off the bottom of the list of checkpoints).
The operator should define a basic rescue configuration that is known to work and give correct
management access to the node.
The location and filename of the rescue file are configurable. The 7210 SAS appends an .rc suffix to the
specified rescue filename.
2.8.3 Operational guidelines
The following points provide some operational guidance on the usage of rollback:
• Both admin save and rollback save should be done periodically:
• Do an admin save to back up 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 hardware changes or major service changes.
– Should be done after any software upgrade.
• Do a 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 of configuration changes have been made
– should be done after any hardware changes
– should be done after any software upgrade
– can 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 configuration files
(generated with admin save).
• 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
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
49
SPACER TEXT
To Next Page
Loading...