OceanStor Dorado 6.0.0 SmartVirtualization Feature Guide

OceanStor Dorado
6.0.0
SmartVirtualization Feature Guide
Issue 07
Date 2021-06-25
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://e.huawei.com
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. i

OceanStor Dorado
SmartVirtualization Feature Guide About This Document
About This Document
Purpose
This document describes the working principle and application scenarios of the
SmartVirtualization feature and explains how to configure and manage this
feature.
The following table lists the product models supporting SmartVirtualization.
Product Series Product Model
OceanStor Dorado V6 series Dorado 3000 V6
Dorado 5000 V6
Dorado 6000 V6
Dorado 8000 V6
Dorado 18000 V6
Intended Audience
This document is intended for:
● Technical support engineers

● Maintenance engineers
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.
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. ii

OceanStor Dorado
Symbol Description
Indicates a hazard with a medium level of risk

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

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

not avoided, could result in equipment damage,
data loss, performance deterioration, or
unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Supplements the important information in the main

text.
NOTE is used to address information not related to
personal injury, equipment damage, and
environment deterioration.
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes in earlier issues.
Issue 07 (2021-06-25)
This issue is the seventh official release.
Optimized some descriptions.
Issue 06 (2021-04-10)
This issue is the sixth official release.
Issue 05 (2020-12-20)
This issue is the fifth official release.
Issue 04 (2020-08-15)
This issue is the fourth official release.
Optimized the descriptions in the document.
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. iii

OceanStor Dorado
Issue 03 (2020-06-05)
This issue is the third official release, which incorporates the following changes:
Issue 02 (2020-01-10)
This issue is the second official release, which incorporates the following changes:
Added descriptions about OceanStor Dorado 18000 V6.
Issue 01 (2019-10-30)
This issue is the first official release.
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. iv

OceanStor Dorado
SmartVirtualization Feature Guide Contents
Contents
About This Document................................................................................................................ ii

1 Feature Description................................................................................................................. 1
1.1 Introduction............................................................................................................................................................................... 1
1.2 License Requirements and Compatible Products......................................................................................................... 3
1.3 Working Principle.................................................................................................................................................................... 4
1.4 Impact and Restrictions.........................................................................................................................................................7
1.5 Application Scenarios............................................................................................................................................................. 9
2 Selecting a Takeover Mode................................................................................................. 12

3 Taking Over Huawei Heterogeneous Storage Systems in Offline Mode................. 14
3.1 Configuration Process.......................................................................................................................................................... 14
3.2 Checking a License File....................................................................................................................................................... 15
3.3 Installation and Deployment............................................................................................................................................ 16
3.4 Configuring the Logical Connection Between the Heterogeneous Storage System and Local Storage
System.............................................................................................................................................................................................. 20
3.4.1 Fibre Channel Connection.............................................................................................................................................. 20
3.4.1.1 Configuring a Heterogeneous Storage System....................................................................................................20
3.4.1.2 Scanning for External LUNs........................................................................................................................................ 20
3.4.2 iSCSI Connection................................................................................................................................................................ 21
3.4.2.1 Managing Logical Ports............................................................................................................................................... 21
3.4.2.2 Adding an External Storage Device......................................................................................................................... 23
3.5 Configuring and Using an eDevLUN.............................................................................................................................. 25
3.5.1 Creating an eDevLUN...................................................................................................................................................... 25
3.5.2 Establishing Mapping Relationships Between eDevLUNs and the Application Server............................. 26
4 Taking Over Third-Party Heterogeneous Storage Systems in Offline Mode.......... 28

System.............................................................................................................................................................................................. 33
4.4.1 Configuring a Heterogeneous Storage System....................................................................................................... 34
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. v

OceanStor Dorado
4.4.2 Scanning for External LUNs........................................................................................................................................... 34

5 Taking Over Huawei Heterogeneous Storage Systems in Online Mode..................38

5.3 Pre-Configuration Check.................................................................................................................................................... 46
System.............................................................................................................................................................................................. 54
5.5.1 Fibre Channel Connection.............................................................................................................................................. 54
5.5.2 iSCSI Connection................................................................................................................................................................ 55
5.5.2.1 Managing Logical Ports............................................................................................................................................... 55
5.5.2.2 Adding an External Storage Device......................................................................................................................... 58
5.6.3 Scanning for eDevLUNs on an Application Server................................................................................................. 62
5.7 Configuring Host Path Switchover.................................................................................................................................. 63
5.7.1 Checking the Multipathing Status............................................................................................................................... 63
5.7.2 Switching Over Host Paths............................................................................................................................................ 66
5.7.3 Migrating the Reserved Information.......................................................................................................................... 69
5.7.4 Confirming the Completion of the Host Path Switchover.................................................................................. 70
5.8 Clearing the Path Switchover Property of the eDevLUNs that Are Masqueraded......................................... 71
6 Taking Over Third-Party Heterogeneous Storage Systems in Online Mode...........73

6.3 Pre-Configuration Check.................................................................................................................................................... 82
System.............................................................................................................................................................................................. 87
6.5.1 Configuring a Heterogeneous Storage System....................................................................................................... 87
6.5.2 Scanning for External LUNs........................................................................................................................................... 88
6.6.1 Checking Application Server Configurations............................................................................................................89
6.6.1.1 Red Hat Linux & SUSE Linux Operating System................................................................................................. 89
6.6.1.1.1 Deleting Virtual LUN 0 Generated Before Mapping.......................................................................................89
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. vi

OceanStor Dorado
6.6.1.1.2 Checking and Recording the ALUA Policy of External LUNs....................................................................... 90

6.6.1.2 HP-UX Operating System............................................................................................................................................ 91
6.6.1.3 VMware ESXi Operating System............................................................................................................................... 91
6.6.1.3.1 Checking Path Selection Policy.............................................................................................................................. 91
6.6.1.3.2 Checking and Recording the ALUA Policy of External LUNs....................................................................... 92
6.6.4 Scanning for eDevLUNs on an Application Server................................................................................................. 95
6.7 Configuring Host Path Switchover.................................................................................................................................. 96
6.7.1 Configuring Host Path Switchover (Red Hat Linux and SUSE Linux Operating Systems)....................... 96
6.7.1.1 Checking Multipathing Software Status................................................................................................................ 96
6.7.1.2 Switching Over Host Paths......................................................................................................................................... 97
6.7.2 Configuring Host Path Switchover (HP-UX Operating Systems)...................................................................... 98
6.7.2.1 Checking Multipathing Software Status................................................................................................................ 98
6.7.2.2 Switching Over Host Paths......................................................................................................................................... 99
6.7.3 Configuring Host Path Switchover (VMware ESXi Operating Systems).......................................................100
6.7.3.1 Checking Multipathing Software Status.............................................................................................................. 100
6.7.3.2 Switching Over Host Paths.......................................................................................................................................102
6.7.4 Confirming the Completion of the Host Path Switchover................................................................................ 104
6.8 Clearing the Path Switchover Property of the eDevLUNs that Are Masqueraded.......................................105
7 Configuring Data Migration............................................................................................. 107

8 Configuring Cold Data Migration....................................................................................109
9 Configuration Example...................................................................................................... 110
9.1 Using SmartMigration and SmartVirtualization to Migrate an Oracle ASM File System......................... 110
9.1.1 Requirement Analysis.................................................................................................................................................... 110
9.1.2 Configuration Planning................................................................................................................................................. 113
9.1.3 Configuration Operations.............................................................................................................................................127
9.1.4 Configuration Verification............................................................................................................................................ 134
9.2 Using SmartVirtualization to Centrally Manage Heterogeneous Storage Systems for an Oracle
Database....................................................................................................................................................................................... 134
9.2.1 Requirement Analysis.................................................................................................................................................... 134
9.2.2 Configuration Planning................................................................................................................................................. 136
9.2.3 Configuration Operations.............................................................................................................................................141
9.2.4 Configuration Verification............................................................................................................................................ 144
10 Managing SmartVirtualization......................................................................................146
10.1 Managing External Storage Devices.......................................................................................................................... 146
10.1.1 Viewing External Storage Device Information....................................................................................................146
10.1.2 Changing the Name of an External Storage Device.........................................................................................147
10.1.3 Adding an iSCSI Link....................................................................................................................................................147
10.1.4 Removing an iSCSI Link.............................................................................................................................................. 148
10.1.5 Removing an External Storage Device.................................................................................................................. 149
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. vii

OceanStor Dorado
10.1.6 Automatically Scanning for LUNs........................................................................................................................... 150

10.2 Managing eDevLUNs...................................................................................................................................................... 151
10.2.1 Expanding the Storage Space of an eDevLUN................................................................................................... 151
10.2.1.1 Capacity Expansion Process................................................................................................................................... 151
10.2.1.2 Precautions.................................................................................................................................................................. 152
10.3 Performing Rollback........................................................................................................................................................ 152
11 FAQs..................................................................................................................................... 156
11.1 Why Does a Local Storage System Display an Incorrect LUN Capacity After an External LUN of a
Heterogeneous Storage System Is Mapped to the Local Storage System?...........................................................157
11.2 What Can I Do If the New Configuration of an External LUN on a Heterogeneous Storage System
Cannot Be Synchronized to the Local Storage System?............................................................................................... 158
11.3 What Can I Do If an External LUN Abnormality Has Been Rectified on a Heterogeneous Storage
System but the Corresponding Remote LUN or eDevLUN Information on the Local Storage System Fails
to Be Updated or the Remote LUN Information Fails to Be Displayed?................................................................ 159
11.4 Why Is the Health Status of the Remote LUN and eDevLUN Still Displayed Normal on the Local
Zero-Load Storage System When an External LUN Malfunctions?..........................................................................161
11.5 How Can I Restore the Link If a Link Between a Switch and an HP EVA8000 Fails to Resume After
the Cable Between the HP EVA8000 and the Fibre Channel Switch Is Removed and Reinserted or the
Switch Is Restarted?.................................................................................................................................................................. 161
11.6 Why Does a Local Storage System Detect Thick LUNs After a Heterogeneous Storage System Maps
Thin LUNs to the Local Storage System?.......................................................................................................................... 162
11.7 Why Does a Local Storage System Detect Thin LUNs After a Heterogeneous Storage System Maps
Thick LUNs to the Local Storage System?........................................................................................................................ 162
11.8 Why Is Default Displayed in Device Name of the Remote Device in DeviceManager of a Local
Storage System After IBM Storwize V Series Storage System Is Connected to the Local Storage System?
......................................................................................................................................................................................................... 163
11.9 Why Does the Link Connection Become Abnormal with a Probability When Oracle SUN Storage6000
Series Is Connected to a Local Storage System Using a Switch?.............................................................................. 163
11.10 What Can I Do After the Heterogeneous Storage System Restarts, the Local Storage System Cannot
Display the Remote LUN That Corresponds to the External LUN or the eDevLUN Fails?............................... 164
11.11 Why Are Services Interrupted After All Physical Connections Between a Local Storage System and
One Controller of Dell Compellent SC Are Disconnected (When Service Loads Exist)?...................................165
11.12 Why Are Services Interrupted When You Restart One Controller of the Sugon DS800-G25/
MacroSAN MS3100/MacroSAN MS3300/MacroSAN MS7000 Series Heterogeneous Storage System with
Service Load?...............................................................................................................................................................................165
11.13 How Can I Discover a Remote LUN Belonging to a Heterogeneous Storage System in a Local
Storage System After the LUN Is Mapped to the Local Storage System for Hosting but the LUN Is Not Yet
Initialized?.................................................................................................................................................................................... 166
11.14 What Can I Do If a Local Storage System Cannot Discover the Remote LUN Corresponding to an
External LUN When the Physical Connection Between a Heterogeneous Storage System and the Local
Storage System Is Changed?..................................................................................................................................................167
11.15 After a LUN Is Mapped from a Heterogeneous Storage System to the OceanStor Dorado V6 series
Storage System (Local Storage System), Why an Unnecessary Remote LUN Can Be Viewed on the
DeviceManager Management Page of the Local Storage System?......................................................................... 167
11.16 Why Are Services Interrupted When the reboot Command Is Executed to Restart One Controller of
NetApp FAS8000 Storage System?...................................................................................................................................... 168
11.17 How Do I Add A Heterogeneous Device to the Whitelist?............................................................................. 168
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. viii

OceanStor Dorado
11.18 Why Is a Logical Path Whose Status is Degraded Found When eDevLUNs Are Scanned After
Huawei VIS6000/VIS6000T Storage Systems Are Taken Over................................................................................... 171
11.19 How Is Load Balancing Implemented for SmartVirtualization?.................................................................... 171
11.20 How Can I Delete the Heterogeneous Disks from the Application Server?..............................................173
12 Troubleshooting................................................................................................................ 178
12.1 The Link Becomes Abnormal After an HP MSA2012FC/MSA2212FC Storage System Enables the
Internal Switch Mechanism.................................................................................................................................................... 179
12.2 After an HP P6500 Storage System Is Powered On After a Power Failure, eDevLUNs for External
LUNs Are Still In the Fault State on DeviceManager for the Local Storage System.......................................... 180
12.3 A Local Storage System Encounters a Power Failure and Cannot Detect External LUNs.......................180
12.4 The DeviceManager Cannot Display Remote Device Information or Remote LUN Information After a
Heterogeneous Storage Systems Is Connected to the Local Storage System...................................................... 181
12.5 When the Physical Connection Is Changed Between NetApp FAS3000/FAS6000/FAS8000 Series/EMC
XtremIO/NetApp AFF8000 Series/NetApp E Series/TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/DX200
S3/DX500 S3/DX600 S3 and the Local Storage System, the Link Is Down............................................................182
12.6 The Local Storage System Cannot Be Connected to OceanStor S2600/5300/5500/5600/S6800E
Heterogeneous Storage System If a SmartIO or 16 Gbit/s Fibre Channel (Two Ports) Module Is
Configured for the Local Storage System......................................................................................................................... 183
12.7 Restarting a VMware ESX VM Fails After Online Migration Is Complete.................................................... 185
13 Configuration Restrictions.............................................................................................. 186

13.1 General Restrictions........................................................................................................................................................ 187
13.2 Compatibility Requirements for an Online Takeover.......................................................................................... 192
13.3 Dell Compellent SC Series............................................................................................................................................. 196
13.4 EMC CLARiiON/Fujitsu CX Series................................................................................................................................ 197
13.5 EMC DMX Series............................................................................................................................................................... 198
13.6 EMC VMAX Series............................................................................................................................................................ 198
13.7 EMC VNX/EMC VNX2 Series......................................................................................................................................... 199
13.8 EMC VPLEX......................................................................................................................................................................... 199
13.9 EMC XtremIO..................................................................................................................................................................... 200
13.10 Fujitsu DX60/80/90....................................................................................................................................................... 200
13.11 Fujitsu DX60 S2.............................................................................................................................................................. 202
13.12 Fujitsu E4000 Model 80/100...................................................................................................................................... 204
13.13 Fujitsu E8000 Model 1200/2200/Inspur AS5600................................................................................................ 207
13.14 HDS AMS2000/HDS HUS 100 Series...................................................................................................................... 209
13.15 HDS AMS/WMS Series................................................................................................................................................. 209
13.16 HDS USP/NSC Series/HDS USP-V/USP-VM/SUN 9985/9985V/9990/9990V/HP SVS200/
XP10000/12000/20000/24000............................................................................................................................................... 210
13.17 HDS HUS VM.................................................................................................................................................................. 210
13.18 HDS VSP G200/G400/G600/G800/G1000/HP XP7............................................................................................. 210
13.19 Huawei Storage System.............................................................................................................................................. 211
13.19.1 Huawei S12100/S12300........................................................................................................................................... 211
13.19.2 Huawei S3000............................................................................................................................................................. 213
13.19.3 Huawei VIS6000/VIS6000T..................................................................................................................................... 213
13.19.4 Other Types of Huawei Storage Systems...........................................................................................................213
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. ix

OceanStor Dorado
13.20 HP EVA Series..................................................................................................................................................................215

13.21 HP MSA1040/MSA2040............................................................................................................................................... 216
13.22 HP MSA2012FC/MSA2212FC..................................................................................................................................... 216
13.23 HP MSA2312FC/MSA2324FC..................................................................................................................................... 216
13.24 HP P2000 Series............................................................................................................................................................. 217
13.25 HP 3PAR Series............................................................................................................................................................... 217
13.26 IBM DS3XXX/IBM DS4XXX/IBM DS5XXX Series/Sugon DS800-G10/DS800-G20/NetApp E series/
Inspur AS1000G6/DCS 3700/Dell PowerVault MD Series/TOYOU iSUM780/iSUM850.....................................218
13.27 IBM DS6000 Series........................................................................................................................................................ 218
13.28 IBM DS8000 Series........................................................................................................................................................ 219
13.29 IBM SVC/V3500/V3700/V5000/V7000/Inspur AS8000-M1/AS8000-M3..................................................... 219
13.30 IBM XIV Series................................................................................................................................................................. 219
13.31 NetApp FAS2000/FAS3000/V3000/FAS6000/V6000/FAS8000/AFF8000 Series And IBM N3000/N6000
Series.............................................................................................................................................................................................. 220
13.32 Oracle SUN StorageTek 2540.................................................................................................................................... 221
13.33 Oracle SUN Storage6000 Series............................................................................................................................... 221
13.34 TMS RamSan Series...................................................................................................................................................... 221
13.35 Application Servers and Management Nodes..................................................................................................... 221
13.35.1 ESXi 5.X VMs................................................................................................................................................................ 221
13.35.2 Windows Server 2012/Windows Server 2008...................................................................................................222
13.35.3 VCS Cluster................................................................................................................................................................... 222
A How to Obtain Help...........................................................................................................223

A.1 Preparations for Contacting Huawei........................................................................................................................... 223
A.1.1 Collecting Troubleshooting Information................................................................................................................. 223
A.1.2 Making Debugging Preparations.............................................................................................................................. 223
A.2 How to Use the Document............................................................................................................................................. 224
A.3 How to Obtain Help from Website..............................................................................................................................224
A.4 Ways to Contact Huawei................................................................................................................................................. 224
B Glossary................................................................................................................................. 225
C Acronyms and Abbreviations........................................................................................... 239
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. x

OceanStor Dorado
SmartVirtualization Feature Guide 1 Feature Description
1 Feature Description
The SmartVirtualization feature enables Huawei OceanStor Dorado V6 series to

take over and centrally manage the storage resources of heterogeneous storage
systems. By working together with SmartMigration, data in the heterogeneous
storage systems can be migrated in online mode. After the migration, OceanStor
Dorado V6 series will carry services. This chapter describes the SmartVirtualization
feature and is organized into five sections: introduction, license requirements and
compatible products, working principle, impact and restrictions, and application
scenarios.
1.1 Introduction
1.2 License Requirements and Compatible Products
1.3 Working Principle
1.4 Impact and Restrictions
1.5 Application Scenarios
1.1 Introduction
This section describes the background, definition, and benefits of
SmartVirtualization.
Background
With an ever-increasing amount of user data, how to properly manage and
expand storage systems becomes important, and the following issues must be
addressed:
● If a user wants to buy a new storage system to replace an existing storage

system, service data must be migrated from the existing system to the new
storage system. The incompatibility between different storage systems may
cause a long data migration period or even a migration failure.
● If a user purchases a new storage system and manages multiple storage
systems in a decentralized manner, the maintenance cost increases and
storage resources of these storage systems cannot be effectively consolidated
or managed as the number of storage systems increases.
Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. 1

OceanStor Dorado
Using SmartVirtualization can address the previous issues. Physical attributes of

different storage systems are masked to achieve easy configuration and
management and efficient storage resource usage.
Definition
SmartVirtualization is a heterogeneous virtualization feature developed by
Huawei. When a local storage system (OceanStor Dorado V6 series storage
system) is connected to another type of Huawei storage system or a third-party
storage system, this feature enables the local storage system to use and manage
storage resources of the peer storage system as local storage resources despite of
the different software and hardware architectures.
SmartVirtualization resolves the incompatibility issues among different storage
systems, so users can manage heterogeneous storage systems and use storage
resources from both legacy and new storage systems, protecting customer
investments.
NOTE
SmartVirtualization allows you to manage storage resources on heterogeneous storage

systems, but you cannot perform any configuration operation on the heterogeneous storage
systems.
SmartVirtualization has the following advantages:

● Excellent compatibility: The local storage system is compatible with
mainstream heterogeneous storage systems, helping achieve centralized
storage resource planning and management.
● Low storage space occupation: When a local storage system uses the storage
space provided by LUNs in a heterogeneous storage system (external LUNs for
short), the local storage system does not generate complete copies for
physical data, so the storage space of the local storage system will not be
wasted.
● Diversified value-added functions: In addition to using external LUNs as local
storage resources, a local storage system can configure value-added functions
such as SmartMigration for these LUNs to ensure high security and reliability
of service data.
Heterogeneous storage systems can be taken over in either online or offline mode.
Benefits
Table 1-1 describes the benefits provided by SmartVirtualization.

OceanStor Dorado
Table 1-1 Benefits
Benefit Description
Resolving the incompatibility issues SmartVirtualization resolves the

among different storage systems and incompatibility issues among different
simplifying storage management storage systems, so users can directly
use a local storage system to manage
heterogeneous storage resources
without performing operations in
these systems one by one.
Integrating storage space and After using SmartVirtualization, you

simplifying space allocation can enable a local storage system to
take over storage resources of a
heterogeneous storage system and use
the local storage system to manage
and allocate storage space of the
heterogeneous storage system,
simplifying space allocation across
different storage systems and
consolidating storage resources of
multiple storage systems.
1.2 License Requirements and Compatible Products

This section describes the license requirements, compatible products, and
specifications of SmartVirtualization.
License Requirements
SmartVirtualization is a value-added feature that requires a license. If the
heterogeneous storage system is a third-party device, you need a license for
SmartVirtualization in the local storage system. If the heterogeneous storage
system is a Huawei device (not including OEM devices), you do not need a license
for SmartVirtualization.
NOTE
To obtain a license, contact your local Huawei representative office or Huawei authorized
distributor.
Compatible Products
Product Series Model Version
OceanStor Dorado V6 Dorado 3000 V6 6.0.0

series
Dorado 5000 V6 6.0.0
Dorado 6000 V6 6.0.0

OceanStor Dorado
Product Series Model Version
Dorado 8000 V6 6.0.0
Dorado 18000 V6 6.0.0
Specifications
SmartVirtualization specifications depend on the product model. For detailed
specifications, refer to the Specifications Query Assistant (http://support-
it.huawei.com/spec/#/home).
1.3 Working Principle

SmartVirtualization allows external LUNs in heterogeneous storage systems to
provide physical storage space for the OceanStor Dorado V6 series storage
systems.
Basic Concepts
● Local storage system
A local storage system refers to OceanStor Dorado V6 series storage system.
● Heterogeneous storage system
In SmartVirtualization, a heterogeneous storage system can be either a
storage system manufactured by another mainstream vendor or a Huawei
storage system of a specific model. For details, see Table 1-2. A
heterogeneous storage system is displayed as an external device on the
DeviceManager.
● External LUN
A LUN in a heterogeneous storage system, also called remote LUN.
● eDevLUN
In the storage pool of a local storage system, the mapped external LUNs are
reorganized as raw storage devices based on a certain data organization form.
A raw device is called an eDevLUN. The physical space occupied by an
eDevLUN in the local storage system is merely the storage space needed by
the metadata. The service data is still stored on the heterogeneous storage
system. Application servers can use eDevLUNs to access data on external
LUNs in the heterogeneous storage system, and the SmartMigration feature
can be configured for the eDevLUNs.
● Online takeover: During the online takeover process, services are not
interrupted, ensuring service continuity and data integrity. In this mode, the
critical identity information about heterogeneous LUNs is masqueraded so
that multipathing software can automatically identify new storage systems
and switch I/Os to the new storage systems. This remarkably simplifies data
migration and minimizes time consumption.
● Offline takeover: During the offline takeover process, connections between
heterogeneous storage systems and application servers are down and services

OceanStor Dorado
are interrupted temporarily. This mode is applicable to all compatible Huawei

and third-party heterogeneous storage systems.
● Hosting
LUNs in a heterogeneous storage system are mapped to a local storage
system for use and management.
Relationship Between an eDevLUN and an External LUN

An eDevLUN consists of data and metadata. A mapping relationship is established
between data and metadata.
● The physical space needed by data is provided by the external LUN from the
heterogeneous storage system. Data does not occupy the capacity of the local
storage system.
● Metadata is used to manage storage locations of data on an eDevLUN. The
space used to store metadata comes from the metadata space in the storage
pool created in the local storage system. Metadata occupies merely a small
amount of space. Therefore, eDevLUNs occupy a small amount of space in the
local storage system. (If no value-added feature is configured for eDevLUNs,
each eDevLUN occupies only dozens of KBs in the storage pool created in the
local storage system.)
NOTE
If value-added features are configured for eDevLUNs, each eDevLUN, like any other local
LUNs, occupies local storage system space to store the metadata of value-added features.
Properly plan storage space before creating eDevLUNs to ensure that value-added features
can work properly.
Figure 1-1 illustrates the relationship between an eDevLUN created in the local
storage system and an external LUN created in the heterogeneous storage system.
An application server accesses an external LUN by reading data from and writing
data to the corresponding eDevLUN.
Figure 1-1 Relationship between an eDevLUN and an external LUN

Application server
Mapping 1
eDevLUN 1
Mapping n
eDevLUN n
External External
Metadata 1 Metadata n
LUN1 LUN n
Storage pool Storage space
Local storage Heterogeneous

system storage system
Metadata space
Data space
Mapping
Read and write I/O

OceanStor Dorado
Data Read and Write Processes

With the use of SmartVirtualization, an application server can read data from and
write data to an external LUN in a heterogeneous storage system through the
local storage system. The entire process is similar to the process of reading data
from and writing data to a LUN in the local storage system.
● Data read process
After an external LUN in a heterogeneous storage system is hosted using
SmartVirtualization, when an application server sends a request to read data
from the external LUN, the eDevLUN in the local storage system receives the
request and reads data from the external LUN, as shown in Figure 1-2.
Figure 1-2 Data read process

Application server
Data read request

Data flow
Physical cable
eDevLUN 2 External
LUN

1 The application server sends a data read request.
2 The eDevLUN of the local storage system receives the

request and reads data from the external LUN.
3 Data is returned to the local storage system and then
the application server.
● Data write process

After an external LUN in a heterogeneous storage system is hosted using
SmartVirtualization, the write process is shown in Figure 1-3.

OceanStor Dorado
Figure 1-3 Data write process

Application server
Data write request

Data flow
Physical cable
1 4
eDevLUN 2 External
LUN

1 The application server writes data into the local storage system.
The local storage system writes the data into the heterogeneous
2 storage system.
3 The heterogeneous storage system sends the write success

message to the local storage system.
4 The local storage system sends the write success message to
1.4 Impact and Restrictions

This section describes the impact of SmartVirtualization on system performance
and other restrictions.
Compatibility
Heterogeneous storage systems supported by SmartVirtualization can be Huawei
storage systems and other third-party storage systems from mainstream vendors.
Use the Huawei Storage Interoperability Navigator to check models of
compatible Huawei storage systems and other mainstream vendors' storage
systems.
NOTICE
Storage systems that are not in the Huawei Storage Interoperability Navigator
are incompatible heterogeneous storage systems. You are advised not to connect
incompatible heterogeneous storage systems to a local storage system for
takeover because incompatibility issues may occur. When you want to connect an
incompatible heterogeneous storage system to a local storage system to meet
service requirements, contact Huawei technical support.

OceanStor Dorado
Table 1-2 lists the connection methods between a local storage system and a
compatible heterogeneous storage system.
Table 1-2 Connection methods between a local storage system and a compatible
heterogeneous storage system
Heterogeneous Storage System Connection Method
OceanStor Dorado3000 V3/Dorado5000 V3/ Fibre Channel or iSCSI

Dorado6000 V3/Dorado18000 V3 storage system connection
OceanStor 2600 V3 storage system (video

surveillance edition)
OceanStor 18500/18800/18800F/18500 V3/18800

V3/18500F V3/18800F V3 storage system
OceanStor 2200 V3/2600 V3/2600F V3 storage

system
OceanStor 5300 V3/5500 V3/5600 V3/5800

V3/6800 V3/6900 V3/5500F V3/5600F V3/5800F
V3/6800F V3 storage system
OceanStor S2200T/S2600T/S5500T/S5600T/
S5800T/S6800T storage system
OceanStor S2900/S3900/S5900/S6900 storage

system
OceanStor S2600 storage system
OceanStor S5300/S5500/S5600 storage system
OceanStor S6800E storage system
OceanStor S3100/S3200/S6800 storage system Fibre Channel connection
Storage devices from mainstream vendors (for Fibre Channel connection

example, IBM DS4700 and EMC CX4-240) NOTE
The 8 Gbit/s Fiber Channel
interface module (four ports)
cannot be used to take over
storage devices from other
vendors.
If you create masqueraded eDevLUNs to take over a heterogeneous storage

system non-disruptively, the operating system of your application server,
multipathing software, and cluster software must meet compatibility
requirements.
● To check whether a Huawei heterogeneous storage system can be taken over,

see Table 13-4.
● To check whether a third-party heterogeneous storage system can be taken
over, see Table 13-5.

OceanStor Dorado
1.5 Application Scenarios

SmartVirtualization resolves incompatibility issues among different storage
systems. Therefore, it is applicable to a variety of scenarios, such as service data
migration and storage resource management across storage systems.
Centralized Management of Storage Resources

If multiple heterogeneous storage systems have been deployed onsite, the
following two challenges may occur:
● Due to incompatibility issues, multipathing software on an application server

may not be compatible with all heterogeneous storage systems.
● In a certain network environment (such as a Fibre Channel direct-connection
network), one application server can only be connected to one storage
system. However, in actual applications, one application server needs to
distribute services to multiple storage systems.
SmartVirtualization functions similarly to virtual gateways. SmartVirtualization

allows you to discover storage resources in multiple heterogeneous storage
systems from the local storage system, and deliver read and write commands to
the storage resources for centralized management.
The local storage system uses eDevLUNs to manage storage resources in

heterogeneous storage systems, as shown in Figure 1-4.
Figure 1-4 Centralized storage resource management based on

SmartVirtualization
eDevLUN 1
I/O
I/O
Mapping Heterogeneous
storage system 1
Local storage I/O

Application I/O system
server
Mapping
eDevLUN n
Heterogeneous
storage system 2
The OceanStor Dorado V6 series storage system can centrally manage resources of
heterogeneous storage systems in two ways, as shown in Figure 1-5.
● Offline takeover
Connections between a heterogeneous storage system and an application
server are down and services are interrupted temporarily.
● Online takeover

OceanStor Dorado
Connections between a heterogeneous storage system and an application

server are not down and services are not interrupted, ensuring service
continuity and data integrity. You can set the masquerading properties of
eDevLUNs to implement an online takeover.
Figure 1-5 Takeover process

eDevLUNs without LUN masquerading properties eDevLUNs with LUN masquerading properties
Read and write I/Os
Step 3 Disconnect the

Step 2 Disconnect the application application server from the
Step 3 Connect the application Step 2 Connect the application server
server from the heterogeneous heterogeneous storage
server to the local storage to the local storage system and then
storage system to stop data system. Data transfer
system and enable the local the application server can identify the
transfer and services. interruption does not affect
storage system to take over masqueraded eDevLUNs.
services.
services.
Heterogeneous Local storage Heterogeneous Local storage
storage system system storage system system
Mapping relationship Mapping relationship

(SmartVirtualization) (SmartVirtualization)
Step 1 Connect the local storage system to the

Step 1 Connect the local storage
heterogeneous storage system and enable the local storage
system to the heterogeneous
system to take over data services from the heterogeneous
storage system.
storage system.
Service Data Migration Between Storage Systems

● Migrating service data from a legacy storage system to a new storage system
As services grow continuously, more storage is required for storing increasing
data. The legacy storage system cannot provide satisfactory data storage
capacity and performance. In this case, you can purchase a storage system
that provides a larger capacity and better performance to replace the legacy
storage system. As software and hardware of the legacy and new storage
systems are different, the services may be interrupted and data may be lost
during data migration. SmartVirtualization can mask the differences between
storage systems to map an external LUN of the legacy storage system to the
new storage system (presented as an eDevLUN on the new storage system).
Then SmartMigration can be used to reliably migrate all service data from the
legacy storage system to the new storage system while keeping services
running. Figure 1-6 shows data migration from a legacy storage system to a
new storage system.
Figure 1-6 Migrating data from a legacy storage system to a new storage
system
LUN
New storage Legacy storage
system system
Data migration
(SmartMigration)
Mapping (SmartVirtualization)
eDevLUN External
LUN

OceanStor Dorado
NOTE
In this application scenario, a new storage system and a legacy storage system serve as a
local storage system and a heterogeneous storage system respectively.
● Migrating cold data from a new storage system to a legacy storage system
After a legacy storage system is replaced with a new storage system, some
data in the new storage system is rarely accessed, which is called cold data. If
massive cold data is stored in the new storage system, the storage resource
utilization of the storage system lowers down, causing a waste of storage
space. To reduce operation expenditure (OPEX), SmartVirtualization can work
with SmartMigration to migrate the cold data to the legacy heterogeneous
storage system. Figure 1-7 shows data migration from a new storage system
to a legacy storage system.
Figure 1-7 Migrating cold data from a new storage system to a legacy
storage system
LUN
New storage Legacy storage
system system
Data migration
(SmartMigration)
Mapping (SmartVirtualization)
eDevLUN External
LUN
NOTE
In this application scenario, a new storage system and a legacy storage system serve as a
local storage system and a heterogeneous storage system respectively.

OceanStor Dorado
SmartVirtualization Feature Guide 2 Selecting a Takeover Mode
2 Selecting a Takeover Mode
SmartVirtualization provides online and offline modes to take over heterogeneous

storage systems. There are three masquerading types for online takeover, which
are basic masquerading, extended masquerading, and third-party masquerading.
The takeover mode depends on the vendors and versions of the heterogeneous
storage systems and multipathing software.
NOTE
When creating an eDevLUN on DeviceManager, you can set Takeover Type to Offline or
Online.
If you select Offline, the masquerading property automatically configured for eDevLUNs is
No masquerading.
If you select Online, the masquerading property automatically configured for eDevLUNs is
Basic masquerading or Third-party based on whether the heterogeneous storage system
is a Huawei or third-party storage system. If you want to use Extended masquerading for
takeover, run the create lun_takeover general command on the CLI.
Offline Takeover
The offline takeover mode is applicable to all compatible Huawei and third-party
heterogeneous storage systems. In this mode, services running on the related
application servers are stopped temporarily and the masquerading property for
eDevLUNs is No masquerading.
Online Takeover
When a Huawei heterogeneous storage system is taken over in online mode, the
masquerading property for eDevLUNs is Basic masquerading or Extended
masquerading. The selection of basic masquerading or extended masquerading
depends on the vendor and version of the multipathing software and the versions
of Huawei heterogeneous storage systems. Figure 2-1 shows how to select a
takeover mode.
WARNING
The online takeover procedure is complex and involves high-risk operations.

Contact the data migration service team to evaluate and implement a migration
solution.

OceanStor Dorado
SmartVirtualization Feature Guide 2 Selecting a Takeover Mode
Figure 2-1 Selecting a takeover mode
Other Huawei storage

systems
Online takeover
Using multipathing
Using UltraPath software from other
vendors
The UltraPath version is

The UltraPath version is
earlier than
V100R008C20 or later.
V100R008C20.
The storage system The storage system SN

SN can be queried cannot be queried using
using UltraPath. UltraPath.
Extended masquerading
Basic masquerading is
is configured for
configured for eDevLUNs.
eDevLUNs.
Models and versions of storage systems whose SNs cannot be queried using
UltraPath:
● S2300E/S2600
● S5300/S5500/S5600
● Dorado2100
● Dorado5100 of versions earlier than V100R001C00SPC800 (excluding
V100R001C00SPCa00 and V100R001C00SPCb00)
● Dorado2100 G2 of versions earlier than V100R001C00SPC500 (excluding
● S2200T/S2600T/S5500T/S5600T/S5800T/S6800T of versions earlier than
V1R5C00SPC400
● S2200T/S2600T/S5500T/S5600T/S5800T/S6800T of versions earlier than
V1R5C01SPC100
When a third-party heterogeneous storage system is taken over in online mode,
the masquerading property for eDevLUNs is Third-party. Huawei storage systems
can take over third-party storage systems only when application servers use the
native multipathing software of operating systems, and the multipathing software
that can take over Huawei storage systems, such as Huawei UltraPath, Symantec
SF DMP, and Veritas Storage Foundation, is not used. Only certain operating
systems and cluster software are supported. For details about supported operating
systems and cluster software, see 13.2 Compatibility Requirements for an
Online Takeover.

OceanStor Dorado 3 Taking Over Huawei Heterogeneous Storage
SmartVirtualization Feature Guide Systems in Offline Mode
3 Taking Over Huawei Heterogeneous

Storage Systems in Offline Mode
If the offline takeover function is configured, you can use the OceanStor Dorado
V6 series storage system (local storage system) to take over LUNs of a
heterogeneous storage system to achieve data migration and service takeover
after you temporarily suspend host services. This chapter describes how to take
over Huawei heterogeneous storage systems in offline mode.
3.1 Configuration Process
3.2 Checking a License File
3.3 Installation and Deployment
3.4 Configuring the Logical Connection Between the Heterogeneous Storage
System and Local Storage System
3.5 Configuring and Using an eDevLUN

Before configuring SmartVirtualization for centralized storage resource
management and taking over Huawei heterogeneous storage systems in offline
mode, learn about the configuration process to ensure a smooth configuration.
Figure 3-1 shows the configuration process.

Figure 3-1 Process for configuring SmartVirtualization for offline takeover

Start
1. Check the Skip this operation if

availability of the heterogeneous storage systems
SmartVirtualziation
Check the license file. are Huawei storage systems
function. (non-OEM ones).
2. Establish a physical
connection between the Install and deploy
heterogeneous storage
system and local storage application servers and
system. storage systems.
3. Establish a logical
connection between the
Fibre
system and local storage Channel iSCSI
system and scan for LUNs. connection connection
Perform this operation when the local and
heterogeneous storage systems are connected over
Configure the heterogeneous Add routes. an iSCSI network and data needs to be transmitted
storage system. across different network segments.
Add an external storage

system.
Configure the heterogeneous

storage system.
Scan for external LUNs. Scan for external LUNs.
Create an eDevLUN.
4. Centrally manage the
heterogeneous storage Configure and use an
system using eDevLUNs. eDevLUN.
Map the eDevLUN to the host.
End Mandatory Mandatory Optional Optional

item sub-item item sub-item
NOTE
Configure SAN services on DeviceManager. For details on how to log in to DeviceManager,

see "Logging In to DeviceManager" in the Basic Storage Service Configuration Guide for
Block corresponding to your product model.

Each value-added feature requires a license file for activation. Before configuring a
value-added feature, ensure that its license file is valid for the feature.
Context
● The heterogeneous virtualization feature is displayed as SmartVirtualization
in the Feature column on DeviceManager.
● When the heterogeneous storage system is a Huawei storage system (non-
OEM ones), no license is required.
Procedure
Step 1 Log in to DeviceManager.

Step 2 Choose Settings > License Management.

Step 3 In the middle function pane, view active license files.
----End
Follow-up Procedure
● If the information about the license of the feature is not displayed, you must
apply for, import and activate a license file. For details about how to apply for,
import and activate a license file, see Initialization Guide of the corresponding
product model.
You can log in to Huawei's technical support website (https://
support.huawei.com/enterprise/) and enter the product model + document
name in the search box to search for, browse, and download the desired
documents.
● If an alarm is generated in the storage system, indicating that the license has
expired, apply for, import and activate a new one.

Before using SmartVirtualization to centrally manage storage resources, connect
the local storage system to the heterogeneous storage system.
Precautions
Suspend services running on application servers before connecting the local
storage system to the heterogeneous storage system. To prevent system services
from being affected, install and deploy storage systems when no services are
running.
Network Planning
The network between a local storage system and a heterogeneous storage system
can be a standard direct-connection network or a standard switch-connection
network. Select an appropriate network based on onsite requirements. Table 3-1
lists the possible networking diagrams between a local storage system and a
heterogeneous storage system.

Table 3-1 Networking diagrams between a local storage system and a

Network Networking Principle Networking Diagram
Type
Standard A crossed networking mode is

direct- adopted to ensure link
connection redundancy, that is, each
network controller in the local storage
system is connected to that in
the heterogeneous storage
system through one link.
Standard ● A crossed networking

switch- mode is adopted to ensure
connection link redundancy, that is,
network each controller in the local
storage system is
connected to that in the
system through two links.
● When a standard switch-
connection network is
adopted, use different
ports on the local storage
system to connect the
system and application
server.
● If Fibre Channel switches
are deployed on the
network, ensure that the
local storage system's
front-end ports used to
connect to the
system and the front-end
ports used to connect to
application servers reside
in different zones.

NOTE
● The total specification for paths of the external LUNs is limited (Total specification =
Maximum path number supported by each external LUN x Number of external LUNs
supported by a storage system). If an external LUN connects to more paths than the
maximum number of paths supported by each external LUN, the access of other
external LUNs will be affected.
● When connecting a local storage system to a heterogeneous storage system, do not
share ports with the HyperMetro service, remote replication service, or any host.
Cable Connection
If SmartVirtualization is used to centrally manage storage resources, connect
cables between a local storage system and a heterogeneous storage system as
follows:
1. Use optical fibers or network cables to connect the service ports of the local
storage system to those of the heterogeneous storage system.
Figure 3-2 shows the cable connections.
Figure 3-2 Connections between a local storage system and a heterogeneous

storage system
Heterogeneous storage system
Application server
Local storage system

Original cable
New cable
NOTE
During cable connection, reads and writes of service data in the heterogeneous
storage system are not interrupted.
2. Stop services running on application servers.
3. Disconnect the application servers from the heterogeneous storage system.

4. Use optical fibers or network cables to connect the host ports of the
application servers to the service ports of the local storage system.
Figure 3-3 Connections between the local storage system and an application
server
Application server Heterogeneous storage system

Original cable
New cable
Removal
Follow-up Procedure
● Optional: Upgrade UltraPath. For details about how to do so, see the upgrade
guide of the corresponding version.
● If optical fibers are used to connect a local storage device to a remote storage
device, the local storage device automatically identifies the remote links. After
the remote storage device is disconnected from the local storage device, the
remote links disappear.
NOTE
After mapping external LUNs to the local storage system as instructed in 3.4.1.1
Configuring a Heterogeneous Storage System, implement full automatic scanning for
LUNs. Then, the remote device that corresponds to the heterogeneous storage system can
be discovered in DeviceManager of the local storage system.
● If network cables are used to connect the local storage device to the remote
storage device, perform the operations in 3.4.2.2 Adding an External Storage
Device so that the local storage device can identify the remote links.

3.4 Configuring the Logical Connection Between the

Heterogeneous Storage System and Local Storage
System
When you use SmartVirtualization to centrally manage storage resources, you
must establish logical connections between the local storage system and the
heterogeneous storage system, map external LUNs to the local storage system,
and scan for the remote LUNs on the local storage system.
3.4.1 Fibre Channel Connection

This section introduces how to establish logical connections between a
heterogeneous storage system and a local storage system and how to scan for
LUNs on the local storage system, when Fibre Channel connection is adopted
between the two storage systems.
3.4.1.1 Configuring a Heterogeneous Storage System

When using SmartVirtualization to centrally manage storage resources, configure
the heterogeneous storage systems and establish mappings between the local
storage system and heterogeneous storage systems, so that external LUNs can be
identified on the local storage system.
After connecting to the local storage system, the heterogeneous storage system
regards the local storage system as a host. Only after a mapping is established
between external LUNs on the heterogeneous storage system and the host, the
local storage system can identify the LUNs mapped from the heterogeneous
storage system.
Configuration operations vary depending on heterogeneous storage systems. For

details, see the related operation guide.
NOTE
Comply with related configuration restrictions when configuring heterogeneous and local
storage systems to ensure that SmartVirtualization can be used to take over LUNs from
heterogeneous storage systems after the local storage system is connected to the
heterogeneous storage systems. For details, see 13 Configuration Restrictions.
3.4.1.2 Scanning for External LUNs

After scanning, LUNs mapped from the external storage device to the local
storage device can be connected to the local storage device.
Prerequisites
● An external storage device has been added.
● LUNs of the external storage device have been mapped to the local storage
device.

Procedure
Step 1 Choose System > External Storage.
Step 2 Select an external storage device and click Scan for External LUN.
The system will automatically scan for LUNs and links mapped by the external
storage system. The scanning will last for dozens of seconds.
Step 3 Click OK. The system automatically scans for LUNs.
----End
3.4.2 iSCSI Connection

LUNs on the local storage system, when iSCSI connection is adopted between the
two storage systems.
3.4.2.1 Managing Logical Ports

This section describes how to manage logical ports. A logical port is created based
on an Ethernet port, a bond port, or a VLAN.
Precautions
It is recommended that you create no more than 64 logical ports for each
controller. If more than 64 logical ports are created for one controller, the logical
ports will fail over to a few available physical ports in the event that a large
number of physical ports fail, decreasing service performance.
Procedure
Step 1 Choose System > Hardware.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
Step 3 Click to switch to the rear view.
Step 4 Select the Ethernet port you want to configure.
Step 5 Click Manage Logical Port.
The Manage Logical Port page is displayed.
Step 6 Create, modify, or delete logical ports on the Ethernet port and manage their
route information as required.
● To create a logical port:
a. Click Create.
The Create Logical Port page is displayed.
b. Set the parameters listed in Table 3-2.

Table 3-2 Logical port parameters

Parameter Description
Port Type Type of the logical port to be created.
Home Port Home port on which the logical port is created.
Name Name of the logical port.

The name must meet the following requirements:
▪ The name must be unique.
▪ The name contains only letters, digits, periods (.),

underscores (_), and hyphens (-).
▪ The name contains 1 to 31 characters.
IP Address Type IP address type of the logical port, which can be

IPv4 or IPv6.
IP Address IPv4 or IPv6 address of the logical port.
Subnet Mask Subnet mask of the logical port's IPv4 address.

NOTE
This parameter is available only when IP Address Type is
set to IPv4.
Prefix Prefix length of the logical port's IPv6 address.

NOTE
set to IPv6.
Gateway Gateway of the logical port's IP address.
c. Click OK.
● To manage route information:
a. Select the desired logical port and click Manage Route.
The Manage Route page is displayed.
NOTE
You can also click on the right of the logical port and choose Manage Route.
b. Configure the route information for the logical port.
i. In the IP Address drop-down list, select the IP address of the logical
port for which you want to add a route.
ii. Click Add.
iii. Set the parameters listed in Table 3-3.

Table 3-3 Route parameters
Paramet Description
er
Type Three types of routes are available:

○ Default route
A route through which data is forwarded by default
if no preferred route is available. The destination
address and mask (IPv4) or prefix (IPv6) of the
default route are automatically set to 0. To use this
option, you only need to add a gateway.
○ Host route
A route to a host. The destination mask (IPv4) or
prefix (IPv6) of the host route is automatically set to
255.255.255.255 or 128. To use this option, you only
need to add the destination address and gateway.
○ Network segment route
A route to a network segment. You must add the
destination address, destination mask (IPv4) or
prefix (IPv6), and gateway.
Destinati IPv4 address, IPv6 address, or network segment of the

on destination service network port on the application
Address server or destination logical port on another storage
system.
Subnet Subnet mask of the IPv4 address or prefix of the IPv6

Mask/ address for the destination service network port on the
Prefix application server or destination logical port on another
storage system.
Gateway Gateway where the local logical port's IP address

resides.
NOTE
The IP address of the gateway must be different from all
internal heartbeat IP addresses. Otherwise, routing will fail.
iv. Click . The route information is added to the list.

NOTE
To delete a route, select it and click .

v. Click Close.
----End
3.4.2.2 Adding an External Storage Device

This section describes how to establish a logical connection between a local
storage device and an external storage device for data transmission.

Procedure
Step 2 Add an external storage device.
● Add an external FC storage device.
Click Add and choose FC. The system will automatically discover external FC
storage devices. This operation will last for dozens of seconds.
● Add an external iSCSI storage device.
a. Click Add and choose iSCSI.
The Add External Storage Device dialog box is displayed.
b. Set up the connection to the external storage device.
i. Set the iSCSI link parameters listed in Table 3-4.
Table 3-4 iSCSI link parameters

Local Port Front-end iSCSI port of the local

storage device.
Remote IP Address IP address of the front-end iSCSI

port on the external storage
device.
ii. (Optional) Enable CHAP Authentication and specify Username and

Password.
NOTE
Before enabling CHAP authentication, ensure that CHAP authentication has

been enabled on the external storage device and the user name and
password have been configured.
c. Click OK.
Confirm your operation as prompted.
----End

storage system.

NOTE

Prerequisites
device.
Procedure
----End

Use SmartVirtualization to map a LUN from a heterogeneous storage system to
the local storage system and use it as an eDevLUN.
3.5.1 Creating an eDevLUN

After an eDevLUN is created, you can map it to an application server or use it to
configure value-added services. eDevLUNs reside in storage pools of the local
storage device.
Prerequisites
● A storage pool has been created on the local storage device.
● LUNs mapped from the external storage device have been added to the
external LUN list after scanning.
● The status of external LUNs is normal.
● The storage pool has sufficient capacity for the eDevLUN to be created.
Precautions
● After creating an eDevLUN for an external LUN, do not map the external LUN
to other hosts or storage devices to avoid data inconsistency.

● If the vStorage APIs for Array Integration (VAAI) or asymmetrical logical unit
access (ALUA) function is enabled on an external LUN of the external storage
device, the storage systems do not support online takeover of the external
LUN.
● Before mapping an external LUN to the local storage device, ensure that no
reserved information exists on the external LUN. Otherwise, the external LUN
cannot be properly taken over by the local storage device, affecting services
on the LUN.
Procedure
Step 2 Click Create eDevLUN.
The Create eDevLUN dialog box is displayed.
Step 3 Create an eDevLUN.

1. Select a storage pool for the eDevLUN to be created.
NOTE
If no storage pool is available, click Create to create one.

2. Specify Takeover Type.
– Offline: Takes over the external storage device in offline mode. Services
will be temporarily interrupted during the takeover process.
– Online: Takes over the external storage device in online mode. During the
takeover process, the basic information such as the WWN of the
eDevLUN will be replaced with the corresponding information of an
external LUN.
3. In External LUN List, select a LUN that you want to configure as an
eDevLUN.
4. Specify the Name for the eDevLUN.
5. Enter related information in Description.
Step 4 Click OK.

NOTE
After the eDevLUN is created, you can choose Storage > LUNs to view and manage the
eDevLUN.
----End
3.5.2 Establishing Mapping Relationships Between eDevLUNs

and the Application Server
After eDevLUNs are mapped to an application server, the latter can identify the
former as readable and writable storage resources, thereby centrally managing
resources of heterogeneous storage systems.

Figure 3-4 Process of establishing mapping relationships between eDevLUNs and

application servers
Start
Create a LUN group.
For application servers running the

Add an initiator. HP-UX operating system, create an
initiator before creating a host.
Create a host.
Create a host group.
Create a mapping Create the mapping relationship

relationship.
between an eDevLUN and the host.
End Mandatory Optional
For details about each step in the process, see the related sections in the basic
storage service configuration guide corresponding to your product and model.
NOTE
You can log in to Huawei's technical support website (https://support.huawei.com/

enterprise/) and enter the product model + document name in the search box to search for,
browse, and download the desired documents.

