Huawei SAN Storage Host Connectivity Guide For Windows

Huawei SAN Storage Host
Connectivity Guide for Windows
Issue 13
Date 2019-08-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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://www.huawei.com
Email: support@huawei.com
Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. i

Huawei SAN Storage Host Connectivity Guide for
Windows Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Purpose........................................................................................................................................................................... 1
1.2 Audience......................................................................................................................................................................... 1
1.3 Related Documents.........................................................................................................................................................1
1.4 Conventions.................................................................................................................................................................... 2
1.5 Where To Get Help.........................................................................................................................................................3
2 Introduction.................................................................................................................................... 4
2.1 Basic Concepts............................................................................................................................................................... 4
2.1.1 Introduction to Windows Server..................................................................................................................................4
2.1.2 File Systems in Windows............................................................................................................................................ 4
2.2 Host-SAN Connectivity..................................................................................................................................................5
2.2.1 FC Connectivity...........................................................................................................................................................5
2.2.2 iSCSI Connectivity...................................................................................................................................................... 6
2.2.3 Multipath Connectivity................................................................................................................................................7
2.2.3.1 UltraPath................................................................................................................................................................... 7
2.2.3.2 MPIO........................................................................................................................................................................ 7
2.2.3.3 ALUA....................................................................................................................................................................... 8
2.2.4 SAN Boot.................................................................................................................................................................... 9
2.3 Interoperability Query.................................................................................................................................................. 10
2.4 Specifications................................................................................................................................................................11
2.5 Common Management Tools and Commands..............................................................................................................12
2.5.1 Remote Login............................................................................................................................................................ 12
2.5.2 Management Tool...................................................................................................................................................... 14
2.5.3 Disk Management Commands...................................................................................................................................16
3 Planning Connectivity................................................................................................................ 20
3.1 Non-HyperMetro Scenarios..........................................................................................................................................20
3.1.1 Direct-Attached FC Connections...............................................................................................................................20
3.1.2 Fabric-Attached FC Connections.............................................................................................................................. 22
3.1.3 Direct-Attached iSCSI Connections.......................................................................................................................... 25
3.1.4 Fabric-Attached iSCSI Connections..........................................................................................................................28
3.2 HyperMetro Scenarios.................................................................................................................................................. 31
4 Preparing for Configuration......................................................................................................32
Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. ii

Windows Contents
4.1 Switch........................................................................................................................................................................... 32
4.2 Storage System............................................................................................................................................................. 32
4.3 Host...............................................................................................................................................................................32
4.3.1 Identifying HBAs...................................................................................................................................................... 33
4.3.2 Querying HBA Properties......................................................................................................................................... 33
5 Configuring Connectivity.......................................................................................................... 35
5.1 Establishing Fibre Channel Connections......................................................................................................................35
5.1.1 Host Configuration.................................................................................................................................................... 35
5.1.2 (Optional) Switch Configuration............................................................................................................................... 35
5.1.3 Storage System Configuration...................................................................................................................................42
5.2 Establishing iSCSI Connections................................................................................................................................... 46
5.2.1 Host Configuration.................................................................................................................................................... 46
5.2.2 (Optional) Switch Configuration............................................................................................................................... 53
5.2.3 Storage System Configuration...................................................................................................................................55
5.2.4 CHAP Authentication................................................................................................................................................59
5.3 Scanning LUNs on a Host............................................................................................................................................ 67
6 Configuring Multipathing.........................................................................................................68
6.1 Concepts....................................................................................................................................................................... 68
6.1.1 Initiator...................................................................................................................................................................... 68
6.1.2 HyperMetro Working Modes.....................................................................................................................................71
6.1.3 ALUA Working Principles........................................................................................................................................ 72
6.1.3.1 ALUA Working Principles and Failover in Non-HyperMetro Scenarios.............................................................. 72
6.1.3.2 ALUA Working Principles and Failover in HyperMetro Scenarios.......................................................................73
6.2 Configuring Multipathing in Non-HyperMetro Scenarios........................................................................................... 74
6.2.1 UltraPath.................................................................................................................................................................... 74
6.2.1.1 Storage System Configuration................................................................................................................................74
6.2.1.2 Host Configuration................................................................................................................................................. 74
6.2.2 OS Native Multipathing Software............................................................................................................................. 76
6.2.2.3 Verification............................................................................................................................................................. 81
6.3 Configuring Multipathing in HyperMetro Scenarios................................................................................................... 82
6.3.1 UltraPath.................................................................................................................................................................... 82
6.3.1.3 Verification............................................................................................................................................................. 85
6.3.2 OS Native Multipathing Software............................................................................................................................. 86
6.3.2.3 Verification............................................................................................................................................................. 92
7 FAQs...............................................................................................................................................94
Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. iii

Windows Contents
7.1 What Can I Do When Being Prompted to Uninstall MPIO During UltraPath Installation?........................................ 94
7.2 What Are Common Management Commands?............................................................................................................95
7.3 How Do I Change the Windows Disk Timeout Time?................................................................................................. 96
7.4 How Do I Modify the Timeout Time for the FC HBA Port Driver?............................................................................97
7.4.1 Modifying Emulex HBA Driver Parameters............................................................................................................. 97
7.4.2 Modifying QLogic HBA Driver Parameters............................................................................................................. 98
7.5 How Do I Modify the iSCSI Initiator's Driver Timeout Time?..................................................................................101
7.6 How Do I Change the Number of TCP Data Retransmission Times?........................................................................102
8 Acronyms and Abbreviations................................................................................................. 104

9 Appendix A Volume Management........................................................................................ 106
10 Appendix B Host High-Availability.................................................................................... 111
10.1 WSFC........................................................................................................................................................................111
10.1.1 Overview................................................................................................................................................................111
10.1.2 Configuration......................................................................................................................................................... 114
10.2 Veritas VCS...............................................................................................................................................................114
10.2.1 Overview................................................................................................................................................................114
10.2.2 Version Compatibility............................................................................................................................................ 114
10.2.3 Installation and Configuration............................................................................................................................... 115
Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. iv

Windows 1 About This Document
1 About This Document
1.1 Purpose
1.2 Audience
1.3 Related Documents
1.4 Conventions
1.5 Where To Get Help
1.1 Purpose
This document details the configuration methods and precautions for connecting Huawei
SAN storage devices to Windows Server hosts.
1.2 Audience
This document is intended for:
l Huawei technical support engineers
l Technical engineers of Huawei's partners
l Personnel who are involved in interconnecting Huawei SAN and Windows servers or
who are interested in the interconnection.
Readers of this guide are expected to be familiar with the following topics:
l Huawei OceanStor V3, OceanStor V5, and Dorado V3
l Windows Server
1.3 Related Documents

For the hosts, host bus adapters (HBAs), and operating systems that are compatible with
Huawei storage devices, go to support-open.huawei.com.
For the latest Huawei storage product documentation, go to support.huawei.com.
For Windows-related documentation or support, go to https://technet.microsoft.com/en-us/.
Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 1

1.4 Conventions
Symbol Conventions
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in Courier

New.
Command Conventions
Format Description
Boldface The keywords of a command line are in boldface.

Format Description
Italic Command arguments are in italics.
1.5 Where To Get Help

Huawei support and product information can be obtained on the Huawei Online Support site.
Product Information
For documentation, release notes, software updates, and other information about Huawei
products and support, go to the Huawei Online Support site (registration required) at http://
support.huawei.com/enterprise/.
Technical Support
Huawei has a global technical support system, able to offer timely onsite and remote technical
support service.
For assistance, contact:
l Your local technical support
http://e.huawei.com/en/branch-office-query
l Huawei company headquarters.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's
Republic of China
Website: http://e.huawei.com/
Document Feedback
Huawei welcomes your suggestions for improving our documentation. If you have comments,
send your feedback to infoit@huawei.com.

Windows 2 Introduction
2 Introduction
2.1 Basic Concepts

2.2 Host-SAN Connectivity
2.3 Interoperability Query
2.4 Specifications
2.5 Common Management Tools and Commands
2.1 Basic Concepts
2.1.1 Introduction to Windows Server

Windows Server is a Microsoft operating system installed on servers. Each Windows Server
Edition has a corresponding home (workstation) edition, except Windows Server 2003 R2.
2.1.2 File Systems in Windows

Windows Server (Windows for short) offers a variety of file systems. For a comparison, see
Table 2-1.
l FAT
File Application Table (FAT) is a file system developed for MS-DOS. This file system is
simple in design and applicable to all Windows operating systems of later versions.
However, a major drawback of FAT is that after a file is deleted, new data is written onto
the file location in chunks, which lowers data read/write speeds.
l FAT32
FAT32 is similar to FAT but applies to larger disk applications. FAT supports only 4 GB
partitions or volumes whereas FAT32 supports up to 2 TB.
l NTFS
New Technology File System (NTFS) is a standard file system that applies to Windows
NT, Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008,
Windows Vista, and Windows 7. NTFS takes the place of FAT as the file system for
Microsoft Windows operating systems. NTFS optimizes FAT and High Performance File
System (HPFS). For example, NTFS supports metadata and uses advanced data

structure, which improves performance, reliability, and disk space utilization. NTFS also
provides extended functions such as the access control list (ACL) and file system logs.
l exFAT
Extended File Allocation Table File System (exFAT) is a Microsoft file system optimized
for flash drives (NFTS cannot be used to manage flash drives). exFAT applies to
Windows Embedded 5.0 and later (including Windows CE 5.0, Windows CE 6.0,
Windows Mobile 5, Windows Mobile 6, and Windows Mobile 6.1). This file system
supports 4 GB or larger files that are not supported by FAT32.
l ReFS
Resilient File System (ReFS) is a new file system introduced with Windows Server
2012. ReFS improves system availability and fault tolerance capabilities in the big data
era. When interworking with Space Storage, ReFS provides a comprehensive, end-to-
end, and flexible storage architecture.
Table 2-1 Comparison of FAST32, NTFS, exFAT, and ReFS
Specifications FAT32 NTFS exFAT ReFS
Operating Versions later Versions later Windows CE 6/ Versions later

system than Windows than Windows Vista SP1 than Windows
95 OSR2 2000 2012
Min. sector size 512 B 512 B 512 B 64 KB
Max. sector size 64 KB 64 KB 64 KB 64 KB
Max. file size 2 B to 4 GB Depends on the 16 EB 16 EB

max. partition
capacity.
Max. formatted 2 TB (NT 2 TB to 256 TB 16 EB 256 ZB when

capacity kernel: 32 GB) (depending on (theoretical using 16 KB
the MBR) value, 256 TB clusters.
in current Windows stack
environments) addressing: 16
EB
Number of 4,194,304 None Greater than -

archives 1000
2.2 Host-SAN Connectivity
2.2.1 FC Connectivity
A Fibre Channel (FC) SAN is a specialized high-speed network that connects host servers to
storage systems. The FC SAN components include HBAs in the host servers, switches that
help route storage traffic, cables, storage processors (SPs), and storage disk arrays.
To transfer traffic from host servers to shared storage, the FC SAN uses the Fibre Channel
protocol to package SCSI commands into Fibre Channel frames.

l Ports in FC SAN
Each node in the SAN, such as a host, a storage device, or a fabric component has one or
more ports that connect it to the SAN. Ports are identified in a number of ways, such as
by:
– World Wide Port Name (WWPN)
A globally unique identifier for a port that allows certain applications to access the
port. The FC switches discover the WWPN of a device or host and assign a port
address to the device.
– Port_ID (or port address)
Within a SAN, each port has a unique port ID that serves as the FC address for the
port. This unique ID enables routing of data through the SAN to that port. The FC
switches assign the port ID when the device logs in to the fabric. The port ID is
valid only when the device is logged on.
l Zoning
Zoning provides access control in the SAN topology. Zoning defines which HBAs can
connect to which targets. When you configure a SAN by using zoning, the devices
outside a zone are not visible to the devices inside the zone.
Zoning has the following effects:
– Reduces the number of targets and LUNs presented to a host.
– Controls and isolates paths in a fabric.
– Separates different environments, for example, a test from a production
environment.
2.2.2 iSCSI Connectivity

In computing, Internet Small Computer Systems Interface (iSCSI) is an IP-based storage
networking standard for linking data storage systems.
By carrying SCSI commands over IP networks, iSCSI is used to access remote block devices
in the SAN, providing hosts with the illusion of locally attached devices.
A single discoverable entity on the iSCSI SAN, such as an initiator or a target, represents an
iSCSI node.
Each iSCSI node can be identified in a number of ways, such as by:
l IP address
Each iSCSI node can have an IP address associated with it so that routing and switching
equipment on your network can establish the connection between the server and storage.
This address is just like the IP address that you assign to your computer to get access to
your company's network or the Internet.
l iSCSI name
A worldwide unique name for identifying the node. iSCSI uses the iSCSI Qualified
Name (IQN) and Extended Unique Identifier (EUI).
By default, Windows generates unique iSCSI names for your iSCSI initiators, for
example, iqn.1991-05.com.microsoft:win-pjcqrusvvl9. The default value is retained in
most situations. If the value needs to be changed, ensure that the new iSCSI entered is
worldwide unique

