HP StorageWorks XP12000, StorageWorks XP10000, StorageWorks SVS200 External Storage XP user guide

HP StorageWorks External Storage XP user guide

XP12000

XP10000

SVS200

Part number: T1706-96005 Fifth edition: June 2006

Legal and notice information

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

z/OS is registered trademarks or trademarks of International Business Machines Corporation.

Microsoft, Windows, and Windows NT are registered trademarks or trademarks of Microsoft Corporation.

Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the U.S. and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

Solaris is a product name of Sun Microsystems, Inc.

External Storage XP user guide

Contents

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1 Overview of connecting external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

External Storage XP features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Preparing for External Storage XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Storage arrays that can be connected as external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

External Storage XP requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installing External Storage XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Preparing for External Storage XP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

External ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

External LU to be mapped. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

External LU groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

External LU attributes set by mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Example of an alternate path configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Examples of switching I/O execution paths to alternate paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Powering arrays on or off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Powering local arrays on or off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

To power local arrays off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

To power local arrays on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Powering external arrays on or off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

To power external arrays off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

To power external arrays on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using mapped external LUs from the host connected to the local array . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Writing new data to mapped external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using existing data in mapped external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Uninstalling External Storage XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Limitations on External Storage XP operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Combining External Storage XP with other HP StorageWorks products . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using external LUs for Auto LUN XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Using external LUs for Continuous Access XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using external LUs for Continuous Access XP Journal operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Using external LUs for Business Copy XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3 Managing cache with external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Guidelines for using cache with external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Determining, setting, or changing the external LU cache mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Determining if the cache mode is disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Changing the cache mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Collecting device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Deleting and remapping the external LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Partitioning cache for external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

For example, Company A uses: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

External Storage XP user guide 3

In another example, Company B uses the following storage tiers: . . . . . . . . . . . . . . . . . . . . . . 47

To partition cache for external storage:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Determining the number and size of needed partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Creating Cache partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Changing storage system modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4 External Storage XP panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

LU Operation pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Device tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Device list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

WWN tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

