Specifications

1265
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S5
• CSCeh23047
Symptoms: After a manual SSO switchover, traffic in the tag switching-to-IP switching direction
between an egress 1-port 10-Gigabit Ethernet Engine 4+ line card and an ingress 4-port Gigabit
Ethernet ISE line card does not recover.
Conditions: This symptom is observed on a Cisco 12000 series that runs the gsr-p-mz image of
Cisco IOS Release 12.0(31)S.
Workaround: Reload microcode onto the 4-port Gigabit Ethernet ISE line card.
• CSCeh27734
Symptoms: For recursive routes with implicit null as the local label, the FIB may point to the rewrite
of the parent prefix. However, this situation may not affect any functionality.
Conditions: This symptom is observed on a router that is configured for MPLS forwarding.
Workaround: Change the affected prefix to be non-recursive.
• CSCeh29983
Symptoms: Several crashes have occurred in multiple VIP's on a Cisco 7513.
Conditions: No conditions which lead to this event have been discovered so far.
Workaround: There is no workaround.
• CSCeh33574
Symptoms: An Engine 4 plus or Engine 5 line card does not come up.
Conditions: This symptom is observed on a Cisco 12000 series that runs a Cisco IOS interim release
for Release 12.0(31)S when IPC timeout errors occur.
Workaround: There is no workaround.
• CSCeh34989
Symptoms: One of the following two symptoms may occur on a POS ISE egress line card:
- The interface may become stuck during transmission. The line protocol will continuously flap
because the interface continues to receive keepalives but is not able to send any keepalives.
- The line card generates the following harmless error message:
%EE48-4-GULF_TX_SRAM_ERROR: ASIC GULF: TX bad packet header detected. Details=0x4000
Conditions: These symptoms are observed on a Cisco 12000 series when an invalid packet is
forwarded to an egress interface on an ISE line card.
Workaround: If the transmission on the interface is stuck, reload the line card by entering the
hw-module slot x reload command.
• CSCeh36824
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."