OISM to MVPN/PIM interworking (MEG/PEG function) with MLDP I-PMSI

This chapter provides information about Optimized Intersubnet Multicast (OISM) to Multicast VPN/Protocol Independent Multicast (MVPN/PIM) interworking (using the MVPN to EVPN Gateway/PIM to EVPN Gateway (MEG/PEG) functions) with Multicast Label Distribution Protocol (MLDP) Inclusive Provider Multicast Service Interface (I-PMSI).

Topics in this chapter include:

Applicability

The information and configuration in this chapter are based on SR OS Release 24.10.R2. Only on FP-based platforms, SR OS Release 22.2.R2 and later support MLDP I-PMSI.

Overview

SR OS Release 21.10.R1 and later support OISM EVPN interworking with MVPN and PIM networks. Two key interworking functions are used to achieve this interworking:
  • MEG (MVPN to EVPN Gateway): Bridges MVPN and EVPN.
  • PEG (PIM to EVPN Gateway): Bridges PIM and EVPN.
The system uses a Designated Router (DR) election process to ensure redundancy. This is achieved by:
  • Including the Designated Forwarder (DF) Election extended community in the Inclusive Multicast Ethernet Tag (IMET) routes.
  • Following the DR selection procedures defined in RFC 8584.

After being elected, the MEG/PEG routers use Ingress Replication (IR) to handle multicast (MC) traffic efficiently within supplementary broadcast domains (SBDs).

In addition to IR and only on FP-based platforms, SR OS Release 22.2.R2 and later also support MLDP root-and-leaf (See P2MP mLDP Tunnels for BUM Traffic in EVPN-MPLS Services for more details) on the SBD of the MEG/PEG routers. On a MEG/PEG router, traffic originating from either the MVPN/PIM domain or the EVPN domain can be forwarded or received by the MEG/PEG DR through an MLDP provider tunnel. The PIM Instance can be in MVPN.

Example topology is used to illustrate the working of OISM EVPN to MVPN/PIM interworking with MLDP I-PMSI.
Figure 1. Example topology

PE-2 and PE-3 connect an OISM EVPN network hosting PE-5 and PE-6, and an MVPN/PIM network hosting PE-7 and PE-8. PE-2 and PE-3 act as MEG/PEG DR candidates. PE-2 and PE-3 forward traffic into the EVPN using MLDP I-PMSIs. An MC receiver connected to PE-6 in the EVPN network joins MC group 225.0.0.1 of an MC source connected to PE-8 in the MVPN/PIM network to receive MC traffic from the MC source. An MC receiver connected to PE-7 in the MVPN/PIM network joins MC group 239.0.0.4 of an MC source connected to PE-5 in the EVPN network to receive MC traffic from the MC source. All PEs exchange BGP messages via a BGP route reflector RR-1 that is connected to PE-2.

The EVPN MPLS services use provider-tunnel inclusive. The owner must be configured as bgp-evpn-mpls. Other options are bgp-ad, bgp-vpls, or no owner configured (default). If bgp-evpn-mpls and bgp-vpls are enabled in the same service, they are mutually exclusive with provider-tunnel. If bgp-evpn-mpls and bgp-ad coexist in the same service, only bgp-evpn-mpls can be the provider-tunnel inclusive owner.

The provider tunnel in the EVPN MPLS services uses the incl-mcast advertise-ingress-replication configuration to determine the Inclusive Multicast route PMSI Tunnel Attribute (PTA) type:
  • incl-mcast advertise-ingress-replication false: the PE does not send IMET-IR or IMET-P2MP-IR routes
  • incl-mcast advertise-ingress-replication true (default)
    • if root-and-leaf is not configured or root-and-leaf false is configured (default): the PE sends an IMET-IR route
    • if root-and-leaf true is configured: the PE sends an IMET-P2MP-IR composite tunnel route

Configuration

The initial configuration includes:
  • cards, MDAs, ports
  • BGP route reflector (RR)
  • router interfaces
  • IBGP in the EVPN network for the EVPN address family
  • IBGP in the MVPN/PIM network for the VPN IPv4 and MVPN IPv4 address families
  • IS-IS on the router interfaces (OSPF or OSPF3 router interfaces are also possible)
  • LDP and MPLS in the EVPN and MVPN/PIM networks (not on the RR)

Router configuration