2.2.3 Multipath Connectivity
2.2.3.1 UltraPath
UltraPath is a Huawei-developed multipathing software. It can manage and process disk
creation/deletion and I/O delivery of operating systems.
UltraPath provides the following functions:
l Masking of redundant LUNs
In a redundant storage network, an application server with no multipathing software
detects a LUN on each path. Therefore, a LUN mapped through multiple paths is
mistaken for two or more different LUNs. UltraPath installed on the application server
masks redundant LUNs on the operating system driver layer to provide the application
server with only one available LUN, the virtual LUN. In this case, the application server
only needs to deliver data read and write operations to UltraPath. UltraPath then masks
the redundant LUNs, and writes data into LUNs without damaging other data.
l Optimum path selection
In a multipath environment, the owning controller of the LUN on the storage system
mapped to an application server is the prior controller. With UltraPath, an application
server accesses the LUN on the storage system through the prior controller, thereby
obtaining the highest I/O speed. The path to the prior controller is the optimum path.
l Failover and failback
– Failover
When a path fails, UltraPath fails over its services to another functional path.
– Failback
UltraPath automatically delivers I/Os to the first path again after the path recovers
from the fault.
l I/O Load balancing
UltraPath provides load balancing within a controller and across controllers.
– For load balancing within a controller, I/Os poll among all the paths of the
controller.
– For load balancing across controllers, I/Os poll among the paths of all these
controllers.
l Path test
UltraPath tests faulty and idle paths:
– Faulty paths
UltraPath frequently tests faulty paths to detect the path recovery as soon as
possible.
– Idle paths
UltraPath tests idle paths to identify potentially faulty paths early on, preventing
unnecessary I/O retries. The test frequency is kept low to minimize impact on
service I/Os.
2.2.3.2 MPIO
Windows Microsoft Multi-Path IO (MPIO) allows storage vendors to develop multipathing
solutions that contain the hardware-specific information needed to optimize connectivity with

storage systems. MPIO can be used independently. This software helps balance loads among
multiple paths, and implement path selection and failover between storage systems and hosts.
MPIO supports the following policy settings:
l Failover Only
This policy does not perform load balancing. This policy uses a single active path, and
the rest of the paths are standby paths. The active path is used for sending all I/Os. If the
active path fails, then one of the standby paths is used. When the failed path is
reactivated or reconnected, the standby path that was activated returns to standby.
l Round Robin
This load balancing policy allows the Device Specific Module (DSM) to use all available
paths for MPIO in a balanced way. This is the default policy that is chosen when the
storage controller follows the active-active model and the management application does
not specifically choose a load balancing policy.
l Round Robin with Subset
This load balancing policy allows the application to specify a set of paths to be used in a
round robin fashion, and with a set of standby paths. The DSM uses paths from a
primary path pool for processing requests as long as at least one of the paths is available.
The DSM uses a standby path only when all the primary paths fail. For example, given 4
paths: A, B, C, and D, paths A, B, and C are listed as primary paths and D is the standby
path. The DSM chooses a path from A, B, and C in round robin fashion as long as at
least one of them is available. If all three paths fail, the DSM uses D, the standby path. If
paths A, B, or C become available, the DSM stops using path D and switches to the
available primary paths.
l Least Queue Depth
This load balancing policy sends I/O down the path with the fewest currently outstanding
I/O requests. For example, consider that there is one I/O sent to LUN 1 on Path 1, and
the other I/O is sent to LUN 2 on Path 1. The cumulative outstanding I/O on Path 1 is 2,
and on Path 2 is 0. Therefore, the next I/O for either LUN will process on Path 2.
l Weighed Paths
This load balancing policy assigns a weight to each path. The weight indicates the
relative priority of a given path. The larger the number, the lower ranked the priority. The
DSM chooses the least-weighted path from among the available paths.
l Least Blocks
This load balancing policy sends I/O down the path with the least number of data blocks
currently being processed. For example, consider that there are two I/Os: one is 10 bytes
and the other is 20 bytes. Both are in process on Path 1, and there are no outstanding I/Os
on Path 2. The cumulative outstanding amount of I/O on Path 1 is 30 bytes. On Path 2, it
is 0. Therefore, the next I/O will process on Path 2.
2.2.3.3 ALUA
l ALUA definition
Asymmetric Logical Unit Access (ALUA) is a multi-target port access model. In a
multipathing state, the ALUA model provides a way of presenting active/passive LUNs
to a host and offers a port status switching interface to switch over the working
controller. For example, when a host multipathing program that supports ALUA detects a
port status change (the port becomes unavailable) on a faulty controller, the program will
automatically switch subsequent I/Os to the other controller.

l Support by Huawei storage

Old-version Huawei storage supports ALUA only in dual-controller configuration, but
not in multi-controller or HyperMetro configuration.
New-version Huawei storage supports ALUA in dual-controller, multi-controller, and
HyperMetro configurations.
Table 2-2 defines old- and new-version Huawei storage.
Table 2-2 Old- and new-version Huawei storage

Storage Type Version Remarks
Old-version Huawei T V1, T V2, 18000 V1, -

storage (namely, V300R001, V300R002,
storage that does not V300R003C00, V300R003C10,
support multi- V300R005, and Dorado
controller ALUA or V300R001C00
ALUA HyperMetro)
New-version Huawei V300R003C20, V300R006C00, V300R003C20: refers to

storage (namely, V500R007C00, Dorado only V300R003C20SPC200
storage that supports V300R001C01, and later versions and later versions.
multi-controller ALUA V300R006C00: refers to
and ALUA only V300R006C00SPC100
HyperMetro) and later versions.
Dorado V300R001C01:
refers to only
V300R001C01SPC100 and
later versions.
l ALUA impacts
ALUA is applicable to a storage system that has only one prior LUN controller. All host
I/Os can be routed through different controllers to the working controller for execution.
ALUA will instruct the hosts to deliver I/Os preferentially from the LUN working
controller, thereby reducing the I/O routing-consumed resources on the non-working
controllers.
If all I/O paths of the LUN working controller are disconnected, the host I/Os will be
delivered only from a non-working controller and then routed to the working controller
for execution.
l Suggestions for using ALUA on Huawei storage
To prevent I/Os from being delivered to a non-working controller, you are advised to
ensure that:
– LUN home/working controllers are evenly distributed on storage systems so that
host service I/Os are delivered to multiple controllers for load balancing.
– Hosts always try the best to select the optimal path to deliver I/Os even after an I/O
path switchover.
2.2.4 SAN Boot

SAN Boot is a network storage management system that stores data (including servers'
operating systems) totally on storage systems. Specifically, operating systems are installed on

and booted from SAN storage devices. SAN Boot is also called Remote Boot or boot from
SAN.
SAN Boot can help to improve system integration, enable centralized management, and
facilitate recovery.
l Server integration: Blade servers are used to integrate a large number of servers within a
small space. There is no need to configure local disks.
l Centralized management: Boot disks of servers are centrally managed on a storage
device. All advanced management functions of the storage device can be fully utilized.
For example, the snapshot function can be used for backup. Devices of the same model
can be quickly deployed using the snapshot function. In addition, the remote replication
function can be used for disaster recovery.
l Quick recovery: Once a server that is booted from SAN fails, its boot volume can be
quickly mapped to another server, achieving quick recovery.
2.3 Interoperability Query

When connecting a storage system to a Windows host, consider the interoperability of upper-
layer applications and components (such as storage systems, Windows systems, HBAs, and
switches) in the environment.
You can query the latest compatibility information by performing the following steps:
Step 1 Log in to the website support-open.huawei.com.
Step 2 On the home page, choose Interoperability Center > Storage Interoperability.
Figure 2-1 Interoperability query page
The Huawei Storage Interoperability Navigator is displayed.

Step 3 Select the components to query and click Submit.

Figure 2-2 Query on Huawei Storage Interoperability Navigator
----End
2.4 Specifications
Windows has different specifications for LUNs and file systems. Table 2-3 lists the
limitations on the number of LUNs. Table 2-4 lists specifications of NTFS with GPT disks.
Table 2-3 Number of LUNs

OS OS Kernel Limitation HBA Limitation
Windows Server 2008 l 8 buses per adapter 4096 LUNs per target
Windows Server 2008 R2 l 128 target IDs per bus (Emulex)
l 255 LUNs per target ID 256 LUNs per target
(QLogic)
Windows Server 2012 and l 255 buses per adapter 4096 LUNs per target
later versions l 128 target IDs per bus (Emulex)
l 255 LUNs per target ID 256 LUNs per target
(QLogic)

NOTE
You can obtain more HBA limitations from its manufacturer.
Table 2-4 Specifications of NTFS with GPT disks

Allocation Unit Size Max. NTFS Volume Size
512 2,199,023,255,040 (2 TB)
1024 4,398,046,510,080 (4 TB)
2048 8,796,093,020,160 (8 TB)
4096 17,592,186,040,320 (16 TB)
8192 35,184,372,080,640 (32 TB)
16,384 70,368,744,161,280 (64 TB)
32,768 140,737,488,322,560 (128 TB)
65,536 281,474,976,645,120 (256 TB)
Table 2-4 lists only part of NTFS specifications. For more information about specifications of
each file system, see the corresponding Microsoft document, for example, NTFS Overview.
2.5 Common Management Tools and Commands

You need to remotely log in to a Windows host and run management commands on the host.
The following details the login method, management tools, and management commands.
2.5.1 Remote Login

To manage a host using the remote desktop, perform the following steps:
Step 1 Ensure that the network connectivity is normal between the client host and the managed host.
Step 2 Configure the firewall on the managed host.

Click Start and choose Administrative Tools > Windows Firewall with Advanced
Security. On the firewall configuration page that is displayed, enable Remote Desktop
(TCP-In) and File and Printer Sharing (Echo Request – ICMPv4-In) in Inbound Rules,
as shown in Figure 2-3.

Figure 2-3 Firewall configuration
Inbound rules refer to rules for receiving network information. After Remote Desktop (TCP-
In) is enabled, other devices can access the managed host through the remote desktop. After
File and Printer Sharing (Echo Request – ICMPv4-In) is enabled, other devices on the
network can ping the managed host to check network connectivity.
To prevent security risks, you are advised to restore firewall configurations to the initial state
after completing host commissioning.
Step 3 Ping each other's IP address on the client host and the managed host respectively to verify
firewall configurations.
Step 4 Configure the remote login level on the managed host.
Right-click My Computer and choose Properties from the shortcut menu. In the dialog box
that is displayed, click Change Settings. In the dialog box that is displayed, click the Remote
tab. In Remote Desktop, select Allow Connections from computers running any version
of Remote Desktop (less secure).
Step 5 On the client host, enter mstsc in the Run window to start the remote desktop connection, as
shown in Figure 2-4.

Figure 2-4 Remote desktop connection
Step 6 In the remote desktop connection dialog box that is displayed, enter the IP address of the
managed host.
Step 7 Enter the username and password of the managed host.
----End
2.5.2 Management Tool

Windows provides a powerful computer management tool Server Manager. This tool provides
most host management functions, such as configuring system features, viewing system logs,
managing system services, and monitoring system performance.
This section describes how to start Server Manager and use this tool to manage disks.
Starting Server Manager

To start Server Manager, perform the following steps:
Step 1 On the host, click Start.
Step 2 Right-click Computer and choose Manage from the shortcut menu.
Server Manager is started, as shown in Figure 2-5.

Figure 2-5 Server Manager
Step 3 In the navigation tree, choose Storage > Disk Management.

The disks available for management are displayed.
----End
Managing Disks
You can use Server Manager to manage storage resources, such as initializing disks,
partitioning disks, formatting disks, and managing volumes.
In Windows Server 2008 and later versions, you need to set the state of LUNs mapped to the
host for the first time to online in Disk Management. The operating system then marks the
LUNs for identification. This process is disk initialization. Only the initialized disks can be
used by the host in volume management. You need to specify disk partition format when
initializing disks. Available formats are:
l Master Boot Record (MBR)
l GUID Partition Table (GPT)
NOTE
In versions earlier than Windows Server 2008, you do not need to set a disk online or specify partition
format. The system uses the default format MBR.
The partition format refers to the method of organizing disk partitions in Windows XP Professional and
Windows Server 2003. For details, see:
https://www.microsoft.com/en-US/download/details.aspx?id=53314
In Windows, disks are categorized as basic and dynamic disks. Only simple volumes can be
created on basic disks. Spanned volumes, mirror volumes, striped volumes, and RAID-5
volumes are created on dynamic disks. In Windows Server 2008 and later versions, the

operating system converts basic disks to dynamic disks when spanned volumes (or other
volumes that can only be created on dynamic disks) are created on basic disks.
2.5.3 Disk Management Commands

