HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

NOTE: APA is not supported in the VM guest, and primary and secondary LAN failover
is not provided in the VM Host.
2. On each of the VM Hosts, use the hpvmnet command to create vswitches.
3. Create the storage configuration on each of the VM Hosts and physical Serviceguard Nodes.
• System disk storage for physical nodes, as well as VM nodes, can be of any type support
by Serviceguard and Integrity VM.
• System disks are required to be presented or available only on the VM Host or physical
node where the node runs.
• Shared package storage is limited to whole disk storage.
• Shared package storage must be presented to each VM Host and physical node where
the package application runs.
4. Ensure that each guest has access to a quorum server or cluster lock disk.
5. Run the hpvmcreate command to create the virtual machine.
6. Run the hpvmstart command to start the virtual machine.
On the Integrity VM guest, perform the following steps:
1. Install and configure the guest operating system and patches.
2. Install the Integrity VM guest kits.
3. If Serviceguard is not included in the HP-UX OE, install Serviceguard on the virtual machine
nodes.
4. Install Serviceguard on the HP-UX guests that will run the application.
On any virtual machine node or physical node, perform the following steps:
1. Use the cmquerycl command to specify the nodes to be included in the cluster and to
generate a template for the cluster configuration file. For example, to set up a cluster named
gcluster that includes nodes host1 and host2, enter the following command:
# cmquerycl -v -C /etc/cmcluster/gcluster.config -n host1 -n host2 -q quorum-server-host
Include the -q option if a quorum server is used on the cluster.
2. Edit the /etc/cmcluster/cluster-name.config file (where cluster-name is the
name of the cluster specified in the cmquerycl command). For details about modifying the
information in the cluster configuration file, see the Managing Serviceguard manual.
3. Use the following command to verify the contents of the file:
# cmcheckconf -k -v -C /etc/cmcluster/gcluster.config
This command ensures that the cluster is configured properly.
4. Generate the binary configuration file and distribute it using the following command:
# cmapplyconf -k -v -C /etc/cmcluster/gcluster.config
5. Start the cluster using the following command:
# cmruncl
These procedures provide an example of creating guest application packages. For information
about how to set up your Serviceguard configuration, see the Managing Serviceguard manual.
11.2.11 Modifying and Managing the Virtual Machine and the Cluster
While the interrelated configuration of the physical hosts, VM Hosts, virtual machine and
Serviceguard must always be taken into consideration; the modification and management of the
virtual machine and Serviceguard cluster, in a VM as Serviceguard Node configuration, are
relatively independent of each other. You modify and manage a Serviceguard cluster by using
typical Serviceguard tools and procedures ,while you modify and manage virtual machines by
using Integrity VM tools and procedures. The virtual machine is basically unaware that
11.2 VMs as Serviceguard Nodes 193