Hypermetro Configuration Guide For Huawei San Storage Using Os Native Multipathing Software

HyperMetro Configuration Guide
for Huawei SAN Storage Using OS

Native Multipathing Software
Issue 13
Date 2020-06-30
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: https://e.huawei.com
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. i

HyperMetro Configuration Guide for Huawei SAN
Storage Using OS Native Multipathing Software About This Document
About This Document
Overview
This document describes how to configure storage systems and multipathing
software for the SAN HyperMetro solution when the host uses OS native
multipathing software.
Intended Audience
This document is intended for:
● Huawei storage technical support engineers
● Technical engineers of Huawei's partners
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if

not avoided, will result in death or serious injury.
Indicates a hazard with a medium level of risk which,

if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if

not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation which, if

not avoided, could result in equipment damage, data
loss, performance deterioration, or unanticipated
results.
NOTICE is used to address practices not related to
personal injury.
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. ii

Storage Using OS Native Multipathing Software About This Document
Symbol Description
Supplements the important information in the main

text.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
CLI Format Conventions

Format Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iii

Storage Using OS Native Multipathing Software Contents
Contents
About This Document................................................................................................................ ii

1 Impact and Restrictions......................................................................................................... 1
1.1 HyperMetro Working Modes............................................................................................................................................... 1
1.1.1 Working Principles and Failover..................................................................................................................................... 2
1.2 Initiator Modes......................................................................................................................................................................... 3
1.2.1 Initiator Parameter Description...................................................................................................................................... 3
1.2.2 Configuring the Initiators.................................................................................................................................................. 6
1.3 Networking Requirements................................................................................................................................................... 8
1.4 Compatibility............................................................................................................................................................................. 8
2 Windows.................................................................................................................................... 9
2.1 Precautions................................................................................................................................................................................ 9
2.2 Configuring Storage Arrays.................................................................................................................................................. 9
2.2.1 Non-NPIV Mode................................................................................................................................................................... 9
2.2.2 NPIV Mode........................................................................................................................................................................... 14
2.2.3 iSCSI Networking............................................................................................................................................................... 19
2.3 Configuring the Host........................................................................................................................................................... 19
2.3.1 Version and Patch Requirements................................................................................................................................. 19
2.3.2 Configuring Multipathing Software............................................................................................................................ 20
2.3.3 Configuring HBAs.............................................................................................................................................................. 27
2.3.4 Configuring Registries...................................................................................................................................................... 29
3 XenServer................................................................................................................................ 30
3.1 Precautions.............................................................................................................................................................................. 30
3.2 Configuring Storage Arrays............................................................................................................................................... 30
3.4 Verifying the Configurations............................................................................................................................................. 36
3.4.1 Checking the Multipathing Software Status............................................................................................................ 36
3.4.2 Verifying Path Information.............................................................................................................................................36
4 HP-UX....................................................................................................................................... 38
4.1 Precautions.............................................................................................................................................................................. 38
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iv


5 Red Hat.................................................................................................................................... 41
5.1 Precautions.............................................................................................................................................................................. 41
6 Oracle VM............................................................................................................................... 46
6.1 Precautions.............................................................................................................................................................................. 46
7 SLES.......................................................................................................................................... 49
7.1 Precautions.............................................................................................................................................................................. 49
7.2 Configuring the Storage Arrays........................................................................................................................................49
8 RHV........................................................................................................................................... 55
8.1 Precautions.............................................................................................................................................................................. 55
8.4.1 Checking the Multipathing Software Status............................................................................................................ 58
8.4.2 Verifying Path Information.............................................................................................................................................58
9 Rocky........................................................................................................................................ 60
9.1 Precautions.............................................................................................................................................................................. 60
10 NeoKylin................................................................................................................................ 63
10.1 Precautions........................................................................................................................................................................... 63
10.2 Configuring Storage Arrays............................................................................................................................................. 63
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. v

10.3 Configuring the Host......................................................................................................................................................... 64

10.3.1 Version and Patch Requirements............................................................................................................................... 64
10.3.2 Configuring Multipathing Software.......................................................................................................................... 65
10.3.3 Configuring HBAs............................................................................................................................................................ 65
11 Solaris.................................................................................................................................... 66
11.1 Precautions........................................................................................................................................................................... 66
11.4 Verifying the Configurations...........................................................................................................................................68
12 Asianux.................................................................................................................................. 71
12.1 Precautions........................................................................................................................................................................... 71
12.4.1 Checking the Multipathing Software Status..........................................................................................................73
12.4.2 Verifying Path Information.......................................................................................................................................... 73
13 Ubuntu................................................................................................................................... 75
13.1 Precautions........................................................................................................................................................................... 75
14 VMware................................................................................................................................. 78
14.1 Precautions........................................................................................................................................................................... 78
14.3.2 Setting Timeout Parameters....................................................................................................................................... 82
14.3.3 Configuring a VMware Cluster................................................................................................................................... 82
14.4.1 Verifying the Multipathing Software Status and Path Information.............................................................. 87
15 AIX.......................................................................................................................................... 89
15.1 Precautions........................................................................................................................................................................... 89
16 FusionCompute.................................................................................................................... 93
16.1 Precautions........................................................................................................................................................................... 93
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vi


16.4.1 Checking the Multipathing Software Status..........................................................................................................96
16.4.2 Verifying Path Information.......................................................................................................................................... 96
17 FAQs....................................................................................................................................... 98
17.1 How Do I Determine Whether the HBA Parameters Configured for the Multipathing Software Have
Taken Effect?................................................................................................................................................................................. 98
17.2 Why Does the Multipathing Software Automatically Return to Its Initial Configuration Every Time
RHV-H Restarts?......................................................................................................................................................................... 100
17.3 Why Does SLES Enter Emergency Mode After the Multipathing Software Is Configured?................... 100
17.4 Why Does the Old Path Information Remain After an HBA Is Replaced on a XenServer Host?......... 101
17.5 What Can I Do If I/Os on a VMware 6.0 Host Are Interrupted After the Replication Link Between the
Storage Systems Goes Down?............................................................................................................................................... 102
17.6 What Can I Do If Links Are Not Aggregated in Linux Due to the Multipathing Software Anomaly?
......................................................................................................................................................................................................... 102
18 Acronyms and Abbreviations......................................................................................... 104
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vii

Storage Using OS Native Multipathing Software 1 Impact and Restrictions
1 Impact and Restrictions
HyperMetro using the native multipathing software of an operating system (OS)

must be implemented using Asymmetric Logical Unit Access (ALUA). The initiators
on the storage systems must be configured with a switchover mode that supports
Huawei's HyperMetro ALUA. These modes include the common ALUA mode and
all special modes.
ALUA is a multi-target port access model that provides a way of presenting active/
standby LUNs to a host and offers an interface for switching over a LUN's owning
controller based on its port status. For example, when the ALUA-supporting
multipathing software on a host detects a change in port status (such as the port
becoming unavailable) on a faulty controller, it will automatically switch
subsequent I/Os to the other controller.
1.1 HyperMetro Working Modes
1.2 Initiator Modes
1.3 Networking Requirements
1.4 Compatibility
1.1 HyperMetro Working Modes

Typically, HyperMetro works in either load balancing mode or local preferred
mode. The typical working modes are valid only when both the storage system
and host use ALUA. You are advised to set the host's path selection policy to
round-robin (this must be round-robin if HyperMetro works in load balancing
mode). If the host does not use ALUA or its path selection policy is not round-
robin, the host's multipathing policy determines the working mode of HyperMetro.
HyperMetro storage arrays can be classified into a local and a remote array by
their physical distance to the host. The one closer to the host is the local array and
the other is the remote array.
Table 1-1 describes the configuration methods and application scenarios of the
typical working modes.
Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 1

Table 1-1 HyperMetro working modes

Working Mode Configuration Method
Load balancing mode Enable ALUA on the host and set the path selection
policy to round-robin.
Configure a switchover mode that supports ALUA for
both HyperMetro storage arrays' initiators that are
added to the host.
Set the path type for both storage arrays' initiators to
the optimal path.
Local preferred mode Enable ALUA on the host. It is advised to set the path
selection policy to round-robin.
Configure a switchover mode that supports ALUA for
both HyperMetro storage arrays' initiators that are
added to the host.
Set the path type for the local storage array's
initiators to the optimal path and that for the remote
storage array's initiators to the non-optimal path.
Other modes Set the initiator switchover mode for the HyperMetro
storage arrays by following instructions in the follow-
up chapters in this guide. The path type does not
require manual configuration.
1.1.1 Working Principles and Failover

When ALUA works, the host multipathing software classifies the physical paths to
disks as Active Optimized (AO) and Active Non-optimized (AN) paths. The host
preferentially delivers services to the storage system via the AO paths.
● An AO path is the optimal I/O access path between the host and the owning
controller of the LUN.
● An AN path is the suboptimal I/O access path between the host and a non-
owning controller.
When HyperMetro works in load balancing mode, the host multipathing software
defines the paths to the owning controllers on both HyperMetro storage arrays as
AO paths, and those to the other controllers as AN paths. The host accesses the
storage arrays via the AO paths. If an AO path fails, the host will deliver I/Os to
another AO path. If a LUN's owning controller fails, the system will activate the
other controller to maintain load balancing.

