Table of Contents
Release Notes for Catalyst 6000 Family MSFC for Cisco IOS Release 12.1(2)E
June 26, 2000
 |
Caution Use this publication if you are running Catalyst software on the supervisor engine and Cisco IOS Release 12.1(2)E on the Multilayer Switch Feature Card (MSFC). If you are using the Cisco IOS on the Catalyst 6000 Family Switches product, which runs Cisco IOS on both the supervisor engine and the MSFC, refer to the Release Notes for Catalyst 6000 Family for Cisco IOS publication: http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/index.htm |
- In these Release Notes, the term "MSFC" refers to either an MSFC2 or an MSFC1, except when specifically differentiated.
- The most current Release Notes for 12.1(2)E are available on Cisco Connection Online:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/78_11048.htm
The online documents may contain updates and modifications made after the hard-copy versions were printed.
- This publication describes the features, modifications, and caveats for Release 12.1(2)E on the Catalyst 6000 family MSFC. These release notes are applicable to Release 12.1(2)E. For features, modifications, and caveats for the Catalyst 6000 family supervisor engine software, refer to the Release Notes for Catalyst 6000 Family Software Release 5.x publication:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/index.htm
- The MSFC ships with Cisco IOS software installed. For Release 12.1(2)E:
- With an MSFC2, ensure that the Catalyst 6000 family supervisor engine is running supervisor engine software release 5.4(3) or later.
- With an MSFC1, ensure that the Catalyst 6000 family supervisor engine is running supervisor engine software release 5.4(1) or later.
- Software images are also available through Cisco Connection Online (CCO).
This publication consists of these sections:
Cisco IOS Release 12.1(2)E supports the Catalyst 6000 family MSFC router daughtercard, and includes images that support the FlexWAN module.
Release 12.1(2)E is based on Release 12.1(1). All functionality in Release 12.1(1) is also in Release 12.1(2)E. Release 12.1(2)E will eventually be merged into 12.1 T. All features and functionality in Releases 12.0 XE, 12.1(1)EX, and Release 12.1(1)E are in Release 12.1(2)E.
For information on Release 12.0(7)XE1, see the Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.0 XE on CCO:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios127xe/78_10404.htm
or the Documentation CD-ROM.
For information on Release 12.1(1)EX, see the Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.1 EX on CCO:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/78_10744.htm
or the Documentation CD-ROM.
For information on Release 12.1, see the Cross-Platform Release Notes for Cisco IOS Release 12.1 on CCO:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/xprn121/index.htm
and the Documentation CD-ROM.
For more information about the Cisco IOS software release process, refer to Cisco IOS Software Releases: Product Bulletin 537 located on the Documentation CD-ROM and on CCO:
http://www.cisco.com/warp/public/cc/cisco/mkt/ios/rel/prodlit/537_pp.htm
These release notes do not describe features that are available in Release 12.1, Release 12.1 T, or other Release 12.1 Early Deployment (ED) releases.
All caveats in Release 12.1(1), Release 12.0 XE, and Release 12.1(1)E are also in Release 12.1(2)E. For a list of the software caveats that apply to Release 12.1(2)E, see the "Caveats" section, the Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.0 XE on CCO (link shown above) and the Caveats for Cisco IOS Release 12.1 document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/121cavs/121mcavs.htm
that accompany these release notes.
This section describes the system requirements for Release 12.1(2)ES:
Release 12.1(2)E requires the following memory configurations:
- MSFC2The default memory configurations are acceptable:
- 128-MB synchronous dynamic random-access memory (SDRAM) DIMM
- 16-MB Flash SIMM
- MSFC1The default memory configurations are acceptable:
- 64-MB synchronous dynamic random-access memory (SDRAM) DIMM
- 16-MB Flash SIMM
- Supervisor Engine 1The default memory configurations are acceptable:
- 64-MB SDRAM DIMM
- 16-MB Flash SIMM
 |
