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 MPLS Traffic Engineering—LSP Attributes feature requires that you configure an MPLS TE tunnel before you configure either an LSP Attribute List or a Path Option for Bandwidth Override feature.
Reoptimization between path options with different priorities is not supported.
With the LSP Attribute List feature, you need to configure priority for path options that is consistent with the priority configured on the tunnel or in other path options used by the tunnel.
The following section provides information about MPLS Traffic Engineering—LSP Attributes.
This document describes how to configure label switched path (LSP) attributes for path options associated with Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels.
The MPLS Traffic Engineering—LSP Attributes feature is an extension to MPLS TE. It provides an LSP Attribute list feature and a Path Option for Bandwidth Override feature. These features provide flexibility in the configuration of LSP attributes for MPLS TE tunnel path options. Several LSP attributes can be applied to path options for TE tunnels using an LSP attribute list. If bandwidth is the only LSP attribute you require, then you can configure a Path Option for Bandwidth Override.
The MPLS Traffic Engineering—LSP Attributes feature provides an LSP Attribute List feature and a Path Option for Bandwidth Override feature. These features have the following benefits:
The LSP Attributes List feature enables you to configure values for several LSP-specific path options for TE tunnels.
One or more TE tunnels can specify specific path options by referencing an LSP Attribute List.
LSP attribute lists make the MPLS TE user interface more flexible, easier to use, and easier to extend and maintain.
The Path Option for Bandwidth Override feature provides a single command that allows a TE tunnel to fall back temporarily to path options that can reduce bandwidth constraints.
MPLS traffic engineering allows constraint-based routing (CBR) of IP traffic. One of the constraints satisfied by CBR is the availability of required bandwidth over a selected path. Regular TE tunnel bandwidth is called the global pool. Subpool bandwidth is a portion of the global pool. If the subpool bandwidth is not in use it is not reserved from the global pool. Therefore, subpool tunnels require a higher priority than other tunnels.
You can configure the LSP Attribute bandwidth path option to use either global pool (default) or subpool bandwidth. The bandwidth value for the path option may be any valid value. The pool does not have to be the same as that configured on the tunnel.
 Note |
