[an error occurred while processing this directive][an error occurred while processing this directive]

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 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 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.

Below is an example configuration for point-to-multipoint LSPs on a selective tunnel with statically configured leafs:

[edit]routing-instances {selective-tunnel-example {instance-type vpls;route-distinguisher 10.255.71.2:100;protocols {vpls {tunnel-services { # This enables vt interfaces for this routing instance.}}provider-tunnel {rsvp-te {label-switched-path-template {mvpn_template;}}}selective {group 225.10.10.1/32 {source 192.2.1.2/32 {rsvp-te {static-lsp lsp1;}}}group 226.10.10.1/32 {source 192.2.1.2/32 {rsvp-te {static-lsp lsp1;}}}}}}}

The following example shows an example with dynamic selective trees and the default template:

[edit]routing-instances {dynamic-selective-tunnel-example {instance-type vpls;route-distinguisher 10.255.71.2:100;protocols {vpls {tunnel-services {}}provider-tunnel {rsvp-te {label-switched-path-template {default-template;}}selective {group 225.10.10.1/32 {source 192.2.1.2/32 {rsvp-te {label-switched-path-template default-template;}}}group 226.10.10.1/32 {source 192.2.1.2/32 {rsvp-te {label-switched-path-template default-template;}}}}}}}

Published: 2010-04-15

[an error occurred while processing this directive]