HP Array Configuration Utility User Guide January 2006 (First Edition) Part Number 416146-001
© Copyright 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft, Windows, and Windows NT are U.S.
Contents Getting started.............................................................................................................................. 5 Features and system requirements................................................................................................................ 5 Installing ACU........................................................................................................................................... 5 Setting the execution mode for Microsoft Windows .......
Controller category........................................................................................................................ 34 Array category.............................................................................................................................. 37 Logical Drive category ................................................................................................................... 37 Error reporting ...................................................................
Getting started In this section Features and system requirements .............................................................................................................. 5 Installing ACU.......................................................................................................................................... 5 Overview for using ACU ...........................................................................................................................
Setting the execution mode for Microsoft Windows During the installation process on a server using a supported Microsoft® Windows® operating system, you are prompted to select the Execution Mode setting. This setting determines whether you can run ACU on the server from a remote network location. You can change the execution mode at any time by selecting Setup HP Array Configuration Utility from the Start menu.
NOTE: Some advanced tasks are not available in all operating modes. For further information, refer to "Tasks possible in each operating mode ("Selecting an operating mode" on page 7)." 2. If you opened ACU in GUI mode: a. Select the controller that you want to configure. b. Select the configuration mode that you want to use ("GUI operating modes" on page 10). 3. Configure the controller.
Opening ACU in Local Application mode 1. Click Start, and navigate to Programs>HP System Tools>HP Array Configuration Utility. The browser opens and launches ACU, which then identifies the controllers that are connected to the system. This process could take a minute or two. 2. When controller detection is complete, select a controller from the list on the left side of the screen. The main ACU configuration screen appears. Opening ACU in Browser mode 1. Open ACU on the host. 2.
The main ACU configuration screen appears. Opening ACU through Systems Insight Manager 1. On the server that has ACU loaded, confirm that the utility is running in Remote Service mode ("Setting the execution mode for Microsoft Windows" on page 6). 2. On the remote server, connect to the Systems Insight Manager server (port :280), and log in. 3. Select Device Queries. 4. Under Device by Type, select All Servers. 5. Connect to the server that is running ACU. 6.
The main ACU configuration screen appears. GUI operating modes The GUI format of ACU has three configuration modes: • Standard mode ("Typical Standard mode screen" on page 10) enables you to manually configure all options on the controller. • Configuration Wizards mode ("Typical Configuration Wizards mode screen" on page 11) guides you through each step of a manual configuration process.
Typical Configuration Wizards mode screen The Configuration Wizards mode screen consists of four regions: the Devices list, the Configuration View panel, the Main Menu, and the FAQ column. • The Devices list on the left side of the screen shows all the identifiable controllers that are connected to the system.
Typical Express Configuration mode screen NOTE: Express mode is listed as a configuration option only if the controller that you select has unused space on an array or physical drives that are not assigned to an array. Express Configuration mode screens are similar in appearance to Configuration Wizards mode screens ("Typical Configuration Wizards mode screen" on page 11), but the directive text is different.
Configuring a new controller In this section Using Standard Configuration mode......................................................................................................... 13 Using Express Configuration mode........................................................................................................... 14 Using the configuration wizards...............................................................................................................
Menu item Possible tasks Array Assign Spare Create Logical Drive Delete Expand Re-Mirror Array Remove Spare Split Mirrored Array More Information Logical drive Migrate RAID/Stripe Size Extend Size Delete Selective Storage Presentation (for RA4x00 controllers) More Information Unused space Create Logical Drive More Information Using Express Configuration mode 1. Click Express Configuration in the lower right panel of the main ACU configuration screen. The Express mode start screen appears. 2.
3. Select a RAID level, and then click Next. 4. If you select a fault-tolerant RAID method and an unassigned physical drive of the appropriate capacity is available, ACU asks if you want to assign spare drives to the array. • If you do not want this array to have a spare, click No, and then click Next. • To assign spares to the array, click Yes, and then click Next. On the next screen, select the drives that you want to be the spares, and then click Next.
The Configuration View panel displays a placeholder for the array that you are about to create. (If there are many physical drives connected to the controller, use the scrollbars in the Configuration View panel to see all the physical drives and arrays.) 3. Select the type of drive that you will use in the array. 4. Select the physical drives that you want to use in the array. • Use physical drives of comparable capacity. ACU uses the same amount of space from each physical drive to build an array.
7. Click Finish to confirm the configuration. The drives are now configured as unused space on the new array. To create more arrays on the same controller, repeat the previous steps. Creating a logical drive 1. Click Create a logical drive, and then click Begin. 2. Select an array that has unused space, and then click Next. (The array must have unused space for logical drive creation to be possible.) The screen displays a list of the fault-tolerance levels that are possible for this configuration.
6. Set the size that you want the logical drive to be, and then click Next. If the controller has an array accelerator, a screen appears that gives you the option of disabling it for the currently selected logical drive. NOTE: Disabling the array accelerator for a logical drive reserves use of the accelerator cache for other logical drives on the array.
Modifying an existing configuration In this section Choices available after opening ACU....................................................................................................... 19 Modifying a configuration using Standard Configuration mode ................................................................... 19 Modifying a configuration using Express mode..........................................................................................
Modifying a configuration using Express mode NOTE: Express mode is listed as a configuration option only if the controller that you select has unused space on an array or physical drives that are not assigned to an array. 1. Click Express Configuration, and then click Begin. If there are unassigned physical drives on the controller, you can create a new array or expand an existing array. Make your choice, and then click Next.
Controller settings The default controller settings that ACU provides are adequate for many purposes. When necessary, however, you can use the Controller Settings task to: • Alter the priority that the system gives to an array expansion or rebuild • Disable the array accelerator (if one is present) • Change the ratio of read cache to write cache (if the controller has battery-backed cache) To change the controller settings: 1. Click Controller Settings, and then click Begin.
• For better system performance, use physical drives that are attached to different ports on the controller. • In RAID 5 configurations, keep the risk of logical drive failure low by assigning no more than 14 physical drives to the array. Each time that you add a physical drive to the array, the configuration view is updated to show how much free space remains on the array. 4. Click Next when you have finished adding physical drives to the array. 5.
The next screen enables you to set the size of the logical drive. The default size shown is the largest possible logical drive size for the RAID level that you chose and the set of physical drives that is being used. Reducing the size of the logical drive liberates drive space, which you can use to build additional logical drives on the same array. 6. Set the size that you want the logical drive to be, and then click Next.
Delete logical drives This task deletes the selected logical drive and converts it into unused drive space. You can then use this unused drive space to: • Create new logical drives ("Create a logical drive" on page 22). • Migrate the RAID level or stripe size of an existing logical drive ("Migrate a logical drive" on page 25). • Extend existing logical drives on the same array ("Extend logical drive" on page 25), if the operating system allows logical drive extension. To delete a logical drive: 1.
To check the progress of an array expansion, click the icon for that array in the Configuration View panel. A More Information pop-up window opens that describes the array status. Extend logical drive This option increases the storage capacity of a logical drive by adding unused space on an array to a logical drive on the same array.
6. Click Finish to accept the changes. At this point (before clicking Save in the next step), you can arrange to migrate another logical drive on the same controller by repeating the previous steps. However, the controller can migrate only one logical drive at a time. Remaining migrations are queued. 7. Click Save. Migration begins. To check the progress of a migration, click the icon for that logical drive in the Configuration View panel.
NOTE: Be sure that every HBA in the system has access to the logical drives for which multi-path will be used. 5. Click Finish. MSA and Smart Array Cluster storage controllers 1. Click Selective Storage Presentation, and then click Begin. On the next screen that appears, select the appropriate radio button to enable or disable SSP, and then click Next. • If you disable SSP, all host controllers have access to all logical drives.
Configuring switches If the selected controller supports switch configuration, the menu link for this feature is given in the Wizards panel in the lower right-hand corner of the main ACU configuration screen. 1. Use the PING command to confirm that the connections between the management server running ACU and the LAN management ports on the switches are reliable. 2. Click Switch Configuration (in the Wizards panel). 3. Select the switch that you want to configure, and then click Next. 4.
The screen now displays a URL for launching the Switch Configuration Utility. This utility is a Java™ applet that enables you to further configure the switch. You might need to load the most current Java™ plug-in to be able to use the applet. 6. Click the URL link. 7. Follow the on-screen prompts and instructions to use the switch configuration utility.
3. Insert the CD that contains ACU into the CD-ROM drive. 4. Open ACU, and stay in Standard configuration mode (the default). 5. Select the controller that contains the array that you want to be re-mirrored. 6. In the Configuration View panel, select the array that you want to use as the source array in the recombined mirrored array. 7. In the Select a Task panel, click Re-Mirror Array. 8. Select the array that is to be mirrored to the source array.
Scripting in ACU In this section Introduction to scripting in ACU ............................................................................................................... 31 Operating modes ................................................................................................................................... 31 Command line syntax ............................................................................................................................. 31 Sample custom input script ....
If you do not specify a capture file name, ACU gives the file the default name of ACUCAPT.INI and places it in the ACU working directory. In Input mode: cpqacuxe -i FILENAME If you do not specify an input file name, ACU gives the file the default name ACUINPUT.INI and places it in the ACU working directory. If any errors occur during either process, these errors are noted in the file ERROR.INI that is logged to the default working directory.
* ArrayAccelerator = Enable|Disable * LogicalDriveSSPState = Enable|Disable * SSPAdaptersWithAccess = [N],[N]...|None PreferredPath = 1|2 HBA_WW_ID = WWN ConnectionName = UserDefinedName HostMode = Default|Windows|Windows(degrade)|openVMS|Tru64|Linux |Solaris|Netware|HP|Windows Sp2 Script file options There are four categories of options in ACU script files: Control, Controller, Array, and Logical Drive.
Category Options Comments Logical Drive LogicalDrive These options define a logical drive that is to be configured on an array that is defined previously in the script. (If no array is previously defined, ACU sends an error message.) The LogicalDrive option must be at the beginning of this section of the script, but you can script the other options in this category in any order.
Controller You must enter a value for this option because it identifies the controller that is to be configured. • All—Configure all detected controllers in the system identically. • Slot [N]—Configure the internal controller in slot number N. • WWN [N]—Configure the external controller that has the World Wide Name N. • SerialNumber [N]—Configure the shared storage controller that has serial number N.
Read:write ratio RA4x00 with 16MB cache RA4x00 with 48MB cache All other controllers with battery-backed cache All other controllers without battery-backed cache 70:30 Y Y -- -- 60:40 Y Y -- -- 50:50 Y Y Y -- 40:60 -- Y -- -- 30:70 -- Y -- -- 25:75 -- Y Y -- 0:50* Y -- -- -- 0:75* -- Y -- -- 0:100 -- -- Y -- * The cache ratio percentages do not total 100 in these cases because the additional 16-MB or 48-MB cache modules are not used.
Array category These options are available under the Array category: • Array (on page 37) • OnlineSpare (on page 37) • Drive (on page 37) Array Enter a letter in the range A–Z or a–f to identify the array that is to be created or reconfigured, bearing in mind these additional limitations: • In Configure mode, ACU creates a new array. The letter value that you specify must be the next available letter in the sequence, considering the number of existing arrays on the controller.
• SSPAdaptersWithAccess (on page 39) • PreferredPath (on page 39) • HBA_WW_ID (on page 39) • ConnectionName (on page 39) • HostMode (on page 40) LogicalDrive Specify the ID number of the logical drive that is to be created or modified. • In Configure mode, you can enter only the ID number of the next possible logical drive in the sequence for the existing configuration. • In Reconfigure mode, you can also enter the ID number of an existing logical drive.
In Reconfigure mode, the default setting is the existing stripe size for the specified logical drive. If you specify a stripe size that is different from the existing value, then ACU attempts to migrate the logical drive to the stripe size that you specify. CAUTION: Back up all data before extending a logical drive. ArrayAccelerator This option specifies whether the array accelerator is enabled or disabled for the specified logical drive. The default value is Enabled.
HostMode This option specifies the HostMode for a selected HBA. Setting the Host Mode optimizes the storage array for the selected operating system. The available host modes for an HBA are device-specific. Not all modes are available on all devices. Not all HBAs support a HostMode.
Message Comment or explanation (if not self-explanatory) Cannot create array. The controller either has no unassigned physical drives, or it already has the maximum number of arrays or logical drives. Cannot create logical drive. There is no free space on the array, or the maximum number of logical drives has already been reached. Cannot expand array. The controller does not support expansion, or the current configuration of the controller does not allow expansion. Cannot extend logical drive.
Message Comment or explanation (if not self-explanatory) Internal error. An internal ACU error has occurred, and some error is not being identified properly. Invalid array accelerator setting. The specified array accelerator setting is invalid or is not supported with the current configuration. Invalid array. The array ID is invalid. Invalid ChassisName. The entered ChassisName is invalid. Use characters from the set a– z, A–Z, 0–9, !, @, #, *, (, ), ,, -, _, +, :, ., /, and [space].
Message Comment or explanation (if not self-explanatory) New array ID already exists. This error occurs in Configure mode when the array ID in the script file already exists in the configuration. You can only use Configure mode to create new arrays. New array ID does not match the next available array ID. The array ID that you specified in the script file does not match the ID of the newly created array.
Using the Command Line Interface In this section Overview of the ACU CLI ........................................................................................................................ 44 Typical procedures ................................................................................................................................. 46 Overview of the ACU CLI The ACU CLI is an interactive command console that provides immediate feedback to the user and is functionally equivalent to the ACU GUI.
The remaining examples in this chapter are described as if entered in Console mode. CLI syntax Whether entered in Command mode or Console mode, a typical ACU CLI command line consists of three parts: a target device, a command, and a parameter with values if necessary.
Keyword Abbreviation in ACU CLI Keyword Abbreviation in ACU CLI chassisname* ch* preferredpathmode ppm chassisslot chs rebuildpriority rp connectionname cn redundantcontroller rc controller ctrl serialnumber sn drivetype dt stripesize ss drivewritecache dwc surfacescandelay ssd expandpriority ep tapedrive td *The CLI also uses this keyword and abbreviation for the terms box name and RAID array ID.
Creating a logical drive When you use the CLI to create a logical drive, the array that holds the logical drive is created implicitly. (The CLI is different from the GUI in this respect, because in the GUI you must create the array explicitly in a separate step.) Syntax: create type=ld [parameter=value] • To create a logical drive on a new array, specify both the controller and the drives that are to constitute the new array.
physicaldrive 1:13 (box 1:bay13, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:14 (box 1:bay14, Parallel SCSI, 9.1 GB, OK) Knowing this information, you can now create the first array with one logical drive: => ctrl ch="Lab 4" create type=ld drives=1:12 Now, verify that the array has been created: => ctrl ch="Lab 4" pd all show In this case, the screen response is: MSA1000 at Lab 4 array A physicaldrive 1:12 (box 1:bay12, Parallel SCSI, 36.4 GB, OK) unassigned physicaldrive 1:13 (box 1:bay13, Parallel SCSI, 9.
logicaldrive 1 (33.9 GB, RAID 0, OK) array B logicaldrive 2 (298 MB, RAID 1+0, OK) logicaldrive 3 (896 MB, RAID 1+0, OK) Modifying the controller chassis name If a controller is configured with at least one logical drive, you can assign the controller a simplified name (the chassis name) to make it easier to identify and enter the correct controller in a command. Syntax: modify ch="new chassis name" where is a controller.
=> ctrl ch="Lab 4" show ssp A typical screen response could be: MSA1000 at Lab 4 Adapter ID: 210000E08B07A68F connectionname: Unknown Location: Local Status: Online Host Mode: Default Adapter ID: 5034414235583942 connectionname: Unknown Location: Unknown Status: Offline Host Mode: Default Now activate SSP, and then show the logical drives that are present so that you can determine which drive to unmask: => ctrl ch="Lab 4" modify ssp=on forced => ctrl ch="Lab 4" ld all show MSA1000 at Lab 4 array A logicaldr
Syntax: modify ai=# cn="connection name" where is a controller that supports SSP. Example command: ctrl ch="Lab 4" ld 1 modify ai=210000E08B07A68F cn="cnxn 3" Managing host modes (connection profiles) Syntax: modify ai=# hostmode="operating system type"|? where is a controller that supports host modes. Example command: => ctrl ch="Lab 3" modify ai=5034414235583942 hostmode=? NOTE: The connection name and the logical unit are required for managing host modes.
Expanding an array You can increase the storage space on an array by adding physical drives. However, the added drives must be of the same type (for example, parallel SCSI or SATA), and they must each have a capacity no less than that of the existing drives in the array. IMPORTANT: An array expansion, logical drive extension, or logical drive migration takes about 15 minutes per gigabyte, or considerably longer if the controller does not have a battery-backed cache.
Syntax: add spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|allunassigned [forced] remove spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|all where is an array. If the array contains only one logical drive, the logical drive can also be the target. The parameter forced represses warning message prompts.
• At the medium setting, rebuilding occurs for half of the time, and normal system operations occur for the rest of the time. • At the high setting, the rebuild takes precedence over all other system operations. If the logical drive is part of an array that has an online spare, rebuilding begins automatically when drive failure occurs. If the array does not have an online spare, rebuilding begins when the failed physical drive is replaced.
modify ssd=# where is a controller and # is a number between 1 and 30. This number determines the delay time in seconds, but you do not need to include units with the command. Example command: => ctrl sn=P56350D9IP903J modify ssd=3 Re-enabling a failed logical drive If a logical drive has failed and the data on it is invalid or non-recoverable, you can re-enable the logical drive so that it can be reused.
modify redundantcontroller=disable where is a controller that has an enabled redundant controller. Example command: => ctrl ch="redundant Lab4" modify rc=disable Setting the target If you must perform several operations on a given target device, you can simplify the required commands by setting the device as the default for the CLI operations.
Setting the preferred path mode The preferred path mode determines how I/O traffic to the logical drives is managed on controllers that are in an active/active configuration. • In Automatic mode, the storage system automatically selects a suitable path for I/O traffic to each logical drive depending on the host I/O patterns at the time. Because the optimum path can vary with time, I/O traffic for any given logical drive can be directed through either controller.
Probability of logical drive failure In this section Factors involved in logical drive failure ..................................................................................................... 58 Factors involved in logical drive failure The probability that a logical drive will fail depends on the RAID-level setting and on the number and type of physical drives in the array.
Probability of logical drive failure vs.
Drive arrays and fault-tolerance methods In this section Drive arrays........................................................................................................................................... 60 Fault-tolerance methods........................................................................................................................... 62 Drive arrays The capacity and performance of a single physical (hard) drive is adequate for home users.
With an array controller installed in the system, the capacity of several physical drives can be combined into one or more virtual units called logical drives (also called logical volumes and denoted by Ln in the figures in this section). Then, the read/write heads of all the constituent physical drives are active simultaneously, reducing the total time required for data transfer.
logical drive, the term array is often used as a synonym for logical drive. However, an array can contain several logical drives, each of a different size. Each logical drive in an array is distributed across all of the physical drives within the array. A logical drive can also extend across more than one port on the same controller, but it cannot extend across more than one controller. Drive failure, although rare, is potentially catastrophic.
• RAID 1+0—Drive Mirroring • RAID 5—Distributed Data Guarding • RAID 6 (ADG)—Advanced Data Guarding RAID 0—No fault tolerance A RAID 0 configuration provides data striping, but there is no protection against data loss when a drive fails. However, it is useful for rapid storage of large amounts of noncritical data (for printing or image editing, for example) or when cost is the most important consideration. Advantages: • Has the highest write performance of all RAID methods.
RAID 1+0—drive mirroring In a RAID 1+0 configuration, data is duplicated to a second drive. When the array has more than two physical drives, drives are mirrored in pairs. In each mirrored pair, the physical drive that is not busy answering other requests answers any read requests that are sent to the array. (This behavior is called load balancing.) If a physical drive fails, the remaining drive in the mirrored pair can still provide all the necessary data.
• No data is lost when a drive fails, as long as no failed drive is mirrored to another failed drive (up to half of the physical drives in the array can fail). Disadvantages: • This method is expensive (many drives are needed for fault tolerance). • Only half of the total drive capacity is usable for data storage. RAID 5—distributed data guarding In a RAID 5 configuration, data protection is provided by parity data (denoted by Px,y in the figure).
and Qx,y in the figure), allowing data to still be preserved if two drives fail. Each set of parity data uses a capacity equivalent to that of one of the constituent drives. This method is most useful when data loss is unacceptable but cost is also an important factor. The probability that data loss will occur when an array is configured with RAID 6 (ADG) is less than it would be if it was configured with RAID 5. Advantages: • This method has a high read performance.
Item RAID 0 RAID 1+0 RAID 5 RAID 6 (ADG) Tolerates simultaneous failure of more than one physical drive No Only if no two failed drives are in the same mirrored pair No Yes Read performance High High High High Write performance High Medium Low Low Relative cost Low High Medium Medium *Values for the fraction of drive space usable are calculated with these assumptions: (1) all physical drives in the array have the same capacity; (2) online spares are not used; (3) no more than 14 phy
Diagnosing array problems In this section Diagnostic tools ..................................................................................................................................... 68 Diagnostic tools Several diagnostic tools provide feedback about problems with arrays. The most important are: • ADU This utility is available on both the SmartStart CD and the HP website (http://www.hp.com/support).
Acronyms and abbreviations ACR Array Configuration Replicator ADG Advanced Data Guarding (also known as RAID 6) ADU Array Diagnostics Utility HBA host bus adapter MSA Modular Smart Array MTBF mean time between failures POST Power-On Self Test PSP ProLiant Support Pack SA Smart Array SSP Selective Storage Presentation WBEM Web-Based Enterprise Management WWN World Wide Name Acronyms and abbreviations 69
Index A abbreviations in CLI 45 ADU (Array Diagnostic Utility) 68 array accelerator, disabling 17, 21, 55 array capacity expansion 24 array concepts 60 array configuration, copying 31 Array Diagnostic Utility (ADU) 68 array expansion, setting priority of 21 array, creating 14, 15 B browser mode 8 C cache ratio, setting 21, 35 clear a configuration 20 CLI (Command Line Interface) 44 Command Line Interface (CLI) 44 configuration modes 10 configuring an array 15, 21 connection name 39, 50 controller duplexin
POST error messages 68 probability of logical drive failure 58 R RAID level migration 25 RAID levels 62, 63, 64, 65 RAID levels, comparison of features 66 RAID, software-based 67 read-write ratio, setting 21 rebuild priority 21 recombining a split array 29 redundant controller, disabling 55 redundant controller, modifying I/O path of 36, 39, 57 redundant controller, preferred path settings for 36, 39, 57 re-enabling a failed logical drive 55 Remote Service mode 6 replication of array configuration 31 resol
