OceanStor S2600T&S5500T&S5600T&S5800T&S6800T Storage System V200R002C20 Basic Storage Service Guide (SAN Volume) 03

8/9/2019 OceanStor S2600T&S5500T&S5600T&S5800T&S6800T Storage System V200R002C20 Basic Storage Service Guide (SAN Volume) 03

1/204

OceanStor

S2600T&S5500T&S5600T&S5800T&S6800TStorage System

V200R002C20

Basic Storage Service Guide (SANVolume)

Issue 03

Date 2014-11-05

HUAWEI TECHNOLOGIES CO., LTD.


2/204

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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 thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://enterprise.huawei.com

Issue 03 (2014-11-05) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i
http://enterprise.huawei.com/


3/204

About This Document

This document describes the basic storage services and explains how to configure and manage basic storage services.

Intended AudienceThis document is intended for:l Technical support engineersl Maintenance engineers

ConventionsThe purchased products, services, and features are stipulated by the commercial contract made

between Huawei and the customer. All or partial products, services and features described inthis document may not be within the purchased scope or the usage scope. Unless otherwiseagreed by the contract, all statements, information, and recommendations in this document are

provided "AS IS" without warranties, guarantees, or representations of any kind, either expressor implied.

As part of an effort to improve and enhance the product performance and capabilities, HuaweiTechnologies Co., Ltd. periodically releases revisions of the hardware and software. Therefore,some functions described in this document may not be supported by all versions of the softwareor hardware currently in use. For the most up-to-date information about product features, refer to the product release notes.

If a product does not function as described in this document, contact Huawei technical supportengineers.

Change HistoryChanges between document issues are cumulative. The latest document issue contains all thechanges made in earlier issues.

Issue 03 (2014-11-05)

This is the third official release.

OceanStor S2600T&S5500T&S5600T&S5800T&S6800TStorage SystemBasic Storage Service Guide (SAN Volume) About This Document


ii


4/204

Modified the section of adding a route and added FAQs.

Issue 02 (2014-08-30)

This is the second official release.Modified the description about the storage space occupied by parity data in planned capacity.Added information about setting SmartTier policies in "Creating a Storage Pool".

Issue 01 (2014-05-30)

This issue is the first official release.

OceanStor S2600T&S5500T&S5600T&S5800T&S6800TStorage SystemBasic Storage Service Guide (SAN Volume) About This Document


iii


5/204

Contents

About Thi s Document.....................................................................................................................ii

1 Basic Storage Services...................................................................................................................11.1 Introduction....................................................................................................................................................................2

1.2 Application Scenarios.....................................................................................................................................................21.3 Basic Storage Principles.................................................................................................................................................3

2 Planning Basic Storage Services...............................................................................................102.1 Planning P rocess...........................................................................................................................................................12

2.2 Planning Applications...................................................................................................................................................14

2.3 Planning t he Capacity...................................................................................................................................................15

2.4 Planning Disk Domains................................................................................................................................................18

2.5 Planning S torage Pools.................................................................................................................................................19

2.6 Planning Read/Write Policies for LUNs......................................................................................................................22

2.7 (Optional) Planning iSCSI CHAP................................................................................................................................24

2.8 Planning User Accounts...............................................................................................................................................25

2.9 Data Preparation Checklist...........................................................................................................................................25

3 Configu ring Basic Storage Services.........................................................................................303.1 Configura tion Process...................................................................................................................................................32

3.2 Checking Before Configuration....................................................................................................................................38

3.3 Logging I n to the DeviceManager................................................................................................................................41

3.4 Creating a Disk Domain...............................................................................................................................................44

3.5 Creating a Storage Pool................................................................................................................................................47

3.6 Creating a LUN............................................................................................................................................................51

3.7 Creating a LUN Group.................................................................................................................................................59

3.8 (Optional) Adding Route (Applicable to iSCSI Connection).......................................................................................60

3.9 Configuring an Initiator (Applicable to iSCSI Connection).........................................................................................62

3.9.1 Configu ring an Initiator (on a Windows-based Application Server).........................................................................63

3.9.2 Configu ring an Initiator (on a SUSE 9.0-based Application Server)........................................................................68

3.9.3 Configuring an Initiator (on a SUSE 10.0-based Application Server)......................................................................71

3.9.4 Configuring an Initiator (on a Red Hat-based Application Server)...........................................................................74

3.9.5 Configuring an Initiator (on a Solaris-based Application Server).............................................................................76

3.9.6 Configuring an Initiator (on an AIX-based Application Server)...............................................................................79

OceanStor S2600T&S5500T&S5600T&S5800T&S6800TStorage SystemBasic Storage Service Guide (SAN Volume) Contents


iv


6/204

3.9.7 Configuring an Initiator (on a HP-UX-based Application Server)............................................................................83

3.9.8 Configuring an Initiator (on a VMware ESX-based Application Server).................................................................86

3.10 Creating a Host...........................................................................................................................................................90

3.10.1 Automatically Scanning for a Host.........................................................................................................................91

3.10.2 Manually Creating a Host........................................................................................................................................91

3.11 Creating a Host Group................................................................................................................................................94

3.12 (Optiona l) Configuring CHAP Authentication (Applicable to iSCSI Connection)...................................................96

3.12.1 Config uring CHAP Authentication (on a Windows-based Application Server).....................................................96

3.12.2 Config uring CHAP Authentication (on a SUSE 9.0-based Application Server)..................................................100

3.12.3 Config uring CHAP Authentication (on a SUSE 10.0-based Application Server)................................................101

3.12.4 Config uring CHAP Authentication (on a Red Hat-based Application Server).....................................................102

3.12.5 Config uring CHAP Authentication (on a Solaris-based Application Server).......................................................102

3.12.6 Config uring CHAP Authentication (on an AIX-based Application Server).........................................................103

3.12.7 Config uring CHAP Authentication (on a HP-UX-based Application Server)......................................................106

3.12.8 Config uring CHAP Authentication (on a VMware ESX-based Application Server)...........................................108

3.13 Creating a Port Group...............................................................................................................................................110

3.14 Creating a Mapping View.........................................................................................................................................111

3.15 Configur ing LUN Mapping Using a Cipher Machine..............................................................................................112

3.16 Making Storage Space Available.............................................................................................................................113

3.16.1 Makin g Storage Space Available (on a Windows-based Application Server)......................................................114

3.16.2 Makin g Storage Space Available (on a SUSE-based Application Server)............................................................118

3.16.3 Makin g Storage Space Available (on a Red Hat-based Application Server)........................................................120

3.16.4 Makin g Storage Space Available (on a Solaris-based Application Server)..........................................................123

3.16.5 Makin g Storage Space Available (on an AIX-based Application Server)............................................................126

