New to Crestron and MULTICAST #crestron #cp4


 

Hi there
We are a hybrid user and I'm wondering how do I get MULTICASTING to work on our network. I have designed one vlan for all of the crestron devices so they can be segmented away from the network.

Our setup involves a LUXUL switch in 5 classrooms trunked to 5 different network switches (all Juniper) These junipers then connect via fiber to our ARUBA8325 cores that has a ARUBA6330M attached that hosts the CrestronNVX director.
My question is how do I ensure that we do not experience LAG? Do I need to have igmp enabled on all of the switches? The edge juniper, the core, the aruba6330m? Our setup isnt complex I just need some guidance


 
Змінено

As far as I know, the DM-NVX-series is the only Crestron device that uses multicast and IGMP snooping and the associated stuff that goes with that.  Since you are using an CrestronNVX director, you are almost certainly using DM-NVX-xxx equipment. So to answer your question, yes you need to enable IGMP snooping on all the switches that NVX is passing through.

Many switches are not compatible with NVX -- particularly if you are planning to run NVX between switches. In particular, you need to make sure your links between switches have enough bandwidth to handle all the NVX traffic summed together.  You might want to look at the following for the NVX requirements:
https://www.crestron.com/getmedia/94a25ed5-6580-48df-a152-4cdc043820ed/dm_nvx_network_min_requirements


But if you are not using DM-NVX, you don't need to do IGMP snooping.  You can, but it is not a requirement.


 

Enable IGMP querier on the switch lowest in the STP. (Only one querier should be enabled).  All other switches can have IGMP snooping enabled and will properly identify the multicast traffic. 


 

Since most IGMP Querier implementations route all traffic to the querier, unless you have oversized uplinks it can actually be a better practice to enable the querier on the switch closest to the majority of the encoders to help limit link saturation issues. But there should always be 1 and not more than one querier for each VL that IGMP snooping is enabled on.

 

Also though I haven’t seen it yet (and seems unlikely I’ll come across it given the types of projects I typically do) but I believe NAX uses the same network concepts as NVX

 

--

Lincoln King-Cliby, CTS, DMC-E-4K/T/D
Commercial Market Director
Sr. Systems Architect | Crestron Certified Master Programmer (Diamond)
ControlWorks Consulting, LLC
Direct: (+1)440.771.4807 | Cleveland: (+1)440.449.1100  | Boston: (+1)508.695.0188 | DC: (+1)202.381.9070  | Fax: (+1)440.449.1106
Crestron Services Provider | Biamp Authorized Independent Programmers | Extron Qualified Independent Programmer

 

From: crestron@groups.io [mailto:crestron@groups.io] On Behalf Of Cortlin Dillon
Sent: Friday, August 13, 2021 1:12 AM
To: crestron@groups.io
Subject: Re: [crestron] New to Crestron and MULTICAST #cp4 #crestron

 

Enable IGMP querier on the switch lowest in the STP. (Only one querier should be enabled).  All other switches can have IGMP snooping enabled and will properly identify the multicast traffic. 


 
Змінено

Thanks so much!

 So the vlan we have is VLAN2199 which is on all of the connnecting switches.

I was going to enable igmp snooping on VLAN2199 on every switch (juniper) where a LUXUL (switch they bought for the crestron classrooms) including our Aruba Core. 

Like I said each LUXUL switch is already configured for IGMP but it is trunked to a JUNIPER switch then connected back to our two core switches which houses the DM-NXV box on a edge switch. Can't I just put igmp snooping on all of the switches with vlan2199 (two cores, the aruba edge switch that connects to the nvx and the switches where there are trunk links to the crestron classrooms (LUXUL)? Would that mitigate any issues? Thanks again for everything!

Thanks for everything thus far!


 

If you are using VLANs, it is highly unlikely the switches are preconfigured  for the VLAN2199.  At least with the switches I use, you have tell the switch which VLANs to use for IGMP snooping and querier.  Also you have to set the multicast router port on all switches to specify which ports are connected to other switches.  I believe most switches that come preconfigured, are only configured for VLAN1.  I may however be wrong because all the switches I have used are not preconfigured for IGMP snooping.

If you have ffmpeg installed on your computers, you can use it to test if the multicast is working.  It beats using NVX for the test because it won't overwhelm your network like NVX will.   The commands I used are:

For the server:

ffmpeg -re -i myvideo.mp4 -vcodec mpeg4 -f mpegts udp://239.255.0.8:23000

 

For the client:

ffplay udp://239.255.0.8:23000

Note that while you may have a firewall blocking port 23000 on the server and it will still stream, on the client, you must allow port 23000 to pass the firewall in order to stream.


 

So the typical set up for a Crestron Room is:
Luxul Switch trunked to a Juniper Switch

Juniper Switch trunked to Aruba Cores

Aruba Cores trunked to Aruba 6330M

Aruba 6330M that has the NVX connected to it.

All paths have VLAN 2199 on it. Does each device along the way need igmp snooping enabled? The LUXUL switch is already configured for igmp snooping as well as the quieter.

LUXUL Switch where the end points are (All configured as per the installer)
The Luxul switch is trunked to a Juniper Switch which is trunked to our Aruba Core which is trunks to an Aruba6300M that is connected to the NVX. I do know they were complaining about Lag from the NVX back to the Classroom. Again I am new to this so I am wondering if enabling igmp snooping on vlan2199 on the ARUBA Cores, ARUBA EDGE as well as the JUNIPER's that are connected to the LUXUL switch. Would this resolve the latency/lag issue? Thanks again so far!


 

Since you are referring to LAG,it sounds like you are having an issue with insufficient bandwidth on your trunk line and you have having to use multiple fiber links to get the uplink bandwidth up to handle the NVX traffic.  If that is the case, it would be best to home run all the NVX stuff to one Ethernet switch to keep the multicast traffic from clogging up your uplinks.  Of course, that is assuming you have the infrastructure to do that or that it can be easily added.  For NVX units that are over 100m away, consider running a home run fiber to each distance DM-NVX unit.  Most DM-NVX have a SFP port just for that purpose.  Running DM-NVX between multiple switch add a whole lot more complexity to the network and usually requires very specialize switches that can handle it.

If you haven't taken Crestron training on the DM-NVX, I highly recommend that you take that course.  It goes into all the stuff required to implement NVX and it is one of the best courses I have taken.  Well worth the time.