Configuration Rules for a Mixed HP 9000 / Integrity Serviceguard Cluster, March 2007
Table Of Contents
- Executive summary
- Version history
- Introduction
- Architectural rules and typical configurations
- Specific ISV information
- HP Superdome Hybrid Servers
- Typical configuration examples
- Transition to Integrity with HP Superdome hybrid servers and mixed clusters
- Adding one Integrity server to a two-node HP 9000 cluster
- Adding two HP Integrity servers to a two-node HP 9000 cluster
- Adding one critical application and two new Integrity nodes to existing four-node HP 9000 cluster
- Mixed clusters as transition aid from HP 9000 to Integrity in a multi-tier SAP environment
- HP 9000 to Integrity transition service utilizing HP Serviceguard cluster technology
- How to implement a mixed HP 9000 / Integrity HP Serviceguard cluster
- For more information
Customers already using HP-UX 11i v2 to cluster HP Integrity systems will see the following change
when transitioning to HP-UX 11i v2UD2:
• The maximum cluster size increases from eight to 16 nodes.
Customers familiar with homogeneous HP Serviceguard clusters on either HP-UX 11i v1 or HP-UX
11i v2 will see the following change when transitioning to HP-UX 11i v2 September 2004:
• No support for vPARs existed at initial release of HP-UX 11i v2UD2. In 2005 a new vPar version
(A.04.01) had been released for HP 9000 and Integrity systems.
• Mixed clusters are not supported with SGeRAC since Oracle is not considering support for RAC in
a mixed cluster. However, in a configuration with two individual clusters in which Data Guard is
used for the data replication, the sending and receiving SGeRAC clusters can be of different
architecture, but each individual cluster has to be homogeneous. This configuration is supported by
Oracle without HP Continentalclusters
Architectural rules and typical configurations
This section explains the architectural rules for mixed PA / Integrity HP Serviceguard clusters. It lists
the requirements on the hardware and software sides.
Cluster hardware architecture
The HP-UX 11i v2UD2 Release Notes (available at http://docs.hp.com) specify the HP 9000 and
Integrity servers supported with the first common operating system for servers of both architectures.
Starting with HP Serviceguard A.11.16, they can be configured in a mixed cluster.
Not all storage arrays—especially older systems—are supported on new Integrity servers. Most often,
customers start with an existing homogeneous HP Serviceguard cluster consisting of HP 9000 systems,
including shared storage. Before adding HP Integrity nodes to the cluster, support for the shared
storage array on HP Integrity systems must be verified. The hardware configuration guide of the
particular server and the “Allowed storage systems in a mixed HP 9000 / Integrity HP Serviceguard
cluster” section provides this information.
Allowed servers in a mixed HP 9000 / Integrity HP Serviceguard cluster
The following servers are supported in a mixed HP 9000 / Integrity HP Serviceguard cluster:
• HP 9000 servers (PCI or PCI-X based backplane only)
– Entry level—rp24xx, rp34xx, rp44xx
– Mid-range—rp54xx, rp74xx, rp84xx
– High end—Superdome
– Current A-, L- and N-class servers
• HP Integrity servers
– Blade Server – BL60p
– Entry level—rx16xx, rx26xx, rx36xx, rx46xx, rx56xx, rx66xx
– Mid-range—rx76xx, rx86xx
– High end—Superdome
Allowed storage systems in a mixed HP 9000 / Integrity HP Serviceguard cluster
The storage system must be supported on both HP 9000 and Integrity Servers with HP-UX 11i v2UD2
to build a mixed cluster. Refer to “HP-UX 11i v2 storage connectivity matrix” for information regarding
currently shipping server/storage combinations.
8