HP PA-8600 User manual

This subchapter pertains to all HP 9000 Superdome servers (running PA-8600, PA-8700, PA-8800, or PA-8900 processors) for all
markets. With Superdome, HP launches a new strategy to ensure a positive Total Customer Experience is achieved via industry
leading HP Services. Our experience has shown us that large solution implementations most often succeed as a result of appropriate
skills and attention being applied to the solution design and implementation. To address this on the implementation side, for
Superdome, HP is responding to Customer and Industry feedback and delivering Superdome Configurations via three, pre
configured Services levels: Critical Service, Proactive Service, and Foundation Service. With Superdome, we introduced a new role,
the TCE Manager, who manages the fulfillment of an integrated business solution based on customer requirements. For each
customer account, the TCE Manager will facilitate the selection of the appropriate configuration. For ordering instructions, please
consult the ordering guide.
Superdome Service Solutions
Superdome Service SolutionsSuperdome Service Solutions
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 described here:
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Overview
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 1

Solution Life Cycle
Solution Life CycleSolution Life Cycle
Solution Life Cycle HP customers have consistently achieved higher levels of satisfaction when key components of their IT
infrastructures are implemented using the Solution Life Cycle
Solution Life CycleSolution Life Cycle
Solution Life Cycle . The Solution Life Cycle focuses on rapid
productivity and maximum availability by examining customers' specific needs at each of five distinct
phases (plan, design, integrate, install, and manage) and then designing their Superdome solution
around those needs.
Service Solutions
Service SolutionsService Solutions
Service Solutions HP offers three pre configured service solutions for Superdome that provide customers with a choice of
lifecycle services to address their own individual business requirements.
Foundation Service Solution:
Foundation Service Solution:Foundation Service Solution:
Foundation Service Solution: This solution reduces design problems, speeds time to production,
and lays the groundwork for long term system reliability by combining pre installation preparation
and integration services, hands on training and reactive support. This solution includes HP Support
Plus 24 to provide an integrated set of 24×7 hardware and software services as well as software
updates for selected HP and third party products.
Proactive Service Solution:
Proactive Service Solution:Proactive Service Solution:
Proactive Service Solution: This solution builds on the Foundation Service Solution by enhancing
the management phase of the Solution Life Cycle with HP Proactive 24 to complement your
internal IT resources with proactive assistance and reactive support. Proactive Service Solution
helps reduce design problems, speed time to production, and lay the groundwork for long term
system reliability by combining pre installation preparation and integration services with hands on
staff training and transition assistance. With HP Proactive 24 included in your solution, you
optimize the effectiveness of your IT environment with access to an HP certified team of experts that
can help you identify potential areas of improvement in key IT processes and implement necessary
changes to increase availability.
Critical Service Solution:
Critical Service Solution:Critical Service Solution:
Critical Service Solution: Mission Critical environments are maintained by combining proactive
and reactive support services to ensure maximum IT availability and performance for companies
that can't tolerate downtime without serious business impact. Critical Service Solution
encompasses the full spectrum of deliverables across the Solution Lifecycle and is enhanced by HP
Critical Service as the core of the management phase. This total solution provides maximum
system availability and reduces design problems, speeds time to production, and lays the
groundwork for long term system reliability by combining pre installation preparation and
integration services, hands on training, transition assistance, remote monitoring, and mission
critical support. As part of HP Critical Service, you get the services of a team of HP certified experts
that will assist with the transition process, teach your staff how to optimize system performance,
and monitor your system closely so potential problems are identified before they can affect
availability.
Other Services
Other ServicesOther Services
Other Services HP's Mission Critical Partnership:
HP's Mission Critical Partnership:HP's Mission Critical Partnership:
HP's Mission Critical Partnership: This service offering provides customers the opportunity to
create a custom agreement with Hewlett Packard to achieve the level of service that you need to
meet your business requirements. This level of service can help you reduce the business risk of a
complex IT infrastructure, by helping you align IT service delivery to your business objectives,
enable a high rate of business change, and continuously improve service levels. HP will work with
you proactively to eliminate downtime, and improve IT management processes.
Service Solution Enhancements:
Service Solution Enhancements:Service Solution Enhancements:
Service Solution Enhancements: HP's full portfolio of services is available to enhance your
Superdome Service Solution in order to address your specific business needs. Services focused
across multi operating systems as well as other platforms such as storage and networks can be
combined to compliment your total solution
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Overview
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 2

NOTE:
NOTE:NOTE:
NOTE: Given that PA-8600/PA-8700 are single core processors and PA-8800 and PA-8900 are dual core processors, the columns
listed in this table refer to 16 processor, 32 processor and 64 processor. This terminology refers to 16 cores, 32 cores and 64 cores
for Superdome PA-8600/PA-8700 and 32 cores, 64 cores and 128 cores for Superdome PA-8800 and PA-8900 systems.
System Size
System SizeSystem Size
System Size Minimum System
Minimum SystemMinimum System
Minimum System Maximum SPU Capacities
Maximum SPU CapacitiesMaximum SPU Capacities
Maximum SPU Capacities
16 Processors
16 Processors16 Processors
16 Processors PA-8600 or
PA-8600 orPA-8600 or
PA-8600 or
PA-8700
PA-8700PA-8700
PA-8700
PA-8800 or PA-8900
PA-8800 or PA-8900PA-8800 or PA-8900
PA-8800 or PA-8900 PA-8600 or
PA-8600 orPA-8600 or
PA-8600 or
PA-8700
PA-8700PA-8700
PA-8700
PA-8800 or PA-8900
PA-8800 or PA-8900PA-8800 or PA-8900
PA-8800 or PA-8900
Processor cores 1 1 16 32
Memory 2 GB 2 GB 64 GB 256 GB
Cell Boards 1 Cell Board 1 Cell Board 4 Cell Boards 4 Cell Boards
PCI Chassis 1 12-slot chassis 1 12-slot chassis 4 12-slot chassis 4 12-slot chassis
32 Processors
32 Processors32 Processors
32 Processors
Processor cores 1 2 32 64
Memory 2 GB 2 GB 128 GB 512 GB
Cell Boards 1 Cell Board 1 Cell Board 8 Cell Boards 8 Cell Boards
PCI Chassis 1 12-slot chassis 1 12-slot chassis 8 12-slot chassis 8 12-slot chassis
64 Processors
64 Processors64 Processors
64 Processors
Processor cores 6 2 64 128
Memory 6 GB 6 GB 256 GB 1024 GB
NOTE:
NOTE:NOTE:
NOTE: 512 GB per
partition
Cell Boards 3 Cell Boards 2 Cell Boards 16 Cell Boards 16 Cell Boards
PCI Chassis 1 12-slot chassis 1 12-slot chassis 16 12-slot chassis 16 12-slot chassis
Standard Features
Standard FeaturesStandard Features
Standard Features Redundant Power Supply
Redundant Fans
HP-UX operating system with unlimited user license
Factory Integration of memory and I/O Cards
Installation Guide, Operators Guide, and Architecture Manual
HP Site planning and Installation
One year warranty with same business day on-site service response
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Standard Features
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 3

