Specifications

Table 5-2 Basic Low End Troubleshooting (continued)
ActionConditionStep
1. Ensure that the Scalable BladeLink installed in the
correct slot and enclosure, see “Installing the Scaleable
BladeLink” (page 45)
2. Ensure that the Scalable BladeLink is properly installed
and fully seated.
3. Check for bent connector pins on the Scalable
BladeLink.
“POWER_FAIL_IMPROPER_SBL” - Power
command failed because the SBL currently
installed is not appropriate for the blade slot
(even/odd) and enclosure (c7000/c3000) being
used
6f
1. Ensure that the Scalable BladeLink is properly installed
and fully seated.
2. Check for bent connector pins on the Scalable
BladeLink.
Incorrect number of processors displayed for
the conjoined blades
6g
1. Ensure that the Scalable BladeLink is properly installed
and fully seated.
“QPI_CPU_LINK_DEGRADED”6h
Table 5-3 Advanced Low End Troubleshooting
ActionSymptom/ConditionStep
SEL logging has stopped (health is steady green and power is steady
green).
1. Examine console messages for any UEFI errors or warnings about
operation or communications.
This issue is fixed when the SEL resumes logging.
Cannot read SEL from the
system console.
6
Front panel LEDs indicate that the server blade power is turned on,
and it is either booting or running the OS (for example, health is steady
green and power is steady green).
Nothing can be logged for this condition.
1. Use the iLO MP Command Menu to initial a ToC, using the tc
command.
2. Reboot the OS and escalate.
3. Obtain the system hardware status dump for root cause analysis.
4. Examine the iLO MP logs for entries related to processors, processor
power modules, shared memory, and core I/O devices (see “Errors
and error logs” (page 65) for more details).
This issue is fixed when the root cause is determined.
OS is non-responsive (hung)7
Methodology 63