OceanStor 2000, 5000, 5000F, 6000, and 6000F Series V500R007 Kunpeng Installation Guide
OceanStor 2000, 5000, 5000F, 6000, and 6000F Series V500R007 Kunpeng Installation Guide
Series
V500R007 Kunpeng
Installation Guide
Issue 10
Date 2021-10-30
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.
Website: https://e.huawei.com
Purpose
This document describes how to install OceanStor 2000 V5, 5000 V5, 5000F, 6000,
and 6000F V5 series storage systems. It consists of the following parts: precautions
and planning, installation process and preparation, hardware installation, cabling
and checking, system power-on and initialization, and software installation. In
addition to FAQs and cable routing and binding basics, this document also
provides instructions on how to prepare labels and cables as well as how to seek
technical support.
The following table lists the product models that this document is applicable to.
OceanStor 5000 V5 OceanStor 5300 V5, 5500 V5, 5600 V5, and 5800 V5
series
OceanStor 5000F OceanStor 5300F V5, 5500F V5, 5600F V5, and 5800F V5
V5 series
Intended Audience
This document is intended for:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue
contains all changes made in earlier issues.
Issue 10 (2021-10-30)
This issue is the tenth official release.
Issue 09 (2021-09-15)
This issue is the ninth official release.
Issue 08 (2021-06-30)
This issue is the eighth official release.
Issue 07 (2021-01-30)
This issue is the seventh official release.
Issue 06 (2020-11-30)
This issue is the sixth official release.
Issue 05 (2020-09-15)
This issue is the fifth official release.
Issue 04 (2020-04-10)
This issue is the fourth official release.
Issue 03 (2019-12-30)
This issue is the third official release.
Issue 02 (2019-10-30)
This issue is the second official release.
Issue 01 (2019-07-30)
This issue is the first official release.
Contents
5.2.3.3 Clearing the Controllers That Failed to Be Added (Applicable to the OceanStor 6000 and 6000F V5
Series)............................................................................................................................................................................................ 364
5.3 (Optional) Installing and Configuring a Key Management Server................................................................... 370
5.4 (Optional) Installing Other Software on an Application Server........................................................................ 370
5.5 Using SmartKit for Deployment Inspection...............................................................................................................372
6 FAQs....................................................................................................................................... 377
6.1 What Can I Do If Controller Expansion Fails Because the Process Lasts for Over 24 Hours After the
Controllers to Be Added Are Powered On?.......................................................................................................................377
6.2 How Do I Query and Configure the NPIV Function of Switches?..................................................................... 378
6.3 How Do I Create AD Domain Users and Groups on the AD Domain Controller?....................................... 379
6.4 How Can I Import the Windows AD Domain Server's CA Certificate to the Storage System?............... 382
6.5 How Can I Use Self-Signed Certificates to Fix the Privacy Error Displayed When I Attempt to Log In to
DeviceManager?.........................................................................................................................................................................384
6.6 How Do I Check Whether Network Firewall Ports Are Enabled?...................................................................... 388
6.7 What Should I Do If Login to DeviceManager over Internet Explorer Failed?..............................................391
7 Appendix............................................................................................................................... 393
7.1 Installation Tools.................................................................................................................................................................393
7.2 Using SmartKit for Capacity Expansion...................................................................................................................... 394
7.2.1 Using SmartKit for Capacity Expansion (Direct-Connection Network)........................................................395
7.2.2 Using SmartKit for Capacity Expansion (Switched Network)..........................................................................403
7.3 Loop ID and Disk Enclosure ID Naming Rules......................................................................................................... 413
7.3.1 OceanStor 2200 V5........................................................................................................................................................ 413
7.3.2 OceanStor 2600 V5........................................................................................................................................................ 415
7.3.3 OceanStor 5300 V5 and 5300F V5............................................................................................................................ 416
7.3.4 OceanStor 5500 V5, 5600 V5, 5800 V5, 5500F V5, 5600F V5, and 5800F V5............................................417
7.3.5 OceanStor 6800 V5 and 6800F V5............................................................................................................................ 419
7.4 Introduction to an FR42612L Cabinet......................................................................................................................... 422
7.5 Installation Environment Checklist............................................................................................................................... 426
7.6 Checking a Third-Party Cabinet.....................................................................................................................................429
7.7 Using SmartKit to Install UltraPath..............................................................................................................................437
7.8 General Cable Routing Principles.................................................................................................................................. 446
7.9 Cable Routing and Binding Basics................................................................................................................................ 447
7.9.1 Cable Routing and Binding.......................................................................................................................................... 447
7.9.2 Optical Fiber Routing and Bundling......................................................................................................................... 449
7.10 Preparing Cables and Connectors.............................................................................................................................. 452
7.10.1 Preparing Ordinary Network Cables...................................................................................................................... 452
7.10.2 Preparing Shielded Network Cables.......................................................................................................................456
7.10.3 Preparing External Power Cables and Ground Cables with OT Terminals................................................461
7.11 Engineering Label Specifications for Cables........................................................................................................... 464
7.11.1 Introduction to Labels................................................................................................................................................. 465
7.11.2 Usage of Labels............................................................................................................................................................. 467
7.11.3 Filling In Labels............................................................................................................................................................. 468
B Glossary................................................................................................................................. 481
C Acronyms and Abbreviations........................................................................................... 482
Before using this document, read this chapter carefully to ensure that the
document is applicable to your storage device. This document applies to
V500R007 Kunpeng, not V500R007. You can check whether the storage device
version is V500R007 Kunpeng by observing the rear view of a controller enclosure
or querying the version on DeviceManager or the CLI.
● If yes, use this document.
● If no, use the OceanStor 5000, 5000F, 6000, and 6000F Series V500R007
Installation Guide.
For details about how to check the device version, see Checking the Device
Version from the Rear View of a Controller Enclosure, Checking the Device
Version on DeviceManager, and Checking the Device Version on the CLI.
Checking the Device Version from the Rear View of a Controller Enclosure
If the slot layout in the rear view of a controller enclosure is shown as Figure 1-1,
Figure 1-2, Figure 1-3, Figure 1-4, Figure 1-5, Figure 1-6, or Figure 1-7, the
device version is V500R007 Kunpeng.
Figure 1-1 Rear view of an OceanStor 2200 V5 controller enclosure (25 disk slots)
Figure 1-2 Rear view of an OceanStor 2200 V5 controller enclosure (12 disk slots)
Figure 1-6 Rear view of an OceanStor 5500 V5/5500F V5/5600 V5/5600F V5/5800
V5/5800F V5 controller enclosure
NOTE
NOTE
For details about how to log in to the CLI, see 5.1.1.4 Logging In to the CLI.
This chapter provides guidelines for safety operations during activities such as
installation, maintenance, and troubleshooting. The guidelines consist of safety
regulations for both personnel and equipment. You must follow these guidelines
to avoid personal injury and equipment damage.
2.1 Alarm and Safety Symbols
2.2 Safety Precautions for ESD Protection
2.3 Safety Precautions for Laser Protection
2.4 Safety Precautions for Using Fibers
2.5 Safety Precautions for Using Power Cables (Applicable to Japan)
2.6 Safety Precautions for Short Circuit Protection
2.7 Safety Precautions for Operating Equipment
2.8 Safety Precautions for Condensation Prevention
Symbol Description
● Do not wear an ESD wrist strap when powering on the equipment to prevent
an electric shock.
● Do not touch devices with bare hands to prevent damage to the electrostatic
sensitive devices (ESSDs) on the circuit boards.
● The electronic line is prone to electrostatic damage. Wear an ESD wrist strap,
ESD gloves, and ESD clothing when handling disks, especially bare disks. Hold
a disk by its edge.
● Since an ESD wrist strap only prevents static electricity from the body, the ESD
clothing is required to prevent static electricity from clothes.
● Before installing or replacing devices, wear an ESD wrist strap, ESD gloves,
and ESD clothing to protect you and the equipment from static electricity.
● Use special ESD bags to carry or transport device components.
● Personal injury
● Equipment damage
Personal Injury
DANGER
The laser emitted by an optical module is an invisible infrared ray, which may
cause permanent eye injury. Do not look into the optical module during device
maintenance.
Equipment Damage
To prevent equipment damage when you handle the equipment, follow these
precautions:
● When not in use, the optical interfaces on the equipment and fiber connectors
on fiber jumpers must be covered with dust-proof caps.
● After removing a fiber jumper that connects to an optical interface on the
equipment, cover the optical interface and the fiber jumper connector with
dust-proof caps.
● When performing a hardware loopback test by connecting a fiber jumper to
an optical interface, add an attenuator to prevent the risk of damage to the
optical module caused by excessively strong optical power.
● When using the Optical Time Domain Reflectometer (OTDR), disconnect the
fiber jumper between the peer equipment and the local equipment to avoid
damage to the optical module caused by excessively strong optical power.
● Unless necessary, do not remove or insert the modules connecting to fibers.
DANGER
The laser beam on an optical interface board or from a fiber may cause eye injury.
Do not look into optical interfaces or fiber connectors during installation and
maintenance.
Replacing Fibers
Use dust-proof caps to cap the connectors of the fibers that are not in use.
NOTICE
● Do not place tools on air intake boards of cabinets. Otherwise, a short circuit
may occur.
● Do not drop screws into a cabinet or the equipment. Otherwise, a short circuit
may occur.
DANGER
● Before checking device installation and cable connections, ensure that the
system power supply is switched off. Otherwise, incorrect or loose cable
connections may result in personal injury or equipment damage.
● Do not wear an ESD wrist strap when powering on the equipment to prevent
an electric shock.
● Do not remove or insert cables and field replaceable units (FRUs) during a
system startup. Otherwise, data loss may occur.
● After you switch off the power supply, wait at least one minute before
switching it back on.
● To avoid disk damage and data loss, do not switch the power supply off while
any disk running indicators are still blinking.
Troubleshooting
DANGER
NOTE
If the temperature difference cannot be determined, wait one night after moving devices to
the equipment room and then install them.
Before installing devices, plan and check the installation environment at the site to
improve installation efficiency.
NOTICE
● Before mounting a device into the cabinet, do not move the device without
using original packaging materials provided by Huawei. Do not install the
device in a third-party cabinet and transport it.
● If you need to move a device to a different equipment room after unpacking,
pack the device with the original packaging materials provided by Huawei.
● Packed devices can be stored for a maximum of six months. After being
unpacked, the devices must be powered on within seven days.
● Once the device has been powered on and you want to power it off, it cannot
stay in the off state for more than 7 days.
Access to LLDesigner
1. Log in to eService with your Uniportal account and password.
2. In the Delivery Service area, click LLDesigner, as shown in Figure 3-1.
3. Click Create LLD and select a scenario to start project planning and design.
NOTE
Context
● Device dimensions
The dimensions of storage devices vary according to their models. Table 3-2
lists the dimensions of the related storage devices.
Device Dimensions
● U-shaped brackets
The distance between the front mounting bar and the inner side of the front
door varies according to the cabinet types. Since the system enclosure needs
to be fixed on the front mounting bars, a longer distance between the front
mounting bars and the inner side of the front door can result in smaller space
for cabling at the rear of the device. In such a case, you can install U-shaped
brackets to move the system enclosure forward and leave more space at the
rear of the device for cabling.
A U-shaped bracket is a mechanical part installed between the mounting ear
of the enclosure and mounting bar of the cabinet to adjust the relative
position between the enclosure and the cabinet. A maximum of two U-shaped
brackets can be stacked.
U-shaped brackets are classified into three types: 25 mm, 50 mm, and 75 mm,
as shown in Figure 3-2.
NOTE
● If U-shaped brackets are not installed, the system enclosure is installed on the
front mounting bar by using captive screws. The distance between the front panel
of the system enclosure and the inner side of the front door is fixed.
● Install the U-shaped brackets on the front mounting bars, and then secure the
system enclosure to U-shaped brackets of the respective size. This allows you to
adjust the distance between the front panel of the system enclosure and the inner
side of the front door within a certain range.
Cabinet Space
Before installing storage devices in a cabinet, ensure that:
● The front panel of the system enclosure does not affect closing of the cabinet
door.
● The distance between the rear of the system enclosure and the rear door of
the cabinet is greater than or equal to 90 mm. Otherwise, the cables at the
rear of the system enclosure may affect routing of cables or closing of the
cabinet door.
If the distance between the front mounting bars and the inner side of the front
door does not meet the installation requirements, use U-shaped brackets to
shorten the distance between the front panel of the system enclosure and the
inner side of the front door. Figure 3-3 and Figure 3-4 show the positions of the
storage system before and after the U-shaped brackets are installed.
NOTE
● A measuring scale is contained in the auxiliary material package. You can use it to
determine the type of U-shaped brackets for your storage device. For details about how
to use the measuring scale, see the instructions on it.
● For details on how to install the U-shaped brackets, see 4.2.4.1 (Optional) Installing
U-shaped Brackets and Adjustable Guide Rails.
● The U-shaped brackets decrease the distance between the front panel of the system
enclosure and the inner side of the front door (L1 in the figures) but increase the
distance between the rear of the system enclosure and the rear door of the cabinet (L2
in the figures).
Figure 3-3 Top view of the cabinet (no U-shaped brackets installed)
NOTE
The preceding cabinet space requirements do not consider the space that may be contained
in the front and rear doors of the cabinet.
Table 3-3 lists the recommended cabinet depths for different storage devices.
a: Applicable to OceanStor 2200 V5, 2600 V5, 5300 V5, and 5300F V5
b: Applicable to OceanStor 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, and
5800F V5
Plan the 1. Leave at least 120 cm between two rows of cabinets and 100
location of a cm between a wall and the nearest cabinet.
cabinet.
2. Use 15 m SAS cables or 10 m RDMA cables to connect
cabinets.
Plan the 1. Ensure that the bearing capacity of guide rails in a cabinet is
locations of larger than 50 kg. For a 4 U controller enclosure, ensure that the
storage bearing capacity of guide rails is larger than 97 kg.
devices in a
cabinet. 2. (Recommended) Install the 2 U and 4 U controller enclosures
in the middle position (19 U to 20 U for the 2 U controller
enclosure and 22 U to 25 U for the 4 U controller enclosure) of a
cabinet.
Scenario Principles
NOTE
The device configuration and installation at your site may vary depending on the number of
components, cabinet types, and disk specifications.
NOTICE
If the maximum cabling distance is met, install devices inside the cabinet in
compliance with the layout requirements.
● In the rear view of a disk enclosure, expansion module A is in the upper part
and expansion module B is in the lower part. An identifier is provided on the
expansion modules.
● In the rear view of a high-density disk enclosure, expansion module A is on
the right, and expansion module B is on the left. An identifier is provided on
the expansion modules.
Connection Principles
Before the planning, note the following:
● Bend cables naturally and reserve at least 97 mm clearance in front of the
enclosure for winding cables.
● High-density disk enclosures are connected to the controller using mini SAS
HD cables. Bend cables naturally and reserve at least 97 mm clearance in
front of the enclosure for winding cables.
● SAS disk enclosures and smart disk enclosures are not connected to the same
expansion loop.
● Standard and high-density disk enclosures are not connected to the same
expansion loop.
● The number of disk enclosures connected to the expansion ports on the
controller enclosure and the number of disk enclosures connected to the
back-end ports must not exceed the upper limit.
● For a 2 U controller enclosure, connect the expansion module on controller A
to expansion module A on each disk enclosure and the expansion module on
controller B to expansion module B on each disk enclosure.
● For a 4 U controller enclosure, connect the expansion module in slot H to
expansion module A on the disk enclosure and the expansion module in slot L
to expansion module B on the disk enclosure.
● The disk enclosure type and the number of cascaded disk enclosures
supported by a controller enclosure must not exceed the specifications. For
details, visit Specifications Query (http://support-it.huawei.com/
storagespecification/#/home).
IOM 0 IOM 1
IOM 0 IOM 1
IOM 0 IOM 1
Connection Planning
To ensure network reliability, connect disk enclosures in the same expansion loop
in forward redundancy mode so that two independent links are set up between
the disk enclosures for mutual backup. In the expansion loops shown in Figure 3-9
and Figure 3-10, the orange and blue lines represent two independent links in
mutual backup. A controller failure does not cause all expansion loops to fail. The
following networking diagrams of disk enclosures are for your reference only. You
can access Huawei Storage Product Networking Assistant (https://
support.huawei.com/onlinetoolsweb/sna/#/home) for more networking
diagrams.
P0
Controller
控制框
P1 enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0 P1
硬盘框1
Disk
P0 enclosure 1
P0
P0
Controller
P1 enclosure
P0
P1
P0
Disk
enclosure 0
P0
P1
P0
P1
Disk
enclosure 1
P0
P0
NOTICE
After disk enclosures are connected and powered on, do not change their positions
in the storage system. Otherwise, IDs of disk enclosures may be displayed
incorrectly, service performance may deteriorate, or some storage resources may
be unavailable.
Connection Planning
To ensure network reliability, connect disk enclosures in the same expansion loop
in forward redundancy mode so that two independent links are set up between
the disk enclosures for mutual backup. In the expansion loops shown in Figure
3-12 and Figure 3-13, the orange and blue lines represent two independent links
in mutual backup. A controller failure does not cause all expansion loops to fail.
The following networking diagrams of disk enclosures are for your reference only.
You can access Huawei Storage Product Networking Assistant (https://
support.huawei.com/onlinetoolsweb/sna/#/home) for more networking
diagrams.
P0
P1 Controller
enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0 P1
Disk
P0 enclosure 1
P0
P0
P1 Controller
enclosure
P0
P1
P0
Disk
enclosure 0
P0
P1
P0
P1
Disk
enclosure 1
P0
P0
For V500R007C71 Kunpeng and later versions, the OceanStor 2600 V5 storage
system supports high-density disk enclosures.
Controller
1 2 enclosure
1 2
High-density
disk enclosure 0
1 2 3 4 1 2 3 4
High-density
disk enclosure 1
3 4 3 4
NOTICE
After disk enclosures are connected and powered on, do not change their positions
in the storage system. Otherwise, IDs of disk enclosures may be displayed
incorrectly, service performance may deteriorate, or some storage resources may
be unavailable.
3.1.2.3.3 Disk Enclosure Connection Planning for OceanStor 5300 V5 (SAS) and
5300F V5 (SAS)
Comply with the following interface module installation rules and work out the
connection plan.
● The recommended slot sequence for installing a 100 Gbit/s RDMA interface
module is as follows: IOM 2 > IOM 1 > IOM 0.
● A 12 Gbit/s SAS interface module can be installed only in slot IOM 2.
Connection Planning
To ensure network reliability, connect disk enclosures in the same expansion loop
in forward redundancy mode so that two independent links are set up between
the disk enclosures for mutual backup. In the expansion loops shown in Figure
3-16, Figure 3-17, and Figure 3-18, the orange and blue lines represent two
independent links in mutual backup. A controller failure does not cause all
expansion loops to fail. The following networking diagrams of disk enclosures are
for your reference only. You can access Huawei Storage Product Networking
Assistant (https://support.huawei.com/onlinetoolsweb/sna/#/home) for more
networking diagrams.
P0 Disk
enclosure 2
P0
P1 Controller
enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0 P1
Disk
P0 enclosure 1
P0
P0
P1 Controller
enclosure
P0
P1
P0
Disk
enclosure 0
P0
P1
P0
P1
Disk
enclosure 1
P0
P0
P0
Controller
P1 enclosure
P0
P1
P0
Disk
P0 enclosure 0
P1
P1
P0
Disk
enclosure 1
P0
P0
Controller
1 2 enclosure
1 2
High-density
disk enclosure 0
1 2 3 4 1 2 3 4
High-density
disk enclosure 1
3 4 3 4
NOTICE
After disk enclosures are connected and powered on, do not change their positions
in the storage system. Otherwise, IDs of disk enclosures may be displayed
incorrectly, service performance may deteriorate, or some storage resources may
be unavailable.
3.1.2.3.4 Disk Enclosure Connection Planning for OceanStor 5300 V5 (NVMe) and
5300F V5 (NVMe)
Comply with the following interface module installation rules and work out the
connection plan.
● The recommended slot sequence for installing a 100 Gbit/s RDMA interface
module is as follows: IOM 2 > IOM 1 > IOM 0.
● A 12 Gbit/s SAS interface module can be installed only in slot IOM 2.
Connection Planning
To ensure network reliability, connect disk enclosures in the same expansion loop
in forward redundancy mode so that two independent links are set up between
the disk enclosures for mutual backup. In the expansion loops shown in Figure
3-21, Figure 3-22, and Figure 3-23, the orange and blue lines represent two
independent links in mutual backup. A controller failure does not cause all
expansion loops to fail. The following networking diagrams of disk enclosures are
for your reference only. You can access Huawei Storage Product Networking
Assistant (https://support.huawei.com/onlinetoolsweb/sna/#/home) for more
networking diagrams.
P0
Controller
P1 enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0
P1
Disk
P0
enclosure 1
P0
P0
P0
Controller
P1 enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0
P1
Disk
enclosure 1
P0
P0
P0
P0
Controller
P1 enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0 P1
Disk
P0 enclosure 1
P0
1 2
1 2
High-density
disk enclosure 0
1 2 1 2
3 4 3 4
High-density
disk enclosure 1
3 4 3 4
NOTICE
After disk enclosures are connected and powered on, do not change their positions
in the storage system. Otherwise, IDs of disk enclosures may be displayed
incorrectly, service performance may deteriorate, or some storage resources may
be unavailable.
3.1.2.3.5 Disk Enclosure Connection Planning for OceanStor 5500 V5, 5500F V5,
5600 V5, 5600F V5, 5800 V5, and 5800F V5
Comply with the following interface module installation rules and work out the
connection plan.
● When the onboard 12 Gbit/s SAS interface module is used, the recommended
slot sequence for installing a 100 Gbit/s RDMA interface module is as follows:
IOM 5 > IOM 4 > IOM 3 > IOM 1 > IOM 0 > IOM 2; the recommended slot
sequence for installing a 12 Gbit/s SAS interface module is as follows: IOM 5
> IOM 4 > IOM 3.
● When the onboard 100 Gbit/s RDMA interface module is used, the
recommended slot sequence for installing the 100 Gbit/s RDMA interface
module is as follows: IOM 5 > IOM 4 > IOM 3 > IOM 1 > IOM 0 > IOM 2. A 12
Gbit/s SAS interface module cannot be installed in any one slot between IOM
5 and IOM 0.
Connection Planning
To ensure network reliability, connect disk enclosures in the same expansion loop
in forward redundancy mode so that two independent links are set up between
the disk enclosures for mutual backup. In the expansion loops shown in Figure
3-26, Figure 3-27, and Figure 3-28, the orange and blue lines represent two
independent links in mutual backup. A controller failure does not cause all
expansion loops to fail. The following networking diagrams of disk enclosures are
for your reference only. You can access Huawei Storage Product Networking
Assistant (https://support.huawei.com/onlinetoolsweb/sna/#/home) for more
networking diagrams.
P0 Disk
enclosure 2
P0
Controller
P1
enclosure
P0
P1
P0
P0 Disk
enclosure 0
P1
P0 P1
P0 Disk
enclosure 1
P0
P0
Controller
P1
enclosure
P0
P1
P0
Disk
enclosure 0
P0
P1
P0
P1
Disk
enclosure 1
P0
P0
P0
P0
Controller
P1
enclosure
P0
P1
P0
Disk
P0 enclosure 0
P1
P0 P1
Disk
P0 enclosure 1
P0 P1
P0
P1 P1
P0 Disk
enclosure 0
P0
P1
For V500R007C70SPC100 Kunpeng and later versions, OceanStor 5500 V5, 5600
V5, and 5800 V5 storage systems support high-density disk enclosures.
Controller
1 2 enclosure
1 2
High-density
disk enclosure 0
1 2 3 4 1 2 3 4
High-density
disk enclosure 1
3 4 3 4
NOTICE
After disk enclosures are connected and powered on, do not change their positions
in the storage system. Otherwise, IDs of disk enclosures may be displayed
incorrectly, service performance may deteriorate, or some storage resources may
be unavailable.
3.1.2.3.6 Disk Enclosure Connection Planning for OceanStor 6800 V5 and 6800F V5
Comply with the following interface module installation rules and work out the
connection plan.
IOM H11
IOM H12
IOM H13
IOM H10
IOM H4
IOM H5
IOM H6
IOM H7
IOM H0
IOM H1
IOM H2
IOM H3
IOM H8
IOM H9
IOM L11
IOM L12
IOM L13
IOM L10
IOM L4
IOM L5
IOM L6
IOM L7
IOM L0
IOM L1
IOM L2
IOM L3
IOM L8
IOM L9
● The recommended slot sequence for installing 12 Gbit/s SAS interface
modules is as follows: IOM H6/L6 > IOM H7/L7 > IOM H5/L5 > IOM H8/L8.
● The recommended slot sequence for installing 100 Gbit/s RDMA interface
modules is as follows: IOM H6/L6 > IOM H7/L7 > IOM H5/L5 > IOM H8/L8 >
IOM H4/L4 > IOM H9/L9 > IOM H2/L2 > IOM H11/L11 > IOM H1/L1 > IOM
H12/L12 > IOM H3/L3 > IOM H10/L10.
NOTE
The SO 100 Gbit/s RDMA interface module used for adding controller enclosures can
be installed only in slots IOM H3/L3 and IOM H10/L10. When connecting disk
enclosures, do not use these slots unless other slots are not enough for disk enclosure
connection.
● The configuration disk enclosure (the enclosure with coffer disk identifiers)
must be installed in slots IOM H6/L6.
Connection Planning
To ensure network reliability, connect disk enclosures in the same expansion loop
in forward redundancy mode so that two independent links are set up between
the disk enclosures for mutual backup. In the expansion loops shown in Figure
3-32, Figure 3-33, and Figure 3-34, the orange and blue lines represent two
independent links in mutual backup. A controller failure does not cause all
expansion loops to fail. The following networking diagrams of disk enclosures are
for your reference only. You can access Huawei Storage Product Networking
Assistant (https://support.huawei.com/onlinetoolsweb/sna/#/home) for more
networking diagrams.
P0
P1 Controller
enclosure
P0
P0
P1
P0 Disk
enclosure 0
P1
P0
P1
P0 Disk
enclosure 1
P0
P0
P0
Controller
P1
enclosure
P0
P1 P0
Disk
enclosure 0
P0
P0 P1
P1
Disk
enclosure 1
P0
P0
P0 Disk
enclosure 2
P0
Controller
P0
enclosure
P0
P0 P0
P0 Disk
enclosure 0
P1
P0
P1
Disk
P0 enclosure 1
P0
Controller
1 enclosure
High-density
disk enclosure 0
1 1
2 2
High-density
disk enclosure 1
2 2
NOTICE
After disk enclosures are connected and powered on, do not change their positions
in the storage system. Otherwise, IDs of disk enclosures may be displayed
incorrectly, service performance may deteriorate, or some storage resources may
be unavailable.
NOTICE
The 25 Gbit/s RDMA interface module that connects two controller enclosures
must be installed in slot IOM 0.
1 3
2 4
Connects to the
management network
1
2
3
4
(Optional) Connects to the
management network
To use remote power-on, connect the maintenance ports between the controller
enclosures using network cables, as shown by the green cables in Figure 3-37.
NOTICE
1 3
2 4
Connects to the
management network
1
2
3
4
(Optional) Connects to the
management network
Note:
If you want to remotely power on the storage system, connect the green cables to the maintenance network ports.
If remote power-on is not needed, you do not need to connect the green cables.
NOTICE
The 25 Gbit/s RDMA interface module that connects two controller enclosures
must be installed in slot IOM 1.
Figure 3-38 Directly connecting two controller enclosures for OceanStor 5300 V5
(SAS) and 5300F V5 (SAS)
Connects to the
management network
4
3
2
1
Controller
enclosure 0
1 3
2 4
Connects to the
management network
2 4
(Optional) Connects to the 1 3
management network Controller
enclosure 1
1
2
3
4
(Optional) Connects to the
management network
Figure 3-39 Directly connecting two controller enclosures for OceanStor 5300 V5
(NVMe) and 5300F V5 (NVMe)
Connects to the
management network
4
3
2
1
Controller
enclosure 0
1 3
2 4
Connects to the
management network
2 4
(Optional) Connects to the 1 3
management network Controller
enclosure 1
1
2
3
4
(Optional) Connects to the
management network
To use remote power-on, connect the maintenance ports between the controller
enclosures using network cables, as shown by the green cables in Figure 3-40 and
Figure 3-41.
NOTICE
1 3
2 4
Connects to the
management network
2 4
(Optional) Connects to the 1 3
management network Controller
enclosure 1
1
2
3
4
(Optional) Connects to the
management network
Note:
In V500R007C70 and later versions, if you want to remotely power on the storage system, connect the
green cables to the maintenance network ports. If remote power-on is not needed, you do not need to
connect the green cables.
1 3
2 4
Connects to the
management network
2 4
(Optional) Connects to the 1 3
management network
Controller
enclosure 1
1
2
3
4
(Optional) Connects to the
management network
Note:
If you want to remotely power on the storage system, connect the green cables to the maintenance network ports.
If remote power-on is not needed, you do not need to connect the green cables.
3.1.2.4.3 Direct-Connection Network (OceanStor 5500 V5, 5500F V5, 5600 V5,
5600F V5, 5800 V5, and 5800F V5)
Figure 3-42 shows the direct-connection network of controller enclosures when
the storage system is configured with two controller enclosures (with four
controllers).
NOTICE
The 25 Gbit/s RDMA interface module that connects two controller enclosures
must be installed in slot IOM 2.
1 3
2 4
Connects to the
management network
(Optional) Connects to
2 4
the management network 1 3
Controller
enclosure 1
(Optional) Connects to 1
the management network 2
3
4
To use remote power-on, connect the maintenance ports between the controller
enclosures using network cables, as shown by the green cables in Figure 3-43.
NOTICE
1 3
2 4
Connects to the
management network
(Optional) Connects to
2 4
the management network 1 3
Controller
enclosure 1
(Optional) Connects to 1
the management network 2
3
4
Note:
In V500R007C70 and later versions, if you want to remotely power on the storage system, connect the
green cables to the maintenance network ports. If remote power-on is not needed, you do not need to
connect the green cables.
NOTICE
The SO 100 Gbit/s RDMA interface modules that connect two controller
enclosures must be installed in slots IOM H3/L3 and IOM H10/L10.
Controller
控制框0 1 2
enclosure 0 Connects to the user
连接到用户管理网络
management network
1 2
Controller
控制框1 1 2 (Optional) Connects to
enclosure 1 连接到用户管理网络
the management network
(Optional) Connects to
连接到用户管理网络
the management network
1 2
To use remote power-on, connect the maintenance ports between the controller
enclosures using network cables, as shown by the green cables in Figure 3-45.
NOTICE
Controller
控制框0 1 2
enclosure 0 Connects to the user
连接到用户管理网络
management network
1 2
Controller
控制框1 1 2 (Optional) Connects to
enclosure 1 连接到用户管理网络
the management network
(Optional) Connects to
连接到用户管理网络
the management network
1 2
Note:
In V500R007C70 and later versions, if you want to remotely power on the storage system, connect the green cables
to the maintenance network ports. If remote power-on is not needed, you do not need to connect the green cables.
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
NOTICE
After the first power-on and initialization, the controller enclosures support
remote power-on in later operations. For the first power-on and initialization, you
must use the power button on the controller enclosures. For details on remote
power-on, see "Powering On the Storage System (Remotely on the CLI, Applicable
to V500R007C70 and Later Versions)" in the administrator guide corresponding to
your product model.
3
1 Data switch 0
(rear)
2
4
3
1
Data switch 1
(rear)
2
4
Connects to the 1 1
management network. Controller
enclosure 0
2 2
Connects to the
management network.
3 3
(Optional) Connects to the
Controller
management network.
enclosure 1
4 4
Follow-up Procedure
After planning ports, you must formulate port correlation tables for connections
between the storage system and switch ports, as listed in Table 3-5.
Table 3-5 Port correlation between the storage system and switches
Port Number Storage System Switch Port Port Number
Port
0 Storage_Port_Y Switch_Port_Y 0
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
Figure 3-47, Figure 3-48, Figure 3-49, Figure 3-50, Figure 3-51, and Figure 3-52
show how to connect multiple controller enclosures.
NOTICE
After the first power-on and initialization, the controller enclosures support
remote power-on in later operations. For the first power-on and initialization, you
must use the power button on the controller enclosures. For details on remote
power-on, see "Powering On the Storage System (Remotely on the CLI, Applicable
to V500R007C70 and Later Versions)" in the Administrator Guide corresponding to
your product model.
3
1 Data switch 0
(rear)
2
4
3
1
Data switch 1
(rear)
2
4
Connects to the 1 1
management network. Controller
enclosure 0
2 2
Connects to the
management network.
3 3
(Optional) Connects to the
Controller
management network.
enclosure 1
4 4
3
1
Data switch 0
2 (rear)
4
3
1
Data switch 1
(rear)
2
4
Connects to the 1 1
management network. Controller
enclosure 0
2 2
Connects to the
management network.
3 3
(Optional) Connects to the Controller
management network. enclosure 1
4 4
5
3
1 Data switch 0
(rear)
2
4
6
5
3
1
Data switch 1
(rear)
2
4
6
Connects to the 1 1
management network. Controller
enclosure 0
2 2
Connects to the
management network.
3 3
(Optional) Connects to the
Controller
management network.
enclosure 1
4 4
5 5
(Optional) Connects to the Controller
management network. enclosure 2
6 6
5
3
1 Data switch 0
(rear)
2
4
6
5
3
1
Data switch 1
(rear)
2
4
6
2 2
Connects to the
management network.
3 3
(Optional) Connects to the Controller
management network. enclosure 1
4 4
5 5
(Optional) Connects to the
management network. Controller
enclosure 2
6 6
Note:
If you want to remotely power on the storage system, connect the cables (green cables) of the maintenance network ports as
instructed in the figure. In other cases, you do not need to connect the green cables.
Figure 3-51 Switched networking among four controller enclosures for OceanStor
5300 V5 (SAS) and 5300F V5 (SAS)
5 7
3
Data switch 0
1
(rear)
2
4
6 8
7
5
3
1
Data switch 1
(rear)
2
4
6
8
Connects to the 1 1
management network. Controller
enclosure 0
2 2
Connects to the
management network.
3 3
(Optional) Connects to the
Controller
management network.
enclosure 1
4 4
5 5
(Optional) Connects to the
Controller
management network.
enclosure 2
6 6
7 7
(Optional) Connects to the
Controller
management network.
enclosure 3
8 8
Figure 3-52 Switched networking among four controller enclosures for OceanStor
5300 V5 (NVMe) and 5300F V5 (NVMe)
5 7
3
1 Data switch 0
2 (rear)
4
6 8
7
5
3
1
Data switch 1
(rear)
2
4
6
8
Connects to the 1 1
Controller
management network.
enclosure 0
2 2
Connects to the
management network.
3 3
(Optional) Connects to the Controller
management network. enclosure 1
4 4
5 5
(Optional) Connects to the Controller
management network. enclosure 2
6 6
7 7
(Optional) Connects to the Controller
management network. enclosure 3
8 8
Follow-up Procedure
After planning ports, you must formulate port correlation tables for connections
between the storage system and switch ports, as listed in Table 3-6.
Table 3-6 Port correlation between the storage system and switches
0 Storage_Port_Y Switch_Port_Y 0
3.1.2.4.7 Switched Network (OceanStor 5500 V5, 5500F V5, 5600 V5, 5600F V5,
5800 V5, and 5800F V5 in V500R007C71 Kunpeng and Later)
When a storage system has two or more controller enclosures, they can be
connected using switches. The 25 Gbit/s RDMA interface module that connects
multiple controller enclosures must be installed in slot IOM 2. To facilitate future
maintenance, attach labels to data switches 0 and 1 to distinguish them after the
networking is complete.
When switches are used for networking, only Huawei CE6865-48S8CQ-EI switches
are supported. Ensure that the switch software version is V200R005C10SPC800
(with the V200R005C10SPH017 patch installed) or later. For details about how to
query and upgrade the switch version, see the product documentation of
CE6865-48S8CQ-EI switches. To obtain the documentation, log in to Huawei's
technical support website (https://support.huawei.com/enterprise/), enter the
product model (for example, CE6865) in the search box, and click the suggested
path beneath the search box. On the documentation page of the product model,
search for, browse through, and download the desired documentation.
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
Figure 3-53, Figure 3-54, and Figure 3-55 show how to connect multiple
controller enclosures.
NOTICE
After the first power-on and initialization, the controller enclosures support
remote power-on in later operations. For the first power-on and initialization, you
must use the power button on the controller enclosures. For details on remote
power-on, see "Powering On the Storage System (Remotely on the CLI, Applicable
to V500R007C70 and Later Versions)" in the Administrator Guide corresponding to
your product model.
3
Data switch 0
1
(rear)
2
3
1
Data switch 1
(rear)
2
4
Connects to the management network.
1 1
Controller enclosure 0
Connects to the
management 2 2
network.
(Optional) Connects to
the management
network.
3 3
Controller enclosure 1
Note:
If you want to remotely power on the storage system, connect the green cables to the maintenance network ports as
instructed in the figure. In other cases, you do not need to connect the green cables.
This figure uses the controller enclosures with onboard 100 Gbit/s RDMA ports as an example. Networking of the controller
enclosures with onboard mini SAS HD ports is the same.
5
3
Data switch 0
1
(rear)
2
4
6
5
3
1
Data switch 1
(rear)
2
4
6
Connects to the
1 1
management network.
Controller enclosure 0
Connects to the
management 2 2
network.
(Optional) Connects
to the management
network.
3 3
Controller enclosure 1
(Optional) Connects to
the management 4 4
network.
Controller enclosure 2
Note:
If you want to remotely power on the storage system, connect the green cables to the maintenance network ports as instructed in the
figure. In other cases, you do not need to connect the green cables.
This figure uses the controller enclosures with onboard 100 Gbit/s RDMA ports as an example. Networking of the controller enclosures
with onboard mini SAS HD ports is the same.
5 7
3
1 Data switch 0
(rear)
2
4
6 8
7
5
3
1
Data switch 1
(rear)
2
4
6
8
Connects to the management network. 1 1
Controller enclosure 0
Connects to the
management 2 2
network.
(Optional) Connects
to the management
network.
3 3
Controller enclosure 1
(Optional) Connects to
the management network.
5 5
Controller enclosure 2
Note:
If you want to remotely power on the storage system, connect the green cables to the maintenance network ports as instructed in the figure.
In other cases, you do not need to connect the green cables.
This figure uses the controller enclosures with onboard 100 Gbit/s RDMA ports as an example. Networking of the controller enclosures with
onboard mini SAS HD ports is the same.
Follow-up Procedure
After planning ports, you must formulate port correlation tables for connections
between the storage system and switch ports, as listed in Table 3-7.
Table 3-7 Port correlation between the storage system and switches
0 Storage_Port_Y Switch_Port_Y 0
When switches are used for networking, only Huawei CE8850-32CQ-EI or CE8850-
SAN switches are supported.
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
Figure 3-56 and Figure 3-57 show how to connect multiple controller enclosures.
NOTICE
After the first power-on and initialization, the controller enclosures support
remote power-on in later operations. For the first power-on and initialization, you
must use the power button on the controller enclosures. For details on remote
power-on, see "Powering On the Storage System (Remotely on the CLI, Applicable
to V500R007C70 and Later Versions)" in the Administrator Guide specific to your
product model.
3
1
Data switch 0
2 (rear)
4
3
1
Data switch 1
(rear)
2
4
1 Connects to the
1 management network.
Controller enclosure 0
(original)
2 Connects to the
2 management network.
(Optional) Connects to
3
the management
3 network.
Controller enclosure 1
(new)
(Optional) Connects to
4 the management
4 network.
Note:
· If you want to remotely power on the storage system, connect the cables (green cables) of the maintenance
network ports as instructed in the figure. In other cases, you do not need to connect the green cables.
· The network uses the controller enclosures with 100 Gbit/s RDMA expansion modules as an example to describe
the networking. Networking of the controller enclosures with 12 Gbit/s SAS expansion modules is the same.
· SO 100 Gbit/s RDMA interface modules must be installed in slots IOM H3/L3 and IOM H10/L10.
3
1 Data switch 0
2 (rear)
3
1
Data switch 1
(rear)
2
4
1 Connects to the
1 management network.
Controller enclosure 0
(original)
2 Connects to the
2 management network.
3 (Optional) Connects to
3 the management
network.
Controller enclosure 1
(new)
(Optional) Connects to
4 4 the management
network.
Note:
If you want to remotely power on the storage system, connect the cables (green cables) of the maintenance
network ports as instructed in the figure. In other cases, you do not need to connect the green cables.
The network uses the controller enclosures with 100 Gbit/s RDMA expansion modules as an example to describe
the networking. Networking of the controller enclosures with 12 Gbit/s SAS expansion modules is the same.
SO 100 Gbit/s RDMA interface modules must be installed in slots IOM H3/L3 and IOM H10/L10.
Follow-up Procedure
After planning ports, you must formulate port correlation tables for connections
between the storage system and switch ports, as listed in Table 3-8.
Table 3-8 Port correlation between the storage system and switches
0 Storage_Port_Y Switch_Port_Y 0
Context
Application servers and storage systems support various network modes. An
application server is usually connected to a storage system over multiple paths for
enhanced data transfer security and reliability.
NOTE
● In planning block services, hosts require multipathing software to select and manage
paths between application servers and storage systems. In planning file services, hosts
do not require multipathing software.
● To connect storage systems to application servers, both iSCSI and Fibre Channel
networks are supported for block services while only the NAS network is supported for
file services. The principles for planning iSCSI and NAS networks between storage
systems and application servers are the same.
● This section uses the block service network planning as an example. For details about
how to configure services, see the Basic Storage Service Configuration Guide for Block
and Basic Storage Service Configuration Guide for File specific to your product model.
Planning Rules
To improve system reliability, comply with the following rules for cable connection:
● Figure 3-58 shows the 2 U controller enclosure of OceanStor 2200 V5. Each
of controllers A and B provides two interface module slots. The slot sequence
for installing interface modules to connect to application servers is IOM 0 >
IOM 1.
IOM 0 IOM 1
IOM 0 IOM 1
IOM 0 IOM 1
● Figure 3-59 shows the 2 U controller enclosure of OceanStor 2600 V5. Each
of controllers A and B provides two interface module slots. The slot sequence
for installing interface modules to connect to application servers is IOM 0 >
IOM 1.
● Figure 3-62 shows the 2 U controller enclosure of OceanStor 5500 V5, 5500F
V5, 5600 V5, 5600F V5, 5800 V5, and 5800F V5. Each of controllers A and B
provides six interface module slots. The slot sequence for installing interface
modules to connect to application servers is IOM 0 > IOM 1 > IOM 3 > IOM 4
> IOM 5 > IOM 2.
NOTICE
Connection Plans
A storage system can be connected to an application server directly or through
two switches.
NOTE
● Other connection modes between storage systems and application servers include
single-switch connection, dual-switch connection in a cluster environment, and dual-
switch connection in a HyperMetro cluster environment. For details, see "Typical
UltraPath Applications" in the OceanStor UltraPath User Guide.
● The following examples use the 2 U controller enclosure of OceanStor 5300 V5.
● Direct connection (single controller enclosure)
An application server is directly connected to a storage system through two
paths. Connect at least one front-end port on each controller to the
application server for redundancy. UltraPath automatically calculates and
selects the optimal path for data transmission based on the operating status
of the storage system. Figure 3-63, Figure 3-64, and Figure 3-65 show the
connection diagrams.
Application server
UltraPath
Network card Network card
0/HBA 0 1/HBA 1
P0 P0
P0 P0
Controller A Controller B
Figure 3-64 Directly connecting the storage device and the application server
over GE electrical ports
Figure 3-65 Directly connecting the storage device and the application server
over Fibre Channel ports
Switch 1 Switch 2
P0 P1 P0 P1
Controller A Controller B
Figure 3-67 Connecting the storage device and the application server through
switches over GE electrical ports
Figure 3-68 Connecting the storage device and the application server through
switches over Fibre Channel ports
Table 3-9 provides an example of zone planning for a Fibre Channel network.
Application server
UltraPath
Network card Network card
0/HBA 0 1/HBA 1
P0 P1 P0 P1
P0 P0 P0 P0
Controller A Controller B Controller A Controller B
Controller enclosure 0 Controller enclosure 1
Switch 1 Switch 2
P0 P1 P0 P1 P0 P1 P0 P1
Controller A Controller B Controller A Controller B
Controller enclosure 0 Controller enclosure 1
Follow-up Procedure
After planning ports, you must formulate port correlation tables for connections
between the application server and switch ports, and for connections between the
storage system and switch ports. Table 3-11 shows port correlation between the
application server and switches, and Table 3-12 shows port correlation between
the storage system and switches.
Table 3-11 Port correlation between the application server and switches
0 Server_Port_Y Switch_Port_Y 0
Table 3-12 Port correlation between the storage system and switches
1 Storage_Port_Y Switch_Port_Y 1
Context
● Application servers and storage systems support various network modes. An
application server is usually connected to a storage system over multiple
paths for enhanced data transfer security and reliability.
NOTE
Planning Rules
To improve system reliability, comply with the following rules for cable connection:
● Figure 3-72 shows a 4 U controller enclosure. From left to right, the slot IDs
are from IOM H0 to IOM H13 in the upper half and are from IOM L0 to IOM
L13 in the lower half.
IOM H11
IOM H12
IOM H13
IOM H10
IOM H4
IOM H5
IOM H6
IOM H7
IOM H0
IOM H1
IOM H2
IOM H3
IOM H8
IOM H9
IOM L11
IOM L12
IOM L13
IOM L10
IOM L4
IOM L5
IOM L6
IOM L7
IOM L0
IOM L1
IOM L2
IOM L3
IOM L8
IOM L9
ii. When the storage system is equipped with four controllers, the
recommended slot sequence for installing front-end interface
modules is as follows: IOM H0/L0 > IOM H13/L13 > IOM H1/L1 >
IOM H12/L12 > IOM H2/L2 > IOM H11/L11 > IOM H4/L4 > IOM
H9/L9 > IOM H5/L5 > IOM H8/L8 > IOM H3/L3 > IOM H10/L10 >
IOM H7/L7.
● Interface modules of the same type must be inserted in sequence.
● Insert the interface modules used for Ethernet networking in ascending order
of their port rates. Then insert the interface modules used for Fibre Channel
networking in ascending order of their port rates.
● The front-end port connections are symmetric between slots H0 to H13 and
slots L0 to L13 on the same storage system. That is, the interface modules
reside in slots with the same slot ID and use the ports in the same positions.
● In the Ethernet port bonding scenario, the member bond ports are symmetric
between slots H0 to H13 and slots L0 to L13 on the same storage system.
That is, the interface modules reside in slots with the same slot ID and use
the ports in the same positions.
NOTICE
Connection Plans
A storage system can be connected to an application server directly or through
two switches.
NOTE
Other connection modes between storage systems and application servers include single-
switch connection, dual-switch connection in a cluster environment, and dual-switch
connection in a HyperMetro cluster environment. For details, see "Typical UltraPath
Applications" in the OceanStor UltraPath User Guide.
● Direct connection (single controller enclosure)
– iSCSI network
i. When the controller enclosure has two controllers, the application
server is directly connected to the storage system through two paths.
UltraPath automatically calculates and selects the optimal path for
data transmission based on the operating status of the storage
system. Figure 3-73, Figure 3-74, and Figure 3-75 show the
connection diagrams.
NOTE
Application server
UltraPath
Network Network
card 0 card 1
P0 P0
P0 P0
Quadrant A Quadrant B
ii. When the controller enclosure has four controllers, the application
server is directly connected to the storage system through four paths.
UltraPath automatically calculates and selects the optimal path for
data transmission based on the operating status of the storage
system. Figure 3-76, Figure 3-77, and Figure 3-78 show the
connection diagrams.
P0 P0 P0 P0
Quadrant A Quadrant B Quadrant C Quadrant D
Alternatively, you can choose to connect the storage system and the application
server through two paths. You only need to configure two interface modules in
the same slots of the H and L planes, respectively.
HBA 0 HBA 1
P0 P1 P0 P1
P0 P0 P0 P0
Quadrant A Quadrant B Quadrant C Quadrant D
Figure 3-80 Directly connecting the storage device and the application
server over Fibre Channel ports
NOTE
Switch 1 Switch 2
P0 P1 P0 P1
Quadrant A Quadrant B
Figure 3-82 Connecting the storage device (two controllers) and the
application server over GE electrical ports through switches
Figure 3-83 Connecting the storage device (two controllers) and the
application server over ETH ports through switches
ii. When the controller enclosure has four controllers, connect the
storage system to each switch through four paths, as shown in
Figure 3-84, Figure 3-85, and Figure 3-86.
Switch 1 Switch 2
P0 P1 P0 P1 P0 P1 P0 P1
Quadrant A Quadrant B Quadrant C Quadrant D
Figure 3-85 Connecting the storage device (four controllers) and the
application server over GE electrical ports through switches
Figure 3-86 Connecting the storage device (four controllers) and the
application server over ETH ports through switches
Alternatively, you can choose to connect the storage system and each switch
through two paths. You only need to configure two interface modules in the
same slots of the H and L planes, respectively.
HBA 0 HBA 1
P0 P0
Switch 1 Switch 2
P0 P1 P0 P1 P0 P1 P0 P1
Quadrant A Quadrant B Quadrant C Quadrant D
Figure 3-88 Connecting the storage device and the application server
over Fibre Channel ports through switches
Switch 1 Switch 2
P0 P1 P0 P1 P0 P1 P0 P1
Quadrant A Quadrant B Quadrant A Quadrant B
Controller enclosure 0 Controller enclosure 1
Switch 1 Switch 2
P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1
Quadrant A Quadrant B Quadrant C Quadrant D Quadrant A Quadrant B Quadrant C Quadrant D
Controller enclosure 0 Controller enclosure 1
HBA 0 HBA 1
P0 P0
Switch 1 Switch 2
P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1
Quadrant A Quadrant B Quadrant C Quadrant D Quadrant A Quadrant B Quadrant C Quadrant D
Controller enclosure 0 Controller enclosure 1
NOTE
On Fibre Channel networks, you can choose to connect the storage system and each
switch through two paths. You only need to configure two interface modules in the
same slots of the H and L planes on each controller enclosure, respectively.
Table 3-14 provides an example of zone planning for a Fibre Channel
network.
Follow-up Procedure
After planning ports, you must formulate port correlation tables for connections
between the application server and switch ports, and for connections between the
storage system and switch ports. Table 3-15 shows port correlation between the
application server and switches, and Table 3-16 shows port correlation between
the storage system and switches.
Table 3-15 Port correlation between the application server and switches
0 Server_Port_Y Switch_Port_Y 0
Table 3-16 Port correlation between the storage system and switches
1 Storage_Port_Y Switch_Port_Y 1
Scenario Principle
Scenario Principle
8. Each circuit breaker in the PDU can only connect one load.
Table 3-18 Default IP addresses and subnet masks of the management network
ports on a 2 U controller enclosure
IP Address Subnet Mask
Table 3-19 Default IP addresses and subnet masks of the management network
ports on a 4 U controller enclosure
IP Address Subnet Mask
NOTE
Before initial configuration of the storage system, plan and take note of the IP
addresses and network parameters for the storage system.
Table 3-20, Table 3-21, Table 3-22, and Table 3-23 list the IP addresses of
management network ports.
NOTE
You need to plan IP addresses and network parameters for the storage system each time
when:
● A controller is added to a 2 U controller enclosure.
● Two controllers are added to a 4 U controller enclosure.
Table 3-24 and Table 3-25 list the alarm policy parameters.
Installation Tools
Common tools include screwdrivers, diagonal pliers, ESD clothing, gloves, and
wrist straps. For details, see Table 7-1.
Installation Meters
Table 3-26 lists the required installation meters.
Software Tools
Table 3-27 lists the required software tools.
Technical Documentation
The documents that must be prepared before installation are as follows:
● Contract, device configuration table, equipment room design, and
construction drawing paper (provided by the customer)
● Table 3-28 lists the required product documents specific to your product
models.
NOTICE
Environmental Requirements
Environmental requirements cover the following aspects: temperature, humidity,
altitude, vibration and shock, particle contaminants, corrosive airborne
Power Requirements
Guidelines for configuring power supplies for the storage system are as follows:
Fire Fighting
To secure an equipment room, ensure that the equipment room have a powerful
fire fighting system.
A fire fighting system should be prepared by the customer. The customer must
consult the insurance underwriter, local fire marshal, and building inspectors to
select a fire fighting system of a correct level of coverage and protection.
Because a fire fighting system must comply with local laws and regulations that
vary with countries and regions, Huawei does not participate in the design and
deployment of the customer's fire fighting system. Therefore, Huawei shares no
responsibility for device damage and personal injuries caused by a fire fighting
system failure.
Prerequisites
● The goods have been delivered to the site.
● The project supervisor and customer representative are present at the site.
Context
1. The bag containing the Packing List is attached to the surface of the carton.
2. After receiving the goods, unpack and inspect them according to the Packing
List.
– If short shipment of goods is stated on the Packing List, contact order
management engineers of Huawei local office for solutions. The project
supervisor and customer representative sign the Packing List.
– If short, wrong, or excessive shipment of goods is found or goods are
damaged, the project supervisor and the customer representative sign the
Memo for Unpacking and Inspecting Goods and Packing List. The project
supervisor fills out the Goods Feedback Form, submits it to the local
Huawei local office within three days, and stores the problematic goods
(including all the internal and external packages) for further
investigation.
– After confirming that the goods are intact and complete, the project
supervisor and the customer representative sign the Packing List.
Procedure
Step 1 Check the appearance and number of packages.
NOTE
Before unpacking goods, take out the Packing List from its bag and check the goods
according to the list.
After a project is started, the project supervisor should work with the customer
representative to check and accept the goods. Table 3-29 lists the check items.
NOTICE
For details about the standard operation procedure, see the unpacking diagram
printed on the carton.
Step 4 Using the information on the Order List and Packing List, inspect all components
in each package.
Step 5 Check the packages of components for obvious damage.
Step 6 Unpack components and check each component for any loss or damage.
● Appearance: tidy without scratches, loose part, or damage
● Silkscreen: clear and intact
● Connector: securely connected
● Quantity: consistent with that specified in the Packing List
NOTE
----End
4 Hardware Installation
Start
Deploy multi-controller
storage system
Deploy applications
Mandatory
End
Optional
a: Applicable to OceanStor 2200 V5, 2600 V5, 5300 V5, and 5300F V5
b: Applicable to OceanStor 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, and
5800F V5
NOTE
If the device is to be installed in a third-party cabinet provided by the customer, check the
third-party cabinet to ensure that it meets the installation requirements. For details, see 7.6
Checking a Third-Party Cabinet.
5. Select the hardware installation multimedia, and click the desired operation
video in the navigation tree.
NOTE
If you are installing a device in a third-party cabinet, check the cabinet first to ensure that it
meets the conditions for installing devices. For details, see 7.6 Checking a Third-Party
Cabinet.
NOTE
For details about the FR42612L cabinet, see 7.4 Introduction to an FR42612L Cabinet in
the Appendix.
Prerequisites
The following required tools have been prepared:
● Multimeter
● Flat-head screwdriver, Phillips screwdriver, and adjustable wrench
● Measuring tape, marker, powder marker, level, right angle, protective gloves
● Ladder
● M6 screw
● Floating nut mounting bar
Meters and instruments must be tested and adjusted before use.
Procedure
Step 1 Before installing a cabinet, check the installation environment and materials.
1. Check whether the device types and quantity are the same as those in the
Packing List.
2. Check whether the cabinet appearance is in good condition and free of
collision and scratch.
3. Check whether the area, height, and ground bearing capacity of the
installation position meet related requirements.
Step 2 Draw the cabinet installation outline to determine the installation position.
1. Check the engineering drawings to determine the positions for installing the
cabinet. Align the measuring tape with the upper edge of the installation
position, and mark the upper edge by using a marker.
2. Use the powder marker to outline the positions for installing the cabinet.
Figure 4-4 shows the outline of the positions for installing a single cabinet.
Figure 4-5 shows the outline of the positions for installing combined cabinets.
NOTE
When using a right angle to determine the cabinet position, ensure that the left or right
side of the cabinet and the outer edge of the rear door are aligned with the outline on the
floor.
3. Rotate the M12 bolts at the bottom of the leveling feet clockwise by using an
adjustable wrench to ensure that the leveling feet contact the ground and the
castors hang in the air. See (3) in Figure 4-7.
NOTE
– Spin the castors by using a Phillips screwdriver. If the castors rotate freely, they are
hanging in the air.
– H indicates the height from the top of the cabinet to the ground. The value of H
ranges from 1995 mm to 2005 mm and can be changed by adjusting the support
feet.
4. Make sure that the heights measured from the front, rear, right, and left of
the cabinet are the same.
Step 5 Adjust the levelness and verticality of a cabinet by raising or lowering its leveling
feet.
1. Use a level and plumb line to check the levelness and verticality respectively.
2. If the cabinet is not level, use an adjustable wrench to adjust the support feet.
NOTE
● Check the levelness in the front of the cabinet and at the rear of the cabinet.
● To check the levelness, lay a level. If the bubbles are in the middle of the level when
they are static, the position you want to check is level.
Step 6 (Optional) After securing and leveling two or more adjacent cabinets, combine the
cabinets.
1. Remove the screws from the connection plates on the front and rear doors
using a Phillips screwdriver. See (1) in Figure 4-9.
NOTE
– The cabinet in the middle provides four connection points on the front and rear
doors respectively.
– A cabinet on the leftmost or rightmost side provides two connection points on the
front and rear doors respectively.
– Ensure that the vertical deviation and the distance between cabinets are not
greater than 3 mm after the cabinets are combined.
2. Pass the connection plate through the gap on the cabinet door and secure it
using the removed screws. See (2) in Figure 4-9.
NOTE
To ensure that PDU tabs can be easily oriented to the installation holes, two persons
are recommended for this operation.
CAUTION
If a floating nut mounting bar is unavailable, you can remove the floating
nuts by using a flat-head screwdriver. When using a flat-head screwdriver to
remove floating nuts, do not apply excessive force and pay attention not to
injure your hands or damage storage devices.
a. Use the floating nut mounting bar to pull one foot of the floating nut
downward, and then take the floating nut out.
Prerequisites
● Cabinets have been installed.
● The power switches of output terminals on the power distribution cabinet
(PDC) are set to OFF.
● All circuit breakers on the PDUs are set to OFF.
● Required materials have been prepared, including power cables, PGND cables,
cable ties, wax strings, and PVC insulation tapes.
● Required tools have been prepared, including diagonal pliers, cable cutters,
Phillips screwdrivers, multimeters, and ladders.
Context
A PDU connector is the IEC60309-32A-compliant standard plug and socket, as
shown in Figure 4-12. The connector used to connect to the PDU is a male plug
that has been connected to the PDU power cable before delivery. The connector
used to connect to a PDC is a female socket. At the installation site, you need to
connect the AC power cable of the PDC to the female socket and then connect the
male plug to the female socket.
Procedure
Step 1 Route PGND cables and power cables.
1. Read the Site Survey Report to determine the layout, routing, and length of
PGND cables and power cables.
NOTE
A cabinet supports both overhead and underfloor cabling. This section uses overhead
cabling as an example to illustrate how to route cables.
2. Use a cable cutter to cut off a piece of cable, and reserve a proper length, as
shown in Figure 4-13.
For details about how to prepare terminals for PGND cables and power cables, see 7.10
Preparing Cables and Connectors.
NOTE
Step 4 Lift the cabinet cover to an angle of approximately 30 degrees and take out the
PDU connectors.
NOTICE
1. Pull the positioning pins on the cover of the rear cabinet door slightly and
push the cabinet cover upwards to an angle of approximately 30 degrees. See
(1) in Figure 4-15.
2. Lead the two PDU connectors out of the two cable outlets on the cabinet
cover. See (2) in Figure 4-15.
3. Restore the cabinet cover.
DANGER
The power switch of the PDC for providing power for the cabinet must remain off
to prevent fatal personal injury.
1. Separate the male plug from the female socket. See (1) in Figure 4-16.
2. Unlock the buckle in the middle of the female socket and disassemble the
female socket by spinning it counterclockwise. See (2) in Figure 4-16.
3. Route the power cable through the PDU female socket and connect a live line
(brown), PGND cable (yellow and green), and neutral wire (blue) respectively
to the L/+ jack, jack, and unidentified jack. Use a Phillips screwdriver to
fasten the screws on the female socket to secure those cables. See (3) in
Figure 4-16.
4. Assemble the two parts of the female socket and insert the male plug to the
female socket. See (4) in Figure 4-16.
Step 6 Connect the other end of the power cable to the wiring terminal of the
uninterruptible power system (UPS), AC PDC, or AC distribution box, as shown in
Figure 4-17.
----End
Prerequisites
The following installation tools and materials have been prepared:
Context
● To facilitate the operation and maintenance of a controller enclosure, you are
advised to install a controller enclosure between the 19th U and the 24th U in
a cabinet. This section uses the recommended installation positions in a 42 U
cabinet as an example. You can plan device installation positions based on
site requirements.
● You are advised to install disk enclosures from the bottom up in descending
order of weight.
Procedure
Step 1 See 3.1.2.2 Cabinet Layout to locate the installation positions of controller
enclosures and disk enclosures in a cabinet.
NOTE
Each three square holes correspond to 1 U height. Each 1 U height is lined out with a scale
mark. If no 1 U scale mark is lined out on the front and rear columns of the cabinet, line
out scale marks to facilitate locating installation positions.
Step 2 Align the bottom of an installation template with the integer U mark on the
mounting bars of the cabinet, as shown in Figure 4-18, Figure 4-19, and Figure
4-20.
Step 3 Use a marker to mark the positions of the screw holes where devices will be
fastened on the mounting bars. Then, you have finished locating the installation
positions of the controller enclosure and disk enclosures.
----End
NOTE
● By default, adjustable guide rails are not included in the accessories of a storage device
to be installed in a third-party cabinet. You must purchase them separately when
placing POs if needed.
● If U-shaped brackets are required, install them with adjustable guide rails together.
There are three types of U-shaped brackets (25 mm, 50 mm, and 75 mm), and a pair of
each type is provided in the auxiliary material package. You do not need to purchase
them separately. Use the measuring scale in the auxiliary material package to determine
the type of U-shaped bracket for your storage device. Follow the instructions on the
measuring scale. For more information about the U-shaped brackets, see U-shaped
brackets.
Prerequisites
● The installation positions of enclosures in the cabinet have been determined.
● The following installation tools and materials have been prepared:
– Phillips screwdriver (M3 to M6)
– Marker
– M6 screws
– Square-hole positioning pins (for square-hole mounting bars)
– Round-hole positioning pins (for round-hole mounting bars)
– U-shaped brackets
Precautions
CAUTION
NOTE
Before performing the installation, you are advised to count several U scales upward from
the position of the first scale at the bottom of the mounting bar, and then mark the
position. This can ensure that the front and rear heights of the adjustable guide rails are
the same.
Context
● You are advised to install storage devices in a cabinet from the bottom up.
● A pair of adjustable guide rails is included with each storage device.
● The length of the adjustable guide rail ranges from 600 mm to 900 mm.
● The square-hole positioning pins come installed on the adjustable guide rails
before delivery. If the installation holes of the screws are round, change the
square-hole positioning pins to round-hole positioning pins before installing
the adjustable guide rails.
NOTE
You can find round-hole positioning pins in the accessory bag delivered with the devices.
NOTICE
● Secure the adjustable guide rails for a 4 U disk enclosure with M6 screws.
Figure 4-21 Attaching the adjustable guide rails for a 4 U disk enclosure
Figure 4-22 Attaching the adjustable guide rails for a 4 U controller enclosure
● Secure the adjustable guide rails for a 2 U storage device with M6 screws.
----End
Figure 4-24 Securing the U-shaped brackets and adjustable guide rails
Floating nuts have been installed on U-shaped brackets before delivery. If no floating nuts
have been installed, install a floating nut into the third hole on each U-shaped bracket.
Insert and clamp one foot of the floating nut into the square hole. Pull the other
foot of the floating nut by using the floating nut mounting bar to clamp it in the
square hole.
CAUTION
----End
Follow-up Procedure
● After the U-shaped brackets are fixed to the front mounting bar and the
floating nuts are installed, install the storage device onto the U-shaped
brackets, as shown in Figure 4-26 and Figure 4-27.
Figure 4-27 Securing the storage device onto the U-shaped bracket
Figure 4-28 Stacking two U-shaped brackets on the adjustable guide rail
Prerequisites
● Guide rails have been properly installed.
● The following installation tools and materials are ready:
– Phillips screwdriver (M3 to M6)
– ESD gloves
– ESD clothes
– ESD wrist strap
Precautions
● To avoid personal injury or device damage, arrange for three persons to carry
and install a 2 U enclosure and four persons for a 4 U enclosure.
● If you remove disks and interface modules to facilitate the movement and
installation of the device, record the mapping between each disk (or interface
module) and it slot in advance, so you can easily insert each disk or interface
module back to its correct slot.
● Storage devices must be installed on adjustable guide rails. Stacking devices
may damage them.
Procedure
Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothes.
2. Repeat Step 2.1 to remove the M3 screws on the right of the protective cover,
and place the removed M3 screws and protective cover into an ESD bag.
Step 3 Slide the controller enclosure or disk enclosure into the cabinet and tighten the
captive screws to secure it to the cabinet, as shown in Figure 4-31 and Figure
4-32.
NOTE
The controller enclosure and disk enclosure are installed in the same way. The following
uses the controller enclosure as an example.
Step 4 (Optional) If disks have not been installed, install the disks into empty slots in
sequence and then close the disk handles, as shown in Figure 4-33.
NOTICE
● Before installing a disk, fully open its handle to ensure proper installation.
● Insert the disk module into the slot by pushing the middle area of the disk
module (as shown in arrow 1 in Figure 4-33) to ensure that the disk module is
properly inserted into its position.
NOTE
Follow the following rules when installing disk modules in SAS and smart SAS disk
enclosures:
● Coffer disks must be configured in slot 0 to slot 3. Their types and capacities must be
the same, and caution labels must be attached to them. The recommended priority for
choosing the type of coffer disks is SSD > SAS > NL-SAS.
● Non-coffer disks are installed from slot 4. The recommended sequence for installing
non-coffer disks by type is as follows: SSD > SAS > NL-SAS.
– When disk modules are of the same type but different capacities, you are advised
to install those with smaller capacities in first slots.
– When disk modules are of the same type and capacity, you are advised to install
those with smaller rotating speeds in first slots.
● The V5 F series storage systems support only SSDs.
Step 5 (Optional) If interface modules have not been installed, install them according to
the plan, as shown in Figure 4-34 and Figure 4-35.
NOTE
The procedure for installing interface modules of 2 U controller enclosures is the same for
different storage models. The following uses the 2 U controller enclosure of OceanStor
5300 V5 as an example.
----End
Follow-up Procedure
NOTICE
If there are vacant disk slots after all disks have been installed, install filler panels
into the vacant slots for proper heat dissipation.
Prerequisites
The following installation tools and materials have been prepared:
● M3 and M6 screws
● Phillips screwdriver (M3 to M6)
● Marker
● Protective gloves
● Cable trays and trays
● Square-hole positioning pins (for square-hole mounting bars)
● Round-hole positioning pins (for round-hole mounting bars)
Context
● If each controller is equipped with more than three interface modules, install
a cable tray to facilitate maintenance and cabling of interface modules.
● You are advised to install a cable tray 1 U (1 U = 44.45 mm) under the
controller enclosure.
Procedure
Step 1 Determine the position for a cable tray. If the position is covered by a filler panel,
mark the position.
Step 2 Extend the adjustable guide rail of the cable tray until positioning pins are inserted
into the rear column.
Step 3 Use M6 screws to secure the adjustable guide rail, as shown in Figure 4-36.
Step 4 Use a Phillips screwdriver to fasten the M3 screws to secure the tray in place, as
shown in Figure 4-37.
NOTE
If the tray is too close to the controller enclosure, perform Step 5 and Step 6 to adjust the
length of the cable tray for convenient cable trimming.
Step 5 (Optional) Loosen the M3 screws on the cable tray and adjust the position of the
guide rail for convenient cable trimming, as shown in Figure 4-38.
Step 6 (Optional) Fasten the M3 screws to secure the guide rail in place, as shown in
Figure 4-39.
----End
4.2.5.1 Installing Ball Bearing Guide Rails (for High-Density Disk Enclosures)
After determining installation positions of storage devices in the cabinet, install
ball bearing guide rails for supporting the high-density disk enclosures. If you do
not need to install high-density disk enclosures, skip this section.
Prerequisites
The following installation tools and materials are ready:
● M3 to M6 Phillips screwdriver
● Marker
● M6 screw
● M4 screw
● M3 screw
● Installation templates
● Ball bearing guide rail components (including ball bearing guide rails, M3
screws, M4 screws, M6 screws, and installation templates)
Context
NOTICE
NOTE
Before performing the installation, you are advised to count several U scales upward from
the position of the first scale at the bottom of the mounting bar, and then mark the
position to ensure that the front and rear heights of the ball bearing guide rails are the
same.
● You are advised to install storage devices in the cabinet from bottom up.
● Configure a pair of ball bearing guide rails for each high-density disk
enclosure.
● The ball bearing guide rails can be extended from 600 mm to 915 mm.
Procedure
Step 1 Pull out the inner rail of the ball bearing guide rails, as shown in Figure 4-40.
1. Pull out the inner rail until the buckle is exposed.
2. Press the buckle and pull out the inner rail from the ball bearing guide rail.
See step (2) in Figure 4-40.
Put the removed inner rail into an ESD bag. The inner rail will be used in installing
a high-density disk enclosure.
NOTE
For the right ball bearing guide rail, press the buckle downward. For the left ball bearing
guide rail, press the buckle upward.
Step 2 Pull out the rail bracket of a ball bearing guide rail, as shown in Figure 4-41.
1. Loosen the four M3 screws on the ball bearing guide rails shown in (1) of
Figure 4-41.
2. Remove the rail bracket, as shown in (2) of Figure 4-41.
The rail bracket will be used to fix the cable tray.
Step 3 Install the left inner rail (identified by L) of the ball bearing guide rails.
1. Loosen the two M4 screws on the external rail of the ball bearing guide rail,
adjust the length of ball bearing guide rail.
NOTE
Align the ball bearing guide rails with the mounting bar of the cabinet in advance. If
the distance is not longer than 10 mm between the front and rear brackets of the ball
bearing guide rails and the front and rear ends of the mounting bar, loosen the two
M4 screws on the external rail of the ball bearing guide rail (pull out the middle guide
rail to expose the two M4 screws on the ball bearing guide rail), as shown in Figure
4-42. If the distance is longer than 10 mm, remove the two M4 screws and align the
distance.
2. Align the bottom edge of the ball bearing guide rail with the integer U scales
on the front mounting bar, and insert the front positioning pins of the ball
bearing guide rail into the square holes. Use M6 screws to fix the front
bracket of the ball bearing guide rail, as shown in Figure 4-43.
3. Stretch the rear bracket of the ball bearing guide rail and insert the rear
positioning pins into the square holes of the rear mounting bar. Use M6
screws to secure the guide rail in place, as shown in Figure 4-43.
4. Fasten the two M4 screws on the ball bearing guide rail, as shown in Figure
4-44.
Step 4 Install the right inner rail (identified by R) of the ball bearing guide rails.
The installation method of the right inner rail is similar to Step 3.
Step 5 Install the ball bearing guide rail bracket, as shown in Figure 4-45.
1. Install the rail bracket and slide the bracket to the ball bearing guide rail. See
step (1) in Figure 4-45.
2. Fasten the four M3 screws on the ball bearing guide rail. See step (2) in
Figure 4-45.
NOTE
Fasten two screws at the top and bottom of the bracket of the ball bearing guide rail,
respectively.
Step 6 After the installation, use the installation templates to check the distance between
the left and right guide rails, and ensure that the template can snatch into the ball
bearing guide rails, as shown in Figure 4-46.
NOTE
If the installation templates cannot snatch into the guide rails, loosen the M6 screws on the
guide rails and mounting bars, and slightly adjust the distance between the left and right
guide rails. After the installation templates successfully snatch into the guide rails, fix the
M6 screws.
Figure 4-47 Sliding the ball to the most front end of the middle rail
2. Check whether the middle rail of the ball bearing guide rail is completed
inserted, that is, the edges of the middle rail and external rail are at the same
vertical plane, as shown in Figure 4-48.
NOTE
If the middle guide rail is not in place, high-density disk enclosures may fail to be pushed in
or pulled out smoothly later. Release the inner rail latch to push the rail into the guide rail.
Figure 4-48 Sliding the middle rail to align it with the edges of the external rail
----End
Prerequisites
● Ensure that the following conditions are met before installing a high-density
disk enclosure:
– The installation environment meets requirements.
– Ball bearing guide rails used for sliding a high-density disk enclosure into
a cabinet have been installed.
● The following installation tools and materials are ready:
– Phillips screwdrivers
– M6 screws
– M4 screws
– M3 screws
– Protective gloves
– High-density disk enclosures
Precautions
WARNING
To prevent personal injury and device damage, arrange for at least three persons
to carry and install an unloaded enclosure into the cabinet and install disk
modules into the enclosure.
If you remove disks to facilitate the movement and installation of the device,
record the mapping between each disk and its slot in advance. This helps you
insert each disk back to its correct slot after the movement and installation.
● Install components into a cabinet from bottom to top to prevent the cabinet
from falling over.
● If a high-density disk enclosure is installed in the top 4 U space, disks cannot
be inserted.
Procedure
Step 1 Wear protective gloves.
Step 2 Install the inner rail to the right of the high-density disk enclosure.
1. Install the inner rail onto the high-density disk enclosure. See step (1) in
Figure 4-49.
2. Use two M4 screws to secure the inner rail. See step (2) in Figure 4-49.
Step 3 Install the inner rail to the left of the high-density disk enclosure.
Step 4 Remove the two M3 screws from the upper panel, as shown in Figure 4-50.
Step 5 Place the side step at the rear of the high-density disk enclosure on the front
bracket of the ball bearing guide rails, and slide the disk enclosure into the cabinet
along the ball bearing guide rails (no manual alignment is required because the
inner rail automatically connects to the middle rail), as shown in Figure 4-51.
NOTICE
● Do not pull out the middle guide rails when sliding the high-density disk
enclosure into the cabinet. Otherwise, the guide rails may misalign.
● Before you install disk modules, install the high-density disk enclosure into the
cabinet.
Step 9 Repeat Step 2 to Step 8 to install other high-density disk enclosures into the
cabinet.
----End
Prerequisites
● All high-density disk enclosures have been installed.
● The following installation tools and materials are ready:
– M3 screws
– Phillips screwdrivers
– Protective gloves
– Cable trays
Procedure
Step 1 Arrange cable trays so that both ends of each cable tray are on the same side, as
shown in Figure 4-54.
Step 2 Insert the two sides of the left cable tray to the same side of the ball bearing
guide rail and the high-density disk enclosure.
1. Insert the upper left of the cable tray into the high-density disk enclosure. See
step (1) in Figure 4-55.
2. Insert the lower left of the cable tray into the bracket of the ball bearing
guide rail. See step (2) in Figure 4-55.
NOTE
● In Figure 4-55, the "L" in a cable tray indicates that the cable tray must be installed on
the left side of the high-density disk enclosure from the rear view.
● In Figure 4-55, the "R" in a ball bearing guide rail indicates the right side of the cabinet
from the front view.
Step 3 Use a Phillips screwdriver to fasten M3 screws to secure the left cable tray.
1. Use a Phillips screwdriver and M3 screws to secure the lower left of the cable
tray. See step (1) in Figure 4-56.
2. Adjust the lower left of the cable tray so that the bottom of the cable tray is
against the limiting latch. See step (2) in Figure 4-56.
3. Use a Phillips screwdriver and M3 screws to secure the upper left of the cable
tray. See step (3) in Figure 4-56.
Step 4 Insert the two sides of the right cable tray to the same side of the ball bearing
guide rail and the high-density disk enclosure.
1. Insert the upper right of the cable tray into the high-density disk enclosure.
See step (1) in Figure 4-57.
2. Insert the lower right of the cable tray into the bracket of the ball bearing
guide rail. See step (2) in Figure 4-57.
NOTE
● In Figure 4-57, the "R" in a cable tray indicates that the cable tray must be installed on
the right side of the high-density disk enclosure from the rear view.
● In Figure 4-57, the "L" in a ball bearing guide rail indicates the left side of the cabinet
from the front view.
Step 5 Use a Phillips screwdriver to fasten M3 screws to secure the right cable tray.
1. Use a Phillips screwdriver and M3 screws to secure the lower right of the
cable tray. See step (1) in Figure 4-58.
2. Use a Phillips screwdriver and M3 screws to secure the upper right of the
cable tray. See step (2) in Figure 4-58.
Repeat the previous steps to route and bind cables onto the left cable tray.
NOTE
● Evenly divide the cables connected to the storage device into two groups. Place the left
group of cables into the troughs of the left cable tray, and the right group into those of
the right.
● To route a 5 m mini SAS HD electrical cable across three cabinets, use the underfloor
and side cabling methods, and do not use the overhead cabling method.
Step 7 Install the spring pins to the left and right cable trays to secure them.
1. Pull up the spring pin, as shown in step (1) in Figure 4-60.
2. Adjust the cable trays to allow the stretchable guide rail of one cable tray to
insert into the support of the other cable tray, as shown in step (2) in Figure
4-60.
When the spring pin aligns with the hole in the support, the spring pin can
automatically disconnect, and the installation of the spring pin is completed.
Prerequisites
The following installation tools and materials are ready:
Procedure
Step 1 Loosen the two screws on the panel and pull out the high-density disk enclosure,
as shown in Figure 4-61.
Step 2 Open the high-density disk enclosure. Insert disks to coffer disk slots A0, A1, A2,
and A3. Then insert disks from left to right (0 to 14) and from inside to outside (E
to A). After disk modules are inserted into the vacant slots according to the arrow
direction, buckle up the handle, as shown in Figure 4-63.
Disk slots of high-density disk enclosures are numbered from 0 to 14 from left to
right and from E to A from inward to outward, as shown in Figure 4-62.
Step 3 (Optional) Attach the caution labels to the coffer disks. The caution labels of
coffer disks of a high-density disk enclosure are attached on slots A0, A1, A2 and
A3.
NOTE
If the caution labels have been attached to the coffer disks, skip this step.
----End
Follow-up Procedure
NOTICE
To ensure well heat dissipation, insert disks into a system subrack from the rear to
front, and install filler panels into the vacant slots if there are any.
Prerequisites
The following installation tools and materials are ready:
Procedure
Step 1 Wear an ESD wrist strap.
Step 2 Take the replacement data switch out of its ESD bag and place it on the ESD
table.
Step 3 Install grounding wires and mounting ears on the replacement data switch, as
shown in Figure 4-64.
1. Use the Phillips screwdriver to install the ground cable on the side panel of
the data switch.
2. Use the Phillips screwdriver to install mounting ears on the left and right
panels of the data switch.
Step 4 Install the floating nut to the mounting bar of the cabinet.
1. Install four floating nuts on the front mounting bar, two on each side.
2. Install four floating nuts on the rear mounting bar, two on each side.
Step 5 Install the data switch to the cabinet, as shown in Figure 4-65.
1. Push the data switch into the cabinet.
2. Use M6 screws to fix the data switch on the cabinet.
3. Verify that the data switch is horizontally installed and firmly secured.
NOTE
To facilitate future maintenance, attach labels to data switches 0 and 1 to distinguish them
after the networking is complete.
----End
Prerequisites
● Before installing a filler panel, ensure that the floating nuts are properly
installed on the mounting bar.
● The following installation tools have been prepared:
– M6 screws
– M3 to M6 Phillips screwdriver
Procedure
Step 1 Install the filler panel on the cabinet with M6 screws, as shown in Figure 4-66.
----End
NOTE
If the operation space is limited, you can use a fiber extractor to remove and insert LC
optical fibers, pluggable optical modules, and unshielded network cables. For details about
how to connect cables, see 7.12 Replacing an Optical Fiber, Optical Module, Electrical
Module, or Network Cable Using a Fiber Extractor.
Prerequisites
The following installation tools and materials have been prepared:
● Ground cable
● Phillips screwdriver (M3 to M6)
● M5 screw
● Diagonal pliers
Context
● If AC power is supplied, 2 U controller enclosures, 4 U controller enclosures, 2
U disk enclosures, and 4 U disk enclosures do not need to be grounded. If DC
power is supplied, disk enclosures and controller enclosures must be
grounded.
● If high-density disk enclosures are used, they must be grounded.
● Figure 4-67, Figure 4-68, Figure 4-69, Figure 4-70, Figure 4-71, and Figure
4-72 show the ground screw holes of a 2 U controller enclosure, smart disk
enclosure, and SAS disk enclosure.
Procedure
Step 1 Use a Phillips screwdriver to remove the ground screw next to the power module.
Step 2 Fasten one OT terminal of the ground cable to the ground screw hole on the
device using a ground screw, as shown in Figure 4-73 and Figure 4-74.
Figure 4-73 Connecting a ground cable (for a SAS disk enclosure or a high-density
disk enclosure)
Figure 4-74 Connecting a ground cable (for a controller enclosure or a smart disk
enclosure)
Step 3 Repeat Step 1 and Step 2 to connect the other OT terminals of the ground cables
to the ground terminals on the cabinet.
NOTE
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
Prerequisites
● The disk enclosure connection plan has been worked out.
● The following installation tools and materials have been prepared:
– Mini SAS HD electrical cables or mini SAS HD optical fibers
– Diagonal pliers
– Cable ties
NOTE
Electrical and optical cables of mini SAS HD are removed and inserted in the same manner.
The following uses mini SAS electrical HD cables as an example.
Procedure
Step 1 Attach labels to mini SAS HD cables.
1. Prepare the mini SAS HD cables for connecting controller enclosures to disk
enclosures.
Mini SAS HD cables shipped with the device have been coiled. Uncoil the
cables based on site requirements to prevent unnecessary cable arrangement
and binding.
2. Prepare labels for guiding cable connections based on the disk enclosure
connection planning.
– The label for connections between a 2 U controller enclosure and a
standard disk enclosure is CTEx-A/Bx-Px TO DAExxx-A/B-Px.
– That between a 2 U controller enclosure and a high-density disk
enclosure is CTEx-A/Bx-Px TO DAExxx-A/B-PRIx.
– That between a 4 U controller enclosure and a disk enclosure is CTEx-
H/Lx-Px TO DAExxx-A/B-Px.
– That between standard disk enclosures is DAExxx-A/B-Px TO DAExxx-A/B-
Px.
– That between high-density disk enclosures is DAExxx-A/B-EXPx TO
DAExxx-A/B-PRIx.
The following table explains the label.
For example: CTE0-A-P0 TO DAE000-A-P0 indicates that one end of the cable
connects to port P0 on the onboard expansion module of controller A in a 2 U
controller enclosure (ID: 0), and the other end connects to port P0 on
expansion module A in disk enclosure 0. CTE0-B1-P0 TO DAE000-B-P0
indicates that one end of the cable connects to port P0 on the expansion
module in slot IOM1 of controller B in a 2 U controller enclosure (ID: 0), and
the other end connects to port P0 on expansion module B in disk enclosure 0.
CTE0-H6-P0 TO DAE000-A-P0 indicates that one end of the cable connects to
port P0 of the expansion module in slot IOM6 on the H plane of a 4 U
controller enclosure (ID: 0), and the other end connects to port P0 on
expansion module A in disk enclosure 0.
Figure 4-75 shows an example of filling in a label.
3. Attach a pair of labels to both ends of a mini SAS HD cable. For details about
how to attach a label, see 7.11 Engineering Label Specifications for Cables.
Step 2 Connect disk enclosures following the connection plan, as shown in Figure 4-76 or
Figure 4-77.
NOTICE
Step 3 Adjust the length of the mini SAS HD cables by wrapping them into circles
according to the distance away from the system bay, and use a cable tie to bind
them and use diagonal pliers to trim off the excess of cable ties, as shown in
Figure 4-78.
NOTE
After mini SAS HD cables are connected, fix extra cables onto the cable tray at the rear of
the system bay by using fiber binding tapes.
NOTE
● For details about how to lay out and bind cables, see 7.8 General Cable Routing
Principles and 7.9 Cable Routing and Binding Basics.
● When connecting cables of a high-density disk enclosure, lay out the cables along the
cable tray and guide rails neatly.
----End
Prerequisites
● The disk enclosure connection plan has been worked out.
● The following installation tools and materials have been prepared:
– RDMA cables
– Diagonal pliers
– Cable ties
Procedure
Step 1 Attach labels to RDMA cables.
1. Prepare the RDMA cables for connecting controller enclosures to disk
enclosures.
RDMA cables shipped with the device have been coiled. Uncoil the cables
based on site requirements to prevent unnecessary cable arrangement and
binding.
2. Prepare labels for guiding cable connections based on the disk enclosure
connection planning.
The label for connections between a 2 U controller enclosure and a disk
enclosure is CTEx-A/Bx-Px TO DAExxx-A/B-Px, that for connections between a
4 U controller enclosure and a disk enclosure is CTEx-H/Lx-Px TO DAExxx-A/B-
Px, and that for connections between disk enclosures is DAExxx-A/B-Px TO
DAExxx-A/B-Px. The following table explains the label.
For example: CTE0-A-P0 TO DAE000-A-P0 indicates that one end of the cable
connects to port P0 on the onboard expansion module of controller A in a 2 U
controller enclosure (ID: 0), and the other end connects to port P0 on
expansion module A in disk enclosure 0. CTE0-B1-P0 TO DAE000-B-P0
indicates that one end of the cable connects to port P0 on the expansion
module in slot IOM1 of controller B in a 2 U controller enclosure (ID: 0), and
the other end connects to port P0 on expansion module B in disk enclosure 0.
CTE0-H6-P0 TO DAE000-A-P0 indicates that one end of the cable connects to
port P0 of the expansion module in slot IOM6 on the H plane of a 4 U
controller enclosure (ID: 0), and the other end connects to port P0 on
expansion module A in disk enclosure 0.
Figure 4-79 shows an example of filling in a label.
3. Attach a pair of labels to both ends of an RDMA cable. For details about how
to attach a label, see 7.11 Engineering Label Specifications for Cables.
Step 2 Connect disk enclosures following the connection plan, as shown in Figure 4-80,
Figure 4-81, Figure 4-82, and Figure 4-83.
NOTICE
Step 3 Adjust the length of the RDMA cables by wrapping them into circles according to
the distance away from the system bay, and use a cable tie to bind them and use
diagonal pliers to trim off the excess of cable ties, as shown in Figure 4-84.
NOTE
After RDMA cables are connected, fix extra cables onto the cable tray at the rear of the
system bay by using fiber binding tapes.
NOTE
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
Prerequisites
● You have developed a plan for connection between multiple controller
enclosures. For details on how to develop a connection plan, see 3.1.2.4
(Optional) Connection Planning for Multiple Controller Enclosures.
● The following installation tools and materials have been prepared:
– RDMA cables
– Diagonal pliers
– Cable ties
Procedure
Step 1 Connect controller enclosures following the connection plan, as shown in Figure
4-85, Figure 4-86, Figure 4-87, and Figure 4-88.
NOTICE
NOTE
It takes 2 minutes for the storage system to identify a new cable. Do not remove the cable
during this period. If the storage system fails to identify the cable after 2 minutes, verify
that the cable is in good shape and properly connected, and then reinstall the cable.
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
Prerequisites
● The connection between the controller enclosure and the application server
has been completed. For details about the connection solution design, see
3.1.2.5 Connection Planning Between Controller Enclosures and
Application Servers.
● If Fibre Channel switches are used, the NPIV function of these switches has
been enabled. For details about how to query and set the NPIV function of a
switch, see 6.2 How Do I Query and Configure the NPIV Function of
Switches?
● The ports on the storage device are set to the autonegotiation mode. To keep
a smooth link, the rates of the ports on the storage device and the application
server (or the switch) must be consistent. If the rates are inconsistent,
perform the following:
– Set the rate of a front-end port. See "Modifying an Ethernet Port" and
"Modifying a Fibre Channel Front-End Port" in the Basic Storage Service
Configuration Guide (Block Service) specific to your product model and
version.
– To set the rate of the ports on the application server (or the switch), see
the documents of the application server (or the switch).
● The following installation tools and materials have been prepared:
– In the event of Ethernet networking:
NOTICE
▪ Network cable
▪ Cable tie
▪ Diagonal pliers
– In the event of Fibre Channel networking:
▪ Optical module
▪ Optical fiber
▪ Diagonal pliers
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
DANGER
When installing an optical fiber, do not look into the optical port without eye
protection.
Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothes.
Step 2 (Optional) Install an optical module to the ports on the SmartIO interface module
of the storage system.
NOTE
If ports on the SmartIO interface module are already equipped with optical modules, go to
Step 3.
1. Remove the protective cap from the optical module. See (1) in Figure 4-90.
2. Insert the optical module into the port on the SmartIO interface module. See
(2) in Figure 4-90.
NOTE
Step 3 Remove the protective cap from the optical fiber connector. See (1) in Figure
4-91.
NOTICE
Step 4 Connect one end of the optical fiber to the port on the SmartIO interface module.
See (2) in Figure 4-91.
NOTE
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
If ETH ports on the storage system are already equipped with optical modules, go to Step
3.
1. Remove the protective cap from the optical module. See (1) in Figure 4-92.
2. Insert the optical module into the ETH port. See (2) in Figure 4-92.
NOTE
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
NOTE
The management network port, maintenance network port, and serial port of the smart
disk enclosure are reserved and do not need cable connection.
Prerequisites
The following installation tools and materials have been prepared:
● Network cable
● Cable tie
● Diagonal pliers
Context
● For a 2 U controller enclosure, each controller is configured with a
management network port and a maintenance network port. For a 4 U
NOTICE
● Do not connect the management network port and maintenance network port
to the same LAN or switch to prevent network loops.
● If multiple controller enclosures are deployed, you only need to connect the
management network ports of controller enclosure 0 to the management
network. For details, see 3.1.2.4 (Optional) Connection Planning for Multiple
Controller Enclosures.
● The management network port and the maintenance terminal can correctly
communicate with each other (the management network port and the
maintenance terminal reside on the same network segment or reside on
different network segments but are connected via a route).
Procedure
Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothes.
Step 2 Prepare a network cable for connecting the management network port on the
controller enclosure to the network port on the maintenance terminal, and label
the cable. For details about how to prepare and attach labels, see 7.11
Engineering Label Specifications for Cables.
Step 3 Locate the network cables that are used to connect the management network
ports (MGMT) on the controller enclosure.
Step 4 Connect the network cables to the management network ports, as shown in
Figure 4-95, Figure 4-96, Figure 4-97, Figure 4-98, Figure 4-99, and Figure
4-100.
A B
NOTE
Ensure that the management network ports of the two controllers in the controller
enclosure are connected to the LAN.
A B
NOTE
Ensure that the management network ports of the two controllers in the controller
enclosure are connected to the LAN.
A B
NOTE
Ensure that the management network ports of the two controllers in the controller
enclosure are connected to the LAN.
A B
NOTE
Ensure that the management network ports of the two controllers in the controller
enclosure are connected to the LAN.
A B
NOTE
Ensure that the management network ports of the two controllers in the controller
enclosure are connected to the LAN.
NOTE
● Ensure that the management network ports of the two management modules are
connected to the LAN.
● For a 4 U controller enclosure, connect only management network port 0 of the two
management modules to the LAN.
NOTE
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
NOTICE
Only serial cables can be inserted into the serial port. Do not insert network cables
into the serial port position.
NOTE
The management network port, maintenance network port, and serial port of the smart
disk enclosure are reserved and do not need cable connection.
Context
There are two types of serial cables: RJ-45 to DB9 serial cable and double RJ-45
serial cable. The type of serial cable to be used depends on the type of the serial
port on the maintenance terminal. Typically, the storage system is connected to a
maintenance terminal through an RJ-45 to DB9 serial cable, as shown in Figure
4-101, Figure 4-102, Figure 4-103, Figure 4-104, Figure 4-105, and Figure
4-106.
NOTE
If you use an RJ-45 to DB9 serial cable, connect the RJ-45 connector to the storage system,
and connect the DB9 connector to the maintenance terminal.
Procedure
Step 1 Wear an ESD wrist strap, ESD gloves, and ESD clothes.
Step 2 Prepare a serial cable used to connect the serial port on the controller enclosure
and a network port on the maintenance terminal, and label the cable. For details
about how to prepare and attach labels, see 7.11 Engineering Label
Specifications for Cables.
Step 3 Connect the RJ-45 end of an RJ-45 to DB9 serial cable to a serial port on the
controller enclosure.
Step 4 Connect the DB9 end of the RJ-45 to DB9 serial cable to the serial port on the
maintenance terminal.
----End
Context
NOTE
● AC devices can only be connected to AC power supplies, and DC devices can only be
connected to DC power supplies.
● Both AC and DC power modules can connect to two power supply routes. To ensure
high availability and avoid unexpected power supply failure caused by external power
supply faults, connect to two separate power supply routes.
● To prevent the power supply failure of a storage device from causing other devices
connected to the circuit breaker to abnormally power off, see Table 7-11 for details
about the current specifications for the circuit breaker of external power supplies to
which the storage system is connected.
Prerequisites
The storage system is disconnected from the external power supply.
Context
● Generally, PDUs are divided into groups. Power of each group is determined
by the specifications of protection components configured for each group.
When power cables of storage devices are connected to PDUs, the power of
the devices connected to each group should not exceed the maximum power
of the group, avoiding overload caused by excessive power on one PDU.
● The AC power module of the storage system supports dual power supplies. To
ensure high availability and avoid unexpected power supply failure caused by
external power supply faults, connect to two separate power supply routes. In
this way, if one power supply fails, the other provides power for the device to
ensure power stability.
● The input AC voltage must range from 100 V to 127 V or 200 V to 240 V.
● To avoid unexpected power loss of storage systems connected to the same
circuit breaker when a storage system has failed, the AC of the circuit breaker
must be no less than 10 A.
Procedure
Step 1 Unpack and take out power cables.
Step 2 Connect the controller enclosure to the power sockets on the cabinet through AC
power cables.
Step 3 Repeat Step 1 and Step 2 to connect disk enclosures to the power sockets on the
cabinet through AC power cables.
Step 4 Check whether the AC power cables of the controller enclosure and disk
enclosures are correctly connected to the AC power supply.
● Figure 4-107, Figure 4-108, Figure 4-109, Figure 4-110, Figure 4-111, and
Figure 4-112 show how to connect AC power cables of a controller enclosure.
● Figure 4-113, Figure 4-114, Figure 4-115, and Figure 4-116 show how to
connect AC power cables of a disk enclosure.
Before fully closing the retention clip, slide it into a position where it will tightly
secure the power cable.
d. Repeat Step 5.a to Step 5.c to secure other AC power cables.
● For controller enclosures and smart disk enclosures, use velcro tapes to secure
AC power cables.
a. Connect the power cable to the cable port on the AC power module. See
(1) in Figure 4-118.
b. Secure the power cable using a velcro strap. See (2) in Figure 4-118.
c. Repeat Step 5.a and Step 5.b to secure other AC power cables.
NOTE
Adjust the position of the velcro strap to ensure that the velcro strap can fasten the AC
power cable and the connector of the AC power cable is secure.
For details about how to lay out and bind cables, see 7.8 General Cable Routing Principles
and 7.9 Cable Routing and Binding Basics.
----End
Prerequisites
● The storage system is disconnected from the external power supply.
● The following installation tools and materials have been prepared:
– DC power cables
– Diagonal pliers
– Phillips screwdriver
Context
● To ensure power reliability, you need to connect the power cables on two
sides of the storage system to two independent power supplies. When one
fails, the other can supply power.
● The input DC voltage ranges from -48 V to -60 V.
● Using DC power helps prolong the service life of devices. DC power is viewed
as the standard power supply in many industries.
Procedure
Step 1 Connect the controller enclosure to the smart disk enclosure through DC power
cables.
1. Remove the plastic insulation tubes on the cord end terminals of the DC
power cables using the diagonal pliers.
2. Install the power cables on the wiring terminals on the power module until
the cables are secured by the spring and cannot be removed. See Figure
4-119.
– Connect the cord end terminal on the negative power cable (blue) to the
NEG(-) wiring terminal on the power module.
– Connect the cord end terminal on the positive power cable (black) to the
RTN(+) wiring terminal on the power module.
Figure 4-119 Connecting the DC power cables of the smart disk enclosure
NOTE
The colors of DC power cables that connect to the anode and cathode of the DC
power supply are subject to the colors of the DC power cables actually configured in
users' equipment rooms.
3. Unfasten the screws of the DC power cable using the Phillips screwdriver and
put the screws through the shock absorption sheets, washers, and OT
terminal round holes. Connect the OT terminal of the black cable to the RTN
(+) end, and the OT terminal of the blue cable to the NEG (-) end, and then
fasten the screws. See step (2) in Figure 4-120.
NOTE
– When unfastening the screws from the DC power cable, prevent the shock
absorption sheets and washers from sliding off.
– The colors of DC power cables that connect to the anode and cathode of the DC
power supply are subject to the colors of the DC power cables actually configured
in users' equipment rooms.
4. Install the protective cover on the DC power module. See step (3) in Figure
4-120.
Step 3 Check whether the DC power cables of the controller enclosure and disk
enclosures are correctly connected to the DC power supply. Figure 4-121, Figure
4-122, Figure 4-123, Figure 4-124, and Figure 4-125 show how to connect DC
power cables.
Step 4 Lay out and bind DC power cables. For details, see 7.8 General Cable Routing
Principles and 7.9 Cable Routing and Binding Basics.
----End
Procedure
Step 1 Check the overall operating status of the storage system.
Filler The vacant slots in the cabinet are The vacant slots in the
panel covered with filler panels. cabinet are not covered with
filler panels.
Overall ● All devices are stably installed ● One or more devices are
effect without displacement. displaced.
● All devices are tightly screwed. ● One or more devices are
slanted.
● The screws are loose or
lost.
2 All cables are arranged smoothly, with no roundabout twists and turns.
4 The trough is needed for cabling outside the cabinet. Do not make the
cables overflow the trough.
5 The radius of the routed optical fibers must be greater than or equal to
50 mm.
6 The power cable and the ground cable are bent smoothly.
7 The power cable and the ground cable are connected correctly and
firmly.
8 The ground cable of the cabinet door should be connected correctly and
reliably.
9 The diameters of the power cable and the ground cable meet the
power distribution requirements.
10 The external power cable and ground cable are arranged separately
from signal cables, with a space of larger than 30 mm.
13 The fiber should not be routed by force or bent unnaturally. The fibers
should not be compressed by other cables after fiber routing.
No. Item
17 All cables are properly bound. The space between the cable ties is even,
and the remaining parts of the cable ties are cut off neatly. All cable
ties face the same direction. The overall appearance is neat.
18 Power cables and ground cables use the entire copper core and contain
no joint.
19 Power cables and ground cables should be labeled neatly toward the
same direction for convenient view.
20 The DC power cables are blue and black, whereas the ground cable is
olive or yellow.
----End
NOTE
● In V500R007C70 Kunpeng and later versions, after the first power-on and initialization,
the controller enclosures support remote power-on in later operations. For the first
power-on and initialization, you must use the power button on the controller enclosures.
● To remotely power on multiple controller enclosures of a storage system, ensure that
you have connected the controller enclosures according to the diagrams in 3.1.2.4
(Optional) Connection Planning for Multiple Controller Enclosures.
● For details on remote power-on, see "Powering On the Storage System (Remotely on
the CLI, Applicable to V500R007C70 and Later Versions)" in the Administrator Guide
specific to your product model.
Prerequisites
Ensure that all devices are properly installed and device installation check is
completed. Otherwise, power on storage devices only after they are correctly
installed.
Context
NOTICE
If the power of a backup battery unit (BBU) is insufficient, the BBU automatically
charges when the storage system is powered on for the first time, and the
Running/Alarm indicator on the BBU is blinking green. When a BBU is fully
charged, its Running indicator is steady green.
Typically, an AC power distribution box (PDB) is configured on the top of a
cabinet. If an AC PDB is not configured, skip the information related to PDBs.
Figure 4-126 shows an AC PDB.
NOTE
Procedure
Step 1 (Optional) If a PDB is configured, check the labels on power cables and match the
power cables with power switches in the PDB.
For example, if the label on the AC power cable connected to a controller
enclosure says PowerBox Output B_8, it indicates that the power cable of the
controller enclosure corresponds to power switch SW8 on module Output B. You
can turn on that power switch to power on the controller enclosure.
Step 2 (Optional) If a PDB is configured, turn on the power switches corresponding to all
the devices in sequence.
Step 3 Press the power button of the controller enclosure.
NOTE
● Install filler panels to the vacant slots, if any, to ensure proper heat dissipation.
● To power on the storage system, press the power button. If the power indicator of the
controller enclosure is blinking green, the storage system is being powered on. Do not
hold down the power button for more than five seconds; otherwise, the storage system
will be powered off.
● The power-on of the storage system takes 15 to 30 minutes.
● After the controller enclosure is powered on, other disk enclosures connected will be
automatically powered on.
● After system power-on, the disk initialization process automatically starts. The time
required for the process is dependent on the quantity of the disks to be initialized.
----End
Follow-up Procedure
NOTE
The following figures and indicators are used only to check whether the system is powered
on properly. For details about indicators, see sections about indicators on components in
the Product Description.
Figure 4-127, Figure 4-128, Figure 4-129, Figure 4-130, Figure 4-131, Figure
4-132, Figure 4-133, and Figure 4-134 show the indicator status after the system
is powered on.
Ensure that the system has been correctly powered on and is working correctly:
NOTE
If data switches are configured, check the status of the indicators on the data switches too.
● The Power indicators on controllers, controller enclosures, and disk enclosures
are steady green.
● The Alarm indicators on controllers, controller enclosures, and disk enclosures
are off.
● The Running indicators on coffer disks are steady green, and the Alarm/
Location indicators are off.
– Disks with coffer disk labels are coffer disks.
– Before services are configured, the Running indicators on the first three
coffer disks are blinking green, and the Alarm/Location indicators are off.
If any Alarm indicator is on, the device is faulty and you need to rectify the fault.
For details about how to rectify faults, see the Troubleshooting Guide of the
storage system. If a power indicator is not steady green, contact Huawei technical
support engineers.
Prerequisites
The storage system is correctly powered on, and the status of device indicators are
normal.
The following installation tools and materials have been prepared:
● Filler panels for 2 U devices
● Filler panels for 4 U devices
Procedure
Step 1 Take out a filler panel. Align the upper side of the panel with that of the device.
Step 2 Use the panel to cover the front side of the device, as shown in Figure 4-135 and
Figure 4-136. Then, release the handles.
----End
Prerequisites
The maintenance terminal has been connected to the serial port on the storage
device through a serial cable.
Context
● For a 2 U controller enclosure, the default IP addresses of the management
network ports on controller A and controller B are 192.168.128.101 and
192.168.128.102, respectively. The default subnet mask is 255.255.0.0.
● For a 4 U controller enclosure, the default IP address of network port 0 on
management module 0 is 192.168.128.101 and that of network port 0 on
management module 1 is 192.168.128.102. The default subnet mask is
255.255.0.0.
● When a single controller enclosure is deployed, the default internal heartbeat
IP addresses are 127.127.127.10 and 127.127.127.11 for a dual-controller
storage system, and the subnet mask is 255.255.255.0; the default internal
heartbeat IP addresses are 127.127.127.10, 127.127.127.11, 127.127.127.12,
and 127.127.127.13 for a four-controller storage system, and the subnet
mask is 255.255.255.0.
NOTE
When multiple controller enclosures are deployed, the default internal heartbeat IP
addresses of each controller enclosure are the same as those when a single controller
enclosure is deployed.
● The default IP address of the maintenance network port is 172.31.128.101 or
172.31.128.102, and the default subnet mask is 255.255.0.0.
After the controller enclosure is connected to the maintenance terminal using a
serial cable, you can log in to the CLI of the storage device using a terminal
program (such as PuTTY).
NOTE
● This document uses PuTTY as an example. You can download PuTTY from the chiark
website.
● To ensure successful login to the storage system, you are advised to use PuTTY of the
latest version.
Precautions
● After the IP addresses of the management network ports are modified,
communication between the maintenance terminal and the storage device
will be lost. Therefore, you are advised to first modify the IP addresses of
controllers' management network ports that are not directly connected to the
maintenance terminal.
● The IP addresses of management network ports and internal heartbeat IP
addresses must be on different network segments. When a single controller
enclosure is deployed, for a dual-controller system, you cannot use IP
addresses that belong to the 127.127.127.XXX network segment; for a four-
controller storage system, you cannot set IP addresses that belong to the
127.127.127.XXX, 172.16.126.XXX, 172.16.127.XXX, and 172.16.128.XXX
network segments.
NOTE
● Heartbeats are packets transmitted between two devices for them to judge the
availability of the peer device. Heartbeats do not require acknowledgement. They are
usually used for node communication, fault diagnosis, and event triggering in an HA
system.
● Internal heartbeat links are established between controllers for these controllers to
detect each other's working status. You do not need to separately connect cables. In
addition, internal heartbeat IP addresses are configured before delivery, and cannot be
modified.
● When multiple controller enclosures are deployed, the default internal heartbeat IP
addresses of each controller enclosure are the same as those when a single controller
enclosure is deployed.
● The IP addresses of both management network ports and those of
maintenance network ports must be on different network segments. You
cannot use IP addresses that belong to the 172.31.XXX.XXX. Otherwise, route
conflicts may occur. You are advised to connect only the management
network port to the network.
● By default, IP addresses of the management network ports and those of the
service network ports are on different network segments. If they are in the
same network segment, some functions of the storage system may be
unavailable. It is strongly recommended that you do not set them on the
same network segment.
Procedure
Step 1 Run PuTTY.
The PuTTY Configuration dialog box is displayed.
Step 2 Set Connection type to Serial. In the Serial line text box, enter the name of the
serial port that connects the maintenance terminal to the storage system, for
example, COM1. In Speed, enter 115200.
You can query the serial port that connects the maintenance terminal to the
storage system as follows (Windows 7 is used as an example):
Figure 5-2 Successful connection between the controller and the maintenance
terminal
2. Enter the username and password for logging in to the storage device.
NOTE
● The default user name is admin. For the default password, refer to the OceanStor
V500R007 Account List.
● You are advised to change the default login password immediately after you log in to
the storage system for the first time and periodically change the password since then.
For details about how to change the login password, see the Administrator Guide.
● For security reasons, the entered password is not displayed.
NOTE
Values of System Name, Product Model, and Product Version vary according to the login
device. If the login fails and the system enters the minisystem mode, continue by following
the prompts that appear.
NOTICE
Ensure that the IP addresses of the two management network ports are modified.
For example:
Set the IPv4 address of the management network port on management module 0
to 172.16.190.2, subnet mask to 255.255.0.0, and gateway address to 172.16.0.1.
admin:/>change system management_ip eth_port_id=CTE0.SMM0.MGMT0 ip_type=ipv4_address
ipv4_address=172.16.190.2 mask=255.255.0.0 gateway_ipv4=172.16.0.1
WARNING: You are going to modify the network address of network port. If you enter an unavailable
network address, the O&M interface of the storage system is inaccessible.
Suggestion: Before you perform this operation, ensure that you have entered an available network address.
NOTE
● After changing the IP address of the management network port, run the show system
management_ip command to verify the IP address information about the management
network port.
● Modifying the IP address of a management port may disconnect the maintenance
terminal from the storage system. Do not modify the IP address of a management
network port unless necessary.
----End
Prerequisites
The temporary maintenance terminal used for initial configuration has been
connected to the storage device's management port, and the maintenance
terminal IP address and management port's default IP address are on the same
network segment.
Check that the maintenance terminal meets the requirements of DeviceManager
before using it.
● Operating system and browser versions of the maintenance terminal are
supported.
DeviceManager supports multiple types of operating systems and browsers.
For details, access Huawei Storage Interoperability Navigator to query.
● The maintenance terminal communicates with the storage system properly.
● The super administrator can only log in to the storage system as a local user.
● To use a lightweight directory access protocol (LDAP) domain user account to
log in to DeviceManager, you must configure the LDAP domain server first,
then set the LDAP server parameters and create an LDAP domain user
account on the storage system.
● By default, DeviceManager allows a maximum of 32 users to log in
concurrently.
Context
● DeviceManager only supports TLS protocols 1.1, 1.2, and 1.3.
NOTE
The super administrator can run change devicemanager tls min_version=? to change the
earliest version of TLS supported by DeviceManager. Then, the super administrator must
run reboot storage service service_name=devicemanager to restart DeviceManager for
the change to take effect.
● For a 2 U controller enclosure, the default IP addresses of the management
network ports on controller A and controller B are 192.168.128.101 and
192.168.128.102, respectively. The default subnet mask is 255.255.0.0.
● For a 4 U controller enclosure, the default IP address of network port 0 on
management module 0 is 192.168.128.101 and that of network port 0 on
management module 1 is 192.168.128.102. The default subnet mask is
255.255.0.0.
● The default user name of the super administrator is admin. For the default
password, refer to the OceanStor V500R007 Account List.
● This section uses the Windows operating system as an example to explain
how to log in to DeviceManager. The login operations on other operating
systems are similar.
● If a user does not perform any operations after logging in to the system for a
period longer than the timeout limit (the limit is 30 minutes by default and
modifiable), the system logs out automatically.
● If an account is not used to log in to the system for a certain period of time
(the period is 60 days by default and modifiable), it will be locked and can
only be unlocked by the super administrator.
Procedure
Step 1 Run Internet Explorer on the maintenance terminal.
The super administrator can only log in to the storage system as a local user.
– LDAP user: Log in to the storage system using LDAP domain
authentication.
You can log in to the storage system in LDAP domain authentication
mode only after the LDAP server is properly configured.
NOTE
Step 4 Type your user name and password in Username and Password respectively.
NOTE
● If you enter wrong passwords for consecutive two times, you need to enter the
verification code. In Verification Code, enter the correct verification code.
● If LDAP User is selected, enter the domain user name and password as well as the
domain name.
– For a domain user of domain authentication server 0, the user can log in to
DeviceManager of a storage system typing domain or a combination of the dc
field in the domain authentication server's base DN in Domain Name.
– For a domain user of domain authentication server 1, 2, or 3, the user can log in to
DeviceManager of a storage system only typing a combination of the dc field in
the domain authentication server's base DN in Domain Name.
1. If the base DN of the domain authentication server contains only one dc field, the dc
field is used as the combination of the dc field in the domain authentication server's
base DN.
For example, if the base DN of the domain authentication server is
ou=applications,dc=bigcorp, bigcorp is the combination of the dc field in the
domain authentication server's base DN.
2. If the base DN of the domain authentication server contains multiple dc fields, they
are combined and then separated by a period (.) to serve as the combination of the
dc field in the domain authentication server's base DN.
For example, if the base DN of the domain authentication server is
ou=applications,dc=bigcorp,dc=com, bigcorp.com is the combination of the dc
field in the domain authentication server's base DN.
● The default user name of the local super administrator is admin. For the default
password, refer to the OceanStor V500R007 Account List.
● If you forget the password as an administrator or a read-only user, the super
administrator can run change user to reset the password. If you forget the password as
a super administrator (admin by default), the root administrator _super_admin can log
in to the CLI through a serial port and run initpasswd to reset the password. For details,
see "Resetting the Password of an Administrator or a Read-Only User" or "Resetting the
Password of a Super Administrator" in the Administrator Guide.
● If you enter incorrect passwords for a specified number of times (3 by default, equal to
the value specified in Number of Incorrect Passwords on the Login Policy page), the
account is automatically locked for 5 minutes. For details on setting the lock period, see
"Configuring a Security Policy for System User" in the Administrator Guide.
● You are advised to change the default login password immediately after you log in to
the storage system for the first time and periodically change the password since then.
For details about how to change the password, see "Changing Password" in the
Administrator Guide.
NOTE
● To view online help, click in the upper right corner. The online help provides details
about each step and operation.
2 Status bar Shows the name and login time of the currently logged-in
user.
----End
Prerequisites
A Wi-Fi network that is connected to the storage system's management network
is available onsite.
Context
● DeviceManager only supports TLS protocols 1.1, 1.2, and 1.3.
● Customers can use a tablet to log in to the storage system through their
wireless routers. You can use iPad Air (Safari) and HUAWEI MediaPad 10 FHD
(Chrome) to log in to the storage system. This section uses iPad as an
example to describe how to log in to DeviceManager. The login operations on
other operating systems are similar. The login operations on other mobile
terminals are similar.
● For a 2 U controller enclosure, the default IP addresses of the management
network ports on controller A and controller B are 192.168.128.101 and
192.168.128.102, respectively. The default subnet mask is 255.255.0.0.
● For a 4 U controller enclosure, the default IP address of network port 0 on
management module 0 is 192.168.128.101 and that of network port 0 on
management module 1 is 192.168.128.102. The default subnet mask is
255.255.0.0.
● The default user name of the super administrator is admin. For the default
password, refer to the OceanStor V500R007 Account List.
● By default, DeviceManager allows a maximum of 32 users to log in
concurrently.
● If a user does not perform any operations after logging in to the system for a
period longer than the timeout limit (the limit is 30 minutes by default and
modifiable), the system logs out automatically.
● If an account is not used to log in to the system for a certain period of time
(the period is 60 days by default and modifiable), it will be locked and can
only be unlocked by the super administrator.
Procedure
Step 1 Connect the iPad to the Wi-Fi network.
1. On the iPad desktop, choose Settings > WLAN.
The WLAN page is displayed.
2. In the CHOOSE A NETWORK area, select the Wi-Fi network.
The Enter Password page is displayed.
3. Enter the password of the Wi-Fi network in the Password text box.
4. Click Join.
The iPad is connected to the Wi-Fi network.
– The default user name is admin. For the default password, refer to the OceanStor
V500R007 Account List.
– If a verification code is required, enter the correct verification code.
– If you forget the password as an administrator or a read-only user, the super
administrator can run change user to reset the password. If you forget the
password as a super administrator (admin by default), the root administrator
_super_admin can log in to the CLI through a serial port and run initpasswd to
reset the password. For details, see "Resetting the Password of an Administrator or
a Read-Only User" or "Resetting the Password of a Super Administrator" in the
Administrator Guide.
– You are advised to change the default login password immediately after you log in
to the storage system for the first time and periodically change the password since
then. For details about how to change the password, see "Changing Password" in
the Administrator Guide.
5. Click Login.
----End
Prerequisites
The temporary maintenance terminal used for initial configuration has been
connected to the storage device's management port, and the maintenance
terminal IP address and management port's default IP address are on the same
network segment.
Context
● For a 2 U controller enclosure, the default IP addresses of the management
network ports on controller A and controller B are 192.168.128.101 and
192.168.128.102, respectively. The default subnet mask is 255.255.0.0.
● For a 4 U controller enclosure, the default IP addresses of the management
network ports on management modules 0 and 1 are 192.168.128.101 and
192.168.128.102, respectively. The default subnet mask is 255.255.0.0.
● When a single controller enclosure is deployed, the default internal heartbeat
IP addresses are 127.127.127.10 and 127.127.127.11 for a dual-controller
storage system, and the subnet mask is 255.255.255.0; the default internal
heartbeat IP addresses are 127.127.127.10, 127.127.127.11, 127.127.127.12,
and 127.127.127.13 for a four-controller storage system, and the subnet
mask is 255.255.255.0.
NOTE
When multiple controller enclosures are deployed, the default internal heartbeat IP
addresses of each controller enclosure are the same as those when a single controller
enclosure is deployed.
● The default IP address of the maintenance network port is 172.31.128.101 or
172.31.128.102, and the default subnet mask is 255.255.0.0.
Precautions
● After the IP addresses of the management network ports are modified,
communication between the maintenance terminal and the storage device
will be lost. Therefore, you are advised to first modify the IP addresses of
controllers' management network ports that are not directly connected to the
maintenance terminal.
● The IP addresses of management network ports and internal heartbeat IP
addresses must be on different network segments. When a single controller
enclosure is deployed, for a dual-controller system, you cannot use IP
addresses that belong to the 127.127.127.XXX network segment; for a four-
controller storage system, you cannot set IP addresses that belong to the
127.127.127.XXX, 172.16.126.XXX, 172.16.127.XXX, and 172.16.128.XXX
network segments.
NOTE
● Heartbeats are packets transmitted between two devices for them to judge the
availability of the peer device. Heartbeats do not require acknowledgement. They are
usually used for node communication, fault diagnosis, and event triggering in an HA
system.
● Internal heartbeat links are established between controllers for these controllers to
detect each other's working status. You do not need to separately connect cables. In
addition, internal heartbeat IP addresses are configured before delivery, and cannot be
modified.
● When multiple controller enclosures are deployed, the default internal heartbeat IP
addresses of each controller enclosure are the same as those when a single controller
enclosure is deployed.
● The IP addresses of both management network ports and those of
maintenance network ports must be on different network segments. You
cannot use IP addresses that belong to the 172.31.XXX.XXX. Otherwise, route
conflicts may occur. You are advised to connect only the management
network port to the network.
● By default, IP addresses of the management network ports and those of the
service network ports are on different network segments. If they are in the
same network segment, some functions of the storage system may be
unavailable. It is strongly recommended that you do not set them on the
same network segment.
Procedure
Step 1 Log in to DeviceManager.
Step 3 Click the controller enclosure where the management network port to be modified
resides.
NOTICE
----End
You can log in to the storage system by either of the following methods:
● This document uses PuTTY as an example. You can download PuTTY from the chiark
website.
● To ensure successful login to the storage system, you are advised to use PuTTY of the
latest version.
1. Run PuTTY.
The PuTTY Configuration dialog box is displayed.
2. Select Serial from the Connection type drop-down list box, and enter
115200 in the Speed text box.
3. Click Open. The following information is displayed.
Storage login:
4. Enter the user name and password as prompted. To ensure system security,
you are required to change the password upon your initial login. If the login is
successful, the following information is displayed.
Storage login: admin
For security purposes, please change the initial password and log in to the system using the new
password.
Old password:*************
New password:**************
Reenter password:**************
NOTE
● The default user name of the super administrator is admin. For the default password,
refer to the OceanStor V500R007 Account List.
● Values of Product Model and Product Version vary according to the login device.
● To ensure system security, you are advised to change your login password periodically by
running the change user_password command.
● If you forget the password as an administrator or a read-only user, the super
administrator can run change user to reset the password. If you forget the password as
a super administrator (admin by default), the root administrator _super_admin can log
in to the CLI through a serial port and run initpasswd to reset the password.
● When use LDAP User:
● For a domain user of domain authentication server 0, the user can log in to the CLI
of a storage system by typing domain/domain user name or a combination of the
dc field in the domain authentication server's base DN/domain user name.
● For a domain user of domain authentication server 1, 2, or 3, the user can log in to
the CLI of a storage system only by typing a combination of the dc field in the
domain authentication server's base DN/domain user name.
1. If the base DN of the domain authentication server contains only one dc field, the dc
field is used as the combination of the dc field in the domain authentication server's
base DN.
For example, if the base DN of the domain authentication server is
ou=applications,dc=bigcorp, bigcorp is the combination of the dc field in the
domain authentication server's base DN.
2. If the base DN of the domain authentication server contains multiple dc fields, they
are combined and then separated by a period (.) to serve as the combination of the
dc field in the domain authentication server's base DN.
For example, if the base DN of the domain authentication server is
ou=applications,dc=bigcorp,dc=com, bigcorp.com is the combination of the dc
field in the domain authentication server's base DN.
● This document uses PuTTY as an example. You can download PuTTY from the chiark
website.
● To ensure successful login to the storage system, you are advised to use PuTTY of the
latest version.
1. Run PuTTY.
The PuTTY Configuration dialog box is displayed, as shown in Figure 5-5.
2. Select Session. In the Specify the destination you want to connect to area,
enter the IP address (for example, 192.168.6.96) of the storage device's
management network port that connects to the maintenance terminal in
Host Name (or IP address) and set Connection type to SSH.
3. Click Open. The following information is displayed.
login as:
4. Enter the user name and password as prompted. To ensure system security,
you are required to change the password upon your initial login. If the login is
successful, the following information is displayed.
login as: admin
For security purposes, please change the initial password and log in to the system using the new
password.
Old password:*************
New password:**************
Reenter password:**************
SN : XXXXXXXXXXXXXXXXXXXXXXXXX
Location :
Product Model : XXXXX
Product Version : XXXXX
Time : XXXX-XX-XX/16:38:22 +08:00
admin:/>
NOTE
● The default user name of the super administrator is admin. For the default password,
refer to the OceanStor V500R007 Account List.
● Values of Product Model and Product Version vary according to the login device.
● To ensure system security, you are advised to change your login password periodically by
running the change user_password command.
● If you forget the password as an administrator or a read-only user, the super
administrator can run change user to reset the password. If you forget the password as
a super administrator (admin by default), the root administrator _super_admin can log
in to the CLI through a serial port and run initpasswd to reset the password.
● When LDAP User is used:
● For a domain user of domain authentication server 0, the user can log in to the CLI
of a storage system by typing domain/domain user name or a combination of the
dc field in the domain authentication server's base DN/domain user name.
● For a domain user of domain authentication server 1, 2, or 3, the user can log in to
the CLI of a storage system only by typing a combination of the dc field in the
domain authentication server's base DN/domain user name.
1. If the base DN of the domain authentication server contains only one dc field, the dc
field is used as the combination of the dc field in the domain authentication server's
base DN.
For example, if the base DN of the domain authentication server is
ou=applications,dc=bigcorp, bigcorp is the combination of the dc field in the
domain authentication server's base DN.
2. If the base DN of the domain authentication server contains multiple dc fields, they
are combined and then separated by a period (.) to serve as the combination of the
dc field in the domain authentication server's base DN.
For example, if the base DN of the domain authentication server is
ou=applications,dc=bigcorp,dc=com, bigcorp.com is the combination of the dc
field in the domain authentication server's base DN.
Prerequisites
● Only a super administrator has the permission to modify users' authentication
mode for logging to the CLI.
● Public key authentication for logging to the CLI is configured for local users
only, not for domain users.
Precautions
● After a private key is generated, keep it secure.
● Change the public key periodically. Use the new private-public key pair for
login authentication to improve system security.
Procedure
Step 1 Generate a private-public key pair for a local user.
1. Run the puttygen.exe file.
Go to the PuTTY Key Generator main window, as shown in Figure 5-6.
2. In the Parameters area, set Type of key to generate to SSH-2 RSA or SSH-2
DSA, and set Number of bits in a generated key to an integer from 2048 to
8192.
3. Click Generate and move the cursor over the blank area in the lower part of
the Key area to generate a public key.
The public key will be displayed in the area, as shown in Figure 5-7.
For security of the private key file, you are advised to configure a secure password to
encrypt the file.
6. Select an appropriate method to generate the private key file. The method
varies according to the tools used to log in to the CLI.
– If you use PuTTY to log in to the CLI, click Save private key and save the
private key file to a local path, as shown in Figure 5-8.
– If you use other tools to log in to the CLI, choose Conversions > Export
OpenSSH key and save the private key file to a local path, as shown in
Figure 5-9.
1. Start PuTTY.
The PuTTY Configuration dialog box is displayed.
2. Click Session. In the right pane, type the IP address of a storage system's
management network port in the Host Name (or IP address) text box. Set
Port and Connection type to 22 and SSH respectively.
3. Choose Connection > Data. In the Login details text box in the right pane,
type the user name of the login authentication mode to be modified.
4. Choose Connection > SSH > Auth. In the right pane, click Browse. Select and
open the locally saved private key file.
5. Click Open to log in to the CLI.
NOTE
If the password of the private key is encrypted in Step 1.5, type the password when logging
in to the CLI, and then press Enter.
Using username "test123".
----End
Follow-up Procedure
To change a user's login authentication mode to Username + Password, run the
change user_ssh_auth_info general user_name=test123 auth_mode=password
command and use the original password to log in to the CLI of a storage system.
Procedure
Step 1 Log in to DeviceManager.
Step 3 On the Basic Information page, configure basic information for the storage
device.
1. In Device Name, type a name for the storage device.
– The name contains 1 to 127 characters.
– The name can contain only letters, digits, periods (.), underscores (_), and
hyphens (-).
2. In Device Location, type a geographical location for the device.
The location contains 1 to 511 characters.
3. (Optional) Change the password of the login user.
a. Click Modify.
b. In Old Password, type the current password for logging in to the device.
c. Type a new password in New Password and Confirm Password.
NOTE
Step 4 Click Next and configure the device time on the Device Time page.
● Select Synchronize client time to synchronize the device time with the
existing client.
● Select Set NTP automatic synchronization to synchronize the device time
with the network time protocol (NTP) server.
NOTE
NOTE
Select Do not adjust the current time on the device if you do not want to modify the
device time.
Step 5 Click Next. On the Configure Disk Domain page, configure the disk domain.
You can configure available disks in the disk domain in either of the following
ways:
● If you select Yes. The system will automatically configure the disk domain,
the system automatically completes disk domain configuration.
NOTE
You can view the number of disks at each layer in the disk domain.
● If you select No. I want to manually configure the disk domain, you need
to manually configure the disk domain.
Step 6 Click Next to configure alarm notification on the Alarm Notification page.
For details about Alarm Notification settings, see 5.1.6 Configuring Alarm and
Event Handling Policies.
Step 7 Click Finish.
A dialog box is displayed, indicating that the initial configuration is completed.
Step 8 Click OK.
----End
Item Description
GTS permission for the ESDP Users who have the GTS permission can
(applicable to Huawei service apply for licenses following instructions in
engineers) 5.1.3.2.1 Applying for a License in
Entitlement Activation Mode. If you do
not have GTS permission, click Permission
Application in the left navigation tree of
the ESDP home page and complete the
permission application.
ASP or Guest permission for the Users who have the ASP or Guest
ESDP (applicable to Huawei permission can apply for licenses following
partners or customers) instructions in 5.1.3.2.2 Applying for a
License in Password Activation Mode.
Click Register Now on the ESDP home
page and complete related registration
information. Then you are granted the ASP
or Guest permission.
NOTE
Figure 5-10 Information plate position of a 2 U controller enclosure (12 disk slots)
Figure 5-11 Information plate position of a 2 U controller enclosure (25 disk slots)
Figure 5-12 Information plate position of a 2 U controller enclosure (36 disk slots)
----End
Step 2 Run the show system general command to view the ESN, namely, the SN field in
the command output.
admin:/>showsystemgeneral
System Name : XXX.Storage
Health Status : Normal
Running Status : Normal
Total Capacity : 3.186TB
SN : 2102XXXXXXXXXXXXXXXX
Location :
Product Model : XXXX
Product Version : VX00R00XCXX
High Water Level(%) : 80
Low Water Level(%) : 30
WWN : XXXX
Time : 2018-07-07/15:34:05 UTC+08:00
Patch Version : SPCXXX SPHXXX
Description :
----End
Prerequisites
You have the GTS permission and access permissions to the ESDP platform
(website: http://app.huawei.com/isdp).
NOTE
If you have only the ASP or Guest permission, apply for a license in password activation
mode. For details, see 5.1.3.2.2 Applying for a License in Password Activation Mode.
Context
1. When applying for a license, you need to know the following concepts:
– Entitlement
Entitlement is a form of agreement between a software provider and a
customer, which entitles the customer to the scope, functions, validity
period of the product purchased or sold.
– Entitlement ID
An entitlement ID is a unique ID that identifies entitlement.
– Entitlement Line
An entitlement line is a unit of entitlement that can be activated.
Entitlement contains one or multiple entitlement lines.
– Activation ID
An activation ID is a unique ID that identifies an entitlement line.
– Equipment (node)
A piece of equipment or node is a system device, entity, or node.
2. On the ESDP, entitlement management and license application are based on
equipment (node).
Procedure
Step 1 Select entitlement.
1. On the ESDP home page, choose License Activation > Entitlement
Activation.
The Step 1: Select Entitlement page is displayed.
2. In the Status field, select Ready and click Search.
The matching entitlements are displayed, as shown in Figure 5-14.
NOTE
The ESDP supports fuzzy match. To improve search accuracy, you can input customer
PO, product name, version, and contract No.
3. Select one or more entitlements from the list. Click Next. The Step 2: Binding
Of ESN page is displayed.
NOTICE
If the specified ESN is incorrect, the license you obtain will be invalid.
2. Select one or more entitlements you want to activate, and click Next.
If the entitlement information differs from the equipment (node) information,
the system displays an error and asks you to reset the information. If the
entitlement information is correct, the Step 3: Confirm Activation page is
displayed.
----End
Follow-up Procedure
After applying for a license, keep your license file secure because it will be used in
subsequent operations.
Prerequisites
You have the ASP or Guest permission and access permissions to the ESDP
platform (website: http://app.huawei.com/isdp). In addition, you have a valid
license certificate that contains the activation password.
NOTE
If you do not have a valid license certificate, you can send the contract No. to your agent to
obtain the license certificate.
Context
1. When applying for a license, you need to know the following concepts:
– Entitlement
Entitlement is a form of agreement between a software provider and a
customer, which entitles the customer to the scope, functions, validity
period of the product purchased or sold.
– Entitlement ID
An entitlement ID is a unique ID that identifies entitlement.
– Entitlement Line
An entitlement line is a unit of entitlement that can be activated.
Entitlement contains one or multiple entitlement lines.
– Activation ID
Procedure
Step 1 Enter your password for activation.
1. On the home page of the ESDP, choose License Activation > Password
Activation. The Step 1: Input Activation Password page is displayed, as
shown in Figure 5-16.
2. Confirm the information and select I have read the above carefully.
3. In the Activation Password field, enter the activation password.
NOTE
– An activation password can be bound with an ESN only once. If the specified
password is incorrect, the license you obtain will be invalid.
– To enter more activation passwords, click Add.
4. Select the activation password you want to bind, and click Next. The Step 2:
Input ESN page is displayed.
NOTICE
If the specified ESN is incorrect, the license you obtain will be invalid.
----End
Follow-up Procedure
After applying for a license, keep your license file secure because it will be used in
subsequent operations.
Context
● After being imported to the storage system, the license file is in inactive state.
You can determine whether to activate it based on your service requirements.
● The file name extension of license files is *.dat.
Procedure
Step 1 Log in to DeviceManager.
NOTE
The dialog boxes vary according to the web browsers that you use.
3. Click Upload.
----End
Procedure
Step 1 Log in to DeviceManager.
----End
Step 1 Log in to the Windows AD domain server. Choose Start > Administrative Tools >
Active Directory Users and Computers. In the Active Directory Users and
Computers window, view and record related parameters.
Step 2 Obtain the Base DN information. As shown in the figure, icp.com maps to Base
DN on the configuration page of the storage system, that is, dc=icp,dc=com.
NOTE
The Attribute Editor option is available only after you select the Advanced Features
in Step 3.1.
Step 4 Obtain the User Directory information. (This information is required when you
create an LDAP user.)
1. Administrator under Users is used as an example. Right-click the Users
folder under icp.com, and choose Properties.
2. In the Users Properties dialog box, click Attribute Editor, select the
distinguishedName property, and click View to obtain the User Directory
information. The queried User Directory record is cn=Users,dc=icp,dc=com.
Step 5 Obtain the Group Directory information. (This information is required when you
create an LDAP user group.)
1. The Domain Admins user group under Users is used as an example. Right-
click the Domain Admins user group and choose Properties.
2. In the Domain Admins Properties dialog box, click Attribute Editor, select
the distinguishedName property, and click View to obtain the Group
Directory information. The queried Group Directory record is cn=Domain
Admins,cn=Users,dc=icp,dc=com.
Step 6 Contact the Windows AD domain server administrator to obtain IP Address and
Bind Password of the AD domain server.
NOTE
For details about how to create AD domain users and groups on the AD domain controller,
see 6.3 How Do I Create AD Domain Users and Groups on the AD Domain Controller?
----End
LDAP directories function as file system directories. For example, LDAP directory
dc=redmond,dc=wa,dc=microsoft,dc=com can be considered as the following file
system directory: com\microsoft\wa\redmond. In another example of directory
cn=user1,ou=user,dc=example,dc=com, cn=user1 indicates a user name and
ou=user indicates the organization unit of Active Directory (AD), that is, user1 is
in the user organization unit of the example.com domain.
o Organization
ou Organization Unit
c Country Name
dc Domain Component
sn Surname
cn Common Name
NOTE
The OpenLDAP installation package is available on the Userbooster website, but not the
OpenLDAP website. It can run on the following types of Windows operating systems:
Windows XP, Windows Server 2003, Windows Server 2008, Windows Vista, Windows 7,
Windows 8, and Windows Server 2012.
rootpw XXXXXXXXXXXX
Step 4 Find configuration files (with .ldif as the file name extension) of users and user
groups that need to access the storage system.
NOTE
LDAP Interchange Format (LDIF) is one of the most common file formats for LDAP
applications. It is a standard mechanism that represents directories in the text format, and
it allows users to import data to and export data from the directory server. LDIF files store
LDAP configurations and directory contents. You can obtain parameter information from
LDIF files.
Step 5 Use the text editing software to open the configuration file and find the DNs that
map to User Directory and Group Directory respectively on the storage system
configuration page.
#root on the top
dn: dc=example,dc=com
dc: example
objectClass: domain
objectClass: top
#First organization unit name: user
dn: ou=user,dc=example,dc=com
ou: user
objectClass: organizationalUnit
objectClass: top
#Second organization unit name: groups
dn: ou=group,dc=example,dc=com
ou: groups
objectClass: organizationalUnit
objectClass: top
#The first user represents user1 that belongs to organization unit user in the organizational structure
topology.
dn: cn=user1,ou=user,dc=example,dc=com
cn: user1
objectClass: posixAccount
objectClass: shadowAccount
objectClass: inetOrgPerson
sn: user1
uid: user1
uidNumber: 2882
gidNumber: 888
homeDirectory: /export/home/ldapuser
loginShell: /bin/bash
userPassword: {ssha}eoWxtWNl8YbqsulnwFwKMw90Cx5BSU9DRA==xxxxxx
#The second user represents user2 that belongs to organization unit user in the organizational structure
topology.
dn: cn=user2,ou=user,dc=example,dc=com
cn: user2
objectClass: posixAccount
objectClass: shadowAccount
objectClass: inetOrgPerson
sn: client
uid: client
uidNumber: 2883
gidNumber: 888
homeDirectory: /export/home/client
loginShell: /bin/bash
userPassword: {ssha}eoWxtWNl8YbqsulnwFwKMw90Cx5BSU9DRA==xxxxxx
#The first user group represents group1 that belongs to organization unit group in the organizational
structure topology. The group contains user1 and user2.
dn: cn=group1,ou=group,dc=example,dc=com
cn: group1
gidNumber: 888
memberUid: user1#Belongs to the group.
memberUid: user2#Belongs to the group.
objectClass: posixGroup
----End
Step 3 Run the ls command to view the slapd.conf system configuration file and the
configuration file (with .ldif as the file name extension) of users and user groups
who want to access the storage system.
linux-ldap:/etc/openldap #ls
example.ldif ldap.conf schema slap.conf slap.con slapd.conf
Step 4 Run the cat command to open the slapd.conf system configuration file where you
can view related parameters.
linux-ldap:/etc/openldap #cat slapd.conf
suffix "dc=example,dc=com"
rootdn "cn=Manager,dc=example,dc=com"
rootpw XXXXXXXXXXXX
----End
Prerequisites
The LDAP server or Windows Active Directory (AD) domain server has been
installed and deployed.
When configuring the LDAP server, you can select LDAP Server or Windows AD
Domain Server as the server type.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Permission Settings > Domain Authentication Server
Settings.
Step 3 Configure the LDAP server.
1. Select the ID of the domain authentication server to be configured, and click
Properties.
NOTE
If LDAP is used, go to Step 3.2. If LDAPS is used, ensure that the CA certificate file of
the corresponding domain server has been imported to the storage system.
– If Windows AD domain authentication is used, import the CA certificate of the AD
domain server to the storage system before selecting LDAPS. For details, see 6.4
How Can I Import the Windows AD Domain Server's CA Certificate to the
Storage System?
– If LDAP domain authentication is used, import the CA certificate of the LDAP
domain server to the storage system before selecting LDAPS. Apply for a CA
certificate that matches the LDAP domain server's certificate from a third-party
certificate authority.
– If you select domain authentication server 0, ensure that the CA
certificate file of the domain authentication certificate has been imported
to the storage system.
– If you select domain authentication server 1, ensure that the CA
certificate file of domain authentication extended certificate 1 has been
imported to the storage system.
– If you select domain authentication server 2, ensure that the CA
certificate file of domain authentication extended certificate 2 has been
imported to the storage system.
– If you select domain authentication server 3, ensure that the CA
certificate file of domain authentication extended certificate 3 has been
imported to the storage system.
For details, see contents related to security certificate management in the
Security Configuration Guide specific to your product model and version.
2. Click Add.
The Add IP Address dialog box is displayed.
To remove an IP address, select the IP address from the IP Address list and click
Remove.
5. Set the basic parameters of the LDAP server. Table 5-5 describes the related
parameters.
6. Click Advanced to set the advanced parameters of the LDAP server. Table 5-6
describes the related parameters.
NOTE
After you configure the LDAP server on the storage system, you need to log in to the
storage system using the LDAP user name or LDAP user group name. Therefore, you need
to create the LDAP user name or LDAP user group name on the storage system.
Step 5 To add the storage system to more domain authentication servers, repeat
operations in Step 3 and Step 4.
NOTE
After the storage system is added to the LDAP domain, you can log in to the storage system
as an LDAP user. For details, see 5.1.1.2 Logging In to DeviceManager or 5.1.1.4 Logging
In to the CLI.
----End
Positioning
Traditionally, alarms and logs are manually collected from storage systems and
cannot be sent to Huawei technical support center in a timely manner. As a result,
Huawei technical
Storage support engineer
system Internet
(HTTPS)
TCP: 7448/8448/9448
Firewall Firewall
Huawei technical
Storage support engineer
system
Internet
(HTTPS)
TCP: 7448/8448/9448
Firewall Firewall
NOTE
● If an internal HTTP proxy server is deployed for network access, ensure that the server is
secure and reliable.
● If neither of these two types of networking is supported, the eService Client can be
deployed to upload storage alarms and logs to the eService cloud system. For details,
see the eService V2R2C00 User Guide.
Operation log ● A .txt file in the JSON Operation logs are uploaded
format to the eService cloud system
● Operation logs about every 24 hours.
device status and function
modules. Function modules
include controllers,
enclosures, power supplies,
BBUs, fans, disks,
expansion modules,
interface modules, ports,
disk domains, storage
pools, and LUNs.
NOTE
5.1.5.2 Preparations
The following table describes preparations that you are advised to make before
configuring eService.
Item Description
Enabling ports 7448/ The eService cloud system uses server ports 7448/TCP,
TCP, 8448/TCP, and 8448/TCP, and 9448/TCP. Enable the three ports on the
9448/TCP on the firewall to allow storage systems to send HTTP
firewall to allow requests to the eService cloud system.
outgoing traffic from For details about how to check whether the ports are
the firewall to the enabled, see 6.6 How Do I Check Whether Network
Internet Firewall Ports Are Enabled?
Item Description
Procedure
Step 1 Log in to DeviceManager.
If it is the first time to enter the eService Settings page, the Sign Authorization Letter
dialog box is displayed. Read the authorization letter carefully, select I have a clear
understanding of the data collection scope and data processing method of Huawei
eService system, and agree to connect to Huawei eService system, and click OK. If you
click Close or , the eService parameter settings cannot be modified or saved. In addition,
the Sign Authorization Letter dialog box will be displayed again when you enter the
eService Settings page the next time.
Step 5 Configure the connectivity between the storage system and external networks.
1. Click Network Configurations.
The Network Configurations dialog box is displayed.
Configure the standby DNS IP address 1 first and then the standby DNS IP
address 2.
d. (Optional) Test the connection between the DNS server and storage
system.
You can click Test of each DNS IP address to test its availability.
4. Click OK.
The network configuration is complete.
Step 6 Enter a site name.
NOTE
The contact person is the administrator of the storage device in the eService system. After
being added successfully, the administrator receives messages from eService.
1. Click Add.
The Add Contact dialog box is displayed.
2. Set the contact person information. Table 5-10 describes the related
parameters.
Parameter Description
Parameter Description
Click . The Audit Log dialog box is displayed. Table 5-11 describes related
parameters.
NOTE
If the Syslog notification function has been enabled and configured for the storage
system, parameters related to audit logs have been set.
be used to represent
neighboring zeros of the
IP address.
3. Click Test to test the connectivity between the storage system and server that
receives audit logs.
Step 10 Save and authenticate eService.
1. Click Save and Authenticate.
The Execution Result dialog box is displayed.
2. Click Close.
The Authenticate Device dialog box is displayed.
3. Enter the device authentication account and password.
NOTE
The device authentication account refers to the Huawei Support account. Apply for an
account at the Support website if you do not have one.
4. Click OK.
The Success dialog box is displayed.
5. Click OK.
After the device authentication is complete, the Access Authentication status
changes to Authenticated.
NOTE
Step 12 After the configuration is successful, log in to the eService cloud management
device. For details, see the eService Intelligent Cloud Management System User
Guide.
----End
Context
● If eService becomes unavailable, the eService client saves data uploaded in
the last 24 hours. After eService recovers, the eService client continues
receiving data. Before eService recovers, you can manually export data
packages to be uploaded.
● Exported data packages include performance, running, and alarm data.
Procedure
Step 1 Log in to the CLI as an administrator or a super administrator.
Step 2 Run the export event event_type=call_home ip=? user=? password=? path=?
command to export data packages to be exported.
path=? Path and file for saving The path must start with /. The
events or logs on an FTP or file is a package.
SFTP server. ● /test/ indicates that events
or logs are saved in the test
folder on the FTP/SFTP
server. The file name is
automatically generated.
● /test indicates that events or
logs are saved in the test
file.
● If you specify the file name,
we recommend you add the
file name extension .tgz. If
you do not specify the file
name extension, the CLI will
add it automatically.
----End
Example
Export certain eService data to an FTP server, where the IP address of the FTP
server is 192.168.8.211, the user name for logging in to the FTP server is admin,
the password is admin, the exported eService data will be stored in the root
directory of the FTP server, and the exported eService data will be saved with the
default file name.
Prerequisites
● The connections between each Simple Mail Transfer Protocol (SMTP) server
and all primary and secondary controllers are working properly.
● The email notification function is available only when the SMTP server is
running properly. Otherwise, the specified email address cannot receive alarm
and event emails.
● The alarm and event email notification function supports PLAIN and LOGIN
authentication mechanisms. Therefore, when you configure the email server,
ensure that at least one of the two authentication mechanisms is supported.
● You have logged in to DeviceManager as an administrator that has the
permission of one of the following:
– Super administrator
– Administrator
● The storage system sends only the alarms and events generated after email
notification is enabled to the SMTP server.
● Before configuring a domain name for the server, ensure that the DNS server
properly communicates with the storage system or third-party server.
Precautions
● To ensure that email notifications can be sent properly, the sender email
address must match the SMTP server address and can send emails to the
recipient email address.
For example, if a Gmail SMTP server is used, the sender email address must
be a Gmail address.
● When two SMTP servers are configured, the sender email address must match
the two SMTP server addresses and can send emails to the recipient email
address.
For example, if the sender email address is a Gmail address, the two SMTP
server addresses must be SMTP server addresses provided by the Gmail
supplier.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Alarm Settings > Email Notification.
Step 3 Set the email address for receiving alarms and events.
1. Select Enable.
2. Set email notification parameters. Table 5-13 describes the related
parameters.
▪ Digits (0-9)
▪ Uppercase
characters (A-Z)
▪ Lowercase
characters (a-z)
▪ Space
▪ Special characters
such as
[\]^_{|}~`@!"#$
%&'()*+-./:;<=>?
[Example]
aJ1p23dySQ
▪ When Notification Type is set to Alarm, you also need to set Alarm
Severity. The alarm severity can be Critical, Major, and Warning.
Prerequisites
● You have logged in to DeviceManager as an administrator that has the
permission of one of the following:
– Super administrator
– Administrator
● A short messaging service (SMS) modem has been installed on the system or
maintenance terminal. The COM port of the SM modem has been configured
to send short messages. For details about how to set the SMS modem, see
5.1.8 (Optional) Setting a GSM Modem.
● The storage system sends only the alarms and events generated after email
notification is enabled to the GSM modem.
Context
The SM notification function is not available to read-only users.
Procedure
Step 1 Log in to DeviceManager.
The phone number of the SMS service center must be prefixed with a plus sign (+)
and a country code.
3. Add a recipient mobile phone number.
a. Click Add.
The Add Recipient Information dialog box is displayed.
b. Set Recipient Number and Notification Type.
NOTE
▪ When Notification Type is set to Alarm, you also need to set Alarm
Severity. The alarm severity can be Critical, Major, and Warning.
Step 4 (Optional) Click Test to check whether the storage system has sent a notification.
----End
Prerequisites
● When the FTP server is used to save alarm information, the FTP server
communicates with the storage system properly. To improve communication
reliability, you are advised to configure the FTP server and storage system on
the same LAN and configure their IP addresses on the same network
segment.
● When the SFTP server is used to save alarm information, the SFTP server
communicates with the storage system properly. To improve communication
reliability, you are advised to configure the SFTP server and storage system on
the same LAN and configure their IP addresses on the same network
segment.
● If alarm information is stored on an FTP server and a firewall is configured on
the network, port 21 is enabled.
● If alarm information is stored on an SFTP server and a firewall is configured
on the network, port 22 is enabled.
Context
● If alarm dump is not configured for the storage system, when the number of
generated events reaches 45,000, alarm "The Space That Stores Event Logs Is
To Be Used Up" is triggered. When the number of generated events reaches
50,000 (the upper limit), the system automatically deletes the earliest 10,000
events.
● If alarm dump is configured for the storage system, when the number of
generated events reaches 45,000, alarm "The Space That Stores Event Logs Is
To Be Used Up" is not triggered. When the number of generated events
reaches the 50,000 (the upper limit), the system automatically dumps and
deletes the earliest 10,000 events to the specified FTP or SFTP server. When
the number of generated login and logout events reaches the 20,000 (the
upper limit), the system automatically dumps and deletes the earliest 10,000
login and logout events.
NOTE
To ensure that all events generated by the storage system are not lost, you are advised to
enable alarm dump.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Alarm Settings.
Step 3 Modify parameters for alarm dump.
1. In the navigation pane, choose Alarm Dump.
2. Table 5-14 describes the related parameters.
▪ Digits (0-9)
▪ Space
● If a success dialog box is displayed, the alarm dump parameters have been
configured correctly.
Step 4 Confirm the parameter configuration for the alarm dump.
1. Click Save.
The Execution Result dialog box is displayed, indicating that the operation
succeeded.
2. Click Close.
----End
Start
SNMPv1 or
SNMPv3
SNMPv2c
Configure SNMP
community strings.
End
Prerequisites
The storage system is running properly.
Procedure
Step 1 Log in to the CLI of the storage system. For details, see 5.1.1.4.1 Logging In to
the CLI (User Name + Password).
Step 2 Run the change snmp port port_number=port number command to configure a
port ID for the SNMP service.
For example, the following command configures port ID 20000 for the SNMP
service:
NOTE
The default value of port number is 161, and the value ranges from 20000 to 20100.
Step 3 Run the show snmp port command to query the port ID.
The command output is as follows:
admin:/>show snmp port
----End
Prerequisites
You have logged in to the CLI of the storage system.
Context
There are SNMPv1, SNMPv2c, and SNMPv3 protocols. The storage system
supports SNMPv3 by default. SNMPv1 and SNMPv2c are disabled because of their
low security.
Procedure
Step 1 Run the change snmp version v1v2c_switch=On command to enable SNMPv1
and SNMPv2c.
The command output is as follows:
admin:/>change snmp version v1v2c_switch=On
CAUTION: You are about to enable SNMPv1 and SNMPv2c. But you are advised to use the secure SNMPv3
protocol only.
Do you wish to continue?(y/n)y
Command executed successfully.
admin:/>
Step 2 Run the show snmp version command to check whether the change takes effect.
The command output is as follows:
admin:/>show snmp version
----End
Prerequisites
You have logged in to the CLI of the storage system.
Context
If you use SNMPv1 or SNMPv2c, you must configure community strings. A third-
party network management tool uses community strings to interwork with the
SNMP service of the storage system.
Procedure
Step 1 Run the change snmp community read_community=*********
write_community=********* command to configure community strings.
NOTE
When you enter a community string, asterisk signs (*) are displayed. Remember or record
the community string.
Step 2 Use the third-party network management tool to verify that the community
strings can be used to interwork with the storage system.
----End
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Alarm Settings > USM User Management.
Step 4 Set USM user parameters. For related parameters, see Table 5-15.
The Execution Result dialog box is displayed, indicating that the operation
succeeded.
----End
Prerequisites
● The SNMP service has been enabled on the storage system. If the service has
not been enabled, run the change snmp status command in the developer
view to enable it. For details about how to use the command, see the
Advanced O&M Command Reference specific to your product model and
version.
● The SNMP service has been enabled on the server.
● A USM user has been created. For details about how to create a USM user,
see 5.1.6.4.5 Adding a USM User (Applicable to SNMPv3).
● A storage system only sends the alarms and events generated after the trap
server is configured and does not send alarms or events generated before the
configuration.
● Before configuring a domain name for the server, ensure that the DNS server
communicates properly with the storage system or third-party server.
Context
Trap is a type of Simple Network Management Protocol (SNMP) message that
indicates the occurrence of an event. These types of messages are sent using User
Datagram Protocol (UDP) and are not reliable.
DeviceManager provides the trap function to send the alarm and event messages
of managed storage devices to another network management system or to a
device at a specific server address. If alarm and event messages are reported in
SNMP mode, you must configure trap server addresses.
NOTE
To enable the trap function, install the associated software on application servers. For
example, you must install MIB interface software on the application servers that run
Windows Server 2003. To download the software, click (here) and identify the required
software as instructed in MIB_Interface_File_Usage_Guide.
Procedure
Step 1 Log in to DeviceManager.
4. Click OK.
----End
Follow-up Procedure
A storage device can send multiple types of alarms or events to the trap server
and each alarm or event has its own push format. For details, click (here) and
identify the required software as instructed in MIB_Interface_File_Usage_Guide.
Context
● The certificate generated on the storage system is not signed and requires to
be signed on the signature server.
● For versions earlier than V500R007C70 Kunpeng, if you use a third-party tool
to export certificate request files, save the exported private key file as well.
These files, together with the signed certificate and CA certificate, are
exported to the storage system when the certificates are verified on the
storage system. For V500R007C70 Kunpeng and later versions, you do not
need to export the private key file.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Storage Settings > Value-added Service Settings >
Credential Management.
----End
Follow-up Procedure
After the Syslog certificate is exported, sign the signature on it.
Export the Syslog certificate and sign the signature based on actual conditions.
Export the CA certificate at the same time for subsequent operations.
Prerequisites
● The signed certificate and CA certificate exist.
● For versions earlier than V500R007C70 Kunpeng, ensure that the private key
file exists if the certificate file is exported and signed by a third-party tool.
Context
If the certificate file is exported and signed by a third-party tool, import the
private key file when you import the activated certificate and CA certificate.
NOTE
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Storage Settings > Value-added Service Settings >
Credential Management.
Step 3 Import and activate the signed certificate.
1. After the certificate has been signed by the server, click Import and Activate.
The Import Certificate dialog box is displayed.
2. Set the certificate type to Certificate of Syslog and import the signed
certificate and CA certificate. Table 5-17 describes related parameters.
3. Click OK.
The Warning dialog box is displayed.
4. Select I have read and understand the consequences associated with
performing this operation, and click OK.
The Success dialog box is displayed.
5. Click OK.
The certificate has been successfully imported and activated.
----End
You can generate the Syslog server certificate using a third-part device (such as
OpenSSL), sign the certificate using a third-party signature server, and export the
corresponding CA certificate.
NOTE
Ensure that the signature server used on the Syslog server is the same as that on the
storage system.
Prerequisites
● You have logged in to DeviceManager as an administrator that has the
operation permission of:
– Super administrator
– Administrator
● Before configuring a domain name for the server, ensure that the DNS server
communicates properly with the storage system or third-party server.
● A storage system has been configured to send only the alarms and events
generated after the Syslog server is configured, but not alarms or events
generated before the configuration.
● Only one Syslog server is configured on a host (recommended). Otherwise,
you may not receive Syslog notification due to port conflicts.
NOTE
● Ensure that the UDP, TCP, and TCP+SSL/TLS protocols have been configured on the
Syslog server. Security risks arise if the protocol is UDP or TCP. You are advised to select
TCP+SSL/TLS.
● The protocol configured on the storage system must be consistent with that configured
on the Syslog server.
Procedure
Step 1 Log in to DeviceManager.
Step 4 (Optional) Click Test to test the connectivity between the storage system and
Syslog server.
----End
Follow-up Procedure
After Syslog alarm notification is configured, alarms will be sent to a specified
application server or maintenance terminal. The Syslog alarm format is shown as
follows:
Info Receive Time | Facility | Severity | Info
2013/6/19 10:55:19 | Local7 | Error | alam:<186> 2015-06-19 10:47:10 xxx.xxx.xxx.xxx 240788 0xF00A000C
Major(1) Hard disk (Controller Enclosure CTE0, slot 2, serial-number XXXXXX) is in single-link state.
2013/6/19 10:58:53 | Local7 | Error | alam:<188> 2015-06-19 10:57:50 2015-06-19 10:57:50 xxx.xxx.xxx.xxx
241093 0xF0C90001 Warning(2): The Licence feature (xxx) is going to expire on 2015-08-14.
Output description:
NOTE
Info Receive Time, Facility, and Severity are defined by the Syslog server. The parsing
result may vary according to tools.
Prerequisites
● The DNS has been configured and is running properly.
● Port 53 of the TCP/UDP protocol between the storage system and the DNS
server is enabled.
Context
● A DNS server is used to resolve host names in a domain.
● If you want to configure a standby DNS server, keep the domain names of the
active and standby servers consistent.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Basic Information > DNS Service.
Configure the standby DNS IP address 1 first and then the standby DNS IP address 2.
4. Optional: Test the connection between the DNS server and storage system.
– You can click Test of each DNS IP address to test its availability.
– You can click Test All to test the connection between the DNS server and
storage system.
The Success dialog box is displayed, indicating that the operation succeeded.
----End
Prerequisites
A GSM modem has been installed and connected to the storage device.
Context
NOTICE
To demonstrate how to configure a GSM modem, this section uses the COM1
serial port (baud rate = 115200 bit/s) on the host and the DB9 serial port on the
GSM modem (default baud rate = 9600 bit/s) as an example.
Procedure
Step 1 Insert a SIM card into the GSM modem.
Step 2 Connect GSM modem to the serial port on the maintenance terminal through a
DB9 serial cable.
Step 3 Put the power cable of the GSM modem into the power supply outlet. Then power
on the GSM modem.
Step 4 Run PuTTY. In the Category navigation tree, choose Session > Logging.
The Basic options for your PuTTY session page for configuring the GSM modem
is displayed, as shown in Figure 5-21.
Figure 5-21 Page for Basic options for your PuTTY session
Step 8 Reset the baud rate of the GSM modem until OK is displayed in the at command
output.
NOTE
● If the baud rate of the GSM modem is not confirmed, reconfigure it to ensure that the
baud rate of the GSM modem and that of the serial port are consistent. In this
condition, the PuTTY can be used to configure the GSM modem.
● The baud rate can be configured using the at+ipr=115200 command.
Step 11 Upon successful configuration, connect the GSM modem to the serial port of the
storage system for use.
NOTE
For details about how to configure the GSM modem, see the corresponding manual
provided with the GSM modem.
----End
Prerequisites
● You have logged in to a Windows operating system through the management
network port.
● The NTP server has been set up on the Windows server. You can download
the NTP software from Meinberg website. For details, see the installation
guide at https://www.satsignal.eu/ntp/setup.html.
NOTE
● Before installation, run the net stop w32Time command to disable the Windows Time
(w32Time) service.
● In the following example, NTP is installed in the C:\Tools\ directory.
Procedure
Step 1 Log in to the Windows server remotely through the maintenance terminal.
1. Choose Start > All Programs > Accessories > Remote Desktop Connection.
The Remote Desktop Connection dialog box is displayed.
2. In Computer, enter the IP address of the management network port on the
Windows server, and press Enter.
3. Type the user name and password, and press Enter.
The main interface of the server is displayed.
Step 2 On the Windows desktop, double-click Computer, select a proper disk partition,
and create the directory for saving the certificate and private key file.
NOTICE
For the NTP server in Windows, if the certificate length is set to 2048, the
generated certificate fails to be signed, causing the storage system synchronization
time to slow down. Besides, an alarm indicating that the time server cannot be
used is reported. If the certificate length is set to 1024, such problem will not
occur but the certificate security decreases. If a certificate with higher security
level is required, you are advised to use the NTP server in the Linux operating
system and generate related certificates on this server.
server_password is the private key encryption password used in generating the certificate
(which can be specified by the user), Storage is the host name, and D:\ntp_config is the
directory where the certificate and private key files are saved.
Step 6 In the Windows command window, run the net stop ntp and net start ntp
commands to restart the NTP service.
NOTE
If multiple NTP servers need to be configured, you can copy the ntpkey_cert_Storage and
ntpkey_host_Storage files generated in Step 3 to the corresponding directory of other NTP
servers and change the file permission to be the same as that on the original server.
Configure the ntp.conf file under this server and restart the NTP service.
----End
Prerequisites
● The IP address of the NTP server has been obtained.
● The login user name and password of the NTP server have been obtained.
● You have configured the maintenance terminal in a Windows operating
system.
● The maintenance terminal is communicating with the storage system
properly.
● If the storage system has been added to a domain, the NTP server
communicates with the domain server properly, and NTP synchronization has
been completed.
Procedure
Step 1 Obtain the certificate from the NTP server and copy it to the maintenance
terminal.
1. On the maintenance terminal, press Win+R.
The Run dialog box is displayed.
2. Enter \\NTP server IP address and click OK.
The maintenance terminal attempts to remotely access the NTP server.
3. Type the user name and password of the NTP server and click OK to enter the
shared directory.
4. Enter the ntp_config folder and select the NTP certificate that contains the
ntpkey_cert field and press Ctrl+C to copy the certificate.
5. Go back to the maintenance terminal desktop and press Ctrl+V to copy the
NTP certificate to the maintenance terminal.
6. Right-click the NTP certificate file and then select Rename from the shortcut
menu. Add the .crt extension to the file name, and click Enter.
Step 2 Log in to DeviceManager through the maintenance terminal.
Step 3 Import the NTP certificate.
1. Choose Settings > Storage Settings > Value-added Service Settings >
Credential Management.
2. Click Import and Activate.
The Import Certificate dialog box is displayed.
3. In Certificate Type, select NTP certificate.
4. Click Select next to CA Certificate File.
In the dialog box that is displayed, find the NTP file directory, select the NTP
certificate, and click Open.
5. Click OK.
The security alert dialog box is displayed.
6. Select I have read and understand the consequences associated with
performing this operation, and click OK.
The Success dialog box is displayed.
7. Click OK.
The certificate list shows imported certificates.
Step 4 Configure the NTP parameters.
1. Choose Settings > Basic Information > Device Time.
2. Select Set NTP automatic synchronization.
3. Type the IPv4 address, IPv6 address, or domain name of the NTP server in
NTP Server Address.
NOTE
– A maximum of two NTP servers can be added. If the time of one NTP server
cannot be automatically synchronized to the device, the system synchronizes the
time from another NTP server.
– Ensure that the time of two NTP servers is consistent.
4. In NTP Authentication, select Enable.
NOTE
Some device models do not support this function. Only when NTPv4 or later is used, NTP
authentication can be enabled to complete identity authentication for the NTP server and
automatically synchronize the system time to the storage device.
----End
Prerequisites
● The maintenance terminal has been connected to the server through a
management network port.
● GNU Compiler Collection (GCC) has been installed on the server running
Linux.
Context
This section uses PuTTY as an example. You can download PuTTY from the chiark
website.
Procedure
Step 1 Run PuTTY.
The PuTTY Configuration dialog box is displayed, as shown in Figure 5-23.
Step 2 Select Session. In Host Name (or IP address) of the Specify the destination you
want to connect to area, enter the IP address of the Linux server's management
network port that connects to the maintenance terminal and set Connection type
to SSH.
Step 3 Click Open. The CLI login page is displayed, as shown in the following:
login as:
Step 4 Enter the user name and password as prompted. The following shows the result of
a successful login.
Last login: Mon Apr 10 10:38:06 2017 from XXX.XXX.XXX.XXX
[storage ~]#
Step 5 Create the directory for saving the certificate and private key files.
1. Run the cd /etc command to go to the etc directory.
2. Run the mkdir ntp_config command to create the ntp_config folder.
The execution result is as follows:
Storage:~ # cd /etc/
Storage:/etc # mkdir ntp_config
NOTE
If a message shows that the parameter -l is not supported, upgrade the NTP on the server
to a version later than 4.2.8.
Step 9 Run the vi /etc/ntp.conf command to modify the NTP configuration file.
keysdir /etc/ntp_config
NOTE
server_password is the private key encryption password used in generating the certificate
(which can be specified by the user), Storage is the host name, and /etc/ntp_config is the
directory where the certificate and private key files are saved.
NOTE
If multiple NTP servers need to be configured, you can copy the ntpkey_cert_Storage and
ntpkey_host_Storage files generated in Step 6 to the corresponding directory of other NTP
servers and change the file permission to be the same as that on the original server.
Configure the ntp.conf file under this server and restart the NTP service.
NOTE
In write list=@root root, the two root fields are the account and password of the samba
user that were just added. Set the codes as required.
----End
Prerequisites
● The IP address of the NTP server has been obtained.
● You have obtained the samba user name and password for logging in to the
NTP server.
● You have configured the maintenance terminal in a Linux operating system.
● The maintenance terminal is communicating with the storage system
properly.
● If the storage system has been added to a domain, the NTP server
communicates with the domain server properly, and NTP synchronization has
been completed.
Procedure
Step 1 Obtain the certificate from the NTP server and copy it to the maintenance
terminal.
1. On the maintenance terminal, press Win+R.
The Run dialog box is displayed.
– A maximum of two NTP servers can be added. If the time of one NTP server
cannot be automatically synchronized to the device, the system synchronizes the
time from another NTP server.
– Ensure that the time of two NTP servers is consistent.
4. In NTP Authentication, select Enable.
NOTE
Some device models do not support this function. Only when NTPv4 or later is used, NTP
authentication can be enabled to complete identity authentication for the NTP server and
automatically synchronize the system time to the storage device.
----End
Prerequisites
● Before building a remote maintenance environment, ensure that PSTN phones
and external modems have been configured in equipment rooms.
● Each controller is equipped with one serial port connected to one modem.
Select the external modem based on your requirements.
Context
You can log in to the CLI through the storage system's serial port to perform
remote management and maintenance. This section uses two 56 K modems that
remotely access the storage system in PSTN dialup mode (in Windows) as an
example to describe how to configure modems for remote maintenance.
NOTE
The PSTN enhances data security by transmitting data over a telephone line instead of
Internet. To further improve security, you are advised to power off the modem when you
are not performing remote maintenance.
To implement remote maintenance, one remote modem and one local modem are
required.
Figure 5-24 shows the network topology.
● Remote modem
The remote modem is connected to the storage system's serial port as an
answer end.
● Local modem
The local modem is connected to the maintenance terminal's serial port as a
call end.
Procedure
Step 1 Configure a remote modem as the answer end.
NOTE
To configure the remote modem, connect the remote modem to a maintenance terminal
temporarily.
1. Connect the remote modem to the power supply. Connect the remote
modem's serial port to the maintenance terminal's serial port using a serial
cable. Connect the remote modem LINE port to the PSTN with a telephone
cable.
2. Run PuTTY.
The PuTTY Configuration dialog box is displayed, as shown in Figure 5-25.
OK!
4. Set initial parameters for the local modem.
Type at&f&w and press Enter. The screen displays:
OK!
NOTICE
1. Run PuTTY on the maintenance terminal, and perform Step 1.2 to Step 1.4.
2. Type at and press Enter. The screen displays:
OK!
3. Type atdt XXX-YYYYYYYYY and press Enter for dialup.
If dialup tasks on both the remote modem and the local modem are
successful, the baud rate is CONNECT. (For modems of different
manufacturers, the screen displays vary.)
NOTE
SN : xxxx
Location :
Product Model : xxxx
Product Version : xxxx
Time : 2014-08-26/14:33:34 +08:00
6. The CLI login succeeds. The storage device can now be remotely managed
and maintained.
----End
Deployment Procedure
Figure 5-26 shows the controller deployment procedure.
NOTICE
Before performing the operations in this section, ensure that the storage system
has no service. If the storage system is running any service, the operations will fail.
Start
End
Prerequisites
● The system network has been connected based on the controller expansion
scenario. For details, see 3.1.2.4 (Optional) Connection Planning for
Multiple Controller Enclosures.
● Controllers on all controller enclosures have the same memory size.
NOTE
You can run the show memory command to query the memory size of a controller.
● All controller enclosures have the same software version.
NOTE
You can run the show version all command to query the software version of
controller enclosures.
● Controller enclosures have been powered on. For a 4 U controller enclosure,
ensure that disk enclosures with coffer disk labels have been properly
connected to the controller enclosure.
● There are no critical or major alarms in the storage system.
● The public/private key pair and password of ibc_os_hs are the default values.
● The IP addresses of the management network ports on controller enclosures
connected to the management network must be different but on the same
network segment. For details, see 5.1.1.1 Changing the Initial IP Address of
the Management Network Port over a Serial Port and 5.1.1.3 (Optional)
Changing IP Addresses of Management Network Ports Using
DeviceManager.
Precautions
● SmartKit is used to expand controllers for the storage system.
● The operation procedure varies according to the SmartKit version. If you use
SmartKit of a different version, the GUI you see may be different from that in
this section.
● The Auto Discovery (AD) process has been enabled on all of the controllers in
the new controller enclosure 1. For details on how to enable the AD process,
see 6.1 What Can I Do If Controller Expansion Fails Because the Process
Lasts for Over 24 Hours After the Controllers to Be Added Are Powered
On?
NOTE
The AD process is used for message forwarding between controllers during expansion.
After enabling the AD process on all of the new controllers, you must add the new
controllers using SmartKit within 24 hours. Otherwise, controller expansion will fail
and you need to enable the AD process on the new controllers again.
Procedure
Step 1 Download SmartKit.
NOTE
If the maintenance terminal cannot access the Internet, you need to use another terminal
that can access the Internet to download the SmartKit installation package. Then copy
the package to the maintenance terminal.
For details about offline installation, see "Function Export" and "Function Import" in the
SmartKit User Guide.
Step 4 Add the storage device for which you want to expand controllers to SmartKit.
1. In the main window of SmartKit, click the Device Management tab and
select Add.
The dialog box to add devices is displayed.
2. In Basic Information, select Specify IP Address (add a device by the IP
address) and enter the management IP address of the storage system. Then
click Next.
3. In Config Information, enter the user name and password of the storage
system administrator and click Finish.
NOTE
● When a device is added for the first time or a device certificate is not trusted, a message
is displayed, indicating that the connection is not trusted.
● When an SSH server is added for the first time or after the fingerprint of an SSH server
changes, a prompt asks you whether you want to continue to register the SSH server.
Step 5 In the main window of SmartKit, choose Home > Storage > Capacity Expansion >
Add Controllers.
The Add Controllers page is displayed. Add the controllers by following the
wizard on SmartKit. For the detailed operations, see 7.2.1 Using SmartKit for
Capacity Expansion (Direct-Connection Network).
Step 6 Check the health status and running status of the added controllers and the disk
enclosure.
Log in to OceanStor DeviceManager and check whether Health Status of the new
controllers and disk enclosure is Normal and Running Status is Online.
----End
Context
If you use SmartKit to configure a switch, modify the IP address of the switch's
management network port to ensure that this IP address resides in the same
network with that of the storage system.
NOTE
Before modifying the IP address of a switch's management network port and the SSH
account, run the reset saved-configuration command to reset the configuration file of the
switch. In the mean time, run the reboot fast command to restart the switch for the
resetting to take effect.
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
Procedure
Step 1 Use the serial port to log in to a switch.
Step 2 Run the system-view command to go to the system view.
Step 3 Run the command-privilege level rearrange command to improve command
levels in batches.
Step 4 Run the commit command to commit the configuration.
Step 5 Run the aaa command to enter the AAA view.
Step 6 Configure the SSH login user for the switch.
1. Run the undo local-user policy security-enhance command to delete SSH
login security policies.
2. Run the local-user username password irreversible-cipher password
command to add a user.
username is the user name and password is the user's password.
3. Run the local-user username service-type ssh command to set the user
service model.
4. Run the local-user username level 15 command to set the user level.
Step 7 Change the IP address of the management network port of the switch.
1. Run the interface MEth0/0/0 command to enter the management network
port view.
2. Run the ip address ipaddress mask command to set the IP address.
ipaddress is the new IP address of the management network port and mask is
the subnet mask of the management network port.
3. Optional: Run the ip route-static ipaddress mask gateway command to set
the switch gateway.
ipaddress indicates the destination network segment, mask indicates the
subnet mask of the destination network segment, and gateway indicates the
gateway.
NOTE
If the switches, the maintenance terminal where SmartKit resides, and the original storage
system are not on the same network, you need to set the switch gateway. To ensure that IP
addresses on all network segments can access switches, you are advised to set a default
gateway, namely, set ipaddress and mask to 0.0.0.0 and 0.0.0.0.
Step 8 Run the user-interface maximum-vty number command to change the number
of SSH connections.
number is the maximum number of SSH connections and the value ranges from 0
to 21.
NOTE
If SmartKit is used to configure switches, you are advised to set number to a value larger
than six.
Step 9 Run the stelnet server enable command to enable the SSH service.
Step 10 Run the ssh authentication-type default password command to set the SSH
user authentication mode to password authentication.
Step 11 Run the user-interface vty 0 n command to set the number of concurrent users.
n indicates the number of concurrent users and the value must be smaller than
that set in Step 8.
Step 12 Run the authentication-mode aaa command to set the user authentication
mode.
Step 13 Run the user privilege level 15 command to set the user level.
Step 14 Run the protocol inbound ssh command to enable the user to support the SSH
protocol.
Step 15 Run the quit command to return to the system view.
Step 16 Run the rsa local-key-pair create command to generate the SSH public key for
the user.
Step 17 Run the commit command to submit the configuration file.
Step 18 Run the quit command to exit the system view.
Step 19 Run the save command to save the configuration file.
----End
Example
Add a user admin123 for SSH, and set a new IP address 172.31.8.54 for the
management network ports on the switches to ensure that the switches, the
maintenance terminal where tool resides, and the original storage system are on
the same network.
<HUAWEI>system-view
Enter system view, return user view with return command.
[~HUAWEI]command-privilege level rearrange
Info: The command levels have been upgraded in batch !
Privilege note: 0-VISIT, 1-MONITOR, 10-SYSTEM, 15-MANAGE
[*HUAWEI]commit
[~HUAWEI]aaa (Enter the AAA view.)
[~HUAWEI-aaa]undo local-user policy security-enhance (Delete SSH login security policies.)
Warning: The current operation may reduce the degree of account security. It is strongly recommended to
keep this enabled.
[*HUAWEI-aaa]local-user admin123 password irreversible-cipher huawei (Add a user admin123 for SSH.)
[*HUAWEI-aaa]local-user admin123 service-type ssh (Set the user service model.)
[*HUAWEI-aaa]local-user admin123 level 15 (Set the user level.)
[*HUAWEI-aaa]interface MEth0/0/0 (Enter the management network port view.)
[*HUAWEI-MEth0/0/0]ip address 172.31.8.54 255.255.0.0 (Set a new IP address for the management
network port)
[*HUAWEI-MEth0/0/0]ip route-static 0.0.0.0 0.0.0.0 172.31.0.1 (Set a default gateway.)
NOTE
Before modifying the IP address of a switch's management network port and the SSH
account, run the reset saved-configuration command to reset the configuration file of the
switch. In the mean time, run the reboot fast command to restart the switch for the
resetting to take effect.
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
Procedure
Step 1 Use the serial port to log in to a switch.
Step 2 Run the system-view command to go to the system view.
Step 3 Run the command-privilege level rearrange command to improve command
levels in batches.
If the switches, the maintenance terminal where SmartKit resides, and the original storage
system are not on the same network, you need to set the switch gateway. To ensure that IP
addresses on all network segments can access switches, you are advised to set a default
gateway, namely, set ipaddress and mask to 0.0.0.0 and 0.0.0.0.
Step 8 Run the user-interface maximum-vty number command to change the number
of SSH connections.
number is the maximum number of SSH connections and the value ranges from 0
to 21.
NOTE
If SmartKit is used to configure switches, you are advised to set number to a value larger
than six.
Step 9 Run the stelnet server enable command to enable the SSH service.
Step 10 Run the ssh authentication-type default password command to set the SSH
user authentication mode to password authentication.
Step 11 Run the user-interface vty 0 n command to set the number of concurrent users.
n indicates the number of concurrent users and the value must be smaller than
that set in Step 8.
Step 12 Run the authentication-mode aaa command to set the user authentication
mode.
Step 13 Run the user privilege level 15 command to set the user level.
Step 14 Run the protocol inbound ssh command to enable the user to support the SSH
protocol.
Step 15 Run the quit command to return to the system view.
Step 16 Run the rsa local-key-pair create command to generate the SSH public key for
the user.
Step 17 Run the commit command to submit the configuration file.
Step 18 Run the quit command to exit the system view.
Step 19 Run the save command to save the configuration file.
----End
Context
If you use SmartKit to configure a switch, modify the IP address of the switch's
management network port to ensure that this IP address resides in the same
network with that of the storage system.
NOTE
Before modifying the IP address of a switch's management network port and the SSH
account, run the reset saved-configuration command to reset the configuration file of the
switch. In the mean time, run the reboot command to restart the switch for the resetting to
take effect.
WARNING
● The two switches used for controller expansion must be of the same model.
● Switches for controller expansion can only be used for scale-out networking. Do
not use them for front-end service networking or other purposes.
● Switches used for controller expansion cannot be stacked or cascaded.
● Do not upgrade the firmware of the switches used for controller expansion.
Procedure
Step 1 Log in to the switch using the serial port.
Step 2 Run the system-view command to go to the system view.
Step 3 Change the IP address of the management network port of the switch.
1. Run the interface MEth 0/0/0 command to enter the management network
port.
If the following error message is displayed, the interface has been unbound from the
VPN instance. Ignore the error message.
[*HUAWEI-MEth0/0/0]undo ip binding vpn-instance _management_vpn_
Error: The VPN instance is not bound to the interface.
If the switches, the maintenance terminal where SmartKit resides, and the original
storage system are not on the same network, you must set the switch gateway. To
ensure that IP addresses on all network segments can access the switches, you are
advised to use the default gateway, that is, set ipaddress and mask to 0.0.0.0 and
0.0.0.0.
6. Run the commit command to commit the configuration.
7. Run the quit command.
Step 4 Set the user authentication mode and enable the user to support the SSH
protocol.
1. Run the system-view command to go to the system view.
2. Run the user-interface vty 0 4 command to set the number of concurrent
users.
3. Run the authentication-mode aaa command to set the user authentication
mode.
4. Run the protocol inbound ssh command to enable the user to support the
SSH protocol.
5. Run the quit command to return to the system view.
6. Run the commit command to commit the configuration.
Step 5 Set the AAA local user name and password.
1. Run the aaa command to enter the AAA view.
2. Run the local-user username password irreversible-cipher password
command to add an AAA local user.
In the command, username indicates the user name, and password indicates
the password of the user.
3. Run the local-user username service-type ssh terminal command to set the
user service mode.
4. Run the local-user username privilege level 3 command to set the user level.
5. Run the quit command to return to the system view.
Step 6 Create an SSH user and configure the authentication mode and service type for
the user.
1. Run the ssh user username command to create an SSH user with the same
name as the AAA local user.
2. Run the ssh user username authentication-type password command to set
the SSH user authentication mode to password authentication.
3. Run the ssh user username service-type stelnet command to set the service
type of the SSH user to STelnet.
4. Run the ssh server-source -i meth 0/0/0 command to configure the source
interface of the SSH server.
NOTE
If the login address is an IPv6 address, run the ssh ipv6 server-source -a ipv6-address
command to configure the source IP address of the SSH server.
5. Run the stelnet server enable command to enable the STelnet server
functions.
6. Run the commit command to commit the configuration.
Step 7 Run the ssh server publickey ecc rsa rsa_sha2_256 rsa_sha2_512 command to
enable the ECC and RSA encryption algorithms.
Step 10 Run the reboot command to restart the switch for the configurations to take
effect.
Step 11 Log in to the switch using SSH as the SSH user created in Step 6 and set the
password as prompted.
----End
NOTE
For details about how to configure switches, see the CloudEngine 7800&6800&5800 Product
Documentation.
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1.
interface 25GE 1/0/1
//Enable root bridge protection on the port.
stp root-protection
//Enable the edge port function.
stp edged-port enable
//Validate the port configuration.
commit
//Exit the configuration view of port 25GE 1/0/1.
quit
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1.
interface 25GE 1/0/1
//Enable LLDP on the port.
undo lldp disable
//Allow LLDP packet transmission and reception.
lldp admin-status txrx
//Validate all the preceding configurations.
commit
//Exit the configuration view of port 25GE 1/0/1
quit
//Create a WRED drop profile and enter the WRED drop profile view.
drop-profile ecn_25G
//Configure ECN parameters.
ecn buffer-size low-limit 7000 high-limit 200000 discard-percentage 30
//Validate the configuration.
commit
//Exit the WRED drop profile view.
quit
//Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
dcb pfc deadlock-detect interval 100
//Validate the configuration.
commit
//Enter the default PFC configuration view.
dcb pfc
//Configure the RDMA link forwarding priority.
priority 0 2
//Configure PFC deadlock detection.
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1
interface 25GE 1/0/1
//Configure the port forwarding priority and QoS parameters.
undo flow-control
dcb pfc enable mode manual
dcb pfc buffer 2 xoff dynamic 4 hdrm 2000
qos drr 0 2
qos queue 0 drr weight 10
qos queue 2 drr weight 90
qos buffer queue 0 shared-threshold dynamic 1
qos buffer queue 2 shared-threshold dynamic 10
qos queue 2 wred ecn_25G
qos queue 2 ecn
//Validate the configuration.
commit
//Exit the configuration view of port 25GE 1/0/1.
quit
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1.
interface 25GE 1/0/1
//Set the port to work in trunk mode.
port link-type trunk
//Configure the PVID.
port trunk pvid vlan 1
//Configure allowed VLAN IDs.
port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104
4011
port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300
to 2303 4005 4007 4008 4010
//Validate the port configuration.
commit
//Exit the configuration view of port 25GE 1/0/1.
quit
----End
stp region-configuration
//Configure a spanning tree instance.
instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203
1300 to 1303 4005 4007
instance 1 vlan 4010 4011
instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008
//Validate the spanning tree configuration.
commit
//Exit the spanning tree configuration view.
quit
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1.
interface 25GE 1/0/1
//Enable root bridge protection on the port.
stp root-protection
//Enable the edge port function.
stp edged-port enable
//Validate the port configuration.
commit
//Exit the configuration view of port 25GE 1/0/1.
quit
NOTE
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1.
interface 25GE 1/0/1
//Enable LLDP on the port.
undo lldp disable
//Allow LLDP packet transmission and reception.
lldp admin-status txrx
//Validate all the preceding configurations.
commit
//Exit the configuration view of port 25GE 1/0/1
quit
//Create a WRED drop profile and enter the WRED drop profile view.
drop-profile ecn_25G
//Configure ECN parameters.
ecn buffer-size low-limit 7000 high-limit 200000 discard-percentage 30
//Validate the configuration.
commit
//Exit the WRED drop profile view.
quit
//Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
dcb pfc deadlock-detect interval 100
//Validate the configuration.
commit
//Enter the default PFC configuration view.
dcb pfc
//Configure the RDMA link forwarding priority.
priority 0 2
//Configure PFC deadlock detection.
priority 0 deadlock-detect time 2 deadlock-recovery time 15
priority 0 turn-off threshold 20
priority 2 deadlock-detect time 2 deadlock-recovery time 15
priority 2 turn-off threshold 20
//Validate the configuration.
commit
//Exit the global RDMA configuration view.
quit
NOTE
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1
interface 25GE 1/0/1
//Configure the port forwarding priority and QoS parameters.
undo flow-control
dcb pfc enable mode manual
dcb pfc buffer 2 xoff dynamic 4 hdrm 2000
qos drr 0 2
qos queue 0 drr weight 10
qos queue 2 drr weight 90
qos buffer queue 0 shared-threshold dynamic 1
qos buffer queue 2 shared-threshold dynamic 10
qos queue 2 wred ecn_25G
qos queue 2 ecn
//Validate the configuration.
commit
//Exit the configuration view of port 25GE 1/0/1.
quit
The following uses port 25GE 1/0/1 as an example. Perform this step on ports 25GE
1/0/1 to 25GE 1/0/48 in sequence.
//Enter the configuration view of port 25GE 1/0/1.
interface 25GE 1/0/1
//Set the port to work in trunk mode.
port link-type trunk
//Configure the PVID.
port trunk pvid vlan 1
//Configure allowed VLAN IDs.
port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104
4011
port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300
to 2303 4005 4007 4008 4010
//Validate the port configuration.
commit
//Exit the configuration view of port 25GE 1/0/1.
quit
----End
stp region-configuration
//Configure a spanning tree instance.
instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203
1300 to 1303 4005 4007
instance 1 vlan 4010 4011
instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008
//Validate the spanning tree configuration.
commit
//Exit the spanning tree configuration view.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Enable root bridge protection on the port.
stp root-protection
//Enable the edge port function.
stp edged-port enable
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
NOTE
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Enable LLDP on the port.
undo lldp disable
//Allow LLDP packet transmission and reception.
lldp admin-status txrx
//Validate all the preceding configurations.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
//Create a WRED drop profile and enter the WRED drop profile view.
drop-profile ecn_100G
//Configure ECN parameters.
ecn buffer-size low-limit 7000 high-limit 750000 discard-percentage 30
//Validate the configuration.
commit
//Exit the WRED drop profile view.
quit
//Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
dcb pfc deadlock-detect interval 100
//Validate the configuration.
commit
//Enter the default PFC configuration view.
dcb pfc
//Configure the RDMA link forwarding priority.
priority 2 3
//Configure PFC deadlock detection.
priority 2 deadlock-detect time 2 deadlock-recovery time 15
priority 2 turn-off threshold 20
priority 3 deadlock-detect time 2 deadlock-recovery time 15
priority 3 turn-off threshold 20
//Validate the configuration.
commit
//Exit the global RDMA configuration view.
quit
NOTE
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Configure the port forwarding priority and QoS parameters.
undo flow-control
dcb pfc enable mode manual
dcb pfc buffer 2 xoff dynamic 4
dcb pfc buffer 3 xoff dynamic 4
qos drr 0 2 3
qos queue 0 drr weight 10
qos queue 2 drr weight 90
qos queue 3 drr weight 90
qos buffer queue 0 shared-threshold dynamic 1
qos buffer queue 2 shared-threshold dynamic 10
qos buffer queue 3 shared-threshold dynamic 10
qos queue 2 wred ecn_100G
qos queue 3 wred ecn_100G
qos queue 2 ecn
qos queue 3 ecn
//Validate the configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Set the port to work in trunk mode.
port link-type trunk
//Configure the PVID.
port trunk pvid vlan 1
//Configure allowed VLAN IDs.
port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104
4011
port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300
to 2303 4005 4007 4008 4010
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
----End
stp region-configuration
//Configure a spanning tree instance.
instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203
1300 to 1303 4005 4007
instance 1 vlan 4010 4011
instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008
//Validate the spanning tree configuration.
commit
//Exit the spanning tree configuration view.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Enable root bridge protection on the port.
stp root-protection
//Enable the edge port function.
stp edged-port enable
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
NOTE
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Enable LLDP on the port.
undo lldp disable
//Allow LLDP packet transmission and reception.
lldp admin-status txrx
//Validate all the preceding configurations.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
//Create a WRED drop profile and enter the WRED drop profile view.
drop-profile ecn_100G
//Configure ECN parameters.
ecn buffer-size low-limit 7000 high-limit 750000 discard-percentage 30
//Validate the configuration.
commit
//Exit the WRED drop profile view.
quit
//Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
dcb pfc deadlock-detect interval 100
//Validate the configuration.
commit
//Enter the default PFC configuration view.
dcb pfc
//Configure the RDMA link forwarding priority.
priority 2 3
//Configure PFC deadlock detection.
priority 2 deadlock-detect time 2 deadlock-recovery time 15
priority 2 turn-off threshold 20
priority 3 deadlock-detect time 2 deadlock-recovery time 15
priority 3 turn-off threshold 20
//Validate the configuration.
commit
//Exit the global RDMA configuration view.
quit
NOTE
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Configure the port forwarding priority and QoS parameters.
undo flow-control
dcb pfc enable mode manual
dcb pfc buffer 2 xoff dynamic 4
dcb pfc buffer 3 xoff dynamic 4
qos drr 0 2 3
qos queue 0 drr weight 10
qos queue 2 drr weight 90
qos queue 3 drr weight 90
qos buffer queue 0 shared-threshold dynamic 1
qos buffer queue 2 shared-threshold dynamic 10
qos buffer queue 3 shared-threshold dynamic 10
qos queue 2 wred ecn_100G
qos queue 3 wred ecn_100G
qos queue 2 ecn
qos queue 3 ecn
//Validate the configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Set the port to work in trunk mode.
port link-type trunk
//Configure the PVID.
port trunk pvid vlan 1
//Configure allowed VLAN IDs.
port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104
4011
port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300
to 2303 4005 4007 4008 4010
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
----End
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Enable root bridge protection on the port.
stp root-protection
//Enable the edge port function.
stp edged-port enable
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
lldp fast-count 3
//Set the LLDP restart delay.
lldp restart 1
//Set the interval for sending LLDP packets.
lldp transmit interval 20
//Configure the LLDP keepalive factor.
lldp transmit multiplier 10
//Validate all the preceding configurations.
commit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Enable LLDP on the port.
undo lldp disable
//Allow LLDP packet transmission and reception.
lldp admin-status txrx
//Validate all the preceding configurations.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Configure the port forwarding priority and QoS parameters.
dcb pfc enable mode manual
dcb pfc buffer 2 xon dynamic 6 xoff dynamic 9
dcb pfc buffer 3 xon dynamic 6 xoff dynamic 9
qos drr 0 2 3
qos queue 0 drr weight 10
qos queue 2 drr weight 90
qos queue 3 drr weight 90
qos buffer queue 0 shared-threshold dynamic 1
qos buffer queue 2 shared-threshold dynamic 10
qos buffer queue 3 shared-threshold dynamic 10
qos queue 2 wred ecn_100G
qos queue 3 wred ecn_100G
qos queue 2 ecn
qos queue 3 ecn
//Validate the configuration.
commit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Set the port to work in trunk mode.
port link-type trunk
//Configure the PVID.
port trunk pvid vlan 1
//Configure allowed VLAN IDs.
port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104
4011
port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300
to 2303 4005 4007 4008 4010
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
----End
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Enable root bridge protection on the port.
stp root-protection
//Enable the edge port function.
stp edged-port enable
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Enable LLDP on the port.
undo lldp disable
//Allow LLDP packet transmission and reception.
lldp admin-status txrx
//Validate all the preceding configurations.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
commit
//Enter the default PFC configuration view.
dcb pfc
//Configure the RDMA link forwarding priority.
priority 2 3
//Configure PFC deadlock detection.
priority 2 turn-off threshold 30
priority 3 turn-off threshold 30
dcb pfc deadlock recovery-behavior forwarding slot 1
dcb pfc deadlock-detect timer 200
dcb pfc deadlock-recovery timer 1500
//Validate the configuration.
commit
//Exit the global RDMA configuration view.
quit
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Configure the port forwarding priority and QoS parameters.
dcb pfc enable mode manual
dcb pfc buffer 2 xon dynamic 6 xoff dynamic 9
dcb pfc buffer 3 xon dynamic 6 xoff dynamic 9
qos drr 0 2 3
qos queue 0 drr weight 10
qos queue 2 drr weight 90
qos queue 3 drr weight 90
qos buffer queue 0 shared-threshold dynamic 1
qos buffer queue 2 shared-threshold dynamic 10
qos buffer queue 3 shared-threshold dynamic 10
The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE
1/0/1 to 100GE 1/0/32 in sequence.
//Enter the configuration view of port 100GE 1/0/1.
interface 100GE 1/0/1
//Change the mode of an Ethernet interface from Layer 3 to Layer 2.
portswitch
//Set the port to work in trunk mode.
port link-type trunk
//Configure the PVID.
port trunk pvid vlan 1
//Configure allowed VLAN IDs.
port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104
4011
port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300
to 2303 4005 4007 4008 4010
//Validate the port configuration.
commit
//Exit the configuration view of port 100GE 1/0/1.
quit
----End
Prerequisites
● The system network has been connected based on the controller expansion
scenario. For details, see 3.1.2.4 (Optional) Connection Planning for
Multiple Controller Enclosures.
● Controllers on all controller enclosures have the same memory size.
NOTE
You can run the show memory command to query the memory size of a controller.
● All controller enclosures have the same software version.
NOTE
You can run the show version all command to query the software version of
controller enclosures.
● Controller enclosures have been powered on. For a 4 U controller enclosure,
ensure that disk enclosures with coffer disk labels have been properly
connected to the controller enclosure.
● There are no critical or major alarms in the storage system.
● The public/private key pair and password of ibc_os_hs are the default values.
● The IP addresses of the management network ports on controller enclosures
connected to the management network must be different but on the same
network segment. For details, see 5.1.1.1 Changing the Initial IP Address of
the Management Network Port over a Serial Port and 5.1.1.3 (Optional)
Changing IP Addresses of Management Network Ports Using
DeviceManager.
Precautions
● SmartKit is used to expand controllers for the storage system.
● The operation procedure varies according to the SmartKit version. If you use
SmartKit of a different version, the GUI you see may be different from that in
this section.
● The Auto Discovery (AD) process has been enabled on all of the controllers in
the new controller enclosures 1 and 2. For details on how to enable the AD
process, see 6.1 What Can I Do If Controller Expansion Fails Because the
Process Lasts for Over 24 Hours After the Controllers to Be Added Are
Powered On?
NOTE
The AD process is used for message forwarding between controllers during expansion.
After enabling the AD process on all of the new controllers, you must add the new
controllers using SmartKit within 24 hours. Otherwise, controller expansion will fail
and you need to enable the AD process on the new controllers again.
Procedure
Step 1 Download SmartKit.
NOTE
If the maintenance terminal cannot access the Internet, you need to use another terminal
that can access the Internet to download the SmartKit installation package. Then copy
the package to the maintenance terminal.
● If you are an enterprise user:
a. Use the maintenance terminal to log in to https://support.huawei.com/
enterprise and Choose Tools > SmartKit.
b. Select the latest version.
c. In the Version and Patch Software area, select and download the
software you need.
● If you are a carrier user:
a. Use the maintenance terminal to log in to https://support.huawei.com.
In the search box on the home page, type SmartKit and choose the
associated SmartKit path from the drop-down list.
b. On the search result page, click the Software tab.
c. On the Software tab page, click the latest version.
The page for downloading the software is displayed.
d. In the Software area, download the software you need.
Step 2 Install SmartKit.
1. On the maintenance terminal, run the SmartKit installation package and
follow the instructions provided by the installation wizard to install SmartKit.
After the installation is complete, SmartKit will automatically start.
2. Type your support website account as prompted to activate SmartKit and read
the safety precautions.
NOTE
For details about offline installation, see "Function Export" and "Function Import" in the
SmartKit User Guide.
Step 4 Add the storage device for which you want to expand controllers to SmartKit.
1. In the main window of SmartKit, click the Device Management tab and
select Add.
The dialog box to add devices is displayed.
2. In Basic Information, select Specify IP Address (add a device by the IP
address) and enter the management IP address of the storage system. Then
click Next.
3. In Config Information, enter the user name and password of the storage
system administrator and click Finish.
NOTE
● When a device is added for the first time or a device certificate is not trusted, a message
is displayed, indicating that the connection is not trusted.
● When an SSH server is added for the first time or after the fingerprint of an SSH server
changes, a prompt asks you whether you want to continue to register the SSH server.
Step 5 In the main window of SmartKit, choose Home > Storage > Capacity Expansion >
Add Controllers.
The Add Controllers page is displayed. Add the controllers by following the
wizard on SmartKit. For the detailed operations, see 7.2.2 Using SmartKit for
Capacity Expansion (Switched Network).
Step 6 Check the health status and running status of the added controllers and the disk
enclosure.
Log in to OceanStor DeviceManager and check whether Health Status of the new
controllers and disk enclosure is Normal and Running Status is Online.
● If yes, the capacity expansion is successful.
● If no, contact Huawei technical support.
----End
Symptom
SmartKit may fail to expand controllers because:
● The configuration information about controller enclosure (enclosure SN: %s)
fails to be modified.
● The BMC information about controller enclosure (enclosure SN: %s) fails to
be synchronized.
NOTICE
Fault Diagnosis
Expansion failure
Yes
Yes
Check whether the new
controllers are normal.
No
NOTICE
When handling controller expansion failure, remove cables of storage systems that
have not been added to the cluster to isolate controllers.
Procedure
Step 1 Roll back controller expansion in the original storage system in normal mode.
1. Run the change user_mode current_mode user_mode=developer command
to go to the developer view.
NOTE
Step 2 Perform the operations described in 5.2.3.2 Clearing the Controllers That Failed
to Be Added (Applicable to the OceanStor 2000, 5000, and 5000F V5 Series).
----End
Prerequisites
You have removed the cables of storage systems that have not been added to the
cluster to isolate controllers.
Procedure
Step 1 Log in to a controller that failed to be added via its serial port or management
network port and check whether the following information is displayed in the CLI.
Storage: minisystem>
● If yes, the controller is in minisystem mode. Go to Step 2.
● If no, the controller is not in minisystem mode. You must enter the
minisystem mode before proceeding with Step 2. You can manually enter the
minisystem mode as follows:
– Run change user_mode current_mode user_mode=developer to enter
the developer mode and then run minisystem to enter the minisystem
mode.
developer:/>minisystem
Storage: minisystem>
– When the storage system is starting, System is not ready, Please
wait(Ctrl+c to exit or Input minisystem to minisystem mode) is
displayed on the CLI. Run minisystem to enter the minisystem mode.
Authorized users only. All activities may be monitored and reported.
WARNING! The remote SSH server rejected X11 forwarding request.
System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode).
\minisystem
NOTE
If you cannot log in to a controller (for example, controller A) using the serial port or
management network port, log in to another controller in the controller enclosure (for
example, controller B) and run the sshtoremoteExt SlotId command in minisystem mode
to log in to controller A. SlotId is controller A's slot number and its value ranges from 0 to
N–1, where N indicates the total number of controllers after controller expansion.
2 U controller enclosures are used as an example. The slot IDs of controllers A and B in
controller enclosure 0 are 0 and 1, those in controller enclosure 1 are 2 and 3, and so on.
4 U controller enclosures are used as an example. The slot IDs of controllers A, B, C, and D
in controller enclosure 0 are 0, 1, 2, and 3, those in controller enclosure 1 are 4, 5, 6, and 7,
and so on.
Step 2 Run bdm_diskbomlist.sh showdisk and check whether Valid of coffer disks (Slot
ranges from 0 to 3 and ID is greater than 63) is Normal.
● If yes, go to Step 4.
● If no, go to Step 3.
Step 3 Wait for 20 minutes and run bdm_diskbomlist.sh showdisk again to check
whether Valid of the coffer disks is Normal.
● If yes, go to Step 4.
● If no, go to Step 6.
Step 4 Run showsysstatus. The value of local node id is the ID of the current controller.
Check whether the controller's status is normal.
● If yes, perform Step 1 to Step 4 on each controller that failed to be added
separately. If all controllers' status are normal, expand controllers again using
the expansion tool.
NOTE
If you still want to clear information about the new controller, go to Step 7.
● If no, go to Step 5.
Step 5 Run sys.sh clearnode -d -all in minisystem mode. The system will clear
information automatically. This process typically takes about 6 minutes and will
not exceed 30 minutes.
Check whether Success is returned.
● If yes, go to Step 9.
● If no, go to Step 8.
NOTE
● This operation will restore all services and configurations of the controller to the initial
state.
● This operation will initialize user passwords. For the default password of the system
administrator, see Security Configuration Guide of the corresponding product model.
Step 6 Run sys.sh clearnode -df -all in minisystem mode. The system will clear
information automatically. This process typically takes about 6 minutes and will
not exceed 30 minutes.
● If yes, go to Step 9.
● If no, go to Step 8.
NOTE
● This operation will restore all services and configurations of the controller to the initial
state.
● This operation will initialize user passwords. For the default password of the system
administrator, see Security Configuration Guide of the corresponding product model.
Step 7 Run sys.sh clearnode -d in minisystem mode. The system will clear information
automatically. This process typically takes about 6 minutes and will not exceed 30
minutes.
After the system clears information automatically, check whether the "FAILED"
message is not displayed.
● This operation will restore all services and configurations of the controller to the initial
state.
● This operation will initialize user passwords. For the default password of the system
administrator, see Security Configuration Guide of the corresponding product model.
Step 8 Observe the indicators to determine whether the controller is running properly
and the coffer disks are normal. For the indicator meanings, see the Product
Description of the corresponding product model.
● If the controller and coffer disks are normal, return to Step 1 and perform the
operations again.
● If a controller fails to be powered on, log in to the controller and enter the
minisystem mode. Then run os_backup_info.sh to collect logs and access the
log path to obtain the logs.
----End
Prerequisites
You have removed the cables of storage systems that have not been added to the
cluster to isolate controllers.
Procedure
Step 1 Log in to a controller that failed to be added via its serial port or management
network port and check whether the following information is displayed in the CLI.
Storage: minisystem>
System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode).
\minisystem
NOTE
If you cannot log in to a controller (for example, controller A) using the serial port or
management network port, log in to another controller in the controller enclosure (for
example, controller B) and run the sshtoremoteExt SlotId command in minisystem mode
to log in to controller A. SlotId is controller A's slot number and its value ranges from 0 to
N–1, where N indicates the total number of controllers after controller expansion.
2 U controller enclosures are used as an example. The slot IDs of controllers A and B in
controller enclosure 0 are 0 and 1, those in controller enclosure 1 are 2 and 3, and so on.
4 U controller enclosures are used as an example. The slot IDs of controllers A, B, C, and D
in controller enclosure 0 are 0, 1, 2, and 3, those in controller enclosure 1 are 4, 5, 6, and 7,
and so on.
Step 3 Wait for 20 minutes. If the configuration disk enclosure is a smart SAS or NVMe
disk enclosure, run the sys.sh showallspecdiskinfo command again to check
whether coffer disks are connected. If the configuration disk enclosure is a SAS
disk enclosure, run the bdm_diskbomlist.sh showdisk command again to check
whether coffer disks are connected.
● If yes, go to Step 4.
● If no, go to Step 6.
Step 4 Run showsysstatus. The value of local node id is the ID of the current controller.
Check whether the controller's status is normal.
● If yes, perform Step 1 to Step 4 on each controller that failed to be added
separately. If all controllers' status are normal, expand controllers again using
the expansion tool.
NOTE
If you still want to clear information about the new controller, go to Step 7.
● If no, go to Step 5.
Step 5 Run sys.sh clearnode -d -all in minisystem mode. The system will clear
information automatically. This process typically takes about 6 minutes and will
not exceed 30 minutes.
● If yes, go to Step 9.
● If no, go to Step 8.
NOTE
● This operation will restore all services and configurations of the controller to the initial
state.
● This operation will initialize user passwords. For the default password of the system
administrator, see Security Configuration Guide of the corresponding product model.
Step 6 Run sys.sh clearnode -df -all in minisystem mode. The system will clear
information automatically. This process typically takes about 6 minutes and will
not exceed 30 minutes.
● If yes, go to Step 9.
● If no, go to Step 8.
NOTE
● This operation will restore all services and configurations of the controller to the initial
state.
● This operation will initialize user passwords. For the default password of the system
administrator, see Security Configuration Guide of the corresponding product model.
Step 7 Run sys.sh clearnode -d in minisystem mode. The system will clear information
automatically. This process typically takes about 6 minutes and will not exceed 30
minutes.
After the system clears information automatically, check whether the "FAILED"
message is not displayed.
● This operation can only clear the information on the controller that you have logged in
to. Therefore, you must log in to all of the new controllers one by one and run this
command.
● This operation will restore all services and configurations of the controller to the initial
state.
● This operation will initialize user passwords. For the default password of the system
administrator, see Security Configuration Guide of the corresponding product model.
Step 8 Observe the indicators to determine whether the controller is running properly
and the coffer disks are normal. For the indicator meanings, see the Product
Description of the corresponding product model.
● If the controller and coffer disks are normal, return to Step 1 and perform the
operations again.
● If the controller or coffer disks are abnormal, go to Step 11.
Step 9 After all controllers have been cleared, log in to any of them and run sys.sh
resetengine -n to reset all controllers in the current controller enclosure.
● If the controller enclosure becomes normal after the controllers have been
reset, go to Step 10.
● If a controller fails to be powered on, log in to the controller and enter the
minisystem mode. Then run os_backup_info.sh to collect logs and access the
log path to obtain the logs.
----End
Table 5-19 Port connections between the key management server and switch
Port ID Port on the Key Port on the Switch Port ID
Management Server
0 Key_Port_Y Switch_Port_Y 2
NOTE
If you use the multipathing software built in your operating system, see the Huawei SAN
Storage Host Connectivity Guide for XXX, where XXX indicates the operating system, such as
Windows.
Prerequisites
● SmartKit of a correct version has been installed on the maintenance terminal.
You can check the version information in the version mapping table. To obtain
the version mapping table, log in to https://support.huawei.com/
enterprise/, enter your storage model in the search box, and select the
associated path to the product documentation page. Then find and download
the version mapping table.
● You have obtained the IP address of the management network port and the
login user name and password.
Procedure
Step 1 Log in to SmartKit. On the Storage tab, select Site Deployment Quality
Inspection in Site Deployment Delivery.
The Inspection Wizard Step 3-1: Check Site Deployment Quality Standards
page is displayed.
Step 5 Select the storage device, and click Fill Result.
The Inspection Wizard Step 3-2: Select Check Items page is displayed.
Step 6 Select the storage device, and click desired check items.
NOTE
● After the inspection is complete, the inspection results are automatically saved and an
inspection report is generated. You can:
– Click Open the result directory to view the inspection result data.
– Click View the report to view the inspection report.
● If any check item has failed, rectify the fault according to the handling suggestions.
----End
6 FAQs
Answer
If a controller expansion lasts for over 24 hours after the controllers to be added
are powered on, the AD process in the storage system will be disabled. As a result,
controllers in the cluster cannot communicate with each other, leading to a
controller expansion failure. You can enable the AD process as follows:
NOTE
Step 1 Log in to the CLI of any controller in the new controller enclosure.
Step 3 Run the change ad_process action=startup command to enable the AD process.
NOTE
● For versions earlier than V500R007C60SPC300, the command for starting the AD
process must be executed on each controller. If you cannot log in to a controller (for
example, controller A) using the serial port or management network port, log in to
another controller in the controller enclosure (for example, controller B) and run the
sshtoremoteExt SlotId command in the minisystem view to log in to controller A.
SlotId is the slot number of controller A and its value ranges from 0 to N-1, where N
indicates the maximum number of controllers that can be inserted in the current
controller enclosure.
● For V500R007C60SPC300 and later versions, the command for starting the AD process is
executed on any controller, and the AD process is enabled on all controllers in the
controller enclosure.
Step 4 Run the show ad_process status command to check whether the status of the AD
process is Online. If the status is Online, the AD process has been enabled.
For details, see the Advanced O&M Command Reference specific to your product
model and version.
----End
Answer
On Brocade Fibre Channel series switches, NPIV is enabled by default.
Cisco switches
Answer
● After the primary AD domain controller is configured, you must create AD
domain users and groups on the AD domain controller. An administrator can
centrally manage domain users and groups and allocate them to different
users.
● A user can log in to a client host in the AD domain as a domain user and is
authenticated by the primary AD domain controller.
● This section uses Windows Server 2008 R2 as an example to explain how to
create AD domain users and groups on the AD domain controller.
Step 1 Log in to the Windows AD domain server. Choose Start > Administrative Tools >
Active Directory Users and Computers.
The Active Directory Users and Computers page is displayed.
Step 2 Create a user.
1. In the Active Directory Users and Computers dialog box, right-click Users.
2. Choose New > User.
5. Enter and confirm the user password. Deselect User must change password
at next logon. Click Next.
6. Click OK.
Return to the Active Directory Users and Computers dialog box.
Step 4 Add a user to a group.
1. In the Active Directory Users and Computers dialog box, right-click a user to
add to a group.
2. Select Add to a group.
3. In the Enter the object name to select text box, enter the name of the group
to which the user is added.
4. Click OK.
A message is displayed, indicating that the operation succeeded.
5. Click OK.
----End
Prerequisites
The web service has been enabled for the Windows AD domain server.
Procedure
Step 1 Access http://localhost/certsrv/ on the Internet Explorer.
Step 2 Click Download a CA certificate, certificate chain, or CRL.
Step 3 Select the CA certificate you want to export, set the encoding mode to DER, and
click Download CA certificate.
The exported CA certificate uses the default format of Windows. You must convert
it to the pem format before importing it to the storage system.
NOTE
To convert the format, copy the CA certificate to a Linux server and run the openssl x509 -
in ./XXX.cer -inform DER -out YYY.pem -outform PEM command in the directory where
the CA certificate is saved.
In the preceding command, XXX represents the name of the CA certificate before
conversion, and YYY represents the name after conversion.
Answer
You can replace the default security certificates of the DeviceManager server and
user browser with self-signed security certificates and private key files to eliminate
the privacy error displayed when you log in to DeviceManager. The configuration
procedure is as follows:
Step 1 Prepare the OpenSSL environment.
1. Prepare a Linux-based device where the OpenSSL tool is installed. (Generally,
the OpenSSL tool has been pre-installed in a CentOS or Ubuntu system.) Run
the openssl version command to verify that the OpenSSL tool version is 0.9.8j
or later.
CTU1000047802:~ # openssl version
OpenSSL 0.9.8j-fips 07 Jan 2009
2. Run the find / -name openssl.cnf command to identify the location of the
openssl.cnf file.
Generally, the openssl.cnf file is under /etc/ssl.
CTU1000047802:/ # cd /etc/ssl
CTU1000047802:/etc/ssl # ls
ca.key ca.pem cacert.pem cert.csr certs demoCA openssl.cnf private private.key
Step 2 Use the OpenSSL tool to generate CA private key and CA certificate files.
1. Create directories and files related to certificate files.
CTU1000047802:/ # mkdir new9
CTU1000047802:/ # cd new9
CTU1000047802:/new9 # mkdir demoCA
CTU1000047802:/new9 # mkdir demoCA/csr demoCA/private demoCA/jks demoCA/newcerts
CTU1000047802:/new9 # touch demoCA/index.txt
CTU1000047802:/new9 # echo 03 > ./demoCA/serial
CN is the common name for the CA certificate. To avoid certificate alarms, set
this parameter to *.*.*.*.
– You must log in to the storage system using the CLI and import the certificate and
key files shared in 4.b.
– The import ssl_certificate command must be executed on each controller to
import the shared certificate and key files.
admin:/>import ssl_certificate ip=XX.XX.117.211 user=admin password=*********
cert_file=deviceManager_cert.pem key_file=deviceManager_key.pem port=32 protocol=SFTP
DANGER: You are about to use an unencrypted SSL certificate to replace the current SSL certificate.
Security risks may exist in the unencrypted certificate. This operation will cause DeviceManager
automatically to restart, interrupting services. The certificate you are about to import has the
following security risks: a certificate loading error (the certificate fails to be loaded, the certificate key
fails to be obtained, certificate public information fails to be obtained, the certificate signature
algorithm fails to be obtained).
Suggestion:
1. Use an encrypted certificate to replace the current certificate.
2. Before running the command, confirm that you want to replace the SSL certificate.
Have you read danger alert message carefully?(y/n)y
Are you sure you really want to perform the operation?(y/n)y
Command executed successfully.
4. Restart DeviceManager.
admin:/>change user_mode current_mode user_mode=developer
DANGER: You are about to switch to the developer view. Commands in this view must be run under
the guidance of R&D engineers. You can choose whether to run this command. If you run this
command to switch to the developer view, it means that you know risks of running commands in the
developer view. Device vendors are not responsible for any loss or damage caused to the user or
others by running commands in the developer view.
1. Running the command in the developer view may cause system reset, restart, offline, service
interruption, data loss, and data inconsistency.
2. Running the command in the developer view may cause the performance to decrease.
3. Running the command in the developer view to delete or remove configurations may have impact
on the service and data.
4. Running the command in the developer view may cause system alarms.
Suggestion: Run this command under the guidance of R&D engineers.
Have you read danger alert message carefully?(y/n)y
Are you sure you really want to perform the operation?(y/n)y
developer:/>reboot ism
DANGER: You are about to restart the DeviceManager for the storage system. This operation causes
the DeviceManager unavailable temporarily.
Suggestion: Before performing this operation, ensure that all users have exit the DeviceManager.
Have you read danger alert message carefully?(y/n)y
Are you sure you really want to perform the operation?(y/n)y
Command executed successfully.
5. Import the certificate file to the browser.
The following uses Google Chrome (67.0) as an example.
NOTE
For details about how to replace the security certificates of other browsers, see section
"Importing a Security Certificate" in the DeviceManager Online Help.
a. Open Google Chrome and choose Settings > Advanced > Manage
Certificate > Trusted Root Certification Authorities > Import. The
Certificate Import Wizard dialog box is displayed.
b. Select and import the certificate file (RootCA.crt in this example) as
prompted.
c. Restart the browser after the certificate is successfully imported.
d. Log in to the storage system again. No privacy error is generated.
----End
Answer
The check method varies depending on whether a proxy server is configured or
not:
● Proxy Server Not Configured
● Proxy Server Configured
3. Test the connection between the DNS server and storage system. If the
connection is normal, go to Step 2.
– You can click Test of each DNS IP address to test its availability.
– You can click Test All to test the connection between the DNS server and
storage system.
Step 2 Obtain the URL of the technical support center to which alarm and event data of
the storage system will be uploaded.
● Carrier in China region: icloudservice-cn.huawei.com
● Carrier in Romania region: itr-eservicero-carrier.huawei.com
● Enterprise in China region: ecloudService-cn.huawei.com
● Enterprise in Romania region: itr-eservicero-ent.huawei.com
Step 4 Check whether the storage system can be properly connected to ports 7448, 8448,
and 9448 of the technical support center.
NOTE
● XXX.XXX.XXX.XXX is the IP address of the technical support center obtained in Step 3.4.
● If the command output displays Connected to XXX.XXX.XXX.XXX, the connection is
normal.
● If the connection is abnormal, check the connectivity between the storage system and
the external network, for example, firewall configuration.
Storage: minisystem> telnet XXX.XXX.XXX.XXX 7448
Trying XXX.XXX.XXX.XXX...
Connected to XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX).
Escape character is '^]'.
----End
Step 2 Obtain the URL of the technical support center to which alarm and event data of
the storage system will be uploaded.
● Carrier in China region: icloudservice-cn.huawei.com
● Carrier in Romania region: itr-eservicero-carrier.huawei.com
● Enterprise in China region: ecloudService-cn.huawei.com
● Enterprise in Romania region: itr-eservicero-ent.huawei.com
Step 4 Check whether the proxy server can be properly connected to ports 7448, 8448,
and 9448 of the technical support center.
Log in to the management interface of the proxy server, and run the telnet
XXX.XXX.XXX.XXX 7448, telnet XXX.XXX.XXX.XXX 8448, and telnet
XXX.XXX.XXX.XXX 9448 commands.
NOTE
● XXX.XXX.XXX.XXX is the IP address of the technical support center obtained in Step 3.2.
● If the command output displays Connected to XXX.XXX.XXX.XXX, the connection is
normal.
● If the connection is abnormal, check the configuration of the firewall between the proxy
server and the external network.
● If the connection is normal but alarms and logs cannot be sent to the eService after the
eService is configured, enable the HTTP proxy service for ports 7448, 8448, and 9448 of
the proxy server by referring to the related product documentation of the proxy server.
[root@localhost ~]# telnet XXX.XXX.XXX.XXX 7448
Trying XXX.XXX.XXX.XXX...
Connected to XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX).
Escape character is '^]'.
----End
Answer
Update your Internet Explorer, use any other browser supported by
DeviceManager, or use CLI commands to change the cipher suite to the
compatible mode.
Step 1 Log in to the CLI. For details, see 5.1.1.4 Logging In to the CLI.
Step 2 Run the change devicemanager ciphersuite suite=compatible command to
change the cipher suite mode to compatible.
admin:/>change devicemanager ciphersuite suite=compatible
WARNING: You are about to change the cipher suite type of DeviceManager.
1. If you change the cipher suite type to "safe", data transmission security will increase, but DeviceManager
may be inaccessible for clients with a lower encryption level.
2. If you change the cipher suite type to "compatible", data transmission security will decrease and user
data may have security risks.
Suggestion: After performing this operation, manually restart DeviceManager to make the operation take
effect.Have you read warning message carefully?(y/n)y
----End
7 Appendix
Parameter Description
6. Click Next.
The Information page is displayed.
7. Read and confirm the displayed message, and click OK.
The Start Evaluation page is displayed and the system starts evaluating the
capacity expansion solution.
NOTE
– After the evaluation is complete, click Open the report to go to the save path of
the evaluation report. The report is a .zip file named by the evaluation time.
– You can also click View the report to open the report directly.
8. Click Finish.
NOTICE
Rectify the failed items (if any) according to the suggestions and evaluate the
solution again. If the items fail again, contact Huawei technical support engineers
for assistance. Otherwise, risks may arise during capacity expansion.
If any check item fails, rectify the faults and perform the check again.
After all check items are passed, click Next.
The Confirm the Networking Environment page is displayed.
NOTICE
Ensure that cables are properly connected according to the network diagram.
Select I have powered on the controller that is added and click Next.
The Scan for Node Information page is displayed.
4. The system automatically detects node information. If the system fails to
detect the information of the new controllers, rectify the faults as prompted
and click Rescan.
After the system obtains the node information, confirm and select the
controller enclosure to be expanded based on Controller enclosure SN.
After confirming all controller enclosures, select I have read the previous
information and understood consequences of the operation and click
Next.
The Check the Added Controller page is displayed.
NOTE
You can query the SN of a controller enclosure on the label on its exterior, for
example, 2102XXXXXXXXE700000X.
5. The system automatically performs a pre-expansion check.
If the check fails, identify and rectify the failed items. Then click Recheck to
perform the check again.
After all check items are passed, click Next.
The Capacity Expansion page is displayed.
6. The system automatically starts adding controllers.
NOTE
– A Danger dialog box will be displayed indicating that this operation will restore
the new controllers to the default settings.
– Confirm the information in the dialog box and select I have read and understood
the consequence associated with performing this operation and click OK. The
system continues to add controllers.
After the controllers are successfully added, click Next.
The Post-expansion Check page is displayed.
7. The system automatically performs a post-expansion check.
If the check fails, identify and rectify the failed items. Then click Recheck to
perform the check again.
After all check items are passed, click Next.
The Completed page is displayed.
8. Click Finish to complete the expansion.
----End
6. Click Next.
The Information page is displayed.
7. Read and confirm the displayed message, and click OK.
The Start Evaluation page is displayed and the system starts evaluating the
capacity expansion solution.
NOTE
– After the evaluation is complete, click Open the report to go to the save path of
the evaluation report. The report is a .zip file named by the evaluation time.
– You can also click View the report to open the report directly.
8. Click Finish.
NOTICE
Rectify the failed items (if any) according to the suggestions and evaluate the
solution again. If the items fail again, contact Huawei technical support engineers
for assistance. Otherwise, risks may arise during capacity expansion.
If any check item fails, rectify the faults and perform the check again.
After all check items are passed, click Next.
The Confirm the Networking Environment page is displayed.
3. Click the network diagram to obtain the network diagram.
NOTICE
Ensure that cables are properly connected according to the network diagram.
Select I have powered on the controller that is added and click Next.
The Configure Data Switch page is displayed.
4. Enter the configuration information about the data switch, as described in
Table 7-4.
Parameter Description
After the system obtains the node information, confirm and select the
controller enclosure to be expanded based on Controller enclosure SN.
After confirming all controller enclosures, select I have read the previous
information and understood consequences of the operation and click
Next.
The Check the Added Controller page is displayed.
NOTE
You can query the SN of a controller enclosure on the label on its exterior, for
example, 2102XXXXXXXXE700000X.
6. The system automatically performs a pre-expansion check.
If the check fails, identify and rectify the failed items. Then click Recheck to
perform the check again.
After all check items are passed, click Next.
The Capacity Expansion page is displayed.
7. The system automatically starts adding controllers.
NOTE
A Danger dialog box will be displayed indicating that this operation will restore the
new controllers to the default settings.
Confirm the information in the dialog box and select I have read and understood the
consequence associated with performing this operation and click OK. The system
continues to add controllers.
After the controllers are successfully added, click Next.
The Post-expansion Check page is displayed.
8. The system automatically performs a post-expansion check.
If the check fails, identify and rectify the failed items. Then click Recheck to
perform the check again.
After all check items are passed, click Next.
The Completed page is displayed.
9. Click Finish to complete the expansion.
----End
NOTE
● SAS disk enclosures can be cascaded to onboard interface modules or 12 Gbit/s SAS
expansion modules in slots IOM 1.
● High-density disk enclosures are deployed in dual-uplink networking and require two
expansion ports for cascading. The loop ID is the smaller one between two loop IDs to
which the two cascading ports correspond.
For example, the loop ID is 3 if ports P0 and P1 (marked by 3 and 4 in Figure 7-1) in
slots IOM 1 are used to cascade a high-density disk enclosure.
3 4 5 6
1 2
3 4 5 6
1 2
Disk Enclosure ID
DAEXXX indicates a disk enclosure ID. The first X indicates the controller enclosure
ID, the second X indicates the hexadecimal loop ID, and the third X indicates the
number of disk enclosures connected in a loop.
NOTE
● For loops 1 to 6, the second X is 1, 2, ..., 5, and 6, and the third X ranges from 0 to 7 (0
for the first disk enclosure, 1 for the second disk enclosure, and so on).
● For example, the ID of the first disk enclosure in loop 2 of controller enclosure 0 is
DAE020.
Table 7-5 describes the rules for naming disk enclosure IDs in each loop.
P1 4 DAE040 to DAE047
P2 5 DAE050 to DAE057
P3 6 DAE060 to DAE067
Loop ID
Each onboard port or port on an expansion module corresponds to a fixed loop ID,
as shown in orange and blue marks in Figure 7-2.
NOTE
● SAS disk enclosures can be cascaded to onboard interface modules or 12 Gbit/s SAS
expansion modules in slots IOM 1.
● High-density disk enclosures are deployed in dual-uplink networking and require two
expansion ports for cascading. The loop ID is the smaller one between two loop IDs to
which the two cascading ports correspond.
For example, the loop ID is 3 if ports P0 and P1 (marked by 3 and 4 in Figure 7-2) in
slots IOM 1 are used to cascade a high-density disk enclosure.
3 4 5 6
1 2
3 4 5 6
1 2
Disk Enclosure ID
DAEXXX indicates a disk enclosure ID. The first X indicates the controller enclosure
ID, the second X indicates the hexadecimal loop ID, and the third X indicates the
number of disk enclosures connected in a loop.
NOTE
● For loops 1 to 6, the second X is 1, 2, ..., 5, and 6, and the third X ranges from 0 to 7 (0
for the first disk enclosure, 1 for the second disk enclosure, and so on).
● For example, the ID of the first disk enclosure in loop 2 of controller enclosure 0 is
DAE020.
Table 7-6 describes the rules for naming disk enclosure IDs in each loop.
P1 4 DAE040 to DAE047
P2 5 DAE050 to DAE057
P3 6 DAE060 to DAE067
Loop ID
Each onboard port or port on an expansion module corresponds to a fixed loop ID,
as shown in orange and blue marks in Figure 7-3 and Figure 7-4.
NOTE
● SAS disk enclosures can be cascaded to onboard interface modules or 12 Gbit/s SAS
expansion modules in slots IOM 2.
● Smart disk enclosures can be cascaded to 100 Gbit/s RDMA expansion modules in slots
IOM 2, 1, or 0.
● High-density disk enclosures are deployed in dual-uplink networking and require two
expansion ports for cascading. The loop ID is the smaller one between two loop IDs to
which the two cascading ports correspond.
For example, the loop ID is 3 if ports P0 and P1 (marked by 3 and 4 in Figure 7-3) in
slots IOM 2 are used to cascade a high-density disk enclosure.
1 2 3 4 5 6
1 2 3 4 5 6
9 10 7 8
3 4
9 10 7 8
3 4
9 10 7 8
3 4
9 10 7 8
3 4
Disk Enclosure ID
DAEXXX indicates a disk enclosure ID. The first X indicates the controller enclosure
ID, the second X indicates the hexadecimal loop ID, and the third X indicates the
number of disk enclosures connected in a loop.
NOTE
● For loops 1 to 10, the second X is 1, 2, ..., 8, 9, and A, and the third X ranges from 0 to 7
(0 for the first disk enclosure, 1 for the second disk enclosure, and so on).
● For example, the ID of the first disk enclosure in loop 10 of controller enclosure 0 is
DAE0A0.
Table 7-7 describes the rules for naming disk enclosure IDs in each loop.
P1 4 DAE040 to DAE047
P2 5 DAE050 to DAE057
P3 6 DAE060 to DAE067
P1 8 DAE080 to DAE087
P1 10 DAE0A0 to DAE0A7
7.3.4 OceanStor 5500 V5, 5600 V5, 5800 V5, 5500F V5, 5600F
V5, and 5800F V5
Loop ID
Each onboard port or port on an expansion module corresponds to a fixed loop ID,
as shown in orange and blue marks in Figure 7-5 and Figure 7-6.
NOTE
● SAS disk enclosures can be cascaded to onboard interface modules or 12 Gbit/s SAS
expansion modules in slots IOM 3, 4, or 5.
● Smart disk enclosures can be cascaded to 100 Gbit/s RDMA expansion modules in slots
IOM 0, 1, 2, 3, 4, or 5.
● High-density disk enclosures are deployed in dual-uplink networking and require two
expansion ports for cascading. The loop ID is the smaller one between two loop IDs to
which the two cascading ports correspond.
For example, the loop ID is 3 if ports P0 and P1 (marked by 3 and 4 in Figure 7-5) in
slots IOM 3 are used to cascade a high-density disk enclosure.
1 2 11 12 13 14 7 8 9 10 3 4 5 6
1 2 11 12 13 14 7 8 9 10 3 4 5 6
19 20 17 18 15 16
1 2 11 12 7 8 3 4
19 20 17 18 15 16
1 2 11 12 7 8 3 4
Disk Enclosure ID
DAEXXX indicates a disk enclosure ID. The first X indicates the controller enclosure
ID, the second X indicates the last digit of the loop ID, and the third X indicates the
number of disk enclosures connected in a loop.
NOTE
● For loops 1 to 15, the second X is 1, 2, ..., 8, 9, A, B, C, D, E, and F, and the third X ranges
from 0 to 7 (0 for the first disk enclosure, 1 for the second disk enclosure, and so on).
● For loops 16 to 20, the second X is 0, 1, 2, 3, and 4, and the third X is 8, 9, A, ..., and F (8
for the first disk enclosure, 9 for the second disk enclosure, and so on).
● For example, the ID of the first disk enclosure in loop 15 of controller enclosure 0 is
DAE0F0, and the ID of the first disk enclosure in loop 20 of controller enclosure 0 is
DAE048.
Table 7-8 describes the rules for naming disk enclosure IDs in each loop.
P1 4 DAE040 to DAE047
P2 5 DAE050 to DAE057
P3 6 DAE060 to DAE067
P1 8 DAE080 to DAE087
P2 9 DAE090 to DAE097
P3 10 DAE0A0 to DAE0A7
P1 12 DAE0C0 to DAE0C7
P2 13 DAE0D0 to DAE0D7
P3 14 DAE0E0 to DAE0E7
P1 16 DAE008 to DAE009,
DAE00A to DAE00F
P1 18 DAE028 to DAE029,
DAE02A to DAE02F
P1 20 DAE048 to DAE049,
DAE04A to DAE04F
Loop ID
Each port on an expansion module corresponds to a fixed loop ID, as shown in
orange and blue marks in Figure 7-7, Figure 7-8, and Figure 7-9.
NOTE
● SAS disk enclosures can connect to 12 Gbit/s SAS expansion modules in slots IOM H5/L5
to IOM H8/L8.
● Smart disk enclosures can connect to 100 Gbit/s RDMA expansion modules in slots IOM
H1/L1 to IOM H12/L12.
Figure 7-7 Scenario where 12 Gbit/s SAS expansion modules are installed
8 0 4 12
9 1 5 13
10 2 6 14
11 3 7 15
8 0 4 12
9 1 5 13
10 2 6 14
11 3 7 15
Figure 7-8 Scenario where 100 Gbit/s RDMA expansion modules are installed
16 12 20 8 4 0 2 6 10 22 14 18
17 13 21 9 5 1 3 7 11 23 15 19
16 12 20 8 4 0 2 6 10 22 14 18
17 13 21 9 5 1 3 7 11 23 15 19
Figure 7-9 Scenario where 12 Gbit/s SAS and 100 Gbit/s RDMA expansion
modules are intermixed
8 0 4 12
16 18
9 1 5 13
10 2 6 14
17 11 3 7 15 19
8 0 4 12 18
16
9 1 5 13
10 2 6 14
17 19
11 3 7 15
Disk Enclosure ID
DAEXXX indicates a disk enclosure ID. The first X indicates the controller enclosure
ID, the second X indicates the loop ID, and the third X indicates the number of disk
enclosures connected in a loop.
NOTE
● For loops 0 to 15, the second X is 0, 1, ..., 8, 9, A, B, C, D, E, and F, and the third X is 0 or
1 (0 for the first disk enclosure and 1 for the second disk enclosure in the loop).
● For loops 16 to 19, the second X can be 0, 1, 2, or 3, and the third X can be 8, 9, ... (8 for
the first disk enclosure and 9 for the second disk enclosure in the loop).
● For example, the ID of the first disk enclosure in loop 15 of controller enclosure 0 is
DAE0F0.
Table 7-9 describes the rules for naming disk enclosure IDs in each loop.
0 DAE000 to DAE007
1 DAE010 to DAE017
2 DAE020 to DAE027
3 DAE030 to DAE037
4 DAE040 to DAE047
5 DAE050 to DAE057
6 DAE060 to DAE067
7 DAE070 to DAE077
8 DAE080 to DAE087
9 DAE090 to DAE097
10 DAE0A0 to DAE0A7
11 DAE0B0 to DAE0B7
12 DAE0C0 to DAE0C7
13 DAE0D0 to DAE0D7
14 DAE0E0 to DAE0E7
15 DAE0F0 to DAE0F7
16 DAE008 to DAE00F
17 DAE018 to DAE01F
18 DAE028 to DAE02F
19 DAE038 to DAE03F
20 DAE048 to DAE04F
21 DAE058 to DAE05F
22 DAE068 to DAE06F
23 DAE078 to DAE07F
Function
The FR42612L cabinet complies with IEC 60297-1 and is an assembled cabinet for
ease of expansion. The distance between front and rear mounting bars in the
cabinet can be adjusted at a minimum unit of 25 mm. The FR42612L cabinet has
the following functions:
● Delivers space for accommodating components that can be interconnected.
● Provides castors to facilitate movement on a flat floor or a gradient that
slopes to less than or equal to 10 degrees.
● Protects components from dust.
● Prevents components from being damaged.
Appearance
The exterior of an FR42612L cabinet is in sand texture black. Figure 7-10 shows
the appearance of an FR42612L cabinet.
Physical Structure
The FR42612L cabinet consists of the racks, front door, rear door, side panels,
cover, and mounting bars. Figure 7-11 shows the structure of an FR42612L
cabinet.
ESD Jack
The FR42612L cabinet provides two ESD jacks. When installing or maintaining a
cabinet, wear an ESD wrist strap and insert the other end into an ESD jack, as
shown in Figure 7-12.
Technical Specifications
Table 7-10 lists the technical specifications of an FR42612L cabinet.
Parameter Value
Parameter Value
Power supply and An FR42612L cabinet supports two types of PDUs, namely,
power distribution single-phase 220 V 32 A PDU and three-phase 380 V 32 A
PDU. Each cabinet must be equipped with two PDUs of the
same type.
● When single-phase 220 V 32 A PDUs are used:
– Input: Two single-phase 32 A inputs must be provided
for each cabinet.
– Output: Each PDU provides twenty C13 outputs and
four C19 outputs.
NOTE
In single-phase power supply mode, the maximum power
consumption of all devices in a cabinet cannot exceed 6336 W.
● When three-phase 380 V 32 A PDUs are used:
– Input: Two three-phase 32 A inputs must be provided
for each cabinet.
– Output: Each PDU provides twenty-four C13 outputs
and three C19 outputs.
NOTE
● Operating temperature and humidity are measured 1.5 m above the floor and 0.4 m in
front of the device in the equipment room.
● Short-term operation means that the consecutive operating time does not exceed 48
hours, and the annual accumulative operating time does not exceed 15 days.
4 Altitude
5 Particle
Contami
nants
6 Corrosive
Airborne
Contami
nants
7 Vibration
and
Shock
12 Dust For the equipment room near dust sources (such as coal
preventio mines, country roads, or farmland), use double-layer
n aluminum alloy windows for proper sealing and an anti-
theft and fireproof door. Separate the devices from the
door with a partition board to avoid dust.
18 High
voltage
DC
19 DC
NOTICE
● When evaluating the power supply capability of a cabinet, consider the voltage
fluctuation range of the locality. Obtain the current fluctuation range allowed
by the external power supply according to its specifications, and then calculate
the actual power supply capability of the cabinet.
● When evaluating the power bearing capability of each PDU and PDU group,
consider the voltage fluctuation range of the locality. Obtain the current
fluctuation range allowed by each PDU and PDU group based on their
specifications, and then calculate the actual power bearing capability of each
PDU and PDU group.
● Connect the power cables of the storage devices to different PDU groups based
on the power consumption, so each PDU group bears similar power load,
preventing overload in any group.
Table 7-12 Check items for a third-party cabinet (for ordinary disk enclosure)
Ground Does the ground □Yes □No The total weight of the
bearing bearing capacity of cabinet and all devices,
of the the equipment room PDUs, and components in
equipm meet requirements? the cabinet does not exceed
ent the ground bearing capacity
room of the equipment room.
Cabinet Is the cabinet a 19-in. □Yes □No The size meets the
parame standard cabinet (in requirements shown in
ters compliance with the Figure 7-13.
IEC 60297 standards)?
Does the cabinet have □Yes □No Check whether the cabinet
adequate space for has adequate space for
installing the installing Huawei devices.
enclosure? Each controller enclosure
occupies 2 U or 4 U, and
each disk enclosure occupies
2 U or 4 U.
Does the power plug □Yes □No If the power plug of the
of the PDU face PDU faces toward the side,
toward the rear door? the FRU cannot be installed
properly.
Table 7-13 Check items for a third-party cabinet (for high-density enclosures)
Catego Check Item Condition Remarks
ry
Ground Does the ground □Yes □No The total weight of the
bearing bearing capacity of the cabinet and all devices,
of the equipment room meet PDUs, and components in
equipm requirements? the cabinet does not exceed
ent the ground bearing capacity
room of the equipment room. The
weight of a single high-
density disk enclosure is 100
kg in full configuration.
Cabinet Is the cabinet a 19-in. □Yes □No The size meets the
parame standard cabinet (in requirements shown in
ters compliance with the Figure 7-13.
IEC 60297 standards)?
Does the cabinet have □Yes □No Check whether the cabinet
adequate space for has adequate space
installing the depending on the product
enclosure? configuration.
Does the power plug □Yes □No If the power plug of the
of the PDU face PDU faces toward the side,
toward the rear door? the high-density disk
enclosure cannot be
installed.
NOTE
If a high-density disk enclosure is installed in the top 4 U space, disks cannot be inserted.
Figure 7-13 Mechanical structure and size requirements for IEC 60297 482.6 mm
(19 in.) series cabinet
Prerequisites
Both UltraPath and SmartKit meet the following requirements:
● UltraPath: 21.1.0 or later
● SmartKit: V2R5C00RC10 or later
Procedure
Step 1 Start SmartKit. Log in to SmartKit as a Huawei engineer or channel partner
engineer. Click the Storage tab. In the Site Deployment Delivery area, select
UltraPath Installation.
NOTE
Based on user permissions, SmartKit users are classified into Huawei engineers, channel
partner engineers, customers, and visitors.
Step 2 In the UltraPath installation wizard, select Check before UltraPath Installation.
Step 3 In the Installation Preparation dialog box that is displayed, complete the
following preparations as prompted:
1. Click download the UltraPath software package. On the support website,
download the corresponding UltraPath software package. In addition,
download the signature verification tool and verify the digital signature. If the
UltraPath software package has been obtained, skip this step.
2. Based on the application scenario, select the types of hosts where UltraPath
needs to be installed.
3. Manually complete a pre-installation check for all host types and select
Confirmed from the Operation drop-down box on the right.
4. Click Finish.
After the devices are added successfully, the tool displays the device information.
Click Next.
3. Click Finish. The configuration is complete and the main window is displayed.
NOTE
● After hosts are added, they are displayed in the main window. If any host is incorrectly
added, select it and click Remove Host to delete the host.
● After all the selected hosts have executed the installation policy, the system
automatically generates a report. To specify a report directory, click Set Directory.
● To modify an installation policy, click Modify in the Installation Policy column.
Step 8 Confirm the precautions in the dialog box that is displayed, select I have read the
previous information and understood consequences of the operation, and click
OK.
NOTE
The installation process consists of four steps. You can click each tab to view details
about the corresponding step.
1. UltraPath Software Package Import: This step automatically uploads the
software package to a host.
2. Pre-Install Check: This step checks that a host allows UltraPath to be installed on
it.
3. Install: This step installs the main program of the UltraPath software.
4. Post-Install Verification: This step checks, activates, and validates the UltraPath
software.
2. If some check items are not passed or need to be optimized, the system will
suspend the installation and Paused will be displayed in the Operation
column in the upper pane. You can click View Details to view the current
status. For a specific check item or operation item, click Details in the
Operation column in the lower pane to view information.
3. The system provides a check method, check criteria, and recovery suggestion.
If a check item fails, you can handle the problem according to the check
result.
NOTE
Each check item can be retried, ignored, or terminated according to the policy
requirements. If the current item does not support an operation, the corresponding
button is unavailable.
– Retry: After the fault is rectified, click Retry to check the current item again.
– Ignore: Ignore this item and proceed with subsequent operations if the current
check item or operation item can be ignored.
– Terminate: If you want to terminate the installation process, click this button. This
may cause UltraPath software exceptions on the host. Exercise caution when
performing this operation.
Step 10 After UltraPath has been installed on all the selected hosts, the system
automatically generates an installation report in Excel format. Click View Report
to view detailed information. Click Close to finish the installation.
NOTICE
Step 11 The main window is displayed, and the UltraPath software installation is complete.
----End
● Cut the corrugated pipe according to the required length during hardware
installation. Wrap tape around the sharp edge of the corrugated pipe to
protect the optical fibers.
● In an equipment room containing brackets and an ESD floor, optical fibers
shielded in the corrugated pipes can be routed through the ground interlayer
or the cable tray.
● Optical fibers can be routed through the cable tray installed on the top of the
cabinet.
● If the cable tray is more than 0.8 m above the cabinet top, set up a cable
ladder above the cabinet.
Cable Routing
● In an equipment room installed with supports and ESD floor, cables can go
through the interlayer (the space between the concrete floor and the ESD
floor) or the cable trough.
● If the cables are led out from the top of the cabinet, a cable tray should be
built over the cabinet. Use cable ties to fix the PDU cables in the cabinet, to
prevent PDU connectors loosening due to gravity of cables.
● The specifications, routing, section, and position for arranging the cables
should be designed beforehand. The cables should be lined up neatly, without
any damage on the cover.
● Signal cables, such as the alarm cables, network cables, and clock cables must
be routed separately from power cables.
● The cable should be turned smoothly at the bends, with the minimum bend
radius no less than three times the diameter of the cable.
● The insulation layer of the conducting wire must be intact.
● The cables should be routed in a way that facilitates future maintenance and
expansion.
Cable Binding
● Bind the cables when laying them on the passage. The cables should be
aligned snugly together. The spacing between the cable ties should be even
with a neat overall appearance.
● Cables run through the ducts do not need to be bound but should be
arranged neatly without crossover. The cable should not overflow the trough.
Bind or attach the cables with ties where they enter or exit the trough and at
turning points.
● The bundles should be tidy and their purpose clear. The bundles can be
classified by type. A large number of cables can be further classified by
column. Bind each group of cables with ties.
● Do not connect two or more cable ties to bind cables, because this may
decrease the strength of the binding.
● Bind the cables neatly and trim the excessive tie.
● The cable ties should be evenly spaced three to four times the diameter of the
cable bundle.
● Use as long a bend radius as possible to prevent internal cable stress and
breakage.
Figure 7-15 shows how to bind cables.
Evenly divide the cables connected to the storage device into two parts. Place the left part
of cables into the troughs of the left cable tray, and the right part in the troughs of the
right cable tray.
● The bending radius of optical fibers must be no less than 50 mm.
● Route optical fibers inside the cabinet along the posts on the sides of the
cabinet and attach them when necessary.
● Corrugated pipes are required when running optical fibers outside the cabinet,
and should be extended into the cabinet about 100 mm.
● When using corrugated pipes, optical fibers can be run through the cable
trough in an equipment room installed with supports and ESD floor, or the
interlayer (the space between the concrete floor and the ESD floor).
● If the optical fibers are led out from the top of the cabinet, a cable tray
should be installed over the cabinet for cabling. If the distance between the
cable tray and the cabinet top is longer than 0.8 m (31.50 in.), a cable ladder
should be used.
WARNING
Before bundling optical fibers, read the instructions and precautions carefully to
prevent man-made accidents.
c. Strain the optical fiber binding tape by the other end with the other
hand. Turn the fiber binding tape around the fiber bundle till the mat
side adheres to the hook side snugly, as shown in Figure 7-18.
● Expected result
The optical fibers are bundled successfully, as shown in Figure 7-19.
● Precautions
– When using a fiber binding tape, keep the mat side inside and the hook
side outside. It is only the mat side of the fiber binding tape that contacts
the optical fiber.
– Arrange the optical fibers tidily into a bundle before bundling.
– Bundle the optical fibers with appropriate force. Never bind them too
tight.
– The interval between two pieces of optical fiber binding tape should not
exceed 40 cm.
– A bundle can contain a maximum of 100 optical fibers (each with a
diameter of 2 mm) or 60 optical fibers (each with a diameter of 3 mm).
If more optical fibers need to be bundled, separate them into different
bundles.
Procedure
Step 1 Use the diagonal pliers to cut the cable according to the required length.
Step 2 Put the cable through the boot, and reserve at least 100 mm of the cable for
installing the connector. Ensure that the boot is installed in the correct direction,
as shown in Figure 7-21.
Step 3 Use a blade or knife to peel off 20 mm of the sheath, as shown in Figure 7-22. Do
not damage the insulation of the wires.
Step 4 Arrange the four pairs of wires according to the color codes followed by pins of
the RJ45 connector shown in Table 7-14. Figure 7-23 illustrates pins of the RJ45
connector (pay attention to the pin colors).
NOTE
In Table 7-14, end A and end B refer to both ends of a network cable.
5 White and blue White and blue White and blue White and blue
Step 5 Ensure that the wires are 13 to 15 mm long. Cut off the excess if the wires are
longer than required, arrange them in the correct order, and then insert them into
the RJ45 connector, as shown in Figure 7-24.
Step 6 Use the RJ45 crimping tool to crimp the connector. Ensure that the connector is
put in the right position in the RJ45 crimping tool. After crimping, the metal cover
on the connector must be lower than other area on the connector.
Step 7 Use a network cable tester or a multimeter to test all the wires and ensure that
they are connected properly.
Step 8 Push the boot to cover the RJ45 connector, as shown in Figure 7-25.
----End
Procedure
Step 1 Install the boot of the RJ45 connector.
1. Select a cable of proper length and install the boot on the RJ45 connector of
the cable, as shown in Figure 7-28.
2. Use a blade or knife to peel off 30 mm of the sheath and use a blade to slit
up to 5 mm on the sheath, as shown in Figure 7-29.
3. Install a shielded iron cover on the cable shield, and then insert the shielded
iron cover into the sheath along the crack. Install the shielded iron cover
correctly, as shown in Figure 7-30.
NOTICE
When peeling off the cable sheath, do not damage the cable shield or the
insulated wires.
1. Use the diagonal pliers to peel the cable shield, grounding wire, aluminum
foil, and polyester band off the first 20 mm of the cable, leaving only the
insulated conductors.
2. Arrange the four twisted pairs properly and insert them into the load bar, as
shown in Figure 7-31 and Figure 7-32. Maintain the original twist pitch of
the twisted pairs.
3. Arrange the pairs smoothly and straightly at the aperture of the load bar.
Arrange the wires properly and cut off the excess of the wires along the edge
of the wire fastening slot. Table 7-15 shows the wires order, and Figure 7-33
shows the pins of the RJ45 connector (pay attention to the colors of pins).
4. Install the plastic cover on the wire fastening slot, and then fasten the slot. To
ensure that the cover is fitted properly, push it into the slot until you hear a
click, as shown in Figure 7-34.
4. Insert the RJ45 connector into the boot, as shown in Figure 7-35.
----End
● Tools:
– Power cable crimping tool
– Hydraulic pliers
– Box cutter
– Diagonal pliers
– Wire clipper
– Heat gun
● Materials:
– Power cables
– Insulation tapes
– OT terminals
– Heat shrink tubes
Procedure
Step 1 Peel off a section of the insulation layer C from the power cable based on the
cross-sectional area of the power cable conductors. A section of power cable
conductor D with a length of L1 is exposed, as shown in Figure 7-36. Table 7-16
lists the recommended lengths of the insulation layer to be peeled off (L1).
Figure 7-36 Peeling off the insulation layer of the power cable
NOTICE
● When peeling off the insulation layer of the power cable, take care not to
scratch the conductor of the power cable.
● You can adjust L1 according to the length of the OT terminal. L1 = L + (1 to 2)
mm.
Table 7-16 Mappings between the cross-sectional area and the length of the
insulation layer to be peeled off (L1)
1 7
1.5 7
2.5 7
4 8
6 9
10 11
16 13
25 14
35 16
50 16
NOTE
Engineers can determine the length of insulation layer to be peeled off by comparing the
cable with the connector to be crimped.
Step 2 Insert the power cable into the heat shrink tube A, as shown in Figure 7-37.
Step 3 Insert the bare conductor of the power cable into the OT terminal B, and then
press the OT terminal close to the insulation layer C, as shown in Figure 7-37.
NOTICE
After the OT terminal is installed, the length of the bare conductor outside the OT
terminal (L2) cannot be larger than 2 mm. If L2 is larger than 2 mm, cut the
excess by using the diagonal pliers or wire clipper, as shown in Figure 7-37.
Step 4 Use the power cable crimping tool to clamp the tail of the OT terminal and the
contact part of the conductor, as shown in Figure 7-38.
Figure 7-38 Clamping the tail of the OT terminal with the contact part of the
conductor
NOTE
Step 5 Push the heat shrink tube A toward the OT terminal, and cover the crimping area
of the OT terminal and the conductor. Use a heat gun to heat the heat shrink
tube, as shown in Figure 7-39.
NOTICE
Stop heating the heat shrink tube once the cable is wrapped by it tightly. Excessive
heat may damage the insulation layer of the cable.
----End
Labels are affixed to the cables to identify the physical positions of the cables on
different devices. There are two types of cable labels: labels for the power cables
and labels for the signal cables.
NOTE
If otherwise required by the customer, fill in and arrange labels in such a way that helps
maintain label consistency in the same equipment room.
Material Specification
The material features of the labels are as follows:
● Thickness: 0.09 mm.
● Color: chalk white.
● Material: Polyester (PET).
● Allowable temperature: -29°C to +149°C.
● The labels can be printed on by a laser printer or written with an oil marker.
● The material must pass the authentication of Underwriters Laboratories (UL)
and Canadian Standards Association (CSA).
Types
There are two types of cable labels: one is for power cables and the other is for
signal cables.
The dividing lines on the label make the position of a cable clearer. For example,
there is a dividing line between the cabinet number and the enclosure number,
and another between the enclosure number and the slot number. The size of the
dividing line is 1.5 mm x 0.6 mm, and its color is PANTONE 656c (light blue).
The dotted lines mark the position for folding the label when you attach it to the
cable.
There is a mark "TO:" (upside down in the figure) at the lower right corner of the
label. Write information about the peer end of the cable, to which the label is
affixed after the mark.
Contents on Labels
The contents on a label for a signal cable are different from the contents on a
label for a power cable.
If the label is viewed from the cable leading-out area, it appears on the right side
of the cable. The side with "TO:" that faces outward indicates the location of one
end of the cable; the other side indicates the location of the other end.
● When you print or write information on the labels or attach the labels, ensure
that the labels are clean.
● Do not use ink-jet printers or ink pens to print or write on the labels because
the label paper is made up of moisture-proof and waterproof material.
● Affix labels neatly. The new label is of striped type. The appearance of the
product is affected if the affixing position is incorrect.
● Bundle the cable ties at the same height, and place all identification plates in
the same direction.
● The positions of "up", "down", "right", and "left" in this section (excluding the
description of printer setting) are from the perspective of facing the labels.
Writing Tool
To keep the labels legible and neat, use a black oil marker to fill in the labels. An
oil marker is more effective than a ballpoint pen. When you use a marker to fill in
the labels, ensure that the surface of the labels is not oily. Oil can smudge the
letters.
NOTE
The delivered marker has two nibs. Use the smaller nib to fill in the labels.
Writing Font
The handwritten font must be similar to the standard typeface "Times New
Roman" so that it is clear and legible. Table 7-17 lists the standard typeface.
0 1 2 3 4 5 6 7 8
9 A B C D E F G H
I J K L M N O P Q
R S T U V W X Y Z
The typeface for handwriting should be of a proper size, identifiable, and neat.
NOTE
If the customers require label consistency in their equipment rooms, fill in and arrange the
labels according to requirements.
This section describes how to attach a label for a signal cable and a power cable.
A label should be affixed to each end of a cable. When the cable is placed
vertically, the label should point rightwards, and when the cable is placed
horizontally, the label should point downwards. Figure 7-44 shows how to
properly attach a label to the signal cable.
Cable ties should be fastened at both ends of a cable. After bundling the cables,
the completed identification plate should be visible on the top of the cable in the
horizontal cabling, or on the right side of the cable in the vertical cabling. Make
sure that the label points outwards, as shown in Figure 7-46.
NOTE
Structure
Figure 7-47 shows the structure of the fiber extractor.
NOTICE
Precautions
● Replacing an optical fiber, network cable, optical module, or electrical module
will interrupt services.
● Wear ESD gloves or an ESD wrist strap when using a fiber extractor to replace
the optical fiber, network cable, optical module, or electrical module.
● Do not exert too much force when using the fiber extractor to prevent
damage to the optical fiber, network cable, optical module, or electrical
module.
Figure 7-49 Clamping method for removing the optical fiber pre-
equipped with an optical attenuator
Align the fiber extractor with the fiber connector. Clamp the fiber
connector with proper force as shown in Figure 7-49, and then pull the
fiber outwards as shown in Figure 7-50.
● Use a fiber extractor to install the optical fiber pre-equipped with an optical
attenuator.
a. Acquire the clamping method of the fiber extractor.
Figure 7-51 shows the clamping method of the fiber extractor when the
fiber extractor is used to install an LC fiber pre-equipped with an optical
attenuator.
Figure 7-51 Clamping method for installing the optical fiber pre-
equipped with an optical attenuator
Figure 7-52 Clamping method for removing the optical fiber not
equipped with an optical attenuator
Figure 7-53 Removing the optical fiber not equipped with an optical
attenuator
● Use a fiber extractor to install the optical fiber not equipped with an optical
attenuator.
a. Acquire the clamping method of the fiber extractor.
Figure 7-54 shows the clamping method of the fiber extractor when the
fiber extractor is used to install an LC fiber not equipped with an optical
attenuator.
Figure 7-54 Clamping method for installing the optical fiber not
equipped with an optical attenuator
NOTICE
NOTICE
B Glossary
A
AC Alternating Current
AD Active Directory
AES Advanced Encryption Standard
ANSI American National Standards Institute
ASHRAE American Society of Heating, Refrigerating and Air-Conditioning
Engineers
ASP Application Service Provider
B
BMC Baseboard Management Controller
C
CLI Command Line Interface
CSA Canadian Standards Association
D
DC Direct Current
3DES Triple Data Encryption Standard
DES Data Encryption Standard
DLC Double Lucent Connector
DNS Domain Name Server
E
ESD Electrostatic Discharge
F
FC Fibre Channel
FC-AL Fibre Channel Arbitrated Loop
FCoE Fibre Channel over Ethernet
FRU Field Replaceable Unit
FTP File Transfer Protocol
G
GE Gigabit Ethernet
GTS Global Technical Service
GSM Global System for Mobile Communications
H
HBA Host Bus Adapter
HD High Density
I
IEC International Electrotechnical Commission
IP Internet Protocol
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISA Instrument Society of America
ISO International Organization for Standardization
L
LDAP Lightweight Directory Access Protocol
LUN Logical Unit Number
M
MD5 Message Digest Algorithm 5
MIB Management Information Base
MPO Multiple-fiber Push-on/Pull-off
MGMT Management
N
NDMP Network Data Management Protocol
NEG Negative
NIS Network Integration Service
NL-SAS Near Line Serial Attached SCSI
NTP Network Time Protocol
O
ODF Optical Distribution Frame
OID Object Identifier
OTDR Optical Time Domain Reflectometer
P
PDU Power Distribution Unit
PO Purchase Order
PPB Part Per Billion
PSTN Public Switched Telephone Network
R
RoHS Restriction of the use of certain Hazardous Substances
RH Relative Humidity
RTN Return Current
S
SAN Storage Area Network
SAS Serial Attached SCSI
SFP Small Form-factor Pluggable
SFTP Secure File Transfer Protocol
SHA Secure Hash Algorithm
SMTP Simple Mail Transfer Protocol
SMS Short Messaging Service
STP Shielded Twisted Pair
SSD Solid State Disk
SSH Secure Shell
T
TC Technical Committee
TLS Transport Layer Security
U
UDP User Datagram Protocol
UL Underwriters Laboratory
UTP Unshielded Twisted Pair
USM User-based Security Model
V
VLAN Virtual Local Area Network