Anda di halaman 1dari 8

setboot(1M)

setboot(1M)

NAME setboot - display and modify boot variables in stable storage SYNOPSIS

setboot [-p primary-path ] [-h HA_alternate -path ] [-a alternate -path ] [-b on|off] [-s on|off] [-m on|off] [-r] [-v] [-t testname =on|off|default]... [-T testname =onoffdefault]...
DESCRIPTION The setboot command displays and sets boot variables in stable storage (also known as nonvolatile memory). Any user can display the values; only a superuser can change them. On all systems, the variables are: primary path, alternate path, HA alternate path (if applicable; see -h option), autoboot ag, and autosearch ag. If SpeedyBoot is installed, the variables expand to include: early CPU tests, late CPU tests, memory initialization (on Integrity systems), full memory tests, processor hardware tests (on PA-RISC), platform dependent tests (on Integrity systems), IO Hardware tests (on Integrity systems), chipset tests (on Integrity systems), and central electronic complex tests (on PA-RISC), hyperthreading (on some Integrity systems). With no options, setboot displays the current values for the primary boot path, alternate boot path, HA alternate boot path, and the autoboot and autosearch ags. If SpeedyBoot is installed, setboot -v also displays the status of the CPU, memory, hardware, and electronics tests. If the platform supports hyperthreading, setboot displays whether processor hyperthreading is enabled/disabled for current and subsequent system boots. SpeedyBoot The SpeedyBoot rmware and software extensions allows a superuser to control which rmware tests are executed by the system during the boot process. The tests settings can be specied both for all subsequent boots and for the next one only. They are described in the The Tests section below. The -v, -t, and -T options of the setboot command provide the user interface to the rmware tests. Currently -t options is not supported on Integrity system architecture. SpeedyBoot augments the test control that is available on systems that have the Boot Console Handler (BCH). By turning off some or all of the boot tests, you can shorten boot time appreciably. However, in the event of a system panic or boot failure, all tests are executed on the subsequent boot. SpeedyBoot Tests The SpeedyBoot tests and the possible display values on a PA-RISC platform are summarized in the following table: Test all SELFTESTS early_cpu late_cpu FASTBOOT full_memory PDH CEC Current on|off|partial on|off|partial on|off on|off on|off|partial on|off on|off on|off Supported yes|no|partial yes|no|partial yes|no yes|no yes|no|partial yes|no yes|no yes|no Default on|off|partial on|off|partial on|off on|off on|off|partial on|off on|off on|off NEXT BOOT on|off|partial on|off|partial on|off on|off on|off|partial on|off on|off on|off

The SpeedyBoot tests and the possible display values on an Integrity platform are summarized in the following table: Test all SELFTESTS early_cpu late_cpu FASTBOOT Platform Full_memory Current on|off|partial on|off|partial on|off on|off on|off|partial on|off on|off Default on|off|partial on|off|partial on|off on|off on|off|partial on|off on|off

HP-UX 11i Version 3: September 2010

Hewlett-Packard Company

setboot(1M)

setboot(1M)

Memory_init IO_HW Chipset The Columns Test Current

on|off on|off on|off

on|off on|off on|off

The keyword names of the tests that can be controlled by SpeedyBoot. See The Tests section below. The current enablement of each test. on means the test is normally executed on each boot. off means the test is normally omitted on each boot. partial means some of the subtests are normally executed on each boot. On Integrity platform any test modied using the -T option will be reected in Current. Whether the test is supported by the system rmware. yes means the test is supported. no means the test is not supported. partial means some of the subtests are supported. On Integrity platform, this Column is not supported. The default values for each test. on, off, and partial are the same as for Current. The values for each test that will be used on the next boot. If they are different from Current, the Current values will be reestablished after the next boot. on, off, and partial are the same as for Current. On Integrity platform, this Column is same as that of Current and hence not displayed separately.

Supported

Default NEXT BOOT