WWN list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Port tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Port list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Filter button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Preset list (LU Operation pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Port Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Port Operation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Port Operation list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Preset list (Port Operation pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5 Configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Overview of configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Setting an external array’s port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Setting a local array’s port attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Mapping external LUs (Add LU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Mapping external LUs individually (Add LU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Select Paths pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Mapping multiple external LUs at one time (Add LU (Auto)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Select LDEV window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Displaying detailed information stored in VMA (VMA information). . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Setting alternate paths for external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Defining alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Changing a defined alternate path priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Canceling alternate path definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Changing alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Adding alternate paths by selecting multiple external LUs (Add Paths) . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Deleting alternate paths by selecting multiple external LUs (Delete Paths) . . . . . . . . . . . . . . . . . . . . . . . . . 90

Checking an external LU’s status (LDEV Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Obtaining information about external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Restoring external LUs (Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Displaying configuration information for external LUs (Volume Detail). . . . . . . . . . . . . . . . . . . . . . . . . 94

Disconnecting external arrays or LUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Disconnecting all external LUs in an external array (Disconnect Subsystem). . . . . . . . . . . . . . . . . . . . . 96

Disconnecting external LUs individually (Disconnect Volume) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.) . . . . . . . 97

Restoring all external LUs in an external array (Check Paths & Restore Vol.) . . . . . . . . . . . . . . . . . . . . 97

Restoring external LUs individually (Check Paths & Restore Vol.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Restoring external LUs (LDEV Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Restoring volumes in an external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Restoring volumes in a mapped external LU individually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Stopping the use of paths to an external LU by specifying an external array’s WWN (Disconnect Paths) . . . 99

Restoring paths to an external LU by specifying an external array’s WWN (Check Paths) . . . . . . . . . . . . . 99

Changing an external array’s port setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Stopping the use of paths to an external LU by specifying a local array’s port (Disconnect Paths) . . . . . . . 101

Restoring paths to an external LU by specifying a local array’s port (Check Paths) . . . . . . . . . . . . . . . . . 101

Deleting external LU mappings (Delete LU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

6 Remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Overview of remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Notices about remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Mapping command devices as remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7 Troubleshooting External Storage XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

A Notes on connecting external arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Connecting Thunder 9500V subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

System parameters for connecting Thunder 9500V subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Relationship between serial numbers in the Device list on the LU Operation pane and Thunder

9500V subsystem models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Relationship between the WWN of the port on the Thunder 9500V subsystem and the controller . . . . 115

Path status and examples of recovery procedures (Thunder 9500V subsystems) . . . . . . . . . . . . . . . . . 116

Connecting TagmaStore AMS and TagmaStore WMS subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems . . . . . . . . . . 117

Relationship between serial numbers in the Device list on the LU Operation pane and TagmaStore

AMS and TagmaStore WMS subsystem models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Relationship between the WWN of the port on the TagmaStore AMS or TagmaStore WMS

subsystem and the controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS

subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Connecting XP12000/XP10000 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) . . . . . . . . . . . . . 120

Connecting XP1024/XP128 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) . . . . . . . . . . . . . . . . 121

Connecting XP512/XP48 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Path status and examples of recovery procedures (XP512/XP48 Disk Arrays) . . . . . . . . . . . . . . . . . . 122

Connecting HP 200 Storage Virtualization System as external storage . . . . . . . . . . . . . . . . . . . . . . . . . 123

Path status and examples of recovery procedures (SVS200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Connecting EVA arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Identifying logical volumes of EVA arrays (using Characteristic 2) . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Alternate path’s behavior when an EVA array is connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

B Required volume capacity for emulation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

C Adjusting volume capacity for copy pair setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Copying data from external arrays (using external LUs as P-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Copying data to external arrays (setting external LUs as S-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

D Using an XP12000/XP10000/SVS200 with an EVA3000/5000 external storage . . . . 133

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Physical array connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Minimum physical configuration for HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Expanded configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Creating new EVA host objects for the XP12000/XP10000/SVS200 . . . . . . . . . . . . . . . . . . . . . . . 134

Creating and presenting EVA Vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Defining XP12000/XP10000/SVS200 external ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Defining XP12000/XP10000/SVS200 external storage LDEVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Performance considerations for using EVAs as external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Defining alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

E Configuring MSA1000/1500 as external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Configuring external array LUs, host mode, and ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Connecting MSA1000/1500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Setting up the MSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Defining MSA array objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Calculating MSA LU size and defining LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Selective Storage Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

External Storage XP user guide 5

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Figures

1 External Storage XP concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Example of alternate path configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 Example of alternate path configuration using two switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 Example of incorrect alternate path configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Alternate path mode is Multi mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6 Alternate path mode is Single mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7 Alternate path mode is Single mode with alternate paths in Normal and Standby . . . . . . . . . . . . . . . 26

8 Alternate path mode is Single mode with alternate paths in Standby only . . . . . . . . . . . . . . . . . . . . . 27

9 Writing new data to mapped external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

10 Using existing data in mapped external LUs (without formatting) . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

11 Example of external LU with 2 TB or less. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

12 External LU capacity is larger than the specified emulation type’s basic capacity (OPEN-3 example) . . 33

13 External LU capacity is smaller than the specified emulation type’s basic capacity . . . . . . . . . . . . . . . 33

14 Example of Auto LUN XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

15 Example of Continuous Access XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

16 Example of Continuous Access XP Journal operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

17 Example of Business Copy operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

18 LU Operation pane, Cache Mode setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

19 LU Operation pane, LU number and UUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

20 LU Operation pane, Path Setting option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

21 Path Setting pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

22 LDEV Information pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

23 Partition Definition pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

24 Partition Definition pane, Cut option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

25 Partition Definition pane, Paste Parity Group option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

26 Panes for External Storage XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

27 LU Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

28 Device tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

29 Device list (external device selected in Device tree) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

30 WWN tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

31 WWN list (External Devices selected in the WWN tree). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

32 Port tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

33 Port list (External selected in Port tree). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

34 Filter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

35 Preset Detail window (mapping operation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

36 Port Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

37 Port Operation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

38 Port Operation list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

39 Preset Detail window (changing port attribute). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

40 Overview of configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

41 Add LU window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

42 Select Paths pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

43 Add LU pane (mapping using the Linear button) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

44 Add LU pane (mapping with the Linear button released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

45 SSID window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

46 Set SSID window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

47 Auto Map Setting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

48 Select LDEV window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

49 VMA Information pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

50 Path Setting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

51 Path Setting window, shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

52 Add Paths window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

53 Delete Paths window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

54 LDEV Information window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

55 Shortcut menu of the LDEV Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

56 Volume Detail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

. . . 92

57 Disconnect Subsystem and Check Paths & Restore Vol. Commands . . . . . . . . . . . . . . . . . . . . . . . . . 96

58 Change Parameter pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

59 Overview of remote command device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

60 Configuration example for which logical volumes can only be identified by characteristic. . . . . . . . . 125

61 LDEV capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

62 Calculating LU capacity (OPEN-3 example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

63 Copying data from external arrays (using external LUs as P-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . 131

64 Copying data to external arrays (setting external LUs as S-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . . 132

65 XP12000/XP10000/SVS200-EVA minimum connections for HA. . . . . . . . . . . . . . . . . . . . . . . . . . 133

66 XP12000/XP10000/SVS200-EVA connections for expanded performance . . . . . . . . . . . . . . . . . . 134

67 Creating EVA host objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

68 Adding ports to XP12000/XP10000/SVS200 host objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

69 Selecting Vdisk’s Preferred path/mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

70 Presenting Vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

71 Defining XP12000/XP10000/SVS200 external ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

72 Selecting EVA LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

73 XP External LDEV definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

74 Configuring alternate paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

75 Example: Connecting an MSA array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

76 Defining MSA array objects with the ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

77 Defining MSA LUs with ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

78 Configuring SSP with ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Storage arrays that can be connected as external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 External Storage XP requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 When external LU’s emulation type is OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5 When external LU’s emulation type is for mainframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6 Recommended individual CLPR cache size for external storage on open systems . . . . . . . . . . . . . . . . . 48

7 Recommended individual CLPR cache size for external storage on HP storage virtualization systems . . . 48

8 External array status values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

9 Mapped external LU status values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

10 Information displayed in the Device column for remote command devices . . . . . . . . . . . . . . . . . . . . . 104

11 Restrictions on remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

12 General External Storage XP troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

13 System parameter settings (Thunder 9500V subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

14 Relationship between serial numbers and subsystem models (Thunder 9500V subsystems) . . . . . . . . . 115

15 Relationship between ports’ WWNs and controllers (Thunder 9500V subsystems) . . . . . . . . . . . . . . . 115

16 Path status and examples of recovery procedures (Thunder 9500V subsystems) . . . . . . . . . . . . . . . . . 116

17 System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems) . . . . . . . . . . . . . . . 117

18 Relationship between serial numbers and subsystem models (TagmaStore AMS and TagmaStore

WMS subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

19 Relationship between ports’ WWNs and controllers (TagmaStore AMS and TagmaStore WMS

subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

20 Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS

subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

21 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) . . . . . . . . . . . . . 120

22 Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) . . . . . . . . . . . . . . . . 121

23 Path status and examples of recovery procedures (XP512/XP48 Disk Arrays) . . . . . . . . . . . . . . . . . . 122

24 Path status and examples of recovery procedures (SVS200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

25 External LU’s maximum usable capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

26 LDEV capacity information for each emulation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

27 Volume capacity information for each emulation type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

External Storage XP user guide 7

About this guide

This guide provides information about:

• Preparing for External Storage XP operations

• Performing External Storage XP operations

• Troubleshooting External Storage XP

• Connecting external arrays

• Using an XP12000/XP10000/SVS200 with EVA3000/50000

• Configuring MSA1000/1500 Disk Arrays as external arrays

Supported storage platforms and firmware

In this guide, the term array refers to the following storage platforms:

• HP StorageWorks XP12000 Disk Array

• HP StorageWorks XP10000 Disk Array

• HP StorageWorks 200 Storage Virtualization System

For information about required firmware versions, see the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.

Intended audience

This guide is intended for customers and HP-authorized service providers with knowledge of:

• Disk array hardware and software

• Data processing and RAID storage subsystems and their basic functions

Prerequisites

Prerequisites for using this product include:

• Installing the HP StorageWorks disk array(s)

• Installing the license key for this product

Related documentation

The following documents provide related information:

• HP StorageWorks XP glossary

• HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200

• HP StorageWorks Auto LUN XP user guide for the XP12000/XP10000/SVS200

• HP StorageWorks Business Copy XP user guide for the XP12000/XP10000/SVS200

• HP StorageWorks Cache LUN XP user guide for XP12000/XP10000/SVS200

• HP StorageWorks Continuous Access XP Journal user guide

• HP StorageWorks Continuous Access XP user guide for the XP12000/XP10000/SVS200

• HP StorageWorks Flex Copy XP user guide

• HP StorageWorks LUN Configuration and Security Manager XP user guide for the

XP12000/XP10000/SVS200

• HP Array Configuration Utility User Guide (for HP StorageWorks Modular Smart Arrays)

You can find the above documents from the Manuals page of the HP Business Support Center web site:

ttp://www.hp.com/support/manuals. In the Storage section, click Storage array systems, and then

select your product.

For the HP StorageWorks 1000 or 1500 Modular Smart Array quickspecs, select your product from the Storage Array Systems page: http://h18006.www1.hp.com/storage/arraysystems.html

External Storage XP user guide 9

Document conventions and symbols

Table 1 Document conventions

Convention Element

Blue text: Table 1 Cross-reference links and e-mail addresses

Blue, underlined text: (http://www.hp.com) Web site addresses

Bold text • Keys that are pressed

Italic text Text emphasis

Monospace text • File and directory names

Monospace, italic text • Code variables

Monospace, bold text Emphasized monospace text

• Text typed into a GUI element, such as a box

• GUI elements that are clicked or selected, such as

menu and list items, buttons, and check boxes

• System output

• Code

• Commands, their arguments, and argument values

• Command variables

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

HP technical support

Telephone numbers for worldwide technical support are listed on the HP support web site:

http://www.hp.com/support/

Collect the following information before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Error messages

• Operating system type and revision level

• Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

Subscription service

HP recommends that you register your product at the Subscriber’s Choice for Business web site:

http://www.hp.com/go/e-updates

After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.

HP web sites

For additional information, see the following HP web sites:

• http://www.hp.com

• http://www.hp.com/go/storage

• http://www.hp.com/service_locator

• http://www.hp.com/support/manuals

• http://www.hp.com/support/downloads

• http://www.hp.com/support/rwc/manuals

Documentation feedback

HP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message to

storagedocs.feedback@hp.com. All submissions become the property of HP.

External Storage XP user guide 11

1 Overview of connecting external arrays

External Storage XP realizes the virtualization of storage arrays. You can use External Storage XP to access multiple storage arrays connected by a Fibre Channel interface as if they were all one storage array. Once you connect another storage array to an XP array or storage virtualization system using External Storage XP, you can also use Command View XP or XP Remote Web Console to manage the data space (but not necessarily the management) of the other storage arrays.

External Storage XP supports external storage LDEVs of any standard XP emulation type, such as OPEN-3, OPEN-8, OPEN-9, OPEN-L, OPEN-K, OPEN-V, 3390-3, or 3390-0.

NOTE: Currently only the HP StorageWorks XP12000 and XP10000 Disk Arrays and the

HP StorageWorks 200 Storage Virtualization System (SVS200) support external storage.

In this user guide, the original XP12000/XP10000/SVS200 is called the local array and the connected storage array is called the external array. The volume managed in the local array is called an internal storage virtualizer LDEV (or internal LDEV), and the volume in an external array is called an external LU.

IMPORTANT: This guide contains information about internal disks or LDEVs. Unlike the

XP12000/XP10000 Disk Arrays, the SVS200 has no internal disks. Therefore, information about internal disks or LDEVs does not apply to the SVS200.

With the help of host mirroring middleware, Auto LUN XP or HP StorageWorks XP Tiered Storage Manager, you can use External Storage XP for online or offline data migration, providing a point-in-time copy of data between an external device and the local array.

Flex Copy XP is another HP StorageWorks product that copies user data between an LU on a local array and an LU on an external storage device. For a detailed description of Flex Copy XP, see the HP StorageWorks Flex Copy XP user guide.

External Storage XP features

The following are External Storage XP features:

• Using External Storage XP to map an external LU as an internal LDEV, you can manage the external LU

capacity using Command View XP or XP Remote Web Console as if it were a volume in the local array.

Mapping means assigning Virtual Devices (VDEVs) and, consequently, Logical Devices (LDEVs) and host port LUs to external LUs. If you map external LUs as internal VDEVs, you can use Command View XP or XP Remote Web Console to then assign the VDEV to an internal CU:LDEV and a port/LU address. This allows you to use an external LU as if it were an LDEV in the local array.

NOTE: The phrases mapped as an internal LU and mapped as an internal LDEV should be

interpreted to mean that the external LU is specifically mapped into the local array as a unique VDEV (Virtual Device), which is then associated with a local array CU:LDEV (Control Unit:Logical Device), which is then typically associated with a unique host port/LU combination. Since a local array LU number is only unique within the name space of a host port (for example, CL1-A), references to “XP LU” should be interpreted as references to either the unique port/LUN combination or the unique CU:LDEV combination.

• If you use Flex Copy XP with External Storage XP, you can copy data in the external array to the local

array and copy data in the local array to the external array. For more information about Flex Copy XP, see the HP StorageWorks Flex Copy XP user guide.

External Storage XP user guide 13

Figure 1 illustrates a local array and an external array that are connected using External Storage XP and

Fibre Channel hardware. In Figure 1, the external array is connected to the external port of the local array via a switch (or hub) using a Fibre Channel interface. External is a local array port attribute used for External Storage XP. In Figure 1, external LUs are mapped as local array VDEVs and LDEVs and, consequently, as an LU.

NOTE: Do not access any external storage volume that is mapped as an External Storage XP volume

from a host connected directly to the external array. Also, do not access an External Storage XP mapped external array volume using the external array’s functions (for example, local replication). After mapping an external LU as a local array volume, access the mapped external LU only from the local array.

NOTE: Except on the MSA, a host can directly access external array volumes that have not been

mapped as local array volumes.

Figure 1 External Storage XP concept

14 Overview of connecting external arrays

2 Preparing for External Storage XP operations

This chapter describes requirements, preparations, and notes for External Storage XP. This chapter also describes the HP StorageWorks products you can use with External Storage XP.

System requirements

External Storage XP operations involve the local array, a storage array used as an external array, and the licensed External Storage XP feature enabled on Command View XP or XP Remote Web Console. System requirements for External Storage XP are:

• Local array (first array)

Install and enable all hardware and microcode required for External Storage XP operations in the local array.

CAUTION: Before installing and enabling the hardware and microcode, see ”Managing cache

with external storage” on page 43 for instructions.

NOTE: Currently only an XP12000/XP10000/SVS200 can be used as a local array.

• External array (second array)

You also need a second storage device, called an external array in this user guide. For more information, see ”Storage arrays that can be connected as external arrays” on page 15.

• HP StorageWorks Command View XP (running on a user-supplied Windows®-based PC) or XP Remote

Web Console For instructions on installing and using Command View XP or XP Remote Web Console, see the

HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.

NOTE: You must run Command View XP or XP Remote Web Console in Modify mode to perform

External Storage XP operations. In View mode, you can only view External Storage XP information.

• External Storage XP

Enable the licensed External Storage XP feature in Command View XP or XP Remote Web Console.

Storage arrays that can be connected as external arrays

Table 2 lists storage arrays that can be connected as external arrays. Notes about the appearance of each

storage array in this document and in External Storage XP panes are also listed.

Table 2 Storage arrays that can be connected as external arrays

Storage array Notes

HP StorageWorks XP12000 Disk Array • In External Storage XP panes, the array appears as

“12000”.

• Alternate paths are in Multi mode (meaning that

dynamic load balancing across multiple active paths is enabled).

HP StorageWorks XP10000 Disk Array • In External Storage XP panes, the array appears as

“10000”.

• Alternate paths are in Multi mode.

External Storage XP user guide 15

Table 2 Storage arrays that can be connected as external arrays (continued)

Storage array Notes

HP StorageWorks XP1024/XP128 Disk Array • In External Storage XP panes, the arrays appear as

“1024” and “128”, respectively.

• Alternate paths are in Multi mode.

HP StorageWorks XP512/XP48 Disk Array • In External Storage XP panes, the arrays appear as

“512” and “48”, respectively.

• Alternate paths are in Multi mode.

HP StorageWorks XP256 Disk Array • In External Storage XP panes, the array appears as

“256”.

• Alternate paths are in Multi mode.

HP StorageWorks 200 Storage Virtualization System • In External Storage XP panes, the array appears as

“SVS200”.

• Alternate paths are in Multi mode.

HP StorageWorks 3000/5000 Enterprise Virtual Array (Active/Standby and Active/Active controllers) or HP StorageWorks 4000/6000/8000 Enterprise Virtual Array (Active/Active controllers)

HP StorageWorks MSA1000/1500 (Active-Standby) • In this user guide, the arrays appear as “MSA

TagmaStore™ Universal Storage Platform subsystem • In this user guide, the array appears as

TagmaStore™ Network Storage Controller subsystem • In this user guide, the array appears as

TagmaStore™ Adaptable Modular Storage subsystem • In this user guide, the array appears as

• In this user guide, the arrays appear as “EVA

array”.

• In External Storage XP panes, the arrays appear as

“EVA”.

• Alternate paths are in Single mode (meaning that

dynamic load balancing across multiple active paths is not enabled).

array”.

• In External Storage XP panes, the arrays appear as

“MSA”.

• Alternate paths are in Single mode.

“TagmaStore™ USP subsystem”.

• In External Storage XP panes, the array appears as

“USP”.

• Alternate paths are in Multi mode.

“TagmaStore™ NSC subsystem”.

• In External Storage XP panes, the array appears as

“NSC”.

• Alternate paths are in Multi mode.

“TagmaStore™ AMS subsystem”.

• In External Storage XP panes, the array appears as

“AMS”.

• Alternate paths are in Single mode.

TagmaStore™ Workgroup Modular Storage subsystem • In this user guide, the array appears as

16 Preparing for External Storage XP operations

“TagmaStore™ WMS subsystem”.

• In External Storage XP panes, the array appears as

“NSC”.

• Alternate paths are in Single mode.

Table 2 Storage arrays that can be connected as external arrays (continued)

Storage array Notes

Lightning 9900V series subsystem • “Lightning 99xxV series subsystem” indicates the

Lightning 9970V and Lightning 9980V.

• In this user guide, the arrays appear as “Lightning

9900V subsystem”.

• In External Storage XP panes, the arrays appear as

“9970V” and “9980V”, respectively.

• Alternate paths are in Multi mode.

Thunder 9500V series subsystem • “Thunder 95xxV series subsystem” indicates the

Thunder 9530V, Thunder 9570V, and Thunder 9580V.

• In this user guide, the arrays appear as “Thunder

9500V subsystem”.

• In External Storage XP panes, the arrays appear as

“9500V”.

• Alternate paths are in Single mode.

Lightning 9900C series subsystem • “Lightning 99xxC series subsystem” indicates the

Lightning 9910 and Lightning 9960.

• In this user guide, the arrays appear as “Lightning

9900 subsystem”.

• In External Storage XP panes, the Lightning 9910

appears as “0401”, and the Lightning 9960 appears as “0400”.

• Alternate paths are in Multi mode.

A/H-6593 subsystem • In External Storage XP panes, the array appears as

“300”.

• Alternate paths are in Multi mode.

SANRISE Universal Storage Platform subsystem • In this user guide, the array appears as “SANRISE

USP subsystem”.

• In External Storage XP panes, the array appears as

“USP”.

• Alternate paths are in Multi mode.

SANRISE Network Storage Controller subsystem • In this user guide, the array appears as “SANRISE

NSC subsystem”.

• In External Storage XP panes, the array appears as

“NSC”.

• Alternate paths are in Multi mode.

SANRISE Adaptable Modular Storage subsystem • In this user guide, the array appears as “SANRISE

AMS subsystem”.

• In External Storage XP panes, the array appears as

“AMS”.

• Alternate paths are in Single mode.

SANRISE Workgroup Modular Storage • In this user guide, the array appears as “SANRISE

WMS subsystem”.

• In External Storage XP panes, the array appears as

“WMS”.

• Alternate paths are in Single mode.

External Storage XP user guide 17

Table 2 Storage arrays that can be connected as external arrays (continued)

Storage array Notes

SANRISE9900V series subsystem • “SANRISE99xxV series subsystem” indicates the

SANRISE9970V and SANRISE9980V.

• In this user guide, the arrays appear as

“SANRISE9900V subsystem”.

• In External Storage XP panes, the arrays appear as

“9970V” and “9980V”, respectively.

• Alternate paths are in Multi mode.

SANRISE9500V series subsystem • “SANRISE95xxV series subsystem” indicates the

SANRISE9530V, SANRISE9570V, and SANRISE9580V.

• In this user guide, the arrays appear as

“SANRISE9500V subsystem”.

• In External Storage XP panes, the arrays appear as

“9500V”.

• Alternate paths are in Single mode.

SANRISE2000 series subsystem • “SANRISE2000 series subsystem” indicates the

SANRISE2200 and SANRISE2800.

• In this user guide, the arrays appear as

“SANRISE2000 subsystem”.

• In External Storage XP panes, the SANRISE2200

appears as “0401”, and the SANRISE2800 appears as “0400”.

• Alternate paths are in Multi mode.

SANRISE H12000 subsystem • In External Storage XP panes, the array appears as

“12000”.

• Alternate paths are in Multi mode.

SANRISE H10000 subsystem • In External Storage XP panes, the array appears as

“10000”.

• Alternate paths are in Multi mode.

SANRISE H1024/H128 subsystem • In External Storage XP panes, the arrays appear as

“1024” and “128”, respectively.

• Alternate paths are in Multi mode.

SANRISE H512/H48 subsystem • In External Storage XP panes, the arrays appear as

“512” and “48”, respectively.

• Alternate paths are in Multi mode.

SANRISE H256 subsystem • In External Storage XP panes, the array appears as

“256”.

• Alternate paths are in Multi mode.

IBM Storage Subsystem For specific supported storage arrays, contact your

HP account support representative.

EMC Storage Subsystem For specific supported storage arrays, contact your

HP account support representative.

Fujitsu Storage Subsystem For specific supported storage arrays, contact your

HP account support representative.

NEC Storage Subsystem For specific supported storage arrays, contact your

18 Preparing for External Storage XP operations

HP account support representative.

CAUTION: For more information about alternate path modes, see ”Setting alternate paths for external

LUs” on page 84.

Contact your HP account support representative for the latest external array and FC switch support matrix.

External Storage XP requirements

Table 3 External Storage XP requirements

Item Requirement

Required products

Maximum number of external LUs addressable per local array port

Maximum number of external LUs that can be connected

Maximum number of FC paths that can exist to one external LU

• HPStorageWorks Command View XP version 2.0 or later, or

XP Remote Web Console

• HP StorageWorks LUN Configuration and Security Manager

XP (for

setup)

• HP StorageWorks RAID Manager XP version 01.12.06 or later

(if Business Copy XP is used)

1,024 per port

• For the XP12000, 15,360 volumes can be connected

• For the XP10000/SVS200, 8,192 volumes can be connected

• 1,024 volumes can be connected per port

NOTE: If you use Snapshot XP, the number of external LUs that can

be connected is as follows:

• For the XP12000:

Number of external LUs + Number of virtual LUs ≤15,360

• For the XP10000/SVS200:

Number of external LUs + Number of virtual LUs ≤8,192

Maximum capacity of an external LU 2 TB (4,294,967,296 blocks) per external LU (OPEN-V)

If you specify an external LU that is larger than 2 TB, you can only access data stored in the field up to 2 TB.

Minimum capacity of an external LU About 38 MB (77,760 blocks) per external LU (non-OPEN-V)

When the volume’s emulation type is OPEN-V, minimum capacity is about 47 MB (96,000 blocks) per external LU.

Installing External Storage XP

To perform External Storage XP operations with Command View XP or XP Remote Web Console, you must install an External Storage XP license key.

1. Start Command View XP or XP Remote Web Console for the local array.

2. Enable the External Storage XP options in Command View XP or XP Remote Web Console and on

each External Storage XP array.

For instructions, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.

Preparing for External Storage XP settings

Before using External Storage XP, collect the information necessary for defining its settings. The following information is required:

External Storage XP user guide 19

• Ports that can be set to external ports (see ”External ports” on page 20)

• External array and LUs to map to the internal LDEVs (see”External LU to be mapped” on page 20)

• Configuration of external LU groups (see ”External LU groups” on page 20)

• Configuration of external LU attributes (see ”External LU attributes set by mapping” on page 20)

• Configuration of alternate paths (see ”Alternate paths” on page 22)

External ports

Local array ports used for External Storage XP must be set to a designation of External. When the external array is connected to the local array’s external port via Fibre Channel, you can view information about the external array from Command View XP or XP Remote Web Console. The external array can be connected only to ports designated as External.

To set the port attribute to External, you must release any existing paths currently configured for the port. You cannot change the attribute of the port where paths are set to External. Before starting External Storage XP operations, you must know which ports you can change to External.

NOTE: You cannot use ports with attributes set for remote copy software (such as RCU Target or Initiator)

or other features as external ports for External Storage XP. If the port attribute is set to something other than External, change its attribute to External. Flex Copy XP and External Storage XP can share an XP12000/XP10000/SVS200 port with an attribute of External.

For instructions, see ”Setting a local array’s port attributes” on page 70.

External LU to be mapped

When connecting an external array to an external port, you can map LUs in the external array (external LUs) as LDEVs in the local array (internal LDEVs). Verify which LUs in which external array can be mapped as internal LDEVs.

You can map only one external LU to a given internal LDEV and map up to a theoretical limit of 1,024 external LUs per local array port.

An external LU’s maximum available capacity depends on the emulation type set when the LU is mapped. You cannot access data stored in the field over the external LU’s maximum available capacity. To set an emulation type other than OPEN-V, you cannot map external LUs smaller than 38 MB (77,760 blocks). To set the OPEN-V emulation type, you cannot map external LUs of smaller than 47 MB (96,000 blocks). For more information about the capacity of the external LU for each emulation type, see ”Required volume

capacity for emulation types” on page 127.

External LU groups

When mapping an external LU as an internal LDEV, you must register the external LU in an external LU group.

You can classify external LUs set by External Storage XP into groups according to their use. The group is called an external LU group (ExG). For instance, you can register several LUs in one external array to one external LU group. Or, if data you want to manage in a chunk is stored in LUs in various external arrays, you can register those LUs in one external LU group, and manage them as a block.

You must assign a number from 1 to 16,384 to each external LU group. For the XP12000, you can create a maximum of 15,360 external LU groups. For the XP10000/SVS200, you can create a maximum of 8,192 external LU groups. You can register a maximum of 256 volumes in one external group.

External LU attributes set by mapping

When mapping an external LU as an internal LDEV, use the Add LU pane in External Storage XP to set the external LU’s attributes. For instructions, see ”Mapping external LUs (Add LU)” on page 70.

The following are the external LU’s attributes:

• Emulation type

20 Preparing for External Storage XP operations

Set the mapped LU’s emulation type by selecting any emulation type from the drop-down list. However, if you plan to use the mapped LU for Flex Copy XP operations, or you plan to access existing data in the external LU, you must select the OPEN-V emulation type to avoid data resizing.

If you plan to use existing data in the external LU from the local array after mapping, you must select the OPEN-V emulation type. For example, to migrate existing data in the external LU to the local array volume, you must set the OPEN-V emulation type when mapping the external LU.

You must also select the OPEN-V emulation type when VMA of LUN Security XP Extension is set for the external LU on the external array side.

If you select an emulation type other than OPEN-V, additional space is taken for XP management information. This means that after mapping, LU capacity is less than the actual external LU capacity (and the original data must be considered lost). For more information about volume capacity, see ”Limitations on External Storage XP operations” on page 32.

• IO Suppression mode (Enable or Disable)

When mapping an LU, determine whether to suppress I/O operations from hosts (via the local array) to the mapped external LU.

If you select Enable, you can use the mapped LU only for Flex Copy XP operations. If you select Disable, a host connected to the local array can use the mapped external LU as if it were

an LU inside the local array, but you cannot use the LU for Flex Copy XP operations. You can sel ect Enable only when you set the OPEN-V emulation type for the mapped LU. When you

set an emulation type other than OPEN-V, the IO Suppression mode is automatically set to Disable.

• Cache Mode (Enable or Disable)

Cache mode specifies if I/O from the host is propagated synchronously or asynchronously to the external storage device. All I/O to and from the local array in both cache modes always uses some amount of cache. Write operations are always backed up in duplex cache.

If you select Enable, the local array signals the host that an I/O operation completed after receiving the data into the local array’s cache memory, and then asynchronously destages the data to the external array’s cache where it is asynchronously destaged to disk.

If you select Disable, the local array signals the host that an I/O operation completed only after the local array has synchronously written the data to the external array’s cache. The external array’s cache then asynchronously destages this data to disk.

NOTE: Users should disable cache for low price/performance arrays, such as the HP MSA

arrays. The MSA array ports are slower than the XP FC ports. Disabling cache prevents applications that use the MSA from consuming significant amounts of XP cache.

NOTE: As an option, consider using XP Disk/Cache Partition as a recommended best practice for

managing XP cache consumption. See ”Managing cache with external storage” on page 43 or contact your HP account support representative for more information about optimizing cache usage for external storage.

When IO Suppression mode is set to Enable, Cache Mode changes by default to Disable. If you use an external LU and set Cache Mode to Disable for Cache LUN XP operations, you cannot

use the Cache LUN XP Bind mode. For more information, see the HP StorageWorks Cache LUN XP user guide for XP12000/XP10000/SVS200.

NOTE: If you set the emulation type of the mainframe system for the mapped LU, host I/O is

always propagated asynchronously to the external LU regardless of the Cache Mode setting.

• CLPR

When using XP Disk/Cache Partition to partition cache memory, set the cache logical partition (CLPR) used for accessing the mapped LU. You can also specify whether the CU selected at mapping is

External Storage XP user guide 21

restricted to the storage management logical partition (SLPR) the CLPR belongs to. For more information about CLPRs and SLPRs, see the HP StorageWorks XP Disk/Cache Partition user guide.

Alternate paths

When mapping an external LU as an internal LDEV, paths are set from the internal LDEV to the external LU.

If two or more paths to the external LU are equipped from different clusters, the number of paths you set when mapping the volume are available. If one path is equipped, only that path is available.

You can set up to eight paths to each external LU, including paths automatically set. Among the paths to the external LU, the path with the highest priority is called the primary path, and other paths are alternate paths.

Alternate path modes include Single mode and Multi mode. The alternate path mode, Single mode or Multi mode, depends on the connected external array. For Single mode, only the path with the highest priority (primary path) is used to execute I/Os to the external LU. When an error occurs in the primary path, the path with the second highest priority is used (that is, no per-LU dynamic load balancing across paths). For Multi mode, all set paths are used at the same time. The paths are used to execute I/Os to the external LU, distributing the work load (round-robin processing).

For example, when an external LU volume with an alternate path in Single mode is mapped to an internal LDEV using External Storage XP, host I/O operations to the external LU via the local array are normally enabled using the mapped path. If the mapped path is not available (for instance, during array maintenance or following a failure in the channel processor), the path is switched automatically to the alternate path (if available). As long as an alternate path is available, host I/O operations continue as usual, even when an error occurs in the original path.

NOTE: When the primary path cannot be used for the length of the Path Blockade Watch timer (for

example, 180 seconds), the path is switched to an alternate path.

If you have not configured any alternate paths, host I/O operations are suspended when the primary path becomes unavailable (such as during array maintenance operations or following a failure in the channel processor).

HP recommends configuring alternate paths for safer operation and increased bandwidth. For instructions, see ”Setting alternate paths for external LUs” on page 84.

You can set alternate paths when the external LUs are mapped as the internal LDEVs (see ”Mapping

external LUs (Add LU)” on page 70). You can also set alternate paths after completing the mapping

operation (see ”Setting alternate paths for external LUs” on page 84).

Example of an alternate path configuration

Figure 2 shows an example of an alternate path configuration. In Figure 2, external array ports WWN A

and WWN B are connected to CL1-A and CL2-A, respectively, which are designated as external ports in

22 Preparing for External Storage XP operations

the local array. You must specify the port of a different cluster in the local array for the alternate path, as ports CL1 and CL2 are specified in the figure.

Figure 2 Example of alternate path configuration

Figure 3 shows another example of an alternate path configuration. In Figure 3, two ports are specified in

the local array and connected to ports in the external array via switches. In this example, two ports from different XP12000/XP10000/SVS200 clusters are specified in the local array, thereby making it possible to configure an alternate path for high availability.

Figure 3 Example of alternate path configuration using two switches

In Figure 4, two paths are configured between the internal LDEV and external LU. However, only one port is specified in the local array and two ports are specified in the external arrays via the switch. Since two ports of different clusters must be set in the local array for External Storage XP to use alternate path settings, HP does not recommend the configuration shown in Figure 4.

Figure 4 Example of incorrect alternate path configurations

Examples of switching I/O execution paths to alternate paths

There are two alternate path modes: Single mode and Multi mode. This section describes examples of the performance when the I/O execution path switches to the alternate path for each path mode.

External Storage XP user guide 23

For more information about path status, see ”Adding alternate paths by selecting multiple external LUs

(Add Paths)” on page 89.

• Alternate path mode is Multi mode

Figure 5 shows an example of when the alternate path mode is Multi mode. When an error occurs in

one path, I/Os execute using paths other than the error path.

NOTE: As you restore the error path, use of the restored path automatically resumes.

Figure 5 Alternate path mode is Multi mode

NOTE: In Multi mode, active I/O load balancing occurs across external array ports and

controllers. The XP and EMC DMX are examples of external arrays that use Multi mode.

• Alternate path mode is Single mode

Figure 6 shows an example of when the alternate path mode is Single mode. When an error occurs in

the path used for I/Os, the I/O execution path switches to the path with the second highest priority.

24 Preparing for External Storage XP operations

NOTE: As you restore the path with a priority higher than the current path, the I/O execution path

automatically switches to the restored path with the highest priority.

Figure 6 Alternate path mode is Single mode

• Alternate path mode is Single mode and at least one alternate path is in Standby status

Figure 7 shows an example of when the alternate path mode is Single mode and there are alternate

paths in Normal and Standby status. Figure 8 shows another example of when the alternate path mode is Single mode. In Figure 8, there are alternate paths in Standby status only.

When an error occurs in the path used for I/Os, the I/O execution path switches to the path with the second highest priority in Normal status (Figure 7). If there is no path in Normal status other than the path used for I/Os, the status of the path in Standby status automatically changes to Normal and the I/O execution path switches to that path (Figure 8).

External Storage XP user guide 25

NOTE: When the external array is an EVA array, as you restore the path with the highest priority,

the I/O execution path switches back to the restored highest priority path. In this case, the status of the path for which the status changed to Normal when the error occurred changes back to Standby.

Figure 7 Alternate path mode is Single mode with alternate paths in Normal and Standby

NOTE: External arrays with Asymmetrical Active/Active (AAA) controllers, such as the Hitachi

Thunder, are an example of Figure 7. A notable characteristic of using AAA controller arrays as external storage is that paths to alternate ports on the owning controller for a given external LU are seen as Normal status, but I/O load balancing does not occur (either across controllers or across ports to the owning controller). Paths to the non-owning external controller’s ports are shown as Standby status.

26 Preparing for External Storage XP operations

Figure 8 Alternate path mode is Single mode with alternate paths in Standby only

NOTE: External arrays with Active/Standby (A/S) controllers, such as the MSA, are an example of

Figure 8. A notable characteristic of using A/S controller arrays as external storage is that there is

typically only a single port to the owning controller. Paths to the non-owning external controller’s ports are shown as Standby status. I/O load balancing does not occur across external controllers.

Powering arrays on or off

This section describes procedures for powering local and external arrays on or off after External Storage XP operations have started.

These procedures use the following commands:

• Disconnect Subsystem

Execute the Disconnect Subsystem command from the Command View XP or XP Remote Web Console GUI when you need to perform maintenance or stop the local or external array. This command stops acceptance of all host I/O operations to the external LU mapped as the internal LDEV. All outstanding data in cache memory on the local array intended for the external LU is written (de-staged) to the external LU.

For instructions on executing the Disconnect Subsystem command, see ”Disconnecting external arrays

or LUs” on page 95.

NOTE: To disconnect an individual LU, use the Disconnect Volume command. To delete a single

external LU’s mapping, use the Disconnect Volume command and then the Delete LU command. For instructions, see ”Deleting external LU mappings (Delete LU)” on page 101.

• Check Paths & Restore Vol.

External Storage XP user guide 27

This command checks if defined information about the mapped external LU and the actual external LU status match. If the external LU can be used as the mapped local array volume, the external LU is set to accept I/O, and you can continue using the external LU as a mapped LU.

Use this command to restore the external LU, which is set to reject host I/O operations by the

Disconnect Subsystem or Disconnect Volume command, as the mapped volume. You can execute the Check Paths & Restore Vol. command for the entire array or an individual LU.

If an error occurs in the external storage path such that the command fails, correct the error so the path can be restored, and execute the Check Paths & Restore Vol. command again.

For instructions, see ”Checking the connection status and resuming external LU operations (Check Paths

& Restore Vol.)” on page 97.

NOTE: When executing the Check Paths & Restore Vol. command, if the external LU is ready to

be restored as the mapped LU, the external LU is set to Available. However, if the external LU is not ready to be restored, the external LU status remains as Blocked.

The following sections describe procedures to power the local and external arrays on or off.

CAUTION: To power both the local and external arrays off, first power off the local array, and then

power off the external array.

CAUTION: To power both the local and external arrays on, first power on the external array, and then

power on the local array. If both are supplied by a common failed power source, one option to ensure that the external array is online and available before the XP powers up is to place the external array on an Uninterruptible Power Supply (UPS).

Powering local arrays on or off

To power local arrays off

1. Stop read and write I/Os to the external LU that is mapped as a local array internal LDEV.

2. Perform other operations required before powering the local array off.

3. Turn the local array’s power off.

NOTE: As you turn the local array’s power off, all data for the external LU in the local array’s cache

memory is written in the external LU (all data is destaged).

To power local arrays on

1. Power on the external array containing the external LU mapped as a local array internal LDEV.

2. Turn on the local array’s power.

CAUTION: When the local array is powered off after executing the Disconnect Subsystem command,

you cannot access the mapped external LU from the local array when you first power on the local array. You must execute the Check Paths & Restore Vol. command to resume using the mapped external LU. The Check Paths & Restore Vol. command checks if the defined information and actual status of the external LU mapped as a local array volume match. If the external LU is ready to be used as a mapped volume, the LU is set to accept I/Os and you can resume using the volume as a mapped volume.

28 Preparing for External Storage XP operations

CAUTION: When the Disconnect Subsystem or Disconnect Volume command is executed and all data in

cache memory is written to the external LU, the displayed information for Ex-Dev. Status in the Device list becomes Disconnect.

Powering external arrays on or off

To power external arrays off

1. Stop read and write I/Os to the external LU that is mapped as a local array internal LDEV and is

located in the external array you want to power off.

2. Execute the Disconnect Subsystem command for the external array you want to power off.

Additional I/O to the external LU is stopped and all data in the local array cache memory is written to the external LU (all data is destaged). For instructions, see ”Disconnecting external arrays or LUs” on page 95.

3. Perform other operations required before powering the external array off.

4. Power the external array off.

CAUTION: After executing the Disconnect Subsystem command, if you need to use the mapped external

LU again, execute the Check Paths & Restore Vol. command.

To power external arrays on

1. Power on the external array containing the external LU that is mapped as a local array internal LDEV.

2. Execute the Check Paths & Restore Vol. command. For instructions, see ”Checking the connection status

and resuming external LU operations (Check Paths & Restore Vol.)” on page 97.

CAUTION: When powering the external array off after executing the Disconnect Subsystem command,

you cannot access the mapped external LU from the local array when you initially turn on the external array. You must execute the Check Paths & Restore Vol. command to resume using the mapped external LU. The Check Paths & Restore Vol. command checks the defined information and the actual status of the external LU mapped as a local array internal LDEV. If the external LU is ready to be used as a mapped volume, the LU is set to accept I/Os and you can resume using the LU as a mapped volume.

Using mapped external LUs from the host connected to the local array

The following sections describe examples of using the mapped external LU from the host connected the local array.

Writing new data to mapped external LUs

Figure 9 shows an example of writing new data in the mapped external LU from the host connected to the

local array.

1. Use the External Storage XP GUI to map the LU in the external array as an internal LDEV of the local

array.

CAUTION: You must set IO Suppression mode to Disable.

You can select the mapped volume’s emulation type as required. If you select an emulation type for an open-system (such as OPEN-V), go to step 2. If you select an emulation type for a mainframe system (such as 3390-3), go to step 3.

For more information, see ”Mapping external LUs (Add LU)” on page 70.

2. For open-system emulation types (such as OPEN-V, which HP recommends), the status of the mapped

LDEV is set to Normal and is not automatically formatted. To optimally initialize the mapped LU’s data

External Storage XP user guide 29

area, use Volume Manager to format the mapped LU. For instructions, see the HP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200.

To to step 4.

3. For mainframe-system emulation types (for example, 3390-XX), the status of the mapped LU is set to

Blockade, pending resizing and formatting. Use Volume Manager to format the volume. If you

mapped a volume for which the data area is already zero-formatted on the external array side, use Volume Manager’s Write to Control Blocks operation to restore the volume. For instructions, see the

HP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200.

4. Configure the path from the Target port to the mapped volume to perform host I/O operations. The

mapped LDEV is available for host I/O operations. After the path is set, host I/O operations to the mapped LU are available.

Figure 9 Writing new data to mapped external LUs

Using existing data in mapped external LUs

Figure 10 shows an example of using existing data in a mapped external LU from the host connected to

the local array.

1. From the host connected to the external array, write data to the LU in the external array.

2. Use External Storage XP to map the LU in the external array containing data as an internal LDEV of the

local array. When mapping the external LU, set the following attributes for the mapped LU:

• Emulation type: OPEN-V

• IO Suppression mode: Disable For more information, see ”Mapping external LUs (Add LU)” on page 70.

CAUTION: You must set the emulation type to OPEN-V to read existing data in the mapped

external LU from the local array side. Other emulation modes require that the data space be resized, which in effect destroys existing data. Once an external LU is mapped to the local array for use by External Storage XP, direct host access to that LU is no longer allowed. Also set the emulation type to OPEN-V when the VMA of LUN Security XP Extension is set for the external LU on the external array side.

3. Configure the path from the Target port to the mapped LU to perform host I/O operations.

30 Preparing for External Storage XP operations

+ 120 hidden pages

HP StorageWorks XP12000, StorageWorks XP10000, StorageWorks SVS200 External Storage XP user guide

Specifications and Main Features

Frequently Asked Questions

User Manual