Fix Readme
Abstract
xxx
Content
Readme file for: VIOS 2.2.0.12 FixPack 24 SP02
Product/Component Release: 1.0.0.0
Update Name: VIOS 2.2.0.12 FixPack 24 SP 02
Fix ID: VIOS_2.2.0.12-FP24-SP02
Publication Date: May 16 2011
Last modified date: May 16 2011
Contents
Installation information
Download location
Below is a list of components, platforms, and file names that apply to this Readme file.
| Product/Component Name: | Platform: | Fix: |
|---|---|---|
| Virtual I/O Server | VIOS 2.2.0.0 | VIOS_2.2.0.12-FP24-SP02 |
Known issues
Restrictions and limitations
The Service Pack includes the following limitations and restrictions.
Service Pack VIOS 2.2.0.12-FP-24 SP-02 limitations
The reject option of the updateios command is not supported on VIOS 2.2.0.11-FP-24 SP-01 and later.
VIOS Shared Storage Pool requirements and limitations
The following requirements and limitations apply to enhancements to virtual storage, including shared storage pools and thin provisioning. These requirements and limitations do not apply to VIOS classic function.
Requirements for Shared Storage Pools
- Platforms: Power6 and Power7 only (includes Blades)
- System: Minimum CPU: 1; Minimum memory: 4GB per VIOS node
- VIOS Storage (minimums):
- 1 fibre-channel attached disk for repository, 20 GB
- At least 1 fibre-channel attached disk for data, 20GB
- Pool Storage Redundancy: All Storage Devices (repository and pool) must be RAIDed
- A shared storage pool configuration should configure the TCP/IP resolver routine for name resolution to resolve host names locally first, and then use the DNS. For step by step instructions, refer to the TCP/IP name resolution documentation in the AIX Information Center.
Limitations for Shared Storage Pools
- VIOS Software updates must be done while all clients utilizing storage in the VIOS are shut down.
- Shared Storage Pool
- Maximum nodes: 1 VIOS node
- Maximum client LPAR per VIOS : 20
- Maximum physical disks in a pool: 128
- Maximum virtual disks in a cluster: 200
- Maximum number of physical volumes that can be added to a pool at one time: 64.
- Uninterrupted network connectivity is required for operation.
- Changing the hostname for a system is not supported when it is in a shared storage pool.
- IP addresses used for shared storage pool should be the first entry in the /etc/hosts file.
- IPV4 Compliance only
- Client LPARs using Shared Storage Pool virtual devices are not supported for Live LPAR Mobility (LPM).
- VIOS Legacy capabilities that are not supported when a VIOS is configured for Shared Storage Pools.
- VIOS node cannot be a MSP/Data Mover (LPM). The VIOS cannot facilitate a Live Partition Mobility operation.
- VIOS node cannot be a PSP (AMS/Hibernation/Remote restart).
- VIOS node does not support SEA in "Interrupt Mode". Only threaded mode is supported (the default mode).
- VIOS Legacy capabilities that are supported when a VIOS is using Shared Storage Pools:
- VIOS node supports vSCSI Classic
- VIOS node supports NPIV
- VIOS node supports SEA (threaded mode only)
- The default AIX, MPIO-based software is the only supported PCM solution for physical devices in the shared storage pool.
- Logical Units in the SAN Storage subsystem imported into the Shared Storage Pool cannot be resized.
- Release 1 vSCSI devices from the Shared Storage Pool may drive higher CPU utilization than vSCSI classic devices.
- The viosbr command has options to "-backup", "-view" and "-restore" virtual configuration data. The "-clustername" option for the viosbr command is not supported until a future release.
NOTE: The system reserves a small amount of the reported Shared Storage Pool capacity to record consistency records. The remainder of the Shared Storage Pool capacity is available for storage of virtual client partition user data. Shared Storage Pool threshold monitoring should be used to notify the VIOS Administrator when free capacity falls below an acceptable level. The default threshold monitoring is set to alert when the free capacity in the pool is lower than 75% of the total capacity. As a precautionary measure, the VIOS Administrator should not allow the free capacity to drop below 5% of the total capacity or I/O operations on the virtual client partition may fail. In the event that no storage capacity is available, physical volumes must to be added to the pool or data deleted from the pool to create additional free capacity.
Installation information
To install a Service Pack, log in to VIOS as padmin , and then follow these steps, entering the specified commands.
- Check the ioslevel
$ ioslevel
To apply this Service Pack, the ioslevel must be:
2.2.0.10-FP-24 - After the Service Pack has been downloaded, enter the following commands:
$ updateios -commit
$ updateios -install -accept -dev /home/padmin⁄<Service_Pack_directory > - After the update is complete, verify the correct IOS level by entering the following command:
$ ioslevel
2.2.0.12-FP24 SP-02 - To load all changes, reboot the VIOS as User padmin
$ shutdown -restart
OR
2.2.0.11-FP-24 SP-01
Note
If interim fixes are installed on your VIOS, the updateios command prompts you to choose whether or not to remove the interim fixes before it installs the Service Pack. The prompt is a Yes/No (y/n) prompt.
- Answering "Yes" ( y ) causes the updateios command to removed the interim fixes, and then continue with the update.
- Answering "No" ( n ) causes the updateios command to exit without completing the update.
To complete the fix pack update, you must remove the interim fixes before running the updateios command again, or by answering "Yes" ( y ) when the updateios prompts you to let it remove interim fixes.
After the interim fixes have been removed, repeat steps two and three of the installation instructions.
Additional information
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.
| 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 |
General installation note
If you see the following message during the installation of Service Pack 02, please ignore it.
*************************************************************************** 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 <> *************************************************************************** These filesets are not required on the VIOS.
Service Pack description
VIOS 2.2.0.12-FP-24 SP-02 contains fixes and enhancements to VIOS functions. It includes enablement of new function and new hardware, as well as general fixes, as follows:
- Client Partition Suspend and Resume
- Shared Storage Pools
- General updates. See the List of fixes.
Service Pack VIOS 2.2.0.12-FP-24 SP-02 is an optional service pack. Apply it to Fix Pack 24 if you want to take advantage of any of the new functional enhancements. Any critical fixes in the List of fixes may be available via interim fix distribution. See Fix Central for a list of download images.
VIOS 2.2.0.12-FP-24 SP-02 should only be applied to systems that are currently at IOS level 2.2.0.10-FP-24 or 2.2.0.11-FP-24 SP-01. If your IOS level is lower than 2.2.0.10-FP-24, you must install Fix Pack 2.2.0.10-FP-24 before you can install this Service Pack. Installing this Service Pack on any other level may result in unexpected operation of the VIOS or the client partitions hosted by the VIOS.
VIOS Fix Central image management policy
The following images will be available on Fix Central for all supported maintenance levels:
- Fix Pack images for supported maintenance levels
- Service Pack images for the supported maintenance levels
Note: Migration images remain on Fix Central as long as the level to which the image migrates the VIOS is still in service. Images are removed from Fix Central after the VIOS level reaches the End of Service (EOS) date.
VIOS service policy
VIOS is an IBM appliance with unique requirements and service stream. In the unlikely case that an issue emerges that was not addressed in a previous level, customers will be asked to migrate up to a level that captures the appropriate fix or will receive a bundled fix packaged at the latest VIOS code level.
VIOS service strategy
The service strategy for VIOS has changed. In addition to Fix Packs, Service Packs for VIOS will be released, depending on the number of needed changes. VIOS Service Packs consist of critical changes found between Fix Pack releases.
VIOS is an IBM appliance with unique requirements and service stream. In the unlikely case that a new issue emerges that was not addressed in a previous level, customers will be asked to migrate up to a level that captures the appropriate fix or will receive a bundled fix packaged at the latest VIOS code level.
VIOS server problem/resolution
To ensure the reliability, availability, and serviceability of a computing environment using the Virtual I/O Server, IBM recommends that you update the Virtual I/O Server to the latest generally available release, Fix Pack or Service Pack. The latest level contains all cumulative fixes for the VIOS. Interim fixes (iFixes) are only provided at the latest shipped level VIOS. You need to upgrade to the latest service level or Fix Pack to install an interim fix. The official fixes may be shipped in the next Fix Pack or Service Pack of VIOS.
VIOS service package definitions
Fix Pack
A Fix Pack updates your VIOS release to the latest level. A Fix Pack update can contain product enhancements, new function and fixes.
Service Pack
A Service Pack applies to only one (the latest) VIOS level. A Service Pack contains critical fixes for issues found between Fix Pack releases. A Service Pack does not update the VIOS to a new level and it can only be applied to the Fix Pack release for which it is specified.
Interim Fix
An Interim Fix (iFix) applies to only one (the latest) VIOS level and provides a fix for a specific issue.
List of fixes
The Service Pack includes the following fixes and miscellaneous enhancements:
Miscellaneous enhancements
- Added SEA support for SSP
- Added support for 64-bit DMA
- Improved RAS for PCI and VDEV bus
- Added support for recovering AMS paging devices on error
- Added TCE Mirror removal support
- Added support to populate NDD statistics counters
- Improved disk error logging on MPIO path selection failure
- Added SIS SAS RAID arrays support in Storage Framework
- Enabled access to some commands in VIOS via RBAC
- Enabled SAN login from VIOS
- Enhanced SEA failover mechanism
Fixes
- Fixed problems and issues in base Clustering Subsystem
- Fixed problems with creating SSP Logical Units
- Fixed issues with SSP database connection
- Fixed client LPAR hang issues in SSP environment
- Fixed problems in Distributed Filesystem Subsystem
- Fixed EtherChannel for IEEE 802.3ad mode
- Fixed an unnecessary failover in ethernet driver with lossless failover enabled
- Fixed issues with mkvdev ?lnagg
- Fixed RDMA issues with ethernet driver
- Fixed problems in Storage Framework Driver
- Fixed issues with server node hang under stress
- Fixed a potential crash problem after disk reserve policy change
- Fixed a problem with failing over to alternate path after ASCQ 9401
- Fixed I/O hang due to oversubscibed LUN
- Fixed a problem with changing MAX_XFER_SIZE on an active hdisk
- Fixed a problem with setting the DIF_protection attribute of a disk
- Fixed a problem with disk attributes changing to defaults after reboot
- Fixed Disk operation error with PR_shared set on SAN
- Fixed a potential crash issue in SCSIDISK_DEL_PATH
- Fixed IOCINFO ioctl I/O throughput issues to degraded disk
- Fixed a potential memory leak issues for non-MPIO disks during rmdev
- Fixed path failures to storage on boot due to stale reserve
- Fixed path reservation conflict issues
- Fixed a potential system crash while configuring disks in mpiodeldriver
- Fixed an issue with excessive interrupt disablement time
- Fixed an issue with LPAR failing to suspend
- Fixed a hang issue with VASI snap data
- Fixed a potential VIOS crash issue while running AMS or during live partition mobility
- Fixed an issue with wrong client DRC name after mobility operation
- Fixed an issue with VIOS crash while unconfiguring vfchost via vfcmap command
- Fixed an issue with NPIV discover targets
- Fixed a potential crash issue with partition Suspend/Resume
- Fixed an issue with VSCSI disk paths recovery after rebooting a failed VIOS
- Fixed issues with inconsistent I/O results with file-backed virtual disks
- Fixed an issue with LPM with Oracle RAC
- Fixed an issue with Vhost driver directing SCSI inquiry to bad path
- Fixed an issue with VIOS closing connection during write to DAT 320 USB drive
- Fixed viosbr command issues and enhaced to backup and restore for SSP
- Fixed an issue with backupios -tape command hang
- Fixed an issue with lsnports parser error with large number of NPIV capable adapters
- Fixed an issue with Map LU
- Fixed an issue with mkbdsp command for SSP
- Fixed an issue with mkuser command
- Fixed a potential hang when changing SEA real adapter to Etherchannel adapter
- Fixed an issue with HEA driver causing multiple idle kernel processes
- Fixed crash problems seen with SEA
- Fixed some problems with MPIO during HBA failure or when changing zones
Document change history
| Date | Description of change |
Was this topic helpful?
Document Information
Modified date:
19 February 2022
UID
isg400001634