Configuring Point-to-Multipoint LSPs for an MBGP MVPN
The 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 autonomous systems). A point-to-multipoint LSP is an RSVP-signaled LSP with a single source and multiple destinations.
You can configure point-to-multipoint LSPs for MBGP MVPNs as follows:
Static point-to-multipoint LSPs—Configure static point-to-multipoint LSPs using the standard MPLS LSP statements specified at the
[edit protocols mpls]hierarchy level. You manually configure each of the leaf nodes for the point-to-multipoint LSP.Dynamic point-to-multipoint LSPs using the default template—Configuring dynamic point-to-multipoint LSPs using the
default-templateoption causes the leaf nodes to be discovered automatically. The leaf nodes are discovered through BGP intra-AS automatic discovery. Thedefault-templateoption allows you to minimize the amount of configuration needed. However, it does not allow you to configure any of the standard MPLS options.Dynamic point-to-multipoint LSPs using a user-configured template—Configuring dynamic point-to-multipoint LSPs using a user-configured template also causes the leaf nodes to be discovered automatically. By creating your own template for the point-to-multipoint LSPs, all of the standard MPLS features (such as bandwidth allocation and traffic engineering) can be configured.
Be aware of the following properties for the egress PE router in a point-to-multipoint LSP configured for a multicast VPN:
Penultimate hop-popping is not used by point-to-multipoint LSPs for multicast VPNs. Only ultimate hop-popping is used.
You must configure either the
vrf-table-labelstatement or a virtual loopback tunnel interface on the egress PE router.If you configure the
vrf-table-labelstatement on the egress PE router, and the egress PE router is also a transit router for the point-to-multipoint LSP, the penultimate hop router sends two copies of each packet over the link to the egress PE router.If you configure the
vrf-table-labelstatement on the egress PE router, and the egress PE router is not a transit router for the point-to-multipoint LSP, the penultimate hop router can send just one copy of each packet over the link to the egress PE router.If you configure a virtual loopback tunnel interface on the egress PE router, and the egress PE router is also a transit router for the point-to-multipoint LSP, the penultimate hop router sends just one copy of each packet over the link to the egress PE router. A virtual loopback tunnel interface can perform two lookups on an incoming packet, one for the multicast MPLS lookup and one for the IP lookup.
Junos OS Release 11.2 and earlier do not support point-to-multipoint LSPs with next-generation multicast VPNs on MX80 routers.
The following sections describe how to configure point-to-multipoint LSPs for MBGP MVPNs:
Configuring RSVP-Signaled Inclusive Point-to-Multipoint LSPs for an MBGP MVPN
You can configure LDP-signaled or RSVP-signaled 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 RSVP-signaled inclusive point-to-multipoint
LSP, include the static-lsp statement:
static-lsp lsp-name;
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name provider-tunnel rsvp-te][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel rsvp-te]
To configure dynamic inclusive point-to-multipoint LSPs, include
the label-switched-path-template statement:
label-switched-path-template (Multicast) { (default-template | lsp-template-name); }
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name provider-tunnel rsvp-te][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel rsvp-te]
You can configure either the default-template option
or manually configure a point-to-multipoint LSP template and specify
the template name.
Configuring Selective Provider Tunnels for an MBGP MVPN
You can configure LDP-signaled or RSVP-signaled 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 {
ldp-p2mp;
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 {
ldp-p2mp;
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 {
ldp-p2mp;
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 {
ldp-p2mp;
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:
[edit routing-instances routing-instance-name provider-tunnel][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel]
The following sections describe how to configure selective point-to-multipoint LSPs for MBGP MVPNs:
- Configuring the Multicast Group Address for an MBGP MVPN
- Configuring the Multicast Source Address for an MBGP MVPN
- Configuring Static Selective Point-to-Multipoint LSPs for an MBGP MVPN
- Configuring Dynamic Selective Point-to-Multipoint LSPs for an MBGP MVPN
- Configuring the Threshold for Dynamic Selective Point-to-Multipoint LSPs for an MBGP MVPN
- Configuring the Tunnel Limit for Dynamic Selective Point-to-Multipoint LSPs for an MBGP MVPN
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:
[edit routing-instances routing-instance-name provider-tunnel selective][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective]
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:
[edit routing-instances routing-instance-name provider-tunnel selective group address][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective group address]
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 by 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:
rsvp-te static-lsp lsp-name;
You can include these statements at the following hierarchy levels:
[edit routing-instances routing-instance-name provider-tunnel selective group address source source-address][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective group address source source-address]
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:
[edit routing-instances routing-instance-name provider-tunnel selective group address source source-address][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective group address source source-address]
The label-switched-path-template statement includes
the following options:
default-template—Specify that point-to-multipoint LSPs are generated dynamically based on the default template. No user configuration is required for the LSPs. However, the automatically generated LSPs include none of the common LSP features, such as bandwidth allocation and traffic engineering.lsp-template-name—Specify the name of an LSP template to be used for the point-to-multipoint LSP. You need to configure the LSP template to be used as a basis for the point-to-multipoint LSPs. You can configure any of the common LSP features for this template.
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:
threshold-rate number;
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name provider-tunnel selective group address source source-address][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective group address source source-address]
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:
[edit routing-instances routing-instance-name provider-tunnel selective][edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective]