> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/maas-documentation/monitoring/all-nodes.md).

# All Nodes

**All Nodes** is the fleet view of every device you have access to. Open it from **TB Nodes > All Nodes**.

<figure><img src="/files/jM7J4DQ011R9Vo9KhSWt" alt=""><figcaption><p>All Nodes fleet table — one host is expanded to show per-unit HA state, CPU and RAM, and active problems</p></figcaption></figure>

***

## What You See

Each row is one device. Columns:

| Column           | Description                                                                                    |
| ---------------- | ---------------------------------------------------------------------------------------------- |
| Device Name      | Friendly name; click to open [Detailed Node](/maas-documentation/monitoring/detailed-node.md). |
| Product          | ProSBC or TMG.                                                                                 |
| Topology         | Standalone or 1+1.                                                                             |
| Firmware         | Active firmware version.                                                                       |
| HA State         | Primary and Secondary states.                                                                  |
| CPU / RAM / Disk | Current usage on the active unit; disk shows the highest across hosts.                         |
| Active Calls     | Concurrent call legs.                                                                          |
| CPS              | Calls per second.                                                                              |
| Reboot / License | Status flags.                                                                                  |
| Problems         | Count of active triggers.                                                                      |

***

## Features

* **Sort** — click a column header. Click again to reverse.
* **Expand a row** — click anywhere on the row to see per-host detail: application HA states, CPU/RAM per unit, active problems, firewall alarms (ProSBC).
* **Filter** — top-right controls narrow the table by product, topology, or "problems only".
* **Export** — downloads the current table as CSV or JSON.
* **Site grouping** — if your devices have a `Site` tag configured, rows are grouped by site. Devices without the tag land in "No Site".

***

## Auto-Refresh

The table refreshes on its own roughly every 48 seconds. Refresh pauses when your browser tab is in the background and resumes with a fresh pull when you return.

***

## Deep Linking

Clicking a device name opens [Detailed Node](/maas-documentation/monitoring/detailed-node.md) for that host. The URL carries a `hostid` parameter so the link can be bookmarked or shared.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/maas-documentation/monitoring/all-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.