Methodology; General Troubleshooting Methodology - HP Integrity rx6600 User's & Service Manual

Troubleshooting

Methodology

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, for example, MCA, has occurred). The following is a list of symptom
examples:
• Front Panel LED blinking
• System Alert present on console
• System won't power-up
• System won't boot
• Error/Event Message received
• Machine Check Abort (MCA) occurred
If an MCA has occurred, call HP for advanced troubleshooting assistance.
NOTE
Next, you narrow down the observed problem to the specific troubleshooting procedure required. Here, you
isolate the failure to a specific part of the server, so that you can perform more detailed troubleshooting. For
example:
• Problem- Front Panel LED blinking
The Front Panel Health LEDs will be flashing amber with a warning indication, or flashing
NOTE
red with a fault indication.
— System Alert on console?
— Analyze the alert by using the system event log (SEL), to identify the last error logged by the server.
Use the iLO 2 MP commands to view the SEL, using either the iLO 2 MP's serial text interface, or
telnet, SSH, or Web GUI on the iLO 2 MP LAN.
At this point, you will have a good idea about which area of the system requires further analysis. For example,
if the symptom was "system won't power-up", the initial troubleshooting procedure may have indicated a
problem with the dc power rail not coming up after the power switch was turned on.
You have now reached the point where the failed Field Replaceable Unit (FRU or FRUs) has been identified
and needs to be replaced. You must now perform the specific removal and replacement procedure, and
verification steps. See Chapter 4, "Removal and Replacement," on page 53 for information.
If multiple FRUs are identified as part of the solution, a fix cannot be guaranteed unless all
NOTE
identified failed FRUs are replaced.
150
Chapter 5