Although Windows is a GUI-based operating system, it also provides the powerful diskpart
MS-DOS management commands. The diskpart disk management module can complete all
operations under Disk Management.
Figure 2-6 shows the diskpart commands.
Figure 2-6 diskpart commands in GUI
The preceding commands show the process that three LUNs are initialized and then used to
create a RAID-5 volume.
Step 1 Scan for LUNs.

DISKPART> rescan
Please wait while DiskPart scans your configuration...

DiskPart has finished scanning your configuration.
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt

-------- ------------- ------- ------- --- ---
Disk 0 Online 279 GB 0 B
Disk 1 Online 279 GB 4094 MB
Disk 2 Offline 5120 MB 5120 MB
Disk 3 Offline 10 GB 0 B *
Step 2 Set the state of the LUNs mapped to the host for the first time to online.
DISKPART> select disk 2
Disk 2 is now the selected disk.
DISKPART> online disk
DiskPart successfully onlined the selected disk.
DISKPART> list disk

-------- ------------- ------- ------- --- ---
* Disk 2 Online 5120 MB 5120 MB
DISKPART> list disk

-------- ------------- ------- ------- --- ---
Disk 2 Online 5120 MB 5120 MB
* Disk 3 Online 10 GB 0 B *
DISKPART> list disk

-------- ------------- ------- ------- --- ---
Disk 2 Online 5120 MB 5120 MB
Disk 3 Online 10 GB 0 B *
* Disk 4 Online 20 GB 0 B *
Step 3 Convert disks to dynamic disks.

DISKPART> convert dynamic
DiskPart successfully converted the selected disk to dynamic format.
Step 4 Create a RAID 5 volume.

DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 System Rese NTFS Partition 350 MB Healthy System
Volume 1 C NTFS Partition 160 GB Healthy Boot
DISKPART> create volume raid size=50 disk=2,3,4
DiskPart successfully created the volume.

---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 2 RAW RAID-5 100 MB Healthy
Step 5 Format the volume.

DISKPART> format
100 percent completed
DiskPart successfully formatted the volume.

---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 2 NTFS RAID-5 100 MB Healthy
Step 6 Mount the file system.

DISKPART> assign
DiskPart successfully assigned the drive letter or mount point.

---------- --- ----------- ----- ---------- ------- --------- --------


* Volume 2 D NTFS RAID-5 100 MB Healthy
NOTE
Compared with the GUI-based disk management, the CLI disk management commands in Windows are
complex. However, those CLI commands are useful in automatic management and tests.
----End

Windows 3 Planning Connectivity
3 Planning Connectivity
Windows hosts and storage systems can be connected based on different criteria. Table 3-1
describes the typical connection modes.
Table 3-1 Connection modes
Criteria Connection Mode
Interface module type Fibre Channel connection/iSCSI connection
Whether switches are used Direct-attached connection (no switches are

used)/Fabric-attached connection (switches
are used)
Whether multiple paths exist Single-path connection/Multi-path

connection
Whether HyperMetro is configured HyperMetro/Non-HyperMetro
Fibre Channel connections are the most widely used. To ensure service data security, both
direct-attached connections and fabric-attached connections require multiple paths.
The following details Fibre Channel and iSCSI connections in HyperMetro and non-
HyperMetro scenarios.
3.1 Non-HyperMetro Scenarios
3.2 HyperMetro Scenarios
3.1 Non-HyperMetro Scenarios
3.1.1 Direct-Attached FC Connections

Huawei provides dual-controller and multi-controller storage systems, which directly connect
to Windows hosts through FC multi-path connections in different ways.

Two-Controller Storage
The following uses Huawei OceanStor 5500 V3 as an example to explain how to directly
connect a Windows host to a two-controller storage system through FC multi-path
connections, as shown in Figure 3-1.
Figure 3-1 Direct-attached FC multi-path connections (two-controller storage)
NOTE
In this connection diagram, each of the two controllers is connected to a host HBA port with an optical
fiber. The cable connections are detailed in Table 3-2.
Table 3-2 Cable connection description (two-controller storage)

Cable No. Description
1 Connects Port P0 on the Windows host to Controller

A on the storage system.

B on the storage system.
Multi-Controller Storage
The following uses Huawei OceanStor 18800 V3 (four-controller) as an example to explain
how to directly connect a Windows host to a multi-controller storage system through FC
multi-path connections, as shown in Figure 3-2.

Figure 3-2 Direct-attached FC multi-path connections (four-controller storage)
NOTE
In this connection diagram, each of the four controllers is connected to a host HBA port with an optical
fiber. The cable connections are detailed in Table 3-3.
Table 3-3 Cable connection description (four-controller storage)

Cable No. Description

A on the storage system.

B on the storage system.

C on the storage system.

D on the storage system.
3.1.2 Fabric-Attached FC Connections

Huawei provides dual-controller and multi-controller storage systems, which connect to
Windows hosts through FC multi-path connections using a switch in different ways.

The following uses Huawei OceanStor 5500 V3 as an example to explain how to connect a
Windows host to a two-controller storage system through FC multi-path connections using a
switch, as shown in Figure 3-3.
Figure 3-3 Fabric-attached FC multi-path connections (dual-controller storage)
NOTE
In this connection diagram, two controllers of the storage system and two ports of the Windows host are
connected to the FC switch through optical fibers. On the FC switch, the ports connecting to the storage
controllers and to the Windows host are grouped in a zone, ensuring connectivity between the host ports
and the storage.
Table 3-4 Zone division on the FC switch (two-controller storage)

Zone Name Zone Members Zone Description
Zone001 Ports 1 and 2 Connects Port P0 on the Windows host to

Controller A on the storage system.

Controller B on the storage system.


NOTE
Zone division in this table is for reference only. Plan zones based on site requirements.

how to connect a Windows host to a multi-controller storage system through FC multi-path
connections using a switch, as shown in Figure 3-4.
Figure 3-4 Fabric-attached FC multi-path connections (four-controller storage)
NOTE
In this connection diagram, four controllers of the storage system and two ports of the Windows host are
connected to the FC switch through optical fibers. On the FC switch, the ports connecting to the storage
controllers and to the Windows host are grouped in a zone, ensuring connectivity between the host ports
and the storage.
Table 3-5 Zone division on the FC switch (four-controller storage)




Controller C on the storage system.

Controller D on the storage system.



Controller C on the storage system.

Controller D on the storage system.
NOTE
Zone division in this table is for reference only. Plan zones based on site requirements.
3.1.3 Direct-Attached iSCSI Connections

Huawei provides dual-controller and multi-controller storage systems, which directly connect
to Windows hosts through iSCSI multi-path connections in different ways.
The following uses Huawei OceanStor 5500 V3 as an example to explain how to directly
connect a Windows host to a two-controller storage system through iSCSI multi-path
connections, as shown in Figure 3-5.
Figure 3-5 Direct-attached iSCSI multi-path connections (two-controller storage)

NOTE
In this connection diagram, each of the two controllers is connected to a port on the host network adapter
with a network cable. The IP address plan is detailed in Table 3-6.
Table 3-6 IP address plan for direct-attached iSCSI multi-path connections (two-controller
storage)
Port Name Port Description IP Address Subnet Mask
Host.P0 Connects the Windows host to 192.168.5.5 255.255.255.0

Controller A on the storage
system.

Controller B on the storage
system.
Storage.A.P0 Connects Controller A on the 192.168.5.6 255.255.255.0

storage system to the Windows
host.
Storage.B.P0 Connects Controller B on the 192.168.6.6 255.255.255.0

host.
NOTE
IP addresses in this table are for reference only. Plan IP addresses based on site requirements.
how to directly connect a Windows host to a multi-controller storage system through iSCSI
multi-path connections, as shown in Figure 3-6.

Figure 3-6 Direct-attached iSCSI multi-path connections (four-controller storage)
NOTE
In this connection diagram, each of the four controllers is connected to a port on host network adapters
with a network cable. The IP address plan is detailed in Table 3-7.
Table 3-7 IP address plan for direct-attached iSCSI multi-path connections (four-controller
storage)

system.

system.

Controller C on the storage
system.

Controller D on the storage
system.

host.


host.
Storage.C.P0 Connects Controller C on the 192.168.7.6 255.255.255.0

host.
Storage.D.P0 Connects Controller D on the 192.168.8.6 255.255.255.0

host.
NOTE
3.1.4 Fabric-Attached iSCSI Connections

Huawei provides dual-controller and multi-controller storage systems, which connect to
Windows hosts through Ethernet switches in different ways.
The following uses Huawei OceanStor 5500 V3 as an example to explain how to connect a
Windows host to a two-controller storage system through iSCSI multi-path connections using
an Ethernet switch, as shown in Figure 3-7.
Figure 3-7 Fabric-attached iSCSI multi-path connections (two-controller storage)

NOTE
In this connection diagram, two controllers of the storage system and two ports of the Windows host
network adapter are connected to the Ethernet switch through network cables. IP addresses of the ports
on the storage and host are in the same subnet, ensuring connectivity between the host ports and the
storage.
Table 3-8 IP address plan for fabric-attached iSCSI multi-path connections (two-controller
storage)

system.

system.

host.

host.
NOTE
how to connect a Windows host to a multi-controller storage system through iSCSI multi-path
connections using an Ethernet switch, as shown in Figure 3-8.

Figure 3-8 Fabric-attached iSCSI multi-path connections (four-controller storage)
NOTE
In this connection diagram, four controllers of the storage system and four ports of the Windows host
network adapters are connected to the Ethernet switch through network cables. IP addresses of the ports
on the storage and host are in the same subnet, ensuring connectivity between the host ports and the
storage.
Table 3-9 IP address plan for fabric-attached iSCSI multi-path connections (four-controller
storage)

system.

system.

Controller C on the storage
system.


Controller D on the storage
system.

host.

host.
Storage.C.P0 Connects Controller C on the 192.168.7.6 255.255.255.0

host.
Storage.D.P0 Connects Controller D on the 192.168.8.6 255.255.255.0

host.
NOTE
3.2 HyperMetro Scenarios

For details about how to plan connectivity in HyperMetro scenarios, see the BC&DR
Solution Product Documentation (Active-Active Data Center).

Windows 4 Preparing for Configuration
4 Preparing for Configuration
This chapter describes the preparations on the switches, storage systems, and hosts.
4.1 Switch
4.2 Storage System
4.3 Host
4.1 Switch
Ensure that the switches are functioning properly and their ports have the necessary licenses
and transmit data normally. Refer to the switch vendor's documentation for details on how to
check functionality and license status for the switches in your environment. Figure 4-1 shows
an example of a port failure due to lack of a license.
Figure 4-1 Switch port status
4.2 Storage System

Create disk domains, storage pools, LUNs, hosts, and mapping views on the storage system
according to your service requirements. For details about these operations, see the Basic
Storage Service Configuration Guide corresponding to your storage system.
4.3 Host
Before connecting a host to a storage system, make sure that the host HBAs have been
identified and are functioning properly. You also need to obtain the world wide names
(WWNs) of HBA ports for subsequent storage system configurations.

4.3.1 Identifying HBAs

After an HBA is installed on a host, you can view whether the HBA exists in Device
Manager. If the HBA exists, the physical connection of the HBA is correct. Then check
whether there is a question mark or exclamation mark on the HBA name. If there is no such
mark, the HBA driver is normal.
Figure 4-2 Checking HBA installation in Device Manager
4.3.2 Querying HBA Properties

After an HBA is installed on a host and the host is powered on, open Device Manager to
check whether the HBA has been identified and whether the driver needs to be installed
manually. More refined management of the HBA requires installation of management
software particular to the HBA.
Table 4-1 lists the management tools of mainstream HBAs.
Table 4-1 Management tools of mainstream HBAs

Vendor Management Software
QLogic Sansurfer
Emulex OneCommand Manager
Brocade Brocade Adapter Software
ATTO Windows Host Adapter Utilities

Windows also provides a Fibre Channel Information Tool for discovery of SAN resources,
which is available at:
http://www.microsoft.com/en-us/download/details.aspx?id=17530
After the software is installed, run fcinfo in the Command Prompt to obtain the HBA
information. Figure 4-3 provides an example.
Figure 4-3 Running the fcinfo command to query HBA information
For Windows Server 2012 and later versions, Windows PowerShell provides the Get-
InitiatorPort command to query the information about WWNs and iSCSI initiators of FC
HBAs. Figure 4-4 shows an example.
Figure 4-4 Querying the FC HBA and iSCSI initiator information in Windows Server 2016

Windows 5 Configuring Connectivity
5 Configuring Connectivity
5.1 Establishing Fibre Channel Connections

5.2 Establishing iSCSI Connections
5.3 Scanning LUNs on a Host
5.1 Establishing Fibre Channel Connections

This section describes how to establish Fibre Channel connections between application
servers and storage systems.
5.1.1 Host Configuration

