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

Introduction
Supported Environments
Chapter 116
documentation for more information on running MC/Service Guard
with vPars.
• Glance and Openview Performance Agent (MeasureWare)
For correct reporting of CPU utilization, you need to run Glance and
MeasureWare versions C.03.35.00 or higher. For correct reporting of
interrupt-enabled CPUs, you need kernel patch PHKL_22987
installed.
• PSets (Processor Sets)
In the current release of vPars, you cannot specify a hardware path
for an unbound CPU. Therefore, to avoid unintentionally removing
unbound CPUs from a non-default pset, initially create the partition
that will be running PSets using only bound CPUs. Then, when you
add or remove an unbound CPU, the unbound CPU will be added to or
removed from only the default pset.
• Ignite/UX
Before using Ignite/UX to install or recover vPars, you will need to
update your Ignite computer. For more information, see “Updating
Your Ignite Server” on page 62.
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
32.
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 computer. 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 computer 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 43.
make_tape_recovery is not supported for vPars computers. 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 45.