HP ProLiant WS460c HP Scripting Toolkit 9.30 for Windows User Guide - Page 30

Capturing a configuration, Using an Input script

Get HP ProLiant WS460c PDF manuals and user guides View all HP ProLiant WS460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

For more information, see the Configuring Arrays on HP Smart Array Controllers Reference Guide on the HP website at http://www.hp.com/support/CASAC_RG_en. 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 (page 30) 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 (page 30) ACU reads the array configuration described in a specified script file. See "Creating an ACU script file" (page 31). ACU then applies this configuration to a target system. NOTE: For a complete list of all command-line parameters, execute the /? utility. 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" (page 31). 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. 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. 30 Scripting Toolkit utilities

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
For more information, see the
Configuring Arrays on HP Smart Array Controllers Reference Guide
on the HP website at
h
t
tp://w
w
w
.hp
.co
m/su
ppo
r
t/CA
S
A
C_R
G_e
n
.
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
(page 30)
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
(page 30)
ACU reads the array configuration described in a specified script file. See
“Creating an ACU
script file” (page 31)
. ACU then applies this configuration to a target system.
NOTE:
For a complete list of all command-line parameters, execute the
/?
utility.
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” (page 31)
.
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.
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.
30
Scripting Toolkit utilities