Query the HBA WWNs. Figure 5-1 provides an example.
Figure 5-1 Querying the HBA WWNs
5.1.2 (Optional) Switch Configuration

Skip this section if you use direct-attached connections.
The following uses a Brocade switch as an example to explain how to configure switches.
Querying the Switch Model and Version

To query the switch model and version, perform the following steps:
Step 1 Log in to the Brocade switch from a web page.

1. On the web browser, enter the IP address of the Brocade switch and press Enter.

2. In the Web Tools login dialog box displayed, enter the account and password.
The default account and password are admin and password.
Web Tools works properly only when Java is installed on the host. Java 1.6 or later is
recommended.
Step 2 On the switch management page that is displayed, click Switch Information.
Figure 5-2 displays example information.
Figure 5-2 Switch information
Major parameters are described as follows:
l Fabric OS version indicates the switch version. The interoperability between switches
and storage systems varies with the switch version. Use only switches with verified
interoperability.
l Type is a decimal consisting of an integer and a decimal fraction. The integer indicates
the switch model and the decimal fraction indicates the switch template version. You
only need to pay attention to the switch model. Table 5-1 describes mapping between
switch types and names.
l Ethernet IPv4 indicates the switch IP address.
l Effective configuration indicates the currently effective configurations. This parameter
is critical to subsequent zone configurations. In this example, the currently effective
configuration is ss.

Table 5-1 Mapping between switch types and names

Switch Switch Name Switch Switch Name
Type Type
1 Brocade 1000 Switch 64 Brocade 5300 Switch
2, 6 Brocade 2800 Switch 66 Brocade 5100 Switch
3 Brocade 2100, 2400 Switches 67 Brocade Encryption Switch
4 Brocade 20x0, 2010, 2040, 69 Brocade 5410 Blade

2050 Switches
5 Brocade 22x0, 2210, 2240, 70 Brocade 5410 Embedded

2250 Switches Switch
9 Brocade 3800 Switch 72 Brocade 5480 Embedded

Switch
10 Brocade 12000 Director 73 Brocade 5470 Embedded

Switch
12 Brocade 3900 Switch 75 Brocade M5424 Embedded

Switch
17 Brocade 3800VL 77 Brocade DCX-4S Backbone
18 Brocade 3000 Switch 83 Brocade 7800 Extension

Switch
21 Brocade 24000 Director 86 Brocade 5450 Embedded

Switch

Switch

Switch
27 Brocade 3250 Switch 92 Brocade VA-40FC Switch
29 Brocade 4012 Embedded 95 Brocade VDX 6720-24 Data

Switch Center Switch
32 Brocade 4100 Switch 96 Brocade VDX 6730-32 Data

Center Switch
33 Brocade 3014 Switch 97 Brocade VDX 6720-60 Data

Center Switch
34 Brocade 200E Switch 98 Brocade VDX 6730-76 Data

Center Switch

Switch Switch Name Switch Switch Name

Type Type
37 Brocade 4020 Embedded 108 Dell M8428-k FCoE

Switch Embedded Switch
38 Brocade 7420 SAN Router 109 Brocade 6510 Switch
40 Fibre Channel Routing (FCR) 116 Brocade VDX 6710 Data

Front Domain Center Switch
41 Fibre Channel Routing, 117 Brocade 6547 Embedded

(FCR) Xlate Domain Switch
42 Brocade 48000 Director 118 Brocade 6505 Switch
43 Brocade 4024 Embedded 120 Brocade DCX 8510-8

Switch Backbone
44 Brocade 4900 Switch 121 Brocade DCX 8510-4

Backbone
45 Brocade 4016 Embedded 124 Brocade 5430 Switch

Switch

Switch
55.2 Brocade 7600 Switch 130 Brocade M6505 Switch

Switch
62 Brocade DCX Backbone 148 Brocade 7840 Switch
----End
Configuring Zones
Zone configuration is important for Fibre Channel switches. The configurations differ with
the switch vendor, model, and version. For details, refer to the configuration guide specific to
the switch used in your layout. The following uses the Brocade 6510 switch as an example to
explain the zone configuration procedure.
Step 1 Log in to the Brocade switch on a web browser.

1. On the web browser, enter the IP address of the Brocade switch and press Enter.
The Web Tools switch login dialog box is displayed.
2. Enter the account and password (admin and password by default) to log in.
Step 2 Check the port status on the switch.

In normal conditions, port indicators on the switch are steady green after the corresponding
ports have been connected to hosts and storage arrays using optical fibers. The example
illustrated in Figure 5-3 uses ports 0, 1, 4, and 5.
Figure 5-3 Port status
Step 3 Go to the Zone Admin page.
Choose Configure > Zone Admin from the main menu of Web Tools.
Figure 5-4 Zone Admin page
Step 4 Check whether the switch has identified hosts and storage systems.
On the Zone Admin page, click the Zone tab. In Member Selection List, check whether all
related ports have been identified, as shown in Figure 5-5.
Figure 5-5 Identified ports

In this example, the hosts use ports 0 and 1, while the storage systems use ports 4 and 5. The
display indicates that the switch has correctly identified the devices connected by the four
ports.
Step 5 Create zones.
On the Zone tab page, click New Zone and enter a name (Zone001 in this example). Add
port 0 (connecting to port P0 of a host) and port 4 (connecting to controller A of a storage
system) to this zone, as shown in Figure 5-6.
Figure 5-6 Creating a zone
Use the same method to create Zone002 to Zone004. Add ports 1 and 5 to Zone0002, ports 0
and 5 to Zone003, and ports 1 and 4 to Zone004.
Step 6 Add the new zones to the configuration file and activate them.
On the Switch View tab page, identify the effective configuration file, as shown in Figure
5-7.

Figure 5-7 Effective configuration file
On the Zone Admin page, click the Zone Config tab. In the Name drop-down list, choose
the effective configuration file New_config.
In Member Selection List, select Zone001 to Zone004 and add them to the configuration
file.
Click Save Config to save the configuration and then click Enable Config for the
configuration to take effect.
Figure 5-8 shows the configuration on the GUI.

Figure 5-8 Adding zones to the configuration file
Step 7 Verify that the configuration has taken effect.
On the Name Server tab page, verify that the ports have been added to the zones and the
zones have taken effect (marked * in the upper right corner), as shown in Figure 5-9.
Figure 5-9 Verifying the configuration
----End
5.1.3 Storage System Configuration

This section details how to add initiators to hosts on the storage system. For other storage
configurations, see the Basic Storage Service Configuration Guide corresponding to your
storage system.
Step 1 Log in to the storage system on a web browser.
After you have configured the zones on the switch, log in to DeviceManager of the storage
system and choose Provisioning > Host > Initiator. On the page that is displayed, select FC
from the Initiator Type drop-down list. Check whether the host initiators have been
discovered.
As shown in Figure 5-10, the host initiators have been discovered and are online.

Figure 5-10 Viewing initiators
Step 2 Click the Host tab, select the host that was created on the storage system, and click Add
Initiator.
Figure 5-11 Add Initiator dialog box
Step 3 Select FC from the Initiator Type drop-down list and find the host initiators' WWNs.

Figure 5-12 Selecting initiators
Step 4 Select the host initiators and add them to Selected Initiators.

Figure 5-13 Adding initiators
Step 5 Verify that the initiators have been added to the host correctly.
Figure 5-14 Verifying the configuration

As shown in Figure 5-14, the initiators have been added to the host successfully. The initiator
properties depend on the operating system and multipathing software used by the hosts. For
details, see storage configurations in 6 Configuring Multipathing.
----End
5.2 Establishing iSCSI Connections

This section describes how to establish iSCSI connections between application servers and
storage systems.
5.2.1 Host Configuration

Checking iSCSI Software on a Host
For Windows Server 2008 and later versions, the iSCSI initiator is built into the operating
system. For versions earlier than Windows Server 2008, download and install the iSCSI
initiator installation package that matches the OS version.

Figure 5-15 iSCSI initiator properties
Configuring IP Addresses on a Host

The network port configuration methods differ with the OS version.
To configure an IP address for a host running Windows Server 2003/2008, perform the
following operations:
Step 1 Choose Control Panel > Network and Internet > Network Connections. Right-click the
desired network port and choose Properties from the shortcut menu.

Step 2 Double-click Internet Protocol Version 4. In the dialog box that is displayed, configure an
IPv4 address. Figure 5-16 shows an example.
Figure 5-16 IPv4 address configuration
Select Use the following IP address and configure the following parameters:
l IP address
l Subnet mask
l Default gateway
----End
To configure an IP address for a host running Windows Server 2012/2016, perform the
following operations:
Step 1 Choose Control Panel > Network and Internet > Network and Sharing Center > Change
adapter settings. Right-click the desired network port and choose Properties from the
shortcut menu.
Step 2 Double-click Internet Protocol Version 4. In the displayed Internet Protocol Version 4
(TCP/IPv4) Properties window, configure an IPv4 address. Figure 5-17 shows an example.

Figure 5-17 IP address configuration
Select the Use the following IP address option and configure the following parameters:
l IP address
l Subnet mask
l Default gateway
----End
Configuring Initiators on a Host

To configure initiators on a host, perform the following steps:
Step 1 Ping IP addresses of the host and storage system respectively to verify the network
connectivity between them.
Step 2 Enter a name for the initiator.
On the iSCSI Initiator Properties page, click the Configuration tab and specify an initiator
name, as shown in Figure 5-18.

Figure 5-18 Specifying an initiator name
In this example, the initiator name is iqn.1991-05.com.microsoft:win-ijqskddbaar.

NOTE
An iSCSI initiator name must comply with the following format:

iqn.domaindate.reverse.domain.name:optional name
An iSCSI initiator name can contain only:
l Special characters: hyphens (-), periods (.), and colons (:)
l Lower-case letters
l Digits
Step 3 Discover the target.

On the Discovery tab page, click Discover Portal. In the dialog box that is displayed, enter
the IP address of the storage system, as shown in Figure 5-19.

Figure 5-19 Configuring the target IP address
NOTE
Retain the default iSCSI port 3260.
Step 4 Set up connections.

On the Target tab page, select the newly discovered target and click Connect. Verify that the
connection status of the target is connected.

According to the iSCSI protocol, a host can send NOP Out heartbeat packets to check link
connectivity between an initiator and a target. By default, this function is disabled for
Windows Server. To enable this function, locate the parameter HKLM\SYSTEM
\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-
BFC1-08002BE10318}\<Instance Number>\Parameters\EnableNOPOut in the registry,
change its value to 1, and restart the host for the modification to take effect.
----End
5.2.2 (Optional) Switch Configuration

This section describes how to configure Ethernet switches, including configuring VLANs and
binding ports. Skip this section if you use direct-attached connections.
Configuring VLANs
When many hosts are connected by an Ethernet network, a large number of broadcast packets
are generated during communication between the hosts. Broadcast packets sent from one host
will be received by all the other hosts on the network, consuming considerable bandwidth.
Moreover, all hosts on the network can access each other, leaving data vulnerable to security
risks.
Dividing hosts on an Ethernet network into multiple logical groups helps save bandwidth and
prevent security risks. Each logical group is a VLAN. The following uses Huawei Quidway
2700 Ethernet switch as an example to explain how to configure VLANs.
In the following example, two VLANs (VLAN 1000 and VLAN 2000) are created. VLAN
1000 contains ports GE 1/0/1 to 1/0/16. VLAN 2000 contains ports GE 1/0/20 to 1/0/24.
Step 1 Go to the system view.
<Quidway>system-view
System View: return to User View with Ctrl+Z.
Step 2 Create VLAN 1000 and add ports to it.

[Quidway]VLAN 1000
[Quidway-vlan1000]port GigabitEthernet 1/0/1 to GigabitEthernet 1/0/16
Step 3 Configure an IP address for VLAN 1000.

[Quidway-vlan1000]interface VLAN 1000
[Quidway-Vlan-interface1000]ip address 192.168.5.1 255.255.255.0
Step 4 Create VLAN 2000, add ports, and configure an IP address.

[Quidway]VLAN 2000
[Quidway-vlan2000]port GigabitEthernet 1/0/20 to GigabitEthernet 1/0/24
[Quidway-vlan2000]interface VLAN 2000
[Quidway-Vlan-interface2000]ip address 192.168.6.1 255.255.255.0
----End
Binding Ports
When storage systems and hosts are connected point-to-point, existing bandwidth may be
insufficient for storage data transmission. Moreover, redundancy in connection cannot be
achieved in point-to-point connection. To address these problems, ports are bound (link
aggregation) to improve bandwidth and balance loads among multiple links.

Three Ethernet link aggregation modes are available:

