Question & Answer
Question
How can I upgrade my PowerVM Virtual I/O Server (VIOS) to a new release?
Answer
VIOS Upgrade Checklist
From 3.1 to 4.1
VIOS updates and upgrades are not the same. For more details, see the Virtual I/O Server (VIOS) Maintenance Strategy.
This document provides a checklist of recommendations to consider in preparation for a VIOS upgrade from version 3.1 to 4.1. A VIOS upgrade is considered a major upgrade as it involves doing a new and fresh installation. Therefore, carefully review the checklist below, as well as miscellaneous information and unsupported upgrade scenarios before performing the upgrade.
There are various methods of upgrading a Virtual I/O Server (VIOS) from version 3.1 to 4.1
Method #1 - Upgrading the VIOS from the HMC (recommended method)
Other Reference: Upgrading Virtual I/O Servers
Method #2 - Use viosupgrade padmin command on the VIOS partition (for non-NIM users)
Method #3 - Use viosupgrade AIX NIM tool (for NIM users)
Method #4 - Use the manual upgrade method, which involves 3 tasks:
1. Manually back up the VIOS metadata by using the viosbr -backup command
2. Install VIOS 3.1 via AIX NIM Server, Flash Storage, or Hardware Management Console (HMC)
3. Restore the VIOS metadata by using the viosbr -restore command
For IBM cross-products compatibility information and VIOS upgrade recommendations for your specific Power System, refer to the Fix Level Recommendation Tool (FLRT) - Power System Recommendations and enter you VIOS environment details.
For storage compatibility questions, contact the storage vendor.
| POWER SYSTEM REQUIREMENT | Complete = X | COMMENTS |
|---|---|---|
Before upgrading your VIOS to version 4, check which versions of VIOS are compatible with your Power System. To determine the VIOS levels supported based on Power System type and model, go to the System Software Maps for PowerVM Virtual I/O Server. | IMPORTANT Ensure the Power System requirement is met before continuing. Not all VIOS versions are supported on Power8. VIOS versions 3.1.4.60+, 4.1.0.40+, and 4.1.1.10+ required Power9 or newer hardware. | |
| VIOS PRE-REQUISITES | Complete = X | COMMENTS |
| 1. If your current VIOS level is 3.1.4.21 or older, update to 3.1.4.30 or higher before upgrading to version 4. | See Supported Virtual I/O Server upgrade levels for Shared Storage Pool (SSP) cluster environment and non-SSP. | |
| 2. If your current VIOS level is 3.1.4.30 or 3.1.4.31, install interim fix for HIPER APAR IJ50326 or update to 3.1.4.40 prior to upgrading the VIOS to prevent padmin login failure after the upgrade. | To obtain the interim fix, go to FLRT HIPER APAR Information for VIOS and enter your current ioslevel. | |
| VIOS REQUIREMENTS | Complete = X | COMMENTS |
1. Obtain VIOS 4.1 installation software to build mksysb needed for the upgrade | How to Obtain Installation Software for PowerVM Virtual I/O Server. (This will require VIOS entitlement verification.) How to build the mksysb file for VIOS 3.1 Migration / Installation | |
2. A spare disk is needed as the viosupgrade process will create a disk clone of the original 3.1 VIOS rootvg | If the current VIOS rootvg is mirrored, it can be temporarily unmirrored to remove the disk from rootvg to be used as the alternate disk to install the available VIOS 4.1 image. See unmirrorios and reducevg commands for more details. To remirror, click here. Related Resource | |
3. If additional software is installed in VIOS 3.1, a custom mksysb image is required with viosupgrade -i option The additional software may include (but it is not limited to):
| To create the custom mksysb:
$ backupios -file filename.mksysb -mksysb This is the image that will need to be used with viosupgrade -i command. | |
4. Use viosupgrade with -g option to restore customized files. viosupgrade tool does a New and Complete installation. Consequently, any customized configurations that might exist on the currently running VIOS before the installation starts (including the time zone), are not included in the new installation image. You must save and backup any customized configurations before running the viosupgrade command and restore them after the installation completes.
| The viosbr backup and restore commands handle only the configurations related to the virtual I/O. The viosupgrade command provides the -g option to save the required configuration files from the currently installed image to the new VIOS image. Related resource: | |
| 5. Determine if there are logical volumes configured in VIOS rootvg and used as backing devices for virtual SCSI disks. | Rootvg LV backed vSCSI disk backup restore not supported. | |
6. If the VIOS is part of a Shared Storage Pool (SSP) cluster, you must use viosupgrade with -c option, e.g. $ viosupgrade -l -i <mksysb image> -a <hdisk> -c | Note 1: To upgrade to VIOS version 4.1, the status of the SSP cluster must be ON_LEVEL for all the nodes. You can verify the status of the cluster by using the command: $ cluster -status -verbose If "Node Upgrade Status" is UP_LEVEL, your cluster nodes (Virtual I/O Servers) are not ready for migration to VIOS version 4.1. Note 2: Supported Virtual I/O Server upgrade levels for Shared Storage Pool (SSP) and non-SSP clusters Note 3: After "Upgrade process is completed successfully", do not boot back from the original 3.1 disk if you encounter any issues. Contact your local IBM SupportLine Representative for investigation. Resources |
RELEVANT RESOURCES
- VIOS 4.1 Overview
- VIOS 4.1 Migration Demystified: Expert Tips and Insights
- VIOS 4.1.1 Release Notes
- How to upgrade to VIOS Version 4.1.0.10 with IBM Storage and non-Shared Storage Pool Environment -
- Upgrading the VIOS from the HMC
- FLRT VIOS HIPER APAR Information
- FLRT VIOS Security APAR Information
- Problem Determination Resources
- Known Issues when upgrading from 3.1.4 to 4.1.0
- known Issues when upgrading to 4.1.1
From 2.2 to 3.1
I need to upgrade my PowerVM Virtual I/O Server (VIOS) to version 3.1 because version 2.2.x reached End of Support.
Following is a checklist of recommendations to consider in order to prepare a VIOS to be upgraded from version 2.2.6.65 to 3.1 using viosupgrade tool.
The upgrade to version 3.1 is considered a major upgrade as it involves doing a new and fresh installation. Therefore, carefully review the checklist below, as well as miscellaneous information and unsupported upgrade scenarios before performing the upgrade.
For cross-product compatibility information and fix recommendations, refer to the Fix Level Recommendation Tool (FLRT) - Power System Recommendations.
There are three methods available for upgrading to version 3.1
- Method #1 - Use viosupgrade tool on the Virtual I/O Server partition (for non-NIM users)
- Method #2 - Use viosupgrade AIX NIM tool (for NIM users)
- Method #3 - Use the manual upgrade method, which involves 3 tasks
- Manually back up the VIOS metadata by using the viosbr -backup command
- Install VIOS 3.1 via AIX NIM Server, Flash Storage, or Hardware Management Console (HMC)
- Restore the VIOS metadata by using the viosbr -restore command
NOTE
viosupgrade tool is included in 2.2.6.30 and above. The enhancement version of this tool available as interim fix at
- viosupgVIO.200807.epkg.Z
- IBM recommends installing this interim fix at 2.2.6.65 before doing the VIOS upgrade.
| SYSTEM REQUIREMENT | Complete = X | COMMENTS |
VIOS version 3.1.3 requires Power8 or later. For more details on VIOS and system compatibility information, refer to the System Software Maps for PowerVM Virtual I/O Server. Ensure Power system requirement is met before proceeding to the VIOS Requirements. | Note 1: VIOS 3.1 is not supported on Power7 and older hardware. Note 2: Only VIOS versions 3.1.0, 3.1.1, and 3.1.2 are supported on Power7+ ("D" models, such as 9117-MMD). For more details about your system type and model, search here for your system sales manual. Note 3: Early versions of VIOS 3.1 have reached End of Service Pack Support (EoSPS). IBM recommends upgrading from 2.2.6.65 to a 3.1 version that is fully supported. See VIOS Lifecycle for details. | |
| VIOS REQUIREMENTS | Complete = X | COMMENTS |
1. VIOS 3.1 installation software (PowerVM VIOS entitlement verification required) | See: | |
| 2. Spare disk(s) needed as the viosupgrade process will create a disk clone of the original 2.2.6 VIOS rootvg. | If the current VIOS rootvg is mirrored, it can be temporarily unmirrored and removed from rootvg to be used for the alternate disk install. See unmirrorios and reducevg commands for more details. To remirror, click here. | |
3. For minimum VIOS 2.2.6 level required, see Recommended upgrade paths to VIOS version 3.1 | MUST READ if your current 2.2.6.X release date is newer than the release date of the 3.1 version you want to upgrade to. | |
4. A custom mksysb image is required with viosupgrade -i option if additional software was installed at 2.2.6. The additional software may include (but it is not limited to):
VIOS Storage Prerequisite Ensure the SAN Storage Mulitpath Software installed at 2.2.6 is supported at the VIOS 3.1.X version that you plan to upgrade to before creating the custom mksysb
| To create the custom mksysb:
$ backupios -file filename.mksysb -mksysb This is the image that will need to be used with viosupgrade command. | |
5. Use viosupgrade with -g option to restore customized files. viosupgrade tool does a New and Complete installation. Consequently, any customized configurations that might exist on the currently running system before the installation starts (including the time zone), are not included in the new installation image. You must save and backup any customized configurations before running the viosupgrade command and restore them after the installation completes.
| The viosbr backup and restore commands handle only the configurations related to the virtual I/O. The viosupgrade command provides the -g option to save the required configuration files from the currently installed image to the new VIOS image. Related resource: | |
6. Determine if there are logical volumes configured in VIOS rootvg and used as backing devices for virtual SCSI disks. | Rootvg LV backed vSCSI disk backup restore not supported. | |
7. If the VIOS is part of a Shared Storage Pool cluster, you must use viosupgrade with -c option. Click here for unsupported scenarios. | Note 1: viosupgrade should not be done if "Node Upgrade Status" is UP_LEVEL $ cluster -status -verbose Note 2: After viosupgrade completes and the VIOS boots from the 3.1 disk, do not boot back from the old 2.2 disk if you encounter any issues. Contact your local IBM SupportLine Representative for investigation. | |
| 8. If the VIOS is not part of a Shared Storage Pool cluster, refer to the Related Resources section below. |
RELEVANT RESOURCES
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m3p000000PCZiAAO","label":"VIOSUPGRADE"}],"ARM Case Number":"TS004042146","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
19 November 2025
UID
ibm16258119