Junos MulticastVPNs

Junos MPLS and VPNs
Chapter 13: Multicast VPNs
© 2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Worldwide Education Services
Chapter Objectives
 After successfully completing this chapter, you will be
able to:
• Describe the flow of control traffic and data traffic in a
next-generation multicast VPN
• Describe the configuration steps for establishing a
• Monitor and verify the operation of next-generation multicast
VPNs
© 2010 Juniper Networks, Inc. All rights reserved. Worldwide Education Services www.juniper.net | 13-2
Agenda: Multicast VPNs
Multicast VPN Overview
 Next-Generation MVPN Operation
 Configuration
 Monitoring
Model for Multiservice Network
Private IP ATM/FR Emulation
PSTN Bearer
and Signalling
Ethernet Services
Internet
L3VPN
L2VPN VPLS ?
(unicast only)
Signalling and Auto-Discovery (BGP)
Transport Infrastructure (MPLS LSPs)
Note: Legacy draft-Rosen L3VPN multicast scheme does not conform to this model.
Legacy Model for MVPN (draft-Rosen)
PIM adjacencies between PEs (per-VRF) to

exchange info about multicast receivers
L3VPN
(multicast)
Signalling and Auto-discovery (PIM)
Transport Infrastructure (multicast GRE tunnels)
Multicast trees across the core signalled by PIM running in

main routing instance
Legacy Multicast Topology (draft-Rosen)
Customer PIM domain Provider’s PIM domain Customer PIM domain
Source
CE
Provider Core PE-2
lo0: 192.168.24.1
B
P-RP OSPF Area 0
1.1.1.1
P1 P2
C-RP/DR
CE PE-1 AS 65412 Receiver
A 1 lo0: 192.168.16.1
1.1.1.1 224.7.7.7 M-cast Data 192.168.16.1 239.1.1.1 1.1.1.1 224.7.7.7 M-cast Data 1.1.1.1 224.7.7.7 M-cast Data
SA DA GRE-SA GRE-DA SA DA SA DA
 PE routers must participate in both customer’s and provider’s multicast

domain
 PIM/multicast traffic from customer instance of PIM encapsulated in
GRE using configured vpn-group-address on PE router (example
uses 239.1.1.1)
• Multicast data, hellos, join/prunes, Bootstrap, Auto-RP, etc.
• PE-1 and PE-2 join configured vpn-group-address within provider’s domain
using the provider RP
Motivations Behind NG-MVPN
 IETF motivations for a new MVPN scheme called
next-generation MVPN
• Increasing interest from customers of Layer 3 VPN services in
having multicast capability, in addition to unicast
• New mission-critical MVPN applications such as IPTV
• Point to multipoint MPLS LSPs provide multicast-like
forwarding
• Realization that existing Rosen scheme for MVPN has
fundamental architectural limitations
Model for Next-Generation MVPN
Private IP ATM/FR emulation
PSTN bearer +
signalling
Ethernet Services
Internet
L3VPN
IPTV
(unicast and L2VPN VPLS ?
multicast)
Signalling and Auto-discovery (BGP)
Transport Infrastructure (MPLS LSPs)
Traffic Engineering, bandwidth guarantees, fast-reroute…
Replacing PIM with BGP
 BGP for PE-PE signaling
• Seven MP-BGP NLRI for
MVPN signaling PE1
• MVPN membership
autodiscovery
• Autodiscovery for selective RR RR
provider tunnels
• Customer PIM join message PE5 PE2
conversion
• Active sources
• PE routers might need only PE4 PE3
a couple of BGP sessions to

route-reflectors
• Can be the same as Layer 3
VPN unicast scheme
Next-Generation MVPN Terms
 Terms
• PMSI : Type of tunnel to use to transport multicast data across
the provider core (also called provider tunnel)
• RSVP point to multipoint LSPs
• Provider instance PIM distribution trees (similar to draft-Rosen)
• MLDP
• I-PMSI
• Multidirectional: All PEs in a MVPN can transmit multicast packets to
all other PEs participating in MVPN
• Unidirectional: Enables only a particular PE to transmit multicast
packets to other PEs
• S-PMSI
• A particular PE can transmit multicast packets to a subset of PEs
 Multicast VPN Overview
Next-Generation MVPN Operation
 Configuration
 Monitoring
Next-Generation MVPN BGP Advertisements
 Next-generation MVPN routes use the MCAST-VPN
NLRI format
• AFI 1/SAFI 5
• Routes tagged with correct route target community are placed
into the bgp.mvpn.0 and routing-instance.mvpn.0
Type Length Route Type Specific
table (1 bytes) (1 bytes) (variable length)
 Next-generation MVPN draft specifies new attributes

