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

Страница: 146 / 236

128 Sun Fire 880 Server Owner’s Guide • August 2001
■
Serial interface failure
■
PCI card failure
■
CPU failure – In this case, a single CPU failure causes the entire CPU/Memory
board to be deconfigured. Another non-failing CPU/Memory board must be
present in the system for the system to attempt a degraded boot.
■
Memory failure – Given a failed memory module, the firmware will
deconfigure the entire logical bank associated with the failed module. Another
non-failing logical bank must be present in the system for the system to
attempt a degraded boot.
Note – If POST or OpenBoot Diagnostics detects a non-fatal error associated with
the normal boot device, the OpenBoot firmware automatically deconfigures the
failed device and tries the next-in-line boot device, as specified by the
boot-device
configuration variable.
3. If a fatal error is detected by POST and/or OpenBoot Diagnostics, the system will
not boot regardless of the settings of
auto-boot?
or
auto-boot-on-error?
.
Fatal non-recoverable errors include the following:
■
All CPUs failed
■
All logical memory banks failed
■
Flash RAM cyclical redundancy check (CRC) failure
■
Critical FRU PROM configuration data failure
■
Critical application specific integrated circuit (ASIC) failure
Reset Scenarios
Two OpenBoot NVRAM configuration variables,
diag-switch?
and
diag-trigger
, control whether the system runs firmware diagnostics in response
to system reset events.
The standard system reset protocol bypasses POST and OpenBoot Diagnostics
completely unless the variable
diag-switch?
is set to
true
. The default setting for
this variable is
false
. Therefore to enable ASR, which relies on firmware
diagnostics to detect faulty devices, you must change this setting to
true
.