Note While 64 MB is the minimum acceptable MSFC1 DRAM configuration, we recommend 128MB of DRAM for most applications. |
Product Number
(append with "=" for spares)
| Product Description
| Minimum Software Version
| Recommended Software Version
|
| MSFC1/MSFC2 on Supervisor Engine 1
|
WS-X6K-S1A-MSFC2 or WS-F6K-MSFC2=
| Multilayer Switch Feature Card 2 (MSFC2) on Supervisor Engine 1 with Policy Feature Card (PFC)
| 12.1(2)E
| 12.1(2)E
|
WS-X6K-SUP1A-MSFC
| Multilayer Switch Feature Card (MSFC1) on Supervisor Engine 1 with Policy Feature Card (PFC)
| 12.0(7)XE1
| 12.1(1)E
|
| FlexWan Module
|
WS-X6182-2PA
| FlexWAN Module
Port adapters:
- Packet over Sonet (OC-3):
PA-POS-OC3MM PA-POS-OC3SMI PA-POS-OC3SML
- ATM (with traffic shaping):
PA-A3-OC3MM PA-A3-OC3SMI PA-A3-T3 PA-A3-OC3SML PA-A3-E3
- T3/E3 (clear-channel and channelized):
PA-T3 PA-T3+ PA-2T3 PA-2T3+ PA-E3 PA-2E3 PA-MC-T3 PA-MC-E3
- T1/E1:
PA-4T+ PA-8T-V35 PA-8T-X21 PA-8T-232 PA-MC-8T1 PA-MC-8E1/120
- HSSI:
PA-H PA-2H
| 12.1(1)E
| 12.1(2)E
|
 |
Note EGP, BGP4 and IS-IS routing protocols require the additional purchase of the InterDomain Routing Feature License (FR-IRC6). |
| Feature Set
| Image Filename
| Orderable Product Number1
|
IOS Release 12.1(2)E Enterprise:
- Wire speed Layer 2 switching (bridging)
- Wire speed Layer 3 switching (routing) for IP (routing protocols include RIPv1, RIPv2, OSFP, IGRP, EIGRP, EGP, BGP4, and IS-IS)
- Wire speed Layer 3 switching (routing) for IPX
- AppleTalk Phase 1/2, DECnet Phase IV, and VINES routing
- DECnet Phase V and CLNS/OSI routing
| MSFC2: c6msfc2-js-mz.121-2.E.bin
| SC6MSFC2A-12102E
|
MSFC2 and FlexWAN: c6msfc2-jsv-mz.121-2.E.bin
| SC6MSFC2AV-12102E
|
MSFC1: c6msfc-js-mz.121-2.E.bin
| SC6MSFCA-12102E
|
MSFC1 and FlexWAN: c6msfc-jsv-mz.121-2.E.bin
| SC6MSFCAV-12102E
|
IOS Release 12.1(2)E Desktop:
- Wire speed Layer 2 switching (bridging)
- Wire speed Layer 3 switching (routing) for IP (routing protocols include RIPv1, RIPv2, OSFP, IGRP, EIGRP, EGP, BGP4, and IS-IS)
- Wire speed Layer 3 switching (routing) for IPX
- AppleTalk Phase 1/2, and DECnet Phase IV routing
| MSFC2: c6msfc2-ds-mz.121-2.E.bin
| SC6MSFC2B-12102E
|
MSFC2 and FlexWAN: c6msfc2-dsv-mz.121-2.E.bin
| SC6MSFC2BV-12102E
|
MSFC1: c6msfc-ds-mz.121-2.E.bin
| SC6MSFCB-12102E
|
MSFC1 and FlexWAN: c6msfc-dsv-mz.121-2.E.bin
| SC6MSFCBV-12102E
|
IOS Release 12.1(2)E IP:
- Wire speed Layer 2 switching (bridging)
- Wire speed Layer 3 switching (routing) for IP (routing protocols include RIPv1, RIPv2, OSFP, IGRP, EIGRP, EGP, and BGP4)
| MSFC2: c6msfc2-is-mz.121-2.E.bin
| SC6MSFC2C-12102E
|
MSFC2 and FlexWAN: c6msfc2-isv-mz.121-2.E.bin
| SC6MSFC2CV-12102E
|
MSFC1: c6msfc-is-mz.121-2.E.bin
| SC6MSFCC-12102E
|
MSFC1 and FlexWAN: c6msfc-isv-mz.121-2.E.bin
| SC6MSFCCV-12102E
|
IOS Release 12.1(2)E IP/IPX:
- Wire speed Layer 2 switching (bridging)
- Wire speed Layer 3 switching (routing) for IP (routing protocols include RIPv1, RIPv2, OSFP, IGRP, EIGRP, EGP, BGP4, and IS-IS)
- Wire speed Layer 3 switching (routing) for IPX
| MSFC2: c6msfc2-ds-mz.121-2.E.bin
| SC6MSFC2D-12102E
|
MSFC2 and FlexWAN: c6msfc2-dsv-mz.121-2.E.bin
| SC6MSFC2DV-12102E
|
MSFC1: c6msfc-ds-mz.121-2.E.bin
| SC6MSFCD-12102E
|
MSFC1 and FlexWAN: c6msfc-dsv-mz.121-2.E.bin
| SC6MSFCDV-12102E
|
MSFC2 boot loader
| c6msfc-boot2-mz.121-2.E.bin
| N/A
|
MSFC1 boot loader (available, but not required to support 12.1(2)E)
| c6msfc-boot-mz.121-2.E.bin
| N/A
|
1Installed on System; append with "=" for spare on floppy media
|
This section describes the new and changed information for the Catalyst 6000 MSFC:
Initial support of the WS-F6K-MSFC2.
 |
