HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

Table 5-2 Virtual Partition States (continued)
DescriptionState
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 143)
• “vparstatus: Verbose Information” (page 144)
• “vparstatus: Available Resources” (page 146)
• “vparstatus: Pending Migrating CPUs Operations” (page 151)
• “vparstatus: Dual-Core CPUs” (page 150)
• “vparstatus: CPU Information on vPars A.04/A.05” (page 148)
• “vparstatus: Pending Migrating Memory Operations” (page 152)
• “vparstatus: Pending nPartition Reboot for Reconfiguration” (page 154)
• “vparstatus: vPars Monitor and Database Information” (page 155)
NOTE:
• Actual vparstatus output differs from version to version of vPars. Depending on your
version and system, the output shown below may differ. For detailed usage, syntax, and
information, see the manpage vparstatus(1M) on your vPars system.
• The kernel path shown in the vparstatus output is the kernel path set in the vPars database.
This may differ from the actual kernel in use.
142 vPars Monitor and Shell Commands