HP-UX Virtual Partitions Ordering and Configuration Guide (March 2012)

Table 13 Maximum Number of Virtual Partitions Per Server (continued)
Maximum Number of Virtual PartitionsServer Model
8 virtual partitions per system. This is a 2-cell system.rp7405, rp7410
8 virtual partitions per nPartition. This is a 2-cell system.rp7420, rp7440, rx7620, rx7640
8 virtual partitions per nPartition, 16 total per system with
no SEU and 32 total per system with SEU. This is a 4-cell
system.
rp8400
8 virtual partitions per nPartition, 16 total per system with
no SEU and 32 total per system with SEU. This is a 4-cell
system.
rp8420, rp8440, rx8620, rx8640
8 virtual partitions per nPartition, where the nPartition is a
maximum of 8 cells; 128 total per Superdome system for
the 128-way Superdome systems, where the nPartition is
a maximum of 8 cells. Note that vPars can now span
multiple cabinets.
Superdome (PA-RISC), Superdome (Integrity)
16 virtual partitions per nPartition
per blade 4 vPars; per SD2-8 processor sockets 16
vPars; per SD2-16 processor sockets 32 vPars
Superdome 2 (SD2) (Integrity)
Notes about Maximum Number of Virtual Partitions
Table 13 assumes single path to I/O; if dual path is used, as in many mission critical
environments, then the recommended and maximum numbers may be half of that stated.
The number of virtual partitions can be limited by the number of available IO slots.
For PA-RISC systems, the number of virtual partitions can be limited by the size of the kernels.
In short, the sum of the kernel sizes must be less than 2GBs. See “Memory Allocation in the
HP-UX Virtual Partitions Administrator Guide for more information.
NOTE: The maximum vPars in an nPar is 16. The maximum number of blades for single nPar is
16. The maximum number of cores per vPar is >64 cores (Intel (R) Itanium(R) 9100 processors or
older) or >128 cores (Intel (R) Itanium(R. 9300 processors).
4.2.5 Minimum Virtual Partition Requirements
Each virtual partition requires a minimum of:
1 processing core
Enough memory to run HP-UX 11i and applications. See the applicable HP-UX Install and
Update Guide for your OS for the minimum amount of memory.
1 unique boot device connected through SCSI or Fiber Channel card on a PCI bus or a Local
Bus Adapter (LBA) that is uniquely owned by that virtual partition)
1 unique LAN card on a PCI-bus/LBA that is uniquely owned by that virtual partition. On
Integrity systems, the LAN card must be bootable if you are installing the OE onto a virtual
partition using Ignite-UX. See the Chapter 4 of the HP-UX Virtual Partitions Administrator Guide
for more information on how vPars uses Ignite-UX.
Notes about Minimum Virtual Partition Requirements
Each PCI bus/LBA is uniquely owned by 1 virtual partition. Therefore, the internal LAN card
and storage connections (associated with each core I/O card) can only be owned by a single
virtual partition. All other virtual partitions require a separate LAN card for network connection,
and external storage (and associated SCSI/FC connections to that storage for boot).
An LBA is typically equivalent to one I/O slot.
4.2 Hardware 31