Download

Title	Size	Downloads
MIB.zip	3.14 MB
H3C HDM Redfish API Reference.pdf	5.34 MB
H3C HDM IPMI Basics Command Reference.pdf	3.86 MB
G5-HDM-3.39.zip	39.81 MB
HDMC HDM-3.39 Release Notes.pdf	1.83 MB

H3C HDM-3.39 Release Notes

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.

Contents

Supported hardware platforms

Hardware and software compatibility matrix

Upgrade restrictions and guidelines

Upgrade recommendation

Hardware feature upgrades

Software feature and command upgrades

Restrictions and cautions

Restrictions

Guidelines

Open problems and workarounds

List of resolved problems

Resolved problems in HDM-3.39

Resolved problems in HDM-3.38.01

Resolved problems in HDM-3.38

Resolved problems in HDM-3.37.01

Resolved problems in HDM-3.37

Resolved problems in HDM-3.36.01

Resolved problems in HDM-3.36

Resolved problems in HDM-3.35.11

Resolved problems in HDM-3.35.01

Resolved problems in HDM-3.35

Resolved problems in HDM-3.34.02

Resolved problems in HDM-3.34.01

Resolved problems in HDM-3.34

Resolved problems in HDM-3.33

Resolved problems in HDM-3.32

Resolved problems in HDM-3.31

Resolved problems in HDM-3.30

Resolved problems in HDM-3.27

Resolved problems in HDM-3.26

Resolved problems in HDM-3.22

Resolved problems in HDM-3.21

Resolved problems in HDM-3.18

Resolved problems in HDM-3.16

Resolved problems in HDM-3.13

Resolved problems in HDM-3.12

Resolved problems in HDM-3.11

Resolved problems in HDM-3.10.21

Resolved problems in HDM-3.10

Resolved problems in HDM-2.99

Resolved problems in HDM-2.98

Resolved problems in HDM-2.97.03

Resolved problems in HDM-2.97.02

Resolved problems in HDM-2.97

Resolved problems in HDM-2.95.05

Resolved problems in HDM-2.95

Resolved problems in HDM-2.93

Resolved problems in HDM-2.92

Resolved problems in HDM-2.91

Resolved problems in HDM-2.87

Resolved problems in HDM-2.86

Resolved problems in HDM-2.81

Resolved problems in HDM-2.80

Resolved problems in HDM-2.78

Resolved problems in HDM-2.76

Resolved problems in HDM-2.73

Resolved problems in HDM-2.70

Resolved problems in HDM-2.64

Resolved problems in HDM-2.63

Resolved problems in HDM-2.60

Resolved problems in HDM-2.59

Resolved problems in HDM-2.58

Resolved problems in HDM-2.57

Resolved problems in HDM-2.55

Resolved problems in HDM-2.54

Resolved problems in HDM-2.53

Resolved problems in HDM-2.52

Resolved problems in HDM-2.51

Resolved problems in HDM-2.48

Resolved problems in HDM-2.47

Resolved problems in HDM-2.43

Resolved problems in HDM-2.42

Resolved problems in HDM-2.41

Resolved problems in HDM-2.40

Resolved problems in HDM-2.32

Resolved problems in HDM-2.31

Resolved problems in HDM-2.29

Resolved problems in HDM-2.27

Resolved problems in HDM-2.25

Resolved problems in HDM-2.24

Resolved problems in HDM-2.23

Resolved problems in HDM-2.18.12

Resolved problems in HDM-2.18

Resolved problems in HDM-2.17

Resolved problems in HDM-2.16.31

Resolved problems in HDM-2.16

Resolved problems in HDM-2.13

Resolved problems in HDM-2.09.00

Resolved problems in HDM-2.07.00

Troubleshooting

Introduction

This document describes the features, restrictions and guidelines, open problems, and workarounds for version HDM-3.39. Before you use this version on a live network, back up the configuration and test the version to avoid software upgrade affecting your live network.

Use this document in conjunction with the documents listed in "Related documentation."

Screenshots in this document are for illustration only.

Version information

Version number

Image file names and the MD5 checksum:

G3-HDM-3.39_signed.bin: 2a82dd12ef67dbecde47e48c798b83ef

G5-HDM-3.39_signed.bin: 21ee13a422b1d6bc7040703598915738

HDM version:

Current version: 3.39

Previous version: 3.38.01

NOTE:

You can access the HDM Web interface of the server to identify the HDM version in the Device information section of the Dashboard page.

Supported languages

HDM supports the following languages:

Chinese.

English.

Supported browsers

As a best practice, use one of the following browsers:

IE 11 or higher.

Firefox 50 or higher.

Chrome 48 or higher.

Supported hardware platforms

H3C UniServer R4700 G5

H3C UniServer R4700LC G5

H3C UniServer R4900 G5

H3C UniServer R4900LC G5

H3C UniServer R4300 G5

H3C UniServer R4300 G3

H3C UniServer R6900 G5

H3C UniServer R6700 G3

H3C UniServer R5500 G5 Intel

H3C UniServer R5500 G5 AMD

H3C UniServer R5300 G5

H3C UniServer R5500K

H3C UniServer R4330 G5

H3C UniServer R4330 G5 H3

H3C UniServer R4930 G5

H3C UniServer R4930 G5 H3

H3C UniServer R4930LC G5 H3

H3C UniServer R4950 G5

H3C UniServer B5700 G5

H3C Uniserver B5700 G3

H3C Uniserver B5800 G3

H3C Uniserver B7800 G3

H3C Uniserver B16000 AE G3

H3C UIS B460 G3

H3C UIS B580 G3

H3C UIS B780 G3

H3C UIS UIS9000 UISM G3

Hardware and software compatibility matrix

CAUTION:

To avoid an upgrade failure, use the following tables in this section to verify the hardware and software compatibility before performing an upgrade.

Table 1 Hardware and software compatibility matrix (for the R4300 G3)

Item	Specifications
Product family	H3C UniServer R4300 G3
BIOS	Version 2.00.62 or later
CPLD	005 or later
EXP	Single RAID: RS3EB24LN012.00.03 or later Dual RAID: RS3EB24LN022.00.03 or later
iMC	iom E0707H01
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 2 Hardware and software compatibility matrix (for the R4300 G5)

Item	Specifications
Product family	H3C UniServer R4300 G5
BIOS	Version 5.58 or later
CPLD	001 or later
iMC	iom E0707H01
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 3 Hardware and software compatibility matrix (for the R6900 G5)

Item	Specifications
Product family	H3C UniServer R6900 G5
BIOS	Version 5.54 or later
CPLD	007 or later
PFR CPLD	005 or later
iMC	iom E0707H01
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 4 Hardware and software compatibility matrix (for the R4900/R4700/R4900LC/R4700LC G5)

Item	Specifications
Product family	H3C UniServer R4900/R4700/R4900LC/R4700LC G5
Hygon 2 BIOS	Version 5.61 or later
CPLD	Version 005 or later
iMC	iom E0707H01
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 5 Hardware and software compatibility matrix (for the R8900 G3)

Item	Specifications
Product family	H3C UniServer R8900 G3
BIOS	Version 2.00.65 or later
NODE CPLD	Version 003 or later
SMC CPLD	Version 003 or later
PDB1 CPLD	Version 004 or later
PDB2 CPLD	Version 002 or later
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 6 Hardware and software compatibility matrix (for the R6700 G3)

Item	Specifications
Product family	H3C UniServer R6700 G3
BIOS	Version 2.00.62 or later
CPLD	Version 003 or later
STBCPLD	Version 003 or later
DB CPLD	Version 005 or later
iMC	iom E0707H01
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 7 Hardware and software compatibility matrix (for the R4900 G3/R4700 G3/R2900 G3/R2700 G3)

Item	Specifications
Product family	H3C UniServer R4900 G3/R4700 G3/R2900 G3/R2700 G3
BIOS	Version 2.00.63P10 or later
CPLD(24DIMM)	Version 004 or later
CPLD(16DIMM)	Version 004 or later
EXP	Version RS3E25B062.00.04 or later
iMC	iom E0707H01
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 8 Hardware and software compatibility matrix (for the R4930 G5)

Item	Specifications
Product family	H3C UniServer R4930 G5
Hygon 2 BIOS	Version 5.29 or later
CPLD	Version 009 or later
iMC	iom E0711
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 9 Hardware and software compatibility matrix (for the R4930 G5 H3)

Item	Specifications
Product family	H3C UniServer R4930 G5 H3
Hygon 3 BIOS	Version 5.73 or later
CPLD	Version 009 or later
iMC	iom E0711
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 10 Hardware and software compatibility matrix (for the R4930LC G5 H3)

Item	Specifications
Product family	H3C UniServer R4930LC G5 H3
Hygon 3 BIOS	Version 5.73 or later
CPLD	Version 009 or later
iMC	iom E0711
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 11 Hardware and software compatibility matrix (for the R4950 G5)

Item	Specifications
Product family	H3C UniServer R4950 G5
Rome BIOS	Version 5.48 or later
Milan BIOS	Version 5.50 or later
CPLD	Version 00D or later
iMC	iom E0711
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 12 Hardware and software compatibility matrix (for the R5300 G3)

Item	Specifications
Product family	H3C UniServer R5300 G3
BIOS	Version 2.00.63P10 or later
CPLD	Version 006 or later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 13 Hardware and software compatibility matrix (for the S4703 G5)

Item	Specifications
Product family	H3C UniServer S4703 G5
BIOS	Version 5.50 or later
CPLD	Version 005 or later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 14 Hardware and software compatibility matrix (for the R5300 G5)

Item	Specifications
Product family	H3C UniServer R5300 G5
BIOS	Version 5.34 or later
CPLD	Version 005 or later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 15 Hardware and software compatibility matrix (for the R5500 G5 AMD)

Item	Specifications
Product family	H3C UniServer R5500 G5 AMD
Rome BIOS	Version 5.48 or later
Milan BIOS	Version 5.52 or later
CPLD	Version 00A or later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 16 Hardware and software compatibility matrix (for the R5500 G5 Intel)

Item	Specifications
Product family	H3C UniServer R5500 G5 Intel
BIOS	Version 5.65 or later
CPLD	Version 006 or later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 17 Hardware and software compatibility matrix (for the R5500 K)

Item	Specifications
Product family	H3C UniServer R5500 K
BIOS	Version 5.65 or later
CPLD	Version 001 or later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 18 Hardware and software compatibility matrix (for the B5700 G5 AMD)

Item	Specifications
Product family	H3C UniServer B5700 G5
BIOS	Version 5.28 or later
CPLD	Version 004 or later
iMC	UCenter SSA 7.3 (E0709P04)
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Table 19 Hardware and software compatibility matrix (for the H3C Uniserver B5700/B5800/B7800/B16000 AE G3 and H3C UIS B460/B580/B780/UIS9000 UISM G3)