Figure 1-1 Load balancing mode
When HyperMetro works in local preferred mode, the host multipathing software
defines the paths to the owning controller on the local storage array as AO paths.
This ensures that the host delivers I/Os only to the owning controller on the local
storage array, reducing link consumption. If all AO paths fail, the host will deliver
I/Os to the AN paths on the non-owning controller. If the owning controller of the
local storage array fails, the system will activate the other controller to maintain
the local preferred mode.
Figure 1-2 Local preferred mode
1.2 Initiator Modes
1.2.1 Initiator Parameter Description
Table 1-2 Initiator parameter description
Parameter Description Example
Uses third-party This parameter is displayed only after an Enabled

multipath initiator has been added to the host.
software If LUNs have been mapped to the host
before you enable or disable this
parameter, restart the host after you
configure this parameter.
You do not need to enable this parameter
on a host with UltraPath.

Switchover Mode Path switchover mode Common

The system supports the following modes: ALUA
● early-version ALUA: default value of

Switchover Mode for an upgrade from
an earlier version to the current version.
Detailed requirements are as follows:
– The storage system must be
upgraded from V300R003C10 and
earlier to V300R003C20 or
V300R006C00SPC100 and later; from
V300R005 to V300R006C00SPC100
and later; from Dorado V300R001C00
to Dorado V300R001C01SPC100 and
later.
– Before the upgrade, the storage
system has enabled ALUA.
● common ALUA: Detailed requirements
are as follows:
– The storage system version must be
V500R007C00 and later,
V300R006C00SPC100 and later, or
Dorado V300R001C01SPC100 and
later.
– The OS of the host that connects to
the storage system must be SUSE,
Red Hat 6.X, Windows Server 2012
(using Emulex HBAs), Windows
Server 2008 (using Emulex HBAs), or
HP-UX 11i V3.
● ALUA not used: does not support ALUA
or HyperMetro. This mode is used when
a host such as HP-UX 11i V2 does not
support ALUA or ALUA is not needed.
● Special mode: This is used when the OS
of the host supports ALUA, but is not
included in common ALUA mode.
Detailed requirements are as follows:
– The storage system version must be
V300R006C00SPC100 and later, or
Dorado V300R001C01SPC100 and
later.
the storage system must be VMware,

AIX, Red Hat 7.X, Windows Server

2012 (using QLogic HBAs), or
Windows Server 2008 (using QLogic
HBAs).
Special mode type Determines which Special mode is used for Mode 0
path switchover. All three special modes
support ALUA. Detailed requirements are as
follows:
● Mode 0:
– The host and storage system must be
connected using a Fibre Channel
network.
the storage system must be Red Hat
7.X, Windows Server 2012 (using
QLogic HBAs), or Windows Server
2008 (using QLogic HBAs).
● Mode 1:
the storage system must be AIX or
VMware.
– HyperMetro works in load balancing
mode.
● Mode 2:
the storage system must be AIX or
VMware.
– HyperMetro works in local preferred
mode.

Path Type The value can be either Optimal Path or Optimal

Non-Optimal Path. Path
● When HyperMetro works in load
balancing mode, set the Path Type for
the initiators of both the local and
remote storage arrays to Optimal Path.
Enable ALUA on both the host and
storage arrays. If the host uses the
round-robin multipathing policy, it
delivers I/Os to both storage arrays in
round-robin mode.
● When HyperMetro works in local
preferred mode, set the Path Type for
the initiator of the local storage array to
Optimal Path, and that of the remote
storage array to Non-Optimal Path.
Enable ALUA on both the host and
storage arrays. The host preferentially
delivers I/Os to the local storage array.
You must configure initiators according to the requirements of the specific OS that
is installed on the host. All of the initiators added to a single host must be
configured with the same switchover mode. Otherwise, host services may be
interrupted.
NOTICE
If a LUN has been mapped to the host, you must restart the host for the
configuration to take effect after you modify the initiator parameters. If you
configure the initiator for the first time, restart is not needed.
1.2.2 Configuring the Initiators

Step 1 Go to the host configuration page.
Open OceanStor DeviceManager. In the navigation tree on the right side, click
Provisioning and then click Host.
Figure 1-3 Going to the host configuration page

Step 2 On the Host tab page, select a host you want to modify. Then select the desired
initiator (on the host) and click Modify.
Figure 1-4 Selecting an initiator you want to modify
Step 3 In the Modify Initiator dialog box, modify the initiator information based on the
requirements of your operating system.
Figure 1-5 Modifying initiator information
Step 4 Repeat the preceding operations to modify other initiators on the host.
Step 5 Restart the host for the configuration to take effect.
----End

1.3 Networking Requirements

When HyperMetro is used with OS native multipathing software:
● Switch networking with multiple paths is used by default.
● Each zone on the switches should only contain one initiator and one target.
You are advised to use dual-switch networking mode to prevent single points of
failure.
1.4 Compatibility
When employing HyperMetro with OS native multipathing software, consider the
compatibility between components (such as storage systems, operating system,
HBAs, and switches) and upper-layer software.
Go to the following website to check the HyperMetro compatibility:
http://support-open.huawei.com/ready/index.jsf
NOTICE
This document only provides the methods to configure the components. For
details about specific compatibility scenarios, see the HyperMetro compatibility
list.

Storage Using OS Native Multipathing Software 2 Windows
2 Windows
2.1 Precautions
2.2 Configuring Storage Arrays
2.3 Configuring the Host
2.1 Precautions
● If all optimal paths have failed, only one non-optimal path will deliver I/Os.
● Currently, HyperMetro LUNs do not support offloaded data transfer (ODX).
● If Hyper-V is enabled, you must close all VMs before restarting a host.
NOTICE
Factors that affect the HyperMetro solution include, but are not limited to,
operating systems, HBAs, switches, clusters, and upper-layer applications. Before
deploying the solution, consult the compatibility list at http://support-
open.huawei.com/ready/index.jsf to ensure that its requirements have been met.
list.
2.2.1 Non-NPIV Mode
Emulex HBAs
Table 2-1 lists the storage array configuration when Emulex HBAs are used in
non-N_Port_ID virtualization (non-NPIV) mode.

Table 2-1 Configuration on storage arrays when Emulex HBAs are used in non-NPIV mode
Server Storage Array Configuration
OS
HyperMetr Storage OS Third-Party Switchover Special Path
o Mode Array Setting Multipathing Mode Mode Type
Software Type
Window Load Local Window Enabled Common N/A Optima

s Server balancing s ALUA l
2008 R2
SP1 Remote Window Enabled Common N/A Optima
s ALUA l
Local Local Window Enabled Common N/A Optima

preferred s ALUA l
Remote Window Enabled Common N/A Non-

s ALUA optimal

s Server balancing s Server ALUA l
2012 2012
Remote Window Enabled Common N/A Optima

s Server ALUA l
2012

preferred s Server ALUA l
2012

s Server ALUA optimal
2012

2012 R2 2012

s Server ALUA l
2012

2012

2012

2016 2012


s Server ALUA l
2012

2012

2012

2019 2012

s Server ALUA l
2012

2012

2012
For details about the Windows versions, see the compatibility list:
http://support-open.huawei.com/ready/pages/user/compatibility/support-
matrix.jsf
NOTICE
QLogic HBAs
Table 2-2 lists the storage array configuration when QLogic HBAs are used in non-
NPIV mode.
Table 2-2 Configuration on storage arrays when QLogic HBAs are used in non-NPIV mode

OS


Software Type

s Server balancing s ALUA l
2008 R2
SP1 Remote Window Enabled Common N/A Optima
s ALUA l

preferred s ALUA l

s ALUA optimal
Window Load Local Window Enabled Special Mode 0 Optima

s Server balancing s Server mode l
2012 2012
Remote Window Enabled Special Mode 0 Optima

s Server mode l
2012
Local Local Window Enabled Special Mode 0 Optima

preferred s Server mode l
2012
Remote Window Enabled Special Mode 0 Non-

s Server mode optimal
2012

2012 R2 2012
Remote Window Enabled Special Mode 0 Optima

s Server mode l
2012

2012

2012

2016 2012
(non-
cluster Remote Window Enabled Common N/A Optima
scenario s Server ALUA l
) 2012


2012

2012

2016 2012
(cluster
scenario Remote Window Enabled Special Mode 0 Optima
) s Server mode l
2012

2012

2012

2019 2012
(non-
cluster Remote Window Enabled Common N/A Optima
scenario s Server ALUA l
) 2012

2012

2012

2019 2012
(cluster
scenario Remote Window Enabled Special Mode 0 Optima
) s Server mode l
2012

2012

2012

matrix.jsf
NOTICE
2.2.2 NPIV Mode
NOTICE
In NPIV mode, VMs directly communicate with storage arrays. The multipathing
software is configured on the VMs. Therefore, the OS versions of the VMs must be
considered.
Currently, only some versions of Windows support Hyper-V (NPIV). For details, see
Microsoft's official explanation:
https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-
v-feature-compatibility-by-generation-and-guest
Emulex HBAs
Table 2-3 lists the storage array configuration when Emulex HBAs are used in
NPIV mode.
Table 2-3 Configuration on storage arrays when Emulex HBAs are used in NPIV mode

OS
Software Type

