NG-MVPN
Configuration Note
Last Updated: 2017-03-23
Version: 1.0
Introduction:
The two main multicast VPN (MVPN) service implementations are the draft-rosen-vpn-mcast [RFC 6037] and the Next-Generation Multicast VPN (NG-MVPN) [RFC 6513 and 6514]. The 7705 SAR supports NG-MVPN only which use BGP for customer-multicast (C-multicast) signaling. NG-MVPN aims to accomplish multicast routing over IP VPNs (VPRNs). The NG-MVPN can leverage existing transport technologies such as Multipoint LDP (mLDP), P2MP RSVP-TE LSPs and GRE.
Prerequisites:
This configuration note assumes that base configuration including cards, MDAs and ports have been implemented on the nodes.
Network setup requirements:
· 7705 SAR – Release 8.0R2 and later.
· 7750 SR – Release 14.0R4 and later.
Setup 1: Intra-AS NG-MVPN with I-PMSI
and S-PMSI
This setup will be having 1 MVPN service configured on Root-PE1 and Leaf-PE2. Root-PE1 has total five Sources available (one source per group). Leaf-PE2 has five Receivers, each expecting to join a unique Source + Group (S*, G*). Moreover, one I-PMSI tunnel per MVPN is generated and multiple S-PMSI tunnels can exist depending upon the traffic rate from the source.
Note: Sources and Receivers are simulated on the tester behind virtual routers, so PIM was required from PE towards Sources to complete the multicast routing topology.
Configuration Steps:
1. Configure all the interfaces, routing protocol (OSPF used here) and LDP as the transport tunnel protocol for all the connecting interfaces.
2. Configure BGP group for NG-MVPN in PE1, PE2 and RR. Include ‘mvpn-ipv4’ into family along with ‘vpn-ipv4’.
A:Root-PE1>config>router>bgp# info
----------------------------------------------
group "MVPN-BGP"
family vpn-ipv4 mvpn-ipv4
peer-as 65000
neighbor 10.10.10.34
exit
exit
no shutdown
----------------------------------------------
A:Leaf-PE2>config>router>bgp# info
----------------------------------------------
group "MVPN-BGP"
family vpn-ipv4 mvpn-ipv4
peer-as 65000
neighbor 10.10.10.34
exit
exit
no shutdown
----------------------------------------------
B:RR>config>router>bgp# info
----------------------------------------------
group "MVPN-RR"
family vpn-ipv4 mvpn-ipv4
peer-as 65000
neighbor 10.10.10.2
cluster 1.0.0.0
exit
neighbor 10.10.10.9
cluster 1.0.0.0
exit
exit
no shutdown
----------------------------------------------
3. Configure a vprn service on PE1 including all the source interface inside the service and enable pim on all interfaces.
A:Root-PE1>config>service>vprn# info
----------------------------------------------
route-distinguisher 10.10.10.9:65000
auto-bind mpls
vrf-target target:65000:23
interface "to-CE-Source" create
address 9.9.9.100/31
sap 1/1/3:100 create
exit
exit
pim
apply-to all
rp
exit
no shutdown
exit
ospf
export "vpn-to-ospf"
area 0.0.0.0 <<<< PE-CE unicast IGP to learn Mcast Source
interface "to-CE-Source"
interface-type point-to-point
no shutdown
exit
exit
exit
shutdown
----------------------------------------------
4. Configure a vprn service on PE2 and include all the receiver interfaces inside a service and enable pim on all interfaces.
A:Leaf-PE2>config>service# vprn 23
A:Leaf-PE2>config>service>vprn# info
----------------------------------------------
route-distinguisher 10.10.10.2:65000
auto-bind mpls
vrf-target target:65000:23
interface "to-CE-1" create
address 2.2.2.0/31
sap 1/1/4:1 create
exit
exit
...
interface "to-CE-5" create
address 2.2.2.8/31
sap 1/1/4:5 create
exit
exit
pim
apply-to all
rp
exit
no shutdown
exit
shutdown
----------------------------------------------
5. Configure mvpn under the service for both PE1 and PE2. Specify mdt-type source-only on PE1 which indicates that PE1 is always a root. The mdt-type as receiver-only on PE2 indicates that it will always be a leaf.
The data traffic from the source uses I-PMSI tunnel until the data-threshold (configured under Selective mLDP configuration) is exceeded then the new S-PMSI tunnel per Source will be generated. Refer below:
A:Root-PE1>config>service# vprn 23
A:Root-PE1>config>service>vprn# info
----------------------------------------------
mvpn
mdt-type sender-only <<< MVPN is always a Root
provider-tunnel
inclusive
mldp
no shutdown
exit
exit
selective <<< S-PMSI w/ mandatory threshold (Kbps) on Root-PE1
mldp
no shutdown
exit
data-threshold 225.0.0.0/7 100000
exit
exit
vrf-target target:65000:1
exit
exit
no shutdown
----------------------------------------------
A:Leaf-PE2>config>service# vprn 23
A:Leaf-PE2>config>service>vprn# info
----------------------------------------------
mvpn
mdt-type receiver-only <<<<< MVPN is always a Leaf
provider-tunnel
inclusive
mldp
no shutdown
exit
exit
selective
mldp
no shutdown
exit
exit
exit
vrf-target target:65000:1
exit
exit
no shutdown
----------------------------------------------
Verification
1. Verify bgp routers mvpn-ipv4 using <show router bgp routes mvpn-ipv4 [hunt|detail]>
*A:Leaf-PE2# show router bgp routes mvpn-ipv4
===============================================================================
BGP Router ID:10.10.10.2 AS:65000 Local AS:65000
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best, b - backup
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag RouteType OriginatorIP LocalPref MED
RD SourceAS Label
Nexthop SourceIP
As-Path GroupIP
-------------------------------------------------------------------------------
i Intra-Ad 10.10.10.2 100 0
10.10.10.2:65000 - -
10.10.10.2 -
No As-Path -
u*>i Intra-Ad 10.10.10.9 100 0
10.10.10.9:65000 - -
10.10.10.9 -
No As-Path -
u*>i Spmsi-Ad 10.10.10.9 100 0
10.10.10.9:65000 - -
10.10.10.9 1.1.1.2
No As-Path 225.0.2.0
-------------------------------------------------------------------------------
Routes : 3
===============================================================================
2. Check the status of all MVPNs.
Number of I-PMSI: 1 [As only 1 I-PMSI tunnel is generated per MVPN]
Number of S-PMSI: 1 [In this scenario the traffic rate from the source of only 1 multicast group is exceeding the configured data-threshold]
A:Root-PE1# show router mvpn-list
===============================================================================
MVPN List
===============================================================================
VprnID Sig A-D iPmsi/sPmsi GroupAddr/Lsp-Template (S,G)/(*,G)
Mdt-Type
-------------------------------------------------------------------------------
23 Bgp Default Mldp/Mldp N/A 5/0
SO
-------------------------------------------------------------------------------
Total PIM I-PMSI tunnels : 0
Total RSVP I-PMSI tunnels : 0
Total MLDP I-PMSI tunnels : 1
Total PIM TX S-PMSI tunnels : 0
Total RSVP TX S-PMSI tunnels : 0
Total MLDP TX S-PMSI tunnels : 1
Total PIM RX S-PMSI tunnels : 0
Total RSVP RX S-PMSI tunnels : 0
Total MLDP RX S-PMSI tunnels : 0
Total (S,G) : 5
Total (*,G) : 0
Total Mvpns : 1
Sig = Signal Pim-a = pim-asm Pim-s = pim-ssm A-D = Auto-Discovery
SR = Sender-Receiver SO = Sender-Only RO = Receiver-Only
===============================================================================
3. Verify the MVPN configuration
A:Root-PE1# show router 23 mvpn
===============================================================================
MVPN 23 configuration data
===============================================================================
signaling : Bgp auto-discovery : Default
UMH Selection : Highest-Ip
intersite-shared : Enabled
vrf-import : N/A
vrf-export : N/A
vrf-target : target:65000:1
C-Mcast Import RT : target:10.10.10.9:2
ipmsi : ldp
i-pmsi P2MP AdmSt : Up
i-pmsi Tunnel Name : mpls-if-73728
Mdt-type : sender-only
spmsi : ldp
s-pmsi P2MP AdmSt : Up
data-delay-interval: 3 seconds
data-threshold : 225.0.0.0/8 --> 100000 kbps
===============================================================================
4. Verify ldp bindings
*A:Leaf-PE2# show router ldp bindings
<Output omitted>
===============================================================================
LDP Generic P2MP Bindings
===============================================================================
P2MP-Id RootAddr
Interface Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
8193 10.10.10.9
73728 10.10.10.34 131064U -- -- --
8194 10.10.10.9
73730 10.10.10.34 131069U -- -- --
-------------------------------------------------------------------------------
No. of Generic P2MP Bindings: 2
===============================================================================
5. Verify the PIM tunnel interfaces for both PEs as below:
*A:Leaf-PE2# show router 23 pim tunnel-interface
===================================================================
PIM Interfaces ipv4
===================================================================
Interface Adm Opr DR Prty Hello Intvl
DR
-------------------------------------------------------------------
mpls-if-73728 Up Up N/A N/A
10.10.10.9
mpls-if-73730 Up Up N/A N/A
10.10.10.9
mpls-virt-if-690176 Up Up N/A N/A
10.10.10.2
-------------------------------------------------------------------
Interfaces : 3
===================================================================
6. Verify S-PMSI created for exceeded threshold.
A:Leaf-PE2# show router 23 pim s-pmsi
====================================================================
PIM LDP Spmsi tunnels
====================================================================
Lsp ID Root Addr SPMSI Index Num VPN State
SGs
--------------------------------------------------------------------
8194 10.10.10.9 73730 1 RX Joined
====================================================================
PIM LDP Spmsi Interfaces : 1
====================================================================
7. Verify PIM groups and interfaces
A:Root-PE1# show router 23 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)
-------------------------------------------------------------------------------
225.0.1.0 (S,G) to-CE-Source 1
1.1.1.1
225.0.2.0 (S,G) to-CE-Source 1
1.1.1.2
225.0.3.0 (S,G) to-CE-Source 1
1.1.1.3
225.0.4.0 (S,G) to-CE-Source 1
1.1.1.4
225.0.5.0 (S,G) to-CE-Source 1
1.1.1.5
-------------------------------------------------------------------------------
Groups : 5
===============================================================================
*A:Leaf-PE2# show router 23 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 225.0.1.0
Source Address : 1.1.1.1
RP Address : 0
Advt Router : 10.10.10.9
Flags : Type : (S,G)
MRIB Next Hop : 10.10.10.9
MRIB Src Flags : remote
<Output omitted>
Rpf Neighbor : 10.10.10.9
Incoming Intf : mpls-if-73728
Outgoing Intf List : to-CE-1 <<< Mcast traffic coming from I-PMSI or S-PMSI must
Egress the interface to-CE-x
Curr Fwding Rate : 98864.6 kbps
Forwarded Packets : 127586382 Discarded Packets : 0
Forwarded Octets : 51034552800 RPF Mismatches : 0
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 225.0.2.0
Source Address : 1.1.1.2
RP Address : 0
Advt Router : 10.10.10.9
Flags : Type : (S,G)
MRIB Next Hop : 10.10.10.9
MRIB Src Flags : remote
<Output omitted>
Rpf Neighbor : 10.10.10.9
Incoming Intf : mpls-if-73728
Incoming SPMSI Intf: mpls-if-73730 <<< S-PMSI is in use
Outgoing Intf List : to-CE-2
Curr Fwding Rate : 104245.1 kbps <<<<<<< Fw. Rate is over the data-threshold
Forwarded Packets : 50153102 Discarded Packets : 0
Forwarded Octets : 20061240800 RPF Mismatches : 0
<Output omitted>
Enable MoFRR
MoFRR can be enabled on all downstream routers to provide FRR protection for its upstream hop. This requires ECMP or Loop free alternate(LFA) routes to be available towards root node at each downstream router. MoFRR allows one backup interface per P2MP LSP. Backup LSPs have the same Root address + Opaque value as the primary P2MP LSP.
A:Leaf-PE2# configure router ldp
A:Leaf-PE2>config>router>ldp# info
----------------------------------------------
mcast-upstream-frr
interface-parameters
interface "to-31"
exit
interface "to-34"
exit
exit
targeted-session
exit
no shutdown
----------------------------------------------
Backup labels are available for the I-PMSI/S-PMSI tunnels on the downstream routers that have MoFRR enabled. Refer below, Leaf has backup labels for both I-PMSI and S-PMSI tunnels.
A:Leaf-PE2# show router ldp bindings
===============================================================================
LDP LSR ID: 10.10.10.2
===============================================================================
<Output omitted>
===============================================================================
LDP Generic P2MP Bindings
===============================================================================
P2MP-Id RootAddr
Interface Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
8193 10.10.10.9
73728 10.10.10.31 131069BU -- -- -- <<I-PMSI Backup
8193 10.10.10.9
73728 10.10.10.34 131063U -- -- --
8194 10.10.10.9
73738 10.10.10.31 131068BU -- -- -- <<S-PMSI Backup
8194 10.10.10.9
73738 10.10.10.34 131062U -- -- --
-------------------------------------------------------------------------------
No. of Generic P2MP Bindings: 4
===============================================================================
The upstream routers will see the valid labels to send traffic over for I-PMSI/S-PMSI tunnels and no Backup labels would be seen. Therefore, traffic is replicated among all LSP tunnels at upstream routers and dropped at Leaf until the primary fails.
A:Root-PE1# show router ldp bindings
===============================================================================
LDP LSR ID: 10.10.10.9
===============================================================================
<Output omitted>
===============================================================================
LDP Generic P2MP Bindings
===============================================================================
P2MP-Id RootAddr
Interface Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
8193 10.10.10.9
73728 10.10.10.31 -- 131071 1/1/2 10.9.31.31
8193 10.10.10.9
73728 10.10.10.34 -- 131070 1/1/4 10.9.34.34
8194 10.10.10.9
73738 10.10.10.31 -- 131066 1/1/2 10.9.31.31
8194 10.10.10.9
73738 10.10.10.34 -- 131067 1/1/4 10.9.34.34
-------------------------------------------------------------------------------
No. of Generic P2MP Bindings: 4
===============================================================================
Setup 2: Inter-AS NG-MVPN BGP 3107 Option-C
Figure 2: 1MVPN, 3 Groups with 1 Source and 1 Receiver each
7705 SAR supports Inter-AS solutions option A and C with BGP 3107. The 7705 SAR is only able to become a ROOT PE in a BGP-3107 Option B or Option C solution as this does not require the acceptance nor generation of recursive FEC messages.
The setup includes RR between PE1 and ASBR1 as 7705 SAR does not support removing the “no-export” community directly from vrf-export. Hence MVPN eBGP session using labeled routes will be between RR and PE2.
Configuration
Configure all the interfaces, routing protocol in each AS (OSPF used here), LDP for all the connecting interfaces.
BGP Configuration
1. At Root, add an export policy to remove no-export community.
The no-export community is removed because Intra-AD route from PE1 has to be distributed via MP-eBGP to PE2.
*A:SAR-Root-PE1>config>router>policy-options# info
----------------------------------------------
community "no-export" members "no-export"
policy-statement "remove"
entry 1
from
family mvpn-ipv4
exit
action accept
community remove "no-export"
exit
exit
exit
----------------------------------------------
A:SAR-Root-PE1>config>router>bgp# info
----------------------------------------------
vpn-apply-import
vpn-apply-export
connect-retry 5
keepalive 5
hold-time 15
min-route-advertisement 2
group "iBGP-RR" <<< iBGP peering with RR
family ipv4 vpn-ipv4 mvpn-ipv4
export "remove"
peer-as 65000
neighbor 10.10.10.253
advertise-label ipv4
exit
exit
no shutdown
----------------------------------------------
2. Configuration at RR
A:SR-RR>config>router>bgp# info
----------------------------------------------
min-route-advertisement 2
cluster 3.3.3.3
group "iBGP-Root-PE1" <<< iBGP peering with Root PE1
peer-as 65000
neighbor 10.10.10.9
family vpn-ipv4 mvpn-ipv4 label-ipv4
exit
exit
group "iBGP-ASBR1" <<< iBGP peering with ASBR1
peer-as 65000
neighbor 10.10.10.10
family vpn-ipv4 mvpn-ipv4 label-ipv4
exit
exit
group "Remote-PE-VPN" <<< MP-eBGP peering with Leaf PE2
neighbor 10.10.10.40
family ipv4 vpn-ipv4 mvpn-ipv4
multihop 5
peer-as 65100
exit
exit
no shutdown
----------------------------------------------
3. Configuration at ASBR1. The Root-PE1 System address (10.10.10.9/32) is exported here so that Leaf PE2 knows the path to the ‘True Root’ address.
B:SR-ASBR1>config>router>policy-options# info
----------------------------------------------
prefix-list "/32-address"
prefix 10.10.10.9/32 exact <<< Root PE1 System Address
prefix 10.10.10.10/32 exact <<< ASBR1 System Address
prefix 10.10.10.253/32 exact <<< RR System Address
exit
policy-statement "/32-add-to-bgp"
entry 10
from
prefix-list "/32-address"
exit
to
protocol bgp-label
exit
action accept
exit
exit
exit
----------------------------------------------
B:SR-ASBR1>config>router>bgp# info
----------------------------------------------
connect-retry 5
keepalive 5
hold-time 15
min-route-advertisement 2
group "eBGP-ASBR2" <<< eBGP peering with ASBR2
export "/32-add-to-bgp"
peer-as 65100
neighbor 10.10.12.20
family vpn-ipv4 mvpn-ipv4 label-ipv4
exit
exit
group "iBGP-RR" <<< iBGP peering with RR
peer-as 65000
neighbor 10.10.10.253
family vpn-ipv4 mvpn-ipv4 label-ipv4
exit
exit
no shutdown
----------------------------------------------
4. Configuration at ASBR2
A:SR-ASBR2>config>router>policy-options# info
----------------------------------------------
prefix-list "/32-address"
prefix 10.10.10.20/32 exact <<< ASBR2 System Address
prefix 10.10.10.40/32 exact <<< Leaf PE2 System Address
exit
policy-statement "test"
entry 10
exit
exit
policy-statement "/32-add-to-bgp"
entry 10
from
prefix-list "/32-address"
exit
to
protocol bgp-label
exit
action accept
exit
exit
exit
----------------------------------------------
A:SR-ASBR2>config>router>bgp# info
----------------------------------------------
connect-retry 5
keepalive 5
hold-time 15
min-route-advertisement 2
group "eBGP-ASBR1" <<< eBGP peering with ASBR1
export "/32-add-to-bgp"
peer-as 65000
neighbor 10.10.12.10
family vpn-ipv4 mvpn-ipv4 label-ipv4
exit
exit
group "iBGP-PE2" <<< iBGP peering with Leaf PE2
family vpn-ipv4 mvpn-ipv4 label-ipv4
peer-as 65100
neighbor 10.10.10.40
family vpn-ipv4 mvpn-ipv4 label-ipv4
exit
exit
no shutdown
----------------------------------------------
5. Configuration at Leaf (PE2)
B:SR-Leaf-PE2>config>router>bgp# info
----------------------------------------------
connect-retry 5
keepalive 5
hold-time 15
min-route-advertisement 2
group "eBGP-RR" <<< MP-eBGP peering with RR
peer-as 65000
neighbor 10.10.10.253
family ipv4 vpn-ipv4 mvpn-ipv4
multihop 5
peer-as 65000
exit
exit
group "iBGP-ASBR2" <<< iBGP peering with ASBR2
family vpn-ipv4 mvpn-ipv4 label-ipv4
peer-as 65100
neighbor 10.10.10.20
exit
exit
no shutdown
----------------------------------------------
6. LDP only advertise labels for /32 addresses. Hence between the ASBRs, static routes are needed to be present in the FIB for LDP to resolve the FECs and advertise labels for the ASBR interface addresses. [Note: BGP routes use interface address as next hop.]
B:SR-ASBR1>config>router# info
<output omitted>
#--------------------------------------------------
echo "Static Route Configuration"
#--------------------------------------------------
static-route-entry 10.10.10.20/32 <<< System Address of ASBR2
next-hop 10.10.12.20
no shutdown
exit
exit
static-route-entry 10.10.12.20/32 <<< Interface Address on ASBR2 towards ASBR1
next-hop 10.10.12.20
no shutdown
exit
exit
#--------------------------------------------------
MVPN Configuration
1. MVPN configuration at Root PE1
A:SAR-Root-PE1# configure service vprn 33
A:SAR-Root-PE1>config>service>vprn# info
----------------------------------------------
autonomous-system 65000
route-distinguisher 10.10.10.9:33
auto-bind ldp
vrf-target target:65000:33
interface "to-CE-Source-X" create
address 8.8.8.100/31
sap 1/1/7:33 create
exit
exit
igmp
no shutdown
exit
pim
interface "to-CE-Source-X"
exit
apply-to all
rp
exit
no shutdown
exit
mvpn
provider-tunnel
inclusive
mldp
no shutdown
exit
exit
selective
mldp
no shutdown
exit
data-threshold 225.0.0.0/8 10000
exit
exit
vrf-target target:65000:33 <<<< Can be same or different as unicast
exit
exit
ospf
export "vpn-to-ospf"
area 0.0.0.0
interface "to-CE-Source-X"
interface-type point-to-point
no shutdown
exit
exit
exit
no shutdown
----------------------------------------------
2. MVPN configuration at Leaf PE2. Note that it contains vrf-export policy to remove the no-export community from the labeled route.
B:SR-Leaf-PE2# configure service vprn 33
B:SR-Leaf-PE2>config>service>vprn# info
----------------------------------------------
autonomous-system 65100
route-distinguisher 10.10.10.40:33
auto-bind-tunnel
resolution-filter
ldp
exit
resolution filter
exit
vrf-target target:65000:33
interface "to-CE1" create
address 3.3.3.0/31
sap 1/1/12:1 create
exit
exit
interface "to-CE2" create
address 3.3.3.2/31
sap 1/1/12:2 create
exit
exit
interface "to-CE3" create
address 3.3.3.4/31
sap 1/1/12:4 create
exit
exit
igmp
no shutdown
exit
pim
apply-to all
rp
static
exit
bsr-candidate
shutdown
exit
rp-candidate
shutdown
exit
exit
no shutdown
exit
mvpn
auto-discovery default
c-mcast-signaling bgp
provider-tunnel
inclusive
mldp
no shutdown
exit
exit
selective
mldp
no shutdown
exit
data-threshold 225.0.0.0/8 25000
exit
exit
vrf-import "mvpnimport70"
vrf-export "mvpnexport70" <<< policy to remove no-export community
exit
no shutdown
----------------------------------------------
B:SR-Leaf-PE2>config# router policy-options
B:SR-Leaf-PE2>config>router>policy-options# info
----------------------------------------------
community "mvpn33" members "target:65000:33"
community "no-export" members "no-export"
policy-statement "mvpnexport70"
entry 1
action accept
community add "mvpn33"
community remove "no-export"
exit
exit
exit
policy-statement "mvpnimport70"
entry 1
from
community "mvpn33"
exit
action accept
exit
exit
exit
----------------------------------------------
Verification
1. Verify bgp routers mvpn-ipv4 using <show router bgp routes mvpn-ipv4 [hunt|detail]>
Note: PE1 contains two Intra-AD routes, one originated by itself and second one received from the leaf PE2.
10.10.10.9 à System Address of Root PE1
10.10.10.40 à System Address of Leaf PE2
10.10.10.253 à System Address of RR
A:SAR-Root-PE1# show router bgp routes mvpn-ipv4
===============================================================================
BGP Router ID:10.10.10.9 AS:65000 Local AS:65000
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best, b - backup
===============================================================================
BGP MVPN-IPv4 Routes
===============================================================================
Flag RouteType OriginatorIP LocalPref MED
RD SourceAS Label
Nexthop SourceIP
As-Path GroupIP
-------------------------------------------------------------------------------
i Intra-Ad 10.10.10.9 100 0
10.10.10.9:33 - -
10.10.10.9 -
No As-Path -
i Spmsi-Ad 10.10.10.9 100 0
10.10.10.9:33 - -
10.10.10.9 6.0.0.8
No As-Path 225.0.8.0
i Spmsi-Ad 10.10.10.9 100 0
10.10.10.9:33 - -
10.10.10.9 6.0.0.9
No As-Path 225.0.9.0
u*>i Source-Join - 100 None
10.10.10.9:33 65000 -
10.10.10.253 6.0.0.8
65100 225.0.8.0
u*>i Source-Join - 100 None
10.10.10.9:33 65000 -
10.10.10.253 6.0.0.9
65100 225.0.9.0
u*>i Source-Join - 100 None
10.10.10.9:33 65000 -
10.10.10.253 6.0.0.10
65100 225.0.10.0
u*>i Intra-Ad 10.10.10.40 100 None
10.10.10.40:33 - -
10.10.10.253 -
65100 -
-------------------------------------------------------------------------------
Routes : 7
===============================================================================
2. Verify MVPN configuration
A:SAR-Root-PE1# show router 33 mvpn
===============================================================================
MVPN 33 configuration data
===============================================================================
signaling : Bgp auto-discovery : Default
UMH Selection : Highest-Ip
intersite-shared : Enabled
vrf-import : N/A
vrf-export : N/A
vrf-target : target:65000:33
C-Mcast Import RT : target:10.10.10.9:3
ipmsi : ldp
i-pmsi P2MP AdmSt : Up
i-pmsi Tunnel Name : mpls-if-73753
Mdt-type : sender-receiver
spmsi : ldp
s-pmsi P2MP AdmSt : Up
data-delay-interval: 3 seconds
data-threshold : 225.0.0.0/8 --> 10000 kbps
===============================================================================
3. Verify PIM tunnel interfaces. Note that PE1 can only be source (Root) since it does not support Recursive FECs, so Rx I-PMSI will be down.
A:SAR-Root-PE1# show router 33 pim tunnel-interface
===================================================================
PIM Interfaces ipv4
===================================================================
Interface Adm Opr DR Prty Hello Intvl
DR
-------------------------------------------------------------------
mpls-if-73753 Up Up N/A N/A
10.10.10.9
mpls-if-73775 Up Down N/A N/A
N/A
mpls-if-73781 Up Up N/A N/A
10.10.10.9
mpls-if-73782 Up Up N/A N/A
10.10.10.9
-------------------------------------------------------------------
Interfaces : 4
===================================================================
Similarly, PE2 is only a leaf since Root PE1 did not establish the Rx I-PMSI, so Tx I-PMSI on Leaf PE2 will be operationally down as shown below.
B:SR-Leaf-PE2>config>service>vprn# show router 33 pim tunnel-interface
===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface Originator Address Adm Opr Transport Type
-------------------------------------------------------------------------------
mpls-if-73731 10.10.10.40 Up Down Tx-IPMSI
mpls-if-73753 10.10.10.9 Up Up Rx-IPMSI
mpls-if-73754 10.10.10.9 Up Up Rx-SPMSI
mpls-if-73755 10.10.10.9 Up Up Rx-SPMSI
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
4. Note: If the mdt-type on root is sender-only and on leaf receiver-only then the Tx-IPMSI on leaf and Rx-IPMSI on root will be virtual interfaces.
[Note: Virtual interfaces (Virt-if) are dummy interfaces created due to the internal implementation on TiMOS.]
*B:SR-Leaf-PE2>config>service>vprn# show router 33 pim tunnel-interface
s
===============================================================================
PIM Interfaces ipv4
===============================================================================
Interface Originator Address Adm Opr Transport Type
-------------------------------------------------------------------------------
mpls-if-73759 10.10.10.9 Up Up Rx-IPMSI
mpls-if-73760 10.10.10.9 Up Up Rx-SPMSI
mpls-if-73761 10.10.10.9 Up Up Rx-SPMSI
mpls-virt-if-1005859 10.10.10.40 Up Up Tx-IPMSI
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
5. Verify LDP bindings.
*B:SR-Leaf-PE2# show router ldp bindings
===============================================================================
LDP Bindings (IPv4 LSR ID 10.10.10.40)
(IPv6 LSR ID ::)
===============================================================================
<Output omitted>
===============================================================================
LDP IPv4 Prefix Bindings
===============================================================================
Prefix IngLbl EgrLbl
Peer EgrIntf/LspId
EgrNextHop
-------------------------------------------------------------------------------
10.10.10.10/32 -- 131063
10.10.10.20:0 --
--
10.10.10.20/32 -- 131071
10.10.10.20:0 1/1/1
10.20.40.20
10.10.10.40/32 131071U --
10.10.10.20:0 --
--
-------------------------------------------------------------------------------
No. of IPv4 Prefix Bindings: 3
===============================================================================
<output omitted>
===============================================================================
LDP GRT Recursive with Generic IPv4 P2MP Bindings
===============================================================================
P2MP-Id
RootAddr Interface IngLbl EgrLbl
InnerRootAddr
EgrNH EgrIf/LspId
Peer
-------------------------------------------------------------------------------
8193
10.10.10.20 73759 131067U --
10.10.10.9
-- --
10.10.10.20:0
8194
10.10.10.20 73760 131066U --
10.10.10.9
-- --
10.10.10.20:0
8195
10.10.10.20 73761 131065U --
10.10.10.9
-- --
10.10.10.20:0
-------------------------------------------------------------------------------
No. of GRT Recursive with Generic IPv4 P2MP Bindings: 3
===============================================================================
A:SR-ASBR2>config>router>bgp# show router ldp bindings
===============================================================================
LDP Bindings (IPv4 LSR ID 10.10.10.20)
(IPv6 LSR ID ::)
===============================================================================
<output omitted>
===============================================================================
LDP GRT Recursive with Generic IPv4 P2MP Bindings
===============================================================================
P2MP-Id
RootAddr Interface IngLbl EgrLbl
InnerRootAddr
EgrNH EgrIf/LspId
Peer
-------------------------------------------------------------------------------
8193
10.10.10.20 (LF) Unknw -- 131067
10.10.10.9
10.20.40.40 3/1/13
10.10.10.40:0
8194
10.10.10.20 (LF) Unknw -- 131066
10.10.10.9
10.20.40.40 3/1/13
10.10.10.40:0
8195
10.10.10.20 (LF) Unknw -- 131065
10.10.10.9
10.20.40.40 3/1/13
10.10.10.40:0
8193
10.10.12.10 (UF) Unknw 131066U --
10.10.10.9
-- --
10.10.12.10:0
8194
10.10.12.10 (UF) Unknw 131059U --
10.10.10.9
-- --
10.10.12.10:0
8195
10.10.12.10 (UF) Unknw 131058U --
10.10.10.9
-- --
10.10.12.10:0
-------------------------------------------------------------------------------
No. of GRT Recursive with Generic IPv4 P2MP Bindings: 6
===============================================================================
*B:SR-ASBR1# show
router ldp bindings
===============================================================================
LDP Bindings (IPv4 LSR ID 10.10.10.10)
(IPv6 LSR ID ::)
===============================================================================
<output omitted>
===============================================================================
LDP Generic IPv4 P2MP Bindings
===============================================================================
P2MP-Id
RootAddr Interface IngLbl EgrLbl
EgrNH EgrIf/LspId
Peer
-------------------------------------------------------------------------------
8193
10.10.10.9 (UF) Unknw 131068U --
-- --
10.10.10.253:0
8194
10.10.10.9 (UF) Unknw 131055U --
-- --
10.10.10.253:0
8195
10.10.10.9 (UF) Unknw 131054U --
-- --
10.10.10.253:0
-------------------------------------------------------------------------------
No. of Generic IPv4 P2MP Bindings: 3
===============================================================================
<output omitted>
===============================================================================
LDP GRT Recursive with Generic IPv4 P2MP Bindings
===============================================================================
P2MP-Id
RootAddr Interface IngLbl EgrLbl
InnerRootAddr
EgrNH EgrIf/LspId
Peer
-------------------------------------------------------------------------------
8193
10.10.12.10 (LF) Unknw -- 131066
10.10.10.9
10.10.12.20 2/1/9
10.10.12.20:0
8194
10.10.12.10 (LF) Unknw -- 131059
10.10.10.9
10.10.12.20 2/1/9
10.10.12.20:0
8195
10.10.12.10 (LF) Unknw -- 131058
10.10.10.9
10.10.12.20 2/1/9
10.10.12.20:0
-------------------------------------------------------------------------------
No. of GRT Recursive with Generic IPv4 P2MP Bindings: 3
===============================================================================
6. Verify PIM groups
*A:SAR-Root-PE1# show router 33 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)
-------------------------------------------------------------------------------
225.0.8.0 (S,G) to-CE-Source-X 1
6.0.0.8
225.0.9.0 (S,G) to-CE-Source-X 1
6.0.0.9
225.0.10.0 (S,G) to-CE-Source-X 1
6.0.0.10
-------------------------------------------------------------------------------
Groups : 3
===============================================================================
*B:SR-Leaf-PE2# show router 33 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)
-------------------------------------------------------------------------------
225.0.8.0 (S,G) mpls-if-73759 1
6.0.0.8
225.0.9.0 (S,G) mpls-if-73759 1
6.0.0.9
225.0.10.0 (S,G) mpls-if-73759 1
6.0.0.10
-------------------------------------------------------------------------------
Groups : 3
===============================================================================
*B:SR-Leaf-PE2# show router 33 pim group detail
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 225.0.8.0
Source Address : 6.0.0.8
RP Address : 0
Advt Router : 10.10.10.9
Flags : Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.10.10.9
MRIB Src Flags : remote
Keepalive Timer : Not Running
Up Time : 0d 00:26:28 Resolved By : rtable-u
Up JP State : Joined Up JP Expiry : 0d 00:00:56
Up JP Rpt : Not Joined StarG Up JP Rpt Override : 0d 00:00:00
Register State : No Info
Reg From Anycast RP: No
Rpf Neighbor : 10.10.10.9
Incoming Intf : mpls-if-73759
Incoming SPMSI Intf: mpls-if-73760 <<< S-PMSI in use for data traffic
Outgoing Intf List : to-CE1
Curr Fwding Rate : 26999.8 kbps
Forwarded Packets : 13948626 Discarded Packets : 0
Forwarded Octets : 5272580628 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
<output omitted>
===============================================================================
PIM Source Group ipv4
===============================================================================
Group Address : 225.0.10.0
Source Address : 6.0.0.10
RP Address : 0
Advt Router : 10.10.10.9
Flags : Type : (S,G)
Mode : sparse
MRIB Next Hop : 10.10.10.9
MRIB Src Flags : remote
Keepalive Timer : Not Running
Up Time : 0d 00:26:31 Resolved By : rtable-u
Up JP State : Joined Up JP Expiry : 0d 00:00:53
Up JP Rpt : Not Joined StarG Up JP Rpt Override : 0d 00:00:00
Register State : No Info
Reg From Anycast RP: No
Rpf Neighbor : 10.10.10.9
Incoming Intf : mpls-if-73759 <<< I-PMSI in use for data traffic
Outgoing Intf List : to-CE3
Curr Fwding Rate : 9000.9 kbps
Forwarded Packets : 4664413 Discarded Packets : 0
Forwarded Octets : 1763148114 RPF Mismatches : 0
Spt threshold : 0 kbps ECMP opt threshold : 7
Admin bandwidth : 1 kbps
-------------------------------------------------------------------------------
Groups : 3
===============================================================================