The Tests These are keywords for the hardware tests that are executed by processor-dependent code (PDC) or rmware upon a boot or reboot of the system.

all SELFTESTS

All the listed tests. Includes the early_cpu and late_cpu tests. This is equivalent to the SELFTESTS option in the boot console handler (BCH) service menu. The difference is that setboot can control the subtests separately, while BCH cannot. When on, run rmware, cache, and CPU-specic tests. Performed out of rmware. When off, skip the tests. When on, run rmware, cache, and CPU-specic tests. Performed out of memory and therefore faster than the early_cpu tests. When off, skip the tests. Includes the full_memory and PDH tests on PA-RISC Platform. Includes the Platform and Full_memory tests on Integrity platform. This is equivalent to the FASTBOOT option in the boot console handler (BCH) service menu. The difference is that setboot can control the subtests separately, while BCH cannot. Note: When FASTBOOT is on, the tests are performed, and vice versa.

early_cpu late_cpu

FASTBOOT

full_memory Platform Full_memory PDH CEC

When on, run write/read-write/read tests on all memory locations. When off, only initialize memory. Supported only on PA-RISC Platform. When on, enables general platform hardware tests. When off, do not. Supported only on Integrity platform. When on, enables full destructive memory tests. When off, do not. Supported only on Integrity platform. Processor-dependent hardware. When on, test a checksum of read-only memory (ROM). When off, do not. Supported only on PA-RISC Platform. Central electronic complex. When on, test low-level bus converters and I/O chips. When off, do not. CEC is not available on all systems. Supported only on PA-RISC Platform. When on, enables full destructive memory tests. When off, do not. Supported only on Integrity platform. 2 HP-UX 11i Version 3: September 2010

Memory_init
2

Hewlett-Packard Company

setboot(1M)

setboot(1M)

IO_HW

IO Hardware. When on, enables system rmware, or EFI drivers to perform all the tests of IO hardware (boot devices only). When off, do not. Supported only on Integrity platform. When on, enables Chipset tests. When off, does not enable Chipset tests. Supported only on Integrity platform.

Chipset

Hyperthreading Some Integrity processors support chip level multiprocessing which is a physical core presenting itself as two (or possibly more) logical CPUs (or hardware threads). Hyperthreading increases the instruction throughput by making use of the idle cycles and idle functional units that occur due to stalls. Supported on some Integrity platform. Failover

setboot will support boot path failover irrespective of whether a persistent device special le, lunpath
hardware path, or legacy hardware path is given as input. A persistent device special le is associated with a device based on its worldwide identier, rather than its physical hardware path. When a persistent device special le is given as input, setboot writes an available lunpath hardware path to the LUN into stable storage. Note: There is no order in which the available lunpath hardware paths get selected. Also, when the same persistent device special le is given as input for more than one boot path, setboot will avoid setting the same lunpath for the concerned boot paths. When a lunpath hardware path is given as input, setboot writes that path into stable storage. When a legacy hardware path is given as input, setboot writes the corresponding lunpath hardware path into stable storage. For more information on legacy hardware path and lunpath hardware path mapping, see ioscan (1M). For more information on Hardware Paths and Device File Naming Conventions, including persistent device special le names, see intro (7). If the hardware path written into stable storage goes ofine, setboot retrieves an alternate available hardware path to the LUN and writes that path into stable storage. setboot supports failover by subscribing to the health of the hardware path that it writes to stable storage using EVM (see EVM(5)). Options The setboot command supports the following options: (none) Display the current values for the primary, HA alternate (if applicable) and alternate boot paths and the autoboot and autosearch ags. See example 2 in the EXAMPLES: General section.

-p primary-path
Set the primary boot path variable to primary-path . setboot will accept legacy hardware paths, lunpath hardware paths, and persistent device special les as valid input (see intro (7)).

