redundancy
admin
config
7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE: standalone-VC
Commands in this context configure redundancy operations.
rollback-sync
admin>redundancy
7210 SAS-R6 and 7210 SAS-R12
This command copies the entire set of rollback checkpoint files from the active CPM CF to the inactive CPM CF.
synchronize {boot-env | config}
admin>redundancy
7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone-VC)
This command performs a synchronization of the standby CPM’s images and/or configuration files to the active CPM. Either the boot-env or config parameter must be specified.
In the admin>redundancy context, this command performs a manually triggered standby CPM synchronization. When the standby CPM takes over operation following a failure or reset of the active CPM, it is important to ensure that the active and standby CPM have identical operational parameters. This includes the saved configuration, CPM and XCMIOM images.
The active CPM ensures that the active configuration is maintained on the standby CPM. 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. If synchronization fails, alarms and log messages that indicate the type of error that caused the failure of the synchronization operation are generated. When the error condition ceases to exist, the alarm is cleared.
Only files stored on the router are synchronized. If a configuration file or image is stored in a location other than on a local compact flash, the file is not synchronized; for example, storing a configuration file on an FTP server.
The no form of this command removes the parameter from the configuration.
Keyword to synchronize all files required for the boot process (loader, BOF, images, and config).
Keyword to synchronize only the primary, secondary, and tertiary configuration files.
display-config [detail | index]
admin
Supported on all 7210 SAS platforms as described in this document
This command displays the system’s running configuration.
By default, only non-default settings are displayed.
Displays default and non-default configuration parameters.
Displays only persistent-indexes.
force-switchover [now]
admin>redundancy
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC
This command forces a switchover to the standby CPM/CFM card. The primary CPM/CFM reloads its software image and becomes the secondary CPM/CFM.
Keyword to force the switchover to the redundant CPM/CFM card immediately.
switchover-exec file-url
no switchover-exec
config>system
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC
This command specifies the location and name of the CLI script file executed following a redundancy switchover from the previously active CPM/CFM card. A switchover can happen because of a fatal failure or by manual action.
The CLI script file can contain commands for environment settings, debug (excluding mirroring settings), and other commands not maintained by the configuration redundancy.
The following commands are not supported in the switchover-exec file: clear, configure, candidate, oam, tools, oam, ping, traceroute, mstat, mtrace and mrinfo.
If the file-url parameter is not specified, no CLI script file is executed.
Specifies the location and name of the CLI script file.
[no] rollback-sync
config>redundancy
7210 SAS-R6 and 7210 SAS-R12
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.
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.
synchronize {boot-env | config}
no synchronize
config>redundancy
7210 SAS-R6 and 7210 SAS-R12
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.
If synchronization fails, alarms and log messages that indicate the type of error that caused the failure of the synchronization operation are generated. When the error condition ceases to exist, the alarm is cleared.
Only files stored on the router are synchronized. If a configuration file or image is stored in a location other than on a local compact flash, the file is not synchronized; for example, storing a configuration file on an FTP server.
The no form of this command removes the parameter from the configuration.
config
Keyword to synchronize all files required for the boot process (loader, BOF, images, and config).
Keyword to synchronize only the primary, secondary, and tertiary configuration files.
multi-chassis
config>redundancy
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure multi-chassis parameters.
peer-name name
no peer-name
config>redundancy>multi-chassis>peer
Supported on all 7210 SAS platforms as described in this document
This command specifies a peer name.
Specifies the peer name, up to 32 characters. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
source-address ip-address
no source-address
config>redundancy>multi-chassis>peer
Supported on all 7210 SAS platforms as described in this document
This command specifies the source address used to communicate with the multi-chassis peer.
Specifies the source address used to communicate with the multi-chassis peer.
[no] sync
config>redundancy>multi-chassis>peer
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure synchronization parameters.
[no] igmp
config>redundancy>multi-chassis>peer>sync
Supported on all 7210 SAS platforms as described in this document
This command specifies whether IGMP protocol information should be synchronized with the multi-chassis peer.
no igmp
[no] igmp-snooping
config>redundancy>multi-chassis>peer>sync
Supported on all 7210 SAS platforms as described in this document
This command specifies whether IGMP snooping information should be synchronized with the multi-chassis peer.
no igmp-snooping
port port-id [sync-tag sync-tag] [create]
no port port-id
config>redundancy>multi-chassis>peer>sync
Supported on all 7210 SAS platforms as described in this document
This command specifies the port to be synchronized with the multi-chassis peer and a synchronization tag to be used while synchronizing this port with the multi-chassis peer.
Specifies the port to be synchronized with the multi-chassis peer.
Specifies a synchronization tag, up to 32 characters, to be used while synchronizing this port with the multi-chassis peer.
Keyword to create an entry.
range encap-range sync-tag sync-tag
no range encap-range
config>redundancy>multi-chassis>peer>sync>port
Supported on all 7210 SAS platforms as described in this document
This command configures a range of encapsulation values.
Specifies a range of encapsulation values on a port to be synchronized with a multi-chassis peer.
Specifies a synchronization tag, up to 32 characters, to be used while synchronizing this encapsulation value range with the multi-chassis peer.