HP Integrity Superdome 16-socket Скачать руководство пользователя страница 13

Страница: 13 / 55

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

Multi-system High

Multi-system High
Availability

Availability

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.

Geographically Dispersed

Geographically Dispersed
Cluster 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.

Windows Server 2003,

Windows Server 2003,
Datacenter Edition for

Datacenter Edition for

Datacenter Edition for
Itanium 2 systems

Itanium 2 systems

Microsoft Cluster Service (MSCS) comes standard with Windows Server 2003. When a customer orders
T2372A, Windows Server 2003, Datacenter 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:

QuickSpecs

HP Integrity Superdome Servers 16-socket, 32-socket,

and 64-socket

Configuration

DA - 11717 Worldwide — Version 20 — May 3, 2005

Page 13