EOS Ti & back up console

Hi all

I am currently at the start of a medium sized production and have an Eos control system in place.

We are using an Eos Ti as the main control. I have 3 nodes and they are happy on the network. The console is out front with the 3 nodes at back stage fed through a switch. This is an unmanaged item.

My query is re the back up console. We are using an Ion 3k as a back up. When we put the console on the same switch, it is not recognised at all. No network light appears on etc, The console in ABOUT shows no IP and so on.

If I run the Ion into the second port of the EOS and assign it an IP no in the range of 2.101.***.***., it will see the console et al. We are looking to put the ION 3K on to the same switch so as to utilise the back up console properly i.e. if the EOS goes down, I would like the back up sitting on the main network so as to be utilised etc.

So to confirm, the Ion 3k is visible through the second network port from the Eos but not through the first network and related switches etc.

I am wondering if anyone could shed some light on what I may be doing wrong or have I just missed something?

All consoles, gateways et al are in the range of 10.101.***.***.

Many thanks

Eamon

Parents

0 ueliriegg over 8 years ago

when you tried to connect the ion through the switch, did you by any chance power up first and only when it was running connect to the switch?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 eamonfx over 8 years ago in reply to ueliriegg

Hi Ueli

I have recycled power a couple of times in various attempts at getting the consoles to talk to each other.

I get what you are saying re not hot swapping an ethernet cable.

I have connected the Ion direct into the switch with no avail.

I also disconnected the gateways et al and just put the Ion and the Eos on the same network via the switch. The ion does see any network activity. The only time the ion saw the eos was via the second network port on the eos.

I can run the Ion back up from the eos but this leaves me without an adequate back up etc.

To confirm, all software for the consoles is 2.4 (latest build)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 eamonfx over 8 years ago in reply to ueliriegg

Hi Ueli

I have recycled power a couple of times in various attempts at getting the consoles to talk to each other.

I get what you are saying re not hot swapping an ethernet cable.

I have connected the Ion direct into the switch with no avail.

I also disconnected the gateways et al and just put the Ion and the Eos on the same network via the switch. The ion does see any network activity. The only time the ion saw the eos was via the second network port on the eos.

I can run the Ion back up from the eos but this leaves me without an adequate back up etc.

To confirm, all software for the consoles is 2.4 (latest build)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 ueliriegg over 8 years ago in reply to eamonfx

it wasn't about hot swapping but rather booting without a network device connected.

when you connected directly to the Ti, did you use the console's other network socket? could it be that only on this other network port you have MultiConsole activated?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 eamonfx over 8 years ago in reply to ueliriegg

Hi Ueli

I see what you are saying re ether net port 1 and multi console option. Can not confirm but will check as soon as there is a break.

That is a good point.

Is there any other possible (logical...) reason as to why both would not converse over port 1? Just looking to trouble shoot in the interim. Console wont be free till lunch etc.

Thanks

Eamon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ueliriegg over 8 years ago in reply to eamonfx

the only thing i know that is different with port 1 is that Wake on LAN only works on port 1. all the rest should work on both, i suppose. provided the respective protocols are activated..

and it could of course be other minor stuff. i.e. did you use a different network cable when connecting to the switch and when connecting to the Ti?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 eamonfx over 8 years ago in reply to ueliriegg

Hi again

yes, did the swap of cables and checked the usual et al.

Reckon the multi console option might be the best port of call..

Many thanks and I hope to come back with some positive news.

Eamon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 eamonfx over 8 years ago in reply to eamonfx

Hi

Have had a quick look at the set up.

The multi console option is selected and there seems nothing on toward in the set up. I could be wrong though.

I am a tad stumped!

Eamon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 eamonfx over 8 years ago in reply to eamonfx

One other thing I do not have set up; There is no default gateway listed...

Would/should I have this assigned to a range?

eamon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ueliriegg over 8 years ago in reply to eamonfx

if you're in ETC's IP-world the default gateway would be 10.101.1.1
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 KevinSmith over 8 years ago in reply to ueliriegg

We also ran with a default gateway assigned 10.101.1.1 to no luck

It also worth noting that we have a Nomad client running successfully. So the network is communicating with multi-console setup.
Originally this client was into the switch on the 10.101.xxx.xxx range with the master Ti port 1 in the same 10.101 range.
I now have the Nomad running directly into the Ti on the 2nd port both on the 2.101.xxx.xxx range so it's definitely not a multi console issue on either port on the Ti.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jay over 8 years ago in reply to KevinSmith

Just as a test, can you run ion as master and eos as backup with all wires and ip addresses as you want for the ideal. If that works, go back to eos as main, ping eos from ion. Make sure subnets are correct. Weird.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 eamonfx over 8 years ago in reply to Jay

Hi all

Managed to sort this issue.

Having spoken to another programmer, they gave me an idea of what I might have been doing wrong.

I have now placed a second network switch at the FOH position. This has cured all the problems and the back up and primary are now talking.
I was under the belief that the ethernet ports on the TI were still switches like the classics. This is not the case and that is where I was being tripped up. With the second network switch at FOH, communication happened instantly.

Have to read up more on my networking!

Many thanks to all who posed suggestions and help.

Eamon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel