Package Information

PACKAGE: Update Release 3.1.3.21
IOSLEVEL: 3.1.3.21

VIOS level is

NIM Master level must be equal to or higher than

Update Release 3.1.3.21

AIX 7200-05-04

 

Please refer to the VIOS Maintenance Strategy here for more details regarding the change to the VIOS release numbering scheme.

General package notes

Do not install this service pack on any release below 3.1.3.0. Instead, please use the 3.1.3.21 Fix Pack to update your VIOS.

Be sure to heed all minimum space requirements before installing.

Review the list of fixes included in Update Release 3.1.3.21

To take full advantage of all the functions available in the VIOS, it may be necessary to be at the latest system firmware level. If a system firmware update is necessary, it is recommended that the firmware be updated before you update the VIOS to Update Release 3.1.3.21.

Microcode or system firmware downloads for Power Systems

Update Release 3.1.3.21 updates your VIOS partition to ioslevel 3.1.3.21. To determine if Update Release 3.1.3.21 is already installed, run the following command from the VIOS command line.

$ ioslevel

If Update Release 3.1.3.21 is installed, the command output is 3.1.3.21.

Installation Information

Pre-installation Information and Instructions

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.3.21. Run the lsvg rootvg command, and then ensure there is enough free space.

Example: 

$ lsvg rootvg 
VOLUME GROUP:       rootvg                   VG IDENTIFIER:  00f6004600004c000000014306a3db3d
VG 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: 2
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         1                        AUTO ON:        yes
MAX PPs per VG:     32512                                     
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable 
PV RESTRICTION:     none                     INFINITE RETRY: no
 
 
Virtual I/O Server support for Power Systems

 

Before installing the VIOS Update Release 3.1.3.21

 

Warning: The update may fail if there is a loaded media repository.

 

Instructions: Checking for 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.

 

Instructions: Migrate Shared Storage Pool Configuration

 

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.3.21 using rolling updates.

A non-disruptive rolling update to VIOS 3.1 requires all SSP nodes to be at VIOS 2.2.6.31 or later. See detailed instructions in the VIOS 3.1 documentation.

 

The rolling updates enhancement allows the user to apply Update Release 3.1.3.21 to the VIOS logical partitions in the cluster individually without causing an outage in the entire cluster. The updated VIOS logical partitions cannot use the new SSP capabilities until all VIOS logical partitions in the cluster are updated.

 

To upgrade the VIOS logical partitions to use the new SSP capabilities, ensure that the following conditions are met:

 

·        All VIOS logical partitions must have VIOS Update Release version 2.2.6.31 or later installed.

·        All VIOS logical partitions must be running. If any VIOS logical partition in the cluster is not running, the cluster cannot be upgraded to use the new SSP capabilities.

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.

 

Installing the Update Release

 

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.

 

 

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:

$ rules -o deploy -d

 

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.

 

  1. Log in to the VIOS as the user padmin.
  2. If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Update Release. See details here.
  3. If you use Shared Storage Pools, then Shared Storage Pool Services must be stopped.

    $     clstartstop -stop -n <cluster_name > -m <hostname >
  4. To apply updates from a directory on your local hard disk, follow the steps:
    1. Create a directory on the Virtual I/O Server.
      $       mkdir <directory_name >

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:

      1. Mount the remote directory onto the Virtual I/O Server:
        $         mount remote_machine_name:directory /mnt

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:

      1. Place the CD-ROM into the drive assigned to VIOS.
  1. Commit previous updates by running the updateios command:
    $     updateios -commit
  2. Verify the updates files that were copied. This step can only be performed if the link to openssl was created.
    $     cp <directory_path >/ck_sum.bff /home/padmin 
    $     chmod 755 </home/padmin>/ck_sum.bff 
    $     ck_sum.bff <directory_path > 
    If there are missing updates or incomplete downloads, an error message is displayed.

    To see how to create a link to openssl, click here.
  3. Apply the update by running the updateios command
    $     updateios -accept -install -dev <directory_name >
  4. To load all changes, reboot the VIOS as user padmin .

$ 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.

  1. If cluster services were stopped in step 3, restart cluster services.

