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

HP ProLiant ML310e HP Scripting Toolkit 9.30 for Windows User Guide - Page 16

Scripting Toolkit utilities, Syntax conventions, Utility online help, numbers, spaces

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

Page 16 highlights

4 Scripting Toolkit utilities Syntax conventions Syntax refers to the way a command and parameters must be entered. Unless specified otherwise, enter commands, parameters, and switches in all uppercase or all lowercase letters. Sample syntax line: SAMPLE[/R|-R][DRIVE:][PATH]FILENAME[...] Command element SAMPLE [ ] / or DRIVE: PATH FILENAME ... Meaning Specifies the name of the command. Indicates a component of the command line. Enter only the information within the brackets, not the brackets themselves. Indicates a command line switch for executable files. Specifies the name of the hard disk drive, diskette drive, or other storage device. Specifies the route the operating system must follow through the directory structure to locate a directory or file. A path and file name must be specified only if the file is not in the current directory. This document uses uppercase file names. A device name or a drive letter cannot be specified for a file name. Indicates that the previous parameter or switch can be repeated several times in a command. Enter only the information, not the ellipsis (...) itself. In this document, the length of an example command or syntax might require it to continue on another line. When this happens, the second line and any additional lines are indented under the first line. Placeholder items used in the syntax lines in this chapter include: • Source-Specifies the location of the data to be transferred to a specified destination or used as input to a command. The source can consist of a drive letter and colon, a directory name, a file name, or a combination of these items. • Destination-Specifies the location to which the data specified by the source is to be transferred. The destination can consist of a drive letter and colon, a directory name, a file name, or a combination of these items. • String-Specifies a group of characters to be treated as a unit. A string can include letters, numbers, spaces, or any other characters and is usually enclosed in double quotation marks. Utility online help Most Scripting Toolkit utilities include usage instructions. To obtain help with the syntax, parameters, and switches of a particular Scripting Toolkit utility, enter the file name followed by /? in the command line. For example, for usage instructions on the CONREP utility, enter the following command: CONREP /? The utility displays information about its command line syntax, argument, and switches. Using Scripting Toolkit utilities The Scripting Toolkit utilities control the installation process, read the source server configuration, and duplicate the configuration on a target server through a generated script file. 16 Scripting Toolkit utilities

