huawei san storage host connectivity guide for...

Technical White Paper

HUAWEI SAN Storage Host Connectivity Guide for Windows

OceanStor Storage Windows

Huawei Technologies Co., Ltd. 2017-08-15

Issue (2017-05-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without

prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not

be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all

statements, information, and recommendations in this document are provided "AS IS" without warranties,

guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://e.huawei.com

http://e.huawei.com/

HUAWEI SAN Storage Host Connectivity Guide for Windows About This Document



ii

About This Document

Overview

This document details the configuration methods and precautions for connecting Huawei SAN

storage devices to Windows hosts.

Intended Audience

This document is intended for:

Huawei technical support engineers

Technical engineers of Huawei's partners

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows:

Symbol Description

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

avoided, will result in death or serious injury.

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

not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,

performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or save time.

Provides additional information to emphasize or supplement

important points of the main text.

HUAWEI SAN Storage Host Connectivity Guide for Windows About This Document



iii

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.

Italic Command arguments are in italics.

HUAWEI SAN Storage Host Connectivity Guide for Windows Contents



iv

Contents

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

1 Windows Operating System ....................................................................................................... 1

1.1 Overview ...................................................................................................................................................................... 1

1.2 System Information ...................................................................................................................................................... 1

1.3 File Systems in Windows .............................................................................................................................................. 2

1.4 Common Management Tools and Commands .............................................................................................................. 4

1.4.1 Remote Login ............................................................................................................................................................ 4

1.4.2 Management Tool ...................................................................................................................................................... 6

1.4.3 Disk Management Commands ................................................................................................................................... 9

1.5 Interoperability Between Windows and Storage Systems ........................................................................................... 12

2 Network Planning ....................................................................................................................... 14

2.2 Fibre Channel Networking Diagram ........................................................................................................................... 14

2.2.1 Multi-Path Directly Connected Network ................................................................................................................. 14

2.2.2 Multi-Path Switch-connected Network .................................................................................................................... 15

2.3 iSCSI Network Diagram ............................................................................................................................................. 17

2.3.1 Multi-Path Directly Connected Network ................................................................................................................. 17

2.3.2 Multi-Path Switch-connected Network .................................................................................................................... 18

2.4 HyperMetro Network .................................................................................................................................................. 19

2.4.1 Fibre Channel Networking Diagram ........................................................................................................................ 20

3 Preparations Before Configuration (on a Host)..................................................................... 22

3.1 Identifying HBAs........................................................................................................................................................ 22

3.2 Querying HBA Properties ........................................................................................................................................... 23

3.3 Windows Disk Timeout .............................................................................................................................................. 24

3.4 Modifying the Timeout Interval for the FC HBA Port Driver .................................................................................... 25

3.4.1 Modifying Emulex HBA Driver Parameters ............................................................................................................ 25

3.4.2 Modifying QLogic HBA Driver Parameters ............................................................................................................ 26

3.5 Modifying the iSCSI Initiator's Driver Timeout Interval ............................................................................................ 29

4 Preparations Before Configuration (on a Storage System) ................................................. 31

5 Configuring Switches ................................................................................................................. 32

5.1 Fibre Channel Switch ................................................................................................................................................. 32

5.1.1 Querying the Switch Model and Version ................................................................................................................. 32




v

5.1.2 Configuring Zones ................................................................................................................................................... 35

5.1.3 Precautions ............................................................................................................................................................... 38

5.2 Ethernet Switch ........................................................................................................................................................... 39

5.2.1 Configuring VLANs ................................................................................................................................................ 39

5.2.2 Binding Ports ........................................................................................................................................................... 40

5.3 FCoE Switch ............................................................................................................................................................... 42

5.3.1 Command Introduction ............................................................................................................................................ 42

5.3.2 Creating a VSAN ..................................................................................................................................................... 45

5.3.3 Creating a VLAN ..................................................................................................................................................... 46

5.3.4 Configuring a Port and Adding It to the VLAN ....................................................................................................... 47

5.3.5 Creating a Zone and Adding the Port to It ............................................................................................................... 48

5.3.6 Creating a Zoneset and Adding the Created Zone to It ............................................................................................ 49

6 Establishing Fibre Channel Connections ............................................................................... 51

6.1 Checking Topology Modes ......................................................................................................................................... 51

6.1.2 OceanStor T V1 Series Storage System ................................................................................................................... 52

6.1.3 OceanStor 18000/T V2 /V3 (V300R001) Series Enterprise Storage System ........................................................... 53

6.1.4 OceanStor V3 (V300R002 and Later)/Dorado V3 Series Enterprise Storage System ............................................. 53

6.2 Adding Initiators ......................................................................................................................................................... 54

6.3 Establishing Connections ............................................................................................................................................ 54

7 Establishing iSCSI Connections .............................................................................................. 56

7.2 Checking Windows iSCSI Initiator Software ............................................................................................................. 56

7.3 Configuring Storage Service IP Addresses ................................................................................................................. 57

7.3.1 OceanStor T Series Storage System ......................................................................................................................... 58

7.3.2 OceanStor 18000/T V2/V3 (V300R001) Series Enterprise Storage System ............................................................ 58


7.4 Host ............................................................................................................................................................................. 61

7.4.1 Configuring IP Addresses on a Host ........................................................................................................................ 61

7.4.2 Configuring Initiators on a Host .............................................................................................................................. 62

7.4.3 Establishing Connections ......................................................................................................................................... 64

7.5 Configuring CHAP Authentication ............................................................................................................................. 64

7.5.1 Storage System ........................................................................................................................................................ 65

7.5.2 Host .......................................................................................................................................................................... 71

8 Mapping and Using LUNs ........................................................................................................ 73

8.1 LUN mapping ............................................................................................................................................................. 73

8.1.1 OceanStor T Series Storage System ......................................................................................................................... 73

8.1.2 OceanStor 18000/T V2/V3 (V300R001) Series Enterprise Storage System ............................................................ 74


8.2 Using the Mapped LUNs ............................................................................................................................................ 76

9 Multipathing Management ....................................................................................................... 77

9.1 Overview .................................................................................................................................................................... 77




vi

9.2 MPIO Policies ............................................................................................................................................................. 77

9.3 Installation and Configuration .................................................................................................................................... 78

9.3.1 Precautions ............................................................................................................................................................... 78

9.3.2 Procedure ................................................................................................................................................................. 79

9.4 Common Management Commands ............................................................................................................................. 83

9.5 Uninstallation .............................................................................................................................................................. 85

10 Windows MPIO Policy Configuration ................................................................................. 87

10.1.1 NMP Configuration for New-Version HUAWEI Storage ...................................................................................... 87

10.1.2 Initiator Mode and Configuration .......................................................................................................................... 90

10.1.3 Storage Array Configuration .................................................................................................................................. 94

10.1.4 Host Configuration .............................................................................................................................................. 104

11 Volume Management ............................................................................................................. 109

12 Host High-Availability .......................................................................................................... 113

12.1 Overview ................................................................................................................................................................ 113

12.1.1 MSCS................................................................................................................................................................... 113

12.1.2 WSFC .................................................................................................................................................................. 114

12.2 Configuration .......................................................................................................................................................... 116

12.2.1 MSCS................................................................................................................................................................... 116

12.2.2 WSFC .................................................................................................................................................................. 116

13 Virtualization Technology .................................................................................................... 117

13.1 Introduction to Hyper-V ......................................................................................................................................... 117

13.2 Hyper-V Configuration ........................................................................................................................................... 117

13.2.1 Adding Hyper-V .................................................................................................................................................. 117

13.2.2 Creating Hyper-V VMs ........................................................................................................................................ 118

A Acronyms and Abbreviations ................................................................................................ 119

HUAWEI SAN Storage Host Connectivity Guide for Windows Figures



vii

Figures

Figure 1-1 System information .............................................................................................................................. 2

Figure 1-2 Firewall configuration ......................................................................................................................... 5

Figure 1-3 Remote desktop connection ................................................................................................................. 6

Figure 1-4 Server Manager .................................................................................................................................... 7

Figure 1-5 diskpart commands in GUI .................................................................................................................. 9

Figure 1-6 Interoperability query page ................................................................................................................ 13

Figure 1-7 Query on OceanStor Interoperability Navigator ................................................................................ 13

Figure 2-2 Fibre Channel multi-path directly connected network diagram (dual-controller) .............................. 15

Figure 2-3 Fibre Channel multi-path directly connected network diagram (four-controller) .............................. 15

Figure 2-4 Fibre Channel multi-path switch-connected network diagram (dual-controller) ............................... 16

Figure 2-5 Fibre Channel multi-path switch-connected network diagram (four-controller) ............................... 16

Figure 2-6 iSCSI multi-path directly connected network diagram (dual-controller) ........................................... 17

Figure 2-7 iSCSI multi-path directly connected network diagram (four-controller) ........................................... 18

Figure 2-8 iSCSI multi-path switch-connected network diagram (dual-controller) ............................................ 18

Figure 2-9 iSCSI multi-path switch-connected network diagram (four-controller) ............................................ 19

Figure 2-10 Fibre Channel multi-path switch-connected networking diagram (dual-controller) ........................ 20

Figure 2-11 Fibre Channel multi-path switch-connected networking diagram (four-controller) ........................ 21

Figure 3-1 Checking HBA installation in Device Manager ................................................................................. 22

Figure 3-2 Run the fcinfo command to query HBA information ........................................................................ 23

Figure 3-3 Running the Windows Server 2016's command to query the FC HBA and iSCSI initiator information

.............................................................................................................................................................................. 24

Figure 3-4 Configuring disk timeout in the registry ............................................................................................ 25

Figure 3-5 Modifying the values of the timeout parameters ............................................................................... 26

Figure 3-6 Management console CLI .................................................................................................................. 27

Figure 3-7 HBA parameters................................................................................................................................. 27

Figure 3-8 HBA port status.................................................................................................................................. 27

Figure 3-9 HBA parameters menu ....................................................................................................................... 28




viii

Figure 3-10 Configure Parameters Menu ........................................................................................................ 28

Figure 3-11 HBA parameter configuration .......................................................................................................... 29

Figure 3-12 Changing the iSCSI initiator driver timeout .................................................................................... 30

Figure 5-1 Switch information ............................................................................................................................ 33

Figure 5-2 Switch port indicator status................................................................................................................ 35

Figure 5-3 Zone tab page ..................................................................................................................................... 36

Figure 5-4 Zone configuration............................................................................................................................. 37

Figure 5-5 Zone Config tab page ......................................................................................................................... 38

Figure 5-6 Name Server page .............................................................................................................................. 38

Figure 5-7 DeviceManager Provisioning page ................................................................................................... 41

Figure 5-8 Bond Ports page................................................................................................................................ 41

Figure 5-9 Process for configuring an FCoE switch ........................................................................................... 42

Figure 6-1 Fibre Channel port details .................................................................................................................. 52



Figure 7-1 iSCSI Initiator page ........................................................................................................................... 57

Figure 7-2 Modifying IPv4 addresses ................................................................................................................. 58

Figure 7-3 Port configuration .............................................................................................................................. 60

Figure 7-4 Ethernet port configuration ................................................................................................................ 60

Figure 7-5 Modifying IPv4 addresses ................................................................................................................. 61

Figure 7-6 IP address modification page ............................................................................................................. 62

Figure 7-7 Entering the initiator name ................................................................................................................ 63

Figure 7-8 Configuring the target IP address ....................................................................................................... 64

Figure 7-9 Initiator CHAP configuration............................................................................................................. 65

Figure 7-10 CHAP Configuration dialog box ................................................................................................... 66

Figure 7-11 Create CHAP dialog box ................................................................................................................ 66

Figure 7-12 Assigning the CHAP account to the initiator ................................................................................... 67

Figure 7-13 Setting CHAP status ........................................................................................................................ 67

Figure 7-14 Enabling CHAP ............................................................................................................................... 68

Figure 7-15 Initiator status after CHAP is enabled .............................................................................................. 68

Figure 7-16 Storage configuration page .............................................................................................................. 69

Figure 7-17 Host configuration page ................................................................................................................... 69

Figure 7-18 Initiator configuration page ............................................................................................................. 69




ix

Figure 7-19 Storage configuration page .............................................................................................................. 70

Figure 7-20 Host configuration page ................................................................................................................... 70

Figure 7-21 Initiator configuration page ............................................................................................................. 71

Figure 7-22 Connecting to the target on a host through CHAP authentication ................................................... 72

Figure 9-1 Configuring MPIO parameters in the registry ................................................................................... 79

Figure 9-2 Adding Multipath I/O ........................................................................................................................ 80

Figure 9-3 Viewing VID and PID ........................................................................................................................ 80

Figure 9-4 Querying disk information ................................................................................................................. 81

Figure 9-5 Taking over Huawei storage .............................................................................................................. 81

Figure 9-6 MPIO policy management page......................................................................................................... 82

Figure 9-7 Path details configuration page .......................................................................................................... 83

Figure 9-8 Deleting iSCSI devices managed by MPIO ....................................................................................... 85

Figure 9-9 Deleting Multipath I/O ...................................................................................................................... 86

Figure 10-1 Going to the host configuration page ............................................................................................... 93

Figure 10-2 Selecting an initiator of which information you want to modify ..................................................... 93

Figure 10-3 Modifying initiator information ....................................................................................................... 94

Figure 10-4 Viewing the storage product information ....................................................................................... 104

Figure 10-5 Taking over Huawei storage .......................................................................................................... 104

Figure 10-6 Viewing disk properties ................................................................................................................. 105

Figure 10-7 Configuring the MPIO policy ........................................................................................................ 106

Figure 10-8 Activating the path verification function ....................................................................................... 107

Figure 10-9 Checking disk multipathing policy ................................................................................................ 108

Figure 11-1 Rescanning for disks ...................................................................................................................... 110

Figure 11-2 Setting the identified disks online .................................................................................................. 110

Figure 11-3 Initializing disks ............................................................................................................................. 111

Figure 11-4 New RAID-5 volume dialog box ................................................................................................... 111

HUAWEI SAN Storage Host Connectivity Guide for Windows Tables



x

Tables

Table 1-1 Comparison among the four file systems .............................................................................................. 3

Table 1-2 Restrictions of NTFS with GPT disks ................................................................................................... 4

Table 2-1 Networking modes ............................................................................................................................... 14

Table 3-1 Management tools of mainstream HBAs ............................................................................................. 23

Table 5-1 Mapping between switch types and names .......................................................................................... 33

Table 5-2 Comparison of link aggregation modes ............................................................................................... 40

Table 6-1 Comparison among the three topology modes .................................................................................... 51

Table 9-1 Default MPIO policy ........................................................................................................................... 82

Table 9-2 CMD commands for MPIO management ............................................................................................ 84

Table 9-3 Meaning of parameter num in the command for modifying the load balancing policy ....................... 84

Table 10-1 Configuration methods and application scenarios of the typical working modes .............................. 88

Table 10-2 HUAWEI storage's support for ALUA .............................................................................................. 89

Table 10-3 Initiator parameter description ........................................................................................................... 90

Table 10-4 ALUA configuration for HUAWEI OceanStor T series ..................................................................... 94

Table 10-5 ALUA configuration for OceanStor V3 ............................................................................................. 95

Table 10-6 Configuration on storage arrays when Emulex HBAs are used in non-NPIV mode ......................... 96

Table 10-7 Configuration on storage arrays when QLogic HBAs are used in non-NPIV mode.......................... 98

Table 10-8 Configuration on storage arrays when Emulex HBAs are used in NPIV mode............................... 100

Table 10-9 Configuration on storage arrays when QLogic HBAs are used in NPIV mode ............................... 102

Table 12-1 Maximum number of nodes supported by different storage systems............................................... 114

Table 12-2 WSFC terms .................................................................................................................................... 115

HUAWEI SAN Storage Host Connectivity Guide for Windows 1 Windows Operating System



1

1 Windows Operating System

1.1 Overview

Windows is a Microsoft operating system intended for servers. Each Windows Server Edition

has a corresponding home (workstation) edition, except Windows Server 2003 R2.

1.2 System Information

On a Windows host, choose Start > Run. In the Run dialog box that is displayed, enter

msconfig to start the system configuration module. Choose tools > system information and

click Launch. The displayed window shows the system information, as shown in Figure 1-1.




2

Figure 1-1 System information

You can also use the MS-DOS command systeminfo to obtain the previous information.

On Windows Server 2008 and later operating systems, you can run the slmgr.vbs –dlv

command on the MS-DOS command-line interface (CLI) to obtain more details.

1.3 File Systems in Windows

Windows supports the following file systems:

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, FAT has a serious drawback. After a file is deleted, new data is written onto the file location in chunks, which lowers later data read/write speeds.




3

FAT32

FAT32 is similar to FAT. One difference is that FAT32 applies to larger disk applications.

FAT supports only 4 GB partitions or volumes whereas those supported by FAT32 can be

up to 2 TB.

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.

exFAT

Extended File Allocation Table File System (exFAT) is a Microsoft file system optimized

for 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.

Compared with exFAT, NTFS is inapplicable to flash drives.

ReFS

Resilient File System (ReFS) is a new file system introduced with Windows Server 2012.

ReFS aims to improve the availability and fault tolerance capability in the big data era.

When interworking with Space Storage, ReFS provides a comprehensive, end-to-end,

and flexible storage architecture.

Table 1-1 Comparison among the four file systems

Specifications FAT32 NTFS exFAT ReFS

Operating system Versions later

than Win 95

OSR2

Versions later

than Win 2000

Win CE 6/Vista

SP1

Versions later

than Win 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 Depending on

the max.

partition

capacity

16 EB 16 EB

Max. formatted

capacity

2 TB (NT

kernel: 32 GB)

2 TB to 256 TB

(depending on

the MBR)

16 EB

(theoretical

value, 256 TB

is supported

currently)

256 ZB using

16 KB cluster

sizes. Windows

stack

addressing: 16

EB

Number of

archives

4,194,304 None At least 1000

Table 1-2 lists the restrictions of NTFS with GPT disks.




4

Table 1-2 Restrictions 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)

