Power10 System Firmware
Applies
to: 9080-HEX
This document provides information about the installation of
Licensed Machine or Licensed Internal Code, which is sometimes referred
to generically as microcode or firmware.
Contents
1.0
Systems Affected
This
package provides firmware for IBM Power System E1080
(9080-HEX) server
only.
The firmware level in this package is:
1.1 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).
- The Minimum HMC Code level for this firmware is: HMC V10R1M1010 (PTF MF68914).
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 V10R1M1010 (PTF MF68914).
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:
http://www-933.ibm.com/support/fixcentral/
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):
http://www14.software.ibm.com/webapp/set2/flrt/home
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.
2.0 Important Information
NovaLink
levels earlier than "NovaLink 1.0.0.16 Feb 2020 release" with
partitions running certain SR-IOV capable adapters is NOT supported at
this firmware release
NovaLink levels earlier than "NovaLink 1.0.0.16 Feb 2020 release" do
not support IO adapter FCs EC2R/EC2S, EC2T/EC2U, EC66/EC67 with FW1010
and later.
Live Partition
Mobility (LPM) support restrictions for FW1010.00:
The LPM restrictions given below are for FW1010 as the LPM target
system and for FW1010 as LPM source system for the specified Peer
System firmware level.
+---------------+-------------------------------+
| FW1010 LPM Restrictions |
+---------------+-------------------------------+
| Peer System | Result |
+---------------+-------------------------------+
| FW8xx | LPM supported |
+---------------+-------------------------------+
| FW910 | LPM supported |
+---------------+-------------------------------+
| FW920 | LPM currently not supported |
+---------------+-------------------------------+
| FW930 | LPM currently not supported |
+---------------+-------------------------------+
| FW940 | LPM supported with system key |
| previous to | |
| FW940.41 | |
+---------------+-------------------------------+
| FW940.41 and | LPM supported |
| later | |
+---------------+-------------------------------+
| FW941 | LPM supported with system key |
+---------------+-------------------------------+
| FW950 | LPM supported with system key |
| previous to | |
| FW950.20 | |
+---------------+-------------------------------+
| FW950 | LPM supported |
| FW950.20 and | |
| later | |
+---------------+-------------------------------+
| FW1010 | LPM supported |
+---------------+-------------------------------+
The following article provides information on how to configure the
trusted system key to enable certain cases of LPM support where "with
system key" is specified in the above table: https://ibm.biz/Bdf8wz/
vNIC and Hybrid Network Virtualization (HNV) system
configurations are not supported in any migrations to and from FW1010.
Note: The following IBM document article for the LPM support
matrix for POWER10 does not list the cases where FW1010.00 does
not have LPM support in the initial GA, so the above table should
be consulted for the specific limitations:
https://www.ibm.com/docs/en/power10?topic=mobility-firmware-support-matrix-partition
2.1 IPv6 Support and
Limitations
IPv6 (Internet Protocol version 6)
is supported in the System Management Services (SMS) in this level of
system firmware. There are several limitations that should be
considered.
When configuring a network interface
card (NIC) for remote IPL, only the most recently configured protocol
(IPv4 or IPv6) is retained. For example, if the network interface card
was previously configured with IPv4 information and is now being
configured with IPv6 information, the IPv4 configuration information is
discarded.
A single network interface card
may only be chosen once for the boot device list. In other words, the
interface cannot be configured for the IPv6 protocol and for the IPv4
protocol at the same time.
2.2 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 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.
2.3 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 can be found
at:
https://www.ibm.com/support/knowledgecenter/9080-M9S/p9hat/p9hat_lparmemory.htm
2.4 SBE Updates
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.
3.0 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
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:
01VHxxx_yyy_zzz
- 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, 01VH900_040_040 and 01VH910_040_045 are different
service packs.
An installation is disruptive if:
- The release levels (xxx) are
different.
Example:
Currently installed release is 01VH900_040_040,
new release is 01VH910_050_050.
- The service pack level (yyy) and the last disruptive
service pack level (zzz) are the same.
Example: VH910_040_040
is disruptive, no matter what level of VH910 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 VH910_040_040 and new service pack
is VH910_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 VH910_040_040, new
service pack is VH910_041_040.
3.1 Firmware
Information and Description
Filename |
Size |
Checksum |
md5sum |
01MH1010_075_075.rpm |
146325165
|
32065
|
13b49c586028755d82aefb3f8f836111
|
Note: The Checksum can be found by running the AIX sum command against
the rpm file (only the first 5 digits are listed).
ie: sum 01MH1010_075_075.rpm
MH1010
For Impact, Severity and other Firmware definitions, Please refer to
the below 'Glossary of firmware terms' url:
http://www14.software.ibm.com/webapp/set2/sas/f/power5cm/home.html#termdefs
The
complete Firmware Fix History for this Release Level can be reviewed at
the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/MH-Firmware-Hist.html
|
MH1010_075_075 / FW1010.02
10/14/21 |
Impact: Availability
Severity: Hiper
System firmware changes that
affect all systems
- HIPER/Non-Pervasive: A problem was fixed for a
system checkstop during a power on IPL when service processor FSP B is
the primary with SRC BC50E504 logged. This problem always happens
if FSP B is in the primary role for the IPL. If FSP B is
currently the primary service processor, this problem can be
circumvented by doing an HMC FSP failover to make FSP A the primary and
FSP B the secondary.
- A problem was fixed for a Power Management halt error that
could prevent the On-Chip Controller (OCC) Safe mode from being fully
achieved (OCC is disabled but frequencies are not throttled), resulting
in the system running at valid high voltage and frequencies but without
the means to react to future thermal events. This could cause the
processors to run too hot and generate over-temperature warnings in
some situations.
This fix updates the Self-Boot Engine (SBE).
|
MH1010_069_069 / FW1010.01
09/28/21 |
Impact: Availability
Severity: Hiper
This service pack is a mandatory install service pack.
New Features and Functions
- DEFERRED: The Minimum Secure Version level was
updated to correlate to FW1010.01. This change will prevent a
back-level firmware update of the system to FW1010.00
System firmware changes that
affect all systems
- HIPER/Non-Pervasive: A problem was fixed
for memory DIMM failures during the IPL with SRCs BC20090F and BC20E504
logged. This is an intermittent and rare problem for a false
memory training error that can be recovered from by unguarding the
failed DIMMs and doing another IPL of the system.
- HIPER/Non-Pervasive: A problem was fixed for
processor spare lane deployment in case of lane failures. Without
the spare lane fix the processor bus goes to half-bandwidth with a
degrade in performance when there are link errors. To recover
from this error, the processor must be replaced.
- A problem was fixed for a system failure during processor
recovery with SRC B113E504 logged. The occurrence of errors which
trigger the need for processor recovery are rare.
- A security problem was fixed for the PowerVM Hypervisor
that could allow a privileged user to gain access to another VM due to
an assignment of duplicate World Wide Port Names (WWPNs). In some
cases, the PowerVM hypervisor can assign duplicate WWPN ids to virtual
fiber channel adapters in peer VMs after a specific series of service
actions are performed The WWPN needs to be a unique identifier in
the network. This Common Vulnerabilities and Exposures(CVE)
id is CVE-2021-38923.
|
MH1010_064_064 / FW1010.00
09/17/21 |
Impact:
New Severity: New
GA Level with key features included listed below.
New Features and Functions
- This server firmware includes the SR-IOV adapter firmware
level xx.30.1004 for the following Feature Codes and CCINs: #EC2R/EC2S
with CCIN 58FA; #EC2T/EC2U with CCIN 58FB; and #EC66/EC67 with CCIN
2CF3.
- Added support in ASMI for a new panel to do Self-Boot
Engine (SBE) SEEPROM validation. This validation can only be run
at the service processor standby state.
If the validation detects a problem, IBM recommends the system not be
used and that IBM service be called.
- Support was added for a new service processor command that
can be used to 'lock' the power management mode, such that the mode can
not be changed except by doing a factory reset.
- Support was changed to disable Service Location Protocol
(SLP) by default for newly shipped systems or systems that are reset to
manufacturing defaults. This change has been made to reduce
memory usage on the service processor by disabling a service that is
not needed for normal system operations.
- Support was added to generate a service processor fipsdump
whenever there is Hostboot (HB) TI and HB dump. Without this new
support, an HB crash (with an HB dump) does not generate a fipsdump and
the FSP FFDC at that point in time. So it was difficult to correlate
what was seen in the HB dump to what was happening on the FSP at the
time of the HB fail.
- Support added to Redfish to provide a command to set the
ASMI user passwords using a new AccountService schema. Using this
service, the ASMI admin, HMC, and general user passwords can be changed.
- Support for Live Partition Mobility (LPM) to allow LPM
migrations when virtual optical devices are configured for a source
partition. LPM automatically removes virtual optical devices as
part of the LPM process. Without this enhancement, LPM is blocked
if virtual optical devices are configured.
- Support for Live Partition Mobility (LPM) to select the
fastest network connection for data transfer between Mover Service
Partitions (MSPs). The configured network capacity of the adapters is
used as the metric to determine what may provide the fastest
connection. The MSP is the term used to designate the Virtual I/O
Server that is chosen to transmit the partition’s memory contents
between source and target servers.
- Support has been dropped for the smaller logical-memory
block (LMB) sizes of 16MB, 32MB, and 64MB. 128MB and 256MB are the only
LMB sizes that can be selected in ASMI.
- Support has been dropped for Active Memory Sharing (AMS) on
POWER10 servers.
- Support for PowerVM
for an AIX Update Access Key (UAK) for AIX 7.2. Interfaces are
provided that validate the OS image date against the AIX UAK expiration
date. Informational messages are generated when the release date
for the AIX operating system has passed the expiration date of the AIX
UAK during normal operation. Additionally, the server periodically
checks and informs the administrator about AIX UAKs that are about to
expire, AIX UAKs that have expired, or AIX UAKs that are missing. It is
recommended that you replace the AIX UAK within 30 days prior to
expiration.
For more information, please refer to the Q&A
document for "Management of AIX Update Access Keys" at
https://www.ibm.com/support/pages/node/6480845.
- Support for LPAR Radix Page Table mode in PowerVM.
- Support for PowerVM encrypted NVRAM that enables encryption
of all partition NVRAM data and partition configuration information.
- Support for isolating faults to a single node that occur
between an SMP cable and two nodes using Time Domain Reflectometry
(TDR).
- Support for booting IBM i from a PCIe4 LP 32Gb 2-port
Optical Fibre Channel Adapter with Feature Code #EN1K.
- Support for VIOS 3.1.3 (based on AIX 7.2 TL5 (AIX 72X) on
POWER10 servers.
- Support for the IBM 4769 PCIe3 Cryptographic Coprocessor
hardware security module (HSM). This HSM has Feature Code #EJ37
with CCIN C0AF. Its predecessors are IBM 4768, IBM 4767, and IBM
4765.
- Support for a mainstream 800GB NVME U.2 7 mm SSD (Solid
State Drive) PCIe4 drive in a 7 mm carrier with Feature Code #EC7Q and
CCIN 59B4 for AIX, Linux, and VIOS.
- Support for a PCIe4 x16 to CXP Converter card for the
attachment of two active optical cables (AOC) to be used for external
storage and PCIe fan-out attachment to the PCIe expansion
drawers. This cable card has Feature Code #EJ24 and CCIN 6B53.
- Support for new PCIe 4.0 x8 dual-port 32 Gb optical Fibre
Channel (FC) short form adapter based on the Marvell QLE2772 PCIe host
bus adapter (6.6 inches x 2.731 inches). The adapter provides two ports
of 32 Gb FC capability using SR optics. Each port can provide up to
6,400 MBps bandwidth. This adapter has feature codes #EN1J/#EN1K with
CCIN 579C.
- Support for new PCIe 3.0 16 Gb quad-port optical Fibre
Channel (FC)l x8 short form adapter based on the Marvell QLE2694L PCIe
host bus adapter (6.6 inches x 2.371 inches). The adapter provides four
ports of 16 Gb FC capability using SR optics. Each port can provide up
to 3,200 MBps bandwidth. This adapter has feature codes #EN1E/#EN1F
with CCIN 579A.
|
4.0 How to
Determine The Currently Installed Firmware Level
You can view the server's
current firmware level on the Advanced System Management Interface
(ASMI) Welcome pane. It appears in the top right corner. Example:
VH920_123.
5.0
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.
6.0 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.
Example: MHxxx_yyy_zzz
Where xxx = release level
- If the release level will stay the same (Example: Level
VH920_040_040 is currently installed and you are attempting to install
level VH920_041_040) this is considered an update.
- If the release level will change (Example: Level VH900_040_040 is
currently installed and you are attempting to install level
VH920_050_050) this is considered an upgrade.
Instructions for installing firmware updates and upgrades can be found
at https://www.ibm.com/support/knowledgecenter/9080-M9S/p9eh6/p9eh6_updates_sys.htm
IBM i Systems:
For information concerning IBM i Systems, go to the following
URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
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:
https://www.ibm.com/support/knowledgecenter/9009-22A/p9eig/p9eig_kickoff.htm
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:"
https://www.ibm.com/support/knowledgecenter/9009-22A/p9eh6/p9eh6_updates_sys.htm
7.0 Firmware History
The complete Firmware Fix History (including HIPER descriptions)
for this Release level can be reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/MH-Firmware-Hist.html