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

Starting with HP Serviceguard A.11.16, HP 9000 and Integrity servers that run HP-UX 11i v2UD2
can be configured to run in a single heterogeneous HP 9000/Integrity Serviceguard cluster.
Purpose of document
This technical whitepaper explains how to create a new cluster with both types of servers and how to
upgrade an existing HP 9000 cluster or an existing HP Integrity cluster to include both server types.
The document:
• Explains the new feature of HP Serviceguard that provides the opportunity to mix HP Integrity and
HP 9000 servers in a single HP Serviceguard cluster
– HP-UX 11i v2UD2 provides the same feature set to both HP 9000 and Integrity platforms.
– HP Serviceguard A.11.16 provides feature parity between HP9000 and Integrity systems.
– Many independent software vendors (ISVs) provide their software in two versions, one for HP
9000 and the other for HP Integrity servers.
• Informs the reader about configuration rules and best practices in regards to mixed clusters for:
– Cluster hardware
– HP-UX 11i v2UD2 and subsequent releases
– nPars and vPars
– HP Serviceguard A.11.16 and subsequent releases
– Protected applications
– Rules when mixing architectures with a single application
– Rules when mixing architectures with multiple applications
– Rules when mixing architectures for multi-tier applications
Definition of terms
Table 2.
Term Definition
Aries
Aries is the HP-UX PA-RISC to HP-UX Intel® Itanium® binary
emulator. Aries transparently emulates both 32- and 64-bit
HP-UX PA-RISC applications when running on HP Integrity
servers.
CFS
Serviceguard Cluster File System based on Veritas CFS;
included in some of the HP Serviceguard Storage
Management Suite bundles.
CVM
Veritas Cluster Volume Manager; included in some of the
Serviceguard Storage Management Suite bundles.
HP-UX 11i v1
HP-UX 11i version 1; HP 9000 server operating system (PA-
RISC) only; internally also know as 11.11 (output of uname
–r command).
HP-UX 11i v2
HP-UX 11i version 2; HP Integrity server operating system
(Intel® Itanium®) only until September 2004; internally also
know as 11.23 (output of uname –r command). All future
versions of HP-UX 11i v2 run on both, HP 9000 and
Integrity servers.
HP-UX 11i v2UD2
HP-UX 11i version 2 September 2004 update; first common
operating system for HP 9000 and Integrity servers; also
know as 11i v2 update 2 (output of swlist for the Operating
Environment will show B.11.23.0409).
ISV independent software vendor
4