HP Scripting Toolkit 9.10 for Linux User Guide
Table Of Contents
- HP Scripting Toolkit for Linux User Guide
- Contents
- 1 Introduction
- 2 Deployment using the Scripting Toolkit
- 3 Booting and OS installation
- 4 Scripting Toolkit utilities
- Native package formats
- Syntax conventions
- Utility online help
- Using Scripting Toolkit utilities
- Using REBOOT
- Using SETBOOTORDER
- Using STATEMGR
- Using RBSURESET
- Using BOOTEXTRACT
- Using HPDISCOVERY
- Using IFHW
- Using HWQUERY
- Using CONREP
- CONREP command-line syntax
- CONREP command line arguments
- CONREP return codes
- CONREP screen output
- CONREP -s (Store to Data file) Example usage for HP ProLiant servers not using the Oxx ROM family
- CONREP –l (Load from Data File) Example Usage for HP ProLiant servers not using the Oxx ROM family
- CONREP Data File Sample Contents for HP ProLiant servers not using the Oxx ROM family
- CONREP command file contents for HP ProLiant servers not using the Oxx ROM family
- Using HPRCU
- Using HPACUSCRIPTING
- Using HPLPCFG
- Using LO100CFG
- Using HPQLAREP
- Using HPONCFG
- 5 Troubleshooting
- 6 Support and other resources
- 7 Documentation feedback
- Acronyms and abbreviations
- Index
Expression examples
ResultExpression 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
DescriptionCommand-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
MeaningValue
The command was completed successfully.
0
N arguments were ignored because they were not in the
variable=<string> format.
n
Using HWQUERY 29