Peavey MediaMatrix NION Hardware Manual page 54

Chapter 6 - Using XDAB clusters with VLANs and CobraNet
An XDAB master that gets its clock as a CobraNet performer that is synched to a
Conductor that is in turn an XDAB slave would create an unstable clock resolution loop.
XDAB would attempt to sync with CobraNet that would in turn be trying to sync with
XDAB.
The XDAB master and CobraNet Conductor will both be in the same NION automatically
when default settings are used. If default settings are changed, then be sure to set the
XDAB priority and CobraNet Conductor priority to insure that a single NION is both the
XDAB master and CobraNet Conductor.
Notes:
If the Conductor is placed within the cluster, then it must also be in the same NION as the
XDAB master. If you increase the Conductor priority for one of the NIONs, you must also
increase its XDAB priority to insure that the Conductor and XDAB master will stay in the
same NION.
If a Conductor for a CobraNet network is placed within an XDAB cluster, the NION
containing the Conductor must also be the XDAB master.
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 49) 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.
50 Version 1.6.1.0 September 30, 2010