advertisement
Configuring Arrays on HP Smart Array Controllers
Reference Guide
Abstract
This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
Part Number: 433572-007
March 2012
Edition: 7
© Copyright 2006, 2012 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.
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.
Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation. Java® is a registered trademark of Oracle and/or its affiliates.
Contents
Contents 3
Contents 4
Overview of array configuration tools
Utilities available for configuring an array
To configure an array on an HP Smart Array controller, three utilities are available:
•
HP Array Configuration Utility (ACU)—An advanced utility that enables you to perform many complex configuration tasks
•
Option ROM Configuration for Arrays (ORCA)—A simple utility used mainly to configure the first logical drive in a new server before the operating system is loaded
•
HP Online Array Configuration Utility for NetWare (CPQONLIN)—A customized version of ACU for online configuration of servers that use Novell NetWare
Before you use a utility, confirm that the utility can support the required task. View a comparison of the utilities
Whichever utility you use, remember the following factors when you build an array:
•
All drives grouped in a logical drive must be of the same type (for example, either all SAS or all SATA and either all hard drives or all solid state drives).
•
For the most efficient use of drive space, all drives within an array should have approximately the same capacity. Each configuration utility treats every physical drive in an array as if it has the same capacity as the smallest drive in the array. Any excess capacity of a particular drive cannot be used in the array and is unavailable for data storage.
•
The more physical drives configured in an array, the greater the probability that the array will experience a drive failure during any given period.
•
To guard against the data loss that occurs when a drive fails, configure all logical drives in an array with a suitable fault-tolerance (RAID) method. For more information, see "Drive arrays and fault-tolerance
Comparison of the utilities
Feature
Interface
Languages
Source of executable file
When the utility can be used
Where the utility can be used
ACU
GUI, CLI, and Scripting
English, French, German,
Italian, Japanese, and
Spanish
Software CD, web, or embedded in the system
All formats can be run in online and offline environments.
Any machine that uses a supported browser
CPQONLIN
Menu-based
English
Software CD or Web
Any time the operating system is running
Only on the local server
ORCA
Menu-based or CLI
English
Preinstalled in ROM of HP
Smart Array controllers
During POST, before the operating system is installed
Only on the local server
Overview of array configuration tools 5
ORCA supports only basic configuration tasks, whereas CPQONLIN and ACU provide full-range support for
Scripting).
Support for standard configuration tasks
A "+" indicates the feature or task is supported. A "–" indicates the feature or task is not supported.
Task ACU CPQONLIN ORCA
Create or delete arrays and logical drives
Assign a RAID level to a logical drive
Identify devices by causing their LEDs to illuminate
Assign a spare drive to an array
Share a spare drive among several arrays
+
+
Assign multiple spare drives to an array
Set the spare activation mode
+
+
Specify the size of the logical drive
Create multiple logical drives per array
Set the stripe size
Migrate the RAID level or stripe size
Expand an array
+
+
Set the expand priority, migrate priority, and accelerator ratio +
Extend a logical drive
+
Set the boot controller
+
+
+
+
+
+
+
+
–
+
+
+
+
+
+
+
+
+
–
+
+
–
–
–
+
–
+
+
–
–
–
–
–
–
–
–
+
Support for advanced configuration tasks
The following table uses these symbols:
+ —The ACU format supports this task.
– —The ACU format does not support this task.
+/– —Support for this task varies by controller. To support this task, some controllers must have SAAP activated by a registered license key.
To identify controller-specific feature support and SAAP requirements, see the controller user guide or the HP website ( http://www.hp.com/products/smartarray ).
For more information, see "About SAAP (on page 8 )."
Procedure
Activate or delete license keys
Configure multiple systems identically
Configure a RAID 6 logical drive
Configure a RAID 60 logical drive
Copy the configuration of one system to multiple systems
Disable a redundant controller
Enable or disable a physical drive write cache
– 1
+ 2
+
+
+ 1
+/–
+/–
ACU GUI ACU CLI ACU Scripting
+
+
+
+ 1
+/–
+/–
– 1 +
–
+
+
+
+/–
+/–
Overview of array configuration tools 6
Procedure
HP Drive Erase (replace the content of a physical drive or logical drive with zeros or random 0 and 1)
Identify devices by causing their LEDs to flash
Move an array (copy all array data to a new array and then delete the old array)
Optimize the controller performance for video
Re-enable a failed logical drive
Set the surface scan delay
Set the preferred controller for a logical drive (in systems that support redundant controllers)
Shrink an array (restripe the data on an array to occupy fewer physical drives, then remove the excess drives from the array)
Split a RAID 1 array or recombine a split array (offline only)
1
Scripting is the most efficient method for this task.
2 The task is supported only from the Configuration screen.
ACU GUI ACU CLI ACU Scripting
+/–
+
+/– 2
+/– 2
+
+
+ 2
+/– 2
+/–
+/–
+
+/–
+/–
+
+
+
+/–
–
–
–
+/–
+/–
–
+
+
+/–
–
Overview of array configuration tools 7
HP Smart Array Advanced Pack
About SAAP
SAAP is a collection of additional and advanced controller features embedded in the firmware of select
Smart Array controllers.
To access SAAP features, activate the software with a registered license key. (SAAP 1.0 is standard on the
HP Smart Array P812 Controller.)
SAAP 1.0 provides the following features:
•
RAID 6 (ADG)
•
RAID 60 (ADG)
•
Advanced Capacity Expansion
•
Mirror splitting and recombining in offline mode
•
Drive Erase
•
Performance optimization for video on demand
•
Dual domain
SAAP 2.0 includes all v1.0 features and also provides the following additional features:
•
RAID 1 (ADM)
•
RAID 10 (ADM)
•
Capability for moving and deleting individual LUNs
To access SAAP features, you must purchase a license key from HP. To obtain a license key, see the SAAP product page on the HP website ( http://www.hp.com/go/SAAP ).
To install the license key and activate SAAP, use one of the following methods:
•
Installing a license key with ORCA (on page 12 )
•
Installing a license key with ACU (on page 44 )
•
Installing a license key with ACU CLI (" Entering or deleting a license key " on page 60 )
•
Installing a license key with ACU Scripting (" LicenseKey, DeleteLicenseKey " on page 79 )
Some SAAP features are required for advanced configuration tasks in ACU. For a list of these tasks, see
"Support for advanced configuration tasks (on page 6 )."
Required hardware
For a list of Smart Array controllers that support SAAP, see the SAAP product page on the HP website
( http://www.hp.com/go/SAAP ).
To support some controller features, the controller may also require a hardware configuration that includes the following cache (array accelerator) options:
HP Smart Array Advanced Pack 8
•
A cache module that is 256 MiB or larger
•
A compatible battery pack or capacitor pack
To obtain these options, contact an HP authorized reseller or see the HP website
( http://www.hp.com/products/smartarray ).
HP Smart Array Advanced Pack 9
Option ROM Configuration for Arrays
About ORCA
ORCA is a ROM-resident array configuration utility that executes automatically during initialization of an HP
Smart Array controller. This utility is designed to enable a logical drive to be configured on a new HP server before the operating system is installed:
•
If the boot drive has not been formatted and the boot controller is connected to six or fewer physical drives, ORCA runs as part of the auto-configuration process when the new server is first powered up.
During this auto-configuration process, ORCA uses all of the physical drives on the controller to set up the first logical drive. The RAID level used for the logical drive depends on the number of physical drives
(one drive = RAID 0; two drives = RAID 1+0; three to six drives = RAID 5). If the drives have different capacities, ORCA locates the smallest drive and uses the capacity of that drive to determine how much space to use on each of the other drives.
•
If the boot drive has been formatted or if there are more than six drives connected to the controller, you are prompted to run ORCA manually.
For more information about the auto-configuration process, see the HP ROM-Based Setup Utility User Guide on the Documentation CD that is provided with the server.
ORCA is available in two formats:
•
Using the ORCA menu-driven interface (on page 10 )
•
Using the ORCA CLI (on page 13 )
HP ProLiant 100 Series servers do not support the CLI format. For these servers, use the menu-driven interface.
Either format provides a quick and easy method for basic logical drive configuration. Both formats have
configuration needs are simple. For example, stripe size is predetermined by the RAID level that you choose, and the size of the logical drive is determined automatically by the size of the physical drives that you select.
Using the ORCA menu-driven interface
1.
Power up the server.
POST runs.
If the BIOS interface is in Command Line mode, change it to Auto mode: a.
Press the F9 key to open RBSU when prompted during POST. b. c.
Set the BIOS interface mode to Auto. Enter the following text: set config bios interface mode 1
RBSU saves the configuration automatically.
Exit RBSU. Enter exit.
The server reboots, and then POST runs again.
Option ROM Configuration for Arrays 10
2.
During POST, all controllers in the server are initialized one at a time in the current boot order sequence.
If a controller is connected to one or more hard drives, a message appears during the initialization process for that controller, prompting you to start ORCA.
At the ORCA prompt for the controller that you want to configure, press the F8 key.
The ORCA main menu appears, enabling you to do the following: o o
Create, view, or delete a logical drive (" Creating a logical drive with ORCA " on page 11 )
Enter an SAAP license key (" Installing a license key with ORCA " on page 12 )
Creating a logical drive with ORCA
1.
2.
Power up the server.
POST runs.
During POST, all controllers in the server are initialized one at a time in the current boot order sequence.
If a controller is connected to one or more hard drives, a message appears during the initialization process for that controller, prompting you to start ORCA.
At the ORCA prompt for the controller that you want to configure, press the F8 key.
Option ROM Configuration for Arrays 11
The ORCA main menu appears.
7.
8.
9.
3.
4.
5.
6.
Select Create Logical Drive.
The screen displays a list of all available (unconfigured) physical drives and the valid RAID options for the system.
Press the arrow keys, spacebar, and Tab key to navigate the screen and set up the logical drive, including an online spare drive, if one is required.
Press the Enter key to accept the settings.
Press the F8 key to confirm the settings and save the new configuration.
After several seconds, the Configuration Saved screen appears.
Press the Enter key to continue.
(Optional) To create additional logical drives, repeat steps 3 through 7.
Format the logical drive. o o
If you have not yet installed the operating system, format the logical drive when you install the operating system.
If the operating system is already installed, format the logical drive as described in the operating system documentation.
Installing a license key with ORCA
If the controller supports SAAP, you can use ORCA to install the license key and activate SAAP functionality.
For more information, see "About SAAP (on page 8 )."
Option ROM Configuration for Arrays 12
To install a license key:
1.
Power up the server.
2.
POST runs.
During POST, all controllers in the server are initialized one at a time in the current boot order sequence.
If a controller is connected to one or more hard drives, a message appears during the initialization process for that controller, prompting you to start ORCA.
At the ORCA prompt for the controller that you want to configure, press the F8 key.
The ORCA main menu appears.
3.
4.
5.
Select Manage License Keys.
This option appears only if the Smart Array controller has a 256-MB, or larger, cache installed.
Under the License Key menu, select Add License Key.
Enter the license key in the space provided.
ORCA issues a notification after the license key activates successfully.
To use SAAP features, use the HP Array Configuration Utility. For more information, see "Configuration tasks
Using the ORCA CLI
1.
Power up the server.
POST runs.
Option ROM Configuration for Arrays 13
2.
3.
4.
If the BIOS interface is in Auto mode, change it to Command Line mode as follows: a.
Press the F9 key to open RBSU when prompted during POST. b. c.
In RBSU, select BIOS Serial Console & EMS>BIOS Interface Mode.
Change the setting to Command Line.
Press the Esc key to exit RBSU, and then press the F10 key to confirm that you want to exit. d.
The server reboots, and POST runs again.
During POST, all controllers in the server are initialized one at a time in the current boot order sequence.
If a controller is connected to one or more hard drives, a message appears during the initialization process for that controller, prompting you to start ORCA.
At the ORCA prompt for the controller that you want to configure, press the F8 key.
The ORCA command line prompt appears.
Enter the command for the task that you want to perform. For information about command syntax and to see a list of possible commands, enter help.
If you create a logical drive, format it when you install the operating system. If the operating system is already installed, follow the instructions for formatting logical drives that are given in the operating system documentation.
Option ROM Configuration for Arrays 14
HP Online Array Configuration Utility for
NetWare
About CPQONLIN
The HP Online Array Configuration Utility for NetWare (CPQONLIN) enables you to configure an array on a NetWare server while the server is online.
To configure an array when the server is offline, use ACU.
To install CPQONLIN, obtain the appropriate Smart Component from the HP website
( http://www.hp.com/support ) or the software CD that is provided with the controller. When prompted for product information, enter the appropriate server model name. Installation instructions are provided with the component.
Summary of configuration procedure using
CPQONLIN
1.
2.
3.
4.
5.
At the console prompt, enter cpqonlin.
Press the arrow keys to scroll the highlight to the Array Configuration Utility menu item, and then press the Enter key.
The screen displays a list of the controllers in the server.
Scroll to the controller that you want to configure and then press the Enter key. o
If there are no logical drives connected to the controller, an auto-configuration wizard opens and displays the optimum configuration for the drives on the controller. You can accept the suggested configuration, modify just the RAID level of any logical drives, or use the Custom Configuration
o
If there is at least one logical drive connected to the controller, CPQONLIN continues in manual
configuration mode (" Operating CPQONLIN in manual configuration mode " on page 15 ). Press
the arrow, Enter, and Esc keys to navigate around the screen and set up the new logical drive. To get online help at any time, press the F1 key.
When you have finished configuring the array, save the changes as prompted.
To make new logical drives available for data storage, format them using the instructions given in the operating system documentation.
Operating CPQONLIN in manual configuration mode
When CPQONLIN opens in manual configuration mode, the screen displays two panels.
HP Online Array Configuration Utility for NetWare 15
•
The main panel is the Logical Configuration View panel, which shows the selected controller and a tree of all arrays, logical drives, and unassigned physical drives that are connected to the controller. (To toggle to the physical configuration view, press the Tab key.)
•
The secondary panel displays a menu of configuration options (" Menu options in CPQONLIN " on page
16 ) for the item that is highlighted in the Logical Configuration View panel.
To begin the configuration process, scroll the highlight to the item listed in the main panel that you want to configure and then press the Enter key. The highlight jumps to the secondary panel, where you can continue the configuration process using the same method (scroll to a menu item, and then press the Enter key). To return the highlight to the previous panel at any time in the configuration process, press the Esc key.
For help, press the F1 key.
Detailed procedures for common tasks are described in "Typical manual configuration procedures (on page
Menu options in CPQONLIN
Menu options are visible only if they are applicable. For example, if you highlight the controller in the Logical
Configuration View panel and the controller does not have any unassigned physical drives, the Controller
Options menu does not display the Create New Array menu option.
•
Controller Options menu (appears in the secondary panel when the controller is highlighted in the
Logical Configuration View panel)
Menu option Result of selecting the option
Controller Settings A new panel opens, displaying settings for three options:
Rebuild Priority, Expand Priority, and Accelerator Ratio.
HP Online Array Configuration Utility for NetWare 16
Menu option Result of selecting the option
Create New Array Three panels open:
•
Create Array (displays a menu with the following options: Assign Drive, Assign Spare, Remove Drive, and Accept Changes)
•
Physical Drives (lists the spare drives and unassigned physical drives that are connected to the controller)
•
New Array (shows the updated physical configuration view)
•
Array Options menu (appears in the secondary panel when an array is highlighted in the Logical
Configuration View panel)
Menu option Result of selecting the option
Expand Array
Three panels open:
•
Expand Array (displays a menu with the following options: Assign Drive, Remove Spare, and Accept
Changes)
• Physical Drives (lists the spare drives and unassigned physical drives that are connected to the controller)
•
Expand Existing Array (shows the updated physical configuration view)
A new panel opens, displaying a menu of the valid drives.
Assign Spare
Remove Spare
A new panel opens, displaying the spares.
Delete Entire Array The data and all the logical drive structures on the array are deleted.
•
Logical Drive Options menu (appears in the secondary panel when a logical drive is highlighted in the
Logical Configuration View panel)
Menu option Result of selecting the option
Delete
Drive Settings
The data and the logical drive structure on the array are deleted.
A new panel opens, displaying settings for two options:
Fault Tolerance and Stripe Size.
SSP Settings*
A new panel opens, displaying the Enable or Disable option.
*This menu option is available only with the MSA1000 and MSA1500.
Typical manual configuration procedures
This section describes the procedures for the following common tasks:
•
Creating a new array and logical drive (on page 18 )
•
Adding spare drives (on page 18 )
•
Setting the rebuild priority or expand priority (on page 19 )
•
Setting the accelerator ratio (on page 19 )
•
Expanding an array (on page 20 )
•
Migrating RAID level or stripe size (on page 20 )
HP Online Array Configuration Utility for NetWare 17
Creating a new array and logical drive
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Open CPQONLIN and select the controller that you want to configure.
The Logical Configuration View panel appears.
Press the Enter key.
The highlight moves to the Controller Options panel.
Highlight the Create New Array option, and then press the Enter key.
The screen displays three panels (Create Array, Physical Drives, and New Array), and the highlight moves to the Create Array panel.
Highlight the Assign Drive option, and then press the Enter key.
The highlight moves to the Physical Drives panel.
Highlight a drive that you want to be part of the array, and then press the Enter key.
The New Array panel displays the added drive, and the highlight returns to the Create Array panel.
Repeat steps 4 and 5 until you have finished building the array. o o o o
For the most efficient use of drive space, select physical drives of comparable capacity.
For optimum system performance, select physical drives that are connected to different ports on the controller.
If you intend to create a RAID 5 configuration, keep the risk of logical drive failure low by assigning no more than 14 physical drives to the array.
Do not select any physical drives that you want to be spare drives. Spare drives are created in a
separate procedure (" Adding spare drives " on page 18 ).
Highlight the Accept Changes menu option, and then press the Enter key.
The Create New Logical Drive panel appears.
Select the RAID level that you want the logical drive to use, and then press the Enter key.
Select the stripe size that you want the logical drive to use, and then press the Enter key.
Enter the capacity that you want the logical drive to have, and then press the Enter key.
Press the Esc key to save the settings and return to the Logical Configuration View panel.
To make new logical drives available for data storage, format them using the instructions given in the operating system documentation.
Adding spare drives
Assigning one or more online spare drives to an array enables you to postpone replacement of faulty drives.
However, it does not increase the fault-tolerance level of any logical drives in the array. For example, a logical drive in a RAID 5 configuration suffers irretrievable data loss if two of its physical drives are simultaneously in a failed state, regardless of the number of spare drives assigned to the array.
Any drive that you want to use as a spare must meet the following criteria:
•
It must be an unassigned drive or a spare for another array.
•
It must be of the same type as existing drives in the array (for example, SATA or SAS).
•
It must have a capacity no less than that of the smallest drive in the array.
To add a spare drive to an array:
HP Online Array Configuration Utility for NetWare 18
3.
4.
5.
1.
2.
In the Logical Configuration View panel, highlight the array that needs a spare, and then press the Enter key.
In the Array Options menu, highlight the Assign Spare option, and then press the Enter key.
The screen displays the Valid Spares Selection(s) panel, which displays only the drives that qualify to be spares for the selected array. If a drive that you expect to see is not listed, it might have too small a capacity compared to the other drives in the array. Press the Tab key to toggle to the physical configuration view and check the drive size.
Highlight the drive that you want to assign as a spare, and then press the Enter key.
(Optional) Add more spares to the array by repeating step 3.
When you have finished assigning spares, press the Esc key to return the highlight to the Array Options menu.
Setting the rebuild priority or expand priority
The settings that you use for the rebuild priority and expand priority features determine how much importance you want an array rebuild or expansion to have relative to normal I/O operations.
•
At the low priority setting, the rebuild or expansion takes place only when the controller is not busy handling normal I/O requests. This setting has minimal effect on normal I/O operations. However, an array that is rebuilt at this setting must operate for an extended time with possibly compromised fault tolerance during the rebuild, and if another physical drive fails during this time, you could lose data.
•
At the medium priority setting, rebuild or expansion occurs for half of the time, and normal I/O requests are handled during the rest of the time.
•
At the high priority setting, the rebuild or expansion occurs at the expense of normal I/O operations.
Although system performance is affected, this setting provides better data protection because the array is vulnerable to drive failure for a shorter time.
To modify either of these settings:
1.
In the Logical Configuration View panel, highlight the controller, and then press the Enter key.
2.
The highlight moves to the Controller Options panel.
Highlight the Controller Settings option, and then press the Enter key.
3.
4.
5.
The Controller Settings panel appears.
Highlight the rebuild priority setting that you want this controller to use, and then press the Enter key.
(This setting applies only to logical drives that have been configured with RAID 1+0, RAID 5, or RAID
6 fault tolerance because only these logical drives can be rebuilt.)
Repeat step 3 for the expand priority setting.
Press the Esc key to save the settings and return to the Logical Configuration View panel.
Setting the accelerator ratio
The setting that you use for the accelerator ratio feature determines how much of the cache memory is allocated to read-ahead cache and how much to posted-write cache. Different applications have different optimum settings. This setting applies only if the controller uses a battery-backed cache.
To modify the accelerator ratio:
1.
In the Logical Configuration View panel, highlight the controller, and then press the Enter key.
The highlight moves to the Controller Options panel.
HP Online Array Configuration Utility for NetWare 19
2.
3.
4.
Highlight the Controller Settings option, and then press the Enter key.
The Controller Settings panel appears.
Highlight the accelerator ratio setting that you want this controller to use, and then press the Enter key.
Press the Esc key to save the settings and return to the Logical Configuration View panel.
Expanding an array
You can increase the storage space on an array by adding physical drives. Any drive that you want to add must meet the following criteria:
•
It must be an unassigned drive.
•
It must be of the same type as existing drives in the array (for example, SATA or SAS).
•
It must have a capacity no less than that of the smallest drive in the array.
When you want to expand an array, allow about 15 minutes per gigabyte for the expansion to be completed. During this time, the controller cannot perform any other expansion or migration. Performance
expand an array during periods of low server use.
To expand an array:
1.
2.
Back up all data on the array. Although array expansion is unlikely to cause data loss, observing this precaution provides extra data security.
Confirm that the cache battery is connected and fully charged.
3.
4.
In the Logical Configuration View panel, highlight the array, and then press the Enter key.
In the Array Options menu, highlight the Expand Array option, and then press the Enter key.
The screen displays three panels (Expand Array, Physical Drives, and Expand Existing Array), and the highlight moves to the Expand Array panel.
5.
6.
7.
8.
9.
Highlight the Assign Drive option, and then press the Enter key.
The highlight moves to the Physical Drives panel.
Highlight a physical drive that you want to add to the array, and then press the Enter key. (For optimum use of drive capacity, select a drive that has the same capacity as other drives in the array.)
The highlight returns to the Expand Array panel.
(Optional) Repeat steps 5 and 6 to add more drives.
Highlight the Accept Changes option, and then press the Enter key.
Press the Esc key to begin the array expansion and return to the Logical Configuration View panel.
To view the progress of the array expansion, press the F3 key, and then scroll to the progress bar near the bottom of the screen.
Migrating RAID level or stripe size
When you want to migrate the RAID level or stripe size, allow about 15 minutes per gigabyte for the migration to be completed. During this time, the controller cannot perform any other expansion or migration.
Performance might be degraded slightly during the migration, depending on the Expand Priority and Rebuild
normal server operations, migrate during periods of low server use.
HP Online Array Configuration Utility for NetWare 20
To perform a migration:
1.
Back up all data on the array. Although migration is unlikely to cause data loss, observing this precaution provides extra data security.
2.
3.
Confirm that the cache battery is connected and fully charged.
In the Logical Configuration View panel, highlight the logical drive and then press the Enter key.
The highlight moves to the Logical Drive Options panel.
4.
5.
6.
Highlight the Drive Settings option, and then press the Enter key.
The Drive Settings panel appears.
Modify the Fault Tolerance and Stripe Size settings on this panel to meet your needs.
Press the Esc key to begin the migration and return to the Logical Configuration View panel.
To view the progress of the migration, press the F3 key, and then scroll to the progress bar near the bottom of the screen.
HP Online Array Configuration Utility for NetWare 21
HP Array Configuration Utility
About ACU
ACU is the main tool for configuring arrays on HP Smart Array controllers. It exists in three interface formats: the ACU GUI, the ACU CLI, and ACU Scripting. All formats provide support for standard configuration tasks
(on page 6 ). ACU also provides support for advanced configuration tasks (on page 6 ). Some of the
advanced tasks are available in only one format.
The diagnostic features in ACU are also available in the standalone software HP Array Diagnostics and
SmartSSD Wear Gauge Utility (on page 96 ).
Starting with ACU version 9.0 and ProLiant Gen8 servers and server blades, ACU is accessible both offline and online:
•
Accessing ACU in the offline environment (on page 22 )
Using one of multiple methods, you can run ACU before launching the host operating system. In offline mode, users can configure or maintain detected and supported ProLiant devices, such as optional Smart
Array controllers, integrated Smart Array controllers, and RAID Array controllers. Some ACU CLI features are only available in the offline environment, such as setting the boot controller and boot volume.
•
Accessing ACU in the online environment (on page 27 )
This method requires an administrator to download the ACU executables and install them. You can run
ACU online after launching the host operating system.
Accessing ACU in the offline environment
To access and launch the ACU GUI in an offline environment, use one of the following methods:
•
Launching ACU with HP Intelligent Provisioning (Gen8 or later) (on page 22 )
•
Launching ACU during POST (Gen8 or later) (on page 23 )
•
Launching ACU from the SmartStart CD (G7 or earlier) (on page 23 )
•
Launching ACU from an ISO image (all generations) (on page 23 )
To access the ACU CLI or ACU Scripting in an offline environment, you must launch ACU from an ISO image.
When offline ACU launches, an Execution Mode screen does not appear, because ACU does not support
Remote Service Mode in an offline environment. For this functionality, use ACU in an online environment
(" Accessing ACU in the online environment " on page 27 ).
Launching ACU with HP Intelligent Provisioning (Gen8 or later)
1.
Boot the server.
2.
Press F10 to launch HP Intelligent Provisioning.
HP Array Configuration Utility 22
3.
4.
At the main screen, select Perform Maintenance.
At the Maintenance screen, select Array Configuration Utility (ACU).
The system launches the ACU GUI.
Launching ACU during POST (Gen8 or later)
1.
2.
Boot the server.
During POST, the system recognizes devices.
When the system recognizes a Smart Array controller, press F5.
The system launches the ACU GUI.
Launching ACU from the SmartStart CD (G7 or earlier)
1.
Close all applications.
2.
3.
4.
5.
6.
Insert the SmartStart CD into the CD-ROM drive.
Restart the server.
The server boots from the CD, and then loads the SmartStart executable and drivers.
When prompted, select the language and agree to the license restrictions.
Click Maintain Server.
Click Array Configuration Utility.
ACU opens, scans the local server, and detects controllers. This process can last up to 2 minutes. When controller detection is complete, the controllers are available on the Controller/Device menu.
Launching ACU from an ISO image (all generations)
To launch ACU, you can also boot from an ISO image. To prepare the image, use one of the following methods:
•
Mounting the image on a local drive (on page 23 )
•
Mounting the image through iLO (on page 24 )
•
Burning the image to a CD or DVD (on page 24 )
•
Flashing the image to a USB memory key or SD card (on page 24 )
•
Installing the image on a PXE server (on page 25 )
Booting from the ISO image on a drive, on a key, or through iLO provides the same GUI interface. The user can select to run Offline ACU GUI, ACU CLI, or ACU Scripting.
Mounting the image on a local drive
1.
2.
3.
4.
Download the HP ProLiant Offline Array Configuration Utility ISO image from the HP website
( http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US
&swItem=MTX-aad98a00c0d6469d8abf78e2f3&mode=4&idx=1 ).
Using ISO mounting software, mount the Offline ACU ISO image to a drive.
Set the server to boot the image.
Reboot the server.
HP Array Configuration Utility 23
Mounting the image through iLO
This iLO functionality requires an iLO Advanced license.
1.
2.
Download the HP ProLiant Offline Array Configuration Utility ISO image from the HP website
( http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US
&swItem=MTX-aad98a00c0d6469d8abf78e2f3&mode=4&idx=1 ).
Browse to the server iLO page.
3.
4.
5.
6.
Start the remote console for the server.
On the remote console, use the iLO mount feature to browse to the location of the ISO image.
Select the ISO image to be mounted.
Reboot the server.
Burning the image to a CD or DVD
1.
2.
3.
4.
5.
Download the HP ProLiant Offline Array Configuration Utility ISO image from the HP website
( http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US
&swItem=MTX-aad98a00c0d6469d8abf78e2f3&mode=4&idx=1 ).
Use a third-party software to burn the ISO image to a CD or DVD.
Set the server to boot from the optical drive.
Insert the CD or DVD.
Reboot the server.
Flashing the image to a USB memory key or SD card
1.
2.
Download the HP ProLiant Offline Array Configuration Utility ISO image from the HP website
( http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US
&swItem=MTX-aad98a00c0d6469d8abf78e2f3&mode=4&idx=1 ).
Download the HP USB Key Utility for Windows from the HP website
( http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US
&swItem=MTX-eee9b3632ced47478f9ef85d43&mode=5 ).
CAUTION: Before creating a bootable USB key from the Offline ACU ISO image, back up any critical data stored on the key to a different location. The utility overwrites all data on the key.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Using ISO mounting software, mount the Offline ACU ISO image to a Windows drive.
For this example, use "E:."
Insert a USB key into a USB connector on the Windows system.
For this example, use "F:."
Run the HP USB Key Utility.
At the main screen, select Next.
If you agree with the end user license agreement, select the Agree radio button, and then click Next.
Select Create a bootable USB key from CD/DVD, and then click Next.
At the requirements screen, click Next.
The Select CD/DVD drive: option is selected by default.
From the pull-down menu, select the drive letter for the location of the mounted ISO image (E:).
HP Array Configuration Utility 24
12.
13.
14.
15.
If the location is not shown, press Rescan Source, and then select the location.
The USB Key Drive Letter field shows the drive letter for the USB key (F:).
If the drive letter is not populated, select Rescan Target, and then select the drive letter.
Click Next.
At the following screen, click Next.
The USB key is overwritten with the Offline ACU ISO image.
Select Finish.
Installing the image on a PXE server
To install the Offline ACU ISO image on a PXE server and boot from the image over a network, use the following procedures:
1.
2.
Review the prerequisites (on page 25 ).
Set up PXELinux (on page 25 ).
3.
4.
Configure PXELinux (on page 26 ).
Specify the ISO image path (on page 26 ).
Depending on the network configuration, boot times might vary.
Prerequisites
Before proceeding with the configuration, you must have all the prerequisites:
•
A good, working knowledge of PXE and TFTP
•
A network with a DHCP server on it
•
A TFTP server configured on the same network as the DHCP server
•
A network file server that hosts the ISO images and is accessible by a PXE booted system
•
PXELinux ( http://syslinux.zytor.com/wiki/index.php/PXELINUX )
These instructions presume that you are using a Linux TFTP server and the TFTP package
( http://www.kernel.org/pub/software/network/tftp ). Other TFTP servers should work similarly.
Set up PXELinux
Before proceeding with the configuration, ensure that your TFTP server and PXELinux configuration is set up and configured properly. To set up PXELinux:
1.
2.
Download the HP ProLiant Offline Array Configuration Utility ISO image from the HP website
( http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US
&swItem=MTX-aad98a00c0d6469d8abf78e2f3&mode=4&idx=1 ).
Copy the ISO image to the network file system, and note the location. NFS and Windows® file shares are supported.
3.
4.
For this example, use the following NFS and path to the ISO image:
192.168.0.99:/path/to/acucd/image/hpacuoffline-8.75-12.0.iso
Before proceeding, test your network file system to ensure that it is accessible.
Access the /system directory of the CD in one of the following ways: o
Burn and mount the ISO image.
HP Array Configuration Utility 25
5. o
Extract the ISO image using a third-party tool.
Copy all the files from the /system directory of the CD to your TFTP server so that it is accessible by the TFTP software.
Configure PXELinux
1.
2.
3.
Using the isolinux.cfg file from the /system/ directory of the CD as a guide, copy the labeled targets to your PXELinux configuration file. You do not need to include the entire file: label sos
MENU LABEL HP ProLiant Offline ACU Image
kernel hpboot_v.c32
append vmlinuz initrd=initrd.img media=cdrom rw root=/dev/ram0 ramdisk_size=257144 init=/bin/init loglevel=3 ide=nodma ide=noraid pnpbios=off vga=791 splash=silent showopts TYPE=AUTOMATIC label vsos
MENU LABEL HP ProLiant Offline ACU Image
kernel hpboot_v.c32
append vmlinuz initrd=initrd.img media=cdrom rw root=/dev/ram0 ramdisk_size=257144 init=/bin/init loglevel=3 ide=nodma ide=noraid pnpbios=off vga=791 splash=silent showopts TYPE=MANUAL
Replace the lines kernel hpboot_v.c32 with kernel vmlinuz.
Remove vmlinuz from the append line.
The paths to the files on the TFTP server are vmlinuz and initrd.img. You must modify them to include any directories or naming conventions you may have on your TFTP server.
Specify the ISO image path
For the PXE-booted server to find the ISO image, you must add the ISO image path to the append line in the
PXELinux configuration file.
Add the following arguments: iso1=nfs://192.168.0.99/path/to/acucd/image/hpacuoffline-8.75-12.0.iso iso1mnt=/mnt/bootdevice
The iso1 parameter helps the PXE-booted ACU Offline CD locate the ISO image. The iso1mnt parameter tells the PXE-booted ACUCD where the iso1 image must be mounted.
Your final configuration must be similar to the following example: label sos
MENU LABEL HP ProLiant Offline ACU Image
kernel vmlinuz
append initrd=initrd.img media=cdrom rw root=/dev/ram0 ramdisk_size=257144 init=/bin/init loglevel=3 ide=nodma ide=noraid pnpbios=off vga=791 splash=silent showopts TYPE=AUTOMATIC iso1=nfs://192.168.0.99/path/to/acucd/image/hpacuoffline-8.75-12.0.iso iso1mnt=/mnt/bootdevice label vsos
MENU LABEL HP ProLiant Offline ACU Image
kernel vmlinuz
HP Array Configuration Utility 26
append initrd=initrd.img media=cdrom rw root=/dev/ram0 ramdisk_size=257144 init=/bin/init loglevel=3 ide=nodma ide=noraid pnpbios=off vga=791 splash=silent showopts TYPE=MANUAL iso1=nfs://192.168.0.99/path/to/acucd/image/hpacuoffline-8.75-12.0.iso iso1mnt=/mnt/bootdevice
You can add additional ISO images by specifying the additional iso# and iso#mnt arguments, for example, iso2=/path/to/iso2.iso iso2mnt=/mnt/iso2.
Supported network file systems
The following network file systems are supported for use with PXE booting:
•
NFS: iso1=nfs://192.168.0.99/path/to/acucd/image/hpacuoffline-8.75-12.0.iso iso1mnt=/mnt/bootdevice
NFS volumes are mounted with the following options: o
-o ro o nolock
•
Windows® operating systems: iso1=smbfs://192.168.0.99/share/path/to/acucd/image/hpacuoffline-8.75-12
.0.iso iso1mnt=/mnt/bootdevice
•
Windows® operating systems with login credentials: iso1=smbfs://user:[email protected]/share/path/to/acucd/image/hpacuo ffline-8.75-12.0.iso iso1mnt=/mnt/bootdevice
Accessing ACU in the online environment
To access, install, and launch ACU in the online environment, you must download the ACU executables. All three formats have separate executables.
Starting with version 8.28.13.0, ACU Scripting is now a standalone application that is distributed with the
ACU CLI application. In ACU versions prior to 8.28.13.0, the scripting executable was provided with the
ACU GUI component.
Users familiar with the previous versions of ACU Scripting must now install the ACU CLI application to obtain the scripting executable. The new ACU scripting executable (hpacuscripting) replaces the former executable
(cpqacuxe) in all scripts.
For information about the minimum monitor settings and the version numbers of supported operating systems and browsers, see the README.txt file provided with the executable.
To use ACU in the online environment:
1.
Obtain the executable files from one of the following locations: o
The HP website ( http://www.hp.com/support )
When prompted for product information, enter the appropriate server or server blade model name.
2.
3. o
The software CD that is provided with the controller
Follow the installation instructions provided with the executable.
After the executables are installed, launch each executable in the following manner:
HP Array Configuration Utility 27
o o o
GUI—Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility>Setup
HP Array Configuration Utility.
Depending on your configuration scenario, choose one of the following options:
—
Launching ACU on a local server (on page 28 )
—
Launching ACU on a local server to configure a remote server (on page 29 )
—
Launching ACU on a remote server to configure a local server (on page 29 )
CLI—Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility>Setup
HP Array Configuration Utility CLI.
Scripting—Run hpacuscripting.exe.
Launching ACU on a local server
Microsoft OS
1.
Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility>Setup HP Array
Configuration Utility.
The Execution Mode screen appears.
2.
3. o o
If Local Application Mode is selected, continue with step 2.
If Remote Service Mode is selected, select Local Application Mode, reboot the server, and then continue with step 2.
Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility.
ACU launches in either a browser (older versions) or application window (v8.70 and later) ACU then scans the system and detects controllers. This process can last up to 2 minutes. When controller detection is complete, the controllers are available on the Controller/Device menu.
Configure a controller (" Configuring a controller " on page 41 ).
When configuration is complete, continue with the next step.
4.
5.
If you changed to Local Application mode in step 1, and you are finished configuring arrays on this server, do the following: a. b.
Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility>Setup HP
Array Configuration Utility.
When the Execution Mode screen appears, select Remote Service Mode. c.
Reboot the server.
(Optional) To make newly created logical drives available for data storage, use the operating system disk management tools to create partitions and format the drives.
Linux OS
1.
From any command prompt, enter one of the following:
2. o o
For local mode, enter: cpqauxe-nosmh
For remote mode, enter: cpqacuxe-R
ACU launches in a browser (Mozilla Firefox).
For a list of options, enter the following: cpqacuxe-h
HP Array Configuration Utility 28
Launching ACU on a local server to configure a remote server
1.
2.
3.
4.
5.
6.
7.
8.
On the local server (host), click Start, and then select Programs>HP System Tools>HP Array
Configuration Utility>Setup HP Array Configuration Utility.
The Execution Mode screen appears. o
If Remote Service Mode is selected, continue with step 2. o
If Local Application Mode is selected, select Remote Service Mode, reboot the server, and then continue with step 2.
On the remote server, open the browser.
Enter the following text into the address field of the remote browser (where servername is the name or
IP address of the host): http://servername:2301
The login screen for the System Management Homepage opens.
Enter your login credentials: o o
If you are using version 2.0.0 or later of the System Management Homepage, use your operating system user name and password.
If you are using an earlier version of the System Management Homepage, use your WBEM user name and password.
The System Management Homepage opens.
For more information about the System Management Homepage, see the following: o
The HP System Management Homepage web page
( http://h18013.www1.hp.com/products/servers/management/agents/index.html
) o
The HP System Management Homepage Installation Guide on the HP website
( http://www.hp.com
)
Click Array Configuration Utility on the left side of the screen.
ACU opens, scans the remote server, and detects controllers. This process can last up to 2 minutes.
When controller detection is complete, the controllers are available on the Controller/Device menu.
Configure a controller (" Configuring a controller " on page 41 ).
When configuration is complete, continue with the next step.
To operate ACU on this server in Local Application mode, do the following: a.
Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility>Setup HP
Array Configuration Utility. b. c.
When the Execution Mode screen appears, select Local Application Mode.
Reboot the server.
(Optional) To make newly created logical drives available for data storage, use the operating system disk management tools to create partitions and format the drives.
Launching ACU on a remote server to configure a local server
1.
On the server where ACU is installed, click Start, and then select Programs>HP System Tools>HP Array
Configuration Utility>Setup HP Array Configuration Utility.
The Execution Mode screen appears. o
If Remote Service Mode is selected, continue with step 2.
HP Array Configuration Utility 29
3.
4.
5.
6.
2.
7.
8.
9.
10.
11. o
If Local Application Mode is selected, select Remote Service Mode, reboot the server, and then continue with step 2.
On the server that you want to configure, connect to the Systems Insight Manager server (port: 280), and then log in.
Select Device Queries.
Under Device by Type, select All Servers.
Connect to the server that is running ACU.
Under Device Links, select System Management Homepage.
The login screen for the System Management Homepage opens.
Log in using your credentials: o o
If you are using version 2.0.0 or later of the System Management Homepage, use your operating system user name and password.
If you are using an earlier version of the System Management Homepage, use your WBEM user name and password.
The System Management Homepage opens.
For more information about the System Management Homepage, see the following: o o
The HP System Management Homepage web page
( http://h18013.www1.hp.com/products/servers/management/agents/index.html
)
The HP System Management Homepage Installation Guide on the HP website
( http://www.hp.com
)
Click Array Configuration Utility on the left side of the screen.
ACU opens, scans the remote server, and detects controllers. This process can last up to 2 minutes.
When controller detection is complete, the controllers are available on the Controller/Device menu.
Configure a controller (" Configuring a controller " on page 41 ).
When configuration is complete, continue with the next step.
To operate ACU on the remote server in Local Application Mode, do the following: a.
Click Start, and then select Programs>HP System Tools>HP Array Configuration Utility>Setup HP
Array Configuration Utility. b.
When the Execution Mode screen appears, select Local Application Mode. c.
Reboot the server.
(Optional) To make newly created logical drives available for data storage, in a Windows OS, use the operating system disk management tools to create partitions and format the drives.
Using the ACU GUI
Access ACU with one of the many methods available:
•
Accessing ACU in the offline environment (on page 22 )
•
Accessing ACU in the online environment (on page 27 )
When you launch the ACU GUI, the application opens and ACU scans the system and detects controllers.
This process can last up to 2 minutes. When controller detection is complete, the controllers are available on the Controller/Device menu.
HP Array Configuration Utility 30
After the GUI is open, tasks are distributed among categories. For more information, see "Navigating the
Navigating the GUI
When you open ACU, the Welcome screen appears.
The following elements are visible:
•
Three tabs appear near the top left of the screen. The latest version of the ACU GUI uses tab navigation.
Clicking a tab displays the screen and tasks for the following categories: o o o
Configuration—This screen displays available controller and array tasks that the user can select and complete manually.
In previous versions of ACU, this process was called the Standard Configuration mode. For more
information, see "Configuration screen (on page 32 )."
Diagnostics/SmartSSD—This screen displays a list of controllers and options for generating, viewing, and saving diagnostic reports for those controllers. In previous versions, this tab and screen were called Diagnostics. For more information, see "Diagnostics/SmartSSD screen (on page
Wizards—This screen displays available array and controller tasks that ACU can complete automatically or with minimal user input, such as express configuration.
In previous versions of ACU, this functionality was called the Configuration Wizards mode and
Express mode. For more information, see "Wizards screen (on page 37 )."
•
The Controller/Device menu is below the tabs.
To select a device, click on the menu, and then select a device. Use the scroll bar to view all the devices, as needed.
•
The Rescan System button is to the right of the menu.
After adding or removing devices, click Rescan System to update the list of available devices.
•
The Help button is near the top right of the screen.
HP Array Configuration Utility 31
To access help topics, press the H key or click Help. For more information, see "ACU Help (on page
•
The Exit ACU button is near the bottom left of the screen.
Configuration screen
To access this screen, click the Configuration tab.
The Configuration screen displays the GUI elements from the Welcome screen and provides status, more detailed information, and available tasks or options for the selected device.
When a device is selected, the following elements appear:
•
System Status—This panel, at left, provides the following information and functionality: o
Date and time stamps for the status o o o
A Refresh button to refresh the status
Status icons (critical, warning, and informational) with the number of individual alerts for each category
A View Status Alert link that displays device-specific alerts on the right side of the screen
•
Systems And Devices—This panel, at left, provides the following information and functionality: o
A tree detailing systems, controllers, arrays, physical drives, and logical drives o
Expand all and collapse all buttons
HP Array Configuration Utility 32
o
A Show menu that toggles between Logical View and Physical View
•
Available Tasks—This panel, at right, provides the following information and functionality: o
Tasks that are available for the selected device based on its current status and configuration
HP Array Configuration Utility 33
o
Options and information pertinent to the task, after a task is selected
For a list of possible tasks that are available on the Configuration screen, see "Configuration tasks (on page
Diagnostics/SmartSSD screen
To access this screen, click the Diagnostics/SmartSSD tab.
HP Array Configuration Utility 34
The Diagnostics/SmartSSD screen provides a list of controllers and options related to generating and viewing diagnostic reports.
Tasks are selectable from this screen. Additional tasks are available upon clicking Run Array Diagnostics
Reports.
On the diagnostic report screen, when a device is selected, the following elements appear:
•
Report Contents—This panel, at left, provides the following information and functionality: o
A list of all connected controllers and devices
HP Array Configuration Utility 35
o
Check boxes for individual controllers or all controllers
•
Available Tasks—This panel, at right, provides the following information and functionality: o
Tasks that are available for the selected device based on its current status and configuration
HP Array Configuration Utility 36
o
Options and information pertinent to the task, after a task is selected
For a list of possible tasks that are available on the Diagnostics/SmartSSD screen, see "Diagnostics tasks (on
Wizards screen
To access this screen, click the Wizards tab.
HP Array Configuration Utility 37
The Wizards screen displays the GUI elements from the Welcome screen and provides status, more detailed information, and available wizards or options for the selected device.
When a device is selected, the following elements appear:
•
System Status—This panel, at left, provides the following information and functionality: o
Date and time stamps for the status o o o
A Refresh button to refresh the status
Status icons (critical, warning, and informational) with the number of individual alerts for each category
A View Status Alert link that displays device-specific alerts on the right side of the screen
•
Systems And Devices—This panel, at left, provides the following information and functionality: o
A tree detailing systems, controllers, arrays, physical drives, and logical drives o
Expand all and collapse all buttons
HP Array Configuration Utility 38
o
A Show menu that toggles between Logical View and Physical View
In this example, the Systems And Devices information continues past the edge of the panel. To view all of the information, use the horizontal scroll bar or use the mouse to widen the panel.
•
Available Wizards—This panel, at right, provides the following information and functionality: o
Wizards that are available for the selected device based on its current status and configuration
HP Array Configuration Utility 39
o
Options and information pertinent to the wizard, after a wizard is selected
ACU help
The Help button, at upper right, opens the embedded ACU help file. In addition to providing information about the main screens and tabs, Help also provides several useful topics for new users, including the following:
•
Image Legend—A visual reference list defining the icons and graphical buttons used in ACU
•
Keyboard Controls—An explanation and list of keyboard functions for navigating the GUI
•
Keyboard Shortcuts—A list of keys and operations they perform within the GUI
To view these help topics and others, press the H key or click Help. When the Help window opens, expand the topic "Getting Started with ACU."
The glossary in ACU help defines industry standard and HP terms as they relate to the ACU application.
Configuration tasks
From the Configuration screen, you can perform tasks related to controllers, arrays, physical drives, and logical drives.
HP Array Configuration Utility 40
For certain tasks, the controller must have SAAP activated by a registered license key. For more information,
see "About SAAP (on page 8 )."
When a controller or device is selected, the tasks that appear are a subset of the total number of possible tasks for the selected item. ACU lists or omits tasks based on the controller model and configuration. For example, if the selected controller has no unassigned physical drives, Create Array is not an available task.
The following table lists all the possible tasks for every type of item.
Item Tasks
Controller
Array
Logical drive
Advanced Controller Settings* **
Array Accelerator Settings
Clear Configuration
Controller Settings
Create Array
Disable Standby Controller
Manage License Keys*
More Information
Physical Drive Write Cache Settings
Redundancy Settings*
View Status Alerts
Create Array
Create Logical Drive
Delete
Expand Array
More Information
Move Array**
Re-Mirror Array**
Shrink Array**
Spare Management
Split Mirrored Array**
View Status Alerts
Create Logical Drive
Delete
Erase Drive* **
Extend Logical Drive
Migrate RAID/Stripe Size
Move Logical Drive* **
More Information
Re-enable Failed Logical Drive
View Status Alerts
Unused space
Physical drive
Create Logical Drive
More Information
Erase Drive**
View Status Alerts
Unassigned drives
Create Array
More Information
*This task is not available on all controller models.
**This task requires a controller with SAAP activated by a registered license key or a controller where SAAP functionality
is standard. See "About SAAP (on page 8 )."
Configuring a controller
1.
Open ACU.
HP Array Configuration Utility 41
2.
For more information, see "Using the ACU GUI (on page 30 )."
Select a controller from the Controller/Device menu.
The Configuration screen appears.
3.
4.
5.
Configure the controller: o o
To configure manually, see "Performing a Configuration task (on page 42 )."
To configure with a wizard, see "Using Wizards (on page 48 )" or "Using Express Configuration (on
When prompted, save the configuration.
Do one of the following: o
Configure an additional controller. Repeat steps 3 through 5. o
Click Exit ACU.
Performing a Configuration task
1.
2.
Open ACU.
For more information, see "Using the ACU GUI (on page 30 )."
If ACU is already open, click the Configuration tab.
Select a device from the Controller/Device menu.
HP Array Configuration Utility 42
The System Status, Systems And Devices, and Available Tasks panels appear. The listed tasks are available for this device in its current configuration. For more information, see "Configuration tasks (on
3.
Click a task button.
A list of all possible options for that task appears on the right side of the screen, replacing the task list.
HP Array Configuration Utility 43
4.
5.
6.
Select the settings or configuration options for the device.
Use the Next and Back buttons to navigate multiple screens of options.
Click Save or OK.
Installing a license key with ACU
If the controller supports SAAP, you can use ACU to install the license key and activate SAAP functionality.
For more information, see "About SAAP (on page 8 )."
To install a license key:
1.
Open ACU.
2.
For more information, see "Using the ACU GUI (on page 30 )."
If ACU is already open, click the Configuration tab.
Select a controller from the Controller/Device menu.
The System Status, Systems And Devices, and Available Tasks panels appear.
3.
4.
5.
6.
In the Available Tasks panel, click Manage License Keys.
Specific license key tasks appear. A complete list of existing license keys also appears.
Click Add License Key.
Enter the license key number.
Click Save.
Changing the Spare Activation Mode
The spare activation mode feature enables the controller firmware to activate a spare drive under the following conditions:
•
When a data drive reports a predictive failure (SMART) status
•
When a data drive fails; this mode is the default.
In normal operations, and for older controllers, the firmware starts rebuilding a spare drive only when a data drive fails. With the predictive failure activation mode, rebuilding can begin before the drive fails, reducing the likelihood of data loss that could occur if an additional drive fails.
To change the Spare Activation Mode:
1.
Open ACU.
For more information, see "Using the ACU GUI (on page 30 )."
If ACU is already open, click the Configuration tab.
2.
3.
4.
Select a controller from the Controller/Device menu.
The System Status, Systems And Devices, and Available Tasks panels appear.
In the Available Tasks panel, click Modify Spare Activation Mode.
From the menu, select one of the following modes:
5. o o
Failure Spare Activation
Predictive Spare Activation
Click Save.
HP Array Configuration Utility 44
Working with mirrored arrays
Among the advanced tasks possible with the ACU GUI, you can split a mirrored array and then recombine it. This process entails breaking a RAID 1 or RAID 1+0 mirror into two identical new arrays consisting of RAID
0 logical drives.
Support for these procedures requires the following:
•
The ACU GUI must be run in offline mode.
•
Select controller models must have a valid SAAP license (" About SAAP " on page 8 ).
•
Mirrored arrays being split can have RAID 1, RAID 1+0, RAID 1 (ADM), or RAID 10 (ADM) configurations. Arrays with other RAID configurations cannot be split.
Several reasons exist for splitting and recombining a mirrored array. For more information, see the "RAID
1(+0): breaking mirrors and rebuilding drives" how-to white paper on the HP website
( http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00378986/c00378986.pdf
).
Splitting a mirrored array
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
At the Configuration screen, select the appropriate controller from the Controller/Device menu.
From the Systems and Devices tree, select the appropriate array.
In the Available Tasks panel, click Split Mirrored Array.
Click OK.
When ACU finishes splitting the array, two logical drives appear in the Systems and Devices tree: o
When a RAID 1 or RAID 1+0 array splits, two RAID 0 logical drives are created. o o
When an array that contains a RAID 1 (ADM) logical drive splits, a RAID 1 logical drive and a RAID
0 logical drive are created.
When an array that contains a RAID 10 (ADM) logical drive splits, a RAID 1+0 logical drive and a
RAID 0 logical drive are created.
Shut down the OS.
Power down the server.
With power off, remove the physical drives that constitute one of the new arrays.
If you do not remove the physical drives for one of the arrays, the OS will be unable to distinguish between the two arrays when the server is restarted, because the arrays are identical.
Power up the server.
Restart the OS.
Recombining a split mirrored array
1.
Run the ACU GUI in offline mode. See "Accessing ACU in the offline environment (on page 22 )."
2.
3.
4.
5.
At the Configuration screen, select the appropriate controller from the Controller/Device menu.
From the Systems and Devices tree, select the array to use as the source array.
In the Available Tasks panel, click Re-Mirror Array.
Select the array to be mirrored to the source array.
HP Array Configuration Utility 45
6.
7.
This array is usually the array that was split from the original mirrored array. However, it can be any other array of the correct size.
Click OK.
When ACU finishes re-mirroring the array, restart the OS.
The controller uses the rebuild process to synchronize the mirrored drives. The drive online LED flashes during the rebuild process. Depending on the hard drive size and the server load, this process can take up to 2 hours. You can boot the OS during this time, but the logical drive is not fault-tolerant until the rebuild is complete.
Diagnostics tasks
The ACU Diagnostics feature replaced the Array Diagnostic Utility supported by SmartStart v8.20 and earlier. Beginning with ACU v8.70.9, the diagnostics functionality within ACU has expanded and includes the SmartSSD Wear Gauge.
ACU generates the following reports and logs:
•
Array diagnostic report
This report contains information about all devices, such as array controllers, storage enclosures, drive cages, as well as logical, physical, and tape drives. For supported solid state drives, this report also contains SmartSSD Wear Gauge information.
•
SmartSSD Wear Gauge report
This report contains information about the current usage level and remaining expected lifetime of solid state drives attached to the system.
•
Serial output logs
This log details the serial output for the selected controller.
For each controller, or for all of them, you can select the following tasks:
•
View Diagnostic Report
•
Generate Diagnostic Report
•
View Serial Output Logs
•
View SmartSSD Wear Gauge Report
•
Generate SmartSSD Wear Gauge Report
For the view tasks, ACU generates and displays the report or log. For the generate tasks, ACU generates a report without the graphical display.
For either task, you can save the report. In the SmartStart environment (G7 or earlier servers), you can save the report to a formatted diskette or USB device. In online and offline environments, ACU saves the diagnostic report to a compressed folder, which contains an XML report, a plain text report, and a viewer file so you can display and navigate the report through a web browser.
Each ACU Diagnostics report contains a consolidated view of any error or warning conditions encountered.
It also provides detailed information for every storage device, including the following:
•
Device status
•
Configuration flags
•
Firmware version numbers
HP Array Configuration Utility 46
•
Physical drive error logs
ACU Diagnostics never collects information about the data content of logical drives. The diagnostic report does not collect or include the following:
•
File system types, contents, or status
•
Partition types, sizes, or layout
•
Software RAID information
•
Operating system device names or mount points
Performing a Diagnostics task
1.
2.
3.
Open ACU.
For more information, see "Using the ACU GUI (on page 30 )."
If ACU is already open, click the Diagnostics/SmartSSD tab.
The Diagnostics/SmartSSD screen appears with the following selections: o o
View SmartSSD Wear Gauge Report
Generate SmartSSD Wear Gauge Report o
Run Array Diagnostic Reports
For this example, use the diagnostic reports selection.
Select Run Array Diagnostic Reports.
The array diagnostic report screen appears.
Select a device or devices from the Report Contents panel.
The Available Tasks panel appears. For more information, see "Diagnostics tasks (on page 46 )."
HP Array Configuration Utility 47
4.
Click one of the task buttons: o
If you select Generate Diagnostic Report, wait for the report to generate, and then click Close Report or Save Report. o o
If you select View Diagnostic Report, the report appears. When you are finished viewing the current report, click Close Report, Refresh Report, or Save Report.
If you select View Serial Output Logs, the log appears. When you are finished viewing the log, click
Close Logs.
For more information about reports and viewing them in a browser, see the following sections:
•
"Reported information (on page 96 )"
•
"Identifying and viewing diagnostic report files (on page 103 )"
•
"Identifying and viewing SmartSSD Wear Gauge report files (on page 105 )"
Wizards
From the Wizards screen, you can perform tasks related to controllers, arrays, physical drives, and logical drives.
For certain tasks, the controller must have SAAP activated by a registered license key. For more information,
see "About SAAP (on page 8 )."
When a controller is selected, the wizards that appear are a subset of the total number of wizards that are possible for the selected controller. ACU lists or omits wizards based on the controller model and configuration. For example, if the selected controller has no unassigned physical drives, Expand Array is not an available wizard.
Wizards are available by selecting the root controller in the Systems and Devices tree. The following list includes all possible wizards:
•
Add Logical Drive
•
Controller Settings
•
Expand Array
•
Express Configuration
•
Manage Spare Drive
•
Migrate Logical Drive
•
Move Array
•
Remove Logical Drive
For more information, see "Using Wizards (on page 48 )."
Using Wizards
1.
2.
Open ACU.
For more information, see "Using the ACU GUI (on page 30 )."
If ACU is already open, click the Wizards tab.
Select a controller from the Controller/Device menu.
HP Array Configuration Utility 48
The System Status, Systems And Devices, and Available Wizards panels appear. The listed wizards are
3.
Click a wizard button.
HP Array Configuration Utility 49
A list of all possible options for that wizard appears on the right side of the screen, replacing the wizard list.
4.
5.
6.
Select the settings or configuration options for the device.
Use the Next and Back buttons to navigate multiple screens of options.
Click Save or OK.
Using Express Configuration
Express Configuration is a wizard that creates the optimum number of arrays and logical drives from all of the physical drives that are attached to the controller.
This wizard is available only under two conditions: when an array on the selected controller contains unused drive space, or when physical drives are connected to the controller, but they are not assigned to an array.
To use Express Configuration:
1.
Open ACU.
For more information, see "Using the ACU GUI (on page 30 )."
If ACU is already open, click the Wizards tab.
2.
3.
Select a controller from the Controller/Device menu.
The System Status, Systems And Devices, and Available Wizards panels appear. The listed wizards are
Click Express Configuration.
HP Array Configuration Utility 50
ACU displays possible logical drive configurations based on groupings of drives with the same capacity.
4.
5.
6.
For each logical drive, select a RAID Type.
ACU identifies possible RAID configurations and lists spare drive capability, the size of the logical drive, fault tolerance, and write performance.
Click Next.
The wizard configures the arrays and logical drives.
When the configuration is complete, click Finish.
Using the ACU CLI
Access ACU with one of the many methods available:
•
Accessing ACU in the offline environment (on page 22 )
•
Accessing ACU in the online environment (on page 27 )
Some ACU CLI features are only available in the offline environment, such as setting the boot controller and boot volume.
ACU CLI has two operating modes:
•
Console mode (" Opening the CLI in Console mode " on page 52 )
You can adjust several configuration parameters on several devices without having to restart ACU each time.
•
Command mode (" Opening the CLI in Command mode " on page 52 )
HP Array Configuration Utility 51
You can make an isolated change of just one configuration parameter on one device.
Opening the CLI in Console mode
The syntax of the command required to open the ACU CLI in Console mode depends on the operating system that you are using.
•
For Microsoft® Windows®, enter the following text:
C:\Program Files\Compaq\Hpacucli\Bin\hpacucli.exe
Alternatively, click Start, and select Programs>HP System Tools>HP Array Configuration Utility CLI>HP
Array Configuration Utility CLI.
•
For Linux, enter the following text:
[root@localhost root]# hpacucli
After you have entered Console mode in either operating system, the screen displays the following message and console prompt:
HP Array Configuration Utility CLI 7.15.17.0
Detecting Controllers...Done.
Type "help" for a list of supported commands.
Type "exit" to close the console.
=>
The remaining examples in the ACU CLI section of this guide are described as if entered in Console mode.
Opening the CLI in Command mode
To use Command mode, identify the appropriate ACU CLI command (" The <command> variable " on page
The following examples use help as the command:
•
Using Microsoft® Windows®:
C:\Program Files\Compaq\Hpacucli\Bin\hpacucli.exe help
•
Using Linux:
[root@localhost root]# hpacucli help
The remaining examples in the ACU CLI section of this guide 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. Using angle brackets to denote a required variable and plain brackets to denote an optional variable, the structure of a typical ACU CLI command line is as follows:
<target> <command> [parameter=value]
The <target> variable
This variable provides the path to the device that you want to configure. The device can be a controller, an array, a logical drive, or a physical drive. The syntax used is as follows: controller all | slot=# | wwn=# | chassisname="AAA" | serialnumber=# | chassisserialnumber=# | [array=all|<id>] [logicaldrive all|#]
[physicaldrive all|allunassigned|[#:]#:#,[#:]#:#...|[#:]#:#-[#:]#:#]
HP Array Configuration Utility 52
For example: controller slot=3 controller wwn=500805F3000BAC11 controller slot=2 array A controller chassisname="A" array B logicaldrive 2 controller chassisname="A" physicaldrive 1:0 controller all controller slot=2 array all controller slot=3 physicaldrive 1:2-1:5
The <command> variable
The <command> variable can be any of the following words or phrases, corresponding to typical configuration tasks: add create delete modify remove set target
Nonconfiguration commands are also available:
diag (" Generating a diagnostic report " on page 59 )
help (" The help command " on page 57 )
rescan (" Rescanning the system " on page 60 )
shorthand (" Keyword abbreviations
" on page 54 ) show (" The show command
version (" Displaying the current versions of the application layers " on page
A command often requires a parameter, and some parameters require a value, but the specific parameters and values that are valid for a given command depend on the target to which you apply the command.
To determine the valid parameters and values for a particular combination of target and command variables,
in other sections of this guide.
Querying a device
If you do not know what values a parameter can have, you can sometimes query the device to find out by entering a ? as the value of the parameter.
Example command:
=> ctrl ch="Lab4" ld 1 modify raid=0 ss=?
A typical screen response in this case could be:
Available options are:
8
16 (current value)
32
64
128 (default)
256
HP Array Configuration Utility 53
Hiding warning prompts
When you enter a command for an operation that can potentially destroy user data, the CLI displays a warning and prompts you for input (a y or an n) before continuing the operation. This situation is undesirable when running batch file scripts. To prevent warning prompts from being displayed, use the term forced as a parameter.
Example command: ctrl ch="Lab4" ld 1 delete forced
Keyword abbreviations
Several commonly used keywords in the ACU CLI have acceptable abbreviations, as shown in the following table. For a complete list of abbreviations, enter help shorthand in the ACU CLI.
Keyword Abbreviation in ACU
CLI
Keyword Abbreviation in
ACU CLI adapterid ai mnpdelay mnpd allunassigned all nobatterywritecache nbwc arrayaccelerator aa parallelscsi ps cacheratio cr physicaldrive pd chassisname* ch* postprompttimeout ppto chassisserialnumber csn preferredpathmode ppm chassisslot chs queuedepth qd configurationmode connectionname cm cn raid1writebuffering rebuildpriority r1wb rp controller ctrl redundantcontroller rc ctrlpath cp serialnumber sn degradedperformancemode dpo drivetype dt drivewritecache dwc elevatorsort es enclosure enc exitonerror eoe expandpriority ep spareactivationmode ssdphysicaldrive stripesize surfaceanalysiseventnotify surfacescandelay surfacescanmode sufacescanpriority sam ssdpd ss saen ssd ssm sp inconsistencyrepairpolicy irp surfacescanschedule sss licensekey lk tapedrive td logicaldrive ld waitforcacheroom wfcr
*The CLI also uses this keyword and abbreviation for the terms box name and RAID array ID.
The show command
The show command enables you to obtain information about a device.
Syntax:
<target> show [detail]|[status]
HP Array Configuration Utility 54
When you specify a target that consists of several devices, the information in the output is normally less comprehensive than when you specify only one device as the target. You can use the [detail] parameter in this case to retain all the information usually given for individual devices.
An extra parameter is available for controller targets: config. This parameter is used as follows:
<target controller> show config [detail]
If you use the config parameter, the output includes information about each device connected to the controller.
Example 1
=> ctrl slot=9 show
A typical output would be:
Smart Array P421 in Slot 9
Bus Interface: PCI
Slot: 9
Serial Number: PBKTV0XTAZZ005
RAID 6 (ADG) Status: Enabled
Controller Status: OK
Hardware Revision: A
Firmware Version: 0.02-106
Rebuild Priority: Medium
Expand Priority: Medium
Surface Scan Delay: 3 secs
Surface Scan Mode: Idle
Queue Depth: Automatic
Monitor and Performance Delay: 60 min
Elevator Sort: Enabled
Degraded Performance Optimization: Disabled
Inconsistency Repair Policy: Disabled
Wait for Cache Room: Disabled
Surface Analysis Inconsistency Notification: Disabled
Post Prompt Timeout: 15 secs
Cache Board Present: True
Cache Status: OK
Accelerator Ratio: 10% Read / 90% Write
Drive Write Cache: Disabled
Total Cache Size: 1024 MB
Total Cache Memory Available: 816 MB
No-Battery Write Cache: Disabled
Cache Backup Power Source: Capacitors
Battery/Capacitor Count: 1
Battery/Capacitor Status: OK
SATA NCQ Supported: True
Spare Activation Mode: Activate on drive failure
Controller Temperature (C): 40
HP Array Configuration Utility 55
Cache Module Temperature (C): 0
Capacitor Temperature (C): 0
Boot Controller: True
Primary Boot Volume: logicaldrive 1
Secondary Boot Volume: logicaldrive 1
Example 2
=> ctrl all show
Because this target consists of several devices, the output will be brief. A typical output would be:
MSA1000 at dog (sn: P56350D9IP903J, csn: (9J3CJN71XDCH, wwn:
500805F3000BAC11)
Smart Array 5312 in Slot 3 (sn: P4AB5X9BFMLNTJ)
Smart Array 532 in Slot 2 (sn: P44940LDAORS4F)
Example 3
=> ctrl ch="lab4" show config
The output in this case will have detailed information because the target consists of only one device. A typical output would be:
MSA1000 at dog (sn: P56350D9IP903J, csn: (9J3CJN71XDCH, wwn:
500805F3000BAC11) array A (Parallel SCSI, Unused Space: 20091 MB) logicaldrive 1 (219 MB, RAID 6(ADG), OK) physicaldrive 1:3 (box 1:bay 3, Parallel SCSI, 4.3 GB, OK) physicaldrive 1:4 (box 1:bay 4, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:5 (box 1:bay 5, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:6 (box 1:bay 6, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:7 (box 1:bay 7, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:9 (box 1:bay 9, Parallel SCSI, ??? GB, failed, spare) unassigned drive 1:1 (box 1:bay 1, Parallel SCSI, 36 GB, OK) physicaldrive 1:2 (box 1:bay 2, Parallel SCSI, 36 GB, OK) physicaldrive 1:8 (box 1:bay 8, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:10 (box 1:bay 10, Parallel SCSI, 9.1 GB, OK) physical physicaldrive 1:11 (box 1:bay 11, Parallel SCSI, 9.1 GB, OK)
Displaying the current versions of the application layers
The version command displays the current versions of the application and other software layers.
Syntax: version
Example command: version
A typical output would be:
ACU CLI Version: 9.10.16.0
HP Array Configuration Utility 56
SoulAPI Version: 6.0.15.0
InfoManager Version: 6.1.14.0
The help command
To get help with the CLI, enter help at the CLI prompt, and then enter one or more help items, as follows:
=> help <item1> [item2] [item3]
A help item can be any of the following:
•
A CLI command (" The <command> variable " on page 53 )
•
An ACU CLI keyword or keyword abbreviation (" Keyword abbreviations " on page 54 )
•
A CLI parameter
•
A term commonly used in ACU, such as migrate, extend, or cache
•
The word shorthand (gives a list of abbreviations for keywords in the CLI)
The help feature of the ACU CLI behaves like a browser search engine in that each item that you add to the help input string reduces the amount of help output text. For example, help controller produces extensive information, while help controller remove restricts the help output to information about how the remove command applies to controllers.
Typical procedures
The following sections describe some common ACU CLI procedures.
Setting the boot controller
This procedure is only available in the offline environment.
The boot controller is the first controller that the system examines (after power up) to find a bootable logical drive or volume. To work properly, the boot controller must have a designated boot volume. See "Setting the
Syntax:
<target> modify [bootcontroller=enable|disable] where <target> is a controller with a volume that can be set as the boot volume.
Example command: controller slot=1 modify bootcontroller=enable
Setting the boot volume
This procedure is only available in the offline environment.
The boot volume is the volume that contains the OS and its support files. To work properly, the boot volume
Syntax:
<target> modify [bootvolume=primary|secondary|none] where <target> is a controller and a logical drive.
Example commands: controller slot=1 ld 1 modify bootvolume=primary controller slot=1 ld 2 modify bootvolume=secondary
HP Array Configuration Utility 57
controller slot=1 ld 1 modify bootvolume=none
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 <target> for the CLI operations.
After you have set the target, any command that you enter in the CLI without a specified <target> is automatically applied to the set target. If you must also perform operations on other devices, you can still do so at any time by specifying the <target> for each of those operations as usual. You can also change the set target or clear it completely. The set target is automatically cleared when you close the CLI.
IMPORTANT: You cannot use the set target command in batch file scripts.
Syntax: set target <target> where <target> is a controller, array, or logical drive.
Example commands:
=> set target ctrl slot=3
=> clear target
Typical scenario
First, set a target as follows:
=> set target ctrl ch="Lab 4"
=> show target controller chassisname="Lab 4"
As an example of how the set target command works, check the status of array A on this controller:
=> array A show
MSA1000 at Lab 4 array A
Interface Type: Parallel SCSI
Unused Space: 7949 MB
Status: OK
Note that the controller does not need to be specified because it is currently the set target.
Now clear the target, reset it, and enter a few commands for the new set target:
=> clear target
=> set target ctrl slot=3
=> array A add drives=1:7,1:8,1:9
=> array B add spares=1:10,1:11
=> ctrl slot=4 ld 3 modify ss=64
=> modify rp=high
This sequence includes a command for a different target (the controller in slot 4) as a demonstration. Note that the next command in the sequence (the one for modifying the rebuild priority) applies to the controller in slot 3, not the one in slot 4. This is because the command does not specify a <target> for the rebuild priority, so the default set target is used instead.
HP Array Configuration Utility 58
Identifying devices
You can enter a command that causes the LEDs on target devices to flash, enabling you to identify the devices. After an hour, the LEDs stop flashing. You can also stop LED flashing by entering the off command.
Syntax:
<target> modify led=on|off
Example commands:
=> ctrl ch="Lab 4" modify led=on
=> ctrl ch="Lab 4" array A modify led=off
Deleting target devices
Syntax:
<target> delete [forced] where <target> can be a controller, array, or logical drive. Except in the case of controllers, you can delete several devices simultaneously if they are of similar type by using the all keyword.
Because deleting a target device can result in data loss, the screen displays a warning prompt unless you include the forced parameter.
Example commands:
=> ctrl ch="Lab 4" delete forced
=> ctrl slot=3 ld all delete
Generating a diagnostic report
HP provides several ways for administrators to generate diagnostic information, including all three ACU formats and the standalone HP Array Diagnostics and SmartSSD Wear Gauge Utility.
In ACU CLI, the diag command outputs diagnostic information about a specified controller or all controllers on the system. The ssdrpt option generates the SmartSSD Wear Gauge report.
Syntax:
<target> diag <file=filename> [ris=on|off] [ssdrpt=on|off] [xml=on|off]
[zip=on|off] where the following is designated:
•
<target> is a controller or all controllers.
•
<file=filename> designates the target file in which the diagnostic information is saved.
•
[ris=on|off] determines whether RIS information is or is not included. The off value is provided for backward compatibility and is ignored.
•
[ssdrpt=on|off] specifies to generate or not generate the Smart SSD Wear Gauge report. The default is off.
•
[xml=on|off] outputs diagnostic information in formatted XML. The off value is provided for backward compatibility and is ignored.
•
[zip=on|off] compresses the output to a zipped file. Default behavior is uncompressed. The off value is provided for backward compatibility and is ignored.
Example commands: ctrl all diag file=c:\allcontrollers.zip ctrl slot=4 diag file=c:\ctrl_slot4.zip ctrl ch="mybox" diag file=mybox.zip ssdrpt=on
HP Array Configuration Utility 59
Erasing a physical or logical drive
Syntax:
<target> modify [erase erasepattern=zero|random_zero|random_random_zero][deleteaftererase=yes|n o] where the target can be any valid physical drive or logical drive. The option to delete the target after erasing it is valid only if the target is a logical drive.
To stop an erase process at any time, enter the stoperase command.
Example commands:
=> ctrl slot=3 ld 2 modify erase erasepattern=zero
=> ctrl slot=4 ld all modify erase erasepattern=random_zero
=> ctrl slot=3 ld 2 modify stoperase
Rescanning the system
A rescan detects devices that have been added to the system since the previous rescan or since the ACU CLI was started, whichever is more recent.
Syntax:
Use the word rescan directly at the ACU CLI prompt, without any target device or parameters.
Example command:
=> rescan
Entering or deleting a license key
Some advanced configuration tasks (available only on certain controller models) can be performed only after software is installed on the controller and a license key is registered to activate the software.
Syntax:
<target> add [lk=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx] where the target is any valid controller. The hyphens are optional.
To delete a license key, use a standard delete command but use the license key (not the controller) as the target:
<target> delete
Example commands:
=> ctrl slot=5 lk=12345-65432-78787-43434-24680 delete
=> ctrl slot=4 add lk=9876543210222224444466666
Optimizing controller performance for video
On some controller models, you can optimize the controller performance for video.
For this feature to be available, you must install SAAP on the controller and register the SAAP license key.
Syntax:
<target> modify dpo=enable elevatorsort=disable irp=enable queuedepth=automatic mnpd=60 where the target is any valid controller.
HP Array Configuration Utility 60
The queuedepth parameter can also have a numerical value from 2 to 32, and the mnpd parameter can have any value from 0 (disabled) to 60.
To disable the video performance optimization feature, reverse the disable and enable values noted above, set the queue depth to automatic, and set mnpd to 0, as in the second example command.
Example commands:
=> ctrl slot=5 modify dpo=enable elevatorsort=disable irp=enable queuedepth=16 mnpd=25
=> ctrl slot=3 modify dpo=disable elevatorsort=enable irp=disable queuedepth=automatic mnpd=0
Creating a logical drive
Syntax:
<target> create type=ld [parameter=value]
<target> is usually a controller, but it can be an array if you are creating an additional logical drive on an existing array.
If you want to create a logical drive on a group of physical drives that are not yet assigned to an array, you do not have to build the array first. In the CLI, unlike in the GUI, the array is created automatically at the same time as the logical drive.
The standard parameters used when creating a logical drive are described in the following table. If you do not specify a particular parameter, the CLI uses the appropriate default value.
Parameter Acceptable values Comments drives raid
[#:]#:#,[#:]#:#,...|[#:]#:#–[#:]#:#
|all|allunassigned
0|1|1adm|1+0|1+0adm|5|50|6|60|?
The default setting is all.
The default setting is the highest RAID level that the controller model and number of drives can support, except
50 or 60 (which must be specified deliberately). numberparityg roups ss
2|#
8|16|32|64|128|256|512|1024|default
|?
The default value is 2.
Units are KB.*
The default setting depends on the
RAID level. size
#|min|max|maxmbr|?
This parameter determines the desired size of the logical drive.
Units are MB.*
The default setting is max. sectors
32|63|default|?
The default setting depends on the operating system. aa drivetype enable|disable|? sas|satalogical|sata|saslogical|par allelscsi|ss_sas|ss_sata|?
The default setting is enable.
—
*Use only these units. Do not enter any extra text in the command to specify the units.
If you specify an array as the target, you can omit the drives parameter, because the drives are already implicitly defined by the array ID. This feature is useful if you are entering the command directly into the CLI console because you do not need to remember which drives belong to the array. When you write a batch file, however, it is often easier to specify every drive in the array than to parse out the array ID.
HP Array Configuration Utility 61
When you use the drives parameter you can list each drive individually, you can specify a drive range, or you can specify both a range and some individual drives. A drive range can span ports, boxes, and bays.
If you specify individual drives, they do not have to form a continuous sequence. If you specify a range, the
CLI automatically excludes from the target any drive in the range that is unavailable (for example, a drive is excluded if it already belongs to an array, is a spare, has too small a capacity, or has failed).
If you want to specify an existing array by its drives rather than by array ID, then all of the drives that you specify must belong to the same array, and none of the drives in the array can be omitted.
Example commands: ctrl slot=5 create type=ld drives=1:0,1:1,1:3 raid=adg ctrl slot=5 create type=ld drives=1:1-1:3 raid=adg ctrl slot=5 create type=ld drives=1:7,1:10-2:5,2:8-2:12 raid=adg ctrl slot=5 array A create type=ld size=330 raid=adg
The following pair of commands demonstrates how the drives parameter can be used in a batch file to create two logical drives on the same array, one of 330 MB and the other of 450 MB: ctrl slot=2 create type=ld drives=1:1-1:6 size=330 raid=adg ctrl slot=2 create type=ld drives=1:1-1:6 size=450 raid=5
Sample scenario
Consider a situation in which you want to create two arrays. One of these arrays needs two logical drives, while the other needs only one.
First, determine what physical drives are available and what their properties are:
=> ctrl ch="Lab 4" pd all show
For this sample scenario, the screen response is:
MSA1000 at Lab 4 unassigned physicaldrive 1:12 (box 1:bay12, Parallel SCSI, 36.4 GB, OK) 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.1 GB, OK) physicaldrive 1:14 (box 1:bay14, Parallel SCSI, 9.1 GB, OK)
The second array is to be created on the two remaining physical drives. Before creating this array, determine what RAID options are available for these drives:
=> ctrl ch="Lab 4" create type=ld drives=1:13,1:14 size=300 raid=?
The response in this case is:
Available options are:
0
HP Array Configuration Utility 62
1+0 (default value)
Now, create the new array:
=> ctrl ch="Lab 4" create type=ld drives=1:13,1:14 size=300 raid=1+0
It is not strictly necessary to specify the RAID level in this example because it is the highest possible level for this scenario and will be used by default. However, it is included in the command as an example.
Now, verify that the array has been formed:
=> ctrl ch="Lab 4" pd all show
The screen response is:
MSA1000 at Lab 4 array A physicaldrive 1:12 (box 1:bay12, Parallel SCSI, 36.4 GB, OK) array B physicaldrive 1:13 (box 1:bay13, Parallel SCSI, 9.1 GB, OK) physicaldrive 1:14 (box 1:bay14, Parallel SCSI, 9.1 GB, OK)
To create a second logical drive on array B, you can specify the array (method A) or you can specify every physical drive in the array (method B).
=> ctrl ch="Lab 4" array B create type=ld size=900 (method A)
=> ctrl ch="Lab 4" create type=ld drives=1:13,1:14 size=900 (method B)
Finally, verify that the logical drives have all been created correctly:
=> ctrl ch="Lab 4" ld all show
MSA1000 at Lab 4 array A 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)
Moving a logical drive
ACU now enables you to move a single logical drive from one array to another array. This feature is available on Gen8 Smart Array controllers with SAAP enabled.
When moving the logical drive, you can choose one of the following destinations:
•
An existing array
•
A new array you create
To move a logical drive to an existing array, use the following information.
Syntax:
<target> modify [newarray=]
Command examples: ctrl slot=1 ld 3 modify newarray=C ctrl slot=1 ld 3 modify newarray=? // shows the available arrays
To move a logical drive and create a new array, use the following information.
Syntax:
<target> modify [drives=[#: ]#:#,[#: ]#:#,[#: ]#:#–[#: ]#:#,...]
Command examples:
HP Array Configuration Utility 63
ctrl slot=1 ld 3 modify drives=2e:1:1-2e:1:4 ctrl slot=1 ld 3 modify drives=? // shows the available drives
You can use the drivetype parameter to specify the drive interface type. When selecting all physical drives, and multiple drive types exist, you must specify the drive interface type. Mixed drives are not allowed on the same array or logical drives. If all drives on a controller are the same type, this parameter is not needed.
For drivetype, use one of the following valid options:
[drivetype=sas | satalogical | sata | saslogical | parallelscsi | ss_sas | ss_sata | ?]
Command examples: controller slot=5 ld 1 modify drives=? drivetype=sas controller slot=5 array A modify drives=? drivetype=ss_sas
Viewing enclosure information
The enclosure keyword is a valid target for the show command, and it outputs the storage enclosure information.
Syntax: enclosure [ all | port:box | serialnumber=xxx ] show [ detail | status ] where the target can be any valid storage controller.
Example commands: controller slot=5 enclosure all show controller slot=5 enclosure 4E:1 show detail controller slot=5 enclosure serialnumber=UAB123456 show status
Viewing physical drives for an HBA
The nonsa keyword shows the physical drives behind an HBA or "non-smart array."
Syntax:
<target> nonsa show [ssdinfo]
Command examples: controller nonsa show controller nonsa show ssdinfo
Viewing SSD physical drives
The ssdphysicaldrive keyword is a valid target for the show command, and it outputs the solid state physical drives on the specified controller.
Syntax:
<target> ssdpd all show [detail] where the target is any valid controller.
Example commands: controller slot=5 ssdpd all show controller slot=5 ssdpd all show detail
Viewing SSD information
The ssdinfo keyword provides a summary for solid state drives for the specified controller.
HP Array Configuration Utility 64
Syntax:
<target> show ssdinfo [detail | summary]
Command examples: controller slot=1 show ssdinfo controller all show ssdinfo controller all show ssdinfo detail controller all show ssdinfo summary
Assigning a chassis name to the controller
If a controller is configured with at least one logical drive, you can give the controller a simplified name (the chassis name) to make it easier to identify and enter the correct controller in a command.
Syntax:
<target> modify ch="new chassis name" where <target> is a controller. If you change the chassis name of a controller that you have set as the
default target (" Setting the target " on page 58 ), you must reset the target.
Example commands:
=> ctrl sn=P56350D9IP903J modify ch="Lab 6"
=> ctrl ch="Lab 4" modify ch="Lab 6"
Managing spare drives
Assigning one or more online spare drives to an array enables you to postpone replacement of faulty drives.
However, it does not increase the fault-tolerance level of any logical drives in the array. For example, a logical drive in a RAID 5 configuration suffers irretrievable data loss if two of its physical drives are simultaneously in a failed state, regardless of the number of spare drives assigned to the array.
Any drive that you want to use as a spare must meet the following criteria:
•
It must be an unassigned drive or a spare for another array.
•
It must be of the same type as existing drives in the array (for example, SATA or SAS).
•
It must have a capacity no less than that of the smallest drive in the array.
Syntax:
<target> add spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|allunassigned
[forced]
<target> remove spares=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|all where <target> is an array (or logical drive, if the array contains only one logical drive). The forced parameter represses any warning message prompts. If you specify a drive range, any drives in the range that do not meet the previous criteria are not used.
Example commands:
=> ctrl slot=3 array B add spares=1:6
=> ctrl slot=4 array all add spares=1:5,1:7
=> ctrl slot=5 array A add spares=1:1–1:5
=> ctrl slot=5 array A remove spares=1:1–1:5
HP Array Configuration Utility 65
Setting the spare activation mode
The spare activation mode feature enables the controller firmware to activate a spare drive under the following conditions:
•
When a data drive reports a predictive failure (SMART) status
•
When a data drive fails; this mode is the default.
In normal operations, and for older controllers, the firmware starts rebuilding a spare drive only when a data drive fails. With the predictive failure activation mode, rebuilding can begin before the drive fails, reducing the likelihood of data loss that could occur if an additional drive fails.
Use the spareactivationmode keyword to toggle the spare activation mode for the controller between drive failure and drive predictive failure.
Syntax:
<target> modify spareactivationmode=[ failure | predictive ]
Example commands: controller slot=1 modify spareactivationmode=predictive controller slot=1 modify spareactivationmode=failure
Expanding an array
You can increase the storage space on an array by adding physical drives. Any drive that you want to add must meet the following criteria:
•
It must be an unassigned drive.
•
It must be of the same type as existing drives in the array (for example, SATA or SAS).
•
It must have a capacity no less than that of the smallest drive in the array.
IMPORTANT: An array expansion, logical drive extension, or logical drive migration takes about 15 minutes per gigabyte. While this process is occurring, no other expansion, extension, or migration can occur simultaneously on the same controller. Controllers that do not support a battery-backed write cache do not support this process.
Syntax:
<target> add drives=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|allunassigned
[forced] where <target> is an array (or a logical drive, if the array contains only one logical drive). The forced parameter represses any warning message prompts. If you specify a drive range, any drives in the range that do not meet the previous criteria are not used.
If you add an odd number of drives to an array that contains a RAID 1+0 logical drive, you are prompted to convert the RAID 1+0 logical drive to RAID 5 or RAID 6 (ADG). Adding the forced parameter to the command prevents this prompt from appearing.
Example commands:
=> ctrl slot=3 array A add drives=1:0,1:1
=> ctrl slot=4 ld 1 add drives=allunassigned
=> ctrl slot=5 array A add drives=1:1–1:5
Shrinking an array
Some controllers may not support this option or may require a license key to enable this feature.
HP Array Configuration Utility 66
You can shrink the size of an array by removing a drive from an existing array. Observe the following criteria:
•
After the shrink, the array must have sufficient capacity to contain all of the configured logical volumes.
•
You may not remove drives from the array if the resulting number of drives does not support the fault tolerance (RAID level) of any existing logical drive. For example, if you have an array with four physical drives and a RAID 5 logical drive, you can remove, at most, one drive, because RAID 5 requires at least three physical drives.
•
If the array contains a RAID 1+0 logical drive, you can remove only an even number of drives.
•
If the array contains a compound RAID (RAID 50 or RAID 60) logical drive, you can remove drives only in multiples of the number of parity groups. For example, an array with 10 physical drives and a RAID
50 logical drive can be shrunk by removing two or four drives only.
Syntax:
<target> remove drives=[#:]#:#-[#:]#:# where <target> is an array, and the specified physical drives are being removed to shrink the array.
For example, in an existing array (array a), six drives (1e:1:4-1e:1:9) are in use. With all criteria met, you can shrink the array to four drives by removing the last two drives with the command: <array a> remove drives=1e:1:8-1e:1:9
Example commands:
=> array a remove drives=1e:1:12-1e:1:14
=> array b remove drives=1c:1:6-1c:1:7
Moving an array
Some controllers may not support this option or may require a license key to enable this feature.
You can move an array by designating different physical drives for the array. To move the array, each of the physical drives where the array will reside must meet the following criteria:
•
It must be an unassigned drive.
•
It must be of the same type as the physical drives currently in the source array (for example, SATA or
SAS).
•
The destination drives must have sufficient capacity to hold all the logical drives present in the source array.
Like array creation and expansion, the useable space in all drives is reduced to the size of the smallest physical drive in the destination disk set.
Moving an array automatically removes any previously assigned spare drives. If spares are assigned to the existing array, they must be designated for the array when it is moved.
Syntax:
<target> modify drives=[#:]#:#-[#:]#:# spares=[#:]#:#-[#:]#:# where <target> is an array, and the specified physical drives are the new destination for the array.
For example, in an existing array, three 72-GB SAS drives (1e:1:4-1e:1:6) are the source. Another drive of the same size is the spare (1e:1:9). With all criteria met, you can move the array to three different 72-GB SAS drives by specifying the new destination drives in the command (1e:1:12-1e:1:14). To maintain the same spare drive, be sure to designate the spare drive for the moved array.
Example commands:
HP Array Configuration Utility 67
=> array a modify drives=1e:1:12-1e:1:14 spares=1e:1:9
=> array b modify drives=1c:1:6-1c:1:7
Replacing an array
Some controllers may not support this option or may require a license key to enable this feature.
You can replace an array by designating different physical drives for the array. To replace the array, each of the physical drives where the array will reside must meet the following criteria:
•
The destination drives must all be the same type (for example, SATA or SAS), but do not have to be same type as the drives in the source array.
•
A destination drive does not have to be an unassigned drive, but if it is assigned, it must be a drive assigned to the array being replaced.
•
The destination drives must have sufficient capacity to hold all the logical drives present in the source array.
Like array creation and expansion, the useable space in all drives is reduced to the size of the smallest physical drive in the destination disk set.
Replacing an array automatically removes any previously assigned spare drives. If spares are assigned to the existing array, they must be designated for the array when it is moved.
Syntax:
<target> modify drives=[#:]#:#-[#:]#:# spares=[#:]#:#-[#:]#:# where <target> is an array, and the specified physical drives are the new destination for the array.
For example, in an existing array, three 72-GB SAS drives (1e:1:4-1e:1:6) are the source. Another drive of the same size is the spare (1e:1:9). With all criteria met, you can move the array to three different 72-GB SAS or SATA drives by specifying the new destination drives in the command (1e:1:12-1e:1:14). To maintain the same spare drive, be sure to designate the spare drive for the moved array.
Example commands:
=> array a modify drives=1e:1:12-1e:1:14 spares=1e:1:9
=> array b modify drives=1c:1:6-1c:1:7
Extending a logical drive
If the operating system supports logical drive extension, you can use any unassigned capacity on an array to enlarge one or more of the logical drives on the array.
IMPORTANT: An array expansion, logical drive extension, or logical drive migration takes about 15 minutes per gigabyte. While this process is occurring, no other expansion, extension, or migration can occur simultaneously on the same controller. Controllers that do not support a battery-backed write cache do not support this process.
Syntax:
<target> modify size=#|max|? [forced] where <target> is a logical drive.
If the operating system does not support logical drive extension, carrying out this command makes data on the logical drive unavailable. Therefore, the CLI displays a warning prompt as a safeguard in case you are using such an operating system. To prevent the prompt from appearing, use the forced parameter.
Example commands:
=> ctrl slot=3 ld 1 modify size=max
HP Array Configuration Utility 68
=> ctrl slot=4 ld 1 modify size=?
=> ctrl slot=3 ld 2 modify size=500 forced
Migrating a logical drive
This command enables you to adjust the stripe size (data block size) or RAID level of a selected logical drive.
For more information, see "Selecting a RAID method (on page 117 )."
Consider the following factors before performing a migration:
•
For some RAID-level migrations to be possible, you might need to add one or more drives to the array.
•
For migration to a larger stripe size to be possible, the array might need to contain unused drive space.
This extra space is necessary because some of the larger data stripes in the migrated array are likely to be filled inefficiently.
IMPORTANT: An array expansion, logical drive extension, or logical drive migration takes about 15 minutes per gigabyte. While this process is occurring, no other expansion, extension, or migration can occur simultaneously on the same controller. Controllers that do not support a battery-backed write cache do not support this process.
Syntax:
<target> modify [raid=0|1+0|1|5|6|adg|?] [ss=8|16|32|64|128|256|default|?] where <target> is a logical drive.
The following limitations apply to this command:
•
You cannot simultaneously query the RAID level and the stripe size of any given logical drive.
•
If you do not specify a RAID level for a query or migration, the CLI uses the existing value by default.
•
If you do not specify a stripe size, the CLI uses the default stripe size value for the RAID level that you specify.
Example commands:
=> ctrl slot=3 ld 1 modify raid=1
=> ctrl slot=4 ld 2 modify ss=16
=> ctrl slot=2 ld 3 modify raid=5 ss=16
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.
•
In Manual mode, all I/O traffic to a given logical drive is directed through a designated controller. In
Syntax:
<target> modify [preferredpathmode=automatic|manual|?] where <target> is a redundant controller.
Example command: controller ch="lab 3" modify ppm=manual
HP Array Configuration Utility 69
Assigning a redundant controller to a logical drive
system to Manual, you must use the chassisslot command to assign each logical drive in the system to one of the redundant controllers.
Syntax:
<target> modify [chassisslot=#|?] where <target> is a valid logical drive on a controller that is in an active/active configuration and # denotes the chassis slot number of the redundant controller. (To obtain the chassis slot number, use the show command on the controller.)
Example command: controller ch="lab 3" ld 1 modify chs=2
Disabling a redundant controller
This command disables a redundant controller that is in an Active-Standby configuration.
IMPORTANT: The redundant controller cannot be re-enabled after you have disabled it.
Syntax:
<target> modify redundantcontroller=disable where <target> is a controller that has an enabled redundant controller.
Example command:
=> ctrl ch="redundant Lab4" modify rc=disable
Changing the Rebuild Priority setting
The Rebuild Priority setting determines the urgency with which the controller treats an internal command to rebuild a failed logical drive.
•
At the low setting, normal system operations take priority over a rebuild.
•
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.
Syntax:
<target> modify rp=high|medium|low|? where <target> is a controller.
Example command:
=> ctrl slot=3 modify rp=high
Changing the Expand Priority setting
The Expand Priority setting determines the urgency with which the controller treats an internal command to expand an array.
HP Array Configuration Utility 70
•
At the low setting level, normal system operations take priority over an array expansion.
•
At the medium setting, expansion occurs for half of the time, and normal system operations occur for the rest of the time.
•
At the high setting, the expansion takes precedence over all other system operations.
Syntax:
<target> modify ep=high|medium|low|? where <target> is a controller.
Example command:
=> ctrl slot=3 modify ep=high
Setting the surface scan mode
The surfacescanmode keyword sets the surface mode for the controller. The available modes are disable, high, or idle. If you specify the idle mode, you must also specify a surface scan delay value.
Syntax:
<target> modify [ surfacescanmode=disable | idle | high | ? ]
Example commands: controller slot=1 modify surfacescanmode=high controller slot=1 modify surfacescanmode=disable controller slot=1 modify surfacescanmode=idle surfacescandelay=3
Changing the surface scan delay time
The setting for the surface scan delay determines the time interval for which a controller must be inactive before a surface scan analysis is started on the physical drives that are connected to it.
Surface scan analysis is an automatic background process that ensures that you can recover data if a drive failure occurs. The scanning process checks physical drives in fault-tolerant logical drives for bad sectors, and in RAID 5 or RAID 6 (ADG) configurations, it also verifies the consistency of parity data.
Syntax:
<target> modify ssd=# where <target> 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. This process preserves the structure of the logical drive and merely deletes data, whereas a delete command applied to a logical drive deletes the logical drive structure as well as the data.
Syntax:
<target> modify reenable [forced]
Example command:
=> ctrl slot=3 ld 1 modify reenable forced
HP Array Configuration Utility 71
Changing the controller cache ratio
The controller cache ratio setting determines the amount of memory allocated to read and write operations.
Different types of applications have different optimum settings. You can change the ratio only if the controller has a battery-backed cache (because only battery-backed cache can be used for write cache) and if there are logical drives configured on the controller.
Syntax:
<target> modify cr=#/#|? where <target> is a controller, and #/# is the cache ratio in the format read percentage/write percentage.
Example command:
=> ctrl slot=3 modify cr=25/75
Enabling or disabling the drive cache
On controllers and drives that support physical drive write cache, you can use this command to enable or disable the write cache for all drives on the controller.
CAUTION: Because physical drive write cache is not battery-backed, you could lose data if a power failure occurs during a write process. To minimize this possibility, use a backup power supply.
Syntax:
<target> modify drivewritecache=enable|disable|? [forced] where <target> is a controller that supports drive write cache.
Example command:
=> ctrl slot=5 modify dwc=enable
Enabling or disabling the array accelerator
If the controller has an array accelerator, you can disable or enable it for specified logical drives.
NOTE: Disabling the array accelerator for a logical drive reserves use of the accelerator cache for other logical drives on the array. This feature is useful if you want the other logical drives to have the maximum possible performance (for example, if the logical drives contain database information).
Syntax:
<target> modify aa=enable|disable|? where <target> is a logical drive.
Example command:
=> ctrl slot=3 ld 1 modify aa=enable
Enabling a script to exit on error
When a script encounters an error during execution, the exitonerror keyword enables the script to decide whether to continue or to exit the application and return an exit code.
Syntax: set [exitonerror=enable | disable]
HP Array Configuration Utility 72
Example commands: set exitonerror=enable set eoe=disable show exitonerror
Using ACU scripting
Access ACU with one of the many methods available:
•
Accessing ACU in the offline environment (on page 22 )
•
Accessing ACU in the online environment (on page 27 )
The ACU Scripting application has two scripting modes:
•
Capture mode for capturing a configuration (on page 73 )
ACU inspects the configuration of all internal and external array controllers connected to the server and then writes a script file describing this configuration.
•
Input mode for using an Input script (on page 73 )
ACU reads the array configuration described in a specified script file. See "Creating an ACU script file
(on page 74 )." ACU then applies this configuration to a target system.
Capturing a configuration
To capture the configuration of a system, enter the following command at the system command line prompt: hpacuscripting -c [drive:][path]OUTPUTFILENAME.ext [-internal | -external]
-e [drive:][path]ERRORFILENAME.ext
OUTPUTFILENAME is the name of the capture file, and ext. is the file extension. If you do not specify a name and location for this file, ACU uses the default name ACUOUTPUT.ini, and places the file in the ACU working directory.
The -internal and -external switches limit capture to internal or external controllers.
The -e switch information is used only if ACU must generate an error file. By default, ACU names the error file ERROR.ini and places it in the ACU working directory.
Using an Input script
To use an Input script to configure or reconfigure a system, first locate a suitable ACU script or see "Creating
an ACU script file (on page 74 )."
Then, enter the following command at the system command line prompt: hpacuscripting -i [drive:][path]FILENAME.ext [-internal | -external] [-reset]
-e [drive:][path]ERRORFILENAME.ext
FILENAME is the name of the ACU input file, and ext is the file extension. If you do not specify the name and location of this file, ACU searches for ACUINPUT.ini in the ACU working directory.
The -internal and -external switches limit configuration operations to internal or external controllers.
The -reset flag destroys any existing data and overwrites the current configuration with the configuration specified in the script.
HP Array Configuration Utility 73
The -e switch information is used only if ACU must generate an error file. By default, ACU names the error file ERROR.ini and places it in the ACU working directory.
Creating an ACU script file
To create a valid ACU script file, use one of the following methods:
•
Modify the sample custom input script (on page 74 ).
•
Create a Capture file for capturing a configuration (on page 73 ).
You can create a capture file from any server that has ACU loaded, and then modify the values of options in the file as necessary for the target system. This method is useful for applying a standard configuration to several servers that have similar storage resources.
•
Write an original script.
Each line of text in an ACU script file is in the format option=value and can be written in uppercase or lowercase letters. For information about possible option values and the minimum configuration
information that a valid script must have, see the sample custom input script (on page 74 ).
You can add blank lines and comments to any script to make it easier to read and understand. To create a comment, enter a semicolon, and then enter the comment text. ACU ignores all text on the same line after a semicolon.
Sample custom input script
The sample script in this section gives all possible values for each option.
•
If an option is shown in bold type, you must enter a value for that option when writing your own script.
•
If a value is shown in bold type, ACU uses that value as a default setting when creating new logical drives.
You can use this script as a template for your own script.
Action = Configure|Reconfigure
Method = Custom|Auto ; COMMENT: ACU cannot create a RAID 50 or RAID 60 configuration in Auto mode. You must create such configurations manually using the Custom setting.
Controller = All | First | Slot [N][:N] | WWN [N] | SerialNumber [N] | IOCabinet
[N],IOBay [N],IOChassis [N],Slot [N],Cabinet [N],Cell [N]
ClearConfigurationWithDataLoss = Yes|No ; COMMENT: This option is now deprecated.
LicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
DeleteLicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX | * ; COMMENT: * is a wild card that enables you to delete all license keys on the specified controller.
RAIDArrayID = “XXXXXXXXXXXXXXXXXXXX”
ReadCache = 0|10|20|25|30|40|50|60|70|75|80|90|100
WriteCache = 0|10|20|25|30|40|50|60|70|75|80|90|100
RebuildPriority = Low|Medium|High
ExpandPriority = Low|Medium|High
SurfaceScanDelay = N
HP Array Configuration Utility 74
PreferredPathMode = Auto|Manual
; COMMENT: the following five entries are used to optimize the controller performance for video
MNPDelay = 0|1|2|...|60 ; units are minutes, zero indicates disabled
IRPEnable = Yes|No
DPOEnable = Yes|No
ElevatorSortEnable = Yes|No
QueueDepth = 2|4|8|16|32|Auto
Array = A|B|C|D|E|F|G|...Z|a|b|c|d|e|f
OnlineSpare = None | N | Port:ID,Port:ID... | Box:Bay,Box:Bay... |
Port:Box:Bay,Port:Box:Bay,... ; COMMENT: These values are available only in
Custom method mode. In Auto method mode, the choices are Yes|No.
Drive = * | N | Port:ID,Port:ID... | Box:Bay,Box:Bay... |
Port:Box:Bay,Port:Box:Bay,...
DriveType = SCSI | SAS | SATA
LogicalDrive = 1|2|3|...32
RAID = 0|1|5|50|6|60|adg|auto ; COMMENT: RAID 6 and 60 are only available when
SAAP is installed and the license key registered
ParityGroups = 2|N ; COMMENT: Necessary only for RAID 50 or 60. N > 2
Size = [N]|Max
Sectors = 32|63
StripeSize = 8|16|32|64|128|256
ArrayAccelerator = Enable|Disable
PreferredPath = 1|2
HBA_WW_ID = WWN
ConnectionName = UserDefinedName
HostMode = Default | Windows | Windows(degrade | openVMS | Tru64 | Linux |
Solaris | Netware | HP | Windows Sp2 ; COMMENT: The Windows(degrade value must be entered as written.
Script file options
Options in ACU script files are divided into the following categories:
•
Control category (on page 77 )
•
Controller category (on page 77 )
•
•
Logical Drive category (on page 83 )
HP Array Configuration Utility 75
•
Each category has several scripting options, but you do not always need to assign values to every option.
ACU can use default values in some instances, while in other instances, a listed option might not be relevant for a particular configuration or scripting mode.
The options for each category are listed in the following table and described in more detail in the remainder of this section.
Category Options Description
Control
Controller
Array
Action
Method
Controller
CacheState
ClearConfigurationWithDataLoss
DeleteLicenseKey
DPOEnable
DriveWriteCache
ElevatorSortEnable
ExpandPriority
IRPEnable
LicenseKey
MNPDelay
NoBatteryWriteCache
PreferredPathMode
QueueDepth
RaidArrayId
ReadCache
RebuildPriority
SurfaceScanDelay
SurfaceScanDelayExtended
SurfaceScanMode
WriteCache
Array
Drive
DriveType
Join
OnlineSpare
Split
Logical Drive ArrayAccelerator
LogicalDrive
NumberOfParityGroups
PreferredPath
RAID
Renumber
Repeat
ResourceVolumeOwner
Sectors
ShrinkSize
Size
SizeBlocks
StripSize
StripeSize
These options define the overall behavior of ACU when it processes scripts and creates configurations. Control options can occur only once in a script file and must be listed first.
Options in this category specify the controller that is to be configured (or the controller that had its configuration captured). Although the Controller option must begin this section of the script, you can script other options in this category in any order.
You can use one script file to configure all controllers in a system, and you can configure the controllers identically or individually. If you define each controller configuration individually, enter the option values for one controller and its arrays and logical drives before specifying the option values for another controller.
These options describe an array that is to be configured on the controller that was previously specified in the script. (If no controller was previously specified, ACU stops processing the script and creates an error file.)
Although the Array option must begin this section of the script, you can script the other options in this category in any order.
These options describe a logical drive that is to be configured on an array that was previously specified in the script. (If no array was previously specified, ACU stops processing the script and creates an error file.)
Although the LogicalDrive option must begin this section of the script, you can script the other options in this category in any order.
HP Array Configuration Utility 76
Category Options
HBA
ConnectionName
HBA_WW_ID
HostMode
Description
These options specify an HBA that is to be configured.
Control category
The Control category has the following options:
•
•
Action mode
You must specify an Action mode:
•
In Configure mode, you can create new arrays, but you cannot modify existing arrays. The controller must be connected to unassigned physical drives for this mode to be available.
•
In Reconfigure mode, you can modify existing arrays. For example, you can set up an array expansion, a logical drive extension, or a migration. These procedures do not destroy data, unless you specifically want the data to be deleted. In this mode, ACU does not change an existing option setting unless you specifically script a different value for that option.
If you use the -reset command line switch, the existing controller configuration is cleared with data loss as the first step in the configuration process. This command line switch is not compatible with Reconfigure mode.
Method mode
The default value for this option is Auto. If you want to use Custom mode, you must specify it.
In Auto mode, ACU can perform an expansion, extension, or migration without user intervention if the values that you set for other options imply that such an operation is necessary.
Controller category
The Controller category has the following options:
•
•
•
ClearConfigurationWithDataLoss (on page 78 )
•
DeleteLicenseKey (" LicenseKey, DeleteLicenseKey " on page 79 )
•
DPOEnable (" Video performance options " on page 80 )
•
•
ElevatorSortEnable (" Video performance options " on page 80 )
•
ExpandPriority (" RebuildPriority, ExpandPriority " on page 80 )
•
IRPEnable (" Video performance options " on page 80 )
•
LicenseKey (" LicenseKey, DeleteLicenseKey " on page 79 )
•
MNPDelay (" Video performance options " on page 80 )
HP Array Configuration Utility 77
•
NoBatteryWriteCache (on page 79 )
•
PreferredPathMode (on page 79 )
•
QueueDepth (" Video performance options " on page 80 )
•
•
ReadCache (" ReadCache, WriteCache " on page 79 )
•
RebuildPriority (" RebuildPriority, ExpandPriority " on page 80 )
•
SurfaceScanDelay (on page 80 )
•
SurfaceScanDelayExtended (on page 80 )
•
WriteCache (" ReadCache, WriteCache " on page 79 )
Controller
You must enter a value for this option because it identifies the controller that you want to configure:
•
All—Configure all detected controllers in the system.
•
First—Configure the first controller found, based on the controller with the lowest PCI slot number.
Internal controllers are used before external controllers.
The -internal and -external command line switches influence what ACU regards as the First controller. For example, if you use the -external switch, the First controller is the first external controller discovered, regardless of the number of internal controllers in the host system.
•
Slot [N][:M]—Configure the internal controller in slot number N, or the external controller at port
M in slot 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.
•
IOCabinet[N],IOBay[N],IOChassis[N],Slot[N],Cabinet[N],Cell[N]—Configure the controller in the Integrity server that has the slot path information defined by this sequence of identifiers.
CacheState
This option enables you to flush the cache or disable flushing of the cache. Values are FlushEnable and
FlushDisable.
You can use this option to prevent stale cache issues.
ClearConfigurationWithDataLoss
Clearing the configuration causes data loss because it deletes all logical volumes and arrays on the controller. If you clear a configuration, you can write commands later in the script file to create a new configuration from the liberated drive capacity.
The values for this option are Yes or No. The default value is No.
DriveWriteCache
This option controls the settings of the write cache for all connected physical disks. For this option, the setting is Enable or Disable. Not all physical disks or controllers support this option.
HP Array Configuration Utility 78
LicenseKey, DeleteLicenseKey
These options enable you to enter a 25-character license key to activate or uninstall some controller features.
Hyphens can be entered, but are not required.
NoBatteryWriteCache
With this option, the controller can enable write cache when no battery is present or when the battery fails.
Values are Enable or Disable. The default is Disable.
Some controllers do not support this option.
PreferredPathMode
The setting that you select for this option determines how the preferred I/O path to a particular logical drive is set for a redundant array controller that is in an active/active configuration.
Not all controllers support this feature, and controllers in an active/standby configuration disregard this option.
•
Auto is the default setting for new configurations. In this case, the storage system automatically selects the I/O path from the redundant controller to the logical drive and dynamically load balances all paths.
•
Manual enables you to assign the logical drive to a specific redundant controller. If you select this
setting, use the PreferredPath (on page 84 ) command to specify the path.
If you are reconfiguring a controller and do not specify a setting for this option, the existing setting remains unchanged.
RaidArrayId
This option specifies the RaidArrayId for controllers that support this feature, such as fibre and shared storage controllers. The RaidArrayId is a user-defined string that identifies controllers.
"XXXXXXXXXXXXXXXXXXXX"
The value can be a string of varying length that consists of any of the following characters: a-z A-Z 0-9 ! @ # * ( ) , - _ + : . / [space]
This string cannot end in a space character.
This string has a maximum length that varies depending on the type of controller. For RA4x00 controllers, the maximum length is 24 characters. For other controllers, the maximum length is 20 characters.
The quotes enclosing the string are optional. The quotes allow you to use leading space characters in the
RaidArrayId.
ReadCache, WriteCache
Enter a number between 0 and 100 to specify the percentage of cache that is to be allocated to drive reads or writes. The default value for both options is 50, depending on the controller and the battery status.
The allowable cache ratios depend on the controller model and whether it has battery-backed write cache, as described in the following table.
A "+" indicates that the specified cache ratio is allowed for that type of controller, while a "–" indicates that the ratio is not allowed.
HP Array Configuration Utility 79
RebuildPriority, ExpandPriority
These options establish the priority for rebuild and expand functions. Each option has three possible values:
Low, Medium, and High.
These options are not required.
SurfaceScanDelay
Enter a number between 0 and 30 to specify the duration of the surface scan delay in seconds. This option is not required. If you do not specify a value for this option, the delay remains unchanged. A value of 0 disables the scan.
SurfaceScanDelayExtended
Enter a number between 0 and 300 to specify the duration of the surface scan delay in tenths of seconds. This option is not required. If you do not specify a value for this option, the delay remains unchanged. A value of
0 disables the scan.
If this parameter and SurfaceScanDelay are both in the input file, this parameter takes precedence.
SurfaceScanMode
This parameter specifies the Surface Scan Mode with the following values:
•
Idle—The delay interval is set with the normal values from SurfaceScanDelay or
SurfaceScanDelayExtended.
•
High—The surface scan enters a mode guaranteed to make progress despite the level of controller I/O.
•
Disabled—No mode is selected.
Video performance options
Video performance options require SAAP (" About SAAP " on page 8 ).
To optimize the controller performance for video, set values for the following options as indicated:
DPOEnable = No
ElevatorSortEnable = Yes
IRPEnable = No
In addition:
•
Set the MNPDelay to any integer value from 1 to 60 (units are minutes). If you want to disable this option, set a value of zero instead.
•
Set the QueueDepth to one of the following values:
2|4|8|16|32|Automatic
Array category
The Array category has the following options:
•
•
•
HP Array Configuration Utility 80
•
•
•
Array
Enter a letter or pair of letters to identify the array that is to be created or reconfigured, and observe these additional limitations:
•
In Configure mode, ACU creates a new array. The value that you specify for the array option must be the next available letter or pair of letters in the sequence, according to the number of existing arrays on the controller. AA follows Z, and BA follows AZ.
•
In Reconfigure mode, ACU can either create a new array or reconfigure an existing array. In this case, the value that you specify can identify an existing array, or it can correspond to the next available array letter or pair of letters in the existing configuration.
Drive
You can use this option in the input file to specify new physical drives for the array. Use this option to build a new array or to expand, shrink, or move an existing array.
Observe the following guidelines:
•
If you are expanding an array, each drive that you add must have a capacity no less than that of the smallest drive already in the array. The added drives and the existing drives in the array must all be the same type (for example, SAS or SATA).
•
If you are moving or shrinking an array, ACU Scripting compares the current drives with the requested drives, and then determines whether you are moving or shrinking. Shrinking or moving an array is supported only in Custom method mode.
•
If the value of the ClearConfigurationWithDataLoss (on page 78 ) option is Yes, you can use
the Drive option to remove drives from an array.
Determine which mode to use:
•
Auto method mode—ACU configures all the available drives on the controller into one array. If the drives are of different capacities, ACU determines the capacity of the smallest drive and uses the same amount of space on all other available drives.
•
Custom method mode—To specify the drives to be used in the array (different arrays on the same controller can use different methods), choose one of the following methods: o
To specify individual drives, use the applicable convention (port:ID, box:bay, or port:box:bay). o o
To specify only the number of drives to use (not which specific drive IDs to use), enter that number as the value for this option. For example, if you enter drive=3, ACU uses the first three available drives to build or expand the array that you define in the remainder of the script. ACU automatically determines which drives are suitable to use.
To use all available drives, enter an asterisk as the value for this option. An array that is configured using this method cannot have a spare.
DriveType
This option specifies the interface type for drives that ACU must use to build the array.
HP Array Configuration Utility 81
Choose one of the valid drive types:
[SCSI | SAS | SATA | SATASSD | SASSSD]
The value is often used with the wildcard (*) or number argument for Drive.
Join
To use the Join command, observe the following requirements:
•
The system must be offline.
•
The -offline command line flag must be set when you start ACU Scripting.
The command fails if the OS reports that any of the volumes involved in the join are in use.
CAUTION: Executing the Join command on an online system can result in kernel panics, blue screens, and/or data loss.
The Split command converts a RAID 1 or RAID 10 logical volume into two RAID 0 logical volumes. The
Join option reverses the splitting process by recombining the two RAID 0 volumes into a single RAID 1 or
RAID 10 volume, depending on the number of physical disks.
For this process, ID is the ID of the resulting volume that was joined. All data on the other volume is lost.
Array = C
Join = A
After the command executes, Array C is removed, and its physical drives are now a mirror of the drives in
Array A. The original contents of Array C are lost.
OnlineSpare
The value for this option determines whether the array specified previously in the script will be configured with spare drives.
The interface type for drives and spare drives must match, for example, all SAS or all SATA.
Method mode
Custom
Auto
Possible values
To specify exactly which drives to use as spares, use the applicable convention (port:ID, box:bay, or port:box:bay).
To specify only the number of spares (not the exact IDs), enter that number as the value for this option. ACU automatically selects only those drives that are suitable for the array.
To specify that the array should not have spares, enter None.
Yes (indicating one spare)
No
Default value
In Configure action mode: None
In Reconfigure action mode, ACU ignores any value entered for this option and keeps any spares that are already present in the configuration.
In Configure action mode: Yes
(indicating one spare)
In Reconfigure action mode, ACU ignores any value entered for this option and keeps any spares that are already present in the configuration.
Split
This command splits RAID 1 or RAID 10 volumes into individual RAID 0 volumes.
Two values are available:
HP Array Configuration Utility 82
HIDDEN—The driver hides the new logical volume from the OS.
VISIBLE—The new logical volume is visible immediately to the OS.
Logical Drive category
The Logical Drive category has the following options:
•
ArrayAccelerator (on page 83 )
•
•
NumberOfParityGroups (on page 83 )
•
•
•
•
•
ResourceVolumeOwner (on page 85 )
•
•
•
•
•
•
ArrayAccelerator
This option specifies whether the array accelerator is enabled or disabled for the specified logical drive. The default value is Enabled.
LogicalDrive
The value that you enter for this option specifies the ID number of the logical drive that is to be created or modified. The first logical drive on an array must have an ID of 1 (not 0), and logical drive numbering must be contiguous.
•
In Configure action mode, ACU accepts only the ID number of the next possible logical drive.
•
In Reconfigure action mode, ACU also accepts the ID number of any existing logical drive.
NumberOfParityGroups
When you create a RAID 50 or RAID 60 configuration, you must also set the number of parity groups.
You can use any integer value greater than 1 for this setting, with the restriction that the total number of physical drives in the array must be exactly divisible by the number of parity groups.
The maximum number of parity groups possible for a particular number of physical drives is the total number of drives divided by the minimum number of drives necessary for that RAID level (three for RAID 50, four for
RAID 60).
HP Array Configuration Utility 83
PreferredPath
If you select the Manual setting for PreferredPathMode (on page 79 ), use the PreferredPath
command to specify the path for I/O to the logical drive on a redundant controller in active/active mode.
The default setting for this option is 1. With this setting, the controller in chassis slot 1 is the preferred controller for I/O to the logical drive. If you select 2, the controller in chassis slot 2 becomes the preferred controller for the logical drive.
To determine the chassis slot numbers, use the show command on a controller that supports redundant controllers.
RAID
The value that you enter for this option specifies the RAID level of the logical drive.
•
When the Action mode is Configure, and the Method mode is Auto, ACU automatically selects the highest RAID level that the controller and drive configuration can support except RAID 50 or RAID 60.
To specify RAID 50 or 60 for a controller that supports either of these RAID levels, use the Custom
•
When the Action mode is Reconfigure, the default value is the existing RAID level for that logical drive.
If you specify a different RAID setting, then ACU either ignores the new setting (when Method mode is
Auto), or attempts to migrate the logical drive to the specified RAID level (when Method mode is
Custom).
ACU supports the following values for RAID levels:
•
60—RAID 60
•
50—RAID 50
•
ADG—RAID ADG is the equivalent of RAID 6
•
6—RAID 6
•
5—RAID 5
•
4—RAID 4
•
10ADM—RAID 1 with 3-way mirroring
•
10—RAID 10 (mirroring with 2 disks)
•
1ADM—RAID 1 with 3-way mirroring
•
1—RAID 1 (mirroring with 2 disks)
•
0—RAID 0
Some RAID levels require SAAP (" About SAAP " on page 8 ).
Renumber
This option renumbers the logical drive to N.
Typically used after a Join command, this option ensures the proper logical volume numbering is set, for example, the boot volume is ID 1.
HP Array Configuration Utility 84
Do not mix Renumber and Join operations in the same script, because ACU Scripting does not update its internal state after a renumber. If other commands are mixed with Renumber, commands targeting specific volumes might target the incorrect volume.
Repeat
The value you enter for this option specifies the number of times that ACU is to repeat this logical drive configuration.
Use one of the following values:
•
N—In Configure mode, ACU creates N new logical drives.
•
MAX—ACU creates the maximum number of logical drives possible. The number of drives created depends on the number of existing drives and the maximum number of logical drives supported by the controller.
You must specify the logical drive ID as Next. This Size option controls the size of each logical drive, or if the size is set to MAX, the size of the volumes is set to consume all available space on the array.
ResourceVolumeOwner
This option specifies that an existing logical drive (N) should be a snapshot resource volume. The option also specifies the owner logical drive ID. If you do not specify this command on some older model controllers, the logical drive remains a normal data volume.
Sectors
This option specifies the number of sectors that are to comprise each track. Enter 32 to disable MaxBoot or
63 to enable it.
•
For new logical drives, the default setting is 63 if the logical drive is larger than 502 GB. Otherwise, the default setting is 32.
•
For an existing logical drive, the default setting is the existing setting.
Logical drive performance is likely to decrease with MaxBoot enabled.
ShrinkSize
In Reconfigure mode, this option specifies the resulting size of the logical drive (in MB) to be reduced.
ShrinkSize is not valid in Configure mode.
Size
This parameter specifies the size of the logical drive.
Use the following values to set the size:
•
N—The size in MB
•
MAX—Uses all available unused space in the array for the logical drive. This value is the default.
•
MAXMBR—Creates the largest size of volume supportable by a 32-bit MBR (2TiB)
In Reconfigure mode, the default setting is the existing size of the logical drive. If you enter a larger value,
ACU extends the logical drive to the new size if there is unused drive capacity on the same array, as long as the operating system supports logical drive extension. You cannot reduce the size of the logical drive.
HP Array Configuration Utility 85
CAUTION: Back up all data before extending a logical drive.
SizeBlocks
This option specifies the size of the logical drive in 512-byte blocks. Use this option to set an exact size without rounding.
When ACU Scripting captures a configuration, it reports volume sizes rounded down to the nearest MB.
When the capture is played back, the size is reduced to fit within the already rounded MB size. This option prevents the loss of volume size over successive generations of captures.
However, if the size does not fit the geometry of the array, caused by different disks or RAID levels, the size will be rounded down to fit the geometry.
StripeSize
Beginning with ACU, ACU CLI, and ACU Scripting v8.55, the term stripe size has been replaced by strip size. This labeling change does not affect functionality.
When distributing data across multiple physical drives (striping), the strip size is the amount of data that is written to each physical drive. The full stripe size refers to the combined size of all the strips across all physical drives, excluding parity-only drives.
For more information, see the option for StripSize (on page 86 ).
StripSize
Beginning with ACU, ACU CLI, and ACU Scripting v8.55, the StripSize option replaces the
StripeSize option. When distributing data across multiple physical drives (striping), the strip size is the amount of data that is written to each physical drive. The full stripe size refers to the combined size of all the strips across all physical drives, excluding parity-only drives.
You can enter a numerical value for this option to specify the size of the data strips (in kilobytes), or you can leave this option blank and allow ACU to use a default value.
Strip sizes available for a RAID level vary based on the controller and the controller firmware level. The maximum strip size changes dynamically and is reduced for arrays with a large number of data drives or with smaller controller cache sizes. (The controller must be able to read an entire stripe of data at a time into cache memory during transformation. Available memory is the limiting factor.
The following strip sizes are available:
•
8—8 KB
•
16—16 KB
•
32—32 KB
•
64—64 KB
•
128—128 KB
•
256—256 KB
•
512—512 KB
•
1024—1024 KB (supported starting with Gen8 controllers)
HP Array Configuration Utility 86
The default strip size value depends on the action mode:
•
In Configure action mode, the default value is determined by the RAID level that you specified earlier in the script.
•
In Reconfigure action mode, the default value for this option is the strip size that is already configured for the logical drive. If you enter a value that is different from the existing strip size, ACU attempts to migrate the logical drive to the strip size that you specify. (If you intend to migrate the logical drive, back up all data before starting the migration procedure.)
HBA category
The HBA category has the following options:
•
•
•
ConnectionName
This option is a user-defined string used as the connection name for the specified HBA.
The string can consist of:
•
A maximum of 16 characters
•
Embedded space characters but cannot end with a space character
•
Any of the following characters: a–z, A–Z, 0–9, !, @, #, *, (, ), -, _, +, :, ., /, and [space]
HBA_WW_ID
This option specifies which HBA, based on its assigned WWN, is modified by the configuration changes.
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.
The following operating system options might be available:
•
Default
•
Microsoft® Windows®
•
OpenVMS
•
Tru64
•
Linux
•
Solaris
•
Netware
•
HP-UX
HP Array Configuration Utility 87
XML support
ACU scripting v8.30 and later support an XML file format for input and output.
XML output
To create an XML output document, use an XML suffix with the output file name:
C:\hpacuscripting -c out.xml
The following text is an example XML output file.
<?xml version="1.0"?>
<Config.document>
<!-- Date captured: Tue Jun 09 10:03:08 2009 -->
<!-- Version: 8:30:4 -->
<Action>Configure</Action>
<Method>Custom</Method>
<Controller ID="Slot 1">
<!-- Controller HP Smart Array P410, Firmware Version 1.99 -->
<ReadCache>25</ReadCache>
<WriteCache>75</WriteCache>
<RebuildPriority>Medium</RebuildPriority>
<ExpandPriority>Medium</ExpandPriority>
<SurfaceScanDelay>3</SurfaceScanDelay>
<DriveWriteCache>Disabled</DriveWriteCache>
<LicenseKey>35DRP-7RH6S-R89GR-4MX6N-8K48X</LicenseKey>
<!-- LicenseKeyType "Flex License" -->
<MNPDelay>60</MNPDelay>
<IRPEnable>Disabled</IRPEnable>
<DPOEnable>Disabled</DPOEnable>
<ElevatorSortEnable>Enabled</ElevatorSortEnable>
<QueueDepth>Automatic</QueueDepth>
<!-- Unassigned Drives 1I:4:5 (60.0 GB), 2I:2:1 (72 GB) -->
<Array ID="A">
<!-- Array Drive Type is Solid State SATA -->
<!-- Free space 0 GBytes -->
<!-- 1I:4:8 (120.0 GB),1I:4:7 (120.0 GB) -->
<Drive>1I:4:8, 1I:4:7</Drive>
<OnlineSpare>No</OnlineSpare>
<LogicalDrive ID="1">
<Raid>1</Raid>
<Size>114439</Size>
<Sectors>32</Sectors>
<StripeSize>128</StripeSize>
<ArrayAccelerator>Enabled</ArrayAccelerator>
</LogicalDrive>
HP Array Configuration Utility 88
</Array>
<Array ID="B">
<!-- Array Drive Type is SAS -->
<!-- Free space 0 GBytes -->
<!-- 1I:4:6 (72 GB),2I:2:4 (72 GB),2I:2:3 (72 GB),2I:2:2 (72 GB)-->
<Drive>1I:4:6, 2I:2:4, 2I:2:3, 2I:2:2</Drive>
<OnlineSpare>No</OnlineSpare>
<LogicalDrive ID="2">
<Raid>5</Raid>
<Size>52478</Size>
<Sectors>32</Sectors>
<StripeSize>64</StripeSize>
<ArrayAccelerator>Enabled</ArrayAccelerator>
</LogicalDrive>
<LogicalDrive ID="3">
<Raid>5</Raid>
<Size>52478</Size>
<Sectors>32</Sectors>
<StripeSize>64</StripeSize>
<ArrayAccelerator>Enabled</ArrayAccelerator>
</LogicalDrive>
<LogicalDrive ID="4">
<Raid>5</Raid>
<Size>52478</Size>
<Sectors>32</Sectors>
<StripeSize>64</StripeSize>
<ArrayAccelerator>Enabled</ArrayAccelerator>
</LogicalDrive>
<LogicalDrive ID="5">
<Raid>5</Raid>
<Size>52478</Size>
<Sectors>32</Sectors>
<StripeSize>64</StripeSize>
<ArrayAccelerator>Enabled</ArrayAccelerator>
</LogicalDrive>
</Array>
</Controller>
</Config.document>
XML input
order as the standard input format.
The following example shows a simple input script in both standard and XML formats.
HP Array Configuration Utility 89
Standard format
Action= Configure
Method= Custom
Controller= Slot 1
Array=A
Drive= 1I:4:8, 1I:4:7
LogicalDrive= 1
RAID= 0
Size= 100000
XML format
<?xml version="1.0"?>
<Config.document>
<Action>Configure</Action>
<Method>Custom</Method>
<Controller ID="Slot 1">
<Array ID="A">
<Drive>1I:4:8, 1I:4:7</Drive>
<LogicalDrive ID="1">
</Controller>
</Config.document>
<Raid>0</Raid>
<Size>100000</Size>
</LogicalDrive>
</Array>
XML input file DTD
The following DTD outlines the parameters for an ACU scripting XML input file.
<!DOCTYPE Config.document [
<!ELEMENT Config.document ( Action, Method, Controller+ ) >
<!ELEMENT Action ( Configure | Reconfigure ) >
<!ELEMENT Method ( Auto | Custom ) >
<!ELEMENT Controller, Array ) ChassisName? |
ClearConfigurationWithDataLoss | DPOEnable? | DriveWriteCache? |
ElevatorSortEnable? | ExpandPriority? | IRPEnable? | Initiator? |
LicenseKey? | MNPDelay? | PreferredPathMode? | QueueDepth? | ReadCache? |
RebuildPriority? | SurfaceScanDelay? | WriteCache? ) >
<!ATTLIST Controller ID PCDATA #REQUIRED >
<!ELEMENT ClearConfigurationWithDataLoss ( YES | NO ) NO >
<!ELEMENT DPOEnable ( YES | NO ) >
<!ELEMENT DriveWriteCache ( ENABLE | DISABLE ) >
<!ELEMENT ElevatorSortEnable ( YES | NO ) >
<!ELEMENT ExpandPriority ( HIGH | MEDIUM | LOW ) >
<!ELEMENT IRPEnable ( YES | NO ) >
<!ELEMENT LicenseKey ( #PCDATA ) >
<!ELEMENT MNPDelay ( #PCDATA ) >
<!ELEMENT PreferredPathMode ( AUTO | MANUAL ) >
<!ELEMENT ReadCache ( 0 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100
) >
<!ELEMENT RebuildPriority ( HIGH | MEDIUM | LOW ) >
<!ELEMENT SurfaceScanDelay ( #PCDATA ) >
<!ELEMENT QueueDepth ( #PCDATA ) >
<!ELEMENT WriteCache ( 0 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 |
100 ) >
<!ELEMENT Array, LogicalDrive+ ( Drive, OnlineSpare ) >
<!ATTLIST Array ID PCDATA #REQUIRED >
HP Array Configuration Utility 90
<!ELEMENT Drive ( ALL | #PCDATA ) >
<!ELEMENT OnlineSpare ( YES | NO | #PCDATA ) >
<!ELEMENT LogicalDrive ( Raid, Repeat | Size, Sectors, StripeSize,
ArrayAccelerator? ) >
<!ATTLIST LogicalDrive ID PCDATA #REQUIRED >
<!ELEMENT ArrayAccelerator ( ENABLE | DISABLE ) ENABLE >
<!ELEMENT Raid (0 | 1 | 1ADM | 10 | 10ADM | 4 | 5 | 6 | ADG | 50 | 60)
>
<!ELEMENT Repeat ( MAX | #PCDATA ) >
<!ELEMENT Sectors ( 32 | 63 ) >
<!ELEMENT Size ( MAX | #PCDATA ) MAX >
<!ELEMENT StripeSize ( 8 | 16 | 32 | 64 | 128 | 256 | 512 ) >
<!ELEMENT Initiator ( HBA_WW_ID, ConnectionName?, HostMode? ) >
<!ELEMENT HBA_WW_ID ( #PCDATA ) >
<!ELEMENT ConnectionName ( #PCDATA ) >
]>
<!ELEMENT HostMode ( #PCDATA ) >
ACU scripting warning messages
Warning code
Warning message
4000
License key is already installed
4001
4002
4003
4004
4005
4006
Comment or clarification
Clear configuration command failed - configuration is already cleared
Chassis name is already set to this value
The input file specified a license key. However, a license key is already installed on the controller.
The -reset option was used on a controller that does not have a configuration.
The chassis name is already set to the supplied value. The command is ignored.
Certain commands require that the controller be configured before they can be sent to the controller.
One or more controller commands were skipped because the controller is not configured
Using Repeat function
The system must be rebooted for the firmware flash to complete
Unable to set the array accelerator for this volume. The cache board may be missing or have a bad status, or the controller may not support a cache
Some commands have been ignored because the
Repeat parameter has been specified in the input file.
A controller has been flashed with new firmware.
The new firmware requires a reboot to take effect.
The controller may not support a cache (for example, some Software RAID controllers) or the cache may be missing or defective.
ACU scripting error messages
Error code Error message
0
—
Comment or clarification
No error exists. The program completed
HP Array Configuration Utility 91
Error code Error message
2053
2056
2059
2064
2817
2818
2819
2821
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
Too many coinciding expansion, migration, or extension operations
Controller does not support license keys
Invalid license key
Controller does not support SSP
Invalid Action
Invalid Method
Invalid Controller
No controllers detected
Invalid Rebuild Priority
Invalid Expand Priority
Invalid Array
Array not specified
New Array ID does not match the next available Array ID.
New Array ID already exists
Cannot create Array
Cannot expand Array
Cannot change Array Spare
Invalid physical drive
Invalid Spare
Invalid logical drive
Comment or clarification successfully.
The new configuration requires more transformations than are possible at one time. For example, you cannot expand a logical volume and transform its RAID level at the same time.
The controller does not support license key entry or deletion.
The entered license key is not a valid license key.
The controller does not support SSP functions.
The requested actions are invalid, for example, combining -reset with capture mode.
The method must be either Custom or Auto.
An invalid controller value was specified.
No controllers were detected. This error applies to
Input mode only.
The specified rebuild priority is not supported.
The specified expand priority is not supported. This error also occurs if the controller does not allow expansion, and therefore does not support expand priority.
The array ID is invalid.
The Array command is missing from the script file.
Some commands were found that require an Array to be specified.
The array ID in the script file does not match the array ID of the next available array. For example, if the configuration has an Array A and the input file specifies Array C (without Array B), then the script generates this error.
The array ID specified in the script file (in Configure mode) already exists in the configuration. Configure mode can only create new arrays.
The controller will not allow a new array to be created, either because the controller has no unassigned physical drives attached or because the maximum number of arrays or logical drives has been reached already.
The Array could not be expanded, either because the controller does not support expansion, or the current configuration does not allow expansion to occur on the array.
The spare state of the array could not be changed.
This error can occur when you attempt to add or drop a spare and the current configuration does not allow a spare state change for the array.
A specified physical drive is not a valid physical drive, or it cannot be placed in the array.
A specified spare is not a valid spare drive, or it cannot be placed in the array as a spare.
The logical drive ID is not valid.
HP Array Configuration Utility 92
Error code Error message
2836
2837
2838
2839
2841
2842
2843
2844
2849
2850
2851
2852
2853
2854
2857
2861
Comment or clarification
New Logical Drive ID does not match the next available logical drive ID.
If you are attempting to replicate a configuration that has non-consecutive logical drive numbers, then you must change the script file so that the logical drive numbers are consecutive.
New Logical Drive ID already exists
Cannot create Logical Drive
Cannot migrate Logical Drive RAID
The script file specifies a logical drive ID that is not the first unused ID in the sequence. For example, this message appears if the controller has only Logical
Drive 1 and the script file specifies creation of
Logical Drive 3 (omitting Logical Drive 2). A common cause of this error is that the input file specifies nonsequential logical drive numbers. In this case, change the logical drive numbers in the input file so that they are sequential.
This error occurs in Configure mode when the logical drive ID specified in the script file already exists in the configuration. In Configure mode, you can create new logical drives only.
The array has no free space, or the maximum number of logical drives has been reached already.
The controller does not support RAID migration, or migration is not possible with the current controller configuration.
Cannot extend Logical Drive
Invalid RAID
Invalid Size
The controller does not support extension, or the current controller configuration cannot be extended.
For example, extension is not possible if the array has no free space.
The specified RAID level is invalid or is not possible with the current physical disk and array configuration.
The specified size is invalid or is not possible with the current configuration.
Invalid Stripe Size
Invalid ClearConfigurationWithDataLoss parameter
The valid parameters are Yes and No (default).
Controller does not support Chassis Name The controller does not support setting a chassis name.
Invalid Chassis Name
Invalid SSP State
The entered chassis name is invalid. Use characters from the set a–z, A–Z, 0–9, !, @, #, *, (, ), ,, -, _, +,
:, ., /, and [space]. The name cannot end with a space character or exceed the maximum number of characters allowed by the controller.
The requested SSP state is not a valid SSP state.
Cannot change SSP settings
The specified stripe size is invalid, not supported by the current RAID level, or not possible with the current configuration.
Invalid SSP Adapter ID
The SSP settings cannot be changed for the controller or logical drive.
The adapter ID is not a valid adapter ID that was detected by the controller.
Invalid Surface Scan Delay
Controller does not support redundancy settings
—
The controller is not redundant or does not support redundancy settings.
2864
2865
Invalid Preferred Path Mode
Invalid Preferred Path
The specified value for the preferred path mode is not valid, or the controller is not available.
The specified preferred path is not a valid chassis
HP Array Configuration Utility 93
3002
3003
3004
3005
3006
3007
3008
Error code Error message
2866
2867
2868
2877
2880
2882
3000
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
Failure opening capture file <text>
Failure opening input file <text>
Failure opening error file <text>
There are no suitable spares available
Invalid Physical Disk Type Specified
Invalid MNP delay
Invalid Option
Comment or clarification slot for an available, active controller, or the controller is not available.
—
—
—
ACU found no drives that could be used as spares for the specified array.
—
The specified value for MNP delay is invalid.
The value of the option supplied to this parameter is invalid.
The controller returned an error for a command.
ACU is unable to delete the license key.
Command Failed
License Key Delete Failed
Invalid Sector Size
Cannot delete Array
Invalid Number of Parity Groups
Chassis name is too long
Chassis name is already in use
—
—
—
—
Another controller is already using the entered chassis name.
Auto Configure failed The Auto Configure mode was unable to complete auto configuration.
Cannot extend logical drive, not enough free space for the requested size
Cannot extend logical drive, requested size is too small
—
—
Cannot specify both SIZE and SHRINKSIZE The input file cannot specify both a SIZE and
SHRINKSIZE parameter.
Cannot shrink Array
Cannot move Array
Invalid operation - Advanced Pack support required
The array shrink operation was not successful.
The array move operation was not successful.
The requested operation requires a valid license key to be entered.
Spare drives cannot be specified by a count in Reconfigure mode
Disk drives cannot be specified by a count in
Reconfigure mode
Invalid number of physical disks
When in Reconfigure mode, the requested spare drives must be specified by their addresses. A simple count cannot be used.
When in Reconfigure mode, the requested data drives must be specified by their addresses. A simple count cannot be used.
—
Cannot create Array - no physical disks specified
ACU cannot create an array unless physical disks are specified in the input file DRIVE parameter.
SSP must be enabled in order to perform this operation
Invalid connection name
For the specified operation, ACU requires SSP to be supported and enabled.
—
HP Array Configuration Utility 94
Error code Error message
3022
3023
The connectionname cannot be removed when the hostmode has a non-default value.
Invalid Host Mode
3024
Invalid Adapter ID
Comment or clarification
—
—
—
3025
This controller does not have host mode modification capability
—
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
You need to have administrator rights to continue.
Another instance of ACU is already running
(possibly a service). Please terminate the
ACU application before running ACU scripting.
Invalid Drive Cache setting. Valid options are ENABLE and DISABLE.
Invalid or out of order Command
Invalid or missing Array for Reconfigure
—
—
—
Verify the ordering of the commands in the input configuration file.
Expecting a valid array in Reconfigure mode
Invalid or missing Filename for Firmware
Update
Firmware Update Failed
This controller has been configured with a more recent version of software. To prevent data loss, configuration changes to this controller are not allowed. Please upgrade to the latest version to be able to continue to configure this controller.
Operations on this Array are temporarily unavailable while the Array is transforming.
Invalid value for NoBatteryWriteCache
Cannot delete Logical Drive
The firmware filename supplied is not a valid filename.
The firmware flash operation on the controller failed.
Some changes to SOULAPI are not backward-compatible. This check prevents the use of an older version of software on a controller configured with a newer version, possibly overriding changes and destroying data.
The user requested too many simultaneous changes.
For example, the user added new disks to an array
(expand array) and changed the size or RAID level of logical volumes on the array. The solution is for the user to wait until the array transformation is complete.
A problem exists with the
NOBATTERYWRITECACHE command. Check the supplied argument. Not all controllers support this operation.
A problem occurred during the attempt to delete the specified logical drive. The drive may be in use by the OS, it may not exist, or it may not be the last logical drive on the array.
HP Array Configuration Utility 95
HP Array Diagnostics and SmartSSD Wear
Gauge Utility
About the utility
Formerly known as the Array Diagnostics Utility, the HP Array Diagnostics and SmartSSD Wear Gauge
Utility collects all possible information about storage devices in the system, detects all problems, and provides a detailed configuration report in .zip format.
After downloading and installing the software, you can run the utility as a GUI or a CLI in an online environment. The functionality in this utility is mirrored in the diagnostics features of the HP Array
Configuration Utility, which can be run in an offline environment.
The utility generates two types of reports:
•
Array diagnostic report
This report contains information about all devices, such as array controllers, storage enclosures, drive cages, as well as logical, physical, and tape drives. For supported solid state drives, this report also contains SmartSSD Wear Gauge information.
•
SmartSSD Wear Gauge report
This report contains information about the current usage level and remaining expected lifetime of solid state drives attached to the system.
For more information, see "Reported information (on page 96 )."
Reported information
The array diagnostic report provides detailed information about devices (array controllers, storage enclosures, drive cages, physical drives, logical drives, and tape drives).
For example, device information on a typical embedded controller might include:
•
Software versions
•
Errors
•
Controller information: o
Name o o o o o
Attached devices
Description
PCI bus
PCI device
PCI function
•
Drive information:
HP Array Diagnostics and SmartSSD Wear Gauge Utility 96
o o o o o o
Interface
WWID
Drive model
Serial number
Firmware revision
Total blocks
The SmartSSD Wear Gauge report contains information on the current usage level of and expected lifetime remaining for solid state drives attached to the system.
For discovered SSDs, the report summary page provides the following calculated totals:
•
Total Solid State Drives with Wearout Status
•
Total Smart Array Solid State Drives
•
Total Non Smart Array Solid State Drives
•
Total Solid State SAS Drives
•
Total Solid State SATA Drives
•
Total Solid State Drives
In addition to these totals, the summary page also displays the following tables:
•
Solid State Drives with Wearout Status
•
Solid State Drives with Less Than an Estimated 56 Days of Life Remaining
•
Solid State Drives with Less Than 2% Usage Remaining
•
Solid State Drives with Less Than 5% Usage Remaining
•
Smart Array Controllers
•
Non Smart Array Controllers
When the generated report is viewed in a browser, the report page displays the following fields in the
SmartSSD Status table.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 97
Field
SSD Wear Status
Power Cycles
Power On Hours
Estimated Life
Remaining Based On
Workload To Date
Usage Remaining
SSD Utilization
Description
Indicates the SSD's wear status with one of the following messages:
•
OK
•
Not Supported
•
The SmartSSD Wear Gauge log is full. Wear
Gauge parameters are not available.
•
SSD has less than 5% usage remaining before wearout.
• SSD has less than 2% usage remaining before wearout.
•
SSD has less than an estimated 56 days before it reaches the maximum usage limit for writes
(wearout) and should be replaced as soon as possible.
•
SSD has less than 5% of usage remaining before wearout. It has less than an estimated 56 days before it reaches the maximum usage limit and should be replaced as soon as possible.
•
SSD has less than 2% of usage remaining before wearout. It has less than an estimated 56 days before it reaches the maximum usage limit and should be replaced as soon as possible.
•
SSD has reached the maximum rated usage limit for writes (wearout) and should be replaced immediately.
Indicates the number of times the SSD has powered on from the powered off state
Indicates the number of hours the SSD has been powered on
Indicates an estimate of the number of days the SSD has before SSD Utilization reaches 100%. This field is not displayed when the SSD Utilization is still at 0%.
Indicates the percentage of the SSD that has not worn out. Usage remaining is equal to the difference of 100 and the SSD Utilization percentage.
Indicates the percentage of the SSD that has worn out
Installing the utility
1.
2.
3.
4.
5.
Browse to the HP Array Configuration Utility website
( http://h18004.www1.hp.com/products/servers/proliantstorage/software-management/acumatrix
/index.html
).
Click Download software.
Select an OS.
Identify the preferred software and version, and then click Download.
Save, and then run, the executable file.
By default, the software installs at C:\Program Files\HP System Tools\.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 98
Setting up ADU Remote Service Mode
You can run ADU as a Windows Service, so that it starts automatically and runs in the background at all times. ACU is accessible remotely from the System Management Homepage ( https://localhost:2381 ).
To set up the service:
1.
2.
Click Start>All Programs>HP System Tools>HP Array Diagnostics and SmartSSD Wear Gauge
Utility>Setup ADU Remote Mode.
Select Enable Remote Service Mode.
3.
Click OK.
Launching the utility in CLI mode
1.
Open a command prompt.
2.
3.
Change directory (cd) to the location where hpaducli.exe is installed.
This directory is commonly C:\Program Files\Compaq\hpadu\bin.
Do one of the following: o o
Generate a diagnostic report with the following command: hpaducli -f adu-report.zip
Generate a SmartSSD Wear Gague report with the following command: hpaducli -ssdrpt -f ssd-report.zip
For more options, use the following command: hpaducli -help
Launching the utility in GUI mode
1.
Click Start>All Programs>HP System Tools>HP Array Diagnostics and SmartSSD Wear Gauge
Utility>HP Array Diagnostics and SmartSSD Wear Gauge Utility.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 99
The splash screen appears.
2.
Select one of the following tasks: o
Viewing the diagnostic report (on page 100 )
o o o
Generating the diagnostic report (on page 102 )
Viewing the SmartSSD Wear Gauge report (on page 103 )
Generating the SmartSSD Wear Gauge report (on page 104 )
For more information about the interface, select Help.
Diagnostic report procedures
Viewing the diagnostic report
1.
2.
Launch the GUI (" Launching the utility in GUI mode " on page 99 ).
Select View Diagnostic Report.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 100
The utility generates and displays the report.
The diagnostic report includes an additional RIS Event Log tab. Smart Array controllers store configuration data in the RAID information sector of all physical drives. The RIS Event Log reads the data and displays the decoded change logs.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 101
3.
Click RIS Event Log.
4.
The log appears.
After reviewing the report, do one of the following: o
Click Save Report, and then save the generated file. o o
Click ADU Home, and then perform additional tasks.
Click Exit ADU.
Generating the diagnostic report
1.
2.
Launch the GUI (" Launching the utility in GUI mode " on page 99 ).
Select Generate Diagnostic Report.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 102
The utility generates the report, and then displays the File Download dialog box.
3.
4.
Open or save the file.
When you are finished with the file, do one of the following: o o o
Click Save Report, and then save the generated file.
Click ADU Home, and then perform additional tasks.
Click Exit ADU.
Identifying and viewing diagnostic report files
The diagnostic report output archive contains the following files:
•
ADUReport.txt—Diagnostic report in text format
•
ADUReport.xml—Diagnostic report in XML format
•
ADUReportViewer.htm—HTML viewer for XML diagnostic report
•
SlotX.txt (SlotX.old)—Controller serial output log
The serial output log file(s) are only available if the HP Smart Array SAS/SATA Event Notification
Service is installed and running.
To view the diagnostic report files in a browser:
1.
2.
Extract ADUReportViewer.htm to a directory.
Open ADUReportViewer.htm in the browser.
SmartSSD Wear Gauge report procedures
Viewing the SmartSSD Wear Gauge report
1.
Launch the GUI (" Launching the utility in GUI mode " on page 99 ).
2.
Select View SmartSSD Wear Gauge Report.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 103
The utility generates and displays the report.
3.
After reviewing the report, do one of the following: o
Click Save Report, and then save the generated file. o o
Click ADU Home, and then perform additional tasks.
Click Exit ADU.
Generating the SmartSSD Wear Gauge report
1.
2.
Launch the GUI (" Launching the utility in GUI mode " on page 99 ).
Select Generate SmartSSD Wear Gauge Report.
The utility generates the report, and then displays the File Download dialog box.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 104
3.
4.
Open or save the file.
After reviewing the report, do one of the following: o o o
Click Save Report, and then save the generated file.
Click ADU Home, and then perform additional tasks.
Click Exit ADU.
Identifying and viewing SmartSSD Wear Gauge report files
The SmartSSD Wear Gauge report output archive contains the following files:
•
SmartSSDWearGaugeReport.txt—SmartSSD wear gauge report in text format
•
SmartSSDWearGaugeReport.json—SmartSSD wear gauge report in JSON format
•
SmartSSDWearGaugeReport.htm—HTML viewer for the JSON wear gauge report
To view the SmartSSD Wear Gauge report files in a browser:
1.
2.
Extract the following files to a directory: o o
SmartSSDWearGaugeReport.json
SmartSSDWearGaugeReport.htm
All files must reside in the same directory.
Open SmartSSDWearGaugeReport.htm in the browser.
HP Array Diagnostics and SmartSSD Wear Gauge Utility 105
Drive arrays and fault-tolerance methods
Drive arrays
The capacity and performance of a single physical (hard) drive is adequate for home users. However, business users demand higher storage capacities, higher data transfer rates, and greater protection against data loss when drives fail.
Connecting extra physical drives (Pn in the figure) to a system increases the total storage capacity but has no effect on the efficiency of read/write (R/W) operations. Data can still be transferred to only one physical drive at a time.
Drive arrays and fault-tolerance methods 106
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.
Because the read/write heads are active simultaneously, the same amount of data is written to each drive during any given time interval. Each unit of data is called a block (denoted by Bn in the figure), and adjacent blocks form a set of data stripes (Sn) across all the physical drives that comprise the logical drive.
For data in the logical drive to be readable, the data block sequence must be the same in every stripe. This sequencing process is performed by the array controller, which sends the data blocks to the drive write heads in the correct order.
A natural consequence of the striping process is that each physical drive in a given logical drive will contain the same amount of data. If one physical drive has a larger capacity than other physical drives in the same logical drive, the extra capacity is wasted because it cannot be used by the logical drive.
Drive arrays and fault-tolerance methods 107
The group of physical drives containing the logical drive is called a drive array, or just array (denoted by An in the figure). Because all the physical drives in an array are commonly configured into just one 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. For arrays that are configured as shown in the previous figure, failure of any physical drive in the array causes every logical drive in the array to suffer irretrievable data loss. To protect against data loss due to physical drive failure, logical drives are configured
with fault tolerance (" Fault-tolerance methods " on page 109 ).
For any configuration except RAID 0, further protection against data loss can be achieved by assigning a drive as an online spare (or hot spare). This drive contains no data and is connected to the same controller as the array. When any other physical drive in the array fails, the controller automatically rebuilds information that was originally on the failed drive to the online spare. The system is thus restored to full
RAID-level data protection, although it now no longer has an online spare. (However, in the unlikely event that another drive in the array fails while data is being rewritten to the spare, the logical drive will still fail.)
When you configure an online spare, it is automatically assigned to all logical drives in the same array.
Additionally, you do not need to assign a separate online spare to each array. Instead, you can configure one hard drive to be the online spare for several arrays if the arrays are all on the same controller.
Effects of a drive failure
When a drive fails, all logical drives that are in the same array are affected. Each logical drive in an array might be using a different fault-tolerance method, so each logical drive can be affected differently.
•
RAID 0 configurations cannot tolerate drive failure. If any physical drive in the array fails, all RAID 0 logical drives in the same array also fail.
•
RAID 1+0 configurations can tolerate multiple drive failures if no failed drives are mirrored to one another.
•
RAID 5 configurations can tolerate one drive failure.
Drive arrays and fault-tolerance methods 108
•
RAID 50 configurations can tolerate one failed drive in each parity group.
•
RAID 6 configurations can tolerate two failed drives at a given time.
•
RAID 60 configurations can tolerate two failed drives in each parity group.
•
RAID 1 (ADM) and RAID 10 (ADM) configurations can tolerate multiple drive failures if no more than two drives, mirrored to one another, fail.
Fault-tolerance methods
Several fault-tolerance methods exist. Those most often used with Smart Array controllers are hardware-based RAID methods.
robust and controlled fault-tolerance environment, so these alternative methods are seldom used.
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.
•
Has the lowest cost per unit of stored data of all RAID methods.
•
All drive capacity is used to store data (none is needed for fault tolerance).
Disadvantages:
•
All data on the logical drive is lost if a physical drive fails.
•
Cannot use an online spare.
•
Can only preserve data by backing it up to external drives.
Drive arrays and fault-tolerance methods 109
RAID 1 and RAID 1+0 (RAID 10)
In RAID 1 and RAID 1+0 (RAID 10) configurations, data is duplicated to a second drive.
When the array contains only two physical drives, the fault-tolerance method is known as RAID 1.
When the array has more than two physical drives, drives are mirrored in pairs, and the fault-tolerance method is known as RAID 1+0 or RAID 10.
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. Several drives in the array can fail without incurring data loss, as long as no two failed drives belong to the same mirrored pair.
This fault-tolerance method is useful when high performance and data protection are more important than the cost of physical drives.
Drive arrays and fault-tolerance methods 110
Advantages:
•
This method has the second highest read performance of any fault-tolerant configuration.
•
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, because many drives are needed for fault tolerance.
•
Only half of the total drive capacity is usable for data storage.
RAID 1 (ADM) and RAID 10 (ADM)
In RAID 1 (ADM) and RAID 10 (ADM) configurations, data is duplicated to two additional drives.
When the array contains only three physical drives, the fault-tolerance method is known as RAID 1 (ADM).
Drive arrays and fault-tolerance methods 111
When the array has more than three physical drives, drives are mirrored in trios, and the fault-tolerance method is known as RAID 10 (ADM).
In each mirrored trio, the physical drives that are not busy answering other requests answer any read requests that are sent to the array. This behavior is called load balancing. If a physical drive fails, the remaining two drives in the mirrored trio can still provide all the necessary data. Several drives in the array can fail without incurring data loss, as long as no three failed drives belong to the same mirrored trio.
This fault-tolerance method is useful when high performance and data protection are more important than the cost of physical drives.
Advantages:
•
This method has the highest read performance of any fault-tolerant configuration.
•
No data is lost when two drives fail, as long as no two failed drives are mirrored to another failed drive.
•
Up to two-thirds of the physical drives in the array can fail.
Disadvantages:
•
This method is expensive, because many drives are needed for fault tolerance.
•
Only one-third of the total drive capacity is usable for data storage.
Drive arrays and fault-tolerance methods 112
RAID 5—distributed data guarding
In a RAID 5 configuration, data protection is provided by parity data (denoted by Px,y in the figure). This parity data is calculated stripe by stripe from the user data that is written to all other blocks within that stripe.
The blocks of parity data are distributed evenly over every physical drive within the logical drive.
When a physical drive fails, data that was on the failed drive can be calculated from the remaining parity data and user data on the other drives in the array. This recovered data is usually written to an online spare in a process called a rebuild.
This configuration is useful when cost, performance, and data availability are equally important.
Advantages:
•
Has high read performance.
•
Data is not lost if one physical drive fails.
•
More drive capacity is usable than with RAID 1+0—parity information requires only the storage space equivalent to one physical drive.
Disadvantages:
•
Has relatively low write performance.
•
Data is lost if a second drive fails before data from the first failed drive is rebuilt.
RAID 6 (ADG)—Advanced Data Guarding
NOTE: Not all controllers support RAID 6 (ADG).
Drive arrays and fault-tolerance methods 113
RAID 6 (ADG), like RAID 5, generates and stores parity information to protect against data loss caused by drive failure. With RAID 6 (ADG), however, two different sets of parity data are used (denoted by Px,y 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.
•
This method allows high data availability—Any two drives can fail without loss of critical data.
•
More drive capacity is usable than with RAID 1+0—Parity information requires only the storage space equivalent to two physical drives.
Disadvantages:
The main disadvantage of RAID 6 (ADG) is a relatively low write performance (lower than RAID 5) because of the need for two sets of parity data.
Drive arrays and fault-tolerance methods 114
RAID 50
RAID 50 is a nested RAID method in which the constituent hard drives are organized into several identical
RAID 5 logical drive sets (parity groups). The smallest possible RAID 50 configuration has six drives organized into two parity groups of three drives each.
For any given number of hard drives, data loss is least likely to occur when the drives are arranged into the configuration that has the largest possible number of parity groups. For example, four parity groups of three drives are more secure than three parity groups of four drives. However, less data can be stored on the array with the larger number of parity groups.
RAID 50 is particularly useful for large databases, file servers, and application servers.
Advantages:
•
Higher performance than for RAID 5, especially during writes.
•
Better fault tolerance than either RAID 0 or RAID 5.
•
Up to n physical drives can fail (where n is the number of parity groups) without loss of data, as long as the failed drives are in different parity groups.
Disadvantages:
•
All data is lost if a second drive fails in the same parity group before data from the first failed drive has finished rebuilding.
•
A greater percentage of array capacity is used to store redundant or parity data than with non-nested
RAID methods.
Drive arrays and fault-tolerance methods 115
RAID 60
RAID 60 is a nested RAID method in which the constituent hard drives are organized into several identical
RAID 6 logical drive sets (parity groups). The smallest possible RAID 60 configuration has eight drives organized into two parity groups of four drives each.
For any given number of hard drives, data loss is least likely to occur when the drives are arranged into the configuration that has the largest possible number of parity groups. For example, five parity groups of four drives are more secure than four parity groups of five drives. However, less data can be stored on the array with the larger number of parity groups.
RAID 60 is particularly useful for data archives and high-availability solutions.
Advantages:
•
Higher performance than for RAID 6, especially during writes.
•
Better fault tolerance than either RAID 0 or RAID 6.
•
Up to 2n physical drives can fail (where n is the number of parity groups) without loss of data, as long as no more than two failed drives are in the same parity group.
Disadvantages:
•
All data is lost if a third drive in a parity group fails before one of the other failed drives in the parity group has finished rebuilding.
•
A greater percentage of array capacity is used to store redundant or parity data than with non-nested
RAID methods.
Comparing the hardware-based RAID methods
Not all controllers support all RAID levels. To support some RAID levels, some controllers require SAAP
Drive arrays and fault-tolerance methods 116
Item RAID 0 RAID 1+0 RAID 5
RAID 6
(ADG)
RAID 1(0)
(ADM)
Alternative name
Striping (no fault tolerance)
Mirroring Distributed
Data
Guarding
Advanced
Data
Guarding
Advanced
Data
Mirroring
Formula for number of drives usable for data (n = total number of drives in array)
n n/2 n-1 n-2 n/3
Percentage of drive space usable* 100%
50% 67% to 93% 50% to 96% 33%
Minimum number of physical drives 1
2 3 4 3
Tolerates failure of one physical drive No
Tolerates simultaneous failure of more than one physical drive
No
Yes
Only if no two failed drives are in the same mirrored pair
High
Yes
No
Yes
Yes
Yes
Only if no three drives are in the same mirror group
Read performance
High High High High
Write performance
High Medium Low Low Medium
Relative cost
Low High Medium Medium Very high
*Values for the percentage 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 physical drives are used per array for
RAID 5; and (4) no more than 56 drives are used with RAID 6 (ADG).
Selecting a RAID method
Not all controllers support all RAID levels. To determine the RAID capabilities of your controller, see the model-specific information for your controller on the HP website
( http://www.hp.com/products/smartarray ).
Most important criterion Also important Suggested RAID level
Fault tolerance
Cost effectiveness
I/O performance
Cost effectiveness
I/O performance
Fault tolerance
I/O performance
Cost effectiveness
Fault tolerance
RAID 6
RAID 10 (ADM), RAID 1+0, RAID 50, RAID 60
RAID 6
RAID 5 (RAID 0 if fault tolerance is not required)
RAID 5 (RAID 0 if fault tolerance is not required)
RAID 10 (ADM), RAID 1+0, RAID 50, RAID 60
Alternative fault-tolerance methods
Your operating system may also support software-based RAID or controller duplexing.
•
Software-based RAID resembles hardware-based RAID, except that the operating system works with logical drives as if they were physical drives. To protect against data loss caused by physical drive failure, each logical drive must be in a different array from the others.
•
Controller duplexing uses two identical controllers with independent, identical sets of drives containing identical data. In the unlikely event of a controller failure, the remaining controller and drives will service all requests.
Drive arrays and fault-tolerance methods 117
Neither of these alternative fault-tolerance methods supports online spares or automatic data recovery, nor do they support auto-reliability monitoring or interim data recovery.
If you decide to use one of these alternative methods, configure your arrays with RAID 0 for maximum storage capacity and refer to your operating system documentation for further implementation details.
Drive arrays and fault-tolerance methods 118
Diagnosing array problems
Diagnostic tools
To troubleshoot array problems and generate feedback about arrays, use the following diagnostic tools:
•
ACU
For more recent products, array diagnostics is available with ACU v8.28.13.0 and later. This utility is available on the SmartStart CD in the controller kit and also on the HP website
( http://www.hp.com/support
). For more information about ACU, see "About ACU (on page 22 )." For
more information about error messages, see the HP ProLiant Servers Troubleshooting Guide.
•
ADU
For products that support SmartStart v8.25 and earlier, this utility is available on the SmartStart CD in the controller kit and also on the HP website ( http://www.hp.com/support ). When prompted for product information, enter the server model name. For more information about the meanings of the various ADU error messages, see the HP ProLiant Servers Troubleshooting Guide.
•
HP Array Diagnostics and SmartSSD Wear Gauge Utility
This standalone diagnostic utility provides configuration and error information about array controllers, storage enclosures, HBAs, drive cages, logical drives, physical drives, and tape drives. For any supported SSDs, the utility provides current usage level and remaining expected lifetime. For more
information, see "HP Array Diagnostics and SmartSSD Wear Gauge Utility (on page 96 )."
•
Event Notification Service
This utility reports array events to the Microsoft® Windows® system event log and IML. You can obtain the utility from the SmartStart CD or the HP website ( http://www.hp.com/support ). When prompted for product information, enter the server model name.
•
HP Insight Diagnostics
HP Insight Diagnostics is a tool that displays information about the system hardware configuration and performs tests on the system and its components, including drives if they are connected to Smart Array controllers. This utility is available on the SmartStart CD and also on the HP website
( http://www.hp.com/servers/diags ).
•
POST messages
Smart Array controllers produce diagnostic error messages (POST messages) at reboot. Many POST messages suggest corrective actions. For more information about POST messages, see the HP ProLiant
Servers Troubleshooting Guide.
Troubleshooting resources
HP ProLiant G7 (and earlier) products
The HP ProLiant Servers Troubleshooting Guide provides procedures for resolving common problems and comprehensive courses of action for fault isolation and identification, error message interpretation, issue resolution, and software maintenance on ProLiant servers and server blades. This guide includes
Diagnosing array problems 119
problem-specific flowcharts to help you navigate complex troubleshooting processes. To view the guide, select a language:
•
English ( http://www.hp.com/support/ProLiant_TSG_en )
•
French ( http://www.hp.com/support/ProLiant_TSG_fr )
•
Italian ( http://www.hp.com/support/ProLiant_TSG_it )
•
Spanish ( http://www.hp.com/support/ProLiant_TSG_sp )
•
German ( http://www.hp.com/support/ProLiant_TSG_gr )
•
Dutch ( http://www.hp.com/support/ProLiant_TSG_nl )
•
Japanese ( http://www.hp.com/support/ProLiant_TSG_jp )
HP ProLiant Gen8 products
The HP ProLiant Gen8 Troubleshooting Guide, Volume I: Troubleshooting provides procedures for resolving common problems and comprehensive courses of action for fault isolation and identification, issue resolution, and software maintenance on ProLiant servers and server blades. To view the guide, select a language:
•
English ( http://www.hp.com/support/ProLiant_TSG_v1_en )
•
French ( http://www.hp.com/support/ProLiant_TSG_v1_fr )
•
Spanish ( http://www.hp.com/support/ProLiant_TSG_v1_sp )
•
German ( http://www.hp.com/support/ProLiant_TSG_v1_gr )
•
Japanese ( http://www.hp.com/support/ProLiant_TSG_v1_jp )
•
Simplified Chinese ( http://www.hp.com/support/ProLiant_TSG_v1_sc )
The HP ProLiant Gen8 Troubleshooting Guide, Volume II: Error Messages provides a list of error messages and information to assist with interpreting and resolving error messages on ProLiant servers and server blades. To view the guide, select a language:
•
English ( http://www.hp.com/support/ProLiant_EMG_v1_en )
•
French ( http://www.hp.com/support/ProLiant_EMG_v1_fr )
•
Spanish ( http://www.hp.com/support/ProLiant_EMG_v1_sp )
•
German ( http://www.hp.com/support/ProLiant_EMG_v1_gr )
•
Japanese ( http://www.hp.com/support/ProLiant_EMG_v1_jp )
•
Simplified Chinese ( http://www.hp.com/support/ProLiant_EMG_v1_sc )
Diagnosing array problems 120
Acronyms and abbreviations
ACU
Array Configuration Utility
ADG
Advanced Data Guarding (also known as RAID 6)
ADM
Advanced Data Mirroring
ADU
Array Diagnostics Utility
CPQONLIN
NetWare Online Array Configuration Utility
HBA host bus adapter
MBR master boot record
MTBF mean time between failures
ORCA
Option ROM Configuration for Arrays
POST
Power-On Self Test
RAID redundant array of inexpensive (or independent) disks
RBSU
ROM-Based Setup Utility
Acronyms and abbreviations 121
RIS reserve information sector
SAAP
Smart Array Advanced Pack
SSP
Selective Storage Presentation
WBEM
Web-Based Enterprise Management
WWN
World Wide Name
Acronyms and abbreviations 122
Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback ( mailto:[email protected]
).
Include the document title and part number, version number, or the URL when submitting your feedback.
Documentation feedback 123
Index
A
ACU (Array Configuration Utility) 22
ACU GUI, methods for opening 30
ACU GUI, procedure overview 42
ADG (advanced data guarding) 113
ADU (Array Diagnostic Utility) 118
advanced configuration tasks, support for 6
advanced data guarding (ADG) 113
array accelerator, enabling or disabling, ACU
array accelerator, enabling or disabling,
array category options, ACU scripting 80
array configuration utilities, features 5
Array Configuration Utility (ACU) 22
array configuration, copying 73, 74
Array Diagnostic Utility (ADU) 118
array expansion, setting priority of 19
array, creating, ACU GUI 42, 50
array, creating, ACU scripting 77, 81
array, expanding, ACU scripting 81
array, moving, ACU scripting 81
array, shrinking, ACU scripting 81 array, specifying, ACU scripting 81
B
boot controller, setting 57 boot volume, setting 57
C
ClearConfigurationWithDataLoss 78 clearing a configuration 78
CLI (Command Line Interface) 13, 51
Command Line Interface (CLI) 13, 51
command mode, opening ACU in 52
comparison of RAID features 115
configuration procedure, CPQONLIN,
configuration tasks, advanced, support for 6
configuration tasks, CPQONLIN 17
configuration tasks, performing 11, 17, 42, 48,
configuration tasks, standard, support for 6
connection name 87 connection profile 87
console mode, opening ACU in 52
control category, ACU scripting 77
Index 124
controller options, ACU scripting 77
controller, specifying, ACU scripting 78
CPQONLIN, procedure overview 15
criteria for selecting a RAID level 116
D
data protection methods 109, 116
device information, obtaining 54
diagnostic report 46, 47, 59, 100, 102, 103
disabling drive cache 72 disabling the array accelerator, ACU CLI 72
disabling the array accelerator, ACU scripting 83
disabling the redundant controller 70
drive cache, enabling or disabling 72, 78
E
enabling drive cache 72 enabling the array accelerator, ACU CLI 72
enabling the array accelerator, ACU GUI 42, 48
enabling the array accelerator, ACU scripting 83
example CLI script, creating logical drive 62
expand priority, ACU scripting 80
expanding an array, ACU CLI 66
expanding an array, ACU GUI 42, 48
expanding an array, ACU scripting 81
expanding an array, CPQONLIN 20
extending logical drive capacity 68, 85
F
failed logical drive, re-enabling 71
fault-tolerance methods 106, 109
G
H
HBA category options, ACU scripting 87
hiding warning prompts, ACU CLI 54
I
I/O path, modifying 69, 70, 79
information about devices, obtaining 54
J
Index 125
K
L
local application, using ACU as 22, 23, 28
logical drive capacity extension 68, 85
logical drive category options, ACU scripting 83
logical drive, creating, ACU CLI 61
logical drive, creating, ACU GUI 42, 48, 50
logical drive, creating, CPQONLIN 18
logical drive, creating, ORCA 11
logical drive, description of 106
logical drive, failed, re-enabling 71
logical drive, migrating, ACU CLI 69
logical drive, migrating, ACU GUI 42
logical drive, migrating, ACU scripting 84, 86
logical drive, migrating, CPQONLIN 20
logical drive, moving, ACU CLI 63
logical drive, specifying, ACU scripting 83
M
methods for opening the ACU GUI 30
migrating stripe size or RAID level, ACU CLI 69
migrating stripe size or RAID level, ACU GUI 42
migrating stripe size or RAID level, ACU
migrating stripe size or RAID level, CPQONLIN 20
mounting virtual media 23, 24, 25
N
Novell NetWare, configuration tool for 5, 15
O
online spare, ACU scripting 82
Option ROM Configuration for Arrays (ORCA) 10
options, scripting, list of 75
ORCA (Option ROM Configuration for Arrays) 10
overview of configuration procedure,
overview of configuration utilities 5
P
parameters, in CLI, obtaining values of 53
physical drive write cache, enabling or
physical drives, adding, ACU CLI 66
physical drives, adding, ACU GUI 42, 48
physical drives, adding, CPQONLIN 20
Q
R
RAID level selection criteria 116
RAID levels 109, 110, 111, 112, 113, 114, 115
RAID levels, comparison of features 115
RAID-level migration, ACU CLI 69
RAID-level migration, ACU GUI 42, 48
RAID-level migration, ACU scripting 84
Index 126
RAID-level migration, CPQONLIN 20
read-write ratio, ACU scripting 79, 83
rebuild priority, ACU scripting 80
recombining a split mirrored array 45
redundant controller, disabling 70
redundant controller, modifying I/O path of 69,
redundant controller, preferred path settings
re-enabling a failed logical drive 71
registering a license key 12, 44
remote server, configuring 29 remote service, using ACU as 29
Repeat 85 repeat configuration 85
S
screen description 10, 15, 31, 32, 34, 37, 40
Selective Storage Presentation (SSP),
shorthand in CLI 54 show (CLI command) 54
Smart Array Advanced Pack (SAAP) 8
SmartSSD Wear Gauge report 47, 103, 104, 105
SmartStart CD as source of ACU 23
spare drives, ACU scripting 82
SSP (Selective Storage Presentation),
standard configuration tasks, support for 6
standby controller, disabling 70
stripe size migration, ACU CLI 69
stripe size migration, ACU GUI 42, 48
stripe size migration, ACU scripting 86
stripe size migration, CPQONLIN 20
summary of configuration procedure,
supported operating systems 27
T
tasks supported in each utility 6
troubleshooting 118 troubleshooting resources 118
typical procedures, ACU CLI 57
typical procedures, CPQONLIN 17
U
V
video performance optimization 60, 80
Index 127
W
warning prompts, hiding, ACU CLI 54
write cache, on physical drives, enabling or
X
Index 128
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project