HP StorageWorks External Storage XP user guide for the XP12000, XP10000, SVS200 Part number: T1706-96009 Eighth edition: September 2007
Legal and notice information © Copyright 1999, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . Supported storage platforms and firmware Intended audience . . . . . . . . . . Prerequisites . . . . . . . . . . . . Related documentation . . . . . . . . Document conventions and symbols . . HP technical support . . . . . . . . . Subscription service . . . . . . . . . HP web sites . . . . . . . . . . . . Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determining, setting, or changing the external LU cache mode . . . Determining if the cache mode is disabled . . . . . . . . . Changing the cache mode . . . . . . . . . . . . . . . . Collecting device information . . . . . . . . . . . . . Deleting and remapping the external LU . . . . . . . . . Partitioning cache for external storage . . . . . . . . . . . . . For example, Company A uses: . . . . . . . . . . . . . .
Changing the cache mode setting of the external LU . . . . . . . . . . . . . . . . . . . . . Changing the cache mode of all external LUs in an external array . . . . . . . . . . . . . . . . Changing the cache mode of an individual external LU . . . . . . . . . . . . . . . . . . . . Stopping the use of paths to an external LU by specifying an external array's WWN (Disconnect Paths) Restoring paths to an external LU by specifying an external array's WWN (Check Paths) . . . . . .
C Adjusting volume capacity for copy pair setting . . . . . . . . . . . Copying data from external arrays (using external LUs as P-VOLs) . . . . . . . . . . . . . . . . . Copying data to external arrays (setting external LUs as S-VOLs) . . . . . . . . . . . . . . . . . D Configuring MSA1000/1500 as external arrays . . . . . . . . . . . Configuring external array LUs, host mode, and ports Connecting MSA1000/1500 . . . . . . . . . . Setting up the MSA . . . . . . . . . . . . . . Defining MSA array objects .
Figures 1 ..External Storage XP concept . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2 ..Example of alternate path configuration . . . . . . . . . . . . . . . . . . . . . . 25 3 ..Example of alternate path configuration using two switches . . . . . . . . . . . . . . 25 4 ..Example of incorrect alternate path configurations . . . . . . . . . . . . . . . . . 26 5 ..Alternate path mode is Multi mode . . . . . . . . . . . . . . . . . . . . . . . . 27 6 ..
38 ..Port Operation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 39 ..Port Operation list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 40 ..Preset Detail window (changing port attribute) . . . . . . . . . . . . . . . . . . . 76 41 ..Overview of configuring external LUs . . . . . . . . . . . . . . . . . . . . . . . 77 42 ..Add LU window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 ..Select Paths pane . . . . . . . . . . . . . . . . .
Tables 1 ..Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 ..Storage arrays that can be connected as external arrays . . . . . . . . . . . . . . . 12 18 3 ..External Storage XP requirements . . . . . . . . . . . . . . . . . . . . . . . . . 21 4 ..When external LU's emulation type is OPEN . . . . . . . . . . . . . . . . . . . . 41 5 ..When external LU's emulation type is for mainframes . . . . . . . . . . . . . . . . 41 6 ..
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 Unless otherwise specified, the term array in this guide refers to the followin
• 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) You can find these documents on the HP manuals web site: http://www.hp.com/support/manuals. Document conventions and symbols Table 1 Document conventions Convention Element Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
• • • • • • Technical support registration number (if applicable) Product serial numbers Product model names and numbers Error messages Operating system type and revision level Detailed questions For continuous quality improvement, calls may be recorded or monitored. Subscription service HP recommends that you register your product at the Subscriber's Choice for Business web site: http://www.hp.com/go/e-updates.
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.
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 Storage array Notes HP StorageWorks XP12000 Disk Array • In External Storage XP panes, the array appears as “12000”. • Alternate paths are in Multi mode (meaning that dynamic load balancing across multiple active paths is enabled). HP StorageWorks XP10000 Disk Array • In External Storage XP panes, the array appears as “10000”. • Alternate paths are in Multi mode.
Storage array Notes 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. • In this user guide, the arrays appear as “Lightning 9900V subsystem”.
Storage array Notes SANRISE9900V series subsystem • “SANRISE99xxV series subsystem” indicates the SANRISE9970V and SANRISE9980V. • 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.
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.
• • • • External array and LUs to map to the internal LDEVs (see External LU to be mapped) Configuration of external LU groups (see External LU groups) Configuration of external LU attributes (see External LU attributes set by mapping) Configuration of alternate paths (see Alternate paths) External ports Local array ports used for External Storage XP must be set to a designation of External.
The following are the external LU's attributes: • Emulation type Set the mapped LU's emulation type by selecting any emulation type from the drop-down list. However, if you plan to use the mapped LU for 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.
NOTE: If you set the emulation type of the mainframe system for the mapped LU, host I/O is always propagated asynchronously to the external LU regardless of the Cache Mode setting. • CLPR When using XP Disk/Cache Partition to partition cache memory, set the cache logical partition (CLPR) used for accessing the mapped LU. You can also specify whether the CU selected at mapping is restricted to the storage management logical partition (SLPR) the CLPR belongs to.
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. In this example, two ports from different XP12000/XP10000/SVS200 clusters are specified in the local array, thereby making it possible to configure an alternate path for high availability.
Figure 4 Example of incorrect alternate path configurations Examples of switching I/O execution paths to alternate paths There are two alternate path modes: Single mode and Multi mode. This section describes examples of the performance when the I/O execution path switches to the alternate path for each path mode. For more information about path status, see Adding alternate paths by selecting multiple external LUs (Add Paths).
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.
NOTE: As you turn the local array's power off, all data for the external LU in the local array's cache memory is written in the external LU (all data is destaged). To power local arrays on CAUTION: When you want to turn on both the local array and the external array, you first need to turn on the external array, and then turn on the local array. 1. Power on the external array containing the external LU mapped as a local array internal LDEV. 2. Turn on the local array's power.
2. Execute the Check Paths & Restore Vol. command. For instructions, see Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.). CAUTION: When powering the external array off after executing the Disconnect Subsystem command, you cannot access the mapped external LU from the local array when you initially turn on the external array. You must execute the Check Paths & Restore Vol. command to resume using the mapped external LU. The Check Paths & Restore Vol.
Using mapped external LUs from the host connected to the local array The following sections describe examples of using the mapped external LU from the host connected the local array. Writing new data to mapped external LUs Figure 9 shows an example of writing new data in the mapped external LU from the host connected to the local array. 1. Use the External Storage XP GUI to map the LU in the external array as an internal LDEV of the local array.
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.
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. 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.
• If you plan to use the mapped external LU from the mainframe OS (volume is mapped with a 3380-x or 3390-x mainframe emulation type), you must select an external LU that consists of one LDEV or you must first adjust the capacity of the external LU to be mapped. If multiple LDEVs exist in one external LU and if numerous I/Os are made to these LDEVs, the read and write commands might timeout. When the commands timeout, the SIM (21D2xx) is reported.
• 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 use the mapped external LU for the copy source or copy destination volume for a Flex Copy XP pair, set the emulation type to OPEN-V when mapping the volume.
• Attributes originally set for an external LU on the external array side (such as port security, LUN security, and Volume Retention Manager attributes) are not kept when the external LU is mapped as a local array internal LDEV. To keep the original attributes, set those attributes on the mapped external LU from the local array side. • If you mapped the external LU and previously set the VMA of LUN Security XP Extension in that volume, the former VMA setting is superseded when you map the volume again.
• You cannot execute the Disconnect Subsystem or 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 displayed information for Ex-Dev. Status in the Device list becomes Cache Destage. Even if there is no data left in cache memory, the displayed status stays Cache Destage until the Disconnect Subsystem or Disconnect Volume command processing is complete.
• If the host connected to the local array issues too many I/Os for the external array to process, commands from the host might time out. When the amount of I/Os from the host to the external LU exceeds the maximum amount of I/Os the external array can accept, commands from the host to the local array might time out. As you configure the system using external LUs, consider the external array's I/O capacity.
• If you use the CVS function to create LDEVs from an external XP LU, the created LDEVs' attributes (IO Suppression mode and Cache Mode) are the same as the source external LU's. • You cannot combine the local array internal LDEV and external LU to form a LUSE volume. • Do not combine LDEVs of multiple external LUs to create a LUSE volume. You can only use LDEVs in the same external LU to set LUSE volumes. • You cannot combine external LUs that have different IO Suppression modes to form a LUSE volume.
You 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. • If you previously mapped the external LU and set the VMA of LUN Security XP Extension in that volume, the previous VMA setting is overwritten when you map the LU again.
For more information, see Mapping external LUs (Add LU). CAUTION: To migrate existing data in the mapped external LU to a local array volume using Auto LUN XP or Business Copy XP, as shown in Figure 14, set the local array's emulation type to OPEN-V when mapping the LU. Only OPEN-V emulation can be used to read existing data in the external LU from the local array side.
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. If you select a mainframe-system emulation type (such as 3390-3), go to step 3. For more information, see Mapping external LUs (Add LU). 2.
Figure 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. Select the mapped volume's emulation type as required. If you select an open-system emulation type (such as OPEN-V), go to step 2. If you select a mainframe-system emulation type (such as 3390-3), go to step 3.
Using external LUs for Business Copy XP operations Figure 17 shows an example of using an external LU for Business Copy XP operations. The mapped external LU is set as the Business Copy XP pair's S-VOL, and the local array internal LDEV is set as the 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.
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. For more information, see Mapping external LUs (Add LU). 2.
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, 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.
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.
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.
• External volumes and internal XP volumes, except for configurations where all external storage LUNs have cache disabled and do not have any external storage devices using data mirroring or migration products NOTE: All HP 200 Storage Virtualization System volumes are external. Partition SVS200 cache according to the other recommendations made in this section.
Table 7 Recommended indiv. CLPR cache size for ext. stor. on HP stor. virt. sys. External volume capacity assigned to CLPR CLPR0 Additional CLPRs Less than 1 TB 4 GB 4 GB 1 TB <= capacity < 16TB 8 GB 4 GB 16 TB <= capacity < 20 TB 12 GB 4 GB 20 TB <= capacity < 128 TB 16 GB 4 GB 128 TB or more 24 GB 8 GB Creating cache partitions Ensure the XP Disk/Cache Partition license is installed, you have Administrator authority on the array, and you are in Modify mode in XP Remote Web Console.
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).
Figure 26 Partition Definition pane, Paste Parity Group option e. Click Apply. f. Repeat step 7b through step 7e until you have allocated the external storage groups to the appropriate CLPRs according to the plan you created after reading Partitioning cache for external storage. For complete information about creating SLPRs and CLPRs, see the HP StorageWorks XP Disk/Cache Partition user guide.
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.
• WWN Entry: Number of LUs that are currently used in the external array out of the maximum theoretically possible (15,360). Displayed in the format The number of connected ports/16,384 (the number of ports which can be connected). • Total number of WWNs: Number of external array ports that are connected. • Total number of Paths: Number of paths set between the local array and external array. • Preset list Displays the contents of settings that were set by operations started on the LU Operation pane.
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 LU status Description Normal LU status is normal. Unknown LU status has yet to be ascertained. Blockade I/O traffic to the LU is not permitted. Warning FC path or paths have an abnormal status. Check the status of the paths. Checking 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.
• 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.
• Product name of the connected external array When selected, displays the name of the external array for which the connection setting is already completed in the tree under External Devices. • WWN of the external array When selected, displays WWNs identifying ports on the connected external array in the tree under the name of the external array product. WWN list Displays information about the connection status of the local array and external array corresponding to the item selected in the WWN tree.
• Mode: How alternate paths between the local array and external array work. Alternate path modes include: • Single: Uses only the path with the highest priority (primary path) to execute I/O to the external LU. When an error occurs in the primary path, the path with the second highest priority is used. • Multi: Uses all set paths at the same time to execute I/Os to the external LU, distributing the work load. • Status: Status of the path set in the port identified by the WWN.
• Internal error: Program error occurred, or there is a logical contradiction. • Timeout: Processing was retried because an abnormal reply (Response) was returned; however, processing was stopped by a timeout. • Standby: External array's port is standing by. Port status is normal, but cannot receive I/O. • Target error: Port failures, such as controller blockade, are detected on the external array side. • Checking: Process of checking the paths' defined configuration information is in progress.
Icon Description Port in Standard mode. Port in Initiator/External MIX mode. Port list Displays information about the ports and paths of the local array or external array, depending on the item selected in the Port tree. You can sort the list by displayed items. For instance, to sort the items by the port number, select Port on the list. Figure 34 Port list (External selected in Port tree) The displayed contents changes depending on the item selected in the Port tree.
• Disconnect: Connection to the external array or external LU was intentionally stopped using the Disconnect Subsystem or Disconnect Volume command. • Warning: There are paths whose status is not normal. Check the status of the paths. • Checking: Process of checking the defined configuration information of the paths is in progress. • Port number of the local array • Port: Port number of the local array selected in the Port tree.
• Unavailable: External array replied Unavailable. The external array demands to change the connected port. Once the status becomes Unavailable, the primary path changes to the alternate path that is in the Standby status. When the primary path changes, the status of the path becomes Normal. • Backoff: External array replied Backoff. The path status is waiting for recovery because a temporary error occurred in the external array's volume.
Figure 36 Preset Detail window (mapping operation) • Delete Cancels settings selected in the Preset list. Port Operation pane Use this pane to check port settings and set port attributes. This section describes items displayed in the Port Operation pane. For instructions, see Setting a local array's port attributes. Figure 37 Port Operation pane • Port Operation tree Displays information about the selected port in the Port list (right pane). You can select Subsystem, a port attribute, or a port number.
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). • Preset list Displays rows corresponding to the ports that are about to be acted upon. The contents displayed in the Preset list have not been applied to the local array yet.
When selected, displays ports designated as an RCU target (receiving) port (used for Continuous Access XP, TrueCopy for z/OS, Continuous Access XP Journal, Universal Replicator for z/OS, and so on). • Initiator/External When selected, displays ports for which the Initiator/External MIX mode is set. • Port number Displays ports assigned to each port attribute in the branch below each port attribute. External Storage XP uses ports set to external.
Maximum time allowed (in seconds) for an external array to perform a fabric login after being connected to a switch. This value is preset and cannot be changed. • PLI_TOV (Port Login Timeout Value) Maximum time allowed (in seconds) for the external array to perform a port login after being connected. This value is preset and cannot be changed. • Margin The sum of the FLI_TOV and PLI_TOV values.
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.
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. Use the Add LU or Auto Map Settings pane to map the external LU as an internal LDEV (Mapping external LUs (Add LU)). 7.
4. Click Apply. A confirmation message appears. 5. Click OK. The port attribute setting is applied to the local array, and the new setting appears in the Port Operation list. If an error occurs, the failed setting and an error code appears in the Preset list. To view error messages, right-click the failed row, and select Detail. 6. Set the topology for the connection configuration. When an FC switch is connected, set Fabric to Enable. When a switch is not connected, set Fabric to Disable, and specify FC-AL.
Figure 42 Add LU window • Vendor External array's vendor. • Product External array's product name. • Serial External array's product serial number. • WWN World Wide Name of the external array port used for connecting to the local array. • LUN LU number of the external LU. • Device External LU's device name. • Ex-Dev. info. External array information. When the external array is an XP1024/XP128 or TagmaStore Workgroup Modular Storage (WMS) array, an asterisk (*) appears.
External LU's extended identifying information. This information is used for identifying logical volumes in the EVA array. For more information, see Identifying logical volumes of EVA arrays (using Characteristic 2). • ExG (1-16384) Group number of the connected external LUs. You can specify any decimal value from 1 to 16384. The E displayed outside the text box is the capital letter of the external LU group.
CAUTION: To set IO Suppression mode to Enable, Flex Copy must be installed. • Cache Mode Specifies if the write I/O from the host is propagated synchronously or asynchronously to the external storage device (see External LU attributes set by mapping). HP recommends that you set cache mode to Disable. NOTE: • If you set the IO Suppression mode to Enable, Cache Mode becomes Disable. • If you select Disable, Cache LUN XP's bind mode cannot be set.
Maps all external LUs listed in the CU:LDEV list at one time. When you click Linear and then select an internal LDEV on the LDEV map, External Storage XP automatically selects from the LDEV map the same number of internal LDEVs as external LUs listed in the CU:LDEV list, starting at the internal LDEV you selected. The LDEV numbers of the selected internal LDEVs are sequential. When Interval is set, mapping is done at the specified number of intervals.
Figure 43 Select Paths pane • Port Local array ports. You can set alternate paths for the selected port. One of the following icons appears for each port: Icon Description Port in Standard mode. Port in Initiator/External MIX mode. • Selected Paths External array port for which you can set the alternate path connecting to the local array port selected in the Port list. By default, all ports that can be set as alternate paths appear. The WWN identifying the external array port appears.
3. In the Device tree, select the port (WWN) you want to connect from the WWNs listed in the Device. External LUs that can be connected from the external array port (WWN) selected in the tree appear in the Device list. 4. Right-click the external LU you want to map as an internal LDEV in the Device list, and select Add LU. The Add LU window appears. 5. Select the internal LDEV that is mapped to the external LU selected in the Device list on the Add LU window.
Figure 44 Add LU pane (mapping using the Linear button) • To map one external LU to another internal LDEV: After automatically mapping the external LU using the Linear button, release the Linear button, and map the external LU individually (Figure 45). 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.
8. Click OK. The Add LU pane appears. 9. When all settings are complete on the Add LU window, click OK. • If you need to set the SSID, the SSID window appears. Go to step 10. Figure 46 SSID window • If the SSID setting is not necessary, the Add LU window closes, and the LU Operation pane appears. Settings appear in blue italics in the Device tree and Device list. Contents specified in the Add LU window appear in the Preset list.
If you already stopped the application, go to step 14. If you have not stopped the application, click Cancel to close the message pane, stop the application, and retry the operation. 14. Click OK. A confirmation message appears. 15. Click OK. The mapping set in the Add LU window is applied to the local array, and the specified contents appear in the Device list. If errors occur during the external LU mapping operation, failed settings and error codes appear in the Preset list.
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.
number. To display only CUs defined for the selected SLPR, select the Limited check box. To display all CUs, regardless of the SLPR, clear the check box. By default, the Limited check box is selected. • Select LDEV button Displays the Select LDEV window (Figure 49) where you can select the first CU:LDEV number in the series. • Select Paths button Displays the Select Paths pane (Figure 43).
• Interval Interval of the CU:LDEV number for mapping each volume. When two or more LDEVs are created from one external LU and mapped, the CU:LDEV number is set at intervals specified in each created LDEV. For example, set the interval as follows: • • • • In the Device list, select three external LUs. In Create LDEVs on the Auto Map Setting window, select 3 (nine LDEVs are created). In Interval, select 1. Set the starting CU:LDEV number to 00:00.
9. If you do not want to automatically set the primary and alternate paths, but you want to specify the paths to be set as candidates for the primary and alternate paths, click Select Paths. The Select Paths window appears. To automatically set alternate paths, go to step 12. 10. Select the path and exclude it from the list of the candidates for the primary and alternate paths. For instructions, see Mapping external LUs individually (Add LU). 11. Click OK. The Auto Map Setting window appears. 12. Click OK.
For more information about items displayed in the VMA Information pane, see the HP StorageWorks LUN Security XP Extension user guide. Figure 50 VMA Information pane • Vendor External array's vendor. • Product External array's product name. • LUN LU number of the external LU. • Attribute Select from the following access attributes: • Read/Write: Read and write operations can be performed on the volume. • Read Only: Only read operations can be performed on the volume. • Protect: You cannot access the volume.
• Hyphen (-): The RAID Manager XP user has not assigned a mode to the logical volume. • Extent Indicates whether extents are set. • Asterisk (*): Extents are set. • Hyphen (-): Extents are not set. • Used Volumes Licensed capacity for 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.
• Single: Uses only the path with the highest priority (primary path) to execute I/Os to the external LU. If selected, the second-highest priority alternate path is enabled only if a maintenance operation or failure affecting the primary path occurs. That is, the external array contains Active/Passive (for example, MSA) or Asymmetrical Active/Active controllers (for example, Hitachi 9500V). • Multi: Uses all of the set paths at the same time to execute I/Os to the external LU, distributing the workload.
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.
Selected rows appear in blue italics in the Device list. Specified contents appear in the Preset list. To check details on intended operations, right-click the setting in the Preset list, and select Detail. To cancel settings, right-click the setting in the Preset list, and select Delete. 8. Click Apply. A confirmation message appears. 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.
Figure 53 Overview of Operation to Replace All the Current Alternate Paths with Newly-added Alternate Paths To replace all the current alternate paths (A and B) with newly-added alternate paths (C and D): 1. Execute the Disconnect Paths command on the alternate path A (see section 5.16). 2. Disconnect the cable which the alternate path A uses, and connect the cable which the alternate path C uses. 3. Cancel the configuration of the alternate path A, and add the alternate path C (see section 5.5.4). 4.
8. Cancel the configuration of the alternate path B, and add the alternate path D (see section 5.5.4). 9. Click the Apply button to apply the settings of the alternate paths B and D. 10. Make sure the status of the alternate path D is Normal.
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. • Unselected Paths External array ports (WWNs) that can configure the path connecting with the local array port selected in the Port list.
Deleting alternate paths by selecting multiple external LUs (Delete Paths) You can delete paths for multiple volumes that belong to the same external LU group at one time. To delete alternate paths for multiple external LUs at one time, select the alternate path in the Delete Paths window, check the setting in the Path Setting window, and apply the setting to the array. CAUTION: At least one normal path must be set on each mapped external LU.
• Release Moves WWNs selected in Selected Paths to Unselected Paths. • OK Saves settings in the Delete Paths window, closes the Delete Paths window, and displays the Path Setting window. • Cancel Cancels all of the settings in the Delete Paths window, and closes the window. To delete paths for multiple volumes at one time: 1. Select the LU Operation tab. The LU Operation pane appears. 2. In the Device tree, select an external LU group number.
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.
• Capacity: External LU's capacity. • Status: External LU's status. Possible values: Normal, Unknown, Blockade, Warning, and Format. Warning indicates that some alternate paths are blocked. Format indicates the external LU is currently being formatted. • View all LUs Displays information about all external LUs in the LDEV list. • View all Volumes When the external LU is part of a LUSE volume, displays all LDEVs that make up the LUSE volume in the LDEV list.
5. In the LDEV list, right-click the row of the external LU to be restored, and select Restore. Figure 57 Shortcut menu of the LDEV Information window The Status column in the selected external LU row changes to Restore. 6. Click OK. The LDEV Information window closes, and the LU Operation pane appears. Specified contents appear in blue italics in the Device list and appear in the Preset list. To check setting details, right-click the setting in the Preset list, and select Detail.
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. Status column in the Device list changes to Cache Destaging.
If errors occur during disconnect operations, failed operations and error codes appear in the Preset list. To check error messages, right-click the failed operation row, and select Detail. CAUTION: To access the external LU after executing the Disconnect Subsystem command, you must execute the Check Paths & Restore Vol. command. Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.
Restoring external LUs individually (Check Paths & Restore Vol.) 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 resume the connection to the local array, and select Check Paths & Restore Vol. The selected external group number in the Device tree and the selected external LU in the Device list appear in blue italics.
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.
6. Click the array whose cache mode you want to change in the Device list, right-click to select the Change Cache Mode command, and then select Enable or Disable. The selected array is displayed in blue and italics in the Device tree and Device list. The contents of the selected array are displayed in the Preset list. To check the details of the selected array, select an item from the Preset list and right-click to select the Detail command.
2. In the WWN tree, select the product name of the connected external array. The WWN of all ports that are connected to the local array and are used appear in the WWN list. 3. In the WWN list, select WWN you want to stop using. When you select the WWN identifying the external array's port in the list, you can stop the use of all ports of the local array connected to the port at one time. 4. Right-click, and select Disconnect Paths. Selected items appear in blue italics in the WWN tree and WWN list.
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). • 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. • 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.
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).
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. • Whether the Disconnect Subsystem or Disconnect Volumes command was executed. All data in cache memory must be written into the mapped external LU using the Disconnect Subsystem or Disconnect Volume command.
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.
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. Confirm that the connection between the local array and the external array is normal. 5. Start NAS OS 1 (NAS channel adapter's OS) and NAS OS 2 using LUN Manager. NOTE: The NAS OS can also be started from the SVP.
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: a. Release the differential-data storage device using NAS Sync Image. b. Delete the NFS share, CIFS share, and file system using NAS Blade Manager. 3. Change resource group 1's execution node to node 2 using NAS Blade Manager (failover). If resource group 1's status is Offline, this operation is not required. 4.
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. command using External Storage XP.
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).
Errors in all paths to the external array The following sections describe the recovery procedures for two examples when the error occurs in all paths connected to the external array. If each node uses a different external array In the configuration in Figure 64, all of the NAS Blade system's user LUs are volumes in the external array. Each node uses the volume of a different array. All of node 1's user LUs are volumes in external array 1.
3. Perform a forced stop operation using NAS Blade Manager for resource group 1, which displays the status as an srmd executable error. 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. To release the blocked status of node 2's file system, perform the following operations: a. Change resource group 2's execution node to node 1 using NAS Blade Manager (failover). b.
Figure 65 If both nodes use the same 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. Perform the forced stop operations using NAS Blade Manager for resource group 1 and resource group 2.
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 66 shows an example.
• XP10000 Disk Array • HP 200 Storage Virtualization System • XP1024/XP128 Disk Array • TagmaStore™ Universal Storage Platform subsystem • TagmaStore™ Network Storage Controller subsystem • TagmaStore™ Adaptable Modular Storage subsystem • TagmaStore™ Workgroup Modular Storage subsystem • Lightning 9900V series subsystem • Thunder 9500V series subsystem • SANRISE Universal Storage Platform subsystem • SANRISE Network Storage Controller subsystem • SANRISE Adaptable Modular Storage subsystem • SANRISE Workgr
Device information about the command device that the remote command device reports to the host includes: • Serial number • Vendor • Device name NOTE: The device name reported to the host is the same as the one displayed in the Device column of the Device list. For the device names reported to the host, see Table 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.
Using Continuous Access XP or Continuous Access XP Journal with remote command devices To use Continuous Access XP or Continuous Access XP Journal with a remote command device, you would traditionally need two different kinds of ports: an initiator port for Continuous Access XP or Continuous Access XP Journal, and an external port for 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.
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. 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.
Error Corrective action The path status that requires the action appears in the Alternate Path list on the Path Setting window (see Setting alternate paths for external LUs). The following rows describe path status values displayed in the Alternate Path list and corrective actions for each status value. See Notes on connecting external arrays for notes on connection settings and examples of recovery procedures, and then take the corrective action. 138 Unknown Status: The path status is unknown.
Error Corrective action Busy Status: The external array's status is BUSY. Corrective action: The external array's port is still recognized. Check the external array's settings and the load on the external array (for example, check whether the configuration assigns too much load on the external array). If you cannot restore the path, contact your HP account support representative. LDEV reserved Status: The external array's status is Reserved.
Error Corrective action The Discovery operation cannot be performed. 140 Internal error Status: A program error occurred, or there is a logical contradiction. Corrective action: Contact your HP account support representative. Timeout Status: Processing was retried because an abnormal reply (Response) was returned, but processing has stopped due to a timeout. Corrective action: The external array's port of is recognized.
Error Corrective action The external LU is blocked. Correct the error and retry the operation. The source of the error could be any one of the following: • All set paths are blockaded (or not connected). • The external LU's attribute is not set to Read/Write. • The external LU is blockaded by an error. The Check Paths & Restore Vol. command has executed and you have waited more than 10 minutes, but the device's status does not change from Checking.
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.
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. Dual Active Mode Specify this parameter when the Thunder 9500V subsystem is in the two-controller configuration. NOTE: Be sure to specify that Data Share Mode will be used. • Hot Stand-By Mode Do not specify this parameter.
NOTE: When using the Thunder 9500V subsystem as an external array, the following versions are recommended. If you use a 9500V subsystem whose version is earlier than the following versions, the SATA drive's information might not be displayed correctly. • For Thunder 9530V, Thunder 9520V, Thunder 9570V: version 0658 or later • For Thunder 9580V, Thunder 9585V: version 1658 or later Relation btw. ser. nums. in the Dev. list on LU Op. pane & Thunder 9500V subsys. mod.
Table 15 Relationship between ports' WWNs and controllers (Thunder 9500V subsystems) Model Controller Port's WWN 9570V 9530V 9520V Controller 0 XXXXXXXXXXXXXXX0 XXXXXXXXXXXXXXX1 Controller 1 XXXXXXXXXXXXXXX2 XXXXXXXXXXXXXXX3 Controller 0 XXXXXXXXXXXXXXX0 XXXXXXXXXXXXXXX1 XXXXXXXXXXXXXXX2 XXXXXXXXXXXXXXX3 Controller 1 XXXXXXXXXXXXXXX4 XXXXXXXXXXXXXXX5 XXXXXXXXXXXXXXX6 XXXXXXXXXXXXXXX7 9580V 9585V NOTE: In WWNs, X is an arbitrary number or character.
Table 16 Path status and examples of recovery procedures (Thunder 9500V subsystems) Path status Examples of recovery procedures External device setting changed LUN Manager may have changed the LU paths' settings. Check the LU paths' settings. If the LU paths' settings changed, change the settings back to the ones used when the volume was mapped. Or use External Storage XP to perform the Delete LU operation, and perform the Add LU operation again.
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.
Table 17 System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems) Pane name Parameters Boot Options Start Attribute Parameter setting • Single Mode Specify this parameter when the TagmaStore AMS or TagmaStore WMS subsystem is in the one-controller configuration. • Dual Active Mode Specify this parameter when the TagmaStore AMS or TagmaStore WMS subsystem is in the two-controller configuration.
Rel. btw. ser. numbs. in Dev. list on the LU Op. pane & T-Stor. AMS & T-Stor. WMS subsys. mods. 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. Table 18 Relation btw. ser. numbs. & subs. mods. (TagmaStore AMS & TagmaStore WMS subs.
NOTE: In WWNs, X is an arbitrary number or character. Ports in the same apparatus have identical values. Path status and examples of rec. proce. (TagmaStore AMS and TagmaStore WMS subsys.) 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 and this table to recover the path status. If you cannot restore the path, contact your HP account support representative. Table 20 Path stat. & ex. of rec.
Connecting XP12000/XP10000 Disk Arrays When connecting an XP12000/XP10000 Disk Array as the external array, you must set the external array port host group for one of two types of Windows hosts (host mode 0C: Windows, host mode 2C: Windows Extension). Also, the port attribute must be the target or RCU target port. Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) Table 21 shows examples of recovery procedures when the path status is not normal.
Table 21 Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) Path status Examples of recovery procedures External device setting changed LUN Manager may have changed the LU paths' settings. Check the LU paths' settings. If the LU paths' settings changed, change the settings back to the ones used when the volume was mapped. Or use External Storage XP to perform the Delete LU operation, and perform the Add LU operation again.
Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) Table 22 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 your HP account support representative.
Path status and examples of recovery procedures (XP512/XP48 Disk Arrays) Table 23 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 your HP account support representative.
Path status and examples of recovery procedures (SVS200) Table 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 and this table to recover the path status. If you cannot restore the path, contact your HP account support representative.
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. If you search for logical volumes by specifying the WWN that indicates EVA Port A in the configuration, such as in Figure 69, logical volumes named LUN 1 and LUN 2 are found for both HostGroup-1 and HostGroup-2.
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 70 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 70 LDEV capacity Figure 71 shows how to determine the volume capacity using the example of the OPEN-3 case. Figure 71 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 Minimum data area capacity Base data area capacity Control information area capacity blocks cylinders blocks cylinders blocks cylinders 3380-3 72,000 50 4,808,160 3,339 10,080 7 3380-3A 72,000 50 4,808,160 3,339 10,080 7 3380-3B 72,000 50 4,808,160 3,339 10,080 7 3380-3C 72,000 50 4,808,160 3,339 10,080 7 3380-K 72,000 50 3,823,200 2,655 10,080 7 3380-KA 72,000 50 3,823,200 2,655 10,080 7 3380-KB 7
Table 27 Volume capacity information for each emulation type Maximum number of LDEVs when maximum capacity of external LU is mapped1 Base LDEV capacity (blocks) Minimum LDEV capacity (blocks) Maximum capacity of external LU (blocks) blocks cylinders blocks cylinders blocks cylinders 3380-3 4,818,240 3,346 82,080 57 1,207,933,920 838,843 250 3380-3A 4,818,240 3,346 82,080 57 1,207,933,920 838,843 250 3380-3B 4,818,240 3,346 82,080 57 1,207,933,920 838,843 250 3380-3C 4,818,
Maximum number of LDEVs when maximum capacity of external LU is mapped1 Base LDEV capacity (blocks) Minimum LDEV capacity (blocks) Maximum capacity of external LU (blocks) blocks cylinders blocks cylinders blocks cylinders 3,674,880 - 84,960 - 940,769,280 - 256 OPEN-L 71,202,240 - 71,202,240 - 1,139,235,840 - 16 OPEN-V – - 96,000 - 4,294,967,296 - 1 Emulation type OPEN-K 1This number refers to the number of LDEVs when an external volume with maximum capacity is mapped.
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.
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. 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.
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). Because you cannot bypass or disable the optimization algorithm, you must compensate for this optimization so that MSA LUs are created at the correct size.
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. For more information about configuring the MSA using the ACU, see the ACU Online User Guide.
Index A Active/Standby (A/S) controllers, 30 ACU (Array Configuration Utility), 168, 168 ACU Selective Storage Presentation (SSP), 169 Add LU (Auto) operation, 88 Add LU operation, 84 Add LU window, 79 alternate paths adding to multiple external LUs, 102 canceling, 100 changing, 100 defining, 24, 95, 98 deleting to multiple external LUs, 104 EVA arrays, 157 LU Operation pane, 61 Path Setting window, 95 ports, 84 priority of, 24, 28, 98 Select Paths pane, 83 switching I/O execution paths to, 26 applications
Disconnect Subsystem command disconnecting external LUs, 109 powering arrays on and off, 30, 32 restrictions, 40 troubleshooting, 141 Disconnect Volume command disconnecting external LUs, 109, 111 powering arrays on and off, 31, 32 restrictions, 40 troubleshooting, 141 Discovery operation, troubleshooting, 140 disk errors, NAS Blade system, 123 document conventions, 12 prerequisites, 11 related documentation, 11 documentation HP web site, 12 providing feedback, 13 E emulation types Add LU window, 81 Auto
external LUs Add LU, 84 alternate paths, adding to multiple, 102 alternate paths, defining, 24, 95 alternate paths, deleting to multiple, 104 Business Copy XP operations, 48 capacities, 37, 159 configuring, 77, 77 connection status, 112 Continuous Access XP Journal operations, 46 Continuous Access XP operations, 45 defined, 15 Delete LU command, 118 Device List, 64 disconnecting, 109 emulation type, setting, 81, 89 groups, 22 HDD types, 41 LU Operation pane, 61 mapping, 79 mapping all at once, 85 mapping mu
LUs.
restoring external array volumes, 113 external LU volumes, 114 external LUs, 107, 112, 113 LDEV Restore, 113 NAS Blade system arrays, 122 paths to external LUs, 116, 118 SVS200, 156 TagmaStore subsystems, 151 Thunder 9500V Series subsystems, 146 XP12000/XP10000 arrays, 152 XP512/XP48 arrays, 155 restrictions External Storage XP operations, 37 Initiator/External MIX mode, 136 remote command devices, 133 retention term, 94 S S-VOLs, 166 Select LDEV window, 91 Select Paths pane, 82, 83 Selective Storage Pres
X XP Remote Web Console about, 15 troubleshooting, 137 176 XP1024/XP128 arrays, connecting, 153 XP12000/XP10000 arrays, connecting, 152 XP512/XP48 arrays, connecting, 154
