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

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

Using SETBOOTORDER, SETBOOTORDER command-line syntax, SETBOOTORDER return codes, Using STATEMGR

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

Page 18 highlights

Using SETBOOTORDER SETBOOTORDER enables you to set the order in which devices are booted, including diskette drives, CD-ROM or DVD drives, hard drives, PXE, and USB devices. This utility sets the boot order only for devices that exist for a server. The devices can be set to boot in any order. SETBOOTORDER cannot be used to set the storage controller order. You must use the CONREP utility. For more information about setting the controller order, see "Using CONREP" (page 24) NOTE: Any changes made to the SETBOOTORDER take affect at the next reboot. For HP ProLiant servers with Oxx ROM Family (most 100 series servers), only one device can be set as the boot device and others cannot be re-ordered. These Oxx servers do not support the default or usb parameters. SETBOOTORDER command-line syntax setbootorder [floppy cdrom pxe hd usb | default] [/?] SETBOOTORDER command-line arguments Options are disabled if not listed in the argument. Command line argument floppy cdrom pxe hd usb default /? Description The order of these arguments sets the boot order for the system devices. Each term can be used only once in any order. It is not necessary to use all terms. HP ProLiant 100 series servers can only pass in one option. This argument resets the boot order to the factory default. This argument displays help information. SETBOOTORDER return codes Value 0 Meaning The boot order was set successfully. SETBOOTORDER command-line examples Command-line argument SETBOOTORDER cdrom hd pxe usb floppy SETBOOTORDER default Description This command sets the system devices to boot in this order: CD-ROM drive, hard drive, PXE, USB, diskette drive. This command sets the boot order to the factory default. Using STATEMGR The STATEMGR utility enables the user to keep track of the execution state during system reboots. This utility saves persistent state information across reboots of the system. NOTE: The STATEMGR utility is not supported on 100 series servers. STATEMGR command-line syntax STATEMGR [/R | -R] [EVNAME] [/?] - or STATEMGR [/W | -W] [EVNAME] [VALUE] [/?] 18 Scripting Toolkit utilities

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

Using SETBOOTORDER

SETBOOTORDER enables you to set the order in which devices are booted, including diskette

drives, CD-ROM or DVD drives, hard drives, PXE, and USB devices. This utility sets the boot order

only for devices that exist for a server. The devices can be set to boot in any order.

SETBOOTORDER cannot be used to set the storage controller order. You must use the CONREP

utility. For more information about setting the controller order, see

“Using CONREP” (page 24)

NOTE:

Any changes made to the SETBOOTORDER take affect at the next reboot. For HP ProLiant

servers with Oxx ROM Family (most 100 series servers), only one device can be set as the boot

device and others cannot be re-ordered. These Oxx servers do not support the

default

usb

parameters.

SETBOOTORDER command-line syntax

setbootorder [floppy cdrom pxe hd usb | default] [/?]

SETBOOTORDER command-line arguments

Options are disabled if not listed in the argument.

Description

Command line argument

The order of these arguments sets the boot order for the

system devices. Each term can be used only once in any

floppy cdrom pxe hd usb

order. It is not necessary to use all terms. HP ProLiant 100

series servers can only pass in one option.

This argument resets the boot order to the factory default.

default

This argument displays help information.

SETBOOTORDER return codes

Meaning

Value

The boot order was set successfully.

SETBOOTORDER command-line examples

Description

Command-line argument

This command sets the system devices to boot in this order:

CD-ROM drive, hard drive, PXE, USB, diskette drive.

SETBOOTORDER cdrom hd pxe usb floppy

This command sets the boot order to the factory default.

SETBOOTORDER default

Using STATEMGR

The STATEMGR utility enables the user to keep track of the execution state during system reboots.

This utility saves persistent state information across reboots of the system.

NOTE:

The STATEMGR utility is not supported on 100 series servers.

STATEMGR command-line syntax

STATEMGR [/R | -R] [EVNAME] [/?]

- or -

STATEMGR [/W | -W] [EVNAME] [VALUE] [/?]

Scripting Toolkit utilities