Specifications

1266
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S5
Workaround: Reset the standby PRE by entering the hw-module standby-cpu reset command to
enable it to reload and come back up properly.
• CSCeh37351
Symptoms: In a tag switching-to-IP switching scenario with an ISE ingress line card and an
Engine 4 plus (E4+) egress line card, the following bad packets may be forwarded to the E4+ line
card:
– tag2ip, with bad ip hdr cksum
– tag2ip, with ip->tl > L2
– tag2ip, with ip->tl < 20
– tag2ip, with ip options packets
– tag2ip, with ip options packets with bad ip hdr cksum
– tag2ip, with ip options packets with ip->tl > L2
– tag2ip, with ip options packets with ip->tl < 20
These bad packets cause packet corruption and an “TX192-3-PAM_PIM” error message on the E4+
line card and may even cause the E4+ line card to reset.
Conditions: This symptom is observed on a Cisco 12000 series.
Workaround: There is no workaround.
Further Problem Description: The fix for this caveat enables the ISE line card to drop the
above-mentioned bad packets.
• CSCeh42465
Symptoms: An Engine 3 line card sends unlabeled traffic after it has been toggled from explicit
routing to default routing. The symptom is related to the handling of a default-route on an Engine 3
ingress line card that functions in an IP-to-MPLS path.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(30)S1 or any other image that includes the fix for caveat CSCsa64782, which is a
preliminary requisite for default-route handling on an Engine 3 line card. The symptom occurs in
the following scenario:
1) You configure BGP to advertise the target address, so the target address is directly known in the
routing table.
2) You remove the advertisement from BGP and return to default routing, with the same source for
the next hop as the platform that was the BGP next hop.
3) You enter the clear ip route network command, with the address of the BGP next hop for the
network argument.
After the transition from non-default routing to default routing, entering the clear ip route network
command, with the address of the next hop for the network argument, causes an inconsistency, and
traffic is forwarded as unlabeled.
Workaround: To restore proper operation, enter the clear ip route 0.0.0.0 command.
• CSCeh46072
Symptoms: When the following sequence if performed on a GSR, multiple subinterfaces will end
up with the same ifnumber, thus resulting in incorrect CEF entries:
1. add serial subinterface (channelized). 2. delete the interface created. 3. add ATM subinterface. 4.
add back the serial subinterface.