1.4 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.

1.4.1 Remote Login

Perform the following steps to manage a host using the remote desktop:

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 1-2.




5

Figure 1-2 Firewall configuration

CAUTION

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 1-3.




6

Figure 1-3 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 user and password of the managed host.

----End

1.4.2 Management Tool

Window 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.

1.4.2.1 Starting Server Manager

Perform the following steps to start Server Manager:

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 1-4.




7

Figure 1-4 Server Manager

In the navigation tree, choose Storage > Disk Management. The disks available for

management are displayed.

----End

1.4.2.2 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:

Master Boot Record (MBR)

GUID Partition Table (GPT)

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:

http://technet.microsoft.com/zh-cn/library/cc738081%28v=ws.10%29.aspx

In Windows, disks are categorized as basic disks 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,

http://technet.microsoft.com/zh-cn/library/cc738081%28v=ws.10%29.aspx




8

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.




9

1.4.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 1-5 shows the diskpart commands.

Figure 1-5 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 2 Scan for LUNs.

DISKPART> rescan

Please wait while DiskPart scans your configuration...

DiskPart has finished scanning your configuration.

DISKPART> list disk




10

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 3 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




11


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



Disk 2 Online 5120 MB 5120 MB

Disk 3 Online 10 GB 0 B *

* Disk 4 Online 20 GB 0 B *

Step 4 Convert disks to dynamic disks.



DISKPART> convert dynamic

DiskPart successfully converted the selected disk to dynamic format.









Step 5 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 6 Format the volume.




12

DISKPART> format

100 percent completed

DiskPart successfully formatted the volume.



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



* Volume 2 NTFS RAID-5 100 MB Healthy

Step 7 Mount the file system.

DISKPART> assign

DiskPart successfully assigned the drive letter or mount point.



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



* Volume 2 D NTFS RAID-5 100 MB Healthy

----End

Compared with the GUI-based disk management, the CLI disk management commands in Windows are

complex. However, those CLI commands are very useful in automatic management and tests.

1.5 Interoperability Between Windows and Storage Systems

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.




13

Figure 1-6 Interoperability query page

Then, the OceanStor Interoperability Navigator is displayed.

Step 3 Select the components to query and click Submit.

Figure 1-7 Query on OceanStor Interoperability Navigator

----End

HUAWEI SAN Storage Host Connectivity Guide for Windows 2 Network Planning



14

2 Network Planning

Windows hosts and storage systems can be networked based on different criteria.

Table 2-1 Networking modes

Criteria Networking Mode

Interface module type Fibre Channel network, iSCSI network, or Fibre Channel over

Ethernet (FCoE) network

Whether switches are

used

Directly-connected network (no switches are used) or

switch-based network (switches are used)

Whether multiple paths

exist

Single-path network or multi-path network

A Fibre Channel network is the most widely used network for Windows operating systems. To

ensure service data security, both directly connected network and switch-connected network

are multi-path networks.

For specific networking connections, refer to the storage system's Quick Installation Guide.

2.2 Fibre Channel Networking Diagram

2.2.1 Multi-Path Directly Connected Network

Huawei provides dual-controller and multi-controller storage systems, whose network

diagrams differ. The following describes network diagrams of dual-controller and

multi-controller storage systems respectively.

2.2.1.1 Dual-Controller

The following uses HUAWEI OceanStor 5800 V3 as an example to explain how to connect a

Windows host to a storage system over a Fibre Channel multi-path directly connected

network, as shown in Figure 2-2.




15

Figure 2-1 Fibre Channel multi-path directly connected network diagram (dual-controller)

On this network, both controllers of the storage system are connected to the host's HBA through optical

fibers.

2.2.1.2 Multi-Controller

The following uses HUAWEI OceanStor 18500 V3 (four-controller) as an example to explain

how to connect a Windows host to a storage system over a Fibre Channel multi-path directly

connected network, as shown in Figure 2-2.

Figure 2-2 Fibre Channel multi-path directly connected network diagram (four-controller)

On this network, the four controllers of the storage system are connected to the host's HBAs through

optical fibers.

2.2.2 Multi-Path Switch-connected Network







16



Windows host to a storage system over a Fibre Channel multi-path switch-connected network,

as shown in Figure 2-3.

Figure 2-3 Fibre Channel multi-path switch-connected network diagram (dual-controller)

On this network, the storage system is connected to the host via two switches. Both controllers of the

storage system are connected to the switches through optical fibers and both switches are connected to

the host through optical fibers. To ensure the connectivity between the host and the storage system, each

zone contains only one storage port and its corresponding host port.



how to connect a Windows host to a storage system over a Fibre Channel multi-path

switch-connected network, as shown in Figure 2-4.

Figure 2-4 Fibre Channel multi-path switch-connected network diagram (four-controller)




17

On this network, the storage system is connected to the host via two switches. All controllers of the

storage system are connected to the switches through optical fibers and both switches are connected to


zone contains only one storage port and its corresponding host port.

2.3 iSCSI Network Diagram

2.3.1 Multi-Path Directly Connected Network






Windows host to a storage system over an iSCSI multi-path directly connected network, as


Figure 2-5 iSCSI multi-path directly connected network diagram (dual-controller)

On this network, both controllers of the storage system are connected to the host's network adapter

through Ethernet cables.



how to connect a Windows host to a storage system over an iSCSI multi-path directly

connected network, as shown in Figure 2-6.




18

Figure 2-6 iSCSI multi-path directly connected network diagram (four-controller)

On this network, the four controllers of the storage system are connected to the host's network adapter

through Ethernet cables.

2.3.2 Multi-Path Switch-connected Network






Windows host to a storage system over an iSCSI multi-path switch-connected network, as


Figure 2-7 iSCSI multi-path switch-connected network diagram (dual-controller)




19

On this network, the storage system is connected to the host via two Ethernet switches. Both controllers

of the storage system are connected to the switches through Ethernet cables and both switches are

connected to the host's network adapter through Ethernet cables. To ensure the connectivity between the

host and the storage system, each VLAN contains only one storage port and its corresponding host port.



how to connect a Windows host to a storage system over an iSCSI multi-path


Figure 2-8 iSCSI multi-path switch-connected network diagram (four-controller)

On this network, the storage system is connected to the host via two Ethernet switches. All controllers of

the storage system are connected to the switches through Ethernet cables and both switches are

connected to the host's network adapter through Ethernet cables. To ensure the connectivity between the

host and the storage system, each VLAN contains only one storage port and its corresponding host port.

2.4 HyperMetro Network

HyperMetro using the OS native multipathing function has the following networking

requirements:

Uses the multi-path switch-connected networking by default.

In the switches' zone configuration, allows a zone to only contain one initiator and one

target.

You are advised to use dual-switch networking to prevent single points of failure.




20

2.4.1 Fibre Channel Networking Diagram

2.4.1.1 Multi-Path Switch-connected Networking




2.4.1.1.1 Dual-Controller

The following uses HUAWEI OceanStor 6800 V3 (dual-controller) as an example to explain

how to connect a VMware host to a storage system over a Fibre Channel multi-path


Figure 2-9 Fibre Channel multi-path switch-connected networking diagram (dual-controller)

On this network, the storage system is connected to the host via two switches. The two storage systems'

two controllers are connected to the switches through optical fibers and both switches are connected to


zone contains only one storage port and its corresponding host port. In this example, the two storage

systems' two controllers are interconnected through optical cables to form replication links. Alternatively,

you can also connect the two controllers through a switch to form replication links.

2.4.1.1.2 Multi-Controller


how to connect a Windows host to a storage system over a Fibre Channel multi-path





21

Figure 2-10 Fibre Channel multi-path switch-connected networking diagram (four-controller)

On this network, the storage system is connected to the host via two switches. All the two storage

systems' four controllers are connected to the switches through optical fibers and both switches are

connected to the host through optical fibers. To ensure the connectivity between the host and the storage

system, each zone contains only one storage port and its corresponding host port. In this example, the

two storage systems' four controllers are interconnected through optical cables to form replication links.

Alternatively, you can also connect the four controllers through two switches to form replication links.

HUAWEI SAN Storage Host Connectivity Guide for Windows 3 Preparations Before Configuration (on a Host)



22

3 Preparations Before Configuration (on a Host)

Before connecting a host to a storage system, make sure that the host HBAs are identified

and working correctly. You also need to obtain the WWNs of HBA ports. The WWNs will be

used in subsequent configuration on the storage system.

This chapter details how to check the HBA status and query WWNs of HBA ports.

3.1 Identifying HBAs

After an HBA is installed on a host, you can view whether the HBA exists in Device

Management. 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. If an HBA is a Fibre Channel HBA, insert the optical

module. Then check whether the driver is installed correctly by viewing whether light comes

out from the optical module outlet.

Figure 3-1 Checking HBA installation in Device Manager




23

3.2 Querying HBA Properties

