HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

Figure 11-2 Guest Application Failover to a Guest on a Different VM Host
Serviceguard Cluster
VM Host VM Host
Guest VM1
Guest VM2
Serviceguard
Package Failover
Physical Node 1 Physical Node 2
In this configuration, the Serviceguard nodes are guests running on either separate hard partitions
(nPars) or HP Integrity servers. Note that Integrity VM does not run on soft partitions (vPars).
11.2.3 Virtual-to-Physical Cluster
Figure 11-3 shows the configuration of an application package that can fail over to a physical
node or partition that is not running Integrity VM software. In this case, the physical node may
be a discreet physical system, a hard partition (nPars), or a soft partition (vPars).
Figure 11-3 Guest Application Failover to an HP Integrity Server
Serviceguard
Package Failover
VM Host Physical Node
Guest VM
Serviceguard
Cluster
The Serviceguard cluster consists of a VM Host system and a Serviceguard node that is not
running Integrity VM. The application configured as a Serviceguard package can fail over to the
physical node. Alternatively, you can run the application on the physical node and configure
the guest on the VM Host system as the adoptive node.
11.2.4 Configuring VMs as Serviceguard Nodes
To configure a Serviceguard cluster that allows an application to fail over from one guest to
another, complete the following procedure
1. Install Serviceguard on the HP-UX guests that may run the application.
2. For the virtual/physical cluster, install Serviceguard on the physical node.
156 Using HP Serviceguard with Integrity VM