Products
H3C UniServer B5700 G5
Restrictions and cautions
Restrictions
The upgrade to BIOS-5.24 or later from an earlier version on the HDM Web interface for the R4900 G5, R4700 G5, R5300 G5, R5500 G5(Intel), S4703 G5, S2703 G5, B5700 G5, or H3C UniStor X10000 G5 supports only the Forcedly restore method. To retain the user-configured settings in the earlier version, perform the following operations:
a.Export the configuration file of the earlier version.
b.Upgrade to BIOS-5.24 or later by selecting the Forcedly restore method.
c.Import the configuration file of the earlier version after the upgrade.
The upgrade to BIOS-5.31 or later from an earlier version on the HDM Web interface for the R6900 G5 supports only the Forcedly restore method. To retain the user-configured settings in the earlier version, perform the following operations:
a.Export the configuration file of the earlier version.
b.Upgrade to BIOS-5.31 or later by selecting the Forcedly restore method.
c.Import the configuration file of the earlier version after the upgrade.
As from release BIOS-5.53, if you use the AFU tool in the OS to perform an upgrade with the user-configured settings retained, you can retain the core disable number setting configured on the Advanced > Socket Configuration > Processor Configuration > Per-Socket Configuration > CPU Socket 1 Configuration screen. If you upgrade from BIOS-5.52 or an earlier version, the core disable number setting cannot be retained.
Guidelines
To avoid BIOS boot failures, do not upgrade or reset HDM during BIOS boot.
Version information
Version number
Version 5.57.10
Table 1 Target file name and MD5 checksum
Model | File name and MD5 checksum |
H3C UniServer B5700 G5 | B57-BIOS-5.57.10-signed.bin: 87692aebbb77c7119b40d5c6457fd344 UN-BPS_02.02.00.1553-signed.bin: edd144ec6baa0f43758d1971213cb386 UN-BPS_02.02.00.1553_Linux.rpm: 175533ad4ba99159d7ba756018eb6244 |
You can access the HDM Web interface of the server to identify the BIOS firmware version in the Device information section of the Dashboard > Summary page, as shown in Figure 1.
Figure 1 Viewing the BIOS version number from HDM

BIOS built-in software version
Table 2 BIOS built-in software version for the H3C UniServer R4300 G5, R4700 G5, R4900 G5, R4900LC G5, R5300 G5, R5500 G5(Intel), S4703 G5, S2703 G5, B5700 G5, and H3C UniStor X10000 G5
Item | Version |
Microcode | IceLake Production MCU: m_87_606a6_0d000375.mcb |
Intel BKC Version | 2022_WW23(KIT #732569) |
RC Code | Intel® Central Park Whitley Release 27P82 |
ME Firmware | SPS_E5_04.04.04.202.0 |
RSTe PreOS Components | v7.6.0.1012 |
VMD VROC | v7.6.0.1012 |
DCPMM UEFI and HII Driver | v02.00.00.3886 |
DCPMM Firmware | 02.02.00.1553 |
BIOS ACM | BIOS ACM v1.1.0/SINIT ACM v1.1.0 |
Table 3 BIOS built-in software version for the R6900 G5
Item | Version |
Microcode | CooperLake A0 MCU: mbf5065a_86000020.mcb CooperLake A1 MCU: mbf5065b_07002501.mcb |
Intel BKC version | 2022.3 IPU-PV(KIT#738662) |
RC code | Intel® Central Park Whitley Release 23P42 |
ME firmware | SPS_E5_04.04.04.202.0 |
RSTe PreOS components | v7.6.0.1012 |
VMD VROC | v7.6.0.1012 |
DCPMM UEFI and HII driver | v02.00.00.3887 |
DCPMM Firmware | 02.02.00.1553 |
BIOS ACM | BIOS ACM v1.3.4/ SINIT ACM v1.3.5 |
Hardware and software compatibility matrixes
| CAUTION: To avoid update failure, verify the hardware and software compatibility before performing an update. |
Table 4 Hardware and software compatibility matrix for H3C UniServer B5700 G5 compute node
Item | Specifications |
Model | H3C UniServer B5700 G5 |
HDM | Version 2.34 or later |
CPLDOM | 002UN_BLADE-OM-1.03.02 or later |
iMC | iom E0715 |
PMem 200 firmware version | UN-BPS_02.02.00.1553 |
Remarks | When updating the BIOS version, or installing, updating, or replacing the PMem 200 firmware, make sure the BIOS version is compatible with the PMem 200 firmware version. |
Update restrictions and guidelines
This version is recommended.
Make sure the software versions are compatible with each other.
To update both HDM and the BIOS, update HDM first.
Make sure the server is running in stable state before the update. That is, the server is powered off or has entered the operating system.
If the server enters the OS before the update, you must power cycle the server for the new firmware to take effect.
If you select the Retain or Restore method to update the BIOS, the update occurs during POST after the server is powered on again. During the update, do not disconnect the power source from the server, or forcedly power off or restart the server.
If you select the Forcedly restore method to update the BIOS, do not disconnect the power source from the server, or power off or restart the server.
Selecting the Restore or Forcedly restore method will restore the default BIOS settings, including restoring the boot mode in the BIOS to the default (UEFI).
During BIOS update with Forcedly restore selected, writing BIOS data, such as restarting the system or saving BIOS configuration from the BIOS setup utility, can cause data write errors. This can lead to BIOS ROM integrity check failures and even system starting failures. If the system prompts Flash Image Broken! System Halt!, forcedly power off the server, and then try to update the BIOS with Forcedly restore selected again.
As a best practice of bulk update, make sure you can update one server successfully before you update the remaining servers.