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
v2UD2 as described previously. The process of converting an Integrity cluster to a mixed HP 9000 /
uard upgrades.
•
cluster nodes) to the existing cluster.
• new requirements:
ies
M th an existing Integrity cluster
rchitectures and would like
to ional steps are required beyond the ones
lis -UX 11i v1 (most likely) or HP-
on HP-UX11i v2 (most likely), HP-UX 11i
v1.6, or HP-UX 11i v2UD2 already. The following steps are involved:
P Serviceguard A.11.16,
• s the remaining cluster. Which of the original clusters will be chosen is
– itical application
packages running on a specific node and restart them on another
-be-dismissed cluster.
h node is moved to the mixed cluster, whether to leave
• R re the package and move it to the mixed cluster if not already done in the step before.
• have two sets of binaries, if available.
• Test the various failover scenarios and configurations.
Integrity cluster is similar to converting a HP 9000 cluster to a mixed HP 9000 / Integrity cluster,
which involves the following steps:
• Upgrade the server 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 Serviceg
– Move applications back to their original node and test failure scenarios.
– Continue the process through the other nodes in the cluster.
Add new HP 9000 systems (with the same version of HP-UX and HP Serviceguard as the existing
Reconfigure the cluster/package to consider
– New and/or changed primary and failover nodes
– Special requirements caused by two sets of application binar
• Test the various failover scenarios and configurations.
erging an existing HP 9000 cluster wi
In the scenario that a customer already deploys different clusters of both a
merge a HP 9000 with an Integrity cluster, a few addit
ted previously. In this scenario, the HP 9000 cluster could be on HP
UX 11i v2UD2 already, and the Integrity cluster could be
• If nodes of both clusters are not already on HP-UX 11i v2UD2 and H
upgrade them at least to HP-UX 11i v2UD2 and HP Serviceguard A.11.16 through the rolling
upgrade process within their homogeneous cluster, 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 Serviceguard upgrades.
– Move applications back to their original node.
Choose one of the clusters a
expected to be case-specific. The decision can be based on the cluster with the:
Most cr
– Largest number of nodes
– Least outstanding changes
• Move the nodes from the cluster that will not survive to the intended mixed HP 9000 / Integrity
cluster, one by one, following these steps:
– Shut down the application
node.
– Remove the node from the to
– Add the node to the intended mixed cluster.
– Decide, on a per-package level after eac
the package on the to-be-dismissed cluster or transition it to the mixed cluster.
econfigu
Consider mixed requirements. The application might
28