Diagnostics Button and LEDs
At blade start-up, POST diagnostics test the CPUs, DIMMs, HDDs, and rear mezzanine modules, and any
failure notifications are sent to Cisco UCS Manager. You can view these notifications in the Cisco UCS
Manager System Error Log or in the output of the
show tech-support
command. If errors are found, an amber
diagnostic LED also lights up next to the failed component. During run time, the blade BIOS and component
drivers monitor for hardware faults and will light up the amber diagnostic LED as needed.
LED states are saved, and if you remove the blade from the chassis the LED values will persist for up to 10
minutes. Pressing the LED diagnostics button on the motherboard causes the LEDs that currently show a
component fault to light for up to 30 seconds for easier component identification. LED fault values are reset
when the blade is reinserted into the chassis and booted, and the process begins from its start.
If DIMM insertion errors are detected, they may cause the blade discovery process to fail and errors will be
reported in the server POST information, which is viewable using the UCS Manager GUI or CLI. DIMMs
must be populated according to specific rules. The rules depend on the blade server model. Refer to the
documentation for a specific blade server for those rules.
Faults on the DIMMs or rear mezzanine modules also cause the server health LED to light solid amber for
minor error conditions or blinking amber for critical error conditions.
Installing the Front Mezzanine Storage Module
The Cisco UCS B200 M5 blade server uses an optional front mezzanine storage module that can provide
support for two drive bays and RAID controller or NVMe-based PCIe SSD support functionality.
To install the front mezzanine storage module, follow these steps:
Cisco UCS B200 M5 Blade Server Installation and Service Note
15
Servicing a Blade Server
Diagnostics Button and LEDs
