Table 40 Advanced Entry Class Troubleshooting
(continued)
Action
Symptom/Condition
Step
Preceding problem is fixed when BMC’s Heartbeat LED is Flashing Green,
and the System Event Log 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, internal health
is steady green, external health is steady green, and power is steady green).
Nothing may be logged for this condition.
OS is non-responsive (hung).
7
1.
Reset the system using one of the following methods:
a.
Use the iLO 2 MP to reset the system:
•
From the command menu of text interface via SSH or Telnet, use
the
TC
command.
•
From the web GUI,
Reset through INIT or TOC signal
from the
Power & Reset
menu on the
Virtual Devices
tab.
For more information see the HP Integrity iLO 2 Operations Guide.
b.
Use a tool (such as a ACX-10 Torx screwdriver or appropriately size
allen wrench) to depress the INIT button on the front panel to start
system initialization.
2.
Reboot the OS.
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 Reading Error Logs” (page 149)
for information.
The problem is fixed when the root cause has been determined, and the
OS is running normally.
Front panel LEDs indicate the server detected a fatal error that it cannot
recover from using OS recovery routines (for example, System Health is
MCA occurs during server
operation; the server reboots the
OS.
NOTE:
Server reboots OS, if
enabled.
8a
Flashing Red, Internal Health is Steady Green, External Health is Steady
Green, and Power is Steady Green).
1.
Capture the MCA dump with the EFI command,
errdumpmca
. If the
system can boot the OS, you can capture binary MCA dump files online.
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 Reading Error Logs” (page 149)
).
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 detected a fatal, front side bus
error, caused by MBEs reading cache or DIMM; or by any parity in the
MCA occurs during server
operation; server reboot of OS is
prevented.
NOTE:
The 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)
NOTE:
You must hard reset the
server to clear the fatal condition
and boot the OS.)
8b
I/O path between SBA, LBA, or HBA (for example, System Health is Off,
Internal Health is Flashing Amber, External Health is Steady Green, Power
is Steady Green). System firmware is running to gather and log all error
data for this MCA event.
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 Reading Error Logs” (page 149)
).
Preceding problem is fixed when the MCA does not repeat.
Methodology
141