Note With an MSFC2, ensure that the Catalyst 6000 family supervisor engine is running supervisor engine software release 5.4(3) or later. |
None.
None.
Initial support of the WS-X6182-2PA FlexWAN module.
None.
None.
None.
Initial support of the MSFC1 on the Catalyst 6000 Family switches.
 |
Note Release 12.1(2)E on MSFC2 supports configuration of up to 1000 VLAN interfaces. |
The Local Proxy ARP feature allows the MSFC to respond to ARP requests for IP addresses within a subnet where normally no routing is required. With the local proxy ARP feature enabled, the MSFC responds to all ARP requests for IP addresses within the subnet and forwards all traffic between hosts in the subnet. Use this feature only on subnets where hosts are intentionally prevented from communicating directly by the configuration on the switch to which they are connected.
The local proxy ARP feature is disabled by default. Use the ip local-proxy-arp interface configuration command to enable the local proxy ARP feature on an interface. Use the no ip local-proxy-arp interface configuration command to disable the feature. ICMP redirects are disabled on interfaces where the local proxy ARP feature is enabled.
The WCCP Layer 2 PFC Redirection feature allows directly connected Cisco Cache Engines to use Layer 2 redirection, which is more efficient than Layer 3 redirection via GRE encapsulation. A directly connected Cache Engine can be configured to negotiate use of the WCCP Layer 2 PFC Redirection feature. The WCCP Layer 2 PFC Redirection feature requires no configuration on the MSFC. The show ip wccp web-cache detail command displays which redirection method is in use for each cache. Observe the following guidelines:
- Use of the WCCP Layer 2 PFC Redirection feature sets the IP flow mask to full-flow mode.
- Cisco Cache Engine software version 2.2 or later can be configured to use the WCCP Layer 2 PFC Redirection feature.
- Layer 2 redirection takes place on the switch and is not visible to the MSFC. The show ip wccp web-cache detail command on the MSFC displays statistics for only the first packet of a Layer 2 redirected flow, which provides an indication of how many flows, rather than packets, are using Layer 2 redirection. The display from the show mls entries command on the supervisor engine includes the other packets in Layer 2 redirected flows.
Configure the Cisco IOS Web Cache Communication Protocol (WCCP) as described in the Cisco IOS Configuration Fundamentals Configuration Guide, under "Configuring Web Cache Services Using WCCP", at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/fun_c/fcprt3/fcd305.htm
With an MSFC2, you can configure the MTU size on VLAN interfaces to support routing of jumbo frames.
The jumbo frame feature supports only a single larger-than-default MTU size on the switch. Configuring a VLAN interface with an MTU size greater than the default automatically configures all other VLAN interfaces that have an MTU size greater than the default to the newly configured size. VLAN interfaces that have not been changed from the default are not affected.
To configure the MTU value, perform this task:
| Step
| Command
| Purpose
|
1.
| Router(config)# interface vlan vlan_ID
| Access VLAN interface configuration mode.
|
2.
| Router(config-if)# mtu mtu_size
| Set the MTU size. Valid values are from 64 to 17952 bytes.
NoteSet the MTU size no larger than 9216, which is the size supported by the supervisor engine.
|
3.
| Router# show interface vlan 111
| Verify the configuration.
|
This example shows how to set the MTU size on a VLAN interface and verify the configuration:
Router(config)# interface vlan 111
Router(config-if)# mtu 9216
Router(config-if)# end
Router# show interface vlan 111
<...Output Truncated...>
MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec,
<...Output Truncated...>
Router#
Configure support for junbo frames on the supervisor engine as described in the "Configuring Ethernet, Fast Ethernet, and Gigabit Ethernet Switching" chapter of the Catalyst 6000 Family Software Configuration Guide.
None.
The ARP on STP Topology Change Notification feature ensures that excessive flooding does not occur when the MSFC receives a topology change notification (TCN) from the supervisor engine. The feature causes the MSFC to send ARP requests for all the ARP entries belonging to the VLAN interface where the TCN is received. When the ARP replies come back, the PFC learns the MAC entries, which were lost as a result of the topology change. Learning the entries immediately following a topology change prevents excessive flooding later.
There is no configuration required on the MSFC. This feature works with supervisor engine software 5.4(2) or later.
RGMP constrains multicast traffic that exits through ports to which disinterested multicast routers are connected. To effectively constrain traffic, RGMP must be supported on both the switches and the routers in the network.
 |
