Setup Guide

f10Ch<Chassis ID>_lp<slot#>_<Process Name>_<timestamp>.acore.gz
An application core dump generated from LM:
f10Ch<Chassis ID>_lp<slot#>_<Process Name>_<timestamp>.acore.gz
Where cpu species a system’s CPU and is one of the following values: cp (Control Processor), rp (Route Processor), lp0 (line-card
processor 0), lp1 (line-card processor 1), or lp2 (line-card processor 2);
application species the name of the executable that has crashed;
timestamp is a text string in the format: yymmddhhmmss (YearMonthDayHourMinuteSecond).
You can also congure the system to automatically move (upload) an application core dump to an external FTP server. Use the logging
coredump server
server-ip-address username ftp-username password ftp-password command in global
conguration mode to congure an FTP server.
When you enter the logging coredump server command, you are required to enter a password. Use the password of the FTP
server where the core les are to be copied. The password can be up to 15 characters; special characters are allowed. After you enter the
password, an FTP URL is created with the credentials in the operating system. The CLI monitors application core dumps in the unit.
NOTE: On the system, when you enable core dumps of application crashes to be uploaded to an FTP server, only core dumps
from the Control Processor are uploaded to the server. Application core-dump les from the Route Processor and line-card
CPUs are moved to ash memory on the Control Processor CPU and can be accessed by performing an FTP to the Control
Processor (CP) core-dump directory:
The application core-dump le for the Route Processor is stored at: ash:/
CORE_DUMP_DIR
/
f10rp_
application
_
timestamp
.acore.gz
The application core-dump le for a line-card processor is stored at:ash:/
CORE_DUMP_DIR
/f10lp
slot-
number
_
application
_
timestamp
.acore.gz
To disable the automatic uploading of application core dumps, enter the no logging coredump server command.
Mini Core Dumps
Dell Networking OS supports mini core dumps for kernel crashes. The mini core dump applies to Master units.
Kernel mini core dumps are always enabled. The mini core dumps contain the stack space and some other very minimal information that
can be used to debug a crash. These les are small les and are written into ash until space is exhausted. When the ash is full, the write
process is stopped.
A mini core dump contains critical information in the event of a crash. Mini core dump les are located in ash://CORE_DUMP_DIR
directory. The kernel mini core lename in the RPM has the following formats:
Kernel mini core dump generated from CP of the RPMs:
f10Ch<Chassis ID>_rpm<0/1>_cp_<timestamp>.kcore.mini.txt
Kernel mini cored ump from RP CPU:
f10Ch<Chassis ID>_rpm<0/1>_rp_<timestamp>.kcore.mini.txt
Kernel mini core dump from LP CPU:
f10Ch<Chassis ID>_lp<slot#>_<timestamp>.kcore.mini.txt
The Kernel mini core dump generated from the LM:
f10Ch<Chassis ID>_lp<slot#>_<timestamp>.kcore.mini.txt
The panic string contains key information regarding the crash. Several panic string types exist, and they are displayed in regular english text
to enable easier understanding of the crash cause.
Example of a Mini Core Text File
VALID MAGIC
------------------------PANIC STRING -----------------
panic string is : <null>
----------------------STACK TRACE START---------------
Debugging and Diagnostics
347