• P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute
Tunnel
Flags Type MPLS Label Tunnel ID
(1 bytes) (1 bytes) (3 bytes) (variable length)
MPLS label that receiving PE should RSVP Session ID for RSVP point to
expect as an inner label for incoming multipoint LSPs
MVPN traffic (0 = No label)
Next-Generation MVPN BGP NLRI Types
(1 of 4)
 Type 1: Intra-AS Inclusive MVPN Membership Discovery
• Sent by all PE routers participating in MVPN
• In the case of I-PMSI using RSVP-TE, these routes determine
where to automatically build the point to multipoint LSPs
• Routes are tagged with PMSI Tunnel attribute
1:10.1.1.1:1:10.1.1.1
Type Sending Sending
PE’s RD PE’s lo0
 Type 2: Inter-AS Inclusive MVPN Membership Discovery

• Used for membership discovery between PE routers in different
ASs
• Not covered in this course 2:10.1.1.1:1:65412
Type Sending Sending
PE’s RD PE’s AS
(2 of 4)
 Type 3: Selective MVPN Autodiscovery Route
• Sent by the PE that initiates an S-PMSI
3:10.255.170.100:1:32:192.168.194.2:32:224.1.2.3:10.255.170.100
Sending C-S using S- C-G using Sending PE’s
Type C-S C-G
PE’s RD PMSI S-PMSI lo0
Mask Mask
 Type 4: Selective MVPN Autodiscovery Route for Leaf

• Sent by receiver PE upon receiving a Type 3 with the leaf
information bit set
4:3:10.255.170.100:1:32:192.168.194.2:32:224.1.2.3:10.255.170.100:10.255.170.98
Type Received Type Sending PE’s
3 Route lo0
(3 of 4)
 Type 5: Source Active Autodiscovery Route
• Sent by PE router that discovers an active multicast source
• Learned through PIM register messages (RP), MSDP source active
messages, or a locally connected source
5:10.255.170.100:1:32:192.168.194.2:32:224.1.2.3
Sending C-S C-G
Type C-S C-G
PE’s RD
Mask Mask
 Type 6: Shared Tree Join Route

• Sent by receiver PE that receives PIM join (C-*,C-G) on VRF
interface
6:10.255.170.100:1:65000:32:10.12.53.12:32:224.1.2.3
RD of upstream C-RP Address C-G
Type AS of C-RP C-G
PE (towards C- upstream Mask Mask
RP) PE
(4 of 4)
 Type 7: Source Tree Join Route
• Sent by receiver PE that receives PIM join (C-S,C-G) on VRF
interface
7:10.255.170.100:1:65000:32:192.168.194.2:32:224.1.2.3
RD of upstream C-S C-G
Type AS of C-S C-G
PE (towards C- upstream Mask Mask
RP) PE
Point-to-Multipoint LSP Concept
 RSVP point-to-multipoint LSPs can be used as the
transport mechanism for next-generation MVPN traffic
across the core
 Traffic can be protected using standard methods like fast reroute and link
protection
PE1
Can use MPLS FRR,
Traffic Engineering,
Core routers only need IGP plus Bandwidth Reservations
MPLS, no PIM needed!
P2
P1
PE5 PE2
PE4 PE3
Next-Generation MVPN Inclusive Trees
 Inclusive trees
• Each tree serves one MVPN
only PE1
• All the multicast traffic in

that MVPN arriving at an
ingress PE is mapped to that
same tree to get from the
ingress PE to all the other PE5 PE2
PEs in the same MVPN
• Analogous to default-MDT
PE4 PE3
in draft-Rosen
Next-Generation MVPN Selective Trees
 Selective trees
• Serves particular selected
multicast group(s) from a PE1
given MVPN
• Similar to data-MDT in Selective Tree
draft-Rosen
PE5 PE2
PE4 PE3
I-PMSI Signaling Example (1 of 4)
 Example with show the use of inclusive trees with RSVP
point to multipoint LSPs
• Prior to enabling an MVPN, the PE routers have an existing
L3VPN established using LDP to signal LSPs
• The provider core does not have PIM enabled
Customer PIM domain Customer PIM domain

Source
PE-2
CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
 With no source or receivers for multicast traffic, an
MVPN is enabled on the PE routers
• Each PE router:
• Advertises a Inclusive MVPN A-D route to each other tagged with
Route Target and PMSI Tunnel Attribute
• Automatically builds a point to multipoint LSP to other PEs with itself
as root and no PHP (virtual tunnel interface or vrf-table-label)
1:192.168.6.1:1:192.168.6.1
PMSI – RSVP Session ID, Label = 0
PE-2 CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
P1 P2
C-DR
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
 Source begins sending multicast traffic
