
412
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S3
–
DC PEM
Workaround: There is no workaround.
• CSCsu92317
Symptoms: Pings fail on an MLPPP interface.
Conditions: There is an MFR interface used for L2 services such as xconnect and an MLPPP
interface on the same SPA. When the member links are removed/added from these bundles
back-to-back, the ping on the MLPPP interface may fail. This symptom is observed so far only on
E5 cards.
Workaround: Reload the line card.
• CSCsu93472
Symptoms: Whenever a service policy that has an action as bandwidth or shaping is applied as
output to the core-facing interface in an imposition PE in a VPLS setup, the egress multicast packets
that are passing through the core-facing interface are being dropped.
Conditions: This symptom is observed when:
–
A service policy with action as bandwidth or shaping is applied as output to the core-facing
interface in an imposition PE in a VPLS setup; and
–
Multicast traffic is flowing through the interface.
Workaround:
1) Remove and re-add the bridge-domain.
2) Reload the ingress line card that has bridge-domain configured on it.
• CSCsu93501
Symptoms: In Cisco IOS Release 12.0(33)S, the VPLS-specific ingress policy matches are not
working for the multicast and VPLS-unknown classes. Either class will match all unicast, multicast,
broadcast, and unknown traffic.
Conditions: This symptom is observed for multicast and VPLS-unknown traffic that passes through
the VPLS-specific ingress policy in Cisco IOS Release 12.0 (33)S images only.
Workaround: There is no workaround.
• CSCsv00039
Symptoms: A customer observed the following message in the log:
The PAM_PIM created confusion as it was being referred to Protocol Independent
Multicast and not to the Packet Assembly Module/Packet Interface Module.
Conditions: This symptom occurs because of a corrupted packet.
Workaround: There is no workaround.
• CSCsv04674
Symptoms: The M(andatory)-Bit is not set in Random Vector AVP, which is a must according to
RFC2661.
Conditions: This symptom is observed with Egress ICCN packet with Random Vector AVP during
session establishment.
Workaround: There is no workaround.
Kommentare zu diesen Handbüchern