Item	Specifications
Product family	H3C Uniserver B5700/B5800/B7800/B16000 AE G3 H3C UIS B460/B580/B780/UIS9000 UISM G3
BIOS	B5700 G3/B5800 G3/B7800 G3/B460 G3/B780 G3/B580 G3: 2.00.43P01 and later B16000 AE/UIS9000 UISM: 1.00.09 and later
CPLD	003 and later
EXP	BS1M2C0S061.02.02 and later
iMC	iom E0707
FIST	Version 2.35 or later
FIST SMS	Version 1.35 or later
iFIST	Version 1.35 or later

Upgrade restrictions and guidelines

Make sure the software versions are compatible with each other. For more information, see "Hardware and software compatibility matrix."

As a best practice, back up the configuration before you upgrade the firmware. For more information, see "(Optional) Backing up the current configuration."

To upgrade both HDM and the BIOS, upgrade HDM first.

Make sure the server operates correctly or is powered off during BIOS or HDM upgrade.

During the upgrade, make sure the network connection is available and do not refresh the Webpage.

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

To avoid HDM or operating system errors, do not power on or power off the server during the firmware upgrade.

After the firmware is upgraded, delete the browsing history before you re-log in to HDM. For more information, see "Clearing the browser cache."

Upgrade both the primary image and backup image to the same image version.

For the R4950 G5 with a Rome processor, to upgrade the BIOS from a version earlier than 5.15 to version 5.15 or later, first upgrade HDM to version 2.32 or later. If you do not do so, black screen of death occurs at device restart.

For the G3 Intel servers and G5 Intel servers of a version earlier than HDM-3.11 (excluded) and later than HDM-2.25 (included), configuration import might cause a power capping issue. As a best practice, disable power capping before upgrading HDM. You can disable power capping through IPMI or from the HDM Web interface.

Upgrade recommendation

This version is optional for upgrade.

Hardware feature upgrades

HDM-3-39

HDM-3.39 added support of the following hardware options for the R5300 G5:

Nvidia H800 GPU

Nvidia L40S GPU

RG800 Pro GPU

HDM-3.39 added support of the following hardware options for the R4930 G5 (H3):

GPU-RG800-32GB-FHFL

25SFF drive backplane PCA-BP-25SFF-2U-G5 used together with NVMe drives

HDM-3.39 added support of the following hardware options for the R4950 G5:

UN-RC-2FHFL-R3-2U-G5

HDM-3-38.01

HDM-3.38.01 added support of the following hardware options for the R4900 G5:

H460-B1 storage controller (no Micron chip)

H460-M1 storage controller (no Micron chip)

HDM-3-38

None.

HDM-3-37.01

HDM-3.37 added support of the following hardware options for the R4900 G5:

Enflame I20 GPU

HDM-3-37

HDM-3.37 added support of the following hardware options for the R5500 G5:

MCX75310AAS-HEAT

HDM-3.37 added support of the following hardware options for the R4930 G5 H3:

NIC-3S910-LP-2*25G

NIC-ETH-N10G-X2-LP-2P

ETH-Agilio-GX-LP-10Gb-2P

HDM-3-36.01

HDM-3.36.01 added support of the following hardware options for the R5500K:

MBF2H536C-CEUOT

HDM-3.36

HDM-3.36 added support of the following hardware options for the R4900 G5:

ScaleFlux CSD3000

L4 GPU

BCM957416N4160C

HDM-3.35.11

None.

HDM-3.35.01

HDM-3.35.01 added support of the following hardware options for the R4900 G5:

MBF2H512C-AEUOT

HDM-3.35

HDM-3.35 added support of the following hardware options for the R5500 G5 Intel:

MBF2H516C-CESOT

MBF2H516C-CEUOT

HDM-3.34.02

None.

HDM-3.34.01

None.

HDM-3.34

HDM-3.34 added support for the following hardware options:

On the R5300 G5:

Changed the display name of Biren BR104P

HW 300I DUO/300T PRO/300V

On the R4950 G5:

NIC-iETH-MBF2H536C-CEUOT

On the R4930 G5 H3:

NIC-ETH-MCX562A-ACAI-3S-2P

HDM-3.33

HDM-3.33 added support for the following hardware options:

On the R4900 G5:

Micron_u.3 7450

Intel DapuStor R5101 3.84TB drive

On the R5300 G5:

Kunlunxin RG800 GPU

Cambricon MLU590-H8 GPU

NVIDIA GPU L40

HDM-3.32

HDM-3.32 added support for the following hardware options:

On the R4900 G5:

DapuStor drives

On the R5300 G5:

GPU-BR104P-32GB

On the R4930 G5 H3:

NIC-ETH-SF400T-LP-4PGE

HDM-3.31

HDM-3.31 added support for the following hardware options:

On the R4900 G5:

U55C Xilinx FPGA

On the R4930 G5 H3:

GPU-Z100-16G-FHFL

GPU-Atlas 300I Pro-24G-LP

On the R5300 G5:

GPU-Z100L-32G-FHFL

16G EF-I20 GPU

HDM-3.30

HDM-3.30 added support for the following hardware options:

On the R4900 G5:

UH711a, UH610a, and UH630a drives

Huawei 1300W power supply

On the R5300 G5:

Lynxi GPU-HP300-8GB

On the R5500 G5 Intel and R5500 G5 AMD:

NVIDIA A800 8-GPU 80GB GPU (PG506)

HDM-3.27

HDM-3.27 added support for the following hardware options:

On the R5300 G5:

NVIDIA A800 80G GPU

HDM-3.26

HDM-3.26 added support for the following hardware options:

On the R5500 G5 Intel and R5500 G5 AMD:

NVIDIA A800 8-GPU 80GB GPU (PG510)

On the R4900 G5:

531F network adapter

YANGTZE MEMORY PE310 drive

On the R4930 G5 H3:

SSD-1.6T-NVMe-R5301

SSD-1.92T-NVMe-R5101

SSD-3.2T-NVMe-R5301

SSD-7.68T-NVMe-R5100

SSD-1.6T-NVMe-D5447

SSD-1.92T-NVMe-D5427

SSD-3.2T-NVMe-D5447

SSD-7.68T-NVMe-D5427

UN-RC-2HHHL-R4-2U-G5

HDM-3.22

None.

HDM-3.21

HDM-3.21 added support for the following hardware options:

On the R4900 G5:

LiteOn 1300W power supply.

HDM-3.18

HDM-3.18 added support for the following hardware options:

On the R4900 G3:

Union Memory UH811a 1.92T/3.84T/7.68T.

HDM-3.16

HDM-3.16 added support for the following hardware options:

On the R4900 G5:

CXMT memory module 32G-3200.

On the R4900 G3:

scaleflux CSD2000.

On the R4930 G5:

SSD-3.2T-NVMe-D6456-AIC.

HDM-3.13

HDM-3.13 added support for the following hardware options:

On the R5300 G5:

GPU_BAIDU_R200.

On the R4930 G5:

RS35RX16R riser card.

RS35B08LF 8LFF drive backplane.

On the R4900 G5:

NIC-X550T2G1P5-LP-2P network adapter.

HDM-3.12

HDM-3.12 added support for the following hardware options:

On the R5300 G5:

RT-Redriver-G5 PCIe module.

HDM-3.11

HDM-3.11 added support for the following hardware options:

On the R5300 G5:

IVA-K5-VA.

On the R4930 G5:

SSD-3.2T-NVMe-D6456.

SSD-6.4T-NVMe-D6456.

SSD-3.84T-NVMe-D6436.

SSD-7.68T-NVMe-D6436.

HDM-3.10.21

None.

HDM-3.10

HDM-3.10 added support for the following hardware options:

On the R4930 G5:

NIC-ETH-RP2000-LP-2P10G.

On the R5500 G5:

IB-P23644-B21-200Gb-1P.

On the R5300 G5:

P5520 hard drive

MBF2H516C-CESOT network adapter

NIC-MCX683105AN-HDAT-1*200G network adapter

HDM-2.99

HDM-2.99 added support for the following hardware options:

On the R4900 G3:

NIC-BCM95719A1904AC-LP-4P.

On the R5500 G3:

Great Wall 2000W power supply CRPS2000.

On the X10828 G5/X10536H G5/X10516H G5/X10828 G5:

4SFF Unibay drive backplane.

On the X10516H G5/X10529H G5/X10536H G5:

2LFF SAS/SATA drive backplane.

On the X10536H G5:

12LFF SAS/SATA drive backplane.

24LFF SAS/SATA drive backplane.

18SFF SAS/SATA+6LFF Unibay drive backplane.

On the X10828 G5:

2SFF Unibay drive backplane.

HDM-2.98

HDM-2.98 added support for the following hardware options:

On the R4900 G3:

DERA D527 1.92T.

HDM-2.97.03

None.

HDM-2.97.02

None.

HDM-2.97

HDM-2.97 added support for the following hardware options:

On the H3C UniStor X10536 G3:

ST01EB24LNI 24LFF drive backplane.

On the R4900 G5:

LITE-ON 2000W power supplies.

On the R4900 G3:

AliFlash 1.92T and 3.84T.

On the R5500 G5 Intel:

MCX512A-ACAT_C06-2*25G.

MCX516A-CCAT_C06-2*100G.

On the R4330 G5:

RS43B24L06ULF 24LFF drive backplane.

On the R4950 G5:

NIC-E810CQDA2OCPV3G-3S-2P.

NIC-BCM957504-N425G-3S-4P.

NIC-BCM957508-N2100G-2P.

iETH-MBF2H516A-CENOT.

HDM-2.95.05

HDM-2.95.05 added support for the following hardware options:

On the R4950 G5 and R4930 G5:

RS35B12L08ULF 12LFF drive backplane.

RS65B25SXP8YD 25SFF drive backplane.

On the R4930 G5:

GPU-MLU370-X4.

HDM-2.95

HDM-2.95 added support for the following hardware options:

On the R4900 G3:

RS33B12L08ULF 12LFF drive backplane.

HDM-2.93

HDM-2.93 added support for the following hardware options:

On the R5300 G5:

GPU-BI-V100-32G.

HDM-2.92

HDM-2.92 added support for the following hardware options:

On the R6900 G5:

RS65B25SXP8YD 25SFF drive backplane.

HDM-2.91

HDM-2.91 added support for the following hardware options:

On the R4300 G3:

PCIe module ALIMOC.

On the R4900 G3:

Smart network adapter iETH-MBF2H512C-AESOT-2P-25G.

On the R5300 G5:

A2-PCIe-16G.

On the R5500 G5:

