RDBGC0.ge0 : 34 +24
RDBGC1.ge0 : 366 +235
RDBGC5.ge0 : 16 +12
RDBGC7.ge0 : 18 +12
GR64.ge0 : 5,176 +24
GR127.ge0 : 1,566 +1,433
GR255.ge0 : 4 +4
GRPKT.ge0 : 1,602 +1,461
GRBYT.ge0 : 117,600 +106,202
GRMCA.ge0 : 366 +235
GRBCA.ge0 : 12 +9
GT64.ge0 : 4 +3
GT127.ge0 : 964 +964
GT255.ge0 : 4 +4
GT511.ge0 : 1 +1
GTPKT.ge0 : 973 +972
GTBCA.ge0 : 1 +1
GTBYT.ge0 : 71,531 +71,467
RUC.cpu0 : 972 +971
TDBGC6.cpu0 : 1,584 +1,449=
Enabling Application Core Dumps
Application core dumps are disabled by default.
A core dump file can be very large. Due to memory requirements the file can only be sent directly to an
FTP server; it is not stored on the local flash.
To enable full application core dumps, use the following command.
• Enable RPM core dumps and specify the Shutdown mode.
CONFIGURATION mode
logging coredump server
To undo this command, use the no logging coredump server command.
Mini Core Dumps
The Dell Networking OS supports mini core dumps on the application and kernel crashes. The mini core
dump applies to Master, Standby, and Member units.
Application and kernel mini core dumps are always enabled. The mini core dumps contain the stack
space and some other minimal information that you can use to debug a crash. These files are small files
and are written into flash until space is exhausted. When the flash is full, the write process is stopped.
A mini core dump contains critical information in the event of a crash. Mini core dump files are located in
flash:/ (root dir). The application mini core filename format is f10StkUnit<Stack_unit_no>.<Application
name>.acore.mini.txt. The kernel mini core filename format is f10StkUnit<Stack_unit_no>.kcore.mini.txt.
The following are sample filenames.
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.
308 Debugging and Diagnostics