HCIP-Storage V5.0 Lab Guide

Huawei Storage Certification Training
HCIP-Storage
Scenario-based Practice of
Flash Storage Fundamentals
(For Trainees)
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of
their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made
between Huawei and the customer. All or part of the products, services and features
described in this document may not be within the purchase scope or the usage scope.
Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has
been made in the preparation of this document to ensure accuracy of the contents, but
all statements, information, and recommendations in this document do not constitute
a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base, Bantian, Longgang, Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.
HCIP-Storage Scenario-based Practice of Flash Storage Fundamentals Page 1
Huawei Certification System

Huawei Certification follows the "platform + ecosystem" development strategy,
which is a new collaborative architecture of ICT infrastructure based on
"Cloud-Pipe-Terminal". Huawei has set up a complete certification system comprising
three categories: ICT infrastructure, Platform and Service, and ICT vertical. Huawei's
technical certification system is the only one in the industry covering all of these fields.
Huawei offers three levels of certification: Huawei Certified ICT Associate (HCIA),
Huawei Certified ICT Professional (HCIP), and Huawei Certified ICT Expert (HCIE).
Huawei Certified ICT Professional-Storage (HCIP-Storage) is designed for Huawei
engineers, students and ICT industry personnel. HCIP-Storage covers storage system
introduction, flash storage technology and application, distributed storage technology
and application, storage design and implementation, and storage maintenance and
troubleshooting.
The HCIP-Storage certificate introduces you to the storage industry and markets,
helps you understand sector innovation, and makes sure you stand out among your
industry peers.


Contents
1 References and Tools ..........................................................................................................4

1.1 References.......................................................................................................................................................................... 4
1.2 Software Tools .................................................................................................................................................................. 4
1.3 Operating Environment ................................................................................................................................................. 4
2 Scenario-based Practice of Flash Storage Fundamentals ............................................5
2.1 Course Overview .............................................................................................................................................................. 5
2.2 Objectives........................................................................................................................................................................... 5
2.3 Case Background ............................................................................................................................................................. 5
2.4 Tasks and Suggested Answers ..................................................................................................................................... 6
2.4.1 Scenario 1: Multipathing Operations ...................................................................................................................... 6
2.4.1.1 Background ................................................................................................................................................................. 6
2.4.1.2 Question ...................................................................................................................................................................... 6
2.4.1.3 Task 1: Configuring UltraPath ............................................................................................................................... 6
2.4.1.4 Question ...................................................................................................................................................................... 8
2.4.1.5 Task 2: Managing UltraPath .................................................................................................................................. 8
2.4.1.6 Question .................................................................................................................................................................... 10
2.4.2 Scenario 2: Basic NAS Configuration .................................................................................................................... 10
2.4.2.1 Background ............................................................................................................................................................... 10
2.4.2.2 Question .................................................................................................................................................................... 10
2.4.2.3 Task 1: Initial Configuration ................................................................................................................................. 10
2.4.2.4 Question .................................................................................................................................................................... 11
2.4.2.5 Task 2: Configuring Basic Storage Services ...................................................................................................... 11
2.4.2.6 Question .................................................................................................................................................................... 13
2.4.2.7 Task 3: Configuring an NFS Share ...................................................................................................................... 13
2.4.2.8 Question .................................................................................................................................................................... 14
2.4.2.9 Task 4: Configuring a CIFS Share........................................................................................................................ 15
2.4.2.10 Question .................................................................................................................................................................. 16
2.5 Summary and Conclusion............................................................................................................................................ 17

