MZ1110_130 / FW1110.20 Release Notes

Fix Readme

Abstract

This document provides information about the installation of Licensed Machine or Licensed Internal Code, which is sometimes referred to generically as microcode or firmware.

This package provides firmware for IBM Power System S1022 (9105-22A) servers only.

NOTE: This firmware package is intended for IBM Power10 Systems running in PowerVS and can not be installed outside of PowerVS.

Release notes for MZ1110_130 / FW1110.20

Service Pack Summary: Concurrent Service Pack

Read the following important information before installing this Service Pack.

Content

Minimum HMC Code Level

This section is intended to describe the "Minimum HMC Code Level" required by the System Firmware to complete the firmware installation process. When installing the System Firmware, the HMC level must be equal to or higher than the "Minimum HMC Code Level" before starting the system firmware update. If the HMC managing the server targeted for the System Firmware update is running a code level lower than the "Minimum HMC Code Level" the firmware update will not proceed.

The Minimum HMC Code levels for this firmware for HMC x86, ppc64 or ppc64le are listed below:

x86 - This term is used to reference the Virtual HMC appliance that runs on x86 with hypervisors KVM, XEN, VMWare ESXi.

ppc64 or ppc64le - Describes the Linux code that is compiled to run on Power-based Hardware appliance or PowerVM based LPARS (Logical Partitions).

The Minimum HMC Code level for this firmware is: HMC V11.1.1110.0 (V11R1M1110).
The Minimum HMC Code level for vHMC is: V11.1.1110.0 (V11R1M1110). Download of the Power Hardware Management Virtual Appliance (vHMC) install images for x86 hypervisors and PowerVM are available at the Entitled Systems Support site (ESS).

The Minimum HMC level supports the following HMC models:

HMC models: 7063-CR2
x86 - KVM, XEN, VMWare ESXi (7.0.2 and 8.0.3)
ppc64le - vHMC on PowerVM (POWER9, POWER10 and Power11 systems)

For information concerning HMC releases and the latest PTFs, go to Fix Central.

For specific fix level information on key components of IBM Power Systems running the AIX, IBM i and Linux operating systems, we suggest using the Fix Level Recommendation Tool (FLRT).

NOTES:
- You must be logged in as hscroot in order for the firmware installation to complete correctly.
- Systems Director Management Console (SDMC) does not support this System Firmware level.

Important Information

Concurrent Firmware Updates

Concurrent system firmware update is supported on HMC Managed Systems only.

Ensure that there are no RMC connections issues for any system partitions prior to applying the firmware update. If there is an RMC connection failure to a partition during the firmware update, the RMC connection will need to be restored and additional recovery actions for that partition will be required to complete partition firmware updates.

Memory Considerations for Firmware Upgrades

Firmware Release Level upgrades and Service Pack updates may consume additional system memory.

Server firmware requires memory to support the logical partitions on the server. The amount of memory required by the server firmware varies according to several factors.

Factors influencing server firmware memory requirements include the following:

Number of logical partitions
Partition environments of the logical partitions
Number of physical and virtual I/O devices used by the logical partitions
Maximum memory values given to the logical partitions

Generally, you can estimate the amount of memory required by server firmware to be approximately 8% of the system installed memory. The actual amount required will generally be less than 8%. However, there are some server models that require an absolute minimum amount of memory for server firmware, regardless of the previously mentioned considerations.

Additional information is at: https://www.ibm.com/docs/en/power11/9824-42A?topic=resources-memory

SBE Updates

These Power servers contain SBEs (Self Boot Engines) that are used to boot the system. SBE is internal to each of the Power chips and used to "self boot" the chip. The SBE image is persistent and is only reloaded if there is a system firmware update that contains an SBE change. If there is an SBE change and the system firmware update is concurrent, then the SBE update is delayed to the next IPL of the CEC which will cause an additional 3-5 minutes per processor chip in the system to be added onto the IPL. If there is an SBE change and the system firmware update is disruptive, the SBE update will cause an additional 3-5 minutes per processor chip in the system to be added onto the IPL. During the SBE update process, the HMC or op-panel will display service processor code C1C3C213 for each of the SBEs being updated. This is a normal progress code and the system boot should not be terminated by the user. Additional time estimate can be between 12-20 minutes per drawer or up to 48-80 minutes for maximum configuration.

The SBE is updated with the 1110.10 service pack. Code updates will take longer.

Firmware Information

Use the following examples as a reference to determine whether your installation will be concurrent or disruptive.

For systems that are not managed by an HMC, the installation of system firmware is always disruptive.

Note: The concurrent levels of system firmware may, on occasion, contain fixes that are known as Deferred and/or Partition-Deferred. Deferred fixes can be installed concurrently, but will not be activated until the next IPL. Partition-Deferred fixes can be installed concurrently, but will not be activated until a partition reactivate is performed. Deferred and/or Partition-Deferred fixes, if any, will be identified in the "Firmware Information and Description" table of this document. For these types of fixes (Deferred and/or Partition-Deferred) within a service pack, only the fixes in the service pack which cannot be concurrently activated are deferred.

