HP StorageWorks 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 StorageWorks XP External Storage operations; connecting external arrays; and using an XP12000/XP10000/SVS200 with EVA3000/50000.
Legal and notice information © Copyright 2007, 2010 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.
Contents 1 Overview of connecting external arrays .............................................. 13 XP External Storage features ....................................................................................................... 13 2 Preparing for XP External Storage operations ....................................... 17 Supported storage platforms and firmware ................................................................................... Prerequisites ..............................................
Collecting device information ........................................................................................ Deleting and remapping the external LU ......................................................................... Partitioning cache for external storage ......................................................................................... Determining the number and size of needed partitions ................................................................... Creating cache partitions ...
Changing the cache mode of all external LUs in an external array ................................................ Changing the cache mode of an individual external LU ............................................................... Stopping the use of paths to an external LU by specifying an external array's WWN (Disconnect Paths) ....................................................................................................................................
Path status and examples of recovery procedure (TagmaStore AMS and TagmaStore WMS subsystems) ..................................................................................................................... Notes When Power Saving Feature is Used (For TagmaStore AMS Subsystem, TagmaStore WMS Subsystem) ...................................................................................................................... Connecting XP24000/XP20000 Disk Arrays .............................................
Figures 1 XP External Storage concept ..................................................................................... 15 2 Example of alternate path configuration ..................................................................... 26 3 Example of alternate path configuration using two switches .......................................... 26 4 Example of incorrect alternate path configurations ....................................................... 27 5 Alternate path mode is Multi mode ...............
32 WWN list (External Devices selected in the WWN tree) .............................................. 72 33 Port tree ................................................................................................................. 74 34 Port list (External selected in Port tree) ........................................................................ 75 35 Filter window .........................................................................................................
68 Using XP Continuous Access or XP Continuous Access Journal with remote command devices ................................................................................................................ 148 69 Configuration example for which logical volumes can only be identified by characteristic ........................................................................................................ 174 70 LDEV capacity .......................................................................................
Tables 1 Storage arrays that can be connected as external arrays .............................................. 18 2 XP External Storage requirements .............................................................................. 21 3 When external LU's emulation type is OPEN .............................................................. 44 4 When external LU's emulation type is for mainframes ..................................................
29 System parameter settings for connecting EMC CLARiiON CX Series ........................... 175 30 System Parameters for Connecting EMC Symmetrix Series ........................................... 176 31 System parameter settings for connecting IBM DS4000 Series .................................... 176 32 External LU's maximum usable capacity ................................................................... 180 33 LDEV capacity information for each emulation type .......................................
1 Overview of connecting external arrays HP StorageWorks 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.
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.
Figure 1 XP External Storage concept .
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 StorageWorks products you can use with XP External Storage.
CAUTION: Before installing and enabling the hardware and microcode, see “Managing cache with external storage” on page 55 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” on page 18.
Storage array HP StorageWorks XP512/XP48 Disk Array HP StorageWorks XP256 Disk Array HP StorageWorks 200 Storage Virtualization System HP StorageWorks 3000/5000 Enterprise Virtual Array (Active/Standby and Active/Active controllers) or HP StorageWorks 4000/6000/8000 Enterprise Virtual Array (Active/Active controllers) Notes • In XP External Storage panes, the arrays appear as “512” and “48”, respectively. • Alternate paths are in Multi mode. • In XP External Storage panes, the array is a “256”.
Storage array Notes • “Lightning 99xxC series subsystem” indicates the Lightning 9910 and Lightning 9960. Lightning 9900C series subsystem • 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. A/H-6593 subsystem • In XP External Storage panes, the array is a “300”. • Alternate paths are in Multi mode.
Storage array SANRISE H10000 subsystem SANRISE H1024/H128 subsystem Notes • In XP External Storage panes, the array is a “10000”. • Alternate paths are in Multi mode. • 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.
Item Requirement Maximum number of external LUs addressable per local array port 1,024 per port • 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 StorageWorks XP Snapshot Software, the number of external LUs that can be connected is as follows: • For the XP12000: Maximum number of external LUs that can be connected Number of external LUs + Number of virtual LUs 15,360 • For the XP10
• • • • • Ports that can be set to external ports (see “External ports” on page 23) External array and LUs to map to the internal LDEVs (see “External LU to be mapped” on page 23) Configuration of external LU groups (see “External LU groups” on page 23) Configuration of external LU attributes (see “External LU attributes set by mapping” on page 24) Configuration of alternate paths (see “Alternate paths” on page 25) Each item above is explained in the following sections.
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). 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.
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.
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). Example of an alternate path configuration Figure 2 shows an example of an alternate path configuration.
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.
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 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.
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 shows an example of when the alternate path mode is Single mode and there are alternate paths in Normal and Standby status. Figure 8 shows another example of when the alternate path mode is Single mode. In Figure 8, there are alternate paths in Standby status only.
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 . 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.
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.
1. Stop read and write I/Os to the external LU that is mapped as a local array internal LDEV. 2. Perform other operations required before powering the local array off. 3. 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).
3. Perform other operations required before powering the external array off. 4. 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. Power on the external array containing the external LU that is mapped as a local array internal LDEV. 2. Execute the Check Paths & Restore Vol. command.
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. Resynchronize all HP StorageWorks XP Business Copy pairs (pairresync operations).
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 StorageWorks 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.
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.
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. 1. 2. Log in to XP Command View Advanced Edition Software or Remote Web Console.
• 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.
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 Appendix B. • If you map an external LU that is equal to or greater than 575.
Figure 12 External LU capacity is larger than the specified emulation type's basic capacity (OPEN-3 example) . Figure 13 External LU capacity is smaller than the specified emulation type's basic capacity . • 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.
To optionally initialize the LU's data area, use Volume Manager to format the LU. For instructions, see the HP StorageWorks 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.
• 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.
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.
Application HDD type FC SATA OK Not Recommended OK OK Backup OK Recommended Archive OK Recommended File operation from host (both Read and Write) File operation from host (mainly Read) Table 4 When external LU's emulation type is for mainframes Application HDD type FC SATA Not Recommended Not Recommended Not Recommended Not Recommended Not Supported Not Supported OK Not Recommended OK OK Backup OK Recommended Archive OK Recommended Database Online Transaction Processing (OLT
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 StorageWorks 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.
• 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.
• 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.
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).
Using external LUs for XP Continuous Access operations Figure 15 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 StorageWorks XP Continuous Access user guide for XP12000/XP10000 Disk Arrays and SVS 200.
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.
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). 2.
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.
For more information about XP Snapshot, see the HP StorageWorks 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.
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.
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.
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.
3. To find the path settings, right-click the external LDEV in the Device list, and select Path Setting (Figure 21). Figure 21 LU Operation pane, Path Setting option .
The Path Setting pane appears (Figure 22). 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). The LDEV Information pane appears (Figure 23). Figure 23 LDEV Information pane .
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). 3. Click Apply. 4. Click either Yes or No. If you click Yes, skip the next step. 5.
• 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 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
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 StorageWorks 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.
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). Figure 25 Partition Definition pane, Cut option . d.
Figure 26 Partition Definition pane, Paste Parity Group option . e. Click Apply. f. 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 StorageWorks XP Disk/Cache Partition user guide for XP12000/XP10000 Disk Arrays and SVS 200.
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.
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.
• 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).
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.
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.
LDEV status Description 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.
• 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.
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).
• 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.
• • • • • • • • • • • • • 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.
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.
• 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).
• • • • • • • • • • • • • • • • 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.
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.
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 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.
Icon Description 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.
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.
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.
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.
7. Use the Add LU or Auto Map Settings pane to map the external LU as an internal LDEV (see Mapping external LUs (Add LU)). 8. 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 StorageWorks XP LUN Configuration and Security Manager user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization System. 9.
5. 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.
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. • 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.
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.
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.
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.
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.
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. 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.
After automatically mapping the external LU using the Linear button, release the Linear button, and map the external LU individually (Figure 45). Figure 45 Add LU pane (mapping with the Linear button released . 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.
9. 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 the setting in the Preset list, and select Detail.
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.
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.
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.
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.
Select LDEV window Figure 49 Select LDEV window . 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.
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.
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) appears. Go to step 13. • If the SSID setting is not necessary, the LU Operation pane appears.
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.
• 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).
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. • Alternate Path list Status of alternate paths. The Alternate Path list consists of two tables.
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.
• 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.
6. Click Apply. A confirmation message appears. 7. 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.
5. In the Configured Paths table, right-click the row of the path defined as the alternate path, and select Priority Up (Figure 52). 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. 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.
3. Follow step 6 to step 8 in Defining alternate paths. 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.
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. 2. 3. 4. 5. Execute the Disconnect Paths command on the alternate path A (see 5.16). Disconnect the cable which the alternate path A uses, and connect the cable which the alternate path C uses. Cancel the configuration of the alternate path A, and add the alternate path C (see 5.5.4).
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 Paths panel, check the setting on the Path Setting panel, and then apply the setting to the array.
Icon Description 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.
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.
• 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.
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.
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.
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. Select the LU Operation tab. The LU Operation pane appears. 2.
8. 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.
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.
2. In the Device list, right-click the external array you want to disconnect from the local array, and select Disconnect Subsystem. 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.
2. 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. Click Apply.
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. In the LU Operation pane, select External Devices in the Device tree. Physically connected external arrays appear in the Device list. 2.
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.
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 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.
6. 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.
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. 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. The WWN of all ports that are connected to the local array and are used appear in the WWN list.
4. 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. Click Apply. A confirmation message appears. 6. Click OK.
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). 5. Change the selected port's parameter. 6. Click OK.
2. 3. 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.
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: The maximum number of external LUs you can set at one time is 256. 3. Click Apply.
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.
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. Stop access from the client. 2. Stop the cluster using NAS Blade Manager. 3.
6. Stop the external array. For instructions, see Restarting external arrays and restoring NAS Blade systems. Restarting external arrays and restoring NAS Blade systems 1. Turn the external array power supply on. For instructions, see Restarting external arrays and restoring NAS Blade systems. 2. Confirm that the external array's status is normal. 3. Execute the Check Paths & Restore Vol. command using XP External Storage to restore the path to the external array.
Figure 62 Error in an external array's disk . 1. Delete all XP Business Copy or XP Continuous Access pairs, if you created pairs. 2. Perform the following operations on node 1: 3. 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. 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.
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. 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.
Figure 63 Error in a path to the external array . 1. 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. 2. 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.). 3. Change resource group 1's execution node to node 2 using NAS Blade Manager (failover).
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.
Figure 64 Error occurs on the path to the external array used for node 1 . 1. 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. 2. 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.). 3.
If both nodes use the same external array In the configuration in Figure 65, 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 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.
3. Perform the forced stop operations using NAS Blade Manager for resource group 1 and resource group 2. 4. Stop the cluster using NAS Blade Manager. 5. 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. 6. Start the cluster using NAS Blade Manager. 7. Start resource group 1 and resource group 2 using NAS Blade Manager.
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.
Figure 66 Overview of remote command device .
• 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 appears.
• 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.
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.
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. 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.
4. 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.
Remote command devices
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 StorageWorks XP Command View Advanced Edition Software user guide for XP Disk Arrays or the HP StorageWorks 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.
Error Corrective action The status appearing in the Ex-Dev. Status column is Normal, but the status appearing in the LDEV Status is Unknown. 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 LDEV's status cannot be determined. This occurs when the LDEV does not exist. The reason for the error could be: • The LDEV was been created when the volume was mapped.
Error Corrective action Status: The reply of the external array was ABORTEDCOMMAND. An error might have occurred on the external array side. Command aborted 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. Status: The external array's status is BUSY.
Error Corrective action Status: The path was removed or the external array's port cannot be found. 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. Cannot detect port • Because security is set on the port, the external array's device cannot be recognized from the local array.
Error Corrective action Status: The target volume in the external subsystem has become inaccessible. Medium error 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. 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.
Error Corrective action The message DEVICE ERROR is issued to the mainframe host as the device status. See the description for The external LU is blocked error in this table for the corrective 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.
9 Support and other resources Related documentation The following documents provide related information: • HP StorageWorks XP glossary • HP StorageWorks XP Snapshot XP user guide: HP XP12000 Disk Array, HP XP10000 Disk Array, HP 200 Storage Virtualization System • HP StorageWorks XP Auto LUN user guide: HP XP12000 Disk Array, HP XP10000 Disk Array • HP StorageWorks Business Copy XP user guide for XP128/XP1024 Disk Arrays • HP StorageWorks Cache LUN XP user guide for XP1024/XP128 Disk Arrays • HP StorageWork
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. 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.
A Notes on connecting external arrays Connecting Thunder 9500V subsystems System parameters for connecting Thunder 9500V subsystems Table 12 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 Parameter setting Start Attribute Specify this parameter when the Thunder 9500V subsystem is in the one-controller configuration.
Pane name Parameter Parameter setting 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 Port Type Controller Option • 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.
Displayed serial number Model 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 shows the relationship between the port's WWN and the controller.
Path status and examples of recovery procedures (Thunder 9500V subsystems) Table 15 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.
Connecting TagmaStore AMS and TagmaStore WMS subsystems System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems Table 16 explains whether to specify system parameters when making settings for ports on TagmaStore AMS and TagmaStore WMS subsystems.
Pane name Parameters Parameter setting Write and verify mode Port Options Host Connection 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 Option You can either specify this parameter or omit specifying this parameter. Host Connection Mode 1 Set this parameter to Standard Mode. Do not specify any parameters.
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. Table 18 shows the relationship between the port's WWN and the controller.
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 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.
Path status Examples of recovery procedures 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.
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.
Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) Table 21 on page 169 shows examples of recovery procedures when the path status is not normal. When the path status is not normal, see “Troubleshooting External Storage XP” on page 151 and this table to recover the path status. If you cannot restore the path, contact technical support.
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) Table 22 on page 170 shows examples of recovery procedures when the path status is not normal.
Path status Examples of recovery procedures 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 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).
Path Status Examples of Recovery Procedure The volume might have been set as a pair volume for data copy. Response error 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.
Name found on the EVA array. You can identify the EVA array's logical volume by this World Wide LUN Name. 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.
are not in the following table, see the manuals of the Sun StorageTek FlexLine 380 and set the parameters appropriately for the connecting configuration.
in the following table, refer to the documentation of the EMC Symmetrix series and set the parameters appropriately for the connecting configuration. Table 30 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.
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.
Notes on connecting external arrays
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.
• Each emulation type has its own maximum usable capacity. Table 32 shows the external LU's maximum usable capacity for each emulation type. Table 32 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.
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 33 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.
Emulation type Minimum data area capacity Base data area capacity Control information area capacity blocks cylinders blocks cylinders blocks cylinders 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 339
Table 34 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.
Emulation type Base LDEV capacity (blocks) blocks Minimum LDEV capacity (blocks) cylinders blocks Maximum capacity of external LU (blocks) cylinders blocks cylinders Maximum number of LDEVs* 1 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 -
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. To adjust the volume capacity to create a pair: 1.
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. 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). 2. Check the capacity of the internal LDEV (B) to which the external LU (A) is mapped.
Index A Add LU (Auto) operation, 96 Add LU operation, 92 Add LU window, 86 alternate paths adding to multiple external LUs, canceling, 109 changing, 110 defining, 25, 104, 107 deleting to multiple external LUs, EVA arrays, LU Operation pane, 65 Path Setting window, ports, 91 priority of, priority of, 25, 29, 108 Select Paths pane, 90 switching I/O execution paths to, applications, combining with XP External Storage, arrays, connecting Thunder 9500V, arrays, connecting SVS200, 172 TagmaStore, 163 XP1024/XP12
Disconnect Volume command disconnecting external LUs, disconnecting external LUs, 119, 121 powering arrays on and off, powering arrays on and off, 32, 33 restrictions, 43 Discovery operation, troubleshooting, 155 disk errors, NAS Blade system, document prerequisites, 17 related documentation, documentation HP website, 157 providing feedback, E emulation types Add LU window, Auto Map Setting window, emulation types capacities, 40, 179 HDD types, 44 remote command devices, 146 restrictions, 40 setting, 24 er
external LUs alternate paths, defining, alternate paths, adding to multiple, alternate paths, defining, 25, 104 alternate paths, deleting to multiple, capacities, 40, 179 configuring, 83 connection status, defined, 13 Delete LU command, 130 disconnecting, 119 emulation type, setting, 88, 97 groups, 23 LU Operation pane, 65 mapping restrictions, mapping all at once, 93 mapping multiple, 96 mapping, defined, maximum number of, 21 P-VOLs, 185 restrictions, 40 S-VOLs, 186 status, 68, 116 stopping paths, 126 tro
local arrays capacity, 179 connection status, defined, 13 mapping restrictions, port settings, port settings, 23, 85 powering on and off, powering on and off, 31, 32 remote command devices, 143 stopping paths, 126 system requirements, 17 volume migration, 48 LU Operation pane, 65 LUs.
prerequisites, 17 Preset list, 78, 81 primary path, 25 priority of alternate paths, changing, R Read and Write performance, 45 related documentation, 157 Remote Web Console troubleshooting, remote command devices defined, 143 mapping, 146 restrictions, 146 specifications, 144 XP Continuous Access, Remote Web Console about, 13 troubleshooting, 151 restarting NAS Blade system arrays, 135 restoring external LU volumes, external LUs, external array volumes, 124 LDEV Restore, 123 NAS Blade system arrays, paths
VMA setting, 87 volume capacity adjusting, volume capacity required, 179 Volume Detail window, 119 Volume Manager, 46 Volume Retention Manager, 48 Volume Security, 48 W websites HP, 158 HP Subscriber's Choice for Business, 157 product manuals, writing data to mapped external LUs, WWN paths stopping, WWN List, 72 WWN paths restoring, 127 WWN Tree, 71 X XP Command View Advanced Edition Software about, XP Auto LUN features, 13 volume migration, XP Business Copy, 47, 52 XP Cache LUN, 47 XP Command View Advanc