A100-SXM4-80GB.

On the R6900 G5:

Drive backplane RS65B25SXP8YD 25SFFF.

On the R6700 G3:

Drive backplane RS33B25SXP8YD 25SFFF.

On the R4900 G3:

Drive backplane RS33B25SXP8YD 25SFFF.

HDM-2.87

HDM-2.87 added support for the following hardware options:

On the R4900 G3:

RS33NGT4MB for Mlom temperature sensor chip.

HDM-2.86

HDM-2.86 added support for the following hardware options:

On the R5300 G5:

KIOXIA 1.92T/3.84T/7.68T NVMe drive.

On the R4930 G5:

NIC-MCX4121A-F-B-25Gb-2P.

HDM-2.81

HDM-2.81 added support for the following hardware options:

On the R4900 G3:

Great Wall 1300W power supply GW-CRPS1300D3.

On the R4300 G3:

Great Wall 1300W power supply GW-CRPS1300D3.

On the R6700 G3:

Great Wall 1300W power supply GW-CRPS1300D3.

HDM-2.80

HDM-2.80 added support for the following hardware options:

On the R4950 G5:

Great Wall 1300W power supply GW-CRPS1300D3.

On the R5300 G5:

Network adapter NIC-MCX653106A-HDAT-2*200G.

Network adapter NIC-MCX623106AN-CDAT-2P.

Network adapter NIC- MCX623436AN-CDAB-2P.

HDM-2.78

HDM-2.78 added support for the following hardware options:

On the R4900 G3:

Network adapter IB-MCX653105A-HDAT-200G-1P.

HDM-2.76

HDM-2.76 added support for the following hardware options:

On the R4900 G3:

NIC-MCX512A-ACUT-2*25Gb Mellanox.

On the R6900 G5:

Great Wall 1300W power supply GW-CRPS1300D3.

Great Wall 1600W power supply GW-CRPS1600D2.

On the R4900 G5:

GPU module GPU_BAIDU_R200.

On the R5300 G5:

Storage controller RAID-P4408-MR-8i-2GB.

NIC-MCX623430MS-CDAB-2*100G.

On the R5500 G5:

NIC-MCX653106A-HDAT-2*200G.

On the R4950 G5:

SSD-3.84T-NVMe-PE8010.

GPU-A6000.

On the R4930 G5:

FAN-6056-2U-G5.

HDM-2.73

None.

HDM-2.70

HDM-2.70 added support for the following hardware options:

On the R4900 G3:

Samsung PM9A3 NVMe drive (960G) customized for big clients.

Samsung PM9A3 NVMe drive (1.92T) customized for big clients.

Samsung PM9A3 NVMe drive (7.68T) customized for big clients.

On the R5300 G5:

A100-PCIe-80GB GPU.

On the R4900 G5:

RD-4NVMe-G5 Redriver.

Great Wall 800W power supply GW-CRPS800N2.

Great Wall 1300W power supply GW-CRPS1300D3.

Great Wall 1600W power supply GW-CRPS1600D2.

HDM-2.64

None.

HDM-2.63

HDM-2.63 added support for the following hardware options:

Samsung PM9A3 NVMe drive (3.84T) customized for big clients on the R4900 G3.

HDM-2.60

HDM-2.60 added support for the following hardware options:

8SFF G3 drive backup backplane, 12LFF EXP G3 drive backup backplane, and revised 620F network adapter on the R4900G3.

NIC-BCM957508-P2100G-2P network adapter and NIC-BCM957414N4140C-3S-2P network adapter on the R5500 G5 AMD.

NIC-ETH-XL710-LP-10G-4P network adapter on the R4930 G5.

HDM-2.59

HDM-2.59 added support for the following hardware options:

RS65B25SXP8YC 25SFF drive backplane on the R4900 G3.

HDM-2.58

None.

HDM-2.57

HDM-2.57 added support for the following hardware options:

SSD-7.68T-NVMe-D5437-UCC drive on the R4900 G5.

HDM-2.55

None.

HDM-2.54

None.

HDM-2.53

None.

HDM-2.52

None.

HDM-2.51

None.

HDM-2.48

HDM-2.48 added support for the following hardware options on the S2703 G5 or S4703 G5:

HBA-LSI-9500-16e storage controller

GPU-A30-24G GPU module

NIC-ETH-MCX623435MN-CDAB-1P network adapter

NIC-ETH-MCX623105AN-CDAT-1P network adapter

HDM-2.47

HDM-2.47 added support for the following hardware:

RD-4NVMe-G5 Redriver riser card on the R4900 G5.

2SFF Unibay drive backplane on the S2703 G5 or S4703 G5.

HDM-2.43

None.

HDM-2.42

None.

HDM-2.41

None.

HDM-2.40

None.

HDM-2.32

None.

HDM-2.31

None.

HDM-2.29

None.

HDM-2.27

None.

HDM-2.25

None.

HDM-2.24

None.

HDM-2.23

HDM-2.23 added support for the following hardware on the R5500 G5 AMD:

A100-SXM4-80GB GPU module.

HDM-2.18.12

None.

HDM-2.18

None.

HDM-2.17

None.

HDM-2.16.31

None.

HDM-2.16

None.

HDM-2.13

None.

HDM-2.09.00

None.

HDM-2.07.00

First release.

Software feature and command upgrades

For information about command changes, see H3C HDM IPMI Basics Command Reference and H3C HDM Redfish API Reference.

HDM-3.38.01

New feature:

Added the device SN QR code to the HDM remote support page.

HDM-3.38.01

None.

HDM-3.38

None.

HDM-3.37.01

None.

HDM-3.37

None.

HDM-3.36.01

None.

HDM-3.36

None.

HDM-3.35.11

None.

HDM-3.35.01

None.

HDM-3.35

None.

HDM-3.34.02

None.

HDM-3.34.01

None.

HDM-3.34

New feature:

Added support for specifying group address & characters when selecting email addresses for SMTP.

HDM-3.33

New feature:

Added support for exporting only event logs through Redfish.

HDM-3.32

None.

HDM-3.31

New feature:

Added the remote support function and maintenance information display on the HDM remote service page.

Added a QR code for users to scan the code and view fault information and recommended actions.

Added support for HD mounting through Redfish.

HDM-3.30

None.

HDM-3.27

None.

HDM-3.26

None.

HDM-3.22

None.

HDM-3.21

None.

HDM-3.18

New feature:

Added support of alarm severity differentiation for Syslog reporting.

HDM-3.16

None.

HDM-3.13

None.

HDM-3.11

None.

HDM-3.10.21

None.

HDM-3.10

None.

HDM-2.99

None.

HDM-2.98

None.

HDM-2.97.03

None.

HDM-2.97.02

None.

HDM-2. 97

This version added support for updating PANGO STBCPLD firmware from the HDM Web interface.

Redfish supports enabling or disabling the HDM shared port.

HDM-2.95.05

None.

HDM-2.95

None.

HDM-2.93

None.

HDM-2.92

This version added support for updating PANGO BPCPLD firmware from the HDM Web interface.

HDM-2.91

None.

HDM-2.87

This version added support for updating PANGO CPLD firmware from the HDM Web interface.

HDM-2.86

This version added support for configuring hot spares. When an LSI or PMC storage controller is installed, you can configure the hot spare status for physical drives managed by the storage controller from the HDM interface.

HDM-2.81

None.

HDM-2.80

None.

HDM-2.78

None.

HDM-2.76

None.

HDM-2.73

None.

HDM-2.70

None.

HDM-2.64

None.

HDM-2.63

None.

HDM-2.60

This version added support for domestic PHY chips for HDM dedicated port.

HDM-2.59

None.

HDM-2.58

None.

HDM-2.57

This version added support for the following features:

GPU power capping on the R5500 G5. You can configure this feature to limit the GPU power.

Syslog reporting. You can configure this feature to report alarm log, sensor log, and serial port log to the target server.

FANMCU firmware upgrade on the R5500 G5. You can configure this feature to upgrade the Micro Control Unit (MCU) of a fan.

Updating storage controller, network adapter, and drive firmware through REPO.

SSH password-free login. You can configure this feature to enable users to log in to HDM CLI through SSH.

This version modified the following features:

Users can modify the names of custom user groups.

HDM-2.48

This version added support for the following features:

Displaying information about RAID-P4408-Ma-8i-2GB storage controller on the blade server.

AMD iHDT. You can use Hardware Debug Tool (HDT) client for debugging.

Updating the FPGA firmware of Redstone GPU module on the 5300 G5.

Service USB devices. You can use service USB devices to download SDS log.

Two-factor authentication. After you enable two-factor authentication, a user must provide the following information before logging in to HDM:

Username and static password.

Dynamic password on the phone token or hardware token.

This version modified the following features:

Simplified KVM feature. KVM supports two modes, and H5 KVM supports four modes. All the modes are displayed in the remote console page, which is hard to select. To resolve this issue, the simplified KVM feature sets the default boot mode for KVM and H5 KVM. Users can also modify the default boot mode.

Importing configuration. HDM will restart only when the imported configuration file contains network configuration information.

HDM-2.43

None.

HDM-2.41

None.

HDM-2.32

None.

HDM-2.24

First release.

MIB upgrades

For more information, see H3C Server SNMP Agent MIB Reference.

IPMI changes

For more information, see H3C HDM IPMI Basics Command Reference.

Redfish changes

For more information, see H3C HDM Redfish API Reference.

Operation changes

None.

Restrictions and cautions

Restrictions

If no media images are mounted, the KVM window automatically closes when the HDM Web session times out.

Each browser can establish only one session with HDM. If you attempt to establish two concurrent sessions from the same browser with different usernames, the first session will automatically end when the second session is established.

Guidelines

This version is available for all supported servers in this document.

Make sure pop-ups are allowed on the browser.

Open problems and workarounds

None.

List of resolved problems

Resolved problems in HDM-3.39

202307180160

Symptom: Ucenter reports Unknown state of logical drives when the R4900 G3 is installed with LSI RAID controllers.

Condition: This symptom might occur when the R4900 G3 is installed with LSI RAID controllers.

202307141581

Symptom: The physical view tab of the storage management page displays additional drive presence information when the R4900 G3 uses the 24 NVMe drive configuration.

Condition: This symptom might occur when the R4900 G3 uses the 24 NVMe drive configuration.

202307120329

Symptom: When the R4300 G5 is installed with drives of multiple types, it takes a long time for SNMP WALK to obtain drive information.

Condition: This symptom might occur when the R4300 G5 is installed with drives of multiple types.

202308070270

Symptom: When a G3/G5 server is installed with two LSI HBA modules, such as 9500-8i+ 9300-8i, the system reports Drive Fault alarms mistakenly.

