Datasheet

223
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
• Reads and writes to Advanced Technology Attachment (ATA) flash filesystem devices are extremely
slow. This problem is resolved in Release 12.1(14)E. (CSCdz27200)
• In rare situations, an MSFC2 might freeze when it can receive control traffic from the supervisor
engine, but it cannot send it. This problem is resolved in Release 12.1(14)E. (CSCdy15598)
• The show interface gigabitethernet output command incorrectly displays significant deviation
between the TXload and RXload parameters. This problem is resolved in Release 12.1(14)E.
(CSCdx40459)
• If the length field in the MSDP TLV is less than the minimum MSDP TLV size (3 bytes), memory
corruption might occur and cause the system to reload. This problem is resolved in
Release 12.1(14)E. (CSCdz25339)
• A Cisco Router that has run out of processor memory may unexpectedly reload due to a bus error at
an invalid address if there is an attempt to connect with secure shell (ssh) into a vty port, which fails
due to a process creation failure. A SYS-2-CFORKMEM error message appears before the restart.
This problem is resolved in Release 12.1(14)E. (CSCdt13023)
• During a PVC discovery test on an ATM port adapter, the MSFC hangs while trying to create a
subinterface for the PVC discovery. This problem is resolved in Release 12.1(14)E. (CSCdy71452)
• Following a number of “-SP-” malloc-related error messages, the supervisor engine might run out
of memory and reload. This problem is resolved in Release 12.1(13)E1. (CSCdy53239)
• In a redundant Cisco IOS server load balancing (Cisco IOS SLB) configuration, a reload might
occur if you enter the debug ip slb replicate command or the debug ip slb all command. This
problem is resolved in Release 12.1(14)E. (CSCin19541)
• When the PBR next hop is not accessible, the new next hop information is not programmed into
hardware. This problem is resolved in Release 12.1(14)E. (CSCdy31272)
• A reload might occur after RFSS_server_action messages. This problem is resolved in
Release 12.1(14)E. (CSCdy10699)
• When PIM sends an Internet Group Management Protocol (IGMP) receive message on the ingress
interface of the MSFC and an (S,G) R state already exists for a source, the -R flag does not clear.
The receiver does not receive traffic for that particular (S,G) entry. This problem is resolved in
Release 12.1(14)E.
• Auto-Rendezvous Point forwarding may stop working after the state of an interface changes. This
symptom is observed on an interface after a route link goes down then comes back up. This problem
is resolved in Release 12.1(14)E. (CSCdx89761)
• The distribute-list 10 in ethernet 10 router configuration command may not be saved under a
Virtual Private Network (VPN) routing and forwarding (VRF) instance. This problem is resolved in
Release 12.1(14)E. (CSCdz38773)
• A router that is running cell-mode tag switching or Multiprotocol Label Switching (MPLS) on a
label controlled ATM (LC-ATM) interface may reload when it receives a more specific prefix for a
label mapping or binding than the one that is already allocated. For example, the router may reload
when it receives the prefix 10.1.1.0/24 if a binding was already allocated for 10.1.1.1/32 on the basis
of the routing entry 10.1.0.0/16. This symptom is observed on an Edge Label Switch Router (ELSR)
or Label Switch Controller (LSC). This problem is resolved in Release 12.1(14)E. (CSCdy51183)
• IP connectivity may be lost and a Telnet session to the system may lock up when the crypto map
map-name seq-num ipsec-isakmp global configuration command is entered. This symptom is
observed when a Telnet session is made to a router over a generic routing encapsulation (GRE)-IP
Security (IPsec) tunnel and when a new crypto map entry is added to an existing crypto map that is