Network slows down after enabling ACN with CEM+ modules

So. I have nearly the exact same problem. 5 racks SP48 2.4k, SP6 (6k), 3 SP12 (12k) All CEM+ running 3.1.2

Ion is running the latest Beta.1.9.11 Build 23

Rack networking, but each rack is in its own group. I would have preferred to set up a group of all 5 racks, but they simply wouldn't recognize each other, and I could at least get the Ion to recognize all 5 and make adjustments from the console.

Wireless is an Apple Airpot Extreme (AAE). iPhone and iPad. Ethernet is connected from console to Ethernet LAN port (WAN is empty). Additional LAN ports feed a switch at Racks, and laptop to configure the router. 10.101.124.101 and router address 10.101.1.1. Bridge mode.

I have been through nearly every combination of trying to get the console to be the DHCP server with the AAE in bridge mode, or have the AAE as the DHCP server. Router addresses as the device's own IP and as 10.101.1.1 Subnet mask is always 255.255.0.0.

Currently iPad & iPhone each work (and only work) with static IPs 10.101.125.101 & 102 Router 10.101.1.1 Console is 10.101.100.101 AEE is 10.101.124.101, with 10.101.1.1 in

At the console networking is off, console has a manual address, with gateway as 10.101.1.1

As soon as I connect the cable running to the racks (through unmanaged ethernet switches) and ACN & DMX on, the i devices start to have a multiple second lag, and I bet the signal strength of the console would drop from 5 bars to 1 though all the CEM+s show up on the ION About screen.

This shoot lasts 4 days (and this is day 3) but I set up all of my shows with networked Sensor racks, an Ion and a wireless router. This all worked as expected until the 5.0+ phone updates. Devices are on 5.1 currently.

So I guess I am asking what am I doing wrong?

Console: 

Should network services be on? DHCP? Routered network? Gateway addresses? I have set them to the IP settings here (http://community.etcconnect.com/wikis/products/knowledgebase-etc-network-ip-addresses.aspx)

Base Station

I couldn't get it to work either receiving or sending DHCP. What should the router address be? Always 10.101.1.1 for all devices?

Finally, I suppose the cable to the racks could be the problem, but the similarity between my case and the case above makes me think not. I cannot turn off DMX since I don't have a gateway, we are shooting today, and I am controlling our racks, a bunch of Kinoflo Image 85s, and 5 installed Sensor racks of the house system on old CEMs. I am using the lower part of one universe and the upper part of another for our racks and theirs.

If this relates to why the CEM+s wouldn't talk to each other I am all for it. Last time it happened on a different job it was because of a bad CEM+ that I kept kicking up the chain as I had only one spare instead of a spare for each rack, but, I was satisfied with putting each rack in its own group. 10.101.10x.101 with gateways the same.

Any assistance would be welcome.

James McNeal

ETCP Certified Entertainment Electrician

IATSE Local #52, ACT

Programmer, HBO Films Project

As an additional note. I can access all racks through Web Connect independent of the network. In the past I could use Web Connect, ACN, iRFR all at the same time.

James

As an additional note. I can access all racks through Web Connect independent of the network. In the past I could use Web Connect, ACN, iRFR all at the same time.

James

Your description of the network sounds very confused, I think you've been running in circles for a while and lost sight of the big picture.

Next time, grab a bit of paper and sketch out exactly what is connected to where and the IP address it has. This really helps find any mistakes.

My guess is duplicate IP addresses or even a circular link somewhere.
- It is very important to have a strict star configuration with no loops*. Loops can have all kinds of strange effects.

I'm unsure what you mean by:

mcliln said:

As an additional note. I can access all racks through Web Connect independent of the network.

Do you mean that if you unplug the rack from the network and connect your laptop directly then it works, while on the main network it does not?
Most likely cause of that would be a bad cable, having eliminated that it may be duplicate IP addresses somewhere or no route from laptop to Sensor+ rack.

Ping is very useful when diagnosing network issues as it can often tell you which of those happened.

* Strictly speaking redundant links are possible with fully-managed switches, but you'd really want a computer networking specialist to set those up as they can be quite complex to fault find.

Sorry for the confusion.