Specifications

1312
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S3
Conditions: This symptom is observed on a Cisco 12000 series when multicast and unicast traffic
are running through the Engine 6 line card.
Workaround: There is no workaround.
• CSCee65004
Symptoms: A 1-port 10-Gigabit Ethernet line card (1X10GE-LR-SC) may crash, reporting
%TX192-3-CPUIF errors.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(27)S1 when you shut down the 10GE port of a 4-port 10 Gigabit Ethernet module
(WS-X6704-10GE) that is installed in a Cisco 7609 at the other side of the connection.
Workaround: There is no workaround.
• CSCee67207
Symptoms: A public recursive route is not labeled.
Conditions: This symptom is observed on a Cisco router that functions as a BGP peer and that has
the neighbor name send-label command enabled as part of an IPv4 address family, which is
required for Inter-AS configurations. The symptom affects routers that perform MPLS forwarding
using ASICs such as some Cisco 7200 series routers, the Cisco 7304, the Cisco 10000 series, the
Cisco 12000 series, and the Cisco RPM-XF. (This list may not be exhaustive.)
Workaround: There is no workaround. Note that the symptom does not occur if the neighbor name
send-label command is enabled as part of an IPv4 address family VRF.
• CSCee67746
Symptoms: E4+ POS cards reporting %TX192-3-PAM_MODULE and %TX192-3-PAM_PIM
errors. On rare occasions, the card may crash due to receiving malformed packet.
Conditions: This symptom is observed with Cisco IOS Release 12.0(25)S3.
Workaround: There is no workaround.
• CSCee68666
Symptoms: It may take up to 1 second for a line card to notify the RP about a physical layer failure
alarm. This situation prevents fast sub-second IGP convergence.
Conditions: This symptom is observed in a non-FRR and non-APS configuration.
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.
• 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.