Configuring Point-to-Multipoint LSPs for an MBGP MVPN

Junos OS supports point-to-multipoint label-switched paths (LSPs) for MBGP MVPNs. Point-to-multipoint LSPs for multicast VPNs are supported for intra-autonomous system (AS) environments (within an AS), but are not supported for inter-AS environments (between ASs). A point-to-multipoint LSP is an RSVP-signaled LSP with a single source and multiple destinations. For more information about point-to-multipoint LSPs, see the Junos MPLS Applications Configuration Guide.

You can configure point-to-multipoint LSPs for MBGP MVPNs as follows:

Be aware of the following properties for the egress PE router in a point-to-multipoint LSP configured for a multicast VPN:

The following sections describe how to configure point-to-multipoint LSPs for MBGP MVPNs:

Configuring Inclusive Point-to-Multipoint LSPs for an MBGP MVPN

You can configure inclusive point-to-multipoint LSPs for MBGP MVPNs. Aggregation is not supported, so you need to configure an inclusive point-to-multipoint LSP for each sender PE router in each multicast VPN routing instance. The sender PE router is in the sender site set of the MBGP MVPN.

To configure a static inclusive point-to-multipoint LSP, include the static-lsp statement:

static-lsp lsp-name;

You can include this statement at the following hierarchy levels:

To configure dynamic inclusive point-to-multipoint LSPs, include the label-switched-path-template statement:

label-switched-path-template {(default-template | lsp-template-name);}

You can include this statement at the following hierarchy levels:

You can configure either the default-template option or manually configure a point-to-multipoint LSP template and specify the template name. For information about how to configure a point-to-multipoint LSP template, see the Junos MPLS Applications Configuration Guide.

Configuring Selective Provider Tunnels for an MBGP MVPN

You can configure selective point-to-multipoint LSPs (also referred to as selective provider tunnels) for MBGP MVPNs. Selective point-to-multipoint LSPs send traffic only to the receivers configured for the multicast VPNs, helping to minimize flooding in the service provider's network.

As with inclusive point-to-multipoint LSPs, you can configure both dynamic and static selective tunnels for the multicast VPN.

To configure selective point-to-multipoint provider tunnels, include the selective statement:

selective {group multicast--prefix/prefix-length {source ip--prefix/prefix-length {pim-ssm {group-range multicast-prefix;}rsvp-te {label-switched-path-template {(default-template | lsp-template-name);}static-lsp point-to-multipoint-lsp-name;}threshold-rate kbps;}wildcard-source {pim-ssm {group-range multicast-prefix;}rsvp-te {label-switched-path-template {(default-template | lsp-template-name);}static-lsp point-to-multipoint-lsp-name;}threshold-rate kbps;}}tunnel-limit number;wildcard-group-inet {wildcard-source {pim-ssm {group-range multicast-prefix;}rsvp-te {label-switched-path-template {(default-template | lsp-template-name);}static-lsp lsp-name;}threshold-rate number;}}wildcard-group-inet6 {wildcard-source {pim-ssm {group-range multicast-prefix;}rsvp-te {label-switched-path-template {(default-template | lsp-template-name);}static-lsp lsp-name;}threshold-rate number;}}}

You can include these statements at the following hierarchy levels:

The following sections describe how to configure selective point-to-multipoint LSPs for MBGP MVPNs:

Configuring the Multicast Group Address for an MBGP MVPN

To configure a point-to-multipoint LSP for an MBGP MVPN, you need to specify a multicast group address by including the group statement:

group address { ... }

You can include this statements at the following hierarchy levels:

The address must be a valid multicast group address. Multicast uses the Class D IP address range (224.0.0.0 through 239.255.255.255).

Configuring the Multicast Source Address for an MBGP MVPN

To configure a point-to-multipoint LSP for an MBGP MVPN, specify a multicast source address by including the source statement:

source address { ... }

You can include this statement at the following hierarchy levels:

Configuring Static Selective Point-to-Multipoint LSPs for an MBGP MVPN

You can configure a static selective point-to-multipoint LSP for an MBGP MVPN. You need to configure a static LSP using the standard MPLS LSP statements at the [edit protocols mpls] hierarchy level. You then include the static LSP in your selective point-to-multipoint LSP configuration using the static-lsp statement. Once this functionality is enabled on the source PE router, the static point-to-multipoint LSP is created based on your configuration.

To configure a static selective point-to-multipoint LSP, include the rsvp-te and the static-lsp statements:

You can include these statements at the following hierarchy levels:

Configuring Dynamic Selective Point-to-Multipoint LSPs for an MBGP MVPN

You can configure a dynamic selective point-to-multipoint LSP for an MBGP MVPN. The leaf nodes for a dynamic point-to-multipoint LSP can be automatically discovered using leaf automatic discovery routes. Selective provider multicast service interface (S-PMSI) automatic discovery routes are also supported.

To configure a dynamic selective point-to-multipoint provider tunnel, include the rsvp-te and label-switched-path-template statements:

rsvp-te label-switched-path-template {(default-template | lsp-template-name);}

You can include these statements at the following hierarchy levels:

The label-switched-path-template statement includes the following options:

Configuring the Threshold for Dynamic Selective Point-to-Multipoint LSPs for an MBGP MVPN

To configure a selective point-to-multipoint LSP dynamically, you need to specify the data threshold (in kilobits per second) required before a new tunnel is created using the threshold-rate statement:

You can include this statement at the following hierarchy levels:

Configuring the Tunnel Limit for Dynamic Selective Point-to-Multipoint LSPs for an MBGP MVPN

To configure a limit on the number of tunnels that can be generated for a dynamic point-to-multipoint LSP, include the tunnel-limit statement:

tunnel-limit number;

You can include this statement at the following hierarchy levels: