- New and Changed Information
- Preface
-
- Configuring the MPLS Label Distribution Protocol
- Configuring MPLS LDP Autoconfiguration
- Configuring MPLS LDP Session Protection
- Configuring MPLS LDP IGP Synchronization
- Configuring MPLS LDP Lossless MD5 Session Authentication
- Configuring MPLS LDP Label Filtering
- Configuring MPLS LDP Static Label Binding
- Configuring MPLS LDP Graceful Restart
-
- Configuring Basic MPLS TE
- Configuring Automatic Bandwidth Adjustment for MPLS TE Tunnels
- Configuring MPLS TE RSVP
- Configuring the Path Selection Metric for MPLS TE Tunnels
- Configuring LSP Attributes for MPLS TE
- Configuring MPLS TE Verbatim Paths
- Configuring MPLS TE Forwarding Adjacency
- Configuring MPLS TE Class-Based Tunnel Selection
- Configuring MPLS TE Path Protection
- Configuring MPLS TE Fast Reroute Link and Node Protection
-
- Configuring Any Transport over MPLS
- Configuring Any Transport over MPLS Pseudowire Provisioning
- Configuring Ethernet over MPLS
- Configuring EoMPLS Layer 2 VPN Graceful Restart
- Configuring Virtual Private LAN Service
- Configuring Layer 2 VPN Pseudowire Redundancy
- Configuring Layer 2 VPN VPLS Dual-Homing with a vPC
- Configuration Limits for Cisco NX-OS MPLS
- RFCs
- Finding Feature Information
- Information About MPLS TE
- Licensing Requirements for MPLS TE
- Prerequisites for MPLS TE
- Guidelines and Limitations for MPLS TE
- Default Settings for MPLS TE
- Configuring MPLS TE
- Verifying the MPLS TE Configuration
- Configuration Examples for MPLS TE
- Additional References for MPLS TE
- Feature History for MPLS TE
Configuring Basic MPLS TE
This chapter describes how to configure Multiprotocol Label Switching (MPLS) traffic engineering (TE) on Cisco NX-OS devices.
This chapter includes the following sections:
- Finding Feature Information
- Information About MPLS TE, page 11-1
- Licensing Requirements for MPLS TE, page 11-3
- Prerequisites for MPLS TE, page 11-3
- Guidelines and Limitations for MPLS TE, page 11-3
- Default Settings for MPLS TE, page 11-3
- Configuring MPLS TE, page 11-4
- Configuring MPLS TE, page 11-4
- Verifying the MPLS TE Configuration, page 11-12
- Configuration Examples for MPLS TE, page 11-13
- Additional References for MPLS TE, page 11-14
- Feature History for MPLS TE, page 11-15
Finding Feature Information
Your software release might not support all the features documented in this module. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your 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 “New and Changed Information” chapter or the Feature History table below.
Information About MPLS TE
MPLS enabled for traffic engineering makes traditional Layer 2 features available to Layer 3.
This section includes the following topics:
MPLS TE Operation
MPLS TE learns the topology and resources available in a network and then maps traffic flows to particular paths based on resource requirements and network resources such as bandwidth. MPLS TE builds a unidirectional tunnel from a source to a destination in the form of a label switched path (LSP), which is then used to forward traffic. The point where the tunnel begins is called the tunnel headend or tunnel source, and the node where the tunnel ends is called the tunnel tailend or tunnel destination.
MPLS uses extensions to a link-state based Interior Gateway Protocol (IGP), such as Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF). MPLS calculates TE tunnels at the LSP head based on required and available resources (constraint-based routing). If configured, the IGP automatically routes the traffic onto these LSPs. Typically, a packet that crosses the MPLS TE backbone travels on a single LSP that connects the ingress point to the egress point. MPLS TE automatically establishes and maintains the LSPs across the MPLS network by using the Resource Reservation Protocol (RSVP).
MPLS TE is built on the following Cisco NX-OS mechanisms:
- TE tunnel interfaces—From a Layer 2 standpoint, an MPLS TE tunnel interface represents the head of an LSP. It is configured with a set of resource requirements, such as bandwidth, media requirements, and priority. From a Layer 3 standpoint, a TE tunnel interface is the headend of a unidirectional virtual link to the tunnel destination.
- MPLS TE path calculation—This calculation, which operates at the LSP head, determines a path to use for an LSP. The path calculation uses a link-state database that contains flooded topology and resource information.
- Resource Reservation Protocol (RSVP) with TE extensions—RSVP, which operates at each LSP hop, is used to signal and maintain LSPs based on the calculated path.
- MPLS TE link management— Link management, which operates at each LSP hop, performs link call admission on the RSVP signaling messages and tracking of topology and resource information to be flooded.
- Link-state IGP (IS-IS or OSPF)—These IGPs (with TE extensions) globally flood topology and resource information based on link management.
- Enhancements to the SPF calculation used by the link-state IGP (IS-IS or OSPF)—If configured, the IGP automatically routes traffic onto the appropriate TE tunnel based on the tunnel destination. You can also use static routes to direct traffic onto TE tunnels.
- Label switching forwarding—This forwarding mechanism provides routers with a Layer 2-like ability to direct traffic across multiple hops of the LSP established by RSVP signaling.
MPLS TE and HA
MPLS TE supports these Cisco NX-OS high availability (HA) features:
MPLS TE supports these Cisco NX-OS HA technologies to allow NSF and Stateful HA:
Licensing Requirements for MPLS TE
Prerequisites for MPLS TE
MPLS TE has the following prerequisites:
- Your network must support Multiprotocol Label Switching (MPLS)
- Your network must support at least one of the following Interior Gateway (IGP) protocols:
Guidelines and Limitations for MPLS TE
MPLS TE has the following configuration guidelines and limitations:
- MPLS TE supports only a single IGP process or instance. You should not configure MPLS TE in more than one IGP process or instance.
- The IGP process or instance that you configure for MPLS TE must be one of the first four OSPFv2 or IS-IS processes or instances created. Cisco NX-OS Release 6.1 introduces support for more than four process instances for OSPFv2 per VDC. However, only the first four configured OSPFv2 instances are supported with MPLS TE.
- You cannot configure MPLS TE over the logical generic routing encapsulation (GRE) tunnel interface.
- MPLS TE is supported in no more than four VDCs.
Default Settings for MPLS TE
Table 11-1 lists the default settings for basic MPLS TE.
|
|
---|---|
Configuring MPLS TE
This section includes the following topics:
- Enabling MPLS TE
- Enabling MPLS TE, page 11-4
- Configuring OSPF for MPLS TE, page 11-6
- Configuring MPLS TE on an Interface, page 11-7
- Configuring an MPLS TE Tunnel, page 11-8
- Configuring an Explicit Path, page 11-10
Enabling MPLS TE
Prerequisites
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS
2. feature mpls traffic-engineering
DETAILED STEPS
|
|
|
---|---|---|
(Optional) Displays information about the running configuration. |
||
(Optional) Copies the running configuration to the startup configuration. |
Configuring IS-IS for MPLS TE
You can configure IS-IS for MPLS TE.

