# Networking overview This section will help you better understand the basic requirements for our network topology. We will provide examples, tips for successful operation, and recommended hardware. ## Redundancy schemas HOLOPLOT systems can provide different levels of redundancy depending on your requirements. Generally, the two main types of redundancy are network redundancy and device redundancy. ### Network redundancy Network redundancy refers to using separate primary and secondary networks that work together to transmit management and audio data to operate the system. It is crucial to understand that using multiple networks for transmitting Audio over Internet Protocol (AoIP) is not only recommended in case of hardware failures in some of the network switches or other unforeseen events, but it is also a standard practice that ensures higher channel counts and lower latencies. This aligns with the [ST 2022-7](#user-content-fn-1)[^1] standard supported by our Audio Modules. ### Device redundancy [HOLOPLOT Control](/holoplot-control/getting-started.md) and Audio Modules require HOLOPLOT Controllers for system management and operation. Device redundancy refers to HOLOPLOT Controllers, for which three redundancy schemas are available. * Non-redundant with a single HOLOPLOT Controller * Cold-spare with two HOLOPLOT Controllers * Seamless Failover with three or more HOLOPLOT Controllers In case of a HOLOPLOT Controller hardware failure, a non-redundant system would disrupt operations. A cold spare would allow for recovery within a few minutes, while a seamless failover would guarantee uninterrupted operation. ## Network topology Let's examine the network topologies required for a HOLOPLOT installation. In this context, we will consider two basic examples that outline the components and their differences. ### Basic deployment The first is a single controller and network configuration. This is the most basic level of deployment, which involves using only one HOLOPLOT Controller and a single network. It outlines the fundamental components required for the installation.

Basic deployment with a single HOLOPLOT Controller and Network

* **HOLOPLOT Controller** or **HOLOPLOT Controller Lite** connects to the network switch using either a copper connection or SFP+/SF28 cages (only available for HOLOPLOT Controller). * **HOLOPLOT Audio Modules** connect to the network switch using a 1GbE copper connection. * An installation that requires a **Dante-to-Ravenna conversion** requires two additional network connections from the HOLOPLOT Controller, one for Dante and another for Ravenna. * A **Network Router** with a DHCP server is required. * A compatible **Network Switch** is required; for X2, it needs to be PoE++ compliant. * An **NTP server** is advised for installations without an internet connection, but not required. ### Network and device redundancy This scenario examines a fully redundant deployment with primary and secondary networks and three HOLOPLOT Controllers. It guarantees the highest protection against disruptions.

Fully redundant deployment with 3 HOLOPLOT Controllers and primary/secondary networks

* The 3x **HOLOPLOT Controllers** are interconnected using a ring topology. * **HOLOPLOT Controller** connects to both **Primary** and **Secondary Network Switches**. * The **Dante-to-Ravenna** conversion also connects to both **Primary** and **Secondary Network Switches** * The **DHCP Server** should provide IP Addresses in distinct Network Ranges for **Primary** and **Secondary Networks**. E.g.: 192.168.100.0/24 for Primary and 192.168.200.0/24 for Secondary. * **HOLOPLOT Audio Modules** require connections to both **Primary** and **Secondary Network Switches**. * An **NTP server** is required for offline installations without an active internet connection. ### Setting up the Ring Connection To enable seamless failover and device redundancy, a ring connection between all three HOLOPLOT Controllers is required. This is achieved by interconnecting the Controllers using the supplied DAC (Direct Attach Cables). Use the ports labeled **HA1** and **HA2** as shown in the diagram below.

Diagram of the connections on the HOLOPLOT Controller

