setboot.1m (2010 09)

s
setboot(1M) setboot(1M)
IO_HW IO Hardware. When on, enables system firmware, or EFI drivers to perform all
the tests of IO hardware (boot devices only). When off, do not. Supported only
on Integrity platform.
Chipset When on, enables Chipset tests. When off, does not enable Chipset tests. Sup-
ported only on Integrity platform.
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 file, lunpath
hardware path, or legacy hardware path is given as input.
A persistent device special file is associated with a device based on its worldwide identifier, rather than
its physical hardware path. When a persistent device special file 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 file is given as input for more than one boot path,
setboot will avoid set-
ting 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 dev-
ice special file names, see intro (7).
If the hardware path written into stable storage goes offline,
setboot retrieves an alternate available
hardware path to the LUN and writes that path into stable storage. setboot supports failover by sub-
scribing 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 flags. 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 files 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 files 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 files 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.
-s onoff
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
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3