Specifications
1272
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S5
When an LSP traceroute is invoked and a transit router replies with a downstream map TLV that
contains a multipath length field that is set to a length shorter than four bytes, existing
implementations handle this situation incorrectly and cause memory packet memory to become
corrupted during the subsequent attempt to build an MPLS echo request packet. This situation
eventually causes the router to crash.
Workaround: If LSP traceroute implementations exist on a transit router that cause the transit router
to reply with a multipath length that is set to a value other than four, avoid using an LSP traceroute.
Note, however, that the implementations of Cisco LSP ping draft version 3 do not reply with
multipath lengths that can cause this crash.
Wide-Area Networking
• CSCeh33185
Symptoms: A POS interface on a VIP4-80 that is configured for PPP goes down and remains down.
Conditions: This symptom is observed on a Cisco 7513 that runs Cisco IOS Release 12.0S only
when PPP receives an LCP PROTOCOL REJECT message for PAP or CHAP. The symptom may
also occur in other releases.
Workaround: Enter the shutdown command followed by the no shutdown command on the afected
POS interface.
• CSCsa49019
Symptoms: A memory leak may occur in the "Multilink Events" process, which can be seen in the
output of the show memory summary command:
0x60BC47D0 0000000024 0000000157 0000003768 MLP bundle name
0x60BC47D0 0000000028 0000000003 0000000084 MLP bundle name
0x60BC47D0 0000000044 0000000001 0000000044 MLP bundle name
0x60BC47D0 0000000048 0000000001 0000000048 MLP bundle name
0x60BC47D0 0000000060 0000000001 0000000060 MLP bundle name
0x60BC47D0 0000000064 0000000013 0000000832 MLP bundle name
0x60BC47D0 0000000068 0000000008 0000000544 MLP bundle name
0x60BC47D0 0000000072 0000000001 0000000072 MLP bundle name
0x60BC47D0 0000000076 0000000001 0000000076 MLP bundle name
0x60BC47D0 0000000088 0000000018 0000001584 MLP bundle name
Conditions: This symptom is observed when two interfaces are configured in the same multilink
group or are bound to the same dialer profile.
Workaround: There is no workaround.