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.
The Multiprotocol Label Switching (MPLS) Transport Profile (TP) enables you to create tunnels that provide the transport network service layer over which IP and MPLS traffic traverse. MPLS-TP tunnels enable a transition from Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) time-division multiplexing (TDM) technologies to packet switching to support services with high bandwidth requirements, such as video.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
MPLS-TP tunnels provide the transport network service layer over which IP and MPLS traffic traverse. MPLS-TP tunnels help transition from SONET/SDH TDM technologies to packet switching to support services with high bandwidth utilization and lower cost. Transport networks are connection oriented, statically provisioned, and have long-lived connections. Transport networks usually avoid control protocols that change identifiers (like labels). MPLS-TP tunnels provide this functionality through statically provisioned bidirectional label switched paths (LSPs), as shown in the figure below.
MPLS-TP LSPs support 1-to-1 path protection. You can configure the working and protect LSPs as part of configuring the MPLS-TP tunnel. The working LSP is the primary LSP used to route traffic. The protect LSP is a backup for a working LSP. If the working LSP fails, traffic is switched to the protect LSP until the working LSP is restored, at which time forwarding reverts back to the working LSP.
MPLS-TP LSPs are bidirectional and co-routed and are comprised of two unidirectional LSPs that are supported by the MPLS forwarding infrastructure. A TP tunnel consists of a pair of unidirectional tunnels providing a bidirectional LSP. Each unidirectional tunnel can optionally be protected with a protect LSP that activates automatically upon failure conditions.
Several OAM protocols and messages support the provisioning and maintenance of MPLS-TP tunnels and bidirectional LSPs:
G-ACh/GAL is used to support in-band OAMs of MPLS LSPs and PWs. The OAM messages are used for fault management, connection verification, continuity check and other functions.
The following OAM messages are forwarded along the specified MPLS LSP:
The following messages are forwarded along the specified PW:
MPLS-TP supports the following combinations of static and dynamic multisegment pseudowires:
MPLS-TP supports one-to-one L2VPN pseudowire redundancy for the following combinations of static and dynamic pseudowires:
With static pseudowires, status notifications can be provided by BFD over VCCV or static pseudowire OAM protocol. However, BFD over VCCV sends only attachment circuit status code notifications. Hop-by-hop notifications of other pseudowire status codes are not supported. Therefore, static pseudowire OAM protocol is preferred. You can acquire per pseudowire OAM for attachment circuit/pseudowire notification over VCCV channel with or without the control word.
MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual interfaces are not supported for MPLS-TP link numbers.
The MPLS-TP link is used to create a level of indirection between the MPLS-TP tunnel and midpoint LSP configuration and the physical interface. The mpls tp linkcommand is used to associate an MPLS-TP link number with a physical interface and next-hop node. On point-to-point interfaces or Ethernet interfaces designated as point-to-point using the medium p2p command, the next-hop can be implicit, so the mpls tp linkcommand just associates a link number to the interface.
Multiple tunnels and LSPs may then refer to the MPLS-TP link to indicate they are traversing that interface. You can move the MPLS-TP link from one interface to another without reconfiguring all the MPLS-TP tunnels and LSPs that refer to the link.
Link numbers must be unique on the router or node.
See Configuring MPLS-TP Links and Physical Interfaces for more information.
Tunnel LSPs, whether endpoint or midpoint, use the same identifying information. However, it is entered differently.
You must specify a static range of MPLS labels using the mpls label rangecommand with the statickeyword.
The bfd-template command allows you to create a BFD template and enter BFD configuration mode. The template can be used to specify a set of BFD interval values. You invoke the template as part of the MPLS-TP tunnel. On platforms that support the BFD Hardware Offload feature and can provide 60-ms cutover for MPLS-TP tunnels, it is recommended to use the higher resolution timers in the BFD template.
When you create the pseudowire class, you specify the parameters of the pseudowire, such as the use of the control word, preferred path, OAM class, and VCCV BFD template.
On the endpoint routers, create an MPLS TP tunnel and configure its parameters. See the interface tunnel-tpcommand for information on the parameters.
Note |
When configuring the LSPs at the midpoint routers, make that the configuration does not reflect traffic back to the originating node. |
MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual interfaces are not supported for MPLS-TP link numbers.
When you configure static-to-dynamic pseudowires, you configure the static pseudowire class with the protocol none command, create a dynamic pseudowire class, then invoke those pseudowire classes with the neighbor commands.
l2 vfi atom point-to-point (static-dynamic MSPW) neighbor 10.116.116.116 4294967295 pw-class dypw (dynamic) neighbor 10.111.111.111 123 pw-class stpw (static) mpls label 101 201 mpls control-word local interface 4 tlv mtu 1 4 1500 tlv description 3 6 str abcd tlv descr C 4 hexstr 0505
Perform the following steps to configure the L2VPN pseudowire redundancy for static multisegment pseudowires that are backed up with static or dynamic multisegment pseudowires.
interface Ethernet1/0 no ip address no shutdown service instance 1 ethernet encapsulation dot1q 10 xconnect 10.113.113.113 123 encapsulation mpls manual pw-class stpw mpls label 0 101 mpls control-word backup peer 1 0.120.120.120 124 pw-class stpw mpls label 0 105 mpls control-word
When the entire tunnel is programmed, use the following commands to verify and help troubleshoot the configuration:
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
MPLS commands |
Cisco IOS MPLS Command Reference |
Standard |
Title |
---|---|
draft-ietf-mpls-tp-gach-gal-xx |
MPLS Generic Associated Channel |
MIB |
MIBs Link |
---|---|
None |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFC |
Title |
---|---|
RFC 5921 |
A Framework for MPLS in Transport Networks |
RFC 5885 |
Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV) |
RFC 5586 |
MPLS Generic Associated Channel |
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for MPLS-TP |
Feature Name | Releases | Feature Information |
---|---|---|
MPLS Transport Profile |
15.1(1)SA 15.3(1)S Cisco IOS XE Release 3.5S |
MPLS Transport Profile (TP) enables you to create tunnels that provide the transport network service layer over which IP and MPLS traffic traverse. MPLS-TP tunnels enable a transition from Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) time-division multiplexing (TDM) technologies to packet switching to support services with high bandwidth requirements, such as video. In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. The following commands were introduced or modified: debug mpls l2transport static-oam, debug mpls tp, interface tunnel-tp interval local interface logging (MPLS-TP) medium p2p mpls tp mpls tp link mpls tp lsp ping mpls tp pseudowire-static-oam class pseudowire-tlv template show mpls l2transport static-oam show mpls tp status protocol notification static timeout refresh tlv tlv template trace mpls tp |
L2VPN Static to Dynamic PW Interconnection & PW Preferred Path for MPLS-TP Tunnels |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS-TP: PW Redundancy for Static PWs |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
Bidirectional MPLS-TP LSP |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS-TP Path Protection |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS-TP OAM: GACH |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS-TP OAM: Continuity Check via BFD |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS-TP OAM: Ping/Trace |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS-TP OAM: Fault Management |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
MPLS TP: IP-less configuration of MPLS TP tunnels |
Cisco IOS XE Release 3.5S |
In Cisco IOS XE Release 3.5S, support was added for the Cisco ASR 903 Router. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.