Filter
Top Products
8800 128 way systems). This requirement is due to a possible 50% cluster failure.
8800 128 way systems). This requirement is due to a possible 50% cluster failure.8800 128 way systems). This requirement is due to a possible 50% cluster failure.
8800 128 way systems). This requirement is due to a possible 50% cluster failure.
51
5151
51
Serviceguard only supports cluster lock up to four nodes. Thus a two cabinet configuration is
Serviceguard only supports cluster lock up to four nodes. Thus a two cabinet configuration isServiceguard only supports cluster lock up to four nodes. Thus a two cabinet configuration is
Serviceguard only supports cluster lock up to four nodes. Thus a two cabinet configuration is
limited to four nodes (i.e., two nodes in one dual cabinet Superdome/ 64-way system or
limited to four nodes (i.e., two nodes in one dual cabinet Superdome/ 64-way system orlimited to four nodes (i.e., two nodes in one dual cabinet Superdome/ 64-way system or
limited to four nodes (i.e., two nodes in one dual cabinet Superdome/ 64-way system or
Superdome/PA 8800 128-way system and two nodes in another dual cabinet Superdome/ 64-
Superdome/PA 8800 128-way system and two nodes in another dual cabinet Superdome/ 64-Superdome/PA 8800 128-way system and two nodes in another dual cabinet Superdome/ 64-
Superdome/PA 8800 128-way system and two nodes in another dual cabinet Superdome/ 64-
way system or Superdome/PA 8800 128 way system). The Quorum Service can support up to
way system or Superdome/PA 8800 128 way system). The Quorum Service can support up toway system or Superdome/PA 8800 128 way system). The Quorum Service can support up to
way system or Superdome/PA 8800 128 way system). The Quorum Service can support up to
50 clusters or 100 nodes (can be arbitrator to both HP UX and Linux clusters).
50 clusters or 100 nodes (can be arbitrator to both HP UX and Linux clusters).50 clusters or 100 nodes (can be arbitrator to both HP UX and Linux clusters).
50 clusters or 100 nodes (can be arbitrator to both HP UX and Linux clusters).
52
5252
52
Two-cabinet configurations must evenly divide nodes between the cabinets (i.e. 3 and 1 is
Two-cabinet configurations must evenly divide nodes between the cabinets (i.e. 3 and 1 isTwo-cabinet configurations must evenly divide nodes between the cabinets (i.e. 3 and 1 is
Two-cabinet configurations must evenly divide nodes between the cabinets (i.e. 3 and 1 is
not a legal 4-node configuration).
not a legal 4-node configuration).not a legal 4-node configuration).
not a legal 4-node configuration).
53
5353
53
Cluster lock must be powered independently of either cabinet.
Cluster lock must be powered independently of either cabinet.Cluster lock must be powered independently of either cabinet.
Cluster lock must be powered independently of either cabinet.
54
5454
54
Root volume mirrors must be on separate power circuits.
Root volume mirrors must be on separate power circuits.Root volume mirrors must be on separate power circuits.
Root volume mirrors must be on separate power circuits.
55
5555
55
Redundant heartbeat paths are required and can be accomplished by using either multiple
Redundant heartbeat paths are required and can be accomplished by using either multipleRedundant heartbeat paths are required and can be accomplished by using either multiple
Redundant heartbeat paths are required and can be accomplished by using either multiple
heartbeat subnets or via standby interface cards.
heartbeat subnets or via standby interface cards.heartbeat subnets or via standby interface cards.
heartbeat subnets or via standby interface cards.
56
5656
56
Redundant heartbeat paths should be configured in separate I/O chassis when possible.
Redundant heartbeat paths should be configured in separate I/O chassis when possible.Redundant heartbeat paths should be configured in separate I/O chassis when possible.
Redundant heartbeat paths should be configured in separate I/O chassis when possible.
57
5757
57
Redundant paths to storage devices used by the cluster are required and can be
Redundant paths to storage devices used by the cluster are required and can beRedundant paths to storage devices used by the cluster are required and can be
Redundant paths to storage devices used by the cluster are required and can be
accomplished using either disk mirroring or via LVM's pvlinks.
accomplished using either disk mirroring or via LVM's pvlinks.accomplished using either disk mirroring or via LVM's pvlinks.
accomplished using either disk mirroring or via LVM's pvlinks.
58
5858
58
Redundant storage device paths should be configured in separate I/O chassis when possible.
Redundant storage device paths should be configured in separate I/O chassis when possible.Redundant storage device paths should be configured in separate I/O chassis when possible.
Redundant storage device paths should be configured in separate I/O chassis when possible.
59
5959
59
Dual power connected to independent power circuits is recommended.
Dual power connected to independent power circuits is recommended.Dual power connected to independent power circuits is recommended.
Dual power connected to independent power circuits is recommended.
Heterogeneous
HeterogeneousHeterogeneous
Heterogeneous
Multi System
Multi SystemMulti System
Multi System
High Availability
High AvailabilityHigh Availability
High Availability
60
6060
60
Cluster configurations can contain a mixture of Superdome and non Superdome nodes.
Cluster configurations can contain a mixture of Superdome and non Superdome nodes.Cluster configurations can contain a mixture of Superdome and non Superdome nodes.
Cluster configurations can contain a mixture of Superdome and non Superdome nodes.
61
6161
61
Care must be taken to configure an even or greater number of nodes outside of the
Care must be taken to configure an even or greater number of nodes outside of theCare must be taken to configure an even or greater number of nodes outside of the
Care must be taken to configure an even or greater number of nodes outside of the
Superdome cabinet
Superdome cabinetSuperdome cabinet
Superdome cabinet
62
6262
62
If half the nodes of the cluster are within a Superdome cabinet, a cluster lock is required
If half the nodes of the cluster are within a Superdome cabinet, a cluster lock is requiredIf half the nodes of the cluster are within a Superdome cabinet, a cluster lock is required
If half the nodes of the cluster are within a Superdome cabinet, a cluster lock is required
(4-node maximum cluster size)
(4-node maximum cluster size)(4-node maximum cluster size)
(4-node maximum cluster size)
63
6363
63
If more than half the nodes of a cluster are outside the Superdome cabinet, no cluster lock is
If more than half the nodes of a cluster are outside the Superdome cabinet, no cluster lock isIf more than half the nodes of a cluster are outside the Superdome cabinet, no cluster lock is
If more than half the nodes of a cluster are outside the Superdome cabinet, no cluster lock is
required (16-node maximum Serviceguard cluster size).
required (16-node maximum Serviceguard cluster size).required (16-node maximum Serviceguard cluster size).
required (16-node maximum Serviceguard cluster size).
64
6464
64
Up to a 4-node cluster is supported within a single cabinet system (Superdome/ 16-way or
Up to a 4-node cluster is supported within a single cabinet system (Superdome/ 16-way orUp to a 4-node cluster is supported within a single cabinet system (Superdome/ 16-way or
Up to a 4-node cluster is supported within a single cabinet system (Superdome/ 16-way or
Superdome/PA 8800 32-way)
Superdome/PA 8800 32-way)Superdome/PA 8800 32-way)
Superdome/PA 8800 32-way)
65
6565
65
Up to an 8-node cluster is supported within a single cabinet system* (Superdome/ 32-way or
Up to an 8-node cluster is supported within a single cabinet system* (Superdome/ 32-way orUp to an 8-node cluster is supported within a single cabinet system* (Superdome/ 32-way or
Up to an 8-node cluster is supported within a single cabinet system* (Superdome/ 32-way or
Superdome/PA 8800 64-way)
Superdome/PA 8800 64-way)Superdome/PA 8800 64-way)
Superdome/PA 8800 64-way)
66
6666
66
Up to a 16-node cluster is supported within a dual cabinet system* (Superdome/ 64-way or
Up to a 16-node cluster is supported within a dual cabinet system* (Superdome/ 64-way orUp to a 16-node cluster is supported within a dual cabinet system* (Superdome/ 64-way or
Up to a 16-node cluster is supported within a dual cabinet system* (Superdome/ 64-way or
Superdome/PA 8800 128-way)
Superdome/PA 8800 128-way)Superdome/PA 8800 128-way)
Superdome/PA 8800 128-way)
67
6767
67
Cluster lock is required for 2-node configurations
Cluster lock is required for 2-node configurationsCluster lock is required for 2-node configurations
Cluster lock is required for 2-node configurations
68
6868
68
Cluster lock must be powered independently of the cabinet.
Cluster lock must be powered independently of the cabinet.Cluster lock must be powered independently of the cabinet.
Cluster lock must be powered independently of the cabinet.
69
6969
69
Root volume mirrors must be on separate power circuits.
Root volume mirrors must be on separate power circuits.Root volume mirrors must be on separate power circuits.
Root volume mirrors must be on separate power circuits.
70
7070
70
Dual power connected to independent power circuits is highly recommended.
Dual power connected to independent power circuits is highly recommended.Dual power connected to independent power circuits is highly recommended.
Dual power connected to independent power circuits is highly recommended.
* Superdome 32-way system requires an I/O expansion cabinet for greater than 4 nodes. Superdome 64-way system requires an I/O expansion cabinet for
greater than 8 nodes.
NOTE
NOTENOTE
NOTE
:
"Recommended" refers to configurations that are fully qualified and offer the best bandwidth performance.
"Supported" refers to configurations that are fully qualified, but do not necessarily offer the best performance.
Instant Capacity on
Instant Capacity onInstant Capacity on
Instant Capacity on
Demand (iCOD)
Demand (iCOD)Demand (iCOD)
Demand (iCOD)
CPU iCOD
CPU iCODCPU iCOD
CPU iCOD
Superdome servers can be populated with Itanium 2 CPUs. It is no longer necessary to pay for the additional CPUs until the
customer uses them. However with HP's iCOD the remaining 2 CPUs that would cause the cell board to become fully
populated can be installed and remain idle. The additional CPUs can be activated instantly with a simple command
providing immediate increases in processing power to accommodate application traffic demands.
In the unlikely event that a CPU fails, the HP system will replace the failed CPU on the cell board at no additional charge.
The iCOD CPU brings the system back to full performance and capacity levels, reducing downtime and ensuring no
degradation in performance.
When additional capacity is required, additional CPUs on a cell board can be brought online. The iCOD CPUs are
activated with a single command.
CPU Instant Capacity on Demand (iCOD) can be ordered pre installed on Superdome servers. All cell boards within the
QuickSpecs
HP Integrity Superdome Servers: 16-way, 32-way,
HP Integrity Superdome Servers: 16-way, 32-way,HP Integrity Superdome Servers: 16-way, 32-way,
HP Integrity Superdome Servers: 16-way, 32-way,
and 64-way
and 64-wayand 64-way
and 64-way
Configuration
DA - 11717 Worldwide — Version 1 — June 30, 2003
Page 24