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

HP-UX Handbook – Rev 13.00 Page 44 (of 46)
Chapter 17 Virtual Partitions (vPars)
October 29, 2013
Note: On PA-RISC, /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
The vPars monitor is not a HP-UX kernel and 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.
The vPars Monitor Event Log
In any running virtual partition extract the monitor's event log:
# vparextract -l
There is one instance of the monitor at /stand/vpmon, and one log file only. No need to run the
command in every partition!
If no HP-UX instances are running, use the monitor's log command to get similar information:
MON> log
The monitor log is very important to track eproblems on a running vPar. Any console outputs or
GSP logs that seem relevant are also appreciated.
The tool vpars-collect
The vpars-collect.sh script is useful to collect vPars configuration and version information.
vpars-collect.sh runs a number of commands including vparstatus(1m) and vparextract.
vpars-collect.sh must be run as root. You need to run the script run in one virtual partition
only to collect the complete information for all.
The script collects the outputs in /var/tmp. The directory name includes the hostname and
process ID.
Upon completion, the outputs are packaged twice, first into a .tar.gz file suitable for transfer to
HP, and a (nearly) complete subset in a <hostname>.txt file that can be mailed without using
MIME, or attached to a CR in Chart.
vpars-collect and some additional tools can be found at: http://wtec.cup.hp.com/~hpux/vm-
pm/vpars/tools.htm (HP Internal).