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

Serviceguard cluster. Depending on the configuration of the cluster, the application configured
as a Serviceguard package can fail over:
• From one guest to another guest in the same VM Host system
• From one guest to another guest in another VM Host system
• From the guest on a VM Host system to a separate physical server or nPar
You can even mix and match VMs as Serviceguard Nodes configurations to meet your specific
requirements. The following sections describe the VMs as Serviceguard Nodes configurations.
11.2.1 Cluster in a Box
Figure 11-1 shows the configuration of an application package that can fail over to another guest
on the same VM Host system.
Figure 11-1 Guest Application Failover to Another Guest on the Same VM Host
VM Host 1
Serviceguard Cluster
Serviceguard
Package
Failover
Guest VM2
Guest VM1
Physical Node 1
In this configuration, the primary node and the adoptive node are guests running on the same
VM Host system. This cluster does not provide protection against Single Point of Failure (SPOF),
because both the primary cluster member and the adoptive cluster member are guests on the
same physical machine. However, this configuration is useful in testing environments.
If you are running more than one guest on the VM Host system, and you need to share the same
storage among the guests, you must change the SHARE attribute of the shared disk to YES using
the hpvmdevmgmt command, as follows:
# hpvmdevmgmt -m gdev:/dev/rdsk/c6t1d4:attr:SHARE=YES
For more information about using the hpvmdevmgmt command, see Section 9.8 (page 138).
11.2.2 Virtual-to-Virtual Cluster
Figure 11-2 shows the configuration of an application package that can fail over to a guest running
on a different VM Host system.
11.2 VMs as Serviceguard Nodes Configurations 155