3211 Front Control Panel Controls and Indicators

CS500 model 3211 server chassis front panel controls and indicators

The CS500 model 3211 server chassis contains a set of control panels in the left and right rack handles. Each control panel contains two sets of control buttons and LEDs, one for each compute node. Each control panel assembly is pre-assembled and fixed within the rack handle.

The control panel houses two independent LEDs and two button integrated LEDs for each node, which are viewable to display the system’s operating status. The system BIOS and the integrated BMC provide functions for the control panel buttons and LEDs.

Figure: CS500 Model 3211 Front Panel Controls and Indicators

Power button with LED. Toggles the node power on and off. Pressing this button sends a signal to the BMC, which either powers the system on or off. The integrated LED is a single color (green) and is capable of supporting different indicator states.

The power LED sleep indication is maintained on standby by the chipset. If the compute node is powered down without going through the BIOS, the LED state in effect at the time of power off is restored when the compute node is powered on until the BIOS clear it.

If the compute node is not powered down normally, it is possible the Power LED will blink at the same time the compute node status LED is off due to a failure or configuration change that prevents the BIOS from running.


State	Power Mode	LED	Description
Power-off	Non-ACPI	Off	Node power is off, and the BIOS has not initialized the chipset.
Power-on	Non-ACPI	On	Node power is on, and the BIOS has not initialized the chipset.
S5	ACPI	Off	Mechanical is off and the operating system has not saved any context to the drive.
S1	ACPI	Blink	DC power is still on. The operating system has saved context and changed to a low-power state. (Blink rate is 1Hz at 50% duty cycle.)
S0	ACPI	On	Node and operating system are up and running.

ID button with LED. Toggles the integrated ID LED and blue ID LED on the rear of the node motherboard on and off. The ID LED is used to visually identify a specific compute node in the server chassis or among several servers in the rack. If the LED is off, pushing the ID button lights the ID LED. Issuing a chassis identify command causes the LED to blink. The LED remains lit until the button is pushed again or until a chassis identify command is received.

Network link/Activity link. When a network link from the compute node is detected, the LED turns on solid. The LED blinks consistently while the network is being used.

Status LED. This is a bicolor LED that is tied directly to the Status LED on the motherboard (if present). This LED indicates the current health of the compute node.

Table 1. CS500 Model 3211 Status LED
LED State	Power Supply Condition
Off	Power off: Compute node unplugged Power on: Compute node powered off and in standby, no prior degraded\non-critical\critical state
Green solid	Compute node ready/no alarm
Green blinking 1Hz	Compute node ready, but degraded: redundancy lost such as the power supply or fan failure; noncritical temp/voltage threshold; battery failure; or predictive power supply failure.
Amber solid	Critical alarm: Critical power nodes failure, critical fans failure, voltage (power supply), critical temperature and voltage.
Amber blinking 1Hz	Non-Critical Alarm: Redundant fan failure redundant power node failure, non-critical temperature and voltage

When the compute node is powered down (transitions to the DC-off state or S5), the BMC is still on standby power and retains the sensor and front panel Status LED state established before the power-down event.

When AC power is first applied to the compute node, the Status LED turns solid amber and then immediately changes to blinking green to indicate that the BMC is booting. If the BMC boot process completes with no errors, the Status LED will change to solid green.

When power is first applied to the compute node and 5V-STBY is present, the BMC controller on the motherboard requires 15-20 seconds to initialize. During this time, the compute node status LED will be solid on, both amber and green. Once BMC initialization has completed, the status LED will stay green solid on. If power button is pressed before BMC initialization completes, the compute node will not boot to POST.

Table 2. CS500 Model 3211 Detailed Status LED
LED State	Criticality	LED State Definition
Off	Not ready	System is powered off (AC and/or DC). System is in EuP Lot6 Off Mode. System is in S5 Soft-Off State.
Green solid	Okay	Indicates that the System is running (in S0 State) and its status is Healthy. The system is not exhibiting any errors. AC power is present and BMC has booted and manageability functionality is up and running. After a BMC reset, and in conjunction with the Chassis ID solid ON, the BMC is booting Linux. Control has been passed from BMC uBoot to BMC Linux itself. It will be in this state for 10-20 seconds.
Green blinking 1Hz	Degraded - system is operating in a degraded state although still functional, or system is operating in a redundant state but with an impending failure warning.	System degraded: Redundancy loss such as power-supply or fan. Applies only if the associated platform sub-system has redundancy capabilities. Fan warning or failure when the number of fully operational fans is less than minimum number needed to cool the system. Non-critical threshold crossed – Temperature (including HSBP temp), voltage, input power to power supply, output current for main power rail from power supply and Processor Thermal Control (Therm Ctrl) sensors. Power supply predictive failure occurred while redundant power supply configuration was present. Unable to use all of the installed memory (more than 1 DIMM installed). Correctable Errors over a threshold and migrating to a spare DIMM (memory sparing). This indicates that the system no longer has spared DIMMs (a redundancy lost condition). Corresponding DIMM LED lit. In mirrored configuration, when memory mirroring takes place and system loses memory redundancy. Battery failure. BMC executing in uBoot. (Indicated by Chassis ID blinking at 3Hz). System in degraded state (no manageability). BMC uBoot is running but has not transferred control to BMC Linux. Server will be in this state 6-8 seconds after BMC reset while it pulls the Linux image into flash. BMC Watchdog has reset the BMC. Power Unit sensor offset for configuration error is asserted. HDD HSC is off-line or degraded.
Amber blinking 1Hz	Non-critical - System is operating in a degraded state with an impending failure warning, although still functioning	Non-fatal alarm – system is likely to fail: Critical threshold crossed – Voltage, temperature (including HSBP temp), input power to power supply, output current for main power rail from power supply and PROCHOT (Therm Ctrl) sensors. VRD Hot asserted. Minimum number of fans to cool the system not present or failed. Hard drive fault. Power Unit Redundancy sensor – Insufficient resources offset (indicates not enough power supplies present). In non-sparing and non-mirroring mode if the threshold of correctable errors is crossed within the window.
Amber solid	Critical, non-recoverable – System is halted	Fatal alarm – system has failed or shut down: CPU CATERR signal asserted MSID mismatch detected (CATERR also asserts for this case). CPU 1 is missing CPU Thermal Trip No power good – power fault DIMM failure when there is only 1 DIMM present and hence no good memory present. Runtime memory uncorrectable error in nonredundant mode. DIMM Thermal Trip or equivalent SSB Thermal Trip or equivalent CPU ERR2 signal asserted BMC/Video memory test failed. (Chassis ID shows blue/solid-on for this condition) Both uBoot BMC FW images are bad. (Chassis ID shows blue/solid-on for this condition) 240VA fault Fatal Error in processor initialization: Processor family not identical Processor model not identical Processor core/thread counts not identical Processor cache size not identical Unable to synchronize processor frequency Unable to synchronize QPI link frequency Uncorrectable memory error in a non-redundant mode