Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring Intra-AS Inclusive Point-to-Multipoint Traffic Engineering LSPs

Point-to-multipoint traffic engineering LSPs are supported as the data plane for intra-AS inclusive 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.

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

On each PE router, a point-to-multipoint traffic engineering LSP must be configured for every multicast VPN instance that belongs to a sender site set. This means that if there are four multicast VPN instances configured on a PE router and three of these multicast VPN instances belong to sender site sets, three point-to-multipoint traffic engineering LSPs must be configured on this PE router. The PE would be the root of the three point-to-multipoint traffic engineering LSPs, and the leaves of the LSPs would be determined either dynamically or through a static configuration.

If the multicast VPN instance is configured for dynamic leaf discovery, the leaves are automatically discovered through intra-AS autodiscovery routes. The point-to-multipoint LSPs can be signaled using default attributes or configured attributes. If you configure the multicast VPN instance to use default attributes, the LSPs cannot be signaled with bandwidth reservation and do not support CAC. Point-to-multipoint LSPs with configured attributes support both bandwidth reservation and CAC. In addition, they can be configured to support traffic engineering attributes such as fast-reroute.

If the multicast VPN instance is configured for static leaf discovery, you configure the leafs statically. Point-to-multipoint LSPs that are configured statically support all traffic engineering attributes.

To configure dynamic leaf discovery, include the label-switched-path-template statement at the [edit routing-instance routing-instance-name provider-tunnel rsvp-te] hierarchy level. Dynamic discovery can be configured by using default attributes with the default-template statement at the [edit routing-instance routing-instance-name provider-tunnel rsvp-te label-switched-path-template] hierarchy level.

If you want to signal with bandwidth reservation, use CAC, or use other traffic engineering options such as link protection, configure a template for dynamic leaf discovery by including the label-switched-path-template template-name statement at the [edit protocols mpls] hierarchy level:

You can apply the configured or default template by including the template name at the [edit routing-instance routing-instance-name provider-tunnel rsvp-te label-switched-path-template] hierarchy level. Be sure to either configure a VT interface or include the vrf-table-label statement in the routing instance.

To configure static LSPs, include the label-switched-path label-switched-path statement at the [edit protocols mpls] hierarchy level:

To apply statically configured LSPs, include the static statement at the [edit routing-instance routing-instance-name provider-tunnel rsvp-te static-lsp static-lsp-name] hierarchy level: