Symptom information checklist
Before troubleshooting a server issue, collect the following symptom information:
- Does the server power on?
- Does the server complete POST?
- If the server does not complete POST, what is the status and behavior of each of the server LEDs?
- Is video display available?
- If server completes POST and video is available, are there any POST error messages? Record the text of the POST error message as displayed.
-
Does the
server successfully boot an operating system or hypervisor? If not, does the
server display any of the following symptoms and at what point did the following symptom occur?
An uncorrectable machine check exception
Stop error or blue screen (Windows)
Purple diagnostic screen (Linux)
Linux kernel panic
A system “hang”
A system “freeze”
- Does the issue occur after an OS is installed?
- Does the issue occur when a new application is loading?
-
What symptoms did the
server display when the
server malfunctioned?
For example, did the server reboot? Were there LED codes, health logs, or messages displayed on the screen?
-
Are any indications present that show that the malfunction was reported as a memory error, PCI error, or so forth?
The processor now contains the memory controller and PCI Express controller, so faults in other areas might be attributed to a processor malfunction.
-
When did the issue occur?
Record exactly when the issue happens (include the date and time). If it happens more than once, keep a list of all symptoms for each occurrence.
- What events preceded the failure? After which steps does the issue occur?
- What has been changed since the time the server was working?
-
Has hardware or software been recently added or removed?
If yes, were the appropriate settings in the server setup utility changed?
- How long has the server exhibited issue symptoms?
- If the issue occurs randomly, what is the duration or frequency of the issue?
- What failed based on the iLO Event Log or the IML?