EVPN S-PMSI A-D routes
This chapter provides information about the support of Selective Provider Multicast Service Interface Auto-Discovery (S-PMSI A-D) routes in EVPN networks.
Topics in this chapter include:
Applicability
The information and configuration in this chapter are based on SR OS Release 25.3.R2. S-PMSI A-D routes in EVPN are supported in SR OS Release 23.3 and later.
Overview
SR OS Releases earlier than SR OS Release 23.3 support route types (RT) 1 through 8. SR OS Release 23.3 and later also support RT 10.
| Type | Description | Usage |
|---|---|---|
| 1 | Ethernet Auto-Discovery (AD) |
Multi-homing:
EVPN-VPWS EVPN-E-Tree |
| 2 | MAC/IP Advertisement | Host MAC/IP dissemination with mobility and protection |
| 3 | Inclusive Multicast Ethernet Tag (IMET) | PE discovery and BUM tree setup |
| 4 | Ethernet Segment (ES) | Multi-homing: ES discovery and DF Election |
| 5 | IP-Prefix (RT5) | IP-Prefix dissemination (IPv4 and IPv6) |
| 6 | Selective Multicast Ethernet Tag (SMET) | Indicates interest for a multicast (*,G) or (S,G) (IPv4 or IPv6) |
| 7 | Mcast Join Synch | Multi-homing: (*,G) or (S,G) join state synch |
| 8 | Mcast Leave Synch | Multi-homing: (*,G) or (S,G) leave state synch |
| 9 | Per-Region I-PMSI A-D | BUM tree creation across regions (domains or AS) |
| 10 | S-PMSI A-D | Explicit Selective PMSI creation for (*,G) or (S,G) |
| 11 | Leaf A-D | Used as a response to explicit tracking requests |
- Basic/single homed VPLS services use RT 2 and RT 3
- Basic/single homed Epipes use RT 1
- When the services are multi homed, RT 1 and RT 4 are also used
- VPRNs use RT 5 for IP signalling. When proxy-arp is enabled, RT 2 is used to signal MAC/IP combinations
- multicast services in EVPN (L3 OISM) use RT 6, RT 7, RT 8, and RT 10
- routed VPLS services that are configured in Optimized Inter-Subset Multicast (OISM) mode
- EVPN VPLS services that are configured with igmp-snooping evpn-proxy or mld-snooping evpn-proxy
- Multicast Label Distribution Protocol (MLDP) wildcard S-PMSI tunnels: used to optimize the delivery of multicast (MC) traffic and forward it to only PEs with IP MC sources or receivers. Wildcard S-PMSIs are enabled with: configure service vpls <vpls> provider-tunnel selective wildcard-spmsi true
- MLDP specific S-PMSI tunnels for (S,G) and (*,G) MC groups: used to optimize the delivery of some MC groups that have receivers only in a limited number of PEs. (S,G) and (*,G) are triggered based on a BW threshold or number of receiver PEs. Specific S-PMSIs are enabled with: configure service vpls <vpls> provider-tunnel selective data-threshold
The configuration options for selective provider tunnels are as follows:
# On PE-1:
configure {
service {
vpls "SBD-8" {
provider-tunnel {
tree detail
[ex:/configure service vpls "SBD-8" provider-tunnel]
A:admin@PE-1# tree detail
+-- apply-groups <reference>
+-- apply-groups-exclude <reference>
+-- inclusive
---snip---
+-- selective
+-- admin-state <keyword>
+-- data-delay-interval <number>
+-- data-threshold
| +-- group-prefix <multicast-ipv4-address-and-prefix |
multicast-ipv6-address-and-prefix>
| +-- apply-groups <reference>
| +-- apply-groups-exclude <reference>
| +-- pe-threshold-add <number>
| +-- pe-threshold-delete <number>
| +-- threshold <number>
+-- maximum-p2mp-spmsi <number>
+-- mldp <boolean>
+-- owner <keyword>
+-- wildcard-spmsi <boolean>- leaf role: configure the selective provider tunnel with only:
- mldp true
- admin-state enable
- root-and-leaf role: configure the selective provider tunnel with:
- mldp true
- admin-state enable
- wildcard-spmsi true or data-threshold or both
The inclusive provider tunnel handles IMET routes (MLDP and composite). The selective provider tunnel handles the S-PMSI A-D routes (only MLDP). Inclusive provider tunnels and selective provider tunnels cannot be configured as admin-state enable at the same time.
The S-PMSI A-D route is specified in draft-ietf-bess-evpn-bum-procedure-updates. When a service is configured to advertise wildcard S-PMSI routes, an RT 10 with Source and Group being all zeros (wildcard S-PMSI) is advertised. For specific S-PMSI routes, an RT 10 with Source and Group populated as in the case of the other MC routes (specific S-PMSI) is advertised. The S-PMSI A-D route is supported in the Provider Tunnel Attribute (PTA) along with the only supported tunnel type: MLDP.
| RD (8 octets) |
| Ethernet Tag ID (4 octets) |
| Multicast Source Length (1 octet) |
| Multicast Source Address (variable) |
| Multicast Group Length (1 octet) |
| Multicast Group Address (Variable) |
| Originator Router Length (1 octet) |
| Originator Router Address (variable) |
For policy support, the evpn-type command is extended to support RT 10 (selective-pmsi-auto-discovery). The existing source-address and group-address commands can match the corresponding fields in the S-PMSI A-D routes.
# On PE-1:
configure {
policy-options {
policy-statement "dummy-policy-statement" {
entry 10 {
from {
evpn-type ?
*[ex:/configure policy-options policy-statement "dummy-policy-statement" entry 10 from]
A:admin@PE-1# evpn-type ?
evpn-type <keyword>
<keyword> - (ethernet-auto-discovery|mac-ip-advertisement|inclusive-multicast|
ethernet-segment|ip-prefix|selective-multicast|multicast-join-sync|multicast-leave-sync|
selective-pmsi-auto-discovery)
EVPN type as a match criterion for the entryconfigure {
policy-options {
policy-statement "dummy-policy-statement" {
entry 10 {
from {
source-address ?
*[ex:/configure policy-options policy-statement "dummy-policy-statement" entry 10 from]
A:admin@PE-1# source-address ?
source-address
Choice: source-address
ip-address :- Source IP address to match
prefix-list :- Name of a source address prefix list to matchconfigure {
policy-options {
policy-statement "dummy-policy-statement" {
entry 10 {
from {
group-address ?
*[ex:/configure policy-options policy-statement "dummy-policy-statement" entry 10 from]
A:admin@PE-1# group-address ?
group-address (<string> | <reference>)
<string> - <1..32 characters>
<reference> - <1..64 characters> - configure policy-options prefix-list <name>
Prefix list of multicast group addresses for mathcingConfiguration
- cards, MDAs, ports
- router interfaces
- IS-IS on the router interfaces (OSPF or OSPF3 router interfaces are also possible)
- IBGP in the EVPN network for the EVPN address family
- LDP
Router configuration
# On PE-1:
configure {
router "Base" {
autonomous-system 64500
interface "int-PE-1-PE-2" {
port 1/1/c2/1:10
ipv4 {
primary {
address 192.168.12.1
prefix-length 30
}
}
ipv6 {
address 2001:db8::168:12:1 {
prefix-length 126
}
}
}
interface "int-PE-1-PE-3" {
port 1/1/c3/1:10
ipv4 {
primary {
address 192.168.13.1
prefix-length 30
}
}
ipv6 {
address 2001:db8::168:13: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-PE-1-PE-2" {
interface-type point-to-point
}
interface "int-PE-1-PE-3" {
interface-type point-to-point
}
interface "system" { }
level 2 {
wide-metrics-only true
}
}
ldp {
interface-parameters {
interface "int-PE-1-PE-2" {
ipv4 { }
ipv6 { }
}
interface "int-PE-1-PE-3" {
ipv4 { }
ipv6 { }
}
}
}The router configuration on PE-2 and PE-3 is similar.
The IBGP configuration on PE-1 is as follows:
# On PE-1:
configure {
router "Base" {
bgp {
rapid-withdrawal true
peer-ip-tracking true
rapid-update {
evpn true
}
group "iBGP" {
type internal
}
neighbor "192.0.2.2" {
group "iBGP"
family {
evpn true
}
}
neighbor "192.0.2.3" {
group "iBGP"
family {
evpn true
}
}
}The IBGP configuration on PE-2 and PE-3 is similar.
Service configuration in the EVPN network
Routed VPLS 8 (SBD-8) is configured on PE-1, PE-2, and PE-3, as follows:
# On PE-1, PE-2, PE-3:
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
}
sel-mcast { # not on PE-1
advertise true
}
}
mpls 1 {
admin-state enable
auto-bind-tunnel {
resolution any
}
}
}
provider-tunnel {
selective {
admin-state enable
owner bgp-evpn-mpls
mldp true
}
}Routed VPLS 3 (BD-3) is configured only on PE-1 and on PE-2, as follows:
# On PE-1, PE-2:
configure {
service {
vpls "BD-3" {
admin-state disable
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 { # sap 1/1/c5/1:3 instead on PE-2
igmp-snooping {
mrouter-port true # fast-leave instead on PE-2
}
}
provider-tunnel {
selective {
admin-state enable
owner bgp-evpn-mpls
wildcard-spmsi true
mldp true
}
}Multicast sources are connected only to PE-1. Multicast receivers are connected to all three PEs.
Routed VPLS 3 (BD-3) connects MC source S1 (IP address 10.3.0.11) on PE-1, and MC receiver R2 (IP address 10.3.0.32) on PE-2.
Routed VPLS 4 (BD-4) is configured similarly on PE-1 only. It connects MC receiver R1 (IP address 10.4.0.21) on PE-1.
Routed VPLS 5 (BD-5) is configured similarly on PE-3 only. It connects MC receiver R3 (IP address 10.5.0.43) on PE-3.
VPRN 1 is configured on PE-1, PE-2, and PE-3, as follows:
# On PE-1:
configure {
service {
vprn "VPRN 1" {
admin-state enable
service-id 1
customer "1"
igmp {
interface "int-BD-3" { }
interface "int-BD-4" { }
}
pim {
apply-to all
interface "int-SBD-8" {
multicast-senders always
}
}
interface "int-BD-3" {
description "to_S1"
ipv4 {
primary {
address 10.3.0.1
prefix-length 24
}
}
vpls "BD-3" { }
}
interface "int-BD-4" {
description "to_R1"
ipv4 {
primary {
address 10.4.0.1
prefix-length 24
}
}
vpls "BD-4" { }
}
interface "int-SBD-8" {
vpls "SBD-8" {
evpn-tunnel {
supplementary-broadcast-domain true
}
}
}The VPRN 1 configuration on PE-2 and PE-3 is similar, on top of the applicable routed VPLSs that connect only MC receivers.
Use cases
The following use cases are described in the following sections:
Advertising S-PMSI A-D routes in OISM mode
An OISM EVPN network hosts PE-1, PE-2, and PE-3 that are connected via SBD-8. S1 connected to PE-1 via BD-3 sends MC traffic for MC group G1: 239.0.0.1 to R1 connected to PE-1 via BD-4, R2 connected to PE-2 via BD-3, and R3 connected to PE-3 via BD-5. VPRN 1 has BD-3, BD-4, BD-5, and SBD-8 as interfaces in the appropriate PEs. R2 joins with an (S1,G1) IGMP/MLD v3 membership report for G1. R3 joins with a (*,G1) IGMP/MLD v3 membership report for G1.
- with the BD-RT / SBD-RT (target:64500:3 target:64500:8) and the RD (192.0.2.1:3) of the ordinary BD where the selective provider tunnel is configured.
- with the SBD-RT only if PE-1 advertises the route for the SBD. This is only in cases where the PE is a MEG/PEG.
where RT is the route target and RD is the route distinguisher. The ordinary BD (broadcast domain) is a routed VPLS where the MC sources and the MC receivers are connected, and SBD (supplementary broadcast domain) is a backhaul routed VPLS configured as an EVPN tree. The SBD is needed to allow sending MC traffic to PEs that are not attached to the source ordinary BD.
Wildcard S-PMSI trees
No active MC sources and no joined MC receivers
# On PE-1:
configure {
service {
vpls "BD-3" {
provider-tunnel {
selective {
admin-state enable
owner bgp-evpn-mpls
wildcard-spmsi true
mldp true
}
}
---snip---When PE-2 and PE-3 receive the EVPN-INCL-MCAST BGP update message from PE-1, only PE-2 imports the IMET route for BD-3, based on the BD-3 RT, because PE-3 does not have BD-3 configured:
# On PE-1:
34 2025/05/06 09:53:28.869 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.2
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 85
Flag: 0x90 Type: 14 Len: 28 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.1
Type: EVPN-INCL-MCAST Len: 17 RD: 192.0.2.1:3, tag: 0,
orig_addr len: 32, orig_addr: 192.0.2.1
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: 24 Extended Community:
target:64500:3
mcast-flags:NO-SBD/NO-MEG/NO-PEG/OISM/NO-MLD-Proxy/NO-IGMP-Proxy
bgp-tunnel-encap:MPLS
Flag: 0xc0 Type: 22 Len: 9 PMSI:
Tunnel-type Ingress Replication (6)
Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
MPLS Label 8388480
Tunnel-Endpoint 192.0.2.1
"[/show router bgp routes evpn]
A:admin@PE-2# incl-mcast
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN Inclusive-Mcast Routes
===============================================================================
Flag Route Dist. OrigAddr
Tag NextHop
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 192.0.2.1
0 192.0.2.1
u*>i 192.0.2.1:8 192.0.2.1
0 192.0.2.1
u*>i 192.0.2.3:8 192.0.2.3
0 192.0.2.3
-------------------------------------------------------------------------------
Routes : 3
===============================================================================[/show router bgp routes evpn]
A:admin@PE-3# incl-mcast
===============================================================================
BGP Router ID:192.0.2.3 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN Inclusive-Mcast Routes
===============================================================================
Flag Route Dist. OrigAddr
Tag NextHop
-------------------------------------------------------------------------------
u*>i 192.0.2.1:8 192.0.2.1
0 192.0.2.1
u*>i 192.0.2.2:8 192.0.2.2
0 192.0.2.2
-------------------------------------------------------------------------------
Routes : 2
===============================================================================When PE-2 and PE-3 receive the wildcard EVPN-SPMSI-AD BGP update message from PE-1:
# On PE-1:
28 2025/05/06 09:53:28.869 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.2
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 100
Flag: 0x90 Type: 14 Len: 30 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.1
Type: EVPN-SPMSI-AD Len: 19 RD: 192.0.2.1:3, tag: 0,
Mcast-Src-Len: 32, Mcast-Src-Addr: 0.0.0.0,
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 0.0.0.0,
Orig Addr: 192.0.2.1/32
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: 24 Extended Community:
target:64500:3
target:64500:8
bgp-tunnel-encap:MPLS
Flag: 0xc0 Type: 22 Len: 22 PMSI:
Tunnel-type LDP P2MP LSP (2)
Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
MPLS Label 0
Root-Node 192.0.2.1, LSP-ID 0x2001
"Both PE-2 and PE-3 import the wildcard route:
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 0.0.0.0
0 0.0.0.0
192.0.2.1
-------------------------------------------------------------------------------
Routes : 1
===============================================================================Identical on PE-3.
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad detail
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Original Attributes
Network : n/a
Nexthop : 192.0.2.1
Path Id : None
From : 192.0.2.1
Res. Nexthop : 192.168.12.1
Local Pref. : 100 Interface Name : int-PE-2-PE-1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : target:64500:3 target:64500:8 bgp-tunnel-encap:MPLS
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 192.0.2.1
Origin : IGP
Flags : Used Valid Best
Route Source : Internal
AS-Path : No As-Path
EVPN type : SPMSI-AD
Tag : 0
Src IP : 0.0.0.0
Grp IP : 0.0.0.0
Originator IP : 192.0.2.1
Route Dist. : 192.0.2.1:3
Route Tag : 0
Neighbor-AS : n/a
DB Orig Val : N/A Final Orig Val : N/A
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h08m20s
-------------------------------------------------------------------------------
PMSI Tunnel Attributes :
Tunnel-type : LDP P2MP LSP
Flags : Type: RNVE(0) BM: 0 U: 0 Leaf: not required
MPLS Label : LABEL 0
Root-Node : 192.0.2.1 LSP-ID : 8193
-------------------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
Routes : 1
===============================================================================The integer value 8193 for the LSP-ID corresponds with the hexadecimal value 0x2001 in the wildcard EVPN-SPMSI-AD BGP update message.
When PE-1 receives the EVPN-MAC BGP update message from PE-2:
# On PE-2:
11 2025/05/06 09:53:23.952 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 = 93
Flag: 0x90 Type: 14 Len: 48 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.2
Type: EVPN-MAC Len: 37 RD: 192.0.2.2:3 ESI: ESI-0, tag: 0,
mac len: 48 mac: 00:02:fe:ff:ff:40, IP len: 4, IP: 10.3.0.3,
label1: 8388480 (Raw Label: 0x7fff80)
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: 24 Extended Community:
target:64500:3
bgp-tunnel-encap:MPLS
mac-mobility:Seq:0/Static
"PE-1 imports the MAC route for int-BD-3 on PE-2:
[/show router bgp routes evpn]
A:admin@PE-1# mac
===============================================================================
BGP Router ID:192.0.2.1 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
u*>i 192.0.2.2:3 00:02:fe:ff:ff:40 ESI-0 # int-BD-3 on PE-2
0 Static LABEL 524280
10.3.0.3
192.0.2.2
-------------------------------------------------------------------------------
Routes : 1
===============================================================================When PE-2 and PE-3 receive the EVPN-MAC BGP update message from PE-1:
# On PE-1:
33 2025/05/06 09:53:28.869 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.2
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 93
Flag: 0x90 Type: 14 Len: 48 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.1
Type: EVPN-MAC Len: 37 RD: 192.0.2.1:3 ESI: ESI-0, tag: 0,
mac len: 48 mac: 00:01:fe:ff:ff:40, IP len: 4, IP: 10.3.0.1,
label1: 8388496 (Raw Label: 0x7fff90)
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: 24 Extended Community:
target:64500:3
bgp-tunnel-encap:MPLS
mac-mobility:Seq:0/Static
"Only PE-2 imports the MAC route for int-BD-3 on PE-1:
[/show router bgp routes evpn]
A:admin@PE-2# mac
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 00:01:fe:ff:ff:40 ESI-0 # int-BD-3 on PE-1
0 Static LABEL 524281
10.3.0.1
192.0.2.1
-------------------------------------------------------------------------------
Routes : 1
===============================================================================[/show router bgp routes evpn]
A:admin@PE-3# mac
===============================================================================
BGP Router ID:192.0.2.3 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
No Matching Entries Found.
===============================================================================The PEs build up the IGMP router port list, using IGMP snooping. For remote IGMP router ports in the same ordinary BD as the querier, the MPLS tunnel with ID mpls:<destination IP>:<egress label> for the ordinary BD is used. When there is both a BD destination (BD-3) and an SBD destination (SBD-8) to the same PE (PE-2), the BD destination has priority over the SBD destination. IGMP only uses the BD destination then in the MFIB. The SBD destination to PE-2 is Down as long as the BD destination to PE-2 is Up.
[/]
A:admin@PE-1# show service id "BD-3" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 3
===============================================================================
Admin State : Up
Querier : 10.3.0.1 on rvpls int-BD-3
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
sap:1/1/c4/1:3 Up Yes No No None None None Local 0
rvpls Up Yes No N/A N/A N/A N/A N/A N/A
mpls:192.0.2.2:524279
Up No No N/A N/A N/A N/A N/A 0
sbd-mpls:192.0.2.2:524281
Down No No N/A N/A N/A N/A N/A 0
sbd-mpls:192.0.2.3:524281
Up No No N/A N/A N/A N/A N/A 0
===============================================================================For remote IGMP router ports in a different BD as the querier, the MPLS tunnel with ID sbd-mpls:<destination IP>:<egress label> for the SBD is used.
[/]
A:admin@PE-1# show service id "BD-4" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 4
===============================================================================
Admin State : Up
Querier : 10.4.0.1 on rvpls int-BD-4
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
sap:1/1/c5/1:4 Up No No Yes None None None Local 0
rvpls Up Yes No N/A N/A N/A N/A N/A N/A
sbd-mpls:192.0.2.2:524281
Up No No N/A N/A N/A N/A N/A 0
sbd-mpls:192.0.2.3:524281
Up No No N/A N/A N/A N/A N/A 0
===============================================================================For remote IGMP router ports in the SBD, the MPLS tunnel with ID sbd-mpls:<destination IP>:<egress label> for the SBD is used.
[/]
A:admin@PE-1# show service id "SBD-8" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 8
===============================================================================
Admin State : Up
Querier : No querier found
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
rvpls Up No No N/A N/A N/A N/A N/A N/A
sbd-mpls:192.0.2.2:524281
Up No No N/A N/A N/A N/A N/A 0
sbd-mpls:192.0.2.3:524281
Up No No N/A N/A N/A N/A N/A 0
===============================================================================Before SR OS Release 23.3, PE-1 sent MC traffic and BUM traffic to any PE with I-PMSI behavior and joined MC receivers, irrespective of the BD that the MC receivers were attached to. From SR OS Release 23.3 onwards, PE-1 sends MC traffic to any PE with I-PMSI behavior and joined MC receivers, and BUM traffic only to PEs with I-PMSI behavior and joined MC receivers that are attached to the source BD-3. PE-1 does not send BUM traffic to PEs that are attached to the SBD only.
[/]
A:admin@PE-1# show service id "BD-3" evpn-mpls
===============================================================================
BGP EVPN-MPLS Dest (Instance 1)
===============================================================================
TEP Address Transport:Tnl Egr Label Oper Mcast Num
State MACs
-------------------------------------------------------------------------------
192.0.2.2 ldp:65537 524279 Up bum 0
192.0.2.2 ldp:65537 524280 Up none 1
192.0.2.2 ldp:65537 524281 Up m 0
192.0.2.3 ldp:65539 524281 Up m 0
-------------------------------------------------------------------------------
Number of entries: 4
-------------------------------------------------------------------------------
===============================================================================
---snip---
===============================================================================[/]
A:admin@PE-1# show service id "BD-4" evpn-mpls
===============================================================================
BGP EVPN-MPLS Dest (Instance 1)
===============================================================================
TEP Address Transport:Tnl Egr Label Oper Mcast Num
State MACs
-------------------------------------------------------------------------------
192.0.2.2 ldp:65537 524281 Up m 0
192.0.2.3 ldp:65539 524281 Up m 0
-------------------------------------------------------------------------------
Number of entries: 2
-------------------------------------------------------------------------------
===============================================================================
---snip---
===============================================================================[/]
A:admin@PE-1# 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.2 ldp:65537 524281 Up m 1
192.0.2.3 ldp:65539 524281 Up m 1
-------------------------------------------------------------------------------
Number of entries: 2
-------------------------------------------------------------------------------
===============================================================================
---snip---
===============================================================================S1 starts
When S1 starts (with MC traffic rate 1000 kbps from S1), S1 joins G1 in BD-3 on PE-1:
[/]
A:admin@PE-1# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (S,G) int-BD-3 0
10.3.0.11
-------------------------------------------------------------------------------
Groups : 1
===============================================================================When PE-2 receives the EVPN-MAC BGP update message from PE-1:
# On PE-1:
1 2025/05/06 10:23:05.574 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.2
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 81
Flag: 0x90 Type: 14 Len: 44 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.1
Type: EVPN-MAC Len: 33 RD: 192.0.2.1:3 ESI: ESI-0, tag: 0,
mac len: 48 mac: 00:10:94:03:00:0b, IP len: 0, IP: NULL,
label1: 8388496 (Raw Label: 0x7fff90)
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:3
bgp-tunnel-encap:MPLS
"PE-2 imports the MAC route for S1 on PE-1. PE-3 does not, because PE-3 does not have BD-3 configured.
[/show router bgp routes evpn]
A:admin@PE-2# mac
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 00:01:fe:ff:ff:40 ESI-0 # int-BD-3 on PE-1
0 Static LABEL 524281
10.3.0.1
192.0.2.1
u*>i 192.0.2.1:3 00:10:94:03:00:0b ESI-0 # S1
0 Seq:0 LABEL 524281
n/a
192.0.2.1
-------------------------------------------------------------------------------
Routes : 2
===============================================================================The MC traffic that PE-1 receives from S1 is not forwarded: the OIL is empty, because there are no MC receivers that sent an IGMP/MLD v3 membership report for G1.
[/]
A:admin@PE-1# show router 1 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : 10.3.0.11
RP Address : 0
Advt Router : 192.0.2.1
Flags : Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.3.0.11
MRIB Src Flags : direct
Keepalive Timer Exp: 0d 00:00:16
Up Time : 0d 00:03:14 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.3.0.11
Incoming Intf : int-BD-3
Outgoing Intf List :
Curr Fwding Rate : 958.440 kbps
Forwarded Packets : 23797 Discarded Packets : 0
Forwarded Octets : 23273466 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
-------------------------------------------------------------------------------
Groups : 1
===============================================================================Configuring data-delay-interval
When only wildcard-spmsi true is configured, the data-delay-interval (in seconds) for the selective provider tunnel determines the delay for the IP MC traffic to switch from the ingress replication (IR) binds over to the wildcard S-PMSI tree on the PE where the MC source is connected (PE-1).
# On PE-1 and PE-2:
configure {
service {
vpls "BD-3" {
provider-tunnel {
selective {
owner bgp-evpn-mpls
wildcard-spmsi true
data-delay-interval 100
delete maximum-p2mp-spmsi
mldp trueJoining the wildcard S-PMSI tree
As long as there are no MC receivers that sent an IGMP/MLD v3 membership report for G1, the wildcard S-PMSI tree for BD-3 remains in state TX Join Pending on PE-1:
[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:00:00
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Join Pending
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================Because the S-PMSI tree is not terminated, it is operationally down for BD-3 on PE-1 and PE-1 does not forward MC traffic that it receives from S1 (on incoming interface int-BD-3) through the S-PMSI tree:
[/]
A:admin@PE-1# tools dump service id "BD-3" provider-tunnels type originating
---snip---
======================================================================================
VPLS 3 Selective Provider Tunnels Originating
======================================================================================
spmsi (LDP) Source-Addr Group-Addr Root-Addr LSP-ID Oper-State
----------------------------------------------------------------------------------------
* * 192.0.2.1 8193 Down
--------------------------------------------------------------------------------------IGMP join on PE-2 (BD-3)
IGMP join behavior during the delay interval
R2 joins G1 in BD-3 on PE-2:
[/]
A:admin@PE-2# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (S,G) int-BD-3 1
10.3.0.11
-------------------------------------------------------------------------------
Groups : 1
===============================================================================When PE-2 receives the local (S1,G1) IGMP/MLD v3 membership report for G1 from R2, PE-2 sends an EVPN-MAC and an (S1,G1) EVPN-SMET BGP update message. The EVPN-MAC BGP update message indicates that R2 is connected to BD-3 on PE-2.
# On PE-2:
1 2025/05/06 10:31:21.024 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 = 81
Flag: 0x90 Type: 14 Len: 44 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.2
Type: EVPN-MAC Len: 33 RD: 192.0.2.2:3 ESI: ESI-0, tag: 0,
mac len: 48 mac: 00:10:94:03:00:20, IP len: 0, IP: NULL,
label1: 8388480 (Raw Label: 0x7fff80)
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:3
bgp-tunnel-encap:MPLS
"PE-1 imports the MAC route for R2:
[/show router bgp routes evpn]
A:admin@PE-1# mac
===============================================================================
BGP Router ID:192.0.2.1 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
u*>i 192.0.2.2:3 00:02:fe:ff:ff:40 ESI-0 # int-BD-3 on PE-2
0 Static LABEL 524280
10.3.0.3
192.0.2.2
u*>i 192.0.2.2:3 00:10:94:03:00:20 ESI-0 # R2
0 Seq:0 LABEL 524280
n/a
192.0.2.2
-------------------------------------------------------------------------------
Routes : 2
===============================================================================The (S1,G1) EVPN-SMET BGP update message indicates that R2 joins G1 for MC traffic from S1.
# On PE-2:
4 2025/05/06 10:31:21.024 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.2
Type: EVPN-SMET Len: 28 RD: 192.0.2.2:8, tag: 0,
Mcast-Src-Len: 32, Mcast-Src-Addr: 10.3.0.11,
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 239.0.0.1,
Orig Addr: 192.0.2.2/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
"PE-1 imports the SMET route:
[/show router bgp routes evpn]
A:admin@PE-1# smet
===============================================================================
BGP Router ID:192.0.2.1 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 10.3.0.11 # S1
0 239.0.0.1
192.0.2.2
192.0.2.2
-------------------------------------------------------------------------------
Routes : 1
===============================================================================When R2 on PE-2 joins G1, the wildcard S-PMSI tree transits to state RX Joined on PE-2 (without delay), while the wildcard S-PMSI tree remains in state TX Join Pending on PE-1 for the duration of data-delay-interval.
[/]
A:admin@PE-2# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:02:08
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:00:00
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Join Pending
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================During the data-delay-interval, the wildcard S-PMSI tree is already operationally up for BD-3 on PE-1, but PE-1 still does not use it for BD-3:
[/]
A:admin@PE-1# tools dump service id "BD-3" provider-tunnels type originating
---snip---
======================================================================================
VPLS 3 Selective Provider Tunnels Originating
======================================================================================
spmsi (LDP) Source-Addr Group-Addr Root-Addr LSP-ID Oper-State
----------------------------------------------------------------------------------------
* * 192.0.2.1 8193 Up
--------------------------------------------------------------------------------------[/]
A:admin@PE-1# show router ldp bindings active p2mp ipv4
===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.1)
(IPv6 LSR ID 2001:db8::2:1)
===============================================================================
---snip---
===============================================================================
LDP Generic IPv4 P2MP Bindings (Active)
===============================================================================
P2MP-Id Interface
RootAddr Op
IngLbl EgrLbl
EgrNH EgrIf/LspId
-------------------------------------------------------------------------------
8193 73728
192.0.2.1 Push
-- 524278
192.168.12.2 1/1/c2/1:10
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 1
===============================================================================
---snip---
===============================================================================[/]
A:admin@PE-2# tools dump service id "BD-3" provider-tunnels type terminating
---snip---
======================================================================================
VPLS 3 Selective Provider Tunnels Terminating
======================================================================================
spmsi (LDP) Source-Addr Group-Addr Root-Addr LSP-ID Oper-State
----------------------------------------------------------------------------------------
* * 192.0.2.1 8193 Up
--------------------------------------------------------------------------------------[/]
A:admin@PE-2# show router ldp bindings active p2mp ipv4
===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.2)
(IPv6 LSR ID 2001:db8::2:2)
===============================================================================
---snip---
===============================================================================
LDP Generic IPv4 P2MP Bindings (Active)
===============================================================================
P2MP-Id Interface
RootAddr Op
IngLbl EgrLbl
EgrNH EgrIf/LspId
-------------------------------------------------------------------------------
8193 73728
192.0.2.1 Pop
524278 --
-- --
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 1
===============================================================================
---snip---
===============================================================================The (S1,G1) SMET from PE-2 adds an entry in the BD-3 MFIB on PE-1 for (S1,G1). Because the local BD RT (target:64500:3) on PE-2 matches wildcard S-PMSI RT (target:64500:3) on PE-1, the entry points to the S-PMSI tree for the ordinary BD.
[/]
A:admin@PE-1# 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
10.3.0.11 239.0.0.1 sap:1/1/c4/1:3 Local Fwd
mpls:192.0.2.2:524279 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 2
===============================================================================The (S1,G1) SMET from PE-2 also adds an entry in the BD-4 MFIB on PE-1 for (S1,G1). Because the local BD RT (target:64500:4) on PE-1 does not match wildcard S-PMSI RT (target:64500:3) on PE-1, the entry points to the S-PMSI tree for the SBD.
[/]
A:admin@PE-1# show service id "BD-4" mfib
===============================================================================
Multicast FIB, Service 4
===============================================================================
Source Address Group Address Port Id Svc Id Fwd
Blk
-------------------------------------------------------------------------------
10.3.0.11 239.0.0.1 sbd-mpls:192.0.2.2:524281 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 1
===============================================================================The IGMP router port list for BD-3 indicates that IGMP router port mpls:192.0.2.2:524279 on PE-1 is a member of a MC group.
[/]
A:admin@PE-1# show service id "BD-3" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 3
===============================================================================
Admin State : Up
Querier : 10.3.0.1 on rvpls int-BD-3
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
---snip---
mpls:192.0.2.2:524279
Up No No N/A N/A N/A N/A N/A 1
---snip---
===============================================================================The IGMP router port list for BD-4 indicates that IGMP router port sbd-mpls:192.0.2.2:524281 on PE-1 is a member of a MC group.
[/]
A:admin@PE-1# show service id "BD-4" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 4
===============================================================================
Admin State : Up
Querier : 10.4.0.1 on rvpls int-BD-4
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
---snip---
sbd-mpls:192.0.2.2:524281
Up No No N/A N/A N/A N/A N/A 1
---snip---
===============================================================================PE-1 forwards MC traffic that it receives from S1 (on incoming interface int-BD-3), using IR: the OIL list has 2 outgoing interfaces:
[/]
A:admin@PE-1# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (S,G) int-BD-3 2
10.3.0.11
-------------------------------------------------------------------------------
Groups : 1
===============================================================================[/]
A:admin@PE-1# show router 1 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : 10.3.0.11
RP Address : 0
Advt Router : 192.0.2.1
Flags : Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.3.0.11
MRIB Src Flags : direct
Keepalive Timer Exp: 0d 00:01:29
Up Time : 0d 00:09:00 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.3.0.11
Incoming Intf : int-BD-3
Outgoing Intf List : int-BD-3, int-BD-4
Curr Fwding Rate : 958.440 kbps
Forwarded Packets : 66219 Discarded Packets : 0
Forwarded Octets : 64762182 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
-------------------------------------------------------------------------------
Groups : 1
===============================================================================PE-1 does not use the S-PMSI tree yet.
[/]
A:admin@PE-1# 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 Down None 3
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-1# show service id "BD-3" sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
-------------------------------------------------------------------------------
Sdp Id 32767:4294967294 -(not applicable)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 32767:4294967294 Type : VplsPmsi
---snip---
PMSI Owner : none
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : * (wildcard)
Admin State : Up Oper State : Down
---snip---
Class Fwding State : Down
Flags : ProviderTunnelDown
---snip---
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
---snip---
-------------------------------------------------------------------------------
Stp Service Destination Point specifics
-------------------------------------------------------------------------------
---snip---
Port Role : N/A Port State : Discarding
---snip---
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
===============================================================================IGMP join behavior after the delay interval expires
When the end of the data-delay-interval is reached, PE-2 joins the wildcard S-PMSI tree, based on the BD RT matching the wildcard S-PMSI RT (target:64500:3). The wildcard S-PMSI tree transits to state TX Joined on PE-1 and remains in that state when at least one PE remains joined. This is independent of the selective provider tunnels on PE-2 and PE-3 having been configured as admin-state enable or as admin-state disable for BD-3, BD-5, and SBD-8.
[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:00:27
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================# On PE-1:
configure {
service {
vpls "SBD-8" {
admin-state enable
provider-tunnel {
selective {
admin-state enable
owner bgp-evpn-mpls
mldp true
---snip---
}
}
---snip---
}
vpls "BD-3" {
admin-state enable
provider-tunnel {
selective {
admin-state enable
owner bgp-evpn-mpls
wildcard-spmsi true
mldp true
---snip---
}
}
---snip---Similar on PE-2 and on PE-3.
PE-1 sends MC traffic for G1 to PE-2 or PE-3, using the S-PMSI trees.
[/]
A:admin@PE-1# 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-1# show service id "BD-3" sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
-------------------------------------------------------------------------------
Sdp Id 32767:4294967294 -(not applicable)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 32767:4294967294 Type : VplsPmsi
---snip---
PMSI Owner : none
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : * (wildcard)
Admin State : Up Oper State : Up
---snip---
Class Fwding State : Down
Flags : None
---snip---
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 3322 E. Fwd. Octets : 3295424
---snip---
-------------------------------------------------------------------------------
Stp Service Destination Point specifics
-------------------------------------------------------------------------------
---snip---
Port Role : N/A Port State : Forwarding
---snip---
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
===============================================================================IGMP join on PE-3 (BD-5)
R3 joins G1 in BD-5 on PE-3:
[/]
A:admin@PE-3# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (*,G) 1
*
239.0.0.1 (S,G) spt int-SBD-8 1
10.3.0.11
-------------------------------------------------------------------------------
Groups : 2
===============================================================================When PE-3 receives the local (*,G1) IGMP/MLD v3 membership report for G1 from R3, PE-3 sends an EVPN-MAC and a (*,G1) EVPN-SMET BGP update message. The EVPN-MAC BGP update message indicates that R3 is connected to BD-5 on PE-3.
# On PE-3:
2 2025/05/06 10:41:10.913 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 = 81
Flag: 0x90 Type: 14 Len: 44 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.3
Type: EVPN-MAC Len: 33 RD: 192.0.2.3:5 ESI: ESI-0, tag: 0,
mac len: 48 mac: 00:10:94:05:00:2b, IP len: 0, IP: NULL,
label1: 8388480 (Raw Label: 0x7fff80)
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:5
bgp-tunnel-encap:MPLS
"PE-1 does not import the MAC route for R3.
The (*,G1) EVPN-SMET BGP update message indicates that R3 joins G1 for MC traffic from any MC source in G1.
# On PE-3:
3 2025/05/06 10:41:10.913 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 = 72
Flag: 0x90 Type: 14 Len: 35 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.3
Type: EVPN-SMET Len: 24 RD: 192.0.2.3:8, tag: 0,
Mcast-Src-Len: 0, Mcast-Src-Addr: 0.0.0.0,
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 239.0.0.1,
Orig Addr: 192.0.2.3/32, Flags(0x8): IE:1/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
"PE-1 imports the SMET route:
[/show router bgp routes evpn]
A:admin@PE-1# smet
===============================================================================
BGP Router ID:192.0.2.1 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 10.3.0.11
0 239.0.0.1
192.0.2.2
192.0.2.2
u*>i 192.0.2.3:8 0.0.0.0
0 239.0.0.1
192.0.2.3
192.0.2.3
-------------------------------------------------------------------------------
Routes : 2
===============================================================================The corresponding S-PMSI tree originates in BD-3 on PE-1 and terminates in SBD-8 on PE-3, because PE-3 has no BD RT matching the wildcard S-PMSI RT (target:64500:3). The wildcard S-PMSI tree transits to state RX Joined on PE-3 (without delay):
[/]
A:admin@PE-3# show service id "SBD-8" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:00:30
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================When the wildcard S-PMSI tree is in state TX Join Pending on PE-1, it remains in state TX Join Pending for the duration of data-delay-interval.
Because R2 has already joined, the wildcard S-PMSI tree is already in state TX Joined on PE-1:
[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:08:36
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================During the data-delay-interval, the S-PMSI tree is already operationally up for SBD-8 on PE-3.
[/]
A:admin@PE-3# tools dump service id "SBD-8" provider-tunnels type terminating
---snip---
======================================================================================
VPLS 8 Selective Provider Tunnels Terminating
======================================================================================
spmsi (LDP) Source-Addr Group-Addr Root-Addr LSP-ID Oper-State
----------------------------------------------------------------------------------------
* * 192.0.2.1 8193 Up
--------------------------------------------------------------------------------------[/]
A:admin@PE-1# show router ldp bindings active p2mp ipv4
===============================================================================
LDP Bindings (IPv4 LSR ID 192.0.2.1)
(IPv6 LSR ID 2001:db8::2:1)
===============================================================================
---snip---
===============================================================================
LDP Generic IPv4 P2MP Bindings (Active)
===============================================================================
P2MP-Id Interface
RootAddr Op
IngLbl EgrLbl
EgrNH EgrIf/LspId
-------------------------------------------------------------------------------
8193 73728
192.0.2.1 Push
-- 524278
192.168.12.2 1/1/c2/1:10
8193 73728
192.0.2.1 Push
-- 524278
192.168.13.2 1/1/c3/1:10
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 2
===============================================================================
---snip---
===============================================================================[/]
A:admin@PE-3# show router ldp bindings active p2mp ipv4
===============================================================================
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
-------------------------------------------------------------------------------
8193 73728
192.0.2.1 Pop
524278 --
-- --
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Active Bindings: 1
===============================================================================
---snip---
===============================================================================PE-1 sends MC traffic for G1 to PE-2 or PE-3, using the S-PMSI trees.
[/]
A:admin@PE-1# 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-1# show service id "BD-3" sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
-------------------------------------------------------------------------------
Sdp Id 32767:4294967294 -(not applicable)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 32767:4294967294 Type : VplsPmsi
---snip---
PMSI Owner : none
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : * (wildcard)
Admin State : Up Oper State : Up
---snip---
Class Fwding State : Down
Flags : None
---snip---
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 63381 E. Fwd. Octets : 62873952
---snip---
-------------------------------------------------------------------------------
Stp Service Destination Point specifics
-------------------------------------------------------------------------------
---snip---
Port Role : N/A Port State : Forwarding
---snip---
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
===============================================================================The (*,G1) SMET from PE-3 adds an entry in the BD-3 MFIB on PE-1 for (*,G1) and modifies the entry for (S1,G1). Because the local BD RT (target:64500:5) on PE-3 does not match wildcard S-PMSI RT (target:64500:3) on PE-1, the entries point to the S-PMSI tree for the SBD.
[/]
A:admin@PE-1# 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
* 239.0.0.1 sap:1/1/c4/1:3 Local Fwd
sbd-mpls:192.0.2.3:524281 Local Fwd
10.3.0.11 239.0.0.1 sap:1/1/c4/1:3 Local Fwd
mpls:192.0.2.2:524279 Local Fwd
sbd-mpls:192.0.2.3:524281 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================The (*,G1) SMET from PE-3 also adds an entry in the BD-4 MFIB on PE-1 for (*,G1) and modifies the entry for (S1,G1). Because the local BD RT (target:64500:5) on PE-3 does not match wildcard S-PMSI RT (target:64500:3) on PE-1, the entries point to the S-PMSI tree for the SBD.
[/]
A:admin@PE-1# show service id "BD-4" mfib
===============================================================================
Multicast FIB, Service 4
===============================================================================
Source Address Group Address Port Id Svc Id Fwd
Blk
-------------------------------------------------------------------------------
* 239.0.0.1 sbd-mpls:192.0.2.3:524281 Local Fwd
10.3.0.11 239.0.0.1 sbd-mpls:192.0.2.2:524281 Local Fwd
sbd-mpls:192.0.2.3:524281 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 2
===============================================================================The IGMP router port list for BD-3 indicates that IGMP router port sbd-mpls:192.0.2.3:524281 on PE-1 is a member of a MC group.
[/]
A:admin@PE-1# show service id "BD-3" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 3
===============================================================================
Admin State : Up
Querier : 10.3.0.1 on rvpls int-BD-3
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
---snip---
sbd-mpls:192.0.2.3:524281
Up No No N/A N/A N/A N/A N/A 1
===============================================================================The IGMP router port list for BD-4 indicates that IGMP router port sbd-mpls:192.0.2.3:524281 on PE-1 is a member of a MC group.
[/]
A:admin@PE-1# show service id "BD-4" igmp-snooping base
===============================================================================
IGMP Snooping Base info for service 4
===============================================================================
Admin State : Up
Querier : 10.4.0.1 on rvpls int-BD-4
SBD service : 8
Evpn-proxy : Disabled
-------------------------------------------------------------------------------
Port Oper MRtr Pim Send Max Max Max MVR Num
Id Stat Port Port Qrys Grps Srcs Grp From-VPLS Grps
Srcs
-------------------------------------------------------------------------------
---snip---
sbd-mpls:192.0.2.3:524281
Up No No N/A N/A N/A N/A N/A 1
===============================================================================PE-1 forwards MC traffic that it receives from S1 (on incoming interface int-BD-3), using the S-PMSI tree for (S1,G1): the OIL has 2 outgoing interfaces. PE-1 forwards MC traffic from other MC sources, using the S-PMSI tree for (*,G1): the OIL has 2 outgoing interfaces. Because there are no other MC sources than S1, the incoming interface is empty and there is no MC traffic.
[/]
A:admin@PE-1# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (*,G) 2
*
239.0.0.1 (S,G) int-BD-3 2
10.3.0.11
-------------------------------------------------------------------------------
Groups : 2
===============================================================================[/]
A:admin@PE-1# show router 1 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : *
RP Address : 0
Advt Router :
Flags : Type : (*,G)
Mode : sparse
MRIB Next Hop :
MRIB Src Flags :
Keepalive Timer : Not Running
Up Time : 0d 00:00:21 Resolved By : unresolved
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
Rpf Neighbor :
Incoming Intf :
Outgoing Intf List : int-BD-3, int-BD-4
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
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : 10.3.0.11
RP Address : 0
Advt Router : 192.0.2.1
Flags : Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.3.0.11
MRIB Src Flags : direct
Keepalive Timer Exp: 0d 00:02:53
Up Time : 0d 00:18:07 Resolved By : rtable-u
Up JP State : Joined Up JP Expiry : 0d 00:00:40
Up JP Rpt : Not Pruned 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.3.0.11
Incoming Intf : int-BD-3
Outgoing Intf List : int-BD-3, int-BD-4
Curr Fwding Rate : 962.352 kbps
Forwarded Packets : 133287 Discarded Packets : 0
Forwarded Octets : 130354686 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
-------------------------------------------------------------------------------
Groups : 2
===============================================================================At PE-2, MC traffic from S1 on PE-1 is delivered via the source BD-3, because PE-2 has local BD-3.
[/]
A:admin@PE-2# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (*,G) 1
*
239.0.0.1 (S,G) spt int-BD-3 1
10.3.0.11
-------------------------------------------------------------------------------
Groups : 2
===============================================================================[/]
A:admin@PE-2# show router 1 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : *
RP Address : 0
Advt Router :
Flags : Type : (*,G)
Mode : sparse
MRIB Next Hop :
MRIB Src Flags :
Keepalive Timer : Not Running
Up Time : 0d 00:00:22 Resolved By : unresolved
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
Rpf Neighbor :
Incoming Intf :
Outgoing Intf List : int-BD-3
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
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : 10.3.0.11
RP Address : 0
Advt Router : 192.0.2.2
Flags : spt, rpt-prn-des Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.3.0.11
MRIB Src Flags : direct
Keepalive Timer Exp: 0d 00:03:07
Up Time : 0d 00:00:22 Resolved By : rtable-u
Up JP State : Joined Up JP Expiry : 0d 00:00:57
Up JP Rpt : Pruned 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.3.0.11
Incoming Intf : int-BD-3
Outgoing Intf List : int-BD-3
Curr Fwding Rate : 958.440 kbps
Forwarded Packets : 2775 Discarded Packets : 0
Forwarded Octets : 2713950 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
-------------------------------------------------------------------------------
Groups : 2
===============================================================================At PE-3, MC traffic from S1 on PE-1 is delivered via the SBD-8, because PE-3 has local BD-5 that does not match source BD-3.
[/]
A:admin@PE-3# show router 1 pim group
===============================================================================
Legend: A = Active S = Standby
===============================================================================
PIM Groups ipv4
===============================================================================
Group Address Type Spt Bit Inc Intf No.Oifs
Source Address RP State Inc Intf(S)
-------------------------------------------------------------------------------
239.0.0.1 (*,G) 1
*
239.0.0.1 (S,G) spt int-SBD-8 1
10.3.0.11
-------------------------------------------------------------------------------
Groups : 2
===============================================================================[/]
A:admin@PE-3# show router 1 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : *
RP Address : 0
Advt Router :
Flags : Type : (*,G)
Mode : sparse
MRIB Next Hop :
MRIB Src Flags :
Keepalive Timer : Not Running
Up Time : 0d 00:00:24 Resolved By : unresolved
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
Rpf Neighbor :
Incoming Intf :
Outgoing Intf List : int-BD-5
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
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 239.0.0.1
Source Address : 10.3.0.11
RP Address : 0
Advt Router :
Flags : spt, rpt-prn-des Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.3.0.11
MRIB Src Flags : direct
Keepalive Timer Exp: 0d 00:03:05
Up Time : 0d 00:00:24 Resolved By : rtable-u
Up JP State : Joined Up JP Expiry : 0d 00:00:00
Up JP Rpt : Pruned 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.3.0.11
Incoming Intf : int-SBD-8
Outgoing Intf List : int-BD-5
Curr Fwding Rate : 958.440 kbps
Forwarded Packets : 2893 Discarded Packets : 0
Forwarded Octets : 2829354 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
-------------------------------------------------------------------------------
Groups : 2
===============================================================================Specific S-PMSI trees
When data-threshold group-prefix <multicast-ipv4-address-and-prefix|multicast-ipv6-address-and-prefix> threshold (in kbps) is configured on the selective provider tunnel on PE-1 for a specific MC group G1, PE-1 starts polling statistics for all MFIB entries that include G1. When the configured threshold (and optionally number of PEs) for (S1,G1) or (*,G1) entries is exceeded, PE-1 signals an S-PMSI A-D route for the (S1,G1) and for the (*,G1) respectively with different MLDP tree information, and after the data-delay-interval configured on the selective provider tunnel on PE-1, PE-1 starts using the new specific S-PMSI tree.
When data-threshold group-prefix <multicast-ipv4-address-and-prefix|multicast-ipv6-address-and-prefix> threshold is configured on the selective provider tunnel on PE-1 for a specific MC group G1, the data-delay-interval (in seconds) for the selective provider tunnel determines the delay for G1 to switch over to the specific S-PMSI tree on the PE where the MC source is connected (PE-1).
Stats polling
Stats polling in EVPN OISM networks is based on the L3 MFIB stats, because there are no L2 MFIB stats. The L3 MFIB stats has no separate counts for (Sn,G1) and (*,G1): the counts for (*,G1) may include counts for (Sn,G1), because, in OISM, leaf PEs may aggregate (*,G1) and (Sn,G1) into a single (*,G1) SMET route.
When the root PE receives an (S1,G1) SMET and a (*,G1) SMET for the same MC group G1 using just 1 MC source S1, the root PE sends an S-PMSI A-D route for both the (S1,G1) and the (*,G1), when the cumulative (S1,G1) and (*,G1) MC traffic rate exceeds the S-PMSI threshold bandwidth.
For routed VPLSs, the VPLS MFIB stats are not incremented when forward-to-ip-interface true is configured for the routed-vpls multicast ipv4 context or for the routed-vpls multicast ipv6 context, because the MFIB lookup is done in the L3 context then.
[/]
A:admin@PE-1# show service id "BD-3" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 3
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* * 4 3984
0.000 kbps
* 239.0.0.1 0 0
0.000 kbps
10.3.0.11 239.0.0.1 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================When forward-to-ip-interface false is configured, there is no multicast to the SBD-8, so PE-1 does not send MC traffic to PE-3.
# On PE-1:
configure {
service {
vpls "BD-3" {
routed-vpls {
multicast {
ipv4 {
forward-to-ip-interface false
}
ipv6 {
forward-to-ip-interface false
}The VPLS MFIB stats are then increased as follows (with MC traffic rate 250 kbps from S1):
[/]
A:admin@PE-1# show service id "BD-3" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 3
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* * 4 3984
0.000 kbps
* 239.0.0.1 0 0
0.000 kbps
10.3.0.11 239.0.0.1 5583 5560668
240.804 kbps
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================[/]
A:admin@PE-1# 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
* 239.0.0.1 sap:1/1/c4/1:3 Local Fwd
sbd-mpls:192.0.2.3:524281 Local Fwd
10.3.0.11 239.0.0.1 sap:1/1/c4/1:3 Local Fwd
mpls:192.0.2.2:524279 Local Fwd
sbd-mpls:192.0.2.3:524281 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================When stats are polled for a specific (S1,G1) S-PMSI and the MFIB data traffic rate drops below the S-PMSI threshold bandwidth, a timer of 30 seconds is started. When the timer expires, the MFIB data traffic rate is verified again. If it is still below the S-PMSI threshold bandwidth, the specific S-PMSI tree is removed.
- the polling is done for each (Sn,G1) that belongs to the configured MC group G1: SR OS computes the cumulative MC data rate on G1.
- when the cumulative MC data rate on G1 exceeds the S-PMSI threshold bandwidth, the root PE initiates a specific S-PMSI A-D route for all received (Sn,G1) SMETs.
- the root PE advertises each S-PMSI A-D route with unique PTA attributes: separate MLDP trees per (Sn,G1).
- for EVPN OISM networks, the polling is done for each (Sn,G1) and (*,G1) that belongs to the configured MC group G1: SR OS computes the cumulative MC data rate on G1. This is so, because the (*,G1) SMET from a leaf PE can be the result of aggregating (Sn,G1) and (*,G1) local IGMP states.
- when the cumulative MC data rate on G1 exceeds the S-PMSI threshold bandwidth, the root PE initiates a specific S-PMSI A-D route for the received (*,G1) SMET.
- the root PE advertises the S-PMSI A-D route with unique PTA attributes: one MLDP tree for the (*,G1).
- for EVPN OISM networks, the polling is done for each (Sn,G1) and (*,G1) that belongs to the configured MC group G1: SR OS computes the cumulative MC data rate on G1. This is so, because the (*,G1) SMET from a leaf PE can be the result of aggregating (Sn,G1) and (*,G1) local IGMP states.
- when the cumulative MC data rate on G1 exceeds the S-PMSI threshold bandwidth, the root PE initiates a specific S-PMSI A-D route for the received (S1.G1) SMET and for the received (*,G1) SMET.
- the root PE advertises the S-PMSI A-D route with unique PTA attributes: one MLDP tree for the (S1,G1) and one MLDP tree for the (*,G1).
Configuring specific S-PMSI trees
The data-threshold command has group-prefix as mandatory parameter. When multiple MC group address/masks are configured for group-prefix, the one with the longest prefix match is used.
The data-threshold group-prefix command has threshold as a mandatory parameter. It specifies the S-PMSI threshold bandwidth in kbps.
The data-threshold group-prefix command has the following optional parameters, indicating a number of PEs with MC receivers that joined a specific MC group (receiver PEs):
- pe-threshold-add (range: 1.. 65535):
Specifies the number of receiver PEs for creating the S-PMSI
tree.
- When the actual number N of receiver PEs for a specific MC group is non-zero and below the value for pe-threshold-add and when the BW threshold is concurrently satisfied, the S-PMSI tree is created.
- When pe-threshold-add is not specified, value 65535 is used. This means that, irrespective of N, the add threshold is always met (N < pe-threshold-add) and when the MC traffic rate exceeds the S-PMSI threshold bandwidth for the MC group the S-PMSI tree is created.
- pe-threshold-delete (range: 2..65535):
Specifies the number of receiver PEs for deleting the S-PMSI
tree.
- When the actual number N of receiver PEs for a specific MC group is above the value for pe-threshold-delete, the S-PMSI tree is deleted and the multicast group moves to IR binds or to the wildcard S-PMSI tree if configured, or potentially to a (*,G) P2MP if the MFIB was previously using an (S,G) S-PMSI tree.
- When pe-threshold-delete is not specified, value 65535 is used. This means that, irrespective of N, the delete threshold is never met (N < pe-threshold-delete) and the S-PMSI tree is used, unless the MC traffic rate drops below the S-PMSI threshold bandwidth for the MC group.
The pe-threshold-delete must be greater than the pe-threshold-add. The CLI enforces that. It is recommended that the delete threshold is significantly larger than the add threshold, to avoid re-signaling of the S-PMSI A-D route when N fluctuates.
SR OS derives N from the number of SMET routes that are included in the MC group range for the SBD/BD. SR OS checks the originator IP of the SMET route, so that the same PE is not counted multiple times. For example, for a (*,G) S-PMSI tree created by PE-1, if PE-2 has a local MC receiver for (S1,G) and another one for (S2,G), PE-2 sends two SMET routes. However, PE-1 receives them with the same originator IP and therefore counts PE-2 as a single receiver PE.
The number of SMET routes may not always accurately match the real number of MC receivers in the network for a specific (*,G) or (S,G). For example, SMETs from a PE may be aggregated: for the local (*,G), (S1..Sm,G) state, SMETs are aggregated into a single (*,G) SMET. The root PE counts only one SMET route for that PE.
For increasing N, pe-threshold-delete causes a switch back from using a specific S-PMSI tree. For decreasing N, pe-threshold-add causes a switch to using a specific S-PMSI tree. pe-threshold-add dictates when to bring back the S-PMSI tree for a MC group, after N has hit pe-threshold-delete, in which case SR OS has deleted the S-PMSI tree for that MC group. pe-threshold-add has no implication on when to set up the S-PMSI tree, because SR OS always waits for the value of data-threshold group-prefix <multicast-ipv4-address-and-prefix|multicast-ipv6-address-and-prefix> threshold to be hit.
- pe-threshold-delete has value 5
- pe-threshold-add has value 2
- the MC traffic rate exceeds the S-PMSI threshold bandwidth for the MC group, so that a specific S-PMSI can exist
- there are no other changes to the S-PMSIs than the increase or decrease of N
| Increase N | Check | PMSI used by the root PE | Effect |
|---|---|---|---|
| from 0 to 1 | N < pe-threshold-add and N < pe-threshold-delete | specific S-PMSI | The specific S-PMSI is signaled. Traffic is carried on the specific S-PMSI |
| from 1 to 2 | N = pe-threshold-add and N < pe-threshold-delete | specific S-PMSI | Traffic remains on the specific S-PMSI |
| from 2 to 3 | N > pe-threshold-add and N < pe-threshold-delete | specific S-PMSI | Traffic remains on the specific S-PMSI |
| from 3 to 4 | N > pe-threshold-add and N < pe-threshold-delete | specific S-PMSI | Traffic remains on the specific S-PMSI |
| from 4 to 5 | N > pe-threshold-add and N = pe-threshold-delete | wildcard S-PMSI if exists, or IR |
Traffic switches back to the wildcard S-PMSI if exists, or IR otherwise. Or potentially a (*,G) S-PMSI if the MFIB was previously using it before moving to the specific (S,G) S-PMSI |
| from 5 to 6 | N > pe-threshold-add and N > pe-threshold-delete | wildcard S-PMSI if exists, or IR |
Traffic remains on the S-PMSI that is selected for N = 5 |
| from 6 to 7 | N > pe-threshold-add and N > pe-threshold-delete | wildcard S-PMSI if exists, or IR |
Traffic remains on the S-PMSI that is selected for N = 5 |
The idea behind pe-threshold-delete is that, when reached for increasing number N, there are too many PEs to justify the further use of specific S-PMSIs.
| Decrease N | Check | PMSI used by the root PE | Effect |
|---|---|---|---|
| from 7 to 6 | N > pe-threshold-add and N > pe-threshold-delete | wildcard S-PMSI if exists, or IR | Traffic remains on the S-PMSI that is selected for N = 5 |
| from 6 to 5 | N > pe-threshold-add and N = pe-threshold-delete | wildcard S-PMSI if exists, or IR | Traffic remains on the S-PMSI that is selected for N = 5 |
| from 5 to 4 | N > pe-threshold-add and N < pe-threshold-delete | wildcard S-PMSI if exists, or IR | Traffic remains on the S-PMSI that is selected for N = 5 |
| from 4 to 3 | N > pe-threshold-add and N < pe-threshold-delete | wildcard S-PMSI if exists, or IR | Traffic remains on the S-PMSI that is selected for N = 5 |
| from 3 to 2 | N = pe-threshold-add and N < pe-threshold-delete | specific S-PMSI | The specific S-PMSI is re-signaled. Traffic switches to the specific S-PMSI |
| from 2 to 1 | N < pe-threshold-add and N < pe-threshold-delete | specific S-PMSI | Traffic remains on the specific S-PMSI |
The idea behind pe-threshold-add is that, when reached for decreasing number N, the number of PEs is sufficiently low to justify the use of specific S-PMSIs.
# On PE-1:
configure {
service {
vpls "BD-3" {
provider-tunnel {
selective {
admin-state enable
owner bgp-evpn-mpls
wildcard-spmsi true
data-delay-interval 3
maximum-p2mp-spmsi 10
mldp true
data-threshold {
group-prefix 239.0.0.0/16 {
threshold 2300
}
}[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel
===============================================================================
Service Provider Tunnel Information
===============================================================================
Type : inclusive Root and Leaf : disabled
---snip---
-------------------------------------------------------------------------------
Type : selective Wildcard SPMSI : enabled
Admin State : enabled Data Delay Intvl : 3 secs
PMSI Type : mLdp Max P2MP SPMSI : 10
PMSI Owner : bgpEvpnMpls
Group range : 239.0.0.0/16
S-PMSI Threshold : 2300 kbps
PE Threshold add : 65535 PE Threshold del : 65535
===============================================================================MC traffic of S1 is below threshold
S1 on PE-1 sends MC traffic for G1 at 1000 kbps. R2 sends an (S1,G1) IGMP/MLD v3 membership report for G1. R3 sends a (*,G1) IGMP/MLD v3 membership report for G1. The measured cumulative MC traffic rate from S1 for G1 is 2*1000 = 2000 kbps < 2300 kbps, based on the receipt of both (S1,G1) and (*,G1) SMET routes.
[/]
A:admin@PE-1# show router 1 pim group 239.0.0.1 source 10.3.0.11
detail | match "Curr Fwding Rate"
Curr Fwding Rate : 958.440 kbpsPE-1 receives (S1,G1) SMET from PE-2 and (*,G1) SMET from PE-3, but does not generate a corresponding S-PMSI A-D route for either of these SMET routes.
[/show router bgp routes evpn]
A:admin@PE-1# smet
===============================================================================
BGP Router ID:192.0.2.1 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 10.3.0.11
0 239.0.0.1
192.0.2.2
192.0.2.2
u*>i 192.0.2.3:8 0.0.0.0
0 239.0.0.1
192.0.2.3
192.0.2.3
-------------------------------------------------------------------------------
Routes : 2
===============================================================================PE-2 and PE-3 only have the wildcard S-PMSI route:
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 0.0.0.0
0 0.0.0.0
192.0.2.1
-------------------------------------------------------------------------------
Routes : 1
===============================================================================Identical on PE-3.
PE-2 and PE-3 receive MC traffic from the wildcard S-PMSI trees for BD-3 and SBD-8 respectively:
[/]
A:admin@PE-2# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73730
Uptime : 0d 00:05:04
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-3# show service id "SBD-8" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73729
Uptime : 0d 00:01:48
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================MC traffic of S1 increases above threshold
The MC traffic rate from S1 increases to 1250 kbps. The measured cumulative MC traffic rate from S1 for G1 is 2*1250 = 2500 kbps > 2300 kbps.
[/]
A:admin@PE-1# show router 1 pim group 239.0.0.1 source 10.3.0.11
detail | match "Curr Fwding Rate"
Curr Fwding Rate : 1197.072 kbps PE-1 generates a corresponding S-PMSI A-D route for the (S1,G1) SMET from PE-2 and for the (*,G1) SMET from PE-3.
# On PE-1:
2 2025/05/06 12:28:10.898 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.2
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 108
Flag: 0x90 Type: 14 Len: 38 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.1
Type: EVPN-SPMSI-AD Len: 27 RD: 192.0.2.1:3, tag: 0,
Mcast-Src-Len: 32, Mcast-Src-Addr: 10.3.0.11,
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 239.0.0.1,
Orig Addr: 192.0.2.1/32
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: 24 Extended Community:
target:64500:3
target:64500:8
bgp-tunnel-encap:MPLS
Flag: 0xc0 Type: 22 Len: 22 PMSI:
Tunnel-type LDP P2MP LSP (2)
Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
MPLS Label 0
Root-Node 192.0.2.1, LSP-ID 0x2003
"
1 2025/05/06 12:28:10.898 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 104
Flag: 0x90 Type: 14 Len: 34 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 192.0.2.1
Type: EVPN-SPMSI-AD Len: 23 RD: 192.0.2.1:3, tag: 0,
Mcast-Src-Len: 32, Mcast-Src-Addr: 0.0.0.0,
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 239.0.0.1,
Orig Addr: 192.0.2.1/32
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: 24 Extended Community:
target:64500:3
target:64500:8
bgp-tunnel-encap:MPLS
Flag: 0xc0 Type: 22 Len: 22 PMSI:
Tunnel-type LDP P2MP LSP (2)
Flags: (0x0)[Type: None BM: 0 U: 0 Leaf: not required]
MPLS Label 0
Root-Node 192.0.2.1, LSP-ID 0x2002
"When PE-2 and PE-3 receive the EVPN-SPMSI-AD BGP update messages from PE-1, they import the corresponding routes:
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 0.0.0.0
0 0.0.0.0
192.0.2.1
u*>i 192.0.2.1:3 0.0.0.0
0 239.0.0.1
192.0.2.1
u*>i 192.0.2.1:3 10.3.0.11
0 239.0.0.1
192.0.2.1
-------------------------------------------------------------------------------
Routes : 3
===============================================================================Identical on PE-3.
PE-1 installs the following S-PMSI trees, for (*,G1), (S1,G1), and wildcard:
[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels detail
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8194 # 0x2002
Root Address : 192.0.2.1
S-PMSI If Index : 73729
Num. Leaf PEs : 1
Uptime : 0d 00:01:37
Group Address : 239.0.0.1
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
Group Receiver PE : 192.0.2.2, 192.0.2.3
-------------------------------------------------------------------------------
LSP ID : 8195 # 0x2003
Root Address : 192.0.2.1
S-PMSI If Index : 73730
Num. Leaf PEs : 1
Uptime : 0d 00:01:37
Group Address : 239.0.0.1
Source Address : 10.3.0.11
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
Group Receiver PE : 192.0.2.2, 192.0.2.3
-------------------------------------------------------------------------------
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:09:08
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================PE-2 can receive MC traffic for G1 only from the (S1,G1) S-PMSI tree or the wildcard S-PMSI tree.
[/]
A:admin@PE-2# show service id "BD-3" provider-tunnel spmsi-tunnels detail
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73731
Num. Leaf PEs : 1
Uptime : 0d 00:01:42
Group Address : 239.0.0.1
Source Address : 10.3.0.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73730
Uptime : 0d 00:09:13
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================PE-3 can receive MC traffic for G1 from the (S1,G1) S-PMSI tree, the (*,G1) S-PMSI tree, or the wildcard S-PMSI tree
[/]
A:admin@PE-3# show service id "SBD-8" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73730
Num. Leaf PEs : 1
Uptime : 0d 00:01:44
Group Address : 239.0.0.1
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73731
Num. Leaf PEs : 1
Uptime : 0d 00:01:44
Group Address : 239.0.0.1
Source Address : 10.3.0.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73729
Uptime : 0d 00:05:56
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================The tools dump service id <service id> provider-tunnels command shows the selective provider tunnels, as follows:
[/]
A:admin@PE-1# tools dump service id "BD-3" provider-tunnels type originating
---snip---
======================================================================================
VPLS 3 Selective Provider Tunnels Originating
======================================================================================
spmsi (LDP) Source-Addr Group-Addr Root-Addr LSP-ID Oper-State
----------------------------------------------------------------------------------------
* 239.0.0.1 192.0.2.1 8194 Up
10.3.0.11 239.0.0.1 192.0.2.1 8195 Up
* * 192.0.2.1 8193 Up
--------------------------------------------------------------------------------------[/]
A:admin@PE-3# tools dump service id "SBD-8" provider-tunnels type terminating
---snip---
======================================================================================
VPLS 8 Selective Provider Tunnels Terminating
======================================================================================
spmsi (LDP) Source-Addr Group-Addr Root-Addr LSP-ID Oper-State
----------------------------------------------------------------------------------------
* 239.0.0.1 192.0.2.1 8194 Up
10.3.0.11 239.0.0.1 192.0.2.1 8195 Up
* * 192.0.2.1 8193 Up
--------------------------------------------------------------------------------------Similar for tools dump service id 3 provider-tunnels type terminating on PE-2, without the (*,239.0.0.1) entry.
show service id <service id> sdp and show service id <service id> sdp detail for the source BD-3 on PE-1 shows the P2MP trees created for G1, including the wildcard and specific S-PMSI trees:
[/]
A:admin@PE-1# show service id "BD-3" sdp
===============================================================================
Services: Service Destination Points
===============================================================================
SdpId Type Far End addr Adm Opr I.Lbl E.Lbl
-------------------------------------------------------------------------------
32767:4294967292 VplsPmsi not applicable Up Up None 3
32767:4294967293 VplsPmsi not applicable Up Up None 3
32767:4294967294 VplsPmsi not applicable Up Up None 3
-------------------------------------------------------------------------------
Number of SDPs : 3
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-1# show service id "BD-3" sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
-------------------------------------------------------------------------------
Sdp Id 32767:4294967292 -(not applicable)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 32767:4294967292 Type : VplsPmsi
---snip---
PMSI Owner : none
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : 10.3.0.11
Group Address : 239.0.0.1
Admin State : Up Oper State : Up
---snip---
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 15019 E. Fwd. Octets : 14898848
---snip---
-------------------------------------------------------------------------------
Sdp Id 32767:4294967293 -(not applicable)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 32767:4294967293 Type : VplsPmsi
---snip---
PMSI Owner : none
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : 239.0.0.1
Admin State : Up Oper State : Up
---snip---
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
---snip---
-------------------------------------------------------------------------------
Sdp Id 32767:4294967294 -(not applicable)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 32767:4294967294 Type : VplsPmsi
---snip---
PMSI Owner : none
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : * (wildcard)
Admin State : Up Oper State : Up
---snip---
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 255920 E. Fwd. Octets : 253872640
---snip---
-------------------------------------------------------------------------------
Number of SDPs : 3
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-1# show service id "BD-3" sdp detail | match "SPMSI" post-lines 3
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : 10.3.0.11
Group Address : 239.0.0.1
Admin State : Up Oper State : Up
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : 239.0.0.1
Admin State : Up Oper State : Up
SPMSI Owner : bgpEvpnMpls
SPMSI
Source Address : *
Group Address : * (wildcard)
Admin State : Up Oper State : UpThe selection of the P2MP trees in the MFIB for IPv4 is as follows:
- An (S1,G1) MFIB uses:
- An (S1,G1) P2MP tree if it exists
- When an (S1,G1) P2MP tree does not exist, then it uses a (*,G1) P2MP tree if it exists
- When a (*,G1) P2MP tree does not exist, then it uses a (*,*) tree if it exists (wildcard-spmsi true)
- A (*,G1) MFIB uses:
- A (*,G1) P2MP tree if it exists
- When a (*,G1) P2MP tree does not exist, then it uses a (*,*) tree if it exists (wildcard-spmsi true)
- When an (S1,G1) MFIB or a (*,G1) MFIB use a P2MP tree that goes operationally down, the MFIB reverts to IR binds
Removing the wildcard S-PMSI tree
When wildcard-spmsi is not configured or when wildcard-spmsi false is configured on PE-1:
# On PE-1:
configure {
service {
vpls "BD-3" {
provider-tunnel {
selective {
owner bgp-evpn-mpls
data-delay-interval 3
maximum-p2mp-spmsi 10
mldp true
data-threshold {
group-prefix 239.0.0.0/16 {
threshold 2300
}
}
admin-state disable
commit
delete wildcard-spmsi
admin-state enable
committhe wildcard S-PMSI route is withdrawn:
# On PE-1:
6 2025/05/06 12:37:36.815 UTC MINOR: DEBUG #2001 Base Peer 1: 192.0.2.2
"Peer 1: 192.0.2.2: UPDATE
Peer 1: 192.0.2.2 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 28
Flag: 0x90 Type: 15 Len: 24 Multiprotocol Unreachable NLRI:
Address Family EVPN
Type: EVPN-SPMSI-AD Len: 19 RD: 192.0.2.1:3, tag: 0,
Mcast-Src-Len: 32, Mcast-Src-Addr: 0.0.0.0,
Mcast-Grp-Len: 32, Mcast-Grp-Addr: 0.0.0.0,
Orig Addr: 192.0.2.1/32
"[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:3 0.0.0.0
0 239.0.0.1
192.0.2.1
u*>i 192.0.2.1:3 10.3.0.11
0 239.0.0.1
192.0.2.1
-------------------------------------------------------------------------------
Routes : 2
===============================================================================Identical on PE-3.
PE-2 can receive MC traffic for G1 only from the (S1,G1) S-PMSI tree.
[/]
A:admin@PE-2# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73732
Num. Leaf PEs : 1
Uptime : 0d 00:02:03
Group Address : 239.0.0.1
Source Address : 10.3.0.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================PE-3 can receive MC traffic for G1 from the (S1,G1) S-PMSI tree or the (*,G1) S-PMSI tree.
[/]
A:admin@PE-3# show service id "SBD-8" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73733
Num. Leaf PEs : 1
Uptime : 0d 00:02:04
Group Address : 239.0.0.1
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73732
Num. Leaf PEs : 1
Uptime : 0d 00:02:04
Group Address : 239.0.0.1
Source Address : 10.3.0.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================wildcard-spmsi true is configured again as follows:
# On PE-1:
configure {
service {
vpls "BD-3" {
provider-tunnel {
selective {
owner bgp-evpn-mpls
data-delay-interval 3
maximum-p2mp-spmsi 10
mldp true
data-threshold {
group-prefix 239.0.0.0/16 {
threshold 2300
}
}
admin-state disable
commit
wildcard-spmsi true
admin-state enable
commitMC traffic of S1 decreases below threshold
The MC traffic rate from S1 decreases to 250 kbps. The measured cumulative MC traffic rate from S1 for G1 is 2*250 = 500 kbps < 2300 kbps.
[/]
A:admin@PE-1# show router 1 pim group 239.0.0.1 source 10.3.0.11
detail | match "Curr Fwding Rate"
Curr Fwding Rate : 234.720 kbps PE-1 generates an S-PMSI A-D unreachable for the (S1,G1) SMET from PE-2 and for the (*,G1) SMET from PE-3. PE-2 and PE-3 leave the specific S-PMSI trees and receive MC traffic from the wildcard S-PMSI tree again.
[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73729
Num. Leaf PEs : 1
Uptime : 0d 00:02:15
Group Address : 239.0.0.1
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Leaving
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73730
Num. Leaf PEs : 1
Uptime : 0d 00:02:15
Group Address : 239.0.0.1
Source Address : 10.3.0.11
Origin IP Address : 192.0.2.1
State : TX Leaving
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73728
Uptime : 0d 00:02:15
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================PE-1 eventually removes the specific S-PMSI trees.
[/]
A:admin@PE-1# show service id "BD-3" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8193
Root Address : 192.0.2.1
S-PMSI If Index : 73733
Uptime : 0d 00:05:30
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================Advertising S-PMSI A-D routes with VPLS evpn-proxy service
SMET routes convey the proxy state for IGMP-snooping or MLD-snooping and can be used in L2 EVPN services as a replacement for data path IGMP/MLD messages.
An EVPN network hosts PE-1, PE-2, and PE-3 that are connected via VPLS 2. MC sources SA1 (IP address 198.51.100.11) and SA2 (IP address 198.51.100.12) connected to PE-1 send MC traffic for MC group G2: 239.0.0.2 to MC receivers RA (IP address 198.51.100.21) connected to PE-1, RB (IP address 198.51.100.32) connected to PE-2, and RC (IP address 198.51.100.43) connected to PE-3. RB joins with an (SA1,G2) join. RC joins with a (*,G2) join.
Non-routed VPLS 2 is configured on PE-1, PE-2, and PE-3, as follows:
# On PE-1:
configure {
service {
vpls "VPLS 2" {
admin-state enable
service-id 2
customer "1"
bgp 1 { }
igmp-snooping {
admin-state enable
evpn-proxy {
admin-state enable
}
}
mld-snooping {
admin-state enable
}
bgp-evpn {
evi 2
mpls 1 {
admin-state enable
auto-bind-tunnel {
resolution any
}
}
}
sap 1/1/c4/1:2 { # only on PE-1
igmp-snooping {
mrouter-port true
}
}
sap 1/1/c5/1:2 {
igmp-snooping {
fast-leave true
send-queries true
}
}
provider-tunnel {
selective {
admin-state enable
data-delay-interval 5
owner bgp-evpn-mpls
wildcard-spmsi true # only on PE-1
mldp true
maximum-p2mp-spmsi 100
}
}The VPLS 2 configuration is identical on PE-2 and PE-3 and similar with the VPLS 2 configuration on PE-1, without the MC source and the wildcard-spmsi true configuration, and with the bgp-evpn routes sel-mcast advertise true configuration.
PE-1 advertises the S-PMSI A-D routes with the RT (target:64500:2) and the RD (192.0.2.1:2) of the VPLS 2 service.
# On PE-1:
configure {
service {
vpls "VPLS 2" {
provider-tunnel {
selective {
admin-state enable
data-delay-interval 5
owner bgp-evpn-mpls
wildcard-spmsi true
mldp true
maximum-p2mp-spmsi 100
data-threshold {
group-prefix 239.0.0.0/16 {
threshold 1000
}
}[/]
A:admin@PE-1# show service id "VPLS 2" provider-tunnel
===============================================================================
Service Provider Tunnel Information
===============================================================================
Type : inclusive Root and Leaf : disabled
---snip---
-------------------------------------------------------------------------------
Type : selective Wildcard SPMSI : enabled
Admin State : enabled Data Delay Intvl : 5 secs
PMSI Type : mLdp Max P2MP SPMSI : 100
PMSI Owner : bgpEvpnMpls
Group range : 239.0.0.0/16
S-PMSI Threshold : 1000 kbps
PE Threshold add : 65535 PE Threshold del : 65535
===============================================================================[/]
A:admin@PE-1# show service id "VPLS 2" provider-tunnel
===============================================================================
Service Provider Tunnel Information
===============================================================================
Type : inclusive Root and Leaf : disabled
---snip---
-------------------------------------------------------------------------------
Type : selective Wildcard SPMSI : enabled
Admin State : enabled Data Delay Intvl : 5 secs
PMSI Type : mLdp Max P2MP SPMSI : 100
PMSI Owner : bgpEvpnMpls
Group range : 239.0.0.0/16
S-PMSI Threshold : 1000 kbps
PE Threshold add : 1 PE Threshold del : 3
===============================================================================
Stats polling
Stats polling in non-routed VPLS networks with EVPN proxy is based on the L2 MFIB, which has separate counts for (Sn,G2) and (*,G2).
When the root PE receives an (SA1,G2) SMET and a (*,G2) SMET for the same MC group G2 using just 1 MC source SA1, the root PE sends an S-PMSI A-D route only for (SA1,G2) upon exceeding the S-PMSI threshold bandwidth. This is different for the same scenario in EVPN OISM networks.
When stats are polled for a specific (SA1,G2) S-PMSI and the MFIB data traffic rate drops below the S-PMSI threshold bandwidth, a timer of 30 seconds is started. When the timer expires, the MFIB data traffic rate is verified again. If it is still below the S-PMSI threshold bandwidth, the specific S-PMSI tree is removed.
One MC source in the MC group
MC traffic of SA1 is below threshold
SA1 on PE-1 sends MC traffic for G2 at 750 kbps. RB sends an (SA1,G2) IGMP/MLD v3 membership report for G2. R3 sends a (*,G2) IGMP/MLD v3 membership report for G2. The measured cumulative MC traffic rate from SA1 for G2 is 750 kbps < 1000 kbps.
PE-2 and PE-3 join the wildcard S-PMSI tree (after the data-delay-interval), based on the service RT matching the S-PMSI RT (target:64500:2).
PE-1 receives (SA1,G2) SMET from PE-2 and (*,G2) SMET from PE-3, but does not generate a corresponding S-PMSI A-D route for either of these SMET routes.
[/show router bgp routes evpn]
A:admin@PE-1# smet
===============================================================================
BGP Router ID:192.0.2.1 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:2 198.51.100.11
0 239.0.0.2
192.0.2.2
192.0.2.2
u*>i 192.0.2.3:2 0.0.0.0
0 239.0.0.2
192.0.2.3
192.0.2.3
-------------------------------------------------------------------------------
Routes : 2
===============================================================================PE-2 and PE-3 only install the wildcard S-PMSI route.
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:2 0.0.0.0
0 0.0.0.0
192.0.2.1
-------------------------------------------------------------------------------
Routes : 1
===============================================================================Identical on PE-3.
PE-2 and PE-3 receive MC traffic from the wildcard S-PMSI trees for VPLS 2:
[/]
A:admin@PE-2# show service id "VPLS 2" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73735
Uptime : 0d 00:05:30
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================Similar for PE-3.
The MFIB has the (SA1,G2), (*,G2), and the wildcard entries.
[/]
A:admin@PE-1# show service id "VPLS 2" mfib
===============================================================================
Multicast FIB, Service 2
===============================================================================
Source Address Group Address Port Id Svc Id Fwd
Blk
-------------------------------------------------------------------------------
* * sap:1/1/c4/1:2 Local Fwd
* 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
198.51.100.11 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
* * (mac) mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================When there is a (*,G2) MFIB entry and a more specific (SA1,G2) MFIB entry in the VPLS service of the root PE, the MC traffic of the more specific (SA1,G2) entry does not match the (*,G2) entry: MC traffic is only forwarded out of the ports that are associated with the (SA1,G2) entry.
[/]
A:admin@PE-1# show service id "VPLS 2" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 2
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* * 20050 19969800
0.000 kbps
* 239.0.0.2 0 0
0.000 kbps
198.51.100.11 239.0.0.2 36295 36149820
730.665 kbps
* * (mac) 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================MC traffic of SA1 increases above threshold
The MC traffic rate from SA1 increases to 1350 kbps. The measured cumulative MC traffic rate from SA1 for G2 is 1350 kbps > 1000 kbps.
PE-1 generates a corresponding S-PMSI A-D route for the (SA1,G2) SMET from PE-2 but does not generate a corresponding S-PMSI A-D route for the (*,G2) SMET from PE-3, because there is a separate counter for (SA1,G2) and for (*,G2), and the MC traffic rate for (SA1,G2) alone exceeds the S-PMSI threshold bandwidth.
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:2 0.0.0.0
0 0.0.0.0
192.0.2.1
u*>i 192.0.2.1:2 198.51.100.11
0 239.0.0.2
192.0.2.1
-------------------------------------------------------------------------------
Routes : 2
===============================================================================Identical on PE-3.
PE-2 and PE-3 both receive MC traffic from the specific (SA1,G2) S-PMSI tree for VPLS 2:
[/]
A:admin@PE-1# show service id "VPLS 2" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73737
Num. Leaf PEs : 1
Uptime : 0d 00:01:34
Group Address : 239.0.0.2
Source Address : 198.51.100.11
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73736
Uptime : 0d 00:11:48
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-2# show service id "VPLS 2" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73736
Num. Leaf PEs : 1
Uptime : 0d 00:01:41
Group Address : 239.0.0.2
Source Address : 198.51.100.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73735
Uptime : 0d 00:11:55
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================Similar for PE-3.
The MFIB has the (SA1,G2), the (*,G2), and the wildcard entries.
[/]
A:admin@PE-1# show service id "VPLS 2" mfib
===============================================================================
Multicast FIB, Service 2
===============================================================================
Source Address Group Address Port Id Svc Id Fwd
Blk
-------------------------------------------------------------------------------
* * sap:1/1/c4/1:2 Local Fwd
* 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
198.51.100.11 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
* * (mac) mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================[/]
A:admin@PE-1# show service id "VPLS 2" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 2
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* * 20050 19969800
0.000 kbps
* 239.0.0.2 0 0
0.000 kbps
198.51.100.11 239.0.0.2 85133 84792468
1320.297 kbps
* * (mac) 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================MC traffic of SA1 decreases below threshold
The MC traffic rate from SA1 decreases to 150 kbps. The measured cumulative MC traffic rate from SA1 for G2 is 150 kbps < 1000 kbps.
PE-1 generates an S-PMSI A-D unreachable for the (SA1,G2) SMET from PE-2. PE-2 and PE-3 leave the specific S-PMSI tree and receive MC traffic from the wildcard S-PMSI tree again.
Two MC sources in the same MC group
When there are 2 MC sources SA1 and SA2 for the same MC group G2, the (SA1,G2) MC traffic matches the (SA1,G2) MFIB entry that is added based on the (SA1,G2) SMET from PE-2, while the (SA2,G2) MC traffic matches the (*,G2) MFIB entry that is added based on the (*,G2) SMET from PE-3.
Combined MC traffic of SA1 and SA2 is below threshold
SA1 on PE-1 sends MC traffic for G2 at 150 kbps. SA2 on PE-1 sends MC traffic for G2 at 825 kbps. RB sends an (SA1,G2) IGMP/MLD v3 membership report for G2. R3 sends a (*,G2) IGMP/MLD v3 membership report for G2. The measured MC traffic rate from SA1 and SA2 for G2 is 150 + 825 = 975 kbps < 1000 kbps.
As in the case for one MC source SA1, PE-1 receives (SA1,G2) SMET from PE-2 and (*,G2) SMET from PE-3, but does not generate a corresponding S-PMSI A-D route for either of these SMET routes. PE-2 and PE-3 only install the wildcard S-PMSI route. PE-2 and PE-3 receive MC traffic from the wildcard S-PMSI trees for VPLS 2. The MFIB for VPLS 2 in PE-1 has the (SA1,G2), the (*,G2) and the wildcard entries. MC traffic of SA1 is forwarded out of the ports that are associated with the (SA1,G2) entry and MC traffic of SA2 is forwarded out of the ports that are associated with the (*,G2) entry.
[/]
A:admin@PE-1# show service id "VPLS 2" mfib
===============================================================================
Multicast FIB, Service 2
===============================================================================
Source Address Group Address Port Id Svc Id Fwd
Blk
-------------------------------------------------------------------------------
* * sap:1/1/c4/1:2 Local Fwd
* 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
198.51.100.11 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
* * (mac) mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================[/]
A:admin@PE-1# show service id "VPLS 2" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 2
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* * 20050 19969800
0.000 kbps
* 239.0.0.2 17296 17226816
810.345 kbps
198.51.100.11 239.0.0.2 102676 102265296
145.017 kbps
* * (mac) 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================Combined MC traffic of SA1 and SA2 increases above threshold
The MC traffic rate from SA1 remains at 150 kbps. The MC traffic rate from SA2 increases to 1125 kbps. The measured MC traffic rate from SA1 and SA2 for G2 is 150 + 1125 = 1275 kbps > 1000 kbps.
PE-1 generates a corresponding S-PMSI A-D route for the (SA1,G2) SMET from PE-2 and for the (*,G2) SMET from PE-3.
[/show router bgp routes evpn]
A:admin@PE-2# spmsi-ad
===============================================================================
BGP Router ID:192.0.2.2 AS:64500 Local AS:64500
===============================================================================
---snip---
===============================================================================
BGP EVPN SPMSI AD Routes
===============================================================================
Flag Route Dist. Src Address
Tag Grp Address
Orig Address
-------------------------------------------------------------------------------
u*>i 192.0.2.1:2 0.0.0.0
0 0.0.0.0
192.0.2.1
u*>i 192.0.2.1:2 0.0.0.0
0 239.0.0.2
192.0.2.1
u*>i 192.0.2.1:2 198.51.100.11
0 239.0.0.2
192.0.2.1
-------------------------------------------------------------------------------
Routes : 3
===============================================================================Identical on PE-3.
PE-2 can receive MC traffic for G2 only from the specific (SA1,G2) S-PMSI tree for VPLS 2. PE-3 can receive MC traffic for G2 from the specific (SA1,G2) S-PMSI tree and from the specific (*,G2) S-PMSI tree for VPLS 2.
[/]
A:admin@PE-1# show service id "VPLS 2" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73738
Num. Leaf PEs : 1
Uptime : 0d 00:05:21
Group Address : 239.0.0.2
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8196
Root Address : 192.0.2.1
S-PMSI If Index : 73739
Num. Leaf PEs : 1
Uptime : 0d 00:05:21
Group Address : 239.0.0.2
Source Address : 198.51.100.11
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73736
Uptime : 0d 00:30:01
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : TX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-2# show service id "VPLS 2" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8196
Root Address : 192.0.2.1
S-PMSI If Index : 73737
Num. Leaf PEs : 1
Uptime : 0d 00:05:27
Group Address : 239.0.0.2
Source Address : 198.51.100.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73735
Uptime : 0d 00:30:07
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================[/]
A:admin@PE-3# show service id "VPLS 2" provider-tunnel spmsi-tunnels
===============================================================================
LDP Spmsi Tunnels
===============================================================================
LSP ID : 8195
Root Address : 192.0.2.1
S-PMSI If Index : 73739
Num. Leaf PEs : 1
Uptime : 0d 00:05:29
Group Address : 239.0.0.2
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8196
Root Address : 192.0.2.1
S-PMSI If Index : 73740
Num. Leaf PEs : 1
Uptime : 0d 00:05:29
Group Address : 239.0.0.2
Source Address : 198.51.100.11
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
LSP ID : 8194
Root Address : 192.0.2.1
S-PMSI If Index : 73737
Uptime : 0d 00:26:26
Group Address : * (wildcard)
Source Address : *
Origin IP Address : 192.0.2.1
State : RX Joined
Remain Delay Intvl : 0
-------------------------------------------------------------------------------
===============================================================================The MFIB has the (SA1,G2), the (*,G2), and the wildcard entries. MC traffic of SA1 is forwarded out of the ports that are associated with the (SA1,G2) entry and MC traffic of SA2 is forwarded out of the ports that are associated with the (*,G2) entry.
[/]
A:admin@PE-1# show service id "VPLS 2" mfib
===============================================================================
Multicast FIB, Service 2
===============================================================================
Source Address Group Address Port Id Svc Id Fwd
Blk
-------------------------------------------------------------------------------
* * sap:1/1/c4/1:2 Local Fwd
* 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
198.51.100.11 239.0.0.2 sap:1/1/c4/1:2 Local Fwd
mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
* * (mac) mpls:192.0.2.2:524278 Local Fwd
mpls:192.0.2.3:524278 Local Fwd
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================[/]
A:admin@PE-1# show service id "VPLS 2" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 2
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* * 20050 19969800
0.000 kbps
* 239.0.0.2 71179 70894284
1102.771 kbps
198.51.100.11 239.0.0.2 110485 110043060
145.017 kbps
* * (mac) 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 4
===============================================================================PE-2 can receive MC traffic for G2 from only one MC source SA1 (from the (SA1,G2) S-PMSI tree), PE-3 can receive MC traffic for G2 from the two MC sources SA1 (from the (SA1,G2) S-PMSI tree) and SA2 (from the (*,G2) S-PMSI tree).
[/]
A:admin@PE-2# show service id "VPLS 2" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 2
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* 239.0.0.2 22138 21960896
0.000 kbps
198.51.100.11 239.0.0.2 110519 109634848
144.405 kbps
* * (mac) 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================[/]
A:admin@PE-3# show service id "VPLS 2" mfib statistics
===============================================================================
Multicast FIB Statistics, Service 2
===============================================================================
Source Address Group Address Matched Pkts Matched Octets
Forwarding Rate
-------------------------------------------------------------------------------
* 239.0.0.2 71663 71089696
1098.155 kbps
198.51.100.11 239.0.0.2 90106 89385152
144.382 kbps
* * (mac) 0 0
0.000 kbps
-------------------------------------------------------------------------------
Number of entries: 3
===============================================================================[/]
A:admin@PE-2# monitor service id "VPLS 2" sap 1/1/c5/1:2 interval 11 repeat 2
===============================================================================
Monitor statistics for Service 2 SAP 1/1/c5/1:2
===============================================================================
---snip---
-------------------------------------------------------------------------------
At time t = 22 sec (Mode: Delta)
-------------------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
Sap per Queue Stats
-------------------------------------------------------------------------------
Packets Octets
Ingress Queue 1 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Ingress Queue 11 (Multipoint) (Priority)
Off. Combined : 0 0
Off. Managed : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Egress Queue 1
For. In/InplusProf : 0 0
For. Out/ExcProf : 202 201068
Dro. In/InplusProf : 0 0
Dro. Out/ExcProf : 0 0
===============================================================================[/]
A:admin@PE-3# monitor service id "VPLS 2" sap 1/1/c5/1:2 interval 11 repeat 2
===============================================================================
Monitor statistics for Service 2 SAP 1/1/c5/1:2
===============================================================================
---snip---
-------------------------------------------------------------------------------
At time t = 22 sec (Mode: Delta)
-------------------------------------------------------------------------------
---snip---
-------------------------------------------------------------------------------
Sap per Queue Stats
-------------------------------------------------------------------------------
Packets Octets
Ingress Queue 1 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Ingress Queue 11 (Multipoint) (Priority)
Off. Combined : 0 0
Off. Managed : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0
Egress Queue 1
For. In/InplusProf : 0 0
For. Out/ExcProf : 1724 1723068
Dro. In/InplusProf : 0 0
Dro. Out/ExcProf : 0 0
===============================================================================Combined MC traffic of SA1 and SA2 decreases below threshold
The MC traffic rate from SA1 remains at 150 kbps. The MC traffic rate from SA2 decreases to 375 kbps. The measured cumulative MC traffic rate from SA1 and SA2 for G2 is 150 + 375 = 525 kbps < 1000 kbps.
PE-1 generates an S-PMSI A-D unreachable for the (SA1,G2) SMET from PE-2 and for the (*,G2) SMET from PE-3. PE-2 and PE-3 leave the specific S-PMSI trees and receive MC traffic from the wildcard S-PMSI tree again.
Conclusion
SR OS supports S-PMSI A-D routes in EVPN OISM networks and in VPLS networks with EVPN proxy.