IBM Support

VIOS 4.1.1.0 Fix Pack Release Notes

Fix Readme


Abstract

Release notes for the 4.1.1.0 VIOS Fix Pack release

Content

VIOS 4.1.1.00 Release Notes

Package Information

PACKAGE: Update Release 4.1.1.00
IOSLEVEL: 4.1.1.00

VIOS level is

The AIX level of the NIM Master level must be equal to or higher than

Update Release 4.1.1.00

AIX 7300-02-02

General package notes

Be sure to heed all minimum space requirements before installing.

Review the list of fixes included in Update Release 4.1.1.00

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

Microcode or system firmware downloads for Power Systems

If the VIOS being updated has filesets installed from the VIOS Expansion Pack, be sure to update those filesets with the latest VIOS Expansion Pack if updates are available.

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

$ ioslevel

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

Upgrade to VIOS 4.1.x

  • Existing VIOS systems with supported versions of 3.1.x.y can be upgraded to VIOS version 4.1.1.0 (DVD image) or 4.1.1.00 (Flash image) using viosupgrade tool . Although it is recommended to be on VIOS 3.1.4.30 or later SP level before upgrading to VIOS 4.1.x level.

  • VIOS systems with SSP configuration must be on 3.1.3.x or later level before upgrading to 4.1.x level or adding 4.1.x nodes into cluster.

  • If Active Memory Sharing (AMS) is configured on the VIOS, it should be un-configured before upgrading. You may refer the link on how to un-configure.

  • Before upgrading, you may read the viosupgrade blog in PowerVM Community which explains various scenarios.

For Customers using NVMe Over Fabric (SAN) as their Boot Disk

Booting from NVMeoF disk may fail if certain fabric errors are returned, hence a boot disk set up with multiple paths is recommended.  In case there is a failure to boot, the boot process may continue if you exit from the SMS menu. Another potential workaround is to discover boot LUNs from the SMS menu and then retry boot.

Note

If the Virtual I/O servers are installed on POWER10 systems and configured with “32Gb PCIe4 2-Port FC Adapter, Feature Code(s) EN1J and EN1K”, then the requirement is to update the adapter microcode level to 7710812214105106.070115 before updating the Virtual I/O server to 4.1.1.00 level.

Please refer to the release notes at this link

HIPER issue: If you are upgrading to VIOS 3.1.4.50 or 4.1.1.x or above version please consult this link

4.1.1.00 New Features

VIOS 4.1.1.00 adds the following new features:

VFC enhancements

  • I/O commands timeout improvements in VFC stack on VIOS. It handles starvation conditions for certain higher IO size workloads ( 256K and above ). It  introduces 2 new attributes ( num_local_cmds and bufs_per_cmd ) at VFC host adapter device level on VIOS to manage resources like memory better overall.

  • Improve Virtual FC Performance Diagnostics provide support for the VFC client partitions ( "IBM i" in this release of 2024) for collecting I/O response times from the VIOS as a whole subsystem, including the timestamps recorded on different layers in NPIV stack on VIOS and FC adapters.

NFS mounted ISO images support in Virtual Media Library

This release adds support for NFS Mounted ISOs in Virtual Media Library which allows to load ISO images from a centralized NFS server, eliminating need for repeated copying of ISO images across multiple VIOS. This saves storage space and time, maintains consistent images, and supports both NFS V3 and V4, allowing multiple images to be linked into the repository.

The ’mkvopt’ command is enhanced to support new option –nfslink which creates a symbolic link  to the specified NFS ISO file, in the repository.

$ mkvopt -name <image_name_in_VML_repository> -file /mnt/<mounted_ISO_file.iso> -nfslink -ro

Refer the PowerVM Community blog  for details.

Remove unwanted language message filesets

The updateios command is extended to support below options to remove unwanted language message filesets.

    1. -listlang : This option lists all the installed language message filesets.
    2. -rmlang : This option should be used to remove language filesets.
    3. -preserve : This option must be used along with -rmlang to specify the languages to preserve. Rest of the language message filesets will be removed.

viosupgrade enhancements

The major enhancements done in viosupgrade in this release are as follows.

  • viosupgrade will now preserve device names for vfchost/vhost adapter devices, fcnvme, nvme, fscsi, iSCSI devices, network adapters, hdisks etc. by default. A new flag -skipdevname is introduced to skip the above device names preservation.

Shared Storage Pool enhancements

The cluster -status -verbose command is enhanced to display additional storage pool specific information.

The clutil command is introduced with the -o pingcheck option to verify if the network
communication among the SSP cluster nodes are in the working state.

Live Partition Mobility (LPM) Validation enhancement for NPIV storage

Discrepancies in LUN IDs for disks between source and destination hosts can arise from misconfigured LUN masking at the storage level. For instance, the active and inactive WWPNs of a client’s virtual FC adapter may be configured as separate hosts at the storage system, then can assign the same LUNs to these hosts in different orders. This results in varying LUN IDs associated with each WWPN.
Since such configuration can lead to LUN access issues after LPAR migration, the validation algorithms have been enhanced to detect such misconfigurations and report to the user.

VIOS 4.1.1.0 has virtual ethernet multi queue feature

This will help to drive more network traffic through virtual ethernet trunk adapter. By default, there will be 12 transmit queues and zero receive queues (legacy receive mode). To increase the bandwidth, one can increase the number of receive queues on virtual ethernet adapter in VIOS by tuning queues_rx attribute of the virtual ethernet adapter. However, using multiple Receive queues to drive more traffic will require more CPU resources.

Other enhancements

  1. Enhancement in alt_root_vg command, to run it in phases. This enhancement allows the alt_root_vg command to separate the cloning phase from the update phase.
  2. Enhancement in chdev command, a new option -dynupdate is added to support dynamic updates of supported device attributes.

Hardware Requirements

Please check this link for supported hardware.

Known Capabilities and Limitations

The following requirements and limitations apply to Shared Storage Pool (SSP) features and any associated virtual storage enhancements.

Requirements for Shared Storage Pool

  • System requirements per SSP node:
    • Minimum CPU: 1 CPU of guaranteed entitlement
    • Minimum memory: 4GB
    • Storage requirements per SSP cluster (minimum): 1 fiber-channel attached disk for repository, 10 GB
    • At least 1 fiber-channel attached disk for data, 10GB

Limitations for Shared Storage Pool

Software Installation

  • When installing updates for VIOS Update Release 4.1.1.00 participating in a Shared Storage Pool, the Shared Storage Pool Services must be stopped on the node being upgraded.

SSP Configuration
 

Feature

Min

Max

Number of VIOS Nodes in Cluster

1

16*

Number of Physical Disks in Pool

1

1024

Number of Virtual Disks (LUs) Mappings in Pool

1

8192

Number of Client LPARs per VIOS node

1

250*

Capacity of Physical Disks in Pool

10GB

16TB

Storage Capacity of Storage Pool