Section	Page
HP Scripting Toolkit for Windows User Guide	1
Contents	3
1 Introduction	6
Scripting Toolkit for Windows	6
Microsoft Windows Preinstallation Environment	6
Minimum requirements	6
2 Deployment using the Scripting Toolkit for Windows	7
Deployment overview	7
Sample deployment procedure	7
Creating a network share	8
Adding drivers to Windows PE 3.0	8
Adding drivers to Windows PE 4.0	9
Capturing a reference configuration from the source server	10
Configuring the target server and installing the operating system	11
3 Advanced topics	12
Overview	12
Customizing deployment scripts using HPDISCOVERY and IFHW	12
Querying the HPDISCOVERY file based on system name	12
Querying the HPDISCOVERY file to determine the presence of a particular card	12
Querying the HPDISCOVERY file to determine the presence of a card family	13
Booting Windows PE from a USB drive key	13
Flashing the ROM in a Windows PE environment	13
Erasing array configurations	15
4 Scripting Toolkit utilities	16
Syntax conventions	16
Utility online help	16
Using Scripting Toolkit utilities	16
Using REBOOT	17
REBOOT command-line syntax	17
REBOOT command-line arguments	17
REBOOT return codes	17
REBOOT command-line examples	17
Using SETBOOTORDER	18
SETBOOTORDER command-line syntax	18
SETBOOTORDER command-line arguments	18
SETBOOTORDER return codes	18
SETBOOTORDER command-line examples	18
Using STATEMGR	18
STATEMGR command-line syntax	18
STATEMGR command-line arguments	19
STATEMGR return codes	19
STATEMGR command-line examples	19
Using RBSURESET	19
RBSURESET command-line syntax	19
RBSURESET command-line arguments	19
RBSURESET return codes	20
Using HPDISCOVERY	20
HPDISCOVERY command-line syntax	20
HPDISCOVERY command line arguments	20
HPDISCOVERY return codes	21
HPDISCOVERY command line examples	21
Using IFHW	21
IFHW command-line syntax	21
IFHW command-line arguments	21
IFHW return codes	21
IFHW command line examples	22
Expression operators and terms	22
Expression examples	22
Using HWQUERY	23
HWQUERY command-line syntax	23
HWQUERY command line arguments	23
HWQUERY return codes	23
HWQUERY command-line examples	23
Using CONREP	24
CONREP command-line syntax	24
CONREP command line arguments	25
CONREP return codes	25
CONREP screen output	25
CONREP -s (Store to Data file) Example usage for HP ProLiant servers not using the Oxx ROM family	26
CONREP –l (Load from Data file) Example usage for HP ProLiant servers not using the Oxx ROM family	26
CONREP Data File Sample Contents for HP ProLiant servers not using the Oxx ROM family	26
CONREP command file contents	27
Using HPRCU	28
HPRCU command-line syntax	28
HPRCU command line arguments	28
HPRCU return codes	29
HPRCU sample XML format	29
Using HPACUSCRIPTING	29
Capturing a configuration	30
Using an Input script	30
Creating an ACU script file	31
Sample custom input script	31
Script file options	32
Control category	33
Action mode	34
Method mode	34
Controller category	34
Controller	34
ChassisName	35
ClearConfigurationWithDataLoss	35
LicenseKey, DeleteLicenseKey	35
PreferredPathMode	35
ReadCache, WriteCache	35
RebuildPriority, ExpandPriority	36
SSPState	36
SurfaceScanDelay	36
Video performance options	36
Array category	37
Array	37
Drive	37
DriveType	37
OnlineSpare	38
Logical Drive category	38
ArrayAccelerator	38
LogicalDrive	38
LogicalDriveSSPState	38
ParityGroups	39
PreferredPath	39
RAID	39
Sectors	39
Size	39
SSPAdaptersWithAccess	40
StripeSize	40
HBA category	40
ConnectionName	40
HBA_WW_ID	41
HostMode	41
ACU scripting error messages	41
Using HPLPCFG	45
HPLPCFG command-line syntax	45
HPLPCFG command-line arguments	45
HPLPCFG return codes	45
HPLPCFG command-line examples	46
Using LO100CFG	46
LO100CFG command-line syntax	46
LO100CFG command-line arguments	47
LO100CFG return codes	47
LO100CFG command-file contents	47
Using HPQLAREP	48
HPQLAREP command-line syntax	48
HPQLAREP command-line arguments	48
HPQLAREP return codes	49
HPQLAREP command-line examples	49
Using HPONCFG	50
HPONCFG command-line syntax	50
HPONCFG command-line arguments	50
HPONCFG return codes	51
HPONCFG command file contents	51
Obtaining an entire configuration	51
Obtaining a specific configuration	52
Setting a configuration	53
HPONCFG command-line examples	53
5 Troubleshooting	54
Troubleshooting table	54
6 Support and other resources	55
Information to collect before contacting HP	55
How to contact HP	55
Subscription service	55
Related information	55
Scripting Toolkit support	55
Typographic conventions	56
HP Insight Remote Support software	56
7 Documentation feedback	58
Acronyms and abbreviations	59

Match case Limit results 1 per page

4 Scripting Toolkit utilities

Syntax conventions

Syntax refers to the way a command and parameters must be entered. Unless specified otherwise,

enter commands, parameters, and switches in all uppercase or all lowercase letters.

Sample syntax line:

SAMPLE[/R|-R][DRIVE:][PATH]FILENAME[...]

Meaning

Command element

Specifies the name of the command.

SAMPLE

Indicates a component of the command line. Enter only the information within the brackets,

not the brackets themselves.

[ ]

Indicates a command line switch for executable files.

/ or -

Specifies the name of the hard disk drive, diskette drive, or other storage device.

DRIVE:

Specifies the route the operating system must follow through the directory structure to locate a

directory or file. A path and file name must be specified only if the file is not in the current

directory.

PATH

This document uses uppercase file names. A device name or a drive letter cannot be specified

for a file name.

FILENAME

Indicates that the previous parameter or switch can be repeated several times in a command.

Enter only the information, not the ellipsis (…) itself.

...

In this document, the length of an example command or syntax might require it to continue on

another line. When this happens, the second line and any additional lines are indented under the

first line.

Placeholder items used in the syntax lines in this chapter include:

•

Source—Specifies the location of the data to be transferred to a specified destination or used

as input to a command. The source can consist of a drive letter and colon, a directory name,

a file name, or a combination of these items.

•

Destination—Specifies the location to which the data specified by the source is to be transferred.

The destination can consist of a drive letter and colon, a directory name, a file name, or a

combination of these items.

•

String—Specifies a group of characters to be treated as a unit. A string can include letters,

numbers, spaces, or any other characters and is usually enclosed in double quotation marks.

Utility online help

Most Scripting Toolkit utilities include usage instructions. To obtain help with the syntax, parameters,

and switches of a particular Scripting Toolkit utility, enter the file name followed by

in the

command line. For example, for usage instructions on the CONREP utility, enter the following

command:

CONREP /?

The utility displays information about its command line syntax, argument, and switches.

Using Scripting Toolkit utilities

The Scripting Toolkit utilities control the installation process, read the source server configuration,

and duplicate the configuration on a target server through a generated script file.

Scripting Toolkit utilities