PACKAGE: Update Release 2.2.6.61
IOSLEVEL: 2.2.6.61
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 2.2.6.61 |
AIX 7100-05-06 or AIX 7200-04-02 |
Please refer to the VIOS Maintenance Strategy here for more details regarding the change to the VIOS release numbering scheme.
Be sure to heed all minimum space requirements before installing.
Review the list of fixes included in Update Release 2.2.6.61
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.6.61.
Microcode or system firmware downloads for Power Systems
If
the VIOS being updated has filesets installed
from the VIOS Expansion Pack, be sure to update those filesets with the latest VIOS Expansion Pack if updates are
available.
Update Release 2.2.6.61 updates your VIOS partition to ioslevel 2.2.6.61. To determine if Update Release 2.2.6.61 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update
Release 2.2.6.61 is installed, the command output is 2.2.6.61.
Outdated Fileset
Info
This release removes
the dependency on Java 7 from many filesets. If you would like to remove these filesets, and Java 7 itself, which goes out of support in
July 2022, you can use the following command:
$
updateios -remove_outdated_filesets
Please ensure that your rootvg contains at least 30 GB and that there is at least 4GB free space before you attempt to update to Update Release 2.2.6.61. Run the lsvg rootvg command, and then ensure there is enough free space.
Example:
$ lsvg rootvg VOLUME GROUP: rootvg VG IDENTIFIER: 00f6004600004c000000014306a3db3dVG 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: 2STALE PVs: 0 STALE PPs: 0ACTIVE PVs: 1 AUTO ON: yesMAX PPs per VG: 32512 MAX PPs per PV: 1016 MAX PVs: 32LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: noHOT SPARE: no BB POLICY: relocatable PV RESTRICTION: none INFINITE RETRY: no
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/Fixpack 2.2.6.10 must be applied to bring the VIOS to the latest Fix Pack VIOS 2.2.6.10 level. The Update Release 2.2.6.61 can then be applied to bring the VIOS to the latest level.
Note that with this Update Release 2.2.6.61, 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.6.61.
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
VIOS Update Release 2.2.6.61 may be applied directly to any VIOS that is at either level 2.2.6.0 or 2.2.6.10.
On a VIOS with a level between 2.2.1.1 and 2.2.5.x, a Single Step update procedure can be used to update to level 2.2.6.61.
Instructions: Single Step Update
To update to Update Release 2.2.6.61 from a level between 2.2.1.1 and 2.2.5.x in a single step, put the 2.2.6.10 updates in the same location as your 2.2.6.61 updates and do the update using the updateios command.
Warning: The update may fail if there is a loaded media repository.
To check for a loaded media repository, and then unload it, follow these steps.
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 Virtual Target Devices 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.
The Virtual I/O Server (VIOS) Version 2.2.2.1 or later, supports rolling updates for SSP clusters. The VIOS can be updated to Update Release 2.2.6.61 using rolling updates.
Version Specific Instructions: Version 2.2.1.3 or earlier.
A cluster that is created and configured on a VIOS at version 2.2.1.3 or earlier must be migrated to version 2.2.1.4 or 2.2.1.5 prior to utilizing rolling updates. This allows the user to keep their shared storage pool devices.
Version Specific Instructions: Version 2.2.1.4 or later.
The rolling updates enhancement allows the user to apply Update Release 2.2.6.61 to the VIOS logical partitions in the cluster individually without causing an outage in the entire cluster. The updated VIOS logical partitions cannot use the new SSP capabilities until all VIOS logical partitions in the cluster are updated.
To upgrade the VIOS logical partitions to use the new SSP capabilities, ensure that the following conditions are met:
· All VIOS logical partitions must have VIOS Update Release version 2.2.1.4 or later installed.
· All VIOS logical partitions must be running. If any VIOS logical partition in the cluster is not running, the cluster cannot be upgraded to use the new SSP capabilities.
Instructions: Verify the cluster is running at the same level as your node.
1.
Run the
following command:
$ cluster -status -verbose
2. Check the Node Upgrade Status field, and you should see one of the following terms:
UP_LEVEL: This means that the software level of the logical partition is higher
than the software level the cluster is running at.
ON_LEVEL: This means the software level of the logical partition and the
cluster are the same.
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.
To verify the VIOS update files, follow these steps:
1. $ oem_setup_env
2. Create a link to openssl
# ln -s /usr/bin/openssl
/usr/ios/utils/openssl
3.
Verify
the link to openssl was created
# ls -alL /usr/bin/openssl /usr/ios/utils/openssl
4. Verify that both files display similar owner and size
5. # exit
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.5.x.
You must put the 2.2.6.10 and 2.2.6.61 on the same location to apply updates in single step. The single step approach fixes an update problem with the builddate on bos.alt_disk_install.boot_images fileset.
Version Specific Warning: Version 2.2.2.1, 2.2.2.2, 2.2.2.3, or 2.2.3.1
You must run updateios command twice to get bos.alt_disk_install.boot_images fileset update problem fixed.
Run the following command after the step of "$ updateios –accept –install –dev <directory_name >" completes.
$ updateios –accept –dev <directory_name >
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.
When the VIOS is the updated, some of the current rules may revert to the
system defaults. Additionally, those changes may have been applied to the
system.
If you notice this issue, the default rules can be re-deployed and captured to
current rules by running the commands below.
$ rules -o deploy -d
$ rules -o
capture
Note: This will overwrite any customized rules in the current rules file.
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:
For VIOS nodes that are part of an SSP cluster, the partner node must be shown in 'cluster -status ' output as having a cluster status of OK and a pool status of OK. If the target node is updated before its VIOS partner is fully operational, client LPARs may crash.
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.
2. Using ftp, transfer the update file(s) to the directory you created.
3. To apply updates from a remotely mounted file system, and the remote file system is to be mounted read-only, follow the steps:
$ shutdown -restart
Note: If shutdown –restart command failed, run swrole –PAdmin in order for padmin to set authorization and establish access to the shutdown command properly.
$ clstartstop -start -n <cluster_name > -m <hostname >
$ ioslevel
Instructions: Checking for an incomplete installation caused by a loaded media repository.
After installing an Update Release, you can use this method to determine if you have encountered the problem of a loaded media library.
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.
Instructions: Recovering 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. Reinstall the ios.cli.rte fileset by running the following commands.
To escape the restricted shell:
$ oem_setup_env
To install the failed fileset:
# installp –Or –agX ios.cli.rte –d <device/directory >
To return to the restricted
shell:
# exit
3. Restart the VIOS.
$ shutdown –restart
4. Verify that the Media Repository is operational by running this command:
$ lsrep
For additional details, including known capabilities, limitations, and additional install considerations, as well as some additional instructions, please reference the readme for 2.2.6.10 located here.
This version will include all fixes found in all previous 2.2.6.X releases. The fixes for the previous release can be found here.
|
APAR |
Description |
|
IJ16381 |
SDK 8.0.0 64-bit SR5
FP36 - 19_02u1 |
|
IJ17106 |
SECLDAPCLNTD MAY DUMP
CORE DUE TO CERTAIN SERVER ERRORS |
|
IJ17150 |
SDK 8.0.0 64-bit SR5
FP37 - 19_02u2 |
|
IJ17845 |
SDK 7.0.0 32-bit SR10 FP50 - 19_03 |
|
IJ17846 |
SDK 7.0.0 64-bit SR10
FP50 - 19_03 |
|
IJ18052 |
SDK 8.0.0 64-bit SR5
FP40 - 19_03 |
|
IJ18767 |
nmon coredumps in collectSEAClients |
|
IJ19036 |
NPIV clients unable to
recover path after storage PID changed |
|
IJ19801 |
SDK 8.0.0 64-bit SR5
FP41 - 19_03u1 |
|
IJ19844 |
VIOS ABEND IN
NET_MALLOC_CPU DURRING LPM |
|
IJ20190 |
STRINGS SEGFAULT IN
MBRTOWC WITH MULTIBYTE DATA |
|
IJ20354 |
VNICSERVER_CRQ PROCESS
HIGH CPU USAGE |
|
IJ20465 |
USER I/O SLOWED DURING
THICK LU RESIZING |
|
IJ20473 |
SDK 7.0.0 32-bit SR10
FP55 - 19_04 |
|
IJ20474 |
SDK 7.0.0 64-bit SR10
FP55 - 19_04 |
|
IJ20781 |
A potential security
issue exists |
|
IJ21065 |
SDK 8.0.0 64-bit SR6 -
19_04 |
|
IJ21172 |
Merge not taking place
after node reboot in split case |
|
IJ21192 |
Uninitialized fields
in the ifnet loopback device cause crash. |
|
IJ21311 |
NDD_ENT_LARGE_SEND SET
ON VEA WITH CHKSUM_OFFLOAD=NO |
|
IJ21576 |
POSSIBLE UNDETECTED
DATA CORRUPTION WITH CERTAIN FIBRE CHANNEL A |
|
IJ21889 |
query for suspend
adapters should include hash character. |
|
IJ21890 |
unavailability of lock
may some time cause cluster op to fail |
|
IJ21891 |
Path is disabled on a
dynamic tracking failure |
|
IJ21893 |
vg names when similar
may lead to failure in HMC. |
|
IJ21894 |
FC define children
migration to non-MPIO not correct |
|
IJ21895 |
Gen4 NVMe drive VPD support |
|
IJ21896 |
IBM 4767 fails EEH
recovery with state ERROR (0x00208000) |
|
IJ21897 |
SSP Volumes may not be
listed in HMC GUI post mapping. |
|
IJ21898 |
PTHREAD_MUTEX_DESTROY() CAN COREDUMP WITH PTHREAD TRACE LIBRARY |
|
IJ21899 |
COMMANDS LIKE LSSRC OR
LSGROUP CAN CORE DUMP |
|
IJ21900 |
ALL TE_POLICY WERE SET
TO OFF AFTER UPDATING BOS.RTE.SECURITY |
|
IJ21901 |
HOSTMIBD DUMPS CORE
WHILE QUERYING MIB HRDEVICE |
|
IJ21902 |
CHVG -G MEMORY
EXHAUSTION WITH LARGE NUMBER OF PPS |
|
IJ21903 |
chuser
command is not showing correct error msg |
|
IJ21904 |
VIOS commands calling mklv/lquerypv may fail |
|
IJ21905 |
getty
display IBM copyright that ends with year 2019. |
|
IJ21906 |
KDB SVMON SUBCOMMAND
REPORTING UADSDPACE CORRUPT |
|
IJ21907 |
SYSTEM CRASH IN BIND PROCESSOR() |
|
IJ21908 |
Kernel memory leak
when Trusted Execution is on |
|
IJ21910 |
nmon
creating tilde files in home directory of uer. |
|
IJ21911 |
WITH MULTIPLE ROUTES
DEFINED NIMQUERY CAN REPORT INCORRECT GW |
|
IJ21912 |
TOPAS/NMON UTILITIES
HAVING VERY SLOW RESPONSE TIME |
|
IJ21913 |
VIOSBR MAY NOT RESTORE
DEFAULT GATEWAY IF IT'S A STATIC ROUTE |
|
IJ21914 |
CAA CLCONFD HANGS DUE
TO BAD SIGNAL HANDLER CODE |
|
IJ21915 |
BACKUPIOS -NOMEDIALIB
ONLY EXCLUDES VMLIBRARY IF IT IS IN ROOT |
|
IJ21916 |
VIOS can crash when
removing VEA from SEA |
|
IJ21917 |
EMSTAT LOOPS IN
SAMPLE_LOOP() WHEN IT FAILED TO CREATE THREADS |
|
IJ21918 |
PPROF REPORTS NEGATIVE
NUMBERS |
|
IJ21919 |
Link Aggregation
create may fail if default rules are set. |
|
IJ21920 |
Log replay error
(RC_BUSY) for lrMigTraverse with isolate |
|
IJ21921 |
Cache collisions occur
with disk worker tasks |
|
IJ21923 |
viosupgrade may fail for input relative path name |
|
IJ21926 |
INCORRECT FORMATTING
OF INTERVAL NUMBERS IN NMON RECORDING FILE |
|
IJ22011 |
SEA fails to configure
when jumbo_frames is set to yes on SEA |
|
IJ22027 |
SEA allowing multiple
trunk adapters with different VSWITCH ID. |
|
IJ22191 |
Tunnel state does not
go back to "Dormant" for ODT |
|
IJ22196 |
SEGMENTATION
FAULT(COREDUMP) WHEN RUNNING LSGROUP |
|
IJ22208 |
Crash in iscsisw_strategy |
|
IJ22260 |
add NVME files to mksysb tape for installation support |
|
IJ22277 |
SDK 7.0.0 32-bit SR10
FP60 - 20_01 |
|
IJ22278 |
SDK 7.0.0 64-bit SR10
FP60 - 20_01 |
|
IJ22315 |
VIOENTDD HANDLES
IEEE802.3 ETHERNET FRAMES WRONGLY |
|
IJ22325 |
SDK 8.0.0 64-bit
SR6FP5 - 20_01 |
|
IJ22420 |
SECLDAPCLNTD SUDDENLY
STARTS CONSUMING LARGE AMOUNTS OF CPU |
|
IJ22426 |
RULESCFGSET FAILS AS
PADMIN ON VIOS 3.1 |
|
IJ22445 |
ETHERCHANNEL
MODIFICATION CRASHES SYSTEM |
|
IJ22560 |
RULES COMMAND MAY
RETURN BOSBOOT ERROR |
|
IJ22644 |
NDD_ENABLE_ADAPTER
taking 15 seconds before calling device driv |
|
IJ22794 |
Fix vSCSI timer logic for LPM |
|
IJ22824 |
Empty pv udid may cause error in
management console |
|
IJ22914 |
IPsec fails to parse
IKE_AUTH with "Unrecognized Notify Error" |
|
IJ22919 |
PMLIST DUMPING CORE IN
PMREADEVS |
|
IJ22954 |
lpar
hung @cache_request_invalidate_run+0001A |
|
IJ22956 |
mlxcentdd
promiscuous mode does not support RSS. |
|
IJ23044 |
To support Mellanox
Embedded SM and the latest OpenSM |
|
IJ23211 |
NPIV CLIENT PATH LOST,
WITH INVALID CRQ REQUEST ERROR ON VIOS |
|
IJ23213 |
Crash seen during rmnode or shutdown on VIOS using SSP. |
|
IJ23214 |
Netmalloc
police debug facility is not thread safe |
|
IJ23228 |
DBN never elects due
to election thread not running. |
|
IJ23229 |
MULTIPLE PHASE2
TUNNELS FOR SINGLE PHASE1 CANNOT BE ESTABLISHED |
|
IJ23380 |
Adapters getting
unresponsive during EEH and device config |
|
IJ23606 |
vio_daemon won't start |
|
IJ23710 |
Crash when kproc takes over 10 seconds to initialize and execute |
|
IJ23747 |
ESA activation failing
when upgrading VIOS |
|
IJ23870 |
Cannot map new SSP LU |
|
IJ23888 |
Reduce CPU consumption
by mlxcentdd driver |
|
IJ23890 |
REDUCE CPU CONSUMPTION
IN ENTCORE |
|
IJ24175 |
SSP database election
taking a very long time or not completing. |