Description

This software is used to upgrade the BIOS version of the R3950 G6 server

Installation steps

Publish Description

Restrictions and cautions

Restrictions

This release is applicable only to H3C UniServer R4950 G6 (Genoa CPU).

Guidelines

To avoid BIOS errors, do not upgrade or reset HDM2 during BIOS boot.

Version information

Version number

Version 6.30.37P02

Table 1 Target file name and MD5 checksum

You can access the HDM Web interface of the server to identify the BIOS firmware version on the Dashboard page, as shown in Figure 1. The figure is for illustration only and the version number in the figure is not the version released this time.

Figure 1 Viewing the BIOS version number from HDM

Table 2 R4950 G6 version history

Table 3 R3950 G6 version history

BIOS built-in software version

Table 4 BIOS built-in software version

Supported languages

English

Chinese

Supported Devices

H3C UniServer R4950 G6

H3C UniServer R3950 G6

Hardware and software compatibility matrixes

Table 5 Hardware and software compatibility matrix for the R4950 G6 Genoa

Table 6 Hardware and software compatibility matrix for the R3950 G6 Genoa

Upgrade recommendation

This version is recommended.

Update restrictions and guidelines

This version is recommended.

Make sure the software versions are compatible with each other.

To update both HDM2 and the BIOS, update HDM2 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).

As a best practice of bulk update, make sure you can update one server successfully before you update the remaining servers.

Problems Solved

Resolved problems in BIOS-6.30.37P02

202503170751

Symptom: When the power supply is not in place, viewing smbios type 39 information under Shell shows plugged as yes.

Condition: Viewing type 39 information when the power distribution is not fully equipped.

202503210313

Symptom: When setting the IPv6 network to static in BIOS, the Prefix Length and IPv6 Router IP Address are filled in incorrectly.

Condition: Setting the IPV6 network configuration to static under SETUP.

New Functions

Version:6.30.39(2025/6/4)

Upgrade recommendations

Recommended Upgrade

Problems Solved

Resolved problems in BIOS-6.30.39

202503211562

Symptom: The R3950 G6 model needs to adapt to the GPU SL200 PRO.

Condition: Inserting the SL200 GPU into the R3950 G6.

202504011137

Symptom: The default PK for SecureBoot in the BIOS package needs to use the PK generated by H3C BIOS, removing the test PK provided by IBV.

Condition: Update requirement for the PK corresponding to the SecureBoot function.

202505121843

Symptom: The customized options "Enable Requested CPU min frequency" and "Requested CPU min frequency" are non-default values, and importing the customized package fails to modify the options.

Condition: Customization of the package for "Enable Requested CPU min frequency" and "Requested CPU min frequency".

202504162006

Symptom: Pressing the physical power button shortly after powering on causes the BMC to not fully start, resulting in the BIOS being unable to obtain a valid OEM flag to enter the load default process; BIOS values do not match customized values.

Condition: Pressing the physical power button shortly after powering on while the BMC has not fully started.

202505070131

Symptom: [ITST][BIOS GNA][Production Requirement] MBIST reports socket number not starting from 1.

Condition: Enable MBIST function and check the location information of the faulty memory reported by MBIST.

202505191929

Symptom: False positive report of Driver fault issue during NVMe hot swapping, need to optimize VPP I2C hot swapping address.

Condition: Fully populated NVMe drives and repeatedly perform hot swapping tests.

New Functions

Version:6.30.37P02(2025/4/10)

Upgrade recommendations

Recommended Upgrade

Problems Solved

Resolved problems in BIOS-6.30.37P02

202503170751

Symptom: When the power supply is not in place, viewing smbios type 39 information under Shell shows plugged as yes.

Condition: Viewing type 39 information when the power distribution is not fully equipped.

202503210313

Symptom: When setting the IPv6 network to static in BIOS, the Prefix Length and IPv6 Router IP Address are filled in incorrectly.

Condition: Setting the IPV6 network configuration to static under SETUP.

New Functions

Version:6.30.33(2024/9/24)

Upgrade recommendations

Recommended Upgrade

Problems Solved

Resolved problems in BIOS-6.30.33

Symptom: The PI 100C upgrade feature is added to the trunk.

Condition: This symptom might occur if the Codebase version has not been upgraded to PI100C.

Symptom: The dmidecode command failed to obtain the power module model and firmware version.

Condition: This symptom might occur if Type 39 failed to obtain the power module model and firmware version from FRU information.

Symptom: The Push Memory Map feature is added to the trunk.

Condition: This symptom might occur if the Push Memory Map feature is not implemented.

New Functions

Version:6.30.30(2024/5/14)

Upgrade recommendations

Recommended Upgrade

Problems Solved

Resolved problems in BIOS-6.30.30

Symptom: The non-brand model removes the QR code from the BIOS page.

Condition: This symptom might occur because a new QR code need is added in the BIOS.

Symptom: Added support for the PI100B upgrade feature.

Condition: This symptom might occur if an upgrade is triggered by a CPU issue for the AMD.

Symptom: The memory loss might occur during the device restart.

Condition: This symptom might occur if the device restarts.

New Functions