PACKAGE: Update Release 3.1.0.21
IOSLEVEL: 3.1.0.21
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 3.1.0.21 |
AIX 7200-03-03 |
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.0.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.0.21.
Microcode or system firmware downloads for Power Systems
Update Release 3.1.0.21 updates your VIOS partition to ioslevel 3.1.0.21. To determine if Update Release 3.1.0.21 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update
Release 3.1.0.21 is installed, the command output is 3.1.0.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.0.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.0.X versions of the VIOS.
Note: 3.1.0.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.0.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.0.21 may be applied directly to any VIOS that is at either level 3.1.0.00 or above.
The VIOS must first be upgraded to 3.1.0.00 before the 3.1.0.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.0.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.0.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.0.10 located here.
This version will include all fixes found in all previous 3.1.0.X releases. The fixes for the previous release can be found here.
|
APAR |
Description |
|
MKSYSB RESTORE FAILS TO CHECK IF SOURCE DISK IS
SAME |
|
|
IJ08438 |
PR_EXCLSVRNS RO AFTER LIVE UPDATE WITH ROOT DISK
USING |
|
IJ09625 |
A potential security issue exists |
|
IJ10405 |
ERRPT: USER DOES NOT HAS SUFFICIENT
AUTHORIZATIONS. |
|
IJ10559 |
IBM HYPERCONVERGED SYS: Unable to boot with
ghostdev=2 |
|
IJ11041 |
ATTRIBUTES SET BY RULES COMMAND NOT HONORED BY OS |
|
IJ11182 |
Kernel panic in ipsec due to double free |
|
IJ11197 |
Memory leak in pth_get_tls() |
|
IJ11374 |
CFGIF OVERWRITES THE IP ADDRESS SET BY DHCPCD |
|
IJ11484 |
UNDER MULTIBYTE LOCALE PROMPT MAY BE TRUNCATED IN
EDIT MODE |
|
IJ11550 |
XORG SECURITY VULNERABILITY |
|
IJ11605 |
TOPAS -M FAILED IN MEMORY TOPOLOGY PANEL. |
|
IJ11614 |
Unable to connect to Database in VIOS |
|
IJ11782 |
VARYONVG FAILURE FOR REMOTE GLVM DISKS BACKED BY
4K BS DISKS |
|
IJ11787 |
ABEND_TRAP IN VNIC_FREE_RX_MBUF_POOL () |
|
IJ11976 |
AFNXTREC/AFREAD FUNCTION CAN NOT HANDLE SPACE IN
FILE NAME |
|
IJ12134 |
entstat shows the link UP when the cable is pulled
on CX4 |
|
IJ12212 |
chsec fails to change stanza longer than 64
characters |
|
IJ12332 |
LSUSER ALL LISTS USER TWICE |
|
IJ12334 |
SNAP -c DOES NOT INCLUDE LIVEUPDATE DATA, APPLIES
TO AIX 7.2 |
|
IJ12335 |
LDAP CLIENT SENDS REPEATED REQUEST TO UPDATE
ATTRIBUTE |
|
IJ12336 |
LVM CONFIG CHANGES WHILE DISKS ARE MISSING CAN
CAUSE PROBLEMS |
|
IJ12339 |
fmemopen followed by getline and feof doesn't work
properly |
|
IJ12341 |
Live Update snap -a and U consistency |
|
IJ12343 |
CRASH IN JFS2 IACTIVATE DURING HIGH INODE USAGE |
|
IJ12344 |
ADDITIONAL LMT TRACES |
|
IJ12345 |
Limited amount of space reclaimed after extending
fs |
|
IJ12346 |
redzoned memory read during unmount |
|
IJ12347 |
devrsrv only looks in CuAt for reserve_policy |
|
IJ12348 |
Very long lun names prevent cfgmgr from
configuring the lun |
|
IJ12350 |
devrsrv -f does not work for PR |
|
IJ12351 |
Transmit software queue timer not running |
|
IJ12352 |
Diagnostics displays wrong messages for PCIe3 16Gb
FC adapter. |
|
IJ12353 |
Transmit software queue timer not running |
|
IJ12354 |
Successful error recovery may lead to DEAD state |
|
IJ12355 |
Running Diagnostic test fails when port connected
to network. |
|
IJ12357 |
Transmit software queue timer not running |
|
IJ12358 |
entstat output displays incorrect Port VLAN value |
|
IJ12359 |
GROWING SSP DISKS BY A LARGE AMOUNT MAY RESULT IN
I/O FAILURE |
|
IJ12360 |
NIMCLIENT-C EXTRACTS LIBSSL.SO.0.9.8 INSTEAD OF
LIBSSL.SO |
|
IJ12361 |
VIOS SSP I/O CAN SLOW AFTER ADDING/REMOVING
UNBALANCED FAILGRP |
|
IJ12362 |
IFCONFIG MAY SHOW FLAGS WITHOUT IFF_DEVHEALTH |
|
IJ12363 |
XMTOPAS FILES NOT ROTATING AS FTELL IS FAILING |
|
IJ12364 |
CLCOMD CORE DUMP AT LOG_PRINTF |
|
IJ12365 |
CAA: UNABLE TO ADD A NEW BACKUP REPOSITORY DISK |
|
IJ12366 |
perfstat_virtualdiskadapter()
writes messages to standard out |
|
IJ12369 |
perfstat_bridgedadapters()
sets errno to 0 if 1st param is inva |
|
IJ12370 |
SNMPDV3NE CORE DUMPS |
|
IJ12371 |
NIM SYNC OPERATION DISPLAYS NIMSTATE: REQUEST
DENIED MESSAGE |
|
IJ12372 |
CAA:UNEXPECTED CLCONFD STARTUP ON STOPPED NODE LEADS TO DEADLOCK |
|
IJ12373 |
NAMED LOGS TOO MANY MESSAGES TO THE LOGGING
CHANNEL |
|
IJ12375 |
ROOTVG DISK ATTRIBUTES RESET TO DEFAULT AFTER
MKSYSB RESTORE |
|
IJ12377 |
INVALID TCPSOCK CONNECTIONS CREATED FOR NON CAA TRAFFIC |
|
IJ12379 |
pmctl -S and -r fails to release counter
reservations |
|
IJ12381 |
The bottom command line doesn't scroll on dtterm |
|
IJ12383 |
Drop ARP hold queue packets if interface does not
match |
|
IJ12384 |
Correcting lparstat usage messages |
|
IJ12385 |
Live update warning after shutting down the
original LPAR. |
|
IJ12387 |
smt mode should be changed to numeric 2 rather
than On |
|
IJ12388 |
smt mode change through smtctl does not effect amepat |
|
IJ12389 |
Segmentation fault occurs by xlsfonts -ll |
|
IJ12390 |
Additional privileges added to ike and ikedb
commands for RBAC |
|
IJ12398 |
AutoFS doesn't work on a live updated system |
|
IJ12399 |
A potential security issue exists |
|
IJ12421 |
CERTAIN SEQUENCE OF LINK UP / DOWN EVENTS COULD
RESULT IN HANG |
|
IJ12422 |
NETSTAT -V LOGS 'PHYSICAL LINK DOWN' IN ERRPT -A |
|
IJ12424 |
Error reported for DLPAR vNIC |
|
IJ12426 |
shientdd device driver recovery state machine fix |
|
IJ12427 |
FC EN0S EN0T EN0U EN0V EN0W EN0X diag hang fix in
APAR IJ11143 |
|
IJ12429 |
EEH logged when removing wrap plug. |
|
IJ12431 |
SLI-4 memory trace fixes |
|
IJ12435 |
GREP MAY DUMP CORE IF A LINE EXCEEDS AVAILABLE
MEMORY |
|
IJ12436 |
CRON LOOPS LOGGING ERROR MESSAGES FOR
"READ" |
|
IJ12437 |
LISTIO64 RETURN 0 WITH ERRNO EIO |
|
IJ12438 |
vi truncates very long line |
|
IJ12439 |
wall comamnd shows error with openssh 7.1 > |
|
IJ12440 |
IMPORTVG FAILS WITH UTF8 LC_COLLATE IF VG NAME HAS
UNDERSCORE |
|
IJ12441 |
cron is not restarting |
|
IJ12442 |
Fsck displays invalid aggregate inode number. |
|
IJ12443 |
Synchronize POF kproc creation and initialization |
|
IJ12444 |
SCHEDO -P -O WAITLOCK_POLICY=1,2 OR 3 FAILS |
|
IJ12445 |
DBX SHOWS WARNING EVEN WHEN EXE HASN`T CHANGED |
|
IJ12446 |
Additional Live Update status bit |
|
IJ12447 |
mclpGrowBlock not dividing element count even
across buckets |
|
IJ12448 |
Crash during force unmount of memory mapped file. |
|
IJ12449 |
latency on drw_lock_done by write owner |
|
IJ12450 |
pci -tm KDB subcommand disrupts system state |
|
IJ12451 |
splat not reporting krlock activity correctly |
|
IJ12452 |
system abend in px_enter_vrma+0006E4 |
|
IJ12453 |
Crash when unmounting while reading external
snapshots. |
|
IJ12454 |
io_delay() of 0 triggers
kernel assert |
|
IJ12456 |
schedo changes for drw_lock_read krlock spin |
|
IJ12457 |
System crash in vm_pgz_binit. |
|
IJ12465 |
KSH MAY OUTPUT NON-ASCII CHARACTERS INCORRECTLY |
|
IJ12481 |
vnicserver produces a fatal error during logical
link down |
|
IJ12590 |
Boot from non-MPIO iSCSI disk fails with 554 LED |
|
IJ12591 |
unmirrorvg command accepts wrong input |
|
IJ12592 |
snmpdv3 unable to retrieve smux peer information |
|
IJ12593 |
LDAP OPERATIONS HANG WITH CIRCULARLY DEFINED
NETGROUPS |
|
IJ12594 |
postgres dumping core when compiled with -pg |
|
IJ12633 |
J2GT THREAD PERFORMANCE ISSUES |
|
IJ12676 |
CM busy error may be seen during adapter config
and unconfig. |
|
IJ12677 |
Access to bad buffer causes new j2 traces to
sometimes crash. |
|
IJ12700 |
NMON IS DELAYING ITS INTERVAL WHEN -S VALUE IS
HIGH |
|
IJ12701 |
NMON COREDUMPS WHEN # OF SEACLIENTS INCREASE IN
2ND DAY. |
|
IJ12702 |
NMON COREDUMPS IN FIND_SEA_CLIENTS IF #OF
SEACLIENTS IS HIGH |
|
IJ12703 |
NMON REPORTS NEGATIVE NUMBER AS INVALID VALUE FOR
-Z FLAG |
|
IJ12704 |
NIM MKSYSB ENCOUNTERS ERROR BUT STDERR MESSAGE NOT
DISPLAYED |
|
IJ12705 |
nmon may coredump in uargs |
|
IJ12706 |
nmon panel shows 1024 CPU in -h option |
|
IJ12709 |
Reservation conflict on ioctl |
|
IJ12712 |
Hang while reading aggregate inode |
|
IJ12789 |
VARYONVG FAILURE FOR RPV CLIENT DISKS BACKED BY 4K
BS DISKS |
|
IJ12802 |
USER_REBOOT EVENT IS NOT RECORDED WHEN RESTARTING
THE SYSTEM |
|
IJ12803 |
SPECULATIVE EXECUTION PROBLEM IN THE MELLANOX
DRIVER |
|
IJ12806 |
Y4 Crypto diagnostics reports software error when
device busy |
|
IJ12809 |
SEA PLSO_BRIDGE=YES LARGE_RECEIVE PACKET
CORRUPTION |
|
IJ12857 |
lsnports tports value may change unexpectedly on
VIOS |
|
IJ12858 |
Live dump call on
Ethernet adapter may lead to AIX system crash |
|
IJ12877 |
BOOTPKG DOES NOT DISPLAY AN ERROR MESSAGE WHEN
/TMP IS FULL |
|
IJ12898 |
TYPESET -Z <LEN> <VAR> SET <VAR>
TO NULL ON SECOND CALL |
|
IJ12919 |
Enhance FFDC tracing for NPIV host driver |
|
IJ12920 |
NVMe Inconsistent lscfg output before & after
download microcode |
|
IJ12921 |
cq_create doesn't unmap DMA on failure. |
|
IJ12967 |
No prompt for LDAP user to re-set password during
grace login. |
|
IJ12983 |
A potential security issue exists |
|
IJ12984 |
CONFIG TIMEOUT OF 0 DOES NOT WORK AS DOCUMENTED |
|
IJ12989 |
ASSERT IN CLOSEF WHEN CALLED FROM VFC_CONFIG() |
|
IJ13068 |
Disconnecting USB3 causes crash in
xhci_offlevel_iodone |
|
IJ13175 |
queue_pairs ODM attribute missing range increment
specifier |
|
IJ13177 |
ldd fails after upgrade to AIX 7.2 |
|
IJ13178 |
SYSTEM HANG - LVM INTERRUPT PRIORITY ISSUE |
|
IJ13188 |
NETSTAT FAILS WITH SYMBOL RESOLUTION ERROR |
|
IJ13189 |
KERNEL ABEND CRASH IN "NETINET" WHEN
RUNNING IFCONFIG |
|
IJ13200 |
unknown subhook 007E in the SEA component trace |
|
IJ13250 |
abend_trap in vm_map_entry_delete |
|
IJ13330 |
SORT MAY INSERT NEWLINE INTO LONG LINE WHEN LANG
IS NOT C |
|
IJ13334 |
creating ibX interface and ibstat command fail |
|
IJ13371 |
CRASH IN SCHED() CODE
WHILE ACCESSING P_JOB FIELD. |
|
IJ13382 |
ifconfig may hang on shientdd driver instance |
|
IJ13384 |
LARGE SNAPSHOT SIZE MAY CAUSE "DF" TO
SHOW INVALID INFO |
|
IJ13403 |
SHIENT_SW_ERR has incorrect error type |
|
IJ13405 |
Correct event scan race condition during boot |
|
IJ13584 |
NFS4_REMOVE: AIX NFS CLIENT MAY LOOP WITH
NFS4ERR-FILE-OPEN |
|
IJ13747 |
Calls to nd_del_filter pass too many arguments |
|
IJ13749 |
NETWORK PERFORMANCE GOES DOWN WHEN LARGESEND IS
ENABLED |
|
IJ13750 |
MKSYSB -F CANNOT USE THE MAP FILES. RESTORE FAILS |
|
IJ13753 |
kdb user displays wrong addresses |
|
IJ13754 |
EILSEQ AFTER MBRTOWC APARS IJ0498 IJ04984 IJ06290
IJ06385 |
|
IJ13950 |
SSP VIOS crash in ngdisk_finish_iodone |
|
IJ13953 |
SYSTEM CRASH IN V_RELFRAME()
WHEN NFS FILESYSTEM GETS FULL |
|
IJ13955 |
ls shows bad time after nfs3 exclusive open
failure |
|
IJ13961 |
NIMADM ERROR IN PHASE6 "0403-058 ASSIGNMENT
REQUIRES AN LVALUE." |
|
IJ14077 |
Issue with dbx subcommand list & move |
|
IJ14078 |
LIVE UPDATE FAILS DURING THE BLACKOUT PERIOD |
|
IJ14081 |
Update Diagnostics VRMF |
|
IJ14082 |
clcomd not using all interfaces for communication |
|
IJ14083 |
VFC CLIENT DRIVER COULD HANG AFTER ERROR RECOVERY |
|
IJ14123 |
CAA NODE HALT IN CLUSTER_HANDLED()
DUE TO RACE CONDITION |
|
IJ14354 |
HOST COULD LOG FCA_ERR2 WITH SENSE DATA 0DB8 AFTER
FABRIC EVENT |
|
IJ14356 |
Incorrect format for print of 'response' field in
KDB 'svva' |
|
IJ14358 |
LPM operation fails with firmware error |
|
IJ14362 |
Update FLADJ register default on USB3 PCIe Adapter |
|
IJ14363 |
system crashing at restore_context due to
synchronize issue. |
|
IJ14365 |
LU VIA NIM WILL FAIL IF CLIENT USES INTERFACE
OTHER THAN IF1 |
|
IJ14366 |
Failed to start probevue session when probing aso
with * |
|
IJ14367 |
nmon recording shows zeros for 1st ite for FC/SEA |
|
IJ14372 |
vm crashed while running 1TH tests |
|
IJ14373 |
netstat -I doesnt throw err for invalid i/p |
|
IJ14374 |
crash in xmalloc with bad pin count |
|
IJ14375 |
Hang when force unmounting nfs filesystem |
|
IJ14382 |
Shipping files for cmdpios and cmdarch |
|
IJ14522 |
schedo krlock_enable needs to be changed to
numeric value |
|
IJ14558 |
DATA COLLECTION PROCESS SLOWS POOL RECOVERY DURING
NETWK OUTAGE |
|
IJ14559 |
NEW METHOD TO HANDLE ASYMMETRIC NETWORK OUTAGE OF
SSP |
|
IJ14590 |
Multiple dynamic filters seen for IKEv2 tunnels |
|
IJ14595 |
Virtio Ethernet device fails to configure |
|
IJ14597 |
unsafe use of temporary files by alog |
|
IJ14598 |
Updating timezone data files to latest available |
|
IJ14617 |
Possible system crash during EEH scenario |
|
IJ14618 |
AIX vNIC client wouldn't recover EEH when physical
link is down |
|
IJ14619 |
SEA sharing mode RARP problem |
|
IJ14620 |
Improve "dump cache all" to reduce
number of objects we dump |
|
IJ14621 |
pool lsattr was not allowing long tier names |
|
IJ14622 |
Client hang in tmTryIndentify()
retry loop for more than 10 hrs |
|
IJ14784 |
clstartstop cmd having permission issue |
|
IJ14942 |
VNIC interfaces dropping large numbers of receive
packets |
|
IJ14943 |
system may hang during AIX build installation |
|
IJ14944 |
POOL STUCK WHILE TRYING TO UNMOUNT |
|
IJ15040 |
LPM operation fails with firmware error |
|
IJ15063 |
Signal 6 in dapl_evd_qp_async_error_callback on
AIX 7.2 TL |
|
IJ15112 |
VIOS becomes extremely unresponsive |
|
IJ15145 |
SSP LU MAP FAILS WITH CANNOT ACCESS A DEVICE |
|
IJ15342 |
A potential security issue exists |
|
IJ15376 |
vnic_server is not returning all
of the buffers on LINK DOWN |
|
IJ15410 |
hxedapl stops running due to resource allocation
failed |
|
IJ15416 |
Packet loss in devices with feature code ENOS and
EN0W |
|
IJ15610 |
Update bos.alt_disk_install.boot_images |
|
IJ15614 |
JAPANESE ERA CHANGE FROM HEISEI TO REIWA |
|
IJ15618 |
rda seg fault on SEAs |
|
IJ15620 |
viosbr fails to restore cluster when prev DBN not
restored first |
|
IJ15621 |
Unexpected I/O error on last path after timeout |
|
IJ15629 |
Invalid opcode error logged by SAS adapter. |