-h HA_alternate -path
Set the High Availability alternate boot path variable to HA_alternate -path . setboot will accept legacy hardware paths, lunpath hardware paths, and persistent device special les as valid input (see intro (7)). High Availability alternate boot path is supported only on Integrity system architecture and for PA-RISC systems that support hardware partitions.

-a alternate -path
Set the alternate boot path variable to alternate -path . setboot will accept legacy hardware paths, lunpath hardware paths, and persistent device special les as valid input (see intro (7)).

-r

Reinitialize the EVM subscription for boot paths currently set in stable storage. This option is useful when the boot path health event subscriptions are not updated after a change in boot paths. For example, when the boot paths are updated between an evmd stop and restart. See evmd(1M). Refer to the Failover section for more information. Enable or disable the autosearch sequence. The interpretation of Autoboot and Autosearch has changed for PA-RISC systems that support hardware partitions. Refer to the WARNINGS

-s onoff

HP-UX 11i Version 3: September 2010

Hewlett-Packard Company

setboot(1M)

setboot(1M)

section. The -s option is not supported on Integrity system architecture.

-b onoff
Enable or disable the autoboot sequence. The interpretation of Autoboot and Autosearch has changed for PA-RISC systems that support hardware partitions. Refer to the WARNINGS section.

-m onoff
Enable or disable hyperthreading. -m option is supported only on Integrity system architecture.

-v

Display the current values for the primary and alternate boot paths and the autoboot and autosearch ags and a status table of the SpeedyBoot tests. See example 1 in the EXAMPLES: SpeedyBoot section. Change the value for the test testname in stable storage to value for all following boots. -t option is not supported on Integrity system architecture. The changes are reected in the Current and NEXT BOOT columns of the setboot -v display. testname can be one of the following keywords, as described above in the DESCRIPTION: SpeedyBoot Tests section.

-t testname =value

all
SELFTESTS early_cpu late_cpu FASTBOOT full_memory PDH CEC
value can be one of:

on off default -T testname =value

Enable the test. Disable the test. Reset the test to the system default, which is shown in the Defaults column of the setboot -v display.

Change the value for the test testname to value for the next system boot only. The change does not modify stable storage, so the permanent values are restored after the boot.

s
0 1

testname can be one of the keywords described above in the DESCRIPTION: SpeedyBoot Tests section. and value are the same as for the -t option. RETURN VALUE The setboot command returns one of: Successful completion Failure

DIAGNOSTICS The setboot command returns the following error messages:

"bootpath " is not a valid bootpath. Bootpaths should be specified with a persistent dsf, lunpath hardware path or a legacy hardware path.
The boot path, bootpath , should be one of the following: persistent LUN dsf, lunpath hardware path or legacy hardware path. See ioscan (1M) and intro(7) for more information on hardware path and persistent dsf format.

cannot open /dev/kepd - message setboot cannot open the kernel pseudo driver le /dev/kepd. The message explains why. cannot set autoboot/autosearch flags
The autoboot or autosearch ag could not be set.

cannot set type boot path


4 Hewlett-Packard Company 4 HP-UX 11i Version 3: September 2010

setboot(1M)

setboot(1M)

setboot cant set the specied boot path. type may be primary, HA_alternate, or alternate. error accessing boot path - message
The message explains why. For example, you may not have permission (not be superuser) to change parameters.

error accessing firmware - message


The rmware could not be read or written. The message explains why.

Failed to retrieve lun token


An error occurs when one of the boot paths is invalid (when running setboot -r or /sbin/init.d/setboot). This kind of error occurs when there is no valid LUN entry corresponding to the boot path or lunpath.

No dsf found
An error occurs while displaying boot paths when there is no valid LUN entry corresponding to the boot path. For example, one or more of these situations has occurred regarding the persistent LUN dsf entry: The persistent LUN dsf corresponding to the boot path (lunpath in stable storage) has been removed (most likely with the rmsf command). The boot path is set to a lunpath, but the associated HBA to that lunpath has been removed or disabled. The boot path is set to a non-existent or invalid boot device in the I/O system. The session is run by non-privileged user, while some drivers require superuser privileges.

