Cisco WS-X6066-SLB-APC - Content Switching Module Software Manual page 520

MSFC Redundancy
Hardware and Software Requirements
To configure Layer 3 redundancy, you must have at least one of the following configurations:
•
•
•
Each MSFC must be running the same release of Cisco IOS software.
Note
Guidelines for Configuring Manual-Mode MSFC Redundancy
Follow these guidelines to configure manual-mode MSFC redundancy:
•
•
Setting both MSFCs to 0x0 is a supported option but requires user intervention in the event the switch
Note
is reset.
•
•
•
Catalyst 6000 Family Software Configuration Guide—Releases 6.3 and 6.4
22-46
A single chassis with two identical supervisor engine daughtercard configurations:
Supervisor Engine 1 with Policy Feature Card (PFC) and MSFC or MSFC2 (both supervisor
–
engines must have the same type of MSFC)
Supervisor Engine 2 with PFC2 and MSFC2
–
Two chassis with a supervisor engine in each—You must have at least one supervisor engine in each
chassis. Each supervisor engine must be equipped with a PFC and an MSFC.
Manual-mode MSFC redundancy requires the following software:
Supervisor engine software release 6.1(3) or later releases and MSFC IOS Release 12.1(7)E or
–
later releases
Supervisor engine software release 5.5.8 or later releases and MSFC IOS Release 12.1(7a)E1
–
or later releases
Because the MSFC switchover is manual, we recommend that you have this feature only in
environments where externally redundant routers are present and where either HSRP is used or some
form of gateway discovery is implemented on hosts.
Ensure that the configuration register on the active MSFC (MSFC-15) is set to 0x2102 and that the
configuration register on the MSFC in ROM-monitor mode (MSFC-16) is set to 0x0. This setting
prevents both MSFCs from becoming active at the same time and allows the active MSFC to come
online after a reset. See the
details on setting the configuration register.
To conserve IP address space and reduce the overall Layer 3 complexity, ensure that configuration
synchronization is disabled on both MSFCs and that all "alt" addresses are removed. If alt addresses
are used, IP address space is not conserved and in cases where link-level peering is present (such as
BGP), the Layer 3 complexity is increased.
When the MSFC in ROM-monitor mode is brought up during a maintenance window, ensure that it
has the exact same configuration as the active MSFC. Follow the configuration guidelines in
Table 22-2 on page 22-20.
During manual-mode MSFC redundancy, high availability should be enabled on the supervisor
engine to keep Layer 2 downtime to a minimum when doing an MSFC switchover. Since high
availability is not compatible with protocol filtering, port security, DVLAN, or GVRP, we
recommend that you disable these features when using manual-mode MSFC redundancy.
"Setting the MSFC Configuration Register" section on page 22-47
Chapter 22 Configuring Redundancy
78-13315-02
for