6 Troubleshooting
The purpose of this chapter is to provide a preferred methodology (strategies and procedures) and
tools for troubleshooting the server error and fault conditions.
How to contact HP
For information on how to contact HP, see
Methodology
General troubleshooting methodology
There are multiple entry points to the troubleshooting process, dependent upon your level of
troubleshooting expertise, the tools/processes/procedures which you have at your disposal, and
the nature of the system fault or failure.
Typically, you select from a set of symptoms, ranging from very simple (system LED is blinking) to
the most difficult (Machine Check Abort (MCA) has occurred. The following is a list of symptom
examples:
NOTE:
Your output might differ from the output in the examples in this book depending on your
server and its configuration.
•
Front panel LED blinking
•
System alert present on console
•
System will not power-up
•
System will not boot
•
Error/Event Message received
•
Machine Check Abort (MCA) occurred
Narrow down the observed issue to the specific troubleshooting procedure required. Isolate the
failure to a specific part of the server, so you can perform more detailed troubleshooting. For
example:
•
Issue- Front panel LED blinking
NOTE:
The front panel health LEDs flash amber with a warning indication, or flash red with
a fault indication.
◦
System Alert on console?
Analyze the alert by using the system event log (SEL) and forward progress log (FPL), to
identify the last error logged by the server. Use the iLO 3 MP commands to view the SEL
and FPL, either through the iLO 3 MP serial text interface, or through Secure Shell, or
through the web GUI on the iLO 3 MP LAN.
You can now determine which area of the system requires further analysis. For example, if the
symptom was "system will not power-up", the initial troubleshooting procedure might indicate a
issue with the DC power rail not coming up after the power switch was turned on.
You have now reached the point where the failed CRU has been identified and needs to be
replaced. Perform the specific removal and replacement procedure, and verification steps.
NOTE:
If multiple CRUs are identified as part of the solution, a fix cannot be guaranteed unless
all identified failed CRUs are replaced.
HP Confidential
How to contact HP
59