3.16.6 Makin g Storage Space Available (on a HP-UX-based Application Server).........................................................129

3.16.7 Makin g Storage Space Available (on a VMware ESX-based Application Server)...............................................132

4 Creating Storage Resources Based on Applications...........................................................1384.1 Configuri ng Microsoft Exchange...............................................................................................................................139

4.1.1 About M icrosoft Exchange......................................................................................................................................139

4.1.2 Creating a Microsoft Exchange Instance.................................................................................................................139

4.2 Configuri ng VMware.................................................................................................................................................144

4.2.1 About V Mware........................................................................................................................................................144

4.2.2 Creating a VMware Instance...................................................................................................................................145

4.3 Configuri ng Hyper-V.................................................................................................................................................150

4.3.1 About H yper-V........................................................................................................................................................150

4.3.2 Creating a Hyper-V Instance...................................................................................................................................151

4.4 Configuri ng Oracle.....................................................................................................................................................157

4.4.1 About O racle............................................................................................................................................................157

4.4.2 Creating an Oracle Instance.....................................................................................................................................157

4.5 Configuri ng SQL Server.............................................................................................................................................162

4.5.1 About S QL Server...................................................................................................................................................162



v


7/204

4.5.2 Creating an SQL Server Instance............................................................................................................................163

5 Managing Permissions.............................................................................................................1685.1 Creating a User Account.............................................................................................................................................169

5.2 Configuring Security Policy.......................................................................................................................................1725.3 Setting Domain Authentication Server Information...................................................................................................176

5.4 Configuring Authorized IP Addresses........................................................................................................................179

6 FAQ..............................................................................................................................................1806.1 How Do I Obtain the Location of Each Disk in a Subgroup?....................................................................................181

6.2 Can I Remove Disks from a Subgroup?.....................................................................................................................181

A How to Obtain Help.................................................................................................................182A.1 Preparations For Contacting Huawei.........................................................................................................................183

A.1.1 Collecting Troubleshooting Information................................................................................................................183

A.1.2 Making Debugging Preparations............................................................................................................................183

A.2 How to Use the Document.........................................................................................................................................183

A.3 How to Obtain Help from Website............................................................................................................................183

A.4 Ways to Contact Huawei...........................................................................................................................................184

B Glossary......................................................................................................................................185

C Acronyms and Abbreviations................................................................................................196



vi


8/204

1 Basic Storage ServicesAbout This Chapter

Configure basic storage services for application servers to use the storage space provided by theS2600T/S5500T/S5600T/S5800T/S6800T storage system.

1.1 IntroductionThe S2600T/S5500T/S5600T/S5800T/S6800T storage systems provide increased responsespeed, scalability, and enhanced self-healing capability.

1.2 Applicati on ScenariosThis section describes the application scenarios of basic storage services.

1.3 Basic Sto rage PrinciplesStorage syste ms provide storage space for application servers. The S2600T/S5500T/S5600T/S5800T/S6800T storage systems use the block virtualization technology to support dynamicallocation an d expansion of storage resources in storage pools. This shortens the response timefor data reads /writes in the storage pool s and the reconstruction time after a hard disk fails.

OceanStor S2600T&S5500T&S5600T&S5800T&S6800TStorage SystemBasic Storage Service Guide (SAN Volume) 1 Basic Storage Services


1


9/204

1.1 IntroductionThe S2600T/S5500T/S5600T/S5800T/S6800T storage systems provide increased responsespeed, scalability, and enhanced self-healing capability.

The S2600T/S5500T/S5600T/S5800T/S6800T storage systems use the block virtualizationtechnology to manage hard disks, which helps automatically and properly allocate storageresources and provide available storage space for application servers.

Block virtualization is a new redundant array of independent disks (RAID) technology thatdivides hard disks into block-level chunks and organizes the chunks into multiple RAID groups.When a hard disk fails, source disks of storage pools in the storage system participate in thereconstruction. This smashes the performance bottleneck in the reconstruction of traditionalRAID groups and greatly improves the data reconstruction speed.

Storage pools are containers of storage resources. The storage resources used by applicationservers are all from storage pools. The storage resources of storage pools originate from disk domains.

The S2600T/S5500T/S5600T/S5800T/S6800T storage systems have the followingcharacteristics:l Increased response speed

The storage system supports load balancing across the entire system. Data is distributed tothe source disks of storage pools to fully use the I/O capabilities of the storage system.

l Scalability

As the storage system manages disks and provides storage space for application servers inthe form of disk domains, you only need to add disks to the disk domains and expandcorresponding storage pools when storage capacity is found insufficient.

l Enhanced self-healing capability

The storage system supports concurrent reconstruction across the entire system. Sourcedisks of storage pools participate in reconstruction simultaneously to eliminate the

performance bottleneck of traditional RAID groups and notably improve datareconstruction speed.

l Balance between performance and cost

The storage system can automatically detect I/O hotspots and migrate data among storagetiers to achieve the best storage performance by using dynamic storage tiering (DST).

NOTE

l DST requires the storage system to support the SmartTier feature. You must purchase a licenseto use SmartTier. For details, see the OceanStor S2600T&S5500T&S5600T&S5800T&S6800T Storage System V200R002C20 SmartTier Feature Guide .

l A storage system with only one type of storage media does not support SmartTier.

1.2 Application ScenariosThis section describes the application scenarios of basic storage services.

The S2600T/S5500T/S5600T/S5800T/S6800T storage systems can be connected to applicationservers through an IP or Fibre Channel network.



2


10/204

l IP network

Strengths: The IP network supports long-distance transmission and can be built andexpanded at a low cost. The IP network is widely used.

Weaknesses: The IP network supports network bandwidth sharing, affecting the datatransfer rate between storage systems and application servers.

l Fibre Channel network

Strengths: The Fibre Channel network provides a fast transfer rate and a high bandwidthto ensure data transfer between storage systems and application servers.

Weaknesses: The Fibre Channel network has a high construction cost and limitedtransmission distance, and is difficult to expand.

The S2600T/S5500T/S5600T/S5800T/S6800T storage systems can be connected to a variety of application servers including Windows, Linux, and UNIX (such as AIX, HP-UX, and Solaris)application servers.

Figure 1-1 shows the application scenarios of basic storage services.

Figure 1-1 The application scenarios of basic storage services

OceanStor storage system

IP/FibreChannelnetwork

Windows-basedapplication server

Linux-basedapplication server

UNIX-basedapplication server

1.3 Basic Storage PrinciplesStorage systems provide storage space for application servers. The S2600T/S5500T/S5600T/S5800T/S6800T storage systems use the block virtualization technology to support dynamicallocation and expansion of storage resources in storage pools. This shortens the response timefor data reads/writes in the storage pools and the reconstruction time after a hard disk fails.



