HP Serviceguard Toolkit for Integrity Virtual Servers User Guide (June 2013)

way. However, the shared storage must be defined as VM or vPar guest storage devices that are
exclusively used by a specific VM or vPar guest.
Both standard LVM and VxVM logical volumes are active and available on only one Serviceguard
node at a time. Whole disks, Shared LVM logical volumes, and VxVM logical volumes managed
by the Cluster Volumes Manager (CVM) and files on a Cluster Files System can be configured to
be active and available on multiple Serviceguard nodes simultaneously. When you configure VMs
or vPars as Serviceguard packages, ensure that only one guest on one node can access these
backing store types.
The easy deployment script, cmdeployvpkg, offered by the toolkit is used to create the
Serviceguard package configuration file to deploy high availability solution to VM or vPar guests
in Serviceguard environment. This script determines the cluster shared backing store and application
data storage used by the VM or vPar guest that is to be packaged. Also, it adds the appropriate
logical volume and mount point entries into the package configuration file for VM or vPar guest
failover.
When you create a Serviceguard cluster with virtual machines acting as packages, the
cmdeployvpkg script correctly identifies CVM logical volumes and CFS files backing stores used
by guests, but requires you to verify or provide activation modes, and package dependencies for
the backing stores.
For information on setting up the storage for Serviceguard package, see the latest:
• Managing Serviceguard manual available at www.hp.com/go/hpux-serviceguard-docs →
HP Serviceguard
• Veritas Storage Foundation 5.0.1 Cluster File System Administrator's Guide Extracts for the
HP Serviceguard Storage Management Suite on HP-UX 11i v3 manual available at
www.hp.com/go/hpux-serviceguard-docs → HP Serviceguard Storage Management Suite
A.03.xx (with 5.0.1 Veritas)
NOTE: If you configure a guest with either DIO LAN or NPIV disks or both, you must use the
application monitoring services to configure DIO LAN or NPIV disk monitoring or both.
For more information on configuring DIO LAN and/or NPIV disk monitoring, see “Configuring
DIO LAN and NPIV disks monitoring using cmappmgr/cmappserver” (page 28).
Storage considerations 9