Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
202508281551
Symptom: In versions earlier than iFIST-1.83, vulnerability scanning detects that iFIST of H3C UniServer R4900 G6 has a security vulnerability where iFIST supports RSA key exchange.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.83.
202508150165
Symptom: During server diagnosis in versions earlier than iFIST-1.83 on H3C UniServer R4950 G6 installed with 8038 fans, when you select fans for fast diagnosis, a diagnosis failure occurs.
Condition: This symptom might occur if you select fans for fast diagnosis during server diagnosis in versions earlier than iFIST-1.83 on H3C UniServer R4950 G6 installed with 8038 fans.
None.
None.
None.
None.
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
202508281551
Symptom: In versions earlier than iFIST-1.83, vulnerability scanning detects that iFIST of H3C UniServer R4900 G6 has a security vulnerability where iFIST supports RSA key exchange.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.83.
202508150165
Symptom: During server diagnosis in versions earlier than iFIST-1.83 on H3C UniServer R4950 G6 installed with 8038 fans, when you select fans for fast diagnosis, a diagnosis failure occurs.
Condition: This symptom might occur if you select fans for fast diagnosis during server diagnosis in versions earlier than iFIST-1.83 on H3C UniServer R4950 G6 installed with 8038 fans.
None.
None.
None.
None.
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
None.
None.
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
None.
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
Symptom: The HTTP Referrer-Policy header missing vulnerability was detected during vulnerability scanning in a version earlier iFIST-1.74.
Condition: This symptom might occur if you perform vulnerability scanning in a version earlier than iFIST-1.74.
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
Symptom: In versions earlier than iFIST-1.73, the vulnerability scanning software detects a security vulnerability that the X-Permitted-Cross-Domain-Policies header is missing.
Condition: This symptom might occur if you use the vulnerability scanning software in version earlier than iFIST-1.73.
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
None.
None.
Symptom: If you use UniSystem to export a cloned image from a server using iFIST-1.69, the export operation fails.
Condition: This symptom might occur if you use UniSystem to export a cloned image from a server using iFIST-1.69.
None.
Symptom: The drive log of DapuStor H5300 6.4T drives failed to be downloaded in a version earlier than iFIST-1.68.
Condition: This symptom might occur if you download the drive log of DapuStor H5300 6.4T drives in a version earlier than iFIST-1.68.
None.
None.
None.
None.
None.
None.
Symptom: If you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing, the Rand Read test fails and the system reports an abnormal program execution error.
Condition: This symptom might occur if you diagnose servers with iFIST-1.63 or earlier versions and select physical or logical drives for stress testing.
None.
None.
None.
Symptom: When you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled, the system reports a diagnostic failure.
Condition: This symptom might occur if you use iFIST of a version earlier than 1.59 for CPU UPI link diagnosis with BIOS NUMA disabled.
Symptom: Failed to enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Condition: This symptom might occur if you enable or disable ACS capability on the H3C UniServer R5500 G5 Intel from iFIST.
Symptom: Failed to install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Condition: This symptom might occur if you install a new version of Windows 2019 by using iFIST-1.58 or earlier.
Symptom: Failed to use iFIST to install the OS on the R5500 G5 server with HDM-3.34.
Condition: This symptom occurs if iFIST is used for OS installation on the R5500 G5 server with HDM-3.34.
Symptom: Vulnerabilities CVE-2023-0286, CVE-2022-4304, CVE-2023-0464, CVE-2023-0215, CVE-2022-4450, CVE-2023-0465, and CVE-2021-3156 are detected during vulnerability scanning in a version earlier than iFIST-1.57P01.
Condition: None.
None.
Symptom: Vulnerability CVE-2023-21830 is detected during vulnerability scanning in a version earlier than iFIST-1.55.
Condition: None.
Symptom: iFIST is stuck at entering the GUI when you start iFIST, and both processors and network adapters are fully configured on R3830 G5 H3.
Condition: This symptom occurs if you start iFIST when both processors and network adapters are fully configured on R3830 G5 H3.
Symptom: When you perform iFIST device diagnosis on servers with a serious fan failure, a diagnosis error occurs on the system diagnosis module.
Condition: This symptom occurs if you perform iFIST device diagnosis on servers with a serious fan failure.
Symptom: When you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310, the system mistakenly identifies the GPU information in slot 9.
Condition: This symptom occurs if you perform iFIST device diagnosis on an H3C UniServer R2700 G3 server installed with the GPU-XG310.
Symptom: Vulnerability CVE-2017-12626 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2020-13956 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerability CVE-2019-10086 is detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2016-1000031 and CVE-2016-3092 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: Vulnerabilities CVE-2019-12406, CVE-2019-12419, CVE-2019-12423, CVE-2019-17573, CVE-2020-13954, CVE-2020-1954, CVE-2021-22696, and CVE-2021-30468 are detected during vulnerability scanning in a version earlier than iFIST-1.51.
Condition: None.
Symptom: If you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process, the white screen error occurs and the system prompts a startup error. iFIST cannot be entered.
Condition: This symptom occurs if you use iFIST to clear data on a server installed with a PMC controller and restart the device during the process.
Symptom: Drive Smart information downloading fails through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Condition: This symptom occurs if you download drive Smart information through iFIST from a server installed with an HBA-LSI-9300-8i-A1-X controller.
Symptom: Drive log downloading from iFIST fails if Samsung NVMe drives are present.
Condition: This symptom occurs if you use iFIST to download drive logs for a server installed with Samsung NVMe drives.
Symptom: Security vulnerability CVE-2022-2068 is found during vulnerability scanning in a version earlier than iFIST-1.47.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.47.
Symptom: Log downloading fails when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Condition: This symptom occurs when you use iFIST of a version earlier than 1.47 to download logs from a server installed with Memblaze Pblaze5 926 NVMe drives.
Symptom: iFIST installation fails on an H3C UniServer R4330 G5 server.
Condition: This symptom might occur if you install iFIST on an H3C UniServer R4330 G5 server.
202205190410
Symptom: The security vulnerability of OpenSSL OS command injection CVE-2022-1292 is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
202205250943
Symptom: The security vulnerability of FastJson remote code execution via deserialization is found when vulnerabilities are scanned for a version earlier than iFIST-1.46.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.46.
Symptom: When an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC, the iFIST diagnosis module cannot recognize the NIC.
Condition: This symptom occurs if an R4900 G5 device is connected to a UN-NIC-iETH-MBF2H512C-AESOT NIC and iFIST performs device diagnosis.
Symptom: When Memblaze hard drives are connected to a device, it takes about an hour to download the hard drive logs on iFIST.
Condition: This symptom occurs if Memblaze hard drives are connected to a device, and you select to download hard drive logs on iFIST.
Symptom: When an R4500 G3 server is installed with multiple storage controllers, these storage controllers cannot be recognized.
Condition: This symptom occurs if you install multiple storage controllers to the R4500 G3 server.
Symptom: OpenSSL security vulnerability CVE-2022-0778 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: OpenSSH security vulnerabilities CVE-2021-36368 and CNNVD-202203-1230 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: cURL security vulnerabilities CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2021-22876, CVE-2021-22890, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, and CVE-2021-22946 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Libcurl security vulnerabilities CVE-2021-22924 and CVE-2021-22945 are found when vulnerabilities are scanned for a version earlier than iFIST-1.43.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: Security vulnerability CVE-2019-17498 is found when vulnerabilities are scanned for a version earlier than iFIST-1.43. With this vulnerability, in libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an input check vulnerability.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.43.
Symptom: The system detects the OpenSSL DoS vulnerability (CVE-2021-3712) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: The system detects the OpenSSL buffer overflow vulnerability (CVE-2021-3711) when vulnerability scanning is performed in versions earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.42.
Symptom: Security vulnerability CVE-2021-4034 (Linux Polkit privilege escalation vulnerability) is found when vulnerabilities are scanned for a version earlier than iFIST-1.42.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.42.
Symptom: The system detects the CVE-2021-42550 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.41.
Condition: This symptom might occur if vulnerability scanning is performed in versions earlier than iFIST-1.41.
Symptom: OpenSSH security vulnerabilities CVE-2016-20012 and CVE-2021-41617 are found when vulnerabilities are scanned for a version earlier than iFIST-1.41.
Condition: This symptom occurs if vulnerabilities are scanned for a version earlier than iFIST-1.41.
Symptom: The system detects the CVE-2021-4104 vulnerability when vulnerability scanning is performed in versions earlier than iFIST-1.40.
Condition: This symptom occurs if vulnerability scanning is performed in versions earlier than iFIST-1.40.
Symptom: iFIST fails to install the system on a device connected to a disk larger than 1 TB.
Condition: This symptom occurs if iFIST installs the system on a device connected to a disk larger than 1 TB.
Symptom: When you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server, the system prompts that the operation succeeds, but the data still exists after restart.
Condition: This symptom occurs if you clear data for the NVDIMM memory with namespaces or the NVDIMM memory on an H3C UniServer R6900 G5 server.
Symptom: On a G5 server, use the one-click clearing function of iFIST, select the HDM+BIOS components, and restart the server after clearing data. The BIOS password is not cleared.
Condition: This symptom occurs if you use the one-click clearing function of iFIST on a G5 server, select the HDM+BIOS components, and restart the server after clearing data.
Symptom: If the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode, the server will automatically restart when iFIST is installed. As a result, the installation fails.
Condition: This symptom occurs if the iFIST image is mounted on an H3C UniServer R4300/R4900 G5 server in legacy mode and then iFIST is installed.
Symptom: If you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the CentOS8.X operating system together with the Mellanox NIC drivers through iFIST.
Symptom: In iFIST 1.36 or earlier, if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server, the installation fails.
Condition: This symptom occurs if you install a Microsoft Windows Server 2016 image loaded with Hygon drivers on an H3C UniServer R4930 G5 server in iFIST 1.36 or earlier.
Symptom: Vulnerabilities in vulnerable JavaScript libraries are found when vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Condition: This symptom occurs if vulnerability scanning is performed in iFIST 1.36 and earlier versions.
Symptom: In iFIST 1.36 and earlier, if you install the Red Hat operating system together with the Mellanox NIC drivers, the Mellanox NIC drivers fail to be installed.
Condition: This symptom occurs if you install the Red Hat operating system together with the Mellanox NIC drivers in iFIST 1.36 and earlier.
Symptom: On the device where the USB flash drive hosting the UniTool tool is installed, if a USB flash drive with the same UUID is installed, only one USB flash drive can be recognized.
Condition: This symptom occurs if a USB flash drive with the same UUID is installed on the device where the USB flash drive hosting the UniTool tool is installed.
Symptom: When iFIST performs diagnostics for a disk that does not support self test, diagnostics time out and fail.
Condition: This symptom occurs if iFIST performs diagnostics for a disk that does not support self test.
Symptom: When the ICE driver version is low in the iFIST system, the Rack_NIC-ETH-E810CQDA1G1P5-1P_FW_Redhat8.2_2.30_Linux component package fails to be updated through HDM out-of-band firmware update.
Condition: This symptom occurs if the ICE driver version is low in the iFIST system.
Symptom: The driver name and driver version for a UN-NIC-RP1000P2SFP-B-10Gb network adapter display N/A.
Condition: This symptom occurs if you view information of a server installed with a UN-NIC-RP1000P2SFP-B-10Gb network adapter.
Symptom: iFIST failed to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Condition: This symptom occurs if you use iFIST to install the Microsoft Windows Server 2016 system on the H3C UniServer R4900 G5 server installed with an HBA-LSI-9440-8i storage controller.
Symptom: Failed to install the RAID-LSI-9460-16i storage controller driver from iFIST.
Condition: This symptom occurs if you install the RAID-LSI-9460-16i storage controller driver together with the Microsoft Windows Server 2012 R2 operating system from iFIST.
Symptom: If iFIST is used to collect storage controller logs, the name of the exported log file does not contain the serial number of the server.
Condition: This symptom occurs if iFIST is used to collect storage controller logs.
Symptom: When you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed, an exception occurs in the import process if the configuration different from that of the first storage controller is imported.
Condition: This symptom occurs if you install the operating system through importing a configuration file on a server with both the LSI and PMC storage controllers installed and the configuration different from that in the first storage controller module is imported.
Symptom: OS installation on an H3C UniServer R6900 G5 server fails because the OS installation process gets stuck on the GRUB screen.
Condition: This symptom occurs if you attempt to install the operating system on the H3C UniServer R6900 G5 server in Legacy boot mode.
Symptom: Installation of the VMware system failed.
Condition: This symptom occurs if the VMware system is to be installed on a raw disk on the RAID-P2404-Mf-4i-2GB controller.
None.
Symptom: The system drivers fail to be installed through iFIST.
Condition: This symptom occurs if a profile is applied in FIST and the CentOS 7.5 (64 bit) operating system and its drivers are installed in iFIST.
Symptom: The Vmware6.7U3 system fails to be installed on a server through iFIST.
Condition: This symptom occurs if you attempt to install Vmware6.7U3 through iFIST on a server that uses the RAID-P4408-Mf-8i-2GB storage controller.
Symptom: iFIST cannot recognize the RAID-P4408-Mf-8i-2GB controllers.
Condition: This symptom occurs if the firmware is upgraded to version 1.98 for the RAID-P4408-Mf-8i-2GB controllers.
Symptom: During CAS OS installation, iFIST displays a popup window prompting the user to manually activate the RAID device.
Condition: This symptom occurs if the user attempts to install the CAS operating system by using the iFIST OS installation wizard.
Symptom: iFIST cannot work correctly and keeps reporting errors.
Condition: This symptom occurs after iFIST has gone through 999 stress tests for 2 consecutive cycles and is left still for eight hours after the test.
Symptom: On a B7800 compute module, iFIST displays a blank screen for 15 minutes or longer after startup.
Condition: This symptom occurs if the B7800 compute module has the maximum number of Ethernet adapters installed and does not have the DHCP service configured.
Symptom: The iFIST Web interface turns white.
Condition: This symptom occurs if iFIST is installed on an R4900 G3 server and it started a cyclic test with the test cycles set to 9999 a few days ago.
Symptom: Installation of the Red Hat Enterprise Linux 7.5 operating system on a blade server failed with the umount file timeout error.
Condition: This symptom occurs if you attempt to install the operating system on a logical drive on the HBA-H5408-Mf-8i storage controller of the blade server.
Symptom: When no DHCP server is configured, OS installation through a server template fails.
Condition: This symptom occurs if you install an OS through a server template without DHCP settings.
Symptom: iFIST cannot start up properly on a server configured with one CPU and 8GB memory.
Condition: This symptom occurs if iFIST is installed on a server configured with one CPU and 8GB memory.
Symptom: The system gets stuck on the INITIAL SETUP page after installation of the CentOS system is complete. The operator must click FINISH CONFIGURATION to open the operating system login page.
Condition: This symptom occurs if a CentOS 7.3 system that uses a static IP address is installed.
Symptom: The Microsoft Hyper-V Server 2016 and Microsoft Hyper-V Server 2012 R2 operating systems cannot be installed on a server that uses a storage controller of model HBA-1000-M2-1.
Condition: This symptom occurs if a logical drive that exceeds 2TB in size is used as the target logical drive for installing the operating system.
Symptom: On an H3C UniServer R8900 G3 server, iFIST can detect only one storage controller for OS installation and RAID configuration even though the server has two HBA-H460-B1 storage controllers installed.
Condition: This symptom occurs if you attempt to use iFIST on an H3C UniServer R8900 G3 server that has two HBA-H460-B1 storage controllers installed.
Symptom: iFIST cannot detect the HBA-LSI-9311-8i-A1-X controller installed on a server.
Condition: This symptom occurs if you attempt to use iFIST on a server that has the HBA-LSI-9311-8i-A1-X controller installed.
Symptom: The iFIST OS installation wizard cannot detect the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server.
Condition: This symptom occurs if you attempt to use the RAID-P460-M4 RAID controller installed on an H3C UniServer R5300 G3 server for OS installation through the iFIST OS installation wizard.
Symptom: Profile-based configuration of the H3C UniServer R8900 G3 server is not available because a profile cannot be configured for the server model through the profile configuration module.
Condition: This symptom occurs if you attempt to configure a profile for the H3C UniServer R8900 G3 server through the profile configuration module.
Symptom: OS installation through the iFIST OS installation wizard failed on an H3C UniServer R8900 G3 server.
Condition: This symptom occurs if the HDM version used by the server failed to meet the lowest HDM version requirement.
First release.
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
Problems Solved
New Functions
Upgrade recommendations
Recommended Upgrade
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
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
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
Version:1.32(2021/4/30)
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
Upgrade recommendations
Problems Solved
New Functions
Upgrade recommendations
Problems Solved
New Functions
Login