3


11/204

Context

A storage system with only one type of storage media does not support SmartTier.

Basic ConceptsGet yourself started with the following basic concepts.

l Disk domain : consisting of the same type or different types of disks. Disk domains areisolated from each other. Therefore, services carried by different disk domains do not affecteach other in terms of performance and faults (if any).

l Storage pool : container of storage resources, which is created under a disk domain. Thestorage resources used by application servers are all from storage pools. Based on thestorage media, a storage pool can have three storage tiers, including the high performancetier, performance tier, and capacity tier.

l Storage tier : a set o f storage media providing the same performance in a storage pool.Storage tiers are used to manage storage media with different performance and provideappropriate storage space for applications having different performance requirements.

l Chunk : CK for short, consecutive physical spaces of a fixed size on a hard disk.l Chunk group : CKG for short, a logical set of chunks on different hard disks. A chunk

group has the properties of a RAID group.l Block virtualization : a new type of redundant array of independent disks (RAID)

technology. Block virtualization divides hard disks into multiple chunks of a fixed size andorganizes them into multiple chunk groups. When a hard disk fails, all the hard disks onwhich the other chunks in the same chunk group as the chunks on the failed hard disk arelocated participate in the reconstruction. This significantly increases the hard disks involved

in the reconstruction, eliminating the performance bottleneck in the reconstruction of traditional RAID groups and improving the data reconstruction speed. In addition, block virtualization distributes data to all the hard disks in a storage system and leverage the I/O

processing capability of the storage system.l Extent : a block of a fixed size in a chunk group, 4 MB by default. The extent is the smallest

unit of a LUN, as well as being the smallest unit used to calculate the requested space,released space, and relocated data.

l Hot spare space : the space used for faulty block data reconstruction in block virtualization.When a chunk is faulty, the system lets a chunk of the hot spare space take over and instructsthe other chunks in the chunk group to perform data reconstruction using the hot sparespace. This ensures data integrity and read/write performance.

Storage Pool Structure

Figure 1-2 shows the structure of a storage pool.



4


12/204

Figure 1-2 Structure of a storage pool

Storage pool

SASTier 1 SAS3SAS2 SAS1

NL-SAS

Tier 2 NL-SAS3NL-SAS2 NL-SAS1

SSD

Tier 0 SSD3SSD2 SSD1

A storage pool consists of three storage tiers. Each storage tier is constructed by the same typeof storage media.

l Tier 0 is the high performance tier, which is composed of solid-state drives (SSDs). Tier 0

provides the highest performance at a high cost. It is used to store frequently accessed data.l Tier 1 is the performance tier, which is composed of serial attached SCSI (SAS) disks. Tier

1 provides high performance at a moderate cost. It is used to store less frequently accesseddata.

l Tier 2 is the capacity tier, which is composed of Near Line SAS (NL-SAS) disks. Tier 2 provides moderate performance and a large capacity per disk at a low cost. It is used tostore a large amount of data and seldom-accessed data.

Block Virtualization Process

Figure 1-3 shows the block virtualization process.



5


13/204

Figure 1-3 Block virtualization process

5 6

SSDHigh-performance

tier

10 11 127 8 9

16 17 1813 14 15

41 2 3

LUN 3

LUN 2

LUN 1

LUN

CKG CKG

Storage Pool 1

Disk Domain

SSD1 SSD2 SSD3

SAS

Performance tier

NL-SAS

Capacity tier

NL-SAS1654

1 2 3

Storage Pool 3

Storage Pool 2

CKG CKG

CKG CKG

Hot spare space

NL-SAS210 11 127 8 9

NL-SAS316 17 1813 14 15

54SAS1 SAS3

1 26 16 17 18

13 14 153

SAS210 11 127 8 9

CKG

Hot spare space

CKG

CKG

Hot spare space

Chunk

ExtentHot Spare Chunk

1. The disks on a storage system can be divided into multiple disk domains. A disk domainconsists of the same type or different types of disks. Disk types of a disk domain determinethe storage tiers of storage pools. The number of storage pools that can be created in a disk domain depends on the capacity of the disk domain.

2. The storage system divides the storage media in disk domains into chunks. Each chunk hasa fixed size, which cannot be changed.

3. When creating a disk domain, the storage system assigns it the default hot spare policy .When a disk is faulty, the storage system allocates free chunks in real time as hot sparespace based on the disk usage.

4. A storage pool in a disk domain supports a maximum of three storage tiers. Each storage

tier consists of the same type of chunk groups.l The high performance tier consists of chunk groups (CKGs) provided by solid state

drives (SSDs) and delivers the highest performance among the three tiers. As SSDshave a high cost and low capacity, the high performance tier is suitable for storingfrequently accessed data.

l The performance tier consists of CKGs provided by SAS disks and delivers high performance. As SAS disks have a moderate cost and large capacity, the performancetier is suitable for storing less frequently accessed data.

l The capacity tier consists of CKGs provided by NL-SAS disks and delivers the lowest performance among the three tiers. As NL-SAS disks have the lowest cost and largestcapacity, the capacity tier is suitable for storing a large amount of the least frequentlyaccessed data.



6


14/204

5. A CKG is formed by chunks in a storage tier based on the RAID policy configured on theDeviceManager. Chunks of each CKG come from different disks. You can set the RAIDpolicy for each storage tier. The RAID policy specifies the RAID level of a storage tier and the number of data blocks and parity blocks for this RAID level.

6. The storage system divides CKGs into extents based on the data migration granularityconfigured on the DeviceManager. The extent is the smallest unit of a LUN. The extentsmay vary according to storage pools but must be the same in one storage pool.

7. The LUNs used by application servers are composed of extents. Space application, spacerelease, and data relocation of LUNs are based on extents. When creating a LUN, you canspecify that the capacity of the LUN comes from a storage tier. In this case, the LUN iscomposed of the extents in the storage tier. When the services are running, the storagesystem relocates data among the storage tiers based on the data activity level and datarelocation policy. (This function requires a license.) After that, data on the LUN isdistributed by extent to the storage tiers in the storage pool.

NOTE

Multiple extents form a LUN. When creating a LUN, you are advised to specify the LUN capacityto a value that is an integer multiple of extents. Otherwise, when the LUN applies for space in theunit of extent, the storage system allocates space that is an integer multiple of extents and larger thanthe specified capacity to the LUN, wasting certain capacity. For example, the capacity of a storage

pool is 1 GB and an extent contains 4 MB. If the capacity of a thick LUN is set to 1 MB, the thick LUN capacity is displayed as 1 MB but actually the thick LUN occupies 4 MB. The remainingcapacity that can be allocated is 1020 MB only. If you want to expand the thick LUN, the thick LUNcan be expanded to 1021 MB only. The thick LUN cannot be expanded to 1 GB.

