HP vPars and Integrity Virtual Machines V6.1 Administrator Guide
533 MT/s bus, CPU version C2
24 logical processors (2 per socket)
Vendor identification: GenuineIntel
Processor version info: 0x0000000020000704
Family 32, model 0, stepping 7
Processor capabilities: 0x0000000000000005
Implements long branch
Implements -byte atomic operations
. . .
# hostname
host20
# machinfo -v
CPU info:
4 Intel(R) Itanium 2 9000 series processors (1.6 GHz, 24 MB)
533 MT/s bus, CPU version C2
8 logical processors (2 per socket)
Vendor identification: GenuineIntel
Processor version info: 0x0000000020000704
Family 32, model 0, stepping 7
Processor capabilities: 0x0000000000000005
Implements long branch
Implements -byte atomic operations
. . .
12.3.2.2 Private network setup
Source and target VSP systems should be connected with a dedicated, high-speed private network.
To use the private network during a migration, specify the name of the private network connection
in the hpvmmigrate -h option. As a helpful convention, if you specify a simple non-qualified
host name, the hpvmmigrate command appends -hpvm-migr to the name and checks if a host
alias has been defined for a private network corresponding to the simple name. If so, that host-alias
is used (that is, host-hpvm-migr is used instead of host.).
To set up a private network between two systems, identify which physical network interfaces are
to be used for the private network. Then connect those ports to the same network switch, or cable
them directly to each other with a cross-over cable if these two VSP systems are the only two systems
that will migrate guests. Also, BladeSystems in the same enclosure can be connected directly
together without an external switch or cable.
Assign private network IP addresses to those interfaces by editing /etc/hosts, /etc/
nsswitch.conf and /etc/rc.config.d/netconf on each host. Private (non-routable) IP
addresses in the range of 10.0.0.0 to 10.255.255.255 are good choices to use. (See the chapter
on "Network Addressing in the current version of the HP-UX LAN Administrator’s Guide for assistance
with subnetworking configuration: HP-UX LAN Adminstrator's Guide).
In the following example, VSP system host2 is using network interface lan3 as its private network
to connect to VSP host1:
Address aliases from/etc/hosts on the host1 and host2 systems:
127.0.0.1 localhost loopback
.17.81.141 host1 host1.alg.hp.com
.17.81.142 host2 host2.alg.hp.com
10.3.81.141 host1-hpvm-migr
10.3.81.142 host2-hpvm-migr
Excerpt from /etc/nsswitch.conf on the VSP systems:
hosts: files dns
ipnodes: files dns
Excerpt from /etc/rc.config.d/netconf on the host2 system:
208 Migrating virtual machines and vPars