Datasheet

114
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Limitations and Restrictions
– If you configure more than 16 HSRP groups, this restriction prevents use of the VLAN number
as the HSRP group number.
• A Supervisor Engine 1 must have ROMMON version 5.2(1) or later.
• You must have a boot loader image in an MSFC1 bootflash device to boot successfully. Do not reset
the switch when there is no boot loader image in the MSFC1 bootflash device. If there is no boot
loader image in the MSFC1 bootflash device and the state of the switch does not support the copy
command, see the “Recovering From Loss of the Boot Loader Image” section on page 320.
• The ip multicast rate-limit command is not supported on Catalyst 6500 series switch LAN ports.
For information about policing, refer to the online Catalyst 6500 Series Cisco IOS QoS
Configuration Guide at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios127xe/qos.htm
(CSCds22281)
• Catalyst 6500 series switches and Cisco 7600 Series Routers do not support network booting.
• You can specify a Catalyst 6500 series switch or Cisco 7600 series router as the MLS route
processor (MLS-RP) for Catalyst 5000 family switches using MLS. Refer to the Layer 3 Switching
Configuration Guide—Catalyst 5000 Family, 4000 Family, 2926G Series, 2926 Series, 2948G for
MLS configuration procedures.
• The IP HTTP server feature is disabled by default. Enter the ip http server command to use the
feature.
• For LAN switching modules, the Cisco IOS show controllers command generates no output on a
Catalyst 6500 series switch or Cisco 7600 series router. Enter the show module command instead.
• To avoid the case where all traffic is out of profile, the burst size specified in a QoS policing rule
must be at least as large as the maximum packet size permissible in the traffic to which the rule is
applied.
• When using the NAT router feature on a Catalyst 6500 series switch, packets traversing the NAT
outside interface might in certain configurations be software routed instead of Layer 3 switched,
regardless of whether they should or should not be translated. For packets traversing the NAT
outside interface, only those packets requiring NAT should be software routed. Cisco IOS only
translates traffic that is traversing from NAT inside interfaces to NAT outside interfaces and vice
versa.
Make the ACL used for NAT more specific to limit the software-handled packets to only those
packets 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 the 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 from or destined to NAT inside interfaces.
However, by making the ACL more specific, you can limit the amount of traffic that is software
routed due to the NAT ACL.
• By default, the MSFC sends Internet Control Message Protocol (ICMP) unreachable messages when
a packet is denied by an access group.
With the ip unreachables command enabled (which is the default), the Supervisor Engine 2 drops
most of the denied packets in hardware and sends only a small number of packets (10 packets per
second, maximum) to the MSFC2 to be dropped, which generates ICMP-unreachable messages.
With the ip unreachables command enabled, the Supervisor Engine 1 sends all the denied packets
to the MSFC to be dropped, which generates ICMP-unreachable messages.