PACKAGE: Update Release 2.2.5.40
IOSLEVEL: 2.2.5.40
|
VIOS level is |
NIM Master level must be equal to or higher than |
|
Update Release 2.2.5.40 |
AIX 6100-09-11 or AIX 7100-05-02 or AIX 7200-02-02 |
In June 2015, VIOS introduced the minipack as a new service stream delivery vehicle as well as a change to the VIOS fix level numbering scheme. 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.
If you are looking for a specific APAR number or fix, please check the list of fixes included in Update Release 2.2.5.40.
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.5.40. You may check the firmware versions using the “Fix Level Recommendation Tool” (FLRT).
Microcode or system firmware downloads for Power Systems
The VIOS Update Release 2.2.5.40 includes the IVM code, but it will not be enabled on HMC-managed systems. Update Release 2.2.5.40, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
Update Release 2.2.5.40 updates your VIOS partition to ioslevel 2.2.5.40. To determine if Update Release 2.2.5.40 is already installed, run the following command from the VIOS command line.
$ ioslevel
If Update Release 2.2.5.40 is installed, the command output is 2.2.5.40.
New Feature Information
Non-Volatile Memory express enhancements
Support for Non-Volatile Memory express (NVMe)
adapters. NVMe is an industry specification for accessing non-volatile storage
via the PCI express (PCIe) interface.
Remote management of NVMe from the Hardware Management Console (HMC) is in
toleration mode. User may not be able to manage virtual storage from HMC for NVMe
based volume group. But it is fully supported from the VIOS command line
interface (ioscli), which is the default padmin shell.
Full support for HMC management for NVMe is in VIOS 2.2.6 and onwards with a
future version of HMC.
VIOS NVMe devices can be used in the following
ways:
· As a VIOS boot device.
· As a way to create volume groups, and to create logical volumes. These logical volumes can be assigned as virtual Small Computer System Interface (vSCSI) devices for client partitions.
·
For
SSP disk caching. For more information about SSP disk caching, see https://www.ibm.com/support/knowledgecenter/POWER9/p9hb1/p9hb1_vios_ssp_flash_accl.htm.
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.5.40. 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.
Note that with this Update Release 2.2.5.40, 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.5.40, as well as the contents of the 2.2.5.10 release.
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.5.40 may be applied directly to any VIOS that is at either level 2.2.5.0 or 2.2.5.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.5.40.
Instructions: Single Step Update
To update to Update Release 2.2.5.40 from a level between 2.2.1.1 and 2.2.3.x in a single step, put the 2.2.5.10 updates in the same location as your 2.2.5.40 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.5.40 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.5.40 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.3.x.
You must put the 2.2.5.10 and 2.2.5.40 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.
/home/padmin/rules/vios_current_rules.xml
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.
To apply updates from a remotely mounted file system, and the remote file
system is to be mounted read-only, follow the steps:
The update release can be burned onto a CD by using the ISO image file(s). To apply updates from the CD/DVD drive, 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.5.10 located here.
This version will include all fixes found in all previous 2.2.5.X releases. The fixes for the previous release can be found here.
|
APAR |
Description |
|
IJ00021 |
scsidisk IOCTL cmd could hang if too many ENXIO errors occur |
|
IJ00170 |
MEMORY LEAK IN ERRLOG API WHEN USING ERRLOG_FIND_FIRST() |
|
IJ00195 |
Abort open sequence if PCM fails path |
|
IJ00288 |
snmpdv3 does not indicate endOfMibView correctly |
|
IJ00289 |
clmigcheck failing with reservation policy issue |
|
IJ00290 |
Applying bos.esagent update image may fail |
|
IJ00291 |
rpcinfo -p not showing service name |
|
IJ00292 |
RUNNING SNAP CAUSES SYNTAX ERRORS IF RUNS FROM CROWDED DIRS. |
|
IJ00294 |
FC 5721:INTERFACE DEFINED AT BOOT |
|
IJ00324 |
vios crashes vs_crq_kproc+0007A0 |
|
IJ00358 |
ARR MAY FAIL TO VARYOFF AND EXPORT CAAVG WHEN LUNS UNMAPPED |
|
IJ00360 |
Fixes for possible hang or crash due to locking issues. |
|
IJ00444 |
Install images for 6100-09-10 |
|
IJ00539 |
MKWPAR FAILED WITH THE OUT OF SPACE ERROR |
|
IJ00540 |
Handling of WWNN changes in PDISC accept Response |
|
IJ00541 |
LPAR is hung for a long time |
|
IJ00546 |
SHELL COMMAND THROWS ERROR WITH USER CAPABILITIES SET |
|
IJ00563 |
Fix multiple tcpdump CVEs from 9/11/2017 |
|
IJ00661 |
Installation from USB DVD Device fails with open device failure |
|
IJ00703 |
system crash during DLPAR operation |
|
IJ00743 |
KSH CORE IF SIGNAL RECEIVED DURING EXIT |
|
IJ00744 |
ENT PORT USING FC5708 FAMILY ADAPTER CAN NOT BE RMDEV |
|
IJ00745 |
Diagnostics does not analyze disk errors |
|
IJ00812 |
BOOT FAILS WITH 0X518 /TMP MNT FAILED |
|
IJ00833 |
System crash with infinite retry with a bad disk and IO delay |
|
IJ00833 |
System crash with infinite retry with a bad disk and IO delay |
|
IJ00886 |
UPGRADE RESETS NTP LINKS |
|
IJ00887 |
XNTPD CHILD PROCESS NEVER EXITS |
|
IJ00889 |
Fix autofs cachefs and stnfs major numbers |
|
IJ00904 |
CDE icon editor crashes while saving XPM format |
|
IJ01231 |
EFS /TMP FILESYSTEM CAUSES MIGRATION TO FAIL |
|
IJ01232 |
SNMP SET OF AIXAGENTCMDSTRING IN AIXMIBD TRUNCATED TO 64 BYTES |
|
IJ01233 |
clcomd generates coredump |
|
IJ01234 |
LKU failing at create_mirvg phase |
|
IJ01234 |
LKU failing at create_mirvg phase |
|
IJ01279 |
VM validation & recovery fails with same LSS VOL num ds8k disks |
|
IJ01281 |
chdef command does not change defaults for some disk attributes |
|
IJ01283 |
MEMORY LEAK DUE TO NFSV4 FILE HANDLES |
|
IJ01494 |
bos.perf.pmaix installation might fail |
|
IJ01567 |
mt__trce dumps cores with long |
|
IJ01569 |
SECLDAPCLNTD HANGS WITH BAD LSLDAP FILTER |
|
IJ01571 |
IPv6 installation hangs when booting across subnets |
|
IJ01572 |
fail to turn off vfc_host threading |
|
IJ01875 |
AUDIT OBJECTS WON'T WORK ON FILENAME WITH COMMA |
|
IJ01877 |
ASSERT AT BOOT IN NC_HEALTH_CHECK_WDOG |
|
IJ01878 |
LPM of vNIC client AIX partition fails |
|
IJ01879 |
Adapter running on another version of firmware after update |
|
IJ01882 |
Cannot add "eventtype=modDir" to rtcd_policy.conf using chsec. |
|
IJ01883 |
USERMOD -L FAILS IF HOST_LAST_LOGIN IS AN IPV6 ADDRESS |
|
IJ01993 |
System may crash during I/O striped LVs with Infinite Retry |
|
IJ01994 |
Fix adapter SMIT ODM |
|
IJ01994 |
Fix adapter SMIT ODM |
|
IJ02019 |
SNAP DOES NOT COLLECT AUTOLOAD WHEN COLLECTING LIVEDUMPS |
|
IJ02134 |
Setting mac addr using ioctl, ping fails |
|
IJ02193 |
cache_mgt device should list NVMe devices. |
|
IJ02194 |
ENOBUFS RETURNED IN ADDING A MULTICAST MEMBERSHIP |
|
IJ02318 |
LEVEL MATCHING PRIMARY & DR LUS MATCH VENDOR ONLY AT HIGHT |
|
IJ02322 |
Allow PCM ALUA code to be more aggressive switching controllers |
|
IJ02323 |
cache attribute for a VG may have wrong value. |
|
IJ02324 |
Improper handling of F3 on successful completion menu |
|
IJ02340 |
diag cmd fails to dwnload micrcd with -f optn |
|
IJ02423 |
clcmd hang |
|
IJ02525 |
CAA CLCOMD CONNECTION REFUSED DURING POWERHA 7.X MIGRATION |
|
IJ02674 |
AFTER UPDATING ALL VIOS SSP NODES, NODE UPGRADE STATUS STILL SHO |
|
IJ02726 |
A potential security issue exists |
|
IJ02806 |
iostat -a does not display disk mapped |
|
IJ02895 |
CRASH IN VS_THREAD_FREE() |
|
IJ03030 |
A potential security issue exists |
|
IJ03057 |
kernel abend on tstart() for EEH callbacks |
|
IJ03204 |
Cache stop may crash the system. |
|
IJ03375 |
Disk event indicates free when actually in use. |
|
IJ03377 |
Update Diag CD VRMF for 72H and 71a |
|
IJ03602 |
Invalid Slot ID firmware download |
|
IJ03634 |
Adapter dump data might be missing on shientdd device driver |
|
IJ03896 |
Stress runs over vnic lose connection |
|
IJ03958 |
ams partition failed with err HSCLA288,HSCLA237 |
|
IJ04078 |
crash @ npiv_dequeue+000014 |
|
IJ04357 |
Deploy or LPM initiated by PowerVC fails |
|
IJ04511 |
illegal instruction (core dump) in mbrtowc_wrap |
|
IJ04518 |
boot hangs on P4 full partition |
|
IJ04596 |
Potential loss of security fixes during LPM to Power7 |
|
IV76745 |
smitty search field filled with the 'n' character |
|
IV84636 |
BOOTPD DOESN'T FIND ROUTE WITH MANY NETWORK INTERFACES IN USE |
|
IV84636 |
Create 6.1 IPPs |
|
IV84705 |
Create 6.1 IPPs |
|
IV86172 |
Create 6.1 IPPs |
|
IV86209 |
Reformat RDMA trcfmt macros to print hardware-specific labels. |
|
IV86215 |
ARTEX support for device attribute settings comparison |
|
IV87170 |
Diagnostics disk verification fails on 4k SSD |
|
IV87224 |
Backspace is not working well on dtterm in JA_JP |
|
IV87498 |
System Crash if print issued without paper in Printer (IBM 5587) |
|
IV87676 |
Create 6.1 IPPs |
|
IV87676 |
SMIT ACCEPT_LICENSE CANNOT COMPLETE DUE TO DE_DE NEIN/JA CASE |
|
IV87792 |
Create 6.1 IPPs |
|
IV87792 |
STRIPNM SHOWING NEGATIVE VALUE FOR SYMBOL SIZE( TLS SYMBOLS ) |
|
IV87836 |
find slow when using "/*" in pathnames on remote filesystems |
|
IV87957 |
FC5899 ENTSTAT PRINTS 1818495488 FOR BAD PACKET COUNT IN NON-C |
|
IV88406 |
Add machine credentials to SUMA eCC downloads |
|
IV88546 |
tttrace generates invalid characters in JA_JP. |
|
IV88739 |
FC5899 may generate wrong ip_sum for large send packets (LSO) |
|
IV88943 |
sed command takes more time to execute |
|
IV88964 |
Possible crash with many (>2000) disks failing a path open. |
|
IV89079 |
AIX Diagnostics fail on transceiver and loopback tests |
|
IV89439 |
mkwpar with long name of 255 chars no longer fails |
|
IV89535 |
SYSTEM CRASH CONFIGURING GXIBDD LHCA INFINIBAND ADAPTER |
|
IV89862 |
JOIN -V COMMAND GIVES IMPROPER RESULT |
|
IV90091 |
The DB2 CF server crashes at dapl_evd_wait() |
|
IV90208 |
RULES COMMAND RETURNS 0590-102 INCORRECT PROFILE ERROR FOR VEA |
|
IV90380 |
ARTEXSET FAILED TO RESTORE BACKUP MKTCPIPPROFILE.XML |
|
IV90645 |
Standalone diags asks to unconfigure fcs dev when testing ent |
|
IV90893 |
DUPLICATE THIN SERVER MAINTENANCE OPTIONS IN SMIT MENU |
|
IV90903 |
LPSTAT WITH -T AND -P GENERATES CONFUSING OUTPUT |
|
IV91003 |
PASTE COMMAND GENERATES FILE WITH LESS LINES THAN ORIGINAL FILES |
|
IV91199 |
DMA errors after increasing num_cmd_elems |
|
IV91385 |
Test Unit progress message contains a misspelled word |
|
IV91386 |
dfcscsi might core dump if INT signal is recv'd at right moment |
|
IV91422 |
SYSTEM CRASH DUE TO DATA CORRUPTION BY SISRAID DRIVER. |
|
IV91435 |
DIAG MEMORY EXERCISER COREDUMP WITH SIGSEGV IN HTX_FINISH |
|
IV91498 |
CRASH IN ISCSI CODE DUE TO A NULL SCSI PTR |
|
IV91583 |
CFGMGR HANG AFTER LPM ON NOT MAPPED NPIV ADAPTER |
|
IV91584 |
SINGLE THREADED PROCESS HANGS IN LDAP_REQUEST MUTEX LOCK |
|
IV91609 |
LSTUN CORE DUMPED |
|
IV91801 |
SNAP -AC ADDS "+" TO /ETC/PASSWD AND ETC/GROUP FILE |
|
IV91810 |
LS -L MIGHT CUT THE END OF THE |
|
IV92497 |
MUSENT ERRORS WITH VIOS 2.2.5.X AND IBM I-SERIES CLIENT |
|
IV92865 |
IFCONFIG/NETSTAT/ENTSTAT HANG DUE TO FAILING LARGE_ALLOC() |
|
IV93269 |
At jobs fails:cannot accept more jobs into queue |
|
IV93457 |
Cannot compile Motif UIL in 64bit |
|
IV93733 |
Diagnostics calls out to replace the wrong Power Supply |
|
IV93735 |
TOPAS -C SHOWS INCORRECT PSZ DATA |
|
IV93972 |
wrong message in schedo -h for tunable select_intercept_max_fd |
|
IV93973 |
diagnostic support for 100Gbit RoCE PCIe3 Adapter |
|
IV94224 |
SMALL LSO PACKETS AND WRONG MSS VALUE |
|
IV94367 |
proctree for users is incorrect for both LPAR & WPAR |
|
IV94370 |
XARGS COMMAND DOES NOT HANDLE -L PARAMETER CORRECTLY |
|
IV94439 |
DUE TO TIMING ISSUE SAS DRIVER MIGHT CRASH THE SYSTEM |
|
IV94445 |
procmap Total is not resetting for multi proc entry |
|
IV94592 |
syntax error of positional formatting in struct.msg |
|
IV94890 |
startlft creates lft when no graphics adapter sw installed |
|
IV94897 |
FC5899: IFCONFIG/NETSTAT/ENTSTAT HANG DUE TO LARGE_ALLOC |
|
IV95159 |
FIND -LS DOES NOT LEAVE SPACE AFTER UID OR GID |
|
IV95318 |
perfprovider reports null value for SEA physicalLocation |
|
IV95527 |
EN0J AND EN0B ARE DISPLAYED AS PCIe2 |
|
IV95749 |
Bessel function jn wrong results for negative n |
|
IV96043 |
libcfg: multiple NULL dereferences in cfglog.c |
|
IV96462 |
DSI DUE TO VLANDD TRANSMIT |
|
IV96499 |
Disk open/close can hang forever |
|
IV96501 |
PROCSTACK <PID> CORE DUMPS |
|
IV96503 |
Prevent OBJECT_MODE=64 from overriding -m flag |
|
IV96553 |
Undetected data loss after storage errors with certain adapters |
|
IV96633 |
tcptr show may display negative session count |
|
IV96663 |
diff -c/-C/-u/-U should not produce output with identical files |
|
IV96831 |
FAILGRP STATE NOT UPDATED AFTER MFS FAILOVER |
|
IV96873 |
AT NOW JOBS RUN AT WRONG TIME NEAR DST CHANGE |
|
IV97012 |
FAILED SU ATTEMPT INCREMENTS UNSUCCESSFUL COUNT TWICE |
|
IV97020 |
LARGESEND PACKETS NOT SENT WITH PROPER IP CHECKSUM ON FC 5772 |
|
IV97279 |
POSSIBLE ISI CRASH ON VIOS IN NGDISK_PROC. |
|
IV97280 |
Pool stop hang during ECC recovery (PMR 32234,001,806) |
|
IV97627 |
sed standards test failure - comment after space |
|
IV97632 |
Fix several MPIO/POF related issues. |
|
IV97638 |
SSP MFS manager inconsistent |
|
IV97715 |
Repeated EEH events may result in hang |
|
IV97842 |
batch writes stderr without string |
|
IV97853 |
Handle media repository files with name length of one char |
|
IV97853 |
Handle media repository files with name length of one char |
|
IV97854 |
Init daemon writes extraneous entries to wtmp |
|
IV97877 |
VLAN and VLAN IP did not get restored as part of viosbr. |
|
IV97925 |
complex math routines are not threadsafe |
|
IV97969 |
SDK 7.0.0 32-bit SR10 FP10 - 17_03 |
|
IV97970 |
SDK 7.0.0 64-bit SR10 FP10 - 17_03 |
|
IV98080 |
ADAPTERS #EN0J IS REPORTING AS PCIE2 INSTEAD OF PCIE3 |
|
IV98127 |
crash in net_malloc_cpu while configuring ib |
|
IV98313 |
migvscsi segfaults in failed remote restart error path |
|
IV98362 |
Brazos CEC in Imcomplete state, vnicserver hang |
|
IV98363 |
memory leak with list lu in ssp. |
|
IV98413 |
Create 6.1 IPPs |
|
IV98504 |
Lpar seems to hang after LPM when adapter was closing |
|
IV98527 |
rm -r with ../ deletes previous directory |
|
IV98528 |
du reports an error when resolving a symbolic link |
|
IV98530 |
Configuration commands may hang on the VIOS |
|
IV98577 |
BASEDN FILTER IS APPENDED TO WRONG BASEDN |
|
IV98790 |
Fix uninitialized variable in lsmpio command |
|
IV98791 |
USB DVD I/Os need to be failed on deferred error |
|
IV98792 |
STARTWPAR LATENCY DUE TO NFS FILE SYSTEMS MOUNT |
|
IV98793 |
FTPD AUDIT RECORDS ARE NOT RECORDED FOR THE FTP USER |
|
IV98794 |
Disk becomes defined when reserve_policy changed to single_path |
|
IV98795 |
alt_disk_copy doesn't allow exclusion of large nfs-mounted file |
|
IV98796 |
alt_dsisk_copy fails when files exist larger than ulimit allow. |
|
IV98797 |
'cache_mgt monitor get' command errors out |
|
IV98798 |
Memory leak in PCM SSP data collection in VIOS. |
|
IV98799 |
#NAME? |
|
IV98800 |
RMUSER SHOULD FAIL WHEN USER HAS RUNNING PROCESSES |
|
IV98801 |
Read did not set variables to the expected values |
|
IV98802 |
multibos from mksysb failing in 4k disks |
|
IV98803 |
sh fails when options without option-arguments |
|
IV98803 |
sh fails when options without option-arguments |
|
IV98805 |
pselect returned late seconds |
|
IV98807 |
wide character value is not as expected for mbrtowc(). |
|
IV98808 |
When domainless group is enabled, Fail to delete group |
|
IV98810 |
Crash in net_kmem_rmlist |
|
IV98811 |
Unable to change password from nonroot user |
|
IV98826 |
A potential security issue exists |
|
IV98919 |
LSTUN COMMAND COULD HANG DURING LPM. |
|
IV98922 |
Timed-out waiting for child to exit |
|
IV98923 |
fc -e error is not redirecting to standard error |
|
IV98924 |
TRUSS REPORTS INCORRECT ARGUMENTS DATA FOR FEW SYSCALLS |
|
IV98925 |
CAA:CHOOSE_SLOT() FAILURE LEADS TO INTERNODE COMMUNICATION ERROR |
|
IV98926 |
cache states are shown as inactive after LPM |
|
IV98927 |
IBM 4767 dd is not returning the Status Request field |
|
IV98942 |
CHDEV -P SETTING MIN OF A BUF SIZE GREATER THAN MAX SHOULD FAIL |
|
IV99012 |
SRIOV adapter(lnc2entdd) dump causes backing device failure |
|
IV99013 |
nim operation hangs when cust script contains unending process |
|
IV99014 |
perfprovider(srcloop) might coredump sometimes. |
|
IV99015 |
vrmf mismatch may not boot message during alt_disk_mksysb |
|
IV99016 |
configassist will be unresponsive in password panel |
|
IV99019 |
CPLV FROM 512 BLOCK SIZE DISK TO 4K DISK WILL FAIL IN COPYRAWL |
|
IV99020 |
Cluster creation failed |
|
IV99021 |
read sets vars incorrectly with tab+nl IFS |
|
IV99024 |
HANG OCCURS IN _LIBS_CHILD_POST_FORK |
|
IV99028 |
A vSCSI client may start having I/O timeout failures |
|
IV99169 |
DSI IN STH_REMOVE_STH |
|
IV99172 |
TRUSS -F MAY HANG IF CHILD TRUSS PROCESS ABORTS |
|
IV99175 |
system crash @ pm_set_perfm_regs |
|
IV99176 |
udfcreate causes VIO instance to reboot |
|
IV99209 |
crash while testing SNMP test bucket |
|
IV99276 |
FC5270,5708:MPOOL LEAK WHEN MSNENTDD OPEN FAIL |
|
IV99281 |
PV INVENTORY REPORTS INCORRECT MPIOALGORITHM FOR EMC XTREMIO |
|
IV99293 |
NVMe drives on a particular adapter all get formatted at once. |
|
IV99294 |
Fix for incorrect DRM thread creation order |
|
IV99295 |
LSCFG COREDUMPS ON LONG LOCATION CODES |
|
IV99296 |
INCORRECT BEHAVIOUR OF CHSEC WHEN DOMAINLESSGROUPS IS ENABLED |
|
IV99297 |
filemon command coredumps |
|
IV99298 |
Display Avg write request size and latency with pfcras. |
|
IV99299 |
crash in sec_thread |
|
IV99300 |
Undesirable behavior may occur once caching is started. |
|
IV99301 |
Fix Cache Engine to handle missing pool disks. |
|
IV99303 |
NFSO COMMAND WITH -P FLAG DOESN'T WRITE INTO NEXTBOOT FILE |
|
IV99304 |
dtterm doesn't show correct size |
|
IV99305 |
query fails when 0 repos in kernext |
|
IV99463 |
Ipcs prints D mode bits for shared memory segments |
|
IV99472 |
CLOSING A ROCE DEVICE TAKES MORE THAN 1 SECOND |
|
IV99548 |
A potential security issue exists |
|
IV99586 |
BACKBYINODE MIGHT LOOP INDEFINITELY IF TTY IS CLOSED |
|
IV99617 |
SYSLOG LOG MAY SHOW ERRONEOUS "INTERNAL ERROR" LOG ENTRIE |
|
IV99619 |
bos.pfcdd install log created with wrong mode bits |
|
IV99659 |
lsmksysb on a USB/UDFS backup may not recognise media |
|
IV99701 |
System may hang/crash during I/O striped LVs with Infinite Retry |
|
IV99706 |
VSCSI ADAPTER HANG DUE TO MULTIPLE SRP LOGIN REQUESTS |
|
IV99733 |
DHCPCD DUMPS CORE IF MORE THAN FOUR INTERFACES ARE SPECIFIED |
|
IV99751 |
memory leak in svmon code |
|
IV99853 |
Failing Diagnostics POST Test on crypto adapter |
|
IV99857 |
BACKBYNAME HANGS ON NFS4 FILE OR MOUNT POINT |