Technical data

Virtual Partitions (vPars) Management on nPartitions
Fault-Tolerant vPar Configurations for nPartitions
HP System Partitions Guide: Administration for nPartitions, rev 5.1 459
The bound attribute value cannot exceed the min attribute, and
so the total of all bound processor attributes for all vPars within
an nPartition also should not exceed the following amount:
[(active_cells - 1) * (processors_per_cell)]
When a bound processor is unavailable, the vPars monitor
assigns and binds a different processor in its place. Thus, even
when some of a vPar’s requested bound processors are
unavailable, the vPar still has the same number of bound
processors requested.
In a multiple-cell nPartition, this guideline for bound and min
processors can accommodate a cell being made inactive or
deleted without preventing any vPars from loading/booting
HP-UX 11i.
❏ The max number of processors for each vPar within an nPartition
can exceed the number of processors assigned to an nPartition.
However, it is not practical to set max to greater than 64 because
HP-UX 11i running on HP Superdome hardware does not
support configurations beyond 64 processors.
❏ The total number of processors for each Virtual Partition can be
any value, but the total processor attribute never needs to be
greater than 64.
To help permit the desired vPar processor configurations to be
loaded and booted, you should ensure that the sum of all vPar
total processor attributes does not exceed the number of
assigned and available processors in the nPartition.
If not enough processors are available for a vPar to be assigned
the configured total , then each vPar is assigned as many
processors as possible after all vPars are assigned their bound
and min processors.
• Fault-Tolerant vPar Input/Output (io) Configuration
You may need to use alternate I/O devices for vPars when nPartition
I/O is unavailable, such as when a cell or I/O chassis is inactive due
to a failure or reconfiguration.
Guidelines for vPar input/output fault tolerance: