KINGSWAY, P.O.

BOX 1037, MASERU 100 LESOTHO

TEL 22 21 1000 * FAX 22 31 0183

MPLS TE Fast Reroute (FRR) link protection testing on ETL IP backbone

Background
With the current NG-SDH Subnetwork Connection Protection (SNCP 1+1 path protection)
mechanism we cannot have all MPLS links protected. This is because of limited resources on
the microwave radios paths of the NG-SDH network, especially on NYANE-BEP-MKB hops.
This document proposes the use of MPLS Traffic Engineering protection mechanisms for
protecting MPLS links
MPLS TE FRR link protection theory
Normal MPLS TE uses Resource Reservation Protocol (RSVP) to automatically establish and
maintain label-switched paths (LSPs) across a network. The route used by an LSP depends on
its resource requirements and available bandwidth resources. Available bandwidth resources
are flooded by links state protocols such as OSPF or IS-IS. Routes are computed by headend
router which also determine new route for the LSP upon failure. With this, headend cannot
recover fast enough (less than 50ms) to choose an alternative route for LSP to restore service.
MPLS TE Fast Reroute link protection provides recovery times less than or equal to 50ms. It
enables traffic carried by an LSP to be rerouted passed/around the failed route via an alternative
defined route. The rerouting decision is controlled locally by the router interfacing the failed route
and the headend is notified of the failure through links state routing protocol or RSVP. LSP
tunnels are switched to backup tunnel when the local router receives interface down notification
or RSVP Hello neighbor down notifications.
MPLS FRR link protection is also called Next-Hop link protection as it bypasses failed next failed
hop and it requires pre-signaled next hop backup tunnel/LSP. This signaling is done by RSVP.
Local router responsible for rerouting of LSP to backup route is called Point of Local repair while
the router where backup route joins primary is the merge point (HQ Point of Local repair (also
headend) and MQQ Merge Point (also tailend) in section below).
Procedure
i.

ii.

Prerequisites for MPLS TE FRR

Link state Internal Gateway Protocol (OSPF or IS-IS) running
MPLS enabled network running over Packet over SDH or using MPLS Global
Label Allocation
MPLS TE tunnels configured
Configuration steps
With link state IGP running, enable MPLS TE on all relevant routers and interfaces

Board Members: Mr. Pako Petlane (Chairman), Mr. Strive Masiyiwa, Mr. Douglas Mboweni (Alternate), Mrs. Tracy Mpofu, Mr. Craig Fitzgerald,
Mr. Bernard Fernandes, Mr. Tseliso Nteso, Mrs. Thato Nkhahle, Mr. Nico Heyns (Chief Executive Officer), Mr. Elia Madondo (Executive Director)

iii.

Configure or define MPLS TE tunnels

Enable MPLS TE Fast reroute on relevant routers interfaces
Configure or define MPLS TE backup tunnels
Assign backup tunnels to protected interfaces

Topology
The proposed topology on ETL MPLS network is below
MQQ PE
router

HQ P
router

BEP PE
router

The rest
PE
Routers

Define primary LSP/MPLS TE tunnel from HQ (headend) to MQQ (tailend), MPLS

TE tunnels are unidirectional
Define secondary/backup LSP or MPLS TE tunnel on HQ-BEP-MQQ routes
Please note that Provider router can either be HQ or Thetsane depending on
interface resources availability.
For this particular case it is proposed that we define static backup MPLS TE
tunnels for starters and do dynamic after successfully testing static one.