Condition: This symptom might occur when a G3/G5 server is installed with two LSI HBA modules, such as 9500-8i+ 9300-8i.

202307240022

Symptom: When the R5500K installed with an OCP network restarts after a stress test, the system reports OCP overtemperature alarms in bulk.

Condition: This symptom might occur if you install an OCP network adapter on the R5500K, perform a stress test, and restart the DC power.

202307192176

Symptom: Heat dissipation issues occur on the R5500 G5 installed with a 332A network adapter.

Condition: This symptom might occur on the R5500 G5 when a 332A intelligent network adapter is installed and the system enters FAKE S5.

Resolved problems in HDM-3.38.01

202307180160

Symptom: UCenter reports that logical drives are in Unknown state on an R4900 G3 installed with an LSI RAID controller.

Condition: This symptom might occur on an R4900 G3 installed with an LSI RAID controller.

202307141581

Symptom: The physical view of the storage management page displays extra drive presence information for an R4900 G3 with the 24 NVMe drive configuration.

Condition: This symptom might occur on an R4900 G3 with the 24 NVMe drive configuration.

202307120329

Symptom: It takes a long time for SNMP WALK to obtain drive information for an R4300 G5 installed with multiple drives.

Condition: This symptom might occur on an R4300 G5 installed with multiple drives.

202308070270

Symptom: The system reports Drive Fault alarms mistakenly if the G3 or G5 device is installed with two LSI HBA modules, such as 9500-8i and 9300-8i.

Condition: This symptom might occur if the G3 or G5 device is installed with two LSI HBA modules, such as 9500-8i and 9300-8i.

202307240022

Symptom: The system reports OCP overtemperature alarms in bulk after you perform stress tests on an R5500K installed with OCP network adapters and restart the server.

Condition: This symptom might occur after you perform stress tests on an R5500K installed with OCP network adapters and then perform DC restart.

202307192176

Symptom: Heat dissipation issues occur on an R5500 G5 installed with 332A network adapters.

Condition: This symptom might occur if the system enters FAKE S5 on an R5500 G5 installed with 332A network adapters.

Resolved problems in HDM-3.38

202306062143

Symptom: When the MCTP channel is enabled on the R4900 G5 server installed with the QLE2692 card, the fans intermittently produce loud noises.

Condition: This symptom might occur if the MCTP channel is enabled on the R4900 G5 server installed with the QLE2692 card.

202306051211

Symptom: The HDM usage might be too high on the R5500 G5 Intel server.

Condition: This symptom might occur if HDM is upgraded or restarted, or the configuration is imported or exported.

202306190034

Symptom: On the R4930 G5 H3 server installed with high-performance dual-rotor fans, if one rotor of a fan fails, an event log message is generated, but the fan can still operate correctly.

Condition: This symptom might occur if one rotor of a high-performance dual-rotor fan on the R4930 G5 H3 server fails.

Resolved problems in HDM-3.37.01

202306200181

Symptom: The fan speed might exceed 90% of the maximum when the R4300 G5 server is installed with the 9300 storage controller.

Condition: This symptom might occur if the R4300 G5 server is installed with the 9300 storage controller.

Resolved problems in HDM-3.37

202306240148

Symptom: When a PMC storage controller is installed on a 4GPU riser card on the R4900 G5, the storage page does not display information about the PMC storage controller.

Condition: This symptom occurs if a PMC storage controller is installed in PCIe slot 3 on a 4GPU riser card on the R4900 G5.

202306020382

Symptom: The G5 Intel servers added support for alarms on DIMMs that are not certificated.

Condition: This symptom occurs if DIMMs that are not certificated by H3C are installed on the G5 Intel servers.

202304141908

Symptom: HDM mistakenly reports supercapacitor errors when a P460 M2 storage controller on the R4900 G3 is not connected to a supercapacitor.

Condition: This symptom occurs if a P460 M2 storage controller on the R4900 G3 is not connected to a supercapacitor.

202302231383

Symptom: HDM mistakenly reports drive loss errors when the R4300 G5 is installed with a 24LFF drive backplane.

Condition: This symptom might occur if the R4300 G5 is installed with a 24LFF drive backplane.

202305221785

Symptom: The models of some drives displayed on HDM are not consistent with the actual models when the R4900 G5 is installed with an LSI storage controller.

Condition: This symptom occurs if the R4300 G5 is installed with an LSI storage controller.

202306061251

Symptom: HDM mistakenly report storage controller battery errors when the R4900 G3 installed with the LSI 9460 and LSI 9361 storage controllers.

Condition: This symptom might occur if the R4900 G3 with the LSI 9460 and LSI 9361 storage controllers.

202306062011

Symptom: The A800 Delta GPU module does not support module exception detection.

Condition: This symptom occurs if a GPU module becomes abnormal.

202305080192

Symptom: When the R4930 G5 H3 is installed with the LSI 9400 storage controller and D6456 SSD (AIC), HDM might fail to display PCIe device information correctly after the server starts up.

Condition: This symptom might occur if the LSI 9400 storage controller and D6456 SSD (AIC).

202306191260

Symptom: The recommended action for the bus fatal error that occurs when the Retimer card and the PM9A3 drive are connected on the R4900 G3 needs to be modified.

Condition: This symptom might occur if the bus fatal error is reported when the Retimer card and the PM9A3 drive are connected on the R4900 G3.

202306020141

Symptom: The message in the response body is misspelled when you create a logical drive on the R4900 G5 through Redfish successfully.

Condition: This symptom might occur if a logical driver is created through Redfish.

Resolved problems in HDM-3.36.01

202306020170

Symptom: HDM might report the Drive Fault error on drive slot 9 at the server front when the R4300 G3 is installed with the 0302A6MQ drive backplane.

Condition: This symptom might occur if the R4300 G3 is installed with 0302A6MQ drive backplane.

Resolved problems in HDM-3.36

202305061271

Symptom: On the R4900 G5 installed with an LSI storage controller, the system does not generate alarms when errors occur on the storage controller.

Condition: This symptom might occur if you install an LSI storage controller on the R4900 G5.

202207020216

Symptom: G5 servers cannot distinguish memory disabled out of errors and memory disabled by POR rules.

Condition: This symptom occurs because G5 servers cannot distinguish memory disabling reasons. You can view the reasons on the memory page as from this release.

202304190418

Symptom: After you add DIMMs to the R4900 G5, the server displays that the DIMMs are not certificated.

Condition: This symptom might occur after you add DIMMs to the R4900 G5.

202304140556

Symptom: The R6900 G5 server has a loud fan noise and abnormal fan speed control.

Condition: This symptom might occur on the R6900 G5 server when the CPU temperature fluctuates significantly during operation.

202305120122

Symptom: After you configure HDM VNC connection, sliding the scroll wheel triggers a right-click.

Condition: This symptom might occur after you configure HDM VNC connection.

202305130354

Symptom: When an IF BANK error occurs on the R4950 G5 Milan, the type of the error is displayed as Unknown on HDM.

Condition: This symptom occurs if an IF BANK error occurs on the R4950 G5 Milan.

Resolved problems in HDM-3.35.11

202303260045

Symptom: The system displays duplicate SNs if the R4900 G5 is equipped with multiple R200 GPUs.

Condition: This symptom might occur if the R4900 G5 is equipped with multiple R200 GPUs.

Resolved problems in HDM-3.35.01

202304271897

Symptom: After the HDM is upgraded from 3.13 to the new version for the R4300 G3, false reporting of drive fault&disk missing errors occur on a large number of devices.

Condition: This symptom might occur if an LSI controller is installed on the R4300 G3 and multiple drives are attached to the LSI controller.

Resolved problems in HDM-3.35

202207060543

Symptom: Blade devices fail to use Redfish interfaces to obtain shared port information and a stack overflow error occurs.

Condition: This symptom might occur if a powered-off blade server attempts to obtain shared port information before PCIe information is obtained.

Resolved problems in HDM-3.34.02

202303171913

Symptom: A drive configuration alarm is generated if you use the 25SFF+4SFF configuration on an R4900 G5 server.

Condition: This symptom might occur if you use the 25SFF+4SFF configuration on an R4900 G5 server.

Resolved problems in HDM-3.34.01

202303291487

Symptom: HDM cannot display link state information for ports on a 560F network adapter after HDM is upgraded to version 3.33.

Condition: This symptom might occur if 560 network adapters are used in HDM version 3.33.

Resolved problems in HDM-3.34

202302130075

Symptom: When you use FIST to manage the server, the system prompts "Error: Unable to establish IPMI v2 / RMCP+ session" after sending an IPMI command.

Condition: This symptom might occur if HDM communication timeout occurs because HDM is busy and the HDM management network port is disconnected and then reconnected immediately.

Resolved problems in HDM-3.33

202211101430

Symptom: On the R5500 G5, if a single Delta module loses power, HDM cannot correctly display the slot of the faulty GPU.

Condition: This symptom might occur if a GPU fails or is removed.

202212280182

Symptom: The BIOS restarts once every 15 minutes because of BIOS watchdog timeout.

Condition: This symptom might occur after you enable IPMI command firewall.

202212290856

Symptom: The Redfish service does not respond to event log query requests triggered by Redfish commands. After you restart HDM, the system recovers.

Condition: This symptom might occur if you use Redfish commands to query server event logs.

Resolved problems in HDM-3.32

202212010817

Symptom: On the R4950 G5, CPU power supply errors might occur, triggering the system board to generate the "Transition to Non-Recoverable from less severe---System detected a power supply failure on Motherboard(P1_VDDCR_CPU)" critical alarm. The server cannot start up correctly.

Condition: This symptom might occur if you power off the server (AC power supply) and then power on the server again.

Resolved problems in HDM-3.31

202210310602

Symptom: After the server restarts, HDM mistakenly reports Drive Fault and Disk is missing errors on all physical drives managed by an HBA-LSI-9400 storage controller.

Condition: This symptom might occur if you restart the server that is installed with two LSI storage controllers, one of which is HBA-LSI-9400.

202212010962

Symptom: On a server installed with one or multiple storage controllers and a drive backplane without an expander chip, if you restart the server to resolve the storage controller identification failure issue, the system can identify the storage controller but Drive Fault and Disk is missing errors are triggered mistakenly.

Condition: This symptom might occur if you restart the server to resolve the storage controller identification failure issue on a server installed with one or multiple storage controllers and a drive backplane without an expander chip.

Resolved problems in HDM-3.30

202211050679

Symptom: A driver fault error alarm might occur on all 8SFF UniBay drives during cold reboot of an R6900 G5 server.

Condition: This symptom might occur if 25 SFF drives are connected to a drive backplane other than the 25SFF UniBay drive backplane on an R6900 G5 server.

202211141099

