Sun Microsystems 440 manual Error Handling Summary

Error Handling Summary

Error handling during the power-on sequence falls into one of the following three cases:

■If no errors are detected by POST or OpenBoot Diagnostics, the system attempts to boot if auto-boot?is true.

■If only nonfatal errors are detected by POST or OpenBoot Diagnostics, the system attempts to boot if auto-boot?is true and auto-boot-on-error?is true. Nonfatal errors include the following:

■Ultra-4 SCSI subsystem failure. In this case, a working alternate path to the boot disk is required. For more information, see “Multipathing Software” on page 50.

■Ethernet interface failure.

■USB interface failure.

■Serial interface failure.

■PCI card 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. For more information, refer to the Netra 440 Server Product Overview (817-3881- xx).

Note – If POST or OpenBoot Diagnostics 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 diag-deviceconfiguration variable.

■If a fatal error is detected by POST or OpenBoot Diagnostics, 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 Netra 440 Server Diagnostics and Troubleshooting Guide (817-3886-xx).

Chapter 2 Managing RAS Features and System Firmware 43