Implementing MPLS Transport Profile
How to Implement MPLS Transport Profile
traffic. Looping back traffic is carried out by the forwarding engine without control plane's involvement. The
label stack of a loopback packet will be modified such that the source of the traffic identifies the packet.
Figure 23: MPLS-TP LSP Wrapping Mechanism
When the forwarding engine at an end-point recognizes a packet from loopback traffic, it sforwards the packet
on protect LSP. As BFD packets over impacted LSPs are also looped-back, the end-point will drop such BFD
packets so that BFD sessions over the impacted LSPs is timed-out and protection switching is activated.
Optionally, when an end-point receives the first looped-back packet, it activates protection switching.
A working LSP remains wrapped until protection switching is activated. Once activated, protect LSP will
carry traffic as usual. When failure is removed and BFD session comes back up resulting in activation of
working LSP.
How to Implement MPLS Transport Profile
MPLS Transport Profile (MPLS-TP) supported by IETF enables the migration of transport networks to a
packet-based network that efficiently scale to support packet services in a simple and cost effective way.
These procedures are used to implement MPLS-TP:
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x
OL-28381-02
317