Symptom: The Transition to Non-recoverable from less severe---System detected a power supply failure onCMOD2 alarm log is generated during the reboot of the R8900 G3 server.

Condition: This symptom might occur if an R8900 G3 server reboots with the G3-RS3M9PWF-1200W AC power supplies as the power source.

202210310497

Symptom: The event logs and event recovery logs are not consistent on HDM for an R4900 G3 server, which causes Huawei eSight not to clear the event logs.

Condition: This symptom might occur if the Bus Uncorrectable Error alarm log is generated.

202211050202

Symptom: HDM reports the battery event log BBU is Miss when an R4900 G3 server is installed with an LSI-9460-8i storage controller.

Condition: This symptom might occur if the firmware version of the LSI-9460-8i storage controller is not consistent with the storage controller driver version on the server.

202211050202

Symptom: The in critical array alarm occurs on physical drives if logical drive rebuilding is performed from HDM 3.10 for an R4900 G3 server.

Condition: This symptom might occur if logical rebuilding is performed from HDM of version 2.98 to 3.10.

202207151080

Symptom: HDM mistakenly reports Drive Fault and Disk is missing errors on the R4900 G3 server, and then automatically clears the errors.

Condition: This symptom might occur if multiple LSI storage controllers are installed.

Resolved problems in HDM-3.27

None.

Resolved problems in HDM-3.26

202207271501

Symptom: On the R4900 G3 server, the system indicates that IERR errors occur on the system board and memory module, which is unclear.

Condition: This symptom might occur if a DCU Poison error is triggered.

202210150091

Symptom: During the BIOS startup on the R4930 G5 H3 server, FRB2 watchdog alarms occur and the BIOS restarts. Services function correctly after the restart and the alarms are recorded in HDM event logs.

Condition: This symptom might occur on the R4930 G5 H3 server during the BIOS startup.

Resolved problems in HDM-3.22

202208161852

Symptom: After a hot restart of the R5500 G5 Intel server, HDM reports OCP module overtemperature alarms.

Condition: This symptom might occur after a hot restart of the R5500 G5 Intel server.

202209081687

Symptom: If a 957508-P1200 Broadcom network adapter is installed on the R5500 G5 Intel server, the negotiated network adapter rate is displayed incorrectly on the HDM Web interface.

Condition: This symptom might occur if a 957508-P1200 network adapter is installed on the R5500 G5 Intel server.

Resolved problems in HDM-3.21

202209071069

Symptom: When an Enflame 32G EF-T20 GPU or 16G EF-I10 GPU is installed on the R5300 G5 server, HDM reports GPU overtemperature alarms during GPU stress tests.

Condition: This symptom might occur if an Enflame 32G EF-T20 GPU or 16G EF-I10 GPU is installed on the R5300 G5 server.

Resolved problems in HDM-3.18

202208040359

Symptom: The drive LED turns amber during server operation if a 12LFF drive backplane is installed at the front of an R4900 G3.

Condition: This symptom might occur if a drive backplane with Expander is installed at the front of an R4900 G3.

Resolved problems in HDM-3.16

202208101823

Symptom: HDM might report Drive Fault errors mistakenly if a 24LFF drive backplane is installed at the front on an R4300 G3 server.

Condition: This symptom might occur if a 24LFF drive backplane is installed at the front on an R4300 G3 server.

202206010719

Symptom: Abnormal fan noise appears if you bring up and then shut down the shared network port on a server repeatedly.

Condition: This symptom might occur if you bring up and then shut down the shared network port on a server repeatedly.

202207290307

Symptom: The HDM storage page does not display upgraded logical drive information for RAID array configuration and drive removal operations on an R4900 G5.

Condition: This symptom might occur if you change the boot mode from UEFI to Legacy and restart the BIOS to access Legacy setup.

202208091382

Symptom: Event log reporting is triggered frequently when an R4900 G3 server is powered on, and the test.csv file might stop recording SEL logs.

Condition: This symptom might occur if event log reporting is triggered frequently when an R4900 G3 server is powered on.

202207211044

Symptom: CE injection tests on an R4950 G5 causes OS crash and HDM restart.

Condition: This symptom might occur if you perform CE injection tests on an R4950 G5.

202207230300

Symptom: You cannot log in to HDM for an R4900 G3 server.

Condition: This symptom might occur a period of time after FIST manages an R4900 G3 server when the server is powered off.

Resolved problems in HDM-3.13

202207071846

Symptom: HDM might report a GPU overtemperature event when the fan speed mode is set to Optimal cooling by default on the R5500 G5 Intel/AMD server and heavy-loaded services are running.

Condition: This symptom might occur if the fan speed mode is set to Optimal cooling by default on the R5500 G5 Intel/AMD server and heavy-loaded services are running.

202207010971

Symptom: SDS logs might fail to be downloaded after the server has been operating for a period of time, and HDM indicates no SDS logs exists for the specified time range.

Condition: This symptom might occur if the server has been operating for a period of time.

202206140565

Symptom: A slow HTTP DoS attack is detected on HDM.

Condition: None.

202207151080

Symptom: HDM might mistakenly report drive fault or disk missing alarms when an LSI storage controller is installed. The slots of drives that generate these alarms are not fixed, and the alarms are triggered and cleared multiple times.

Condition: This symptom might occur if an LSI storage controller is installed.

202205210677

Symptom: HDM might fail to be connected when the VLAN service is enabled from HDM, but the length declared in the packet header of a received RMCP packet is inconsistent with the actual length.

Condition: None.

202206150423

Symptom: For the R8900 G3 server, the maximum power value recorded in the history power trend graph exceeds the upper limit of the normal power range of the server.

Condition: None.

202206280527

Symptom: When the network connectivity is poor, the system might prompt that the current user does not have the upgrade permission when the user attempts to upgrade firmware from the Web interface.

Condition: This symptom might occur when the network connectivity is poor and a user attempts to upgrade firmware from the Web interface.

202112140466

Symptom: Vulnerabilities CVE-2021-41617 and CVE-2016-20012 were detected.

Condition: CVE-2021-41617 exists in OpenSSH allowing privilege escalation because supplemental groups are not initialized as expected. CVE-2016-20012 exists in OpenSSH of version earlier than 8.7, allowing remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session.

Resolved problems in HDM-3.12

None.

Resolved problems in HDM-3.11

202206080347

Symptom: No GPU is installed on the R5300 G5 server and fans rotate at nearly-full speed.

Condition: This symptom might occur if no GPU is installed on the R5300 G5 server.

202205261044

Symptom: HDM might generate an event log message Exceeded the upper minor threshold when power consumption on the R5500 G5 Intel server is high.

Condition: This symptom might occur if power consumption is high on the R5500 G5 Intel server.

202206100167

Symptom: For a B5700 G5 node is installed in a B16000 enclosure, the fans in the B5700 G5 node operate at a relatively high speed when the ambient temperature is normal. The fan speed mode for the B5700 G5 node needs to be optimized.

Condition: This symptom might occur if the fans on a B5700 G5 node installed in a B16000 enclosure operate at a relatively high speed when the ambient temperature is normal.

202206140546

Symptom: Failed to log in to the HDM Web interface when a monitor platform accessed HDM over WSMAN.

Condition: This symptom might occur if a monitor platform accesses HDM.

202206140590

Symptom: After the Intel BIOS is upgraded with the Forced restore option, the server imports HDM configuration with power capping disabled. However, power capping is enabled after you power cycle the server with the power cords reconnected or restart HDM during the initialization phase of system restart.

Condition: This symptom might occur if you perform the following operations:

a.Upgrade the Intel BIOS with the Forced restore option, and then imports HDM configuration with power capping disabled.

b.Power cycle the server with the power cords reconnected or restart HDM during the initialization phase of system restart.

202206140619

Symptom: The configuration specifications for IPMI commands to configure BIOS hyper-threading on the R4900 G5 server are inconsistent with those on G3 servers.

Condition: This symptom might occur if you configure BIOS hyper-threading settings by using IPMI commands on the R4900 G5 server.

202206140592

Symptom: HDM does not display NVMe drive information on the R4900 G5 server.

Condition: This symptom might occur if the R4900 G5 server is installed with 12LFF drive backplane, 8*SATA/SAS+4*UniBay (SATA/SAS/NVMe) (0302A5DA), and NVMe drives are connected to SlimSAS connectors on the system board.

Resolved problems in HDM-3.10.21

202206110180

Symptom: A GPU overtemperature event might be reported by HDM during operation of heavy-load services when fans on the R5500 G5 Intel/AMD server are operating in Optimal cooling mode.

Condition: This symptom might occur if fans on the R5500 G5 Intel/AMD server are operating in Optimal cooling mode and heavy-load services are running.

Resolved problems in HDM-3.10

202205101609

Symptom: HDM mistakenly generates an event log message Board found PSU output can't be enabled.

Condition: This symptom might occur if an R4950 G5 server is installed with two power supplies and you remove and re-install the power supplies in turn when the server is powered on.

202205060378

Symptom: Information of an NVMe drive is displayed in different slots on the Storage menu of HDM.

Condition: This symptom might occur if an R4950 G5 server is installed with Hygon H2 5xxx series processors and NVMe drives at the server rear.

202205061496

Symptom: When an Uncorrected Error (UCE) occurred on a server installed with Intel CPUs, HDM health log does not displays the error type, which might be Fatal, Recoverable, or Correct.

Condition: This symptom might occur if an Uncorrected Error (UCE) occurred on a server installed with Intel CPUs.

202204060513

Symptom: When a server is powered on, the server status obtained through IPMI indicates that the server is powered off.

Condition: This symptom might occur if you use IPMI commands to obtain the server status when the server is powered on.

Resolved problems in HDM-2.99

202204090320

Symptom: The error type reported in the HDM system health log does not indicate whether an Uncorrected Error (UCE) occurred on R4900 G3 server is recoverable.

Condition: This symptom might occur if an UCE occurs on an R4900 G3 server.

Resolved problems in HDM-2.98

202203050362

Symptom: HDM cannot detect LS-HWA faults that occur during operation or report alarms when Milan CPUs are installed on an R4950 G5 server.

Condition: This symptom might occur if LS-HWA faults occur during the operation of a Milan CPU installed on an R4950 G5 server.

202201210384

Symptom: HDM cannot detect a system board hardware error or report an alarm even if the error causes temporary power output failure on an R4950 G5 server.

Condition: This symptom might occur if a system board hardware error causes temporary power output failure on an R4950 G5 server.

Resolved problems in HDM-2.97.03

None.

Resolved problems in HDM-2.97.02

202202280580

Symptom: HDM reports drive failure SEL logs mistakenly at HDM or OS restarts if the server is installed with an LSI storage controller or LSI 9311 HBA and a large number of logical drives (over 25) are created. The alarms are cleared automatically after a period of time.