Process for Making Storage Space Available

Figure 1-4 shows the process for making storage space available.



7


15/204

Figure 1-4 Process for making storage space available

LUN Group 1

D:\

/dev/sdb1

Windows

Linux

Mappingview 1

UNIX

Virtual Machine

/dev/testlv

/dev/sdc1

Mapping

Application server

4

Mappingview 2

Mappingview 3

Mappingview 4

Storage system

iSCSI or Fibre Channel network

Mapping relationshipData reads and writes

1

3

LUN Group 2

LUN Group 3

LUN Group 4

Host Group 12

Host Group 2

Host Group 3

Host Group 4

iSCSI/FC

iSCSI/FC

5

1. Create LUNs based on the specified names, capacity and number of LUNs. To facilitateLUN management, the storage system directly manages LUN groups instead of individual



8


16/204

LUNs. After LUNs are created, you need to create a LUN group for those LUNs so thatthey can be added to a mapping view.

2. A host represents an application server on a storage system. Following Create HostWizard on the DeviceManager, link the host with the application server. To facilitate host

management, the storage system directly manages host groups instead of individual hosts.After hosts are created, you need to create a host group for those hosts so that they can beadded to a mapping view.

3. Optional: On an Internet Small Computer Systems Interface (iSCSI) network, you mustconfigure iSCSI initiators on application servers for the application servers to properlycommunicate with the storage system. When using a Fibre Channel network, you do notneed to perform this operation.

4. After a mapping view is created, and a host group and a LUN group are added to themapping view, the application servers, host group, and LUN group are logically associated.Then the application servers can detect LUNs in the LUN group.

5. Scan for LUNs on the application server. The allocated storage space will be discovered.The application server can use the storage space as its local hard disks.



9


17/204

2 Planning Basi c Storage ServicesAbout This Chap ter

To achieve a balance among the security, performance, and cost, make appropriate plans tofacilitate sub sequent configuration and maintenance before configuring basic storage services.

2.1 Planning ProcessBefore using a storage system, make the following plans to achieve a balance among the security,

performance, and cost for using a storage system.

2.2 Planning ApplicationsThe storage s ystem provides application-based wizards to create storage resources. The

applications i nclude Microsoft Exchange, VMware, Hyper-V, Oracle, and SQL Server.Therefore, yo u can use the corresponding wizard to create storage resources for the precedingfive applicati ons. To create storage resources for other applications, follow the configuration

procedure for basic storage services.

2.3 Planning the CapacityThe capacity of a storage system is used to store service data and system data. To ensure thatthe capacity f or service data is sufficient, the capacity for system data must be properly planned.

2.4 Planning Disk DomainsA disk domain provides storage space for storage pools, whose storage tiers and availablecapacities depend on the disk types, capacity, and hot spare policy of the disk domain.

2.5 Planning Storage PoolsBefore using a storage system, create storage pools to provide storage space for applicationservers, and make the following plans on the storage tiers, RAID levels and hot spare policies

based on your requirements.

2.6 Planning Read/Write Policies for LUNsSelect appropriate read/write policies and prefetch policies for LUNs based on the data storagerequirements to achieve the optimal performance of the storage system.

2.7 (Optional) Planning iSCSI CHAPTo ensure the storage system access security, plan iSCSI Challenge Handshake AuthenticationProtocol (CHAP) to control the access to the storage system.

2.8 Planning User Accounts

OceanStor S2600T&S5500T&S5600T&S5800T&S6800TStorage SystemBasic Storage Service Guide (SAN Volume) 2 Planning Basic Storage Services


10


18/204

Any user that has logged in to a storage system can execute operations. Misoperations by a user can impair the storage system reliability and data integrity. To avoid data risks, the S2600T/S5500T/S5600T/S5800T/S6800T storage system defines three user levels and the operationsallowed for each user level.

2.9 Data Preparation ChecklistObtain the data required for configuration or plan the data based on site requirements.



11


19/204

2.1 Planning ProcessBefore using a storage system, make the following plans to achieve a balance among the security,

performance, and cost for using a storage system.

Figure 2-1 shows the recommended planning process, which is based on user behaviors indifferent stages.

Figure 2-1 Planning process

Planning iSCSICHAP

Purchasing a

storage system

Allocatingstorage space

Making storagespace available

Managing/

Maintaining thestorage system

User behaviors(by stage)

Planning thecapacity

Planning useraccounts

Planning Read/Write Policies for

LUNs

Planning storagepools

Storage tiers

RAID levels

User name andpassword (applicableto iSCSI networking)

Number andlevels of users

Required Optional

Planning diskdomains

Disk types

Capacity

Hot spare policies

Planningapplications

Table 2-1 describes the planning items.



12


20/204

Table 2-1 Planning items

Item Description Reference

Planning

applications

The storage system provides application-based

wizards to create storage resources. The applicationsinclude Microsoft Exchange, VMware, Hyper-V,Oracle, and SQL Server. Therefore, you can use thecorresponding wizard to create storage resources for the preceding five applications. To create storageresources for other applications, follow theconfiguration procedure for basic storage services.

2.2 Planning

Applications

Planning thecapacity

Storage capacity is users' basic requirement and must be planned first of all.

2.3 Planning theCapacity

Planning

disk domains

A disk domain provides storage space for storage

pools, whose storage tiers and available capacitiesdepend on the disk types, capacity, and hot spare

policy of the disk domain. Therefore, the disk types,capacity, and hot spare policy must be properly

planned for a disk domain.l Disk type: Disk types of a disk domain determine

the storage tiers of storage pools. Plan disk types based on site requirements.

l Capacity: The capacity of a disk domaindetermines the available capacities of storage

pools.l Hot spare policy: Plan hot spare policies and hot

spare space so that the hot spare space can takeover data from failed member disks.

2.4 Planning Disk

Domains

Planningstorage

pools

A storage system provides storage space for application servers in the form of storage pools.

The storage tiers and RAID levels of the storage poolsmust be properly planned in advance for better storageutilization.l Storage tier: Plan storage tiers to meet the need for

optimal distribution of hot data and cold data.l RAID level: Plan RAID levels based on actual

needs because RAID levels vary in performance,cost, and reliability.

2.5 PlanningStorage Pools

PlanningRead/WritePolicies for LUNs

Different read/write policies configured for LUNsaffect the response time of the storage system.Properly planned write policies and prefetch policiescan help improve the response speed of the storagesystem.

2.6 Planning Read/Write Policies forLUNs



13


21/204

Item Description Reference

(Optional)Planning

iSCSIChallengeHandshakeAuthentication Protocol(CHAP)

Considering the storage system access security whenapplication servers connect to the storage system

through iSCSI and use the storage space provided bythe storage system, plan the CHAP user name and password to control the access to the storage system.

