SOLVED
Hello,
There is no separate command for enabling IGMP snooping on this platform. The command "ip igmp" in VLAN context enables both. If the VLAN doesnt have IP address only IGMP snopping is enabled, if there is IP in the VLAN the switch can also act as L3 IGMP snooping quierier.
You have provided only the configuration of VLAN 1 on all 3 switches. Does it mean that your multicast streamer Avercaster SE510 Lite AND the multicast receivers are both connected to ports in the same VLAN 1?
If this is the case then you actually don't need PIM at all. PIM is mutlicast routing protocol. If both multicast source and receivers are in the same VLAN no multicast routing is necessary even if the source and receivers are separated by multiple switches. IGMP should be sufficient for L2 multicast forwarding. PIM is necessary when sources and receivers are in different VLANs.
PIM dense mode has the advantage that is is much easier to configure. You just enable PIM al all interfaces which should forward the multicast. The disadventage is that a PIM dense router will flood the multicast to all its PIM neighbors by default until the neigbors indicate that they dont need it. But this shouldnt actually affect the performace of the multicast receivers. It would affect other devices in the network because they receive mutlicast they dont need.
PIM sparse will only forward multicasts to PIM neighbors which explicitly request it. So it is more efficient in environments with bandwidth restrictions. But PIM sparse has more complex configuration. You need to have RP which can be statically or dynamically configured. For dynamic RP allocation you also need to configure BSR routers. Troubleshooting is also a bit more complex.
There are a lot of differences in the configuration of PIM sparse and dense mode. You specify the mode as pim-sparse and pim-dense in the VLAN context. For PIM-sparse you need to have RPs. They can be statically configured on all PIM routers or you can use candidate RP and BSR routers. This is more something for complex environments.
You can find more details about the Multicast protocols in the Aruba Multicast and Routing guide.
https://www.hpe.com/psnow/doc/a00091313en_us
Hello,
If the multicast stream has to be forwarded to wireless users in VLAN 101 then you need PIM on the router indeed. To be honest I havenāt seen by now PIM sparse mode running on a single multicast routing switch. Dense mode should be sufficient here and the adventages of sparse mode are achieved in more complex environments.
The idea of having a RP address is that all the multicast routers in the network know the RP as a predefined root point of the multicast tree so that they can join the multicast tree as soon as they have receivers even if the source didnt start streaming yet. In your case probably it will be sufficient to define the IP of the router in VLAN 1 as RP for all groups.
Yes, the end devices have sent joins for other multicast groups as well.
224.0.1.60 is assigned to hp-device-disc (this should be a group used by HP printers)
224.0.6.151 Canon-Device-Control (probably a group used by Canon devices).
239.255.255.250 SSDP (simple service discovery protocol, this is a zero configuration protocol similar to mDNS Bonjour)
239.255.255.253 ā SLPv2 Discovery (Service Location Protocol v2)
Couldnt find information on the other groups. This may be traffic which is needed for the proper functioning of the devices. If you determine that some type of application is consuming too much bandwidth you can filter it using ACL. Here is an example on how to stop SSDP packets from getting into the switch.
Here is another example on how to block IGMP traffic. In this case it blocks every group but of course it can be adapter to block only certain groups.
https://community.arubanetworks.com/blogs/esupport1/2018/10/03/acl-to-block-igmp-traffic-on-2530