l Manual aggregation
Commands are run to add ports to an aggregation group. Ports added to the aggregation
group must have the same link type.
l Static aggregation
Commands are run to add ports to an aggregation group. Ports added to the aggregation
group must have the same link type and LACP must be enabled.
l Dynamic aggregation
The protocol dynamically adds ports to an aggregation group. Ports added in this way
must have LACP enabled and the same speed, duplex mode, and link type.
Table 5-2 compares these aggregation modes.
Table 5-2 Comparison among link aggregation modes

Link Aggregation Packet Exchange Port Detection CPU Usage
Mode
Manual aggregation No No Low
Static aggregation Yes Yes High
Dynamic Yes Yes High

aggregation
Huawei OceanStor storage devices support 802.3ad link aggregation (dynamic aggregation).
In this link aggregation mode, multiple network ports are in an active aggregation group and
work in duplex mode at the same speed. After binding iSCSI front-end ports on a storage
device, enable aggregation for their peer ports on the switch. Otherwise, links are unavailable
between the storage device and the switch.
This section uses switch ports GE 1/0/1 and GE 1/0/2 and the storage system's ports P2 and
P3 as an example to explain how to bind ports.
The port binding method differs with the OceanStor system version. For details, refer to the
specific storage product documentation.
Step 1 Log in to DeviceManager and choose Provisioning > Port > Ethernet Ports.
Step 2 Bind ports.
1. Select the ports that you want to bind and choose More > Bond Port.
The Bond Port dialog box is displayed.
2. Specify Bond Name, select the target ports, and click OK.
3. In the security alert dialog box that is displayed, select I have read and understand the
consequences associated with performing this operation and click OK.
4. In the Success dialog box that is displayed, click OK.
After the storage system ports are bound, configure link aggregation on the switch using the
following command:
<Quidway>system-view
System View: return to User View with Ctrl+Z.

[Quidway-Switch]interface GigabitEthernet 1/0/1

[Quidway-Switch-GigabitEthernet1/0/1]lacp enable
LACP is already enabled on the port!
[Quidway-Switch-GigabitEthernet1/0/1]quit
[Quidway-Switch]interface GigabitEthernet 1/0/2
[Quidway-Switch-GigabitEthernet1/0/2]lacp enable
LACP is already enabled on the port!
[Quidway-Switch-GigabitEthernet1/0/2]quit
After the command is executed, LACP is enabled for ports GE 1/0/1 and GE 1/0/2. Then the
ports can be automatically detected and added to an aggregation group.
----End
5.2.3 Storage System Configuration

Configuring Port IP Addresses
Configure Ethernet port parameters to ensure proper communication between the storage
system and application server.
Note the following items when setting the properties of an Ethernet port:
l The default internal heartbeat IP addresses of a dual-controller storage system are
127.127.127.10 and 127.127.127.11, and those of a four-controller storage system are
127.127.127.10, 127.127.127.11, 127.127.127.12, and 127.127.127.13. Therefore, the IP
address of the Ethernet port must not be in the 127.127.127.XXX segment and the
gateway address must not be 127.127.127.10, 127.127.127.11, 127.127.127.12, or
127.127.127.13. Otherwise, routing will fail. Internal heartbeat links are established
between controllers for these controllers to detect each other's working status. You do not
need to separately connect cables. In addition, internal heartbeat IP addresses have been
assigned before delivery, and you cannot change these IP addresses.
l The IP address of the Ethernet port cannot be in the same network segment as that of a
management network port.
l The IP address of the Ethernet port cannot be in the same network segment as that of a
maintenance network port.
l If the Ethernet port connects to an application server, the IP address of the Ethernet port
must be in the same network segment as that of the service network port on the
application server. If the Ethernet port connects to another storage device, the IP address
of the Ethernet port must be in the same network segment as that of the Ethernet port on
the other storage device. Add routes if available IP addresses in the desired segment are
insufficient.
To configure an IP address for an Ethernet port, perform the following steps:
Step 1 Go to the Ethernet Port dialog box.

1. On the DeviceManager home page, click System.
2. In the middle function pane, click the cabinet whose Ethernet port you want to view.
3. Click the controller enclosure where the desired Ethernet port resides. The controller
enclosure view is displayed.
4. Click to switch to the rear view.

5. Click the Ethernet port whose information you want to modify.
The Ethernet Port dialog box is displayed.

6. Click Modify.
Step 2 Modify the Ethernet port, as shown in Figure 5-20.

1. Specify IPv4 Address or IPv6 Address.
2. Specify Subnet Mask or Prefix
3. Specify MTU (Byte).
MTU is the maximum size of data packet that can be transferred between the Ethernet
port and the host. The value is an integer ranging from 1500 to 9216.
Figure 5-20 Configuring an IP address
Step 3 Confirm the Ethernet port modification.

1. Click Apply.
The Danger dialog box is displayed.
2. Confirm the information in the dialog box and select I have read and understand the
consequences associated with performing this operation.
3. Click OK.
The Success dialog box is displayed, indicating that the operation is successful.
4. Click OK.
----End
(Optional) Adding Routes

If iSCSI networking is used and data needs to be transmitted across network segments,
perform the following operations to configure routes:
Step 1 Log in to DeviceManager.

Step 2 Choose Provisioning > Port > Ethernet Ports.

Step 3 Select the Ethernet port for which you want to add a route and click Route Management.
The Route Management dialog box is displayed.
Step 4 Configure the route information for the Ethernet port.
1. Specify IP Address.
2. Click Add.
The Add Route dialog box is displayed.
3. Specify Type for the route to be added.
There are three route options:
– Default route
Data is forwarded through this route by default if no preferred route is available.
The destination address field and the destination mask field (IPv4) or prefix (IPv6)
of the default route are automatically set to 0. To use this option, you only need to
add a gateway.
– Host route
A route to an individual host. The destination mask (IPv4: 255.255.255.255) or
prefix (IPv6: 128) of the host route is automatically set. To use this option, add the
destination address and a gateway.
– Network segment route
A route to a network segment. You need to add the destination address, destination
address mask (IPv4) or prefix (IPv6), and gateway. For example, the destination
address is 172.17.0.0, destination address mask is 255.255.0.0, and gateway is
172.16.0.1.
4. Set Destination Address to the IPv4 or IPv6 (depending on which one you use) address
or network segment of the application server's service network port or that of the other
storage system's Ethernet port.
5. Set Destination Mask (IPv4) or Prefix (IPv6).
– If an IPv4 address is used, this parameter specifies the subnet mask of the IP
address for the service network port on the application server or the other storage
device.
– If an IPv6 address is used, this parameter specifies the prefix of the IPv6 address for
the application server's service network port or that of the other storage system's
Ethernet port.
6. In Gateway, enter the gateway of the local storage system's Ethernet port IP address.
Step 5 Click OK.
A security alert dialog box is displayed.
Step 6 Confirm the information in the dialog box and select I have read and understand the
consequences associated with performing this operation.
Step 7 Click OK.
The Success dialog box is displayed, indicating that the operation is successful.
NOTE
To remove a route, select it and click Remove.

Step 8 Click Close.
----End
Adding an Initiator to a Host

This section details how to add initiators to hosts on the storage system. For other storage
configurations, see the Basic Storage Service Configuration Guide corresponding to your
storage system.
Step 1 Log in to DeviceManager.
Step 2 Choose Provisioning > Host.
Step 3 Select the target host and click Add Initiator.
Figure 5-21 Selecting a host
Step 4 Select the initiator and click to add it to Selected Initiators.

Figure 5-22 Adding an initiator
Step 5 Click OK.
----End
The initiator properties depend on the operating system and multipathing software used by the
hosts. For details, see storage configurations in 6 Configuring Multipathing.
5.2.4 CHAP Authentication

CHAP authentication is configured to protect iSCSI links. After CHAP authentication is
configured, a host can connect a discovered target only after the correct user name and
password are provided.
The following describes how to configure CHAP authentication on a host and storage system
respectively.

Configuring CHAP Information on a Host

Go to the Target tab page, select the desired target, and click Connect. In the dialog box that
is displayed, click Advanced. In the dialog box that is displayed, select Enable CHAP log
on, and enter the user name and password configured on the storage system, as shown in
Figure 5-23.
Figure 5-23 Connecting to the target on a host through CHAP authentication
Windows iSCSI Initiator will automatically connect to favorite targets after down links are
recovered. However, when CHAP authentication is configured, iSCSI Initiator will not
automatically update CHAP authentication information about the favorite targets before
automatic target connection. As a result, the automatic target connection may fail. To ensure
correct connection to favorite targets, update favorite target information after configuring
CHAP authentication as follows:
Step 1 On the Favorite Target tab page of iSCSI Initiator, delete the previously configured target.
Step 2 Reconnect to the iSCSI target. Enter the user name and password of CHAP authentication and
select Add this connection to the list of Favorite Targets.
----End
Configuring CHAP Information on a Storage System

The method for configuring CHAP authentication varies with storage systems. The following
describes how to configure CHAP authentication on various storage systems.
OceanStor T V1 storage system
To configure CHAP authentication on OceanStor T V1, perform the following steps:
Step 1 Go to the CHAP configuration page.

In the ISM navigation tree, choose SAN Services > Mappings > Initiators. In the function
pane, select the initiator whose CHAP authentication you want to configure and choose
CHAP > CHAP Configuration in the navigation bar, as shown in Figure 5-24.
Figure 5-24 Initiator CHAP configuration
Step 2 In the CHAP Configuration dialog box that is displayed, click Create in the lower right
corner, as shown in Figure 5-25.
Figure 5-25 CHAP Configuration dialog box

In the Create CHAP dialog box that is displayed, enter the CHAP user name and password,
as shown in Figure 5-26.
Figure 5-26 Create CHAP dialog box
The CHAP user name contains 4 to 25 characters and the password contains 12 to 16
characters.
The limitations to CHAP user name and password vary with storage systems. For details, see
the help documentation of corresponding storage systems.
Step 3 Assign the CHAP user name and password to the initiator, as shown in Figure 5-27.
Figure 5-27 Assigning the CHAP account to the initiator

Step 4 Enable the CHAP account that is assigned to the host.
In the ISM navigation tree, choose SAN Services > Mappings > Initiators. In the function
pane, select the initiator whose CHAP account is to be enabled and choose CHAP > Status
Settings in the navigation bar, as shown in Figure 5-28.
Figure 5-28 Setting CHAP status
Step 5 In the Status Settings dialog box that is displayed, choose Enabled from the CHAP Status
drop-down list, as shown in Figure 5-29.
Figure 5-29 Enabling CHAP
On the ISM, view the initiator status, as shown in Figure 5-30.
Figure 5-30 Initiator status after CHAP is enabled

----End
OceanStor 18000/T V2/V3 (V300R001) storage system
The iSCSI initiators' CHAP authentication methods are similar for OceanStor 18000/T V2/V3
systems. The following uses OceanStor V3 (V300R001) as an example to describe how to
configure CHAP authentication.
Step 1 On DeviceManager, click the icon on the right navigation tree. Then, click Host in the
displayed page.
Figure 5-31 Storage configuration page
Step 2 Select the host for which CHAP authentication needs to be enabled. In the initiator list, select
the target initiator and click Modify.
Figure 5-32 Host configuration page
Step 3 In the displayed Modify Initiator dialog box, select Enable CHAP authentication, enter the
CHAP name and password, and then click OK.

Figure 5-33 Initiator configuration page
CHAP authentication is configured on the storage system.
----End
OceanStor V3 (V300R002 and later)/Dorado V3/OceanStor V5 storage system
The iSCSI CHAP authentication methods are similar for OceanStor V3 (V300R002 and
later), OceanStor V5, and Dorado V3. The following uses OceanStor V3 as an example to
describe how to configure CHAP authentication.
Step 1 On DeviceManager, choose Provisioning > Host.
Figure 5-34 Storage configuration page
Step 2 Select the host for which CHAP authentication needs to be enabled. In the initiator list, select
the target initiator and click Properties.

Figure 5-35 Host configuration page
Step 3 In the displayed Initiator Properties dialog box, select Enable CHAP authentication, enter
the CHAP name and password, and then click OK.
Figure 5-36 Initiator configuration page

CHAP authentication is configured on the storage system.
----End
5.3 Scanning LUNs on a Host

After establishing connections, scan for LUNs on a host. For details, see 9 Appendix A
Volume Management.

Windows 6 Configuring Multipathing
6 Configuring Multipathing
6.1 Concepts
6.2 Configuring Multipathing in Non-HyperMetro Scenarios
6.3 Configuring Multipathing in HyperMetro Scenarios
6.1 Concepts
6.1.1 Initiator
Table 6-1 describes the key parameters of initiators.
Table 6-1 Key parameters of initiators

Parameter Description Example
Uses third- l This parameter is displayed only after an initiator Enabled

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

Switchover Path switchover mode

Mode The system supports the following modes:
l 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.
l common ALUA: Detailed requirements are as
follows:
– The storage system version must be
V500R007C00 and later, V300R003C20 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.
l 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.
l 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:
system must be VMware, AIX, Red Hat 7.X,
Windows Server 2012 (using QLogic HBAs), or
Windows Server 2008 (using QLogic HBAs).