2.7 (Optional)Planning iSCSI

CHAP

Planninguser accounts

Plan the number of users and their permissionscarefully for subsequent management andmaintenance. Users with different responsibilitiesshould have different permissions.

2.8 Planning UserAccounts

2.2 Planning ApplicationsThe storage system provides application-based wizards to create storage resources. Theapplications include Microsoft Exchange, VMware, Hyper-V, Oracle, and SQL Server.Therefore, you can use the corresponding wizard to create storage resources for the precedingfive applications. To create storage resources for other applications, follow the configuration

procedure for basic storage services.

This storage system provides two storage resource creation methods: the method based on

applications and the method based on the configuration procedure of basic storage services. Normally, all storage resources are created following the configuration procedure of basicstorage services. However, if Microsoft Exchange, VMware, Hyper-V, Oracle, and SQL Server are involved, you can use the corresponding storage resource wizard provided by the storagesystem to create storage resources. Therefore, before you configure services, check whether the

previous five applications are involved. Table 2-2 shows the details of the two configurationmethods.

Table 2-2 Two methods of creating storage resources

Application Type Method of Creating

Storage Resources

Reference

The five applications:Microsoft Exchange,VMware, Hyper-V, Oracle,and SQL Server

Create storage resourcesusing the correspondingwizard provided by thestorage system.

4 Creating StorageResources Based onApplications

Other applications Create storage resources byfollowing the configuration

procedure for basic storageservices.

3.1 Configuration Process

Note: If your services are one of the preceding five applications, refer to the correspondingchapter for configuration details.



14


22/204

Before you use the application-based method to create storage resources, ensure that a storage pool for the specific application exists in the storage system, while all required LUNs, LUNgroups, and host groups are automatically configured, which significantly reduces planning andconfiguration time and improves configuration efficiency.

Since the five applications have different requirements on storage medium and RAID policiesin the storage pool, the configuration procedures for the five applications may be different:l If there is no storage pool in the storage system or none of the existing storage pools meet

the application's requirements, create a new storage pool following instructions displayedon the wizard. For details, see 3.5 Creating a Storage Pool .

l If one of the existing storage pools can meet the application's requirements and the capacityin it is suffici ent, the sto rage system automatically match a storage pool that can be used.Therefore, you can use the storage resource creation wizard to configure services, and theapplication server can use the storage sources in the application.

2.3 Planning the CapacityThe capacity of a storage system is used to store service data and system data. To ensure thatthe capacity for service data is sufficient, the capacity for system data must be properly planned.

The capacity for storing system data refers to the file system capacity, hot spare capacity, andcoffer disk capacity. The space overhead consumed by the storage system makes the actualavailable capacity smaller than the capacity provided by the storage system.

The space overhead consumed by the storage system comprises several parts:l Capacity used by the parity data or mirrored data in a RAID group.l Capacity used by hot spare space.l Capacity used by coffer disks.l Capacity used by file systems and volume management software on the application server.l The reserved capacity of a storage pool is no more than 5.2% of the total capacity of the

storage pool.l Parity data space used for enhancing the data reliability of a storage system. For example,

the size of a sector is 520 bytes, 8 bytes of which are used for storing parity data.

The following describes the principles and methods for planning the capacities:l Disk utilization of different RAID levels

Table 2-3 lists the disk utilization of different RAID levels.

Table 2-3 Disk utilization of different RAID levels

RAID Level Available Capacity

RAID 1 Total capacity of data blocks for mirroring. The disk utilization is 1/n, where n is the number of RAID 1 member disks.



15


23/204

RAID Level Available Capacity

RAID 3 l 4Da + 1P b (recommended): The disk utilization is about80%.

l 2D + 1P: The disk utilization is about 66.67%.l 8D + 1P: The disk utilization is about 88.89%.

RAID 5 l 4D + 1P (recommended): The disk utilization is about80%.

l 2D + 1P: The disk utilization is about 66.67%.l 8D + 1P: The disk utilization is about 88.89%.

RAID 6 l 4D + 2P (recommended): The disk utilization is about66.67%.

l 8D + 2P: The disk utilization is about 80%.

RAID 10 The disk utilization is 50%.

RAID 50 l 4D + 2P (recommended): The disk utilization is about66.67%.

l 8D + 2P: The disk utilization is about 80%.l 16D + 2P: The disk utilization is about 88.89%.

a: D indicates the data block.

b: P indicates the parity block.

l Hot spare space

To prevent data loss or performance deterioration caused by a member disk failure in astorage pool, the storage system employs hot spare space to store data on the failed member disk.

The following are the supported hot spare policies: High: A storage tier uses the capacity of one hard disk in every 12 hard disks as the hot

spare space. The capacity of hot spare space non-linearly increases as the number of disks increases. When the number of hard disks reaches 168, a storage tier uses thecapacity of one hard disk in every 96 hard disks as the hot spare space.

Low: A storage tier uses the capacity of one hard disk in every 24 hard disks as the hotspare space. The capacity of hot spare space non-linearly increases as the number of disks increases. When the number of hard disks reaches 168, a storage tier uses thecapacity of one hard disk in every 192 hard disks as the hot spare space.

Table 2-4 shows that the capacity of hot spare space non-linearly increases as the number of disks increases.



16


24/204

Table 2-4 The capacity changes of hot spare space

Number of Disks(Block)

Critical Value ofHot Spare SpaceCapacity (Block)

Capacity of HighHot Spare Policy(Block)

Capacity of LowHot Spare Policy(Block)

1 to 12 12 1 1

13 to 24 24 2

25 to 48 48 3 2

49 to 72 72 4

73 to 120 120 5 3

121 to 168 168 6

169 to 264 264 7 4265 to 360 360 8

NOTE

Table 2-4 lists common capacity changes of the hot spare space. The number of disks supported bya storage system and the capacity of their hot spare space are based on actual conditions.

When creating a storage pool, ensure that there are sufficient disks to provide the hot sparearea.

l Coffer disks The first four disks in the controller enclosure of the S2600T/S5500T are configured as

coffer disks. Coffer disks store critical system data. The first four disks in the first disk enclosure of the S5600T/S5800T/S6800T are

configured as coffer disks. Coffer disks store critical system data.

NOTE

The rest of the coffer disk space can be used to store service data.

l File systems and volume management software on the application server

File systems and volume management software of multiple types on the application server

may occupy some capacities of LUNs in the storage system. The actually occupiedcapacities depend on the deployment of applications on the application server.

The disk capacity defined by disk manufacturers is different from that calculated by operatingsystems. As a result, the nominal capacity of a hard disk is different from that displayed in theoperating system.

l Disk capacity defined by disk manufacturers: 1 GB = 1,000 MB, 1 MB = 1,000 KB, 1 KB= 1,000 bytes.

