Readme and Release Notes for Virtual I/O Server 2.2 VIOS 2.2.1.1 FixPack 25 Readme

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

Prior to installation

NOTE: Minimum disc space requirement has changed for Release 2.2.0 and beyond.

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 Release 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 Update Release.

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

For a current VIOS configured with a cluster (previously called Shared Storage Pool)

These instructions refer only to migrating a cluster configuration from the version supported in V2.2.0.11 Fix Pack 24, Fix Pack 24 Service Pack 01 or Fix Pack 24 Service Pack 02 to the current version, VIOS 2.2.1.1, by using the VIOS command line.

The cluster that is created and configured on VIOS Version 2.2.0.11 Fix Pack 24, Fix Pack 24 SP 01 or Fix Pack 24 SP 02 can be migrated to VIOS Version 2.2.1.0 or later. This migration allows you to keep your shared storage pool devices. If this procedure is not followed and the cluster is running, the update will fail.

Note: If you choose to destroy the devices supported by the storage pool, you can delete the cluster and skip these steps. However, you will not be able to recover client data, except from existing backups, taken from client partitions.

Follow these steps to migrate your cluster configuration from a VIOS at V2.2.0.11 FP 24, or Fix Pack 24 SP1 or Fix Pack 24 SP2.

1. Close all devices that are mapped to the shared storage pool, which may entail shutting down clients.
2. As user padmin, create a backup of the old version cluster
   $ viosbr -backup -file oldCluster -clustername clusterA
3. Save the generated backup file, oldCluster.clusterA.tar.gz, on different system.
4. List devices and note the storage with the name caa_private0
5. Run chkdev on this device and note the IDENTIFIER
   Example:
   $ chkdev -dev caa_private0
   NAME: caa_private0
   IDENTIFIER: 3E213600A0B80006E4482000095C84DD6746D0F1818 FAStT03IBM fcp
   PHYS2VIRT_CAPABLE: YES
   VIRT2NPIV_CAPABLE: NA
   VIRT2PHYS_CAPABLE: NA
6. List devices and note devices with the prefix cldisk
7. Run chkdev on the devices with this name, and note the IDENTIFIER. These devices have your client data and should not be reallocated after the install.
   Note: The physical volumes used for storagepool, should not be touched. These have a name like cldiskX .
8. Reinstall VIOS system with Version 2.2.1.0 or later.
9. After the installation of VIOS Version 2.2.1.0 is completed, convert the backup file created in Step 1 to the new format. This action generates a migrated backup file, in gz format.
   Example: oldCluster_MIGRATED.clusterA.tar.gz
   $ viosbr -migrate -file oldCluster.clusterA.tar.gz
10. Clean the physical volume that has the matching IDENTIFIER from Step 4. If the device name no longer exists or is in the defined state, you can use the chkdev command to identify the correct physical volume.
    Example:
    $ chkdev -dev hdisk9
    NAME: hdisk9
    IDENTIFIER: 3E213600A0B80006E4482000095C84DD6746D0F1818 FAStT03IBM fcp
    PHYS2VIRT_CAPABLE: YES
    VIRT2NPIV_CAPABLE: NA
    VIRT2PHYS_CAPABLE: NA
11. Run the cleandisk command on the device found from Step 10, in this example hdisk9. Do not run this command on other devices.
    $ cleandisk -r hdisk9
12. Restore the cluster using migrated backup file from Step 9, specifying the physical volume from Step 10, in this example, hdisk9.
    $ viosbr -restore -file oldCluster_MIGRATED.clusterA.tar.gz -clustername clusterA -repopvs hdisk9
    After a successful restore, cluster and all Shared Storage Pool mappings are configured as earlier.
13. To verify that the above cluster restored successfully, list the nodes in the cluster and then list the storage mappings on the VIOS.
    $ cluster -listnode -clustername clusterA
    $ lsmap -all

Installing

Use one of the following methods to install the latest VIOS Update Release.

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 Update Release. 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 Update Release 2.2.1.1 (FP 25) 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.1.1.
    $ioslevel

Back to top

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 Update Release. 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 Update Release 2.2.1.1 (FP 25) 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.1.1.
   $ioslevel

Back to top

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 Update Release. 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 Update Release 2.2.1.1 (FP 25) 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.1.1.
   $ioslevel

Back to top

Before installing the Update Release

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 Update Release

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

The following errors can be ignored during installation; these requisites are note required on the VIOS.

 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.     X11.loc.fr_FR.base.lib 4.3.0.0         # Base Level Fileset     X11.samples.apps.clients 6.1.0.0       # Base Level Fileset     X11.samples.lib.Core 6.1.0.0           # Base Level Fileset     bos.INed 6.1.6.0                       # Base Level Fileset     bos.mls.rte 6.1.7.0                    # Base Level Fileset     bos.mls.rte 6.1.1.0                    # Base Level Fileset     devices.tmiscsw.rte 6.1.0.0            # Base Level Fileset     rsct.exp.cimrm 2.5.4.0                 # Base Level Fileset 

