EOS in large network with multiple stages

A few ways you can approach it.

You can run concurrently using multiple users and multiple cue lists. Each stage with it's own cue lists and consoles all on the same show.  The benefit and drawback of being able to control other stages from any console if you want to (or don't know what you are doing).

You can run each console with an sACN offset on the same network. Give each console a block of 50 or 125 universes.  As primary they won't step on each other, in client you will see each console on the network you want to connect to. aRFR will see it the same.

For the TV and Movies I work on I work with the first system.  As we are sharing set builds, effects, colors and working together.  If I was not working with the same team or if other companies were also shooting these stages then I'd do version 2.

None of theese answer is what i hope for, after I worked with Cobalt.

We don´t need to share or control other stage, we just would have them in the same network because of our WIFI for remotes. We have one SSID that routes in the RFR-traffic to our lighting network, isolated from all other traffic on that network.

Option two: I have chosen to stop all sACN through my Core switch, so my 1st universe on all stage is universe 1. So I still have all universe on every stage free and not locked up on other stages. Easier when you make your setup on your DMX-nodes on every stage. :)

Is there any network port that show all the concoles in the ACN-protocol? Kill port "3030" in your coreswitch and you would't see and communicate with the consoles on other stage?

I am not sure this will do it, but if you use consoles, IonXE and upwards you have 2 network ports on them. If I'm not totally mistaken you can run one as main output on a isolated network for each stage (Maybe 10.101x.x.x, 10.102.x.x and filter on 255.255.0.0) and the 2nd you run only remotes on and then in one big network over all stages. When longing in to the remote you pick what console to connect to and then that console only output on it's own stage.

So you have one sACN V-LAN network for each stage  and one "global" network on another V-Lan for remotes.  And then you can have a remote ON/OFF macro on each console so you can turn it off during shows so that no one else can control your show. 

Maybe someone at ETC can confirm if this will work. I do not have access to my consoles right now.

It could work... but the problem is that I would have some more control in the network and see stuff that is loocked out with this solution. ;)

It was great with Cobalt and there NET-setup and software CongFuKitty... I could see all the consoles in the network, but I can´t communicate from stage to stage if I select diffrent net in the setup/startup. I had my sACN-blocker in the Core-switch and no sACN pass through to another stage. In this case I had standard setup for my stage switch and could easily change them, but I have full control.

If I isolate one networkport to WIFI and FileServer, put sACN on a separated networkport i miss to control all our DMX-nodes in the network. I use ELC 3-port and via there software I got DMX-sniffer from my office and could help collegues under reharsel whitout going down on stage. Realy nice feature when we have 8 stage in the buildning, all connected togheter, to help and figure out why something don´t work in the rig. Is´t the conosles or a fixtureproblem?

If I could stop the networktraffic on a IP-port in my coreswitch that consoles comunicate with each other, I got full control over the network but stop all the comunication between consoles on diffrent stages.

Yes, I´m probably little crazy but I like my Cobalt networksetup to much... :)

It could work... but the problem is that I would have some more control in the network and see stuff that is loocked out with this solution. ;)

It was great with Cobalt and there NET-setup and software CongFuKitty... I could see all the consoles in the network, but I can´t communicate from stage to stage if I select diffrent net in the setup/startup. I had my sACN-blocker in the Core-switch and no sACN pass through to another stage. In this case I had standard setup for my stage switch and could easily change them, but I have full control.

If I isolate one networkport to WIFI and FileServer, put sACN on a separated networkport i miss to control all our DMX-nodes in the network. I use ELC 3-port and via there software I got DMX-sniffer from my office and could help collegues under reharsel whitout going down on stage. Realy nice feature when we have 8 stage in the buildning, all connected togheter, to help and figure out why something don´t work in the rig. Is´t the conosles or a fixtureproblem?

If I could stop the networktraffic on a IP-port in my coreswitch that consoles comunicate with each other, I got full control over the network but stop all the comunication between consoles on diffrent stages.

Yes, I´m probably little crazy but I like my Cobalt networksetup to much... :)

But if they all run on two V-lans and they on Lan1 are only isolated by IP mask as in my example you can still go in and connect to the individual stages. you just need to be on the right ip range. Probably things like Concert or ELCs software will see all devices on the network without the need to be in the right IP range. Otherwise you just need to know that on stage X the IP is 10.104.x.x and log on with that setting on the compiuter.

I have no experience of doing that, so I can't say if it is a good or bad thing to have one big network with 7 parts isolated only by IP and Mask... But with only sACN it maybe works?

Not perfect but may get you where you want to.