Manual

Chapter 2 Managing RAS Features and System Firmware 41
■ 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.
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:
■ 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 system configuration card (SCC) read failure.
■ Critical application-specific integrated circuit (ASIC) failure.
For more information about troubleshooting fatal errors, refer to the service manual
for your server.
Reset Scenarios
Three ILOM /HOST/diag configuration properties, mode, level, and trigger,
control whether the system runs firmware diagnostics in response to system reset
events.
The default settings for these properties are:
■ mode = normal
■ level = max
■ trigger = power-on-reset error-reset
TABLE 2-3 ILOM Property Settings for Reset Scenario
Property Value
mode normal or service
level min or max
trigger power-on-reset error-reset