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
Chapter 6 - Using XDAB clusters with VLANs and CobraNet
54 Version 1.6.2a.0 May 17, 2011
Scenario 7 - Network with VLAN and XDAB
This scenario is a variant of the previous scenario (on page 53).
The Conductor for VLAN1 is outside the XDAB cluster. This will still work.
The CobraNet interface in the XDAB master will sync to the Conductor outside the
cluster. That clock will become the XDAB master clock. XDAB and VLAN 1 will be in
sync.
However, the Conductor for VLAN 2 must still remain within the cluster because all
XDAB slaves in a cluster will receive their clock from XDAB and not from CobraNet.
Placement of VLAN 2’s Conductor outside the cluster will cause the XDAB clock and
externally sourced VLAN 2 CobraNet clock to be in conflict.