The router configuration on PE-2 is as follows:
# On PE-2:
configure {
    router "Base" {
        interface "int-PE-2-PE-3" {
            port 1/1/c3/1
            ipv4 {
                primary {
                    address 192.168.23.1
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:23:1 {
                    prefix-length 126
                }
            }
        }
        interface "int-PE-2-PE-5" {
            port 1/1/c5/1
            ipv4 {
                primary {
                    address 192.168.25.1
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:25:1 {
                    prefix-length 126
                }
            }
        }
        interface "int-PE-2-PE-6" {
            port 1/1/c6/1
            ipv4 {
                primary {
                    address 192.168.26.1
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:26:1 {
                    prefix-length 126
                }
            }
        }
        interface "int-PE-2-PE-7" {
            port 1/1/c7/1
            ipv4 {
                primary {
                    address 192.168.27.1
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:27:1 {
                    prefix-length 126
                }
            }
        }
        interface "int-PE-2-PE-8" {
            port 1/1/c8/1
            ipv4 {
                primary {
                    address 192.168.28.1
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:28:1 {
                    prefix-length 126
                }
            }
        }
        interface "int-PE-2-RR-1" {
            port 1/1/c1/1
            ipv4 {
                primary {
                    address 192.168.12.2
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:12:2 {
                    prefix-length 126
                }
            }
        }
        interface "system" {
            ipv4 {
                primary {
                    address 192.0.2.2
                    prefix-length 32
                }
            }
            ipv6 {
                address 2001:db8::2:2 {
                    prefix-length 128
                }
            }
        }
        isis 0 {
            admin-state enable
            advertise-router-capability as
            ipv6-routing native
            level-capability 2
            traffic-engineering true
            area-address [49.0001]
            traffic-engineering-options {
                ipv6 true
                application-link-attributes { }
            }
            interface "int-PE-2-PE-3" {
                interface-type point-to-point
            }
            interface "int-PE-2-PE-5" {
                interface-type point-to-point
            }
            interface "int-PE-2-PE-6" {
                interface-type point-to-point
            }
            interface "int-PE-2-PE-7" {
                interface-type point-to-point
            }
            interface "int-PE-2-PE-8" {
                interface-type point-to-point
            }
            interface "int-PE-2-RR-1" {
                interface-type point-to-point
            }
            interface "system" { }
            level 2 {
                wide-metrics-only true
            }
        }
        ldp {
            interface-parameters {
                interface "int-PE-2-PE-3" {
                    ipv4 { }
                    ipv6 { }
                }
                interface "int-PE-2-PE-5" {
                    ipv4 { }
                    ipv6 { }
                }
                interface "int-PE-2-PE-6" {
                    ipv4 { }
                    ipv6 { }
                }
                interface "int-PE-2-PE-7" {
                    ipv4 { }
                    ipv6 { }
                }
                interface "int-PE-2-PE-8" {
                    ipv4 { }
                    ipv6 { }
                }
            }
        }
        mpls {
            admin-state enable
            interface "int-PE-2-PE-3" { }
            interface "int-PE-2-PE-5" { }
            interface "int-PE-2-PE-6" { }
            interface "int-PE-2-PE-7" { }
            interface "int-PE-2-PE-8" { }
        }
        rsvp {
            interface "int-PE-2-PE-3" { }
            interface "int-PE-2-PE-5" { }
            interface "int-PE-2-PE-6" { }
            interface "int-PE-2-PE-7" { }
            interface "int-PE-2-PE-8" { }
        }

The router configuration on PE-3, PE-5, PE-6, PE-7 and PE-8 is similar. PE-3, PE-5, PE-6, PE-7 and PE-8 have no interface to RR-1.

RR-1 is the BGP route reflector. RR-1 is connected with PE-2 and runs IS-IS. RR-1 is configured as follows:
# On RR-1:
configure {
    router "Base" {
        interface "int-RR-1-PE-2" {
            port 1/1/c2/1
            ipv4 {
                primary {
                    address 192.168.12.1
                    prefix-length 30
                }
            }
            ipv6 {
                address 2001:db8::168:12:1 {
                    prefix-length 126
                }
            }
        }
        interface "system" {
            ipv4 {
                primary {
                    address 192.0.2.1
                    prefix-length 32
                }
            }
            ipv6 {
                address 2001:db8::2:1 {
                    prefix-length 128
                }
            }
        }
        isis 0 {
            admin-state enable
            advertise-router-capability as
            ipv6-routing native
            level-capability 2
            traffic-engineering true
            area-address [49.0001]
            traffic-engineering-options {
                ipv6 true
                application-link-attributes { }
            }
            interface "int-RR-1-PE-2" {
                interface-type point-to-point
            }
            interface "system" { }
            level 2 {
                wide-metrics-only true
            }
        }
The IBGP configuration on RR-1 is as follows:
# On RR-1:
configure {
    router "Base" {
        autonomous-system 64500
        bgp {
            rapid-withdrawal true
            peer-ip-tracking true
            rapid-update {
                vpn-ipv4 true
                mvpn-ipv4 true
                evpn true
            }
            group "IBGP" {
                type internal
                cluster {
                    cluster-id 1.1.1.1
                }
            }
            neighbor "192.0.2.2" {
                group "IBGP"
                family {
                    vpn-ipv4 true
                    mvpn-ipv4 true
                    evpn true
                }
            }
            neighbor "192.0.2.3" {
                group "IBGP"
                family {
                    vpn-ipv4 true
                    mvpn-ipv4 true
                    evpn true
                }
            }
            neighbor "192.0.2.5" {
                group "IBGP"
                family {
                    evpn true
                }
            }
            neighbor "192.0.2.6" {
                group "IBGP"
                family {
                    evpn true
                }
            }
            neighbor "192.0.2.7" {
                group "IBGP"
                family {
                    vpn-ipv4 true
                    mvpn-ipv4 true
                }
            }
            neighbor "192.0.2.8" {
                group "IBGP"
                family {
                    vpn-ipv4 true
                    mvpn-ipv4 true
                }
            }
The IBGP configuration on PE-2 is as follows:
# On PE-2:
configure {
    router "Base" {
        autonomous-system 64500
        bgp {
            rapid-withdrawal true
            peer-ip-tracking true
            rapid-update {
                vpn-ipv4 true
                mvpn-ipv4 true
                evpn true
            }
            group "IBGP" {
                type internal
            }
            neighbor "192.0.2.1" {
                group "IBGP"
                family {
                    vpn-ipv4 true
                    mvpn-ipv4 true
                    evpn true
                }
            }
        }

The IBGP configuration on PE-3, PE-5, PE-6, PE-7, and PE-8 is similar. PE-2 and PE-3 operate in both the EVPN and the MVPN/PIM networks. They support the VPN IPv4, MVPN IPv4, and EVPN address families. PE-5 and PE-6 operate in the EVPN network only. They support only the EVPN address family. PE-7 and PE-8 operate in the MVPN/PIM network only. They support only the VPN IPv4 and MVPN IPv4 address families.

Service configuration in the EVPN network

The initial routed VPLS SBD-8 is configured on all PEs in the EVPN network, as follows. To forward IPv4/IPv6 multicast traffic from the VPLS side of the routed VPLS service to the IP side, routed-vpls multicast ipv4 forward-to-ip-interface true and/or routed-vpls multicast ipv6 forward-to-ip-interface true must be configured.
# On PE-2, PE-3, PE-5, PE-6:
configure {
    service {
        vpls "SBD-8" {
            admin-state enable
            service-id 8
            customer "1"
            routed-vpls {
                multicast {
                    ipv4 {
                        forward-to-ip-interface true
                    }
                    ipv6 {
                        forward-to-ip-interface true
                    }
                }
            }
            bgp 1 { }
            igmp-snooping {
                admin-state enable
            }
            mld-snooping {
                admin-state enable
            }
            bgp-evpn {
                evi 8
                routes {
                    mac-ip {
                        advertise false
                    }
                    ip-prefix {
                        advertise true
                        domain-id "64500:8"
                    }
                    sel-mcast {
                        advertise true
                    }
                }
                mpls 1 {
                    admin-state enable
                    ingress-replication-bum-label true
                    auto-bind-tunnel {
                        resolution any
                    }
                }
            }
            provider-tunnel {
                inclusive {
                    admin-state enable
                    owner bgp-evpn-mpls
                    mldp
                }
            }

bgp-evpn routes ip-prefix domain-id 64500:8 is needed for loop prevention between EVPN and MVPN/PIM. See Domain Path Attribute for VPRN BGP Routes for the use of this command.

Additionally, PE-2 and PE-3 are configured as MEG/PEG router, as follows:
# On PE-2, PE-3:
configure {
    service {
        vpls "SBD-8" {
            routed-vpls {
                multicast {
                    evpn-gateway {
                        admin-state enable
The provider tunnel on the routed VPLS SBD-8 service on PE-2 and PE-3 is additionally configured as root-and leaf, as follows:
# On PE-2, PE-3:
configure {
    service {
        vpls "SBD-8" {
            provider-tunnel {
                inclusive {
                    admin-state enable
                    owner bgp-evpn-mpls
                    root-and-leaf true
                    mldp
The initial VPRN-1 is configured on all PEs, depending on their role in the EVPN or MVPN/PIM networks. PE-2 and PE-3 have identical VPRN-1 configuration (except for their route-distinguisher), as follows:
# On PE-2, PE-3:
configure {
    service {
        vprn "VPRN-1" {
            admin-state enable
            service-id 1
            customer "1"
            igmp {
                interface "int-SBD-8" { }    # to reach EVPN MC receiver
            }
            pim {
                apply-to all
                interface "int-SBD-8" {    # to reach EVPN MC source
                    multicast-senders always
                }
            }
            mvpn {
                c-mcast-signaling bgp
                auto-discovery {
                    type bgp
                }
                vrf-target {
                    unicast true
                }
                provider-tunnel {
                    inclusive {
                        mldp {
                            admin-state enable
                        }
                    }
                }
            }
            bgp-ipvpn {
                mpls {
                    admin-state enable
                    route-distinguisher "192.0.2.2:1"    # 192.0.2.3:1 for PE-3
                    domain-id "64500:1"
                    vrf-target {
                        community "target:64500:1"
                    }
                    auto-bind-tunnel {
                        resolution any
                    }
                }
            }
            interface "int-SBD-8" {
                vpls "SBD-8" {
                    evpn-tunnel {
                        supplementary-broadcast-domain true
                    }
                }
            }

VPRN-1 on PE-2 and on PE-3 uses SBD-8 toward the EVPN MC source on PE-5 and toward the EVPN MC receiver on PE-6.

PE-5 and PE-6 have an identical initial VPRN-1 configuration, which uses SBD-8 toward the MEG/PEG routers, as follows. Because an SBD interface does not have IP addresses, multicast-senders always must be configured to pass the RPF-check.
# On PE-5, PE-6:
configure {
    service {
        vprn "VPRN-1" {
            admin-state enable
            service-id 1
            customer "1"
            igmp { }
            pim {
                apply-to all
                interface "int-SBD-8" {
                    multicast-senders always
                }
            }
            interface "int-SBD-8" {
                vpls "SBD-8" {
                    evpn-tunnel {
                        supplementary-broadcast-domain true
                    }
                }
            }
PE-7 and PE-8 have nearly identical initial VPRN-1, with IGMP on PE-7 on the interface to the directly connected MC receiver and PIM on PE-8 on the interface to the directly connected MC source, as follows:
# On PE-7:
configure {
    service {
        vprn "VPRN-1" {
            admin-state enable
            service-id 1
            customer "1"
            igmp {
                interface "to-receiver" { }
            }
            pim {
                apply-to all
            }
            mvpn {
                c-mcast-signaling bgp
                umh-selection highest-ip    # this is the default
                auto-discovery {
                    type bgp
                }
                vrf-target {
                    unicast true
                }
                provider-tunnel {
                    inclusive {
                        mldp {
                            admin-state enable
                        }
                    }
                }
            }
            bgp-ipvpn {
                mpls {
                    admin-state enable
                    route-distinguisher "192.0.2.7:1"
                    vrf-target {
                        community "target:64500:1"
                    }
                    auto-bind-tunnel {
                        resolution any
                    }
                }
            }
            interface "to-receiver" {
                ipv4 {
                    primary {
                        address 203.0.113.1
                        prefix-length 24
                    }
                }
                sap 1/1/c4/1:8 { }
            }
# On PE-8:
configure {
    service {
        vprn "VPRN-1" {
            admin-state enable
            service-id 1
            customer "1"
            igmp { }
            pim {
                apply-to all
                interface "to-source" { }
            }
            mvpn {
                c-mcast-signaling bgp
                auto-discovery {
                    type bgp
                }
                vrf-target {
                    unicast true
                }
                provider-tunnel {
                    inclusive {
                        mldp {
                            admin-state enable
                        }
                    }
                }
            }
            bgp-ipvpn {
                mpls {
                    admin-state enable
                    route-distinguisher "192.0.2.8:1"
                    vrf-target {
                        community "target:64500:1"
                    }
                    auto-bind-tunnel {
                        resolution any
                    }
                }
            }
            interface "to-source" {
                ipv4 {
                    primary {
                        address 198.51.100.1
                        prefix-length 24
                    }
                }
                sap 1/1/c4/1:8 { }
            }

Use cases

The following use cases are described in the following sections:

MC traffic from MC source in MVPN/PIM network to MC receiver in EVPN network

MVPN/PIM MC source - EVPN MC receiver example setup illustrates MVPN/PIM to OISM EVPN interworking.
Figure 2. MVPN/PIM MC source - EVPN MC receiver example setup

The MC source is connected to PE-8 in the MVPN/PIM network. The MC receiver is connected to PE-6 in the EVPN network. The MC source (198.51.100.21) sends MC traffic to the MC receiver (10.0.4.21) that requested group membership for MC group 225.0.0.1.

The following cases are described in the following sections:
MC source configuration

The MC source is directly connected to VPRN-1 on PE-8 and needs no further configuration beyond the initial VPRN-1 configuration.

MC receiver configuration
The MC receiver is connected to routed VPLS BD-4 on PE-6, as follows:
# On PE-6:
configure {
    service {
        vpls "BD-4" {
            admin-state enable
            service-id 4
            customer "1"
            routed-vpls {
                multicast {
                    ipv4 {
                        forward-to-ip-interface true
                    }
                    ipv6 {
                        forward-to-ip-interface true
                    }
                }
            }
            bgp 1 { }
            igmp-snooping {
                admin-state enable
            }
            mld-snooping {
                admin-state enable
            }
            bgp-evpn {
                evi 4
                mpls 1 {
                    admin-state enable
                    ingress-replication-bum-label true
                    auto-bind-tunnel {
                        resolution any
                    }
                }
            }
            sap 1/1/c4/1:4 {
                igmp-snooping {
                    fast-leave true
                }
            }
            provider-tunnel {
                inclusive {
                    admin-state enable
                    owner bgp-evpn-mpls
                    mldp
                }
            }
VPRN-1 on PE-6 uses BD-4 toward the MC receiver (next to SBD-8 toward the MEG/PEG routers) and is additionally configured as follows:
# On PE-6:
configure {
    service {
        vprn "VPRN-1" {
            ---snip---
            igmp {
                interface "int-BD-4" { }
            }
            interface "int-BD-4" {
                description "to_receiver_OISM"
                ipv4 {
                    primary {
                        address 10.0.4.1
                        prefix-length 24
                    }
                }
                vpls "BD-4" { }
            }
            ---snip---
MEG/PEG DR election
PE-2 and PE-3 run the MEG/PEG DR election. The MEG/PEG DR election is based on the default algorithm used for EVPN DF election: modulo function of the EVI and the number of PEs. Result 0 corresponds with the lowest IP, result 1 corresponds with the next-lowest IP, and so on. The MEG/PEG routers build a list of up to 4 MEG/PEG DR candidates using the orig_addr field in the IMET routes for SBD-8. PE-2 is elected as MEG/PEG DR:
[/]
A:admin@PE-2# show service id "SBD-8" evpn-mcast-gateway all

===============================================================================
Service Evpn Multicast Gateway
===============================================================================
Type                         : mvpn-pim                
Admin State                  : Enabled                 
DR Activation Timer          : 3 secs                  
Mvpn Evpn Gateway DR         : Yes                     
Pim  Evpn Gateway DR         : Yes                     
===============================================================================

===============================================================================
Mvpn Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : Yes                     
DR Last Change               : 01/09/2025 13:36:37     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.2                               01/09/2025 13:36:37
192.0.2.3                               01/09/2025 13:36:51
-------------------------------------------------------------------------------
Number of Entries: 2
===============================================================================

===============================================================================
Pim Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : Yes                     
DR Last Change               : 01/09/2025 13:36:37     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.2                               01/09/2025 13:36:37
192.0.2.3                               01/09/2025 13:36:51
-------------------------------------------------------------------------------
Number of Entries: 2
===============================================================================
[/]
A:admin@PE-3# show service id "SBD-8" evpn-mcast-gateway all

===============================================================================
Service Evpn Multicast Gateway
===============================================================================
Type                         : mvpn-pim                
Admin State                  : Enabled                 
DR Activation Timer          : 3 secs                  
Mvpn Evpn Gateway DR         : No                      
Pim  Evpn Gateway DR         : No                      
===============================================================================

===============================================================================
Mvpn Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : No                      
DR Last Change               : 01/09/2025 13:36:51     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.2                               01/09/2025 13:36:51
192.0.2.3                               01/09/2025 13:36:51
-------------------------------------------------------------------------------
Number of Entries: 2
===============================================================================

===============================================================================
Pim Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : No                      
DR Last Change               : 01/09/2025 13:36:51     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.2                               01/09/2025 13:36:51
192.0.2.3                               01/09/2025 13:36:51
-------------------------------------------------------------------------------
Number of Entries: 2
===============================================================================
# On PE-3:
16 2025/01/09 13:36:37.181 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.1
"Peer 1: 192.0.2.1: UPDATE
Peer 1: 192.0.2.1 - Received BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 123
    Flag: 0x90 Type: 14 Len: 28 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 192.0.2.2
        Type: EVPN-INCL-MCAST Len: 17 RD: 192.0.2.2:8, tag: 0, 
orig_addr len: 32, orig_addr: 192.0.2.2 
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
    Flag: 0x80 Type: 9 Len: 4 Originator ID: 192.0.2.2
    Flag: 0x80 Type: 10 Len: 4 Cluster ID:
        1.1.1.1
    Flag: 0xc0 Type: 16 Len: 32 Extended Community:
        target:64500:8
        mcast-flags:SBD/MEG/PEG/OISM/NO-MLD-Proxy/NO-IGMP-Proxy
        df-election::DF-Type:Auto/DP:0/DF-Preference:0/AC:0
        bgp-tunnel-encap:MPLS
    Flag: 0xc0 Type: 22 Len: 25 PMSI:
        Tunnel-type Composite LDP P2MP IR (130)
        Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
        MPLS Label1 Ag  0
        MPLS Label2 IR 8388320
        Root-Node 192.0.2.2, LSP-ID 0x2002
        "
The MEG/PEG non-DR is configured such that it does not attract traffic, as follows:
# On PE-3:
configure {
    service {
        vpls "SBD-8" {
            routed-vpls {
                multicast {
                    evpn-gateway {
                        non-dr-attract-traffic none
The MEG/PEG non-DR does not send wild card EVPN Selective Multicast Ethernet Tag (EVPN-SMET) BGP updates. The MEG/PEG DR does send the wildcard EVPN-SMET BGP update and attracts traffic.
MC traffic verification
When the MC source on PE-8 starts sending MC traffic for MC group 225.0.0.1, PE-8 sends out an MVPN Source-Ad BGP update in the MVPN/PIM network. PE-2 and PE-3 install the corresponding source-ad route:
[/]
A:admin@PE-2# show router bgp routes mvpn-ipv4 type source-ad group-ip 225.0.0.1
===============================================================================
 BGP Router ID:192.0.2.2        AS:64500       Local AS:64500      
===============================================================================
 Legend -
 Status codes  : u - used, s - suppressed, h - history, d - decayed, * - valid
                 l - leaked, x - stale, > - best, b - backup, p - purge
 Origin codes  : i - IGP, e - EGP, ? - incomplete

===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag  RouteType                   OriginatorIP           LocalPref   MED
      RD                          SourceAS               Path-Id     IGP Cost
      Nexthop                     SourceIP                           Label
      As-Path                     GroupIP                            
-------------------------------------------------------------------------------
u*>i  Source-Ad                   -                      100         0
      192.0.2.8:1                 -                      None        -
      192.0.2.8                   198.51.100.21                       
      No As-Path                  225.0.0.1                           
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
[/]
A:admin@PE-3# show router bgp routes mvpn-ipv4 type source-ad group-ip 225.0.0.1
===============================================================================
 BGP Router ID:192.0.2.3        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag  RouteType                   OriginatorIP           LocalPref   MED
      RD                          SourceAS               Path-Id     IGP Cost
      Nexthop                     SourceIP                           Label
      As-Path                     GroupIP                            
-------------------------------------------------------------------------------
u*>i  Source-Ad                   -                      100         0
      192.0.2.8:1                 -                      None        -
      192.0.2.8                   198.51.100.21                       
      No As-Path                  225.0.0.1                           
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
When the MC receiver on PE-6 joins the MC group 225.0.0.1, PE-6 sends out an EVPN-SMET BGP update in the EVPN network. PE-2 and PE-3 install the corresponding SMET route:
# On PE-6:
2 2025/01/09 13:52:39.926 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.1
"Peer 1: 192.0.2.1: UPDATE
Peer 1: 192.0.2.1 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 76
    Flag: 0x90 Type: 14 Len: 39 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 192.0.2.6
        Type: EVPN-SMET Len: 28 RD: 192.0.2.6:8, tag: 0, 
Mcast-Src-Len: 32, Mcast-Src-Addr: 198.51.100.21, 
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 225.0.0.1, 
Orig Addr: 192.0.2.6/32, Flags(0x4): IE:0/V3:1/V2:0/V1:0 
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
    Flag: 0xc0 Type: 16 Len: 16 Extended Community:
        target:64500:8
        bgp-tunnel-encap:MPLS
"
[/]
A:admin@PE-2# show router bgp routes evpn smet
===============================================================================
 BGP Router ID:192.0.2.2        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP EVPN Smet Routes
===============================================================================
Flag  Route Dist.         Src Address
      Tag                 Grp Address
                          Orig Address
                          NextHop
-------------------------------------------------------------------------------
---snip---
u*>i  192.0.2.6:8         198.51.100.21
      0                   225.0.0.1
                          192.0.2.6
                          192.0.2.6

-------------------------------------------------------------------------------
Routes : 3
===============================================================================
[/]
A:admin@PE-3# show router bgp routes evpn smet
===============================================================================
 BGP Router ID:192.0.2.3        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP EVPN Smet Routes
===============================================================================
Flag  Route Dist.         Src Address
      Tag                 Grp Address
                          Orig Address
                          NextHop
-------------------------------------------------------------------------------
---snip---
u*>i  192.0.2.6:8         198.51.100.21
      0                   225.0.0.1
                          192.0.2.6
                          192.0.2.6

-------------------------------------------------------------------------------
Routes : 3
===============================================================================
Only the MEG/PEG DR updates its MFIB with the entry based on the received EVPN-SMET BGP update:
[/]
A:admin@PE-2# show service id "SBD-8" mfib

===============================================================================
Multicast FIB, Service 8
===============================================================================
Source Address  Group Address         Port Id                      Svc Id   Fwd
                                                                            Blk
-------------------------------------------------------------------------------
198.51.100.21   225.0.0.1             sbd-mpls:192.0.2.6:524274    Local    Fwd
-------------------------------------------------------------------------------
Number of entries: 1
===============================================================================
[/]
A:admin@PE-3# show service id "SBD-8" mfib

===============================================================================
Multicast FIB, Service 8
===============================================================================
Source Address  Group Address         Port Id                      Svc Id   Fwd
                                                                            Blk
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of entries: 0
===============================================================================
The MEG/PEG DR does not create SBD EVPN multicast destinations to peer MEG/PEG routers in the same SBD: each MEG/PEG candidate DR removes its EVPN multicast destinations to all other candidate DRs in the same SBD.
[/]
A:admin@PE-2# show service id "SBD-8" evpn-mpls

===============================================================================
BGP EVPN-MPLS Dest (Instance 1)
===============================================================================
TEP Address                     Transport:Tnl     Egr Label  Oper  Mcast  Num
                                                             State        MACs
-------------------------------------------------------------------------------
192.0.2.5                       ldp:65539         524274     Up    m      0
192.0.2.6                       ldp:65541         524274     Up    m      0
192.0.2.6                       ldp:65541         524275     Up    none   1
-------------------------------------------------------------------------------
Number of entries: 3
-------------------------------------------------------------------------------
===============================================================================
---snip---
Upon receiving the EVPN-SMET BGP update from PE-6, the MEG/PEG DR creates L3 state, generates the MVPN Source-Join BGP update, and starts attracting traffic.
# On PE-2:
4 2025/01/09 13:52:39.948 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.1
"Peer 1: 192.0.2.1: UPDATE
Peer 1: 192.0.2.1 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 76
    Flag: 0x90 Type: 14 Len: 33 Multiprotocol Reachable NLRI:
        Address Family MVPN_IPV4
        NextHop len 4 NextHop 192.0.2.2
        Type: Source-Join Len:22 RD: 192.0.2.8:1 SrcAS: 64500 
Src: 198.51.100.21 Grp: 225.0.0.1
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
    Flag: 0xc0 Type: 8 Len: 4 Community:
        no-export
    Flag: 0xc0 Type: 16 Len: 8 Extended Community:
        target:192.0.2.8:2
"
Upon receiving the MVPN Source-Join BGP update, PE-8 installs the corresponding source-join route:
[/]
A:admin@PE-8# show router bgp routes mvpn-ipv4 type source-join group-ip 225.0.0.1
===============================================================================
 BGP Router ID:192.0.2.8        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag  RouteType                   OriginatorIP           LocalPref   MED
      RD                          SourceAS               Path-Id     IGP Cost
      Nexthop                     SourceIP                           Label
      As-Path                     GroupIP                            
-------------------------------------------------------------------------------
u*>i  Source-Join                 -                      100         0
      192.0.2.8:1                 64500                  None        -
      192.0.2.2                   198.51.100.21                       
      No As-Path                  225.0.0.1                           
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
The MC source in the MVPN/PIM network is local to PE-8. It can reach the MC receiver on PE-6 in the EVPN network via a VPN tunnel toward PE-2.
[/]
A:admin@PE-8# show router "1" route-table

===============================================================================
Route Table (Service: 1)
===============================================================================
Dest Prefix[Flags]                            Type    Proto     Age        Pref
      Next Hop[Interface Name]                                    Metric   
-------------------------------------------------------------------------------
10.0.4.0/24                                   Remote  BGP VPN   00h04m12s  170
       192.0.2.2 (tunneled)                                         10
198.51.100.0/24                               Local   Local     00h16m59s  0
       to-source                                                    0
203.0.113.0/24                                Remote  BGP VPN   00h16m54s  170
       192.0.2.7 (tunneled)                                         20
-------------------------------------------------------------------------------
No. of Routes: 3
---snip---
===============================================================================
The MC receiver in the EVPN network is local to PE-6, where it is connected via int-BD-4. It can reach the MC source on PE-8 in the MVPN/PIM network via an EVPN interface toward PE-2, where it is connected via int-SBD-8.
[/]
A:admin@PE-6# show router "1" route-table

===============================================================================
Route Table (Service: 1)
===============================================================================
Dest Prefix[Flags]                            Type    Proto     Age        Pref
      Next Hop[Interface Name]                                    Metric   
-------------------------------------------------------------------------------
10.0.4.0/24                                   Local   Local     00h04m09s  0
       int-BD-4                                                     0
198.51.100.0/24                               Remote  EVPN-IFF  00h15m34s  169
       int-SBD-8 (ET-00:02:fe:ff:ff:45)                             0
203.0.113.0/24                                Remote  EVPN-IFF  00h15m34s  169
       int-SBD-8 (ET-00:02:fe:ff:ff:45)                             0
-------------------------------------------------------------------------------
No. of Routes: 3
---snip---
===============================================================================
MC traffic from the MC source on PE-8 reaches the MEG/PEG DR and is forwarded from there to the MC receiver on PE-6. In the MEG/PEG DR, int-SBD-8 is in the Outgoing Intf List. In the MEG/PEG non-DR, the SBD interface is not in the Outgoing Intf List:
[/]
A:admin@PE-2# show router "1" pim group 225.0.0.1 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 225.0.0.1
Source Address     : 198.51.100.21
RP Address         : 0
Advt Router        : 192.0.2.8
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 192.0.2.8
MRIB Src Flags     : remote             
Keepalive Timer Exp: 0d 00:03:15        
Up Time            : 0d 00:00:15        Resolved By        : rtable-u
 
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:45
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 192.0.2.8
Incoming Intf      : mpls-if-73731
Outgoing Intf List : int-SBD-8
 
Curr Fwding Rate   : 477.264 kbps       
Forwarded Packets  : 925                Discarded Packets  : 0
Forwarded Octets   : 904650             RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
[/]
A:admin@PE-3# show router "1" pim group 225.0.0.1 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 225.0.0.1
Source Address     : 198.51.100.21
RP Address         : 0
Advt Router        : 192.0.2.8
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 192.0.2.8
MRIB Src Flags     : remote             
Keepalive Timer Exp: 0d 00:03:12        
Up Time            : 0d 00:00:17        Resolved By        : rtable-u
 
Up JP State        : Not Joined         Up JP Expiry       : 0d 00:00:00
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 192.0.2.8
Incoming Intf      : mpls-if-73731
Outgoing Intf List : 
 
Curr Fwding Rate   : 0.000 kbps         
Forwarded Packets  : 0                  Discarded Packets  : 0
Forwarded Octets   : 0                  RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
The MEG/PEG DR forwards the MC traffic to the MC receiver on PE-6 in the EVPN network. int-SBD-8 is the Incoming Intf, while the local int-BD-4 is in the Outgoing Intf List:
[/]
A:admin@PE-6# show router "1" pim group detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 225.0.0.1
Source Address     : 198.51.100.21
RP Address         : 0
Advt Router        : 
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 198.51.100.21
MRIB Src Flags     : direct             
Keepalive Timer    : Not Running        
Up Time            : 0d 00:01:15        Resolved By        : rtable-u
 
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:00
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 198.51.100.21
Incoming Intf      : int-SBD-8
Outgoing Intf List : int-BD-4
 
Curr Fwding Rate   : 477.264 kbps       
Forwarded Packets  : 4558               Discarded Packets  : 0
Forwarded Octets   : 4457724            RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
PE-6 creates the MFIB at BD-4 with sbd-mpls:192.0.2.2:524270 toward the MEG/PEG DR for wildcard joins and (S,G) joins on the MEG/PEG DR:
[/]
A:admin@PE-6# show service id "BD-4" mfib

===============================================================================
Multicast FIB, Service 4
===============================================================================
Source Address  Group Address         Port Id                      Svc Id   Fwd
                                                                            Blk
-------------------------------------------------------------------------------
*               *                     sbd-mpls:192.0.2.2:524270    Local    Fwd
198.51.100.21   225.0.0.1             sap:1/1/c4/1:4               Local    Fwd
                                      sbd-mpls:192.0.2.2:524270    Local    Fwd
*               * (mac)               sbd-mpls:192.0.2.2:524270    Local    Fwd
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================
PE-8 receives MC traffic from the locally connected MC source and forwards it in the MVPN/PIM network. PE-3 (MEG/PEG non-DR) and PE-7 do not forward the MC traffic. PE-2 forwards the MC traffic into the EVPN network. PE-5 has no MC receivers and does not forward the MC traffic. PE-6 forwards the MC traffic to the MC receiver that requested the group membership:
[/]
A:admin@PE-8# monitor port all-ethernet-rates interval 3 repeat 5

=====================================================================
Monitor statistics for all Ethernet Port Rates
=====================================================================
Port-Id          D                 Bits   Packets     Errors    Util
---------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
At time t = 15 sec (Mode: Rate)
-------------------------------------------------------------------------------
1/1/c1/1         I                    0         0          0    0.00
                 O                    0         0          0    0.00

1/1/c2/1         I                 1016         1          0    0.00
                 O               492088        63          0    0.00

1/1/c3/1         I                 1016         1          0    0.00
                 O               491640        63          0    0.00

1/1/c4/1         I               490664        61          0    0.00
                 O                    0         0          0    0.00

1/1/c7/1         I                    0         0          0    0.00
                 O                    0         0          0    0.00

=====================================================================
[/]
A:admin@PE-3# monitor port all-ethernet-rates interval 3 repeat 5

=====================================================================
Monitor statistics for all Ethernet Port Rates
=====================================================================
Port-Id          D                 Bits   Packets     Errors    Util
---------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
At time t = 15 sec (Mode: Rate)
-------------------------------------------------------------------------------
1/1/c1/1         I                    0         0          0    0.00
                 O                  216         0          0    0.00

1/1/c2/1         I                 1392         2          0    0.00
                 O                 1376         2          0    0.00

1/1/c5/1         I                 2312         2          0    0.00
                 O                 2640         2          0    0.00

1/1/c6/1         I                 2744         3          0    0.00
                 O                 2872         3          0    0.00

1/1/c7/1         I                 2096         2          0    0.00
                 O                 2376         3          0    0.00

1/1/c8/1         I               492192        63          0    0.00
                 O                 1720         1          0    0.00

=====================================================================
[/]
A:admin@PE-2# monitor port all-ethernet-rates interval 3 repeat 5

=====================================================================
Monitor statistics for all Ethernet Port Rates
=====================================================================
Port-Id          D                 Bits   Packets     Errors    Util
---------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
At time t = 15 sec (Mode: Rate)
-------------------------------------------------------------------------------
1/1/c1/1         I                 1096         1          0    0.00
                 O                 1288         2          0    0.00

1/1/c3/1         I                 1792         2          0    0.00
                 O                 2256         2          0    0.00

1/1/c5/1         I                 1384         2          0    0.00
                 O               500480        64          0    0.00

1/1/c6/1         I                 1200         1          0    0.00
                 O               500032        63          0    0.00

1/1/c7/1         I                 1768         2          0    0.00
                 O               493344        64          0    0.00

1/1/c8/1         I               492456        63          0    0.00
                 O                 2704         3          0    0.00

=====================================================================
[/]
A:admin@PE-5# monitor port all-ethernet-rates interval 3 repeat 5

=====================================================================
Monitor statistics for all Ethernet Port Rates
=====================================================================
Port-Id          D                 Bits   Packets     Errors    Util
---------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
At time t = 15 sec (Mode: Rate)
-------------------------------------------------------------------------------
1/1/c1/1         I                    0         0          0    0.00
                 O                  216         0          0    0.00

1/1/c2/1         I               498984        63          0    0.00
                 O                 2144         2          0    0.00

1/1/c3/1         I                 1888         2          0    0.00
                 O                 1384         1          0    0.00

1/1/c4/1         I                    0         0          0    0.00
                 O                    0         0          0    0.00

1/1/c6/1         I                 1648         2          0    0.00
                 O                 1144         1          0    0.00

=====================================================================
[/]
A:admin@PE-6# monitor port all-ethernet-rates interval 3 repeat 5

=====================================================================
Monitor statistics for all Ethernet Port Rates
=====================================================================
Port-Id          D                 Bits   Packets     Errors    Util
---------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
At time t = 15 sec (Mode: Rate)
-------------------------------------------------------------------------------
1/1/c1/1         I                    0         0          0    0.00
                 O                  216         0          0    0.00

1/1/c2/1         I               498768        62          0    0.00
                 O                  864         1          0    0.00

1/1/c3/1         I                 1440         1          0    0.00
                 O                  992         1          0    0.00

1/1/c4/1         I                    0         0          0    0.00
                 O               490664        61          0    0.00

1/1/c5/1         I                 1024         1          0    0.00
                 O                 1648         2          0    0.00

=====================================================================

MC traffic from MC source in EVPN network to MC receiver in MVPN/PIM network

EVPN MC source - MVPN/PIM MC receiver example setup, with non-DR as UMH for PE-7 illustrates OISM EVPN to MVPN/PIM interworking.
Figure 3. EVPN MC source - MVPN/PIM MC receiver example setup, with non-DR as UMH for PE-7

The MC source is connected to PE-5 in the EVPN network. The MC receiver is connected to PE-7 in the MVPN/PIM network. The MC source (10.0.3.21) sends MC traffic to the MC receiver (203.0.113.21) that requested the group membership for MC group 239.0.0.4.

The following cases are described in the following sections:
MC source configuration
The MC source is connected to routed VPLS BD-3 on PE-5, as follows:
# On PE-5:
configure {
    service {
        vpls "BD-3" {
            admin-state enable
            service-id 3
            customer "1"
            routed-vpls {
                multicast {
                    ipv4 {
                        forward-to-ip-interface true
                    }
                    ipv6 {
                        forward-to-ip-interface true
                    }
                }
            }
            bgp 1 { }
            igmp-snooping {
                admin-state enable
            }
            mld-snooping {
                admin-state enable
            }
            bgp-evpn {
                evi 3
                mpls 1 {
                    admin-state enable
                    ingress-replication-bum-label true
                    auto-bind-tunnel {
                        resolution any
                    }
                }
            }
            sap 1/1/c4/1:3 { }
            provider-tunnel {
                inclusive {
                    admin-state enable
                    owner bgp-evpn-mpls
                    root-and-leaf true
                    mldp
                }
            }
VPRN-1 on PE-5 uses BD-3 toward the MC source (next to SBD-8 toward the MEG/PEG routers) and is additionally configured as follows:
# On PE-5:
configure {
    service {
        vprn "VPRN-1" {
            ---snip---
            igmp {
                interface "int-SBD-8" { }
            }
            interface "int-BD-3" {
                description "to_source_OISM"
                ipv4 {
                    primary {
                        address 10.0.3.1
                        prefix-length 24
                    }
                }
                vpls "BD-3" { }
            }
            ---snip---
MC receiver configuration

The MC receiver is directly connected to VPRN-1 on PE-7 and needs no further configuration beyond the initial VPRN-1 configuration.

MEG/PEG DR election
MEG/PEG DR election does not change, so PE-3 is MEG/PEG non-DR. The MEG/PEG non-DR is configured with routed-vpls multicast evpn-gateway non-dr-attract-traffic none, so it does not send wildcard EVPN-SMET BGP update and does not attract traffic. The MEG/PEG DR still sends the wildcard EVPN-SMET BGP update and attracts traffic.
# On PE-2:
27 2025/01/09 13:36:39.745 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.1
"Peer 1: 192.0.2.1: UPDATE
Peer 1: 192.0.2.1 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 68
    Flag: 0x90 Type: 14 Len: 31 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 192.0.2.2
        Type: EVPN-SMET Len: 20 RD: 192.0.2.2:8, tag: 0, 
Mcast-Src-Len: 0, Mcast-Src-Addr: 0.0.0.0, 
Mcast-Grp-Len: 0, Mcast-Grp-Addr: 0.0.0.0, 
Orig Addr: 192.0.2.2/32, Flags(0x0): IE:0/V3:0/V2:0/V1:0 
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
    Flag: 0xc0 Type: 16 Len: 16 Extended Community:
        target:64500:8
        bgp-tunnel-encap:MPLS
"
MEG/PEG non-DR as upstream multicast hop (UMH)
Ensure that the connection from PE-7 to PE-2 has a lower IGP cost than the connection from PE-7 to PE-3, as follows:
# On PE-7:
configure {
    router "Base" {
        isis 0 {
            interface "int-PE-7-PE-2" {
                interface-type point-to-point
                level 1 {
                    metric 5    # for proof of umh-selection
                }
                level 2 {
                    metric 5    # for proof of umh-selection
                }

PE-7 receives two VPN IPv4 routes for the MC source address in the 10.0.3.0/24 address range, one from PE-2 with configured IGP cost 5 and one from PE-3 with default IGP cost 10.

[/]
A:admin@PE-7# show router bgp routes vpn-ipv4
===============================================================================
 BGP Router ID:192.0.2.7        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP VPN-IPv4 Routes
===============================================================================
Flag  Network                                            LocalPref   MED
      Nexthop (Router)                                   Path-Id     IGP Cost
      As-Path                                                        Label
-------------------------------------------------------------------------------
u*>i  192.0.2.2:1:10.0.3.0/24                            100         None
      192.0.2.2                                          None        5
      No As-Path                                                     524274
u*>i  192.0.2.3:1:10.0.3.0/24                            100         None
      192.0.2.3                                          None        10
      No As-Path                                                     524274
---snip---
-------------------------------------------------------------------------------
Routes : 4
===============================================================================

Configure PE-7 with the default mvpn umh-selection highest-ip configuration, so that, to select the upstream multicast hop, PE-7 uses the highest next hop IP address and not the lowest IGP cost.

MC traffic verification

Because PE-5 is configured with root-and-leaf for BD-3, PE-5 originates a P2MP tunnel in the EVPN network from BD-3 with LSP-ID 8193, when BD-3 is enabled. SR OS dynamically assigns the LSP-ID. When the same LSP-ID is reused on different PEs, they represent different P2MP tunnels.

[/]
A:admin@PE-5# tools dump service id "BD-3" provider-tunnels    # only on PE-5

========================================================================================
VPLS 3 Inclusive Provider Tunnels Originating             
========================================================================================
ipmsi (LDP)                                     Root-Addr       LSP-ID       Oper-State
----------------------------------------------------------------------------------------
8193                                            192.0.2.5       8193         Up

----------------------------------------------------------------------------------------

========================================================================================
VPLS 3 Inclusive Provider Tunnels Terminating             
========================================================================================
ipmsi (LDP)                                     Root-Addr       LSP-ID       Oper-State
----------------------------------------------------------------------------------------

No Tunnels Found  
----------------------------------------------------------------------------------------

---snip---
and PE-5 sends an EVPN-INCL-MCAST BGP Update message. Because the MC source and the MC receiver do not belong to the same IP address space, this BGP update message contains 2 target fields: target:64500:3 for BD-3 and target:64500:8 for SBD-8.
# On PE-5:
5 2025/01/23 15:05:14.906 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.1
"Peer 1: 192.0.2.1: UPDATE
Peer 1: 192.0.2.1 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 109
    Flag: 0x90 Type: 14 Len: 28 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 192.0.2.5
        Type: EVPN-INCL-MCAST Len: 17 RD: 192.0.2.5:3, tag: 0, 
orig_addr len: 32, orig_addr: 192.0.2.5 
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
    Flag: 0xc0 Type: 16 Len: 32 Extended Community:
        target:64500:3
        mcast-flags:NO-SBD/NO-MEG/NO-PEG/OISM/NO-MLD-Proxy/NO-IGMP-Proxy
        target:64500:8
        bgp-tunnel-encap:MPLS
    Flag: 0xc0 Type: 22 Len: 25 PMSI:
        Tunnel-type Composite LDP P2MP IR (130)
        Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
        MPLS Label1 Ag  0
        MPLS Label2 IR 8388544
        Root-Node 192.0.2.5, LSP-ID 0x2001
"
The MEG/PEG DR (PE-2) and the MEG/PEG non-DR (PE-3) receive the EVPN-INCL-MCAST BGP Update message and terminate a P2MP tunnel in the EVPN network from SBD-8 on PE-5, with LSP-ID 8193:
[/]
A:admin@PE-2# tools dump service id "SBD-8" provider-tunnels

========================================================================================
VPLS 8 Inclusive Provider Tunnels Originating             
========================================================================================
ipmsi (LDP)                                     Root-Addr       LSP-ID       Oper-State
----------------------------------------------------------------------------------------
8193                                            192.0.2.2       8193         Up

----------------------------------------------------------------------------------------

========================================================================================
VPLS 8 Inclusive Provider Tunnels Terminating             
========================================================================================
ipmsi (LDP)                                     Root-Addr       LSP-ID       Oper-State
----------------------------------------------------------------------------------------
                                                192.0.2.5       8193         Up

----------------------------------------------------------------------------------------
---snip---

The tunnel that originates on PE-2 (Root-Addr 192.0.2.2) is another P2MP tunnel that is present for the earlier scenario, where a MC receiver is connected to PE-6 in the EVPN network. That tunnel is not relevant for this scenario. Similar on PE-3.

The MEG/PEG DR and the MEG/PEG non-DR belong to the MC list of BD-3 and SBD-8 on PE-5:
[/]
A:admin@PE-5# tools dump service id "BD-3" evpn-mpls default-multicast-list
-------------------------------------------------------------------------
TEP Address                              Egr Label            
                                         Transport            
-------------------------------------------------------------------------
192.0.2.2                                524284               
                                         ldp                  
192.0.2.3                                524284               
                                         ldp                  
---snip---
-------------------------------------------------------------------------
[/]
A:admin@PE-5# tools dump service id "SBD-8" evpn-mpls default-multicast-list
-------------------------------------------------------------------------
TEP Address                              Egr Label            
                                         Transport            
-------------------------------------------------------------------------
192.0.2.2                                524284               
                                         ldp                  
192.0.2.3                                524284               
                                         ldp                  
---snip---
-------------------------------------------------------------------------
PE-5 pushes MC traffic from its connected MC source to PE-3 in the EVPN network:
[/]
A:admin@PE-5# show router ldp bindings p2mp p2mp-id 8193

===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.5)
             (IPv6 LSR ID 2001:db8::2:5)
===============================================================================
Label Status:
        U - Label In Use, N - Label Not In Use, W - Label Withdrawn
        WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
        e - Label ELC
FEC Flags:
        LF - Lower FEC, UF - Upper FEC, M - Community Mismatch,
        BA - ASBR Backup FEC
===============================================================================
LDP Generic IPv4 P2MP Bindings
===============================================================================
P2MP-Id                                      
RootAddr                                    Interface
Peer                                         
IngLbl                                      EgrLbl
EgrNH                                       EgrIf/LspId
-------------------------------------------------------------------------------
---snip---
8193
192.0.2.5                                   73728
192.0.2.3:0
  --                                        524270
192.168.35.1                                1/1/c3/1
                                             
---snip---
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Bindings: 5
===============================================================================
---snip---
Similar to PE-2.
[/]
A:admin@PE-5# show router ldp bindings active p2mp p2mp-id 8193

===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.5)
             (IPv6 LSR ID 2001:db8::2:5)
===============================================================================
Label Status:
        U - Label In Use, N - Label Not In Use, W - Label Withdrawn
        WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
        e - Label ELC
FEC Flags:
        LF - Lower FEC, UF - Upper FEC, M - Community Mismatch,
        BA - ASBR Backup FEC
===============================================================================
LDP Generic IPv4 P2MP Bindings (Active)
===============================================================================
P2MP-Id                                     Interface
RootAddr                                    Op
IngLbl                                      EgrLbl
EgrNH                                       EgrIf/LspId
-------------------------------------------------------------------------------
---snip---
8193                                        73728
192.0.2.5                                   Push
  --                                        524270
192.168.35.1                                1/1/c3/1
                                             
---snip---
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 5
===============================================================================
---snip---

Similar to PE-2.

PE-3 pops MC traffic from PE-5 in the EVPN network and pushes it to PE-7 in the MVPN/PIM network:

A:PE-3# show router ldp bindings active p2mp p2mp-id 8193 

===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.3)
             (IPv6 LSR ID 2001:db8::2:3)
===============================================================================
---snip---
===============================================================================
LDP Generic IPv4 P2MP Bindings (Active)
===============================================================================
P2MP-Id                                     Interface
RootAddr                                    Op
IngLbl                                      EgrLbl
EgrNH                                       EgrIf/LspId
-------------------------------------------------------------------------------
---snip---
8193                                        73728
192.0.2.3                                   Push
  --                                        524272
192.168.37.2                                1/1/c7/1
                                             
---snip---
8193                                        73734
192.0.2.5                                   Pop
524269                                        --
  --                                          --
                                             
---snip---
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 7
===============================================================================
---snip---

Similar for PE-2.

PE-7 pops MC traffic from PE-3 in the MVPN/PIM network:

A:PE-7# show router ldp bindings active p2mp p2mp-id 8193 

===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.7)
             (IPv6 LSR ID 2001:db8::2:7)
===============================================================================
---snip---
===============================================================================
LDP Generic IPv4 P2MP Bindings (Active)
===============================================================================
P2MP-Id                                     Interface
RootAddr                                    Op
IngLbl                                      EgrLbl
EgrNH                                       EgrIf/LspId
-------------------------------------------------------------------------------
---snip---
8193                                        73731
192.0.2.3                                   Pop
524272                                        --
  --                                          --
                                             
---snip---
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 6
===============================================================================
---snip---

Similar from PE-2.

When the MC source on PE-5 starts sending MC traffic for MC group 239.0.0.4, PE-5 creates the MFIB at BD-3 with sbd-mpls:192.0.2.2:524270 toward the MEG/PEG DR for wildcard joins and (S,G) joins on the MEG/PEG DR.

When the MC receiver on PE-7 joins the MC group 239.0.0.4, PE-7 selects the MEG/PEG non-DR as upstream multicast hop (UMH) for its (S,G) join, based on the mvpn umh-selection highest-ip default configuration.
[/]
A:admin@PE-3# show router bgp routes mvpn-ipv4 type source-join group-ip 239.0.0.4
===============================================================================
 BGP Router ID:192.0.2.3        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag  RouteType                   OriginatorIP           LocalPref   MED
      RD                          SourceAS               Path-Id     IGP Cost
      Nexthop                     SourceIP                           Label
      As-Path                     GroupIP                            
-------------------------------------------------------------------------------
u*>i  Source-Join                 -                      100         0
      192.0.2.3:1                 64500                  None        -
      192.0.2.7                   10.0.3.21                           
      No As-Path                  239.0.0.4                           
-------------------------------------------------------------------------------
Routes : 1
===============================================================================
So the MEG/PEG non-DR does send the corresponding (S,G) EVPN-SMET BGP update. PE-5 adds sbd-mpls:192.0.2.3:524270 toward the MEG/PEG non-DR to the MFIB at BD-3, only for (S,G) joins on the MEG/PEG non-DR.
[/]
A:admin@PE-5# show service id "BD-3" mfib

===============================================================================
Multicast FIB, Service 3
===============================================================================
Source Address  Group Address         Port Id                      Svc Id   Fwd
                                                                            Blk
-------------------------------------------------------------------------------
*               *                     sap:1/1/c4/1:3               Local    Fwd
                                      sbd-mpls:192.0.2.2:524270    Local    Fwd
10.0.3.21       239.0.0.4             sap:1/1/c4/1:3               Local    Fwd
                                      sbd-mpls:192.0.2.2:524270    Local    Fwd
                                      sbd-mpls:192.0.2.3:524270    Local    Fwd
*               * (mac)               sbd-mpls:192.0.2.2:524270    Local    Fwd
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================
The MC source in the EVPN network is local to PE-5, where it is connected via int-BD-3. It can reach the MC receiver on PE-7 in the MVPN/PIM network via an EVPN interface toward PE-2, where it is connected via int-SBD-8.
[/]
A:admin@PE-5# show router "1" route-table

===============================================================================
Route Table (Service: 1)
===============================================================================
Dest Prefix[Flags]                            Type    Proto     Age        Pref
      Next Hop[Interface Name]                                    Metric   
-------------------------------------------------------------------------------
10.0.3.0/24                                   Local   Local     00h01m57s  0
       int-BD-3                                                     0
198.51.100.0/24                               Remote  EVPN-IFF  00h21m13s  169
       int-SBD-8 (ET-00:02:fe:ff:ff:45)                             0
203.0.113.0/24                                Remote  EVPN-IFF  00h21m13s  169
       int-SBD-8 (ET-00:02:fe:ff:ff:45)                             0
-------------------------------------------------------------------------------
No. of Routes: 3
---snip---
===============================================================================
The MC receiver in the MVPN/PIM network is local to PE-7. It can reach the MC source on PE-5 in the EVPN network via a VPN tunnel toward PE-2.
[/]
A:admin@PE-7# show router "1" route-table

===============================================================================
Route Table (Service: 1)
===============================================================================
Dest Prefix[Flags]                            Type    Proto     Age        Pref
      Next Hop[Interface Name]                                    Metric   
-------------------------------------------------------------------------------
10.0.3.0/24                                   Remote  BGP VPN   00h02m00s  170
       192.0.2.2 (tunneled)                                         5
198.51.100.0/24                               Remote  BGP VPN   00h22m16s  170
       192.0.2.8 (tunneled)                                         15
203.0.113.0/24                                Local   Local     00h22m27s  0
       to-receiver                                                  0
-------------------------------------------------------------------------------
No. of Routes: 3
---snip---
===============================================================================
PE-5 sends MC traffic from the MC source with source address 10.0.3.21 for MC group 239.0.0.4 to PE-3 and all other MC traffic to PE-2, because the MEG/PEG DR sends the wildcard SMET route.
[/]
A:admin@PE-5# show router bgp routes evpn smet
===============================================================================
 BGP Router ID:192.0.2.5        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP EVPN Smet Routes
===============================================================================
Flag  Route Dist.         Src Address
      Tag                 Grp Address
                          Orig Address
                          NextHop
-------------------------------------------------------------------------------
u*>i  192.0.2.2:8         0.0.0.0
      0                   0.0.0.0
                          192.0.2.2
                          192.0.2.2

u*>i  192.0.2.3:8         10.0.3.21
      0                   239.0.0.4
                          192.0.2.3
                          192.0.2.3

-------------------------------------------------------------------------------
Routes : 2
===============================================================================
MC traffic from the MC source on PE-5 reaches the MEG/PEG non-DR and is forwarded from there to the MC receiver on PE-7. In the MEG/PEG DR, the MVPN tunnel interface is not in the Outgoing Intf List. In the MEG/PEG non-DR, the MVPN tunnel interface is in the Outgoing Intf List:
[/]
A:admin@PE-2# show router "1" pim group 239.0.0.4 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.0.0.4
Source Address     : 10.0.3.21
RP Address         : 0
Advt Router        : 
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 10.0.3.21
MRIB Src Flags     : direct             
Keepalive Timer Exp: 0d 00:03:07        
Up Time            : 0d 00:00:33        Resolved By        : rtable-u
 
Up JP State        : Not Joined         Up JP Expiry       : 0d 00:00:00
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : Join               Register Stop Exp  : 0d 00:00:00
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 10.0.3.21
Incoming Intf      : int-SBD-8
Outgoing Intf List : 
 
Curr Fwding Rate   : 719.808 kbps       
Forwarded Packets  : 3003               Discarded Packets  : 0
Forwarded Octets   : 2936934            RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
[/]
A:admin@PE-3# show router "1" pim group 239.0.0.4 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.0.0.4
Source Address     : 10.0.3.21
RP Address         : 0
Advt Router        : 
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 10.0.3.21
MRIB Src Flags     : direct             
Keepalive Timer Exp: 0d 00:02:55        
Up Time            : 0d 00:00:34        Resolved By        : rtable-u
 
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:00
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 10.0.3.21
Incoming Intf      : int-SBD-8
Outgoing Intf List : mpls-if-73728
 
Curr Fwding Rate   : 715.896 kbps       
Forwarded Packets  : 3131               Discarded Packets  : 0
Forwarded Octets   : 3062118            RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
[/]
A:admin@PE-3# show router "1" pim tunnel-interface

===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface                        Originator Address   Adm  Opr  Transport Type
-------------------------------------------------------------------------------
mpls-if-73728                    192.0.2.3            Up   Up   Tx-IPMSI
mpls-if-73729                    192.0.2.2            Up   Up   Rx-IPMSI
mpls-if-73730                    192.0.2.7            Up   Up   Rx-IPMSI
mpls-if-73731                    192.0.2.8            Up   Up   Rx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
The MEG/PEG non-DR forwards the MC traffic to the MC receiver PE-7 in the MVPN/PIM network. The MVPN tunnel interface is the Incoming Intf, while the local SAP is in the Outgoing Intf List:
[/]
A:admin@PE-7# show router "1" pim group 239.0.0.4 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.0.0.4
Source Address     : 10.0.3.21
RP Address         : 0
Advt Router        : 192.0.2.3
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 192.0.2.3
MRIB Src Flags     : remote             
Keepalive Timer Exp: 0d 00:03:02        
Up Time            : 0d 00:00:28        Resolved By        : rtable-u
 
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:31
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 192.0.2.3
Incoming Intf      : mpls-if-73730
Outgoing Intf List : to-receiver
 
Curr Fwding Rate   : 715.896 kbps       
Forwarded Packets  : 2532               Discarded Packets  : 0
Forwarded Octets   : 2476296            RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
[/]
A:admin@PE-7# show router "1" pim tunnel-interface

===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface                        Originator Address   Adm  Opr  Transport Type
-------------------------------------------------------------------------------
mpls-if-73728                    192.0.2.7            Up   Up   Tx-IPMSI
mpls-if-73729                    192.0.2.2            Up   Up   Rx-IPMSI
mpls-if-73730                    192.0.2.3            Up   Up   Rx-IPMSI
mpls-if-73731                    192.0.2.8            Up   Up   Rx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
Egress statistics for the MLDP are increased in the Root (OISM) VPLS.
[/]
A:admin@PE-5# show service id "BD-3" sdp

===============================================================================
Services: Service Destination Points
===============================================================================
SdpId            Type     Far End addr    Adm     Opr       I.Lbl     E.Lbl
-------------------------------------------------------------------------------
32767:4294967294 VplsPmsi not applicable  Up      Up        None      3
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
===============================================================================
[/]
A:admin@PE-5# show service id "BD-3" sdp detail | match "Statis" post-lines 4
Statistics            :
I. Fwd. Pkts.      : 0                        I. Dro. Pkts.     : 0
I. Fwd. Octs.      : 0                        I. Dro. Octs.     : 0
E. Fwd. Pkts.      : 10624                    E. Fwd. Octets    : 10507552
-------------------------------------------------------------------------------

PE-5 receives MC traffic from the locally connected MC source and forwards it to PE-2 and PE-3. PE-2 (MEG/PEG DR) forwards the MC traffic only to PE-3 (MEG/PEG non-DR). PE-3 forwards the MC traffic to PE-2, PE-7 and PE-8. PE-8 has no MC receivers. PE-7 forwards the MC traffic to the MC receiver that requested the group membership.

MEG/PEG DR as upstream multicast hop (UMH)
The upstream multicast hop selection for PE-7 is changed to prefer PE-2, as follows:
# On PE-7:
configure {
    service {
        vprn "VPRN-1" {
            mvpn {
                umh-selection unicast-rt-pref

The P2MP tunnels in the EVPN network remain the same. IngLbl, EgrLbl, and ldp binding Interface in the MVPN/PIM network change.

Figure 4. EVPN MC source - MVPN/PIM MC receiver example setup, with DR as UMH for PE-7

When the MC receiver on PE-7 joins the MC group 239.0.0.4, PE-7 now selects the MEG/PEG DR PE-2 as upstream multicast hop (UMH) for its (S,G) join, because the PE-7 to PE-2 connection has lower IGP cost than the PE-7 to PE-3 connection.

The MEG/PEG DR sends the corresponding (S,G) EVPN-SMET BGP update. PE-5 only keeps sbd-mpls:192.0.2.2:524270 toward the MEG/PEG DR in the MFIB at BD-3, only for wildcard joins on the MEG/PEG DR.
[/]
A:admin@PE-5# show service id "BD-3" mfib

===============================================================================
Multicast FIB, Service 3
===============================================================================
Source Address  Group Address         Port Id                      Svc Id   Fwd
                                                                            Blk
-------------------------------------------------------------------------------
*               *                     sap:1/1/c4/1:3               Local    Fwd
                                      sbd-mpls:192.0.2.2:524270    Local    Fwd
*               * (mac)               sbd-mpls:192.0.2.2:524270    Local    Fwd
-------------------------------------------------------------------------------
Number of entries: 2
===============================================================================
PE-5 sends all MC traffic from the MC source to PE-2.
[/]
A:admin@PE-5# show router bgp routes evpn smet
===============================================================================
 BGP Router ID:192.0.2.5        AS:64500       Local AS:64500      
===============================================================================
---snip---
===============================================================================
BGP EVPN Smet Routes
===============================================================================
Flag  Route Dist.         Src Address
      Tag                 Grp Address
                          Orig Address
                          NextHop
-------------------------------------------------------------------------------
u*>i  192.0.2.2:8         0.0.0.0
      0                   0.0.0.0
                          192.0.2.2
                          192.0.2.2

u*>i  192.0.2.2:8         10.0.3.21
      0                   239.0.0.4
                          192.0.2.2
                          192.0.2.2

-------------------------------------------------------------------------------
Routes : 2
===============================================================================
MC traffic from the MC source on PE-5 reaches the MEG/PEG DR and is forwarded from there to the MC receiver on PE-7. In the MEG/PEG DR, the MVPN tunnel interface is in the Outgoing Intf List. In the MEG/PEG non-DR, the MVPN tunnel interface is not in the Outgoing Intf List:
[/]
A:admin@PE-2# show router "1" pim group 239.0.0.4 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.0.0.4
Source Address     : 10.0.3.21
RP Address         : 0
Advt Router        : 
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 10.0.3.21
MRIB Src Flags     : direct             
Keepalive Timer Exp: 0d 00:03:28        
Up Time            : 0d 00:03:42        Resolved By        : rtable-u
 
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:00
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : Join               Register Stop Exp  : 0d 00:00:00
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 10.0.3.21
Incoming Intf      : int-SBD-8
Outgoing Intf List : mpls-if-73728
 
Curr Fwding Rate   : 719.808 kbps       
Forwarded Packets  : 20466              Discarded Packets  : 0
Forwarded Octets   : 20015748           RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
[/]
A:admin@PE-2# show router "1" pim tunnel-interface

===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface                        Originator Address   Adm  Opr  Transport Type
-------------------------------------------------------------------------------
mpls-if-73728                    192.0.2.2            Up   Up   Tx-IPMSI
mpls-if-73729                    192.0.2.3            Up   Up   Rx-IPMSI
mpls-if-73731                    192.0.2.8            Up   Up   Rx-IPMSI
mpls-if-73735                    192.0.2.7            Up   Up   Rx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
[/]
A:admin@PE-3# show router "1" pim group 239.0.0.4 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.0.0.4
Source Address     : 10.0.3.21
RP Address         : 0
Advt Router        : 
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 10.0.3.21
MRIB Src Flags     : direct             
Keepalive Timer Exp: 0d 00:02:40        
Up Time            : 0d 00:03:44        Resolved By        : rtable-u
 
Up JP State        : Not Joined         Up JP Expiry       : 0d 00:00:00
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 10.0.3.21
Incoming Intf      : int-SBD-8
Outgoing Intf List : 
 
Curr Fwding Rate   : 719.808 kbps       
Forwarded Packets  : 20595              Discarded Packets  : 0
Forwarded Octets   : 20141910           RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
The MEG/PEG DR forwards the MC traffic to the MC receiver PE-7 in the MVPN/PIM network. The MVPN tunnel interface is the Incoming Intf, while the local SAP is in the Outgoing Intf List:
[/]
A:admin@PE-7# show router "1" pim group 239.0.0.4 detail

===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address      : 239.0.0.4
Source Address     : 10.0.3.21
RP Address         : 0
Advt Router        : 192.0.2.2
Flags              :                    Type               : (S,G)
Mode               : sparse             
MRIB Next Hop      : 192.0.2.2
MRIB Src Flags     : remote             
Keepalive Timer Exp: 0d 00:02:36        
Up Time            : 0d 00:00:54        Resolved By        : rtable-u
 
Up JP State        : Joined             Up JP Expiry       : 0d 00:00:06
Up JP Rpt          : Not Joined StarG   Up JP Rpt Override : 0d 00:00:00
 
Register State     : No Info            
Reg From Anycast RP: No                 
 
Rpf Neighbor       : 192.0.2.2
Incoming Intf      : mpls-if-73735
Outgoing Intf List : to-receiver
 
Curr Fwding Rate   : 719.808 kbps       
Forwarded Packets  : 4917               Discarded Packets  : 0
Forwarded Octets   : 4808826            RPF Mismatches     : 0
Spt threshold      : 0 kbps             ECMP opt threshold : 7
Admin bandwidth    : 1 kbps             
-------------------------------------------------------------------------------
Groups : 1
===============================================================================
[/]
A:admin@PE-7# show router "1" pim tunnel-interface

===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface                        Originator Address   Adm  Opr  Transport Type
-------------------------------------------------------------------------------
mpls-if-73732                    192.0.2.7            Up   Up   Tx-IPMSI
mpls-if-73733                    192.0.2.8            Up   Up   Rx-IPMSI
mpls-if-73734                    192.0.2.3            Up   Up   Rx-IPMSI
mpls-if-73735                    192.0.2.2            Up   Up   Rx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================

PE-5 receives MC traffic from the locally connected MC source and forwards it to PE-2 and PE-3. PE-3 (MEG/PEG non-DR) forwards the MC traffic only to PE-2 (MEG/PEG DR). PE-2 forwards the MC traffic to PE-3, PE-7, and PE-8. PE-8 has no MC receivers. PE-7 forwards the MC traffic to the MC receiver that requested the group membership.

Delayed MEG/PEG DR election

Upon booting up an OISM MEG/PEG router, the advertising of its IMET routes for the SBD and the start of the MEG/PEG DR election are delayed until after the boot timer expires.

The boot timer is configured on the MEG/PEG DR candidate that is expected to become the MEG/PEG DR after MEG/PEG election, as follows:
# On PE-2:
[ex:/configure redundancy bgp-evpn ethernet-segment]
A:admin@PE-2#                 boot-timer ?

 boot-timer <number>
 <number> - <0..1800> - seconds
 Default  - 10

    Time before BGP EVPN multi-homing DF election algorithm
As an example, the PE-2 configuration is saved, the boot-timer on PE-2 is set to 180 seconds, and PE-2 is rebooted.
# On PE-2:
configure {
    redundancy {
        bgp-evpn ethernet-segment {
            boot-timer 180
After the reboot, PE-2 waits 180 seconds before advertising its IMET routes and starting the MEG/PEG DR election. During that time, PE-2 is not in the candidate list and PE-3 is the MEG/PEG DR.
[/]
A:admin@PE-2# show service id "SBD-8" evpn-mcast-gateway all

===============================================================================
Service Evpn Multicast Gateway
===============================================================================
Type                         : mvpn-pim                
Admin State                  : Enabled                 
DR Activation Timer          : 3 secs                  
Mvpn Evpn Gateway DR         : No                      
Pim  Evpn Gateway DR         : No                      
===============================================================================

===============================================================================
Mvpn Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : No                      
DR Last Change               : 01/09/2025 14:05:32     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================

===============================================================================
Pim Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : No                      
DR Last Change               : 01/09/2025 14:05:32     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
When the command is launched a little later on PE-2, PE-3 is already in the candidate list.
[/]
A:admin@PE-3# show service id "SBD-8" evpn-mcast-gateway all

===============================================================================
Service Evpn Multicast Gateway
===============================================================================
Type                         : mvpn-pim                
Admin State                  : Enabled                 
DR Activation Timer          : 3 secs                  
Mvpn Evpn Gateway DR         : Yes                     
Pim  Evpn Gateway DR         : Yes                     
===============================================================================

===============================================================================
Mvpn Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : Yes                     
DR Last Change               : 01/09/2025 14:04:28     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.3                               01/09/2025 13:36:51
-------------------------------------------------------------------------------
Number of Entries: 1
===============================================================================

===============================================================================
Pim Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : Yes                     
DR Last Change               : 01/09/2025 14:04:28     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.3                               01/09/2025 13:36:51
-------------------------------------------------------------------------------
Number of Entries: 1
===============================================================================
When the reboot timer expires, PE-2 sends its IMET routes:
# On PE-2:
9 2025/01/09 14:13:16.051 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.1
"Peer 1: 192.0.2.1: UPDATE
Peer 1: 192.0.2.1 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 109
    Flag: 0x90 Type: 14 Len: 28 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 192.0.2.2
        Type: EVPN-INCL-MCAST Len: 17 RD: 192.0.2.2:8, tag: 0, 
orig_addr len: 32, orig_addr: 192.0.2.2 
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
    Flag: 0xc0 Type: 16 Len: 32 Extended Community:
        target:64500:8
        mcast-flags:SBD/MEG/PEG/OISM/NO-MLD-Proxy/NO-IGMP-Proxy
        df-election::DF-Type:Auto/DP:0/DF-Preference:0/AC:0
        bgp-tunnel-encap:MPLS
    Flag: 0xc0 Type: 22 Len: 25 PMSI:
        Tunnel-type Composite LDP P2MP IR (130)
        Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
        MPLS Label1 Ag  0
        MPLS Label2 IR 8388544
        Root-Node 192.0.2.2, LSP-ID 0x2001
"
PE-2 is added to the candidate list and becomes the new MEG/PEG DR.
[/]
A:admin@PE-2# show service id "SBD-8" evpn-mcast-gateway all

===============================================================================
Service Evpn Multicast Gateway
===============================================================================
Type                         : mvpn-pim                
Admin State                  : Enabled                 
DR Activation Timer          : 3 secs                  
Mvpn Evpn Gateway DR         : Yes                     
Pim  Evpn Gateway DR         : Yes                     
===============================================================================

===============================================================================
Mvpn Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : Yes                     
DR Last Change               : 01/09/2025 14:08:01     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.2                               01/09/2025 14:08:01
192.0.2.3                               01/09/2025 14:06:31
-------------------------------------------------------------------------------
Number of Entries: 2
===============================================================================

===============================================================================
Pim Evpn Gateway
===============================================================================
DR Activation Timer Remaining: 0 secs                  
DR                           : Yes                     
DR Last Change               : 01/09/2025 14:08:01     
===============================================================================

===============================================================================
Candidate list
===============================================================================
Orig-Ip                                 Time Added
-------------------------------------------------------------------------------
192.0.2.2                               01/09/2025 14:08:01
192.0.2.3                               01/09/2025 14:06:31
-------------------------------------------------------------------------------
Number of Entries: 2
===============================================================================

Conclusion

SR OS supports the interworking of OISM EVPN networks and MVPN/PIM networks in both directions. The choice for the upstream multicast hop selection can be configured. The start of the MEG/PEG DR election can be configured with the boot timer.