> 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/setting-up-system-essentials.md).
# Setting up system essentials
This page provides guidance on configuring system settings for optimal performance, with a focus on Audio over IP (AoIP) protocols and network redundancy.
## Selecting an AoIP Protocol
Settings › Network Settings › AoIP Protocol
HOLOPLOT provides Audio Modules with hardware options that support either the Dante or RAVENNA AoIP standards. The **X1 MD96** and **MD80-S** models are available in both Dante and RAVENNA configurations, while the **X2 MD30** model is exclusively offered in RAVENNA.\
\
In this section, we will guide you through setting up the system for these two distinct protocols.
### Toggling between Dante and RAVENNA
1. On the navigation bar, click **Settings** › **System Settings.**
2. You can use the section inside the settings page to toggle between the two standards. Make sure to select the AoIP standard that matches your active HOLOPLOT Audio Module system.
#### Dante
* Network and Clock configuration and routing between Dante transmitters and HOLOPLOT Audio Modules will happen inside Dante Controller.
* Routing of the Dante channels into audio inputs will happen inside HOLOPLOT Control.
#### RAVENNA
* Network Configuration and Clock configuration will happen inside HOLOPLOT Control.
* Stream management and stream routing will happen inside HOLOPLOT Control.
{% hint style="warning" %}
* Switching between Dante and RAVENNA will erase some information on the system.
* When moving away from RAVENNA, the system will discard audio stream subscriptions, audio input routings, and Network Settings.
{% endhint %}
***
## Network redundancy
A HOLOPLOT system can be configured with or without network redundancy. This affects how network statuses appear in the Device List. With redundancy enabled, both networks are considered when calculating the Network status for controllers and modules.
To configure network redundancy, go to **Settings › System Settings** and check the Secondary Network box under **Audio Networking and Hardware**.
Network Redundancy toggle
***
## Module's LED indicators
Overview of Module's LED Behavior
The LEDs on any module type provide information about the module's general state, including health (left) and power (right).
| Left LED color | Health Status |
| -------------- | ------------------------------------------------------ |
| Green | Functional Hardware & Network |
| Orange | Hardware & Network Unknown, Warning, Error or Critical |
| Right LED color | Power Status |
| --------------- | ------------------------------------------- |
| White | Awake/On |
| Light blue | Transition states going to sleep, waking up |
| Dark blue | Deep sleep / Sleep / Power saving |
The **Settings › System Settings** page in Control contains an **Always On** toggle that changes the behavior of all modules' LEDs in an active system. This toggle can be useful for quickly diagnosing the status.
**Always On (disabled)**
* Used for regular operation.
* LEDs are visible during power status changes, then return to OFF.
* Clicking the Blink icon will flash the LEDs for 2 seconds for identification. Once the blinking sequence is finished, the LEDs will return to an OFF state.
**Always On (enabled)**
* Useful when setting up a system for the first time.
* All loudspeaker module LEDs are constantly ON and show their current health and power status.
* Clicking the Blink icon will flash the LEDs for 2 seconds for identification. Once the blinking sequence is finished, the LEDs will return to an ON state.
LED indicators toggle
---
# 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://docs.holoplot.com/holoplot-control/configuring-the-system/setting-up-system-essentials.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.
