HP-UX vPars and Integrity VM V6.3 Administrator Guide

NOTE: A transient network error might cause the vswitch connectivity check of the hpvmmigrate
command to report a failure. If the connectivity check fails, retry the migration by rerunning the
hpvmmigrate command.
If the network connectivity check of the hpvmmigrate command continues to fail, verify the vswitch
and network configuration, and test connectivity with the nwmgr command.
If the vswitch connectivity required by the guest on the target VSP is properly configured and
verified, you can use the hpvmmigrate -w option to bypass vswitch connectivity checks.
The Online VM migration feature is supported with Serviceguard packaged guests. For more
information, see the HP Serviceguard Toolkit for Integrity Virtual Servers User Guide at
nl
http://www.hp.com/go/hpux-serviceguard-docs.
12.2.5 Using the hpvminfo command in the guest
The hpvminfo command is a part of the Integrity VM guest kit and must be installed on all the
guests. In the case of Integrity VM V6.3, if VirtualBase B.06.30 is installed on the guest, the guest
kit need not be installed. You can use the hpvminfo -V option to view information about the
guest and the current VSP.
Following is a shell script using the hpvminfo -M option (for machine-readable output) that you
can run on any Unix guest to know when an online migration has occurred. The script gets the
guest name (G), and the current host (H1), and then begins an infinite loop testing and reporting
whether the host on which it is running has changed. Terminate the shell script with a ^C.
G=$(hpvminfo -M | awk -F : '{print $12;}')
H1=$(hpvminfo -M | awk -F : '{print $7;}')
echo $(date) $G: Current host is $H1
while true
do
H2=$(hpvminfo -M | awk -F : '{print $7;}')
if [ "$H1" != "$H2" ]; then H1=$H2; echo $(date) $G: host is now $H2; fi
done
Following is a sample output from this script:
Tue Aug 26 10:52:39 PDT 2008 vm6: Current host is host2
Tue Aug 26 10:53:36 PDT 2008 vm6: host is now host1
Tue Aug 26 10:54:28 PDT 2008 vm6: host is now host2
Tue Aug 26 10:55:19 PDT 2008 vm6: host is now host1
12.3 VSP and VM configuration considerations
This section discusses the configuration information required for a successful migration and how
to chose the hosts and guests that can participate in OVMM. Effective migration of online guests
among VSPs depends on proper configuration of the networks and storage that is connected to
the VSP and used by the online guests. The hpvmmigrate command verifies that the source and
target hosts provide the guest with symmetric accessibility to network and storage resources. If you
set up the configuration on both hosts before you migrate the guest, the migration task is easier
and faster.
To migrate guests among a group of VSP servers, the VSPs require common access to storage
devices, networks, and virtual switch configurations. Pathnames to storage must not be identical;
however, the same LUNs assigned to a guest must be presented to both the source and the target
VSPs. There must be equal access to guest storage and equal network reachability on both the
source and the target VSPs. The network on the target VSP must be able to make all the same
network connections that can be used by the guest on the source VSP.
A vswitch of the same name, connected to the same network must be available on the source and
target VSP servers. The hpvmmigrate command verifies connectivity before migration. You can
use the hpvmmigrate -w option to bypass the vswitch connectivity checks, but only use -w if
12.3 VSP and VM configuration considerations 205