Filter
Top Products
4-6 Netra CP3260 Blade Server User’s Guide • April 2009
4.3.2 Auto-Boot Options
The system firmware stores a configuration variable called auto-boot?, which
controls whether the firmware will automatically boot the operating system after
each reset. The default setting for Sun platforms is true.
Normally, if a system fails power-on diagnostics, auto-boot? is ignored and the
system does not boot unless an operator boots the system manually. An automatic
boot is generally not acceptable for booting a system in a degraded state. Therefore,
the Netra CP3260 server OpenBoot firmware provides a second setting,
auto-boot-on-error?. This setting controls whether the system will attempt a
degraded boot when a subsystem failure is detected. Both the auto-boot? and
auto-boot-on-error? switches must be set to true to enable an automatic
degraded boot. To set the switches, type:
Note – The default setting for auto-boot-on-error? is false. The system will
not attempt a degraded boot unless you change this setting to true. In addition, the
system will not attempt a degraded boot in response to any fatal nonrecoverable
error, even if degraded booting is enabled. For examples of fatal nonrecoverable
errors, see Section 4.3.4, “OpenBoot Configuration Variables” on page 4-12.
4.3.3 OpenBoot Commands
You type the OpenBoot commands at the ok prompt. The OpenBoot commands that
can provide useful diagnostic information include:
■ probe-scsi and probe-scsi-all
■ probe-ide
■ show-devs
For a complete list of OpenBoot commands and more information about the
OpenBoot firmware, refer to the OpenBoot 4.x Command Reference Manual. An online
version of the manual is included with the OpenBoot Collection AnswerBook that
ships with Solaris software.
{0} ok setenv auto-boot? true
{0} ok setenv auto-boot-on-error? true