After an HBA is installed on a host and the host is powered on, open Device Management to

check whether the HBA is identified and whether the driver needs to be installed manually.

Further management of the HBA requires that the corresponding management software be

installed.

Table 3-1 lists the management tools of mainstream HBAs.

Table 3-1 Management tools of mainstream HBAs

Vendor Management Software

QLogic Sansurfer

Emulex OneCommmand Manager

Brocade Brocade Adapter Software

ATTO Windows Host Adapter Utilities

In addition, you can download the query program Fibre Channel Information Tool at:

http://www.microsoft.com/en-us/download/details.aspx?id=17530

After the software is installed, run fcinfo on the DOS CLI to obtain the HBA information, as


Figure 3-2 Run the fcinfo command to query HBA information

For Windows Server 2012 and later versions, Windows PowerShell provides a command

Get-InitiatorPort for query the WWN and iSCSI initiator information of the FC HBA card.

Figure 3-3 shows that FC HBA query using PowerShell of Windows Server 2016.

http://www.microsoft.com/en-us/download/details.aspx?id=17530




24

Figure 3-3 Running the Windows Server 2016's command to query the FC HBA and iSCSI

initiator information

3.3 Windows Disk Timeout

If a host's request for disk data has no response during a disk timeout, the operating system of

the host considers no response as normal. However, if the host still receives no response after

the disk timeout expires, the host operating system reports an error or abandons this data

request.

By default, the disk timeout in Windows is 60 seconds. The disk timeout can be changed in

some special conditions, for example, installing drivers. In this case, you need to change the

disk timeout to 60 seconds.

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.

If no, right-click the function pane and choose New > DWORD Value. Set the name to

TimeOutValue and go to step 4.

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 3-4.




25

Figure 3-4 Configuring disk timeout in the registry

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

----End

3.4 Modifying the Timeout Interval for the FC HBA Port Driver

When a Windows host connects to a storage array through FC HBA, 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.

3.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:

https://www.broadcom.com/products/storage/fibre-channel-host-bus-adapters/onecommand-m

anager-centralized#downloads

https://www.broadcom.com/products/storage/fibre-channel-host-bus-adapters/onecommand-manager-centralized#downloads

https://www.broadcom.com/products/storage/fibre-channel-host-bus-adapters/onecommand-manager-centralized#downloads




26

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 3-5.

Figure 3-5 Modifying the values of the timeout parameters

----End

3.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, double-click the icon to open this tool

(2.1.0 build 11) and run the qaucli command to navigate to the management CLI window.

http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNewSearch.aspx




27

Figure 3-6 Management console CLI

Step 3 Set HBA parameters.

Select 2: Adapter Configuration. The following window is displayed.

Figure 3-7 HBA parameters

Select 3: HBA Parameters. The HBA port status window is displayed.

Figure 3-8 HBA port status

Select a port and go to the HBA Parameters Menu.




28

Figure 3-9 HBA parameters menu

Select 2: Configure HBA Parameters. The Configure Parameters Menu window is

displayed.

Figure 3-10 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.




29

Figure 3-11 HBA parameter configuration

Step 4 Complete the configurations of all ports

Step 5 Repeat Step XX to configure other ports.

----End

3.5 Modifying the iSCSI Initiator's Driver Timeout Interval

During an iSCSI initiator driver timeout, 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 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 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





30

Figure 3-12 Changing the iSCSI initiator driver timeout

Step 3 Modify the registry key.

By default, LinkDownTime and MaxRequestHoldTime are 15 seconds and 60 seconds

respectively. On a multi-path network, the path failover time decreases with the values of the

two parameters.

CAUTION

For details about how to configure LinkDownTime and MaxRequestHoldTime, see:

http://blogs.msdn.com/b/san/archive/2008/07/27/microsoft-iscsi-software-initiator-isns-server

-timers-quick-reference.aspx

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.

Step 4 Restart the host for the change to take effect.

----End

http://blogs.msdn.com/b/san/archive/2008/07/27/microsoft-iscsi-software-initiator-isns-server-timers-quick-reference.aspx

http://blogs.msdn.com/b/san/archive/2008/07/27/microsoft-iscsi-software-initiator-isns-server-timers-quick-reference.aspx

HUAWEI SAN Storage Host Connectivity Guide for Windows

4 Preparations Before Configuration (on a Storage

System)



31

4 Preparations Before Configuration (on a Storage System)

Make sure that RAID groups, LUNs, and hosts are correctly created on the storage systems.

For details, refer to the specific storage system's Configuration Guide.

HUAWEI SAN Storage Host Connectivity Guide for Windows 5 Configuring Switches



32

5 Configuring Switches

Windows hosts and storage systems can be connected over a Fibre Channel switch-connected

network, an iSCSI switch-connected network, and an FCoE switch-connected network. The

three types of networks use Fibre Channel switches, Ethernet switches, and FCoE switches

respectively. This chapter describes how to configure those switches.

5.1 Fibre Channel Switch

The commonly used Fibre Channel switches are from vendors such as Brocade and QLogic.

The following uses a Brocade switch as an example to explain how to configure switches.

5.1.1 Querying the Switch Model and Version

Perform the following steps to query the switch model and version:

Step 1 Log in to the Brocade switch from a web page.

On the web page, enter the IP address of the Brocade switch. The Web Tools switch login

dialog box is displayed. Enter the account and password. The default account and password

are admin and password. The switch management page is displayed.

CAUTION

Web Tools works correctly only when Java is installed on the host. Java 1.6 or later is

recommended.

Step 2 View the switch information.

On the switch management page that is displayed, click Switch Information. The switch

information is displayed, as shown in Figure 5-1.




33

Figure 5-1 Switch information

Note the following parameters:

Fabric OS version: indicates the switch version information. The interoperability

between switches and storage systems varies with the switch version. Only switches of

authenticated versions can interconnect correctly with storage systems.

Type: This parameter is a decimal consists 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 switch

model mapping.

Table 5-1 Mapping between switch types and names

Switch Type

Switch Name Switch Type

Switch Name

1 Brocade 1000 Switch 58 Brocade 5000 Switch

2,6 Brocade 2800 Switch 61 Brocade 4424 Embedded

Switch

3 Brocade 2100, 2400 Switches 62 Brocade DCX Backbone

4 Brocade 20x0, 2010, 2040,

2050 Switches

64 Brocade 5300 Switch

5 Brocade 22x0, 2210, 2240,

2250 Switches


7 Brocade 2000 Switch 67 Brocade Encryption Switch




34

Switch Type


Switch Name

9 Brocade 3800 Switch 69 Brocade 5410 Blade

10 Brocade 12000 Director 70 Brocade 5410 Embedded

Switch

12 Brocade 3900 Switch 71 Brocade 300 Switch

16 Brocade 3200 Switch 72 Brocade 5480 Embedded

Switch

17 Brocade 3800VL 73 Brocade 5470 Embedded

Switch

18 Brocade 3000 Switch 75 Brocade M5424 Embedded

Switch

21 Brocade 24000 Director 76 Brocade 8000 Switch

22 Brocade 3016 Switch 77 Brocade DCX-4S

Backbone

26 Brocade 3850 Switch 83 Brocade 7800 Extension

Switch


Switch

29 Brocade 4012 Embedded

Switch 87 Brocade 5460 Embedded

Switch


Switch

33 Brocade 3014 Switch 92 Brocade VA-40FC Switch

34 Brocade 200E Switch 95 Brocade VDX 6720-24

Data Center Switch


Switch 96 Brocade VDX 6730-32

Data Center Switch

38 Brocade 7420 SAN Router 97 Brocade VDX 6720-60

Data Center Switch

40 Fibre Channel Routing (FCR)

Front Domain

98 Brocade VDX 6730-76

Data Center Switch

41 Fibre Channel Routing,

(FCR) Xlate Domain

108 Dell M8428-k FCoE

Embedded Switch

42 Brocade 48000 Director 109 Brocade 6510 Switch


Switch

116 Brocade VDX 6710 Data

Center Switch


Switch




35

Switch Type


Switch Name


Switch


46 Brocade 7500 Switch 120 Brocade DCX 8510-8

Backbone


Switch

121 Brocade DCX 8510-4

Backbone

55.2 Brocade 7600 Switch

Ethernet IPv4: indicates the switch IP address.

Effective Configuration: indicates the currently effective configurations. This parameter

is important and is related to zone configurations. In this example, the currently effective

configuration is ss.

----End

5.1.2 Configuring Zones

Zone configuration is important for Fibre Channel switches. The zone configurations

differ with the switch vendor, model, and version. For details, refer to the specific switch's

Configuration Guide. With the Brocade 300 switch as an example, the zone configuration

steps are as follows:

Step 1 Log in to the Brocade switch from a web page. This step is the same as that in section 5.1.1

"Querying the Switch Model and Version."

Step 2 Check the switch port status.

Normally, the switch port indicators are steady green, as shown in Figure 5-2.

Figure 5-2 Switch port indicator status

If the port indicators are abnormal, check the topology mode and rate. Proceed with the next

step after all indicators are normal.

Step 3 Go to the Zone Admin page.

On the menu bar of the switch, choose Configure > Zone Admin.




36

Step 4 Check whether the switch identifies hosts and storage systems.

On the Zone Admin page, click the Zone tab. In Member Selection List, check whether all

related ports are identified, as shown in Figure 5-3.

Figure 5-3 Zone tab page

The preceding figure shows that ports 1,16 and 1,17 in use are correctly identified by the

switch.

Step 5 Create a zone.

When configuring a zone, you can add a switch to a zone by the switch port or the switch

ports' connected device WWN. This section describes zone configuration by WWN.

On the Zone tab page, click New Zone to create a new zone and name it R910_2. Select the

device WWN numbers of ports 1,3 (connecting the storage system) and 1,17 (connecting the

host), and click Add Member to add them to the new zone, as shown in Figure 5-4.




37

Figure 5-4 Zone configuration

Step 6 Add the new zone to the configuration file and activate the new zone.

On the Zone Admin page, click the Zone Config tab. In the Name drop-down list, choose the

currently effective configuration Dell_R910.

In Member Selection List, select zone R910_2 and click Add Member to add it to the

configuration file.

Click Save Config to save the configuration and click Enable Config to make the

configuration effective.

Figure 5-5 shows the Zone Config page.




38

Figure 5-5 Zone Config tab page

Step 7 Verify that the configuration takes effect.

In the navigation tree of Web Tools, choose Task > Monitor > Name Server to go to the

Name Server page. You can also choose Monitor > Name Server in the navigation bar.

Figure 5-6 shows the Name Server page.

Figure 5-6 Name Server page

The preceding figure shows that the WWNs have been added to the zone that is now effective.

An effective zone is marked by an asterisk (*).

----End

5.1.3 Precautions

Note the following when connecting a Brocade switch to a storage system at a rate of 8

Gbit/s:

The topology mode of the storage system must be set to switch.




39

fill word of ports through which the switch is connected to the storage system must be

set to 0. To configure this parameter, run the portcfgfillword <port number> 0

command on the switch.

Note the following when connecting a Brocade switch to a storage system at a rate of 8

Gbit/s:

When the switch is connected to module HP VC 8Gb 20-port FC or HP VC

FlexFabric 10Gb/24-port, change the switch configuration. For details, refer to the HP

Virtual Connect FlexFabric Cookbook:

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02616817

5.2 Ethernet Switch

This section describes how to configure Ethernet switches, including configuring VLANs and

binding ports.

5.2.1 Configuring VLANs

On an Ethernet network to which many hosts are connected, a large number of broadcast

packets are generated during the host communication. Broadcast packets sent from one

host will be received by all other hosts on the network, consuming more bandwidth. Moreover,

all hosts on the network can access each other, resulting data security risks.

To save bandwidth and prevent security risks, hosts on an Ethernet network are divided into

multiple logical groups. 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 the IP address of VLAN 1000.

[Quidway-vlan1000]interface VLAN 1000

[Quidway-Vlan-interface1000]ip address 1.0.0.1 255.255.255.0

Step 4 Create VLAN 2000, add ports, and configure the 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 2.0.0.1 255.255.255.0

----End




40

5.2.2 Binding Ports

When storage systems and hosts are connected in point-to-point mode, existing bandwidth

may be insufficient for storage data transmission. Moreover, devices cannot be redundantly

connected in point-to-point mode. To address these problems, ports are bound (link

aggregation). Port binding can improve bandwidth and balance load among multiple links.

5.2.2.1 Link Aggregation Modes

Three Ethernet link aggregation modes are available:

Manual aggregation

Manually run a command to add ports to an aggregation group. Ports added to the

aggregation group must have the same link type.

Static aggregation

Manually run a command to add ports to an aggregation group. Ports added to the

aggregation group must have the same link type and LACP enabled.

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 the three link aggregation modes.

Table 5-2 Comparison of link aggregation modes

Link Aggregation Mode

Packet Exchange Port Detection CPU Usage

Manual aggregation No No Low

Static aggregation Yes Yes High

Dynamic

aggregation

Yes Yes High

5.2.2.2 Procedure

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 and at the same speed. After binding iSCSI host ports on a storage

device, enable aggregation for their peer ports on a 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 IOM1 module's ports P0 and P1 as

examples to explain how to bind ports. The two ports on the storage system are

CTE0.A.IOM1.P0 and CTE0.A.IOM1.P1.

The port binding method differs with the OceanStor system version. For details, refer to the

specific storage product documentation. The following steps show how to bind ports (with

OceanStor V3 V300R003 as an example).

