Monitor Crash Dump

Directory Location and Filenames

When a virtual partition crashes, the monitor dump file is initially written to a pre-existing file /stand/vpmon.dmp.

Subsequently, when the virtual partition boots, the following files are created in /var/adm/crash/vpar (where n is a number representing the nth occurrence of a dump):

	NOTE: /stand/vpmon.dmp is a special file. Do not delete, move, rename, or modify this file. If you need to look at the contents of the monitor dump file, use the vpmon.dmp.n file located in /var/adm/crash/vpar.

Monitor Dump Analysis Tool

Because the vPars monitor is not a HP-UX kernel, you cannot use a kernel dump analysis tool to examine a monitor dump file. Contact your HP Support Representative to analyze the monitor dump file.

	NOTE: TOC and Kernel Dumps: If a TOC (transfer of control) for the entire hard partition is generated either through a Ctrl-B TC command or by an OS of a virtual partition, a kernel dump will not automatically be saved to /var/adm/crash for those partitions that have not previously had a kernel dump occur. You can save their dumps to /var/adm/crash by performing the following on each of those virtual partitions: Obtain of list of dump devices, noting the DEVICE and OFFSET information: # crashconf -v DEVICE OFFSET(kB) SIZE(kB) LOGICAL VOL. NAME -------------- ---------- --------- ------------- -------------- 31:0X022000 314208 4194304 64:0X000002 /dev/vg00/lvol2 The DEVICE is 31:0X022000, and the OFFSET is 314208. Map the minor number from the DEVICE information to a device file: # ls -l /dev/dsk | grep "022000" brw-r----- 1 bin sys 31 0x022000 Oct 13 2001 c2t2d0 The corresponding device file is /dev/dsk/c2t2d0. Using the OFFSET information and the device file, save the dump to /var/adm/crash: # savecrash -r -f -D /dev/dsk/c2t2d0 -O 314208