User's Manual

Table 9 Basic Low End Troubleshooting (continued)
ActionConditionStep
1. If the Blade Link was not removed, be sure that is
properly installed and fully seated.
“SBL_REMOVED “ - Blade Link was removed6b
2. Look for bent connector pins on the Blade Link.
1. Be sure that the Blade Link is properly installed and
fully seated.
“ILO_RST_REASON_SBL” - The iLO 3 was reset
because the Blade Link was installed (FPL only)
6c
2. Look for bent connector pins on the Blade Link.
1. Use the sysset command.“SYSVARS_MISMATCH” - The system variable
stored on the Blade Link does not match the
system variable stored on the blade.
6d
1. Be sure that the Blade Link installed in the correct slot
and enclosure, see “Installing the Blade Link for BL860c
i4, BL870c i4 or BL890c i4 configurations” (page 21)
“SBL_DOMAIN_IMPROPER_SBL - The Blade Link
currently installed is not appropriate for the blade
slot (even/odd) and enclosure (c7000/c3000)
being used
6e
2. Be sure that the Blade Link is properly installed and
fully seated.
3. Look for bent connector pins on the Blade Link.
1. Be sure that the Blade Link installed in the correct slot
and enclosure, see “Installing the Blade Link for BL860c
i4, BL870c i4 or BL890c i4 configurations” (page 21)
“POWER_FAIL_IMPROPER_SBL” - Power
command failed because the Blade Link currently
installed is not appropriate for the blade slot
6f
2. Be sure that the Blade Link is properly installed and
fully seated.
(even/odd) and enclosure (c7000/c3000) being
used
3. Look for bent connector pins on the Blade Link.
1. Be sure that the Blade Link is properly installed and
fully seated.
Incorrect number of processors displayed for the
conjoined blades
6g
2. Look for bent connector pins on the Blade Link.
3. Check the MP logs for CPUs that were de-configured
by system firmware. The UEFI cpuconfig command can
be used to show and re-configure hardware or software
de-configured CPUs.
1. Be sure that the Blade Link is properly installed and
fully seated.
“QPI_CPU_LINK_DEGRADED”6h
Table 10 Advanced Low End Troubleshooting
ActionSymptom/ConditionStep
SEL logging has stopped (health is steady green and power is steady
green).
Cannot read SEL from the system
console.
6
1. Examine console messages for any UEFI errors or warnings about
operation or communications.
This issue is fixed when the SEL resumes logging.
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).
OS is non-responsive (hung)7
Nothing can be logged for this condition.
1. Use the iLO 3 MP Command Menu to initial a ToC, using the tc
command.
2. Reboot the OS and escalate.
Methodology 83