> 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/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/power-supply.md).

# Power Supply

### Redundant Power Supplies

The redundant power supplies is standard for all [Tmedia](/products/tmedia/tmedia.md) products (optional for [TMG800](/products/tmedia/tmg800.md)).

This allows the unit to keep running even if the one of them breaks.

It is also worth mentioning that the dual power supplies are [hot-swappable](/other-pages/operations/hot-swap.md). Therefore, a defective power supply can be replaced without shutting down the system.

### Redundant Power Source

TelcoBridges recommends to connect the [Tmedia](/products/tmedia/tmedia.md) system to 2 independent power sources. This recommendation extends to the system peripheral components like the network switches, for example.

#### Recommended Setup

Here is the schematic of a system with 2 power entry points:

![Power Distribution Recommended Setup](https://docs.telcobridges.com/w/images/6/6a/Ha_Power_Entry_Setup.png)

Even if the primary power source fails, the system can still operate, like shown in the following picture.

![Power Distribution Recommended Setup with Primary Source Failure](https://docs.telcobridges.com/w/images/2/29/Ha_Power_Entry_Fail.png)


---

# 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/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/power-supply.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.