Step 1 Log in to the DeviceManager and go to the page for binding ports.

In the DeviceManager navigation tree, choose Provisioning > Port.




41

Figure 5-7 DeviceManager Provisioning page

Step 2 Bind ports.

Select the ports that you want to bind and choose Bind Ports > Create in the menu bar.

The Create Bound Port dialog box is displayed. In Name, enter the name for the port to be

bound, select the Controller housing the port, select the target ports, and click OK.

Figure 5-8 Bond Ports page

After the storage system ports are bound, configure link aggregation on the switch. Run the

following command on the switch:

<Quidway>system-view

System View: return to User View with Ctrl+Z.

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

[Quidway-Switch-GigabitEthernet1/0/19]lacp enable

LACP is already enabled on the port!

[Quidway-Switch-GigabitEthernet1/0/19]quit

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

[Quidway-Switch-GigabitEthernet1/0/20]lacp enable




42

LACP is already enabled on the port!

[Quidway-Switch-GigabitEthernet1/0/20]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.3 FCoE Switch

The configurations of FCoE switches are different from those of FC switches and Ethernet

switches. For details, see the specific switch vendor-provided configuration guide.

Taking Cisco Nexus5548 as an example, Figure 5-9 shows an FCoE configuration process.

Figure 5-9 Process for configuring an FCoE switch

5.3.1 Command Introduction

When using SSH to log in to and manage an FCoE switch, you can have all supported

commands displayed by inputting "?":

switch# ?

callhome Callhome commands

cd Change current directory

cfs CFS parameters

checkpoint Create configuration rollback checkpoint

clear Reset functions

cli CLI commands

clock Manage the system clock

configure Enter configuration mode

copy Copy from one file to another

debug Debugging functions

debug-filter Enable filtering for debugging functions

delete Delete a file or directory

diff-clean Remove temp files created by '| diff' filters

dir List files in a directory

discover Discover information

dos2nxos DOS to NXOS text file format converter

echo Echo argument back to screen (useful for scripts)




43

ethanalyzer Configure cisco packet analyzer

event Event Manager commands

fcdomain Fcdomain internal command

fcping Ping an N-Port

fctrace Trace the route for an N-Port.

find Find a file below the current directory

fips Enable/Disable FIPS mode

gunzip Uncompresses LZ77 coded files

gzip Compresses file using LZ77 coding

hardware Change hardware usage settings

install Upgrade software

ip Configure IP features

ipv6 Configure IPv6 features

load Load system image

locator-led Turn on locator beacon

mkdir Create new directory

modem Modem commands

move Move files

mping Run mping

mtrace Trace multicast path from receiver to source

no Negate a command or set its defaults

ntp NTP configuration

ping Test network reachability

ping6 Test IPv6 network reachability

pktmgr Display Packet Manager information

purge Deletes unused data

pwd View current directory

reload Reboot the entire box

restart Manually restart a component

rmdir Delete a directory

rollback Rollback configuration

routing-context Set the routing context

run-script Run shell scripts

san-port-channel Port-Channel related commands

scripting Configure scripting parameters

send Send message to open sessions

setup Run the basic SETUP command facility

show Show running system information

sleep Sleep for the specified number of seconds

sockets Display sockets status and configuration

ssh SSH to another system

system System management commands

system System configuration commands

tac-pac Save tac info in a compressed .gz file at specific location

tail Display the last part of a file

tar Archiving operations

tclsh Source tclsh script

telnet Telnet to another system

telnet6 Telnet6 to another system using IPv6 addressing

terminal Set terminal line parameters

test Test command

traceroute Traceroute to destination

traceroute6 Traceroute6 to destination

undebug Disable Debugging functions (See also debug)

write Write current configuration




44

xml Xml agent

xml Module XML agent

zone Execute Zone Server commands

zoneset Execute zoneset commands

end Go to exec mode

exit Exit from command interpreter

pop Pop mode from stack or restore from name

push Push current mode to stack or save it under name

where Shows the cli context you are in

switch#

For example, to query the model and version, run the following command:

switch# show version

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Documents:

http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html

Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 3.5.0

loader: version N/A

kickstart: version 5.1(3)N1(1a)

system: version 5.1(3)N1(1a)

power-seq: Module 1: version v1.0

Module 3: version v2.0

uC: version v1.2.0.1

SFP uC: Module 1: v1.0.0.0

BIOS compile time: 02/03/2011

kickstart image file is: bootflash:///n5000-uk9-kickstart.5.1.3.N1.1a.bin

kickstart compile time: 2/7/2012 23:00:00 [02/08/2012 07:49:30]

system image file is: bootflash:///n5000-uk9.5.1.3.N1.1a.bin

system compile time: 2/7/2012 23:00:00 [02/08/2012 12:44:33]

Hardware

cisco Nexus5548 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")

Intel(R) Xeon(R) CPU with 8263880 kB of memory.

Processor Board ID FOC16256KUW

Device name: switch

bootflash: 2007040 KB

Kernel uptime is 15 day(s), 1 hour(s), 59 minute(s), 8 second(s)

Last reset at 299763 usecs after Wed Feb 18 05:48:07 2009

Reason: Reset Requested by CLI command reload

System version: 5.1(3)N1(1a)




45

Service:

plugin

Core Plugin, Ethernet Plugin, Fc Plugin

5.3.2 Creating a VSAN

To create a VSAN on a Cisco Nexus5548 VSAN, do as follows:

Step 1 Activate FCoE.

switch# conf t

Enter configuration commands, one per line. End with CNTL/Z.

switch(config)# feature fcoe

fcoe fcoe-npv

switch(config)# feature fcoe

switch(config)# show fcoe

Global FCF details

FCF-MAC is 54:7f:ee:b4:f8:20

FC-MAP is 0e:fc:00

FCF Priority is 128

FKA Advertisement period for FCF is 8 seconds

Step 2 Create a VSAN.

In the following display, the switch(config-vsan-db)# vsan 200 command in red is the VSAN

create command. Additionally, you can run show vsan command to check whether the VSAN

is created successfully.

switch(config)# show vsan

vsan 1 information

name:VSAN0001 state:active

interoperability mode:default

loadbalancing:src-id/dst-id/oxid

operational state:down

vsan 100 information




operational state:up

vsan 4079:evfp_isolated_vsan

vsan 4094:isolated_vsan

switch(config)# vsan database

switch(config-vsan-db)# vsan 200

switch(config-vsan-db)# exit

switch(config)# show vsan

vsan 1 information









46




operational state:up






vsan 4079:evfp_isolated_vsan

vsan 4094:isolated_vsan

----End

5.3.3 Creating a VLAN

To create a VLAN on a CISCO Nexus5548, do as follows:

Step 1 Check for existing VLANs.

switch(config)# show vlan

VLAN Name Status Ports

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

1 default active Eth1/1, Eth1/2, Eth1/4, Eth1/5

Eth1/6, Eth1/7, Eth1/8, Eth1/15

Eth1/21, Eth1/22, Eth1/23

Eth1/24, Eth1/25, Eth1/26

Eth1/27, Eth1/28

100 VLAN0100 active Eth1/1, Eth1/2, Eth1/3, Eth1/4

Eth1/5, Eth1/6, Eth1/7, Eth1/8

Eth1/9, Eth1/10, Eth1/11

Eth1/12, Eth1/13, Eth1/14

Eth1/15, Eth1/16, Eth1/17

Eth1/18, Eth1/19, Eth1/20

VLAN Type Vlan-mode

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

1 enet CE

100 enet CE

Remote SPAN VLANs

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

Primary Secondary Type Ports

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

Step 2 Create a VLAN and check whether the creation is successful.

switch(config)# vlan 200

switch(config-vlan)# show vlan




47

VLAN Name Status Ports

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

1 default active Eth1/1, Eth1/2, Eth1/4, Eth1/5

Eth1/6, Eth1/7, Eth1/8, Eth1/15

Eth1/21, Eth1/22, Eth1/23

Eth1/24, Eth1/25, Eth1/26

Eth1/27, Eth1/28


Eth1/5, Eth1/6, Eth1/7, Eth1/8

Eth1/9, Eth1/10, Eth1/11

Eth1/12, Eth1/13, Eth1/14

Eth1/15, Eth1/16, Eth1/17

Eth1/18, Eth1/19, Eth1/20


Eth1/6, Eth1/7, Eth1/8, Eth1/15

VLAN Type Vlan-mode

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

1 enet CE

100 enet CE

200 enet CE

Remote SPAN VLANs

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

Primary Secondary Type Ports

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

----End

5.3.4 Configuring a Port and Adding It to the VLAN

To configure and add a port to a created VLAN, do as follows:

Step 1 Configure the port running mode and add it to the VLAN.

switch (config)# interface ethernet 1/1

switch (config-if)# switchport mode trunk

switch (config-if)# spanning-tree port type edge trunk

Step 2 Create a VFC and bind it to the physical port.

switch (config)# interface vfc 1

switch (config-if)# bind interface ethernet 1/1

switch (config-if)# no shutdown

Step 3 Add the new VFC to the VSAN.

NEXUS(config)# vsan database

NEXUS(config-vsan-db)# vsan 2 interface vfc 1

----End




48

5.3.5 Creating a Zone and Adding the Port to It

To create a zone and add a port to it on a CISCO Nexus5548, do as follows:

Step 1 Check the WWN of the FCoE device connected to the CISCO Nexus5548 switch:

switch# show flogi database

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

INTERFACE VSAN FCID PORT NAME NODE NAME

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

vfc1 100 0x2b0002 21:00:00:0e:1e:0a:6b:ab 20:00:00:0e:1e:0a:6b:ab

vfc4 100 0x2b0008 21:00:00:c0:dd:13:e2:a1 20:00:00:c0:dd:13:e2:a1

[lzh1]

vfc5 100 0x2b0007 20:00:00:07:43:ab:ce:07 10:00:00:07:43:ab:ce:07

vfc6 100 0x2b0009 21:00:00:c0:dd:13:e2:a3 20:00:00:c0:dd:13:e2:a3

[lzh2]

Total number of flogi = 4.

Step 2 On the switch, register a device name for the FCoE device. Then, either the device name or

the WWN can be used during later operations such as zone division.

switch(config)# device-alias database

switch(config-device-alias-db)# device-alias name test1 pwwn 20:00:00:0e:1e:0a:6b:ab

switch(config-device-alias-db)# device-alias name test2 pwwn 10:00:00:07:43:ab:ce:07

switch(config-device-alias-db)# device-alias commit

switch(config-device-alias-db)# show device-alias database

device-alias name lzh1 pwwn 21:00:00:c0:dd:13:e2:a1

device-alias name lzh2 pwwn 21:00:00:c0:dd:13:e2:a3

device-alias name lzh3 pwwn 20:00:00:07:43:ab:cd:ef

device-alias name lzh4 pwwn 20:00:00:07:43:ab:cd:f7

device-alias name test1 pwwn 20:00:00:0e:1e:0a:6b:ab

device-alias name test2 pwwn 10:00:00:07:43:ab:ce:07

Step 3 Add the device name to the zone.

switch# show zone

zone name zonexzh vsan 100

pwwn 21:00:00:0e:1e:0a:6b:ab

pwwn 00:00:00:07:43:ab:cd:f7

pwwn 20:00:00:07:43:ab:ce:07

zone name zonexzh02 vsan 100

pwwn 21:00:00:0e:1e:0a:6b:af

zone name zonexz vsan 100

pwwn 21:00:00:c0:dd:12:06:03

pwwn 20:00:00:07:43:ab:cd:ff

zone name lzhzone1 vsan 100

pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]

pwwn 20:00:00:07:43:ab:cd:ef [lzh3]


pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]

pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]




49


switch(config)# zone name lzhzone3 vsan 100

switch(config-zone)# member device-alias test1

switch(config-zone)# member device-alias test2

switch(config-zone)# show zone


pwwn 21:00:00:0e:1e:0a:6b:ab

pwwn 00:00:00:07:43:ab:cd:f7

pwwn 20:00:00:07:43:ab:ce:07


pwwn 21:00:00:0e:1e:0a:6b:af


pwwn 21:00:00:c0:dd:12:06:03

pwwn 20:00:00:07:43:ab:cd:ff


pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]

pwwn 20:00:00:07:43:ab:cd:ef [lzh3]


pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]

pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]


pwwn 20:00:00:0e:1e:0a:6b:ab [test1]

pwwn 10:00:00:07:43:ab:ce:07 [test2]

----End

5.3.6 Creating a Zoneset and Adding the Created Zone to It

To create a zoneset and add a zone to it, do as follows:

Step 1 Create a zoneset in the VSAN.

switch(config)# zoneset name lzhzoneset5 vsan 100

switch(config-zoneset)# show zoneset

zoneset name zoneset100 vsan 100


pwwn 21:00:00:0e:1e:0a:6b:ab

pwwn 00:00:00:07:43:ab:cd:f7

pwwn 20:00:00:07:43:ab:ce:07


pwwn 21:00:00:0e:1e:0a:6b:af


pwwn 21:00:00:c0:dd:12:06:03

pwwn 20:00:00:07:43:ab:cd:ff


pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]

pwwn 20:00:00:07:43:ab:cd:ef [lzh3]




50


pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]

pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]

zoneset name lzhzoneset5 vsan 100

Step 2 Add the zone to the created zoneset.

switch(config-zoneset)# member lzhzone3

switch(config-zoneset)# show zoneset

zoneset name zoneset100 vsan 100


pwwn 21:00:00:0e:1e:0a:6b:ab

