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

...
Modify the package configuration ([y]/n)? y
Completed the cluster update
e. Run the package associated with the SLVM and virtual machine independent order:
# cmrunpkg hpvm_vgsharedA
Running package hpvm_sharedA on node ghost1
Successfully started package hpvm_sharedA on node ghost1
Running package hpvm_sharedA on node ghost2
Successfully started package hpvm_sharedA on node ghost2
cmrunpkg: All specified packages are running
# cmrunpkg slvmtest
Running package slvmtest on node ghost1
Successfully started package slvmtest on node ghost1
cmrunpkg: All specified packages are running
NOTE: If the package associated with the SLVM is not run prior to starting the package
associated with the virtual machine, then a message similar to the following is displayed:
# cmrunpkg slvmtest
Unable to execute command. Dependency on the following packages not met:
hpvm_vgsharedA
cmrunpkg: Unable to start some package or package instances
11.5.3 Online Migration of VMs with SLVM Virtual Disks in VM as Serviceguard
Package Configurations Requires Manual Reconfiguration
Successful online migration of VMs with SLVM virtual disks in VMs as Serviceguard Package
configurations requires you to configure each SLVM as an independent multinode package.
Additionally, the VM as Serviceguard Package must be modified to indicate a new package
dependency that is the package name associated with the SLVM package.
If the SLVM created and associated with VM is created and associated with the package, perform
the following steps:
1. Create and apply to the cluster an SLVM package for each using multinode and
volume_group modules.
2. Edit the VM package configuration:
a. Remove all references to the volume data reference for each SLVM.
b. Add a dependency for each SLVM package associated with the VM.
c. Check and apply the VM package configuration.
3. Ensure that all SLVM packages are running on all nodes.
4. Ensure that the VM package is running on the desired node.
5. Verify failover and online migration function as expected prior to placing systems into
production.
11.6 Troubleshooting Network Problems When Using Serviceguard
If the guest has network problems after failover:
• Make sure the vswitches are 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 parameter are
system- and load-dependent.
— 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
206 Using HP Serviceguard with Integrity VM