Related Documentation
- M, MX, T Series
- Multicast over Layer 3 VPNs Overview
- Configuring BGP, MPLS, RSVP, and an IGP on the PE and Core Routers for Draft Rosen VPNs
- Configuring BGP, MPLS, RSVP, and an IGP on the PE and Core Routers for MBGP MVPNs
- Configuring Interfaces for Layer 3 VPNs
- Configuring Intra-AS Inclusive Point-to-Multipoint Traffic Engineering LSPs
- Configuring Intra-AS Selective Provider Tunnels
- Configuring MBGP MVPNs to Support IPv6 Multicast Traffic
- Configuring PIM and the VPN Group Address in a Routing Instance
- Configuring Provider Tunnels
- Configuring the Master PIM Instance on the PE Router for BGP-Based Multicast VPNs
- Configuring the Master PIM Instance on the PE Router in the Service Provider Network
- Creating a Routing Instance for a Multiprotocol BGP-Based Multicast VPN
- Configuring the Router’s IPv4 Bootstrap Router Priority
- Creating a Unique Logical Loopback Interface for the Routing Instance for Draft Rosen VPNs
- Creating a Unique Logical Loopback Interface for the Routing Instance for MBGP MVPNs
- Dual PIM Draft-Rosen Multicast VPN Operation
- Enabling Multicast VPN in BGP
- Option: Configuring MSDP Within a Layer 3 VPN
- Option: Configuring Multicast Distribution Trees for Data
- Option: Configuring PIM Sparse Mode Graceful Restart for a Layer 3 VPN
- Option: Configuring Sender and Receiver Sites
- Option: Specifying Route Targets
- Understanding Multiprotocol BGP-Based Multicast VPNs: Next-Generation
- M, MX, PTX, T Series
- MBGP Multicast VPN Extranets Configuration Guidelines
- Understanding MBGP Multicast VPN Extranets
Example: IPv4 Multicast with Interprovider VPNs Configuration
Figure 1: IPv4 Multicast with Interprovider VPNs Topology Diagram