pwwn 00:00:00:07:43:ab:cd:f7

pwwn 20:00:00:07:43:ab:ce:07


pwwn 21:00:00:0e:1e:0a:6b:af


pwwn 21:00:00:c0:dd:12:06:03

pwwn 20:00:00:07:43:ab:cd:ff


pwwn 21:00:00:c0:dd:13:e2:a1 [lzh1]

pwwn 20:00:00:07:43:ab:cd:ef [lzh3]


pwwn 21:00:00:c0:dd:13:e2:a3 [lzh2]

pwwn 20:00:00:07:43:ab:cd:f7 [lzh4]

zoneset name lzhzoneset5 vsan 100


pwwn 20:00:00:0e:1e:0a:6b:ab [test1]

pwwn 10:00:00:07:43:ab:ce:07 [test2]\

Step 3 Activate the zoneset.

switch (config)# zoneset activate name zoneset_1 vsan 2

zoneset activation initiated. check zone status

WARNING

Generally, for an FCoE switch, only one zoneset can be activated. Therefore, it is advisable to

keep all the zones in a same zoneset, preventing impacts on other services.

HUAWEI SAN Storage Host Connectivity Guide for Windows 6 Establishing Fibre Channel Connections



51

6 Establishing Fibre Channel Connections

After the physical connections are set up between a Windows host and a storage system and

zone division on the switch is completed, the FC connections between the Windows and the

storage system will be automatically available. You can verify whether the FC connections are

available by checking whether the host initiator status is online.

6.1 Checking Topology Modes

There are three topology modes available to Fibre Channel networks: point-to-point,

arbitrated loop, and switches fabric. Table 6-1 compares the three topology modes.

Table 6-1 Comparison among the three topology modes

Property Point-to-Point Arbitrated Loop Switched Fabric

Number of ports 2 2 to 127 Up to 224

Max. bandwidth Link rate x 2 Link rate x 2 Link rate x Number

of ports

Bandwidth

allocation rule

Dedicated Shared by ports in a

loop

Allocated by

switches

Address allocation

mechanism

N_Port Login Loop initialization or

Fabric Login

Fabric Login

Number of

concurrent

channels

1 1 Number of ports/2

Impact of port

failures

Link failure Loop failure (when

port bypass is

unavailable)

Links fail between

the failed port and

switches

Scalability Extra

point-to-point links

Public loop Expansion switch

High reliability Redundant ports

and point-to-point

links

Dual-loop and

dual-port

Redundancy switch




52

Property Point-to-Point Arbitrated Loop Switched Fabric

Link rate All All (The link rates to

devices on a loop must

be the same.)

All (support for

mixing rate)

Media type All All All

Service category All Categories 1, 2, 3 All

Frame transfer

order

Organized Organized Unorganized

Congestion No Yes No

On a directly connected network, the topology mode of the storage system must be the same

as that of HBAs.

To learn about port adaption of storage systems, refer to the related version mappings.

The method for checking topology modes varies with storage systems. The following

describes how to check the topology mode of the OceanStor T series storage system and the

OceanStor 18000 series enterprise storage system.

6.1.2 OceanStor T V1 Series Storage System

The check method is as follows:

In the ISM navigation tree, choose Device Info > Storage Unit > Ports. In the function pane,

click FC Host Ports. Select a port connected to the host and then view the port details, as


Figure 6-1 Fibre Channel port details

As shown in the preceding figure, the topology mode of the OceanStor T series storage

system is Public Loop.




53

6.1.3 OceanStor 18000/T V2 /V3 (V300R001) Series Enterprise Storage System

For the OceanStor 18000/T V2/V3 (V300R001), the check method is as follows:

In the ISM navigation tree, choose System. Then click the device view icon in the upper right

corner. Choose Controller Enclosure ENG0 > Controller > Interface Module > FC Port

and click the port whose details that you want to view, as shown in Figure 6-2.

In the navigation tree, you can see controller A and controller B, each of which has different interface

modules. Choose a controller and an interface module based on actual conditions.


As shown in the preceding figure, the port working mode of the OceanStor 18000 series

enterprise storage system is P2P.

6.1.4 OceanStor V3 (V300R002 and Later)/Dorado V3 Series Enterprise Storage System

For the OceanStor V3 (V300R002 and later)/Dorado V3, the check method is as follows:

In the DeviceManager navigation tree, choose System. Then click the device view icon in the

upper right corner. Choose Controller Enclosure > Controller > Interface Module > FC

Port and click the port whose details that you want to view, as shown in Figure 6-2.




54


As shown in the preceding figure, the port working mode of the storage system is P2P.

6.2 Adding Initiators

This section describes how to add host HBA initiators on a storage system. Perform the

following steps to add initiators:

Step 1 Check HBA WWNs on the host.

Step 2 Check host WWNs on the storage system and add the identified WWNs to the host.

The method for checking host WWNs varies with storage systems. The following describes

how to check WWNs on the OceanStor T series storage system and the OceanStor 18000

storage system.

OceanStor T Series Storage System

Log in to the ISM and choose SAN Services > Mappings > Initiators in the navigation

tree. In the function pane, check the initiator information. Ensure that the WWNs in step

1 are identified. If the WWNs are not identified, check the Fibre Channel port status.

Ensure that the port status is normal.

OceanStor 18000/T V2/V3 (V300R001) Series Enterprise Storage System

Log in to the ISM and choose Host in the navigation tree. On the Host tab page that is

displayed, select a host, click Add Initiator, and check that the WWNs in step 1 are found.

If the WWNs are not identified, check the Fibre Channel port status. Ensure that the port

status is normal.

OceanStor V3 (V300R002 and Later) Series Enterprise Storage System

Log in to the storage management system DeviceManager. In the DeviceManager

navigation tree, choose Resource Allocation > Host. Select the target host in the host

list and click Add Initiator. In the displayed Add Initiator page, set Initiator Type to

FC. In the displayed FC initiator list, search for and select the initiator corresponding to

the Windows system WWN. Click to add the host and click OK.

----End

6.3 Establishing Connections

Add the WWNs (initiators) to the host and ensure that the initiator connection status is

Online.




55

If the initiator status is Online, Fibre Channel connections are established correctly.

If the initiator status is Offline, check the physical links and topology mode.

HUAWEI SAN Storage Host Connectivity Guide for Windows 7 Establishing iSCSI Connections



56

7 Establishing iSCSI Connections

IP addresses and iSCSI services need to be configured before you establish iSCSI connections.

The procedure for establishing iSCSI connections is as follows:

1. Confirm that required software packages are installed on the host.

2. Configure service IP addresses on the host and the storage system.

3. Configure iSCSI initiators on the host.

4. Check the iSCSI targets of the storage system.

5. Configure the iSCSI service on the host.

6. Check initiators on the storage system and establish connection.

7.2 Checking Windows iSCSI Initiator Software

Windows Server 2008 and later has built-in iSCSI Initiator software. If your operating system

version is earlier than Windows Server 2008, download the iSCSI Initiator installation

package, as shown in Figure 7-1.




57

Figure 7-1 iSCSI Initiator page

You are advised to install Windows iSCSI Initiator 2.08 or later.

7.3 Configuring Storage Service IP Addresses

Storage systems and hosts use IP addresses to identify each other in iSCSI services. Therefore,

service IP addresses must be configured for storage systems and hosts.

Different versions of storage systems support different IP protocols. Specify the IP protocols

for storage systems based on actual storage system versions and application scenarios.

Observe the following principles when configuring IP addresses of iSCSI ports on storage

systems:

The IP addresses of an iSCSI host port and a management network port must reside on

different network segments.

The IP addresses of an iSCSI host port and a heartbeat network port must reside on

different network segments.

The IP addresses of the iSCSI host ports on the same controller cannot be in the same

network segment.




58

CAUTION

Read-only users are not allowed to modify the IP address of an iSCSI host port.

Modifying the IP address of an iSCSI host port will interrupt the services on the port.

The IP address configuration varies with storage systems. The following explains how to

configure IPv4 addresses on the OceanStor T series storage system and the OceanStor 18000

series enterprise storage system.

7.3.1 OceanStor T Series Storage System

Perform the following steps:

Step 1 In the ISM navigation tree, choose Device Info > Storage Unit > Ports. In the function pane,

click iSCSI Host Ports.

Select a port and choose IP Address > Modify IPv4 Address in the tool bar, as shown in

Figure 7-2.

Figure 7-2 Modifying IPv4 addresses

Step 2 In the ISM navigation tree, choose Device Info > Storage Unit > Ports. In the function pane,

click iSCSI Host Ports.

In the dialog box that is displayed, enter the new IP address and subnet mask and click OK.

----End

7.3.2 OceanStor 18000/T V2/V3 (V300R001) Series Enterprise Storage System


Step 1 Go to the iSCSI Host Port dialog box.

Then perform the following steps:

1. On the right navigation bar, click .

2. In the basic information area of the function pane, click the device icon.




59

3. In the middle function pane, click the cabinet whose iSCSI ports you want to view.

4. Click the controller enclosure where the desired iSCSI host ports reside. The controller

enclosure view is displayed.

5. Click to switch to the rear view.

6. Click the iSCSI host port whose information you want to modify.

7. The iSCSI Host Port dialog box is displayed.

8. Click Modify.

Step 2 Modify the iSCSI host port.

1. In IPv4 Address or IPv6 Address, enter the IP address of the iSCSI host port.

2. In Subnet Mask or Prefix, enter the subnet mask or prefix of the iSCSI host port.

3. In MTU (Byte), enter the maximum size of data packet that can be transferred between

the iSCSI host port and the host. The value is an integer ranging from 1500 to 9216.

Step 3 Confirm the iSCSI host port modification.

1. Click Apply. The Danger dialog box is displayed.

2. Carefully read the contents of the dialog box. Then click the check box next to the

statement I have read the previous information and understood subsequences of the

operation to confirm the information.

3. Click OK. The Success dialog box is displayed, indicating that the operation succeeded.

4. Click OK.

----End