OceanStor Dorado 4 Taking Over Third-Party Heterogeneous Storage
4 Taking Over Third-Party Heterogeneous

Storage Systems in Offline Mode
If the offline takeover function is configured, you can use the OceanStor Dorado
V6 series storage system (local storage system) to take over LUNs of a
heterogeneous storage system to achieve data migration and service takeover
after you temporarily suspend host services. This chapter describes how to take
over third-party heterogeneous storage systems in offline mode.

Before configuring SmartVirtualization for centralized storage resource
management and taking over third-party heterogeneous storage systems in offline
mode, learn about the configuration process to ensure a smooth configuration.

Figure 4-1 Process for configuring SmartVirtualization for offline takeover
Start
1. Check the availability of

the SmartVirtualziation Check the license file.
function.
2. Establish a
physical connection
between the Install and deploy
heterogeneous application servers and
storage system and storage systems.
local storage system.
3. Establish a logical Fibre Channel connection

connection between
the heterogeneous Configure the
storage system and
local storage system
and scan for LUNs. system.
Scan for external LUNs.
4. Centrally manage
systems using
Create an eDevLUN.
eDevLUNs.
Configure and use an
eDevLUN
Map the eDevLUN to the host.
End
Mandatory Mandatory
item sub-item
NOTE


Each value-added feature requires a license file for activation. Before configuring
the takeover function, ensure that its license file is valid.
Context
The heterogeneous virtualization feature is displayed as SmartVirtualization in
the Feature column on DeviceManager.

Procedure
----End
Follow-up Procedure
product model.
documents.
expired, apply for, import, and activate a new one.

Before using SmartVirtualization to centrally manage storage resources, connect
the local storage system to the heterogeneous storage system.
Precautions
storage system to the heterogeneous storage system. To prevent system services
from being affected, install and deploy storage systems when no services are
running.
Network Planning


Type

Standard ● A crossed networking mode

