Table 13 Basic Low End Troubleshooting
(continued)
Action
Condition
Step
4. As a last resort, replace the server blade. Preceding
problem is fixed when all boot paths are found.
Nothing may be logged for this condition.
Cannot see OS prompt on system console. BMC
and iLO 2 MP are running.
5
1. Examine the iLO 2 MP logs for entries related to
processors, processor power modules (PPM)s, and shared
memory, and core I/O devices (see
“Errors and Error Logs”
(page 98)
). Preceding problem is fixed when the OS
prompt appears on the system console.
Table 14 Advanced Low End Troubleshooting
Action
Symptom/Condition
Step
System event logging has stopped and a BMC malfunction is assumed
(health is steady green and power is steady green).
Cannot read System Event Log
from the system console.
6
1. Examine console messages for any EFI errors or warnings about BMC
operation or communications.
2. Test the operation of the BMC by toggling the UID locator LED on the
front panel -- the blue LED is turned On/Off by the BMC through the
system console.
Preceding problem is fixed when the System Event Log resumes logging.
Front panel LEDs indicate that the server blade’s power is turned on,
and it is either booting or running the OS (for example, health is steady
green and power is steady green).
OS is non-responsive (hung)
7
Nothing may be logged for this condition.
1. Use the system console to start a system initialization, or push the Init
(ToC) pinhole button on the front of the server blade.
2. Reboot the OS and escalate.
3. Obtain the system hardware status dump for root cause analysis.
4. Examine the iLO 2 MP logs for entries related to processors, processor
power modules (PPMs), shared memory, and core I/O devices (see
“Errors and Error Logs” (page 98)
).
The preceding problem is fixed when the root cause is determined.
Front panel LEDs indicate that the server blade detected a fatal error
that it cannot recover from through OS recovery routines (for example,
health is flashing red and power is steady green).
MCA occurs during server blade
operation; the server blade
reboots the OS.
8a
1. Capture the MCA dump with the EFI command,
errdumpmca
. If the
server blade can boot the OS, you can capture binary MCA dump files
online.
Note:
Server blade reboots OS if
enabled.
2. Examine the iLO 2 MP logs for entries related to processors, processor
power modules (PPMs), shared memory, and core I/O devices (See
“Errors and Error Logs” (page 98)
).
Preceding problem 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 blade detected a fatal, front
side bus error, caused by MBEs reading cache or DIMM; or by any
MCA occurs during server blade
operation; server blade reboot of
OS is prevented.
8b
parity in the I/O path between SBA, LBA, or HBA (for example, health
is Off Power is Steady Green).
Note:
The troubleshooting actions
for this step are identical to those System firmware is running to gather and log all error data for this MCA
event.
in Step 8a, except that the server
blade in this step must be hard
1. Examine the iLO 2 MP logs for entries related to processors, processor
power modules (PPMs), shared memory, and core I/O devices (see
“Errors and Error Logs” (page 98)
).
reset to begin the booting
process.
90
Troubleshooting
