> 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/getting-started/navigating-the-dashboard.md).
# Navigating the Dashboard
Once you've logged in, you'll land on the main dashboard. Think of this as your at-a-glance health check for the entire server. It summarizes the most critical information in one place, so you can quickly assess the system's status before diving into specific tasks.
This chapter will help you get familiar with the layout and understand the key information presented on the dashboard.
## **Understanding the interface layout**
The BMC web interface is organized into three main areas. Getting to know them will help you find what you need quickly.
* **Top Bar**: Located at the very top, this bar shows real-time status icons for **Health**, **Power**, and **BIOS**. It also contains the user menu, a **Refresh** button to update the data on the page, and the **Logout** button.
* **Sidebar Menu**: This is your main navigation tool, located on the left. It provides access to all the functional areas of the BMC, such as **Monitoring**, **Remote Operations**, and **Security**. We'll explore these in detail throughout this guide.
* **Main Panel**: This is the largest area in the center of the screen. It displays the detailed information or configuration options for whichever module you've selected from the sidebar menu.
## **Reviewing the system information summary**
The main panel of the dashboard is filled with widgets that give you a snapshot of the server's identity and health.
* **Server Information**: This widget displays the server's hardware identity, including its **Model**, **Manufacturer**, and **Serial number**. This is essential for asset tracking and when you need to request support.
* **Status Information**: This area acts as a health summary. It shows a count of **Critical** and **Warning** events from the system logs. A high number of critical events is a clear sign that the server needs immediate attention.
{% hint style="info" %}
**Pro Tip: Start here for any issue**
When you're troubleshooting a server, the dashboard is the best place to start. The event log summary can instantly tell you if the BMC has detected a specific hardware fault, saving you valuable diagnostic time.
{% endhint %}
## **Checking firmware and network status**
Two other critical widgets on the dashboard help you verify the server's current software state and its connectivity.
* **Firmware Information**: This shows the **Running** firmware version for the BMC. It's important to check this to confirm if a recent firmware update was successful or to know which version you're on when reporting an issue.
* **Network Information**: This widget displays the BMC's current network settings, including its **Hostname**, **Link status**, and assigned **IP Address**. If you're having trouble connecting to the BMC, this is the first place to check if it has the correct IP address and a "LinkUp" status.
---
# 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/getting-started/navigating-the-dashboard.md?ask=&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.
