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
How to implement a mixed HP 9000 / Integrity HP
cluster. The
depend on
wo major steps are involved:
• All systems must run the same version of HP-UX, as a minimum 11i v2UD2.
lling upgrade process to upgrade
– cluster, use the rolling upgrade process to bring all
Starting with an existing cluster
Cu
or more clusters in plac her the customer uses only systems of a single
in different clusters, the procedure for how to achieve a
wing sections.
are already in use and the customer
wants to transition to Integrity with individual applications. The following high-level process describes
• f HP-UX and HP Serviceguard as the existing
•
St cluster
Th cause the HP-UX version is
rd version that might be upgraded to
A.11.16 or later through the rolling upgrade process. In the rare circumstance that the nodes are on
HP-UX 11i v1.6 or HP-UX 11i v2, they must be upgraded to at least HP-UX 11i v2UD2. This upgrade
process is similar to the rolling upgrade process of HP 9000 nodes from HP-UX 11i v1 to HP-UX 11i
Serviceguard cluster
There are several paths to get to a supported mixed HP 9000 / Integrity HP Serviceguard
starting point is always a currently supported configuration. The transition process details
the current customer configuration. T
– Upgrade the systems to the desired version of HP-UX before adding them to the cluster.
– If the systems are already part of an existing cluster, use the ro
the systems to the desired version of HP-UX.
•
All nodes must have the same version HP Serviceguard installed, as a minimum A.11.16.
Install the desired version of
– HP Serviceguard before adding a new node to a mixed HP 9000 /
Integrity cluster.
If the systems are already part of an existing
nodes to the same version HP Serviceguard.
stomers interested in mixed HP 9000 / Integrity HP Serviceguard clusters most probably have one
e already. Depending on whet
architecture or HP 9000 and Integrity servers
mixed cluster varies, as described in the follo
Starting with an existing HP-UX 11i v1 HP 9000 cluster
The most typical scenario in which customers would like to deploy mixed clusters is when existing HP
9000 clusters with HP Serviceguard 11.15 on HP-UX 11i v1
the necessary steps:
• Upgrade the servers to at least HP-UX 11i v2UD2 and HP Serviceguard A.11.16 through the rolling
upgrade process as described in Appendix E of the HP Serviceguard user manual:
– Shut down the application packages running on a specific node and restart them on another
node.
– Perform HP-UX and HP Serviceguard upgrades.
– Move applications back to their original node and test failure scenarios.
– Continue the process through the other nodes in the cluster.
Add new Integrity systems (with the same version o
cluster nodes) to the existing cluster.
:
Reconfigure the cluster/package to consider new requirements
New and/or c
– hanged primary and failover nodes
– Special requirements caused by two sets of application binaries
• Test the various failover scenarios and configurations.
arting with an existing HP-UX 11i v1.6 or v2 Integrity
is use case is much less likely than the one described previously. Be
probably already up to date, it is only the HP Servicegua
27