
639
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S2
Conditions: This symptom is observed on a Cisco 12000 series, that functions as a PE router, and
that is located in the network core when a SPA that is installed in the SIP interconnects the PE router
with a P router.
Workaround: There is no workaround.
• CSCsd37840
Symptoms: When a Cisco 7500 series that runs in SSO mode reloads (for example, because of a
“c7500 CCB PLAYBACK” error), the active RP comes up properly but the standby RP crashes.
When the router reloads while running in RPR+ mode, the standby RP does not crash but an
“%HA-3-SYNC_ERROR: CCB Playback error” message is generated.
Conditions: This symptom is observed on a Cisco 7500 series that is configured for SSO or RPR+.
Workaround: There is no workaround. The symptom does not occur when you disable SSO or RPR+.
• CSCsd38657
Symptoms: An RP crashes when a Gigabit Ethernet interface of a SPA is shut down. When this
situation occurs, the following error message and traceback is generated:
Unexpected exception to CPUvector 700, PC = 2CEE34 -Traceback= 2CEE34 4C40000 2D8958
2D8D2C 2C1164 14048C 2CFB4C
If a crashinfo file is generated, the last log message is the following:
%SYS-6-STACKLOW: Stack for process CEF process running low, 0/6000
On a router that is configured with two RPs that function in RPR+ mode, when the RP crashes, a
switchover occurs. However, the crashed RP does not come up and remains in standby mode.
Conditions: These symptoms are observed on a Cisco router when the recursive lookup on a static
MPLS route does not specify a next hop interface. For example, the symptom occurs when the ip
route destination-prefix mask next-hop1 command is enabled but does not occur when the ip
route destination-prefix mask interface1 next-hop1 command is enabled.
Workaround: Ensure that the interface argument is included in the static route, as in the following
command: ip route destination-prefix mask interface1 next-hop1.
• CSCsd40253
Symptoms: Aggregated Output NetFlow may aggregate output traffic on an incorrect prefix (such
as 0.0.0.0/0) on a PE router that functions in an MPLS VPN environment.
Conditions: This symptom is observed on a SIP-600 that is installed in a Cisco 12000 series that runs
Cisco IOS Release 12.0(32)S when egress traffic streams are sent in different routing contexts (via
the global routing table and via a VRF or different VRFs) and when Aggregated Output NetFlow is
enabled using a Prefix-ToS aggregation scheme.
The symptom occurs for both IP-to-IP and tag-to-IP traffic (the latter one from the MPLS core). The
symptom does not occur when the egress traffic is within the same routing context, that is, when all
egress interfaces are either in the global routing table or in the same VRF).
Workaround: There is no workaround.
• CSCsd43102
Symptoms: On a GSR router configured for MVPN, the reload of any E3 Edge facing line card can
cause VRF mroutes to be missing on the reloaded line card while they are present on PRP and on
other line cards. This will cause punts to PRP CPU and, depending on number of missing mroutes,
potentially high PRP CPU utilization due to IP Input.
Conditions: This symptom has been observed to happen in a scaled MVPN environment and is
triggered only by linecard reload.
Comentarios a estos manuales