Specifications
1413
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S
Conditions: This symptom is observed on a Cisco 12000 series that is running Cisco IOS
Release 12.0 S.
Workaround: Enter the clear log EXEC command directly on the line card.
• CSCuk47444
Symptoms: Memory allocated by the ip cef linecard ipc memory kbps global configuration
command is not freed when a standby Route Processor (RP) becomes an active RP.
Conditions: This symptom is observed only when the ip cef linecard ipc memory kbps global
configuration command is used because the allocated memory on the standby RP memory is not
freed when the standby RP switches over to become the active RP.
Workaround: There is no workaround.
• CSCuk47482
Symptoms: A router may reload unexpectedly while you disable label distribution protocol (LDP)
on an interface.
Conditions: This symptom is observed on a router that has several interfaces that are configured for
LDP when you disable LDP on all interfaces and when there is still one open TCP connection that
is passively used by LDP while you disable LDP on the last interface.
Workaround: There is no workaround.
• CSCuk47528
Symptoms: Packet redirection to a cache may not occur even though Web Cache Communication
Protocol (WCCP) is enabled and the cache farm has formed successfully. The symptom may be
invisible to end users because packets, usually packets that are part of HTTP sessions, still flow
successfully to and from their original destinations.
Conditions: This symptom is observed on a Cisco platform when both WCCP and Cisco Express
Forwarding (CEF) are enabled.
Workaround: Disable CEF on all interfaces on which a WCCP redirect statement is configured.
• CSCuk48314
Symptoms: During an SSO switchover, the newly active Route Processor (RP) may output the
following error message:
%SCHED-7-WATCH: Attempt to monitor uninitialized watched queue (address 0).
-Process= "CEF LC IPC Background"
This error is harmless, and no functional problem will occur when this error is received.
Conditions: This symptom occurs during an SSO
switchover.
Workaround: There is no workaround.