PACKAGE: Update Release 3.1.0.30
IOSLEVEL: 3.1.0.30
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 3.1.0.30 |
AIX 7200-03-04 |
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.30
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.30.
Microcode or system firmware downloads for Power Systems
Update Release 3.1.0.30 updates your VIOS partition to ioslevel 3.1.0.30. To determine if Update Release 3.1.0.30 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update Release
3.1.0.30 is installed, the command output is 3.1.0.30.
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.30. 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.30 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.30 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.30
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.30 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 |
|
IJ16736 |
WITH IV92991
INSTALLED, FSCK MAY FAIL IN "BMAP: INCORRECT SIZE" |
|
IJ06738 |
crash in hd_extend()
during reorgvg/migratepv/migratelp |
|
IJ12342 |
CRASH IN TXLOG AFTER A
FORCE UNMOUNT IN JFS2 FILE SYSTEM |
|
IJ13255 |
BACKUPIOS MAY FAIL
WITHOUT ANY ERROR MESSAGE |
|
IJ14398 |
NETWORK PERFORMANCE
DEGRADED WITH MORE IPSEC FILTER RULES |
|
IJ14421 |
PROGRAMS USING
MALLINFO_HEAP() CAN CORE DUMP WITH SIGSEGV |
|
IJ14500 |
NIMADM ERROR RPM: NO
ARGUMENTS GIVEN FOR QUERY |
|
IJ14586 |
MBUF MEMORY LEAK IN
VIOENTDD |
|
IJ14587 |
PLSO ENABLED SOCKETS
DROP PLATFORM LARGE SEND PACKET AFTER LPM |
|
IJ14589 |
SECLDAPCLNTD HEARTBEAT
SEARCH FILTER PERFORMANCE ISSUE |
|
IJ15075 |
CORE IN SECLDAPCLNTD
CACHE CODE |
|
IJ15382 |
RMUSER FROM PADMIN
DOES NOT REMOVE ENTRY FROM /ETC/SECURITY/PASS |
|
IJ15486 |
Network not working
after viosupgrade |
|
IJ15502 |
FCSTAT -CLIENT MAY
REPORT CLIENT LPAR STAT UNDER THE WRONG HBA |
|
IJ15614 |
JAPANESE ERA CHANGE
FROM HEISEI TO REIWA |
|
IJ15657 |
SYSTEM CRASH DUE TO
IMPROPER T_LOCKCOUNT |
|
IJ15765 |
CFGECH ALWAYS SET
BACKUP INTERFACE'S MTU AS 1500 IN AIX 7.2 |
|
IJ15798 |
SIGNAL HANDLER NOT
CLEARED AFTER EXEC() |
|
IJ16187 |
FCSTAT REPORTS 0 FOR
LINK SPEED WITH NPIV BACKED 32GB SPEED ADAP |
|
IJ16303 |
AUTOFSMOUNT DUMPS CORE
WHEN LANG IS NOT "C" |
|
IJ16393 |
VIOSBR METADATA
BACKWARD COMATIBITLY FROM 2.X TO 3.1 IO_DMA |
|
IJ16394 |
vios_recovery not resetting when vm table empty |
|
IJ16521 |
SSP snap or ffdc can take longer than needed |
|
IJ16522 |
MFS pool start can
timeout due to large IOPGMap cache |
|
IJ16562 |
Fix various Platform
Large Send related issues |
|
IJ16586 |
netstat prints some
messages incorrectly |
|
IJ16690 |
TRUSTCHK FAILS WHEN
ADDING FILES >512M |
|
IJ16699 |
AFTER SPOT CREATION
LPPCHK FINDS INCONSISTENCY WITH RC.BOOT FILE |
|
IJ16744 |
VIOS cmnd failing as vios in
VIOS_DB_RECOVERING |
|
IJ16745 |
work around open hang |
|
IJ16746 |
stopvm
returning 138 even in local mode |
|
IJ16854 |
LKU operation may fail
with vios busy error. |
|
IJ16925 |
SHIENT_SW_ERR AND
LDMP_COMPLETE ERROR IN ERRPT |
|
IJ16973 |
Add TU lib update for
FCs adapters |
|
IJ17022 |
After migration VM
going to stopped state |
|
IJ17023 |
HM not active after vios reboot |
|
IJ17024 |
Invoke vioPoolSafe()
in vioGetPoolSpaceInfo |
|
IJ17065 |
NTPV3 MARCH 2019
SECURITY VULNERABILITIES |
|
IJ17067 |
Unable to perform
DLPAR operations |
|
IJ17068 |
crash at
rmcpu_doit+000AF4 |
|
IJ17140 |
VIOS CRASHED IN ngdisk_other_node_down |
|
IJ17157 |
ASSERT IN ADAPTER
DRIVER DURING ERROR RECOVERY |
|
IJ17200 |
LSGROUP WITH -C AND -A
GIVES IMPROPERLY FORMATTED OUTPUT |
|
IJ17233 |
HANG OR CORE WITH LDAP
+ NETGROUPS |
|
IJ17239 |
SNAP ON VIOS IS NOT
COLLECTING VNIC DATA |
|
IJ17299 |
LKU FAILING DUE TO TCP
HANG |
|
IJ17326 |
RMTCPIP -ALL REMOVES
LOCALHOST ADDRESS FROM HOSTS FILE |
|
IJ17361 |
IP_INPUT DROPPING PLSO
PACKETS |
|
IJ17487 |
HANG IN MULTITHREADED
APPS WITH FORK() AND LOAD |
|
IJ17493 |
TELNET USER ATTRIBUTE
SHOULD BE REMOVED. |
|
IJ17505 |
IJ17505 - Live Update
fails when applying 7200-03-03 / IJ09625 |
|
IJ17555 |
VM migration fails if
SSP is down on source vios |
|
IJ17556 |
VIOS not going to
LOCAL DB mode |
|
IJ17637 |
HM daemon active but hmhactive not showing as active |
|
IJ17642 |
ADAPTER GET STATISTICS
PROGRAMS MAY FAIL DUE TO IOCTL ERROR |
|
IJ17643 |
URH-END-IO-Handler
consuming CPU with Flashcache not configured |
|
IJ17766 |
ldedit
missing option list in the usage output |
|
IJ18107 |
SNA PACKETS ARE
DROPPED UNDER VLAN ENV |
|
IJ18149 |
Mutiple
IPsec IKE tunnels with IKEv2 PSK cannot be setup |
|
IJ18150 |
IKEV2D COREDUMP IN
PROCESS_MSG |
|
IJ18151 |
ikev2d leaks memory
during rekey |
|
IJ18152 |
IPsec tmd daemon enters inconsistent state |
|
IJ18210 |
WITH SEA USING
MLXCENTDD WITH DEFAULT FLIP_N_RUN=NO DEGRADES PER |
|
IJ18255 |
Deadlock in threaded
program between unload and fork |
|
IJ18263 |
SECLDAPCLNTD
CORRUPTION/CORES WITH MALLOCDEBUG |
|
IJ18331 |
ISSUES WHEN TRYING TO
START PERSISTENT NMON VIA "SMITTY TOPAS" |
|
IJ18385 |
SYSTEM CRASH IN
NFS4_GET_LEASE_TIME() |
|
IJ18445 |
VIRTUAL ADAPTER
CONFIGURED BEFORE SR ADAPTERS AFTER VIOSUPGRADE |
|
IJ18515 |
SPLAT DUMPING CORE IN
0XE8A8 |
|
IJ18524 |
Correct the TLSv1.1
flag name in ftpd.cnf |
|
IJ18588 |
MEMORY LEAK IN LIBSM.A
GET_VGID_FROM_NAME |
|
IJ18684 |
MAXEXPIRED DOESN'T
WORK FOR LDAP USERS |
|
IJ18786 |
Update bos.alt_disk_install.boot_images |
|
IJ18827 |
j2gt won't delete
recently added files right away |
|
IJ18870 |
AIXIF_ARP_DUP_ADDR
ERRORS IN ERRPT DURING LIVE UPDATE |
|
IJ18871 |
ADAPTER OPEN MIGHT
HANG UNDER CERTAIN ERROR CONDITION |
|
IJ18872 |
HANG USING FAILOVER
ALGORITHM WHEN ADAPTER IS OUT OF CMD_ELEMS. |
|
IJ18873 |
ETHERNET ADAPTER
"MINIMUM MEDIUM BUFFERS" ATTRIBUTE NOT IN SMIT |
|
IJ18874 |
ACCESS TO FABRIC
NAMESERVER COULD BE IMPARED IF LOGGED OUT |
|
IJ18875 |
CRASH IN
NPIV_FAIL_COMMAND AFTER DYNAMIC TRACKING EVENT |
|
IJ18876 |
System crash/hang in npiv_stop_target_port |
|
IJ18877 |
VIOS crashes during vhost adapter config in target_cdt_add |
|
IJ18878 |
CLEARACA DURING
ADAPTER RESET NOT RETURNED TO DISK DRIVER |
|
IJ18879 |
Very long lun names prevent cfgmgr from
configuring the lun |
|
IJ18880 |
Adapter performs livedump on adapter parity error |
|
IJ18881 |
Platform Large send
statistics are not reset after entstat -r |
|
IJ18882 |
Optimize thick lu create and extend |
|
IJ18884 |
Enforce 1GB unmap limit per Write-same SCSI cmd |
|
IJ18885 |
mkiscsi
-f option does not work with CHAP name |
|
IJ18886 |
Not able to boot from
iSCSI disk |
|
IJ18887 |
PCIDMA error with NVMe adapter |
|
IJ18889 |
DMA_ERR errlog entries, adapters still configure |
|
IJ18891 |
FC5899 RX may not work
properly when flow_ctrl was set to "no" |
|
IJ18893 |
INFO "vhost" error logged in VIOS paritions
after LPM |
|
IJ18899 |
vioservice dumps core @ malloc_y |
|
IJ18901 |
Correct use of ndd_parent_nddp pointer by SEA & Etherchannel |
|
IJ18905 |
System may crash
during error scenarios |
|
IJ18908 |
Adapter may not
recover from EEH resulting in IO Error |
|
IJ18910 |
Improve identification
of iSCSI disks |
|
IJ18912 |
System may crash
during certain error conditions |
|
IJ18915 |
GetLSI
might not be able to get data for some XIV disks |
|
IJ18919 |
fscsi
devices are not populated in CMDB after dlpar add. |
|
IJ18921 |
change vSCSI client rw_timeout value
to 45 seconds |
|
IJ18925 |
Machine may hang
during controller failover on storage |
|
IJ18927 |
find_devices did not fail when fc port disabled |
|
IJ18929 |
Permanent EEH on
FC5899 after EEH gets injected |
|
IJ18931 |
Etherchannel backup ports not detached during error cleannup |
|
IJ18933 |
User mode vrtent KDB displays incorrect dev data |
|
IJ18935 |
IP interface down when
VNIC client added to shared memory LPAR |
|
IJ18936 |
amount of memory is
calculated incorrectly |
|
IJ18938 |
LPM validation fails
if vios has alredy 64 lpars on same FC port |
|
IJ18940 |
RNID ELS Response
Payload returns wrong size |
|
IJ18942 |
IO may fail during EEH
error conditions. |
|
IJ18945 |
Display transceiver
connection speed |
|
IJ18947 |
IO may fail during EEH
error conditions |
|
IJ18950 |
vioentdd
not restoring ndd_physaddr during close |
|
IJ18951 |
16MB size IO hang |
|
IJ18952 |
Incorrect resid value reported to IBMi
client |
|
IJ18954 |
LDAP CACHE MAY NOT
WORK DUE TO CASE SENSITIVITY |
|
IJ18955 |
LDAP LOGIN ALLOWED
WITH BAD PASSWORD |
|
IJ18956 |
EXTRA WAIT TIME AT THE
END OF WLMSTAT |
|
IJ18957 |
SYSTEM CRASH IN
TSTART_MIGRATE() |
|
IJ18958 |
CHUSER DOES NOT REPORT
ERROR ON FAILURE TO CHANGE LDAP USER |
|
IJ18959 |
REPLACEPV FAILS WHEN
PP SIZE OF A VG IS GREATER THAN 1024MB |
|
IJ18960 |
SYSTEM WITH LOW MEMORY
CAN CRASH IN LIO_LISTIO64() |
|
IJ18961 |
fsck
-n on large corrupt directory inode may hang |
|
IJ18962 |
ff USAGE message needs
to be improved |
|
IJ18963 |
Segmentation fault in srcmstr |
|
IJ18964 |
csum
failing on file system that doesn't support shmat() |
|
IJ18965 |
ld: INTERNAL ERROR when
linking large module with -bnosymbolic |
|
IJ18966 |
ls -s doesn't use 512 byte block while writing |
|
IJ18967 |
head -n not positioned
file offset properly |
|
IJ18968 |
locale -ck doesn't
process the command line operands |
|
IJ18970 |
Hard-coded messages in
csum |
|
IJ18972 |
Shell exits when fc
command fails |
|
IJ18974 |
pax -r -w usage
correction |
|
IJ18976 |
string length cannot
be greater than 4096 using -n |
|
IJ18978 |
locale -k LC_CTYPE
gives same value |
|
IJ18980 |
RPM SYMLINKS MAY BE
DELETED DURING INSTALL ON WPARS |
|
IJ18982 |
Unable to create j2
filesystem on a super strict mirrorpool |
|
IJ18989 |
POOLFS STUCK STARTING
NEW SERVERS AFTER CHALLENGE DISK ERRORS |
|
IJ18993 |
vio_daemon coredump @unnamed block in getColumnDesciption |
|
IJ18995 |
During a firmware
update, the system dropped to KDB. |
|
IJ18998 |
VLAN ACL status in VF
is not clear |
|
IJ18999 |
cluster -create can
fail with viosecure high |
|
IJ19008 |
TRACE CHANGES NEEDED
TO H_SEND_LOGICAL_LAN() FOR PERF TOOLS |
|
IJ19009 |
FAILURE MOUNTING 3RD
PARTY FILE SYSTEMS LIKE VXFS |
|
IJ19011 |
possible deadlock
between soshutdown and soreceive |
|
IJ19012 |
Rare crash when
removing cpus or turning off SMT with trace on |
|
IJ19014 |
System crash during ewlm deactive_localresourcemg |
|
IJ19015 |
A potential security
issue exists |
|
IJ19016 |
Potential performance
degradation migrating to P9 |
|
IJ19018 |
mv is unable to
duplicate owner and mode after move |
|
IJ19021 |
After using gencore, the target process can hang. |
|
IJ19022 |
j2_force_unmap can
crash when force unmount a mapped file |
|
IJ19023 |
Crash clearing a
threads eventlist without serialization. |
|
IJ19024 |
64-bit program fails
with SIGILL when making system call |
|
IJ19025 |
AIX lpar crashed at net_free |
|
IJ19026 |
modify krlock_enabled default value |
|
IJ19027 |
PASSWORD CHANGE MAY
CORE FOR USER |
|
IJ19028 |
MULTIBOS/ALT_DISK
UPGRADE TO 7200-03 MAKE PRIOR LEVEL UNBOOTAB |
|
IJ19029 |
ALT_DISK FAILURE:
/USR/SBIN/ALT_DISK_COPY[1461]: -M: NOT FOUND |
|
IJ19031 |
adding bos.xerces to NIM 6.1 lpp_sources |
|
IJ19096 |
SET_ADAPTER FAILS IF
THERE IS A BAD FC PORT ON SYSTEM |
|
IJ19178 |
FTP -S SOMETIMES DOES
NOT ENCRYPT DATA CHANNEL |
|
IJ19179 |
VIO SERVER CRASH IN
INSERT_LARGESEND_OPTION - MBUF NOT PINNED |
|
IJ19180 |
FILE TRANSFER WITH
TFTP PRODUCES INCORRECT OUTPUT |
|
IJ19182 |
SYSTEM CRASH IN PFFINDTYPE() IN THE INTERRUPT CONTEXT |
|
IJ19183 |
WPAR ODM ONLY SAVED
WHEN SHUTDOWN CLEANLY |
|
IJ19184 |
2.2.6.301 UPDATE OF
IOS.ARTEX_PROFILE.RTE LSATTR ERROR DISPLAYED |
|
IJ19185 |
CAA CLUSTER FAILS TO
JOIN DUE TO SECURITY ISSUES |
|
IJ19186 |
topas/nmon is delaying due to unknown lv's
present in CuAt |
|
IJ19187 |
ASSERT IN NFSV4 DUE TO
ERRONOUS RETURN CODE |
|
IJ19188 |
CAA: CLCONFD CORE
DUMP. |
|
IJ19189 |
ISILON .SNAPSHOT FILES MAY NOT BE VISIBLE ON AIX CLIENT |
|
IJ19190 |
DTTERM RESIZE DOES NOT
AFFECT COLUMNS |
|
IJ19191 |
SYMBOLIC LINK NOT
REMOVED FROM MOUNTED SHARES LIST AFTER UNMOUN |
|
IJ19192 |
AIX logo doesn't show
up on CDE login screen |
|
IJ19195 |
ike cmd=list
db shows incorrect IKE version and Remote ID |
|
IJ19196 |
Redundant tunnel
entries for IKEv1 due to successive activates |
|
IJ19199 |
Machine crash at
queue_msg_v6 |
|
IJ19203 |
unable to create test
notification from IVM |
|
IJ19204 |
ikedb
gives wrong error message for IPSec_KeyOverlap |
|
IJ19206 |
clstartstop fails to start Node after addips |
|
IJ19207 |
CAA:Core dump in libcluster.a
xcluster_wrapper functions |
|
IJ19209 |
Select Input Kuten Panel are not closed |
|
IJ19210 |
ESA activation fails
upgrading VIOS |
|
IJ19214 |
SEA becomes defined
state after enabling jumbo_frames. |
|
IJ19215 |
Unexpected input focus
change |
|
IJ19216 |
SSP logs slow disk IO
by mistake. |
|
IJ19217 |
Fixed race condition
in ahafs. |
|
IJ19219 |
caa -glob kdb command may not work |
|
IJ19220 |
VIOSUPGRADE FAILS TO
RESTORE THE INTERFACE WHEN REARRANGED |
|
IJ19222 |
LU fails liveupdatedata is served by client instead of master |
|
IJ19223 |
DTERM RESIZING
TERMINATES THE WINDOW |
|
IJ19224 |
Improving the name
resolution using /etc/hosts file. |
|
IJ19226 |
viosupgrade is failing to create mksysb with ISOimage |
|
IJ19227 |
viosupgrade is failing to create mksysb with ISOimage |
|
IJ19228 |
sync_repos needs to ignore backup disks |
|
IJ19230 |
VIX=NO file system
attribute not preserved after restore |
|
IJ19232 |
Preserve VIX attribute
for / FS after NIM mksysb restore |
|
IJ19233 |
assembler is missing
some extended mnemonics |
|
IJ19237 |
WPAR code maintenance |
|
IJ19238 |
IPSEC DOES NOT
NEGOTIATE WHEN IKEV2 IS CONFIGURED TO USE FQDN |
|
IJ19239 |
mkwpar
-f <spec file> may produce an extraneous Perl script msg |
|
IJ19246 |
ADAPTER STATISTIC
RESET MAY FAIL IN RARE CASES |
|
IJ19282 |
long pid/serial could cause buffer overrun |
|
IJ19283 |
sdiff
results in errors when comparing |
|
IJ19284 |
CHSEC DOESN'T MODIFY
LDAP_USER ATTRIBUTE W/O VALUE SPECIFIED |
|
IJ19285 |
WRITESRV DEAMON STUCK
LOOPING IN SIGSEGV CONSUMING CPU |
|
IJ19286 |
DIFF COMMAND ON
DIRECTORIES FAILS ON NFS FILE SYSTEMS |
|
IJ19287 |
Error reading stanza
in system reboot |
|
IJ19288 |
ed command alters the
file during default signal |
|
IJ19289 |
ed -s is failing
without error message |
|
IJ19290 |
awk with locale
LC_NUMERIC gives same value |
|
IJ19291 |
Linker ignores symbol
visibility in XCOFF32 archive member |
|
IJ19296 |
kdb command 'scsidisk -o' shows incorrect open list |
|
IJ19297 |
Excessive clusterwide snaps being taken during election failure |
|
IJ19298 |
Crash in sn_start_mb_commands_timer: abend_trap |
|
IJ19299 |
Fix vscsi error log entries |
|
IJ19300 |
LU udid
saved in CM database may be stale. |
|
IJ19301 |
FC5899 must signal
end-of-handling for interrupt offload |
|
IJ19302 |
System may crash if
memory allcoation fails |
|
IJ19304 |
DUPLICATE ENTRY IN
INITTAB IS NOT COMMENTED OUT BY AIXPERT |
|
IJ19305 |
Bottom command line
doesn't scroll |
|
IJ19307 |
p11admin,p11km
error while running on WPARS. Error AIX CF data |
|
IJ19309 |
viosupgrade fails to identify the disk and shows prompt |
|
IJ19310 |
Update of VIOS from
3.1.0 to 3.1.1 fails |
|
IJ19313 |
Potential crash on
reopen of device if reopen has failure |
|
IJ19314 |
Etherchannel failover takes more time after LPADUMP |
|
IJ19347 |
cl_vg_fence_init hung due to lock condition in disk driver |
|
IJ19348 |
Update to AIX 7.1.5.4
on reboot lpar w/VNIC hangs LED 581 |
|
IJ19349 |
trustchk
reports error for /e/s/ldap/*.map files after
update |
|
IJ19750 |
AIX7 LOGO IS MISSING
FROM CDE LOGIN SCREEN ON AIX72. |
|
IJ19814 |
CALLER3 CRASH IN
AHAFS_RELE |
|
IJ19815 |
SEA: health_time from CuAt might be
out of new PdAt range |
|
IJ19816 |
route command might
hang inside the kernel |
|
IJ19817 |
restwpar
fails to restore the WPAR |
|
IJ19819 |
VMX set to 0 and NX is
getting enabled |
|
IJ19820 |
acfo
-t tunables checks should be done |
|
IJ19821 |
Reset of NX is not
finding correct attribute |
|
IJ19824 |
client in hang state
after successful lpm |
|
IJ19825 |
DSI - PROC
@percpu_iodone_offl+0004AC |
|
IJ19826 |
LPD RESTARTS WHEN
PORTSCANNED (3WAY-RST) |
|
IJ19830 |
NVMe
drive moved from another OS does not work in AIX |
|
IJ19971 |
postgres
connections hang indefinitely if former DBN crashes |
|
IJ19972 |
commands are getting
hung |
|
IJ19977 |
dump command truncates
long symbol names |
|
IJ20153 |
Checksum error hit
after migrate -isolate |
|
IJ20154 |
Update of VIOS from
3.1.0 to 3.1.1 fails |
|
IJ20156 |
Restarting VM on
different machine fails |
|
IJ20205 |
lpar
got crashed @abend_trap+000000 |
|
IJ20246 |
LPAR hangs after LPM
with multiple vfc adapters and active IO |
|
IJ20333 |
Aix client may crash
due to stale pointer |
|
IJ20337 |
System DSI (NOT panic)
in IPRA.$topology_monitor |
|
IJ20399 |
Oracle coredumped during install |
|
IJ20498 |
Install images for
7200-04 |
|
IJ20563 |
AIX SOFTWARE ERROR or
KDB running diag on EN0H adapter on POWER7 |
|
IJ20564 |
diag
-cvd hung after eeh on
bell |
|
IJ20565 |
max_xfer_size negotiation with host |
|
IJ20711 |
AIX may crash with dsi during LPM |
|
IJ20712 |
Diagnostic displays
random SFP speed test after wrap-plug test. |
|
IJ20999 |
max_xfer_size not to exceed config requested |
|
IJ21168 |
LPAR PROBEVCT CRASH AT
XM_BAD_FREE+00026C |
|
IJ22202 |
system crash at
abend_trap+000000 |