Hardware manual
Table Of Contents
- Cover Page
- Contents
- About this guide
- Safety Instructions and safety warnings
- Before you start
- Introduction to NION
- Setting up the NION
- Introduction
- Configuration
- Updating the firmware
- Using the front panel
- Using the web interface
- Using XDAB clusters with VLANs and CobraNet
- Introduction
- Important concepts
- Use cases
- Scenario 1 - Basic network
- Scenario 2 - Network using VLAN
- Scenario 3 - Network with VLAN and analog interconnects
- Scenario 4 - Network with VLAN and digital interconnects
- Scenario 5 - Network with an XDAB cluster
- Scenario 6 - Network with VLAN and XDAB
- Scenario 7 - Network with VLAN and XDAB
- Scenario 8 - Network with VLAN and two XDAB clusters
- Scenario 9 - Network with VLAN and three XDAB clusters
- Setting conductor and XDAB priority in NWare
- Further examples
- Troubleshooting
- Connector ports
- Technical specifications
- Reference Information
- Warranty statement
NION Hardware Manual
May 17, 2011 Version 1.6.2a.0 53
Scenario 6 - Network with VLAN and XDAB
In this scenario, the network is divided into VLANs and an XDAB cluster is used. Two
VLANs are shown; more are possible.
XDAB is used to pass digital audio between NIONs within a cluster and therefore between
VLANs.
VLANs logically become one of two types in this scenario:
A master VLAN, i.e. the VLAN in which the XDAB master resides.
A slave VLAN, i.e. all other VLANs in the cluster.
The Conductor on the one master VLAN must be either:
completely outside the XDAB cluster
or
must also be the XDAB master.
The same caveats regarding Conductor location as described in the previous scenario (on
page 52) must be observed. But it is also important to properly locate the CobraNet
Conductors for the slave VLAN (VLAN 2) to be sure that a clocking conflict is not created
between XDAB and VLAN 2’s CobraNet clock.
Regardless of whether the VLAN 1 Conductor is inside or outside of the cluster, all
NIONS in the cluster that are in VLAN 2 will be getting their clock from XDAB and
cannot receive their clock from an outside Conductor. This would create a clocking
conflict.
Therefore, the Conductor for VLAN 2 must be located within the XDAB cluster, as
shown.