Sun Microsystems Sun Fire V480, Administration Manual

Page: 93 / 270

Chapter 4 Network Interfaces and System Firmware 65
■
If only non-fatal errors are detected by POST or OpenBoot Diagnostics, the
system attempts to boot if
auto-boot?
is
true
and
auto-boot-on-error?
is
true
. Non-fatal errors include the following:
■
FC-AL subsystem failure – In this case, a working alternate path to the boot
disk is required. For more information, see “About Multipathing Software” on
page 69.
■
Ethernet interface failure
■
USB interface failure
■
Serial interface failure
■
PCI card failure
■
CPU failure – In this case, a single CPU failure causes the entire CPU/Memory
board to be unconfigured. 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
unconfigure 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 unconfigures the
failed device and tries the next-in-line boot device, as specified by the
boot-device
configuration variable.
■
If a fatal error is detected by POST 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 field-replaceable unit (FRU) PROM configuration data failure
■
Critical application-specific integrated circuit (ASIC) failure
Reset Scenarios
Three OpenBoot configuration variables,
diag-switch?
,
obdiag-trigger
, and
post-trigger
, control whether the system runs firmware diagnostics in response
to system reset events.