> 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/configuration/managing-firmware.md).

# Managing Firmware

Keeping your server's firmware up-to-date is one of the most important maintenance tasks you can perform. Firmware updates provide critical security patches, bug fixes, and sometimes even new features for both the BMC and the host system's BIOS.

This chapter guides you through checking your current firmware versions and safely applying updates.

## **Checking current firmware versions**

Before you perform an update, you should always verify the versions you are currently running.

1. In the sidebar menu, navigate to **Operations** > **Firmware**.
2. The page displays the status for both the BMC and the Host (BIOS).

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcznLYnTk4M_gUOeGyPJmthwZlI73lcF2OpVpN9l11np8gDkSKfOpfMdQDtzEUpehwqth-8cx-vLVR--p0BNIk2jOxWHDfOi3VOPrIzDASt-hHsvXlkH-9OSxw2VnWNQJTvgLxA2Q?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

For both the **BMC** and **Host**, you will see:

* **Running image**: The version that is currently active.
* **Backup image**: The version stored in the backup slot. The system can revert to this image if an update fails.

## **Updating the BMC and BIOS firmware**

The update process is the same for both the BMC and the Host firmware. You will need to have the firmware image file (usually a `.tar` file) downloaded to your local machine.

1. On the **Firmware** page, scroll down to the **Update firmware** section.
2. Select whether you want to update the **Active Image** or the **Backup Image**.
3. Click **Add file** and select the firmware image file from your computer.
4. Click **Start update**.

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

{% hint style="danger" %}
**Caution: Do not interrupt the update process**

* A firmware update is a critical operation. The process can take **15 minutes or more**. During the update, the BMC will be unresponsive and your web session will be disconnected.
* **Do not power off the server or disconnect the network cable** during this time, as it could leave the BMC in an unrecoverable state. Once the update is complete, the BMC will restart, and you will be able to log in again.
  {% endhint %}

## **Understanding update options**

The firmware update interface provides a few options that give you more control over the process.

* **Apply Time**: This dropdown lets you decide when the new firmware becomes active.
  * **Immediate**: The update process begins as soon as the file upload is complete. This is the most common option.
  * **On Reset**: The firmware is uploaded and staged, but it will only be applied the next time the BMC or server is reset. This is useful if you want to upload the firmware now but schedule the actual update for a planned maintenance window.
* **Preserving Configuration**: Before updating, you can choose which settings to preserve. Navigate to **Operations**> **Preserve** to select configurations like **Network** or **Authentication** that you want to keep. This saves you from having to reconfigure everything from scratch after an update. (This is covered in more detail in Chapter 15).


---

# 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/configuration/managing-firmware.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.