l Disk capacity calculated by operating systems: 1 GB = 1,024 MB, 1 MB = 1,024 KB, 1KB = 1,024 bytes.

NOTE

This mapping table is for reference only. The disk capacity displayed on the DeviceManager prevails.



17


25/204

2.4 Planning Disk DomainsA disk domain provides storage space for storage pools, whose storage tiers and availablecapacities depend on the disk types, capacity, and hot spare policy of the disk domain.

Planning Disk Types for a Disk Domain

A disk type in a disk domain corresponds to a storage tier of a storage pool. If the disk domaindoes not have a specific disk type, the corresponding storage tier cannot be created for a storage

pool.

Table 2-5 describes the mapping between disk types and storage tiers.

Table 2-5 Mapping between disk types and storage tiers

Disk Type Storage Tier

SSD High performance tier

SAS disk Performance tier

NL-SAS disk Capacity tier

Planning Capacity for a Disk Domain

The space of a storage pool originates from a disk domain. Therefore, the capacity of the disk domain determines the available capacity of the storage pool.

Planning Hot Spare Policies for a Disk Domain

To prevent data loss or performance deterioration caused by a member disk failure, the storagesystem employs hot spare space to take over data from the failed member disk.

The following are the supported hot spare policies:l High: A storage tier uses the capacity of one hard disk in every 12 hard disks as the hot

spare space. The capacity of hot spare space non-linearly increases as the number of disks

increases. When the number of hard disks reaches 168, a storage tier uses the capacity of one hard disk in every 96 hard disks as the hot spare space.l Low: A storage tier uses the capacity of one hard disk in every 24 hard disks as the hot

spare space. The capacity of hot spare space non-linearly increases as the number of disksincreases. When the number of hard disks reaches 168, a storage tier uses the capacity of one hard disk in every 192 hard disks as the hot spare space.

Table 2-6 shows that the capacity of hot spare space non-linearly increases as the number of disks increases.



18


26/204

Table 2-6 The capacity changes of hot spare space

Number of Disks(Block)

Critical Value ofHot Spare SpaceCapacity (Block)

Capacity of HighHot Spare Policy(Block)

Capacity of LowHot Spare Policy(Block)

1 to 12 12 1 1

13 to 24 24 2

25 to 48 48 3 2

49 to 72 72 4

73 to 120 120 5 3

121 to 168 168 6

169 to 264 264 7 4265 to 360 360 8

NOTE

l Table 2-6 lists common capacity changes of the hot spare space. The number of disks supported bya storage system and the capacity of their hot spare space are based on actual conditions.

l The disk domain uses the High hot spare policy by default. You cannot modify the hot spare policyon the DeviceManager. You must log in to the command-line interface (CLI) of the storage systemto modify a hot spare policy. For details, see the OceanStor

S2600T&S5500T&S5600T&S5800T&S6800T Storage System V200R002C20 Command Reference .

When creating a disk domain, ensure that there are sufficient disks to provide the hot spare area.

2.5 Planning Storage PoolsBefore using a storage system, create storage pools to provide storage space for applicationservers, and make the following plans on the storage tiers, RAID levels and hot spare policies

based on your requirements.

Storage Tiers

A storage pool is a logical combination of one or more storage tiers. The storage pool of thestorage system supports a maximum of three storage tiers. A storage tier is a set of storage mediathat has the same performance and uses the same RAID level. Each storage tier provides different

performance at different costs. You can configure storage tiers based on your requirements.

Table 2-7 lists the specifications of each storage tier.



19


27/204


28/204

RAIDLevel

Redundancy andData RecoveryCapability

ReadPerformance

WritePerformance

Disk Utilization

RAID3 Relatively high. Eachchunk group has onechunk as the paritychunk. Data on any datachunk can be recoveredusing the parity chunk. If two or more blocks fail,the RAID level fails.

High Low l

4Da + 1P

b

(recommended):The disk utilization isabout 80%.

l 2D + 1P: Thedisk utilization isabout 66.67%.


RAID5

Relatively high. The parity data is distributedon different chunks. Ineach chunk group, the

parity data occupies achunk space. RAID 5allows the failure of onlyone chunk. If two or more blocks fail, theRAID level fails.

Relativelyhigh

Relativelyhigh

l 4D + 1P(recommended):The disk utilization isabout 80%.


RAID6

Relatively high. Twogroups of parity data aredistributed on differentchunks. In each chunk group, the parity dataoccupies two chunk space. RAID 6 allowstwo chunks to failsimultaneously. If threeor more data blocks fail,the RAID level fails.

Medium Medium l 4D + 2P(recommended):The disk utilization isabout 66.67%.

l 8D + 2P: Thedisk utilization isabout 80%.

RAID10

High. RAID 10 allowsmultiple chunks to failsimultaneously. When achunk fails, the mirror chunk can be used for data recovery. If a chunk and its mirror chunk failsimultaneously, theRAID level fails.

Relativelyhigh

Relativelyhigh

The disk utilizationis 50%.



21


29/204

RAIDLevel

Redundancy andData RecoveryCapability

ReadPerformance

WritePerformance

Disk Utilization

RAID50 Relatively high. The parity data is distributedon different chunks of each RAID 5 sub-group.In each RAID 5 sub-group, only one chunk isallowed to fail. If two or more data blocks of aRAID 5 sub-group failsimultaneously, theRAID level fails.

Relativelyhigh Relativelyhighl

4D + 2P(recommended):The disk utilization isabout 66.67%.

l 8D + 2P: Thedisk utilization isabout 80%.


a: D indicates the data block.

b: P indicates the parity block.

2.6 Planning Read/Write Policies for LUNsSelect appropriate read/write policies and prefetch policies for LUNs based on the data storagerequirements to achieve the optimal performance of the storage system.

Planning a Cache PolicyCache policies are divided into read policies and write policies. A cache read/write policy definesthe way that an application server reads data from or writes to disks after sending read and writeI/O requests. Improper setting of read and write policies will deteriorate the read and write

performance and reduce the reliability of a storage system.

A storage system supports both read and write policies. Table 2-9 describes the principles andapplication scenarios of the two policies.



22


30/204

Table 2-9 Principles and application scenarios of read and write policies

Policy Principle Application Scenario

Read policy Update rate of data in a cache

to be read. Possible values areResident , Default , andRecycle . Because cacheresources of a system arelimited, the read policy canimprove the overall utilizationand hit ratio of cache resourcesin specific scenarios.

l Resident : Applies to randomly

accessed services, ensuring thatdata can be cached as long as

possible to improve the read hitratio.

l Default : Applies to regular services, striking a balance

between the hit ratio and disk access performance.

