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

Introduction
Supported Environments
Chapter 1 27
When Ignite-UX reports the Total Number of CPUs for a partition, it
includes unassigned unbound CPUs in the count. For information on
bound and unbound CPUs, see “Bound and Unbound CPUs” on
page 48.
For example, if you have three virtual partitions, each with one
bound CPU, and two unbound CPUs not assigned to any of the
partitions, this is a total of five CPUs in the server. Ignite-UX will
report three CPUs (one bound and two unbound CPUs) for each
partition. However, adding up the numbers results in a total of nine
CPUs for the server when there are actually only five physical CPUs.
• Ignite-UX Recovery and Expert Recovery
Ignite-UX Recovery via make_net_recovery requires additional
steps as noted in “Ignite-UX Network Recovery” on page 59.
make_tape_recovery is not supported for vPars servers. You need to
use make_net_recovery.
Expert recovery works as documented in the Ignite-UX manual;
however, you must account for the vPars differences described in
“Expert Recovery” on page 62.
• Ignite-UX and other Curses Applications
On the virtual console, when using applications that use curses, such
as the terminal versions of Ignite-UX and SAM, do not press Ctrl-A
to toggle to the console display window of another virtual partition
while you are still within the curses application. This is especially
applicable when you are using vparboot -I and the Ignite-UX
application to install vPars. For more information on curses, see the
curses_intro (3X) manpage.
• UPS (uninterruptible power supply) software
UPS hardware communicates with UPS software via the serial port.
By default, a hard partition has only one serial port. For a vPars
hard partition, the serial port can be owned by at most one virtual
partition. Therefore, on a vPars hard partition, the UPS can
communicate with only the virtual partition that owns the serial
port.
Alternately, the HP PowerTrust II-MR UPS product can be
configured across virtual partitions using network connections,
providing all the virtual partitions reside on the same network.