Cisco Cisco IOS Software Release 12.0(22)S
Postswitchover Core Dump
Prerequisites
3
Cisco IOS Release: Multiple releases (see the Feature History table)
Prerequisites
Redundant RPs must be running Cisco IOS Release 12.0(18)ST or a later release.
Configuration Tasks
None.
No new commands or configuration tasks were implemented for this feature. Refer to “Troubleshooting
the Router” in the “System Management” part of the Cisco IOS Configuration Fundamentals
Configuration Guide, Release 12.2, for information on how to configure the networking device for a core
dump.
the Router” in the “System Management” part of the Cisco IOS Configuration Fundamentals
Configuration Guide, Release 12.2, for information on how to configure the networking device for a core
dump.
Verifying Postswitchover Core Dump
Step 1
Configure the networking device to perform a core dump following a processor failure. For information
on how to configure the networking device for a core dump, refer to “Troubleshooting the Router” in the
“System Management” part of the Cisco IOS Configuration Fundamentals Configuration Guide,
Release 12.2.
on how to configure the networking device for a core dump, refer to “Troubleshooting the Router” in the
“System Management” part of the Cisco IOS Configuration Fundamentals Configuration Guide,
Release 12.2.
Step 2
Contact your Cisco TAC representative to assist you in generating a core dump file.
Step 3
Verify that the core dump file was written to the preconfigured location and that it has the same filename
that was configured on the networking device. Confirm that the core dump file is appended with the slot
number of the previously active processor.
that was configured on the networking device. Confirm that the core dump file is appended with the slot
number of the previously active processor.
Troubleshooting Tips
The Core Dump Process Appears Slow
Check that the software images running on the processors are compatible. If for any reason the
Cisco IOS software image on the newly active processor is incompatible with the software image
running on the previously active processor, the Postswitchover Core Dump feature will not use the newly
active processor for dumping the system core information. Instead, the failed processor will use existing
processes for writing the core file to Flash memory or to a network file; however, this method will slow
down the switchover process. Contact your Cisco TAC representative for assistance.
Cisco IOS software image on the newly active processor is incompatible with the software image
running on the previously active processor, the Postswitchover Core Dump feature will not use the newly
active processor for dumping the system core information. Instead, the failed processor will use existing
processes for writing the core file to Flash memory or to a network file; however, this method will slow
down the switchover process. Contact your Cisco TAC representative for assistance.
The Core Dump File Is Missing
If the Cisco software image on the newly active processor software is compatible with the software
running on the previously active processor, but the processor-to-processor communication is not
successful, the core dump information will not be written to a file. Contact your Cisco TAC
representative for assistance.
running on the previously active processor, but the processor-to-processor communication is not
successful, the core dump information will not be written to a file. Contact your Cisco TAC
representative for assistance.
Line Card Dump Information Is Taking a Long Time
If the networking device experiences one or more line card failures at the same time that the newly active
primary processor is writing the core dump information from the failed primary processor, the line card
information will be written to a file; however, this process might take more time than for a failed RP
alone. Contact your Cisco TAC representative for assistance.
primary processor is writing the core dump information from the failed primary processor, the line card
information will be written to a file; however, this process might take more time than for a failed RP
alone. Contact your Cisco TAC representative for assistance.