2012 R2 2012
With
Hyper- Remote Window Enabled Common N/A Optima
V1 s Server ALUA l
2012

2012


2012

2012 2012
With
V2 s Server ALUA l
2012

2012

2012

2016 2012
With
V3 s Server ALUA l
2012

2012

2012

2019 2012
With
V4 s Server ALUA l
2012

2012

2012

matrix.jsf
1. If the server is running Windows Server 2012 R2 with Hyper-V, the OS of the VMs
created on the server must be Windows Server 2012.
2. If the server is running Windows Server 2012 with Hyper-V, the OS of the VMs created
on the server must be Windows Server 2012.
on the server can be Windows Server 2012, Windows Server 2012 R2, or Windows
Server 2016. Patches must be installed in Windows Server 2012 R2.
on the server can be Windows Server 2012, Windows Server 2012 R2, Windows Server
2016, or Windows Server 2019. Patches must be installed in Windows Server 2012 R2.
NOTICE
QLogic HBAs
Table 2-4 lists the storage array configuration when QLogic HBAs are used in
NPIV mode.
Table 2-4 Configuration on storage arrays when QLogic HBAs are used in NPIV mode

OS
Software Type

2012 R2 2012
With
Hyper- Remote Window Enabled Special Mode 0 Optima
V1 s Server mode l
2012

2012

2012


2012 2012
With
Hyper- Remote Window Enabled Special Mode 0 Optima
V2 s Server mode l
2012

2012

2012

2016 2012
With
Hyper-V Remote Window Enabled Common N/A Optima
(non- s Server ALUA l
cluster 2012
scenario Local Local Window Enabled Common N/A Optima
)3 preferred s Server ALUA l
2012

2012

2016 2012
With
Hyper-V Remote Window Enabled Special Mode 0 Optima
(cluster s Server mode l
scenario 2012
)3 Local Local Window Enabled Special Mode 0 Optima
2012

2012

2019 2012
With
Hyper-V Remote Window Enabled Common N/A Optima
(non- s Server ALUA l
cluster 2012

scenario Local Local Window Enabled Common N/A Optima

)4 preferred s Server ALUA l
2012

2012

2019 2012
With
Hyper-V Remote Window Enabled Special Mode 0 Optima
(cluster s Server mode l
scenario 2012
)4 Local Local Window Enabled Special Mode 0 Optima
2012

2012
matrix.jsf
1. If the server is running Windows Server 2012 R2 with Hyper-V, the OS of the VMs
created on the server must be Windows Server 2012.
on the server must be Windows Server 2012.
on the server can be Windows Server 2012, Windows Server 2012 R2, or Windows
Server 2016. Patches must be installed in Windows Server 2012 R2.
on the server can be Windows Server 2012, Windows Server 2012 R2, Windows Server
2016, or Windows Server 2019. Patches must be installed in Windows Server 2012 R2.
NOTICE

2.2.3 iSCSI Networking

On an iSCSI network, storage system configurations are the same as those in non-
NPIV mode in which Emulex HBAs are used.
2.3.1 Version and Patch Requirements
NOTICE
If the patches listed in this section are not installed, exceptions will occur upon a
switchover due to a path failure.
Windows Server 2008 R2 SP1

The following patches must be installed:
Patch Microsoft Windows Server Microsoft Windows Server

Number 2008 R2 Enterprise x64 2008 R2 Datacenter x64
Edition SP1 Edition SP1
KB976932 Yes Yes
KB976902 Yes Yes
KB3125574 Yes Yes
KB3020369 Yes Yes
KB2821052 Yes Yes
KB2754704 Yes Yes
KB2718576 Yes Yes
KB2684681 Yes Yes
KB2528357 Yes Yes
KB2522766 Yes Yes
KB2520235 Yes No
KB2511962 Yes Yes
Windows Server 2012

The OS is Microsoft Windows Server 2012 Datacenter x64 Edition.

Figure 2-1 Operating system version
No patch needs to be installed.
Windows Server 2012 R2

The OS is Microsoft Windows Server 2012 R2 Standard x64 Edition.
Figure 2-2 Operating system version
The following patch files must be installed.
Figure 2-3 Patch files
2.3.2 Configuring Multipathing Software

The native multipathing software in different versions of Windows is configured in
a similar way. This section uses Windows Server 2008 R2 SP1 as an example.
Installing and Enabling the Multipathing Software

In Windows, the multipathing software is disabled by default. Perform the
following operations to install and enable it.
Step 1 Open Server Manager.

In Windows, open Command Prompt and run the servermanager command to
open Server Manager.
Step 2 Add Multipath I/O.
In Windows Server 2008 R2 SP1: On the Server Manager page, right-click
Features and choose Add Features from the shortcut menu.

Figure 2-4 Adding a new feature (Windows Server 2008 R2 SP1)
In Windows Server 2012: On the Server Manager page, click Local Server and
choose Manage > Add Roles and Features.
Figure 2-5 Adding a new feature (Windows Server 2012)
On the Add Features Wizard page, select Multipath I/O.

Figure 2-6 Selecting Multipath I/O
Click Next and select Install to complete the installation.

----End
Configuring the Multipathing Software

After LUNs mapped by a storage array are detected on a host, you must set their
MPIO path policy.
Step 1 Identify the product ID (PID) and vendor ID (VID) of the storage array.
On the Windows server, open Command Prompt and run the mpclaim -e
command to check the LUNs identified by the multipathing software.
Figure 2-7 Viewing the storage product information
In the preceding figure, the VID is HUAWEI and the PID is XSG1. If the value of
the MPIO-ed parameter is NO, the vendor's LUNs have not been taken over by
MPIO.
Step 2 Take over the storage array.
On the Windows server, open the CMD command line and run the mpclaim -r -i -
d "HUAWEI XSG1 " command, as shown in the following figure.

Figure 2-8 Taking over Huawei storage
The VID must contain eight characters and the PID must contain 12 characters. If the
characters are insufficient, add spaces. You can copy the command from the output of the
mpclaim -e command.
NOTICE
After the preceding command is executed, the host restarts automatically.
Step 3 Configure a multipathing policy.
NOTICE
Ensure that you modify the properties of every LUN.
After the host has restarted, right-click a disk discovered by the server and choose
Properties from the shortcut menu.
Figure 2-9 Viewing disk properties
On the HUAWEI XSG1 Multi-Path Disk Device Properties page, click the MPIO
tab. In Select the MPIO policy, select Round Robin With Subset.

Figure 2-10 Configuring the MPIO policy
Activate path verification. On the MPIO tab, click Details. In the DSM Details
dialog box, select Path Verify Enabled.

Figure 2-11 Activating path verification
Step 4 Restart the host.

After the host has been restarted, verify that all parameters have been modified.
You can also run the following command to check whether the disk's path
information has been modified.

Figure 2-12 Checking disk multipathing policy
----End
Verification
Run the mpclaim -s -d command to verify that the configuration has taken effect.
Figure 2-13 Verifying the MPIO disk information
Run the mpclaim -s -d MPIO Disk No. command to verify path information about
an MPIO disk.

Figure 2-14 Verifying path information about an MPIO disk
Both AO (whose TPG_State is Active/Optimized) and AN (whose TPG_State is

Active/Unoptimized) paths are displayed, indicating that ALUA configuration has
taken effect.
2.3.3 Configuring HBAs

During verification, modify the HBA timeout period for the host to detect path
failures quickly, preventing I/Os from stopping for a long time.
Emulex
For Emulex HBAs, modify the following parameters:
● LinkTimeOut
The default value is 30. Set it to 10.
● NodeTimeOut
The default value is 30. Set it to 10.
NOTICE
If the default values for these parameters are different from those specified in this
document, do not modify them. Contact related project personnel for
confirmation.
The modification procedure is as follows.
Step 1 Open the Emulex HBA management tool.

Step 2 Modify the LinkTimeOut and NodeTimeOut parameters.
Select the HBA port and click the Driver Parameters tab. Select each parameter,
enter the new value in the text box, and click Apply.

Figure 2-15 Modifying the timeout parameters
NOTICE
Ensure that you modify the properties of every HBA port.
----End
QLogic
For QLogic HBAs, modify the following parameters:
● Port Down Retry Count

The default value is 30 seconds. Set it to 10.
● Link Down Timeout (seconds)
NOTICE
confirmation.
For details about how to modify these parameters, see 3.3.2 Configuring HBAs.

2.3.4 Configuring Registries

On an iSCSI network, you need to change related registry values so that a host
can detect path failure in a timely manner, preventing I/Os from being suspended
for a long period of time.
For details, see section 7.5 "How Do I Modify the iSCSI Initiator's Driver Timeout
Time?" and section 7.6 "How Do I Change the Number of TCP Data
Retransmission Times" in the Huawei SAN Storage Host Connectivity Guide for
Windows.

Storage Using OS Native Multipathing Software 3 XenServer
3 XenServer
3.1 Precautions
3.4 Verifying the Configurations
3.1 Precautions
NOTICE
list.

Table 3-1 Configuration on storage arrays when a XenServer system is used

OS
Software Type
XenServe Load Local XenServe Enabled Special Mode 0 Optima

r balancing r mode l

Remote XenServe Enabled Special Mode 0 Optima

r mode l
Local Local XenServe Enabled Special Mode 0 Optima

