> 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/tb-multi-blade-switch.md).

# TB Multi-Blade switch

![Photo of the TB Multi-Blade switch](https://docs.telcobridges.com/w/images/3/31/TB-Multi-Blade-photo.jpg) With up to 1024 trunks in a single system, the non-blocking architecture of the Multi-Blade™ solution provides you with a superior level of density and redundancy.

Our unique technology enables you to bridge multiple [TB640](https://telcobridges.com/products/development-platforms-tdev/) System-Blades™ together to a level never before seen in the market. It is the most flexible and powerful solution to increasing your overall system capacity.

### Features and benefits

**Density:** Most systems on the market today only support a small number of trunks per blade or per chassis. Scaling up with low-density cards means that more rack space is needed for cards and additional cooling modules and maintenance access.

**Flexibility:** All newly-deployed services require adjustment and fine-tuning to match subscriber requirements and preferences. Unfortunately, most systems have fixed specifications that do not adjust easily to the variable requirements of the service provider. They also perform in a less-than-optimum fashion when trying to accommodate multiple-applications simultaneously.

**Ease of Integration:** Most providers have huge investments in already-installed equipment. But new applications that run on dedicated Compact-PCI chassis can be difficult to integrate with the existing equipment. Equipment that cannot be easily integrated “in the field” generates extra costs that are not easy to recoup. So, to maintain their competitive advantage, service providers need to be able to rapidly integrate new services, and capitalize on the additional investment.

**Availability:** As density increases, the risk of system failure increases. Most systems have a single point of failure, such as the PCI bus on a Compact-PCI chassis, which is shared across all the boards in that chassis: if one board or the CPU card fails, the entire chassis can fail.

**Performance:** High density, scalability and flexibility all call for high-performance. A system that performs marginally before scaling up, is unlikely to perform better after scaling up. Performance therefore sets a limit to the maximum size a system will gracefully scale up.

### References

* [Data sheet](https://docs.telcobridges.com/w/images/6/68/TB-Multi-Blade_Data-Sheet.pdf)


---

# 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/tb-multi-blade-switch.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.