Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

multicast-replication

Syntax

Hierarchy Level

Description

Configure the mode of multicast replication that helps to optimize multicast latency.

Note:

The multicast-replication statement is supported only on platforms with the enhanced-ip mode enabled.

Default

This statement is disabled by default.

Options

Note:

The ingress and the local-latency-fairness options do not apply to EVPN configurations.

ingress

Complete ingress replication of the multicast data packets where all the egress Packet Forwarding Engines receive packets from the ingress Packet Forwarding Engines directly.
local-latency-fairness

Complete parallel replication of the multicast data packets.
evpn irb local-only | local-remote | oism

Enable inter-VLAN multicast forwarding in an EVPN-VXLAN network in one of these modes:

  • evpn irb local-only—Use this mode with a collapsed IP fabric, also known as an edge-routed bridging overlay. In this mode, the PFE on the leaf devices in the fabric performs local multicast routing at the fabric edge. The spine devices, also called lean spines, primarily act as IP transit devices for the fabric.

  • evpn irb local-remote—Use this mode with a two-layer IP fabric, also known as a centrally-routed bridging overlay. In this mode, the spine devices in the fabric centrally route the multicast traffic between VLANS. The spine devices forward the routed VLAN traffic into the EVPN core toward interested receivers. The spine devices use a PIM designated router (DR) to avoid duplicating packets into the core. The leaf devices forward multicast traffic received on a VLAN to their receivers on that VLAN.

  • evpn irb oism—Use this mode with a collapsed IP fabric (edge-routed bridging overlay) to also support routing multicast traffic between the fabric and external devices. This mode implements optimized inter-subnet multicast (OISM) according to the IETF draft https://tools.ietf.org/html/draft-ietf-bess-evpn-irb-mcast-04. In this mode, the leaf devices operate in local-remote mode like in a centrally-routed bridging overlay design. At the same time, the device performs local multicast routing.

    OISM also supports:

    • Selective forwarding on the source VLAN.

    • Routing multicast traffic through an external PIM domain.

Default mode: evpn irb local-remote

You can enable only one of these modes at a time.

Note:

Only local-remote and oism modes support selective multicast (SMET) forwarding.

smet-nexthop-limit smet-nexthop-limit

Configures a limit for the number of SMET next hops for selective multicast forwarding. A PE device uses the SMET next hops list of outgoing interfaces to selectively replicate and forward multicast traffic. When the list of SMET next hops reaches this limit, the PE device stops adding new SMET next hops. At that point, the PE device sends new multicast group traffic to all egress devices.

  • Range: 10,000 through 40,000

  • Default: 10,000

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 15.1.

evpn stanza introduced in Junos OS Release 17.3R3 for QFX Series switches.

oism option in evpn irb stanza introduced in Junos OS Release 21.2R1.

Related Documentation