Home » HP Manuals » Servers » HP ProLiant DL288 » Manual Viewer

HP ProLiant DL288 Configuring Arrays on HP Smart Array Controllers Reference G - Page 74

Using ACU scripting, Capturing a configuration, Using an Input script

Add to My Manuals
Save this manual to your list of manuals

Page 74 highlights

Using ACU scripting 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. The ACU Scripting application has two scripting modes: • Capture mode for capturing a configuration (on page 74) 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 74) ACU reads the array configuration described in a specified script file. See "Creating an ACU script file (on page 75)." 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 75)." 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 74

Section	Page
Configuring Arrays on HP Smart Array Controllers Reference Guide	1
Notice	2
Contents	3
Overview of array configuration tools	5
Utilities available for configuring an array	5
Comparison of the utilities	5
Support for standard configuration tasks	6
Support for advanced configuration tasks	6
HP Smart Array Advanced Pack	8
About SAAP	8
Required hardware	8
Option ROM Configuration for Arrays	9
About ORCA	9
Using the ORCA menu-driven interface	9
Creating a logical drive with ORCA	10
Installing a license key with ORCA	11
Using the ORCA CLI	12
HP Online Array Configuration Utility for NetWare	14
About CPQONLIN	14
Summary of configuration procedure using CPQONLIN	14
Operating CPQONLIN in manual configuration mode	15
Menu options in CPQONLIN	15
Typical manual configuration procedures	16
Creating a new array and logical drive	17
Adding spare drives	17
Setting the rebuild priority or expand priority	18
Setting the accelerator ratio	19
Expanding an array	19
Migrating RAID level or stripe size	20
HP Array Configuration Utility	21
About ACU	21
Using the ACU GUI	21
Configuring a server that has ACU installed	22
Configuring a remote server using ACU located on a local server	23
Configuring a local server using ACU located on a remote server	24
Configuring a server using ACU located on the SmartStart CD	26
Navigating the GUI	28
Configuration screen	29
Access Control (SSP) screen	31
Diagnostics screen	34
Wizards screen	37
ACU help	40
Configuration tasks	40
Installing a license key with ACU	41
Performing a Configuration task	42
Working with mirrored arrays	43
Splitting a mirrored array	44
Recombining a split mirrored array	44
Access Control (SSP) tasks	44
Performing an Access Control (SSP) task	45
Diagnostics tasks	47
Performing a Diagnostics task	47
Wizards	50
Using Wizards	51
Using Express Configuration	52
Using the ACU CLI	54
Opening the CLI in Console mode	54
Opening the CLI in Command mode	55
CLI syntax	55
The <target> variable	55
The <command> variable	56
Querying a device	56
Hiding warning prompts	56
Keyword abbreviations	57
The show command	57
The help command	59
Typical procedures	59
Setting the target	59
Identifying devices	60
Deleting target devices	60
Generating a diagnostic report	61
Erasing a physical or logical drive	61
Rescanning the system	61
Entering or deleting a license key	62
Optimizing controller performance for video	62
Creating a logical drive	62
Sample scenario	63
Assigning a chassis name to the controller	65
Managing spare drives	65
Expanding an array	66
Shrinking an array	66
Moving an array	67
Extending a logical drive	67
Migrating a logical drive	68
Using Selective Storage Presentation	68
Sample scenario	69
Modifying connection names	70
Managing host modes (connection profiles)	70
Setting the preferred path mode	71
Assigning a redundant controller to a logical drive	71
Disabling a redundant controller	71
Changing the Rebuild Priority setting	71
Changing the Expand Priority setting	72
Changing the surface scan delay time	72
Re-enabling a failed logical drive	72
Changing the controller cache ratio	73
Enabling or disabling the drive cache	73
Enabling or disabling the array accelerator	73
Using ACU scripting	74
Capturing a configuration	74
Using an Input script	74
Creating an ACU script file	75
Sample custom input script	75
Script file options	76
Control category	78
Action mode	78
Method mode	78
Controller category	78
Controller	79
ChassisName	79
ClearConfigurationWithDataLoss	79
LicenseKey, DeleteLicenseKey	80
PreferredPathMode	80
ReadCache, WriteCache	80
RebuildPriority, ExpandPriority	81
SSPState	81
SurfaceScanDelay	81
Video performance options	81
Array category	81
Array	81
Drive	82
DriveType	82
OnlineSpare	82
Logical Drive category	83
ArrayAccelerator	83
LogicalDrive	83
LogicalDriveSSPState	84
ParityGroups	84
PreferredPath	84
RAID	84
Sectors	84
Size	85
SSPAdaptersWithAccess	85
StripeSize	85
HBA category	86
ConnectionName	86
HBA_WW_ID	86
HostMode	86
ACU scripting warning messages	86
ACU scripting error messages	87
Probability of logical drive failure	92
Factors involved in logical drive failure	92
Relative probability of failure for different logical drives	93
Drive arrays and fault-tolerance methods	94
Drive arrays	94
Fault-tolerance methods	96
RAID 0—No fault tolerance	97
RAID 1+0 (RAID 10)	98
RAID 5—distributed data guarding	99
RAID 6 (ADG)—Advanced Data Guarding	100
RAID 50	101
RAID 60	102
Comparing the hardware-based RAID methods	102
Selecting a RAID method	103
Alternative fault-tolerance methods	103
Diagnosing array problems	105
Diagnostic tools	105
Troubleshooting resources	105
Acronyms and abbreviations	107

Match case Limit results 1 per page

HP Array Configuration Utility

Using ACU scripting

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.

The ACU Scripting application has two scripting modes:

•

Capture mode for capturing a configuration (on page

)

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

)

ACU reads the array configuration described in a specified script file. See "Creating an ACU script

file (on page

)." 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

)."

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.