Using Hprcu; Hprcu Command-Line Syntax - HP ProLiant DL320e User Manual

Hp scripting toolkit 9.30 for linux user guide
Hide thumbs Also See for ProLiant DL320e:
Table of Contents

Advertisement

<Index0>00 </Index0>
<Index1>01 </Index1>
<Index2>03 </Index2>
<Index3>02 </Index3>
<Index4>04 </Index4>
<Index5>ff </Index5>
<Index6>ff </Index6>
<Index7>ff </Index7>
</Section>
<Section name="PCI_Devices"
helptext=
"Lists of PCI devices and their interrupts-not displayed if default" >EMPTY_DELETE</Section>
<Section name="Controller_Order"
helptext=
"Lists the current boot controller ordering">
<Id0>80 86 25 a3 </Id0>
<Slot0>00 </Slot0>
<BusDev0>00 fa </BusDev0>
<Rest0>41 </Rest0>
<Id1>0e 11 ff ff </Id1>
<Slot1>00 </Slot1>
<BusDev1>00 78 </BusDev1>
<Rest1>c1 </Rest1>
</Section>
</Conrep>

Using HPRCU

HPRCU is an RBSU configuration utility similar to CONREP. This utility is supported on HP ProLiant
Gen8 servers and later. 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 now number based. Each feature and option has a unique number.
Using HPRCU over CONREP has the following benefits:
Simpler user interface— All system ROM settings and the current selections are listed together
in one output/input XML file.
Fewer updates—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.
Default ROM settings enhancement—The HPRCU XML file now shows users the default settings
for each RBSU option.

HPRCU command-line syntax

hprcu -s | -l [-f
34
Scripting Toolkit utilities
file.xml ] [ -h ]

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Proliant ml310eScripting toolkit for linux

Table of Contents