10GB

512TB

Capacity of a Virtual Disk (LU) in Pool

1GB

4TB

Number of Repository Disks

1

1

Capacity of Repository Disk

10GB

1016GB

Number of Client LPARs per Cluster

1

2000

*Support for additional VIOS Nodes and LPAR Mappings:

Prerequisites for expanded support:

  • Over 16 VIOS Nodes requires that the SYSTEM (metadata) tier contains only SSD storage.
  • Over 250 Client LPARs per VIOS requires each VIOS have at least 4 CPUs and 8 GB memory.

Here are the new maximum values for each of these configuration options, if the associated hardware specification has been met:
 

Feature

Default Max

High Spec Max

Number of VIOS Nodes in Cluster

16

24

Number of Client LPARs per VIOS node

250

400

Other notes:

  • Maximum number of physical volumes that can be added to or replaced from a pool at one time: 64
  • The Shared Storage Pool cluster name must be less than 63 characters long.
  • The Shared Storage Pool pool name must be less than 127 characters long.
  • The maximum supported LU size is 4TB, however for high I/O workloads recommendation is to use multiple smaller LUs as it will improve performance. For example, using 16 separate 16GB LUs would yield better performance than a single 256GB LU for applications that perform reads and writes to a variety of storage locations concurrently.
  • The size of the /var drive should be greater than or equal to 3GB to ensure proper logging.


Network Configuration

  • Uninterrupted network connectivity is required for operation. i.e., the network interface used for Shared Storage Pool configuration must be on a highly reliable network which is not congested.
  • A Shared Storage Pool configuration can use IPV4 or IPV6, but not a combination of both.
  • A Shared Storage Pool configuration should configure the TCP/IP resolver routine for name resolution to resolve host names locally first, and then use the DNS. For step by step instructions, refer to the TCP/IP name resolution documentation in the IBM Knowledge Center.
  • The forward and reverse lookup should resolve to the IP address/hostname that is used for Shared Storage Pool configuration.
  • It is recommended that the VIOSs that are part of the Shared Storage Pool configuration keep their clocks synchronized.


Storage Configuration

  • Virtual SCSI devices provisioned from the Shared Storage Pool may drive higher CPU utilization than the classic Virtual SCSI devices.
  • Using SCSI reservations (SCSI Reserve/Release and SCSI-3 Reserve) for fencing physical disks in the Shared Storage pool is not supported.
  • SANCOM will not be supported in a Shared Storage Pool environment.


Shared Storage Pool capabilities and limitations

  • On the client LPAR Virtual SCSI disk is the only peripheral device type supported by SSP at this time.
  • When creating Virtual SCSI Adapters for VIOS LPARs, the option "Any client partition can connect" is not supported.
  • VIOSs configured for SSP require that Shared Ethernet Adapter(s) (SEA) be setup for Threaded mode (the default mode). SEA in Interrupt Mode is not supported within SSP.
  • Client LPARs are not supported if they use JFS as their filesystem.  If JFS is used, there is a risk of data corruption in the event of a network outage.  JFS2 and other file systems are unaffected by this issue.

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

VIOS upgrades with Third Party Software

When the user upgrades from 3.1.x.y to 4.1.0.00 level and above, third-party software is not packaged with the IBM supplied mksysb image. User needs to install the respective third-party software after the upgrade is complete and run viosupgrade -o rerun to restore the respective devices.

Updating from VIOS version 4.1.0.00

VIOS Update Release 4.1.1.00 may be applied directly to any VIOS at level 4.1.0.00.

Before installing the VIOS Update Release 4.1.1.00

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.

  1. To unload media images, run the following commands on all Virtual Target Devices that have loaded images.

unloadopt -vtd <file-backed_virtual_optical_device >

  1. 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 3.1.x.y or later, supports rolling updates to release 4.1.1.00 for SSP clusters.

The rolling updates enhancement allows the user to apply Update Release 4.1.1.00 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 3.1.x.y  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 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 if required
    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:

Note: The "padmin" user is restricted to redirect command output to a file, you must be in the root shell. Use "oem_setup_env" to become a root user.

 

oem_setup_env

# 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 1:

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 2:

Updateios command is suggested to run using “-install” option. This option installs new base-level filesets that are shipped along with the existing fileset updates. For example: enabling resize command in VIOS 4.1.1.00 onwards.

Running updateios command with “-install” flag may lead to few fileset update error messages that can be ignored. See below the list of filesets for which the error message can be ignored:

X11.apps.msmit 7.3.3.0                    # AIXwindows msmit Application

bos.msg.ca_ES.mls.rte 7.3.3.0             # Trusted AIX Messages - Catalan

bos.msg.ca_ES.svprint 7.3.3.0             # System V Print Subsystem Msg...

bos.msg.de_DE.mls.rte 7.3.3.0             # Trusted AIX Messages - German

bos.msg.de_DE.svprint 7.3.3.0             # System V Print Subsystem Msg...

bos.msg.en_US.mls.rte 7.3.3.0             # Trusted AIX Messages - U.S. ...

bos.msg.es_ES.mls.rte 7.3.3.0             # Trusted AIX Messages - Spanish

bos.msg.es_ES.svprint 7.3.3.0             # System V Print Subsystem Msg...

bos.msg.fr_FR.mls.rte 7.3.3.0             # Trusted AIX Messages - French

bos.msg.fr_FR.svprint 7.3.3.0             # System V Print Subsystem Msg...

bos.msg.it_IT.mls.rte 7.3.3.0             # Trusted AIX Messages - Italian

bos.msg.it_IT.svprint 7.3.3.0             # System V Print Subsystem Msg...

bos.msg.pt_BR.mls.rte 7.3.3.0             # Trusted AIX Messages - Brazi...

bos.msg.pt_BR.svprint 7.3.3.0             # System V Print Subsystem Msg...

bos.net.tcp.rcmd 7.3.3.0                  # TCP/IP Remote Command Client...

bos.net.tcp.rcmd_server 7.3.3.0           # TCP/IP Remote Command Server...

Also, In case you choose to run updateios without “-install” flag, you will not see any of the error messages above but you will lose installation of resize command and “RSCT Software Resource Manager” along with a bunch of language message filesets for locales “it_IT, fr_FR, ca_ES, pt_BR, de_DE, es_ES”. Below is the list of filesets that you will miss:

bos.msg.it_IT.txt.tfs - Text Formatting Services Msgs - Italian

bos.msg.it_IT.net.ipsec - IP Security Messages - Italian

bos.msg.it_IT.alt_disk_inst - Alternate Disk Install Msgs -Italian

bos.msg.it_IT.diag.rte - Hardware Diagnostics Messages - Italian

(Same filesets as above for fr_FR, ca_ES, pt_BR, de_DE, es_ES)

X11.apps.xterm - AIXwindows xterm Application

X11.apps.xdm - AIXwindows xdm Application