preferred r mode l
Remote XenServe Enabled Special Mode 0 Non-

r mode optimal
For details about the XenServer versions, see the compatibility list:
matrix.jsf
NOTICE

After editing the /etc/multipath.conf file, perform the following operations to
enable DM-Multipath.
Step 1 Right-click the server and choose Enter Maintenance Mode from the shortcut
menu.
NOTICE
Other services will be suspended.

Figure 3-1 Entering the maintenance mode
Step 2 Enable multipathing on the server.

Right-click the server and choose Properties from the shortcut menu. In the
dialog box that is displayed, select Enable multipathing on this server.
Figure 3-2 Enabling multipathing on this server
Step 3 Right-click the server and exit the maintenance mode.

Step 4 Map LUNs to the host and create storage repositories (SRs) on the host. The LUNs
are taken over by the multipathing software.
----End


Add the following contents to the /etc/multipath.conf configuration file of the
multipathing software in XenServer.
device {
vendor "HUAWEI"
product "XSG1"
path_grouping_policy "group_by_prio"
prio alua
path_checker "tur"
path_selector "round-robin 0"
fast_io_fail_tmo 15
dev_loss_tmo 30
}

This section uses QLogic HBAs as an example to describe how to modify timeout
parameters. For other HBAs, contact the HBA vendors for technical support.
NOTICE
confirmation.
The modification procedure is as follows.
Step 1 Download and install the QLogic HBA management tool.

Go to the following website to download the tool.
http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/
DefaultNewSearch.aspx
Step 2 Open the management page.
For the latest QLogic management software (2.01.00 build 03), run the qaucli
command.

Figure 3-3 Management window
Step 3 Configure HBA parameters.

Type 2 to select Adapter Configuration. The following window is displayed.
Figure 3-4 HBA parameters
Type 3 to select HBA Parameters. The HBA port status window is displayed.
Figure 3-5 HBA port status
Select a port to go to the HBA parameters menu.

Figure 3-6 HBA parameters menu
Type 2 to select Configure HBA Parameters. The Configure Parameters Menu

window is displayed.
Figure 3-7 Configure Parameters Menu
Select 13 and 15 and set the values of each to 10. Then type 20 to Commit
Changes.
After the configuration is complete, check the HBA parameters.

Figure 3-8 HBA parameter configuration
Step 4 Complete the configuration for all ports.

Perform the operations in step 3 to configure other ports.
----End
3.4.1 Checking the Multipathing Software Status

After the configuration is complete, run the following command to confirm that
the multipathing software has been enabled:
systemctl status multipathd.service
Figure 3-9 Checking the multipathing software status
3.4.2 Verifying Path Information

After you create SRs on XenCenter for the XenServer host using the LUNs mapped
by the storage system, perform the following operations:
On XenCenter, check the SR status and number of paths. Figure 3-10 shows an
example.
In the XenServer CLI, run the multipath -ll command to verify that the
configuration has taken effect. Figure 3-11 shows an example.

Figure 3-10 Checking the SR status and number of paths
Figure 3-11 Verifying the multipathing configuration
In the command output, status=active corresponds to the AO path and

status=enabled corresponds to the AN path. This indicates that the ALUA
configuration has taken effect. Generally, the prio value of an AO path on a
XenServer system is 50, and that of an AN path is 10. In the preceding figure,
there are one AO path and three AN paths. If the number of paths is the same as
that on the storage systems, the multipathing software has been configured
successfully.

Storage Using OS Native Multipathing Software 4 HP-UX
4 HP-UX
4.1 Precautions
4.1 Precautions
NOTICE
list.

Table 4-1 Configuration on storage arrays when an HP-NX system is used
OS
Software Type
HP-UX Load Local HP-UX Enabled Common N/A Optima

11iv3 balancing ALUA l
Remote HP-UX Enabled Common N/A Optima

ALUA l

Local Local HP-UX Enabled Common N/A Optima

preferred ALUA l
Remote HP-UX Enabled Common N/A Non-

ALUA optimal
For details about the HP-UX versions, see the compatibility list:
matrix.jsf
NOTICE

HP-UX 11i v3 Update 4 (11.31.0903) and later versions are supported.
Run the following command to check the OS version.

# swlist | grep HPUX11i
HPUX11i-BOE B.11.31.1603 HP-UX Base Operating Environment
In the preceding command output, the version is HP-UX 11i v3 1603.

HP-UX's multipathing software (NMP) is enabled by default. No extra
configuration is required.
Run the following commands to check the multipathing software.

# scsimgr get_attr -D /dev/rdisk/disk24 -a load_bal_policy
SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk24
name = load_bal_policy
current = round_robin
default = round_robin
saved =
# scsimgr get_attr -D /dev/rdisk/disk24 -a alua_enabled
SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk24
name = alua_enabled
current = true
default = true
saved =


Keep the default configuration. You can use the following command to view the
path information.
Figure 4-1 View path
In this example:
● State
Path state. ACTIVE paths are AO paths and STANDBY paths are AN paths. If
both AO and AN paths are displayed, ALUA configuration has taken effect.
NOTICE
When a LUN mapped to the host does not have any service, the state of
paths to this LUN on the host becomes UNOPEN. To restore the path status
to ACTIVE, run the ioscan command or read or write the mapped LUN.
● LUN access type

T10 Asymmetric Active-Active indicates that ALUA is supported.
● Asymmetric logical unit access supported
If ALUA is enabled, the supported ALUA type will be displayed (Implicit or
Explicit).

Storage Using OS Native Multipathing Software 5 Red Hat
5 Red Hat
5.1 Precautions
5.1 Precautions
NOTICE
list.

Table 5-1 Configuration on storage arrays when an RHEL system is used

OS
Software Type
RHEL 6.x Load Local Linux Enabled Common N/A Optima

balancing ALUA l

Remote Linux Enabled Common N/A Optima

ALUA l
Local Local Linux Enabled Common N/A Optima

preferred ALUA l
Remote Linux Enabled Common N/A Non-

ALUA optimal
RHEL 7.x Load Local Linux Enabled Special Mode 0 Optima

balancing mode l
Remote Linux Enabled Special Mode 0 Optima

mode l
Local Local Linux Enabled Special Mode 0 Optima

preferred mode l
Remote Linux Enabled Special Mode 0 Non-

mode optimal
For details about the RHEL versions, see the compatibility list:
matrix.jsf
NOTICE

In Red Hat, the DM-Multipath software is not installed by default. To check
whether DM-Multipath has been installed, run the following command:
rpm –qa|grep multipath
If the following command output is displayed, DM-Multipath has been installed.
Figure 5-1 DM-Multipath has been installed

If the preceding command output is not displayed, install and enable DM-
Multipath as follows:
Step 1 Find the DM-Multipath software package on the installation CD-ROM of the OS
and run the rpm -vih packagename command to install DM-Multipath.
Step 2 Configure the multipath service to run at host startup.
For RHEL 7.x, run the following command to check whether the multipath service
runs at startup.
Figure 5-2 Checking whether the multipath service runs at startup
If the multipath service status in the command output is not enabled, run the
following command to enable it.
systemctl enable multipathd.service
Step 3 Modify the configuration file of the multipathing software.
Add the Huawei storage information to the /etc/multipath.conf configuration

file. For details, see the next section.
Step 4 Start the multipath service.
For RHEL 7.x, run the following commands to start the multipath service and
check its status.
Figure 5-3 Starting the multipath service
----End

For Red Hat 6.x and 7.x, add the contents in Figure 5-4 to the /etc/
multipath.conf file.

Figure 5-4 Configuration file contents
dev_loss_tmo and fast_io_fail_tmo specify the retry time and switchover time in the event
of a link fault. The preceding figure provides recommended values for these two
parameters, and you can modify them according to your own requirements.

QLogic
For details about the modification procedure, see section 3.3.2 Configuring HBAs.

Run the multipath -ll command to verify that the configuration has taken effect.
As shown in Figure 5-5, paths to the HyperMetro storage systems have been
converged successfully and the number of paths is correct. status=active
corresponds to the AO path to the owning controller of the LUN, and

status=enabled corresponds to the AN path to the non-owning controller of the

LUN. This indicates that the ALUA configuration has taken effect.
Generally, the prio value of an AO path on a Linux system is 50, and that of an AN path is
10.

Storage Using OS Native Multipathing Software 6 Oracle VM
6 Oracle VM
6.1 Precautions
6.1 Precautions
NOTICE
list.

Table 6-1 Configuration on storage arrays when an Oracle VM system is used
OS
Software Type
Oracle Load Local Oracle Enabled Common N/A Optima

VM balancing VM ALUA l
Remote Oracle Enabled Common N/A Optima

VM ALUA l

Local Local Oracle Enabled Common N/A Optima

preferred VM ALUA l
Remote Oracle Enabled Common N/A Non-

VM ALUA optimal
Oracle Load Local Oracle Enabled Special Mode 0 Optima

VM balancing VM mode l
3.3.1 Remote Oracle Enabled Special Mode 0 Optima
VM mode l
Local Local Oracle Enabled Special Mode 0 Optima

preferred VM mode l
Remote Oracle Enabled Special Mode 0 Non-

VM mode optimal
For details about the Oracle VM versions, see the compatibility list:
matrix.jsf
NOTICE