1 References and Tools
1.1 References
The commands, documents, and document paths listed in this document are for reference
only. The actual commands, documents, and document paths may vary.
Huawei OceanStor Dorado V6 Product Documentation
Note:
The specifications of features vary by product. For details, see the product documentation
of the desired product model. You can log in to Huawei's technical support website
(https://support.huawei.com/enterprise/) and use the search box to find and download the
desired document or tool.
1.2 Software Tools

PuTTY
Note:
You are advised to use the open-source software PuTTY to log in to a terminal. You can
visit its public website (putty.org) to find and download the desired document or tool.
1.3 Operating Environment

Name Version Quantity Remarks
Storage system Huawei OceanStor Dorado V6 2
Windows Server 2012 or

Windows OS - Recommended version
Windows Server 2016

2 Scenario-based Practice of Flash

Storage Fundamentals
2.1 Course Overview

This course provides case study and scenario-based practices to help trainees consolidate
their knowledge of Huawei OceanStor storage and equip them with the capabilities of
using Huawei UltraPath, basic NAS configuration, and SmartQuota application.
2.2 Objectives
 To understand the functions of UltraPath
 To be able to install and use UltraPath
 To be able to configure basic NAS services
 To apply the SmartQuota feature
2.3 Case Background

Note:
Cases in this document are examples only. The actual configurations may vary according to
actual environments. For details, see the corresponding product documentation. The
names in this document can be customized (for example, LUN_XXX) for different trainees if
they use the same device.
A company is deploying a storage system to provide block and file services. The company
uses Huawei OceanStor all-flash storage devices that adopt the redundancy design to meet
the high reliability and performance requirements of the storage network. UltraPath is
used to provide multipathing management functions, meeting basic failover and load
balancing requirements. SmartQuota is used to flexibly configure resource management
and control policies.
Help the storage engineer of the company to install and configure UltraPath, set basic NAS
services, and configure SmartQuota.

2.4 Tasks and Suggested Answers

2.4.1 Scenario 1: Multipathing Operations
2.4.1.1 Background
The company wants to install UltraPath to implement multipathing management on the
storage system. The storage engineer needs to install UltraPath on a Windows host in the
NAS scenario, view the device information related to UltraPath, process alarms, and
monitor the I/O performance of each path in real time.
In normal cases, UltraPath selects the optimal path for data transmission. If the optimal
path is down, data is transmitted over a secondary path. After the optimal path recovers, it
takes over data transmission again.
2.4.1.2 Question
What are the functions of Huawei UltraPath?
2.4.1.3 Task 1: Configuring UltraPath

Install OceanStor UltraPath on a Windows host.
Before installing and using UltraPath, learn about the installation precautions and
configuration process. This helps you correctly install, configure, and use UltraPath.
Step 1 Streamline the process.

Streamline and draw the flowchart for configuring UltraPath.
[Suggested Procedure]
For details, see section "Installing UltraPath for Windows" in the OceanStor UltraPath for
Windows User Guide.
Step 2 Prepare for the installation.

To smoothly install UltraPath, you need to obtain the hardware and software packages in
advance and prepare or plan the data required for the installation.
1. Check the UltraPath software packages.

For details, see section "Preparing Software Packages and Data" in the OceanStor
UltraPath for Windows User Guide.
Note:
Due to constant software upgrades, the actual version of UltraPath may differ from that in
the document. In this case, use the actual version.
2. Check the application server data that you need to prepare for installing UltraPath.
For details, see section "Preparing Software Packages and Data" in the OceanStor
3. Check the installation environment.
Before installing UltraPath, check the hardware and software of the application server and
storage system to ensure that the requirements for installing and running UltraPath are
met.
For details, see section "Preparing the Installation Environment" in the OceanStor
Note:
The requirements of UltraPath on the operating system may vary with the version upgrade.
For details, log in to the Huawei technical support website
(https://support.huawei.com/enterprise for enterprises; https://support.huawei.com for
carriers), enter UltraPath in the search box, select the path that is automatically displayed,
and go to the UltraPath documentation page to search for, browse, and download the
Release Notes of the corresponding version.
Step 3 Install and configure UltraPath.

Upload the UltraPath software package to the application server and install UltraPath.

For details, see section "Installing UltraPath for Windows" in the OceanStor UltraPath for
Windows User Guide.
Note:
In this practice, you need to download the UltraPath software package from the FTP server.
The installation path of UltraPath for Windows may vary with the software version.
Step 4 Verify the installation.

Check whether UltraPath for Windows has been successfully installed.
Check whether you can access UltraPath Console and then check whether UltraPath takes
effect.
For details, see "Follow-up Procedure" in section "Silent Installation" or "Non-Silent
Installation" in the OceanStor UltraPath for Windows User Guide.
Note:
To maintain normal operation of UltraPath for Windows, do not move, modify, or delete
any files in the UltraPath installation directory in the system disk.
If Checking environment and config in the command output does not pass the check, check
whether UltraPath is installed as instructed in "Installing UltraPath for Windows". If the
check still fails, UltraPath does not take effect or the environment is abnormal.
2.4.1.4 Question
Can I log in to an application server as a visitor to install UltraPath?
2.4.1.5 Task 2: Managing UltraPath

After UltraPath is installed, you can maintain, upgrade, or uninstall it based on service
running conditions.
Step 1 View array information.

View details about disk arrays on the array management page of UltraPath for Windows.

For details, see section "Management > Route Maintenance > Viewing Array Information"
in the OceanStor UltraPath for Windows User Guide.
Step 2 View physical path information.

View the detailed information about a physical path.
For details, see section "Management > Route Maintenance > Viewing Physical Path
Information" in the OceanStor UltraPath for Windows User Guide.
Step 3 Manage critical events.

View critical events and save selected critical events on a local disk.
For details, see section "Management > Route Maintenance > Critical Event Management"
in the OceanStor UltraPath for Windows User Guide.
Step 4 (Optional) Upgrade or uninstall UltraPath.

1. Upgrade UltraPath to the latest version to obtain the latest UltraPath functions.
For details about how to upgrade UltraPath, see the UltraPath Upgrade Guide. Log in to
the Huawei technical support website (https://support.huawei.com/enterprise for
enterprises; https://support.huawei.com for carriers), enter UltraPath in the search box,
select the path that is automatically displayed, and go to the UltraPath documentation
page to search for, browse, and download the Upgrade Guide of the corresponding version.
2. Uninstall UltraPath if it is no longer required due to service adjustment.

For details, see section "Management > Uninstalling UltraPath for Windows" in the
OceanStor UltraPath for Windows User Guide.
2.4.1.6 Question
How can I install Huawei UltraPath on a Linux host?
2.4.2 Scenario 2: Basic NAS Configuration

2.4.2.1 Background
Complete basic NAS services for flash storage systems according to the plan.
2.4.2.2 Question
When configuring a storage pool, set hot spare policy to Low (1 disk). What does "1 disk"
mean?
2.4.2.3 Task 1: Initial Configuration

Step 1 Start the initial configuration wizard.
After logging in to DeviceManager, perform initial configuration on the storage system in
the initial configuration wizard. You can configure basic information and create storage
pools. You do not need to scan for UltraPath hosts or allocate storage resources.
Note:
To access the initial configuration wizard, enter https://XXX.XXX.XXX.XXX:8088/initialize in
the web browser on your maintenance terminal. In this address, XXX.XXX.XXX.XXX indicates
the IP address of the management network port of the storage system. This address is for
reference only, and may vary with the experiment environment.
Basic Information Example
Name Storage001
Location Hangzhou
Device Time 2020-07-24 10:22:59 UTC+08:00 (Beijing,

Asia)
Name, Capacity Alarm Threshold (%), and

StoragePool001, 80%, and 90%
Capacity Used Up Alarm Threshold (%)
For details, see section "Install and Initialize > Initialization Guide > Logging In and Starting
Initialization > Initially Configuring a Storage Device" in the product documentation.
Note:
A license file is a credential for using basic or value-added storage features. Before
configuring basic NAS services, check whether the obtained license file is valid.
In this practice, you do not need to import the license as the license file has been imported
and activated. You can manage the license in the initial configuration wizard.
2.4.2.4 Question
Draw the flowchart for configuring a file system.
2.4.2.5 Task 2: Configuring Basic Storage Services

Log in to DeviceManager and configure basic NAS storage services based on the plan.
Create file systems and then configure shares.
Step 1 Perform check before configuration.

Before configuring basic storage services, check whether the initial configuration meets the
requirements.

For details, see section "Configure > Basic Storage Service Configuration Guide for File >
Configuring Basic Storage Services > Check Before Configuration" in the product
documentation.
Step 2 Log in to DeviceManager and create a storage pool.

Log in to DeviceManager and create storage pools for application servers to use the
storage space provided by a storage system.
Configuring Basic Storage Services > Creating a Storage Pool" in the product
documentation.
Step 3 Create a file system.

Create a file system to share storage resources in the form of files or directories.
Configuring Basic Storage Services > Creating a File System" in the product documentation.
Step 4 (Optional) Create a dtree.

You can create a dtree after a file system is created.
Configuring Basic Storage Services > (Optional) Creating a Dtree" in the product
documentation.
Step 5 Create a quota.

Create a quota to control and collect statistics of the space usage or file quantity of one or
all dtrees in a file system or of a single user or user group.
Configuring Basic Storage Services > (Optional) Creating a Quota" in the product
documentation.
2.4.2.6 Question
Draw the flowchart for configuring an NFS share.
Configuring Basic Storage Services > Sharing File Systems > Configuring an NFS Share >
Configuration Process" in the product documentation.
2.4.2.7 Task 3: Configuring an NFS Share

Users can access a file system only after the file system is shared. Configure an NFS share
and assign different access permissions to different clients based on the plan.
Step 1 Configure the network.

Before configuring shared services, plan and configure a network properly for accessing
and managing file services.
Create a logical port for accessing file services.
Configuring a Network" in the product documentation.
Step 2 Create an NFS share.

Create an NFS share for the SUSE client to access the file system.
Creating an NFS Share" in the product documentation.
Step 3 Add an NFS share client.

Add an NFS share client so that the client can access the shared file system through the
network.
Adding an NFS Share Client" in the product documentation.
Step 4 Access an NFS share.

Log in to a client and use the client to access an NFS share.
Accessing an NFS Share" in the product documentation.
2.4.2.8 Question
Draw the flowchart for configuring a CIFS share.

Configuring Basic Storage Services > Sharing File Systems > Configuring a CIFS Share >
Configuration Process" in the product documentation.
2.4.2.9 Task 4: Configuring a CIFS Share

Configure a CIFS share based on the plan, so that users can access the shared directory for
which they have the access permission.
Step 1 Configure a network.

Before configuring shared services, plan and configure a network properly for accessing
and managing file services.
Create a logical port for accessing file services.
Configuring a Network" in the product documentation.
Step 2 Create a local authentication user.

Create a local authentication user for accessing shares.
Configuring a Local Authentication User (Group)" in the product documentation.
Step 3 Add a storage system to an AD domain.

Connect a storage system to a DNS server and configure AD domain authentication
parameters.

For details, see section " Configure > Basic Storage Service Configuration Guide for File >
Adding a Storage System to an AD Domain" in the product documentation.
Step 4 Create a CIFS share.

Create a CIFS share for users to access the shared storage space.
Creating a CIFS Share" in the product documentation.
Step 5 Access a CIFS share.

Log in to the Windows client and access the CIFS share.
Accessing a CIFS Share" in the product documentation.
2.4.2.10 Question
What is the difference between a logical port and an Ethernet port? What is the basis for
creating a logical port?

2.5 Summary and Conclusion

My Opinion：
_________________________________________________________________________________________
_________________________________________________________________________________________
__________________________________________________________________

Scenario-based Practice of Flash Storage
Fundamentals
Background
 A company is deploying a storage system to provide block and file services. The
company uses Huawei OceanStor all-flash storage devices that adopt the
redundancy design to meet the high reliability and performance requirements
of the storage network. UltraPath is used to provide multipathing management
functions, meeting basic failover and load balancing requirements. SmartQuota
is used to flexibly configure resource management and control policies.
 Help the storage engineer of the company to install and configure UltraPath,
set basic NAS services, and configure SmartQuota.
1 Huawei Confidential
Practice Mode
Objectives Form
• To be able to plan and design typical • Trainees split into groups of two or three.
networks. • Each group prepares materials for
• To be able to install and configure presentation.
Huawei OceanStor UltraPath. • After each presentation, the technical
• To be able to configure NAS services on officer asks questions, and the evaluator
OceanStor Dorado all-flash devices. gives feedback and scores.
Opinion
Sharing
Procedure Assessment Criteria
• Topic introduction • Accuracy
• Case study • Completeness
• Scenario-based practice • Presentation
• Presentation • Time control
• Evaluation and feedback
Scenario 1: Multipathing Operations
Task 1 Task 2
Configuring Managing
UltraPath UltraPath
Question
 What are the functions of Huawei UltraPath?
 Suggested answer:
 Eliminating single points of failure (SPOFs)
 Load balancing
 Failover and fault recovery
Task 1: Configuring UltraPath
 Install OceanStor UltraPath on a Windows host.
 Streamline the process.
 Prepare for the installation. (Check the UltraPath software package and data on the
application server.)
 Install and configure UltraPath.
 Verify the installation.
Question
 Can I log in to an application server as a visitor to install UltraPath?
 No. Before installing UltraPath for Windows, use an administrator account to log in
to the application server where UltraPath for Windows is to be installed.
Task 2: Managing UltraPath
 After UltraPath is installed, you can maintain, upgrade, or uninstall it based on
service running conditions.
 View array information.
 View physical path information.
 Manage critical events.
 Upgrade or uninstall UltraPath.
Question
 How can I install Huawei UltraPath on a Linux host?
 For details, see the OceanStor UltraPath for Linux User Guide.
Scenario 2: Basic NAS Configuration
Task 1 Task 2 Task 3 Task 4
Initial Configuring basic Configuring an Configuring a

configuration storage services NFS share CIFS share
Question
 When configuring a storage pool, set hot spare policy to Low (1 disk). What
does "1 disk" mean?
 Hot spare capacity is provided by all member disks in each storage pool because the
storage system uses RAID 2.0+ virtualization technology. For ease of understanding,
the hot spare capacity is expressed in the number of hot spare disks on
DeviceManager.
Task 1: Initial Configuration
 After logging in to DeviceManager, perform initial configuration on the storage
system in the initial configuration wizard. You can configure basic information
and create storage pools. You do not need to scan for UltraPath hosts or
allocate storage resources.
Question
 Draw the flowchart for configuring a file system.
Task 2: Configuring Basic Storage Services
 Log in to DeviceManager and configure basic NAS storage services based on the
plan. Create file systems and then configure shares.
 Perform check before configuration.
 Log in to DeviceManager and create a storage pool.
 Create a file system.
 (Optional) Create a dtree.
 Create a quota.
Question
 Draw the flowchart for configuring an NFS share.
Task 3: Configuring an NFS Share
 Configure an NFS share and assign different access permissions to different
clients based on the plan.
 Configure the network.
 Create an NFS share.
 Add an NFS share client.
 Access the NFS share.
Question
 Draw the flowchart for configuring a CIFS share.
Task 4: Configuring a CIFS Share
 Configure a CIFS share based on the plan, so that users can access the shared
directory for which they have the access permission.
 Configure a network.
 Create a local authentication user.
 Add a storage system to an AD domain.
 Create a CIFS share.
 Access the CIFS share.
Question
 What is the difference between a logical port and an Ethernet port? What is the
basis for creating a logical port?
 An Ethernet port is physically visible on a device. An Ethernet port is the basis for
creating a logical port.
 Logical ports are created on Ethernet ports, bound ports, or VLANs for running NAS
services.
Trainee Assessment
Item Description Score Rating
Accuracy The trainee's explanation is logical and fluent. 1 to 10
The answers presented by the trainee are

Completeness 1 to 20
complete.
Presentation The trainee presents answers clearly. 1 to 10
The trainee provides the correct answers within

Time control 1 to 10
the specified time.
Overall /
Thank you. 把数字世界带入每个人、每个家庭、
每个组织，构建万物互联的智能世界。
Bring digital to every person, home, and
organization for a fully connected,
intelligent world.
Copyright©2020 Huawei Technologies Co., Ltd.

All Rights Reserved.
The information in this document may contain predictive

statements including, without limitation, statements regarding
the future financial and operating results, future product
portfolio, new technology, etc. There are a number of factors that
could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements.
Therefore, such information is provided for reference purpose
only and constitutes neither an offer nor an acceptance. Huawei
may change the information at any time without notice.
HCIP-Storage
HyperMetro Disaster
Recovery
(For Trainees)

Notice


HCIP-Storage Scenario-based Practice of HyperMetro Disaster Recovery Page 1

troubleshooting.
industry peers.


Contents
1 References and Tools .......................................................................................................... 4

1.1 References...........................................................................................................................................................................4
1.2 Software Tools ...................................................................................................................................................................4
1.3 Operating Environment ..................................................................................................................................................5
2 Scenario-based Practice of HyperMetro Disaster Recovery ......................................... 6
2.1 Course Overview ...............................................................................................................................................................6
2.2 Objectives............................................................................................................................................................................6
2.3 Case Background ..............................................................................................................................................................6
2.4 Tasks and Suggested Answers ......................................................................................................................................7
2.4.1 Scenario 1: HyperMetro Configuration....................................................................................................................7
2.4.2 Scenario 2: HyperMetro Management and O&M ............................................................................................. 11
3 Teaching Guidance ................................................................................. 错误!未定义书签。

3.1 Training Procedure .......................................................................................................................... 错误!未定义书签。
3.2 Grouping ............................................................................................................................................ 错误!未定义书签。
3.3 Auxiliary Materials and Tools ....................................................................................................... 错误!未定义书签。
3.4 Trainee Assessment......................................................................................................................... 错误!未定义书签。
3.5 Assessment Form ............................................................................................................................. 错误!未定义书签。

1.1 References
Note:
The specifications of HyperMetro vary by product. For details, see the product
documentation of the desired product model. You can log in to Huawei's technical support
website (https://support.huawei.com/enterprise/) and use the search box to find and
download the desired document or tool.
1.2 Software Tools

1. Huawei OceanStor UltraPath
Note:
You can log in to Huawei's technical support website
(https://support.huawei.com/enterprise/) and enter UltraPath in the search box to find and
2. PuTTY
Note:
You are advised to use the open-source software PuTTY to log in to a terminal. You can visit
its public website (putty.org) to find and download the desired document or tool.
3. Huawei quorum server
Note:
(https://support.huawei.com/enterprise/) and enter Dorado in the search box to find and


Recommended
Storage system Huawei OceanStor Dorado V6 6.0.1 2
version
Windows Server 2012 or Windows Recommended

Windows OS --
Server 2016 version
Recommended
Linux OS SUSE, Red Hat, CentOS, or EulerOS --
version
S5700 switch -- 1
Multipathing Recommended
UltraPath 21.6.3 --
software version
Quorum server Recommended

Dorado_V6_6.0.1_QuorumServer --
software version

2 Scenario-based Practice of HyperMetro

Disaster Recovery
2.1 Course Overview

their knowledge on the use of HyperMetro. HyperMetro is a common advanced storage
technology. Before using HyperMetro, you are advised to learn how to configure basic
storage services.
2.2 Objectives
 To be able to set up the HyperMetro application scenarios
 To be able to complete the configuration of HyperMetro
 To be able to perform the management and O&M of HyperMetro
2.3 Case Background

Note:
names of storage pools and LUNs involved in this document can be customized (for
example, LUN_XXX) for different trainees if they use the same device.
An enterprise has purchased two sets of Huawei OceanStor all-flash storage devices and
plans to protect data using LUN HyperMetro to ensure high service reliability. Therefore,
the enterprise has purchased the HyperMetro license. As a storage engineer, you need to
help the company complete the configuration of the HyperMetro feature.
The following figure shows the network topology of the enterprise's storage system.

Figure 2-1 Network topology of the enterprise's storage system

2.4.1 Scenario 1: HyperMetro Configuration
2.4.1.1 Background
Storage engineers have created data LUNs, installed the multipathing software on the host,
and mapped the LUNs to the service host in iSCSI mode. The reference configurations are
as follows:
Storage Mounting LUN

Application LUN Name Remarks
Name Method Capacity
Storage Data
Lun_001 iSCSI 3 GB HyperMetro
device 01 services
Storage Data
Lun_001 iSCSI 3 GB HyperMetro
device 02 services
2.4.1.2 Question
What are the main types of Huawei storage HyperMetro architecture?

2.4.1.3 Task 1: Preparing the Test Environment

Before configuring the HyperMetro feature, you need to check the test environment to
ensure that the network is connected, and install the multipathing software and the
quorum server software.
Step 1 Check the test environment before configuration.
Before configuring HyperMetro, you need to check related functions in the current test
environment.
For details, see Documentation (of your product) > Configuration & Commissioning >
Feature Guide > HyperMetro Feature Guide (specific to your product model and version) >
Check Before Delivery.
Step 2 Install the multipathing software.
To ensure that link aggregation can be performed when HyperMetro LUNs are mapped to
a host, install the multipathing software on the host before configuring HyperMetro.
Configuring Multipathing Software > Installing Multipathing Software > Installing
UltraPath.
Step 3 Install and configure the quorum server software.
After installing the multipathing software, you also need to install and configure the
quorum server software on the quorum server.

Configuring the Quorum Network > Installing Quorum Server Software > Installing
Quorum Server Software on a Huawei Dedicated Quorum Server.
Configuring the Quorum Network > Configuring Quorum Server Software > Huawei
Dedicated Quorum Server.
2.4.1.4 Question
What are the differences between the static priority mode and the quorum server mode?
2.4.1.5 Task 2: Configuring HyperMetro

After preparing the environment, you can start to configure HyperMetro.
Step 1 Check the configuration process.
The following figure shows the configuration process of the HyperMetro feature.
The reference process is as follows: Check the license file > Add a remote device > Create a
quorum server > Create a HyperMetro domain > Create a HyperMetro pair or HyperMetro
consistency group.
Step 2 Add a remote device.
This section describes how to establish a logical connection between a local storage system
and a remote storage system for data transmission.
1. Create a remote user on storage 01 and storage 02.
2. Create logical ports on storage 01 and storage 02.

3. (Optional) Configure routes.

4. Add a remote device.
Configuring HyperMetro > Adding a Remote Device.
Step 3 Create a HyperMetro domain.
This section describes how to create a HyperMetro domain, which defines the relationships
among the local and remote devices as well as the quorum server.
1. Select the quorum server mode and create a HyperMetro domain.
2. Configure the quorum server.
Configuring HyperMetro > Creating a HyperMetro Domain.
Step 4 Create a HyperMetro pair and a HyperMetro consistency group.

This operation enables you to set up a HyperMetro relationship between a local resource
and a remote resource. You can create a HyperMetro pair as a LUN or create a HyperMetro
consistency group as a LUN group.
1. Create a HyperMetro pair for LUNs and map the LUNs on storage 01 and storage 02 to
the host.
2. (Optional) Create a HyperMetro consistency group for the LUN group and map
storage resources to the host.

Configuring HyperMetro > Creating a HyperMetro Domain > Creating a HyperMetro
Pair/Consistency Group.
Step 5 (Optional) Verify HyperMetro configuration.
1. Log in to the host to view the mapped LUNs.

2. Simulate a device fault, for example, cancel the LUN mapping of storage device 01,
and check whether the HyperMetro LUNs can be read and written properly on the
host.
Procedure: On the DeviceManager of storage 01, choose Services > LUN/LUN Group >
Unmap. Check whether the LUN resource status on the host is normal and whether the
LUN can be read and written.
In this case, the LUN mapping of storage 01 is canceled, and the host cannot access the
LUN of storage 01. However, the LUN mapping of storage 02 still works, and the host can
still access the LUN of storage 02. In addition, the LUNs of storage devices 01 and 02 are
configured in HyperMetro mode. Therefore, although the LUN of one storage device is
inaccessible, the host can still access the LUN.
2.4.2 Scenario 2: HyperMetro Management and O&M

2.4.2.1 Background
In routine operations and applications, you also need to understand some routine
management operations. You need to help engineers get familiar with how to manage
remote HyperMetro consistency groups.

2.4.2.2 Question
What is a HyperMetro domain? What precautions should I take when configuring a
HyperMetro domain?
2.4.2.3 Task 1: HyperMetro Management and O&M

After completing the configuration, you need to know routine management operations,
such as modifying and deleting HyperMetro configurations. You need to help engineers get
familiar with the routine management operations.
Step 1 Modify a HyperMetro domain.
Change the HyperMetro domain name and change the HyperMetro domain to the static
priority mode.
Routine Management > Managing HyperMetro Domains > Modifying a HyperMetro
Domain.
Step 2 Delete a quorum server.

Delete a quorum server.
Routine Management > Managing Quorum Servers > Deleting a Quorum Server.
Step 3 Uninstall the quorum server software.

Uninstall the quorum server software.

Routine Management > Managing Quorum Servers > Uninstalling the Quorum Server.
Step 4 Manage the HyperMetro pair.
On storage device 01, modify, pause, and synchronize the HyperMetro pair, and perform a
switchover to the preferred site.
1. Set the data synchronization rate of the HyperMetro pair to high.
2. Pause the HyperMetro pair.
3. Restore the HyperMetro pair.
4. Switch to the preferred site in the HyperMetro pair.
5. Delete the HyperMetro pair.
Routine Management > Managing HyperMetro Pairs > Modifying a HyperMetro Pair.
Routine Management > Managing HyperMetro Pairs > Pausing a HyperMetro Pair.
Routine Management > Managing HyperMetro Pairs > Synchronizing a HyperMetro
Pair.

Routine Management > Managing HyperMetro Pairs > Switching the Preferred Site
for a HyperMetro Pair.
Routine Management > Managing HyperMetro Pairs > Deleting a HyperMetro Pair.
Step 5 (Optional) Manage the HyperMetro consistency group.
On storage device 01, browse, pause, and synchronize the HyperMetro consistency group,
and perform a switchover to the preferred site in the group.
1. Set the data synchronization rate of the HyperMetro consistency group to high.
2. Pause the HyperMetro consistency group.
3. Restore the HyperMetro consistency group.
4. Switch to the preferred site in the HyperMetro consistency group.
5. Delete the HyperMetro consistency group.
Routine Management > Managing HyperMetro Consistency Groups > Modifying a
HyperMetro CG.
Routine Management > Managing HyperMetro Consistency Groups > Pausing a
HyperMetro CG.
Routine Management > Managing HyperMetro Consistency Groups > Synchronizing a
HyperMetro CG.
Routine Management > Managing HyperMetro Consistency Groups > Switching the
Preferred Site for a HyperMetro CG.
Routine Management > Managing HyperMetro Consistency Groups > Deleting a
HyperMetro CG.

2.4.2.4 Discussion
How can I delete the HyperMetro domain and the quorum server?
[Suggested Answer]
1. Set the running status of the HyperMetro consistency group to Paused.
2. Delete the HyperMetro consistency group.
3. Delete the HyperMetro pair.
4. Delete the HyperMetro domain and the quorum server.

My Opinion:

Scenario-based Practice of HyperMetro
Disaster Recovery
Background
 An enterprise has purchased two sets of Huawei OceanStor all-flash storage devices and plans to
protect data using LUN HyperMetro to ensure high service reliability. Therefore, the enterprise
has purchased the HyperMetro license. As a storage engineer, you need to help the company
complete the configuration of the HyperMetro feature.
Storage Mounting
Application LUN Name LUN Size Remarks
Device Method
Storage device HyperMetro

Data services Lun_001 iSCSI 3 GB
01 experiment
Storage device HyperMetro

Data services Lun_001 iSCSI 3 GB
02 experiment
 Note: Cases in this document are examples only. The actual configurations may vary according to operating
environments. For details about the configuration steps, see the corresponding product documentation.
Networking Diagram
Practice
Objectives Form
• To know the application scenarios of • Trainees split into groups of two or
HyperMetro through case study. three.
• To be able to configure HyperMetro • Each group prepares materials for
through case study. presentation.
• To be able to perform the management • After each presentation, the technical
and O&M of HyperMetro. officer asks questions, and the
evaluator gives feedback and scores.
Opinion
Sharing
Scenario 1: HyperMetro Operations and Configurations
Task 1 Task 2
Set up the test Configure

environment HyperMetro
Question
 What are the main types of Huawei storage HyperMetro architecture?
[Suggested Answer]
 There are two types of Huawei storage HyperMetro logical architecture: local DC deployment and cross-DC deployment.
1. Local data center deployment: In most cases, data centers are deployed in different equipment rooms in the same
industrial park. Hosts are deployed in cluster mode. Hosts and storage devices communicate with each other through
switches, which can be either FC or IP switches. In addition, HyperMetro mirroring channels are deployed between the
storage devices to ensure that the HyperMetro services can run properly.
2. Cross-DC deployment: Two data centers are deployed in the same city or adjacent cities, with their physical distance
less than 300 km. Both are running and can carry the same services at the same time, improving the overall service
capability and system resource utilization of the data centers. If a single point failure occurs, services are automatically
switched to the other DC. In the scenario of cross-DC deployment with long-distance transmission (a minimum of 80
km for IP networking and 25 km for FC networking), dense wavelength division multiplexing (DWDM) devices must be
deployed to ensure a short transmission latency. In addition, HyperMetro mirroring channels are deployed
between the storage devices to ensure that the HyperMetro services can run properly.
Task 1: Setting Up the Test Environment
 Check the test environment before configuration.
 Install the multipathing software.
 Install and configure the quorum server software.
Question
 What are the differences between the static priority mode and the quorum server mode?
[Suggested Answer]
 If no quorum server is configured or the quorum server is inaccessible, HyperMetro works in static priority mode. When
an arbitration occurs, the preferred site in a HyperMetro pair wins the arbitration and provides services.
 If a link between storage arrays is disconnected or the site that is set as the non-preferred site in a HyperMetro pair breaks down, LUNs
at the preferred site continue to provide HyperMetro services while LUNs at the non-preferred site stop providing HyperMetro services.
 If the site that is set as the preferred site in a HyperMetro pair breaks down, the non-preferred site cannot automatically take over
HyperMetro services. As a result, the HyperMetro services are stopped. You need to forcibly start the HyperMetro services at the non-
preferred site.
 An independent physical server or VM is used as a quorum server. It is recommended that the quorum server be deployed
at a dedicated site that is in a different fault domain from the two data centers. In this way, when a disaster occurs in a
single data center, the quorum server still works.
 In quorum server mode, in the event of a DC failure or link disconnection between the storage systems, each storage
system sends an arbitration request to the quorum server, and only the winner continues providing services. The preferred
site takes precedence in arbitration.
Task 2: Configuring HyperMetro
 Check the configuration process.
 Add a remote device.
 Create a HyperMetro domain.
 Create a HyperMetro pair and a HyperMetro consistency group.
 (Optional) Verify HyperMetro configuration.
Question
 What is the function of a remote replication consistency group? How can I configure a consistency group
when no consistency group needs to be created?
 A remote replication consistency group (CG) ensures that the secondary LUNs of all remote replication pairs in the CG
are at the same point in time. In this way, availability of data backup and recovery can be ensured when a host writes
data to multiple primary LUNs. After remote replication pairs are added to a consistency group, you can perform
operations only on the consistency group rather than the pairs in the consistency group.
 If services are associated between the primary LUN and other LUNs, create a consistency group. If the primary LUN is
independent and not associated with other LUNs, you can create a pair without creating a consistency group.
 You can also use DeviceManager to configure a remote replication pair. For details, see Documentation (of your product)
> Configuration & Commissioning > Feature Guide > HyperMetro Feature Guide (specific to your product model and
version) > Configuring HyperMetro > Creating a HyperMetro Domain > Creating a HyperMetro Pair/Consistency
Group.
Scenario 2:
Task 1
HyperMetro
Management and O&M
Task 1: HyperMetro Management and O&M
 Modify a HyperMetro domain.
 Delete a quorum server.
 Uninstall the quorum server.
 Manage a HyperMetro pair.
 Manage a HyperMetro consistency group.
Question
 What is a HyperMetro domain? What precautions should I take when configuring a HyperMetro domain?
 [Suggested Answer]
 A HyperMetro domain is a collection of local and remote devices and a quorum server (which is optional). It defines the
relationships among the local and remote devices as well as the quorum server.
 A remote device provides HyperMetro services at the remote end in a HyperMetro domain. When initial synchronization
is implemented for HyperMetro, the remote device serves as the secondary end for the synchronization.
 A quorum server must be added to the HyperMetro domain if you want to use the quorum server arbitration mode. You
must create a quorum server for the local and remote storage systems so that it can arbitration judgment for host access
in case of a device fault in the HyperMetro domain.
 A quorum server provides arbitration services to determine which site in a HyperMetro domain continues to provide
services when a device fault occurs or a link is disconnected. If no quorum server is configured in a HyperMetro domain,
the preferred site will provide services by default after a fault occurs. If a quorum server is configured, the quorum server
determines which site continues providing services in the event of a fault.
Trainee Assessment

complete.

the specified time.
Overall
intelligent world.


HCIP-Storage
HyperReplication Disaster
Recovery
(For Trainees)
1
Notice


HCIP-Storage Scenario-based Practice of HyperReplication Disaster Recovery Page 1

troubleshooting.
industry peers.


Contents

1.1 References...........................................................................................................................................................................4
1.2 Software Tools ...................................................................................................................................................................4
2 Scenario-based Practice of HyperReplication Disaster Recovery ............................... 5
2.1 Course Overview ...............................................................................................................................................................5
2.2 Objectives............................................................................................................................................................................5
2.3 Case Background ..............................................................................................................................................................5
2.4 Tasks and Suggested Answers ......................................................................................................................................6
2.4.1 Scenario 1: Initial Configuration ................................................................................................................................6
2.4.2 Scenario 2: Application and Management .......................................................................................................... 10

1.1 References
Note:
The specifications of HyperReplication vary by product. For details, see the product
1.2 Software Tools

DeviceManager Demo
Note:
(https://support.huawei.com/enterprise/) and search DeviceManager Demo to find and

Storage system Huawei OceanStor Dorado V6 6.0.1 2

Windows OS --
Server 2016 version

2
HyperReplication Disaster Recovery
2.1 Course Overview

their knowledge on the use of HyperReplication.
2.2 Objectives
 To be able to know the application scenarios of HyperReplication through case study
 To be able to configure HyperReplication through case study
2.3 Case Background

Note:
A company is considering establishing disaster recovery (DR) protection for the current
services, involving two remote sites. The two sites use Huawei OceanStor all-flash storage
devices, and the license for HyperReplication has been purchased. Now, you need to help
the storage engineers of the company complete the test configuration and function
verification of the HyperReplication feature.
The following figure shows the network topology of the company's storage system.

Figure 2-1

2.4.1 Scenario 1: Initial Configuration
2.4.1.1 Background
To implement HyperReplication DR, the company plans to implement asynchronous
remote replication between the active and standby storage systems through the IP
replication network.
In the initial environment, a file system has been established and mounted for Data_LUN
and Control_LUN on Huawei all-flash storage at the primary site on the host running the
Windows. Services on the two LUNs are consistent. The detailed test configurations are as
follows:
LUN Mapping
Storage Device Application LUN Name Test File
Capacity Host
Host running
Storage device Data_LUN 5 GB Service.txt
the Windows
at the primary Database
site Host running
Control_LUN 5 GB Log.txt
the Windows
2.4.1.2 Question
What are the differences between synchronous remote replication and asynchronous
remote replication?
2.4.1.3 Task 1: Preparing for the Configuration

Before configuring HyperReplication, you need to sort out the configuration processes and
prepare for the configuration.

Step 1 Check the configuration process.

Sort out the following configuration processes, draw a flowchart, and introduce how to
configure HyperReplication using the flowchart to engineers.
Figure 2-2
Feature Guide > HyperReplication Feature Guide (specific to your product model and
version) > Configuring HyperReplication > Configuration Process.
Step 2 Prepare for the configuration.

Before configuring HyperReplication, you need to set device information, including the
device name and location, on both the primary and secondary storage devices to
distinguish them. In addition, to ensure that customers have the permission to use
HyperReplication, check that the license file contains the information about this feature.
Before configuring HyperReplication, help engineers change the device name and location
and check the HyperReplication license information.
version) > Configuring HyperReplication > Preparing for the Configuration/Checking
the License File.

2.4.1.4 Question
What operations may be involved in the configuration preparation phase?
2.4.1.5 Task 2: Configuring HyperReplication

After the preparations are completed, you can perform the initial configuration of the
HyperReplication feature in this scenario.
Step 1 Add an authentication user of the remote device.

Authentication is a process of checking whether a user has the permission to access the
system. Based on specific service requirements, super administrators can create different
levels of user accounts and grant them only necessary permissions, thereby ensuring
system stability and data security. You can help engineers create a user with the role of the
remote device administrator.
version) > Configuring HyperReplication > Adding an Authentication User.
Step 2 Add a remote device.

Before adding a remote device, ensure that the connection between the local and remote
devices is established. In this scenario, configure the link type of the remote device as IP
link. Therefore, you must ensure that the IP address of the local port of the selected IP link
and the IP address of the front-end port of the remote device are on the same network
segment and can communicate with each other. Help engineers add remote devices whose
link type is IP link.
version) > Configuring HyperReplication > Adding a Remote Device.
Step 3 Create a protection group.

In this scenario, two LUNs with service consistency are involved. You need to create a
protection group to configure the remote replication consistency group. Help engineers
create a protection group for Data_LUN and Control_LUN.

version) > Configuring HyperReplication > Creating PGs.
Step 4 Create an asynchronous remote replication consistency group.

Help engineers create a remote replication consistency group for Data_LUN and
Control_LUN using the protection group created in step 3 and set the replication mode to
Asynchronous.
version) > Configuring HyperReplication > Creating a Remote Replication CG >
Creating an Asynchronous Remote Replication CG.
2.4.1.6 Question
What is the function of a remote replication consistency group? How can I configure a
consistency group when no consistency group needs to be created?
2.4.1.7 Discussion
In the preceding scenarios, HyperReplication is configured based on block storage services.
In actual applications, storage devices can also be used to provide file services. Think about
and discuss the following questions:
1. When Huawei all-flash storage devices are used, what is the difference between the
remote replication feature in the file service scenario and that in the block service
scenario?
2. How can I configure HyperReplication for file services? You can try to draw a
flowchart.

2.4.2 Scenario 2: Application and Management

2.4.2.1 Background
After HyperReplication is configured, storage engineers need to understand some routine
management operations. You need to help engineers get familiar with how to manage
remote replication consistency groups.
2.4.2.2 Task 1: Managing a Remote Replication Consistency Group

Step 1 Modify a remote replication consistency group.
Link compression is an inline compression technology. In asynchronous remote replication,
data is compressed in advance on the primary device before being transferred. Then the
compressed data is decompressed on the secondary device after being received, reducing
the bandwidth required for data transfer. To reduce the bandwidth required for data
transfer, engineers intend to enable the link compression function. Help them modify the
remote replication consistency group and enable the link compression function.
version) > Managing a Remote Replication CG > Modifying a Remote Replication CG.
Step 2 Synchronize a remote replication consistency group.

