MediaMatrix nTouch 60 Manuel télécharger pdf (Page 60)

Chapter 6 - Using XDAB clusters with VLANs and CobraNet

56 Version 1.6.2a.0 May 17, 2011

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.

Setting conductor and XDAB priority in NWare

Introduction

You can use NWare to change the CobraNet Conductor and XDAB master priorities. These

settings will ensure that a particular device within an XDAB cluster will become the XDAB

master or that a particular CobraNet device on a network or VLAN segment will become a

CobraNet Conductor.

1 2 ... 55 56 57 58 59 60 61 62 63 64 65 ... 97 98

Pas de commentaire

MediaMatrix nTouch 60 Manuel Page 60