PACKAGE: Update Release 3.1.1.21
IOSLEVEL: 3.1.1.21
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 3.1.1.21 |
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 3.1.1.21
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.1.21.
Microcode or system firmware downloads for Power Systems
Update Release 3.1.1.21 updates your VIOS partition to ioslevel 3.1.1.21. To determine if Update Release 3.1.1.21 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update Release 3.1.1.21 is installed, the command output is 3.1.1.21.
A database manager change has occurred for Shared Storage Pool (SSP). This change will have no direct impacts on behavior, however it does mean that non-disruptive upgrades of an SSP cluster to 3.1.X.X requires that SSP nodes first are updated to version 2.2.6.31 or higher before upgrading to a version of 3.1.0.0 or higher.
Once all VIOS nodes in the cluster have been updated to the latest 2.2.6.X version, double check that rolling upgrade has completed. This can be done by checking the output of “cluster -status -verbose” while logged in as padmin on one of the VIOS nodes in the cluster. Then, check the output for each node, and check for this field:
Node Upgrade Status: 2.2.6.31 ON_LEVEL
If all nodes have 2.2.6.31 or newer, and all say that they are “ON_LEVEL,” then upgrades to the VIOS to 3.1.0.00 or newer can occur without disruption to the SSP cluster.
Additionally, backup and restore can be used to restore older versions of the SSP cluster to 3.1.X.X versions of the VIOS.
Note: 3.1.X.X nodes are unable to join SSP clusters that contain nodes below level 2.2.6.31 or clusters with exclusively 2.2.6.31 or higher nodes prior to the nodes completing a rolling upgrade and saying that they are ON_LEVEL.
Lastly, customers that do not use Shared Storage Pool will be unaffected by this change.
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.1.21. 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 Virtual I/O Server support for Power Systems
VIOS Update Release 3.1.1.21 may be applied directly to any VIOS that is at either level 3.1.1.00 or above.
The VIOS must be upgraded to version 3.1.1.00 or 3.1.1.10 before Update Release 3.1.1.21 may be applied.
A single-step upgrade can be performed, but it requires that the user does the following:
1. Put the 3.1.1.10 install packages into the desired install directory.
2. Place the 3.1.1.21 install packages in the same directory.
3. Use the updateios command to perform the update.
The VIOS must first be upgraded to 3.1.0.00 before the 3.1.1.21 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.1.21 using rolling updates.
A non-disruptive
rolling update 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.1.21 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.
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 Filesetbos.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:
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:
$ 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 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
For additional details, including known capabilities, limitations, and additional install considerations, as well as some additional instructions, please reference the readme for 3.1.1.10 located here.
This version will include all fixes found in all previous 3.1.1.X releases. The fixes for the previous release can be found here.
|
APAR |
Description |
|
IJ22637 |
In multybyte locale diff -i report upper&lower |
|
IJ22346 |
0042-053 M_CKMAC: THERE IS NO NIM OBJECT NAMED "CERTIFICATE" |
|
IJ20786 |
A potential security issue exists |
|
IJ20963 |
Create 7.2 IPPs |
|
IJ20967 |
max_xfer_size not to exceed config requested |
|
IJ21137 |
POTENTIAL FOR SYSTEM HANG WHEN REMOVING A CPU WHILE TRACING |
|
IJ21173 |
Merge not taking place after node reboot in split case |
|
IJ21196 |
Uninitialized fields in the ifnet loopback device cause crash. |
|
IJ21335 |
VIOS commands calling mklv/lquerypv may fail |
|
IJ21338 |
VNICSERVER_CRQ PROCESS HIGH CPU USAGE |
|
IJ21353 |
PTHREAD_MUTEX_DESTROY() CAN COREDUMP WITH PTHREAD TRACE LIBRARY |
|
IJ21354 |
COMMANDS LIKE LSSRC OR LSGROUP CAN CORE DUMP |
|
IJ21355 |
STRINGS SEGFAULT IN MBRTOWC WITH MULTIBYTE DATA |
|
IJ21356 |
REPORT ALLOCATIONS ARE MISSING WITH MALLOCDEBUG=LOG SET |
|
IJ21357 |
ALL TE_POLICY WERE SET TO OFF AFTER UPDATING BOS.RTE.SECURITY |
|
IJ21358 |
LSUSER -A MAY NOT SHOW ALL USERS |
|
IJ21359 |
CSUM DOES NOT READ OUTPUT PAST 4096 BYTES WHEN READ FROM STDIN |
|
IJ21360 |
HOSTMIBD DUMPS CORE WHILE QUERYING MIB HRDEVICE |
|
IJ21361 |
CHVG -G MEMORY EXHAUSTION WITH LARGE NUMBER OF PPS |
|
IJ21362 |
chuser command is not showing correct error msg |
|
IJ21364 |
Shift + p doesn't work at vi after cw command |
|
IJ21365 |
NPIV clients unable to recover path after storage PID changed |
|
IJ21366 |
unavailability of lock may some time cause cluster op to fail |
|
IJ21368 |
SAN disk capacity is not displayed correctly |
|
IJ21369 |
user space kdb coredumps when running vnic dev command |
|
IJ21370 |
handle maxuproc value for sys0 in VIOS 3.1 |
|
IJ21371 |
iSCSI define children not creating new hdisk |
|
IJ21373 |
Path is disabled on a dynamic tracking failure |
|
IJ21379 |
vg names when similar may lead to failure in HMC. |
|
IJ21380 |
FC define children migration to non-MPIO not correct |
|
IJ21381 |
vfchost adapter may continually fail commands from client |
|
IJ21384 |
Permission denied for /proc/<PID>/cwd |
|
IJ21385 |
KDB SVMON SUBCOMMAND REPORTING UADSDPACE CORRUPT |
|
IJ21386 |
SYSTEM CRASH IN BIND PROCESSOR() |
|
IJ21387 |
SYSTEM CRASH WITH INTERRUPT STACK OVERFLOW WHILE DOING JFS2 IO |
|
IJ21388 |
SYSTEM CRASH IN NBC_LOCATE() |
|
IJ21390 |
VPM intelligent folding not supported |
|
IJ21391 |
Deleting file from nfs client while audit mode is on has bug. |
|
IJ21393 |
Minor fix to GZIP accelerator framework |
|
IJ21397 |
STARTWPAR LATENCY DUE TO NFS FILE SYSTEMS MOUNT |
|
IJ21398 |
nmon coredumps in collectSEAClients |
|
IJ21399 |
nmon creating tilde files in home directory of uer. |
|
IJ21400 |
WITH MULTIPLE ROUTES DEFINED NIMQUERY CAN REPORT INCORRECT GW |
|
IJ21401 |
system crash in copy_context pmsvcs kernel extension |
|
IJ21402 |
REMOVING LARGE NFS FILES RETURNS "NO SUCH FILE" ERROR |
|
IJ21405 |
TOPAS/NMON UTILITIES HAVING VERY SLOW RESPONSE TIME |
|
IJ21406 |
VIOS ABEND IN NET_MALLOC_CPU DURRING LPM |
|
IJ21409 |
CAA CLCONFD HANGS DUE TO BAD SIGNAL HANDLER CODE |
|
IJ21410 |
ALT_BOOT_VRMF DOES NOT MATCH BOS_MP64_VRMF |
|
IJ21411 |
EMSTAT LOOPS IN SAMPLE_LOOP() WHEN IT FAILED TO CREATE THREADS |
|
IJ21412 |
AIX NFS CLIENT CREATING DIRECTORY WITH GID OF -1 |
|
IJ21413 |
PPROF REPORTS NEGATIVE NUMBERS |
|
IJ21414 |
Link Aggregation create may fail if default rules are set. |
|
IJ21415 |
xstr command does not work correctly |
|
IJ21416 |
Log replay error (RC_BUSY) for lrMigTraverse with isolate |
|
IJ21419 |
USER I/O SLOWED DURING THICK LU RESIZING |
|
IJ21462 |
CMDB MAY STOP WHEN CHANGING TAPE BLOCK_SIZE |
|
IJ21505 |
lsmpio -ar shows all paths Failed when some are Available |
|
IJ21506 |
query for suspend adapters should include hash character. |
|
IJ21508 |
Gen4 NVMe drive VPD support |
|
IJ21509 |
IBM 4767 fails EEH recovery with state ERROR (0x00208000) |
|
IJ21527 |
POSSIBLE UNDETECTED DATA CORRUPTION WITH CERTAIN FIBRE CHANNEL A |
|
IJ21563 |
Treat ALUA Transitioning state as non-optimized |
|
IJ21564 |
VIOS 3.1.1 SSP may not recover from network loss |
|
IJ21727 |
NETCD REPEATEDLY CACHING SAME ENTRY |
|
IJ21818 |
imapd and pop3d entries are not inserted into /etc/inetd.conf |
|
IJ21819 |
VIOSBR MAY NOT RESTORE DEFAULT GATEWAY IF IT'S A STATIC ROUTE |
|
IJ21820 |
FAILED VIOSECURE/AIXPERT RULES ON VIOS |
|
IJ21821 |
BACKUPIOS -NOMEDIALIB ONLY EXCLUDES VMLIBRARY IF IT IS IN ROOT |
|
IJ21822 |
VIOS can crash when removing VEA from SEA |
|
IJ21823 |
Cache collisions occur with disk worker tasks |
|
IJ21824 |
viosupgrade may fail for input relative path name |
|
IJ21825 |
TRUSTCHK FAILS WHILE ADDING MULTIPLE LIBRARIES |
|
IJ21827 |
LARGE ENTRY IN .SH_HISTORY CAN CAUSE CORE DUMP FOR KSH93 |
|
IJ21829 |
SSP Volumes may not be listed in HMC GUI post mapping. |
|
IJ21830 |
Kernel memory leak when Trusted Execution is on |
|
IJ21831 |
bind to addr whose sun_path has trailing slash succeeds |
|
IJ21879 |
DBX CORE DUMPING WITH WATSON2 MALLOC SUBSYSTEM. |
|
IJ21885 |
getty display IBM copyright that ends with year 2019. |
|
IJ21963 |
INCORRECT FORMATTING OF INTERVAL NUMBERS IN NMON RECORDING FILE |
|
IJ21967 |
namespace pollution in <netdb.h> |
|
IJ21968 |
SEA allowing multiple trunk adapters with different VSWITCH ID. |
|
IJ22023 |
MKINSTALLP MAY FAIL WHEN CREATING ADDITIONAL LICENSE FILESET |
|
IJ22049 |
SOFTWARE ERROR logged against iscsi0 during boot |
|
IJ22069 |
SEGMENTATION FAULT(COREDUMP) WHEN RUNNING LSGROUP |
|
IJ22090 |
INTERRUPTING USRCK WITH CTL-C CAN DELETE PASSWD/GROUP FILES |
|
IJ22091 |
iSCSI login hangs if sb_max is set to 1GB or greater |
|
IJ22101 |
DEPRECATED PERL FUNCTION CAUSES 'DSH -E' TO FAIL |
|
IJ22119 |
SENDMAIL FAILS WHEN CALLED VIA KSH93 PIPE |
|
IJ22147 |
Run time error for CMSG_FIRSTHDR and CMSG_NXTHDR |
|
IJ22148 |
possible missing parenthesis ')' or ',' |
|
IJ22151 |
add NVME files to mksysb tape for installation support |
|
IJ22193 |
Tunnel state does not go back to "Dormant" for ODT |
|
IJ22209 |
NULL assignments to pointers & variables |
|
IJ22211 |
Crash in iscsisw_strategy |
|
IJ22264 |
SECLDAPCLNTD MAY DUMP CORE DUE TO CERTAIN SERVER ERRORS |
|
IJ22265 |
MEMORY LEAK IN GETGRSET_NETGROUP() |
|
IJ22267 |
PUTUSERPWX() IS NOT INCLUDED IN USERPW.H HEADER FILE |
|
IJ22287 |
EAFNOSUPPORT - Address family not supported |
|
IJ22288 |
Machine crashed @ soreserve+00008C |
|
IJ22289 |
sendmail command is not working with TLS Functionality |
|
IJ22290 |
IO HANG ON NPIV CLIENT BACKED BY SLI-4 ADAPTER ON VIOS |
|
IJ22304 |
FTPD MAY HANG IF THE CLIENT NEVER CLOSES ITS DATA CONNECTION |
|
IJ22306 |
LU: UPDATE LVUP_SAFE_KE TO INCLUDE SMT_LOADPIN |
|
IJ22348 |
iSCSI driver improvements for LPM |
|
IJ22377 |
PASSIVE CONCURRENT VG DOES NOT COME OUT OF SILENT MODE AFTER LKU |
|
IJ22423 |
MULTIPLE PHASE2 TUNNELS FOR SINGLE PHASE1 CANNOT BE ESTABLISHED |
|
IJ22437 |
DUPLICATE PACKETS WITH ETHERCHANNEL IN VNIC/SR-IOV ENVIRONMENT |
|
IJ22439 |
SECLDAPCLNTD SUDDENLY STARTS CONSUMING LARGE AMOUNTS OF CPU |
|
IJ22440 |
VIOS intermittently crashes |
|
IJ22461 |
Adding a LAR, interactive mkinstallp msg issue |
|
IJ22462 |
Error entry in devinst_log POST vios installation |
|
IJ22463 |
NDD_ENT_LARGE_SEND SET ON VEA WITH CHKSUM_OFFLOAD=NO |
|
IJ22464 |
ETHERCHANNEL MODIFICATION CRASHES SYSTEM |
|
IJ22465 |
cannot add or delete multiple backup adapters in smit |
|
IJ22466 |
FIND -LS DOES NOT PRINT "P" IN THE MODE FOR PIPE/ |
|
IJ22467 |
KRLOCK CONTENTION IN VM_FIXLMB_DR() WHEN APPS USING GETPROCS() |
|
IJ22468 |
Need better solution for machine crash at soreserve |
|
IJ22513 |
tmd dumps core |
|
IJ22514 |
MSYNC SYSTEM CALL CAN TAKE MORE TIME ON AIX 7.2 COMPARED TO 7.1 |
|
IJ22585 |
SYSTEM CRASH IN PROCXMT() |
|
IJ22586 |
bootinfo error installing into wpars |
|
IJ22587 |
Command hang when closing iSCSI disk |
|
IJ22588 |
Potential system crash when system trace is on for hook 419 |
|
IJ22603 |
ikekey.kdb Lock contention between ikev2d & cpsd |
|
IJ22604 |
Need even better solution for machine crash at soreserve |
|
IJ22605 |
RULES COMMAND MAY RETURN BOSBOOT ERROR |
|
IJ22618 |
DISKS MISSING AT INSTALL TIME DUE TO ERRORS IN GET_RVG_DISKS |
|
IJ22623 |
Live Update operation fails because space runs out. |
|
IJ22639 |
NDD_ENABLE_ADAPTER taking 15 seconds before calling device driv |
|
IJ22669 |
CAT: 0652-050 CANNOT OPEN BOS.FILESET.RTE.AL WHEN UPDATING |
|
IJ22714 |
Possible undetected data corruption when rw_max_time is non-zero |
|
IJ22738 |
SYSTEM CAN CRASH IN V_PFEND_FSEG WHEN WLMCNTRL COMMAND RUNNING |
|
IJ22743 |
clconfd connectmon thread |
|
IJ22754 |
VIOENTDD HANDLES IEEE802.3 ETHERNET FRAMES WRONGLY |
|
IJ22767 |
Add VIOS request by ksys may result in false success. |
|
IJ22789 |
Add support for links in mount stubs for nfs lku code |
|
IJ22790 |
Fix vSCSI timer logic for LPM |
|
IJ22821 |
Empty pv udid may cause error in management console |
|
IJ22882 |
IPsec fails to parse IKE_AUTH with "Unrecognized Notify Error" |
|
IJ22912 |
ikedb -p gives error after reboot -q |
|
IJ22913 |
AIX->Windows ping hangs after SA idletimeout |
|
IJ22933 |
PMLIST DUMPING CORE IN PMREADEVS |
|
IJ22936 |
lpar hung @cache_request_invalidate_run+0001A |
|
IJ22937 |
mlxcentdd promiscuous mode does not support RSS. |
|
IJ22976 |
FD leak problem seen during ike negotiations |
|
IJ23011 |
reducevg unclear on delay when waiting for inflight reclaim req |
|
IJ23066 |
refresh of ike daemons not cleaning deleted IPs from netstat o/p |
|
IJ23067 |
IKEv2 OnDemand filter rules are removed after Phase1 Refresh. |
|
IJ23068 |
To support Mellanox Embedded SM and the latest OpenSM |
|
IJ23073 |
RESULT0645-007 ATTENTION:SUBSHRC() RETURNED AN UNEXPECTED |
|
IJ23092 |
SOME VFC ERRORS MAY GET LOGGED INCORRECTLY |
|
IJ23093 |
AUTOMOUNTD USES UP ALL MEMORY AND CORE DUMPS |
|
IJ23120 |
LDD IN AIX 7100-05-02-1832 AND 7200-03-02-1846 CAN NOT FIND LIB |
|
IJ23121 |
SEGMENTATION FAULT(COREDUMP) IN PWD -P |
|
IJ23122 |
Failure to commit with update_all |
|
IJ23123 |
Procstack missing stack before signal reception from 7.2 |
|
IJ23124 |
Diag failed to format any namespace greater than 9. |
|
IJ23125 |
Handle filename paths in the RTAS snap collection script |
|
IJ23128 |
Crash seen during rmnode or shutdown on VIOS using SSP. |
|
IJ23173 |
diff -b fails to treat carriage return as white space |
|
IJ23174 |
chdev fails to change nthreads SEA attribute |
|
IJ23176 |
RTB_LOCK CAUSES PERFORMANCE DEGRADATION IN AIX 7.2 TL3 SP3 |
|
IJ23190 |
Netmalloc police debug facility is not thread safe |
|
IJ23222 |
POSSIBLE I/O PERFORMANCE PROBLEM WITH LINUX CLIENT LPARS |
|
IJ23234 |
DBN never elects due to election thread not running. |
|
IJ23235 |
AIX Diag fail to secure delete RDX over 1TB |
|
IJ23236 |
sa_ & key_rem_lifetime are non 0 though tunnels remov |
|
IJ23237 |
KDB command - Potential errors when displaying PPDA |
|
IJ23238 |
Updating timezone data files to latest available for 2020 |
|
IJ23395 |
Adapters getting unresponsive during EEH and device config |
|
IJ23396 |
RULESCFGSET FAILS AS PADMIN ON VIOS 3.1 |
|
IJ23397 |
IKE Phase2 SA not cleaned up when its Phase1 is deleted. |
|
IJ23399 |
Performance regression in non-fastpath AIO |
|
IJ23400 |
Potential LPM failure when GZIP accelerator is in use |
|
IJ23436 |
STOP A WPAR WOULD UNLOAD RANDOM/URANDOM FOR THE LPAR SOMETIMES |
|
IJ23437 |
Diag failed to display microcode for PCIe3 10Gb 4-Port FCoE |
|
IJ23594 |
jumbo_frames setting incorrect for adapter added to EtherChannel |
|
IJ23628 |
Reduce CPU consumption by mlxcentdd driver |
|
IJ23711 |
Crash when kproc takes over 10 seconds to initialize and execute |
|
IJ23731 |
REDUCE CPU CONSUMPTION IN ENTCORE |
|
IJ23741 |
UPGRADING TO AIX 7.2 TL4 TRUNCATES /ETC/MAIL/ALIASES |
|
IJ23742 |
DB connection string in multiple IP conn can have junk in string |
|
IJ23743 |
lpar is hanging with ref. code 888 102 700 |
|
IJ23770 |
VIOS may crash or deadlock |
|
IJ23863 |
Cannot map new SSP LU |
|
IJ24004 |
Error accessing NFS files during LKU |
|
IJ24059 |
privileges for non-root users to use mail/mailx/sendmail |
|
IJ24176 |
SSP database election taking a very long time or not completing. |
|
IJ24184 |
AIX lpar may crash on a PHYP error to register CRQ |
|
IJ24307 |
vhost or vfchost adapter may hang or crash |
|
IJ24319 |
Error entry in update and cons log |
|
IJ24323 |
Crash in dbUpdatePMap after truncate |
|
IJ24572 |
Fix /usr/sbin/emgr[46]:RC:not found msg |
|
IJ24575 |
Kernel error during interrupt deconfiguration |
|
IV97329 |
Install images for devices.common.IBM.soe |