- Title
- New and Changed Information
- Preface
-
- 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 Path Protection
- Configuring MPLS TE Fast Reroute Link and Node Protection
- Configuration Limits for Cisco NX-OS MPLS
- RFCs
- Finding Feature Information
- Information About the Path Selection Metric for MPLS TE Tunnels
- Licensing Requirements for the Path Selection Metric for MPLS TE Tunnels
- Prerequisites for the Path Selection Metric for MPLS TE Tunnels
- Guidelines and Limitations for the Path Selection Metric for MPLS TE Tunnels
- Default Settings for the Path Selection Metric for MPLS TE Tunnels
- Configuring the Path Selection Metric for MPLS TE Tunnels
- Verifying the Path Selection Metric Configuration for MPLS TE Tunnels
- Configuration Examples for the Path Selection Metric for MPLS TE Tunnels
- Additional References for MPLS TE Tunnels
- Feature History for the Path Selection Metric for MPLS TE Tunnels
Configuring the Path Selection Metric for MPLS TE Tunnels
This chapter describes how to configure the path selection metric for Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels on Cisco NX-OS devices.
This chapter includes the following sections:
- Finding Feature Information
- Information About the Path Selection Metric for MPLS TE Tunnels, page 13-203
- Licensing Requirements for the Path Selection Metric for MPLS TE Tunnels, page 13-203
- Prerequisites for the Path Selection Metric for MPLS TE Tunnels, page 13-203
- Guidelines and Limitations for the Path Selection Metric for MPLS TE Tunnels, page 13-203
- Default Settings for the Path Selection Metric for MPLS TE Tunnels, page 13-204
- Configuring the Path Selection Metric for MPLS TE Tunnels, page 13-204
- Verifying the Path Selection Metric Configuration for MPLS TE Tunnels, page 13-207
- Configuration Examples for the Path Selection Metric for MPLS TE Tunnels, page 13-208
- Additional References for MPLS TE Tunnels, page 13-210
- Feature History for the Path Selection Metric for MPLS TE Tunnels, page 13-211
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 the Path Selection Metric for MPLS TE Tunnels
Certain tunnels carry voice traffic, which requires low delay, and other tunnels carry data.You can configure the path selection metric for TE tunnels on a global or per-tunnel basis. You can specify the TE link metric on an interface, or let it default to the IGP link metric. You can also specify the link metric for path selection for these low-delay traffic tunnels and let the other tunnels use the Interior Gateway Protocol (IGP) metric for path selection. MPLS TE supports Intermediate System-to-Intermediate System (IS-IS) and Open Shortest Path First (OSPF) as the IGP.
Prerequisites for the Path Selection Metric for MPLS TE Tunnels
The path selection metric for MPLS TE tunnels has the following prerequisites:
- You must enable MPLS TE on your device. See the “Configuring MPLS TE”.
Guidelines and Limitations for the Path Selection Metric for MPLS TE Tunnels
The path selection metric has the following configuration guidelines and limitations:
- Unless explicitly configured, the TE link metric (administrative-weight) for a given link is the IGP link metric. When the TE link metric is used to represent a link property that is different from the cost/distance, you must configure every network link that can be used for TE tunnels with a TE link metric that represents that property. Failure to do so might cause tunnels to use unexpected paths.
- You cannot configure MPLS TE over the logical generic routing encapsulation (GRE) tunnel interface.
- MPLS TE supports only a single IGP process or instance. Multiple IGP processes or instances are not supported and you should not configure MPLS TE in more than one IGP process or instance. You might configure MPLS TE in multiple OSPF areas or both IS-IS levels.
Default Settings for the Path Selection Metric for MPLS TE Tunnels
Table 13-1 lists the default settings for the path selection metric for MPLS TE tunnels.
Note Although both the global path selection metric and TE tunnel path selection metric default to TE, because the interface TE link metric defaults to the IGP link metric, the effective default configuration uses the IGP link metrics.
Configuring the Path Selection Metric for MPLS TE Tunnels
This section includes the following topics:
- Configuring the Global Path Selection Metric Type for MPLS TE Tunnels, page 13-204
- Configuring the Path Selection Metric Type for a TE Tunnel, page 13-205
Configuring the Global Path Selection Metric Type for MPLS TE Tunnels
You can configure the path selection to use either the IGP metric or the TE metric for all MPLS TE tunnels.
Note The configured TE tunnel interface path selection metric type takes precedence over the global path selection metric type.
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
2. mpls traffic-eng configuration
3. path-selection metric { igp | te }
4. (Optional) show mpls traffic-eng tunnels tunnel-te number
DETAILED STEPS
Configuring the Path Selection Metric Type for a TE Tunnel
You can override the global tunnel path selection metric on a per-TE tunnel interface, and you can also override the IGP link metric on any link by configuring the TE administrative weight on that link.
SUMMARY STEPS
3. path-selection metric { igp | te }
4. (Optional) interface type/ number
5. (Optional) mpls traffic-eng administrative-weight weight
6. (Optional) show mpls traffic-eng tunnels tunnel-te number
DETAILED STEPS
Verifying the Path Selection Metric Configuration for MPLS TE Tunnels
To display the path selection metric for MPLS TE tunnels, perform one of the following tasks:
Displays each link’s administrative weight and whether it was inherited from the IGP or is an override with the TE administrative weight. |
For detailed information about the fields in the output from these commands, see the Cisco NX-OS MPLS Command Reference .
Configuration Examples for the Path Selection Metric for MPLS TE Tunnels
The section shows how to configure the link metric type that you can use for the tunnel path selection and how to configure the link metrics. The configuration commands included in this section allow you to specify the metric type for path selection and assign metrics to links. Additional commands are required to fully configure the example scenario. For example, you need the IGP commands to continue TE and the link interface commands to enable TE and specify the available bandwidth.
The example in this section supports the simple network technology shown in Figure 13-1.
Note This example applies only to dynamic tunnels, not to ones with an explicit path.
In Figure 13-1, the topology shows the following:
- Tunnel1 and Tunnel2 connects from R1 (headend) to R4 (tailend).
- Tunnel3 connects from R1 to R5.
- The path selection for Tunnel1 and Tunnel3 should use a metric that represents a link delay because these tunnels carry voice traffic.
- The path selection for Tunnel2 should use IGP metrics because MPLS TE carries data traffic with no delay requirement.
The following configuration fragments for each of the routers show the configuration that relates to link metrics and their use in the tunnel path selection. TE metrics that represent a link delay must be configured for the network links on each of the routers, and the three tunnels must be configured on R1.
These configuration fragments force Tunnel1 to take path R1-R3-R4, Tunnel2 to take path R1-R2-R4, and Tunnel3 to take path R1-R3-R4-R5 (if the links have sufficient bandwidth to accommodate the tunnels).
Additional References for MPLS TE Tunnels
The following sections provide references related to the path selection metric for MPLS TE tunnels.
Feature History for the Path Selection Metric for MPLS TE Tunnels
Table 13-2 lists the release history for this feature.
Feedback