At some points in time, you need to manually start synchronization for all remote
replication pairs in the consistency group to ensure that the data on the primary and
secondary LUNs of each remote replication pair in the consistency group keeps consistent
at the synchronization point in time. Help engineers synchronize the remote replication
consistency group.
version) > Managing a Remote Replication CG > Synchronizing a Remote Replication
CG.

Step 3 Split a consistency group.

After a remote replication consistency group is split, all remote replication pairs in the
consistency group are split at the same time to generate a complete copy of the secondary
LUNs of all remote replication pairs at a specific point in time. Help engineers splitting the
remote replication consistency group.
version) > Managing a Remote Replication CG > Splitting a Remote Replication CG.
Step 4 Enable or disable protection for the secondary resources of a consistency group.
After protection for the secondary resources of a consistency group is enabled, data cannot
be written to the secondary resources, ensuring data security of the secondary resources.
After protection for the secondary resources in a consistency group is disabled, data can be
written to the secondary resources again. Help engineers get familiar with how to enable
and disable protection for the secondary resources of a consistency group.
version) > Managing a Remote Replication CG > Enabling/Disabling Protection for the
Secondary Resource in a Remote Replication CG.
Step 5 Perform a primary/secondary switchover for a consistency group.

When the primary LUNs in a consistency group fail, you can initiate a primary/secondary
switchover to enable the secondary LUNs to become the new primary LUNs, taking over
services from the original primary LUNs to ensure service continuity. Help engineers
perform a primary/secondary switchover for the consistency group.

