Reference Guide

Debugging and Diagnostics | 263
Figure 13-19. Mini Core Text File Example
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
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.
Kernel Core Dumps
The kernel core dump can be large and may take up to 5 to 30 minutes to upload. FTOS does not overwrite
application core dumps; you should delete them as necessary to conserve space on the flash. If the flash is
out of memory, the coredump is aborted. On the S-Series, if the FTP server is not reachable, the application
coredump is aborted. FTOS completes the coredump process and waits until the upload is complete before
rebooting the system.
TCP Dumps
TCP dump captures CPU-bound control plane traffic to improve troubleshooting and system
manageability. When enabled, a TCP dump captures all the packets on the local CPU, as specified in the
CLI.
The traffic capture files can be saved 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 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.
Task Command CommandMode
Enable coredump on a stack logging coredump stack-unit {0-5/all} CONFIGURATION