IBM VIOS update from v2.2.6.10 to v2.2.6.32 and then upgrade to v3.1

Please, pay attention: it will be disruptive upgrade if we are using SSP or/and single VIOS configuration!

PowerVM VIOS 3.1 brings new capabilities to the Power System, offers improved security and resiliency, also the third version based on the code base of AIX 7.2 TL3. The PowerVM VIOS 3.1 uses the POWER9 on-chip compression and/or encryption capabilities to provide secure LPM option that encrypts and compresses a LPARs during mobility operations.

The key improvements:

• support for iSCSI (network storage virtualization) for AIX and Linux workloads
• SSP enhancements
• enabled for enhanced I/O scaling
• ready for P9 HW feature exploitation
• storage multi-pathing enhancement
• native compatibility mode for POWER8 and POWER9
• USB flash drive installation

Before upgrade to VIOS 3.1, we should update our current VIOS to version 2.2.6.32. We used the Fix Central portal to download the latest updates for 2.2.6.10. To download the latest VIOS 3.1 ( use Flash Image! ) we should have access to the IBM Entitled Systems Support.

It is the very easiest process: perform VIOS configuration backup, then run the following command:

$ updateios –accept –dev /path_to_updates

Updates will be applied and if already is OK( need to reboot VIOS ) we can commit updates by issuing the following command:

$ updateios -commit

After update to VIOS 2.2.6.32 we are able to use viosupgrade command.

Please,pay attention! When we have updated VIOS to version 2.2.6.32, we was unable to change/show Virtual SCSI devices that are configured to a LPAR ( Virtual Storage menu of LPAP ) in HMC. There were no any logical volumes that were previously assigned to LPAR from Storage Pool. At the time of update we had the following HMC version:

hscroot@hmc-v9:~> lshmc -V
"version= Version: 9
 Release: 1
 Service Pack: 910
HMC Build level 1803052221

So, update of the HMC fixed that issue:

hscroot@hmc-v9:~> lshmc -V
"version= Version: 9
 Release: 1
 Service Pack: 921
HMC Build level 1810262054

Go to major upgrade!

Be careful, because upgrade to VIOS 3.1 is MAJOR upgrade it means viosupgrade command will perform new and complete installation.

At this step we use backupios and viosbr ( again! ) to backup user-defined virtual devices, media library ( yes, we use it ) and creates a backup of the base code, fix packs, custom drivers, and user-defined metadata.

So, use the following command to start upgrade process, where file vios31_mksysb - is the mksysb image retrieved from VIOS 3.1 Flash Image ( use IBM ESS site ), and hdisk3 - is the alternate disk which is being used to install VIOS 3.1 during upgrade process:

viosupgrade -l -i /vios31_mksysb -a hdisk3

Voilà!

$ ioslevel
3.1.0.10
$
$ oem_setup_env
# oslevel -s
7200-03-02-1846
#

P.S.

If everything works fine do not forget to remove old root volume group:

$ lsvg
old_rootvg
rootvg
client_sp
$
$ oem_setup_env
#
# alt_disk_install -X old_rootvg
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the
alt_rootvg_op man page and documentation for more details.
Executing command: /usr/sbin/alt_rootvg_op -X old_rootvg
+-----------------------------------------------------------------------------+
#
$ lsvg
rootvg
client_sp
$
$ bootlist -mode normal -ls
hdisk3 blv=hd5 pathid=0
$ lspv
NAME             PVID                                 VG               STATUS
hdisk0           00c05240fe0fd3b0                     None
hdisk1           00c05240003e1902                     client_sp        active
hdisk2           00c05240e30b762e                     client_sp        active
hdisk3           00c05240003e1b94                     rootvg           active