Hi LEEBAHI
>A single homed MCAST receiver lives behind L1 while there is no receiver behind L2.
I checked your topology. Does a MCAST receiver live behind L2?
Both of your packet captures looks like that source IP is 3.3.3.3 and dst IP is 2.2.2.2. I think this is correct.
>Also why does JUNOS recommends using IGMP proxy ? what problem are we solving using this knob in this multicast case?
If you don't use EVPN type6 route, you will use EVPN type3 route. When you use EVPN type3 route for Multicast traffic, BUM traffic increases.
Furthermore, when you use EVPN type6 route, you can alse use Multicast Optimization called Assisted Replication.
Please refer bellow.
https://www.juniper.net/documentation/us/en/software/junos/evpn/topics/topic-map/assisted-replication-evpn.html
------------------------------
RYOTA KOSAKA
------------------------------
Original Message:
Sent: 12-27-2024 18:45
From: LEEBAHI
Subject: EVPN NLRI 6 purpose
Hi everyone,
I am trying to learn the purpose of EVPN NLRI 6. Please consider the following case:
A single homed MCAST receiver lives behind L1 while there is no receiver behind L2. MCAST-SRC behind L3 is generating MCAST stream for 238.1.1.1. In this case, L3 will perform ingress-replication and unicast this MCAST traffic to both L1 and L2 . L1 ends up receving MCAST while it has no receiver.
Using EVPN NLRI6 along with igmp snooping will fix this problem.
We enable igmp-snooping for vlan 199 on L1/L2 and L3. MCAST-SRC is still sending MCAST stream at 238.1.1.1 . Since L2 has MCAST receiver for 238.1.1.1 , therefore, it has advertised NLRI 6 to both L1 and L3. L3 will only perform ingress-replication towards L2.

Observed behavior:
L3 does ingress-replication to L1 and L2 even though it is only L2 which has advertised NLRI6 route.
Packet capture taken on L3 ge-0/0/0 :
Ingress replication from L3 to L1( 3.3.3.3-->1.1.1.1):

Ingress replication to L2 from L3 ( 3.3.3.3->2.2.2.2)

Am I missing anything in my config?
Also why does JUNOS recommends using IGMP proxy ? what problem are we solving using this knob in this multicast case?
Much appreciated!!

Configs:



------------------------------
Be kind!!
------------------------------