Oracle VM's multipathing software is installed by default. No extra operations are
required.

If the switchover mode is Special Mode, add the following contents to the /etc/
multipath.conf configuration file on the host.

Figure 6-1 Configuration file in Special Mode
If the switchover mode is Common ALUA, add the following contents to the /etc/
multipath.conf configuration file on the host.
devices {
device {
vendor "HUAWEI"
product "XSG1"
path_grouping_policy group_by_prio
prio alua
path_checker tur
failback immediate
fast_io_fail_tmo 5
dev_loss_tmo 30
}
}

QLogic
If the switchover mode is Special Mode, modify the following parameters:

Storage Using OS Native Multipathing Software 7 SLES
7 SLES
7.1 Precautions
7.2 Configuring the Storage Arrays
7.1 Precautions
● It is recommended that you shield the server's local disks before configuring
the multipathing software.
● For SLES 12 SP1, the kernel patch must be installed.
NOTICE
list.
7.2 Configuring the Storage Arrays

Table 7-1 Configuration on storage arrays when an SLES system is used

OS


o Mode Setting Multipathing Mode Mode Type
Software Type
SLES Load Local Linux Enabled Common N/A Optima

balancing ALUA l

ALUA l

preferred ALUA l

ALUA optimal
For details about the SLES versions, see the compatibility list:
matrix.jsf
NOTICE

SLES 12 SP1
The following figure shows the host's OS version.
Figure 7-1 Host's OS version
The system kernel has been upgraded and is not the original standard kernel.
The kernel-default-3.12.55-52.42.1.x86_64.rpm patch must be installed.


In SLES, the DM-Multipath software is not installed by default. To check whether
DM-Multipath has been installed, run the following command:
For SLES 12.x, run the following command to check whether the multipath service
runs at startup.
Figure 7-3 Checking whether the multipath service runs at startup (SLES 12.x)
For SLES 11.x and earlier versions, run the following command to check whether
the multipath service runs at startup.
Figure 7-4 Checking whether the multipath service runs at startup (SLES 11.x and
earlier versions)
If the multipath service status in the command output is not on, run the following
command to enable it.
chkconfig multipathd on
The following figure shows the status after the command is executed.

Figure 7-5 Status after the command is executed

For SLES 12.x, run the following commands to start the multipath service and
check its status.
Figure 7-6 Starting the multipath service in SLES 12.x
Ensure that the service status is active.

For SLES 11.x and earlier versions, run the following commands to start the
multipath service and check its status.
Figure 7-7 Starting the multipath service in SLES 11.x and earlier versions
----End
NOTICE
If the system enters the emergency mode after the multipathing software is
enabled and the host is restarted, isolate the local disks of the OS to prevent DM-
Multipath from taking them over. For details, go to the following website:
https://www.suse.com/documentation/sles-12/stor_admin/data/
sec_multipath_trouble.html

For SLES 11 and versions of SLES 12 earlier than SP2, add the following contents
to the /etc/multipath.conf configuration file of the multipathing software.
Figure 7-8 Multipathing configuration in SLES 11 and SLES 12 (earlier than SP2)
The WWID in the blacklist in the preceding figure is the server's local disk information.
Change it to the actual information at your site (this also applies to SLES 12 SP2). For
details, go to the following website:
For SLES 12 SP2, the configuration file of the multipathing software is as follows.
Figure 7-9 Configuration file of the multipathing software in SLES 12 SP2


As shown in Figure 7-10, paths to the HyperMetro storage systems have been
converged successfully and the number of paths is correct. status=active
corresponds to the AO path to the owning controller of the LUN, and
status=enabled corresponds to the AN path to the non-owning controller of the
LUN. This indicates that the ALUA configuration has taken effect. Generally, the
prio value of an AO path on a Linux system is 50, and that of an AN path is 10.

Storage Using OS Native Multipathing Software 8 RHV
8 RHV
8.1 Precautions
8.1 Precautions
NOTICE
list.

Table 8-1 Configuration on storage arrays when an RHV system is used

OS
Software Type
RHV Load Local Linux Enabled Special Mode 0 Optima

balancing mode l


mode l

preferred mode l

mode optimal
For details about the RHV versions, see the compatibility list:
matrix.jsf
NOTICE

In Red Hat Virtualization Host (RHV-H), check whether DM-Multipath has been
installed using the following command:
Figure 8-1 Command output indicating that DM-Multipath has been installed
Step 1 Find the DM-Multipath software package n the installation CD-ROM of the OS
Run the following command to check whether the multipath service runs at
startup.


NOTICE
The configuration file for RHV-H is different from that of other Red Hat OSs. After
the configuration is complete, you must run the persist /etc/multipath.conf
command. For details, see 17.2 Why Does the Multipathing Software
Automatically Return to Its Initial Configuration Every Time RHV-H Restarts?

Run the following command to start the multipath service and check its status.
Figure 8-3 Starting the multipath service in RHV
Ensure that the service status is active.
----End

multipathing software on the host.
devices {
device {
vendor "HUAWEI"
product "XSG1"
prio alua

path_checker tur
failback immediate
fast_io_fail_tmo 15
dev_loss_tmo 30
}
}


After the paths are taken over, the path information is as follows.

In the command output, status=active corresponds to the AO path and

status=enabled corresponds to the AN path. This indicates that the ALUA
configuration has taken effect. Generally, the prio value of an AO path on a Linux
system is 50, and that of an AN path is 10. In the preceding figure, there are one
AO path and three AN paths. If the number of paths is the same as that on the
storage systems, the multipathing software has been configured successfully.

Storage Using OS Native Multipathing Software 9 Rocky
9 Rocky
9.1 Precautions
9.1 Precautions
NOTICE
list.

Table 9-1 Configuration on storage arrays when a Rocky system is used
OS
Software Type
Rocky Load Local Linux Enabled Common N/A Optima

balancing ALUA l

ALUA l


preferred ALUA l

ALUA optimal
For details about Rocky versions, see the compatibility list:

matrix.jsf
NOTICE

Rocky 6.0.42.41
The following figure shows the host's OS version.
Figure 9-1 OS version
Rocky's kernel and multipathing software versions change frequently and require extra
attention.
If your version differs from that in the preceding figure, contact Huawei's technical support.


Contact Rocky engineers to obtain the installation package and install the
multipathing software.

Figure 9-2 Multipathing software configuration in Rocky 6.0.42.41

Storage Using OS Native Multipathing Software 10 NeoKylin
10 NeoKylin
10.1 Precautions
10.1 Precautions
NOTICE
list.

Table 10-1 Configuration on storage arrays when a NeoKylin system is used
OS
Software Type
Neokylin Load Local Linux Enabled Common N/A Optima

6.x balancing ALUA l

ALUA l


preferred ALUA l

ALUA optimal
Neokylin Load Local Linux Enabled Special Mode 0 Optima

7.x balancing mode l

mode l

preferred mode l

mode optimal
For details about the Neokylin versions, see the compatibility list:
matrix.jsf
NOTICE
NeoKylin 6.0_U5 (mips64)

The following figure shows the system version and kernel.
Figure 10-1 NeoKylin 6.0_U5 and kernel


Contact NeoKylin engineers to install and enable the multipathing software.

devices {
device {
vendor "HUAWEI"
product "XSG1"
prio alua
path_checker tur
failback immediate
fast_io_fail_tmo 5
dev_loss_tmo 30
}
}

QLogic
Set the following parameters:
For details about how to modify the parameters, see section 3.3.2 Configuring
HBAs.

Storage Using OS Native Multipathing Software 11 Solaris
11 Solaris
11.1 Precautions
11.1 Precautions
NOTICE
list.

Table 11-1 Configuration on storage arrays when a Solaris system is used

OS
Software Type
Solaris Load Local Solaris Enabled Common N/A Optima

balancing ALUA l

Remote Solaris Enabled Common N/A Optima

ALUA l
Local Local Solaris Enabled Common N/A Optima

preferred ALUA l
Remote Solaris Enabled Common N/A Non-

ALUA optimal
For details about the Solaris versions, see the compatibility list:
matrix.jsf
NOTICE

After ALUA is enabled on the storage system, you do not need to configure the
host system. Run the stmsboot -D fp -e command.
After the command is executed, information similar to the following command

output is displayed.
bash-3.2# stmsboot -D fp -e
WARNING: This operation will require a reboot.
Do you want to continue ? [y/n] (default: y) y
The changes will come into effect after rebooting the system.
Reboot the system now ? [y/n] (default: y) y
updating /platform/sun4u/boot_archive
NOTICE
After you perform this operation, the host system will restart.
After the host system has restarted, the LUN information is as follows:

Figure 11-1 LUN information in Solaris
The path format is scsi_vhci. This is the path information after multiple paths are
aggregated.

No extra configuration is required.

After LUNs are mapped from a storage system to a host, scan for and check the
LUNs to ensure that the numbers and status of the optimal and non-optimal
paths are correct. Run the following command to check the information.
root@solarisx86:~# mpathadm show lu /dev/dsk/c0t6222222100222222000E25A800000004d0s2
Logical Unit: /dev/rdsk/c0t6222222100222222000E25A800000004d0s2
mpath-support: libmpscsi_vhci.so
Vendor: HUAWEI
Product: XSG1
Revision: 4303
Name Type: unknown type
Name: 6222222100222222000e25a800000004
Asymmetric: yes
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 2100001b3210fbda
Target Port Name: 200800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Target Port Name: 2602222222222222
Override Path: NA
Path State: OK
Disabled: no
Override Path: NA
Path State: OK

