Specifications

1113
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S3
Symptoms: When the HA mode is RPR+ and a standby PRE comes up after a crash, the HA mode
may change from RPR+ to SSO and the standby PRE displays error messages that indicate that the
running configuration of the active PRE is “mode rpr-plus” but the running configuration of the
standby PRE is “mode sso.”
When the HA mode is SSO and a standby PRE comes up after a crash, the standby PRE may become
stuck in its initialization and does not enter the “STANDBY_HOT” state.
Conditions: These symptoms are observed on a Cisco 10000 series when the standby PRE crashes
but does not report a switchover (that is, a “standby down” event occurs but not a switchover event),
causing the standby PRE to come up in an inconsistent state. When the standby PRE crashes, the
active PRE shows an error message that includes the text “PEER_CRASH_INTERRUPT.”
Workaround: Reset the standby PRE by entering the hw-modulestandby-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.
• CSCeh40882
Symptoms: On a Cisco 12000 series router with a 1xChOC12/DS1 ISE line card configured with
multilink MFR protocol and a MQC policy, after a reload the QoS does not get applied to the bundle.
The QoS goes to the suspend mode.
Conditions: The bundle loses its QoS policy when the router is reloaded. This problem is observed
when running Cisco IOS Releases 12.0(28)S1, 12.0(30)S, and an interim release for
Release 12.0(31)S.
Workaround: Remove the service-policy from the bundle and re-apply it.
• 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.