Datasheet

293
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
Resolved Caveats in Release 12.1(8b)E7
• For multicast flows, the PFC provides Layer 3 switching only when the ingress interface MTU size
matches the minimum MTU size of the egress interface. This problem is resolved in
Release 12.1(8b)E7. (CSCdu71710)
• Configuring broadcast suppression on a Gigabit Ethernet interface filters all broadcast traffic. This
problem is resolved in Release 12.1(8b)E7. (CSCdv85377)
• When multiple switches configured with Supervisor Engine 1 and MSFC1 are connected to each
other, in rare situations the MSFCs freeze temporarily while waiting for the neighboring MSFC to
reply to an EIGRP query. The condition clears after MSFCs run through the default 3-minute SIA
timer. This problem is resolved in Release 12.1(8b)E7. (CSCdv85419)
• The MSFC may reload after the show ip igmp groups command is entered if the command is paused
for a prolonged period of time at the ‘more’ prompt and restarted later. This problem is resolved in
Release 12.1(8b)E7. (CSCdu04678)
• If you change the configuration of a service policy, the show policy-map interface command
displays incorrect statistics until you clear the policy map counters. This problem is resolved in
Release 12.1(8b)E7. (CSCdr36213)
• With EIGRP, if a default network other than 0.0.0.0 and next hop are learned on an MSFC on a
Supervisor Engine 1, and later the next hop changes, using either the same default network or a
different default network, the MLS entries associated with the original next hop are not purged. This
results in suboptimal routing or loss of traffic until you enter the clear mls entry ip all command to
clear the MLS cache. This problem is resolved in Release 12.1(8b)E7. (CSCdt71961)
• An MSFC configured as a PIM router that receives a PIM sparse-mode JOIN/PRUNE message for
the auto-RP groups causes those groups to transition from dense-mode forwarding to sparse-mode
forwarding. This problem is resolved in Release 12.1(8b)E7. (CSCdu17859)
• The Open Shortest Path First (OSPF) database may not create the necessary entries to resubmit an
OSPF interarea route. This problem is resolved in Release 12.1(8b)E7. (CSCdt93586)
• With data-link switching (DLSw) and Ethernet Redundancy (ER) configured, the MSFC might
reload. This problem is resolved in Release 12.1(8b)E7. (CSCdv16277)
• With Enhanced Interior Gateway Routing Protocol (EIGRP) configured for any Layer 3 protocol
(EIGRP-IP, EIGRP-IPX, and EIGRP-APPLETALK), the MSFC might reload. This problem is
resolved in Release 12.1(8b)E7. (CSCdv04283)
Resolved Caveats in Release 12.1(8b)E6
• On a Supervisor Engine 1, during periods of very high route-update traffic, the pool of control
message buffers might be exhausted. This problem is resolved in Release 12.1(8b)E6.
(CSCdt73406)
• With a large number of multicast route entries with a large number of output interfaces (OIFs) for
each entry, all multicast Layer 3 switching entries might get purged. This problem is resolved in
Release 12.1(8b)E6. (CSCdv75054)
• With a redundant configuration, if a fan tray fails, the redundant supervisor engine does not become
active if the active supervisor engine fails. This problem is resolved in Release 12.1(8b)E6.
(CSCdv74489)
• NetFlow v7 records have an incorrect destination interface index if the MLS entry does not have an
ingress SrcDstPorts entry. This problem is resolved in Release 12.1(8b)E6. (CSCdv11257)
• MBGP redistribution might not work as expected. Some autosummarization might take place
instead. This problem is resolved in Release 12.1(8b)E6. (CSCdt62457)