• CE-A sends register messages to PE-1
• PE-1 is now aware of an active source
• PE-1 sends SA Autodiscovery Route to remote PEs
5:192.168.6.1:1:32:10.0.101.2:32:224.7.7.7
PE-2
CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
PIM Registers
 Using IGMP, receivers join source specific group
• Receiver CEs send PIM (S,G) join upstream to PE-2 and PE-3
• Receiver PEs convert PIM join to MVPN Source Tree Join
• Source PE convert MVPN Source Tree Join to PIM (S,G) Join
and sends it to the DR to complete the multicast tree
PIM (S,G) 7:192.168.6.1:1:65512:32:10.0.101.2:32:224.7.7.7 PIM (S,G)
Join Join
CE
Provider Core PE-2 B
OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR Receivers
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
I-PMSI Forwarding
 After multicast forwarding tree is built
• CE-A sends native multicast packets to PE-1
• PE-1 encapsulates packets in a single MPLS header
• Outbound MPLS label is derived from the point to multipoint LSP
• P2 sends copies of packets to both PE-2 and PE-3
• Receiver PE’s pop outer label and send traffic based on VRF
S-IP 224.7.7.7 M-cast Data Label S-IP 224.7.7.7 M-cast Data S-IP 224.7.7.7 M-cast Data
SA DA MPLS SA DA SA DA
PE-2
CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
S-IP=10.0.101.2
P1 P2
C-DR Receivers
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
S-PMSI Signaling Example (1 of 5)
 Example with show the use of selective trees with RSVP
point to multipoint LSPs
• Prior to enabling an MVPN, the PE routers have an existing
L3VPN established using LDP to signal LSPs
• The provider core does not have PIM enabled

Source
PE-2 CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
 With no source or receivers for multicast traffic, an

MVPN is enabled on the PE routers
• Each PE router:
• Advertises a Inclusive MVPN A-D route to each other tagged with
Route Target
• No point to multipoint LSPs are built between PEs at this point
Customer PIM domain 1:192.168.6.1:1:192.168.6.1 Customer PIM domain
CE
Provider Core PE-2 B
OSPF Area 0 lo0: 192.168.2.1
P1 P2
C-DR
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
 Source begins sending multicast traffic
• CE-A sends register messages to PE-1
• PE-1 is now aware of an active source
• PE-1 sends SA Autodiscovery Route to remote PEs
5:192.168.6.1:1:32:10.0.101.2:32:224.7.7.7
PE-2
CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
PIM Registers
 Using IGMP, receivers join source specific group
• Receiver CE-B sends PIM (S,G) join upstream to
• Receiver PE-2 converts PIM join to MVPN Source Tree Join
• No receiver attached to CE-C
7:192.168.6.1:1:65512:32:10.0.101.2:32:224.7.7.7 PIM (S,G)
Join
PE-2
CE
Provider Core B
OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR Receiver
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
 PE-1 completes the multicast forwarding tree
• PE-1 sends S-PMSI Autodiscovery route remote PEs
• Only PE-2 responds with a Leaf Autodiscovery route
• PE-1 builds point to multipoint LSP to responding leaf PEs and
sends PIM join towards the DR
1 3:192.168.6.1:1:0:0.0.0.0:32:224.7.7.7:192.168.6.1
PMSI – RSVP Session ID, Label = 0, Leaf Info Required
4 4:3:192.168.6.1:1:0:0.0.0.0:32:224.7.7.7:192.168.6.1:192.168.2.1 2
PIM (S,G) Customer PIM domain
JoinPIM domain
Customer
PE-2 CE
Provider Core B
3 OSPF Area 0 lo0: 192.168.2.1
10.0.101.2
P1 P2
C-DR Receiver
CE PE-1
AS 65512
A 1 lo0: 192.168.6.1
C-RP
PE-3 CE
lo0: 192.168.2.2 C
Hardware Requirements for
Next-Generation MVPNs
 Requires tunnel service PIC on certain routers
• Customer’s first hop DR
• Customer’s candidate RPs
• All PE routers participating in customer’s multicast network
• Except when using vrf-table-label
• Tunnel services simply needs to be enabled on the
MX Series DPC/MPCs
[edit]
user@pe1# show chassis
fpc 1 {
pic 0 {
tunnel-services {
bandwidth 1g;
}
}
}
Next-Generation MVPN Junos OS Support
 Junos OS supports:
