IBM Virtual I/O Server support for Power Systems

Contents

This Readme contains installation and other information about VIOS Update Release 2.2.4.60

• Package information
• Installation information
  • Pre-installation information and instructions
  • Installing the Update Release
  • Post-installation information and instructions
• Additional information
• Fixes included in this release

PACKAGE: Update Release 2.2.4.60
IOSLEVEL: 2.2.4.60

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.

If you are looking for a specific APAR number or fix, please check the list of fixes included in Update Release 2.2.4.60.

To take full advantage of all the functions 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.4.60. You may check the firmware versions using the "Fix Level Recommendation Tool" (FLRT).

Microcode or system firmware downloads for Power Systems

The VIOS Update Release 2.2.4.60 includes the IVM code, but it will not be enabled on HMC-managed systems. Update Release 2.2.4.60, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.

Update Release 2.2.4.60 updates your VIOS partition to ioslevel 2.2.4.60. To determine if Update Release 2.2.4.60 is already installed, run the following command from the VIOS command line:

$ ioslevel

If Update Release 2.2.4.60 is installed, the command output is 2.2.4.60.

New Feature Information

Non-Volatile Memory express enhancements

Support for Non-Volatile Memory express (NVMe) adapters. NVMe is an industry specification for accessing non-volatile storage via the PCI express (PCIe) interface. Remote management of NVMe from the Hardware Management Console (HMC)is in toleration mode. User may not be able to manage virtual storage from HMC for NVMe based volume group. But it is fully supported from the VIOS command line interface (ioscli), which is the default padmin shell. Full support for HMC management for NMVe is in VIOS 2.2.6 and onwards with a future version of HMC.

VIOS NVMe devices can be used in the following ways:

• As a VIOS boot device.
• As a way to create volume groups, and to create logical volumes. These logical volumes can be assigned as virtual Small Computer System Interface (vSCSI) devices for client partitions.
• For SSP disk caching. For more information about SSP disk caching, see https://www.ibm.com/support/knowledgecenter/POWER9/p9hbl_vios_ssp_flash_accl.htm.

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.4.60. 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.

Note that with this Update Release 2.2.4.60, 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.4.60, as well as the contents of the 2.2.4.10 release.

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.4.60 may be applied directly to VIOS level between 2.2.4.0 and 2.2.4.10.

On a VIOS level between 2.2.1.1 and 2.2.3.x, a Single Step update procedure can be used to update to level 2.2.4.60.

Instructions: Single step update

To update to Update Release 2.2.4.60 from a level between 2.2.1.1 and 2.2.3.x in a single step, put the 2.2.4.10 updates in the same location as your 2.2.4.60 updates and do the update using the updateios command.

Before installing the VIOS Update Release 2.2.4.60

Warning: The update may fail if there is a loaded media repository.

Instructions: Checking for a loaded media repository

Instructions: Migrate Shared Storage Pool Configuration

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.

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.3.x

Version specific warning: Version 2.2.2.1, 2.2.2.2, 2.2.2.3, or 2.2.3.1

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.

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

Post-installation information and instructions

Instructions: Checking for an incomplete installation caused by a loaded media repository

Instructions: Recovering from an incomplete installation caused by a loaded media repository

For additional details, including known capabilities, limitations, and additional install considerations, as well as some additional instructions, please reference the Readme for 2.2.4.10 located here.

This version will include all fixes found in all previous 2.2.4.X releases. The fixes for the previous release can be found here.