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

HP ProLiant SL4545 HP Scripting Toolkit 9.30 for Windows User Guide - Page 23

Using HWQUERY, HWQUERY command-line syntax, HWQUERY return codes

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

Page 23 highlights

Expression input HWQ:SystemName eq "ProLiant DL380 G2" and "PCI:Smart Array 5i" and HWQ:ROMDate eq "11/12/2004" Result True if the system is a ProLiant DL380 G2 with a Smart Array 5i Controller present and a ROM date of 11/12/2004 "PCI:Smart Array 5i" or "PCI:Smart Array True if the system contains a Smart Array 5i Controller or 6i" a Smart Array 6i Controller Using HWQUERY HWQUERY is used from a script, in conjunction with other utilities, to control the deployment. The HWQUERY utility enables you to use data from the hardware discovery file in your own scripts. HWQUERY cannot alter environment variables directly. To set the variable, the output of HWQUERY must be used by the hosting script. The most common way to use it is to write the output to an intermediate script that is subsequently called by the hosting script. HWQUERY command-line syntax hwquery [drive:][path]hpdiscoveryfilename [drive:][path]allboards.xml variable= ... HWQUERY command line arguments Command-line argument [drive:][path]hpdiscoveryfilename [drive:][path]allboards.xml variable= ... Description This argument specifies the hardware discovery file used to run the query. This argument specifies the allboards.xml PCI device list file, which is used to convert PCI IDs found in hardware discovery into device names, such as "Smart Array 5i Controller." In this argument, variable is the name of an environment variable and is a PCI device name or the name of an element from the hardware discovery file. Arguments must be in quotes if contains spaces. is case-sensitive. You can specify multiple variable= arguments. HWQUERY return codes Value 0 n HWQUERY command-line examples Meaning The command was completed successfully. N arguments were ignored because they were not in the variable= format. Command-line argument hwquery hpdiscovery.xml allboards.xml MY_SYS_RAM=TotalRAM Description For a hpdiscovery.xml file that contains 768, HWQUERY produces the following: Using HWQUERY 23

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

Result

Expression input

True if the system is a ProLiant DL380 G2 with a Smart

Array 5i Controller present and a ROM date of

11/12/2004

HWQ:SystemName eq

"ProLiant DL380 G2" and "PCI:Smart Array

5i" and HWQ:ROMDate eq "11/12/2004"

True if the system contains a Smart Array 5i Controller or

a Smart Array 6i Controller

"PCI:Smart Array 5i" or "PCI:Smart Array

6i"

Using HWQUERY

HWQUERY is used from a script, in conjunction with other utilities, to control the deployment. The

HWQUERY utility enables you to use data from the hardware discovery file in your own scripts.

HWQUERY cannot alter environment variables directly. To set the variable, the output of HWQUERY

must be used by the hosting script. The most common way to use it is to write the output to an

intermediate script that is subsequently called by the hosting script.

HWQUERY command-line syntax

hwquery [

drive:

][

path

]hpdiscoveryfilename

[

drive:

][

path

]allboards.xml

variable

string

> ...

HWQUERY command line arguments

Description

Command-line argument

This argument specifies the hardware discovery file used

to run the query.

[drive:][path]hpdiscoveryfilename

This argument specifies the

allboards.xml

PCI device

list file, which is used to convert PCI IDs found in hardware

[drive:][path]allboards.xml

discovery into device names, such as "Smart Array 5i

Controller."

In this argument,

variable

is the name of an environment

variable and <

string

> is a PCI device name or the name

variable=<string>

of an element from the hardware discovery file. Arguments

must be in quotes if <string> contains spaces. <

string

> is

case-sensitive.

You can specify multiple

variable

string

> arguments.

...

HWQUERY return codes

Meaning

Value

The command was completed successfully.

arguments were ignored because they were not in the

variable=<string>

format.

HWQUERY command-line examples

Description

Command-line argument

For a

hpdiscovery.xml

file that contains

<TotalRAM>768</TotalRAM>, HWQUERY produces the

following:

hwquery hpdiscovery.xml allboards.xml

MY_SYS_RAM=TotalRAM

Using HWQUERY