version) > Managing a Remote Replication CG > Performing a Primary/Secondary
Switchover for a Remote Replication CG.
2.4.2.3 Question
How can I verify the configuration of a remote replication consistency group?
2.4.2.4 Task 2: Managing Protection Groups

Step 1 Add or remove LUNs.
In some scenarios, you need to add LUNs to a protection group to increase storage capacity
or remove unnecessary LUNs from a protection group to release storage space. Instruct
engineers to add LUNs to or remove LUNs from a protection group.
version) > Managing PGs > Adding/Removing a LUN.
Step 2 Modify protection groups.

You may need to modify the basic information about a protection group based on actual
service requirements. Help engineers change the name of the protection group to PG_test.
version) > Managing PGs > Modifying PGs.
2.4.2.5 Question
What are the differences between a LUN group and a protection group?
2.4.2.6 Task 3: Deleting and Clearing

Step 1 Delete a consistency group.

If you do not need to uniformly manage remote replication through a consistency group,
you can delete the consistency group. Instruct engineers to delete a remote replication
consistency group.
version) > Managing a Remote Replication CG > Deleting a Remote Replication CG.
Step 2 Delete a protection group.

Instruct engineers to delete an unwanted protection group.
version) > Managing PGs > Deleting a PG.
Step 3 Remove a remote device.

Instruct engineers to delete an unwanted remote device.
version) > Managing Remote Devices > Removing a Remote Device.

My Opinion:


Scenario-based Practice of HyperReplication
Disaster Recovery
Background
 A company is considering establishing disaster recovery (DR) protection for the current services, involving two remote sites.
The two sites use Huawei OceanStor all-flash storage devices, and the license for HyperReplication has been purchased. Now,
you need to help the storage engineers of the company complete the test configuration and function verification of the
HyperReplication feature.
 To implement HyperReplication DR, the company plans to implement asynchronous remote replication between the active
and standby storage systems through the IP replication network.
 In the initial environment, a file system has been established and mounted for Data_LUN and Control_LUN on Huawei all-
flash storage at the primary site on the host running the Windows. Services on the two LUNs are consistent. The detailed test
configurations are as follows:
Storage Device Application LUN Name LUN Capacity Mapping Host Test File
Data_LUN 5 GB Host running the Windows Service.txt
Storage device at
Database
the primary site
Control_LUN 5 GB Host running the Windows Log.txt
 Note: Cases in this document are examples only. The actual configurations may vary according to operating environments.
For details about the configuration steps, see the corresponding product documentation.
Networking Diagram
Host Name/IP Host Name/IP

Address Address
IP
network
Storage device at the Storage device at the

primary site secondary site
Practice
Objectives Form
• To be able to know the application • Trainees split into groups of two or
scenarios of HyperReplication through three.
case study • Each group prepares materials for
• To be able to configure presentation.
HyperReplication through case study • After each presentation, the technical
officer asks questions, and the
Opinion
Sharing
Scenario 1: Initial Configuration
Task 1 Task 2
Preparing for the Configuring

Configuration HyperReplication
Question
 What are the differences between synchronous remote replication and asynchronous remote replication?
 They are implemented in different ways and applied to different service scenarios.
 Implementation methods: In synchronous remote replication mode, when data is written to a primary resource, the write request is also sent
to a secondary resource. After both the primary and secondary resources return a write success response, the storage system sends a write
success message to the host. In this way, data on the primary resource is kept consistent with that on the secondary resource, preventing data
loss in the event of a disaster. In asynchronous remote replication mode, when data is written to the primary resource, the primary site
records the modified data. After the primary resource returns a write success response, the primary site returns a write success response to
the host. When the amount of modified data reaches a certain value, all modified data is synchronized to the secondary resource of the
remote storage device at a time.
 Application scenarios: Synchronous remote replication has high requirements for bandwidth and data latency. Therefore, synchronous remote
replication mainly applies to DR scenarios where the primary and secondary devices are close to each other, for example, intra-city DR and
backup. Asynchronous remote replication has low requirements for bandwidth and data latency. Therefore, it applies to DR scenarios where
the primary and secondary devices are far from each other or the network bandwidth is limited.
Task 1: Preparing for the Configuration
 Check the configuration process.
 Prepare for the configuration.
Question
 What operations may be involved in the configuration preparation phase?
 If you find that the HyperReplication feature is unavailable when checking the license
information, import and activate the HyperReplication license on the storage system before
using it.
 Before configuring the HyperReplication feature, you need to select a replication port.
HyperReplication supports data transmission through fiber channel (FC) ports or Ethernet
ports. In actual networking, you need to consider the characteristics of FC or Ethernet ports,
bandwidth, latency, network quality, and security to ensure link efficiency and stability during
data transmission.
Task 2: Configuring HyperReplication
 Add an authentication user of the remote device.
 Add a remote device.
 Create a protection group.
 Create an asynchronous remote replication consistency group.
Question
 What is the function of a remote replication consistency group? How can I configure a consistency group
when no consistency group needs to be created?
 A HyperReplication consistency group (CG) ensures that the secondary LUNs of all remote replication pairs in the CG are
