No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address:Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
This document provides the product information about the Huawei ES3000 V3 PCIe SSD
(ES3000 V3 for short) and describes how to install, configure, operate, and maintain the
ES3000 V3.
NOTE
The document does not contain the commands for production, equipment, and return detection. These
commands are commonly used during engineering implementation and fault locating. Incorrect use of
the commands results in device faults or service interruption. To obtain the commands, contact Huawei
technical support.
About This Document
About This Document
Intended Audience
This document is intended for:
lServer installation engineers
lServer maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level or medium level of
risk which, if not avoided, could result in death or
serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
1.1 General Safety Notice.....................................................................................................................................................1
1.2 Labels on Devices...........................................................................................................................................................2
2.5 System Requirements................................................................................................................................................... 20
3 Installation and Configuration................................................................................................. 22
3.1 Installation and Configuration Process.........................................................................................................................23
3.4 Verifying the Upgrade Package Integrity..................................................................................................................... 30
3.5 Transferring Files by Using WinSCP........................................................................................................................... 30
3.6 Installing the Driver......................................................................................................................................................32
3.6.1 Installing the ES3000 V3 Driver in Linux.................................................................................................................32
3.6.2 Installing the ES3000 V3 Driver in Windows...........................................................................................................35
3.6.3 Installing the ES3000 V3 Driver in ESXi................................................................................................................. 42
3.7 Installing the Tool Package...........................................................................................................................................43
3.7.1 Installing the Tool Package (Linux).......................................................................................................................... 43
3.7.2 Installing the Tool Package (Windows).....................................................................................................................44
3.7.3 Installing the Tool (ESXi)..........................................................................................................................................48
4 Hot Plug.........................................................................................................................................49
4.1 OSs Supporting Hot Plug............................................................................................................................................. 50
4.2 Orderly Hot Plug.......................................................................................................................................................... 50
4.2.1 Orderly Hot Plug of a Disk in Linux OS................................................................................................................... 50
4.2.2 Orderly Hot Plug of a Disk in Windows....................................................................................................................60
5 Maintenance and Upgrade.........................................................................................................62
5.1 Uninstalling the Driver................................................................................................................................................. 62
5.1.1 Uninstalling the Driver in Linux............................................................................................................................... 63
5.1.2 Uninstalling the Driver in Windows..........................................................................................................................64
5.1.3 Uninstalling the Driver in ESXi................................................................................................................................ 65
5.2 Upgrading the Driver....................................................................................................................................................65
5.2.1 Upgrading the Driver in Linux.................................................................................................................................. 66
5.2.2 Upgrading the ES3000 V3 Driver in Windows.........................................................................................................68
5.2.3 Upgrading the Driver in ESXi................................................................................................................................... 68
5.3 Uninstalling, and Upgrading the Tool Package............................................................................................................ 69
5.3.1 Uninstalling the Tool Package (Linux)...................................................................................................................... 69
5.3.2 Uninstalling the Tool Package (Windows)................................................................................................................ 69
5.3.3 Uninstalling the Tool (ESXi)..................................................................................................................................... 70
5.3.4 Upgrading the Tool Package (Linux)........................................................................................................................ 70
5.3.5 Upgrading the Tool Package (Windows)...................................................................................................................71
5.3.6 Upgrading the Tool (ESXi)........................................................................................................................................72
5.4 Installing and Uninstalling Citrix System Drivers and Tools....................................................................................... 72
5.4.1 Installing Citrix Drivers and Tools............................................................................................................................ 72
5.4.2 Uninstalling Citrix Drivers and Tools........................................................................................................................73
5.5 Upgrading the Controller Firmware............................................................................................................................. 73
5.5.1 Upgrading the Controller Firmware in Linux............................................................................................................73
5.5.2 Upgrading the Controller Firmware in Windows......................................................................................................75
5.5.3 Upgrading the Controller Firmware in ESXi............................................................................................................ 76
5.6 Querying Health Status.................................................................................................................................................77
5.7 Information Collection................................................................................................................................................. 77
5.10 Common Faults...........................................................................................................................................................82
5.10.1 Hardware Connection Faults or Other Faults.......................................................................................................... 82
5.10.2 Disk Identification Faults or Other Faults............................................................................................................... 82
5.10.3 Disk Internal Faults or Other Faults........................................................................................................................ 82
5.11 Indicator Status Descriptions......................................................................................................................................85
5.11.1 ES3000 SSD Disk Indicator State Descriptions...................................................................................................... 85
5.11.2 ES3000 SSD Card Indicator State Descriptions......................................................................................................86
5.12 Removing an ES3000 V3........................................................................................................................................... 86
6.1.1 Querying the SSD List...............................................................................................................................................94
6.1.2 Querying Basic Information About a Device............................................................................................................ 95
6.1.3 Querying the SMART Information About a Device..................................................................................................96
6.1.4 Querying Advanced Information of a Device........................................................................................................... 99
6.2 Querying, Upgrading, and Activating Firmware........................................................................................................101
6.2.1 Querying the Firmware Version of an SSD............................................................................................................. 101
6.2.2 Upgrading the Firmware of an SSD........................................................................................................................ 102
6.2.3 Activating the Firmware of an SSD........................................................................................................................ 103
6.3 Querying and Setting the Capacity.............................................................................................................................104
6.3.1 Querying the Capacity of an SSD............................................................................................................................104
6.3.2 Setting the Capacity of an SSD............................................................................................................................... 105
6.4.1 Formatting a Logical Disk.......................................................................................................................................107
6.4.2 Formatting an SSD.................................................................................................................................................. 108
6.5 Safely Erasing User Data of an SSD.......................................................................................................................... 110
6.6 Querying and Setting the Power Consumption Level................................................................................................ 112
6.6.1 Querying the Power Consumption Level of an SSD............................................................................................... 112
6.6.2 Setting the Power Consumption Level of an SSD...................................................................................................112
6.7.1 Obtaining Logs of a Device..................................................................................................................................... 113
6.7.2 Obtaining All Logs of a Device At a Time..............................................................................................................114
6.8 Querying and Setting Temperature Thresholds.......................................................................................................... 115
6.8.1 Querying the Temperature Information About a Device......................................................................................... 115
6.8.2 Setting the Temperature Thresholds of a Device..................................................................................................... 117
6.9 Querying and Setting the Write Mode........................................................................................................................119
6.9.1 Querying the Write Mode of an SSD.......................................................................................................................119
6.9.2 Setting the Write Mode of an SSD.......................................................................................................................... 119
6.10 Querying the Diagnosis Result of a Specified SSD................................................................................................. 120
6.11 Querying the Electronic Label Information About an SSD......................................................................................122
6.12 Recovering Data for an SSD.................................................................................................................................... 122
6.13 Querying and Configuring Namespaces...................................................................................................................123
6.13.1 Querying the Namespace Distribution of an SSD................................................................................................. 123
6.13.2 Creating a Namespace for an SSD........................................................................................................................ 124
6.13.3 Attaching a Namespace to an NVMe Controller...................................................................................................125
6.13.4 Detaching a Namespace from an NVMe Controller..............................................................................................126
6.13.5 Deleting a Namespace of an SSD..........................................................................................................................128
6.13.6 Setting the Number of Namespaces for an SSD....................................................................................................129
6.14 Querying or Setting the Atomic Write Status...........................................................................................................130
6.14.1 Querying the Atomic Write Status of a Specified SSD.........................................................................................130
6.14.2 Setting the Atomic Write Status for a Specified SSD........................................................................................... 131
6.15 Querying Historical Amount of Written Data.......................................................................................................... 131
A.5 Supported Set Feature Commands.............................................................................................................................146
A.6.1.1 Obtaining the Enablement Status of User Functions...........................................................................................149
A.6.1.3 Obtaining SSD ID Parameters............................................................................................................................. 152
A.6.1.4 Obtaining the Enablement Status of Functions................................................................................................... 154
A.6.1.5 Querying the Maximum Available Capacity of the SSD.....................................................................................155
A.6.1.6 Obtaining the Vendor Log Length....................................................................................................................... 156
A.6.1.7 Querying the PCB Version...................................................................................................................................156
A.6.1.9 Obtaining the DIEID of a Chip............................................................................................................................157
A.6.1.11 Obtaining the Number of SRIOV VFs...............................................................................................................161
A.6.1.12 Querying the Average DWPD........................................................................................................................... 161
A.6.2.5 Configuring the NN Value................................................................................................................................... 165
A.6.2.7 Configuring the Number of SRIOV VFs.............................................................................................................167
B Out-of-Band Management...................................................................................................... 168
B.3 Temperature Register................................................................................................................................................. 173
C SNMP Function.........................................................................................................................175
C.2 Configuring the SNMP Function in Windows...........................................................................................................176
C.3 Configuring the SNMP Function in Linux................................................................................................................ 176
G.1.2 Making Debugging Preparations............................................................................................................................ 197
G.2 Getting Help from Huawei Support Website............................................................................................................. 197
This topic describes the safety precautions to be observed when you install and maintain
devices.
1 Safety
1 Safety
1.1 General Safety Notice
This topic describes the safety precautions you must take before installing or maintaining
Huawei equipment.
1.2 Labels on Devices
This topic describes the warning labels, grounding labels, and electrostatic discharge (ESD)
labels on devices.
1.3 Electrical Safety
This topic describes safety notice about high voltage, thunderstorm, high electrical leakage,
power cable, fuse, electrostatic discharge.
1.1 General Safety Notice
This topic describes the safety precautions you must take before installing or maintaining
Huawei equipment.
Overview
lTo ensure safety of humans and the equipment, pay attention to the safety symbols on the
equipment and all the safety instructions in this document.
lThe "NOTE", "CAUTION", and "WARNING" marks in other documents do not
represent all the safety instructions. They are only supplements to the safety instructions.
Local Safety Regulations
이 기기는 업무용 환경에서 사용할 목적으로 적합성평가를 받은 기기로서가정용 환경
에서 사용하는 경우 전파간섭의 우려가 있습니다.
When operating Huawei equipment, you must follow the local laws and regulations. The
safety instructions in this document are only supplements to the local laws and regulations.
wrong operations may cause
device damage or human
injury.
External groundingThis label indicates
grounding of external
devices. The terminals of
the grounding cable are
connected to different
devices. This ensures
normal running of the
devices and the safety of the
operator.
Internal groundingThis label indicates
grounding of internal
devices. The terminals of
the grounding cable are
connected to different
components of the same
device. This ensures normal
running of the devices and
the safety of the operator.
1.3 Electrical Safety
This topic describes safety notice about high voltage, thunderstorm, high electrical leakage,
power cable, fuse, electrostatic discharge.
ESD-Preventive LabelThis label indicates an static
sensitive area. Do not touch
the device with your hands.
When operating the device
within this area, take
electrostatic discharge
(ESD)-preventive measures.
For example, wear an ESDpreventive wrist strap.
l The high voltage power supply provides power for the device operation. Direct or indirect
contact (through damp objects) with high voltage and AC mains supply may result in fatal
danger.
l Non-standard and improper high voltage operations may result in fire and electric shock.
Thunderstorm
Do not perform any operation, including high voltage and AC operations, on a steel tower or
mast during a thunderstorm.
1 Safety
High Electrical Leakage
Ground the device before powering it on. Otherwise, personal injury or device damage may
be caused by high leakage current.
If a "high electrical leakage" tag is present on the power terminal of the device, you must
ground the device before powering it on.
Power Cable
Do not install or remove power cables when the device is on. Transient contact between the
core of the power cable and the conductor may generate electric arcs or sparks, which may
cause fire or hurt human eyes.
lBefore installing or removing the power cable, turn off the power switch.
lBefore connecting a power cable, check that the label on the power cable is correct.
Fuse
If a fuse is to be replaced, the new fuse must be of the same type and specifications.
The static electricity generated by human bodies may damage the electrostatic-sensitive
components on boards, for example, the large-scale integrated (LSI) circuits.
Human body movement, friction between human bodies and clothes, friction between shoes
and floors, or handling of plastic articles causes static electromagnetic fields on human
bodies. These static electromagnetic fields cannot be eliminated until the static is discharged.
To prevent electrostatic-sensitive components from being damaged by the static on human
bodies, you must wear a well-grounded ESD wrist strap when touching the device or handling
boards or application-specific integrated circuits (ASICs).
The ES3000 V3 introduced in this document includes two types of products: ES3000 V3
NVMe PCIe SSDs and ES3000 V3 NVMe PCIe SSD cards. V100R003C10 includes ES3000
V3 NVMe PCIe SSDs. ES3500P V3 and ES3600P V3 are available. V100R003C20 includes
ES3000 V3 NVMe PCIe SSD cards. The ES3600C V3 series is available. V100R003C50
includes ES3000 V3 NVMe PCIe SSDs and NVMePCIe SSD cards. The ES3620P V3 series
is available for NVMe PCIe SSDs and the ES3620C V3 series is available for NVMe PCIe
SSD cards.
2.1 Security
This section describes the information security features of the ES3000 V3.
2.2 Overview
This section describes the ES3000 V3 appearance and standards.
2.3 Features
This section describes the features and technical specifications of the ES3000 V3.
2.4 Specifications
This section describes the specifications of the ES3000 V3.
2.5 System Requirements
This section describes the ES3000 V3 requirements for server software and hardware.
2.1 Security
This section describes the information security features of the ES3000 V3.
Huawei is committed to ensuring stability and security of customer networks and services.
As a storage device within a server or storage host, the ES3000 V3 provides the following
security features:
– In Linux, only administrators have the permission to install and uninstall the driver
– In Windows and ESXi, only administrators or administrator group members have
lOperation logs: The settings performed on the ES3000 V3 are recorded.
– In Linux, only administrators have the permission to perform operations on the
– In Windows and ESXi, only administrators and administrator group members have
lSecurity maintenance: The ES3000 V3 provides a data clearance tool that helps you
delete all user data from the devices to be repaired.
lFirmware upgrade: The upgrade tool verifies the integrity of the ES3000 V3 firmware
upgrade file to ensure that the upgrade is successful.
NOTE
To use the management tool, obtain the administrator rights. For example, the Windows administrator
group must run as administrator.
2 Getting to Know the ES3000 V3
and tool packages, and use management tools.
the permission to install and uninstall the driver and tool packages, and use
management tools.
ES3000 V3 and view operation logs.
the permission to perform operations on the ES3000 V3 and view operation logs.
2.2 Overview
This section describes the ES3000 V3 appearance and standards.
Two products are included: ES3000 V3 NVMe PCIe SSD disk and ES3000 V3 NVMe PCIe
SSD card. The disk consists of the ES3500P V3, ES3600P V3, and ES3620P V3 series. The
card consists of the ES3600C V3 and ES3620C V3 series. The ES3000 V3 meets the
requirements for high input/output operations per second (IOPS), high reliability, high
bandwidth, and large data storage capacity. It applies to services with frequent random read
and write operations, such as search, cache, and databases.
lThe ES3000 V3 NVMe PCIe SSD disk is a 2.5-inch PCIe 3.0 x 4 SSD disk that uses the
HiSilicon Hi1812 chip and complies with the SFF-8639 standard. It can be installed in
universal servers, such as rack servers.
Figure 2-1 shows the appearance of the ES3000 V3 NVMe PCIe SSD disk.
The label on an ES3000 V3 NVMe PCIe SSD provides the World Wide Name (WWN)
and serial number (S/N).
A WWN uniquely identifies an ES3000 V3 NVMe PCIe SSD and is a string generated
from the MAC address. A WWN is required when you apply for technical support from
Huawei.
An example S/N is 031YSW10G3000001. Figure 2-2 describes the S/N format.
Figure 2-2 Example S/N
2 Getting to Know the ES3000 V3
No.
Description
1Indicates the material identification code
(6 characters).
2Indicates the vendor code (two
characters).
3Indicates the year and month (two
characters).
4Indicates the serial number (six digits).
lThe ES3000 V3 NVMe PCIe SSD card is a standard high-height, half-length PCIe 3.0 x
4 card. It can be installed in universal servers, such as rack servers.
Figure 2-3 shows the appearance of the ES3000 V3 NVMe PCIe SSD card.
– Advanced flash access technology: combines the read retry and adaptive read
– Data inspection technology: periodically inspects data and prevents errors.
– Power-off protection: prevents disk data loss when a power failure occurs on the
lProvides multiple maintenance and management tools with comprehensive functions and
high performance.
– Provides in-band online upgrades to facilitate routine maintenance.
– Provides device information in a centralized manner, including the types, capacities,
– Supports log query for querying device health status.
– Provides the manufacture dates and serial numbers to facilitate asset management.
2 Getting to Know the ES3000 V3
correction capability than that required by flash chips and ensures device reliability.
can be restored if an error occurs in a channel.
from channel failures.
and prolongs the device service life.
technologies of flash chips and ensures data validity.
server.
versions, remaining service life, and health status.
2.4 Specifications
This section describes the specifications of the ES3000 V3.
The ES3000 V3 comes in two form factors: disk and card. The disk consists of the ES3500P
V3, ES3600P V3 and ES3620P V3 series. The card consists of the ES3600C V3 and
ES3620C V3 series.
The ES3000 V3 driver version needs to have an I/O timeout period of 30 seconds or more.
The default power consumption level 0 ensures optimal performance. A non-default power
consumption level is not recommended.
2.4.1 ES3500P V3 Specifications
Figure 2-4 shows the nameplates for the ES3500P V3 series.
lFor details about the OS types and versions supported by the ES3000 V3, visit Server
Compatibility Checker, find the Compatibility List of the corresponding server.
lOSs listed in this section support common I/O services. To obtain the list of OSs that
support hot plug, see 4.1 OSs Supporting Hot Plug. To obtain the list of OSs that can be
installed on the ES3000 V3, see F Installing an OS on the ES3000 V3.
This section describes the process for installing and configuring the ES3000 V3.
3 Installation and Configuration
If the ES3000 V3 exceeds the overtemperature threshold, handle the problem promptly;
otherwise, management operations on the SSD may fail. For details about the command for
querying temperature information, see 6.8.1 Querying the Temperature Information About
a Device.
3.1 Installation and Configuration Process
The installation and configuration process includes the overall procedures for installing and
configuring the ES3000 V3. You can learn about ES3000 V3 installation and configuration
logic.
3.2 Installing ES3000 V3
This topic describes how to install the ES3000 V3.
3.3 Driver Information
This section describes how to obtain the ES3000 V3 software package.
3.4 Verifying the Upgrade Package Integrity
Verify that the obtained upgrade package is consistent with the original one at the website
http://support.huawei.com/enterprise.
3.5 Transferring Files by Using WinSCP
This section describes how to transfer files by using WinSCP. You can also transfer files by
using other software.
3.6 Installing the Driver
This section describes how to install the ES3000 V3 driver in different operating systems
(OSs). The ES3500P V3, ES3600P V3, ES3620P V3, ES3600C V3, and ES3620C V3 series
use the same drivers and firmware.
3.7 Installing the Tool Package
This section describes how to install the tool package in Linux, Windows, and ESXi operating
systems (OSs).
The installation and configuration process includes the overall procedures for installing and
configuring the ES3000 V3. You can learn about ES3000 V3 installation and configuration
logic.
the flowchart for installing and configuring ES3000 V3 is shown in Figure 3-1.
Figure 3-1 Installation and configuration flowchart
Start
Installing ES3000 V3
Drive Information
3 Installation and Configuration
Verifying the Upgrade
Package Integrity
Installing the Driver
Installing the Tool
Package
End
3.2 Installing ES3000 V3
This topic describes how to install the ES3000 V3.
Operation Scenario
lThe method of installing the ES3000 V3 NVMe PCIe SSD disk is the same as the
method of installing a common hard disk. For details, see Installing the ES3000 V3
NVMe PCIe SSD Disk.
lIf the PCIe card slots are on a riser card, the ES3000 V3 NVMe PCIe SSD card needs to
be installed on the riser card. For details, see Installing the ES3000 V3 NVMe PCIe
SSD card on a Riser Card.
lIf the PCIe card slots are on the mainboard, the ES3000 V3 NVMe PCIe SSD card needs
to be installed on the mainboard. For details, see Installing the ES3000 V3 NVMe PCIe
lStop all services on the server and back up data.
lUnpack and inspect the devices.
Check that the items shipped are complete and intact based on the following list:
– ES3000 V3
– Quick Start Guide
– Warranty card
lTools
– ESD gloves
Pay attention to the following in Linux:
3 Installation and Configuration
Used to prevent ESD damage when you insert, remove, or hold the ES3000 V3 or a
precision device.
Procedure
l Do not perform direct read or write operations on a raw SSD to avoid processing the
wrong SSD due to a changed drive letter. Restarting the server, installing or uninstalling
the SSD driver, inserting and removing the SSD may change the SSD drive letter.
l If you have to perform direct read or write operations on a raw SSD, use the hioadm info
command to check the SSD information and confirm the drive letter through the SSD SN.
l It is recommended that you use the mount command to mount the SSD partitions to a
specified path before performing read and write operations. To ensure normal release of
system resources, use the unmount command to cancel the mounted SSD partitions before
installing or uninstalling the driver, and inserting or removing the SSD.
l You can also add information to the /etc/fstab file so that SSD partitions are automatically
mounted during system startup, driver installation and uninstallation, and SSD insertion
and removal. For details, run the man fstab command to view help information. After
enabling the automatic mounting of SSD partitions, you do not need to run the umount
command before installing or uninstalling the driver, and inserting or removing the SSD.
lInstall the ES3000 V3 NVMe PCIe SSD.
a.Wear ESD gloves.
b.Take the ES3000 V3 out of the ESD bag. Check whether a 2.5-inch or 3.5-inch hard
disk tray is used.
nFor a 2.5-inch hard disk tray, go to c.
nFor a 3.5-inch hard disk tray, go to e.
c.Place the ES3000 V3 into the hard disk tray. See step (1) in Figure 3-2.
d.Use four screws to secure the ES3000 V3 to the hard disk tray. See step (2) in
b.Turn off the power to the server and remove the chassis cover.
c.Hold the upper edge of the ES3000 V3, align its connecting part with the PCIe slot,
3 Installation and Configuration
and vertically insert the ES3000 V3 downwards into the PCIe slot. See Figure 3-2.
Figure 3-8 Installing the ES3000 V3 on the mainboard
d.Turn on the power to the server.
----End
Follow-up Procedure
After the ES3000 V3 is connected to power, the startup process takes about 30 seconds.
If the active indicator associated with the ES3000 V3 NVMe PCIe SSD is on and the fault
indicator is off, the SSD hardware is installed successfully.
If the green indicator (active indicator) on the ES3000 V3 NVMe PCIe SSD is on and the
orange indicator (fault indicator) is off, the SSD hardware is installed successfully.
3.3 Driver Information
This section describes how to obtain the ES3000 V3 software package.
Confirm the scenario before downloading the driver.
lIf the server uses only ES3000 V3 NVMe PCIe SSD disks and does not use SSDs
provided by other vendors. You can use either the NVMe driver integrated in the OS or
that provided by Huawei. For details about how to install Huawei's NVMe driver, see 3.6
lIf the server running Linux uses both ES3000 V3 NVMe PCIe SSD disks and SSDs
provided by other vendors, use the NVMe driver integrated in the OS and you do not
need to install Huawei's NVMe driver.
lIf Huawei's NVMe driver has been installed in Linux and you need to use SSDs provided
by other vendors, uninstall Huawei's NVMe driver.
lFor Windows Server 2008 R2 or Windows Server 2012, if the KB2990941 patch has
been installed, the OS is integrated with the NVMe driver. To install Huawei's NVMe
driver, uninstall the KB2990941 patch first. For details, see 3.6.2 Installing the ES3000
V3 Driver in Windows.
lThe following OSs are also integrated with the NVMe driver:
– Windows Server 2012 R2
– ESXi 6.0
– RHEL 6.5 or later
– CentOS 6.5 or later
– OEL 6.5 or later
– Ubuntu 14.04 or later
– SLES 11 SP4 or later
3 Installation and Configuration
You can download drivers as follows: log in to Huawei Enterprise support website http://
support.huawei.com/enterprise, choose Select a Product to Get Support > IT > Server >
TaiShan > ES3000 V3, click Downloads, and download the required software package. The
l If a key file was not selected during the first login, a warning Continue connecting and add host
l By default, the C:\Documents and Settings\Administrator\My Documents directory of the local
Step 4 In the right pane, choose a directory of the remote host for storing files, for example, /root/
firmware.
Step 5 In the left pane, select a directory of the local PC for storing files, for example E:\Software,
and then select the file to be transferred.
Step 6 Choose File > Copy.
The Copy dialog box is displayed.
Step 7 Confirm the file to be copied and the directory of the remote host, and then click Copy.
The system starts to copy the file from the local PC to the remote host.
----End
3 Installation and Configuration
key to cache is displayed. Click Yes. The WinSCP file transfer page is displayed.
PC is opened in the left pane, and the /root directory of the remote host is opened in the right pane.
3.6 Installing the Driver
This section describes how to install the ES3000 V3 driver in different operating systems
(OSs). The ES3500P V3, ES3600P V3, ES3620P V3, ES3600C V3, and ES3620C V3 series
use the same drivers and firmware.
3.6.1 Installing the ES3000 V3 Driver in Linux
Operation Scenario
If you decide to use Huawei's NVMe driver after reading 3.3 Driver Information, install it
by referring to this section before using the ES3000 V3 for the first time.
If you install multiple ES3000 V3s on a server, you need to install the driver only once.
NOTE
The Linux driver package naming rules are as follows:
lRHEL, CentOS, or OEL driver package name: kmod-hiodriver-Driver version-Supported kernel
version.System distributor.Hardware platform.rpm, such as kmod-
hiodriver-3.3.5.2-3.10.0_123.el7.centos.x86_64.rpm, kmodhiodriver-3.3.5.2-3.10.0_123.el7.redhat.x86_64.rpm, or kmodhiodriver-3.3.5.2-3.10.0_123.el7.oracle.x86_64.rpm.
Before installing the ES3000 V3 driver, check that:
lYou have correctly installed the ES3000 V3 on the server.
lYou have downloaded the ES3000 V3 driver package to the server, and verified the
package integrity.
lYou have uploaded the driver package to a directory (for example, /home) on the server
by using WinSCP.
Procedure
Step 1 Log in to the OS as an administrator.
Step 2 Go to the directory that stores the ES3000 V3 driver package, for example, /home.
Step 3 Run the installation command based on the OS type.
lFor RHEL, CentOS, OEL, SLES, or UVP, run rpm -ivh driver package name.
An example package name for CentOS is rpm -ivh kmod-hiodriver-3.3.5.3-2.6.32_431.el6.centos.x86_64.rpm.
lFor Ubuntu or Debian, run dpkg -i driver package name.
An example package name for Ubuntu is dpkg -ihiodriver-3.3.5.3-3.19.0_15_generic.ubuntu.amd64.deb.
3 Installation and Configuration
NOTE
– If the CPU hardware capabilities are insufficient for processing high-speed I/O services of NVMe
devices during interruption, it is recommended that you configure the NVMe driver to work in
threaded_irq mode before installing it. The configuration method is as follows:
1. Run the vim /etc/modprobe.d/nvme.conf command to create or open the configuration file for
editing.
2. Enter i.
3. In the configuration file, change the value of options nvme use_threaded_interrupts to 1:
options nvme use_threaded_interrupts=1
4. Press Esc, enter :wq, and press Enter to save the edits.
5. Run the chmod +x /etc/modprobe.d/nvme.conf command to change the permission onnvme.conf.
– If the NVMe driver works in threaded_irq mode, the I/O latency increases: Both the 4 KB read
latency and write latency increase by 5 μs.
Step 4 Check whether the following message indicating an incorrect installation package is
displayed.
Error: The installing package does not match the current OS. Please execute
command: rpm -e kmod-hiodriver to uninstall the installing rpm.
lIf yes, go to Step 5.
lIf no, go to Step 6.
Step 5 Uninstall the installed package as prompted. Upload the correct driver package for the OS to
the server and perform Step 2 again to install the driver.
Step 6 Check whether the following message is displayed. The message indicates that the original
NVMe driver fails to be uninstalled during the installation.
Warning: fail to uninstall the old nvme kernel module. Please uninstall the old
nvme kernel module manually or reboot the system.
l For RHEL 6, CentOs 6, or SLES 12, you can add IRQBALANCE_ARGS="--hintpolicy=exact" to the
end of the /etc/sysconfig/irqbalance file content to better balance interrupts.
l To configure the irqbalance service in other OSs, refer to documents related to the OSs.
If the OS cannot find the service, it indicates that the OS does not use the irqbalance service
for balance interrupts. If the command can be run, check whether errors are reported after
running the command for restarting the irqbalance service.
lIf yes, go to Step 15.
lIf no, no further action is required.
Step 15 Contact Huawei technical support for help.
NOTE
If the ES3000 V3 hiodriver is used, certain operating systems such as SUSE Linux will record the
module verification failed error in dmesg logs. This error message is a notification indicating that an
operating system detects a third-party driver with an unmatched signature. It does not affect services.
For detailed reasons and solutions, see Why the "module verification failed " Message Is Displayed
When ES3000 V3 PCIe SSDs Use Huawei-developed SUSE NVMe Drivers.
3 Installation and Configuration
----End
3.6.2 Installing the ES3000 V3 Driver in Windows
Operation Scenario
If you decide to use Huawei's NVMe driver after reading 3.3 Driver Information, install it
by referring to this section before using the ES3000 V3 for the first time.
NOTE
l If you install multiple ES3000 V3s on a server, you need to install the driver only once.
l The ES3000 V3 tool is incompatible with the NVMe driver built in the Windows OS. Ensure that
you have installed Huawei's NVMe driver before using the tool.
l To install Windows on the ES3000 V3, see F Installing an OS on the ES3000 V3.
Preparations
Before installing the ES3000 V3 driver, check that:
lYou have correctly installed the ES3000 V3 on the server.
lYou have downloaded the driver package and verified its integrity. For details, see 3.4
Verifying the Upgrade Package Integrity.
lYou have uploaded the driver package to the server by using WinSCP or other software.
Procedure
Select an operation based on the OS type.
lFor Windows Server 2012 R2, go to 8.
lFor Windows Server 2008 R2 or Windows Server 2012, go to 1.
Check whether the SSD driver is provided by the OS.
7Right-click the KB2990941 patch in the Microsoft Windows column and choose
Uninstall from the shortcut menu.
Install the driver.
8Double-click the driver installation file hiodriver_v3.3.5.2_2008R2_x84_64.msi.
There are three driver installation file types for three Windows versions. *.*.*.* indicates the version
number. This procedure uses hiodriver_v3.3.5.2_2008R2_x84_64.msi as an example.
– hiodriver_v*.*.*.*_2008R2_x84_64.msi
– hiodriver_v*.*.*.*_2012_x84_64.msi
– hiodriver_v*.*.*.*_2012R2_x84_64.msi
The installation interface is displayed, as shown in Figure 3-13.
– If yes, the driver has been successfully installed.
– If no, contact Huawei technical support.
Figure 3-19 Expanding Disk drives
----End
3.6.3 Installing the ES3000 V3 Driver in ESXi
Operation Scenario
3 Installation and Configuration
Preparations
Procedure
Step 1 Log in to the OS as an administrator or a member of the administrator group.
Step 2 Install the ES3000 V3 driver.
You need to install the ES3000 V3 driver on the server before using the ES3000 V3 for the
first time.
NOTE
l If you install multiple ES3000 V3s on a server, you need to install the driver only once.
l To install ESXi on the ES3000 V3, see F Installing an OS on the ES3000 V3.
Before installing the ES3000 V3 driver, check that:
lYou have correctly installed the ES3000 V3 on the server.
lYou have downloaded the ES3000 V3 driver package to the server, and verified the
package integrity.
lYou have uploaded the driver package to the server by using WinSCP or other software.
The following procedure assumes that the driver package is in the /tmp directory, and the
driver package name is hiodriver-3.3.5.2-1OEM.550.0.0.2768847.x86_64.vib.
Run the following command to install the ES3000 V3 driver package:
esxcli software vib install -v driver package in a directory
Step 1 Log in to the operating system (OS) as an administrator.
Step 2 Go to the directory that stores the tool package, for example, /home.
Step 3 Run the installation command based on the OS type.
lFor RHEL, CentOS, OEL, or SLES, run rpm -ivh tool package name.
Example: rpm -ivh hioadm-3.3.5.2-1.x86_64.rpm
lFor Ubuntu or Debian, run dpkg -i tool package name.
Example: dpkg -i hioadm-3.3.5.2-1.amd64.deb
Step 4 Run the following command to obtain help information about the tool:
hioadm -h or hioadm --help
Step 5 Copy linux/tool/ host_info_collect.sh to /opt/hio.
----End
3.7.2 Installing the Tool Package (Windows)
3 Installation and Configuration
Operation Scenario
Install the tool package for managing the ES3000 V3. The ES3000 V3 tool is incompatible
with the NVMe driver built in the Windows OS. Ensure that you have installed Huawei's
NVMe driver before using the tool.
Preparations
lYou have correctly installed the ES3000 V3 on the server.
lYou have downloaded the tool package and verified its integrity.
lYou have uploaded the tool package to the server by using Windows Secure Copy
(WinSCP) or other software.
Procedure
Step 1 Log in to the operating system (OS) as an administrator or administrator group member.
Step 2 Double-click the tool package file hioadm_v3.3.5.4_x86_64.msi.
NOTE
v3.3.5.4 indicates a driver version number. This procedure uses hioadm_v3.3.5.4_x86_64.msi as an example.
The installation interface is displayed, as shown in Figure 3-20.
Ensure that the server and BIOS supports hot plug.
Only SSDs for data storage can be hot-plugged. Do not hot-plug SSDs running OSs.
The following OSs support hot plug of the ES3000 V3:
lMainstream Linux OSs:
– Red Hat: 6.6, 6.7, 7.0, 7.1, 7.2
– CentOS: 6.6, 6.7, 6.8, 7.0, 7.1, 7.2
– SLES: 11SP4, 12, 12 SP1
– Oracle: OEL 7.0, OEL 7.1, OEL 7.2
– Ubuntu: 14.04 LTS, 15.04
– SUSE: 12 SP1
lMainstream Windows OSs:
– Windows Server 2008 R2 64-Bit
– Windows Server 2012 64-Bit
– Windows Server 2012 R2 64-Bit
4 Hot Plug
4.2 Orderly Hot Plug
You can insert the ES3000 V3 disks to running servers. For Linux and Windows, notify the
OS by referring to this section before hot removing the ES3000 V3 disk. Currently ESXi does
not support orderly hot removal of the ES3000 V3.
4.2.1 Orderly Hot Plug of a Disk in Linux OS
Operation Scenario
In Linux, perform the operations described in this topic before performing an orderly hot plug
of an ES3000 V3 disk.
Preparations
You have correctly installed the ES3000 V3 disk on the server.
Configuring Linux kernel
In Linux (such as Red Hat7.0), hot plug of the ES3000 V3 NVMe PCIe SSD disk will cause
unmatched maximum payload size, I/O write errors, and other issues. This is because Linux
does not fully support hot plug. To avoid this issue, make changes to the Linux kernel file.
The changes vary with the Linux OS type.
Perform an operation based on the OS type:
lRed Hat (7.0, 7.1, 7.2) and CentOS (7.0, 7.1, 7.2) => Go to Red Hat (7.0, 7.1, 7.2) and
Between the added content and its preceding content, a space is required and no line
feed is allowed.
…(Some code omitted.)
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Oracle Linux Server, with Linux 3.10.0-123.el7.x86_64' -class oracle --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option 'gnulinux-3.10.0-123.el7.x86_64-advancedeba3dd96-8be3-46ce-a8d9-21699e3fbedb' {
load_video
e.Press Esc, enter :wq, and press Enter to save the edits.
f.Restart the OS for the settings to take effect.
g.Go to Notifying the OS.
lSLES 12
a.Log in to the operating system (OS) as an administrator.
b.Run the vim /boot/grub2/grub.cfg command to open the boot configuration file.
c.Enter i.
d.In the boot configuration file, add pciehp.pciehp_force=1 pci=pcie_bus_perf to
4 Hot Plug
if [ "x$default" = 'Oracle Linux Server, with Unbreakable Enterprise
Kernel 3.8.13-35.3.1.el7uek.x86_64' ]; then default='Advanced options
for Oracle Linux Server>Oracle Linux Server, with Unbreakable Enterprise
Kernel 3.8.13-35.3.1.el7uek.x86_64'; fi;
### END /etc/grub.d/10_linux ###
…(Some code omitted.)
the boldface part shown in the following:
Between the added content and its preceding content, a space is required and no line
feed is allowed.
…(Some code omitted.)
### BEGIN /etc/grub.d/10_linux ###
menuentry 'SLES12' --class sles12 --class gnu-linux --class gnu --class
os $menuentry_id_option 'gnulinux-simple-dcbfdecb-bcd9-4003-ba51a95c7e31c56e' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod btrfs
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'
dcbfdecb-bcd9-4003-ba51-a95c7e31c56e
else
search --no-floppy --fs-uuid --set=root dcbfdecb-bcd9-4003ba51-a95c7e31c56e
fi
echo 'Loading Linux 3.12.28-4-default ...'
linux /boot/vmlinuz-3.12.28-4-default root=UUID=dcbfdecbbcd9-4003-ba51-a95c7e31c56e ${extra_cmdline} resume=/dev/disk/by-uuid/
9a586421-38ef-43bb-9209-afe5eede22e3 splash=silent quiet
crashkernel=216M-:108M showopts pciehp.pciehp_force=1 pci=pcie_bus_perf
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-3.12.28-4-default
}
submenu 'Advanced options for SLES12' --hotkey=1 $menuentry_id_option
'gnulinux-advanced-dcbfdecb-bcd9-4003-ba51-a95c7e31c56e' {
menuentry 'SLES12, with Linux 3.12.28-4-default' --hotkey=2 -class sles12 --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-3.12.28-4-default-advanced-dcbfdecbbcd9-4003-ba51-a95c7e31c56e' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod btrfs
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hintbios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 -hint='hd0,msdos2' dcbfdecb-bcd9-4003-ba51-a95c7e31c56e
else
search --no-floppy --fs-uuid --set=root dcbfdecbbcd9-4003-ba51-a95c7e31c56e
fi
echo 'Loading Linux 3.12.28-4-default ...'
linux /boot/vmlinuz-3.12.28-4-default
root=UUID=dcbfdecb-bcd9-4003-ba51-a95c7e31c56e ${extra_cmdline}
resume=/dev/disk/by-uuid/9a586421-38ef-43bb-9209-afe5eede22e3
splash=silent quiet crashkernel=216M-:108M showopts
pciehp.pciehp_force=1 pci=pcie_bus_perf
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-3.12.28-4-default
}
menuentry 'SLES12, with Linux 3.12.28-4-default (recovery mode)'
--hotkey=3 --class sles12 --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-3.12.28-4-default-recovery-dcbfdecbbcd9-4003-ba51-a95c7e31c56e' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod btrfs
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hintbios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 -hint='hd0,msdos2' dcbfdecb-bcd9-4003-ba51-a95c7e31c56e
else
search --no-floppy --fs-uuid --set=root dcbfdecbbcd9-4003-ba51-a95c7e31c56e
fi
echo 'Loading Linux 3.12.28-4-default ...'
linux /boot/vmlinuz-3.12.28-4-default
root=UUID=dcbfdecb-bcd9-4003-ba51-a95c7e31c56e ${extra_cmdline}
showopts apm=off noresume edd=off powersaved=off nohz=off highres=off
processor.max_cstate=1 nomodeset x11failsafe crashkernel=216M-:108M
i.Press Esc, enter :wq, and press Enter to save the edits.
j.Restart the OS for the settings to take effect.
k.Go to Notifying the OS.
lUbuntu (14.04 or 15.04)
The following procedure uses Ubuntu 14.04 as an example:
a.Log in to the operating system (OS) as an administrator.
b.Run the vim /boot/grub/grub.cfg command to open the boot configuration file.
c.Enter i.
d.In the boot configuration file, add pciehp.pciehp_force=1 pci=pcie_bus_perf to
4 Hot Plug
NOTE
Whether the file content includes "title Xen" depends on whether Xen Hypervisor is selected
during OS installation.
the boldface part shown in the following:
Between the added content and its preceding content, a space is required and no line
feed is allowed.
…(Some code omitted.)
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class
os $menuentry_id_option 'gnulinux-simple-b7889e8e-dbc4-4fe9-bf5cdab9c20a93f8' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 -hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 b7889e8e-dbc4-4fe9bf5c-dab9c20a93f8
else
search --no-floppy --fs-uuid --set=root b7889e8e-dbc4-4fe9-bf5cdab9c20a93f8
fi
Step 4 Click eject in Figure 4-1 and then click eject succeed OK.
If a success message is displayed, you can hot remove the ES3000 V3 disk. If a failure
message indicating the OS is accessing the ES3000 V3 disk, stop related services before
clicking eject again. You can hot remove the ES3000 V3 disk only when a success message is
displayed.
Step 11 Contact Huawei technical support for help.
----End
5.1.2 Uninstalling the Driver in Windows
Operation Scenario
If you want to stop using or replace the ES3000 V3, uninstall its driver first.
5 Maintenance and Upgrade
Procedure
Uninstall the ES3000 V3 driver by following the procedure described in this topic.
Do not uninstall the ES3000 V3 driver by using Device Manager. If you have uninstalled the
ES3000 V3 driver by using Device Manager, you still need to uninstall the driver by
following the procedure described in this topic before installing the driver again. To install the
driver, see 3.6.2 Installing the ES3000 V3 Driver in Windows.
lUninstall the driver by using Control Panel.
a.Log in to the OS as an administrator or a member of the administrator group.
b.Stop the programs that are accessing the ES3000 V3.
c.Choose Start > Control Panel.
The Control Panel window is displayed.
d.Click Uninstall a program.
The Uninstall or change a program window is displayed, as shown in Figure 5-1.
Figure 5-1 Uninstall or change a program
e.Right-click the ES3000 V3 driver, and choose Uninstall/Change from the shortcut
You can upgrade the driver after a new version is released.
The Linux driver package naming rules are as follows:
lRHEL, CentOS, or OEL driver package name: kmod-hiodriver-Driver version-
Supported kernel version.System distributor.Hardware platform.rpm, such as kmod-
hiodriver-3.3.5.2-3.10.0_123.el7.centos.x86_64.rpm, kmodhiodriver-3.3.5.2-3.10.0_123.el7.redhat.x86_64.rpm, or kmodhiodriver-3.3.5.2-3.10.0_123.el7.oracle.x86_64.rpm.
Step 1 Run the hioadm -v command to check whether the tool version is later than 3.3.7.5.
lIf yes, go to Step 3.
lIf no, go to Step 2.
Step 2 Run the following command to uninstall the hioadm tool:
esxcli software vib remove -n hioadm
Step 3 Install the new driver. For details, see 3.6.3 Installing the ES3000 V3 Driver in ESXi.
NOTE
Install the new driver package directly. The system will automatically replace the old driver.
----End
5.3 Uninstalling, and Upgrading the Tool Package
You can download the software package as follows: log in to Huawei Enterprise support
website http://support.huawei.com/enterprise, choose Select a Product to Get Support >
IT > Server > TaiShan > ES3000 V3, click Downloads, and download the required software
package. The software package contains host tools (including hioadm) and Huawei's NVMe
driver.
5.3.1 Uninstalling the Tool Package (Linux)
Operation Scenario
Uninstall the tool package to free up space when ES3000 V3 management is not needed.
Procedure
Step 1 Log in to the operating system (OS) as an administrator.
Step 2 Run the uninstallation command based on the OS type.
lFor RHEL, CentOS, OEL, or SLES, run the rpm -e hioadm command.
lFor Ubuntu or Debian, run the dpkg -r hioadm command.
----End
5.3.2 Uninstalling the Tool Package (Windows)
Operation Scenario
Uninstall the tool package to free up space when ES3000 V3 management is not needed.
Procedure
Step 1 Log in to the operating system (OS) as an administrator or administrator group member.
[root@xenserver-citrix6u2sp1 ~]# rpm -e hiodriver-data-1.0-20170114051700
NOTE: There are some user files under the directory /opt/hio.
If you don't need them, you can delete them manually.
Uninstall ES3000 V3 hiodriver-data-1.0 successfully.
[root@xenserver-citrix6u2sp1 ~]# rpm -e hiodriver-modules-
lStop or exit the ES3000 V3 SSD applications or services, and umount the file system
that uses the SSD device.
lThe firmware upgrade does not damage data on SSDs. However, you are advised to back
up important data on SSDs.
lYou have downloaded the firmware package to the server, and verified the package
integrity.
lYou have uploaded the controller firmware file ES3000V3_FW_2.43.bin to the server.
Procedure
Step 1 Log in to the OS as an administrator.
Step 2 Run the following command to query the SSD controller (such asnvme0) firmware version:
hioadm updatefw -d nvme0
The command output contains the following controller firmware version:
slot version activation
slot1 2.09
slot2 2.10 current
slot3 2.11 next
5 Maintenance and Upgrade
NOTE
The version number to the left of next indicates the version that takes effect after the next reset. The version
number to the left of current indicates the version in use.
Step 3 Access the folder where the controller firmware is stored, for example, /home.
NOTE
You can use an absolute or relative path when upgrading the driver. If you do not perform this step, you must
enter an absolute path in the command in the next step.
Step 4 Run the following command to upgrade the controller firmware.
lMethod 1: hioadm updatefw -d nvme0 -f ES3000V3_FW_2.43.bin, then go to step 5,
6, 7.
lMethod 2: hioadm updatefw -d nvme0 -f ES3000V3_FW_2.43.bin -a 1, go to step 5,
then go to #es3000_user_050/step7 directly.
Step 5 Enter y and press Enter.
Step 6 After the upgrade, run the reboot command to restart the OS.
Step 7 Run the following command to check whether the SSD device controller firmware is
Step 10 Contact Huawei technical support for help.
----End
5.5.3 Upgrading the Controller Firmware in ESXi
Operation Scenario
You can upgrade the controller firmware when a new version is released.
Preparations
Before upgrading the firmware, check that:
lStop or exit the ES3000 V3 SSD applications or services.
lThe firmware upgrade does not damage data on SSDs. However, you are advised to back
up important data on SSDs.
lYou have downloaded the firmware package to the server, and verified the package
integrity.
lYou have uploaded the controller firmware file ES3000V3_FW_2.43.bin to the server.
5 Maintenance and Upgrade
Procedure
Step 1 Log in to the OS as an administrator or a member of the administrator group.
Step 2 Run the following command to query the SSD controller (such asnvme0) firmware version:
Step 3 Navigate to the folder where the controller firmware is stored, for example, /tmp.
Step 4 Upgrade the controller firmware.
hioadm updatefw -d nvme0
The command output contains the following controller firmware version:
slot version activation
1 1.20
2 1.20 next
3 1.20 current
NOTE
The version number to the left of next indicates the version that takes effect after the next reset. The version
number to the left of current indicates the current version in use.
NOTE
You can use an absolute path or a relative path when upgrading the driver. If you do not perform this step, you
must enter an absolute path in the command in the next step.
hioadm updatefw -d nvme0 -f ES3000V3_FW_2.43.bin
Step 5 Enter y and press Enter.
Step 6 After the upgrade, run the reboot command to restart the OS.
Step 7 Run the following command to check whether the SSD device controller firmware is
maximum capacity : 1.6TB
current capacity : 1.6TB
volatile write cache : Enable
serial number : 0503023HDCN107C80013
model number : HWE32P430016M00N
firmware version : 2.14
NVMe version : 1.2
device status : healthy
----End
5.7 Information Collection
5.7.1 Collecting SSD Information
Operation Scenario
Collect SSD information when maintaining SSDs.
Procedure
Step 1 Log in to the OS as an administrator or a member in the administrator group.
maximum capacity : 1.6TB
current capacity : 1.6TB
volatile write cache : Enable
serial number : 0503023HDCN107C80013
model number : HWE32P430016M00N
firmware version : 2.14
NVMe version : 1.2
device status : healthy
Step 3 Run the following command to query the SMART information of the SSD controller (such as
nvme0):
hioadm info -d nvme0 –s
5 Maintenance and Upgrade
The command output is similar to the following:
[root@localhost tool]# hioadm info -d nvme0 -s
critical warning : no warning
composite temperature : 308 degrees Kelvin (35 degrees Celsius)
available spare : 100%
available spare threshold : 10%
percentage used : 0%
data units read : 68.8 MB
data units written : 0.0 MB
host read commands : 17748
host write commands : 0
controller busy time : 0 mins
power cycles : 89 times
power on hours : 1164 h
unsafe shutdowns : 35 times
media and data integrity errors: 0
number of error information log entries: 0
warning composite temperature time: 0 min
critical composite temperature time: 0 min
data status : OK
----End
5.7.2 Collecting SSD Logs
Operation Scenario
Collect SSD information when maintaining SSDs.
Procedure
Step 1 Log in to the OS as an administrator or a member in the administrator group.
Step 2 Run the following command to collect the SSD controller (such as nvme0) log information:
hioadm log -d nvme0 -a
The command output shows the log collecting result and file path.
save firmware key log file successed(/opt/hio/nvme0_key.log)
firmware all log saving..........OK
save firmware all log file successed(/opt/hio/nvme0_fw.log)
firmware core dump log saving..........OK
save firmware core dump log file successed(/opt/hio/nvme0_coredump.log)
other log saving..........OK
save other logs file successed(/opt/hio/nvme0_other.log)
logs has been saved.
----End
5.7.3 One-Click Log Collection
Scenario
Collect SSD and system operation logs when maintaining SSD devices.
Prerequisite
You have downloaded the software package from the Software Download tab at http://
support.huawei.com/enterprise (Product Support > Enterprise Data Center > Servers >
Acceleration Component > ES3000 V3.
5 Maintenance and Upgrade
Linux
Step 1 Copy host_info_collect.sh from /linux/tool in the package to /opt/hio.
Step 2 Log in to the OS as an administrator or a member in the administrator group.
Step 3 Run the bash /opt/hio/host_info_collect.sh command.
Step 4 Obtain the log file hostInfoCollect.zip from the /opt/hio directory.
Step 5 (Optional) Delete the log file after use to free disk space.
Windows
Step 1 Copy diagnostic_win.bat from /windows/Windows_Tool in the package to C:\Program Files
Step 2 Log in to the OS as an administrator or a member in the administrator group.
Install the hioadm tool before performing one-click log collection. For details about how to
install the tool, see section 3.7 Installing the Tool Package.
----End
(x86)\hioadm.
Step 3 Double-click diagnostic_win.ba in C:\Program Files (x86)\hioadm\.
Step 4 Obtain all log files from the C:\Program Files (x86)\hioadm\ directory.
Step 5 (Optional) Delete the log file after use to free disk space.
Step 2 Run the following command to securely erase data from the SSD (such as nvme0):
hioadm secure -d nvme0
The warning of the risks of data erasure is displayed.
[root@localhost tool]# hioadm secure -d nvme0
WARNING! The secure operation will clear all data.
WARNING! You have selected the format operation.
Proceed with the secure? (Y|N):
Step 3 After confirming the risks, enter y to start the secure erasure.
The operation result is displayed.
[root@localhost tool]# hioadm secure -d nvme0
WARNING! The secure operation will clear all data.
WARNING! You have selected the format operation.
Proceed with the secure? (Y|N): y
Formatting.... OK
secure operate successed.
Please remove and then install the NVMe driver or reboot the OS.
----End
5 Maintenance and Upgrade
5.9 Querying SSD Lifespans
Scenario
Query the lifespan of an SSD.
Procedure
Step 1 Log in to the OS as an administrator or a member in the administrator group.
Step 2 Run the following command to query the SMART information of the SSD controller (such as
nvme0):
hioadm info -d nvme0 –s
The command output is similar to the following:
[root@localhost tool]# hioadm info -d nvme0 -s
critical warning : no warning
composite temperature : 308 degrees Kelvin (35 degrees Celsius)
available spare : 100%
available spare threshold : 10%
percentage used : 0%
data units read : 68.8 MB
data units written : 0.0 MB
host read commands : 17748
host write commands : 0
controller busy time : 0 mins
power cycles : 89 times
power on hours : 1164 h
unsafe shutdowns : 35 times
media and data integrity errors: 0
number of error information log entries: 0
warning composite temperature time: 0 min
critical composite temperature time: 0 min
data status : OK
Step 3 The percentage used parameter displays the used lifespan percentage of the SSD.
If the value of percentage used exceeds 100%, the SSD lifespan has expired, and Huawei's
warranty service is unavailable. You need to back up data on the SSD as soon as possible and
replace the SSD.
----End
5.10 Common Faults
5.10.1 Hardware Connection Faults or Other Faults
Hardware connection faults are mostly identified by indicators. If the yellow indicator of a
device is on and the green indicator is off 30 seconds after a new disk is installed or during
proper operating, hardware faults occur. See 5.11 Indicator Status Descriptions to identify
the faults.
5 Maintenance and Upgrade
Typical fault causes are as follows:
lThe disk is not securely installed.
lThe disk is installed in a non-NVMe slot.
lA disk hardware port fault occurs.
5.10.2 Disk Identification Faults or Other Faults
Disk identification faults indicate scenarios where the host OS disk manager (for example,
fdisk-l in Linux and the device manager in Windows) cannot properly identify ES3000 SSDs
when hardware connections are correct. If disk identification faults occur, collect all logs. For
details, see 5.7.3 One-Click Log Collection.
Typical fault causes are as follows:
lThe NVMe driver is not installed on the OS.
lOS driver loading fails.
5.10.3 Disk Internal Faults or Other Faults
Disk internal faults indicate scenarios where disk internal alarms occur while the OS can
properly identify disks. If such faults occur, the disks do not function properly or cannot be
used. This topic uses an example to describe how to identify such faults.
Use Instance
Step 1 Determine the disk health status. For details, see 6.1.2 Querying Basic Information About a
maximum capacity : 1.6TB
current capacity : 1.6TB
volatile write cache : Enable
serial number : 0503023HDCN107C80013
model number : HWE32P430016M00N
firmware version : 2.14
NVMe version : 1.2
device status : healthy
device status in the command output indicates the SSD controller health status.
The value healthy indicates that the device is healthy.
The value warning indicates that an exception occurs on the device. For details, see Step 2.
Step 2 Determine the SMART status of the disk. For details, see 6.1.3 Querying the SMART
Information About a Device.
# Query the SMART information of nvme0.
[root@localhost tool]# hioadm info -d nvme0 -s
critical warning : no warning
composite temperature : 308 degrees Kelvin (35 degrees Celsius)
available spare : 100%
available spare threshold : 10%
percentage used : 0%
data units read : 68.8 MB
data units written : 0.0 MB
host read commands : 17748
host write commands : 0
controller busy time : 0 mins
power cycles : 89 times
power on hours : 1164 h
unsafe shutdowns : 35 times
media and data integrity errors: 0
number of error information log entries: 0
warning composite temperature time: 0 min
critical composite temperature time: 0 min
data status : OK
5 Maintenance and Upgrade
Critical Warning: Critical exceptions occur on the device, and emergency handling is
required.
Hot swap: Users are allowed to take out and replace faulty hard disks, PSUs, or cards when the system
is not stopping or the power is not switched off. Surprised hot swap and orderly host swap are
supported. For details, see 4 Hot Plug.
lRemoving an ES3000 V3 NVMe PCIe SSD card
– If PCIe card slots are on a riser card, the SSD card needs to be removed from the
– If PCIe card slots are on the mainboard, the SSD card needs to be removed from the
Preparations
Before removing an ES3000 V3 NVMe PCIe SSD, make the following preparations:
lWear ESD gloves.
Used to prevent ESD damage when you insert, remove, or hold the ES3000 V3 or a
precision device.
lBack up data.
– Stop the access to a hot swappable SSD disk.
– Stop the services on the server and power off the server if you need to remove an
5 Maintenance and Upgrade
NOTE
riser card. For details, see 5.12.3 Removing an ES3000 V3 NVMe PCIe SSD
Card on a Riser Card.
mainboard. For details, see 5.12.4 Removing an ES3000 V3 NVMe PCIe SSD
Card from the Mainboard.
SSD card or a non-hot-swappable SSD disk.
5.12.1 Removing a Non-Hot-Swappable ES3000 V3 NVMe PCIe
SSD Disk
Prerequisites
Wear ESD gloves.
Procedure
Step 1 Determine the position of the disk in the server and power off the server.
Step 2 Press the ejector release button. See (1) in Figure 5-6.