PACKAGE: Update Release 3.1.0.50
IOSLEVEL: 3.1.0.50
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 3.1.0.50 |
AIX 7200-03-06 |
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.50
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.50.
Microcode or system firmware downloads for Power Systems
Update Release 3.1.0.50 updates your VIOS partition to ioslevel 3.1.0.50. To determine if Update Release 3.1.0.50 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update Release 3.1.0.50 is installed, the command output is 3.1.0.50.
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.50. 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.50 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.50 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.50 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.50 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 |
|
IJ27554 |
A 32-bit program core dumps when ASLR and TLS are used together. |
|
IJ27546 |
accel_decompress does not properly fail-over to software decompre |
|
IJ27488 |
Add formatted trace in SEA code path where RARPs are sent |
|
IJ24856 |
ADD IANA 2020A TZ CHANGES FOR MOROCCO DST |
|
IJ26103 |
Add PowerVM secure boot support in DSM |
|
IJ28290 |
ADD_MS operation failed to lock the database. |
|
IJ25168 |
AddMS fail for CEC during discovery |
|
IJ27630 |
Address the issues with firmware assisted dump for Veritas |
|
IJ28298 |
AIX or VIOS may crash on FC cable pull |
|
IJ27434 |
AIX parition crashed EEH and rmdev operation on USB |
|
IJ27451 |
AIX system crashed at emfsc_log_err function |
|
IJ27443 |
Allow LUN RESET on error for iSCSI |
|
IJ24318 |
APPLICATION HANG WITH MALLOCTYPE WATSON2 |
|
IJ27468 |
ARTEXGET 0590-201 ERROR EXECUTING EXTERNAL COMMAND |
|
IJ28261 |
as generates RLD for relative branch when csect is weak |
|
IJ26904 |
ASO DAEMON CORE DUMP IN THE FUNCTION JOB_ADD_SYSTEM_PROCESS() |
|
IJ28266 |
Assembler performance is poor with very large input files |
|
IJ29069 |
Assert/crash in vnic stack while replenishing rx resources. |
|
IJ28271 |
Avoid mapping shared objects loaded from NFS file systems. |
|
IJ27469 |
BACKUPIOS DOES NOT HAVE AN OPTION TO EXCLUDE FILES FROM BACKUP |
|
IJ27453 |
bootlist alt_disk_copy alt_disk_mksysb fail hot plug FC adapter |
|
IJ27421 |
BOOTLIST SHOWS DASH FOR VALID BOOT DEVICES |
|
IJ27466 |
CAA CLCOMD COREDUMP IN LOG_NLPRINTF() |
|
IJ28279 |
Cable pulls on one storage type impact paths on ano |
|
IJ27436 |
Cannot config adapter into kernel |
|
IJ27431 |
chsp -replace hang in SSP replacedisk badpath |
|
IJ27619 |
CHUSER FAILS TO CHANGE BOOLEAN VALUE ATTRIBUTES WITH 389-DS SR |
|
IJ27452 |
Clover EEH test - INTRPPC_ERR - mac3p6 2 |
|
IJ25041 |
cluster nodes fail when network goes down |
|
IJ27513 |
Cluster Restore might Fail with altdisk using viosupgrade on |
|
IJ28573 |
cluster -status command may cause failure. |
|
IJ24414 |
CM or DLPAR PCI NVMe bootlist fails |
|
IJ27598 |
COMMAND TIMEOUTS AFTER LINK DOWN ON RETRY OF I/O ON GOOD PATHS |
|
IJ27534 |
Comment CAA ahafs code to keep kernel/KE in synch |
|
IJ28574 |
Compilation failure in C++ mode when including <sys/timeb.h> |
|
IJ26507 |
CONCURRENT VG FORCED OFFLINE WHEN DISK MISSING |
|
IJ25608 |
CONNECTION WITH SSP CLUSTER CAN HANG REQUIRING RE-BOOT OF VIOS |
|
IJ27485 |
context incorrect for pool fileset inode after disk failure |
|
IJ28293 |
core dump @hsDBFreeRes vioservice |
|
IJ27459 |
core dump@getLockForUpdate vio_daemon |
|
IJ27566 |
CORE IN LIBC/LOCAL CODE WHEN USING NIS |
|
IJ25174 |
coredump in VIO_DR_CLEAN_UP |
|
IJ27576 |
cpio does not always extract correctly from rpm2cpio archive |
|
IJ27538 |
Crash during facility_enable with temporary attach memory |
|
IJ27525 |
Crash in IPSec esp_rply_decap4() while freeing mbuf |
|
IJ26714 |
Crash in iscsisw_send_kproc on freed mbuf |
|
IJ27516 |
Crash while running iptrace with LKU |
|
IJ27637 |
crfs successfully creates a filesystem on an unavailable lv |
|
IJ25927 |
CVE-2020-8616 and CVE-2020-8617 |
|
IJ28276 |
defragfs command giving too much output for wrong input |
|
IJ25245 |
DEFRAGFS -F CAN CRASH IN DBBACKSPLIT WHEN BLOCKMAP IS CORRUPT |
|
IJ27438 |
Diagnostics Service Aid task reports software error |
|
IJ27606 |
Direct Attach to DS8890 cable pulls do not recover |
|
IJ24675 |
Disabling ipsec under high network load causes system hang |
|
IJ24268 |
DMPUNCOMPRESS: CORRUPT INPUT, PARTIAL DUMP FILE IS PRESERVED |
|
IJ26988 |
DSH COMMAND FAILS WITH "UNESCAPED LEFT BRACE IN REGEX.." ERROR |
|
IJ27419 |
elxent_eeh_entry leads to creach in elxent_bugout |
|
IJ27429 |
Empty storage port passed to lu_val calls to get LU details |
|
IJ27491 |
Err msg coming in console for up level cluster node |
|
IJ28288 |
Error "Unable to query record" observed during tier create |
|
IJ27552 |
Error in the CAPI accelerator page fault path |
|
IJ27467 |
errors in errpt due to unconnected fc from topas_nmon |
|
IJ27426 |
ethchan_config -d -b should return error |
|
IJ27579 |
ETHERCHANNEL WITH VEA DOESN'T UPDATE PLSO FLAGS |
|
IJ24674 |
Ethernet adapter doesn't report link events during FW update |
|
IJ27522 |
exportfs failure when re-exporting different NFS version |
|
IJ27496 |
Failed to change the mode of a Link Aggregation adapter |
|
IJ27481 |
Fails to restore node ssp mappings with -xmlvtds option |
|
IJ28282 |
Free LUN list memory in right place for DR function in mig_vscsi |
|
IJ28657 |
Free PV may be seen as in_use in HMC. |
|
IJ27572 |
GREP: CAN'T OPEN /TMP/TDD.ADD DISPLAYED DURING MKSYSB INSTALL |
|
IJ24067 |
HANG IN DISK DRIVER IF LUN IS UN-MAPPED AND OPEN ATTEMPTED |
|
IJ27416 |
HBAAPI INTERNAL CALL TO GA_NXT RESULTS IN ADDITIONAL FCP FRAME |
|
IJ28278 |
HM inactive in db after host failure |
|
IJ27448 |
HMC may give "System busy" error |
|
IJ25170 |
HSmon status is inoperative error |
|
IJ24195 |
IMPROPER HANDLING OF TIMERS IN KTIMER_SETTIME() |
|
IJ27515 |
Improve err msg for create SEA w/adapter under other SEA |
|
IJ27601 |
Improve LGPG creation engine |
|
IJ28285 |
Improve the CM process start logic |
|
IJ25122 |
IN RARE CASE FSCK MAY COMPLETE AND LEAVE THE METADATA CORRUPT |
|
IJ25422 |
IN VM RECOVERY MANAGER ENVIRONMENT, PUT_STORAGE MAY FAIL FOR EMC |
|
IJ27455 |
Inactive migration is failing from mac13fp |
|
IJ27441 |
Inconsistency with the sequence number in inventory response |
|
IJ27782 |
INCORRECT REPORT WITH "LSCTPIP -FMT ...." ON VIOS 3.1 |
|
IJ28268 |
INCORRECT RETURN CODE AND ERR MSG FOR "RMVDEV -LNAGG" |
|
IJ26116 |
INCORRECT VPD IN LSCFG OUTPUT FOR 2145/2076 DISKS USING AIXPCM |
|
IV88500 |
Install images for bos.msg.CA_ES.alt_disk_install.rte |
|
IJ27634 |
instsecattr not called to remove tsd entries |
|
IJ27539 |
INTERNAL SNAPSHOT TRIED TO TAKE LOCK TWICE AND CRASHED |
|
IJ27623 |
INVALID LOGIN NAME/PASSWORD ERROR GIVEN FOR SUCCESSFUL LOGIN |
|
IJ27476 |
IPsec filter state information at ike command |
|
IJ27509 |
IPv6 IKE Phase2 SA not cleaned up when its Phase1 is deleted |
|
IJ27520 |
IPv6 IKE tunnels cause tmd to hang on the responder |
|
IJ27425 |
iSCSI disks or paths not coming available |
|
IJ27563 |
Issue for applications using zlibNX during LKU |
|
IJ27710 |
Issue with ESA problem reporting |
|
IJ25150 |
JFS2 DEFRAGFS -F <MNTPT> CMD MAY PUT FILE SYSTEM IN READ-ONLY |
|
IJ27556 |
kdb may hang if kernel image doesn't match memory |
|
IJ27561 |
Kernel thread state set by EnableCriticalSections gets unset |
|
IJ27536 |
kproc incorrectly marked as exiting |
|
IJ25631 |
KRB5 MODULE PREVENTS NON-KRB5 USERNAMES FROM CONTAINING @ |
|
IJ27490 |
KSU NOT COMPATIBLE WITH GSSD/NFSV4 WITH KRB5 |
|
IJ28287 |
ksys_hsmond dumps core @ vioHmErrHandler |
|
IJ26516 |
LDAP USER LOGIN CAUSES MANY USER QUERIES |
|
IJ27567 |
LIBT/LIBPTHREADS.A OUTPUT WRONG PID |
|
IJ27527 |
Live update failed restoring ifnet6 mca |
|
IJ25190 |
LIVEUPDATE LOG "0590-121 NOT ENOUGH MEMORY" ERROR FROM ARTEXDIFF |
|
IJ29066 |
LKU fails when shared library file permissions are changed. |
|
IJ27569 |
LOCAL USERS CAN AUTHENTICATE THROUGH KRB5 UNEXPECTEDLY |
|
IJ27550 |
Locking problem in GZIP kernel accelerator framework on Power9 |
|
IJ27571 |
LOGINRESTRICTIONSX IGNORES GRAMMAR WITH LDAP HOST RESTRICTIONS |
|
IJ28565 |
LPAR crashes in vfc stack on P9 |
|
IJ27530 |
lpar got crashed @abend_trap+000000 |
|
IJ28264 |
lpar got hung at @drw_lock_write+000120 |
|
IJ27432 |
LPAR migration may hang if migrated with path loss LPM option |
|
IJ27589 |
LPM of linux client using iSCSI backed disks fails |
|
IJ27437 |
LPM of Linux clients using iscsi disks |
|
IJ27471 |
LS -L DISPLAYED FILE SIZES MAY BE INCORRECT ON NFSV4 CLIENT |
|
IJ24894 |
LS -S INCORRECTLY REPORTS SIZE IN 1024 |
|
IJ27628 |
lscore give incorrect error message when queried with module |
|
IJ27428 |
lsmpio may report incorrect connection information for NVMe disk |
|
IJ25967 |
LU: 1020-154 RESOURCE /DEV/KMEM IS NOT CHECKPOINTABLE |
|
IJ24932 |
LVM config commands hang/segmenation fault |
|
IJ27549 |
malloc_thread free kmem loop needs to disable intr |
|
IJ27586 |
MARGINALLY SLOWER TO RETRY I/O AFTER I/O FAILURE |
|
IJ27521 |
memory allocated for perfmon slih min saving are not freed |
|
IJ28281 |
Minor RAS cleanup/enhancement in Disk Driver |
|
IJ28289 |
Missing FFC in check condition |
|
IJ27621 |
MKSECLDAP FAILS IF BASE DN CONTAINS A SPACE |
|
IJ27489 |
Modified diagnostics default log file size. |
|
IJ26172 |
MOUNT POINT OUTPUT TRUNCATED WITH LSPV WITH -FMT OR -FIELD |
|
IJ27501 |
mproc cache attaching to StabilityMonitorAdvanced |
|
IJ27570 |
NETCD CACHES NEGATIVE TYPE 2 ENTRIES WITH A LONG TTL |
|
IJ28571 |
New disk capacity may not be seen in database. |
|
IJ28275 |
NFS4 ACLS NOT RETAINED AFTER A 'CP -P' |
|
IJ27465 |
NFS4 EXECUTABLES CAN FAIL WITH "PERMISSION DENIED" MSG |
|
IJ24497 |
NIMCLIENT ERROR ON CONSOLE AFTER NIM MKSYSB RESTORE |
|
IJ26144 |
NO OPERATIONS USING RESTART_INETD DISPLAY ERROR DUE TO LOCALE |
|
IJ27510 |
Node update hanged using "viosupgrade -l -c -a -u" |
|
IJ24498 |
NON MPIO DISK DRIVER MAY CAUSE ERROR ON HMC |
|
IJ27472 |
NTPv3 some times may loose synchronization |
|
IJ26529 |
Numa topology becomes inconsistent |
|
IJ28568 |
NVMe Diag format task reports software error when F3 pressed |
|
IJ27450 |
NVMe download microcode trims spaces from the microcode level |
|
IJ27445 |
ODM cfgmgr_psafe is missing from shientdd |
|
IJ24335 |
ODM ENTRIES FOR AUTO-REMOVED DUMP DEVICE REMAIN AFTER MIGRATION |
|
IJ27511 |
Partition migration operation fails wit |
|
IJ26669 |
PASSIVE CONCURRENT VG DOES NOT COME OUT OF SILENT MODE AFTER LU |
|
IJ26142 |
patch fail with diff listings produced by diff -u |
|
IJ27461 |
PCIDMA errors and adapter fails to configure |
|
IJ27524 |
pmctl -E exits with Hardware counters already in use error |
|
IJ27526 |
Pool replica set contains disks removed from SYSTEM tier |
|
IJ28562 |
Possible crash in FC drivers |
|
IJ28566 |
Possible LPM failure |
|
IJ27545 |
Possible LPM failure on Power9 when using GZIP accelerator |
|
IJ28267 |
Prefetch performance fix for pfFileLogicalToVirtPrefetch |
|
IJ25721 |
PROCTREE NOT REPORTING ALL PROCESSES |
|
IJ27480 |
Prompted Graphical BOS Install Summary menu issue |
|
IJ27458 |
putLSI did not fail when lss_number is empty |
|
IJ26170 |
PVUSED FIELD ATTRIBUTE IS NOT VALID WITH LSPV (PADMIN) |
|
IJ27547 |
Rare LPM failure (hang) when using GZIP accelerator on P9 |
|
IJ28304 |
RAS fixes & improvements for dpcom |
|
IJ27528 |
RAS: Extend replicaSet repair to allow addition of known disks |
|
IJ27577 |
read() may return less bytes than specified (4*32) |
|
IJ27507 |
Refresh of the IKE group might cause IKE tunnel outage |
|
IJ27626 |
REORGVG FAILS AFTER DMP DEV CHANGE FROM FW-ASSISTED TO TRADION |
|
IJ27635 |
reorgvg system crash if concurrent VG is forced offline |
|
IJ27620 |
RESOLVING NESTED GROUPS MAKES TOO MANY QUERIES |
|
IJ27573 |
RESTORE USING MAP FILE MAY FAIL WITH RDX/DVD IF DISK NUMS DIFFER |
|
IJ27622 |
SECLDAPCLNTD HUNG JOBS AND MEMORY LEAK |
|
IJ27493 |
second inulag -D call has missing exit line |
|
IJ27442 |
segfault seen in cluster commands and vio_daemon |
|
IJ25379 |
Separate IPsec locks into different cache lines to improve perf |
|
IJ27424 |
shientdd device odm attribute correction |
|
IJ27625 |
SINGLEBYTE LOCALE DIFF -I REPORT UPPER&LOWER CHAR |
|
IJ28262 |
snap commands gives error in nfs |
|
IJ24490 |
SNAP -E MAY LOG LIVEDUMP MESSAGE IN AIX ERRLOG |
|
IJ28295 |
SoE fileset may get uninstalled when device is in use |
|
IJ28294 |
soestat -av displays wrong message for certain statistics |
|
IJ27575 |
Some math functions set ERANGE with infinity input |
|
IJ28277 |
splitvg on an asynchronous GLVM VG may fail with a core dump. |
|
IJ27487 |
srcloop got coredump @findEntry@AF38_24 |
|
IJ28564 |
SRIOV VF configuration failures with FW950 |
|
IJ29065 |
SSP POOLFS SERVER STOP MAY TAKE EXCESSIVE TIME |
|
IJ28269 |
STACK OVERFLOW IN OBJECTUPDATEHASHTABLE() |
|
IJ25175 |
STOP an START HB failed |
|
IJ27627 |
STREAMS ROUTINES MAY CONSUME ALL CPU RESOURCES AT INTMAX |
|
IJ27574 |
STRESSED PTHREAD_ONCE MIGHT RETURN BEFORE ONCE FUNC IS EXECUTED |
|
IJ29733 |
strndup coredump and memory corruption |
|
IJ23727 |
SYNCROOT: ERROR SYNCHRONIZING RPM ROOT FILES |
|
IJ26432 |
SYSTEM CAN CRASH IN V_CMEM_INIT_SG_LIST() ON AME ENABLED LPARS |
|
IJ27535 |
SYSTEM CAN HANG WITH CPUS SPINNING IN RSIMPLE_LOCK |
|
IJ27435 |
system crash @rrhba_init_adapter+000154 |
|
IJ28575 |
System crash after LKU with enabled critical sections. |
|
IJ27497 |
System crash during livedump and autofs unmount |
|
IJ27433 |
System crash in vNIC driver when accessing invalid lockword |
|
IJ27517 |
System crash possible during IPv6 interface assignment |
|
IJ23846 |
SYSTEM CRASH WHEN UNCONFIGURING A DEVICE WHILE RUNNING WLM |
|
IJ28265 |
System crash when VIOS renames a file in the pool. |
|
IJ17609 |
System hang in aso_sleep_update() |
|
IJ27440 |
System hangs with livedump with fwdump test. |
|
IJ27417 |
SYSTEM WILL CRASH ON A FIBRE CHANNEL LOGOUT |
|
IJ27494 |
TAKING MKSYSB WITH SNAPSHOTS MAY LEAVE A SNAPSHOT LV MOUNTED |
|
IJ27464 |
TCP CHECKSUM VALIDATION IS BROKEN IN IPREPORT |
|
IJ25284 |
TCP CONNECTIONS REMAIN IN LAST_ACK STATE |
|
IJ28270 |
TE LOGS RELATIVE FILE PATH INTO SYSLOG |
|
IJ26486 |
tmd dumps core when 'ike' command is used with 'ipaddr' option |
|
IJ27478 |
topasout -s coredump with topasrec cluster rec. |
|
IJ27732 |
truss cannot create subject process when some kernext are loaded |
|
IJ21826 |
TRUSTCHK : ADDING LIBRARIES WITH ONLY 64 OBJECTS FAILS |
|
IJ27479 |
trustchk errors for files owned by mcr.rte |
|
IJ27624 |
TRUSTCHK: UNABLE TO EXTRACT CERTIFICATE ID |
|
IJ27638 |
trusted installs of AIX software may hang during confirmation |
|
IJ27444 |
Typo in NVMe download microcode menu |
|
IJ27555 |
Unable to lower sidle_S3runq_mload tunable with schedo in SMT8 |
|
IJ28572 |
Unexpeced node expel behavior |
|
IJ27668 |
UPDATE ALTLIB SCRIPT TO ENSURE POSIX LC_COLLATION FOR REGEX |
|
IJ27504 |
Update node failed using viosupgrade tool |
|
IJ27420 |
UPGRADE TO VIOS 3.1.1.21 CAN CAUSE FAILURES IN VM REC MGR |
|
IJ27592 |
USB diagnostic displaying wrong menu. |
|
IJ27588 |
USB Diagnostics leaves the device in diagnose state |
|
IJ23963 |
vfcmap fails with "does not appear to be a valid FC port" |
|
IJ27462 |
VIOS may crash during validation |
|
IJ27558 |
VIOS vnicserver crash in tstart |
|
IJ24306 |
VIOS_VFC_HOST ERROR MAY OCCUR DURING LPM |
|
IJ27492 |
viosbr backup may fail if issued from HMC when file is "test" |
|
IJ24145 |
VIOSBR RESTORE FAIL FOR 2.X ATTR VALUES NOT COMPATIBLE WITH 3.1 |
|
IJ27418 |
VIOSERVICE CORE_DUMP IN VIOFREEOBJECTLIST |
|
IJ29732 |
vioservice dumps core |
|
IJ27495 |
viosupgrade fails to restore SEA |
|
IJ27512 |
VIOSUPGRADE RESTORE UNABLE COMPLETE DUE TO -G FILE COPY FAILURE |
|
IJ27473 |
vlan traffic stops when dynamically add/delete SEA trunk adap. |
|
IJ27463 |
VMRM VM MOVE MAY FAIL IF OVERCOMITTED ADAPTERS AND EXTRA ADAPTER |
|
IJ27454 |
vNIC client driver mbuf leak |
|
IJ29068 |
VNIC failover backing VF can get stuck in LINK DOWN state |
|
IJ27548 |
VPM throughput mode not working correctly in SMT8. |