Package Information

PACKAGE: Update Release 3.1.1.60
IOSLEVEL: 3.1.1.60

VIOS level is	NIM Master level must be equal to or higher than
Update Release 3.1.1.60	AIX 7200-04-06

 

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

 

General package notes

Be sure to heed all minimum space requirements before installing.

Review the list of fixes included in Update Release 3.1.1.60

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

Microcode or system firmware downloads for Power Systems

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

$ ioslevel

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

Important Changes in 3.1.X.X for SSP users

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.X.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.X.X versions of the VIOS.

 

Note: 3.1.X.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.

 

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

 

Upgrading from VIOS version 3.1.1.00 and above

 

VIOS Update Release 3.1.1.60 may be applied directly to any VIOS that is at either level 3.1.1.00 or above.

 

Upgrading from VIOS version 3.1.0.00 and above

 

The VIOS must be upgraded to version 3.1.1.00 or 3.1.1.10 before Update Release 3.1.1.60 may be applied.

 

A single-step upgrade can be performed, but it requires that the user does the following:

 

1.     Put the 3.1.1.10 install packages into the desired install directory.

2.     Place the 3.1.1.60 install packages in the same directory.

3.     Use the updateios command to perform the update.

  

Upgrading from VIOS version 2.2.6.X and below

 

The VIOS must first be upgraded to 3.1.0.00 before the 3.1.1.60 update can be applied.  To learn more about how to do that, please read the information provided here. 

 

Before installing the VIOS Update Release 3.1.1.60

 

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

 

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.

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.

5. Commit previous updates by running the updateios command:
   $ updateios -commit
6. 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.
7. Apply the update by running the updateios command
   $ updateios -accept -install -dev <directory_name >
8. 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.

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

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

10. 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.1.60.

$ 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.1.10 located here.

Fixes included in this release

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

 

The list of fixes in 3.1.1.60

 

