Table 13 Advanced low end troubleshooting
Action
Symptom/Condition
Step
System event logging has stopped and a iLO MP malfunction is assumed
(system health is steady green, and power is steady green).
Cannot read System Event Log
from the iLO console.
6
1. Examine console messages for any UEFI errors or warnings about iLO
operation or communications.
2. Test the operation of the iLO MP by toggling the UID locator switch
LED on the front panel -- the blue LED is turned on/off by the iLO, when
this switch is toggled.
3. Reset iLO 3 MP, by using the iLO 3 physical presence pinhole button
on the rear panel of the server.
The preceding issue is fixed when the SEL resumes logging.
Front panel LEDs indicate that the server power is turned on, and it is
either booting or running the OS (system health is steady green, and
power is steady green). Nothing might be logged for this condition.
1. Use the iLO 3 MP Command Menu to initiate a ToC, using the
tc
command.
OS is non-responsive (hung).
7
2. Reboot the OS and escalate.
3. Obtain the system hardware status dump for root cause analysis.
4. Examine the iLO 3 MP logs for entries related to processors, processor
power modules (PPMs), shared memory, and core I/O devices (see
and reading error logs” (page 73)
for details).
The preceding issue is fixed when the root cause has been determined.
Front panel LEDs indicate that the server detected a fatal error that it
cannot recover from through OS recovery routines (system health is
flashing red, SEL is red, and power is steady green).
1. Capture the MCA dump with the UEFI
errdump mca
command. If
the system can boot the OS, you can capture binary MCA dump files
online.
MCA occurs during server
operation; the server reboots the
OS. (NOTE: Server reboots OS,
if enabled)
8a
2. Examine the iLO 3 MP logs for entries related to processors, processor
power modules (PPMs), shared memory, and core I/O devices (see
and reading error logs” (page 73)
for more details).
The preceding issue is fixed when the MCA does not repeat, or the source
of the MCA has been determined and dealt with.
Front panel LEDs indicate that the server detected a fatal, front side bus
error, caused by DIMMs; or by any parity in the I/O path between SBA,
MCA occurs during server
operation; server reboot of OS
8b
LBA, or HBA (system health is flashing red, SEL is red, power is steady
is prevented. NOTE: The
green). System firmware is running to gather and log all error data for
this MCA event.
1. Examine the iLO 3 MP logs for entries related to processors, processor
power modules (PPMs), shared memory, and core I/O devices (See
“Errors and reading error logs” (page 73)
for details).
troubleshooting actions for this
step are identical to those in
Step 8a, except that the server
in this step must be hard reset
to begin the booting process
The preceding issue is fixed when the MCA does not repeat.
You must hard reset the server
to clear the fatal condition and
boot the OS
Troubleshooting tools
Use the following tools to aid in troubleshooting the server.
HP Confidential
64
Troubleshooting
