HP StorageWorks External Storage XP user guide (T1706-96006, June 2006)
Table Of Contents
- HP StorageWorks External Storage XP user guide
- Contents
- About this guide
- 1 Overview of connecting external arrays
- 2 Preparing for External Storage XP operations
- System requirements
- External Storage XP requirements
- Installing External Storage XP
- Preparing for External Storage XP settings
- Powering arrays on or off
- Using mapped external LUs from the host connected to the local array
- Uninstalling External Storage XP
- Limitations on External Storage XP operations
- Figure 11 Example of external LU with 2 TB or less
- Figure 12 External LU capacity is larger than the specified emulation type’s basic capacity (OPEN-3 example)
- Figure 13 External LU capacity is smaller than the specified emulation type’s basic capacity
- Table 4 When external LU’s emulation type is OPEN
- Table 5 When external LU’s emulation type is for mainframes
- Combining External Storage XP with other HP StorageWorks products
- 3 Managing cache with external storage
- Guidelines for using cache with external storage
- Determining, setting, or changing the external LU cache mode
- Partitioning cache for external storage
- Determining the number and size of needed partitions
- Creating Cache partitions
- Changing storage system modes
- 4 External Storage XP panes
- 5 Configuring external LUs
- Overview of configuring external LUs
- Setting an external array’s port
- Setting a local array’s port attributes
- Mapping external LUs (Add LU)
- Setting alternate paths for external LUs
- Adding alternate paths by selecting multiple external LUs (Add Paths)
- Deleting alternate paths by selecting multiple external LUs (Delete Paths)
- Checking an external LU’s status (LDEV Information)
- Disconnecting external arrays or LUs
- Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.)
- Restoring external LUs (LDEV Restore)
- Stopping the use of paths to an external LU by specifying an external array’s WWN (Disconnect Paths)
- Restoring paths to an external LU by specifying an external array’s WWN (Check Paths)
- Changing an external array’s port setting
- Stopping the use of paths to an external LU by specifying a local array’s port (Disconnect Paths)
- Restoring paths to an external LU by specifying a local array’s port (Check Paths)
- Deleting external LU mappings (Delete LU)
- 6 Troubleshooting NAS Blade systems that include external arrays
- 7 Remote command devices
- 8 Troubleshooting External Storage XP
- A Notes on connecting external arrays
- Connecting Thunder 9500V subsystems
- System parameters for connecting Thunder 9500V subsystems
- Relationship between serial numbers in the Device list on the LU Operation pane and Thunder 9500V subsystem models
- Relationship between the WWN of the port on the Thunder 9500V subsystem and the controller
- Path status and examples of recovery procedures (Thunder 9500V subsystems)
- Connecting TagmaStore AMS and TagmaStore WMS subsystems
- System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems
- Relationship between serial numbers in the Device list on the LU Operation pane and TagmaStore AMS and TagmaStore WMS subsystem models
- Relationship between the WWN of the port on the TagmaStore AMS or TagmaStore WMS subsystem and the controller
- Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS subsystems)
- Connecting XP12000/XP10000 Disk Arrays
- Connecting XP1024/XP128 Disk Arrays
- Connecting XP512/XP48 Disk Arrays
- Connecting HP 200 Storage Virtualization System as external storage
- Connecting EVA arrays
- Connecting Thunder 9500V subsystems
- B Required volume capacity for emulation types
- C Adjusting volume capacity for copy pair setting
- D Using an XP12000/XP10000/SVS200 with an EVA3000/5000 external storage
- E Configuring MSA1000/1500 as external arrays
- Index

External Storage XP user guide 13
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.