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

98 Configuring external LUs
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.
• You cannot execute the Disconnect Subsystem or Disconnect Volume command for external LUs that
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.