> 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/other-pages/operations/hardware-power-supply.md).

# Hardware:Power Supply

This page explains how to provide high availability for the power source of your system.

### Dual power Connector

The following Tmedia units can be purchased with dual power connector:

* TMP6400 (2 U box)
* [TMG7800](/tmedia-documentation/products/tmedia/tmg7800.md) series

The dual power supply allows the unit to keep running even if the one of them fails.

It is also important to mention that the dual power supplies are [hot-swappable](/tmedia-documentation/other-pages/operations/hot-swap.md). This means that you can replace a defective power supply without shutting down the system.

### Dual Power Source

TelcoBridges recommends to connect the Tdev system to 2 independent power sources.

Each rack has 2 power entry, which will distribute the 2 independent power sources throughout the whole system.

### Other System Devices

As for other devices included in your system like servers, Ethernet switches, etc. It is recommended to get redundant power supplies for them as well, to increase the reliability of the system.

### Recommended Setup

The following schematic shows the recommended power connections for a high availability system:

![Ha Power Distribution](https://docs.telcobridges.com/w/images/f/fc/Ha_Power_Distribution.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://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/hardware-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.