There are three basic building blocks in the Superdome system architecture: the cell, the crossbar backplane, and the I/O
subsystem. Please note that Superdome with PA-8800 and PA-8900 is based on a different chip set (sx1000 or sx2000) than
Superdome with PA-8600 or PA-8700. For more information on the sx1000 and sx2000 chip sets, please refer to: HP Integrity
Superdome QuickSpec .
Cabinets
CabinetsCabinets
Cabinets A Superdome system can consist of up to four different types of cabinet assemblies:
At least one Superdome left cabinet. The Superdome cabinets contain all of the processors,
memory and core devices of the system. They will also house most (usually all) of the system's I/O
cards. Systems may include both left and right cabinet assemblies containing, a left or right
backplane respectively.
One or more HP Universal Rack cabinets. These 19-inch rack cabinets are used to hold the system
peripheral devices such as disk drives.
Optionally, one or more I/O expansion cabinets (utilizing the Universal Rack). An I/O expansion
cabinet is required when a customer requires more PCI cards than can be accommodated in their
Superdome cabinets.
Superdome cabinets are serviced from the front and rear of the cabinet only. This enables customers to
arrange the cabinets of their Superdome system in the traditional row fashion found in most computer
rooms. The width of the cabinet accommodates moving it through common doorways in the U.S. and
Europe. The intake air to the main (cell) card cage is filtered. This filter can be removed for
cleaning/replacement while the system is fully operational.
A status display is be 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.
For PA-8800 and PA-8900 processors (dual core per processor):
Superdome 32 processor cores: single cabinet (a left cabinet)
Superdome 64 processor cores: single cabinet (a left cabinet)
Superdome 128 processor cores: dual cabinet (a left cabinet and a right cabinet)
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. The base configuration
product numbers for each of the models are as follows:
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 4

Cells
CellsCells
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:
Four processor sockets that can hold PA 8600, PA 8700, PA 8800 or PA-8900 processors (only
one type is allowed per cell)
Memory (up to 16-GB RAM with 512-MB DIMMs, 32-GB RAM with 1-GB DIMMs and 64-GB
with 2-GB DIMMs.
NOTE:
NOTE:NOTE:
NOTE: Only 1 GB and 2 GB DIMMs are supported with Superdome PA 8800 and PA 8900).
One cell controller (CC)
Power converters
Data buses
Optional link to I/O card cage
Please note the following:
PA-8600 and PA-8700 processors can be mixed within a Superdome system, but must reside on
different cells and in different partitions (nPars). PA-8800 and PA-8900 processors cannot be
mixed within a Superdome system with PA-8600 or PA-8700 processors.
A Superdome PA-8800 and PA-8900 system can support up to 1 TB of memory with 2 GB
DIMMs. However, due to the limitation of HP-UX 11i, the maximum amount of memory supported
in a partition is 512 GB.
For PA-8600 and PA-8700 processors: The minimum configuration includes one active processor
and 2 GB memory per cell board. The maximum configuration includes four active processor and
16 GB memory per cell board. Each cell board ships with four PA-8600 or PA-8700 processors.
However, based on the number of active processors ordered, from one through four processors
are activated prior to shipment.
For PA-8800 and PA-8900 processors: The minimum configuration includes one active processor
and 2 GB of memory per cell board. The maximum configuration includes eight active processors
and 64 GB of memory per cell board using 2 GB DIMMs. The minimum number of active
processors on each cell board is one. Additional processors on the cell board can be activated
individually (not in pairs).
512 MB, 1 GB and 2 GB DIMMs can be mixed on a cell board in Superdome PA 8800 and PA
8900 systems only.
Crossbar Backplane
Crossbar BackplaneCrossbar Backplane
Crossbar Backplane 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 resulting in a Superdome PA-8600 or Superdome PA-8700 32 processor or Superdome PA-8800
or PA-8900 64 processor system. A backplane supporting four cells would result in a Superdome PA
8600 or Superdome PA-8700 16 processor and a Superdome PA-8800 or PA-8900 32 processor
system. Two backplanes can be linked together with flex cables to produce a cabinet that can support up
to 16 cells resulting in a Superdome PA-8600 or Superdome PA-8700 64 processor core or Superdome
PA-8800 or PA-8900 128 processor core system.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 5

I/O Subsystem
I/O SubsystemI/O Subsystem
I/O Subsystem Each I/O chassis provides twelve I/O slots. Superdome PA-8600 and Superdome PA-8700 support I/O
chassis with 12 PCI 66 capable slots, eight supported via single (1x) ropes (266 MB/s peak) and four
supported via dual (2x) ropes (533 MB/s peak). Superdome PA-8800 and PA-8900 supports I/O
chassis with 12 PCI-X 133 capable slots, eight supported via single enhanced (2x) ropes (533 MB/s
peak) and four supported via dual enhanced (4x) ropes (1066 MB/s peak).
Each Superdome cabinet supports a maximum of four internal I/O chassis. The optional I/O expansion
cabinet can support three I/O chassis enclosures (ICE), each of which supports two I/O chassis for a
maximum of six I/O chassis per I/O expansion cabinet.
Each Each cell board connects to at most one I/O chassis, and therefore the number of I/O chassis
supported is dependent on the number of cells present in the system. A Superdome system can have
more cells than I/O chassis. For instance, an 8 cell Superdome can have one to eight I/O chassis. Each
partition must have at least one I/O chassis with the number of I/O chassis not exceeding the number of
cells.
A 4-cell Superdome supports four I/O chassis for a maximum of 48 PCI slots.
An 8-cell Superdome supports eight I/O chassis for a maximum of 96 PCI slots. Since a single
Superdome cabinet only supports four I/O chassis, an I/O expansion cabinet and two I/O chassis
enclosures are required to support all eight I/O chassis.
A 16-cell Superdome supports 16 I/O chassis for a maximum of 192 PCI slots. Since two Superdome
cabinets (left and right) only support eight I/O chassis, two I/O expansion cabinets and four I/O chassis
enclosures are required to support all 16 I/O chassis. The four I/O chassis enclosures are spread across
the two I/O expansion cabinets, either three ICE in one I/O expansion cabinet and one ICE in the other
or two ICE in each.
Core I/O
Core I/OCore I/O
Core I/O Superdome's core I/O 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. 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 form factor but will add a second card cage
connection to the I/O backplane for additional non-PCI signals (USB and utilities). This secondary
connector will not impede the ability to support standard PCI cards in the core slot when a core I/O card
is not installed.
Newer sx2000 based systems (which support only the PA-8900) do not require and do not support the
traditional core I/O card. These systems do require LAN connectivity at a minimum to support system
boot. Other I/O cards can be added to this basic functionality.
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 an I/O
chassis cannot be configured in the system unless attached to a cell.
The core I/O card's primary functions are:
Partitions (console support) including USB and RS-232 connections
10/100Base-T LAN (general purpose)
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 add in cards.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 6

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:
Product/Option Number
Product/Option NumberProduct/Option Number
Product/Option Number Description
DescriptionDescription
Description
A7108A RJ-45 Loopback Connector
0D1 Factory integration RJ-45 Loopback Connector
I/O Expansion Cabinet
I/O Expansion CabinetI/O Expansion Cabinet
I/O Expansion Cabinet The I/O expansion functionality is physically partitioned into four rack mounted chassis-the 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 I/O
chassis.
Factory Integration
Factory IntegrationFactory Integration
Factory Integration When an I/O Expansion cabinet is ordered as an upgrade to a Superdome system, it includes the factory
testing and integration of any components that are ordered at the same time as the cabinet. This
includes any I/O Chassis, PCI or PCI-X cards and peripherals. If it is ordered as an upgrade but not at
the time of the Superdome system, additional installation assistance may be required and can be
ordered as field installation products.
Field Racking
Field RackingField Racking
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 the 10K G2 Universal 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 the 10K G2 Universal Rack and all expansion components
mount in the rack. Each component is designed to install independently in the rack. The 10K G2
Universal Rack has 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 10K G2 Universal Rack perforated rear
door.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 7

