> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/configuration/web-portal-3-3/system/status/detailed-status-views/verifyhostrole.md).

# Host Status

\*\*\*Applies to version(s): v2.9, v2.10, v3.0\*\*\*

There are multiple ways to verify the status of a host. This article illustrates how to verify status using the Welcome page and the Navigation panel.

#### Welcome Page

1- Click **Welcome** in the navigation panel. (This screen is displayed when you log on to the Web Portal.)

![StatusHost 0](https://docs.telcobridges.com/w/images/d/dd/StatusHost_0.png)

This screen indicates, (in two areas), the role of the host that you are connected to. In this example, the host is primary.

In the following example, the host role is secondary.

![StatusHost 1](https://docs.telcobridges.com/w/images/a/a8/StatusHost_1.png)

#### Navigation Panel

1- Select **Hosts** in the navigation panel.

![StatusHost 2](https://docs.telcobridges.com/w/images/2/27/StatusHost_2.png)

2- Click the **Status** tab.

![StatusHost 3](https://docs.telcobridges.com/w/images/f/fb/StatusHost_3.png)

3- The hosts appear in the **Host Status List**

![StatusHost 4](https://docs.telcobridges.com/w/images/c/c1/StatusHost_4.png)

4- To view more details about a host, select the host in the **Host Status List**'

![StatusHost 5](https://docs.telcobridges.com/w/images/7/71/StatusHost_5.png)

<details>

<summary>Northbound Interface</summary>

**Path**

```
/configurations/@[configuration_name]/hosts/@[hardware_name]/status
```

</details>


---

# 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://tmediadocs.telcobridges.com/configuration/web-portal-3-3/system/status/detailed-status-views/verifyhostrole.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.