Advertisement
QuickSpecs
Configuration
Multi-system High
Multi-system High
Multi-system High
Multi-system High
Availability
Availability
Availability
Availability
Geographically Dispersed
Geographically Dispersed
Geographically Dispersed
Geographically Dispersed
Cluster Configurations
Cluster Configurations
Cluster Configurations
Cluster Configurations
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 HA software clusters can be configured within a single Superdome system (i.e.,
two 4-node clusters configured within a 32-socket Superdome system).
HP-UX: Serviceguard and Serviceguard Extension for RAC
Windows Server 2003: Microsoft Cluster Service (MSCS) - limited configurations supported
Red Hat Enterprise Linux AS 3 and SUSE SLES 9: Serviceguard for Linux
HP-UX 11i v2
HP-UX 11i v2
HP-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.5 GHz processors or both
Superdomes must have mx2 processor 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.
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.
DA - 11717
North America — Version 15 — January 3, 2005
HP Integrity Superdome Servers: 16-socket, 32-
HP Integrity Superdome Servers: 16-socket, 32-
HP Integrity Superdome Servers: 16-socket, 32-
HP Integrity Superdome Servers: 16-socket, 32-
socket, and 64-socket
socket, and 64-socket
socket, and 64-socket
socket, and 64-socket
Page 12
Advertisement
