setboot Command

setboot has been enhanced to provide support for setting the High Availability (HA) Alternate boot path using a new option -h.

The SpeedyBoot firmware and software extensions allow a superuser to control which firmware tests are executed by the system during the boot process. Formerly, the setboot command could only be used to set these firmware tests on a PA-RISC platform. Now, however, setboot has been enhanced to support the setting of a firmware test for the next boot on the Itanium®-based platform.

setboot has been enhanced to enable or disable hyperthreading environment for the next boot on a Dual-Core Intel® Itanium® 2 platform. The following new option has been added to enable/disable hyperthreading environment:

setboot has been modified to accept a persisent device special file (dsf) as input. setboot selects then any lunpath hardware path currently available to the corresponding LUN and writes it to stable storage for use as the bootpath at next boot. setboot also accepts a lunpath hardware path as input, in which case it writes that lunpath hardware path to stable storage.

To maintain backwards compatibility, setboot continues to accept a legacy hardware path as input. However, the path stored in stable storage is no longer the legacy hardware path itself but is the corresponding lunpath hardware path. If the path stored in stable storage happens to fail later, setboot will be notified via an EVM event and will automatically select an alternate available path to the LUN and reconfigure it to stable storage, regardless if it was setup via a persistent dsf, or via a lunpath or legacy hardware path.

setboot has been enhanced to enable or disable hyperthreading environment for the next boot on a Dual-Core Intel® Itanium® 2 platform. The following new option has been added to enable/disable hyperthreading environment:

setboot has been modified to accept a persisent device special file (dsf) as input. setboot selects any lunpath hardware path currently available to the corresponding LUN and writes it to stable storage for use as the bootpath at next boot. setboot also accepts a lunpath hardware path as input, in which case it writes that lunpath hardware path to stable storage.

To maintain backwards compatibility, setboot continues to accept a legacy hardware path as input. However, the path stored in stable storage is no longer the legacy hardware path itself but is the corresponding lunpath hardware path. If the path stored in stable storage happens to fail later, setboot will be notified via an EVM event and will automatically select an alternate available path to the LUN and reconfigure it to stable storage, regardless if it was setup via a persistent dsf, or via a lunpath or legacy hardware path.