APAR	Description
IJ38412	/OPT/FREEWARE FILESYSTEM CORRUPTED AFTER DVD/NIM MIGRATION
IJ34179	/PROC OPEN FAILS EVEN WHEN EGID RGID SGID MATCHES AFTER IJ21384
IJ22238	Install images for bos.dsc
IJ30113	SYSTEM HANG IN PGSIGNAL()
IJ31672	LDAP NEGATIVE CACHE NOT WORKING FOR UID/GID NUMBERS
IJ31883	mksysb restore displays error warning if hdisk number different
IJ31950	NPIV PATH MISSING AFTER VIOSUPGRADE FROM 2.2.6.X TO 3.1.X.X
IJ32354	SNMP HOSTMIBD REPORTING WRONG CPU INFO
IJ32571	LDAP NEGATIVE CACHE WON'T WORK IF THERE'S AN INVALID DN
IJ32839	DOMAINLESSGROUPS DOESN'T WORK WITH NETGROUP
IJ32840	GETGRGID DOESN'T WORK WITH DOMAINLESS GROUPS - AFFECTS SUDO
IJ33422	UPDATEIOS -REMOVE_OUTDATED_FILESETS FLAG NOT DOCUMENTED
IJ33490	LSPV MAY SHOW A DEVICE LOCKED TWICE
IJ33596	ASO CORE DUMPS IN PROCESSMAP_MERGE_LISTS()
IJ33733	CRASH IN TFREE() WHEN VFCDD IS PERFORMING VFC_CFG_CLEANUP
IJ33772	pkcs11 kernext crash with a bad memory pointer
IJ34667	REMOVE_OUTDATED_FILESET OPTION IN UPDATEIOS REMOVES PART COMMAND
IJ34765	ASO CORE DUMPS IN LGPG_PSTATUS_HOTSEGS()
IJ34839	SECLDAPCLNTD MAINTAINS AN INVALID BIND TO SERVER
IJ35163	EXPORTFS ERRORS MAY OCCUR WHEN ALLOCATING NIM RESOURCES
IJ35194	UNRECOVERABLE EN0W FC ADAPTER AFTER FIRMWARE UPDATE.
IJ35294	SYNTAX ERRORS WHEN SCRIPT CALLS MULTIPLE HEREDOCS
IJ35312	SecondsSinceLastReset not reset from fcstat -z fcsX command
IJ35465	EXTENDVG MAY GIVE MISLEADING ERROR MESSAGE REGARDING MAX PPS
IJ35512	VIOS snap does not collect vnicstat output on a vNIC server
IJ35515	IEEE802.3AD ETHERCHANNEL FAILBACK RIGHT AFTER FAILOVER
IJ35523	CAA CL_RESYNC_SITE() DELAYS REBOOT WHEN MERGE OCCURS
IJ35574	Make error check less aggressive when using delayed_fail
IJ35720	AIX vNIC client receive hang condition
IJ35735	NEWLY CREATED CERTIFICATES ARE REPORTING EXPIRED
IJ35831	PATCH PROGRAM ASSERTS WHEN IT CAN'T FIND A HUNK
IJ36041	COMPRESS CMD MAY NOT BE ABLE TO DISPLAY RIGHT OUTPUT IN JAPANESE
IJ36291	Using LDR_PRELOAD or LDR_PRELOAD64 leads to out-of-memory error
IJ36467	clearaca cmd failure, due to link down, could cause hang.
IJ36490	REDUCEVG ON CONCURRENT SVG CAN LEAVE PASSIVE NODE OUT OF SYNC
IJ36496	max_npivs not stored in CuAt at boot or during config method
IJ36528	MODIFIED STORAGE KEY SETTINGS NOT REFLECTING AFTER UPGRADE
IJ36730	Stopping HA services fails when a node is halted.
IJ36806	A potential security issue exists
IJ36973	RESTVG FAILED AFTER THE SYSTEM RESTORED FROM A MKSYSB BACKUP
IJ37091	CFGVIOS NEEDS TO CHECK AND UPDATE SYSTEM MODEL NAME AND ODM
IJ37225	Lame cache can be abused to severely degrade res
IJ37311	Live Update fails when a thread is waiting for a WLM event
IJ37382	HD_SYNC_TIMER_HANDLER MAY CAUSE RECURLOCK CRASH AT INTIODONE
IJ37478	EXCESSIVE "VIO_INFO: HM LOST ACCESS TO DATA BASE" IN ERRLOG
IJ37496	A potential security issue exists
IJ37501	A potential security issue exists
IJ37502	A potential security issue exists
IJ37503	A potential security issue exists
IJ37504	A potential security issue exists
IJ37654	OLSON TZ: JORDAN STARTS DST FEB 24 22 (2019B)
IJ37705	A potential security issue exists
IJ38059	AIX VNIC CLIENT: NETWORK UNRESPONSIVE AFTER RX NETWORK BURST
IJ38115	A potential security issue exists
IJ38116	A potential security issue exists
IJ38116	A potential security issue exists
IJ38391	LDAP AFFECTS VIOS PKG UPDATE SCRIPT CREATE VIOS AUTHORIZATION
IJ38392	IKEV2D GETS STUCK IN AN INFINITE LOOP WHEN A EMPTY UDP PACKET IS
IJ38393	TRC_GENERATE_EA_DATA() REPORTING DISTANCE AS INVALID
IJ38394	A SECURITY PROBLEM EXISTS WITH LOG FILES
IJ38395	RESTORE SYMLINKS FOR @DOUBLEBYTE JIM MODIFIER
IJ38396	PORTMAP / RPCBIND RETURNING WRONG ADDRESS FOR NIS CLIENT TO USE
IJ38397	FAILURE TO INSTALL ADDITIONAL RPMS DURING NIM MKSYSB INSTALL
IJ38398	IPSEC TUNNEL CONFIGURATION REJECTS SINGLE CERTIFICATE
IJ38399	NFSV4 MOUNT HANG TRIGGERED BY THE REMOUNT COMMAND
IJ38400	ARP -A CONSUMES HUGE MEMORY
IJ38401	SEA IS NOT REGISTERING ITS LINK STATUS CALL BACK FUNCTION
IJ38402	GSSD MEMORY LEAK / CORE DUMP
IJ38403	VIOSBR RUN WITH FREQUENCY REMOVES AUTOVIOSBR FROM CRON
IJ38404	RESTVG ON ON LARGE DISKS MAY FAIL CREATING FILESYSTEMS
IJ38405	MISSING /ETC/SECURITY/SECMIGCONF FILE WRONGLY LEADS TO SECLPM
IJ38406	UPDATEIOS TO 3.1.3.10 LEADS TO CLEANDISK UNAVAILABLE FOR PADMIN
IJ38408	ERASE DISKS OPTION NOT WORKING IN MAINTENANCE BOOT
IJ38409	CURRENT RULES FILE IS MISSING NEW ENTRIES AFTER UPDATEIOS
IJ38410	FB_DELAY IS NOT WORKING SOMETIMES IN SIMPLIFIED SEA SETUP
IJ38411	LKU FROM NIM MAY FAIL WITH:KSH: 0403-057 SYNTAX ERROR AT LINE 1
IJ38413	ospf_monitor command core dumps when passed very long argument
IJ38414	ntptrace command core dumps when passed very long arguments
IJ38415	USB Diagnostics download microcode source fails
IJ38416	Possible crash with tier remove when using SSP disk caching
IJ38417	for P10 lparstat now show Mode
IJ38418	Extraneous pthread_mutex_unlock call in clcomd
IJ38421	Text Editor disappeared in ja_JP.IBM-eucJP
IJ38422	ICON Editor not save state into session
IJ38423	Need to create caa_slave.stdio at install time
IJ38424	NETMON SHOULD RUN WHEN ONLY A SINGLE NODE IS UP
IJ38425	Kernel panic with m_get failure in cap6_decapsulate
IJ38426	Crash with disabling storage pool disk worker threads
IJ38427	Lpar crashed, where its running iperf
IJ38428	SUMA FAILS WITH JVMCFRE003 BAD MAJOR VERSION
IJ38430	Crash seen during IP output queue processinig.
IJ38431	Pool capacity is less than disk capacity after replace disk.
IJ38433	Crash at abend_trap when starting pool
IJ38435	pv -remove performance fix for SSP
IJ38437	Update Diagnostics VRMF
IJ38438	Diagnostics Disk Maintenance task lists unsupported disk
IJ38441	do_trace_control+000264 abend
IJ38442	LDAP USER/GROUP WITH PARENTHESES NOT FOUND
IJ38443	DU COMMAND MAY LOOP ENDLESSLY
IJ38444	JFS2 ROLLBACK FOR A LARGE FILESYSTEM MAY NOT COMPLETE CORRECTLY
IJ38445	SYSTEM MAY CRASH WHEN MOUNTING CDROM
IJ38446	LSLPP -L RPM PACKAGE OUTPUT GARBLED FOR CS_CZ LOCALE
IJ38447	MEMORY LEAK IN LDAP LOAD MODULE
IJ38448	BOS.RTE.SREAMS LEFTOVERS AFTER MIGRATION TO AIX 7.3
IJ38449	NON-DEFAULT SIZE FOR VIOSVC.LOG LEADS TO CORE_DUMP
IJ38450	Handle the strdup failures in exit path of cache update funcs
IJ38451	joinvg -f system crash during space reclaim of split PV's
IJ38452	DSI when deleting a PV when space reclaim is in progress
IJ38453	NIM Maintenance boot lvmstat error messages
IJ38454	NIM maintenance boot sees logredo64 error while mounting rootvg
IJ38455	lvmstat core dump when reporting space reclaim statistics
IJ38458	Update signed images inventory
IJ38459	lsvg/lspv not displaying total, free, used PPs properly for ver
IJ38461	TRUSTCHK POLICY CHANGES ARE NOT LOGGED TO SYSLOG
IJ38462	audit_svcstart() should not return -1
IJ38463	Crash during removal of active device
IJ38464	System crash during LPM or DPO after starting WLM
IJ38465	Crash in setnewrq during DLPAR CPU removal thread migration
IJ38466	BACKUP FROM A MOUNTED JFS2 SNAPSHOT MAY CRASH SYSTEM
IJ38467	Crash during restvg operation
IJ38469	crash in shmctl()
IJ38470	Opening a quota file and then force unmount causes a crash
IJ38471	EEXIST logged after LPM
IJ38472	nextroute() needs to take cached routes in account
IJ38473	ERROR IN DIIAGREAD CAUSES CRASH IN IKILL
IJ38474	LU surr crashed at uipc_usrreq func
IJ38475	Rare potential crash during LPM when using GZIP accelerator
IJ38477	Problem during FWAD init at boot with LMB sizes larger than 256M
IJ38479	IN RARE CASES JFS2 AIO_RETURN() HAS A STALE VALUE
IJ38480	Pthread sigsuspend returns an unsupported errno after LKU
IJ38481	fail to collect adapter dump when device is not in use
IJ38482	Firmware update returns zero for the FW version and logs error
IJ38484	Ethernet transmit timeouts followed by port DEAD state
IJ38486	Potential hang during storage device removal
IJ38487	JFS2 FILE SYSTEM CAN  GET MARKED CORRUPT AFTER EXTENDING FS.
IJ38488	/usr/include/stdio.h unmatched {}
IJ38489	Improve Live Partition Mobility RAS
IJ38490	no command need to display help about a ifstat32 tunable
IJ38520	LINK ERRORS ON NPIV CLIENT WHEN RUNNING CFGMGR ON VIOS
IJ38521	fcstat output for pend_cmd's may continue to increment.
IJ38523	Enabling SANCOM failing after LPM
IJ38524	Improve logging during violib DB function load
IJ38525	'vioservice' coredump on a cluster with more than 10 nodes.
IJ38526	Writing iso image to unformatted USB DVD media might hang
IJ38528	Add of LV backed paging device to CM database fails with error.
IJ38529	cryptstat can not load translation message for cmd usage
IJ38530	Add an error message for unsupported disks
IJ38531	Crash when set dpages_regular to 0x20000 on RoCE adapters
IJ38532	Firmware update causes diagnostic TU41 to fail
IJ38533	wrong error message with API testing
IJ38535	DR verify fails for DS8K
IJ38536	add ERRID_ACL_VIOLATION error ID to lnc2entdd device driver
IJ38537	Fix deadlock issue in VMRM HA solution.
IJ38538	VMRM Host Monitor inoperative after add VIOS
IJ38539	VIOS Hard Failures error message returned to KSYS.
IJ38540	Crash in processFcpError on disk open
IJ38541	Host monitor not started when adding VIOS.
IJ38542	Commands are getting hung and software program errors on errpt
IJ38543	Disk ping driver NDD_JOIN fails with ENOMEM
IJ38544	Configuring IP on Etherchannel madeup of vEths, may fail.
IJ38546	Failed rootvg paths may not automatically recover
IJ38550	VIOS crashed at d_unmap_list_tce+0000A4
IJ38759	LDAP USER NOT FOUND EVEN THOUGH IT IS PROPERLY DEFINED
IJ38760	IN ALL SUPPORTED LEVELS SMITTY DATE CAN'T CHANGE DATE AFTER 2038
IJ38761	GENCOPY -D /DEV/CDX FAILS TO COPY RPM FROM A CD TO DESTINATATION
IJ38763	Improve package signing process
IJ38765	IKDEB -P THROWS ERROR "A LSP FUNCTION DETECTED A BAD PARAMETER"
IJ38766	SEA HA state in limbo when changing real adapter
IJ38767	Cleanup Microcode files on Diagnostics Standalone CD
IJ38768	Error while listing rules for num_io_queues attribute
IJ38769	Crash in iostdel on rmdev of non-MPIO device with debug kernel
IJ38798	rules list not proper for redfish/bluefish fc adapters codedrop
IJ38801	cached route using stale pointers
IJ38951	Write past end of device does not return error code
IJ38954	Updating timezone data files to latest available for 2022
IJ39096	GETGROUPATTR MEMORY LEAK
IJ39099	fsck does not fix issues in dmap leaves correctly
IJ39100	Lpar crashed, where its running iperf serve
IJ39769	crash @ pmtu_alloc+000604