> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v20-en-us/parallels-ras-20-administrators-guide/load-balancing-and-halb/high-availability-load-balancing-halb/halb-device-status-and-version-number.md).

# HALB Device status and version number

HALB device status and version information can be verified in two places in the RAS Console, which are described below.

## **Site tab**

You can view HALB devices and related information on the **Site** tab in the RAS Console. To see it, navigate to **Farm** > **Site**. Note the **Agent** and **Agent Version** columns. The two columns are described below.

The **Agent column** can have the following values:

* **Not verified** (red) - The agent is not verified and cannot communicate. If you see this, verify the agent.
* **Needs update** (yellow) - The agent is functioning normally but is an older version. If you see this, you should update the agent to the latest version.
* **Agent OK** (green) - The agent is OK. No actions are necessary.

The **Agent Version** column displays the actual agent version, including the Parallels RAS version and build numbers.

You can also ping a HALB device by right-clicking it and choosing **Tools** > **Ping host**. For additional information about using the **Tools** menu and the **Ping** tool specifically, please see [**Computer management tools**](/landing/ras-admin-guide/v20-en-us/parallels-ras-20-administrators-guide/common-management-tasks/computer-management-tools.md).

## **Devices tab**

The HALB devices agent status and version can also be viewed in the main HALB subcategory. To see it, navigate to **Farm** > **Site** > **HALB** and select the **Devices** tab. The agent information displayed here is the same as on the **Site** tab described above.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.parallels.com/landing/ras-admin-guide/v20-en-us/parallels-ras-20-administrators-guide/load-balancing-and-halb/high-availability-load-balancing-halb/halb-device-status-and-version-number.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 `build a script that syncs our docs to a CMS` 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.