When you configure bandwidth for path options with the bandwidth [global] kbps command, use either all subpool bandwidths or all global-pool bandwidths. |
You can configure bandwidth on both dynamic and explicit path options using either the LSP Attribute List feature or the Path Option for Bandwidth Override feature. The commands that enable these features are exclusive of each other. If bandwidth is the only LSP attribute that you need to set on the path option, then use the command to enable the feature. This is the simplest way to configure multiple path options with decreasing bandwidth constraints. Once the bandwidth keyword is entered on the tunnel mpls traffic-eng path-option command in interface configuration mode, you cannot configure an LSP Attribute List for that path option.
Cisco IOS XE tunneling interfaces have many parameters associated with MPLS TE. Typically, you configure these parameters with tunnel mpls traffic-eng commands in interface configuration mode. Many of these commands determine tunnel-specific properties, such as the load-sharing factor for the tunnel. These commands configure parameters that are unrelated to the particular LSP in use by the tunnel. However, some of the tunneling parameters apply to the LSP that the tunnel uses. You can configure the LSP-specific properties using an LSP Attribute list.
An LSP Attribute list can contain values for each LSP-specific parameter that is configurable for a TE tunnel. You configure an LSP attribute list with the mpls traffic-eng lsp attributes string command, where string identifies the attribute list. The LSP attributes that you can specify include the following:
Attribute flags for links that make up the LSP (affinity command)
LSP bandwidth--global pool or subpool (bandwidth command)
Disable reoptimization of the LSP (lockdown command)
LSP priority (priority command)
Record the route used by the LSP (record-route command)
The MPLS Traffic Engineering—LSP Attributes feature also provides commands that help you manage LSP Attribute lists. You can do the following:
Relist all attribute list entries (list command)
Remove a specific attribute from the list (no attribute command)
The exit command exits from the LSP attributes configuration submode and returns you to global configuration mode.
Based on your requirements, you can configure LSP attributes lists with different sets of attributes for different path options. LSP attribute lists also provide an easy way to configure multiple TE tunnels to use the same LSP attributes. That is, you can reference the same LSP attribute list to configure LSP-specific parameters for one or more TE tunnels.
MPLS traffic engineering automatically establishes and maintains LSPs across the backbone by using the Resource Reservation Protocol (RSVP). The path that an LSP uses is determined by the LSP resource requirements and network resources, such as bandwidth. Traffic engineering tunnels are calculated at the LSP head based on a fit between required and available resources (constraint-based routing).
Without the Path Option for Bandwidth Override feature, a TE tunnel establishes an LSP based on dynamic or explicit path options in order of preference. However, the bandwidth and other attributes configured on the TE tunnel allow the setup of an LSP only if LSP path options satisfy the constraints. If a path cannot be found that satisfies the configured path options, then the tunnel is not set up.
The Path Option for Bandwidth Override feature provides a fallback path option that allows overriding the bandwidth configured on the TE tunnel interface. For example, you can configure a path option that sets the bandwidth to zero (0) effectively removing the bandwidth constraint imposed by the constraint-based routing calculation.
Reoptimization occurs when a device with traffic engineering tunnels periodically examines tunnels with established LSPs to learn if better LSPs are available. If a better LSP seems to be available, the device attempts to signal the better LSP. If the signaling is successful, the device replaces the older LSP with the new, better LSP.
Reoptimization can be triggered by a timer, the issuance of an mpls traffic-eng reoptimize command, or a configuration change that requires the signalling of a tunnel. The MPLS AutoBandwidth feature, for example, uses a timer to set the frequency of reoptimization based on the bandwidth path option attribute. The Path Option for Bandwidth Override feature allows for the switching between bandwidth configured on the TE tunnel interface and bandwidth configured on a specific path option. This increases the success of signaling an LSP for the TE tunnel.
With bandwidth override configured on a path option, the traffic engineering software attempts to reoptimize the bandwidth every 30 seconds to reestablish the bandwidth configured on the tunnel (see the Configuring a Path Option for Bandwidth Override section).
You can disable reoptimization of an LSP with the lockdown command in an LSP Attribute list. You can apply the LSP Attribute list containing the lockdown command to a path option with the tunnel mpls traffic-eng path-option command.
Note |
When you configure bandwidth for path options with the bandwidth [global ] kpbs command, use either all subpool bandwidths or all global-pool bandwidths. Do not mix subpool and other bandwidths, otherwise the path option does not reoptimize later. |
The Path Option for Bandwidth Override feature allows you to configure bandwidth parameters on a specific path option. The tunnel mpls traffic-eng path-option command's bandwidth keyword can be used for this purpose. When an LSP is signaled using a path option with a configured bandwidth, the bandwidth associated with the path option is signaled instead of the tunnel's configured bandwidth.
This feature also provides the ability to configure multiple path options that reduce the bandwidth constraint each time the headend of a tunnel fails to establish an LSP.
The following configuration uses the tunnel mpls traffic-eng bandwidth command to configure the bandwidth of the tunnel and three tunnel mpls traffic-eng path-option commands that define the signalling path options for the LSP:
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 1 explicit name path1
tunnel mpls traffic-eng path-option 2 explicit name path2 bandwidth 500
tunnel mpls traffic-eng path-option 3 dynamic bandwidth 0
The device selects a path option for an LSP in order of preference, as follows:
The device attempts to signal an LSP using path options starting with path option 1.
The device attempts to signal an LSP with the 1000 kbps bandwidth configured on the tunnel interface because path-option 1 has no bandwidth configured.
If 1000 kbps bandwidth is not available over the network, the device attempts to establish an LSP using path-option 2.
Path option 2 has a bandwidth of 500 kbps configured. This reduces the bandwidth constraint from the original 1000 kbps configured on the tunnel interface.
If 500 kbps is not available, the device attempts to establish an LSP using path-option 3.
Path-option 3 is configured as dynamic and has bandwidth 0. The device establishes the LSP if an IP path exists to the destination and all other tunnel constraints are met.
Values for path option attributes for a TE tunnel are determined in this manner:
LSP attribute list values referenced by the path option take precedence over the values configured on the tunnel interface.
If you do not specify an attribute in the LSP attribute list, the device uses the attribute in the tunnel configuration. LSP attribute lists do not have defaults.
If you do not configure the attribute on the tunnel, then the device uses the tunnel default value, as follows:
{Affinity= affinity 0 mask 0,
Bandwidth= bandwidth 0,
Lockdown= no lockdown,
Priority= priority 7 7,
Record-route= no record-route
.
.
.
}
The following section provides information on configuring MPLS Traffic Engineering—LSP Attributes.
Perform this task to configure a label switched path (LSP) attribute list with the desired attributes to be applied on a path option. Based on your requirements, you can configure LSP attributes lists with different sets of attributes for different path options. The LSP attribute list provides a user interface that is flexible, easy to use, and easy to extend and maintain for the configuration of MPLS TE tunnel path options.
LSP attribute lists also provide an easy way to configure multiple TE tunnels to use the same LSP attributes. That is, you can reference the same LSP attribute list to configure LSP-specific parameters for one or more TE tunnels.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
mpls traffic-eng lsp attributes string Example: |
Configures an LSP attribute list and enters LSP Attributes configuration mode.
|
|
Step 4 |
affinity value [mask value ] Example: |
(Optional) Specifies attribute flags for links comprising an LSP.
|
|
Step 5 |
bandwidth [global ]kbps Example: |
(Optional) Specifies LSP bandwidth.
|
|
Step 6 |
list Example: |
(Optional) Displays the contents of the LSP attribute list. |
|
Step 7 |
lockdown Example: |
(Optional) Disables reoptimization of the LSP. |
|
Step 8 |
priority setup-priority [hold-priority ] Example: |
(Optional) Specifies the LSP priority.
|
|
Step 9 |
record-route Example: |
(Optional) Records the route used by the LSP. |
|
Step 10 |
no sub-command Example: |
(Optional) Removes a specific attribute from the LSP attributes list.
|
|
Step 11 |
exit Example: |
(Optional) Exits from LSP Attributes configuration mode. |
|
Step 12 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
Perform this task to add attributes to an LSP attribute list. The LSP attribute list provides a user interface that is flexible, and easy to use. You can extend or change the LSP attribute list at any time to meet the requirements of your MPLS TE tunnel traffic. LSP Attributes configuration mode is used to display the specific LSP attributes list and to add or change the required path option attribute.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
mpls traffic-eng lsp attributes string Example: |
Configures an LSP Attribute list and enters LSP Attributes configuration mode.
|
|
Step 4 |
affinity value [mask value ] Example: |
(Optional) Specifies attribute flags for links comprising an LSP.
|
|
Step 5 |
bandwidth [ global ] kbps Example: |
Specifies an LSP bandwidth.
|
|
Step 6 |
priority setup-priority [hold-priority ] Example: |
Specifies the LSP priority.
|
|
Step 7 |
list Example: |
(Optional) Displays the contents of the LSP attribute list.
|
|
Step 8 |
exit Example: |
(Optional) Exits LSP Attributes configuration mode. |
|
Step 9 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
The following example shows how to remove the priority attribute from the LSP attribute list identified by the string 'simple'.
Device(config)# mpls traffic-eng lsp attributes simple
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# list
LIST simple
priority 1 1
!
Device(config-lsp-attr)# no priority
Device(config-lsp-attr)# list
LIST simple
!
Device(config-lsp-attr)# exit
Perform this task to modify an attribute in an LSP attribute list. The LSP attribute list provides a flexible user interface. You can extend or modifiy the LSP attribute list any time to meet the requirements of your MPLS TE tunnel traffic. LSP Attributes configuration mode is used to display the specific LSP attributes list and to modify the required path option attribute.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
mpls traffic-eng lsp attributes string Example: |
Configures an LSP Attribute list and enters LSP Attributes configuration mode.
|
|
Step 4 |
affinity value [mask value ] Example: |
Specifies attribute flags for links comprising an LSP.
|
|
Step 5 |
list Example: |
(Optional) Displays the contents of the LSP Attribute list.
|
|
Step 6 |
affinity value [mask value ] Example: |
Specifies attribute flags for links comprising an LSP.
|
|
Step 7 |
list Example: |
(Optional) Displays the contents of the LSP attribute list.
|
|
Step 8 |
exit Example: |
(Optional) Exits LSP Attributes configuration mode. |
|
Step 9 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
Perform this task to delete an LSP attribute list. You would perform this task when you no longer require the LSP attribute path options specified in the LSP attribute list for an MPLS TE tunnel.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
no mpls traffic-eng lsp attributes string Example: |
Removes a specified LSP Attribute list from the device configuration.
|
|
Step 4 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
|
Step 5 |
show mpls traffic-eng lsp attributes [string] Example: |
(Optional) Displays information about configured LSP attribute lists.
|
To verify the attributes within an LSP attribute list, perform this procedure.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
mpls traffic-eng lsp attributes string list Example: |
Enters LSP Attributes configuration mode. Verifies the contents for a specific LSP attribute list. |
|
Step 4 |
exit Example: |
Exits LSP Attributes configuration mode. |
|
Step 5 |
end Example: |
Exits to privileged EXEC mode. |
Perform this task to verify all configured LSP attribute lists. Use this task to display all LSP attribute lists to verify that the attributes lists that you configured are in operation.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
show mpls traffic-eng lsp attributes string [details] Example: |
Displays all configured LSP attribute lists. |
|
Step 3 |
show running-config | begin text-string Example: |
Verifies that all configured LSP attribute lists are as expected. The begin command modifier with thempls traffic-eng lsp text-string locate the LSP attributes information in the configuration file. |
|
Step 4 |
exit Example: |
Exits to user EXEC mode. |
Perform this task to associate an LSP attribute list with a path option for an MPLS TE tunnel. This task is required if you want to apply the LSP attribute list that you configured to path options for your MPLS TE tunnels.
Based on your requirements, you can configure LSP attributes lists with different sets of attributes for different path options. LSP attribute lists also provide an easy way to configure multiple TE tunnels to use the same LSP attributes. That is, you can reference the same LSP attribute list to configure LSP-specific parameters for one or more TE tunnels.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface type number Example: |
Configures an interface type and enters interface configuration mode.
|
||
|
Step 4 |
tunnel destination {hostname | ip-address } Example: |
Specifies the destination of the tunnel for this path option.
|
||
|
Step 5 |
tunnel mode mpls traffic-eng Example: |
Sets the encapsulation mode for the tunnel for MPLS TE. |
||
|
Step 6 |
tunnel mpls traffic-eng autoroute announce Example: |
Specifies that the IGP should use the tunnel (if the tunnel is up) in its enhanced shortest path first (SPF) calculation. |
||
|
Step 7 |
tunnel mpls traffic-eng bandwidth [|global ] bandwidth Example: |
Configures the bandwidth required for an MPLS TE tunnel and assigns it either to the subpool or the global pool.
|
||
|
Step 8 |
tunnel mpls traffic-eng priority setup-priority [hold-priority ] Example: |
Sets the priority to be used when the system determines which existing tunnels are eligible to be preempted.
Valid values are from 0 through 7. A lower number indicates a higher priority. An LSP with a setup priority of 0 can preempt any LSP with a non-0 priority.
Valid values are from 0 through 7, where a lower number indicates a higher priority. |
||
|
Step 9 |
tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | path-number } [verbatim ]} [attributes string ] [bandwidth [ global ] kbps ] [lockdown ] Example: |
Adds an LSP attribute list to specify LSP-related parameters for a path option for an MPLS TE tunnel.
|
||
|
Step 10 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
Perform this task to modify the path option to use a different LSP Attribute list.
Based on your requirements, you can configure LSP attributes lists with different sets of attributes for different path options. You can change the set of attributes associated with a path option. The tunnel mpls traffic-eng path-option number dynamic attributes string command is used in interface configuration mode to modify the path option to use a different LSP attribute list. The attributes and string keyword and argument names the new LSP attribute list for the path option specified.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface type number Example: |
Configures the interface type and enters interface configuration mode.
|
||
|
Step 4 |
tunnel destination {hostname | ip-address } Example: |
Specifies the destination of the tunnel for this path option.
|
||
|
Step 5 |
tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | path-number } [verbatim ]} [attributes string ] [bandwidth [ global ] kbps ] [lockdown ] Example: |
Adds an LSP Attribute list to specify LSP-related parameters for a path option for an MPLS TE tunnel.
|
||
|
Step 6 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
Perform this task to remove a path option for an LSP for an MPLS TE tunnel. Use this task to remove a path option for an LSP when your MPLS TE tunnel traffic requirements change.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface type number Example: |
Configures the interface type and enters interface configuration mode.
|
||
|
Step 4 |
tunnel destination {hostname | ip-address } Example: |
Specifies the destination of the tunnel for this path option.
|
||
|
Step 5 |
no tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | path-number } [verbatim ]} [attributes string ] [bandwidth [ global ] kbps ] [lockdown ] Example: |
Removes an LSP Attribute list that specifies LSP-related parameters for a path option for an MPLS TE tunnel.
|
||
|
Step 6 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
To verify that the LSP is signaled using the correct attributes for the specifed tunnel, perform this procedure.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
show mpls traffic-eng tunnels tunnel-interface [brief ] Example: |
Verifies that the LSP is signaled using the correct attributes for the specified tunnel. |
|
Step 3 |
exit Example: |
Use this command to return to user EXEC mode. For example: |
The following section contains the tasks for configuring a path option for bandwidth override.
Note |
Once you configure bandwidth as a path-option parameter, you can no longer configure an LSP Attribute list as a path-option parameter. |
Perform this task to configure fallback bandwidth path options for a TE tunnel. Use this task to configure path options that reduce the bandwidth constraint each time the headend of a tunnel fails to establish an LSP.
Configuration of the Path Option for Bandwidth Override feature can reduce bandwidth constraints on path options temporarily. It improves the chances that an LSP is set up for the TE tunnel. When a TE tunnel uses a path option with bandwidth override, the traffic engineering software attempts every 30 seconds to reoptimize the tunnel to use the preferred path option with the original configured bandwidth. The Path Option for Bandwidth Override feature is designed as a temporary reduction in bandwidth constraint. To force immediate reoptimization of all traffic engineering tunnels, you can use the mpls traffic-eng reoptimize command. You can also configure the lockdown command with bandwidth override to prevent automatic reoptimization.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface type number Example: |
Configures an interface type and enters interface configuration mode.
|
||
|
Step 4 |
tunnel destination {hostname | ip-address } Example: |
Specifies the destination of the tunnel for this path option.
|
||
|
Step 5 |
tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | path-number } [verbatim ]} [attributes string ] [bandwidth [ global ] kbps ] [lockdown ] Example: |
Adds a Path Option for Bandwidth Override to specify a bandwidth fallback for a path option for an MPLS TE tunnel.
|
||
|
Step 6 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
Perform this task to modify the bandwidth on a Path Option for Bandwidth Override. You might need to further reduce or modify the bandwidth constraint for a path option to ensure that the headend of a tunnel establishes an LSP.
The Path Option for Bandwidth Override feature is designed as a temporary reduction in bandwidth constraint. To force immediate reoptimization of all traffic engineering tunnels, you can use the mpls traffic-eng reoptimize command. You can also configure the lockdown command with bandwidth override to prevent automatic reoptimization.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface type number Example: |
Configures the interface type and enters interface configuration mode.
|
||
|
Step 4 |
tunnel destination {hostname | ip-address } Example: |
Specifies the destination of the tunnel for this path option.
|
||
|
Step 5 |
tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | path-number } [verbatim ]} [attributes string ] [bandwidth [global ] kbps ] [lockdown ] Example:Example: |
Adds a Path Option for Bandwidth Override to specify a bandwidth fallback for a path option for an MPLS TE tunnel.
|
||
|
Step 6 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
||
|
Step 7 |
show mpls traffic-eng tunnels tunnel-interface [brief ] Example: |
(Optional) Displays information about tunnels.
|
Perform this task to remove the bandwidth on the path option for bandwidth override. The Path Option for Bandwidth Override feature is designed as a temporary reduction in bandwidth constraint. Use this task to remove the bandwidth override when it is not required.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface tunnel number Example: |
Configures a tunnel interface type and enters interface configuration mode.
|
||
|
Step 4 |
tunnel destination {hostname | ip-address } Example: |
Specifies the destination of the tunnel for this path option.
|
||
|
Step 5 |
no tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-name | path-number } [verbatim ]} [attributes string ] [bandwidth [ global ] kbps ] [lockdown ] Example: |
Removes a path option for bandwidth override that specifies a bandwidth fallback for a path option for an MPLS TE tunnel.
|
||
|
Step 6 |
end Example: |
(Optional) Exits to privileged EXEC mode. |
||
|
Step 7 |
show mpls traffic-eng tunnels tunnel-interface [brief ] Example: |
(Optional) Displays information about tunnels.
|
To verify that the LSP is signaled using the correct bandwidth, perform this procedure.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password, if prompted. |
|
Step 2 |
show mpls traffic-eng tunnels tunnel-interface [brief ] Example: |
Verifies that the LSP is signaled with the correct bandwidth. Overrides the bandwidth configured on the tunnel. If bandwidth override is actively being signaled, the show mpls traffic-eng tunnel command displays the bandwidth override information under the Active Path Option Parameters heading. The example shows that BandwidthOverride is enabled and that the tunnel is signaled using path-option 2. The bandwidth signaled is 500. This is the value configured on the path option 2 and it overrides the 1000 kbps bandwidth configured on the tunnel interface. |
|
Step 3 |
exit Example: |
Use this command to exit to user EXEC mode. For example: |
The following section provides configuration examples for configuring MPLS Traffic Engineering—LSP Attributes.
This example shows the configuration of the affinity and bandwidth LSP-related attributes in an LSP attribute list identified with the numeral 1.
Device(config)# mpls traffic-eng lsp attributes 1
Device(config-lsp-attr)# affinity 7 mask 7
Device(config-lsp-attr)# bandwidth 1000
Device(config-lsp-attr)# exit
This example shows the addition of priority attributes to the LSP attribute list identified with the numeral 1.
Device(config)# mpls traffic-eng lsp attributes 1
Device(config-lsp-attr)# affinity 7 mask 7
Device(config-lsp-attr)# bandwidth 1000
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# exit
The following example shows how to remove the priority attribute from the LSP attribute list identified by the string 'simple'.
Device(config)# mpls traffic-eng lsp attributes simple
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# list
LIST simple
priority 1 1
!
Device(config-lsp-attr)# no priority
Device(config-lsp-attr)# list
LIST simple
!
Device(config-lsp-attr)# exit
The following example shows how to modify the bandwidth in an LSP attribute list identified by the numeral 5.
Device(config)# mpls traffic-eng lsp attributes 5
Device(config-lsp-attr)# bandwidth 1000
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# list
LIST 5
bandwidth 1000
priority 1 1
Device(config-lsp-attr)# bandwidth 500
Device(config-lsp-attr)# list
LIST 5
bandwidth 500
priority 1 1
Device(config-lsp-attr)# exit
The following example shows how to delete an LSP attribute list identified by the numeral 1.
Device(config)# mpls traffic-eng lsp attributes 1
Device(config-lsp-attr)# affinity 7 mask 7
Device(config-lsp-attr)# bandwidth 1000
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# exit
!
Device(config)# no mpls traffic-eng lsp attributes 1
The following example associates the LSP attribute list identified by the numeral 3 with path option 1.
Device(config)# mpls traffic-eng lsp attributes 3
Device(config-lsp-attr)# bandwidth 1000
Device(config-lsp-attr)# priority 2 2
Device(config-lsp-attr)# exit
!
!
Device(config)# interface Tunnel 1
Device(config-if)# ip unnumbered FastEthernet1/0/1
Device(config-if)# tunnel destination 10.112.0.12
Device(config-if)# tunnel mode mpls traffic-eng
Device(config-if)# tunnel mpls traffic-eng affinity 1
Device(config-if)# tunnel mpls traffic-eng bandwidth 5000
Device(config-if)# tunnel mpls traffic-eng path-option 1 dynamic attributes 3
In this configuration, the LSP has the following attributes:
{bandwidth = 1000
priority = 2 2
affinity 1
reroute enabled.
}
The LSP attribute list referenced by the path option takes precedence over the values configured on the tunnel interface.
The following example modifies path option 1 to use an LSP attribute list identified by the numeral 1.
Device(config)# mpls traffic-eng lsp attributes 1
Device(config-lsp-attr)# affinity 7 mask 7
Device(config-lsp-attr)# bandwidth 500
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# exit
Device(config)# mpls traffic-eng lsp attributes 2
Device(config-lsp-attr)# bandwidth 1000
Device(config-lsp-attr)# priority 1 1
Device(config-lsp-attr)# exit
Device(config)# interface Tunnel 1
Device(config-if)# ip unnumbered FastEthernet1/0/1
Device(config-if)# tunnel destination 10.112.0.12
Device(config-if)# tunnel mode mpls traffic-eng
Device(config-if)# tunnel mpls traffic-eng affinity 1
Device(config-if)# tunnel mpls traffic-eng bandwidth 5000
Device(config-if)# tunnel mpls traffic-eng path-option 1 dynamic attributes 1
In this configuration, the LSP has the following attributes:
{affinity = 7 mask = 7
bandwidth = 500
priority = 1 1
}The following example shows the removal of path option 1 for an LSP for a TE tunnel.
Device(config)# interface Tunnel 1
Device(config-if)# ip unnumbered FastEthernet1/0/1
Device(config-if)# tunnel destination 10.112.0.12
Device(config-if)# tunnel mode mpls traffic-eng
Device(config-if)# tunnel mpls traffic-eng affinity 1
Device(config-if)# tunnel mpls traffic-eng bandwidth 5000
Device(config-if)# tunnel mpls traffic-eng path-option 1 explicit path1 attributes 1
Device(config-if)# tunnel mpls traffic-eng path-option 2 explicit path2 attributes 2
!
!
Device(config-if)# no tunnel mpls traffic-eng path-option 1 explicit path1 attributes 1
The following examples show how to configure a path option to override the bandwidth:
Device(config-if)# tunnel mpls traffic-eng path-option 3 explicit name path1 ?
attributes Specify an LSP attribute list
bandwidth override the bandwidth configured on the tunnel
lockdown not a candidate for reoptimization
<cr>
Device(config-if)# tunnel mpls traffic-eng path-option 3 explicit name path1 bandwidth ?
<0-4294967295> bandwidth requirement in kbps
Device(config-if)# tunnel mpls traffic-eng path-option 3 explicit name path1 bandwidth 500 ?
lockdown not a candidate for reoptimization
<cr>
Note |
Once you configure bandwidth as a path-option parameter, you can no longer configure an LSP attribute list as a path-option parameter. |
The following example shows multiple path options configured with the tunnel mpls traffic-eng path-option command:
interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 10.10.10.12
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 1 explicit name path1
tunnel mpls traffic-eng path-option 2 explicit name path2 bandwidth 500
tunnel mpls traffic-eng path-option 3 dynamic bandwidth 0
end
The device selects a path option for an LSP in order of preference, as follows:
The device attempts to signal an LSP using path options starting with path-option 1.
The device attempts to signal an LSP with the 1000 kbps bandwidth configured on the tunnel interface because path-option 1 has no bandwidth configured.
If 1000 kbps bandwidth is not available over the network, the device attempts to establish an LSP using path-option 2.
Path-option 2 has a bandwidth of 500 kbps configured. This reduces the bandwidth constraint from the original 1000 kbps configured on the tunnel interface.
If 500 kbps is not available, the device attempts to establish an LSP using path-option 3.
Path-option 3 is configured as dynamic and has bandwidth 0. The device establishes the LSP if an IP path exists to the destination and all other tunnel constraints are met.
The following example shows modifying the bandwidth on a path option for bandwidth override. Path-option 3 is changed to an explicit path with a bandwidth of 100 kbps. Path-option 4 is configured with bandwidth 0.
interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 10.10.10.12
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 1 explicit name path1
tunnel mpls traffic-eng path-option 2 explicit name path2 bandwidth 500
tunnel mpls traffic-eng path-option 3 dynamic bandwidth 0
!
!
Device(config)# tunnel mpls traffic-eng path-option 3 explicit name path3 bandwidth 100
Device(config)# tunnel mpls traffic-eng path-option 4 dynamic bandwidth 0
The following example shows the removal of the bandwidth for path option 3 for an LSP for an MPLS TE tunnel:
interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 10.10.10.12
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 1 explicit name path1
tunnel mpls traffic-eng path-option 2 explicit name path2 bandwidth 500
tunnel mpls traffic-eng path-option 3 explicit name path3 bandwidth 100
tunnel mpls traffic-eng path-option 4 dynamic bandwidth 0
!
Router(config)# no tunnel mpls traffic-eng path-option 3 explicit name path3 bandwidth 100
|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
|
|
MPLS traffic engineering commands |
|
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. |
This table provides release and related information for the features explained in this module.
These features are available in all the releases subsequent to the one they were introduced in, unless noted otherwise.
|
Release |
Feature |
Feature Information |
|---|---|---|
| Cisco IOS XE Bengaluru 17.6.1 |
MPLS Traffic Engineering LSP Attributes |
The MPLS Traffic Engineering—LSP Attributes feature is an extension to MPLS TE that provides an LSP Attribute List feature and a Path Option for Bandwidth Override feature. These features provide flexibility in the configuration of LSP attributes for MPLS TE tunnel path options. Several LSP attributes can be applied to path options for TE tunnels using an LSP attribute list. If bandwidth is the only LSP attribute you require, then you can configure a Path Option for Bandwidth Override. |
|
Cisco IOS XE Cupertino 17.7.1 |
MPLS Traffic Engineering LSP Attributes |
This feature was implemented on Cisco Catalyst 9600 Series Supervisor 2 Module (C9600X-SUP-2). |
Use the Cisco Feature Navigator to find information about platform and software image support. To access Cisco Feature Navigator, go to https://cfnng.cisco.com/
Feedback