I/O Chassis Enclosure
I/O Chassis EnclosureI/O Chassis Enclosure
I/O Chassis Enclosure
(ICE)
(ICE)(ICE)
(ICE)
The I/O chassis enclosure (ICE) provides expanded I/O capability for Superdome. Each ICE supports up
to 24 I/O slots by using two 12 slot Superdome I/O chassis. The I/O chassis installation in the ICE puts
the I/O 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 a 10K G2 Universal Rack and consumes 9U of vertical rack
space.
To provide online addition/replacement/deletion access to I/O 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
Cabinet Height andCabinet Height and
Cabinet Height and
Configuration Limitations
Configuration LimitationsConfiguration Limitations
Configuration Limitations
Although the individual I/O expansion cabinet components are designed for installation in any Rack
System E cabinet, rack size limitations have been agreed upon. IOX Cabinets will ship in either the 1.6-
meter (33U) or 1.96-meter (41U) cabinet. 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://HP.com/go/rackandpower for more information.
Peripheral Support
Peripheral SupportPeripheral Support
Peripheral Support All peripherals qualified for use with Superdome and/or for use in a Rack System E 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
Server SupportServer Support
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 cabinet.
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
Standalone I/OStandalone I/O
Standalone I/O
Expansion Cabinet
Expansion CabinetExpansion Cabinet
Expansion Cabinet
If an I/O expansion cabinet is ordered alone, its field installation can be ordered via option 750 in the
ordering guide (option 950 for Superdome Advanced Architect Program Channel partners).
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 8

DVD Solution
DVD SolutionDVD Solution
DVD Solution The DVD solution for Superdome requires the following components per partition. External racks
AF004A or AF014A must also be ordered with the DVD solution.
NOTE:
NOTE:NOTE:
NOTE: One DVD and one DAT is required per nPartition.
Superdome DVD Solutions
Superdome DVD SolutionsSuperdome DVD Solutions
Superdome DVD Solutions
Description
DescriptionDescription
Description Part Number
Part NumberPart Number
Part Number Option Number
Option NumberOption Number
Option Number
PCI Ultra160 SCSI Adapter or PCI Dual Channel Ultra160 SCSI
Adapter
A6828A or
A6829A
0D1
Surestore Tape Array 5300 C7508AZ
HP DVD+RW Array Module (one per partition)
NOTE:
NOTE:NOTE:
NOTE: HP DVD-ROM Array Module for the TA5300 (C7499B) is
replaced by HP DVD+RW Array Module (Q1592A) to give
customers read capabilities for loading software from CD or DVD,
DVD write capabilities for small amount of data (up to 4 GB) and
offline hot-swap capabilities.
Q1592A 0D1
HP DAT 40m Array Module C7497A 0D1
HP DAT 72 Array Module (carbon) Q1524B
DDS-4/DAT40 (one per partition) C7497B 0D1
PCI LVD/SE SCSI card
PCI LVD/SE SCSI cardPCI LVD/SE SCSI card
PCI LVD/SE SCSI card
NOTE:
NOTE:NOTE:
NOTE: A5149A supports the MSA30 SB/DB as a boot device on
Superdome running HP-UX 11i.
NOTE:
NOTE:NOTE:
NOTE: MSA 30 is End of Life and may not be available.
A5149A 0D1
Jumper SCSI Cable for DDS-4 (optional)
1
C2978B 0D1
SCSI Cable 10m VHD/HDTS68 LVD/SE ILT M/M C7556A
SCSI cable 5 meter C7520A 0D1
SCSI Terminator C2364A 0D1
1
0.5-meter HD-HDTS68 is required if DDS-4 is used.
If using DAT72, it is recommended to use an A6829A dual port SCSI with daisy chaining to connect the
DVD and the DAT72 leaving the second port available to connect a SCSI data storage device.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 9