Perform the following steps (with the OceanStor V3's SmartIO port as an example):

Step 1 Go to the iSCSI Host Port dialog box.


1. On the DeviceManager navigation tree, select System.

2. In the left working area, choose Controller Enclosure > Controller > Interface

Module > Ports.

3. Click the controller enclosure where the desired iSCSI host ports reside.

The controller enclosure view is displayed.

4. Select the desired iSCSI host port. In the displayed FCoE Port window, select the

Ethernet Port tab.

5. Click Modify.




60

Figure 7-3 Port configuration

Step 2 Modify the iSCSI host port.

1. In IPv4 Address or IPv6 Address, enter the IP address of the iSCSI host port.

2. In Subnet Mask or Prefix, enter the subnet mask or prefix of the iSCSI host port.

3. In MTU (Byte), enter the maximum size of data packet that can be transferred between

the iSCSI host port and the host. The value is an integer ranging from 1280 to 9216.

Figure 7-4 Ethernet port configuration

Step 3 Confirm the iSCSI host port modification.

1. Click Apply. The Danger dialog box is displayed.

2. Carefully read the contents of the dialog box. Then click the check box next to the

statement I have read the previous information and understood subsequences of the

operation to confirm the information.

3. Click OK. The Success dialog box is displayed, indicating that the operation succeeded.

4. Click OK.

----End




61

7.4 Host

7.4.1 Configuring IP Addresses on a Host

The network interface configuration steps differ with the OS version. The following shows

how to set IP addresses for the host system (with Windows Server 2003 and 2008 as

examples).

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 the

IPv4 address, as shown in Figure 7-5.

Figure 7-5 Modifying IPv4 addresses

Select Use the following IP address and configure the following parameters:

IP address

Subnet mask

Default gateway

----End

For Windows Server 2012/2016, you can set the host IP address as follows:

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, set the IPv4 address.




62

Figure 7-6 IP address modification page

Select the Use the following IP address option and set parameters:

IP address

Subnet mask

Default gateway

----End

7.4.2 Configuring Initiators on a Host

Perform the following steps to configure initiators on a host:

Step 1 Ensure that the network connectivity is normal between the host and the storage system.

Ping each other's IP address on the host and storage system respectively.

Step 2 Enter a name for the initiator.

On the iSCSI Initiator Properties page, click the Configuration tab and enter the initiator

name, as shown in Figure 7-7.




63

Figure 7-7 Entering the initiator name

In this example, the initiator name is iqn.1991-05.com.microsoft:win-bs.1s108mrc2.

An iSCSI initiator name must comply with the following format:

iqn.domaindate.reverse.domain.name:optional name

An iSCSI initiator name contains only:

Special characters: hyphens (-), periods (.), and semicolons (:)

Lower-case letters, for example, a to z

Digits, for example, 0 to 9

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 7-8.




64

Figure 7-8 Configuring the target IP address

Keep the default iSCSI port 3260 unchanged.

Step 4 Set up connections.

On the Target tab page, select the newly discovered target and click Connect. Check whether

the connection status of the target is connected. If yes, the connections are correctly set up

between the host and the storage system.

----End

7.4.3 Establishing Connections

After completing configurations on the host, discover initiators on the storage system. The

methods of adding initiators and LUNs are the same as those in establishing Fibre Channel

connections. For details, see section 6.3 "Establishing Connections."

7.5 Configuring CHAP Authentication

CHAP authentication is configured to protect iSCSI link security. After CHAP authentication

is configured, a host can connect a discovered target only after correct user name and

password are provided.




65

The following describes how to configure CHAP authentication on a host and storage system

respectively.

7.5.1 Storage System

The method for configuring CHAP authentication varies with storage systems. The following

describes how to configure CHAP authentication on the OceanStor T series storage systems

and the OceanStor 18000 series enterprise storage systems.

7.5.1.1 OceanStor T V1 Series Storage System


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 7-9.

Figure 7-9 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 7-10.




66

Figure 7-10 CHAP Configuration dialog box

In the Create CHAP dialog box that is displayed, enter the CHAP user name and password,

as shown in Figure 7-11.

Figure 7-11 Create CHAP dialog box

CAUTION

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 7-12.




67

Figure 7-12 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 7-13.

Figure 7-13 Setting CHAP status




68

Step 5 In the Status Settings dialog box that is displayed, choose Enabled from the CHAP Status

drop-down list, as shown in Figure 7-14.

Figure 7-14 Enabling CHAP

On the ISM, view the initiator status, as shown in Figure 7-15.

Figure 7-15 Initiator status after CHAP is enabled

----End

7.5.1.2 OceanStor 18000/T V2/V3 (V300R001) Series Enterprise 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.




69

Figure 7-16 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 7-17 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 7-18 Initiator configuration page




70

CHAP authentication is configured on the storage system.

----End

7.5.1.3 OceanStor V3 (V300R002 and Later)/Dorado V3 Series Enterprise Storage System

The iSCSI CHAP authentication methods are similar for OceanStor V3 (V300R002 and later).

The following uses OceanStor V3 (V300R002) as an example to describe CHAP

authentication configuration steps.

Step 1 On DeviceManager, click Provisioning on the right navigation tree. Then, click Host in the

displayed page.

Figure 7-19 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 7-20 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.




71

Figure 7-21 Initiator configuration page

CHAP authentication is configured on the storage system.

----End

7.5.2 Host

7.5.2.1 Configuring CHAP Information

Go to the Target tab page, select the desired target, and click Connect. On the dialog box that

is displayed, click Advanced. In the dialog box that is displayed, enter the user name and

password configured on the storage system, as shown in Figure 7-22.




72

Figure 7-22 Connecting to the target on a host through CHAP authentication

7.5.2.2 Updating Favorite Target Information

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.


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

HUAWEI SAN Storage Host Connectivity Guide for Windows 8 Mapping and Using LUNs



73

8 Mapping and Using LUNs

8.1 LUN mapping

After a storage system is connected to a Windows host, map the storage system LUNs to the

host.

Two methods are available for mapping LUNs:

Mapping LUNs to a host: This method is applicable to scenarios where only one

small-scale client is deployed.

Mapping LUNs to a host group: This method is applicable to cluster environments or

scenarios where multiple clients are deployed.

The method for mapping LUNs varies with storage systems. The following describes how to

map LUNs of the OceanStor T series storage system and the OceanStor 18000 series

enterprise storage system.

8.1.1 OceanStor T Series Storage System

8.1.1.1 Prerequisites

RAID groups have been created on the storage system. LUNs have been created on the RAID

groups.

8.1.1.2 Procedure

This document explains how to map LUNs to a host. Perform the following steps to map

LUNs to a host:

Step 1 In the ISM navigation tree, choose SAN Services > Mappings >Hosts.

Step 2 In the function pane, select the desired host. In the navigation bar, choose Mapping > Add

LUN Mapping. The Add LUN Mapping dialog box is displayed.

Step 3 Select LUNs that you want to map to the host and click OK.

----End




74

CAUTION

When mapping LUNs on a storage system to a host, ensure that the host LUN whose ID is 0

is mapped.

8.1.2 OceanStor 18000/T V2/V3 (V300R001) Series Enterprise Storage System


LUNs, LUN groups, hosts, and host groups have been created on the storage system.

8.1.2.2 Procedure


LUNs to a host:

Step 1 Go to the Create Mapping View dialog box.


1. On the right navigation bar, click .

2. On the host management page, click Mapping View.

3. Click Create. The Create Mapping View dialog box is displayed.

Step 2 Set basic properties for the mapping view.

1. In the Name text box, enter a name for the mapping view.

2. (Optional) In the Description text box, describe the mapping view.

Step 3 Add a LUN group to the mapping view.

1. Click . The Select LUN Group dialog box is displayed.

If your service requires a new LUN group, click Create to create one.

You can select Shows only the LUN groups that do not belong to any mapping view to quickly locate

LUN groups.

2. From the LUN group list, select the LUN groups you want to add to the mapping view.

3. Click OK.

Step 4 Add a host group to the mapping view.

1. Click .

If your service requires a new host group, click Create to create one.

2. The Select Host Group dialog box is displayed.

3. From the host group list, select the host group you want to add to the mapping view.




75

4. Click OK.

Step 5 (Optional) Add a port group to the mapping view.

1. Select Port Group.

2. Click .

3. The Select Port Group dialog box is displayed.

If your service requires a new port group, click Create to create one.

4. From the port group list, select the port group you want to add to the mapping view.

5. Click OK.

Step 6 Confirm the creation of the mapping view.

1. Click OK. The Execution Result dialog box is displayed, indicating that the operation

succeeded.

2. Click Close.

----End



LUNs, LUN groups, hosts, and host groups have been created on the storage system.

8.1.3.2 Procedure


LUNs to a host:

Step 1 Go to the Create Mapping View dialog box.


1. On the right navigation bar, click Provisioning.

2. On the host management page, click Mapping View.

3. Click Create. The Create Mapping View dialog box is displayed.

Step 2 Set basic properties for the mapping view.

1. In the Name text box, enter a name for the mapping view.

2. (Optional) In the Description text box, describe the mapping view.

Step 3 Add a LUN group to the mapping view.

1. Click . The Select LUN Group dialog box is displayed.

If your service requires a new LUN group, click Create to create one.

You can select Shows only the LUN groups that do not belong to any mapping view to quickly locate

LUN groups.

2. From the LUN group list, select the LUN groups you want to add to the mapping view.




76

3. Click OK.

Step 4 Add a host group to the mapping view.

1. Click .

If your service requires a new host group, click Create to create one.

2. The Select Host Group dialog box is displayed.

3. From the host group list, select the host group you want to add to the mapping view.

4. Click OK.

Step 5 (Optional) Add a port group to the mapping view.

1. Select Port Group.

2. Click .

3. The Select Port Group dialog box is displayed.

If your service requires a new port group, click Create to create one. Only ports in the port group can be

used for the host system to access the mapped storage.

4. From the port group list, select the port group you want to add to the mapping view.

5. Click OK.

Step 6 Confirm the creation of the mapping view.

1. Click OK. The Execution Result dialog box is displayed, indicating that the operation

succeeded.

2. Click Close.

----End

8.2 Using the Mapped LUNs

After the mapped LUNs are detected on a host, you can use the LUNs after scanning for them.

For details about how to scan for LUNs, see section 1.4.3 "Disk Management Commands."

If you want to create file systems, use the Windows volume management tool. Creating file

system is simple and therefore not detailed here.

If the host and the storage system are connected over a multi-path network, see chapter 9

"Multipathing Management" to configure the multipathing function.

HUAWEI SAN Storage Host Connectivity Guide for Windows 9 Multipathing Management



77

9 Multipathing Management

9.1 Overview

Windows supports two pieces of multipathing software: UltraPath and Windows Microsoft

Multi-Path IO (MPIO).

UltraPath is a Huawei's self-developed software product. For details, see the UltraPath

product documentation.

MPIO is a framework provided by Microsoft. It allows storage vendors to develop

multipathing solutions that contain the hardware-specific information needed to optimize

connectivity with the storage systems. MPIO can be used independently. This software helps

balance load among multiple paths and implement path selection and failover between storage

systems and hosts.

The chapter details the functions and configuration of MPIO.

9.2 MPIO Policies

MPIO supports six policies: Fail Over Only, Round Robin, Round Robin with Subset

(RRWS), Least Queue Depth, Weighed Paths, and Least Blocks. The following details each

policy.

Fail Over 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/O. 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.

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.




78

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 paths among A, B, and C.

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 2. 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.

Weighed Paths

This load balancing policy assigns a weight to each path. The weight indicates the relative

priority of a given path. The large the number, the lower ranked the priority. The DSM

chooses the least-weighted path from among the available paths.

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 both have completed 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.

9.3 Installation and Configuration

9.3.1 Precautions

Registry keys related to MPIO may be changed after other software is installed on the host.

Before using MPIO, make sure that all MPIO-related registry keys are not changed. Pay

special attention to PathVerifyEnabled. You are advised to configure parameters as shown in

Figure 9-1.




79

Figure 9-1 Configuring MPIO parameters in the registry

To configure the parameter, run CMD command regedit to start Registry Editor, and choose

HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > mpio >

Parameters.

CAUTION

The MPIO-related registry keys are changed after software that interworks with MPIO is

installed. In this case, you need to confirm and restore those registry keys to defaults when

using MPIO to manage the mapped LUNs.

9.3.2 Procedure

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 2008 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

2008 R2 and therefore will not be detailed. For more details, see the Microsoft official

documentations

Step 1 Add Multipath I/O.

Start Serer Manager, choose Feature, and select Multipath I/O, as shown in Figure 9-2.




80

Figure 9-2 Adding Multipath I/O

Step 2 Query device VID and PID.

VID: indicates the vendor ID, for example, HUAWEI.

PID: indicates the product ID, for example, S5500T, S5600T, or XSG.

In Device Management, right-click the SCSI device that you want to add and choose

Properties from the shortcut menu. In the dialog box that is displayed, choose Hardware Ids

from the Property drop-down list to view VID and PID, as shown in Figure 9-3.

Figure 9-3 Viewing VID and PID

As shown in the preceding figure, VID is HUASY and PID is S5600T.




81

If MPIO is installed on Windows 2008 or later versions, you can use multipathing command

mpclaim to query disk information, as shown in Figure 9-4.

Figure 9-4 Querying disk information

As shown in the preceding figure, VID is HUAWEI and PID is S2600.

CAUTION

The PID and VID in this section are examples only. PID and VID are subject to actual

conditions.

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 on the CMD command window to take over the storage.

In this example, a command is run on the CMD window:

On the Windows server, open the CMD command line window and run the mpclaim -r -i -d

"HUAWEI XSG1" command, as shown in Figure 9-5.

Figure 9-5 Taking over Huawei storage

The VID must contain eight characters and the PID must contain 12 characters. If characters are

insufficient, add spaces. You can copy the command from the output of the mpclaim -e command.

WARNING

After the mpclaim -r -i -d "HUAWEI XSG1" command is executed, the host automatically

restarts.

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

9-6.




82

Figure 9-6 MPIO policy management page

Normally, the default MPIO policy is preferred.

The default policy varies with operating system configurations. Table 9-1 lists the default

policies for commonly used operating systems.

Table 9-1 Default MPIO policy

Operating System Storage System

Default MPIO Policy Remarks

Windows Server 2008 ALUA enabled Round Robin With

Subset

ALUA disabled Fail over only

Windows Server 2008 R2 ALUA enabled Round Robin With

Subset

ALUA disabled Round Robin


Subset


Windows Server 2012 DC ALUA enabled Round Robin With

Subset



Subset


For Windows in non-HyperMetro networking, it is advisable to use the default MPIO policy.

Step 5 Reset a path state.

You need to reset a path state for special scenarios or requirements.




83

For example, if the policy is set to Fail Over Only, only one activate path is allowed. You need

to change the state of other paths to standby.

In Windows 2008, set the state of the path connected to the owning controller to

Active/Optimized and set the state of paths connected to other controllers to

Active/Unoptimized.

Figure 9-7 shows the path details configuration page.

Figure 9-7 Path details configuration page

Windows MPIO allows each LUN to have a maximum of 32 paths. If a LUN has more than 32 paths, the

Windows host may display a blue screen. Therefore, when using Windows MPIO to arrange LUN paths,

ensure that each LUN has fewer than 32 paths.

If a storage system does not support ALUA, configure the MPIO policy to the one applicable to storage

systems with ALUA disabled.

Step 6 Save the path state configuration.

States of paths to disks are not updated on the MPIO policy configuration page immediately

after being changed. You need to click OK to save path state changes on the MPIO policy

configuration page and open the page again to check the path states.

----End

9.4 Common Management Commands

You can use the following CMD commands to manage MPIO. Table 9-2 lists the commands.




84

Table 9-2 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 devices.

mpclaim.exe -r -i -d <_VendorID> <_ProductID>

Disables MPIO from

managing Fibre Channel

devices.

mpclaim.exe -r -u -d <_VendorID> <_ProductID>

Uses MPIO to manage iSCSI

devices.

mpclaim -r -i -d "MSFT2005iSCSIBusType_0x9"

Disables MPIO from

managing iSCSI devices.

mpclaim.exe -r -u -d "MSFT2005iSCSIBusType_0x9"

Uses MPIO to manage all

storage devices.

mpclaim.exe -r -i -a ""

Disables MPIO from

managing all storage devices.

mpclaim.exe -r -u -a ""

Views storage devices

managed by Microsoft DSM.

mpclaim -r

Modifies the load balancing

policy.

mpclaim.exe –L –M <_num>

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 9-3.

Table 9-3 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




85

Parameter Definition

5 Weighted Paths

6 Least Blocks

7 Vendor Specific

9.5 Uninstallation

Third-party multipathing software can be installed correctly only after MPIO is uninstalled.

When installing third-party multipathing software, you are prompted to uninstall MPIO to

avoid software conflict.

Perform the following steps to uninstall MPIO:

Step 1 Clear all iSCSI devices managed by MPIO. On the MPIO Device tab page, click Remove to

delete storage devices, as shown in Figure 9-8.

Figure 9-8 Deleting iSCSI devices managed by MPIO

It is of great importance to delete devices managed by MPIO before you uninstall MPIO. If devices

managed by MPIO are not deleted, third-party multipathing software still cannot be installed correctly or

manage storage devices correctly after MPIO is uninstalled.

Step 2 In Server Management, choose Remove Features. On Remove Features Wizard that is

displayed, deselect Multipath I/O and click Next, as shown in Figure 9-9.




86

Figure 9-9 Deleting Multipath I/O

Step 3 Click Remove and restart the host for the uninstallation to take effect.

----End

HUAWEI SAN Storage Host Connectivity Guide for Windows 10 Windows MPIO Policy Configuration



87

10 Windows MPIO Policy Configuration

The MPIO policy differs with the OS version.

This chapter describes the MPIO policy configurations recommended when Windows hosts

and HUAWEI storage systems are interconnected.

HUAWEI storage firmwares' support for the OS-inherent multipathing HyperMetro solution

is as follows:

Old-version HUAWEI storage (namely, storage that does not support multi-controller ALUA or ALUA HyperMetro): OceanStor T V1/T V2/18000

V1/V300R001/V300R002/V300R003C00/V300R003C10/V300R005/Dorado V300R001C00

New-version HUAWEI storage (namely, storage that supports multi-controller ALUA

and ALUA HyperMetro): V300R003C20/V300R006C00 (only V300R006C00SPC100 and

later)/Dorado V300R001C01 (only V300R001C01SPC100 and later)

10.1.1 NMP Configuration for New-Version HUAWEI Storage

10.1.1.1 HyperMetro Working Modes

Typically, HyperMetro works in load balancing mode or local preferred mode. The

typical working modes are valid only when both the storage system and host use ALUA. It is

advised to set the host's path selection policy to round-robin. If HyperMetro works in load

balancing mode, the host's path selection policy must be round-robin. If the host does not use

ALUA or its path selection policy is not round-robin, the host's multipathing policy

determines the working mode of HyperMetro.

HyperMetro storage arrays can be classified into a local and a remote array by their distance

to the host. The one closer to the host is the local array and the other one is the remote array.

Table 10-1 describes the configuration methods and application scenarios of the

typical working modes.




88

Table 10-1 Configuration methods and application scenarios of the typical working modes

Working Mode

Configuration Method Application Scenario

Load balancing

mode

Enable ALUA on the host and set the path

selection policy to round-robin.

Configure a switchover mode that supports

ALUA for both HyperMetro storage arrays'

initiators that are added to the host.

Set the path type for both storage arrays'

initiators to the optimal path.

The distance between

both HyperMetro

storage arrays is less

than 1 km. For example,

they are in the same

equipment room or on

the same floor.

Local preferred

mode

Enable ALUA on the host. It is advised to set

the path selection policy to round-robin.

Configure a switchover mode that supports

ALUA for both HyperMetro storage arrays'

initiators that are added to the host.

Set the path type for the local storage array's

initiators to the optimal path and that for the

remote storage array's initiators to the

non-optimal path.

The distance between

both HyperMetro

storage arrays is greater

than 1 km. For example,

they are in different

locations or data centers.

Other modes Set the initiator switchover mode for the

HyperMetro storage arrays by following

instructions in the follow-up chapters in this

guide. The path type does not require manual

configuration.

User-defined

10.1.1.1.2 Working Principles and Failover

When ALUA works, the host multipathing software divides the physical paths to disks into

Active Optimized (AO) and Active Non-optimized (AN) paths. The host delivers services to

the storage system via the AO paths preferentially.

An AO path is the optimal I/O access path and is between the host and a working

controller.

An AN path is the suboptimal I/O access path and is between the host and a non-working

controller.

When HyperMetro works in load balancing mode, the host multipathing software selects the

paths to the working controllers on both HyperMetro storage arrays as the AO paths, and

those to the other controllers as the AN paths. The host accesses the storage arrays via the AO

paths. If an AO path fails, the host delivers I/Os to another AO path. If the working controller

of a storage array fails, the system switches the other controller to the working mode and

maintains load balancing.

Host

A B A B

AO AOAN AN

Host

A B A B

AO AOAO’AN

Site A Site B Site A Site B

Path failure SP failure




89

When HyperMetro works in local preferred mode, the host multipathing software selects the

paths to the working controller on the local storage array as the AO paths. This ensures that

the host delivers I/Os only to the working controller on the local storage array, reducing link

consumption. If all AO paths fail, the host delivers I/Os to the AN paths on the non-working

controller. If the working controller of the local storage array fails, the system switches the

other controller to the working mode and maintains the local preferred mode.

Host

A B A B

AO ANAN AN

Host

A B A B

AO ANAO’ AN

Site A Site B Site A Site B

Path failure SP failure

10.1.1.2 Introduction to ALUA

10.1.1.2.1 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.

10.1.1.2.2 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 10-2 describes the HUAWEI storage's support for ALUA.

Table 10-2 HUAWEI storage's support for ALUA

Storage Type Version Remarks

Old-version HUAWEI

storage (namely,

storage that does not

support multi-controller

ALUA or ALUA

HyperMetro)

T V1/T V2/18000

V1/V300R001/V300R002/V300R

003C00/V300R003C10/V300R00

5/Dorado V300R001C00

New-version HUAWEI

storage (namely,

storage that supports

multi-controller ALUA

and ALUA

HyperMetro)

V300R003C20/V300R006C00/D

orado V300R001C01

V300R006C00: refers to

only

V300R006C00SPC100 and

later versions.

Dorado V300R001C01: refers to only




90

V300R001C01SPC100 and

later versions.

10.1.1.2.3 ALUA Impacts

ALUA is mainly applicable to a storage system that has one (only one) preferred LUN

controller. All host I/Os can be routed through different controllers to the working controller

for execution. The storage 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.

Once the LUN working controller's all I/O paths are disconnected, the host I/Os will be

delivered only from a non-working controller and then routed to the working controller for

execution. This scenario must be avoided.

10.1.1.2.4 Suggestions for Using ALUA on HUAWEI Storage

To prevent IOs from being delivered to a non-working controller, you are advised to:

Ensure that the LUN home/working controllers are evenly distributed on storage

systems.

A change to the storage system (node fault or replacement) may cause an I/O path

switchover. Ensure that the host always tries the best to select the optimal path to deliver

I/Os.

Prevent all host service I/Os from being delivered only to one controller, thereby

preventing load unbalancing on the storage system.

10.1.2 Initiator Mode and Configuration

10.1.2.1.1 Initiator Parameter Description

Table 10-3 Initiator parameter description

Parameter Description Example

Uses

third-party

multipath

software

This parameter is displayed only after an initiator

has been added to the host.

If LUNs have been mapped to the host before you

enable or disable this parameter, restart the host

after you configure this parameter.

You do not need to enable this parameter on a

host with UltraPath.

Enabled

Switchover

Mode

Path switchover mode

The system supports the following modes:

early-version ALUA: default value of

Switchover Mode for an upgrade from an

earlier version to the current version. The

detailed requirements are as follows:

− The storage system is upgraded from

V300R003C10 and earlier to

V300R003C20 or V300R006C00SPC100




91

and later; from V300R005 to

V300R006C00SPC100 and later;

from Dorado V300R001C00 to Dorado

V300R001C01SPC100 and later.

− Before the upgrade, the storage system has a

single or dual controllers and has enabled

ALUA.

common ALUA: applies to V300R003C20 and

later, V300R006C00SPC100 and later,

or Dorado V300R001C01SPC100 and later. The

detailed requirements are as follows:

− The storage system version is V300R003C20,

V300R006C00SPC100, Dorado

V300R001C01SPC100, or later.

− The OS of the host that connects to the storage

system is SUSE, Red Hat 6.X, Windows

Server 2012 (using Emulex HBAs),

Windows Server 2008 (using Emulex

HBAs), or HP-UX 11i V3.

ALUA not used: does not support ALUA or

HyperMetro. This mode is used when a host

such as HP-UX 11i V2 does not support ALUA

or ALUA is not needed.

Special mode: supports ALUA and has multiple

values. It applies to V300R003C20 and later,

V300R006C00SPC100 and later, or Dorado

V300R001C01SPC100 and later. It is used by

host operating systems that are not supported by

the common ALUA mode. The detailed

requirements are as follows:

− The storage system version V300R003C20,

V300R006C00SPC100, Dorado

V300R001C01SPC100, or later.


system is VMware, AIX, Red Hat 7.X,

Windows Server 2012 (using QLogic

HBAs), or Windows Server 2008 (using

QLogic HBAs).

Special mode

type

Special modes support ALUA and apply to

V300R003C20 and later, V300R006C00SPC100

and later, or Dorado V300R001C01SPC100 and

later. The detailed requirements are as follows:

Mode 0:

− The host and storage system must be

connected using a Fibre Channel network.


system is Red Hat 7.X, Windows Server

2012 (using QLogic HBAs), or Windows

Server 2008 (using QLogic HBAs).

Mode 1:

Mode 0




92


system is AIX or VMware.

− HyperMetro works in load balancing mode.

Mode 2:


system is AIX or VMware.

− HyperMetro works in local preferred mode.

Path Type The value can be either Optimal Path or

Non-Optimal Path.

When HyperMetro works in load balancing

mode, set the Path Type for the initiators of

both the local and remote storage arrays to

Optimal Path. Enable ALUA on both the host

and storage arrays. If the host uses the

round-robin multipathing policy, it delivers I/Os

to both storage arrays in round-robin mode.

When HyperMetro works in local preferred

mode, set the Path Type for the initiator of the

local storage array to Optimal Path, and that of

the remote storage array to Non-Optimal Path.

Enable ALUA on both the host and storage

arrays. The host delivers I/Os to the local

storage array preferentially.

Optimal Path

Configure the initiators according to the requirements of each OS. The initiators that are

added to the same host must be configured with the same switchover mode. Otherwise, host

services may be interrupted.

After the initiator mode is configured on a storage array, you must restart the host for the

configuration to take effect.

10.1.2.2 Configuring the Initiators

If you want to configure the initiator mode, perform the following operations.

Step 1 Go to the host configuration page.

Open OceanStor DeviceManager. In the right navigation tree, click Provisioning and then

click Host, as shown in Figure 10-1.




93

Figure 10-1 Going to the host configuration page

Step 2 Select an initiator of which information you want to modify.

On the Host tab page, select a host you want to modify. Then select the initiator (on the host)

you want to modify. Click Modify.

Figure 10-2 Selecting an initiator of which information you want to modify

Step 3 Modify the initiator information.

In the Modify Initiator dialog box that is displayed, modify the initiator information based on

the requirements of your operating system. Figure 10-3 shows the initiator information

modification page.




94

Figure 10-3 Modifying initiator information

Step 4 Repeat the preceding operations to modify the information about other initiators on the host.

Step 5 Configure host multipathing. For details, refer to section 10.1.4 "Host Configuration."

Step 6 Restart the host to enable the configuration to take effect.

----End

10.1.3 Storage Array Configuration

Different models of HUAWEI storage support different ALUA policies. For details, refer to

the specific HUAWEI storage model's product documentation. Unless otherwise specified, the

recommended configurations for HUAWEI storage that supports ALUA are detailed as

follows:

10.1.3.1 OceanStor T Series Storage System

Table 10-4 describes the recommended configurations for HUAWEI OceanStor T series

V1/V2.

WARNING

After the initiator mode is configured on a storage array, you must restart the host to enable

the new configuration to take effect.

Table 10-4 ALUA configuration for HUAWEI OceanStor T series

Operating System Storage System Remarks

OceanStor T V1 OceanStor T V2

Windows Server 2003 ALUA enabled ALUA enabled




95

Operating System Storage System Remarks

Windows Server 2003 R2 ALUA enabled ALUA enabled

Windows Server 2008 ALUA enabled ALUA enabled After ALUA is

enabled/disabled,

path preferential

selection fails on

Windows Server

2008 and

Windows Server

2008 SP2; in this

case, you need to

set path

preferential

selection

manually.

Windows Server 2008 R2 ALUA enabled ALUA enabled

Windows Server 2012 ALUA enabled ALUA enabled

10.1.3.2 OceanStor V3 Series Storage System (Non-HyperMetro Networking)

Table 10-5 describes the recommended configuration for HUAWEI OceanStor V3.

WARNING



Table 10-5 ALUA configuration for OceanStor V3

Operating System

Storage System Remarks

OceanStor V3 (V300R003C20 and Earlier)

OceanStor V3 (V300R003C20 and Later)

Windows Server

2003 ALUA disabled ALUA disabled

Windows Server

2003 R2

ALUA disabled ALUA disabled

Windows Server

2008

ALUA disabled ALUA disabled

Windows Server

2008 R2

ALUA disabled ALUA enabled (general mode)




96

Operating System

Storage System Remarks

Windows Server

2012


Windows Server

2012 R2


Windows Server

2016


10.1.3.3 OceanStor V3 Series Storage System in HyperMetro Networking and Windows MPIO Environment

In Windows MPIO environment, OceanStor V3 series only of version V300R003C20 or later

supports HyperMetro. For the host system versions that support MPIO and HyperMetro, refer

to the HUAWEI storage interoperability list. For detailed system configurations, refer to the

HyperMetro Configuration Guide for Huawei SAN Storage with Multipathing Software

Provided by the Operating System.

The FC HBAs from different vendors have different performance in Windows and Hyper-V

N_Port_ID virtualization (NPIV) environment. Therefore, you need to configure a specific

Windows host FC initiator mode on OceanStor V3.

WARNING



10.1.3.3.1 Non-NPIV Mode

In non-NPIV mode (for both common Windows hosts and NPIV-disabled Hyper-V hosts), the

storage system connects to physical Windows hosts and the storage space on the storage

system is directly mapped to the hosts. Operations such as multipathing management over the

mapped storage space are performed on the physical hosts. Table 10-6 lists the storage array

configuration when Emulex HBAs are used in non-NPIV mode.

Table 10-6 Configuration on storage arrays when Emulex HBAs are used in non-NPIV mode

OS Storage Array Configuration

HyperMetro

Working

Mode

Storage OS Third-Party

Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Windows

Server 2008 R2

SP1

Load

balancing

Local

storage

array

Windows Enabled Common

ALUA

Optimal

path

Remote

storage

array


ALUA

Optimal

path




97


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Local

preferred

Local

storage

array


ALUA

Optimal

path

Remote

storage

array


ALUA

Non-optimal

path

Windows

Server 2012

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enable Common

ALUA

Non-optimal

path

Windows

Server 2012 R2

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

Windows

Server 2016

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path




98


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

For details about the Windows versions, see the compatibility list:

http://support-open.huawei.com/ready/pages/user/compatibility/support-matrix.jsf



Table 10-7 lists the storage array configuration when QLogic HBAs are used in non-NPIV

mode.

Table 10-7 Configuration on storage arrays when QLogic HBAs are used in non-NPIV mode


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Windows

Server 2008 R2

SP1

Load

balancing

Local

storage

array


ALUA

Optimal

path

Remote

storage

array


ALUA

Optimal

path

Local

preferred

Local

storage

array


ALUA

Optimal

path

Remote

storage

array


ALUA

Non-optimal

path

Windows

Server 2012

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Special mode Mode 0 Optimal

path

Remote

storage

array

Windows

Server

2012


path





99


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Local

preferred

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012

Enabled Special mode Mode 0 Non-optimal

path

Windows

Server 2012 R2

Load

balancing

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Local

preferred

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Windows

Server 2016

(non-cluster

scenario)

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

Windows

Server 2016

(cluster

scenario)

Load

balancing

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Local

preferred

Local

storage

array

Windows

Server

2012


path




100


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Remote

storage

array

Windows

Server

2012


path





10.1.3.3.2 NPIV Mode

In Windows Hyper-V NPIV environment, Hyper-V hosts create Virtual FC HBAs for VMs.

VMs set up connections to the storage system through virtual FC HBAs. The storage system's

storage space is directly mapped to VMs, not to bottom-layer Hyper-V physical hosts. SAN

storage disk and multipathing managements by VMs are transparent and not sensed by

Hyper-V physical hosts.

Currently, the operating systems that support Windows Hyper-V (NPIV) are limited. For

details, see the official explanation of Microsoft.

https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-feature-compati

bility-by-generation-and-guest

Table 10-8 lists the storage array configuration when Emulex HBAs are used in NPIV mode.

Table 10-8 Configuration on storage arrays when Emulex HBAs are used in NPIV mode


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Windows

Server 2012 R2

With Hyper-V1

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path


https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-feature-compatibility-by-generation-and-guest

https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-feature-compatibility-by-generation-and-guest




101


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

Windows

Server 2012

With Hyper-V2

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

Windows

Server 2016

With Hyper-V3

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

The operating system of VMs with Windows Server 2016 with Hyper-V can be Windows Server

2012, Windows Server 2012 R2, or Windows Server 2016. Patches must be installed in Windows

Server 2012 R2.


2012.



Server 2012 R2.




102





Table 10-9 lists the storage array configuration when QLogic HBAs are used in NPIV mode.

Table 10-9 Configuration on storage arrays when QLogic HBAs are used in NPIV mode


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Windows

Server 2012 R2

With Hyper-V1

Load

balancing

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Local

preferred

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Windows

Server 2012

With Hyper-V2

Load

balancing

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Local

preferred

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path





103


HyperMetro

Working

Mode


Multipathing

Software

Switchover

Mode

Special

Mode

Type

Path Type

Windows

Server 2016

With Hyper-V

(non-cluster

scenario)3

Load

balancing

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Local

preferred

Local

storage

array

Windows

Server

2012

Enabled Common

ALUA

Optimal

path

Remote

storage

array

Windows

Server

2012

Enabled Common

ALUA

Non-optimal

path

Windows

Server 2016

With Hyper-V

(cluster

scenario)3

Load

balancing

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path

Local

preferred

Local

storage

array

Windows

Server

2012


path

Remote

storage

array

Windows

Server

2012


path



Server 2012 R2.


2012.



Server 2012 R2.







104



10.1.4 Host Configuration

In Windows MPIO environment, you can retain the default MPIO policy for non-HyperMetro

networking. For the default Windows Server MPIO policies, see Table 9-1.

In HyperMetro networking, you need to set the Windows Server MPIO policy to Round

Robin with Subset and enable the DSM multipathing verification function as follows:

Step 1 Identify the PID and VID of the storage array.

VID: vendor ID, such as HUAWEI

PID: product ID, such as XSG1

On the Windows server, open the CMD command line and run the mpclaim -e command to

check the LUNs identified by the multipathing software.

Figure 10-4 Viewing the storage product information

In the preceding figure, VID is HUAWEIand PID is XSG1. If the value of the

MPIO-edparameter is NO, the LUNs of the vendor are not taken over by MPIO.

Step 2 Take over the storage array.

On the Windows server, open the CMD command line and run the mpclaim -r -i -d

"HUAWEI XSG1" command, as shown in Figure 10-5.

Figure 10-5 Taking over Huawei storage

The VID must contain eight characters and the PID must contain 12 characters. If the number of

characters does not meet requirements, add spaces. You can directly copy the command from the output

of the mpclaim -e command.




105

WARNING

After the preceding command is executed, the host automatically restarts.

Step 3 Configure a multipathing policy.

After the host restarts, right-click the disk discovered by the server and choose Properties

form the shortcut menu, as shown in Figure 10-6.

Figure 10-6 Viewing disk properties

On the page HUAWEI XSG1 Multi-Path Disk Device Properties, click the MPIO tab. In

Select the MPIO policy, select Round Robin With Subset, as shown in Figure 10-7.




106

Figure 10-7 Configuring the MPIO policy

WARNING

Ensure that the properties of each LUN are modified.

Step 4 Activate the path verification function (for Hyper-Metro networking).

On the MPIO tab page, click Details. In the DSMDetails dialog box that is displayed, select

Path Verify Enabled, as shown in Figure 10-8.




107

Figure 10-8 Activating the path verification function

WARNING

Ensure that the properties of each LUN are modified.

Step 5 Restart the host.

After the host is restarted, check the parameters to ensure that all parameters have been

modified.

You can also run the following command to check whether the disk path information is

modified.




108

Figure 10-9 Checking disk multipathing policy

----End

HUAWEI SAN Storage Host Connectivity Guide for Windows 11 Volume Management



109

11 Volume Management

In Windows, disks are categorized as basic disks 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.

CAUTION

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:

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.

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.

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.

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:




110

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 11-1.

Figure 11-1 Rescanning for disks

Step 2 The states of the identified LUNs are Unknown and Offline. 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 11-2.

Figure 11-2 Setting the identified disks online




111

Step 3 Right-click a disk and choose Initialize Disks from the shortcut menu. In the Initialize Disks

dialog box 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 11-3.

Figure 11-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 11-4.

Figure 11-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.

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.




112

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

HUAWEI SAN Storage Host Connectivity Guide for Windows 12 Host High-Availability



113

12 Host High-Availability

12.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.

12.1.1 MSCS

An MSCS server cluster contains a maximum of eight nodes, and can be configured as either

of the following clusters:

Single-node cluster

Single-quorum device cluster

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 12-1 lists the maximum number of nodes supported by different operating systems.




114

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

Operating System Storage Type Max. Number of Nodes

Windows Server 2003 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)