Special mode Determines which Special mode is used for path Mode 0
type switchover. All special modes support ALUA. Detailed
requirements are as follows:
l Mode 0:
– The host and storage system must be connected
using a Fibre Channel network.
system must be Red Hat 7.X, Windows Server
2012 (using QLogic HBAs), or Windows Server
2008 (using QLogic HBAs).
l Mode 1:
system must be AIX or VMware.
– If HyperMetro is deployed, HyperMetro must
work in load balancing mode.
l Mode 2:
system must be AIX or VMware.
– If HyperMetro is deployed, HyperMetro must
work in local preferred mode.
l Mode 3:
V500R007C00 and later,
V300R006C10SPC100 and later, or Dorado
V300R001C01SPC100 and later.
system must be Linux or Solaris.
– HyperMetro must work in local preferred mode.

Path Type In HyperMetro scenarios, the value can be either Optimal Path
Optimal Path or Non-Optimal Path.
l 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.
l 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.
In non-HyperMetro scenarios, the value is Optimal
Path.
NOTE
l 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.
l After configuring an initiator's switchover mode, you must restart the host for the configuration to
take effect.
6.1.2 HyperMetro Working Modes

Typically, HyperMetro works in load balancing or local preferred mode. These modes are
valid only when the storage system and host both use ALUA. You are advised to set the host's
path selection policy to round-robin (this is mandatory if HyperMetro works in load balancing
mode).
HyperMetro storage arrays can be classified into a local and a remote array by their distance
to the host. The one closer to the host is the local array and the other is the remote array.
Table 6-2 describes the configuration methods and application scenarios of the typical
working modes.

Table 6-2 HyperMetro working modes

Working Configuration Method Application Scenario
Mode
Load balancing 1. Enable ALUA on the host and set the path The distance between
mode selection policy to round-robin. both HyperMetro
2. Configure an ALUA-supporting storage arrays is less
switchover mode for the initiators on both than 1 km, such as when
HyperMetro storage arrays. If multiple they are in the same
initiators are assigned to a host, this equipment room or on
should be done for each of the initiators. the same floor.
3. Set the path type of the initiators on both
storage arrays to optimal.
Local preferred 1. Enable ALUA on the host. It is advised to The distance between
mode set the path selection policy to round- both HyperMetro
robin. storage arrays is greater
2. Configure an ALUA-supporting than 1 km, such as when
switchover mode for the initiators on both they are in different
HyperMetro storage arrays. If multiple locations or data centers.
initiators are assigned to a host, this
should be done for each of the initiators.
3. Set the path type of the initiators on the
local array to optimal and those on the
remote array to non-optimal.
6.1.3 ALUA Working Principles

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.
l An AO path is the optimal I/O access path between the host and the owning controller of
a LUN.
l An AN path is the suboptimal I/O access path between the host and a non-owning
controller.
6.1.3.1 ALUA Working Principles and Failover in Non-HyperMetro Scenarios

If an AO path fails, the host will deliver I/Os to another AO path.
If all AO paths on the owning controller fail, the host will deliver I/Os to the AN paths on the
non-owning controller, as shown in "Path failure" in Figure 6-1.
If a LUN's owning controller fails, the system will activate the other controller as the new
owning controller, as shown in "SP failure" in Figure 6-1.

Figure 6-1 Failover in non-HyperMetro scenarios
Host Host
AO AN AO AO’
A B A B
Path failure SP failure
6.1.3.2 ALUA Working Principles and Failover in HyperMetro Scenarios

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 6-2 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 6-3 Local preferred mode

6.2 Configuring Multipathing in Non-HyperMetro

Scenarios
6.2.1 UltraPath
6.2.1.1 Storage System Configuration

If you use UltraPath, retain the default initiator settings. Do not select Uses third-party
multipath software.
Figure 6-4 Initiator setting when UltraPath is used
6.2.1.2 Host Configuration

Install UltraPath by following instructions in the OceanStor UltraPath for Windows User
Guide.

NOTE
You can log in to Huawei's technical support website (http://support.huawei.com/enterprise/) and

enter UltraPath in the search box. Then, select a path from the paths that are automatically displayed to
go to the document page. Search for, browse, and download desired documents. To download UltraPath
software, click the Software Download tab, and search for and download UltraPath software specific to
your product version.
After you install UltraPath, set the trespass policy for LUNs as follows:
NOTE
This configuration must be performed on all hosts separately. Retain the default settings for other
parameters.
l For UltraPath earlier than 21.2.0, it is recommended that you run the set luntrespass
command to disable the trespass function.
UltraPath CLI #3 >set luntrespass=off array_id=0
The current configuration will overwrite the configuration of all VLUNs in

this array.
Are you sure you want to continue? [y,n]: y
Succeeded in executing the command.

The command format is set luntrespass={ on | off } [ array_id=ID | vlun_id={ ID |
ID1,ID2... | ID1-ID2 } ]. Table 6-3 describes the key parameters in the command.
Table 6-3 Parameter description

Parameter Description Default
Value
{ on | off } Trespass policy of LUNs on

l on: Switchover of LUNs' working
controller is enabled.
l off: Switchover of LUNs' working
controller is disabled.
array_id=ID ID of the storage array None

You can run the show array command to
query the ID of the storage array.
vlun_id={ ID | ID of the virtual LUN None

ID1,ID2... | ID1- You can run the show vlun type=all
ID2 } command to query the IDs of all virtual
LUNs.
l For UltraPath 21.2.0 and later, it is recommended that you retain the default settings (the
trespass function is disabled by default).
If a path switchover takes a long period of time, you can modify the timeout time for a driver
by following instructions in 7.4 How Do I Modify the Timeout Time for the FC HBA Port
Driver? or 7.5 How Do I Modify the iSCSI Initiator's Driver Timeout Time?, thereby
shortening I/O interruption.

6.2.2 OS Native Multipathing Software

Huawei storage firmware is classified into:
l Old storage version
T V1, T V2, 18000 V1, V300R001, V300R002, V300R003C00, V300R003C10,
V300R005, and Dorado V300R001C00
l New storage version
V500R007C00 and later, V300R003C20SPC200 and later, V300R006C00SPC100 and
later, and Dorado V300R001C01SPC100 and later
NOTE
For details about the old and new storage versions, see 2.2.3.3 ALUA.

If you use OS native multipathing software, you must select Uses third-party multipath
software for the initiator, as shown in Figure 6-5.
Figure 6-5 Using OS native multipathing software
The Switchover Mode and Path Type depend on the actual services. Different models of
Huawei storage systems support different ALUA policies. For details, refer to the specific
Huawei storage model's product documentation.

For details about the Windows versions, see the Huawei Storage Interoperability
Navigator.
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.
Unless otherwise specified, the recommended configurations for Huawei storage that supports
ALUA are detailed as follows:
ALUA Configuration on Old-Version Storage
Table 6-4 ALUA configuration on old-version storage
Server OS ALUA Enabled or Disabled on Storage Remarks
OceanStor T V1 OceanStor T V2
Windows Server Enabled Enabled -

2003

2003 R2
Windows Server Enabled Enabled Optimal path

2008 selection fails on
Windows Server
Windows Server Enabled Enabled 2008 and Windows
2008 R2 Server 2008 SP2
even after ALUA is
enabled. You must
set optimal paths
manually.

2012
NOTE
You are advised to enable ALUA on OceanStor T V1 because mirror link interruption may interrupt
services if ALUA is disabled.
ALUA Configuration on New-Version Storage
Table 6-5 ALUA configuration on new-version storage
Server OS ALUA Enabled or Disabled on Storage Remarks

Versions Earlier Than OceanStor

OceanStor V300R003C20SPC200
V300R003C20 and Later,
V300R006C00SPC100
and Later,
V500R007C00 and
Later, or Dorado
V300R001C01SPC100
and Later
Windows Server Disabled Disabled -

2003

2003 R2

2008
Windows Server Disabled Enabled (common -

2008 R2 ALUA)

2012 ALUA)

2012 R2 ALUA)

2016 ALUA)
Windows Server Disabled Enabled (common

2019 ALUA)

As a built-in service in Windows, MPIO is disabled by default. You need to manually enable
it. Moreover, ALUA must be configured on storage systems as required.
This section uses Windows Server 2012 R2 as an example to describe how to install and
configure MPIO. The MPIO installation and configuration procedures are the same as these
for Windows Server 2012 R2 and therefore will not be detailed. For more details, see the
Microsoft official documentations.
Step 1 Add Multipath I/O.

Start Server Manager, choose Manage > Add Roles and Features, and select Multipath
I/O, as shown in Figure 6-6.

Figure 6-6 Adding Multipath I/O
Step 2 Query the device's VID and PID.

VID indicates the vendor ID, for example, HUAWEI.
PID indicates the product ID, for example, S5500T, S5600T, or XSG1.
If MPIO is installed on Windows Server 2008 or later versions, you can use multipathing
command mpclaim to query disk information, as shown in Figure 6-7.
Figure 6-7 Querying disk information
In the preceding figure, the VID is HUAWEI and the PID is XSG1.
NOTE
The PID and VID in this section are examples only.
Step 3 Configure MPIO to take over the storage system.

You can add the target storage system on the MPIO console or run a command in Command
Prompt to take over the storage. In this example, a command is run in Command Prompt.
On the Windows server, open Command Prompt and run the mpclaim -r -i -d "HUAWEI
XSG1 " command, as shown in Figure 6-8.
Figure 6-8 Taking over Huawei storage

NOTE
The VID must contain eight characters and the PID must contain 12 characters. If the characters are
insufficient, add spaces. You can copy the VID and PID from the output of the mpclaim -e command.
After the mpclaim -r -i -d "HUAWEI XSG1 " command is executed, the host restarts
automatically.
Step 4 View MPIO policies.

Rescan for disks after restarting the host. Ensure that the number of discovered disks is
consistent with that of LUNs mapped to the host. Right-click a disk and choose Properties
from the shortcut menu. You can view the policies on the MPIO tab page, as shown in Figure
6-9.
Figure 6-9 MPIO policy management page
Normally, the default MPIO policy is preferred.

The default policy varies with operating system configurations. Table 6-6 lists the default
policies for commonly used operating systems.

Table 6-6 Default MPIO policy
Operating System Storage System Default MPIO Policy Remarks
Windows Server ALUA enabled Round Robin with Subset -

2008
ALUA disabled Failover only -

2008 R2
ALUA disabled Round Robin -

2012

2012 R2

2016
Windows Server ALUA enabled Round Robin With Subset -

2019
For Windows in non-HyperMetro networking, it is advisable to use the default MPIO policy.
Driver?, 7.5 How Do I Modify the iSCSI Initiator's Driver Timeout Time?, and 7.6 How
Do I Change the Number of TCP Data Retransmission Times? to shorten I/O interruption.
----End
6.2.2.3 Verification
Run the mpclaim -s -d command to verify that the configuration has taken effect.
Figure 6-10 Verifying the MPIO disk information

Run the mpclaim -s -d MPIO Disk No. command to verify path information about an MPIO
disk.
Figure 6-11 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.
6.3 Configuring Multipathing in HyperMetro Scenarios

This section describes the multipathing configurations on the hosts and storage systems. For
details about how to configure HyperMetro services, see the BC&DR Solution Product
Documentation (Active-Active Data Center).
6.3.1 UltraPath
This section describes the operations on storage systems and hosts when UltraPath is used.

If you use UltraPath, retain the default initiator settings. Do not select Uses third-party
multipath software.

Figure 6-12 Initiator setting when UltraPath is used

Install UltraPath by following instructions in the OceanStor UltraPath for Windows User
Guide.
After you install UltraPath, set the trespass policy for LUNs as follows:
l For UltraPath earlier than 21.2.0, it is recommended that you run the set luntrespass
command to disable the trespass policy.
UltraPath CLI #3 >set luntrespass=off array_id=0
The current configuration will overwrite the configuration of all VLUNs in

this array.
Are you sure you want to continue? [y,n]: y
Succeeded in executing the command.
The command format is set luntrespass={ on | off } [ array_id=ID | vlun_id={ ID |

ID1,ID2... | ID1-ID2 } ]. Table 6-7 describes the key parameters in the command.


Parameter Description Default
Value
{ on | off } Trespass policy of LUNs on

l on: Switchover of LUNs' working
controller is enabled.
l off: Switchover of LUNs' working
controller is disabled.
array_id=ID ID of the storage array None

You can run the show array command to
query the ID of the storage array.
vlun_id={ ID | ID of the virtual LUN None

ID1,ID2... | ID1-ID2 } You can run the show vlun type=all
command to query the IDs of all virtual
LUNs.
l For UltraPath 21.2.0 and later, it is recommended that you retain the default settings (the
trespass policy is disabled by default).
After configuring the trespass policy, set the HyperMetro working mode to local preferred on
UltraPath. In this mode, the local storage array is preferred in processing host services. The
remote storage array is used only when the local array is faulty. This improves the service
response speed and reduces the access latency.
Table 6-8 lists the command for setting the HyperMetro working mode.
Table 6-8 Setting the HyperMetro working mode

