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

• VxVm - Before starting a package, ServiceGuard requires that all disk groups associated
with the package are deported. See the Managing ServiceGuard manual for details.
• Files - Before starting a package, ServiceGuard requires that filesystems of file backing stores
associated with the package are unmounted.
If the guest has problems accessing network, make sure the network devices are available on the
VM Host system. Packages do not start if any of their defined subnets are unavailable. This causes
multiple failures if no standby LANs are available, or when one or more switches, hubs, interfaces
or cables fail.
A common issue when starting a package is the lack of available memory. For more information
about providing the required memory resources, see Chapter 3 (page 31) .
11.5.2 Creating Distributed Guests
This manual describes how to use the hpvmsg_package script to help you configure guests as
Serviceguard packages. If you create the Serviceguard package configuration and control scripts
manually instead, use the following options to the hpvmcreate , hpvmmodify, or hpvmclone
command to identify the Serviceguard package name and to mark the guest as a distributed
guest.
• Use the -i option to specify the Serviceguard package. (For example, -i
SG_package_name.)
• Use the -j 1 option to specify that the guest is a distributed guest.
For more information, read the hpvmsg_package file.
11.5.3 Networking
If the guest has network problems after failover:
• Make sure the vswitches are properly configured on the adoptive node. If you are using the
VLAN feature of Integrity VM vswitches, make sure that appropriate VLAN IDs are assigned
to each port.
• Adjust the values of the following Serviceguard parameters in the cluster configuration file.
The correct settings for the HEARTBEAT_INTERVAL and the NODE_TIMEOUT parameters
are system- and load-dependent. Specifically:
— The HEARTBEAT_INTERVAL parameter specifies the normal interval between the
transmission of heartbeat messages from one node to the other in the cluster. The value
of the HEARTBEAT_INTERVAL parameter is entered in microseconds; the default value
is 1,000,000 microseconds. Setting the value of this parameter to less than the default is
not recommended. The default should be used where possible. The maximum value
recommended is 15 seconds, and the maximum value supported is 30 seconds. This
value should be at least half the value of the NODE_TIMEOUT parameter.
— The NODE_TIMEOUT parameter specifies the amount of time after which the Serviceguard
node may decide that the other node has become unavailable and initiate cluster
reformation. This parameter is entered in microseconds; the default value is 2,000,000
microseconds. The minimum is two times the value of the HEARTBEAT_INTERVAL
parameter. The maximum recommended value for this parameter is 30,000,000.. The
default setting yields the fastest cluster reformations. However, using the default value
increases the potential for spurious reformations due to momentary system hangs or
network load spikes. For many installations, a setting of 5,000,000 to 8,000,000 (5 to 8
seconds) is more appropriate. The maximum value recommended is 30 seconds and
the maximum value supported is 60 seconds.
166 Using HP Serviceguard with Integrity VM