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

security. Also, a high-speed, private network helps ensure efficient online migrations and
preserves the bandwidth and performance of the site network.
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 VM Host 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
10.3.1.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 VM Host
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:
• hpvmmigrate -h host39 — Look up host39-hpvm-migr first, and if not found, look
up host39.
• hpvmmigrate -h host39-hpvm-migr — Look up host39–hpvm-migr.
• hpvmmigrate -h host39.atl — Look up host39.atl.
Of course, target.fully.qualified.domain-name will not be modified.
By following this convention, defining an alias with suffix —hpvm-migr for the private network
connections, you block use of the site network for online migrations in case someone accidentally
specifies the target VM Host's hostname for the hpvmmigrate -h option.
10.3 VM Host and Virtual Machine Configuration Considerations 177