Migrating vPar Systems to Integrity VM

3 of 13
Networking for the VM Host
Any one of the physical network interface cards (NICs) on the Integrity server may be used for the VM
Host’s network configuration, including any of those used by the virtual partitions. Should you select
a NIC that a virtual partition was using, it may be prudent to select the virtual partition with the
lightest network load. This is due to the fact that this physical NIC will probably have to be shared
between the VM Host and the VM replacing that virtual partition.
Take care to identify the subnet and gateway information for the NIC you expect to use for the VM
Host so that the VH Host’s IP is chosen correctly.
Collecting the Systems’ Configuration Details
Before starting the transition, collect the critical configuration information for each virtual partition.
Except where noted, this information should be kept on a system safe and separate from the one
being reconfigured. That is, don’t put the configuration information on a vPar that you’re about to
convert to a VM. The following sections identify what information is to be collected and saved on
each vPar. Some of these may seem like ‘overkill,’ but the more data you have the better off you will
be in the event of a disaster.
Collect the network (LAN) information for each vPar
Identify the LANs, their configurations (if configured), including MAC, IP, subnet mask, gateway,
DNS, domain, and hostname where possible.
For example, suppose we have three virtual partitions that we want to migrate to virtual machines:
vpolyd02, vpolyd05, and vpolyd06. Collect the lanscan information for each of these:
# hostname
vpolyd02
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/2/1/0 0x00306EF46D5A 0 UP lan0 snap0 1 ETHER Yes 119
…
# hostname
vpolyd05
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
1/0/0/1/0 0x00306E4B5A56 0 UP lan0 snap0 1 ETHER Yes 119
…
# hostname
vpolyd06
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
1/0/2/1/0 0x00306EF46DC1 0 UP lan0 snap0 1 ETHER Yes 119
This actually illustrates the power and versatility of virtual partitions – note that each of the virtual
partitions’ LAN specifications has a unique hardware path and MAC address (i.e., Station Address).
Whenever the VM Host is created, these parameters will remain the same as will be illustrated later.