Specifications

1087
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S4
• CSCee56252
Symptoms: An Engine 3 or Engine 5 line card may pause indefinitely when an IPv6 ACL that is
configured for security and classification on the line card is modified while being used.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(28)S when the ACL is configured on two or more interfaces of the line card and when
IPv6 QoS is configured on these interfaces.
Workaround: Remove the ACL from the interfaces of the line card before you modify the ACL.
• CSCee93598
Symptoms: An LSP ping reports that an LSP is fine although the LSP is unable to carry MPLS
payloads such as VPN traffic.
Conditions: This symptom is observed on a Cisco router when MPLS echo request packets are
forwarded from untagged interfaces that are directly connected to the destination of the LSP ping
and when the IP time-to-live (TTL) value for the MPLS echo request packets is set to 1.
Workaround: There is no workaround.
• CSCef41934
Symptoms: A router processes incoming LSP ping packets as unlabeled IP packets on a VRF
interface or a non-MPLS interface.
Conditions: This symptom is observed on a Cisco router that has the MPLS LSP Ping feature
enabled.
Workaround: Use an ACL to block port 3503 that is used for LSP ping packets. However, note that
this may prevent some MPLS LSP Ping applications from functioning properly, as noted below:
LSP ping packets that enter on a VRF interface are dropped because the router uses the global
routing table in its attempt to reply to MPLS echo requests, which could cause the reply to be
forwarded to the wrong destination.
LSP ping packets that enter on an interface that is not configured for MPLS are processed, but
depending on the type of MPLS echo packet, the following occurs:
– MPLS echo request packets are dropped.
– MPLS echo reply packets are not dropped. (It possible for an MPLS echo reply packets to be
received on a non-MPLS interface because the reply path is asymmetric with the forward LSP.)
• CSCef52974
Symptoms: An Engine 3 ingress line card crashes continuously with alpha errors and IPC errors
when it processes ingress multicast traffic.
Conditions: This symptom is observed on a Cisco 12000 series when you reload an Engine 3 ingress
line card that has 5000 (S,G) entries.
Workaround: There is no workaround.
• CSCef56201
Symptoms: Multicast MAC rewrites are not updated, preventing multicast traffic from being
switched.
Conditions: This symptom is observed when the VLAN encapsulation is changed, for example from
dot1q to dot1q, from dot1q to QinQ, or from QinQ to dot1q.
Workaround: Enter the clear ip mroute command.
• CSCef64439
Symptoms: A PRE requires a long time to enter the STANDBY HOT state after a switchover.