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
LogicalDriveSSPState
This option is valid only for controllers that enable SSP on a logical drive basis. Other controllers
that support SSP use the SSPState option (page 42).
The following defaults apply:
• For new logical drives, the default value is Disabled.
• For existing logical drives, the default value is the current logical drive setting.
ParityGroups
When you create a RAID 50 or RAID 60 configuration, you must also set the number of parity
groups.
You can use any integer value greater than 1 for this setting, with the restriction that the total
number of physical drives in the array must be exactly divisible by the number of parity groups.
The maximum number of parity groups possible for a particular number of physical drives is the
total number of drives divided by the minimum number of drives necessary for that RAID level (three
for RAID 50, four for RAID 60).
PreferredPath
If you select the Manual setting for PreferredPathMode, use the PreferredPath command
to specify the path for I/O to the logical drive on a redundant controller in active/active mode.
The default setting for this option is 1. With this setting, the controller in chassis slot 1 is the preferred
controller for I/O to the logical drive. If you select 2, the controller in chassis slot 2 becomes the
preferred controller for the logical drive.
To determine the chassis slot numbers, use the
show
command on a controller that supports redundant controllers.
RAID
The value that you enter for this option specifies the RAID level of the logical drive.
• When the Action mode is Configure, and the Method mode is Auto, ACU automatically selects
the highest RAID level that the controller and drive configuration can support except RAID 50
or RAID 60. To specify RAID 50 or 60 for a controller that supports either of these RAID levels,
use the Custom setting. In this case, you must also specify the number of parity groups
(page 45).
• When the Action mode is Reconfigure, the default value is the existing RAID level for that
logical drive. If you specify a different RAID setting, then ACU either ignores the new setting
(when Method mode is Auto), or attempts to migrate the logical drive to the specified RAID
level (when Method mode is Custom).
Sectors
This option specifies the number of sectors that are to comprise each track. Enter 32 to disable
MaxBoot or 63 to enable it.
• For new logical drives, the default setting is 63 if the logical drive is larger than 502 GB.
Otherwise, the default setting is 32.
• For an existing logical drive, the default setting is the existing setting.
Logical drive performance is likely to decrease with MaxBoot enabled.
Using HPACUSCRIPTING 45