$ clstartstop -start -n <cluster_name > -m <hostname >

  1. Verify that the update was successful by checking the results of the updateios command and by running the isolevel command, which should indicate that the ioslevel is now 3.1.3.21.

$ ioslevel

Post-installation Information and Instructions

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

Additional Information

For additional details, including known capabilities, limitations, and additional install considerations, as well as some additional instructions, please reference the readme for 3.1.3.21 located here.

Fixes included in this release

This version will include all fixes found in all previous 3.1.3.X releases.  The fixes for the previous release can be found here.

 

The list of fixes in 3.1.3.21

 

APAR

Description

IJ22238

Install images for bos.dsc

IJ32952

SRCMSTR NOT LOGGING SRC_RSTRT AND SRC_TRYX

IJ33842

clearaca cmd failure, due to link down, could cause hang.

IJ33848

PAX FAILS TO RESTORE MODIFICATION TIMES

IJ33852

RESTORE SYMLINKS FOR @DOUBLEBYTE JIM MODIFIER

IJ33947

FAILURE TO INSTALL ADDITIONAL RPMS DURING NIM MKSYSB INSTALL

IJ34700

NFSV4 MOUNT HANG TRIGGERED BY THE REMOUNT COMMAND

IJ34711

CDP daemon output discrepancy

IJ34739

support max value of 300 sec for rw_timeout attribute

IJ34994

EXPORTFS ERRORS MAY OCCUR WHEN ALLOCATING NIM RESOURCES

IJ34997

GETGRGID DOESN'T WORK WITH DOMAINLESS GROUPS - AFFECTS SUDO

IJ34998

DOMAINLESSGROUPS DOESN'T WORK WITH NETGROUP

IJ35110

RUNNING MOUNT -A CHANGE MOUNT FROM HARD TO SOFT

IJ35164

SYNTAX ERRORS WHEN SCRIPT CALLS MULTIPLE HEREDOCS

IJ35253

I/O MAY HANG DURING LPM WITH 7.2 TL5 SP2

IJ35254

7.2 TL5 logs Temp transport faults during LPM

IJ35322

LDAP NEGATIVE CACHE NOT WORKING FOR UID/GID NUMBERS

IJ35475

Disk ping driver NDD_JOIN fails with ENOMEM

IJ35480

NEWLY CREATED CERTIFICATES ARE REPORTING EXPIRED

IJ35575

Make error check less aggressive when using delayed_fail

IJ35612

NETMON SHOULD RUN WHEN ONLY A SINGLE NODE IS UP

IJ35788

VIOS snap does not collect vnicstat output on a vNIC server

IJ35828

AIX vNIC client receive hang condition

IJ35912

fcstat output for pend_cmd's may continue to increment.

IJ35948

fcstat reports wrong control requests on virtual fc adapter

IJ35977

VFC4_ERR10 WITH VFC_ERR_LOC_18E LOGGED AFTER RSCN ON 7.2 TL5

IJ35998

IN RARE CASES JFS2 AIO_RETURN() HAS A STALE VALUE

IJ36078

RESTVG ON ON LARGE DISKS MAY FAIL CREATING FILESYSTEMS

IJ36253

Better error when required redundancy paths are not met

IJ36254

Fix deadlock issue in VMRM HA solution.

IJ36255

VMRM Host Monitor inoperative after add VIOS

IJ36256

EXCESSIVE "VIO_INFO: HM LOST ACCESS TO DATA BASE" IN ERRLOG

IJ36257

Add an error message for unsupported disks

IJ36258

VIOS Hard Failures error message returned to KSYS.

IJ36259

AddMS failed hsmon not up.

IJ36273

FCP_ERR14 with error code A2 AFTER RSCN ON 7.2 TL5

IJ36339

DR verify fails for DS8K

IJ36638

mksysb restore displays error warning if hdisk number different

IJ36641

SNMP HOSTMIBD REPORTING WRONG CPU INFO

IJ36643

IKEV2D GETS STUCK IN AN INFINITE LOOP WHEN A EMPTY UDP PACKET IS

IJ36645

pkcs11 kernext crash with a bad memory pointer

