Software User Manual
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 139
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.