Supported products
H3C UniServer R3900 G7
Restrictions and cautions
Restrictions
None.
Guidelines
To avoid BIOS boot failures, do not upgrade or reset HDM during BIOS boot.
Version information
Version number
Version 7.10.19
Image file name and MD5 checksum:
BIOS-7.10.19-signed.bin: aad60c91f45a62a9e3e79a05e12bad3c
You can access the HDM Web interface of the server to identify the BIOS firmware version in the Device information section of the Dashboard page, as shown in Figure 1.
Figure 1 Viewing the BIOS version number from HDM

BIOS built-in software version
Table 1 AP CPU BIOS built-in software version
Item | Version |
Microcode | GNR B* Production MCU: m_95_a06d1_010003d0.inc |
Intel BKC version | 2025_WW25 |
Intel RC version | 3544P64 |
BIOS ACTM | GNR V01.00.00 |
VROC UEFI | 9.1.2.1002 |
Production BIOS ACM / Production SINIT ACM Binaries | v1.0.7 |
Seamloader Version | GNR SEAMLDR 2.0.00.20 |
TDX module version | GNR 2.0.08.00.882 |
Supported languages
English
Chinese
Supported devices
Hardware series | PUID |
H3C UniServer R3900 G7 | R3900-G7-UAS0 R3900-G7-UAL0 |
Hardware and software compatibility matrixes
| CAUTION: To avoid update failure, verify the hardware and software compatibility before performing an update. |
Table 2 Hardware and software compatibility matrix for H3C UniServer R3900 G7
Item | Specifications |
Product family | H3C UniServer R3900 G7 |
HDM | HDM3-2.10 and later |
CPLD | V003 and later |
iMC | N/A |
Update suggestions
This version is recommended.
Update restrictions and guidelines
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.