Table of Contents
Advertisement
■
■
■
■
Note – If POST or OpenBoot firmware detects a nonfatal 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 firmware, the system does not
■
boot regardless of the settings of auto-boot? or auto-boot-on-error?. Fatal
nonrecoverable errors include the following:
■
■
■
■
■
4.5
Automatic System Recovery
Automatic system recovery (ASR) consists of self-test features and an
autoconfiguration capability to detect failed hardware components and unconfigure
them. By enabling ASR, the server is able to resume operating after certain nonfatal
hardware faults or failures have occurred.
If a component is monitored by ASR and the server is capable of operating without
it, the server automatically reboots if that component develops a fault or fails. This
capability prevents a faulty hardware component from stopping operation of the
entire system or causing the system to fail repeatedly.
If a fault is detected during the power-on sequence, the faulty component is
disabled. If the system remains capable of functioning, the boot sequence continues.
SATA subsystem failure. In this case, a working alternate path to the boot disk
is required.
Ethernet interface failure.
Serial interface failure.
Memory failure. Given a failed DIMM, the firmware will unconfigure the entire
logical bank associated with the failed module. Another nonfailing logical
bank must be present in the system for the system to attempt a degraded boot.
Any CPU 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
Chapter 4
Firmware and Blade Server Management
4-13
Advertisement
Table of Contents
