Issue with sCAN out putting to a node

Thank you for providing the network map. This helps a lot!

Haven't dug into the logs yet, but would you mind listing the make and models of your three unmanaged switches?

the POE and booth switches are TP-link, TL-SG1218MP(poe) and TL-SG116. Tech Table is Trendnet Teg-S50g

Also just an update, we have taken the Puck (our backup) out of the equation and it everything has worked as normal. would you like the logs for the puck (backup)?

so adding to this as this is still an issue. I have used wireshark and everything is outputting on the perspective universes until the puck (backup) loads the show file from the primary console. i have control of everything i need with no issues and no intermitted sACN interruptions until the puck loads. 

Sorry about that.

The problem you're seeing is a short interruption when the backup takes over from the primary? Or is the problem that the backup doesn't successfully take over at all?

Could you post a photo of the About Screen of the Puck when it is connected to the
IonXE20? I am wondering if the Puck doesn't have enough universes, and is limiting

the IonXE20 addresses when it connects.

The other concern that I have is that the "smart" Unmanaged Switch TL-SG1218MP utilzes an industry standard of 802.1p/DHCP QoS which is a Quality of Service (QoS) process defined within the IEEE 802.1Q standard. The technique uses a three-bit field within an Ethernet frame header to assign priority levels to packets moving within a network segment. With the technique, this priority value is used to differentiate traffic. It directs the switches to automatically give priority to certain traffic like for example voice packets and also other traffic, which means other data can be intermittently interrupted.
Such "Smart" unmanaged switches are optimized for office use where VOIP/Webbrowser are main uses, and unfortunately doesn't allow for this prioritization to be disabled. At least I couldn't find a manual that allows that for this switch. Such "smart" unmanaged switches can start causing problems in networks much later than when they were first commissioned and not recommended for lighting networks.

It’s not when the puck takes over, it’s when the puck boots and scans for the primary and retrieves the show file from the primary. I have seemed to find a fix and unicast the sACN universes to the proper nodes. Will hear back from my board op tomorrow to see if it happens again. 

Thanks for the info! We are only outputting two universes worth of data over four universes and the only affected universe is the first. I believe the puck can output 4 total universes, will check tomorrow when I’m in the space.

The only node that’s affected is a node going through a 16 port unmanaged netgear switch.  The other thing is that after about a minute of waiting the first universe comes right back up. 

I have seemed to find a “fix” and unicast the sACN to the prospective nodes. Will know more tomorrow when my board op comes in tomorrow. 

Hi Brandon

So it sounds more like an issue in the network than in the Puck. All the same - could you send a screenshot of the Puck About screen when connected as Backup in the showfile where the problem occurs - where the Total channel count, software version, etc can be seen like this :

But this is probably all fine - as said, I feel that QoS (Quality of Service) functions in your "smart" unmanaged switch is causing the pausing of sACN output to the nodes intermittently. I don't think its possible to disable or modifiy the QoS Settings in your switch TL-SG116 or TL-SG1218MP(poe). Can you check your switch manuals if its possible to disable these settings? If not, can you source a real unmanaged Switch with no QoS functions for troubleshooting here and put in your control room between the Ion+Puck and the Nodes for U1 and U2?

Thanks.

Also - I just noticed your data from Ion+Puck that go through a Switch then go thru a router before getting to the Node with U1 + U2 Outputs. What is the make/model of this router?