Partitions
PartitionsPartitions
Partitions Hardware Partitions
Hardware PartitionsHardware Partitions
Hardware Partitions
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. nPars are logically isolated from each other such that transactions in one nPar are not visible
to other nPars 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. On HP Integrity Superdome systems, nPars may be executing
different operating systems altogether (HP-UX, Windows Server 2003 or Linux). Please refer to the HP
Integrity Superdome section for details on these operating systems.
Each nPar has its own independent processors, memory and I/O resources consisting of the resources of
the cells that make up the nPar. Resources may be removed from one nPar and added to another
without having to physically manipulate the hardware just by using commands that are part of the System
Management interface.
Superdome HP-UX 11i supports static nPars. Static nPars imply that any nPar configuration change
requires a reboot of that nPar. In a future HP-UX release, dynamic nPars will be supported. Dynamic
nPars imply that the nPar configuration changes do not require a reboot of that 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.
NOTE:
NOTE:NOTE:
NOTE: It is possible for PA-8800 and PA-8900 nPars to co exist with Itanium 2 1.6 GHz nPars in the
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
in the field onlyin the field only
in the field only . Factory
orders for mixed Itanium and PA RISC nPars are not allowed.
Virtual Partitions
Virtual PartitionsVirtual Partitions
Virtual Partitions
A virtual partition (vPar) provides the capability of dividing a system into different HP UX operating system
images.
VPars is available on HP-UX 11i and therefore can run on Superdome PA 8600/PA 8700 servers. vPars
on Superdome PA-8800 and PA-8900 is also supported.
Mixing of PA-RISC and
Mixing of PA-RISC andMixing of PA-RISC and
Mixing of PA-RISC and
Itanium Cells in
Itanium Cells inItanium Cells in
Itanium Cells in
Superdome
SuperdomeSuperdome
Superdome
1)
1)1)
1) Which processors can be mixed in a Superdome?
Which processors can be mixed in a Superdome?Which processors can be mixed in a Superdome?
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 or sx1000 chipset or sx2000) 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 and sx2000 chipsets, processors of like architectures (PA RISC and Itanium architectures)
that are supported by the specific 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. As
an example, 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.
The table below highlights which processors can co-exist on a Superdome in separate hard partitions.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 10

PA-
PA-PA-
PA-
8600
86008600
8600
PA-
PA-PA-
PA-
8700
87008700
8700
PA-
PA-PA-
PA-
8700
87008700
8700
+
++
+
PA-
PA-PA-
PA-
8800
88008800
8800
PA-
PA-PA-
PA-
8900
89008900
8900
Itanium
ItaniumItanium
Itanium
2 6M
2 6M2 6M
2 6M
Itanium
ItaniumItanium
Itanium
2 9M
2 9M2 9M
2 9M
mx2
mx2mx2
mx2
dual-
dual-dual-
dual-
core
corecore
core
processor
processorprocessor
processor
module
modulemodule
module
Montecito
MontecitoMontecito
Montecito Montvale
MontvaleMontvale
Montvale
PA-8600
PA-8600PA-8600
PA-8600 NA Yes Yes No No No No No No No
PA-8700
PA-8700PA-8700
PA-8700 Yes NA Yes No No No No No No No
PA-8700
PA-8700PA-8700
PA-8700
+
++
+
Yes Yes NA No No No No No No No
PA-8800
PA-8800PA-8800
PA-8800 No No No NA Yes No Yes No No No
PA-8900
PA-8900PA-8900
PA-8900 No No No Yes NA No Yes No Yes* Yes*
Itanium 2
Itanium 2Itanium 2
Itanium 2
6M
6M6M
6M
No No No No No NA Yes Yes No No
Itanium 2
Itanium 2Itanium 2
Itanium 2
9M
9M9M
9M
No No No Yes Yes Yes NA Yes No No
mx2 dual-
mx2 dual-mx2 dual-
mx2 dual-
core
corecore
core
processor
processorprocessor
processor
module
modulemodule
module
No No No No No Yes Yes NA No No
Montecito
MontecitoMontecito
Montecito * No No No No Yes No No No NA Yes
Montvale
MontvaleMontvale
Montvale * No No No No Yes No No No Yes NA
*Requires the sx2000 chipset
2)
2)2)
2) In order to run an Itanium-based partition in an HP 9000 server, what changes are required?
In order to run an Itanium-based partition in an HP 9000 server, what changes are required?In order to run an Itanium-based partition in an HP 9000 server, what changes are required?
In order to run an Itanium-based partition in an HP 9000 server, what changes are required?
In order to add a new partition with Itanium 2 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 2-based cell (s)
Step #3: Plug in cell boards for Itanium 2-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 2-based partition
Upgrading a PA-RISC partition to support Itanium 2 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 2 processor (protects investment in
current memory)
Step #4: Plug in cell boards for Itanium 2-based cell boards
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 11

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 2-based partition
The in-box addition of Itanium 2 processors can be done with no additional hardware, no new chassis
and no change to backplane.
3) When will mixing of PA-RISC and Itanium 2 processors be available?
3) When will mixing of PA-RISC and Itanium 2 processors be available?3) When will mixing of PA-RISC and Itanium 2 processors be available?
3) When will mixing of PA-RISC and Itanium 2 processors be available?
Support for mixing PA RISC and Itanium 2 processors within systems based on the sx1000 and/or sx2000
chipsets (in separate hard partitions) is available now
4) Is mixing of PA-RISC and Itanium processors factory configurable?
4) Is mixing of PA-RISC and Itanium processors factory configurable?4) Is mixing of PA-RISC and Itanium processors factory configurable?
4) Is mixing of PA-RISC and Itanium processors factory configurable?
NO. The way to do this is to enable PA RISC systems that shipped from the factory to add 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.
The current policy is not
notnot
not to allow PA RISC or Intel Itanium based partitions to be added to systems in the
factory. However, depending on the geographic region, shipment of Superdome systems with a mix of PA
RISC and Intel Itanium based partitions may be possible.
5)
5)5)
5) How long does it take to add an Itanium-based partition in an HP 9000 customers?
How long does it take to add an Itanium-based partition in an HP 9000 customers?How long does it take to add an Itanium-based partition in an HP 9000 customers?
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 architecture.
The process is currently being tested by R&D. This document will be updated as we learn more through
testing.
6)
6)6)
6) Will mixing impact the overall performance of a Superdome
Will mixing impact the overall performance of a SuperdomeWill mixing impact the overall performance of a Superdome
Will mixing impact the overall performance of a Superdome (i.e. would an Itanium-based partition
have the same performance in a mixed Superdome as in a Superdome only populated with Itanium 2
processors)?
No. For example, suppose you have a hard partition with 16 Intel Itanium 2 9M processors. This partition
would have the same performance in a system with a mix of PA-RISC and Itanium 2-based hard partitions
as a server where all of the other partitions are Itanium 2-based. This is assuming that besides the type of
processors, all of the other configuration options are the same (memory, cell board locations, number of
partitions, etc).
7) Can I add PA-RISC processors to an Itanium-based Integrity Superdome?
7) Can I add PA-RISC processors to an Itanium-based Integrity Superdome?7) Can I add PA-RISC processors to an Itanium-based Integrity Superdome?
7) Can I add PA-RISC processors to an Itanium-based Integrity Superdome?
Yes. 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 serves as a safety net/insurance policy. If the customer determines after
the fact that a specific application is not ready for the Itanium technology, they can simply add a PA-RISC
hard partition to that Integrity Superdome and continue the execution of the application while it is
certified.
8) Why can't PA-8700+ processors be mixed with Itanium 2 9M processors?
8) Why can't PA-8700+ processors be mixed with Itanium 2 9M processors?8) Why can't PA-8700+ processors be mixed with Itanium 2 9M processors?
8) Why can't PA-8700+ processors be mixed with Itanium 2 9M processors?
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 12

