> 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/tmedia-documentation/server-and-os-administration/hardware-hosts.md).

# Hardware:Hosts

The hosts are another critical module of TelcoBridges solutions and hosts redundancy will greatly improve the high availability and reliability of your system.

#### Primary switchover

Let's see the consequences of losing the [primary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host. Here is the state of a redundancy host setup after an installation:

![Host redundancy original state after a new installation](https://docs.telcobridges.com/w/images/4/4b/Host_redundancy_original.png)

If the primary host is lost, two high availability mechanisms will be activated:

* [standby](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) Toolpack will become [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md)
* [slave](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/master-slave/README.md) database will become [master](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/master-slave/README.md). This will allow the system to keep functioning without manual operation (note that [transient calls](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/transient-calls/README.md) will be lost during the switchover), as illustrated in the following picture.

![Host redundancy state after losing the primary host](https://docs.telcobridges.com/w/images/1/19/Host_redundancy_primary_lost.png)

When the [primary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host is recovered, the [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) Toolpack system and the [master](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/master-slave/README.md) database will stay on the [secondary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host.

![Host redundancy state after the recover of the primary host](https://docs.telcobridges.com/w/images/2/25/Host_redundancy_primary_recover.png)

#### Secondary switchover

Let's see the consequences of losing the [secondary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host. Here is the state of a redundancy host setup after an installation:

![Host redundancy original state after a new installation](https://docs.telcobridges.com/w/images/4/4b/Host_redundancy_original.png)

If the [secondary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host is lost there are no effect on the system, since the [active](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) Toolpack system was already running the [primary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host.

![Host redundancy state after losing the secondary host](https://docs.telcobridges.com/w/images/9/9e/Host_redundancy_secondary_lost.png)

When the [secondary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) host is recovered, the system returns to its original state (just like after the installation).

![Host redundancy original state after the recover of the secondary host](https://docs.telcobridges.com/w/images/4/4b/Host_redundancy_original.png)

NOTE: The database and host redundancy mechanism are two separate features, meaning that a database switchover will not necessarily cause a host switchover as well.

### Recommended Setup

#### Recommended Hardware

* Use TelcoBridges servers [TMG7800-CTRL](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/), [TSBC-HW-SRV](https://github.com/telcobridges-main/tmedia-wiki/tree/main/_excluded/sbc/freesbc-and-prosbc/README.md)
* Having dual power supplies is a plus
* The number of network interface needed by a system is application specific, but for TelcoBridges products at least two independent network interfaces are needed for controlling [Tmedia](https://telcobridges.com/media-gateways/products/tmedia-gateways/) and another one to connect to the management network.

#### Warnings

* IP Teaming/ IP Bonding - TelcoBridges Hardware **doesn't** support [IP Teaming (Ip Bonding)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/voip-bonding/README.md). TelcoBridges products **can't** work with the host configure with Ip Teaming in the system. TelcoBridges products uses 2 network interfaces to achieve the same goal.
* RAID - It is highly recommended to disable BIOS RAID on the motherboard. Use software RAID instead, also known as MD RAID.


---

# 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/tmedia-documentation/server-and-os-administration/hardware-hosts.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.