Disabled: no
Override Path: NA
Path State: OK
Disabled: no
Override Path: NA
Path State: OK
Disabled: no
Override Path: NA
Path State: OK
Disabled: no
Override Path: NA
Path State: OK
Disabled: no
Override Path: NA
Path State: OK
Disabled: no
Target Port Groups:
ID: 33
Explicit Failover: no
Access State: active optimized
Target Ports:
Name: 200800ac01020304
Relative ID: 8193
ID: 1
Access State: active optimized
Target Ports:
Name: 2602222222222222
Relative ID: 23
Name: 2601222222222222
Relative ID: 22
ID: 2
Access State: active not optimized
Target Ports:
Name: 2619222222222222
Relative ID: 282
Name: 2618222222222222
Relative ID: 281
ID: 35
Target Ports:
Name: 202800ac01020304
Relative ID: 8705
ID: 34
Target Ports:
Name: 201800ac01020304
Relative ID: 8449
ID: 36
Target Ports:
Name: 203800ac01020304
Relative ID: 8961
root@solarisx86:~#
In the command output:

● If Access State is active optimized, the path is a preferred one.

● If Access State is active not optimized, the path is a non-preferred one.
In this example, there are three preferred paths and five non-preferred paths. The
result is the same as configured, indicating that the configuration is successful.

Storage Using OS Native Multipathing Software 12 Asianux
12 Asianux
12.1 Precautions
12.1 Precautions
NOTICE
list.

Table 12-1 Configuration on storage arrays when an Asianux system is used

OS
Software Type
Asianux Load Local Linux Enabled Common N/A Optima

balancing ALUA l


ALUA l

preferred ALUA l

ALUA optimal
For details about the Asianux versions, see the compatibility list:
matrix.jsf
NOTICE

The method used to enable the multipathing software in Asianux is the same as
that used in Red Hat. For details, see 5.3.1 Configuring Multipathing Software.

The configuration file of the multipathing software on an Asianux 4.x host is as
follows.
Figure 12-1 Configuration file of the multipathing software on an Asianux 4.x

host

NOTICE
If you use DM-Multipath for the first time, you are advised to copy a file
from /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf when
configuring the /etc/multipath.conf file, rather than using the default /etc/
multipath.conf file.

There are no special requirements for configuring HBAs in Asianux.

/etc/init.d/multipathd status
The following figure shows the command output.
Run the following command to confirm that the multipathing software runs at
system startup.
Figure 12-3 Confirming that the multipathing software runs at system startup

After the paths are taken over, the path information is as follows.

Figure 12-4 Path information in Asianux 4.x

Storage Using OS Native Multipathing Software 13 Ubuntu
13 Ubuntu
13.1 Precautions
13.1 Precautions
NOTICE
list.

Table 13-1 Configuration on storage arrays when a Ubuntu system is used
OS
Software Type
Ubuntu Load Local Linux Enabled Common N/A Optima

balancing ALUA l

ALUA l


preferred ALUA l

ALUA optimal
For details about the Ubuntu versions, see the compatibility list:
matrix.jsf
NOTICE

You can find the multipathing software package on the OS installation CD-ROM.
The operations are as follows.
Step 1 Insert the CD-ROM in a server and mount it.

In this example, the CD-ROM is mounted to the /mnt directory.
Step 2 Configure the software library.
Modify the /etc/apt/sources.list file, as shown in the following figure.
Figure 13-1 Configuring the software library
Step 3 Install the software.

Run the following command to install the multipathing software.
apt-get install multipath-tools
----End


The configuration file of the multipathing software on a Ubuntu 16.04 host is as
follows.
Figure 13-2 Configuration file of the multipathing software on a Ubuntu 16.04

host

Storage Using OS Native Multipathing Software 14 VMware
14 VMware
14.1 Precautions
14.1 Precautions
When using HyperMetro with VMware ESXi, note the following:
● If two HyperMetro LUNs are mapped to a host as VMFS datastores, their host
LUN IDs must be the same when the host is of ESXi 6.5.0 GA build 4564106 or
a subsequent version earlier than ESXi 6.5 U1 build 5969303. For other ESXi
versions, it is recommended that the host LUN IDs be the same.
● If two HyperMetro LUNs are mapped to a host as raw devices (RDM), their
host LUN IDs must be the same regardless of host versions.
● If a HyperMetro LUN is mapped to multiple ESXi hosts in a cluster as VMFS
datastores or raw devices (RDM), the host LUN IDs of the LUN for all of these
ESXi hosts must be the same. You are advised to add all ESXi hosts in a cluster
that are served by the same storage device to a host group and to the same
mapping view.
You can query the host LUN ID mapped to the ESXi host in the Mapping
View of OceanStor DeviceManager, as shown in Figure 14-1.
Figure 14-1 Changing the host LUN ID

Before modifying the Host LUN ID, read the following warnings carefully
since misoperations may cause service interruption. To modify the host LUN
ID for a LUN, right-click the LUN and choose Change host LUN ID from the
shortcut menu. In the displayed dialog box, set the same Host LUN ID value
for the two storage devices in the HyperMetro pair and then click OK.
Changing the host LUN ID with an incorrect procedure may cause service
interruption.
If no datastore has been created on either LUN in the HyperMetro pair, you
can directly change the host LUN ID for the LUNs. Wait for about 5 to 15
minutes after the modification is complete, and then run the Rescan
command in the ESXi host CLI to verify that the LUNs in the HyperMetro pair
have been restored and are online.
If a datastore has been created on either LUN in the HyperMetro pair and a
service has been deployed in the datastore, change the host LUN ID using
only the following two methods (otherwise, changing the host LUN ID for
either LUN will cause the LUN to enter the PDL state and consequently
interrupt services):
● Method 1: You do not need to restart the ESXi host. Migrate all VMs in
the datastore deployed on the LUNs in the HyperMetro pair to another
datastore, and then change the host LUN ID on the OceanStor
DeviceManager. Wait for about 5 to 15 minutes after the modification is
complete, and then run the Rescan command in the ESXi host CLI to
verify that the LUNs in the HyperMetro pair have been restored and are
online. Then, migrate the VMs back to the datastore deployed on the
LUNs in the HyperMetro pair.
● Method 2: You need to restart the ESXi host. Power off all VMs in the
datastore deployed on the LUNs in the HyperMetro pair to ensure that no
service is running on the LUNs. Then, modify the host LUN ID on the
OceanStor DeviceManager. Then, restart the ESXi host for the
modification to take effect. After restarting the ESXi host, check whether
the LUNs in the HyperMetro pair have been restored and are online.
● For OceanStor V3 V300R003C20SPC200, a single array with ALUA enabled can

have a maximum of 8 controllers; two active-active arrays with ALUA enabled
also cannot have more than 8 controllers.
● VMware ESXi 6.0 U2 and later versions support HyperMetro configuration.
Versions earlier than VMware ESXi 6.0 U2 have their defects.
● Dorado V3 must be V300R001C01SPC100 and later versions, supporting
multi-controller and HyperMetro ALUA.
NOTICE
When deploying HyperMetro with VMware ESXi NMP, consider the compatibility
between components (such as storage system, operating system, HBAs, and
switches) and the application software.

Before deploying the solution, consult the compatibility list at http://support-

list.

Table 14-1 Storage array configurations when a VMware system is used

OS
Software Type
VMware Load Local VMware Enabled Special Mode 1 Optima

ESXi balancing ESX mode l
Remote VMware Enabled Special Mode 1 Optima

ESX mode l
Local Local VMware Enabled Special Mode 2 Optima

preferred ESX mode l
Remote VMware Enabled Special Mode 2 Non-

ESX mode optimal
For details about the VMware ESXi versions, see the compatibility list:
matrix.jsf
NOTICE
On OceanStor V3 V300R003C20, special modes 1 and 2 are disabled by default.

You can enable them by running the change tgt_alua_config command in
developer mode. For details about this command, see the OceanStor 5300
V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003C20 Restricted
Command Reference or OceanStor 18500 V3&18800 V3 Storage System
V300R003C20 Restricted Command Reference. Contact Huawei technical support
engineers to obtain the documents.

On OceanStor V3 V300R006C00SPC100, Dorado V3 V300R001C01SPC100, and

later versions, you can configure special modes 1 and 2 directly on
DeviceManager.
Figure 14-2 Querying the special mode type

The multipathing software has been installed in the OS by default.

Run the following command on the host to add SATP rules:
esxcli storage nmp satp rule add -V HUAWEI -M XSG1 -s VMW_SATP_ALUA -P VMW_PSP_RR -c tpgs_on