X11.apps.custom - AIXwindows Runtime Common Directories

X11.apps.config - AIXwindows Configuration Applications

X11.apps.clients - AIXwindows Client Applications

rsct.msg.EN_US.basic.rte - RSCT Basic Msgs - U.S. English (UTF)

rsct.opt.softwarerm - RSCT Software Resource Manager

rsct.msg.en_US.opt.software - RSCT Software RM Msgs - U.S. English

rsct.msg.EN_US.opt.software - RSCT Software RM Msgs - U.S. English (UTF)

Warning:

Update to VIOS 4.1.1.00 will update ios.database.rte fileset which might throw below errors, and they can be ignored:

        3001-408  The user "vpgadmin" has an invalid lastupdate attribute.

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 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 ioslevel command, which should indicate that the ioslevel is now 4.1.1.00.

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>

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

  1. Restart the VIOS.

shutdown –restart

  1. Verify that the Media Repository is operational by running this command:

lsrep

Content modified in this release

Software Updated

- Two versions of postgres database (version 15.6 and 13.14) are included in base image. Postgres version 13 is required to support mixed mode cluster where node versions 3.1.4.x and 4.1.0.x are part of the cluster.

Content removed from 4.1.0.x release and above

ITM Agents software

        ITM (IBM Tivoli Monitoring) filesets are not part of VIOS 4.1.0.00 & above versions. Users need to download and install the ITM software from an external location. The ITM VIOS Premium Agent and ITM CEC Base Agent can be downloaded and installed separately as part of an updated IBM Tivoli Monitoring System P Agents 6.22 Fix Pack 4 or later bundle. Here is a link to the readme file containing information about how to obtain the image and instructions for installing.  When these agents are installed in the default directory of /opt/IBM/ITM, they can continue to utilize the cfgsvc, startsvc, and stopsvc commands to configure, start and stop the agent.

AMS

        Active Memory Sharing (AMS) feature is removed.

Software Removed

        Following filesets that are deemed not necessary are removed.

  • bos.net.tcp.rcmd, bos.net.tcp.rcmd_server (A copy is saved under: /usr/sys/inst.images/installp/ppc)
  • cas.agent tivoli.tivguid
  • rsct.opt.fence.blade rsct.opt.fence.hmc
  • sysmgt.cim.providers.metrics sysmgt.cim.providers.osbase
  • sysmgt.cim.providers.scc sysmgt.cim.providers.smash
  • sysmgt.cim.smisproviders.hba_hdr sysmgt.cim.smisproviders.hhr
  • sysmgt.cim.smisproviders.vblksrv sysmgt.cimserver.pegasus.rte
  • Java7.jre Java7.sdk Java7_64.jre Java7_64.sdk
  • itm.cec.agent itm.premium.rte itm.vios_premium.agent
  • bos.net.nfs.server devices.vdevice.IBM.vfc-client.rte
  • X11.adt.ext X11.adt.motif X11.apps.clients X11.apps.config X11.apps.custom X11.apps.msmit X11.apps.xdm
  • X11.apps.xterm X11.base.xpconfig X11.compat.adt.Motif12 X11.compat.lib.Motif10 X11.compat.lib.Motif114
  • X11.compat.lib.X11R3 X11.compat.lib.X11R4 X11.Dt.bitmaps X11.Dt.helpinfo X11.Dt.helpmin X11.Dt.helprun
  • X11.Dt.lib X11.Dt.rte X11.Dt.ToolTalk X11.fnt.coreX X11.fnt.deform_JP X11.fnt.fontServer X11.fnt.Gr_Cyr_T1
  • X11.fnt.ibm1046 X11.fnt.ibm1046_T1 X11.fnt.iso1 X11.fnt.iso2 X11.fnt.iso3 X11.fnt.iso4 X11.fnt.iso5
  • X11.fnt.iso7 X11.fnt.iso8 X11.fnt.iso8_T1 X11.fnt.iso9 X11.fnt.iso_T1 X11.fnt.ksc5601.ttf X11.fnt.ucs.cjk
  • X11.fnt.ucs.com X11.fnt.ucs.ttf_CN X11.fnt.ucs.ttf_extb X11.fnt.util X11.loc.en_US.base.lib
  • X11.loc.en_US.base.rte X11.loc.en_US.Dt.rte X11.vsm.lib

Fixes included in this release

The list of fixes in 4.1.1.00

APAR

Description

IJ41832

Install images for ICU4C.adt

IJ47979

NFS CAN ABEND WITH TRUSTED BINARY/SCRIPT ON AN NFS FS

IJ47980

SAVEVG FAILS TO BACKUP SOME ATTRIBUTES OF CONCURRENT-CAPABLE VGS

IJ47982

Errors Observed during cache.mgt fileset installation.

IJ47984

Memory leak or system crash when using cached routes

IJ47985

rping fails first time when there is no ARP entry of target node

IJ47990

SEA creation fails when ipv6 offload is not supported

IJ47991

Boot hang when FC lg_term_dma attr is chaged with ODM min value

IJ47993

WHEN VIOS GOES DOWN, VSCSI DISK I/O MIGHT HANG

IJ47994

In Etherchannel-teaming mode possible to add same adapter name

IJ47996

Validation failure of lpmp16 in Iteration 11.

IJ47998

lsmap not listing the client id

IJ48001

DSI IN XFIDTONAME DUE TO  UNINITIALIZED VNODE POINTER

IJ48002

get_stack_size causing lock contention on U_handy_lock

IJ48007

EID being logged in errpt during the adapter firmware upgrade

IJ48008

ioscli snap -gzip <SCRIPT> not working properly.

IJ48011

unamex should  be declared in sys/utsname.h

IJ48012

LDATA_DESTROY CALLED AFTER FAILED LDATA_CREATE CAUSES AN ASSERT

IJ48101

missing dr/scripts/ entries in TSD

IJ48103

SSL not enabled for NIM Primary, Alternate and NIM client

IJ48105

Incomplete error msg on LU cmd if NIM client is not conf

IJ48107

nim master and client conn ok,nim cmds are failing

IJ48109

alt_rootvg_op -X is removing vg, which is nt copy of rootvg

IJ48119

System crash while stop virtual initiator (SCIOLSTOPINITR)

IJ48130

lpar crashed @validate_thread_runq

IJ48208

ALT_DISK_INSTALL CLEANS ALTINST_ROOTVG IF SETUP_WORKDIR FAILS

IJ48210

improper Error message while creating sea in sharing md

IJ48212

Console getting spanned while updating mcr.rte fileset

IJ48214

NX accelerator becomes unavailable after LPM

IJ48215

Configured 1500 mtu is reset to 9000 if use_jumbo_frames=set

IJ48246

Update Diagnostics VRMF for Fall 2023

IJ48254

Avoid starting ksys_hsmon in non VMRM HA environment.

IJ48255