Condition: This symptom might occur at HDM or OS restarts if the server is installed with an LSI storage controller or LSI 9311 HBA and a large number of logical drives (over 25) are created.

Resolved problems in HDM-2.97

202202141100

Symptom: HDM cannot identify the H3C-proprietary network adapter installed in the PCIe slot 25 on a R6900 G3 server. The network adapter cannot be displayed on the HDM Web interface.

Condition: This symptom might occur if an H3C-proprietary network adapter is installed in the PCIe slot 25 on a R6900 G3 server.

202202151210

Symptom: If the PPIN of an installed processor starts with 00, HDM displays N/A in the PPIN field.

Condition: This symptom might occur if the PPIN of an installed processor starts with 00.

202112170659

Symptom: HDM can still detect the presence of a DIMM on an H3C G3 server even if the DIMM is disabled and isolated by the BIOS.

Condition: This symptom might occur on an H3C G3 server if a DIMM is disabled and isolated by the BIOS.

Resolved problems in HDM-2.95.05

None.

Resolved problems in HDM-2.95

None.

Resolved problems in HDM-2.93

202112241261

Symptom: HDM does not report an event log when a PMC storage controller installed on an R4300/R4900/R6700 G3 server operates incorrectly.

Condition: This symptom might occur if a PMC storage controller installed on an R4300/R4900/R6700 G3 server operates incorrectly.

202112280415

Symptom: For an R4900 G3/R5300 G3/R5300 G5/R5500 G5 AMD/R5500 G5 Intel server installed with a GPU that supports NVLINK detection, HDM reports an event log about an NVLINK CRC error.

Condition: This symptom might occur if an R4900 G3/R5300 G3/R5300 G5/R5500 G5 AMD/R5500 G5 Intel server is configured with a GPU that supports NVLINK detection.

202201051030

Symptom: For an R5300 G3 server installed with a GPU adapter that supports 8 GPUs, the DrMOS burnt issue occurs for the VR power supply on the adapter.

Condition: This symptom might occur if an R5300 G3 server is configured with a GPU adapter that supports 8 GPUs.

Resolved problems in HDM-2.92

None.

Resolved problems in HDM-2.91

202110150155

Symptom: Added a field to Test packets for SNMP trap to indicate the Info alarm level.

Condition: None.

202109090447

Symptom: The (recommended) string was removed from the Event mode field on the Remote O&M > Alarm Settings > SNMP trap page.

Condition: None.

202109140123

Symptom: Trap packets of SNMPv2 or SNMPv3 carry trap OIDs.

Condition: This symptom might occur when SNMPv2 or SNMPv3 trap is used.

202112131150

Symptom: When an alarm is triggered, the HDM client and the email server establish a TCP connection, and the email server sends the first packet 5 seconds later, causing session timeout on the HDM client. The client sends a FIN packet and email sending fails.

Condition: This symptom might occur because the email server sends the first packet 5 seconds later after a TCP connection is established.

202110200521

Symptom: The health status page does not display alarms for fan redundancy loss, power redundancy loss, or memory isolation events.

Condition: This symptom might occur when a fan redundancy loss, power redundancy loss, or memory isolation event occurs.

202111250333

Symptom: With a MCX512A-ACAT or NIC-MCX4121A-F-B-25Gb-2P network adapter installed, HDM cannot obtain or display the connection status of the network adapter.

Condition: This symptom might occur when a MCX512A-ACAT or NIC-MCX4121A-F-B-25Gb-2P network adapter is installed.

202112180531

Symptom: For an R4900 G5 server installed with four GPU_BAIDU_R200 modules, GPU firmware upgrade from the HDM Web interface fails.

Condition: This symptom might occur if an R4900 G5 is installed with four GPU_BAIDU_R200 modules.

Resolved problems in HDM-2.87

202109020462

Symptom: You cannot upgrade PANGO CPLD firmware from the HDM Web interface.

Condition: This symptom might occur if a PANGO CPLD is used.

Resolved problems in HDM-2.86

202111250465

Symptom: On an S4703/S2703 G5 configured with an NIC-ETH-MCX623436AN-CDAB-2P OCP network adapter, overtemperature alarms occur during operation.

Condition: This symptom might occur if an NIC-ETH-MCX623436AN-CDAB-2P OCP network adapter is installed on an S4703/S2703 G5 server.

202111121522

Symptom: On an R5300 G3 configured with an HBA-LSI-9311-8i-A1-X module, HDM cannot read storage controller and drive information during driver installation for the storage controller in the OS.

Condition: This symptom might occur during driver installation for a storage controller in the OS if the R5300 G3 is installed with an HBA-LSI-9311-8i-A1-X module.

202110141209

Symptom: With an NVIDIA GPU installed, the GPU part number displayed on the HDM PCIe module page is inconsistent with the part number obtained from the OS.

Condition: This symptom might occur if the server is installed with an NVIDIA GPU.

202111050263

Symptom: If you import the power capping disabling setting to a server enabled with power capping, the disabling operation might fail. Power capping is still enabled and system crush occurs after HDM restarts.

Condition: This symptom might occur if you import the power capping disabling setting to a server enabled with power capping.

Resolved problems in HDM-2.81

202109280480

Symptom: On a R4900 G3 configured with 8SFF SAS/SATA + 8SFF SAS/SATA + 8SFF NVMe drives at the front, if an NVMe SSD expander module is installed, NVMe drive numbers displayed on HDM are incorrect. HDM displays that NVMe drives are also present in Box3-3 while the drives only exist in Box3-0.

Condition: This symptom might occur if an NVMe SSD expander module is installed on a R4900 G3 configured with 8SFF SAS/SATA + 8SFF SAS/SATA + 8SFF NVMe drives at the front.

Resolved problems in HDM-2.80

202109280529

Symptom: HDM generates a CPU absence alarm and the health LED turns amber. However, the health LED is still amber after the alarm is removed.

Condition: This symptom might occur because CPU absence alarm removal is not associated with the HDM health system. The health state cannot be recovered even if the alarm is removed.

Resolved problems in HDM-2.78

None.

Resolved problems in HDM-2.76

202108251029

Symptom: If logic drives in RAID degrade and then recover, alarm trigger and removal logs generated during the process have incorrect time stamps.

Condition: This issue might occur after RAID setup.

202108300061

Symptom: When FRU information reading fails, the system displays that the BMC_Self_Test is in abnormal state, but no event logs related to the failure are reported.

Condition: This symptom might occur if FRU information reading fails.

202108300356

Symptom: You cannot select the product serial number as the alarm log host ID on the syslog settings page of HDM.

Condition: None.

202105130683

Symptom: If all the drives monitored by one temperature sensor are absent on a R6900 G3, the fan speed increases.

Condition: This symptom might occur if all the drives monitored by one temperature sensor are absent on a R6900 G3.

202108310746

Symptom: If the DUID is used to assign IP addresses to HDM, IPv6 address cannot be assigned in bonding mode unless HDM restarts. However, the assigned IPv6 address gets lost after you reconnect the network cable to the dedicated HDM network port.

Condition: This symptom might occur if you use the DUID to assign IP addresses to HDM.

Resolved problems in HDM-2.73

202108310737

Symptom: With a PMC storage controller installed, HDM generates Drive fault alarms when the server restarts.

Condition: This issue might occur at server restarts if a PMC storage controller is installed.

Resolved problems in HDM-2.70

202108040539

Symptom: The DIMM failure log generated on an R6900 G3 server during the POST phase does not display the slot number.

Condition: This symptom might occur when a DIMM failure occurs on an R6900 G3 server during the POST phase.

202107301491

Symptom: The LED of the rear 2LFF backplane drive on an X10529/X10529F G3 server cannot be turned on through IPMI.

Condition: This symptom might occur when you turn on the LED of the rear 2LFF backplane drive on an X10529/X10529F G3 server through IPMI.

202107280119

Symptom: The rotation speed of the fan on an R5500 G5 server becomes zero after the server restarts.

Condition: This symptom might occur when an R5500 G5 server restarts.

Resolved problems in HDM-2.64

202108070074

Symptom: HDM fails to obtain the temperature of a DCPMM(AEP) on a server.

Condition: This symptom might occur when the server is installed with a DCPMM(AEP).

Resolved problems in HDM-2.63

None.

Resolved problems in HDM-2.60

202107130260

Symptom: On the R4950 G5, HDM detects a PCIe error in a slot that is not installed with a PCIe device. The health LED is orange and flashing, but the health state displayed on HDM is normal.

Condition: This symptom might occur when HDM detects a PCIe error in a slot that is not installed with a PCIe device on the R4950 G5.

202105280659

Symptom: After you enable network adapter auto-adaptation mode in a Layer 3 network, the IPv6 static address of HDM cannot be accessed.

Condition: This symptom might occur when you enable network adapter auto-adaptation mode in a Layer 3 network.

202106100459

Symptom: Reporting failed when a user logs in to HDM, closes the webpage or removes the network cable, and uses IPMI commands to modify user information.

Condition: This symptom might occur when a user logs in to HDM, closes the webpage or removes the network cable, and uses IPMI commands to modify user information.

202106020728

Symptom: The drive reports slot information error when the device is installed with PMC storage controller and drive extended board.

Condition: This symptom might occur when the device is installed with PMC storage controller and drive extended board.

Resolved problems in HDM-2.59

None.

Resolved problems in HDM-2.58

202107070060

Symptom: After you configure RAID settings for all drives on an X10536 G3 server installed with RAID-LSI-9460-8i (4G) in the operating system, the operating system displays that all drives are in online state, while HDM displays that all drives are in Unconfigured Good state.

Condition: This symptom might occur when you configure RAID settings for all drives on an X10536 G3 server installed with RAID-LSI-9460-8i (4G) in the operating system.

Resolved problems in HDM-2.57

202106300095

Symptom: The minor alarm log BMC read fru failed occurs on HDM.

Condition: This symptom might occur if you install a NIC-ETH-X2522-25Gb-2P network adapter on the server.

202105070592

Symptom: After logging in to HDM, you cannot view operation logs or download SDS logs until you power cycle the server.

Condition: This symptom might occur when the device is installed with Emmc Flash MTFC4GACAJCN-1M WT, and the Emmc Flash internal controller is abnormal.

202106280595

Symptom: An overtemperature alarm is generated for PSU1 on an R4300 G3 server during the device test.

Condition: This symptom might occur when the following conditions exist:

The temperature of the device test environment is high, and the air temperature of the device air inlet is in the range of 28 °C to 33 °C.

Riser card 1 on the R4300 G3 server is configured with three PCIe network adapters, and the network adapters have a poor heat dissipation performance.

202106260480

