MY1110_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 E1050 (9043-MRX) server only.

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

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/9043-MRU?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 in 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	01MY1110_130_119.img
Size	310022560
Checksum	63948
sha256sum	26813e5c7c43594fae2f3c64077d86c1fff3c5c5e989fbd99f2449208c5a4f63

Filename	01MY1110_130_119.tar
Size	210155520
Checksum	14645
sha256sum	a53fcbad08531028cdd475ee902f649729d559decd4b306c8ce58bc54cceed6d

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 01MY1110_130_119.img

MY1110 For Impact, Severity and other Firmware definitions, please refer to this Glossary of firmware terms.
MY1110_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.
MY1110_119_119 / FW1110.11	Impact: Availability Severity: SPE System Firmware changes included in 1110.11: System firmware changes applicable to all systems A problem was fixed for concurrent firmware activation updates from FW1110.02/FW1110.03 to FW1110.10 and future Service Packs. Systems which have booted on FW1110.10 will operate normally. The resolution to this issue is that activating the FW1110.11 Service Pack will be a disruptive activation. The FW1110.11 Service Pack has the same functional content as FW1110.10. You may choose to move to FW1110.11 or a future FW1110 Service Pack during a disruptive service window, so future FW1110 Service Packs may be concurrently applied. System Firmware changes included in 1110.10: New Features and Functions Support was added for PCIe x16 dual monitor graphics adapter (FC EC90). Support was enhanced for Link Layer Discovery Protocol (LLDP) capability when an adapter is in SR-IOV shared mode, allowing collection of network topology information via network switches. Support was added for Link Layer Discovery Protocol (LLDP) on IBM Power System E1180 (9080-HEU). Support was added for “inband” HMC to OS communication (RMC Connection). This eliminates external network dependencies for RMC for OS versions that are enabled for in-band RMC. Support was added for The Linux Integrity Measurement Architecture (IMA). IMA verifies signatures against critical BMC software components, measuring and logging these measurements in the TPM and allowing attestation of these results at runtime. Support was added to auto provision vTPM during partition creation, provisioning a signed endorsement key certificate during instantiation to provide that proof of authenticity. System firmware changes that affect all systems A problem was fixed where error logs were not created for correctable or uncorrectable BMC memory errors. A problem was fixed where error SRC - BD561008 is logged for the missing lcd panel even though panel is accessible. A problem was fixed where user cannot direct connect to BMC eth0/eth1 when gateway is set to non zero address. A security problem was fixed for CVE-2025-38556. A change was made to make the BC8A090F error informational until the Power Management complex activation has finished all retries. A problem was fixed by providing help text where the Status value of Sensors page confuses the user in ASM GUI. A problem was fixed for a system going into a "No Connection" state to the VMI (xxxxx) from the HMC. The HMC lssysconn command will show vmi_state=No connection. A problem was fixed for the Virtualization Management Interface where it can generate resource dumps. Platform Event Logs with SRC BD8D6025 and SRC BD8D6029 will also be produced because of the failure. A problem was fixed in BMC network where the direct HMC connection using the static network fails. System goes to NoConnection state, as BMC can not route the packets back to HMC. A problem was fixed to prevent an SRC BC8A264F. A problem was fixed where 12V current share warning error log SRC 110015F1 was incorrectly showing as serviceable PEL. A problem was fixed where a user will see any ACF certificate can be uploaded irrespective of the type selected. A problem was fixed where BMC ASM GUI button hover was overlapping with loading bar. A problem was fixed where BMC ASM PCIe topology page was always empty. A problem was fixed where BMC may reboot unexpectedly with an error SRC BD8DC201. A problem was fixed where customer was seeing invalid characters on Inventory and LED page. A problem was fixed where error log download content is partially empty when it is downloaded from ASMI or any clients. A problem was fixed where fabric adapters information was missing in the ASM GUI. A problem was fixed where firmware code update from the Host Operating system failed with the SRC BD8DC201. A problem was fixed where HTTP 500 error status returned for redfish call to get event logs after BMC reboot. A problem was fixed where if BMC reboots when the system is at runtime state an unexpected BMCDUMP may be logged. A problem was fixed where Overview page of ASMI shows power cap value when it is disabled. A problem was fixed where policy to guard bad hardware was fixed for SRCs with the format BxxxE51x. A problem was fixed where ReadOnly account modification via ASM will display the error message. A problem was fixed where the CEC would be stuck in the initialization stage during a firmware downgrade. A problem was fixed where the client overwhelms the BMC with too many requests and the BMC holds the requests open longer than needed, leading to a slower recovery. A problem was fixed where the 'Previously Activated' and 'Entry Check' entries under 'Processor Information' and 'Memory Information' on the Capacity on Demand page were displaying default values. A problem was fixed where the user had to use ServiceLogin Certificate option to upload Admin reset certificate in ASM GUI. A problem was fixed where a user logged in as a read-only user did not receive a general error message along with the 'User Unauthorized' message when attempting actions on the ASM Server Power Operations page or Firmware page. A problem was fixed where user was able to click the BMC GUI table filter checkbox name instead of the actual checkbox rendering table unfiltered. A problem was fixed where user was not able to clear guard records using the ASMI GUI. As a workaround, the customer can use the Guard command line tool to clear the core guard records. Changes were made to support only for the following MACS: hmac-sha2-256-etm@openssh.com, hmac-sha2-512-etm@openssh.com, hmac-sha2-256, hmac-sha2-512. A change was made to correctly report DDR5 memory characteristics to OS inventory. No functional impact, effective after system IPL. BMC support was added for Linux IMA (Integrity Measurement Architecture) to create informational PELs when a binary on the BMC is executed and its Linux IMA signature verification fails. BMC support was added for Linux IMA (Integrity Measurement Architecture) will create informational PELs when a binary on the BMC is executed and its Linux IMA signature verification fails. Support was added so that an informational PEL will be created when a BMC factory reset is requested. A problem was fixed when removing a system from Power Enterprise Pool 2.0 when there are guarded cores in the system. A problem was fixed for a failure or partial completion for a processor config change for a partition. As a workaround, the processor config change can be retried. A problem was fixed where B400FF04 SRCs are seen on the system after non-concurrently replacing an SR-IOV adapter while it is in shared mode and has logical ports configured. A problem was fixed where the error message "HSCL146A The I/O adapter: null is not valid." may be displayed by the management console when transitioning an SR-IOV adapter from shared to dedicated mode even though the operation was successful. The version of OpenSSL used by PowerVM has been updated to OpenSSL 3.0.18. A security problem was fixed for CVE-2025-52497 and CVE-2025-49087. A security problem was fixed for CVE-2025-36194. A security problem was fixed for CVE-2025-36238. A change was made to move SR-IOV adapters up to the latest level of adapter firmware. This update contains important reliability enhancements and performance fixes for adapters in promiscuous mode. This change updates the adapter firmware to XX.43.3608 for the following Feature Codes and CCIN: #EC71/EC72 with CCIN 2CF9, #EC75,EC76 with CCIN 2CFB, #EC85,EC86 with CCIN EC2C, and #EN24,EN26 with CCIN EC2A. Applying the update will cause a re-initialization of the specific SR-IOV adapter environment, causing a brief outage. Update instructions: https://www.ibm.com/docs/en/power10?topic=adapters-updating-sr-iov-adapter-firmware A change was made to suppress logging TPM failures with SRC B7009009 during TPM health checks. A problem has been fixed where a combination of communication fails to the power IC devices on a DDIMM could result in an IPL crash, with no log indicating which parts caused the fail. This fix will properly call out and deconfigure the failing DDIMM. A problem has been fixed to improve the firmware selection of processor cores added to an active dedicated processor partition. A problem was fixed for a multi-port adapter failing to configure or encountering performance impacts. The problem only pertains to multi-port adapters in an ENZ0 PCIe4 expansion drawer. The problem does not pertain to adapters running in SR-IOV shared mode. After installing the firmware service pack containing this fix, the partition(s) owning the impacted adapter(s) will need to be rebooted or the adapter(s) will need to be dynamically removed and added back to the partition(s) for the fix to activate for the impacted adapter(s). A problem was fixed for a possible system termination with SRC B700F105 after changing the I/O configuration or deleting a partition that is in the failed state with the SRC B2001230. A problem was fixed for a possible system termination with SRC B700F105 when running KVM in a PowerVM LPAR. A problem was fixed for a system state of incomplete on the management console which is not recoverable with a "Recover system" option of the managed system. The problem occurs when a new partition is created on the system, but the internal representation of the partition is not completed. The fix allows for the system firmware to validate partition creation is complete and will synchronize inconsistencies in the partition representation. A problem was fixed for network adapters with Feature Codes EC24/EC26 where traffic loss for SR-IOV logical ports configured on the adapter may occur and SRC B400FF02 platform event log will be created. This problem may intermittently occur when the adapter is configured in shared mode and a manually initiated resource dump is initiated from the HMC or ASMI targeting the adapter. A problem was fixed in firmware that prevented the external stand-alone USB DVD (Feature EUA5) from being selected as a boot device via the SMS menu and the SMS macros. A problem was fixed in the Power Hypervisor code where resources assigned to Virtual Functions may be deallocated even when there are configured VF resources for partitions. This could happen during hardware repair or replacement (FRU Repair or Exchange) if the VF resources weren’t removed from the operating system before starting the procedure. A problem was fixed where a concurrent firmware update would fail and the system would go to Incomplete state on the HMC. A problem was fixed that prevented the HMC from displaying daily notifications on the GUI and sending daily email notifications for a system in a Power Enterprise Pool 2.0 (PEP 2.0) whose PEP 2.0 Capacity on Demand code was within 7 days of expiration. A problem was fixed to continue to configure all the PCIe Switch slots under a PCIe Switch when one of the slot initialization operations fails under the PCIe Switch. The problem occurs only when there is an issue with one or more slots in IPL under PCIe Switch. This fix is applicable for all PCIe Switches in System Units and in IO Expansion Units. A problem was fixed where a B2006002 SRC may be seen when re-IPLing a system with 2 or more SR-IOV adapters in shared mode, even though no adapters were replaced. The failed SR-IOV adapter can be powered on again and it should boot correctly. A problem was fixed where a serviceable event for a processor issue was logged with an incorrect call out. A problem was fixed where AIX Update Access Key (UAK) expiration HMC notifications are logged along with A7004763 and A7004764 SRCs on IBMi partitions on systems with no AIX LP installed. With the fix, these notices will be suppressed if no AIX partition exists on the system. A problem was fixed where booting to the SMS menu and executing a specific SMS key sequence could cause undefined behavior. The problem may occur if a user executes the following key sequence upon boot to the SMS menu: 5 (Select Boot Options) ->1 (Select/Install boot device) ->5 (List all Devices). A problem was fixed where firmware might get out of sync after a runtime code update followed by a memory-preserving IPL. The fix addresses the issue and ensures proper security checks pass with the new code. A problem was fixed where if all TPM (trusted platform module) hardware has been marked as failed in the hypervisor, the hypervisor will block live partition migrations with the system key and capacity on demand activation codes from being applied. A problem was fixed where long running CoD based firmware operations, such as the processing of applied entitlements, may time-out. This results in the server state being set to incomplete on the HMC, which will require a rebuild of the server. A problem was fixed where Power Enterprise Pool 2.0 (PEP 2.0) and virtual serial number activation codes applied on the HMC may time-out. A problem was fixed where the hypervisor could allow memory to be over-configured on the system, leading to inconsistent memory values and errors on the management console. A problem was fixed where the hypervisor was reserving too much memory for SR-IOV adapters that are configured in shared mode. Activating this service pack will automatically resolve the issue and free up memory on the system. A problem was fixed where the SMS boot position (index) may not populate properly. SMS options: 5 (Select Boot Options) -> 1 (Select/Install boot device) ->5 (List all Devices). Workaround: SMS options: 5 (Select Boot Options) -> 2 (Configure Boot Device Order) -> [ESC] -> 5 (Select Boot Options) -> 1 (Select/Install boot device) -> 5 (List all Devices). A problem was fixed where unnecessary SBE Updates were being performed on Cold IPLs (ie, the system is powered off before IPLing/booting). The solution better determines if a SBE Update is really necessary on a Cold IPL and saves IPL time by bypassing any unnecessary SBE Updates. A problem was fixed where preventative errors were being flagged incorrectly and unnecessarily during testing. This fix reconfigures the flags that are set for watching for these preventative errors. Add a recovery mechanism to work around hardware erratum on certain PMIC components on certain 4U DDIMMs which would otherwise cause them to reset voltage settings leading the DIMM to run in N-mode until the system reboots.

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: (MY1110_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/9043-MRU?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/9043-MRU?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/9043-MRU?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/7240442

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSMI4EA","label":"IBM Power E1050 (9043-MRX)"},"ARM Category":[{"code":"a8m3p000000F983AAC","label":"eBMC-\u003EUpdate \/ Upgrade Firmware"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]

Tips