Specifications

1059
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
Conditions: This symptom is observed when a dual SRP ring is configured on three routers that run
Cisco IOS Release 12.2S. The symptom may also occur in other releases.
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.
• 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.
• 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.
• CSCee74886
Symptoms: After you enter the microcode reload pxf command or after a PXF crash occurs,
EoMPLS packets that should be encapsulated with EoMPLS encapsulation are treated as if they are
normal IP packets, and are likely to be dropped by the router.
Conditions: This symptom is observed on a Cisco 10720 router when an SRP (sub)interface is used
as the EoMPLS backbone interface to transport EoMPLS packets to other EoMPLS PE routers and
when the (sub)interface has the xconnect destination-address vc-id encapsulation mpls command
enabled.
Workaround: Remove the xconnect destination-address vc-id encapsulation mpls command from
the (sub)interface that connects to a customer device, and reconfigure it on the (sub)interface.
• CSCee74920
Symptoms: An RP crashes after you remove the event manager applet.
Conditions: This symptom is observed on a Cisco platform that runs Cisco IOS Release 12.0(26)S
or a later 12.0 S release when an EEM policy is removed from the configuration by entering the no
event manager applet applet-name command while actions within the EEM policy are being
executed.
Workaround: There is no workaround.