REDUCEVG MAY ERROR OUT ON AIX 7.3 CONVERTED SVG

IJ48256

A potential security issue exists

IJ48363

CHNFSMNT CAN INCORRECTLY MODIFY OPTIONS IN /ETC/FILESYSTEM

IJ48364

Potential undetected data loss by using zlibNX

IJ48367

vmstat output fi/fo seems incorrect when system is in a paging

IJ48370

eccConnect.properties misses new attrs. of 1163894 after u/m

IJ48377

Observing SCSI path recovery failed on cable pull tests

IJ48378

APPLYING BOS.RTE.SERV_AID UPDATE MAY LOOP INFINATELY

IJ48381

bosboot command fails with not enough space error

IJ48383

mmap issue, for SPEC1170 specification, when mapping memory at

IJ48384

SAVEBASE MAY FAIL WITH 4K BLOCK SIZE DISK

IJ48386

create_ova created image will not import into PowerVC

IJ48387

Prereq between OFED, mlxentdd, mlxcentdd and unix_64 for RoCEV2.

IJ48425

TAIL -NXX MAY DISPLAY MORE LINES

IJ48426

tail(1) misidentifies directories as files

IJ48427

Update AIX cmds and scripts to use ksh93 instead of ksh

IJ48429

dd doesn't write status to error stream when SIGINT

IJ48430

cksum issue with multiple argument when env XPG_SUS_ENV is set

IJ48431

tail -c fails with zero exit status

IJ48432

A potential security issue exists

IJ48434

TRUSTCHK STOP_UNTRUSTD=TROJAN RESULTS IN LIBC.A ERRORS

IJ48435

MULTIPLE NIMADM UPDATES IN PARALLEL MAY FAIL

IJ48437

Boot time tunables overwritten on systems with LMB size > 256MB

IJ48438

lpar may crash in netkmem_dr_cpu_remove

IJ48439

Lpar crashed while running kernel extn test for PKS

IJ48440

cdpd does not add multicast address during port add operation

IJ48441

A potential security issue exists

IJ48442

A potential security issue exists

IJ48443

Increase max ldata pool limit in pfcurh

IJ48444

n/a

IJ48448

After Inactive LPM lpar not coming up

IJ48450

VIOS crashed with stack ___memmove64 -> npiv_passthru_

IJ48556

pvrecovmd allowd on diff disks

IJ48557

hdcryptmgr CLI can core dump with corrupted LV meta data

IJ48560

ibv_devinfo -e does not show new interface info with out reboot

IJ48561

LSUSER MAY NOT DISPLAY ALL OF AN LDAP USER'S GROUPS

IJ48562

unix socket lock pair problems in sofree2

IJ48563

System Call Input Validation - netinfo

IJ48592

PASSWORD CHANGE ATTEMPT FAILS

IJ48594

lpar crashed @ nfs4_put_resarray

IJ48599

READVGDA PREFERRED READ VALUE FOR SVG W/ MIRROR POOLS INCORRECT

IJ48635

console spamming Successfully updated the Kernel

IJ48636

od -t fails with exit code zero

IJ48638

echo writes additional new line

IJ48641

A potential security issue exists

IJ48642

vios upgrade may hang in cluster environment.

IJ48648

BOS.ESAGENT UPGRADE MAY FAIL IF IBM.ESAGENT WAS ACTIVATED

IJ48649

lpar crashed @tcp_trace+00009C

IJ48693

LDAP SERVER MARKED DOWN DOESN'T RECOVER QUICKLY ENOUGH

IJ48694

SECLDAPCLNTD NESTED GROUP HANG, CORE, OR ERRORS WITH ITDS

IJ48695

Exitstatus wasn't found in standard output

IJ48696

SWITCH.PRT FAILS IF THERE ARE EXISTING JOBS

IJ48697

Update libodm to use 64 bit libviocmnotify.a

IJ48699

wcsxfrm_l() returns incorrect value when argument 'n' is 0

IJ48700

ibv_create_ah() will fail for RoCEv2 mode

IJ48701

A potential security issue exists

IJ48702

A potential security issue exists

IJ48704

Boot-image creation error in nimadm phase 8

IJ48706

fw-assisted dump goes to panic break - H/W Page Ta

IJ48707

VIOS CAN CRASH DURING ASYNC EVENT ON UNMAPPED VFCHOST

IJ48759

clsnmp command not working after 5 seconds.

IJ48767

'geninstall -kd' didnt throw any syntax error

IJ48768

block vpmem LV in vscsi map.

IJ48782

MLXCENTDD CRASHED AT MLXCENT_CMDQ_RESERVE_MBOX_TYPE

IJ48783

DISK OPERATION ERROR: PATH HAS FAILED

IJ48797

DEFERED:ISST:ASO coredump at pthread_kill:dialpar01

IJ48839

CHDEV TO CHANGE AN SEA FAILS WITH RBAC USER

IJ48840

LPAR may crash when ipsec tunnels are created on top of vxl tunnels.

IJ48858

Don't remove vg,if it is not part of rootvg

IJ48859

Don't remove vg,if it is not part of rootvg

IJ48860

hmcauth command failing with c_rsh -e

IJ48897

RESTORE MAY DISPLAY WRONG FILE TIMESTAMP

IJ48973

Error while fetching cluster details.

IJ48975

decauto10 crashed at panic_trap

IJ48980

SNMPDV3 LOGS INCORRECT MESSAGE WHEN STOPSRC IS ISSUED

IJ48981

RESTVG WITH -R OPTION FAILS WITH OUTLINE LOGS

IJ48982

NIM MKSYSB RESTORE MAY HANG FOR ENTERPRISE_CLOUD EDITION

IJ48986

spurious message from alt_rootvg_op -X on some VGs

IJ48991

SYSTEM MAY CRASH WITH LVM SERIALIZED IO ENABLED ON LV

IJ49004

After 7.3 migration, sysdumpdev -l returns error

IJ49022

VF INTERFACE ATTACHED TO VNIC NOT REMOVED DURING LPM

IJ49024

htxcmdline -createmdt command got hung

IJ49025

viosupgrade with paging space device did not fail

IJ49027

Shell returns non-zero exit status

IJ49051

COMMAND CHDEV SAVE INCORRECT IPV4 ALIAS NETMASK IN ODM

IJ49052

BADLOCK ISSUE CAUSING NFS ACCESS FAILURE WITH ESTALE

IJ49053

LKU: SURROGATE CRASH IN "IN6_DELMULTI_SOURCE"

IJ49054

topasrec start using smitty gave usage error

IJ49055

EXPR: NOT FOUND ERRORS WHILE RESTORING MULTI VOLUME MKSYSB

IJ49056

update viosbr help and manpage for -dr option

IJ49059

Probable system crash in cvfsc_cmd_recv

IJ49083

restore memory leaks

IJ49099

SEA with incorrect error code for failure.

IJ49100

lsdev -state does not fail for wrong input

