HP 16 processor - Page 19

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 HA software
clusters can be configured within a single Superdome system (i.e., two 4-node clusters configured
within a 32-processor Superdome system).
HP-UX: Serviceguard and Serviceguard Extension for RAC
Windows Server 2003: Microsoft Cluster Service (MSCS) - limited configurations supported
RHEL 4 and SUSE SLES 9: Serviceguard for Linux
HP OpenVMS Cluster Software
Multi-system High
Multi-system HighMulti-system High
Multi-system High
Availability
AvailabilityAvailability
Availability
HP-UX 11i v2
HP-UX 11i v2HP-UX 11i v2
HP-UX 11i v2
Any Superdome partition that is protected by Serviceguard or Serviceguard Extension for RAC can be
configured in a cluster with:
Another Superdome with like processors (i.e., both Superdomes must have Itanium 2 1.6 GHz
processors or both Superdomes must have mx2 processor (sx1000 systesm only) modules in the
partitions that are to be clustered together.)
One or more standalone non Superdome systems with like processors
Another partition within the same single cabinet Superdome (refer to "HA Cluster-in-a-Box" above
for specific requirements) that has like processors
Separate partitions within the same Superdome system can be configured as part of different
Serviceguard clusters.
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 Integrity Superdome Servers 16- processor, 32-
HP Integrity Superdome Servers 16- processor, 32-HP Integrity Superdome Servers 16- processor, 32-
HP Integrity Superdome Servers 16- processor, 32-
processor, and 64- processor Systems
processor, and 64- processor Systemsprocessor, and 64- processor Systems
processor, and 64- processor Systems
Configuration
DA - 11717 Worldwide — Version 57 — October 23, 2009 Page 19