Migrating your Virtual IO server to VIO 2.1
1. Prepare for migration:
The key prerequisites to perform the migration are:
? The system must be managed by HMC version 7 or later
? The virtual IO server must be at least at version 1.3.
? The physical volume for rootvg must be assigned to the VIO
? Double check that you have the Migration DVD for VIOS and not the
Installation DVD for VIOS. (The media for Migration and Installation are
different and using the install media will overwrite your current VIOS
Prior to any update or migration process, it is strongly recommended to backup the VIO server
and check your disaster/recovery process.
Note: It may be useful to record the precise location of the rootvg disks of the VIOS you want to
migrate. Before stopping your Virtual I/O Server for migration, you can run the following
commands from padmin:
$ lsvg -pv rootvg
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 319 11 00..00..00..00..11
hdisk1 active 319 27 00..00..00..00..27
$ lsdev -dev hdisk0 -vpd
MPIO Other FC SCSI Disk Drive
$ lsdev -dev hdisk1 -vpd
MPIO Other FC SCSI Disk Drive
In our example both disks are Fiber Attached disks, that’s why we have the slot number,
worldwide name of the fiber channel adapter and the LUN id of the disks. From the migration
menu you should be able to have some of this information.
This step is not required for the migration to succeed, the migration menu should be able to find
the good VIOS rootvg disk to migrate, but in certain configurations it may be needed to check we
are about to migrate the right disk or manually select it.
2. What happens during migration?
The purpose of migration is to change the VIOS software to the most recent and attempt to
preserve your configuration files.
The migration process saves configuration files, install the new software on your system and then
restore your configuration files. At the end of the migration process, you should be able to find
most of your configuration files.
In a single VIO server configuration, during the migration, the client partition needs to be
shutdown. Once the migration is complete and the VIO has been restarted, the client partition
can be brought up without any further configuration. In a dual VIO server environment, you can
update one VIO server at a time as to avoid any interruption of service to the clients. The client
partition can be up and running through the migration process of each of the VIO servers.
3. How to migrate?
Before you start double-check that the following statements are true:
? The managed system‟s HMC is attached to the system, and both the managed
system and HMC are working properly.
? A DVD optical device is allocated to the VIOS partition, if not, perform a DLPAR
operation or modify the partition profile, to do so.
? The VIOS Migration media is inserted in your optical device.
? If you don‟t have a recent backup, run backupios command and keep the output
file in a safe location.
? Note the location of the rootvg disks
Before shutting down the VIO server you want to migrate, we would recommend to check the
? In a dual VIOS environment, check that the alternate VIOS is up and running, and
is serving I/O to client. (SEA failover, virtual SCSI mapping, and so on…)
? In case of LVM mirroring on clients, check that both disks of any mirrored
volume group are available in the system and the mirroring is properly
If any of the following steps in the process of migration fails, please contact your Support Service
Representative for further help and debugging.
1. Activate the VIOS partition in SMS mode :
a. Insert the Virtual I/O Server migration DVD in the optical device allocated to VIOS
b. From the HMC GUI, select your VIOS partition.
c. Click on Tasks ? Operations ? Activate.
d. Select the proper profile from the popup window that appears. (Profile with rootvg disk
from the VIOS and DVD optical device allocated.)
e. Select “Open a terminal window or console session” to have the console during the
boot and migration process.
f. Click on Advance button, and select “SMS” as boot mode.
g. Click OK twice (one to validate the SMS boot and the other boot the partition).
Figure1: Activation menu from the HMC GUI.
Left Figure 2. HMC Popup window for advanced boot option.
Right Figure3: HMC popup window for boot option.
At this step a Java window is opened and gives you the console. The partition will go through all
standard hardware checking and continue its boot process until reaching the SMS menu.
2. Select the boot device from SMS menu
a. Type the “Select Boot Option” number and press enter.
b. Type the “Select the Install/Boot device” number and press enter.
c. Type the number of the DVD device and press enter. You can also use the “List all
devices” function, but in case you have many devices attached (such as Ethernet adapter,
fiber channel adapter and/or disks…) this function might take long time to scan all those
d. Select the “Normal mode boot”, press enter and validate all your choices by selecting
“Yes” and press enter.
Top left figure 4: Root of the SMS menu. (step a.)
Middle figure 5: Root of the boot/install menu from the SMS. (step b)
Low right figure 6: Boot type selection menu (step d)
The boot process on the DVD will start, and you should be able to follow the different stages of
boot by observing the LED code on the operator panel of the partition from the HMC GUI, until
the system prompts you for the next migration step:
3. Migrate the VIO server
a. Select the desired console.
b. Select the language you want during the installation.
c. Double check that you are facing the “Migration menu” and NOT the “Install menu”.
(See the screen copy below)
Note: Be aware that if you install the VIOS instead of migrating it, you will be unable
to recover your configuration and you’ll have to restore or reconfigure your entire
d. Select “Continue with Install” to start the install process.
Figure 7: Installation Menu
From the first menu of the installation there‟s no indication of the installation type. We can not
confirm if we are migrating our VIO server or just installing it. But at this step our current VIO
installation is still safe.
Figure 8: Installation Menu after selecting option 2 in Figure 7
On this screen, we can see that we have booted our system from the VIOS Migration
Media. If you selected the option 2 on the previous screen, and you don’t have a menu
similar to the one above, you should stop the migration process at once. Check you have
inserted the appropriate media into the Optical Device, and also you have allocated the
correct slot to your VIO server partition.
Figure 9. Here we can see that our VIO server is reported as an AIX 5.3
system. This is correct, but note that other disks, not part of VIOS rootvg,
can also have AIX 5.3 installed on.
The two firsts disks are SCSI internal disks usually used to install VIOS, Figure 9: Installation Menu to choose the disks hdisk12 is another VIOS installation on SAN Lun.
Note: Those disks are not the same than those one specified on page
If you select option 1, it shows you all the system already installed on your partition‟s disks. On
this screen you should check the location code of your VIO‟s disks. (If you mapped disks to
client partition and a rootvg is installed on this disk, it could appear in this menu and being
overwritten by the migration process if selected.)
Figures 9 and 10: Installation Menu to choose the disks and confirm Migration
This is the last screen before the migration really starts, so this is our last chance to avoid the
currently installed VIOS to be overwritten.
From this menu you can check what will be changed and/or removed from your configuration.
All your SCSI mappings and network configuration should be available after migration, but if
you installed third party application or made special configuration to your VIO you should
probably check here if those modifications will be preserved or not.
Figure 10: Beginning of Migration process
Figure 11.After validating the previous screen, you will see the migration starting and initializing saving your configuration.
4. Checking Migration and some debug help:
At the end of the Migration you will be prompted to accept the license, and eventually install other software. Then you can exit and connect to the system using “padmin” user.
Check that your previous configuration has been properly restored by the migration process. $ ioslevel
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9113.550.10BE8DD-V1-C11 0x00000003
Backing device lpar1_rootvg
Name Mtu Network Address ZoneID Ipkts Ierrs Opkts Oerrs Coll
en2 1500 link#2 a6.24.d0.0.10.3 27642 0 8402 0 0
en2 1500 9.3.131 zlab081 27642 0 8402 0 0
lo0 16896 link#1 1197 0 1201 0 0
lo0 16896 127 localhost 1197 0 1201 0 0
lo0 16896 ::1 0 1197 0 1201 0 0
If this is not the case, and you‟re back to another configuration or a fresh install configuration,
check your VIOS is booted on the correct hdisk, check the media used was the one for migration.
5. Migrate your VIO Server using NIM:
First of all we need to create the appropriate resources for migration.
There are two methods to create the appropriate resources and start NIM migration:
5.1. Method one:
The installios command is the preferred method for creating NIM resources for VIOS migration.
If you wish to manually create an lpp_source without using the installios command, you must use the procedure provided below. The following steps will create a valid VIOS Migration lpp_source + spot and initiate a VIOS migration:
a. Use the gencopy command to copy ALL of the install images from the VIOS Migration
DVD to the desired filesystem location on the NIM master. This operation will require
approximately 3GB of free space on the target filesystem and will take several minutes to
# gencopy -d /dev/cd0 -t /export/lpp_source/vios_migration_lpp all
b. When the gencopy command completes successfully use NIM to define an lpp_source,
specifying the above directory as the 'location' attribute. The following command uses the NIM
master to serve the lpp_source:
# nim -o define -t lpp_source -a location=/export/lpp_source/vios_migration_lpp -a
c. At this point you will have defined a valid NIM VIOS Migration lpp_source named
'vios_migration_lpp'. When creating a NIM SPOT resource to be used for the VIOS migration
operation you can choose to specify either this lpp_source or the VIOS Migration DVD as a
# nim -o define -t spot -a location=/export/spot -a server=master -a source=vios_migration_lpp
# nim -o define -t spot -a location=/export/spot -a server=master -a source=/dev/cd0
d. The VIOS migration can now be initiated by issuing a 'bos_inst' operation from NIM,
specifying the lpp_source and spot created in steps 2 and 3:
# nim -o bos_inst -a spot=vios_migration_spot -a lpp_source=vios_migration_lpp ...
object name of VIOS machine>
The bos_inst operation will default to migration, provided that the existing rootvg on the target
system contains VIOS from a prior release. Keep in mind that the VIOS migration will fail if
VIOS is already at the version that you are attemping to migrate to.
5.2. Method two:
To create the lpp_source, insert the VIO 2.1 Migration media in the optical device allocated to
your NIM master
Using smitty :
# smitty nim_mkres
? Select resource type : lpp_source
? Enter the name you want for your resource.
? Enter the resource name for Server of Resource (usually “master”)
? Enter the fully qualified path to your lpp_source in “Location of Resource”
? Select cdX as “Source of Install Images”
? Enter “all” for “Names of Option Packages”
Note: . Using the VIOS Migration DVD as a source will not produce a valid lpp_source
that can be used for migrating a VIOS system, if you do not enter “all” for “Names of
When your lpp_source is created you can check the simages attribute is “yes” with “lsnim –l
a. Create the spot.
- Using smitty :
# smitty nim_mkres
? Select resource type: spot
? Enter the name you want for your spot resource
? Enter the resource for Server of Resource (usually “master”) ? Enter the fully qualified path to your spot in “Location of Resource”
? Select the lpp_source you previously created as “Source of Install Images”
b. Create the resource for your VIO.
- Check the name resolution and routing are good to access your VIOS from the NIM
master. (Use „host‟, „traceroute‟… command) - Using smitty :
# smitty nim_mkmac
? Enter the hostname of the VIOS, if network is properly configured, this should fill up the
other required information (related to network configuration, such as NIM network and
Host Name) with appropriate value.
? Machine Type is Standalone
? Hardware Platform Type is chrp
? Kernel to use for Network Boot is “64” (due to AIX 6.1 only support 64bits kernel)
? Cable Type: usually tp
c. Prepare the NIM master for installation.
Now, all the required NIM resources are ready to use, we can process to installation itself.
- Using smitty :
# smitty nim_bosinst
? Select the client we previously defined. (Our VIOS)
? Select Installation Type: “rte - Install from installation images” ? Select the lpp_source we previously created
? Select the spot we previously created.
? Set “ACCEPT new license agreements?” to yes ? Set “Initiate reboot and installation now?” to no
d. Migrate the VIOS
Follow the procedure described under section 3.1 to restart your VIOS partition in SMS mode.
From the SMS menu on the console, follow this procedure:
Note that depending on your hardware platform and the firmware release of your system the
menu can be slightly different.
- Select “Setup Remote IPL (Initial Program Load)” - Select the appropriate adapter to boot on. (For VIO it should be a physical adapter
unless your nim master is in the same CEC and on dedicated virtual network)
- Select “IP parameters” and check the configuration is good to access the nim master.