SOLVED
Hello @DPullin
For PIM sparse mode to work it is not enough to just enable IGMP and PIM on all VLANs where sources and receivers reside. You need to define a Rendezvous Point (RP). In PIM-SM the RP for all or specific multicast group is the distribution point for the multicast forwarding. The designated router of the source will start sending the multicast to the RP and the designated routers of the receives will send their joins also to the RP.
The RP can be defined statically on every switch in the PIM domain or can be elected using boot strap routers and candidate RPs. The static method is simple but doesnt scale and doesnt allow redundancy. The dynamic is a bit more complex to configure but scales better in large environments.
You can find more details in the documentation but you didnt provide the models of your switches/routers. If it is an Aruba switch here Chapter 4 PIM-SM page 85
https://support.hpe.com/hpesc/public/docDisplay?docId=a00091313en_us
For Comware switches here for example the IP Multicast Guide of 5940 series., page 120.
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c05212291
Hello
Here is what I can add since I am also in this topic. @akg7 may add his view later.
Based on the configuration we see that source router 192.168.254.249 is the elected BSR and based on the configuration it should be also the RP for all multicast groups. But did you check with "show ip pim rp-set" if all routers see it as RP?
The command show ip pim pending is showing us that the source routers has received IGMP joins in VLAN 93 and the receiver router in VLAN 141. Pending routes in SM however should have upstream and downstream interfaces. The receiver router should select the upstream interface with the best route to the RP. The source router should be able to show downstream interfaces if some PIM neighbors requested to receive the stream so we can see which routers have joined the tree. It would be helpful to check with the following command how exactly is seen his mroute on source and receiver router.
show ip mroute [group-addr ][ source-addr]
In my eyes the configuration should be actually OK. I see that you have enabled IGMP in VLAN 400 on all 3 routers. I understand that there are no mcast receivers in VLAN 400 so IGMP is not necessary there. I am not quire sure if having it can cause any harm. Because this command enables L3 and L2 IGMP at the same time and L2 IGMP will block multicasts if there are no IGMP joins in particular VLAN. (which is the case for the central router). Maybe it wouldnt be so difficult to test what happens if IGMP is disabled on VLAN 400 on all 3 routers.
Hello,
sorry for the delayed response.
Did you try what happens if you disable IGMP on VLAN 400 on all the routers. You dont have mcast receivers there so IGMP is not needed.
I see that IP 172.20.141.1 is in the RP set. This is the IP of the destination router in VLAN 141 which is also the VLAN of the mcast receivers. The RP candidates were configured with source VLAN 400 so I am not sure how exactly this happened. Probably you tested something in between and changed the config. Maybe you can make sure that all RP candidates use the IP in the VLAN in which they have the PIM neighborhood, 400.
Anyway from what I see the static routing should be working. I assume that you have tested the ping between the multicast source and mcast receivers.
It is hard to tell if your connectivity issues are caused by PIM or something else. PM-SM should by default not route multicast traffic unless it is requested. IGMP on the receiver VLAN should make sure that multicast is only forwarded on the ports where multicast receivers are connected.