Receiver: set protocols sap listen group 188.8.131.52 set protocols igmp interface [int | all] static group 184.108.40.206
Where I run Pim I do see the join filtering upwards but still no response from receiver. The routing table is fully converged. One point that comes to mind is 'chassis fpc 0 pic 0 tunnel-services bandwidth 1g' - I have this in notes but it is unclear if this goes on everyone particapating in multicasting? just the source? everyone but the receiver? I notice that it also affects auto-rp negatively, so should it just be configured on customer-facing interfaces? if so how would I handle a vmx vFP with only one pic?
I have deployed 18.2 version vMX's and am still not getting either adjacent neighbor pings through or responses from within the chassis itself. Very simple configuration in use, receiver pasted in below, source is similar without igmp or sap. ping command is "run ping 220.127.116.11 ttl 10 bypass-routing interface ge-0/0/0.0 source 18.104.22.168", similar ping when run on the receiver. Chassis Network-service is enhanced-ip. one control-plane one forwarding-plane. Unicast scope pings are working, ospf is converged, source igmp is aware of the static groups on receiver. Using a vmx trial license newly installed.
set chassis fpc 0 lite-mode
set chassis network-services enhanced-ip
set interfaces ge-0/0/0 unit 0 family inet address 10.1.2.2/24
set interfaces lo0 unit 0 family inet address 22.214.171.124/32
set protocols igmp interface ge-0/0/0.0 static group 126.96.36.199
set protocols sap listen 188.8.131.52
set protocols sap listen 184.108.40.206
set protocols sap listen 220.127.116.11
set protocols sap listen 18.104.22.168
set protocols ospf area 0.0.0.0 interface ge-0/0/1.0
set protocols ospf area 0.0.0.0 interface ge-0/0/0.0
set protocols ospf area 0.0.0.0 interface lo0.0