HP Integrity Superdome Servers 16- processor Systems Overview page 16

QuickSpecs
Configuration
Partitions Partitions Partitions Partitions Superdome can be configured with hardware partitions, (nPars). Given that Windows Server 2003, SuSE
SLES 9, Red Hat (RHEL) AS 3 and 4, and OpenVMS do not support virtual partitions (vPars), Superdome
systems running Windows Server 2003, Datacenter Edition or *Enterprise Edition, SuSE SLES 9, Red Hat
RHEL AS 3 and 4, or OpenVMS, do not support vPars.
A hardware partition (nPar) consists of one or more cells that communicate coherently over a high
bandwidth, low latency crossbar fabric. Individual processors on a single cell board cannot be separately
partitioned. Hardware partitions are logically isolated from each other such that transactions in one
partition are not visible to the other hardware partitions within the same complex.
Each nPar runs its own independent operating system. Different nPars may be executing the same or
different revisions of an operating system, or they may be executing different operating systems altogether.
Superdome supports HP UX 11i version 2, Windows Server 2003, Datacenter Edition or Enterprise
Edition, SuSE SLES 10, Red Hat RHEL AS 3 and 4, and OpenVMS operating systems. The diagram below
shows a multi OS environment within Superdome. Note: The sx2000 Superdome with Mad9M processors
only supports HP UX 11i version2 and Windows Server 2003, Datacenter Edition or Windows Server
2003, Enterprise Edition.
NOTE: It is possible for PA 8800 and PA 8900 nPars to co exist with Itanium 2 1.6 GHz nPars in the NOTE: NOTE: NOTE:
same Superdome system, but on different partitions. Customers can configure an Itanium 2 1.6 GHz nPar
in an HP 9000 Superdome running PA 8800 or PA 8900 (and vice versa) in the field only. Factory orders
for mixed Itanium and PA RISC nPars are not allowed.
*Enterprise Edition is not supported with mx2 modules.
Each nPar has its own independent processors, memory and I/O resources consisting of the resources of
the cells that make up the partition. Resources (cell boards and/or I/O chassis) may be removed from one
nPar and added to another without having to physically manipulate the hardware, but rather by using
commands that are part of the System Management interface. The table below shows the maximum size
of nPars per operating system:
Maximum size of nPar Maximum size of nPar Maximum size of nPar Maximum size of nPar
Maximum number of Maximum number of Maximum number of Maximum number of
nPars nPars nPars nPars
For information on type of I/O cards for networking and mass storage for each operating environment,
please refer to the Technical Specifications Technical Specifications section of this document. For licensing information for each Technical Specifications Technical Specifications
operating system, please refer to the Ordering Guide.
Superdome supports static partitions. Static partitions imply that any nPar configuration change requires a
reboot of the nPar. In a future HP-UX and Windows release, dynamic nPars will be supported. Dynamic
npars imply that nPar configuration changes do not require a reboot of the nPar. Using the related
capabilities of dynamic reconfiguration (i.e. on-line addition, on-line removal), new resources may be
added to an nPar and failed modules may be removed and replaced while the nPar continues in
operation. Adding new nPars to Superdome system does not require a reboot of the system.
DA - 11717 Worldwide — Version 35 — December 6, 2006
HP Integrity Superdome Servers 16- processor, 32- HP Integrity Superdome Servers 16- processor, 32- HP Integrity Superdome Servers 16- processor, 32- HP Integrity Superdome Servers 16- processor, 32-
HP-UX 11i HP-UX 11i HP-UX 11i HP-UX 11i Windows Windows Windows Windows
Version 2 Version 2 Version 2 Version 2 Server 2003 Server 2003 Server 2003 Server 2003
64 32
processors/128 processors/64
cores, cores, Data
512 GB RAM Center
8
processors/16
cores
Enterprise
Edition
512 GB RAM
16 16
processor, and 64- processor Systems processor, and 64- processor Systems processor, and 64- processor Systems processor, and 64- processor Systems
Red Hat Red Hat Red Hat Red Hat SUSE SLES 9 SUSE SLES 9 SUSE SLES 9 OpenVMS SUSE SLES 9
8 processors 16
(RHEL 3), processors,32
32 processors, cores
64 cores 256 GB RAM
(RHEL4)
512 GB RAM
16 16
OpenVMS OpenVMS OpenVMS
sx1000 - 4
cells with up
to 16 P/16C,
256 GB RAM
sx2000 - 4
cells with up
to 16
Processors/
32 Cores,
512 GB RAM
16
Page 16