HP StorageWorks
XP24000/XP20000 External Storage
Software User Guide
Abstract
This guide describes how to connect and map external storage to HP StorageWorks XP24000/XP20000 storage systems.
Topics include instructions for setting ports and paths, mapping volumes, maintaining connections, using spreadsheets to map
external volumes, and mapping remote command devices. The intended audience is a storage system administrator or authorized
service provider with independent knowledge of HP StorageWorks XP storage systems and HP StorageWorks Remote Web
Console.
HP Part Number: T5206-96015
Published: May 2011
Edition: Fifteenth
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Microsoft, Windows, and Windows XP are U.S. registered trademarks of Microsoft Corporation.
Hitachi and Universal Replicator are registered trademarks of Hitachi, Ltd.
ShadowImage and TrueCopy are registered trademarks of Hitachi, Ltd. and Hitachi Data Systems Corporation.
Export Requirements
You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.
Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident
of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.
This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce
Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly
or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified
in the U.S. Export Administration Regulations (15 CFR 744).
Revision History
DescriptionDateEdition
This edition applies to microcode version 60-01-31-00/00 or later.June 2007First
This edition applies to microcode version 60-01-68-00/00 or later.September 2007Second
This edition applies to microcode version 60-02-04-00/00 or later.November 2007Third
This edition applies to microcode version 60-02-25-00/00 or later.January 2008Fourth
This edition applies to microcode version 60-02-48-00/00 or later.April 2008Fifth
This edition applies to microcode version 60-03-04-00/00 or later.June 2008Sixth
This edition applies to microcode version 60-03-24-00/00 or later.September 2008Seventh
This edition applies to microcode version 60-04-04-00/00 or later.December 2008Eighth
This edition applies to microcode version 60-04-13-00/00 or later.February 2009Ninth
This edition applies to microcode version 60-05-00-00/00 or later.June 2009Tenth
This edition applies to microcode version 60-05-00-00/00 or later.August 2009Eleventh
This edition applies to microcode version 60-06-05-00/00 or later.December 2009Twelfth
This edition applies to microcode version 60-07-00-00/00 or later.June 2010Thirteenth
This edition applies to microcode version 60-07-50-00/00 or later.October 2010Fourteenth
This edition applies to microcode version 60-08-01-00/00 or later.May 2011Fifteenth
Contents
1 Overview of HP StorageWorks XP External Storage Software...........................9
XP External Storage..................................................................................................................9
Unifying Copy Operations between Different Storage Systems........................................................9
Unifying Connections from a Host to Different Storage Systems.....................................................10
2 About XP External Storage Operations........................................................12
This chapter provides an overview of XP External Storage.
•“XP External Storage” (page 9)
•“Unifying Copy Operations between Different Storage Systems” (page 9)
•“Unifying Connections from a Host to Different Storage Systems” (page 10)
Unless otherwise specified, the term storage system in this document refers to the following disk
arrays:
•HP StorageWorks XP24000 Disk Array
•HP StorageWorks XP20000 Disk Array
The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer
browser. Actual windows may differ depending on the operating system and browser used. GUI
contents also vary with licensed program products, storage system models, and firmware versions.
XP External Storage
XP External Storage provides the virtualization of a multi-tiered storage area network comprised
of heterogeneous storage systems. It enables the operation of multiple storage systems connected
to an HP XP storage system as if they were all one storage system and provides common
management tools and software. The shared storage capacity comprised of external storage
volumes can be used with storage system-based software for data migration and replication, as
well as any host-based application. Combined with HP StorageWorks XP Auto LUN Software, XP
External Storage provides a data lifecycle management solution across multiple tiers of storage.
The key features and benefits of XP External Storage include:
•Virtualizes external storage attached to the XP storage system
•Enables deployment of multi-tiered storage
•Integrates heterogeneous systems
•Creates extended storage capacity independent of physical location
•Creates new opportunities based on enhanced capability of existing business continuity
software and management tools to manage external storage devices
Unifying Copy Operations between Different Storage Systems
When you copy data between different storage systems, the copy operations are usually different
depending on the storage system that you use.
If you install XP External Storage, you can perform the following copy operations in the same way
as when you copy data between volumes in the XP storage system.
•To copy data between a volume in the XP storage system and a volume in an external storage
system.
•To copy data between a volume in an external storage system and a volume in another external
storage system.
XP External Storage9
Figure 1 Unifying Copy Operations between Different Storage Systems
Unifying Connections from a Host to Different Storage Systems
When a system has multiple storage systems, a host usually needs to connect all storage systems.
When a system administrator configures the connections from a host to volumes, they need to
follow the different instructions depending on the storage systems.
If you install XP External Storage, a system administrator only needs to configure the connection
from a host to the XP storage system. After the configuration is completed, a host can manipulate
volumes in the external storage system in the same way as volumes in the XP storage system.
10Overview of HP StorageWorks XP External Storage Software
Figure 2 Unifying Connections from a Host to Different Storage Systems
Unifying Connections from a Host to Different Storage Systems11
2 About XP External Storage Operations
This chapter explains the functions and the applications of XP External Storage.
•“Connecting External Storage Systems” (page 12)
•“XP External Storage Components” (page 13)
•“XP External Storage Operations” (page 15)
•“Configuring XP External Storage” (page 16)
•“Choosing Mapping Policy” (page 26)
•“Using a Mapped External Volume from a Connected Host” (page 27)
•“Interoperability with other Products and Functions” (page 29)
•“Examples of Using External Volumes with Other Products” (page 31)
Connecting External Storage Systems
XP External Storage enables you to use HP XP storage systems and other vendors' storage systems
(such as IBM or EMC) as connectable external storage systems. Hosts will recognize these volumes
as internal volumes of the original XP storage system. From this section onward, the original storage
system is called local storage system and a connected storage system is called the external storagesystem.
External volume mapping is required for manipulating external volumes from a local storage system.
Mapping means assigning management numbers to the external volumes. These management
numbers are required for manipulating external volumes from a local storage system. By assigning
management numbers to the external volumes, the system administrator will be able to manipulate
not only internal volumes of a local storage system but also external volumes using Remote Web
Console. The management numbers consist of external volume group number - sequential number
(for example, E2-1, E50-3).
Figure 3 (page 13) shows the concept of a local storage system and an external storage system
that are connected by XP External Storage. In the figure, the external storage system is connected
to the external port of the local storage system via a switch using the Fibre Channel interface. The
external port is a kind of port attribute that is used for XP External Storage. The external volumes
are mapped as internal volumes.
12About XP External Storage Operations
Figure 3 Concept of XP External Storage
By mapping an external volume as an internal volume using XP External Storage as shown in
Figure 3 (page 13), it becomes possible to operate the external volume using Remote Web Console
as if it is a volume in the local storage system.
XP External Storage Components
Systems using XP External Storage usually contain the following components:
•Local storage system
•External storage system
•Remote Web Console computer
•XP External Storage
•External volume
•Internal volume, which is a virtual representation of an external volume
•LDEVs (Logical Devices) in an external volume
•Cross-subsystem path
•Mapping path
Figure 4 (page 14) illustrates the relations of the XP External Storage components.
XP External Storage Components13
Figure 4 XP External Storage Components
This section describes the details on the storage systems, cross-subsystem paths, volumes and
mapping paths as shown in Figure 4 (page 14).
Storage Systems and Cross-subsystem Paths
Before using XP External Storage, connect the Fibre Channel port of the local storage system to
the external storage system port with the fiber cable. The route between the ports that are connected
with the cable, is called the cross-subsystem path.
The Fibre Channel port of the local storage system is set to connect to a host by default. The Fibre
Channel port can be connected to an external storage system if you change the attribute of the
Fibre Channel port to make it an external port. The external storage system port can be a target
port, that is, a port that would be connected to a host if the storage system were not being used
as external storage.
Two or more external storage systems can be connected to one external port. You can add an
external storage system to a port that is being used by another external storage system.
To manipulate XP External Storage, you need to install XP External Storage using the license key.
Use your Remote Web Console computer to access the local storage system via SVP (web server)
and perform the XP External Storage operations.
Volumes and Mapping Paths
Volumes in the external storage system (see C in Figure 4 (page 14)) are called external volumes.
Mapping is necessary to manipulate an external volume from the local storage system. The system
administrator maps an external volume as an internal volume (see B in Figure 4 (page 14)) in the
14About XP External Storage Operations
local storage system. After the mapping, you can manipulate the external volume from the local
storage system in the same way as manipulating an internal volume.
When external volumes in external storage systems are mapped as internal volumes in your storage
systems, the external volumes can be accessed and copied by hosts connecting to your storage
systems, but not by hosts connecting to the external storage systems.
This document sometimes uses the term external volume or mapped external volume to mention an
internal volume where an external volume is mapped (see B in Figure 4 (page 14)), because this
internal volume is a virtual representation of an external volume.
When you perform mapping, a path is automatically created between an internal volume and an
external volume. This path is called a mapping path, which connects one volume with another
volume. A cross-subsystem path is a part of a mapping path.
To use the external volumes that you mapped as an internal volume (see B in Figure 4 (page 14))
- from the host or other program products, the system administrator needs to create LDEVs in the
external volume (see A in Figure 4 (page 14)). To create LDEVs, use XP External Storage at the
time of mapping, or use the Virtual LVI/LUN (VLL) function on the internal volume where an external
volume is mapped after mapping. The LDEVs created by these methods are called LDEVs in theexternal volume in this document. These LDEVs are usually called external volumes in other
documents.
An external volume corresponds to a VLL VDEV (Virtual Device). An LDEV in the external volume
corresponds to a VLL LDEV. Therefore, you can use the VLL function to create custom-sized volumes
in an external volume after mapping, in the same way as creating custom-sized volumes in the
normal internal volumes. For details on VDEVs and LDEVs, see the HP StorageWorksXP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User Guide.
XP External Storage Operations
Use XP External Storage to execute the following operations.
•Preparing to use external volumes
You can map external volumes, set port attributes, and set cross-subsystem paths. For details,
see “Configuring XP External Storage” (page 16) and “Overview of Setting Operations”
(page 65).
•Preparing to manipulate the power supply of the storage systems
You must follow specific procedures to manipulate the power supply of the storage systems
when external volumes are used. To turn on or off the power supply of the external storage
system after starting to use the external volumes, you need to execute the commands of XP
External Storage. For details, see “Turning On or Off the Storage System” (page 88).
•Setting up and removing the cross-subsystem paths
When you set up or remove the path (cable) connecting the storage systems, you need to use
XP External Storage to make settings on the path. For details on removal, see “Disconnecting
External Storage System or Disconnecting External Volume” (page 91) and “Checking
Connection Status and Resuming External Volume Operation” (page 93). For details on setup,
see “Configuring the Cross-subsystem Path” (page 81).
•Referring to the status of external volumes
You can see the status and the configuration of external volumes. For details, see “Checking
the External Volume Details” (page 85).
•Stopping the use of external volumes
You can cancel mapping of external volumes. For details, see “Deleting the External Volume
Mapping (Delete Volume Command)” (page 99).
XP External Storage Operations15
•Using spreadsheets to map external volumes
XP External Storage supports Configuration File Loader spreadsheets. These spreadsheets
allow you to configure the mapping of multiple external volumes at the same time, which is
efficient when mapping large numbers of volumes. For details, see “Using Spreadsheets for
XP External Storage Operations” (page 101).
•Setting the remote command device
By using the remote command device, you can manipulate volumes in the external storage
system from RAID Manager on host computers. For details, see “Remote Command Devices”
(page 119).
Configuring XP External Storage
Before configuring the XP External Storage settings, answer the following:
•Which ports can be connected to external storage systems? (see “Choosing the External Port”
(page 16))
•Which external storage system and volumes should be mapped as the internal volumes? (see
“Choosing and Mapping External Volumes” (page 16))
•How will you configure external volume groups? (see “Registering a Volume to an External
Volume Group (ExG)” (page 17))
•What external volume attributes will be configured? (see “Configuring External Volume
Attributes” (page 17)).
•How will you configure cross-subsystem paths? (see “Cross-subsystem Paths” (page 18))
•How will you make volumes usable from the local storage system? (see “Connecting Mainframe
Volumes” (page 25) and “Connecting Open Systems Volumes” (page 26))
Each item is explained in the following sections.
Choosing the External Port
The port used for XP External Storage must be set as the external port. When the external storage
system is connected to the external port of the local storage system, you can view the information
on the external storage system from the Remote Web Console computer. The external storage
system cannot be connected to ports other than the external port.
In order to set the port attribute to external, any LU paths set to the port must be released. The
attribute of the port where LU paths are already set cannot be changed to external. Therefore, you
must identify ports whose attributes can be changed to external before starting the XP External
Storage operations.
The ports whose attributes are set for remote copy software (for example, RCU target, initiator) or
other features cannot be used as external ports for XP External Storage. In addition, change the
port attribute to external if the port attribute is set to other than external.
For instructions on configuring port attributes, see “Setting Port Attribute for Local Storage System”
(page 67).
Choosing and Mapping External Volumes
When connecting an external storage system to an external port, volumes in the external storage
system (external volumes) become available for mapping as volumes in the local storage system
16About XP External Storage Operations
(internal volumes). Identify the volumes in each external storage system that should be mapped as
internal volumes.
•You cannot access the data that is stored in an external volume beyond the maximum available
capacity.
For example, if an external volume of 100 GB was mapped as an internal volume of 70 GB,
then 30 GB of the external volume would not be accessible from the local storage system side.
•You cannot map an external volume whose capacity is smaller than the minimum available
capacity.
For example, you cannot map an external volume of 10 GB as an internal volume requiring
at least 30 GB.
The maximum or minimum available capacity of an external volume depends on the emulation
type that is set when the volume is mapped. See “Required Volume Capacity for Each Emulation
Type” (page 152) for the capacity of the external volume for each emulation type. For the maximum
number of external volumes that can be mapped, see “XP External Storage Requirements” (page 37).
Registering a Volume to an External Volume Group (ExG)
When you map an external volume as an internal volume, you need to register the external volume
to an external volume group.
External volumes, which are set by XP External Storage, can be classified into groups by usage.
Any group of this type is called an external volume group (ExG). For instance, you can register
multiple volumes in one external storage system to one external volume group. Or you can register
the volumes in one external volume group and manage them in block, even though the data you
want to manage in a lump is stored in volumes in the different external storage systems.
You need to assign numbers to external volume groups. See “XP External Storage Requirements”
(page 37) for details on a maximum number of external volume groups, or a maximum number of
volumes to be registered in one external volume group.
Configuring External Volume Attributes
When you map an external volume as an internal volume, you set the attributes of the external
volume. External volume attributes can be set using the mapping policy or the Set External Volume
Parameter dialog box of XP External Storage. For details on the mapping policy, see “Choosing
Mapping Policy” (page 26). For details on the Set External Volume Parameter dialog box, see
“Set External Volume Parameter Dialog Box” (page 72).
The attributes of the external volume are as follows:
•Emulation type
Select an emulation type for the mapped external volume from the list.
The emulation type OPEN-V must be selected if, after the mapping, you are planning to use
the existing data in the external volume from the local storage system. For example, to migrate
the existing data in the external volume to the local storage system volume, set the OPEN-V
emulation type when the external volume is mapped.
If you select the emulation type other than OPEN-V, the volume requires a specific area to be
provided for management data. Once this area is provided, volume capacity after the mapping
becomes less than the actual external volume capacity for the area (volume). For details on
volume capacity, see “Capacity Guidelines” (page 40).
•Cache Mode (Enable or Disable)
Cache mode specifies whether the write data from the host to the external storage system is
propagated synchronously (Disable) or asynchronously (Enable). By default, cache mode is
Configuring XP External Storage17
set to Disable. All I/O to and from the local storage system (either Enable or Disable) always
uses cache mode. Write operations are always backed up in duplex cache.
◦If you select Enable, after receiving the data into the local storage system cache memory
, the local storage system signals the host that an I/O operation has completed and then
asynchronously destages the data to the external storage system.
◦When emulating OPEN volumes and selecting Disable, the local storage system signals
the host that an I/O operation has completed only after the local storage system has
synchronously written the data to the external storage system. When emulating mainframe
volumes, when you select Disable, after receiving the data into the local storage system
cache memory, the local storage system signals the host that an I/O operation has
completed and then asynchronously destages the data to the external storage system.
If you perform the Cache Residency Manager operation on an external volume with
Cache Mode set to Disable, the bind mode of Cache Residency Manager cannot be
specified. For Cache Residency Manager operations, see the HP StorageWorksXP24000/XP20000 Cache Residency Manager User Guide.
When you set the cache mode, note the following:
◦Data that is not written by the host (for example, data written by HP StorageWorks XP
Continuous Access Software) is asynchronously destaged to the external storage system
regardless of the Cache Mode setting.
◦If you set the emulation type for a mainframe system (such as 3390-x), data that is written
by a host using a command such as Format Write is asynchronously destaged to the
external storage system regardless of the Cache Mode setting. Data that is written by a
host using a command such as Update Write is destaged to the external storage system
as configured in the Cache Mode setting.
•Inflow Control (Enable or Disable)
Inflow control specifies whether the writing operation to the cache memory is stopped (Enable)
or continued (Disable) when the writing operation to the external volume is impossible. By
default, inflow control is set to Disable.
◦If you select Enable, the writing operation to cache is stopped and the I/O from the host
is not accepted when the writing operation to the external volume is impossible.
◦If you select Disable, the I/O from the host during the retry operation is written to the
cache memory even after the writing operation to the external volume is impossible. Once
the writing operation to the external volume becomes normal, all the data in the cache
memory is written to the external volume (all the data is destaged).
•CLPR
When the cache memory is partitioned using HP StorageWorks XP Disk/Cache Partition
Software, configure a cache logical partition (CLPR) to access the mapped volume. It is strongly
recommended that you place External Storage array groups in a CLPR other than CLPR0. See
the HP StorageWorks XP24000/XP20000 Disk/Cache Partition User Guide for detailed
information on CLPR.
Cross-subsystem Paths
A cross-subsystem path is a route from a local storage system port to an external storage system
port. To prepare for possible failures of the cable, the switch, or the channel processor, HP
recommends that you create redundant cross-subsystem paths. This redundancy allows you to
continue performing the I/O operations to the external volumes when you maintain the cable. You
can set up to eight paths.
18About XP External Storage Operations
If two or more external volumes use the same redundant cross-subsystem paths, these external
volumes can be a group. This group is called a path group. In the redundant cross-subsystem paths,
the cross-subsystem path that has the highest priority is called the primary path. The cross-subsystem
paths other than the primary path are called alternate paths.
•Setting of the path groups
A path group is automatically set when you map the external volume or when you change a
path group by using spreadsheets. You cannot set a new path group by itself. For more
information about changing a path group by using spreadsheets, see “Changing Path Group”
(page 115).
•Setting of cross-subsystem paths
Use fiber cables to establish multiple paths between the external storage system and the local
storage system. At this time, connect to the external storage system from a different cluster
port of the local storage system.
If multiple paths are established between the two storage systems, the starting points of the
paths (that is, external ports of the local storage system) and the ending points (that is, WWNs
showing the ports of the external storage system) will be displayed in a dialog box when you
map an external volume. In this dialog box, you can set cross-subsystem paths by selecting
the starting points and the ending points of the paths according to the actual cable connections.
For details on how to set cross-subsystem paths, see “Configure Cross-subsystem Paths Dialog
Box” (page 79).
•Setting of redundant cross-subsystem paths
Path Mode
Path mode is either Single mode or Multi mode, depending on the connected external storage
system.
•In the Single mode, only the path with the highest priority (primary path) is used to execute
•In the Multi mode, all of the set paths are used at the same time. The multiple paths are used
For example, when a volume in the external storage system with the path mode of the Single mode
is mapped as an internal volume using XP External Storage, the host I/O operations to the external
volume are enabled using the primary path set in the mapping operation. The path is automatically
switched to the alternate path when the primary path set in mapping operation cannot be used
due to, for instance, maintenance operation in the storage system, or a failure in the channel
processor. Because the path is switched to the alternate path, the I/O operation to the external
volume continues even though an error occurred in the original path.
When the primary path cannot be used for three minutes continuously, the path is switched to the
alternate path.
You can set redundant cross-subsystem paths (add alternate paths) when you set the
cross-subsystem paths. You can also add an alternate path or change the priority after
completing the mapping of the external volume (see “Setting the Cross-subsystem Paths”
(page 78)).
the I/O to the external volume. When an error occurs in the primary path, the path with the
second highest priority is used.
to execute the I/Os to the external volume thus distributing the work load (round-robin
processing).
Examples of Alternate Paths
Figure 5 (page 20) illustrates an example of setting an alternate path. External storage system
ports, WWN A and WWN B, are connected to CL1-A and CL2-A respectively, which are set to
the external ports in the local storage system. You need to specify the port of a different cluster in
Configuring XP External Storage19
the local storage system for the alternate path. Therefore, CL1 port and CL2 port are specified as
shown in the figure.
Figure 5 Example of Alternate Path Setting
Figure 6 (page 20) illustrates an example of setting an alternate path when a switch is used. Two
ports are specified in the local storage system, and connected to the ports in the external storage
system through the switch. In this case, two ports of different clusters are specified in the local
storage system. Therefore, the setting of the alternate path is enabled.
Figure 6 Example of Available Alternate Path Setting
In Figure 7 (page 21), two paths are also set between the internal volume and the external volume.
However, one port is specified in the local storage system, and two ports are specified in the
external storage systems over the switch. This configuration is not recommended because two ports
of different clusters need to be set in the local storage system for alternate path settings in XP
External Storage.
20About XP External Storage Operations
Figure 7 Example of Unavailable Alternate Path Setting
Examples of Switching I/O Execution Paths to Alternate Paths
This section describes examples of the performance when the I/O execution path is switched to
the alternate path for each path mode as follows:
•When the path mode is Multi mode
•When the path mode is Single mode
•When the path mode is Single mode and there is at least one alternate path in the Standby
status
For the description about the path status, see “Mapping Path Information Dialog Box” (page 86).
•When the path mode is Multi mode
Figure 8 (page 22) shows an example of when the path mode is Multi mode. When an error
occurs in one path, I/Os are executed using the paths other than the error path.
As you restore the error path, the use of the restored path is automatically resumed.
Configuring XP External Storage21
Figure 8 When the Path Mode is Multi Mode
•When the path mode is Single mode
Figure 9 (page 23) shows an example of when the path mode is Single mode. When an error
occurs in the path that is being used for I/Os, the I/O execution path is switched to the path
with the second highest priority.
As you restore the path with the priority higher than the currently used path, the I/O execution
path is automatically switched to the restored path that has the highest priority.
22About XP External Storage Operations
Figure 9 When the Path Mode is Single Mode
•When the path mode is Single mode and there is at least one alternate path in the Standby
status
Figure 10 (page 24) shows an example of when the path mode is Single mode, and there
are alternate paths in Normal status and Standby status. Figure 11 (page 25) shows another
example of when the path mode is Single mode. For Figure 11 (page 25), there are alternate
paths in Standby status only.
When an error occurs in the path that is being used for I/Os, the I/O execution path is
switched to the path with the second highest priority in Normal status (see Figure 10 (page
24)). If there is no path in Normal status other than the path that is being used for I/Os, the
status of the path in Standby status is automatically changed to Normal, and the I/O execution
path is switched to that path (see Figure 11 (page 25)).
As you restore the path with the highest priority, note that only when the external storage
system is an EVA storage system, the I/O execution path is switched back to the restored
highest priority path. In this case, the status of the path for which the status was changed to
Normal when the error occurred changes back to Standby.
Configuring XP External Storage23
Figure 10 Single Mode with Alternate Paths in Normal and Standby
24About XP External Storage Operations
Figure 11 Single Mode with Alternate Paths in Standby Only
Connecting Mainframe Volumes
Mainframe volumes that pre-exist on an external storage system and are accessed by ESCON or
FICON channels cannot connect directly to the storage system as an external volume. The storage
system does not recognize these volumes because of Fibre Channel.
To use external volumes as mainframe volumes, there are two ways:
•Zero-format external volumes on the external storage system side, map the external volumes
to the internal volumes using XP External Storage on the local storage system side, and then
perform the Write to Control Blocks operation using the VLL function on the local storage system
side.
•Map the external volumes to the internal volumes using XP External Storage on the local storage
system side, and then format the mapped external volumes using the VLL function on the local
storage system side.
If you set the emulation type for the mainframe system (such as 3390) as you map the external
volume, the status of the mapped volume becomes Blockade after the mapping operation. After
the system administrator performs the Write to Control Blocks operation or formats the mapped
external volumes using the VLL function on the local storage system side, the mainframe host can
then access the new mainframe volume through the local storage system's ESCON or FICON
channels.
If you format the mapped volume of the external storage system from the external storage system
side, the existing data before formatting cannot be assured. When you use the mapped external
volume from the mainframe operating system, format the mapped volume from the local storage
system side.
Configuring XP External Storage25
For the volume formatting and Write to Control Blocks operation procedures, see the HPStorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User Guide.
Connecting Open Systems Volumes
Open systems volumes in external storage system connect to and are recognized by the storage
system as open systems volumes, without requiring reformatting. Reformatting is not required
because the connection between the storage system and the external storage system is Fibre
Channel. If you need to initialize the data area for the volume, format the volume using the VLL
function. For the volume formatting operation procedure, see the HP StorageWorksXP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User Guide.
OPEN-V emulation is recommended because, in most cases, OPEN-V emulation provides the most
efficient use of storage and the best performance. Also, emulation types other than OPEN-V may
not retain existing data after being mapped.
Choosing Mapping Policy
Mapping policy is a list of settings of the necessary information for mapping the external volume.
By setting the mapping policy in advance, the setting at the time of mapping will be easier.
The default mapping policy is prepared in advance. You can change the values of the default
mapping policy.
Difference between Automatic Mapping and Manual Mapping
When you map the external volume, you need to configure:
•Cross-subsystem paths
•External volume parameters
•LDEV number to LDEVs in the external volume
•SSID (storage system ID)
When you perform automatic mapping, users configure only cross-subsystem paths and all the
other settings are automatically made by XP External Storage according to the mapping policy.
When you perform manual mapping, users configure all the settings.
Automatic mapping maps all the external volumes found by volume discovery to internal volumes.
Automatic mapping requires fewer settings but you are not allowed to set different parameters for
each external volume or to specify an LDEV number for each LDEV. You can set the parameters
such as emulation type to the mapping policy in advance.
NOTE:In automatic mapping, external volumes are mapped in the order of the local storage
system recognizing. Therefore, the LDEV number is also specified in this order. Moreover, when
you copy external volumes with the program product for copying, the copy operation is performed
in the order of the LDEV number if you specify two or more external volumes for the initial copy or
resynchronization. Therefore, when you copy external volumes that are mapped automatically with
the program product for copying, the copy operation might focus on a specific RAID group and
cause insufficient performance. To prevent the copy operation from focusing on a specific RAID
group, HP recommends that the external volumes be mapped manually so that the copy operation
is distributed to two or more RAID groups.
Port Discovery and Volume Discovery
Port discovery and volume discovery are methods used to find external volumes, and are executed
when you map external volumes or when you add cross-subsystem paths.
•Port discovery searches for and gets information about target ports of the connected external
storage system from an external port of the local storage system. The latest information about
26About XP External Storage Operations
the external storage system can be displayed in a dialog box of XP External Storage when
you execute port discovery.
You can set in advance the mapping policy on whether to execute port discovery automatically
or manually. If port discovery is executed automatically, WWNs connected to all the external
ports of the local storage system will be searched for. If port discovery is executed manually,
you can select a specific external port and limit the scope to search WWNs. If you can specify
which external port to search for, you can reduce the operation time by executing the port
discovery manually.
•Volume discovery searches for and gets information about external volumes from the target
ports of the external storage system. Volume discovery is automatically executed after the port
discovery process.
When a port in an external storage system is connected to an XP storage system and has a
management LU (for example, Universal Xport LU), an extra operation is required. A management
LU is an LU that receives commands issued by a particular application. The management LU controls
or manages that application. The management LU stores control information from that application
and, therefore, the management LU cannot be used as an external volume. A command device is
not a management LU.
Before performing port discovery or volume discovery, perform one of the following operations on
the external storage system.
•Delete the management LU from the port connected to the XP storage system.
•Make sure that at least one LU is used for data storage and has a smaller LUN ID than the
LUN of the management LU. Also make sure that the data storage LU is set to the port connected
to the XP storage system.
•Use the security function and configure the access attribute of the management LU to prohibit
read and write operations.
If none of the operations is performed, an external storage system that has a management LU might
not be recognized by the local storage system.
Using a Mapped External Volume from a Connected Host
There are two ways of using the mapped external volume from a host that is connected the local
storage system.
•“Storing New Data in the Mapped External Volume” (page 27)
•“Using Existing Data in the Mapped External Volume” (page 28)
Storing New Data in the Mapped External Volume
To store new data in a mapped external volume from a host that is connected to the local storage
system:
1.Map the volume in the external storage system as an internal volume of the local storage
system using XP External Storage.
Select the emulation type of the mapped volume as you required. If you select the emulation
type for the open system (such as OPEN-V), go to step 2. If you select the emulation type for
the mainframe system (such as 3390-3), go to step 3.
For information on mapping operations, see “Mapping an External Volume Automatically”
(page 67).
2.If you set the emulation type for the open system when you map the volume, the status of the
mapped volume automatically becomes Normal. If you need to initialize the data area of the
mapped volume, format the volume using the VLL function. For the volume formatting procedure,
Using a Mapped External Volume from a Connected Host27
see the HP StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder
User Guide.
Go to step 4.
3.If you set the emulation type for the mainframe system when you map the volume, the status
of the mapped volume becomes Blockade. Format the volume using the VLL function.
For zero-formatted external volumes, when you select that volume to map, you can use the
VLL function to perform the Write to Control Blocks operation to restore the volume. For
instructions on how to format volumes and the Write to Control Blocks operation, see the HP
StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User Guide.
Go to step 4.
4.To perform the host I/O operations, set the LU path from the Target port to the mapped volume.
After the LU path is set, the host I/O operation to the mapped volume becomes available.
Figure 12 Storing the New Data in the Mapped External Volume
Using Existing Data in the Mapped External Volume
To use the existing data in the mapped external volume from the host that is connected to the local
storage system:
1.Store the data from the host that is connected to the external storage system to the volume in
the external storage system.
2.Map the volume containing data in the external storage system as an internal volume of the
local storage system using XP External Storage.
When you map the external volume, set the attributes of the mapped volume to Emulation
type = OPEN-V to read the existing data in the mapped external volume from the local storage
system side.
3.Set the LU path from the Target port to the mapped volume to perform the host I/O operation.
After the LU path is set, the host I/O operation to the mapped volume can be initiated.
Make sure that you do not access the external volume, which has been mapped as an internal
volume, from the host that is connected to the external storage system. Also make sure that you do
not access the mapped external volume using the function (for example, copy function) of the
external storage system. Once you have mapped an external volume as an internal volume, you
can access the mapped external volume only from the local storage system side.
28About XP External Storage Operations
From the host, you can access the external storage system volumes that have not been mapped as
internal volumes. There is no restriction. Figure 13 (page 29) illustrates using existing data in a
mapped external volume.
Figure 13 Using the Existing Data in the Mapped External Volume
Interoperability with other Products and Functions
You can use XP disk array program products to use and manage the external volumes you have
set using XP External Storage. For the operations and notes on each program product, see the
respective user's guides.
LUN Manager and Configuration File Loader
If you set the emulation type for the open system as you map an external volume, you need to set
the LU path for the mapped volume using LUN Manager.
Consider the following for the Configuration File Loader function:
•You can set the LU path definition for the external volume (add, delete, or change LU paths).
•You can set the command device for the external volume (add or delete the setting).
•The setting of the channel adapter (CHA) mode, host group, and WWN for the external port
is not supported. When an external volume is mapped through that external port, the setting
operation of the topology is not available, either.
LUN Expansion (LUSE)
Consider the following for LUN Expansion (LUSE):
•The internal volume in the local storage system and the external volume cannot be combined
to form a LUSE volume.
•Do not combine LDEVs of multiple external volumes to create a LUSE volume. Only the LDEVs
in the same external volume can be used to configure the LUSE volumes.
•All external volumes in a LUSE volume must be in the same Cache Mode.
Interoperability with other Products and Functions29
Virtual LVI/LUN (VLL)
Consider the following for Virtual LVI/LUN (VLL):
•If you set the emulation type for the mainframe system as you map the external volume, you
need to format the mapped volume or perform the Write to Control Blocks operation using the
VLL function before you use the external volume.
For the volume formatting operation and Write to Control Blocks operation procedures, see
the HP StorageWorks XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User
Guide.
•If you create LDEVs in an external volume using the VLL function, the cache mode of the created
LDEVs becomes the same as that of the source external volume.
Cache Residency Manager
Consider the following for Cache Residency Manager:
•The bind mode of the Cache Residency Manager operation cannot be specified for the external
volume if the Cache Mode is set to Disable.
•If you use the mapped external volume for the Cache Residency Manager operation and set
the bind mode, a cache of twice as much capacity as the user data is required for the Cache
Residency Manager operation.
Performance Monitor and XP Auto LUN
Consider the following for Performance Monitor and XP Auto LUN:
•Performance Monitor can be used to display the monitoring information about the external
volumes.
•Mapped volumes can be used for XP Auto LUN. For instructions on adjusting volume capacity,
see “Adjusting the Volume Capacities for Pairs” (page 156).
For the configuration example of XP Auto LUN, see “XP Auto LUN Operations” (page 31).
XP Continuous Access and Hitachi TrueCopy™ for Mainframe
Mapped volumes can be used for XP Continuous Access and for TrueCopy for Mainframe. For a
configuration example of XP Continuous Access, see “XP Continuous Access Operations” (page 32).
HP StorageWorks XP Continuous Access Journal Software and Hitachi Universal
Replicator™ for Mainframe
Mapped volumes can be used for XP Continuous Access Journal and Universal Replicator for
Mainframe. For a configuration example of XP Continuous Access Journal, see “XP Continuous
Access Journal Operations” (page 33).
HP StorageWorks XP Business Copy Software and Hitachi ShadowImage™ for
Mainframe
Mapped volumes can be used for XP Business Copy and ShadowImage for Mainframe. For a
configuration example of XP Business Copy, see “XP Business Copy Operations” (page 35).
30About XP External Storage Operations
Loading...
+ 140 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.