Parallel SCSI 2



Version:

Windows Server 2003



Platform:

x86 and x64 (Itanium)

Fiber Channel 8



Version:



Platform:

x86 and x64 (Itanium)

iSCSI or SAS 8

12.1.2 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:

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.

Resource management




115

Individual nodes in the cluster may provide physical resources such as direct-attached

storage, network interfaces, and access to share disk storage. Hosted applications register

themselves as cluster resources, and may configure startup and health dependencies upon

other resources.

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.

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 12-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.

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.




116

Term Description

Forced quorum The process to start the cluster even through only a

minority of the elements that are required for quorum

are in communication.

12.2 Configuration

12.2.1 MSCS

For details, visit:

http://technet.microsoft.com/zh-cn/library/cc731844%28v=WS.10%29.aspx

Huawei also provides MSCS configuration guides. You can obtain the guides from the

Huawei customer service center.

12.2.2 WSFC

For details, visit:

http://technet.microsoft.com/zh-CN/library/cc732035%28v=ws.10%29.aspx

Huawei also provides WSFC configuration guides. You can obtain the guides from the

Huawei customer service center.

http://technet.microsoft.com/zh-cn/library/cc731844%28v=WS.10%29.aspx

http://technet.microsoft.com/zh-CN/library/cc732035%28v=ws.10%29.aspx

