Datasheet
216
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Caveats
• An MSFC2 might reload with the following error messages:
MISTRAL-3-ERROR: Error condition detected: SYSAD_TIMEOUT_DPATH
and:
sysad_dpath_addr_log = 0x100002E1
This problem is resolved in Release 12.1(19)E. (CSCdu83548)
• With PIM dense mode configured, multicast traffic might get dropped when all routers have the
multicast group in a pruned state even though interested receivers are present. This problem is
resolved in Release 12.1(19)E. (CSCea26993)
• When you insert an SFM and cause a transition to truncated mode, QoS policing and marking stop
working. This problem is resolved in Release 12.1(19)E. (CSCeb09034)
• Web sites that require authentication become unreachable. This symptom is observed on an MSFC
on which Web Cache Communication Protocol (WCCP) is enabled and Cisco Express Forwarding
(CEF) switching is disabled. This problem is resolved in Release 12.1(19)E. (CSCdz36099)
• No command exists to disable the generation of PPP Link Control Protocol (LCP) keepalive failure
link-down traps. These traps are sent by default when the LCP goes down. This problem is resolved
in Release 12.1(19)E with the introduction of the new no ppp link trap command. (CSCdy05898)
• An interface that is defined in an Enhanced Interior Gateway Routing Protocol (EIGRP) network
statement may fail to come up in the EIGRP topology table. This symptom is observed after a system
reload. The occurrence of the symptom depends on the type of interface that is connected and on the
timing of the interface activation. This problem is resolved in Release 12.1(19)E. (CSCdz41087)
• The system may reload unexpectedly when saving the configuration to NVRAM. This symptom is
observed in a system that is configured with the service compress-config global configuration
command. This problem is resolved in Release 12.1(19)E. (CSCdz32940)
• A window condition may occur if an initial program load (IPL) is performed on a mainframe while
it is processing a primary logical unit secondary logical unit (PLU-SLU) session over a dependent
logical unit requester (DLUR). A logical unit (LU) may hang and may cause a downstream physical
unit (DSPU) to pause indefinitely. The DSPU state is shown as “reset” even though the finite state
machine (FSM) history shows the DSPU state as “reset link inactive.” The state of the LU is also
reset, and the DSPU cannot be used. An IPL has to be performed on the Systems Network
Architecture (SNA) switch to recover the DSPU. These symptoms are observed only in a small
window condition when an IPL is performed on a host while DLUR is used. This problem is resolved
in Release 12.1(19)E. (CSCdx77062)
• UP and DOWN status messages may be displayed on the console. This symptom is observed when
a leased-line configuration is in the UP state, but the peer is not responding. This symptom occurs
because PPP calls the interface reset vector regularly if the peer is not responding to the PPP
attempts to communicate. This problem is resolved in Release 12.1(19)E. (CSCdx55880)
• TCP processing fails in the data repacketized process and creates inaccurate packets. A data-link
switching (DLSw) circuit disconnects suddenly, and the following error message is displayed if you
enter the debug dlsw core command on one for the DLSW routers:
DLSW: Invalid dlsw version 78
The number 78 is an example and may be any other number. These symptoms are observed during
an attempted TCP retransmission of a message and TCP data packet reconstruction on a DLSw
router. This problem is resolved in Release 12.1(19)E. (CSCdx55357)
• A Systems Network Architecture Switching Services (SNASw) router that is configured with a
downstream port of conntype=len incorrectly advertises itself as nodetype=NN in the exchange
identification (XID) exchange. This problem is resolved in Release 12.1(19)E. (CSCdx47521)