Building network automation solutions

9 module online course

Start now!

MPLS TE Autoroute Fundamentals

An MPLS Traffic Engineering (MPLS TE) tunnel is a unidirectional Label Switched Path (LSP) established between the tunnel head-end Label Switch Router (LSR) and tail-end LSR. Once the tunnel is established and operational, it’s ready to forward IPv4 data traffic. However, no traffic will enter the tunnel unless the IPv4 routing tables and CEF tables are modified. You can push the traffic into an MPLS TE tunnel with a static route or with policy-based routing (PBR) or modify the behavior of the link-state algorithm used to implement MPLS TE in your network.

The autoroute functionality configured with the tunnel mpls autoroute announce interface configuration command automatically inserts the MPLS TE tunnel in the SPF tree and ensures the tunnel is used to transport all the traffic from the head-end LSR to all destinations behind the tail-end LSR.

The following text written by Ivan Pepelnjak in 2010 was originally published on CT3 wiki. That web site became unreachable in early 2019. We retrieved the original text from the Internet Archive, cleaned it up, updated it with recent information if necessary, and republished it on ipSpace.net blog on December 4, 2020

Theory of operation

Autoroute is an extra step in the intra-area (or intra-level) best route selection process in OSPF or IS-IS. Without the autoroute-enabled MPLS TE tunnels, the SPF algorithm builds the shortest path tree (ignoring stub network IP prefixes) to compute the minimum cost to all other routers in the area and then selects the best routes based on the minimum cost toward individual IP prefixes. The autoroute computation modifies the shortest path tree on the tunnel head-end LSR before the best routes are selected: the path toward the tunnel tail-end LSR is replaced by a direct link (MPLS TE tunnel) in the SPF tree.

The modification of the SPF tree is local to the head-end router and does not affect the topology database or the SPF trees built by other routers.

Step-by-step autoroute example

The auroute functionality will be illustrated in a simple Service Provider network. The network has five core routers connected in a ring and two access routers connected to two of the core routers:

Sample MPLS TE network

Sample MPLS TE network

IS-IS is used as the routing protocol in the network and the IS-IS circuit costs have been set to 10 on the core links and to 50 on the access links.

Once the IS-IS adjacencies have been established and the link state information distributed between the routers, the information stored in the IS-IS topology database of router A represents the following graph:

Link state topology graph

Link state topology graph

SPF tree built on router A

When the router A runs the SPF algorithm, the link between nodes C and D is not used in the shortest-path tree; all the traffic from router A to router Y flows through routers E and D.

SPF tree created in router A

SPF tree created in router A

The traffic from router X to router Y also flows through routers E and D. A is the downstream router of router X; whatever routing decisions router X makes, once the packet arrives at router A, it’s forwarded using the CEF tables in router A.

Creation of an MPLS TE tunnel

The network operator might decide to create an MPLS TE tunnel between routers A and D to utilize the alternate path A-B-C-D.

MPLS TE tunnel is created on router A

MPLS TE tunnel is created on router A

After the tunnel is created and the LSP from A to D is established, the tunnel interface state changes to up/up, but the tunnel is not yet used to forward the data traffic. The SPF tree in router A is not modified and although the tunnel is operational, it’s not used by the routing algorithm (IS-IS or OSPF) as there’s no router-to-router adjacency established over it.

MPLS TE tunnel is ignored by the SPF algorithm

MPLS TE tunnel is ignored by the SPF algorithm

You cannot establish a routing protocol adjacency across an MPLS TE tunnel as it’s a unidirectional path; the tail-end router has no means of sending the hello packets across the same LSP-based point-to-point link. You can, however, add the MPLS TE tunnel as a link in the IGP topology database with the MPLS TE Forwarding Adjacency functionality.

MPLS TE tunnel with autoroute

However, once the network operator enables autoroute functionality on the newly-created MPLS TE tunnel, the SPF algorithm uses the MPLS TE tunnel in its path calculation. After the SPF tree is built on router A, the path A-E-D is replaced by a direct link (MPLS TE tunnel) from A to D. From the perspective of router A, router D and all destinations beyond it reachable solely through the MPLS TE tunnel.

Autoroute MPLS TE tunnel is inserted in the SPF tree

Autoroute MPLS TE tunnel is inserted in the SPF tree

The MPLS TE tunnel replaces the original path computed by the SPF algorithm; after the autoroute is enabled, all the traffic from A to D flows through the MPLS TE tunnel established on the path A-B-C-D.

If you want to load-share the traffic between A and D across both paths (A-E-D and A-B-C-D), you have to create two MPLS TE tunnels between A and D. Multiple MPLS TE tunnels with the same tail-end LSR are inserted in the SPF tree and consequently used in the IP routing table.
Add comment
Sidebar