For years, HP has had a high level of investment protection with the HP 9000 Superdome. Customers
have been provided with the maximum investment protection level by keeping their investment in PA8600
and PA8700 processors while adding the higher speed PA8700+. In addition, each processor type runs
at its rated speed so there is no downgrading of the higher speed processors (some competitors are
erroneously saying Superdome has to downgrade the higher speed processors). For example, the PA8700
runs at a full 750 MHz while the PA8600 runs at 550 MHz-there is no forcing of the PA8700 down to
550 MHz just to obtain compatibility. This is possible because the processor speeds are independent from
the bus speeds.
The Intel Itanium processor family is an advanced architecture featuring exceptional floating point and
SSL performance. The Itanium 2 processors have the processing power that is consistent with a
Superdome class high-end server. In addition, the Itanium processor accesses cache memory using a
data block that is greater than twice the size of the PA8600, PA8700, and PA8700+. Thus, the Itanium
processor family and subsequent PA-8800 and PA-8900 processors require a different chipset than the
PA8600, PA8700, or PA8700+ processors. One of the key restrictions in mixing processors is that all cell
boards in a given Superdome must have the same chipset. The PA-8700+ is supported by a legacy
chipset that only supported PA-RISC processors. As a result, the PA-8700+ can only be mixed with PA-
8700 and PA-8600 processors. In order to support Itanium 2 9M processors in their current HP 9000
Superdome, the customer would be required first to upgrade all of their PA-8700+ processors to PA-
8800 or PA-8900 processors utilizing the sx1000 chipset. Once this is complete, the customer would
then have the option of adding the Itanium 2 9M processor in a separate partition because it is also
supported by the sx1000 chipset.
9) Why aren't Itanium 6M processors and mx2 dual core processor modules supported?
9) Why aren't Itanium 6M processors and mx2 dual core processor modules supported?9) Why aren't Itanium 6M processors and mx2 dual core processor modules supported?
9) Why aren't Itanium 6M processors and mx2 dual core processor modules supported?
The original plan was to enable PA RISC systems that shipped from the factory to add Itanium based
partitions later on. The plan was not to allow PA RISC based partitions to be added to systems that
shipped from the factory as Itanium based servers with Itanium 6M processors and/or mx2 dual core
processor modules. This is the only case where we encounter a problem with no support for Itanium 6M
processors and mx2 dual core processor modules. If a customer has already made the decision to go
with Integrity Superdomes, it is very unlikely that they will take a back step to PA RISC based partitions.
Conversely, if a customer wants to upgrade a PA RISC based partition to be Itanium based, they are
much more likely to use the Itanium 9M processor than the Itanium 6M processors or mx2 dual core
processor modules because of the added performance and larger cache sizes.
Finally, this feature requires a significant amount of resources to test the different type of configurations
supported in a Superdome. In order to provide this functionality in a timely basis to customers, we had to
narrow the scope. Thus, the decision was made to not support Itanium 2 6M processors and mx2 dual
core processors in a mixed processor type of system.
If a customer with Itanium 6M processors or mx2 dual core processor modules wants to add PA RISC
modules, they would need to first upgrade the partitions with Itanium 6M processors or mx2 dual core
processor modules to Itanium 9M processors and then they could add a PA RISC based partition to the
Superdome.
10) Which versions of the HP-UX 11i operating system will be supported?
10) Which versions of the HP-UX 11i operating system will be supported?10) Which versions of the HP-UX 11i operating system will be supported?
10) Which versions of the HP-UX 11i operating system will be supported?
Currently HP supports HP UX 11.11 (HP UX 11i v1) for the PA RISC architecture as well as 11.23 (HP UX
11i v2) for Itanium processors and PA RISC processors in a mixed environment. Based on HP's testing,
using HP UX 11.11 (HP UX 11i v1) in a mixed configuration requires a PA RISC Firmware update.
11) Does a customer have to power down when they add an Itanium-based partition to a PA-RISC-
11) Does a customer have to power down when they add an Itanium-based partition to a PA-RISC-11) Does a customer have to power down when they add an Itanium-based partition to a PA-RISC-
11) Does a customer have to power down when they add an Itanium-based partition to a PA-RISC-
based Superdome?
based Superdome?based Superdome?
based Superdome?
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 13

It depends. If the existing PA-RISC based partitions are running HP-UX 11i v2 and PDC 22.1 (released in
December 2004) then an Itanium-based partition may be added while the PA-RISC partitions are active.
If the customer is running WLM it must be patched for proper operation in a mixed environment. We are
currently checking with the WLM team to see what impact this would have on the PA-RISC partitions.
HP's shipping firmware for PA RISC processors does not fully support mixing if the PA RISC partitions are
running HP UX 11i v1. In this case, downtime for all PA RISC based partitions would be required to
update to the new PDC. The partitions could all be updated independently if desired. The above
comment regarding WLM also applies.
12) What are the minimum firmware requirements for mixing various operating environments?
12) What are the minimum firmware requirements for mixing various operating environments?12) What are the minimum firmware requirements for mixing various operating environments?
12) What are the minimum firmware requirements for mixing various operating environments?
The matrix below describes the minimum firmware requirements:
Mixing Mad9M with PA-
Mixing Mad9M with PA-Mixing Mad9M with PA-
Mixing Mad9M with PA-
8800/PA-8900
8800/PA-89008800/PA-8900
8800/PA-8900
11i v2 HWE0409
11i v2 HWE040911i v2 HWE0409
11i v2 HWE0409
11i v2 HWE0505
11i v2 HWE050511i v2 HWE0505
11i v2 HWE0505 (no vPars)
Windows Server 2003
Windows Server 2003Windows Server 2003
Windows Server 2003
Linux
LinuxLinux
Linux
11i v2 HWE0505
11i v2 HWE050511i v2 HWE0505
11i v2 HWE0505 (vPars)
11i v1
11i v111i v1
11i v1 PDC 22.3
IPF 2.54
MFW 15.14
PDC 22.3
IPF 3.x
MFW 15.20
11i v2
11i v211i v2
11i v2 PDC 22.1
IPF 2.50
MFW 15.14
PDC 22.1
IPF 3.x
MFW 15.20
Mixing Scenarios:
Mixing Scenarios:Mixing Scenarios:
Mixing Scenarios:
operating systems,
operating systems,operating systems,
operating systems,
firmware and
firmware andfirmware and
firmware and
management tools
management toolsmanagement tools
management tools
The following table summarizes the various operating environments supported on the PA-8800, PA-8900
and Intel Itanium 2 1.6 GHz processors:
Processor
ProcessorProcessor
Processor Operating System
Operating SystemOperating System
Operating System
PA-8800 HP-UX 11.i v1 HWE 0312 (with patches)
HP-UX 11.i v1 HWE 0406
HP-UX 11.i v1 HWE 0412
HP-UX 11.i v2 HWE 0409
HP-UX 11.i v2 HWE 0505
PA-8900 HP-UX 11.i v1 HWE 0412
HP-UX 11.i v2 HWE 0409
HP-UX 11.i v2 HWE 0505
Itanium 2 1.6 GHz HP-UX 11.i v2 HWE 0409
HP-UX 11.i v2 HWE 0505
Linux RHEL3 U3 (and higher)
Linux SLES 9 (and higher)
Windows 2003 Server, Smart Setup 3.1 (and higher)
The following table lists the minimum firmware requirements for mixing:
Processor
ProcessorProcessor
Processor Supported
SupportedSupported
Supported Not Supported
Not SupportedNot Supported
Not Supported
PA-8800 PDC 22.1 (SMS rel_5.0) or above PDC 20.8, 21.2
PA-8900 PDC 22.1 (SMS rel_5.0) or above n/a
Itanium 2 1.6 GHz A1 IPF 2.50 (SMS rel_5.0) or above n/a
Itanium 2 1.6 GHz A2 IPF 2.52 (SMS rel_5.1) or above n/a
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 14