Operating System Command Example
Windows set hypermetroworking- upadm set hypermetro

mode={priority| workingmode=priority
balance}primary_array_id primary_array_id=0
=ID
Table 6-9 describes the parameters.


Parameter Description Default Value
workingmode={ pr HyperMetro working mode. priority

iority | balance } l priority: local preferred mode priority is recommended.
l balance: load balancing mode balance is applicable when
two active-active data
NOTE
If you set the HyperMetro working
centers are in the same
mode for a specific virtual LUN first building.
and then the global HyperMetro
working mode for the storage system,
the working mode for the virtual LUN
remains unchanged.
primary_array_id ID of the preferred storage array. None

=ID The ID is allocated by UltraPath. NOTE
The storage array that is in the same Mapping relationship between
application hosts and storage
data center as the application hosts
arrays:
is preferred.
l Storage array A is the
Run the command to obtain the preferred array for all
storage array ID: application hosts in data
center A.
l Linux: upadmin show array
l Storage array B is the
l Windows/AIX/Solaris: upadm preferred array for all
show array application hosts in data
NOTE center B.
l In priority mode, this parameter
indicates the storage array to which
I/Os are preferentially delivered.
l In balance mode, this parameter
indicates the storage array where the
first slice section resides.
Driver? or 7.5 How Do I Modify the iSCSI Initiator's Driver Timeout Time?, thereby
shortening I/O interruption.
Run the upadm show upconfig command. If the command output contains the following
information, the configuration is successful.
HyperMetro WorkingMode : read write within primary array
Figure 6-13 provides an example.

Figure 6-13 Verifying the HyperMetro working mode
6.3.2 OS Native Multipathing Software

If you use OS native multipathing software, you must select Uses third-party multipath
software for the initiator, as shown in Figure 6-14.

Figure 6-14 Using OS native multipathing software
The Switchover Mode and Path Type depend on the actual services. For details, see
HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native
Multipathing Software.
For details about the Windows versions, see the Huawei Storage Interoperability
Navigator.
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.

As a built-in service in Windows, MPIO is disabled by default. You need to manually enable
it. Moreover, ALUA must be configured on storage systems as required.
This section uses Windows Server 2012 R2 as an example to describe how to install and
configure MPIO. The MPIO installation and configuration procedures for other Windows
systems are the same and therefore will not be detailed. For more details, see the Microsoft
official documentations.

Step 1 Add Multipath I/O.

Start Server Manager, choose Manage > Add Roles and Features, and select Multipath
I/O, as shown in Figure 6-15.
Figure 6-15 Adding Multipath I/O
Step 2 Query the device's VID and PID.

VID indicates the vendor ID, for example, HUAWEI.
PID indicates the product ID, for example, S5500T, S5600T, or XSG1.
If MPIO is installed on Windows Server 2008 or later versions, you can use multipathing
command mpclaim to query disk information, as shown in Figure 6-16.
Figure 6-16 Querying disk information
In the preceding figure, the VID is HUAWEI and the PID is XSG1.
NOTE
The PID and VID in this section are examples only.
Step 3 Configure MPIO to take over the storage system.

You can add the target storage system on the MPIO console or run a command in Command
Prompt to take over the storage. In this example, a command is run in Command Prompt.

On the Windows server, open Command Prompt and run the mpclaim -r -i -d "HUAWEI
XSG1 " command, as shown in Figure 6-17.
Figure 6-17 Taking over Huawei storage
NOTE
The VID must contain eight characters and the PID must contain 12 characters. If the characters are
insufficient, add spaces. You can copy the VID and PID from the output of the mpclaim -e command.
After the mpclaim -r -i -d "HUAWEI XSG1 " command is executed, the host restarts
automatically.
Step 4 View MPIO policies.

Rescan for disks after restarting the host. Ensure that the number of discovered disks is
consistent with that of LUNs mapped to the host. Right-click a disk and choose Properties
from the shortcut menu. You can view the policies on the MPIO tab page, as shown in Figure
6-18.

Figure 6-18 MPIO policy management page
Normally, the default MPIO policy is preferred.
The default policy varies with operating system configurations. Table 6-10 lists the default
policies for commonly used operating systems.
Table 6-10 Default MPIO policy
Operating System Storage System Default MPIO Remarks

Policy
Windows Server ALUA enabled Round Robin with -

2008 Subset
ALUA disabled Failover only -

2008 R2 Subset

2012 Subset

Operating System Storage System Default MPIO Remarks

Policy

2012 R2 Subset

2016 Subset

2019 Subset
For Windows in non-HyperMetro networking, it is advisable to use the default MPIO policy.
Step 5 Enable path verification.
On the MPIO tab, click Details. In the dialog box that is displayed, select Path Verify
Enabled and click OK. Then restart the host for the configuration to take effect.

Figure 6-19 Enabling path verification
Driver?, 7.5 How Do I Modify the iSCSI Initiator's Driver Timeout Time?, and 7.6 How
Do I Change the Number of TCP Data Retransmission Times? to shorten I/O interruption.
----End
Run the mpclaim -s -d command to verify that the configuration has taken effect.

Figure 6-20 Verifying the MPIO disk information
Run the mpclaim -s -d MPIO Disk No. command to verify path information about an MPIO
disk.
Figure 6-21 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.

Windows 7 FAQs
7 FAQs
7.1 What Can I Do When Being Prompted to Uninstall MPIO During UltraPath Installation?
7.2 What Are Common Management Commands?
7.3 How Do I Change the Windows Disk Timeout Time?
7.4 How Do I Modify the Timeout Time for the FC HBA Port Driver?
7.5 How Do I Modify the iSCSI Initiator's Driver Timeout Time?
7.6 How Do I Change the Number of TCP Data Retransmission Times?
7.1 What Can I Do When Being Prompted to Uninstall

MPIO During UltraPath Installation?
If being prompted to uninstall MPIO when installing UltraPath, you do not need to uninstall
MPIO. You only need to remove Huawei devices managed by MPIO as follows:
On the MPIO Device tab page, select devices whose names contain "HUAWEI", "HS",
"SYMANTEC", and "MSFT2005iSCSIBusType_0x9", and click Remove. After all related
devices are deleted, reboot the host and re-install UltraPath.

Windows 7 FAQs
Figure 7-1 Deleting iSCSI devices managed by MPIO
7.2 What Are Common Management Commands?

Table 7-1 lists CMD commands for MPIO management.
Table 7-1 CMD commands for MPIO management
Function Syntax
Views the currently installed features. dism /online /get-features
Activates MPIO. dism /online /enable-feature:MultipathIo
Deactivates MPIO. dism /online /disable-feature:MultipathIo
Views the discovered storage devices. mpclaim -e
Uses MPIO to manage Fibre Channel mpclaim.exe -r -i -d <_VendorID>

devices. <_ProductID>

Windows 7 FAQs
Function Syntax
Disables MPIO from managing Fibre mpclaim.exe -r -u -d <_VendorID>

Channel devices. <_ProductID>
Uses MPIO to manage iSCSI devices. mpclaim -r -i -d

"MSFT2005iSCSIBusType_0x9"
Disables MPIO from managing iSCSI mpclaim.exe -r -u -d

devices. "MSFT2005iSCSIBusType_0x9"
Uses MPIO to manage all storage devices. mpclaim.exe -r -i -a ""
Disables MPIO from managing all storage mpclaim.exe -r -u -a ""

devices.
Views storage devices managed by mpclaim -r

Microsoft DSM.
Modifies the load balancing policy. mpclaim.exe –L –M <_num>
NOTE
l VendorID must be eight bytes long and ProductID 16 bytes long. If VendorID or ProductID
contains fewer bytes, use spaces as placeholders.
For details about the meaning of parameter num in the command for modifying the load
balancing policy, see Table 7-2.
Table 7-2 Meaning of parameter num in the command for modifying the load balancing
policy
Parameter Definition
0 Clear the Policy
1 Failover Only
2 Round Robin
3 Round Robin with Subset
4 Least Queue Depth
5 Weighted Paths
6 Least Blocks
7 Vendor Specific
7.3 How Do I Change the Windows Disk Timeout Time?

If a host's request for disk data has no response during disk timeout time, the operating system
of the host considers no response as normal. However, if the host still receives no response

Windows 7 FAQs
after the disk timeout time expires, the host operating system reports an error or abandons this
data request.
By default, the disk timeout time in Windows is 60s. The disk timeout time can be changed in
some special conditions, for example, installing drivers. In this case, you need to change the
disk timeout time back to 60s after drivers are installed.
The following explains how to change the disk timeout in the registry.
Step 1 Run the CMD command regedit to start Registry Editor.
Step 2 Choose HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > Disks.
Step 3 In the function pane, check whether TimeOutValue exists.

l If no, right-click the function pane and choose New > DWORD Value. Set the name to
TimeOutValue and go to step 4.
l If yes, double-click TimeOutValue and go to step 4.
Step 4 In Value data, enter a desired value. You can specify the value format. Available formats are
Hexadecimal and Decimal, as shown in Figure 7-2.
Figure 7-2 Configuring disk timeout in the registry
Step 5 Restart the host for the change to take effect.
----End
7.4 How Do I Modify the Timeout Time for the FC HBA

Port Driver?
When a Windows host connects to a storage array through FC HBAs, the FC HBA port
driver's timer parameter directly affects the time of a multipath switchover upon a fault. For
common FC HBAs from Emulex and QLogic, it is advisable to set Port Down Retry Count
and Link Down Timeout to 10.
Before modifying FC HBA port parameters, you need to download the HBA management
tool from the HBA vendor. The following describes how to modify Emulex and QLogic FC
HBAs' port parameters.
7.4.1 Modifying Emulex HBA Driver Parameters

Step 1 From the Emulex official website, download the One Command Manager and install it to the
Windows host:

Windows 7 FAQs
https://www.broadcom.com/products/storage/fibre-channel-host-bus-adapters/
onecommand-manager-centralized#downloads
Step 2 Open the Emulex HBA management tool. This tool will automatically detect the Emulex
HBA port that the local host uses. Select the HBA port, click Driver Parameters tab, select
the parameter you want to modify, type the value, and click Apply, as shown in Figure 7-3.
Figure 7-3 Modifying the values of the timeout parameters
----End
7.4.2 Modifying QLogic HBA Driver Parameters

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 tool.
After downloading and installing the tool, open the tool (2.1.0 build 11) and run the qaucli
command to navigate to the management CLI.

Windows 7 FAQs
Figure 7-4 Management console CLI
Step 3 Set HBA parameters.
Select 2: Adapter Configuration. The following window is displayed.
Figure 7-5 HBA parameters
Select 3: HBA Parameters. The HBA port status window is displayed.
Figure 7-6 HBA port status
Select a port and go to the HBA Parameters Menu.

Windows 7 FAQs
Figure 7-7 HBA parameters menu
Select 2: Configure HBA Parameters. The Configure Parameters Menu window is

displayed.
Figure 7-8 Configure Parameters Menu
Select 13 and 15. Set the values of the parameters to 10. Then select 20: Commit Changes.
After the configuration, check the HBA parameters.

Windows 7 FAQs
Figure 7-9 HBA parameter configuration
Step 4 Complete the configurations of all ports.
Step 5 Repeat the preceding steps to configure other ports.
----End
7.5 How Do I Modify the iSCSI Initiator's Driver Timeout

Time?
During the iSCSI initiator driver timeout time, a host can still send device files to upper-layer
applications when links to the host are down.
If multipathing software is installed, the iSCSI initiator driver timeout time needs to be
changed so that the multipathing software can receive link errors in a timely manner and then
initiates a path switchover.
To change the iSCSI initiator driver timeout time in the registry, perform the following steps:
Step 1 Run the CMD command regedit to start Registry Editor.
Step 2 Query the registry key.

Choose HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > Class >
{4D36E97B-E325-11CE-BFC1-08002BE10318} > Instance Number > Parameters, as
shown in Figure 7-10.

Windows 7 FAQs
Figure 7-10 Changing the iSCSI initiator driver timeout
Step 3 Modify the registry key.

By default, LinkDownTime and MaxRequestHoldTime are 15s and 60s respectively. On a
multi-path network, the path failover time decreases with the values of the two parameters. If
MPIO is enabled, it is recommended that you set LinkDownTime to 5s; if MPIO is not
enabled, it is recommended that you set MaxRequestHoldTime to 5s.
If UltraPath is installed, run CMD command iscsiconfig get timeout value to query the iSCSI
initiator driver timeout and then run iscsiconfig set timeout xxx to specify the timeout value.
Step 4 Restart the host for the change to take effect.
----End
7.6 How Do I Change the Number of TCP Data

