Datasheet

149
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
• A reload might occur when a distance vector multicast routing protocol (DVMRP) tunnel is
configured and routing information is being redistributed between DVMRP and MBGP. This
problem is resolved in Release 12.1(26)E. (CSCee66936)
• With policy-based routing (PBR) and an input ACL configured on the same interface, if you enter
the clear arp-cache command, PBR is done in software instead of hardware. This problem is
resolved in Release 12.1(26)E.(CSCee58127)
• If you enter the attach command through the Cisco IOS web browser interface, a reload might occur.
This problem is resolved in Release 12.1(26)E. (CSCee56618)
• If you enter the debug ip slb connections acl command, the debugging output might consume all
available resources. This problem is resolved in Release 12.1(26)E with the debug ip slb
connections [state] [acl_name] command. (CSCee33923)
• With a PFC2 or DFCs, you might see “L3-PS-DRVR” messages. This problem is resolved in
Release 12.1(26)E. (CSCee24424)
• With Cisco IOS SLB configured, a reload might occur if you remove the SLB configuration while
the SLB virtual servers are handling traffic. This problem is resolved in Release 12.1(26)E.
(CSCee23087)
• When an OSPF neighbor on a local IP segment has multiple interfaces on that IP segment, OSPF
installs only a single next-hop entry to routes reachable through the OSPF neighbor, instead of
multiple next-hop entries, as required by RFC 2328. This problem is resolved in Release 12.1(26)E.
(CSCee21928)
• With Cisco IOS SLB configured, you might see “ALIGN-3-SPURIOUS” messages. This problem is
resolved in Release 12.1(26)E. (CSCed58748)
• After a reload, the bridge ID MAC address of a bridge group might change. This problem is resolved
in Release 12.1(26)E. (CSCed38840)
• If you enable PIM on a VLAN interface and configure a bridge group on the VLAN interface, and
then remove the PIM configuration from the VLAN interface, EIGRP neighborships are lost. This
problem is resolved in Release 12.1(26)E. (CSCed12722)
• With a Y-cable Automatic Protection Switching (APS) configuration, there might be 30 to 45
seconds of traffic loss following an APS switchover. This problem is resolved in Release 12.1(26)E.
(CSCdz66609)
• The “Do Not Learn” bit is not set in Layer 2 traffic processed by bridge groups on the MSFC. This
problem is resolved in Release 12.1(26)E. (CSCeb56814)
• If you change the configuration of a permanent virtual circuit (PVC) after an alarm indication signal
(AIS) is received on the PVC, the PVC does not come up; additionally, the PVC does not come up
after the AIS stops. This problem is resolved in Release 12.1(26)E. (CSCdy04914)
• When configured as a provider edge (PE) router, IP path MTU discovery does not work from directly
connected network devices. For example, IP path MTU discovery might not work between BGP
peers. This problem is resolved in Release 12.1(26)E. (CSCds90697)
• Configuring an extended Border Gateway Protocol (BGP) community-list statement with any illegal
regular expression pattern might cause a reload. This problem is resolved in Release 12.1(26)E.
(CSCdx71842)
• After you enter a shutdown command on a physical ATM interface, ATM subinterfaces configured
on the physical ATM interface are displayed as “down” instead of “administratively down.” This
problem is resolved in Release 12.1(26)E. (CSCea92873)
• The allowed VLAN list does not filter the traffic transmitted from a SPAN destination trunk port.
This problem is resolved in Release 12.1(26)E. (CSCeb01318)