l Recycle : Applies to sequentiallyaccessed services, releasing cacheresources for other services as soonas possible.

Write policy Update rate of data in a cache.Possible values are Resident ,Default , and Recycle . Becausecache resources of a system arelimited, the write policy canimprove the overall utilizationand hit ratio of cache resourcesin specific scenarios.

l Resident : Applies to randomlyaccessed services, ensuring thatdata can be cached as long as

possible to improve the read hitratio.

l Default : Applies to regular services, striking a balance

between the hit ratio and disk access performance.

l Recycle : Applies to sequentiallyaccessed services, releasing cacheresources for other services as soonas possible.

Planning Prefetch Policies

Applications have different size requirements for data read. The prefetch policies of LUNs canimprove the read performance.

The S2600T/S5500T/S5600T/S5800T/S6800T supports four prefetch policies: intelligent prefetch, constant prefetch, variable prefetch, and non-prefetch. Table 2-10 describes the principles and application scenarios of the four prefetch policies.



23


31/204

Table 2-10 Principles and application scenarios of prefetch policies

Prefetch Policy Principle Application Scenario

Intelligent

prefetch

Intelligent prefetch analyzes

whether the requested data issequential. If it is, the datafollowing the currentlyrequested data is prefetchedfrom hard disks to the cache toimprove the cache hit ratio. Thelength of intelligent prefetchranges from the start address of the currently requested data tothe end address of the chunk.

Intelligent prefetch is suitable for

single-stream read applications or for the read applications that cannot bedetermined sequential or random, for example, file read/write.

Constant prefetch After receiving a data readrequest, the storage system

prefetches the data to the cache based on the preset prefetchlength, regardless of the readlength specified in the I/Orequest.

The constant prefetch policy issuitable for the sequential readapplications that have a fixed size, for example, requests initiated by multipleusers for playing streaming media ondemand at the same bit rate.

Variable prefetch After receiving a data readrequest, the storage system

prefetches the data to the cache based on a multiple of the readlength specified in the I/Orequest.

The variable prefetch policy is suitablefor the sequential read applicationsthat have an unfixed size or for themulti-user concurrent readapplications whose prefetch dataamount cannot be determined, for example, requests initiated by multipleusers for playing multimedia ondemand at different bit rates.

Non-prefetch The host reads data directlyfrom hard disks based on theread length specified in the I/Orequest without a prefetch

process.

The non-prefetch policy is suitable for small-block random read applications,for example, databases.

NOTE

Cache prefetch may deteriorate the system performance when random read services are running on thestorage system, you are advised to use the non-prefetch policy.

2.7 (Optional) Planning iSCSI CHAPTo ensure the storage system access security, plan iSCSI Challenge Handshake AuthenticationProtocol (CHAP) to control the access to the storage system.

The CHAP is a method of verifying the identity of the peer using a 3-way handshake. Thisverification is based on a ciphertext or cipher key.



24


32/204

1. During the establishment of a link, the authenticator sends a challenge message to the peer.

2. The peer encrypts the random packet using the password and algorithm and responds withthe ciphertext.

3. The authenticator checks the response by encrypting the random packet using the peer's password and algorithm that have been saved. If the two ciphertexts match, theauthentication is acknowledged. If the two ciphertexts do not match, the authentication isnot acknowledged.

After CHAP authentication is enabled on the storage system, you must enter the CHAP user name and password when accessing the storage system from an application server.

When planning CHAP, note the following:l CHAP user name and password

The user name cont ains 4 to 25 letters, digits, periods (.), colons (:), or hyphens (-), and itmust start with a letter or digit. The password contains 12 to 16 characters.

l Mapping between CHAP user accounts and initiatorsCreate CHAP user accounts and assign them to corresponding initiators.

2.8 Planning User AccountsAny user that has logged in to a storage system can execute operations. Misoperations by a user can impair the storage system reliability and data integrity. To avoid data risks, the S2600T/S5500T/S5600T/S5800T/S6800T storage system defines three user levels and the operationsallowed for each user level.

The S2600T/S5500T/S5600T/S5800T/S6800T defines three local user levels:l Super administrator: A super administrator has the full control permission for the storage

system and can create the administrator and read-only user accounts.l Administrator: An administrator has the partial control permission for the storage system

but cannot create user accounts, upgrade the storage system.l Read-only user: A read-only user has only the access permission for the storage system and

can perform queries only, for example, querying the running status and health status of thestorage system.

When planning local user accounts, plan the number of users in each level and assign the user accounts to corresponding users.

2.9 Data Preparation ChecklistObtain the data required for configuration or plan the data based on site requirements.

Table 2-11 describes the data to be obtained before storage space configuration.



25


33/204

Table 2-11 Data to be obtained

Operation Item Default/Actual Value

Logging in to the

DeviceManager

IP addresses of the

management network ports.

IP address to be entered inthe browser address box for logging in to the

DeviceManager of the storage system.

Default valuel Controller A: 192.168.128.101l Controller B: 192.168.128.102

System name Name of the storage system.

__________________

User name and password

User name and password for logging in to the

DeviceManager of the storage system.

Super administrator user name: admin

Initial password: Admin@storage

Creating a disk domain

Disk domain name Name of the disk domain tobe created.

__________________

Disk type Disk types in the disk domain, which determine

the storage tiers that can becreated. SSDs correspond tothe high performance tier,SAS disks correspond to the

performance tier, and NL-SAS disks correspond to thecapacity tier.

High performance Tier (SSD) __________________

Performance Tier (SAS) __________________ Capacity Tier (NL-SAS)

__________________

Creating a storage pool

Storage pool name Name of the storage pool tobe created.

__________________

Storage tierThe storage pool can havethe high performance tier,

performance tier, and capacity tier. Each tier usesdifferent types of disks. If

you are going to applySmartTier, the storage pool must have two storage tiersat least.

High performance Tier (SSD) __________________

Performance Tier (SAS) __________________

Capacity Tier (NL-SAS) __________________



26


34/204


RAID policy Each tier is configured with

a specific RAID policy. Thedefault RAID policy on the DeviceManager isrecommended. For example, the default RAID

policy of the performancetier on the DeviceManager is RAID5 4D+1P , where Dindicates the data block and

P indicates the parity block.

High performanceTier__________________

PerformanceTier__________________

Capacity Tier__________________

Capacity

Capacity of each storagetier. The value must be aninteger on the

DeviceManager.

High performance

Tier__________________ PerformanceTier__________________

Capacity Tier__________________

Creating a LUN LUN name If the LUN is created in abatch, three digits areautomatically added after the LUN name.

__________________

Enable SmartThin or not If you enable the SmartThinwhen creating a LUN, a thin

LUN will be created. The storage system first allocates an initial capacityto a thin LUN and thenincreases the LUN capacityin real time and on demand based on the required

