Version:3.52(2025/1/6)
Upgrade recommendations
optional for upgrade
Problems Solved
Resolved problems in HDM-3.52
Symptom: The event log reports a power supply self-test error 15 days after you set the active/standby power supply mode for the server.
Condition: This symptom might occur if you set the active/standby power supply mode for the server.
Symptom: When you view the operation log from the HDM Web interface, the Web interface automatically returns to the login page.
Condition: This symptom might occur if the operation log contains garbled information.
New Functions
HDM-3.52
HDM-3.52 added support of the following hardware options for the R5300 G5:
Hexaflake C20 GPU
Kunlunxin P800 GPU
HDM-3.52 added support of the following hardware options for the R4900 G5:
NIC-ETH330T-3S-4P network adapter
Upgrade recommendations
optional for upgrade
Problems Solved
Resolved problems in HDM-3.51
Symptom: The HDM Web interface does not display information about the NIC-BCM957508-P2100G-2P network adapter.
Condition: This symptom might occur if you set FunCtion Mode to NPAR1.0 for NIC-BCM957508-P2100G-2P on the Advanced menu in the BIOS setup utility, save the configuration, and then restart the device.
Symptom: The HDM Web interface mistakenly reports an uncorrected error on DIMMs..
Condition: This symptom might occur if the server misinterprets M2M related registers when it reports MCA alarms.
New Functions
HDM-3.51
HDM-3.51 added support of the following hardware options for the R5300 G5:
CXMT 32G memory module.
Upgrade recommendations
optional for upgrade
Problems Solved
Resolved problems in HDM-3.50
Symptom: For the R4900 G5, the HDM Web page displays that a drive missing alarm is present but no anomaly is detected under the system.
Condition: This symptom might occur if an issue occurs with communicating with the storage controller to retrieve information during the HDM startup process.
New Functions
HDM-3.50
HDM-3.50 added support of the following hardware options for the R4900 G5:
Leadtek 4090D GPU.
Union Memory UM311b 480G/960G/1.92T/3.84T SATA SSD.
HDM-3.50 added support of the following hardware options for the R4930 G5 H3:
Scaleflux CSD3000 7.68T NVMe drive
NIC-ETH-N500L-FH-4P-GE network adapter
HDM-3.50 added support of the following hardware options for the R5300 G5:
metaScale-200S network adapter
metaScale-200 network adapter
HDM-3.50 added support of the following hardware options for the R5500 G5 AMD:
3140H network adapter
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-6.14.01
Symptom: When you use the Redfish interface to obtain some performance metric data, execution errors occur.
Condition: This symptom might occur when you use the Redfish interface to obtain some performance metric data.
Symptom: When you obtain power consumption data through HDM on the R4900 G5 server, data fluctuation issues occur.
Condition: This symptom might occur when you obtain power consumption data through HDM on the R4900 G5 server.
Symptom: After prolonged server operation, SDS logs failed to be downloaded through HDM, leading to repeated HDM restarts.
Condition: This symptom might occur after the server operates for a long period of time.
New Functions
HDM-6.14.01
HDM-6.14.01 added support of the following hardware options for the R4900 G5:
QLE2694-SR-AK 16G FC-HBA
HDM-6.14.01 added support of the following hardware options for the R4930 G5 H3:
UN-SSD-1.6T-NVMe-PE321
UN-SSD-1.92T-NVMe-PE321
UN-SSD-3.2T-NVMe-PE321
UN-SSD-3.84T-NVMe-PE321
UN-SSD-6.4T-NVMe-PE321
UN-SSD-7.68T-NVMe-PE321
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.49.01
202405141974
Symptom: The server's input and output power values obtained through the Redfish interface are the same.
Condition: This symptom might occur if you use the Redfish interface to obtain the power values for a server installed with an Intel processor.
202408230652
Symptom: When you change the user password through the HDM web page, if the ID in the interface URL and the ID in the BODY are inconsistent, the change can still succeed.
Condition: This symptom might occur if the ID in the interface URL and the ID in the BODY are inconsistent when you change the user password through the HDM web page.
202406191302
Symptom: The R4900 G5 server intermittently shows the hard drive status as Ready.
Condition: This symptom might occur if you configure logical drives under a PMC storage controller for an R4900 G5. The status of member drives of the logical drives might change to Ready.
202407070061
Symptom: After the server runs for a period, SDS logs cannot be downloaded via HDM, leading to repeated HDM reboots.
Condition: This symptom might occur after the server runs for a period.
New Functions
HDM-3.49.01
HDM-3.49.01 added support of the following hardware options for the R5300 G5:
Enflame S60 GPU
HDM-3.49.01 added support of the following hardware options for the R4900 G5:
NS8500 G2 1.92&3.2&7.68TB SSD
HDM-3.49.01 added support of the following hardware options for the R4950 G5:
SSD-7.68T-NVME-CD8P
SSD-7.68T-NVME-7940M
HDM-3.49.01 added support of the following hardware options for the R4930 G5 H3:
SSD-1.92T-NVME-J5100
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.48
Symptom: The B5700 G5 failed to interconnect with the OM module after historical passwords are disabled on BMC for the B5700 G5.
Condition: This symptom might occur if historical passwords are disabled on BMC for the B5700 G5.
Symptom: A service alarm occurs on the server due to I/O delays.
Condition: This symptom might occur if the LSI storage controller is configured and CC inspection is enabled in an in-band manner.
Symptom: You can create a logical drive in RAID 10 for the LSI-9460-8i storage controller through the Web interface. If the number of RAID arrays exceeds eight, the creation might fail, causing the storage process to get stuck.
Condition: This symptom might occur if you create a logical drive in RAID 10 for the LSI-9460-8i storage controller through the Web interface, but the number of RAID arrays exceeds eight.
Symptom: The Redfish library failed to use the BMC interface to obtain part of performance indexes incorrectly.
Condition: This symptom might occur if the Redfish library uses the BMC interface to obtain power output consumption.
New Functions
HDM-3.48
HDM-3.48 added support of the following hardware options for the R4900 G5:
QLE2694-SR-AK 16G FC-HBA
ScaleFlux CSD 3320 3.84TSSD
HDM-3.48 added support of the following hardware options for the R4950 G5:
Hanbo GPU VG1000-32G-LP
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.47
Symptom: Multiple devices report that the number of out-of-band user connections has reached the upper limit and the response from the IPMI command indicates that the session resources are insufficient.
Condition: This symptom might occur if the sol activate and sol deactivate commands are executed in the script under pressure.
Symptom: Eight R4900 G5 servers in the same rack abnormally shut down. After manual restart, the servers recover to normal.
Condition: This symptom might occur if an abnormal external power input led to a secondary power alarm on the server.
Symptom: Some indexes obtained from the Redfish API are abnormal.
Condition: This symptom might occur if you use the Redfish API to obtain input and output power multiple times.
Symptom: An HDM login failure occurs when you use a password containing percent symbols (%).
Condition: This symptom might occur if a password used for HDM login contains percent symbols (%).
Symptom: When you use the OID (.1.3.6.1.4.1.25506.13.1.2.1.2.2.1.1.7) to monitor temperature status on components according to the MIB and SNMP manuals, the component health status information is returned. The MIB and SNMP manuals are incorrect.
Condition: This symptom might occur if you use the OID (.1.3.6.1.4.1.25506.13.1.2.1.2.2.1.1.7) to monitor the temperature status of components.
New Functions
HDM-3.47
HDM-3.47 added support of the following hardware options for the R4900 G5:
MCX515A-CCUT network adapter
NIC-ETH-SP670-FHHL-2P 100G network adapter
Dapustor R5 1.92&3.2&7.68TB drive
HDM-3.47 added support of the following hardware options for the R5300 G5:
Hanbo VA10 GPU
HDM-3.47 added support of the following hardware options for the CX8028G G5:
IB-MCX755106AS-HEAT-200Gb-2P
HDM-3.47 added support of the following hardware options for the R5500K:
VR chip compatible with the Infineon solution
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.46.01
Symptom: After you configure an NVMe drive, the life span read is 255, triggering a critical life span alarm.
Condition: This symptom might occur if the system reads the life span of an NVMe drive after you configure the drive.
New Functions
HDM-3.46.01
HDM-3.46.01 added support of the following hardware options for the R4900 G5:
Dapustor R5101-1.92T/R5301-3.2T
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.46
Symptom: When you update HDM from the Web interface for the R4900 G3, the page prompts that the admin account does not the permission to perform the update.
Condition: This symptom might occur if the HDM Web service restarts exceptionally.
Symptom: When you set the domain name for an SNMP trap server through the Redfish interface, the domain name cannot contain three or more dots (.).
Condition: This symptom might occur if you set the domain name for an SNMP trap server through the Redfish interface.
New Functions
HDM-3.46
HDM-3.46 added support of the following hardware options for the R5300 G5:
DapuStor H5100 7.68TB(FW:FF035008) NVMe drive
NVIDIA L2 GPU
VR chip compatible with the Infineon solution
Colorful 4090 GPU
HDM-3.46 added support of the following hardware options for the R4900 G5:
DapuStor Jiaorong 5 1.92&3.2&7.68TB
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.45
Symptom: The fan noise is loud in the R4900 G3 server.
Condition: This symptom might occur if DHCPv6 packets that carry NoAddrAvail information is transmitted in the network.
Symptom: Continuously initiating SSH connection requests to HDM results in a false BIOS reset alarm being printed in HDM, even though the actual server has not restarted.
Condition: This symptom might occur if SSH connection requests are continuously initiated to HDM.
Symptom: The model of the NIC-GE-4P-360T-B2-1-X network adapter is displayed as N/A on the web page.
Condition: This symptom might occur if an NIC-GE-4P-360T-B2-1-X network adapter is installed.
Symptom: When a UCME alarm is triggered for the A0 and E0 memory of the R4900 G5 server, BMC incorrectly interprets the CPU1 E0 CE alarm as a CPU1 A0 E0 UCE alarm.
Condition: This symptom might occur if a UCME alarm is triggered for the A0 and E0 memory.
Symptom: The server subscribed to Redfish events is unable to receive log reports of PMC controller failures.
Condition: This symptom might occur if the Redfish event subscription server subscribes to the corresponding device and a PMC controller alarm is triggered.
Symptom: HDM cannot be accessed through HTTPS.
Condition: This symptom might occur under a large number of HTTPS attacks because Lighttpd has a mechanism that uses iptables to add the corresponding port and IP to the denylist.
Symptom: The power LED on the R4900 G3 server turns red for an alarm, but HDM does not associate with the fault.
Condition: This symptom might occur if the power LED on the R4900 G3 server turns red for an alarm.
New Functions
HDM-3.45
HDM-3.45 added support of the following hardware options for the R4930 G5 H3:
DATSSD 480G/960G/1.92T/3.84T-SATA-DSS200-B K5 SSD
union 480G/960G/1.92T-UM310a drive
UN-SSD-1.92T/3.84T/7.68T/1.6T/3.2T/6.4T-NVMe-PE321 drive
HDM-3.45 added support of the following hardware options for the R4900 G5:
NIC-ETH-3S910-LP-2P-25G network adapter
NIC-ETH-SF200T-LP-2P-GE network adapter
NIC-ETH-SF400T-LP-4P-GE network adapter
NIC-ETH-RP1000P2SFP-LP-2P network adapter
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.44.01
Symptom: After the R4900 G3 has been running for 497 days, some monitoring platforms cannot display SNMP v3 traps generated on the server.
Condition: This symptom might occur is you view SNMP v3 traps on some monitoring platforms after the R4900 G3 has been running for 497 days.
New Functions
HDM-3.44.01
None.
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.43
Symptom: The NVMe drive information in the physical view of the storage management page on HDM does not match the actual information when the following conditions are met:
The R4930 G5 (H3) server is installed with the 25SFF drive backplane and the rear 4SFF Unibay drive backplane.
NVMe drives are attached to the rear 4SFF Unibay drive backplane.
Condition: This symptom might occur if the R4930 G5 (H3) server is installed with the 25SFF drive backplane and the rear 4SFF Unibay drive backplane and NVMe drives are attached to the rear 4SFF Unibay drive backplane.
Symptom: HDM might mistakenly report a drive fault alarm on all the drives attached to an LSI storage controller on the server.
Condition: This symptom might occur if an LSI storage controller is installed on the server.
Symptom: BMC reports a power fault on the system board when a sudden AC power-off occurs due to an unstable power grid for the R4900 G5.
Condition: This symptom might occur if a sudden AC power-off occurs due to an unstable power grid for the R4900 G5.
New Functions
HDM-3.43
HDM-3.43 added support of the following hardware options for the R4930 G5 H3:
SSD-3.2T-NVMe-PB6537-AIC
SSD-6.4T-NVMe-PB6537-AIC
SSD-3.2T-NVMe-J5310-AIC
SSD-6.4T-NVMe-J5310-AIC
SSD-7.68T-NVMe-J5110-AIC
Hanbo GPU VG1000-64G-LP
NIC-ETH-RP1000SFPH102-3S-10G-2P
HDM-3.43 added support of the following hardware options for the R4900 G5:
X710-T2L network adapter
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.42
Symptom: When the password validity is set on the server, hREST cannot obtain the related information.
Condition: This symptom might occur when the password validity is set on the server.
Symptom: Overtemperature occurs on the module if the R300 module is used on the R5500K.
Condition: This symptom might occur if the R300 module is used on the R5500K.
New Functions
HDM-3.42
HDM-3.42 added support of the following hardware options for the R4900 G5:
Vastai VA1L GPU
Vastai VA1-16G GPU
Solidigm P5520 15.36T drive
HDM-3.42 added support of the following hardware options for the R4930 G5 H3:
Denglin GPU Goldwasser-L256
SSD-7.68T-NVME-PB6531-AIC
Longsys SATA SSD
HDM-3.42 added support of the following hardware options for the R5300 G5:
Iluvatar BI-V150 GPU
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.41
Symptom: When the password validity is set on the server, hREST cannot obtain the related information.
Condition: This symptom might occur when the password validity is set on the server.
Symptom: When drives are installed to the R4900 G5 with the 8SFF UniBay drive backplane, the drive locations displayed on HDM do not match the actual configurations.
Condition: This symptom might occur if the R4900 G5 is installed with 8SFF UniBay drive backplane.
Symptom: When an ADDDC error occurs, the server does not report the corresponding log information.
Condition: This symptom might occur if an ADDDC error occurs on the server.
Symptom: When the server is installed with a PCIe module that has MB in its name and an error occurs on the PCIe module, MCA suggests replacing the module. However, HDM shows a critical alarm on the system board.
Condition: This symptom might occur if the server is installed with a PCIe module that has MB in its name and an error occurs on the PCIe module.
Symptom: An SEL alarm of system detected the absence of a DIMM was mistakenly reported on the R5500 G5.
Condition: This symptom might occur if a G5 Intel sever is installed with non-certified DIMMs and is restarted.
New Functions
HDM-3.41
HDM-3.41 added support of the following hardware options for the R4900 G5:
Solidigm P5520 15.36T drive
Great Wall 2700W power supply
IVA-CP24-VA
HDM-3.40 added support of the following hardware options for the R4950 G5:
Configuration only with the rear 4SFF UniBay drive backplane
HDM-3.40 added support of the following hardware options for the R5300 G5:
Iluvatar V100 (MR) GPU
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.40
Symptom: When there is a partial power failure in the R4900 G3 server, the health LED turns red, and there are no alarm messages displayed on the HDM webpage.
Condition: The symptom might occur when there is a partial power failure in the R4900 G3 server.
Symptom: In R4930 G5 H3 servers with multiple drive backplanes, there is a low probability of receiving drive fault and missing alarm logs on HDM during the host startup process.
Condition: The symptom might occur when R4930 G5 H3 servers are configured with multiple drive backplanes, and there is a low probability of receiving false disk alarms on HDM during the host startup process.
Symptom: When performing fieldiag on R5500 G5 servers, there is a random occurrence of errors.
Condition: The symptom might occur when R5500 G5 servers are paired with a specific version of HDM and fieldiag is executed in-band.
New Functions
HDM-3.40
HDM-3.40 added support of the following hardware options for the R4900 G5:
95 series storage controllers for 12LFF+2SFF UniBay configuration
9560-8i storage controller for 8UniBay configuration
HDM-3.40 added support of the following hardware options for the R4930 G5 H3:
NIC-ETH-3S930-LP-2*100G
HDM-3.40 added support of the following hardware options for the R5500 G5:
NVIDIA A800 HGX 40G module
Upgrade recommendations
Recommended Upgrade
Problems Solved
Resolved problems in HDM-3.39
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.
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.
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.
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.
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.
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.
New Functions
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
Upgrade recommendations
Recommended Upgrade
Problems Solved
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.
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.
New Functions
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)
Upgrade recommendations
Problems Solved
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.
New Functions
HDM-3-37.01
None.
Upgrade recommendations
Problems Solved
Resolved problems in HDM-3.35.01
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.
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.
New Functions
HDM-3-35.01
HDM-3.35.01 added support of the following hardware options for the R4900 G5:
MBF2H512C-AEUOT
Upgrade recommendations
Problems Solved
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
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
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.
Symptom: The BIOS restarts once every 15 minutes because of BIOS watchdog timeout.
Condition: This symptom might occur after you enable IPMI command firewall.
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
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
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.
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
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.
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.
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.
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.
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.
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
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.
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
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.
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
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
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
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.
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.
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.
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.
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.
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
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.
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.
Symptom: A slow HTTP DoS attack is detected on HDM.
Condition: None.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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
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
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.
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.
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.
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
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
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.
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
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
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.
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.
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
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.
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.
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
Symptom: Added a field to Test packets for SNMP trap to indicate the Info alarm level.
Condition: None.
Symptom: The (recommended) string was removed from the Event mode field on the Remote O&M > Alarm Settings > SNMP trap page.
Condition: None.
Symptom: Trap packets of SNMPv2 or SNMPv3 carry trap OIDs.
Condition: This symptom might occur when SNMPv2 or SNMPv3 trap is used.
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.
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.
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.
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
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
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.
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.
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.
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
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
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
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.
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.
Symptom: You cannot select the product serial number as the alarm log host ID on the syslog settings page of HDM.
Condition: None.
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.
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
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
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.
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.
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
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
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.
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.
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.
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
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
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.
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.
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.
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.
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.
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.
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.
Symptom: Added support for configuring and obtaining CPU turbo frequency.
Condition: None.
Symptom: Added support for importing and exporting AD configuration.
Condition: None.
Resolved problems in HDM-2.55
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
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).
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.
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.
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.
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
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.
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
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
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.
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.
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.
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
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
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.
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
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
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
Symptom: Added support for disabling the IPMI access service.
Condition: None.
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.
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
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
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.
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.
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.
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
Symptom: A memory leak occurs.
Condition: This symptom might occur if you start the pressure test on the server.
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
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
Symptom: HDM prompts an import failure when you attempt to import HDM configuration on the Remote O&M > Manage Configuration page.
Condition: None.
Symptom: HDM prompts an error when you attempt to add a new blacklist rule on the Users & Security > Security > Firewall page.
Condition: None.
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
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
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
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
Symptom: You can still add users on the User Accounts page after 16 users have been added in the HDM.
Condition: None.
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
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
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
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.
Symptom: Security vulnerability CVE-2020-14314 exists in the Linux kernel, which allows attackers to use do_split() to trigger service denial.
Condition: None.
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
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.
New Functions
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
Marvell storage controller
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.
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Login
Login