> 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/hardware-clocking.md). # Hardware:Clocking The clock is a necessary component of a TDM network. Synchronizing your system on the right clock, allows it to perform properly. ### Clock Sources The Toolpack system can synchronize the system on 3 types of sources: * BITS port (Available on [TMG7800](/products/tmedia/tmg7800.md) telecom units and [TMG7800 telecom units](/products/tmedia/tmg7800.md) with DS3 or SONET/SDH mezzanine. Also available on the [7800 TMS](/products/tmedia/tmg7800.md) ) * [Line Service](https://tmediadocs.telcobridges.com/telecom-references/transmission-and-lines/line-service) * [SONET/SDH interface](https://tmediadocs.telcobridges.com/telecom-references/transmission-and-lines/sonet-sdh-interfaces) ### Choosing Clock Reference Always place the most reliable clock source at the top of the clock references list in the web portal. This will avoid unnecessary clock switch over. TelcoBridges recommend to synchronize the clock on the BITS port when available. If your system includes [7800 TMS](/products/tmedia/tmg7800.md), it is recommended that you use the [7800 TMS](/products/tmedia/tmg7800.md) BITS ports as clock sources. When the system selects a clock, it will only use clock sources that are valid and that are available on an active device of the system. For example, in a system containing two [7800 TMS](/products/tmedia/tmg7800.md) ( one will be active, the other standby ) the clock sources on the standby [7800 TMS](/products/tmedia/tmg7800.md) (BITS ports) will not be selected. In the figure below, the clock source #3 and #4 will not be selected as system clock unless the standby [7800 TMS](/products/tmedia/tmg7800.md) becomes active. ### Clock Redundancy The system clock is configured using the Toolpack web portal. Toolpack allows the system to have a system clock references list. Clock redundancy is accomplished by configuring at least 2 valid clock references in the system. The system will scan through the clock references list until it finds a valid one. If the active clock source becomes unavailable, the system will scan through the clock reference list again to find another valid clock source. Clock recovery, which means that the system will switch back to a more preferred clock source if it becomes available again, can be configured in TMS network. Another redundancy feature for the system clock are the two BITS ports that can be assigned to different clock source. #### Recommended Setup Here is an example of a system clock where 2 [7800 TMS](/products/tmedia/tmg7800.md) and the system have selected clock source #1 as system clock: ![Clocking Ha TMS](https://docs.telcobridges.com/w/images/4/49/Clocking_Ha_TMS.png) ### References \*\*NOTE:\*\*These references assume that your system is running at the very minimum on Toolpack v2.3. To configure the system, please select the appropriate [Toolpack Web Tutorial Guide](/other-pages/other/web-portal.md). --- # 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/hardware-clocking.md?ask=&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.