Symptom: HDM fails to obtain information about all NVMe drives on an R4700 G3/R2700 G3 server.

Condition: This symptom might occur when an R4700 G3/R2700 G3 server is installed with an RS33RDN4P-4-port NVMe SSD expander module.

202106281095

Symptom: System event log Battery failed is generated when the device is installed with a PMC storage controller but is not installed with a supercapacitor.

Condition: This symptom might occur when the device is installed with a PMC storage controller but is not installed with a supercapacitor.

202106190187

Symptom: HDM fails to obtain the temperature of HBA-1000-M2-1.

Condition: This symptom might occur when the device is installed with HBA-1000-M2-1.

202106070654

Symptom: The backup firmware image fails to be upgraded when you upgrade HDM by using the REPO package.

Condition: This symptom might occur when you upgrade HDM by using the REPO package.

202106180720

Symptom: Added support for configuring and obtaining CPU turbo frequency.

Condition: None.

202106180720

Symptom: Added support for importing and exporting AD configuration.

Condition: None.

Resolved problems in HDM-2.55

202105210754

Symptom: The temperature sensor page cannot display temperature information about the CPU1 VR and CPU2 VR sensors on the X10828 G5 server.

Condition: This symptom might occur if you log in to HDM temperature sensor page to view the temperature of the X10828 G5 server.

Resolved problems in HDM-2.54

202105160074

Symptom: The sensor for the DCPMMs (BPS) on the B5700 G5 server becomes unavailable after you restart the server.

Condition: This symptom might occur if the B5700 G5 server is installed with DCPMMs (BPS).

202105180385

Symptom: Security vulnerability CVE-2021-28041 exists in OpenSSH before 8.5, which allows unconstrained agent-socket access on a legacy operating system.

Condition: None.

202105180351

Symptom: Security vulnerability CVE-2020-14145 exists in OpenSSH 5.7 through 8.3, which can cause information leakage. Attackers can exploit the vulnerability to obtain information.

Condition: None.

202105180388

Symptom: Security vulnerability CVE-2021-27097 exists in U-Boot before 2021.04-rc2. The vulnerability stems from mishandling of a modified FIT by the boot loader.

Condition: None.

202105180392

Symptom: Security vulnerability CVE-2021-27138 exists in Das U-Boot before 2021.04-rc2. The vulnerability stems from mishandling of unit address use by the boot loader.

Condition: None.

Resolved problems in HDM-2.53

202105211001

Symptom: The sensors System, ACPI State, and Button are displayed as sensor PSU5_Fan_Staus on the event log.

Condition: This symptom might occur if you power on the R5500 G5 Intel server.

202105280575

Symptom: An alarm about the Watchdog 2 sensor occurs.

Condition: This symptom might occur if you start the pressure test on the R5500 G5 Intel server.

Resolved problems in HDM-2.52

202105071152

Symptom: The log about the processor errors reported by the Redfish interface is inaccurate.

Condition: This symptom might occur if you install two processors of different models on the R5300 G3 server.

Resolved problems in HDM-2.51

202104132214

Symptom: The driver fault log occurs on HDM.

Condition: This symptom might occur if you install an 8SFF drive backplane on the R5500 G5 Intel server and issue an IPMI command to restore the factory configuration.

202104160866

Symptom: Encryption vulnerability CVE-2021-23839 exists in OpenSSL 1.0.2. This vulnerability stems from version rollback attack check performed during RSA signature unpadding.

Condition: None.

202104160876

Symptom: Input verification error vulnerability CVE-2021-23840 exists in OpenSSL, which can be exploited by attackers to cause program misoperation or crash.

Condition: None.

202104160935

Symptom: Input verification error vulnerability CVE-2021-23841 exists in OpenSSL public API. The vulnerability stems from errors that might occur when the X509_issuer_and_serial_hash function fails to parse the issuer field.

Condition: None.

Resolved problems in HDM-2.48

202103030059

Symptom: JBOD storage nodes fail to power off after you power off the server in HDM.

Condition: This symptom might occur if you connect JBOD storage nodes to the S2703 G5 or S4703 G5 server.

Resolved problems in HDM-2.47

None.

Resolved problems in HDM-2.43

202104131588

Symptom: The disabled DNS service becomes enabled after the host name is modified through the HDM Redfish API.

Condition: This symptom occurs if you use HDM Redfish API to modify the host name when the DNS service is disabled.

202104191314

Symptom: The HDM Redfish API fails to obtain the new host name after the host name is modified through the HDM Redfish API.

Condition: This symptom occurs if you use the HDM Redfish API to modify the host name.

Resolved problems in HDM-2.42

None.

Resolved problems in HDM-2.41

202104091411

Symptom: For HDM SMTP settings, the username used for connecting to the SMTP server cannot contain dots (.).

Condition: This symptom occurs when you configure SMTP settings from HDM.

Resolved problems in HDM-2.40

202104011179

Symptom: The ME_Sts sensor on the S2703 G5 or S4703 G5 server generates alarm logs after you run a power cycle stress test on the server.

Condition: This symptom might occur if you run a power cycle stress test on an S2703 G5 or S4703 G5 server.

Resolved problems in HDM-2.32

202103180439

Symptom: Added support for disabling the IPMI access service.

Condition: None.

202103220244

Symptom: On an R5500 G5 AMD server, you cannot execute IPMI commands in the OS to change the password of an HDM user.

Condition: This symptom might occur if you execute IPMI commands to change the password of an HDM user in the OS of an R5500 G5 AMD server.

202103021586

Symptom: On an R5500 G5 AMD server, the OS does not support updating the FPGA or CE firmware for DELTA GPU modules.

Condition: None.

Resolved problems in HDM-2.31

202103151548

Symptom: The DIMMG0_Temp temperature sensor on the S2703 or S4703 G5 server becomes unavailable after you restart the server.

Condition: This symptom might occur if the S2703 G5 or S4703 G5 server is installed with DCPMMs (BPS).

Resolved problems in HDM-2.29

202101052027

Symptom: Encryption vulnerability CVE-2018-0737 exists in RSA key generation algorithm in OpenSSL 1.1.0 through 1.1.0h and 1.0.2b through 1.0.2o. The vulnerability stems from incorrect use of key algorithms by network systems or products and can cause incorrect encryption, weak encryption, or even plaintext storage of sensitive information.

Condition: None.

202101052133

Symptom: Security vulnerability CVE-2020-1971 exists in OpenSSL 1.1.1 and 1.0.2. Null pointer dereference and system crash may occur, leading to a possible denial of service attack.

Condition: None.

202101052090

Symptom: Security vulnerability CVE-2019-1547 exists in OpenSSL 1.0.2 through 1.0.2s, 1.1.0 through 1.1.0k, and 1.1.1 through 1.1.1c. Attackers might exploit the vulnerability to obtain sensitive information.

Condition: None.

202101052032

Symptom: Encryption vulnerability CVE-2018-0734 exists in DSA signature algorithms in OpenSSL 1.1.1, 1.1.0 through 1.1.0i, and 1.0.2 through 1.0.2p. The vulnerability stems from incorrect use of key algorithms by network systems or products and can cause incorrect encryption, weak encryption, or even plaintext storage of sensitive information.

Condition: None.

Resolved problems in HDM-2.27

202101261374

Symptom: A memory leak occurs.

Condition: This symptom might occur if you start the pressure test on the server.

202101052128

Symptom: Security vulnerability CVE-2020-29371 exists in the Linux kernel before 5.8.4. This vulnerability stems from an error occurred during fs romfs store .c reading from romfs dev and might cause uninitialized memory leaks to userspace.

Condition: None.

Resolved problems in HDM-2.25

202011190001

Symptom: The information about the PMC P4408 storage controller is not displayed on HDM.

Condition: This symptom might occur if the B7800 G3 server is installed with a PMC P4408 storage controller.

Resolved problems in HDM-2.24

202012091682

Symptom: HDM prompts an import failure when you attempt to import HDM configuration on the Remote O&M > Manage Configuration page.

Condition: None.

202012160379

Symptom: HDM prompts an error when you attempt to add a new blacklist rule on the Users & Security > Security > Firewall page.

Condition: None.

202101271439

Symptom: The PPIN number is NA on the processor page.

Condition: This symptom might occur if you log in to HDM for the R5500 G5 AMD server.

Resolved problems in HDM-2.23

202012130575

Symptom: You cannot log in to HDM and the fan LED is steady red.

Condition: This symptom might occur if you restart the R5500 G5 AMD server.

Resolved problems in HDM-2.18.12

202011301444

Symptom: A power alarm log occurs.

Condition: This symptom might occur if the power consumption of the R4950 G5 server exceeds 1275 W.

Resolved problems in HDM-2.18

202011300424

Symptom: HDM restarts because of BMC errors.

Condition: This symptom might occur if you perform the shutdown or shutdown and restart operations on HDM when the fan speed ratio of the R5500 G5 AMD server exceeds 70%.

Resolved problems in HDM-2.17

202010221126

Symptom: You can still add users on the User Accounts page after 16 users have been added in the HDM.

Condition: None.

202009031229

Symptom: You can use the ipmitool sdr elist command to obtain the rotation speed of the rear rotor of fan 4 on the R6900 G5 server even if the fan is not present.

Condition: This symptom might occur on the R6900 G5 server when fan 4 is absent.

Resolved problems in HDM-2.16.31

202011201532

Symptom: A 12V voltage alarm on the system board occurs.

Condition: This symptom might occur if you power off the R5500 G5 AMD server.

Resolved problems in HDM-2.16

202011030522

Symptom: The CPU_Total_Power state is unavailable on the Sensors > Power page.

Condition: This symptom might occur if the R4950 G5 server is installed with a specific processor.

Resolved problems in HDM-2.13

202009160334

Symptom: The virtual ports created through OM are not displayed on HDM.

Condition: This symptom might occur if the G3 blade server is installed with a NIC-ETH682i-MB-2 network adapter and you create a virtual port on the OM page.

202010091263

Symptom: Security vulnerability CVE-2020-14314 exists in the Linux kernel, which allows attackers to use do_split() to trigger service denial.

Condition: None.

202010091254

Symptom: Security vulnerability CVE-2020-25212 exists in the Linux kernel before 5.8.3. The vulnerability stems from TOCTOU mismatching in NFS client codes and can be exploited by attackers to obtain sensitive information.

Condition: None.

Resolved problems in HDM-2.09.00

202005110427

Symptom: No information about the NIC-FC730i-Mb-2P-M network adapter is displayed on the FC HBA page.

Condition: This symptom might occur if the G3 blade server is installed with a NIC-FC730i-Mb-2P-M network adapter.

Resolved problems in HDM-2.07.00

First release.

Troubleshooting

