> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-control/configuring-the-system/network-settings-ravenna-only.md).

# Network Settings - RAVENNA only

HOLOPLOT Control offers configuration capabilities similar to those in Dante Controller when using RAVENNA. This page will explain these capabilities and what you can do with them.

To configure the network settings, on the navigation bar, click **Settings** › **Network Settings**

<figure><img src="/files/UYfJ0rEHf5vh5xvSaMRf" alt=""><figcaption><p>Network Settings for Ravenna</p></figcaption></figure>

### Network settings groups

To customize the system according to your network topology, you can create different network settings groups. Each group has unique PTP and audio VLAN settings, and you can assign Audio Modules to different network segments with multiple VLAN assignments, PTP clock domains, or roles.

{% hint style="info" %}
Currently, only the **X1 Audio Modules** support the configuration of VLANs for real-time audio networks.
{% endhint %}

While all Audio Modules are initially assigned to the "Default" Network Group during system setup, you can create additional groups if needed. This flexibility allows you to tailor the system to your specific network requirements.

<figure><img src="/files/AqB2ptPE3WJScVgnELsX" alt="" width="375"><figcaption><p>Group Network Settings Window</p></figcaption></figure>

### PTP and QOS Settings

RAVENNA employs the PTPv2 standard as its clocking mechanism, which is sufficiently flexible to ensure compatibility with other standards such as ST2110 or AES67. To find an appropriate configuration, it is recommended that you match your existing RAVENNA/AES67 audio source.

{% hint style="success" %}
Find out more information on how to set up different devices on AES67 mode to work with a HOLOPLOT System. [AES67 Quick start guide](/user-guides/holoplot-system-deployment/aes67-quick-start-guide.md)
{% endhint %}

{% hint style="info" %}
In other systems, the terms *follower*, *leader*, and *grand leader* are sometimes replaced by *slave*, *master*, and *grandmaster*, respectively.
{% endhint %}

Here are some guidance to get you started:

* [**QOS PTP DSCP**](#user-content-fn-1)[^1]**:** This term refers to the prioritization of network packages for supported switches based on the application's QOS requirements. More information is available on [Ravenna's website](https://www.ravenna-network.com/your-practical-guide-to-aes67-part-2-2/).
  * for AES67/Dante inter compatibility: 46 (EF)
  * for RAVENNA: 48 (CS6)
* **PTP Domain:** When working in complex audio networks or sharing the same network with multiple AoIP standards, the domain for Audio Modules to handle PTP syncing can be defined.
* **Follower-Only mode**: This option prevents Audio Modules from assuming the roles of leader or grand leader in the network.
* **PTP priority 1 and 2**: When Follower-only Mode is disabled, Audio Modules will advertise those priorities to participate in the BMCA (Best master clock algorithm).
  * The value ranges from 0-255. A lower value is preferred for electing a Grand Leader.
* **PTP announce and sync interval**: Allows for configuring different message intervals for PTP syncing and announcement.
* **PTP delay mechanism**: Should be left in E2E unless specified otherwise.

{% hint style="info" %}
Dante devices rely on the older PTPv1 standard and can only function in PTP Domain 0. If you're sharing a network with other Dante devices that aren't using AES67 mode, it's recommended that you use a different PTP Domain to avoid conflicts. It's crucial that your source device follows the same PTP Domain as well to ensure reliable synchronization.
{% endhint %}

[^1]: The acronym QOS PTP DSCP stands for Quality-of-Service (QOS) Precision Time Protocol (PTP) Differentiated Services Code Point (DSCP).


---

# 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://docs.holoplot.com/holoplot-control/configuring-the-system/network-settings-ravenna-only.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.