> 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-n-1-trunk-protection.md). # TB N+1 Trunk Protection ![Photo of the TB N+1 shelf](https://docs.telcobridges.com/w/images/5/5a/Photo-TB-N+1-shelf.jpg) The TelcoBridges [N+1](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/n-1/README.md) Shelf family of products were specifically designed to facilitate maintenance and protect the system against any interruption of a [TB640](https://telcobridges.com/products/development-platforms-tdev/) System-Blade™ connected to the N+1 Shelf. For example, the TB-N+1-16 Solution comprises up to fifteen primary TB640 System-Blades™ connected to the network through the N+1 shelf, plus one redundant TB640 blade waiting to be connected to the network in case of need. The redundant TB640 System-Blade™ can takeover at any time any one primary TB640 System-Blade™, and re-route the traffic to the redundant blade until the necessary maintenance is completed. The N+1 architecture is compatible with the TB-Multi-Blade™ architecture. With N+1, fifteen primary blades plus one redundant blade can be fully interconnected to create a non-blocking switch of 960 trunks. Control, maintenance and diagnostics are all provided through TB640 API calls, with a full set of easy-to-use functions for complete system status monitoring and control. N+1 blades can be added live to a system with no downtime. This means the system can scale from a 1:1 to 15:1 protection while it is still running. The TB640 System-Blades™ attached to the N+1 blades also provide the low power needed by the system. ### References * [Data sheet](https://docs.telcobridges.com/w/images/0/0a/Data-sheet-TB-N+1_Shelf.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-n-1-trunk-protection.md?ask=&goal= ``` `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.