HP StorageWorks External Storage XP user guide for the XP12000, XP10000, SVS200 Part number: T1706-96010 Ninth edition: November 2007
Legal and notice information © Copyright 2007 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 About this guide ................................................................................. 11 Supported storage platforms and firmware ................................................................................... Intended audience .................................................................................................................... Prerequisites .............................................................................................................................
Using external LUs for Business Copy XP operations ................................................................ 52 Using external LUs for Snapshot XP operations ....................................................................... 53 3 Managing cache with external storage ............................................... 55 Guidelines for using cache with external storage ...........................................................................
Restoring external LUs (Restore) .......................................................................................... 119 Displaying configuration information for external LUs (Volume Detail) ...................................... 120 Disconnecting external arrays or LUs ......................................................................................... 121 Disconnecting all external LUs in an external array (Disconnect Subsystem) ..............................
Rel. btw. ser. numbs. in Dev. list on the LU Op. pane & T-Stor. AMS & T-Stor. WMS subsys. mods. ............................................................................................................................. 170 Relation btw. the WWN of the port on the TagmaStore AMS or TagmaStore WMS subsys. and contr. .............................................................................................................................. 171 Path status and examples of rec. proce.
Figures 1..External Storage XP concept .................................................................................... 17 2..Example of alternate path configuration .................................................................... 27 3..Example of alternate path configuration using two switches .......................................... 28 4..Example of incorrect alternate path configurations ...................................................... 28 5..Alternate path mode is Multi mode .............
33..Port tree ................................................................................................................ 76 34..Port list (External selected in Port tree) ........................................................................ 77 35..Filter window ......................................................................................................... 79 36..Preset Detail window (mapping operation) ................................................................ 80 37..
68..Using Continuous Access XP or Continuous Access XP Journal with remote command devices ................................................................................................................. 151 69..Configuration example for which logical volumes can only be identified by characteristic ......................................................................................................................... 181 70..LDEV capacity ..................................................................
Tables 1..Document conventions ............................................................................................. 12 2..Storage arrays that can be connected as external arrays ............................................. 20 3..External Storage XP requirements .............................................................................. 23 4..When external LU's emulation type is OPEN .............................................................. 44 5..
About this guide This document provides information about: • • • • • • • Preparing for External Storage XP operations Performing External Storage XP operations Troubleshooting NAS Blade systems that include external arrays Troubleshooting External Storage XP Connecting external arrays Using an XP12000/XP10000/SVS200 with EVA3000/50000 Configuring MSA1000/1500 Disk Arrays as external arrays Supported storage platforms and firmware Unless otherwise specified, the term array in this document refers to the fo
HP StorageWorks Business Copy XP user guide for the XP12000/XP10000/SVS200 HP StorageWorks Cache LUN XP user guide for XP12000/XP10000/SVS200 HP StorageWorks Continuous Access XP Journal user guide HP StorageWorks Continuous Access XP user guide for the XP12000/XP10000/SVS200 HP StorageWorks Flex Copy XP user guide HP StorageWorks LUN Configuration and Security Manager XP user guide for XP12000/XP10000/SVS200 • HP Array Configuration Utility User Guide (for HP StorageWorks Modular Smart Arrays) • • • • • •
NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http:// www.hp.com/support/.
About this guide
1 Overview of connecting external arrays External Storage XP realizes the virtualization of storage arrays. You can use External Storage XP to access multiple storage arrays connected by a Fibre Channel interface as if they were all one storage 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.
Figure 1 External Storage XP concept External Storage XP user guide for the XP12000, XP10000, SVS200 17
Overview of connecting external arrays
2 Preparing for External Storage XP operations This chapter describes requirements, preparations, and notes for External Storage XP. This chapter also describes the HP StorageWorks products you can use with External Storage XP. System requirements External Storage XP operations involve the local array, a storage array used as an external array, and the licensed External Storage XP feature enabled on Command View XP or XP Remote Web Console.
Storage arrays that can be connected as external arrays Table 2 lists storage arrays that can be connected as external arrays. Notes about the appearance of each storage array in this document and in External Storage XP panes are also listed. Table 2 Storage arrays that can be connected as external arrays Storage array Notes HP StorageWorks XP12000 Disk Array • In External Storage XP panes, the array appears as “12000”.
Storage array Notes • In External Storage XP panes, the array appears as “AMS”. • Alternate paths are in Single mode. TagmaStore™ Workgroup Modular Storage subsystem • In this user guide, the array appears as “TagmaStore™ WMS subsystem”. • In External Storage XP panes, the array appears as “NSC”. • Alternate paths are in Single mode. Lightning 9900V series subsystem • “Lightning 99xxV series subsystem” indicates the Lightning 9970V and Lightning 9980V.
Storage array Notes • In this user guide, the arrays appear as “SANRISE9900V subsystem”. • In External Storage XP 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 External Storage XP panes, the arrays appear as “9500V”. • Alternate paths are in Single mode.
Contact your HP account support representative for the latest external array and FC switch support matrix. External Storage XP requirements Table 3 External Storage XP requirements Item Requirement Required products • HP StorageWorks Command View XP version 2.0 or later, or XP Remote Web Console • HP StorageWorks LUN Configuration and Security Manager XP (for setup) • HP StorageWorks RAID Manager XP version 01.12.
For instructions, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200. Preparing for External Storage XP settings Before using External Storage XP, collect the information necessary for defining its settings.
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 External Storage XP 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.
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 disk 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 disk array. NOTE: Users should disable cache for low price/performance arrays, such as the HP MSA arrays.
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 External Storage XP, host I/O operations to the external LU via the local array are normally enabled using the mapped path.
Figure 3 Example of alternate path configuration using two switches In Figure 4, 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 External Storage XP to use alternate path settings, HP does not recommend the configuration shown in Figure 4.
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 NOTE: External arrays with Asymmetrical Active/Active (AAA) controllers, such as the Hitachi Thunder, are an example of Figure 7. A notable characteristic of using AAA controller arrays as external storage is that paths to alternate ports on the owning controller for a given external LU are seen as Normal status, but I/O load balancing does not occur (either across controllers or across ports to the owning controller).
Figure 8 Alternate path mode is Single mode with alternate paths in Standby only NOTE: External arrays with Active/Standby (A/S) controllers, such as the MSA, are an example of Figure 8. A notable characteristic of using A/S controller arrays as external storage is that there is typically only a single port to the owning controller. Paths to the non-owning external controller's ports are shown as Standby status. I/O load balancing does not occur across external controllers.
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.
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. 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.
Powering external arrays on or off To power external arrays off 1. 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. 2. 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).
CAUTION: Make sure that the power supply of the local array is completely off and then go on to the next step. 5. 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: 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.
Figure 9 Writing new data to mapped external LUs Using existing data in mapped external LUs Figure 10 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 External Storage XP to map the LU in the external array containing data as an internal LDEV of the local array.
NOTE: Do not access any external storage volume that is mapped as an External Storage XP volume from a host connected directly to the external array. Also, do not access an External Storage XP 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.
5. Use the Command View XP or XP Remote Web Console Licensing module to remove the Flex Copy XP license key. For instructions, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200. 6. For the local array, use the Command View XP or XP Remote Web Console Licensing module to remove the External Storage XP license key.
• 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.
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 External Storage XP, select Disable. For Flex Copy XP, select Enable.
• If you set a mainframe-system emulation type for the mapped LU, host I/O is always propagated asynchronously to the external LU regardless of the Cache Mode setting. • External LU attributes (IO Suppression mode and Cache Mode) set when the LU is mapped cannot be changed while the LU is mapped. To change these attributes, delete the external LU mapping (Delete LU operation), and remap the LU with different attributes (Add LU operation).
• 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 Command View XP or XP 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.
Application HDD type FC HD-FC S-ATA 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 5 When external LU's emulation type is for mainframes Application HDD type FC HD-FC S-ATA 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
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.
• • • • • HP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200. 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.
• 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. • LUN Security XP Extension • You must set the IO Suppression mode to Disable to use the mapped external LU for LUN Security XP Extension operations.
Figure 14 Example of Auto LUN XP operations 1. Use External Storage XP 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 Continuous Access XP operations Figure 15 shows an example of using an external LU for Continuous Access XP operations. The mapped external LU is set as the Continuous Access XP pair's S-VOL, and the volume in the local array that is connected as the MCU is set as the Continuous Access XP pair's P-VOL. For more information about Continuous Access XP operations, see the HP StorageWorks Continuous Access XP user guide for the XP12000/XP10000/SVS200.
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 StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200. Go to step 4. 4. Set the Continuous Access XP pair's P-VOL and S-VOL. Using external LUs for Continuous Access XP Journal operations Figure 16 shows an example of using the external LU for Continuous Access XP Journal 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 StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200. Go to step 4. 3.
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 StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200. Go to step 4. 3.
For more information, see Mapping external LUs (Add LU). 2. 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 StorageWorks LUN Configuration and Security manager XP user guide for the XP12000/XP10000/SVS200. 3. Create a pool, and add the mapped external LU to that pool as a pool-VOL. 4.
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.
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.
2. To find the LU number and UUID, select an external device group in the Device tree (Figure 20). 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. 58 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.
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.
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 6 shows the recommended cache sizes for external storage CLPRs on open systems. Table 7 shows the same information for HP storage virtualization systems.
Figure 24 Partition Definition pane 5. Click Apply for the changes to becomes effective. 6. Repeat step 3 through step 5 to define any additional CLPRs that you need. 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.
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). The selected external storage groups are added to the CLPR resource list. Figure 26 Partition Definition pane, Paste Parity Group option e. 64 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. Changing storage system modes In addition to cache partitioning and cache modes, array system modes control LU cache usage.
Managing cache with external storage
4 External Storage XP panes External Storage XP operations involve the LU Operation and Port Operation panes. In addition to these two panes, the Flex Copy pane is available if you licensed Flex Copy XP. When you select a tab, the corresponding pane appears. Figure 27 Panes for External Storage XP operations LU Operation pane This pane appears when you start External Storage XP. 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).
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 External Storage XP 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.
• 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 8 External array status values 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.
• LDEV Status: Mapped external LU's status. Possible values: Normal, Unknown, Blockade, Warning, and Format. Table 9 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.
• Group: External LU group number and reference number assigned to each LU in the external LU group. External Storage XP 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”. • 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.
• 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.
• 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.
• • • • • • • • • • • • • • • • • 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.
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. External Storage XP 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. External Storage XP 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. • Information area Displays the total number of ports currently displayed in the Port Operation list (Total Number of Ports).
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.
Port Operation list Displays ports in the local array that External Storage XP 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.
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.
5 Configuring external LUs Use External Storage XP 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 External Storage XP to configure external LUs. Overview of configuring external LUs Figure 41 shows an example of using External Storage XP to configure external LUs.
4. 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, Command View XP or XP Remote Web Console must be in Modify mode. 5. 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. 6.
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 Virtual Partition Manager, 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. Select the Port Operation tab. 2. In the Port Operation list, select the port. To set multiple ports at one time to External, select all the ports. 3.
Mapping external LUs individually (Add LU) This section describes mapping operations starting with the Add LU command. Use the Add LU (Figure 42), Select Paths (Figure 43), SSID (Figure 46), and Set SSID (Figure 47) panes for mapping external LUs individually. NOTE: Before mapping the external LU, ensure that no other applications (such as RAID Manager XP) that use the command device are executing. Stop any applications that are executing. Figure 42 Add LU window • Vendor External array's vendor.
• VMA Information about the VMA setting of LUN Security XP Extension. If you mapped the external LU and previously set the VMA of LUN Security XP Extension, an asterisk (*) appears. If LUN Security XP 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.
CAUTION: To use the mapped external LU for the software products other than Flex Copy XP (such as Cache LUN XP, Auto LUN XP, Continuous Access XP, Continuous Access XP Journal Business Copy XP, or Snapshot XP), set IO Suppression mode to Disable. CAUTION: To set IO Suppression mode to Disable, External Storage XP must be installed. CAUTION: To set IO Suppression mode to Enable, Flex Copy must be installed.
Displays the Select Paths pane (Figure 43). 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 path, use the Select Paths pane to specify candidates for alternate paths.
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. 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.
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. • 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.
• 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). 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 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. 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. 8. Click OK.
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. To cancel settings, right-click the setting in the Preset list, and select Delete. Go to step 13. 10.
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.
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 Flex Copy XP (such as Cache LUN XP, Auto LUN XP, Continuous Access XP, Continuous Access XP Journal, and Business Copy XP), set IO Suppression mode to Disable. CAUTION: To set I/O Suppression mode to Disable, External Storage XP must be installed. CAUTION: To set IO Suppression mode to Enable, Flex Copy XP must be installed.
CAUTION: If the specified number of alternate paths cannot be set, an error appears in the Preset list. • 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.
Select LDEV window Figure 49 Select LDEV window • CU list CU number of the local array to which you want to map the external LU. • 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).
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.
• 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.
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 LUN Security XP 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.
• 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.
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).
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.
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.
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. 112 Execute the Disconnect Paths command on the alternate path A (see section 5.16).
2. 3. 4. 5. 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 section 5.5.4). Click the Apply button to apply the settings of the alternate paths A and C. 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.
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: 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.
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.
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.
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. 5. In the Unselected Paths list, select ports (WWNs of the external array), and click Set. The selected ports move to the Selected Paths list. 6. Click OK. The Path Setting window appears. 7. Ensure that deleted paths are applied to the array in the Path Setting window.
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.
• • • • Path: Number of set paths. Emulation Type: External LU's emulation type set when it was mapped. 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.
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 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. 4. Select View all LUs. 5.
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.
CAUTION: Note the following for the Disconnect Subsystem and Disconnect Volume commands: • After executing the Disconnect Subsystem or Disconnect Volume command, click the Refresh button • • • • • • ( ) on the Command View XP or XP Remote Web Console main pane to update the information, and check the current progress status. If you execute the Disconnect Subsystem or Disconnect Volume command when I/Os from an open-system host are in progress, host I/Os to the specified volume are forcibly stopped.
Figure 59 Disconnect Subsystem and Check Paths & Restore Vol. 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 of 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. Click Apply. A confirmation message appears. 4. Click OK. The Ex-Dev.
3. Click Apply. A confirmation message appears. 4. Click OK. The Ex-Dev.Status column in the Device list changes to Cache Destaging. When External Storage XP 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.
2. 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. 4. Click OK.
Restoring volumes in an external array 1. In the LU Operation pane, select External Devices in the Device tree. Connected external arrays appear in the Device list. 2. 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.
• 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 Cache LUN XP or change the cache residency mode to the priority mode. • Whether the IO Suppression mode is set to Disable.
4. Click the LU Operation tab. The LU Operation pane is displayed. 5. 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. 6. 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 (see Figure 5.15). The selected external LU is displayed in blue and italics in the Device tree and Device list.
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: The path must be in a status that can be restored. 1. In the LU Operation pane, select the WWN tab. The WWN tree and WWN list appear. 2.
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.
8. Click OK. 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).
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.
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.
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. For more information about each procedure, see the following manuals: • For NAS Blade Manager, see the NAS Blade Manager User's Guide. • For NAS Sync Image, see the NAS Sync Image User's Guide.
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.
Restarting external arrays and restoring NAS Blade systems 1. Turn the external array power supply on. For instructions, see Topowerexternalarrayson. 2. Confirm that the external array's status is normal. 3. Execute the Check Paths & Restore Vol. command using External Storage XP to restore the path to the external array. For instructions, see Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.). 4.
Figure 62 Error in an external array's disk 1. Delete all Business Copy XP or Continuous Access XP 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.
11. Restart NAS OS 2 (NAS channel adapter's OS) using LUN Manager 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. Change the error disk in the external array to restore the external array's status. 15. Execute the Check Paths & Restore Vol.
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 External Storage XP. 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).
• 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 External Storage XP. For instructions, see Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.). 3.
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, 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 is as follows: • None of the user LUs can be used from node 1 or node 2. • Clients cannot access volumes.
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 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 RAID Manager XP 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 shows an example.
Figure 66 Overview of remote command device 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: • 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 subsyst
• You do not need a license for External Storage XP or Flex Copy XP to map command devices as remote command devices. • Remote command devices are displayed on External Storage XP's panes. As you select an external LU group number in the Device tree on the LU Operation pane, the information shown in Table 10 appears.
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 10. • 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.
NOTE: Command devices that can be mapped as remote command devices are displayed on External Storage XP's panes as shown in Table 10. 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.
Figure 67 Difference between Standard and Initiator/External MIX modes Figure 68 shows an example of using Continuous Access XP or Continuous Access XP Journal with a remote command device. In Figure 68, local array 1 functions as the MCU of Continuous Access XP or Continuous Access XP Journal, and at the same time it functions as the local array of the remote command device.
Figure 68 Using Continuous Access XP or Continuous Access XP 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.
5. Start the Continuous Access XP or Continuous Access XP 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 Continuous Access XP and Continuous Access XP Journal copy processing and operation. 2. Stop accessing the remote command device. 3. Delete the remote command device mapping. 4. Change the port block setting from Initiator/External MIX mode to Standard mode.
8 Troubleshooting External Storage XP If you have a problem with the Command View XP computer or Command View XP or XP Remote Web Console software, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console for XP12000/XP10000/SVS200 for troubleshooting information. For additional assistance, contact your HP account support representative. Table 12 provides general troubleshooting instructions for External Storage XP operations.
Error Corrective action The status appearing in the Ex-Dev. Status column is Normal, but the status appearing in the LDEV Status is Unknown. 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 Command View XP or XP Remote Web Console. The LDEV's status cannot be determined.
Error Corrective action 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.
Error Corrective action 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.
Error Corrective action 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.
Error Corrective action • 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.
Error Corrective action 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.
Error Corrective action • 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 LUN of the local array does not have a status of Normal. • The external LU capacity is insufficient (less than 46.86 MB). • The cable to the switch is not properly connected.
Error Corrective action REQUIRED is issued to the mainframe host as the device status. normally, the device can be used immediately. If the device is blocked as a result of the device status transition, see the description for the “The external LU is blocked.” error in this table for corrective action. The message DEVICE ERROR is issued to the mainframe host as the device status. See the description for the “The external LU is blocked.” error in this table for the corrective action.
Troubleshooting External Storage XP
A Notes on connecting external arrays NOTE: If you have an EVA or MSA connected as external storage and you need to perform a firmware upgrade on the EVA or MSA, you must use the EVA/MSA offline firmware upgrade function. When the EVA or MSA is connected as XP external storage, online EVA/MSA firmware upgrade is not supported at this time. Therefore, you must stop host I/O to the arrays in question, and issue the Disconnect Subsystem command before the upgrade.
Connecting Thunder 9500V subsystems System parameters for connecting Thunder 9500V subsystems Table 13 explains whether to specify system parameters when making settings for ports on the Thunder 9500V subsystem. Table 13 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.
Pane name Port Type Controller Option Host Connection Mode Parameter Parameter setting 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.
Relation btw. ser. nums. in the Dev. list on LU Op. pane & Thunder 9500V subsys. mod. 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 14 shows the relationship between serial numbers displayed in the Serial column and subsystem models.
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 16 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.
Path status Examples of recovery procedures 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 Business Copy XP, Continuous Access XP, 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. Open LDEV Guard may have changed the volume's access attribute. Check the volume's access attribute.
Connecting TagmaStore AMS and TagmaStore WMS subsystems System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems Table 17 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 LUN Manager to set the data transfer speed of the XP12000/XP10000/SVS200 external port you use to a fixed value other than Auto Negotiation.
Pane name Parameters Parameter setting WEB Title You can either specify this parameter or omit specifying this parameter. Write and verify mode Set this parameter to ON. 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: Do not specify HISUP OFF mode, either.
Relation btw. the WWN of the port on the TagmaStore AMS or TagmaStore WMS subsys. and contr. 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 19 shows the relationship between the port's WWN and the controller. Table 19 Relation btw. ports' WWNs & contrs. (TagmaStore AMS & TagmaStore WMS subs.
Path status Examples of recovery procedures 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 External Storage XP to perform the Delete LU operation, and perform the Add LU operation again. LUN Security XP 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.
Path status Examples of recovery procedures 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.
Path status Examples of recovery procedures 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 External Storage XP to perform the Delete LU operation, and perform the Add LU operation again. LUN Security XP 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.
Path status Examples of recovery procedures 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.
Path status Examples of recovery procedures the settings back to the ones used when the volume was mapped. Or use External Storage XP to perform the Delete LU operation, and perform the Add LU operation again. Open LDEV Guard 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.
Path status Examples of recovery procedures 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 LUN Manager to set the Fibre Channel port properly.
Path status Examples of recovery procedures 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 Business Copy XP, Continuous Access XP, 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.
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 External Storage XP connection) or “RCU target port” (for a Continuous Access XP connection).
Path Status Examples of Recovery Procedure 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. LUN Security XP 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.
Path Status Examples of Recovery Procedure LUN Manager 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 Identifying logical volumes of EVA arrays (using Characteristic 2) When the connected external array is an EVA array, LUNs are displayed as Characteristic in External Storage XP's panes.
microprogram version 4.000 or later • Array type: EVA4000/6000/8000 microprogram version 5.031 or later To replace the EVA array's microprogram, check whether the alternate path's behavior changes as a result of changing the microprogram version. If the alternate path's behavior changes, perform External Storage XP's Delete LU operation to release the setting for the EVA array volume's mapping before you actually replace the microprogram.
B Required volume capacity for emulation types When mapping an external LU as a local array internal LDEV, you must specify the mapped volume's emulation type. The capacity required for the LDEV to be mapped is the total capacity of the data area for storing actual user data and the control information area for storing control information.
Emulation type External LU's maximum usable capacity 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.
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.
Emulation type Minimum data area capacity Base data area capacity Control information area capacity blocks cylinders blocks cylinders blocks cylinders 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 27 lists the base LDEV capacity,
Emulation type Base LDEV capacity (blocks) Minimum LDEV capacity (blocks) Maximum capacity of external LU (blocks) Maxm i um number of LDEVs when maxm i um capacity of external LU is mapped1 blocks cylinders blocks cylinders blocks cylinders 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
Required volume capacity for emulation types
C Adjusting volume capacity for copy pair setting When creating a Business Copy XP or Flex Copy XP 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.
D Configuring MSA1000/1500 as external arrays NOTE: Externally connected MSAs must not contain Continuous Access XP P-VOLs or S-VOLs. Configuring external array LUs, host mode, and ports This appendix describes how to configure the MSA external array. For other arrays, see the documentation for that external array. You do not need to configure the SAN topology parameters on the MSA array.
NOTE: References to MSA generally refer to both the MSA1000 and the MSA1500 (both with an Active/Passive controller). Although the standby MSA controller may connect to the same XP12000/XP10000/SVS200 port as the active MSA controller (shown in Figure 74), HP recommends that it connect to an XP port on a different XP cluster. Figure 74 Example: Connecting an MSA array The following is a summary of the port setting status of the local array when you connect the MSA external array.
Defining MSA array objects Use the Array Configuration Utility (ACU) to define at least one internal MSA array object (for instance, “A”) when first setting up the array. After defining an array object, specify LUs within that array object. Figure 75 Defining MSA array objects with the ACU Calculating MSA LU size and defining LUs The ACU used for configuring the MSA uses an optimization algorithm to calculate the user size of a new LU given a user-specified size in MB (Figure 76).
Figure 76 Defining MSA LUs with ACU Selective Storage Presentation You must institute LUN security on MSAs using the ACU Selective Storage Presentation (SSP) feature (Figure 77). Use SSP to limit access to individual MSA LUs (in this case, logical drives 1 and 2) by selected host (or XP12000/XP10000/SVS200) HBA world wide names. When using SSP, set the operating system mode corresponding to the XP12000/XP10000/SVS200 array port WWN to TRU64.
Index C A Active/Standby (A/S) controllers, 32 ACU (Array Configuration Utility), 192, 193 ACU Selective Storage Presentation (SSP), 194 Add LU (Auto) operation, 97 Add LU operation, 93 Add LU window, 88 alternate paths adding to multiple external LUs, 113 canceling, 110 changing, 111 defining, 26, 105, 108 deleting to multiple external LUs, 115 EVA arrays, 181 LU Operation pane, 67 Path Setting window, 105 ports, 92 priority of, 26, 30, 109 Select Paths pane, 92 switching I/O execution paths to, 28 applic
D deinstalling External Storage XP, 39 Delete LU command, 132 Device Error message, 161 Device list, 70 Device tree, 69 Disconnect Paths, 131 Disconnect Subsystem command disconnecting external LUs, 121 powering arrays on and off, 32, 34 restrictions, 44 troubleshooting, 160 Disconnect Volume command disconnecting external LUs, 121, 123 powering arrays on and off, 33, 34 restrictions, 44 troubleshooting, 160 Discovery operation, troubleshooting, 159 disk errors, NAS Blade system, 137 document conventions, 1
external LUs Add LU, 93 alternate paths, adding to multiple, 113 alternate paths, defining, 26, 105 alternate paths, deleting to multiple, 115 Business Copy XP operations, 52 capacities, 40, 183 configuring, 85, 85 connection status, 124 Continuous Access XP Journal operations, 51 Continuous Access XP operations, 50 defined, 15 Delete LU command, 132 Device List, 70 disconnecting, 121 emulation type, setting, 89, 98 groups, 25 HDD types, 44 LU Operation pane, 67 mapping, 87 mapping all at once, 94 mapping m
local arrays capacity, 183 configuring, 191 connection status, 74 defined, 15 Fibre Channel connections, 16 mapping restrictions, 16 port settings, 24, 86 powering on and off, 32, 34 remote command devices, 145 stopping paths, 128 system requirements, 19 volume migration, 48 LU Operation pane, 67 LUN Security XP Extension, 48 LUs.
R RAID Manager XP, 104, 145 Read and Write performance, 45 related documentation, 11 remote command devices Continuous Access XP, 149 defined, 145 mapping, 148 restrictions, 148 specifications, 146 Remote Web Console about, 15 troubleshooting, 153 restarting NAS Blade system arrays, 137 restoring external array volumes, 126 external LU volumes, 126 external LUs, 119, 124, 125 LDEV Restore, 125 NAS Blade system arrays, 137 paths to external LUs, 129, 131 SVS200, 179 TagmaStore subsystems, 171 Thunder 9500V S
V VMA information, displaying, 103 VMA setting, 89 volume capacity adjusting, 189 required, 183 Volume Detail window, 120 Volume Manager, 46 Volume Retention Manager, 48 Volume Security, 48 W web sites HP documentation, 12, 13 HP service locator, 13 HP storage, 13 HP Subscriber's Choice for Business, 13 writing data to mapped external LUs, 36 WWN List, 74 WWN paths restoring, 129 stopping, 128 WWN Tree, 73 X XP Remote Web Console about, 15 troubleshooting, 153 XP1024/XP128 arrays, connecting, 175 XP12000/