● In VMware ESXi 6.0 P07 (build number 9239799) and later 6.0 releases, the system
integrates Huawei storage's VMW_SATP_ALUA and PSP_RR rules (system-level) by
default.
In VMware ESXi 6.5 Patch 02 (build number 7388607) and later 6.5 releases, the system
integrates Huawei storage's VMW_SATP_ALUA and PSP_RR rules (system-level) by
default.
In all VMware ESXi 6.7 releases, the system integrates Huawei storage's
VMW_SATP_ALUA and PSP_RR rules (system-level) by default. However, you are advised
to run the preceding commands to manually add VMW_SATP_ALUA and PSP_RR rules
(user-level). Manually added rules have a higher priority than the default ones.
● The preceding command only applies to ESXi 5.0 and later. For ESXi versions that
HyperMetro supports, see the compatibility list at http://support-open.huawei.com/
ready/pages/user/compatibility/support-matrix.jsf
● New SATP rules will immediately take effect for newly mapped LUNs, but will not take
effect for previously mapped LUNs until the host is restarted.
● For details about the parameters in the host commands, see https://
docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.storage.doc/GUID-
D10F7E66-9DF1-4CB7-AAE8-6F3F1F450B42.html.
14.3.2 Setting Timeout Parameters
Fibre Channel Network

You do not need to set timeout parameters for a Fibre Channel network.
iSCSI Network
Run the following commands on the host:
esxcli iscsi adapter param set -A vmhba35 -k NoopOutInterval -v 1
esxcli iscsi adapter param set -A vmhba35 -k NoopOutTimeout -v 10
esxcli iscsi adapter param set -A vmhba35 -k RecoveryTimeout -v 1
● The preceding commands only apply to ESXi 5.0 and later. For ESXi versions that
HyperMetro supports, see the compatibility list at http://support-open.huawei.com/
ready/pages/user/compatibility/support-matrix.jsf
● Replace vmhba35 with iSCSI storage adapters as required.
● The settings shorten the path switchover time to about 11s. In comparison, the default
ESXi settings may result in an up-to-35s path switchover time for ESXi 6.0.* and ESXi
6.5.* and an up-to-25s path switchover time for ESXi 6.7.*.
Restart the host for the configuration to take effect.
14.3.3 Configuring a VMware Cluster

Mandatory Configuration Items:
Table 14-2 Cluster configuration when the OS native multipathing software (VMware NMP) is used
VMware vSphere Host Parameter Cluster Remarks

ESXi Version Parameter

VMkernel.Boot.te Disk.Autoremove VM policies for

rminateVMOnPD OnPDL APD and PDL
L
5.5.* True 0 Select Turn on After configuring

vSphere HA. an ESXi 5.5.* host,
you must restart
the host for the
configuration to
take effect.
6.0 GA HyperMetro is not supported if the OS native multipathing software (VMware

6.0 U1 NMP) is used. You are advised to upgrade the operating system to ESXi 6.0
U2 or later.
NOTE
Storage PDL responses may not trigger path failover in VMware vSphere 6.0 GA and 6.0
U1. For details, see VMware KB.
6.0 U2 False (Retain the 1 (Retain the 1. Select Turn on For a host of a
6.0 U3 default value.) default value.) vSphere HA. version from ESXi
2. Set Datastore 6.0 U2 to ESXi
6.5.* with PDL to 6.7.*, retain the
Power off and default host
6.7.* parameter
restart VMs.
settings. You only
3. Set Datastore
need to enable
with APD to
HA again in
Power off and
vCenter for the
restart VMs-
settings to take
Aggressive
effect.
restart policy.
● For VMware vSphere 5.0 u1, 5.1, and 5.5, deploy ESXi hosts across data
centers in an HA cluster and configure the cluster with the HA advanced
parameter das.maskCleanShutdownEnabled = True.
● A VM service network requires L2 interworking between data centers for VM
migration between data centers without affecting VM services.
● For VMware vSphere 5.0 u1, later 5.0 versions, and 5.1 versions, log in to the
CLI of each ESXi host using SSH and add Disk.terminateVMOnPDLDefault =
True in the /etc/vmware/settings file.
● For VMware vSphere 5.5.*, 6.0 u1, and versions between them, use vSphere
Web Client to connect to vCenter, go to the cluster HA configuration page,
and select Turn on vSphere HA. Then, log in to each ESXi host using vSphere
Web Client or vCenter and complete the following settings:
Set VMkernel.Boot.terminateVMOnPDL = True. The parameter forcibly
powers off VMs on a datastore when the datastore enters the PDL state.

Figure 14-3 Boot parameter settings
Set Disk.AutoremoveOnPDL = 0. This setting ensures that datastores in the

PDL state will not be automatically removed.
Figure 14-4 Disk parameter settings
● For VMware vSphere 6.0 u2 and later versions:

After connecting to vCenter through the Web Client, enter the cluster HA
configuration. The configuration requirements are as follows.

Figure 14-5 vSphere 6.0 cluster configuration
● For VMware vSphere 6.5:

configuration. The configuration requirements are as follows.
Figure 14-6 vSphere 6.5 cluster configuration-1

● For VMware vSphere 6.7 and later update versions:

configuration and set the parameters as follows.

Recommended Configuration Items

● Configure the vMotion, service, and management networks with different
VLAN IDs to prevent network interference.
● Configure the management network to include the vCenter Server
management node and ESXi hosts. Deny access from external applications.
● Divide the service network into VLANs to ensure logical isolation and control
broadcast domains.
● Configure a DRS group to ensure that VMs can be recovered first in the local
data center in the event of the breakdown of a single host.
14.4.1 Verifying the Multipathing Software Status and Path

Information
Perform the following operations to verify that VMware NMP configurations take
effect:
Step 1 Run the esxcli storage nmp satp rule list | grep -i huawei command to verify
that SATP rules are successfully added.

The command output shows that SATP rules are successfully added.
Step 2 Run the esxcli storage nmp device list -d=naa.6xxxxxxx command to verify that
working paths of LUNs are properly configured.
naa.6xxxxxxx indicates the drive letter of a LUN after being mapped to the host.
Working paths are successfully configured if their Storage Array Type and Path
Selection Policy are the same as those configured, and the number of Working
Paths is equal to the total number of paths in the port group.
Example:
The following SATP rule is configured:
esxcli storage nmp satp rule add -V HUAWEI -M XSG1 -s VMW_SATP_ALUA -P VMW_PSP_RR -c tpgs_on
The port group has four paths.
In the command output, Storage Array Type is VMW_SATP_ALUA, Path

Selection Policy is VMW_PSP_RR, and Working Path is 4, consistent with the
corresponding AO path parameters. Therefore, working paths are successfully
configured.
When Path Selection Policy is VMW_PSP_FIXED, only one working path is available, which
is any path in the port group where AO paths reside.
----End

Storage Using OS Native Multipathing Software 15 AIX
15 AIX
15.1 Precautions
15.1 Precautions
NOTICE
list.

Table 15-1 Configuration on storage arrays when an AIX system is used
OS
Software Type
AIX Load Local AIX Enabled Special Mode 1 Optima

balancing mode l
Remote AIX Enabled Special Mode 1 Optima

mode l

Local Local AIX Enabled Special Mode 2 Optima

preferred mode l
Remote AIX Enabled Special Mode 2 Non-

mode optimal
For details about the AIX versions, see the compatibility list:
matrix.jsf
NOTICE
On OceanStor V3 V300R003C20, special modes 1 and 2 are disabled by default.

You can enable them by running the change tgt_alua_config command in
developer mode. For details about this command, see the OceanStor 5300
V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003C20 Restricted
Command Reference or OceanStor 18500 V3&18800 V3 Storage System
V300R003C20 Restricted Command Reference. Contact Huawei technical support
engineers to obtain the documents.
On OceanStor V3 V300R006 and Dorado V3 V300R001C01, you can configure
special modes 1 and 2 directly on DeviceManager.
Figure 15-1 Querying the special mode type


AIX's native MPIO can take over Huawei storage disks only if the AIX ODM
package has been installed. For details on how to install AIX ODM, see AIX ODM
for MPIO User Guide at the following link:
http://support.huawei.com/enterprise/docinforeader.action?
contentId=DOC1000087218&idPath=7919749|7941815|9523109|8576127
You can run the following command to check whether MPIO takes over Huawei
storage disks.
Figure 15-2 Checking whether MPIO takes over Huawei storage disks

The default system I/O policy is fail_over, and I/Os can be delivered only on one
path. To allow I/Os to be delivered on paths of two active-active arrays, you can
run the following command to change the I/O policy to round_robin:
Figure 15-3 Changing the I/O policy

After I/Os have been delivered, you can run the following command to check
whether the path priority is correct:
Figure 15-4 Querying paths
If the value of path_status has Opt, the corresponding paths are preferred ones.
Other paths are non-preferred ones.
In the example shown in Figure 15-4, there are two preferred paths and 10 non-
preferred paths. The result is the same as configured, indicating that the
configuration is successful.
NOTICE
Only AIX 6.1 TL9, AIX 7.1 TL3, and later versions support the lsmpio command.
For other AIX versions, you can only use the lspath command to query paths.

Storage Using OS Native Multipathing Software 16 FusionCompute
16 FusionCompute
16.1 Precautions
16.1 Precautions
NOTICE
deploying the solution, consult the FusionCompute team to ensure that its
requirements are met.
list.

Table 16-1 Configuration on storage arrays when a FusionCompute system is used

OS
Software Type
FusionC Load Local Linux Enabled Special Mode 0 Optima

ompute balancing mode l
6.3.0/6.3

. Remote Linux Enabled Special Mode 0 Optima