Note: The file names and service pack levels used in the following examples are for clarification only, and are not necessarily levels that have been, or will be released.

System firmware file naming convention:

01M?xxxx_yyy_zzz

where:

"?" is the second letter in the system type (MX, MY, MZ for Power 11)
xxxx is the release level
yyy is the service pack level
zzz is the last disruptive service pack level

NOTE: Values of service pack and last disruptive service pack level (yyy and zzz) are only unique within a release level (xxxx). For example, 01M?1110_040_040 and 01M?1120_040_040 are different service packs.

An installation is disruptive if:

The release levels (xxxx) are different.
Example: Currently installed release is M?1110_040_040, new release is M?1120_040_040.
The service pack level (yyy) and the last disruptive service pack level (zzz) are the same.
Example: M?1110_040_040 is disruptive, no matter what level of M?1110 is currently installed on the system.
The service pack level (yyy) currently installed on the system is lower than the last disruptive service pack level (zzz) of the service pack to be installed.
Example: Currently installed service pack is M?1110_040_040 and new service pack is M?1110_050_045.

An installation is concurrent if:

The release level (xxxx) is the same, and
The service pack level (yyy) currently installed on the system is the same or higher than the last disruptive service pack level (zzz) of the service pack to be installed.

Example: Currently installed service pack is M?1110_040_040, new service pack is M?1110_041_040.

Firmware Information and Description

Filename	01MZ1110_130_119.img
Size	315389792
Checksum	04910
sha256sum	7c6ef6b4722dcd509fbced1b035395f31bba772c8aca7b1ecf63c8a49217e5f2

Filename	01MZ1110_130_119.tar
Size	212418560
Checksum	56910
sha256sum	dde3cc2e3792e348273d4c99c8d9d168af03ac32d3bc892db83a61d2ff65ed96

Note: The Checksum can be found by running the AIX sum command against the img file (only the first 5 digits are listed).
Example: sum 01MZ1110_130_119.img

MZ1110 For Impact, Severity and other Firmware definitions, please refer to this Glossary of firmware terms.
MZ1110_130_119 / FW1110.20	Impact: Security Severity: HIPER System firmware changes applicable to all systems A security problem was fixed for CVE-2026-22796 A problem was fixed where, in rare cases, first failure capture data may not be able to be collected from the Virtualization Management Interface or Runtime Processor Diagnostics. The probability of encountering this problem can be reduced by using a 256 MB Logical Memory Block size. A problem was fixed for the display of Resource Group information from the Management Console. The problem occurs if any single Resource Group encounters an error during the query process causing the results to contain no information for that Resource Group or any subsequent Resource Groups. A problem was fixed where application of an activation CoD key via the service processor's ASMI interface during system IPL could cause a Hypervisor task to fail with an B7000602 SRC. The failed task would block all activation keys from being accepted when applied via ASMI until the system is re-IPL'd. A change was made for multiple misleading logs with SRC BA180005, which may be logged when an LPAR is booted. The fix replaces the log with checkpoint CA00E15C, which indicates a boot driver is loaded for an OEM NVMe adapter. A problem was fixed for an OS crash that can occur after an LPM. The problem can occur after many iterations of LPM for an LPAR OS that supports an inband HMC to OS communication (RMC Connection). A problem was fixed when deleting a resource group. The problem only occurs when dedicated cores are disabled on a system using Power Enterprise Pool 2.0. A change was made to enhance the affinity scores generated for Resource Groups. A problem was fixed for possible improper placement of partitions during a Dynamic Platform Optimization operation that includes partitions in two or more Resource Groups. A problem was fixed where a side switch failure may cause the system to end up with a mismatched hypervisor firmware level. A problem was fixed where inband code update failed with error SRC BD8D3609 on a standalone IBM i server. The Common Vulnerabilities and Exposures number for this problem is CVE-2025-61984. The fix updates the BMC SSH version, so network security scans no longer incorrectly give a false positive report. A problem has been fixed where stale data was visible on GUI even after a PCIe card was removed from the system and the BMC was rebooted. Additionally, corrected the behavior where inventory item names were incorrectly cleared from the GUI when items were removed from inventory records. The fix ensures inventory names remain visible on the GUI at all times, as they are statically associated with location codes and should be independent of the item's presence state. A fix was made to prevent an SRC of BD561009. A problem is fixed where ASM screen is blank when ASM is launched from HMC UI A problem was fixed for a null pointer exception during system checkstop analysis due to a TOD clock failure. A problem was fixed for where system crash failure analysis could fail, which would result in loss of first failure data capture. A problem was fixed in which the user doesn't see any error message in the password field when logging in with empty password in the ASM GUI. A problem was fixed where ASM GUI pages opened via hyperlinks could not be accessed in a new tab. A problem was fixed where the ASM GUI user was not able to see icons aligned in an IP address table A problem was fixed where the BMC ASM GUI PCIe topology page does not display the correct information. A problem was fixed where BMC state goes to Quiesced state and SRC BD8D2685 is logged. A problem was fixed where IBMi service function was not executable from the ASM GUI. A problem was fixed where, after the hostname change on ASM GUI, it does not log out automatically and the hostname is not updated until the BMC GUI page is refreshed. A problem was fixed where an incorrect message was displayed on ASM to the customer when a table search or filter returned no results. A problem was fixed where hardware deconfigurations will incorrectly persist across ipls, even after replacing parts. The system will log BD8D300B SRC and may fail to boot upon re-ipl. There will be loss of system resources. This fix will prevent and repair this situation. A problem was fixed where, applying the date filter on the ASM GUI Audit logs, the page did not filter the entries correctly. A problem was fixed where, on entering 'service' in Search bar, other entries are also displayed in Audit logs page. A problem was fixed where sorting the 'Settings' column on the Hardware Deconfiguration page resulted in unexpected message when reconfiguring the manually deconfigured and spare cores. A problem was fixed where the ASM GUI user sees a error message along with the success message on updating Activation code in Capacity on demand page. A problem was fixed where the ASM user could configure a static IPv6 address with a prefix length of 0 or change the prefix length to 0 during editing. A problem was fixed where the BMC ASM Secure version lock-in setting toggle on the Policies page was not working properly. A problem was fixed where the dumps were downloaded with .txt extension. A problem was fixed where the system ipl would be stuck in the initialization state when it is powered on followed by firmware update or BMC reboot. A problem was fixed where the user sees an error when clicking on Continue to OS Running in Server power operations of ASM GUI. A problem was fixed where the user sees error on selecting the privilege in Chrome and Edge browsers while adding a new user in ASM GUI. A problem was fixed where the user was unable to enable MFA in proxy ASM GUI. A problem was fixed where the user was unable to upload the admin reset certificate via ASM GUI login page. A problem was fixed where the user, when logged in as Administrator and 'Service Login Certificate' not present in the system, was not able to add a new Service Login Certificate via ASM GUI. A problem was fixed where user account status was incorrectly displayed as "Unlocked" . This occurs only when the User Unlock Method was set to 'Manual' and after the account was locked due to exceeding the maximum failed login attempts. A problem was fixed where user is not able to configure VMI static configuration with 0.0.0.0 gateway. A problem was fixed where user was not able to disable MFA bypass for a user through ASMI. A problem was fixed where user wasn't able to clear the checkbox with no even log entries being selected in the table using ASMI. The fix prevents logging a BD572684 PEL after a BMC reset. A problem was fixed where LDAP could not be enabled. A problem was fixed where firmware code downgrade may fail with error SRC BD8DC201. A security problem was addressed. The Common Vulnerabilities and Exposures number for this problem is CVE-2025-8194.

