Sun Fire V445 Server Administration Guide - SCN Research

If a fault occurs on a running server, and it is possible for the server to run without
the failed component, the server automatically reboots. This prevents a faulty
hardware component from keeping the entire system down or causing the system to
crash repeatedly.
To support such a degraded boot capability, the OpenBoot firmware uses the 1275
Client Interface (via the device tree) to mark a device as either failed or disabled, by
creating an appropriate status property in the device tree node. The Solaris OS will
not activate a driver for any subsystem so marked.
As long as a failed component is electrically dormant (not causing random bus
errors or signal noise, for example), the system will reboot automatically and resume
operation while a service call is made.
Note – ASR is enabled by default.
Auto-Boot Options
The OpenBoot firmware stores configuration variables on a ROM chip called autoboot?
and auto-boot-on-error? The default setting on the Sun Fire V445 server
for both of these variables is true.
The auto-boot? setting controls whether or not the firmware automatically boots
the OS after each reset. The auto-boot-on-error? 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? settings must be set to true (default) to
enable an automatic degraded boot.
▼
To Set the Auto-Boot Switches
1. Type the following commands:
ok setenv auto-boot? true
ok setenv auto-boot-on-error? true
Note – With both of these variables set to true, the system attempts a degraded
boot in response to any fatal nonrecoverable error.
196 Sun Fire V445 Server Administration Guide • August 2006