storage capacity.

Yes____

No____

CapacityCapacity of the LUN to becreated. For a thin LUN, thecapacity is the maximumallowed capacity for it after expansion.

__________________

Initial allocated capacityCapacity initially allocated to a thin LUN. This

parameter is available onlywhen you are creating a thin

LUN.

__________________



27


35/204


Quantity of LUNs A maximum of 100 LUNs

can be created at a time.

__________________

Creating a LUNgroup

LUN group name Name of the LUN group tobe created.

__________________

LUNs in the LUN group LUNs in the LUN group. LUNs in a LUN group canbe used by application

servers only after the LUN group is added to the

mapping view.

LUN group

________

________

LUN

________

________

Configuring aninitiator (applicableto iSCSIconnection)

iSCSI host port IP address of the iSCSI host port connected to theapplication server.

IP address__________________

Subnet mask/IPv6 prefix__________________

Gateway__________________

IQNs and IP addresses of the host ports (applicableto iSCSI connection)The initiator qualified name(IQN) is used by a storage

system to identifyapplication servers and canbe changed on application

servers.

IQNs

_____________

_____________

Host port IPaddresses

____________

____________

Creating a host Host nameThe host is a concept used inthe storage systemenvironment. A host corresponds to anapplication server.

__________________

WWPN of the FibreChannel port on theapplication server(applicable to FibreChannel connection)World Wide Port Name(WWPN) of the FibreChannel port on theapplication server.

__________________



28


36/204


Creating a hostgroup

Host group name Name of the host group to be

created.

__________________

Hosts in the host group Hosts in the host group.

Host group

________

________

Host

________

________

Creating a portgroup

Port group name Name of the port group to becreated.

__________________

Host ports in the portgroup

Host ports in the port group.

Port group

________

________

Port

________

________

Creating a mappingview

Mapping view name Name of the mapping view tobe created. You are not advised to use the default mapping view.

__________________

Mapping Mapping between host groups and LUN groups.

Host group

________

________

LUN group

________

________



29


37/204

3 Configuring Basic Storage ServicesAbout This Chap ter

Configure the S2600T/S5500T/S5600T/S5800T/S6800T to divide the storage space into LUNsand map them to application servers so that the application server can read and write the storagespace provided by the storage system.

3.1 Configur ation ProcessThe configur ation process includes the overall procedures for configuring the storage space.You can lear n about the storage space configuration logic.

3.2 Checking Before Configuration

Check wheth er the software installation and initial configuration meet the requirements for storage space configuration.

3.3 Logging I n to the DeviceManager The DeviceM anager is a device management pro gram developed by Huawei Technologies Co.,Ltd. The Dev iceManager has been loaded to the storage system before delivery. You can log into the Device Manager on any maintenance terminal connected to the storage system by usingthe managem ent network port IP address of the storage system and the local or domain user name in a browser.

3.4 Creating a Disk DomainThe types of disks in a domain decide which storage tiers can be created. The first step for

creating a storage pool is to build a disk domain and specify the types and quantity of comprisingdisks.

3.5 Creating a Storage PoolCreate storage pools for application servers to use the storage space provided by a storage system.

3.6 Creating a LUNThe storage space of a newly created storage pool cannot be identified by the host. The host canuse the storage space only after the storage space of the storage pool is divided into logical unitnumbers (LUNs) and the LUNs are mapped to the host.

3.7 Creating a LUN GroupFor easy management of multiple LUNs, logically add the LUNs to a LUN group.

3.8 (Optional) Adding Route (Applicable to iSCSI Connection)

OceanStor S2600T&S5500T&S5600T&S5800T&S6800TStorage SystemBasic Storage Service Guide (SAN Volume) 3 Configuring Basic Storage Services


30


38/204

If the IP addresses of the iSCSI host port on a storage system and the service network port onan application server are on different network segments, or if two storage system reside ondifferent local area networks (LANs), add a route for the iSCSI host port of the storage systemto establish a connection to the application server or the other storage system. If it is a Fibre

Channel network, skip this task.3.9 Configuring an Initiator (Applicable to iSCSI Connection)A storage system cannot communicate with an application server if you only physically connectone of its iSCSI host ports to a service network port on the application server using a network cable. You must configure an initiator on the application server to establish a logical connection

between the application server and storage system.

3.10 Creating a HostCreate a host to establish a connection between a storage system and an application server, andadd an initiator for the host to establish a mapping relationship between the host and applicationserver.

3.11 Creating a Host GroupTo centrally manage multiple hosts, you can logically aggregate hosts into a host group.

3.12 (Optional) Configuring CHAP Authentication (Applicable to iSCSI Connection)On a public n etwork, any application server can access the storage system whose IP address of the iSCSI hos t port resides on the same network segment as that of the application server toimplement da ta reads/writes. This poses risks to the data security of the storage system. To ensurethe storage sy stem access security, configure CHAP authentication to c ontrol the access to thestorage system.

3.13 Creating a Port GroupThis operatio n enables you to create a port gr oup and add it to a mapping view. After that, LUNs

of a specified LUN group use the ports of the port group to communicate with the correspondinghosts of the h ost group. If no port group is added to the mapping view, available ports arerandomly use d.

3.14 Creating a Mapping ViewThis operatio n enables you to create a m apping view and manage the mapping relationship

between multiple host groups and LUN groups by adding them to the mapping view.

3.15 Configu ring LUN Mapping Using a Cipher MachineUse a cipher machine to configure mapping relationships between application servers and LUNsto keep critic al services running in an encrypted environment. If no cipher machine is available,skip this secti on.

3.16 Making Storage Space AvailableAfter a conne ction is established between a storage system and an application server, theapplication se rver must discover the newly -added logical disk (that is, the storage space specified

by the mapped LUN) to use it as a normal hard disk for data reads and writes.



31


39/204

3.1 Configuration ProcessThe configuration process includes the overall procedures for configuring the storage space.You can learn about the storage space configuration logic.

If critical data must be encrypted, you are advised to deploy a cipher machine. The process for configuring storage space differs between a storage system configured with a cipher machineand that without a cipher machine. The processes are described as follows:

l When a storage system is not configured with a cipher machine, the flowchart for configuring storage space is shown in Figure 3-1 .



32


40/204

Figure 3-1 Flowchart for configuring storage space (without a cipher machine)

Start

Checking beforeconfiguration

Creating a LUN

Creating a storage pool

End

1. Preparing forconfiguration

2. Creatingstorage space

3. Setting upa connection

4. Makingstorage spaceavailable

To protect iSCSIconnections using CHAPauthentication, configureCHA

Documents

OceanStor S2600T&S5500T&S5600T&S5800T&S6800T Storage System V200R002C20 Basic Storage Service Guide (SAN Volume) 03