- Preface
- Overview
- Configure Initial Router Settings on Cisco 4000 Series ISRs
- Basic Router Configuration
- Using Cisco IOS XE Software
- Smart Licensing
- Managing the Device Using Web User Interface
- Console Port, Telnet, and SSH Handling
- Installing the Software
- Installing the Software using install Commands
- Support for Security-Enhanced Linux
- Slot and Subslot Configuration
- Cisco Thousand Eyes Enterprise Agent Application Hosting
- Process Health Monitoring
- System Messages
- Trace Management
- Packet Trace
- Environmental Monitoring and PoE Management
- Factory Reset
- Configuring High Availability
- Secure Sockets Layer Virtual Private Network (SSL VPN)
- Configuring Call Home
- Configuring Bridge Domain Interfaces
- Managing Cisco Enhanced Services and Network Interface Modules
- SFP Auto-Detect and Auto-Failover
- Cellular IPv6 Address
- Radio Aware Routing
- Session Initiation Protocol Triggered VPN
- Configuring Voice Functionality
- Dying Gasp Through SNMP, Syslog and Ethernet OAM
- Support for Software Media Termination Point
- LTE Support on Cisco 4000 Series Integrated Services Router
- Configuration Examples
- System Report
- Unsupported Commands
System Report
System reports or crashinfo files save information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to crash. It is necessary to collect critical crash information quickly and reliably and bundle it in a way that it can be identified with a specific crash occurrence. System reports are generated and saved into the ‘/core’ directory, either on harddisk: or flash: filesystem. The system does not generate reports in case of a reload.
In case of a system crash, the following details are collected:
-
Full process core
-
IOSd core file and IOS crashinfo file if there was an IOSd process crash
-
-
Tracelogs
-
System process information
-
Bootup logs
-
Certain types of /proc information
This report is generated before the router goes down to rommon/bootloader. The information is stored in separate files which are then archived and compressed into the tar.gz bundle. This makes it convenient to get a crash snapshot in one place, and can be then moved off the box for analysis.
Device hostname, the ID of the module that generated the system report and its creation timestamp are embedded in the file name:
<hostname>_<moduleID>-system-report_<timestamp>.tar.gz
Example:
Router1_RP_0-system-report_20210204-163559-UTC
A device with hostname Router1 experienced an unexpected reload of RP0 module and the system-report was generated on 4th February 2021 at 4:39:59 PM UTC.
├── bootflash/ │ └── pd_info/ │ ├── dmesg_output-20210204-163538-UTC.log │ ├── filesystems-20210204-163538-UTC.log │ ├── memaudit-20210204-163538-UTC.log │ ├── proc_cpuinfo-20210204-163538-UTC.log │ ├── proc_diskstats-20210204-163538-UTC.log │ ├── proc_interrupts-20210204-163538-UTC.log │ ├── proc_oom_stats-20210204-163538-UTC.log │ ├── proc_softirqs-20210204-163538-UTC.log │ ├── system_report_trigger.log │ └── top_output-20210204-163538-UTC.log ├── harddisk/ │ ├── core/ │ │ └── Router1_RP_0_hman_17716_20210212-123836-UTC.core.gz │ └── tracelogs/ ├── tmp/ │ ├── fp/ │ │ └── trace/ │ ├── maroon_stats/ │ ├── rp/ │ │ └── trace/ │ └── Router1_RP_0-bootuplog-20210204-163559-UTC.log └── var/ └── log/ └── audit/ └── audit.log