Table of Contents
Advertisement
To support this degraded boot capability, the OpenBoot firmware uses the 1275
client interface (by means of the device tree) to mark a device as either failed or
disabled, creating an appropriate status property in the device tree node. The Solaris
OS does not activate a driver for any subsystem marked in this way.
As long as a failed component is electrically dormant (not causing random bus
errors or signal noise, for example), the system reboots automatically and resumes
operation while a service call is made.
Once a failed or disabled device is replaced with a new one, the OpenBoot firmware
automatically modifies the status of the device upon reboot.
Note – ASR is not enabled until you activate it (see
Automatic System Recovery" on page
4.5.1
Enabling and Disabling Automatic System
Recovery
The automatic system recovery (ASR) feature is not activated until you enable it.
Enabling ASR requires changing configuration variables in ALOM as well as
OpenBoot.
4.5.1.1
To Enable Automatic System Recovery
1. At the ok prompt, type:
ok setenv auto-boot true
ok setenv auto-boot-on-error? true
2. To cause the parameter changes to take effect, type:
TABLE 4-6
ok reset-all
The system permanently stores the parameter changes and boots automatically
when the OpenBoot configuration variable auto-boot? is set to true (its default
value).
4-14
Netra CP3060 Board User's Guide • April 2009
Section 4.5.1.1, "To Enable
4-14).
Advertisement
Table of Contents