switch- is adopted to ensure link
network controller in the local
storage system is
adopted, use different ports
on the local storage system
to connect the
server.
are deployed on the
connect to the
application servers reside in
different zones.
NOTE
The total specification for paths of the external LUNs is limited (Total specification =
maximum number of paths supported by each external LUN, the access of other external
LUNs will be affected.

Cable Connection
If SmartVirtualization is used to centrally manage storage resources, connect
cables between a local storage system and a heterogeneous storage system as
follows:
1. Use optical fibers to connect the service ports of the local storage system to
those of the heterogeneous storage system.
NOTE
Only Fibre Channel connections are supported between the local storage system and
the heterogeneous storage system.
Figure 4-2 Connections between a local storage system and a heterogeneous

storage system
Heterogeneous storage system
Application server

Original cable
New cable
NOTE
During cable connection, reads and writes of service data in the heterogeneous
storage system are not interrupted.
2. Stop services running on application servers.
3. Disconnect the application servers from the heterogeneous storage system.
4. Use optical fibers or network cables to connect the host ports of the
application servers to the service ports of the local storage system.

Figure 4-3 Connections between the local storage system and an application
server
Application server Heterogeneous storage system

Original cable
New cable
Removal
Follow-up Procedure
Use optical fibers to connect a local storage device to a remote storage device, the
local storage device automatically identifies the remote links. After the remote
storage device is disconnected from the local storage device, the remote links
disappear.
NOTE
After mapping external LUNs to the local storage system, implement full automatic
scanning for LUNs as instructed in 4.4.2 Scanning for External LUNs. Then, the remote
device that corresponds to the heterogeneous storage system can be discovered in
DeviceManager of the local storage system.

System
and scan for the remote LUNs on the local storage system. When taking over
third-party heterogeneous storage systems, the local storage system must be

connected to heterogeneous storage systems through Fibre Channel. To establish

logical connections, you are only required to map external LUNs to the local
storage system and then perform full automatic scanning.
4.4.1 Configuring a Heterogeneous Storage System

storage system.
NOTE
4.4.2 Scanning for External LUNs

Prerequisites
device.
Procedure
----End



storage device.
Prerequisites
Precautions
LUN.
on the LUN.
Procedure

NOTE

external LUN.
eDevLUN.

Step 4 Click OK.

NOTE
eDevLUN.
----End


application servers
Start
Create a LUN group.

Create a host.

relationship.

NOTE


SmartVirtualization Feature Guide Systems in Online Mode
5 Taking Over Huawei Heterogeneous

Storage Systems in Online Mode
After configuring the online takeover function, you can enable the OceanStor
Dorado V6 series storage system (local storage system) to take over the original
OceanStor storage system (heterogeneous storage system) and complete data
migration and service takeover. This chapter describes how to take over Huawei
heterogeneous storage systems online.
WARNING

solution.
Context
To master GUI-based operations, you are advised to read this document and
practice the operations using the DeviceManager Demo. As a simulation program
of storage system management software, the DeviceManager Demo simulates
configuration and management operations on a storage system.
Precautions
Do not perform the following operations until an online takeover completes.
● Capacity expansion
● Upgrade (including the upgrades of storage systems and UltraPath software)
● Primary/Secondary switchover of a cluster or restart of a node in the cluster
● Array-level UltraPath configuration
5.3 Pre-Configuration Check


5.7 Configuring Host Path Switchover
5.8 Clearing the Path Switchover Property of the eDevLUNs that Are Masqueraded

Before configuring the online takeover function and taking over Huawei
heterogeneous storage systems in online mode, understand the configuration
process to ensure a smooth configuration.

Figure 5-1 Process for configuring online takeover

Start
Skip this operation if heterogeneous

storage systems are Huawei storage
Check the license file. systems (non-OEM ones).
Check the application

server.
Perform a pre-configuration
check. Check the heterogeneous
storage system.
Check the local storage

Install and deploy storage system.
systems.
FC connection iSCSI connection
Perform this operation when the heterogeneous

Configure the and local storage systems communicate with
heterogeneous storage Add a route. each other over iSCSI and across network
segments.
system.
Add an external storage

device.

Configure the
system.
Create eDevLUNs.
Configure and use Map eDevLUNs to an

eDevLUNs. application server.
Scan for eDevLUNs on the

application server.
Check the multipathing

status.
Switch over host paths.

Configure host path
switchover.
Migrate the reserved
information.
Clear the path switchover Confirm the host path

property of the eDevLUNs switchover.
that are masqueraded.
Mandatory Optional Mandatory Optional

End
item item sub-item sub-item
NOTE

Table 5-1 describes specific operations for configuring online takeover, purposes of
the operations, precautions, and devices on which the operations are operated.

Table 5-1 Each step of the configuration process

Configurati Procedure Description Operation
on Process Position
Checking - Before configuring the Local storage

the license online takeover function, system
file ensure that the license file
contains the information
about SmartVirtualization.
NOTE
If heterogeneous storage
systems are Huawei storage
systems (non-OEM storage
systems), no license is
required.
Performing Check the ● Check whether services Application

a pre- application are running properly server
configuratio server. based on service types.
n check ● Check the health
condition of the host
multipathing software
based on the software
type and version.
Check the Check whether the Heterogeneous

heterogeneous heterogeneous storage storage system
storage system. system is running properly.
Check the local Check whether the local Local storage

storage system. storage system is running system
properly.
Connecting - ● Connect physical cables Heterogeneous

cables between the storage system,
heterogeneous storage local storage
system and local storage system, and
system. application
● Connect physical cables servers
between the local
storage system and
application servers.
Establishing Establish Fibre Channel connections.

a logical NOTE
connection You must use Fibre Channel when OceanStor S3100/S3200/S6800 storage
between the systems are taken over.
heterogeneo
Configure a Configure the Heterogeneous
us storage
system and
storage system. system and map the LUNs
local storage
of the storage system to
system
the local storage system.


on Process Position
Enable full Full automatic LUN Local storage

automatic LUN scanning enables all LUNs system
scanning. of the heterogeneous
storage systems that have
been mapped to the local
storage system to be
connected to the local
storage system.
Establish iSCSI connections.
(Optional) Add When the heterogeneous Local storage

a route. storage system and local system
storage system reside on
different network
segments, these two
storage systems can
communicate correctly
using a router.
Add a remote You can discover the Local storage

device. remote device that system
corresponds to the
system in the local storage
system by adding a remote
device.
Configure a Configure the Heterogeneous

storage system. system and map the LUNs
of the storage system to
the local storage system.
Enable You can connect the Local storage

automatic LUN external LUNs in the system
scanning. heterogeneous storage
system to the local storage
system by enabling
automatic LUN scanning.
Configuring Create Create eDevLUNs for Local storage

and using eDevLUNs (with external LUNs in storage system
eDevLUNs masquerading pools of the local storage
property). system and configure the
LUN masquerading
property of the eDevLUNs.


on Process Position
Map eDevLUNs Establish a mapping Local storage

to an application relationship between system
server. eDevLUNs and an
application server so that
the application server can
identify the eDevLUNs.
1. Creating a LUN group:
To achieve convenient
management of
multiple eDevLUNs, add
the eDevLUNs that are
created after the
system is mapped to the
local storage system for
online takeover to a
LUN group.
2. Creating a host and
adding the initiator:
Create a host that
corresponds to the
application server and
establish a logical
local storage system and
application server by
adding the initiator that
corresponds to the
application server's
service port to the local
storage system.
3. Creating a host group:
To achieve convenient
management of
multiple hosts, add
hosts to a host group.
4. Creating a mapping
view: Create a mapping
view and map the
eDevLUNs to the
application server.


on Process Position
Scan for A scan triggers Application

eDevLUNs on multipathing software to server
the application update the information
server. about the paths among the
local storage system,
system, and application
server.
Configuring Check the Check whether newly Application

host path multipathing added paths are identified server
switchover status. on an application server.
Switch over host ● If OceanStor UltraPath Application

paths. whose version is earlier server
than V100R008C20 is
installed on an
application server,
remove the physical
cables between the
server to switch over
host paths.
● If OceanStor UltraPath
whose version is
V100R008C20 or later is
installed on an
application server, run
start migration to
switch over host paths.
● If third-party
multipathing software is
installed on an
application server, see
the document of the
third-party multipathing
software to obtain the
command used for a
host path switchover.
NOTE
Operations may differ in the
case when some
systems are taken over online.
For details, see 13
Configuration Restrictions.


on Process Position
Migrate the Migrate the reserved Local storage

reserved information of a LUN from system
information. the heterogeneous storage
system to the eDevLUN
(that corresponds to the
LUN) created in the local
storage system.
Confirming host Confirm the completion of Local storage

path switchover the host path switchover. system
Clearing the - Clear the path switchover Local storage

path property of the eDevLUNs system
switchover that are masqueraded and
property of convert them into common
the LUNs so that the LUNs can
eDevLUNs be used in other online
that are takeover tasks.
masquerade
d

Each value-added feature requires a license file for activation. Before configuring a
value-added feature, ensure that its license file is valid for the feature.
Context
● The heterogeneous virtualization feature is displayed as SmartVirtualization
in the Feature column on DeviceManager.
● When the heterogeneous storage system is a Huawei storage system (non-
OEM ones), no license is required.
Procedure
----End
Follow-up Procedure
product model.


documents.
expired, apply for, import and activate a new one.

Before configuring the online takeover function, check whether the application
server, heterogeneous storage system, and local storage system work properly to
ensure that the local storage system can smoothly take over services from the
Check Items
Table 5-2 lists the pre-configuration check items.
Table 5-2 Pre-configuration check items

Category Check Item Operation
Applicatio Service running Check the service running status on the

n server status application server.
Version of the Check the version of the multipathing

multipathing software installed on the application
software installed server.
on the application
server
Number and status Check the number and status of the paths
of the paths between the heterogeneous storage
between the system and the application server.
heterogeneous
storage system and
the application
server
IDs and WWNs of Check IDs and WWNs of the LUNs

the LUNs mapped mapped to the application server.
to the application
server
Heteroge Operating status Check the operating status and health

neous and health condition of the heterogeneous storage
storage condition of the system.
system heterogeneous
storage system

Category Check Item Operation
Local Operating status Check the operating status and health

storage and health condition of the local storage system.
system condition of the
local storage system
NOTE
The following operations use an application server with OceanStor UltraPath installed as an
example. If a third-party multipathing software is installed on the application server, see
the operation guide specific to the multipathing software used on site for command details.
● Check the status of services running on application servers.
Check whether services are running properly based on service types. When the
service status is abnormal, restore the services first. For details about the
operations, contact Huawei technical support.
● Check the version of the multipathing software installed on the application
server.
NOTE
Go to the CLI management page of UltraPath before running any multipathing-related

commands. For details, see the UltraPath user guide of your operating system installed on
UltraPath CLI #0 >show version
Software Version : 8.03.XXX
Driver Version : 8.03.XXX
The version information is indicated by Software Version in the command output:

● If Software Version is 8.03.XXX, OceanStor UltraPath V100R008C20 is
installed on the application servers.
● If Software Version is earlier than 8.03.XXX, OceanStor UltraPath of a
version earlier than V100R008C20 is installed on the application servers. If
Software Version is later than 8.03.XXX, OceanStor UltraPath of a version
later than V100R008C20 is installed on the application servers.
NOTE
Use UltraPath of V100R005 or later when Huawei VIS6000/VIS6000T storage systems are
taken over online.
If UltraPath is used and the version is earlier than V100R008C20, some functions
of the local storage system will be unavailable because the UltraPath version is
too early. At the same time, masquerading properties will be configured on
eDevLUNs during online takeover, and some new functions of the local storage
system will not be available. If you do not need to use the new functions, keep the
status quo.
If you will use the new functions, upgrade the UltraPath and modify the
masquerading properties of eDevLUNs to No Masquerading. For details, see
13.19.4 Other Types of Huawei Storage Systems.
Both upgrading the UltraPath whose version is earlier than V100R008C20 and
installation and deployment for an offline takeover require service suspension, and

the eDevLUNs are configured with no masquerading properties during offline

takeover. Therefore, you are advised to upgrade UltraPath first and then perform
installation and deployment for an offline takeover. For details about offline
takeover, see 3 Taking Over Huawei Heterogeneous Storage Systems in Offline
Mode.
● Check the number, information, and status of paths between the

heterogeneous storage system and application server.
UltraPath CLI #0 >show path
-----------------------------------------------------------------------------------------------------------------------
-----
Path ID Initiator Port Array Name Controller Target Port Path State Check State Port
Type Port ID
0 2100001b32053e20 Huawei.Storage48 0B 20184846fb8ca15f Normal --
FC --
1 2100001b32053e21 Huawei.Storage48 0A 200b4846fb8ca15f Normal --
FC --
4 2100001b32055f20 Huawei.Storage48 0B 20194846fb8ca15f Normal --
FC --
5 2100001b32055f21 Huawei.Storage48 0A 20084846fb8ca15f Normal --
FC --
-----------------------------------------------------------------------------------------------------------------------
-----
Note and record the following information:

– Record the number of output records, which is the number of paths
between the heterogeneous storage system and the application server.
– Record the Initiator Port and Target Port of each path.
– If Path State is Normal, the status of the paths between the
heterogeneous storage system and application server is normal.
NOTE
If Path State is not Normal, ensure that the physical connection is normal between the
heterogeneous storage system and application server before performing the following
steps.
● Check the IDs and WWNs of vLUNs mapped to the application server.
UltraPath CLI #0 >show vlun
-----------------------------------------------------------------------------------------------------------------------
------------------------
Vlun ID Disk Name Lun WWN Status Capacity Ctrl(Own/Work)
Array Name Dev Lun ID
0 sdb hl_luntest 630d17e100b33e3900135b9900000024 Normal 1.00GB --/--
Huawei.Storage48 36
1 sdc hl_luntest_2 630d17e100b33e3909eae968000000f2 Normal 1.00GB
--/-- Huawei.Storage48 242
-----------------------------------------------------------------------------------------------------------------------
-------------------------
UltraPath CLI #0 >show vlun id=0
=======================================================
VLUN#0 Information
=======================================================
Disk : sdb
Name : hl_luntest
Status : Normal
Capacity : 1.00GB
Driver : Vendor-specific(DEFAULT)
Product Name : XXXXX
Vendor Name : HUAWEI
Owning Controller : --
Working Controller : --
Num of Paths :2
LUN WWN : 630d17e100b33e3900135b9900000024
Dev Lun ID : --

Array Name : Huawei.Storage48

Controller 0A
Path 0 : Normal
Manual IO Suspension : Off
-------------------------------------------------------
Note and record Vlun ID and Lun WWN in the command output.
● Check the heterogeneous storage system status.
admin:/>show system general
System Name : XXX.Storage

Health Status : Normal
Running Status : Normal
Total Capacity : 2.000TB
SN : 210235G6EHZ0CX0000XX
Location :
Product Model : XXXX
Product Version : VX00R00XCXX
High Water Level(%) : 80
Low Water Level(%) : 30
Time : 2015-04-17/16:51:03 +08:00
NOTE
Based on the model or version of the heterogeneous storage system to be taken over
online, command outputs may be different. For details, see the operation manual of the
● When Health Status and Running Status are displayed as Normal, the
heterogeneous storage system is normal, you can perform subsequent
operations.
● When Health Status and Running Status are not displayed as Normal,
rectify the fault of the heterogeneous storage system, and perform
subsequent steps after ensuring that the heterogeneous storage system
becomes normal.
● Check the local storage system status.
SN : 210235G6EHY0CX0000XX
Location :
Time : 2015-04-17/17:00:03 +08:00
– When Health Status and Running Status are displayed as Normal, the
local storage system is normal, you can perform subsequent operations.
– When Health Status and Running Status are not displayed as Normal,
rectify the fault of the local storage system, and perform subsequent
steps after ensuring that the local storage system becomes normal.
Follow-up Procedure
To ensure that the online takeover function can be used normally, continue
subsequent steps after completing configurations for the application server and
cluster nodes. For details about the restrictions on configurations for the
application server and cluster nodes, see 13.35 Application Servers and
Management Nodes.


This section describes how to deploy and install application servers, a
heterogeneous storage system, and a local storage system when the online
takeover function is configured.
Precautions
storage system to the remote storage system. To prevent system services from
being affected, install and deploy storage systems when no services are running.
If UltraPath is used and the version is earlier than V100R008C20, some functions
of the local storage system will be unavailable because the UltraPath version is
too early. Therefore, you are advised to upgrade UltraPath when services are
suspended during installation and deployment so that services will not be
interrupted for several times. For details about how to check the UltraPath version,
see Check the version of the multipathing software installed on the
application server.
NOTE
To upgrade UltraPath whose version is earlier than V100R008C20, suspend services on the
application server.
Network Planning

Type



Type
Standard ● A crossed networking

switch- mode is adopted to ensure
connection link redundancy, that is,
network each controller in the local
storage system is
adopted, use different
ports on the local storage
system to connect the
server.
are deployed on the
connect to the
application servers reside
in different zones.
NOTE
● The total specification for paths of the external LUNs is limited (Total specification =
maximum number of paths supported by each external LUN, the access of other
external LUNs will be affected.
● When connecting the local storage system to the heterogeneous storage system, do not
share ports with HyperMetro and HyperReplication services.
Deployment and Installation

Figure 5-2 shows the deployment and installation process of application servers, a

Figure 5-2 Deployment and installation process

Connect the local storage system to the
1 Check initial status. 2 heterogeneous storage system and
Application server Application server
Heterogeneous Local storage Heterogeneous

storage system system storage system
4 Remove the heterogeneous storage 3 Take over external LUNs.

system from the service system.
Hosting
External
Heterogeneous eDevLUN
Local storage Local storage LUN
storage system Heterogeneous
system system storage system
Original cable
New cable
Removal
NOTE
Comply with the following rules when deploying and installing the application servers,
heterogeneous storage system, and local storage system:
● The method used to connect the local storage system to application servers must be the
same as that used to connect the heterogeneous storage system to application servers.
For example, if the heterogeneous storage system is connected to application servers
through Fibre Channel links, the local storage system must be connected to application
servers through Fibre Channel links.
● Application servers must use the HBAs from the same vendor and with the same model
and driver version to connect to the heterogeneous storage system and local storage
system.

Table 5-4 describes the deployment and installation process.
Table 5-4 Description of the deployment and installation process

Procedure Description
1. Check the initial status. The application servers are connected to the
heterogeneous storage system and the
heterogeneous storage system carries service data.
2. Connect the local Connect the local storage system to the

storage system to the heterogeneous storage system and application
heterogeneous storage servers.
system and application NOTE
servers. ● For details about how to connect the local storage
system to the heterogeneous storage system, see
Table 5-3.
● If optical fibers are used to connect a local storage
device to a remote storage device, the local storage
device automatically identifies the remote links. After
the remote storage device is disconnected from the
local storage device, the remote links disappear. After
mapping external LUNs to the local storage system as
instructed in 5.5.1.1 Configuring a Heterogeneous
Storage System, implement full automatic scanning
for LUNs. Then, the remote device that corresponds to
the heterogeneous storage system can be discovered
in DeviceManager of the local storage system.
● If network cables are used to connect the local
storage device to the remote storage device, perform
the operations in 3.4.2.2 Adding an External Storage
Device so that the local storage device can identify
the remote links.
3. Take over external Use SmartVirtualization to take over LUNs of the

LUNs. heterogeneous storage system.
NOTE
For details, see 5.5 Configuring the Logical Connection
Between the Heterogeneous Storage System and Local
Storage System to 5.8 Clearing the Path Switchover
Property of the eDevLUNs that Are Masqueraded.
4. (Optional) Remove the After external LUNs are taken over successfully, use
heterogeneous storage SmartMigration to migrate data on the
system from the service heterogeneous storage system to the local storage
system. system. Then the local storage system carries
service data.
NOTE
For details about how to configure SmartMigration, see
the OceanStor Dorado 6.0.0 SmartMigration Feature
Guide.


System
When you use SmartVirtualization to take over storage resources online, you must
establish logical connections between the local storage system and the
and scan for the remote LUNs on the local storage system.
5.5.1 Fibre Channel Connection

LUNs on the local storage system, when Fibre Channel connection is adopted
between the two storage systems.

Configure the heterogeneous storage system and map the LUNs of the storage
system to the local storage system.
Table 5-5 lists the operations that must be performed in the heterogeneous
storage system.
Table 5-5 Operations that must be performed in the heterogeneous storage

system
Configuration Procedure Description
Create a host. For the heterogeneous storage system,

the local storage system is equivalent
to a host. You can create a host and
add its initiator to the local storage
system to establish a logical
heterogeneous storage system and
NOTE
The initiator WWPN of the local storage
system is the WWPN of the port that
connects to the heterogeneous storage
system.
Create a host group. To achieve convenient management of

multiple hosts, add hosts to a host
group.
Create a mapping view. Create a mapping view to map the

LUNs of the heterogeneous storage

Modify host LUN IDs. Host LUN IDs mapped to the local
storage system must be the same as
those mapped from the heterogeneous
storage system to the application
server. Otherwise, the online takeover
will fail.
NOTE
Operations vary depending on different models of heterogeneous storage systems. The

preceding configuration procedures are for reference only. For details, see the operation
guide of heterogeneous storage systems of each model.

Prerequisites
device.
Procedure
----End
5.5.2 iSCSI Connection

LUNs on the local storage system, when iSCSI connection is adopted between the
two storage systems.
5.5.2.1 Managing Logical Ports

This section describes how to manage logical ports. A logical port is created based
on an Ethernet port, a bond port, or a VLAN.

Precautions
It is recommended that you create no more than 64 logical ports for each
controller. If more than 64 logical ports are created for one controller, the logical
ports will fail over to a few available physical ports in the event that a large
number of physical ports fail, decreasing service performance.
Procedure
Step 1 Choose System > Hardware.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
Step 3 Click to switch to the rear view.

Step 4 Select the Ethernet port you want to configure.
Step 5 Click Manage Logical Port.
The Manage Logical Port page is displayed.
Step 6 Create, modify, or delete logical ports on the Ethernet port and manage their
route information as required.
● To create a logical port:
a. Click Create.
The Create Logical Port page is displayed.
b. Set the parameters listed in Table 5-6.
Table 5-6 Logical port parameters
Port Type Type of the logical port to be created.
Home Port Home port on which the logical port is created.
Name Name of the logical port.

The name must meet the following requirements:
▪ The name must be unique.
▪ The name contains only letters, digits, periods (.),

underscores (_), and hyphens (-).
▪ The name contains 1 to 31 characters.
IP Address Type IP address type of the logical port, which can be

IPv4 or IPv6.
IP Address IPv4 or IPv6 address of the logical port.
Subnet Mask Subnet mask of the logical port's IPv4 address.

NOTE
set to IPv4.

Prefix Prefix length of the logical port's IPv6 address.

NOTE
set to IPv6.
Gateway Gateway of the logical port's IP address.
c. Click OK.
● To manage route information:
a. Select the desired logical port and click Manage Route.
The Manage Route page is displayed.
NOTE
You can also click on the right of the logical port and choose Manage Route.
b. Configure the route information for the logical port.
i. In the IP Address drop-down list, select the IP address of the logical
port for which you want to add a route.
ii. Click Add.
iii. Set the parameters listed in Table 5-7.
Table 5-7 Route parameters
Paramet Description
er
Type Three types of routes are available:

○ Default route
A route through which data is forwarded by default
if no preferred route is available. The destination
address and mask (IPv4) or prefix (IPv6) of the
default route are automatically set to 0. To use this
option, you only need to add a gateway.
○ Host route
A route to a host. The destination mask (IPv4) or
prefix (IPv6) of the host route is automatically set to
255.255.255.255 or 128. To use this option, you only
need to add the destination address and gateway.
○ Network segment route
A route to a network segment. You must add the
destination address, destination mask (IPv4) or
prefix (IPv6), and gateway.
Destinati IPv4 address, IPv6 address, or network segment of the

on destination service network port on the application
Address server or destination logical port on another storage
system.

Paramet Description
er
Subnet Subnet mask of the IPv4 address or prefix of the IPv6

Mask/ address for the destination service network port on the
Prefix application server or destination logical port on another
storage system.
Gateway Gateway where the local logical port's IP address

resides.
NOTE
The IP address of the gateway must be different from all
internal heartbeat IP addresses. Otherwise, routing will fail.
iv. Click . The route information is added to the list.

NOTE
To delete a route, select it and click .

v. Click Close.
----End
5.5.2.2 Adding an External Storage Device

This section describes how to establish a logical connection between a local
storage device and an external storage device for data transmission.
Procedure
Step 2 Add an external storage device.

● Add an external FC storage device.
Click Add and choose FC. The system will automatically discover external FC
storage devices. This operation will last for dozens of seconds.
● Add an external iSCSI storage device.
a. Click Add and choose iSCSI.
The Add External Storage Device dialog box is displayed.
b. Set up the connection to the external storage device.
i. Set the iSCSI link parameters listed in Table 5-8.

storage device.


port on the external storage
device.
ii. (Optional) Enable CHAP Authentication and specify Username and

Password.
NOTE
Before enabling CHAP authentication, ensure that CHAP authentication has

been enabled on the external storage device and the user name and
password have been configured.
c. Click OK.
Confirm your operation as prompted.
----End

storage system.

system
Create a host. For the heterogeneous storage system, the local

storage system is equivalent to a host. You can
create a host and add its initiator to the local
storage system to establish a logical connection
between the heterogeneous storage system and
NOTE
The initiator IQN of the local storage system is the IQN of
the port that connects to the heterogeneous storage
system.
Add the host to the host Add the created host to the host group where the
group. application server resides.
NOTE



Prerequisites
device.
Procedure
----End


storage device.
Prerequisites
Precautions
LUN.

on the LUN.
Procedure
NOTE

external LUN.
eDevLUN.
Step 4 Click OK.
NOTE
eDevLUN.
----End



application servers
Start
Create a LUN group.

Create a host.

relationship.
NOTE

5.6.3 Scanning for eDevLUNs on an Application Server

After an application server scans for mapped eDevLUNs, OceanStor UltraPath
updates the information about the paths among the local storage system,
heterogeneous storage system, and application server.
The procedures for scanning LUNs vary on application servers running different
operating systems. For details, see section "Using the Storage Space on an
Application Server" of the OceanStor Dorado 6.0.0 Basic Storage Service
Configuration Guide.


Switch over host paths to the paths between application servers and the local
storage system so that the local storage system can smoothly carry service data.
5.7.1 Checking the Multipathing Status

Check information about paths between the heterogeneous storage system, local
storage system, and application server, LUNs mapped to the application server,
and the number of I/O paths of the LUNs to determine whether eDevLUNs are
LUNs from the heterogeneous storage system.
Prerequisites
The IDs, WWNs, and path information that are queried in Table 5-2 have been
recorded.
Context
OceanStor UltraPath V100R008C20 is used as an example here. If UltraPath of an
earlier version or third-party multipathing software is installed on the application
server, refer to the operation guide of the corresponding multipathing software for
specific commands.
Procedure
Step 1 Log in to the application server and go to the CLI management page of the
UltraPath.
Step 2 Run show path to query information about paths between the heterogeneous
storage system, local storage system, and application server.
UltraPath CLI #0 >show path
----------------------------------------------------------------------------------------------------------------------------
Path ID Initiator Port Array Name Controller Target Port Path State Check State Port Type Port
ID
0 2100001b32053e20 Huawei.Storage48 0B 20184846fb8ca15f Normal -- FC
--
1 2100001b32053e20 Huawei.Storage48 0A 200b4846fb8ca15f Normal -- FC
--
4 2100001b32055f20 Huawei.Storage48 0B 20194846fb8ca15f Normal -- FC
--
5 2100001b32055f20 Huawei.Storage48 0A 20084846fb8ca15f Normal -- FC
--
----------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------
Path ID Initiator Port Array Name Controller Target Port Path State Check State Port Type Port
ID
2 2100001b32054e20 Huawei.Storage46 0B 24103400a30d9c5f Normal -- FC
--
3 2100001b32054e21 Huawei.Storage46 0A 24003400a30d9c5f Normal -- FC
--
6 2100001b32056f20 Huawei.Storage46 0B 24113400a30d9c5f Normal -- FC
--
7 2100001b32056f21 Huawei.Storage46 0A 24013400a30d9c5f Normal -- FC
--
----------------------------------------------------------------------------------------------------------------------------

NOTE
Differentiate the local storage system from the heterogeneous storage system based on
Array Name. For example, in the preceding command output, Huawei.Storage48 and
Huawei.Storage46 indicate the heterogeneous storage system and local storage system,
respectively.
In the command output, check whether the following requirements are met:
● Initiator Port and Target Port of each path between the heterogeneous
storage system and application server are consistent with the information
recorded in chapter 5.3 Pre-Configuration Check.
● Initiator Port and Target Port of each path between the local storage system
and application server is different from those of each path between the
heterogeneous storage system and application server.
– If yes, paths are normal. Perform Step 3.
– If no, paths are abnormal. Perform the following steps to check
information about paths between the application server, heterogeneous
storage system, and local storage system.
i. Check the physical networking and confirm the number of devices
that connect the application server to the heterogeneous storage
system and local storage system, and information about the initiator
port and target port.
ii. Run show path to check the number of paths between the
application server, heterogeneous storage system, and local storage
system, and information about Initiator Port and Target Port of
each path.
iii. Locate the path that is different from other paths.
iv. Reinsert the physical connection of the abnormal path.
v. Run show path, wait until path status becomes normal, and perform
Step 3.
Step 3 Run the show vlun type=all command to query the information about the LUNs
that are mapped to the application server.
UltraPath CLI #0 >show vlun type=all
------------------------------------------------------------------------------------------------------------------------------
-----------------
Vlun ID Disk Name Lun WWN Status Capacity Ctrl(Own/Work) Array
Name Dev Lun ID
Huawei.Storage48 36
Huawei.Storage46 37
1 sdc hl_luntest_2 630d17e100b33e3909eae968000000f2 Normal 1.00GB --/--
Huawei.Storage48 242
1 sdc hl_luntest_2 630d17e100b33e3909eae968000000f2 Normal 1.00GB --/--
Huawei.Storage46 243
------------------------------------------------------------------------------------------------------------------------------
------------------
In the command output, check for identical Vlun ID values and whether Lun
WWN is the same as that obtained in Table 5-2:
● If yes, eDevLUNs have been masqueraded as the LUNs in the heterogeneous

storage system. Go to Step 4.

● If no, eDevLUNs are not masqueraded as the LUNs in the heterogeneous

storage system. Configure the eDevLUNs again.
Step 4 Run the show vlun id=XXX type=all command to query the path information
about a specific LUN.
NOTE
XXX indicates the ID of the vLUN mapped to the application server queried in Step 3 after
an external LUN on the heterogeneous storage system is masqueraded as an eDevLUN. For
example, in Step 3, Vlun ID of the eDevLUN mapped to the application server is 0.
UltraPath CLI #0 >show vlun id=0 type=all
=======================================================
VLUN#0 Information
=======================================================
Disk : sdb
Manual IO Suspension : Off
Aggregation Type : Migration
Aggregation Specific Attribution
IO Direction : Source
Rollback : Disable
Aggregation Member#0 Information
Name : hl_edvlun1
Status : Normal
Capacity : 1.00GB
Aggregation Specific Attribution : Target Device
LUN WWN : 630d17e100b33e3900135b9900000024
Array SN : 210235980510XX0000XX
Product Name : XXXXX
Working Controller: --
Num of Paths :4
Controller 0A
Path 0 : Normal
Path 7 : Normal
Controller 0B
Path 2 : Normal
Path 6 : Normal
Aggregation Member#1 Information
Name : hl_luntest
Status : Normal
Capacity : 1.00GB
Aggregation Specific Attribution : Source Device
LUN WWN : 630d17e100b33e3900135b9900000024
Array SN : SN98765432XX765432XX
Product Name : XXXXx
Working Controller: --
Num of Paths :4
Controller 0A
Path 1 : Normal
Path 5 : Normal
Controller 0B
Path 0 : Normal
Path 4 : Normal
-------------------------------------------------------

NOTE
After the external LUN is taken over online, Aggregation Type becomes Migration in the
command output.
● In the command output, information in Source Device of Aggregation Specific
Attribution indicates the information about the vLUN mapped from the external LUN
of the heterogeneous storage system to the application server.
● In the command output, information in Target Device of Aggregation Specific
Attribution indicates the information about the vLUN mapped from the eDevLUN
masqueraded in the local storage system to the application server.
In the command output of the external LUN and eDevLUN, check whether their
LUN WWNs, Product Names, and Vendor Names are consistent, and their Array
SNs are different.
● If yes, the application server identifies the eDevLUN as a LUN on the
● If no, the application server identifies the eDevLUN as a new LUN. Contact
Huawei technical support.
----End
Follow-up Procedure
If the LUN path information that is queried increases (that is, the application
server identifies eDevLUNs as the LUNs in the heterogeneous storage system) and
the OceanStor Dorado V6 series storage system does not need to take over
services from the heterogeneous storage system, perform a rollback. For details
about the operations, see 10.3 Performing Rollback.
5.7.2 Switching Over Host Paths

Switch over host I/O paths to the paths between the local storage system and
application servers. In this way, application servers can use eDevLUNs to deliver
host I/Os to the heterogeneous storage system.
NOTE
OceanStor UltraPath is used as an example here. If third-party multipathing software is

installed on application servers, see the third-party multipathing software document to
obtain commands.
The methods used to switch over host paths vary depending on different versions
of OceanStor UltraPath installed on application servers.
● If OceanStor UltraPath whose version is earlier than V100R008C20 is installed
on an application server, remove the physical cables between the
heterogeneous storage system and application server. The application server
automatically switches over the I/O transfer path to the path between the
local storage system and application server.

NOTE
● Remove the physical cables between heterogeneous storage systems and application
servers to switch paths in the case when Huawei VIS6000/VIS6000T storage systems are
taken over online. The UltraPath version is irrelevant.
● If extended masquerading is used, the application server cannot run the command for
switching over the host I/O path. In this case, remove the physical connection between
the heterogeneous storage system and application server to switch over the path.
● If OceanStor UltraPath V100R008C20 or later is installed on an application
server, perform an operation specific to the network environment to switch
over the I/O transfer path to the path between the local storage system and
– In a non-cluster environment or the cluster is running on AIX or Oracle
RAC or is not configured with SCSI-3 and SCSI-2 reservation, run the start
migration command on UltraPath CLI of the application server.
The format of the start migration command is start migration
vlun_id=ID direction={ source | target } rollback={ enable | disable }.
Table 5-10 describes the command parameters.
Table 5-10 Parameter description
vlun_id=ID ID of the LUN scanned by the application

server.
direction={ source | Path switchover direction. Switch over I/Os

target } to the target array or source array.
● source: Switch over I/Os to the source
array (heterogeneous storage system).
● target: Switch over I/Os to the target
array (local storage system).
In this operation, switch over I/Os to the
target array.
rollback={ enable | Enable or disable automatic rollback after

disable } an I/O switchover.
● enable: Enable automatic rollback after
an I/O switchover. If an online migration
fails, I/Os can be automatically switched
back to the source array.
NOTE
rollback can be set to enable only when
direction is set to target.
● disable: Disable automatic rollback after
an I/O switchover. If an online migration
fails, I/Os cannot be switched back to
the source array.
– In other types of cluster networking, perform the following operations on

each host in the cluster:

i. Run the start iosuspension vlun_id=<id> timeout=<value>

command to suspend I/Os. This ensures consistency of registration
and reserved information in the cluster during follow-up operations.
You are advised to set <value> to 30, namely, 30 seconds, and ensure
that follow-up operations can be completed within 30 seconds.
ii. Run the start migration vlun_id= direction=target rollback=enable
command to switch I/Os to the path between the local storage
system and the application server.
iii. To ensure that the operations in 5.7.3 Migrating the Reserved
Information and 5.7.4 Confirming the Completion of the Host
Path Switchover can be completed within 30 seconds, run the show
vlun id=<id> command to check whether the I/O suspension has
timed out.
UltraPath CLI #2 >show vlun id=1
=======================================================
VLUN#1 Information
=======================================================
Disk : sdc
Name : test_0001
Status : Normal
Capacity : 1.00GB
Product Name : XSG1
Vendor Name : XXXXX
Owning Controller : --/--
Working Controller : --/--
Num of Paths : 4
LUN WWN : 648435a10077515b1a08cd540000002a
Array Name : Huawei.Storage219.70
Controller 0A
Path 4 [1:0:4:2] (up-5) : Normal
Path 10 [4:0:4:2] (up-13) : Normal
Controller 0B
Path 0 [1:0:0:2] (up-1) : Normal
Path 8 [4:0:2:2] (up-9) : Normal
Dev Lun ID : 42
Manual IO Suspension : XXX
-------------------------------------------------------
In the command output, Manual IO Suspension indicates whether

I/O suspension has timed out.
○ If Manual IO Suspension is Off, I/O suspension has timed out.
Run the start migration vlun_id= direction=source
rollback=disable command to switch the I/O path back to the
path between the heterogeneous storage system and the
application server, and perform 5.7.2 Switching Over Host
Paths again.
○ If Manual IO Suspension is On (timeout/remain :{30000}
seconds/{XXXXX} seconds) and XXXXX is smaller than 30000,
I/O suspension has not timed out and you can perform follow-
up operations.
Follow-up Procedure
● For UltraPath earlier than V100R008C20, run show path on the application
server to confirm that the status of all paths between the local storage
system and the application server is normal. On DeviceManager, confirm that
read and write I/Os exist. The host path is switched over successfully.

After the host I/O path is switched over to the path between the local storage
system and application server, remove the initiator that corresponds to the
application server from the created hosts on the management interface of the
● For UltraPath V100R008C20 and later versions, run show iostat vlun_id=?
interval=? on the application server to check performance statistics about a
specified LUN at a statistics interval. If read and write I/Os are generated, the
host path is switched over successfully.
After the host I/O path is switched over to the path between the local storage
system and application server, perform the following operations:
a. Disconnect the heterogeneous storage system from the application server.
b. On the management interface of the heterogeneous storage system,
remove the initiator that corresponds to the application server from the
created hosts.
c. Delete the heterogeneous storage system's disks from the application
server. For details, see 11.20 How Can I Delete the Heterogeneous
Disks from the Application Server?.
5.7.3 Migrating the Reserved Information

Run the related command in the local storage system to migrate the reserved
information from the heterogeneous storage system to the local storage system.
Context
The Resource Reservation Protocol (RSVP) is a transport-layer protocol designed to
reserve resources for data flows. The protocol neither transports application data
flows nor executes routing. It is similar to a control protocol. The protocol is used
for reserved information migration.
An application server delivers a reserved information migration request to a

storage system. When LUN services are migrated from the heterogeneous storage
system to the local storage system, the reserved information on the LUNs is also
migrated to the local storage system, ensuring that the application server can
properly read data from and write data into the local storage system.
Procedure
Step 1 Log in to the management interface of the local storage system's CLI.
Step 2 Run the change protocol service command to migrate the reserved information
from the heterogeneous storage system to the local storage system.
The format of the change protocol service command is change protocol service
operation_code=? operation_object_type=? operation_object_id=?. Table 5-11
describes the parameters.
Table 5-11 Parameter description
operation_code=? Operation type. The value is relocate.

operation_object_type=? Operation object type. The value is

lun_reservation.
operation_object_id=? Operation object ID. The value is the

ID of an eDevLUN that is mapped to
NOTE
To obtain the value, run show
lun_takeover genera.
----End
Follow-up Procedure
After migrating the reserved information to the local storage system, perform a
rollback if you do not want to use the OceanStor Dorado V6 series storage system
for online takeover. For details, see 10.3 Performing Rollback.
5.7.4 Confirming the Completion of the Host Path Switchover

Run the related command in the local storage system to ensure that I/Os are
transmitted through the paths between the local storage and the application
server.
Precautions
The operation of checking whether a host path is switched over successfully needs
to be performed in developer mode on the CLI management interface of the local
storage system, and this operation can be only performed by Huawei technical
support.
Before performing this operation, ensure that the operations in 5.7.1 Checking
the Multipathing Status, 5.7.2 Switching Over Host Paths, and 5.7.3 Migrating
the Reserved Information have been completed. Otherwise, this operation may
have risks such as data inconsistency and service interruption.
Procedure
Step 1 Check whether the host path of LUNs is switched over to the target storage
system.
1. Log in to the management interface of the local storage system's CLI and go
to the developer mode.
Log in to the CLI as user admin and enter change user_mode current_mode
user_mode=developer. Then press Enter.
admin:/>change user_mode current_mode user_mode=developer
developer:/> \\Successful login
2. Run the change lun_takeover finish_switch_path lun_id=? command to

ensure that I/Os are transmitted through the paths between the local storage
and the application server.

NOTE
For details, see the advanced O&M command reference of the corresponding product
model.
Step 2 Optional: If host nodes are clustered on the network and the cluster is not
running AIX or Oracle RAC and not configured with SCSI-3 or SCSI-2 reservation,
run stop iosuspension vlun_id=<id> on each of the host nodes to stop I/O
suspension.
----End
5.8 Clearing the Path Switchover Property of the

eDevLUNs that Are Masqueraded
Clear the path switchover property of the eDevLUNs that are masqueraded and
convert them into common LUNs so that other online takeover tasks can be
executed.
Precautions
This operation needs to be performed in developer mode on the CLI management
interface of the local storage system, and this operation can be only performed by
Context
After the path switchover property of an eDevLUN that is masqueraded is cleared,
the storage system where the LUN resides can be used as a heterogeneous storage
system to configure other online takeover tasks.
Procedure
Step 1 Log in to the management interface of the local storage system's CLI and go to
the developer mode.
Step 2 Run the change lun_takeover disable_switch_path lun_id=lunid command to

clear the properties of the eDevLUNs that are masqueraded.

NOTE
model.
----End
Follow-up Procedure
● Run the debug command to go to the diagnostic view. In the diagnostic view,
run the lun showctrl command to check whether the properties of the
masqueraded eDevLUNs are cleared successfully. The format of the lun
showctrl command is lun showctrl lunid. For example, run lun showctrl 1. If
both Is Dst LUN and Edev LUN bypass cache are displayed as no in the
command output, the properties of the masqueraded eDevLUNs are cleared
successfully.
NOTE
model.
● Do not restore the connection (command or physical cable) between the
application server and heterogeneous storage system. Otherwise, data on
external LUNs may become inconsistent.
● If an application server is running OceanStor UltraPath V100R008C20 or later,
remove the mapping between the application server and the heterogeneous
storage system. Otherwise, after the application server is restarted, the
mapping with the heterogeneous storage system automatically recovers,
causing data inconsistency on the external LUN.
● If the UltraPath version is earlier than V100R008C20 and you need to use new
functions of the local storage system, stop services on the application server,
upgrade the UltraPath and modify the masquerading properties of eDevLUNs.
If you need to configure data migration after the takeover, the upgrade and
modification are not necessary.
As eDevLUNs with masquerading properties cannot use some functions of the
local storage system and modifying masquerading properties requires service
suspension, you can modify the masquerading properties of eDevLUNs to No
Masquerading when upgrading the UltraPath after services are suspended.
For details about how to do so, see the content about using UltraPath in
13.19.4 Other Types of Huawei Storage Systems.

6 Taking Over Third-Party Heterogeneous

Storage Systems in Online Mode
After configuring the online takeover function, you can enable the OceanStor
Dorado V6 series storage system (local storage system) to take over the
heterogeneous storage system and complete data migration and service takeover.
This chapter describes how to take over third-party heterogeneous storage
systems online.
WARNING

solution.
Context
A third-party storage system can be taken over online only when the application
server runs the native multipathing software of operating systems and does not
run any other multipathing software that can take over Huawei storage systems,
such as Huawei UltraPath, Symantec SF DMP, and Veritas Storage Foundation.
Only certain operating systems and cluster software are supported. For details
about supported operating systems and cluster software, see 13.2 Compatibility
Requirements for an Online Takeover.
NOTE
In the case of Windows and AIX operating systems, you are advised to ask professional
service engineers of Huawei Storage to use the dedicated tool for takeover.
Precautions
Do not perform the following operations until an online takeover completes.

● Capacity expansion
● Storage system upgrade
● Primary/Secondary switchover of a cluster or restart of a node in the cluster
6.8 Clearing the Path Switchover Property of the eDevLUNs that Are Masqueraded

Before configuring the online takeover function and taking over third-party
heterogeneous storage systems in online mode, understand the configuration
process to ensure a smooth configuration.

Figure 6-1 Process for configuring online takeover
Start
Check the license file.
Check the application

server.
Perform a pre-configuration Check the

check. heterogeneous storage
system.
Install and deploy the system.
storage systems.
Fibre Channel connection
Configure the
system.
Create eDevLUNs.
Configure and use Map eDevLUNs to an

eDevLUNs. application server.
Scan for eDevLUNs on
Check the multipathing

status.
Configure host path
switchover. Switch over host paths.
Confirm the host path

switchover.
Clear the path switchover
property of the masqueraded
eDevLUNs.
End
Mandatory item Mandatory sub-item
NOTE


Table 6-1 describes specific operations for configuring online takeover, purposes of
the operations, precautions, and devices on which the operations are operated.
Table 6-1 Each step of the configuration process

Configurati Procedure Description Operation Position
on Process
Checking the - Before Local storage system

license file configuring the
online takeover
function, ensure
that the license
file contains the
information
about
SmartVirtualiza-
tion.
Performing Check the ● Check Application server

a pre- application whether
configuratio server. services are
n check running
properly
based on
service types.
● Check the
health
condition of
the host
multipathing
software
based on the
software
type and
version.
Check the Check whether Heterogeneous storage

heterogeneous the system
storage system. heterogeneous
storage system
is running
properly.
Check the local Check whether Local storage system

storage system. the local
storage system
is running
properly.


on Process
Installing - ● Use Fibre Heterogeneous storage

and Channel to system, local storage
deploying connect the system, and application
the heterogeneo servers
application us storage
server and system with
storage the local
systems storage
system.
● Connect
physical
cables
between the
local storage
system and
application
servers.
NOTE
● Only Fibre
Channel
connections
are
supported
between the
local storage
system and
the third-
party storage
system.
● The method
used to
connect the
local storage
system to
application
servers must
be the same
as that used
to connect
the
heterogeneo
us storage
system to
application
servers.


on Process
Establishing Configure a Configure the Heterogeneous storage

a logical heterogeneous heterogeneous system
connection storage system. storage system
between the and map the
heterogeneo LUNs of the
us storage storage system
system and to the local
local storage storage system.
system
Enable full Full automatic Local storage system
automatic LUN LUN scanning
scanning. enables all
LUNs of the
heterogeneous
storage systems
that have been
mapped to the
local storage
system to be
connected to
the local
storage system.
Configuring Create Create Local storage system

and using eDevLUNs eDevLUNs for
eDevLUNs (masquerading external LUNs
property: Third- in storage pools
party). of the local
storage system
and configure
the
masquerading
property as
Third-party.


on Process
Map eDevLUNs Establish a Local storage system

to an application mapping
server. relationship
between
eDevLUNs and
an application
server so that
the application
server can
identify the
eDevLUNs.
1. Creating a
LUN group:
To achieve
convenient
management
of multiple
eDevLUNs,
add the
eDevLUNs
that are
created after
the
heterogeneo
us storage
system is
mapped to
the local
storage
system for
online
takeover to a
LUN group.
2. Creating a
host and
adding the
initiator:
Create a host
that
corresponds
to the
application
server and
establish a
logical
connection
between the
local storage


on Process
system and
application
server by
adding the
initiator that
corresponds
to the
application
server's
service port
to the local
storage
system.
3. Modifying
initiator
properties:
Check and
modify the
ALUA policy
of the
initiator to
make it the
same as the
ALUA policy
of external
LUNs.
4. Creating a
host group:
To achieve
convenient
management
of multiple
hosts, add
hosts to a
host group.
5. Creating a
mapping
view: Create
a mapping
view and
map the
eDevLUNs to
the
application
server.


on Process
Scan for A scan triggers Application server

eDevLUNs on multipathing
the application software to
server. update the
information
about the paths
among the local
storage system,
heterogeneous
storage system,
and application
server.
Configuring Check the Check whether Application server

host path multipathing newly added
switchover status. paths are
identified on an
application
server.
Switch over host For commands Application server

paths. used to switch
over host paths,
see documents
for the native
multipathing
software of
operating
systems.
Confirming host Confirm the Local storage system

path switchover completion of
the host path
switchover.
Clearing the - Clear the path Local storage system

path switchover
switchover property of the
property of eDevLUNs that
the are
eDevLUNs masqueraded
that are and convert
masquerade them into
d common LUNs
so that the
LUNs can be
used in other
online takeover
tasks.


Each value-added feature requires a license file for activation. Before configuring
the takeover function, ensure that its license file is valid.
Context
The heterogeneous virtualization feature is displayed as SmartVirtualization in
the Feature column on DeviceManager.
Procedure
----End
Follow-up Procedure
product model.
documents.
expired, apply for, import, and activate a new one.

Before configuring the online takeover function, check whether the application
server, heterogeneous storage system, and local storage system work properly to
ensure that the local storage system can smoothly take over services from the
Check items are as follows:
● Check the status of services running on application servers.

Check whether services are running properly based on service types. When the
service status is abnormal, restore the services first.
NOTE
If an application server uses the native multipathing software of the operating system when
a third-party heterogeneous storage system is taken over online, see the related
multipathing software document to obtain commands.

● Check the heterogeneous storage system status. If the system is abnormal,

rectify the fault of the storage system before performing subsequent
operations.
NOTE
For operations on a third-party heterogeneous storage system, see its operation guide.
● Check the local storage system status.
SN : 210235G6EHY0CX0000XX
Location :
Time : 2015-04-17/17:00:03 +08:00
– When Health Status and Running Status are displayed as Normal, the
local storage system is normal, you can perform subsequent operations.
– When Health Status and Running Status are not displayed as Normal,
rectify the fault of the local storage system, and perform subsequent
steps after ensuring that the local storage system becomes normal.

This section describes how to deploy and install application servers, a
Network Planning


Type

Standard ● A crossed networking mode

switch- is adopted to ensure link
network controller in the local
storage system is
adopted, use different ports
on the local storage system
to connect the
server.
are deployed on the
connect to the
application servers reside in
different zones.
NOTE
The total specification for paths of the external LUNs is limited (Total specification =
maximum number of paths supported by each external LUN, the access of other external
LUNs will be affected.

Deployment and Installation

Figure 6-2 shows the deployment and installation process of application servers, a
Figure 6-2 Deployment and installation process

Connect the local storage system to the
1 Check initial status. 2 heterogeneous storage system and
Heterogeneous Local storage Heterogeneous

storage system system storage system
4 Remove the heterogeneous storage 3 Take over external LUNs.

system from the service system.
Hosting
External
Heterogeneous eDevLUN
Local storage Local storage LUN
storage system Heterogeneous
system system storage system
Original cable
New cable
Removal
Table 6-3 describes the deployment and installation process.

Table 6-3 Description of the deployment and installation process

1. Check the initial status. The application servers are connected to the
heterogeneous storage system and the
heterogeneous storage system carries service data.
2. Connect the local Connect the local storage system to the

storage system to the heterogeneous storage system and application
heterogeneous storage servers.
system and application NOTE
servers. Comply with the following rules when deploying and
installing the application servers, heterogeneous storage
system, and local storage system:
● The method used to connect the local storage system
to application servers must be the same as that used
to connect the heterogeneous storage system to
application servers. For example, if the heterogeneous
storage system is connected to application servers
through Fibre Channel links, the local storage system
must be connected to application servers through Fibre
Channel links.
● Application servers must use the HBAs from the same
vendor and with the same model and driver version to
connect to the heterogeneous storage system and local
storage system.
● Only Fibre Channel connections are supported between
the local storage system and the heterogeneous
storage system.
● If optical fibers are used to connect a local storage
device to a remote storage device, the local storage
device automatically identifies the remote links. After
the remote storage device is disconnected from the
local storage device, the remote links disappear. After
mapping external LUNs to the local storage system as
instructed in 5.5.1.1 Configuring a Heterogeneous
Storage System, implement full automatic scanning
for LUNs. Then, the remote device that corresponds to
the heterogeneous storage system can be discovered in
DeviceManager of the local storage system.
3. Take over external Use SmartVirtualization to take over LUNs of the

LUNs. heterogeneous storage system.
NOTE
For details, see 6.5 Configuring the Logical Connection
Between the Heterogeneous Storage System and Local
Storage System to 6.8 Clearing the Path Switchover
Property of the eDevLUNs that Are Masqueraded.

4. (Optional) Remove the After external LUNs are taken over successfully, use
heterogeneous storage SmartMigration to migrate data on the
system from the service heterogeneous storage system to the local storage
system. system. Then the local storage system carries
service data.
NOTE
For details about how to configure SmartMigration, see
the OceanStor Dorado 6.0.0 SmartMigration Feature
Guide.

System
and scan for the remote LUNs on the local storage system. When taking over
third-party heterogeneous storage systems, the local storage system must be
connected to heterogeneous storage systems through Fibre Channel. To establish
logical connections, you are only required to map external LUNs to the local
storage system and then perform full automatic scanning.
6.5.1 Configuring a Heterogeneous Storage System

storage system.


system
Create a host. For the heterogeneous storage system,

the local storage system is equivalent
to a host. You can create a host and
add its initiator to the local storage
system to establish a logical
heterogeneous storage system and
NOTE
The initiator WWPN of the local storage
system is the WWPN of the port that
connects to the heterogeneous storage
system.
Create a host group. To achieve convenient management of

multiple hosts, add hosts to a host
group.
Create a mapping view. Create a mapping view to map the

LUNs of the heterogeneous storage
Modify host LUN IDs. Host LUN IDs mapped to the local
storage system must be the same as
those mapped from the heterogeneous
storage system to the application
server. Otherwise, the online takeover
will fail.
NOTE

6.5.2 Scanning for External LUNs

Prerequisites
device.

Procedure
----End

6.6.1 Checking Application Server Configurations

Before creating eDevLUNs, confirm that configurations about Red Hat Linux &
SUSE Linux, HP-UX, and VMware ESXi meet takeover requirements.
6.6.1.1 Red Hat Linux & SUSE Linux Operating System

For Red Hat Linux & SUSE Linux operating systems, ensure that virtual LUN 0
generated before mapping does not exist. Check and record the ALUA policy of
external LUNs.
6.6.1.1.1 Deleting Virtual LUN 0 Generated Before Mapping

When connections between the application server and the local storage system
are established, a useless virtual LUN 0 may be generated on the application
server before mapping of eDevLUNs. Check and delete the virtual LUN 0 before
mapping.
Context
Information about the automatically generated virtual LUN 0: ID 0, vendor
HUAWEI, model XSG1.
Procedure
Step 1 Log in to the application server.
Step 2 Run lsscsi to query path information.
linux-wxfv:~ # lsscsi
[0:0:0:0] cd/dvd MATSHITA DVD-ROM UJDA782 WA84 /dev/sr0
[4:0:0:0] disk IBM-ESXS ST9146852SS B626 -
[4:0:1:0] disk IBM-ESXS ST9146852SS B626 -
[4:1:1:0] disk LSILOGIC Logical Volume 3000 /dev/sda
[5:0:0:0] disk 3PARdata VV 3123 /dev/sdi
[5:0:0:1] disk 3PARdata VV 3123 /dev/sdb
[5:0:0:2] disk 3PARdata VV 3123 /dev/sdc
[5:0:0:254] disk 3PARdata VV 3123 /dev/sdd
[5:0:1:0] disk HUAWEI XSG1 4301 -

[5:0:1:1] disk HUAWEI XSG1 4301 /dev/sdj

[5:0:2:0] disk HUAWEI XSG1 4301 -
[5:0:2:1] disk HUAWEI XSG1 4301 /dev/sdk
[6:0:0:0] disk IMM Virtual Floppy 0316 /dev/sde
[7:0:0:0] disk 3PARdata VV 3123 /dev/sdl
[7:0:0:1] disk 3PARdata VV 3123 /dev/sdf
[7:0:0:2] disk 3PARdata VV 3123 /dev/sdg
[7:0:0:254] disk 3PARdata VV 3123 /dev/sdh
[7:0:1:0] disk HUAWEI XSG1 4301 -
[7:0:1:1] disk HUAWEI XSG1 4301 /dev/sdm
[7:0:2:0] disk HUAWEI XSG1 4301 -
[7:0:2:1] disk HUAWEI XSG1 4301 /dev/sdn
In the command output, the first column is the scsi address and the four numbers
represent scsi_host, channel, target_number, and virtual LUN ID respectively. The
third column is vendor and the fourth column is model. In this case, virtual LUN 0s
are [5:0:1:0], [5:0:2:0], [7:0:1:0], and [7:0:2:0].
Step 3 Run sys/class/scsi_device/scsi_device_id/device/delete to delete virtual LUN 0s.

# echo 1 > /sys/class/scsi_device/5\:0\:1\:0/device/delete
----End
6.6.1.1.2 Checking and Recording the ALUA Policy of External LUNs

This section describes how to check the ALUA policy in Red Hat Linux and SUSE
Linux operating systems.
Context
The ALUA policy of the local storage system must be the same as that of the
external LUNs on the heterogeneous storage system. If the ALUA policies are
different, ALUA will not take effect after online takeover. If necessary, modify the
local storage system's ALUA policy after you confirm the ALUA policy of external
LUNs.
Procedure
Step 2 Run multipath -ll to check information about paths between the heterogeneous
storage system and the application server.
# multipath -ll
mpathae (36e4a8b6100b0a1cc001613170000000f) dm-9 IBM,XSG1
size=16G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=130 status=active
| `- 0:0:3:2 sdh 8:112 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
`- 1:0:3:2 sdx 65:112 active ready running
Step 3 Check whether prio of a disk has the same value and check the ALUA policy.
NOTE
If ALUA is enabled for a disk, the heterogeneous storage system has ALUA enabled.
● If prio has different values and status is active and enabled, ALUA is
enabled.

● If prio has the same value, ALUA is disabled.
----End
6.6.1.2 HP-UX Operating System

For the HP-UX operating system, check and record the ALUA policy of external
LUNs.
Context
LUNs. This section describes how to check the ALUA policy in the HP-UX operating
system.
Procedure
Step 2 Run scsimgr get_attr -D disk -a alua_enabled to check whether ALUA is enabled
for external LUNs.
scsimgr get_attr -D /dev/rdisk/ disk17052 -a alua_enabled
SCSI ATTRIBUTES FOR LUN : /dev/rdisk/ disk17052
name = alua_enabled
current = true
default = true
saved =
If current is true, ALUA is enabled. If current is false, ALUA is disabled.
----End
6.6.1.3 VMware ESXi Operating System

For VMware ESXi operating systems, ensure that path selection policy is set to
VMW_PSP_FIXED before an online takeover is successful. Check and record the
ALUA policy of external LUNs.
6.6.1.3.1 Checking Path Selection Policy

Set the path selection policy of the application server to VMW_PSP_FIXED before
the takeover completes. This ensures that I/Os are written only to one storage
system before paths between the application server and the heterogeneous
storage system are disconnected.
Context
VMW_PSP_FIXED path selection policy is the default configuration for ALUA. This
mode does not support load balancing. As a result, I/Os of all LUNs may be
written to the storage system through the same path and performance problems
may occur. After the takeover, modify the path selection policy based on the

configuration suggestions of the application server's built-in multipathing software

or configuration suggestions of guides in Huawei Storage Interoperability
Navigator. If online migration is required after a takeover, modify the path
selection policy after the migration completes.
Procedure
Step 1 Log in to the application servers as user root.
Step 2 Run esxcli storage nmp device list to check the path selection policy.
root@~ #esxcli storage nmp device list
naa.6ec4d47100683cd11ee336360000000a
Device Display Name: HUAWEI Fibre Channel Disk (naa.6ec4d47100683cd11ee336360000000a)
Storage Array Type: VMW_SATP_DEFAULT_AA
Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=vmhba2:C0:T5:L1;current=none}
Path Selection Policy Device Custom Config:
Working Paths:
Is Local SAS Device: false
Is Boot USB Device: false
Storage Array Type is the path selection policy.

Step 3 Run esxcli storage nmp device set -d disk --psp=VMW_PSP_FIXED to change the
path selection policy to VMW_PSP_FIXED.
#esxcli storage nmp device set -d naa.6ec4d47100683cd11ee336360000000a --psp=VMW_PSP_FIXED
Step 4 Run Step 2 again. Check whether the path selection policy is modified.
If the path selection policy is not modified, contact the technical engineers of the
application server vendor.
----End
6.6.1.3.2 Checking and Recording the ALUA Policy of External LUNs

This section describes how to check the ALUA policy in the VMware ESXi operating
system.
Context
LUNs.
Procedure
Step 2 Run esxcli storage nmp satp list -d disk to check whether ALUA is enabled for
external LUNs.
# esxcli storage nmp satp list –d naa.6ec4d47100683cd1228b1de20000000b
naa.6ec4d47100683cd1228b1de20000000b
Device Display Name: HUAWEI Fibre Channel Disk (naa.6ec4d47100683cd1228b1de20000000b)
Storage Array Type: VMW_SATP_ALUA
Storage Array Type Device Config: {implicit_support=on; explicit_support=on; explicit_allow=on;

alua_followover=on; action_OnRetryErrors=off; {TPG_id=2,TPG_state=AO}{TPG_id=1,TPG_state=ANO}}

Path Selection Policy: VMW_PSP_MRU
Path Selection Policy Device Config: Current Path=vmhba2:C0:T5:L1
Working Paths: vmhba2:C0:T5:L1
Is USB: false
If Storage Array Type is VMW_SATP_ALUA, ALUA is enabled; if Storage Array

Type is of other values, ALUA is disabled.
----End

storage device.
Prerequisites
Precautions
LUN.
on the LUN.
Procedure

NOTE


external LUN.
eDevLUN.
Step 4 Click OK.
NOTE
eDevLUN.
----End



application servers
Start
Create a LUN group.

Create a host.

relationship.
NOTE

6.6.4 Scanning for eDevLUNs on an Application Server

After an application server scans for mapped eDevLUNs, OceanStor UltraPath
updates the information about the paths among the local storage system,
heterogeneous storage system, and application server.
The procedures for scanning LUNs vary on application servers running different
operating systems. For details, see section "Using the Storage Space on an
Application Server" of the OceanStor Dorado 6.0.0 Basic Storage Service
Configuration Guide.


Switch over host paths to the paths between application servers and the local
storage system so that the local storage system can smoothly carry service data.
6.7.1 Configuring Host Path Switchover (Red Hat Linux and

SUSE Linux Operating Systems)
This section describes how to switch over host paths in Red Hat Linux and SUSE
operating systems.
6.7.1.1 Checking Multipathing Software Status

Check information about paths between heterogeneous and local storage systems
and an application server and query the information about the LUNs that are
mapped to the application server and number of each LUN's I/O paths to check
whether eDevLUNs are masqueraded as the LUNs in the heterogeneous storage
system.
Prerequisites
Built-in multipathing software of operating systems has been enabled on the
application server.
Procedure
Step 2 Run multipath –ll and lsscsi to check information about paths between the
heterogeneous and local storage systems and the application server.
1. Run multipath –ll to query the number of paths and check whether all paths
are active ready running. If any path is abnormal, check the physical
connections between the heterogeneous storage systems and the application
server and those between the local storage system and the application server
respectively.
In the command output, disk dm-5 has 8 paths sdc, sds, sde, sdu, sdm, sdi,
sdg, and sdk.
# multipath –ll
mpathc (200173800102103e8) dm-5 IBM,2810XIV
mpathc (200173800102103e8) dm-5 IBM,2810XIV
size=16G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 0:0:1:1 sdc 8:32 active ready running
|- 1:0:1:1 sds 65:32 active ready running
|- 0:0:2:1 sde 8:64 active ready running
|- 1:0:2:1 sdu 65:64 active ready running
|- 1:0:4:1 sdm 8:192 active ready running
|- 0:0:4:1 sdi 8:128 active ready running
|- 0:0:3:1 sdg 8:96 active ready running
`- 1:0:3:1 sdk 8:160 active ready running
2. Run lsscsi to check the owning storage system of each path.
Disk dm-5 has paths sdc, sds, sde, sdu, sdm, sdi, sdg, and sdk. Identify the
owing storage system of each path using the command output. According to

the command output, the first four paths of disk dm-5 belong to third-party
heterogeneous storage systems and the last four paths belong to Huawei
local storage systems.
NOTE
You can use the third column in the output of the lsscsi command to determine whether a
path belongs to a third-party heterogeneous storage system or a Huawei local storage
system. For example, in the command output, IBM indicates a heterogeneous storage
system and HUAWEI indicates a local storage system.
# lsscsi
[0:0:0:0] disk HITACHI OPEN-V 7303 /dev/sda
[0:0:0:1] disk HITACHI OPEN-V 7303 /dev/sdb
[0:0:1:0] storage IBM 2810XIV-LUN-0 10.2 -
[0:0:1:1] disk IBM 2810XIV 10.2 /dev/sdc
[0:0:1:2] disk IBM 2810XIV 10.2 /dev/sdd
[0:0:2:1] disk IBM 2810XIV 10.2 /dev/sde
[0:0:2:2] disk IBM 2810XIV 10.2 /dev/sdf
[0:0:3:0] disk HUAWEI XSG1 4301 -
[0:0:3:1] disk HUAWEI XSG1 4301 /dev/sdg
[0:0:3:2] disk HUAWEI XSG1 4301 /dev/sdh
[0:0:4:0] disk HUAWEI XSG1 4301 -
[0:0:4:1] disk HUAWEI XSG1 4301 /dev/sdi
[0:0:4:2] disk HUAWEI XSG1 4301 /dev/sdj
[1:0:0:0] disk HITACHI OPEN-V 7303 /dev/sdq
[1:0:0:1] disk HITACHI OPEN-V 7303 /dev/sdr
[1:0:1:1] disk IBM 2810XIV 10.2 /dev/sds
[1:0:1:2] disk IBM 2810XIV 10.2 /dev/sdt
[1:0:2:1] disk IBM 2810XIV 10.2 /dev/sdu
[1:0:2:2] disk IBM 2810XIV 10.2 /dev/sdv
[1:0:3:0] disk HUAWEI XSG1 4301 -
[1:0:3:1] disk HUAWEI XSG1 4301 /dev/sdk
[1:0:3:2] disk HUAWEI XSG1 4301 /dev/sdl
[1:0:4:0] disk HUAWEI XSG1 4301 -
[1:0:4:1] disk HUAWEI XSG1 4301 /dev/sdm
[1:0:4:2] disk HUAWEI XSG1 4301 /dev/sdn
[4:0:0:0] disk ATA ST31000524NS SN12 -
[4:0:1:0] disk ATA ST31000524NS SN12 -
[4:1:0:0] disk LSILOGIC Logical Volume 3000 /dev/sdag
----End
6.7.1.2 Switching Over Host Paths

Switch over host I/O paths to the paths between the local storage system and the
application server. In this way, the application server can use eDevLUNs to deliver
NOTE
Refer to the operation guide of the corresponding multipathing software for specific
commands.
Run commands on the application server to delete paths between the application
server and the heterogeneous storage system. Command format is sys/class/
scsi_device/scsi_device_id/device/delete.

After the paths are deleted, services are delivered to the local storage system.
Follow-up Procedure
Run multipath –ll on the application server to check whether the paths between
the local storage system and the application server are normal. Run iostat interval
to confirm that read and write I/Os are generated on the paths between the local
storage system and the application server. interval is the statistics interval (unit:
second). On DeviceManager, confirm that read and write I/Os exist. Host paths are
switched over successfully.
After confirming the successful path switchover, disconnect the cables between
the application server and the heterogeneous storage system.
6.7.2 Configuring Host Path Switchover (HP-UX Operating

Systems)
This section describes how to switch over host paths in HP-UX operating systems.

system.
Prerequisites
The native multipathing software of the operating system has been enabled on
Procedure
Step 2 Run ioscan -funNC disk to check information about LUNs in the heterogeneous
storage system.
# ioscan -funNC disk
disk 17052 64000/0xfa00/0x12a4 esdisk CLAIMED DEVICE IBM 2810XIV
/dev/disk/disk17052 /dev/rdisk/disk17052
In the command output, the disk is a LUN of an IBM storage system.

Step 3 Run scsimgr lun_map -D disk to check information about paths between the
heterogeneous and local storage systems and the application server.
# scsimgr lun_map -D /dev/rdisk/disk6
LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk6
Total number of LUN paths =2

World Wide Identifier(WWID) = 0x50002ac09e041c9f
LUN path : lunpath4

Class = lunpath
Instance =4
Hardware path = 0/0/0/5/0/0/0.0x20110002ac001c9f.0x4001000000000000

SCSI transport protocol = fibre_channel

State = ACTIVE
Last Open or Close state = ACTIVE
LUN path : lunpath6

Class = lunpath
Instance =6
Hardware path = 0/0/0/6/0/0/0.0x21110002ac001c9f.0x4001000000000000
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE
NOTE
If the disk is not in use, State and Last Open or Close state are UNOPEN.
In the command output, Total number of LUN paths = 4 of disk17052 indicates

that four paths exist between the application server and storage systems.
Step 4 Use the storage system WWPN displayed in Hardware path to determine whether
the path belongs to the local storage system or the heterogeneous storage system.
For example, Hardware path in LUN path : lunpath12290 is

0/0/0/6/0/0/0.0x5001738010210150.0x1000000000000, wherein
5001738010210150 is the storage port WWPN.
Step 5 Run scsimgr get_attr –D disk -a state to check information about disks and check
path status. If any path is abnormal, check the physical connections between the
heterogeneous storage system and the application server and those between the
local storage system and the application server respectively.
In the command output, current is the path status. If the status is ONLINE, the
path is normal.
# scsimgr get_attr -D /dev/rdisk/disk2778 -a state
SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk2778
name = state
current = ONLINE
default =
saved =
----End

NOTE
commands.
Run commands on the application server to delete paths between the application
server and the heterogeneous storage system. Command format is rmsf -H
hw_path.

NOTE
Hardware path in the command output of Step 3 in 6.7.2.1 Checking Multipathing

Software Status indicates the disk path, which is the value entered for hw_path.
#rmsf -H 0/0/0/6/0/0/0.0x5001738010210140.0x1000000000000
After the paths are deleted, services are delivered to the local storage system.
Follow-up Procedure
Run iostat [-t] [-L] [interval [count]] to confirm that read and write I/Os are
generated on the paths between the local storage system and the application
server. interval is the statistics interval (unit: second). For example, iostat –L 5
means that I/O delivery status is displayed every five seconds.
# iostat –L 5
lunpath bps sps msps
disk2778_lunpath159 936 1872.5 1.0
disk2778_lunpath158 936 1872.8 1.0
disk2778_lunpath2200 936 1872.8 1.0
disk2778_lunpath3222 936 1872.5 1.0
NOTE
A command output is displayed only when the paths have I/Os. If the paths are normal but
have no I/Os, no command output is displayed.
On DeviceManager, confirm that read and write I/Os exist. Host paths are
switched over successfully.
After confirming the successful path switchover, disconnect the cables between
the application server and the heterogeneous storage system.
6.7.3 Configuring Host Path Switchover (VMware ESXi

Operating Systems)
This section describes how to switch over host paths in VMware ESXi operating
systems.

system.
Prerequisites
The native multipathing software of the operating system has been enabled on
Procedure

Step 2 Run esxcli storage nmp device list to check information about disks on the
application server. Confirm the disks to be migrated.
# esxcli storage nmp device list
mpx.vmhba4:C0:T8:L0
Device Display Name: Local PMCSIERA Enclosure Svc Dev (mpx.vmhba4:C0:T8:L0)
Storage Array Type: VMW_SATP_LOCAL
Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.
Path Selection Policy Device Config: {preferred=vmhba4:C0:T8:L0;current=vmhba4:C0:T8:L0}
Is USB: false
naa.69ce37410035d86d0694090a00000008
Device Display Name: GUAWEI Fibre Channel Disk (naa.69ce37410035d86d0694090a00000008)
Storage Array Type: VMW_SATP_DEFAULT_AA
Storage Array Type Device Config: {action_OnRetryErrors=off}
Path Selection Policy Device Config: {preferred=vmhba3:C0:T6:L2;current=vmhba3:C0:T6:L2}
Is USB: false
Step 3 Run esxcli storage nmp path list-d disk to show information about disk paths
and check whether all paths are active. If any path is abnormal, check the
physical connections between the heterogeneous storage system and the
application server and those between the local storage system and the application
server respectively.
In the command outputs, Group State is the path status. Disk naa.
69ce37410035d86d0694090a00000008 has four paths.
#esxcli storage nmp path list -d naa.69ce37410035d86d0694090a00000008
fc.20000024ff372178:21000024ff372178-fc.2100ec4d47683cd1:2000ec4d47683cd1-naa.
69ce37410035d86d0694090a00000008
Runtime Name: vmhba2:C0:T3:L1
Device: naa.69ce37410035d86d0694090a00000008
Device Display Name: HUAWEI Fibre Channel Disk (naa.69ce37410035d86d0694090a00000008)
Group State: active
Array Priority: 0
Storage Array Type Path Config: SATP VMW_SATP_DEFAULT_AA does not support path configuration.
Path Selection Policy Path Config: {current: yes; preferred: yes}
69ce37410035d86d0694090a00000008
Device: naa.69ce37410035d86d0694090a00000008
Group State: active
Array Priority: 0
Path Selection Policy Path Config: {current: no; preferred: no}
69ce37410035d86d0694090a00000008
Device: naa.69ce37410035d86d0694090a00000008
Group State: active
Array Priority: 0
69ce37410035d86d0694090a00000008
Device: naa.69ce37410035d86d0694090a00000008


Group State: active
Array Priority: 0
Step 4 Use the target WWPN to determine whether the path belongs to the local storage
system or the heterogeneous storage system.
For example, 2000ec4d47683cd1 in fc.20000024ff372178:21000024ff372178-fc.
2100ec4d47683cd1:2000ec4d47683cd1-naa.
69ce37410035d86d0694090a00000008, the first line of the command output in
6.7.3.1 Checking Multipathing Software Status, indicates the WWPN of the
storage port.
----End

NOTE
commands.
Run commands on the application server to disable paths between the application
server and the heterogeneous storage system. The command format is esxcli
storage core path set -p Runtime Name or Path UID --state off.
NOTE
Runtime Name can be obtained from Step 3.

#esxcli storage core path set -p vmhba3:C0:T3:L1 --state off
#esxcli storage nmp path list -d naa.6ec4d47100683cd11ee336360000000a
6ec4d47100683cd11ee336360000000a
Device: naa.6ec4d47100683cd11ee336360000000a
Group State: active
Array Priority: 0
Path Selection Policy Path Config: {current: yes; preferred: yes}
6ec4d47100683cd11ee336360000000a
Group State: active
Array Priority: 0
6ec4d47100683cd11ee336360000000a
Group State: active
Array Priority: 0


6ec4d47100683cd11ee336360000000a
Group State: off
Array Priority: 0
After the paths are disabled, services are delivered to the local storage system.
Follow-up Procedure
Confirm that read and write I/Os are generated on paths on the application server
and DeviceManager. This indicates that host paths are switched over successfully.
Disconnect the cables between the application server and the heterogeneous
storage system.
Methods of confirming read and write I/Os on the application server are as
follows:
● ESXi 5.X
a. Use the vCenter client to take over an ESXi host. Click the host and
choose Performance > Advanced.
b. Select Storage path for Switch to on the right.
c. In the Performance Chart Legend area, select Average of the path
Object that you want to view and confirm whether read and write I/Os
exist on the corresponding path.
NOTE
Object corresponds to Runtime Name of a path.
● ESXi 6.X
a. Use the web client to take over an ESXi host. Click the host and choose
Monitor > Performance > Advanced.

b. Select Storage path for View on the right.

c. In the Performance Chart Legend area, select Average of the path
Object that you want to view and confirm whether read and write I/Os
exist on the corresponding path.
6.7.4 Confirming the Completion of the Host Path Switchover

Run the related command in the local storage system to ensure that I/Os are
transmitted through the paths between the local storage and the application
server.
Precautions
The operation of checking whether a host path is switched over successfully needs
to be performed in developer mode on the CLI management interface of the local
storage system, and this operation can be only performed by Huawei technical
support.
Before performing this operation, ensure that you have checked the multipathing
software status and switched over host paths. Otherwise, this operation may have
risks such as data inconsistency and service interruption.
Procedure
the developer mode.
Step 2 Run the change lun_takeover finish_switch_path lun_id=<id> command to

ensure that I/Os are transmitted through the paths between the local storage and

NOTE
model.
----End
6.8 Clearing the Path Switchover Property of the

eDevLUNs that Are Masqueraded
Clear the path switchover property of the eDevLUNs that are masqueraded and
convert them into common LUNs so that other online takeover tasks can be
executed.
Precautions
This operation needs to be performed in developer mode on the CLI management
interface of the local storage system, and this operation can be only performed by
Context
After the path switchover property of an eDevLUN that is masqueraded is cleared,
the storage system where the LUN resides can be used as a heterogeneous storage
system to configure other online takeover tasks.
Procedure
the developer mode.
Step 2 Run the change lun_takeover disable_switch_path lun_id=lunid command to

clear the properties of the eDevLUNs that are masqueraded.
NOTE
model.
----End

Follow-up Procedure
● Run the debug command to go to the diagnostic view. In the diagnostic view,
run the lun showctrl command to check whether the properties of the
masqueraded eDevLUNs are cleared successfully. The format of the lun
showctrl command is lun showctrl lunid. For example, run lun showctrl 1. If
both Is Dst LUN and Edev LUN bypass cache are displayed as no in the
command output, the properties of the masqueraded eDevLUNs are cleared
successfully.
NOTE
model.
● Do not restore the connection (command or physical cable) between the
application server and heterogeneous storage system. Otherwise, data on
external LUNs may become inconsistent.
● After a successful takeover, configure the native multipathing software of the
operating system in the local storage system based on suggestions in Huawei
Storage Interoperability Navigator. If online migration is required after a
takeover, configure the multipathing software after the migration completes.

OceanStor Dorado
SmartVirtualization Feature Guide 7 Configuring Data Migration
7 Configuring Data Migration
After a heterogeneous storage system (legacy storage system) is replaced with a

local storage system (new storage system), use SmartVirtualization to manage the
service LUNs in the heterogeneous storage system and leverage SmartMigration to
migrate data from the service LUNs in the heterogeneous storage system to the
local storage system. In this way, the local storage system carries services
originally running on the heterogeneous storage system.
Procedure for configuring data migration:
1. Check the license file.

Before configuring SmartMigration, ensure that the SmartMigration license is
contained on the license file list.
2. Install and deploy the storage systems.
Ensure that the physical connection between the local storage system and
heterogeneous storage system is correct.
3. Configure the heterogeneous storage system.
Map the service LUNs from the heterogeneous storage system to the local
storage system.
4. Configure the local storage system.
Create eDevLUNs to host the service LUNs in the heterogeneous storage
system.
NOTICE
Before migration is complete, do not configure other value-added features on

eDevLUNs.
5. Configure SmartMigration.
Configure SmartMigration for the local storage system and migrate data from
the heterogeneous storage system to the local system. In this process, the
source LUN is the eDevLUN (in the local storage system) that takes over the
service LUN from the heterogeneous storage system. The target LUN is the
LUN that is created in the local storage system.

OceanStor Dorado
SmartVirtualization Feature Guide 7 Configuring Data Migration
6. Optional: If the UltraPath version is earlier than V100R008C20 and you need
to use new functions of the local storage system, stop services on the
application server and upgrade the UltraPath.
As eDevLUNs with masquerading properties cannot use some functions of the
local storage system and modifying masquerading properties requires service
suspension, you can modify the extended properties of eDevLUNs to No
Masquerading when upgrading the UltraPath after services are suspended. If
you upgrade UltraPath not for using new functions, you do not need to
modify the masquerading properties of eDevLUNs.
7. After a third-party heterogeneous storage system is taken over online and the
migration is successful, configure the native multipathing software of the
operating system in the local storage system based on suggestions in Huawei
Storage Interoperability Navigator.
NOTE
● For detailed steps of 1 to 4, see descriptions in 3 Taking Over Huawei Heterogeneous

Storage Systems in Offline Mode, 4 Taking Over Third-Party Heterogeneous
Storage Systems in Offline Mode, 5 Taking Over Huawei Heterogeneous Storage
Systems in Online Mode, or 6 Taking Over Third-Party Heterogeneous Storage
Systems in Online Mode.
● For detailed steps of 5, see OceanStor Dorado 6.0.0 SmartMigration Feature Guide.
● For detailed steps of 6, see the content about using UltraPath in 13.19.4 Other Types of
Huawei Storage Systems.

OceanStor Dorado
SmartVirtualization Feature Guide 8 Configuring Cold Data Migration
8 Configuring Cold Data Migration
When a local storage system (new storage system) is used to replace a

heterogeneous storage system (legacy storage system) to carry service data, the
local storage system has a large amount of cold data (data that is rarely
accessed), so the storage resource utilization is low and storage space is wasted.
SmartVirtualization can work with SmartMigration to migrate cold data to the
heterogeneous storage system. In this way, storage space on the local storage
system is released.
Procedure for configuring cold data migration:
1. Configure the heterogeneous storage system.
Create a LUN in the heterogeneous storage system and map the LUN to the
2. Configure the local storage system.
Create an eDevLUN to take over the LUN created in the heterogeneous
storage system.
3. Configure SmartMigration.
Configure SmartMigration in the local storage system to migrate cold data of
the local storage system to the heterogeneous storage system. In this process,
the LUN where cold data resides serves as the source LUN, and the LUN
created on the heterogeneous storage system serves as the target LUN.
NOTE
● For detailed steps of 1 to 2, see descriptions in 3 Taking Over Huawei Heterogeneous

Storage Systems in Offline Mode, 4 Taking Over Third-Party Heterogeneous
Storage Systems in Offline Mode, 5 Taking Over Huawei Heterogeneous Storage
Systems in Online Mode, or 6 Taking Over Third-Party Heterogeneous Storage
Systems in Online Mode.
● For details about 3, see OceanStor Dorado 6.0.0 SmartMigration Feature Guide.

OceanStor Dorado
SmartVirtualization Feature Guide 9 Configuration Example
9 Configuration Example
SmartVirtualization is typically used to manage heterogeneous storage resources

in a unified manner. It can also be used with SmartMigration to migrate data. The
configuration processes in actual application scenarios are described to help you
understand how to use SmartVirtualization.
9.1 Using SmartMigration and SmartVirtualization to Migrate an Oracle ASM File
System
9.2 Using SmartVirtualization to Centrally Manage Heterogeneous Storage
Systems for an Oracle Database
9.1 Using SmartMigration and SmartVirtualization to

Migrate an Oracle ASM File System
This configuration example introduces how to use SmartVirtualization and
SmartMigration to migrate an Oracle ASM file system. Details of the requirement
analysis, configuration planning, configuration operations, and configuration
verification can be found in this section.
9.1.1 Requirement Analysis

Before implementing data migration, analyze service requirements, make a
service-related plan, and determine an implementation solution, so that data
migration can be implemented as smoothly as possible.
Requirement Source
● Service introduction
An enterprise has three storage systems: Huawei OceanStor Dorado 6000 V6,
HDS USP-V storage system, and S5600T V100R005 storage system. The
OceanStor Dorado 6000 V6 storage system is newly purchased and no service
is running on it. In addition, the assets management information system and
archive&backup system are running on the two storage systems respectively.
– The asset management information system, which is served by an Oracle
database, records the enterprise's asset information.
– The archive&backup system archives service data that is infrequently
accessed.

OceanStor Dorado
Table 9-1 lists the hardware components of the asset management

information system and the archive&backup system.
Table 9-1 Hardware components of service systems
System Name Hardware Component
Asset ● AIX-based application server

management ● HDS USP-V storage system
information
system
Archive&backup ● AIX-based application servera

system
● S5600T storage system V100R005b
a: The asset management information system and the archive&backup

system run on the same AIX-based application server.
b: The S5600T only runs basic storage services. No value-added services
are in use.
Figure 9-1 shows the network where the two service systems are
deployed.
Figure 9-1 Existing network
AIX-based application server
Fibre Channel
switch
HDS USP-V storage OceanStor S5600T

Table 9-2 lists the zones created to ensure normal communication

between the AIX-based application server and each storage system.

OceanStor Dorado
Table 9-2 Network zoning
Zone Name Included Node
Zone1 The AIX-based application server and the HDS USP-V
Zone2 The AIX-based application server and the S5600T
Table 9-3 lists the LUN configuration of the HDS UPS-V.
Table 9-3 LUN configuration of the HDS UPS-V
LUN Name LUN Capacity Function
LUN_HDS1 340 GB Stores Oracle Cluster

Registry (OCR) files of the
Oracle database.
LUN_HDS2 1.9 TB Stores data files of the

Oracle database.
● Service requirements
As the enterprise keeps growing, an ever-increasing amount of asset
management information needs to be recorded. The HDS USP-V has been
used for a long time. Its lifecycle is about to end, and its storage space is
about to be used up. The customer wants to migrate the asset management
information system to the S5600T. The asset management information system
stores non-critical data. Therefore, the S5600T can meet the performance
requirement, and existing storage resources can be reused.
Specific customer requirements are as follows:
– Data should be migrated to the S5600T non-disruptively.
– Data should be migrated during off-peak hours at night.
– After data is migrated, the S5600T can take over the asset management
information system from the HDS USP-V.
Requirement Analysis and Conclusions

It can be inferred from the customer requirements that an inter-storage-system
data migration solution suits the customer. The following value-added features
provided by Huawei storage systems can be used for data migration:
HyperReplication and SmartMigration. Table 9-4 describes the data copy
characteristics and typical application scenarios of these features.
Table 9-4 Feature selection analysis
Consideration HyperReplication SmartMigration
Storage system support Between storage systems Within a storage system

and between storage
systems

OceanStor Dorado
Consideration HyperReplication SmartMigration
Typical application Data backup and Data migration

scenarios disaster recovery
Impact of data migration - Online data migration is

on system services implemented without
affecting services.
● Conclusion 1: The customer needs to migrate data between storage systems.

It can be concluded from the preceding table that SmartMigration can
address the need. However, the license file in the S5600T used by the
customer does not grant permission to use value-added features. Therefore,
the customer cannot use SmartMigration to migrate data from the HDS USP-
V to the S5600T.
● Conclusion 2: The customer wants online data migration. Therefore,
SmartMigration can address the need.
● Conclusion 3: The customer requires data to be migrated during off-peak
hours. Therefore, the migration speed can be set to High for higher data
migration efficiency.
The S5600T does not contain a SmartMigration license. Therefore, the customer
cannot use SmartMigration to migrate data from the HDS USP-V to the S5600T.
The OceanStor Dorado 6000 V6 storage system purchased by the customer
supports SmartVirtualization and SmartMigration. Therefore, data can be migrated
using the following method:
1. Use the OceanStor Dorado 6000 V6 to take over LUNs created on the HDS
USP-V and the S5600T, and create eDevLUNs corresponding to these LUNs.
2. On the OceanStor Dorado 6000 V6, configure SmartMigration for eDevLUNs
to migrate data.
NOTE
9.1.2 Configuration Planning

Before migrating data, make network and service plans to facilitate subsequent
operations.
Network Planning
According to the requirement analysis, the OceanStor Dorado 6000 V6 is used to
take over LUNs created on the HDS USP-V and the S5600T. Before configuring
data migration, the customer needs to connect the OceanStor Dorado 6000 V6 to
the existing network. Figure 9-2 shows the transformed network.

OceanStor Dorado
Figure 9-2 Transformed network

AIX-based
application server
Fibre Channel switch
HDS USP-V storage Dorado 6000 V6 OceanStor S5600T

system storage system storage system
Table 9-5 lists the zones created to ensure normal communication among storage
systems and the application server.
Table 9-5 Zoning

Zone1' The AIX-based application server and the OceanStor Dorado

6000 V6
Zone2' The OceanStor Dorado 6000 V6 and the HDS USP-V
Zone3' The OceanStor Dorado 6000 V6 and the S5600T
Service Planning
From the conclusions of the requirement analysis, it can be inferred that the
enterprise uses SmartVirtualization and SmartMigration to migrate data. Figure
9-3 illustrates the configuration roadmap.

OceanStor Dorado
Figure 9-3 Configuration roadmap

Start
Connect the Dorado 6000 V6

storage system to the network.
Change the network.
Create zones on the Fibre Channel
switch.
Create target LUNs for the data
migration. Set up a logical connection
between the Dorado 6000 V6 and
HDS USP-V.
Set up a logical connection
between storage systems. Set up a logical connection
between Dorado 6000 V6 and
S5600T.
Check the feature license.
Start LUN scanning.

Enable the Dorado 6000 V6 to host
LUNs created on the HDS USP-V.
Create eDevLUNs.
Delete the multipathing software

delivered with the HDS USP-V.
Stop services running on the HDS Close the database.

USP-V.
Remove the AIX-based application
server and the HDS USP-V from
their joint zone.
Install Huawei UltraPath.

Set up a mapping relationship
between the AIX-based application
Enable the Dorado 6000 V6 to take server and the eDevLUNs
over services. corresponding to LUNs created on
the HDS USP-V.
Search for LUNs on the AIX-based
application server.
Create a SmartMigration task for

eDevLUN_HDS1 and
eDevLUN_Target_HDS1.
Use SmartMigration to set up a
data migration relationship. Create a SmartMigration task for
eDevLUN_HDS2 and
eDevLUN_Target_HDS2.
Close the database.
Stop services running on the Remove the AIX-based application

Dorado 6000 V6. server and the Dorado 6000 V6
from their joint zone.
Set up a mapping relationship

between the AIX-based application
server and the target LUNs created
Enable the S5600T to take over on the S5600T.
services. Scan for LUNs on the AIX-based
application server.
End
Table 9-6 describes the configuration operations and plan items.

OceanStor Dorado
Table 9-6 Configuration operations and plan items

Configuratio Major Plan Item GUI Planned
n Roadmap Operation Parameter Value
and Purpose
Change the Connect the None None None

network. OceanStor
Dorado 6000
V6 to the
existing
network.
Create zones Zone names None Planned

on the Fibre and nodes based on
Channel included in Table 9-5
switch. each zone
Create target On the ● Names of ● Name ● Target_LU

LUNs for the S5600T, create target ● Capacity N_HDS1
data two LUNs to LUNs and
migration act as target ● Capacities Target_LU
LUNs for the of target N_HDS2
data LUNs ● 500 GB
migration. and 3 TB
NOTE
To meet
future data
growth needs,
it is
recommended
that the
capacities of
the target
LUNs be
larger than
the original
LUNs on the
HDS USP-V.

OceanStor Dorado

and Purpose
Set up a Set up a None None None

logical logical
connection connection
between between the
storage OceanStor
systems. Dorado 6000
V6 and the
HDS USP-V.

OceanStor Dorado

and Purpose
NOTE
● For details
about how
to map the
LUNs of an
HDS USP-V
storage
system to
an
OceanStor
Dorado
6000 V6
storage
system,
see the
specific
HDS USP-V
user guide.
● For the
precaution
s about
configurati
on
operations
on the
HDS USP-V
storage
system,
see the
section
about HDS
USP/NSC
Series/HDS
USP-V/
USP-
VM/SUN
9985/9985
V/
9990/9990
V/HP
SVS200/
XP10000/1
2000/2000
0/240000
in the
SmartVirtu
alization
feature
guide.

OceanStor Dorado

and Purpose
Set up a ● Host group ● Host ● Host_group

logical correspond Group _1
connection ing to the Name ● Host_1
between the OceanStor ● Host
OceanStor Dorado ● Linux
Name
Dorado 6000 6000 V6 ● 22130022a
V6 and the ● OS 100c890
● Host
S5600T. correspond ● Identifier ● Target_LU
NOTE ing to the ● LUN Name N_HDS1
After the OceanStor and
OceanStor Target_LU
Dorado
Dorado 6000
V6 is 6000 V6 N_HDS2
connected to ● Initiator
the S5600T, correspond
the S5600T
ing to the
identifies the
OceanStor front-end
Dorado 6000 port on the
V6 as a host. OceanStor
Dorado
6000 V6
connected
to the
S5600T
● Names of
the LUNs
that need
to be
mapped to
the
OceanStor
Dorado
6000 V6

OceanStor Dorado

and Purpose
Enable the Use the ● Remote ● Name (of ● HDS USP-V

OceanStor OceanStor device a remote ● 60:02:2A:
Dorado 6000 Dorado 6000 name of device) 11:00:06:8d
V6 to host V6 to host the HDS ● WWN (of :fe:
LUNs created LUNs created USP-V a remote 07:a4:a4:6d
on the on the HDS ● WWNs of LUN) :
original USP-V, and the LUNs 26:00:00:00
storage create ● Name (of
mapped to an :73 and
systems. eDevLUNs the 60:02:2A:
corresponding eDevLUN)
OceanStor 11:00:06:8d
to these LUNs. Dorado ● Owning :fe:
6000 V6 Storage 07:a4:a4:6d
for hosting Pool :
purposes ● Storage 26:00:00:00
● Names of Medium :74
eDevLUNs and RAID ● eDevLUN_
to be Policy HDS1 and
created ● Capacity eDevLUN_
● Storage (of a HDS2
pool to storage ● StoragePoo
which pool) l1
eDevLUNs ● SSDs with
belong RAID 5 (4D
+1P)
● 1 TB

OceanStor Dorado

and Purpose
Use the ● Remote ● Name (of ● S5600T

OceanStor device a remote ● 60:02:2A:
Dorado 6000 name of device) 11:00:06:8d
V6 to host the S5600T ● WWN (of :fe:
LUNs created ● WWNs of a remote 07:a4:a4:6d
on the the LUNs LUN) :
S5600T, and mapped to 26:00:00:00
create ● Name (of
the an :75 and
eDevLUNs OceanStor 60:02:2A:
corresponding eDevLUN)
Dorado 11:00:06:8d
to these LUNs. 6000 V6 ● Owning :fe:
for hosting Storage 07:a4:a4:6d
purposes Pool :
● Names of ● Storage 26:00:00:00
eDevLUNs Medium :76
to be and RAID ● eDevLUN_
created Policy Target_HD
● Storage ● Capacity S1 and
pool to (of a eDevLUN_
which storage Target_HD
eDevLUNs pool) S2
belong ● StoragePoo
l1
● SSDs with
RAID 5 (4D
+1P)
● 1 TB
Stop services Delete the None None None

running on HDLM
the HDS multipathing
USP-V. software
delivered with
the HDS USP-
V.
Close the None None None

database.
Remove the None None None

AIX-based
application
server and the
HDS USP-V
from their
joint zone.

OceanStor Dorado

and Purpose
Enable the Install Version of None None

OceanStor OceanStor OceanStor
Dorado 6000 UltraPath. UltraPath to
V6 to take be installed
over services.

OceanStor Dorado

and Purpose
Set up a ● Name of ● Name (of ● Host_AIX

mapping the host a host) ● AIX
relationship correspond ● OS
between the ing to the ● HostGroup
AIX-based AIX-based ● Name (of _001
application application a host ● FC and
server and the server group) 200330d17
eDevLUNs ● Operating ● Initiator eb4f761
corresponding system of Type and ● LUNGroup_
to LUNs the host WWPN/IQ 001
created on the correspond N (including
HDS USP-V. ing to the ● Name (of eDevLUN_
AIX-based a LUN HDS1 and
application group) eDevLUN_
server ● Name (of HDS2)
● Name of a mapping ● MappingVi
the host view) ew_001
group to
which the
host
correspond
ing to the
AIX-based
application
server
belongs
● Type and
identifier
of the
initiator
correspond
ing to the
HBA port
on the AIX-
based
application
server
connected
to the
OceanStor
Dorado
6000 V6
● Names of
the LUNs
mapped to
the AIX-
based

OceanStor Dorado

and Purpose
application
server and
name of
the LUN
group to
which the
LUNs
belong
● Name of
the
mapping
view
created for
the host
group and
LUN group
Scan for LUNs None None None

on the AIX-
based
application
server.
Use Configure ● Source ● Source ● eDevLUN_

SmartMigrati SmartMigratio LUNs LUN Name HDS1 and
on to set up n. involved in ● Target eDevLUN_
a data SmartMigr LUN Name HDS2
migration ation ● eDevLUN_
relationship. ● Migration
● Target Speed Target_HD
LUNs S1 and
involved in eDevLUN_
SmartMigr Target_HD
ation S2
● Data (correspon
migration ding to the
speed preceding
source
LUNs)
● High
Stop services Close the None None None

running on database.
the
OceanStor
Dorado 6000
V6.

OceanStor Dorado

and Purpose
Remove the None None None

OceanStor
Dorado 6000
V6 and the
AIX-based
application
server from
their joint
zone.

OceanStor Dorado

and Purpose
Enable the Set up a ● Name of ● Host ● Host_AIX1

S5600T to mapping the host Name ● AIX
take over relationship correspond ● OS
services. between the ing to the ● HostGroup
AIX-based AIX-based ● Host _002
application application Group ● 221312345
server and the server Name 6789123
target LUNs ● Operating ● Identifier ● Target_LU
created on the system of ● LUN Name N_HDS1
S5600T. the host and
correspond Target_LU
ing to the N_HDS2
AIX-based
application
server
● Name of
the host
correspond
ing to the
AIX-based
application
server
● Identifier
of the
initiator
correspond
ing to the
HBA port
on the AIX-
based
application
server
connected
to the
S5600T
● Names of
the LUNs
mapped to
the AIX-
based
application
server

OceanStor Dorado

and Purpose
Scan for LUNs None None None

on the AIX-
based
application
server.
a: The description in the brackets after a parameter indicates the object of the
parameter.
NOTE
Retain the default values for the parameters not mentioned in Table 9-6.
9.1.3 Configuration Operations

After planning the network and services, complete specific configurations on the
application server and storage systems, so that data can be migrated based on
SmartVirtualization and SmartMigration.
Procedure
Step 1 Change the network.
1. Connect OceanStor Dorado 6000 V6 to the existing network as the network
diagram shown in Figure 9-2.
2. Create zones on the Fibre Channel switch to ensure normal communication
among the HDS USP-V, S5600T, OceanStor Dorado 6000 V6, and AIX-based
application server.
NOTE
For details about how to create zones on the Fibre Channel switch, refer to the user manual
of the Fibre Channel switch.
Step 2 Log in to the S5600T, and create target LUNs for data migration.
Navigation path: Choose Storage Resources > LUNs > Create > LUN.

OceanStor Dorado
NOTE
The preceding figure shows the parameter settings of Target_LUN_HDS1. When you create
Target_LUN_HDS2, set parameters as follows:
● Set Name to Target_LUN_HDS2.
● Set Capacity to 1 TB.
Step 3 Set up a logical connection between storage systems.

1. Set up a logical connection between the OceanStor Dorado 6000 V6 and the
HDS USP-V.
After you allocate the OceanStor Dorado 6000 V6 and the HDS USP-V to the
same zone, the HDS USP-V automatically identifies the initiator corresponding
to the OceanStor Dorado 6000 V6 and sets up a logical connection.
2. Log in to the S5600T, and set up a logical connection between the OceanStor
Dorado 6000 V6 and the S5600T.
a. Create a host group corresponding to the OceanStor Dorado 6000 V6.
Navigation path: Choose SAN Services > Mappings > Host Groups >
Create.

OceanStor Dorado
b. Create a host corresponding to the OceanStor Dorado 6000 V6.

Navigation path: Choose SAN Services > Mappings > Hosts > Create.
c. Map the target LUNs created on the S5600T to the host corresponding to
the OceanStor Dorado 6000 V6.
Navigation path: Choose SAN Services > Mappings > Hosts, select the
host whose Name is Host_1, and choose Mapping > Add LUN Mapping
in the navigation bar.

OceanStor Dorado
Step 4 Log in to the OceanStor Dorado 6000 V6, and check whether the
SmartVirtualization and SmartMigration licenses are valid.
Navigation path: Choose Settings > License Management.
Step 5 Use the OceanStor Dorado 6000 V6 to host LUNs created on the HDS USP-V and
the S5600T.
1. Create a storage pool that is used to create eDevLUNs.
Navigation path: Choose System > Storage Pools > Create.
2. Initiate automatic LUN scanning.
Navigation path: Choose System > External Storage, select the remote device
whose Name is HDS USP-V, and click Scan for External LUN.
3. Create eDevLUNs.
whose Name is HDS USP-V, and click Create eDevLUN.
NOTE
The preceding operations are performed to enable the OceanStor Dorado 6000 V6 to
host LUNs created on the HDS USP-V. To enable the OceanStor Dorado 6000 V6 to
host LUNs created on the S5600T, set parameters as follows:
– Set Name of the remote device to S5600T.
– Set WWNs of the remote LUNs to 60:02:2A:11:00:06:8d:fe:07:a4:a4:6d:
26:00:00:00:75 and 60:02:2A:11:00:06:8d:fe:07:a4:a4:6d:26:00:00:00:76.
– Set Name of eDevLUNs to eDevLUN_Target_HDS1 and eDevLUN_Target_HDS2.
– Set Storage Pool to which the eDevLUNs belong to StoragePool1.
Step 6 On the AIX-based application server, perform the following operations to stop
services running on the HDS USP-V:
1. Close the database and enable the file system to go offline.
2. Delete the LUNs mapped from the HDS USP-V and the multipathing software
delivered with the HDS USP-V.
rmdev -dl hdiskX//Delete the LUNs mapped to the application server.

OceanStor Dorado
smitty remove//Delete the multipathing software delivered with the HDS

USP-V.
lslpp -l | grep -i dlmanager//Check whether the multipathing software is
deleted. If no command output is displayed, the multipathing software is
successfully deleted.
3. Remove the AIX-based application server and the HDS USP-V from their joint
zone.
4. Restart the AIX-based application server.
Step 7 Enable the OceanStor Dorado 6000 V6 to take over services.
1. Install Huawei UltraPath on the AIX-based application server.
NOTE
For details about the operation procedure, see the relevant UltraPath user guide
(applicable to the AIX operating system).
2. Log in to the OceanStor Dorado 6000 V6, and set up a mapping relationship
between the AIX-based application server and eDevLUN_HDS1 as well as
between the AIX-based application server and eDevLUN_HDS2.
Perform the following operations:
a. Create a host.
Navigation path: Choose Services > Block Service > Hosts > Hosts >
Create > Create Host.
b. Create a host group.
Navigation path: Choose Services > Block Service > Hosts > Host
Groups > Create.
c. Create a LUN group.
Navigation path: Choose Services > Block Service > LUN Groups >
Create.
d. Create a mapping.
Navigation path: Choose Services > Block Service > Hosts.
3. On the AIX-based application server, scan for LUNs and start the database.
cfgmgr//Scan for mapped logical disks.
show vlun//Query LUN information.
importvg -y prod hdiskX//Import VG information into the ODM library.
mount /dev/prodlv /Oracle//Mount the file system.
Step 8 Use SmartMigration to set up a data migration relationship between source LUNs
(eDevLUN_HDS1 and eDevLUN_HDS2) and target LUNs (eDevLUN_Target_HDS1
and eDevLUN_Target_HDS2).
Navigation path: Choose Services > Resource Tuning >SmartMigration > Create.

OceanStor Dorado
NOTE
The preceding operations are performed to set up a data migration relationship between
eDevLUN_HDS1 and eDevLUN_Target_HDS1. To set up a data migration relationship
between eDevLUN_HDS2 and eDevLUN_Target_HDS2, set parameters as follows:
● Source LUN: eDevLUN_HDS2
● Target LUN: eDevLUN_Target_HDS2
● Migration speed: High
Step 9 After data migration is complete, stop services running on the OceanStor Dorado
6000 V6.
1. Close the database and enable the file system to go offline.
2. Remove the OceanStor Dorado 6000 V6 and the AIX-based application server
from their joint zone.
Step 10 Enable the S5600T to take over services.
1. Log in to the S5600T, and set up a mapping relationship between the AIX-
based application server and Target_LUN_HDS1 as well as between the AIX-
based application server and Target_LUN_HDS2.
a. Create a host group.
Navigation path: Choose SAN Services > Mappings > Host Groups >
Create.
b. Create a host.
Navigation path: Choose SAN Services > Mappings > Hosts > Create.

OceanStor Dorado
c. Add LUN mappings.

Navigation path: Choose SAN Services > Mappings > Hosts, select the
host whose Name is Host_AIX1, and choose Mapping > Add LUN
Mapping in the navigation bar.
2. On the AIX-based application server, scan for LUNs.

cfgmgr//Scan for mapped logical disks.
show vlun//Query LUN information.
importvg -y prod hdiskX//Import VG information into the ODM library.
mount /dev/prodlv /Oracle//Mount the file system.
----End

OceanStor Dorado
9.1.4 Configuration Verification

After the file system is mounted, start the Oracle database to check whether data
migration is successful.
Procedure
Step 1 Log in to the AIX-based application server.
Step 2 Start the Oracle database and check whether it can successfully start.
su - oracle//Log in as user oracle.
echo $ORACLE_SID//View the current ORACLE_SID.
export ORACLE_SID=XXX//Specify a database instance.
sqlplus /nolog//Run the nolog command to enter the sqlplus environment.
conn as sysdba//Log in to the database as an administrator. (You must obtain the user name and password
of an administrator account.)
startup//Start the current database instance.
lsnrctl start//Start listening. If "Success" is displayed, the database successfully starts.
● If Success is displayed, data is successfully migrated from the HDS USP-V to

the S5600T.
● If Success is not displayed, the data migration failed. Check whether the
configuration operations are correctly performed.
----End
9.2 Using SmartVirtualization to Centrally Manage

Heterogeneous Storage Systems for an Oracle
Database
This configuration example introduces how to use SmartVirtualization to centrally
manage storage resources on a local storage system and a heterogeneous storage
system for Oracle Database 11g. Details of the requirement analysis, configuration
planning, configuration operations, and configuration verification can be found in
this section.
9.2.1 Requirement Analysis

Before centrally managing storage resources, analyze service requirements, make a
service-related plan, and determine an implementation solution, so that storage
resources can be managed as smoothly as possible.
Requirement Source
● Service introduction
A university owns a campus cloud storage system and a library storage
system.
These two systems contain the following hardware components:
– IBM Power 740 servers, running the Oracle RAC database system
– EMC VNX5500 storage system
Figure 9-4 shows the network where the two service systems are
deployed.

OceanStor Dorado
Figure 9-4 Existing network
IBM Power 740 IBM Power 740
EMC VNX5500 storage

system
Table 9-7 lists the LUN configuration of the EMC VNX5500 storage system.
Table 9-7 LUN configuration of the EMC VNX5500 storage system

LUN Name LUN Capacity Function
LUN_VNX1 340 GB Stores OCR files of the Oracle

database.
LUN_VNX2 1.9 TB Stores data files of the Oracle

database.
● Service requirements
As the university's service data volume increases, the storage system where
the database resides is pushing the limits against capacity and performance,
and struggling to cope with growing management and capacity expansion
complexities.
Specific customer requirements are as follows:
– Improved system capacity and performance
– Reuse of the existing storage system to protect the investment cost
– Central management of the existing and new storage systems to reduce
the management complexity
– Minimized service disruption
– No single point of failure in links
Requirement Analysis and Conclusions

The customer requirements are concluded as follows:

OceanStor Dorado
● Conclusion 1: Connect an OceanStor Dorado V6 series with

SmartVirtualization enabled to the existing storage system.
● Conclusion 2: Use the OceanStor Dorado V6 series to host LUNs created on
the EMC VNX5500.
● Conclusion 3: Provide the storage space of the OceanStor Dorado V6 series to
the IBM Power 740 servers for service acceleration.
● Conclusion 4: Change the existing direct connection network to a Fibre
Channel switch connection network.
9.2.2 Configuration Planning

Before centrally managing storage resources, make network and service plans to
facilitate subsequent operations.
Network Planning
According to the requirement analysis, the OceanStor Dorado V6 series needs to
be deployed to host LUNs created on the EMC VNX5500, and the existing direct
connection network needs to be restructured into a Fibre Channel switch
connection network. Before configuring central resource management, the
customer needs to connect the OceanStor Dorado V6 series to the existing
network. Figure 9-5 shows the new network.
Figure 9-5 New network

IBM Power 740 IBM Power 740
Fibre Channel switch Fibre Channel switch
EMC VNX5500 storage

OceanStor storage system
system
Table 9-8 lists the zones created to ensure normal communication among storage
systems and application servers.

OceanStor Dorado
Table 9-8 Zoning

Zone1 One IBM Power 740 server and the EMC VNX5500
Zone2 The other IBM Power 740 server and the OceanStor Dorado
V6 series
Zone3 The EMC VNX5500 and the OceanStor Dorado V6 series
Service Planning
From the conclusions of the requirement analysis, it can be inferred that the
university uses SmartVirtualization of the OceanStor Dorado V6 series to take over
the Oracle database services from the EMC VNX5500. Figure 9-6 illustrates the
configuration roadmap.

OceanStor Dorado
Figure 9-6 Configuration roadmap
Table 9-9 describes the configuration operations and plan items.

OceanStor Dorado
Table 9-9 Configuration operations and plan items

and Purpose
Collect 1. Collect the None None None

information file system
before taking and disk
over informatio
database n.
services. 2. Collect the
database
informatio
n.
Stop 1. Check the None None None

database value of
services. ASM
diskstring.
2. Stop all
CRS
services.
3. Shut down
the IBM
Power 740
servers
(Oracle
hosts).
Delete the Delete the None None None

mappings LUN
between the mappings
heterogeneo between the
us storage EMC VNX
system and 5500 and the
the Oracle Oracle hosts.
hosts.
Check the Check the SmartVirtualiz Feature SmartVirtualiz

license file license file ation ation
for feature for the information in
information. information the license file
about
SmartVirtuali
zation.
Change the Connect the None None None

network. OceanStor
Dorado V6
series to the
existing
network.

OceanStor Dorado

and Purpose
Create zones Zone names None Planned based

on Fibre and nodes on Table 9-8.
Channel included in
switches. each zone
Install Install None None None

Huawei Huawei
UltraPath. UltraPath on
the Oracle
hosts.
Set up a Set up a None None None

logical logical
connection connection
between between the
storage OceanStor
systems. Dorado V6
series and
the EMC
VNX5500.
Enable the Configure ● Remote ● Name (of ● EMC

OceanStor eDevLUNs on device a remote VNX5500
Dorado V6 the name device) ● 60:02:2A:
series to host OceanStor correspondi ● WWN (of 11:00:06:8d
LUNs created Dorado V6 ng to the a remote :fe:
on the series. The EMC LUN) 07:a4:26:00
heterogeneo Oracle hosts VNX5500 :00:00:73
us storage employ the ● Name (of
● WWNs of an and
system. OceanStor the LUNs 60:02:2A:
Dorado V6 eDevLUN)
mapped to 11:00:06:8d
series as a the ● Owning :f43
bridge to use OceanStor Storage
the LUN Pool ● eDevLUN_V
Dorado V6 NX1 and
resources on series for ● Storage
the EMC eDevLUN_V
hosting Medium NX2
VNX5500. purposes and RAID
Policy ● StoragePoo
● Names of l1
eDevLUNs ● Capacity
to be (of a ● SSDs with
created storage RAID 5 (4D
pool) +1P)
● Storage
pool to ● 1 TB
which
eDevLUNs
belong

OceanStor Dorado

and Purpose
Enable the None None None

Oracle hosts
to scan for
LUNs.
9.2.3 Configuration Operations

After planning the network and services, complete specific configurations on the
application servers and storage systems, so that storage resources on the local
storage system and heterogeneous storage system can be centrally managed
based on SmartVirtualization.
Procedure
Step 1 Collect information about the IBM Power 740 servers (Oracle hosts) before
switching database services.
1. Collect the file system and disk information.
a. Run the lspv-u command as user root to record the mapping relationship
between the EMC VNX5500 LUNs and the Oracle host hdisks.
b. Run the lsattr -El hdiskx command to collect the properties of each
Oracle host hdisk.
▪ x in the lsattr -El hdiskx command indicates a drive letter.

c. Collect the file system information.
Run the mount, df, and cat /etc/filesystems commands in sequence.
d. Run the ls -l /dev |grep disk command to collect the permission
information.
2. Collect the database information.
a. Run the ocrcheck command as user grid to collect the database OCR
information.
Then run the ocrconfig -showbackup command as user grid to back up
the database OCR information. If any fault occurs, run the ocrconfig -
restore command as user grid to restore the OCR information.
b. Run the crsctl query css votedisk command to collect the Voting Disk
information.
c. Log in to the database as a system user and go to the ASM instance. Run
the show parameter asm_diskstring command to collect the
asm_diskstring settings in ASM. Run the select path from v$asm_disk;
command to collect the disk information in the ASM disk groups.
d. Run the archive log list; command to collect the Oracle archive mode.
e. Run the select name from v$controlfile; command to collect the control
file information.

OceanStor Dorado
f. Run the select name from v$datafile; command to collect the data file
information.
g. Run the select member from v$logfile; command to collect the log file
information.
h. Run the select name from v$tempfile; command to collect the
temporary file information.
Step 2 Stop database services on the Oracle hosts.
1. Log in to the database as a system user and go to the ASM instance. Run the
show parameter spfile command to view the ASM diskstring value.
– If the current ASM instance is not using an spfile file, the value in the
command output is empty. Then perform the following operations:
i. Run the vi command to edit the $ORACLE_HOME/dbs/init+ASM.ora
file and set asm_diskstring='/dev/rhdisk*'.
ii. Shut down the database and ASM instance.
– If the current ASM instance is using an spfile file, the value in the
command output indicates the location of the spfile file. Then perform
the following operations:
i. Go to the ASM instance. Run the create pfile from spfile; command
to create a pfile file for the ASM instance.
ii. Shut down the database and ASM instance.
iii. Run the vi command to edit the $ORACLE_HOME/dbs/init+ASM.ora
file and set asm_diskstring='/dev/rhdisk*'.
iv. Run the startup pfile='$ORACLE_HOME/dbs/init+ASM1.ORA';
command to start the ASM instance.
v. Run the $mv $ORACLE_HOME/dbs/spfilesxsb1.ora
$ORACLE_HOME/dbs/spfilesxsb1.ora.bak command to move the
spfile file to another location.
vi. Run the create spfile from pfile; command to create an spfile based
on the pfile.
vii. Shut down the ASM instance.
2. Stop all CRS services.
a. Run the crsctl stop cluster command as user root to shut down the
cluster.
b. Run the crs_stat -t -v command to confirm that all CRS services have
been stopped.
c. Run the ps -ef|grep d.bin to confirm that the process has been stopped.
3. Shut down the Oracle hosts.
a. Run the shutdown -Fr command to restart the operating system.
b. Run the crs_stat -t command as user grid. Log in to the database as a
system user. Run the select instance_name,status from v$instance;
command to confirm that the database services are operating properly.
c. Log in to the database as a system user. Run the shutdown immediate;
and exit commands in sequence to shut down the database.
d. Run the crsctl stop cluster command as user root to shut down the
cluster.

OceanStor Dorado
Step 3 Log in to the EMC VNX5500 and delete its LUN mappings to the Oracle hosts.
NOTE
For details, refer to the related EMC documentation.
Step 4 Log in to the OceanStor Dorado V6 series, and check whether the
SmartVirtualization license is valid.
Navigation path: Choose Settings > License Management.
Step 5 Change the network.
1. Based on the network diagram shown in Figure 9-5, connect the OceanStor
Dorado V6 series to the existing network.
2. Create zones on the Fibre Channel switches to ensure normal communication
among the EMC VNX5500, the OceanStor Dorado V6 series, and Oracle hosts.
NOTE
For details about how to create zones on the Fibre Channel switches, refer to the user
manual of the Fibre Channel switch.
Step 6 Install Huawei UltraPath on the Oracle hosts.

NOTE
For details about how to install Huawei UltraPath, see OceanStor UltraPath for AIX
V100R008 User Guide.
Step 7 Set up a logical connection between the OceanStor Dorado V6 series and the EMC
VNX5500.
In the EMC VNX5500 storage system, map LUNs to the OceanStor Dorado V6
series storage system. For details, see the related EMC VNX500 user guide.
Step 8 Enable the OceanStor Dorado V6 series to host LUNs created on the EMC
VNX5500.
1. Create a storage pool for eDevLUNs.
Navigation path: Choose System > Storage Pools > Create.
2. Initiate automatic LUN scanning.
whose Name is EMC VNX5500, and click Scan for External LUN.
3. Create eDevLUNs.
whose Name is EMC VNX5500, and click Create eDevLUN.
4. Set up a mapping relationship between the Oracle hosts and eDevLUN_VNX1
as well as between the Oracle hosts and eDevLUN_VNX2.
a. Create a host.
Navigation path: Choose Services > Block Service > Hosts > Hosts >
Create > Create Host.
b. Create a host group.
Navigation path: Choose Services > Block Service > Hosts > Host
Groups > Create.

OceanStor Dorado
c. Create a LUN group.

Navigation path: Choose Services > Block Service > LUN Groups >
Create.
d. Create a mapping.
Navigation path: Choose Services > Block Service > Hosts.
5. Run the cfgmgr command on each of the Oracle hosts to scan for the
mapped logical disks.
----End
9.2.4 Configuration Verification

After scanning for LUNs on the Oracle hosts, confirm the disk and database
information and restart the database services to check whether heterogeneous
storage resources are centrally managed.
Procedure
Step 1 Check the mapping relationship between host hdisk IDs and LUN WWNs.
1. Before eDevLUN mappings are created, the mapping relationship between the
EMC VNX5500 LUN WWNs and the Oracle host hdisk IDs can be obtained
according to Step 1.1 of 9.2.3 Configuration Operations.
2. Log in to each IBM Power 740 server (Oracle host), and run the lspv-u
command as user root to query the mapping relationship between the Oracle
host hdisk IDs and the OceanStor Dorado V6 series eDevLUN WWNs.
3. Log in to the DeviceManager, and query the mapping relationship between
the OceanStor Dorado V6 series eDevLUN WWNs and the EMC VNX5500 LUN
WWNs.
a. In the navigation bar, choose Storage > LUNs.
b. In the middle function pane, view the WWNs of eDevLUNs.
4. Compare the Oracle host hdisk IDs, the OceanStor Dorado V6 series eDevLUN
WWNs, and EMC VNX5500 LUN WWNs, and make sure they are matched.
If the Oracle host hdisk IDs and EMC VNX5500 LUN WWNs are not matched
after the OceanStor Dorado V6 series eDevLUNs are mapped, delete all LUNs
from the mapping view between the eDevLUNs and host. Then add LUNs one
by one to the mapping view, and trigger a LUN scanning job on the host each
time after a new LUN is added to the mapping view. In this way, the hdisk IDs
are generated in a correct sequence.
Step 2 Add permissions to the host hdisks.
Based on the hdisk permission information collected in Step 1.1 of 9.2.3

Configuration Operations, run the chown hdisk1 -R oracle:dba command to add
permissions to the hdisks newly mapped from the eDevLUNs.
Step 3 Verify the database OCR and Voting Disk information.
Go to the bin directory as user grid. Run the ocrcheck command to verify the
database OCR information. Run the crsctl query css votedisk command to verify
the database Voting Disk information.

OceanStor Dorado
Step 4 Start the RAC cluster.

1. Run the crsctl start cluster command as user root to start the cluster.
2. Run the crs_stat -t -v command to confirm that all CRS services are operating
properly.
3. Run the ps -ef|grep d.bin command to confirm that the process is running.
4. Run the srvctl status asm -n vioc1 command as user oracle to confirm that
the ASM instance is in the normal state.
Step 5 Start upper-layer services.
----End

OceanStor Dorado
SmartVirtualization Feature Guide 10 Managing SmartVirtualization
10 Managing SmartVirtualization
After SmartVirtualization is deployed, you can configure value-added features for

eDevLUNs, perform routine maintenance, and set heterogeneous storage
information to enhance SmartVirtualization's role in service running.
10.1 Managing External Storage Devices
A logical connection based on an FC or iSCSI link is set up between a local storage
device and an external storage device for data transmission during remote
replication. This section describes how to manage external storage devices.
10.2 Managing eDevLUNs
10.3 Performing Rollback
10.1 Managing External Storage Devices

A logical connection based on an FC or iSCSI link is set up between a local storage
device and an external storage device for data transmission during remote
replication. This section describes how to manage external storage devices.
10.1.1 Viewing External Storage Device Information

This section describes how to view basic information about external storage
devices.
Procedure
Step 2 View basic information about external storage devices.
Table 10-1 describes the parameters.

OceanStor Dorado
Table 10-1 Basic information about external storage devices

Name Name of the external storage device.
ID ID of the external storage device.
Health Status Health status of the external storage device.
Running Status Running status of the external storage device.
WWN WWN of the external storage device.
ESN ESN of the external storage device.
Device Manufacturer Manufacturer of the external storage device.
FC Links Number of Fibre Channel links between the local and

external storage devices.
iSCSI Links Number of iSCSI links between the local and external
storage devices.
----End
10.1.2 Changing the Name of an External Storage Device

If the name of an external storage device is changed, its name on DeviceManager
needs to be changed accordingly.
Prerequisites
An external storage device has been added.
Procedure
Step 2 Click on the right of the external storage device and choose Modify.
The Modify External Storage Device dialog box is displayed.
Step 3 Enter a new name for the external storage device.
NOTE
● The name consists of 1 to 31 characters.

● The name contains only letters, digits, underscores (_), hyphens (-), and periods (.).
Step 4 Click OK.
----End
10.1.3 Adding an iSCSI Link

This section describes how to add an iSCSI link for an external storage device.

OceanStor Dorado
Procedure
Step 2 Click on the right of the external storage device and choose Add iSCSI Link.
The Add iSCSI Link dialog box is displayed.
Step 3 Set up the connection to the external storage device.

1. Set the iSCSI link parameters listed in iSCSI link parameters.

storage device.

port on the external storage device.
NOTE
You can click to add an iSCSI link or click to remove an iSCSI link.
2. (Optional) Click and enable CHAP Authentication. Then, specify

Username and Password.
NOTE
Before enabling CHAP authentication, ensure that CHAP authentication has been
enabled on the external storage device and the user name and password have been
configured.
Step 4 Click OK.
----End
10.1.4 Removing an iSCSI Link

This section describes how to remove an iSCSI link from an external storage
device.
Procedure
Step 2 Click on the right of the external storage system and choose Remove iSCSI Link.
The Remove iSCSI Link dialog box is displayed.
Step 3 Select the iSCSI link to be removed, and click to add it to the right list.

OceanStor Dorado
Step 4 Click OK.
----End
10.1.5 Removing an External Storage Device

This section describes how to remove an unwanted external storage device.
Prerequisites
● All links between the external storage system and local storage system have
been disconnected. The external storage system is in the faulty status.
● eDevLUNs created on the local storage system to take over external LUNs
have been deleted.
Context
The following describes how to disconnect the local storage system from an
external storage system:
● Removing an iSCSI link:

– You can remove an iSCSI link using the CLI.
i. Run the show iscsi target command to query the ID and Local
Control ID of the link whose Application Type is Heterogeneity.
ii. Run the delete iscsi target iscsi_id=? local_control_id=? command
to delete the iSCSI target. In the command, iscsi_id and
local_control_id indicate the ID and Local Control ID queried in the
previous step respectively.
– Alternatively, you can remove an iSCSI link using DeviceManager.
i. Choose System > External Storage, and then select the external
storage device to be removed.
ii. Click on the right and choose Remove iSCSI Link.

● Removing a Fibre Channel link:
You can remove a Fibre Channel link by changing the status of the related
Fibre Channel port on the CLI:
a. Run the show port general command to query the ID of the Fibre
Channel port.
b. In developer mode, run the change port enabled port_id=?
port_type=FC enabled=no command to disable the Fibre Channel port to
disconnect the heterogeneous link on the Fibre Channel port.
NOTICE
After the port is disabled, other services on the port will be interrupted. Before
using this method, check whether other services are running on the port.

OceanStor Dorado
Procedure
Step 2 Click on the right of the external storage device and choose Remove.
Step 3 Confirm your operation as prompted.
----End
10.1.6 Automatically Scanning for LUNs

If another external LUN is mapped from the heterogeneous storage system to the
local storage system, or an external LUN mapped to the local storage system is
deleted from the heterogeneous storage system, or the configuration of an
external LUN is changed, you can update LUN mapping relationships or
synchronize the statuses of remote LUNs by scanning for LUNs.
Prerequisites
● A heterogeneous storage device has mapped its LUNs to the local storage
device.
● A heterogeneous storage device has been added.
● Automatic scan is applicable only to heterogeneous storage devices.
Context
Automatic scan can be performed based on a storage device or a link.
● Based on a storage device: Automatically scanning the selected storage

device, the system displays the information of LUNs mapped by the selected
storage device to the local storage device and the information of links
between storage devices.
● Based on a link: Automatically scanning the selected link of storage device,
the system displays the information of LUNs mapped by the selected storage
device to the local storage device through this link.
The following steps introduce how to implement automatic scanning based on

storage devices. If you want to know how to implement scanning based on the
links between devices, see the help information on DeviceManager.
Procedure
Step 3 Choose a remote device that you want to scan for LUNs automatically.
Step 4 Click Scan for External LUN above the device list.
The Scan for External LUN dialog box is displayed, prompting that the scan may
take tens of seconds.

OceanStor Dorado
Step 5 Click OK to perform automatic scanning.
----End
10.2 Managing eDevLUNs

After creating eDevLUNs, you can view eDevLUN properties and expand eDevLUN
capacity to allow the local storage system to better utilize storage space provided
by external LUNs.
10.2.1 Expanding the Storage Space of an eDevLUN

After services are running for a period, the original storage space of an external
LUN may not meet storage requirements of service data. You must expand the
storage space of the external LUN. After expanding the storage space of the
external LUN, you must expand the storage space of the eDevLUN. In this way,
application servers can use the storage space of the expanded external LUN by
employing the eDevLUN.
10.2.1.1 Capacity Expansion Process

Before expanding storage capacity, learn about the capacity expansion process to
ensure smooth capacity expansion.
Figure 10-1 shows the flowchart for expanding an eDevLUN.
Figure 10-1 Flowchart for expanding an eDevLUN

OceanStor Dorado
Table 10-3 eDevLUN expansion steps

Step Description Operation Path
Expand the external Expand the external LUN For details, see operation
LUN. to the desired capacity. instructions for a
system.
Refresh information Refresh information Choose System >

about the remote LUN. about the remote LUN External Storage > Scan
on the local storage for External LUN.
system for the remote For details about the
LUN to identify the operation, see the
capacity added to the DeviceManager online
corresponding external help.
LUN on the
system.
Expand the eDevLUN. Expand the eDevLUN Choose Services > LUNs.
and update its capacity Then, click More on the
to the new capacity of right of the LUN to be
the corresponding expanded and choose
external LUN. Expand.
For details about the
operation, see the
DeviceManager online
help.
10.2.1.2 Precautions
During capacity expansion, observe the capacity expansion precautions to ensure
smooth capacity expansion.
● Any eDevLUN used by SmartMigration cannot be expanded.
● eDevLUNs can only be fully expanded. The total capacity after expansion
equals the remote LUN capacity.
● To ensure data integrity, stop services on an eDevLUN before expanding it.
10.3 Performing Rollback

During the process of configuring the online takeover function, if you do not want
to use the OceanStor Dorado V6 series storage system (local storage system) for
online takeover and the heterogeneous storage system is required to continue
carrying application servers' services, perform rollback.
Rollback operations vary depending on different operations performed to
configure the online takeover function. For details, see Table 10-4.

OceanStor Dorado
Table 10-4 Rollback operations

Configuration Completed Operation Rollback Operation
Process
Performing a pre- Check the application N/A

configuration check server status.
Check the heterogeneous

storage system status.

system status.
Connecting cables - 1. Power off the local

storage system.
Establishing a logical ● Create a LUN group.
connection between 2. Disconnect the local
● Create a host group. storage system from
the heterogeneous
storage system and ● Create a host and add the heterogeneous
local storage system the initiator. storage system and
● Create a mapping view. application servers.
Checking the license -

file
Configuring and (Optional) Add a remote

using eDevLUNs device.
Enable automatic LUN

scanning.
Create eDevLUNs.
Map eDevLUNs to an 1. Disconnect the local

application server. storage system from
Scan for eDevLUNs on the
2. Cancel the mapping
application server.
relationship between
Configuring host Check the multipathing the eDevLUNs and
path switchover status. application server.
3. Disconnect the local
storage system from
the heterogeneous
storage system.
Switch over host paths. 1. Restore the path

between the
system (restore the
physical connection
between the

OceanStor Dorado

Process
Migrate the reserved system or add the

information. initiator of the
NOTE application server to
This operation is not required the host that
when a third-party corresponds to the
heterogeneous storage application server).
system is taken over online.
2. Scan for LUNs on the
verify that the transfer
path identified by the
multipathing software
has been restored
between the
system.
3. Switch I/O path to that
between the
system and the
application server.
When OceanStor
UltraPath whose
version is earlier than
V100R008C20 is
installed on the
application server,
ignore this operation.
a. On the application
server, run the
command to switch
back the
multipathing
software to the path
of the original array.
b. Remove the
mapping between
the application
server and the
connected port of
the local storage
system.
c. Scan for LUNs on
the application
server.
Wait 60 seconds for
the vLUNs' status to
become normal.

OceanStor Dorado

Process
NOTE
In a cluster environment,
perform the following
operations on each of the
clustered host nodes.
4. Disconnect the local
storage system from
Confirm the completion of The online takeover is

the host path switchover. completed after you clear
the path switchover
Clearing the path - property of masqueraded
switchover property eDevLUNs. Then you
of the eDevLUNs cannot perform online
that are rollback. To perform
masqueraded rollback, stop host services
first.

OceanStor Dorado
SmartVirtualization Feature Guide 11 FAQs
11 FAQs
This chapter describes frequently asked questions (FAQs) about the

SmartVirtualization feature. If a problem occurs when you configure and maintain
the feature, you can browse this chapter for the answer to the problem.
11.1 Why Does a Local Storage System Display an Incorrect LUN Capacity After an
External LUN of a Heterogeneous Storage System Is Mapped to the Local Storage
System?
11.2 What Can I Do If the New Configuration of an External LUN on a
Heterogeneous Storage System Cannot Be Synchronized to the Local Storage
System?
11.3 What Can I Do If an External LUN Abnormality Has Been Rectified on a
Heterogeneous Storage System but the Corresponding Remote LUN or eDevLUN
Information on the Local Storage System Fails to Be Updated or the Remote LUN
Information Fails to Be Displayed?
11.4 Why Is the Health Status of the Remote LUN and eDevLUN Still Displayed
Normal on the Local Zero-Load Storage System When an External LUN
Malfunctions?
11.5 How Can I Restore the Link If a Link Between a Switch and an HP EVA8000
Fails to Resume After the Cable Between the HP EVA8000 and the Fibre Channel
Switch Is Removed and Reinserted or the Switch Is Restarted?
11.6 Why Does a Local Storage System Detect Thick LUNs After a Heterogeneous
Storage System Maps Thin LUNs to the Local Storage System?
11.7 Why Does a Local Storage System Detect Thin LUNs After a Heterogeneous
Storage System Maps Thick LUNs to the Local Storage System?
11.8 Why Is Default Displayed in Device Name of the Remote Device in
DeviceManager of a Local Storage System After IBM Storwize V Series Storage
System Is Connected to the Local Storage System?
11.9 Why Does the Link Connection Become Abnormal with a Probability When
Oracle SUN Storage6000 Series Is Connected to a Local Storage System Using a
Switch?
11.10 What Can I Do After the Heterogeneous Storage System Restarts, the Local
Storage System Cannot Display the Remote LUN That Corresponds to the External
LUN or the eDevLUN Fails?

OceanStor Dorado
11.11 Why Are Services Interrupted After All Physical Connections Between a Local
Storage System and One Controller of Dell Compellent SC Are Disconnected
(When Service Loads Exist)?
11.12 Why Are Services Interrupted When You Restart One Controller of the Sugon
DS800-G25/MacroSAN MS3100/MacroSAN MS3300/MacroSAN MS7000 Series
Heterogeneous Storage System with Service Load?
11.13 How Can I Discover a Remote LUN Belonging to a Heterogeneous Storage
System in a Local Storage System After the LUN Is Mapped to the Local Storage
System for Hosting but the LUN Is Not Yet Initialized?
11.14 What Can I Do If a Local Storage System Cannot Discover the Remote LUN
Corresponding to an External LUN When the Physical Connection Between a
Heterogeneous Storage System and the Local Storage System Is Changed?
11.15 After a LUN Is Mapped from a Heterogeneous Storage System to the
OceanStor Dorado V6 series Storage System (Local Storage System), Why an
Unnecessary Remote LUN Can Be Viewed on the DeviceManager Management
Page of the Local Storage System?
11.16 Why Are Services Interrupted When the reboot Command Is Executed to
Restart One Controller of NetApp FAS8000 Storage System?
11.17 How Do I Add A Heterogeneous Device to the Whitelist?
11.18 Why Is a Logical Path Whose Status is Degraded Found When eDevLUNs Are
Scanned After Huawei VIS6000/VIS6000T Storage Systems Are Taken Over
11.19 How Is Load Balancing Implemented for SmartVirtualization?
11.20 How Can I Delete the Heterogeneous Disks from the Application Server?
11.1 Why Does a Local Storage System Display an

Incorrect LUN Capacity After an External LUN of a
Heterogeneous Storage System Is Mapped to the Local
Storage System?
Question
Why does a local storage system display an incorrect LUN capacity after an
external LUN of a heterogeneous storage system is mapped to the local storage
system?
Answer
Possible reasons are as follows:
● Some heterogeneous storage systems are specially processed in displaying

capacities, which leads to inconsistent displays of capacities in the units of KB,
MB, GB and TB on the local storage system and the heterogeneous storage
system. However, when the capacity is displayed in the unit of sector, it is the

OceanStor Dorado
same on both the local storage system and the heterogeneous storage system
(for example, the IBM XIV series storage systems).
● Due to their special processing mechanisms, some heterogeneous storage
systems report a smaller capacity to a local storage system after mapping an
external LUN to the local storage system. Therefore, the local storage system
displays an incorrect capacity information about the mapped external LUN.
Some value-added features on a local storage system require that the used local
LUN and external LUN have the same capacity. Therefore, the local LUN must
have the same capacity as the external LUN. Create a local LUN following the
procedure below:
Step 1 View the capacity of eDevLUN.

1. Log in to the DeviceManager for local storage system 1.
2. In the navigation bar, choose Services > Block Service > LUNs. View the
number of sectors on the eDevLUN.
Step 2 On local storage system 2, create a local LUN.

2. In the navigation bar, choose Services > Block Service > LUNs.
3. Click Create.
The Create LUN dialog box is displayed.
4. In the Capacity text box, enter the number of blocks that you saw in Step 1.
Set the unit to Blocks.
NOTE
Set the other LUN parameters as required.

5. Click OK.
Step 3 Check whether the created local LUN has the same capacity as the external LUN.
2. In the navigation bar, choose Services > Block Service > LUNs.
3. Check whether the created local LUN has the same capacity as the external
LUN.
– If yes, you have created a correct local LUN.
– If no, perform Step 1 and Step 2 to re-create a local LUN.
----End
11.2 What Can I Do If the New Configuration of an

External LUN on a Heterogeneous Storage System
Cannot Be Synchronized to the Local Storage System?
Question
What can I do if the new configuration of an external LUN on a heterogeneous
storage system cannot be synchronized to the local storage system?

OceanStor Dorado
Answer
If information about the external LUN is not updated on the local storage system
after operations on the heterogeneous storage system such as adding or deleting
initiators or LUN mappings, or expanding external LUNs, manually scan the local
storage system for LUNs.
Manually scan for LUNs using one of the following methods:
● Start an automatic LUN scan in DeviceManager.

● In CLI, run the scan remote_lun command.
NOTE
The operations in the following procedure are based on DeviceManager. For details about
how to use scan remote_lun, see the command reference of the corresponding product
model.
Step 1 Log in to the DeviceManager for the local storage system.
Step 2 Go to the Automatic LUN Scan dialog box.

1. In the navigation bar, choose System > External Storage.
2. Based on Name and SN, select the remote device that corresponds to the
heterogeneous storage system. In the lower function pane, click Scan for
External LUN.
The OK dialog box is displayed.
Step 3 Click OK to start an automatic LUN scan.
DeviceManager then scans for LUNs, and synchronizes the configuration of the
remote LUN with that of the external LUN and updates the number of remote
LUNs.
Step 4 Click Close.
----End
11.3 What Can I Do If an External LUN Abnormality

Has Been Rectified on a Heterogeneous Storage
System but the Corresponding Remote LUN or
eDevLUN Information on the Local Storage System
Fails to Be Updated or the Remote LUN Information
Fails to Be Displayed?
What can I do if an external LUN abnormality has been rectified on a
heterogeneous storage system but the corresponding remote LUN or eDevLUN
information on the local storage system fails to be updated or the remote LUN
information fails to be displayed?

OceanStor Dorado
Answer
If a local storage system has one of the following abnormalities after the external
LUN mapped from a heterogeneous storage system becomes normal, manually
scan the local storage system for LUNs:
● The local storage system cannot display information about the remote LUN
corresponding to the external LUN.
● The remote LUN corresponding to the external LUN on the local storage
system is still in the fault state.
● The eDevLUN is still in the faulty state.
Use one of the following methods to scan for LUNs:
NOTE
model.

External LUN.
DeviceManager then scans for LUNs, and updates information about the remote
LUN and eDevLUN, making the information consistent with information about the
external LUN.
Step 4 Click Close.
----End

OceanStor Dorado
11.4 Why Is the Health Status of the Remote LUN and

eDevLUN Still Displayed Normal on the Local Zero-
Load Storage System When an External LUN
Malfunctions?
Question
Why is the health status of the remote LUN and eDevLUN still displayed normal
on the local zero-load storage system when an external LUN malfunctions?
Answer
When the local storage system has no service loads, it cannot set the remote LUN
and eDevLUN to be in the faulty state based on I/O error statistics. If the external
LUN malfunctions when the local storage system is processing I/O loads, the local
storage system automatically updates the status of the external LUN and set the
remote LUN and eDevLUN to be in the faulty state.
11.5 How Can I Restore the Link If a Link Between a

Switch and an HP EVA8000 Fails to Resume After the
Cable Between the HP EVA8000 and the Fibre Channel
Switch Is Removed and Reinserted or the Switch Is
Restarted?
Question
How can I restore the link if a link between a switch and an HP EVA8000 fails to
resume after the cable between the HP EVA8000 and the Fibre Channel switch is
removed and reinserted or the switch is restarted?
Answer
A local storage system is connected to an HP EVA8000 storage system through a
Fibre Channel switch. After the cable between the HP EVA8000 and the switch is
removed and reinserted or the switch is restarted, the switch sends LIP-loop
initialization frames (loop acknowledgement) to the HP EVA8000. However, the
HP EVA8000 does not support the loop mode and therefore does not return a
response message. As a result, the switch resets the link connected to the HP
EVA8000. Afterwards, the HP EVA8000's port mode becomes abnormal
intermittently and the link fails to resume.
On the HP EVA8000, set its port mode to Fabric for the link to resume.

OceanStor Dorado
NOTE
Unless you have to, do not perform any of the following operations when links are normal:
● Remove the optical fiber to a port.
● Simulate intermittent port disconnection.
● Restart switches.
11.6 Why Does a Local Storage System Detect Thick

LUNs After a Heterogeneous Storage System Maps
Thin LUNs to the Local Storage System?
Question
Why does a local storage system detect thick LUNs after a heterogeneous storage
system maps thin LUNs to the local storage system?
Answer
Some heterogeneous storage systems such as IBM Storwize V series, EMC DMX3/
DMX4, HDS HUS VM, HDS VSP, HP P9500 or Sugon DS800-G10/DS800-G20/
NetApp E series/Inspur AS1000G6/DCS3700/Dell PowerVault MD series cannot
transmit its thin LUN properties to local storage systems. Therefore, after a local
storage system takes over thin LUNs from a heterogeneous storage system,
services on those thin LUNs can still run normally but those thin LUNs are
presented as thick LUNs on the local storage system.
11.7 Why Does a Local Storage System Detect Thin

LUNs After a Heterogeneous Storage System Maps
Thick LUNs to the Local Storage System?
Question
Why does a local storage system detect thin LUNs after a heterogeneous storage
system (for example NetApp FAS 3000 series/V3000 series/FAS 8000 series) maps
thick LUNs to the local storage system?
Answer
Due to the innate faults of some heterogeneous storage systems (for example
NetApp FAS 3000 series/V3000 series/FAS 8000 series), the local storage system
may detect thin LUNs after it takes over the thick LUNs of the heterogeneous
storage system without affecting the proper running of the LUN services.

OceanStor Dorado
11.8 Why Is Default Displayed in Device Name of the

Remote Device in DeviceManager of a Local Storage
System After IBM Storwize V Series Storage System Is
Connected to the Local Storage System?
Question
Why is Default displayed in Name of the remote device in DeviceManager of a
local storage system after IBM Storwize V series storage system is connected to
the local storage system?
Answer
After IBM Storwize V series storage system is connected to the local storage
system, the local storage system cannot obtain the unique identifier of the
heterogeneous storage system and identifies the storage system as a default
device. As a result, the Name of the remote device is displayed as Default on the
DeviceManager. Even though being identified as a default device, the
heterogeneous storage system's functions are not affected when
SmartVirtualization is used.
11.9 Why Does the Link Connection Become Abnormal

with a Probability When Oracle SUN Storage6000
Series Is Connected to a Local Storage System Using a
Switch?
Question
Why does the link connection become abnormal with a probability when Oracle
SUN Storage6000 series is connected to a local storage system using a switch?
Answer
After Oracle SUN Storage6000 series is connected to the local storage system
using a switch, some ports on Oracle SUN Storage6000 series will be disconnected
from the switch with a probability due to problems of Oracle SUN Storage6000
series. As a result, the link connection becomes abnormal.

OceanStor Dorado
11.10 What Can I Do After the Heterogeneous Storage

System Restarts, the Local Storage System Cannot
Display the Remote LUN That Corresponds to the
External LUN or the eDevLUN Fails?
Question
What can I do after the heterogeneous storage system restarts, the local storage
system cannot display the remote LUN that corresponds to the external LUN or
the eDevLUN fails?
Answer
If the local storage system has either of the following issues after the
heterogeneous storage system restarts, scan for LUNs manually:
● The local storage system cannot display the remote LUN that corresponds to
the external LUN.
● The eDevLUN for the external LUN fails.
Manually scan for LUNs using one of the following methods:
NOTE
how to use scan remote_lun, see command reference of the corresponding product model.

External LUN.
DeviceManager then scans for LUNs, and synchronizes the configuration of the
remote LUN with that of the external LUN and updates the number of remote
LUNs.
Step 4 Click Close.
----End

OceanStor Dorado
11.11 Why Are Services Interrupted After All Physical

Connections Between a Local Storage System and One
Controller of Dell Compellent SC Are Disconnected
(When Service Loads Exist)?
Question
Why are services interrupted after all physical connections between a local storage
system and one controller of Dell Compellent SC are disconnected (when service
loads exist)?
Answer
All physical connections between the local storage system and one controller of
Dell Compellent SC are disconnected when service loads exist. Although the local
storage system is still connected to the other controller of Dell Compellent SC,
Dell Compellent SC does not support failover in this scenario. As a result, services
are interrupted.
11.12 Why Are Services Interrupted When You Restart

One Controller of the Sugon DS800-G25/MacroSAN
MS3100/MacroSAN MS3300/MacroSAN MS7000 Series
Heterogeneous Storage System with Service Load?
Question
Why are services interrupted when you restart one controller of the Sugon DS800-
G25/MacroSAN MS3100/MacroSAN MS3300/MacroSAN MS7000 series
heterogeneous storage system with service load?
Answer
When there is service load, restarting one controller of the Sugon DS800-G25/
MacroSAN MS3100/MacroSAN MS3300 /MacroSAN MS7000 series heterogeneous
storage system will cause service interruption. That is because the heterogeneous
storage system does not support failover in this scenario even though the local
storage system connects with the other controller of this storage system.

OceanStor Dorado
11.13 How Can I Discover a Remote LUN Belonging to

a Heterogeneous Storage System in a Local Storage
System After the LUN Is Mapped to the Local Storage
System for Hosting but the LUN Is Not Yet Initialized?
Question
How can I discover a remote LUN belonging to a heterogeneous storage system in
a local storage system after the LUN is mapped to the local storage system for
hosting but the LUN is not yet initialized?
Answer
Step 1 Wait until the LUN is initialized on the heterogeneous storage system.
Step 2 Manually scan for LUNs on the local storage system.
NOTE
Use one of the following methods to scan for LUNs:

model.
1. Log in to the DeviceManager for the local storage system.

External LUN.
4. Click OK to start an automatic LUN scan.
After the automatic scan is completed, the remote LUN configurations on the
local storage system are updated, and the quantity of remote LUNs is
changed.
----End

OceanStor Dorado
11.14 What Can I Do If a Local Storage System Cannot

Discover the Remote LUN Corresponding to an External
LUN When the Physical Connection Between a
Heterogeneous Storage System and the Local Storage
System Is Changed?
Question
What can I do if a local storage system cannot discover the remote LUN
corresponding to an external LUN when the physical connection between a
heterogeneous storage system and the local storage system is changed?
Answer
For some heterogeneous storage systems, their initiators and targets are in a one-
to-one mapping relationship. After the physical connection is changed, the
mapping relationship is also changed. You must re-establish a mapping
relationship among initiators, targets, and LUNs on the management interface of
the heterogeneous storage system. (If the local storage system fails to
automatically discover LUNs, manually scan for LUNs.) Otherwise, the
heterogeneous storage system will not report LUNs.
11.15 After a LUN Is Mapped from a Heterogeneous

Storage System to the OceanStor Dorado V6 series
Storage System (Local Storage System), Why an
Unnecessary Remote LUN Can Be Viewed on the
DeviceManager Management Page of the Local
Storage System?
Question
After a LUN is mapped from a heterogeneous storage system to the OceanStor
Dorado V6 series storage system (local storage system), why an unnecessary
remote LUN can be viewed on the DeviceManager management page of the local
storage system?
Answer
On the DeviceManager page, check the remote LUN information. If the LUN has a
small amount of capacity, the LUN is a command device. Do not use this remote
LUN as an eDevLUN and map it to application servers.

OceanStor Dorado
11.16 Why Are Services Interrupted When the reboot

Command Is Executed to Restart One Controller of
NetApp FAS8000 Storage System?
Question
Why are services interrupted when the reboot command is executed to restart one
controller of NetApp FAS8000 storage system?
Answer
When service loads exist, the reboot command is executed to restart one
controller of NetApp FAS8000 storage system. Although the local storage system
is still connected to the other controller of NetAppFAS8000 storage system,
NetAppFAS8000 storage system does not support failover in this scenario. As a
result, services are interrupted.
11.17 How Do I Add A Heterogeneous Device to the

Whitelist?
Question
How do I add the array to the whitelist when alarm "Incompatible Heterogeneous
Array Connected to the System" is reported on the local storage system?
Answer
NOTICE
Contact Huawei technical support engineers to decide whether to add the array to
the whitelist. If yes, the engineers will perform operations. Do not perform the
operations by yourself. Otherwise, services may be affected.
The following takes HP P2000 G3 as an example. In practice, the array model and
vendor may be different.
Step 1 Log in to the interface for managing heterogeneous storage devices that have
been taken over, and record the vendor, model (VID and PID), and running status
of the array.

OceanStor Dorado
Step 2 Check the heterogeneous storage arrays that are compatible with the local storage
system.
1. On the CLI, log in to the storage system and enter the engineer mode.
admin:/>change user_mode current_mode user_mode=engineer
engineer:/>
2. Run show remote_device support_array_list to check the compatible

heterogeneous storage arrays.
engineer:/>show remote_device support_array_list
Manufacturer Model Path Selector Fail Over Fail Back ASL ID
------------ ---------------- ------------- --------- -------------- ------
HUASY V1500 ROUND_ROBIN ENABLE DELAY_FAILBACK 1
HUASY V1800 ROUND_ROBIN ENABLE DELAY_FAILBACK 1
EMC VPLEX LEAST_QUEUE ENABLE NOT_FAILBACK 22
HP MSA2212fc ROUND_ROBIN ENABLE NOT_FAILBACK 10
HP P2000 G3 ROUND_ROBIN ENABLE NOT_FAILBACK 10
HP XP20000 ROUND_ROBIN ENABLE NOT_FAILBACK 12
NOTE
You can find out the vendor of a heterogeneous storage array by running show
remote_device support_array_list manufacturer=HP, and then check the array
models of this vendor compatible with the local storage system.
engineer:/>show remote_device support_array_list manufacturer=HP
Manufacturer Model Path Selector Fail Over Fail Back ASL ID
------------ ---------- ------------- --------- ------------ ------
HP MSA2212fc ROUND_ROBIN ENABLE NOT_FAILBACK 10
HP P2000 G3 ROUND_ROBIN ENABLE NOT_FAILBACK 10
HP XP20000 ROUND_ROBIN ENABLE NOT_FAILBACK 12
3. Check whether the heterogeneous array whose information is queried in
11.17 How Do I Add A Heterogeneous Device to the Whitelist? is one of
the compatible heterogeneous storage devices queried in 11.17 How Do I
Add A Heterogeneous Device to the Whitelist?
– If yes, go to Step 3.
– If no, contact Huawei technical support engineers to confirm whether a
corresponding heterogeneous support package needs to be developed.
Step 3 Add the array to the whitelist.
1. Run show remote_device elink to obtain information about the link through
which the array is connected.
engineer:/>show remote_device elink
FC Link:
ID Health Status Running Status Local Controller Remote Device Type In Remote

OceanStor Dorado
Device Remote Device ID Remote Device WWN Remote Controller

--------- ------------- -------------- ---------------- ------------------------- ----------------
---------------- ----------------- -----------------
268435456 Normal Link Up 0A Other Manufacturer Device Yes
512 -- --
268435457 Normal Link Up 0A Other Manufacturer Device Yes
512 -- --
268435458 Normal Link Up 0B Other Manufacturer Device Yes
512 -- --
268435459 Normal Link Up 0B Other Manufacturer Device Yes
512 -- --
– If Remote Device ID is 512, the array has not been added to the
whitelist. Go to Step 3.2.
– If Remote Device ID is not 512, the array has been added to the
whitelist. No further action is required.
2. Obtain the VID and PID of the array based on the link ID.
engineer:/>show remote_device array_info link_id=268435456
Link ID : 268435456
Remote Device ID : 512
Vendor : HP
Product ID : P2000 G3 FC
In this example, the VID and PID are HP and P2000 G3 FC respectively.
3. Run show remote_device white_list to check the heterogeneous device
whitelist of the local storage device, and compare whether the VID and PID
queried in Step 3.2 are on the whitelist.
engineer:/>show remote_device white_list
Record ID Vendor Product ID Path Selector Fail Back Fail Over ASL ID Is User Added
--------- -------- ---------------- ------------- -------------- --------- ------ -------------
11 EMC CX4-120 ROUND_ROBIN DELAY_FAILBACK ENABLE 3 No
46 HP HSV360 ROUND_ROBIN NOT_FAILBACK ENABLE 5 No
47 HPP2000G3 FC/iSCSI ROUND_ROBIN NOT_FAILBACK ENABLE 10 No
48 HP MSA2212fc ROUND_ROBIN NOT_FAILBACK ENABLE 10 No
– If yes, no further action is required.

– If no, add the array to the whitelist manually.
4. Run add remote_device white_list to add the array to the whitelist.
Note the following when running this command:
– The spaces in vendor and product names can be replaced by asterisks (*).
– Vendor and Product_id must be the same as the information queried in
Step 3.2.
– Path Selector, Fail Back, Fail Over, and ASL ID must be the same as the
policies of the compatibility list queried in 11.17 How Do I Add A
Heterogeneous Device to the Whitelist?
engineer:/>add remote_device white_list vendor=HP product_id=P2000*G3*FC
path_selector=ROUND_ROBIN fail_back=NOT_FAILBACK fail_over=ENABLE asl_id=10
Command executed successfully.
5. Run show remote_device whitelist to check the whitelist and confirm that
the array has been added to the whitelist.
engineer:/>show remote_device white_list
--------- -------- ---------------- ------------- -------------- --------- ------ -------------
47 HP P2000G3 FC/iSCSI ROUND_ROBIN NOT_FAILBACK ENABLE 10
No

OceanStor Dorado

159 HP P2000 G3 FC ROUND_ROBIN NOT_FAILBACK ENABLE 10
Yes
50 HUASY V1500 ROUND_ROBIN DELAY_FAILBACK ENABLE 1 No
If a wrong array has been added, run remove remote_device white list to
delete the record. For example, to delete a record whose Record ID is 159,
run the following command.
engineer:/>remove remote_device white_list record_id=159
WARNING: You are going to remove remote device white list. This operation deletes the information
about the remote device white list from the system.
Suggestion: Before you perform this operation, ensure that you have selected the correct remote
device white list and confirm that the remote device white list can be deleted.
Have you read warning message carefully?(y/n)y
Are you sure you really want to perform the operation?(y/n)y
----End
11.18 Why Is a Logical Path Whose Status is Degraded

Found When eDevLUNs Are Scanned After Huawei
VIS6000/VIS6000T Storage Systems Are Taken Over
Question
Why is a logical path whose Status is Degraded found when eDevLUNs are
scanned after Huawei VIS6000/VIS6000T storage systems are taken over?
Answer
When UltraPath of V100R005 or V100R006 is installed, the paths between the
application servers and the local storage systems will be set to Degraded status
because of the processing mechanism of UltraPath. When the path status is
restored to Normal, perform the follow-up operations (after about 10 minutes).
11.19 How Is Load Balancing Implemented for

SmartVirtualization?
Question
How is load balancing implemented for SmartVirtualization?
Answer
Load balancing within a controller and load balancing between controllers are
enabled by default. Users can modify the heterogeneous storage device whitelist
to set the path selection algorithm to define the load balancing policy of the array.
The detailed procedure is as follows.

OceanStor Dorado
NOTE
A heterogeneous array whitelist is a list of Huawei's or third-party vendors' devices that

Huawei storage systems can take over. You can configure the whitelist to set the path
selection algorithm used by the local storage system to take over heterogeneous storage
systems and failover and failback policies.
1. Run show remote_device general to obtain the ID of the remote array.

admin:/>show remote_device general\
ID Name Health Status Running Status WWN SN Device Type Remote Device Type
--- --------------------- ------------- -------------- ---------------- -------------------- -------------
------------------
0 Huawei.Storage_217.88 Normal Link Up 210020f17ce12dff 2102350FJQ10G5000018
Replication --
513 HUAWEI_XSG1_513 Normal Link Up -- 2102350FJQ10G5000018 Heterogeneity XSG1
2. Run show remote_lun general array_type=? remote_device_id=? to query

basic information about the remote LUN. The Vendor and Model fields in the
command output indicate the vendor and model of the remote storage
device.
admin:/>show remote_lun general array_type=heterogeneity remote_device_id=513
Lun Id Name Health Status Device ID Device SN Capacity Lun WWN Vendor
Model Lun Path Number
------ ---- ------------- --------- -------------------- -------- -----------------------------------------------
-------- ---------------- ---------------
-- -- Normal 513 2102350FJQ10G5000018 20.000GB 62:0f:17:c1:00:e1:2d:ff:19:b7:72:8f:
00:00:03:a6 HUAWEI XSG1 9
-- -- Normal 513 2102350FJQ10G5000018 20.000GB 62:0f:17:c1:00:e1:2d:ff:
19:b7:72:45:00:00:03:a5 HUAWEI XSG1 11
3. Run show remote_device white_list to query the whitelist of heterogeneous

arrays. The Path Selector field in the command output indicates the path
selection algorithm of the heterogeneous array.
admin:/>show remote_device white_list
--------- -------- ---------------- ------------- -------------- --------- ------ -------------
15 EMC VNX5100 ROUND_ROBIN DELAY_FAILBACK ENABLE 3 No
24 EMC CX300 ROUND_ROBIN DELAY_FAILBACK ENABLE 3 No
30 EMC AX4-5 ROUND_ROBIN DELAY_FAILBACK ENABLE 3 No
31 EMC VNX5200 LEAST_QUEUE NOT_FAILBACK ENABLE 3 No
--More--(Quit : q|Q)(Next Record : Enter)(Next Page : Space)(To End : G)
4. Run change remote_device white_list to modify the heterogeneous array

whitelist.
admin:/>change remote_device white_list record_id=11 path_selector=FIX fail_back=NOT_FAILBACK
fail_over=ENABLE

OceanStor Dorado
NOTE
The path_selector field is used to set the path selection algorithm of the array. Its values
include FIX, ROUND_ROBIN, and LEAST_QUEUE. FIX indicates that the specific path is
selected, that is, the working controller is preferentially selected. The ROUND_ROBIN
algorithm rotates through all paths, thus balancing I/Os. The LEAST_QUEUE algorithm
selects the path that has the least number of I/Os. The ROUND_ROBIN and LEAST_QUEUE
path selection algorithms support load balancing. The FIX path selection algorithm does not
support load balancing.
NOTE
For details about the commands, see the command reference of the specific product model.
The following explains load balancing within a controller and load balancing
between controllers.
● Load balancing within a controller: On the sending end, all the links to the
heterogeneous storage that belong to the same controller have almost the
same transmission bandwidth.
Example: Assume that array A takes over array B and the total transmission
bandwidth is 200 MB/s. Controller 1 on array A has two links, link 0 and link
1.
– If load balancing within a controller is enabled, the bandwidth of both
link 0 and link 1 is 100 MB/s.
– If load balancing within a controller is disabled, the bandwidth of link 0 is
200 MB/s and the bandwidth of link 1 is 0 MB/s.
● Load balancing between controllers: If the bandwidth usage of the source
controller on the sending end exceeds 50% of the total bandwidth, services
are switched over to other controllers for load balancing.
11.20 How Can I Delete the Heterogeneous Disks from

the Application Server?
Question
After heterogeneous disks have been taken over by the local storage system, how
can I delete the heterogeneous disks from the application server?
Answer
Windows:
1. Open the cmd prompt and run diskmgmt.msc to open Disk Management.
2. Choose Action > Rescan Disks.
3. After the scanning is complete, open the cmd prompt and run upadm show
vlun type=migration to verify that all heterogeneous disks have been
deleted.
The following is an example:
Command output before heterogeneous disks are deleted:
C:\> upadm show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------

OceanStor Dorado
-------------------------------------------------------------
Name Dev Lun ID No. of Paths(Available/Total)
0 Disk1 hy1 600188210062f2579636991a00000006 Normal 1023.00MB --/--
storage219_70 -- 4/4
0 Disk1 eDevLUN022_001 600188210062f2579636991a00000006 Normal 1023.00MB
--/-- storage219_73 154 2/2
2 Disk2 hy2 600188210062f2579636e59500000007 Normal 1022.50MB --/--
storage219_70 -- 4/4
2 Disk2 eDevLUN022_002 600188210062f2579636e59500000007 Normal 1022.50MB
--/-- storage219_73 155 2/2
-----------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
Command output after heterogeneous disks are deleted:

C:\> upadm show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
Name Dev Lun ID No. of Paths(Available/Total)
0 Disk1 eDevLUN022_001 600188210062f2579636991a00000006 Normal 1023.00MB
--/-- storage219_73 154 2/2
2 Disk2 eDevLUN022_002 600188210062f2579636e59500000007 Normal 1022.50MB
--/-- storage219_73 155 2/2
-----------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
Linux:
1. Run the hot_add command to scan for disks.

2. After the scanning is complete, run the upadmin show vlun type=migration
command to verify that all heterogeneous disks have been deleted.
linux:~ # upadmin show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------
--------------
Name Dev Lun ID
0 sdc hy1 600188210062f2579636991a00000006 Normal 1023.00MB --/--
storage219_70 102
0 sdc eDevLUN022_001 600188210062f2579636991a00000006 Normal 1023.00MB
--/-- storage219_73 21
2 sdd hy2 600188210062f2579636e59500000007 Normal 1022.50MB --/--
storage219_70 103
2 sdd eDevLUN022_002 600188210062f2579636e59500000007 Normal 1022.50MB
--/-- storage219_73 22
-----------------------------------------------------------------------------------------------------------------------
--------------

linux:~ # upadmin show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------
--------------
Name Dev Lun ID
0 sdc eDevLUN022_001 600188210062f2579636991a00000006 Normal 1023.00MB
--/-- storage219_73 21
2 sdd eDevLUN022_002 600188210062f2579636e59500000007 Normal 1022.50MB
--/-- storage219_73 22
-----------------------------------------------------------------------------------------------------------------------
--------------
AIX:

OceanStor Dorado
Because the local and heterogeneous storage systems use the same disk names,
heterogeneous disks cannot be deleted by name. You must remove the logical
paths of the heterogeneous disks to delete them. The procedure is as follows:
1. Run the upadm show vlun type=migration command to query the names of
the heterogeneous disks to be deleted. In this example, the disk name is
hdisk0, which represents both the local and heterogeneous disks.
-bash-3.00# upadm show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------
Vlun ID Host Lun ID Disk Name Vlun Name Vlun WWN Status In Use
Capacity Controller(Own/Work) Array Name Array SN Dev Lun ID No. of
Paths(Available/Total)
0 1 hdisk0 Lun_008 632373610031304180C259F600000150 Fault No
8.00GB --/-- array_test_218_185 210235G6EDZ0AB201103 -- 0/4
0 0 hdisk0 eDevLUN155_002 632373610031304180C259F600000150 Available
No 8.00GB --/-- storage219_70 2102350SHY10G6000014 155 2/2
-----------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------
2. Run the lspath -l name -F"name:parent:connection:status" command to

query all logical paths of hdisk0. The result includes the logical paths of both
the local and heterogeneous disks.
-bash-3.00# lspath -l hdisk0 -F"name:parent:connection:status"
hdisk0:fscsi2:2400323736313041,0:Failed
hdisk0:fscsi2:201248435a775148,1000000000000:Enabled
hdisk0:fscsi2:200348435a775148,1000000000000:Enabled
NOTE
In the preceding command, -l name represents the disk name that is obtained by the
upadm show vlun type=migration command.
3. Run the upadm show phypath command to query the path of the
heterogeneous storage system in Target Port.
-bash-3.00# upadm show phypath
-----------------------------------------------------------------------------------------------------------------------
-----------------------
PhyPath ID Initiator Port Array Name Controller Target Port PhyPath State Check
State Port Type Port ID
0 10000090fa1c6c32 array_test_218_185 -- 2400323736313041 Normal
-- FC --
-- FC --
-- FC --
-- FC --
6 10000090fa1c6c32 storage219_70 -- 201248435a775148 Normal
-- FC CTE0.B.IOM0.P2
7 10000090fa1c6c32 storage219_70 -- 200348435a775148 Normal
-- FC CTE0.A.IOM0.P3
-----------------------------------------------------------------------------------------------------------------------
-----------------------
NOTE
Target Port indicates the WWN of the port on a storage system. In this example, the
paths whose PhyPathID is 0, 1, 2, and 3 belong to the heterogeneous storage system.
4. According to the results in 2 and 3, the logical paths of hdisk0 on the
heterogeneous storage system are the following:

OceanStor Dorado
5. Run the rmpath -w connection -l name -p parent -d command to delete
the logical paths obtained in 4.
NOTE
-w connection represents the path to be deleted. -l name represents the disk name. -
p parent represents the logical device name of the parent device. -d indicates
deletion.
-bash-3.00# rmpath -w 2400323736313041,0 -l hdisk0 -p fscsi2 -d
path Deleted
path Deleted
path Deleted
path Deleted
6. Run the upadm show vlun type=migration command to verify that the
heterogeneous disk represented by hdisk0 has been deleted.
Command output before the heterogeneous disk is deleted:
-----------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------
0 1 hdisk0 Lun_008 632373610031304180C259F600000150 Fault No
8.00GB --/-- array_test_218_185 210235G6EDZ0AB201103 -- 0/4
-----------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------
Command output after the heterogeneous disk is deleted:
-----------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------
Solaris:
1. Run the upRescan command to scan for disks.
2. After the scanning is complete, run the upadm show vlun type=migration
command to verify that all heterogeneous disks have been deleted.
root@solaris:~# upadm show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Vlun ID Disk Name Lun WWN Status Capacity
Ctrl(Own/Work) Array Name Dev Lun ID No. of Paths(Available/Total)
0 c5t69CE37410023339202AE6DBA00000099d0 solaris228Lun_008
69ce37410023339202ae6dba00000099 Normal 100.00GB --/-- Huawei.Storage219.90
-- 4/4
0 c5t69CE37410023339202AE6DBA00000099d0 eDevLUN155_001

OceanStor Dorado
6 4/4
1 c5t69CE37410023339202AE5DBF00000098d0 solaris228Lun_007
69ce37410023339202ae5dbf00000098 Normal 20.00GB --/-- Huawei.Storage219.90
-- 4/4
1 c5t69CE37410023339202AE5DBF00000098d0 eDevLUN155_002
7 4/4
-----------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------

root@solaris:~# upadm show vlun type=migration
-----------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Vlun ID Disk Name Lun WWN Status Capacity
Ctrl(Own/Work) Array Name Dev Lun ID No. of Paths(Available/Total)
0 c5t69CE37410023339202AE6DBA00000099d0 eDevLUN155_001
6 4/4
1 c5t69CE37410023339202AE5DBF00000098d0 eDevLUN155_002
7 4/4
-----------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------

OceanStor Dorado
SmartVirtualization Feature Guide 12 Troubleshooting
12 Troubleshooting
This chapter describes how to troubleshoot common problems related to the

SmartVirtualization feature. If a problem occurs when you configure and maintain
the feature, you can browse this chapter for the problem.
12.1 The Link Becomes Abnormal After an HP MSA2012FC/MSA2212FC Storage
System Enables the Internal Switch Mechanism
12.2 After an HP P6500 Storage System Is Powered On After a Power Failure,
eDevLUNs for External LUNs Are Still In the Fault State on DeviceManager for the
Local Storage System
12.3 A Local Storage System Encounters a Power Failure and Cannot Detect
External LUNs
12.4 The DeviceManager Cannot Display Remote Device Information or Remote
LUN Information After a Heterogeneous Storage Systems Is Connected to the
12.5 When the Physical Connection Is Changed Between NetApp FAS3000/
FAS6000/FAS8000 Series/EMC XtremIO/NetApp AFF8000 Series/NetApp E Series/
TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/DX200 S3/DX500 S3/DX600 S3 and
the Local Storage System, the Link Is Down
12.6 The Local Storage System Cannot Be Connected to OceanStor
S2600/5300/5500/5600/S6800E Heterogeneous Storage System If a SmartIO or 16
Gbit/s Fibre Channel (Two Ports) Module Is Configured for the Local Storage
System
12.7 Restarting a VMware ESX VM Fails After Online Migration Is Complete

OceanStor Dorado
12.1 The Link Becomes Abnormal After an HP

MSA2012FC/MSA2212FC Storage System Enables the
Internal Switch Mechanism
Symptom
An HP MSA2012FC/MSA2212FC storage system is connected to a local storage
system over a switched network. When data is being transferred between the two
storage systems, the link between them breaks intermittently.
Alarm Information
DeviceManager continuously generates alarms about link disconnection and link
recovery (alarm ID: 0xF000B005D).
Possible Causes
On the HP MSA2012FC/MSA2212FC, the Interconnected option is configured for
front-end ports. With this option, HP MSA2012FC/MSA2212FC storage system
enables its internal switch mechanism. Ports between its controllers are
interconnected for link redundancy.
When HP MSA2012FC/MSA2212FC storage system is connected to a local storage

system using switches, you are advised to disable the internal switch mechanism
of HP MSA2012FC/MSA2212FC storage system. That is because the compatibility
issue with HP MSA2012FC/MSA2212FC storage system causes the intermittent link
disconnection.
Procedure
Step 1 Log in to the management software for HP MSA2012FC/MSA2212FC.
Step 2 Choose MANAGE > GENERAL CONFIG > host port configuration. In the function
pane, click Change FC Port Interconnect Settings.
Step 3 Under Host Port Configuration, set Internal Host Port Interconnect to Straight-
through.
----End
Suggestion and Summary

● If HP MSA2012FC/MSA2212FC storage system is connected to a local storage
system using switches, you are advised to disable the internal switch
mechanism, as well as set Internal Host Port Interconnect to Straight-
through.
● If HP MSA2012FC/MSA2212FC storage system is connected to a local storage
system using direct connections, you are advised to enable the internal switch
mechanism, as well as set Internal Host Port Interconnect to
Interconnected.

OceanStor Dorado
12.2 After an HP P6500 Storage System Is Powered On

After a Power Failure, eDevLUNs for External LUNs Are
Still In the Fault State on DeviceManager for the Local
Storage System
Symptom
When a local storage system is connected to an HP P6500 storage system,
DeviceManager for the local storage system displays the eDevLUNs for mapped
external LUNs. After the HP P6500 storage system is powered on after a power
failure, the eDevLUNs are still in the Fault state.
Possible Causes
After the disk enclosures of an HP P6500 storage system are powered on after a
power failure, the local storage system reports a link disconnection and
reconnection event. Because remote LUNs are not ready, the local storage system
does not detect external LUNs after delivering a LUN scan command to the
heterogeneous storage system. In addition, the local storage system does not
detect external LUNs also when it does not detect a change in the status of
external LUNs.
Procedure
Step 1 In the management software for the HP P6500 storage system, check whether the
disk enclosures have been successfully powered on.
● If yes, go to Step 2.
● If no, wait for the disk enclosures to be completely powered on.
Step 2 In DeviceManager for the local storage system, manually start a scan for external
LUNs.
Step 3 Check whether eDevLUNs restore to the normal state.
● If yes, no further action is required.
● If no, keep the fault environment intact and contact technical support
engineers.
----End
12.3 A Local Storage System Encounters a Power

Failure and Cannot Detect External LUNs
Symptom
An HP P6500 storage system is connected to a local storage system. The local
storage system loses power and the HP P6500 storage system disks fail as well

OceanStor Dorado
when read or write I/Os are being transmitted between them. After the local
storage system regained power, DeviceManager does not detect the remote LUNs
that correspond to external LUNs. Later when the HP P6500 storage system disks
recover, DeviceManager still does not detect the remote LUNs.
Possible Causes
After the local storage system is powered on, it establishes a connection to the HP
P6500 storage system and uses the established connection to scan for mapped
external LUNs. Because the HP P6500 storage system's disks fail, its external LUNs
become unavailable. Consequently, the local storage system does not detect
external LUNs, and DeviceManager for the local storage system does not the
remote LUNs that correspond to the external LUNs.
Procedure
Step 1 Remove and reinsert all the cables between the local storage system and the
Step 2 In DeviceManager, check whether there are remote LUNs that correspond to
external LUNs.
● If no, keep the fault environment intact and contact technical support
engineers.
----End
12.4 The DeviceManager Cannot Display Remote

Device Information or Remote LUN Information After a
Heterogeneous Storage Systems Is Connected to the
Symptom
After connecting a heterogeneous storage system to the local storage system,
choose Data Protection > Remote Device. However, remote device information
fails to be displayed, or remote device information succeed to be displayed, but in
the Details area, click the Remote LUN tab. However, DeviceManager does not
display information about the mapped external LUNs.
Possible Causes
No logical link is established between the local storage system and the
heterogeneous storage system or no external LUN is mapped.
Procedure
Step 1 Check whether the initiator and external LUN mapping are successfully added.
● If yes, go to Step 2.

OceanStor Dorado
● If no, add the initiator and external LUN mapping.

NOTE
For details, see operation guides related to the heterogeneous storage system.
Step 2 Reinsert the physical cables between the heterogeneous storage system and local
storage system.
Step 3 On the DeviceManager, check whether the remote device information is correctly
displayed.
● If no, keep the fault environment intact and contact Huawei technical
support.
----End
Suggestion and Summary

The previous method applies to the following heterogeneous storage systems:
● HDS AMS series
● HDS HUS 100 series
● HDS HUS VM
● HDS USP-VM/HDS USP-V/SUN 9985V/SUN 9990V/HP XP20000/HP XP24000
● HDS USP/NSC series/SUN 9985/SUN 9990/HP SVS200/HP XP10000/HP
XP12000
● HDS VSP G200/G600/G800/G1000/HP XP7
● Fujitsu E4000 Model 80/100
● Sugon DS800-G25/MacroSAN MS3100/MacroSAN MS3300/MacroSAN
MS7000 series
● HDS VSP/HP P9500
● FALCON NSS/CDP series
12.5 When the Physical Connection Is Changed

Between NetApp FAS3000/FAS6000/FAS8000
Series/EMC XtremIO/NetApp AFF8000 Series/NetApp E
Series/TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/
DX200 S3/DX500 S3/DX600 S3 and the Local Storage
System, the Link Is Down
Symptom
NetApp FAS3000/FAS6000/FAS8000 Series/EMC XtremIO/NetApp AFF8000 Series/
NetApp E Series/TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/DX200 S3/DX500
S3/DX600 S3 is connected to the local storage system through a Fibre Channel
switch. When the physical connection is changed (the optical fiber is connected to

OceanStor Dorado
a different port of the switch or the optical fiber is moved from one port of the
heterogeneous storage system to another) between the NetApp FAS3000/
TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/DX200 S3/DX500 S3/DX600 S3 and
the switch, the link cannot be detected on DeviceManager of the local storage
system even though the physical connection works properly.
Possible Causes
NetApp FAS3000/FAS6000/FAS8000 Series/EMC XtremIO/NetApp AFF8000 Series/
NetApp E Series/TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/DX200 S3/DX500
S3/DX600 S3 automatically detects the status of the connection between its port
and the local storage system's port. If an inconsistency is found, NetApp FAS3000/
TOYOU iSUM780/iSUM850/Fujitsu DX100 S3/DX200 S3/DX500 S3/DX600 S3
refuses the connection, causing the link to become unreachable.
Procedure
Step 1 Remove and then insert the cable on the switch.
NOTE
This operation is performed on the switch port where the change occurs.
Step 2 On DeviceManager of the local storage system, check whether the link can be
detected.
● If no, keep the fault environment intact and contact Huawei technical
support.
----End
12.6 The Local Storage System Cannot Be Connected to

OceanStor S2600/5300/5500/5600/S6800E
Heterogeneous Storage System If a SmartIO or 16
Gbit/s Fibre Channel (Two Ports) Module Is Configured
for the Local Storage System
Symptom
If a SmartIO or 16 Gbit/s Fibre Channel (two ports) module is configured for the
OceanStor Dorado V6 series storage system (local storage system) and the local
storage system is connected to OceanStor S2600/S5300/S5500/S5600/S6800E
heterogeneous storage system using an optical fiber:
● The remote device that corresponds to the heterogeneous storage system

cannot be discovered in DeviceManager of the local storage system.

OceanStor Dorado
● The initiator that corresponds to the local storage system cannot be

discovered on the management interface of the heterogeneous storage
system.
Possible Causes
The mode of Fibre Channel front-end ports on the heterogeneous storage system
is not the TGT mode.
Procedure
Step 1 Log in to the management interface of the heterogeneous storage system's CLI.
Step 2 Run the econfrenewcfg -s fc_cfg_X_Y -i port_mode -v 2 -f 1 command to set the

mode of Fibre Channel front-end ports to TGT.
fc_cfg_X_Y indicates the serial number (SN) of a Fibre Channel front-end port in
the configuration file. Table 12-1 lists the SNs of ports on different devices.
Table 12-1 Port SNs
Device Type Port ID Port SN
S2600 0x1100a00b fc_cfg_4_0
0x110001 fc_cfg_4_1
0x110002 fc_cfg_6_0
0x110003 fc_cfg_6_1
S5300/S5500/S5600/ 0x110000 fc_cfg_5_0

S6800E
0x110001 fc_cfg_5_1
0x110002 fc_cfg_5_2
0x110003 fc_cfg_5_3
0x110100 fc_cfg_3_0
0x110101 fc_cfg_3_1
0x110102 fc_cfg_3_2
0x110103 fc_cfg_3_3
a: The first two digits in the last four digits of a port ID indicate the slot ID of
the port.
b: The last two digits in the last four digits of a port ID indicate the port SN.
Step 3 Restart the heterogeneous storage system to enable the configuration of Fibre
Channel front-end ports to take effect.
----End

OceanStor Dorado
12.7 Restarting a VMware ESX VM Fails After Online

Migration Is Complete
Symptom
After online migration is complete, restarting a VMware ESX VM that uses a raw
device mapping (RDM) fails.
Possible Causes
The VML IDs generated for the VMware ESX VM before and after it is restarted are
inconsistent. For details, go to https://kb.vmware.com/s/article/1016210.
Procedure
1. Delete the RDM from the VM.
2. Add the RDM again.
For the detailed procedure, go to https://kb.vmware.com/s/article/1016210.

OceanStor Dorado
SmartVirtualization Feature Guide 13 Configuration Restrictions
13 Configuration Restrictions
To ensure the correct implementation of SmartVirtualization, observe the

configuration restrictions while configuring the local and heterogeneous storage
systems.
NOTE
● This chapter only lists some of the supported heterogeneous storage systems. Use the
Huawei Storage Interoperability Navigator to obtain a complete list of supported
heterogeneous storage systems.
● The configuration restrictions described in this chapter are aimed at heterogeneous
storage systems unless otherwise specified.
13.1 General Restrictions

13.2 Compatibility Requirements for an Online Takeover
13.3 Dell Compellent SC Series
13.4 EMC CLARiiON/Fujitsu CX Series
13.5 EMC DMX Series
13.6 EMC VMAX Series
13.7 EMC VNX/EMC VNX2 Series
13.8 EMC VPLEX
13.9 EMC XtremIO
13.10 Fujitsu DX60/80/90
13.11 Fujitsu DX60 S2
13.12 Fujitsu E4000 Model 80/100
13.13 Fujitsu E8000 Model 1200/2200/Inspur AS5600
13.14 HDS AMS2000/HDS HUS 100 Series
13.15 HDS AMS/WMS Series
13.16 HDS USP/NSC Series/HDS USP-V/USP-VM/SUN 9985/9985V/9990/9990V/HP
SVS200/XP10000/12000/20000/24000

OceanStor Dorado
13.17 HDS HUS VM

13.18 HDS VSP G200/G400/G600/G800/G1000/HP XP7
13.19 Huawei Storage System
13.20 HP EVA Series
13.21 HP MSA1040/MSA2040
13.22 HP MSA2012FC/MSA2212FC
13.24 HP P2000 Series
13.25 HP 3PAR Series
13.26 IBM DS3XXX/IBM DS4XXX/IBM DS5XXX Series/Sugon DS800-G10/DS800-
G20/NetApp E series/Inspur AS1000G6/DCS 3700/Dell PowerVault MD Series/
TOYOU iSUM780/iSUM850
13.27 IBM DS6000 Series
13.29 IBM SVC/V3500/V3700/V5000/V7000/Inspur AS8000-M1/AS8000-M3
13.30 IBM XIV Series
13.31 NetApp FAS2000/FAS3000/V3000/FAS6000/V6000/FAS8000/AFF8000 Series
And IBM N3000/N6000 Series
13.32 Oracle SUN StorageTek 2540
13.33 Oracle SUN Storage6000 Series
13.34 TMS RamSan Series
13.35 Application Servers and Management Nodes
13.1 General Restrictions

This section describes the restrictions that must be observed when the OceanStor
Dorado V6 series hosts LUNs created on a heterogeneous storage system.
● After you modify configurations (including but not limited to creating
mappings, canceling mappings, or removing initiators) on the remote storage
device, scan for external LUNs on the local storage device to scan for disks
again.
● Generally, external LUNs that have been mapped to a local storage system
cannot be mapped to any hosts or storage systems any more.
Perform the following operations to map the external LUNs that have been
mapped to a local storage system to a host:
a. Stop services on the eDevLUN that corresponds to the external LUN.
b. Wait until all service data on the eDevLUN is sent to the heterogeneous
storage system.
Run the show lun_cache general command to view cache data on the
eDevLUN. If the values in Dirty Page and Fault Page are No, all service

OceanStor Dorado
data on the eDevLUN has been sent to the heterogeneous storage

system.
c. Delete the eDevLUN and cancel the mapping relationship between the
external LUNs and the local storage system in the heterogeneous storage
system.
d. Map the external LUNs to a host and restart services on the external
LUNs.
● Before deleting the external LUN from the heterogeneous storage system,
delete its corresponding eDevLUN from the local storage system.
● Do not map read-only LUNs (such as snapshot LUNs in some heterogeneous
storage systems and LUNs for which write protection is configured) to the
● Do not map external LUNs whose sector size is 4 KB to the local storage
system.
NOTE
For details about how to view the sector size, see operation guides for heterogeneous
storage systems.
● To ensure data on the heterogeneous storage system is consistent with that
on the local storage system, do not change Host LUN ID of external LUNs on
the heterogeneous storage system if external LUNs have been connected to
the local storage system and there are services on the external LUNs.
● The number of heterogeneous storage systems connected to a local storage
system cannot exceed the upper limit.
If the number of heterogeneous storage systems reaches or exceeds the upper
limit, take recommended actions in Table 13-1.
NOTE
For detailed specifications, refer to the Specifications Query Assistant (http://support-


OceanStor Dorado
Table 13-1 Recommended actions when the number of heterogeneous storage

systems reaches or exceeds the upper limit
Configuration Symptom Recommended Action
Scenario
The number of New heterogeneous 1. Remove one or more

heterogeneous storage systems heterogeneous storage systems
storage systems cannot be on the DeviceManager.
reaches the upper connected. 2. Disconnect the local storage
limit. system from the existing
3. Connect the local storage
system to new heterogeneous
storage systems.
4. Optional: If an iSCSI network is
set up between the local
storage system and the
add the new heterogeneous
storage systems on the
DeviceManager.
NOTE
After removing a cable, wait at least
30 seconds before reinserting it.
The number of Connected 1. Remove one or more

heterogeneous heterogeneous heterogeneous storage systems
storage systems storage systems on the DeviceManager.
exceeds the upper cannot be correctly 2. Disconnect the local storage
limit. identified. system from the storage
systems that cannot be
identified.
3. Connect the local storage
system to the storage systems
that cannot be identified.
4. Optional: If an iSCSI network is
set up between the local
storage system and the
add the unidentified
on the DeviceManager.
NOTE
● The number of links between a local storage system and heterogeneous

storage systems cannot exceed the upper limit.
If the number of links reaches or exceeds the upper limit, take recommended
actions in Table 13-2.

OceanStor Dorado
NOTE
For detailed specifications, refer to the Specifications Query Assistant (http://support-

Table 13-2 Recommended actions when the number of links reaches or exceeds
the upper limit
Scenario
The number of links New links cannot be 1. Remove one or more links
between a local added to the between the local storage
storage system and storage systems. system and heterogeneous
storage systems 2. Re-connect the new links.
reaches the upper
NOTE
limit. After removing a cable, wait at least
The number of links Connected links 1. Remove one or more links

between a local cannot be identified between the local storage
storage system and by the local storage system and heterogeneous
heterogeneous system. storage systems.
storage systems 2. Re-connect the links that
exceeds the upper cannot be identified.
limit.
NOTE
● When external LUNs are mapped to the local storage system, the number of
LUNs mapped from the same heterogeneous storage system to the local
storage system cannot exceed the upper limit, and host LUN IDs must range
from 0 to 8191.
If the number of mapped LUNs reaches or exceeds the upper limit, take
recommended actions in Table 13-3.

OceanStor Dorado
Table 13-3 Recommended actions when the number of LUN mappings reaches
the upper limit
Scenario
The number of LUNs New mapped LUNs cannot be 1. Perform the following
mapped to a local identified by the local storage operations on the
storage system system any more. heterogeneous
reaches the upper storage system:
limit. a. Remove at least
one LUN mapping.
b. Add a new LUN
mapping.
2. Perform the following
operation on the local
storage system:
a. Scan for LUNs.
The number of LUNs ● Existing mapped LUNs 1. Remove one or more

mapped to a local cannot be identified by the LUN mappings and
storage system local storage system. LUN mappings that
exceeds the upper ● The number of remote cannot be identified
limit. LUNs in the local link is on the heterogeneous
different from the number storage systems.
of remote LUNs actually 2. Scan for LUNs on the
mapped to the local local storage system.
storage system. 3. Add LUN mappings
NOTE for LUNs that cannot
Existing mapped LUNs cannot be identified on the
be identified by the local storage
heterogeneous
system after it is powered off
and re-powered on. storage systems.
4. Scan for LUNs on the
The number of LUNs After the new heterogeneous 1. Perform the following
mapped to the local storage system is connected operations on the
storage system to the controller, the local heterogeneous
through a controller storage system fails to storage system:
reaches the upper identify the heterogeneous Cancel the mapping
limit. storage system. of one or multiple
LUNs that are not in
use.
2. Perform the following
operation on the local
storage system:
Scan for LUNs.

OceanStor Dorado
13.2 Compatibility Requirements for an Online

Takeover
This section describes the compatibility requirements that the operating systems
of application servers, multipathing software, and cluster software must meet
upon an online takeover of a heterogeneous storage system.
Table 13-4 lists the compatibility requirements for an online takeover of a Huawei
Table 13-4 Compatibility requirements for an online takeover of a Huawei

Operating System Multipathing Cluster Software
Software
Microsoft Windows Server 2003 ● UltraPatha ● WSFC

R2 ● MPIO ● Oracle RAC 10g, Oracle
RAC 11g, and Oracle RAC
12c
Microsoft Windows Server 2008 ● UltraPath ● WSFC

SP2 ● MPIO ● Oracle RAC 10g, Oracle
12c

R2 SP1 ● MPIO ● Oracle RAC 10g, Oracle
12c

● MPIO ● Oracle RAC 10g, Oracle
12c

R2 ● MPIO ● Oracle RAC 10g, Oracle
12c
RHEL 5 and RHEL 5.1 to 5.11 UltraPath Oracle RAC 10g, Oracle RAC
11g, and Oracle RAC 12c
Device-Mapper Oracle RAC 10g, Oracle RAC


OceanStor Dorado

Software
SF DMP ● Storage Foundation and

High Availability 5.1 SP1
● Storage Foundation and
High Availability
6.0/6.0.1/6.0.2/6.0.3/6.0.5
/6.1/6.2


High Availability
6.0/6.0.1/6.0.2/6.0.3/6.0.5
/6.1/6.2

SF DMP Storage Foundation and

High Availability 6.1/6.2
SUSE 10 SP4 UltraPath -

SF DMP Storage Foundation and

High Availability 6.1 or later
SUSE 11 and SUSE 11 SP1 to UltraPath -

SP4

SUSE 12 and SUSE 12 SP1 to UltraPath -

SP4

OceanStor Dorado

Software

CentOS 5 and CentOS 5.1 to UltraPath -

5.11
CentOS 6 and CentOS 6.1 to UltraPath -

6.10
CentOS 7 and CentOS 7.1 to 7.5 UltraPath -
AIX 5.3 TL04 to TL12 ● UltraPath ● HACMP 5.3, 5.4

● AIX MPIO ● Oracle RAC 10g, Oracle
12c
AIX 6.1 ● UltraPath ● HACMP 6.1

12c
AIX 7.1 ● UltraPath ● HACMP 7.1b

12c
HP-UX 11i v1 PVLINK HP MC/Service Guard
HP-UX 11i v3 NMP ● HP MC/Service Guard

High Availability 6/6.2
● Oracle RAC 10g, Oracle
12c
Solaris 10 ● STMS ● Cluster 3.1 and Cluster

● UltraPath 3.2
12c
Solaris 11 and Solaris 11.1 to STMS ● Cluster 4.1 and Cluster

11.3 4.3
12c

OceanStor Dorado

Software
Oracle VM 3.1 to 3.4 for x86 Device-Mapper Oracle RAC 10g, Oracle RAC
a: UltraPath V100R008C20 or later supports basic masquerading. Versions that

are earlier than V100R008C20 support expended masquerading.
b: Set to No Reserve.
Table 13-5 shows the compatibility requirements for an online takeover of a third-
party heterogeneous storage system.
Table 13-5 Compatibility requirements for an online takeover of a third-party

Software
RHEL 5 and RHEL 5.1 to 5.11 DM-MultiPath Oracle RAC 11g and Oracle
RAC 12c
RHEL 6 and RHEL 6.1 to 6.10
RHEL 7 and RHEL 7.1 to 7.6
SUSE 10 SP1 and SUSE 10 SP3 Device Mapper
SUSE 11 and SUSE 11 SP1 to

SP4
SUSE 12 and SUSE 12 SP1 to

SP4
HP-UX 11i v3 Native ServiceGuard 11.20 (LVM

Multipathing Active-Passive)
ESXi 5.0/5.1/5.5/6.0/6.5/6.7 NMP vSphere HA

SATP only
supports
VMW_SATP_A
LUA or
VMW_SATP_D
EFAULT_AA
mode. PSP
only supports
VMW_PSP_FIX
ED,
VMW_PSP_RR,
or
VMW_PSP_MR
U mode.

OceanStor Dorado

Software
Microsoft Windows Server 2012 MPIO -

R2 and Microsoft Windows
Server 2016
AIX 6.1/7.1 AIX MPIO -
Note: In the case of Windows and AIX operating systems, you are advised to ask
professional service engineers of Huawei Storage to use the dedicated tool for
takeover.
13.3 Dell Compellent SC Series

This section describes the precautions about configuration operations performed
on the Dell Compellent SC series whose LUNs are hosted by the OceanStor
Dorado V6 series.
● The local storage system and Dell Compellent SC series (heterogeneous
storage systems) support switch-connection networks only, instead of direct-
connection networks.
● Comply with the following rules upon zone division:
– When zones are divided by port, allocate the primary port and reserved
port of Dell Compellent SC series and ports of Huawei storage system to
the same zone and all primary and reserved ports (on Dell Compellent SC
series) that are connected to switches to another zone.
– When zones are divided by WWN, allocate the primary port WWN of Dell
Compellent SC series and port WWNs of Huawei storage system to the
same zone and WWNs of all primary and reserved ports (on Dell
Compellent SC series) that are connected to switches to another zone.
● Set Operational Mode of ports of Dell Compellent SC series to Legacy Mode.
Ensure that each Fault Domain contains one port of both controllers and
Purpose is set to Front End Primary and Front End Reserved respectively.
On the management interface of Dell Compellent SC series, choose System
Management > System > Setup > Configure Local Ports. The Configure
Local Ports dialog box is displayed. You can view and modify the desired
information, as shown in Figure 13-1.

OceanStor Dorado
Figure 13-1 Configure Local Ports dialog box
● Click Create Server to create a host and set Operating System to Other
Multipath.
NOTE
For details about how to set parameters that are not mentioned in this section, see the
related documents of the Dell Compellent SC series.
13.4 EMC CLARiiON/Fujitsu CX Series

on the EMC CLARiiON/Fujitsu CX series whose LUNs are hosted by the OceanStor
Dorado V6 series.
● For CLARiiON CX200/CX400/CX600/Fujitsu CX200/CX400/CX600, set Initiator

Type to CLARiiON Open, and Failover Mode to 1.
● For CLARiiON AX4-5, do not map snapshot LUNs (snapshots) to the local
storage system for hosting. Select Connection and set Operating System to
STANDARD.
● For other supported heterogeneous storage systems, set Initiator Type to
CLARiiON Open, and Failover Mode to 4.
NOTE
Before resetting Failover Mode, disconnect the front-end port (that corresponds to the
initiator) on the local storage system from EMC storage system. After the resetting is
complete, restore the connection.
NOTE
related documents of the EMC CLARiiON/Fujitsu CX series.

OceanStor Dorado
13.5 EMC DMX Series

on the EMC DMX series whose LUNs are hosted by the OceanStor Dorado V6
series.
When configuring a port, set parameters based on the following information:
● Set Volume_Set_Addressing to Disabled.

● Set Non_Participating to Disabled.
● Set Common_Serial_Number to Enabled.
● Set Disable_Q_Reset_on_UA to Disabled.
● Set Return_busy_for_abort to Disabled.
● Set SCSI-3 to Enabled.
● Set Unique_WWN to Enabled.
● Set Point_to_Point to Enabled.
NOTE
When the EMC DMX series storage system is connected to the local storage system in a
standard switched network, set this parameter to Enabled. When the EMC DMX series
storage system is connected to the local storage system in a standard direct-connection
network, set this parameter to Disabled.
● Set OpenVMS to Disabled.
● Set SPC-2 to Enabled.
● Set Enable Auto Negotiation (EAN) to Disabled.
NOTE
related documents of the EMC DMX series.
13.6 EMC VMAX Series

on the EMC VMAX series whose LUNs are hosted by the OceanStor Dorado V6
series.
When configuring a port, set parameters based on the following information:
● Set Negotiate_Reset(N) to Disabled.

● Set Soft_Reset(S) to Disabled.
● Set Environ_Set(E) to Disabled.
● Set HP3000_Mode(B) to Disabled.
● Set Common_Serial_Number(C) to Enabled.
● Set Disable_Q_Reset_on_UA(D) to Enabled.
● Set Sunapee(SCL) to Disabled.
● Set Siemens(S) to Disabled.

OceanStor Dorado
● Set Sequent(SEQ) to Disabled.

● Set Avoid_Reset_Broadcast(ARB) to Disabled.
● Set Server_On_AS400(A4S) to Disabled.
● Set SCSI_3(SC3) to Enabled.
● Set SPC2_Protocol_Version(SPC2) to Enabled.
● Set SCSI_Support1(OS2007) to Enabled.
● Set Volume_Set_Addressing(V) to Disabled.
● Set Non_Participating(NP) to Disabled.
● Set Unique_WWN(UWN) to Enabled.
● Set Access_Logix(ACLX) to Enabled.
● Set OpenVMS(OVMS) to Disabled.
● Set AS400(AS4) to Disabled.
● Set Auto_Negotiate(EAN) to Enabled.
● For a standard direct-connection network, set Init_Point_to_Point to
Disabled. For a standard switched network, set Init_Point_to_Point to
Enabled.
13.7 EMC VNX/EMC VNX2 Series

on the EMC VNX/EMC VNX2 series whose LUNs are hosted by the OceanStor
Dorado V6 series.
Set Initiator Type to CLARiiON/VNX, and Failover Mode to Active-Active

mode(ALUA)-failovermode 4. When configuring the series of storage systems,
note the following:
NOTE
Before resetting Failover Mode, disconnect the front-end port (that corresponds to the
initiator) on the local storage system from EMC storage system. After the resetting is
complete, restore the connection.
NOTE
related documents of the EMC VNX/EMC VNX2 series.
13.8 EMC VPLEX

on the EMC VPLEX whose LUNs are hosted by the OceanStor Dorado V6 series.
When registering an initiator, set Host Type to default.
NOTE
related documents of the EMC VPLEX.

OceanStor Dorado
13.9 EMC XtremIO

on EMC XtremIO storage system that is taken over by the OceanStor Dorado V6
series.
● Set the type of the initiator's operating system to Linux.

● Do not map external LUNs whose sector size is 4 KB to the local storage
system.
NOTE
For details about other parameters, see the documents specific to EMC XtremIO storage
system.
13.10 Fujitsu DX60/80/90

on the Fujitsu DX60/80/90 whose LUNs are hosted by the OceanStor Dorado V6
series.
● When creating a LUN, set Type to Open.

● When configuring system parameters, do not select Reject INQUIRY from
Unauthorized Host in Setup Subsystem Parameters.
● Configure port parameters based on the values in the following figure.
Connection ● For a standard switched network,

set Connection to Fabric.
● For a standard direct-connection
network, set Connection to FC-AL.
Transfer Rate (Gbit/s) Auto Negotiation

OceanStor Dorado
Host Affinity Enable
Reset Scope T_L
NOTE
In the preceding figure, the Set Loop ID, Loop ID, Frame Size (byte) and Release
Reservation if Chip is Reset configuration has no restrictions.
● Configure host parameters based on the values in the following figure.
Byte-0 of Inquiry Response No Conversion (Default)
Inquiry VPD ID Type Type1 + Type3 (Default)
Inquiry Standard Data Version Version 5 (Default)
Command Timeout Interval Default (25sec.)
Load Balance Response [Disable] Unit Attention (Default)
Reservation conflict Response For Test Normal (Default)

Unit Ready
Change Volume Mapping Report
Volume Capacity Expansion Report
Vendor Unique Sense Code Report
Host Specific Mode Normal (Default)
Asymmetric/Symmetric Logical Unit ACTIVE-ACTIVE/PREFERRED_PATH

Access (Default)
Sense Data Conversion Linux Recommended (When not using

GRMPD)

OceanStor Dorado
● When Host Specific Mode is set to Normal (Default) and a LUN mapping is
added, the value of the Host LUN ID parameter cannot be larger than 255.
NOTE
related documents of the Fujitsu DX60/80/90.
13.11 Fujitsu DX60 S2

on the Fujitsu DX60 S2 whose LUNs are hosted by the OceanStor Dorado V6
series.
● When configuring system parameters, do not select Reject INQUIRY from
Unauthorized Host in Setup Subsystem Parameters.
Connection ● For a standard switched network,

set Connection to Fabric.
● For a standard direct-connection
network, set Connection to FC-AL.
Transfer Rate (Gbit/s) Auto Negotiation
Host Affinity Enable
Reset Scope I_T_L
NOTE
In the preceding figure, the Set Loop ID, Loop ID, Frame Size (byte) and Release
Reservation if Chip is Reset configuration has no restrictions.

OceanStor Dorado
Byte-0 of inquiry Response No Conversion (Default)
Command Timeout Interval Default (25sec.)
Load Balance Response [Disable] Unit Attention (Default)
Reservation conflict Response For Test Normal (Default)

Unit Ready
Change Volume Mapping No Report (Default)
Volume Capacity Expansion No Report (Default)
Vendor Unique Sense Code No Report (Default)
Host Specific Mode Normal (Default)
Asymmetric/Symmetric Logical Unit ACTIVE-ACTIVE/PREFERRED_PATH

Access (Default)
Unrecoverable Sense Report Mode Disable (Default)
Sense Data Conversion Linux Recommended (When not using

GRMPD)
● When Host Specific Mode is set to Normal (Default) and a LUN mapping is
added, the value of the Host LUN ID parameter cannot be larger than 255.
NOTE
related documents of the Fujitsu DX60 S2.

OceanStor Dorado
13.12 Fujitsu E4000 Model 80/100

on the Fujitsu E4000 Model 80/100 whose LUNs are hosted by the OceanStor
Dorado V6 series.
● For a standard direct-connection network, set FC Connection Settings to FC-
AL Connection. For a standard switched network, set FC Connection
Settings to Fabric Connection.

OceanStor Dorado
Service Class Class 3
FC Transfer Rate 4G/2G/1G Bit Auto Setting
Scope of LUR Action Acts on T_L
HP-UX Connection Setting Disable
Addressing Mode Settings Host Table Settings Mode
NOTE
In the preceding figure, the Frame Size Setting and Release Reservation upon Chip Reset
configuration has no restrictions.

OceanStor Dorado
Response status to host when Unit Attention (Delay)

overloaded

OceanStor Dorado
Response to inquiry commands Default
Inquiry Standard Data NACA Function Disable
Inquiry Standard Data Version Field Default
Inquiry Command Page 83 Type 01 & 03
Target Port Group Access Support Enable
Response Sense at Firmware Hot Enable

Switching
NOTE
In the preceding figure, the Reservation Conflict Response to Test Unit Ready
Commands configuration has no restrictions.
NOTE
related documents of the Fujitsu E4000 Model 80/100.
13.13 Fujitsu E8000 Model 1200/2200/Inspur AS5600

on the Fujitsu E8000 Model 1200/2200/Inspur AS5600 whose LUNs are hosted by
the OceanStor Dorado V6 series.
● For a standard direct-connection network, set Connection Topology to FC-AL

Connection; For a standard switched network, set Connection Topology to
Fabric Connection.
Transfer Rate 8G/4G/2Gbps Auto
Affinity Mode ON
Reset Scope T_L

OceanStor Dorado
NOTE
In the preceding figure, the Loop-ID (Manual), Loop-ID (Auto), FC Frame Size and
Reserve Cancel at Chip Reset configuration has no restrictions.
Command Time-out Interval Standard (25 Seconds)
Host Specific Mode Normal Mode (Default)
Asymmetric/Symmetric Logical Unit ACTIVE/ACTIVE (Default)

Access
LUN Mapping Changes Report
LUN Capacity Expansion Report
Sense Code Conversion Pattern Linux Recommended (When not using

GRMPD)
NOTE
In the preceding figure, the Reservation Conflict Response for Test Unit Ready
NOTE
related documents of the Fujitsu E8000 Model 1200/2200/Inspur AS5600.

OceanStor Dorado
13.14 HDS AMS2000/HDS HUS 100 Series

on the HDS AMS2000/HDS HUS 100 series whose LUNs are hosted by the
OceanStor Dorado V6 series.
● For a standard direct-connection network, set Topology to Loop. For a

standard switched network, set Topology to Point to Point.
● When creating a host, set Platform, Middleware, and Common Setting to
Linux, not specified, and Standard Mode respectively.
● When an external LUN is set as a command device, do not map it to a local
storage system for hosting.
● For those external LUNs that are mapped to a local storage system, do not set
them as command devices.
● Do not map snapshot LUNs (Snapshot Logical Units) to a local storage
system for hosting.
NOTE
This restriction only applies to HDS AMS2000 series storage systems.

● The default values of Vendor ID and Product ID are HITACHI and DF600F
respectively. Do not modify them.
NOTE
related documents of the HDS AMS2000/HDS HUS 100 series.
13.15 HDS AMS/WMS Series

on the HDS AMS/WMS series whose LUNs are hosted by the OceanStor Dorado V6
series.
● The default values of Vendor ID and Product ID are HITACHI and DF600F
respectively. Do not modify them.
● Set Platform to Linux, Alternate Path to not specified, and Failover to not
specified.
● Set Host Connection Mode 1 to Standard Mode. For Host Connection
Mode 2, do not modify the values of the parameters. Keep the default value
Disable for all parameters.
● Do not map the external LUNs whose property is Differential
ManagementLU to a local storage system.
storage system for hosting.
● External LUNs that have been mapped to the local storage system for hosting
cannot be set to Command Device.
● For a standard direct-connection network, set Topology to Loop. For a
standard switched network, set Topology to Point to Point.

OceanStor Dorado
NOTE
related documents of the HDS AMS/WMS series.
13.16 HDS USP/NSC Series/HDS USP-V/USP-VM/SUN

9985/9985V/9990/9990V/HP SVS200/
XP10000/12000/20000/24000
on the HDS USP/NSC Series/HDS USP-V/USP-VM/SUN 9985/9985V/
9990/9990V/HP SVS200/XP10000/12000/20000/24000 whose LUNs are taken over
by the OceanStor Dorado V6 series.
● For Fibre Channel front-end ports on a standard direct-connection network,
set Connection to FC-AL and Fabric to Off.
● For Fibre Channel front-end ports on a switched network, set Connection to
Point to Point and Fabric to On.
● Set HOST MODE as Windows.
storage system.
NOTE
For details about how to set other parameters not mentioned in this section, see the related
documents of the HDS USP/NSC Series/HDS USP-V/USP-VM/SUN 9985/9985V/
9990/9990V/HP SVS200/XP10000/12000/20000/24000.
13.17 HDS HUS VM

on the HDS HUS VM whose LUNs are hosted by the OceanStor Dorado V6 series.
● When creating a host, set Host Mode to 0C[Windows].
● For those external LUNs that are mapped to a local storage system, do not set
them as command devices.
● Do not map the snapshot LUNs to a local storage system for hosting.
NOTE
related documents of the HDS HUS VM.
13.18 HDS VSP G200/G400/G600/G800/G1000/HP XP7

on the HDS VSP G200/G400/G600/G800/G1000/HP XP7 whose LUNs are hosted
by the OceanStor Dorado V6 series.

OceanStor Dorado
● When creating a host, set Host Mode to 00[Standard].

storage system.
NOTE
related documents of the HDS VSP G200/G400/G600/G800/G1000/HP XP7 series.
13.19 Huawei Storage System

on a Huawei storage system whose LUNs are hosted by the OceanStor Dorado V6
series.
13.19.1 Huawei S12100/S12300

on the Huawei S12100/S12300 whose LUNs are hosted by the OceanStor Dorado
V6 series.
● For a standard direct-connection network, set Connection Topology to FC-AL
Connection. For a standard switched network, set Connection Topology to
Fabric Connection.
Transfer Rate 8G/4G/2Gbps Auto
Affinity Mode ON
Reset Scope T_L

OceanStor Dorado
NOTE
In the preceding figure, the Loop-ID (Manual), Loop-ID (Auto), FC Frame Size and
Reserve Cancel at Chip Reset configuration has no restrictions.
Command Time-out Interval Standard (25 Seconds)
Host Specific Mode Normal Mode (Default)
Asymmetric/Symmetric Logical Unit ACTIVE/ACTIVE (Default)

Access
LUN Mapping Changes Report
LUN Capacity Expansion Report
Sense Code Conversion Pattern Linux Recommended (When not using

GRMPD)

OceanStor Dorado
NOTE
In the preceding figure, the Reservation Conflict Response for Test Unit Ready
NOTE
related documents of the Huawei S12100/S12300.
13.19.2 Huawei S3000

on the Huawei S3000 whose LUNs are hosted by the OceanStor Dorado V6 series.
When creating a host, set its type to Linux and ADT STATUS to Disabled.
NOTE
related documents of the Huawei S3000.
13.19.3 Huawei VIS6000/VIS6000T

This section describes configuration of the local storage system and Huawei
VIS6000/VIS6000T storage systems when OceanStor Dorado V6 series storage
system takes over services of Huawei VIS6000/VIS6000T storage systems.
● For Huawei VIS6000 storage systems, set the operating system type to Linux
when creating the host. For Huawei VIS6000T storage systems, set the
operating system type to Linux.
● Pay attention to the following precautions when the local storage system
takes over services of Huawei VIS6000/VIS6000T online:
– You are advised to install UltraPath of V100R005 or later versions on the
application server.
– When switching the path on a host, remove the physical cables between
the heterogeneous storage system and application server.
NOTE
For other parameters that are not included in this section, see related documents on
Huawei VIS6000/VIS6000T storage system.
13.19.4 Other Types of Huawei Storage Systems

on other types of Huawei storage systems whose LUNs are hosted by the
● Do not select the ALUA mode for initiators.

NOTE
It applies to all Huawei storage systems in a non-online takeover scenario.

● When creating a host, set its type to Linux.

OceanStor Dorado
NOTE
It applies to all Huawei storage systems in a non-online takeover scenario.

● Do not enable CHAP authentication for iSCSI connections.
NOTE
It applies to Huawei T series storage system.

● Before mapping multiple thin LUNs to the local storage system, weigh the I/O
pressure on the host that delivers services. Assess whether the service I/O
pressure on the host remains within the capability of the thin LUNs on the
NOTE

● Do not map command devices to the local storage system for hosting.
NOTE
It applies to Huawei T/Dorado series storage system.

● If external LUNs are mapped to the local storage system through the default
host group, the LUN information cannot be updated automatically. In this
case, manually scan for LUNs.
NOTE

● If OceanStor UltraPath is used, note the following:
– When OceanStor UltraPath of which the version is earlier than
V100R008C20 is installed on an application server, you can use the online
takeover function of the local storage system to create eDevLUNs whose
LUN masquerading type is Extended masquerading and use the
eDevLUNs to take over external LUNs online, or you can use the offline
takeover function.
After the takeover, if OceanStor UltraPath is upgraded to V100R008C20
or later, perform the following operations to ensure the functionality of
the SmartVirtualization feature and storage systems' new features as well
as for the online takeover by using the basic masquerading function:
i. Cancel the mappings of the eDevLUNs and scan for LUNs on the
application server.
ii. Add the mappings of the eDevLUNs and scan for LUNs on the
application server.
If OceanStor UltraPath needs to be upgraded to V100R008C20 or
later before an offline takeover, stop services on the application
server, disconnect the application server and the heterogeneous
storage system, use optical fibers or network cables to connect the
host port on the application server and the service port on the local
storage system, preventing services on the application server from
being stopped multiple times.
– When OceanStor UltraPath of which the version is V100R008C20 and
later is installed on an application server, if the SN of the heterogeneous
storage system version can be queried, you are advised to use the online

OceanStor Dorado
takeover function of the local storage system to create eDevLUNs whose

LUN masquerading type is Basic masquerading and use the eDevLUNs
to take over external LUNs online. If the SN of the heterogeneous storage
system version cannot be queried, you can use the online takeover
function of the local storage system to create eDevLUNs whose LUN
masquerading type is Extended masquerading and use the eDevLUNs to
take over external LUNs online, or you can use the offline takeover
function.
Models and versions of storage systems whose SNs cannot be queried
using UltraPath:
▪ S2300E/S2600
▪ S5300/S5500/S5600
▪ Dorado2100
▪ Versions earlier than Dorado5100 V100R001C00SPC800 (excluding

▪ Versions earlier than Dorado2100 G2 V100R001C00SPC500

(excluding V100R001C00SPCa00 and V100R001C00SPCb00)
▪ Versions earlier than S2200T/S2600T/S5500T/S5600T/S5800T/S6800T

V1R5C00SPC400
▪ Versions earlier than S2200T/S2600T/S5500T/S5600T/S5800T/S6800T

V1R5C01SPC100
NOTE
related documents of the Huawei storage system.
13.20 HP EVA Series

on the HP EVA series whose LUNs are hosted by the OceanStor Dorado V6 series.
● When creating a host, set its type to Linux.

● Do not connect two or more heterogeneous storage systems with the same
WWN to the same local storage system.
● Do not map two or more external LUNs with the same WWN to the same
local storage system for hosting.
● For HP EVA5000, when it is connected to a local storage system over a
standard direct-connection network, set Direct Connect On All Host Ports to
Yes in Host Port Config. When it is connected to a local storage system over
a standard switch-connection network, set Direct Connect On All Host Ports
to No in Host Port Config.
NOTE
related documents of the HP EVA series.

OceanStor Dorado
13.21 HP MSA1040/MSA2040
on the HP MSA1040/MSA2040 storage system that is taken over by the OceanStor
Dorado V6 series.
● In a scenario where a standard direct-connection network is used, set

Topology of Fibre Channel ports to Auto.
● In a scenario where LUN mappings are created, set Mode to read-write.
NOTE
For details about other parameters, see the documents specific to HP MSA1040/MSA2040
storage system.
on the HP MSA2012FC/MSA2212FC whose LUNs are hosted by the OceanStor
Dorado V6 series.
● For a standard direct-connection network, set the link mode to loop, as well
as Internal Host Port Interconnect to Interconnected to enable the internal
switch mechanism.
● For a standard switched network, set the link mode to loop or Point to Point,
as well as Internal Host Port Interconnect to Straight-through to disable
the internal switch mechanism.
NOTE
After modifying the link mode, remove and reinsert the cables.
● Do not change the owning controller of virtual disks
NOTE
related documents of the HP MSA2012FC/MSA2212FC.
on the HP MSA2312FC/MSA2324FC storage system that is taken over by the
● In a scenario where a standard direct-connection network is used, choose

Configuration > System Settings > Host Interfaces and set Connection
Mode to loop.
● In a scenario where a standard switch network is used, choose Configuration
> System Settings > Host Interfaces and set Connection Mode to Point to
Point.
● In the Manage Host Mappings dialog box, set Access to read-write.

OceanStor Dorado
NOTE
After modifying the link mode, remove and insert the cables.
NOTE
For details about other parameters, see the documents specific to HP MSA2312FC/
MSA2324FC storage system.
13.24 HP P2000 Series

on the HP P2000 series whose LUNs are hosted by the OceanStor Dorado V6
series.
● When creating a host, set Profile to Standard.
● The host LUN ID of an external LUN mapped to a local storage system ranges
from 1 to 255.
● For the same initiator, external LUNs can be mapped to a local storage system
using the default or explicit mapping method, and different methods require
different host LUN IDs.
● Do not map external LUNs whose property is Access LUN to a local storage
system.
● When read or write I/Os are being processed, do not change the owning
controller of virtual disks.
NOTE
related documents of the HP P2000 series.
13.25 HP 3PAR Series

on the HP 3PAR series whose LUNs are hosted by the OceanStor Dorado V6 series.
● Do not map the same LUN with different host LUN IDs to hosts and the host
group where the hosts reside.
● For a standard direct-connection network, set Connection Type to Loop. For
a standard switched network, set Connection Type to Point.
● When creating a host, set Persona to 1-Generic, set Host OS to Linux.
● When setting the port, set Connection mode to Host, set VLUN Change
Notification (VCN) to Disabled.
NOTE
related documents of the HP 3PAR series.

OceanStor Dorado
13.26 IBM DS3XXX/IBM DS4XXX/IBM DS5XXX Series/

Sugon DS800-G10/DS800-G20/NetApp E series/Inspur
AS1000G6/DCS 3700/Dell PowerVault MD Series/
TOYOU iSUM780/iSUM850
on the IBM DS3XXX/IBM DS4XXX/IBM DS5XXX Series/Sugon DS800-G10/DS800-
G20/NetApp E series/Inspur AS1000G6/DCS 3700/Dell PowerVault MD Series/
TOYOU iSUM780/iSUM850 whose LUNs are hosted by the OceanStor Dorado V6
series.
● For IBM DS4200/DS4300/DS4700/DS4800/DS4300 Turbo/DS4500/DS5020/

DS5100/DS5300/DS3400/DS3950/DS4100/DS4400, set Host type to
LNXCLVMWARE or LNXCLUSTER.
● For IBM DS3512/DS3524, set Host type (operating system) to Linux (MPP/
RDAC).
● For Sugon DS800-G10/DS800-G20/NetApp E series/Inspur AS1000G6/DCS
3700/Dell PowerVault MD series/TOYOU iSUM780/iSUM850, set Host type
(operating system) to Linux (MPP/RDAC).
system.
NOTE
For some heterogeneous storage systems, you must add Access LUN mappings before
adding other types of LUN mappings. Therefore, after the other types of LUN mappings are
added, delete the Access LUN mappings if they are not necessary.
● When read or write I/Os are being processed, do not change the owning
controller of logical drives.
NOTE
Logical drives are presented as LUNs.
NOTE
For details about how to set other parameters not mentioned in this section, see the related
documents of the IBM DS3XXX/IBM DS4XXX/IBM DS5XXX series/Sugon DS800-G10/DS800-
G20/NetApp E series/Inspur AS1000G6/DCS 3700/Dell PowerVault MD series/TOYOU
iSUM780/iSUM850.

on the IBM DS6000 series whose LUNs are hosted by the OceanStor Dorado V6
series.
● When creating volume group, set Host Type to LinuxSuse.

● When creating host, set Type to Intel-based servers (Linux Suse)
(LinuxSuse).

OceanStor Dorado
● When creating Volume, set Volume type to Standard Open Systems - DS

Sizes.
NOTE
related documents of the IBM DS6000 series.

on the IBM DS8000 series whose LUNs are hosted by the OceanStor Dorado V6
series.
● When creating a host, set host type to LinuxSuse or profile to Intel -
LinuxSuse.
NOTE
When running the mkvolgrp command to create a volume group, set host type to
LinuxSuse or set type to scsimap256.
● When creating a volume group, set type to scsimap256.
● For a standard direct-connection network, set the port mode to FC-AL.
● For a switched network, set the port mode to SCSI-FCP.
NOTE
related documents of the IBM DS8000 series.
13.29 IBM SVC/V3500/V3700/V5000/V7000/Inspur

AS8000-M1/AS8000-M3
on the IBM SVC/V3500/V3700/V5000/V7000/Inspur AS8000-M1/AS8000-M3 that
are hosted by the OceanStor Dorado V6 series.
● When creating a host, set Host Type to Generic (Default).
● If Fibre Channel ports cannot be automatically discovered on the
heterogeneous storage system when you create hosts, manually add Fibre
Channel ports.
NOTE
For details about other parameters, see documentation of IBM SVC/V3500/V3700/V5000/

V7000/Inspur AS8000-M1/AS8000-M3 series storage systems.
13.30 IBM XIV Series

on the IBM XIV storage systems when Huawei OceanStor Dorado V6 series takes
over them.
When creating a host, set its Type to default.

OceanStor Dorado
NOTE
For details about other parameters, see documentation of IBM XIV storage systems.
13.31 NetApp FAS2000/FAS3000/V3000/FAS6000/

V6000/FAS8000/AFF8000 Series And IBM N3000/N6000
Series
on the NetApp FAS2000/FAS3000/V3000/FAS6000/V6000/FAS8000/AFF8000 series
and IBM N3000/N6000 series whose LUNs are hosted by the OceanStor Dorado
V6 series.
● When creating a LUN, set Type of LUNs to Linux, or set LUN Protocol Type
to Linux.
● When creating an initiator group, set Operating System to Linux, and select
Enable ALUA, or run the igroup set [-f] <initiator_group> alua yes command
on the CLI to enable ALUA.
● Do not modify the WWNs of external LUNs when mapping them to the local
storage system.
● Do not set the external LUNs to the offline status when services are running.
● The NetApp FAS3220/FAS3250/V3220/V3250/FAS6000/V6000 series supports
only C-Mode.
– The type of a heterogeneous storage system's port that used to connect
to the local storage system must be target. You can run the node run -
node <node name> fcadmin config -t target <Adapter> command to
check the port type.
– The local storage system can only be connected to the heterogeneous
system over the network using switches.
● The other device models support only 7-Mode.
– The type of a heterogeneous storage system's port that used to connect
to the local storage system must be target. You can run the fcadmin
config command to check the port type.
– The value of cfmode must be single_image. You can run the fcp show
cfmode command on the heterogeneous storage system to check the
current mode.
– The nodename of each controller must be the same. You can run the fcp
nodename command on the heterogeneous storage system to check the
current nodename value.
NOTE
related documents of the NetApp FAS2000/FAS3000/V3000/FAS6000/V6000/FAS8000/
AFF8000 series and IBM N3000/N6000 series.

OceanStor Dorado
13.32 Oracle SUN StorageTek 2540

on the Oracle SUN StorageTek 2540 storage systems when Huawei OceanStor
Dorado V6 series takes over them.
When creating a host, set Host Mode to Linux.
NOTE
For details about other parameters, see documentation of Oracle SUN StorageTek 2540
storage systems.
13.33 Oracle SUN Storage6000 Series

on the Oracle SUN Storage6000 series whose LUNs are hosted by the OceanStor
Dorado V6 series.
● When creating a host, set Host Mode to Linux.
● For NVSRAM, set offset 0x24=0x00 and offset 0x27=0x00.
system.
NOTE
related documents of the Oracle SUN Storage6000 series.
13.34 TMS RamSan Series

on the TMS RamSan series storage system that are taken over by the OceanStor
Dorado V6 series.
Do not map external LUNs whose sector size is 4 KB to the local storage system.
NOTE
For details about other parameters, see documentation about the TMS RamSan series
storage system.
13.35 Application Servers and Management Nodes

When configuring SmartVirtualization, comply with related restrictions to
configure application servers and management nodes.
13.35.1 ESXi 5.X VMs

This section describes configuration operations required to be performed on ESXi
5.X VMs when a Huawei OceanStor Dorado V6 series storage system (local

OceanStor Dorado
storage system) is used to take over services from heterogeneous storage systems
in an ESXi 5.X hypervisor.
In an ESXi hypervisor, if services taken over by the local storage system using
SmartVirtualization are not required, you need to restore the mapping
relationships between heterogeneous storage systems and VMs, so that the
heterogeneous storage systems can continue to carry VM services. If the VAAI
function enabled on the ESXi VMs is not supported by the heterogeneous storage
systems, click the following official VMware website link and configure ESXi 5.X
VMs to ensure the normal operating of VM services: https://kb.vmware.com/
selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2006858.
13.35.2 Windows Server 2012/Windows Server 2008

This section describes how to configure an application server to install Windows
Server 2012/Windows Server 2008 on it.
In a non-cluster or cluster environment where Windows Server 2012/Windows
Server 2008 and Microsoft Multipath I/O (MPIO) are deployed, set the MPIO
routing policy to Round Robin With Subnet before configuring the online
takeover function.
1. Log in to the Windows Server 2012/Windows Server 2008 application server.
2. Right-click Computer and choose Manage from the shortcut menu.
The Server Manager dialog box is displayed.
3. In the navigation tree, choose Store > Disk Management.
4. Right-click a logical disk that is mapped from the heterogeneous storage
system to the application server and choose Properties from the shortcut
menu.
5. In the Properties dialog box, click the MPIO tab.
6. Set Load Balance Policy to Round Robin.
NOTE
In a cluster environment, perform the operations on each node in the cluster.
13.35.3 VCS Cluster

This section describes how to configure a VCS cluster.
● If you map the LUN whose host lun id is 0 from the heterogeneous storage
system or local storage system to a VCS cluster, you must restart the VCS
cluster so that the LUN can be scanned.
● Before eDevLUNs are taken over (that is, before the change lun_takeover
finish_switch_path command is executed on all eDevLUNs), new logical disks
cannot be created and used in VCS.

OceanStor Dorado
SmartVirtualization Feature Guide A How to Obtain Help
A How to Obtain Help
If a tough or critical problem persists in routine maintenance or troubleshooting,

contact Huawei for technical support.
A.1 Preparations for Contacting Huawei

To better solve the problem, you need to collect troubleshooting information and
make debugging preparations before contacting Huawei.
A.1.1 Collecting Troubleshooting Information

You need to collect troubleshooting information before troubleshooting.
You need to collect the following information:
● Name and address of the customer
● Contact person and telephone number
● Time when the fault occurred
● Description of the fault phenomena
● Device type and software version
● Measures taken after the fault occurs and the related results
● Troubleshooting level and required solution deadline
A.1.2 Making Debugging Preparations

When you contact Huawei for help, the technical support engineer of Huawei
might assist you to do certain operations to collect information about the fault or
rectify the fault directly.
Before contacting Huawei for help, you need to prepare the boards, port modules,
screwdrivers, screws, cables for serial ports, network cables, and other required
materials.

OceanStor Dorado
SmartVirtualization Feature Guide A How to Obtain Help
A.2 How to Use the Document

Huawei provides guide documents shipped with the device. The guide documents
can be used to handle the common problems occurring in daily maintenance or
troubleshooting.
To better solve the problems, use the documents before you contact Huawei for
technical support.
A.3 How to Obtain Help from Website

Huawei provides users with timely and efficient technical support through the
regional offices, secondary technical support system, telephone technical support,
remote technical support, and onsite technical support.
Contents of the Huawei technical support system are as follows:
● Huawei headquarters technical support department
● Regional office technical support center
● Customer service center
● Technical support website: https://support.huawei.com/enterprise/
You can query how to contact the regional offices at https://
support.huawei.com/enterprise/.
A.4 Ways to Contact Huawei

Huawei Technologies Co., Ltd. provides customers with comprehensive technical
support and service. For any assistance, contact our local office or company
headquarters.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's
Republic of China
Website: https://e.huawei.com/

OceanStor Dorado
SmartVirtualization Feature Guide B Glossary
B Glossary
A
AC power module The module that transfers the external AC power
supply into the power supply for internal use.
Application server A service processing node (a computer device) on the
network. Application programs of data services run
on the application server.
Asynchronous remote A kind of remote replication. When the data at the
replication primary site is updated, the data does not need to be
updated synchronously at the mirroring site to finish
the update. In this way, performance is not reduced
due to data mirroring.
Air baffle It optimizes the ventilation channels and improves
the heat dissipation capability of the system.
B
Backup A collection of data stored on (usually removable)
non-volatile storage media for purposes of recovery
in case the original copy of data is lost or becomes
inaccessible; also called a backup copy. To be useful
for recovery, a backup must be made by copying the
source data image when it is in a consistent state.
The act of creating a backup.
Backup window An interval of time during which a set of data can be
backed up without seriously affecting applications
that use the data.
Bandwidth The numerical difference between the upper and
lower frequencies of a band of electromagnetic
radiation. A deprecated synonym for data transfer
capacity that is often incorrectly used to refer to
throughput.

OceanStor Dorado
Baud rate The maximum rate of signal state changes per

second on a communications circuit. If each signal
state change corresponds to a code bit, then the
baud rate and the bit rate are the same. It is also
possible for signal state changes to correspond to
more than one code bit, so the baud rate may be
lower than the code bit rate.
Bit error An incompatibility between a bit in a transmitted
digital signal and the corresponding bit in the
received digital signal.
Bit error rate The probability that a transmitted bit will be
erroneously received. The bit error rate (BER) is
measured by counting the number of bits in error at
the output of a receiver and dividing by the total
number of bits in the transmission. BER is typically
expressed as a negative power of 10.
Bonding Bonding of multiple independent physical network
ports into a logical port, which ensures the high
availability of server network connections and
improves network performance.
Boundary scan A test methodology that uses shift registers in the
output connections of integrated circuits (ICs). One IC
is often connected to the next IC. A data pattern is
passed through the chain and the observed returned
data stream affected by the circuit conditions gives
an indication of any faults present. The system is
defined under IEEE standard 1149.1 and is also
known as Joint Test Action Group (JTAG).
Browser/Server Architecture that defines the roles of the browser and
server. The browser is the service request party and
the server is the service provider.
Built-in FRU Alarm It indicates errors on the built-in FRUs of a controller,
indicator such as errors on fans or memory modules.
C
Cache hit ratio The ratio of the number of cache hits to the number
of all I/Os during a read task, usually expressed as a
percentage.
Captive screw Specially designed to lock into place on a parent
board or motherboard, allowing for easy installation
and removal of attached pieces without release of
the screw.

OceanStor Dorado
Challenge Handshake A password-based authentication protocol that uses a

Authentication challenge to verify that a user has access rights to a
Protocol system. A hash of the supplied password with the
challenge is sent for comparison so the cleartext
password is never sent over the connection.
Coffer A technology for ensuring data security and integrity
in a storage system. It is used to store the mission-
critical data of the system.
Coffer disk Disks that build up the coffer.
Compliance mode A protection mode of WORM. In compliance mode,
files within their protection period cannot be changed
or deleted by either the file user or by the system
administrator. Files with expired protection periods
can be deleted but not changed by the file user or
the system administrator.
Controller The control logic in a disk or tape that performs
command decoding and execution, host data transfer,
serialization and deserialization of data, error
detection and correction, and overall management of
device operations. The control logic in a storage
subsystem that performs command transformation
and routing, aggregation (RAID, mirroring, striping, or
other), high-level error recovery, and performance
optimization for multiple storage devices.
Controller enclosure An enclosure that accommodates controllers and
provides storage services. It is the core component of
a storage system and generally consists of
components, such as controllers, power supplies, and
fans.
Copying A pair state. The state indicates that the source LUN
data is being synchronized to the target LUN.
D
Data compression The process of encoding data to reduce its size. Lossy
compression (i.e., compression using a technique in
which a portion of the original information is lost) is
acceptable for some forms of data (e.g., digital
images) in some applications, but for most IT
applications, lossless compression (i.e., compression
using a technique that preserves the entire content of
the original data, and from which the original data
can be reconstructed exactly) is required.

OceanStor Dorado
Data flow A process that involves processing data extracted

from the source system. These processes include:
filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting
invalid data so that the processed data meets the
requirements of the destination system for the input
data.
Data migration A movement of data or information between
information systems, formats, or media. Migration is
performed for reasons such as possible decay of
storage media, obsolete hardware or software
(including obsolete data formats), changing
performance requirements, the need for cost
efficiencies etc.
Data source A system, database (database user; database
instance), or file that can make BOs persistent.
Deduplication The replacement of multiple copies of data — at
variable levels of granularity — with references to a
shared copy in order to save storage space and/or
bandwidth.
Dirty data Data that is stored temporarily on the cache and has
not been written onto disks.
Disaster recovery The recovery of data, access to data and associated
processing through a comprehensive process of
setting up a redundant site (equipment and work
space) with recovery of operational data to continue
business operations after a loss of use of all or part
of a data center. This involves not only an essential
set of data but also an essential set of all the
hardware and software to continue processing of that
data and business. Any disaster recovery may involve
some amount of down time.
Disk array A set of disks from one or more commonly accessible
disk subsystems, combined with a body of control
software. The control software presents the disks'
storage capacity to hosts as one or more virtual disks.
Control software is often called firmware or
microcode when it runs in a disk controller. Control
software that runs in a host computer is usually
called a volume manager.
Disk domain A disk domain consists of the same type or different
types of disks. Disk domains are isolated from each
other. Therefore, services carried by different disk
domains do not affect each other in terms of
performance and faults (if any).

OceanStor Dorado
Disk enclosure Consists of the following parts in redundancy:

expansion module, disk, power module, and fan
module. System capacity can be expanded by
cascading multiple disk enclosures.
Disk location The process of locating a disk in the storage system
by determining the enclosure ID and slot ID of the
disk.
Disk utilization The percentage of used capacity in the total available
capacity.
E
eDevLUN Logical storage array space created by a third-party
storage array.
Expansion module A component used for expansion.
Expansion Connects a storage system to more disk enclosures
through connection cables, expanding the capacity of
the storage system.
F
Field replaceable unit A unit or component of a system that is designed to
be replaced in the field, i.e., without returning the
system to a factory or repair depot. Field replaceable
units may either be customer-replaceable or their
replacement may require trained service personnel.
Firmware Low-level software for booting and operating an
intelligent device. Firmware generally resides in read-
only memory (ROM) on the device.
Flash Translation Layer Flash Translation Layer (FTL) organizes and manages
host data, enables host data to be allocated to NAND
flash chips of SSDs in an orderly manner, maintains
the mapping relationship between logical block
addresses (LBAs) and physical block addresses
(PBAs), and implements garbage collection, wear
leveling, and bad block management.
Front-end port The port that connects the controller enclosure to the
service side and transfers service data. There are
three types of front-end ports: SAS, Fibre Channel,
and iSCSI.
Front-end interconnect On a storage device, all controllers share the front-
I/O module (FIM) end interface modules.

OceanStor Dorado
Garbage collection The process of reclaiming resources that are no

longer in use. Garbage collection has uses in many
aspects of computing and storage. For example, in
flash storage, background garbage collection can
improve write performance by reducing the need to
perform whole block erasures prior to a write.
Gateway A device that receives data via one protocol and
transmits it via another.
Global garbage With a view to defragmentation of storage arrays
collection and garbage collection of disks, global garbage
collection reduces garbage of disks by enabling
storage arrays to inform disks of not implementing
invalid data relocation and of controlling space
release so that disks and controllers consume less
space, reducing costs and prolonging the useful life
of storage arrays.
Global system for The second-generation mobile networking standard
mobile defined by the European Telecommunications
communications Standards Institute (ETSI). It is aimed at designing a
standard for global mobile phone networks. GSM
consists of three main parts: mobile switching
subsystem (MSS), base station subsystem (BSS), and
mobile station (MS).
Global wear leveling With a view to individual characteristics of a single
disk, global wear leveling uses space allocation and
write algorithms to achieve wear leveling among
disks, preventing a disk from losing efficacy due to
excessive writes and prolonging the useful life of the
disk.
H
Hard disk tray The tray that bears the hard disk.
Heartbeat Heartbeat supports node communication, fault
diagnosis, and event triggering. Heartbeats are
protocols that require no acknowledgement. They are
transmitted between two devices. The device can
judge the validity status of the peer device.
Hit ratio The ratio of directly accessed I/Os from the cache to
all I/Os.
Hot swap The substitution of a replacement unit (RU) in a
system for a defective unit, where the substitution
can be performed while the system is performing its
normal functioning normally. Hot swaps are physical
operations typically performed by humans.

OceanStor Dorado
HyperMetro A value-added service of storage systems.

HyperMetro means two datasets (on two storage
systems) can provide storage services as one dataset
to achieve load balancing among applications and
failover without service interruption.
HyperMetro domain A HyperMetro configuration object generally; made
up of two storage arrays and one quorum server.
HyperMetro services can be created on a HyperMetro
domain.
HyperMetro vStore A HyperMetro vStore pair consists of two vStores,
pair that is, two tenants. After a HyperMetro relationship
is set up for a pair of vStores, the datasets in the two
vStores work in redundancy mode and provide
storage services in one dataset view, achieving hitless
service failover.
HyperMetro-Inner On an eight-controller network, with HyperMetro-
Inner, continuous mirroring, back-end global sharing,
and three-copy technologies, a storage system can
tolerate one-by-one failures of seven controllers
among eight controllers, concurrent failures of two
controllers, and failure of a controller enclosure.
Handle A handle resides on the structural part of a module. It
is used to insert or remove a module into or from a
chassis, not helpful in saving efforts.
I
In-band management The management control information of the network
and the carrier service information of the user
network are transferred through the same logical
channel. In-band management enables users to
manage storage arrays through commands.
Management commands are sent through service
channels, such as I/O write and read channels. The
advantages of in-band management include high
speed, stable transfer, and no additional
management network ports required.
Initiator The system component that originates an I/O
command over an I/O interconnect. The endpoint
that originates a SCSI I/O command sequence. I/O
adapters, network interface cards, and intelligent I/O
interconnect control ASICs are typical initiators.

OceanStor Dorado
I/O Shorthand for input/output. I/O is the process of

moving data between a computer system's main
memory and an external device or interface such as a
storage device, display, printer, or network connected
to other computer systems. This encompasses
reading, or moving data into a computer system's
memory, and writing, or moving data from a
computer system's memory to another location.
Interface module A replaceable field module that accommodates the
service or management ports.
L
Load balance A method of adjusting the system, application
components, and data to averagely distribute the
applied I/Os or computing requests to physical
resources of the system.
Logical unit The addressable entity within a SCSI target that
executes I/O commands.
Logical unit number The SCSI identifier of a logical unit within a target.
Industry shorthand, when phrased as "LUN", for the
logical unit indicated by the logical unit number.
LUN formatting The process of writing 0 bits in the data area of the
logical drive and generating related parity bits so that
the logical drive can be in the ready state.
LUN mapping A storage system maps LUNs to application servers
so that application servers can access storage
resources.
LUN migration A method for the LUN data to migrate between
different physical storage spaces while ensuring data
integrity and uninterrupted operation of host
services.
LUN snapshot A type of snapshot created for a LUN. This snapshot
is both readable and writable and is mainly used to
provide a snapshot LUN from point-in-time LUN
data.
Lever A lever resides on the structural part of a module. It
is used to insert or remove a module into or from a
chassis, saving efforts.
M
Maintenance terminal A computer connected through a serial port or
management network port. It maintains the storage
system.
Management interface The module that integrates one or more
module management network ports.

OceanStor Dorado
Management network An entity that provides means to transmit and

process network management information.
Management network The network port on the controller enclosure
port connected to the maintenance terminal. It is provided
for the remote maintenance terminal. Its IP address
can be modified with the change of the customer's
environment.
N
NVM Express A host controller interface with a register interface
and command set designed for PCI Express-based
SSDs.
NVMe SSD A solid state disk (SSD) with a non-volatile memory
express (NVMe) interface. Compared with other
SSDs, such SSDs can deliver higher performance and
shorter latency.
O
Out-of-band A management mode used during out-of-band
management networking. The management and control
information of the network and the bearer service
information of the user network are transmitted
through different logical channels.
P
Power failure When an external power failure occurs, the AC PEM
protection depends on the battery for power supply. This
ensures the integrity of the dirty data in the cache.
Pre-copy When the system monitors a failing member disk in a
RAID group, the system copies the data from the disk
to a hot spare disk in advance.
Palm-sized NVMe SSD A palm-sized NVMe SSD is a type of NVMe SSD of
which the dimensions (H x W x D) are 160 mm x 79.8
mm x 9.5 mm (neither 3.5-inch nor 2.5-inch).
Q
Quorum server A server that can provide arbitration services for
clusters or HyperMetro to prevent the resource access
conflicts of multiple application servers.
Quorum Server Mode A HyperMetro arbitration mode. When a HyperMetro
arbitration occurs, the quorum server decides which
site wins the arbitration.

OceanStor Dorado
RAID level The application of different redundancy types to a

logical drive. A RAID level improves the fault
tolerance or performance of the logical drive but
reduces the available capacity of the logical drive.
You must specify a RAID level for each logical drive.
Reconstruction The regeneration and writing onto one or more
replacement disks of all of the user data and check
data from a failed disk in a mirrored or RAID array. In
most arrays, a rebuild can occur while applications
are accessing data on the array's virtual disks.
Redundancy The inclusion of extra components of a given type in
a system (beyond those required by the system to
carry out its function) for the purpose of enabling
continued operation in the event of a component
failure.
Remote replication A core technology for disaster recovery and a
foundation that implements remote data
synchronization and disaster recovery. This
technology remotely maintains a set of data mirrors
through the remote data connection function of the
storage devices that are separated in different places.
Even when a disaster occurs, the data backup on the
remote storage device is not affected. Remote
replication can be divided into synchronous remote
replication and asynchronous remote replication.
Reverse The process of restoring data from the redundancy
synchronization machine (RM) when the services of the production
machine (PM) are recovering.
Route The path that network traffic takes from its source to
its destination. On a TCP/IP network, each IP packet
is routed independently. Routes can change
dynamically.
S
Script A parameterized list of primitive I/O interconnect
operations intended to be executed in sequence.
Often used with respect to ports, most of which are
able to execute scripts of I/O commands
autonomously (without policy processor assistance).
A sequence of instructions intended to be parsed and
carried out by a command line interpreter or other
scripting language. Perl, VBScript, JavaScript and Tcl
are all scripting languages.

OceanStor Dorado
Serial port An input/output location (channel) that sends and

receives data (one bit at a time) to and from the CPU
of a computer or a communications device. Serial
ports are used for serial data communication and as
interfaces for some peripheral devices, such as mouse
devices and printers.
Service data The user and/or network information required for the
normal functioning of services.
Service network port The network port that is used to store services.
Simple network An IETF protocol for monitoring and managing
management protocol systems and devices in a network. The data being
monitored and managed is defined by an MIB. The
functions supported by the protocol are the request
and retrieval of data, the setting or writing of data,
and traps that signal the occurrence of events.
Single point of failure One component or path in a system, the failure of
which would make the system inoperable.
Slot A position defined by an upper guide rail and the
corresponding lower guide rail in a frame. A slot
houses a board.
Small computer system A collection of ANSI standards and proposed
interface standards that define I/O interconnects primarily
intended for connecting storage subsystems or
devices to hosts through host bus adapters. Originally
intended primarily for use with small (desktop and
desk-side workstation) computers, SCSI has been
extended to serve most computing needs, and is
arguably the most widely implemented I/O
interconnect in use today.
Snapshot A point in time copy of a defined collection of data.
Clones and snapshots are full copies. Depending on
the system, snapshots may be of files, LUNs, file
systems, or any other type of container supported by
the system.
Snapshot copy A copy of a snapshot LUN.
Source LUN The LUN where the original data is located.
Static Priority Mode A HyperMetro arbitration mode. When a HyperMetro
arbitration occurs, the preferred site always wins the
arbitration.
Storage system An integrated system that consists of the following
parts: controller, storage array, host bus adapter,
physical connection between storage units, and all
control software.

OceanStor Dorado
Storage unit An abstract definition of backup storage media for

storing backup data. The storage unit is connected to
the actual storage media used to back up data.
Streaming media Streaming media is media continuously streamed
over the network. Combining technologies
concerning streaming media data collection,
compression, encoding, storage, transmission,
playback, and network communications, streaming
media can provide high-quality playback effects in
real time at low bandwidth.
Subnet A type of smaller network that forms a larger
network according to a rule, such as, forming a
network according to different districts. This
facilitates the management of a large network.
Smart disk enclosure Being compared with traditional disk enclosures, the
smart disk enclosures are equipped with Arm chips
and DDR memories or other computing modules to
achieve powerful computing capabilities. With such
capabilities, the smart disk enclosures can help
controllers to share some computing loads,
accelerating data processing.
T
Target The endpoint that receives a SCSI I/O command
sequence.
Target LUN The LUN on which target data resides.
Thin LUN A logic disk that can be accessed by hosts. It
dynamically allocates storage resources from the thin
pool according to the actual capacity requirements of
users.
Topology The logical layout of the components of a computer
system or network and their interconnections.
Topology deals with questions of what components
are directly connected to other components from the
standpoint of being able to communicate. It does not
deal with questions of physical location of
components or interconnecting cables. The
communication infrastructure that provides Fibre
Channel communication among a set of PN_Ports
(e.g., a Fabric, an Arbitrated Loop, or a combination
of the two).
Trim A method by which the host operating system may
inform a storage device of data blocks that are no
longer in use and can be reclaimed. Many storage
protocols support this functionality via various
names, e.g., ATA TRIM and SCSI UNMAP.

OceanStor Dorado
U
User interface The space where users interact with a machine.
U-shaped bracket It is an optional structural part like letter "U". It is
located between the mounting ear of a chassis and
the mounting bar of a cabinet or bay and is used to
adjust the locations of the chassis and mounting bar
of the cabinet or bay.
W
Wear leveling A set of algorithms utilized by a flash controller to
distribute writes and erases across the cells in a flash
device. Cells in flash devices have a limited ability to
survive write cycles. The purpose of wear leveling is
to delay cell wear out and prolong the useful life of
the overall flash device.
Write amplification Increase in the number of write operations by the
device beyond the number of write operations
requested by hosts.
Write amplification The ratio of the number of write operations on the
factor device to the number of write operations requested
by the host.
Write back A caching technology in which the completion of a
write request is signaled as soon as the data is in the
cache. Actual writing to non-volatile media occurs at
a later time. Write back includes inherent risks: an
application will take action predicated on the write
completion signal, and a system failure before the
data is written to non-volatile media will cause
media contents to be inconsistent with that
subsequent action. For these reasons, sufficient write
back implementations include mechanisms to
preserve cache contents across system failures
(including power failures) and a flushed cache at
system restart time.
Write Once Read Many A type of storage, designed for fixed content, that
preserves what is written to it in an immutable
fashion. Optical disks are an example of WORM
storage.
Write through A caching technology in which the completion of a
write request is not signaled until data is safely
stored on non-volatile media. Write performance
equipped with the write through technology is
approximately that of a non-cached system. However,
if the written data is also held in a cache, subsequent
read performance may be dramatically improved.

OceanStor Dorado
Zone A collection of Fibre Channel N_Ports and/or

NL_Ports (i.e., device ports) that are permitted to
communicate with each other via the fabric. Any two
N_Ports and/or NL_Ports that are not members of at
least one common zone are not permitted to
communicate via the fabric. Zone membership may
be specified by: 1) port location on a switch, (i.e.,
Domain_ID and port number); or, 2) the device's
N_Port_Name; or, 3) the device's address identifier;
or, 4) the device's Node_Name. Well-known
addresses are implicitly included in every zone.

OceanStor Dorado
SmartVirtualization Feature Guide C Acronyms and Abbreviations
C Acronyms and Abbreviations
C
CHAP Challenge Handshake Authentication Protocol
F
FC Fiber Channel
I
IP Internet Protocol
IQN iSCSI Qualified Name
iSCSI Internet Small Computer Systems Interface
L
LUN Logical Unit Number
O
OCR Oracle Cluster Registry
OEM Original Equipment Manufacturer
R
RAID Redundant Array of Independent Disks
S
SAS Serial Attached SCSI
SSD Solid-State Drive
W
WWN World Wide Name

OceanStor Dorado
SmartVirtualization Feature Guide C Acronyms and Abbreviations
WWPN World Wide Port Name

OceanStor Dorado 6.0.0 SmartVirtualization Feature Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OceanStor Dorado 6.0.0 SmartVirtualization Feature Guide

Uploaded by

Copyright:

Available Formats

OceanStor Dorado

SmartVirtualization Feature Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. i

About This Document

The following table lists the product models supporting SmartVirtualization.

Product Series Product Model

OceanStor Dorado V6 series Dorado 3000 V6

● Technical support engineers

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

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a hazard with a medium level of risk

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

Indicates a potentially hazardous situation which, if

Supplements the important information in the main

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. iii

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. iv

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

2 Selecting a Takeover Mode................................................................................................. 12

4 Taking Over Third-Party Heterogeneous Storage Systems in Offline Mode.......... 28

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. v

4.4.2 Scanning for External LUNs........................................................................................................................................... 34

5 Taking Over Huawei Heterogeneous Storage Systems in Online Mode..................38

6 Taking Over Third-Party Heterogeneous Storage Systems in Online Mode...........73

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. vi

6.6.1.1.2 Checking and Recording the ALUA Policy of External LUNs....................................................................... 90

7 Configuring Data Migration............................................................................................. 107

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. vii

10.1.6 Automatically Scanning for LUNs........................................................................................................................... 150

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. viii

13 Configuration Restrictions.............................................................................................. 186

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. ix

13.20 HP EVA Series..................................................................................................................................................................215

A How to Obtain Help...........................................................................................................223

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. x

The SmartVirtualization feature enables Huawei OceanStor Dorado V6 series to

● If a user wants to buy a new storage system to replace an existing storage

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. 1

Using SmartVirtualization can address the previous issues. Physical attributes of

SmartVirtualization allows you to manage storage resources on heterogeneous storage

SmartVirtualization has the following advantages:

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. 2

Table 1-1 Benefits

Resolving the incompatibility issues SmartVirtualization resolves the

Integrating storage space and After using SmartVirtualization, you

1.2 License Requirements and Compatible Products

OceanStor Dorado V6 Dorado 3000 V6 6.0.0

Dorado 6000 V6 6.0.0

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. 3

Product Series Model Version

Dorado 8000 V6 6.0.0

Dorado 18000 V6 6.0.0

1.3 Working Principle

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. 4

are interrupted temporarily. This mode is applicable to all compatible Huawei

Relationship Between an eDevLUN and an External LUN

Figure 1-1 Relationship between an eDevLUN and an external LUN

Local storage Heterogeneous

Issue 07 (2021-06-25) Copyright © Huawei Technologies Co., Ltd. 5

Data Read and Write Processes

Figure 1-2 Data read process

Data read request