Fix Readme
Abstract
VIOS Maintenance Strategy
Content
IBM PowerVM Virtual I/O Server
VIOS release
VIOS releases (TL's) contain product enhancements, new feature / function, new hardware support and fixes. VIOS releases are typically released once per year. A VIOS release is reflected by an increase to the version, release, and/or maintenance level number(s) (See VRMF section).
VIOS service strategy
VIOS follows the standard IBM software lifecycle which provides three years of standard support per release. Extended support may be at an additional cost. Contact your IBM representative for more information.
See the VIOS lifecycle page "PowerVM VIOS Lifecycle Information".
The VIOS service stream has four delivery vehicles: Fix packs, Service packs, Mini packs(New), and Interim Fixes:
Fix pack
A fix pack (FP) updates the VIOS software to the latest level. It contains new feature / function, product enhancements, new hardware enablement, and fixes. It is used to upgrade an existing VIOS to a new VIOS release level while preserving existing customized information. Applying a fix pack to a VIOS will update one or all of the VIOS's version, release, or maintenance level (see VRMF section).
Service pack
Service packs contain fixes and new hardware enablement (Power servers and I/O). Service packs do not typically introduce new feature function.
A service pack (SP) applies to a specific VIOS release level only. For example, a v2.2.6 SP (ie. 2.2.6.20) could only be applied to a v2.2.6 VIOS.
Service packs are cumulative. For example, SP5 for a particular VIOS release (VRM) will contain all fixes and HW enablement that was in SP's 1-4.
Applying a service pack will result in an update to the fix level (last nibble) of the VIOS version, it does not change the VIOS version-release-maintenance level (see VRMF section). For example, applying a SP update to VIOS 2.2.6.10 could result in a VRMF of 2.2.6.20.
Minipack
Minipacks (MP) introduced June 2015
A minipack is a supplement to a service pack. A minipack is very similar to a service pack in that it contains a bundle of fixes (same PTF format), but it is targeted to specific enablement (ie HW, PowerVC, ectc). This enablement would typically be delivered via interim fix in the past. Minipacks are being introduced to provide an improved lifecycle management option in limited cases. Interim fix will continue to be a service delivery vehicle.
A minipack always has a prereq to a specific service pack. For example, MP 2.2.3.51 may be targeted for HW specific enablement. SP 2.2.3.50 is a prereq for MP 2.2.3.51. This relationship can be easily determined by fix level numbering scheme (see the VRMF section).
Minipacks are cumulative only back to the parent service pack. For example, MP 2.2.3.55 for a particular VIOS SP (fix level) will contain all fixes and HW enablement contained in MP's 2.2.3.51 2.2.3.54. SP 50 is a prereq.
Minipacks are intended for specific enablement (ie HW, other solutions). While it is generally recommended to apply SP's for general fixes, MP's are recommended in cases where enablement of a specific solution is needed, otherwise they are optional.
Interim fix
An interim fix (iFix) applies to a specific VIOS service pack (ie. fix level) and provides a fix for a specific issue. The official fixes are typically bundled in the next VIOS service packs and / or fix packs. Applying one or more interim fixes will not alter the VIOS VRMF level.
VRMF
Version-Release-Maintenance-Fix level; describes the level of a VIOS
Update to the VIOS fix level numbering scheme:
There has been a change to the numbering scheme used for the VIOS fix level l (last nibble in the VIOS VRMF). VIOS fix level is associated with service pack level. Before June 2015, the VIOS fix level was always single digits, incremented by 1 for each service pack. Beginning in June 2015:
The fix level for VIOS service packs are always a multiple of 10 (ie. 2.2.3.50, 2.2.3.60, 2.2.3.70)
The fix level for VIOS minipacks will increment by 1's off the associated service pack (ie. 2.2.3.51, 2.2.3.52, etc)
For example, a service pack VRMF could be 2.2.3.50, and the minipacks associated to that service pack could be 2.2.3.51, 2.2.3.52, 2.2.3.53, etc.
Note : applying a VIOS service pack or minipack will always result in a change to the VIOS Fix Level (4th nibble, see VRMF section).
- VIOS release: reflected by an increase to the version, release, and / or maintenance level
For example: v1.5.0, v2.2.3, v2.2.4, v3.1.0 - VIOS service pack: reflected by an increase to the fix level
For example: v2.2.1.7, v2.2.3.4, v2.2.3.50 (new format, see description below) - VIOS minipack: reflected by an increase to the fix level
For example: v2.2.3.51, v2.2.3.52 (new format, see description below) - VIOS interim fix: no change to VIOS VRMF, use emgr for interim fix management
VIOS problem resolution
To ensure the reliability, availability, and serviceability of a computing environment using the Virtual I/O Server, IBM recommends that Virtual I/O Servers are maintained to the recommended fix level for that particular release. That level contains all cumulative fixes for the specified VIOS release. Please refer to FLRT for recommended VIOS levels:
http://www-304.ibm.com/webapp/set2/flrt/liteTable?prodKey=vios
Service pack fix delivery is provided for the VIOS releases that are still under standard support. This is typically the current (designated as n) and the VIOS Release preceding the latest release (n ‐ 1).
See the VIOS lifecycle page "PowerVM VIOS Lifecycle Information".
Was this topic helpful?
Document Information
Modified date:
13 September 2022
UID
hpc1vios-179c37c