NOTE:
NOTE:NOTE:
NOTE: PDC 20.8 and PDC 21.2 do not contain the required enhancements for mixing. Customers who
are running on either of these PDC versions will be required to upgrade to PDC 22.1 to enable mixing.
PDC 22.1 also happens the minimum firmware required to support PA-8900.
Any of the above operating environments may be used on a mixed Superdome. In the process of testing
all of the above combinations some issues and restrictions were discovered with WLM, gWLM and the
GUI version of partition manager on HP-UX 11i v1. Firmware, operating system or application updates
can resolve these issues. However, such updates may not always be possible or practical.
The following mixing scenarios serve to illustrate the issues that were found during testing and possible
ways to work around or resolve them. For simplicity, the first three scenarios assume that all the PA
partitions in the Superdome are running the same version of HP-UX. The fourth scenario explains the
more general case where the PA partitions are running different versions of HP-UX.
Scenario 1:
Scenario 1:Scenario 1:
Scenario 1: PA-8800 Partitions running HP-UX 11i v1 HWE 0312 or 0406 mixed with Itanium 2 1.6
PA-8800 Partitions running HP-UX 11i v1 HWE 0312 or 0406 mixed with Itanium 2 1.6PA-8800 Partitions running HP-UX 11i v1 HWE 0312 or 0406 mixed with Itanium 2 1.6
PA-8800 Partitions running HP-UX 11i v1 HWE 0312 or 0406 mixed with Itanium 2 1.6
GHz
GHzGHz
GHz
Known issue with the GUI version of
Known issue with the GUI version ofKnown issue with the GUI version of
Known issue with the GUI version of Parmgr
ParmgrParmgr
Parmgr :
Both of these HWEs shipped with Parmgr V1. This version of Parmgr and the stack that sits under it are
not capable of managing Integrity partitions. Parmgr generates error messages when trying to access the
Integrity cells and display information about them.
Alternatives to running
Alternatives to runningAlternatives to running
Alternatives to running Parmgr
ParmgrParmgr
Parmgr GUI on the PA partitions
GUI on the PA partitionsGUI on the PA partitions
GUI on the PA partitions :
Integrity partitions (and PA partitions) may be managed from the SMS
Integrity partitions (and PA partitions) may be managed by parcmds from any partition
Integrity partitions (and PA partitions) may be managed by the GUI version of Parmgr on any
Integrity partition
The minimum firmware listed in the table above is sufficient for running this configuration.
Possible Upgrades:
Possible Upgrades:Possible Upgrades:
Possible Upgrades:
If it is important to be able to use the parmgr GUI on the PA HP UX 11i v1 you can upgrade HP UX to
HWE 0412 and follow the process in Scenario 2. If a customer upgrades to any 11i v1 HWE beyond
HWE 0412 (HWE 0509 and later) then the proper nPar provider is already included in the HWE and the
firmware upgrades in Scenario 2 are sufficient to get full functionality.
Scenario 2:
Scenario 2:Scenario 2:
Scenario 2: PA 8800 partitions or PA 8900 partitions running 11i v1 HWE 0412 mixed with Itanium
PA 8800 partitions or PA 8900 partitions running 11i v1 HWE 0412 mixed with ItaniumPA 8800 partitions or PA 8900 partitions running 11i v1 HWE 0412 mixed with Itanium
PA 8800 partitions or PA 8900 partitions running 11i v1 HWE 0412 mixed with Itanium
1.6 GHz
1.6 GHz1.6 GHz
1.6 GHz
Known issue with the GUI version of
Known issue with the GUI version ofKnown issue with the GUI version of
Known issue with the GUI version of Parmgr
ParmgrParmgr
Parmgr :
HP-UX 11i v1 HWE 0412 introduced Parmgr V2. This version of Parmgr will exhibit the same issues as
Scenario 1 with the minimum required firmware from the table. However, upgrades to firmware and the
nPar provider will make this version of Parmgr fully functional and capable of managing Integrity
partitions. See the upgrade section below for details.
Alternatives to running Parmgr GUI on the PA partitions:
These are essentially the same as Scenario 1.
Integrity partitions (and PA partitions) may be managed from the SMS
Integrity partitions (and PA partitions) may be managed by parcmds from any partition
Integrity partitions (and PA partitions) may be managed by the GUI version of Parmgr on any
Integrity partition
The minimum firmware listed in the table above is sufficient for running this configuration.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 15

