Datasheet

169
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
• With a switch fabric module (SFM), some modules might stop egressing traffic. This problem is
resolved in Release 12.1(23)E. (CSCee08015)
• A reload might follow this message:
%C6KERRDETECT-SP-2-SUPSWO: Supervisor card switchover due to unrecoverable errors
detected, Reason: Failed In-band Path
This problem is resolved in Release 12.1(23)E. (CSCee01297)
• WCCP-redirected packets that have no next hop ARP cache entry are process-switched to generate
an ARP request. Because the WCCP redirection causes no ARP requests to be sent, the ARP cache
is never populated for the next hop, and subsequent WCCP-redirected packets continue to be process
switched. This problem is resolved in Release 12.1(23)E. (CSCed92290)
• When the maximum-paths eibgp command or maximum-paths ibgp command is configured, the
withdraw message of a multipath (not bestpath) from a BGP neighbor deletes the path from the BGP
table but it does not uninstall the route from the IP routing table. This problem is resolved in
Release 12.1(23)E. (CSCed60800)
• After a few days of running time, the show environment temperature command does not display
current values. This problem is resolved in Release 12.1(23)E. (CSCed49423)
• Some packet loss might occur when a host sends and receives both bridged traffic and routed traffic
through a Layer 2 switch that connects through a nontrunking cross-DFC EtherChannel to a
Supervisor Engine 2. This problem is resolved in Release 12.1(23)E. (CSCed06744)
• Under heavy traffic conditions, online insertion and removal (OIR) of a switch fabric module or OIR
of a nonfabric-enabled module might cause OSMs to stop forwarding traffic. This problem is
resolved in Release 12.1(23)E. (CSCec49269)
• The time-to-live value (TTL value) might not be decremented correctly in tunnel traffic. This
problem is resolved in Release 12.1(23)E. (CSCea77189)
• The Multicast Broader Gateway Protocol (MBGP) default route is advertised as 0.0.0.0/0 to a
Protocol Independent Multicast (PIM) neighbor, but the MBGP default route is not considered for a
multicast Reverse Path Forwarding (RPF) check on the router. This problem is resolved in
Release 12.1(23)E. (CSCdy59996)
FlexWAN Module Caveats
• Open FlexWAN Module Caveats in Release 12.1(23)E4, page 169
• Resolved FlexWAN Module Caveats in Release 12.1(23)E4, page 169
• Resolved FlexWAN Module Caveats in Release 12.1(23)E3, page 170
• Resolved FlexWAN Module Caveats in Release 12.1(23)E2, page 170
• Resolved FlexWAN Module Caveats in Release 12.1(23)E1, page 170
• Resolved FlexWAN Module Caveats in Release 12.1(23)E, page 170
Open FlexWAN Module Caveats in Release 12.1(23)E4
None.
Resolved FlexWAN Module Caveats in Release 12.1(23)E4
None.