Download Netra 440 Server Diagnostics and Troubleshooting Guide

13. Check the system’s recent service history.
A system that has had several recent Fatal Reset errors and subsequent FRU
replacements should be monitored closely to determine whether the recently
replaced parts were, in fact, not faulty, and whether the actual faulty hardware has
gone undetected.
Troubleshooting a System That Does Not
Boot
A system might be unable to boot due to hardware or software problems. If you
suspect that the system is unable to boot for software reasons, refer to
“Troubleshooting Miscellaneous Software Problems” in the Solaris System
Administration Guide: Advanced Administration. If you suspect the system is unable to
boot due to a hardware problem, use the following procedure to determine the
possible causes.
This procedure assumes that the system console is in its default configuration, so
that you are able to switch between the system controller and the system console.
Refer to the Netra 440 Server System Administration Guide.
1. Log in to the system controller and access the sc> prompt.
For information, refer to the Netra 440 Server System Administration Guide.
2. Examine the ALOM event log. Type:
sc> showlogs
The ALOM event log shows system events such as reset events and LED indicator
state changes that have occurred since the last system boot. To identify problems,
examine the output for Service Required LEDs that are ON. CODE EXAMPLE 7-31
shows a sample event log, which indicates that the front panel Service Required LED
is ON.
Chapter 7
Troubleshooting Hardware Problems
141