Navigation
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: Basic IPv4 Multicast over a Layer 3 VPN Configuration
Figure 1: Basic IPv4 Multicast over a Layer 3 VPN Topology Diagram
In Figure 1, the multicast source sends to group 229.1.1.1, and the receiver listens to the same group address. The VPN C-RP is located at Router CE1, whereas the SP-RP is located at Router P0. The routing instances are named VPN-A on both routers PE0 and PE1.
Router CE0
[edit]protocols {pim {rp {dense-groups {229.0.0.0/8;}static {address 10.254.245.91;}}interface all {mode sparse-dense;version 2;}interface fxp0.0 {disable;}}}
In this example, the interface all statement is configured. If the topology requires only a few interfaces to be configured for PIM, then loopback interface lo0 must also be one of the configured interfaces.
Router PE0
[edit]protocols {pim {rp {static {address 10.254.71.47;}}interface all {mode sparse;version 2;}interface fxp0.0 {disable;}}}
Router PE0 also requires a standard VPN configuration, along with the PIM instance configuration. The vpn-group-address command is the only new PIM statement with PIM used exclusively with a routing instance multicast configuration.
Router PE0
[edit]routing-instances {VPN-A {instance-type vrf;interface t1-0/3/0:0.0; interface lo0.1 route-distinguisher 10.254.71.46:100;vrf-import VPNA-import;vrf-export VPNA-export;provider-tunnel {pim-asm {group-address 239.1.1.1;}}protocols {ospf {export bgp-to-ospf;area 0.0.0.0 {interface t1-0/3/0:0.0;interface lo0.1;}} pim { dense-groups {229.0.0.0/8;} vpn-group-address 239.1.1.1; rp {static {address 10.254.245.91;}}interface t1-0/3/0:0.0 {mode sparse-dense;version 2;} interface lo0.1 { mode sparse-dense;version 2;}}}}}
Router P0
[edit]protocols {pim {rp {local { address 10.254.71.47;}}interface all {mode sparse;version 2;}interface fxp0.0 {disable;}}}
Again, if the configuration calls for specific interfaces to be configured for PIM, loopback interface lo0 must be included as one of the interfaces running PIM.
Router PE1
[edit]protocols {pim {rp {static {address 10.254.71.47;}}interface all {mode sparse;version 2;}interface fxp0.0 {disable;}}}routing-instances {VPN-A {instance-type vrf;interface t1-1/0/0:0.0;interface lo0.1;route-distinguisher 10.254.71.51:100;vrf-import VPNA-import;vrf-export VPNA-export;provider-tunnel {pim-asm {group-address 239.1.1.1;}}protocols {ospf {export bgp-to-ospf;area 0.0.0.0 {interface t1-1/0/0:0.0;interface lo0.1;}}pim {dense-groups {229.0.0.0/8;}vpn-group-address 239.1.1.1; rp {static {address 10.254.245.91;}}interface t1-1/0/0:0.0 {mode sparse-dense;version 2;}interface lo0.1 { mode sparse-dense;version 2;}}}}}
Router CE1
[edit]protocols {pim {dense-groups {229.0.0.0/8;} rp { local {address 10.254.245.91;}}interface all {mode sparse-dense;version 2;}interface fxp0.0 {disable;}}}
Verifying Your Work
To verify correct operation of basic IPv4 multicast over a Layer 3 VPN, use the following commands:
- show pim
- show pim rps
- show pim rps instance instance-name
- show pim join
- show pim join extensive
- show pim join extensive instance instance-name
- show multicast route extensive
- show multicast next-hops
- show interfaces mt-fpc/pic/port extensive
The following sections show the output of these commands used with the configuration example:
RP Information
You can view PIM information for the master instance with the show pim command. You can see information on the PIM routing instance with the show pim (rps | join extensive) instance instance-name command. Output verifying the SP-RP (10.254.71.47) as well as the VPN C-RP (10.254.245.91) follows.
user@PE0> show pim rps
Instance: PIM.master Family: INET RP address Type Holdtime Timeout Active groups Group prefixes 10.254.71.47 static 0 None 1 224.0.0.0/4 Family: INET6 RP address Type Holdtime Timeout Active groups Group prefixes user@PE0> show pim rps instance VPN-A Instance: PIM.VPN-A Family: INET RP address Type Holdtime Timeout Active groups Group prefixes 10.254.245.91 static 0 None 0 224.0.0.0/4 Family: INET6 RP address Type Holdtime Timeout Active groups Group prefixes
PIM Information Before Multicast Transmission
With the configuration properly set, the backbone PIM sessions should be established before any traffic is forwarded. In the output below, the routers were configured, but the traffic source was not transmitting and the receiver was not requesting to be part of a group. Notice that there is no PIM join information for the routing instances yet.
Router PE0
user@PE0> show pim join extensive Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: so-0/0/2.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.46
Flags: sparse
Upstream interface: local
Upstream State: Local Source, Prune to RP
Keepalive timeout: 166
Downstream Neighbors:
Interface: so-0/0/2.0
192.168.296.70 State: Join Flags: S Timeout: 204
Group: 239.1.1.1
Source: 10.254.71.51
Flags: sparse,spt-pending
Upstream interface: so-0/0/2.0
Upstream State: Join to Source
Keepalive timeout: 166
Downstream Neighbors:
Interface: mt-1/1/0.32769
0.0.0.0 State: Join Flags: S Timeout: Infinity
user@PE0> show pim join extensive instance VPN-A
Instance: PIM.VPN-A Family: INET
Router P0
user@P0> show pim join extensive Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: local
Upstream State: Local RP
Downstream Neighbors:
Interface: so-0/0/0.0
192.168.296.34 State: Join Flags: SRW Timeout: 186
Interface: so-0/0/2.0
192.168.296.69 State: Join Flags: SRW Timeout: 198
Group: 239.1.1.1
Source: 10.254.71.46
Flags: sparse,spt
Upstream interface: so-0/0/2.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 170
Downstream Neighbors:
Interface: so-0/0/0.0
192.168.296.34 State: Join Flags: S Timeout: 186
Interface: so-0/0/2.0 (pruned)
192.168.296.69 State: Prune Flags: SR Timeout: 198
Group: 239.1.1.1
Source: 10.254.71.51
Flags: sparse,spt
Upstream interface: so-0/0/0.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 170
Downstream Neighbors:
Interface: so-0/0/0.0 (pruned)
192.168.296.34 State: Prune Flags: SR Timeout: 186
Interface: so-0/0/2.0
192.168.296.69 State: Join Flags: S Timeout: 198
Router PE1
user@PE1> show pim join extensive Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: so-0/1/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.46
Flags: sparse,spt-pending
Upstream interface: so-0/1/0.0
Upstream State: Join to Source
Keepalive timeout: 180
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: 180
Downstream Neighbors:
Interface: so-0/1/0.0
192.168.296.33 State: Join Flags: S Timeout: 168
Successful PIM Join Verification
In the remaining output for this example, the show pim join output shows group participation. Also displayed is the output from the show multicast route extensive and show multicast next-hop commands. The join output for PIM within a VPN will reference the group 229.1.1.1, while the service provider side of the network will reference the join information for group 239.1.1.1 (which is the VPN group ID). In the show multicast route extensive output, you can view the group, sender, and upstream interface toward the sender.
Router CE0
user@CE0> show pim join
Instance: PIM.master Family: INET
Group: 229.1.1.1
Source: 192.168.295.34
Flags: dense
Upstream interface: fe-2/0/1.0
Instance: PIM.master Family: INET6
user@CE0> show multicast route extensive Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
229.1.1.1 192.168.295.34 /32 A F 120 8010 0 360
Upstream interface: fe-2/0/1.0
Session name: Unknown
Forwarding rate: 1 kbps (10 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@CE0> show multicast next-hops Family: INET ID Refcount KRefcount Downstream interface 120 2 1 t1-2/2/0:0.0
Router PE0
user@PE0> show pim join extensive Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: so-0/0/2.0
Upstream State: Join to RP
Downstream Neighbors:
Interface: mt-1/1/0.32769
10.1.71.46 State: Join Flags: SRW Timeout: Infinity
Group: 239.1.1.1
Source: 10.254.71.46
Flags: sparse
Upstream interface: local
Upstream State: Local Source, Prune to RP
Keepalive timeout: 188
Downstream Neighbors:
Interface: so-0/0/2.0
192.168.296.70 State: Join Flags: S Timeout: 180
Instance: PIM.master Family: INET6
user@PE0> show interfaces mt-1/1/0 extensive Physical interface: mt-1/1/0, Enabled, Physical link is Up
Interface index: 37, SNMP ifIndex: 45, Generation: 36
Type: Multicast-GRE, Link-level type: GRE, MTU: Unlimited, Speed: 800mbps
Hold-times : Up 0 ms, Down 0 ms
Device flags : Present Running
Interface flags: SNMP-Traps
Statistics last cleared: Never
Traffic statistics:
Input bytes : 2887970 0 bps
Output bytes : 0 0 bps
Input packets: 31896 0 pps
Output packets: 0 0 pps
Logical interface mt-1/1/0.32769 (Index 43) (SNMP ifIndex 0) (Generation 46)
Flags: Point-To-Point SNMP-Traps
IP-Header 239.1.1.1:10.254.71.46:47:df:64:0000000800000000
Encapsulation: GRE-NULL
Traffic statistics:
Input bytes : 0
Output bytes : 2396
Input packets: 0
Output packets: 34
Local statistics:
Input bytes : 0
Output bytes : 2396
Input packets: 0
Output packets: 34
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4446, Generation: 79, Route table: 3
Flags: None
Logical interface mt-1/1/0.49154 (Index 44) (SNMP ifIndex 0) (Generation 47)
Flags: Point-To-Point SNMP-Traps Encapsulation: GRE-NULL
Traffic statistics:
Input bytes : 1550
Output bytes : 0
Input packets: 33
Output packets: 0
Local statistics:
Input bytes : 1550
Output bytes : 0
Input packets: 33
Output packets: 0
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: Unlimited, Generation: 80, Route table: 3
Flags: None
user@PE0> show pim join extensive instance
VPN-A Instance: PIM.VPN-A Family: INET
Group: 229.1.1.1
Source: 192.168.295.34
Flags: dense
Upstream interface: t1-0/3/0:0.0
Downstream interfaces:
mt-1/1/0.32769
Instance: PIM.VPN-A Family: INET6
user@PE0> show pim join Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: so-0/0/2.0
Group: 239.1.1.1
Source: 10.254.71.46
Flags: sparse
Upstream interface: local
Instance: PIM.master Family: INET6
user@PE0> show pim join instance VPN-A
Instance: PIM.VPN-A Family: INET
Group: 229.1.1.1
Source: 192.168.295.34
Flags: dense
Upstream interface: t1-0/3/0:0.0
Instance: PIM.VPN-A Family: INET6
user@PE0> show multicast route extensive Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
239.1.1.1 10.254.71.46 /32 A F 86 9174 0 360
Upstream interface: local
Session name: Administratively Scoped
Forwarding rate: 1 kBps (10 pps)
239.1.1.1 10.254.71.51 /32 A F 96 36 0 360
Upstream interface: so-0/0/2.0
Session name: Administratively Scoped
Forwarding rate: 0 kBps (0 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@PE0> show multicast route extensive instance
VPN-A Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
229.1.1.1 192.168.295.34 /32 A F 85 9408 0 360
Upstream interface: t1-0/3/0:0.0
Session name: Unknown
Forwarding rate: 1 kBps (10 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@PE0> show multicast next-hops Family: INET ID Refcount KRefcount Downstream interface 86 2 1 so-0/0/2.0 85 2 1 mt-1/1/0.32769 96 2 1 mt-1/1/0.49154 Family: INET6
Router P0
user@P0> show pim join
Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: local
Group: 239.1.1.1
Source: 10.254.71.46
Flags: sparse,spt
Upstream interface: so-0/0/2.0
Group: 239.1.1.1
Source: 10.254.71.51
Flags: sparse,spt
Upstream interface: so-0/0/0.0
Instance: PIM.master Family: INET6
user@P0> show multicast route extensive Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
239.1.1.1 10.254.71.46 /32 A F 127 9906 195 360
Upstream interface: so-0/0/2.0
Session name: Administratively Scoped
Forwarding rate: 1 kBps (10 pps)
239.1.1.1 10.254.71.51 /32 A F 126 135 23 359
Upstream interface: so-0/0/0.0
Session name: Administratively Scoped
Forwarding rate: 0 kBps (0 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@P0> show multicast next-hops Family: INET ID Refcount KRefcount Downstream interface 127 2 1 so-0/0/0.0 126 2 1 so-0/0/2.0 Family: INET6
Router PE1
user@PE1> show pim join extensive Instance: PIM.master Family: INET
Group: 239.1.1.1
Source: *
RP: 10.254.71.47
Flags: sparse,rptree,wildcard
Upstream interface: so-0/1/0.0
Upstream State: Join to RP
Downstream Neighbors:
Interface: mt-1/1/0.32769
10.1.71.51 State: Join Flags: SRW Timeout: Infinity
Group: 239.1.1.1
Source: 10.254.71.46
Flags: sparse,spt-pending
Upstream interface: so-0/1/0.0
Upstream State: Join to Source
Keepalive timeout: 199
Downstream Neighbors:
Interface: mt-1/1/0.32769
10.1.71.51 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: 79
Downstream Neighbors:
Interface: so-0/1/0.0
192.168.296.33 State: Join Flags: S Timeout: 174
Interface: register to RP 10.254.71.47 on pe-1/1/0.32769
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.34
Flags: dense
Upstream interface: mt-1/1/0.32769
Downstream interfaces:
t1-1/0/0:0.0
Instance: PIM.VPN-A Family: INET6
user@PE1> show interfaces mt-1/1/0 extensive Physical interface: mt-1/1/0, Enabled, Physical link is Up
Interface index: 38, SNMP ifIndex: 45, Generation: 37
Type: Multicast-GRE, Link-level type: GRE, MTU: Unlimited, Speed: 800mbps
Hold-times : Up 0 ms, Down 0 ms
Device flags : Present Running
Interface flags: SNMP-Traps
Statistics last cleared: Never
Traffic statistics:
Input bytes : 2265256 7568 bps
Output bytes : 0 0 bps
Input packets: 24981 10 pps
Output packets: 0 0 pps
Logical interface mt-1/1/0.32769 (Index 45) (SNMP ifIndex 0) (Generation 46)
Flags: Point-To-Point SNMP-Traps
IP-Header 239.1.1.1:10.254.71.51:47:df:64:0000000800000000
Encapsulation: GRE-NULL
Traffic statistics:
Input bytes : 0
Output bytes : 10934
Input packets: 0
Output packets: 153
Local statistics:
Input bytes : 0
Output bytes : 10934
Input packets: 0
Output packets: 153
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 4418, Generation: 77, Route table: 1
Flags: None
Logical interface mt-1/1/0.49154 (Index 46) (SNMP ifIndex 0) (Generation 47)
Flags: Point-To-Point SNMP-Traps Encapsulation: GRE-NULL
Traffic statistics:
Input bytes : 1820512
Output bytes : 0
Input packets: 19848
Output packets: 0
Local statistics:
Input bytes : 5536
Output bytes : 0
Input packets: 120
Output packets: 0
Transit statistics:
Input bytes : 1814976 7568 bps
Output bytes : 0 0 bps
Input packets: 19728 10 pps
Output packets: 0 0 pps
Protocol inet, MTU: Unlimited, Generation: 78, Route table: 1
Flags: None
user@PE1> show multicast route extensive Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
239.1.1.1 10.254.71.46 /32 A F 76 11014 0 360
Upstream interface: so-0/1/0.0
Session name: Administratively Scoped
Forwarding rate: 1 kBps (10 pps)
239.1.1.1 10.254.71.51 /32 A F 103 1 0 360
Upstream interface: local
Session name: Administratively Scoped
Forwarding rate: 0 kBps (0 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@PE1> show multicast route extensive instance
VPN-A Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
229.1.1.1 192.168.295.34 /32 A F 99 10976 4 360
Upstream interface: mt-1/1/0.49154
Session name: Unknown
Forwarding rate: 1 kBps (10 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@PE1> show multicast next-hops Family: INET ID Refcount KRefcount Downstream interface 75 2 1 so-0/1/0.0 99 2 1 t1-1/0/0:0.0 76 2 1 mt-1/1/0.49154 Family: INET6
Router CE1
user@CE1> show pim join
Instance: PIM.master Family: INET
Group: 229.1.1.1
Source: 192.168.295.34
Flags: dense
Upstream interface: t1-7/0/0:0.0
Instance: PIM.master Family: INET6
user@CE1> show multicast route extensive 2 1 fe-3/0/2.0
Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
229.1.1.1 192.168.295.34 /32 A F 120 8010 0 360
Upstream interface: t1-7/0/0:0.0
Session name: Unknown
Forwarding rate: 1 kBps (10 pps)
Family: INET6
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
user@CE1> show multicast next-hopsFamily: INET ID Refcount KRefcount Downstream interface 120
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