1/6.5.0/6 mode l
.
5.1/8.0.0 Local Local Linux Enabled Special Mode 0 Optima
preferred mode l

mode optimal
For details about the FusionCompute versions, see the compatibility list:
matrix.jsf
NOTICE

To check whether DM-Multipath has been installed on FusionCompute, run the
following command:

For FusionCompute 6.3.0, 6.3.1, and 6.5.0, run the following command to check
whether the multipath service runs at startup.

For FusionCompute 6.3.0, 6.3.1, and 6.5.0, run the following commands to start
the multipath service and check its status.
Figure 16-3 Starting the multipath service
Ensure that the service status is active (running).

----End

For FusionCompute 6.3.0, 6.3.1, and 6.5.0, add the contents in Figure 16-4 to
the /etc/multipath.conf file.
Figure 16-4 Configuration file contents

After the configuration is complete, run the following command to restart the
multipath service for the configuration to take effect.
systemctl restart multipathd.service


Run the following command to verify that the multipathing software is normal.
If the status is active (running), the multipathing software is normal.

Run the following command to check the path information.
multipath –ll
After the paths are taken over, the path information similar to the following is
displayed on the host.
Figure 16-6 LUN path information

After the configuration has taken effect, the status of some LUN paths is prio=50
status=active and that of other LUN paths is prio=10 status=enabled.

Storage Using OS Native Multipathing Software 17 FAQs
17 FAQs
17.1 How Do I Determine Whether the HBA Parameters Configured for the
Multipathing Software Have Taken Effect?
17.2 Why Does the Multipathing Software Automatically Return to Its Initial
Configuration Every Time RHV-H Restarts?
17.3 Why Does SLES Enter Emergency Mode After the Multipathing Software Is
Configured?
17.4 Why Does the Old Path Information Remain After an HBA Is Replaced on a
XenServer Host?
17.5 What Can I Do If I/Os on a VMware 6.0 Host Are Interrupted After the
Replication Link Between the Storage Systems Goes Down?
17.6 What Can I Do If Links Are Not Aggregated in Linux Due to the Multipathing
Software Anomaly?
17.1 How Do I Determine Whether the HBA

Parameters Configured for the Multipathing Software
Have Taken Effect?
Symptom
After the /etc/multipath.conf file has been configured, the configured timeout
period does not take effect. The I/O suspension time upon a failover exceeds the
expectation.
Solution
Perform the following operations to check whether the configuration file has
taken effect.
Step 1 Check the target information about each path.
Run the multipath -ll command to obtain path information.

Figure 17-1 Obtaining target information
In the preceding command output, the target information corresponding to the

drive letter includes 0, 1, 2, and 3.
Step 2 Obtain the remote port information.
Run the following command:
grep . /sys/class/fc_remote_ports/rport-0\:0-*/scsi_target*
The command output is as follows.
Figure 17-2 Obtaining the remote port information
In the command output, the remote port information is from 0:0-2 to 0:0-5.
Step 3 Check the fast_io_fail_tmo information.
grep . /sys/class/fc_remote_ports/rport-0\:0-*/fast*
Figure 17-3 Obtaining the fast_io_fail_tmo information
The value of the remote ports' (0:0-2 to 0:0-5) fast_io_fail_tmo parameter is 5.

The configuration has taken effect.
Step 4 Check the dev_loss_tmo information.
grep . /sys/class/fc_remote_ports/rport-0\:0-*/dev_loss*

Figure 17-4 Obtaining the dev_loss_tmo information
The value of the remote ports' (0:0-2 to 0:0-5) dev_loss_tmo parameter is 30. The
configuration has taken effect.
----End
17.2 Why Does the Multipathing Software

Automatically Return to Its Initial Configuration Every
Time RHV-H Restarts?
Symptom
After the RHV-H multipathing software has been configured, the configuration file
will automatically restore its initial configuration every time RHV-H restarts.
Solution
This problem can be found at Red Hat's official website:
https://access.redhat.com/articles/43459
For RHV-H, the first two lines in the multipath.conf file are as follows:
# RHEV REVISION
# RHEV PRIVATE
The two lines must be retained and cannot be deleted.
After the multipath.conf file is configured, run the following command:

persist /etc/multipath.conf
After the command is executed, the configuration data will be retained after the
host is restarted.
17.3 Why Does SLES Enter Emergency Mode After the

Multipathing Software Is Configured?
Symptom
The system enters emergency mode after the SLES multipathing software has
been enabled and the host has restarted.

Solution
This is a known problem with SLES. It can be found at SLES's official website:
The handling procedure is as follows.
Step 1 View local disk information.
In emergency mode, run the multipath -v2 command to view the path
information.
multipath -v2
Dec 18 10:10:03 | 3600508b1001030343841423043300400: ignoring map
Step 2 Add the WWID found in step 1 to the blacklist.
Edit the /etc/multipath.conf file and add the following content to the blacklist.
blacklist {
wwid 3600508b1001030343841423043300400
}
Step 3 Restart the host.
----End
17.4 Why Does the Old Path Information Remain After

an HBA Is Replaced on a XenServer Host?
Symptom
There are eight paths between a XenServer host and the storage system. An HBA
on the host is replaced.
The expected result is that the new HBA will have eight new paths and those of
the original HBA will disappear. However, there are now 16 paths. The original
eight paths remain and their status is faulty.
Solution
Perform the following operations.
Step 1 Close all VMs.
Step 2 Enter maintenance mode.
Step 3 Disable the multipathing software.
Step 4 Enable the multipathing software.
Step 5 Exit maintenance mode.

For details, go to the following website:

http://discussions.citrix.com/topic/361137-xenserver-65-multipath-error-2-of-3-paths-active/
----End
17.5 What Can I Do If I/Os on a VMware 6.0 Host Are

Interrupted After the Replication Link Between the
Storage Systems Goes Down?
Symptom
After the replication link between the storage systems is disconnected, I/Os on a
VMware 6.0 host are interrupted.
Solution
This problem is caused by internal defects of VMware 6.0. VMware's official
website provides an explanation:
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2144657
Upgrade your system to VMware 6.0 U2 to solve this problem.
17.6 What Can I Do If Links Are Not Aggregated in

Linux Due to the Multipathing Software Anomaly?
Symptom
LUNs are mapped to a Linux host on which the multipathing software is properly
configured. However, when the LUNs' path information is checked, it is found that
some links are not aggregated.
Figure 17-5 Links that are not aggregated

In the preceding figure, the links with a priority of 130 are not aggregated, nor are
those with a priority of 10.
Solution
An exception occurred when the multipathing software processed path priorities.
The status of the paths with a priority of 130 should be active rather than
enabled. Run the following command to let the multipathing software identify
the paths again:
multipathd -k"reconfigure"
After this command is executed, the path information becomes normal.
Figure 17-6 Updated path information

Storage Using OS Native Multipathing Software 18 Acronyms and Abbreviations
18 Acronyms and Abbreviations
D
DM-Multipath Device Mapper-Multipath
F
FC Fiber Channel
H
HBA Host Bus Adapter
L
LUN Logical Unit Number
O
ODX Offloaded Data Transfer
P
PID Product ID
V
VID Vendor ID

Hypermetro Configuration Guide For Huawei San Storage Using Os Native Multipathing Software

Uploaded by

Document Information

Original Title

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

Hypermetro Configuration Guide For Huawei San Storage Using Os Native Multipathing Software

Uploaded by

Copyright:

Available Formats

HyperMetro Configuration Guide

for Huawei SAN Storage Using OS

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Indicates a hazard with a high level of risk which, if

Indicates a hazard with a medium level of risk which,

Indicates a hazard with a low level of risk which, if

Indicates a potentially hazardous situation which, if

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. ii

Supplements the important information in the main

CLI Format Conventions

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iii

About This Document................................................................................................................ ii

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iv

4.3 Configuring the Host........................................................................................................................................................... 39

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. v

10.3 Configuring the Host......................................................................................................................................................... 64

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vi

16.2 Configuring Storage Arrays............................................................................................................................................. 93

18 Acronyms and Abbreviations......................................................................................... 104

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vii

1 Impact and Restrictions

HyperMetro using the native multipathing software of an operating system (OS)

1.1 HyperMetro Working Modes

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 1

Table 1-1 HyperMetro working modes

1.1.1 Working Principles and Failover

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 2

Figure 1-1 Load balancing mode

Figure 1-2 Local preferred mode

1.2 Initiator Modes

1.2.1 Initiator Parameter Description

Table 1-2 Initiator parameter description

Parameter Description Example

Uses third-party This parameter is displayed only after an Enabled

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 3

Parameter Description Example

Switchover Mode Path switchover mode Common

● early-version ALUA: default value of

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 4

Parameter Description Example

AIX, Red Hat 7.X, Windows Server

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 5

Parameter Description Example

Path Type The value can be either Optimal Path or Optimal

1.2.2 Configuring the Initiators

Figure 1-3 Going to the host configuration page

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 6

Figure 1-4 Selecting an initiator you want to modify

Figure 1-5 Modifying initiator information

Step 5 Restart the host for the configuration to take effect.

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 7

1.3 Networking Requirements

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 8

2.2 Configuring Storage Arrays

2.2.1 Non-NPIV Mode

Issue 13 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 9

Window Load Local Window Enabled Common N/A Optima