EVPN

IPv4 multicast with IGMPv3 and IPv6 multicast with MLDv1 and MLDv2 in EVPN-VXLAN–centrally routed bridging overlay fabrics (EX4300-48MP, EX4400-48MP, EX4400-24MP, EX4400-48P, EX4400-48T, EX4400-24P, EX4400-24T, EX4400-48F)—Starting in Junos OS Release 23.1R1, you can configure multicast with Internet Group Management Protocol version 3 (IGMPv3) and Multicast Listener Discovery versions 1 (MLDv1) and 2 (MLDv2) in an Ethernet VPN–Virtual Extensible LAN (EVPN-VXLAN) centrally routed bridging (CRB) overlay fabric. With this feature, you can enable multihoming for the following IPv4 and IPv6 multicast traffic use cases:

• Intra-VLAN forwarding

• Inter-VLAN routing

IGMPv3 or MLD multicast works with these multicast optimizations:

• IGMP or MLD snooping

• Selective multicast Ethernet tag (SMET) forwarding

• Assisted replication (AR)

These devices process:

• MLDv1 reports as any-source multicast (ASM) (*,G) reports

• MLDv2 reports in one of these modes:

  • Any-source multicast (ASM) (*,G) reports by default

  • Source-specific multicast (SSM) (S,G) reports (only if you explicitly configure this mode)

These devices process IGMPv3 reports in one of two modes:

• Any-source multicast (ASM) (*,G) reports by default

• Source-specific multicast (SSM) (S,G) reports when you explicitly configure this mode

[See Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN, Overview of Selective Multicast Forwarding, Assisted Replication Multicast Optimization in EVPN Networks Environment, and evpn-ssm-reports-only.]

Determine IRB interface state changes based on local and remote connectivity states in EVPN fabrics (EX4300-MP, EX4400-48MP, EX4650, MX204, MX240, MX480, MX960, MX2010, MX2020, vMX, QFX5110, QFX5120-48T, QFX5120-48Y, QFX5210, QFX10002, QFX10002-60, and QFX10008)—Starting in Junos OS Release 23.1R1, the provider edge (PE) devices in an EVPN fabric consider the following factors when determining the state (up or down) of an L3 integrated routing and bridging (IRB) interface. These factors apply to an L3 IRB interface that is associated with a bridge domain or a VLAN in an EVPN instance (EVI).

• Associated local L2 interface states

  To customize the L2 interface name and other parameters that the device uses to compute the IRB interface state, configure the interface-state statement at the [edit interfaces irb unit n] hierarchy.

• Remote provider edge (PE) device reachability based on the network isolation state of the bridge domain or the EVI

  The device includes the states of the associated EVPN overlay tunnel interfaces in the network isolation state evaluation.

  To define the parameters that determine when an EVI or a bridge domain is in a network isolation state:

  1. Configure the network-isolation group group-name statement at the [edit protocols] hierarchy level to define a network isolation profile using the available options.

  2. Assign the network isolation group profile to a bridge domain or an EVI using the network-isolation-profile group network-isolation-group-name statement at these hierarchy levels:

     • Bridge domain—[edit bridge-domain bd-name bridge-options]

     • EVI—[edit routing-instance instance-name switch-options]

[See Determine IRB Interface State Changes from Local and Remote Connectivity States in EVPN Fabrics, interface-state, and network-isolation.]