IJ49101

Error msg handeling for Phase2/3 foralt_disk_copy.

IJ49102

nimadm fails for 72X "mksysb" to 73D "mksysb" migration

IJ49103

Lower packet rate with higher number of thread

IJ49250

SNAPSHOT -LIST -LU MAY LIST CLIENT IMAGE LUS

IJ49251

ALT_DISK_COPY UNFORMATTED ERRORS ON EFS MOUNT POINTS

IJ49253

Update AIX cmds and scripts to use ksh93 instead of ksh

IJ49255

RULESCFGSET COMMAND FAILS AFTER VIOS UPDATE

IJ49256

Fix warnings reported by ios.cli package

IJ49259

NPIV CLIENT REQUESTED IMPLICIT LOGO, DRIVER SENT EXPLICIT LOGO

IJ49260

Remove the inquiry command buffer size check as per spec

IJ49261

FCSTAT OUTPUT FOR PEND_CMD'S MAY CONTINUE TO INCREMENT

IJ49262

INVALID TZ WILL CAUSE DBN ELECTION INSTABILITY

IJ49263

VIOD_BKPS DIR CONTAINS TOO MANY LOGS

IJ49270

albertv1

IJ49272

DBN connection fails after upgrade to VIOS 4.1

IJ49304

NPIV client crashed with sysdump after EEH+IO

IJ49305

Enable parallel nimadm install

IJ49310

SNAP COMPRESSION FAILS SILENTLY AND SNAP NOT USEABLE ON 7300-01

IJ49311

installp fails when a package is specified AND DSP policy is ON

IJ49435

NFS ver4 mount may fail at boot if nfsrgyd is slow to activate

IJ49436

LKU hung at 000e LED - RAW LVs - 2nd iteration

IJ49438

SSL handshake error when using proxy server

IJ49439

Driver unrecoverable if rmdev,nddctl,entstat run in parallel

IJ49441

vNIC Adapter reset causes ping to fail

IJ49469

LKU preview may fail to identify the PKS migration support

IJ49489

Set ANA Delay as per ANATT

IJ49493

directory permission not restored with viosupg

IJ49496

nim_master_recover cmd removed alt_mstr

IJ49501

INCORRECT ERROR ON LDAP USER PASSWORD CHANGE

IJ49502

THE DEFAULT DOWNLOAD PATH OF EMGR_CHECK_IFIXES IS /TMP/IFIX

IJ49503

tail -c fails with zero exit status

IJ49504

DSI NPIV_REAL_FCSCSI_ASYNC

IJ49505

SRIOV VF Diagnostic stalled or results in failure

IJ49506

VIOS_VFC_HOST WITH ERROR NPIV_ERR_006E RC:EINVAL ALREADY STARTED

IJ49604

ERRORS IN NMON "PEAK KB/S READ+WRITE" COLUMN

IJ49605

ISSUE FACED WHILE CHANGING THE IKE ENTRIES USING SMITTY TOOL

IJ49606

dump device message in errpt

IJ49607

cron entries merging fails during upgrade

IJ49608

MLXENTDD DRIVER IS NOT HAVING ENOUGH DMA_SIZE MEMORY

IJ49611

Microcode installation message

IJ49647

liveupdate may fail catch PKS migration support during preview

IJ49693

Avoid ATTENTION msg

IJ49694

correct dev/null to /dev/null in alt_disk_copy.sh, 1174724

IJ49730

LI #OEP Bar0 changes for honouring odm configuration

IJ49733

VIOS SNAP LOG COLLECTION FROM HMC FAILS

IJ49735

restvg -S, enc policy mismatch, not removing encr

IJ49737

Incorrect print queue status

IJ49750

0590-102 INCORRECT PROFILE - UPDATEIOS FROM 3.1.4.10 TO 3.1.4.21

IJ49752

OFED crash in cm_alloc_response_msg() while interface detached

IJ49809

OSLEVEL NOT WORKING FOR USERS WITH LONG UIDS

IJ49813

fwupdate on multipath splitter device ret wrong msg

IJ49814

CHVG -G CAN CRASH THE SYSTEM IF LVMBB IS PROCESSING ON SAME VG

IJ49833

Irrelevant command being passed to binder

IJ49848

rmdev may fail with ODM lock timeout error

IJ49849

nim LU hangs after completion

IJ49891

Inactive LPM is failing with LU validation syst

IJ49894

Update kernel copyright notice for 2024

IJ49896

THE EMGR -L OUPUT IS NOT ALIGNED

IJ49898

NIM MKSYSB RESTORE HANG DUE TO DATADAEMON CORE DUMP

IJ49901

artexget may fail to collect expected tunables data

IJ49941

CRASH IN TIMER INTERRUPT AFTER LKU IN MEMORY CONSTRAINED ENV

IJ49951

LPM adapter fails after an adapter reset on VFC client.

IJ49952

sscanf gives wrong output/segmentation fault.

IJ49967

A potential security issue exists

IJ49984

SYSTEM CRASH IN LDATA_ALLOC() WITH ESYSERROR_SL_RECURLOCK

IJ49986

SECLDAPCLNTD GROUP CACHE NOT ALWAYS WORKING

IJ49987

SECLDAPCLNTD SLOW MEMORY LEAK

IJ49988

SECLDAPCLNTD GROUP CACHE IMPROVEMENT

IJ50051

MAKE SECLDAPCLNTD SERVER CONNECTION TIMEOUT ADJUSTABLE

IJ50052

RXQ KPROCS CAN RUN CONTINUOUSLY DISABLED AT INTPRI3 ON SOME CPUS

IJ50054

Crash while upgrading firmware on Mellanox network adapter

IJ50092

Adding more traces in semop

IJ50112

/proc filesystem missing after OS migration

IJ50190

crashed at lock_free_com+000058

IJ50191

NETISR.H INCLUDES FILE SYS/LIBSYSP.H WHICH IS NOT SHIPPED

IJ50192

PVID load up criteria missing in datadaemon

IJ50203

System crash in ld_execload()

IJ50205

SYSDUMPDEV: UNEXPECTED ERROR MESSAGE WITH TRADITIONAL DUMP

IJ50227

Few OFED verbs failing when RoCEv2 was enabled

IJ50250

CRASH IN EXEC OR EXIT PATH FOR PROCESS USING NX/GZIP ON 7.3.1

IJ50251

Linker asked to preserve internal global warning from libLTO

IJ50254

System crash in ras_if_gne_callback()

IJ50258

UMOUNT FAILS WHEN READLINK AND RMDIR RUN IN PARALLEL IN /PROC

IJ50260

BOOT OR DUMP FAILURE ON NVME DISKS DUE TO INCORRECT FW PATH NAME

IJ50297

VIOS crashed during boot time with stack ct_hook1, afte

IJ50299

Verify the System Dump failing

IJ50300

Kbd/mouse not detected with KVM switch