To obtain troubleshooting information, access the H3C official website at https://www.h3c.com/en/Support/Resource_Center/EN/Home/Severs/00-Public/Maintain/Troubleshooting/H3C_Servers_TG/.

Technical support

To obtain support services, contact H3C Support at service@h3c.com.

Appendix A Feature list

Table 20 Software features

Category	Features
Web UI	Web interface in both Chinese and English Online help Compatible with IE 11, Chrome 48, Firefox 78, and later versions
IPMI	IPMI 2.0, compatible with DCMI
Redfish	Redfish (version 1.5.0)
SNMP	SNMPv1, SNMPv2c, and SNMPv3 Authentication and encryption for SNMPv3 SNMP trap
Unified control	Device adding and removal Device status query Power control HDM access H5 KVM remote console
LCD display	Touchable 3.5-inch LCD display optional for some server models HDM and BIOS firmware versions Health status of the server and its components Management port network settings, including DHCP enablement, IPv4 address, network adapter mask, and default gateway Restoration of administrator account information
Intelligent security bezel	Use of lighting effect to indicate system health and power load status
System information	Product information (product name, serial number, and configurable asset label) Hardware and status information about components, including processors, memory, storage, fans, power supplies, network adapters, PCIe modules, GPU modules, and FC HBAs CUPS information (CPU, memory, and I/O CUPS dynamic load factors used to indicate running service composition)
Sensors	Sensor information display History temperature, current, voltage, and fan speed curves Temperature heatmaps in 3D view
Resource monitoring	Processor, memory, and drive usage monitoring and alarming with FIST SMS installed Threshold configuration
Health diagnosis	Viewing the health status of the server system Fault and predictive failure alarms about processors, memory, PCIe devices, storage controllers, storage media, fans, and power supplies Viewing the current POST code and all POST codes generated during the current startup Reboot reason query
Log management	HDM event log (info, minor, major, and critical severity levels) HDM operation log, including audit log, firmware upgrade log, hardware upgrade log, and configuration log SDS log (supporting time range-based log filtering and SDS log encryption) Log download
Log reporting	SNMP trap based on module OID or event OID Alert email notification by severity levels Syslog settings, such as server port number, transmission protocol, and TLS encryption transmission Event log report configuration through Redfish event subscription
Server U disk	Log download upon USB disk insertion
Local serial port and SOL connection	Connection mode for the local serial port and SOL connection: BIOS, smart network adapter, and mezzanine RAID controller.
BSoD screenshots	Blue screen of death screenshots for Windows operating systems
Video replay	Downloading, deleting, and playing videos that record system crash, reset, or shutdown events
Alert policies	NMI control MCA policy: Server restart upon IERR occurrence
RemoteXDP	Viewing and debugging server processors, an alternative to Jtag XDP Supported only by servers using Skylake and Whitely processors of Gen 4 or lower
iHDT	Remote out-of-band JTAG debugging of AMD processors Collection of information about processors, memory, and other components
Device management	Intelligent fan speed adjustment and fan speed mode selection Overtemperature protection LEDs, including the UID, power state LED, and health LED Diagnostic panel Network adapter information obtaining through MCTP, including MAC address, connection status, and speed information FC HBA information obtaining, including temperature, link status, and speed DCPMM information obtaining, including DCPMM temperature, controller temperature, and remaining life
Storage information	Collection of information about storage controllers and storage media Configuration of logical drives managed by LSI storage controllers (excluding 9300 and 9310) and P460 and H460 PMC storage controllers Status configuration of physical drives managed by LSI storage controllers (excluding 9300 and 9310) Obtaining information about NVMe drives, including NVMe status, slot number, and read/write lifetime
Hard partitioning	Allowing an 8-processor server to operate as two independent 4-processor servers
Boot options	Boot mode and boot option for the next startup Validity period for the next boot mode and option
Power profile	Power actions: Force system reset, force power-off, graceful power-off, power-on, and force power-cycle. Power-on policy: Always power on, always power off, restore last power state, and power-on delay Power match protection: Input control of a mismatched power supply and alarm generation History power curve
Power control	Power supply mode: Active/standby and active/active Power supply operating mode: Performance, balanced performance, balanced power, and power Processor power states, including P-states and T-states. Power capping for Intel and AMD processors
Remote control	Remote server access KVM remote consoles, including shared mode and dedicated mode H5 KVM remote consoles, including shared mode, dedicated mode, and encrypted mode Remote image mounting Virtual file folders
VNC	Dedicated mode and shared mode Password complexity check
Dual network interface backup	Concurrent connections with both the HDM dedicated port and shared port for management link backup Bonding mode NCSI port autosensing Network port autosensing
Network port	IPv4 and IPv6 DHCPv4 and DHCPv6 VLAN DNS and registration by DHCP Client FQDN and host name
USB Wi-Fi	Connecting a Xiaomi USB Wi-Fi adapter to the G5 server to provide the wireless hotspot service for HDM
NTP	NTP time synchronization DHCP time synchronization Time synchronization with the server
LLDP	Obtaining information about all switches in the local network LLDP frame sending
Security	Local user management, including interface privilege configuration User-group defined user privileges (three predefined user groups and five custom user groups) Enhanced password complexity Configuring, filtering, and deleting sessions Service configuration, including the service port and maximum number of sessions SSL certificate upload, generation, and viewing
Domain users	LDAP user authentication AD authentication
Platform Firmware Resiliency (PFR)	Firmware protection, detection, and restoration by using the Intel PFR
Two-factor authentication	Using DKEY token, one-time password (OTP) servers, and GM encryption algorithm to provide two-factor authentication
Network firewall	Whitelist and blacklist based on IP address, time range, and MAC address
Configuration management	HDM, BIOS, or RAID configuration import and export Restoring HDM factory default
Firmware upgrade	In-band firmware upgrade Out-of-band firmware upgrade Firmware upgrade for HDM, BIOS, CPLD, LCD, and power supply Primary/backup BMC firmware switchover

Appendix B Updating software for rack servers

The following information describes how to upgrade the HDM firmware from the HDM Web interface for the R6900 G5 server.

Screenshots in this section are for illustration only. They might vary as the software version changes.

About HDM upgrade

Hardware Device Management (HDM) is a microprocessor embedded in the server to provide server management and control. You can upgrade HDM from the HDM Web interface without affecting server operation.

Logging in to HDM

1.Open a browser, and enter the HDM management IP address in the https://hdm_ip_address format in the address bar. In this example, the HDM management IP address is 172.17.0.211.

2.On the sign-in page, enter the username and password, and then click Sign in.

The default username is admin and the default password is Password@_.

Figure 1 HDM sign-in page

(Optional) Backing up the current configuration

As a best practice, back up the current configuration in case the upgrade causes a configuration loss.

To back up the current configuration:

1.On the top navigation bar, click Remote O&M.

2.In the left navigation pane, select Manage Configuration.

3.In the navigation pane, select Remote O&M > Manage Configuration.

Figure 2 Backing up the current configuration

4.Click Export to save the configuration locally.

Updating the HDM firmware

CAUTION:

Do not refresh the page during the upgrade.

Do not power on or power off the server during the upgrade.

To upgrade the HDM firmware:

1.On the top navigation bar, click Remote O&M.

2.In the left navigation pane, select Upgrade Firmware.

3.In the Upgrade Firmware section, click Upgrade Firmware.

4.In the work pane, specify the upgrade firmware image file:

a.Select HDM as the firmware type.

b.Select the new firmware image file (.bin file).

c.Select the HDM restart method after the upgrade is complete. You can have HDM automatically restart or manually restart HDM when the upgrade finishes.

d.To remove all user-configured settings after the upgrade, enable restoring factory default.

CAUTION:

Do not enable restoring factory default, unless otherwise required by the new version. The Restore factory default option removes all user configured settings when HDM starts up with the new firmware. When you select this option, make sure you understand its impact on the services.

e.Click Next.

Figure 3 Specifying the new HDM firmware image

5.Verify that the new firmware image version is correct, and then click Next.

Figure 4 Verifying the HDM firmware image version

$C:\Users\l18583\Desktop\1-3.PNG$

6.Follow the system instructions to complete the upgrade.

Figure 5 Upgrade start confirmation

7.Restart HDM if you selected Restart HDM manually.

a.On the top navigation bar, click Remote O&M.

b.In the left navigation pane, select Upgrade Firmware.

c.In the Upgrade Firmware section, click Restart HDM.

Figure 6 Restarting HDM

8.Clear the browser cache, and then re-sign in to HDM.

Clearing the browser cache ensures the correct display of webpage contents after you re-sign in to HDM. For more information, see "Clearing the browser cache."

9.Verify that the primary image has been upgraded on the Remote O&M > Upgrade Firmware page.

Figure 7 Verifying that the primary HDM firmware image has been upgraded

10.Click Switchover.

11.After HDM restarts, re-sign in to HDM and repeat the upgrade process. Make sure both the primary and backup images are upgraded to the same version.

Handling firmware upgrade failures

If a firmware upgrade fails, the system starts up with the original firmware version.

To resolve the firmware upgrade failure issue:

1.Verify that HDM is selected as the firmware type.

2.Verify that the firmware image file is compatible with your server model and is not corrupt. Download the desired image file again if the image file is incompatible with the server or is corrupt.

3.Verify that the HDM client and the HDM server have a stable network connection.

Clearing the browser cache

Deleting the browsing history in Internet Explorer

1.Click the Tools icon, and then select Internet options from the menu that opens.

Figure 8 Tools menu

2.Click Delete….

Figure 9 Internet options

3.In the Delete Browsing History window, retain the default settings, and then click Delete.

Figure 10 Deleting the browsing history

Deleting the browsing history in Firefox

1.Click the Open menu icon, and then select Library from the menu that opens.

Figure 11 Menu options

2.Select History.

Figure 12 Library options

3.Select Clear Recent History….

Figure 13 Clearing the recent history

4.Click Clear Now.

Figure 14 Clearing history now

Deleting the browsing history in Chrome

1.Click the Customize and control Google Chrome menu icon, and then select History from the menu that opens.

Figure 15 Customize and control Google Chrome menu

2.Click Clear browsing data….

Figure 16 Clearing browsing data

Appendix C Acronyms

Acronym	Full name
HDM	Hardware Device Management
BIOS	Basic Input and Output System
FIST	Fast Intelligent Scalable Toolkits
REPO	Repository
SDS	Smart Diagnosis System
RAID	Redundant Arrays of Independent Disks
MCA	Machine Check Architecture

Appendix D Fixed security vulnerabilities

Fixed vulnerabilities in HDM-3.33

CVE-2022-2827

After you set the number of login failures that can trigger account lockdown, users can deduce backwards which users exist and which users do not.