at the same point in time. In this way, availability of data backup and recovery can be ensured when a host writes data to
multiple primary LUNs. After remote replication pairs are added to a consistency group, you can perform operations only
on the consistency group rather than the pairs in the consistency group.
 If services are associated between the primary LUN and other LUNs, create a consistency group. If the primary LUN is
independent and not associated with other LUNs, you can create a pair without creating a consistency group.
 You can also use DeviceManager to configure a remote replication pair. For details, see Documentation (of your product)
> Configuration & Commissioning > Feature Guide > HyperReplication Feature Guide (specific to your product model
and version) > Configuring HyperReplication > Creating a Remote Replication Pair.
Discussion
 In the preceding scenarios, HyperReplication is configured based on block storage
services. In actual applications, storage devices can also be used to provide file services.
Think about and discuss the following questions:
 When Huawei all-flash storage devices are used, what is the difference between the remote
replication feature in the file service scenario and that in the block service scenario?
 How can I configure HyperReplication for file services? You can try to draw a flowchart.
 Note: If possible, you can perform an experiment to verify the result.
Scenario 2: Application and Management
Task 1 Task 2 Task 3
Managing a Remote Managing Deleting and

Replication Protection Groups Clearing
Consistency Group
Task 1: Managing a Remote Replication Consistency
Group
 Modify a remote replication consistency group.
 Synchronize a remote replication consistency group.
 Split a consistency group.
 Enable or disable protection for the secondary resources of a consistency group.
 Perform a primary/secondary switchover for a consistency group.
Question
 How can I verify the configuration of a remote replication consistency group?
 You can view the running status of a remote replication consistency group and determine
whether to synchronize, split, or perform a primary/secondary switchover for the group based
on the status. After the operation is complete, you can log in to the host mapped by the
primary or secondary storage device to perform read and write operations and verify the
configuration.
 For details, see Documentation (of your product) > Configuration & Commissioning >
version) > Configuring HyperReplication > Verifying the Configuration.
 To verify the configuration of a remote replication consistency group, you need to map all
primary and secondary LUNs in the consistency group to the host. You can perform an
experiment if possible.
Task 2: Managing Protection Groups
 Add or remove LUNs.
 Modify protection groups.
Question
 What are the differences between a LUN group and a protection group?
 LUN groups are used in mapping scenarios. You can divide LUN groups based on hosts or
applications.
 Protection groups are used to protect data in consistency groups. You can plan data protection
policies based on applications, select different data protection policies for different
components in applications, and protect LUNs that apply to the same protection scenario in
multiple applications in a unified manner.
 For example, to protect LUNs that apply to the same protection scenario in multiple
applications in a unified manner, you can combine the LUNs into a LUN group, map the LUN
group to a host or host group, and create a protection group for the LUN group.
Task 3: Deleting and Clearing
 Delete a consistency group.
 Delete a protection group.
 Remove a remote device.
Trainee Assessment

complete.

the specified time.
Overall
intelligent world.


HCIP-Storage
LUN Migration for
Heterogeneous Storage
Systems
(For Trainees)

Notice


HCIP-Storage Scenario-based Practice of LUN Migration for Heterogeneous
Storage Systems Page 1

troubleshooting.
industry peers.


Contents

1.1 References.......................................................................................................................................................................... 4
1.2 Software Tools .................................................................................................................................................................. 4
2 Scenario-based Practice of LUN Migration for Heterogeneous Storage Systems ...6
2.1 Course Overview .............................................................................................................................................................. 6
2.2 Objectives........................................................................................................................................................................... 6
2.3 Case Background ............................................................................................................................................................. 6
2.4.1 Scenario 1: Taking Over Huawei Storage Devices in Offline Mode ............................................................... 7
2.4.2 Scenario 2: Migrating Services from Heterogeneous Storage Systems ....................................................... 12

1.1 References
Note:
The specifications of SmartVirtualization vary by product. For details, see the product
1.2 Software Tools