How to Determine The Currently Installed Firmware Level

You can view the server's current firmware level on the Advanced System Management Interface (ASMI) Overview page under the System Information section in the Firmware Information panel. Example: (MZ1110_067)

Downloading the Firmware Package

Follow the instructions on Fix Central. You must read and agree to the license agreement to obtain the firmware packages.

Note: If your HMC is not internet-connected, you must download the new firmware level to a USB flash memory device or ftp server.

Installing the Firmware

The method used to install new firmware depends on the release level of firmware which is currently installed on your server. The release level can be determined by the prefix of the new firmware's filename.

Example: 01M?xxxx_yyy_zzz

where:

"?" is the second letter in the system type (MX, MY, MZ for Power 11)
xxxx is the release level

If the release level will stay the same, this is considered an update. (Example: Level M?1110_040_040 is currently installed and you are attempting to install level M?1110_041_040.)

If the release level will change, this is considered an upgrade. (Example: Level M?1110_040_040 is currently installed and you are attempting to install level M?1120_050_050.)

Instructions for installing firmware updates and upgrades are at:
https://www.ibm.com/docs/en/power11/9824-22A?topic=support-getting-fixes

IBM i Systems

For information concerning IBM i Systems, go to Fix Central.

Choose "Select product", under Product Group specify "System i", under Product specify "IBM i", then Continue and specify the desired firmware PTF accordingly.

HMC and NovaLink Co-Managed Systems (Disruptive firmware updates only)

A co-managed system is managed by HMC and NovaLink, with one of the interfaces in the co-management master mode.
Additional information is at:
https://www.ibm.com/docs/en/power11/9824-22A?topic=environment-powervm-novalink

Then the firmware updates can proceed with the same steps as for the HMC managed systems except the system must be powered off because only a disruptive update is allowed. If a concurrent update is attempted, the following error will occur: "HSCF0180E Operation failed for <system name> (<system mtms>)." Additional information is at:
https://www.ibm.com/docs/en/power11/9824-22A?topic=support-getting-fixes

Firmware History

The complete Firmware Fix History (including HIPER descriptions) for this Release level can be reviewed at:
https://www.ibm.com/support/pages/node/7240443

[{"Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSE1FSG","label":"IBM Power S1022 (9105-22A)"},"ARM Category":[{"code":"a8m3p000000F983AAC","label":"eBMC-\u003EUpdate \/ Upgrade Firmware"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Type":"MASTER"}]

Tips