Reset Scenarios; To Enable Asr - Sun Microsystems Fire V240 Administration Manual

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 how the system runs firmware diagnostics in response to
system reset events.
The standard system reset protocol bypasses POST and OpenBoot Diagnostics unless
diag-switch? is set to true. The default setting for this variable is false. Because
ASR relies on firmware diagnostics to detect faulty devices, diag-switch? must
be set to true for ASR to run. For instructions, see "To Enable ASR" on page 83.
To control which reset events, if any, automatically initiate firmware diagnostics, use
obdiag-trigger and post-trigger. For detailed explanations of these variables
and their uses, see "Controlling POST Diagnostics" on page 58 and "Controlling
OpenBoot Diagnostics Tests" on page 61.

To Enable ASR

1. At the system ok prompt, type:
ok setenv diag-switch? true
ok setenv auto-boot? true
ok setenv auto-boot-on-error? true
Chapter 6 Diagnostics 83