Fix Readme
Abstract
Downloads for Workload Partition Manager for AIX
Content
IBM PowerVM Virtual I/O Server
Tab navigation
- Installation instructions- selected tab,
- Documentation
Tab navigation
Anchor link navigation
Support for PowerVM Virtual I/O Server is moving.
This site will be sunset on May 31, 2011 . Fixes and updates for VIOS have already moved to Fix Central. The IBM Support Portal will be your new starting point to find both support information as well as download support for VIOS.
Overview
If you are planning to update a version of VIOS lower than 2.1.0, you must first migrate your VIOS to VIOS version 2.1.0 using the Migration DVD. After the VIOS is at version 2.1.0, the Fix Pack can be applied to bring the VIOS to the latest level.
While the above process is the most straightforward for most users, you should note that with this Fix Pack version, a single boot alternative to this two-step process is available to NIM users. NIM users can create a single, merged lpp_source by combining the contents of the Migration DVD with the contents of this Fix Pack update.
A single, merged lpp_source is not supported for VIOS that use SDDPCM. However, if you use SDDPCM, you can still enable a single boot update by using the alternate method described at the following location:
http://www-01.ibm.com/support/docview.wss?uid=ssg1S7002686
Important Notices
When upgrading to VIOS 2.2.0.10-FP-24
- Fix Pack 24 enables Role Based Access Control (RBAC) roles and authorizations for the padmin user on the VIOS. Roles and authorizations are enabled immediately. If you upgrade to VIOS 2.2.0.10-FP-24 via the updateios command, the only two commands that you can run before the VIOS is rebooted are the shutdown and swrole commands. In some instances you will need to run the swrole - PAdmin command before you can reboot. See the following installation instructions.
- Fix Pack 24 (VIOS 2.2.0.10-FP-24) adds new features and capabilities to the VIOS. As a result of these additions, VIOS now requires a minimum space of 30GB in the rootvg volume group. Please ensure that your rootvg contains at least 30GB of available space before you attempt to install or upgrade to Fix Pack 24.
- If you use the IEEE 802.3ad link aggregation features provided by the VIOS, then before you install Fix Pack 24, please confirm that your switch is configured in LACP mode. Using link aggregation with a misconfigured switch may lead to loss of network connectivity after you install Fix Pack 24.
General installation note
If you see the following message during the installation of Fix Pack 24, please ignore it.
***************************************************************************
MISSING REQUISITES: The following filesets are required by one or more
of the selected filesets listed above. They are not currently installed
and could not be found on the installation media.
Java5.source 5.0.0.0 # Base Level Fileset
devices.pciex.e4143a16e4143009.rte 6.1.0.0 # Base Level Fileset
***************************************************************************
These filesets are not required on the VIOS.
NIM installation notes
Using NIM to back up and install the VIOS is supported as follows.
- Always create the SPOT resource directly from the VIOS mksysb image. Do NOT update the SPOT from an LPP_SOURCE.
- Do NOT use NIM to apply VIOS updates. Only the updateios command should be used to update the VIOS.
- To use NIM, ensure that the NIM Master is at the appropriate level to support the VIOS image. Refer to the following table.
| VIOS level is | NIM Master level must be equal to or higher than |
|---|---|
| Fix Pack 24 (VIOS 2.2.0.10-FP-24) |
AIX 6100-06-01-1043 |
| Service Pack 01 for Fix Pack 24 (VIOS 2.2.0.11-FP24-SP01) |
AIX 6100-06-03-1048 |
Applying updates from a local hard disk
To apply the updates from a directory on your local hard disk, follow these steps.
The current level of the VIOS must be 2.1.0 or higher
- Log in to the VIOS as the user padmin.
- If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here..
- Create a directory on the Virtual I/O Server.
$ mkdir <directory_name> - Using ftp, transfer the update file(s) to the directory you created.
- Commit previous updates by running the updateios command
$ updateios -commit - Apply the update by running the updateios command
$ updateios -accept -install -dev <directory_name> - If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 8 if you are upgrading from a prior level of the VIOS):
$ swrole - PAdmin - To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart - After the VIOS has rebooted, you are required to accept the license.
$ license -accept - Verify that the update was successful by checking the results of the updateios command and by running the ioslevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.
$ioslevel
Applying updates from a remotely mounted file system
If the remote file system is to be mounted read-only, follow one of these steps.
The current level of the VIOS must be 2.1.0 or higher
- Log in to the VIOS as the user padmin.
- If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here..
- Mount the remote directory onto the Virtual I/O Server.
$ mount remote_machine_name:directory /mnt - Commit previous updates, by running the updateios command
$ updateios -commit - Apply the update by running the updateios command
$ updateios -accept -install -dev /mnt - If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 7 if you are upgrading from a prior level of the VIOS):
$ swrole - PAdmin - To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart - After the VIOS has rebooted, you are required to accept the license.
$ license -accept - Verify that the update was successful by checking the results of the updateios command and by running the ioslevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.
$ioslevel
Applying updates from the CD/DVD drive
This fix pack can be burned onto a CD by using the ISO image file(s). After the CD has been created, follow these steps.
The current level of the VIOS must be 2.1.0 or higher
- Log in to the VIOS as the user padmin
- If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here.
- Place the CD-ROM into the drive assigned to VIOS
- Commit previous updates, by running the updateios command
$ updateios -commit - Apply the update by running the following updateios command:
$ updateios -accept -install -dev /dev/cdX
where X is the device number 0-N assigned to VIOS - If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 7 if you are upgrading from a prior level of the VIOS):
$ swrole - PAdmin - To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart - After the VIOS has rebooted, you are required to accept the license.
$ license -accept - Verify that the update was successful by checking the results of the updateios command and by running the ioslevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.
$ioslevel
Refer to the Virtual I/O Server online publications for additional information on the updateios, ioslevel and mount commands. Information on these commands can be obtained from the IBM Systems Hardware Information Center
Was this topic helpful?
Document Information
Modified date:
19 February 2022
UID
hpc1vios-d220f2f