Specifications

1178
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S1
Workaround: There is no workaround.
• CSCee70024
Symptoms: LSP-Ping packets may include a Vendor Enterprise Code TLV Type 5 with a length that
is greater than 4 and with Vendor Private Extensions. According to the
draft-ietf-mpls-lsp-ping-05.txt IETF draft, the Vendor Enterprise Code TLV Length should always
be 4, and the vendor extensions should use a TLV Type that is in the range 64512-65535.
Conditions: This symptom is observed on a Cisco platform that functions in an MPLS OAM
environment.
Workaround: There is no workaround.
• CSCee70478
Symptoms: If hardware multicast forwarding is enabled on an Engine 2 line card that is connected
to the source of multicast traffic, multicast traffic may not be forwarded after the router has reloaded.
Conditions: This symptom is observed on a Cisco 12000 series that runs the gsr-p-mz image of
Cisco IOS Release 12.0(27)S2.
Workaround: Remove and reapply hardware multicast forwarding to the line card.
• CSCee71793
Symptoms: Malformed MPLS echo request packets may cause excessive Route Processor (RP) CPU
cycles to be consumed during parsing of malformed TLVs.
Conditions: This symptom is observed when MPLS echo request packet are decoded and incorrectly
parse beyond the packet boundary due to improper bounds checking.
Workaround: There is no workaround.
• CSCee72027
Symptoms: WRED does not share WRED labels even when WRED parameters are identical.
Because Engine 4 and Engine 4+ line cards have only seven WRED labels, when you configure
WRED for all eight IP precedences, the line cards display the following error:
% Can not configured WRED, all WRED labels are in use.
This situation prevents part of the precedence (WRED group) command for the 8th IP precedence
from being applied to the interface policy map.
Conditions: This symptom is observed when you apply a policy map that uses more than seven
WRED labels and when WRED labels are not shared.
Workaround: There is no workaround.
• CSCee72353
Symptoms: An LDP session over a tunnel interface may drop and not come back up.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0 S when
auto-tunnel traffic engineering is configured and when RSVP label distribution and LDP are
configured in the MPLS core.
If the no mpls ip command is configured on the physical interface to disable LDP, and RSVP label
distribution remains enabled, auto-tunnel traffic engineering fails and you cannot bring the tunnel
back up.
Workaround: Run LDP in the MPLS core for all interfaces that have auto-tunnel traffic engineering
configured.