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
29
In
W
ms,
d desired ISV individually.
stalling a new mixed cluster
hen no cluster exists, there is little to consider because nodes of both architectures form the cluster.
One point to address is the requirements caused by two sets of application binaries.
You must have HP-UX 11i v2UD2 and HP Serviceguard A.11.16 or newer installed on all syste
s before creating the cluster or by
which can be achieved by installing the MCOE on all system
installing the base operating system, HP Serviceguard, an