Possible upgrades:
Possible upgrades:Possible upgrades:
Possible upgrades:
If it is important to be able to use the parmgr GUI on the PA partitions to manage the Integrity partitions
the following updates must be made to the system:
PDC must be at revision 22.3 or higher in the 11.i v1 partition. This version of PDC contains a single fix
on top of PDC 22.1 that compensates for the byte reversal in the cell info structure between PA and
Integrity (this is due to the different "endianness" of the processors). PDC 22.3 will be released as part of
SMS rel_6.0 in September 2005.
Integrity firmware must be upgraded to the version that supports vPars. This version of Integrity firmware
contains a fix that populates I/O slot information in cell info structures used by the PA partition
management stack. Currently shipping Integrity firmware does not populate this information and causes
the PA management stack to report errors for Integrity cells. This version of Integrity firmware will be
released as part of SMS rel_6.0 in September 2005.
The nPartition provider ("nPar" bundle) must be updated to version B.11.11.01.04 or above. This version
will first be released on HP UX 11.i v1 HWE 0509. The version of nPar provider that shipped with HWE
0412 did not properly handle the single core Madison 9M processors.
Scenario 3:
Scenario 3:Scenario 3:
Scenario 3: PA-8800 partition or PA-8900 partition running 11.i v2 (HWE 0409 or 0505) mixed with
PA-8800 partition or PA-8900 partition running 11.i v2 (HWE 0409 or 0505) mixed withPA-8800 partition or PA-8900 partition running 11.i v2 (HWE 0409 or 0505) mixed with
PA-8800 partition or PA-8900 partition running 11.i v2 (HWE 0409 or 0505) mixed with
Itanium 1.6 GHz
Itanium 1.6 GHzItanium 1.6 GHz
Itanium 1.6 GHz
This is the simplest scenario. The minimum firmware listed in the table is sufficient and all the partition
management tools just work. The PA partition can manage other PA partitions and the Integrity partition
and vice versa. Enjoy.
Scenario 4:
Scenario 4:Scenario 4:
Scenario 4: PA-8800 or PA-8900 partitions running a mixture of the above scenarios mixed with
PA-8800 or PA-8900 partitions running a mixture of the above scenarios mixed withPA-8800 or PA-8900 partitions running a mixture of the above scenarios mixed with
PA-8800 or PA-8900 partitions running a mixture of the above scenarios mixed with
Itanium 1.6 GHz
Itanium 1.6 GHzItanium 1.6 GHz
Itanium 1.6 GHz
The previous scenarios apply to the individual partition pairs. For instance, say you have a Superdome
with a PA8800 11.i v1 HWE0406 partition, a PA8900 11.i v1 HWE0412 partition a PA8800 11.i v2
partition and an Integrity partition. As described in Scenario 1 the PA8800 11.i v1 HWE0406 partition
will not be able to recognize the Integrity cells. Manage the Integrity partition from the SMS, the PA8800
11.i v2 partition or using parcmds. As described in Scenario 2, the PA8900 11.i v1 HWE0412 partition
cannot manage the Integrity partition with out the firmware and nPar provider upgrades outlined above.
Use the SMS, the PA 11.i v2 partition or parcmds to manage the Integrity partition.
Workload Manager
Workload ManagerWorkload Manager
Workload Manager (WLM)
WLM currently uses the UNIX command " uname -i " to ensure that all the partitions it is managing are on
the same Superdome. WLM verifies that all the managed partitions " uname -i " values match. It turns out
the Integrity partitions and PA partitions on the same Superdome do not return the same value for " uname
-i ". This prevents WLM from properly managing all the partitions on a single Superdome in a mixed
environment with iCAP. The WLM team has provided patches WLM A.03.00 for both 11.i v1
(PHSS_33499 s700_800 11.11 WLM A.03.00 Cumulative Patch) and 11.i v2 (PHSS_33477 s700_800
11.23 WLM A.03.00 Cumulative Patch) to resolve this issue. Customers who wish to use WLM in a mixed
environment with iCAP will need to install/upgrade to version A.03.00 and install the appropriate patch.
Customers who are using either WLM A.02.x or A.03.x in a non iCAP environment can use their current
version of WLM with no upgrade/patch. Future versions of WLM (A.03.00.01 and later) will not require a
patch.
Global Workload Manager
Global Workload ManagerGlobal Workload Manager
Global Workload Manager (gWLM)
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 16

gWLM 1.1.1 was first released with HP UX 11.i v2 HWE0505. It has the same issue with "uname -i" as
WLM. This only affects gWLM iCAP SRDs. VPAR, PSET and FSS SRDs work correctly in mixed
environments. The gWLM team plans to remedy this issue in the first maintenance release of gWLM.
Contact [email protected] for a workaround if you have a gWLM 1.1.1 customer who needs to
deploy an iCAP SRD on a mixed complex before the first maintenance release is available.
High Availability
High AvailabilityHigh Availability
High Availability NOTE:
NOTE:NOTE:
NOTE: Online addition/replacement for cell boards is not currently supported and will be available in a
future HP UX release. Online addition/replacement of individual processors and memory DIMMs will
never be supported.)
Superdome high availability offering is as follows:
Processor:
Processor:Processor:
Processor: The features below nearly eliminate the down time associated with processor cache
errors (which are the majority of processor errors).
Dynamic processor resilience w/ Instant Capacity enhancement.
Processor cache ECC protection and automatic de allocation
Processor bus parity protection
Redundant DC conversion
Memory
MemoryMemory
Memory : The memory subsystem design is such that a single SDRAM chip does not contribute
more than 1 bit to each ECC word. Therefore, the only way to get a multiple-bit memory error
from SDRAMs is if more than one SDRAM failed at the same time (rare event). The system is also
resilient to any cosmic ray or alpha particle strike because these failure modes can only affect
multiple bits in a single SDRAM. If a location in memory is "bad", the physical page is de-allocated
dynamically and is replaced with a new page without any OS or application interruption. In
addition, a combination of hardware and software scrubbing is used for memory. The software
scrubber reads/writes all memory locations periodically. However, it does not have access to
"locked-down" pages. Therefore, a hardware memory scrubber is provided for full coverage.
Finally data is protected by providing address/control parity protection.
Memory DRAM fault tolerance (i.e., recovery of a single SDRAM failure)
DIMM address/control parity protection
Dynamic memory resilience (i.e., page de-allocation of bad memory pages during
operation)
Hardware and software memory scrubbing
Redundant DC conversion
Cell COD
I/O
I/OI/O
I/O : Partitions configured with dual path I/O can be configured to have no shared components
between them, thus preventing I/O cards from creating faults on other I/O paths. I/O cards in
hardware partitions (nPars) are fully isolated from I/O cards in other hard partitions. It is not
possible for an I/O failure to propagate across hard partitions. It is possible to dynamically repair
and add I/O cards to an existing running partition.
Full single-wire error detection and correction on I/O links
I/O cards fully isolated from each other
Hardware for the prevention of silent corruption of data going to I/O
On-line addition/replacement (OLAR) for individual I/O cards, some external peripherals,
SUB/HUB
Parity protected I/O paths
Dual path I/O
Crossbar and Cabinet Infrastructure
Crossbar and Cabinet InfrastructureCrossbar and Cabinet Infrastructure
Crossbar and Cabinet Infrastructure :
Recovery of a single crossbar wire failure
Localization of crossbar failures to the partitions using the link
Automatic de-allocation of bad crossbar link upon boot
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 17

