PACKAGE: Update Release 2.2.6.41
IOSLEVEL: 2.2.6.41
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 2.2.6.41 |
AIX 7100-05-04 or 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 2.2.6.41
To take full advantage of all the functions available in the VIOS, it may be necessary to be at the latest system firmware level. If a system firmware update is necessary, it is recommended that the firmware be updated before you update the VIOS to Update Release 2.2.6.41.
Microcode or system firmware downloads for Power Systems
The VIOS Update Release 2.2.6.41 includes the IVM code, but it will not be enabled on HMC-managed systems. Update Release 2.2.6.41, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
Update Release 2.2.6.41 updates your VIOS partition to ioslevel 2.2.6.41. To determine if Update Release 2.2.6.41 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update Release 2.2.6.41 is installed, the command output is 2.2.6.41.
Please ensure that your rootvg contains at least 30 GB and that there is at least 4GB free space before you attempt to update to Update Release 2.2.6.41. Run the lsvg rootvg command, and then ensure there is enough free space.
Example:
$ lsvg rootvg VOLUME GROUP: rootvg VG IDENTIFIER: 00f6004600004c000000014306a3db3dVG STATE: active PP SIZE: 64 megabyte(s)VG PERMISSION: read/write TOTAL PPs: 511 (32704 megabytes)MAX LVs: 256 FREE PPs: 64 (4096 megabytes)
LVs: 14 USED PPs: 447 (28608 megabytes)OPEN LVs: 12 QUORUM: 2 (Enabled)TOTAL PVs: 1 VG DESCRIPTORS: 2STALE PVs: 0 STALE PPs: 0ACTIVE PVs: 1 AUTO ON: yesMAX PPs per VG: 32512 MAX PPs per PV: 1016 MAX PVs: 32LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: noHOT SPARE: no BB POLICY: relocatable PV RESTRICTION: none INFINITE RETRY: no
If you are planning to update a version of VIOS lower than 2.1, you must first migrate your VIOS to VIOS version 2.1.0 using the Migration DVD. After the VIOS is at version 2.1.0, the Update/Fixpack 2.2.6.10 must be applied to bring the VIOS to the latest Fix Pack VIOS 2.2.6.10 level. The Update Release 2.2.6.41 can then be applied to bring the VIOS to the latest level.
Note that with this Update Release 2.2.6.41, a single boot alternative to this multiple step process is available to NIM users. NIM users can update by creating a single, merged lpp_source that combines the contents of the Migration DVD with the contents of this Update Release 2.2.6.41.
A single, merged lpp_source is not supported for VIOS that uses SDDPCM. However, if you use SDDPCM, you can still enable a single boot update by using the alternate method described at the following location:
SDD and SDDPCM migration procedures when migrating VIOS from version 1.x to version 2.x
After the VIOS migration is complete, from 1.X to 2.X, you must set the Processor Folding, described here under "Migration DVD":
Instructions
to disable Processor Folding are detailed at the link below.
See the "Migration DVD" section:
Virtual I/O Server support for Power Systems
VIOS Update Release 2.2.6.41 may be applied directly to any VIOS that is at either level 2.2.6.0 or 2.2.6.10.
On a VIOS with a level between 2.2.1.1 and 2.2.5.x, a Single Step update procedure can be used to update to level 2.2.6.41.
Instructions: Single Step Update
To update to Update Release 2.2.6.41 from a level between 2.2.1.1 and 2.2.5.x in a single step, put the 2.2.6.10 updates in the same location as your 2.2.6.41 updates and do the update using the updateios command.
Warning: The update may fail if there is a loaded media repository.
To check for a loaded media repository, and then unload it, follow these steps.
1. To check for loaded images, run the following command:
$ lsvopt
The Media column lists any loaded media.
2. To unload media images, run the following commands on all Virtual Target Devices that have loaded images.
$ unloadopt -vtd <file-backed_virtual_optical_device >
3.
To verify
that all media are unloaded, run the following command again.
$ lsvopt
The command output should show No
Media for all VTDs.
The Virtual I/O Server (VIOS) Version 2.2.2.1 or later, supports rolling updates for SSP clusters. The VIOS can be updated to Update Release 2.2.6.41 using rolling updates.
Version Specific Instructions: Version 2.2.1.3 or earlier.
A cluster that is created and configured on a VIOS at version 2.2.1.3 or earlier must be migrated to version 2.2.1.4 or 2.2.1.5 prior to utilizing rolling updates. This allows the user to keep their shared storage pool devices.
Version Specific Instructions: Version 2.2.1.4 or later.
The rolling updates enhancement allows the user to apply Update Release 2.2.6.41 to the VIOS logical partitions in the cluster individually without causing an outage in the entire cluster. The updated VIOS logical partitions cannot use the new SSP capabilities until all VIOS logical partitions in the cluster are updated.
To upgrade the VIOS logical partitions to use the new SSP capabilities, ensure that the following conditions are met:
· All VIOS logical partitions must have VIOS Update Release version 2.2.1.4 or later installed.
· All VIOS logical partitions must be running. If any VIOS logical partition in the cluster is not running, the cluster cannot be upgraded to use the new SSP capabilities.
Instructions: Verify the cluster is running at the same level as your node.
1.
Run the
following command:
$ cluster -status -verbose
2. Check the Node Upgrade Status field, and you should see one of the following terms:
UP_LEVEL: This means that the software level of the logical partition is higher
than the software level the cluster is running at.
ON_LEVEL: This means the software level of the logical partition and the
cluster are the same.
There is now a method to verify the VIOS update files before installation. This process requires access to openssl by the 'padmin' User, which can be accomplished by creating a link.
Instructions: Verifying VIOS update files.
To verify the VIOS update files, follow these steps:
1. $ oem_setup_env
2.
Create
a link to openssl
# ln -s /usr/bin/openssl
/usr/ios/utils/openssl
3. Verify the link to openssl was created
# ls -alL /usr/bin/openssl /usr/ios/utils/openssl
4. Verify that both files display similar owner and size
5. # exit
Use one of the following methods to install the latest VIOS Service Release. As with all maintenance, you should create a VIOS backup before making changes.
If you are running a Shared Storage Pool configuration, you must follow the steps in Migrate Shared Storage Pool Configuration.
Note: While running 'updateios' in the following steps, you may see accessauth messages, but these messages can safely be ignored.
Version Specific Warning: Versions between 2.2.1.1 and 2.2.5.x.
You must put the 2.2.6.10 and 2.2.6.41 on the same location to apply updates in single step. The single step approach fixes an update problem with the builddate on bos.alt_disk_install.boot_images fileset.
Version Specific Warning: Version 2.2.2.1, 2.2.2.2, 2.2.2.3, or 2.2.3.1
You must run updateios command twice to get bos.alt_disk_install.boot_images fileset update problem fixed.
Run the following command after the step of "$ updateios –accept –install –dev <directory_name >" completes.
$ updateios –accept –dev <directory_name >
Depending on the VIOS level, one or more of the LPPs below may be reported as "Missing Requisites", and they may be ignored.
MISSING REQUISITES:
X11.loc.fr_FR.base.lib 4.3.0.0 # Base Level Fileset bos.INed 6.1.6.0 # Base Level Fileset bos.loc.pc.Ja_JP 6.1.0.0 # Base Level Fileset bos.loc.utf.EN_US 6.1.0.0 # Base Level Fileset bos.mls.rte 6.1.x.x # Base Level Fileset
Warning: If VIOS rules have been deployed.
When the VIOS is the updated, some of the current rules may revert to the
system defaults. Additionally, those changes may have been applied to the
system.
If you notice this issue, the default rules can be re-deployed and captured to
current rules by running the commands below.
$ rules
-o deploy -d
$ rules -o capture
Note: This will overwrite any customized rules in the current rules file.
Applying Updates
Warning:
If the target node to be updated is part of a redundant VIOS pair, the VIOS partner node must be fully operational before beginning to update the target node.
Note:
For VIOS nodes that are part of an SSP cluster, the partner node must be shown in 'cluster -status ' output as having a cluster status of OK and a pool status of OK. If the target node is updated before its VIOS partner is fully operational, client LPARs may crash.
Note: The current level of the VIOS must be 2.2.2.1 or later if you use the Share Storage Pool.
Instructions: Applying updates to a VIOS.
2. Using ftp, transfer the update file(s) to the directory you created.
3. To apply updates from a remotely mounted file system, and the remote file system is to be mounted read-only, follow the steps:
$ shutdown -restart
Note: If shutdown –restart command failed, run swrole –PAdmin in order for padmin to set authorization and establish access to the shutdown command properly.
$ clstartstop -start -n <cluster_name > -m <hostname >
$ ioslevel
Instructions: Checking for an incomplete installation caused by a loaded media repository.
After installing an Update Release, you can use this method to determine if you have encountered the problem of a loaded media library.
Check the Media
Repository by running this command:
$ lsrep
If the command reports: "Unable to retrieve repository date due to incomplete repository structure," then you have likely encountered this problem during the installation. The media images have not been lost and are still present in the file system of the virtual media library.
Running the lsvopt command should show the media images.
Instructions: Recovering from an incomplete installation caused by a loaded media repository.
To recover from this type of installation failure, unload any media repository images, and then reinstall the ios.cli.rte package. Follow these steps:
1. Unload any media images
$ unloadopt -vtd <file-backed_virtual_optical_device>
2. Reinstall the ios.cli.rte fileset by running the following commands.
To escape the
restricted shell:
$ oem_setup_env
To install the failed fileset:
# installp –Or –agX ios.cli.rte –d <device/directory >
To return to the restricted
shell:
# exit
3. Restart the VIOS.
$ shutdown –restart
4. Verify that the Media Repository is operational by running this command:
$ lsrep
For additional details, including known capabilities, limitations, and additional install considerations, as well as some additional instructions, please reference the readme for 2.2.6.10 located here.
This version will include all fixes found in all previous 2.2.6.X releases. The fixes for the previous release can be found here.
|
APAR |
Description |
|
GROWING SSP DISKS BY A LARGE AMOUNT MAY RESULT IN
I/O FAILURE |
|
|
IJ06644 |
ADAPTER FIRMWARE UPGRADE COULD FAIL W/ FCA_ERR6
AND SENSE 518 |
|
IJ06887 |
devrsrv only looks in CuAt for reserve_policy |
|
IJ07424 |
VIOS SSP I/O CAN SLOW AFTER ADDING/REMOVING
UNBALANCED FAILGRP |
|
IJ07457 |
VIOS SSP CAN CRASH IF MEMTRACEDETAIL SET FOR
POOL.FIO COMPONEN |
|
IJ07818 |
MKSYSB RESTORE FAILS TO CHECK IF SOURCE DISK IS
SAME |
|
IJ07829 |
SRIOV adapter Transmit stalls |
|
IJ07859 |
HOST COULD LOG FCA_ERR2 WITH SENSE DATA 0DB8 AFTER
FABRIC EVENT |
|
IJ07904 |
VIOSBR -AUTOBACKUP FAILS TO CAPTURE BACKUP FOR
NON-SSP VIOS |
|
IJ07938 |
LDAP CLIENT SENDS REPEATED REQUEST TO UPDATE
ATTRIBUTE |
|
IJ07954 |
snmpdv3 unable to retrieve smux
peer information |
|
IJ07960 |
SDK 7.0.0 32-bit SR10 FP30 - 18_03 |
|
IJ07961 |
SDK 7.0.0 64-bit SR10 FP30 - 18_03 |
|
IJ08086 |
NMON COREDUMPS WHEN # OF SEACLIENTS INCREASE IN
2ND DAY. |
|
IJ08222 |
RULES COMMAND MAY FAIL IF THERE IS A VG ON HDISKPOWER
DEVICE |
|
IJ08380 |
NMON COREDUMPS IN FIND_SEA_CLIENTS IF #OF
SEACLIENTS IS HIGH |
|
IJ08815 |
CERTAIN SEQUENCE OF LINK UP / DOWN EVENTS COULD
RESULT IN HANG |
|
IJ08856 |
mkuser not working when TLP=ON |
|
IJ08982 |
Release the XTBUF extra hold if not used in last 2
hours. |
|
IJ09539 |
PART COMMAND IS SHOWING INCORRECT STAT FOR NPIV
CLIENTS |
|
IJ09619 |
A potential security issue exists |
|
IJ09707 |
upgrade of the nodes takes cluster services down |
|
IJ09708 |
coredump in clconfd when running SSP tiercreate |
|
IJ09709 |
viosupgrade tool failed to trigger install |
|
IJ09710 |
Potential data miscompare
on NVMe and other high B/W adapters |
|
IJ09711 |
NVMe support refresh |
|
IJ09732 |
vioserver coredumped |
|
IJ09733 |
Node added to a cluster, but cluster -status says
down. |
|
IJ09734 |
move lu command hung |
|
IJ10105 |
SSP VIOS crash in ngdisk_finish_iodone |
|
IJ10133 |
Crash in algorithmLeastSimilarPath() during dump |
|
IJ10134 |
A potential security issue exists |
|
IJ10297 |
subsequent viosupgrade
fails after the first run |
|
IJ10298 |
FW dump is incorrect for lnc2entdd driver |
|
IJ10299 |
Further extend LUN reset retries before disk
failure |
|
IJ10300 |
Avoid flash memory writes for adapter commands |
|
IJ10413 |
ssp cluster -status command is hanging |
|
IJ10415 |
Get unwanted messages from cluster related
commands. |
|
IJ10538 |
UNDER CERTAIN CIRCUMSTANCE SSP ROLLING UPGRADE MAY
FAIL |
|
IJ10548 |
cluster commands are hung after network disruption |
|
IJ10549 |
Adding support for NVMe
disk in viosupgrade tool. |
|
IJ10550 |
viosbr restore hungs if triggered via viosupgrade tool. |
|
IJ10614 |
CLFFDC TRIGGERED ON REBOOT |
|
IJ10696 |
viosbr fails if previous viosbr is terminated |
|
IJ10697 |
viosupgrade fails to restore SEA for NIM altdisk
installations |
|
IJ10804 |
Crash when many processes use 64K text pages for |
|
IJ10805 |
FC5270, FC5708 may crash in msnent_rx_handler() |
|
IJ10844 |
EXTENDVG IN PADMIN RETURNS USAGE WITH DISK
"DISK/SAS/SISARRAY" |
|
IJ10890 |
RULES SETTING FOR NUM_CMD_ELEMS ON 16G FC ADAPTER
INCORRECT |
|
IJ11000 |
XORG SECURITY VULNERABILITY |
|
IJ11198 |
Memory leak in pth_get_tls() |
|
IJ11224 |
SDK 7.0.0 32-bit SR10 FP35 - 18_04 |
|
IJ11225 |
SDK 7.0.0 64-bit SR10 FP35 - 18_04 |
|
IJ11648 |
SECLDAPCLNTD HAS UNSUITABLE STDIN IN SRC
CONFIGURATION |
|
IJ11649 |
SYSCK DOES NOT TELL WHICH ENTRY IS AT FAULT IN
SOME CASES |
|
IJ11650 |
SECLDAPCLNTD CORE IN CACHE FUNCTIONS |
|
IJ11651 |
CRON LOOPS LOGGING ERROR MESSAGES FOR
"READ" |
|
IJ11652 |
LISTIO64 RETURN 0 WITH ERRNO EIO |
|
IJ11653 |
vi truncates very long line |
|
IJ11654 |
chuser is appending groups instead of overwrite |
|
IJ11655 |
Error reading stanza after system reboot |
|
IJ11656 |
LSUSER ALL LISTS USER TWICE |
|
IJ11657 |
UUID_CREATE RETURNS DUPLICATE UUIDS DURING AIX
TIME ADJUSTMENT |
|
IJ11659 |
Backporting fix for malloc pool core dump |
|
IJ11660 |
fmemopen followed by getline and feof
doesn't work properly |
|
IJ11661 |
Pool allocator references memory outside heap |
|
IJ11662 |
SCHEDO -P -O WAITLOCK_POLICY=1,2 OR 3 FAILS |
|
IJ11663 |
DBX SHOWS WARNING EVEN WHEN EXE HASN`T CHANGED |
|
IJ11664 |
fcntl() with socket does not return correct errno
in unix mode |
|
IJ11665 |
creat() doesn't return -1 with trailing slash |
|
IJ11666 |
Improved accuracy of atime,
mtime, and ctime in unix mode |
|
IJ11667 |
link() doesn't set correct errno |
|
IJ11668 |
rename() did not set correct errno |
|
IJ11669 |
readlink() does not update atime of a symlink |
|
IJ11670 |
fcntl() did not return expected flags |
|
IJ11671 |
System crash@unborrow_counts
while ASO optimizes |
|
IJ11672 |
System crash in swapper@mrq_next_wrap |
|
IJ11673 |
entstat hung-adapter reset, entstat in parallel |
|
IJ11675 |
P9 VPM fold threshold |
|
IJ11676 |
mpool recursive read lock kernel hang |
|
IJ11678 |
Illegal Trap i_eoi+0000 |
|
IJ11681 |
Extra double quote in chiscsi
help statement |
|
IJ11682 |
CX4/CX5 EEH injection during fw
update fails / does not recover |
|
IJ11683 |
Nim installs takes long time and tasks in system are slow |
|
IJ11684 |
Parallel format of 10 disks fails with segfault of uformat. |
|
IJ11685 |
Traces insufficient for some error paths |
|
IJ11686 |
Error messages for SSP API is not proper when
invalid Cluster |
|
IJ11687 |
shientdd device driver recovery state machine fix |
|
IJ11688 |
FC EN0S EN0T EN0U EN0V EN0W EN0X diag hang fix in APAR IJ11143 |
|
IJ11692 |
AFTER RPM.RTE V4 UPDATE SAVEWPAR OPERATION HANGS
INDEFINITELY |
|
IJ11694 |
NMON IS SHOWING JUNK MESSAGES FOR SOME FC ADAPTERS |
|
IJ11696 |
LDAP OPERATIONS HANG WITH CIRCULARLY DEFINED
NETGROUPS |
|
IJ11697 |
NMON IS DELAYING ITS INTERVAL WHEN -S VALUE IS
HIGH |
|
IJ11698 |
IFCONFIG MAY SHOW FLAGS WITHOUT IFF_DEVHEALTH |
|
IJ11699 |
XMTOPAS FILES NOT ROTATING AS FTELL IS FAILING |
|
IJ11700 |
perfstat_bridgedadapters() sets errno to 0 if 1st
param is inva |
|
IJ11701 |
SNMPDV3NE CORE DUMPS |
|
IJ11702 |
NIM SYNC OPERATION DISPLAYS NIMSTATE: REQUEST
DENIED MESSAGE |
|
IJ11703 |
NAMED LOGS TOO MANY MESSAGES TO THE LOGGING
CHANNEL |
|
IJ11704 |
ROOTVG DISK ATTRIBUTES RESET TO DEFAULT AFTER
MKSYSB RESTORE |
|
IJ11705 |
Icon Name of ICON Editor is garbage characters |
|
IJ11706 |
Receive unexpected keysym
data with Greek Lock state |
|
IJ11707 |
Very long lun names
prevent cfgmgr from configuring the lun |
|
IJ11710 |
Transmit software queue timer not running |
|
IJ11711 |
Transmit software queue timer not running |
|
IJ11712 |
Successful error recovery may lead to DEAD state |
|
IJ11713 |
Running Diagnostic test fails when port connected
to network. |
|
IJ11714 |
Transmit software queue timer not running |
|
IJ11718 |
Fix some POF related problems |
|
IJ11719 |
Synchronize POF kproc
creation and initialization |
|
IJ11721 |
CRASH IN JFS2 IACTIVATE DURING HIGH INODE USAGE |
|
IJ11722 |
RAS ENHANCEMENT FOR IPUT CRASH |
|
IJ11723 |
The same trace hook ID is used for multiple events |
|
IJ11802 |
ATTRIBUTES SET BY RULES COMMAND NOT HONORED BY OS |
|
IJ12062 |
entstat shows the link UP when the cable is pulled on CX4 |
|
IJ12063 |
EEH logged when removing wrap plug. |
|
IJ12064 |
vios busy error may be seen following some cluster operations |
|
IJ12065 |
vnicserver produces a fatal error during logical link down |
|
IJ12068 |
entstat output displays incorrect Port VLAN value |
|
IJ12070 |
redzoned memory read during unmount |
|
IJ12071 |
Fsck displays invalid aggregate inode number. |
|
IJ12073 |
Drop ARP hold queue packets if interface does not
match |
|
IJ12074 |
Additional privileges added to ike
and ikedb commands for RBAC |
|
IJ12075 |
Update bos.alt_disk_install.boot_images |
|
IJ12143 |
SEA PLSO_BRIDGE=YES LARGE_RECEIVE PACKET
CORRUPTION |
|
IJ12412 |
pci -tm KDB subcommand disrupts system state |
|
IJ12414 |
devices.ethernet.lnc.rte (lncentdd) driver may crash |
|
IJ12415 |
A potential security issue exists |
|
IJ12560 |
Incorrect clear queue behavior for some q_err bit values |
|
IJ12665 |
SPECULATIVE EXECUTION PROBLEM IN THE MELLANOX
DRIVER |
|
IJ12695 |
LU -CREATE FAILS TO CREATE VTD MAPPING WITH
REL_PORT_ID ERROR |
|
IJ12746 |
viosbr fails to copy in mounted path, if cmd called
remotely. |
|
IJ12748 |
cq_create doesn't unmap DMA on failure. |
|
IJ12749 |
Reservation conflict on ioctl |
|
IJ12750 |
Y4 Crypto diagnostics reports software error when
device busy |
|
IJ12752 |
Access to bad buffer causes new j2 traces to
sometimes crash. |
|
IJ12861 |
lsnports tports value may change unexpectedly on VIOS |
|
IJ12862 |
Live dump call on
Ethernet adapter may lead to AIX system crash |
|
IJ12973 |
Enhance FFDC tracing for NPIV host driver |
|
IJ12974 |
Error reported for DLPAR vNIC |
|
IJ12975 |
NVMe Inconsistent lscfg output before & after
download microcode |
|
IJ12976 |
CONFIG TIMEOUT OF 0 DOES NOT WORK AS DOCUMENTED |
|
IJ12977 |
BOOTPKG DOES NOT DISPLAY AN ERROR MESSAGE WHEN
/TMP IS FULL |
|
IJ12978 |
A potential security issue exists |
|
IJ12988 |
Disconnecting USB3 causes crash in xhci_offlevel_iodone |
|
IJ13001 |
SEA sharing mode RARP problem |
|
IJ13151 |
ldd fails after upgrade to AIX 7.2 |
|
IJ13213 |
unknown subhook 007E in
the SEA component trace |
|
IJ13226 |
NETSTAT FAILS WITH SYMBOL RESOLUTION ERROR |
|
IJ13251 |
Transmit software queue timer not running |
|
IJ13293 |
creating ibX interface
and ibstat command fail |
|
IJ13575 |
viosbr backup does not collect artex file. |
|
IJ13591 |
UPGRADE TO 2.2.6.30 INCOMPLETE WITH SSP UP_LEVEL
WHEN VIOSECURE |
|
IJ13627 |
SHIENT_SW_ERR has incorrect error type |
|
IJ13629 |
ifconfig may hang on shientdd
driver instance |
|
IJ13630 |
kdb user displays wrong addresses |
|
IJ13896 |
Improve "dump cache all" to reduce
number of objects we dump |
|
IJ13897 |
pool lsattr was not
allowing long tier names |
|
IJ13967 |
Disk errchecklvl >= 7
causes assert crash in scsidisk_start() |
|
IJ13968 |
SYSTEM CRASH IN V_RELFRAME()
WHEN NFS FILESYSTEM GETS FULL |
|
IJ14085 |
Update Diagnostics VRMF |
|
IJ14086 |
clcomd not using all interfaces for communication |
|
IJ14188 |
Update FLADJ register default on USB3 PCIe Adapter |
|
IJ14346 |
Incorrect format for print of 'response' field in
KDB 'svva' |
|
IJ14348 |
NFS4_REMOVE: AIX NFS CLIENT MAY LOOP WITH
NFS4ERR-FILE-OPEN |
|
IJ14349 |
Fix DR event handler code to avoid system crash |
|
IJ14350 |
lsdev doesnt show any vnic
adapters on vios. |
|
IJ14352 |
Network not working after viosupgrade |
|
IJ14413 |
Possible system crash during EEH scenario |
|
IJ14415 |
Client hang in tmTryIndentify() retry
loop for more than 10 hrs |
|
IJ14447 |
Multiple dynamic filters seen for IKEv2 tunnels |
|
IJ14682 |
DATA COLLECTION PROCESS SLOWS POOL RECOVERY DURING
NETWK OUTAGE |
|
IJ14749 |
NEW METHOD TO HANDLE ASYMMETRIC NETWORK OUTAGE OF
SSP |
|
IJ14844 |
POOL STUCK WHILE TRYING TO UNMOUNT |
|
IJ14932 |
VNIC interfaces dropping large numbers of receive packets |
|
IJ14933 |
system may hang during AIX build installation |
|
IJ14934 |
viosbr command shows failed but cluster restored |
|
IJ14986 |
Diagnostics MPIO task core dumps |
|
IJ15111 |
VIOS becomes extremely unresponsive |
|
IJ15314 |
remove PowerSC filesets from VIOS |
|
IJ15344 |
A potential security issue exists |
|
IJ15348 |
vio_daemon core dumps when sspcaching is enabled. |
|
IJ15377 |
vnic_server is not returning all of the buffers on LINK
DOWN |
|
IJ15412 |
hxedapl stops running due to resource allocation failed |
|
IJ15415 |
Packet loss in devices with feature code ENOS and
EN0W |
|
IJ15609 |
Update bos.alt_disk_install.boot_images |
|
IJ15615 |
JAPANESE ERA CHANGE FROM HEISEI TO REIWA |
|
IJ15619 |
rda seg fault on SEAs |
|
IJ15631 |
Invalid opcode error logged by SAS adapter. |
|
IJ15651 |
SSP LU MAP FAILS WITH CANNOT ACCESS A DEVICE |
|
IJ15760 |
INCREASE TCP_MAXQUEUELEN DEFAULT VALUE TO STOP
CONNECTION LOSS |