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
Figure 2. Original four-node HP 9000 cluster
Node A
PA-8800
App2
App1
OraDB
NFS
Failover
OK
OK
Node C
PA-8800
Node B
PA-8800
Node D
PA-8800
The customer would like to first transition his NFS server to Integrity. In order to achieve this, he first
moves the NFS server to cluster node A and under some circumstances App2 to cluster node C. Then
he upgrades the firmware of Superdome 1 if needed and replaces the PA-8800 CPUs with the
desired Intel® Itanium® 2 CPUs.
Four-node mixed cluster with one HP 9000 Superdome and one hybrid Superdome
After the upgrade is completed, he moves the application packages back to their primary nodes. The
NFS server’s primary node and the database’s secondary node are now on nPars with Intel®
Itanium® 2 CPUs.
Figure 3. Four-node mixed cluster with one HP 9000 Superdome and one hybrid Superdome
Now the customer can gain experience with Integrity servers in his production mission critical
environment at the granularity of a single application and at the time he chooses. The support for PA-
RISC and Intel® Itanium® nPars in a HP Superdome hybrid server allowed him to only upgrade part
of his Superdome. Support for mixed PA-RISC / Intel® Itanium® architecture clusters by Serviceguard
and his applications – in this example a single instance Oracle database and a NFS server – allowed
him to only upgrade one cluster node and still maintain the same level of high availability. This
example demonstrates how utilizing available technologies provides customers with a smooth path to
Integrity servers without requiring a huge investment from the beginning.
App2
App1
OraDB
Failover
OK
OK
Node A
PA-8800
Node B
Itanium®
NFS
Node C
PA-8800
Node D
PA-8800
17