Cisco Catalyst 4500 Series, Руководство по настройке программного обеспечения

Страница: 507 / 2086

11-5
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 11 Configuring Supervisor Engine Redundancy Using RPR and SSO on Supervisor Engine 6-E and Supervisor
Supervisor Engine Redundancy Guidelines and Restrictions
When a redundant supervisor engine is running in RPR mode, the following events trigger
synchronization of the configuration information:
• When the redundant supervisor engine boots, the auto-sync command synchronizes the persistent
configuration. This command is enabled by default. For details, refer to “Synchronizing the
Supervisor Engine Configurations” section on page 11-11 .
•
When the active supervisor engine detects the redundant supervisor engine, the configuration
information is synchronized from the active supervisor engine to the redundant supervisor engine.
This synchronization overwrites any existing startup configuration file on the redundant supervisor
engine.
• When you make changes to the configuration, you must use the write command to save and
synchronize the startup configuration of the redundant supervisor engine.
SSO Supervisor Engine Configuration Synchronization
When a redundant supervisor engine runs in SSO mode, the following events trigger synchronization of
the configuration information:
• When the active supervisor detects the redundant supervisor engine, synchronization of the
persistent and running configuration takes place, allowing the redundant supervisor engine to arrive
at a fully-initiated state.
•
When real-time changes occur, the active supervisor engine synchronizes the running-config and
(or) the persistent configuration (if necessary) with the redundant supervisor engine.
• When you change the configuration, you must use the write command to allow the active supervisor
engine to save and synchronize the startup configuration of the redundant supervisor engine.
Supervisor Engine Redundancy Guidelines and Restrictions
The following guidelines and restrictions apply to supervisor engine redundancy:
•
If SSO mode cannot be established between the active and standby supervisor engines because of
an incompatibility in the configuration file, a mismatched command list (MCL) is generated at the
active supervisor engine and a reload into RPR mode is forced for the standby supervisor engine.
Subsequent attempts to establish SSO, after removing the offending configuration and rebooting the
standby supervisor engine with the exact same image, might cause the
C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL and
ISSU-3-PEER_IMAGE_INCOMPATIBLE messages to appear because the peer image is listed as
incompatible. If the configuration problem can be corrected, you can clear the peer image from the
incompatible list with the
redundancy config-sync ignore mismatched-commands EXEC
command while the peer is in a standby cold (RPR) state. This action allows the standby supervisor
engine to boot in standby hot (SSO) state when it reloads.
Here are the steps:
Step 1 Clear the offending configuration (that caused an MCL) while the standby supervisor engine is in
standby cold (RPR) state.
Step 2
Enter the redundancy config-sync ignore mismatched-commands EXEC command at the active
standby supervisor engine.
Step 3 Perform write memory .