IJ36646

A SECURITY PROBLEM EXISTS WITH LOG FILES

IJ36647

VMRM RECEIVES ADAPTER DOWN / UP FROM CAA

IJ36649

IPSEC TUNNEL CONFIGURATION REJECTS SINGLE CERTIFICATE

IJ36651

ASO CORE DUMPS IN LGPG_PSTATUS_HOTSEGS()

IJ36653

SEA IS NOT REGISTERING ITS LINK STATUS CALL BACK FUNCTION

IJ36658

ospf_monitor command core dumps when passed very long argument

IJ36659

ntptrace command core dumps when passed very long arguments

IJ36660

USB Diagnostics download microcode source fails

IJ36664

Possible crash with tier remove when using SSP disk caching

IJ36666

for P10 lparstat now show Mode

IJ36667

Extraneous pthread_mutex_unlock call in clcomd

IJ36668

amepat P10 CPU frequency

IJ36669

libld.a does not handle large files in 32-bit programs

IJ36673

IPv6 perf. degrades with IPSEC, chksum_offload & ipv6_offload

IJ36677

Text Editor disappeared in ja_JP.IBM-eucJP

IJ36678

ICON Editor not save state into session

IJ36680

Need to create caa_slave.stdio at install time

IJ36681

A potential security issue exists

IJ36682

A potential security issue exists

IJ36689

IPSECv6 component kernel trace not getting logged.

IJ36691

UNRECOVERABLE EN0W FC ADAPTER AFTER FIRMWARE UPDATE.

IJ36692

fcstat -z may not zero High water "Adapter Driver Queue Stats"

IJ36693

IEEE802.3AD ETHERCHANNEL FAILBACK RIGHT AFTER FAILOVER

IJ36694

max_npivs not stored in CuAt at boot or during config method

IJ36695

FC adapter Input/Output statistics misreported in VIOS 3.1.X

IJ36700

Enabling SANCOM failing after LPM

IJ36701

IO failure on client after DBN node reboot

IJ36702

Improve logging during violib DB function load

IJ36703

Avoid error logging, for FCNVMe LS_RJT for lower error checks

IJ36704

Writing iso image to unformatted USB DVD media might hang

IJ36706

Need clear err msg when changing EC teaming mode to other mode

IJ36707

Add of LV backed paging device to CM database fails with error.

IJ36708

cryptstat can not load translation message for cmd usage

IJ36710

Crash when set dpages_regular to 0x20000 on RoCE adapters

IJ36711

Migrations fail at start due to total bytes=0 error

IJ36712

add ERRID_ACL_VIOLATION error ID to lnc2entdd device driver

IJ36714

AIX lpar crashes for stale cmd after adatper reset sequence.

IJ36715

Crash in processFcpError on disk open

IJ36716

Configuring IP on Etherchannel madeup of vEths, may fail.

IJ36718

Failed rootvg paths may not automatically recover

IJ36723

Pthread sigsuspend returns an unsupported errno after LKU

IJ36725

segmentation fault occurs on hdcryptmgr pksshow

IJ36726

DU COMMAND MAY LOOP ENDLESSLY

IJ36727

LDAP NEGATIVE CACHE WON'T WORK IF THERE'S AN INVALID DN

IJ36728

LSPV MAY SHOW A DEVICE LOCKED TWICE

IJ36729

JFS2 ROLLBACK FOR A LARGE FILESYSTEM MAY NOT COMPLETE CORRECTLY

IJ36731

EXTENDVG MAY GIVE MISLEADING ERROR MESSAGE REGARDING MAX PPS

IJ36732

cleanup issue

IJ36733

joinvg -f system crash during space reclaim of split PV's

IJ36734

DSI when deleting a PV when space reclaim is in progress

IJ36735

NIM Maintenance boot lvmstat error messages

IJ36736

NIM maintenance boot sees logredo64 error while mounting rootvg

IJ36737

lvmstat core dump when reporting space reclaim statistics

IJ36741

od -N fails for large integer values

IJ36742

fail to collect adapter dump when device is not in use

IJ36743

Improve Live Partition Mobility RAS

