Fix Readme
Abstract
Downloads for Workload Partition Manager for AIX
Content
IBM PowerVM Virtual I/O Server
Contents
This Readme contains installation and other information about VIOS Update Release 2.2.6.23
Package information
PACKAGE: Update Release 2.2.6.23
IOSLEVEL: 2.2.6.23
| VIOS level is | NIM Master level must be equal to or higher than |
|---|---|
| Update Release 2.2.6.23 | AIX 6100-09-11 or AIX 7100-05-02 or AIX 7200-02-02 |
In June 2015, VIOS introduced the minipack as a new service stream delivery vehicle, as well as a change to the VIOS fix level numbering scheme. Please refer to the VIOS Maintenance Strategy here for more details regarding the change to the VIOS release numbering scheme.
General package notes
Be sure to heed all minimum space requirements before installing.
Review the list of fixes included in Update Release 2.2.6.23.
To take full advantage of all the function available in the VIOS, it may be necessary to be at the latest system firmware level. If a system firmware update is necessary, it is recommended that the firmware be updated before you update the VIOS to Update Release 2.2.6.23.
Microcode or system firmware downloads for Power Systems
The VIOS Update Release 2.2.6.23 includes the IVM code, but it will not be enabled on HMC-managed systems. Update Release 2.2.6.23, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
Update Release 2.2.6.23 updates your VIOS partition to ioslevel 2.2.6.23. To determine if Update Release 2.2.6.23 is already installed, run the following command from the VIOS command line:
$ ioslevel
If Update Release 2.2.6.23 is installed, the command output is 2.2.6.23.
Installation information
Pre-installation information and instructions
Please ensure that your rootvg contains at least 30GB and that there is at least 4GB free space before you attempt to update to Update Release 2.2.6.23. Run the lsvg rootvg command, and then ensure there is enough free space.
Example:
$ lsvg rootvg VOLUME GROUP: rootvg VG IDENTIFIER: 00f6004600004c000000014306a3db3d VG STATE: active PP SIZE: 64 megabyte(s) VG PERMISSION: read/write TOTAL PPs: 511 (32704 megabytes) MAX LVs: 256 FREE PPs: 64 (4096 megabytes) LVs: 14 USED PPs: 447 (28608 megabytes) OPEN LVs: 12 QUORUM: 2 (Enabled) TOTAL PVs: 1 VG DESCRIPTORS: 2 STALE PVs: 0 STALE PPs: 0 ACTIVE PVs: 1 AUTO ON: yes MAX PPs per VG: 32512 MAX PPs per PV: 1016 MAX PVs: 32 LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no HOT SPARE: no BB POLICY: relocatable PV RESTRICTION: none INFINITE RETRY: no
Upgrading from VIOS version lower than 2.1.0
If you are planning to update a version of VIOS lower than 2.1, 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 Update/Fixpack 2.2.6.10 must be applied to bring the VIOS to the latest Fix Pack VIOS 2.2.6.10 level. The Update Release 2.2.6.23 can then be applied to bring the VIOS to the latest level.
Note that with this Update Release 2.2.6.23, a single boot alternative to this multiple step process is available to NIM users. NIM users can update by creating a single, merged lpp_source that combines the contents of the Migration DVD with the contents of this Update Release 2.2.6.23.
A single, merged lpp_source is not supported for VIOS that uses SDDPCM. However, if you use SDDPCM, you can still enable a single boot update by using the alternate method described at the following location:
SDD and SDDPCM migration procedures when migrating VIOS from version 1.x to version 2.x
After the VIOS migration is complete, from 1.X to 2.X, you must set the Processor Folding, described here under "Migration DVD":
Instructions to disable Processor Folding are detailed at the link below.
See the "Migration DVD" section:
Virtual I/O Server support for Power Systems
Upgrading from VIOS version 2.1.0 and above
VIOS Update Release 2.2.6.23 may be applied directly to any VIOS that is either level 2.2.6.0 or 2.2.6.10.
On a VIOS with a level between 2.2.1.1 and 2.2.5.x, a Single Step update procedure can be used to update to level 2.2.6.23.
Instructions: Single Step Update
To update to Update Release 2.2.6.23 from a level between 2.2.1.1 and 2.2.5.x, a single step, put the 2.2.6.21 updates in the same location as your 2.2.6.23 updates and do the update using the updateios command.
Before installing the VIOS Update Release 2.2.6.23
Warning: The update may fail if there is a loaded media repository.
Instructions: Checking for a loaded media repository
To check for a loaded media repository, and then unload it, follow these steps.
- To check for loaded images, run the following command:
$ lsvopt
The Media column lists any loaded media. - To unload media images, run the following commands on all Virtual Target Devices that have loaded images.
$ unloadopt -vtd <file-backed_virtual_optical_device >
- To verify that all media are unloaded, run the following command again.
$ lsvopt
The command output should show No Media for all VTDs.
Instructions: Migrate Shared Storage Pool Configuration
The Virtual I/O Server (VIOS) Version 2.2.2.1 or later, supports rolling updates for SSP clusters. The VIOS can be updated to Update Release 2.2.6.23 using rolling updates.
Version specific instructions: Version 2.2.1.3 or earlier.
A cluster that is created and configured on a VIOS Version at 2.2.1.3 or earlier must be migrated to version 2.2.1.4 or 2.2.1.5 prior to utilizing rolling updates. This allows the user to keep their shared storage pool devices.
Version specific instructions: Version 2.2.1.4 or later.
The rolling updates enhancement allows the user to apply Update Release 2.2.6.23 to the VIOS logical partitions in the cluster individually without causing an outage in the entire cluster. The updated VIOS logical partitions cannot use the new SSP capabilities until all VIOS logical partitions in the cluster are updated.
To upgrade the VIOS logical partitions to use the new SSP capabilities, ensure that the following conditions are met:
- All VIOS logical partitions must have VIOS Update Release version 2.2.1.4 or later installed.
- All VIOS logical partitions must be running. If any VIOS logical partition in the cluster is not running, the cluster cannot be upgraded to use the new SSP capabilities.
Instructions: Verify the cluster is running at the same level as your node.
- Run the following command:
$ cluster -status -verbose
- Check the Node Upgrade Status field, and you should see one of the following terms:
UP_LEVEL: This means that the software level of the logical partition is higher than the software level the cluster is running at.
ON_LEVEL: This means the software level of the logical partition and the cluster are the same.
Installing the Update Release
There is now a method to verify the VIOS update files before installation. This process requires access to openssl by the 'padmin' User, which can be accomplished by creating a link.
Instructions: Verifying VIOS update files.
To verify the VIOS update files, follow these steps:
- $ oem_setup_env
- Create a link to openssl
# ln -s /usr/bin/openssl /usr/ios/utils/openssl - Verify the link to openssl was created
# ls -alL /usr/bin/openssl /usr/ios/utils/openssl - Verify that both files display similar owner and size
- # exit
Use one of the following methods to install the latest VIOS Service Release. As with all maintenance, you should create a VIOS backup before making changes.
If you are running a Shared Storage Pool configuration, you must follow the steps in Migrate Shared Storage Pool Configuration.
Note : While running 'updateios' in the following steps, you may see accessauth messages, but these messages can safely be ignored.
Version specific warning: Versions between 2.2.1.1 and 2.2.5.x
You must put the 2.2.6.10 and 2.2.6.23 on the same location to apply updates in single step. The single step approach fixes an update problem with the builddate on bos.alt_disk_install.boot_images fileset.
Version specific warning: Version 2.2.2.1, 2.2.2.2, 2.2.2.3, or 2.2.3.1
You must run updateios command twice to get bos.alt_disk_install.boot_images fileset update problem fixed.
Run the following command after the step of "$ updateios –accept –install –dev <directory_name >" completes.
$ updateios –accept –dev <directory_name >
Depending on the VIOs level, one or more of the LPPs below may be reported as "Missing Requisites", and they may be ignored.
MISSING REQUISITES:
X11.loc.fr_FR.base.lib 4.3.0.0 # Base Level Fileset
bos.INed 6.1.6.0 # Base Level Fileset
bos.loc.pc.Ja_JP 6.1.0.0 # Base Level Fileset
bos.loc.utf.EN_US 6.1.0.0 # Base Level Fileset
bos.mls.rte 6.1.x.x # Base Level Fileset
Warning: If VIOS rules have been deployed:
When the VIOS is the updated, some of the current rules may revert to the system defaults. Additionally, those changes may have been applied to the system.
If you notice this issue, the default rules can be re-deployed and captured to current rules by running the commands below.
First, to capture your current system settings, run this command:
$ rules -o deploy -d
$ rules -o capture
Note: This will overwrite any customized rules in the current rules file.
Applying updates
Warning: If the target node to be updated is part of a redundant VIOS pair, the VIOS partner node must be fully operational before beginning to update the target node.
Note: For VIOS nodes that are part of an SSP cluster, the partner node must be shown in 'cluster -status ' output as having a cluster status of OK and a pool status of OK. If the target node is updated before its VIOS partner is fully operational, client LPARs may crash.
Note: The current level of the VIOS must be 2.2.2.1 or later if you use the Share Storage Pool.
Instructions: Applying updates to a VIOS
- 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 Update Release. See details here.
- If you use Shared Storage Pools, then Shared Storage Pool Services must be stopped.
$ clstartstop -stop -n <cluster_name > -m <hostname >
- To apply updates from a directory on your local hard disk, follow the steps:
To apply updates from a remotely mounted file system, and the remote file system is to be mounted read-only, follow the steps:
- Mount the remote directory onto the Virtual I/O Server:
$ mount remote_machine_name:directory /mnt
The update release can be burned onto a CD by using the ISO image file(s). To apply updates from the CD/DVD drive, follow the steps:
- Place the CD-ROM into the drive assigned to VIOS.
- Create a directory on the Virtual I/O Server.
$ mkdir <directory_name > - Using ftp, transfer the update file(s) to the directory you created.
- Mount the remote directory onto the Virtual I/O Server:
- Commit previous updates by running the updateios command
$ updateios -commit
- Verify the updates files that were copied. This step can only be performed if the link to openssl was created.
$ cp <directory_path >/ck_sum.bff /home/padmin
$ chmod 755 </home/padmin>/ck_sum.bff
$ ck_sum.bff <directory_path >
If there are missing updates or incomplete downloads, an error message is displayed.
- Apply the update by running the updateios command
$ updateios -accept -install -dev <directory_name >
- To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart
Note: If shutdown –restart command failed, run swrole –PAdmin in order for padmin to set authorization and establish access to the shutdown command properly.
- If cluster services were stopped in step 3, restart cluster services.
$ clstartstop -start -n <cluster_name > -m <hostname >
- Verify that the update was successful by checking the results of the updateios command and by running the isolevel command, which should indicate that the ioslevel is now 2.2.6.23.
$ ioslevel
Post-installation information and instructions
Instructions: Checking for an incomplete installation caused by a loaded media repository
After installing an Update Release, you can use this method to determine if you have encountered the problem of a loaded media library.
Check the Media Repository by running this command:
$ lsrep
If the command reports: "Unable to retrieve repository date due to incomplete repository structure," then you have likely encountered this problem during the installation. The media images have not been lost and are still present in the file system of the virtual media library.
Running the lsvopt command should show the media images.
Instructions: Recovering from an incomplete installation caused by a loaded media repository
To recover from this type of installation failure, unload any media repository images, and then reinstall the ios.cli.rte package. Follow these steps:
- Unload any media images
$ unloadopt -vtd <file-backed_virtual_optical_device>
- Reinstall the ios.cli.rte fileset by running the following commands.
To escape the restricted shell:
$ oem_setup_env
To install the failed fileset:
# installp –Or –agX ios.cli.rte –d <device/directory >
To return to the restricted shell:
# exit - Restart the VIOS.
$ shutdown –restart
- Verify that the Media Repository is operational by running this command:
$ lsrep
Additional information
For additional details, including known capabilities, limatations, and additional install considerations, as well as some additional instructions, please reference the Readme for 2.2.6.10 located here.
Fixes included in this release
This version will include all fixes found in all previous 2.2.6.X releases. The fixes for the previous release can be found here.
| APAR | Description |
|---|---|
| IJ02915 | A potential security issue exists |
| IJ03186 | SMALL CHECKSUM OFFLOAD PACKETS SENT VIA SEA HAVE INVALID TCP SUM |
| IJ03872 | VIOS SSP LU -CREATE -THICK FAILURE CAN CAUSE SERVER NODE FAIL |
| IJ04118 | VIOS SSP CONSUMES EXTRA CPU ON 2.2.6 |
| IJ04592 | Snap -a is not collecting vnic data on VIOS |
| IJ04826 | HIT DOUBLE FREE ISSUE WHEN XTTHICHINDIRECT() FAILS |
| IJ05541 | TCP uses largesend with ESP and shouldn't |
| IJ05658 | A potential security issue exists |
| IJ05824 | A potential security issue exists |
| IJ06154 | FC5899 entstat and port open may hang |
| IJ06274 | FC5899 may have TRANSMIT FAILURE and miscompare |
| IJ06378 | Update NVMe data units read/write command health status |
| IJ06415 | Validation of reserved blocks in bMap |
| IJ06554 | NVMe Drive cannot configure, because of unsupported LBA format |
| IJ06632 | Cannot boot client LPARs after VIOS 2.2.6 upgrade on P5/P6. |
| IJ06651 | A potential security issue exists |
| IJ07221 | Remove metadata format support. |
| IJ07318 | deadlock in shientdd device driver |
| IJ07432 | JZPFP37P1 KDB DURING MICROCODE UPDATE |
| IJ07561 | Avoid requesting PCI fundamental reset for SRIOV ports |
Was this topic helpful?
Document Information
Modified date:
19 February 2022
UID
hpc1vios-39887d01