Redundant and hotswap DC converters for the crossbar backplane
ASIC full burn-in and "high quality" production process
Full "test to failure" and accelerated life testing on all critical assemblies
Strong emphasis on quality for multiple-nPartition single points of failure (SPOFs)
System resilience to Management Processor (MP)
Isolation of nPartition failure
Protection of nPartitions against spurious interrupts or memory corruption
Hot swap redundant fans (main and I/O) and power supplies (main and backplane power
bricks)
Dual power source
Phone-Home capability
"HA Cluster-In-A-Box" Configuration
"HA Cluster-In-A-Box" Configuration"HA Cluster-In-A-Box" Configuration
"HA Cluster-In-A-Box" Configuration : The "HA Cluster-In-A-Box" allows for failover of users'
applications between hardware partitions (nPars) on a single Superdome system. All providers of
mission critical solutions agree that failover between clustered systems provides the safest
availability-no single points of failures (SPOFs) and no ability to propagate failures between
systems. However, HP supports the configuration of HA cluster software in a single system to allow
the highest possible availability for those users that need the benefits of a non-clustered solution,
such as scalability and manageability. Superdome with this configuration will provide the greatest
single system availability configurable. Since no single-system solution in the industry provides
protection against a SPOF, users that still need this kind of safety and HP's highest availability
should use HA cluster software in a multiple system HA configuration. Multiple Serviceguard or
Serviceguard Extension for RAC clusters can be configured within a single Superdome system (i.e.,
two 4-node clusters configured within a 32-processor Superdome system).
Multi-system High
Multi-system HighMulti-system High
Multi-system High
Availability
AvailabilityAvailability
Availability
Any Superdome partition with PA-RISC processors that is protected by Serviceguard or Serviceguard
Extension for RAC can be configured in a cluster with:
Another Superdome with PA-RISC processors
One or more standalone non Superdome systems with PA-RISC processors
Another partition within the same single cabinet Superdome (refer to "HA Cluster-in-a-Box" above
for specific requirements)
Separate partitions within the same Superdome system can be configured as part of different
Serviceguard clusters.
Please note that when you add nodes or initially create a cluster, all nodes must be at the same version
of the operating system and Serviceguard. This means that you may have to load an operating system
update for hardware enablement of the newer hardware, even on older systems. Please refer to the
"Compatibility and Feature Matrix" at
http://docs.hp.com/hpux/onlinedocs/4076/SG%20SGeRAC%20EMS%20Support%20Matrix_10 3
03.htm
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 18

Geographically Dispersed
Geographically DispersedGeographically Dispersed
Geographically Dispersed
Cluster Configurations
Cluster ConfigurationsCluster Configurations
Cluster Configurations
The following Geographically Dispersed Cluster solutions fully support cluster configurations using
Superdome systems. The existing configuration requirements for non-Superdome systems also apply to
configurations that include Superdome systems. An additional recommendation, when possible, is to
configure the nodes of cluster in each datacenter within multiple cabinets to allow for local failover in the
case of a single cabinet failure. Local failover is always preferred over a remote failover to the other
datacenter. The importance of this recommendation increases as the geographic distance between
datacenters increases.
Extended Campus Clusters (using Serviceguard with Mirrordisk/UX)
MetroCluster with Continuous Access XP
MetroCluster with EMC SRDF
ContinentalClusters
From an HA perspective, it is always better to have the nodes of an HA cluster spread across as many
system cabinets (Superdome and non Superdome systems) as possible. This approach maximizes
redundancy to further reduce the chance of a failure causing down time.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Configuration
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 19

Supportability and management features on HP 9000 Superdome are covered in the next section.
Service Processor (MP)
Service Processor (MP)Service Processor (MP)
Service Processor (MP) The service processor (MP) utility hardware is an independent support system for nPartition servers. It
provides a way for you to connect to a server complex and perform administration or monitoring tasks
for the server hardware and its nPartitions. The main features of the service processor include the
Command menu, nPartition consoles, console logs, chassis code viewers, and partition Virtual Front
Panels (live displays of nPartition and cell states).
Access to the MP is restricted by user accounts. Each user account is password protected and provides a
specific level of access to the Superdome complex and service processor commands. Multiple users can
independently interact with the service processor because each service processor login session is private.
Up to 16 users can simultaneously log in to the service processor through its network (customer LAN)
interface and they can independently manage nPartitions or view the server complex hardware states.
Two additional service processor login sessions can be supported by the local and remote serial ports.
These allow for serial port terminal access(through the local RS 232 port) and external modem access
(through the remote RS 232 port).
In general, the service processor (MP) on Superdome servers is similar to the service processor on other
HP servers, while providing enhanced features necessary for managing a multiple nPartition server. For
example, the service processor manages the complex profile, which defines nPartition configurations as
well as complex wide settings for the server. The service processor also controls power, reset, and TOC
capabilities, displays and records system events (chassis codes), and can display detailed information
about the various internal subsystems.
Functional capabilities:
Functional capabilities:Functional capabilities:
Functional capabilities: The primary features available through the service processor are:
The Service Processor Command Menu
The Service Processor Command MenuThe Service Processor Command Menu
The Service Processor Command Menu : provides commands for
system service, status, access configuration, and manufacturing tasks.
Partition Consoles
Partition ConsolesPartition Consoles
Partition Consoles : Each nPartition in a server complex has its own
console. Each nPartition's console provides access to Boot Console
Handler (BCH) interface and the HP-UX console for the nPartition.
Console Logs
Console LogsConsole Logs
Console Logs : Each nPartition has its own console log, which has a
history of the nPartition console's output, including boot output, BCH
activity, and any HP-UX console login activity.
Chassis Logs Viewers
Chassis Logs ViewersChassis Logs Viewers
Chassis Logs Viewers (Live and Recorded Chassis Codes): Three types
of chassis code log views are available: activity logs, error logs, and
live chassis code logs.
Virtual Front Panels:
Virtual Front Panels:Virtual Front Panels:
Virtual Front Panels: Each nPartition's Virtual Front Panel (VFP)
displays real-time status of the nPartition boot status and activity, and
details about all cells assigned to the nPartition. The VFP display
automatically updates as cell and nPartition status changes.
QuickSpecs
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
HP 9000 Superdome Servers (PA-8600, PA-8700, PA-
8800 and PA-8900)
8800 and PA-8900)8800 and PA-8900)
8800 and PA-8900)
Management Features
DA - 11721 Worldwide — Version 28 — October 23, 2009 Page 20