Chapter 2: Service Menus
Retrieving a Crash Dump File
Quantum DXi6900 G2 Field Service Manual
55
l
Transferring the Crash Dump File on page 58
Accessing the Crash Dump File
There are several ways of accessing a crash dump file:
l
Use WebEx to remotely access the customer system.
l
If the customer is using Guardian, access the customer system remotely using Guardian.
l
Use WinSCP to remotely access the customer system
l
Attach to the DXi6900 G2 system directly using
ServiceLogin
access.
Note:
During the time when the crash dump file is being moved to the
/snfs/Kdumps
directory, the
system will be unavailable or in Limited Mode. This can take up to 30 minutes to complete.
Regardless of the method used to access the DXi6900 G2 system, the crash dump file is stored in the
following directory:
/snfs/Kdumps/
1. Once you are logged into the DXi6900 G2 system,
grep
for
KDUMP
messages in the messages file to see
if the crash dump file is available.
# grep KDUMP /var/log/messages
Jul 02 11:43:48 Flames KDUMP: CRIT : KERNEL PANIC/OOPS/CRASH has occurred
Jul 02 11:43:50 Flames KDUMP: INFO :
*********begin
stack traces ********
Jul 02 11:44:26 Flames KDUMP:
PID: 30096
TASK: ffff8107a9d0e140
CPU: 2
COMMAND:
"bash"
Jul 02 11:44:27 Flames KDUMP:
#0 [ffff8103dbb3bd20] machine_kexec at
ffffffff80218c3b
Jul 02 11:44:27 Flames KDUMP:
#1 [ffff8103dbb3bde0] crash_kexec at
ffffffff8024fc96
Jul 02 11:44:27 Flames KDUMP:
#2 [ffff8103dbb3bea0] sysrq_handle_crashdump at
ffffffff803715d9
Jul 02 11:44:27 Flames KDUMP:
#3 [ffff8103dbb3beb0] __handle_sysrq at
ffffffff803717c6
Jul 02 11:44:27 Flames KDUMP:
#4 [ffff8103dbb3bef0] write_sysrq_trigger at
ffffffff802b658c
Jul 02 11:44:27 Flames KDUMP:
#5 [ffff8103dbb3bf10] vfs_write at ffffffff8027bc75
Jul 02 11:44:27 Flames KDUMP:
#6 [ffff8103dbb3bf40] sys_write at ffffffff8027bdca
Jul 02 11:44:27 Flames KDUMP:
#7 [ffff8103dbb3bf80] system_call at
ffffffff80209e5e
Jul 02 11:44:27 Flames KDUMP:
RIP: 00002b659e2d2302
RSP: 00007fff0cbaaa50
RFLAGS:
00010203
