HP - ExternalStorageUG Rootsan Technologies PVT LTD

HP StorageWorks
External Storage XP user guide

XP12000
XP10000
SVS200
Part number: T1706-96006

Sixth edition: June 2006
Legal and notice information
© Copyright 2005, 2006 Hewlett-Packard Development Company, L.P.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
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
Using external LUs for Snapshot XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3 Managing cache with external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Guidelines for using cache with external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Determining, setting, or changing the external LU cache mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Determining if the cache mode is disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Changing the cache mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Collecting device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Deleting and remapping the external LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Partitioning cache for external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
External Storage XP user guide 3

For example, Company A uses: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
In another example, Company B uses the following storage tiers: . . . . . . . . . . . . . . . . . . . . . . 49
To partition cache for external storage:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Determining the number and size of needed partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Creating Cache partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Changing storage system modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4 External Storage XP panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

LU Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Device tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Device list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
WWN tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
WWN list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Port tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Port list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Filter button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Preset list (LU Operation pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Port Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Port Operation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Port Operation list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Preset list (Port Operation pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5 Configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Overview of configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Setting an external array’s port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Setting a local array’s port attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Mapping external LUs (Add LU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Mapping external LUs individually (Add LU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Select Paths pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Mapping multiple external LUs at one time (Add LU (Auto)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Select LDEV window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Displaying detailed information stored in VMA (VMA information). . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Setting alternate paths for external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Defining alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Changing a defined alternate path priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Canceling alternate path definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Changing alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Adding alternate paths by selecting multiple external LUs (Add Paths) . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Deleting alternate paths by selecting multiple external LUs (Delete Paths) . . . . . . . . . . . . . . . . . . . . . . . . . 93
Checking an external LU’s status (LDEV Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Obtaining information about external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Restoring external LUs (Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Displaying configuration information for external LUs (Volume Detail). . . . . . . . . . . . . . . . . . . . . . . . . 97
Disconnecting external arrays or LUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Disconnecting all external LUs in an external array (Disconnect Subsystem). . . . . . . . . . . . . . . . . . . . . 99
Disconnecting external LUs individually (Disconnect Volume) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.) . . . . . . 100
Restoring all external LUs in an external array (Check Paths & Restore Vol.) . . . . . . . . . . . . . . . . . . . 100
Restoring external LUs individually (Check Paths & Restore Vol.) . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restoring external LUs (LDEV Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restoring volumes in an external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restoring volumes in a mapped external LU individually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Stopping the use of paths to an external LU by specifying an external array’s WWN (Disconnect Paths) . . 102
Restoring paths to an external LU by specifying an external array’s WWN (Check Paths) . . . . . . . . . . . . 102
Changing an external array’s port setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Stopping the use of paths to an external LU by specifying a local array’s port (Disconnect Paths) . . . . . . . 104
Restoring paths to an external LU by specifying a local array’s port (Check Paths) . . . . . . . . . . . . . . . . . 104
Deleting external LU mappings (Delete LU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4
6 Troubleshooting NAS Blade systems that include external arrays . . . . . . . . . . . . . . . . . 107
Stopping and restarting external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Stopping external arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Restarting external arrays and restoring NAS Blade systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Recovery procedures for errors in external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Errors in an external array’s disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Errors in a path to the external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Errors in all paths to the external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
If each node uses a different external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
If both nodes use the same external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
7 Remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Overview of remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Notices about remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Mapping command devices as remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Using Continuous Access XP or Continuous Access XP Journal with remote command devices . . . . . . . . . 117
Using Initiator/External MIX mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Restrictions on Initiator/External MIX mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8 Troubleshooting External Storage XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

A Notes on connecting external arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Connecting Thunder 9500V subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
System parameters for connecting Thunder 9500V subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Relationship between serial numbers in the Device list on the LU Operation pane and Thunder
9500V subsystem models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Relationship between the WWN of the port on the Thunder 9500V subsystem and the controller . . . . 129
Path status and examples of recovery procedures (Thunder 9500V subsystems) . . . . . . . . . . . . . . . . . 130
Connecting TagmaStore AMS and TagmaStore WMS subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems . . . . . . . . . . 130
Relationship between serial numbers in the Device list on the LU Operation pane and TagmaStore
AMS and TagmaStore WMS subsystem models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Relationship between the WWN of the port on the TagmaStore AMS or TagmaStore WMS
subsystem and the controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS
subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Connecting XP12000/XP10000 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) . . . . . . . . . . . . . 134
Connecting XP1024/XP128 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) . . . . . . . . . . . . . . . . 135
Connecting XP512/XP48 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Path status and examples of recovery procedures (XP512/XP48 Disk Arrays) . . . . . . . . . . . . . . . . . . 136
Connecting HP 200 Storage Virtualization System as external storage . . . . . . . . . . . . . . . . . . . . . . . . . 137
Path status and examples of recovery procedures (SVS200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Connecting EVA arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Identifying logical volumes of EVA arrays (using Characteristic 2) . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Alternate path’s behavior when an EVA array is connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
B Required volume capacity for emulation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

C Adjusting volume capacity for copy pair setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Copying data from external arrays (using external LUs as P-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Copying data to external arrays (setting external LUs as S-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
D Using an XP12000/XP10000/SVS200 with an EVA3000/5000 external storage . . . . 147

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Physical array connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Minimum physical configuration for HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Expanded configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Creating new EVA host objects for the XP12000/XP10000/SVS200 . . . . . . . . . . . . . . . . . . . . . . . 148
Creating and presenting EVA Vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Defining XP12000/XP10000/SVS200 external ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Defining XP12000/XP10000/SVS200 external storage LDEVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Performance considerations for using EVAs as external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Defining alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
E Configuring MSA1000/1500 as external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Configuring external array LUs, host mode, and ports . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 155
Connecting MSA1000/1500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 155
Setting up the MSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 156
Defining MSA array objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 156
Calculating MSA LU size and defining LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 156
Selective Storage Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. .. ...... 157
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
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 Example of Snapshot XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
19 LU Operation pane, Cache Mode setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
20 LU Operation pane, LU number and UUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
21 LU Operation pane, Path Setting option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
22 Path Setting pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
23 LDEV Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
24 Partition Definition pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
25 Partition Definition pane, Cut option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
26 Partition Definition pane, Paste Parity Group option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
27 Panes for External Storage XP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
28 LU Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
29 Device tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
30 Device list (external device selected in Device tree) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
31 WWN tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
32 WWN list (External Devices selected in the WWN tree). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
33 Port tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
34 Port list (External selected in Port tree). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
35 Filter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
36 Preset Detail window (mapping operation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
37 Port Operation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
38 Port Operation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
39 Port Operation list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
40 Preset Detail window (changing port attribute). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6
41 Overview of configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
42 Add LU window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
43 Select Paths pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
44 Add LU pane (mapping using the Linear button). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
45 Add LU pane (mapping with the Linear button released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
46 SSID window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
47 Set SSID window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
48 Auto Map Setting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
49 Select LDEV window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
50 VMA Information pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
51 Path Setting window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
52 Path Setting window, shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
53 Add Paths window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
54 Delete Paths window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
55 LDEV Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
56 Shortcut menu of the LDEV Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
57 Volume Detail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
58 Disconnect Subsystem and Check Paths & Restore Vol. Commands . . . . . . . . . . . . . . . . . . . . . . . . . 99
59 Change Parameter pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
60 Example of a NAS Blade system configuration that includes an external array . . . . . . . . . . . . . . . . 107
61 Error in an external array’s disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
62 Error in a path to the external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
63 Error occurs on the path to the external array used for node 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
64 If both nodes use the same external array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
65 Overview of remote command device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
66 Difference between Standard and Initiator/External MIX modes . . . . . . . . . . . . . . . . . . . . . . . . . . 118
67 Using Continuous Access XP or Continuous Access XP Journal with remote command devices . . . . . . 119
68 Configuration example for which logical volumes can only be identified by characteristic. . . . . . . . . 139
69 LDEV capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
70 Calculating LU capacity (OPEN-3 example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
71 Copying data from external arrays (using external LUs as P-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . 145
72 Copying data to external arrays (setting external LUs as S-VOLs) . . . . . . . . . . . . . . . . . . . . . . . . . . 146
73 XP12000/XP10000/SVS200-EVA minimum connections for HA . . . . . . . . . . . . . . . . . . . . . . . . . . 147
74 XP12000/XP10000/SVS200-EVA connections for expanded performance . . . . . . . . . . . . . . . . . . 148
75 Creating EVA host objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
76 Adding ports to XP12000/XP10000/SVS200 host objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
77 Selecting Vdisk’s Preferred path/mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
78 Presenting Vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
79 Defining XP12000/XP10000/SVS200 external ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
80 Selecting EVA LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
81 XP External LDEV definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
82 Configuring alternate paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
83 Example: Connecting an MSA array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
84 Defining MSA array objects with the ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
85 Defining MSA LUs with ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
86 Configuring SSP with ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5 When external LU’s emulation type is for mainframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6 Recommended individual CLPR cache size for external storage on open systems . . . . . . . . . . . . . . . . . 50
7 Recommended individual CLPR cache size for external storage on HP storage virtualization systems . . . 50
8 External array status values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
9 Mapped external LU status values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
10 Information displayed in the Device column for remote command devices . . . . . . . . . . . . . . . . . . . . . 116
11 Restrictions on remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

12 General External Storage XP troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
13 System parameter settings (Thunder 9500V subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
14 Relationship between serial numbers and subsystem models (Thunder 9500V subsystems) . . . . . . . . . 129
15 Relationship between ports’ WWNs and controllers (Thunder 9500V subsystems) . . . . . . . . . . . . . . . 129
16 Path status and examples of recovery procedures (Thunder 9500V subsystems). . . . . . . . . . . . . . . . . 130
17 System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems) . . . . . . . . . . . . . . . 131
18 Relationship between serial numbers and subsystem models (TagmaStore AMS and TagmaStore
WMS subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
19 Relationship between ports’ WWNs and controllers (TagmaStore AMS and TagmaStore WMS
subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
20 Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS
subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
21 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) . . . . . . . . . . . . . 134
22 Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) . . . . . . . . . . . . . . . . 135
23 Path status and examples of recovery procedures (XP512/XP48 Disk Arrays) . . . . . . . . . . . . . . . . . . 136
24 Path status and examples of recovery procedures (SVS200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
25 External LU’s maximum usable capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
26 LDEV capacity information for each emulation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
27 Volume capacity information for each emulation type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8
About this guide
This guide provides information about:
• Preparing for External Storage XP operations
• Performing External Storage XP operations
• Troubleshooting NAS Blade systems that include external arrays
• 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:
http://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.

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

• 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
Italic text Text emphasis
Monospace text • File and directory names

• System output
• Code
• Commands, their arguments, and argument values
Monospace, italic text • Code variables
• Command variables
Monospace, bold text Emphasized monospace text
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.
10
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.

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

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 45 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).
“10000”.
• Alternate paths are in Multi mode.

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.
HP StorageWorks XP512/XP48 Disk Array • In External Storage XP panes, the arrays appear as
“256”.
HP StorageWorks 200 Storage Virtualization System • In External Storage XP panes, the array appears as
“SVS200”.
HP StorageWorks 3000/5000 Enterprise Virtual Array • In this user guide, the arrays appear as “EVA
(Active/Standby and Active/Active controllers) or array”.
HP StorageWorks 4000/6000/8000 Enterprise Virtual • In External Storage XP panes, the arrays appear as
Array (Active/Active controllers) “EVA”.
• Alternate paths are in Single mode (meaning that
dynamic load balancing across multiple active paths
is not enabled).
HP StorageWorks MSA1000/1500 (Active/Standby) • In this user guide, the arrays appear as “MSA
array”.
• In External Storage XP panes, the arrays appear as
“MSA”.
• Alternate paths are in Single mode.
TagmaStore™ Universal Storage Platform subsystem • In this user guide, the array appears as
“TagmaStore™ USP subsystem”.
• In External Storage XP panes, the array appears as
“USP”.
TagmaStore™ Network Storage Controller subsystem • In this user guide, the array appears as
“TagmaStore™ NSC subsystem”.
“NSC”.
TagmaStore™ Adaptable Modular Storage subsystem • In this user guide, the array appears as
“TagmaStore™ AMS subsystem”.
“AMS”.
TagmaStore™ Workgroup Modular Storage subsystem • In this user guide, the array appears as
“TagmaStore™ WMS subsystem”.
“NSC”.

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”.
“9970V” and “9980V”, respectively.
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”.
“9500V”.
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”.
A/H-6593 subsystem • In External Storage XP panes, the array appears as

“300”.
SANRISE Universal Storage Platform subsystem • In this user guide, the array appears as “SANRISE
USP subsystem”.
“USP”.
SANRISE Network Storage Controller subsystem • In this user guide, the array appears as “SANRISE
NSC subsystem”.
“NSC”.
SANRISE Adaptable Modular Storage subsystem • In this user guide, the array appears as “SANRISE
AMS subsystem”.
“AMS”.
SANRISE Workgroup Modular Storage • In this user guide, the array appears as “SANRISE
WMS subsystem”.
“WMS”.

Storage array Notes

SANRISE9900V series subsystem • “SANRISE99xxV series subsystem” indicates the
SANRISE9970V and SANRISE9980V.
• In this user guide, the arrays appear as
“SANRISE9900V subsystem”.
“9970V” and “9980V”, respectively.
SANRISE9500V series subsystem • “SANRISE95xxV series subsystem” indicates the

SANRISE9530V, SANRISE9570V, and
SANRISE9580V.
“SANRISE9500V subsystem”.
“9500V”.
SANRISE2000 series subsystem • “SANRISE2000 series subsystem” indicates the

SANRISE2200 and SANRISE2800.
“SANRISE2000 subsystem”.
• In External Storage XP panes, the SANRISE2200
appears as “0401”, and the SANRISE2800
appears as “0400”.
SANRISE H12000 subsystem • In External Storage XP panes, the array appears as

“12000”.

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

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


“256”.
IBM Storage Subsystem For specific supported storage arrays, contact your
HP account support representative.
EMC Storage Subsystem For specific supported storage arrays, contact your
Fujitsu Storage Subsystem For specific supported storage arrays, contact your
NEC Storage Subsystem For specific supported storage arrays, contact your

CAUTION: For more information about alternate path modes, see ”Setting alternate paths for external
LUs” on page 86.
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 • HP StorageWorks 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)
Maximum number of external LUs 1,024 per port
addressable per local array port
Maximum number of external LUs that can • For the XP12000, 15,360 volumes can be connected
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 number of FC paths that can exist 8

to one external LU
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:

• 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 72.
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 141.
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 73.
The following are the external LU’s attributes:
• Emulation type

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 select 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 45 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
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

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 86.
You can set alternate paths when the external LUs are mapped as the internal LDEVs (see ”Mapping
external LUs (Add LU)” on page 73). You can also set alternate paths after completing the mapping
operation (see ”Setting alternate paths for external LUs” on page 86).
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

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.

For more information about path status, see ”Adding alternate paths by selecting multiple external LUs
(Add Paths)” on page 91.
• 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.

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

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.

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 98.
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 104.
• Check Paths & Restore Vol.

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

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 98.
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 100.
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 73.
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

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

After the path is set, host I/O operations to the mapped volume are available.
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 disk volume as a local array volume, access the mapped external disk volume only via the
local array.
NOTE: Except on the MSA, a host can directly access external array volumes that are not mapped as
local array volumes.
Figure 10 Using existing data in mapped external LUs (without formatting)
Uninstalling External Storage XP

To uninstall External Storage XP, cancel any existing Flex Copy copy pairs, and delete any external LU
mappings.
1. Log in to Command View XP or XP Remote Web Console. For instructions, see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console
2. Click the External Storage XP button ( ). External Storage XP starts.
3. Cancel any existing Flex Copy pairs. For instructions, see the HP StorageWorks Flex Copy XP user
guide.
4. Delete any external LU mapping. For instructions, see ”Deleting external LU mappings (Delete LU)” on
page 104.
5. Use the Command View XP or XP Remote Web Console Licensing module to remove the Flex Copy XP
license key. 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.
6. For the local array, use the Command View XP or XP Remote Web Console Licensing module to
remove the External Storage XP license key. 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.

Limitations on External Storage XP operations
• External LUs can be mapped as any CU:LDEV combination from 00:00 to 3F:FF.
• Only ports in SLPR0 can be set as external ports.
• 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 disk volume as a local array volume, access the mapped external disk volume
only via the local array.
• Except on the MSA, a host can directly access external array volumes that have not been mapped as
local array volumes.
• Continuous Access XP P-VOLs, S-VOLs, and journal volumes are not supported on MSA arrays.
• HP does not recommend that volumes involved with Snapshot XP reside on external MSA arrays.
• If you map an external LU that is more than 2 TB with the setting of OPEN-V emulation type, you can
access data stored in the field up to 2 TB. You cannot access data stored in the field over 2 TB.
• When mapping a volume that has a capacity of 2 TB or less in the external array and (external LU)
with the OPEN-V emulation type, the LU is defined as an internal LDEV with the same capacity as the
mapped external LU. That is, no space is forfeited for management space, and no formatting of that
data occurs. Therefore, OPEN-V is recommended.
Figure 11 Example of external LU with 2 TB or less

• If you map an external LU that is equal to or greater than 575.98 GB with an OPEN emulation type
other than OPEN-V, you can access data stored in the field up to 575.98 GB. You cannot access data
stored in the field over 575.98 GB.
However, for emulation types with a small base capacity, some of the field of 575.98 GB might not
be available. For more information, see ”Required volume capacity for emulation types” on
page 141.
• If you map an external LU that is equal to or greater than 575.98 GB with a 3380 mainframe
emulation type, you can access data stored in the field up to 575.98 GB. You cannot access data
page 141.
• If you map an external LU that is equal to or greater than 695.98 GB with a 3390 mainframe
emulation type, you can access data stored in the field up to 695.98 GB. You cannot access data
page 141.
• If you plan to use the mapped external LU from the mainframe OS (volume is mapped with a 3380-x
or 3390-x mainframe emulation type), you must select an external LU that consists of one LDEV or you
must first adjust the capacity of the external LU to be mapped. If multiple LDEVs exist in one external LU
and if numerous I/Os are made to these LDEVs, the read and write commands might timeout. When
the commands timeout, the SIM (21D2xx) is reported.
• When mapping an external LU as internal LDEVs with emulation types other than OPEN-V, the number
of volumes and the volume capacity of the mapped internal LDEVs depends on the original external

LU’s capacity and each emulation type’s normal size. When mapping an external LU using emulation
types other than OPEN-V, an XP array management information area is required in the mapped LU.
This means that the capacity available after mapping is slightly smaller than the actual external LU
capacity. Available capacity decreases by the size of the XP array management information area,
and all prior data must be considered lost. For more information, see the HP StorageWorks Flex Copy
XP user guide.
Figure 12 shows an example where the external LU’s original capacity is larger than (or a multiple of)
the normal size of the local array’s emulation type (OPEN-3 in this example). Therefore, in this
example, the local array can realize two fully-sized OPEN-3 LDEVs, with some space (insufficient to
create a full OPEN-3) left over.
Figure 12 External LU capacity is larger than the specified emulation type’s basic capacity (OPEN-3
example)
Figure 13 shows an example where the external LU’s original capacity is smaller than the normal size
of the local array’s emulation type. In this example, since the resulting space is insufficient to create a
local array OPEN-3 LDEV, you can designate it as either a local array OPEN-V or an OPEN-3 CVS
LDEV. If the external LU were an XP of OPEN-3 emulation type, forfeiting a small amount of
management space would also result in an OPEN-3 CVS volume or an OPEN-V.
Figure 13 External LU capacity is smaller than the specified emulation type’s basic capacity
• IO Suppression mode can only be selected when the volume being mapped is set to the OPEN-V
emulation type. If a different emulation type is set, IO Suppression mode is automatically set to Disable.
• If you use the mapped external LU from the host connected to the local array, set the IO Suppression
mode to Disable when mapping the LU. For External Storage XP, select Disable. For Flex Copy XP, select
Enable.
• If you use the mapped external LU for the copy source or copy destination volume for a Flex Copy XP
pair, set the emulation type to OPEN-V when mapping the volume.
• If you use the mapped external LU for the copy source or copy destination volume for a Flex Copy XP
pair, set IO Suppression mode to Enable when mapping the volume.

• The local array does not force the external array to reserve the mapped external LU. Therefore, do not
write directly to an external array LU (that is, without writing via the local XP array) with IO Suppression
mode set to Disable from the external array side.
If Flex Copy XP operations are in progress for a volume with IO Suppression mode set to Enable, be
careful when updating data in that external LU from the external array side.
• IO Suppression mode is automatically set to the same status for all LDEVs in a given external LU.
• Cache Mode is automatically set to the same status for all LDEVs in a given external LU.
• If you set an open-system emulation type (such as OPEN-V) when mapping the external LU, you can
use the external LU immediately.
To optionally initialize the LU’s data area, use Volume Manager to format the LU. For instructions, see
the HP StorageWorks LUN Configuration and Security Manager XP user guide for the
XP12000/XP10000/SVS200.
• If you set a mainframe-system emulation type (such as 3390-3) when mapping the external LU, format
the LU or perform the Write to Control Blocks operation to make the volume usable.
After the mapping operation, the mapped LU’s status is Blockade. Use Volume Manager to format the
volume or perform the Write to Control Blocks operation to make the volume usable.
• If you mapped a volume that has already been zero-formatted on the external array side, perform
the Write to Control Blocks operation.
• If you mapped a volume that has not been zero-formatted on the external array side, format the
volume on the local array side.
For instructions on the formatting and Write to Control Blocks operations, see the HP StorageWorks
LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200.
If you format the external array’s mapped LU from the external array side, data that existed prior to
formatting cannot be ensured. When using the mapped external LU from the mainframe OS, format the
mapped volume from the local array side.
• If you set a mainframe-system emulation type for the mapped LU, host I/O is always propagated
asynchronously to the external LU regardless of the Cache Mode setting.
• External LU attributes (IO Suppression mode and Cache Mode) set when the LU is mapped cannot be
changed while the LU is mapped. To change these attributes, delete the external LU mapping (Delete LU
operation), and remap the LU with different attributes (Add LU operation).
• External LU attributes for all LDEVs created in an external LU are set to the same values. Those attributes
are modified when the LDEVs are reconfigured using Volume Manager.
• Mapped LUs that have different external LU attributes or reside on different arrays cannot be used to
create one LUSE volume.
• A mapped external LU with IO Suppression mode set to Enable (such as for Flex Copy XP) cannot be
used for the local array’s Cache LUN XP operations.
• For a mapped external LU with IO Suppression mode set to Disable (such as for External Storage XP),
Cache LUN XP’s Bind mode is not available.
• If you use the mapped external LU for Cache LUN XP operations and set the bind mode, Cache LUN XP
operations require a cache of twice the capacity of the user data.
• For External Storage XP, IO Suppression mode is typically set to Disable. You cannot use a mapped
external LU with IO Suppression mode set to Enable for pair copy operations in Continuous Access XP,
TrueCopy for z/OS®, Continuous Access XP Journal, Universal Replicator for z/OS, Business Copy XP,
ShadowImage for z/OS, or Snapshot XP. Also, the external LU cannot be used for automatic Auto LUN
XP operations.
• Attributes originally set for an external LU on the external array side (such as port security, LUN
security, and Volume Retention Manager attributes) are not kept when the external LU is mapped as a
local array internal LDEV. To keep the original attributes, set those attributes on the mapped external LU
from the local array side.
• If you mapped the external LU and previously set the VMA of LUN Security XP Extension in that volume,
the former VMA setting is superseded when you map the volume again. However, if LUN Security XP
Extension is not installed when you remap the volume, the volume with the VMA setting cannot be
mapped. To change the VMA setting, change it from the local array side.

• Do not combine LDEVs from multiple external LUs to create a LUSE volume.
• Do not update a volume being used or operated by Flex Copy XP. Also do not update the external LU
on the external array side.
• You can delete up to 256 mappings for external LUs at one time.
• Operations cannot be performed if some parts of the local array are blocked. In this case, restore
blocked parts of the local array, and retry the operation.
• When using the Thunder 9500V series subsystem as an external array, the following versions are
recommended. If you use a 9500V array with a version that is earlier than the following versions, the
SATA drive information might not display correctly.
• For Thunder 9530V, Thunder 9520V, Thunder 9570V: version 0658 or later
• For Thunder 9580V, Thunder 9585V: version 1658 or later
• Do not map multiplatform volumes of external arrays as internal LDEVs.
• After executing the Check Paths & Restore Vol., Disconnect Subsystem, or Disconnect Volume
command, click the Refresh button ( ) on the Command View XP or XP Remote Web Console main
pane to update the information, and check the current status.
• When the external LU’s status is Blockade, execute the Check Paths & Restore Vol. command.
If the Check Paths & Restore Vol. command does not restore the external LU’s status, the path to the
external array might be blocked. In this case, see ”Troubleshooting External Storage XP” on page 121
for instructions on restoring the path to the external array.
If the external LU’s status remains Blockade even though you restored the path to the external array
and executed the Check Paths & Restore Vol. command, execute the Restore command.
• If you execute the Disconnect Subsystem or Disconnect Volume command when I/Os from the open
system host are in progress, host I/Os to the specified volume are forcibly stopped. When executing
the Disconnect Subsystem o Disconnect Volume command, stop host I/Os, and unmount the volume
from the host.
• If the volume is online from the mainframe host, you cannot execute the Disconnect Subsystem or
Disconnect Volume command. Stop host I/Os to the volume, and perform the Vary Offline operation.
• You cannot execute the Disconnect Subsystem or Disconnect Volume command for external LUs that
include LDEVs set as copy pairs for Flex Copy XP, Business Copy XP, ShadowImage for z/OS,
Continuous Access XP Journal, Universal Replicator for z/OS, Continuous Access XP, TrueCopy for
z/OS, or Snapshot XP. However, if the copy pair status is PSUE, you can execute these commands.
When the external LU is set as a pool volume (pool-VOL) and that Snapshot XP pair’s status is PAIR, you
can execute these commands.
include LDEVs for which Auto LUN XP’s migration processing is in progress.
• When executing the Disconnect Subsystem or Disconnect Volume command, the displayed information
for Ex-Dev. Status in the Device list becomes Cache Destage. Even if there is no data left in cache
memory, the displayed status stays Cache Destage until the Disconnect Subsystem or Disconnect Volume
command processing is complete.
• 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.
• When using the mapped external LU from the mainframe OS, set the Missing Interrupt Handler (MIH)
timer to 45 seconds, which is the recommended value.
• In the internal processing, the external LU’s RAID level is handled as RAID-1 across the board. A bar (–)
appears on the Command View XP or XP Remote Web Console panes. The external LU’s RAID level is
reported as RAID-1 when information about the external array is reported to higher-level devices (OS).

• Table 4 and Table 5 show the recommended application level for the mapped external LU according
to the external LU’s HDD type.
Table 4 When external LU’s emulation type is OPEN
Application HDD type

FC S-ATA
Database Not Recommended Not Recommended
Online Transaction Processing (OLTP)
File operation from host OK Not Recommended

(both Read and Write)
File operation from host OK OK

(mainly Read)
Backup OK Recommended
Archive OK Recommended
Table 5 When external LU’s emulation type is for mainframes
Application HDD type

FC S-ATA
Database Not Recommended Not Recommended
Online Transaction Processing (OLTP)
System volumes Not Recommended Not Recommended

(Journal, Check points)
Operation from TPF Not Supported Not Supported
File operation from host OK Not Recommended

(both Read and Write)
File operation from host OK OK

(mainly Read)
Backup OK Recommended
Archive OK Recommended
• The external array’s performance and status affect the mapped external LU’s Read and Write
performance. If there is a heavy load on the external array, the Read and Write operation’s processing
speed slows. In this case, I/Os from the mainframe host might have an MIH error.
• If the host connected to the local array issues too many I/Os for the external array to process,
commands from the host might time out.
When the amount of I/Os from the host to the external LU exceeds the maximum amount of I/Os the
external array can accept, commands from the host to the local array might time out. As you configure
the system using external LUs, consider the external array’s I/O capacity.
• When executing commands in HP StorageWorks software products to the mapped external LU and,
therefore, too many I/Os are issued for the external array to process, commands might time out and
errors might occur.
When the amount of I/Os from the software products to the external LU exceeds the maximum amount
of I/Os the external array can accept, commands might time out and errors might occur. As you
configure the system using external LUs, consider the external array’s I/O capacity.
• When using an external LU from the host, note the external LU’s Path Blockade Watch time. If the Path
Blockade Watch time is longer than the host command’s timeout period, commands from the host might
time out when the power supply is off or errors occur for the external array. If host I/O is a significant

concern, ensure that the external LU’s Path Blockade Watch time is the same as or shorter than the host
command’s timeout period.
• Host access to the external storage LU must be via the local array, and must not be via a direct physical
connection to the external storage device LU. For external array LUs not involved with External Storage
XP, direct access from a host is allowed for all supported external storage except MSA. If you use MSA
as external storage, it must be entirely dedicate as external storage.
• For all external storage, either set the ES XP cache mode option in Command View XP or XP Remote
Web Console to cache disabled or partition resources associated with external storage in its own CLPR
(for example, CLPR1). While HP strongly recommends this new default for all external storage in
general, this new default is mandatory for any external array that is slower than an XP12000 external
port (for example, the Modular Smart Array product line) unless it resides in its own CLPR partition with
isolated port/MP/cache resources.
Combining External Storage XP with other HP StorageWorks products

You can use HP StorageWorks software products to operate and manage the external LUs you set using
External Storage XP.
The following sections provide configuration examples for specific HP StorageWorks software products:
• ”Using external LUs for Auto LUN XP operations” on page 39
• ”Using external LUs for Continuous Access XP operations” on page 39
• ”Using external LUs for Continuous Access XP Journal operations” on page 40
• ”Using external LUs for Business Copy XP operations” on page 41
• ”Using external LUs for Snapshot XP operations” on page 42
The following HP StorageWorks software products support the use of mapped external LUs. For operations
and notes about each software product, see the product’s user guide.
• LUN Manager
• If you set an open-system emulation type when mapping the external LU, you must use LUN
Manager to set the mapped LU’s path.
• You cannot use the mapped external LU as a NAS system volume.
• You cannot use the mapped external LU as a NAS user volume.
• Volume Manager
• If you set a mainframe-system emulation type when mapping the external LU, you must format the
mapped volume or perform the Write to Control Blocks operation using the Custom Volume Size
(CVS) function before putting the external LU into use. For instructions, see the HP StorageWorks
• If you use the CVS function to create LDEVs from an external XP LU, the created LDEVs’ attributes (IO
Suppression mode and Cache Mode) are the same as the source external LU’s.
• You cannot combine the local array internal LDEV and external LU to form a LUSE volume.
• Do not combine LDEVs of multiple external LUs to create a LUSE volume. You can only use LDEVs in
the same external LU to set LUSE volumes.
• You cannot combine external LUs that have different IO Suppression modes to form a LUSE volume.
• You cannot combine external LUs that have different Cache Mode settings to form a LUSE volume.
• Cache LUN XP
• You must set the IO Suppression mode to Disable to use the mapped external LU for Cache LUN XP
operations.
• You cannot specify Cache LUN XP’s bind mode for an external LU that has Cache Mode set to
Disable.
• If you use the mapped external LU for a Cache LUN XP operation and set the bind mode, the Cache
LUN XP operation requires a cache that is twice the size of the user data.
• Continuous Access XP (Synchronous and Asynchronous)

You must set the IO Suppression mode to Disable to use the mapped external LU for Continuous Access
XP operations. For a Continuous Access XP configuration example, see ”Using external LUs for
Continuous Access XP operations” on page 39.
• TrueCopy for z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for TrueCopy for z/OS
operations.
• Continuous Access XP Journal
You must set the IO Suppression mode to Disable to use the mapped external LU for Continuous Access
XP Journal operations. For a Continuous Access XP Journal configuration example, see ”Using external
LUs for Continuous Access XP Journal operations” on page 40.
• Universal Replicator for z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for Universal
Replicator for z/OS operation.
• Business Copy XP
You must set the IO Suppression mode to Disable to use the mapped external LU for Business Copy XP
operations. For a Business Copy XP configuration example, see ”Using external LUs for Business Copy
XP operations” on page 41.
• ShadowImage for z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for ShadowImage for
z/OS operations.
• Snapshot XP
You must set the IO Suppression mode to Disable to use the mapped external LU for Snapshot XP
operations. For a Snapshot XP configuration example, see ”Using external LUs for Snapshot XP
operations” on page 42.
• Compatible PAV for IBM z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for Compatible PAV for
IBM z/OS operations.
• Volume Security
You must set the IO Suppression mode to Disable to use the mapped external LU for Volume Security
operations.
• Volume Retention Manager
You must set the IO Suppression mode to Disable to use the mapped external LU for Volume Retention
Manager operations.
• LUN Security XP Extension
• You must set the IO Suppression mode to Disable to use the mapped external LU for LUN Security XP
Extension operations.
• If you previously mapped the external LU and set the VMA of LUN Security XP Extension in that
volume, the previous VMA setting is overwritten when you map the LU again. However, if LUN
Security XP Extension is not installed when you remap the LU, you cannot map the LU with the VMA
setting.
• SNMP
Information about the mapped external LU and external port is displayed.
• Configuration File Loader
• You can set the path definition for external LUs (add, delete, or change paths).
• You can set the command devices on external LUs (add or delete the setting).
• CHA mode, host group, and WWN settings for external ports are not supported. When an external
LU is mapped through that external port, the topology setting is not available.
NOTE: Some mainframe products might be marketed under different HP names and are not supported at
this time. Contact your HP account support representative for the latest support matrix.

Using external LUs for Auto LUN XP operations
Figure 14 shows an example of using an external LU for Auto LUN XP operations. The mapped external
LU is set as the source volume, and the local array internal LDEV is set as the target volume. Existing data
in the external LU is (in effect) manually migrated to the internal LDEV on the local array using Auto LUN
XP. For more information, see the HP StorageWorks Auto LUN XP user guide for the
XP12000/XP10000/SVS200.
Figure 14 Example of Auto LUN XP operations

1. Use External Storage XP to map a volume in the external array to an internal LDEV of the local array.
For this example, set the following attributes for the mapped LU:
• Emulation type: OPEN-V
• IO Suppression mode: Disable
CAUTION: To migrate existing data in the mapped external LU to a local array volume using Auto
LUN XP or Business Copy XP, as shown in Figure 14, set the local array’s emulation type to
OPEN-V when mapping the LU. Only OPEN-V emulation can be used to read existing data in the
external LU from the local array side.
To copy existing data in the mapped external LU using HP StorageWorks software products, such
as Continuous Access XP and Business Copy XP, the mapped external LU’s emulation type must
also be OPEN-V.
2. Prepare a local array internal LDEV with the same capacity as the mapped external LU. Use Volume
Manager to adjust the internal LDEV’s capacity as required. For instructions, see the HP StorageWorks
CAUTION: The emulation type of the local array’s prepared internal LDEV must be OPEN-V.
3. Set the mapped external LU as the source volume, and set the local array internal LDEV as the target
volume.
4. Use Auto LUN XP to manually migrate existing data in the mapped external LU to the local array
internal LDEV (without changing the associated LDEV/LU).
Using external LUs for Continuous Access XP operations

Figure 15 shows an example of using an external LU for Continuous Access XP operations. The mapped
external LU is set as the Continuous Access XP pair’s S-VOL, and the volume in the local array that is
connected as the MCU is set as the Continuous Access XP pair’s P VOL. For more information about

Continuous Access XP operations, see the HP StorageWorks Continuous Access XP user guide for the
XP12000/XP10000/SVS200.
Figure 15 Example of Continuous Access XP operations

1. Use External Storage XP to map a volume in the external array to an internal LDEV of the local
Continuous Access XP RCU array.
CAUTION: Set the IO Suppression mode to Disable.
Select the mapped volume’s emulation type as required. If you select an open-system emulation type
(such as OPEN-V), go to step 2. If you select a mainframe-system emulation type (such as 3390-3), go
to step 3.
2. If you set an open-system emulation type when mapping the volume, the mapped volume’s status
automatically becomes Normal. However, the volume-formatting process is not automatically
executed. To optionally format the mapped volume, use the Custom Volume Size (CVS) function. For
instructions, see the HP StorageWorks LUN Configuration and Security Manager XP user guide for the
XP12000/XP10000/SVS200.
Go to step 4.
3. If you set a mainframe-system emulation type when mapping the volume, the mapped volume’s status
becomes Blockade. To format the volume, use the CVS function. To restore the volume, perform the
Write to Control Blocks operation if you mapped a volume for which the data area has already been
zero-formatted on the external array side. For instructions, see the HP StorageWorks LUN
Go to step 4.
4. Set the Continuous Access XP pair’s P-VOL and S-VOL.
Using external LUs for Continuous Access XP Journal operations

Figure 16 shows an example of using the external LU for Continuous Access XP Journal operations. The
mapped external LU is set as the Continuous Access XP Journal pair’s S-VOL, and the volume in the local

array that is connected as the MCU is set as the Continuous Access XP Journal’s P-VOL. For more
information, see the HP StorageWorks Continuous Access XP Journal user guide.
Figure 16 Example of Continuous Access XP Journal operations

1. Use External Storage XP to map the volume in the external array as an internal LDEV of the local array,
which is used as the RCU for Continuous Access XP Journal operations.
to step 3.
XP12000/XP10000/SVS200.
Go to step 4.
becomes Blockade. To format the volume, use the CVS function. To restore the volume, use the Write
to Control Blocks operation if you mapped the volume for which the data area has already been
Go to step 4.
4. Set the Continuous Access XP Journal pair’s P-VOL and S-VOL.
Using external LUs for Business Copy XP operations

Figure 17 shows an example of using an external LU for Business Copy XP operations. The mapped
external LU is set as the Business Copy XP pair’s S-VOL, and the local array internal LDEV is set as the

Business Copy XP pair’s P-VOL. For more information, see the HP StorageWorks Business Copy XP user
guide for the XP12000/XP10000/SVS200.
Figure 17 Example of Business Copy operations

to step 3.
XP12000/XP10000/SVS200.
Go to step 4.
becomes Blockade. To format the volume, use the CVS function. To restore the volume, perform the
Write to Control Blocks operation if you mapped a volume for which the data area has already been
Go to step 4.
4. Set the Business Copy XP pair’s P-VOL and S-VOL.
Using external LUs for Snapshot XP operations

Figure 18 shows an example of using an external LU for Snapshot XP operations. The mapped external LU
is set as a pool-VOL for the Snapshot XP pair.

For more information about Snapshot XP, see the HP StorageWorks Snapshot XP user guide.
Figure 18 Example of Snapshot XP operations

CAUTION: You must set the volume’s emulation type to OPEN-V when mapping the volume. You
can set only a volume with the OPEN-V emulation type as a Snapshot XP pool-VOL. Set the IO
Suppression mode to Disable.
2. The mapped volume’s status automatically becomes Normal. However, the volume formatting
processing does not execute automatically. To format the mapped volume, format the volume using the
CVS function. For instructions, see the HP StorageWorks LUN Configuration and Security manager XP
user guide for the XP12000/XP10000/SVS200.
3. Create a pool, and add the mapped external LU to that pool as a pool-VOL.
4. Set the Snapshot XP pair’s P-VOL and S-VOL specifying the pool you created in step 3.

3 Managing cache with external storage
XP disk arrays and storage virtualization systems use cache to facilitate host and internal I/O. When cache
mode is enabled, host I/O is accepted as quickly as it is received into the array’s cache where the
associated read or write is buffered. When cache mode is disabled, the array limits caching to one block
of read and write data per LDEV. Cache is also used by Data Mirroring and Data Migration products that
generate internal I/O to copy and move data between devices, such as:
• Business Copy XP
• Continuous Access XP software products
• Business Copy XP’s Snapshot feature
• Auto LUN XP
• XP Tiered Storage Manager
Having cache mode enabled for external storage devices that are slower than the XP array can provide a
performance benefit for some very specific and well-defined workloads, such as single-threaded sequential
access to a device. HP strongly recommends that you configure all external storage devices with cache
mode disabled unless you have determined that you meet these exact workload descriptions. When you
deviate from these workload descriptions, performance might not be as good as when cache is disabled.
Consult your HP account support representative to discuss the availability of tuning services for your XP
array.
This chapter explains how to balance cache usage between internal and external storage and protect the
potential benefits of using cache.
Guidelines for using cache with external storage

• Disable cache for external devices.
• Always disable cache mode for external LUs in an MSA or other storage array that is slower than
the XP or SVS200 external ports.
• Always disable cache mode for external LUs that are used by XP data replication or data migration
software (for example, P-VOLs, S-VOLs, pool volumes, and Auto LUN XP or XP Tiered Storage
Manager target volumes).
See ”Determining, setting, or changing the external LU cache mode” on page 45.
• Partition cache for external storage.
• Always put external volumes and internal XP volumes in separate cache partitions (CLPRs).
• Always partition external storage LUNs that are targets for XP data replication or migration software
(Business Copy XP, Continuous Access XP software products, Snapshot XP, Auto LUN XP, or XP
Tiered Storage Manager).
• Partition any external LUs that have cache enabled. External LUNs with cache enabled can use
large amounts of cache.
See ”Partitioning cache for external storage” on page 49.
• Consult HP account support representative to verify or change storage system modes. See ”Changing
storage system modes” on page 53.
Determining, setting, or changing the external LU cache mode

You set the cache mode when you define external LUs. HP strongly recommends that you set cache mode
to Disabled for external LUs. For instructions on mapping external LUs in a new configuration, see
”Mapping external LUs (Add LU)” on page 73.
CAUTION: Before you delete any LUs that you want to remap, carefully record necessary configuration
information. If you remap existing LUs with changed configuration settings (other than cache mode), you
can lose access to the LUs and the data they contain.

Determining if the cache mode is disabled
If you have an existing configuration and need to determine if your external LUs are configured with cache
mode disabled, follow this procedure:
1. In the XP Remote Web Console main pane, click the External Storage button in the left pane. The LU
Operation pane appears.
2. In the Device tree, select an external device group.
3. In the Device list, check the Cache Mode setting (Figure 19). If cache mode is enabled, you should
change it to Disabled.
Figure 19 LU Operation pane, Cache Mode setting
Changing the cache mode

If you need to change the cache mode for existing external LUs, you must delete and remap the external LU
path and definition.
CAUTION: Before you delete any LUs that you want to remap, carefully record necessary configuration
information. If you remap existing LUs with changed configuration settings (other than cache mode), you
can lose access to the LUs and the data they contain.
Collecting device information

Before you remap an external storage device, collect the following information for each device:
• LU number in the group
• Universal Unique ID (UUID)
• Path settings
• CVS settings
• Mapped location
• External group number
• CU:LDEV identifier
To collect each of these items:

1. In the XP Remote Web Console main pane, click the External Storage button in the left pane. The LU
Operation pane appears.
2. To find the LU number and UUID, select an external device group in the Device tree (Figure 20).
The LU number appears in the LUN column in the Device list.
The UUID appears in the Characteristic2 column in the Device list.
Figure 20 LU Operation pane, LU number and UUID

3. To find the path settings, right-click the external LDEV in the Device list, and select Path Setting
(Figure 21).
Figure 21 LU Operation pane, Path Setting option

The Path Setting pane appears (Figure 22).
Figure 22 Path Setting pane

4. To find the CVS settings, mapped location, external group number, and CU:LDEV identifier, right-click
the LDEV in the Device list on the LU Operation pane, and select LDEV Information (Figure 21). The
LDEV Information pane appears (Figure 23).
Figure 23 LDEV Information pane

Deleting and remapping the external LU
You must delete and remap each LU that needs the cache setting changed. Using the information recorded
in ”Collecting device information” on page 46, delete and remap each LDEV.
1. On the LU Operation pane, select the appropriate external LU group number in the Device tree.
2. In the Device list, right-click the external LU that you want to delete, and select Delete LU (Figure 21).
3. Click Apply.
4. Click either Yes or No. If you click Yes, skip the next step.

5. Click OK in response to the warning message.
6. Click OK.
7. Remap the LU using all the previous settings except for the cache mode setting, which is disabled. See
”Mapping external LUs (Add LU)” on page 73.
NOTE: When scanning for devices to add, the order in which devices are discovered might be
different. The UUID is always the same for the same external device. Ensure that the UUID of the
device being remapped matches the UUID that was deleted for the same LU number.
8. Recheck to ensure that the same external storage LUs (identified by UUIDs) are now assigned their
original settings and the desired cache mode. If not, delete and remap the external LU again.
Partitioning cache for external storage

Separate cache partitions isolate the applications that are using XP arrays and storage virtualization
systems from the I/O dampening effects of a cache that is filling up with host and internal I/O for slower
external targets. HP requires separate cache partitions (CLPRs) for:
• External volumes and internal XP volumes, except for configurations where all external storage LUNs
have cache disabled and do not have any external storage devices using data mirroring or migration
products
NOTE: All HP 200 Storage Virtualization System volumes are external. Partition SVS200 cache
according to the other recommendations made in this section.
• External volumes that are used by XP data replication or data migration products, including Business
Copy XP, Continuous Access XP software products, Snapshot XP, Auto LUN XP, and XP Tiered Storage
Manager
• SVS200 source volumes and data copy or target volumes that have slower throughput
For example, Company A uses:
• XP10000 internal disks for database applications
• EVA3000 for backup applications
Cache can be partitioned for Company A as follows:
• CLPR0: XP10000 for Business Copy XP P-VOL
• CLPR1: EVA3000 for Business Copy XP S0VOL (external LU cache is disabled)
In another example, Company B uses the following storage tiers:
• Tier 1 is an XP12000 (6 TB of internal space) for P-VOLs
• Tier 2 is an EVA (20 TB) for P-VOLs and Business Copy XP S-VOLs
• Tier 3 is two MSA 1500 (10 TB) for the Business Copy XP S-VOLs
Cache can be partitioned for Company B as follows:
• CLPR0: 12 GB for the internal XP12000 P-VOL
• CLPR1: 4 GB for the EVA S-VOL and P-VOL
• CLPR2: 4 GB for the MSA S-VOL
• All external LU cache is disabled.
To partition cache for external storage:
1. Determine the number and size of the partitions you need (see page 50).
2. Create the partitions (see page 50).

Determining the number and size of needed partitions
The minimum cache partition (CLPR) size is 4 GB. Determine the size you need for each CLPR being used
for external storage based on the total capacity of the assigned external volumes. Table 6 shows the
recommended cache sizes for external storage CLPRs on open systems. Table 7 shows the same
information for HP storage virtualization systems.
Table 6 Recommended individual CLPR cache size for external storage on open systems
External storage volume capacity assigned to CLPR Recommended cache size for CLPR
Less than 128,000 GB 4 GB
128,000 GB or more 8 GB
Table 7 Recommended individual CLPR cache size for external storage on HP storage virtualization
systems
External volume capacity assigned to CLPR CLPR0 Additional CLPRs

Less than 1 TB 4 GB 4 GB
1 TB <= capacity < 16TB 8 GB 4 GB
16 TB <= capacity < 20 TB 12 GB 4 GB
20 TB <= capacity < 128 TB 16 GB 4 GB
128 TB or more 24 GB 8 GB
Creating Cache partitions

Ensure the XP Disk/Cache Partition license is installed, you have Administrator authority on the array, and
you are in Modify mode in XP Remote Web Console. For more information about license keys and user
administration procedures, see the HP StorageWorks XP Remote Web Console user guide for
XP12000/XP10000/SVS200.
1. In XP Remote Web Console, click the Install button in the left pane.
2. Click the Partition Definition tab.
3. In the Cache Logical Partition tree, right-click SLPR0 (if you have additional storage partitions
configured, click the storage partition you want the CLPR to be created in), and select Create CLPR. The
new CLPR is added to the tree.

4. Select the new CLPR in the tree, and change the size and other CLPR settings as needed (Figure 24).
Figure 24 Partition Definition pane

5. Click Apply for the changes to becomes effective.
6. Repeat step 3 through step 5 to define any additional CLPRs that you need.
7. To allocate external storage groups to a CLPR:
a. Double-click the SLPR.
b. Select the CLPR that you want to assign the external storage groups from (this will be CLPR0 if this is
the first time you are configuring partitioning).

c. Select and right-click the external storage groups that you want to assign to another CLPR, and then
select Cut (Figure 25).
Figure 25 Partition Definition pane, Cut option

d. Right-click the CLPR that you want to assign the selected external storage groups to, and then select
Paste Parity Group (Figure 26). The selected external storage groups are added to the CLPR
resource list.
Figure 26 Partition Definition pane, Paste Parity Group option

e. Click Apply.

f. Repeat step 7b through step 7e until you have allocated the external storage groups to the
appropriate CLPRs according to the plan you created after reading ”Partitioning cache for external
storage” on page 49.
For complete information about creating SLPRs and CLPRs, see the HP StorageWorks XP Disk/Cache
Partition user guide.
Changing storage system modes

In addition to cache partitioning and cache modes, array system modes control LU cache usage.
HP service representatives can set the XP and SVS200 array system modes to adjust the array’s behavior.
For SVS200 arrays, no adjustments are needed.
For XP arrays, contact your HP account support representative to change the system modes if either of the
following is true:
• Your external LUs are used by XP or SVS200 data mirroring and data migration products such as
Business Copy XP, Snapshot XP, Auto LUN XP, or XP Tiered Storage Manager.
• You need cache enabled for external LUs.

4 External Storage XP panes
External Storage XP operations involve the LU Operation and Port Operation panes. In addition to these
two panes, the Flex Copy pane is available if you licensed Flex Copy XP. When you select a tab, the
corresponding pane appears.
Figure 27 Panes for External Storage XP operations

LU Operation pane
This pane appears when you start External Storage XP. Information about the external array appears on
the LU Operation pane. Use this pane to perform operations such as mapping external LUs and setting
alternate paths.
Device tree Device list Filter button
Preset list Information area

Operation information area Apply and Cancel buttons
Figure 28 LU Operation pane
• Device, WWN, and Port trees
Displays information in the Device, WWN, or Port list depending on the item selected in the tree.
Select the tab to display a tree. The following items can be selected in each tree:
• Items you can select in the Device tree include Subsystem (local XP), External Devices (arrays),
product names of connected external arrays, external LU group numbers, Discovery, and external
array WWNs. For more information, see ”Device tree” on page 57.
• Items you can select in the WWN tree include Subsystem, External Devices, product names of
connected external arrays, and external array WWNs. For more information, see ”WWN tree” on
page 60.
• Items you can select in the Port tree include Subsystem, External Devices, product names of
connected external arrays, and port numbers set to external ports. For more information, see ”Port
tree” on page 63.
• Filter button
Displays the Filter window, where you can restrict items displayed in the Device, WWN, and Port lists.
For more information, see ”Filter button” on page 66.
• Device, WWN, and Port lists
Displays information about the external array corresponding to the item selected in the Device, WWN,
or Port tree.
You can sort the list by displayed items. For example, to sort the list by LUN numbers, select LUN on
the list. For more information, see ”Device list” on page 58, ”WWN list” on page 61, and ”Port list”
on page 64.
• Information area
Displays information about the contents of the Device, WWN, or Port list, including:

• Total number of Devices: Number of external LUs that are connected.
• Total number of External Groups: Number of external LU groups that are set.
• Total number of External LUs: Number of external LUs that are connected.
• Found WWNs: WWNs found when you clicked Discovery in the Device tree.
• Remain LUs: Number of external LU numbers available (out of 15,360), other than those that have
already been used.
• WWN Entry: Number of LUs that are currently used in the external array out of the maximum
theoretically possible (15,360).
Displayed in the format The number of connected ports/16,384 (the number of ports which can be
connected).
• Total number of WWNs: Number of external array ports that are connected.
• Total number of Paths: Number of paths set between the local array and external array.
• Preset list
Displays the contents of settings that were set by operations started on the LU Operation pane.
Contents displayed in the Preset list have not yet been applied to the local array. They are applied
when you click Apply. For more information, see ”Preset list (LU Operation pane)” on page 66.
• Operation information area
Displays operation information about settings in the Preset list, including:
• Operation: Setting operation name.
• Number of Objects in Preset: Number of rows displayed in the Preset list.
• Apply button
Applies pending operations in the Preset list to the local array. When operations are applied
successfully, they are removed from the Preset list. Otherwise, error messages appear and error
settings remain in the Preset list.
• Cancel button
Cancels all settings in the Preset list.
Device tree
Displays information about the external array connected to the external port.
Figure 29 Device tree

The Device list (right pane) changes according to the item selected in the Device tree.
• Subsystem
When selected, displays nothing in the Device list and displays the External Devices branch of the tree.
Subsystem is selected when you start External Storage XP and display the Device tree.
• External Devices
When selected, the Device list displays information about external arrays connected to external ports
that have been detected (supported).
NOTE: Not all types of detected external arrays are supported.
• Product name of the connected external array

Displays the name of the external array that can be connected using External Storage XP in the tree
under External Devices. When you select an external array’s product name, the Device list displays
detailed product information.
• External LU group number
Displays user-assigned numbers in the branch under the external array’s product name, which is
connected to the local array and is already used. When you select an external LU group number, the
Device list displays information about external LUs registered in the selected group.
• Discovery
Appears in the branch under the product name of the external array connected to the local array.
When selected, External Storage XP searches for external array ports that can be connected, and
displays their WWNs.
• WWN of the external array
If you select the WWN found by selecting Discovery in the Device tree, the Device list displays
information about external LUs that can be connected from the port indicated by the WWN.
Device list
Displays information about external arrays corresponding to the item selected in the Device tree. You can
sort the list by displayed items. For example, to sort by LUN numbers, click LUN in the list.
When performing setting operations, the settings appear in the Preset list and the corresponding row in
the Device list appears in blue italics. For more information, see ”Preset list (LU Operation pane)” on
page 66.
Figure 30 Device list (external device selected in Device tree)

• Subsystem
Displays nothing. Subsystem is automatically selected when you select the Device tree.
• External Devices (for example, external storage group numbers currently defined for that external
device)
• Serial: Product serial number.
• Product: Product name.
• Vendor: Vendor name.
• Ex-Dev. Status: Status of the operation executed to the external array, or status of path connection.
External array’s status. Possible values: Normal, Unknown, Blockade, Warning, Checking, Cache
Destage, and Disconnect.
Table 8 External array status values
LU status Description
Normal LU status is normal.
Unknown LU status has yet to be ascertained.
Blockade I/O traffic to the LU is not permitted.

Table 8 External array status values (continued)
LU status Description
Warning FC path or paths have an abnormal status. Check the status of the paths.
Checking External Storage XP is verifying configuration information defined for FC paths.
Cache Destage External Storage XP is writing all data in the local array cache memory to the LU.
Disconnect Connection to external array or external LU was intentionally stopped using the
Disconnect Subsystem or Disconnect Volume command.
• LDEV Status: Mapped external LU’s status. Possible values: Normal, Unknown, Blockade, Warning,
and Format.
Table 9 Mapped external LU status values
LDEV status Description

Normal LDEV status is normal.
Unknown LDEV status has yet to be ascertained.
Blockade I/O traffic to the LDEV is not permitted.
Warning External LUs have abnormal status.
Format Volume is in the process of being formatted.

• ExG: External LU group number. This appears when you group the LUs from one or more external
arrays under a common number.
• Ex-Dev. Status: Status of the operation executed on the external array, or status of the path
connection. Possible values: Normal, Unknown, Blockade, Warning, Checking, Cache Destage,
and Disconnect. For a description of these values, see Table 8.
and Format. For a description of these values, see Table 9.
• External LU group number
• Characteristic: External LU’s identification number.
• Device: External LU’s device name.
• Capacity: External LU’s capacity in 512-byte blocks.
• Ex-Dev. info.: External array information. When the external array is an XP1024/XP128 or
TagmaStore Workgroup Modular Storage (WMS) array, an asterisk (*) appears.
• VMA: Information about the VMA setting by LUN Security XP Extension. When VMA is set for the
volume, an asterisk (*) appears.
• Alter. Path: Number of configured paths in the format The number of valid paths (the number of
primary alternate paths).
• IO Suppression: I/O Suppression mode: Enable or Disable. For more information, see ”External LU
attributes set by mapping” on page 20.
• Cache Mode: Cache mode: Enable or Disable. For more information, see ”External LU attributes set
by mapping” on page 20.
• Path: When paths are set, an asterisk (*) appears.
• Group: External LU group number and reference number assigned to each LU in the external LU
group. External Storage XP automatically assigns reference numbers to LUs in the group when
external LUs are mapped. This appears in the format “external LU group number - reference
number of the LU in the group”.

• Ex-Dev. Status: Status of the operation executed to the external array, or status of the path
connection. Possible values: Normal, Unknown, Blockade, Warning, Checking, Cache Destage,
and Disconnect. For a description of these values, see Table 8.
and Format. For a description of these values, see Table 9.
• Progress: When Status is Cache Destage, displays the destaging process progress, from 1% to
100%.
• Characteristic2: External LU’s extended identifying information. This information is used for
identifying logical volumes in the EVA array. For more information, see ”Identifying logical
volumes of EVA arrays (using Characteristic 2)” on page 138.
• Discovery
• WWN: World Wide Name identifying the port in the external array that can be set.
• LUN: LU number in the external array.
• Characteristic: External LU’s ID number.
• Device: External LU’s device name.
• Ex-Dev. info.: Information about the external array. When the external array is an SATA/FATA
drive, an asterisk (*) appears.
• VMA: Information about the VMA setting by LUN Security XP Extension. When VMA is set for the
volume, an asterisk (*) appears.
• Capacity: External LU’s capacity in blocks.
WWN tree
Displays information about items set in the Device tree. The contents of the WWN list changes depending
on the items selected in the WWN tree.
Figure 31 WWN tree

• Subsystem
When selected, displays nothing in the WWN tree. Subsystem is selected when you initially display
the WWN tree.
When selected, displays information about the external array connected to the external port in the
WWN list.
When selected, displays the name of the external array for which the connection setting is already
completed in the tree under External Devices.
When selected, displays WWNs identifying ports on the connected external array in the tree under
the name of the external array product.

WWN list
Displays information about the connection status of the local array and external array corresponding to
the item selected in the WWN tree. You can sort the list by displayed items. For example, to sort by the
LUN number, select LUN on the list.
When performing setting operations, the settings appear in the Preset list and the corresponding row in
the WWN list appears in blue italics. For more information, see ”Preset list (LU Operation pane)” on
page 66.
Figure 32 WWN list (External Devices selected in the WWN tree)

The contents displayed in the WWN list changes depending on the item selected in the WWN tree.
• Subsystem
When selected, displays nothing in the WWN tree. Subsystem is selected when you initially display
the WWN tree.
• Ex-Dev. Status: Status of the operation executed to the external array, or status of the path
connection. Possible values: Normal, Unknown, Blockade, Warning, Checking, Cache Destage, or
Disconnect. For a description of these values, see Table 8.
or Format. For a description of these values, see Table 9.
• WWN: WWN identifying the port in the external array for which the connection setting is
completed.
• Path: Number of set paths.
• I/O TOV: Value specified as the timeout for I/O to the external LU.
• Qdepth: Number of Read/Write commands that can be issued (queued) to the external LU at one
time.
• Path Watch: Time period beginning when the connection of all paths to the external LU are down
and ending when the external LU is blocked.
• Mode: How alternate paths between the local array and external array work. Alternate path
modes include:
• Single: Uses only the path with the highest priority (primary path) to execute I/O to the external
LU. When an error occurs in the primary path, the path with the second highest priority is used.
• Multi: Uses all set paths at the same time to execute I/Os to the external LU, distributing the
work load.
• Status: Status of the path set in the port identified by the WWN. The highest emergency level status
appears when two or more paths are set. Statuses include:
• Normal: Path is normal.
• Unknown: Path status is unknown.

• Blockade: Path is blocked.
• Disconnect: Connection to the external array or external LU was intentionally stopped using the
• Warning: There are paths whose status is not normal. Check the status of the paths.
• Checking: Process of checking the paths’ defined configuration informations is in progress.
• Port: Port number of the local array connected to the port identified by the WWN selected in the
Port tree. One of the following icons appears for each port:
Icon Description
Port in Standard mode.
Port in Initiator/External MIX mode
• WWN: WWN of the external array selected in the Port tree.

• LUN: External array’s LU number.
group. External Storage XP automatically assigns reference numbers to LUs in the group when the
external LUs are mapped. This is displayed in the format of “external LU group number - reference
number of volume in the group”.
• Status: Status of the path configured by the port of the local array and the port of the external array
identified by the WWN. One of the following statuses is displayed:
• External device setting changed: External array setting changed. For example, the path
definition was deleted, or the external array itself was replaced by another device.
• LDEV size reduced: External array’s volume capacity setting changed (volume capacity was
reduced).
• Not ready: External array replied NOTREADY.
• Illegal request: External array replied ILLEGALREQUEST.
• Command aborted: External array replied ABORTEDCOMMAND.
• Busy: External array is in BUSY status.
• LDEV reserved: External array is in Reserve status.
• Response error: External array is in blocked status caused by an abnormal reply (Response).
• Initiator port: External array’s port attribute changed to the initiator port.
• Unknown port: External array’s port attribute is unknown.
• Cannot detect port: Path was removed or external array’s port could not be found.
• Internal error: Program error occurred, or there is a logical contradiction.
• Timeout: Processing was retried because an abnormal reply (Response) was returned; however,
processing was stopped by a timeout.
• Standby: External array’s port is standing by. Port status is normal, but cannot receive I/O.
• Target error: Port failures, such as controller blockade, are detected on the external array side.
• Checking: Process of checking the paths’ defined configuration information is in progress.
• Unavailable: External array replied Unavailable. The external array demands to change the
connected port. Once the status becomes Unavailable, the primary path changes to the

alternate path that is in the Standby status. When the primary path changes, the status of the
path becomes Normal.
• Backoff: External array replied Backoff. The path status is waiting for recovery because a
temporary error occurred in the external array’s LU. Even if the primary path’s status becomes
Backoff, the primary path does not immediately change to the alternate path. After the error
recovery, the status becomes Normal. If the status cannot be recovered from the error, the path
status changes to the other status.
Port tree
When you select the Port tab, this tree displays information about ports that have the External attribute.
The contents displayed in the Port list changes depending on the item selected in the Port tree. For
instructions on setting the port attribute, see ”Setting a local array’s port attributes” on page 72.
Figure 33 Port tree

• Subsystem
When selected, displays nothing in the Port list. Subsystem is selected when you initially display the
Port tree.
• External
When selected, displays information about the port whose port attribute is set to External in the Port
list.
• Local array port number
When selected, displays connection information about the selected port in the Port list. One of the
following icons appears on the left of each port number:
Icon Description

Port list
Displays information about the ports and paths of the local array or external array, depending on the item
selected in the Port tree. You can sort the list by displayed items. For instance, to sort the items by the port
number, select Port on the list.
Figure 34 Port list (External selected in Port tree)

The displayed contents changes depending on the item selected in the Port tree.
• Subsystem
When selected, displays nothing in the Port tree. Subsystem is selected when you initially display the
Port tree.
• External
• Port: Port of the local array with the port attribute is set to External. One of the following icons
appears for each port:
Icon Description

• FLI_TOV: Wait time (in seconds) from the switch to FLOGI when the switch is connected. External
Storage XP automatically sets this value. You cannot change the value.
• PLI_TOV: Wait time (in seconds) of PLOGI to the external array when the switch is not connected.
External Storage XP automatically sets this value. You cannot change the value.
• Margin: Additional wait time (in seconds) to FLI_TOV (FLOGI wait time) or PLI_TOV (PLOGI wait
time). External Storage XP automatically sets this value. You cannot change the value. As a result,
the sum of the FLI_TOV time and margin time, or the sum of the PLI_TOV time and margin time is set
as a total wait time.
• Status: Status of the path set in the port identified by the WWN. The highest emergency level status
is displayed when two or more paths are set. One of the following statuses is displayed:
Disconnect Subsystem ore Disconnect Volume command.
• Warning: There are paths whose status is not normal. Check the status of the paths.
• Checking: Process of checking the defined configuration information of the paths is in progress.
• Port number of the local array

• Port: Port number of the local array selected in the Port tree. One of the following icons appears for
each port:
Icon Description
• WWN: WWN identifying the external array’s port. This port is connected to the local array port
selected in the Port tree.
• LUN: External array’s LU number.
group. External Storage XP automatically assigns the reference numbers to LUs in the group when
the external LUs are mapped. This is displayed in the format of “external LU group number -
reference number of volume in the group”.
• Status: Status of the path configured by the port of the local array and the port of the external array
identified by the WWN.
• External device setting changed: External array’s setting changed. For example, the path
definition was deleted or the external array itself was replaced by another device.
• LDEV size reduced: External array’s volume capacity changed (volume capacity was reduced).
• Busy: External array is in BUSY status.
• LDEV reserved: External array is in Reserve status.
• Response error: External array is in blocked status caused by an abnormal reply (Response).
• Initiator port: External array’s port attribute changed to the initiator port.
• Cannot detect port: Path was removed or external array’s port could not be found.
• Timeout: Processing was retried because an abnormal reply (Response) was returned; however,
processing was stopped by a timeout.
• Standby: External array’s port is standing by. The port status is normal, but cannot receive I/O.
• Target error: Port failures, such as controller blockade, are detected on the external array side.
• Checking: Process of checking the paths’ defined configuration information is in progress.
connected port. Once the status becomes Unavailable, the primary path changes to the
alternate path that is in the Standby status. When the primary path changes, the status of the
path becomes Normal.
• Backoff: External array replied Backoff. The path status is waiting for recovery because a
temporary error occurred in the external array’s volume. Even if the primary path’s status
becomes Backoff, the primary path does not changed to the alternate path immediately. After
the error recovery, the status becomes Normal. If the status cannot be recovered from the error,
the path status changes to the other status.

Filter button
Displays the Filter window where you can restrict LUs displayed in the Device list.
Figure 35 Filter window

This window contains Enable and Disable options that control the display of unsupported devices. When
you select Enable, information about unsupported arrays appears in the Device tree and Device list.
Unsupported arrays are indicated by Unknown Devices in the Device tree and Device list.
The Disable option is selected by default.
Preset list (LU Operation pane)

Displays rows from the Device list that are about to be acted upon. You can apply settings to the local array
after checking the contents in the Preset list. Information displayed in the Preset list appears in blue italics
in the Device list. If you click Apply in the LU Operation pane, settings displayed in the Preset list are
applied to the local array. At that point, the contents of the Preset list disappear and the Device list appears
normally.
If you click Cancel in the LU Operation pane, all settings in the Preset list are canceled.
If settings in the Preset list contain errors, they are not applied to the local array even if you click Apply. In
that case, error messages appear and incorrect settings appear in the Preset list. In addition, error codes
appear in the Preset list.
NOTE: Depending on the type of errors that occur, identical error codes might be displayed for all errors
listed in the Preset list. In this case, check the status of settings to identify the source of the error.
When you right-click an item in the Preset list, the following commands appear:
• Detail

Displays the Preset Detail window with detailed information about settings selected in the Preset list.
When an error code appears in the Preset list, a corresponding error message appears in this window.
Figure 36 Preset Detail window (mapping operation)

• Delete
Cancels settings selected in the Preset list.
Port Operation pane

Use this pane to check port settings and set port attributes. This section describes items displayed in the
Port Operation pane. For instructions, see ”Setting a local array’s port attributes” on page 72.
Port Operation tree Port Operation list
Preset list
Information area
Operation information area Apply and Cancel buttons
Figure 37 Port Operation pane

• Port Operation tree
Displays information about the selected port in the Port list (right pane). You can select Subsystem, a
port attribute, or a port number. For more information, see ”Port Operation tree” on page 68.

• Port Operation list
Displays detailed information about ports selected in the Port Operation tree. For more information,
see ”Port Operation list” on page 69.
• Information area
Displays the total number of ports currently displayed in the Port Operation list (Total Number of Ports).
• Preset List
Displays rows corresponding to the ports that are about to be acted upon. The contents displayed in
the Preset list have not been applied to the local array yet. When you click Apply on the Port
Operation pane, actions designated in the Preset list are applied to the local array. For more
information, see ”Preset list (Port Operation pane)” on page 70.
• Operation information area
Displays operation information about settings displayed in the Preset list.
• Operation: Setting operation name.
• Number of Objects in Preset: Number of settings displayed in the Preset list.
• Apply button
Applies actions designated in the Preset list to the local array. When actions are applied without
error, they are removed from the Preset list. If errors occur, actions are not applied, error messages
appear, and the actions remain in the Preset list.
• Cancel button
Cancels all settings in the Preset list.
Port Operation tree

Displays ports in the connected local array. Contents displayed in the Port Operation list (right pane)
varies according to the item selected in the Port Operation tree (left pane).
Figure 38 Port Operation tree

• Subsystem
When selected, displays nothing in the Port Operation list. Subsystem is selected when you initially
display the Port Operation pane.
• External
When selected, displays ports designated a external ports, which is the port attribute used for External
Storage XP. External ports do not have High Speed mode.
• Initiator
When selected, displays ports designated as an initiator (sending) port (used for Continuous Access
XP, TrueCopy for z/OS, Continuous Access XP Journal, Universal Replicator for z/OS, and so on).
• Target
When selected, displays ports designated as host target ports (used for host connect).
• RCU Target
When selected, displays ports designated as an RCU target (receiving) port (used for Continuous
Access XP, TrueCopy for z/OS, Continuous Access XP Journal, Universal Replicator for z/OS, and so
on).
• Initiator/External
When selected, displays ports for which the Initiator/External MIX mode is set.
• Port number

Displays ports assigned to each port attribute in the branch below each port attribute. External
Storage XP uses ports set to external. One of the following icons appears on the left of each port
number:
Icon Description
Port in High Speed mode.
Port Operation list

Displays ports in the local array that External Storage XP can use or set. The port information displayed
corresponds to the item selected in the Port tree.
You can sort the list by attribute. For example, to sort by port numbers, click Port on the list.
Rows corresponding to ports that are about to be acted upon appear in the Preset list, and the
corresponding row in the Port Operation list appears in blue italics.
Figure 39 Port Operation list

• Port
Port number. One of the following icons appears for each port:
Icon Description
Port in High Speed mode.
• Attribute
Port attribute. External ports are used for connecting to the external array. To set a remote command
device, you can use the port for which the Initiator/External MIX mode has been set.
• PCB Mode
Port’s PCB mode. Standard, High Speed, or MIX (for Initiator/External MIX mode) appears. External
ports do not have High Speed mode. For more information about the PCB mode, see the
XP12000/XP10000/SVS200. For more information about the Initiator/External MIX mode, see
”Using Continuous Access XP or Continuous Access XP Journal with remote command devices” on
page 117.
• FLI_TOV (Fabric Login Timeout Value)
Maximum time allowed (in seconds) for an external array to perform a fabric login after being
connected to a switch. This value is preset and cannot be changed.
• PLI_TOV (Port Login Timeout Value)
Maximum time allowed (in seconds) for the external array to perform a port login after being
connected. This value is preset and cannot be changed.
• Margin

The sum of the FLI_TOV and PLI_TOV values.
Preset list (Port Operation pane)

This list displays rows from the Port Operation list that are about to be acted on. Check the contents of the
Preset list before applying them to the local array. Contents displayed in the Preset list appear in blue
italics in the Port Operation list. When you click Apply in the Port Operation pane, actions designated in
the Preset list are applied to the local array and the contents of the Preset list disappear.
If you click Cancel in the Port Operation pane, all designated actions in the Preset list are canceled.
If settings in the Preset list contain errors, actions are not applied to the local array even if you click Apply.
In that case, error messages appear, incorrect settings appear in the Preset list, and error codes appear in
the Preset list.
When you right-click a setting in the Preset list, the following commands appear:
• Detail
Displays the Preset Detail window with detailed information about actions selected in the Preset list.
When an error code appears in the Preset list, a corresponding error message appears in the Preset
Detail window.
Figure 40 Preset Detail window (changing port attribute)

• Delete
Cancels actions selected in the Preset list.

5 Configuring external LUs
Use External Storage XP to perform operations to access external LUs, such as setting the port attribute to
the external port and mapping the external LU as the internal LDEV.
This chapter describes procedures for using External Storage XP to configure external LUs.
Overview of configuring external LUs

Figure 41 shows an example of using External Storage XP to configure external LUs.
Figure 41 Overview of configuring external LUs

The following is the general procedure for configuring external LUs.
1. Configure the port and system parameters for the external array. For instructions, see the external LU’s
documentation, ”Setting an external array’s port” on page 72, and ”Notes on connecting external
arrays” on page 127.
2. Start External Storage XP operations. 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.
3. Set the external array port attribute to External. For instructions, see ”Setting a local array’s port
attributes” on page 72.
4. Perform the Discovery operation.
In the Device tree on the LU Operation pane, select an external array, and select Discovery (see
”Mapping external LUs (Add LU)” on page 73).
NOTE: To perform Discovery operations, Command View XP or XP Remote Web Console must be
in Modify mode.
5. Display the LU Operation pane, right-click the external LU to be mapped as an internal LDEV in the
Device list, and select Add LU or Add LU (Auto). The Add LU or Auto Map Setting pane appears.

6. Use the Add LU or Auto Map Settings pane to map the external LU as an internal LDEV (”Mapping
external LUs (Add LU)” on page 73).
7. If you select a mainframe emulation type on the Add LU pane, use Volume Manager to reformat the
volume or perform the Write to Control Blocks operation. For instructions, (see the HP StorageWorks
8. Define alternate paths between the external array or mapped LU and the local array. For instructions,
see ”Defining alternate paths” on page 89.
9. Use LUN Manager to define paths. For instructions, see the HP StorageWorks LUN Configuration and
Security Manager XP user guide for the XP12000/XP10000/SVS200.
Setting an external array’s port

This section describes the procedure for setting the external array’s port. For more information, see the
external array’s documentation.
1. Set the topology information for the connection configuration.
2. Set the data transfer speed for the configuration.
3. Set the system parameters. For more information about system parameters for specific external arrays,
see ”Notes on connecting external arrays” on page 127.
4. Define the port’s LUN.
Setting a local array’s port attributes

The attribute of any port used for External Storage XP must be set to External.
NOTE: Only ports in SLPR0 can be set as external ports.
1. Select the Port Operation tab.

2. In the Port Operation list, select the port.
To set multiple ports at one time to External, select all the ports.
3. Right-click, and select Change to External.
In the Port Operation list, the selected port’s attribute changes to External, and the selected port’s row
appears in blue italics. Rows to be affected appear in the Preset list. To check setting details, right-click
the setting in the Preset list, and select Detail. To cancel settings, right-click the setting in the Preset list,
and select Delete.
4. Click Apply. A confirmation message appears.
5. Click OK. The port attribute setting is applied to the local array, and the new setting appears in the Port
Operation list.
If an error occurs, the failed setting and an error code appears in the Preset list. To view error
messages, right-click the failed row, and select Detail.
6. Set the topology for the connection configuration.
When an FC switch is connected, set Fabric to Enable. When a switch is not connected, set Fabric to
Disable, and specify FC-AL. Set Connection according to the actual connection configuration. For more
information about setting the topology, see the HP StorageWorks LUN Configuration and Security
Manager XP user guide for the XP12000/XP10000/SVS200.
7. Set the data transfer speed to Auto Negotiation.
NOTE: When connecting to a TagmaStore AMS or TagmaStore WMS subsystem, use LUN
Manager to set the data transfer speed of the XP12000/XP10000/SVS200 external port you use
to a fixed value other than Auto Negotiation. Also, set the data transfer speed of the target port of
the TagmaStore AMS or TagmaStore WMS subsystem to the same fixed value according to the
external port’s data transfer speed.

Mapping external LUs (Add LU)
After setting the port used for External Storage XP to External, map the external LU as an internal LDEV.
If you mapped the external LU and previously set the VMA of LUN Security XP Extension in that volume, the
former VMA setting is overwritten when you map the volume again. However, if LUN Security XP Extension
is not installed when you remap the volume, the volume with the VMA setting cannot be mapped.
Mapping external LUs individually (Add LU)

This section describes mapping operations starting with the Add LU command. Use the Add LU
(Figure 42), Select Paths (Figure 43), SSID (Figure 46), and Set SSID (Figure 47) panes for mapping
external LUs individually.
NOTE: Before mapping the external LU, ensure that no other applications (such as RAID Manager XP)
that use the command device are executing. Stop any applications that are executing.
CU list
CU:LDEV list LDEV map
Figure 42 Add LU window

• Vendor
External array’s vendor.
• Product
External array’s product name.
• Serial
External array’s product serial number.
• WWN
World Wide Name of the external array port used for connecting to the local array.
• LUN
LU number of the external LU.
• Device
External LU’s device name.
• Ex-Dev. info.
External array information. When the external array is an XP1024/XP128 or TagmaStore Workgroup
Modular Storage (WMS) array, an asterisk (*) appears.
• VMA

Information about the VMA setting of LUN Security XP Extension. If you mapped the external LU and
previously set the VMA of LUN Security XP Extension, an asterisk (*) appears. If LUN Security XP
Extension is not installed when you remap the volume, you cannot map the volume with the VMA
setting.
• Capacity
External LU’s capacity in blocks.
• Characteristic
External LU’s identification number.
• Characteristic2
External LU’s extended identifying information. This information is used for identifying logical volumes
in the EVA array. For more information, see ”Identifying logical volumes of EVA arrays (using
Characteristic 2)” on page 138.
• ExG (1-16384)
Group number of the connected external LUs. You can specify any decimal value from 1 to 16384. The
E displayed outside the text box is the capital letter of the external LU group.
• Emulation Type
Emulation type of the mapped external LU (from the XP12000/XP10000/SVS200 perspective) (see
”External LU attributes set by mapping” on page 20).
If you clear the Except OPEN-V check box, OPEN-V and available mainframe emulation types appear
in the list.
If you select the Except OPEN-V check box, open-system emulation types other than OPEN-V appear in
the list. To map the external LU as an open-system volume, define the emulation type to use for the
mapped LU as OPEN-V or another type. To map the external LU as an open-system volume using an
emulation type other than OPEN-V, select the Except OPEN-V check box.
If you plan to use the mapped external LU for a Flex Copy XP pair, you must select OPEN-V.
When the external LU to be mapped has the VMA setting, you must select OPEN-V.
• LDEV Capacity
Default capacity of the emulation type selected in the Emulation Type box. When the external LU’s
capacity is larger than the capacity displayed in LDEV Capacity, the external LU is divided into the
displayed capacity, and multiple LDEVs are created.
• LDEV
Number of LDEVs created at mapping. By default, the maximum number of LDEVs corresponding to the
capacity supported by the emulation type specified in the Emulation Type box appears. When the
external LU to be mapped has the VMA setting, you can select only 1.
• IO Suppression
Mapped external LU’s IO Suppression mode (for OPEN-V emulation only) (see ”External LU attributes
set by mapping” on page 20).
To suppress I/O operations from hosts (by way of the XP12000/XP10000/SVS200) to the mapped
external LU or use the mapped external LU for a Flex Copy pair, select Enable.
If you do not suppress I/O from hosts to the mapped external LU, select Disable (for example, for use
with External Storage XP).
If you set the emulation type to something other than OPEN-V, IO Suppression mode is automatically set
to Disable.
When the external LU to be mapped has the VMA setting, IO Suppression mode is automatically set to
Disable.
CAUTION: To use the mapped external LU for the software products other than Flex Copy XP (such
as Cache LUN XP, Auto LUN XP, Continuous Access XP, Continuous Access XP Journal Business
Copy XP, or Snapshot XP), set IO Suppression mode to Disable.

CAUTION: To set IO Suppression mode to Disable, External Storage XP must be installed.
CAUTION: To set IO Suppression mode to Enable, Flex Copy must be installed.
• Cache Mode
Specifies if the write I/O from the host is propagated synchronously or asynchronously to the external
storage device (see ”External LU attributes set by mapping” on page 20).
HP recommends that you set cache mode to Disable.
NOTE:
• If you set the IO Suppression mode to Enable, Cache Mode becomes Disable.
• If you select Disable, Cache LUN XP’s bind mode cannot be set.
• If you specified a mainframe-system emulation type for the mapped LU, host I/O is always
propagated asynchronously to the external LU regardless of the Cache Mode setting.
• Alternate Path
Number of alternate paths automatically set when mapped. Value can be from 0 to 7. Default is 1.
CAUTION: If the specified number of alternate paths cannot be set, an error appears in the Preset
list.
• CLPR (see ”External LU attributes set by mapping” on page 20)

When cache memory is partitioned using XP Disk/Cache Partition, you can select the CLPR used to
access the mapped volume from the list. The SLPR number that the selected CLPR belongs to appears on
the right of the list. However, if you select a mainframe emulation type in Emulation Type, you can only
select CLPRs belonging to SLPR number 0. The Limited check box appears on the right of the SLPR
number. To display only CUs defined for the selected SLPR, select the Limited check box. To display all
CUs, regardless of the SLPR, clear the check box. By default, the Limited check box is selected.
• Select Paths button
Displays the Select Paths pane (Figure 43). Use the Select Paths pane to select paths as candidates for
primary and alternate paths and select paths that cannot be set to primary and alternate paths. By
default, all paths with a confirmed connection status of normal are set as candidates for primary and
alternate paths. However, to set a specific path as the alternate path, use the Select Paths pane to
specify candidates for alternate paths. Alternate paths are automatically set from the candidates, as
many as the number set in Alternate Path.
CAUTION: If you do not set alternate paths on the Select Paths pane, alternate paths are
automatically set according to the WWN selected in the Device tree on the LU Operation pane
when you started the Add LU operation.
• Clear button
Resets all the external LU’s attributes.
• CU list
CU number of the local array to which you want to map the external LU. Select the CU number from the
list. When the Limited check box is selected, the selection range is limited to the CU belonging to the
SLPR displayed in CLPR.
• Linear button
Maps all external LUs listed in the CU:LDEV list at one time. When you click Linear and then select an
internal LDEV on the LDEV map, External Storage XP automatically selects from the LDEV map the same

number of internal LDEVs as external LUs listed in the CU:LDEV list, starting at the internal LDEV you
selected. The LDEV numbers of the selected internal LDEVs are sequential. When Interval is set,
mapping is done at the specified number of intervals. To map one external LU to another internal LDEV
after mapping the external LU automatically using the Linear button, release the Linear button, and map
the external LU individually.
• CU:LDEV list
Displays the XP12000/XP10000/SVS200 CU:LDEV numbers of external LUs mapped as internal
LDEVs. (N/A) (Not Assigned) means the external LUs are not yet mapped as internal LDEVs. To map an
external LU as an internal LDEV, select an external LU with (N/A) in the CU:LDEV list. To map all external
LUs in the CU:LDEV list at one time, use the Linear button.
• Interval
If you select two or more volumes in the CU:LDEV list or click Linear for mapping, you can select the
interval that arranges each volume. Values can be from 0 to 255. Default is 0.
For example, if you select three volumes in the CU:LEDV list, set Interval to 255, and map the first
volume to CU:LDEV number 00:01, the second and third volumes are mapped to 01:01 and 02:01,
respectively.
• LDEV map
Each cell in the map represents an internal LDEV. Select a cell for the internal LDEV on the map. The
selected cell turns blue, and the selected LDEV is mapped to the external LU. internal LDEVs that have
been mapped appear in gray, and those not yet mapped appear in white.
• Previous and Next buttons
If you select multiple external LUs in the Device list, click Previous to map the external LU in the row just
above the currently selected external LU. Click Next to map the external LU in the row just below the
currently selected external LU.
• OK button
Displays the SSID window, where you can continue with the next step of the mapping operation. If the
SSID setting is not necessary, the Add LU window closes, and the LU Operation pane appears.
The OK button is available when mapping on the Add LU window is complete.
• Cancel button
Cancels all mapping operations, closes the Add LU window, and returns to the LU Operation pane.
Select Paths pane
All paths that can be set as primary and alternate paths appear in the Select Paths pane. To set a specific
path as the alternate path, use the Select Paths pane to specify candidates for the alternate paths.
If you let alternate paths be automatically set with all connected normal paths as candidates, you can omit
the setting operation on the Select Paths pane.
Figure 43 Select Paths pane

• Port

Local array ports. You can set alternate paths for the selected port. One of the following icons appears
for each port:
Icon Description
• Selected Paths
External array port for which you can set the alternate path connecting to the local array port selected
in the Port list. By default, all ports that can be set as alternate paths appear. The WWN identifying
the external array port appears. If the primary path and as many alternate paths as you set in
Alternate Path in the Add LU pane cannot be set with the paths selected in Selected Paths, an error
occurs and appears in the Preset list.
• Unselected Paths
Ports excluded from being candidates for the ports setting the primary and alternate paths appear
among the external array ports that can be set as the primary and alternate paths. WWNs identifying
the external array ports appear in the list.
• Set button
If you select the port (external array WWN) you want to set as the candidate for the primary and
alternate paths in Unselected Paths, and click Set, the selected WWN moves to Selected Paths.
• Release button
If you select the port (external array WWN) you want to exclude from the list of candidates for the
primary and alternate paths in Selected Paths, and click Release, the selected WWN moves to
Unselected Paths.
• OK button
Saves settings in the Select Paths pane, and closes the pane.
• Cancel button
Cancels all settings in the Select Paths pane, and closes the pane.
To map an external LU as an internal LDEV individually:
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select Discovery. WWNs appear in the tree indicating external array ports that can
be connected.
3. In the Device tree, select the port (WWN) you want to connect from the WWNs listed in the Device.
External LUs that can be connected from the external array port (WWN) selected in the tree appear in
the Device list.
4. Right-click the external LU you want to map as an internal LDEV in the Device list, and select Add LU.
The Add LU window appears.
5. Select the internal LDEV that is mapped to the external LU selected in the Device list on the Add LU
window. Enter the following items in the Add LU window:
a. In the ExG box, select an external LU group number.
b. From the Emulation Type list, select an emulation type.
c. In the LDEV box, select the number of volumes to create.
d. Select the IO Suppression mode.
e. Select the Cache Mode.
f. In the Alternate Path box, select the number of alternate paths that are automatically set.
g. In the CLPR box, select the CLPR to be used. To limit the CU selection range, select the Limited check
box.
h. In the CU# list, select the CU number.

i. To map two or more external LU at the same time, select the interval that arranges each volume in
the Interval box.
j. Select one or more external LUs, and select one or more cells in the LDEV map.
When selecting two or more external LUs in the CU:LDEV list, if you select one cell of the internal
LDEV number in the LDEV map, the number of cells automatically selected is the same as the
number external LUs selected in the CU:LDEV list with the selected internal LDEV first. When Interval
is set, mapping is done at intervals of the specified number.
• To map all the external LUs displayed in the CU:LDEV list at one time:
Click Linear, and select an internal LDEV on the LDEV map. The same number of internal LDEVs
as the external LUs listed in the CU:LDEV list are automatically selected on the LDEV map
following the internal LDEV you selected (Figure 44). The LDEV numbers of the selected XP LDEV
are in a series. When Interval is set, the mapping is done at the specified interval.
Figure 44 Add LU pane (mapping using the Linear button)

• To map one external LU to another internal LDEV:

After automatically mapping the external LU using the Linear button, release the Linear button,
and map the external LU individually (Figure 45)
.
Figure 45 Add LU pane (mapping with the Linear button released

6. If you do not want to automatically set primary and alternate paths, but want to specify paths set as
candidates for primary and alternate paths, click Select Paths. The Select Paths pane appears.
To automatically set alternate paths, go to step 9.
7. Select the path and exclude it from the list of candidates for primary and alternate paths in the Select
Paths pane. For more information, see ”Select Paths pane” on page 76.
8. Click OK. The Add LU pane appears.
9. When all settings are complete on the Add LU window, click OK.
• If you need to set the SSID, the SSID window appears. Go to step 10.
Figure 46 SSID window

• If the SSID setting is not necessary, the Add LU window closes, and the LU Operation pane
appears. Settings appear in blue italics in the Device tree and Device list. Contents specified in the
Add LU window appear in the Preset list. To check setting details, right-click the setting in the Preset

list, and select Detail. To cancel settings, right-click the setting in the Preset list, and select Delete.
Go to step 13.
10.If you need to set an SSID to the mapped internal LDEV, the SSID pane appears. When storage is
partitioned using XP Disk/Cache Partition, select the SLPR number in the SLPR box. If you select the
Limited check box and select the SLPR number, you can set only SSIDs that can be used for the selected
the SLPR. If you do not select the Limited check box, you can set the SSID from all unused SSIDs
regardless of the selected SLPR number. Right-click the CU:LDEV number on the SSID pane, and select
Set SSID. The Set SSID window appears.
Figure 47 Set SSID window

11.Enter the SSID. If you selected the Limited check box on the SSID window, only SSIDs that can be used
in the SLPR selected on the SSID pane appear in the drop-down list. If you did not select the Limited
check box on the SSID pane, all unused SSIDs appear in the list, regardless of the selected SLPR. You
can enter 0x0004 to 0xFFFE as an SSID.
12.Click OK. The Set SSID window closes, and the LU Operation pane appears.
Settings appear in blue italics in the Device tree and Device list and also appear in the Preset list. To
check setting details, right-click the setting in the Preset list, and select Detail. To cancel settings,
right-click the setting in the Preset list, and select Delete.
13.Click Apply. A confirmation message appears.
If you already stopped the application, go to step 14. If you have not stopped the application, click
Cancel to close the message pane, stop the application, and retry the operation.
14.Click OK. A confirmation message appears.
15.Click OK. The mapping set in the Add LU window is applied to the local array, and the specified
contents appear in the Device list.
If errors occur during the external LU mapping operation, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
Mapping multiple external LUs at one time (Add LU (Auto))

This section describes the procedure to map multiple external LUs at one time. The procedure starts with the
Add LU (AUTO) command.
NOTE: Before mapping the external LU, you must check whether any application (for example, RAID
Manager XP) using the command device is in progress. If any application using the command device is in
progress, stop the application.
When mapping multiple external LUs at one time, the CU:LDEV numbers for the mapped destination
internal LDEVs are assigned in a series. When performing the mapping operation, you can select the first
CU:LDEV number for the mapped destination internal LDEVs. External Storage XP assigns the selected
CU:LDEV number as the first mapped destination LDEV, and as many subsequent CU:LDEV numbers are
kept for mapping as the number external LUs required to be mapped. To automatically perform the
mapping operation, you can let External Storage XP select the first CU:LDEV number.
NOTE: If you set Interval for the mapping, the CU:LDEV number of the internal LDEV that must be
mapped is set to the specified interval value.

CAUTION: If the LUs you are mapping include a volume with the VMA setting, you cannot use the Add LU
(AUTO) command to map them at one time.
Use the Auto Map Setting and Select LDEV windows (Figure 49) for mapping multiple external LUs at one
time.
Figure 48 Auto Map Setting window

• ExG (1-16384)
Group number containing the specified external LU. Specify any decimal value from 1 to 16384. The E
displayed outside of the text box is the capital letter of the external LU group.
• Emulation Type
Emulation type of the external LU from the perspective of the XP12000/XP10000/SVS200 (see
”External LU attributes set by mapping” on page 20).
If you clear the Except OPEN-V check box, OPEN-V and available mainframe emulation types appear
in the list.
If you select the Except OPEN-V check box, open-system emulation types other than OPEN-V also
appear in the list. To map the external LU as an open system LU, decide the mapped LU’s emulation
type, either OPEN-V or other than OPEN-V. To map the external LU as an open-system LU with an
emulation type other than OPEN-V, select the Except OPEN-V check box.
If you plan to use the mapped external LU for a Flex Copy XP pair, you must specify OPEN-V.
When the external LU to be mapped has the VMA setting, you must select OPEN-V.
Due to the advantages of the OPEN-V emulation type, HP recommends OPEN-V as the default type for
use with External Storage XP.
• Create LDEVs
Number of LDEVs that can be mapped based on the capacity supported by the emulation type
specified in the Emulation Type box. Select the number of LDEVs you want to map from the Create
LDEVs list. The default is Full. When Create LDEVs is Full, the maximum number of LDEVs that can be
created based on the capacity supported by the specified emulation type are mapped. The total
number of LDEVs being mapped appears at Total.
• IO Suppression
When you specify the OPEN-V emulation type, you can specify the mapped LU’s IO Suppression mode
(see ”External LU attributes set by mapping” on page 20).
If you suppress I/O operations from hosts (by way of the XP12000/XP10000/SVS200) to the mapped
external LU or use the mapped external LU for a Flex Copy XP pair, select Enable.
If you do not suppress I/O from hosts to the mapped external LU, select Disable (for example, for
External Storage XP).
When setting the emulation type to something other than OPEN-V, I/O Suppression mode is
automatically set to Disable.

When the external LU to be mapped has the VMA setting, IO Suppression mode is automatically set to
Disable.
CAUTION: To use the mapped external LU for products other than Flex Copy XP (such as Cache
LUN XP, Auto LUN XP, Continuous Access XP, Continuous Access XP Journal, and Business Copy
XP), set IO Suppression mode to Disable.
CAUTION: To set I/O Suppression mode to Disable, External Storage XP must be installed.
CAUTION: To set IO Suppression mode to Enable, Flex Copy XP must be installed.
• Cache Mode
Specifies if the write I/O from the host is propagated synchronously or asynchronously to the external
storage device (”External LU attributes set by mapping” on page 20).
To propagate write I/Os from the host to the external array asynchronously, select Enable.
To propagate write I/Os from the host to the external array synchronously, select Disable.
If you set IO Suppression mode to Enable, Cache Mode is automatically set to Disable.
CAUTION: If you set Disable, Cache LUN XP’s bind mode cannot be set.
CAUTION: If you set the mapped LU to a mainframe-system emulation type, the host I/O is always
propagated asynchronously to the external LU, regardless of the Cache Mode setting.
• Start CU:LDEV
First CU:LDEV number in the series of mapped destination internal LDEVs. The default is “- : -”. Interval
also appears. The default is 0.
To have External Storage XP select the first CU:LDEV number for the mapped internal LDEV, leave the
default (“- : -”). External Storage XP searches for an available CU:LDEV number starting with 00:00,
and selects the first one it finds.
To specify the first CU:LDEV number and interval, click Select LDEV. The Select LDEV window
(Figure 49) appears.
• Alternate Path
Number of alternate paths automatically set when mapped. Values can be from 0 to 7. Default is 1.
CAUTION: If the specified number of alternate paths cannot be set, an error appears in the Preset
list.
• CLPR (see ”External LU attributes set by mapping” on page 20)

When cache memory is partitioned using XP Disk/Cache Partition, you can select the CLPR used to
access the mapped LU from the list. The SLPR number that the selected CLPR belongs to appears on the
right of the list. However, when you select a mainframe emulation type in Emulation Type, you can only
select CLPRs belonging to SLPR number 0. The Limited check box appears on the right of the SLPR
number. To display only CUs defined for the selected SLPR, select the Limited check box. To display all
CUs, regardless of the SLPR, clear the check box. By default, the Limited check box is selected.
• Select LDEV button
Displays the Select LDEV window (Figure 49) where you can select the first CU:LDEV number in the
series.

• Select Paths button
Displays the Select Paths pane (Figure 43). Use the Select Paths pane to select paths as candidates for
primary and alternate paths and select paths not set to primary and alternate paths. By default, all
paths with a confirmed connection status of normal are set as candidates for primary and alternate
paths. However, to set a specific path as the alternate path, specify candidates for alternate paths on
the Select Paths pane. Alternate paths are automatically set from the candidates, as many as the
number set in Alternate Path.
See ”Mapping external LUs individually (Add LU)” on page 73 for more information about settings on
the Select Paths pane.
CAUTION: If you do not set alternate paths on the Select Paths pane, alternate paths are
automatically set according to the WWN selected in the Device tree on the LU Operation pane
when you start the Add LU operation.
• OK button
Starts mapping internal CU:LDEV numbers to external LUs. When mapping is complete, the SSID
window appears if the SSID setting is required. If the SSID setting is not required, the Auto Map Setting
window closes, and the LU Operation pane appears.
• Cancel button
Cancels all mapping operations, closes the Auto Map Setting window, and returns to the LU Operation
pane.
Select LDEV window
Figure 49 Select LDEV window

• CU list
CU number of the local array to which you want to map the external LU.
• Interval
Interval of the CU:LDEV number for mapping each volume. When two or more LDEVs are created from
one external LU and mapped, the CU:LDEV number is set at intervals specified in each created LDEV.
For example, set the interval as follows:
• In the Device list, select three external LUs.
• In Create LDEVs on the Auto Map Setting window, select 3 (nine LDEVs are created).
• In Interval, select 1.
• Set the starting CU:LDEV number to 00:00.

For this example, LDEVs created from the first external LU are mapped to 00:00, 00:02, and 00:04,
respectively. The starting CU:LDEV number of LDEVs created from the second external LU is 00:06, and
subsequent LDEVS are mapped to 00:08 and 00:0A. The starting CU:LDEV number of LDEVs created
from the third external LU is 00:0C, and subsequent LDEVs are mapped to 00:0E and 00:10.
• LDEV map
Each cell in the map represents an internal XP CU and LDEV number. Select a cell for the internal LDEV
on the map. The selected cell turns blue, and the LU of the selected cell becomes the first CU:LDEV
number of the mapped destination LUs. Defined (in use) internal LDEVs appear in gray, and internal
LDEVs to be mapped appear in white.
• Clear button
Releases the cell selected on the LDEV map.
• OK button
Closes the Select LDEV window, and returns to the Auto Map Setting window. On the Auto Map Setting
window, the CU:LDEV number you selected on the Select LDEV window as the head CU:LDEV number
of the mapped destination internal LDEVs appears in Start CU:LDEV.
• Cancel button
Cancels all settings in the Select LDEV window, and returns to the Auto Map Setting window.
To map multiple external LUs as internal LDEVs at one time:
2. In the Device tree, select Discovery. WWNs identifying the external array port that can be connected
appear in the tree.
3. In the Device tree, select the port (WWN) you want to connect from the WWNs displayed. External LUs
that can be connected from the port (WWN) selected in the tree appear in the Device list.
4. In the Device list, select the external LUs you want to map as internal LDEVs, right-click, and select Add
LU (Auto). The Auto Map Setting window (Figure 48) appears.
5. Set the attributes for the external LUs you selected on the Device list.
NOTE: Attributes for all LUs mapped at one time are identical.
• To select the first CU:LDEV number of the mapped destination internal LDEVs and the mapping
interval, go to step 6.
• To let External Storage XP select the first CU:LDEV number, go to step 9.
6. Click Select LDEV. The Select LDEV window appears.
7. Select the first CU:LDEV number of the mapped destination internal LDEVs and the mapping interval.
8. Click OK. The Auto Map Setting window appears.
9. If you do not want to automatically set the primary and alternate paths, but you want to specify the
paths to be set as candidates for the primary and alternate paths, click Select Paths. The Select Paths
window appears.
To automatically set alternate paths, go to step 12.
10.Select the path and exclude it from the list of the candidates for the primary and alternate paths. For
instructions, see ”Mapping external LUs individually (Add LU)” on page 73.
11.Click OK. The Auto Map Setting window appears.
12.Click OK. The Auto Map Setting window closes, and mapping the internal CU:LDEV numbers to the
external LUs starts.
NOTE: If the CU:LDEV numbers cannot be mapped properly because too many external LUs are
selected on the Device list, all processing is canceled and the message pane appears.
• After the CU:LDEV number mapping is complete, if the SSID setting is required, the SSID window
(Figure 46) appears. Go to step 13.

• If the SSID setting is not necessary, the LU Operation pane appears. Settings appear in blue italics
in the Device tree and Device list. The contents specified in the Auto Map Setting window appear in
the Preset list. To check setting details, right-click the setting in the Preset list, and select Detail. To
cancel settings, right-click the setting in the Preset list, and select Delete. Go to step 16.
13.If you need to set an SSID to the mapped internal LDEV, the SSID window appears. When storage is
partitioned using XP Disk/Cache Partition, select the SLPR number in the SLPR list. If you select the
Limited check box and select the SLPR number, only SSIDs that can be used for the selected SLPR can
be set. If you do not select the Limited check box, you can set the SSID from all of the unused SSIDs
regardless of the selected SLPR number. Right-click the CU:LDEV number on the SSID window, and
select Set SSID. The Set SSID window (Figure 47) appears.
14.Enter the SSID on the Set SSID window. If you selected the Limited check box on the SSID window, only
SSIDs that can be used in SLPR selected on the SSID window appear in the list. If you do not select the
Limited check box on the SSID window, all of the unused SSIDs appear in the list, regardless of the
selected SLPR. You can enter 0x0004 to 0xFFFE as an SSID.
15.Click OK. The Set SSID window closes, and the LU Operation pane appears.
Settings appear in blue italics in the Device tree and Device list. Settings appear in the Preset list. To
16.Click Apply. A confirmation message appears.
Cancel, stop the application, and retry the operation.
17. If you already stopped the application, click OK. A confirmation message appears.
18.Click OK. The mapping set in the Auto Map Setting window is applied to the local array, and the
specified contents appear in the Device list.
When an error occurs during the external LU mapping process, the failed setting and an error code
appears in the Preset list. To check the error message, right-click the failed setting, and select Detail.
Displaying detailed information stored in VMA (VMA information)

When VMA of LUN Security XP Extension is set for an external LU, you can check information stored in
the VMA before mapping the LU. Information stored in the VMA appears in the VMA Information pane
(Figure 50). To view the VMA Information pane, select WWN in the Device tree, and select the external
array’s port. Right-click the volume you want to display, and select VMA Information.
For more information about items displayed in the VMA Information pane, see the HP StorageWorks LUN
Security XP Extension user guide.
Figure 50 VMA Information pane

• Vendor

• Product
• LUN
LU number of the external LU.
• Attribute
Select from the following access attributes:
• Read/Write: Read and write operations can be performed on the volume.
• Read Only: Only read operations can be performed on the volume.
• Protect: You cannot access the volume. Read and write operations cannot be performed.
• S-Vol
Indicates whether or not the volume can be specified as an S-VOL: Enable or Disable.
• Reserved
Indicates whether RAID Manager XP and Command View XP or XP Remote Web Console can be used
to make LU path and command device settings.
• Hyphen (-): You can use RAID Manager XP and Command View XP or XP Remote Web Console to
make LU path and command device settings.
• RAID Manager: You can use RAID Manager XP to make LU path and command device settings, but
cannot use Command View XP or XP Remote Web Console.
• Retention Term
Period (in days) when you cannot change the Attribute field to Read/Write.
• Mode
Mode the RAID Manager XP user assigns to the logical volume.
• Zer: Zero Read Cap mode is assigned to the logical volume.
• Inv: Invisible mode is assigned to the logical volume.
• Zer/Inv: Zero Read Cap and Invisible mode are assigned to the logical volume.
• Hyphen (-): The RAID Manager XP user has not assigned a mode to the logical volume.
• Extent
Indicates whether extents are set.
• Asterisk (*): Extents are set.
• Hyphen (-): Extents are not set.
• Used Volumes
Licensed capacity for LUN Security XP Extension that the LU has used.
Setting alternate paths for external LUs

Before using an external LU mapped as an internal LDEV, you must set at least one alternate path from the
internal LDEV to the external LU (likely by way of an alternate controller). The number of alternate paths set
is the same as the number specified on the Add LU or Auto Map Setting window when the LU was mapped
as the internal LDEV. For more information, see ”Alternate paths” on page 22.
Use the Path Setting window (Figure 51) to add and define alternate paths to the paths set at mapping or
change the alternate paths.
NOTE: You can add or delete alternate paths by selecting multiple external LUs at one time. For more
information, see ”Adding alternate paths by selecting multiple external LUs (Add Paths)” on page 91 and
”Deleting alternate paths by selecting multiple external LUs (Delete Paths)” on page 93.
Use the Path Setting window (Figure 51) to define alternate paths.
You can perform the following operations on the Path Setting window:
• ”Defining alternate paths” on page 89

• ”Changing a defined alternate path priority” on page 89
• ”Canceling alternate path definitions” on page 91
• ”Changing alternate paths” on page 91
The Path Setting window displays information about external arrays and the condition of paths set from the
internal LDEV to the external LU.
Defined
paths
Available
paths
Figure 51 Path Setting window

• Vendor
• Product
• Serial
External array’s serial number.
• Group
External LU group and reference number of the external LU in the group.
• Characteristic
• Device
• Capacity
External LU’s capacity in blocks.
• Alternate Path List
Status of alternate paths. The Alternate Path list consists of two tables. The Configured Paths table
displays previously defined paths. The Available Paths table displays available paths. The Alternate
Path list displays the following information:

• Port: Port number in the local array connected to the external array. One of the following icons
appears for each port:
Icon Description
• WWN: External array port’s identification number.

• LUN: LU number of the external LU.
• Priority: Priority of paths connecting to the external LU. A 1 indicates the path with the highest
priority.
• Status: Status of the path to the external LU. For information about reacting to the displayed status,
see ”Troubleshooting External Storage XP” on page 121. Possible values:
• External device setting changed: External array’s setting changed. For example, the path
definition was deleted or the external array itself was replaced.
• LDEV size reduced: External array’s volume capacity setting changed (volume capacity was
reduced).
• Busy: External array status is BUSY.
• LDEV reserved: External array status is Reserve.
• Response error: External array status is blocked because of an abnormal reply (Response).
• Initiator port: External array’s port attribute changed to initiator port.
• RCU target port: External array’s port attribute changed to RCU target.
• Cannot detect port: Path was removed or external array port could not be found.
• Timeout: Processing was retried because of an abnormal reply, but a timeout occurred.
• Standby: External array’s port is standing by. Port status is normal, but cannot receive I/O.
• Target error: Port failures, such as controller blockade, were detected on the external array side.
• Checking: External Storage XP is checking defined path configuration information.
• Disconnect: Connection to the external array or LU was stopped using the Disconnect Subsystem
or Disconnect Volume command.
connected port. After the status becomes Unavailable, the primary path changes to the alternate
path that is in the Standby status. When the primary path changes, the path status becomes
Normal.
• Backoff: External array replied Backoff. The path status is Waiting for Recovery because a
temporary error occurred in the external array’s volume. Even if the primary path’s status
becomes Backoff, the primary path does not change to the alternate path immediately. After the
error recovery, the status becomes Normal. If you cannot recover the status from the error, the
path status changes to the other status.
• I/O TOV: Time over value for I/O to the external LU
• Qdepth: Number of Read/Write commands that can be issued (queued) to an external LU at one
time

• Path Watch: Time period beginning when the connection of all paths to the external LU is down and
ending when the external LU is blocked
• Mode: How the local array manages alternate paths when defined. Possible values:
• Single: Uses only the path with the highest priority (primary path) to execute I/Os to the external
LU. If selected, the second-highest priority alternate path is enabled only if a maintenance
operation or failure affecting the primary path occurs. That is, the external array contains
Active/Passive (for example, MSA) or Asymmetrical Active/Active controllers (for example,
Hitachi 9500V).
• Multi: Uses all of the set paths at the same time to execute I/Os to the external LU, distributing
the workload. That is, the external array contains Symmetrical Active/Active controllers (for
example, XP).
If you select multiple external LUs in the Device list, click Previous to change the Alternate Path list to the
external LU appearing just above the currently displayed LU. Click Next to change the Alternate Path
list to the external LU appearing just below the currently displayed LU.
• OK button
Closes the Path Setting window, and returns to the LU Operation pane. Contents specified in the Path
Setting window appear in blue italics in the Device list, and settings appear in the Preset list.
• Cancel button
Cancels all alternate path setting operations, closes the Path Setting window, and returns to the LU
Operation pane.
Defining alternate paths

Use the Path Setting window to define alternate paths.
2. In the Device tree, select the external LU group number. Information about the external LU mapped as
an internal LDEV appears in the Device list.
3. In the Device list, right-click the external LU, and select Path Setting. The Path Setting window appears.
The Configured Paths table displays detailed information about one currently defined path and the
alternate paths. The Available Paths table displays paths that can be set as alternate paths.
4. In the Available Paths table, right-click the row of the path to be defined as an alternate path, and
select Add.
The selected path is defined as an alternate path, and detailed information appears in the Configured
Paths table.
5. Click OK. The Path Setting window closes, and the LU Operation pane appears.
Selected rows appear in blue italics in the Device list. Specified contents also appear in the Preset list.
To check details on intended operations, right-click the setting in the Preset list, and select Detail. To
cancel settings, right-click the setting in the Preset list, and select Delete.
7. Click OK.
The alternate path defined in the Path Setting window is applied to the local array, and the specified
contents appear in the Device list.
If errors occur during alternate path operations, failed settings and error codes appear in the Preset list.
To check error messages, right-click the failed setting, and select Detail.
Changing a defined alternate path priority

To change the alternate path’s priority, use the Priority Up and Priority Down commands displayed in the
Path Setting window (Figure 52).
• Priority Up: Raises the priority of the path selected in the Alternate Path list.
• Priority Down: Lowers the priority of the path selected in the Alternate Path list.

As long as the external array uses Symmetrical Active/Active controllers (for example, XP), change an
alternate path to the currently used path by simply raising the priority of the alternate path or lowering the
priority of the currently used path.
NOTE: If the two paths connect to different controllers on the external array (for example, MSA), do not
use a path priority change to attempt to force a controller failover. Instead, use either a manual cable
disconnect or a Disconnect Paths GUI operation on the active controller WWN in the device list. In other
words, while the XP firmware may respond to a cable disconnect leading to the primary path and active
controller as a reason to activate the passive controller and path and continue I/Os, a simple change in
path priorities may not have the same effect, and I/Os may become blocked.

3. In the Device list, right-click the external LU, and select Path Setting. The Path Setting window
(Figure 51) appears.
4. Detailed information about the currently used path and alternate path appears in the Configured Paths
table, and paths that can be defined as alternate paths appear in the Available Paths table.
5. In the Configured Paths table, right-click the row of the path defined as the alternate path, and select
Priority Up (Figure 52). The row for the selected path switches with the row above it. The alternate
path’s priority is raised, and the path is set as the currently used path.
Figure 52 Path Setting window, shortcut menu

6. Repeat the Priority Up command until the row of the selected path is displayed on the first line of the
Configured Path list and that row’s Priority column changes to 1.
When the Priority column changes to 1, the path is set as the typically used one (primary path).
Selected rows appear in blue italics in the Device list. Specified contents appear in the Preset list. To
check details on intended operations, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.

9. Click OK. The change in the alternate path defined in the Path Setting window is applied to the local
array, and specified contents appear in the Device list.
If errors occur during alternate path operations, failed settings and error codes appear in the Preset list.
Canceling alternate path definitions

Use the Path Setting pane to cancel an alternate path definition.
1. Follow step 1 to step 3 in ”Defining alternate paths” on page 89.
2. In the Configured Paths table, right-click the row of the alternate path, and select Delete.
The selected alternate path’s definition is canceled, and detailed information about the path is deleted
from the Configured Paths table.
Changing alternate paths

To change an alternate path, cancel the current alternate path, and then define another path as a new
alternate path.
2. In the Configured Paths table, right-click the row of the path currently defined as the alternate path, and
select Delete.
The selected alternate path’s definition is canceled, and detailed information about the path is deleted
from the Configured Paths table.
3. In the Available Paths table, right-click the row of the path to be defined as the new alternate path, and
select Add.
The specified alternate path is defined, and detailed information about the path is displayed in the
Configured Paths table.
Adding alternate paths by selecting multiple external LUs (Add Paths)

To add paths other than the alternate paths you set when you mapped the volume, add paths at one time
by selecting multiple external LUs belonging to the same external LU group. To do this, set the alternate
path in the Add Paths window (Figure 53), check the setting in the Path Setting window (Figure 51), and
apply the setting to the array.
CAUTION: After adding paths using the Add Paths window, you can change the path setting for each
external LU in the Path Setting window. However, you cannot delete all current paths to completely
interchange them with the newly added paths. At least one current path setting must remain, even if you
added new paths using the Add Paths window.

NOTE: Use the Add Paths window to add paths to multiple external LUs at one time. However, path
settings might not be applied because of the current path setting of each volume. After setting paths in the
Add Paths window, check whether or not the new path settings can be applied in the Path Setting window
for each external LU. If the setting cannot be applied, the setting from the Add Paths window does not
appear on the Path Setting window. The setting from the Add Paths window also does not appear in the
Preset list or in the LU Operation pane.
Figure 53 Add Paths window

• Port
Local array ports. After selecting a port, you can add paths. One of the following icons appears for
each port:
Icon Description
• Selected Paths
Paths that are added as ports that configure alternate paths. WWNs identify ports on the external
array. Nothing is displayed when you initially access the Add Paths window.
External array ports (WWNs) that can configure the path connecting with the local array port selected
in the Port list. Select WWNs from this list to add as alternate paths.
• Set
Moves WWNs selected in Unselected Paths to Selected Paths.
• Release
Moves WWNs selected in Selected Paths to Unselected Paths.
• OK
Saves settings in the Add Paths window, closes the Add Paths window, and displays the Path Setting
window.
• Cancel
Cancels all settings in the Add Paths window, and closes the window.
To add alternate paths to multiple external LUs at one time:
2. In the Device tree, select an external LU group number. Information about external LUs mapped as
internal LDEVs appears in the Device list.
3. In the Device list, select multiple external LUs, right-click, and select Add Paths. The Add Paths window
appears.

4. In the Port list, select the local array port. External array ports (WWNs) that can configure the path
connecting with the selected local array port appear in Unselected Paths.
5. In the Unselected Paths list, select the port’s WWNs, and click Set. The selected WWNs move to
Selected Paths.
6. Click OK. The Path Setting window appears.
7. Ensure that added paths are applied to the array in the Path Setting window. You can also change the
alternate path setting in this window. For more information, see ”Setting alternate paths for external
LUs” on page 86.
Selected rows in the Device list appear in blue italics. Specified settings appear in the Preset list. To
10.Click OK. Alternative paths added using the Add Paths and Path Setting windows are applied to the
array, and the specified content appears in the Device list.
If errors occur during alternate path definition, failed settings and error codes appear in the Preset list.
Deleting alternate paths by selecting multiple external LUs (Delete Paths)

You can delete paths for multiple volumes that belong to the same external LU group at one time. To delete
alternate paths for multiple external LUs at one time, select the alternate path in the Delete Paths window,
check the setting in the Path Setting window, and apply the setting to the array.
CAUTION: At least one normal path must be set on each mapped external LU.
NOTE: Use the Delete Paths window to delete paths to multiple external LUs at one time. However, the
deleted path settings might not be applied because of the current path setting of each volume. After you set
the deletion in the Delete Paths window, check whether or not the new path settings can be applied in the
Path Setting window for each external LU. If the setting cannot be applied, the setting from the Delete Paths
window does not appear on the Path Setting window. The setting from the Delete Paths window also does
not appear in the Preset list or in the LU Operation pane.
Figure 54 Delete Paths window

• Port

Local array ports. After selecting a port, you can add the paths. One of the following icons appears for
each port:
Icon Description
• Selected Paths
Paths of WWNs to be deleted. WWNs identify ports on the external array. Nothing is displayed when
you first access the Delete Paths window.
Ports (WWNs) on the external array that have paths configured for connecting with the local array port
selected in the Port list. Select WWNs from this list to delete paths.
• Set
Moves WWNs selected in Unselected Paths to Selected Paths.
• Release
Moves WWNs selected in Selected Paths to Unselected Paths.
• OK
Saves settings in the Delete Paths window, closes the Delete Paths window, and displays the Path
Setting window.
• Cancel
Cancels all of the settings in the Delete Paths window, and closes the window.
To delete paths for multiple volumes at one time:
2. In the Device tree, select an external LU group number. Information about external LUs mapped as
internal LDEVs appears in the Device list.
3. In the Device list, select multiple external LUs, right-click, and select Delete Paths. The Delete Paths
window (Figure 54) appears.
4. In the Port list, select the local array port. External array ports (WWNs) that have been configured with
paths connecting to the local array port appear in the Unselected Paths list.
5. In the Unselected Paths list, select ports (WWNs of the external array), and click Set. The selected ports
move to the Selected Paths list.
6. Click OK. The Path Setting window appears.
7. Ensure that deleted paths are applied to the array in the Path Setting window. You can also change the
alternate path setting in this window. For more information, see ”Setting alternate paths for external
LUs” on page 86.
Selected rows in the Device list appear in blue italics. Specified settings appear in the Preset list. To
10.Click OK.
Alternative paths deleted using the Delete Paths and Path Setting window are applied to the array, and
the specified content appears in the Device list.
If errors occur during alternate path definition, failed settings and error codes appear in the Preset list.

Checking an external LU’s status (LDEV Information)
After mapping an external LU as a local array internal LDEV, the external LU is available for operations in
External Storage XP, Flex Copy, and other HP StorageWorks products that support mapped external LUs.
Use the LDEV Information window (Figure 55) to check the status of mapped external LUs.
When a failure occurs in the path between the local array and external array, and also in the specified
alternate paths, the local array recognizes the external LU as blocked (Blockade). To restore the blocked
volume, execute the Restore command on the LDEV Information window.
Obtaining information about external LUs

The LDEV Information window displays information about external arrays and external LUs mapped as
internal LDEVs. To display this window, select the external LU group number in the Device list, right-click
the LU you want to display in the Device list, and select LDEV Information.
LDEV List
Figure 55 LDEV Information window

• Vendor
• Product
• Serial
External array’s product serial number.
• Group
External LU group and reference number of the external LU in the group.
• Characteristic
• Device
• Capacity
External LU’s capacity. When the mapped external LU’s emulation type is for open systems, capacity is
displayed in 512-byte blocks. When the mapped external LU’s emulation type is for mainframe
systems, capacity is displayed in cylinders.

NOTE: When you use the Custom Volume Size (CVS) function to make an S-VOL for a Flex Copy
XP copy pair that has the same capacity as the P-VOL, set the S-VOL’s capacity in blocks or
cylinders according to the emulation type.
• LDEV List
The status of external LU mapped as internal LDEV. The following information appears:
• CU:LDEV: CU:LDEV number of the internal LDEV to which the external LU is mapped.
• Emulation Type: External LU’s emulation type set when it was mapped.
• Capacity: External LU’s capacity.
• Status: External LU’s status. Possible values: Normal, Unknown, Blockade, Warning, and Format.
Warning indicates that some alternate paths are blocked. Format indicates the external LU is
currently being formatted.
• View all LUs
Displays information about all external LUs in the LDEV list.
• View all Volumes
When the external LU is part of a LUSE volume, displays all LDEVs that make up the LUSE volume in the
LDEV list. However, LDEVs in other external LUs are not displayed, even though those LDEVs might be
part of the LUSE volume. To check all LDEVs configuring a LUSE volume, use the Volume Detail
command (”Displaying configuration information for external LUs (Volume Detail)” on page 97).
If you select multiple external LUs in the Device list in the LU Operation pane, click Previous to change
the LDEV list to the external LU appearing just above the currently displayed LU. Click Next to change
the LDEV list to the external LU appearing just below the currently displayed LU.
• OK button
Closes the LDEV Information window, and returns to the LU Operation pane. Contents specified in the
LDEV Information window appear in blue italics in the Device list, and settings appear in the Preset list.
• Cancel button
Cancels all setting operations, closes the LDEV Information window, and returns to the LU Operation
pane.
Restoring external LUs (Restore)

Use the Restore command to restore the status of external LUs.
When errors occur in all paths between the local array and external array, the local array changes the
status of the external LU to Blockade. In this case, see ”Troubleshooting External Storage XP” on
page 121 and restore the path to the external array according to the troubleshooting instructions. Then
execute the Check Paths & Restore Vol. command to make the external LU in Blockade status usable. If the
external LU’s status remains Blockade, even though you restored the path to the external array and
executed the Check Paths & Restore Vol. command, execute the Restore command from the LDEV
Information window.
NOTE: If paths between the local array and external array are not restored, the external LU cannot be
restored to a usable status, even though you execute the Restore command.
NOTE: If you set a mainframe-system emulation type (such as 3390-3) when you mapped the external LU,
and you restore the mapped LU without formatting the LU or performing the Write to Control Blocks
operation, data in the volume cannot be read correctly.

3. In the Device list, right-click the external LU you want to restore, and select LDEV Information. The LDEV
Information window appears. The LDEV list displays information about the external LU selected in the
Device list on the LU Operation pane.
4. Select View all LUs.
5. In the LDEV list, right-click the row of the external LU to be restored, and select Restore.
Figure 56 Shortcut menu of the LDEV Information window

The Status column in the selected external LU row changes to Restore.
6. Click OK. The LDEV Information window closes, and the LU Operation pane appears.
Specified contents appear in blue italics in the Device list and appear in the Preset list. To check setting
details, right-click the setting in the Preset list, and select Detail. To cancel settings, right-click the setting
in the Preset list, and select Delete.
8. Click OK.
The status of the external LU set in the LDEV Information window changes to Restore (restored), and the
external LU can be used in Command View XP or XP Remote Web Console.
If errors occur when changing the external LU’s status, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
Displaying configuration information for external LUs (Volume Detail)

To display the Volume Detail window, right-click a row with an external LU from the LDEV list in the LDEV
Information window, and select Volume Detail (Figure 56). If you select an external LU that is a LUSE

volume in the LDEV list, the Volume Detail window displays a list of all LDEVs that make up the LUSE
volume.
Figure 57 Volume Detail window

You can also check the LDEVs making up a LUSE volume by selecting View all Volumes at the bottom of the
LDEV Information window. However, only LDEVs in the specified external LU appear. The Volume Detail
window displays all LDEVs, including LDEVs of other external LUs.
The Volume Detail command is available after you restore the external LU using the Restore command.
Disconnecting external arrays or LUs

Use the Disconnect Subsystem and Disconnect Volume commands to disconnect external LUs. This is
necessary, for example, before turning off the power on local arrays or external arrays for maintenance or
before deleting an external LU’s mapping.
The Disconnect Subsystem or Disconnect Volume command stops all host I/O to the mapped external LU,
and writes all data in the XP12000/XP10000/SVS200 cache memory to the external LU (all data is
destaged).
Mapping settings are preserved, even though the external LU is disconnected using the Disconnect
Subsystem or Disconnect Volume command. Therefore, you can resume using the external LU as a mapped
volume with the former settings. For instructions, see ”Checking the connection status and resuming
external LU operations (Check Paths & Restore Vol.)” on page 100.
CAUTION: Note the following for the Disconnect Subsystem and Disconnect Volume commands:
• After executing the Disconnect Subsystem or Disconnect Volume command, click the Refresh button ( )
on the Command View XP or XP Remote Web Console main pane to update the information, and
check the current progress status.
• If you execute the Disconnect Subsystem or Disconnect Volume command when I/Os from an
open-system host are in progress, host I/Os to the specified volume are forcibly stopped. When
executing the Disconnect Subsystem or Disconnect Volume command, stop host I/Os, and unmount the
volume from the host.
• If the volume is online from the mainframe host, you cannot execute the Disconnect Subsystem or
Disconnect Volume command. Stop host I/Os to the volume, and perform the Vary Offline operation.
include LDEVs that are set as the copy pair for Flex Copy XP, Business Copy XP, ShadowImage for
z/OS, Continuous Access XP Journal, Universal Replicator for z/OS, Continuous Access XP, TrueCopy
for z/OS, or Snapshot XP. However, if the copy pair status is PSUE, you can execute these commands.
When the external LU is set as a pool volume (pool-VOL) and the Snapshot XP pair’s status is PAIR, you
can execute these commands.

• You cannot execute the Disconnect Subsystem ore Disconnect Volume command for external LUs that
include LDEVs for which Auto LUN XP’s migration processing is in progress.
• When executing the Disconnect Subsystem or Disconnect Volume command, the Ex-Dev. Status column
in the Device list changes to Cache Destage. Even if there is no data left in cache memory, the
displayed status remains as Cache Destage, until the Disconnect Subsystem or Disconnect Volume
command processing is complete.
• When the Disconnect Subsystem or Disconnect Volume command is executed and all data in cache
memory is written to the external LU, the Ex-Dev. Status column in the Device list changes to Disconnect.
Disconnecting all external LUs in an external array (Disconnect Subsystem)

1. In the LU Operation pane, select External Devices in the Device tree. Connected external arrays appear
in the Device list.
2. In the Device list, right-click the external array you want to disconnect from the local array, and select
Disconnect Subsystem.
Figure 58 Disconnect Subsystem and Check Paths & Restore Vol. Commands
The selected external array appears in blue italics in the LU list and Device list, and appears in the
Preset list. To check details of the intended operations, right-click the setting in the Preset list, and select
Detail. To cancel settings, right-click the setting in the Preset list, and select Delete.
4. Click OK.
The Ex-Dev. Status column in the Device list changes to Cache Destaging. When External Storage XP
finishes writing data from cache to the external LU, the Ex-Dev. Status column changes to Disconnect.
If errors occur during disconnect operations, failed settings and error codes appear in the Preset list. To
check error messages, right-click the failed setting, and select Detail.
CAUTION: To access the external array after executing the Disconnect Subsystem command, you must
execute the Check Paths & Restore Vol. command.

Disconnecting external LUs individually (Disconnect Volume)
1. In the LU Operation pane, select an external LU group number in the Device tree. Information about
external LUs in the selected external LU group appears in the Device list.
2. In the Device list, right-click the external LU you want to disconnect from the local array, and select
Disconnect Volume. The selected external LU group number in the Device tree and the selected external
LU in the Device list appear in blue italics. It also appears in the Preset list.
To check details of the intended operation, right-click the row in the Preset list, and select Detail. To
cancel settings, right-click the row in the Preset list, and select Delete.
4. Click OK. The Ex-Dev.Status column in the Device list changes to Cache Destaging. When External
Storage XP finishes writing data from cache to the external LU, the Ex-Dev. Status column changes to
Disconnect.
If errors occur during disconnect operations, failed operations and error codes appear in the Preset list.
To check error messages, right-click the failed operation row, and select Detail.
CAUTION: To access the external LU after executing the Disconnect Subsystem command, you must
execute the Check Paths & Restore Vol. command.
Checking the connection status and resuming external LU operations

(Check Paths & Restore Vol.)
When errors occur in the path between the local array and external array, and also in all alternate paths,
the local array changes the external LU’s status to Blockade. In this case, see ”Troubleshooting External
Storage XP” on page 121 and restore the path to the external array according to the troubleshooting
procedure. Execute the Check Paths & Restore Vol. command to make the external LU in Blockade status
usable.
When executing the Check Paths & Restore Vol. command for the disconnected external LU for which
mapping settings are preserved, the defined mapping setting and the external LU’s current status are
compared and checked to see if the settings match the actual status. The path status and all other mapping
configuration definitions are checked. If the external LU can be resumed as a mapped volume as a result of
the checking processing, the volume status is set to be available for I/O operations.
Use the Check Paths & Restore Vol. command to resume using an external LU that has been disconnected
using the Disconnect Subsystem or Disconnect Volume command.
CAUTION: After executing the Check Paths & Restore Vol. command, click the Refresh button ( ) on the
Command View XP or XP Remote Web Console main pane to update the information, and check the
current progress status.
NOTE: If you execute the Check Paths & Restore Vol. command and the external LU is ready to be
restored as the mapped LU, the external LU is set to accept I/Os and you can resume using the external LU
as a mapped LU. However, if the external LU is not ready to be resumed, the status of the disconnected
volume remains Blockade.
Restoring all external LUs in an external array (Check Paths & Restore Vol.)
1. In the LU Operation pane, select External Devices in the Device tree. Physically connected external
arrays appear in the Device list.
2. In the Device list, right-click the external array you want to restore the connection to the local array, and
select Check Paths & Restore Vol. The selected external array appears in blue italics in the LU list and
Device list. It also appears in the Preset list.

To check setting details, right-click the setting in the Preset list, and select Detail. To cancel settings,
4. Click OK.
The path status in the Path Setting pane changes to Checking. When External Storage XP finishes
checking path status and the external array can be restored, the Status column changes to Normal. If
the external array cannot be restored, the status changes to Blockade.
Restoring external LUs individually (Check Paths & Restore Vol.)

1. In the LU Operation pane, select an external LU group number in the Device tree. Information about
external LUs in the selected external LU group appears in the Device list.
2. In the Device list, right-click the external LU you want to resume the connection to the local array, and
select Check Paths & Restore Vol.
The selected external group number in the Device tree and the selected external LU in the Device list
appear in blue italics. Rows with operations to be performed on appear in the Preset list. To check
setting details, right-click the setting in the Preset list, and select Detail. To cancel settings, right-click the
setting in the Preset list, and select Delete.
4. Click OK.
The path status displayed in the Path Setting pane changes to Checking. When External Storage XP
finishes checking path status and the external LU can be restored, the Status column changes to
Normal. If the external array cannot be restored, the status changes to Blockade.
Restoring external LUs (LDEV Restore)

The external LU’s status might be blocked (Blockade) if errors occur during the setting operation or the
volume-formatting process fails. In this case, see ”Troubleshooting External Storage XP” on page 121 and
restore the path to the external array according to the troubleshooting procedure. Then execute the Check
Paths & Restore Vol. command to make the external LU in Blockade status usable. If the external LU’s status
remains Blockade, even though you restored the path to the external array and executed the Check Paths &
Restore Vol. command, execute the LDEV Restore command to restore the volume.
NOTE: If the path between the local array and external array is not restored, you cannot restore the
external array’s status to be usable, even though you execute the LDEV Restore command.
NOTE: You can also restore the external LU by executing the Restore command on the LDEV Information
window. For more information, see ”Restoring external LUs (Restore)” on page 96.
Restoring volumes in an external array

1. In the LU Operation pane, select External Devices in the Device tree. Connected external arrays appear
in the Device list.
2. In the Device list, right-click the external array you want to restore all volumes in, and select LDEV
Restore.
The selected external array appears in blue italics in the Device tree and Device list. The contents of the
setting appears in the Preset list. To check setting details, right-click the setting in the Preset list, and
select Detail. To cancel the setting, right-click the setting in the Preset list, and select Delete.
4. Click OK.
For the external LUs of the selected external array, the Status column of the Device list changes to the
restored status, and the external LU can be used in Command View XP or XP Remote Web Console.
When errors occur during a status change for the external LU, the failed setting and error code appears
in the Preset list. To check the error message, right-click the failed setting, and select Detail.

Restoring volumes in a mapped external LU individually
1. In LU Operation pane, select an external LU group number in the Device tree. Information about the
external LUs in the selected external LU group appear in the Device list.
2. In the Device list, right-click the external LU you want to restore, and select LDEV Restore.
The selected external LU group number and external LU appear in blue italics in the Device tree and
Device list. The contents of the setting appears in the Preset list. To check setting details, right-click the
setting in the Preset list, and select Detail. To cancel the setting, right-click the setting in the Preset list,
and select Delete.
4. Click OK.
For the external LUs of the selected external array, the Status column of the Device list changes to the
restored status, and the external LU can be used in the Command View XP or XP Remote Web Console.
When errors occur during the status change for the external LU, the failed setting and error code
appears in the Preset list. To check the error message, right-click the failed setting, and select Detail.
Stopping the use of paths to an external LU by specifying an external

array’s WWN (Disconnect Paths)
To stop using the path between the local array and the external array by specifying the WWN that
identifies the external array’s port, select the WWN tree to display the WWN list.
NOTE: The Disconnect Paths command is not for the actual disconnection of the path to the external LU.
You must confirm that some normal paths to the external LU are set, other than the path for which you plan
to execute the Disconnect Paths command.
1. In the LU Operation pane, select the WWN tab. The WWN tree and WWN list appear.
2. In the WWN tree, select the product name of the connected external array. The WWN of all ports that
are connected to the local array and are used appear in the WWN list.
3. In the WWN list, select WWN you want to stop using. When you select the WWN identifying the
external array’s port in the list, you can stop the use of all ports of the local array connected to the port
at one time.
4. Right-click, and select Disconnect Paths. Selected items appear in blue italics in the WWN tree and
WWN list. The contents of the setting appears in the Preset list.
To check the setting details, right-click the setting in the Preset list, and select Detail. To cancel the
setting, right-click the setting in the Preset list, and select Delete.
6. Click OK.
Restoring paths to an external LU by specifying an external array’s

WWN (Check Paths)
To restore the path between the local array and external array by specifying the WWN that identifies the
external array’s port, select the WWN tree to display the WWN list.
NOTE: The path must be in a status that can be restored.
2. In the WWN tree, select the product name of the connected external array or the WWN identifying the
external array’s port.
• If you select the product name of the connected external array, all WWNs that are connected to the
local array and are used appear in the WWN list.

• If you select the external array’s WWN, connection information about the paths between the
selected WWN and local array ports appear in the WWN list.
3. In the WWN list, select the WWN for which you want to restore the path.
• If you selected the product name of the connected external array in the WWN tree, select the
WWN identifying the external array’s port in the WWN list. In this case, you can restore the path of
all ports of the local array connected to the WWN at one time.
• If you selected the external array’s WWN in the WWN tree, select the path between the selected
WWN and the port of the local array. In this case, you can restore the selected path to the port of
the local array individually.
4. Right click, and select Check Paths. Selected items appear in blue italics in the WWN tree and WWN
list. The contents of the setting appears in the Preset list.
6. Click OK.
Changing an external array’s port setting

You can change the setting of an external array’s port by specifying the WWN that identifies the external
array’s port in the WWN list. Use the Change Parameter pane (Figure 59) to change the port setting.
Figure 59 Change Parameter pane

• IO TOV (10-240): Timeout value for the I/O to the external LU. The value can be 10 to 240 (in second).
• QDepth (8-128): Number of Read/Write commands that can be issued (queued) to the external LU at
one time. The value can be from 8 to 128.
• Path Blockade Watch (10-180): Time period beginning when the connection of all paths to the external
LU is down and ending when the external LU is blocked. Commands from the host are accepted until
the time set for this parameter has passed. After the time has passed, the path status becomes
Blockade. The value can be from 10 to 180 (seconds).
CAUTION: If there is no problem with the default setting, use the default setting.
CAUTION: For the external LU used for typical I/O, set IO TOV to 15 seconds.
CAUTION: To change the setting, match the value to the recommended value for the external array.
To change the setting of the port identified by the WWN by specifying an external array’s WWN:
2. In the WWN tree, select the product name of the connected external array identifying the external
array’s port. The WWNs of all the ports that are connected to the local array and are used appear in
the WWN list.
3. In the WWN list, select the port for which you want to restore the path.

4. Right click, and select Change Parameter. The Change Parameter pane appears (Figure 59).
5. Change the selected port’s parameter.
6. Click OK. The Change Parameter pane closes, and the LU Operation pane appears. Selected items
appear in blue italics in the WWN tree and WWN list. The contents of the setting appears in the Preset
list.
8. Click OK.
Stopping the use of paths to an external LU by specifying a local array’s

port (Disconnect Paths)
To stop using the path between the local array and external array by specifying the port of the local array,
select the Port Operation tree. The Port Operation list appears.
1. In the LU Operation pane, select the Port Operation tab. The Port Operation tree and Port Operation list
appear.
2. In the Port Operation tree, select External (the port attribute for the external array connection). The local
array’s external ports appear in the Port Operation list.
3. In the Port Operation list, right-click the port of the local array you want to stop using, and select
Disconnect Paths.
Selected items appear in blue italics in the Port tree and Port list. The contents of the setting appear in
the Preset list. To check the setting details, right-click the setting in the Preset list, and select Detail. To
cancel the setting, right-click the setting in the Preset list, and select Delete.
5. Click OK.
Restoring paths to an external LU by specifying a local array’s port

(Check Paths)
To restore the path between the local array and external array by specifying the local array’s port, select
the Port Operation tree. The Port Operation list appears.
NOTE: The path must be in a status that can be restored.
1. In the LU Operation pane, select the Port tab. The Port Operation tree and Port Operation list appear.
2. In the Port tree, select External (the port attribute for the external array connection) or the local array
port.
• If you select External, the local array port setting with the External attribute appears in the Port
Operation list.
• If you select the local array port, connection information about the path between the selected port
and external array appears.
3. In the Port Operation list, right-click the port of the local array for which you want to restore the path,
and select Check Paths.
Selected items appear in blue italics in the Port Operation tree and Port Operation list. The contents of
the setting appear in the Preset list. To check the setting details, right-click the setting in the Preset list,
and select Detail. To cancel the setting, right-click the setting in the Preset list, and select Delete.
5. Click OK.
Deleting external LU mappings (Delete LU)

You can start deleting external LU mappings from the LU Operation pane. To delete the external LU
mapping, select Delete LU from the shortcut menu displayed in the LU Operation pane. Although you can

use the Delete LU command to delete the mapping between an internal LDEV and external LU, you cannot
use this command to reliably delete data in the external LU or internal LDEV.
Before deleting the external LU mapping, notice if any of the following are true:
• Whether or not the execution of any application (for example, RAID Manager XP) that is using the
command device is in progress.
If any application using an external LU command device is executing, stop the application.
• Whether the Disconnect Subsystem or Disconnect Volumes command was executed.
All data in cache memory must be written into the mapped external LU using the Disconnect Subsystem
or Disconnect Volume command. For more information about the Disconnect Subsystem and Disconnect
Volume commands, see ”Disconnecting external arrays or LUs” on page 98.
• The volume is part of a LUSE volume.
• A path is set.
• The volume is configured as part of a Continuous Access XP, Continuous Access XP Journal, Business
Copy XP, or Snapshot XP pair.
• The volume is set as a reserved LU for Business Copy XP or Auto LUN XP.
• The volume is set as a pool-VOL.
If any of these conditions are true, you cannot delete the external LU mapping.
1. In the LU Operation pane, select the external LU group number in the Device tree. Information about the
external LU mapped as an internal LDEV appears in the Device list.
2. In the Device list, right-click the external LU for which you want to delete the mapping, and select Delete
LU.
Settings appear in blue italics in the Device list, and they appear in the Preset list. To check details
regarding intended changes, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.
NOTE: The maximum number of external LUs you can set at one time is 256.

Cancel, stop the application, and retry the operation.
4. Click OK. A confirmation message appears.
5. Click Yes or No.
If you click Yes, a confirmation message appears.
If you click No, a warning message appears. To execute the Delete LU operation without writing data in
the local array cache memory to the external LU, click OK. To cancel the operation, click Cancel. If you
click OK, a confirmation message appears.
NOTE: If you click OK in response to the warning, the Delete LU operation is performed, but data
in the local array cache memory that is not yet written to the external LU might be lost.
6. Click OK. The external LU whose mapping is deleted is removed from the Device list.
If errors occur, failed settings and error codes appear in the Preset list. To check error messages,
right-click the failed setting, and select Detail.

6 Troubleshooting NAS Blade systems that include
external arrays
If your local array is provided with a NAS package, you can configure the NAS Blade system that includes
an external array. This chapter describes procedures to stop the external array for maintenance and
recover the external array from a failure.
For more information about each procedure, see the following manuals:
• For NAS Blade Manager, see the NAS Blade Manager User’s Guide.
• For NAS Sync Image, see the NAS Sync Image User’s Guide.
• For Business Copy XP, see the HP StorageWorks Business Copy XP user guide for the
XP12000/XP10000/SVS200.
• For LUN Manager, see the HP StorageWorks LUN Configuration and Security Manager XP user guide
for the XP12000/XP10000/SVS200.
• For Continuous Access XP, see the HP StorageWorks Continuous Access XP user guide for the
XP12000/XP10000/SVS200.
Stopping and restarting external arrays

Figure 60 shows an example of a NAS Blade system configuration that includes an external array. The
procedures to stop the external array for maintenance and restart the external array after maintenance to
restore the NAS Blade system are described below, referring to Figure 60.
Figure 60 Example of a NAS Blade system configuration that includes an external array
CAUTION: To stop the external array, execute the procedure according to the following description. If you
execute the wrong procedure, an error occurs in the NAS Blade system (for example, the file system might
be blocked or the resource group’s status might become inappropriate).

Stopping external arrays
1. Stop access from the client.
2. Stop the cluster using NAS Blade Manager.
3. Delete all Business Copy XP or Continuous Access XP pairs, if you created the pairs specifying the
external LU.
4. Stop NAS OS 1 (NAS channel adapter’s OS) and NAS OS 2 using LUN Manager.
NOTE: The NAS OS can also be stopped from the SVP. To stop the NAS OS from the SVP, contact
your HP account support representative.
5. Disconnect the external array using External Storage XP. For instructions, see ”Disconnecting external
arrays or LUs” on page 98.
6. Stop the external array. For instructions, see ”To power external arrays off” on page 29.
Restarting external arrays and restoring NAS Blade systems

1. Turn the external array power supply on. For instructions, see ”To power external arrays on” on
page 29.
2. Confirm that the external array’s status is normal.
3. Execute the Check Paths & Restore Vol. command using External Storage XP to restore the path to the
external array. For instructions, see ”Checking the connection status and resuming external LU
operations (Check Paths & Restore Vol.)” on page 100.
4. Confirm that the connection between the local array and the external array is normal.
5. Start NAS OS 1 (NAS channel adapter’s OS) and NAS OS 2 using LUN Manager.
NOTE: The NAS OS can also be started from the SVP. To start the NAS OS from the SVP, contact
6. If you deleted Business Copy XP or Continuous Access XP pairs as you stopped the external array,
re-create the deleted pairs.
7. Start the cluster using NAS Blade Manager.
8. Resume access from the client.
Recovery procedures for errors in external arrays

This section describes recovery procedures for when an error occurs in the NAS Blade system’s external
array.
Errors in an external array’s disk

Figure 61 shows an example of when an error occurs in an external array’s disk. The situation in
Figure 61 is as follows:
• Data itself stored in the error disk in external array 1 cannot be restored. To restore data to the original
disk after recovering the NAS Blade system, the data should have been backed up in a disk other than
the error disk.
• Clients cannot access volumes in the error disk. Clients can only access volumes other than the error
disk.
108 Troubleshooting NAS Blade systems that include external arrays

• The local array recognizes that the status of the file system and volume in the error disk is blocked.
Figure 61 Error in an external array’s disk

1. Delete all Business Copy XP or Continuous Access XP pairs, if you created pairs.
2. Perform the following operations on node 1:
a. Release the differential-data storage device using NAS Sync Image.
b. Delete the NFS share, CIFS share, and file system using NAS Blade Manager.
3. Change resource group 1’s execution node to node 2 using NAS Blade Manager (failover).
If resource group 1’s status is Offline, this operation is not required.
4. Stop node 1 using NAS Blade Manager.
5. Restart NAS OS 1 (NAS channel adapter’s OS) using LUN Manager or NAS Blade Manager.
6. Start node 1 using NAS Blade Manager.
7. Perform one of the following operations using NAS Blade Manager:
• When resource group 1’s status is Online, change resource group 1’s execution node to node 1
(failback).
• When resource group 1’s status is Offline, start resource group 1.
8. Perform the following operations on node 2:
a. Release the differential-data storage device using NAS Sync Image.
b. Delete the NFS share, CIFS share, and file system using NAS Blade Manager.
10.Stop node 2 using NAS Blade Manager.
11.Restart NAS OS 2 (NAS channel adapter’s OS) using LUN Manager or NAS Blade Manager.
12.Start node 2 using NAS Blade Manager.
13.Perform one of the following operations using NAS Blade Manager:
(failback).

14.Change the error disk in the external array to restore the external array’s status.
15.Execute the Check Paths & Restore Vol. command using External Storage XP. For instructions, see
”Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.)” on
page 100.
16.Perform the following operations on node 1 and node 2:
a. Set up the differential-data storage device using NAS Sync Image.
b. Create the file system, and create the NFS share and CIFS share using NAS Blade Manager.
17. Return the backed-up data to the external array’s restored disk, if you had the backed up data in a disk
other than the error disk.
18.Recreate the Business Copy XP and Continuous Access XP pairs.
Errors in a path to the external array

Figure 62 shows an example of when an error occurs in a path between the local array and an external
array. In Figure 62, an error occurs in the path between the local array and external array 1; however,
the path between the local array and external array 2 is normal.
The situation in Figure 62 is as follows:
• Clients cannot access volumes in external array 1, but can access volumes in external array 2.
• The local array recognizes that the status of all file systems and volumes in external array 1 are
blocked.
x
Figure 62 Error in a path to the external array

1. Restore (for example, check the cable’s connection status or change the switch) the status of the error
path between the local array and external array 1.
2. Execute the Check Paths & Restore Vol. command using External Storage XP. For instructions, see
page 100.

7. Perform one of the following operations using NAS Blade Manager:
(failback).
10.Restart NAS OS 2 (NAS channel adapter’s OS) using LUN Manager or NAS Blade Manager.
11.Start node 2 using NAS Blade Manager.
12.Perform one of the following operations using NAS Blade Manager:
(failback).
Errors in all paths to the external array

The following sections describe the recovery procedures for two examples when the error occurs in all
paths connected to the external array.
If each node uses a different external array
In the configuration in Figure 63, all of the NAS Blade system’s user LUs are volumes in the external
array. Each node uses the volume of a different array. All of node 1’s user LUs are volumes in external
array 1. Therefore, if an error occurs in the path between the local array and external array 1, the error
occurs in all paths connected from node 1 to external array 1. In this situation, no user LU is available for
node 1.
• The NAS Blade system attempts to change resource group 1’s execution node to node 2 because no
user LU can be used from node 1 (failover). However, node 2 cannot access volumes in external
array 1, the failover function failed, and an srmd executable error appears as error information for
resource group 1.
• The file system’s status is blocked on node 2 because of the failure of the failover of resource group 1.
• Clients cannot access volumes in external array 1, but can access volumes in external array 2.

• The local array recognizes that the status of all file systems and volumes in external array 1 are
blocked.
Figure 63 Error occurs on the path to the external array used for node 1
page 100.
3. Perform a forced stop operation using NAS Blade Manager for resource group 1, which displays the
status as an srmd executable error.
7. To release the blocked status of node 2’s file system, perform the following operations:
a. Change resource group 2’s execution node to node 1 using NAS Blade Manager (failover).
b. Restart NAS OS 2 (NAS channel adapter’s) using LUN Manager or NAS Blade Manager.
c. Change resource group 2’s execution node to node 2 (failback).
8. Start resource group 1 on node 1 using NAS Blade Manager.
If both nodes use the same external array
In the configuration in Figure 64, all of the NAS Blade system’s user LUs are volumes in the external
array. Only one external array is connected to the local array. Also, only one path is set between the
local array and external array. In this case, if an error occurs in the only set path, none of the volumes in
the external array can be used.

NOTE: In the configuration in Figure 64, HP recommends setting alternate paths to prevent the NAS
Blade system from being blocked because of the path failure. For more information, see ”Alternate paths”
on page 22.

• None of the user LUs can be used from node 1 or node 2.
• Clients cannot access volumes.
• The local array recognizes that the status of all file systems and volumes are blocked.
Figure 64 If both nodes use the same external array

page 100.
3. Perform the forced stop operations using NAS Blade Manager for resource group 1 and resource
group 2.
4. Stop the cluster using NAS Blade Manager.
5. Restart NAS OS 1 and NAS OS 2 (NAS channel adapter’s OS) using LUN Manager or NAS Blade
Manager.
6. Start the cluster using NAS Blade Manager.
7. Start resource group 1 and resource group 2 using NAS Blade Manager.

7 Remote command devices
This chapter describes remote command devices.
Overview of remote command devices

A remote command device is a device in the local array to which a command device in the external array
is mapped.
As you send RAID Manager XP commands to a remote command device located in the local array, you
can execute those commands on the external array’s command device to manage pairs in the external
array.
Figure 65 shows an example. The OPEN host connected to the local array sends RAID Manager XP
commands for Business Copy XP or Continuous Access XP to the remote command device. This means
commands are forwarded to the command device in the external array to operate Business Copy XP or
Continuous Access XP pairs in the external array.
For more information about RAID Manager XP and command devices, see the HP StorageWorks RAID
Manager XP User’s Guide.
Figure 65 Overview of remote command device
Notices about remote command devices

• You can map command devices as remote command devices when one of the following arrays is
connected as an external array:
• XP12000 Disk Array
• XP10000 Disk Array
• HP 200 Storage Virtualization System
• XP1024/XP128 Disk Array
• TagmaStore™ Universal Storage Platform subsystem
• TagmaStore™ Network Storage Controller subsystem
• TagmaStore™ Adaptable Modular Storage subsystem

• TagmaStore™ Workgroup Modular Storage subsystem
• Lightning 9900V series subsystem
• Thunder 9500V series subsystem
• SANRISE Universal Storage Platform subsystem
• SANRISE Network Storage Controller subsystem
• SANRISE Adaptable Modular Storage subsystem
• SANRISE Workgroup Modular Storage subsystem
• SANRISE9900V series subsystem
• SANRISE9500V series subsystem
• SANRISE H12000 subsystem
• SANRISE H10000 subsystem
• SANRISE H1024/H128 subsystem
• You do not need a license for External Storage XP or Flex Copy XP to map command devices as
remote command devices.
• Remote command devices are displayed on External Storage XP’s panes.
As you select an external LU group number in the Device tree on the LU Operation pane, the
information shown in Table 10 appears.
Table 10 Information displayed in the Device column for remote command devices
Storage array Information displayed in Device column of

Device list
XP12000 Disk Array Format: “Emulation Type” + “-CM”
XP10000 Disk Array Example: OPEN-V-CM, OPEN-3-CM
HP 200 Storage Virtualization System
XP1024/XP128 Disk Array
TagmaStore™ Universal Storage Platform subsystem
TagmaStore™ Network Storage Controller subsystem
Lightning 9900V series subsystem
SANRISE Universal Storage Platform subsystem
SANRISE Network Storage Controller subsystem
SANRISE9900V series subsystem
SANRISE H12000 subsystem
SANRISE H10000 subsystem
SANRISE H1024/H128 subsystem
TagmaStore™ Adaptable Modular Storage subsystem DF600F-CM

TagmaStore™ Workgroup Modular Storage subsystem
Thunder 9500V series subsystem
SANRISE Adaptable Modular Storage subsystem
SANRISE Workgroup Modular Storage subsystem
SANRISE9500V series subsystem
• If you access a remote command device from an OPEN host, the remote command device reports
device information about the command device, which is mapped as a remote command device of the
external array.
Device information about the command device that the remote command device reports to the host
includes:
• Serial number
• Vendor

• Device name
NOTE: The device name reported to the host is the same as the one displayed in the Device
column of the Device list. For the device names reported to the host, see Table 10.
• The following are restrictions for mapping command devices as remote command devices.
Table 11 Restrictions on remote command devices
Item Restriction
Emulation type OPEN-V
Number of LDEVs in an external LU 1
IO Suppression mode Disable
Cache mode Disable
Minimum capacity 96,000 blocks (about 47 MB)
Maximum capacity 2 TB
• External Storage XP’s Discovery operation cannot identify remote command devices.
• You cannot execute I/Os to remote command devices.
• You cannot set command devices to disabled on remote command devices.
• You cannot set command devices’ security on remote command devices.
• Do not set command devices’ security on the external array side for command devices mapped as
remote command devices.
• You cannot create LUSE volumes using remote command devices.
• You cannot use Volume Manager to create CVs in remote command devices.
• Cache LUN XP is not available on remote command devices.
Mapping command devices as remote command devices

To map command devices in external arrays as remote command devices, see ”Mapping external LUs
(Add LU)” on page 73.
NOTE: Command devices that can be mapped as remote command devices are displayed on External
Storage XP’s panes as shown in Table 10.
When you select Discovery in the Device tree on the LU Operation pane, the external array’s WWNs
appear. When you select an external array’s WWN in the Device tree, information such as OPEN-V-CM
appears in the Device column of the Device list for command devices that can be mapped. Select a
command device that can be mapped, and follow the procedure in ”Mapping external LUs (Add LU)” on
page 73 to map it.
Using Continuous Access XP or Continuous Access XP Journal with

remote command devices
To use Continuous Access XP or Continuous Access XP Journal with a remote command device, you would
traditionally need two different kinds of ports: an initiator port for Continuous Access XP or Continuous
Access XP Journal, and an external port for the remote command device. However, if you set the
Initiator/External MIX mode, you can use a port as both the initiator port for Continuous Access XP or
Continuous Access XP Journal and as the external port only for remote command device use.
Before setting the Initiator/External MIX mode, you must prepare initiator and external ports in one port
block of Standard mode. You can set the Initiator/External MIX mode on the port block consisting of the
initiator and external ports.

Figure 66 shows the difference between Standard and Initiator/External MIX modes. When ports are set
to Standard modes, you must connect the cables for the initiator and external ports. However, if you set
the Initiator/External MIX mode, you must connect only one cable, and you can use that path to operate
Continuous Access XP or Continuous Access XP Journal and the remote command device.
For more information about port blocks and setting the Initiator/External MIX mode, see the
XP12000/XP10000/SVS200.
Figure 66 Difference between Standard and Initiator/External MIX modes

Figure 67 shows an example of using Continuous Access XP or Continuous Access XP Journal with a
remote command device. In Figure 67, local array 1 functions as the MCU of Continuous Access XP or
Continuous Access XP Journal, and at the same time it functions as the local array of the remote command
device. Local array 2 functions as the RCU of Continuous Access XP or Continuous Access XP Journal, and
at the same time it functions as the external array of the remote command device. In this case, setting the
Continuous Access XP or Continuous Access XP Journal pair and setting the remote command device are
both done using the port of the Initiator/External MIX mode. As this example shows, you only need to

connect one cable to one of the ports set to Initiator/External MIX mode, which means that you do not
need to connect cables to each port of different port attributes.
Figure 67 Using Continuous Access XP or Continuous Access XP Journal with remote command devices
Using Initiator/External MIX mode

This section describes the procedure to use Initiator/External MIX mode and the procedure to stop using
Initiator/External MIX mode.
To use Initiator/External MIX mode:
1. Prepare the initiator ports of the Standard mode and external ports of the Standard mode in one port
block.
For the procedure to set the port attribute to initiator, see the HP StorageWorks Continuous Access XP
user guide for the XP12000/XP10000/SVS200 or the HP StorageWorks Continuous Access XP
Journal user guide.
For the procedure to set the port attribute to external, see ”Setting a local array’s port attributes” on
page 72.
2. Set the Initiator/External MIX mode to the port block consisting of the initiator ports of the Standard
mode and external ports of the Standard mode.
For the procedure to set the Initiator/External MIX mode, see the HP StorageWorks LUN Configuration
and Security Manager XP user guide for the XP12000/XP1000/SVS200.
3. Connect the cable to the port, and connect an array to be used as an MCU and local array and an
array to be used as an RCU and external array.
4. Map the command device as the remote command device.
NOTE: Only the command device can be recognized when the discovery operation is performed
using the external port of the Initiator/External MIX mode.
5. Start the Continuous Access XP or Continuous Access XP Journal operation and the remote command
device operation using the port of the Initiator/External MIX mode.
To stop using Initiator/External MIX mode:
1. Stop the Continuous Access XP and Continuous Access XP Journal copy processing and operation.

2. Stop accessing the remote command device.
3. Delete the remote command device mapping.
4. Change the port block setting from Initiator/External MIX mode to Standard mode.
For the procedure to change the port block setting, see the HP StorageWorks LUN Configuration and
Restrictions on Initiator/External MIX mode

Restrictions on Initiator/External MIX mode are:
• Restrictions on High Speed mode are also restrictions on Initiator/External MIX mode. For High Speed
mode the restrictions, see the HP StorageWorks LUN Configuration and Security Manager XP user
guide for the XP12000/XP1000/SVS200.
• A point-to-point connection is not available.
• You cannot set Initiator/External MIX mode on external ports of the Standard mode that have already
been used to map the external LUs. You cannot set Standard mode on the port of the Initiator/External
MIX mode that has already been used to map the remote command device. You must delete the
external volume’s mapping, and then change the port mode’s setting.
• Using a port of the Initiator/External MIX mode, the command device of the external array can only
be recognized by the discovery operation and mapped. Other volumes cannot be recognized by the
discovery operation or mapped using the port of the Initiator/External MIX mode.

8 Troubleshooting External Storage XP
If you have a problem with the Command View XP computer or Command View XP or XP Remote Web
Console software, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the
HP StorageWorks XP Remote Web Console for XP12000/XP10000/SVS200 for troubleshooting
information.
For additional assistance, contact your HP account support representative.
Table 12 provides general troubleshooting instructions for External Storage XP operations.
Table 12 General External Storage XP troubleshooting
Error Corrective action

The Command View XP Correct the error and retry the operation.
management station or XP
The reason for the error could be one of the following:
Remote Web Console cannot
access the external LU. • The Fibre Channel (FC) switch is off or an error occurred in the switch.
• The FC cables are not properly connected.
• The configuration of the external array changed, and the external LU was
deleted.
• An error occurred with the external LU in the external array.
• The path in the external array changed.
• The port attribute of the local array is no longer external.
• The topology information is not set correctly.
The external LU cannot be Correct the error and retry the operation.
mapped as an internal LDEV
The source of the error could be any of the following:
of the local array.
• The number of mapped external LUs exceeds the maximum number (15,360
LUs for XP12000 or 8,192 LUs for XP10000/SVS200) available for the local
array.
• There are not enough CU:LDEV numbers available for external LU mapping.
The path to the external LU is 1. The errors listed in the first row of this table (Error: The Command View XP
blocked. management station or XP Remote Web Console cannot access the external
LU) could be the reason for this error. Check the reasons in the first row,
correct the error, and retry the operation. If the error persists, try step 2b.
2. Try the following procedures. If they do not work and the path is not restored,
contact your HP account support representative.
a. Verify that the cable between the local array and external array is
connected properly.
b. If the cable between the local array and external array is connected
properly, disconnect and reconnect it. After 30 seconds, check the path
status from Command View XP or XP Remote Web Console.
The status appearing in the The LDEV’s status cannot be determined. This occurs when the LDEV does not
Ex-Dev. Status column is exist. The reason for the error could be:
Normal, but the status
• The LDEV was been created when the volume was mapped.
appearing in the LDEV Status
is Unknown. • The LDEV in the external LU was deleted by the Volume Manager function.
If LDEV Status becomes Unknown by any reason other than above, contact you
The path status that requires The following rows describe path status values displayed in the Alternate Path list
the action appears in the and corrective actions for each status value. See ”Notes on connecting external
Alternate Path list on the Path arrays” on page 127 for notes on connection settings and examples of recovery
Setting window (see ”Setting procedures, and then take the corrective action.
alternate paths for external
LUs” on page 86).

Table 12 General External Storage XP troubleshooting (continued)

Unknown Status: The path status is unknown.
Corrective action: The path status cannot be
identified. Contact your HP account support
representative.
Blockade Status: The external port is blocked.

Corrective action: The external port is blocked
because of the microprogram or package
replacement or some other factor. Check the local
array’s status. If you cannot restore the path, contact
External device setting Status: The external array’s configuration changed.

changed For example, the path definition was deleted, or the
external array itself was replaced by another
device.
Corrective action: The external array’s port is
recognized. See the internal array’s documentation,
and check if the operation that changes the mapped
device’s setting information has not been
performed.
LDEV size reduced Status: The external array’s volume capacity setting
changed (was reduced).
Corrective action: Check the volume capacity of the
external array’s LU. Execute the Delete LU
operation, and retry the Add LU operation.
Not ready Status: The reply from the external array was
NOTREADY. The external array’s drive is spinning
up, or the external array’s device is being
formatted.
Corrective action: The path cannot be used to
access the external array. Check the external
array’s status. If you cannot restore the path, contact
Illegal request Status: The reply from the external array was
ILLEGALREQUEST. The command cannot be
executed to the external array’s device. Data
protection might be set on the external array’s
device.
recognized. Check the external array’s setting. If
you cannot restore the path, contact your
Command aborted Status: The reply of the external array was

ABORTEDCOMMAND. An error might have
occurred on the external array side.
Corrective action: The port of the external array is
recognized. Check the external array’s setting and
the condition of the connection to the external array
(for example, cables or switches). If you cannot
restore the path, contact your HP account support
representative.


Busy Status: The external array’s status is BUSY.
Corrective action: The external array’s port is still
recognized. Check the external array’s settings and
the load on the external array (for example, check
whether the configuration assigns too much load on
the external array). If you cannot restore the path,
contact your HP account support representative.
LDEV reserved Status: The external array’s status is Reserved. You

cannot access the external array’s device from the
local array.
Corrective action: Remove the Reserve status on the
external array’s device.
Response error Status: The external array’s status is Blocked due to

an abnormal reply (Response). You might not be
able to access the external array’s device, or data
protection might be set on the external array’s
device.
recognized. Check the external array’s setting and
status. If you cannot restore the path, contact your
Initiator port Status: The external array (for example, XP) port
attribute changed to Initiator.
Corrective action: Set the external array’s port
attribute back to target. If you cannot restore the
path, contact your HP account support
representative.
RCU target port Status: The port attribute of the external array
changed to RCU target.
Corrective action: Set the port attribute of the
external array to Target. If you cannot restore the
path, contact your HP account support
representative.
Unknown port Status: The external array’s port attribute is

unknown.
recognized. Check the condition of the connection
(for example, cables and switches) to the external
array. If you cannot restore the path, contact your


Cannot detect port Status: The path was removed or the external
array’s port cannot be found. There is a problem
with the connection to the external array. The
following are possible causes:
• The fibre cable is not connected properly.
• The topology setting between the external and
target ports does not match.
• Because security is set on the port, the external
array’s device cannot be recognized from the
local array.
• If the external array is connected through
switches, the switches’ settings might not be
appropriate.
Corrective action: Check the condition of the
connection to the external array. If you cannot
restore the path, contact your HP account support
representative.
Internal error Status: A program error occurred, or there is a
logical contradiction.
Corrective action: Contact your HP account support
representative.
Timeout Status: Processing was retried because an abnormal

reply (Response) was returned, but processing has
stopped due to a timeout.
Corrective action: The external array’s port of is
recognized. Check the condition of the connection
(for example, cables and switches) to the external
array. If you cannot restore the path, contact your
Target error Status: An error, such as blockade of the controller,

was found in the external array’s port.
Corrective action: Check the status of the external
array’s ports. If you cannot restore the path, contact
Unavailable Status: The reply from the external array was

Unavailable. The external array requested a change
to the connected port. When the status becomes
Unavailable, the primary path changes to the
alternate path that is in Standby status. When the
primary path changes, the path status becomes
Normal.
Corrective action: If the path does not change
properly, check the external array’s status. If you
cannot restore the path, contact your HP account
support representative.


Backoff Status: The reply from the external array was
Backoff. The path status is Waiting for Recovery
because a temporary error occurred in the external
array’s volume. Even if the primary path’s status
becomes Backoff, the primary path does not change
to the alternate path immediately. After error
recovery, the status becomes Normal.
Corrective action: If you cannot recover the status
from the error, the path status changes to another
status. Take the corrective action for the new path
status. If you cannot restore the path, contact your
The Discovery operation Correct the error and retry the operation.
cannot be performed.
The source of the error could be one of the following:
• Command View XP or XP Remote Web Console is not in Modify mode.
• The local array port and external array port are not connected using FC
cables.
• Port security is improperly set on the external array.
• The status of the device in the external array is not Normal.
• The external array is not connected to a local array port set to External.
• The external LUN of the local array does not have a status of Normal.
• The external LU capacity is insufficient (less than 46.86 MB).
• The cable to the switch is not properly connected.
• The zoning for the switch is not set properly.
If none of these correct the problem, disconnect and then reconnect the cable
between the local array and external array. After 30 seconds, retry the
operation.
The external LU is blocked. Correct the error and retry the operation.
The source of the error could be any one of the following:
• All set paths are blockaded (or not connected).
• The external LU’s attribute is not set to Read/Write.
• The external LU is blockaded by an error.
The Check Paths & Restore Click Refresh ( ) on the Command View XP or XP Remote Web Console pane
Vol. command has executed to update the displayed information. If the device status remains Checking, even
and you have waited more though you updated the information, execute the Check Paths & Restore Vol.
than 10 minutes, but the command again.
device’s status does not
If the problem persists despite retrying, contact your HP account support
change from Checking.
representative.
The Disconnect Subsystem or Click Refresh ( ) on the Command View XP or XP Remote Web Console pane
Disconnect Volume command to update the displayed information. If the progress information for the Cache
has executed, but the Destage status is not updated, even though you updated the information contact
progress status information is your HP account support representative.
not updated.
NOTE: The time required to write of data from cache to the external LU
(destaging processing) depends on the volume capacity (more time is required for
a larger volume than a smaller one). The processing speed is about 20 MB/s.
However, processing speed depends on the external array’s performance and
status.


The message The device status is currently changing. Please wait for a while, and then check
INTERVENTION REQUIRED the device status again. When the transition of the device status completes
is issued to the mainframe normally, the device can be used immediately. If the device is blocked as a result
host as the device status. of the device status transition, see the description for the “The external LU is
blocked.” error in this table for corrective action.
The message DEVICE See the description for the “The external LU is blocked.” error in this table for the
ERROR is issued to the corrective action.
mainframe host as the device
status.

A Notes on connecting external arrays
NOTE: If you have an EVA or MSA connected as external storage and you need to perform a firmware
upgrade on the EVA or MSA, you must use the EVA/MSA offline firmware upgrade function. When the
EVA or MSA is connected as XP external storage, online EVA/MSA firmware upgrade is not supported at
this time. Therefore, you must stop host I/O to the arrays in question, and issue the Disconnect Subsystem
command before the upgrade. After performing the upgrade, issue the Check Paths & Restore Vol.
command. See ”Disconnecting external arrays or LUs” on page 98 and ”Checking the connection status
and resuming external LU operations (Check Paths & Restore Vol.)” on page 100 for details. You must
also perform these procedures on other external arrays that do not support online firmware upgrade
NOTE: If your application server contains boot devices from external arrays that are EVA or
MSA-resident, and you need to perform a firmware upgrade on the EVA or MSA, you must shut down any
servers that boot from these arrays (through the XP, or otherwise) before the upgrade procedure. Perform
the following steps:
1. Power down the application server containing boot devices from the external array.
2. From XP Remote Web Console, issue the Disconnect Subsystem command. See ”Disconnecting
external arrays or LUs” on page 98 for more information.
3. Perform the external array firmware upgrade as directed in the external array’s user documentation.
4. From XP Remote Web Console, issue the Check Paths & Restore Vol. command after the firmware has
been upgraded. See the ”Checking the connection status and resuming external LU operations (Check
Paths & Restore Vol.)” on page 100 for more information.
5. Power on the application server, and resume the applications.
If the boot device is from an external array that does not support online firmware upgrade, you also must
perform this procedures. See the firmware upgrade procedure for the external array for instructions.
Connecting Thunder 9500V subsystems

System parameters for connecting Thunder 9500V subsystems
Table 13 explains whether to specify system parameters when making settings for ports on the Thunder
9500V subsystem.
Table 13 System parameter settings (Thunder 9500V subsystems)
Pane name Parameter Parameter setting

System Startup Settings Start Attribute
• Single Mode Specify this parameter when the Thunder

9500V subsystem is in the one-controller
configuration.
• Dual Active Mode Specify this parameter when the Thunder

9500V subsystem is in the two-controller
configuration.
NOTE: Be sure to specify that Data

Share Mode will be used.
• Hot Stand-By Mode Do not specify this parameter.

Table 13 System parameter settings (Thunder 9500V subsystems) (continued)
Pane name Parameter Parameter setting

Common 1 Delay Planned Shutdown You can either specify this parameter or
omit specifying this parameter.
OPTION 1 SCSI Fibre Channel Common Options You can either specify this parameter or
OPTION 2 SCSI Fibre Channel Common Options You can either specify this parameter or
Data Striping Operation if the processor failure occurs Set this parameter to Reset of occurred.
Inquiry Setting Command Queuing Mode Set this parameter to ON.
Vendor ID Keep this parameter as HITACHI (default),

and do not change.
Product ID Keep this parameter as DF600F (default),

and do not change.
ROM Microprogram Version You can either specify this parameter or

RAM Microprogram Version You can either specify this parameter or

WEB Title You can either specify this parameter or

Port Type Reset/LIP Mode
• Reset/LIP Mode (Signal) You can either specify this parameter or

• Reset/LIP Mode (Process) You can either specify this parameter or

• LIP Reset Mode You can either specify this parameter or

Controller Option RS232C Error Information Outflow Mode You can either specify this parameter or
Write and verify mode Set this parameter to ON.
Host Connection Mode Host Connection Mode 1 Set this parameter to Standard Mode.
Host Connection Mode 2 Specify HISUP Mode.
NOTE: Do not specify any other

parameters.
NOTE: When using the Thunder 9500V subsystem as an external array, the following versions are
recommended. If you use a 9500V subsystem whose version is earlier than the following versions, the
SATA drive’s information might not be displayed correctly.
• For Thunder 9530V, Thunder 9520V, Thunder 9570V: version 0658 or later
• For Thunder 9580V, Thunder 9585V: version 1658 or later
128 Notes on connecting external arrays

Relationship between serial numbers in the Device list on the LU Operation pane
and Thunder 9500V subsystem models
When the external array is a Thunder 9500V subsystem, you can identify the subsystem model from the
serial number displayed in the Serial column in the Device list on the LU Operation pane.
Table 14 shows the relationship between serial numbers displayed in the Serial column and subsystem
models.
Table 14 Relationship between serial numbers and subsystem models (Thunder 9500V subsystems)
Displayed serial number Model

D600XXXX 9570V, 9520V
D60JXXXX 9530V
D60HXXXX 9580V, 9585V
NOTE: In serial numbers, X is an arbitrary number or character.
Relationship between the WWN of the port on the Thunder 9500V subsystem and
the controller
When the external array is a Thunder 9500V subsystem, you can identify the controller (controller 0 or
controller 1) from the port’s WWN.
Table 15 shows the relationship between the port’s WWN and the controller.
Table 15 Relationship between ports’ WWNs and controllers (Thunder 9500V subsystems)
Model Controller Port’s WWN

9570V Controller 0 XXXXXXXXXXXXXXX0
9530V XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX3

9585V XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
Controller 1 XXXXXXXXXXXXXXX4
XXXXXXXXXXXXXXX5
XXXXXXXXXXXXXXX6
XXXXXXXXXXXXXXX7
NOTE: In WWNs, X is an arbitrary number or character. Ports in the same apparatus have identical
values.

Path status and examples of recovery procedures (Thunder 9500V subsystems)
Table 16 shows examples of recovery procedures when the path status is not normal. When the path
status is not normal, see ”Troubleshooting External Storage XP” on page 121 and this table to recover the
path status. If you cannot restore the path, contact you HP account support representative.
Table 16 Path status and examples of recovery procedures (Thunder 9500V subsystems)
Path status Examples of recovery procedures

External device setting changed LUN Manager may have changed the LU paths’ settings.
Check the LU paths’ settings. If the LU paths’ settings changed, change the
settings back to the ones used when the volume was mapped. Or use
External Storage XP to perform the Delete LU operation, and perform the
Add LU operation again.
Open LDEV Guard may have changed the volume’s access attribute.
Check the volume’s access attribute. If the volume is protected by the
access attribute, release the protection.
Illegal request The volume may have been set as a pair volume for data copy.
Check if the volume is set as a pair volume for Business Copy XP,
Continuous Access XP, or another copy program. If the volume is set as a
pair volume, the volume might be protected because of the pair status. If
the volume is protected, change the pair status or delete the pair.
Response error The volume may have been set as a pair volume for data copy.
Cannot detect port There is a problem with the connection to the external array. The following
are possible causes:
• The topology setting between the external and target ports does not
match.
• If the external array is connected through switches, the switches’
settings might not be appropriate.
Check if the fibre cable is connected properly, and use LUN Manager to
set the Fibre Channel port properly.
LUN Manager may have enabled host group security.

Check if host group security is enabled. If host group security is enabled,
disable host group security.
Connecting TagmaStore AMS and TagmaStore WMS subsystems

System parameters for connecting TagmaStore AMS and TagmaStore WMS
subsystems
Table 17 explains whether to specify system parameters when making settings for ports on TagmaStore
AMS and TagmaStore WMS subsystems.

NOTE: When connecting to a TagmaStore AMS or TagmaStore WMS subsystem, use LUN Manager to
set the data transfer speed of the XP12000/XP10000/SVS200 external port you use to a fixed value
other than Auto Negotiation. Also, set the data transfer speed of the target port of the TagmaStore AMS or
TagmaStore WMS subsystem to the same fixed value according to the data transfer speed of the external
port.
Table 17 System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems)
Pane name Parameters Parameter setting

Boot Options Start Attribute
• Single Mode Specify this parameter when the TagmaStore

AMS or TagmaStore WMS subsystem is in
the one-controller configuration.
• Dual Active Mode Specify this parameter when the TagmaStore

AMS or TagmaStore WMS subsystem is in
the two-controller configuration.
Delay Planned Shutdown You can either specify this parameter or omit
specifying this parameter.
Drive blocking mode You can either specify this parameter or omit
Vendor ID Keep this parameter as HITACHI (default),

and do not change.
Product ID Keep this parameter as DF600F (default),

and do not change.
ROM Microprogram Version You can either specify this parameter or omit
RAM Microprogram Version You can either specify this parameter or omit
System Parameter Option You can either specify this parameter or omit
Operation if the processor failure occurs Set this parameter to Reset of occurred.
WEB Title You can either specify this parameter or omit

Write and verify mode Set this parameter to ON.
Port Options Port Option You can either specify this parameter or omit
Host Connection Host Connection Mode 1 Set this parameter to Standard Mode.
Mode
Host Connection Mode 2 Do not specify any parameters.
NOTE: Do not specify HISUP OFF mode,

either.
NOTE: You can either specify or omit any other parameters.

Relationship between serial numbers in the Device list on the LU Operation pane
and TagmaStore AMS and TagmaStore WMS subsystem models
When the external array is a TagmaStore AMS or TagmaStore WMS subsystem, you can identify the
subsystem model from the serial number displayed in the Serial column in the Device list on the LU
Operation pane.
Table 18 shows the relationship between serial numbers displayed in the Serial column and subsystem
models.
Table 18 Relationship between serial numbers and subsystem models (TagmaStore AMS and TagmaStore
WMS subsystems)
Storage subsystem Displayed serial number Model

AMS 77XXXXXX AMS 1000
75XXXXXX AMS 500
73XXXXXX AMS 200
WMS 71XXXXXX WMS 100
NOTE: In serial numbers, X is an arbitrary number or character.
Relationship between the WWN of the port on the TagmaStore AMS or

TagmaStore WMS subsystem and the controller
When the external array is a TagmaStore AMS or TagmaStore WMS subsystem, you can identify the
controller (controller 0 or controller 1) from the port’s WWN.
Table 19 shows the relationship between the port’s WWN and the controller.
Table 19 Relationship between ports’ WWNs and controllers (TagmaStore AMS and TagmaStore WMS
subsystems)
Model Controller Port’s WWN

AMS 200 Controller 0 XXXXXXXXXXXXXXX0
WMS 100 Controller 1 XXXXXXXXXXXXXXX1

XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX3

XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
XXXXXXXXXXXXXXX5
XXXXXXXXXXXXXXX6
XXXXXXXXXXXXXXX7

NOTE: In WWNs, X is an arbitrary number or character. Ports in the same apparatus have identical
values.
Path status and examples of recovery procedures (TagmaStore AMS and

TagmaStore WMS subsystems)
Table 20 shows the examples of recovery procedures when the path status is not normal. When the path
status is not normal, see ”Troubleshooting External Storage XP” on page 121 and this table to recover the
path status. If you cannot restore the path, contact your HP account support representative.
Table 20 Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS
subsystems)

LUN Security XP Extension may have changed the volume’s access

attribute.

attribute.

attribute.

Table 20 Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS
subsystems) (continued)

match.
LUN Manager may have enabled the host group security.

Check if host group security is enabled. If host group security is enabled,
disable host group security.
Connecting XP12000/XP10000 Disk Arrays

When connecting an XP12000/XP10000 Disk Array as the external array, you must set the external array
port host group for one of two types of Windows hosts (host mode 0C: Windows, host mode 2C:
Windows Extension).
Also, the port attribute must be the target or RCU target port.
Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)

Table 21 shows examples of recovery procedures when the path status is not normal. When the path status
is not normal, see ”Troubleshooting External Storage XP” on page 121 and this table to recover the path
status. If you cannot restore the path, contact your HP account support representative.
Table 21 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)


attribute.
Continuous Access XP, Continuous Access XP Journal, or another copy
program. If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is protected, change the
pair status or delete the pair.

attribute.

Table 21 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) (continued)

Continuous Access XP, Continuous Access XP Journal, or another copy
program. If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is protected, change the
pair status or delete the pair.

attribute.
match.
Check if the fibre cable is connected properly, and use LUN Management
to set the Fibre Channel port properly.
LUN Management may have enabled LUN security.

Check if LUN security is enabled. If LUN security is enabled, disable LUN
security.

When connecting an XP1024/XP128 Disk Array as the external array, you must set the external array port
host group for one of two types of Windows hosts (host mode 0C: Windows, host mode 2C: Windows
Extension).




Cannot detect port There is a problem with connection to the external array. The following are
possible causes:
match.
Check if the fibre cable is connected properly, and use LUN Manager to set
the Fibre Channel port properly.
LUN Manager may have set LUN security.

security.

When connecting an XP512/XP48 Disk Array as the external array, you must set the port’s host mode to
PC Server (0C).




Cannot detect port There is a problem with connection to the external array. The following are
possible causes:
match.
Hitachi SANtinel may have set LUN security.

security.
Connecting HP 200 Storage Virtualization System as external storage

When connecting an HP 200 Storage Virtualization System (SVS200) as the external array, you must set
the SVS200 port to a host group for Windows hosts (host mode 0C: Windows or host mode 2C: Windows
Extension).
Also, the SVS200 port attribute must be “target” (for an External Storage XP connection) or “RCU target
port” (for a Continuous Access XP connection).
NOTE: If you are using microcode that does not support the SVS200, the SVS200 is recognized as an
XP12000 Disk Array. To recognize the connected external array as the SVS200, use the microcode
version that supports the SVS200 (which is microcode version 50-07-0X-XX/XX or higher). If you used an
earlier microcode version that does not support the SVS200 to map the SVS200 volumes, delete the
mapping setting, and then change the microcode version to the one that supports the SVS200.

Path status and examples of recovery procedures (SVS200)
Figure 24 shows examples of the recovery procedures when the path status is not normal. When the path
status is not normal, use ”Troubleshooting External Storage XP” on page 121 and this table to recover the
path status. If you cannot restore the path, contact your HP account support representative.
Table 24 Path status and examples of recovery procedures (SVS200)
Path Status Examples of Recovery Procedure

External device setting changed • LUN Manager might have changed the LU paths’ settings.
Check the LU paths’ settings. If the LU paths’ settings changed, change
the settings back to the ones when the volume was mapped. Or use
External Storage XP to perform the Delete LU operation, and perform
the Add LU operation again.
• LUN Security XP Extension might have changed the volume’s access
attribute.
Illegal request • The volume might have been set as a pair volume for data copy.
Check if the volume is set as a pair volume of Business Copy XP,
Continuous Access XP, Continuous Access XP Journal, or some other
copy program. If the volume is set as a pair volume, the volume might
be protected because of the pair status. If the volume is protected,
change the pair status or delete the pair.
attribute.
Response error • The volume might have been set as a pair volume for data copy.
Check if the volume is set as a pair volume of Business Copy XP,
Continuous Access XP, Continuous Access XP Journal, or some other
copy program. If the volume is set as a pair volume, the volume might
be protected because of the pair status. If the volume is protected,
change the pair status or delete the pair.
attribute.
Cannot detect port • There is a problem with connection to the external array. The following
• The fibre cable is not physically connected properly.
• The topology setting does not match between the external and
target ports.
Check if the fibre cable is connected properly, and then set the Fibre
Channel port properly using LUN Manager.
• LUN Manager might have enabled LUN security.
Check if the LUN security is enabled or not. If LUN security is enabled,
disable LUN security.
Connecting EVA arrays

Identifying logical volumes of EVA arrays (using Characteristic 2)
When the connected external array is an EVA array, LUNs are displayed as Characteristic in External
Storage XP’s panes.

If you search for logical volumes by specifying the WWN that indicates EVA Port A in the configuration,
such as in Figure 68, logical volumes named LUN 1 and LUN 2 are found for both HostGroup-1 and
HostGroup-2. In this case, two different logical volumes with the same name, such as LUN 1 and LUN 2,
are found as logical volumes that can be connected from EVA Port A, but you can only tell which LUN 1
and LUN 2 belong to HostGroup-1 or HostGroup-2 by examining the Characteristic field.
In the configuration in Figure 68, you can identify logical volumes by referring to Characteristic2 in
External Storage XP’s panes. The first 32 characters of Characteristic2 indicate the World Wide LUN
Name found on the EVA array. You can identify the EVA array’s logical volume by this World Wide LUN
Name.
Figure 68 Configuration example for which logical volumes can only be identified by characteristic
Alternate path’s behavior when an EVA array is connected

When an EVA array is connected, the alternate path’s behavior differs depending on the EVA array’s
microprogram version.
The alternate path’s behavior differs between EVA arrays of the microprogram version shown below and
EVA arrays of earlier microprogram versions:
• Array type: EVA3000/5000
microprogram version 4.000 or later
• Array type: EVA4000/6000/8000
microprogram version 5.031 or later
To replace the EVA array’s microprogram, check whether the alternate path’s behavior changes as a result
of changing the microprogram version. If the alternate path’s behavior changes, perform External Storage
XP’s Delete LU operation to release the setting for the EVA array volume’s mapping before you actually
replace the microprogram.
See the EVA array manuals for more information how the alternate path’s behavior changes.

B Required volume capacity for emulation types
When mapping an external LU as a local array internal LDEV, you must specify the mapped volume’s
emulation type.
The capacity required for the LDEV to be mapped is the total capacity of the data area for storing actual
user data and the control information area for storing control information. The capacity of the data area
(called base data area capacity) and the capacity of the control information area (called control
information area capacity) depend on the emulation type. The minimum capacity of the data area for
Customized Volume (CV) (called minimum data area capacity) also depends on the emulation type.
Use the following equation to calculate the minimum capacity required for an LDEV (minimum LDEV
capacity) for each emulation type:
Minimum LDEV capacity = Minimum data area capacity + control information area capacity
If the external LU’s capacity is less than this minimum LDEV capacity, the emulation type cannot be
specified.
Use the following equation to calculate the base LDEV capacity for each emulation type:
Base LDEV capacity = Base data area capacity + Control information area capacity
When the external LU’s capacity is less than the emulation type’s base LDEV capacity, one CV is created
in the external LU as you map the volume. When the external LU’s capacity is more than the emulation
type’s base LDEV capacity, the external LU is divided into multiple LDEVs, each having the base LDEV
capacity. Because the OPEN-V emulation type supports a maximum of 2TB of the volume, one LDEV is
always created when the external LU is mapped.
If you use Volume Manager, you can divide the mapped external LU into a maximum of 256 CVs.
However, LDEVs as they are mapped are used for the OPEN-L emulation type because Volume Manager
is not applicable to the OPEN-L emulation type.
The following restrictions apply for the external LU’s maximum usable capacity:
• The external LU can be divided into a maximum of 256 CVs. Therefore, the external LU’s maximum
capacity must meet the following equation:
Maximum usable capacity of the external LU ≤ Base LDEV capacity × 256
• Each emulation type has its own maximum usable capacity. Table 25 shows the external LU’s
maximum usable capacity for each emulation type.
Table 25 External LU’s maximum usable capacity
Emulation type External LU’s maximum usable capacity

OPEN-V 2 TB
OPEN emulation type other than OPEN-V 575.98 GB
3380 mainframe emulation type 575.98 GB
3390 mainframe emulation type 695.98 GB
According to these restrictions, you can determine the external LU’s maximum usable capacity for each
emulation type. When the mapped external LU’s capacity is more than the maximum capacity of the
specified emulation type, a certain part of the external LU cannot be used.

Figure 69 shows the relationship of the minimum LDEV capacity, base LDEV capacity, minimum data area
capacity, base data area capacity, and control information area capacity.
Figure 69 LDEV capacity

Figure 70 shows how to determine the volume capacity using the example of the OPEN-3 case.
Figure 70 Calculating LU capacity (OPEN-3 example)

Table 26 lists the minimum data area capacity, base data area capacity, and control information area
capacity for each emulation type. For the OPEN-L emulation type, CVs cannot be created. Therefore, the
base data area capacity and minimum data area capacity for OPEN-L emulation type are the same. For
the OPEN-V emulation type, the base data area capacity is not listed because there is no concept of the
base data area capacity.
Table 26 LDEV capacity information for each emulation type
Emulation type Minimum data area Base data area Control information
capacity (blocks) capacity (blocks) area capacity (blocks)
3380-3 72,000 4,808,160 10,080
3380-3A 72,000 4,808,160 10,080
3380-3B 72,000 4,808,160 10,080
3380-3C 72,000 4,808,160 10,080
3380-K 72,000 3,823,200 10,080
142 Required volume capacity for emulation types

Table 26 LDEV capacity information for each emulation type (continued)
Emulation type Minimum data area Base data area Control information
capacity (blocks) capacity (blocks) area capacity (blocks)
3380-KA 72,000 3,823,200 10,080
3380-KB 72,000 3,823,200 10,080
3380-KC 72,000 3,823,200 10,080
3390-3 87,000 5,809,860 10,440
3390-3A 87,000 5,809,860 10,440
3390-3B 87,000 5,809,860 10,440
3390-3C 87,000 5,809,860 10,440
3390-3R 87,000 5,809,860 10,440
3390-9 87,000 17,429,580 43,500
3390-9A 87,000 17,429,580 43,500
3390-9B 87,000 17,429,580 43,500
3390-9C 87,000 17,429,580 43,500
3390-L 87,000 57,002,400 40,020
3390-LA 87,000 57,002,400 40,020
3390-LB 87,000 57,002,400 40,020
3390-LC 87,000 57,002,400 40,020
3390-M 87,000 114,004,800 92,220
3390-MA 87,000 114,004,800 92,220
3390-MB 87,000 114,004,800 92,220
3390-MC 87,000 114,004,800 92,220
OPEN-3 72,000 4,806,720 11,520
OPEN-8 72,000 14,351,040 38,880
OPEN-9 72,000 14,423,040 38,880
OPEN-E 72,000 28,452,960 27,360
OPEN-L 71,192,160 71,192,160 10,080
OPEN-V 96,000 – 0
Table 27 lists the base LDEV capacity, minimum LDEV capacity, maximum external LU capacity, and
number of LDEVs that can be defined for the external LU with maximum capacity. For the OPEN-L
emulation type, the base LDEV capacity and the minimum LDEV capacity are the same because CVs
cannot be created. For the OPEN-V emulation type, the base LDEV capacity is not listed because there is
no concept of the base LDEV capacity.

Table 27 Volume capacity information for each emulation type
Emulation type Base LDEV Minimum LDEV Maximum capacity Maximum number
capacity (blocks) capacity (blocks) of external LU of LDEVs when
(blocks) maximum capacity
of external LU is
mapped
3380-3 4,818,240 82,080 1,207,934,976 250
3380-3A 4,818,240 82,080 1,207,934,976 250
3380-3B 4,818,240 82,080 1,207,934,976 250
3380-3C 4,818,240 82,080 1,207,934,976 250
3380-K 3,833,280 82,080 981,319,680 256
3380-KA 3,833,280 82,080 981,319,680 256
3380-KB 3,833,280 82,080 981,319,680 256
3380-KC 3,833,280 82,080 981,319,680 256
3390-3 5,820,300 97,440 1,459,588,096 250
3390-3A 5,820,300 97,440 1,459,588,096 250
3390-3B 5,820,300 97,440 1,459,588,096 250
3390-3C 5,820,300 97,440 1,459,588,096 250
3390-3R 5,820,300 97,440 1,459,588,096 250
3390-9 17,473,080 130,500 1,459,588,096 83
3390-9A 17,473,080 130,500 1,459,588,096 83
3390-9B 17,473,080 130,500 1,459,588,096 83
3390-9C 17,473,080 130,500 1,459,588,096 83
3390-L 57,042,420 127,020 1,459,588,096 25
3390-LA 57,042,420 127,020 1,459,588,096 25
3390-LB 57,042,420 127,020 1,459,588,096 25
3390-LC 57,042,420 127,020 1,459,588,096 25
3390-M 114,097,020 179,220 1,459,588,096 12
3390-MA 114,097,020 179,220 1,459,588,096 12
3390-MB 114,097,020 179,220 1,459,588,096 12
3390-MC 114,097,020 179,220 1,459,588,096 12
OPEN-3 4,818,240 83,520 1,207,934,976 250
OPEN-8 14,389,920 110,880 1,207,934,976 83
OPEN-9 14,461,920 110,880 1,207,934,976 83
OPEN-E 28,480,320 99,360 1,207,934,976 42
OPEN-K 3,674,880 84,960 940,769,280 256
OPEN-L 71,202,240 71,202,240 1,139,235,840 16
OPEN-V – 96,000 4,294,967,296 1
144 Required volume capacity for emulation types

C Adjusting volume capacity for copy pair setting
When creating a Business Copy XP or Flex Copy XP copy pair, the S-VOL’s capacity must be the same as
the P VOL. To set a copy pair’s desired volume, you might need to adjust the volume capacity. This
section describes the procedure to adjust the volume capacity.
Copying data from external arrays (using external LUs as P-VOLs)

For A, B, and C in the following description, see Figure 71.
To adjust the volume capacity to create a pair:
1. Map the external LU (A) as an internal LDEV (B) of the local array. Ensure that the volume’s emulation
type is OPEN-V.
2. Select the local array volume (C) with the same capacity as the mapped internal LDEV (B) or a bigger
capacity than the mapped internal LDEV (B). The volume’s (C) emulation type must be OPEN-V.
3. If you select the local array volume (C) with a bigger capacity than the mapped internal LDEV (B),
create the CV with the same capacity as the mapped internal LDEV (B) out of the local array volume
(C) using Volume Manager. For more information, see the HP StorageWorks LUN Configuration and
NOTE: When using Volume Manager to create a CV with the same capacity as the mapped
internal LDEV (B), specify the CV’s capacity according to the Blocks capacity displayed in the
Capacity column on the LDEV Information pane in External Storage XP (see ”Checking an external
LU’s status (LDEV Information)” on page 95).
NOTE: To create a Continuous Access XP pair with a volume of an XP1024/XP128 Disk Array,
you might not be able to create a CV with the same capacity as the internal LDEV (B) because
Volume Manager does not allow you to specify the capacity in blocks. In this case, you cannot
create a Continuous Access XP pair.
4. Create a copy pair.
Figure 71 Copying data from external arrays (using external LUs as P-VOLs)
Copying data to external arrays (setting external LUs as S-VOLs)

For A, B, and C in the following description, see Figure 72.
To adjust the external LU’s capacity to create a pair:

1. Map the external LU (A) as an internal LDEV (B) of the local array. Set the emulation type to the same
as the copy source volume (C).
2. Check the capacity of the internal LDEV (B) to which the external LU (A) is mapped. If the mapped
internal LDEV’s (B) capacity is not same as the copy source volume (C), use Volume Manager to create
a CV with the same capacity as the copy source volume (C) out of volume (B).
3. Create a copy pair.
Figure 72 Copying data to external arrays (setting external LUs as S-VOLs)
146 Adjusting volume capacity for copy pair setting

D Using an XP12000/XP10000/SVS200 with an
EVA3000/5000 external storage
Preface
This appendix describes the procedure and relevant recommendations for configuring HP StorageWorks
XP12000/XP10000/SVS200 and EVA3000/5000 Disk Arrays where the EVA is used as a highly
available external storage array.
The XP firmware version and external firmware version must be compatible. Consult your HP account
support representative for the latest firmware version required.
Configuration
Physical array connections
The XP12000/XP10000/SVS200 can use multiple Fibre Channel connections to an attached EVA. The
two XP12000/XP10000/SVS200-EVA configuration examples in the following sections—minimum and
expanded—are designed with Fibre Channel switches to maximize the ability of separate hosts to directly
use the EVA in addition to the XP12000/XP10000/SVS200. This also allows for connecting hosts to the
EVA that run software applications such as HP StorageWorks Command View EVA and System Insight
Manager so the EVA can be managed in-band as well as monitoring its operational status. The
XP12000/XP10000/SVS200 does not forward detailed SIM (status) messages the EVA generates during
operation. Monitoring all EVAs must be done by a host connected in-band to the EVA via a Fibre
Channel.
Minimum physical configuration for HA
For highly available (HA) functionality to be possible, each EVA controller must be connected to the
XP12000/XP10000/SVS200 so there is at least one fiber channel path from each
XP12000/XP10000/SVS200 cluster to one of the separate EVA controllers through their respective Fibre
Channel switch connections. Figure 73 illustrates this connection.
Figure 73 XP12000/XP10000/SVS200-EVA minimum connections for HA

This configuration allows the XP12000/XP10000/SVS200 to execute basic failover and failback
operations with the EVA array subordinated. Unlike the MSA series of arrays, the EVA allows access to

different logical units (LUs) from each of the two EVA controllers at the same time. This allows an attached
host (or XP12000/XP10000/SVS200) to use both paths shown in Figure 73 for processing I/O
simultaneously.
Expanded configuration
To better realize the performance capability of an EVA being used as an external storage array, add the
connections illustrated in Figure 73 so each of the two XP12000/XP10000/SVS200 clusters have at
least one Fibre Channel path to each of the two EVA controllers through their respective Fibre Channel
switches and switch connections as described previously. This configuration allows for a greater
performance potential in that more than one XP port can drive a single active EVA port to a particular
EVA LU. An example of this configuration is illustrated in Figure 74.
Figure 74 XP12000/XP10000/SVS200-EVA connections for expanded performance
Creating new EVA host objects for the XP12000/XP10000/SVS200

The EVA family of arrays organizes its LU presentations to attached hosts by defining and manipulating
host objects. Each host object consists of the following information:
• Host name
• IP address (optional)
• Operating system
• World wide port names of host HBAs
After this object is created for a given host, EVA Vdisks (virtual LUs) can be assigned to that host.
For the XP12000/XP10000/SVS200 to use LUs resident on the attached EVA, a host object must be
defined for the XP12000/XP10000/SVS200.
Use HP StorageWorks Command View EVA to create EVA host objects. Set Host name to a unique name
representing the XP12000/XP10000/SVS200, and set Port WW Name to the world wide port name of a
148 Using an XP12000/XP10000/SVS200 with an EVA3000/5000 external storage

connected XP12000/XP10000/SVS200 external port. Additionally, set Host OS to Microsoft Windows
for the XP12000/XP10000/SVS200 to use the EVA LUs correctly. Figure 75 illustrates this step.
Figure 75 Creating EVA host objects

After the host object is created, add the remaining XP12000/XP10000/SVS200 external ports by
selecting the new host object, and clicking the Ports tab. For each port, enter the world wide port name,
and click Add Port. Figure 76 illustrates this step.
Figure 76 Adding ports to XP12000/XP10000/SVS200 host objects
Creating and presenting EVA Vdisks

Vdisks created on the XP12000/XP10000/SVS200-attached EVA3000/5000 must have Path A
Failover/Failback or Path B Failover/Failback selected for Preferred path/mode. Figure 77 illustrates this
step. Path A Failover/Failback indicates that the given Vdisk is hosted from EVA Controller A and
migrates via failover function to Controller B if the need arises. To achieve better performance for a given

configuration, HP recommends defining Vdisk settings so the number of Vdisks presented to the XP is
balanced between the two EVA controllers and across controller ports.
Figure 77 Selecting Vdisk’s Preferred path/mode

After EVA Vdisks are created, they can be assigned to the previously defined
XP12000/XP10000/SVS200 host object; thereby presenting them to the XP12000/XP10000/SVS200.
Figure 78 illustrates this step.
Figure 78 Presenting Vdisks
Defining XP12000/XP10000/SVS200 external ports

For the XP12000/XP10000/SVS200 to access and use storage present on the EVA array, EVA-attached
XP12000/XP10000/SVS200 ports must be functionally redefined as dedicated external storage Fibre
Channel ports. Use Command View XP or XP Remote Web Console to define these EVA-connected

XP12000/XP10000/SVS200 ports to external ports. On the Port Operation pane in External Storage,
right-click on the desired ports, and select Change to External. Figure 79 illustrates this step.
Figure 79 Defining XP12000/XP10000/SVS200 external ports

After external ports are defined, EVA LUs presented to the XP12000/XP10000/SVS200 can be defined
as XP external storage LDEVs.
Defining XP12000/XP10000/SVS200 external storage LDEVs

Use Command View XP or XP Remote Web Console to define external storage LDEVs. On the LU
Operation pane in External Storage, select one of the two EVA controller port world wide port names in
the Device tree. In the Device list, right-click on one or more EVA LUs being presented through the
controller previously selected, and select Add LU. Figure 80 illustrates this step.

NOTE: You must select external storage LUs through the presenting controller. Failure to do so results in
new external LDEVs being placed in a blockade state shortly after a host attempts to access them.
Figure 80 Selecting EVA LUs

After you select an external logical unit (LU), the Add LU pane appears. At this point, you can configure
each individual external LU by choosing options such as the emulation type, the number of LDEVs (CVS is
used), and the LU’s unique LDEV identifiers within the XP12000/XP10000/SVS200. Figure 81 illustrates
this step.
Figure 81 XP External LDEV definition

After this step is complete and external storage LDEVs are created, these LDEVs can be presented to any
XP12000/XP10000/SVS200-attached host for immediate use. For more information about assigning
XP12000/XP10000/SVS200 LDEVs to an XP12000/XP10000/SVS200-attached host, 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.
Recommendations
Performance considerations for using EVAs as external storage
Unlike the MSA family of arrays, an EVA can be configured to perform I/O operations with both its
controllers on separate EVA LUs simultaneously (Active/Passive capability). Therefore, it is possible to
realize more/better performance from an EVA in an external storage role by creating multiple
connections from the XP12000/XP10000/SVS200 external port to a given EVA controller (remembering
that the EVA3000/5000 models have two ports per controller) than a similar configuration with an MSA
(only one port per controller). In spite of this, HP strongly cautions you to carefully weigh the financial cost
of a dedicated XP12000/XP10000/SVS200 external port versus the benefit of any added EVA external
storage performance. For firmware revisions specified in ”Preface” on page 147, a host-connected EVA
port can out-perform an external storage-connected XP12000/XP10000/SVS200 external port by an
estimated ratio of as much as 4 to1 when the number of usable I/O operations per second (IOPS) is
considered. It is for this reason that you must be careful when choosing the number of
XP12000/XP10000/SVS200 external ports to dedicate to accessing an attached EVA.
Defining alternate paths

The XP12000/XP10000/SVS200 supports up to eight defined Fibre Channel paths to an external
storage LDEV. HP recommends verifying that each EVA3000/5000-resident external storage LDEV has at
least one alternate path to the controller to which it does not have a preferred path assigned. If additional
redundancy is desired, configure more paths. These paths, however, are not used for I/O unless a fault
occurs and the EVA is forced to failover to these paths. Use Command View XP or XP Remote Web
Console to verify and configure external storage LDEV paths. On the LU Operation pane in External
Storage, right-click on an external LU, and select Path Settings. The Path Setting pane appears. Right-click
on the undefined paths in the Alternate Paths list, and select Add Path. Figure 82 illustrates this step.
Figure 82 Configuring alternate paths

In addition to adding and deleting paths, use this pane to change a path’s priority. Right-click on the path,
and select Priority Up or Priority Down.
For failover operations, the XP12000/XP10000/SVS200 attempts to fail between defined paths to a
given external LDEV provided that it does not encounter another previously active (prior to path fault)
path. Unlike the MSA, failback operations for EVA-resident external LDEVs is automatic.

Troubleshooting
• Be careful to define an external storage LDEV presented to the XP12000/XP10000/SVS200 by the
EVA from the EVA controller that is presently serving its associated LU in an active status.
• If you attempt to define an LDEV from an LU via that LU’s passive controller, the resulting external
storage LDEV is placed in a blockade state.

E Configuring MSA1000/1500 as external arrays
NOTE: Externally connected MSAs must not contain Continuous Access XP P-VOLs or S-VOLs.
Configuring external array LUs, host mode, and ports

This appendix describes how to configure the MSA external array. For other arrays, see the
documentation for that external array.
You do not need to configure the SAN topology parameters on the MSA array. The MSA automatically
detects whether it is connected to the local array via a switch or point-to-point connection, and adjusts its
parameters accordingly.
If no LUNs are available on the MSA, you must create them.
1. Set the channel transfer speed according to the configuration.
Generally, select Auto Negotiation.
2. Use Selective Storage Presentation to configure the MSA LUs involved with External Storage XP.
Connecting MSA1000/1500
If you connect an HP StorageWorks Modular Smart Array (MSA) with two controllers (highly
recommended) as an external array, set the port’s host mode to Tru64 and use Selective Storage
Presentation.
NOTE: If only a single MSA controller will be known to the XP12000/XP10000/SVS200, using
Selective Storage Presentation in the MSA ACU is optional and the host mode may be set to Windows.
For the purposes of this document, it is assumed that two MSA controllers are in use, which greatly
improves the array’s availability and allows primary copies of important data to be stored on the MSA.
See the following documents for information about configuring MSA:

• HP StorageWorks Modular Smart Array quickspecs
• HP Array Configuration Utility User Guide
NOTE: References to MSA generally refer to both the MSA1000 and the MSA1500 (both with an
Active/Passive controller). Although the standby MSA controller may connect to the same
XP12000/XP10000/SVS200 port as the active MSA controller (shown in Figure 83), HP recommends
that it connect to an XP port on a different XP cluster.
Figure 83 Example: Connecting an MSA array

The following is a summary of the port setting status of the local array when you connect the MSA external
array.
Topology Fabric ON Fabric OFF
Loop Supported Supported
Point-to-Point Supported Not supported
Setting up the MSA

To set up the MSA for use as an external array connected to the XP12000/XP10000/SVS200, perform
the following steps:
1. Define the MSA Array Object.
2. Define the MSA LU.
3. Use MSA Selective Storage Presentation to institute LUN security.
After defining the MSA array object, specify individual storage LUs within the array object. At this point,
institute LUN security on the MSA using the ACU Selective Storage Presentation (SSP) functionality.
Use the HP StorageWorks Array Configuration Utility (ACU) to configure the MSA for its role as an
external array. ACU runs from a server attached to the MSA via a Fibre Channel path.
The MSA Array does not require any special firmware level or hardware additive to be usable by External
Storage XP as long as the firmware level in use supports the appropriate host mode setting (for example,
Windows or Tru64).
NOTE: Download the ACU and ACU Online User Guide from the following address:
http://h18004.www1.hp.com/products/servers/proliantstorage/software-management/acumatrix/ind
ex.html
Defining MSA array objects

Use the Array Configuration Utility (ACU) to define at least one internal MSA array object (for instance,
“A”) when first setting up the array. After defining an array object, specify LUs within that array object.
Figure 84 Defining MSA array objects with the ACU
Calculating MSA LU size and defining LUs

The ACU used for configuring the MSA uses an optimization algorithm to calculate the user size of a new
LU given a user-specified size in MB (Figure 85). Because you cannot bypass or disable the optimization
algorithm, you must compensate for this optimization so that MSA LUs are created at the correct size.
When requesting a new LU through the ACU, make the request 2 to 3 MB larger than needed for
156 Configuring MSA1000/1500 as external arrays

presentation to the XP12000/XP10000/SVS200. For example, suppose you want to create a 40 GB
(40960 MB) LU on the MSA for use as XP12000/XP10000/SVS200 external storage. If you request only
the exact size needed, the ACU optimizes the LU to a size of 40959 MB, which is 1 MB smaller than
needed. In this case, the optimization algorithm the ACU uses can be compensated for by specifying a
size of 40963 MB, which results in the correct size of 40960 MB (40 GB).
Figure 85 Defining MSA LUs with ACU
Selective Storage Presentation

You must institute LUN security on MSAs using the ACU Selective Storage Presentation (SSP) feature
(Figure 86). Use SSP to limit access to individual MSA LUs (in this case, logical drives 1 and 2) by
selected host (or XP12000/XP10000/SVS200) HBA world wide names. When using SSP, set the
operating system mode corresponding to the XP12000/XP10000/SVS200 array port WWN to TRU64.
For more information about configuring the MSA using the ACU, see the ACU Online User Guide.
Figure 86 Configuring SSP with ACU

158 Configuring MSA1000/1500 as external arrays
Index
A Cache Mode
Active/Standby (A/S) controllers 27 Auto Map window 82
ACU (Array Configuration Utility) 156 LU window 75
ACU Selective Storage Presentation (SSP) 157 remote command devices 117
Add LU (Auto) operation 80 restrictions 34, 37
Add LU operation 77 settings 21
Add LU window 73 cache, managing 45
alternate paths capacity, required 141
adding to multiple external LUs 91 Check Paths & Restore Vol. command
canceling 91 powering arrays on and off 27, 28, 29
changing 91 restoring external LUs 100, 101
defining 22, 86, 89 restrictions 35
deleting to multiple external LUs 93 troubleshooting 125
EVA arrays 139 Check Paths, Port Operation list 104
LU Operation pane 56 Check Paths, WWN list 102
Path Setting window 86 CLPR 21, 75
ports 76 Command View XP
priority of 22, 25, 89 about 13
Select Paths pane 76 troubleshooting 121
settings 75 Compatible PAV for IBM z/OS 38
switching I/O execution paths to 23 Configuration File Loader 38
XP12000/XP10000/SVS200 and EVA3000/5000 connecting arrays
153 EVA 138
applications, combining with External Storage XP 37 SVS200 137
Array Configuration Utility (ACU) 156 TagmaStore 130
arrays, connecting Thunder 9500V 127
SVS200 137 XP1024/XP128 135
TagmaStore 130 XP12000/XP10000 134
Thunder 9500V 127 XP512/XP48 136
XP1024/XP128 135 connection status 61, 100
XP12000/XP10000 134 Continuous Access XP
XP512/XP48 136 remote command devices 117
arrays. See external arrays; local arrays Continuous Access XP external LUs 37, 39
Asymmetrical Active/Active (AAA) controllers 26 Continuous Access XP Journal
attributes, mapping 20 remote command devices 117
audience, documentation 9 Continuous Access XP Journal external LUs 38, 40
Auto LUN XP conventions, document 10
features 13 copy pair settings, adjusting volume capacity 145
volume migration 39 CU:LDEV list 76, 80
customer support 10
B
D
Blockade status
restoring 95, 96, 101 deinstalling External Storage XP 31
troubleshooting 122 Delete LU command 104
Business Copy XP 38, 41 Device Error message 126
Device list 58
C Device tree 57
Disconnect Paths 104
Cache LUN XP 37
Disconnect Subsystem command
disconnecting external LUs 98
powering arrays on and off 27, 28, 29
restrictions 35
troubleshooting 125

Disconnect Volume command external arrays
disconnecting external LUs 98, 100 A/S 27
powering arrays on and off 27, 28, 29 AAA 26
restrictions 35 Add LU window 73
troubleshooting 125 compatible storage devices 15
Discovery operation, troubleshooting 125 configuring 155
disk errors, NAS Blade system 108 connection status 61
document copying data from 145
conventions 10 copying data to 145
feedback 11 defined 13
prerequisites 9 Device List 58
related documentation 9 Device list 58
Device tree 57
E errors, NAS Blade system 108
emulation types Fibre Channel connections 14
Add LU window 74 mapping 13, 20
Auto Map Setting window 81 mapping restrictions 14, 32
capacities 32, 141 MSA configuration 155
HDD types 36 NAS Blade systems, troubleshooting 107
remote command devices 117 path errors 110, 111
restrictions 32 port settings 20, 72, 103
setting 21 powering on and off 27, 29
errors remote command devices 115
NAS Blade system 108 restarting NAS Blade system 108
errors, External Storage XP 121 restoring external LUs 100, 101
ES XP cache mode 37 restoring volumes 101
EVA3000/5000 arrays restrictions 36
about 147 status 95
alternate paths 153 stopping NAS Blade system 107, 108
configuring 147 stopping paths 102
connecting 138 SVS200, connecting 137
creating new EVA host objects 148 system parameters 127
expanded configuration 148 system requirements 15
external ports, defining 150
external storage LDEVs 151
HA requirements 147
performance considerations 153
troubleshooting 154
Vdisks 149
160
external LUs HP
Add LU 77 storage web site 11
alternate paths, adding to multiple 91 Subscriber’s choice web site 10
alternate paths, defining 22, 86 technical support 10
alternate paths, deleting to multiple 93 HP StorageWorks XP Tiered Storage Manager 13
Business Copy XP operations 41
capacities 32, 141 I
configuring 71 I/O execution paths, switching to alternate paths 23
connection status 100 Initiator/External MIX mode 117, 119
Continuous Access XP Journal operations 40 installing External Storage XP 19
Continuous Access XP operations 39 internal LDEVs
defined 13 Add LU 77
Delete LU command 104 alternate paths 22, 86
Device List 58 capacity 32, 141
disconnecting 98 configuring 71
emulation type, setting 74, 81 defined 13
groups 20 groups 20
HDD types 36 mapping all at once 78
LU Operation pane 56 mapping external LUs 73
mapping 73 mapping, defined 13
mapping all at once 78 troubleshooting 121
mapping multiple 80 Interval 76
mapping restrictions 20 Intervention Required message 126
mapping, defined 13 IO Suppression mode
maximum number of 19 Auto Map Setting window 81
P-VOLs 145 LU window 74
restoring 96, 100, 101 remote command devices 117
restrictions 32 restrictions 33
Snapshot XP operations 42 settings 21
status 58, 95
stopping paths 102 L
S-VOLs 145 LDEV Information window 95
troubleshooting 121 LDEV Restore command 101
using data in 30 LDEVs
Volume Detail window 97 capacity 74, 141
volume migration 39 emulation types supported 13
writing data to 29 Information window 95
External port setting 20 See also internal LDEVs
Select window 83
F status 95
features 13 limitations
feedback, documentation 11 External Storage XP operations 32
Filter button 66 Initiator/External MIX mode 120
firmware supported 9 remote command devices 117
Flex Copy pane 55 Linear button 75, 78
Flex Copy XP 13 local arrays
fonts, document conventions 10 capacity 141
configuring 155
G connection status 61
group number 74, 81 defined 13
groups, external LUs 20 Fibre Channel connections 14
mapping restrictions 14
H port settings 20, 72
HA (highly available) functionality requirements 147 powering on and off 27, 28
HDD types 36 remote command devices 115
help, obtaining 10, 11 stopping paths 102
highly available (HA) functionality requirements 147 system requirements 15
volume migration 39
LU Operation pane 56

LUN Security XP Extension 38 path status
LUs. See external LUs SVS200 138
TagmaStore subsystems 133
M Thunder 9500V Series subsystems 130
managing cache 45 troubleshooting 121
manuals 9 XP12000/XP10000 134
mapping XP512/XP48 136
access restrictions 14 paths
Add LU command 77 disconnecting 104
Add LU window 73 errors, external arrays 110, 111
all external LUs at once 78 primary 22
alternate paths, defining 22, 86, 89 restoring 104
attributes 20 See also alternate paths
defined 13 performance 36, 153
Delete LU command 104 phone support 10
deleting 35 platforms supported 9
emulation type, setting 21 Port Operation list 69
external LUs 20, 73 Port Operation pane 67
groups 20 Port Operation tree 68
LU Operation pane 56 ports
multiple external LUs 80 alternate paths 76
remote command devices 115, 117 Device tree 57
restrictions 14, 20, 32, 36 external array settings 72, 103
troubleshooting 121 limitations 32
VMA information, displaying 85 list of 68, 69
migration, volume 39 local array settings 72
MSA settings 20, 67
A/S controllers 27 stopping paths 102
array objects 156 SVS200 137
external array configuration 155 troubleshooting 122, 123, 124
LU size, calculating 156 XP12000/XP10000/SVS200, defining 150
restrictions 31, 32 powering arrays on and off
Selective Storage Presentation (SSP) 157 commands 27, 29
Multi mode local 28
defined 22 prerequisites 9
example 24 Preset list 66, 70
multiple storage arrays, accessing 13 primary path 22
priority of alternate paths, changing 89
N P-VOLs 145
NAS Blade systems, troubleshooting
disk errors 108 R
documentation 107 RAID Manager XP 86, 115
path errors 110, 111 Read and Write performance 36
restarting external arrays 107, 108 registration, product 10
stopping external arrays 107, 108 remote command devices
Continuous Access XP 117
O defined 115
OPEN-V mapping 117
initializing data areas 30 restrictions 117
restrictions 32 specifications 115
setting emulation type 21, 74, 81 Remote Web Console
about 13
P troubleshooting 121
restarting NAS Blade system arrays 108
panes 55
Path Setting window 86
162
restoring T
external array volumes 101 TagmaStore AMS subsystems
external LU volumes 102 path status and recovery 133
external LUs 96, 100, 101 port WWNs 132
LDEV Restore 101 serial numbers 132
NAS Blade system arrays 108 system parameters 130
paths to external LUs 102, 104 TagmaStore WMS subsystems
SVS200 138 path status and recovery 133
TagmaStore subsystems 133 port WWNs 132
Thunder 9500V Series subsystems 130 serial numbers 132
XP12000/XP10000 arrays 134 system parameters 130
XP512/XP48 arrays 136 technical support, HP 10
restrictions telephone support 10
External Storage XP operations 32 text symbols, document conventions 10
Initiator/External MIX mode 120 Thunder 9500V Series subsystems
remote command devices 117 path status 130
retention term 86 port WWNs 129
serial numbers and subsystem models 129
S system parameters 127
Select LDEV window 83 Tiered Storage Manager 13
Select Paths pane 75, 76 troubleshooting
Selective Storage Presentation (SSP) 157 External Storage XP 121
settings 19 NAS Blade systems 107
ShadowImage for z/OS 38 XP12000/XP10000/SVS200 and EVA3000/5000
Single mode 154
defined 22 TrueCopy for z/OS 38
example 24, 25, 26, 27
Snapshot XP 38, 42 U
SNMP 38 uninstalling External Storage XP 31
speed 36, 153 Universal Replicator for z/OS 38
SSID window 79 user guides 9
SSP (Selective Storage Presentation) 157 using data in external LUs 30
status
Blockade 101 V
connection 100
Vdisks, creating and presenting 149
external LUs 58, 95
VMA information, displaying 85
SVS200 138
VMA setting 74
TagmaStore subsystems 133
volume capacity
Thunder 9500V Series subsystems 130
adjusting 145
troubleshooting 121
required 141
WWN 61
Volume Detail window 97
XP1024/XP128 arrays 135
Volume Manager 37
XP12000/XP10000 arrays 134
Volume Retention Manager 38
XP512/XP48 arrays 136
Volume Security 38
stopping
NAS Blade system arrays 107, 108
W
stopping external LU paths 102, 104
storage platforms supported 9 web sites
Subscriber’s choice, HP 10 HP documentation 9
support, technical 10 HP storage 11
supported storage platforms and firmware 9 HP Subscriber’s choice 10
S-VOLs 145 support 10
SVS200 137 writing data to mapped external LUs 29
switching I/O execution paths to alternate paths 23 WWN List 61
symbols, document conventions 10 WWN paths
system parameters for external arrays 127 restoring 102
system requirements 15, 19 stopping 102
WWN Tree 60

X
XP Remote Web Console
about 13
troubleshooting 121
XP1024/XP128 arrays, connecting 135
XP12000/XP10000/SVS200 arrays
about 147
alternate paths 153
configuring 147
creating new EVA host objects 148
expanded configuration 148
external ports, defining 150
external storage LDEVs 151
HA requirements 147
performance considerations 153
troubleshooting 154
Vdisks 149
164

HP - ExternalStorageUG Rootsan Technologies PVT LTD

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP - ExternalStorageUG Rootsan Technologies PVT LTD

Uploaded by

Copyright:

Available Formats

HP StorageWorks

External Storage XP user guide

Part number: T1706-96006

External Storage XP user guide

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

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

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

3 Managing cache with external storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

External Storage XP user guide 3

4 External Storage XP panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5 Configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

7 Remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8 Troubleshooting External Storage XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

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

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

External Storage XP user guide 5

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

External Storage XP user guide 7

Supported storage platforms and firmware

External Storage XP user guide 9

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, bold text Emphasized monospace text

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

External Storage XP user guide 11

External Storage XP features

External Storage XP user guide 13

Figure 1 External Storage XP concept

14 Overview of connecting external arrays

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

• External array (second array)

Storage arrays that can be connected as external arrays

Table 2 Storage arrays that can be connected as external arrays

Storage array Notes

External Storage XP user guide 15

Storage array Notes

16 Preparing for External Storage XP operations

Storage array Notes

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

External Storage XP user guide 17

Storage array Notes

SANRISE9500V series subsystem • “SANRISE95xxV series subsystem” indicates the

SANRISE2000 series subsystem • “SANRISE2000 series subsystem” indicates the

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

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

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

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

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

18 Preparing for External Storage XP operations

External Storage XP requirements

Required products • HP StorageWorks Command View XP version 2.0 or later, or

Maximum number of FC paths that can exist 8

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

Installing External Storage XP

Preparing for External Storage XP settings

External Storage XP user guide 19

External LU attributes set by mapping

20 Preparing for External Storage XP operations