Retransmission Times?
TcpMaxDataRetransmissions indicates the number of TCP data retransmission times. If the
network environment is poor, increase the value of this parameter for effective
communication. If the network environment is good, decrease the value of this parameter to
shorten the verification time. If multipathing software is available, it is advised to set this
parameter to 3 so that multipathing software can receive link fault information in a timely
manner and start path switchover.
To modify this parameter, perform the following steps:
Step 1 In Command Prompt, run the regedit command to go to the registry editing page.
Step 2 Choose HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > Tcpip
> Parameters.

Windows 7 FAQs
Step 3 Check whether TcpMaxDataRetransmissions exists.

l If yes, it is advised to change its value to 3.
Figure 7-11 Modifying TcpMaxDataRetransmissions
l If no, right-click in the blank area and choose New > DWORD (32 bits) to create
TcpMaxDataRetransmissions with its value being 3.
Figure 7-12 Adding TcpMaxDataRetransmissions
----End

Windows 8 Acronyms and Abbreviations
8 Acronyms and Abbreviations
C
CHAP Challenge Handshake Authentication Protocol
CLI Command Line Interface
CDFS CD-ROM File System
D
DM-Multipath Device Mapper-Multipath
E
Ext2 The Second Extended File System
Ext3 The Third Extended File System
Ext4 The Fourth Extended File System
F
FC Fiber Channel
G
GE Gigabit Ethernet
H
HBA Host Bus Adapter
I
IP Internet Protocol
ISM Integrated Storage Manager
iSCSI Internet Small Computer Systems Interface

Windows 8 Acronyms and Abbreviations
L
LACP Link Aggregation Control Protocol
LE Logical Extent
LUN Logical Unit Number
LV Logical Volume
LVM Logical Volume Manager
M
MB Megabyte
N
NFS Network File System
R
RAID Redundant Array of Independent Disks
S
SAN Storage Area Network
P
PE Physical Extent
PV Physical Volume
V
VLAN Virtual Local Area Network
VG Volume Group
W
WWN World Wide Name

Windows 9 Appendix A Volume Management
9 Appendix A Volume Management
In Windows, disks are categorized as basic and dynamic disks. Only simple volumes can be
created on basic disks. Spanned volumes, mirror volumes, striped volumes, and RAID-5
volumes are created on dynamic disks.
RAID-5 volumes are not supported in desktop operating systems such as Windows XP,
Windows 7, and Windows 8.
In Windows Server 2008 and later versions, the operating system converts basic disks to
dynamic disks when spanned volumes (or other volumes that can only be created on dynamic
disks) are created on basic disks.
The definitions of the volumes are as follows:
l Spanned volume
A spanned volume is created on a single or multiple disks and combines the disks as a
whole. A spanned volume is used to expand volume capacity.
l Mirror volume
A mirror volume is created on two or multiple disks. Member disks in a mirror volume
are mirrors to each other. Mirror volumes improve data reliability.
l Striped volume
A striped volume is created on two or multiple disks. Member disks in a striped volume
are of the same size and stripped. When data is written onto a striped volume, the data is
divided into several parts and the parts are written onto each member disk. Theoretically,
striped volumes help improve write performance and expand volume capacity.
l RAID-5 volume
After incorporating a parity disk, a striped volume becomes a RAID-5 volume.
Therefore, a RAID-5 volume has all advantages of a striped volume and also ensures
data reliability.
Windows volume management is simple. You can manage Windows volumes on a graphical
user interface (GUI).
The following uses Windows 2012 as an example to explain how to create a RAID-5 volume:

Step 1 After LUNs are mapped to the host, start Computer Management. Right-click Disk
Management and choose Rescan Disks from the shortcut menu, as shown in Figure 9-1.
Figure 9-1 Rescanning for disks
The states of the identified LUNs are Unknown and Offline.

Step 2 Right-click a disk and choose Online from the shortcut menu to set the disk online. The state
of the disk is changed to Unknown or Not Initialized, as shown in Figure 9-2.

Figure 9-2 Setting the identified disks online
Step 3 Right-click a disk and choose Initialize Disks from the shortcut menu. In the Initialize Disks
dialog box that is displayed, select the disks that you want to initialize and the partition
format. In this example, partition format MBR is selected. Then, the states of the selected
disks change to Online, as shown in Figure 9-3.

Figure 9-3 Initializing disks
Step 4 Right-click a disk and choose New RAID-5 Volume from the shortcut menu. The New
RAID-5 Volume dialog box is displayed, as shown in Figure 9-4.
Figure 9-4 New RAID-5 volume dialog box
Step 5 Select the disks that you want to add to the RAID-5 volume, specify capacities of the selected
disks, and click Next. Select a drive letter for the newly created RAID-5 volume, the file
system type for volume formatting, strip size, and fast formatting.

NOTE
A RAID-5 volume has at least three member disks. After a RAID-5 volume is created, it spends a
certain period of time in synchronous verification. The verification time grows with the volume capacity.
Fast formatting is recommended.
A disk must be formatted after being installed. The operating system creates partitions on a disk only
after writing the disk identifier, end-of-sector marker (also called a signature), and MBR or GUID.
----End

Windows 10 Appendix B Host High-Availability
10 Appendix B Host High-Availability
10.1 WSFC
10.2 Veritas VCS
10.1 WSFC
10.1.1 Overview
Earlier Windows versions (such as Windows Server 2003) use Microsoft Cluster Service
(MSCS) to provide clustering functions. Windows Server 2008 and later versions use
Windows Server Failover Cluster (WSFC).
An MSCS cluster is a server group consisting of independent computers. Nodes in the cluster
work together as a single system to ensure that key applications and resources are always
available to clients. The clustering function enables users and administrators to manage nodes
as a whole instead of independent computers.
WSFC server clustering software adds new functions on the basis of MSCS. The new
functions include the validation wizard and GPT disks.
MSCS
An MSCS server cluster contains a maximum of eight nodes, and can be configured as either
of the following clusters:
l Single-node cluster
l Single-quorum device cluster
l Multi-node cluster
Each cluster node is connected to one or multiple cluster storage devices. In most Windows
Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition versions, cluster
storage devices can be iSCSI, SAS, parallel SCSI, and Fibre Channel devices.
Table 10-1 lists the maximum number of nodes supported by different operating systems.

Table 10-1 Maximum number of nodes supported by different storage systems

Operating System Storage Type Max. Number of Nodes
Windows Server 2003 Parallel SCSI 2

Enterprise Edition or
Windows Server 2003
Datacenter Edition
Version:
Windows Server 2003
Windows Server 2003 SP1
Windows Server 2003 R2
Platform:
x86 and x64 (non Itanium)
Windows Server 2003 Fiber Channel 8

Windows Server 2003
Datacenter Edition
Version:
Windows Server 2003
Platform:
x86 and x64 (Itanium)
Windows Server 2003 iSCSI or SAS 8

Windows Server 2003
Datacenter Edition
Version:
Platform:
x86 and x64 (Itanium)
WSFC
A WSFC cluster is a group of independent servers that work together to improve the
availability of applications and services. WSFC provides infrastructure features that support
high-availability and disaster recovery scenarios for hosted server applications. If a cluster
node or service fails, the services that were hosted on that node can be automatically or
manually transferred to another available node in a process known as failover.
The nodes in a WSFC cluster work together to collectively provide the following types of
capabilities:

l Distributed metadata and notifications

WSFC service and hosted application metadata is maintained on each node in the cluster.
This metadata includes WSFC configuration and status in addition to hosted application
settings. Changes to a node's metadata or status are automatically propagated to the other
nodes in the cluster.
l Resource management
Individual nodes in the cluster may provide physical resources such as direct-attached
storage, network interfaces, and access to shared disk storage. Hosted applications
register themselves as cluster resources, and may configure startup and health
dependencies upon other resources.
l Health monitoring
Inter-node and primary node health detection is accomplished through a combination of
heartbeat-style network communication and resource monitoring. The overall health of
the cluster is determined by the votes of a quorum of nodes in the cluster.
l Failover coordination
Each resource is configured to be hosted on a primary node, and each can be manually or
automatically transferred to one or more secondary nodes. A health-based failover policy
controls automatic transfer of resource ownership between nodes. Nodes and hosted
applications are notified when failover occurs so that they can react appropriately.
Table 10-2 WSFC terms

Term Description
Node A Microsoft Server system that is an active

or inactive member of a server cluster.
Cluster resource A physical or logical entity that can be

owned by a node, brought online and taken
offline, moved between nodes, and managed
as a cluster object. A cluster resource can be
owned by only a single node at any point in
time.
Resource group A collection of cluster resources managed

as a single cluster object. Typically a
resource group contains all of the cluster
resources that are required to run a specific
application or service. Failover and failback
always act on resource groups.
Resource dependency A resource on which another resource

depends. If resource A depends on resource
B, then B is a dependency of A.
Network name resource A logical server name that is managed as a

cluster resource. A network name resource
must be used with an IP address resource.

Term Description
Preferred owner A node on which a resource group prefers to

run. Each resource group is associated with
a list of preferred owners sorted in order of
preference. During automatic failover, the
resource group is moved to the next
preferred node in the preferred owner list.
Possible owner A secondary node on which a resource can

run. Each resource group is associated with
a list of possible owners. Resource groups
can fail over only to nodes that are listed as
possible owners.
Quorum mode The quorum configuration in a failover

cluster that determines the number of node
failures that the cluster can sustain.
Forced quorum The process to start the cluster even through

only a minority of the elements that are
required for quorum are in communication.
10.1.2 Configuration
For details, visit:
https://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
10.2 Veritas VCS
10.2.1 Overview
Veritas Cluster Server (VCS) can connect multiple independent systems to a management
framework to improve availability. Each system (or node) runs its own operating system and
collaborates at the software level to form a cluster. The VCS combines common hardware
with intelligent software to provide failover and control for applications. If a node or a
monitored application becomes faulty, other nodes perform predefined operations to take over
services and start these services in other locations in the cluster.
10.2.2 Version Compatibility

The VCS software must meet the compatibility requirements of the host operating system.
VCS software of a specific version may not be suitable for all versions of Windows.
For details about the compatibility between VCS and Windows, see the Veritas Enterprise
Products and Platforms Matrix.

10.2.3 Installation and Configuration

For details on how to install and configure Veritas products, visit its official website: https://
sort.veritas.com/documents.
l For 6.1 and earlier versions, select Storage Foundation and High Availability for
Product to obtain the installation and configuration guide of the corresponding version.
l For 7.0 and later versions, select InfoScale Enterprise for Product to obtain the
installation and configuration guide of the corresponding version.

Huawei SAN Storage Host Connectivity Guide For Windows

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

Huawei SAN Storage Host Connectivity Guide For Windows

Uploaded by

Copyright:

Available Formats

Huawei SAN Storage Host

Connectivity Guide for Windows

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. i

1 About This Document.................................................................................................................. 1

4 Preparing for Configuration......................................................................................................32

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. ii

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. iii

8 Acronyms and Abbreviations................................................................................................. 104

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. iv

1 About This Document

1.3 Related Documents

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 1

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

Times New Roman Normal paragraphs are in Times New Roman.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in Courier

Boldface The keywords of a command line are in boldface.

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 2

Italic Command arguments are in italics.

1.5 Where To Get Help

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 3

2.1 Basic Concepts

2.1 Basic Concepts

2.1.1 Introduction to Windows Server

2.1.2 File Systems in Windows

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 4

Table 2-1 Comparison of FAST32, NTFS, exFAT, and ReFS

Specifications FAT32 NTFS exFAT ReFS

Operating Versions later Versions later Windows CE 6/ Versions later

Min. sector size 512 B 512 B 512 B 64 KB

Max. sector size 64 KB 64 KB 64 KB 64 KB

Max. file size 2 B to 4 GB Depends on the 16 EB 16 EB

Max. formatted 2 TB (NT 2 TB to 256 TB 16 EB 256 ZB when

Number of 4,194,304 None Greater than -

2.2 Host-SAN Connectivity

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 5

2.2.2 iSCSI Connectivity

Each iSCSI node can be identified in a number of ways, such as by:

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 6

2.2.3 Multipath Connectivity

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 7

MPIO supports the following policy settings:

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 8

l Support by Huawei storage

Table 2-2 Old- and new-version Huawei storage

Old-version Huawei T V1, T V2, 18000 V1, -

New-version Huawei V300R003C20, V300R006C00, V300R003C20: refers to

2.2.4 SAN Boot

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 9

2.3 Interoperability Query

Step 1 Log in to the website support-open.huawei.com.

Figure 2-1 Interoperability query page

The Huawei Storage Interoperability Navigator is displayed.

Issue 13 (2019-08-15) Copyright © Huawei Technologies Co., Ltd. 10

Figure 2-2 Query on Huawei Storage Interoperability Navigator

Table 2-3 Number of LUNs