HP Serviceguard Toolkit for Integrity Virtual Servers manual Change the vgnamecmd to vgchange -a s

5.On the secondary nodes:

•Optional: If the vswitch (vlan), identical to the one created on the primary node is not configured in step 2, then you must configure it.

6.On the primary node, distribute the virtual machine or vPar to the secondary node

7.On the secondary nodes:

a.Verify the virtual machine or vPar operation.

b.Stop the virtual machine or vPar.

NOTE: To configure more than two nodes for package configuration:

a.Repeat from step 4–f to 7–b.

b.Distribute the virtual machine or vPar to remaining nodes from the secondary node.

8.On the primary node:

a.Reconfigure, import, activate, and mount virtual machine or vPar storage.

b.Verify the virtual machine or vPar operation.

For more information on Integrity VM or HP-UX vPars commands, see the latest HP Integrity Virtual Machines: Installation, Configuration, and Administration or HP-UX vPars and Integrity VM Administrator Guide manual respectively at http://www.hp.com/go/hpux-hpvm-docs.

Configuring VMs/vPars as Serviceguard packages having SLVM backing storage

You can deploy VMs or vPars as Serviceguard packages. Multiple virtual machines can have virtual disks mapped to logical volumes in a single SLVM volume group. If one of these VMs or vPars is moved to another node (VM or vPar Host) in the Serviceguard cluster, the other VMs or vPars must have continued access to logical volumes in that volume group. To enable the continued access, configure Serviceguard multi-node packages for the SLVM volume groups:

1.Create a Serviceguard multi-node package configuration file for each SLVM volume group:

#mkdir /etc/cmcluster/hpvm_vgsharedA

#cd /etc/cmcluster/hpvm_vgsharedA

#ls

#cmmakepkg -m sg/multi_node -m sg/volume_group > hpvm_vgsharedA.conf Package template is created.

This file must be edited before it can be used.

#

2.Edit the configuration file, making the following modifications:

a.Name the package (for example, hpvm_vgshareA).

b.Change the vgname_cmd to vgchange -a s.

c.Add the vg name for the SLVM volume group. For example, if vgsharedA is the SLVM volume group that the virtual machines use on this VM Host, add the following line:

vg vgsharedA

d.If only some nodes in the cluster have the SLVM volume groups, identify each of those nodes with the node_name attribute. If all nodes can run the SLVMs, retain the value of the attribute as asterisk (*).

e.Verify the configuration and, if it is valid, apply the package configuration to the cluster:

#cmcheckconf -P /etc/cmcluster/hpvm_vgsharedA/hpvm_vgsharedA.conf Attempting to validate hpvm_vgsharedA.

...

cmcheckconf: Verification completed with no errors found. Use the cmapplyconf command to apply the configuration.

#cmapplyconf -P /etc/cmcluster/hpvm_vgsharedA/hpvm_vgsharedA.conf Attempting to validate hpvm_vgsharedA.

...

Modify the package configuration ([y]/n)? y

Creating packages 13