Datasheet

213
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
Open General Caveats in Release 12.1(19)E1a
None.
Resolved General Caveats in Release 12.1(19)E1a
• Routing protocols do not work on EtherChannels that are reconfigured from Layer 2 to Layer 3. This
problem is resolved in Release 12.1(19)E1a. (CSCeb60132, CSCeb07123)
• A global command is needed for enabling link state messages on interfaces. This problem is resolved
in Release 12.1(19)E1a. (CSCeb06765)
• After a Systems Network Architecture (SNA) physical unit (PU) has been disconnected for several
hours and then reconnected, the physical unit fails to connect when using Data Link Switching
(DLSw) Ethernet Redundancy (ER) with transparent map statements. This problem is resolved in
Release 12.1(19)E1a. (CSCeb02695)
• The Cisco IOS DHCP server does not send a DHCPNAK message when it receives a broadcast
DHCPREQUEST message from a DHCP client that has moved from one subnet to another. This
problem is resolved in Release 12.1(19)E1a. (CSCeb33403)
• If you enter a show interface etherchannel command or a show interface etherchannel module
command for an EtherChannel with ports on a module that is no longer installed, the MSFC might
reload or there might be a switchover to a redundant supervisor engine. This problem is resolved in
Release 12.1(19)E1a. (CSCeb53215)
• Loss of a fan, either through failure or because of power supply shutdown, might cause a reload.
This problem is resolved in Release 12.1(19)E1a. (CSCeb51698)
• When you save the configuration, the following spurious message appears:
%This controller does not support APS[OK]
This problem is resolved in Release 12.1(19)E1a. (CSCin43261)
Resolved General Caveats in Release 12.1(19)E1
• A memory leak might occur with Layer 2 aging and EtherChannels that include ports on different
DFC-equipped modules configured. This problem is resolved in Release 12.1(19)E1.
(CSCeb48732)
• A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a
Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by
default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the
malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject
a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this
advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
This problem is resolved in Release 12.1(19)E1. (CSCdu53656)
• A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a
Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by
default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the
malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject
a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this
advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.