Each Controller must be directly connected to the other two. In other words, Controller 1 should have a direct cable to both Controller 2 and Controller 3—and the same applies to the others. Refer to the table below to see exactly which ports should be connected to each other. | Controller | HA1 port should be connected to | HA2 port should be connected to | | ---------------- | ------------------------------- | ------------------------------- | | **Controller 1** | Controller 2 - HA1 | Controller 3 - HA1 | | **Controller 2** | Controller 1 - HA1 | Controller 3 - HA2 | | **Controller 3** | Controller 1 - HA2 | Controller 2 - HA2 | ## Networking requirements ### DHCP and IP addresses HOLOPLOT Audio Modules and controllers rely on DHCP servers for IP sddress assignment. If you want to use fixed IPs, you can do so by configuring Static DHCP Leases with the MAC addresses of HOLOPLOT Audio Modules and controllers in your DHCP server/network router. The [X1 Series](/introduction-to-holoplot/product-family.md#the-x1-series) (MD96 and MD80-S) requires up to four IP addresses from the DHCP server. These include management primary/secondary and audio primary/secondary. Even though only one physical cable is present per network, X1 Audio Modules have an internal switch that splits into audio and management networks.\ \ On the other hand, the [X2 Series](/introduction-to-holoplot/product-family.md#the-x2-series) (MD30) requires up to two IP addresses from the DHCP server, one for primary and one for secondary. Audio and management share the same network interface. {% hint style="warning" %} HOLOPLOT does not support the configuration of static IP addresses or using Zero-configuration networking (Zeroconf). DHCP Servers cannot operate in the Link-Local Addressing reserved IP Range of `169.254.1.0` to `169.254.254.25`. {% endhint %} ### AV-compatible network switches Due to the nature of our system's signal routing, it is advisable to use AV-compatible network switches that can appropriately handle multicast routing and have no adverse effects on PTP. Network switches must support IGMP[^2] Snooping v1, v2, and v3 are supported by various network hardware. ### Time syncing For the correct operation of our system, two clocking mechanisms are required. Network Time Protocol (NTP) for Management and Precise Time Protocol (PTP) for Audio over IP. #### NTP If you have an internet connection, our system will automatically synchronize with Google's NTP server for time synchronization, so you don't need any additional hardware. However, if you don't have an active internet connection, it is advisable to use an NTP server for non-redundant installations. An NTP server is also required for a [Seamless Failover](#redundancy-schemas) installation. #### PTP HOLOPLOT Audio Modules use two different Precision Time Protocol (PTP) versions for clock synchronization over Audio over IP. The two versions are PTPv1 (Dante) and PTPv2 (Ravenna). \ \ If you are using HOLOPLOT Audio Modules in large installations, it's recommended that you don't use them as Clock leaders. Instead, it's advisable to use an external device to perform the leader function. This external device could be your Audio Signal Source, like a mixing console, external DSP, or a dedicated Wall Clock. It is important to note that Dante and Ravenna use different PTP versions. Dante uses PTPv1, while Ravenna uses PTPv2. If your installation requires both standards to function simultaneously, keeping them isolated in distinct networks is recommended. If impossible, you can avoid clocking issues by setting Ravenna's PTP Domain to a value different than 0. {% hint style="info" %} You can learn how to define network settings for Ravenna Audio Modules in our [HOLOPLOT Control](/holoplot-control/configuring-the-system/network-settings-ravenna-only.md) guide. {% endhint %} ## Recommended network devices Extensive testing and validation have been conducted on various network devices to ensure their compatibility with HOLOPLOT Audio Modules. The following are examples of network devices confirmed to work seamlessly with HOLOPLOT Audio Modules, showcasing the diverse options available for optimal performance. It's important to note that this list is not exhaustive, and other compatible devices may not be mentioned here. ### Network switches * Netgear M4250 AV Line * Netgear M4300 AV Line * Netgear M4350 AV Line * Netgear M4500 AV Line * Cisco 300 Series * Cisco 350 Series * Luminex Gigacore Lines {% hint style="info" %} PoE++ compliance is required for the [X2 Series](/introduction-to-holoplot/product-family.md#the-x2-series). Calculating the switch's required power budget based on the number of modules is also advisable. {% endhint %} ### Network routers & DHCP servers * MikroTik RB2011UiAS-RM ### Clock sources for NTP and PTP * TimeMachines TM1000A - NTP * TimeMachines TM2000B - NTP & PTP [^1]: [](https://web.archive.org/web/20201108064040id_/https://ieeexplore.ieee.org/ielx7/8716820/8716821/08716822.pdf) [^2]: Internet Group Management Protocol --- # Agent Instructions: 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: ``` GET https://docs.holoplot.com/user-guides/holoplot-system-deployment/networking-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.