
609
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S4
Workaround: Enter the clear ip mds linecard linecard-slot-number command. For the
linecard-slot-number argument, enter the core-facing slot.
• CSCek45970
Symptoms: In unidirectional mode, an Automatic Protection Switching (APS) switchover from a
protect channel to a working channel may fail because the interface of the working channel remains
in the up/down state.
Conditions: This symptom is observed on a Cisco 12416 that runs Cisco IOS Release 12.0(32)S3
and that has two redundant 1-port channelized OC-48 POS ISE line cards that are configured for
APS.
Workaround: There is no workaround.
• CSCek49119
Symptoms: On an Engine 3 CH/OC12 card configured for MLPPP, when MTU is mismatched
between the two ends, shutting down and restarting causes MTU to be negotiated. However, this
action causes buffer recarving, which is undesirable.
Conditions: This symptom has been observed when MLPPP configured mismatched MTU values,
such that the new MTU value would be one that triggers a recarve.
Workaround: Match the MTU values on both sides on the interface
• CSCek49158
Symptoms: Changing an MTU value on an interface may cause the RP to trigger buffer recarve
unexpectedly.
Conditions: This symptom has been observed when changing the MTU value using the mtu bytes
command. The new bytes value may or may not trigger the buffer recarve, and this behavior needs
to be characterized.
Workaround: There is no workaround.
• CSCsa72313
Symptoms: The following error messages may be generated on a router that has IP ACL enabled:
%SYS-2-INSCHED: suspend within scheduler
-Process= "<interrupt level>", ipl= 3
-Traceback= 40525388 40628848 4060AED4 403F15BC 403F34F8 403F37EC 400901C8
4008E730 406A0EEC 40621120
Conditions: This symptom is observed on a Cisco router such as a Cisco 7200 series, Cisco 7304,
and Cisco 7500 series when a Turbo ACL compilation is configured along with an ACL on an
ingress interface and when traffic passes through the ingress interface. The symptom does not affect
the Cisco 10000 series.
Workaround: There is no workaround.
• CSCsc83817
Symptoms: When MPLS-aware NetFlow is properly configured, it may not capture MPLS-labeled
traffic.
Conditions: This symptom is observed on a Cisco router when MPLS-aware NetFlow is configured
via the ip flow-cache mpls label-position label-position-1 global configuration command and when
NetFlow is enabled on the interface via the ip route-cache flow interface configuration command.
When MPLS traffic passes over the interface that is configured to capture MPLS-aware NetFlow
statistics, MPLS-aware NetFlow should capture label information for the traffic flow, but it does not
because the MPLS switching vectors are not properly updated. You can verify this condition in the
Kommentare zu diesen Handbüchern