HP-UX HB v13.00 Ch-17 - vPars

HP-UX Handbook – Rev 13.00 Page 43 (of 46)
Chapter 17 Virtual Partitions (vPars)
October 29, 2013
Use vparreset -t (for TOC) from another running virtual partition to perform a soft reset on a
vPar. For example, if vpar2 is hung, we can execute vparreset from the running partition vpar1:
vpar1# vparreset -p vpar2 -t
The target virtual partition either shuts down or reboots according to the setting of the autoboot
attribute of that virtual partition.
Other virtual partitions are unaffected by one virtual partition’s reset.
Note: Unlike the RS and TC commands, the vparreset command also displays Processor
Information Module (PIM) data unless the -q option is specified.
The target virtual partition on cell-based systems will not be rebooted until all the virtual
partitions within the nPartition are shut down and the virtual partition monitor is rebooted.
The monitor dump
If the monitor crashes, the whole nPar and all vPars on it go down.
On PA-RISC, the monitor writes a dump to /stand/vpmon.dmp. This file is also present on a
running vPar. The file reserved the space to save the crashdump for the Monitor.
On Integrity, the Monitor dump is written to the file vpmon.dmp in the EFI partition of the
monitor’s boot disk. The file can be found at fsN:/efi/hpux/vpmon.dmp.
When the virtual partition owning the monitor’s boot disk is booted, the following files will be
created in /var/adm/crash/vpar:
 vpmon ( copy of the executable image of the monitor at dump time)
 vpmon.dmp (monitor dump file)
 summary (analysis of the crash including PIM info for each CPU)
All three files should be collected for analysis. The HP-UX crash dumps from running virtual
partitions may also be required.
A quick way to check, if there is a crash dump in a vpmon.dmp file, is to run the following
command:
$ strings /stand/vpmon.dmp | egrep -v 'ZDUMP_IMAGE_LIST|VPAR Monitor Memory Image'
VPAR
VPAR indicates no available crash dump.