IBM Support

Power11 System Firmware Fix History - Release levels MY11xx

Fix Readme


Abstract

Firmware History for MY11xx Levels.

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

Content

 

MY1110

MY1110
For Impact, Severity and other Firmware definitions, please refer to this Glossary of firmware terms.
MY1110_145_119 / FW1110.30
 
2026/06/26

Impact: Security     Severity: SPE

System firmware changes applicable to all systems

  • A security problem was fixed for CVE-2025-66199
  • A problem was fixed related to IBM i tagged loadsource failures generating a platform event log with SRC B200308C. The platform event log has a hardware FRU callout as the first priority FRU callout. The fix changes the SRC B200308C FRU callout list to have an appropriate isolation procedure as the first callout instead of immediately replacing hardware.
  • A fix was made to allow service representatives to install targeted ACFs through ASMI without impacting existing service ACF authorization.
  • A problem was fixed for performance degradation of a shared processor partition in a resource group that has been recreated.
  • A problem has been fixed when allocating more memory than could be contained in a DCM/Drawer when zero cores were assigned to the partition.
  • A problem was fixed for performance degradation, including I/O response time, of shared processor partitions after creating or updating resource groups. If shared processor partitions are experiencing performance degradation following a create or update of a resource group, one of the following can be performed to restore normal performance: 1) Power off all shared processor partitions in the affected resource group. All shared processor partitions must be in the powered off state before powering on any shared processor partitions. 2) Use Live Partition Mobility (LPM) to migrate all shared processor partitions in the affected resource group to another server. All shared processor partitions must be migrated away before migrating any of them back. 3) Reboot the server.
  • Fan floor adjustment for cooling improvements on FC adapters
  • A change was made to fix link instability issues with adapters. This problem can occur on E1150 systems with FC adapters.
  • A problem was fixed where an incorrect error code would be returned when a user is using Redfish API to configure DNS with a string or null or empty value
  • A problem was fixed where service login would still work after installing other targeted ACF.
  • A problem was fixed where inband code update was failing intermittently with src BA278006
  • A problem has been fixed where inventory item names were incorrectly cleared from the ASM GUI when items were removed from inventory records.
  • A problem was fixed for ACFs (Access Control Files) expiring before the end of the day that they are listed to expire. The fix allows for uploaded ACF files to be valid through the end of the day that they are listed to expire.
  • A problem was fixed to ensure a customer set power cap will be honored following a hardware change without rebooting the BMC
  • A problem was fixed to ensure the correct Idle Power Saver to Enter/Exit utilization values are used when changed
  • A problem was fixed where 'Step 1' information pop up message was not displayed when the customer switched the firmware backup image to running using ASM GUI
  • A problem was fixed where 'Step 1' information pop up message was not displayed when the customer updated the firmware using ASM GUI
  • A problem was fixed where BMC ASM users were unable to view the options under the 'Certificate Type' field when adding a certificate.
  • A problem was fixed where BMC state would change to a quiesced state with SRC BD8DC201 and BMCDUMP would be generated.
  • A problem was fixed where an LDAP user was able to see MFA options using ASM GUI
  • A problem was fixed where entries in the IPv6 static default gateway were not cleared after getting an error in ASM GUI.
  • A problem was fixed where date was already present in the date filter when accessing ASM GUI via Safari browser.
  • A problem was fixed where empty IP address submission in SNMP alerts should have given error message in ASM GUI.
  • A problem was fixed where functional processors are shown as non-functional via ASM GUI or via Redfish commands.
  • A problem was fixed where the ASM GUI Certificates page content was displayed in the language selected during the user's previous login.
  • A problem was fixed where the ASM GUI user was navigated to the Overview page on clicking 'Refresh' on pop up message.
  • A problem was fixed where the ASM GUI "Add file" button styling was incorrect when a language other than English was selected.
  • A problem was fixed where the IPv4 DCHP wasn't reverting to its original state on ASM.
  • A problem was fixed where the VMI static network was not reachable when the IPv6 gateway is set
  • A problem was fixed where the error message was partially hidden on ASM when there was a mismatch between the selected and added certificate types.
  • A problem was fixed where the table header was checked even though no item in the table was selected in User management page in ASM GUI.
  • A problem was fixed where the user sees an error message after deleting their own account. Occurs only when deleting the currently logged in account in ASM GUI.
  • A problem was fixed where the user was unable to load the Health, Power, and Profile Settings pages when opened in a new tab via hyperlink in ASM GUI.
  • A problem was fixed where the user was unable to load the Host Console ASM GUI menu when opened in a new tab via hyperlink.
  • A problem was fixed where a user sees an error on ASM GUI when multiple redfish sessions are disconnected.
  • A problem was fixed where users could temporarily reconfigure processors/DIMMs isolated by firmware while the system is powered off using ASM. This fix prevents manual reconfiguration of system-isolated processors/DIMMs.
  • A problem was fixed with error output during system checkstop analysis.
  • Improved logging for eBMC connection issues related to reaching the maximum allowed connections.
  • This fix will prevent BD572683 PEL after a BMC reboot
  • A new ASM GUI option was added to disable fault reminder SRC (BD50F138) for existing issues. While the ( BD50F138 ) SRC will no longer occur, the underlying issue still exists, and the customer must remember to take care of the issue. For any new issue, the BD50F138 SRC will start occurring again, and would need to be suppressed again.
  • A problem was fixed for adapters configured in SR-IOV mode where a loss of function is possible and may present the following if virtual functions are assigned to AIX or VIOS partitions: MLXCENT_DEAD_EXIT MLXCENT_DEAD_ENTRY MLXCENT_DEAD_REQ MLXCENT_SW_ERR MLXCENT_TX_ERR. The problem only occurs with the following adapter types: EC2R/#EC2S with CCIN 58FA and #EC2T/#EC2U with CCIN 58FB. The problem occurs for the mentioned adapters when a high volume of network traffic is being transmitted on a virtual function.
  • A change was made to how Preventative errors are being flagged.