• Provider Tunnel Types
• RSVP Inclusive Trees
• RSVP Selective Trees
• PIM–ASM Tunnels
• PIM-SSM Tunnels
• Data MDT Tunnels
• PIM features
• PIM Sparse Mode
• PIM Dense Mode
• Auto-RP
• Bootstrap Protocol
Configuration
 Monitoring
Next-Generation MVPN Configuration
(1 of 4)
 PE to PE MP-BGP session must be configured to allow
for MVPN signaling
[edit]
user@pe1# show protocols bgp
family inet {
unicast;
any;
}
family inet-vpn {
any;
}
family inet-mvpn {
signaling;
}
group my-int-group {
type internal;
local-address 192.168.6.1;
neighbor 192.168.2.2;
neighbor 192.168.2.1;
}
(2 of 4)
 Configure P2MP LSP template for provider tunnel
[edit]
user@pe1# show protocols mpls
label-switched-path mvpn-example {
 Configure RSVP-TE LSP totemplate;
be used as provider tunnel
no-cspf;
link-protection;
p2mp;
}
Inclusive Provider Tunnel Selective Provider Tunnel

[edit routing-instances mcast-pe-vrf] [edit routing-instances mcast-pe-vrf]
user@pe1# show user@pe1# show
… …
provider-tunnel { provider-tunnel {
rsvp-te { selective {
label-switched-path-template { group 224.7.7.0/24 {
mvpn-example; wildcard-source {
} rsvp-te {
} label-switched-pat…{
} default-template;
… …
vrf-table-label; vrf-table-label;
…
(3 of 4)
 Configure the VRF to participate in the C-PIM domain
as well as the MVPN
[edit]
user@pe1# show routing-instances mcast-pe-vrf
…
protocols {
…
pim {
rp {
local {
address 192.168.13.3;
}
}
interface all {
mode sparse;
}
}
mvpn {
mvpn-mode {
spt-only;
}
…
(4 of 4)
 Full VRF example configuration
[edit routing-instances mcast-pe-vrf] …
user@pe1# show pim {
instance-type vrf; rp {
interface ge-1/0/9.251; local {
interface lo0.13; address 192.168.13.3;
provider-tunnel { }
rsvp-te { }
label-switched-path-template { interface all {
mvpn-example; mode sparse;
} }
} }
} mvpn {
vrf-target target:65512:100; mvpn-mode {
vrf-table-label; spt-only;
protocols { }
bgp { }
group external { }
type external;
export exp-policy;
neighbor 10.0.50.2 {
peer-as 65501;
}
}
…
Next-Generation MVPN Configuration Options
 Provider tunnels
[edit routing-instances mcast-pe-vrf]
user@pe1# set provider-tunnel ?
Possible completions:
…
> mdt Data MDT tunnels for PIM MVPN
> pim-asm PIM-SM provider tunnel
> pim-ssm PIM-SSM provider tunnel
> rsvp-te RSVP-TE point-to-multipoint LSP for flooding
> selective Selective tunnels
 MVPN settings
[edit routing-instances mcast-pe-vrf]
user@pe1# set protocols mvpn ?
Possible completions:
…
> autodiscovery-only Use MVPN exclusively for PE router autodiscovery
> mvpn-mode MVPN mode of operation
receiver-site MVPN instance has sites only with multicast receivers
> route-target Configure route-targets for MVPN routes
sender-site MVPN instance has sites only with multicast sources
> traceoptions Trace options for BGP-MVPN
unicast-umh-election Upstream Multicast Hop election based on unicast route
preference
 Configuration
Monitoring
View VRF PIM Status
 Verify PIM status
user@pe1> show pim join instance mcast-pe-vrf extensive
Instance: PIM.mcast-pe-vrf Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.7.7.7
Source: 10.0.101.2
Flags: sparse
Upstream interface: ge-1/0/9.251
Upstream neighbor: 10.0.50.2
Upstream state: Local RP, Join to Source
Keepalive timeout:
Downstream neighbors:
Interface: Pseudo-MVPN
Instance: PIM.mcast-pe-vrf Family: INET6

R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Verify Multicast Packet Forwarding
 Verify multicast traffic
user@pe1> show multicast route extensive instance mcast-pe-vrf
Family: INET
Group: 224.7.7.7
Source: 10.0.101.2/32
Upstream interface: ge-1/0/9.251
Session description: Unknown
Statistics: 139 kBps, 263 pps, 532482 packets
Next-hop ID: 3638
Upstream protocol: MVPN
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 0
Family: INET6
MVPN RIB-IN
 View MVPN routes learned from remote PEs
• Routes that populate this table have been accepted by vrf-
import policy (based on vrf-target matching)
user@pe1> show route table bgp.mvpn.0
bgp.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
1:192.168.2.1:65535:192.168.2.1/240
*[BGP/170] 18:13:11, localpref 100, from 192.168.2.1
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
1:192.168.2.2:65535:192.168.2.2/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299808
7:192.168.6.1:5:65512:32:10.0.101.2:32:224.7.7.7/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
VRF Specific MVPN Routes
 View MVPN routes specific to a particular VRF
user@pe1> show route table mcast-pe-vrf.mvpn.0
mcast-pe-vrf.mvpn.0: 5 destinations, 6 routes (5 active, 1 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
1:192.168.2.1:65535:192.168.2.1/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
1:192.168.2.2:65535:192.168.2.2/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299808
1:192.168.6.1:5:192.168.6.1/240
*[MVPN/70] 00:41:29, metric2 1
Indirect
5:192.168.6.1:5:32:10.0.101.2:32:224.7.7.7/240
*[PIM/105] 18:23:21
Multicast (IPv4)
7:192.168.6.1:5:65512:32:10.0.101.2:32:224.7.7.7/240
*[PIM/105] 00:18:31
Multicast (IPv4)
[BGP/170] 00:18:31, localpref 100, from 192.168.2.1
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
Verify Provider Tunnel
 View status of point to multipoint LSP
user@pe1> show rsvp session
Ingress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
192.168.2.1 192.168.6.1 Up 0 1 SE - 300096 192.168.2.1:192.168.6.1:5:mvpn:mcast-pe-vrf
192.168.2.2 192.168.6.1 Up 0 1 SE - 300096 192.168.2.2:192.168.6.1:5:mvpn:mcast-pe-vrf
Total 2 displayed, Up 2, Down 0
 Verify multicast traffic with traverse point to multipoint

LSP
user@pe1> show route forwarding-table destination 224.7.7.7 extensive
Routing table: mcast-pe-vrf.inet [Index 5]
Internet:
…
Destination: 224.7.7.7.10.0.101.2/64
Route type: user
Route reference: 0 Route interface-index: 223
Flags: cached, check incoming interface , accounting, sent to PFE
Next-hop type: flood Index: 3638 Reference: 2
Nexthop: 172.22.250.2
Next-hop type: Push 300096 Index: 3625 Reference: 1
Next-hop interface: ge-1/0/4.250
…
Summary
 In this chapter, we:
• Described the flow of control traffic and data traffic in a
• Described the configuration steps for establishing a
• Monitored and verified the operation of next-generation
multicast VPNs
Review Questions
1. What is the primary difference between the

draft-Rosen approach to multicast VPNs and the
next-generation MVPN approach?
2. Name and briefly describe two of the seven MVPN
NLRI types.
3. In a next-generation multicast VPN network what
devices require a tunnel services interface?
Worldwide Education Services

Junos MulticastVPNs

Uploaded by

Copyright:

Available Formats

Junos MulticastVPNs

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Junos MulticastVPNs

Uploaded by

Copyright:

Available Formats

Junos MPLS and VPNs

Chapter 13: Multicast VPNs

Signalling and Auto-Discovery (BGP)

Transport Infrastructure (MPLS LSPs)

PIM adjacencies between PEs (per-VRF) to

Signalling and Auto-discovery (PIM)

Transport Infrastructure (multicast GRE tunnels)

Multicast trees across the core signalled by PIM running in

 PE routers must participate in both customer’s and provider’s multicast

Signalling and Auto-discovery (BGP)

Transport Infrastructure (MPLS LSPs)

Traffic Engineering, bandwidth guarantees, fast-reroute…

a couple of BGP sessions to

 Next-generation MVPN draft specifies new attributes

 Type 2: Inter-AS Inclusive MVPN Membership Discovery

 Type 4: Selective MVPN Autodiscovery Route for Leaf

 Type 6: Shared Tree Join Route

• All the multicast traffic in

Customer PIM domain Customer PIM domain

Customer PIM domain Customer PIM domain

Customer PIM domain Customer PIM domain

 With no source or receivers for multicast traffic, an

Customer PIM domain Customer PIM domain

Inclusive Provider Tunnel Selective Provider Tunnel

Instance: PIM.mcast-pe-vrf Family: INET6

bgp.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

mcast-pe-vrf.mvpn.0: 5 destinations, 6 routes (5 active, 1 holddown, 0 hidden)

 Verify multicast traffic with traverse point to multipoint

1. What is the primary difference between the

You might also like