IJ50301

AIX takes too long to configure new Samsung nvme

IJ50382

NPIV CLIENT REQ IMPLICIT LOGO, QL DRIVER SENT EXPLICIT LOGO

IJ50384

Wrong FFC Code For an SRN-802

IJ50388

mksysb to "client" successful parallel migration gen

IJ50392

nimadm cmd help changes for bootlist and reboot flags

IJ50404

NIMHTTP WITH SECURE NIMSH FAILS

IJ50491

NX window close operation may fail for stale windows

IJ50492

CRL DOWNLOAD FAILS AFTER CHANGE IN CERTIFICATE SERVER

IJ50493

EMGR_DOWNLOAD_IFIX FAILS WITH SSL CONNECTION FAILED

IJ50495

errpt while promoting data from a 4K device when it is cached.

IJ50496

A potential security issue exists

IJ50522

MULTICAST BIND FAILS ON VLAN

IJ50523

AIXPERT COMINETDCONF SCRIPT

IJ50524

SYSTEM CAN CRASH IN PFFINDTYPE() ON AIX 7.3 AND ABOVE

IJ50526

ASO NOT DISABLED AFTER UPDATE FROM VIOS 3.1.4.0 TO 3.1.4.10

IJ50537

Potential security issue sendmail_advisory4.asc

IJ50542

IO HANG IN CAVIUM FIBRE ADAPTER AFTER LINK DOWN EVENT.

IJ50543

sysdumpdev -e hung looping in aixdiskpcmke:getPathDataSize

IJ50546

fw level from kdb is not lsting latest version

IJ50547

vnic kproc names should not have space characters

IJ50550

Kookaburra/Kite 15TB reports error after NS delete

IJ50552

lscfg description for Shearewater Gen5 NVMe is generic

IJ50553

shared ns deleted though attached to another cntlr

IJ50554

UNRELEASED ZOMBIE FILES CAUSING FULL FILESYSTEM ISSUE

IJ50556

llvupdate -u in parallel to llvupdate -a is

IJ50608

clsnmp walk sysDescr shows incorrect OS level

IJ50609

NO -L DISPLAY WRONG VALUE

IJ50610

DURING LKU RESTORATION OF THE TCPTR TABLE MAY CAUSE A HANG

IJ50612

AIX NFSv4 Client to Linux NFS Server- fail to copy

IJ50614

VIOS upgrade fails between major vios versions

IJ50615

set the maxexpired = -1 for padmin for install and update

IJ50616

userdel command error with -r flag

IJ50619

LOGINS HANG WITH TRUNCATED LASTLOG FILE

IJ50620

crash @aso_bufmgr_put_data

IJ50647

Potential security issue libxml2_advisory6.asc

IJ50648

Timezone tool is not able to handle the SIGSTOP signal action

IJ50676

NDD_TRACE HOOKS ARE NOT CLEARED WHEN STOP IPTRACE

IJ50682

Improper error msg for wrong country code

IJ50688

FVT defect fixes (03/29/2024)

IJ50690

POSSIBLE CONTINUOUS FCA_ERR6 0X2F AND FCA_ERR2 0X27 ERRPT ERRORS

IJ50693

system crash at emfc_init_dma_handle, when 64K TCE enab

IJ50694

Commands such as lsmpio, lspath probably will hang

IJ50696

KSH CAN DUMP CORE WHEN DISCONNECTING REMOTE LOGIN CONNECTION

IJ50705

NIM hangs even after LKU is completed successfully

IJ50730

ike cmd=list db shows incorrect Remote IP Address

IJ50731

viosupgrade tool with P option, failed to dispay status

IJ50779

LSPV CORE DUMPS IN ODM_GET_FIRST()

IJ50780

vioscmd.sh is timed out when starting cluster se

IJ50782

fw level in kdb not listing latest for partner adapte

IJ50784

LLDPCTL ADD FAILING ON VIOS 3.1.4.21

IJ50790

SAVEBASE CAN FAIL WITH 4K DISKS IN ROOTVG AND LARGE ODM

IJ50807

MEMORY LEAK IN PERFSTAT_PROCESS LIBPERFSTAT API

IJ50808

FTPD IS INCONSISTENT WHEN "READWRITE:" STATEMENT IS INVALID

IJ50817

GDLC IN ETHERCHANNEL ENVIRONMENT, MAY NOT WORK PROPERLY.

IJ50818

Timezone update tool does not print DB version

IJ50856

MKGROUP OF LOCAL GROUP DOESN'T ALLOW ADDING NIS USERS

IJ50857

DSI during varyoffvg when space reclamation is in progress.

IJ50914

lsrsrc IBM.MCP cmd fails post rmcd llvupdate

IJ50915

watson malloc coredump during LLU

IJ50925

Potential security issue kernel_advisory7.asc

IJ50929

CRASH WHEN INCREASING THE MAX NUMBER OF LVS ON A SCALABLE VG

IJ51030

tprof reports NaNQ values

IJ51047

IO HANG WHEN TARGET SUPPORT TAGET RESET

IJ51052

Fixing logical errors in driver stack.

IJ51058

SNAP DO NOT COLLECT POSTGRES SSP DB IN VIOS 3.1.4.31 /4.1.0.X

IJ51116

Update the NPIV flow similar to the NVMe code flow.

IJ51118

Error was Observed in trustchk_log post 2415B_73F WB

IJ51123

system crash @xmdbg_do_xmfree_record

IJ51134

SAVEVG -IR FAILS WHEN A FILESYSTEM IS FULL IN THE VOLUME GROUP

IJ51138

CAA ndd_recv may pass null pointer

IJ51139

DH Group and PFS is wrong for AH tunnels after P2 refresh

IJ51143

nimadm cmd doesn't exit gracefully if "/var" FS is full

IJ51147

aio_qlock and pio_qlock locks of aio to be 128 byte cache align

IJ51187

OUTPUT OF "TRUSS -TKFCNTL <PID>" SHOIWNG 14

IJ51194

qprt:behavior changed from prev version

IJ51224

YNew SMS function NVMe SED Password not working

IJ51229

Observing core dump while configuring VFC Host.

IJ51232

Dispatcher short term load balancing

IJ51236

GCC ISSUE CHECK FOR BINDER CHANGES

IJ51237

LIVE UPDATE LEADS TO VG QUORUM LOSS AND FILESYSTEM INCONSISTENCY

IJ51240

truss issues with LLU enabled

IJ51241

NIM sync operation removes certificate obj on alt master

IJ51288

PTHREAD_KILL() IS NOT ASYNC-SIGNAL-SAFE RESULTING IN APP HANG

IJ51294

rules command after fresh install leaves algorithm wrong

IJ51309

MKDVD MAY CHANGE THE TIMESTAMP OF FILES

IJ51311

Timezone data update for latest IANA version 2024a

IJ51312

AuditBIN error after LKU completion on auditstart

