XP External Storage Software User Guide

HP
XP External Storage Software User Guide
HP XP12000 Disk Array
HP XP10000 Disk Array
HP 200 Storage Virtualization System
nl
nl
Abstract
This document provides information about preparing for, performing, and troubleshooting HP XP External Storage operations;
connecting external arrays; and using an XP12000/XP10000/SVS200 with EVA3000/50000.
HP Part Number: T1706-96018
Published: May 2011
Edition: Eighteenth
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P.
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
edition
date
Description
eighth
june 2007
This edition applies to microcode version 50-09-30-00-00 or later.
ninth
september 2007
This edition applies to microcode version 50-09-31-00-00 or later.
tenth
november 2007
This edition applies to microcode version 50-09-50-00-00 or later.
eleventh
january 2008
This edition applies to microcode version 50-09-70-00-0-00 or later.
twelfth
april 2008
This edition applies to microcode version 50-09-71-00/00 or later.
thirteenth
june 2008
This edition applies to microcode version 50-09-71-00/00 or later.
fourteenth
december 2008
This edition applies to microcode version 50-09-78-00/00 or later.
fifteenth
february 2009
This edition applies to microcode version 50-09-83-00/00 or later.
sixteenth
december 2009
This edition applies to microcode version 50-09-90-00/00 or later.
seventeenth june 2010
This edition applies to microcode version 50-09-94-00/00 or later.
eighteenth
This edition applies to microcode version 50-09-01-00/00 or later.
may 2011
Contents
1 Overview of connecting external arrays.........................................................7
XP External Storage features.......................................................................................................7
2 Preparing for XP External Storage operations.................................................9
Supported storage platforms and firmware...................................................................................9
Prerequisites.............................................................................................................................9
System requirements..................................................................................................................9
Storage arrays that can be connected as external arrays.........................................................10
XP External Storage requirements..............................................................................................15
Installing XP External Storage...................................................................................................16
Preparing for XP External Storage settings..................................................................................16
External ports....................................................................................................................17
External LU to be mapped...................................................................................................17
External LU groups.............................................................................................................17
External LU attributes set by mapping...................................................................................17
Alternate paths..................................................................................................................19
Example of an alternate path configuration.......................................................................20
Examples of switching I/O execution paths to alternate paths.............................................21
Powering arrays on or off.........................................................................................................25
Commands for Turning On or Off Only an External Array.......................................................25
Powering local arrays on or off............................................................................................26
To power local arrays off................................................................................................26
To power local arrays on................................................................................................26
Powering external arrays on or off........................................................................................26
To power external arrays off...........................................................................................26
To power external arrays on...........................................................................................26
Turning On or Off Power Supply of Both local and external arrays............................................27
Using mapped external LUs from the host connected to the local array...........................................27
Writing new data to mapped external LUs.............................................................................28
Using existing data in mapped external LUs..........................................................................29
Uninstalling XP External Storage...............................................................................................29
Limitations on XP External Storage operations.............................................................................30
Combining XP External Storage with other HP products...............................................................37
Using external LUs for XP Auto LUN operations......................................................................40
Using external LUs for XP Continuous Access operations..........................................................41
Using external LUs for XP Continuous Access Journal operations...............................................42
Using external LUs for XP Business Copy operations................................................................43
Using external LUs for XP Snapshot Software operations..........................................................44
3 Managing cache with external storage........................................................46
Guidelines for using cache with external storage........................................................................46
Determining, setting, or changing the external LU cache mode.....................................................47
Determining if the cache mode is disabled............................................................................47
Changing the cache mode..................................................................................................47
Collecting device information..........................................................................................48
Deleting and remapping the external LU...........................................................................51
Partitioning cache for external storage.......................................................................................51
Determining the number and size of needed partitions................................................................52
Creating cache partitions........................................................................................................52
Changing storage system modes...............................................................................................55
4 XP External Storage panes.........................................................................56
LU Operation pane.................................................................................................................56
Contents
3
Device tree........................................................................................................................58
Device list.........................................................................................................................59
WWN tree.......................................................................................................................62
WWN list.........................................................................................................................63
Port tree............................................................................................................................66
Port list.............................................................................................................................67
Filter button.......................................................................................................................70
Preset list (LU Operation pane).............................................................................................70
Port Operation pane...............................................................................................................71
Port Operation tree............................................................................................................72
Port Operation list..............................................................................................................73
Preset list (Port Operation pane)...........................................................................................74
5 Configuring external LUs............................................................................75
Overview of configuring external LUs.........................................................................................75
Setting an external array's port.................................................................................................77
Setting a local array's port attributes.........................................................................................77
Discovering and Mapping LUs..................................................................................................78
Mapping external LUs individually (Add LU)...........................................................................78
Select Paths pane..........................................................................................................82
Mapping multiple external LUs at (Add LU (Auto))...................................................................86
Select LDEV window......................................................................................................89
Displaying detailed information stored in VMA (VMA information)...........................................92
Setting alternate paths for external LUs......................................................................................93
Defining alternate paths......................................................................................................96
Changing a defined alternate path priority............................................................................97
Canceling alternate path definitions.....................................................................................98
Changing alternate paths...................................................................................................99
Replacing all the alternate paths with newly-added alternate paths...........................................99
Adding alternate paths by selecting multiple external LUs (Add Paths)..........................................100
Deleting alternate paths by selecting multiple external LUs (Delete Paths)......................................102
Checking an external LU's status (LDEV Information)..................................................................104
Obtaining information about external LUs...........................................................................104
Restoring external LUs (Restore)..........................................................................................106
Displaying configuration information for external LUs (Volume Detail)......................................107
Disconnecting external arrays or LUs.......................................................................................108
Disconnecting all external LUs in an external array (Disconnect Subsystem)..............................109
Disconnecting external LUs individually (Disconnect Volume)..................................................110
Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.)....111
Restoring all external LUs in an external array (Check Paths & Restore Vol.)..............................111
Restoring external LUs individually (Check Paths & Restore Vol.)..............................................112
Restoring external LUs (LDEV Restore).......................................................................................112
Restoring volumes in an external array................................................................................112
Restoring volumes in a mapped external LU individually........................................................113
Changing the cache mode setting of the external LU.................................................................113
Changing the cache mode of all external LUs in an external array..............................................114
Changing the cache mode of an individual external LU.............................................................114
Stopping the use of paths to an external LU by specifying an external array's WWN (Disconnect
Paths)..................................................................................................................................115
Restoring paths to an external LU by specifying an external array's WWN (Check Paths)...............115
Changing an external array's port setting................................................................................116
Stopping the use of paths to an external LU by specifying a local array's port (Disconnect Paths).....117
Restoring paths to an external LU by specifying a local array's port (Check Paths).........................117
Deleting external LU mappings (Delete LU)...............................................................................117
4
Contents
6 Troubleshooting NAS Blade systems that include external arrays...................119
Stopping and restarting external arrays...................................................................................119
Stopping external arrays...................................................................................................120
Restarting external arrays and restoring NAS Blade systems...................................................120
Recovery procedures for errors in external arrays......................................................................121
Errors in an external array's disk........................................................................................121
Errors in a path to the external array..................................................................................123
Errors in all paths to the external array................................................................................124
If each node uses a different external array.....................................................................124
If both nodes use the same external array.......................................................................125
7 Remote command devices.......................................................................127
Overview of remote command devices....................................................................................127
Notices about remote command devices..................................................................................128
Mapping command devices as remote command devices..........................................................130
Using XP Continuous Access or XP Continuous Access Journal with remote command devices.........130
Using Initiator/External MIX mode.....................................................................................132
Restrictions on Initiator/External MIX mode..........................................................................133
8 Troubleshooting XP External Storage.........................................................134
Calling HP technical support..................................................................................................139
9 Support and other resources....................................................................140
Related documentation..........................................................................................................140
HP technical support.............................................................................................................140
Subscription service..............................................................................................................140
HP websites.........................................................................................................................141
Documentation feedback.......................................................................................................141
A Notes on connecting external arrays.........................................................142
Connecting Thunder 9500V subsystems...................................................................................142
System parameters for connecting Thunder 9500V subsystems...............................................142
Relationship between serial number and array model of Hitachi Thunder 9500V subsystem.......143
Relationship between the WWN of the port on the Thunder 9500V subsystem and the
controller........................................................................................................................143
Path status and examples of recovery procedures (Thunder 9500V subsystems)........................144
Connecting TagmaStore AMS and TagmaStore WMS subsystems...............................................145
System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems............145
Relationship between serial numbers in device list on the LU operation panel and TagmaStore
AMS and TagmaStore WMS subsystem models...................................................................146
Relation between the WWN of the port on the TagmaStore AMS or TagmaStore WMS subsystem
and controller..................................................................................................................146
Path status and examples of recovery procedure (TagmaStore AMS and TagmaStore WMS
subsystems).....................................................................................................................147
Notes When Power Saving Feature is Used (For TagmaStore AMS Subsystem, TagmaStore WMS
Subsystem)......................................................................................................................149
Connecting VSP Subsystem....................................................................................................149
Path Status and Examples of Recovery Procedure (For VSP Subsystem).....................................149
Connecting XP24000/XP20000 Disk Arrays............................................................................150
Path status and examples of recovery procedure (for XP24000/XP20000 Disk Arrays)..............150
Connecting XP12000/XP10000 Disk Arrays............................................................................151
Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)..................151
Connecting XP1024/XP128 Disk Arrays...................................................................................152
Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays)........................152
Connecting XP512/XP48 Disk Arrays......................................................................................153
Path status and examples of recovery procedures (XP512/XP48 Disk Arrays)............................154
Connecting HP 200 Storage Virtualization System as external storage.........................................154
Contents
5
Path status and examples of recovery procedures (SVS200)...................................................155
Connecting EVA arrays..........................................................................................................156
System parameter settings for connecting EVA arrays............................................................156
Identifying logical volumes of EVA arrays (using Characteristic 2)...........................................156
Alternate path's behavior when an EVA array is connected...................................................157
System parameter settings for connecting Sun StorEdge 6120/6320.......................................157
System parameter settings for connecting Sun StorageTek FlexLine 380...................................157
System parameter settings for connecting Sun StorageTek 2540.............................................157
Alternate paths for connecting Sun StorageTek V2X2............................................................158
Connecting EMC CLARiiON CX Series...............................................................................158
System parameter settings for connecting EMC CLARiiON CX Series.................................158
Notes on Connecting EMC CLARiiON CX Series.................................................................158
System Parameter for Connecting EMC Symmetrix Series.......................................................158
System parameter settings for connecting IBM DS4000 Series................................................158
Alternate Path Mode for Connecting IBM DS8000 Series......................................................159
IBM V7000 Series............................................................................................................159
System parameters for connecting IBM V7000 series.......................................................159
Notes on Connecting IBM V7000 CX Series...................................................................159
Non-HP arrays.................................................................................................................159
B Required volume capacity for emulation types............................................160
How to determine the required external volume capacity...........................................................160
Capacity list for each emulation type.......................................................................................161
C Adjusting volume capacity for copy pair setting.........................................164
Copying data from external arrays (using external LUs as P-VOLs)................................................164
Copying data to external arrays (setting external LUs as S-VOLs).................................................164
Index.......................................................................................................166
6
Contents
1 Overview of connecting external arrays
HP XP External Storage realizes the virtualization of storage arrays. You can use XP External Storage
to access multiple storage arrays connected by a Fibre Channel interface as if they were all one
storage array. Once you connect another storage array to an XP array or storage virtualization
system using XP External Storage, you can also use XP Command View Advanced Edition Software
or Remote Web Console to manage the data space (but not necessarily the management) of the
other storage arrays.
XP External Storage supports external storage LDEVs of any standard XP emulation type, such as
OPEN-3, OPEN-8, OPEN-9, OPEN-L, OPEN-K, OPEN-V, 3390-3, or 3390-0.
NOTE: Currently only the HP XP12000 and XP10000 Disk Arrays and the HP 200 Storage
Virtualization System (SVS200) support external storage.
In this user guide, the original XP12000/XP10000/SVS200 is called the local array and the
connected storage array is called the external array. The volume managed in the local array is
called an internal storage virtualizer LDEV (or internal LDEV), and the volume in an external array
is called an external LU.
IMPORTANT: This guide contains information about internal disks or LDEVs. Unlike the
XP12000/XP10000 Disk Arrays, the SVS200 has no internal disks. Therefore, information about
internal disks or LDEVs does not apply to the SVS200.
With the help of host mirroring middleware, HP XP Auto LUN Software or HP XP Tiered Storage
Manager, you can use XP External Storage Software for online or offline data migration, providing
a point-in-time copy of data between an external device and the local array.
HP XP Flex Copy is another HP product that copies user data between an LU on a local array and
an LU on an external storage device. For a detailed description of XP Flex Copy, see the HP Flex
Copy XP user guide.
XP External Storage features
The following are XP External Storage features:
•
Using XP External Storage to map an external LU as an internal LDEV, you can manage the
external LU capacity using XP Command View Advanced Edition Software or Remote Web
Console as if it were a volume in the local array.
Mapping means assigning Virtual Devices (VDEVs) and, consequently, Logical Devices (LDEVs)
and host port LUs to external LUs. If you map external LUs as internal VDEVs, you can use XP
Command View Advanced Edition Software or Remote Web Console to then assign the VDEV
to an internal CU:LDEV and a port/LU address. This allows you to use an external LU as if it
were an LDEV in the local array.
NOTE: The phrases mapped as an internal LU and mapped as an internal LDEV should be
interpreted to mean that the external LU is specifically mapped into the local array as a unique
VDEV (Virtual Device), which is then associated with a local array CU:LDEV (Control Unit:Logical
Device), which is then typically associated with a unique host port/LU combination. Since a
local array LU number is only unique within the name space of a host port (for example,
CL1-A), references to “XP LU” should be interpreted as references to either the unique port/LUN
combination or the unique CU:LDEV combination.
•
If you use XP Flex Copy with XP External Storage, you can copy data in the external array to
the local array and copy data in the local array to the external array. For more information
about XP Flex Copy, see the HP Flex Copy XP user guide.
XP External Storage features
7
Figure 1 (page 8) illustrates a local array and an external array that are connected using XP
External Storage and Fibre Channel hardware. In Figure 1 (page 8), the external array is connected
to the external port of the local array via a switch (or hub) using a Fibre Channel interface. External
is a local array port attribute used for XP External Storage. In Figure 1 (page 8), external LUs are
mapped as local array VDEVs and LDEVs and, consequently, as an LU.
NOTE: Do not access any external storage volume that is mapped as an XP External Storage
volume from a host connected directly to the external array. Also, do not access an XP External
Storage mapped external array volume using the external array's functions (for example, local
replication). After mapping an external LU as a local array volume, access the mapped external
LU only from the local array.
NOTE: Except on the MSA, a host can directly access external array volumes that have not been
mapped as local array volumes.
Figure 1 XP External Storage concept
8
Overview of connecting external arrays
2 Preparing for XP External Storage operations
This chapter describes requirements, preparations, and notes for XP External Storage. This chapter
also describes the HP products you can use with XP External Storage.
•
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
•
Combining External Storage XP with other HP StorageWorks products
Supported storage platforms and firmware
Unless otherwise specified, the term array in this document refers to the following supported storage
platforms:
•
HP XP12000 Disk Array
•
HP XP10000 Disk Array
•
HP 200 Storage Virtualization System
For supported firmware versions, see HP XP Remote Web Console user guide for
XP12000/XP10000 Disk Arrays and SVS200.
Prerequisites
Prerequisites for using this product include:
•
Installing the HP disk array(s)
•
Installing the license key for this product
System requirements
XP External Storage operations involve the local array, a storage array used as an external array,
and the licensed XP External Storage feature enabled on XP Command View Advanced Edition
Software or Remote Web Console. System requirements for XP External Storage are:
•
Local array (first array)
Install and enable all hardware and microcode required for XP External Storage operations
in the local array.
CAUTION: Before installing and enabling the hardware and microcode, see “Managing
cache with external storage” (page 46) for instructions.
NOTE:
•
Currently only an XP12000/XP10000/SVS200 can be used as a local array.
External array (second array)
You also need a second storage device, called an external array in this user guide. For more
information, see “Storage arrays that can be connected as external arrays” (page 10).
Supported storage platforms and firmware
9
•
XP Command View Advanced Edition Software (running on a user-supplied Windows®-based
PC) or Remote Web Console
For instructions on installing and using XP Command View Advanced Edition Software or
Remote Web Console, see the HP XP Command View Advanced Edition Software user guide
for XP Disk Arrays or the HP XP Remote Web Console user guide for XP12000/XP10000
Disk Arrays and SVS 200.
NOTE: You must run XP Command View Advanced Edition Software or Remote Web Console
in Modify mode to perform XP External Storage operations. In View mode, you can only view
XP External Storage information.
•
XP External Storage
Enable the licensed XP External Storage feature in XP Command View Advanced Edition
Software or Remote Web Console.
Storage arrays that can be connected as external arrays
Table 1 (page 10) lists storage arrays that can be connected as external arrays. Notes about the
appearance of each storage array in this document and in XP External Storage panes are also
listed.
Table 1 Storage arrays that can be connected as external arrays
Storage array
Notes
Virtual Storage Platform subsystem
In this user's guide, the subsystem appears as “VSP
subsystem”.
In the Universal Volume Manager panels, Virtual Storage
Platform subsystem appears as “VSP”.
Alternate paths are in Multi mode.
Universal Storage Platform V subsystem
In this user's guide, the subsystem appears as “USP V
subsystem”.
In the Universal Volume Manager panels, Universal Storage
Platform V subsystem appears as “USP V”.
Alternate paths are in Multi mode
Universal Storage Platform VM subsystem
In this user's guide, the subsystem appears as “USP VM
subsystem”.
In the Universal Volume Manager panels, Universal Storage
Platform VM subsystem appears as “USP VM”.
Alternate paths are in Multi mode,.
10
Preparing for XP External Storage operations
Table 1 Storage arrays that can be connected as external arrays (continued)
Storage array
Notes
HP XP12000 Disk Array
• In XP External Storage panes, the array is a “12000”.
• Alternate paths are in Multi mode (meaning that
dynamic load balancing across multiple active paths is
enabled).
HP XP10000 Disk Array
• In XP External Storage panes, the array is a “10000”.
• Alternate paths are in Multi mode.
HP XP1024/XP128 Disk Array
• In XP External Storage panes, the arrays appear as
“1024” and “128”, respectively.
• Alternate paths are in Multi mode.
HP XP512/XP48 Disk Array
• In XP External Storage panes, the arrays appear as
“512” and “48”, respectively.
• Alternate paths are in Multi mode.
HP XP256 Disk Array
• In XP External Storage panes, the array is a “256”.
• Alternate paths are in Multi mode.
XP External Storage Software
P9500 subsystem
In the XP External Storage Software panes, the array is
“P9500”.
Alternate paths are in Multi mode.
XP24000 subsystem
In the XP External Storage Software panes, the the array
is “24000”.
Alternate paths are in Multi mode.
XP20000 subsystem
In the XP External Storage Software panes, the the array
is “20000”.
Alternate paths are in Multi mode.
System requirements
11
Table 1 Storage arrays that can be connected as external arrays (continued)
Storage array
Notes
HP 200 Storage Virtualization System
• In XP External Storage panes, the array is an “SVS200”.
• Alternate paths are in Multi mode.
HP 3000/5000 Enterprise Virtual Array (Active/Standby
and Active/Active controllers) or HP 4000/6000/8000
Enterprise Virtual Array (Active/Active controllers)
• In this user guide, the arrays appear as “EVA array”.
• In XP External Storage panes, the arrays appear as
“EVA”.
• Alternate paths are in Single mode (meaning that
dynamic load balancing across multiple active paths is
not enabled).
HP MSA1000/1500 (Active/Standby)
• In this user guide, the arrays appear as “MSA array”.
• In XP External Storage panes, the arrays appear as
“MSA”.
• Alternate paths are in Single mode.
TagmaStore™ Universal Storage Platform subsystem
• In this user guide, the array is a “TagmaStore™ USP
subsystem”.
• In XP External Storage panes, the array is a “USP”.
• Alternate paths are in Multi mode.
TagmaStore™ Network Storage Controller subsystem
• In this user guide, the array is a “TagmaStore™ NSC
subsystem”.
• In XP External Storage panes, the array is an “NSC”.
• Alternate paths are in Multi mode.
TagmaStore™ Adaptable Modular Storage subsystem
• In this user guide, the array is a “TagmaStore™ AMS
subsystem”.
• In XP External Storage panes, the array is an “AMS”.
• Alternate paths are in Single mode.
TagmaStore™ Workgroup Modular Storage subsystem
• In this user guide, the array is a “TagmaStore™ WMS
subsystem”.
• In XP External Storage panes, the array is an “NSC”.
• Alternate paths are in Single mode.
Lightning 9900V series subsystem
• “Lightning 99xxV series subsystem” indicates the
Lightning 9970V and Lightning 9980V.
• In this user guide, the arrays appear as “Lightning
9900V subsystem”.
• In XP External Storage panes, the arrays appear as
“9970V” and “9980V”, respectively.
• Alternate paths are in Multi mode.
Thunder 9500V series subsystem
• “Thunder 95xxV series subsystem” indicates the Thunder
9530V, Thunder 9570V, and Thunder 9580V.
• In this user guide, the arrays appear as “Thunder 9500V
subsystem”.
• In XP External Storage panes, the arrays appear as
“9500V”.
• Alternate paths are in Single mode.
Lightning 9900C series subsystem
12
Preparing for XP External Storage operations
• “Lightning 99xxC series subsystem” indicates the
Lightning 9910 and Lightning 9960.
Table 1 Storage arrays that can be connected as external arrays (continued)
Storage array
Notes
• In this user guide, the arrays appear as “Lightning 9900
subsystem”.
• In XP External Storage panes, the Lightning 9910 is a
“0401”, and the Lightning 9960 is a “0400”.
• Alternate paths are in Multi mode.
Virtual Storage Platform VP9500 subsystem
XP External Storage Software panes, the array is “P9500”.
Alternate paths are in Multi mode.
H24000 subsystem
In the XP External Storage Software panes, the array is
“24000”.
Alternate paths are in Multi mode.
H20000 subsystem
In the XP External Storage Software panes, the array is
“20000”.
Alternate paths are in Multi mode.
System requirements
13
Table 1 Storage arrays that can be connected as external arrays (continued)
Storage array
Notes
A/H-6593 subsystem
• In XP External Storage panes, the array is a “300”.
• Alternate paths are in Multi mode.
SANRISE Universal Storage Platform subsystem
• In this user guide, the array is a “SANRISE USP
subsystem”.
• In XP External Storage panes, the array is a “USP”.
• Alternate paths are in Multi mode.
SANRISE Network Storage Controller subsystem
• In this user guide, the array is a “SANRISE NSC
subsystem”.
• In XP External Storage panes, the array is a “NSC”.
• Alternate paths are in Multi mode.
SANRISE Adaptable Modular Storage subsystem
• In this user guide, the array is a “SANRISE AMS
subsystem”.
• In XP External Storage panes, the array is an “AMS”.
• Alternate paths are in Single mode.
SANRISE Workgroup Modular Storage
• In this user guide, the array is a “SANRISE WMS
subsystem”.
• In XP External Storage panes, the array is a “WMS”.
• Alternate paths are in Single mode.
SANRISE9900V series subsystem
• “SANRISE99xxV series subsystem” indicates the
SANRISE9970V and SANRISE9980V.
• In this user guide, the arrays appear as
“SANRISE9900V subsystem”.
• In XP External Storage panes, the arrays appear as
“9970V” and “9980V”, respectively.
• Alternate paths are in Multi mode.
SANRISE9500V series subsystem
• “SANRISE95xxV series subsystem” indicates the
SANRISE9530V, SANRISE9570V, and
SANRISE9580V.
• In this user guide, the arrays appear as
“SANRISE9500V subsystem”.
• In XP External Storage panes, the arrays appear as
“9500V”.
• Alternate paths are in Single mode.
SANRISE2000 series subsystem
• “SANRISE2000 series subsystem” indicates the
SANRISE2200 and SANRISE2800.
• In this user guide, the arrays appear as “SANRISE2000
subsystem”.
• In XP External Storage panes, the SANRISE2200 is a
“0401”, and the SANRISE2800 is a “0400”.
• Alternate paths are in Multi mode.
SANRISE H12000 subsystem
• In XP External Storage panes, the array is a “12000”.
• Alternate paths are in Multi mode.
SANRISE H10000 subsystem
• In XP External Storage panes, the array is a “10000”.
• Alternate paths are in Multi mode.
14
Preparing for XP External Storage operations
Table 1 Storage arrays that can be connected as external arrays (continued)
Storage array
Notes
SANRISE H1024/H128 subsystem
• In XP External Storage panes, the arrays appear as
“1024” and “128”, respectively.
• Alternate paths are in Multi mode.
SANRISE H512/H48 subsystem
• In XP External Storage panes, the arrays appear as
“512” and “48”, respectively.
• Alternate paths are in Multi mode.
SANRISE H256 subsystem
• In XP External Storage panes, the array is a “256”.
• Alternate paths are in Multi mode.
IBM Storage Subsystem
For specific supported storage arrays, contact your
HP account support representative.
EMC Storage Subsystem
For specific supported storage arrays, contact your
HP account support representative.
Fujitsu Storage Subsystem
For specific supported storage arrays, contact your
HP account support representative.
NEC Storage Subsystem
For specific supported storage arrays, contact your
HP account support representative.
CAUTION: For more information about alternate path modes, see “Setting alternate paths for
external LUs” (page 93).
Contact your HP account support representative for the latest external array and FC switch support
matrix.
XP External Storage requirements
Table 2 XP External Storage requirements
Item
Requirement
Required products
• XP Command View Advanced Edition Software version
2.0 or later, or Remote Web Console
• HP XP LUN Configuration and Security Manager (for
setup)
• HP XP RAID Manager version 01.12.06 or later (if HP
XP Business Copy is used)
Maximum number of connected external disk arrays
60 per port
Maximum number of external LUs addressable per local
array port
1,024 per port
XP External Storage requirements
15
Table 2 XP External Storage requirements (continued)
Item
Requirement
Maximum number of external LUs that can be connected
• For the XP12000, 15,360 volumes can be connected
• For the XP10000/SVS200, 8,192 volumes can be
connected
• 1,024 volumes can be connected per port
NOTE: If you use HP XP Snapshot Software, the number
of external LUs that can be connected is as follows:
• For the XP12000:
Number of external LUs + Number of virtual
LUs
15,360
• For the XP10000/SVS200:
Number of external LUs + Number of virtual
LUs
8,192
NOTE: A LUN ID of a connected external volume should
be set in the range of 0 – 1,023. An external volume that
has a LUN ID equal to or larger than 1,024 cannot be
connected.
Maximum number of FC paths that can exist to one external 8
LU
Maximum capacity of an external LU
2 TB (4,294,967,296 blocks) per external LU (OPEN-V)
If you specify an external LU that is larger than 2 TB, you
can only access data stored in the field up to 2 TB.
Minimum capacity of an external LU
About 38 MB (77,760 blocks) per external LU
(non-OPEN-V)
When the volume's emulation type is OPEN-V, minimum
capacity is about 47 MB (96,000 blocks) per external LU.
Installing XP External Storage
To perform XP External Storage operations with XP Command View Advanced Edition Software
or Remote Web Console, you must install an XP External Storage license key.
1. Start XP Command View Advanced Edition Software or Remote Web Console for the local
array.
2. Enable the XP External Storage options in XP Command View Advanced Edition Software or
Remote Web Console and on each XP External Storage array.
For instructions, see the HP XP Command View Advanced Edition Software user guide for XP Disk
Arrays or the HP XP Remote Web Console user guide for XP12000/XP10000 Disk Arrays and
SVS 200.
Preparing for XP External Storage settings
Before using XP External Storage, collect the information necessary for defining its settings. The
following information is required:
16
•
Ports that can be set to external ports (see “External ports” (page 17))
•
External array and LUs to map to the internal LDEVs (see “External LU to be mapped” (page 17))
•
Configuration of external LU groups (see “External LU groups” (page 17))
•
Configuration of external LU attributes (see “External LU attributes set by mapping” (page 17))
•
Configuration of alternate paths (see “Alternate paths” (page 19))
Preparing for XP External Storage operations
Each item above is explained in the following sections.
External ports
Local array ports used for XP External Storage must be set to a designation of External. When the
external array is connected to the local array's external port via Fibre Channel, you can view
information about the external array from XP Command View Advanced Edition Software or Remote
Web Console. The external array can be connected only to ports designated as External.
To set the port attribute to External, you must release any existing paths currently configured for
the port. You cannot change the attribute of the port where paths are set to External. Before starting
XP External Storage operations, you must know which ports you can change to External.
Note: You cannot use ports with attributes set for XP Continuous Access Software (such as RCU
Target or Initiator) or other features as external ports for XP External Storage. If the port attribute
is set to something other than External, change its attribute to External. XP Flex Copy and XP
External Storage can share an XP12000/XP10000/SVS200 port with an attribute of External.
For instructions, see Setting a local array's port attributes.
External LU to be mapped
When connecting an external array to an external port, you can map LUs in the external array
(external LUs) as LDEVs in the local array (internal LDEVs). Verify which LUs in which external array
can be mapped as internal LDEVs.
You can map only one external LU to a given internal LDEV and map up to a theoretical limit of
1,024 external LUs per local array port.
Note: A LUN ID of a connected external volume should be set in the range of 0 – 1,023. An
external volume that has a LUN ID equal to or larger than 1,024 cannot be connected.
An external LU's maximum available capacity depends on the emulation type set when the LU is
mapped. You cannot access data stored in the field over the external LU's maximum available
capacity. To set an emulation type other than OPEN-V, you cannot map external LUs smaller than
38 MB (77,760 blocks). To set the OPEN-V emulation type, you cannot map external LUs of smaller
than 47 MB (96,000 blocks). For more information about the capacity of the external LU for each
emulation type, see “Required volume capacity for emulation types” (page 160).
External LU groups
When mapping an external LU as an internal LDEV, you must register the external LU in an external
LU group.
You can classify external LUs set by XP External Storage into groups according to their use. The
group is called an external LU group (ExG). For instance, you can register several LUs in one
external array to one external LU group. Or, if data you want to manage in a chunk is stored in
LUs in various external arrays, you can register those LUs in one external LU group, and manage
them as a block.
You must assign a number from 1 to 16,384 to each external LU group. For the XP12000, you
can create a maximum of 15,360 external LU groups. For the XP10000/SVS200, you can create
a maximum of 8,192 external LU groups. You can register a maximum of 256 volumes in one
external group.
External LU attributes set by mapping
When mapping an external LU as an internal LDEV, use the Add LU pane in XP External Storage
to set the external LU's attributes. For instructions, see Mapping external LUs (Add LU).
Preparing for XP External Storage settings
17
The following are the external LU's attributes:
•
Emulation type
Set the mapped LU's emulation type by selecting any emulation type from the drop-down list.
However, if you plan to use the mapped LU for XP Flex Copy operations, or you plan to access
existing data in the external LU, you must select the OPEN-V emulation type to avoid data
resizing.
If you plan to use existing data in the external LU from the local array after mapping, you must
select the OPEN-V emulation type. For example, to migrate existing data in the external LU to
the local array volume, you must set the OPEN-V emulation type when mapping the external
LU.
You must also select the OPEN-V emulation type when VMA of HP XP LUN Security Extension
Software is set for the external LU on the external array side.
If you select an emulation type other than OPEN-V, additional space is taken for XP
management information. This means that after mapping, LU capacity is less than the actual
external LU capacity (and the original data must be considered lost). For more information
about volume capacity, see Limitations on External Storage XP operations.
•
IO Suppression mode (Enable or Disable)
When mapping an LU, determine whether to suppress I/O operations from hosts (via the local
array) to the mapped external LU.
If you select Enable, you can use the mapped LU only for XP Flex Copy operations.
If you select Disable, a host connected to the local array can use the mapped external LU as
if it were an LU inside the local array, but you cannot use the LU for XP Flex Copy operations.
You can select Enable only when you set the OPEN-V emulation type for the mapped LU.
When you set an emulation type other than OPEN-V, the IO Suppression mode is automatically
set to Disable.
•
Cache Mode (Enable or Disable)
Cache mode specifies if I/O from the host is propagated synchronously (Disable) or
asynchronously (Enable) to the external storage device. By default cache mode is set to Enable.
All I/O to and from the local array in both cache modes always uses cache. Write operations
are always backed up in duplex cache.
If you select Enable, the local array signals the host that an I/O operation completed after
receiving the data into the local array's cache memory, and then asynchronously destages
the data to the external array.
If you select Disable, the local array signals the host that an I/O operation completed only
after the local array has synchronously written the data to the external array.
When IO Suppression mode is set to Enable, Cache Mode changes by default to Disable.
If you use an external LU and set Cache Mode to Disable for HP XP Cache LUN Software
operations, you cannot use the XP Cache LUN Bind mode. For more information, see the HP
XP Cache LUN user guide for XP12000/XP10000 Disk Arrays and SVS 200.
18
Preparing for XP External Storage operations
NOTE:
•
When you set the cache mode, note the following:
◦
Data that is not written by the host (for example, data written by XP Business Copy
Software) is asynchronously destaged to the external array 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 array 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 array as configured in the
Cache Mode setting.
CLPR
When using XP Disk/Cache Partition to partition cache memory, set the cache logical partition
(CLPR) used for accessing the mapped LU. You can also specify whether the CU selected at
mapping is restricted to the storage management logical partition (SLPR) the CLPR belongs to.
For more information about CLPRs and SLPRs, see the HP XP Disk/Cache Partition user guide
for XP12000/XP10000 Disk Arrays and SVS 200.
Alternate paths
When mapping an external LU as an internal LDEV, paths are set from the internal LDEV to the
external LU.
If two or more paths to the external LU are equipped from different clusters, the number of paths
you set when mapping the volume are available. If one path is equipped, only that path is available.
You can set up to eight paths to each external LU, including paths automatically set. Among the
paths to the external LU, the path with the highest priority is called the primary path, and other
paths are alternate paths.
Alternate path modes include Single mode and Multi mode. The alternate path mode, Single mode
or Multi mode, depends on the connected external array. For Single mode, only the path with the
highest priority (primary path) is used to execute I/Os to the external LU. When an error occurs
in the primary path, the path with the second highest priority is used (that is, no per-LU dynamic
load balancing across paths). For Multi mode, all set paths are used at the same time. The paths
are used to execute I/Os to the external LU, distributing the work load (round-robin processing).
For example, when an external LU volume with an alternate path in Single mode is mapped to an
internal LDEV using XP External Storage, host I/O operations to the external LU via the local array
are normally enabled using the mapped path. If the mapped path is not available (for instance,
during array maintenance or following a failure in the channel processor), the path is switched
automatically to the alternate path (if available). As long as an alternate path is available, host
I/O operations continue as usual, even when an error occurs in the original path.
NOTE: When the primary path cannot be used for the length of the Path Blockade Watch timer
(for example, 180 seconds), the path is switched to an alternate path.
If you have not configured any alternate paths, host I/O operations are suspended when the
primary path becomes unavailable (such as during array maintenance operations or following a
failure in the channel processor).
HP recommends configuring alternate paths for safer operation and increased bandwidth. For
instructions, see Setting alternate paths for external LUs.
You can set alternate paths when the external LUs are mapped as the internal LDEVs (see Mapping
external LUs (Add LU)). You can also set alternate paths after completing the mapping operation
(see Setting alternate paths for external LUs).
Preparing for XP External Storage settings
19
Example of an alternate path configuration
Figure 2 (page 20) shows an example of an alternate path configuration. In Figure 2 (page 20),
external array ports WWN A and WWN B are connected to CL1-A and CL2-A, respectively,
which are designated as external ports in the local array. You must specify the port of a different
cluster in the local array for the alternate path, as ports CL1 and CL2 are specified in the figure.
Figure 2 Example of alternate path configuration
Figure 3 (page 20) shows another example of an alternate path configuration. In Figure 3 (page
20), two ports are specified in the local array and connected to ports in the external array via
switches. In this example, two ports from different XP12000/XP10000/SVS200 clusters are
specified in the local array, thereby making it possible to configure an alternate path for high
availability.
Figure 3 Example of alternate path configuration using two switches
In Figure 4 (page 21), two paths are configured between the internal LDEV and external LU.
However, only one port is specified in the local array and two ports are specified in the external
arrays via the switch. Since two ports of different clusters must be set in the local array for XP
External Storage to use alternate path settings, HP does not recommend the configuration shown
in Figure 4 (page 21).
20
Preparing for XP External Storage operations
Figure 4 Example of incorrect alternate path configurations
Examples of switching I/O execution paths to alternate paths
There are two alternate path modes: Single mode and Multi mode. This section describes examples
of the performance when the I/O execution path switches to the alternate path for each path mode
as follows:
•
Alternate path mode is Multi mode.
•
Alternate path mode is Single mode.
•
Alternate path mode is Single mode and at least one alternate path is in Standby status.
For more information about path status, see Adding alternate paths by selecting multiple external
LUs (Add Paths).
•
Alternate path mode is Multi mode.
Figure 5 (page 22) shows an example of when the alternate path mode is Multi mode. When
an error occurs in one path, I/Os execute using paths other than the error path.
NOTE:
As you restore the error path, use of the restored path automatically resumes.
Preparing for XP External Storage settings
21
Figure 5 Alternate path mode is Multi mode
Note: In Multi mode, active I/O load balancing occurs across external array ports and
controllers. The XP and EMC DMX are examples of external arrays that use Multi mode.
•
Alternate path mode is Single mode.
Figure 6 (page 23) shows an example of when the alternate path mode is Single mode. When
an error occurs in the path used for I/Os, the I/O execution path switches to the path with
the second highest priority.
Note: As you restore the path with a priority higher than the current path, the I/O execution
path automatically switches to the restored path with the highest priority.
22
Preparing for XP External Storage operations
Figure 6 Alternate path mode is Single mode
•
Alternate path mode is Single mode and at least one alternate path is in Standby status.
Figure 7 (page 24) shows an example of when the alternate path mode is Single mode and
there are alternate paths in Normal and Standby status. Figure 8 (page 24) shows another
example of when the alternate path mode is Single mode. In Figure 8 (page 24), there are
alternate paths in Standby status only.
When an error occurs in the path used for I/Os, the I/O execution path switches to the path
with the second highest priority in Normal status (Figure 7 (page 24)). If there is no path in
Normal status other than the path used for I/Os, the status of the path in Standby status
automatically changes to Normal and the I/O execution path switches to that path
(Figure 8 (page 24)).
NOTE: When the external array is an EVA array, as you restore the path with the highest
priority, the I/O execution path switches back to the restored highest priority path. In this
case, the status of the path for which the status changed to Normal when the error occurred
changes back to Standby.
Preparing for XP External Storage settings
23
Figure 7 Alternate path mode is Single mode with alternate paths in Normal and Standby
Figure 8 Alternate path mode is Single mode with alternate paths in Standby only
24
Preparing for XP External Storage operations
Powering arrays on or off
This section describes procedures for powering local and external arrays on or off after XP External
Storage operations have started.
This section explains the following:
•
“Commands for Turning On or Off Only an External Array” (page 25)
•
Powering local arrays on or off
•
Poweringexternalarraysonoroff
•
“Turning On or Off Power Supply of Both local and external arrays” (page 27)
CAUTION: To power both the local and external arrays off, first power off the local array, and
then power off the external array.
CAUTION: To power both the local and external arrays on, first power on the external array,
and then power on the local array.
Commands for Turning On or Off Only an External Array
When you turn on or off the power supply of only external array while the power supply of XP12000
Disk Array keeps on, you need to execute the following XP External Storage Software commands.
The procedures below will utilize the following commands:
•
Disconnect Subsystem
Execute the Disconnect Subsystem command from the XP Command View Advanced Edition
Software or Remote Web Console GUI when you need to perform maintenance or stop the
local or external array. This command stops acceptance of all host I/O operations to the
external LU mapped as the internal LDEV. All outstanding data in cache memory on the local
array intended for the external LU is written (destaged) to the external LU.
For instructions on executing the Disconnect Subsystem command, see Disconnecting external
arrays or LUs.
NOTE: To disconnect an individual LU, use the Disconnect Volume command. To delete a
single external LU's mapping, use the Disconnect Volume command and then the Delete LU
command. For instructions, see Deleting external LU mappings (Delete LU).
•
Check Paths & Restore Vol.
This command checks if defined information about the mapped external LU and the actual
external LU status match. If the external LU can be used as the mapped local array volume,
the external LU is set to accept I/O, and you can continue using the external LU as a mapped
LU.
Use this command to restore the external LU, which is set to reject host I/O operations by the
Disconnect Subsystem or Disconnect Volume command, as the mapped volume. You can
execute the Check Paths & Restore Vol. command for the entire array or an individual LU.
If an error occurs in the external storage path such that the command fails, correct the error
so the path can be restored, and execute the Check Paths & Restore Vol. command again.
For instructions, see Checking the connection status and resuming external LU operations
(Check Paths & Restore Vol.).
NOTE: When executing the Check Paths & Restore Vol. command, if the external LU is ready
to be restored as the mapped LU, the external LU is set to Available. However, if the external
LU is not ready to be restored, the external LU status remains as Blocked.
Powering arrays on or off
25
Powering local arrays on or off
To power local arrays off
CAUTION: When you want to turn off both the local array and the external array, you first need
turn off the local array, and then turn off the external array.
1.
2.
3.
Stop read and write I/Os to the external LU that is mapped as a local array internal LDEV.
Perform other operations required before powering the local array off.
Turn the local array's power off.
NOTE: As you turn the local array's power off, all data for the external LU in the local array's
cache memory is written in the external LU (all data is destaged).
To power local arrays on
CAUTION: When you want to turn on both the local array and the external array, you first need
to turn on the external array, and then turn on the local array.
1.
2.
Power on the external array containing the external LU mapped as a local array internal LDEV.
Turn on the local array's power.
CAUTION: When the local array is powered off after executing the Disconnect Subsystem
command, you cannot access the mapped external LU from the local array when you first power
on the local array. You must execute the Check Paths & Restore Vol . command to resume using
the mapped external LU. The Check Paths & Restore Vol. command checks if the defined information
and actual status of the external LU mapped as a local array volume match. If the external LU is
ready to be used as a mapped volume, the LU is set to accept I/Os and you can resume using the
volume as a mapped volume.
CAUTION: When the Disconnect Subsystem or Disconnect Volume command is executed and all
data in cache memory is written to the external LU, the displayed information for Ex-Dev. Status
in the Device list becomes Disconnect.
Powering external arrays on or off
To power external arrays off
1.
2.
Stop read and write I/Os to the external LU that is mapped as a local array internal LDEV
and is located in the external array you want to power off.
Execute the Disconnect Subsystem command for the external array you want to power off.
Additional I/O to the external LU is stopped and all data in the local array cache memory is
written to the external LU (all data is destaged). For instructions, see Disconnecting external
arrays or LUs.
3.
4.
Perform other operations required before powering the external array off.
Power the external array off.
CAUTION: After executing the Disconnect Subsystem command, if you need to use the mapped
external LU again, execute the Check Paths & Restore Vol. command.
To power external arrays on
1.
26
Power on the external array containing the external LU that is mapped as a local array internal
LDEV.
Preparing for XP External Storage operations
2.
Execute the Check Paths & Restore Vol. command. For instructions, see Checking the connection
status and resuming external LU operations (Check Paths & Restore Vol.).
CAUTION: When powering the external array off after executing the Disconnect Subsystem
command, you cannot access the mapped external LU from the local array when you initially turn
on the external array. You must execute the Check Paths & Restore Vol. command to resume using
the mapped external LU. The Check Paths & Restore Vol. command checks the defined information
and the actual status of the external LU mapped as a local array internal LDEV. If the external LU
is ready to be used as a mapped volume, the LU is set to accept I/Os and you can resume using
the LU as a mapped volume.
Turning On or Off Power Supply of Both local and external arrays
This section explains how to turn on or off the power supply of both the local and external array
using XP Business Copy Software.
To turn OFF the power supply of both arrays:
1. Stop all read or write I/Os to the local array.
2. Split all HP XP Business Copy pairs (pairsplit operation). For details on the pairsplit operation,
see HP XP Business Copy user guide for XP12000/XP10000 Disk Arrays and SVS 200.
3. Turn off the power supply of the local array.
CAUTION: Make sure that the power supply of the local array is completely off and then
go on to the next step.
4.
Turn off the power supply of the external array.
CAUTION:
Make sure that the power supply of the external array is completely off.
To turn ON the power supply of both arrays:
1. Turn on the power supply of the external array.
CAUTION: Make sure that the power supply of the external array is completely on and then
go on to the next step.
2.
Turn on the power supply of the local array.
CAUTION: Make sure that the power supply of the local array is completely on and then
go on to the next step.
3.
4.
Resynchronize all HP XP Business Copy pairs (pairresync operations). For details on the
pairresync operation, see HP XP Business Copy user guide for XP12000/XP10000 Disk Arrays
and SVS 200.
Start the read or write I/Os to the local array.
All read and write I/Os with Fibre Channel connections, iSCSI connections, and NAS
connections should be started.
Using mapped external LUs from the host connected to the local array
The following sections describe examples of using the mapped external LU from the host connected
the local array. There are different ways of using the mapped external volume.
•
Writing new data to mapped external LUs
•
Using existing data in mapped external LUs
Using mapped external LUs from the host connected to the local array
27
Writing new data to mapped external LUs
Figure 9 (page 28) shows an example of writing new data in the mapped external LU from the
host connected to the local array.
1. Use the XP External Storage GUI to map the LU in the external array as an internal LDEV of
the local array.
CAUTION:
Set the IO Suppression mode to Disable.
You can select the mapped volume's emulation type as required. If you select an emulation
type for an open-system (such as OPEN-V), go to step 2. If you select an emulation type for a
mainframe system (such as 3390-3), go to step 3
For more information, see Mapping external LUs (Add LU).
2.
For open-system emulation types (such as OPEN-V, which HP recommends), the status of the
mapped LDEV is set to Normal and is not automatically formatted. To optimally initialize the
mapped LU's data area, use Volume Manager to format the mapped LU. For instructions, see
the HP XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP
XP10000 Disk Array, HP 200 Storage Virtualization System.
Go to step 4.
3.
4.
For mainframe-system emulation types (for example, 3390-XX), the status of the mapped LU
is set to Blockade, pending resizing and formatting. Use Volume Manager to format the volume.
If you mapped a volume for which the data area is already zero-formatted on the external
array side, use Volume Manager's Write to Control Blocks operation to restore the volume.
For instructions, see the HP XP LUN Configuration and Security Manager user guide: HP
XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization System.
Configure the path from the Target port to the mapped volume to perform host I/O operations.
The mapped LDEV is available for host I/O operations.
After the path is set, host I/O operations to the mapped LU are available.
Figure 9 Writing new data to mapped external LUs
28
Preparing for XP External Storage operations
Using existing data in mapped external LUs
Figure 10 (page 29) shows an example of using existing data in a mapped external LU from the
host connected to the local array.
1. From the host connected to the external array, write data to the LU in the external array.
2. Use XP External Storage to map the LU in the external array containing data as an internal
LDEV of the local array.
When mapping the external LU, set the following attributes for the mapped LU:
•
Emulation type: OPEN-V
•
IO Suppression mode: Disable
For more information, see Mapping external LUs (Add LU).
CAUTION: You must set the emulation type to OPEN-V to read existing data in the mapped
external LU from the local array side.
3.
Configure the path from the Target port to the mapped LU to perform host I/O operations.
After the path is set, host I/O operations to the mapped volume are available.
NOTE: Do not access any external storage volume that is mapped as an XP External Storage
volume from a host connected directly to the external array. Also, do not access an XP External
Storage mapped external array volume using the external array's functions (for example, local
replication). After mapping an external disk volume as a local array volume, access the mapped
external disk volume only via the local array.
NOTE: Except on the MSA, a host can directly access external array volumes that are not mapped
as local array volumes.
Figure 10 Using existing data in mapped external LUs (without formatting)
Uninstalling XP External Storage
To uninstall XP External Storage, cancel any existing Flex Copy pairs, and delete any external LU
mappings.
Uninstalling XP External Storage
29
1.
Log in to XP Command View Advanced Edition Software or Remote Web Console. For
instructions, see the HP XP Command View Advanced Edition Software user guide for XP Disk
Arrays or the HP XP Remote Web Console user guide for XP12000/XP10000 Disk Arrays
and SVS 200.
2.
3.
4.
Click the XP External Storage button (
). XP External Storage starts.
Cancel any existing Flex Copy pairs. For instructions, see the HP Flex Copy XP user guide.
Delete any external LU mapping. For instructions, see Deleting external LU mappings (Delete
LU).
Use the XP Command View Advanced Edition Software or Remote Web Console Licensing
module to remove the XP Flex Copy license key. For instructions, see the HP XP Command
View Advanced Edition Software user guide for XP Disk Arrays or the HP XP Remote Web
Console user guide for XP12000/XP10000 Disk Arrays and SVS 200.
For the local array, use the XP Command View Advanced Edition Software or Remote Web
Console Licensing module to remove the XP External Storage license key. For instructions, see
the HP XP Command View Advanced Edition Software user guide for XP Disk Arrays or the
HP XP Remote Web Console user guide for XP12000/XP10000 Disk Arrays and SVS 200.
5.
6.
Limitations on XP External Storage operations
•
External LUs can be mapped as any CU:LDEV combination from 00:00 to 3F:FF.
•
Only ports in SLPR0 can be set as external ports.
•
Before mapping external LUs, make sure that external LUs are not reserved by a host.
External LUs that are reserved by a host cannot be mapped as internal LDEVs. If external LUs
are reserved by a host, cancel the reserve settings and then map the external LUs.
•
Do not reserve mapped external LUs for a host.
Internal LDEVs, to which external LUs are mapped, will be blocked if the mapped external LUs
are reserved by a host.
•
Do not access any external storage volume that is mapped as an XP External Storage volume
from a host connected directly to the external array. Also, do not access an XP External Storage
mapped external array volume using the external array's functions (for example, local
replication). After mapping an external disk volume as a local array volume, access the
mapped external disk volume only via the local array.
•
Except on the MSA, a host can directly access external array volumes that have not been
mapped as local array volumes.
•
XP Continuous Access P-VOLs, S-VOLs, and journal volumes are not supported on MSA arrays.
•
HP does not recommend that volumes involved with XP Snapshot reside on external MSA
arrays.
•
When an external array that has an ownership is connected to XP12000 Disk Array, configure
the path to the primary controller in the external array as primary path.
Ownership is an exclusive right to control volumes. A controller that has an ownership is called
a primary controller. If a path to a controller without ownership is configured as primary path,
the ownership will be transferred and it may affect the performance.
30
Preparing for XP External Storage operations
•
When a port in an external array connected to XP12000 Disk Array has a management LU
(for example, Universal Xport LU) that stores control information from a particular application,
note the following:
◦
A management LU cannot be used as an external volume. A management LU in this
document means an LU that receives commands issued by a particular application and
that controls or manages the application. A command device is not a management LU.
◦
Perform one of the following operations on the external array before you perform discovery
operation. If none of the following operations are performed, an external array that has
a management LU might not be recognized.
–
Delete the management LU from the port connected to XP12000 Disk Array.
–
Make sure that at least one LU is used for data storage and has a smaller LUN than
the LUN of the management LU. Also make sure that this LU is set to the port connected
to XP12000 Disk Array.
–
Configure the access attribute of the management LU to prohibit read and write
operations by using security function.
•
If you map an external LU that is more than 2 TB with the setting of OPEN-V emulation type,
you can access data stored in the field up to 2 TB. You cannot access data stored in the field
over 2 TB.
•
When mapping a volume that has a capacity of 2 TB or less in the external array and (external
LU) with the OPEN-V emulation type, the LU is defined as an internal LDEV with the same
capacity as the mapped external LU. That is, no space is forfeited for management space,
and no formatting of that data occurs. Therefore, OPEN-V is recommended.
Figure 11 Example of external LU with 2 TB or less
•
If you map an external LU that is equal to or greater than 575.98 GB with an OPEN emulation
type other than OPEN-V, you can access data stored in the field up to 575.98 GB. You cannot
access data stored in the field over 575.98 GB.
However, for emulation types with a small base capacity, some of the field of 575.98 GB
might not be available. For more information, see “Required volume capacity for emulation
types” (page 160).
•
If you map an external LU that is equal to or greater than 575.98 GB with a 3380 mainframe
emulation type, you can access data stored in the field up to 575.98 GB. You cannot access
data stored in the field over 575.98 GB.
However, for emulation types with a small base capacity, some of the field of 575.98 GB
might not be available. For more information, see “Required volume capacity for emulation
types” (page 160).
Limitations on XP External Storage operations
31
•
If you map an external LU that is equal to or greater than 695.98 GB with a 3390 mainframe
emulation type, you can access data stored in the field up to 695.98 GB. You cannot access
data stored in the field over 695.98 GB.
However, for emulation types with a small base capacity, some of the field of 695.98 GB
might not be available. For more information, see “Required volume capacity for emulation
types” (page 160).
•
If you plan to use the mapped external LU from the mainframe OS (volume is mapped with a
3380-x or 3390-x mainframe emulation type), you must select an external LU that consists of
one LDEV or you must first adjust the capacity of the external LU to be mapped. If multiple
LDEVs exist in one external LU and if numerous I/Os are made to these LDEVs, the read and
write commands might time-out. When the commands time-out, the SIM (21D2xx) is reported.
•
When mapping an external LU as internal LDEVs with emulation types other than OPEN-V,
the number of volumes and the volume capacity of the mapped internal LDEVs depends on
the original external LU's capacity and each emulation type's normal size. When mapping
an external LU using emulation types other than OPEN-V, an XP array management information
area is required in the mapped LU. This means that the capacity available after mapping is
slightly smaller than the actual external LU capacity. Available capacity decreases by the size
of the XP array management information area, and all prior data must be considered lost. For
more information, see the HP Flex Copy XP user guide.
Figure 12 (page 32) shows an example where the external LU's original capacity is larger
than (or a multiple of) the normal size of the local array's emulation type (OPEN-3 in this
example). Therefore, in this example, the local array can realize two fully-sized OPEN-3 LDEVs,
with some space (insufficient to create a full OPEN-3) left over.
Figure 12 External LU capacity is larger than the specified emulation type's basic capacity
(OPEN-3 example)
32
Preparing for XP External Storage operations
Figure 13 External LU capacity is smaller than the specified emulation type's basic capacity
•
IO Suppression mode can only be selected when the volume being mapped is set to the
OPEN-V emulation type. If a different emulation type is set, IO Suppression mode is
automatically set to Disable.
•
If you use the mapped external LU from the host connected to the local array, set the IO
Suppression mode to Disable when mapping the LU. For XP External Storage, select Disable.
For XP Flex Copy, select Enable.
•
If you use the mapped external LU for the copy source or copy destination volume for an XP
Flex Copy pair, set the emulation type to OPEN-V when mapping the volume.
•
If you use the mapped external LU for the copy source or copy destination volume for an XP
Flex Copy pair, set IO Suppression mode to Enable when mapping the volume.
•
The local array does not force the external array to reserve the mapped external LU. Therefore,
do not write directly to an external array LU (that is, without writing via the local XP array)
with IO Suppression mode set to Disable from the external array side.
If XP Flex Copy operations are in progress for a volume with IO Suppression mode set to
Enable, be careful when updating data in that external LU from the external array side.
•
IO Suppression mode is automatically set to the same status for all LDEVs in a given external
LU.
•
Cache Mode is automatically set to the same status for all LDEVs in a given external LU.
•
If you set an open-system emulation type (such as OPEN-V) when mapping the external LU,
you can use the external LU immediately.
To optionally initialize the LU's data area, use Volume Manager to format the LU. For
instructions, see the HP XP LUN Configuration and Security Manager user guide: HP XP12000
Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization System.
•
If you set a mainframe-system emulation type (such as 3390-3) when mapping the external
LU, format the LU or perform the Write to Control Blocks operation to make the volume usable.
After the mapping operation, the mapped LU's status is Blockade. Use Volume Manager to
format the volume or perform the Write to Control Blocks operation to make the volume usable.
◦
If you mapped a volume that has already been zero-formatted on the external array side,
perform the Write to Control Blocks operation.
◦
If you mapped a volume that has not been zero-formatted on the external array side,
format the volume on the local array side.
For instructions on the formatting and Write to Control Blocks operations, see the HP XP LUN
Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk
Array, HP 200 Storage Virtualization System.
Limitations on XP External Storage operations
33
If you format the external array's mapped LU from the external array side, data that existed
prior to formatting cannot be ensured. When using the mapped external LU from the mainframe
OS, format the mapped volume from the local array side.
34
•
IO Suppression mode is set when the LU is mapped and it cannot be changed while the LU
is mapped. To change IO Suppression mode, delete the external LU mapping (Delete LU
operation), and remap the LU with different attributes (Add LU operation).
•
External LU attributes for all LDEVs created in an external LU are set to the same values. Those
attributes are modified when the LDEVs are reconfigured using Volume Manager.
•
Mapped volumes that have different external volume attributes (IO Suppression mode, Cache
Mode) cannot be used to create one LUSE volume.
•
A mapped external LU with IO Suppression mode set to Enable (such as for XP Flex Copy)
cannot be used for the local array's XP Cache LUN operations.
•
For a external LU with IO Suppression mode set to Disable (such as for XP External Storage),
XP Cache LUN's Bind mode is not available.
•
If you use the mapped external LU for XP Cache LUN operations and set the bind mode, XP
Cache LUN operations require a cache of twice the capacity of the user data.
•
For XP External Storage, IO Suppression mode is typically set to Disable. You cannot use a
mapped external LU with IO Suppression mode set to Enable for pair copy operations in XP
Continuous Access, Hitachi TrueCopy™ for z/OS, XP Continuous Access Journal, Hitachi
Universal Replicator™ for z/OS, XP Business Copy, Hitachi ShadowImage™ for z/OS, or
XP Snapshot. Also, the external LU cannot be used for automatic XP Auto LUN operations.
•
Attributes originally set for an external LU on the external array side (such as port security, HP
XP Secure Manager, and Volume Retention Manager attributes) are not kept when the external
LU is mapped as a local array internal LDEV. To keep the original attributes, set those attributes
on the mapped external LU from the local array side.
•
If you map an external LU for which the VMA of Data Retention Utility is set, you need to
configure system options before performing the Discovery operation to enable the VMA
information. Call HP technical support to ask about how to configure system options.
•
If you mapped the external LU and previously set the VMA of Data Retention Utility in that
volume, the former VMA setting is superseded when you map the volume again. However, if
Data Retention Utility is not installed when you remap the volume, the volume with the VMA
setting cannot be mapped. To change the VMA setting, change it from the local array side.
•
Do not combine LDEVs of multiple external volumes to create a LUSE volume. The LDEVs in
the same external volume can only be used to set the LUSE volumes. When you combine LDEVs
of multiple external volumes to create a LUSE volume, you need to consider:
◦
If a LUSE volume consists of multiple external volumes and one external volume has lower
performance than the other volumes, the lower performance of the volume affects the
performance of the LUSE volume.
◦
When an external volume which is a component of a LUSE volume is blocked, data
reliability of the LUSE volume will deteriorate because the LUSE volume has both accessible
area and inaccessible area from a host.
◦
When you disconnect an external volume or resume the use of an external volume, you
need to perform the operation at the same time on all the external volumes which are
components of the LUSE volume.
•
Do not update a volume being used or operated by XP Flex Copy. Also do not update the
external LU on the external array side.
•
You can delete up to 256 mappings for external LUs at one time.
Preparing for XP External Storage operations
•
Operations cannot be performed if some parts of the local array are blocked. In this case,
restore blocked parts of the local array, and retry the operation.
•
When using the Thunder 9500V series subsystem as an external array, the following versions
are recommended. If you use a 9500V array with a version that is earlier than the following
versions, the SATA drive information might not display correctly.
•
◦
For Thunder 9530V, Thunder 9520V, Thunder 9570V: version 0658 or later
◦
For Thunder 9580V, Thunder 9585V: version 1658 or later
When you use TagmaStore AMS 2000 series (AMS2100/2300/2500) subsystem as an
external disk array, unnecessary load to the external disk array should be avoided. When
the TagmaStore AMS 2000 series subsystem is used as an external disk array, the path mode
between disk array is Multi mode. Therefore, when there are a lot of external paths and
mapping volumes, the load to the external subsystem becomes high and some commands
from host to XP24000 or some commands from XP24000 to the external disk array may time
out.
To keep the load proper, the following is recommended.
◦
Define volumes of each TagmaStore AMS2000 series disk array to set external path
number to two. In that case, set the paths to the ports of each controller of TagmaStore
AMS2000 series subsystem.
◦
Set the queue of commands which are issued at the same time from one AMS2000 series
disk array to 500 or less. The calculation formula to derive the number of the queue
commands per AMS2000 series disk array is shown as follows. (number of queues) x
(number of paths of external volumes) x (number of external volumes which issue commands
at the same time) < 500 For more information about setting the queue of commands (see
“Changing an external array's port setting” (page 116) ).
•
When you use external volumes of TagmaStore AMS2000 series disk array with copy software,
the copy operation needs to be distributed to two or more RAID groups. There is an upper
bound to the number of pairs, which can be used for initial copy or resynchronization.
Therefore, the copy operation may focus on a specific RAID group according to the order of
the copy operation when the copy operation is performed to two or more external volumes.
The drive of the TagmaStore AMS2000 series disk array may become a bottleneck, which
causes insufficient performance, when the copy operation focuses on a specific RAID group.
•
Do not map multiplatform volumes of external arrays as internal LDEVs.
•
After executing the Check Paths & Restore Vol., Disconnect Subsystem, or Disconnect Volume
command, click the Refresh button ( ) on the XP Command View Advanced Edition Software
or Remote Web Console main pane to update the information, and check the current status.
•
When the external LU's status is Blockade, execute the Check Paths & Restore Vol. command.
If the Check Paths & Restore Vol. command does not restore the external LU's status, the path
to the external array might be blocked. In this case, see Troubleshooting External Storage XP
for instructions on restoring the path to the external array.
If the external LU's status remains Blockade even though you restored the path to the external
array and executed the Check Paths & Restore Vol. command, execute the Restore command.
•
If you execute the Disconnect Subsystem or Disconnect Volume command when I/Os from the
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.
Limitations on XP External Storage operations
35
•
You cannot execute the Disconnect Subsystem or Disconnect Volume command for external
LUs that include LDEVs set as copy pairs for XP Flex Copy, XP Business Copy, Hitachi
ShadowImage for z/OS, XP Continuous Access Journal, Hitachi Universal Replicator for z/OS,
XP Continuous Access, Hitachi TrueCopy for z/OS, or XP Snapshot. However, these commands
can be executed in one of the following cases:
◦
When the XP Business Copy pair status is PSUE
◦
When the ShadowImage for z/OS™ pair status is Suspend.
◦
When the external volume is set as a pool volume (pool-VOL) and the status of that XP
Snapshot pair is PAIR
•
You cannot execute the Disconnect Subsystem or Disconnect Volume command for external
LUs that include LDEVs for which XP Auto LUN's migration processing is in progress.
•
When executing the Disconnect Subsystem or Disconnect Volume command, the displayed
information for Ex-Dev. Status in the Device list becomes Cache Destage. Even if there is no
data left in cache memory, the displayed status stays Cache Destage until the Disconnect
Subsystem or Disconnect Volume command processing is complete.
•
When the Disconnect Subsystem or Disconnect Volume command is executed and all data in
cache memory is written to the external LU, the displayed information for Ex-Dev. Status in
the Device list becomes Disconnect.
•
When using the mapped external LU from the mainframe OS, set the Missing Interrupt Handler
(MIH) timer to 45 seconds, which is the recommended value.
•
In the internal processing, the external LU's RAID level is handled as RAID-1 across the board.
A bar (–) appears on the XP Command View Advanced Edition Software or Remote Web
Console panes. The external LU's RAID level is reported as RAID-1 when information about
the external array is reported to higher-level devices (OS).
•
Table 3 (page 36) and Table 4 (page 37) show the recommended application level for the
mapped external LU according to the external LU's HDD type.
Table 3 When external LU's emulation type is OPEN
Application
HDD type
FC
SATA
Not Recommended
Not Recommended
OK
Not Recommended
OK
OK
Backup
OK
Recommended
Archive
OK
Recommended
Database
Online
Transaction
Processing
(OLTP)
File operation
from host
(both Read and
Write)
File operation
from host
(mainly Read)
36
Preparing for XP External Storage operations
Table 4 When external LU's emulation type is for mainframes
Application
HDD type
FC
SATA
Not Recommended
Not Recommended
Not Recommended
Not Recommended
Operation from
TPF
Not Supported
Not Supported
File operation
from host
OK
Not Recommended
OK
OK
Backup
OK
Recommended
Archive
OK
Recommended
Database
Online
Transaction
Processing
(OLTP)
System volumes
(Journal, Check
points)
(both Read and
Write)
File operation
from host
(mainly Read)
•
The external array's performance and status affect the mapped external LU's Read and Write
performance. If there is a heavy load on the external array, the Read and Write operation's
processing speed slows. In this case, I/Os from the mainframe host might have an MIH error.
•
If the host connected to the local array issues too many I/Os for the external array to process,
commands from the host might time out.
When the amount of I/Os from the host to the external LU exceeds the maximum amount of
I/Os the external array can accept, commands from the host to the local array might time out.
As you configure the system using external LUs, consider the external array's I/O capacity.
•
When executing commands in HP software products to the mapped external LU and, therefore,
too many I/Os are issued for the external array to process, commands might time out and
errors might occur.
When the amount of I/Os from the software products to the external LU exceeds the maximum
amount of I/Os the external array can accept, commands might time out and errors might
occur. As you configure the system using external LUs, consider the external array's I/O
capacity.
•
When using an external LU from the host, note the external LU's Path Blockade Watch time.
If the Path Blockade Watch time is longer than the host command's timeout period, commands
from the host might time out when the power supply is off or errors occur for the external array.
If host I/O is a significant concern, ensure that the external LU's Path Blockade Watch time is
the same as or shorter than the host command's time-out period.
Combining XP External Storage with other HP products
You can use HP software products to operate and manage the external LUs you set using XP External
Storage.
Combining XP External Storage with other HP products
37
The following sections provide configuration examples for specific HP software products:
•
Using external LUs for Auto LUN XP operations
•
Using external LUs for Continuous Access XP operations
•
Using external LUs for Continuous Access XP Journal operations
•
Using external LUs for Business Copy XP operations
•
Using external LUs for Snapshot XP operations
The following HP software products support the use of mapped external LUs. For operations and
notes about each software product, see the product's user guide.
•
•
•
•
XP LUN Configuration and Security Manager Software
◦
If you set an open-system emulation type when mapping the external LU, you must use
XP LUN Configuration and Security Manager Software to set the mapped LU's path.
◦
You cannot use the mapped external LU as a NAS system volume.
◦
You cannot use the mapped external LU as a NAS user volume.
Volume Manager
◦
If you set a mainframe-system emulation type when mapping the external LU, you must
format the mapped volume or perform the Write to Control Blocks operation using the
Custom Volume Size (CVS) function before putting the external LU into use. For instructions,
see the HP XP LUN Configuration and Security Manager user guide: HP XP12000 Disk
Array, HP XP10000 Disk Array, HP 200 Storage Virtualization System.
◦
If you use the CVS function to create LDEVs from an external XP LU, the created LDEVs'
attributes (IO Suppression mode and Cache Mode) are the same as the source external
LU's.
◦
You cannot combine the local array internal LDEV and external LU to form a LUSE volume.
◦
Do not combine LDEVs of multiple external LUs to create a LUSE volume. You can only
use LDEVs in the same external LU to set LUSE volumes.
◦
You cannot combine external LUs that have different IO Suppression modes to form a
LUSE volume.
◦
You cannot combine external LUs that have different Cache Mode settings to form a LUSE
volume.
XP Cache LUN
◦
You must set the IO Suppression mode to Disable to use the mapped external LU for XP
Cache LUN operations.
◦
You cannot specify XP Cache LUN's bind mode for an external LU that has Cache Mode
set to Disable.
◦
If you use the mapped external LU for an XP Cache LUN operation and set the bind mode,
the XP Cache LUN operation requires a cache that is twice the size of the user data.
XP Auto LUN Base Monitor
XP Auto LUN Base Monitor can be used to display the monitoring information for the external
LUs.
You need to set the IO Suppression mode to Disable to use the mapped external volume for
the XP Auto LUN Software operation.
For the configuration example of XP Auto LUN Software, see Using external LUs for Auto LUN
XP operations.
38
Preparing for XP External Storage operations
•
XP Continuous Access (Synchronous and Asynchronous)
You must set the IO Suppression mode to Disable to use the mapped external LU for XP
Continuous Access operations. For an XP Continuous Access configuration example, see Using
external LUs for Continuous Access XP operations.
•
Hitachi TrueCopy for z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for Hitachi
TrueCopy for z/OS operations.
When the write operation is executed to the XP Continuous Access M-VOL to which the external
volume is assigned, the cache mode is always enabled regardless of the enabled or disabled
setting. For further information on the cache mode, see External LU attributes set by mapping.
•
XP Continuous Access Journal
You must set the IO Suppression mode to Disable to use the mapped external LU for XP
Continuous Access Journal operations. For an XP Continuous Access Journal configuration
example, see Using external LUs for Continuous Access XP Journal operations.
•
Hitachi Universal Replicator for z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for Hitachi
Universal Replicator for z/OS operation.
•
XP Business Copy
You must set the IO Suppression mode to Disable to use the mapped external LU for XP Business
Copy operations. For an XP Business Copy configuration example, see Using external LUs for
Business Copy XP operations.
•
Hitachi ShadowImage for z/OS
You must set the IO Suppression mode to Disable to use the mapped external LU for Hitachi
ShadowImage for z/OS operations.
•
XP Snapshot
You must set the IO Suppression mode to Disable to use the mapped external LU for XP Snapshot
operations. For an XP Snapshot configuration example, see Using external LUs for Snapshot
XP operations.
•
Hitachi Parallel Access Volumes (HPAV)
You must set the IO Suppression mode to Disable to use the mapped external LU for Hitachi
Parallel Access Volumes (HPAV) operations.
•
Volume Security
You must set the IO Suppression mode to Disable to use the mapped external LU for Volume
Security operations.
•
Volume Retention Manager
You must set the IO Suppression mode to Disable to use the mapped external LU for Volume
Retention Manager operations.
•
Data Retention Utility
◦
You must set the IO Suppression mode to Disable to use the mapped external LU for Data
Retention Utility operations.
◦
If you previously mapped the external LU and set the VMA of Data Retention Utility in
that volume, the previous VMA setting is overwritten when you map the LU again. However,
if Data Retention Utility is not installed when you remap the LU, you cannot map the LU
with the VMA setting.
Combining XP External Storage with other HP products
39
•
SNMP
Information about the mapped external LU and external port is displayed.
•
Configuration File Loader
◦
You can set the path definition for external LUs (add, delete, or change paths).
◦
You can set the command devices on external LUs (add or delete the setting).
◦
CHIP mode, host group, and WWN settings for external ports are not supported. When
an external LU is mapped through that external port, the topology setting is not available.
NOTE: Some mainframe products might be marketed under different HP names and are not
supported at this time. Contact your HP account support representative for the latest support matrix.
Using external LUs for XP Auto LUN operations
Figure 14 (page 40) shows an example of using an external LU for XP Auto LUN operations. The
mapped external LU is set as the source volume, and the local array internal LDEV is set as the
target volume. Existing data in the external LU is (in effect) manually migrated to the internal LDEV
on the local array using XP Auto LUN. For more information, see the HP XP LUN Configuration
and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200
Storage Virtualization System.
Figure 14 Example of XP Auto LUN operations
1.
Use XP External Storage to map a volume in the external array to an internal LDEV of the local
array.
For this example, set the following attributes for the mapped LU:
•
Emulation type: OPEN-V
•
IO Suppression mode: Disable
For more information, see Mapping external LUs (Add LU).
CAUTION: To migrate existing data in the mapped external LU to a local array volume using
XP Auto LUN or XP Business Copy, as shown in Figure 14 (page 40), set the local array's
emulation type to OPEN-V when mapping the LU. Only OPEN-V emulation can be used to
read existing data in the external LU from the local array side.
To copy existing data in the mapped external LU using HP software products, such as XP
Continuous Access and XP Business Copy, the mapped external LU's emulation type must also
be OPEN-V.
40
Preparing for XP External Storage operations
2.
Prepare a local array internal LDEV with the same capacity as the mapped external LU. Use
Volume Manager to adjust the internal LDEV's capacity as required. For instructions, see the
HP XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP
XP10000 Disk Array, HP 200 Storage Virtualization System.
CAUTION:
3.
4.
The emulation type of the local array's prepared internal LDEV must be OPEN-V.
Set the mapped external LU as the source volume, and set the local array internal LDEV as
the target volume.
Use XP Auto LUN to manually migrate existing data in the mapped external LU to the local
array internal LDEV (without changing the associated LDEV/LU).
Using external LUs for XP Continuous Access operations
Figure 15 (page 41) shows an example of using an external LU for XP Continuous Access operations.
The mapped external LU is set as the XP Continuous Access pair's S-VOL, and the volume in the
local array that is connected as the MCU is set as the XP Continuous Access pair's P-VOL. For more
information about XP Continuous Access operations, see the HP XP Continuous Access user guide
for XP12000/XP10000 Disk Arrays and SVS 200.
Figure 15 Example of XP Continuous Access operations
1.
Use XP External Storage to map a volume in the external array to an internal LDEV of the local
XP Continuous Access RCU array.
CAUTION:
Set the IO Suppression mode to Disable.
Select the mapped volume's emulation type as required. If you select an open-system emulation
type (such as OPEN-V), go to step 2. If you select a mainframe-system emulation type (such
as 3390-3), go to step 3.
For more information, see Mapping external LUs (Add LU).
2.
If you set an open-system emulation type when mapping the volume, the mapped volume's
status automatically becomes Normal. However, the volume-formatting process is not
automatically executed. To optionally format the mapped volume, use the Custom Volume
Size (CVS) function. For instructions, see the HP XP LUN Configuration and Security Manager
Combining XP External Storage with other HP products
41
user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization
System.
Go to step 4.
3.
If you set a mainframe-system emulation type when mapping the volume, the mapped volume's
status becomes Blockade. To format the volume, use the CVS function. To restore the volume,
perform the Write to Control Blocks operation if you mapped a volume for which the data
area has already been zero-formatted on the external array side. For instructions, see the HP
XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000
Disk Array, HP 200 Storage Virtualization System.
Go to step 4.
4.
Set the XP Continuous Access pair's P-VOL and S-VOL.
Using external LUs for XP Continuous Access Journal operations
Figure 16 (page 42) shows an example of using the external LU for XP Continuous Access Journal
operations. The mapped external LU is set as the XP Continuous Access Journal pair's S-VOL, and
the volume in the local array that is connected as the MCU is set as the XP Continuous Access
Journal's P-VOL. For more information, see the HP XP Continuous Access user guide for
XP12000/XP10000 Disk Arrays and SVS 200.
Figure 16 Example of XP Continuous Access Journal operations
1.
Use XP External Storage to map the volume in the external array as an internal LDEV of the
local array, which is used as the RCU for XP Continuous Access Journal operations.
CAUTION:
Set the IO Suppression mode to Disable.
Select the mapped volume's emulation type as required. If you select an open-system emulation
type (such as OPEN-V), go to step 2. If you select a mainframe-system emulation type (such
as 3390-3), go to step 3.
For more information, see Mapping external LUs (Add LU).
42
Preparing for XP External Storage operations
2.
If you set an open-system emulation type when mapping the volume, the mapped volume's
status automatically becomes Normal. However, the volume-formatting process is not
automatically executed. To optionally format the mapped volume, use the Custom Volume
Size (CVS) function. For instructions, see the HP XP LUN Configuration and Security Manager
user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization
System.
Go to step 4.
3.
If you set a mainframe-system emulation type when mapping the volume, the mapped volume's
status becomes Blockade. To format the volume, use the CVS function. To restore the volume,
use the Write to Control Blocks operation if you mapped the volume for which the data area
has already been zero-formatted on the external array side. For instructions, see the HP XP
LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000
Disk Array, HP 200 Storage Virtualization System.
Go to step 4.
4.
Set the XP Continuous Access Journal pair's P-VOL and S-VOL.
Using external LUs for XP Business Copy operations
Figure 17 (page 43) shows an example of using an external LU for XP Business Copy operations.
The mapped external LU is set as the XP Business Copy pair's S-VOL, and the local array internal
LDEV is set as the XP Business Copy pair's P-VOL. For more information, see the HP XP Business
Copy user guide for XP12000/XP10000 Disk Arrays and SVS 200.
Figure 17 Example of XP Business Copy operations
1.
Use XP External Storage to map a volume in the external array to an internal LDEV of the local
array.
CAUTION:
Set the IO Suppression mode to Disable.
Select the mapped volume's emulation type as required. If you select an open-system emulation
type (such as OPEN-V), go to step 2. If you select a mainframe-system emulation type (such
as 3390-3), go to step 3.
For more information, see Mapping external LUs (Add LU).
2.
If you set an open-system emulation type when mapping the volume, the mapped volume's
status automatically becomes Normal. However, the volume-formatting process is not
automatically executed. To optionally format the mapped volume, use the Custom Volume
Size (CVS) function. For instructions, see the HP XP LUN Configuration and Security Manager
Combining XP External Storage with other HP products
43
user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization
Systemr.
Go to step 4.
3.
If you set a mainframe-system emulation type when mapping the volume, the mapped volume's
status becomes Blockade. To format the volume, use the CVS function. To restore the volume,
perform the Write to Control Blocks operation if you mapped a volume for which the data
area has already been zero-formatted on the external array side. For instructions, see the HP
XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000
Disk Array, HP 200 Storage Virtualization System.
Go to step 4.
4.
Set the XP Business Copy pair's P-VOL and S-VOL.
Using external LUs for XP Snapshot Software operations
Figure 18 (page 44) shows an example of using an external LU for XP Snapshot operations. The
mapped external LU is set as a pool-VOL for the XP Snapshot pair.
For more information about XP Snapshot, see the HP Snapshot XP user guide for XP12000/XP10000
Disk Arrays and SVS 200.
Figure 18 Example of XP Snapshot operations
1.
Use XP External Storage to map a volume in the external array to an internal LDEV of the local
array.
CAUTION: You must set the volume's emulation type to OPEN-V when mapping the volume.
You can set only a volume with the OPEN-V emulation type as an XP Snapshot pool-VOL. Set
the IO Suppression mode to Disable.
For more information, see Mapping external LUs (Add LU).
2.
3.
44
The mapped volume's status automatically becomes Normal. However, the volume formatting
processing does not execute automatically. To format the mapped volume, format the volume
using the CVS function. For instructions, see the HP XP LUN Configuration and Security Manager
user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization
System.
Create a pool, and add the mapped external LU to that pool as a pool-VOL.
Preparing for XP External Storage operations
4.
Set the XP Snapshot pair's P-VOL and S-VOL specifying the pool you created in step 3.
Combining XP External Storage with other HP products
45
3 Managing cache with external storage
XP disk arrays and storage virtualization systems use cache to facilitate host and internal I/O.
When cache mode is enabled, host I/O is accepted as quickly as it is received into the array's
cache where the associated read or write is buffered. When cache mode is disabled, the array
limits caching to one block of read and write data per LDEV. Cache is also used by Data Mirroring
and Data Migration products that generate internal I/O to copy and move data between devices,
such as:
•
XP Business Copy
•
XP Continuous Access software products
•
XP Business Copy's Snapshot feature
•
XP Auto LUN
•
XP Tiered Storage Manager
Having cache mode enabled for external storage devices that are slower than the XP array can
provide a performance benefit for some very specific and well-defined workloads, such as
single-threaded sequential access to a device. HP strongly recommends that you configure all
external storage devices with cache mode disabled unless you have determined that you meet
these exact workload descriptions. When you deviate from these workload descriptions, performance
might not be as good as when cache is disabled. Consult your HP account support representative
to discuss the availability of tuning services for your XP array.
This chapter explains how to balance cache usage between internal and external storage and
protect the potential benefits of using cache.
Guidelines for using cache with external storage
•
Disable cache for external devices.
◦
Always disable cache mode for external LUs in an MSA or other storage array that is
slower than the XP or SVS200 external ports.
◦
Always disable cache mode for external LUs that are used by XP data replication or data
migration software (for example, P-VOLs, S-VOLs, pool volumes, and XP Auto LUN or XP
Tiered Storage Manager target volumes).
See Determining, setting, or changing the external LU cache mode.
•
Partition cache for external storage.
◦
Always put external volumes and internal XP volumes in separate cache partitions (CLPRs).
◦
Always partition external storage LUNs that are targets for XP data replication or migration
software (XP Business Copy, XP Continuous Access software products, XP Snapshot, XP
Auto LUN, or XP Tiered Storage Manager).
◦
Partition any external LUs that have cache enabled. External LUNs with cache enabled
can use large amounts of cache.
See Partitioning cache for external storage.
•
46
Consult HP account support representative to verify or change storage system modes. See
Changing storage system modes.
Managing cache with external storage
Determining, setting, or changing the external LU cache mode
You set the cache mode when you define external LUs. HP strongly recommends that you set cache
mode to Disabled for external LUs. For instructions on mapping external LUs in a new configuration,
see Mapping external LUs (Add LU).
CAUTION: Before you delete any LUs that you want to remap, carefully record necessary
configuration information. If you remap existing LUs with changed configuration settings (other
than cache mode), you can lose access to the LUs and the data they contain.
Determining if the cache mode is disabled
If you have an existing configuration and need to determine if your external LUs are configured
with cache mode disabled, follow this procedure:
1. In the Remote Web Console main pane, click the External Storage button in the left pane. The
LU Operation pane appears.
2. In the Device tree, select an external device group.
3. In the Device list, check the Cache Mode setting (Figure 19 (page 47)). If cache mode is
enabled, you should change it to Disabled.
Figure 19 LU Operation pane, Cache Mode setting
Changing the cache mode
If you need to change the cache mode for existing external LUs, you must delete and remap the
external LU path and definition.
CAUTION: Before you delete any LUs that you want to remap, carefully record necessary
configuration information. If you remap existing LUs with changed configuration settings (other
than cache mode), you can lose access to the LUs and the data they contain.
Determining, setting, or changing the external LU cache mode
47
Collecting device information
Before you remap an external storage device, collect the following information for each device:
•
LU number in the group
•
Universal Unique ID (UUID)
•
Path settings
•
CVS settings
•
Mapped location
•
External group number
•
CU:LDEV identifier
To collect each of these items:
1. In the Remote Web Console main pane, click the External Storage button in the left pane. The
LU Operation pane appears.
2. To find the LU number and UUID, select an external device group in the Device tree
(Figure 20 (page 48)).
The LU number appears in the LUN column in the Device list.
The UUID appears in the Characteristic2 column in the Device list.
Figure 20 LU Operation pane, LU number and UUID
3.
48
To find the path settings, right-click the external LDEV in the Device list, and select Path Setting
(Figure 21 (page 49)).
Managing cache with external storage
Figure 21 LU Operation pane, Path Setting option
Determining, setting, or changing the external LU cache mode
49
The Path Setting pane appears (Figure 22 (page 50)).
Figure 22 Path Setting pane
4.
To find the CVS settings, mapped location, external group number, and CU:LDEV identifier,
right-click the LDEV in the Device list on the LU Operation pane, and select LDEV Information
(Figure 21 (page 49)). The LDEV Information pane appears (Figure 23 (page 50)).
Figure 23 LDEV Information pane
50
Managing cache with external storage
Deleting and remapping the external LU
You must delete and remap each LU that needs the cache setting changed. Using the information
recorded in Collecting device information, delete and remap each LDEV.
1. On the LU Operation pane, select the appropriate external LU group number in the Device
tree.
2. In the Device list, right-click the external LU that you want to delete, and select Delete LU
(Figure 21 (page 49)).
3. Click Apply.
4. Click either Yes or No. If you click Yes, skip the next step.
5. Click OK in response to the warning message.
6. Click OK.
7. Remap the LU using all the previous settings except for the cache mode setting, which is
disabled. See Mapping external LUs (Add LU).
NOTE: When scanning for devices to add, the order in which devices are discovered might
be different. The UUID is always the same for the same external device. Ensure that the UUID
of the device being remapped matches the UUID that was deleted for the same LU number.
8.
Recheck to ensure that the same external storage LUs (identified by UUIDs) are now assigned
their original settings and the desired cache mode. If not, delete and remap the external LU
again.
Partitioning cache for external storage
Separate cache partitions isolate the applications that are using XP arrays and storage virtualization
systems from the I/O dampening effects of a cache that is filling up with host and internal I/O for
slower external targets. HP requires separate cache partitions (CLPRs) for:
•
External volumes and internal XP volumes, except for configurations where all external storage
LUNs have cache disabled and do not have any external storage devices using data mirroring
or migration products
NOTE: All HP 200 Storage Virtualization System volumes are external. Partition SVS200
cache according to the other recommendations made in this section.
•
External volumes that are used by XP data replication or data migration products, including
XP Business Copy, XP Continuous Access software products, XP Snapshot, XP Auto LUN, and
XP Tiered Storage Manager
•
SVS200 source volumes and data copy or target volumes that have slower throughput
For example, Company A uses:
•
XP10000 internal disks for database applications
•
EVA3000 for backup applications
Cache can be partitioned for Company A as follows:
•
CLPR0: XP10000 for XP Business Copy P-VOL
•
CLPR1: EVA3000 for XP Business Copy S-VOL (external LU cache is disabled)
In another example, Company B uses the following storage tiers:
•
Tier 1 is an XP12000 (6 TB of internal space) for P-VOLs
•
Tier 2 is an EVA (20 TB) for P-VOLs and XP Business Copy S-VOLs
•
Tier 3 is two MSA 1500 (10 TB) for the XP Business Copy S-VOLs
Partitioning cache for external storage
51
Cache can be partitioned for Company B as follows:
•
CLPR0: 12 GB for the internal XP12000 P-VOL
•
CLPR1: 4 GB for the EVA S-VOL and P-VOL
•
CLPR2: 4 GB for the MSA S-VOL
•
All external LU cache is disabled
To partition cache for external storage:
1. Determine the number and size of the partitions you need (see Determining the number and
size of needed partitions).
2. Create the partitions (see Creating cache partitions).
Determining the number and size of needed partitions
The minimum cache partition (CLPR) size is 4 GB. Determine the size you need for each CLPR being
used for external storage based on the total capacity of the assigned external volumes.
Table 5 (page 52) shows the recommended cache sizes for external storage CLPRs on open systems.
Table 6 (page 52) shows the same information for HP storage virtualization systems.
Table 5 Recommended individual CLPR cache size for external storage on open systems
External storage volume capacity assigned to CLPR
Recommended cache size for CLPR
Less than 128,000 GB
4 GB
128,000 GB or more
8 GB
Table 6 Recommended individual CLPR cache size for external storage on HP storage virtual systems
External volume
capacity assigned to
CLPR
CLPR0
Additional CLPRs
Less than 1 TB
4 GB
4 GB
1 TB <= capacity <
16TB
8 GB
4 GB
16 TB <= capacity <
20 TB
12 GB
4 GB
20 TB <= capacity < 16 GB
128 TB
4 GB
128 TB or more
8 GB
24 GB
Creating cache partitions
Ensure the XP Disk/Cache Partition license is installed, you have Administrator authority on the
array, and you are in Modify mode in Remote Web Console. For more information about license
keys and user administration procedures, see the HP XP Remote Web Console user guide for
XP12000/XP10000 Disk Arrays and SVS 200.
1. In Remote Web Console, click the Install button in the left pane.
2. Click the Partition Definition tab.
3. In the Cache Logical Partition tree, right-click SLPR0 (if you have additional storage partitions
configured, click the storage partition you want the CLPR to be created in), and select Create
CLPR. The new CLPR is added to the tree.
4. Select the new CLPR in the tree, and change the size and other CLPR settings as needed
(Figure 24 (page 53)).
52
Managing cache with external storage
Figure 24 Partition Definition pane
5.
6.
Click Apply for the changes to becomes effective.
Repeat step 3 through step 5 to define any additional CLPRs that you need.
Creating cache partitions
53
7.
To allocate external storage groups to a CLPR:
a. Double-click the SLPR.
b. Select the CLPR that you want to assign the external storage groups from (this will be
CLPR0 if this is the first time you are configuring partitioning).
c. Select and right-click the external storage groups that you want to assign to another CLPR,
and then select Cut (Figure 25 (page 54)).
Figure 25 Partition Definition pane, Cut option
d.
Right-click the CLPR that you want to assign the selected external storage groups to, and
then select Paste Parity Group (Figure 26 (page 54)). The selected external storage groups
are added to the CLPR resource list.
Figure 26 Partition Definition pane, Paste Parity Group option
54
Managing cache with external storage
e.
f.
Click Apply.
Repeat step 7b through step 7e until you have allocated the external storage groups to
the appropriate CLPRs according to the plan you created after reading Partitioning cache
for external storage.
For complete information about creating SLPRs and CLPRs, see the HP XP Disk/Cache Partition
user guide for XP12000/XP10000 Disk Arrays and SVS 200.
Changing storage system modes
In addition to cache partitioning and cache modes, array system modes control LU cache usage.
HP service representatives can set the XP and SVS200 array system modes to adjust the array's
behavior.
For SVS200 arrays, no adjustments are needed.
For XP arrays, contact your HP account support representative to change the system modes if either
of the following is true:
•
Your external LUs are used by XP or SVS200 data mirroring and data migration products
such as XP Business Copy, XP Snapshot, XP Auto LUN, or XP Tiered Storage Manager.
•
You need cache enabled for external LUs.
Changing storage system modes
55
4 XP External Storage panes
XP External Storage operations involve the LU Operation and Port Operation panes. In addition
to these two panes, the Flex Copy pane is available if you licensed XP Flex Copy. When you select
a tab, the corresponding pane appears.
Figure 27 Panes for XP External Storage operations
LU Operation pane
This pane appears when you start XP External Storage. Information about the external array appears
on the LU Operation pane. Use this pane to perform operations such as mapping external LUs and
setting alternate paths.
56
XP External Storage panes
Figure 28 LU Operation pane
•
Device, WWN, and Port trees
Displays information in the Device, WWN, or Port list depending on the item selected in the
tree. Select the tab to display a tree. The following items can be selected in each tree:
•
◦
Items you can select in the Device tree include Subsystem (local XP), External Devices
(arrays), product names of connected external arrays, external LU group numbers,
Discovery, and external array WWNs. For more information, see Device tree.
◦
Items you can select in the WWN tree include Subsystem, External Devices, product names
of connected external arrays, and external array WWNs. For more information, see
WWN tree.
◦
Items you can select in the Port tree include Subsystem, External Devices, product names
of connected external arrays, and port numbers set to external ports. For more information,
see Port tree.
Filter button
Displays the Filter window, where you can restrict items displayed in the Device, WWN, and
Port lists. For more information, see Filter button.
•
Device, WWN, and Port lists
Displays information about the external array corresponding to the item selected in the Device,
WWN, or Port tree.
You can sort the list by displayed items. For example, to sort the list by LUN numbers, select
LUN on the list. For more information, see Device list, WWN list, and Port list.
LU Operation pane
57
•
Information area
Displays information about the contents of the Device, WWN, or Port list, including:
◦
Total number of Devices: Number of external LUs that are connected.
◦
Total number of External Groups: Number of external LU groups that are set.
◦
Total number of External LUs: Number of external LUs that are connected.
◦
Found WWNs: WWNs found when you clicked Discovery in the Device tree.
◦
Remain LUs: Number of external LU numbers available (out of 15,360), other than those
that have already been used.
◦
WWN Entry: Number of LUs that are currently used in the external array out of the
maximum theoretically possible (15,360).
Displayed in the format The number of connected ports/16,384 (the number of ports
which can be connected).
•
◦
Total number of WWNs: Number of external array ports that are connected.
◦
Total number of Paths: Number of paths set between the local array and external array.
Preset list
Displays the contents of settings that were set by operations started on the LU Operation pane.
Contents displayed in the Preset list have not yet been applied to the local array. They are
applied when you click Apply. For more information, see Preset list (LU Operation pane).
•
Operation information area
Displays operation information about settings in the Preset list, including:
•
◦
Operation: Setting operation name.
◦
Number of Objects in Preset: Number of rows displayed in the Preset list.
Apply button
Applies pending operations in the Preset list to the local array. When operations are applied
successfully, they are removed from the Preset list. Otherwise, error messages appear and
error settings remain in the Preset list.
•
Cancel button
Cancels all settings in the Preset list.
Device tree
To display the Device tree, select the Device tab. The Device tree displays information on the external
array that is connected to the external port. The contents displayed in the Device list (upper right
of the panel) change depending on the items selected in the Device tree.
58
XP External Storage panes
Figure 29 Device tree
The Device list (right pane) changes according to the item selected in the Device tree.
•
Subsystem
When selected, displays nothing in the Device list and displays the External Devices branch
of the tree. Subsystem is selected when you start XP External Storage and display the Device
tree.
•
External Devices
When selected, the Device list displays information about external arrays connected to external
ports that have been detected (supported).
NOTE:
•
Not all types of detected external arrays are supported.
Product name of the connected external array
Displays the name of the external array that can be connected using XP External Storage in
the tree under External Devices. When you select an external array's product name, the Device
list displays detailed product information.
•
External LU group number
Displays user-assigned numbers in the branch under the external array's product name, which
is connected to the local array and is already used. When you select an external LU group
number, the Device list displays information about external LUs registered in the selected group.
•
Discovery
Appears in the branch under the product name of the external array connected to the local
array. When selected, XP External Storage searches for external array ports that can be
connected, and displays their WWNs.
•
WWN of the external array
If you select the WWN found by selecting Discovery in the Device tree, the Device list displays
information about external LUs that can be connected from the port indicated by the WWN.
Device list
Displays information about external arrays corresponding to the item selected in the Device tree.
You can sort the list by displayed items. For example, to sort by LUN numbers, click LUN in the
list.
When performing setting operations, the settings appear in the Preset list and the corresponding
row in the Device list appears in blue italics. For more information, see Preset list (LU Operation
pane).
LU Operation pane
59
Figure 30 Device list (external device selected in Device tree)
Following items are displayed in the Device list. The displayed contents differ depending on the
items selected in the Device tree. The items displayed in the Device list are described below on
each item selected in the Device tree.
•
Subsystem
Displays nothing. Subsystem is automatically selected when you select the Device tree.
•
External Devices (for example, external storage group numbers currently defined for that
external device)
◦
Serial: Product serial number.
◦
Product: Product name.
◦
Vendor: Vendor name.
◦
Ex-Dev. Status: Status of the operation executed to the external array, or status of path
connection. External array's status. Possible values: Normal, Unknown, Blockade, Warning,
Checking, Cache Destage, and Disconnect.
Table 7 External array status values
◦
60
LU status
Description
Normal
LU status is normal.
Unknown
LU status has yet to be ascertained.
Blockade
I/O traffic to the LU is not permitted.
Warning
FC path or paths have an abnormal status. Check the status of the paths.
Checking
XP External Storage is verifying configuration information defined for FC paths.
Cache Destage
XP External Storage is writing all data in the local array cache memory to the LU.
Disconnect
Connection to external array or external LU was intentionally stopped using the Disconnect
Subsystem or Disconnect Volume command.
LDEV Status: Mapped external LU's status. Possible values: Normal, Unknown, Blockade,
Warning, and Format.
XP External Storage panes
Table 8 Mapped external LU status values
•
•
LDEV status
Description
Normal
LDEV status is
normal.
Unknown
LDEV status has
yet to be
ascertained.
Blockade
I/O traffic to the
LDEV is not
permitted.
Warning
External LUs
have abnormal
status.
Format
Volume is in the
process of being
formatted.
Product name of the connected external array
◦
ExG: External LU group number. This appears when you group the LUs from one or more
external arrays under a common number.
◦
Serial: Product serial number.
◦
Product: Product name.
◦
Vendor: Vendor name.
◦
Ex-Dev. Status: Status of the operation executed on the external array, or status of the
path connection. Possible values: Normal, Unknown, Blockade, Warning, Checking,
Cache Destage, and Disconnect. For a description of these values, see Table 7 (page 60).
◦
LDEV Status: Mapped external LU's status. Possible values: Normal, Unknown, Blockade,
Warning, and Format. For a description of these values, see Table 8 (page 61).
External LU group number
◦
Characteristic: External LU's identification number.
◦
Device: External LU's device name.
◦
Capacity: External LU's capacity in 512-byte blocks.
◦
Ex-Dev. info.: External array information. When the external array is an XP1024/XP128
or TagmaStore Workgroup Modular Storage (WMS) array, an asterisk (*) appears.
◦
VMA: Information about the VMA setting by XP LUN Security Extension. When VMA is
set for the volume, an asterisk (*) appears.
◦
Alter. Path: Number of configured paths in the format The number of valid paths (the
number of primary alternate paths).
◦
IO Suppression: I/O Suppression mode: Enable or Disable. For more information, see
External LU attributes set by mapping.
◦
Cache Mode: Cache mode: Enable or Disable. For more information, see External LU
attributes set by mapping.
◦
Path: When paths are set, an asterisk (*) appears.
◦
Group: External LU group number and reference number assigned to each LU in the
external LU group. XP External Storage automatically assigns reference numbers to LUs
in the group when external LUs are mapped. This appears in the format “external LU
group number - reference number of the LU in the group”.
LU Operation pane
61
•
•
◦
Ex-Dev. Status: Status of the operation executed to the external array, or status of the
path connection. Possible values: Normal, Unknown, Blockade, Warning, Checking,
Cache Destage, and Disconnect. For a description of these values, see Table 7 (page 60).
◦
LDEV Status: Mapped external LU's status. Possible values: Normal, Unknown, Blockade,
Warning, and Format. For a description of these values, see Table 8 (page 61).
◦
Progress: When Status is Cache Destage, displays the write process progress, from 1%
to 100%.
◦
Characteristic2: External LU's extended identifying information. This information is used
for identifying logical volumes in the EVA array. For more information, see Identifying
logical volumes of EVA arrays (using Characteristic 2).
Discovery
◦
WWN: World Wide Name identifying the port in the external array that can be set.
◦
Serial: Product serial number.
◦
Product: Product name.
◦
Vendor: Vendor name.
WWN of the external array
◦
LUN: LU number in the external array.
◦
Characteristic: External LU's ID number.
◦
Device: External LU's device name.
◦
Ex-Dev. info.: Information about the external array. When the external array is an
SATA/FATA drive, an asterisk (*) appears.
◦
VMA: Information about the VMA setting by XP LUN Security Extension. When VMA is
set for the volume, an asterisk (*) appears.
◦
Capacity: External LU's capacity in blocks.
◦
Characteristic2: External LU's extended identifying information. This information is used
for identifying logical volumes in the EVA array. For more information, see Identifying
logical volumes of EVA arrays (using Characteristic 2).
WWN tree
To display the WWN tree, select the WWN tab. The information already set in the status that the
Device tree is selected is displayed. The contents displayed in the WWN list (upper right of the
panel) change corresponding to the items selected in the WWN tree.
62
XP External Storage panes
Figure 31 WWN tree
•
Subsystem
When selected, displays nothing in the WWN tree. Subsystem is selected when you initially
display the WWN tree.
•
External Devices
When selected, displays information about the external array connected to the external port
in the WWN list.
•
Product name of the connected external array
When selected, displays the name of the external array for which the connection setting is
already completed in the tree under External Devices.
•
WWN of the external array
When selected, displays WWNs identifying ports on the connected external array in the tree
under the name of the external array product.
WWN list
Displays information about the connection status of the local array and external array corresponding
to the item selected in the WWN tree. You can sort the list by displayed items. For example, to sort
by the LUN number, select LUN on the list.
When performing setting operations, the settings appear in the Preset list and the corresponding
row in the WWN list appears in blue italics. For more information, see Preset list (LU Operation
pane).
Figure 32 WWN list (External Devices selected in the WWN tree)
LU Operation pane
63
Following items are displayed in the WWN list. The displayed contents differ depending on the
items selected in the WWN tree. The items displayed in the WWN list are described below on
each item selected in the WWN tree.
•
Subsystem
When selected, displays nothing in the WWN tree. Subsystem is selected when you initially
display the WWN tree.
•
•
External Devices
◦
Serial: Product serial number.
◦
Product: Product name.
◦
Vendor: Vendor name.
◦
Ex-Dev. Status: Status of the operation executed to the external array, or status of the
path connection. Possible values: Normal, Unknown, Blockade, Warning, Checking,
Cache Destage, or Disconnect. For a description of these values, see Table 7 (page 60).
◦
LDEV Status: Mapped external LU's status. Possible values: Normal, Unknown, Blockade,
Warning, or Format. For a description of these values, see Table 8 (page 61).
Product name of the connected external array
◦
WWN: WWN identifying the port in the external array for which the connection setting
is completed.
◦
Path: Number of set paths.
◦
I/O TOV: Value specified as the timeout for I/O to the external LU.
◦
Qdepth: Number of Read/Write commands that can be issued (queued) to the external
LU at one time.
◦
Path Watch: Time period beginning when the connection of all paths to the external LU
are down and ending when the external LU is blocked.
◦
Mode: How alternate paths between the local array and external array work. Alternate
path modes include:
◦
64
–
Single: Uses only the path with the highest priority (primary path) to execute I/O to
the external LU. When an error occurs in the primary path, the path with the second
highest priority is used.
–
Multi: Uses all set paths at the same time to execute I/Os to the external LU,
distributing the work load.
Status: Status of the path set in the port identified by the WWN. The highest emergency
level status appears when two or more paths are set. Statuses include:
–
Normal: Path is normal.
–
Unknown: Path status is unknown.
–
Blockade: Path is blocked.
–
Disconnect: Connection to the external array or external LU was intentionally stopped
using the Disconnect Subsystem or Disconnect Volume command.
XP External Storage panes
•
–
Warning: There are paths whose status is not normal. Check the status of the paths.
–
Checking: Process of checking the paths' defined configuration informations is in
progress.
WWN of the external array
◦
Port: Port number of the local array connected to the port identified by the WWN selected
in the Port tree. One of the following icons appears for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
◦
WWN: WWN of the external array selected in the Port tree.
◦
LUN: External array's LU number.
◦
Characteristic: External LU's identification number.
◦
Group: External LU group number and reference number assigned to each LU in the
external LU group. XP External Storage automatically assigns reference numbers to LUs
in the group when the external LUs are mapped. This is displayed in the format of “external
LU group number - reference number of volume in the group”.
◦
Status: Status of the path configured by the port of the local array and the port of the
external array identified by the WWN. One of the following statuses is displayed:
–
Normal: Path is normal.
–
Unknown: Path status is unknown.
–
Blockade: Path is blocked.
–
External device setting changed: External array setting changed. For example, the
path definition was deleted, or the external array itself was replaced by another
device.
–
LDEV size reduced: External array's volume capacity setting changed (volume capacity
was reduced).
–
Not ready: External array replied NOTREADY.
–
Illegal request: External array replied ILLEGALREQUEST.
–
Command aborted: External array replied ABORTEDCOMMAND.
–
Busy: External array is in BUSY status.
–
LDEV reserved: External array is in Reserve status.
–
Response error: External array is in blocked status caused by an abnormal reply
(Response).
–
Initiator port: External array's port attribute changed to the initiator port.
–
Unknown port: External array's port attribute is unknown.
–
Cannot detect port: Path was removed or external array's port could not be found.
–
Internal error: Program error occurred, or there is a logical contradiction.
–
Timeout: Processing was retried because an abnormal reply (Response) was returned;
however, processing was stopped by a timeout.
LU Operation pane
65
◦
–
Standby: The port of the external subsystem is standing by. The port status is normal
but cannot receive I/O.
–
Target error: Port failures, such as controller blockade are detected on the external
subsystem side.
–
Checking: Process of checking the paths' defined configuration information is in
progress.
–
Disconnect: Connection to the external array or external LU was intentionally stopped
using the Disconnect Subsystem or Disconnect Volume command.
–
Unavailable: External array replied Unavailable. The external array demands to
change the connected port. Once the status becomes Unavailable, the primary path
changes to the alternate path that is in the Standby status. When the primary path
changes, the status of the path becomes Normal.
–
Backoff: External array replied Backoff. The path status is waiting for recovery because
a temporary error occurred in the external array's LU. Even if the primary path's
status becomes Backoff, the primary path does not immediately change to the alternate
path. After the error recovery, the status becomes Normal. If the status cannot be
recovered from the error, the path status changes to the other status.
–
Device check error: The target volume in the external subsystem is not accessible,
even though the external volume was mapped.
–
Medium error: The target volume in the external subsystem has become inaccessible.
Characteristic2: External LU's extended identifying information. This information is used
for identifying logical volumes in the EVA array. For more information, see Identifying
logical volumes of EVA arrays (using Characteristic 2).
Port tree
To display the Port tree, select the Port tab. When you select the Port tab, this tree displays
information about ports that have the External attribute. The contents displayed in the Port list
changes depending on the item selected in the Port tree. For instructions on setting the port attribute,
see Setting a local array's port attributes.
Figure 33 Port tree
66
XP External Storage panes
The items displayed in the Port tree and the contents displayed in the Port list when you select each
item are as follows.
•
Subsystem
When selected, displays nothing in the Port list. Subsystem is selected when you initially
display the Port tree.
•
External
When selected, displays information about the port whose port attribute is set to External in
the Port list.
•
Local array port number
When selected, displays connection information about the selected port in the Port list. One
of the following icons appears on the left of each port number:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
Port list
Displays information about the ports and paths of the local array or external array, depending on
the item selected in the Port tree. You can sort the list by displayed items. For instance, to sort the
items by the port number, select Port on the list.
Figure 34 Port list (External selected in Port tree)
LU Operation pane
67
The displayed contents changes depending on the item selected in the Port tree.
•
Subsystem
When selected, displays nothing in the Port tree. Subsystem is selected when you initially
display the Port tree.
•
External
◦
Port: Port of the local array with the port attribute is set to External. One of the following
icons appears for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
•
◦
Path: Number of set paths.
◦
FLI_TOV: Wait time (in seconds) from the switch to FLOGI when the switch is connected.
XP External Storage automatically sets this value. You cannot change the value.
◦
PLI_TOV: Wait time (in seconds) of PLOGI to the external array when the switch is not
connected. XP External Storage automatically sets this value. You cannot change the
value.
◦
Margin: Additional wait time (in seconds) to FLI_TOV (FLOGI wait time) or PLI_TOV (PLOGI
wait time). XP External Storage automatically sets this value. You cannot change the value.
As a result, the sum of the FLI_TOV time and margin time, or the sum of the PLI_TOV time
and margin time is set as a total wait time.
◦
Status: Status of the path set in the port identified by the WWN. The highest emergency
level status is displayed when two or more paths are set. One of the following statuses
is displayed:
–
Normal: Path is normal.
–
Unknown: Path status is unknown.
–
Blockade: Path is blocked.
–
Disconnect: Connection to the external array or external LU was intentionally stopped
using the Disconnect Subsystem or Disconnect Volume command.
–
Warning: There are paths whose status is not normal. Check the status of the paths.
–
Checking: Process of checking the defined configuration information for the paths is
in progress.
Port number of the local array
◦
Port: Port number of the local array selected in the Port tree. One of the following icons
appears for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
68
XP External Storage panes
◦
WWN: WWN identifying the external array's port. This port is connected to the local
array port selected in the Port tree.
◦
LUN: External array's LU number.
◦
Characteristic: External LU's identification number.
◦
Group: External LU group number and reference number assigned to each LU in the
external LU group. XP External Storage automatically assigns the reference numbers to
LUs in the group when the external LUs are mapped. This is displayed in the format of
“external LU group number - reference number of volume in the group”.
Status: Status of the path configured by the port of the local array and the port of the
external array identified by the WWN.
◦
–
Normal: Path is normal.
–
Unknown: Path status is unknown.
–
Blockade: Path is blocked.
–
External device setting changed: External array's setting changed. For example, the
path definition was deleted or the external array itself was replaced by another
device.
–
LDEV size reduced: External array's volume capacity changed (volume capacity was
reduced).
–
Not ready: External array replied NOTREADY.
–
Illegal request: External array replied ILLEGALREQUEST.
–
Command aborted: External array replied ABORTEDCOMMAND.
–
Busy: External array is in BUSY status.
–
LDEV reserved: External array is in Reserve status.
–
Response error: External array is in blocked status caused by an abnormal reply
(Response).
–
Initiator port: External array's port attribute changed to the initiator port.
–
Unknown port: External array's port attribute is unknown.
–
Cannot detect port: Path was removed or external array's port could not be found.
–
Internal error: Program error occurred, or there is a logical contradiction.
–
Timeout: Processing was retried because an abnormal reply (Response) was returned;
however, processing was stopped by a timeout.
–
Standby: External array's port is standing by. The port status is normal, but cannot
receive I/O.
–
Target error: Port failures, such as controller blockade, are detected on the external
array side.
–
Checking: Process of checking the paths' defined configuration information is in
progress.
–
Disconnect: Connection to the external array or external LU was intentionally stopped
using the Disconnect Subsystem or Disconnect Volume command.
–
Unavailable: External array replied Unavailable. The external array demands to
change the connected port. Once the status becomes Unavailable, the primary path
changes to the alternate path that is in the Standby status. When the primary path
changes, the status of the path becomes Normal.
–
Backoff: External array replied Backoff. The path status is waiting for recovery because
a temporary error occurred in the external array's volume. Even if the primary path's
LU Operation pane
69
status becomes Backoff, the primary path does not changed to the alternate path
immediately. After the error recovery, the status becomes Normal. If the status cannot
be recovered from the error, the path status changes to the other status.
◦
Characteristic2: External LU's extended identifying information. This information is used
for identifying logical volumes in the EVA array. For more information, see Identifying
logical volumes of EVA arrays (using Characteristic 2).
Filter button
Displays the Filter window where you can restrict LUs displayed in the Device list.
Figure 35 Filter window
This window contains Enable and Disable options that control the display of unsupported devices.
When you select Enable, information about unsupported arrays appears in the Device tree and
Device list. Unsupported arrays are indicated by Unknown Devices in the Device tree and Device
list.
The Disable option is selected by default.
Preset list (LU Operation pane)
Displays rows from the Device list that are about to be acted upon. You can apply settings to the
local array after checking the contents in the Preset list. Information displayed in the Preset list
appears in blue italics in the Device list. If you click Apply in the LU Operation pane, settings
displayed in the Preset list are applied to the local array. At that point, the contents of the Preset
list disappear and the Device list appears normally.
If you click Cancel in the LU Operation pane, all settings in the Preset list are canceled.
If settings in the Preset list contain errors, they are not applied to the local array even if you click
Apply. In that case, error messages appear and incorrect settings appear in the Preset list. In
addition, error codes appear in the Preset list.
NOTE: Depending on the type of errors that occur, identical error codes might be displayed for
all errors listed in the Preset list. In this case, check the status of settings to identify the source of
the error.
When you right-click an item in the Preset list, the following commands appear:
•
Detail
Displays the Preset Detail window with detailed information about settings selected in the
Preset list. When an error code appears in the Preset list, a corresponding error message
appears in this window.
70
XP External Storage panes
Figure 36 Preset Detail window (mapping operation)
•
Delete
Cancels settings selected in the Preset list.
Port Operation pane
Use this pane to check port settings and set port attributes. This section describes items displayed
in the Port Operation pane. For instructions, see Setting a local array's port attributes.
Figure 37 Port Operation pane
•
Port Operation tree
Displays information about the selected port in the Port list (right pane). You can select
Subsystem, a port attribute, or a port number. For more information, see Port Operation tree.
•
Port Operation list
Displays detailed information about ports selected in the Port Operation tree. For more
information, see Port Operation list.
Port Operation pane
71
•
Information area
Displays the total number of ports currently displayed in the Port Operation list (Total Number
of Ports).
•
Preset list
Displays rows corresponding to the ports that are about to be acted upon. The contents
displayed in the Preset list have not been applied to the local array yet. When you click Apply
on the Port Operation pane, actions designated in the Preset list are applied to the local array.
For more information, see Preset list (Port Operation pane).
•
Operation information area
Displays operation information about settings displayed in the Preset list.
•
◦
Operation: Setting operation name.
◦
Number of Objects in Preset: Number of settings displayed in the Preset list.
Apply button
Applies actions designated in the Preset list to the local array. When actions are applied
without error, they are removed from the Preset list. If errors occur, actions are not applied,
error messages appear, and the actions remain in the Preset list.
•
Cancel button
Cancels all settings in the Preset list.
Port Operation tree
Displays ports in the connected local array. Contents displayed in the Port Operation list (right
pane) varies according to the item selected in the Port Operation tree (left pane).
Figure 38 Port Operation tree
•
Subsystem
When selected, displays nothing in the Port Operation list. Subsystem is selected when you
initially display the Port Operation pane.
•
External
When selected, displays ports designated a external ports, which is the port attribute used
for XP External Storage. External ports do not have High Speed mode.
•
Initiator
When selected, displays ports designated as an initiator (sending) port (used for XP Continuous
Access, Hitachi TrueCopy for z/OS, XP Continuous Access Journal, Hitachi Universal Replicator
for z/OS, and so on).
72
XP External Storage panes
•
Target
When selected, displays ports designated as host target ports (used for host connect).
•
RCU Target
When selected, displays ports designated as an RCU target (receiving) port (used for XP
Continuous Access, Hitachi TrueCopy for z/OS, XP Continuous Access Journal, Hitachi
Universal Replicator for z/OS, and so on).
•
Initiator/External
When selected, displays ports for which the Initiator/External MIX mode is set.
•
Port number
Displays ports assigned to each port attribute in the branch below each port attribute. XP
External Storage uses ports set to external. One of the following icons appears on the left of
each port number:
Icon
Description
Port in Standard mode.
Port in High Speed mode.
Port in Initiator/External MIX mode.
Port Operation list
Displays ports in the local array that XP External Storage can use or set. The port information
displayed corresponds to the item selected in the Port tree.
You can sort the list by attribute. For example, to sort by port numbers, click Port on the list.
Rows corresponding to ports that are about to be acted upon appear in the Preset list, and the
corresponding row in the Port Operation list appears in blue italics.
Figure 39 Port Operation list
•
Port
Port number. One of the following icons appears for each port:
Icon
Description
Port in Standard mode.
Port in High Speed mode.
Port in Initiator/External MIX mode.
Port Operation pane
73
•
Attribute
Port attribute. External ports are used for connecting to the external array. To set a remote
command device, you can use the port for which the Initiator/External MIX mode has been
set.
•
PCB Mode
Port's PCB mode. Standard, High Speed, or MIX (for Initiator/External MIX mode) appears.
External ports do not have High Speed mode. For more information about the PCB mode, see
the HP XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP
XP10000 Disk Array, HP 200 Storage Virtualization System. For more information about the
Initiator/External MIX mode, see Using Continuous Access XP or Continuous Access XP Journal
with remote command devices.
Preset list (Port Operation pane)
This list displays rows from the Port Operation list that are about to be acted on. Check the contents
of the Preset list before applying them to the local array. Contents displayed in the Preset list appear
in blue italics in the Port Operation list. When you click Apply in the Port Operation pane, actions
designated in the Preset list are applied to the local array and the contents of the Preset list
disappear.
If you click Cancel in the Port Operation pane, all designated actions in the Preset list are canceled.
If settings in the Preset list contain errors, actions are not applied to the local array even if you
click Apply. In that case, error messages appear, incorrect settings appear in the Preset list, and
error codes appear in the Preset list.
When you right-click a setting in the Preset list, the following commands appear:
•
Detail
Displays the Preset Detail window with detailed information about actions selected in the
Preset list. When an error code appears in the Preset list, a corresponding error message
appears in the Preset Detail window.
Figure 40 Preset Detail window (changing port attribute)
•
Delete
Cancels actions selected in the Preset list.
74
XP External Storage panes
5 Configuring external LUs
Use XP External Storage to perform operations to access external LUs, such as setting the port
attribute to the external port and mapping the external LU as the internal LDEV.
This chapter describes procedures for using XP External Storage to configure 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)
•
“Changing the cache mode setting of the external LU” (page 113)
•
“Changing the cache mode of all external LUs in an external array” (page 114)
•
“Changing the cache mode of an individual external LU” (page 114)
•
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)
Overview of configuring external LUs
Figure 41 (page 76) shows an example of using XP External Storage to configure external LUs.
Overview of configuring external LUs
75
Figure 41 Overview of configuring external LUs
The following is the general procedure for configuring external LUs.
1. Configure the port and system parameters for the external array. For instructions, see the
external LU's documentation, Setting an external array's port, and Notes on connecting external
arrays.
2. Start XP External Storage operations. For instructions, see the HP XP Command View Advanced
Edition Software user guide for XP Disk Arrays or the HP XP Remote Web Console user guide
for XP12000/XP10000 Disk Arrays and SVS 200.
3. Change to Modify mode.
For instructions, see the HP XP Remote Web Console user guide for XP12000/XP10000 Disk
Arrays and SVS 200.
4.
5.
Set the external array port attribute to External. For instructions, see Setting a local array's
port attributes.
Perform the Discovery operation.
In the Device tree on the LU Operation pane, select an external array, and select Discovery
(see Mapping external LUs (Add LU)).
NOTE: To perform Discovery operations, XP Command View Advanced Edition Software
or Remote Web Console must be in Modify mode.
6.
7.
8.
76
Display the LU Operation pane, right-click the external LU to be mapped as an internal LDEV
in the Device list, and select Add LU or Add LU (Auto). The Add LU or Auto Map Setting pane
appears.
Use the Add LU or Auto Map Settings pane to map the external LU as an internal LDEV (see
Mapping external LUs (Add LU)).
If you select a mainframe emulation type on the Add LU pane, use Volume Manager to reformat
the volume or perform the Write to Control Blocks operation. For instructions, (see the HP XP
LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000
Disk Array, HP 200 Storage Virtualization System.
Configuring external LUs
9.
Define alternate paths between the external array or mapped LU and the local array. For
instructions, see Defining alternate paths.
10. Use XP LUN Configuration and Security Manager Software to define paths. For instructions,
see the HP XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array,
HP XP10000 Disk Array, HP 200 Storage Virtualization System.
Setting an external array's port
This section describes the procedure for setting the external array's port. For more information, see
the external array's documentation.
1. Set the topology information for the connection configuration.
2. Set the data transfer speed for the configuration.
3. Set the system parameters. For more information about system parameters for specific external
arrays, see Notes on connecting external arrays.
4. Define the port's LUN.
Setting a local array's port attributes
The attribute of any port used for XP External Storage must be set to External.
NOTE: The ports that can be set as external ports are only the ports serving LDEVs, belonging
to CU group 0. If the storage is partitioned by using XP Disk/Cache Partition Software, the ports
that can be set as external ports are only the ports serving LDEVS associated with CU group 0,
and are allocated to SLPR 0 as well.
1.
2.
Select the Port Operation tab.
In the Port Operation list, select the port.
To set multiple ports at one time to External, select all the ports.
3.
Right-click, and select Change to External.
In the Port Operation list, the selected port's attribute changes to External, and the selected
port's row appears in blue italics. Rows to be affected appear in the Preset list. To check
setting details, right-click the setting in the Preset list, and select Detail. To cancel settings,
right-click the setting in the Preset list, and select Delete.
4.
5.
Click Apply. A confirmation message appears.
Click OK. The port attribute setting is applied to the local array, and the new setting appears
in the Port Operation list.
If an error occurs, the failed setting and an error code appears in the Preset list. To view error
messages, right-click the failed row, and select Detail.
6.
Set the topology for the connection configuration.
When an FC switch is connected, set Fabric to Enable. When a switch is not connected, set
Fabric to Disable, and specify FC-AL. Set Connection according to the actual connection
configuration. For more information about setting the topology, see the HP XP LUN
Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk
Array, HP 200 Storage Virtualization System.
7.
Set the data transfer speed to Auto Negotiation.
NOTE: When connecting to a TagmaStore AMS or TagmaStore WMS subsystem, use XP
LUN Configuration and Security Manager Software to set the data transfer speed of the
XP12000/XP10000/SVS200 external port you use to a fixed value other than Auto
Negotiation. Also, set the data transfer speed of the target port of the TagmaStore AMS or
TagmaStore WMS subsystem to the same fixed value according to the external port's data
transfer speed.
Setting an external array's port
77
Discovering and Mapping LUs
After setting the port used for XP External Storage to External, map the external LU as an internal
LDEV.
If you mapped the external LU and previously set the VMA of XP LUN Security Extension in that
volume, the former VMA setting is overwritten when you map the volume again. However, if XP
LUN Security Extension is not installed when you remap the volume, the volume with the VMA
setting cannot be mapped.
Following are the operations related to mapping:
•
Mapping external LUs individually (Add LU)
•
Mapping multiple external LUs at one time (Add LU (Auto))
•
Displaying detailed information stored in VMA (VMA information)
Mapping external LUs individually (Add LU)
This section describes mapping operations starting with the Add LU command. Use the Add LU
(Figure 42 (page 78)), Select Paths (Figure 43 (page 82)), SSID (Figure 46 (page 85)), and Set
SSID (Figure 47 (page 86)) panes for mapping external LUs individually.
NOTE: Before mapping the external LU, ensure that no other applications (such as XP RAID
Manager) that use the command device are executing. Stop any applications that are executing.
Figure 42 Add LU window
•
Vendor
External array's vendor.
•
Product
External array's product name.
•
Serial
External array's product serial number.
•
WWN
World Wide Name of the external array port used for connecting to the local array.
78
Configuring external LUs
•
LUN
LU number of the external LU.
•
Device
External LU's device name.
•
Ex-Dev. info.
External array information. When the external array is an XP1024/XP128 or TagmaStore
Workgroup Modular Storage (WMS) array, an asterisk (*) appears.
•
VMA
Information about the VMA setting of XP LUN Security Extension. If you mapped the external
LU and previously set the VMA of XP LUN Security Extension, an asterisk (*) appears. If XP
LUN Security Extension is not installed when you remap the volume, you cannot map the
volume with the VMA setting.
•
Capacity
External LU's capacity in blocks.
•
Characteristic
External LU's identification number.
•
Characteristic2
External LU's extended identifying information. This information is used for identifying logical
volumes in the EVA array. For more information, see Identifying logical volumes of EVA arrays
(using Characteristic 2).
•
ExG (1-16384)
Group number of the connected external LUs. You can specify any decimal value from 1 to
16384. The E displayed outside the text box is the capital letter of the external LU group.
•
Emulation Type
Emulation type of the mapped external LU (from the XP12000/XP10000/SVS200 perspective)
(see External LU attributes set by mapping).
If you clear the Except OPEN-V check box, OPEN-V and available mainframe emulation types
appear in the list.
If you select the Except OPEN-V check box, open-system emulation types other than OPEN-V
appear in the list. To map the external LU as an open-system volume, define the emulation
type to use for the mapped LU as OPEN-V or another type. To map the external LU as an
open-system volume using an emulation type other than OPEN-V, select the Except OPEN-V
check box.
If you plan to use the mapped external LU for an XP Flex Copy pair, you must select OPEN-V.
When the external LU to be mapped has the VMA setting, you must select OPEN-V.
•
LDEV Capacity
Default capacity of the emulation type selected in the Emulation Type box. When the external
LU's capacity is larger than the capacity displayed in LDEV Capacity, the external LU is divided
into the displayed capacity, and multiple LDEVs are created.
•
LDEV
Number of LDEVs created at mapping. By default, the maximum number of LDEVs
corresponding to the capacity supported by the emulation type specified in the Emulation Type
box appears. When the external LU to be mapped has the VMA setting, you can select only
1.
Discovering and Mapping LUs
79
•
IO Suppression
Mapped external LU's IO Suppression mode (for OPEN-V emulation only) (see External LU
attributes set by mapping).
To suppress I/O operations from hosts (by way of the XP12000/XP10000/SVS200) to the
mapped external LU or use the mapped external LU for a Flex Copy pair, select Enable.
If you do not suppress I/O from hosts to the mapped external LU, select Disable (for example,
for use with XP External Storage).
If you set the emulation type to something other than OPEN-V, IO Suppression mode is
automatically set to Disable.
When the external LU to be mapped has the VMA setting, IO Suppression mode is automatically
set to Disable.
CAUTION: To use the mapped external LU for the software products other than XP Flex Copy
(such as XP Cache LUN, XP Auto LUN, XP Continuous Access, XP Continuous Access Journal
XP Business Copy, or XP Snapshot), set IO Suppression mode to Disable.
•
CAUTION:
To set IO Suppression mode to Disable, XP External Storage must be installed.
CAUTION:
To set IO Suppression mode to Enable, Flex Copy must be installed.
Cache Mode
Specifies if the write I/O from the host is propagated synchronously or asynchronously to the
external storage device (see External LU attributes set by mapping).
To propagate the write I/O from the host to the external array asynchronously, select Enable.
To propagate the write I/O from the host to the external array synchronously, select Disable.
Data that is not written by the host (for example, data written by XP Business Copy) is
asynchronously destaged to the external array regardless of the Cache Mode setting.
If you set the IO Suppression mode to Enable, Cache Mode becomes Disable.
CAUTION:
•
If you select Disable, XP Cache LUN's bind mode cannot be set.
Alternate Path
Number of alternate paths automatically set when mapped. Value can be from 0 to 7. Default
is 1.
CAUTION:
Preset list.
•
If the specified number of alternate paths cannot be set, an error appears in the
CLPR (see External LU attributes set by mapping)
When cache memory is partitioned using XP Disk/Cache Partition, you can select the CLPR
used to access the mapped volume from the list. The SLPR number that the selected CLPR
belongs to appears on the right of the list. However, if you select a mainframe emulation type
in Emulation Type, you can only select CLPRs belonging to SLPR number 0. The Limited check
box appears on the right of the SLPR number. To display only CUs defined for the selected
SLPR, select the Limited check box. To display all CUs, regardless of the SLPR, clear the check
box. By default, the Limited check box is selected.
•
Select Paths button
Displays the Select Paths pane (Figure 43 (page 82)). Use the Select Paths pane to select paths
as candidates for primary and alternate paths and select paths that cannot be set to primary
and alternate paths. By default, all paths with a confirmed connection status of normal are set
as candidates for primary and alternate paths. However, to set a specific path as the alternate
80
Configuring external LUs
path, use the Select Paths pane to specify candidates for alternate paths. Alternate paths are
automatically set from the candidates, as many as the number set in Alternate Path.
CAUTION: If you do not set alternate paths on the Select Paths pane, alternate paths are
automatically set according to the WWN selected in the Device tree on the LU Operation
pane when you started the Add LU operation.
•
Clear button
Resets all the external LU's attributes.
•
CU list
CU number of the local array to which you want to map the external LU. Select the CU number
from the list. When the Limited check box is selected, the selection range is limited to the CU
belonging to the SLPR displayed in CLPR.
•
Linear button
Maps all external LUs listed in the CU:LDEV list at one time. When you click Linear and then
select an internal LDEV on the LDEV map, XP External Storage automatically selects from the
LDEV map the same number of internal LDEVs as external LUs listed in the CU:LDEV list, starting
at the internal LDEV you selected. The LDEV numbers of the selected internal LDEVs are
sequential. When Interval is set, mapping is done at the specified number of intervals. To
map one external LU to another internal LDEV after mapping the external LU automatically
using the Linear button, release the Linear button, and map the external LU individually.
•
CU:LDEV list
Displays the XP12000/XP10000/SVS200 CU:LDEV numbers of external LUs mapped as
internal LDEVs. (N/A) (Not Assigned) means the external LUs are not yet mapped as internal
LDEVs. To map an external LU as an internal LDEV, select an external LU with (N/A) in the
CU:LDEV list. To map all external LUs in the CU:LDEV list at one time, use the Linear button.
•
Interval
If you select two or more volumes in the CU:LDEV list or click Linear for mapping, you can
select the interval that arranges each volume. Values can be from 0 to 255. Default is 0.
For example, if you select three volumes in the CU:LEDV list, set Interval to 255, and map the
first volume to CU:LDEV number 00:01, the second and third volumes are mapped to 01:01
and 02:01, respectively.
•
LDEV map
Each cell in the map represents an internal LDEV. Select a cell for the internal LDEV on the
map. The selected cell turns blue, and the selected LDEV is mapped to the external LU. internal
LDEVs that have been mapped appear in gray, and those not yet mapped appear in white.
•
Previous and Next buttons
If you select multiple external LUs in the Device list, click Previous to map the external LU in
the row just above the currently selected external LU. Click Next to map the external LU in the
row just below the currently selected external LU.
•
OK button
Displays the SSID window, where you can continue with the next step of the mapping operation.
If the SSID setting is not necessary, the Add LU window closes, and the LU Operation pane
appears.
Discovering and Mapping LUs
81
The OK button is available when mapping on the Add LU window is complete.
•
Cancel button
Cancels all mapping operations, closes the Add LU window, and returns to the LU Operation
pane.
Select Paths pane
All paths that can be set as primary and alternate paths appear in the Select Paths pane. To set a
specific path as the alternate path, use the Select Paths pane to specify candidates for the alternate
paths.
If you let alternate paths be automatically set with all connected normal paths as candidates, you
can omit the setting operation on the Select Paths pane.
Figure 43 Select Paths pane
•
Port
Local array ports. You can set alternate paths for the selected port. One of the following icons
appears for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
•
Selected Paths
External array port for which you can set the alternate path connecting to the local array port
selected in the Port list. By default, all ports that can be set as alternate paths appear. The
WWN identifying the external array port appears. If the primary path and as many alternate
paths as you set in Alternate Path in the Add LU pane cannot be set with the paths selected
in Selected Paths, an error occurs and appears in the Preset list.
•
Unselected Paths
Ports excluded from being candidates for the ports setting the primary and alternate paths
appear among the external array ports that can be set as the primary and alternate paths.
WWNs identifying the external array ports appear in the list.
82
Configuring external LUs
•
Set button
If you select the port (external array WWN) you want to set as the candidate for the primary
and alternate paths in Unselected Paths, and click Set, the selected WWN moves to Selected
Paths.
•
Release button
If you select the port (external array WWN) you want to exclude from the list of candidates
for the primary and alternate paths in Selected Paths, and click Release, the selected WWN
moves to Unselected Paths.
•
OK button
Saves settings in the Select Paths pane, and closes the pane.
•
Cancel button
Cancels all settings in the Select Paths pane, and closes the pane.
To map one individual LU as one internal LDEV:
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select Discovery. WWNs appear in the tree indicating external array ports
that can be connected.
3. In the Device tree, select the port (WWN) you want to connect from the WWNs listed in the
Device.
External LUs that can be connected from the external array port (WWN) selected in the tree
appear in the Device list.
4.
5.
Right-click the external LU you want to map as an internal LDEV in the Device list, and select
Add LU. The Add LU window appears.
Select the internal LDEV that is mapped to the external LU selected in the Device list on the
Add LU window. Enter the following items in the Add LU window:
a. In the ExG box, select an external LU group number.
b. From the Emulation Type list, select an emulation type.
c. In the LDEV box, select the number of volumes to create.
d. Select the IO Suppression mode.
e. Select the Cache Mode.
f. In the Alternate Path box, select the number of alternate paths that are automatically set.
g. In the CLPR box, select the CLPR to be used. To limit the CU selection range, select the
Limited check box.
h. In the CU# list, select the CU number.
i. To map two or more external LU at the same time, select the interval that arranges each
volume in the Interval box.
Discovering and Mapping LUs
83
j.
Select one or more external LUs, and select one or more cells in the LDEV map.
When selecting two or more external LUs in the CU:LDEV list, if you select one cell of the
internal LDEV number in the LDEV map, the number of cells automatically selected is the
same as the number external LUs selected in the CU:LDEV list with the selected internal
LDEV first. When Interval is set, mapping is done at intervals of the specified number.
•
To map all the external LUs displayed in the CU:LDEV list at one time:
Click Linear, and select an internal LDEV on the LDEV map. The same number of
internal LDEVs as the external LUs listed in the CU:LDEV list are automatically selected
on the LDEV map following the internal LDEV you selected (Figure 44 (page 84)).
The LDEV numbers of the selected XP LDEV are in a series. When Interval is set, the
mapping is done at the specified interval.
Figure 44 Add LU pane (mapping using the Linear button)
•
To map one external LU to another internal LDEV:
After automatically mapping the external LU using the Linear button, release the
Linear button, and map the external LU individually (Figure 45 (page 84)).
Figure 45 Add LU pane (mapping with the Linear button released
84
Configuring external LUs
6.
If you do not want to automatically set primary and alternate paths, but want to specify paths
set as candidates for primary and alternate paths, click Select Paths. The Select Paths pane
appears.
To automatically set alternate paths, go to step 9.
7.
8.
9.
Select the path and exclude it from the list of candidates for primary and alternate paths in
the Select Paths pane. For more information, see Select Paths pane.
Click OK. The Add LU pane appears.
When all settings are complete on the Add LU window, click OK.
•
If you need to set the SSID, the SSID window appears. Go to step 10.
Figure 46 SSID window
•
If the SSID setting is not necessary, the Add LU window closes, and the LU Operation
pane appears. Settings appear in blue italics in the Device tree and Device list. Contents
specified in the Add LU window appear in the Preset list. To check setting details, right-click
Discovering and Mapping LUs
85
the setting in the Preset list, and select Detail. To cancel settings, right-click the setting in
the Preset list, and select Delete. Go to step 13.
10. If you need to set an SSID to the mapped internal LDEV, the SSID pane appears. When storage
is partitioned using XP Disk/Cache Partition, select the SLPR number in the SLPR box. If you
select the Limited check box and select the SLPR number, you can set only SSIDs that can be
used for the selected the SLPR. If you do not select the Limited check box, you can set the SSID
from all unused SSIDs regardless of the selected SLPR number. Right-click the CU:LDEV number
on the SSID pane, and select Set SSID. The Set SSID window appears.
Figure 47 Set SSID window
11. Enter the SSID. If you selected the Limited check box on the SSID window, only SSIDs that can
be used in the SLPR selected on the SSID pane appear in the drop-down list. If you did not
select the Limited check box on the SSID pane, all unused SSIDs appear in the list, regardless
of the selected SLPR. You can enter 0x0004 to 0xFFFE as an SSID.
12. Click OK. The Set SSID window closes, and the LU Operation pane appears.
Settings appear in blue italics in the Device tree and Device list and also appear in the Preset
list. To check setting details, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.
13. Click Apply. A confirmation message appears.
If you already stopped the application, go to step 14. If you have not stopped the application,
click Cancel to close the message pane, stop the application, and retry the operation.
14. Click OK. A confirmation message appears.
15. Click OK. The mapping set in the Add LU window is applied to the local array, and the
specified contents appear in the Device list.
If errors occur during the external LU mapping operation, failed settings and error codes
appear in the Preset list. To check error messages, right-click the failed setting, and select
Detail.
Mapping multiple external LUs at (Add LU (Auto))
This section describes the procedure to map multiple external LUs at one time. The procedure starts
with the Add LU (AUTO) command.
NOTE: Before mapping the external LU, you must check whether any application (for example,
XP RAID Manager) using the command device is in progress. If any application using the command
device is in progress, stop the application.
When mapping multiple external LUs at one time, the CU:LDEV numbers for the mapped destination
internal LDEVs are assigned in a series. When performing the mapping operation, you can select
the first CU:LDEV number for the mapped destination internal LDEVs. XP External Storage assigns
the selected CU:LDEV number as the first mapped destination LDEV, and as many subsequent
CU:LDEV numbers are kept for mapping as the number external LUs required to be mapped. To
automatically perform the mapping operation, you can let XP External Storage select the first
CU:LDEV number.
CAUTION: If the LUs you are mapping include a volume with the VMA setting, you cannot use
the Add LU (AUTO) command to map them at one time.
86
Configuring external LUs
NOTE: If you set Interval for the mapping, the CU:LDEV number of the internal LDEV that must
be mapped is set to the specified interval value.
Use the Auto Map Setting and Select LDEV windows (Figure 49 (page 89)) for mapping multiple
external LUs at one time.
Figure 48 Auto Map Setting window
•
ExG (1-16384)
Group number containing the specified external LU. Specify any decimal value from 1 to
16384. The E displayed outside of the text box is the capital letter of the external LU group.
•
Emulation Type
Emulation type of the external LU from the perspective of the XP12000/XP10000/SVS200
(see External LU attributes set by mapping).
If you clear the Except OPEN-V check box, OPEN-V and available mainframe emulation types
appear in the list.
If you select the Except OPEN-V check box, open-system emulation types other than OPEN-V
also appear in the list. To map the external LU as an open system LU, decide the mapped LU's
emulation type, either OPEN-V or other than OPEN-V. To map the external LU as an open-system
LU with an emulation type other than OPEN-V, select the Except OPEN-V check box.
If you plan to use the mapped external LU for an XP Flex Copy pair, you must specify OPEN-V.
When the external LU to be mapped has the VMA setting, you must select OPEN-V.
Due to the advantages of the OPEN-V emulation type, HP recommends OPEN-V as the default
type for use with XP External Storage.
•
Create LDEVs
Number of LDEVs that can be mapped based on the capacity supported by the emulation
type specified in the Emulation Type box. Select the number of LDEVs you want to map from
the Create LDEVs list. The default is Full. When Create LDEVs is Full, the maximum number of
LDEVs that can be created based on the capacity supported by the specified emulation type
are mapped. The total number of LDEVs being mapped appears at Total.
•
IO Suppression
When you specify the OPEN-V emulation type, you can specify the mapped LU's IO Suppression
mode (see External LU attributes set by mapping).
If you suppress I/O operations from hosts (by way of the XP12000/XP10000/SVS200) to
the mapped external LU or use the mapped external LU for an XP Flex Copy pair, select Enable.
Discovering and Mapping LUs
87
If you do not suppress I/O from hosts to the mapped external LU, select Disable (for example,
for XP External Storage).
When setting the emulation type to something other than OPEN-V, I/O Suppression mode is
automatically set to Disable.
When the external LU to be mapped has the VMA setting, IO Suppression mode is automatically
set to Disable.
CAUTION: To use the mapped external LU for products other than XP Flex Copy (such as
XP Cache LUN, XP Auto LUN, XP Continuous Access, XP Continuous Access Journal, and XP
Business Copy), set IO Suppression mode to Disable.
•
CAUTION:
To set I/O Suppression mode to Disable, XP External Storage must be installed.
CAUTION:
To set IO Suppression mode to Enable, XP Flex Copy must be installed.
Cache Mode
Specifies if the write I/O from the host is propagated synchronously or asynchronously to the
external storage device (External LU attributes set by mapping).
To propagate write I/Os from the host to the external array asynchronously, select Enable.
To propagate write I/Os from the host to the external array synchronously, select Disable.
Data that is not written by the host (for example, data written by XP Business Copy) is
asynchronously destaged to the external array regardless of the Cache Mode setting.
If you set IO Suppression mode to Enable, Cache Mode is automatically set to Disable.
CAUTION:
•
If you set Disable, XP Cache LUN's bind mode cannot be set.
Start CU:LDEV
First CU:LDEV number in the series of mapped destination internal LDEVs. The default is “- :
-”. Interval also appears. The default is 0.
To have XP External Storage select the first CU:LDEV number for the mapped internal LDEV,
leave the default (“- : -”). XP External Storage searches for an available CU:LDEV number
starting with 00:00, and selects the first one it finds.
To specify the first CU:LDEV number and interval, click Select LDEV. The Select LDEV window
(Figure 49 (page 89)) appears.
•
Alternate Path
Number of alternate paths automatically set when mapped. Values can be from 0 to 7. Default
is 1.
CAUTION:
Preset list.
•
If the specified number of alternate paths cannot be set, an error appears in the
CLPR (see External LU attributes set by mapping)
When cache memory is partitioned using XP Disk/Cache Partition, you can select the CLPR
used to access the mapped LU from the list. The SLPR number that the selected CLPR belongs
to appears on the right of the list. However, when you select a mainframe emulation type in
Emulation Type, you can only select CLPRs belonging to SLPR number 0. The Limited check
box appears on the right of the SLPR number. To display only CUs defined for the selected
SLPR, select the Limited check box. To display all CUs, regardless of the SLPR, clear the check
box. By default, the Limited check box is selected.
88
Configuring external LUs
•
Select LDEV button
Displays the Select LDEV window (Figure 49 (page 89)) where you can select the first CU:LDEV
number in the series.
•
Select Paths button
Displays the Select Paths pane (Figure 43 (page 82)). Use the Select Paths pane to select paths
as candidates for primary and alternate paths and select paths not set to primary and alternate
paths. By default, all paths with a confirmed connection status of normal are set as candidates
for primary and alternate paths. However, to set a specific path as the alternate path, specify
candidates for alternate paths on the Select Paths pane. Alternate paths are automatically set
from the candidates, as many as the number set in Alternate Path.
See Mapping external LUs individually (Add LU) for more information about settings on the
Select Paths pane.
CAUTION: If you do not set alternate paths on the Select Paths pane, alternate paths are
automatically set according to the WWN selected in the Device tree on the LU Operation
pane when you start the Add LU operation.
•
OK button
Starts mapping internal CU:LDEV numbers to external LUs. When mapping is complete, the
SSID window appears if the SSID setting is required. If the SSID setting is not required, the
Auto Map Setting window closes, and the LU Operation pane appears.
•
Cancel button
Cancels all mapping operations, closes the Auto Map Setting window, and returns to the LU
Operation pane.
Select LDEV window
Figure 49 Select LDEV window
Discovering and Mapping LUs
89
The Select LDEV pane consists of the following items.
•
CU list
CU number of the local array to which you want to map the external LU. You can select the
CU number from the drop-down list.
•
Interval
Interval of the CU:LDEV number for mapping each volume. When two or more LDEVs are
created from one external LU and mapped, the CU:LDEV number is set at intervals specified
in each created LDEV.
For example, set the interval as follows:
◦
In the Device list, select three external LUs.
◦
In Create LDEVs on the Auto Map Setting window, select 3 (nine LDEVs are created).
◦
In Interval, select 1.
◦
Set the starting CU:LDEV number to 00:00.
For this example, LDEVs created from the first external LU are mapped to 00:00, 00:02,
and 00:04, respectively. The starting CU:LDEV number of LDEVs created from the second
external LU is 00:06, and subsequent LDEVS are mapped to 00:08 and 00:0A. The
starting CU:LDEV number of LDEVs created from the third external LU is 00:0C, and
subsequent LDEVs are mapped to 00:0E and 00:10.
•
LDEV map
Each cell in the map represents an internal XP CU and LDEV number. Select a cell for the
internal LDEV on the map. The selected cell turns blue, and the LU of the selected cell becomes
the first CU:LDEV number of the mapped destination LUs. Defined (in use) internal LDEVs
appear in gray, and internal LDEVs to be mapped appear in white.
•
Clear button
Releases the cell selected on the LDEV map.
•
OK button
Closes the Select LDEV window, and returns to the Auto Map Setting window. On the Auto
Map Setting window, the CU:LDEV number you selected on the Select LDEV window as the
head CU:LDEV number of the mapped destination internal LDEVs appears in Start CU:LDEV.
•
Cancel button
Cancels all settings in the Select LDEV window, and returns to the Auto Map Setting window.
To map multiple external LUs as internal LDEVs at one time:
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select Discovery. WWNs identifying the external array port that can be
connected appear in the tree.
3. In the Device tree, select the port (WWN) you want to connect from the WWNs displayed.
External LUs that can be connected from the port (WWN) selected in the tree appear in the
Device list.
4. In the Device list, select the external LUs you want to map as internal LDEVs, right-click, and
select Add LU (Auto). The Auto Map Setting window (Figure 48 (page 87)) appears.
5. Set the attributes for the external LUs you selected on the Device list.
90
Configuring external LUs
NOTE:
6.
7.
8.
9.
Attributes for all LUs mapped at one time are identical.
•
To select the first CU:LDEV number of the mapped destination internal LDEVs and the
mapping interval, go to step 6.
•
To let XP External Storage select the first CU:LDEV number, go to step 9.
Click Select LDEV. The Select LDEV window appears.
Select the first CU:LDEV number of the mapped destination internal LDEVs and the mapping
interval.
Click OK. The Auto Map Setting window appears.
If you do not want to automatically set the primary and alternate paths, but you want to specify
the paths to be set as candidates for the primary and alternate paths, click Select Paths. The
Select Paths window appears.
To automatically set alternate paths, go to step 12.
10. Select the path and exclude it from the list of the candidates for the primary and alternate
paths. For instructions, see Mapping external LUs individually (Add LU).
11. Click OK. The Auto Map Setting window appears.
12. Click OK. The Auto Map Setting window closes, and mapping the internal CU:LDEV numbers
to the external LUs starts.
NOTE: If the CU:LDEV numbers cannot be mapped properly because too many external LUs
are selected on the Device list, all processing is canceled and the message pane appears.
•
After the CU:LDEV number mapping is complete, if the SSID setting is required, the SSID
window (Figure 46 (page 85)) appears. Go to step 13.
•
If the SSID setting is not necessary, the LU Operation pane appears. Settings appear in
blue italics in the Device tree and Device list. The contents specified in the Auto Map
Setting window appear in the Preset list. To check setting details, right-click the setting in
the Preset list, and select Detail. To cancel settings, right-click the setting in the Preset list,
and select Delete. Go to step 16.
13. If you need to set an SSID to the mapped internal LDEV, the SSID window appears. When
storage is partitioned using XP Disk/Cache Partition, select the SLPR number in the SLPR list.
If you select the Limited check box and select the SLPR number, only SSIDs that can be used
for the selected SLPR can be set. If you do not select the Limited check box, you can set the
SSID from all of the unused SSIDs regardless of the selected SLPR number. Right-click the
CU:LDEV number on the SSID window, and select Set SSID. The Set SSID window
(Figure 47 (page 86)) appears.
14. Enter the SSID on the Set SSID window. If you selected the Limited check box on the SSID
window, only SSIDs that can be used in SLPR selected on the SSID window appear in the list.
If you do not select the Limited check box on the SSID window, all of the unused SSIDs appear
in the list, regardless of the selected SLPR. You can enter 0x0004 to 0xFFFE as an SSID.
15. Click OK. The Set SSID window closes, and the LU Operation pane appears.
Settings appear in blue italics in the Device tree and Device list. Settings appear in the Preset
list. To check setting details, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.
16. Click Apply. A confirmation message appears.
If you already stopped the application, go to step 17. If you have not stopped the application,
click Cancel, stop the application, and retry the operation.
17. If you already stopped the application, click OK. A confirmation message appears.
Discovering and Mapping LUs
91
18. Click OK. The mapping set in the Auto Map Setting window is applied to the local array, and
the specified contents appear in the Device list.
When an error occurs during the external LU mapping process, the failed setting and an error
code appears in the Preset list. To check the error message, right-click the failed setting, and
select Detail.
Displaying detailed information stored in VMA (VMA information)
When VMA of XP LUN Security Extension is set for an external LU, you can check information
stored in the VMA before mapping the LU. Information stored in the VMA appears in the VMA
Information pane (Figure 50 (page 92)). To view the VMA Information pane, select WWN in the
Device tree, and select the external array's port. Right-click the volume you want to display, and
select VMA Information.
For more information about items displayed in the VMA Information pane, see the HP LUN Security
XP Extension user guide.
Figure 50 VMA Information pane
•
Vendor
External array's vendor.
•
Product
External array's product name.
•
LUN
LU number of the external LU.
•
Attribute
Select from the following access attributes:
•
◦
Read/Write: Read and write operations can be performed on the volume.
◦
Read Only: Only read operations can be performed on the volume.
◦
Protect: You cannot access the volume. Read and write operations cannot be performed.
S-Vol
Indicates whether or not the volume can be specified as an S-VOL: Enable or Disable.
92
Configuring external LUs
•
Reserved
Indicates whether XP RAID Manager and XP Command View Advanced Edition Software or
Remote Web Console can be used to make LU path and command device settings.
•
◦
Hyphen (-): You can use XP RAID Manager and XP Command View Advanced Edition
Software or Remote Web Console to make LU path and command device settings.
◦
RAID Manager: You can use XP RAID Manager to make LU path and command device
settings, but cannot use XP Command View Advanced Edition Software or Remote Web
Console.
Retention Term
Period (in days) when you cannot change the Attribute field to Read/Write.
•
Mode
Mode the XP RAID Manager user assigns to the logical volume.
•
◦
Zer: Zero Read Cap mode is assigned to the logical volume.
◦
Inv: Invisible mode is assigned to the logical volume.
◦
Zer/Inv: Zero Read Cap and Invisible mode are assigned to the logical volume.
◦
Hyphen (-): The XP RAID Manager user has not assigned a mode to the logical volume.
Extent
Indicates whether extents are set.
•
◦
Asterisk (*): Extents are set.
◦
Hyphen (-): Extents are not set.
Used Volumes
Licensed capacity for XP LUN Security Extension that the LU has used.
Setting alternate paths for external LUs
Before using an external LU mapped as an internal LDEV, you must set at least one alternate path
from the internal LDEV to the external LU (likely by way of an alternate controller). The number of
alternate paths set is the same as the number specified on the Add LU or Auto Map Setting window
when the LU was mapped as the internal LDEV. For more information, see Alternate paths.
Use the Path Setting window (Figure 51 (page 94)) to add and define alternate paths to the paths
set at mapping or change the alternate paths.
NOTE: You can add or delete alternate paths by selecting multiple external LUs at one time. For
more information, see Adding alternate paths by selecting multiple external LUs (Add Paths) and
Deleting alternate paths by selecting multiple external LUs (Delete Paths).
CAUTION: You cannot delete all the current alternate paths to substitute newly-added alternate
paths for them in one operation. To replace all the current alternate paths with newly-added alternate
paths, you need to perform more than two operations and leave at least one current alternate path
setting when you perform the first operation.
Use the Path Setting window (Figure 51 (page 94)) to define alternate paths.
You can perform the following operations on the Path Setting window:
•
Defining alternate paths
•
Changing a defined alternate path priority
Setting alternate paths for external LUs
93
•
Canceling alternate path definitions
•
Changing alternate paths
•
“Replacing all the alternate paths with newly-added alternate paths” (page 99)
The Path Setting window displays information about external arrays and the condition of paths set
from the internal LDEV to the external LU.
Figure 51 Path Setting window
•
Vendor
External array's vendor.
•
Product
External array's product name.
•
Serial
External array's serial number.
•
Group
External LU group and reference number of the external LU in the group.
•
Characteristic
External LU's identification number.
•
Device
External LU's device name.
•
Capacity
External LU's capacity in blocks.
94
Configuring external LUs
•
Alternate Path list
Status of alternate paths. The Alternate Path list consists of two tables. The Configured Paths
table displays previously defined paths. The Available Paths table displays available paths.
The Alternate Path list displays the following information:
◦
Port: Port number in the local array connected to the external array. One of the following
icons appears for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
◦
WWN: External array port's identification number.
◦
LUN: LU number of the external LU.
◦
Priority: Priority of paths connecting to the external LU. A 1 indicates the path with the
highest priority.
◦
Status: Status of the path to the external LU. For information about reacting to the displayed
status, see Troubleshooting External Storage XP. Possible values:
–
Normal: Path is normal.
–
Unknown: Path status is unknown.
–
Blockade: Path is blocked.
–
External device setting changed: External array's setting changed. For example, the
path definition was deleted or the external array itself was replaced.
–
LDEV size reduced: External array's volume capacity setting changed (volume capacity
was reduced).
–
Not ready: External array replied NOTREADY.
–
Illegal request: External array replied ILLEGALREQUEST.
–
Command aborted: External array replied ABORTEDCOMMAND.
–
Busy: External array status is BUSY.
–
LDEV reserved: External array status is Reserve.
–
Response error: External array status is blocked because of an abnormal reply
(Response).
–
Initiator port: External array's port attribute changed to initiator port.
–
RCU target port: External array's port attribute changed to RCU target.
–
Unknown port: External array's port attribute is unknown.
–
Cannot detect port: Path was removed or external array port could not be found.
–
Internal error: Program error occurred, or there is a logical contradiction.
–
Timeout: Processing was retried because of an abnormal reply, but a timeout occurred.
–
Standby: External array's port is standing by. Port status is normal, but cannot receive
I/O.
–
Target error: Port failures, such as controller blockade, were detected on the external
array side.
–
Checking: XP External Storage is checking defined path configuration information.
Setting alternate paths for external LUs
95
•
–
Disconnect: Connection to the external array or LU was stopped using the Disconnect
Subsystem or Disconnect Volume command.
–
Unavailable: External array replied Unavailable. The external array demands to
change the connected port. After the status becomes Unavailable, the primary path
changes to the alternate path that is in the Standby status. When the primary path
changes, the path status becomes Normal.
–
Backoff: External array replied Backoff. The path status is Waiting for Recovery
because a temporary error occurred in the external array's volume. Even if the primary
path's status becomes Backoff, the primary path does not change to the alternate
path immediately. After the error recovery, the status becomes Normal. If you cannot
recover the status from the error, the path status changes to the other status.
–
Device check error: The target volume in the external subsystem is not accessible,
even though the external volume was mapped.
–
Medium error: The target volume in the external subsystem has become inaccessible.
◦
I/O TOV: Time over value for I/O to the external LU
◦
Qdepth: Number of Read/Write commands that can be issued (queued) to an external
LU at one time
◦
Path Watch: Time period beginning when the connection of all paths to the external LU
is down and ending when the external LU is blocked.
◦
Mode: How the local array manages alternate paths when defined. Possible values:
–
Single: Uses only the path with the highest priority (primary path) to execute I/Os to
the external LU. If selected, the second-highest priority alternate path is enabled only
if a maintenance operation or failure affecting the primary path occurs. That is, the
external array contains Active/Passive (for example, MSA) or Asymmetrical
Active/Active controllers (for example, Hitachi 9500V).
–
Multi: Uses all of the set paths at the same time to execute I/Os to the external LU,
distributing the workload. That is, the external array contains Symmetrical
Active/Active controllers (for example, XP).
Previous and Next buttons
If you select multiple external LUs in the Device list, click Previous to change the Alternate Path
list to the external LU appearing just above the currently displayed LU. Click Next to change
the Alternate Path list to the external LU appearing just below the currently displayed LU.
•
OK button
Closes the Path Setting window, and returns to the LU Operation pane. Contents specified in
the Path Setting window appear in blue italics in the Device list, and settings appear in the
Preset list.
•
Cancel button
Cancels all alternate path setting operations, closes the Path Setting window, and returns to
the LU Operation pane.
Defining alternate paths
Use the Path Setting window to define alternate paths.
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select the external LU group number. Information about the external LU
mapped as an internal LDEV appears in the Device list.
96
Configuring external LUs
3.
In the Device list, right-click the external LU, and select Path Setting. The Path Setting window
appears.
The Configured Paths table displays detailed information about one currently defined path
and the alternate paths. The Available Paths table displays paths that can be set as alternate
paths.
4.
In the Available Paths table, right-click the row of the path to be defined as an alternate path,
and select Add.
The selected path is defined as an alternate path, and detailed information appears in the
Configured Paths table.
5.
Click OK. The Path Setting window closes, and the LU Operation pane appears.
Selected rows appear in blue italics in the Device list. Specified contents also appear in the
Preset list. To check details on intended operations, right-click the setting in the Preset list, and
select Detail. To cancel settings, right-click the setting in the Preset list, and select Delete.
6.
7.
Click Apply. A confirmation message appears.
Click OK.
The alternate path defined in the Path Setting window is applied to the local array, and the
specified contents appear in the Device list.
If errors occur during alternate path operations, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
Changing a defined alternate path priority
To change the alternate path's priority, use the Priority Up and Priority Down commands displayed
in the Path Setting window (Figure 52 (page 98)).
•
Priority Up: Raises the priority of the path selected in the Alternate Path list.
•
Priority Down: Lowers the priority of the path selected in the Alternate Path list.
As long as the external array uses Symmetrical Active/Active controllers (for example, XP), change
an alternate path to the currently used path by simply raising the priority of the alternate path or
lowering the priority of the currently used path.
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select the external LU group number. Information about the external LU
mapped as an internal LDEV appears in the Device list.
3. In the Device list, right-click the external LU, and select Path Setting. The Path Setting window
(Figure 51 (page 94)) appears.
4. Detailed information about the currently used path and alternate path appears in the Configured
Paths table, and paths that can be defined as alternate paths appear in the Available Paths
table.
5. In the Configured Paths table, right-click the row of the path defined as the alternate path, and
select Priority Up (Figure 52 (page 98)). The row for the selected path switches with the row
above it. The alternate path's priority is raised, and the path is set as the currently used path.
Setting alternate paths for external LUs
97
Figure 52 Path Setting window, shortcut menu
6.
Repeat the Priority Up command until the row of the selected path is displayed on the first line
of the Configured Path list and that row's Priority column changes to 1.
When the Priority column changes to 1, the path is set as the typically used one (primary
path).
7.
Click OK. The Path Setting window closes, and the LU Operation pane appears.
Selected rows appear in blue italics in the Device list. Specified contents appear in the Preset
list. To check details on intended operations, right-click the setting in the Preset list, and select
Detail. To cancel settings, right-click the setting in the Preset list, and select Delete.
8.
9.
Click Apply. A confirmation message appears.
Click OK. The change in the alternate path defined in the Path Setting window is applied to
the local array, and specified contents appear in the Device list.
If errors occur during alternate path operations, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
Canceling alternate path definitions
Use the Path Setting pane to cancel an alternate path definition.
1. Follow step 1 to step 3 in Defining alternate paths.
2. In the Configured Paths table, right-click the row of the alternate path, and select Delete.
The selected alternate path's definition is canceled, and detailed information about the path
is deleted from the Configured Paths table.
3.
98
Follow step 6 to step 8 in Defining alternate paths.
Configuring external LUs
Changing alternate paths
To change an alternate path, cancel the current alternate path, and then define another path as
a new alternate path.
CAUTION: You cannot delete all the current alternate paths to substitute newly-added alternate
paths for them in one operation. To replace all the current alternate paths with newly-added alternate
paths, you need to perform more than two operations and leave at least one current alternate path
setting when you perform the first operation. For the detailed procedure, see “Replacing all the
alternate paths with newly-added alternate paths” (page 99).
1.
2.
Follow step 1 to step 3 in Defining alternate paths.
In the Configured Paths table, right-click the row of the path currently defined as the alternate
path, and select Delete.
The selected alternate path's definition is canceled, and detailed information about the path
is deleted from the Configured Paths table.
3.
In the Available Paths table, right-click the row of the path to be defined as the new alternate
path, and select Add.
The specified alternate path is defined, and detailed information about the path is displayed
in the Configured Paths table.
4.
Follow step 6 to step 8 in Defining alternate paths.
Replacing all the alternate paths with newly-added alternate paths
This section explains how to change all the current alternate paths to newly-added alternate paths
with an example.
The following figure shows the overview of the operation and the status of the alternate paths.
When you delete the current alternate paths (A and B) and add new alternate paths (C and D),
you cannot delete both the current alternate paths (A and B) in one operation because at least one
current path which functions normally has to be configured. In this case, you need to delete the
alternate path A and add the alternate path C, and then apply the setting. After that, you need to
delete the alternate path B and add the alternate path D.
Setting alternate paths for external LUs
99
Figure 53 Overview of Operation to Replace All the Current Alternate Paths with Newly-added
Alternate Paths
To replace all the current alternate paths (A and B) with newly-added alternate paths (C and D):
1. Execute the Disconnect Paths command on the alternate path A (see 5.16).
2. Disconnect the cable which the alternate path A uses, and connect the cable which the alternate
path C uses.
3. Cancel the configuration of the alternate path A, and add the alternate path C (see 5.5.4).
4. Click the Apply button to apply the settings of the alternate paths A and C.
5. Make sure the status of the alternate path C is Normal.
At this point, the alternate paths B and C are configured as normal paths.
Take the following steps to delete the alternate path B and add the alternate path D.
6.
7.
Execute the Disconnect Paths command on the alternate path B (see 5.16).
Disconnect the cable which the alternate path B uses, and connect the cable which the alternate
path D uses.
8. Cancel the configuration of the alternate path B, and add the alternate path D (see 5.5.4).
9. Click the Apply button to apply the settings of the alternate paths B and D.
10. Make sure the status of the alternate path D is Normal.
Adding alternate paths by selecting multiple external LUs (Add Paths)
To add paths other than the alternate paths you have set as you have mapped the volume, you
can add paths at one time selecting the multiple volumes that belong to the same external volume
group. To add the alternate paths to the multiple volumes at one time, you need to set on the Add
100 Configuring external LUs
Paths panel, check the setting on the Path Setting panel, and then apply the setting to the array.
You can also change the setting of the paths by each external volume on the Path Setting panel.
CAUTION: You cannot delete all the current alternate paths to substitute newly-added alternate
paths for them in one operation. To replace all the current alternate paths with newly-added alternate
paths, you need to perform more than two operations and leave at least one current alternate path
setting when you perform the first operation. For the detailed procedure, see “Replacing all the
alternate paths with newly-added alternate paths” (page 99).
NOTE: Use the Add Paths window to add paths to multiple external LUs at one time. However,
path settings might not be applied because of the current path setting of each volume. After setting
paths in the Add Paths window, check whether or not the new path settings can be applied in the
Path Setting window for each external LU. If the setting cannot be applied, the setting from the
Add Paths window does not appear on the Path Setting window. The setting from the Add Paths
window also does not appear in the Preset list or in the LU Operation pane.
Figure 54 Add Paths window
•
Port
Local array ports. After selecting a port, you can add paths. One of the following icons appears
for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
•
Selected Paths
Paths that are added as ports that configure alternate paths. WWNs identify ports on the
external array. Nothing is displayed when you initially access the Add Paths window.
•
Unselected Paths
External array ports (WWNs) that can configure the path connecting with the local array port
selected in the Port list. Select WWNs from this list to add as alternate paths.
•
Set
Moves WWNs selected in Unselected Paths to Selected Paths.
•
Release
Moves WWNs selected in Selected Paths to Unselected Paths.
Adding alternate paths by selecting multiple external LUs (Add Paths)
101
•
OK
Saves settings in the Add Paths window, closes the Add Paths window, and displays the Path
Setting window.
•
Cancel
Cancels all settings in the Add Paths window, and closes the window.
To add alternate paths to multiple external LUs at one time:
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select an external LU group number. Information about external LUs mapped
as internal LDEVs appears in the Device list.
3. In the Device list, select multiple external LUs, right-click, and select Add Paths. The Add Paths
window appears.
4. In the Port list, select the local array port. External array ports (WWNs) that can configure
the path connecting with the selected local array port appear in Unselected Paths.
5. In the Unselected Paths list, select the port's WWNs, and click Set. The selected WWNs move
to Selected Paths.
6. Click OK. The Path Setting window appears.
7. Ensure that added paths are applied to the array in the Path Setting window. You can also
change the alternate path setting in this window. For more information, see Setting alternate
paths for external LUs.
8. Click OK. The Path Setting window closes, and the LU Operation pane appears.
Selected rows in the Device list appear in blue italics. Specified settings appear in the Preset
list. To check setting details, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.
9. Click Apply. A confirmation message appears.
10. Click OK. Alternative paths added using the Add Paths and Path Setting windows are applied
to the array, and the specified content appears in the Device list.
If errors occur during alternate path definition, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
Deleting alternate paths by selecting multiple external LUs (Delete Paths)
You can delete paths for multiple volumes that belong to the same external LU group at one time.
To delete alternate paths for multiple external LUs at one time, select the alternate path in the Delete
Paths window, check the setting in the Path Setting window, and apply the setting to the array.
CAUTION:
At least one normal path must be set on each mapped external LU.
NOTE: Use the Delete Paths window to delete paths to multiple external LUs at one time. However,
the deleted path settings might not be applied because of the current path setting of each volume.
After you set the deletion in the Delete Paths window, check whether or not the new path settings
can be applied in the Path Setting window for each external LU. If the setting cannot be applied,
the setting from the Delete Paths window does not appear on the Path Setting window. The setting
from the Delete Paths window also does not appear in the Preset list or in the LU Operation pane.
102 Configuring external LUs
Figure 55 Delete Paths window
•
Port
Local array ports. After selecting a port, you can add the paths. One of the following icons
appears for each port:
Icon
Description
Port in Standard mode.
Port in Initiator/External MIX mode.
•
Selected Paths
Paths of WWNs to be deleted. WWNs identify ports on the external array. Nothing is
displayed when you first access the Delete Paths window.
•
Unselected Paths
Ports (WWNs) on the external array that have paths configured for connecting with the local
array port selected in the Port list. Select WWNs from this list to delete paths.
•
Set
Moves WWNs selected in Unselected Paths to Selected Paths.
•
Release
Moves WWNs selected in Selected Paths to Unselected Paths.
•
OK
Saves settings in the Delete Paths window, closes the Delete Paths window, and displays the
Path Setting window.
•
Cancel
Cancels all of the settings in the Delete Paths window, and closes the window.
To delete paths for multiple volumes at one time:
1. Select the LU Operation tab. The LU Operation pane appears.
2. In the Device tree, select an external LU group number. Information about external LUs mapped
as internal LDEVs appears in the Device list.
3. In the Device list, select multiple external LUs, right-click, and select Delete Paths. The Delete
Paths window (Figure 55 (page 103)) appears.
4. In the Port list, select the local array port. External array ports (WWNs) that have been
configured with paths connecting to the local array port appear in the Unselected Paths list.
Deleting alternate paths by selecting multiple external LUs (Delete Paths) 103
5.
6.
7.
8.
In the Unselected Paths list, select ports (WWNs of the external array), and click Set. The
selected ports move to the Selected Paths list.
Click OK. The Path Setting window appears.
Ensure that deleted paths are applied to the array in the Path Setting window. You can also
change the alternate path setting in this window. For more information, see Setting alternate
paths for external LUs.
Click OK. The Path Setting window closes, and the LU Operation pane appears.
Selected rows in the Device list appear in blue italics. Specified settings appear in the Preset
list. To check setting details, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.
9. Click Apply. A confirmation message appears.
10. Click OK.
Alternative paths deleted using the Delete Paths and Path Setting window are applied to the
array, and the specified content appears in the Device list.
If errors occur during alternate path definition, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
Checking an external LU's status (LDEV Information)
After mapping an external LU as a local array internal LDEV, the external LU is available for
operations in XP External Storage, Flex Copy, and other HP products that support mapped external
LUs. Use the LDEV Information window (Figure 56 (page 105)) to check the status of mapped external
LUs.
When a failure occurs in the path between the local array and external array, and also in the
specified alternate paths, the local array recognizes the external LU as blocked (Blockade). To
restore the blocked volume, execute the Restore command on the LDEV Information window.
•
Obtaining information about external LUs
•
Restoring external LUs (Restore)
•
Displaying configuration information for external LUs (Volume Detail)
Obtaining information about external LUs
The LDEV Information window displays information about external arrays and external LUs mapped
as internal LDEVs. To display this window, select the external LU group number in the Device list,
right-click the LU you want to display in the Device list, and select LDEV Information.
104 Configuring external LUs
Figure 56 LDEV Information window
•
Vendor
External array's vendor.
•
Product
External array's product name.
•
Serial
External array's product serial number.
•
Group
External LU group and reference number of the external LU in the group.
•
Characteristic
External LU's identification number.
•
Device
External LU's device name.
•
Capacity
External LU's capacity. When the mapped external LU's emulation type is for open systems,
capacity is displayed in 512-byte blocks. When the mapped external LU's emulation type is
for mainframe systems, capacity is displayed in cylinders.
NOTE: When you use the Custom Volume Size (CVS) function to make an S-VOL for an XP
Flex Copy pair that has the same capacity as the P-VOL, set the S-VOL's capacity in blocks
or cylinders according to the emulation type.
•
LDEV list
The status of external LU mapped as internal LDEV. The following information appears:
◦
CU:LDEV: CU:LDEV number of the internal LDEV to which the external LU is mapped.
◦
Path: Number of set paths.
◦
Emulation Type: External LU's emulation type set when it was mapped.
Checking an external LU's status (LDEV Information) 105
•
◦
Capacity: External LU's capacity.
◦
Status: External LU's status. Possible values: Normal, Unknown, Blockade, Warning, and
Format. Warning indicates that some alternate paths are blocked. Format indicates the
external LU is currently being formatted.
View all LUs
Displays information about all external LUs in the LDEV list.
•
View all Volumes
When the external LU is part of a LUSE volume, displays all LDEVs that make up the LUSE
volume in the LDEV list. However, LDEVs in other external LUs are not displayed, even though
those LDEVs might be part of the LUSE volume. To check all LDEVs configuring a LUSE volume,
use the Volume Detail command (see Displaying configuration information for external LUs
(Volume Detail)).
•
Previous and Next buttons
If you select multiple external LUs in the Device list in the LU Operation pane, click Previous
to change the LDEV list to the external LU appearing just above the currently displayed LU.
Click Next to change the LDEV list to the external LU appearing just below the currently
displayed LU.
•
OK button
Closes the LDEV Information window, and returns to the LU Operation pane. Contents specified
in the LDEV Information window appear in blue italics in the Device list, and settings appear
in the Preset list.
•
Cancel button
Cancels all setting operations, closes the LDEV Information window, and returns to the LU
Operation pane.
Restoring external LUs (Restore)
Use the Restore command to restore the status of external LUs.
When errors occur in all paths between the local array and external array, the local array changes
the status of the external LU to Blockade. In this case, see Troubleshooting External Storage XP and
restore the path to the external array according to the troubleshooting instructions. Then execute
the Check Paths & Restore Vol. command to make the external LU in Blockade status usable. If the
external LU's status remains Blockade, even though you restored the path to the external array and
executed the Check Paths & Restore Vol. command, execute the Restore command from the LDEV
Information window.
NOTE: If paths between the local array and external array are not restored, the external LU
cannot be restored to a usable status, even though you execute the Restore command.
NOTE: If you set a mainframe-system emulation type (such as 3390-3) when you mapped the
external LU, and you restore the mapped LU without formatting the LU or performing the Write to
Control Blocks operation, data in the volume cannot be read correctly.
1.
2.
3.
4.
Select the LU Operation tab. The LU Operation pane appears.
In the Device tree, select the external LU group number. Information about the external LU
mapped as an internal LDEV appears in the Device list.
In the Device list, right-click the external LU you want to restore, and select LDEV Information.
The LDEV Information window appears. The LDEV list displays information about the external
LU selected in the Device list on the LU Operation pane.
Select View all LUs.
106 Configuring external LUs
5.
In the LDEV list, right-click the row of the external LU to be restored, and select Restore.
Figure 57 Shortcut menu of the LDEV Information window
The Status column in the selected external LU row changes to Restore.
6.
Click OK. The LDEV Information window closes, and the LU Operation pane appears.
Specified contents appear in blue italics in the Device list and appear in the Preset list. To
check setting details, right-click the setting in the Preset list, and select Detail. To cancel settings,
right-click the setting in the Preset list, and select Delete.
7.
8.
Click Apply. A confirmation message appears.
Click OK.
The status of the external LU set in the LDEV Information window changes to Restore (restored),
and the external LU can be used in XP Command View Advanced Edition Software or Remote
Web Console.
If errors occur when changing the external LU's status, failed settings and error codes appear
in the Preset list. To check error messages, right-click the failed setting, and select Detail.
Displaying configuration information for external LUs (Volume Detail)
To display the Volume Detail window, right-click a row with an external LU from the LDEV list in
the LDEV Information window, and select Volume Detail (Figure 57 (page 107)). If you select an
external LU that is a LUSE volume in the LDEV list, the Volume Detail window displays a list of all
LDEVs that make up the LUSE volume.
Checking an external LU's status (LDEV Information) 107
Figure 58 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
108 Configuring external LUs
a mapped volume with the former settings. For instructions, see Checking the connection status
and resuming external LU operations (Check Paths & Restore Vol.).
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 XP Command View Advanced Edition Software or 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 XP Flex Copy, XP Business Copy,
Hitachi ShadowImage for z/OS, XP Continuous Access Journal, Hitachi Universal Replicator
for z/OS, XP Continuous Access, Hitachi TrueCopy for z/OS, or XP Snapshot. However,
these commands can be executed in one of the following cases:
◦
When the XP Business Copy pair status is PSUE
◦
When the ShadowImage for z/OS™ pair status is Suspend.
◦
When the external volume is set as a pool volume (pool-VOL) and the status of that XP
Snapshot pair is PAIR
•
You cannot execute the Disconnect Subsystem ore Disconnect Volume command for external
LUs that include LDEVs for which XP Auto LUN's migration processing is in progress.
•
When executing the Disconnect Subsystem or Disconnect Volume command, the Ex-Dev. Status
column in the Device list changes to Cache Destage. Even if there is no data left in cache
memory, the displayed status remains as Cache Destage, until the Disconnect Subsystem or
Disconnect Volume command processing is complete.
•
When the Disconnect Subsystem or Disconnect Volume command is executed and all data in
cache memory is written to the external LU, the Ex-Dev. Status column in the Device list changes
to Disconnect.
The procedures of disconnecting the external volume are described as follows.
•
Disconnecting all external LUs in an external array (Disconnect Subsystem)
•
Disconnecting external LUs individually (Disconnect Volume)
Disconnecting all external LUs in an external array (Disconnect Subsystem)
1.
2.
In the LU Operation pane, select External Devices in the Device tree. Connected external arrays
appear in the Device list.
In the Device list, right-click the external array you want to disconnect from the local array,
and select Disconnect Subsystem.
Disconnecting external arrays or LUs 109
Figure 59 Disconnect array and check paths and restore volume commands
The selected external array appears in blue italics in the LU list and Device list, and appears
in the Preset list. To check details on the intended operations, right-click the setting in the Preset
list, and select Detail. To cancel settings, right-click the setting in the Preset list, and select
Delete.
3.
4.
Click Apply. A confirmation message appears.
Click OK.
The Ex-Dev. Status column in the Device list changes to Cache Destaging. When XP External
Storage finishes writing data from cache to the external LU, the Ex-Dev. Status column changes
to Disconnect.
If errors occur during disconnect operations, failed settings and error codes appear in the
Preset list. To check error messages, right-click the failed setting, and select Detail.
CAUTION: To access the external array after executing the Disconnect Subsystem command, you
must execute the Check Paths & Restore Vol. command.
Disconnecting external LUs individually (Disconnect Volume)
1.
2.
In the LU Operation pane, select an external LU group number in the Device tree. Information
about external LUs in the selected external LU group appears in the Device list.
In the Device list, right-click the external LU you want to disconnect from the local array, and
select Disconnect Volume. The selected external LU group number in the Device tree and the
selected external LU in the Device list appear in blue italics. It also appears in the Preset list.
To check details on the intended operation, right-click the row in the Preset list, and select
Detail. To cancel settings, right-click the row in the Preset list, and select Delete.
3.
110
Click Apply. A confirmation message appears.
Configuring external LUs
4.
Click OK. The Ex-Dev.Status column in the Device list changes to Cache Destaging. When XP
External Storage finishes writing data from cache to the external LU, the Ex-Dev. Status column
changes to Disconnect.
If errors occur during disconnect operations, failed operations and error codes appear in the
Preset list. To check error messages, right-click the failed operation row, and select Detail.
CAUTION: To access the external LU after executing the Disconnect Subsystem command, you
must execute the Check Paths & Restore Vol. command.
Checking the connection status and resuming external LU operations (Check
Paths & Restore Vol.)
When errors occur in the path between the local array and external array, and also in all alternate
paths, the local array changes the external LU's status to Blockade. In this case, see Troubleshooting
External Storage XP and restore the path to the external array according to the troubleshooting
procedure. Execute the Check Paths & Restore Vol. command to make the external LU in Blockade
status usable.
When executing the Check Paths & Restore Vol. command for the disconnected external LU for
which mapping settings are preserved, the defined mapping setting and the external LU's current
status are compared and checked to see if the settings match the actual status. The path status and
all other mapping configuration definitions are checked. If the external LU can be resumed as a
mapped volume as a result of the checking processing, the volume status is set to be available for
I/O operations.
Use the Check Paths & Restore Vol. command to resume using an external LU that has been
disconnected using the Disconnect Subsystem or Disconnect Volume command.
CAUTION:
After executing the Check Paths & Restore Vol. command, click the Refresh button
( ) on the XP Command View Advanced Edition Software or Remote Web Console main pane
to update the information, and check the current progress status.
NOTE: If you execute the Check Paths & Restore Vol. command and the external LU is ready to
be restored as the mapped LU, the external LU is set to accept I/Os and you can resume using the
external LU as a mapped LU. However, if the external LU is not ready to be resumed, the status of
the disconnected volume remains Blockade.
The procedures of resuming the external volume are described as follows.
•
Restoring all external LUs in an external array (Check Paths & Restore Vol.)
•
Restoring external LUs individually (Check Paths & Restore Vol.)
Restoring all external LUs in an external array (Check Paths & Restore Vol.)
1.
2.
In the LU Operation pane, select External Devices in the Device tree. Physically connected
external arrays appear in the Device list.
In the Device list, right-click the external array you want to restore the connection to the local
array, and select Check Paths & Restore Vol. The selected external array appears in blue italics
in the LU list and Device list. It also appears in the Preset list.
To check setting details, right-click the setting in the Preset list, and select Detail. To cancel
settings, right-click the setting in the Preset list, and select Delete.
3.
Click Apply. A confirmation message appears.
Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.)
111
4.
Click OK.
The path status in the Path Setting pane changes to Checking. When XP External Storage
finishes checking path status and the external array can be restored, the Status column changes
to Normal. If the external array cannot be restored, the status changes to Blockade.
Restoring external LUs individually (Check Paths & Restore Vol.)
1.
2.
In the LU Operation pane, select an external LU group number in the Device tree. Information
about external LUs in the selected external LU group appears in the Device list.
In the Device list, right-click the external LU you want to resume the connection to the local
array, and select Check Paths & Restore Vol.
The selected external group number in the Device tree and the selected external LU in the
Device list appear in blue italics. Rows with operations to be performed on appear in the
Preset list. To check setting details, right-click the setting in the Preset list, and select Detail. To
cancel settings, right-click the setting in the Preset list, and select Delete.
3.
4.
Click Apply. A confirmation message appears.
Click OK.
The path status displayed in the Path Setting pane changes to Checking. When XP External
Storage finishes checking path status and the external LU can be restored, the Status column
changes to Normal. If the external array cannot be restored, the status changes to Blockade.
Restoring external LUs (LDEV Restore)
The external LU's status might be blocked (Blockade) if errors occur during the setting operation or
the volume-formatting process fails. In this case, see Troubleshooting External Storage XP and
restore the path to the external array according to the troubleshooting procedure. Then execute
the Check Paths & Restore Vol. command to make the external LU in Blockade status usable. If the
external LU's status remains Blockade, even though you restored the path to the external array and
executed the Check Paths & Restore Vol. command, execute the LDEV Restore command to restore
the volume.
NOTE: If the path between the local array and external array is not restored, you cannot restore
the external array's status to be usable, even though you execute the LDEV Restore command.
NOTE: You can also restore the external LU by executing the Restore command on the LDEV
Information window. For more information, see Restoring external LUs (Restore).
Following subsections describe the procedure of restoring external volume as follows.
•
Restoring volumes in an external array
•
Restoring volumes in a mapped external LU individually
Restoring volumes in an external array
1.
2.
In the LU Operation pane, select External Devices in the Device tree. Connected external arrays
appear in the Device list.
In the Device list, right-click the external array you want to restore all volumes in, and select
LDEV Restore.
The selected external array appears in blue italics in the Device tree and Device list. The
contents of the setting appears in the Preset list. To check setting details, right-click the setting
in the Preset list, and select Detail. To cancel the setting, right-click the setting in the Preset list,
and select Delete.
3.
112
Click Apply. A confirmation message appears.
Configuring external LUs
4.
Click OK.
For the external LUs of the selected external array, the Status column of the Device list changes
to the restored status, and the external LU can be used in XP Command View Advanced Edition
Software or Remote Web Console.
When errors occur during a status change for the external LU, the failed setting and error
code appears in the Preset list. To check the error message, right-click the failed setting, and
select Detail.
Restoring volumes in a mapped external LU individually
1.
2.
In LU Operation pane, select an external LU group number in the Device tree. Information
about the external LUs in the selected external LU group appear in the Device list.
In the Device list, right-click the external LU you want to restore, and select LDEV Restore.
The selected external LU group number and external LU appear in blue italics in the Device
tree and Device list. The contents of the setting appears in the Preset list. To check setting
details, right-click the setting in the Preset list, and select Detail. To cancel the setting, right-click
the setting in the Preset list, and select Delete.
3.
4.
Click Apply. A confirmation message appears.
Click OK.
For the external LUs of the selected external array, the Status column of the Device list changes
to the restored status, and the external LU can be used in the XP Command View Advanced
Edition Software or Remote Web Console.
When errors occur during the status change for the external LU, the failed setting and error
code appears in the Preset list. To check the error message, right-click the failed setting, and
select Detail.
Changing the cache mode setting of the external LU
You can change the cache mode of the external LU in the LU Operation pane. To change the cache
mode of the external LU, right-click the array or the external LU, select the Change Cache Mode in
the pop-up menu, and then select Enable or Disable. Data that is not written by the host (for example,
data written by XP Business Copy) is asynchronously destaged to the external array regardless of
the Cache Mode setting.
Data that is not written by the host (for example, data written by XP Business Copy) is asynchronously
destaged to the external array regardless of the Cache Mode setting.
Check the following before changing the cache mode of the external volume.
•
Whether the LU is part of a LUSE. When it constitutes a part of a LUSE, the cache mode setting
should be same among all LUs which constitute the LUSE LU.
Whether the bind mode of a Cache LUN is set. When bind mode is set, you cannot change
the cache mode from Enable to Disable. To change the cache mode to Disable, first cancel
the setting for XP Cache LUN or change the cache residency mode to the priority mode.
•
Whether the IO Suppression mode is set to Disable. When the IO Suppression mode is set to
Enable, you cannot change the cache mode from Disable to Enable.
Whether the volume is not a remote command device. When the volume is a remote command
device, you cannot change the cache mode from Disable to Enable.
The procedures for changing the cache mode of the external volume are described as follows.
•
“Changing the cache mode of all external LUs in an external array” (page 114)
•
“Changing the cache mode of an individual external LU” (page 114)
Changing the cache mode setting of the external LU
113
Changing the cache mode of all external LUs in an external array
The procedure to change the cache mode of all external volumes in an external array is as follows:
1. Log on to Remote Web Console.
2.
3.
4.
5.
6.
7.
8.
Click the XP External Storage icon (
) on the Remote Web Console main pane. The
XP External Storage pane (LU Operation pane) is displayed.
Change the session to Modify mode by clicking the modify icon. For the procedure to change
the operation mode to Modify mode, see the HP XP Remote Web Console user guide for
XP12000/XP10000 Disk Arrays and SVS 200.
Click the LU Operation tab. The LU Operation pane is displayed.
Click External Devices in the Device tree. The connected external arrays are displayed in the
Device list.
Click the array whose cache mode you want to change in the Device list, right-click to select
the Change Cache Mode command, and then select Enable or Disable. The selected array is
displayed in blue and italics in the Device tree and Device list. The contents of the selected
array are displayed in the Preset list. To check the details on the selected array, select an item
from the Preset list and right-click to select the Detail command. To cancel the setting, click the
item in the Preset list, and right-click to select the Delete command.
Click Apply on the LU Operation pane. A message asking if you want to apply the settings
to the array is displayed.
Select OK to close the message. The cache mode settings in the Preset list are applied to the
array. When an error occurs during the cache mode change of the external LU, the failed
setting is displayed in the Preset list, and an error code is displayed. To check the error
message, select the failed setting and right-click to select the Detail command.
Changing the cache mode of an individual external LU
The procedure to change the cache mode of an individual external LU is as follows:
1. Log on to the Remote Web Console.
2.
3.
4.
5.
6.
7.
8.
Click the button with the XP External Storage icon (
) on the Remote Web Console
main pane. The External Storage pane (LU Operation pane) is displayed.
Change the session to Modify. For the procedure to change the operation mode to Modify
mode, see the HP XP Remote Web Console user guide for XP12000/XP10000 Disk Arrays
and SVS 200.
Click the LU Operation tab. The LU Operation pane is displayed.
Click an external LU group number in the Device tree. The information on the external LUs in
the selected external LU group is displayed in the Device list.
Click the external LU whose cache mode you want to change in the Device list, right-click to
select the Change Cache Mode command, and then select Enable or Disable. The selected
external LU is displayed in blue and italics in the Device tree and Device list. The contents of
the setting are displayed in the Preset list. To check the details on the setting, select the setting
in the Preset list and right-click to select the Detail command. To cancel the setting, select the
setting in the Preset list, and right-click to select the Delete command.
Click Apply on the LU Operation pane. A message asking if you want to apply the settings
to the array is displayed.
Click OK to close the message.
The cache mode settings in the Preset list are applied to the array. When an error occurs during
the cache mode change of the external LU, the failed setting is displayed in the Preset list, and an
error code is displayed. To check the error message, select the failed setting and right-click to select
the Detail command.
114
Configuring external LUs
Stopping the use of paths to an external LU by specifying an external
array's WWN (Disconnect Paths)
To stop using the path between the local array and the external array by specifying the WWN
that identifies the external array's port, select the WWN tree to display the WWN list.
NOTE: The Disconnect Paths command is not for the actual disconnection of the path to the
external LU. You must confirm that some normal paths to the external LU are set, other than the
path for which you plan to execute the Disconnect Paths command.
1.
2.
3.
4.
In the LU Operation pane, select the WWN tab. The WWN tree and WWN list appear.
In the WWN tree, select the product name of the connected external array. The WWN of all
ports that are connected to the local array and are used appear in the WWN list.
In the WWN list, select WWN you want to stop using. When you select the WWN identifying
the external array's port in the list, you can stop the use of all ports of the local array connected
to the port at one time.
Right-click, and select Disconnect Paths. Selected items appear in blue italics in the WWN tree
and WWN list. The contents of the setting appears in the Preset list.
To check the setting details, right-click the setting in the Preset list, and select Detail. To cancel
the setting, right-click the setting in the Preset list, and select Delete.
5.
6.
Click Apply. A confirmation message appears.
Click OK.
Restoring paths to an external LU by specifying an external array's WWN
(Check Paths)
To restore the path between the local array and external array by specifying the WWN that
identifies the external array's port, select the WWN tree to display the WWN list.
NOTE:
1.
2.
3.
4.
The path must be in a status that can be restored.
In the LU Operation pane, select the WWN tab. The WWN tree and WWN list appear.
In the WWN tree, select the product name of the connected external array or the WWN
identifying the external array's port.
•
If you select the product name of the connected external array, all WWNs that are
connected to the local array and are used appear in the WWN list.
•
If you select the external array's WWN, connection information about the paths between
the selected WWN and local array ports appear in the WWN list.
In the WWN list, select the WWN for which you want to restore the path.
•
If you selected the product name of the connected external array in the WWN tree, select
the WWN identifying the external array's port in the WWN list. In this case, you can
restore the path of all ports of the local array connected to the WWN at one time.
•
If you selected the external array's WWN in the WWN tree, select the path between the
selected WWN and the port of the local array. In this case, you can restore the selected
path to the port of the local array individually.
Right click, and select Check Paths. Selected items appear in blue italics in the WWN tree and
WWN list. The contents of the setting appears in the Preset list.
To check the setting details, right-click the setting in the Preset list, and select Detail. To cancel
the setting, right-click the setting in the Preset list, and select Delete.
5.
6.
Click Apply. A confirmation message appears.
Click OK.
Stopping the use of paths to an external LU by specifying an external array's WWN (Disconnect Paths)
115
Changing an external array's port setting
You can change the setting of an external array's port by specifying the WWN that identifies the
external array's port in the WWN list. Use the Change Parameter pane (Figure 60 (page 116)) to
change the port setting.
Figure 60 Change Parameter pane
•
IO TOV (10-240): Timeout value for the I/O to the external LU. The value can be 10 to 240
(in second). The default value is 15.
•
QDepth (8-128): Number of Read/Write commands that can be issued (queued) to the external
LU at one time. The value can be from 8 to 128. The default value is 8.
•
Path Blockade Watch (10-180): Time period beginning when the connection of all paths to
the external LU is down and ending when the external LU is blocked. Commands from the
host are accepted until the time set for this parameter has passed. After the time has passed,
the path status becomes Blockade. The value can be from 10 to 180 (seconds). The default
value is 180.
CAUTION:
If there is no problem with the default setting, use the default setting.
CAUTION:
For the external LU used for typical I/O, set IO TOV to 15 seconds.
CAUTION:
array.
To change the setting, match the value to the recommended value for the external
To change the setting of the port identified by the WWN by specifying an external array's WWN:
1. In the LU Operation pane, select the WWN tab. The WWN tree and WWN list appear.
2. In the WWN tree, select the product name of the connected external array identifying the
external array's port. The WWNs of all the ports that are connected to the local array and
are used appear in the WWN list.
3. In the WWN list, select the port for which you want to restore the path.
4. Right click, and select Change Parameter. The Change Parameter pane appears
(Figure 60 (page 116)).
5. Change the selected port's parameter.
6. Click OK. The Change Parameter pane closes, and the LU Operation pane appears. Selected
items appear in blue italics in the WWN tree and WWN list. The contents of the setting appears
in the Preset list.
To check the setting details, right-click the setting in the Preset list, and select Detail. To cancel
the setting, right-click the setting in the Preset list, and select Delete.
7.
8.
116
Click Apply. A confirmation message appears.
Click OK.
Configuring external LUs
Stopping the use of paths to an external LU by specifying a local array's
port (Disconnect Paths)
To stop using the path between the local array and external array by specifying the port of the
local array, select the Port Operation tree. The Port Operation list appears.
1. In the LU Operation pane, select the Port Operation tab. The Port Operation tree and Port
Operation list appear.
2. In the Port Operation tree, select External (the port attribute for the external array connection).
The local array's external ports appear in the Port Operation list.
3. In the Port Operation list, right-click the port of the local array you want to stop using, and
select Disconnect Paths.
Selected items appear in blue italics in the Port tree and Port list. The contents of the setting
appear in the Preset list. To check the setting details, right-click the setting in the Preset list,
and select Detail. To cancel the setting, right-click the setting in the Preset list, and select Delete.
4.
5.
Click Apply. A confirmation message appears.
Click OK.
Restoring paths to an external LU by specifying a local array's port (Check
Paths)
To restore the path between the local array and external array by specifying the local array's port,
select the Port Operation tree. The Port Operation list appears.
NOTE:
1.
2.
3.
The path must be in a status that can be restored.
In the LU Operation pane, select the Port tab. The Port Operation tree and Port Operation list
appear.
In the Port tree, select External (the port attribute for the external array connection) or the local
array port.
•
If you select External, the local array port setting with the External attribute appears in
the Port Operation list.
•
If you select the local array port, connection information about the path between the
selected port and external array appears.
In the Port Operation list, right-click the port of the local array for which you want to restore
the path, and select Check Paths.
Selected items appear in blue italics in the Port Operation tree and Port Operation list. The
contents of the setting appear in the Preset list. To check the setting details, right-click the
setting in the Preset list, and select Detail. To cancel the setting, right-click the setting in the
Preset list, and select Delete.
4.
5.
Click Apply. A confirmation message appears.
Click OK.
Deleting external LU mappings (Delete LU)
You can start deleting external LU mappings from the LU Operation pane. To delete the external
LU mapping, select Delete LU from the shortcut menu displayed in the LU Operation pane. Although
you can use the Delete LU command to delete the mapping between an internal LDEV and external
LU, you cannot use this command to reliably delete data in the external LU or internal LDEV.
Stopping the use of paths to an external LU by specifying a local array's port (Disconnect Paths)
117
Before deleting the external LU mapping, notice if any of the following are true:
•
Whether or not the execution of any application (for example, XP RAID Manager) that is using
the command device is in progress.
If any application using an external LU command device is executing, stop the application.
•
Whether the Disconnect Subsystem or Disconnect Volumes command was executed.
All data in cache memory must be written into the mapped external LU using the Disconnect
Subsystem or Disconnect Volume command. For more information about the Disconnect
Subsystem and Disconnect Volume commands, see Disconnecting external arrays or LUs.
•
The volume is part of a LUSE volume.
•
A path is set.
•
The volume is configured as part of an XP Continuous Access, XP Continuous Access Journal,
XP Business Copy, or XP Snapshot pair.
•
The volume is set as a reserved LU for XP Business Copy or XP Auto LUN.
•
The volume is set as a pool-VOL.
If any of these conditions are true, you cannot delete the external LU mapping.
1. In the LU Operation pane, select the external LU group number in the Device tree. Information
about the external LU mapped as an internal LDEV appears in the Device list.
2. In the Device list, right-click the external LU for which you want to delete the mapping, and
select Delete LU.
Settings appear in blue italics in the Device list, and they appear in the Preset list. To check
details regarding intended changes, right-click the setting in the Preset list, and select Detail.
To cancel settings, right-click the setting in the Preset list, and select Delete.
NOTE:
3.
The maximum number of external LUs you can set at one time is 256.
Click Apply. A confirmation message appears.
If you already stopped the application, go to step 4. If you have not stopped the application,
click Cancel, stop the application, and retry the operation.
4.
5.
Click OK. A confirmation message appears.
Click Yes or No.
If you click Yes, a confirmation message appears.
If you click No, a warning message appears. To execute the Delete LU operation without
writing data in the local array cache memory to the external LU, click OK. To cancel the
operation, click Cancel. If you click OK, a confirmation message appears.
NOTE: If you click OK in response to the warning, the Delete LU operation is performed,
but data in the local array cache memory that is not yet written to the external LU might be
lost.
6.
Click OK. The external LU whose mapping is deleted is removed from the Device list.
If errors occur, failed settings and error codes appear in the Preset list. To check error messages,
right-click the failed setting, and select Detail.
118
Configuring external LUs
6 Troubleshooting NAS Blade systems that include external
arrays
If your local array is provided with a NAS package, you can configure the NAS Blade system that
includes an external array. This chapter describes procedures to stop the external array for
maintenance and recover the external array from a failure. This chapter consists of the following
sections:
•
Stopping and restarting external arrays
•
Recovery procedures for errors in external arrays
For more information about each procedure, see the following manuals:
•
For XP Business Copy, see the HP XP Business Copy user guide for XP12000/XP10000 Disk
Arrays and SVS 200.
•
For XP LUN Configuration and Security Manager Software, see the HP XP LUN Configuration
and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP
200 Storage Virtualization System.
•
For XP Continuous Access, see the HP XP Continuous Access Journal user guide for
XP12000/XP10000 Disk Arrays and SVS 200.
Stopping and restarting external arrays
Figure 61 (page 120) shows an example of a NAS Blade system configuration that includes an
external array. The procedures to stop the external array for maintenance and restart the external
array after maintenance to restore the NAS Blade system are described below, referring to
Figure 61 (page 120).
Stopping and restarting external arrays
119
Figure 61 Example of a NAS Blade system configuration that includes an external array
CAUTION: To stop the external array, execute the procedure according to the following
description. If you execute the wrong procedure, an error occurs in the NAS Blade system (for
example, the file system might be blocked or the resource group's status might become
inappropriate).
Stopping external arrays
1.
2.
3.
4.
Stop access from the client.
Stop the cluster using NAS Blade Manager.
Delete all XP Business Copy or XP Continuous Access pairs, if you created the pairs specifying
the external LU.
Stop NAS OS 1 (NAS channel adapter's OS) and NAS OS 2 using XP LUN Configuration
and Security Manager Software.
NOTE: The NAS OS can also be stopped from the SVP. To stop the NAS OS from the SVP,
contact your HP account support representative.
5.
6.
Disconnect the external array using XP External Storage. For instructions, see Disconnecting
external arrays or LUs.
Stop the external array. For instructions, see Restarting external arrays and restoring NAS
Blade systems.
Restarting external arrays and restoring NAS Blade systems
1.
2.
Turn the external array power supply on. For instructions, see Restarting external arrays and
restoring NAS Blade systems.
Confirm that the external array's status is normal.
120 Troubleshooting NAS Blade systems that include external arrays
3.
4.
5.
Execute the Check Paths & Restore Vol. command using XP External Storage to restore the
path to the external array. For instructions, see Checking the connection status and resuming
external LU operations (Check Paths & Restore Vol.).
Confirm that the connection between the local array and the external array is normal.
Start NAS OS 1 (NAS channel adapter's OS) and NAS OS 2 using XP LUN Configuration
and Security Manager Software.
NOTE: The NAS OS can also be started from the SVP. To start the NAS OS from the SVP,
contact your HP account support representative.
6.
7.
8.
If you deleted XP Business Copy or XP Continuous Access pairs as you stopped the external
array, re-create the deleted pairs.
Start the cluster using NAS Blade Manager.
Resume access from the client.
Recovery procedures for errors in external arrays
This section describes recovery procedures for when an error occurs in the NAS Blade system's
external array. The recovery procedures are described using examples as follows.
•
Errors in an external array's disk
•
Errors in a path to the external array
•
Errors in all paths to the external array
Errors in an external array's disk
Figure 62 (page 122) shows an example of when an error occurs in an external array's disk. The
situation in Figure 62 (page 122) is as follows:
•
Data itself stored in the error disk in external array 1 cannot be restored. To restore data to
the original disk after recovering the NAS Blade system, the data should have been backed
up in a disk other than the error disk.
•
Clients cannot access volumes in the error disk. Clients can only access volumes other than
the error disk.
•
The local array recognizes that the status of the file system and volume in the error disk is
blocked.
Recovery procedures for errors in external arrays
121
Figure 62 Error in an external array's disk
1.
2.
Delete all XP Business Copy or XP Continuous Access pairs, if you created pairs.
Perform the following operations on node 1:
a. Release the differential-data storage device using NAS Sync Image.
b. Delete the NFS share, CIFS share, and file system using NAS Blade Manager.
3.
Change resource group 1's execution node to node 2 using NAS Blade Manager (failover).
If resource group 1's status is Offline, this operation is not required.
4.
5.
6.
7.
Stop node 1 using NAS Blade Manager.
Restart NAS OS 1 (NAS channel adapter's OS) using XP LUN Configuration and Security
Manager Software or NAS Blade Manager.
Start node 1 using NAS Blade Manager.
Perform one of the following operations using NAS Blade Manager:
•
When resource group 1's status is Online, change resource group 1's execution node to
node 1 (failback).
•
When resource group 1's status is Offline, start resource group 1.
8.
Perform the following operations on node 2:
a. Release the differential-data storage device using NAS Sync Image.
b. Delete the NFS share, CIFS share, and file system using NAS Blade Manager.
9.
Change resource group 2's execution node to node 1 using NAS Blade Manager (failover).
If resource group 2's status is Offline, this operation is not required.
10. Stop node 2 using NAS Blade Manager.
11. Restart NAS OS 2 (NAS channel adapter's OS) using XP LUN Configuration and Security
Manager Software or NAS Blade Manager.
12. Start node 2 using NAS Blade Manager.
122
Troubleshooting NAS Blade systems that include external arrays
13. Perform one of the following operations using NAS Blade Manager:
•
When resource group 2's status is Online, change resource group 2's execution node to
node 2 (failback).
•
When resource group 2's status is Offline, start resource group 2.
14. Change the error disk in the external array to restore the external array's status.
15. Execute the Check Paths & Restore Vol. command using XP External Storage. For instructions,
see Checking the connection status and resuming external LU operations (Check Paths &
Restore Vol.).
16. Perform the following operations on node 1 and node 2:
a. Set up the differential-data storage device using NAS Sync Image.
b. Create the file system, and create the NFS share and CIFS share using NAS Blade
Manager.
17. Return the backed-up data to the external array's restored disk, if you had the backed up data
in a disk other than the error disk.
18. Recreate the XP Business Copy and XP Continuous Access pairs.
Errors in a path to the external array
Figure 63 (page 123) shows an example of when an error occurs in a path between the local array
and an external array. In Figure 63 (page 123), an error occurs in the path between the local array
and external array 1; however, the path between the local array and external array 2 is normal.
The situation in Figure 63 (page 123) is as follows:
•
Clients cannot access volumes in external array 1, but can access volumes in external array 2.
•
The local array recognizes that the status of all file systems and volumes in external array 1
are blocked.
Figure 63 Error in a path to the external array
Recovery procedures for errors in external arrays
123
1.
2.
3.
Restore (for example, check the cable's connection status or change the switch) the status of
the error path between the local array and external array 1.
Execute the Check Paths & Restore Vol. command using XP External Storage. For instructions,
see Checking the connection status and resuming external LU operations (Check Paths &
Restore Vol.).
Change resource group 1's execution node to node 2 using NAS Blade Manager (failover).
If resource group 1's status is Offline, this operation is not required.
4.
5.
6.
7.
8.
Stop node 1 using NAS Blade Manager.
Restart NAS OS 1 (NAS channel adapter's OS) using XP LUN Configuration and Security
Manager Software or NAS Blade Manager.
Start node 1 using NAS Blade Manager.
Perform one of the following operations using NAS Blade Manager:
•
When resource group 1's status is Online, change resource group 1's execution node to
node 1 (failback).
•
When resource group 1's status is Offline, start resource group 1.
Change resource group 2's execution node to node 1 using NAS Blade Manager (failover).
If resource group 2's status is Offline, this operation is not required.
9. Stop node 2 using NAS Blade Manager.
10. Restart NAS OS 2 (NAS channel adapter's OS) using XP LUN Configuration and Security
Manager Software or NAS Blade Manager.
11. Start node 2 using NAS Blade Manager.
12. Perform one of the following operations using NAS Blade Manager:
•
When resource group 2's status is Online, change resource group 2's execution node to
node 2 (failback).
•
When resource group 2's status is Offline, start resource group 2.
Errors in all paths to the external array
The following sections describe the recovery procedures for two examples when the error occurs
in all paths connected to the external array.
•
If each node uses a different external array
•
If both nodes use the same external array
If each node uses a different external array
In the configuration in Figure 64 (page 125), all of the NAS Blade system's user LUs are volumes
in the external array. Each node uses the volume of a different array. All of node 1's user LUs are
volumes in external array 1. Therefore, if an error occurs in the path between the local array and
external array 1, the error occurs in all paths connected from node 1 to external array 1. In this
situation, no user LU is available for node 1.
The situation in Figure 64 (page 125) is as follows:
124
•
The NAS Blade system attempts to change resource group 1's execution node to node 2
because no user LU can be used from node 1 (failover). However, node 2 cannot access
volumes in external array 1, the failover function failed, and an srmd executable error appears
as error information for resource group 1.
•
The file system's status is blocked on node 2 because of the failure of the failover of resource
group 1.
Troubleshooting NAS Blade systems that include external arrays
•
Clients cannot access volumes in external array 1, but can access volumes in external array 2.
•
The local array recognizes that the status of all file systems and volumes in external array 1
are blocked.
Figure 64 Error occurs on the path to the external array used for node 1
1.
2.
3.
4.
5.
6.
7.
8.
Restore (for example, check the cable's connection status or change the switch) the status of
the error path between the local array and external array 1.
Execute the Check Paths & Restore Vol. command using XP External Storage. For instructions,
see Checking the connection status and resuming external LU operations (Check Paths &
Restore Vol.).
Perform a forced stop operation using NAS Blade Manager for resource group 1, which
displays the status as an srmd executable error.
Stop node 1 using NAS Blade Manager.
Restart NAS OS 1 (NAS channel adapter's OS) using XP LUN Configuration and Security
Manager Software or NAS Blade Manager.
Start node 1 using NAS Blade Manager.
To release the blocked status of node 2's file system, perform the following operations:
a. Change resource group 2's execution node to node 1 using NAS Blade Manager
(failover).
b. Restart NAS OS 2 (NAS channel adapter's) using XP LUN Configuration and Security
Manager Software or NAS Blade Manager.
c. Change resource group 2's execution node to node 2 (failback).
Start resource group 1 on node 1 using NAS Blade Manager.
If both nodes use the same external array
In the configuration in Figure 65 (page 126), all of the NAS Blade system's user LUs are volumes
in the external array. Only one external array is connected to the local array. Also, only one path
Recovery procedures for errors in external arrays
125
is set between the local array and external array. In this case, if an error occurs in the only set
path, none of the volumes in the external array can be used.
NOTE: In the configuration in Figure 65 (page 126), HP recommends setting alternate paths to
prevent the NAS Blade system from being blocked because of the path failure. For more information,
see Alternate paths.
The situation in Figure 65 (page 126) is as follows:
•
None of the user LUs can be used from node 1 or node 2.
•
Clients cannot access volumes.
•
The local array recognizes that the status of all file systems and volumes are blocked.
Figure 65 If both nodes use the same external array
1.
2.
3.
4.
5.
6.
7.
126
Restore (for example, check the cable's connection status or change the switch) the status of
the error path between the local array and external array 1.
Execute the Check Paths & Restore Vol. command using XP External Storage. For instructions,
see Checking the connection status and resuming external LU operations (Check Paths &
Restore Vol.).
Perform the forced stop operations using NAS Blade Manager for resource group 1 and
resource group 2.
Stop the cluster using NAS Blade Manager.
Restart NAS OS 1 and NAS OS 2 (NAS channel adapter's OS) using XP LUN Configuration
and Security Manager Software or NAS Blade Manager.
Start the cluster using NAS Blade Manager.
Start resource group 1 and resource group 2 using NAS Blade Manager.
Troubleshooting NAS Blade systems that include external arrays
7 Remote command devices
This chapter describes remote command devices.
•
Overview of remote command devices
•
Notices about remote command devices
•
Mapping command devices as remote command devices
•
Using Continuous Access XP or Continuous Access XP Journal with remote command devices
Overview of remote command devices
A remote command device is a device in the local array to which a command device in the external
array is mapped.
As you send XP RAID Manager commands to a remote command device located in the local array,
you can execute those commands on the external array's command device to manage pairs in the
external array.
Figure 66 (page 127) shows an example. The OPEN host connected to the local array sends XP
RAID Manager commands for XP Business Copy or XP Continuous Access to the remote command
device. This means commands are forwarded to the command device in the external array to
operate XP Business Copy or XP Continuous Access pairs in the external array.
For more information about XP RAID Manager and command devices, see the HP XP RAID Manager
user guide.
Figure 66 Overview of remote command device
Overview of remote command devices
127
Notices about remote command devices
•
You can map command devices as remote command devices when one of the following arrays
is connected as an external array:
◦
Virtual Storage Platform subsystem
◦
Universal Storage Platform V subsystem
◦
Universal Storage Platform VM subsystem
◦
XP12000 Disk Array
◦
XP10000 Disk Array
◦
HP 200 Storage Virtualization System
◦
XP1024/XP128 Disk Array
◦
TagmaStore™ Universal Storage Platform subsystem
◦
TagmaStore™ Network Storage Controller subsystem
◦
TagmaStore™ Adaptable Modular Storage subsystem
◦
TagmaStore™ Workgroup Modular Storage subsystem
◦
Lightning 9900V series subsystem
◦
Thunder 9500V series subsystem
◦
SANRISE Universal Storage Platform subsystem
◦
SANRISE Network Storage Controller subsystem
◦
Virtual Storage Platform VP9500 subsystem
◦
H24000 subsystem
◦
H20000 subsystem
◦
SANRISE Adaptable Modular Storage subsystem
◦
SANRISE Workgroup Modular Storage subsystem
◦
SANRISE9900V series subsystem
◦
P9500 subsystem
◦
XP24000 subsystem
◦
XP20000 subsystem
◦
SANRISE9500V series subsystem
◦
SANRISE H12000 subsystem
◦
SANRISE H10000 subsystem
◦
SANRISE H1024/H128 subsystem
•
You do not need a license for XP External Storage or XP Flex Copy to map command devices
as remote command devices.
•
Remote command devices are displayed on XP External Storage's panes.
As you select an external LU group number in the Device tree on the LU Operation pane, the
information shown in Table 9 (page 128) appears.
Table 9 Information displayed in the Device column for remote command devices
128
Storage array
Information displayed in Device column of
Device list
Virtual Storage Platform subsystem
Format: “Emulation Type” + “-CM”
Remote command devices
Table 9 Information displayed in the Device column for remote command devices (continued)
Storage array
Information displayed in Device column of
Device list
Universal Storage Platform V subsystem
Example: OPEN-V-CM, OPEN-3-CM
Universal Storage Platform VM subsystem
XP12000 Disk Array
XP10000 Disk Array
HP 200 Storage Virtualization System
XP1024/XP128 Disk Array
TagmaStore™ Universal Storage Platform subsystem
TagmaStore™ Network Storage Controller subsystem
Virtual Storage Platform VP9500 subsystem
H24000 subsystem
H20000 subsystem
Lightning 9900V series subsystem
SANRISE Universal Storage Platform subsystem
SANRISE Network Storage Controller subsystem
P9500 subsystem
XP24000 subsystem
XP20000 subsystem
SANRISE9900V series subsystem
SANRISE H12000 subsystem
SANRISE H10000 subsystem
SANRISE H1024/H128 subsystem
TagmaStore™ Adaptable Modular Storage subsystem
DF600F-CM
TagmaStore™ Workgroup Modular Storage subsystem
Thunder 9500V series subsystem
SANRISE Adaptable Modular Storage subsystem
SANRISE Workgroup Modular Storage subsystem
SANRISE9500V series subsystem
•
If you access a remote command device from an OPEN host, the remote command device
reports device information about the command device, which is mapped as a remote command
device of the external array.
Device information about the command device that the remote command device reports to
the host includes:
◦
Serial number
◦
Vendor
◦
Device name
NOTE: The device name reported to the host is the same as the one displayed in the
Device column of the Device list. For the device names reported to the host, see
Table 9 (page 128).
•
Even if the status of the remote command device is normal, an error may occur when the
operations or commands are performed on the remote command device.
If an error occurs even though the status of the remote command device is normal, check the
status of the command device of the external array, not the remote command device.
Notices about remote command devices
129
•
The following are restrictions for mapping command devices as remote command devices.
Table 10 Restrictions on remote command devices
Item
Restriction
Emulation type
OPEN-V
Number of LDEVs in an external LU
1
IO Suppression mode
Disable
Cache mode
Disable
Minimum capacity
96,000 blocks (about 47 MB)
Maximum capacity
2 TB
•
XP External Storage's Discovery operation cannot identify remote command devices.
•
When an external array has a remote command device (that is, when a command device in
another external array is mapped to this external array), make sure that the remote command
device does not have the smallest LUN ID on the port in the external array.
•
You cannot execute I/Os to remote command devices.
•
You cannot set command devices to disabled on remote command devices.
•
You cannot set command devices' security on remote command devices.
•
Do not set command devices' security on the external array side for command devices mapped
as remote command devices.
•
You cannot create LUSE volumes using remote command devices.
•
You cannot use Volume Manager to create CVs in remote command devices.
•
XP Cache LUN is not available on remote command devices.
Mapping command devices as remote command devices
To map command devices in external arrays as remote command devices, see Mapping external
LUs (Add LU).
NOTE: Command devices that can be mapped as remote command devices are displayed on
XP External Storage's panes as shown in Table 9 (page 128).
When you select Discovery in the Device tree on the LU Operation pane, the external array's
WWNs appear. When you select an external array's WWN in the Device tree, information such
as OPEN-V-CM appears in the Device column of the Device list for command devices that can be
mapped. Select a command device that can be mapped, and follow the procedure in Mapping
external LUs (Add LU) to map it.
Using XP Continuous Access or XP Continuous Access Journal with remote
command devices
To use XP Continuous Access or XP Continuous Access Journal with a remote command device,
you would traditionally need two different kinds of ports: an initiator port for XP Continuous Access
or XP Continuous Access Journal, and an external port for the remote command device. However,
if you set the Initiator/External MIX mode, you can use a port as both the initiator port for XP
Continuous Access or XP Continuous Access Journal and as the external port only for remote
command device use.
Before setting the Initiator/External MIX mode, you must prepare initiator and external ports in one
port block of Standard mode. You can set the Initiator/External MIX mode on the port block
consisting of the initiator and external ports.
130 Remote command devices
Figure 67 (page 131) shows the difference between Standard and Initiator/External MIX modes.
When ports are set to Standard modes, you must connect the cables for the initiator and external
ports. However, if you set the Initiator/External MIX mode, you must connect only one cable, and
you can use that path to operate XP Continuous Access or XP Continuous Access Journal and the
remote command device.
For more information about port blocks and setting the Initiator/External MIX mode, see the HP XP
LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk
Array, HP 200 Storage Virtualization System.
Figure 67 Difference between Standard and Initiator/External MIX modes
Figure 68 (page 132) shows an example of using XP Continuous Access or XP Continuous Access
Journal with a remote command device. In Figure 68 (page 132), local array 1 functions as the
MCU of XP Continuous Access or XP Continuous Access Journal, and at the same time it functions
as the local array of the remote command device. Local array 2 functions as the RCU of XP
Continuous Access or XP Continuous Access Journal, and at the same time it functions as the
external array of the remote command device. In this case, setting the XP Continuous Access or
XP Continuous Access Journal pair and setting the remote command device are both done using
the port of the Initiator/External MIX mode. As this example shows, you only need to connect one
cable to one of the ports set to Initiator/External MIX mode, which means that you do not need to
connect cables to each port of different port attributes.
Using XP Continuous Access or XP Continuous Access Journal with remote command devices
131
Figure 68 Using XP Continuous Access or XP Continuous Access Journal with remote command
devices
Using Initiator/External MIX mode
This section describes the procedure to use Initiator/External MIX mode and the procedure to stop
using Initiator/External MIX mode.
To use Initiator/External MIX mode:
1. Prepare the initiator ports of the Standard mode and external ports of the Standard mode in
one port block.
For the procedure to set the port attribute to initiator, see the HP XP Continuous Access user
guide for XP12000/XP10000 Disk Arrays and SVS 200 or the HP XP Continuous Access
Journal user guide for XP12000/XP10000 Disk Arrays and SVS 200.
For the procedure to set the port attribute to external, see Setting a local array's port attributes.
2.
Set the Initiator/External MIX mode to the port block consisting of the initiator ports of the
Standard mode and external ports of the Standard mode.
For the procedure to set the Initiator/External MIX mode, see the HP XP LUN Configuration
and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP
200 Storage Virtualization System.
3.
4.
Connect the cable to the port, and connect an array to be used as an MCU and local array
and an array to be used as an RCU and external array.
Map the command device as the remote command device.
NOTE: Only the command device can be recognized when the discovery operation is
performed using the external port of the Initiator/External MIX mode.
5.
Start the XP Continuous Access or XP Continuous Access Journal operation and the remote
command device operation using the port of the Initiator/External MIX mode.
To stop using Initiator/External MIX mode:
1. Stop the XP Continuous Access and XP Continuous Access Journal copy processing and
operation.
132
Remote command devices
2.
3.
4.
Stop accessing the remote command device.
Delete the remote command device mapping.
Change the port block setting from Initiator/External MIX mode to Standard mode.
For the procedure to change the port block setting, see the HP XP LUN Configuration and
Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200
Storage Virtualization System.
Restrictions on Initiator/External MIX mode
Restrictions on Initiator/External MIX mode are:
•
Restrictions on High Speed mode are also restrictions on Initiator/External MIX mode. For
High Speed mode the restrictions, see the HP XP LUN Configuration and Security Manager
user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization
System.
•
A point-to-point connection is not available.
•
You cannot set Initiator/External MIX mode on external ports of the Standard mode that have
already been used to map the external LUs. You cannot set Standard mode on the port of the
Initiator/External MIX mode that has already been used to map the remote command device.
You must delete the external volume's mapping, and then change the port mode's setting.
•
Using a port of the Initiator/External MIX mode, the command device of the external array
can only be recognized by the discovery operation and mapped. Other volumes cannot be
recognized by the discovery operation or mapped using the port of the Initiator/External MIX
mode.
Using XP Continuous Access or XP Continuous Access Journal with remote command devices
133
8 Troubleshooting XP External Storage
If you have a problem with the XP Command View Advanced Edition Software computer or XP
Command View Advanced Edition Software or Remote Web Console software, see the HP XP
Command View Advanced Edition Software user guide for XP Disk Arrays or the HP XP Remote
Web Console user guide for XP12000/XP10000 Disk Arrays and SVS 200 for troubleshooting
information.
For additional assistance, contact your HP account support representative.
Table 11 (page 134) provides general troubleshooting instructions for XP External Storage operations.
Table 11 General XP External Storage troubleshooting
Error
Corrective action
The XP Command View Advanced Edition Correct the error and retry the operation.
Software management station or Remote The reason for the error could be one of the following:
Web Console cannot access the external
• The Fibre Channel (FC) switch is off or an error occurred in the switch.
LU.
• The FC cables are not properly connected.
• The configuration of the external array changed, and the external LU was deleted.
• An error occurred with the external LU in the external array.
• The path in the external array changed.
• The port attribute of the local array is no longer external.
• The topology information is not set correctly.
The external LU cannot be mapped as an Correct the error and retry the operation.
internal LDEV of the local array.
The source of the error could be any of the following:
• The number of mapped external LUs exceeds the maximum number (15,360 LUs
for XP12000 or 8,192 LUs for XP10000/SVS200) available for the local array.
• There are not enough CU:LDEV numbers available for external LU mapping.
The path to the external LU is blocked.
1. The errors listed in the first row of this table (Error: The XP Command View Advanced
Edition Software management station or Remote Web Console cannot access the
external LU) could be the reason for this error. Check the reasons in the first row,
correct the error, and retry the operation. If the error persists, try step 2b.
2. Try the following procedures. If they do not work and the path is not restored,
contact your HP account support representative.
a. Verify that the cable between the local array and external array is connected
properly.
b. If the cable between the local array and external array is connected properly,
disconnect and reconnect it. After 30 seconds, check the path status from XP
Command View Advanced Edition Software or Remote Web Console.
The status appearing in the Ex-Dev. Status The LDEV's status cannot be determined. This occurs when the LDEV does not exist.
column is Normal, but the status
The reason for the error could be:
appearing in the LDEV Status is Unknown. • The LDEV was been created when the volume was mapped.
• The LDEV in the external LU was deleted by the Volume Manager function.
If LDEV Status becomes Unknown by any reason other than above, contact you
HP account support representative.
The path status that requires the action
appears in the Alternate Path list on the
Path Setting window (see Setting alternate
paths for external LUs).
The following rows describe path status values displayed in the Alternate Path list and
corrective actions for each status value. See Notes on connecting external arrays for
notes on connection settings and examples of recovery procedures, and then take the
corrective action.
Unknown
134
Troubleshooting XP External Storage
Status: The path status is unknown.
Table 11 General XP External Storage troubleshooting (continued)
Error
Corrective action
Corrective action: The path status cannot
be identified. Contact your HP account
support representative.
Blockade
Status: The external port is blocked.
Corrective action: The external port is
blocked because of the microcode or
package replacement or some other factor.
Check the local array's status. If you cannot
restore the path, contact your HP account
support representative.
External device setting changed
Status: The external array's configuration
changed. For example, the path definition
was deleted, or the external array itself was
replaced by another device.
Corrective action: The external array's port
is recognized. See the internal array's
documentation, and check if the operation
that changes the mapped device's setting
information has not been performed.
LDEV size reduced
Status: The external array's volume
capacity setting changed (was reduced).
Corrective action: Check the volume
capacity of the external array's LU. Execute
the Delete LU operation, and retry the Add
LU operation.
Not ready
Status: The reply from the external array
was NOTREADY. The external array's drive
is spinning up, or the external array's
device is being formatted.
Corrective action: The path cannot be used
to access the external array. Check the
external array's status. If you cannot restore
the path, contact your HP account support
representative.
Illegal request
Status: The reply from the external array
was ILLEGALREQUEST. The command
cannot be executed to the external array's
device. Data protection might be set on the
external array's device.
Corrective action: The external array's port
is recognized. Check the external array's
setting. If you cannot restore the path,
contact your HP account support
representative.
Command aborted
Status: The reply of the external array was
ABORTEDCOMMAND. An error might
have occurred on the external array side.
Corrective action: The port of the external
array is recognized. Check the external
array's setting and the condition of the
connection to the external array (for
example, cables or switches). If you cannot
restore the path, contact your HP account
support representative.
135
Table 11 General XP External Storage troubleshooting (continued)
Error
Corrective action
Busy
Status: The external array's status is BUSY.
Corrective action: The external array's port
is still recognized. Check the external
array's settings and the load on the
external array (for example, check whether
the configuration assigns too much load on
the external array). If you cannot restore
the path, contact your HP account support
representative.
LDEV reserved
Status: The external array's status is
Reserved. You cannot access the external
array's device from the local array.
Corrective action: Remove the Reserve
status on the external array's device.
Response error
Status: The external array's status is
Blocked due to an abnormal reply
(Response). You might not be able to
access the external array's device, or data
protection might be set on the external
array's device.
Corrective action: The external array's port
is recognized. Check the external array's
setting and status. If you cannot restore the
path, contact your HP account support
representative.
Initiator port
Status: The external array (for example, XP)
port attribute changed to Initiator.
Corrective action: Set the external array's
port attribute back to target. If you cannot
restore the path, contact your HP account
support representative.
RCU target port
Status: The port attribute of the external
array changed to RCU target.
Corrective action: Set the port attribute of
the external array to Target. If you cannot
restore the path, contact your HP account
support representative.
Unknown port
Status: The external array's port attribute
is unknown.
Corrective action: The external array's port
is recognized. Check the condition of the
connection (for example, cables and
switches) to the external array. If you
cannot restore the path, contact your
HP account support representative.
Cannot detect port
136
Troubleshooting XP External Storage
Status: The path was removed or the
external array's port cannot be found.
There is a problem with the connection to
Table 11 General XP External Storage troubleshooting (continued)
Error
Corrective action
the external array. The following are
possible causes:
• The fibre cable is not connected
properly.
• The topology setting between the
external and target ports does not
match.
• Because security is set on the port, the
external array's device cannot be
recognized from the local array.
• If the external array is connected
through switches, the switches' settings
might not be appropriate.
Corrective action: Check the condition of
the connection to the external array. If you
cannot restore the path, contact your
HP account support representative.
Internal error
Status: A program error occurred, or there
is a logical contradiction.
Corrective action: Contact your HP account
support representative.
Timeout
Status: Processing was retried because an
abnormal reply (Response) was returned,
but processing has stopped due to a
timeout.
Corrective action: The external array's port
of is recognized. Check the condition of
the connection (for example, cables and
switches) to the external array. If you
cannot restore the path, contact your
HP account support representative.
Target error
Status: An error, such as blockade of the
controller, was found in the external array's
port.
Corrective action: Check the status of the
external array's ports. If you cannot restore
the path, contact your HP account support
representative.
Unavailable
Status: The reply from the external array
was Unavailable. The external array
requested a change to the connected port.
When the status becomes Unavailable, the
primary path changes to the alternate path
that is in Standby status. When the primary
path changes, the path status becomes
Normal.
Corrective action: If the path does not
change properly, check the external array's
status. If you cannot restore the path,
contact your HP account support
representative.
Backoff
Status: The reply from the external array
was Backoff. The path status is Waiting for
Recovery because a temporary error
occurred in the external array's volume.
137
Table 11 General XP External Storage troubleshooting (continued)
Error
Corrective action
Even if the primary path's status becomes
Backoff, the primary path does not change
to the alternate path immediately. After
error recovery, the status becomes Normal.
Corrective action: If you cannot recover the
status from the error, the path status
changes to another status. Take the
corrective action for the new path status. If
you cannot restore the path, contact your
HP account support representative.
Device check error
Status: The target volume in the external
subsystem is not accessible, even though
the external volume was mapped.
Corrective action: Check the status of the
target volume in the external subsystem. If
the volume is not in the normal status,
restore the volume. If the volume is not
formatted, format the volume.
Medium error
Status: The target volume in the external
subsystem has become inaccessible.
Corrective action: Check the status of the
target volume in the external subsystem. If
the volume is not in the normal status,
restore the volume. If the volume is not
formatted, format the volume.
The Discovery operation cannot be
performed.
Correct the error and retry the operation.
The source of the error could be one of the following:
• XP Command View Advanced Edition Software or Remote Web Console is not in
Modify mode.
• The local array port and external array port are not connected using FC cables.
• Port security is improperly set on the external array.
• The status of the device in the external array is not Normal.
• The external array is not connected to a local array port set to External.
• The external LU capacity is insufficient (less than 46.86 MB).
• The cable to the switch is not properly connected.
• The zoning for the switch is not set properly.
If none of these correct the problem, disconnect and then reconnect the cable between
the local array and external array. After 30 seconds, retry the operation.
The external LU is blocked.
Correct the error and retry the operation. The source of the error could be any one of
the following:
• All set paths are blockaded (or not connected).
• The external LU's attribute is not set to Read/Write.
• The external LU is blockaded by an error.
The Check Paths & Restore Vol. command
) on the XP Command View Advanced Edition Software or Remote
has executed and you have waited more Click Refresh (
Web
Console
pane
to update the displayed information.
than 10 minutes, but the device's status
does not change from Checking.
If the device status remains Checking, even though you updated the information,
execute the Check Paths & Restore Vol. command again. If the problem persists despite
retrying, contact your HP account support representative.
138
Troubleshooting XP External Storage
Table 11 General XP External Storage troubleshooting (continued)
Error
Corrective action
The Disconnect Subsystem or Disconnect
) on the XP Command View Advanced Edition Software or Remote
Volume command has executed, but the Click Refresh (
progress status information is not updated. Web Console pane to update the displayed information. If the progress information
for the Cache Destage status is not updated, even though you updated the information
contact your HP account support representative.
NOTE: The time required to write of data from cache to the external LU (destaging
processing) depends on the volume capacity (more time is required for a larger volume
than a smaller one). The processing speed is about 20 MB/s. However, processing
speed depends on the external array's performance and status.
The message INTERVENTION
The device status is currently changing. Please wait for a while, and then check the
REQUIRED is issued to the mainframe host device status again. When the transition of the device status completes normally, the
device can be used immediately. If the device is blocked as a result of the device
as the device status.
status transition, see the description for The external LU is blocked error in this table
for corrective action.
The message DEVICE ERROR is issued See the description for The external LU is blocked error in this table for the corrective
to the mainframe host as the device status. action.
Calling HP technical support
If you need to call HP technical support, be sure to provide as much information about the problem
as possible. Include the circumstances surrounding the error or failure, the XP12000/XP10000
Disk Array configuration information saved in the floppy disk(s) by the FD Dump Tool, the exact
content of any messages displayed on the Remote Web Console, and the severity levels and
reference codes displayed on the Status tab of the Remote Web Console main pane.
Calling HP technical support
139
9 Support and other resources
Related documentation
The following documents provide related information:
•
HP XP glossary
•
HP XP Snapshot XP user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200
Storage Virtualization System
•
HP XP Auto LUN user guide: HP XP12000 Disk Array, HP XP10000 Disk Array
•
HP Business Copy XP user guide for XP128/XP1024 Disk Arrays
•
HP Cache LUN XP user guide for XP1024/XP128 Disk Arrays
•
HP XP Continuous Access Journal user guide: HP XP12000 Disk Array, HP XP10000 Disk
Array, HP 200 Storage Virtualization System
•
HP XP Continuous Access user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP
200 Storage Virtualization System
•
HP Flex Copy XP user guide
•
HP XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP
XP10000 Disk Array, HP 200 Storage Virtualization System
•
HP Array Configuration Utility User Guide (for HP Modular Smart Arrays)
You can find these documents on the HP Manuals website:
http://www.hp.com/support/manuals
In the Storage section, click Storage Software and then select a product.
HP technical support
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
•
Product model names and numbers
•
Technical support registration number (if applicable)
•
Product serial numbers
•
Error messages
•
Operating system type and revision level
•
Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber’s Choice for Business website:
http://www.hp.com/go/e-updates
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
140 Support and other resources
HP websites
For additional information, see the following HP websites:
•
http://www.hp.com
•
http://www.hp.com/go/storage
•
http://www.hp.com/support/manuals
•
http://www.hp.com/storage/spock
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, send a message to
storagedocs.Feedback@hp.com. All submissions become the property of HP.
HP websites
141
A Notes on connecting external arrays
Connecting Thunder 9500V subsystems
System parameters for connecting Thunder 9500V subsystems
Table 12 (page 142) explains whether to specify system parameters when making settings for ports
on the Thunder 9500V subsystem.
Table 12 System parameter settings (Thunder 9500V subsystems)
Pane name
Parameter
System Startup Settings
Start Attribute
Parameter setting
• Single Mode
Specify this parameter when the Thunder 9500V subsystem
is in the one-controller configuration.
• Dual Active Mode
Specify this parameter when the Thunder 9500V subsystem
is in the two-controller configuration.
NOTE:
used.
• Hot Stand-By Mode
Do not specify this parameter.
Common 1
Delay Planned Shutdown
You can either specify this parameter or omit specifying this
parameter.
OPTION 1
SCSI Fibre Channel
Common Options
You can either specify this parameter or omit specifying this
parameter.
OPTION 2
SCSI Fibre Channel
Common Options
You can either specify this parameter or omit specifying this
parameter.
Data Striping
Operation if the processor Set this parameter to Reset of occurred.
failure occurs
Inquiry Setting
Command Queuing Mode Set this parameter to ON.
Port Type
Controller Option
142
Be sure to specify that Data Share Mode will be
Notes on connecting external arrays
Vendor ID
Keep this parameter as HITACHI (default), and do not
change.
Product ID
Keep this parameter as DF600F (default), and do not
change.
ROM Microprogram
Version
You can either specify this parameter or omit specifying this
parameter.
RAM Microprogram
Version
You can either specify this parameter or omit specifying this
parameter.
WEB Title
You can either specify this parameter or omit specifying this
parameter.
Reset/LIP Mode
• Reset/LIP Mode
(Signal)
You can either specify this parameter or omit specifying this
parameter.
• Reset/LIP Mode
(Process)
You can either specify this parameter or omit specifying this
parameter.
• LIP Reset Mode
You can either specify this parameter or omit specifying this
parameter.
RS232C Error Information You can either specify this parameter or omit specifying this
Outflow Mode
parameter.
Table 12 System parameter settings (Thunder 9500V subsystems) (continued)
Pane name
Host Connection Mode
Parameter
Parameter setting
Write and verify mode
Set this parameter to ON.
Host Connection Mode 1
Set this parameter to Standard Mode.
Host Connection Mode 2
Specify HISUP Mode.
NOTE:
Do not specify any other parameters.
NOTE: When using the Thunder 9500V subsystem as an external array, the following versions
are recommended. If you use a 9500V subsystem whose version is earlier than the following
versions, the SATA drive's information might not be displayed correctly.
•
For Thunder 9530V, Thunder 9520V, Thunder 9570V: version 0658 or later
•
For Thunder 9580V, Thunder 9585V: version 1658 or later
Relationship between serial number and array model of Hitachi Thunder 9500V
subsystem
When the external array is a Thunder 9500V subsystem, you can identify the subsystem model
from the serial number displayed in the Serial column in the Device list on the LU Operation pane.
Table 13 (page 143) shows the relationship between serial numbers displayed in the Serial column
and subsystem models.
Table 13 Relationship between serial numbers and subsystem models (Thunder 9500V subsystems)
Displayed serial number
Model
D600XXXX
9570V, 9520V
D60JXXXX
9530V
D60HXXXX
9580V, 9585V
NOTE:
In serial numbers, X is an arbitrary number or character.
Relationship between the WWN of the port on the Thunder 9500V subsystem and
the controller
When the external array is a Thunder 9500V subsystem, you can identify the controller (controller
0 or controller 1) from the port's WWN.
Table 14 (page 143) shows the relationship between the port's WWN and the controller.
Table 14 Relationship between ports' WWNs and controllers (Thunder 9500V subsystems)
Model
Controller
Port's WWN
9570V
Controller 0
XXXXXXXXXXXXXXX0
9530V
9520V
XXXXXXXXXXXXXXX1
Controller 1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
9580V
Controller 0
9585V
XXXXXXXXXXXXXXX0
XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
Controller 1
XXXXXXXXXXXXXXX4
Connecting Thunder 9500V subsystems
143
Table 14 Relationship between ports' WWNs and controllers (Thunder 9500V subsystems) (continued)
Model
Controller
Port's WWN
XXXXXXXXXXXXXXX5
XXXXXXXXXXXXXXX6
XXXXXXXXXXXXXXX7
NOTE: In WWNs, X is an arbitrary number or character. Ports in the same apparatus have
identical values.
Path status and examples of recovery procedures (Thunder 9500V subsystems)
Table 15 (page 144) shows examples of recovery procedures when the path status is not normal.
When the path status is not normal, see Troubleshooting External Storage XP and this table to
recover the path status. If you cannot restore the path, contact you HP account support representative.
Table 15 Path status and examples of recovery procedures (Thunder 9500V subsystems)
Path status
Examples of recovery procedures
External device setting changed
XP LUN Configuration and Security Manager Software
may have changed the LU paths' settings.
Check the LU paths' settings. If the LU paths' settings
changed, change the settings back to the ones used when
the volume was mapped. Or use XP External Storage to
perform the Delete LU operation, and perform the Add LU
operation again.
XP LUN Security Extension Software may have changed
the volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Illegal request
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
XP LUN Security Extension Software may have changed
the volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Response error
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
XP LUN Security Extension Software may have changed
the volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
144 Notes on connecting external arrays
Table 15 Path status and examples of recovery procedures (Thunder 9500V subsystems) (continued)
Path status
Examples of recovery procedures
Cannot detect port
There is a problem with the connection to the external
array. The following are possible causes:
• The fibre cable is not connected properly.
• The topology setting between the external and target
ports does not match.
• If the external array is connected through switches, the
switches' settings might not be appropriate.
Check if the fibre cable is connected properly, and use XP
LUN Configuration and Security Manager Software to set
the Fibre Channel port properly.
XP LUN Configuration and Security Manager Software
may have enabled host group security.
Check if host group security is enabled. If host group
security is enabled, disable host group security.
Connecting TagmaStore AMS and TagmaStore WMS subsystems
System parameters for connecting TagmaStore AMS and TagmaStore WMS
subsystems
Table 16 (page 145) explains whether to specify system parameters when making settings for ports
on TagmaStore AMS and TagmaStore WMS subsystems.
NOTE: When connecting to a TagmaStore AMS or TagmaStore WMS subsystem, use XP LUN
Configuration and Security Manager Software to set the data transfer speed of the
XP12000/XP10000/SVS200 external port you use to a fixed value other than Auto Negotiation.
Also, set the data transfer speed of the target port of the TagmaStore AMS or TagmaStore WMS
subsystem to the same fixed value according to the data transfer speed of the external port.
Table 16 System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems)
Pane name
Parameters
Boot Options
Start Attribute
Parameter setting
• Single Mode
Specify this parameter when the
TagmaStore AMS or TagmaStore WMS
subsystem is in the one-controller
configuration.
• Dual Active Mode
Specify this parameter when the
TagmaStore AMS or TagmaStore WMS
subsystem is in the two-controller
configuration.
Delay Planned Shutdown
You can either specify this parameter
or omit specifying this parameter.
Drive blocking mode
You can either specify this parameter
or omit specifying this parameter.
Vendor ID
Keep this parameter as HITACHI
(default), and do not change.
Product ID
Keep this parameter as DF600F
(default), and do not change.
ROM Microprogram Version
You can either specify this parameter
or omit specifying this parameter.
Connecting TagmaStore AMS and TagmaStore WMS subsystems
145
Table 16 System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems) (continued)
Pane name
System Parameter
Parameters
Parameter setting
RAM Microprogram Version
You can either specify this parameter
or omit specifying this parameter.
Option
You can either specify this parameter
or omit specifying this parameter.
Operation if the processor failure
occurs
Set this parameter to Reset of occurred.
WEB Title
You can either specify this parameter
or omit specifying this parameter.
Write and verify mode
Specify this parameter to ON for AMS
1000, AMS 500, AMS 200, and
WMS 100.
Specify this parameter to OFF for AMS
2500 and AMS 2300, and AMS
2100.
Port Options
Port Option
You can either specify this parameter
or omit specifying this parameter.
Host Connection Mode
Host Connection Mode 1
Set this parameter to Standard Mode.
Host Connection Mode 2
Do not specify any parameters.
NOTE: As for AMS 1000, AMS 500,
AMS 200, and WMS 100, do not
specify HISUP OFF mode either.
NOTE:
You can either specify or omit any other parameters.
Relationship between serial numbers in device list on the LU operation panel and
TagmaStore AMS and TagmaStore WMS subsystem models
When the external array is a TagmaStore AMS or TagmaStore WMS subsystem, you can identify
the subsystem model from the serial number displayed in the Serial column in the Device list on the
LU Operation pane.
Table 17 (page 146) shows the relationship between serial numbers displayed in the Serial column
and subsystem models.
Table 17 Relation between serial numbers and subsystem models (TagmaStore AMS and TagmaStore
WMS subsystems)
Storage subsystem
Displayed serial number
Model
AMS
87XXXXXX
AMS 2500
85XXXXXX
AMS 2300
83XXXXXX
AMS 2100
WMS
71XXXXXX
WMS 100
NOTE:
In serial numbers, X is an arbitrary number or character.
Relation between the WWN of the port on the TagmaStore AMS or TagmaStore
WMS subsystem and controller
When the external array is a TagmaStore AMS or TagmaStore WMS subsystem, you can identify
the controller (controller 0 or controller 1) from the port's WWN.
146
Notes on connecting external arrays
Table 18 (page 147) shows the relationship between the port's WWN and the controller.
Table 18 Relation between ports' WWNs and controllers (TagmaStore AMS and TagmaStore WMS
subsystems)
Model
Controller
Port's WWN
AMS 200
Controller 0
XXXXXXXXXXXXXXX0
WMS 100
Controller 1
XXXXXXXXXXXXXXX1
AMS 2100
Controller 0
XXXXXXXXXXXXXXX0
AMS 500
XXXXXXXXXXXXXXX1
Controller 1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
AMS 2300
Controller 0
AMS 1000
XXXXXXXXXXXXXXX0
XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
Controller 1
XXXXXXXXXXXXXXX4
XXXXXXXXXXXXXXX5
XXXXXXXXXXXXXXX6
XXXXXXXXXXXXXXX7
AMS 2500
Controller 0
XXXXXXXXXXXXXXX0
XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
XXXXXXXXXXXXXXX4
XXXXXXXXXXXXXXX5
XXXXXXXXXXXXXXX6
XXXXXXXXXXXXXXX7
Controller 1
XXXXXXXXXXXXXXX0
XXXXXXXXXXXXXXX1
XXXXXXXXXXXXXXX2
XXXXXXXXXXXXXXX3
XXXXXXXXXXXXXXX4
XXXXXXXXXXXXXXX5
XXXXXXXXXXXXXXX6
XXXXXXXXXXXXXXX7
NOTE: In WWNs, X is an arbitrary number or character. Ports in the same apparatus have
identical values.
Path status and examples of recovery procedure (TagmaStore AMS and TagmaStore
WMS subsystems)
Table 19 (page 148) shows the examples of recovery procedures when the path status is not normal.
When the path status is not normal, see Troubleshooting External Storage XP and this table to
recover the path status. If you cannot restore the path, contact your HP account support
representative.
Connecting TagmaStore AMS and TagmaStore WMS subsystems
147
Table 19 Path status and examples of recovery procedure (TagmaStore AMS and TagmaStore WMS
subsystems)
Path status
Examples of recovery procedures
External device setting changed
XP LUN Configuration and Security Manager Software
may have changed the LU paths' settings.
Check the LU paths' settings. If the LU paths' settings
changed, change the settings back to the ones used when
the volume was mapped. Or use XP External Storage to
perform the Delete LU operation, and perform the Add LU
operation again.
XP LUN Security Extension may have changed the volume's
access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Illegal request
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
XP LUN Security Extension may have changed the volume's
access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Response error
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
XP LUN Security Extension may have changed the volume's
access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Cannot detect port
There is a problem with the connection to the external
array. The following are possible causes:
• The fibre cable is not connected properly.
• The topology setting between the external and target
ports does not match.
• If the external array is connected through switches, the
switches' settings might not be appropriate.
Check if the fibre cable is connected properly, and use XP
LUN Configuration and Security Manager Software to set
the Fibre Channel port properly.
XP LUN Configuration and Security Manager Software
may have enabled the host group security.
Check if host group security is enabled. If host group
security is enabled, disable host group security.
148
Notes on connecting external arrays
Notes When Power Saving Feature is Used (For TagmaStore AMS Subsystem,
TagmaStore WMS Subsystem)
When the external disk array is TagmaStore AMS2500, AMS2300, or AMS2100 and the power
saving feature is used, do not access the external volume which is spinning down from the host.
When you access the external volume which is spinning down from the host, the state of the external
volume becomes Blockade.
When the state of the external volume becomes Blockade, the external volume will recover
automatically in several hours. The external volume can be recovered manually by executing the
Check Paths & Restore Vol. command.
Connecting VSP Subsystem
When you connect a VSP subsystem as the external subsystem, the local TagmaStore USP microcode
version must be 50-09-98-00/01 or higher. If the local TagmaStore USP microcode version is less
than 50-09-98-00/01, you cannot connect a VSP subsystem as the external subsystem.
When you connect an VSP subsystem as the external subsystem, you need to set the port to the
host group for the Windows hosts (host mode 0C: Windows, host mode 2C: Windows Extension).
Also, the port attribute must be the target port or the RCU target port.
Path Status and Examples of Recovery Procedure (For VSP Subsystem)
Table 20 shows the examples of the recovery procedure when the path status is not normal. When
the path status is not normal, see the troubleshooting of Universal Volume Manager and this table
to recover the path status. If you cannot restore the path, please call the Support Center.
Table 20 Path Status and Examples of Recovery Procedure (For VSP Subsystem)
Path Status
Examples of Recovery Procedure
External device setting changed
Settings of the LU paths may have been changed by LUN
Manager.
Check the settings of the LU paths. If the settings of the LU
paths have been changed, change the settings back to the
ones when the volume is mapped. Or use Universal Volume
Manager to perform the Delete Volume operation and
perform the Add Volume operation again.
The access attribute of the volume may have been changed
by Data Retention Utility. Check the access attribute of the
volume. If the volume is protected by the access attribute,
release the protection.
Illegal request
The volume may have been set as a pair volume for data
copy. Check if the volume is set as a pair volume of
ShadowImage, TrueCopy, Universal Replicator or some
other copy program. If the volume is set as a pair volume,
the volume may be protected because of the pair status.
When the volume is protected, change the pair status or
delete the pair.
The access attribute of the volume may have been changed
by Data Retention Utility. Check the access attribute of the
volume. If the volume is protected by the access attribute,
release the protection
Response error
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume of
ShadowImage, TrueCopy, Universal Replicator or some
other copy program. If the volume is set as a pair volume,
the volume may be protected because of the pair status.
When the volume is protected, change the pair status or
delete the pair.
Connecting VSP Subsystem
149
Table 20 Path Status and Examples of Recovery Procedure (For VSP Subsystem) (continued)
Path Status
Examples of Recovery Procedure
The access attribute of the volume may have been changed
by Data Retention Utility. Check the access attribute of the
volume. If the volume is protected by the access attribute,
release the protection.
Cannot detect port
There is a problem with connection to the external
subsystem. The following are possible causes:
• The fibre cable is not physically connected in the proper
way.
• The setting of the topology does not match between the
external port and the target port.
• If the external subsystem is connected through switches,
the settings for the switches may not be appropriate.
Check if the fibre cable is connected properly, and then
set the fibre channel port properly using LUN Manager.
e LUN security may have been enabled by LUN Manager.
Check if the LUN security is enabled or not. If the LUN
security is enabled, disable the LUN security.
Connecting XP24000/XP20000 Disk Arrays
When you connect an XP24000 Disk Array or XP20000 Disk Array as the external array, you
need to set the port to the host group for the Windows hosts (host mode 0C: Windows, host mode
2C: Windows Extension). Also, the port attribute must be the target port or the RCU target port.
Path status and examples of recovery procedure (for XP24000/XP20000 Disk Arrays)
Table 21 (page 150) shows the examples of the recovery procedure when the path status is not
normal. When the path status is not normal, see “Troubleshooting External Storage XP” (page 134)
and this table to recover the path status. If you cannot restore the path, call technical support.
Table 21 Path status and examples of recovery procedure (for XP24000/XP20000 Disk Arrays)
Path status
Examples of recovery procedure
External device setting
changed
Settings of the LU paths may have been changed by XP LUN Configuration and Security
Manager Software. Check the settings of the LU paths. If the settings of the LU paths have
been changed, change the settings back to the ones when the volume is mapped. Or
use XP External Storage Software to perform the Delete Volume operation and perform
the Add Volume operation again.
The access attribute of the volume may have been changed by Data Retention Utility.
Check the access attribute of the volume. If the volume is protected by the access attribute,
release the protection.
Illegal request
The volume may have been set as a pair volume for data copy. Check if the volume is
set as a pair volume of XP Business Copy Software, XP Continuous Access Synchronous,
XP Continuous Access Journal or some other copy program. If the volume is set as a pair
volume, the volume may be protected because of the pair status. When the volume is
protected, change the pair status or delete the pair.
The access attribute of the volume may have been changed by Data Retention Utility.
Check the access attribute of the volume. If the volume is protected by the access attribute,
release the protection.
Response error
150
The volume may have been set as a pair volume for data copy. Check if the volume is
set as a pair volume of XP Business Copy Software, XP Continuous Access Synchronous,
XP Continuous Access Journal or some other copy program. If the volume is set as a pair
volume, the volume may be protected because of the pair status. When the volume is
protected, change the pair status or delete the pair.
Notes on connecting external arrays
Table 21 Path status and examples of recovery procedure (for XP24000/XP20000 Disk Arrays)
(continued)
The access attribute of the volume may have been changed by Data Retention Utility.
Check the access attribute of the volume. If the volume is protected by the access attribute,
release the protection.
Cannot detect port
There is a problem with connection to the external array. The following are possible
causes:
• The fibre cable is not physically connected in the proper way.
• The setting of the topology does not match between the external port and the target
port.
• If the external array is connected through switches, the settings for the switches may
not be appropriate.
Check if the fibre cable is connected properly, and then set the Fibre Channel port
properly using XP LUN Configuration and Security Manager Software.
The LUN security may have been enabled by the XP LUN Configuration and Security
Manager Software.
Check if the LUN security is enabled or not. If the LUN security is enabled, disable the
LUN security.
Connecting XP12000/XP10000 Disk Arrays
When connecting an XP12000/XP10000 Disk Array as the external array, you need to set the
port to the host group for the Windows hosts (host mode 0C: Windows, host mode 2C: Windows
Extension).
Also, the port attribute must be the target or RCU target port.
Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)
“Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)” (page 151)
shows examples of recovery procedures when the path status is not normal. When the path status
is not normal, see “Troubleshooting External Storage XP” (page 134) and this table to recover the
path status. If you cannot restore the path, contact technical support.
Table 22 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)
Path status
Examples of recovery procedures
External device setting changed
XP LUN Configuration and Security Manager Software
may have changed the LU paths' settings.
Check the LU paths' settings. If the LU paths' settings
changed, change the settings back to the ones used when
the volume was mapped. Or use XP External Storage
Software to perform the Delete LU operation, and perform
the Add LU operation again.
Data Retention Utility may have changed the volume's
access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Illegal request
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy Software, XP Continuous Access Synchronous, XP
Continuous Access Journal, or another copy program. If
the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
Connecting XP12000/XP10000 Disk Arrays
151
Table 22 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays)
(continued)
Path status
Examples of recovery procedures
Data Retention Utility may have changed the volume's
access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Response error
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy Software, XP Continuous Access Synchronous, XP
Continuous Access Journal, or another copy program. If
the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
Data Retention Utility may have changed the volume's
access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Cannot detect port
There is a problem with the connection to the external
array. The following are possible causes:
• The fibre cable is not connected properly.
• The topology setting between the external and target
ports does not match.
• If the external array is connected through switches, the
switches' settings might not be appropriate.
Check if the fibre cable is connected properly, and use XP
LUN Configuration and Security Manager Software to set
the Fibre Channel port properly.
Data Retention Utility may have enabled LUN security.
Check if LUN security is enabled. If LUN security is
enabled, disable LUN security.
Connecting XP1024/XP128 Disk Arrays
When connecting an XP1024/XP128 Disk Array as the external array, you must set the external
array port host group for one of two types of Windows hosts (host mode 0C: Windows, host mode
2C: Windows Extension).
Also, the port attribute must be the target or RCU target port.
Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays)
“Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays)” (page 152) shows
examples of recovery procedures when the path status is not normal. When the path status is not
normal, see “Troubleshooting External Storage XP” (page 134) and this table to recover the path
status. If you cannot restore the path, contact technical support.
Table 23 Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays)
Path status
Examples of recovery procedures
External device setting changed
XP LUN Configuration and Security Manager Software
may have changed the LU paths' settings.
Check the LU paths' settings. If the LU paths' settings
changed, change the settings back to the ones used when
the volume was mapped. Or use XP External Storage to
152
Notes on connecting external arrays
Table 23 Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) (continued)
Path status
Examples of recovery procedures
perform the Delete LU operation, and perform the Add LU
operation again.
XP LUN Security Extension Software may have changed
the volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Illegal request
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
XP LUN Security Extension Software may have changed
the volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Response error
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
XP LUN Security Extension Software may have changed
the volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Cannot detect port
There is a problem with connection to the external array.
The following are possible causes:
• The fibre cable is not connected properly.
• The topology setting between the external and target
ports does not match.
• If the external array is connected through switches, the
switches' settings might not be appropriate.
Check if the fibre cable is connected properly, and use XP
LUN Configuration and Security Manager Software to set
the Fibre Channel port properly.
XP LUN Configuration and Security Manager Software
may have set LUN security.
Check if LUN security is enabled. If LUN security is
enabled, disable LUN security.
Connecting XP512/XP48 Disk Arrays
When connecting an XP512/XP48 Disk Array as the external array, you must set the port's host
mode to PC Server (0C).
Also, the port attribute must be the target or RCU target port.
Connecting XP512/XP48 Disk Arrays
153
Path status and examples of recovery procedures (XP512/XP48 Disk Arrays)
“Path status and examples of recovery procedures (XP512/XP48 Disk Arrays)” (page 154) shows
examples of recovery procedures when the path status is not normal. When the path status is not
normal, see “Troubleshooting External Storage XP” (page 134) and this table to recover the path
status. If you cannot restore the path, contact technical support.
Table 24 Path status and examples of recovery procedures (XP512/XP48 Disk Arrays)
Path status
Examples of recovery procedures
External device setting changed
XP LUN Configuration and Security Manager Software
may have changed the LU paths' settings.
Check the LU paths' settings. If the LU paths' settings
changed, change the settings back to the ones used when
the volume was mapped. Or use XP External Storage to
perform the Delete LU operation, and perform the Add LU
operation again.
Illegal request
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
Response error
The volume may have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume for XP Business
Copy, XP Continuous Access, or another copy program.
If the volume is set as a pair volume, the volume might be
protected because of the pair status. If the volume is
protected, change the pair status or delete the pair.
Cannot detect port
There is a problem with connection to the external array.
The following are possible causes:
• The fibre cable is not connected properly.
• The topology setting between the external and target
ports does not match.
• If the external array is connected through switches, the
switches' settings might not be appropriate.
Check if the fibre cable is connected properly, and use XP
LUN Configuration and Security Manager Software to set
the Fibre Channel port properly.
Hitachi SANtinel for z/OS may have set LUN security.
Check if LUN security is enabled. If LUN security is
enabled, disable LUN security.
Connecting HP 200 Storage Virtualization System as external storage
When connecting an HP 200 Storage Virtualization System (SVS200) as the external array, you
must set the SVS200 port to a host group for Windows hosts (host mode 0C: Windows or host
mode 2C: Windows Extension).
Also, the SVS200 port attribute must be “target” (for an XP External Storage connection) or “RCU
target port” (for an XP Continuous Access connection).
154 Notes on connecting external arrays
NOTE: If you are using microcode that does not support the SVS200, the SVS200 is recognized
as an XP12000 Disk Array. To recognize the connected external array as the SVS200, use the
microcode version that supports the SVS200 (which is microcode version 50-07-0X-XX/XX or
higher). If you used an earlier microcode version that does not support the SVS200 to map the
SVS200 volumes, delete the mapping setting, and then change the microcode version to the one
that supports the SVS200.
Path status and examples of recovery procedures (SVS200)
“Path status and examples of recovery procedures (SVS200)” (page 155) shows examples of the
recovery procedures when the path status is not normal. When the path status is not normal, use
“Troubleshooting External Storage XP” (page 134) and this table to recover the path status. If you
cannot restore the path, contact technical support.
Table 25 Path status and examples of recovery procedures (SVS200)
Path Status
Examples of Recovery Procedure
External device setting changed
XP LUN Configuration and Security Manager Software
might have changed the LU paths' settings.
Check the LU paths' settings. If the LU paths' settings
changed, change the settings back to the ones when the
volume was mapped. Or use XP External Storage Software
to perform the Delete LU operation, and perform the Add
LU operation again.
XP LUN Security Extension might have changed the
volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Illegal request
The volume might have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume of XP Business
Copy, XP Continuous Access, XP Continuous Access
Journal, or some other copy program. If the volume is set
as a pair volume, the volume might be protected because
of the pair status. If the volume is protected, change the
pair status or delete the pair.
XP LUN Security Extension might have changed the
volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Response error
The volume might have been set as a pair volume for data
copy.
Check if the volume is set as a pair volume of XP Business
Copy, XP Continuous Access, XP Continuous Access
Journal, or some other copy program. If the volume is set
as a pair volume, the volume might be protected because
of the pair status. If the volume is protected, change the
pair status or delete the pair.
XP LUN Security Extension might have changed the
volume's access attribute.
Check the volume's access attribute. If the volume is
protected by the access attribute, release the protection.
Connecting HP 200 Storage Virtualization System as external storage
155
Table 25 Path status and examples of recovery procedures (SVS200) (continued)
Path Status
Examples of Recovery Procedure
Cannot detect port
There is a problem with connection to the external array.
The following are possible causes:
• The fibre cable is not physically connected properly.
• The topology setting does not match between the
external and target ports.
• If the external array is connected through switches, the
switches' settings might not be appropriate.
Check if the fibre cable is connected properly, and then
set the Fibre Channel port properly using XP LUN
Configuration and Security Manager Software.
XP LUN Configuration and Security Manager Software
might have enabled LUN security.
Check if the LUN security is enabled or not. If LUN security
is enabled, disable LUN security.
Connecting EVA arrays
System parameter settings for connecting EVA arrays
When you connect an EVA array as an external array, set the system parameters of the EVA array
according to the following table. For the system parameters that are not in the following table, see
the manuals of the EVA array and set the parameters appropriately for the connecting configuration.
Table 26 System parameter settings for connecting EVA array
Parameter
Add a host
Parameter setting
Host OS
Windows
Identifying logical volumes of EVA arrays (using Characteristic 2)
When the connected external array is an EVA array, LUNs are displayed as Characteristic in XP
External Storage's panes.
If you search for logical volumes by specifying the WWN that indicates EVA Port A in the
configuration, such as in Figure 69 (page 157), 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 69 (page 157), you can identify logical volumes by referring to
Characteristic2 in XP External Storage'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.
156
Notes on connecting external arrays
Figure 69 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 microcode version.
If the array type is EVA3000/5000, the behavior of the alternate path differs between the EVA
arrays of the microcode version 4.000 or later and the EVA subsystems of the earlier microcode
versions.
To replace the EVA array's microcode, check whether the alternate path's behavior changes as a
result of changing the microcode version. If the alternate path's behavior changes, perform XP
External Storage's Delete LU operation to release the setting for the EVA array volume's mapping
before you actually replace the microcode.
See the EVA array manuals for more information how the alternate path's behavior changes.
System parameter settings for connecting Sun StorEdge 6120/6320
When you connect a Sun StorEdge 6120/6320 as an external array, set the system parameters
of the Sun StorEdge 6120/6320 according to the following table. For the system parameters that
are not in the following table, see the manuals of the Sun StorEdge 6120/6320 and set the
parameters appropriately for the connecting configuration.
Table 27 System parameter settings for connecting Sun StorEdge 6120/6320
Parameter
Parameter setting
port host
SUN
System parameter settings for connecting Sun StorageTek FlexLine 380
When you connect a Sun StorageTek FlexLine 380 as an external array, set the system parameters
of the Sun StorageTek FlexLine 380 according to the following table. For the system parameters
that are not in the following table, see the manuals of the Sun StorageTek FlexLine 380 and set
the parameters appropriately for the connecting configuration.
Table 28 System parameter settings for connecting Sun StorageTek FlexLine 380
Parameter
Parameter setting
host type
Windows Non-clustered (DMP Support)
System parameter settings for connecting Sun StorageTek 2540
When you connect a Sun StorageTek 2540 as an external array, set the system parameters of the
Sun StorageTek 2540 according to the following table. For the system parameters that are not in
Connecting EVA arrays
157
the following table, see the manuals of the Sun StorageTek 2540 and set the parameters
appropriately for the connecting configuration.
Table 29 System parameter settings for connecting Sun StorageTek 2540
Parameter
Parameter setting
host type
Windows 2K non Clustered DMP
Alternate paths for connecting Sun StorageTek V2X2
If you connect a Sun StorageTek V2X2 as an external array, specify 0 for Alternate Path when you
map external volumes. Do not add any alternate paths after you finish mapping external volumes.
Connecting EMC CLARiiON CX Series
System parameter settings for connecting EMC CLARiiON CX Series
When you connect an EMC CLARiiON CX series as an external array, set the system parameters
of the EMC CLARiiON CX series according to the following table. For the system parameters that
are not in the following table, see the manuals of the EMC CLARiiON CX series and set the
parameters appropriately for the connecting configuration.
Table 30 System parameter settings for connecting EMC CLARiiON CX Series
Parameter
Parameter setting
Initiator type
CLARiiON Open
Failover mode
2
Notes on Connecting EMC CLARiiON CX Series
RAID-0 volumes on the EMC CLARiiON CX series are not supported.
System Parameter for Connecting EMC Symmetrix Series
When you connect an EMC Symmetrix series as an external storage system, set the system
parameters of the EMC Symmetrix series according to the following table. For the system parameters
that are not in the following table, refer to the documentation of the EMC Symmetrix series and
set the parameters appropriately for the connecting configuration.
Table 31 System Parameters for Connecting EMC Symmetrix Series
Parameter
Parameter Setting
SC3 flag
Enable
SPC2 flag
Disable
System parameter settings for connecting IBM DS4000 Series
When you connect an IBM DS4000 series as an external array, set the system parameters of the
IBM DS4000 series according to the following table. For the system parameters that are not in the
following table, see the manuals of the IBM DS4000 series and set the parameters appropriately
for the connecting configuration.
Table 32 System parameter settings for connecting IBM DS4000 Series
158
Parameter
Parameter settings
host type
When alternate paths are connected to different clusters
on the DS4000 series side: Linux
Notes on connecting external arrays
Alternate Path Mode for Connecting IBM DS8000 Series
The alternate path mode for an IBM DS8000 series is Single by default. The alternate path mode
for all IBM DS8000 series connected as external Storage can be changed to Multi when System
Option Mode 566 to ON. Please call the Support Center to arrange for this mode to be set to ON
and activated.
NOTE: This System Option Mode requires minimum Microcode Version 50-09-77-00/00 (or
higher).
This mode can be changed either to ON or OFF non-disruptively.
This mode can be changed by authorized service personnel.
To immediately activate the mode, perform [Check Paths] for a V-VOL that has already been
mapped to the DS8000. For more information about [Check Paths], see “Restoring paths to an
external LU by specifying a local array's port (Check Paths)” (page 117). Note that once per hour
a device health check is automatically run which will change the path mode to reflect the setting
of Mode 566 (Single or Multi) without the need to perform [Check Paths].
CAUTION: If Check Paths is performed while ShadowImage for z/OS, FlashCopy Mirror, or XP
Flex Copy pairs are defined in the mapped volume, the Check Path operation will be rejected with
message number 605 2518. If this should occur, wait for the path mode to be automatically
changed when device health check runs instead of performing Check Paths.
The Remote Web Console may not correctly display the alternate path mode after it has changed
until you select the All Refresh and then recheck the display.
IBM V7000 Series
System parameters for connecting IBM V7000 series
When connecting an IBM V7000 series as an external storage system, set the system parameters
of the IBM V7000 series according to the following table. For system parameters that are not in
Table 33 (page 159), refer to the documentation of the IBM V7000 series and set the parameters
appropriately for the connecting configuration.
Table 33 System Parameter (IBM V7000 Series)
Parameter
Parameter Setting
host type
Generic
Notes on Connecting IBM V7000 CX Series
The model name of the IBM V7000 series is displayed as "SVC" on the Remote Web Console.
Non-HP arrays
Generally, when you connect a non-HP array as the external array, the non-HP array port must be
configured as a target attached to a Windows host. The third-party vendor should be contacted
as necessary for the technical details to accomplish this.
Connecting EVA arrays
159
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.
How to determine the required external volume capacity
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 34 (page 160) shows the
external LU's maximum usable capacity for each emulation type.
Table 34 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
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.
Figure 70 (page 161) shows the relationship of the minimum LDEV capacity, base LDEV capacity,
minimum data area capacity, base data area capacity, and control information area capacity.
160 Required volume capacity for emulation types
Figure 70 LDEV capacity
Figure 71 (page 161) shows how to determine the volume capacity using the example of the OPEN-3
case.
Figure 71 Calculating LU capacity (OPEN-3 example)
Capacity list for each emulation type
This section explains the LDEV capacity and volume capacity for each emulation type in the units
of blocks and cylinders.
Table 35 (page 162) lists the minimum data area capacity, base data area capacity, and control
information area capacity for each emulation type. For the OPEN-L emulation type, CVs cannot
be created. Therefore, the base data area capacity and minimum data area capacity for OPEN-L
emulation type are the same. For the OPEN-V emulation type, the base data area capacity is not
listed because there is no concept of the base data area capacity.
In this section, the numbers of cylinders are calculated from the following formulas.
For 3380 mainframe volumes: 1 cylinder = 1,440 blocks
For 3390 mainframe volumes: 1 cylinder = 1,740 blocks
Capacity list for each emulation type
161
Table 35 LDEV capacity information for each emulation type
Emulation type
Minimum data area capacity Base data area capacity
Control information
area capacity
blocks
cylinders
blocks
cylinders
blocks
cylinders
3380-3
72,000
50
4,808,160
3,339
10,080
7
3380-3A
72,000
50
4,808,160
3,339
10,080
7
3380-3B
72,000
50
4,808,160
3,339
10,080
7
3380-3C
72,000
50
4,808,160
3,339
10,080
7
3380-K
72,000
50
3,823,200
2,655
10,080
7
3380-KA
72,000
50
3,823,200
2,655
10,080
7
3380-KB
72,000
50
3,823,200
2,655
10,080
7
3380-KC
72,000
50
3,823,200
2,655
10,080
7
3390-3
87,000
50
5,809,860
3,339
10,440
6
3390-3A
87,000
50
5,809,860
3,339
10,440
6
3390-3B
87,000
50
5,809,860
3,339
10,440
6
3390-3C
87,000
50
5,809,860
3,339
10,440
6
3390-3R
87,000
50
5,809,860
3,339
10,440
6
3390-9
87,000
50
17,429,580
10,017
43,500
25
3390-9A
87,000
50
17,429,580
10,017
43,500
25
3390-9B
87,000
50
17,429,580
10,017
43,500
25
3390-9C
87,000
50
17,429,580
10,017
43,500
25
3390-L
87,000
50
57,002,400
32,760
40,020
23
3390-LA
87,000
50
57,002,400
32,760
40,020
23
3390-LB
87,000
50
57,002,400
32,760
40,020
23
3390-LC
87,000
50
57,002,400
32,760
40,020
23
3390-M
87,000
50
114,004,800
65,520
92,220
53
3390-MA
87,000
50
114,004,800
65,520
92,220
53
3390-MB
87,000
50
114,004,800
65,520
92,220
53
3390-MC
87,000
50
114,004,800
65,520
92,220
53
OPEN-3
72,000
—
4,806,720
—
11,520
—
OPEN-8
72,000
—
14,351,040
—
38,880
—
OPEN-9
72,000
—
14,423,040
—
38,880
—
OPEN-E
72,000
—
28,452,960
—
27,360
—
OPEN-L
71,192,160
—
71,192,160
—
10,080
—
OPEN-V
96,000
—
–
—
0
—
Table 36 (page 163) lists the base LDEV capacity, minimum LDEV capacity, maximum external LU
capacity, and number of LDEVs that can be defined for the external LU with maximum capacity.
For the OPEN-L emulation type, the base LDEV capacity and the minimum LDEV capacity are the
same because CVs cannot be created. For the OPEN-V emulation type, the base LDEV capacity
is not listed because there is no concept of the base LDEV capacity.
162
Required volume capacity for emulation types
Table 36 Volume capacity information for each emulation type
Emulation
type
Base LDEV capacity
(blocks)
blocks
Minimum LDEV capacity Maximum capacity of external Maximum
(blocks)
LU (blocks)
number
of
cylinders blocks
cylinders blocks
cylinders
LDEVs*
1
3380-3
4,818,240
3,346
82,080
57
1,207,933,920
838,843
250
3380-3A
4,818,240
3,346
82,080
57
1,207,933,920
838,843
250
3380-3B
4,818,240
3,346
82,080
57
1,207,933,920
838,843
250
3380-3C
4,818,240
3,346
82,080
57
1,207,933,920
838,843
250
3380-K
3,833,280
2,662
82,080
57
981,319,680
681,472
256
3380-KA
3,833,280
2,662
82,080
57
981,319,680
681,472
256
3380-KB
3,833,280
2,662
82,080
57
981,319,680
681,472
256
3380-KC
3,833,280
2,662
82,080
57
981,319,680
681,472
256
3390-3
5,820,300
3,345
97,440
56
1,459,586,820
838,843
250
3390-3A
5,820,300
3,345
97,440
56
1,459,586,820
838,843
250
3390-3B
5,820,300
3,345
97,440
56
1,459,586,820
838,843
250
3390-3C
5,820,300
3,345
97,440
56
1,459,586,820
838,843
250
3390-3R
5,820,300
3,345
97,440
56
1,459,586,820
838,843
250
3390-9
17,473,080
10,042
130,500
75
1,459,586,820
838,843
83
3390-9A
17,473,080
10,042
130,500
75
1,459,586,820
838,843
83
3390-9B
17,473,080
10,042
130,500
75
1,459,586,820
838,843
83
3390-9C
17,473,080
10,042
130,500
75
1,459,586,820
838,843
83
3390-L
57,042,420
32,783
127,020
73
1,459,586,820
838,843
25
3390-LA
57,042,420
32,783
127,020
73
1,459,586,820
838,843
25
3390-LB
57,042,420
32,783
127,020
73
1,459,586,820
838,843
25
3390-LC
57,042,420
32,783
127,020
73
1,459,586,820
838,843
25
3390-M
114,097,020
65,573
179,220
103
1,459,586,820
838,843
12
3390-MA
114,097,020
65,573
179,220
103
1,459,586,820
838,843
12
3390-MB
114,097,020
65,573
179,220
103
1,459,586,820
838,843
12
3390-MC
114,097,020
65,573
179,220
103
1,459,586,820
838,843
12
OPEN-3
4,818,240
-
83,520
-
1,207,934,976
-
250
OPEN-8
14,389,920
-
110,880
-
1,207,934,976
-
83
OPEN-9
14,461,920
-
110,880
-
1,207,934,976
-
83
OPEN-E
28,480,320
-
99,360
-
1,207,934,976
-
42
OPEN-K
3,674,880
-
84,960
-
940,769,280
-
256
OPEN-L
71,202,240
-
71,202,240
-
1,139,235,840
-
16
OPEN-V
–
-
96,000
-
4,294,967,296
-
1
1
*This number refers to the number of LDEVs when an external volume with maximum capacity is mapped.
Capacity list for each emulation type
163
C Adjusting volume capacity for copy pair setting
When creating an XP Business Copy or XP Flex Copy pair, the S-VOL's capacity must be the same
as the P VOL. To set a copy pair's desired volume, you might need to adjust the volume capacity.
This section describes the procedure to adjust the volume capacity.
Copying data from external arrays (using external LUs as P-VOLs)
For A, B, and C in the following description, see Figure 72 (page 164).
To adjust the volume capacity to create a pair:
1. Map the external LU (A) as an internal LDEV (B) of the local array. Ensure that the volume's
emulation type is OPEN-V.
2. Select the local array volume (C) with the same capacity as the mapped internal LDEV (B) or
a bigger capacity than the mapped internal LDEV (B). The volume's (C) emulation type must
be OPEN-V.
3. If you select the local array volume (C) with a bigger capacity than the mapped internal LDEV
(B), create the CV with the same capacity as the mapped internal LDEV (B) out of the local
array volume (C) using Volume Manager. For more information, see the HP XP LUN
Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk
Array, HP 200 Storage Virtualization System.
NOTE: When using Volume Manager to create a CV with the same capacity as the mapped
internal LDEV (B), specify the CV's capacity according to the Blocks capacity displayed in the
Capacity column on the LDEV Information pane in XP External Storage (see Checking an
external LU's status (LDEV Information)).
NOTE: To create an XP Continuous Access pair with a volume of an XP1024/XP128 Disk
Array, you might not be able to create a CV with the same capacity as the internal LDEV (B)
because Volume Manager does not allow you to specify the capacity in blocks. In this case,
you cannot create an XP Continuous Access pair.
4.
Create a copy pair.
Figure 72 Copying data from external arrays (using external LUs as P-VOLs)
Copying data to external arrays (setting external LUs as S-VOLs)
For A, B, and C in the following description, see Figure 73 (page 165).
To adjust the external LU's capacity to create a pair:
1. Map the external LU (A) as an internal LDEV (B) of the local array. Set the emulation type to
the same as the copy source volume (C).
164 Adjusting volume capacity for copy pair setting
2.
3.
Check the capacity of the internal LDEV (B) to which the external LU (A) is mapped. If the
mapped internal LDEV's (B) capacity is not same as the copy source volume (C), use Volume
Manager to create a CV with the same capacity as the copy source volume (C) out of volume
(B).
Create a copy pair.
Figure 73 Copying data to external arrays (setting external LUs as S-VOLs)
Copying data to external arrays (setting external LUs as S-VOLs)
165
Index
A
Add LU (Auto) operation, 86
Add LU operation, 83
Add LU window, 78
alternate paths
adding to multiple external LUs, 100
canceling, 98
changing, 99
defining, 19, 93, 96
deleting to multiple external LUs, 102
EVA arrays, 157
LU Operation pane, 56
Path Setting window, 93
ports, 82
priority of, 19, 23, 97
Select Paths pane, 82
switching I/O execution paths to, 21
applications, combining with XP External Storage, 37
arrays, connecting
SVS200, 154
TagmaStore, 145
Thunder 9500V, 142
XP1024/XP128, 152
XP12000/XP10000, 151
XP512/XP48, 153
arrays. See external arrays; local arrays, 9
attributes, mapping, 17
Thunder 9500V, 142
XP1024/XP128, 152
XP12000/XP10000, 151
XP512/XP48, 153
connection status, 63, 111
copy pair settings, adjusting volume capacity, 164
CU:LDEV list, 81, 86
D
Blockade status
restoring, 104, 106, 112
troubleshooting, 135
Data Retention Utility, 39
Delete LU command, 117
Device Error message, 139
Device list, 59
Device tree, 58
Disconnect Paths, 117
Disconnect Subsystem command
disconnecting external LUs, 108
powering arrays on and off, 25, 26
restrictions, 35
troubleshooting, 139
Disconnect Volume command
disconnecting external LUs, 108, 110
powering arrays on and off, 25, 26
restrictions, 35
troubleshooting, 139
Discovery operation, troubleshooting, 138
disk errors, NAS Blade system, 121
document
prerequisites, 9
related documentation, 140
documentation
HP website, 140
providing feedback, 141
C
E
Cache Mode
Auto Map window, 88
LU window, 80
remote command devices, 130
restrictions, 33
settings, 18
cache, managing, 46
capacity, required, 160
Check Paths & Restore Vol. command
powering arrays on and off, 25, 26
restoring external LUs, 111, 112
restrictions, 35
troubleshooting, 138
Check Paths, Port Operation list, 117
Check Paths, WWN list, 115
CLPR, 19, 80
Configuration File Loader, 40
connecting arrays
EVA, 156
SVS200, 154
TagmaStore, 145
emulation types
Add LU window, 79
Auto Map Setting window, 87
capacities, 31, 160
HDD types, 36
remote command devices, 130
restrictions, 31
setting, 18
errors
NAS Blade system, 121
errors, XP External Storage, 134
EVA3000/5000 arrays
connecting, 156
external arrays
A/S, 23
Add LU window, 78
compatible storage devices, 10
connection status, 63
copying data from, 164
copying data to, 164
defined, 7
B
166 Index
Device List, 59
Device list, 59
Device tree, 58
errors, NAS Blade system, 121
Fibre Channel connections, 8
mapping, 7, 17
mapping restrictions, 8, 30
NAS Blade systems, troubleshooting, 119
path errors, 123, 124
port settings, 17, 77, 116
powering on and off, 25, 26
remote command devices, 127
restarting NAS Blade system, 120
restoring external LUs, 111, 112
restoring volumes, 112
restrictions, 37
status, 104
stopping NAS Blade system, 119, 120
stopping paths, 115
SVS200, connecting, 154
system parameters, 142
system requirements, 9
external LUs
Add LU, 83
alternate paths, adding to multiple, 100
alternate paths, defining, 19, 93
alternate paths, deleting to multiple, 102
capacities, 31, 160
configuring, 75
connection status, 111
defined, 7
Delete LU command, 117
Device List, 59
disconnecting, 108
emulation type, setting, 79, 87
groups, 17
HDD types, 36
LU Operation pane, 56
mapping, 78
mapping all at once, 84
mapping multiple, 86
mapping restrictions, 17
mapping, defined, 7
maximum number of, 15
P-VOLs, 164
restoring, 106, 111, 112
restrictions, 31
S-VOLs, 164
status, 59, 104
stopping paths, 115
troubleshooting, 134
using data in, 29
Volume Detail window, 107
volume migration, 40
writing data to, 28
XP Business Copy operations, 43
XP Continuous Access Journal operations, 42
XP Continuous Access operations, 41
XP Snapshot operations, 44
External port setting, 17
F
features, 7
Filter button, 70
Flex Copy pane, 56
G
group number, 79, 87
groups, external LUs, 17
H
HDD types, 36
help
obtaining, 140
Hitachi ShadowImage for z/OS, 39
Hitachi TrueCopy for z/OS, 39
Hitachi Universal Replicator for z/OS, 39
HP
technical support, 140
HP XP Tiered Storage Manager, 7
I
I/O execution paths, switching to alternate paths, 21
Initiator/External MIX mode, 130, 132
installing XP External Storage, 16
internal LDEVs
Add LU, 83
alternate paths, 19, 93
capacity, 31, 160
configuring, 75
defined, 7
groups, 17
mapping all at once, 84
mapping external LUs, 78
mapping, defined, 7
troubleshooting, 134
Interval, 81
Intervention Required message, 139
IO Suppression mode
Auto Map Setting window, 87
LU window, 80
remote command devices, 130
restrictions, 33
settings, 18
L
LDEV Information window, 104
LDEV Restore command, 112
LDEVs
capacity, 79, 160
emulation types supported, 7
Information window, 104
See also internal LDEVs, 104
Select window, 89
status, 104
limitations
Initiator/External MIX mode, 133
remote command devices, 130
167
XP External Storage operations, 30
Linear button, 81, 84
local arrays
capacity, 160
connection status, 63
defined, 7
Fibre Channel connections, 8
mapping restrictions, 8
port settings, 17, 77
powering on and off, 25, 26
remote command devices, 127
stopping paths, 115
system requirements, 9
volume migration, 40
LU Operation pane, 56
LUs. See external LUs, 104
M
managing cache, 46
mapping
access restrictions, 8
Add LU command, 83
Add LU window, 78
all external LUs at once, 84
alternate paths, defining, 19, 93, 96
attributes, 17
defined, 7
Delete LU command, 117
deleting, 34
emulation type, setting, 18
external LUs, 17, 78
groups, 17
LU Operation pane, 56
multiple external LUs, 86
remote command devices, 128, 130
restrictions, 8, 17, 30, 37
troubleshooting, 134
VMA information, displaying, 92
migration, volume, 40
MSA
restrictions, 29, 30
Multi mode
defined, 19
example, 21
multiple storage arrays, accessing, 7
N
NAS Blade systems, troubleshooting
disk errors, 121
documentation, 119
path errors, 123, 124
restarting external arrays, 119, 120
stopping external arrays, 119, 120
O
OPEN-V
initializing data areas, 28
restrictions, 31
setting emulation type, 18, 79, 87
168 Index
P
P-VOLs, 164
panes, 56
Parallel Access Volumes
HPAV, 39
Path Setting window, 93
path status
SVS200, 155
TagmaStore subsystems, 147
Thunder 9500V Series subsystems, 144
troubleshooting, 134
XP12000/XP10000, 151
XP512/XP48, 154
paths
disconnecting, 117
errors, external arrays, 123, 124
primary, 19
restoring, 117
See also alternate paths, 80
performance, 37
Port Operation list, 73
Port Operation pane, 71
Port Operation tree, 72
ports
alternate paths, 82
Device tree, 58
external array settings, 77, 116
limitations, 30
list of, 72, 73
local array settings, 77
settings, 17, 71
stopping paths, 115
SVS200, 154
troubleshooting, 135, 136, 137
powering arrays on and off
commands, 25, 26
local, 26
prerequisites, 9
Preset list, 70, 74
primary path, 19
priority of alternate paths, changing, 97
R
Read and Write performance, 37
related documentation, 140
remote command devices
defined, 127
mapping, 130
restrictions, 130
specifications, 128
XP Continuous Access, 130
Remote Web Console
about, 7
troubleshooting, 134
restarting NAS Blade system arrays, 120
restoring
external array volumes, 112
external LU volumes, 113
external LUs, 106, 111, 112
LDEV Restore, 112
NAS Blade system arrays, 120
paths to external LUs, 115, 117
SVS200, 155
TagmaStore subsystems, 147
Thunder 9500V Series subsystems, 144
XP12000/XP10000 arrays, 151
XP512/XP48 arrays, 154
restrictions
Initiator/External MIX mode, 133
remote command devices, 130
XP External Storage operations, 30
retention term, 93
Thunder 9500V Series subsystems
path status, 144
port WWNs, 143
serial numbers and subsystem models, 143
system parameters, 142
Tiered Storage Manager, 7
troubleshooting
NAS Blade systems, 119
XP External Storage, 134
S
V
S-VOLs, 164
Select LDEV window, 89
Select Paths pane, 80, 82
settings, 16
Single mode
defined, 19
example, 22, 23
SNMP, 40
speed, 37
SSID window, 85
status
Blockade, 112
connection, 111
external LUs, 59, 104
SVS200, 155
TagmaStore subsystems, 147
Thunder 9500V Series subsystems, 144
troubleshooting, 134
WWN, 63
XP1024/XP128 arrays, 152
XP12000/XP10000 arrays, 151
XP512/XP48 arrays, 153
stopping
NAS Blade system arrays, 119, 120
stopping external LU paths, 115, 117
Subscriber's Choice, HP, 140
SVS200, 154
switching I/O execution paths to alternate paths, 21
system parameters for external arrays, 142
system requirements, 9, 15
VMA information, displaying, 92
VMA setting, 79
volume capacity
adjusting, 164
required, 160
Volume Detail window, 107
Volume Manager, 38
Volume Retention Manager, 39
Volume Security, 39
T
TagmaStore AMS subsystems
path status and recovery, 147
port WWNs, 146
serial numbers, 146
system parameters, 145
TagmaStore WMS subsystems
path status and recovery, 147
port WWNs, 146
serial numbers, 146
system parameters, 145
technical support, 141
HP, 140
U
uninstalling XP External Storage, 29
using data in external LUs, 29
W
websites
HP, 141
HP Subscriber's Choice for Business, 140
product manuals, 140
writing data to mapped external LUs, 28
WWN List, 63
WWN paths
restoring, 115
stopping, 115
WWN Tree, 62
X
XP Auto LUN
features, 7
volume migration, 40
XP Business Copy, 39, 43
XP Cache LUN, 38
XP Command View Advanced Edition Software
about, 7
troubleshooting, 134
XP Continuous Access
remote command devices, 130
XP Continuous Access external LUs, 39, 41
XP Continuous Access Journal
remote command devices, 130
XP Continuous Access Journal external LUs, 39, 42
XP Flex Copy, 7
XP RAID Manager, 93, 127
XP Snapshot, 39, 44
XP1024/XP128 arrays, connecting, 152
XP12000/XP10000 arrays, connecting, 151
XP512/XP48 arrays, connecting, 153
169
Download PDF
Similar pages