HP ROM-Based Setup Utility User Guide

HP ROM Configuration Utility (HPRCU)
NOTE: This utility is available for HP ProLiant Gen8 servers, except for the HP ProLiant DL580
Gen8 server.
For more information, see the HP Scripting Toolkit User Guide for your operating system environment
on the HP website (http://www.hp.com/go/stk/docs).
Using HPRCU
HPRCU is an RBSU configuration utility similar to CONREP. This utility is supported on all HP
ProLiant Gen8 servers except the HP ProLiant DL580 Gen8 server. This utility does not use a
definition XML file like the CONREP utility, but directly reads the same table that RBSU uses for
feature names and settings. All features and options are number based. Each feature and option
has a unique number.
Using HPRCU has the following features:
• All system ROM settings and the current selections are listed together in one output/input XML
file.
• No updated binary or XML file is needed when BIOS adds or changes features. HPRCU now
reads the same tables that RBSU does, which are located in the memory at system boot. When
the BIOS changes or adds a new setting, no update to HPRCU is needed.
• The HPRCU XML file shows the default settings for each RBSU option.
• HPRCU is not supported on UEFI-based ProLiant servers. Instead, use CONREP.
HPRCU command-line syntax
hprcu -s | -l [-f file.xml ] [ -h ]
HPRCU command line arguments
DescriptionCommand line argument
This argument saves the system configuration to a file.
-s
This argument loads the system configuration from a file
and writes it to the target server.
-l
Name of the input or output file. If not specified, the XML
configuration defaults to hprcu.xml.
-f {file.xml}
This argument displays program usage.
-h
Outputs the help and warning text for each feature. Only
valid with the -s option.
-t
Save/Load raw data features (IPL, PCI Devices, controller
Order, etc.) Must be applied to identical systems.
-r
HPRCU return codes
DescriptionCommand line argument
The command was completed successfully.0
The server is not supported by this utility.1
The input XML file is missing or is in an invalid format.2
One of the dependencies is missing. See the error message
for details.
3
Scripted configuration flow 203