IJ51315

During LPM,START_TARGET_PORT failed for NVME target port.

IJ51316

NPIV disks are not visible on LPAR

IJ51350

npiv client hang with 2005 reference code in HMC after lpm run.

IJ51351

INSTALLP MISSING OUTPUT FOR SIGNATURE VERIFICATION

IJ51352

ragent is not able to access usb device in diag M

IJ51359

mksysb_iso msg differ between default and catalog messages

IJ51375

ldedit/ld commands doesnt enable llu

IJ51377

MEMORY LEAK BY POOLFS CAN CAUSE VIOS SERVER RUN OUT OF MEMORY

IJ51387

Few disks in encrypted when drive is locked

IJ51390

verify_packages fails to verify rpm signature usng -R

IJ51424

VIOSBR ON SSP FAILS WITH ERROR "FAILED SENDING COMMAND TO NODE"

IJ51429

INCREASE SECLDAPCLNTD BASE DN LIMIT

IJ51430

 0781-181

IJ51433

nvmemgr remove ns differs from help text

IJ51435

ID / SU COMMANDS AND LOGIN SLOW FOR LDAP USER

IJ51471

mkvg -k is failing from version 7.2.5.0 if running from client

IJ51475

Group LPM operation failed with error

IJ51483

NIMADM MAY FAIL WITH REACHED USER FILE SIZE LIMIT APPLIES

IJ51522

J2 FILE REMOVAL OVER NFS CAN RESULT IN A CRASH

IJ51623

In SSP environment, cluster add node may hang.

IJ51633

Error while updating vios4.1.0.20 -> 4.1.0.21

IJ51636

Standardise updateios install.log path.

IJ51665

system crash @empty_bucket during during dr cpu add/remove

IJ51666

ofed, Avoid using get_en_softc() instead of ifunit()

IJ51673

VIOSUPGRADE FAILS WITH SPECIAL CHARACTERS IN CRONTAB

IJ51726

EFS KEYS FAIL TO LOAD WHEN LOT OF USERS CONNECT AT THE SAME TIME

IJ51728

signal blocking/unblocking framework during LLU

IJ51732

WRONG INPUTS TO CHFS COMMAND CAN MESS UP /ETC/FILESYSTEMS

IJ51743

viosupgrade failed while we are using 4.1.0.10 mksyb imag

IJ51776

64bit target binary Pr->why is not updated corretly with LLU on

IJ51780

vios got crashed due to memory leakage@kthread_sta

IJ51802

MKKRB5CLNT GIVES MISLEADING ERROR

IJ51803

System crashed with NIS bucket execution

IJ51807

ASO CORE DUMPS AFTER UPDATING THE AIX  TO 7.3 TL02

IJ51810

System Crash during DR when the number of page mappings is > 256

IJ51812

UNMIRRORING PASSIVE MWC LV CAN LEAVE DIRTY BIT SET ON DISK

IJ51848

POTENTIAL CRASH IN NFS OR LFS WHEN ERROR REPORTED BY NFS

IJ51850

diag -T update shows menus 801001 801004 on HMC Contr

IJ51852

Enable iodone migration to another cpu for vscsi i/o

IJ51853

ISCSI I/O HUNG WHEN TASK CMDS ARE LOST

IJ51855

VIOS got crashed with stack abend_trap->npiv_channel

IJ51858

Additional data in Event text is not seen as formated text

IJ51859

Some 10GbE/40GbE RoCE adapters do not configure on recent SPs

IJ51860

Lib update failing for some process post LKU

IJ51879

SEASTAT: INVALID VALUE REPORTED WITH OPTION -F OR -F

IJ51881

viosupgrade tool is failing while user created LV on root

IJ51888

viosbr -dr cluster restore is failing on 73F node.

IJ51891

MANAGE_DISK_DRIVERS -L STILL DISPLAYS AIX_APPCM IN AIX 7.3

IJ51892

VNOP_GETATTR_FLAGS MIGHT PASS BAD VA_MASK TO PFS

IJ51904

tprof dumping core in cook_cleanup

IJ51922

snmpinfo -m dump -v hrProcessorLoad sometime gives wrong output

IJ51924

smitty topas may cause topasout coredump for List recordings.

IJ51930

OD MAY OUTPUT HEXADECIMAL VALUE IN REVERSE

IJ51932

VIOS got crashed with stack abend_trap

IJ51982

LACP ERRLOG MESSAGES ARE MISSING THE PORT INFORMATION

IJ51983

cluster status API hang

IJ51984

Probable data corruption for data under run case

IJ51987

VIOS may crash in npiv stack

IJ51988

malloc pool dumps core after LLU

IJ51990

SNAP -R IN AIX 7.3 OR VIOS 4.1.X DOES NOT CLEAR SNAP.PAX.GZ

IJ52001

Crash while collecting netstats info

IJ52002

POST_VGSYNC REPORTS ERROR MESSAGES DURING MKSYSB RESTORATION

IJ52011

Crash can happen if MFS recovery and dump activity run parallel

IJ52083

Abend Trap in xmfree

IJ52087

ABEND IN TIMER INTERRUPT DUE TO VLANDD LINK WATCHDOG TIMER

IJ52088

system traces format incorrectly

IJ52089

entstat's ouput "Device Type" looks to be wrong for Austin

IJ52091

Probable fcstat hang during certain error conditions.

IJ52094

lscfg and lsmcode commands doesn't show info for Bolt

IJ52096

VIOS may crash in stressed environment.

IJ52098

LPAR crash in aso_get_procname

IJ52100

Build breaking while compiling LIBC without LLU for LIBC

IJ52103

I/O fails after few iterations of EEH in single FC adapter case

IJ52148

Probable rmdev hang after microcode download

IJ52150

Change default LLU mode

IJ52156

MALFORMED LDAP NETGROUP TRIPLE CAUSES USERS TO NOT BE FOUND

IJ52157

Observed coredump during filemon bucket exec

IJ52158

system crash @wlm_start_totalclass+000140

IJ52159

LI-03Y:ISST:LKU is failing while running with workload

IJ52166

UNIXv7: Standard output isn't the same as file in trap with nul

IJ52176

lport value needs to be displayed for closed connection.

IJ52177

System crash in in_rtchange()

IJ52178

system crash in devcopen when running lvmstat

IJ52180

network memory usage may go high when processing ICMP redirects

IJ52181

System may crash if too many kernel extensions are loaded

IJ52183

NIM MKSYSB RESTORE HANG IF A VERY LONG LANG VALUE IN IMAGE.DATA

IJ52184

LI2E2: Build breaking while compiling LIBC without LLU for LIBS

IJ52191

fix memory leak in CFG_INIT failure path

IJ52192

use lsmap -proto in svfc collect script

IJ52196

Probable I/O hang when Quick I/O failover feature is enabled

IJ52198

Lack of pragma in .msg.S files causes problems for translation

IJ52200

