Datasheet

236
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
• If you replace a WS-X6148-GE-TX or WS-X6148V-GE-TX switching module with a
WS-X6548-GE-TX or WS-X6548V-GE-TX switching module, any switchport commands
configured on the WS-X6148-GE-TX or WS-X6148V-GE-TX switching module do not work on the
WS-X6548-GE-TX or WS-X6548V-GE-TX switching module. This problem is resolved in
Release 12.1(13)E10. (CSCea89432)
• Deny ACEs that do not specify any Layer 4 ports incorrectly do not deny fragmented packets. This
problem is resolved in Release 12.1(13)E10. (CSCeb04343)
• With IGMP snooping configured on a VLAN, but with PIM not enabled on the Layer 3 VLAN
interface, PIM register and register-stop packets are routed to the interface on which they are
received causing additional load on the network and MSFC. This problem is resolved in
Release 12.1(13)E10. (CSCeb12540)
• The show mls qos command might incorrectly show support for egress QoS. This problem is
resolved in Release 12.1(13)E10. (CSCeb29483)
• With a Supervisor Engine 2, the IOS ARP and adjacency entries for the next-hop IP address
configured for a static route might not be created. This problem is resolved in Release 12.1(13)E10.
(CSCeb38062)
• With RPR redundancy configured, the MSFC and OSMs might incorrectly reload. This problem is
resolved in Release 12.1(13)E10. (CSCeb49134)
• The CEF entries for traffic from a directly connected Layer 3 address are removed and recreated
randomly, which causes Unicast traffic loss for the affected entries. This problem is resolved in
Release 12.1(13)E10. (CSCeb53542)
• Incorrect VTP pruning might occur if you delete or rename VLANs in VLAN database mode. This
problem is resolved in Release 12.1(13)E10. (CSCeb60262)
• Supervisor Engine 1 does not have RP-SP inband channel communication monitoring. This problem
is resolved in Release 12.1(13)E10. (CSCeb46610)
• Memory usage when handling route flaps is not optimal, which causes the route-flap handling
process to hold memory longer than necessary and which can cause out-of-memory conditions when
routes flap continuously. This problem is resolved in Release 12.1(13)E10. (CSCeb57465)
• When the multicast traffic level exceeds the Layer 3 hardware switching capacity, the excess
multicast traffic might be dropped instead of being routed in software on the MSFC. This problem
is resolved in Release 12.1(13)E10. (CSCeb62692)
• If you enter the shutdown command and then the no shutdown command on an interface that is
handling a high volume of Layer 3 hardware switched multicast traffic, some of the multicast traffic
is routed in software on the MSFC instead of being Layer 3 switched in hardware when the interface
comes back up. This problem is resolved in Release 12.1(13)E10. (CSCeb67996)
• With QoS and Cisco IOS server load balancing (Cisco IOS SLB) configured on a Supervisor Engine
1, a VACL configured to filter multicast traffic on one VLAN might incorrectly be applied to
multicast traffic on other VLANs. This problem is resolved in Release 12.1(13)E10. (CSCeb69582)
• If you configure the mac-address-table aging-time command with a nonzero value, a static MAC
address for traffic that egresses through a DFC-equipped card might change to a dynamic MAC
address. This problem is resolved in Release 12.1(13)E10. (CSCeb72014)
• With PBR configured on an interface, if the link goes down or if you enter a clear arp command,
traffic that should be Layer 3 switched in hardware might be routed in software on the MSFC. This
problem is resolved in Release 12.1(13)E10. (CSCeb78050)
• Multicast traffic that should be Layer 3 switched in hardware might be dropped or routed in software
on the MSFC. This problem is resolved in Release 12.1(13)E10. (CSCeb80373)