> 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/telecom-references/ss7-and-signalling/isup/general-guidelines-to-achieve-highly-redundant-high-performance-system-host-failure.md).

# General guidelines to achieve highly redundant high-performance system (host failure)

1. Extending the previous guidelines, every module should have a backup module on another machine (refer to the figure below) in case an unexpected failure occurs (i.e., power failure on a host machine). The standby module should monitor the active module and decide to take over in case of failure.
2. Depending on the system requirements, the architect may want to use host machine capable to handle twice the normal load if no performance hit is required in case of failures.
3. Inter-module communication through IP must be made fail-safe as well to avoid dealing with link failure or message re-ordering within the functional modules.
4. Call control module redundancy is mostly implemented by the TB640 API architecture since it is always possible to recover the configuration and/or state of all resources and calls present on a Tmedia device at any moment. Thus, the standby call control application only has to query the different TB640 blades and reconstruct its internal data structure based on this information.
5. Communication links between hosts and the TB640 blades are protected by the TelcoBridges’ network redundancy (i.e., link disconnection, switch failures, bad cables, etc.) and thus only require the proper system configuration (i.e. having two Ethernet switches and two Ethernet line cards on each host machine).

![HA introduced in large systems](https://docs.telcobridges.com/w/images/6/67/HA_introduced_in_large_systems.jpg)


---

# 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/telecom-references/ss7-and-signalling/isup/general-guidelines-to-achieve-highly-redundant-high-performance-system-host-failure.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.