Back to top

NIM installation information

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.

PACKAGE: Update Release 2.2.1.1 (FP 25)

IOSLEVEL: 2.2.1.1

General package notes

Update Release 2.2.1.1 (FP 25) 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.1.1.

Review the list of fixes included in Update Release 2.2.1.1 (FP 25).

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.

Microcode or system firmware downloads for Power Systems

There is no migration path from an HMC-managed VIOS to an IVM-managed VIOS. Update Release 2.2.1.1 (FP 25) includes the IVM code, but it will not be enabled on HMC-managed systems. Update Release 2.2.1.1 (FP 25), like all VIOS fix packs, can be applied to either HMC-managed or IVM-managed VIOS.

Update Release 2.2.1.1 (FP 25) updates your VIOS partition to ioslevel V2.2.1.1. To determine if Update Release 2.2.1.1 (FP 25) is already installed, run the following command from the VIOS command line:

# ioslevel

If Update Release 2.2.1.1 (FP 25) is installed, the command output is V2.2.1.1 .

Installing the fix pack

If the above procedure shows that the VIOS Update Release 2.2.1.1 (FP 25) is not installed, follow the installation instructions in this Readme to install the Fix Pack.

Note : After you install the Update Release, you must reboot the VIOS Server.

Installing the latest version of Tivoli TSM

This release of VIOS contains several enhancements. These enhancements are in the area of POWER virtualization. The following list provides the features of each element by product area.

Note: Version 6.1.0, the previous version of Tivoli TSM, is still shipped and installed from the VIOS installation DVD.

Tivoli TSM version 6.2.2

The Tivoli TSM filesets are now being shipped on the VIOS Expansion Pack, with the required GSKit8 libraries.

The following are sample installation instructions for the new Tivoli TSM filesets:

1. Insert the VIOS Expansion DVD into the DVD drive, that is assigned to the VIOS partition.
2. List Contents of the VIOS Expansion DVD
   $ updateios -list -dev /dev/cd0
   Fileset Name
   GSKit8.gskcrypt32.ppc.rte 8.0.14.7
   GSKit8.gskcrypt64.ppc.rte 8.0.14.7
   GSKit8.gskssl32.ppc.rte 8.0.14.7
   GSKit8.gskssl64.ppc.rte 8.0.14.7
   ..
   tivoli.tsm.client.api.32bit 6.2.2.0 tivoli.tsm.client.api.64bit 6.2.2.0
   ..
3. Install Tivoli TSM filesets
   $ updateios -fs tivoli.tsm.client.api.32bit -dev /dev/cd0
   NOTE: Any prerequisite filesets will be pulled in from Expansion DVD. For TSM, this includes GSKit8.gskcrypt
4. If needed, install additional TSM filesets
   $ updateios -fs tivoli.tsm.client.ba.32bit -dev /dev/cd0
5. Verify TSM installed by listing software installed.
   $ lssw
   Sample output:
   ..
   tivoli.tsm.client.api.32bit 6.2.2.0 C F TSM Client - Application Programming Interface

Back to top

This update release contains fixes for the following:

• Issues with DMA errors with remote device
• Issues with I/O entitlement
• Issues with ethernet device driver
• Issues with installation using USB DVD
• Issues with DASD Expanders and Drawers
• Issue with releasing of stale reserve when running with no_reserve
• Initialization issues in cfgscsidisk method
• Issues with MPIO FC driver
• Issues with disk attributes reverting to defaults after reboot
• Issues with disk operation with PR_Shared set on SAN
• Issue with iocinfo ioctl causing I/O throughput issues to degraded disk
• Issues with system crash during installation from USB optical drive
• Issues with interrupts not reaching the trunk adapter
• Issues with VASI snap support
• Issues with vfcmap failing
• Issues with VFC host driver
• Potential issues with VIOS under heavy NPIV load
• Issues with VHOST driver directing SCSI inquiry to bad path
• Issues with with closing connection during write to DAT320 USB drive
• Issues with shutdown/reboot after fixpack install
• Issues with the cfglnagg command
• Issues with cfgsvc failing to create tunnel
• Issues with updateios command not installing new filesets or ifixes
• Issues with vfcmap command failing
• Iseveral issues with viosbr command
• Issues with viosecure command with -view option
• Issues with virtual ethernet device for LPM
• Issues with chgsea command
• Iseveral issues with SEA driver including creation and deletion of SEA device
• A problem were live partition mobility operations may fail with viosecure

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