HP-UX vPars and Integrity VM V6.1.5 Administrator Guide (5900-2295, April 2013)

SUBNET_MASK[3]=255.255.252.0
BROADCAST_ADDRESS[3]=""
INTERFACE_STATE[3]=""
DHCP_ENABLE[3]=0
INTERFACE_MODULES[3]=""
Example output from netstat on the host2 VSP system:
# netstat -in
Name Mtu Network Address Ipkts ...
lan3 1500 10.3.80.0 10.3.81.142 1022313379 ...
lan0 1500 .17.80.0 .17.81.142 2420913 ...
lo0 32808 127.0.0.0 127.0.0.1 123762 ...
You can also use the nwmgr command to help verify the connection. The following example uses
the nwmgr command on host1 to get the Station Address (MAC):
# nwmgr
Name/ Interface Station Sub- Interface Related
ClassInstance State Address system Type Interface
============== ========= ============== ======== ============== =========
lan2 UP 0x001E0B5C0572 igelan 1000Base-SX
lan0 UP 0x001E0B5C05C0 igelan 1000Base-SX
lan1 DOWN 0x001E0B5C05C1 igelan 1000Base-SX
lan3 UP 0x001E0B5C0573 igelan 1000Base-SX
lan900 DOWN 0x000000000000 hp_apa hp_apa
lan901 DOWN 0x000000000000 hp_apa hp_apa
lan902 DOWN 0x000000000000 hp_apa hp_apa
lan903 DOWN 0x000000000000 hp_apa hp_apa
lan904 DOWN 0x000000000000 hp_apa hp_apa
The following example on host2 tests the connection to host1's Station Address
0x001E0B5CO573:
# nwmgr --diag -A dest=0x001E0B5C0573 -c lan3
lan3: Link check succeeded.
Use the ssh and the env commands to check that the private network connection is working
properly between two VSP systems, and that you are actually using the correct network interfaces.
For example:
# ssh host1-hpvm-migr env | grep -i connection
SSH_CONNECTION=10.3.81.142 52215 10.3.81.141 22
NOTE: Because Integrity VM disables the TSO and CKO capabilities on the LAN interface's IP
address (resulting in poorer than expected VM Host data-transfer performance), HP recommends
that you dedicate a LAN interface solely for Online VM Migration data transfer to improve data
transfer time. That is, to receive the best performance on host-to-remote data transfers on a LAN
interface, do not configure a vswitch over it.
12.3.2.3 Conventions for using target-hpvm-migr names for private networks
If the name specified for the hpvmmigrate -h option is a simple basename, the hpvmmigrate
command concatenates its conventional private network suffix -hpvm-migr to the basename and
first checks if that name can be resolved. A simple basename is a reasonably short string with no
specified domain hierarchy (for example, period (.) in the name). The simple basename cannot
already contain the conventional suffix —hpvm-migr either. You should add the alias
target-hpvm-migr to /etc/hosts that maps to the private IP network address for VSP target
and modify /etc/nsswitch.conf, so lookups reference /etc/host before using DNS. (The
resolution check is done by looking up the modified name with the gethostbyname function, so
DNS is used if there is no alias in /etc/hosts.)
Because this is just a convention implemented local to each host, administrators can use it or not..
If this convention is configured correctly, both target and target-hpvm-migr resolve to the
proper address. For example:
12.3 VSP and virtual machine configuration considerations 213