[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Traffic Engineering Point-to-Multipoint LSPs in Provider Tunnels

You can configure point-to-multipoint MPLS traffic engineering data plane support for intra-AS traffic. Point-to-multipoint LSPs can be used for TE inclusive and selective provider tunnels. A multicast VPN can be configured to use a combination of inclusive and selective trees or only inclusive trees or only selective trees. Aggregation is not supported for point-to-multipoint TE 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:

Intra-AS Inclusive Point-to-Multipoint TE LSPs

Point-to-multipoint TE LSPs are supported as the data plane for intra-AS inclusive provider tunnels. On each PE router, a point-to-multipoint TE 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 TE LSPs must be configured on this PE router. The PE would be the root of the three point-to-multipoint TE 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:

[edit]
protocols {
mpls {
label-switched-path mvpn-example-p2mp-temlate {
template;
p2mp;
link-protection;
optimize-timer 50;
traceoptions {
file mvpn-a-p2mp-lsp.log;
flag all;
}
}
}
}

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.

[edit]
routing-instance {
routing-instance configured-dynamic-example {
instance-type vrf;
interface ge-1/0/0.0;
route-distinguisher 10.255.71.1:100;
vrf-table-label;
provider-tunnel {
rsvp-te label switched-path-template mvpn-example-p2mp-temlate;
}
}
}

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

[edit]
protocols {
mpls {
label-switched-path vpls-example-p2mp-s21_lsp_a {
to 192.168.1.1
p2mp example-static-lsp;
}
label-switched-path vpls-example-p2mp-s21_lsp_b {
to 192.168.1.2;
p2mp example-static-lsp;
}
}
}

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:

[edit]
routing-instance example-static {
provider-tunnel {
rsvp-te {
static-lsp example-static-lsp;
}
}
}

Intra-AS Selective Provider Tunnels

Point-to-multipoint TE LSPs are supported as the data plane for selective provider tunnels. When selective trees are used, there must be a separate point-to-multipoint TE 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 auto-discovery 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 vrf;
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 vrf;
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;
}
}
}
}
}
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.