Installing and Managing HP-UX Virtual Partitions (A.02.01)

How vPars Works
Virtual Consoles
Chapter 2 43
— From a running partition, reset the partition that owns the
hardware console port by executing vparreset -p
target_partition -h, where target_partition is the
partition that owns the hardware console port.
— From a running partition, boot the partition that owns the
hardware console port by executing vparboot -p
target_partition, where target_partition is the partition
that owns the hardware console port
If no other virtual partitions are accessible, you must reboot the
server or hard partition in order to regain console input.
CAUTION The first virtual partition that you create must own the LBA (local bus
adapter) that contains the physical hardware console port. For an
example, see “Ensuring the Hardware Console Port Is Owned by the
First Virtual Partition” on page 73.
Logs on a nPartition Server
On a nPartition server running vPars, all virtual partitions within a
nPartition share the same console device: the nPartition’s console.
Thus, a 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 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
GSP’s Show Chassis Log menu. For more information, see the Help
within the GSP’s 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).