Interprovider VPNs are also mentioned in RFC 4364. An example is shown in Figure 1. The topology is slightly different; the main difference is the addition of MSDP between the two provider core transit (P) routers. In this limited topology, each P router is an SP-RP for the local autonomous system (AS), and Router CE1 is the VPN C-RP. VPN-A is the name of the routing instance on routers PE0 and PE1.
Router CE0
Router PE0
Router P0
Router P1
Router PE1
Router CE1
Verifying Your Work
The show commands used to verify proper functionality of multicast in an interprovider environment are the same ones used with the first Layer 3 VPN multicast example (see Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration).
The following output provides details for RP and the PIM join information:
- Router CE0 Status
- Router PE0 Status
- Router P0 Status
- Router P1 Status
- Router PE1 Status
- Router CE1 Status
Router CE0 Status
user@CE0> show pim rps extensive
Instance: PIM.master Family: INET RP: 10.254.14.132 Learned via: static configuration Time Active: 00:21:35 Holdtime: 0 Device Index: 119 Subunit: 32769 Interface: pe-6/0/0.32769 Group Ranges: 224.0.0.0/4 Active groups using RP: Register State for RP: Group Source FirstHop RP Address State Timeout Family: INET6
user@CE0> show pim join extensive
Instance: PIM.master Family: INET Group: 229.1.1.1 Source: 192.168.295.38 Flags: dense Upstream interface: fe-3/0/2.0 Downstream interfaces: t1-7/0/0:0.0 Instance: PIM.master Family: INET6
Router PE0 Status
user@PE0> show pim rps extensive
Instance: PIM.master Family: INET RP: 10.254.71.49 Learned via: static configuration Time Active: 00:22:07 Holdtime: 0 Device Index: 34 Subunit: 32769 Interface: pe-1/1/0.32769 Group Ranges: 224.0.0.0/4 Active groups using RP: 239.1.1.1 total 1 groups active Register State for RP: Group Source FirstHop RP Address State Timeout 239.1.1.1 10.254.71.51 10.254.71.51 10.254.71.49 Suppress 20 Family: INET6
user@PE0> show pim rps extensive instance VPN-A
Instance: PIM.VPN-A Family: INET RP: 10.254.14.132 Learned via: static configuration Time Active: 00:22:22 Holdtime: 0 Device Index: 34 Subunit: 32771 Interface: pe-1/1/0.32771 Group Ranges: 224.0.0.0/4 Active groups using RP: Register State for RP: Group Source FirstHop RP Address State Timeout Family: INET6
user@PE0> show pim join extensive
Instance: PIM.master Family: INET Group: 239.1.1.1 Source: * RP: 10.254.71.49 Flags: sparse,rptree,wildcard Upstream interface: so-0/0/0.0 Upstream State: Join to RP Downstream Neighbors: Interface: mt-1/1/0.32769 0.0.0.0 State: Join Flags: SRW Timeout: Infinity Group: 239.1.1.1 Source: 10.254.71.47 Flags: sparse,spt-pending Upstream interface: so-0/0/0.0 Upstream State: Join to Source Keepalive timeout: 198 Downstream Neighbors: Interface: mt-1/1/0.32769 0.0.0.0 State: Join Flags: S Timeout: Infinity Group: 239.1.1.1 Source: 10.254.71.51 Flags: sparse Upstream interface: local Upstream State: Local Source, Prune to RP Keepalive timeout: 198 Downstream Neighbors: Interface: so-0/0/0.0 192.168.296.42 State: Join Flags: S Timeout: 176 Instance: PIM.master Family: INET6
user@PE0> show pim join extensive instance
VPN-A
Instance: PIM.VPN-A Family: INET Group: 229.1.1.1 Source: 192.168.295.38 Flags: dense Upstream interface: t1-1/0/0:0.0 Downstream interfaces: mt-1/1/0.32769 Instance: PIM.VPN-A Family: INET6
Router P0 Status
user@P0> show pim rps extensive
Instance: PIM.master Family: INET RP: 10.254.71.49 Learned via: static configuration Time Active: 00:30:43 Holdtime: 0 Device Index: 33 Subunit: 32768 Interface: pd-1/1/0.32768 Group Ranges: 224.0.0.0/4 Active groups using RP: 239.1.1.1 total 1 groups active Register State for RP: Group Source FirstHop RP Address State Timeout 239.1.1.1 10.254.71.51 10.254.71.51 10.254.71.49 Receive Family: INET6
user@P0> show pim join extensive
Instance: PIM.master Family: INET Group: 239.1.1.1 Source: * RP: 10.254.71.49 Flags: sparse,rptree,wildcard Upstream interface: local Upstream State: Local RP Downstream Neighbors: Interface: so-0/1/0.0 192.168.296.41 State: Join Flags: SRW Timeout: 184 Group: 239.1.1.1 Source: 10.254.71.47 Flags: sparse,spt-pending Upstream interface: so-0/0/2.0 Upstream State: Local RP, Join to Source Keepalive timeout: 207 Downstream Neighbors: Interface: so-0/1/0.0 192.168.296.41 State: Join Flags: S Timeout: 184 Group: 239.1.1.1 Source: 10.254.71.51 Flags: sparse,spt Upstream interface: so-0/1/0.0 Upstream State: Local RP, Join to Source Keepalive timeout: 207 Downstream Neighbors: Interface: so-0/0/2.0 192.168.296.73 State: Join Flags: S Timeout: 186 Interface: so-0/1/0.0 (pruned) 192.168.296.41 State: Prune Flags: SR Timeout: 184 Instance: PIM.master Family: INET6
Router P1 Status
user@P1> show pim rps extensive
Instance: PIM.master Family: INET RP: 10.254.71.48 Learned via: static configuration Time Active: 06:26:56 Holdtime: 0 Device Index: 32 Subunit: 32768 Interface: pd-1/1/0.32768 Group Ranges: 224.0.0.0/4 Active groups using RP: 239.1.1.1 total 1 groups active Register State for RP: Group Source FirstHop RP Address State Timeout 239.1.1.1 10.254.71.47 10.254.71.47 10.254.71.48 Receive 0 Family: INET6
user@P1> show pim join extensive
Instance: PIM.master Family: INET Group: 239.1.1.1 Source: * RP: 10.254.71.48 Flags: sparse,rptree,wildcard Upstream interface: local Upstream State: Local RP Downstream Neighbors: Interface: so-0/0/1.0 192.168.296.50 State: Join Flags: SRW Timeout: 174 Group: 239.1.1.1 Source: 10.254.71.47 Flags: sparse,spt Upstream interface: so-0/0/1.0 Upstream State: Local RP, Join to Source Keepalive timeout: 196 Downstream Neighbors: Interface: so-0/0/1.0 (pruned) 192.168.296.50 State: Prune Flags: SR Timeout: 174 Interface: so-0/0/2.0 192.168.296.74 State: Join Flags: S Timeout: 178 Group: 239.1.1.1 Source: 10.254.71.51 Flags: sparse,spt-pending Upstream interface: so-0/0/2.0 Upstream State: Local RP, Join to Source Keepalive timeout: 196 Downstream Neighbors: Interface: so-0/0/1.0 192.168.296.50 State: Join Flags: S Timeout: 174 Instance: PIM.master Family: INET6
Router PE1 Status
user@PE1> show pim rps extensive
Instance: PIM.master Family: INET RP: 10.254.71.48 Learned via: static configuration Time Active: 00:25:13 Holdtime: 0 Device Index: 34 Subunit: 32770 Interface: pe-1/1/0.32770 Group Ranges: 224.0.0.0/4 Active groups using RP: 239.1.1.1 total 1 groups active Register State for RP: Group Source FirstHop RP Address State Timeout 239.1.1.1 10.254.71.47 10.254.71.47 10.254.71.48 Suppress 42 Family: INET6
user@PE1> show pim rps extensive instance VPN-A
Instance: PIM.VPN-A Family: INET RP: 10.254.14.132 Learned via: static configuration Time Active: 00:25:17 Holdtime: 0 Device Index: 34 Subunit: 32771 Interface: pe-1/1/0.32771 Group Ranges: 224.0.0.0/4 Active groups using RP: Register State for RP: Group Source FirstHop RP Address State Timeout Family: INET6
user@PE1> show pim join extensive
Instance: PIM.master Family: INET Group: 239.1.1.1 Source: * RP: 10.254.71.48 Flags: sparse,rptree,wildcard Upstream interface: so-0/0/3.0 Upstream State: Join to RP Downstream Neighbors: Interface: mt-1/1/0.32769 0.0.0.0 State: Join Flags: SRW Timeout: Infinity Group: 239.1.1.1 Source: 10.254.71.47 Flags: sparse Upstream interface: local Upstream State: Local Source, Prune to RP Keepalive timeout: 173 Downstream Neighbors: Interface: so-0/0/3.0 192.168.296.49 State: Join Flags: S Timeout: 199 Group: 239.1.1.1 Source: 10.254.71.51 Flags: sparse,spt-pending Upstream interface: so-0/0/3.0 Upstream State: Join to Source Keepalive timeout: 173 Downstream Neighbors: Interface: mt-1/1/0.32769 0.0.0.0 State: Join Flags: S Timeout: Infinity Instance: PIM.master Family: INET6
user@PE1> show pim join extensive instance
VPN-A
Instance: PIM.VPN-A Family: INET Group: 229.1.1.1 Source: 192.168.295.38 Flags: dense Upstream interface: mt-1/1/0.32769 Downstream interfaces: t1-1/0/0:0.0 Instance: PIM.VPN-A Family: INET6
Router CE1 Status
user@CE1> show pim rps extensive
Instance: PIM.master Family: INET RP: 10.254.14.132 Learned via: static configuration Time Active: 00:28:22 Holdtime: 0 Device Index: 69 Subunit: 32768 Interface: pd-3/1/0.32768 Group Ranges: 224.0.0.0/4 Active groups using RP: Register State for RP: Group Source FirstHop RP Address State Timeout Family: INET6
user@CE1> show pim join extensive
Instance: PIM.master Family: INET Group: 229.1.1.1 Source: 192.168.295.38 Flags: dense Upstream interface: t1-2/0/0:0.0 Downstream interfaces: fe-2/2/0.0 Instance: PIM.master Family: INET6
Related Documentation
- M, MX, T Series
- Multicast over Layer 3 VPNs Overview
- Configuring BGP, MPLS, RSVP, and an IGP on the PE and Core Routers for Draft Rosen VPNs
- Configuring BGP, MPLS, RSVP, and an IGP on the PE and Core Routers for MBGP MVPNs
- Configuring Interfaces for Layer 3 VPNs
- Configuring Intra-AS Inclusive Point-to-Multipoint Traffic Engineering LSPs
- Configuring Intra-AS Selective Provider Tunnels
- Configuring MBGP MVPNs to Support IPv6 Multicast Traffic
- Configuring PIM and the VPN Group Address in a Routing Instance
- Configuring Provider Tunnels
- Configuring the Master PIM Instance on the PE Router for BGP-Based Multicast VPNs
- Configuring the Master PIM Instance on the PE Router in the Service Provider Network
- Creating a Routing Instance for a Multiprotocol BGP-Based Multicast VPN
- Configuring the Router’s IPv4 Bootstrap Router Priority
- Creating a Unique Logical Loopback Interface for the Routing Instance for Draft Rosen VPNs
- Creating a Unique Logical Loopback Interface for the Routing Instance for MBGP MVPNs
- Dual PIM Draft-Rosen Multicast VPN Operation
- Enabling Multicast VPN in BGP
- Option: Configuring MSDP Within a Layer 3 VPN
- Option: Configuring Multicast Distribution Trees for Data
- Option: Configuring PIM Sparse Mode Graceful Restart for a Layer 3 VPN
- Option: Configuring Sender and Receiver Sites
- Option: Specifying Route Targets
- Understanding Multiprotocol BGP-Based Multicast VPNs: Next-Generation
- M, MX, PTX, T Series
- MBGP Multicast VPN Extranets Configuration Guidelines
- Understanding MBGP Multicast VPN Extranets
Published: 2012-11-15
Related Documentation
- M, MX, T Series
- Multicast over Layer 3 VPNs Overview
- Configuring BGP, MPLS, RSVP, and an IGP on the PE and Core Routers for Draft Rosen VPNs
- Configuring BGP, MPLS, RSVP, and an IGP on the PE and Core Routers for MBGP MVPNs
- Configuring Interfaces for Layer 3 VPNs
- Configuring Intra-AS Inclusive Point-to-Multipoint Traffic Engineering LSPs
- Configuring Intra-AS Selective Provider Tunnels
- Configuring MBGP MVPNs to Support IPv6 Multicast Traffic
- Configuring PIM and the VPN Group Address in a Routing Instance
- Configuring Provider Tunnels
- Configuring the Master PIM Instance on the PE Router for BGP-Based Multicast VPNs
- Configuring the Master PIM Instance on the PE Router in the Service Provider Network
- Creating a Routing Instance for a Multiprotocol BGP-Based Multicast VPN
- Configuring the Router’s IPv4 Bootstrap Router Priority
- Creating a Unique Logical Loopback Interface for the Routing Instance for Draft Rosen VPNs
- Creating a Unique Logical Loopback Interface for the Routing Instance for MBGP MVPNs
- Dual PIM Draft-Rosen Multicast VPN Operation
- Enabling Multicast VPN in BGP
- Option: Configuring MSDP Within a Layer 3 VPN
- Option: Configuring Multicast Distribution Trees for Data
- Option: Configuring PIM Sparse Mode Graceful Restart for a Layer 3 VPN
- Option: Configuring Sender and Receiver Sites
- Option: Specifying Route Targets
- Understanding Multiprotocol BGP-Based Multicast VPNs: Next-Generation
- M, MX, PTX, T Series
- MBGP Multicast VPN Extranets Configuration Guidelines
- Understanding MBGP Multicast VPN Extranets