This document describes the steps necessary for collecting and sending system dumps in AIX Versions 4.1 and 4.2. The section "Collecting the system dump" discusses dump collection, and "Submitting the testcase" describes the various methods of sending testcases. The section "Forcing a system dump" provides information if a valid dump does not result from the initial collection procedure.
For best results, have a tape drive connected to your system before proceeding with the following steps.
Unless the default dump configuration has been modified with the sysdumpdev command, the dump will be copied to /var/adm/ras/vmcore.x when the system is powered on.
NOTE: If /var is too small to hold the dump, the system will prompt the user to copy the dump to external media such as tape or pre-formatted diskettes. If a tape drive is not connected, the system will prompt for diskettes. Using diskettes is NOT a recommended method of collecting a dump. If you are unable to save the dump, IBM will not be able to determine what caused your system to crash.
sysdumpdev -L
Check the sysdumpdev -L output for a valid time-stamp. If the time-stamp matches an approximate time of the system crash, then go to the next section. If the time-stamp does not match OR if the sysdumpdev command does not result in any output, a valid dump was not captured at this time.
NOTE: Overnight and internet submissions are recommended. VM is not a preferred shipment method.
If you are sending the dump on tape, acceptable media are 8mm, 4mm or 1/4" QIC tape.
/usr/sbin/snap -gfkD -o /dev/rmt#.
This copies the unix file image and the error log needed for a complete dump analysis.
NOTE: In the previous instructions, replace /dev/rmt# with the device name for your tape drive (usually /dev/rmt0).
tar -tvf /dev/rmt#
In the output, there should be three lines that look similar to the following:
-rw-r--r-- 1 user group 36243456 Feb 21 10:05 dump.Z -rw-r--r-- 1 user group 176 Feb 20 15:13 dump.snap -rw-r--r-- 1 user group 933536 Feb 20 15:13 unix.Z
NOTE: The file dump.Z may be just dump, and the file unix.Z may be just unix. These files should also be greater than 0 in size. In this case, dump.Z = 453088 bytes and unix.Z = 1270849 bytes.
<customer name> <pmr #, branch #> tape block_size = <xxx> <the command used to copy the information to tape>
NOTE: The tape block size can be obtained with the command:
lsattr -El rmt#
The copy command is generally snap.
IMPORTANT: If the person who is sending the testcase is NOT the person who reported the problem, be sure to include the name of the person who reported it. If the proper information is not on the package, then process delays will occur.
IBM Corp. / Zip 2900 / Bldg 42
Attn: AIX Testcase Dept. J66S
11400 Burnet Road
Austin, TX 78758-3493
Extension 3-4050
NOTE: If you specify Saturday delivery, you must first make special arrangements with an AIX Support specialist. Otherwise, there could be a delay of several days.
sysdumpdev -L
df /tmp
If space is not available to contain the dump, then increase the size of /tmp.
snap -gfkD
cd /tmp/ibmsupt/dump tar -xf/dev/rmt#
snap -c
zcat /tmp/ibmsupt/snap.tar.Z | tar -tvf -
In the output, there should be three lines that look similar to the following:
-rw-r--r-- 1 user group 36243456 Feb 21 10:05 dump.Z -rw-r--r-- 1 user group 176 Feb 20 15:13 dump.snap -rw-r--r-- 1 user group 933536 Feb 20 15:13 unix.Z
If so, go to step 6.
NOTE: The file dump.Z may be just dump, and the file unix.Z may be just unix. These files should also be greater than 0 in size. In this case, dump.Z = 453088 bytes and unix.Z = 1270849 bytes.
zcat /tmp/ibmsupt/snap.tar.Z | tar -tvf -
In the output, there should be three lines that look similar to the following:
-rw-r--r-- 1 user group 36243456 Feb 20 10:05 dump.Z -rw-r--r-- 1 user group 176 Feb 20 15:13 dump.snap -rw-r--r-- 1 user group 933536 Feb 20 15:13 unix.Z
Go to step 6.
NOTE: The file dump.Z may be just dump, and the file unix.Z may be just unix. These files should also be greater than 0 in size. In this case, dump.Z = 453088 bytes and unix.Z = 1270849 bytes.
ad1000.tar.Z
(item number.tar.Z)
1x234.001.tar.Z
(problem_report_#.branch_office_#.tar.Z)
1x234.1234567.tar.Z (problem_report_#.customer_#.tar.Z)
Follow theses steps to ftp the file to the testcase repository:
REMINDER: If you have absolutely no other available electronic method of sending a testcase, you can send it through VNET. This method only works for IBM internal customers. It is not automated, which could cause delays in testcase processing. FTP IS THE PREFERRED METHOD FOR SENDING TESTCASES.
The testcase should be combined into a single compressed tar archive and uploaded in BINARY format.
Please name the file PPPPPBBB TARZBIN, where PPPPP is the PMR number and BBB is the branch office number (without the b).
node = AUSVMR
userid = V3DEFECT
If the system does not respond to mouse or keypad input, then it is in a hung state.
If the user cannot telnet, rlogin, or ping to the system, it is a hung system. Another indication of this is if the user can ping the system but the rest of the system is not available.
It is likely that the system will hang again. If this event recurs, the following steps will prepare the system for a forced dump.
NOTE: In AIX Version 4.1.4 or later, a system dump can be forced without a key switch. The system needs to be initially configured to use this method, which you can do through SMIT by following the fast path.
Run the following command:
smit dump
Change the attribute Always Allow System Dump to TRUE.
When the system hangs again, proceed according to the type of system: