An auto-configuring capability designed into the OpenBoot firmware enables the system to unconfigure failed components and to restore system operation. As long as the system is capable of operating without the failed component, the ASR features enable the system to reboot automatically, without operator intervention.
Note – ASR is not activated until you enable it. See “Enabling and Disabling Automatic System Recovery” on page 44.
For more information about ASR, refer to the Netra 440 Server Diagnostics and Troubleshooting Guide (817-3886-xx).
Auto-Boot Options
The OpenBoot firmware stores a configuration variable on the system configuration card (SCC) called auto-boot?, which controls whether the firmware will automatically boot the operating system after each reset. The default setting for Sun platforms is true.
Normally, if a system fails power-on diagnostics, auto-boot?is ignored and the system does not boot unless an operator boots the system manually. A manual boot is obviously not acceptable for booting a system in a degraded state. Therefore, the Netra 440 server OpenBoot firmware provides a second setting, auto-boot-on-error?. This 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?switches must be set to true to enable an automatic degraded boot. To set the switches, type:
ok setenv auto-boot? true
ok setenv auto-boot-on-error? true
Note – The default setting for auto-boot-on-error?is false. Therefore, the system will not attempt a degraded boot unless you change this setting to true. In addition, the system will not attempt a degraded boot in response to any fatal nonrecoverable error, even if degraded booting is enabled. For examples of fatal nonrecoverable errors, see “Error Handling Summary” on page 43.
42 Netra 440 Server System Administration Guide • August 2004
