Peavey MediaMatrix Nion, Hardware Manual

Page: 56 / 94

Chapter 6 - Using XDAB clusters with VLANs and CobraNet
52 Version 1.6.1.0 September 30, 2010
This scenario is a variant of the previous scenario (on page 51), but contains more than one
XDAB cluster.
ƒ The same rules apply as in the previous scenario.
ƒ Again, the Conductor for VLAN 2 must be within the XDAB cluster.
ƒ It does not matter which cluster the Conductors are in. In this case, the Conductors are
show in cluster 1.
ƒ In this example, it does not matter which device in cluster 2 is the XDAB master. The
XDAB master will receive its audio clock from a CobraNet Conductor in either VLAN 2
or VLAN 1, both of which are in sync with each other.
ƒ The clock received by any device in cluster 2 via CobraNet will be the same because the
Conductors for both VLANs are in cluster 1 and are synched to the same clock.
Scenario 9 - Network with VLAN and three XDAB clusters
In this scenario, there are three VLANs, three XDAB clusters and no cluster contains all three
VLANs.
ƒ In cluster 1, VLAN 1 contains the XDAB master.
ƒ In cluster 1, VLAN 2 receives its clock from XDAB and is therefore in sync with VLAN 1.
ƒ In cluster 2, VLAN 1 is the XDAB master and receives its clock from the VLAN 1
Conductor in cluster 1.
ƒ In cluster 2, VLAN 3 receives its clock from XDAB. This clock is derived from the
Conductor of VLAN 1.
ƒ In cluster 2, one of the devices in VLAN 3 is the Conductor for VLAN 3.
ƒ In cluster 3, VLAN 3 is the XDAB master and receives its clock from the Conductor in
VLAN 3 in cluster 2.
ƒ In cluster 3, VLAN 2 is receiving its clock from the XDAB master in VLAN 3.
ƒ All Conductors in this topology are ultimately deriving their clocks from the Conductor
and XDAB master in VLAN 1 of cluster 1. So all clocks in this network in all three
VLANs will be in sync. No clock conflicts will exist.