IJ36760

Update to kdb disassembly of dcbt/dcbtst instructions

IJ36790

Compress cmd may not able to display right output

IJ36792

lsvg/lspv not displaying total, free, used PPs properly for ver

IJ36810

A potential security issue exists

IJ36821

MINISNAP COLLECTION MAY FAIL WITH SYNTAX ERROR

IJ36835

_pks_state is missing from syscalls.imp after update install

IJ36942

MEMORY LEAK IN LDAP LOAD MODULE

IJ37006

LDAP USER/GROUP WITH PARENTHESES NOT FOUND

IJ37007

SECLDAPCLNTD MAINTAINS AN INVALID BIND TO SERVER

IJ37008

BOS.RTE.SREAMS LEFTOVERS AFTER MIGRATION TO AIX 7.3

IJ37010

Firmware update returns zero for the FW version and logs error

IJ37013

ASO CORE DUMPS IN PROCESSMAP_MERGE_LISTS()

IJ37014

Active System Optimizer jobs not deleted during LPM/DPO

IJ37049

FS mount fails after importvg of VG of encrypted LV's

IJ37052

GettingLVM_SA_QUORCLOSE event for GLVM Async VG

IJ37058

Commands are getting hung and software program errors on errpt

IJ37062

MISSING /ETC/SECURITY/SECMIGCONF FILE WRONGLY LEADS TO SECLPM

IJ37128

Improve error messages for link-time optimization and ibm-clang

IJ37129

Better processing for ibm-clang with profile-guided optimization

IJ37133

CFGVIOS NEEDS TO CHECK AND UPDATE SYSTEM MODEL NAME AND ODM

IJ37136

discovery failing at startVM

IJ37143

fix for IJ35178 missing hd_pin and hdcryptmgr

IJ37150

CAA CL_RESYNC_SITE() DELAYS REBOOT WHEN MERGE OCCURS

IJ37153

LIBCLUSTER.A __CLUSTER_INIT IS LEAKING ON DLOPEN/DLCLOSE

IJ37162

ERASE DISKS OPTION NOT WORKING IN MAINTENANCE BOOT

IJ37185

GSSD MEMORY LEAK / CORE DUMP

IJ37188

Host monitor not started when adding VIOS.

IJ37203

JFS2 FILE SYSTEM CAN  GET MARKED CORRUPT AFTER EXTENDING FS.

IJ37223

Lame cache can be abused to severely degrade res

IJ37239

perror() gets unresolved

IJ37242

REDUCEVG ON CONCURRENT SVG CAN LEAVE PASSIVE NODE OUT OF SYNC

IJ37243

NON-DEFAULT SIZE FOR VIOSVC.LOG LEADS TO CORE_DUMP

IJ37257

VFC ADAPTER MAY LOG DMA AND ENOMEM ERROR DURING LPM

IJ37261

FCSTAT MAY REPORTS INVALID VALUE FOR IN/OUTPUT BYTES

IJ37315

PATCH PROGRAM ASSERTS WHEN IT CAN'T FIND A HUNK

IJ37318

VIO USES TOO SHORT A TIMEOUT TO CHECK IF POOL IS SAFE

IJ37360

TRC_GENERATE_EA_DATA() REPORTING DISTANCE AS INVALID

IJ37362

wrong error message with API testing

IJ37377

POSTGRES MAY NOT RUN PROPERLY AFTER UPDATING FROM 3.1.0 TO 3.1.3

IJ37377

POSTGRES MAY NOT RUN PROPERLY AFTER UPDATING FROM 3.1.0 TO 3.1.3

IJ37380

RESTVG FAILED AFTER THE SYSTEM RESTORED FROM A MKSYSB BACKUP

IJ37395

SUMA FAILS WITH JVMCFRE003 BAD MAJOR VERSION

IJ37485

LINK ERRORS ON NPIV CLIENT WHEN RUNNING CFGMGR ON VIOS

IJ37488

A potential security issue exists

IJ37489

HD_SYNC_TIMER_HANDLER MAY CAUSE RECURLOCK CRASH AT INTIODONE

IJ37494

A potential security issue exists

