Cisco Cisco Packet Data Gateway (PDG)
System Logs
▀ Configuring and Viewing Crash Logs
▄ ASR 5500 System Administration Guide, StarOS Release 18
168
Step 1
View a list of software crash events by entering the following Exec mode command:
[local]host_name# show crash { all | list | number crash_num }
Notes:
Run show crash list to obtain the number for a specific crash event.
Run show crash number crash_num to display the output for the target crash event.
Important:
Information about similar crash events is suppressed in the output of this command.
Step 2
View the dump file associated with a specific crash event.
The information contained in the dump file helps identify and diagnose any internal or external factors causing the
software to crash.
software to crash.
Crash # – unique number assigned by StarOS when logging the crash event
SW Version – StarOS build release in format: RR.n(bbbbb)
Similar Crash Count – number of similar crashes
Time of first crash – timestamp when first crash occurred in format: YYYY-MMM-DD+hh:mm:ss
Failure message – text of event message
Function – code identifier
Process – where the crash occurred (Card, CPU, PID, etc.)
Crash time – timestamp for when the crash occurred in the format: YYYY-MMM-DD+hh:mm:ss time zone
Recent errno – text of most recent error number.
Stack – memory stack information
Last Bounce – information about the messaging received prior to the crash
Registers – memory register contents
Current inbound message – hexadecimal information for the current inbound message
Address Map
Recent heap activity (oldest first)
Recent events (oldest first)
Profile depth
Important:
The informational content of each crash log entry varies based on the type of crash and the StarOS
release.