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

HP ProLiant ML310e HP Scripting Toolkit 9.30 for Linux User Guide - Page 29

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

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

Page 29 highlights

Expression examples Expression input "PCI:Smart Array 5i" Result True if the Smart Array 5i Controller is found in the system HWQ:TotalRAM gte 512 HWQ:ROMDate neq "11/12/2004" True if the amount of RAM in the hardware discovery file is at least 512 True if the ROM date in the hardware discovery file is not 11/12/2004 HWQ:SystemName eq "ProLiant DL380 G2" True if the system name in the hardware discovery file exactly matches "ProLiant DL380 G2" HWQ:SystemName eq "ProLiant DL380 G2" and "PCI:Smart Array 5i" and HWQ:ROMDate eq "11/12/2004" 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 [path]hpdiscoveryfilename [path]allboards.xml variable= ... HWQUERY command-line arguments Command-line argument [path]hpdiscoveryfilename [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 Meaning The command was completed successfully. N arguments were ignored because they were not in the variable= format. Using HWQUERY 29

Section	Page
HP Scripting Toolkit for Linux User Guide	1
Contents	3
1 Introduction	7
Scripting Toolkit	7
Minimum requirements	7
2 Deployment using the Scripting Toolkit	8
Deployment overview	8
Sample deployment procedure	8
Creating a network share	9
Capturing a reference configuration from the source server	9
Creating an ISO image to be written to media	10
Configuring the target server	10
Installing the operating system	11
3 Booting and OS installation	12
SYSLINUX	12
Booting using PXE	12
Setting up a TFTP server	13
Populating the TFTP directory share	14
Setting up a DHCP server	14
Booting from a USB drive key	15
Performing an unattended operating system installation	15
System hardware configuration	15
Microsoft Windows install_win.sh sample script	19
Red Hat Linux anaconda-ks.cfg sample file	19
4 Scripting Toolkit utilities	22
Native package formats	22
Syntax conventions	22
Utility online help	22
Using Scripting Toolkit utilities	23
Using REBOOT	23
REBOOT command-line syntax	23
REBOOT command-line arguments	23
REBOOT return codes	23
REBOOT command-line examples	24
Using SETBOOTORDER	24
SETBOOTORDER command-line syntax	24
SETBOOTORDER command-line arguments	24
SETBOOTORDER return codes	24
SETBOOTORDER command-line examples	24
Using STATEMGR	24
STATEMGR command-line syntax	25
STATEMGR command-line arguments	25
STATEMGR return codes	25
STATEMGR command-line examples	25
Using RBSURESET	25
RBSURESET command-line syntax	26
RBSURESET command-line arguments	26
RBSURESET return codes	26
Using BOOTEXTRACT	26
BOOTEXTRACT command-line syntax	26
BOOTEXTRACT command-line arguments	26
BOOTEXTRACT return codes	26
Using HPDISCOVERY	26
HPDISCOVERY command-line syntax	27
HPDISCOVERY command-line arguments	27
HPDISCOVERY return codes	27
HPDISCOVERY command-line examples	27
Using IFHW	27
IFHW command-line syntax	27
IFHW command-line arguments	27
IFHW return codes	28
IFHW command-line examples	28
Expression operators and terms	28
Expression examples	29
Using HWQUERY	29
HWQUERY command-line syntax	29
HWQUERY command-line arguments	29
HWQUERY return codes	29
HWQUERY command-line examples	30
Using CONREP	30
CONREP command-line syntax	31
CONREP command line arguments	31
CONREP return codes	31
CONREP screen output	31
CONREP -s (Store to Data file) Example usage for HP ProLiant servers not using the Oxx ROM family	32
CONREP –l (Load from Data File) Example Usage for HP ProLiant servers not using the Oxx ROM family	32
CONREP Data File Sample Contents for HP ProLiant servers not using the Oxx ROM family	32
CONREP command file contents for HP ProLiant servers not using the Oxx ROM family	33
Using HPRCU	34
HPRCU command-line syntax	34
HPRCU command line arguments	35
HPRCU return codes	35
HPRCU sample XML format	35
Using HPACUSCRIPTING	36
Capturing a configuration	36
Using an Input script	36
Creating an ACU script file	37
Sample custom input script	37
Script file options	38
Control category	39
Action mode	40
Method mode	40
Controller category	40
Controller	40
ChassisName	41
ClearConfigurationWithDataLoss	41
LicenseKey, DeleteLicenseKey	41
PreferredPathMode	41
ReadCache, WriteCache	41
RebuildPriority, ExpandPriority	42
SSPState	42
SurfaceScanDelay	42
Video performance options	42
Array category	43
Array	43
Drive	43
DriveType	43
OnlineSpare	44
Logical Drive category	44
ArrayAccelerator	44
LogicalDrive	44
LogicalDriveSSPState	44
ParityGroups	45
PreferredPath	45
RAID	45
Sectors	45
Size	45
SSPAdaptersWithAccess	46
StripeSize	46
HBA category	46
ConnectionName	46
HBA_WW_ID	47
HostMode	47
ACU scripting error messages	47
Using HPLPCFG	51
HPLPCFG command-line syntax	51
HPLPCFG command-line arguments	51
HPLPCFG return codes	51
HPLPCFG command-line examples	52
Using LO100CFG	52
LO100CFG command-line syntax	52
LO100CFG command-line arguments	53
LO100CFG return codes	53
LO100CFG command-file contents	53
Using HPQLAREP	54
HPQLAREP command-line syntax	54
HPQLAREP command-line arguments	54
HPQLAREP return codes	55
HPQLAREP command-line examples	55
Using HPONCFG	56
HPONCFG command-line syntax	56
HPONCFG command-line arguments	56
HPONCFG return codes	57
HPONCFG command file contents	57
Obtaining an entire configuration	57
Obtaining a specific configuration	58
Setting a configuration	59
HPONCFG command-line examples	59
5 Troubleshooting	60
Troubleshooting table	60
6 Support and other resources	61
Information to collect before contacting HP	61
How to contact HP	61
Subscription service	61
Related information	61
Scripting Toolkit support	62
Typographic conventions	62
HP Insight Remote Support software	62
7 Documentation feedback	64
Acronyms and abbreviations	65

Match case Limit results 1 per page

Expression examples

Result

Expression input

True if the Smart Array 5i Controller is found in the system

"PCI:Smart Array 5i"

True if the amount of RAM in the hardware discovery file

is at least 512

HWQ:TotalRAM gte 512

True if the ROM date in the hardware discovery file is not

11/12/2004

HWQ:ROMDate neq

"11/12/2004"

True if the system name in the hardware discovery file

exactly matches "ProLiant DL380 G2"

HWQ:SystemName eq

"ProLiant DL380 G2"

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 [

path

]hpdiscoveryfilename [

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.

[path]hpdiscoveryfilename

This argument specifies the allboards.xml PCI device list

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

[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.

Using HWQUERY