Nokia 7210 - Access codes

CLI Usage
50
7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
© 2021 Nokia.
Use subject to Terms available at: www.nokia.com
3HE 17358 AAAB TQZZA
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).