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), IBM Power System S1024 (9105-42A), IBM Power System S1022S (9105-22B), IBM Power System S1014 (9105-41B), IBM Power System L1022 (9786-22H), and IBM Power System L1024 (9786-42H) servers only.
Release notes for ML1040_021 / FW1040.00.
At the time of general availability, FW1040 is required to support the NED24 NVMe Expansion Drawer. FW1040 is a limited, interim release, and is different from IBM's normal releases in the following manner:
- Normal releases have service pack support for 2 years after the release. However, FW1040 is only supported from GA until the next major FW version becomes available.
- Only a single service pack for FW1040 is planned near the release of the next major FW version.
- Clients who install FW1040 must perform a disruptive upgrade once the next major FW version becomes available.
- IBM manufacturing installs FW1040 for customer orders with NED24 NVMe Expansion Drawers included. However, FW1030 is installed for customer orders without NED24 NVMe Expansion Drawers.
- IBM is not planning to release IBM i PTFs for FW1040. Support will continue for the FW1030 stream ONLY until the next firmware release is published.
Read the following important information prior to installing this Release level.
Service Pack Summary: New Release level (disruptive install).
When installing the FW1030 firmware to a system that previously was at a FW1020 level, you need to complete the upgrade then perform the upgrade again consecutively. This to ensure both the T (temporary, also known as current) and P (permanent, also known as backup) are equal. This was previously known as the "Accept" process that was performed automatically. This will be addressed in a newer release/PTF of the HMC to automatically do the accept. Improvements in FW1030.00 and higher to the eBMC will cause any IPL from a backup side that is at a FW1020 firmware level to fail. An AC power cycle would be required to recover from this condition.
For systems with Power Linux partitions, support was added for a new Linux secure boot key. The support for the new secure boot key for Linux partitions may cause secure boot for Linux to fail if the Linux OS for SUSE or RHEL distributions does not have a secure boot key update. The affected Linux distributions as follows need the Linux fix level that includes "Key for secure boot signing grub2 builds ppc64le" : 1) SLES 15 SP4 - The GA for this Linux level includes the secure boot fix. 2) RHEL 8.5- This Linux level has no fix. The user must update to RHEL: 8.6 or RHEL 9.0. 3) RHEL 8.6 4) RHEL 9.0. Please note for this firmware level, any Linux OS partition not updated to a secure boot fix level will fail to secure boot.
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 legacy HMC that runs on x86/Intel/AMD hardware for the Virtual HMC that can run on the Intel hypervisors (KVM, XEN, VMWare ESXi).
ppc64 or ppc64le - describes the Linux code that is compiled to run on Power-based servers or LPARS (Logical Partitions)
- The Minimum HMC Code level for this firmware is: HMC V10R21040 (PTF MF70893/ MF70894)
PTF MF70893 HMC V10 R2M1040.0 – for vHMC for x86_64 hypervisors (5765-VHX)
PTF MF70894 HMC V10 R2M1040.0 – for 7063 Hardware or vHMC for PowerVM (5765-HMB)
- 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-CR1 and 7063-CR2
x86 - KVM, XEN, VMWare ESXi (6.0/6.5)
ppc64le - vHMC on PowerVM (POWER8,POWER9, and POWER10 systems)
For information concerning HMC releases and the latest PTFs, go to the following URL to access 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).
- 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.
FW1030 needs to be installed twice when upgrading from FW1020 firmware levels
When installing the FW1030 firmware to a system that previously was at a FW1020 level, you need to complete the upgrade then perform the upgrade again consecutively. This to ensure both the T (temporary, also known as current) and P (permanent, also known as backup) are equal. This was previously known as the "Accept" process that was performed automatically. This will be addressed in a newer release/PTF of the HMC to automatically do the accept.
Improvements in FW1030.00 and higher to the eBMC will cause any IPL from a backup side that is at a FW1020 firmware level to fail. An AC power cycle would be required to recover from this condition.
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 a 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.
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 can be found at: https://www.ibm.com/docs/en/power10/9105-42A?topic=resources-memory
Power10 servers contain SBEs (Self Boot Engines) and are used to boot the system. SBE is internal to each of the Power10 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 a SBE change. If there is a SBE change and 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 on to the IPL. If there is a SBE change and the system firmware update is disruptive, then SBE update will cause an additional 3-5 minutes per processor chip in the system to be added on to 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 system boot should be 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 image is updated with this service pack.
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 Update Descriptions" 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:
- xxx 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 (xxx). For example, 01ML1010_040_040 and 01ML1020_040_040 are different service packs.
An installation is disruptive if:
- The release levels (xxx) are different.
Example: Currently installed release is 01ML1010_040_040, new release is 01ML1020_050_050.
- The service pack level (yyy) and the last disruptive service pack level (zzz) are the same.
Example: ML1020_040_040 is disruptive, no matter what level of ML1020 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 ML1010_040_040 and new service pack is ML1020_050_045.
An installation is concurrent if:
The release level (xxx) 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 ML1010_040_040, new service pack is ML1010_041_040.
Firmware Information and Description
ie: sum 01ML1040_021_021.img
For Impact, Severity and other Firmware definitions, Please refer to the below 'Glossary of firmware terms' url:
|ML1040_021_021 / FW1040.00
Impact: New Severity: New
GA Level with key features listed below. All features and fixes are included from FW1030.20 but are not explicitly listed here except for the following feature exceptions that are not supported for FW1040.00:
New features and functions
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: (ML1020_079)
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 will need to download the new firmware level to a USB flash memory device or ftp server.
Installing the Firmware
The method used to install new firmware will depend 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.
Where xxx = release level
- If the release level will stay the same (Example: Level ML1020_040_040 is currently installed and you are attempting to install level ML1020_041_040) this is considered an update.
- If the release level will change (Example: Level ML1020_040_040 is currently installed and you are attempting to install level ML1030_050_050) this is considered an upgrade.
Instructions for installing firmware updates and upgrades can be found at https://www.ibm.com/docs/en/power10/9105-42A?topic=9105-42A/p10eh6/p10eh6_updates_sys.htm
IBM i Systems:
For information concerning IBM i Systems, go to the following URL to access 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.
Instructions for installing firmware updates and upgrades on systems co-managed by an HMC and Novalink is the same as above for a HMC managed systems since the firmware update must be done by the HMC in the co-management master mode. Before the firmware update is attempted, one must be sure that HMC is set in the master mode using the steps at the following IBM KnowledgeCenter link for NovaLink co-managed systems:
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>). The operation failed. E302F861 is the error code:"
The complete Firmware Fix History (including HIPER descriptions) for this Release level can be reviewed at the following url:
Was this topic helpful?
22 May 2023