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