HP StorageWorks XP24000/XP20000 Auto LUN Software User Guide Abstract This guide explains how to balance system workloads and improve performance by migrating high-usage volumes to low-usage and high-performance disks using HP StorageWorks XP Auto LUN Software. Topics include how to create and execute migration plans manually and automatically and how to troubleshoot errors.
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of HP StorageWorks XP Auto LUN Software.....................................5 Overview of XP Auto LUN..........................................................................................................5 Volume Migration to Balance Workloads.....................................................................................5 2 About XP Auto LUN Operations....................................................................7 Components................................................
HP Websites..........................................................................................................................78 Documentation Feedback.........................................................................................................78 Glossary....................................................................................................79 Index.........................................................................................................
1 Overview of HP StorageWorks XP Auto LUN Software This chapter describes the following volume migration operations: • “Overview of XP Auto LUN” (page 5) • “Volume Migration to Balance Workloads” (page 5) Unless otherwise specified, the term storage system in this guide refers to the following disk arrays: • HP StorageWorks XP24000 Disk Array • HP StorageWorks XP20000 Disk Array The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer browser.
• In manual migrations, the system administrator specifies the volumes to be migrated and the migration destinations, and then executes migrations. • In auto migrations, XP Auto LUN automatically determines the volumes to be migrated and the migration destinations, and also executes migrations automatically. CAUTION: When an error condition exists in the storage system, resource usage can increase or become unbalanced.
2 About XP Auto LUN Operations This chapter provides an overview of XP Auto LUN operations.
NOTE: • You can also migrate an XP Thin Provisioning virtual volume or an external volume manually. However, you cannot examine the estimated usage rate after migration because the usage rate of an external volume cannot be collected. • OPEN-V volumes, other than the XP Thin Provisioning virtual volumes, might not be displayed as target volumes.
A, but are faster than parity groups in class C. Parity groups in higher classes (such as class A) provide faster disk access than parity groups in lower classes (such as class C). NOTE: In the storage system documentation, the terms class and HDD class mean the same thing. Figure 3 Classes and Parity Groups That Appear in the XP Auto LUN Window Next, you should choose a low-usage parity group from the fast parity groups. You can find low-usage volumes in the XP Auto LUN window (see Figure 4 (page 9)).
NOTE: When you use XP Auto LUN for the first time, you must reserve volumes for migration destinations in advance. These reserved volumes are marked with the icon. When you specify a volume to be migrated, icons of some reserved volumes ( ) that can be used as a migration icons. For details on reserving volumes for migration destinations, destination will change to the see “Reserving Migration Destinations for Volumes” (page 52).
NOTE: The storage system documents (including this manual) use the term source volumes to refer to volumes that should be migrated. The term target volumes is used for volumes that should become migration destinations. The XP Auto LUN operation consists of two steps: 1. 2. Copy the data on the XP Auto LUN source volume to the XP Auto LUN target volume (see Figure 6 (page 11)). Transfer host access to the target volume to complete the migration (see Figure 7 (page 12)).
Figure 7 Data Flow after a Volume Migration Operation NOTE: Immediately after a volume to be migrated and a volume of a migration destination replace each other, the RAID level before the replacement might be displayed or an internal error might occur in the storage system. In this case, click the Refresh button to update the display of the window. Automatic Volume Migration XP Auto LUN allows you to create and execute migration plans.
to any other parity group. Also, no volumes will be migrated to Grp1-1. For details on how to specify fixed parity groups, see “Setting a Fixed Parity Group” (page 55). NOTE: In a manual migration, a fixed parity group operates the same as a normal parity group. In this case, you can specify a volume in a fixed parity group as a target or source volume. 3. Review the disk usage limit for each HDD class. Each HDD class is assigned a disk usage limit by default.
class or to a parity group in the same HDD class with lower utilization. This storage-tuning method addresses and can eliminate bottlenecks in hard disk drive activity and also provides load balancing of hard disk drive usage. XP Auto LUN uses the estimated usage rates to verify each proposed auto migration, and will not perform a migration operation which might result in a target parity group exceeding the user-specified maximum disk usage rate.
Figure 10 Migrating a Volume Automatically to a Lower HDD Class The auto migration function can also move a volume from one parity group to another group of the same HDD class, forcing another volume out of the destination parity group. To move one volume into a parity group of the same HDD class, and force another volume out of that parity group, the auto migration function requires a minimum of 20% difference in estimated disk usage between the two volumes.
Specify the volumes that satisfy these conditions as the source and target volumes. The source and target volumes must be specified by LDEV ID, not VOLSER or port/TID/LUN. OPEN-V volumes other than XP Thin Provisioning virtual volumes might not be displayed as target volumes. If the Inquiry commands are executed on the volumes that are displayed as OPEN-V in the XP Auto LUN window, the replies from some volumes are OPEN-V and from other volumes are OPEN-0V.
Asynchronous Software volume is PSUS or PSUE, the volume can be used as a source volume. If not, the volume cannot be used as a source volume. ◦ When an XP Continuous Access pair is deleted from the MCU, the status of both volumes changes to SMPL, and both volumes can be used as source volumes. ◦ When an XP Continuous Access pair is deleted from the RCU, the status of the P-VOL changes to PSUS and the status of the S-VOL changes to SMPL, and both volumes can be used as source volumes.
Table 1 Pair Status in 3DC Multi-target Configuration When P-VOL of Universal Replicator for Mainframe Delta Resync Pair Is Set as an XP Auto LUN Source Volume Pair Name Status TrueCopy for Mainframe pair SUSPEND or DUPLEX Universal Replicator for Mainframe pair Any pair status can be acceptable Universal Replicator for Mainframe for delta resync operation pair HOLD or HLDE Table 2 Pair Status in 3DC Multi-target Configuration When S-VOL of Universal Replicator for Mainframe Delta Resync Pair Is Set
Table 3 Pair Status in 3DC Multi-target Configuration When P-VOL of XP Continuous Access Journal Delta Resync Pair Is Set as an XP Auto LUN Source Volume Pair Name Status XP Continuous Access pair PSUS or PAIR XP Continuous Access Journal pair Any pair status can be acceptable XP Continuous Access Journal delta resync pair HOLD or HLDE Table 4 Pair Status in 3DC Multi-target Configuration When S-VOL of XP Continuous Access Journal Delta Resync Pair Is Set as an XP Auto LUN Source Volume Pair Name S
Compatible XRC: If the status of a Compatible XRC pair volume is suspended because the session was canceled, the volume can be used as a source volume. XP Snapshot: Usage of XP Snapshot pair volume as a source volume depends on following conditions: ◦ S-VOL for an XP Snapshot pair cannot be used as a source volume. ◦ P-VOL for an XP Snapshot pair can be used as a source volume if the status of the XP Snapshot pair is PAIR.
CAUTION: If any of the following operations are performed on an XP Auto LUN source volume during migration, the volume migration process stops: ◦ Compatible XRC operation ◦ Concurrent Copy (CC) operation ◦ TrueCopy for Mainframe operation that changes the volume status to something other than suspended or simplex ◦ XP Continuous Access operation that changes the volume status to something other than PSUS, PSUE, or SMPL ◦ XP Continuous Access Journal operation or Universal Replicator for Mainframe o
◦ Volumes on which RAID Manager is performing volume migration operations ◦ Volumes that form an XP Snapshot pair ◦ Pool volumes used by XP Thin Provisioning ◦ Volumes that are in an abnormal or inaccessible condition (for example, pinned track, fenced) ◦ Volumes on which Quick Format is being performed ◦ System disks ◦ Quorum disks You can also reserve external volumes as target volumes. You can also reserve XP Thin Provisioning virtual volumes as target volumes.
• Manual migration execution. XP Auto LUN will not execute a manual migration operation when the current write pending rate for the storage system is 60% or higher. • If heavy workloads are imposed on your storage system: Avoid volume migration operations when heavy workloads are imposed on your storage system due to I/O requests from hosts. If you perform a volume migration, the migration could fail. If the migration fails, reduce the workloads on your storage system and then retry the volume migration.
products. The maximum increase may be as much as doubled. The amount of increase in the copy time depends on the number of pairs set to the program product.
How to Calculate the Number of Concurrent Migration Plans In using XP Auto LUN for manual volume migration, the number of migration plans that can be executed concurrently might be restricted. The number of migration plans that can be executed concurrently depends on the following conditions: • How much shared memory is available for differential tables: You can install additional shared memory for differential tables.
how to calculate the number of differential tables and pair tables used by programs other than XP Auto LUN, see the following manuals: • For XP Business Copy, see the HP StorageWorks XP24000/XP20000 Business Copy Software User Guide. • For ShadowImage for Mainframe, see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array. • For FlashCopy Mirroring and FlashCopy Mirroring V2, see the HP StorageWorks XP24000/XP20000 for FlashCopy Mirroring Software User Guide.
Table 9 Number of Control Cylinders According to Emulation Types (continued) Emulation Type Number of Control Cylinders 3390-3 6 3390-3A 6 3390-3B 6 3390-3C 6 3390-3R 6 3390-9 25 3390-9A 25 3390-9B 25 3390-9C 25 3390-L 23 3390-LA 23 3390-LB 23 3390-M 53 3390-MA 53 3390-MB 53 3390-MC 53 3390-LC 23 NF80-F 22 NF80-K 7 NF80-KA 7 NF80-KB 7 NF80-KC 7 Calculating Differential Tables Required for Open-System Volume Migration When you migrate open-system volumes, use the
Table 10 Total Number of Differential Tables Per Migration Plan Emulation Type Expression OPEN-3 Total number of differential tables per migration plan = ((X) ÷ 48 + (Y) × 15) ÷ (Z) OPEN-8 (X): The capacity of the volume to be migrated (kilobyte).1 OPEN-9 (Y): The number of control cylinders. See Table 11 (page 28). (Z): The number of slots that can be managed by a differential table (20,448).
volume and a target volume. In Table 12 (page 29), the XP Thin Provisioning virtual volume is called TP-VOL. Table 12 Combinations of Source Volumes and Target Volumes The source volume The internal volume as the source volume TP-VOL as the source volume 1 The internal volume as the target volume TP-VOL as the target volume Normal state Normal state A migration A migration plan can be plan can be created. created.1 Normal state A migration plan can be created.
Table 13 Relation between Increase of XP Thin Provisioning Virtual Volume Capacity and XP Auto LUN Operation XP Auto LUN Source Volume Volumes Increase of Capacity TP-VOL Capacity is increasing. XP Auto LUN Target Volume Volumes TP-VOL XP Auto LUN Operation Increase of Capacity Performing XP Auto LUN Operation Canceling XP Auto LUN Operation Cannot be performed1 Cannot be canceled2 Capacity is increasing.
3 Using the XP Auto LUN GUI This chapter describes the volume migration windows. • “Using the XP Auto LUN Windows” (page 31) • “Manual Plan Window of XP Auto LUN” (page 31) • “Auto Plan Window of XP Auto LUN” (page 39) • “Attribute Window of XP Auto LUN” (page 43) • “History Window of XP Auto LUN” (page 49) Using the XP Auto LUN Windows XP Auto LUN can be used to balance workloads among hard disk drives and thus remove bottlenecks from the system.
Figure 14 Manual Plan Window of XP Auto LUN The Manual Plan window displays the following: • Monitoring Term: Displays the monitoring period specified in the Performance Management window. XP Auto LUN analyzes disk usage information collected by Performance Monitor, XP Performance Control, or XP Auto LUN during the monitoring period, and then calculates estimated usage rates for the source and target parity groups after a proposed volume migration.
◦ indicates a RAID-5 parity group. The HDD class for this parity group is D. ◦ indicates a RAID-6 parity group. The HDD class for this parity group is A. ◦ indicates a RAID-6 parity group. The HDD class for this parity group is B. ◦ indicates a RAID-6 parity group. The HDD class for this parity group is C. ◦ indicates a RAID-6 parity group. The HDD class for this parity group is D.
External volume group icons: indicates an external volume group when it appears below the External Group folder. ◦ No volumes in this external volume group can be used as target volumes for manual migration. Figure 16 Information about External Volume Groups XP Thin Provisioning group icons: ◦ indicates an XP Thin Provisioning virtual volume group when it appears below the XP Thin Provisioning folder.
Ave. (%) Indicates the average usage rate for the parity group. If an exclamation mark (!) is displayed, the reported usage rate is likely to be inaccurate, because the volumes may be moved by XP Auto LUN or formatted by Virtual LVI or Open Volume Management. If a plus mark (+) is displayed before 0, such as +0, the usage rate is not 0, but it is less than 1. Max (%) Indicates the maximum usage rate for the parity group.
• Target button: After selecting the volume to migrate in the LDEVs, click the Target button. The list of LDEVs in the Target (Reserved) LDEV is displayed. • Target (Reserved) LDEV: A list of volumes that correspond to the Source LDEV and for which volume migration is possible is displayed. Select a row to specify the Target LDEV. Specify the target volume that is the destination volume in the text box.
Figure 18 Graph Window ◦ Source LDEV lets you specify the source volume (that is, the volume that you want to migrate). To the right of the text box is the following: – The current usage rate for the parity group that the source volume belongs to. – An estimated usage rate for the parity group after a proposed volume migration. If you specify an external volume as a source volume, XP Auto LUN cannot calculate the estimated usage rate after migration.
XP Auto LUN performs multiple migration plans concurrently. When a migration plan is finished, the plan will disappear from the list. A migration plan being executed by a program other than XP Auto LUN (such as RAID Manager) is also displayed in the list. Migration plans executed by other programs are not erased from the list automatically until the user finishes using the program that performed the volume migration.
XX is an ID that is given by this program. For example, 01 indicates RAID Manager, and 99 indicates HP StorageWorks XP Tiered Storage Manager Software. A migration plan executed by a program other than XP Auto LUN is indicated by the (green) icon displayed in the LDEV column and by Other[XX] displayed in the Owner column. You cannot delete such a migration plan by the Delete button. • Display usage rate.
Figure 19 Auto Plan Window of XP Auto LUN NOTE: The migration of volumes in a fixed parity group, external volumes, and volumes reserved by a program other than XP Auto LUN cannot be automated. NOTE: Auto migration is not directed to volumes in a fixed parity group, external volumes, and volumes reserved by a program other than XP Auto LUN. The Auto Plan window of XP Auto LUN displays the following: • Monitoring Term: Displays the monitoring period specified in the Performance Management window.
◦ If Under migration is displayed, XP Auto LUN is executing an auto migration plan. ◦ If Last migration has been canceled is displayed, XP Auto LUN has canceled the last migration plan. Plan Creation: Indicates when the auto migration plans were created. Next Migration: Indicates the next time that XP Auto LUN will perform auto migration operations. Auto Refresh: Enables you to specify whether to automate updating of information about migration plans, which is displayed in the list.
• Auto Plan Parameters lets you specify parameters that affect the automatic creation and execution of migration plans. ◦ Auto Migration Function: Specifies whether to automate volume migrations. If you select Enable, volumes are automatically migrated. If you select Disable, volumes are not automatically migrated. ◦ Sampling Term: The XP Auto LUN auto migration function analyzes resource usage within the specified sampling term and then creates auto migration plans based on that analysis.
• The Reset button restores each parameter in Auto Plan Parameters to the value before changes. • The Close button closes the Auto Plan window. Attribute Window of XP Auto LUN When you click the XP Auto LUN button in the Performance Management window, XP Auto LUN starts. The Attribute window of XP Auto LUN lets you find out which parity group belongs to which HDD class.
The icons of parity groups, external volume groups, and XP Thin Provisioning virtual volume groups are as follows: ◦ The icon indicates a fixed parity group when it appears below an HDD class folder. This icon also indicates an external volume group when it appears below the External Group folder. XP Auto LUN cannot perform auto migration for the volumes in a fixed parity group or an external volume group. ◦ indicates a RAID-1 parity group. The HDD class for this parity group is A.
◦ Ave. indicates the average usage rate for the parity group. If an exclamation mark (!) is displayed, the reported usage rate is likely to be inaccurate, because the configuration has changed (for example, volumes have been moved by XP Auto LUN or changed by Virtual LVI or Open volume Management). If a plus mark (+) is displayed before a usage rate 0, such as +0, the usage rate is not 0, but it is less than 1. ◦ Max. indicates the maximum usage rate for the parity group.
change this volume to a normal volume ( source volume. ), and then you can use this volume as a (green) indicates a reserved volume of other programs. This volume is reserved by a program other than XP Auto LUN (such as RAID Manager); therefore, XP Auto LUN cannot operate on it. You cannot change the attribute of this volume. ◦ Emulation indicates the emulation type of the volume. ◦ Capacity indicates the capacity of the volume. ◦ Ave. indicates the average usage rate for the volume.
◦ Reserved indicates the number of reserved volumes. ◦ CLPR indicates the number and name of the CLPR corresponding to the external volume group in the format CLPR-number:CLPR-name. For details on CLPRs, see HP StorageWorks XP24000/XP20000 Disk/Cache Partition User Guide. When you select an external volume group in the tree, the list displays information about external volumes (that is, volumes in the external volume groups).
Figure 25 Information about XP Thin Provisioning Virtual Volume Groups ◦ XP Thin Provisioning indicates the ID of the XP Thin Provisioning virtual volume group. The letter X stands for an XP Thin Provisioning virtual volume group. The number before the hyphen (-) is the frame number. The number after the hyphen is the group number. icon.
◦ Capacity indicates the capacity of the XP Thin Provisioning virtual volume. ◦ CLPR indicates the number and name of the CLPR corresponding to the XP Thin Provisioning virtual volume group to which the XP Thin Provisioning virtual volume belongs, in the format CLPR-number:CLPR-name. For details on CLPRs, see the HP StorageWorks XP24000/XP20000 Disk/Cache Partition User Guide. ◦ Owner indicates the program that reserved this volume, if it is reserved.
Figure 27 History Window of XP Auto LUN The History window displays the following information: • Monitoring Term displays the monitoring period specified in the Performance Management window. • Gathering Interval displays the collection interval in long range used in Performance Monitor. The interval in long range is fixed to 15 minutes. • Auto Migration History displays logs of the creation and execution of auto migration plans. The Erase button lets you erase all log information.
product. For example, 00 indicates RAID Manager, and 99 indicates XP Tiered Storage Manager Software. • The Erase button lets you erase the entire information. NOTE: • The Source[Parity Gr.] and Target[Parity Gr.] columns also display the information about external volume group migration, though these groups are not parity groups.
4 XP Auto LUN Operations This chapter describes the following volume migration operations: • “Starting XP Auto LUN” (page 52) • “Reserving Migration Destinations for Volumes” (page 52) • “Migrating Volumes Manually” (page 53) • “Automating Volume Migrations” (page 55) • “Viewing the Migration History Log” (page 58) Starting XP Auto LUN To start XP Auto LUN, take the following steps: 1. Ensure that the Remote Web Console main window is in Modify mode.
1. 2. Start XP Auto LUN and click the Attribute tab in the XP Auto LUN window. In the tree, locate a volume that you want to use as a migration destination. To locate a volume, first double-click an HDD class (or the External Group folder) in the tree to display a list of parity groups (or external volume groups). Next, click a parity group (or an external volume group). The list to the right displays a list of volumes in that group. 3.
1. 2. 3. In Auto Migration Plans, click the Delete All button to remove all auto migration plans. In Auto Migration Function, click the Disable button. Click the Set button to apply the settings to the storage system. CAUTION: When performing a series of manual migration operations, remember that the configuration changes after each migration is complete. To migrate volumes manually: 1. 2. Start XP Auto LUN and click the Manual Plan tab in the XP Auto LUN window.
When a volume starts migration, the % (percentage) column displays the progress of the migration. When the migration finishes, the migration plan of that volume will disappear from the list. If execution of the migration plan created by application software other than Remote Web Console has failed, PSUE is displayed in the Stat column. In this case, you must check the status of the application software that created the migration plan.
1. 2. Start XP Auto LUN and select the Attribute window of XP Auto LUN. In the tree, double-click the HDD class folder. The list to the right displays a list of parity groups in the HDD class. The icon indicates fixed parity groups, which do not include source or target volumes. Other icons indicate parity groups that can include source or target volumes. 3. Select a parity group from the displayed list that is represented by any icon other than the icon. Right-click the 4.
1. 2. 3. Start XP Auto LUN and click the Auto Plan tab in the XP Auto LUN window. In Auto Refresh, specify Enable or Disable. • If you specify Enable, a new plan will be automatically added to the Auto Migration Plans list when the plan is automatically created. If a migration plan executes, the progress of the execution is displayed and will automatically be updated in the Auto Migration Plans list. XP Auto LUN displays a message notifying you whenever the Auto Migration Plans list is updated.
Migration plans will be automatically created 30 minutes later than the specified sampling term. For example, if you specified 13:00–15:00 for the sampling term, plan creation will be performed at 15:30. 9. Click the Close button to close the Auto Plan window. NOTE: Plans are executed from the top of the list downward when XP Auto LUN performs auto migration. Related topics • To delete all auto migration plans, click the Delete All button.
Table 15 Messages in the Auto Migration Logs (continued) yyyy/mm/dd hh:min The auto migration finished. (a) XP Auto LUN finished executing auto migration plans. For details on the processing of an auto migration plan, see the message of the executed plan. (a) Execution end time yyyy/mm/dd hh:min The auto migration stopped because XXXXXXXXXXXX (a) (b) The execution of auto migration plans stopped due to the cause shown in XXXXXXXXXXXX.
yyyy/mm/dd hh:min The auto migration plan (LDKC:CU:LDEV (X-X)->LDKC:CU:LDEV (X-X)) was (a) (b) (c) (d) (e) canceled because of invalid parity group information. The auto migration plan (LDKC:CU:LDEV (X-X)->LDKC:CU:LDEV (X-X)) was canceled because the specified parity group information is incorrect. The correspondence between the source or target volume and the parity group is invalid. That volume might have been migrated manually after the creation of the auto migration plan.
Failed to check the usage rate of the source volume. The check of the disk usage rate of the parity group including the source or target volume ended abnormally. For the measures, call HP technical support. Failed to check the target volume. The check of the target volume ended abnormally. For the measures, call HP technical support. An unknown error occurred in checking target volumes. An unknown error occurred in checking the target volume. For the measures, call HP technical support.
Failed to specify a proper target volume. XP Auto LUN could not specify a proper target volume for creating an auto migration plan. For details, see (d) Reason why a proper target volume could not be found in the second message of the D. Messages about creating each auto migration plan (output during the creation) section. Insufficient statistics data in the sampling term. The statistics data for creating auto migration plans is insufficient.
In Group X-X, there are X invalid samples. These samples were not used for creating the auto (a) (b) migration plans. There are some invalid samples in the parity group X-X. Therefore, XP Auto LUN created auto migration plans without using these samples. (If there is one invalid sample, this message is shown as ... there is invalid sample. This sample was ...) (a) Parity group (b) Number of invalid samples There is too much invalid data in Group X-X LDKC:CU:LDEV.
yyyy/mm/dd hh:min Source candidate = LDKC:CU:LDEV in Group X-X (a) (b) (c) Failed to specify a proper target volume for this source candidate. Cause: XXXXXXXXXXXX (d) XP Auto LUN could not find a proper candidate for the target volume corresponding to the specified candidate for the source volume.
Table 16 Messages in the Migration Logs (displayed in the Action column) Message Meaning Migration Started The migration operation started. Migration Completed The migration operation completed successfully. Migration Canceled by User The migration operation was canceled by the user. Migration Failed The migration operation failed. Migration Canceled by Controller The migration operation was canceled by XP Auto LUN (for example, volume usage rate exceeded specified maximum).
5 Using RAID Manager for Manual Volume Migration In the environment where XP Auto LUN is installed on the storage system, users can use RAID Manager to perform manual volume migrations from an open-system host. This chapter explains the procedure and notes for using RAID Manager to perform manual volume migrations.
Figure 29 Status Transition Chart for a Pair during Volume Migration by RAID Manager Volume Migration Errors When you perform a volume migration by using RAID Manager, note the following: • A reserved volume of XP Auto LUN cannot be used when you perform a volume migration by using RAID Manager. • A migration plan being executed by XP Auto LUN cannot be canceled from RAID Manager. • A migration plan created by XP Auto LUN cannot be displayed by using RAID Manager.
6 Troubleshooting This chapter provides troubleshooting information on XP Auto LUN. For troubleshooting information on Remote Web Console, see the HP StorageWorks XP24000/XP20000 Remote Web Console User Guide and HP StorageWorks XP24000/XP20000 Remote Web Console Error Codes.
1. Find the error code from the logs displayed on the RAID Manager window. Figure 30 (page 69) shows an example of a log displayed on the RAID Manager window. Figure 30 Example of a Log Displayed on the RAID Manager Window Error codes appear to the right side of SSB=. The last four digits of the alphanumeric characters that appear to the left of the comma (,) indicate SSB1 (for example, B9E1).
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager Error Code (SSB1) B9AE/B9AF Error Code (SSB2) Cause Measure 2027 The cache mode between the migration source volume and the migration target volume does not match. This migration plan cannot be executed. Check the configuration definition file. 2039 The migration source volume is the quorum disk. This migration plan cannot be executed. Check the configuration definition file.
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Cause Measure The migration target volume corresponds to either of the following causes: 1. The volume is a P-VOL of the XP Snapshot pair. 2. The volume is an S-VOL of the XP Snapshot pair or a V-VOL of XP Snapshot. Perform the following measures for each cause: 1. Release the XP Snapshot pair, and then migrate the volume. 2. This volume migration cannot be executed.
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Cause Measure Migration is not allowed between the normal volume specified as a LUSE volume and the XP Thin Provisioning virtual volume. 72 20A1 The migration source volume is used in an XP Continuous Access Asynchronous pair. The CLPR of the migration source volume and the CLPR of the migration target volume are mismatched.
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Cause Measure 2322 The migration source volume is set as the Release the pair of XP Business Copy, leaf volume of XP Business Copy. and then migrate the volume. 2328 The migration target volume is set as the Release the pair of XP Business Copy, secondary volume of XP Business Copy. and then migrate the volume.
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Cause Measure The migration source volume is not This migration plan cannot be deleted. paired with the migration target volume. The migration cannot be canceled. Check the configuration definition file. 2351 The migration source volume and the migration target volume are set to the same volume.
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Cause Measure The migration source volume is a secondary volume of an XP Business Copy pair that is in the SP-PEND status. Perform the volume migration after the XP Business Copy pair is changed to the SPLIT status. 2370 The migration source volume is not installed. This migration plan cannot be executed. Check the configuration definition file.
Table 17 Errors during Volume Migration or Migration Cancellation by using RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Cause Measure The pair operation command was rejected because the specified secondary volume is not implemented. B913 The pair operation command was Specify a mirror ID from 0 to 2. rejected because the mirror ID is invalid.
7 Support and Other Resources Related Documentation • HP StorageWorks XP RAID Manager User Guide • HP StorageWorks XP24000/XP20000 for FlashCopy Mirroring Software User Guide • HP StorageWorks XP24000/XP20000 Snapshot User Guide • HP StorageWorks XP24000/XP20000 Thin Provisioning Software User Guide • HP StorageWorks XP24000/XP20000 LUN Manager User Guide • Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array • HP StorageWorks XP24000/XP20000 Business Copy
• 1 PB (petabyte) = 1,0245 bytes • 1 block = 512 bytes HP Technical Support For worldwide technical support information, see the HP support website: http://www.hp.
Glossary C CU Control unit. D DASD Direct-access storage device. DFW DASD fast write. DKA Disk adapter. DKCMAIN Disk controller main. E ESCON Enterprise systems connection An optical interface used to connect the mainframe to the control unit; a predecessor to FICON. L LD, LDEV Logical device. An LDEV is created when a RAID group is carved into pieces according to the selected host emulation mode (that is, OPEN-3, OPEN-8, OPEN-9).
Index A T auto migration, 5 operations, 55 overview, 12 target volume, 11, 36 technical support, 78 HP, 78 C W class, 9 conventions storage capacity values, 77 websites HP, 78 HP Subscriber's Choice for Business, 78 product manuals, 77 D document related documentation, 77 documentation HP website, 77 providing feedback, 78 E expanded LUs, 21 F fixed parity group, 12 H HDD class, 9 help obtaining, 78 HP technical support, 78 M manual migration, 5 operations, 53 overview, 7 migration operation, 11