Specifications

1058
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
• CSCee58083
Symptoms: A Cisco router that runs a Cisco IOS interim release for Cisco 12.0(29)S or interim
Release 12.3(9.3) or 12.3(9.2)T may log the following error message and traceback, and IPC
services using large RPC messages/replies may fail:
%IPC-SP-5-INVALID: Invalid dest port=0x2220000
-Traceback= 402F3784 403027CC 403025AC 4030A10C 4030A4F8 4030A7B8 402F7E78 402F8244
40309478 402F8890 4033A0E8 40344284
Conditions: This symptom is observed without any external trigger occurring.
Workaround: There is no workaround.
• CSCee59585
Symptoms: On a Cisco router, the output of the execute-on slot number show ip cef prefix command
may display the same imposed label twice for a recursive public route.
Conditions: This symptom is observed on a Cisco platform that supports distributed forwarding such
as a Cisco 7500 series or a Cisco 12000 series when the neighbor name send-label command is
configured under an IPv4 BGP address family on a VIP or line card and when one of the following
actions occurs:
– You enter the clear cef linecard command.
– You perform an OIR of the VIP or line card.
– You enter the no ip cef distributed command followed by the ip cef distributed command.
The symptom disappears after the affected prefix flaps.
Workaround: There is no non-impacting workaround, but you can enter the clear ip route prefix
command or reset the BGP peer to solve the problem.
• CSCee66206
Symptoms: When you boot a Cisco 7200 series that is configured with an NPE-300 or NPE-400 and
that runs a c7200-js-mz image, the router may crash with a traceback.
Conditions: This symptom is observed when the c7200-kboot-mz image is the bootloader and when
the router runs Cisco IOS interim Release 12.1(22.3)E1. The symptom may also occur in other
releases such as 12.0 S, 12.2 S, and 12.3.
Workaround: There is no workaround.
• CSCee69861
Symptoms: When a host sends a path MTU discovery packet into a L2TPv3 tunnel, a Cisco 10720
returns an ICMP unreachable packet, indicating that the path MTU is “MTU-32byte (L2TPv3
header)-(layer2 header of customer packets),” which is incorrect. This situation causes TCP
communications such as FTP or HTTP downloads over the L2TPv3 tunnel to fail. For example, 26
bytes (outer IP + L2TPv3 header sizes) may be missing.
Conditions: This symptom is observed on a Cisco 10720 that functions as a PE router.
Workaround: If this is an option, set an MTU with a small size at the server side. If this is not an
option, there is no workaround.
• CSCee69887
Symptoms: A dual SRP ring fails to become active completely due to an is-type mismatch. The
output of the show clns neighbors command indicates that a certain system interface remains in the
“Init” state indefinitely, although the output of the show ip interface brief command shows that this
interface is up.