Dell Force10 MXL Blade - Page 670

668 | Debugging and Diagnostics
www.dell.com | support.dell.com
Figure 39-17. Mini application core file naming example
When a member or standby unit crashes, the mini core file gets uploaded to master unit. When the master
unit crashes, the mini core file is uploaded to new master. In the MXL Switch, only the master unit has the
ability to upload the coredump.
Figure 39-18. Mini core text file example
The panic string contains key information regarding the crash. Several panic string types exist, and they are
displayed in regular English text to allow easier understanding of the crash cause.
FTOS#dir
Directory of flash:
1 drw- 16384 Jan 01 1980 00:00:00 +00:00 .
2 drwx 1536 Sep 03 2009 16:51:02 +00:00 ..
3 drw- 512 Aug 07 2009 13:05:58 +00:00 TRACE_LOG_DIR
4 d--- 512 Aug 07 2009 13:06:00 +00:00 ADMIN_DIR
5 -rw- 8693 Sep 03 2009 16:50:56 +00:00 startup-config
6 -rw- 8693 Sep 03 2009 16:44:22 +00:00 startup-config.bak
7 -rw- 156 Aug 28 2009 16:16:10 +00:00 f10StkUnit0.mrtm.acore.mini.txt
8 -rw- 156 Aug 28 2009 17:17:24 +00:00 f10StkUnit0.vrrp.acore.mini.txt
9 -rw- 156 Aug 28 2009 18:25:18 +00:00 f10StkUnit0.sysd.acore.mini.txt
10 -rw- 156 Aug 28 2009 19:07:36 +00:00 f10StkUnit0.frrp.acore.mini.txt
11 -rw- 156 Aug 31 2009 16:18:50 +00:00 f10StkUnit2.sysd.acore.mini.txt
12 -rw- 156 Aug 29 2009 14:28:34 +00:00 f10StkUnit0.ipm1.acore.mini.txt
13 -rw- 156 Aug 31 2009 16:14:56 +00:00 f10StkUnit0.acl.acore.mini.txt
flash: 3104256 bytes total (2959872 bytes free)
FTOS#
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