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

• Commands will be logged whether executed on the vPars database in memory, an alternate
database, or in standalone mode.
• The command line text will be logged on only the partition from which the command was
executed. The logging of the command will not be duplicated to the target syslog file (the
syslog file of the target virtual partition.
For example, if the vparmodify command is executed from winona1 with the target
partition being winona2 (winona1# vparmodify -p winona2 ...), the syslog entries
will only appear in the log file of winona1. Nothing will appear in the log file of winona2.
• Error messages from the failure of a vpar* command execution are not logged.
Additionally, for only vPars A.03.03 and earlier and A.04.02 and earlier:
• When confirmation to execute a vPars command is requested, but the user replies “no”, the
vPars command is not logged.
Syslog and Priority and Facility Codes
With the logging, vPars uses LOG_INFO as the priority level and LOG_USER as the facility.
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 5-2 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
Commands: Displaying vPars Monitor and Resource Information (vparstatus) 141