HP ProLiant DL280 Configuring Arrays on HP Smart Array Controllers Reference G - Page 68

Enabling a script to exit on error, Using ACU scripting, Capturing a configuration

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

Page 68 highlights

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] 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 10) • Accessing ACU in the online environment (on page 15) The ACU Scripting application has two scripting modes: • Capture mode for capturing a configuration (on page 68) 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 68) ACU reads the array configuration described in a specified script file. See "Creating an ACU script file (on page 69)." 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 69)." 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 HP Array Configuration Utility 68

  • 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
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
HP Array Configuration Utility
68
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]
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
10
)
•
Accessing ACU in the online environment (on page
15
)
The ACU Scripting application has two scripting modes:
•
Capture mode for capturing a configuration (on page
68
)
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
68
)
ACU reads the array configuration described in a specified script file. See "Creating an ACU script file
(on page
69
)." 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
69
)."
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