![]() ![]() For more details, see Retrieving Information from the Crashinfo File.Ī core dump is a full copy of the router's memory image. For the Cisco 7000 Route Processor (RP), the file is stored by default to flash:crashinfo. ![]() For the Cisco 7500 Versatile Interface Processor 2 (VIP2), this file is stored by default to bootflash: vip2_slot_no_crashinfo where the slot_no is the VIP2 slot number. The crashinfo is written by default to bootflash:crashinfo on the Cisco 12000 Gigabit Router Processor (GRP), the Cisco 70 Route Switch Processors (RSPs), and the Cisco 7200 series routers. When a router crashes due to data or stack corruption, more reload information is needed to debug this type of crash than just the output from the normal show stacks command. The crashinfo file is a collection of useful information related to the current crash, stored in bootflash or flash memory. So most of the time, syslog output is not very useful for troubleshooting crashes. However, when the router is crashing, it might not be able to send the most useful information to this syslog server. If the router is set up to send logs to a syslog server, you will see some information on what happened before the crash on the syslog server. Once the router comes up again, do not forget to get the show stacks output. Keep this information and the logs before it. *** System received a Software forced crash *** If you are connected to the console of the router at the time of the crash, you will see something like this during the crash: This command is useful in collecting general information about the router when you report a problem. This command first appeared in Cisco IOS Software Release 11.2. all the register contents at the time of the crash.signal number, code, and router uptime information.The output displayed from the show context command includes: Context information for different router types could therefore differ. Context information is specific to processors and architectures, whereas software version and uptime information are not. The show context EXEC command is used to display information stored in nonvolatile RAM (NVRAM) when an exception occurs. This command first appeared in Cisco IOS Software Release 10.3. IMPORTANT: If the router is reloaded after the crash (for example, through power-cycle or the reload command), this information will be lost so try to collect it before reloading! The show stacks output is one of the most indispensable sources of information to collect when the router crashes. The show stacks EXEC command is used to monitor the stack usage of processes and interrupt routines. This command first appeared in Cisco IOS Software Release 10.0. IMPORTANT: If the router is reloaded after the crash (for example, if it has been power-cycled or the reload command has been issued), this information will be lost, so try to collect it before reloading! The show version EXEC command displays the configuration of the system hardware, the software version, the names and sources of configuration files and software images, the router uptime, and information on how the system has been restarted. This command first appeared in Cisco IOS ® Software Release 10.0. In order to use Cisco CLI Analyzer, you must be a registered customer, be logged in, and have JavaScript enabled. If you have the output of a show version, show stacks, show context, or show tech support command from your Cisco device, you can use Cisco CLI Analyzer to display potential issues and fixes. These outputs give some indication and information on the crash. All information about the crash, except that which has been successfully stored in the crashinfo file, is lost after a manual reload or power-cycle. When the router crashes, it is extremely important to gather as much information as possible about the crash before you manually reload or power-cycle the router. If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. This document is not restricted to specific software and hardware versions. There are no specific requirements for this document. The ROM monitor identifies the error, prints a message, saves information about the failure, and restarts the system. A "system crash" is a situation where the system has detected an unrecoverable error and has restarted itself. The errors that cause crashes are typically detected by processor hardware, which automatically branches to special error handling code in the ROM monitor. This document describes how to troubleshoot router crashes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |