Related Documentation
- EX, M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPNs
- M, MX, T Series
- Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration
- Example: Configuring MBGP MVPN Senders and Receivers using PIM SM and RSVP-TE Provider Tunnels
- Example: Configuring Point-to-Multipoint LDP LSPs as the Data Plane for Intra-AS MBGP MVPNs
- Example: IPv4 Multicast with Interprovider VPNs Configuration
- M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPN Extranets
Configuring Intra-AS Selective Provider Tunnels
Point-to-multipoint traffic engineering LSPs are supported as the data plane for selective provider tunnels. A multicast VPN can be configured to use inclusive trees or selective trees or a combination of both. Aggregation is not supported for point-to-multipoint traffic engineering LSPs.
 | Note: Configure either LDP or regular MPLS LSPs between PE routers or switches to ensure VPN unicast connectivity. Point-to-multipoint LSPs are used for multicast data forwarding only. |
You must configure the following when configuring point-to-multipoint LSPs in provider tunnels:
- The BGP multicast VPN control plane, as described in Creating a Routing Instance for a Multiprotocol BGP-Based Multicast VPN.
- Point-to-multipoint traffic engineering as the provider tunnel technology on each PE configured for multicast VPN that belongs to the sender site.
- Either a VT interface or a vrf-table-label on the multicast VPN instance. For more information about configuring VT interfaces, see the Junos OS VPNs Configuration Guide.
- Point-to-multipoint traffic engineering support on each P router.
When selective trees are used, there must be a separate point-to-multipoint traffic engineering LSP for each multicast distribution tree in the backbone that carries traffic belonging to a specified set of one or more multicast groups, from one or more multicast VPNs. Multiple groups can be bound to the same selective point-to-multipoint LSP if the selective point-to-multipoint LSP leaves are statically configured. If the leaves are dynamically discovered, only one source or group can be bound to it.
Selective point-to-multipoint LSPs can be statically configured or triggered by a bandwidth threshold. If the threshold rate is configured, a S-PMSI autodiscovery route is generated for a particular (C-S, C-G) if it falls in the range specified by (C-S prefix, C-G prefix) and its data rate exceeds the configured threshold rate. In the following example, the threshold rate is set to zero Kbps. This causes the selective tunnel to be created immediately, meaning that the multicast traffic does not use an inclusive tunnel at all. Optionally, you can leave the threshold rate unconfigured and the result is the same as setting the threshold to zero.
Below is an example configuration for point-to-multipoint LSPs on a selective tunnel with statically configured leafs:
The following example shows an example with dynamic selective trees and the default template:
Related Documentation
- EX, M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPNs
- M, MX, T Series
- Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration
- Example: Configuring MBGP MVPN Senders and Receivers using PIM SM and RSVP-TE Provider Tunnels
- Example: Configuring Point-to-Multipoint LDP LSPs as the Data Plane for Intra-AS MBGP MVPNs
- Example: IPv4 Multicast with Interprovider VPNs Configuration
- M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPN Extranets
Published: 2013-04-03
Related Documentation
- EX, M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPNs
- M, MX, T Series
- Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration
- Example: Configuring MBGP MVPN Senders and Receivers using PIM SM and RSVP-TE Provider Tunnels
- Example: Configuring Point-to-Multipoint LDP LSPs as the Data Plane for Intra-AS MBGP MVPNs
- Example: IPv4 Multicast with Interprovider VPNs Configuration
- M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPN Extranets
