Alcatel-Lucent 7450 Basic System Configuration Manual page 45

Basic System Configuration Guide
comment-string: an 255 char comment associated with the
checkpoint
• Rollback checkpoints include all current operationally active configuration:
→ Changes from direct CLI commands in the configuration branch.
→ SNMP sets
• Rollback checkpoints do not include bof configurations. The BOF file (and bof
config) is not part of a rollback-save or rollback. A rollback does not change any of
the bof configuration. The BOF contains basic information for the node and does not
change frequently (mostly during initial commissioning of the node).
• A rollback save feature can be automatically executed (scheduled, for example,
monthly) using the cron facility of SR OS.
• The latest rollback checkpoint file uses a suffix of ".rb". The next latest rollback
checkpoint file has a suffix of ".rb.1", the next oldest has a suffix of "rb.2" etc:
file-url.rb <--- latest rollback file
file-url.rb.1
...
file-url.rb.9
• When a rollback save is executed, the system shifts the file suffix of all the previous
checkpoints by 1 (new id = old id + 1). If there are already as many checkpoint files
as the maximum number supported then the last checkpoint file is deleted.
• The maximum number of rollback checkpoints is configurable and defaults to 10
("latest" and 1 through 9, where checkpoint file 9 is deleted during the next rollback-
save).
• The location and name of the rollback checkpoint files is configurable to be local (on
compact flash) or remote. The file-url must not contain a suffix (just a path/directory
+ filename). The suffix for rollback checkpoint files is .rb and is automatically
appended to rollback checkpoint files.
config>system>rollback# rollback-location file-url
• There is no default rollback-location. If one is not specified (or it is cleared using "no
rollback-location") and a rollback save is attempted, the rollback save will fail and
return an error message.
• The entire set of rollback checkpoint files can be copied from the active CPM CF to
the inactive CPM CF. This synchronization is done via the following command:
admin>redundancy# rollback-sync
• The operator can enable automatic synchronization of rollback checkpoint files
between the active CPM and inactive CPM. When this automatic synchronization is
enabled, a rollback save will cause the new checkpoint file to be saved to both the
active and standby. The suffixes of the old checkpoint files on both active and
standby CPMs are incremented.
<--- oldest rollback file
CLI Usage
45