L3VPN over RSVP-TE

Updated: June 17, 2026

Want to summarize with AI?

Describes integrating L3VPN with RSVP-TE, including configuration procedures to establish advanced VPN services over traffic-engineered MPLS tunnels.

L3VPN over RSVP-TE is an MPLS L3VPN transport option that

uses MPLS-TE to map traffic flows to paths based on network resources
uses RSVP to signal MPLS-TE label switched paths (LSPs), and
reserves resources for local and remote data flows.

Feature history

The feature history table lists release support for this feature.

Table 1. Feature History Table
Feature Name	Release Information	Feature Description
L3VPN over RSVP-TE	Release 25.4.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only) This feature is supported on: 8011-32Y8L2H2FH 8011-12G12X4Y-A/D
L3VPN over RSVP-TE	Release 25.1.1	Introduced in this release on: Fixed Systems (8700 [ASIC: K100], 8010 [ASIC: A100])(select variants only) This feature is supported on: 8011-4G24Y4H-I 8712-MOD-M
L3VPN over RSVP-TE	Release 24.4.1	Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100])(select variants only); Modular Systems (8800 [LC ASIC: P100])(select variants only) *This feature is supported on: 8212-48FH-M 8711-32FH-M 88-LC1-36EH 88-LC1-12TH24FH-E 88-LC1-52Y8H-EM
L3VPN over RSVP-TE	Release 7.3.2	Using labeled switch paths (LSPs), this feature enables resource reservations in each node across data paths on MPLS-configured Layer 3 VPNs. Such reservations allow service providers to offer high throughput to their subscribers with optimal network operations.

RSVP-TE details

MPLS Traffic Engineering (MPLS-TE) learns the topology and resources available in a network, then maps traffic flows to particular paths based on network resources. MPLS-TE builds unidirectional tunnels from source to destination in the form of label switched paths (LSPs), which are then used to forward traffic. MPLS-TE uses RSVP to signal LSPs.

RSVP processes protocol messages from other systems, handles resource requests from local clients, and generates protocol messages. As a result, resources are reserved for data flows on behalf of both local and remote clients. RSVP creates, maintains, and deletes these resource reservations. RSVP is automatically enabled on interfaces where MPLS-TE is configured.

For more information on RSVP-TE and MPLS-TE, see the MPLS Configuration Guide for Cisco 8000 Series Routers.

Configure L3VPN over RSVP-TE

Set up Layer 3 VPN (L3VPN) service over MPLS Traffic Engineering tunnels using RSVP-TE to optimize routing, resource utilization, and traffic management.

MPLS Traffic Engineering (MPLS-TE) builds label switched paths (LSPs) signaled with RSVP, allowing for efficient mapping of traffic flows. Each LSP acts as a unidirectional tunnel across the core. L3VPN, delivered over RSVP-TE, combines these tunnels with MP-BGP for multi-site connectivity.

For more information on RSVP-TE and MPLS-TE, see the MPLS Configuration Guide for Cisco 8000 Series Routers.

Before you begin

Plan the core routing protocol, MPLS label distribution method, MP-BGP peering, PE-CE protocol support, and tunnel destinations before you begin.

Procedure

	1.	Configure core routing protocols. Ensure all core routers have consistent, reachability-focused routing configuration. Use standard IGP (OSPF or IS-IS). For specifics, see the Routing Configuration Guide for Cisco 8000 Series Routers.
	2.	Enable MPLS and configure label distribution. Enable MPLS on all core interfaces. Decide between: MPLS LDP—See the Implementing MPLS Label Distribution Protocol chapter in the MPLS Configuration Guide for Cisco 8000 Series Routers for configuration information. MPLS Traffic Engineering Resource Reservation Protocol (RSVP)—See the Implementing RSVP for MPLS-TE chapter in the MPLS Configuration Guide for Cisco 8000 Series Routers for configuration information.
	3.	Configure RSVP-TE tunnels in the core. Signal label switched paths using RSVP-TE from each ingress PE. RSVP is automatically enabled on interfaces with MPLS-TE configuration.
	4.	Set up MP-BGP for VPNv4 routes. Configure MP-BGP peering between all PEs to carry VPN routes across the MPLS core.
	5.	Configure PE-CE protocol support. Set up appropriate routing protocols or static routes for PE-CE connections according to your solution design.
	6.	Verify and test end-to-end L3VPN connectivity. Ensure services are reachable and that traffic engineering objectives are met.

After all steps are complete, L3VPN transport runs over RSVP-TE tunnels across your MPLS core, allowing for optimal routing, resiliency, and cross-domain VPN connectivity.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.