Designing High Availability Solutions with HP Serviceguard and HP Integrity Virtual Machines

9
Known issues when using the Integrity VM Serviceguard toolkit:
• If the VM guest backing store resides on storage using a volume manager, the hpvmsg_package command
expects the volume manager to be activated so that the backing store is accessible on the node before you run the
command.
• The hpvmsg_package command does not add appropriate entries to the package configuration and control script
files for VM guests on CVM or CFS backing stores. After running the hpvmsg_package command to package a
guest that contains CVM or CFS backing stores, review and modify the package configuration, and control scripts
for each cluster member. As part of this process, add CVM and/or CFS backing store entries to these files.
• The hpvmsg_package command with the –U option must be used to deconfigure a VM guest from a Serviceguard
package and delete the package, rather than using the Serviceguard cmdeleteconf command. This is necessary to
reconfigure the VM guest to be started and stopped using HPVM commands after deleting the package.
• When using the hpvmsg_package command with the –U option to unpackage a VM guest, it will result in the
modify, runnable, and visible status for the VM guest being disabled on all nodes except where the command was
run. You must manually re-enable those status parameters before you can run the VM guest on those nodes.
• You should not use the SG-IVS Toolkit commands, cmdeployvpkg and cmmovevpkg for managing packages
created with the Integrity VM Serviceguard toolkit. The sole exception to this is when you wish to convert a
package using the Integrity VM Serviceguard toolkit to use the SG-IVS toolkit instead.
The HP Serviceguard toolkit for Integrity Virtual servers
The HP Serviceguard toolkit for Integrity Virtual servers (SG-IVS) version B.01.00 became available as a
Web release
in September 2011. It is initially available as a no-cost download from software.hp.com, under the Virtualization
software->Virtualization section. The documentation for this toolkit is available at:
www.hp.com/go/hpux-
serviceguard-docs. The SG-IVS toolkit is based on the Integrity VM Serviceguard toolkit, but has improved integration
with Serviceguard, and is intended as the going-forward replacement of the Integrity VM Serviceguard toolkit. The
SG-IVS toolkit can coexist with the Integrity VM Serviceguard toolkit; however, VM guest packages should be
managed with the commands provided by the toolkit they were created with. The SG-IVS provides two commands:
• cmdeployvpkg—This is an Package Easy Deployment command, used to take an existing Integrity VM guest
configured on Serviceguard cluster shared storage, and create a Serviceguard package which will start, stop, and
monitor the VM guest. In addition, cmdeployvpkg can be used for either offline or online conversion of a VM guest
package created using the Integrity VM Serviceguard toolkit, to use the SG-IVS toolkit. After a VM guest has been
packaged, the VM guest can only be started and stopped using Serviceguard commands; the HPVM commands
hpvmstart and hpvmstop are disabled from starting and stopping the VM guest. If the VM guest’s backing store is
located on a volume manager that supports exclusively shared storage, such as LVM or VxVM, the command will
configure the activation of the volume manager in the generated package. If the VM guest’s backing store is
located on a volume manager that supports concurrently shared storage, such as Shared LVM (SLVM) the command
will configure the generated package to have a same node dependency on the multi-node package for the volume
group or mount point package.
• cmmovevpkg—This command is used to perform an online migration of VM guests in Serviceguard packages.
Note that online migration is only supported for VM guests running on concurrently shared storage, such as whole
disk backing stores, Shared LVM volume groups or CFS file systems.
Because the SG-IVS toolkit has been implemented using Serviceguard package modules, it is also possible to
generate modular packages for VM guests using the Serviceguard cmmakepkg command. To create a VM guest
package:
cmmakepkg –m tkit/vtn/vtn –n <vm_name> pkg.conf
Where:
• cmmakepkg is the HP Serviceguard command to create the package.
• tkit/vtn/vtn is the name of the SG-IVS toolkit module.
• <vm_name> is the name of package. VM name and the package name must be the same.
• pkg.conf is the name of the package configuration file.