PACKAGE: Update Release 3.1.3.10
IOSLEVEL: 3.1.3.10
VIOS level is |
The AIX level of the NIM Master
level must be equal to or higher than |
Update Release 3.1.3.10 |
AIX
7200-05-03 |
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.
Be sure to
heed all minimum space requirements before installing.
Review the list of fixes included
in Update Release 3.1.3.10
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 3.1.3.10.
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 3.1.3.10
updates your VIOS partition to ioslevel 3.1.3.10.
To determine if Update Release 3.1.3.10
is already installed, run the following command from the VIOS command line.
$
ioslevel
If Update
Release 3.1.3.10
is installed, the command output is 3.1.3.10.
For
Customers Using Third Party Java-based Software
This only applies to
customers who both use third party Java based software and have run updateios -remove_outdated_filesets
to remove Java 7 from their system.
To prevent errant behavior when editing customer’s /etc/environment
file, updateios does not make changes to that file
when run. If a customer is using software that depends on using Java and having
the path to it in your PATH environment variable, the following edit should be
made to allow programs that use the PATH environment variable to locate Java 8.
In the /etc/environment
file, customers should see:
PATH=[various
directories]:/usr/java7_64/jre/bin:/usr/java7_64/bin
To address a potential issue with
Java-dependent third party software, this should be
converted to:
PATH=[various
directories]:/usr/java8_64/jre/bin:/usr/java8_64/bin
VIOS 3.1.3.10 adds the following new features:
LU
Rename Support Added for Shared Storage Pool (SSP)
Support has been
added to allow users to rename their LUs. This operation can be performed via
the new flag, [-modify], added to the lu
command in ioscli.
The ability
to convert LUs from the thin provisioned to thick provisioned dynamically has
been added. Performed via the new [-modify] flag added to the lu command in ioscli, this
feature allows users to preallocate storage for
existing LUs, rather than being forced to continue to rely on the just-in-time
provisioning after the LU has been created.
Note: This feature currently only allows
for unmapped LUs to have their provisioning changed to thick. An enhancement
for this feature is in development that will allow users to thicken mapped LUs
and will be added in a future release.
VIOSBR
Multiple Network Interface Support for SSP
In earlier
VIOS releases where multiple network interfaces were supported, VIOS Backup and
Restore did not fully support the feature. This meant that when an SSP Cluster
was restored from a backup, any network interfaces that were being used other
than the primary had to be added back manually. In this release, the restore
operation will now restore all network interfaces.
Other
Noteworthy Changes
·
SSP
IO performance improvements are available for fast SSD and NVMe
storage.
·
The
SSP and Change Management databases have been upgraded from Postgres 10 to
Postgres 13, a change that brings with it all the improvements to Postgres that
have been added in versions 11, 12, and 13.
Note: In order to move an
existing SSP Cluster to Postgres 13, a rolling upgrade must complete first. A
prerequisite for the rolling upgrade to occur is that all nodes in the cluster
be at version 3.1.3.10 or later.
VIOS
3.1.3.10 can run on any of the following Power Systems:
POWER 8 or
later.
The following requirements
and limitations apply to Shared Storage Pool (SSP) features and any associated
virtual storage enhancements.
Software Installation
SSP
Configuration
Feature |
Min |
Max |
Number of VIOS
Nodes in Cluster |
1 |
16* |
Number of
Physical Disks in Pool |
1 |
1024 |
Number of
Virtual Disks (LUs) Mappings in Pool |
1 |
8192 |
Number of
Client LPARs per VIOS node |
1 |
250* |
Capacity
of Physical Disks in Pool |
10GB |
16TB |
Storage Capacity
of Storage Pool |
10GB |
512TB |
Capacity
of a Virtual Disk (LU) in Pool |
1GB |
4TB |
Number of
Repository Disks |
1 |
1 |
Capacity
of Repository Disk |
512MB |
1016GB |
Number of
Client LPARs per Cluster |
1 |
2000 |
Prerequisites
for expanded support:
Here are the
new maximum values for each of these configuration options, if the associated
hardware specification has been met:
Feature |
Default
Max |
High
Spec Max |
Number of
VIOS Nodes in Cluster |
16 |
24 |
Number of
Client LPARs per VIOS node |
250 |
400 |
Network Configuration
Storage Configuration
Shared Storage Pool capabilities and limitations
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
3.1.3.10. 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 |
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
Virtual I/O Server support for Power Systems
VIOS Update Release 3.1.3.10 may be applied directly to any VIOS
at level 3.1.0.00.
The VIOS must first be upgraded to 3.1.0.00 before the 3.1.3.10
update can be applied. To learn more
about how to do that, please read the information provided here.
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
3.1.3.10 using rolling updates.
Non-disruptive rolling updated to VIOS 3.1 requires all SSP
nodes to be at VIOS 2.2.6.31 or later. See detailed instructions in the VIOS
3.1 documentation
The rolling updates enhancement allows the user to apply Update
Release 3.1.3.10 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.6.31 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: 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.
During update, there have been occasional issues with VIOS Rules files getting
overwritten and/or system settings getting reset to their default values.
To
ensure that this doesn’t affect you, we recommend making a backup of the
current rules file. This file is located
here:
/home/padmin/rules/vios_current_rules.xml
First, to capture your current system settings, run this command:
$ rules -o capture
Then,
either copy the file to a backup location, or save off a list of your current
rules:
$
rules -o list > rules_list.txt
After
this is complete, proceed to update as normal.
When your update is complete, check your current rules and ensure that
they still match what is desired. If
not, either overwrite the original rules file with your backup, or proceed to
use the ‘rules -o modify’ and/or ‘rules -o add’ commands to change the rules to
match what is in your backup file.
Finally,
if you’ve failed to back up your rules, and are not sure what the rules should
be, you can deploy the recommended VIOS rules by using the following command:
$
rules -o deploy -d
Then,
if you wish to copy these new VIOS recommended rules to your current rules
file, just run:
$
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.
Instructions:
Applying updates to a VIOS.
2.
Using ftp, transfer the update file(s) to the directory you
created.
To apply updates from a remotely mounted file system, and the remote file
system is to be mounted read-only, follow the steps:
The update release can be burned onto a CD by using the ISO
image file(s). To apply updates from the CD/DVD drive, follow the steps:
$ shutdown -restart
Note: If shutdown –restart command failed, run swrole –PAdmin 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 data
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
APAR |
Description |
IJ29073 |
/etc/mail/aliases gets overwritten
during update |
IJ29952 |
_P_SIGTIMEDWAIT() NOT HANLDING MALLOC
FAILURE |
IJ22238 |
Install images for bos.dsc |
IJ28658 |
Free PV may be seen as in_use in HMC. |
IJ28724 |
Delay in err msg when resolving hostname with empty resolv.conf |
IJ28726 |
UNABLE TO SEND MAIL AFTER UPGRADING TO AIX 7.2 TL4 SP2 |
IJ28728 |
SENDMAIL MAY NOT USE /ETC/MAIL/ALIASES |
IJ28731 |
aixpert does
not check nextboot tunable values |
IJ28732 |
Select Input Kuten Panel are not
closed by esc key |
IJ28733 |
Coredump occur
when execute xlsfonts -l |
IJ28734 |
Modifying a type in alt_rootvg_op
command |
IJ28736 |
Unable to create cluster with 1023 pool |
IJ28738 |
Improve ESB migration delay logic to avoid spurious interrupts |
IJ28739 |
TOTAL ETHERCHANNEL FAILURE AFTER REBOOT |
IJ28740 |
CM or DLPAR PCI NVMe bootlist fails |
IJ28741 |
crash with large number of VFC client adapters |
IJ28742 |
REDUCEVG FAILS WHEN PVID OF DISK IN 'REMOVED STATE' IS USED |
IJ28743 |
WITH NO MTA, ALIAS RESOLUTION USING SUBMIT.CF DOES NOT WORK |
IJ28744 |
LVM reclaim code should use DF_LBP |
IJ28773 |
VFC client driver loops forever on unexpected PHYP return code. |
IJ28954 |
kdb may
core dump during snap collection |
IJ29014 |
ROOTVG DISK'S ALGORITHM CHANGED TO DEFAULT AFTER MKSYSB RESTORE |
IJ29016 |
Improve trace format for undispatch
hook 4B0 |
IJ29018 |
add_managed_system failed
for CEC |
IJ29020 |
Potential hang during device removal |
IJ29021 |
Cluster creation may fail for disk size change on the storage |
IJ29072 |
PowerVM response
to XSD request has invalid data |
IJ29075 |
AIXIM coredump in zh_CN
with some inputs |
IJ29165 |
System dump with IO failed with " -4" status |
IJ29167 |
core dump by ikev2d in ParsePayload |
IJ29196 |
Handle chdev of udid
attr for SEA |
IJ29197 |
Log PERM error instead of info error when there is an outstandi |
IJ29198 |
Unconfig of
non-mpio disks can result in crash. |
IJ29233 |
A truncated TSIG response can lead to an assert |
IJ29245 |
iptrace -T/-B/-Q
give wrong PID and unreadable trace file. |
IJ29246 |
iptrace fails
on IPv6-only network interface using BPF |
IJ29247 |
coredump by isakmpd at getGSSIdentityName |
IJ29250 |
After migration, some of the VMs discovery might fail. |
IJ29316 |
KSH93 TEST -E FAILS TO KEEP THE CORRECT UID EUID GID EGID |
IJ29349 |
CMDB MAY NOT WORK WITH UMASK 077 FOR ROOT |
IJ29391 |
Missing title message when displaying an error diagmenu 802032 |
IJ29393 |
System get hung during IPL with ref
code Code: 2578 |
IJ29475 |
NIM SAVEVG WITH -R OPTION FAILED DUE TO WRONG SPACE REQUIREMENT |
IJ29476 |
trcnm fails
when a kernel pathname is specified |
IJ29477 |
isakmpd hits
assert in isakmp_buf::~isakmp_buf |
IJ29481 |
DYN_TRACKING / MOVE_LOGIN FAILURE ON VIOS COULD CAUSE CRASH |
IJ29483 |
NPIV BOOT FAILURE WITH 554 AFTER UPGRADING TO 7200-05-01-2038 |
IJ29522 |
nmon(m)
panel not showing AMS statistics |
IJ29524 |
DR support for DGC UNITY Storage |
IJ29538 |
A TIMING WINDOW CAN LEAD TO NODE CRASH DUE TO A NULL POINTER |
IJ29540 |
Added kernel tracing for disaster recovery |
IJ29595 |
nimadm does
not set BLV size for 7.1 and 7.2 |
IJ29764 |
MOVE TO DISTRIBUTING IF PARTNER AGREES REGARDLESS OF EXPIRED BIT |
IJ29766 |
dumpfs
displays incorrect dmap information on large fs |
IJ29771 |
IN 7200-05 NIMADM FAILS DURING "INITIALIZING NIM
CLIENT" |
IJ29779 |
KSH ERROR IF CD '..' (DOT DOT) IN SYMLINK DIR |
IJ29803 |
KSH CANNOT CD '..' (DOT DOT) IN SOME MBCS NAMED DIRECTORIES |
IJ29830 |
Users unable to login with LAM authentication |
IJ29860 |
DU COMMAND REPORTS SIZES INCORRECTLY FOR UDF FILESYSTEMS |
IJ29861 |
A potential security issue exists |
IJ29864 |
NIM SAVEVG -R FLAG MAY NOT GETTING PASSED TO CLIENT |
IJ29867 |
IPTRACE DOES NOT CAPTURE ARP WITH FILTERS APPLIED |
IJ29868 |
system hung due to IPSEC SA idle timer handler lock contention |
IJ29870 |
Code that locks bmaps may cause
operations to fail. |
IJ29888 |
PAM_AUTH WON'T DISPLAY LDAP SERVER PASSWORD POLICY WARNINGS |
IJ29892 |
After LPM on 3.1.2 for npiv, there may
be a slight slowness |
IJ29893 |
Migration may not complete, stuck in collecting minisnap data |
IJ29894 |
chcluster fails
adding backup disks with diff name in same site |
IJ29897 |
mksysb
migration may fail with extendlv error of /usr |
IJ29928 |
sockets iocp do not work well with
live update |
IJ29930 |
Correctly handle target structure when Move Login fails |
IJ29931 |
Client may hang on a small icrease of num_cmd_elems attribute |
IJ29959 |
LDAPAFILES FAILS IF USERS ARE MISSING LDAP ATTRS |
IJ30056 |
migration install may fail to create boot image |
IJ30058 |
ahafs device
name change to /aha post live update |
IJ30114 |
Tape backup or restore may fail or be slow with VIOS 3.1.2 |
IJ30115 |
ISDS ADVANCED PASSWORD POLICY ERRORS NOT SHOWN |
IJ30121 |
MEMORY LEAKS IN GETUSERATTRS AND LOGINRESTRICTIONSX |
IJ30207 |
PERFSTAT_DISK_TOTAL CAN LEAK MEMORY |
IJ30209 |
Merged output for "lparstat -mpw" due to large values |
IJ30210 |
WHEN IPTRACE IS STOPPED/KILLED NDD_TRACE HOOKS ARE NOT CLEARED |
IJ30215 |
Lun-level
validation should copy correct vfcFrame data out |
IJ30216 |
LPM of IBMi client with double mapped
adapters could fail |
IJ30217 |
HSmon status
is inoperative on few VIOS |
IJ30292 |
REMOVE THE VNIC_LOG AS IT CAN CAUSE LOWLEVEL KDB TO CRASH |
IJ30313 |
rmdev hang
on client vNIC device |
IJ30317 |
SU USES PAM EVEN IF AIX.SECURITY.SU AUTHORISATION APPLIES |
IJ30318 |
Error seen while adding tsd entry for
libraries |
IJ30321 |
NIM AT 7200-05 NIMADM MAY FAIL WITH KSH: C_CH_NFSEXP: NOT FOUND |
IJ30468 |
Improve stuck-in-ENXIO state handling |
IJ30472 |
Trace timestamp for I/O INTERRUPT FLIH Hook D2 parameter |
IJ30474 |
tunnel_offload
setting does not display in SMIT |
IJ30476 |
Options missing from Ethernet adapter SMIT menus |
IJ30477 |
ksh core
dumps with pwd command |
IJ30478 |
MKVDEV WITH MIRRORED=TRUE CAN FAIL IN VIOS 3.1 |
IJ30479 |
Allow varyoffvg operation when all
local disks are unavailable |
IJ30481 |
A potential security issue exists |
IJ30483 |
LKU TUNABLES TRANSFER FAILURE DUE TO MISSING BOS.NET.NIS.CLIEN |
IJ30484 |
NIMADM FAILS WITH: 0042-130 C_CH_NFSEXP: "NFS_VERS"
CANNOT BE... |
IJ30486 |
assembler does not handle ptesync or xxspltd correctly |
IJ30487 |
POSIX_FALLOCATE NOT ALWAYS RETURNING ERROR |
IJ30496 |
VKE LOGS EALREADY WHEN CAA RETURNS EMPTY IP LIST WITH VIPA |
IJ30497 |
Junk chars after rmdev cmd during migration abort case |
IJ30540 |
ksys_hsmon daemon
is not up, in VMRM HA solution. |
IJ30543 |
PAM LOGS INCORRECT SYSLOG ERROR MESSAG WHEN RUNNING SU. |
IJ30548 |
Remove VIOS by Ksys should fail on fail
to connect to database. |
IJ30612 |
PMU Interrupt Rate Monitoring Event Change |
IJ30613 |
ike cmd=log not working for ikev2d |
IJ30615 |
SAVEVG -R WITH SIZE PREVIEW SHOULD NOT DO SAVEVG & JUST EXIT |
IJ30617 |
WHEN /AUDIT GETS FULL, AUDITSELECT RETURNS A WRONG ERRNO |
IJ30618 |
A potential security issue exists |
IJ30619 |
INCORRECT ODM ATTRIBUTE DESCRIPTIONS FOR CERTAIN INTERFACE TYPES |
IJ30734 |
VFC4_ERR19 ERROR LOGGED ON NPIV ADAPTERS AFTER UPGRADE TO 7.2.5 |
IJ30736 |
LPM of clients using NPIV may fail under rare circumstances. |
IJ30737 |
Device FFC missing from Diagnostics menu number |
IJ30742 |
System crash caused by nfs4 remount. |
IJ30760 |
vfc_host need
to set SUPPRESS_ABTS bit in login resp |
IJ30762 |
LSPV COREDUMP WITH MALLOCDEBUG DUE TO A DOUBLE FREE IN LIBSM.A |
IJ30780 |
Memory leak fix in ikev2d |
IJ30781 |
vfcmap fails
with "does not appear to be a valid FC port" |
IJ30867 |
alert events not generated in SSP Cluster |
IJ30869 |
ssp_postgres_backup fails
if hostname aliases are defined |
IJ30870 |
suma_swinv does
not function due to syntax error |
IJ30877 |
Send process_login to the correct
channel |
IJ30881 |
Several fixes regarding user interface |
IJ30882 |
Multithreaded applications core dump or hang |
IJ31200 |
incorrect VIOS error log recommendation |
IJ31201 |
bootlist too
large error 0514-222, install requests user input |
IJ31206 |
Updating timezone data files to latest
available for 2021 |
IJ31209 |
longjmp restores
VSRs incorrectly when compiled with __EXTABI__ |
IJ31538 |
error message needs update |
IJ31542 |
Live Update - socket time-out for memory migration |
IJ31544 |
PAX MAY LIST OR EXTRACT FILE IN PAX ARCHIVE |
IJ31545 |
A potential security issue exists |
IJ31548 |
PAM IMAP AND POP3 AUTHENTICATION FAILURES GIVE WRONG SYSLOG MSG |
IJ31549 |
CRASH IN ENTCORE_IOCTL DURING RMDEV OF ETHERCHANNEL |
IJ31550 |
send data transferred infor to
protocol driver |
IJ31552 |
Using npiv can lead to I/O errors |
IJ31587 |
TRUSTCHK UNDEFINED BEHAVIOR WITH INVALID FILE NAMES |
IJ31588 |
pwd behavioural change moving from SP3 to SP7 with a |
IJ31591 |
Correct NX GZIP accelerator advertisement for applications |
IJ31630 |
NIMCLIENT CUST INSTALL WITH '-RPATH' FAILS IF CONTAINS 'U' CHAR |
IJ31684 |
SYSTEM CRASH WITH STACK OVERFLOW FROM CONWRITE/CONLOG |
IJ31720 |
Later migration fails if vfchost dev
is not rem in prev mig op |
IJ31765 |
svmon may
take very long time when run with -C parameter. |
IJ31770 |
USERNAME WITH @ FAILING IF KRB5 IS CONFIGURED |
IJ31771 |
dsmserv hang
in on AIX 7.2 TL5 level |
IJ31772 |
PAM LOGS INCORRECT SYSLOG ERROR MESSAG WHEN RUNNING SU. |
IJ31773 |
QOS credit DLPAR operation may lead to misleading message on HMC |
IJ31774 |
bosboot
command fails disk names other than hdisk[0-9]... |
IJ31802 |
ipreport is
broken for VLAN packets |
IJ31870 |
Error in POWER9 dms file |
IJ31871 |
ikev2d core dump. |
IJ31876 |
AIX partition crashed removal of USB clover |
IJ31915 |
Bell Card Serial Adapter AIX - Undetermined Error / 41G ZZ |
IJ31919 |
NTP fileset migration may change links
to NTP3 |
IJ31920 |
ikev2d going into inoperative when PSK value="" |
IJ31921 |
A potential security issue exists |
IJ31929 |
Diagnostics reports Firmware License Expired. |
IJ31954 |
Using npiv can lead to
crash/errors/potential data corruption |
IJ31956 |
SSP: /HOME/IOS/LOGS MIGHT BE FILLED UP VKE_FATAL COLLECTION |
IJ31959 |
SCALABLEVG VARYONVG -NCA FAIL(CONC VG)
WHEN MIRRORED DISKS FAIL |
IJ31977 |
BEAM complaints for ips_filt |
IJ31980 |
Fix encryption status load error management |
IJ31983 |
rendev
support to rename VTD's |
IJ31984 |
LU rename code drop |
IJ31999 |
SAVEVG -T <VGNAME> USES FREE PPS FROM ROOTVG INSTEAD OF
<VGNAME> |
IJ32057 |
The warning message are not displayed by invalid par |
IJ32072 |
Crash in VNIC when unconfiguring and Livedump
running |
IJ32125 |
lvup_caa.sh to stop clcomd when in
NO_CLUSTER state |
IJ32141 |
Channel aware client is disconnected on subsequent NPIV Login w |
IJ32144 |
LI1M2 - AIX Install UAK Support |
IJ32166 |
performance issue due to a cache line that was holding a rt_loc |
IJ32170 |
Command to surface information from virtual adapter |
IJ32173 |
VIOS crashed while doing restart from ksys |
IJ32234 |
lpar
crashed @pm_trb_handler+000104 |
IJ32235 |
ikev2d inopertive due to coredump on multi xml tunnel |
IJ32263 |
SSP luresize did not fail for invalid
input |
IJ32264 |
lsattr -El
not listing srad_id attr
for puntfish FC |
IJ32265 |
LDAP ISSUES WITH NESTED GROUPS |
IJ32266 |
AIX CRASH IN SM4_DG_POLICY() |
IJ32312 |
DIAGNOSTICS DEVICE BUSY ERROR MESSAGE |
IJ32313 |
FABRIC FORMATTED RSCN MAY CAUSE IO PATH FAILURE |
IJ32314 |
Path loss after successful Migration |
IJ32413 |
SPLAT has strange output under Lock class & address column |
IJ32433 |
NIM AT 7200-05 NIMADM MAY FAIL IN P10 - C_CH_NFSEXP: NOT FOUND. |
IJ32453 |
ipreport can't
open files larger than 2GB |
IJ32454 |
NIM install using NFS4 fails. |
IJ32456 |
EFS KEYSTORE DOESN'T ALWAYS LOAD WHEN LOGGING IN |
IJ32458 |
Fix for VMRM DR solution for DGC Unity storage. |
IJ32460 |
VIOS can crash if NPIV passthru
response length is > 12K |
IJ32461 |
lsdev shows
PCIe3 adapter as PCIe4 |
IJ32468 |
CORRECTLY HANDLE TARGET STRUCTURE WHEN MOVE LOGIN FAILS |
IJ32470 |
tprof -E
incorrect address translation in compat mode |
IJ32476 |
Live Update - fix to reduce blackout time |
IJ32542 |
FC5899 sends packets with bad TCP checksums in SEA environment |
IJ32548 |
OFED list pointers need to be initialized before use |
IJ32596 |
Hang when configuring or unconfiguring iSCSI disks |
IJ32618 |
SNAPSHOT VG/ BACKUP LV DATA IS NOT ACCESSIBLE |
IJ32619 |
crti.o has
dependency on C++ runtime |
IJ32685 |
PMCFG SCRIPT MAY RESULT IN AUTOMOUNTD ERROR |
IJ32689 |
Seeing core in vios when vios in local mode |
IJ32722 |
IPv4 tunnel not activated when xml contains both IPV4 and IPV6. |
IJ32727 |
Pool doesn't mount automatically after reboot or pool restart. |
IJ32730 |
smitty malng remove language error |
IJ32736 |
Fix an object leak in memory. |
IJ32737 |
pthread_rwlock_unlock fails
with EPERM |
IJ32757 |
crash@vfc_wakeup_thread+00003C |
IJ32758 |
NFS MOUNT LINKS NOT COPIED DURING ALT_DISK_COPY |
IJ32759 |
dipnvme lpar crashed at @sched_free+000050 |
IJ32766 |
PSK tunnel may not activate |
IJ32767 |
snap failure when trying to get hdcrypt
snap |
IJ32822 |
CUSTOMISED PRE-DEFINED ATTRIBUTES ARE LOST WHEN CLONING ROOTVG |
IJ32823 |
VIOS GDR support for reduced number of paths. |
IJ32825 |
lu -list
may not return proper data when no mapping exists |
IJ32829 |
CRASH IN KGSS_RELEASE_CRED |
IJ32842 |
fail to establish tunnel with wide range of p2 remote addresses |
IJ32930 |
ikev2d not supporting multiple IKETransform
stanzas |
IJ32931 |
ikev2d core dump |
IJ32933 |
LOCAL disk events not sent to listeners |
IJ32935 |
KSH93 IN INTERACTIVE MODE MAY HANG |
IJ33021 |
CRASH IN CSQ_RUN FROM PTM_PUT |
IJ33029 |
INFINITE WHILE LOOP IN SCSIDISK_FORMAT_MODE_DATA |
IJ33033 |
Improve error messages for double mapped configuration failures |
IJ33069 |
CLUSTER.TA IN VIO_DAEMON FOR NODE THAT SWITCHED TO NEW |
IJ33070 |
AIX client may crash if frame not copy
on error |
IJ33071 |
client hang
after lpm |
IJ33074 |
trustchk may
give error for NTP binaries |
IJ33075 |
DBX will crash if debug_info includes DW_AT_location (DW_OP_bre |
IJ33121 |
DSH FAILS WITH CSH AFTER IJ26988 |
IJ33150 |
ikedb -p put
some big number for phase2 refresh(IPV6) |
IJ33151 |
scrloop coredumped |
IJ33157 |
'vioservice' coredump
on a cluster with more than 10 nodes. |
IJ33158 |
AIX may crash during live dump |
IJ33159 |
Incomplete error message displayed while updating |
IJ33212 |
ikev2d becomes inoperative on AIX-LINUX with IPV6 tunnels |
IJ33216 |
SSP nodes using invalid IP address to connect to the DBN. |
IJ33218 |
IO devices fail to configure if component trace mem too high |
IJ33219 |
extendvg core
dumps when mirror pool is specified. |
IJ33221 |
lpar
crashed @abend_trap+000000 |
IJ33229 |
Perform explicit LOGO to FC target ports |
IJ33230 |
PERFORM EXPLICIT LOGO TO FC TARGET PORTS |
IJ33280 |
CVE-2021-25215:AN ASSERTION CHECK CAN FAIL WHILE ANSWERING |
IJ33292 |
VM not migrating when Critical App is Failured |
IJ33294 |
DR validation may try unsued ports
another time. |
IJ33336 |
loopmount allows
invalid mounts of loopback devices |
IJ33337 |
Migration fails saying no free FC ports, even though there are |
IJ33343 |
Fix certain fields in SEA entstat
output |
IJ33344 |
extendvg:clean Hdcrypt metadata |
IJ33381 |
MELLANOX ADAPTER SENDING LLDP MULTICAST CAUSES NETWORK FAILURE |
IJ33382 |
System crash during LVM component dump |
IJ33409 |
rw_timeout may
expire too early for vscsi disks |
IJ33491 |
CHUSRATTR DOESN'T SET USER PADMIN STANZA AS IT SHOUL |
IJ33493 |
DBX prints in decimal format for signed char. |
IJ33495 |
CAA performance improvement |
IJ33497 |
defunct processes left in process table by vio_daemon |
IJ33498 |
DBN relinquishes DBN status unnecessarily. |
IJ33500 |
System crash at pcmGetPathState() |
IJ33501 |
System reboots during full-memory dump with huge pages enabled |
IJ33502 |
SSP luresize did not fail for invalid
input |
IJ33506 |
Fix memory leaking issues |
IJ33522 |
LPM can fail when migrating large LPARs over slower networks |
IJ33553 |
Pool goes down after failure to reserve ilog
blocks |
IJ33555 |
raw disk I/O stopped after successful LKU |
IJ33558 |
lpar got
hung @.ipoll_wait_test+000000 |
IJ33605 |
PROCESSES WHICH ARE UISNG IOCP CAN HANG IN IOCP_SLEEP |
IJ33617 |
Fixing security leaks in memory |
IJ33621 |
VNIC IN ETHERCHANNEL UPDATES LINK SPEED ONLY DURING OPEN() |
IJ33622 |
Software error seen with Adv Diagnostics on 4port 10/1Gb ent |
IJ33623 |
Additional event is reported when tape device is configured |
IJ33658 |
CAA additional performance improvement |
IJ33659 |
Zero-out password buffers in efs
application code |
IJ33700 |
Add PV fails with error |
IJ33737 |
NMVE BLANK STATUS IN CMDB CAUSES POWERVC 500 ERROR RESPONSE |
IJ33738 |
vio_daemon is
locked up, cannot get cluster status, add cluster |
IJ33754 |
command line kdb fails to run vfcs commands on dump analysis |
IJ33812 |
SSP database unable to start after clstartstop
used. |
IJ33815 |
NVMe disk
attribute algorithm may sometimes be empty. |
IJ33819 |
Improve fork-exec scalability |
IJ33919 |
Problem configuring virtual adapters after VIOS upgrade |
IJ33926 |
USING IPV6, VNIC CLIENT UNREACHABLE AFTER A TIME |
IJ33970 |
Discovery failing with add_ms error |
IJ34153 |
vioservice core
dump with large number of disks |
IJ34154 |
Random cable pulls fail all paths |
IJ34155 |
AIX client lpar may crash with vfc adapter in play. |
IJ34227 |
Incorrect num of scsi channels are
enabled after migration |
IJ34258 |
System may crash trying to aquire a
lock held |
IJ34259 |
change management process may hang for map of file back device |
IJ34332 |
IPV6 ACTIVITY MIGHT CAUSE CERTAIN SYSCALLS TO BEHAVE UNEXPECTLY |
IJ34618 |
Revert fix for APAR IJ33381. |
IJ34661 |
Inactive LPM of IBMi partion witg same phys FC port twice, fails |
IJ34662 |
crash in build_map_list |
IJ34665 |
ld can
fail when linking C++ objects |
IJ34668 |
ROCE ADAPTER SENDING LLDP MULTICAST CAUSES NETWORK FAILURE |
IJ34674 |
Blocking in_core switch in acfo command with LV-Encrypt disks |
IJ34678 |
AIX reports continuous error logs during LPM. |
IJ34717 |
crash may occur when RoCE adapter
takes too long for a command |