Note CGMP and IGMP snooping constrain multicast traffic that exits through switch ports to which hosts are connected. They do not constrain traffic that exits through ports to which one or more multicast routers are connected. |
Restrictions
The following restrictions apply to RGMP on the MSFC:
- RGMP supports PIM sparse-mode only. RGMP does not support PIM dense-mode. RGMP explicitly supports the two AutoRP groups in dense-mode by not restricting traffic to those groups but by flooding it to all router ports. For this reason, you should configure PIM sparse-dense-mode. If you configure groups other than the AutoRP groups for dense-mode, their traffic will not be correctly forwarded through router ports that have been enabled for RGMP.
- IGMP snooping must be enabled on the switch.
- To effectively constrain multicast traffic with RGMP, connect RGMP-enabled routers to separate ports on RGMP-enabled switches.
- RGMP only constrains traffic that exits through ports on which it detects an RGMP-enabled router. If a non-RGMP enabled router is detected on a port, that port receives all multicast traffic.
- RGMP does not support directly connected sources in the network. A directly connected source will send traffic into the network without signaling this through RGMP or PIM. This traffic will not be received by an RGMP-enabled router unless the router already requested receipt of that group through RGMP. This restriction applies to hosts and to functions in routers that source multicast traffic, such as the ping and mtrace commands and multicast applications that source multicast traffic, such as UDPTN.
- RGMP supports directly connected receivers in the network.Traffic to these receivers will be restricted by IGMP snooping, or if the receiver is a router itself, by PIM and RGMP. CGMP is not supported in networks where RGMP is enabled on routers. Enabling RGMP and CGMP on a router interface is mutually exclusive. If RGMP is enabled on an interface, CGMP is silently disabled or vice versa.
- The following properties of RGMP are the same as for IGMP snooping:
- RGMP restricts traffic based on the multicast group, not on the sender's IP address.
- If spanning tree topology changes occur in the network, the state is not flushed as it is with CGMP.
- RGMP does not restrict traffic for the multicast groups 224.0.0.x (x = 0...255), allowing PIMv2 BSR to be used in an RGMP-controlled network.
- RGMP in Cisco switches operates on MAC addresses, not on the IP multicast addresses. As more than one IP multicast addresses are mapped to one MAC address (see RFC1112), no restriction of traffic will happen between different IP multicast groups that map to the same MAC address.
- The capability of the switch to restrict traffic is limited by its CAM table capacity.
Configuration Tasks
Refer to the Catalyst 6000 Software Configuration Guide for guidelines on how to configure RGMP on the Catalyst 6000 family switches:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_5_4/index.htm
Step 1 Establish an appropriate topology on the VLANs where you want to use RGMP.
Step 2 Enable RGMP on the switch:
Switch> (enable) set igmp enable
Switch> (enable) set rgmp enable
The first command enables IGMP snooping, the second enables RGMP. Enabling these features on the switch is a global configuration. RGMP has no effect in those VLANs where there is not at least a single router also configured for RGMP.
Step 3 Enable RGMP on each interface that has a topology appropriate for RGMP:
router(config)# vlan-interface 10
router(config-if)# ip rgmp
Step 4 Monitor RGMP on the switch:
Switch> (enable) show rgmp group [<mac_addr>] [<vlan_id>]
Switch> (enable) show rgmp group count [<vlan_id>]
Switch> (enable) show rgmp statistics [<vlan>]
Switch> (enable) clear rgmp statistics
Switch> (enable) show multicast router [igmp|rgmp] [<mod>/<port>] [<vlan_id>]
Switch> (enable> show multicast protocol status
Step 5 Monitor RGMP on the MSFC:
router(enable)# debug ip rgmp [<name-or-group_address>]
- IOS Release 12.0(7)XE1 supports the High Availability feature in supervisor engine software release 5.4(1) and later. There are no IOS commands or configuration required on the MSFC for the High Availability feature.
- IOS Release 12.0(7)XE1 supports the private VLAN (PVLAN) feature in supervisor engine software release 5.4(1) and later.
- Use the show pvlan command to display information about PVLANs.
- The show pvlan command displays information about PVLANs only when the primary PVLAN is up.
- Entry of set pvlan mapping or clear pvlan mapping commands on the supervisor engine generates MSFC syslog messages. For example:
%PV-6-PV_MSG:Created a private vlan mapping, Primary 100, Secondary 101
%PV-6-PV_MSG:Created a private vlan mapping, Primary 200, Secondary 201
%PV-6-PV_MSG:Purged a private vlan mapping, Primary 100, Secondary 101
- You can enter the interface vlan command to configure Layer 3 parameters only for primary PVLANs.
- On the supervisor engine, you cannot create isolated or community VLANs using VLAN numbers for which interface vlan commands have been entered on the MSFC.
- ARP entries learned on Layer 3 PVLAN interface are sticky ARP entries (we recommend that you display and verify PVLAN interface ARP entries).
- For security reasons, PVLAN interface sticky ARP entries do not age out. Connecting new equipment with the same IP address generates a message and the ARP entry is not created.
- Since the PVLAN interface ARP entries do not age out, you must manually remove PVLAN interface ARP entries if a MAC address changes.
- You can add or remove PVLAN ARP entries manually. For example:
obelix-rp(config)#no arp 11.1.3.30
IP ARP:Deleting Sticky ARP entry 11.1.3.30
obelix-rp(config)#arp 11.1.3.30 0000.5403.2356 arpa
IP ARP:Overwriting Sticky ARP entry 11.1.3.30, hw:00d0.bb09.266e by hw:0000.5403.2356
- Some commands clear and recreate PVLAN mapping. For example:
obelix-rp(config)#xns routing
obelix-rp(config)#
%PV-6-PV_MSG:Purged a private vlan mapping, Primary 100, Secondary 101
%PV-6-PV_MSG:Purged a private vlan mapping, Primary 100, Secondary 102
%PV-6-PV_MSG:Purged a private vlan mapping, Primary 100, Secondary 103
%PV-6-PV_MSG:Created a private vlan mapping, Primary 100, Secondary 101
%PV-6-PV_MSG:Created a private vlan mapping, Primary 100, Secondary 102
%PV-6-PV_MSG:Created a private vlan mapping, Primary 100, Secondary 103
The features listed below were introduced but not fully tested at wire rate in supervisor engine software release 5.3(1a)CSX and MSFC IOS releases 12.0(3)XE1 and 12.0(3)XE2. They have been fully tested in 5.3(3)CSX and MSFC IOS release 12.0(7)XE and are fully operational.
- IPX MLS at wire rate (software release 5.3(1a)CSX and MFSC IOS release 12.0(7)XE or later does support IPX routing at wire rate)
- IOS IPX ACLs at wire rate (software release 5.3(1a)CSX and MFSC IOS release 12.0(7)XE or later does support standard and extended IOS IPX ACLs at wire rate)
- QoS IPX ACLs
There are no new features in Release 12.0(3)XE2.
Initial support of the MSFC1 on the Catalyst 6000 Family switches: refer to the Catalyst 6000 Family Multilayer Switch Feature Card and Policy Feature Card Configuration Guide
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
- Integrated Routing and Bridging (IRB) and Concurrent Routing and Bridging (CRB) have deliberately been disabled on the Catalyst 6000 family switches. Routable Layer 2 VLANs and VLAN interfaces should be used for normal bridging and inter-VLAN routing. Bridge groups are supported only to bridge non-routable protocols.
- If you are using the Catalyst 6000 family switch to switch thousands of IPX flows which may all arrive in simultaneous bursts, we recommend that you configure the following to avoid excessive CPU load:
Router(config)# ipx route-cache inactivity-timeout 1 100
- The above command sets the IPX cache inactivity-timeout to 1 minute and the maximum invalidations per minute to 100.
- Before you can use a system image stored on the supervisor engine Flash PC card, you must set the BOOTLDR environment variable. In privileged mode, enter the boot bootldr bootflash: boot_loader_image command.
- Data-link switching plus (DLSw+) was mistakenly identified as not being supported in MSFC IOS Release 12.0(3)XE1 and subsequent releases. DLSw+ is supported in 12.0(3)XE1 and subsequent releases.
- Cisco IOS Release 12.0(3)XE1 and subsequent releases support:
- The Web Cache Control Protocol (WCCP) feature, versions 1 and 2
- In addition to the Layer 3 routing protocols listed in the Catalyst 6000 Family MSFC(12.0) & PFC Configuration Guide: Apollo, AppleTalk Routing, DECnet, VINES, and XNS
- At power up or manual reset you must configure the MSFC to boot from its bootflash (or the supervisor engine's Flash PC card; however, bootflash is preferred). When you reset the supervisor engine through either a power up or a manual reset, the MSFC cannot boot from a TFTP server on the network. However, when the supervisor engine is up and the port over which the network is being accessed is in forwarding state, you can boot the MSFC from a TFTP server on the network.
- In a redundant supervisor engine setup, if a specific VLAN interface on one MSFC is shut down, you should manually shut down the corresponding VLAN interface on the other MSFC.
- By default, the MSFC sends Internet Control Message Protocol (ICMP) unreachables when a packet is denied by an access group; these access-group-denied packets are not dropped in hardware but are bridged to the MSFC so it can generate the ICMP-unreachable message. To drop access-group-denied packets in hardware, you must disable ICMP unreachables using the no ip unreachables interface configuration command. Note that the ip unreachables command is enabled by default.
- You can specify the MSFC as the MLS route processor (MLS-RP) for Catalyst 5000 family switches using MLS. Refer to the Layer 3 Switching Configuration GuideCatalyst 5000 Family, 4000 Family, 2926G Series, 2926 Series, 2948G for MLS configuration procedures.
- If one MSFC fails in a system with redundant MSFCs, second hop routers could continue to send traffic to the failed MSFC for a period of time until the second hop router realizes that the MSFC is down.
- HSRP addresses only first hop redundancy; it ensures that the default gateway configured on the clients (workstations) remains up even if one router from the HSRP group goes down.
- HSRP ensures that traffic going from the client through the default gateway to the ultimate destination is supported with the loss of one MSFC.
- The HSRP MAC and IP addresses are never known to the other routers, which means that the reverse traffic from the destination to the originating client may or may not go through the same router. This is especially true if the source and destination are more than one hop away. The second hop router (from the client) will see that the client is reachable through both the MSFCs and through load balancing, and could spread the reverse traffic between the two MSFCs.
- When one MSFC fails, the HSRP detects it fairly fast (10 seconds based on default HSRP settings), which means that traffic from the client to its destination goes through. However, the second hop router has to rely on the routing protocol's (RIP/OSPF) convergence time (from 30 to 90 seconds) to realize that one MSFC is down and will try to send the reverse traffic to the failed MSFC.
- The reverse traffic can flow through either MSFC if the source and destination are more than one hop away.
- NetFlow Data Export (NDE) version 7 is not supported for the MSFC.
- When using the Network Address Translation (NAT) router feature on the MSFC, packets traversing the NAT outside interface might, under certain configurations, be software routed instead of being shortcut, regardless of whether they should or should not be translated. Ideally, for packets traversing the NAT outside interface, you would want only those packets requiring NAT to be software routed. The IOS in software will only translate traffic that is traversing from NAT inside to NAT outside interfaces and vice versa.
- By making the ACL used for NAT more specific, you can limit the software-handled packets to only those requiring NAT translation.
- For example, if you use a general ACL (such as permit ip any any) to specify the traffic that requires NAT, then all traffic inbound or outbound on the NAT outside interface will be software routed (including traffic not originating or destined to NAT inside interfaces). If it is possible to use a more specific ACL (such as permit ip 10.1.1.0 0.0.0.255 any), then only the NAT outside traffic matching that ACL will be software routed. This traffic will still be software routed regardless of whether it is originating or destined to NAT inside interfaces. By making the ACL more specific, you can limit the amount of traffic that is software routed due to the NAT ACL.
- ACL configuration guidelines: When configuring ACLs on an interface with the configuration command tcam priority {high | low | normal}, entering high Ternary Content Addressable Memory (TCAM) priority gives ACLs on that interface priority for getting into the TCAM over ACLs of interfaces with lower (low or normal) priority.
- If the ACLs on an interface with high priority do not fit in the TCAM, the ACLs for interfaces of lower priority will not be inserted into the TCAM until it is possible to fit the high-priority ACLs into the TCAM.
- You can configure VLAN access control lists (VACLs) on the switch to apply to all packets that are routed into or out of a VLAN, or are bridged within a VLAN. VACLs are strictly for security packet filtering and redirecting traffic to specific physical switch ports. Unlike IOS ACLs, VACLs are not defined by direction (input or output).
- Refer to the Catalyst 6000 Family Multilayer Switch Feature Card and Policy Feature Card Configuration Guide for detailed information.
- MAC address-based IOS ACLs are not supported for packets shortcut in hardware. MAC address-based IOS ACLs will be applied on software-switched packets. MAC address-based access control can be supported in hardware for non-IP/IPX packets using VACLs. We recommend that you use VACLs to do MAC-addressed-based ACLs.
- Broadcast-to-multicast translation used with the multicast helper command does not work if a flow is hardware switched.
- If TFTP downloads (net boots) are timing out, use the following IOS global configuration command for TFTP booting:
ip tftp boot-interface tftp_interface
- where tftp_interface is the interface the TFTP boot server is on.
- If you enable multicast routing globally, then you should also enable multicast routing (using the ip pim command) on all Layer3 interfaces on which you anticipate receiving IP multicast traffic. This causes the packets to be sent to the process switching level for creating the route entry. However, if you disable multicast routing on the RPF interface, the entry cannot be created and the packet is dropped. Exceeding the source-traffic rate that can be handled by the process level can have an undesirable impact on the system. For instance, HSRP timers can expire on a standby router and cause HSRP flapping.
- Delivery acknowledgment timeouts might occur:
SCP-4-DACK_TIMEOUT_MSG:SCP delivery ack timeout for opcode=118
- When a delivery acknowledgment timeout occurs for opcode 118 (i.e. multicast MLS SCP messages), then the impact depends on whether MMLS is in IDLE or ACTIVE state (can be determined by entering the show mls ip multicast statistics command). If MMLS is ACTIVE, the message is only a warning and can be ignored. If MMLS is IDLE, this message displays:
Multicast MLS is disabled due to internal messaging error
- The feature is disabled on the MSFC. You must disable and reenable the IGMP feature on the NMP before reenabling MMLS on the MSFC.
- After enabling PIM on an interface, you need to enter the ip mroute-cache command on the interface to enable multicast fast-switching. If you have "no ip mroute-cache" configured, multicast packets that are not hardware switched will go to a process level. This process increases the load on the router. Software fast-switching is useful for flows that can only be partially hardware switched.
- FlexWAN module support for switches with redundant supervisor engines will be in a future software release. The FlexWAN module does not support switches with redundant supervisor engines with Release 12.1(2)E.
- FlexWAN module support for IPX MLS will be in a future software release. The FlexWAN module does not support IPX MLS with Release 12.1(2)E.
- MSFC Caveats:
- FlexWAN Module Caveats:
- On a switch with redundant MSFCs configured for PIM sparse mode and auto RP discovery, one of the MSFCs might age out the RP, but eventually relearns it. (CSCdr63601)
- The IPX rip-response-delay interface command does not work on an MSFC, which prevents configuration of preferred routes with this command. (CSCdr45398)
- Under heavy switching loads, process level activity can be delayed. Enter a scheduler allocate command to guarantee adequate process level cycles. (CSCdp90088)
- Entering the no ip routing command does not generate a purge request.
- The MSFC does not send a global purge request to the supervisor engine NMP the first time you enter the no ip routing command on the MSFC after a reload. IP traffic continues to be switched by the NMP even after the MSFC is configured with no ip routing.
- Workaround: Issuing the ip routing command followed by the no ip routing command a second time sends a global purge message to the NMP which purges shortcuts on the supervisor engine NMP. (CSCdm91663)
- When a redundant MSFC comes up, an incorrect inventory message might be received after the Feature Manager is spawned. As a result, an incorrect module ID is used to communicate to the other MSFC. This is an intermittent bug. This problem corrects itself and the message can be ignored. (CSCdp56663, CSCdm72599)
If you lose the boot loader image, please refer to the following link for boot loader image recovery procedures:
http://www.cisco.com/warp/customer/473/14.html
The following sections describe the documentation available for the MSFC on Catalyst 6000 family switches. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents. Documentation is available as printed manuals or electronic documents.
Use these release notes with these documents:
The following documents are specific to Release 12.1 and are located on CCO and the Documentation CD-ROM:
- Cross-Platform Release Notes for Cisco IOS Release 12.1
- On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/xprn121/index.htm
- On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Release Notes: Cross-Platform Release Notes
- Product bulletins, field notices, and other release-specific documents on CCO at:
Technical Documents
- Caveats for Cisco IOS Release 12.1
- As a supplement to the caveats listed in the "Caveats" section, see the Caveats for Cisco IOS Release 12.1 document.
- On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
- On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Caveats
 |
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, go to CCO and press Login. Then go to Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go to http://www.cisco.com/support/bugtools. |
- For earlier versions: Release Notes for Catalyst 6000 Family Multilayer Switch Feature Card Cisco IOS Release 12.0 XE
- On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Catalyst 6000 Family Multilayer Switches: Release Notes for Cisco IOS Release 12.0 XE : Release Notes for MSFC IOS Release 12.0
- On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Release Notes: Catalyst 6000 Family Multilayer Switches: Release Notes for Cisco IOS Release 12.0 XE : Release Notes for MSFC IOS Release 12.0
The following documents are available for the MSFC on the Catalyst 6000 family switches:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
- Catalyst 6000 Family FlexWAN Module Installation and Configuration Note
- Catalyst 6000 Family Multilayer Switch Feature Card & Policy Feature Card Configuration Guide
- Catalyst 6000 Family Software Configuration Guide
- Catalyst 6000 Family Command Reference publication
Feature modules describe new features supported by Release 12.1(1) and are an update to the Cisco IOS documentation set.
A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online on CCO or the documentation CD-ROM. The feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation
On the Documentation CD-ROM:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: New Feature Documentation: New Features in Release 12.1
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that are shipped with your order in electronic form on the Documentation CD-ROMunless you specifically ordered the printed versions.
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. You can use each configuration guide in conjunction with its corresponding command reference.
On CCO and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
On the Documentation CD-ROM:
Cisco Products Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1: Configuration Guides and Command References
The following table describes the contents of the Cisco IOS Release 12.1 software documentation set, which is available in electronic form and in printed form ordered.
 |
Note You can find the most current Cisco IOS documentation on CCO and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed. |
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.1
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.1
| Books
| Major Topics
|
- Cisco IOS Configuration Fundamentals Configuration Guide
- Cisco IOS Configuration Fundamentals Command Reference
| Cisco IOS User Interfaces Cisco IOS File Management Cisco IOS System Management
|
- Cisco IOS Bridging and IBM Networking Configuration Guide
- Cisco IOS Bridging and IBM Networking Command Reference, Volume I
- Cisco IOS Bridging and IBM Networking Command Reference, Volume II
| Using Cisco IOS Software Overview of SNA Internetworking Bridging IBM Networking
|
- Cisco IOS Dial Services Configuration Guide: Terminal Services
- Cisco IOS Dial Services Configuration Guide: Network Services
- Cisco IOS Dial Services Command Reference
| Preparing for Dial Access Modem Configuration and Management ISDN and Signalling Configuration PPP Configuration Dial-on-Demand Routing Configuration Dial-Backup Configuration Terminal Service Configuration Large-Scale Dial Solutions Cost-Control Solutions Virtual Private Networks X.25 on ISDN Solutions Telco Solutions Dial-Related Addressing Services Interworking Dial Access Scenarios
|
- Cisco IOS Interface Configuration Guide
- Cisco IOS Interface Command Reference
| Interface Configuration Overview Configuring LAN Interfaces Configuring Serial Interfaces Configuring Logical Interfaces
|
- Cisco IOS IP and IP Routing Configuration Guide
- Cisco IOS IP and IP Routing Command Reference
| IP Addressing and Services IP Routing Protocols IP Multicast
|
- Cisco IOS AppleTalk and Novell IPX Configuration Guide
- Cisco IOS AppleTalk and Novell IPX Command Reference
| AppleTalk and Novell IPX Overview Configuring AppleTalk Configuring Novell IPX
|
- Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Configuration Guide
- Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Command Reference
| Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Overview Configuring Apollo Domain Configuring Banyan VINES Configuring DECnet Configuring ISO CLNS Configuring XNS
|
- Cisco IOS Multiservice Applications Configuration Guide
- Cisco IOS Multiservice Applications Command Reference
| Multiservice Applications Overview Voice Video Broadband
|
- Cisco IOS Quality of Service Solutions Configuration Guide
- Cisco IOS Quality of Service Solutions Command Reference
| Quality of Service Overview Classification Congestion Management Congestion Avoidance Policing and Shaping Signalling Link Efficiency Mechanisms Quality of Service Solutions
|
- Cisco IOS Security Configuration Guide
- Cisco IOS Security Command Reference
| Security Overview Authentication, Authorization, and Accounting (AAA) Security Server Protocols Traffic Filtering and Firewalls IP Security and Encryption Other Security Features
|
- Cisco IOS Switching Services Configuration Guide
- Cisco IOS Switching Services Command Reference
| Cisco IOS Switching Services Overview Cisco IOS Switching Paths Cisco Express Forwarding NetFlow Switching MPLS Switching Multilayer Switching Multicast Distributed Switching Virtual LANs LAN Emulation
|
- Cisco IOS Wide-Area Networking Configuration Guide
- Cisco IOS Wide-Area Networking Command Reference
| Wide-Area Networking Overview Configuring ATM Configuring Frame Relay Configuring Frame Relay-ATM Interworking Configuring SMDS Configuring X.25 and LAPB
|
- New Features in 12.1-Based Limited Lifetime Releases
- New Features in Release 12.1 T
- Release Notes (Release note and caveat documentation for 12.1-based releases and various platforms)
- Cisco IOS Debug Command Reference
- Cisco IOS Dial Services Quick Configuration Guide
|
|
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
- WWW: www.cisco.com
- Telnet: cco.cisco.com
- Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
- From North America, call 408 526-8070
- From Europe, call 33 1 64 46 40 82
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language
| E-mail Address
|
English
| tac@cisco.com
|
Hanzi (Chinese)
| chinese-tac@cisco.com
|
Kanji (Japanese)
| japan-tac@cisco.com
|
Hangul (Korean)
| korea-tac@cisco.com
|
Spanish
| tac@cisco.com
|
Thai
| thai-tac@cisco.com
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.








Posted: Thu Sep 21 11:57:17 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.