Migrating vPar Systems to Integrity VM

8 of 13
Virtual Switch Configuration
Now that the Integrity VM software is installed, we will need to set up the virtual networking for use
by the virtual machines hosted there. For each subnet and gateway used by the virtual partitions, a
LAN must be identified on the VM Host that is connected to that subnet and gateway. The simplest
approach to this is to define a virtual switch for each of the LANs used by the virtual partitions. Using
the LAN descriptions for the partitions (discussed previously in the section ‘Collect the network (LAN)
information for each vPar’), these LANs are identified, on the VM Host, by their hardware path or
MAC address (either will suffice).
After identifying the LANs, create a virtual switch for each of them using hpvmnet, labeling them for
ease of management (depending on your scenario).
For our example partitions (see the section ‘Collect the network (LAN) information for each vPar’
above), we are looking for the following HW paths and/or MAC addresses:
Host (vPar) LAN path(s) MAC address(es)
vpolyd02 0/0/2/1/0 0x00306EF46D5A
vpolyd05 1/0/0/1/0 0x00306E4B5A56
vpolyd06 1/0/2/1/0 0x00306EF46DC1
From the VM Host, examine lanscan for the appropriate LANs:
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/1/0 0x00306E4B4AED 0 UP lan0 snap0 1 ETHER Yes 119
1/0/0/1/0 0x00306E4B5A56 4 UP lan4 snap4 2 ETHER Yes 119
1/0/2/1/0 0x00306EF46DC1 5 UP lan5 snap5 3 ETHER Yes 119
0/0/2/1/0 0x00306EF46D5A 1 UP lan1 snap1 4 ETHER Yes 119
1/0/8/1/0 0x00306E4C5E35 6 UP lan6 snap6 5 ETHER Yes 119
1/0/12/1/0 0x00306EF4F06F 7 UP lan7 snap7 6 ETHER Yes 119
1/0/14/1/0 0x00306EF4F091 8 UP lan8 snap8 7 ETHER Yes 119
0/0/12/1/0 0x00306EF4F08D 2 UP lan2 snap2 8 ETHER Yes 119
0/0/14/1/0 0x00306EF4F097 3 UP lan3 snap3 9 ETHER Yes 119
Combining this information, we see that virtual networking is needed for lan1 (vpolyd02), lan4
(vpolyd05), and lan5 (vpolyd06). So, virtual switches for each of these is created and started on the
VM Host, using the LAN number as part of the naming convention:
# hpvmnet -c -S vsw1 -n 1
# hpvmnet -c -S vsw4 -n 4
# hpvmnet -c -S vsw5 -n 5
# hpvmnet -b -S vsw1
# hpvmnet -b -S vsw4
# hpvmnet -b -S vsw5
Finally, verify that all the virtual switches are ready:
# hpvmnet
Name Number State Mode PPA MAC Address IP Address
======== ====== ======= ========= ====== ============== ===============
localnet 1 Up Shared N/A N/A
vsw1 2 Up Shared lan1 0x00306ef46d5a
vsw4 3 Up Shared lan4 0x00306e4b5a56
vsw5 4 Up Shared lan5 0x00306ef46dc1
Each of these may now be used as virtual switches in defining the virtual machines vpolyd02,
vpolyd05, and vpolyd06.