Configuring Software Crash Log Destinations - Cisco ASR 5500 System Administration Manual

Hide thumbs Also See for ASR 5500:
Table of Contents

Advertisement

Configuring Software Crash Log Destinations

2 The associated minicore, NPU or kernel dump file is stored in the /flash/crsh2 directory.
3 A full core dump is stored in a user configured directory.
Important
The following behaviors apply to the crash logging process.
• When a crash event arrives on an active management card, the event record is stored in its crashlog2
• When a crash log entry is deleted via CLI command, it is deleted on both the active and standby
• When a management card is added or replaced, active and standby cards will automatically synchronize
• When a crash event is received and the crash log file is full, the oldest entry in the crash log and its
• Duplicate crash events bump the count of hits in the existing record and update the new record with the
Configuring Software Crash Log Destinations
The system can be configured to store software crash log information to any of the following locations:
• On the ASR 5500:
• On VPC
• Network Server: Any workstation or server on the network that the system can access using the Trivial
Important
ASR 5500 System Administration Guide, StarOS Release 21.5
144
The crashlog2 file along with associated minicore, NPU and kernel dumps are automatically synchronized
across redundant management cards (SMC, MIO/UMIO). Full core dumps are not synchronized across
management cards.
file along with the minicore, NPU, or kernel dump file in /flash/crsh2. The crash event and dump file
are also automatically stored in the same locations on the standby management card.
management cards.
crash logs and dump files.
related dump file will be replaced with the latest arrived event and dump file on both management cards.
Information for a maximum of 120 crash events can be stored on management cards.
old crash record. Additions to the count use the timestamp for the first time the event happened.
◦ Flash memory: Installed on the active MIO/UMIO [abridged crash log and associated dump files
only]
◦ USB memory stick: Installed in the USB slot on the active MIO/UMIO
◦ Flash memory: Accessible by the virtual machine
◦ USB memory stick: Installed in the USB slot of the platform (USB slot has been enabled via the
hypervisor)
File Transfer Protocol (TFTP), the File Transfer Protocol (FTP), the Secure File Transfer Protocol
(SFTP), or the Hyper-Text Transfer Protocol (HTTP); this is recommended for large network deployments
in which multiple systems require the same configuration
In release 20.0 and higher Trusted StarOS builds, FTP is not supported.
System Logs

Advertisement

Table of Contents
loading

Table of Contents