Specifications

1271
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S5
• CSCsa65732
Symptoms: When you remove a policy map from a subinterface, the subinterface may become stuck,
preventing traffic from passing through the subinterface.
Conditions: This symptom is observed on a Cisco 10000 series that runs Cisco IOS
Release 12.0(25)SX7 when a nested policy map is applied to the main or physical interface in
addition to the one that is already applied to the subinterface. The symptom could also occur in
Release 12.0S.
Workaround: Remove the policy map from the physical interface before you remove the policy map
from the subinterface. When the subinterface configuration is updated, re-apply the policy map to
the physical interface.
• CSCsa67488
Symptoms: A Cisco 10008 router with PRE1 may report a PXF crash.
Conditions: The symptom is observed when modifying an access-list that is already attached to a
multilink interface.
Workaround: Modify an access-list only if it not attached to the interface. If the access-list cannot
be removed from the interface, then create a new one and apply.
• CSCsa68301
Symptoms: Inter-MVPN traffic does not function on an Engine 4+ line card.
Conditions: This symptom is observed on a Cisco 12000 series and may occur with any Engine 4+
line card.
Workaround: There is no workaround.
• CSCsa68616
Symptoms: An IPC failure occurs and an OC-12 line card that is configured for Frame Relay over
MPLS resets.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(27)S1.
Workaround: There is no workaround.
Further Problem Description: The IPC failure and the line card reset occur after a depletion of the
elements in the FrFab 608 byte queue for the line card. Consecutive outputs of the show controllers
slot-number frfab queue command show a consistent and rapid leak of these buffers.
• CSCsa70274
Symptoms: A Cisco router may crash during an LSP traceroute when a transit router responds with
a downstream map TLV that contains a multipath length field that is set to 0, 1, 2, or 3.
Conditions: This symptom is observed during testing of the Cisco LSP ping draft version 3 in a
network that uses a later version of the LSP ping draft.
The implementation of draft version 3 does not handle the multipath length field settings correctly.
In draft version 3 and earlier drafts, there is an ambiguity on whether or not the multipath length
field includes the four bytes comprising of the hash-key type, depth limit, and multipath length
fields. As such, all implementations of the draft version 3 encode the length as four bytes and reply
with a multipath length of four bytes.