Readme and Release Notes for Virtual I/O Server 2.2 VIOS 2.2.0.10 FixPack 24 Readme

Readme file for: VIOS 2.2.0.10 FixPack 24
Product/Component Release: 2.2
Update Name: VIOS 2.2.0.10 FixPack 24
Fix ID: VIOS_2.2.0.10-FP24
Publication Date: 11 August 2011
Last modified date: 11 August 2011

Download location

Below is a list of components, platforms, and file names that apply to this Readme file.

Fix Download for Others

Product/Component Name: Platform: Fix:
Virtual I/O Server VIOS 2.1
VIOS_2.2.0.10-FP24

Installation information

Prior to installation

NOTE: Minimum disc space requirement has changed for Fix Pack 24 (VIOS 2.2.0.10-FP-24

Fix Pack 24 (VIOS 2.2.0.10-FP-24) adds new features and capabilities to 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 before you attempt to install or upgrade to Fix Pack 24.

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 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:

Installing

Use one of the following methods to install the latest VIOS Fix Pack.

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

  1. Log in to the VIOS as the user padmin.
  2. 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..
  3. Create a directory on the Virtual I/O Server.
    $ mkdir
  4. Using ftp, transfer the update file(s) to the directory you created.
  5. Commit previous updates by running the updateios command
    $ updateios -commit
  6. Apply the update by running the updateios command
    $ updateios -accept -install -dev
  7. 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
  8. To load all changes, reboot the VIOS as user padmin .
    $ shutdown -restart
  9. After the VIOS has rebooted, you are required to accept the license.
    $ license -accept
  10. 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.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

  1. Log in to the VIOS as the user padmin.
  2. 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..
  3. Mount the remote directory onto the Virtual I/O Server.
    $ mount remote_machine_name:directory /mnt
  4. Commit previous updates, by running the updateios command
    $ updateios -commit
  5. Apply the update by running the updateios command
    $ updateios -accept -install -dev /mnt
  6. 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
  7. To load all changes, reboot the VIOS as user padmin .
    $ shutdown -restart
  8. After the VIOS has rebooted, you are required to accept the license.
    $ license -accept
  9. 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.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

  1. Log in to the VIOS as the user padmin
  2. 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..
  3. Place the CD-ROM into the drive assigned to VIOS
  4. Commit previous updates, by running the updateios command
    $ updateios -commit
  5. 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
  6. 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
  7. To load all changes, reboot the VIOS as user padmin .
    $ shutdown -restart
  8. After the VIOS has rebooted, you are required to accept the license.
    $ license -accept
  9. 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.0.10-FP-24.
    $ioslevel

Before installing the Fix Pack

How to check for a loaded media repository, and then unload it

  1. To check for loaded images, run the following command:
    & lsvopt
    The Media column lists any loaded media.
  2. To unload media images. run the following commands on all VTDs that have loaded images.
    & unloadopt -vtd <file-backed_virtual_optical_device >
  3. To verify that all media are unloaded, run the following command again.
    & lsvopt
    The command output should show No Media for all VTDs.

After installing the Fix Pack

How to check for an incomplete installation caused by a loaded media repository

After installing a fix pack, you can use either one of the following two methods to determine if you have encountered the problem of a loaded media library.

Method 1

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.

Method 2

Check the install.log and look for a failure message like this one:

 ios.cli.rte                 6.1.4.1         USR         APPLY       SUCCESS    
 ios.cli.rte                 6.1.4.1         ROOT        APPLY       FAILED     
 ios.cli.rte                 6.1.4.1         ROOT        CLEANUP     SUCCESS

 Renaming Media Repository Logical Volume:
 VMLibrary_LV --> VMLibrary
 umount: error unmounting /dev/VMLibrary_LV: Device busy

 Media Repository failed to unmount. We cannot continue
 until it can be successfully unmounted. Please address
 and retry.
 update: Failed while executing the ios.cli.rte.post_u script.

 installp: The installation has FAILED for the "root" part 
 of the following filesets:
 ios.cli.rte 6.1.4.1

 installp: Cleaning up software for:
 ios.cli.rte 6.1.4.1

How to recover 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:

  1. Unload any media images
    $ unloadopt -vtd <file-backed_virtual_optical_device>
  2. If you have not yet restarted the VIOS, restart it now. You must restart before you can run the installp command in the next step.
    $ shutdown -restart
  3. Reinstall the ios.cli.rte fileset by running the following commands.
    To escape the restricted shell:
    $ em_setup_env
    To install the failed fileset:
    # installp -Or -agX ios.cli.rte
    To return to the restricted shell:
    # exit
  4. Verify that the Media Repository is operational by running this command:
    $ lsrep

Additional information

NIM installation information

Using NIM to back up and install the VIOS is supported as follows.

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


PACKAGE: Fix Pack 24

IOSLEVEL: 2.2.0.10-FP-24

General package notes

Fix Pack 24 provides updates to Virtual I/O Server (VIOS) 2.2.0 installations. Applying this package will upgrade the VIOS to the latest level, V2.2.0.10-FP-24.

Review the list of fixes included in Fix Pack 24.

To take full advantage of all the function available in the VIOS on IBM Systems based on POWER6 or POWER7 technology, it is 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 upgrade the VIOS to V2.2.0.

There is no migration path from an HMC-managed VIOS to an IVM-managed VIOS. Fix Pack 24 includes the IVM code, but it will not be enabled on HMC-managed systems. Fix Pack 24, like all VIOS fix packs, can be applied to either HMC-managed or IVM-managed VIOS.

Fix Pack 24 updates your VIOS partition to ioslevel V2.2.0.10-FP-24. To determine if Fix Pack 24 is already installed, run the following command from the VIOS command line:

# ioslevel

If Fix Pack 24 is installed, the command output is V2.2.0.10-FP-24

Installing the fix pack

If the above procedure shows that the VIOS Fix Pack 24 is not installed, follow the installation instructions in this Readme to install the Fix Pack.

Note : After you install the Fix Pack, you must reboot the VIOS Server.

List of fixes

Fixes in Fix Pack 24 (VIOS V2.2.0.10 FP-24) include:

For other fixes included in this Fix Pack, refer to the Cumulative fix history for VIOS Version 2.1.

Document change history


Date Description of change




























































Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Virtual I/O Server

Reference #:

00000259

Modified date:

2011-10-31

Translate my page

Machine Translation

Content navigation