HP StorageWorks External Storage XP user guide XP12000 XP10000 SVS200 Part number: T1706-96006 Sixth edition: June 2006
Legal and notice information © Copyright 2005, 2006 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
For example, Company A uses: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In another example, Company B uses the following storage tiers: . . . . . . . . . . . . . . . . . . . . . . To partition cache for external storage:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number and size of needed partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Cache partitions . . . .
6 Troubleshooting NAS Blade systems that include external arrays . . . . . . . . . . . . . . . . . 107 Stopping and restarting external arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping external arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting external arrays and restoring NAS Blade systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating new EVA host objects for the XP12000/XP10000/SVS200 . . . . . . . . . . . . . . . . . . . . . . . Creating and presenting EVA Vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining XP12000/XP10000/SVS200 external ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining XP12000/XP10000/SVS200 external storage LDEVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommendations. . . . . . . . . . . . . . . . . . .
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 Tables 1 2 3 4 5 6 7 8 9 10 11 Overview of configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Add LU window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Select Paths pane. . . . . . . . . . . . . . . . . . . . . . . . . . .
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 8 General External Storage XP troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 System parameter settings (Thunder 9500V subsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Relationship between serial numbers and subsystem models (Thunder 9500V subsystems) . . . . . . . . . 129 Relationship between ports’ WWNs and controllers (Thunder 9500V subsystems) . . . . . . . . . . . . . .
About this guide This guide 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 In this guide, the term array refers to the following storage platforms: • HP St
Document conventions and symbols Document conventions Table 1 Convention Element Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: (http://www.hp.
After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP web sites For additional information, see the following HP web sites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.com/support/rwc/manuals Documentation feedback HP welcomes your feedback.
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.
Figure 1 illustrates a local array and an external array that are connected using External Storage XP and Fibre Channel hardware. In Figure 1, the external array is connected to the external port of the local array via a switch (or hub) using a Fibre Channel interface. External is a local array port attribute used for External Storage XP. In Figure 1, external LUs are mapped as local array VDEVs and LDEVs and, consequently, as an LU.
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.
Table 2 Storage arrays that can be connected as external arrays (continued) Storage array Notes HP StorageWorks XP1024/XP128 Disk 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) • • • HP StorageWorks MSA1000/1500 (Acti
Table 2 Storage arrays that can be connected as external arrays (continued) Storage array Notes Lightning 9900V series subsystem • • • • Thunder 9500V series subsystem • • • • Lightning 9900C series subsystem • • • • A/H-6593 subsystem • • SANRISE Universal Storage Platform subsystem • • • SANRISE Network Storage Controller subsystem • • • SANRISE Adaptable Modular Storage subsystem • • • SANRISE Workgroup Modular Storage • • • “Lightning 99xxV series subsystem” indicates the Lightning 9
Table 2 Storage arrays that can be connected as external arrays (continued) Storage array Notes SANRISE9900V series subsystem • • • • SANRISE9500V series subsystem • • • • SANRISE2000 series subsystem • • • • SANRISE H12000 subsystem • • SANRISE H10000 subsystem • • SANRISE H1024/H128 subsystem • • SANRISE H512/H48 subsystem • • SANRISE H256 subsystem • • 18 “SANRISE99xxV series subsystem” indicates the SANRISE9970V and SANRISE9980V.
CAUTION: For more information about alternate path modes, see ”Setting alternate paths for external LUs” on page 86. 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.
• Ports that can be set to external ports (see ”External ports” on page 20) • External array and LUs to map to the internal LDEVs (see”External LU to be mapped” on page 20) • Configuration of external LU groups (see ”External LU groups” on page 20) • Configuration of external LU attributes (see ”External LU attributes set by mapping” on page 20) • Configuration of alternate paths (see ”Alternate paths” on page 22) External ports Local array ports used for External Storage XP must be set to a designation of
Set the mapped LU’s emulation type by selecting any emulation type from the drop-down list. However, if you plan to use the mapped LU for Flex Copy XP operations, or you plan to access existing data in the external LU, you must select the OPEN-V emulation type to avoid data resizing. If you plan to use existing data in the external LU from the local array after mapping, you must select the OPEN-V emulation type.
restricted to the storage management logical partition (SLPR) the CLPR belongs to. For more information about CLPRs and SLPRs, see the HP StorageWorks XP Disk/Cache Partition user guide. Alternate paths When mapping an external LU as an internal LDEV, paths are set from the internal LDEV to the external LU. If two or more paths to the external LU are equipped from different clusters, the number of paths you set when mapping the volume are available. If one path is equipped, only that path is available.
the local array. You must specify the port of a different cluster in the local array for the alternate path, as ports CL1 and CL2 are specified in the figure. Figure 2 Example of alternate path configuration Figure 3 shows another example of an alternate path configuration. In Figure 3, two ports are specified in the local array and connected to ports in the external array via switches.
For more information about path status, see ”Adding alternate paths by selecting multiple external LUs (Add Paths)” on page 91. • Alternate path mode is Multi mode Figure 5 shows an example of when the alternate path mode is Multi mode. When an error occurs in one path, I/Os execute using paths other than the error path. NOTE: As you restore the error path, use of the restored path automatically resumes.
NOTE: As you restore the path with a priority higher than the current path, the I/O execution path automatically switches to the restored path with the highest priority. 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.
NOTE: When the external array is an EVA array, as you restore the path with the highest priority, the I/O execution path switches back to the restored highest priority path. In this case, the status of the path for which the status changed to Normal when the error occurred changes back to Standby.
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.
This command checks if defined information about the mapped external LU and the actual external LU status match. If the external LU can be used as the mapped local array volume, the external LU is set to accept I/O, and you can continue using the external LU as a mapped LU. Use this command to restore the external LU, which is set to reject host I/O operations by the Disconnect Subsystem or Disconnect Volume command, as the mapped volume. You can execute the Check Paths & Restore Vol.
CAUTION: When the Disconnect Subsystem or Disconnect Volume command is executed and all data in cache memory is written to the external LU, the displayed information for Ex-Dev. Status in the Device list becomes Disconnect. Powering external arrays on or off To power external arrays off 1. 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.
area, use Volume Manager to format the mapped LU. For instructions, see the HP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200. To to step 4. 3. For mainframe-system emulation types (for example, 3390-XX), the status of the mapped LU is set to Blockade, pending resizing and formatting. Use Volume Manager to format the volume.
After the path is set, host I/O operations to the mapped volume are available. NOTE: Do not access any external storage volume that is mapped as an 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.
Limitations on External Storage XP operations • External LUs can be mapped as any CU:LDEV combination from 00:00 to 3F:FF. • Only ports in SLPR0 can be set as external ports. • 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).
LU’s capacity and each emulation type’s normal size. When mapping an external LU using emulation types other than OPEN-V, an XP array management information area is required in the mapped LU. This means that the capacity available after mapping is slightly smaller than the actual external LU capacity. Available capacity decreases by the size of the XP array management information area, and all prior data must be considered lost. For more information, see the HP StorageWorks Flex Copy XP user guide.
• The local array does not force the external array to reserve the mapped external LU. Therefore, do not write directly to an external array LU (that is, without writing via the local XP array) with IO Suppression mode set to Disable from the external array side. If Flex Copy XP operations are in progress for a volume with IO Suppression mode set to Enable, be careful when updating data in that external LU from the external array side.
• Do not combine LDEVs from multiple external LUs to create a LUSE volume. • Do not update a volume being used or operated by Flex Copy XP. Also do not update the external LU on the external array side. • You can delete up to 256 mappings for external LUs at one time. • Operations cannot be performed if some parts of the local array are blocked. In this case, restore blocked parts of the local array, and retry the operation.
• Table 4 and Table 5 show the recommended application level for the mapped external LU according to the external LU’s HDD type.
concern, ensure that the external LU’s Path Blockade Watch time is the same as or shorter than the host command’s timeout period. • Host access to the external storage LU must be via the local array, and must not be via a direct physical connection to the external storage device LU. For external array LUs not involved with External Storage XP, direct access from a host is allowed for all supported external storage except MSA.
You must set the IO Suppression mode to Disable to use the mapped external LU for Continuous Access XP operations. For a Continuous Access XP configuration example, see ”Using external LUs for Continuous Access XP operations” on page 39. • TrueCopy for z/OS You must set the IO Suppression mode to Disable to use the mapped external LU for TrueCopy for z/OS operations.
Using external LUs for Auto LUN XP operations Figure 14 shows an example of using an external LU for Auto LUN XP operations. The mapped external LU is set as the source volume, and the local array internal LDEV is set as the target volume. Existing data in the external LU is (in effect) manually migrated to the internal LDEV on the local array using Auto LUN XP. For more information, see the HP StorageWorks Auto LUN XP user guide for the XP12000/XP10000/SVS200.
Continuous Access XP operations, see the HP StorageWorks Continuous Access XP user guide for the XP12000/XP10000/SVS200. Figure 15 Example of Continuous Access XP operations 1. Use External Storage XP to map a volume in the external array to an internal LDEV of the local Continuous Access XP RCU array. CAUTION: Set the IO Suppression mode to Disable. Select the mapped volume’s emulation type as required. If you select an open-system emulation type (such as OPEN-V), go to step 2.
array that is connected as the MCU is set as the Continuous Access XP Journal’s P-VOL. For more information, see the HP StorageWorks Continuous Access XP Journal user guide. Figure 16 Example of Continuous Access XP Journal operations 1. Use External Storage XP to map the volume in the external array as an internal LDEV of the local array, which is used as the RCU for Continuous Access XP Journal operations. CAUTION: Set the IO Suppression mode to Disable.
Business Copy XP pair’s P-VOL. For more information, see the HP StorageWorks Business Copy XP user guide for the XP12000/XP10000/SVS200. Figure 17 Example of Business Copy operations 1. Use External Storage XP 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.
For more information about Snapshot XP, see the HP StorageWorks Snapshot XP user guide. Figure 18 Example of Snapshot XP operations 1. Use External Storage XP 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 a Snapshot XP pool-VOL. Set the IO Suppression mode to Disable.
Preparing for External Storage XP operations
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 if the cache mode is disabled If you have an existing configuration and need to determine if your external LUs are configured with cache mode disabled, follow this procedure: 1. In the XP Remote Web Console main pane, click the External Storage button in the left pane. The LU Operation pane appears. 2. In the Device tree, select an external device group. 3. In the Device list, check the Cache Mode setting (Figure 19). If cache mode is enabled, you should change it to Disabled.
1. In the XP Remote Web Console main pane, click the External Storage button in the left pane. The LU Operation pane appears. 2. To find the LU number and UUID, select an external device group in the Device tree (Figure 20). 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.
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.
5. Click OK in response to the warning message. 6. Click OK. 7. Remap the LU using all the previous settings except for the cache mode setting, which is disabled. See ”Mapping external LUs (Add LU)” on page 73. NOTE: When scanning for devices to add, the order in which devices are discovered might be different. The UUID is always the same for the same external device. Ensure that the UUID of the device being remapped matches the UUID that was deleted for the same LU number. 8.
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.
4. Select the new CLPR in the tree, and change the size and other CLPR settings as needed (Figure 24). 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. 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. 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. 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” on page 49. 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.
LU Operation pane This pane appears when you start External Storage XP. Information about the external array appears on the LU Operation pane. Use this pane to perform operations such as mapping external LUs and setting alternate paths.
• Total number of Devices: Number of external LUs that are connected. • Total number of External Groups: Number of external LU groups that are set. • Total number of External LUs: Number of external LUs that are connected. • Found WWNs: WWNs found when you clicked Discovery in the Device tree. • Remain LUs: Number of external LU numbers available (out of 15,360), other than those that have already been used.
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.
Table 8 External array status values (continued) LU status Description Warning FC path or paths have an abnormal status. Check the status of the paths. Checking External Storage XP is verifying configuration information defined for FC paths. Cache Destage External Storage XP is writing all data in the local array cache memory to the LU. Disconnect Connection to external array or external LU was intentionally stopped using the Disconnect Subsystem or Disconnect Volume command.
• Ex-Dev. Status: Status of the operation executed to the external array, or status of the path connection. Possible values: Normal, Unknown, Blockade, Warning, Checking, Cache Destage, and Disconnect. For a description of these values, see Table 8. • LDEV Status: Mapped external LU’s status. Possible values: Normal, Unknown, Blockade, Warning, and Format. For a description of these values, see Table 9. • Progress: When Status is Cache Destage, displays the destaging process progress, from 1% to 100%.
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)” on page 66.
• Blockade: Path is blocked. • Disconnect: Connection to the external array or external LU was intentionally stopped using the Disconnect Subsystem or Disconnect Volume command. • Warning: There are paths whose status is not normal. Check the status of the paths. • Checking: Process of checking the paths’ defined configuration informations is in progress. • WWN of the external array • Port: Port number of the local array connected to the port identified by the WWN selected in the Port tree.
alternate path that is in the Standby status. When the primary path changes, the status of the path becomes Normal. • Backoff: External array replied Backoff. The path status is waiting for recovery because a temporary error occurred in the external array’s LU. Even if the primary path’s status becomes Backoff, the primary path does not immediately change to the alternate path. After the error recovery, the status becomes Normal.
Port list Displays information about the ports and paths of the local array or external array, depending on the item selected in the Port tree. You can sort the list by displayed items. For instance, to sort the items by the port number, select Port on the list. Figure 34 Port list (External selected in Port tree) The displayed contents changes depending on the item selected in the Port tree. • Subsystem When selected, displays nothing in the Port tree.
• Port: Port number of the local array selected in the Port tree. One of the following icons appears for each port: Icon Description Port in Standard mode. Port in Initiator/External MIX mode • WWN: WWN identifying the external array’s port. This port is connected to the local array port selected in the Port tree. • LUN: External array’s LU number. • Characteristic: External LU’s identification number. • Group: External LU group number and reference number assigned to each LU in the external LU group.
• Characteristic2: External LU’s extended identifying information. This information is used for identifying logical volumes in the EVA array. For more information, see ”Identifying logical volumes of EVA arrays (using Characteristic 2)” on page 138. Filter button Displays the Filter window where you can restrict LUs displayed in the Device list. Figure 35 Filter window This window contains Enable and Disable options that control the display of unsupported devices.
Displays the Preset Detail window with detailed information about settings selected in the Preset list. When an error code appears in the Preset list, a corresponding error message appears in this window. Figure 36 Preset Detail window (mapping operation) • Delete Cancels settings selected in the Preset list. Port Operation pane Use this pane to check port settings and set port attributes. This section describes items displayed in the Port Operation pane.
• Port Operation list Displays detailed information about ports selected in the Port Operation tree. For more information, see ”Port Operation list” on page 69. • Information area Displays the total number of ports currently displayed in the Port Operation list (Total Number of Ports). • Preset List Displays rows corresponding to the ports that are about to be acted upon. The contents displayed in the Preset list have not been applied to the local array yet.
Displays ports assigned to each port attribute in the branch below each port attribute. External Storage XP uses ports set to external. One of the following icons appears on the left of each port number: Icon Description Port in Standard mode. Port in High Speed mode. Port in Initiator/External MIX mode Port Operation list Displays ports in the local array that External Storage XP can use or set. The port information displayed corresponds to the item selected in the Port tree.
The sum of the FLI_TOV and PLI_TOV values. 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.
6. Use the Add LU or Auto Map Settings pane to map the external LU as an internal LDEV (”Mapping external LUs (Add LU)” on page 73). 7. 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 LUN Configuration and Security Manager XP user guide for the XP12000/XP10000/SVS200. 8. Define alternate paths between the external array or mapped LU and the local array.
Mapping external LUs (Add LU) After setting the port used for External Storage XP to External, map the external LU as an internal LDEV. If you mapped the external LU and previously set the VMA of LUN Security XP Extension in that volume, the former VMA setting is overwritten when you map the volume again. However, if LUN Security XP Extension is not installed when you remap the volume, the volume with the VMA setting cannot be mapped.
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 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. • 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” on page 20). HP recommends that you set cache mode to Disable. NOTE: • If you set the IO Suppression mode to Enable, Cache Mode becomes Disable.
number of internal LDEVs as external LUs listed in the CU:LDEV list, starting at the internal LDEV you selected. The LDEV numbers of the selected internal LDEVs are sequential. When Interval is set, mapping is done at the specified number of intervals. To map one external LU to another internal LDEV after mapping the external LU automatically using the Linear button, release the Linear button, and map the external LU individually.
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.
i. To map two or more external LU at the same time, select the interval that arranges each volume in the Interval box. j. Select one or more external LUs, and select one or more cells in the LDEV map. When selecting two or more external LUs in the CU:LDEV list, if you select one cell of the internal LDEV number in the LDEV map, the number of cells automatically selected is the same as the number external LUs selected in the CU:LDEV list with the selected internal LDEV first.
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.
list, and select Detail. To cancel settings, right-click the setting in the Preset list, and select Delete. Go to step 13. 10.If you need to set an SSID to the mapped internal LDEV, the SSID pane appears. When storage is partitioned using XP Disk/Cache Partition, select the SLPR number in the SLPR box. If you select the Limited check box and select the SLPR number, you can set only SSIDs that can be used for the selected the SLPR.
CAUTION: If the LUs you are mapping include a volume with the VMA setting, you cannot use the Add LU (AUTO) command to map them at one time. Use the Auto Map Setting and Select LDEV windows (Figure 49) for mapping multiple external LUs at one time. Figure 48 Auto Map Setting window • ExG (1-16384) Group number containing the specified external LU. Specify any decimal value from 1 to 16384. The E displayed outside of the text box is the capital letter of the external LU group.
When the external LU to be mapped has the VMA setting, IO Suppression mode is automatically set to Disable. CAUTION: To use the mapped external LU for products other than 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.
• Select Paths button 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 not set to primary and alternate paths. By default, all paths with a confirmed connection status of normal are set as candidates for primary and alternate paths. However, to set a specific path as the alternate path, specify candidates for alternate paths on the Select Paths pane.
For this example, LDEVs created from the first external LU are mapped to 00:00, 00:02, and 00:04, respectively. The starting CU:LDEV number of LDEVs created from the second external LU is 00:06, and subsequent LDEVS are mapped to 00:08 and 00:0A. The starting CU:LDEV number of LDEVs created from the third external LU is 00:0C, and subsequent LDEVs are mapped to 00:0E and 00:10. • LDEV map Each cell in the map represents an internal XP CU and LDEV number. Select a cell for the internal LDEV on the map.
• 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.
• Product External array’s product name. • LUN LU number of the external LU. • Attribute Select from the following access attributes: • Read/Write: Read and write operations can be performed on the volume. • Read Only: Only read operations can be performed on the volume. • Protect: You cannot access the volume. Read and write operations cannot be performed. • S-Vol Indicates whether or not the volume can be specified as an S-VOL: Enable or Disable.
• ”Changing a defined alternate path priority” on page 89 • ”Canceling alternate path definitions” on page 91 • ”Changing alternate paths” on page 91 The Path Setting window displays information about external arrays and the condition of paths set from the internal LDEV to the external LU. Defined paths Available paths Figure 51 Path Setting window • Vendor External array’s vendor. • Product External array’s product name. • Serial External array’s serial number.
• Port: Port number in the local array connected to the external array. One of the following icons appears for each port: Icon Description Port in Standard mode. Port in Initiator/External MIX mode • WWN: External array port’s identification number. • LUN: LU number of the external LU. • Priority: Priority of paths connecting to the external LU. A 1 indicates the path with the highest priority. • Status: Status of the path to the external LU.
• Path Watch: Time period beginning when the connection of all paths to the external LU is down and ending when the external LU is blocked • Mode: How the local array manages alternate paths when defined. Possible values: • Single: Uses only the path with the highest priority (primary path) to execute I/Os to the external LU. If selected, the second-highest priority alternate path is enabled only if a maintenance operation or failure affecting the primary path occurs.
As long as the external array uses Symmetrical Active/Active controllers (for example, XP), change an alternate path to the currently used path by simply raising the priority of the alternate path or lowering the priority of the currently used path. NOTE: If the two paths connect to different controllers on the external array (for example, MSA), do not use a path priority change to attempt to force a controller failover.
9. Click OK. The change in the alternate path defined in the Path Setting window is applied to the local array, and specified contents appear in the Device list. If errors occur during alternate path operations, failed settings and error codes appear in the Preset list. To check error messages, right-click the failed setting, and select Detail. Canceling alternate path definitions Use the Path Setting pane to cancel an alternate path definition. 1.
NOTE: Use the Add Paths window to add paths to multiple external LUs at one time. However, path settings might not be applied because of the current path setting of each volume. After setting paths in the Add Paths window, check whether or not the new path settings can be applied in the Path Setting window for each external LU. If the setting cannot be applied, the setting from the Add Paths window does not appear on the Path Setting window.
4. In the Port list, select the local array port. External array ports (WWNs) that can configure the path connecting with the selected local array port appear in Unselected Paths. 5. In the Unselected Paths list, select the port’s WWNs, and click Set. The selected WWNs move to Selected Paths. 6. Click OK. The Path Setting window appears. 7. Ensure that added paths are applied to the array in the Path Setting window. You can also change the alternate path setting in this window.
Local array ports. After selecting a port, you can add the paths. One of the following icons appears for each port: Icon Description Port in Standard mode. Port in Initiator/External MIX mode • Selected Paths Paths of WWNs to be deleted. WWNs identify ports on the external array. Nothing is displayed when you first access the Delete Paths window. • Unselected Paths Ports (WWNs) on the external array that have paths configured for connecting with the local array port selected in the Port list.
Checking an external LU’s status (LDEV Information) After mapping an external LU as a local array internal LDEV, the external LU is available for operations in External Storage XP, Flex Copy, and other HP StorageWorks products that support mapped external LUs. Use the LDEV Information window (Figure 55) to check the status of mapped external LUs.
NOTE: When you use the Custom Volume Size (CVS) function to make an S-VOL for a Flex Copy XP copy pair that has the same capacity as the P-VOL, set the S-VOL’s capacity in blocks or cylinders according to the emulation type. • LDEV List The status of external LU mapped as internal LDEV. The following information appears: • CU:LDEV: CU:LDEV number of the internal LDEV to which the external LU is mapped. • Path: Number of set paths. • Emulation Type: External LU’s emulation type set when it was mapped.
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.
volume in the LDEV list, the Volume Detail window displays a list of all LDEVs that make up the LUSE volume. Figure 57 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.
• You cannot execute the Disconnect Subsystem ore Disconnect Volume command for external LUs that include LDEVs for which Auto LUN XP’s migration processing is in progress. • When executing the Disconnect Subsystem or Disconnect Volume command, the Ex-Dev. Status column in the Device list changes to Cache Destage. Even if there is no data left in cache memory, the displayed status remains as Cache Destage, until the Disconnect Subsystem or Disconnect Volume command processing is complete.
Disconnecting external LUs individually (Disconnect Volume) 1. In the LU Operation pane, select an external LU group number in the Device tree. Information about external LUs in the selected external LU group appears in the Device list. 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.
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. The path status in the Path Setting pane changes to Checking. When External Storage XP finishes checking path status and the external array can be restored, the Status column changes to Normal. If the external array cannot be restored, the status changes to Blockade.
Restoring volumes in a mapped external LU individually 1. In LU Operation pane, select an external LU group number in the Device tree. Information about the external LUs in the selected external LU group appear in the Device list. 2. In the Device list, right-click the external LU you want to restore, and select LDEV Restore. The selected external LU group number and external LU appear in blue italics in the Device tree and Device list. The contents of the setting appears in the Preset list.
• If you select the external array’s WWN, connection information about the paths between the selected WWN and local array ports appear in the WWN list. 3. In the WWN list, select the WWN for which you want to restore the path. • If you selected the product name of the connected external array in the WWN tree, select the WWN identifying the external array’s port in the WWN list. In this case, you can restore the path of all ports of the local array connected to the WWN at one time.
4. Right click, and select Change Parameter. The Change Parameter pane appears (Figure 59). 5. Change the selected port’s parameter. 6. Click OK. The Change Parameter pane closes, and the LU Operation pane appears. Selected items appear in blue italics in the WWN tree and WWN list. The contents of the setting appears in the Preset list. To check the setting details, right-click the setting in the Preset list, and select Detail.
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. Before deleting the external LU mapping, notice if any of the following are true: • Whether or not the execution of any application (for example, RAID Manager XP) that is using the command device is in progress. If any application using an external LU command device is executing, stop the application.
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.
Stopping external arrays 1. Stop access from the client. 2. Stop the cluster using NAS Blade Manager. 3. Delete all Business Copy XP or Continuous Access XP pairs, if you created the pairs specifying the external LU. 4. Stop NAS OS 1 (NAS channel adapter’s OS) and NAS OS 2 using LUN Manager. NOTE: The NAS OS can also be stopped from the SVP. To stop the NAS OS from the SVP, contact your HP account support representative. 5. Disconnect the external array using External Storage XP.
• The local array recognizes that the status of the file system and volume in the error disk is blocked. Figure 61 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: a. Release the differential-data storage device using NAS Sync Image. b. Delete the NFS share, CIFS share, and file system using NAS Blade Manager. 3.
• When resource group 2’s status is Offline, start resource group 2. 14.Change the error disk in the external array to restore the external array’s status. 15.Execute the Check Paths & Restore Vol. command using External Storage XP. For instructions, see ”Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.)” on page 100. 16.Perform the following operations on node 1 and node 2: a. Set up the differential-data storage device using NAS Sync Image. b.
4. Stop node 1 using NAS Blade Manager. 5. Restart NAS OS 1 (NAS channel adapter’s OS) using LUN Manager or NAS Blade Manager. 6. Start node 1 using NAS Blade Manager. 7. Perform one of the following operations using NAS Blade Manager: • When resource group 1’s status is Online, change resource group 1’s execution node to node 1 (failback). • When resource group 1’s status is Offline, start resource group 1. 8. Change resource group 2’s execution node to node 1 using NAS Blade Manager (failover).
• The local array recognizes that the status of all file systems and volumes in external array 1 are blocked. Figure 63 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.
NOTE: In the configuration in Figure 64, 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” on page 22. The situation in Figure 64 is as follows: • None of the user LUs can be used from node 1 or node 2. • Clients cannot access volumes. • The local array recognizes that the status of all file systems and volumes are blocked. Figure 64 If both nodes use the same external array 1.
Troubleshooting NAS Blade systems that include external arrays
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 65 shows an example.
• TagmaStore™ Workgroup Modular Storage subsystem • Lightning 9900V series subsystem • Thunder 9500V series subsystem • SANRISE Universal Storage Platform subsystem • SANRISE Network Storage Controller subsystem • SANRISE Adaptable Modular Storage subsystem • SANRISE Workgroup Modular Storage subsystem • SANRISE9900V series subsystem • SANRISE9500V series subsystem • SANRISE H12000 subsystem • SANRISE H10000 subsystem • SANRISE H1024/H128 subsystem • You do not need a license for External Storage XP or Flex
• Device name NOTE: The device name reported to the host is the same as the one displayed in the Device column of the Device list. For the device names reported to the host, see Table 10. • The following are restrictions for mapping command devices as remote command devices.
Figure 66 shows the difference between Standard and Initiator/External MIX modes. When ports are set to Standard modes, you must connect the cables for the initiator and external ports. However, if you set the Initiator/External MIX mode, you must connect only one cable, and you can use that path to operate Continuous Access XP or Continuous Access XP Journal and the remote command device.
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 67 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.
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. For the procedure to change the port block setting, see the HP StorageWorks LUN Configuration and Security Manager XP user guide for the XP12000/XP1000/SVS200.
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.
Table 12 General External Storage XP troubleshooting (continued) Error Corrective action Unknown Status: The path status is unknown. Corrective action: The path status cannot be identified. Contact your HP account support representative. Blockade Status: The external port is blocked. Corrective action: The external port is blocked because of the microprogram or package replacement or some other factor. Check the local array’s status.
Table 12 Error General External Storage XP troubleshooting (continued) Corrective action Busy Status: The external array’s status is BUSY. Corrective action: The external array’s port is still recognized. Check the external array’s settings and the load on the external array (for example, check whether the configuration assigns too much load on the external array). If you cannot restore the path, contact your HP account support representative.
Table 12 General External Storage XP troubleshooting (continued) Error Corrective action Cannot detect port 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.
Table 12 General External Storage XP troubleshooting (continued) Error Corrective action Backoff Status: The reply from the external array was Backoff. The path status is Waiting for Recovery because a temporary error occurred in the external array’s volume. Even if the primary path’s status becomes Backoff, the primary path does not change to the alternate path immediately. After error recovery, the status becomes Normal.
Table 12 General External Storage XP troubleshooting (continued) Error Corrective action The message INTERVENTION REQUIRED is issued to the mainframe host as the device status. The device status is currently changing. Please wait for a while, and then check the device status again. When the transition of the device status completes normally, the device can be used immediately. If the device is blocked as a result of the device status transition, see the description for the “The external LU is blocked.
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.
Table 13 System parameter settings (Thunder 9500V subsystems) (continued) Pane name Parameter Parameter setting Common 1 Delay Planned Shutdown You can either specify this parameter or omit specifying this parameter. OPTION 1 SCSI Fibre Channel Common Options You can either specify this parameter or omit specifying this parameter. OPTION 2 SCSI Fibre Channel Common Options You can either specify this parameter or omit specifying this parameter.
Relationship between serial numbers in the Device list on the LU Operation pane and Thunder 9500V subsystem models 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.
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” on page 121 and this table to recover the path status. If you cannot restore the path, contact you HP account support representative.
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. Also, set the data transfer speed of the target port of the TagmaStore AMS or TagmaStore WMS subsystem to the same fixed value according to the data transfer speed of the external port.
Relationship between serial numbers in the Device list on the LU Operation pane and TagmaStore AMS and TagmaStore WMS subsystem models When the external array is a TagmaStore AMS or TagmaStore WMS subsystem, you can identify the subsystem model from the serial number displayed in the Serial column in the Device list on the LU Operation pane. Table 18 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 (TagmaStore AMS and TagmaStore WMS subsystems) Table 20 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” on page 121 and this table to recover the path status. If you cannot restore the path, contact your HP account support representative.
Table 20 Path status and examples of recovery procedures (TagmaStore AMS and TagmaStore WMS subsystems) (continued) Path status Examples of recovery procedures Cannot detect port There is a problem with the connection to the external array. The following are possible causes: • • • The fibre cable is not connected properly. The topology setting between the external and target ports does not match. If the external array is connected through switches, the switches’ settings might not be appropriate.
Table 21 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) (continued) 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, Continuous Access XP Journal, or another copy program. If the volume is set as a pair volume, the volume might be protected because of the pair status.
Table 22 Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) (continued) 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.
Table 23 Path status and examples of recovery procedures (XP512/XP48 Disk Arrays) (continued) 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.
Path status and examples of recovery procedures (SVS200) Figure 24 shows examples of the recovery procedures when the path status is not normal. When the path status is not normal, use ”Troubleshooting External Storage XP” on page 121 and this table to recover the path status. If you cannot restore the path, contact your HP account support representative.
If you search for logical volumes by specifying the WWN that indicates EVA Port A in the configuration, such as in Figure 68, logical volumes named LUN 1 and LUN 2 are found for both HostGroup-1 and HostGroup-2. In this case, two different logical volumes with the same name, such as LUN 1 and LUN 2, are found as logical volumes that can be connected from EVA Port A, but you can only tell which LUN 1 and LUN 2 belong to HostGroup-1 or HostGroup-2 by examining the Characteristic field.
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. 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.
Figure 69 shows the relationship of the minimum LDEV capacity, base LDEV capacity, minimum data area capacity, base data area capacity, and control information area capacity. Figure 69 LDEV capacity Figure 70 shows how to determine the volume capacity using the example of the OPEN-3 case. Figure 70 Calculating LU capacity (OPEN-3 example) Table 26 lists the minimum data area capacity, base data area capacity, and control information area capacity for each emulation type.
Table 26 LDEV capacity information for each emulation type (continued) Emulation type Minimum data area capacity (blocks) Base data area capacity (blocks) Control information area capacity (blocks) 3380-KA 72,000 3,823,200 10,080 3380-KB 72,000 3,823,200 10,080 3380-KC 72,000 3,823,200 10,080 3390-3 87,000 5,809,860 10,440 3390-3A 87,000 5,809,860 10,440 3390-3B 87,000 5,809,860 10,440 3390-3C 87,000 5,809,860 10,440 3390-3R 87,000 5,809,860 10,440 3390-9 87,000 17,42
Table 27 Volume capacity information for each emulation type Emulation type Base LDEV capacity (blocks) Minimum LDEV capacity (blocks) Maximum capacity Maximum number of external LU of LDEVs when (blocks) maximum capacity of external LU is mapped 3380-3 4,818,240 82,080 1,207,934,976 250 3380-3A 4,818,240 82,080 1,207,934,976 250 3380-3B 4,818,240 82,080 1,207,934,976 250 3380-3C 4,818,240 82,080 1,207,934,976 250 3380-K 3,833,280 82,080 981,319,680 256 3380-KA 3,833,280 82,
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 71. To adjust the volume capacity to create a pair: 1.
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. If the mapped internal LDEV’s (B) capacity is not same as the copy source volume (C), use Volume Manager to create a CV with the same capacity as the copy source volume (C) out of volume (B). 3. Create a copy pair.
D Using an XP12000/XP10000/SVS200 with an EVA3000/5000 external storage Preface This appendix describes the procedure and relevant recommendations for configuring HP StorageWorks XP12000/XP10000/SVS200 and EVA3000/5000 Disk Arrays where the EVA is used as a highly available external storage array. The XP firmware version and external firmware version must be compatible. Consult your HP account support representative for the latest firmware version required.
different logical units (LUs) from each of the two EVA controllers at the same time. This allows an attached host (or XP12000/XP10000/SVS200) to use both paths shown in Figure 73 for processing I/O simultaneously.
connected XP12000/XP10000/SVS200 external port. Additionally, set Host OS to Microsoft Windows for the XP12000/XP10000/SVS200 to use the EVA LUs correctly. Figure 75 illustrates this step. Figure 75 Creating EVA host objects After the host object is created, add the remaining XP12000/XP10000/SVS200 external ports by selecting the new host object, and clicking the Ports tab. For each port, enter the world wide port name, and click Add Port. Figure 76 illustrates this step.
configuration, HP recommends defining Vdisk settings so the number of Vdisks presented to the XP is balanced between the two EVA controllers and across controller ports. Figure 77 Selecting Vdisk’s Preferred path/mode After EVA Vdisks are created, they can be assigned to the previously defined XP12000/XP10000/SVS200 host object; thereby presenting them to the XP12000/XP10000/SVS200. Figure 78 illustrates this step.
XP12000/XP10000/SVS200 ports to external ports. On the Port Operation pane in External Storage, right-click on the desired ports, and select Change to External. Figure 79 illustrates this step. Figure 79 Defining XP12000/XP10000/SVS200 external ports After external ports are defined, EVA LUs presented to the XP12000/XP10000/SVS200 can be defined as XP external storage LDEVs.
NOTE: You must select external storage LUs through the presenting controller. Failure to do so results in new external LDEVs being placed in a blockade state shortly after a host attempts to access them. Figure 80 Selecting EVA LUs After you select an external logical unit (LU), the Add LU pane appears.
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. Recommendations Performance considerations for using EVAs as external storage Unlike the MSA family of arrays, an EVA can be configured to perform I/O operations with both its controllers on separate EVA LUs simultaneously (Active/Passive capability).
Troubleshooting • Be careful to define an external storage LDEV presented to the XP12000/XP10000/SVS200 by the EVA from the EVA controller that is presently serving its associated LU in an active status. • If you attempt to define an LDEV from an LU via that LU’s passive controller, the resulting external storage LDEV is placed in a blockade state.
E 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.
The following is a summary of the port setting status of the local array when you connect the MSA external array. Topology Fabric ON Fabric OFF Loop Supported Supported Point-to-Point Supported Not supported Setting up the MSA To set up the MSA for use as an external array connected to the XP12000/XP10000/SVS200, perform the following steps: 1. Define the MSA Array Object. 2. Define the MSA LU. 3. Use MSA Selective Storage Presentation to institute LUN security.
presentation to the XP12000/XP10000/SVS200. For example, suppose you want to create a 40 GB (40960 MB) LU on the MSA for use as XP12000/XP10000/SVS200 external storage. If you request only the exact size needed, the ACU optimizes the LU to a size of 40959 MB, which is 1 MB smaller than needed. In this case, the optimization algorithm the ACU uses can be compensated for by specifying a size of 40963 MB, which results in the correct size of 40960 MB (40 GB).
Configuring MSA1000/1500 as external arrays
Index A Active/Standby (A/S) controllers 27 ACU (Array Configuration Utility) 156 ACU Selective Storage Presentation (SSP) 157 Add LU (Auto) operation 80 Add LU operation 77 Add LU window 73 alternate paths adding to multiple external LUs 91 canceling 91 changing 91 defining 22, 86, 89 deleting to multiple external LUs 93 EVA arrays 139 LU Operation pane 56 Path Setting window 86 ports 76 priority of 22, 25, 89 Select Paths pane 76 settings 75 switching I/O execution paths to 23 XP12000/XP10000/SVS200 and E
Disconnect Volume command disconnecting external LUs 98, 100 powering arrays on and off 27, 28, 29 restrictions 35 troubleshooting 125 Discovery operation, troubleshooting 125 disk errors, NAS Blade system 108 document conventions 10 feedback 11 prerequisites 9 related documentation 9 E emulation types Add LU window 74 Auto Map Setting window 81 capacities 32, 141 HDD types 36 remote command devices 117 restrictions 32 setting 21 errors NAS Blade system 108 errors, External Storage XP 121 ES XP cache mode
external LUs Add LU 77 alternate paths, adding to multiple 91 alternate paths, defining 22, 86 alternate paths, deleting to multiple 93 Business Copy XP operations 41 capacities 32, 141 configuring 71 connection status 100 Continuous Access XP Journal operations 40 Continuous Access XP operations 39 defined 13 Delete LU command 104 Device List 58 disconnecting 98 emulation type, setting 74, 81 groups 20 HDD types 36 LU Operation pane 56 mapping 73 mapping all at once 78 mapping multiple 80 mapping restricti
LUN Security XP Extension 38 LUs.
restoring external array volumes 101 external LU volumes 102 external LUs 96, 100, 101 LDEV Restore 101 NAS Blade system arrays 108 paths to external LUs 102, 104 SVS200 138 TagmaStore subsystems 133 Thunder 9500V Series subsystems 130 XP12000/XP10000 arrays 134 XP512/XP48 arrays 136 restrictions External Storage XP operations 32 Initiator/External MIX mode 120 remote command devices 117 retention term 86 S Select LDEV window 83 Select Paths pane 75, 76 Selective Storage Presentation (SSP) 157 settings 19
X XP Remote Web Console about 13 troubleshooting 121 XP1024/XP128 arrays, connecting 135 XP12000/XP10000 arrays, connecting 134 XP12000/XP10000/SVS200 arrays about 147 alternate paths 153 configuring 147 creating new EVA host objects 148 expanded configuration 148 external ports, defining 150 external storage LDEVs 151 HA requirements 147 performance considerations 153 troubleshooting 154 Vdisks 149 XP512/XP48 arrays, connecting 136 164