HUAWEI SAN Storage Host Connectivity Guide for Windows 13 Virtualization Technology



117

13 Virtualization Technology

13.1 Introduction to Hyper-V

Hyper-V is used to create a virtualized server computing environment where multiple

hardware resources are utilized to improve computing efficiency.

Hyper-V provides the following functions:

Virtualization based 64-bit virtual machine (VM) management programs

Concurrent running of 32-bit and 64-bit VMs

Single-processor and multi-processor VMs

VM snapshots: captures the status, data, and hardware configuration of running VMs.

You can use VM snapshots to restore VMs to their original states.

Large VM memory

Virtual local area network (VLAN)

Microsoft Management Console (MMC)

Windows Management Instrumentation (WMI) interfaces that facilitate script

compilation and management archiving

Hyper-V has the following requirements on server hardware and operating systems:

Operating system: 64-bit Windows Server 2008 Standard, Windows Server 2008

Enterprise, Windows Server 2008 Datacenter, and Windows Server 2012 Datacenter

CPU: support for Hardware-assisted virtualization (HAV) and hardware-enforced Data

Execution Prevention (DEP) functions and with those functions enabled

You can configure HAV and hardware-enforced DEP in BIOS.

13.2 Hyper-V Configuration

Hyper-V is built in Windows Server 2008 and later versions. It functions correctly only after

you manually add the Hyper-V role and complete related configurations.

13.2.1 Adding Hyper-V

Perform the following steps to add the Hyper-V role:

Step 1 Start Server Manager and choose Role to add the Hyper-V role.

HUAWEI SAN Storage Host Connectivity Guide for Windows 13 Virtualization Technology



118

Step 2 Select the service network adapter of the host and bind the network adapter as virtual network

adapter.

Step 3 Confirm the configuration and restart the host for the configuration to take effect.

----End

13.2.2 Creating Hyper-V VMs

Creating a Hyper-V VM is similar to creating a new server. During Hyper-V VM creation,

you need to configure memories, network adapters, and disks, and name the VM to be

created.

Note the following when creating Hyper-V VMs:

The size of the VM memory cannot exceed that of the server's physical memory.

In versions earlier than Hyper-V 3.0, the virtual disk format is VHD. Therefore, the

virtual disk capacity cannot exceed 2 TB. In Hyper-V 3.0, the virtual disk format is

VHDX and the virtual disk size can be up to 64 TB.

For details about how to create Hyper-V VMs, visit:

http://technet.microsoft.com/zh-cn/library/hh831531.aspx

http://technet.microsoft.com/zh-cn/library/hh831531.aspx

HUAWEI SAN Storage Host Connectivity Guide for Windows A Acronyms and Abbreviations



119

A Acronyms and Abbreviations

A

ALUA Asymmetric Logical Unit Access

B

BIOS

C

Basic Input Output System

CHAP Challenge Handshake Authentication Protocol

CLI Command Line Interface

CPU Central Processing Unit

D

DNS Domain Name System

DSM Device-Specific Module

E

exFAT Extended File Allocation Table File System

F

Fibre Channel Fibre Channel

FCoE Fibre Channel over Ethernet

FAT

File Allocation Table

http://baike.baidu.com/view/1425612.htm

http://baike.baidu.com/view/1172818.htm




120

G

GPT GUID Partition Table

GUID Globally Unique Identifier

H

HBA Host Bus Adapter

I

IP Internet Protocol

ISM Integrated Storage Manager

iSCSI Internet Small Computer Systems Interface

L

LAN Local Area Network

LUN Logical Unit Number

M

MBR Master Boot Record

MMC Microsoft Management Console

MPIO Microsoft Multi-Path IO

MSCS Microsoft Cluster Service

N

NTFS New Technology File System

O

OS Operating System

R

level Redundant Array of Independent Disks




121

P

PID Product ID

S

SAN Storage Area Network

SAS Serial Attached SCSI

SCSI Small Computer System Interface

V

VHD Virtual Hard Disk

VID Vendor ID

VG Volume Group

VLAN Virtual Local Area Network

VSAN Virtual Storage Area Network

W

WSFC Windows Server Failover Cluster

WWN World Wide Name