HP-UX vPars and Integrity VM V6.3 Administrator Guide
Table 28 Itanium processor families (continued)
SeriesModelFamily
Itanium 9100132
Itanium 9300232
Itanium 9500033
You can lookup processor Family as shown in the following example output from the machinfo
-v command. (As more processors families and models are added, more specific capability
requirements might be necessary.) The systems host19 and host20 in this example are compatible
for migration, because they have the same processor family (32) and therefore they belong
to the same processor group as defined earlier.
# hostname
host19
# machinfo -v
CPU info:
12 Intel(R) Itanium 2 9000 series processors (1.6 GHz, 24 MB)
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 must 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 is 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 the physical network interfaces that 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 migrates guests. Also, BladeSystems in the same enclosure can be connected directly together
without an external switch or cable.
208 Migrating VMs and vPars