![](/images/new-backgrounds/1285121/285121167x1.webp)
Table 10 Advanced Low End Troubleshooting (continued)
Step | Symptom/Condition | Action |
3.Use the following commands to obtain the system hardware status by capturing the logs.
•sl -e -nc
•l
•df -d
•ps
•ss
•sr
•sysset
•npar
•UEFI info all
•VFP
8a | MCA occurs during server blade |
| operation. The server blade |
| reboots the OS. |
Note: The server blade reboots
OS if enabled.
8b | MCA occurs during server blade |
| operation and it is repeated; |
| server blade reboot of OS is |
| prevented. |
Note: The troubleshooting actions for this step are identical to those in Step 8a, except that the server blade in this step must be hard reset to begin the booting process.
4.Examine the iLO 3 MP logs for entries related to processors, processor power modules, shared memory, and core I/O devices (see “Errors and error logs” (page 93) for more details).
This issue 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).
1.Capture the MCA dump with the UEFI command, errdump mca. If the server blade can boot the OS, you can capture binary MCA dump files online.
2.Examine the iLO 3 MP logs for entries related to processors, processor power modules, shared memory, and core I/O devices (See “Errors and error logs” (page 93) for more details).
The issue is fixed when the MCA does not repeat or the source of the MCA has been eliminated.
Front panel LEDs indicate that the server blade detected a fatal, front side bus error.
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, shared memory, and core I/O devices (see “Errors and error logs” (page 93)for more details).
If the system repeats the MCA, it is unable to capture MCA dumps since the system is unable to boot to UEFI shell. Reduce the system configuration and try the boot with the minimum configuration. For the i4 server blades, you may need to manage the nPar configuration for the minimum configuration.
2.Try dc power off/on.
3.Try reseating the blades.
This issue is fixed when the MCA does not repeat.
Troubleshooting tools
The HP Integrity BL860c i4 Server Blade uses LEDs and other tools to help troubleshoot problems that occur in the server blade.
84 Troubleshooting