MY1110_130_119 / FW1110.20
 
2026/03/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
 
2026/01/14

Impact: Availability     Severity: SPE

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.

MY1110_116_082 / FW1110.10
 
2025/12/12
 
Impact: Function     Severity: SPE
 

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.
  
MY1110_107_082 / FW1110.03
 
2025/11/14
Impact: Function     Severity: SPE
 
System firmware changes that affect all systems
  • 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.

 

MY1110_088_082 / FW1110.01
 
2025/08/15
Impact: Performance     Severity: SPE
 
System firmware changes that affect all systems
  • A problem was fixed in the BMC network where the direct HMC connection using the static network fails.  System goes to NoConnection state, as BMC cannot route the packets back to HMC.
  • A problem was fixed that could cause reduced system performance due to incorrect core state handling on certain processor configurations, including field core override settings and guarded processors.
  • A problem was fixed that could lead to reduced performance on mid-range systems configured with a combination of core+cache and cache-only modes.
  • Allow older IBMi OS levels to run on FW1110 on Power10 servers. 
 
MY1110_082_082 / FW1110.00

2025/07/25
Impact:  New      Severity:  New

GA Level with key features included listed below.

New Features and Functions
  • Support was added to improve IPL times.
  • Support was added to improve LPAR Boot Performance.
  • Support was added for spare cores.
  • Support was added to increase DDR5 memory speeds.
  • Support was added for resource groups.
  • Support was added for Quantum Safe Secure Boot and LPM.
  • Support was added for "Energy-efficient Mode" available on the HMC/ASMI.
  • Support was added for eBMC LLDP.
  • Support was added for eBMC Multi-Factor Authentication (MFA).
  • This server firmware includes new adapter support for PCIe5 x16 2-port 200 GbE capable RoCE adapter (FC EC85 and FC EC86; CCIN EC2C), Please find more details here: PCIe5 x16 2-port 200 GbE RoCE adapter (FC EC85 and FC EC86; CCIN EC2C)
  • This server firmware includes the SR-IOV adapter firmware level 28.42.1000  for the following Feature Codes and CCINs: EC85/EC86 with CCIN EC2C; xx.42.1000 for EC71/EC72 with CCIN 2CF9 and EN24/EN26 with CCIN EC2A and EC75/EC76 with CCIN 2CFB
  • This server firmware includes the SR-IOV adapter firmware level xx.35.2000 for the following Feature Codes and CCINs: EC66/EC67 with CCIN 2CF3
  • This server firmware includes the SR-IOV adapter firmware level xx.32.1010 for the following Feature Codes and CCINs: EC2R/EC2S with CCIN 58FA; EC2T/EC2U with CCIN 58FB
 

 

[{"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":""}]

Document Information

Modified date:
26 June 2026

UID

ibm17240442

Page Feedback