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

Catalyst 6000 series software configuration guide
Hide thumbs Also See for WS-X6066-SLB-APC - Content Switching Module:
Table of Contents

Advertisement

MSFC Redundancy
Table 22-2
Identical Requirements—
Global and Interface Levels
1. Dynamic and reflexive ACLs, which are based on actual data flow, may be programmed by either MSFC.
2. In addition to defining the same ACLs on both MSFCs, you must also apply the ACLs to the same VLAN interfaces, in the
3. The IP or IPX addresses do not have to be identical on both MSFCs, but there
For information on specifying alternate configurations for the interface and global level exceptions
listed in
Redundant supervisor engines must have identical hardware (MSFC and PFC). See the
Software Requirements" section on page 22-19
For MSFC and MSFC2 memory requirements, refer to the Release Notes for MSFC publication:
Note
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/index.htm
Routing Protocol Peering
In a redundant supervisor engine and dual MSFC configuration, one supervisor engine is fully
operational (active) and the other supervisor engine is in standby mode; however, both MSFCs are
operational (in terms of programming the PFC on the active supervisor engine) and act as independent
routers.
PFC: With the PFC, MLS entries can be associated with either MSFC (based on which MSFC routed
Note
the first packet). Only the PFC on the active supervisor engine switches the packets.
PFC2: With PFC2, only the designated MSFC programs the forwarding information base (FIB) the
Note
adjacency table, Cisco IOS software, and policy routing ACLs on the active supervisor engine. If you
configure static routes or policy routing, you must have the identical configuration on both MSFCs.
If you have a static route on the nondesignated MSFC that is not on the designated MSFC, that route
will not be programmed in the PFC2.
Catalyst 6000 Family Software Configuration Guide—Releases 6.3 and 6.4
22-20
Single Chassis Layer 3-Redundancy Requirements
Both MSFCs must have the
following:
Same routing protocols
Same static routes
Same default routes
Same policy routes
Same VLAN interfaces
1, 2
Same IOS ACLs
All interfaces must have the
same administrative status
same direction, on both MSFCs.
both MSFCs.
Table
22-2, see the
"alt Keyword Usage" section on page
Exceptions—Interface Level
HSRP standby commands
IP address commands
3
IPX network
for more information.
Chapter 22
Configuring Redundancy
Exceptions—Global Level
IP default-gateway
3
IPX internal-network
IPX default-route
must
be an IP or IPX address configured on
22-33.
"Hardware and
78-13315-02

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents