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
Windows Server 2003,
Windows Server 2003,
Windows Server 2003,
Windows Server 2003,
Datacenter
Datacenter
Datacenter
Datacenter
Edition/Enterprise Edition
Edition/Enterprise Edition
Edition/Enterprise Edition
Edition/Enterprise Edition
for Itanium 2 systems
for Itanium 2 systems
for Itanium 2 systems
for Itanium 2 systems
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.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.
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.
Microsoft Cluster Service (MSCS) comes standard with Windows Server 2003. When a customer orders
T2372A, Windows Server 2003, Datacenter Edition or T2373A Windows Server 2003, Enterprise
Edition for Itanium 2 systems, it includes Microsoft Cluster Service there is no additional SKU or charge
for this Windows Server 2003 functionality. MSCS does not come preconfigured from HP's factories,
however, so it is recommended that if your customer is interested in a MSCS configuration with Integrity
Superdome, HP Services be engaged for a statement of work to configure MSCS on Integrity Superdome
with HP storage.
HP Storage is qualified and supported with MSCS clusters. HP storage arrays tested and qualified with
MSCS clusters on Superdome are:
EVA 3000 v3.01
EVA 5000 v3.01
XP 48/512
XP 128/1024.
XP12000
MSA1000
MSA1500
In addition, the following EMC storage arrays are supported with MSCS:
DA - 11717
Worldwide — Version 35 — December 6, 2006
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 Systems
processor, and 64- processor Systems
processor, and 64- processor Systems
Page 26
Advertisement
