|
|
Overview
| HP Integrity Superdome Servers: 16- processor, 32- processor, and 64- processor Systems |
![]() |
![]() |
| At A Glance | |||
| The latest release of Superdome, HP Integrity
Superdome supports the new and improved sx2000 chip set. The Integrity Superdome with the sx2000 chipset supported the Mad9M Itanium processor at initial release. HP Integrity Superdome currently supports the following processors: sx2000
sx1000
The November 2007 release of Montvale is accompanied by the release of a new I/O chassis for Superdome. The mixed interface I/O chassis supports six slots of PCI-Express (PCIe) and six slots of PCI-X. The abbreviation PCIeX is used below to discuss this product. HP sx1000 Integrity Superdome supports mixing the Intel Itanium 1.6-GHz/9M
processor and the HP mx2 processor module in the same system, but in different
partitions, as long as they have the same chipset. All cell boards to
be mixed in a system must contain the same chipset, sx1000 or sx2000,
but not both. HP Integrity sx1000 Superdome supports mixing the Itanium
1.6-GHz/9M processor, PA 8800 and PA 8900 processors in the same system,
but in different partitions, again only with the same chipset, sx1000.
HP Integrity sx2000 Superdome supports mixing the dual core Intel Itanium
1.6 GHz, Itanium 1.6 GHz processor and PA 8900 processors in the same
system, but in different partitions, again only with the same chipset,
sx2000. Throughout the rest of this document, the term HP sx1000 Integrity Superdome with Itanium 2 1.6 GHz processors or mx2 processor modules will be referred to as simply "Superdome sx1000." The HP sx2000 Integrity Superdome with dual core Itanium processors or single core Itanium 2 processors will be referred to as "Superdome sx2000." Integrity Superdome (with Itanium processors) showcases HP's commitment to delivering a 64 processor Intel Itanium server and superior investment protection. It is the dawn of a new era in high end computing with the emergence of commodity based hardware. Superdome supports a multi OS environment. Currently, HP UX, Windows Server 2008, and Windows Server 2003, Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), and OpenVMS are shipping with Integrity Superdome sx1000. Customers can order any combination of HP UX 11i v2, Windows Server 2003 Datacenter Edition, Windows Server 2003 Enterprise Edition, Windows Server 2008 for Itanium-based Systems, RHEL 4 or 5, SLES 9 or10 or OpenVMS running in separate hard partitions. With the release of HP Superdome sx2000 with dual core Intel Itanium
processors, HP-UX, Windows Server 2003, Windows Server 2008, OpenVMS,
and Linux are all supported in separate hard partitions. Some details of each Operating Environment offered by
Superdome are listed below. |
|||
| | |||
| HP-UX 11i version 2 (sx1000 & sx2000 systems) |
|
||
|
|
|||
| Windows Server 2008 for Itanium-based Systems (sx1000 and sx2000 Superdome servers) and Windows Server 2003, Datacenter Edition or Enterprise Edition for Itanium (sx1000 and sx2000 Itanium systems) |
NOTE: Windows Server 2003, Enterprise Edition is not supported with mx2 modules |
||
|
|
|||
| Red Hat Enterprise Linux
4 and 5, SUSE Linux Enterprise Server 10 (sx2000 systems) Red Hat Enterprise Linux 3 and 4, SUSE Linux Enterprise Server 9 and 10 (sx1000 Itanium systems) |
|
||
|
|
|||
| OpenVMS |
|
||
|
|
|||
| Superdome Service Solutions |
Superdome continues to provide the same positive Total Customer Experience via industry-leading HP Services, as with existing Superdome servers. The HP Services component of Superdome is as follows:
| ||
|
|
Standard Features
| NOTE:
HP Integrity Superdome (sx2000) supports all 4 OEs with either Montvale
or Montecito processors NOTE: HP Superdome (sx2000) systems (Itanium 2 (1.6 GHz) '"Mad9M") support only HP-UX and Windows. |
| Minimum/Maximum Configurations for Superdome (sx1000 and sx2000) with Intel Itanium Processors (all versions) |
| System Size |
Minimum Configuration
|
Maximum Configuration
(One Partition) |
|||||||
|
HP UX
11i v2//v3 |
Windows Server 2008 for Itanium-based Systems; Windows
2003
Datacenter Edition and Enterprise Edition4 |
Red Hat RHEL AS3 & 4and SuSE SLES 9 & 10
(sx1000 only) |
OpenVMS version 8.2 1 (or higher)3
|
HP-UX 11i V2
|
Windows Server 2008 for Itanium-based Systems;
Windows 2003 Datacenter/ *Enterprise Edition4 |
SUSE
SLES 9 (sx1000 only) |
Red Hat
RHEL AS 4 (sx1000 only) |
OpenVMS version 8.2 1 (or higher)3
|
|
| 16 Processors | |||||||||
| Processors |
2
|
2
|
2
|
2
|
16
|
16/
*8 |
16
|
16
|
16
|
| Memory |
2 GB
|
2 GB
|
2 GB
|
2 GB
|
256 GB/
512 GB (sx2000) |
256 GB (sx1000 with DC Edition)/
512GB (sx2000 with DC Edition)/ 128 GB (sx1000 with EE)/ 256 GB (sx2000 with EE) |
256 GB
|
256 GB
|
256 GB
|
| Cell Boards |
1
|
1
|
1
|
1
|
4
|
4 /
*2 |
4
|
4
|
4
|
| PCI-X Chassis |
1
|
1
|
1
|
1
|
4
|
4/
*2 |
2
|
2
|
4
|
| Max nPARS |
1
|
1
|
1
|
1
|
4
|
4/
*2 |
4
|
4
|
4
|
| 32-Processors | |||||||||
| Processors |
2
|
2
|
NS
|
2
|
32
|
32/
*8 |
NS
|
NS
|
16
|
| Memory |
2 GB
|
2 GB
|
N/A
|
2 GB
|
512 GB/
256 GB (sx2000) |
512 GB (sx1000 with DC Edition)/
1024 GB (sx2000 with DC Edition)/ 128 GB (sx1000 with EE)/ 256 GB (sx2000 with EE) |
N/A
|
N/A
|
256 GB
|
| Cell Boards |
1
|
1
|
N/A
|
1
|
8
|
8 /
*2 |
N/A
|
N/A
|
4
|
| PCI-X Chassis |
1
|
1
|
N/A
|
1
|
8
|
8/
*2 |
N/A
|
N/A
|
4
|
| Max nPARS |
1
|
1
|
1
|
1
|
8 (1)
|
81/
*2 |
N/A
|
N/A
|
8(1)
|
| 64 Processors | |||||||||
| Processors |
4
|
4
|
NS
|
2
|
64
|
64/
*8 |
NS
|
NS
|
16
|
| Memory |
6 GB
|
6 GB
|
N/A
|
2 GB
|
1024 GB/
2048 GB (sx2000) |
1024 GB (both sx1000 and sx2000 with DC Edition)/
128 GB (sx1000 with EE)/ 256 GB (sx2000 with EE) |
N/A
|
N/A
|
256 GB
|
| Cell Boards |
2
|
2 (Datacenter Edition or Enterprise Edition)
|
N/A
|
1
|
16
|
16 /
*2 |
N/A
|
N/A
|
4
|
| PCI-X Chassis |
1
|
1
|
N/A
|
1
|
16
|
16/
*2 |
N/A
|
N/A
|
4
|
| Max nPARS |
1
|
1
|
N/A
|
1
|
16 (2)
|
162/
*2 |
N/A
|
N/A
|
16 (2)
|
| N/A = Not applicable; NS = Not Supported | |||||||||
| 1Requires
I/O expansion cabinet if more than 4 nPARS 2Requires I/O expansion cabinet if more than 8 nPARS 31.6 Ghz Mad9M Processors only on sx1000 configurations for OpenVMS 4Windows Server 2003, Enterprise Edition is not support with mx2 modules. *HP Superdome (sx2000) systems (Itanium 1.6 GHz "Mad9M") support only HP UX and Windows Server. |
|||||||||
| Minimum/Maximum Configurations for Superdome (sx2000) with Dual core Intel Itanium Processors (both Montvale and Montecito) |
|
Minimum Configuration
|
Maximum Configuration (One Partition)
|
|||||||||
|
HP-UX 11i V2
|
Windows Server 2008 for Itanium-based Systems;
Windows 2003 Datacenter Edition and Enterprise Edition |
SLES10 |
Red Hat R4
|
OpenVMS V8.3 (or higher)3
|
HP-UX 11i V2
|
Windows Server 2008 for Itanium-based Systems;
Windows 2003 Datacenter/ Enterprise Edition |
SLES 10
|
Red Hat
RHEL 4 |
OpenVMS version 8.3 (or higher)3
|
|
|
16 Processors / 32 Cores
|
||||||||||
| Processors/ cores |
1/1
|
1/1
|
1/1
|
1/1
|
1/1
|
16/32
|
Datacenter 16/32;
Enterprise 8/16 |
16/32
|
16/32
|
16/32
|
| Memory |
2 GB
|
2 GB
|
4 GB
|
4GB
|
2 GB
|
512 GB
|
Datacenter
512 GB; Enterprise256 GB |
512 GB
|
512 GB
|
512 GB
|
| Cell Boards |
1
|
1
|
1
|
1
|
1
|
4
|
Datacenter 4;
Enterprise 2 |
4
|
4
|
4
|
| PCIeX Chassis |
1
|
1
|
1
|
1
|
1
|
4
|
Datacenter 4;
Enterprise 2 |
4
|
4
|
4
|
| PCI X Chassis |
1
|
1
|
1
|
1
|
1
|
4
|
Datacenter 4;
Enterprise 2 |
4
|
4
|
4
|
| Maximum nPars |
N/A
|
N/A
|
N/A
|
N/A
|
N/A
|
4
|
Datacenter 4;
Enterprise 2 |
4
|
4
|
4
|
|
32 Processors / 64 Cores
|
||||||||||
| Processors / Cores |
1/1
|
1/1
|
1/1
|
1/1
|
1/1
|
32/64
|
Datacenter 32/64;
Enterprise 8/16 |
32/64
|
32/64
|
16/32
|
| Memory |
2 GB
|
2 GB
|
4 GB
|
4 GB
|
2 GB
|
1024 GB
|
Datacenter 1024 GB;
Enterprise 256 GB |
1024 GB
|
1024 GB
|
512 GB
|
| Cell Boards |
1
|
1
|
1
|
1
|
1
|
8
|
Datacenter 8;
Enterprise 2 |
8
|
8
|
4
|
| PCIeX Chassis |
1
|
1
|
1
|
1
|
1
|
8
|
Datacenter 8;
Enterprise 2 |
8
|
4
|
4
|
| PCI X Chassis |
1
|
1
|
1
|
1
|
1
|
8
|
Datacenter 8; Enterprise 2
|
8
|
4
|
4
|
| Maximum nPars |
N/A
|
N/A
|
1
|
N/A
|
N/A
|
81
|
Datacenter 81; Enterprise 2
|
81
|
81
|
81
|
| 64 Processors / 128 Cores | ||||||||||
| Processors / Cores |
2/2
|
2/2
|
2/2
|
2/2
|
1/1
|
64/128
|
Datacenter 32/64; Enterprise 8/16
|
64/128
|
64/128
|
16/32
|
| Memory |
16 GB
|
16 GB
|
16 GB
|
16 GB
|
2 GB
|
2048 GB
|
Datacenter 1024 GB; Enterprise
256 GB |
2048 GB
|
2048 GB
|
512 GB
|
| Cell Boards |
2
|
2
|
2
|
2
|
1
|
16
|
Datacenter 16;
Enterprise 2 |
16
|
16
|
4
|
| PCIeX Chassis |
1
|
1
|
1
|
1
|
1
|
16
|
Datacenter 16; Enterprise 2
|
8
|
6
|
4
|
| PCI X Chassis |
1
|
1
|
1
|
1
|
1
|
16
|
Datacenter 16; Enterprise 2
|
8
|
6
|
4
|
| Maximum nPars |
1
|
1
|
1
|
1
|
1
|
162
|
Datacenter 162; Enterprise 2
|
16 2
|
16 2
|
162
|
| 1Requires
I/O expansion cabinet if more than 4 nPars 2 Requires I/O expansion cabinet if more than 8 nPars 3 Dual core Montecito processors only on sx2000 configurations for OpenVMS and Linux |
||||||||||
| Standard Hardware Features |
Superdome with Intel Itanium and Dual core Itanium Processors Standard Hardware Features
|
||||||||
| The
HP Integrity (sx1000) Superdome servers may require a firmware update to
support Intel Itanium 2 Processor/Cell Add on products shipping after June
15, 2005.
Affected Intel Itanium 2 processor products for
the Integrity (sx1000) Superdome are:
ACTION: NOTE: For sx1000 configurations, OpenVMS requires firmware version rel_6.0 or later and for for systems with PA RISC and Integrity partitions, firmware version rel_6.1 or later. NOTE: Once the firmware is at the supported revision level, proceed with attaching the Processor/Cell Add-On Products to the server using the Service Guide. The Service Guide is available at http://docs.hp.com. |
|||||||||
| Minimum/Maximum Configurations for Superdome with mx2 Processor Modules (sx1000 systems only) |
| System Size |
Minimum Configuration
|
Maximum Configuration
(One Partition) |
||
|
HP-UX 11i V2
|
Windows Server 2008 and Windows Server 2003
Datacenter |
HP-UX 11i V2
|
Windows Server 2008 and Windows Server 2003
Datacenter |
|
| 16 Processors | ||||
| Processors Memory Cell Boards PCI-X Chassis Max nPARS |
2
|
2
|
32
|
32
|
|
2 GB
|
2 GB
|
256 GB
|
256 GB
|
|
|
1
|
1
|
4
|
4
|
|
|
1
|
1
|
4
|
4
|
|
|
Not applicable
|
Not applicable
|
4
|
4
|
|
| 32-Processors | ||||
| Processors Memory Cell Boards PCI-X Chassis Max nPARS |
2
|
2
|
64
|
64
|
|
2 GB
|
2 GB
|
512 GB
|
512 GB
|
|
|
1
|
1
|
8
|
8
|
|
|
1
|
1
|
8
|
8
|
|
|
Not applicable
|
Not applicable
|
8 (1)
|
8 (1)
|
|
| 64-Processors | ||||
| Processors Memory Cell Boards PCI-X Chassis Max nPARS |
6
|
6
|
128
|
64
|
|
6 GB
|
6 GB
|
1024 GB
|
1024 GB
|
|
|
3
|
3
|
16
|
16
|
|
|
1
|
1
|
16
|
16
|
|
|
Not Applicable
|
Not Applicable
|
16 (2)
|
16 (2)
|
|
| Standard Hardware Features |
|
|||
| (1) Requires
I/O Expansion cabinet if more than 4 nPARS (2) Requires I/O Expansion cabinet if more than 8 nPARS |
||||
|
|
Configuration
| There are three basic building blocks in the Superdome system architecture: the cell, the crossbar backplane and the PCI-X based I/O subsystem. |
|
|
| Cabinets (sx1000 & sx2000) |
Starting with the sx1000 chip set, Superdome servers have been released with the graphite color. A Superdome system will consist of up to four different types of cabinet assemblies:
Superdome cabinets will be serviced from the front and rear of the cabinet only. This will enable customers to arrange the cabinets of their Superdome system in the traditional row fashion found in most computer rooms. The width of the cabinet will accommodate moving it through common doorways in the U.S. and Europe. The intake air to the main (cell) card cage will be filtered. This filter is removable for cleaning/replacement while the system is fully operational. A status display is located on the outside of the front and rear doors of each cabinet. The customer and field engineers can therefore determine basic status of each cabinet without opening any cabinet doors. Superdome 16 processor and Superdome 32 processor systems are available in single cabinets. Superdome 64 processor systems are available in dual cabinets. Each cabinet may contain a specific number of cell boards (consisting of processors and memory) and I/O. See the following sections for configuration rules pertaining to each cabinet. |
||
|
|
|||
| Cells (Processors and Memory) | A cell, or cell
board, is the basic building block of a Superdome system. It is a symmetric
multi processor (SMP), containing up to four processor modules and up to
16 GB of main memory using 512-MB DIMMs (sx1000 only) in 32 memory slots,
up to 32 GB of main memory using 1 GB DIMMs, up to 64 GB of main memory
using 2 GB DIMMs, and up to 128 GB of main memory using 4-GB DIMMS (sx2000
only). It is also possible to mix DIMM sizes on the same cell board. A connection
to a 12 slot PCI X card cage is optional for each cell. Each hard partition
must be connected to at least one PCI-X I/O card cage.
The Superdome cell boards shipped from the factory are offered with 1, 2, 3, or 4 processors. The Superdome cell board contains:
|
||
|
|
|||
| Crossbar Backplane | sx2000: Each backplane contains
three independent crossbar fabrics resulting in a robust highly available
system. A High speed serial (HSS) link technology is employed for crossbars
interconnect. Each backplane cabinet can support up to eight cells. Eight
cells support a 32 processor module Superdome. Two backplanes (two cabinets)
can be linked together with flex cables to produce a complex that can support
up to 16 cells resulting in a 64 processor module Superdome (128 core dual
core Itanium or 64 core Itanium (Mad9M)).
sx1000: Each crossbar backplane contains two sets of two crossbar chips that provide a non blocking connection between eight cells and the other backplane. Each backplane cabinet can support up to eight cells. A backplane supporting four cells results in a 16 processor Superdome (16 core Itanium Madison or 32 core Itanium mx2). Similarly, a backplane supporting eight cells would result in a 32 processor Superdome (32 core Itanium Madison or 64 core Itanium mx2). Two backplanes can be linked together with flex cables to produce a cabinet that can support up to 16 cells resulting in a 64 processor Superdome (64 core Itanium Madison or 128 core Itanium mx2). |
|
|
|
| I/O Subsystem |
Each I/O chassis provides twelve I/O slots.
|
|
|
|
| Core I/O (required by sx1000 systems only, sx2000 systems do not have a core I/O) | The core I/O in Superdome provides
the base set of I/O functions required by every Superdome partition. Each
partition must have at least one core I/O card in order to boot. sx2000
systems must have I/O cards with at least LAN connectivity as its "core"
I/O capability in each partition. Multiple core I/O cards may be present
within a partition (one core I/O card is supported per I/O backplane); however,
only one may be active at a time. Core I/O will utilize the standard long
card PCI X form factor but will add a second card cage connection to the
I/O backplane for additional non PCI X signals (USB and utilities). This
secondary connector will not impede the ability to support standard PCI
X cards in the core slot when a core I/O card is not installed.
Any I/O chassis can support a Core I/O card that is required for each independent partition. A system configured with 16 cells, each with its own I/O chassis and core I/O card could support up to 16 independent partitions. Note that cells can be configured without I/O chassis attached, but I/O chassis cannot be configured in the system unless attached to a cell. |
|
|
|
| HP-UX Core I/O (A6865A)(sx1000 systems only, sx2000 systems do not have a core I/O) |
The core I/O card's primary functions are:
|
|||||
| Other common functions, such as Ultra/Ultra2 SCSI, Fibre Channel, and Gigabit Ethernet, are not included on the core I/O card. These functions are, of course, supported as normal PCI-X add-in cards. | ||||||
| The unified 100Base-T Core LAN driver code searches to verify whether there is a cable connection on an RJ-45 port or on an AUI port. If no cable connection is found on the RJ-45 port, there is a busy wait pause of 150 ms when checking for an AUI connection. By installing the loopback connector (description below) in the RJ-45 port, the driver would think an RJ-45 cable was connected and would not continue to search for an AUI connection, hence eliminate the 150 ms busy wait state | ||||||
|
||||||
|
|
||||||
| Core I/O (A6865A and optional VGA/USB A6869A/A6869B)- (sx1000 systems only, sx2000 systems do not have core I/O) | For Windows Server 2003 and Windows Server 2008, Windows does not support the 10/100 LAN on the A6865A core I/O card, a separate Gigabit Ethernet card such as the A7061A, A7073A, A9899A, or A9900A is required. The use of Graphics/USB card (A6869A/A6869B) is optional and not required. NOTE: A6869A is not supported on systems with the sx2000 chipset. |
|
|
|
| Linux Core I/O (A6865A)(sx1000 systems only, sx2000 systems do not have core I/O) |
The core I/O card's primary functions are:
Other common functions, such as Ultra/Ultra2 SCSI, Fibre Channel, and Gigabit Ethernet, are not included on the core I/O card. These functions are supported as normal PCI-X add-in cards. |
|
|
|
| OpenVMS Core I/O (A6865A)(sx1000 systems only, sx2000 systems do not have core I/O) |
The core I/O card's primary functions are:
Other common functions, such as Ultra320 SCSI, Fibre Channel, and Gigabit Ethernet, are not included on the core I/O card. These functions are supported as normal PCI X add in cards. |
|
|
|
| I/O Expansion Cabinet | The I/O expansion functionality is physically partitioned into four rack-mounted chassisthe I/O expansion utilities chassis (XUC), the I/O expansion rear display module (RDM), the I/O expansion power chassis (XPC) and the I/O chassis enclosure (ICE). Each ICE supports up to two 12-slot PCI-X chassis. |
|
|
|
| Field Racking |
The only field rackable I/O expansion components are the ICE and the 12-slot I/O chassis. Either component would be field installed when the customer has ordered additional I/O capability for a previously installed I/O expansion cabinet. No I/O expansion cabinet components will be delivered to be field installed in a customer's existing rack other than a previously installed I/O expansion cabinet. The I/O expansion components were not designed to be installed in racks other than Rack System E or the new Universal 10K G2 rack. In other words, they are not designed for Rosebowl I, pre merger Compaq, Rittal, or other third party racks. The I/O expansion cabinet is based on a modified HP Rack System E and the new Universal 10K G2 and all expansion components mount in the rack. Each component is designed to install independently in the rack. The Rack System E and the Universal 10K G2 cabinet have been modified to allow I/O interface cables to route between the ICE and cell boards in the Superdome cabinet. I/O expansion components are not designed for installation behind a rack front door. The components are designed for use with the standard Rack System E and the Universal 10K G2 perforated rear door. |
|
|
|
| I/O Chassis Enclosure (ICE) | The I/O chassis enclosure (ICE)
provides expanded I/O capability for Superdome. Each ICE supports up to
24 PCI X slots by using two 12 slot Superdome I/O chassis. The I/O chassis
installation in the ICE puts the PCI X cards in a horizontal position. An
ICE supports one or two 12 slot I/O chassis. The I/O chassis enclosure (ICE)
is designed to mount in an HP Universal 10K G2 rack and consumes 9U of vertical
rack space.
To provide online addition/replacement/deletion access to PCI or PCI-X cards and hot-swap access for I/O fans, all I/O chassis are mounted on a sliding shelf inside the ICE. Four (N+1) I/O fans mounted in the rear of the ICE provide cooling for the chassis. Air is pulled through the front as well as the I/O chassis lid (on the side of the ICE) and exhausted out the rear. The I/O fan assembly is hot swappable. An LED on each I/O fan assembly indicates that the fan is operating. |
|
|
|
| Cabinet Height and Configuration Limitations |
Although the individual I/O expansion cabinet components are designed for installation in an HP Universal 10K G2 rack, rack size limitations have been agreed upon. In order to allay service access concerns, the factory will not install IOX components higher than 1.6 meters from the floor. Open space in an IOX cabinet will be available for peripheral installation. Refer to the 10K G2 Series Rack Best Practices Guide for information on rack deployment, stabilization, and transportation. Go to: http://www.hp.com/go/rackandpower for more information. |
| | |
| Peripheral Support | All peripherals qualified for use with Superdome and/or for use in a Universal 10K G2 are supported in the I/O expansion cabinet as long as there is available space. Peripherals not connected to or associated with the Superdome system to which the I/O expansion cabinet is attached may be installed in the I/O expansion cabinet. |
|
|
|
| Server Support |
No servers except those required for Superdome system management such as Superdome Support Management Station or ISEE may be installed in an I/O expansion. Peripherals installed in the I/O expansion cabinet cannot be powered by the XPC. Provisions for peripheral AC power must be provided by a PDU or other means. |
|
|
|
| Standalone I/O Expansion Cabinet | If an I/O expansion cabinet is ordered alone, its field installation can be ordered via option 750 in the ordering guide. |
|
|
|
| DVD Solution | The DVD solution for Superdome requires the following components. These components are required per partition. External racks A4901A and A4902A must also be ordered with the DVD solution. Note: One DVD is required and one DAT is recommended per nPartition. | |||||||||||||||||||||||
| NOTE: One DVD and one DAT is required per nPartition. | ||||||||||||||||||||||||
| NOTE: For OpenVMS, only the one DVD is required per nPartition. | ||||||||||||||||||||||||
| Superdome DVD Solutions | ||||||||||||||||||||||||
|
||||||||||||||||||||||||
|
10.5-meter HD HDTS68 is required if DDS-4 or DDS-5 is used. |
||||||||||||||||||||||||
|
|
||||||||||||||||||||||||
| Partitions |
Superdome can be configured with hardware partitions, (nPars). Superdome systems running Windows Server 2008 for Itanium-based Systems, Windows Server 2003, Datacenter Edition or Enterprise Edition , SUSE Linux Enterprise Server, Red Hat Enterprise Linux, or OpenVMS, do not support virtual partitions (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 and electrically 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 and 3, Windows Server 2008 for Itanium-based
Systems, and Windows Server 2003, Datacenter Edition or Enterprise Edition,
SUSE SLES 9 and 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 3 , and Windows Server 2008 for Itanium-based Systems, Windows Server 2003, Datacenter Edition or Windows Server 2003, Enterprise Edition (does not support any version of Linux or OpenVMS) NOTE: It is possible for PA 8800
and PA 8900 nPars to co exist with Itanium 1.6 GHz nPars in the same Superdome
system, but on different partitions. Customers can configure an Itanium
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. 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: |
|||||||||||||||||
|
||||||||||||||||||
|
For information on type of I/O cards for networking and mass storage for each operating environment, please refer to the Technical Specifications section of this document. For licensing information for each operating system, please refer to the Ordering Guide. Superdome,supports static hard partitions (nPars) on all operating environments.
Static partitions imply that any nPar configuration change requires a
reboot of the nPar. |
||||||||||||||||||
|
|
||||||||||||||||||
| Windows Server 2008, Datacenter edition for Itanium-based systems - HP Product Structure |
Product Number T8704A Options:
|
|
|
|
| Windows Server 2003, Enterprise Edition for Itanium based Systems-HP Product Structure |
Product Number T8768A Options:
NOTE: See Windows 2003 and/pr Windows Server 2008 Ordering Section for further information. Not available/supported in Japan. Windows Server 2003, Enterprise Edition is not supported with mx2 modules. |
|
|
|
| Mixing of PA-RISC and Itanium Cells in Superdome |
1) Which processors can be mixed in a Superdome? The first step in determining which processors can be mixed within a Superdome is to look at the chipset. A Superdome can only support one type of chipset (legacy chipset, sx1000, or sx2000 chipset) at a time. The legacy chipset only supports the PA RISC architecture. The PA 8600, PA 8700, and PA 8700+ processors were supported with this chipset. As a result, they can be mixed within the Superdome but they cannot be mixed with processors supported by other chipsets (i.e., Itanium 9M with the sx1000 chipset). With the sx1000 chipset, processors of like architectures (PA RISC and Itanium architectures) that are supported by the sx1000 chipset can be mixed in separate hard partitions. For example, the HP 9000 Superdome supports mixing the PA 8800 and PA 8900 processors in separate hard partitions. The HP Integrity Superdome supports mixing the Itanium 9M processors as well as the mx2 dual processor module in separate hard partitions. In addition, a subset of the PA RISC and Itanium processors (PA 8800, PA 8900 and Itanium 9M processors) can be supported at the same time in different hard partitions within a Superdome. With the sx2000 chipset, dual core Itanium (Montecito and Montvale) and
Itanium 1.6 GHz (Mad9M) processors, and PA-8900 are the supported processors
and like above, all of these types of processors can be mixed in separate
hard partitions. The table below highlights which processors can co-exist on a Superdome in separate hard partitions. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
2) In order to run an Itanium-based partition in an Integrity server, what changes are required? In order to add a new partition with Itanium 9M processors on an HP 9000 Superdome, the following steps are required: Step #1: Upgrade firmware on PA-RISC based partitions Step #2: Create a new hard partition in the Superdome for Itanium based cell (s) Step #3: Plug in cell boards for Itanium based cells Step #4: Some I/O cards may need to be added for that specific hard partition (Windows does not support the identical set of I/O cards that HP-UX 11i supports) Step #5: Load operating system for Itanium based partition Upgrading a PA-RISC partition to support Itanium processors would require similar steps: Step #1: Upgrade firmware on PA-RISC based partitions Step #2: Pull out existing PA-RISC cell boards Step #3: Swap existing memory into cell boards for Intel Itanium processor (protects investment in current memory) Step #4: Plug in cell boards for Itanium based cell boards Step #5: Some I/O cards may need to be added for that specific hard partition (Windows does not support the identical set of I/O cards that HP-UX 11i supports) Step #6: Load operating system for Itanium based partition
3) Is mixing of PA-RISC and Itanium processors factory configurable? No. HP supports PA RISC systems that shipped from the factory adding Itanium partitions later on in the field. In addition, HP offers the ability to enable Itanium based systems that shipped from the factory to add PA RISC partitions later on in the field (this will happen less frequently) HP does not allow PA RISC partitions to be added to Intel Itanium-based
Integrity systems that shipped from the factory. Mixing of sx1000 and
sx2000 chipsets in the same system is NOT supported. 4) How long does it take to add an Itanium-based partition in an HP 9000 customers? The effort required to add an Itanium-based partition to an HP 9000 Superdome is slightly more than what is required to add a new PA-RISC-based partition. In both cases you have to create a new hard partition in the Superdome, plug in cell boards for the new processors and load the operating system. There are no hardware changes required to support mixing of processor types. The only known difference at this time is that a customer would need to upgrade the firmware to support the Itanium arch | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||