Sun Microsystems Netra CP3060, Руководство пользователя

Страница: 62 / 129

Chapter 4 Firmware and Blade Server Management 4-5
Caution – Obtaining the
ok
prompt suspends all application and operating system
software. After you issue firmware commands and run firmware-based tests from
the
ok
prompt, the system might not be able to resume where it left off.
If possible, back up system data before starting accessing the
ok
prompt. Also exit or
stop all applications, and warn users of the impending loss of service. For
information about the appropriate backup and shutdown procedures, see Solaris
system administration documentation.
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 Sun Netra CP3060 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
“OpenBoot Configuration Variables” on page 9 .
4.3.3 OpenBoot Commands
You type the OpenBoot commands at the
ok
prompt. Two of the OpenBoot
commands that can provide useful diagnostic information include:
■ probe-ide
ok setenv auto-boot? true
ok setenv auto-boot-on-error? true