Invalid Arguments Passed to the invoked PDC routine


This is an internal error.

test not found in /etc/setboot_tests file


The test you specied is not dened for your system.

The firmware of your system does not support querying or changing SELFTEST and FASTBOOT settings except through the boot-time console interface, ie, BCH menu. Invoked PDC routine [option] not implemented. (On PA-RISC Platform
only.)

or The firmware of your system does not support querying or changing the SpeedyBoot settings. (On Integrity platform only.)
You have specied a SpeedyBoot option (-t, -T, or -v) and your system does not have the rmware to support SpeedyBoot. Currently, the Integrity platform does not support -t options.

Unknown error errno encountered by setboot(1M)


An unexpected error, number errno , was encountered while setboot was updating boot variable.

Warning: Autoboot flag must be on for autosearch flag to have effect


If the autoboot ag is off, automatic searching for a bootable system cannot occur, even if the autosearch ag is on.

warning: invalid data in /etc/setboot_tests


The /etc/setboot_tests le contains tests that are not supported by setboot on your system. Do not modify this le. EXAMPLES General 1. Set the primary path to 2/4.1.0 and enable the autoboot sequence:

setboot -p 2/4.1.0 -b on
2. Set the alternate path (using a persistent device special le) to /dev/disk/disk2 and enable the autoboot sequence: 5 Hewlett-Packard Company 5

HP-UX 11i Version 3: September 2010

setboot(1M)

setboot(1M)

setboot -a /dev/disk/disk2 -b on setboot displays: Alternate boot path set to 0/0/0/3/0.0x6.0x0 (/dev/disk/disk2)
3. Display the boot paths, auto ags and hyperthreading:

setboot
on PA-RISC and Integrity system architecture displays:

Primary bootpath : 0/0/0/3/0.0x5.0x0 (/dev/rdisk/disk3) HA Alternate bootpath : 0/0/0/3/0.0x6.0x0 (/dev/rdisk/disk2) Alternate bootpath : 0/0/0/3/0.0x6.0x0 (/dev/rdisk/disk2) Autoboot is ON (enabled) Autosearch is ON (enabled)
on Integrity system architecture which support hardware threads displays:

Primary bootpath : 0/3/2/0.0x50001fe15002c7f9.0x4001000000000000 (/dev/rdisk/disk7) HA Alternate bootpath : 0/1/1/1.0x0.0x0 (/dev/rdisk/disk10) Alternate bootpath : 0/1/1/0.0x1.0x0 (/dev/rdisk/disk9) Autoboot is ON (enabled) Hyperthreading : ON : ON (next boot)
SpeedyBoot 1. Display all current stable storage values.

setboot -v
on PA-RISC architecture displays:

Primary bootpath : 0/0/0/3/0.0x5.0x0 (/dev/rdisk/disk3) HA Alternate bootpath : 0/0/0/3/0.0x6.0x0 (/dev/rdisk/disk2) Alternate bootpath : 0/0/0/3/0.0x6.0x0 (/dev/rdisk/disk2) Autoboot is ON (enabled) Autosearch is OFF (disabled)

TEST ---all SELFTESTS early_cpu late_cpu FASTBOOT full_memory PDH CEC

CURRENT ------partial partial off on partial off on off

SUPPORTED --------partial yes yes yes yes yes yes no

DEFAULT ------partial on on on on on on off

NEXT BOOT --------partial partial off on partial off on off

on Integrity system architecture displays:

Primary bootpath : 0/1/1/0.0x1.0x0 (/dev/rdisk/disk9) HA Alternate bootpath : 0/1/1/1.0x0.0x0 (/dev/rdisk/disk10) Alternate bootpath : 0/1/1/1.0x0.0x0 (/dev/rdisk/disk10) Autoboot is ON (enabled) TEST ---all SELFTESTS early_cpu late_cpu
6 Hewlett-Packard Company