IJ37509

touch with -r option to file doesn't work

IJ37513

Stopping HA services fails when a node is halted.

IJ37585

AIX 7.2 EXHIBITS SLOW FTPD READ PERFORMANCE

IJ37586

installp can coredump with XPG_SUS_ENV=ON after

IJ37587

MODIFIED STORAGE KEY SETTINGS NOT REFLECTING AFTER UPGRADE

IJ37611

aix system crashes if write is performed on proc file

IJ37627

Handle the strdup failures in exit path of cache update funcs

IJ37670

Update Diagnostics VRMF

IJ37671

Diagnostics Disk Maintenance task lists unsupported disk

IJ37699

Firmware update causes diagnostic TU41 to fail

IJ37730

STOP CREATING DATABASE ENTRIES FOR EXPECT/TCL/TK RPM IMAGES

IJ37819

pv -remove performance fix for SSP

IJ37823

LKU FROM NIM MAY FAIL WITH:KSH: 0403-057 SYNTAX ERROR AT LINE 1

IJ37839

POSSIBLE CONFIG HANG IF CLIENT HAS I/O ACTIVE DURING MOVE_LOGIN

IJ37921

SYSTEM MAY CRASH WHEN MOUNTING CDROM

IJ37923

Clean up error messages for LTO

IJ37957

OLSON TZ: JORDAN STARTS DST FEB 24 22 (2019B)

IJ37959

Linking errors when using link-time optimization

IJ37960

fsck does not fix issues in dmap leaves correctly

IJ38001

In NPIV multi-q vios may start failing sub-queue registration

IJ38003

ras_cb operation failure when client is connected.

IJ38005

vfchost miss to send cancel during NPIV_LOGOUT for some cases

IJ38042

LPM POST PHASE MEMORY PROCESSING HOLDS ON COMMANDS LIKE VARYONVG

IJ38101

FB_DELAY IS NOT WORKING SOMETIMES IN SIMPLIFIED SEA SETUP

IJ38117

A potential security issue exists

IJ38118

A potential security issue exists

IJ38118

A potential security issue exists

IJ38132

SYSTEM HANG IN PGSIGNAL()

IJ38134

do_trace_control+000264 abend

IJ38188

rules list not proper for redfish/bluefish fc adapters codedrop

IJ38190

VIOS crashed at d_unmap_list_tce+0000A4

IJ38210

/OPT/FREEWARE FILESYSTEM CORRUPTED AFTER DVD/NIM MIGRATION

IJ38255

NETWORK UNRESPONSIVE DUE AFTER RX NETWORK BURST

IJ38560

IBM i client getting Transport Fault responses to NPIV L

IJ38565

IN ALL SUPPORTED LEVELS SMITTY DATE CAN'T CHANGE DATE AFTER 2038

IJ38570

IKDEB -P THROWS ERROR "A LSP FUNCTION DETECTED A BAD PARAMETER"

IJ38572

Cleanup Microcode files on Diagnostics Standalone CD

IJ38573

Error while listing rules for num_io_queues attribute

IJ38595

LDAP USER NOT FOUND EVEN THOUGH IT IS PROPERLY DEFINED

IJ38598

script priority is wrong for LVUP_POST_IMPORTVG_1

IJ38599

SEA HA state in limbo when changing real adapter

IJ38601

Crash in iostdel on rmdev of non-MPIO device with debug kernel

IJ38820

Updating timezone data files to latest available for 2022

IJ38862

SSP cluster create failed due to inability to create database.

IJ38864

crash @ npiv_cmd_handler+000070

IJ38977

GETGROUPATTR MEMORY LEAK

IJ39006

AIX NPIV mapping to one target VIOS with So

IJ39042

system crash while performing heavy IO using vdbench.

IJ39043

Need to increase the default size of /tmp

IJ39157

Npiv client hang aftr lpm in mix vio env

IJ39158

VIOS may crash during NPIV adapter unconfigure and ras operation

IJ39719

alt_disk_mksysb may require greater than 32MB BLV

IJ39721

/home fills up quickly on VIOS running SSP

IJ39739

crash @ pmtu_alloc+000604