Administrator Guide

• 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---------------
0035d60c <f10_save_mmu+0x120>:
00274f8c <panic+0x144>:
0024e2b0 <db_fncall+0x134>:
0024dee8 <db_command+0x258>:
0024d9c4 <db_command_loop+0xc4>:
002522b0 <db_trap+0x158>:
0026a8d0 <mi_switch+0x1b0>:
0026a00c <bpendtsleep>:
------------------------STACK TRACE END----------------
---------------------------FREE MEMORY---------------
uvmexp.free = 0x2312
Full Kernel Core Dumps
The system supports full core dumps for kernel crashes. The kernel core dump applies to all switch CPUs and is not enabled by default. To
enable full kernel core dumps, enter the logging coredump command in global configuration mode. The kernel core dump is copied to
flash://CORE_DUMP_DIR/f10_cpu_timestamp.kcore.gz
Where cpu specifies a switch CPU and is one of the following values: cp (Control Processor), cp (Route Processor), lp0 (line-card
processor 0), lp1 (line-card processor 1), or lp2 (line-card processor 2);
timestamp is a text string in the format: yyyyddmmhhmmss (YearDayMonthHourMinuteSecond).
To disable the full kernel and other core dumps, enter the no logging coredump command.
The Kernel full core dump name in RPM’s uses the following formats:
• Kernel full core dump generated from CP of the RPMs
f10Ch<Chassis ID>_rpm<0/1>_cp_<timestamp>.kcore.gz
• Kernel full core dump from RP application
f10Ch<Chassis ID>_rpm<0/1>_rp_<timestamp>.kcore.gz
• Kernel full core dump from LP application
f10Ch<Chassis ID>_lp<slot#>_<timestamp>.kcore.gz
Enabling TCP Dumps
A TCP dump captures CPU-bound control-plane traffic to improve troubleshooting and system manageability. You can perform a TCP
dump on the Control Processor (CP) and Route Processor (RP) CPUs.
When you enable TCP dumps, a dump captures all the packets on the local CPU, as specified in the CLI.
You can save the traffic capture files to flash, to FTP, SCP, or TFTP. The files saved on the flash are located in the flash://
TCP_DUMP_DIR/tcpdump_<time_stamp_dir>/ directory and are labeled tcpdump_*.pcap. There can be up to 20
tcpdump_<time_stamp_dir> directories. The file after 20 overwrites the oldest saved file. The maximum file size for a TCP dump capture
is 1MB. When a file reaches 1MB, a new file is created, up to the specified total number of files.
Maximize the number of packets recorded in a file by specifying the snap-length to capture the file headers only.
The tcpdump command has a finite run process. When you enable the command, it runs until the capture-duration timer and/or the
packet-count counter threshold is met. If you do not set a threshold, the system uses a default of 5 minute capture-duration and/or a
single 1k file as the stopping point for the dump.
310
Debugging and Diagnostics