CURRENT ------partial off off off

DEFAULT ------partial on on on
6 HP-UX 11i Version 3: September 2010

setboot(1M)

setboot(1M)

FASTBOOT Platform Full_memory Memory_init IO_HW Chipset


2.

on on on on off on

on on on on off on

Enable full_memory and PDH tests and have those tests executed on all subsequent reboots.

setboot -t FASTBOOT=on
3. Disable the late processor tests and have those tests skipped on all subsequent reboots. If early CPU tests are on when this command is executed, the SELFTESTS state in BCH stays on while setboot -v shows the state as partial.

setboot -t late_cpu=off
4. Reset all tests to the machine-shipped default values.

setboot -t all=default
5. Reset only the FASTBOOT (full_memory and PDH) tests to their default values.

setboot -t FASTBOOT=default
6. Cause the early and late CPU tests to be executed on the next system boot. The previously set test values take effect again after the single boot.

setboot -T SELFTESTS=on
7. Cause all tests to be skipped on the next reboot. The previously set test values will take effect for subsequent reboots.

setboot -T all=off
8. Enable hyperthreading for next system boot.

setboot -m on
WARNINGS The setboot command fails under the following circumstances: On Integrity systems, a device cannot be set as a boot path if the device does not have an EFI partition. The number of writes to the stable storage exceeds the number allowed by the architecture implementation. Hardware failure. The implementation does not have memory for the alternate boot path, in which case, this variable is neither readable nor writable.

Autoboot and Autosearch on PA-RISC Systems The interpretation of Autoboot and Autosearch has changed for PA-RISC systems that support hardware partitions. The rmware interprets the bits in combination and not individually as done before. In order to approximate the traditional behavior of setboot, the user input for the autoboot and autosearch ags is internally mapped to the right combination to achieve the desired behavior. This mapping should be transparent to the user of setboot, but might show up when accessing the rmware using means other than setboot. For the primary path, the boot action corresponds to the Autoboot and Autosearch ags in the following manner: AutoBoot off on on AutoSearch off off on Boot Action Go to the BCH and prompt the user. Attempt the primary path; on failure go to BCH. Attempt the primary path; on failure

HP-UX 11i Version 3: September 2010

Hewlett-Packard Company

setboot(1M)

setboot(1M)

off

on

try next path. Skip the primary path and try alternate path. If the alternate paths are not congured to boot or fail, go to BCH.

Additionally, systems with hardware partitions support a boot action for each path. However the boot action for the paths other than the primary path cannot be set using setboot. Instead, these must be set through the Boot Console Handler using the pf (path ags) command of the BCH Conguration menu. The default boot action for the hardware partitions is to "skip this device and try next path". The case where both the autosearch and autoboot ags are on, will not work as expected until the path ags for the alternate paths are set appropriately through the BCH. In the default case, specifying setboot -b on -s on will not cause an alternate path to be automatically booted when the primary path fails, instead the user will be prompted. DEPENDENCIES If SpeedyBoot is not installed on a system, options -v, -t, and -T will produce a diagnostic error. Currently -t option is not supported on Integrity system architecture. If the platform does not support hyperthreading, then the -m option will produce a diagnostic error. AUTHOR

setboot was developed by HP.


FILES

/dev/kepd

Special device le used by the setboot command. Secondary EVM logger conguration les for setboot.

/var/evm/adm/config/logger/setboot*.conf /etc/setboot_tests
Denitions of tests which can be viewed or controlled with the -v, -t, and -T options.

SEE ALSO evmlogger(1M), evmreload(1M), hpux(1M), ioscan(1M), isl(1M), mkboot(1M), EVM(5), intro(7), errno(2).

Hewlett-Packard Company

HP-UX 11i Version 3: September 2010

Anda mungkin juga menyukai