Note MPLS TE supports a single IGP process or instance. You should not configure MPLS TE in more than one IGP process or instance.
Prerequisites
You must have the MPLS TE feature enabled (see the “Configuring MPLS TE”).
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS

Note You can configure a router running IS-IS so that Protocol-Independent Multicast (PIM) and MPLS TE can work together with the mpls traffic-eng multicast-intact command. You can disable the interoperability between PIM and MPLS TE with the no mpls traffic-eng multicast-intact command.
4. mpls traffic-eng { level-1 | level-1-2 | level-2 }
5. mpls traffic-eng router-id interface
DETAILED STEPS
Configuring OSPF for MPLS TE
You can configure OSPF for MPLS TE.

Note MPLS TE supports a single IGP process or instance. You should not configure MPLS TE in more than one IGP process or instance.
Prerequisites
You must have the MPLS TE feature enabled (see the “Configuring MPLS TE”).
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS

Note You can configure a router running OSPF so that Protocol-Independent Multicast (PIM) and MPLS TE can work together with the mpls traffic-eng multicast-intact command. You can disable the interoperability between PIM and MPLS TE with the no mpls traffic-eng multicast-intact command.
4. mpls traffic-eng area area-id
5. mpls traffic-eng router-id interface
DETAILED STEPS
Configuring MPLS TE on an Interface
Prerequisites
You must have the MPLS TE feature enabled (see the “Configuring MPLS TE”).
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS
4. mpls traffic-eng bandwidth [ interface-kbps | percent percentage ]
DETAILED STEPS
Configuring an MPLS TE Tunnel
You can configure an MPLS TE tunnel with a preferred explicit path or a backup dynamic path option.

Note This configuration applies only to the TE headend node.
Prerequisites
You must have the MPLS TE feature enabled (see the “Configuring MPLS TE”).
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS
3. ip unnumbered type slot / port
5. (Optional) bandwidth bandwidth
6. path-option [ protect ] preference-number { dynamic | explicit { identifier id | name name} [ verbatim ]} [ lockdown ] [ bandwidth kbps] [ attributes listname]
7. (Optional) autoroute announce
DETAILED STEPS
Configuring an Explicit Path
You can configure an explicit LSP path on the headend router.
Prerequisites
You must have the MPLS TE feature enabled (see “Configuring MPLS TE”).
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS
2. mpls traffic-eng configuration
3. explicit-path { identifier id | name name }
4. [ index number ] { next-address [ loose | strict ] | exclude-address } address
5. Repeat step 4 for each router in the path.
DETAILED STEPS
Verifying the MPLS TE Configuration
To display the MPLS TE configuration, perform one of the following tasks:
For detailed information about the fields in the output from these commands, see the Cisco NX-OS MPLS Command Reference.
Configuration Examples for MPLS TE
This section includes the following configuration examples:
- Example: Enabling MPLS TE Using IS-IS, page 11-13
- Example: Enabling MPLS TE Using OSPF, page 11-13
- Example: Configuring MPLS TE on an Interface, page 11-14
- Example: Configuring an MPLS TE Tunnel, page 11-14
- Example: Creating an Explicit Path, page 11-14
Example: Enabling MPLS TE Using IS-IS
The following example shows how to enable MPLS TE with IS-IS routing:

Note You must enter the following commands on every router or switch in the traffic-engineered portion of your network.
Example: Enabling MPLS TE Using OSPF
The following example shows how to enable MPLS TE with OSPF routing:

Note You must enter the following commands on every router or switch in the traffic-engineered portion of your network.
Example: Configuring MPLS TE on an Interface
The following example shows how to configure TE on an interface:

Note The interface must be configured to be used by the IGP. In ISIS, you would have something like the following syntax:
ip router isis p1
Example: Configuring an MPLS TE Tunnel
The following example shows how to configure a TE tunnel:
Example: Creating an Explicit Path
The following example shows how to configure an explicit path:
Additional References for MPLS TE
For additional information related to implementing MPLS TE, see the following sections:
Related Document
|
|
---|---|
MIBs
|
|
---|---|
To locate and download Cisco MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Feature History for MPLS TE
Table 11-2 lists the release history for this feature.
|
|
|
---|---|---|