strptime("-2-1", "%C%y", testbuf) failed.

IJ52201

Probable system crash during certain error conditions.

IJ52215

FOC73F:FVTR-DEV:vio_daemon core dump on DBN node

IJ52217

0 size malloc broken when vectors in use

IJ52229

LDAP KRB5 BIND WILL FAIL WITH UTF8 TRANSLATION ENABLED

IJ52230

UNIXv7: batch doesn't retain the environment set

IJ52231

Error causes message to standard error and non-zero exit

IJ52232

UNIXv7: SigWait: child exited with code 153

IJ52233

UNIXv7: wcsftime() returned incorrectly formatted string

IJ52234

LIBC LLU Version support

IJ52235

SVT_VMR_HADRHA: VM_CLEANUP_ON_HMC_SUCCESS event logged thrice

IJ52237

NFSV4 FILE CREATE HANGS DUE TO /ETC/NFS/SECURITY_DEFAULT

IJ52238

ISST:restvg with -S fails on different system without listed PV

IJ52240

A potential security issue exists

IJ52241

1MT:Change the default value of schedo disp_latency_loadbalance

IJ52242

Disable LLU by default

IJ52325

DUMPCHECK PRINTS UNKNOWN LOCALE

IJ52327

dkeyexch cmd hangs in NIM Master

IJ52328

Dumping SIER, SIER2 and SIER3 registers in P10

IJ52331

A potential security issue exists

IJ52336

CRASH DURING REBOOT

IJ52339

A potential security issue exists

IJ52341

gencopy errors seen in "nim" update cmd

IJ52342

TPM utilities linking with older version of openssl

IJ52343

VIOS DR LIBRARY SUPPORT FOR EMC 8500

IJ52346

Probable I/O hang during FC link failure error recovery

IJ52349

VIO_HS_ADD_VIOS returning VIO_HS_STOP_VM response

IJ52353

system crashed in aso_bufmger_stop_cpu_trace

IJ52371

VIOSBR WRONGLY BACKUP HOSTNAME TO IP CONFIGURED IF NOT IN HOSTS

IJ52374

A potential security issue exists

IJ52375

A potential security issue exists

IJ52377

System crash or hang when ipsec and dog threads are enabled

IJ52379

A potential security issue exists

IJ52380

A potential security issue exists

IJ52381

Memory leak in syscall ptx_readinst when called by non-root user

IJ52382

Correct SSL code logic and add error handling

IJ52383

Avoiding errpt when cache_mgt cache start is ran.

IJ52385

pmsvcs consumes more pinned memory

IJ52386

MANY HDISK CONFIG 4.1 UPGRADE HAS VIOSBR RESTORE MEM ALLOC FAIL

IJ52388

VIOS SERVER WITH HIGH NUMBER OF VNIC/ROCE ADAPTERS WON'T BOOT

IJ52392

Diag menu's FFC001 and FFC002 are not displayed properly

IJ52393

SVC firmware update may cause LPAR hang and IO failure.

IJ52394

Support for Future TL/SP

IJ52395

WITH SYNCVG THROTTLING A CRASH IN VALIDATE_REQ CAN OCCUR

IJ52396

LPPCHK -F GIVES INCORRECT OUTPUT FOR LARGE SIZED FILES

IJ52401

A potential security issue exists

IJ52538

WHEN LANG SET TO FR_FR MKCD FAILS WITH 0403-057 SYNTAX ERROR

IJ52540

A potential security issue exists

IJ52541

A potential security issue exists

IJ52542

A potential security issue exists

IJ52543

A potential security issue exists

IJ52544

 Password change prompt appears post viosupgrade

IJ52545

Viosupgrade unable to backup rootvg user-defined JFS filesystem

IJ52547

ISST:AUS:rinsev1: Random value "159" in viosupgrade outpu

IJ52549

PERF:LI-19S:Double free with ipsec aes gcm code

IJ52555

RTPG responses larger than 1024 bytes could cause an assert

IJ52556

 ragent fails to load the usb mount point for the

IJ52557

VIOS may crash when MODS is enabled.

IJ52559

LOCAL MKGROUP FAILING IF LDAP GROUP EXISTS WITH SAME GID NUMBER

IJ52561

Error in usage statement for grep.msg and ugrep.msg

IJ52563

PERF:LI 1MT : SYSTEM CRASH DURING RUN IN 73F 2435A

IJ52565

Performance impact with nonblocking UDP socket (EWOULDBLOCK)

IJ52576

A potential security issue exists

IJ52586

 observed splat coredump

IJ52589

UNIXv7: id: exitstatus [^0]" wasn't found in standard out

IJ52681

nvmehealth shows error: invalid option --o

IJ52682

EMGR FAILS WITH AWK ERROR IF TRADEMARK SIGN IN A FILESET'S DESC

IJ52685

Initial 64-Byte size check for LI-157

IJ52697

ISST:BLK:System not booting up and hung at 0555 LED code :

IJ52702

RENAMED LV IN IMAGE.DATA IS NOT UPDATED AFTER ALT_DISK_COPY.

IJ52703

LOCKING ISSUE IN VIRTUAL ADAPTER DRIVER CAUSES COMMAND AND PARTI

IJ52704

System may crash during FC-NVMe protocol driver configuration.

IJ52705

correcting DD_ENTRY_BSTART trace entry

IJ52741

ALTERNATE ROOTVG OPERATIONS FAILS IN TRUSTED ENVIRONMENT

IJ52745

GETCONF DISKSIZE RETURNS INCORRECT LUN SIZE FOR FC-NVME DISKS

IJ52746

VNICSTAT NOT WORKING FOR PADMIN AFTER UPDATE

IJ52748

Reset vioservice trace level

IJ52752

AUTHENTICATION WITH EFS LEAK WHEN KEYSTORE DOESN'T EXIST

IJ52753

MKSECLDAP HANG

IJ52754

AUDITPR DOES NOT SUPPORT SINGLE LINE OUTPUT FOR MULTI LINE EVENT

IJ52755

Updating timezone data files to latest 2024b database

IJ52758

A potential security issue exists

IJ52763

UNIXv7:SIGCHLD is not pending after wait()

IJ52764

AUTHENTICATE() MIGHT RETURN ENOENT INSTEAD OF ENOMEM

IJ52806

 trustchk coredump with Ptools bucket exec

IJ52822

 VIOS/AIX boot may hang during Broadcom FC HBA config

IJ52897

HST 1060.20 SP: Inactive LPM is failing for NPIV lpar with HSC

IJ52922

vmstat output fi/fo seems incorrect when system is in a paging

IJ52943

JAVA 21: PROBLEM EXTRACTING FILES FROM JAR/ZIP WITH NX/GZIP

IJ52947

Logs in ASO to capture reason for unsuccessful SHM promotions

IJ53032

rebase bos.loc.com.CN

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
06 December 2024

UID

ibm17178052