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
148 Using an XP12000/XP10000/SVS200 with an EVA3000/5000 external storage
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