> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/bmc-user-guide/monitoring/hardware-health.md).

# Hardware Health

One of the most powerful features of the BMC is its ability to give you a real-time view into the server's physical health. Proactively monitoring hardware can help you prevent downtime by catching potential issues before they become critical failures.

In this chapter, you'll learn how to check the status of your server's key hardware components, including sensors, fans, and health indicators.

## **Checking overall system health**

The first place to check for a high-level health summary is the **Inventory and LEDs** page. It consolidates the status of all monitored components into a single health indicator.

To check the overall system health:

1. In the sidebar menu, navigate to **Hardware status** > **Inventory and LEDs**.
2. Look for the **Overall System Health** field.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeOP8ZQsVF-J1_cu5Fi7Sq0rylfBt9YZy6zNWE5Zu0kFBaKS7vMgb2a8UBk90VCN2aWwK5ZCbX0WzxvEz4vigEZd52UP2tMBw_fLV7r2zfEk-A9bO0vnkswib7FlmWRU48-cen8sA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

This field provides a top-level status based on all active sensors and event logs. It will typically show one of the following states:

* **Healthy**: No critical or warning events are detected.
* **Degraded**: One or more warning-level events are present. The system is still operational but requires attention.
* **Critical**: A critical event has been detected that could lead to failure. This requires immediate investigation.

## **Monitoring sensors (temperature, voltage)**

The **Sensors** page gives you detailed, real-time readings from every sensor in the system, including those for temperature, voltage, and current. This is the most important screen for diagnosing thermal or power-related issues.

Navigate to **Hardware status** > **Sensors** to view the sensor list.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdh9x4_z4-cnAV1K5K4h3KHe7WYyY-IzD56n4fWv1qxWvkoDOvDBJnB9mIGjZbfIweeKS62M15OK-7jaIQUsnHtr_A8pYqbohAxz7_TCvIkHa0-iWCyVHDcqJwX_v4W-05ab_jlbA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

The sensor table provides the following information for each component:

* **Name**: The unique identifier for the sensor (e.g., `Core 48 CPU1`, `P12V AUX`).
* **State**: The operational state of the sensor, which can be `Enabled` or `Disabled`.
* **Status**: The current health of the sensor reading, which can be `OK`, `Warning`, or `Critical`.
* **Lower Critical / Lower Warning**: The minimum threshold values. If the current value drops below these, an alert will be triggered.
* **Current Value**: The real-time reading from the sensor, with the appropriate unit (e.g., `Cel` for Celsius, `V` for Volts).
* **Upper Warning / Upper Critical**: The maximum threshold values. If the current value exceeds these, an alert will be triggered.

{% hint style="success" %}
**Best Practice: Focus on the thresholds**

When reviewing sensor data, pay close attention to the `Current Value` in relation to the `Upper Warning`and `Upper Critical` thresholds. A value consistently near the warning level may indicate a cooling problem or a component under excessive load.
{% endhint %}

You can use the **Search** bar to find a specific sensor by name or use the **Filter** option to narrow down the list to only show sensors in a `Warning` or `Critical` state. This is extremely useful for quickly identifying the source of a problem.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdZCuua-PxEnFlAB3tWJ3izxAqITTPZiAk_2WoALcFYTtjFbI6-TtMBbu3mTH364dwdaZFC8gVRQO3bZik1xyQxMjbpSvat3-QpJKrcY-bDskgBC4J2L1OgDA2-LDQiMhf1o1ijhA?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

## **Monitoring fan status and control**

System fans are critical for maintaining proper operating temperatures. The **Fans** page displays the real-time speed and status of each fan in the chassis and allows for manual control.

Navigate to **Hardware status** > **Fans** to view the fan information.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcgfMvRuiqOFOTuUV9Yc5nMl_ZjsZaAKDZVUHWT3nyjC9kreHAr9BRgC7GCcu45C6HBkke5eWA4YLGmO0YZGc1mg-FVEQwuGnfueHcjyjvrfQQnw0N9JRcaV-7uxr0NLqb9wzGWOQ?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

The page shows the overall **Fan Health** and lists each fan with its current **Status** and **Fan speed** (in RPM).

You can also use the **Fan Control** buttons to change the fan speed profile:

* **Normal duty**: The standard operating mode, balancing cooling and power consumption.
* **High duty**: Forces fans to a higher speed for maximum cooling. This is useful when you anticipate a heavy workload or if ambient temperatures are high.
* **Auto control**: Allows the BMC to dynamically adjust fan speeds based on sensor readings. This is the recommended setting for most environments.

## **Using the identify LED**

In a data center with racks full of identical servers, finding the specific machine you need to work on can be challenging. The **System Identify LED** is a simple but essential tool to solve this problem.

To turn on the identify LED:

1. Navigate to **Hardware status** > **Inventory and LEDs**.
2. In the **LED light control** section, find the **System Identify LED** toggle.
3. Switch it to **On**.    \
   &#x20;     &#x20;

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdF0euEGSzlJal8rcVBBPec1ORa5j5bVz9uQzpROZbBSW1woHYSUQtJBOnf9Wk7Bl_Wzx8mF0A5gQ3xf7znWJI12dyoWM3UEw98vLvIkQemYEG0aoi_ay0QoFMfWiChuAlwNETnhw?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

This will cause a physical LED on the front and/or back of the server chassis to light up or blink (usually blue), making it easy to spot in the rack.

{% hint style="info" %}
**Pro Tip: A technician's best friend**

Before sending a remote hands technician to perform physical work on a server (like replacing a drive or a PSU), always turn on the identify LED first. This simple step prevents accidental work on the wrong machine, which can be a costly mistake.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/bmc-user-guide/monitoring/hardware-health.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.