Note:
(https://support.huawei.com/enterprise/) and search UltraPath to find and download the
2. Huawei OceanStor DeviceManager Demo
Note:

Storage system OceanStor Dorado V6 2

Windows OS --
Server 2016 version

Linux OS SUSE, Red Hat, CentOS, or EulerOS
UltraPath 21.6.3 --
software version

2 Scenario-based Practice of LUN

Migration for Heterogeneous Storage
Systems
2.1 Course Overview

their knowledge on the use of SmartVirtualization and SmartMigration.
2.2 Objectives
 To understand the application scenarios of SmartVirtualization and SmartMigration
 To be able to configure SmartVirtualization and SmartMigration
2.3 Case Background

Note:
To upgrade its enterprise storage systems, a company has purchased a Huawei OceanStor
all-flash storage device and the SmartVirtualization and SmartMigration licenses. Help
storage engineers of the company use the new device to take over the legacy Huawei
storage device and migrate data to the new storage device.
The following figure shows the company's live network topology.


2.4.1 Scenario 1: Taking Over Huawei Storage Devices in Offline
Mode
2.4.1.1 Background
To upgrade its storage systems, the company plans to use a new Huawei storage device to
replace the legacy one. It is planned to use SmartVirtualization to take over service LUNs
on the original storage device. As the customer allows a short service interruption, offline
takeover is used.
In the initial environment, LUN_SOUR on the original storage device has been mapped and
accessible to the Windows host. The following table lists the test configurations of the
original storage device:
Storage LUN Mapping

Application LUN Name Test File
Device Capacity Host
Original
Windows
storage Database LUN_SOUR 5 GB test.txt
host
device
2.4.1.2 Question
In SmartVirtualization, what are online takeover and offline takeover? What are the
differences in the masquerading properties for eDevLUNs between the two modes?
2.4.1.3 Task 1: Preparing for the Configuration

After analyzing requirements and planning configurations, perform the following
operations to prepare for the configuration:
Step 1 Streamline the process.

Engineers are familiar with the configuration of SmartMigration. Draw a flowchart for
configuring SmartVirtualization based on the following operations. Then, introduce how to
use SmartVirtualization to take over Huawei storage devices in offline mode based on the
flowchart.
For details about how to draw a flowchart, see Configure > SmartVirtualization Feature
Guide > Taking Over Huawei Heterogeneous Storage Systems in Offline Mode >
Configuration Process in the product documentation.
Step 2 Check the license file.
Ensure that permissions to use SmartVirtualization and SmartMigration have been granted.
Help the engineer check the SmartVirtualization and SmartMigration license information.
For details, see Operation and Maintenance > Administrator Guide > Routine
Management > Managing License Files in the product documentation.

2.4.1.4 Question
What are the differences between the online takeover process and offline takeover process
when Huawei all-flash devices are used to take over Huawei storage devices?
2.4.1.5 Task 2: Configuring Connections Between Storage Devices

Step 1 Add an external storage device.
The new and original storage devices have been physically connected. They are on the
same network segment using iSCSI connection. Assist engineers in adding an external iSCSI
device. The iSCSI device is automatically named by the system after being created. You can
change the device name based on the site requirements.
For details, see Configure > SmartVirtualization Feature Guide > Taking Over Huawei
Heterogeneous Storage Systems in Offline Mode > Configuring the Logical
Connection Between the Heterogeneous Storage System and the Local Storage
System > iSCSI Connection > Adding an External Storage Device in the product
documentation.
Step 2 Configure the original storage device.
Assist engineers in suspending the Windows host services on the original storage device,
that is, unmapping the original storage device and host. Then, create mapping between the
new and original storage devices.
After the connection between the new storage device and the original storage device is
established, the original storage device takes the new storage device as a host.
The configuration operations vary depending on the storage device. For details, see the
operation guide of the original storage device.
If a Huawei all-flash storage device is used to simulate the original storage device in a lab
environment, see Configure > Basic Storage Service Configuration Guide for Block in
the product documentation.
Step 3 Scan for external LUNs.

Assist engineers in scanning for external LUNs. After scanning, LUNs mapped from the
original storage device to the new storage device can be connected to the new storage
device.
Heterogeneous Storage Systems in Offline Mode > Configuring the Logical
Connection Between the Heterogeneous Storage System and Local Storage System >
iSCSI Connection > Scanning for External LUNs in the product documentation.
2.4.1.6 Question
What does takeover mean?
2.4.1.7 Task 3: Configuring and Using the eDevLUN

Step 1 Create an eDevLUN.
To configure SmartMigration, you need to create an eDevLUN that belongs to the storage
pool of the new storage device. A storage pool has been created. Assist engineers in
creating an eDevLUN named eDevLUN_XXX.
Heterogeneous Storage Systems in Offline Mode > Configuring and Using an
eDevLUN > Creating an eDevLUN in the product documentation.
Step 2 Manage the eDevLUN.
After the eDevLUN is created, introduce how to view and manage the eDevLUN.
For details, see Configure > Basic Storage Service Configuration Guide for Block >
Managing Basic Storage Services > Managing LUNs in the product documentation.

2.4.1.8 Question
What are the differences between external LUNs and eDevLUNs?
2.4.1.9 (Optional) Task 4: Managing Heterogeneous Storage System

Resources in a Centralized Manner
Step 1 (Optional) Establish the mapping between eDevLUNs and application servers.
Stop services on the original storage device and install Huawei UltraPath on the application
server. To centrally manage resources of heterogeneous storage systems, you need to map
eDevLUNs to application servers so that the application servers can identify the eDevLUNs
as readable and writable storage resources.
For details, see Configure > SmartVirtualization Feature Guide >Taking Over Huawei
Heterogeneous Storage Systems in Offline Mode > Configuring and Using an
eDevLUN > Establishing Mapping Relationships Between eDevLUNs and the
Application Server in the product documentation.
Step 2 (Optional) Scan for LUNs on the application server.
After the storage configuration is complete, scan for LUNs on the host and check whether
the content in the test.txt file is correct.
corresponding operation guide. After the host scans for LUNs, you can write data to the
test_new.txt file to verify the read and write functions.
2.4.1.10 Question
After the eDevLUN takes over online services, if the original storage device is faulty
(unavailable), will the online services of the application server be affected?

2.4.2 Scenario 2: Migrating Services from Heterogeneous Storage

Systems
2.4.2.1 Background
After service LUNs are taken over from the original storage device with the
SmartVirtualization feature, you need to use the SmartMigration feature to migrate data
from the service LUNs to the new storage device.
2.4.2.2 Question
How is load balancing implemented for SmartVirtualization?
2.4.2.3 Task 1: Migrating LUNs

Step 1 Configure SmartMigration.
Assist engineers in configuring SmartMigration and establishing a data migration

relationship between the source LUN (eDevLUN_XXX) and target LUN. You can name the
target LUN MT_eDevLUN_XXX.
For details about operations on DeviceManager, see Configure > SmartMigration Feature
Guide > Configuring SmartMigration in the product documentation.
Step 2 Delete a SmartMigration task.
You are advised to delete the SmartMigration task before taking over services. If you do not
delete the SmartMigration task, the mapping to the target LUN may fail to be created.
Assist engineers in deleting the SmartMigration task.
For details about operations on DeviceManager, see Configure > SmartMigration Feature
Guide > Managing SmartMigration in the product documentation.

2.4.2.4 (Optional) Task 2: Taking Over Services

Step 1 (Optional) Create the mapping between the application server and the target LUN.
After Huawei UltraPath is installed on the application server, you need to map
MT_eDevLUN_XXX to the application server so that the application server can identify
MT_eDevLUN_XXX as a readable and writable storage resource.
For details, see Configure > Basic Storage Service Configuration Guide for Block in the
product documentation.
Step 2 (Optional) Use the target LUN on the application server.
After the configuration on the storage device is complete, scan for and use the target LUN
on the host and check whether the content in the test.txt file is correct.
related operation guide. After the host scans for LUNs, you can write new files to verify the
read and write functions.
2.4.2.5 Question
What can I do if a fault (for example, the source LUN or target LUN is faulty) occurs during
LUN migration? What will be done after the fault is rectified?
2.4.2.6 Discussion
Think and discuss how to use Huawei all-flash storage devices to take over third-party
storage devices in offline mode. You can draw a flowchart to describe the process.


My Opinion:

Scenario-based Practice of LUN Migration
for Heterogeneous Storage Systems
Background
 To upgrade its enterprise storage systems, a company has purchased a Huawei OceanStor all-flash storage device and the
SmartVirtualization and SmartMigration licenses. Help storage engineers of the company use the new device to take over the
legacy Huawei storage device and migrate data to the new storage device.
 The company plans to use a new Huawei storage device to replace the legacy one. It is planned to use SmartVirtualization to
take over service LUNs on the original storage device. As the customer allows a short service interruption, offline takeover is
used.
 In the initial environment, LUN_SOUR on the original storage device has been mapped and accessible to the Windows host.
The following table lists the test configurations of the original storage device.
Mapping
Storage Device Application LUN Name LUN Capacity Test File
Host
Original storage
Database LUN_SOUR 5 GB Windows host test.txt
device
 Note: Cases in this course are examples only. The actual configurations may vary according to actual environments.
For details, see the corresponding product documentation.
Networking Diagram
Host Host
IP
network
New storage device Original storage device
Practice Mode
Objectives Form
• To understand the application • Trainees split into groups of two or
scenarios of SmartVirtualization and three.
SmartMigration • Each group prepares materials for
• To be able to configure presentation.
SmartVirtualization and • After each presentation, the technical
SmartMigration officer asks questions, and the
Opinion
Sharing
Scenario 1: Taking Over Huawei Storage Devices in
Offline Mode
Task 1 Task 2 Task 3 Task 4
Preparing for the Configuring Connections Configuring and Using (Optional) Managing
Configuration Between Storage Devices the eDevLUN Resources in a
Centralized Manner
Question
 In SmartVirtualization, what are online takeover and offline takeover? What are the differences in the masquerading
properties for eDevLUNs between the two modes?
 Offline takeover: During the offline takeover process, connections between heterogeneous storage systems and application servers are down
and services are interrupted temporarily. This mode is applicable to all compatible Huawei and third-party heterogeneous storage systems.
 Online takeover: During the online takeover process, services are not interrupted, ensuring service continuity and data integrity. In this mode,
the critical identity information about heterogeneous LUNs is masqueraded so that multipathing software can automatically identify new
storage systems and switch I/Os to the new storage systems. This remarkably simplifies data migration and minimizes time consumption.
 To perform an offline takeover, you need to suspend services on the application server and the masquerading property of eDevLUNs is No
masquerading. During the online take over of Huawei heterogeneous storage systems, the basic information such as the WWNs of the
eDevLUNs will be replaced with the corresponding information of external LUNs. The masquerading property of eDevLUNs is Basic
masquerading or Extended masquerading. The selection of basic masquerading or extended masquerading depends on the vendor and
version of the multipathing software and the versions of Huawei heterogeneous storage systems. For details, see the product documents of
the corresponding version.
Task 1: Preparing for the Configuration
 Streamline the process.
 Check the license information.
Question
 What are the differences between the online takeover process and offline takeover process when Huawei all-
flash devices are used to take over Huawei storage devices?
 Before configuring online takeover, you need to check whether the information about the application server, original
storage device, and new storage device is normal for a proper online takeover.
 Online takeover switches over host paths to ensure service continuity, while offline takeover does not. During an offline
takeover, eDevLUNs are remapped to the host to implement takeover. Host path switchover is configured to switch the
host path to the path between the application server and the new storage device so that the new storage device can
smoothly carry service data. For details about how to configure host path switchover for online takeover, see the related
 After host path switchover is complete, clear the path switchover property of the masqueraded eDevLUN to convert it
into a common LUN for other online takeover tasks.
 Note: The online takeover procedure is complex and involves high-risk operations. Contact the data migration
service team to evaluate and implement a migration solution.
Task 2: Configuring Connections Between Storage
Devices
 Add an external storage device.
 Configure the original storage device.
 Scan for external LUNs.
Question
 What does "takeover" mean?
 Takeover refers to the mapping of LUNs in a heterogeneous storage system to the
local storage system for use and management.
Task 3: Configuring and Using the eDevLUN
 Create an eDevLUN.
 Manage the eDevLUN.
Question
 What are the differences between external LUNs and eDevLUNs?
 An external LUN is a LUN in a heterogeneous storage system, displayed as a remote LUN on DeviceManager of the local
storage system.
 In the storage pool of a local storage system, the mapped external LUNs are reorganized as raw storage devices based on
a certain data organization form. A raw device is called an eDevLUN. The physical space occupied by an eDevLUN in the
local storage system is merely the storage space needed by the metadata. The service data is still stored on the
heterogeneous storage system. Application servers can use eDevLUNs to access data on external LUNs in the
heterogeneous storage system, and the SmartMigration feature can be configured for the eDevLUNs.
 An eDevLUN consists of data and metadata. A mapping relationship is established between data and metadata.
The physical space needed by data is provided by the external LUN from the heterogeneous storage system. Data does
not occupy the capacity of the local storage system.
Metadata is used to manage storage locations of data on an eDevLUN. The space used to store metadata comes from
the metadata space in the storage pool created in the local storage system. Metadata occupies merely a small amount of
space. Therefore, eDevLUNs occupy a small amount of space in the local storage system.
(Optional) Task 4: Managing Heterogeneous Storage
System Resources in a Centralized Manner
 Establish the mapping between eDevLUNs and application servers.
 (Optional) Scan for LUNs on the application server.
Question
 After the eDevLUN takes over online services, if the original storage device is
faulty (unavailable), will the online services of the application server be
affected?
 Yes, the online services of the application server will be affected. The eDevLUN
involves the metadata space and data space. The data space is on the original
storage device. If the original storage device is faulty (unavailable), the data space of
the eDevLUN is unavailable, and services on the application server are interrupted.
Scenario 2: Migrating Services from Heterogeneous
Storage Systems
Task 1 Task 2
Migrating (Optional) Taking

LUNs Over Services
Question
 How is load balancing implemented for SmartVirtualization?
 Load balancing within a controller and load balancing between controllers are enabled by
default. Users can modify the heterogeneous storage device whitelist to set the path selection
algorithm to define the load balancing policy of the storage device.
 A heterogeneous device whitelist is a list of Huawei's or third-party vendors' devices that
Huawei storage devices can take over. You can configure the whitelist to set the path selection
algorithm used by the local storage device to take over heterogeneous storage devices as well
as failover and failback policies.
Task 1: Migrating LUNs
 Configure SmartMigration.
 Delete a SmartMigration task.
(Optional) Task 2: Taking Over Services
 (Optional) Create the mapping between the application server and the target
LUN.
 (Optional) Use the target LUN on the application server.
Question
 What can I do if a fault (for example, the source LUN or target LUN is faulty)
occurs during LUN migration? What will be done after the fault is rectified?
 When a LUN migration task is interrupted, I/Os are written only to the source LUN
and the data difference is recorded. (If the source LUN is faulty, the source LUN
cannot receive I/O requests from the production host.) After the fault is rectified, the
LUN migration task automatically enters the migrating state, and data is
synchronized to the target LUN in resumable mode. You do not need to manually
resume the task.
Discussion
 Think and discuss how to use Huawei all-flash storage devices to take over
third-party storage devices in offline mode. You can draw a flowchart to
describe the process.
 Note: If conditions permit, you can perform an experiment to verify the result.
intelligent world.


portfolio, new technology, etc. There are a number of factors
that
HCIP-Storage
Distributed Storage
Technology Application
(For Trainees)
1
Notice


HCIP-Storage Scenario-based Practice of Distributed Storage
Technology Application Page 1

which is a new collaborative architecture of ICT infrastructure based on "Cloud-Pipe-
Terminal". Huawei has set up a complete certification system comprising three
categories: ICT infrastructure, Platform and Service, and ICT vertical. Huawei's technical
certification system is the only one in the industry covering all of these fields.
troubleshooting.
industry peers.


Contents
Contents.................................................................................................................................... 3
1.1 References...........................................................................................................................................................................4
1.2 Software Tools ...................................................................................................................................................................4
2 Scenario-based Practice of Distributed Storage Technology Application................. 6
2.1 Course Overview ...............................................................................................................................................................6
2.2 Objectives............................................................................................................................................................................6
2.3 Case Background ..............................................................................................................................................................6
2.4 Tasks.....................................................................................................................................................................................7
2.4.1 Scenario 1: Storage Initialization ..............................................................................................................................7
2.4.2 Scenario 2: Service Configuration .......................................................................................................................... 10

1.1 References
The commands and documents listed in this document are for reference only. The actual
commands and documents may vary.
Huawei OceanStor Distributed Storage Product Documentation
Note:
The features supported by Huawei OceanStor distributed storage products vary by model.
For details, see the product documentation of the desired product model. You can log in
to Huawei's technical support website (https://support.huawei.com/enterprise/) and use
the search box to find and download the desired document or tool.
1.2 Software Tools

Note:
(https://support.huawei.com/enterprise/) and search UltraPath to find and download the
2. Huawei OceanStor DeviceManager Demo for distributed storage
Note:

Recommended
Storage system Huawei OceanStor distributed storage 1
version
Windows OS Windows Server 2012 or Windows - Recommended

Server 2016 version
Recommended
Linux OS SUSE, Red Hat, CentOS, or EulerOS -
version
UltraPath 21.6.3 -
software version

2 Scenario-based Practice of Distributed

Storage Technology Application
2.1 Course Overview

their knowledge of initial configuration and basic service deployment and
implementation of Huawei OceanStor distributed storage.
2.2 Objectives
 To understand common networking modes for distributed storage services
 To complete the initial configuration of the distributed storage system
 To plan and configure block services
 To plan and configure object services
 To plan and configure HDFS services
2.3 Case Background

Note:
Cases in this document are examples only. The actual configurations may vary according
to actual environments. For details, see the corresponding product documentation.
To build a new service line, company W needs to add a distributed storage system for e-
commerce transaction database services, online videos, file sharing, and big data
analytics. After market surveys, company W decides to purchase a set of Huawei
OceanStor distributed storage equipment to build its service system. The company also
purchases licenses for block services, object services, and HDFS services.
As a storage engineer, you are responsible for network planning and design, initial
configuration, and service configuration of the storage system.

2.4 Tasks
2.4.1 Scenario 1: Storage Initialization
2.4.1.1 Background
Huawei OceanStor distributed storage equipment purchased by company W has been
delivered. How can the storage engineer install hardware and software?
2.4.1.2 Question
What do we need to prepare for hardware installation?
2.4.1.3 Task 1: Installing Devices

Step 1 Check the process.
Output the overall hardware installation process to ensure smooth device installation.
Step 2 Learn about the network planes.
What are the network planes for distributed storage? Mark the different types of network
planes in following the graph.

2.4.1.4 Question
What are the installation modes for distributed storage products?
2.4.1.5 Task 2: Installing Software

Step 1 Learn about the operations.
Which of the following operations involved in distributed storage software installation?
For details, see Installation > Installing the Object Service > Installing OceanStor 100D
Software in the product documentation.
Step 2 Install a management node.
Sort out the following rocesses, draw a flowchart of installing the management nodes.

Step 3 Add storage nodes.
Add 100 storage nodes in a batch by using a template.
Software > Adding Storage Nodes in the product documentation.
Step 4 Configure the storage network.
Configure storage IP addresses for nodes using the IP addresses provided in the template.
Software > Configuring the Storage Network in the product documentation.
Step 5 Install storage nodes.
Complete storage node installation as instructed by the wizard.
Software > Installing Storage Nodes in the product documentation.
Step 6 Create a control cluster.
Create a control cluster named SDSCluster.

Software > Creating a Control Cluster in the product documentation.
2.4.1.6 Question
What are the deployment modes for block services?
For details, see Installation > Software Installation Guide > Block Service Node
Requirements in the product documentation.
2.4.1.7 Task 3: Obtaining and Loading a License

Step 1 Import the license file.
Import and activate a license and view license information.
For details, see Installation > Installing the Object Service > Obtaining and Loading a
License in the product documentation.
2.4.2 Scenario 2: Service Configuration

2.4.2.1 Background
After installing and initializing devices, configure basic services of the storage system
based on customer requirements. The detailed requirements are as follows.
Service Storage Service

Resource Usage Feature
Name Resource Application
Block Volume 1: 100 GB

Database Linux + MySQL HyperSnap
service Volume 2: 50 GB
Online Object Per account: 10 SmartQuota and

Web application
video service GB SmartDedupe
A maximum of
five subdirectories
Big data HDFS can be created in
Hadoop SmartTier
analytics service /hdfs. The
directory capacity
quota is 100 GB.

2.4.2.2 Task 1: Configuring the Block Service

Configure block service storage resources based on customer requirements.
Step 1 Check the license file.
For details, see Configuration > Basic Block Service Configuration Guide > Configuring
Basic Storage Services > Checking License Files in the product documentation.
Note:
If you use the Demo, create a non-empty file named license.dat.
The example only shows how to input information. The actual information may vary
according to actual environments.
Step 2 Allocate storage space.
Create Volume 1 (100 GB) and Volume 2 (50 GB), and map them to database servers
using iSCSI.
Basic Storage Services > Allocating Storage Space (iSCSI Protocol-VMware/Hyper-
V/Linux/Windows) in the product documentation.
Note:
Creating a storage pool and creating a VBS do not conflict. You can create either first.
This document uses creating a storage pool first as an example.
Step 3 Create snapshots.
Create snapshot Vol1snap for Volume 1 and snapshot Vol2snap for Volume 2.

For details, see Configuration > Block Service Feature Guide > HyperSnap > Creating a
Snapshot in the product documentation.
[Suggested Answer]
The snapshots are created successfully.
2.4.2.3 Question
How do I mount storage volumes to a Linux host and use them for databases?
Basic Storage Services > Allocating Storage Space (iSCSI Protocol-VMware/Hyper-
V/Linux/Windows) in the product documentation.
2.4.2.4 Task 2: Configuring the Object Service

Configure object service storage resources using single-region scenarios based on
customer requirements.
Step 1 Import an object service package.
For details, see Installation > Software Installation Guide > Installing the Object Service >
Initializing the Object Service > Importing an Object Service Package in the product
documentation.
Note:
When using DeviceManager Demo, create a non-empty file named
OceanStor_DS_OBS_version.tar.gz.
If an object service package has been imported during management node installation,
skip this step.
Step 2 Create a storage pool.

a Set the name to objectpool.

b Set the service type to object.
c Set the security level to node.
d Set the redundancy policy to EC and the parity fragments to +2.
e Set the disk pool name to objhdpool and select 20 nodes.
Initializing the Object Service > Creating a Storage Pool in the product documentation.
Step 3 Configure networks.
a Set the transmission protocol to TCP and the bond mode to bond4.
b Set the IP address segment to 10.44.44.0/24.
c Set the ports to phy3 and phy4.
Initializing the Object Service > Configuring Networks in the product documentation.
Step 4 Configure a region.
a Select the single-region scenario and set the global domain name to objglobal.com.
b Set the object service cluster name to objcluster.
c Set the authentication type to POE.
Initializing the Object Service > Configuring a Region in the product documentation.
Step 5 Configure the DNS service.

a Automatically create the DNS service for object services.

b Set the LS domain name to portal.objglobal.com.
c Set the POE service domain name to poe.objglobal.com.
For details, see Configuration > Basic Object Service Configuration Guide > Configuring
Basic Services > Configuring the DNS Service in the product documentation.
[Suggested Answer]
The settings are saved successfully with no error reported.
Step 6 Create account resources.
a Set both the account ID and name to objuser.

b Set the bucket name, parity fragments, and total quota to obj001, 2, and 2 TB,
respectively.
c Set the bucket permission to public read.
d Create a user named objtest and user certificates. Create a user policy named
objtestpolicy and set the policy mode to read-only.
Basic Services > Creating Account Resources in the product documentation.
Step 7 Enable the deduplication function for an account.
Basic Services > Enabling the Deduplication Function for an Account in the product
documentation.

2.4.2.5 Task 3: Configuring the HDFS Service

Configure HDFS service storage resources based on customer requirements.
Step 1 Create a storage pool.
a Set the storage pool name to bigdatapool.

b Set the service type to HDFS.
c Set the security level to node.
d Set the redundancy policy to EC and the parity fragments to +2.
e Set the disk pool name to bigdatahdpool and select 20 nodes.
For details, see Configuration > Basic HDFS Service Configuration Guide > Configuring
Basic Services > Creating an HDFS Storage Pool in the product documentation.
Step 2 Create an account.
Set the account name to bigdatauser.
Basic Services > Creating an Account in the product documentation.
Step 3 Create a file system.
Create a file system named bigdatafs for the account bigdatauser.
Basic Services > Creating a File System in the product documentation.
Step 4 Create a subnet.

a Set the subnet name to bigdatasubnet.

b Set the IP address type to IPv4.
c Set the subnet gateway and subnet mask to 10.44.45.1 and 24, respectively.
d Set the IP address of the DNS service to 10.44.45.10.
e Set the root domain name to bigdata.bdglobal.com.
Basic Services > Configuring a Service Network > Creating a Subnet in the product
documentation.
Step 5 Create a global zone.
a Set the sub-domain name to gz.

b Set the polling mode to the number of node connections.
c Enable the DNS service.
d Set the IP address range to 10.44.45.20/24-10.44.45.50/24.
Basic Services > Configuring a Service Network > Creating a Global Zone in the product
documentation.
Step 6 Create a NameNode zone.
a Set the NameNode zone name to bigdatanz and the sub-domain name to nz.
b Set the associated file system to bigdatafs.
c Set the DNS policy to CPU usage.
d Set the IP address range to 10.44.45.60/24-10.44.45.70/24.

Basic Services > Configuring a Service Network > Creating a NameNode Zone in the

My Opinion：
_________________________________________________________________________________________
_________________________________________________________________________________________
__________________________________________________________________

Scenario-based Practice of Distributed Storage
Technology Application
Background
 To build a new service line, company W needs to add a distributed storage
system for e-commerce transaction database services, online videos, file sharing,
and big data analytics. After market surveys, company W decides to purchase a
set of Huawei OceanStor distributed storage equipment to build its service
system. The company also purchases licenses for block services, object services,
and HDFS services.
 As a storage engineer, you are responsible for network planning and design,
initial configuration, and service configuration of the storage system.
Practice Mode
Objectives Form
• To be able to plan and design typical • Trainees split into groups of two or three.
networks • Each group prepares materials for
• To be able to complete initial configuration presentation.
and service configuration and deployment for • After each presentation, the technical officer
Huawei distributed storage asks questions, and the evaluator gives
feedback and scores.
Opinion
Sharing
Scenario 1: Storage Initialization
Install Install software Perform

devices initialization
Question
 What do I need to prepare for hardware installation?
 Hardware installation preparations include but are not limited to the following:
 Technical document preparations, tool and instrument preparations, installation
environment check, and device specifications confirmation.
Task 1: Installing Devices
 Check the process.
 Learn about the network planes.
Check the Process
 How do I design the overall hardware installation process to ensure smooth
device installation?
Install components
Start inside cabinets.
Install PGND and power cables for

Prepare for installation. components.
Unload and carry the Install signal cables.

equipment.
Perform unpacking and

Check installation.
acceptance.
Are Huawei Yes Install corresponding Install filler panels of

cabinets used？ cabinets. cabinets.
No Check third-party Power on equipment.

cabinets.
End
Learn About the Network Planes
Management
 What are the network Clients Terminals
Application Servers
planes for distributed
1.
1. Service
storage? Mark the
network 2.
2.BMC/Manage
different types of ment network
network planes in
following the graph
……
Storage Storage Storage Storage

Nodes Nodes Nodes Nodes
3. Storage
network
Question
 What are the installation modes for distributed storage products?
 Suggested Answer:
 Storage delivery includes two modes: software and hardware integration and software and
hardware separation.
 In the integration mode, the OS and drivers are preinstalled before delivery. When the versions
of the OS and related drivers are consistent with those in the version mapping, you do not
need to install the OS separately. You can directly install OceanStor 100D software using
DeviceManager Client. If the versions of the OS and drivers are different from those in the
version mapping, reinstall the OS and drivers on each node.
 In the separation mode, you need to install the OS and drivers on each node manually.
Task 2: Installing Software
 Learn about the operations.
 Install a management node.
 Add storage nodes.
 Configure the storage network.
 Install storage nodes.
 Create a control cluster.
Learn about the Operations
 Which of the following operations involved in distributed storage software
installation?
Installing Management Nodes Installing Storage Nodes
Creating a Control Cluster Allocating Storage Space
Install a Management Node
 Sort out the following rocesses, draw a flowchart of installing the management
nodes.
Start
Open DeviceManager Client.
Enter the information about the management node.
Click Add Management Node.
Upload installation packages.
Configure the management node.
End
Question
 What are the deployment modes for block services?
 Suggested Answer:
 Converged deployment of compute and storage nodes and separated deployment of
compute and storage nodes
Task 3: Obtaining and Loading a License
 Import the license file.
Scenario 2: Service Configuration
Configure the Configure the Configure the

block service object service HDFS service
Background
 After installing and initializing devices, configure basic services of the storage
system based on the following customer requirements.
Storage
Service Name Service Application Resource Usage Feature
Resource
Volume 1: 100 GB
Database Block service Linux + MySQL HyperSnap
Volume 2: 50 GB
SmartQuota and
Online video Object service Web application Per account: 10 GB
SmartDedupe
A maximum of five
subdirectories can be
Big data
HDFS service Hadoop created in /hdfs. The SmartTier
analytics
directory capacity quota
is 100 GB.
Task 1: Configuring the Block Service
 Check the license file.
 Allocate storage space.
 Create snapshots.
Question
 How do I mount storage volumes to a Linux host and use them for databases?
 Discover the iSCSI storage: iscsiadm -m discovery -t st -p ISCSI_IP
 View iSCSI discovery records: iscsiadm -m node
 Delete iSCSI discovery records: iscsiadm -m node -o delete -T LUN_NAME -p
ISCSI_IP
 Log in to the iSCSI storage: iscsiadm -m node -T LUN_NAME -p ISCSI_IP -l
 Log out of the iSCSI storage: iscsiadm -m node -T LUN_NAME -p ISCSI_IP -u
Task 2: Configuring the Object Service
 Import an object service package.
 Create a storage pool.
 Configure networks.
 Configure a region.
 Configure the DNS service.
 Create account resources.
 Enable the deduplication function for an account.
Task 3: Configuring the HDFS Service
 Create a resource pool.
 Create an account.
 Create a file system.
 Create a subnet.
 Create a global zone.
 Create a NameNode zone.
Trainee Assessment

complete.

the specified time.
Overall /
intelligent world.


HCIP-Storage
Storage Maintenance and
Troubleshooting
(For Trainees)

All other trademarks and trade names mentioned in this document are the property
of their respective holders.
Notice
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.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129

HCIP-Storage Scenario-based Practice of Storage Maintenance
and Troubleshooting Page 1

which is a new collaborative architecture of ICT infrastructure based on "Cloud-Pipe-
Terminal". Huawei has set up a complete certification system comprising three
categories: ICT infrastructure, Platform and Service, and ICT vertical. Huawei's technical
certification system is the only one in the industry covering all of these fields.
troubleshooting.
industry peers.


Contents

1.1 References.......................................................................................................................................................................... 4
1.2 Software Tools .................................................................................................................................................................. 4
2 Scenario-based Practice of Storage Maintenance and Troubleshooting ..................5
2.1 Course Overview .............................................................................................................................................................. 5
2.2 Objectives........................................................................................................................................................................... 5
2.3 Case Background ............................................................................................................................................................. 5
2.4.1 Scenario 1: Routine Maintenance ............................................................................................................................ 6
2.4.2 Scenario 2: Troubleshooting .................................................................................................................................... 10
3 Teaching Guidance .................................................................................错误!未定义书签。

3.1 Training Procedure .......................................................................................................................... 错误!未定义书签。
3.2 Grouping ............................................................................................................................................ 错误!未定义书签。
3.3 Auxiliary Materials and Tools ....................................................................................................... 错误!未定义书签。
3.4 Trainee Assessment......................................................................................................................... 错误!未定义书签。
3.5 Assessment Form ............................................................................................................................. 错误!未定义书签。

1.1 References
The commands, documents, and document paths listed in this document are for
reference only. The actual commands, documents, and document paths may vary.
Note:
The specifications of a storage device vary with product models. For details, see the
product documentation of the desired product model. You can log in to Huawei's
technical support website (https://support.huawei.com/enterprise/) and use the search
box to find and download the desired document or tool.
1.2 Software Tools

PuTTY
Note:
You are advised to use the open-source software PuTTY to log in to a terminal. You can
visit its public website (putty.org) to find and download the desired document or tool.

Huawei OceanStor Dorado V6

Storage system 1
6.0.1
Windows Server 2012 or

Windows OS - Recommended version
Windows Server 2016

2 Scenario-based Practice of Storage

Maintenance and Troubleshooting
2.1 Course Overview

their knowledge of routine maintenance and troubleshooting of storage devices.
2.2 Objectives
 To be able to perform routine maintenance and management on physical devices.
 To be able to inspect hardware faults of physical devices and collect relevant
information.
 To be able to troubleshoot common hardware faults of physical devices.
2.3 Case Background

Note:
Cases in this document are examples only. The actual configurations may vary according
to actual environments. For details, see the corresponding product documentation. The
names in this document can be customized (for example, LUN_XXX) for different trainees
if they use the same device.
After one month of intensive implementation, integrator A finally helped enterprise B
complete the deployment and configuration of a service system. According to the
contract delivery requirements, integrator A needs to hand over the O&M work to the IT
O&M team of enterprise B. The following figure shows the network topology of the
enterprise.

Figure 2-1 Network topology

2.4.1 Scenario 1: Routine Maintenance
2.4.1.1 Background
After OceanStor Dorado is deployed, O&M engineer E of the enterprise needs to master
routine maintenance and management operations on storage devices as soon as possible,
so that engineer E can efficiently maintain storage devices in case of service changes or
O&M needs.
2.4.1.2 Question
What items of a storage system need to be managed and maintained during the routine
maintenance and management work of the system administrator? What is the
maintenance cycle of each item?
2.4.1.3 Task 1: Inspecting Storage Devices

Routine maintenance allows you to check whether the device environment and device
status are normal and handle exceptions in a timely manner to ensure that storage
devices can run properly.
Step 1 Inspect storage devices using SmartKit.
Install the SmartKit inspection tool on the maintenance terminal and instruct engineer E
to inspect storage devices using SmartKit.

For details, see section "Operation and Maintenance > Administrator Guide > Routine
Maintenance > Inspection Using SmartKit" in the product documentation.
Step 2 View and handle alarms.
Detailed descriptions and rectification suggestions provided to each alarm in the alarm
list can help engineers rectify alarms of the storage system to ensure proper running of
devices and services.
Maintenance > Manual Inspection > Viewing and Handling Alarms" in the product
documentation.
Step 3 Collect storage system information.
Instruct engineers to collect storage system information. If a fault occurs, engineers can
promptly collect and report basic information, fault information, as well as storage
device, network, and application server information to help maintenance engineers
quickly locate and rectify faults.
Maintenance > Collecting Storage System Information > Collecting Logs and Alarms
Using DeviceManager" in the product documentation.
2.4.1.4 Question
What operations are required if a feature of the storage system is unavailable?
2.4.1.5 Task 2: Routine Management

After the preparations are complete, instruct engineers to configure system security
policies to improve system security. The following table lists the required configurations
according to the O&M requirements.

No. Operation Item Configuration Requirement
1. Import a license file.

License
1 2. Activate the license.
management
3. Back up the license.
1. Configure an account policy. In this policy, the

password validity period is 90 days and a warning
message is sent 7 days before password expiration.
The minimum length of the user name is 6
characters, and the password length is 8 to 16
2 User and security characters.
2. Configure a login policy. In this policy, the session
timeout duration is 30 minutes, the account is
locked after three consecutive incorrect password
attempts, and the account is automatically unlocked
in 5 minutes.
Set alarm notification information, including:

1. IP address of the SMTP server: 1.1.1.1
3 Alarm settings 2. Email address of the sender: send@test.com
3. Email address of the recipient: recieve@test.com
4. Receive only major and critical information.
Configure an SNMP security policy containing the

following information:
1. Minimum password length: 4
2. Maximum password length: 16
SNMP
4 3. Password complexity: Normal
management
4. Statistic collection interval of authentication failures:
100s
5. Allowed consecutive authentication failures: 5
6. IP address lockout time: 300s
1. Permit information upload to eService.

2. eService site: Enterprise in Chinese mainland
5 eService settings
3. Site name: test
4. Add a contact.
Step 1 Manage license files.
License files are authority credentials for value-added features of a storage device.
During routine maintenance, check that license files are available for their value-added
features. Instruct engineers to view and back up license files.

Management > Managing License Files" in the product documentation.
Step 2 Create a local user.
The O&M team needs to create different levels of users based on service requirements.
Instruct engineers to create a local user test, set the password to Huawei@123, set the
role to Administrator, allow all login methods, and set login authentication to Login
password.
Management > Managing Access Permissions of a Storage System > Managing Users >
Creating a Local User" in the product documentation.
Step 3 Configure security policies.
Configure account policies and login policies based on O&M requirements.
Management > Managing Access Permissions of a Storage System > Configuring Security
Policies" in the product documentation.
Step 4 Configure trap notifications.
Assist engineers in configuring SNMP security policies and trap notifications based on
O&M requirements.

Management > Managing Alarms and Events" in the product documentation.
Step 5 Configure the eService.
Assist engineers in configuring and managing the eService based on O&M requirements.
Management > Enabling and Managing the eService" in the product documentation.
2.4.1.6 Question
How do I use DeviceManager to monitor the performance of a storage device?
2.4.2 Scenario 2: Troubleshooting

2.4.2.1 Background
Storage engineers need to master troubleshooting operations on storage devices. Help
engineers get familiar with the troubleshooting process and common troubleshooting
methods.
2.4.2.2 Task 1: Handling Disk Module Faults

Step 1 Check indicators on the disk module.
Log in to DeviceManager and check indicators on the disk module.
For details, see section "Troubleshoot > Troubleshooting > Emergency Handling >
Emergency Handling of Hardware Module Faults > Disk Failure" in the product
documentation.
Step 2 Collect storage system fault information.
Log in to DeviceManager and collect alarms and events of the storage system.

For details, see section "Troubleshoot > Troubleshooting > Collecting Information and
Reporting a Fault" in the product documentation.
2.4.2.3 Question 1
How do I handle faults after fault information is collected?
Step 1 Check whether the Alarm/Location indicator of the disk module on the storage
device is steady yellow.
If yes, go to step 2.
If no, keep the fault environment intact and contact Huawei technical support.
Step 2 Remove and reinsert the disk module.
After the disk module is reinserted, check whether the Alarm/Location indicator of the
disk module is steady off and Health Status of the disk module on DeviceManager is
Normal.
If yes, no further action is required.
If no, go to step 3.
Step 3 Replace the faulty disk module.
2.4.2.4 Question 2
What preparations are required before spare parts replacement?

My Opinion：

Scenario-based Practice of Storage
Maintenance and Troubleshooting
Background
 After one month of intensive implementation, integrator A finally helped enterprise B complete the
deployment and configuration of a service system. According to the contract delivery requirements, integrator
A needs to hand over the O&M work to the IT O&M team of enterprise B. The following figure shows the
network topology of the storage system.
Huawei OceanStor All-

Flash Storage
Practice Mode
Objectives Form
• To be able to perform routine maintenance • Trainees split into groups of two or three.
and management on physical devices. • Each group prepares materials for
• To be able to inspect hardware faults of presentation.
physical devices and collect relevant • After each presentation, the technical
information. officer asks questions, and the evaluator
• To be able to troubleshoot common gives feedback and scores.
hardware faults of physical devices.
Opinion
Sharing
Scenario 1: Routine Maintenance
Task 1 Task 2
Inspecting storage Routine

devices management
Question
 What items of a storage system need to be managed and maintained during
the routine maintenance and management work of the system administrator?
What is the maintenance cycle of each item?
Suggested answer:
 The system administrator can check the device environment and device status
according to the list of maintenance items and their cycles. If an exception
occurs, the system administrator can handle the exception in a timely manner
to ensure continuous and healthy running of the storage system.
Task 1: Inspecting Storage Devices
 Inspect storage devices using SmartKit.
 View and handle alarms.
 Collect storage system information.
Question
 What operations are required if a feature of the storage system is unavailable?
Suggested answer:
 If you find that a feature such as remote replication is unavailable when
checking the license information, import the license of the remote replication
feature to the storage system and activate the license.
Task 2: Routine Management
 Manage license files.
 Create a local user.
 Configure security policies.
 Configure trap notification.
 Configure eService.
Question
 How do I use DeviceManager to monitor the performance of a storage device?
Suggested answer:
 You can monitor and view performance data to know system performance and
apply optimization configurations to improve system performance.
 You can use DeviceManager to monitor the performance of storage devices. You
do not need to install DeviceManager separately. After logging in to
DeviceManager through a web browser on the maintenance terminal, you can
check the real-time performance data, alarms, and power consumption of
storage systems.
Scenario 2: Troubleshooting
 Help engineers get familiar with the troubleshooting process and common
troubleshooting methods.
Scenario 2: Troubleshooting
Handling disk Question 1 Question 2

module faults
Task 1: Handling Disk Module Faults
 Check indicators on the disk module.
 Collect storage system fault information.
Question 1
 How do I handle faults after fault information is collected?
Suggested answer:
If a disk module is faulty, the disk domain where the disk module resides will be degraded or faulty. If the disk
domain is degraded, the read/write performance of the system will deteriorate and data may be lost. If the disk
domain is faulty, data in the disk domain will be lost and services will be interrupted. The following describes the
troubleshooting process for a disk module failure.
1. Check whether the Alarm/Location indicator of the disk module on the storage device is steady yellow.
If yes, go to step 2.
If no, keep the fault environment intact and contact Huawei technical support.
2. Remove and reinsert the disk module.
After the disk module is reinserted, check whether the Alarm/Location indicator of the disk module is steady
off and Health Status of the disk module on DeviceManager is Normal.
If yes, no further action is required.
If no, go to step 3.
3. Replace the faulty disk module.
Question 2
 What preparations are required before spare parts replacement?
Suggested answer:
Requirements on maintenance personnel
The maintenance personnel must have an understanding of:
 Storage technologies such as redundant array of independent disks (RAID), network attached storage (NAS),
direct attached storage (DAS), and storage area network (SAN)
 Ethernet technologies
 TCP/IP basics
 Components of storage devices at the deployment site
 Using tools and instruments
 Confirming the IDs of spare parts
Trainee Assessment

complete.

the specified time.
Overall /
intelligent world.



HCIP-Storage V5.0 Lab Guide

Uploaded by

Copyright:

Available Formats

HCIP-Storage V5.0 Lab Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HCIP-Storage V5.0 Lab Guide

Uploaded by

Copyright:

Available Formats

Huawei Storage Certification Training

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

Huawei Certification System

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1 References and Tools ..........................................................................................................4

Huawei Proprietary and Confidential

1 References and Tools

1.2 Software Tools

1.3 Operating Environment

Storage system Huawei OceanStor Dorado V6 2

Windows Server 2012 or

Huawei Proprietary and Confidential

2 Scenario-based Practice of Flash

2.1 Course Overview

2.3 Case Background

Huawei Proprietary and Confidential

2.4 Tasks and Suggested Answers

2.4.1.3 Task 1: Configuring UltraPath

Step 1 Streamline the process.

Step 2 Prepare for the installation.

Huawei Proprietary and Confidential

Step 3 Install and configure UltraPath.

Huawei Proprietary and Confidential

Step 4 Verify the installation.

2.4.1.5 Task 2: Managing UltraPath

Step 1 View array information.

Huawei Proprietary and Confidential

Step 2 View physical path information.

Step 3 Manage critical events.

Step 4 (Optional) Upgrade or uninstall UltraPath.

Huawei Proprietary and Confidential

2.4.2 Scenario 2: Basic NAS Configuration

2.4.2.3 Task 1: Initial Configuration

Basic Information Example

Device Time 2020-07-24 10:22:59 UTC+08:00 (Beijing,

Huawei Proprietary and Confidential

Name, Capacity Alarm Threshold (%), and

2.4.2.5 Task 2: Configuring Basic Storage Services

Step 1 Perform check before configuration.

Huawei Proprietary and Confidential

Step 2 Log in to DeviceManager and create a storage pool.

Step 3 Create a file system.

Step 4 (Optional) Create a dtree.

Step 5 Create a quota.

Huawei Proprietary and Confidential

2.4.2.7 Task 3: Configuring an NFS Share

Step 1 Configure the network.

Step 2 Create an NFS share.

Huawei Proprietary and Confidential

Step 3 Add an NFS share client.

Step 4 Access an NFS share.

Huawei Proprietary and Confidential

2.4.2.9 Task 4: Configuring a CIFS Share

Step 1 Configure a network.

Step 2 Create a local authentication user.

Step 3 Add a storage system to an AD domain.