Supervisor Engine Configuration Synchronization; Supervisor Engine Redundancy Guidelines And Restrictions; Redundancy Guidelines And Restrictions; Hardware Configuration Guidelines And Restrictions - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Chapter 6 Configuring RPR Supervisor Engine Redundancy

Supervisor Engine Configuration Synchronization

Configuration changes made through SNMP are not synchronized to the redundant supervisor engine.
Note
After you configure the switch through SNMP, copy the running-config file to the startup-config file on
the active supervisor engine to trigger synchronization of the startup-config file on the redundant
supervisor engine.
During RPR mode operation, the startup-config files and the config-register configurations are
synchronized by default between the two supervisor engines. In a switchover, the new active supervisor
engine uses the current configuration.

Supervisor Engine Redundancy Guidelines and Restrictions

These sections describe supervisor engine redundancy guidelines and restrictions:
•
•
•

Redundancy Guidelines and Restrictions

These guidelines and restrictions apply to RPR redundancy modes:
•
•
•
•

Hardware Configuration Guidelines and Restrictions

For redundant operation, the following guidelines and restrictions must be met:
•
•
•
OL-11439-03
Redundancy Guidelines and Restrictions, page 6-3
Hardware Configuration Guidelines and Restrictions, page 6-3
Configuration Mode Restrictions, page 6-4
When a redundant supervisor engine is in standby mode, the two Gigabit Ethernet interfaces on the
redundant supervisor engine are always active.
Supervisor engine redundancy does not provide supervisor engine mirroring or supervisor engine
load balancing. Only one supervisor engine is active.
Configuration changes made through SNMP are not synchronized to the redundant supervisor
engine. After you configure the switch through SNMP, copy the running-config file to the
startup-config file on the active supervisor engine to trigger synchronization of the startup-config
file on the redundant supervisor engine .
Supervisor engine switchover takes place after the failed supervisor engine completes a core dump.
A core dump can take up to 15 minutes. To get faster switchover time, disable core dump on the
supervisor engines.
Cisco IOS running on the supervisor engine and the PISA supports redundant configurations where
the supervisor engines and PISA routers are identical. If they are not identical, one will boot first
and become active and hold the other supervisor engine and PISA in a reset condition.
Each supervisor engine must have the resources to run the switch on its own, which means all
supervisor engine resources are duplicated, including all Flash devices.
Make separate console connections to each supervisor engine. Do not connect a Y cable to the
console ports.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
Supervisor Engine Redundancy Guidelines and Restrictions
6-3