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

Executive summary
With the advent of HP-UX 11i version 2 (HP-UX 11i v2), HP Integrity (Intel® Itanium®-based) systems
are becoming prevalent in customer environments. Many customers are using HP Serviceguard to
protect their mission-critical applications. For their HP 9000 servers, customers are running HP UX 11i
version 1 (HP-UX 11i v1) and they are using HP-UX 11i version 2 (HP-UX 11i v2) for their HP Integrity
servers. In the fourth calendar quarter of 2004, HP shipped an update of its HP-UX 11i v2 operating
system that supports both HP 9000 and Integrity systems. This update was referred to as HP-UX 11i
v2 September 2004 update or release or as HP-UX 11i v2 update 2 (HP-UX 11i v2UD2) when it
released. For the remainder of this document it will be referred to as HP-UX 11i v2UD2.
Prior to this version of HP-UX, it was not possible to combine HP 9000 and Integrity servers into a
single cluster because two different versions of the operating system were required for them. It has
also not been possible to have two versions of HP-UX or two versions of HP Serviceguard in the same
cluster, except in a rolling upgrade situation. Starting with HP-UX 11i v2UD2 and HP Serviceguard
A.11.16, it is possible to have HP 9000 and Integrity servers in the same cluster.
It is expected that this mixed cluster support will:
• Provide a much easier transition from one server architecture to the other
• Provide investment protection for existing customers
• Allow a much longer transition period than what would have been possible by having each
architecture running in a separate cluster
Version history
Table 1. HP-UX 11i v2 storage connectivity
version 1.0
The initial version of this document did not contain a version number. It was
published at the time when the requirements for mixed clusters became true.
These are a common operating system for HP 9000 and Integrity servers with
HP-UX 11i v2UD2 and a common Serviceguard version (A.11.16) for both
hardware platforms.
version 1.1
Since the initial version of this document several events made an update
necessary. Version 1.1 reflects the following changes:
• availability of Serviceguard Storage Management Suite / Cluster File
System with Serviceguard A.11.17
• support for HP Superdome hybrid servers allowing mixing of PA-RISC and
Intel® Itanium® 2 in one Superdome
• change of ISV support status for
– Oracle single instance database
– some SAP configurations
– Informix IDS 10.0
• Support for M by N Metrocluster/Symmetrix Remote Data Facility (SRDF)
became available for Integrity. The current versions of HP Metrocluster and
Continentalclusters have no longer specific requirements for mixed clusters
and fully support them.
Introduction
Starting with HP-UX 11i v2UD2, HP provides one operating system version with similar functionality to
the HP 9000 and Integrity lines of servers.
3