HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

NOTE:
nPartition Logs (see also “nPartition Logs” (page 35))
On an nPartition server running vPars, all virtual partitions within an nPartition share the same
console device: the nPartition’s console. Thus, an nPartition’s console log contains console I/O for
multiple virtual partitions. Further, since the vPars Monitor interface is displayed and accessed
through the nPartition’s console, vPars Monitor output is also recorded in the nPartition’s console
log. There is only one vPars Monitor per nPartition.
The server chassis logs record nPartition and server complex hardware events. The chassis logs
do not record vPars-related configuration or vPars boot events; however, the chassis logs do record
HP-UX "heartbeat" events. The server chassis logs are viewable from the GSPs Show Chassis Log
menu. For more information, see the Help within the GSPs online help.
The vPars Monitor event logs record only vPars events; it does not contain any nPartition chassis
events. For more information, see vparstatus(1M).
Also, for a given nPartition, the Virtual Front Panel (VFP) of the nPartition’s console displays an OS
heartbeat whenever at least one virtual partition within the nPartition is up.
Commands: Displaying vPars Monitor and Resource Information (vparstatus)
The vPars Monitor and the partition database maintains information about all the virtual partitions,
including the current state of the virtual partitions and their resources. Using the shell command
vparstatus, you can display this information. This section describes the possible virtual partition
states and the common usages of the vparstatus command.
Virtual Partition States
Virtual partitions can be in the following states:
Table 26 Virtual Partition States
DescriptionState
The vPars Monitor is loading the kernel image of the virtual partition. This is the first step of booting a
virtual partition. If successful, the state moves to boot.
load
The vPars Monitor has successfully loaded the kernel image and is continuing with the boot process. If
the launch is successful, the state moves to up.
boot
The virtual partition is up and running.up
The virtual partition is shutting down gracefully. Once the partition is shutdown, the state moves to down.shut
The virtual partition is down.down
The virtual partition is crashing because of a panic (HPMC, TOC, etc.). Once the partition has completed
crashing, the state moves to down.
crash
The virtual partition is not responding.hung
The virtual partition is in a database file that is not active, so it has no state. The database file can be
inactive because either the system is in standalone mode (the vPars Monitor is not running) or the database
file acted upon is an alternate database file that is not in vPars Monitor memory.
N/A
vparstatus Output Examples
The next few pages show examples of using the vparstatus command:
• “vparstatus: Summary Information” (page 141)
• “vparstatus: Verbose Information” (page 142)
• “vparstatus: Available Resources” (page 144)
140 vPars Monitor and Shell Commands