Dante replaces all of those connections with a computer network, effortlessly sending video or hundreds of channels of audio over slender Ethernet cables with perfect digital fidelity. All connections are now managed with software, making routes fast, readable and reliable. Because all devices share the same network, signals can be sent between any devices no matter where they are located on a site, with no change to the wiring at all. Dante systems are easily expanded, exactly as one might add a printer to a network. Just connect additional devices to any available network jack and start using it. (https://www.audinate.com/meet-dante/what-is-dante)
CCCC Uses Dante pervasivly in the Tech Booth and we expect it to expand into other areas also.
The problem is that the network switches that carry Dante traffic must be managed (some currently are not) and must be specifically configured for Dante. Dante uses IGMP, PTP, and QoS (and other things) to create the environment necessary for it to function.
Dante began being implemented before we were aware of the switch requirements, and one of the problems was that the Dante enabled devices were spewing multicast packets to the point they were using upto 97% of the LAN bandwidth.
After a bunch of research I have collected the steps necessary for the Cisco SG300 switch, and will implemented them shortly. These same steps may be necessary for the Engenius switch in the tech booth, and anywhere else Dante devices will be used.
The Switch must support;
Dante uses UDP primarily;
IPv4 multicast groups are mapped to MAC 01:00:5E:00:00:00 through 01:00:5E:7F:FF:FF
224.0.0.0/24 is a broadcast, but not registered with IGMP.
The above tables were copied from https://www.audinate.com/learning/faqs/which-network-ports-does-dante-use
Dante Updater
(old devices)
The above table was copied from https://www.audinate.com/learning/faqs/which-network-ports-does-dante-use
