System Management
488
7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
3HE 16132 AAAB TQZZA Edition: 01
Context config>redundancy
Supported
Platforms
7210 SAS-R6 and 7210 SAS-R12
Description The command enables automatic synchronization of rollback checkpoint files between the
active CPM and inactive CPM. When automatic synchronization is enabled, a rollback save
will cause the new checkpoint file to be saved on both the active and standby CPMs. The
suffixes of the old checkpoint files on both active and standby CPMs are incremented.
Automatic synchronization only causes the ONE new checkpoint file to be copied to both CFs
(the other 9 checkpoints are not automatically copied from active to standby but that can be
done manually with admin>red>rollback-sync).
Automatic synchronization of rollback checkpoint files across CPMs is only performed if the
rollback-location is configured as a local file-url (for example, "cf3:/rollback-files/rollback).
Synchronization is not done if the rollback-location is remote.
synchronize
Syntax synchronize {boot-env | config}
no synchronize
Context config>redundancy
Supported
Platforms
7210 SAS-R6 and 7210 SAS-R12
Description This command enables automatic synchronization of the standby CPM/CFM’s images and
config files to the active CPM/CFM. Either the boot-env or config parameter must be
specified.
When the standby CPM/CFM takes over operation following a failure or reset of the active
CPM/CFM, it is important to ensure that the active and standby CPM/CFMs have identical
operational parameters. This includes the saved configuration, CPM and IOM images. This
includes the saved configuration and CFM images.
The active CPM/CFM ensures that the active configuration is maintained on the standby
CPM/CFM. However, to ensure smooth operation under all circumstances, runtime images
and system initialization configurations must also be automatically synchronized between the
active and standby CPM/CFM.
Note: The config red sync {boot-env | config} and admin red sync {boot-env | config}
commands do not apply to rollback checkpoint files. These commands do not manually or
automatically sync rollback checkpoint files. The dedicated rollback-sync command must
be used to sync rollback checkpoint files.