MPLS Traffic Engineering Commands on Cisco IOS XR Software
This chapter describes the commands that you will use to configure Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) and Generalized MPLS (GMPLS). In this chapter, all GMPLS-specific commands are identified with "(GMPLS)" in the command title.
Your network must support the following Cisco features before you can enable MPLS-TE:
•MPLS
•IP Cisco Express Forwarding (CEF)
•Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF) routing protocol
•Resource Reservation Protocol (RSVP)
MPLS Label Distribution Protocol (LDP), Resource Reservation Protocol (RSVP), and Universal Control Plane (UCP) command descriptions are documented separately.
For detailed information about MPLS concepts, configuration tasks, and examples, refer to
Cisco IOS XR MPLS Configuration Guide.
adjustment-threshold (MPLS-TE)
To configure the tunnel bandwidth change threshold to trigger an adjustment, use the adjustment-threshold command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.
adjustment-threshold percentage [min minimum bandwidth]
no adjustment-threshold percentage [min minimum bandwidth]
Syntax Description
percentage |
Bandwidth change percent threshold to trigger an adjustment if the largest sample percentage is higher or lower than the current tunnel bandwidth. Range is from 1 to 100 percent. The default value is 5 percent. |
min minimum bandwidth |
(Optional) Configures the bandwidth change value to trigger an adjustment. The tunnel bandwidth is changed only if the largest sample is higher or lower than the current tunnel bandwidth in kilobits per second (kbps). Range is from 10 to 4294967295. The default value is 10. |
Defaults
percentage: 10
minimum bandwidth: 10 kbps
Command Modes
MPLS-TE automatic bandwidth interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you configure or modify the adjustment threshold while the automatic bandwidth is already running, the next band-aids application is impacted for that tunnel. The new adjustment threshold determines if an actual bandwidth takes place.
Examples
The following example configures the tunnel bandwidth change threshold to trigger an adjustment:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# adjustment-threshold 20 min 500
Related Commands
admin-weight
To override the Interior Gateway Protocol (IGP) administrative weight (cost) of the link, use the admin-weight command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
admin-weight weight
no admin-weight weight
Syntax Description
weight |
Administrative weight (cost) of the link. Range is 0 to 4294967295. |
Defaults
weight: IGP Weight (default OSPF 1, ISIS 10)
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
To use MPLS the admin-weight command for MPLS LSP path computations, path-selection metric must be configured to TE.
Examples
The following example shows how to override the IGP cost of the link and set the cost to 20:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# admin-weight 20
Related Commands
affinity
To configure an affinity (the properties the tunnel requires in its links) for an MPLS-TE tunnel, use the affinity command in interface configuration mode. To return to the default behavior, use the no form of this command.
affinity {{affinity-value mask mask-value} | exclude name | exclude-all | include name | include-strict name}
no affinity {{affinity-value mask mask-value} | exclude name | exclude-all | include name | include-strict name}
Syntax Description
affinity-value |
Attribute values that are required for links to carry this tunnel. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1. |
mask mask-value |
Checks the link attribute. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute mask is 0 or 1. |
exclude name |
Configures a particular affinity to exclude. |
exclude-all |
Excludes all affinities. |
include |
Configures the affinity to include in the loose sense. |
include-strict |
Configures the affinity to include in the strict sense. |
Defaults
affinity-value: 0X00000000
mask-value: 0X0000FFFF
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
Support was added for the Name-Based Affinity Constraint scheme. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
Affinity colors definition for MPLS-TE was added. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Affinity determines the link attributes of the tunnel (that is, the attributes for which the tunnel has an affinity). The attribute mask determines which link attribute the router should check. If a bit in the mask is 0, the attribute value of a link or that bit is irrelevant. If a bit in the mask is 1, the attribute value of that link and the required affinity of the tunnel for that bit must match.
A tunnel can use a link if the tunnel affinity equals the link attributes and the tunnel affinity mask.
Any properties set to 1 in the affinity should be 1 in the mask. The affinity and mask should be set as follows:
tunnel_affinity=tunnel_affinity and tunnel_affinity_mask
You can configure up to 16 affinity constraints under a given tunnel. The following constraints are used to configure affinity constraints for the tunnel:
•Include constraint—Specifies that a link is considered for CSPF if it contains all the affinities associated with the include constraint. An acceptable link contains more affinity attributes than those associated with the include statement. You can have multiple include statements under a tunnel configuration.
•Include-strict constraint—Specifies that a link is considered for CSPF if it contains only the colors associated with the include-strict statement. The link cannot have any additional colors. In addition, a link without a color is rejected.
•Exclude constraint—Specifies that a link satisfies an exclude constraint if it does not have all the colors associated with the constraint. In addition, a link that does not have any attribute satisfies an exclude constraint.
•Exclude-all constraint—Specifies that only the links without any attribute are considered for CSPF. An exclude-all constraint is not associated with any color; whereas, all other constraint types are associated with up to 10 colors.
You are setting one bit for each color; however, the sample output shows multiple bits at the same time. For example, you can configure red and black colors on GigabitEthernet0/4/1/3 from the interface command. The sample output from the show mpls traffic-eng link-management interfaces command shows that the Attributes field is set to 0x21, which means that there are 0x20 and 0x1 bits on the link.
Examples
The following example shows how to configure the tunnel affinity and mask:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity 0101 mask 303
The following example shows that a link is eligible for CSPF if it has at least red color. The link can have any additional colors.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity include red
The following example shows that a link is eligible for CSPF if it has at least red and black colors. The link can have any additional colors.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity include red black
The following sample output shows that the include constraint from the show mpls traffic-eng tunnels command is 0x20 and 0x1:
Name: tunnel-te1 Destination: 0.0.0.0
Admin: up Oper: down Path: not valid Signalling: Down
G-PID: 0x0800 (internally specified)
Bandwidth: 0 kbps (CT0) Priority: 7 7
Number of configured name based affinity constraints: 1
Name based affinity constraints in use:
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 0 equal loadshares
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 0
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Reason for the tunnel being down: No destination is configured
The following example shows that a tunnel can go over a link that contains red or black affinity. A link is eligible for CSPF if it has a red color or a black color. Thus, a link with red and any other colors and a link with black and any additional colors must meet the constraint.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity include red
RP/0/RP0/CPU0:router(config-if)# affinity include black
The following sample output shows that the include constraint from the show mpls traffic-eng tunnels command is 0x20 or 0x1:
Name: tunnel-te1 Destination: 0.0.0.0
Admin: up Oper: down Path: not valid Signalling: Down
G-PID: 0x0800 (internally specified)
Bandwidth: 0 kbps (CT0) Priority: 7 7
Number of configured name based affinity constraints: 2
Name based affinity constraints in use:
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 0 equal loadshares
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 0
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Reason for the tunnel being down: No destination is configured
The following example shows that a link is eligible for CSPF if it has only red color. The link must not have any additional colors.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity include-strict red
The following example shows that a link is eligible for CSPF if it does not have the red attribute:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity exclude red
The following example shows that a link is eligible for CSPF if it does not have red and blue attributes. Thus, a link that has only a red attribute or only a blue attribute is eligible for CSPF.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity exclude red blue
The following example shows that a link is eligible for CSPF if it does not have either a red or a blue attribute:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# affinity exclude red
RP/0/RP0/CPU0:router(config-if)# affinity exclude blue
Related Commands
affinity-map
To assign a numerical value to each affinity name, use the affinity-map command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
affinity-map affinity name affinity value
no affinity-map affinity name affinity value
Syntax Description
affinity name |
Affinity map name-to-value designator (in hexadecimal, 0-ffffffff). |
affinity value |
Affinity map value designator (in hexadecimal, 0-ffffffff). |
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note The name-to-value mapping must represent a single bit of a 32-bit value.
Examples
The following example shows how to assign a numerical value to each affinity name:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map red 1
RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map blue 2
Related Commands
application (MPLS-TE)
To configure the application frequency, in minutes, for the applicable tunnel, use the application command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.
application minutes
no application minutes
Syntax Description
minutes |
Frequency, in minutes, for the automatic bandwidth application. Range is from 5 to 10080 (7 days). |
Defaults
minutes: 1440 (24 hours)
Command Modes
MPLS-TE automatic bandwidth interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you configure and modify the application frequency, the application period can reset and restart for that tunnel. The next bandwidth application for the tunnel happens within the specified minutes.
Examples
The following example shows how to configure application frequency to 1000 minutes for MPLS-TE interface 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# application 1000
Related Commands
attribute-flags
To configure attribute flags for an interface, use the attribute-flags command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
attribute-flags attribute flags
no attribute-flags attribute flags
Syntax Description
attribute flags |
Links attributes that are compared to the affinity bits of a tunnel during selection of a path. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits) where the value of an attribute is 0 or 1. |
DefaultsDefaults
attributes: 0x0
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The attribute-flags command assigns attributes to a link so that tunnels with matching attributes (represented by their affinity bits) prefer this link instead of others that do not match.
The interface attribute is flooded globally so that it can be used as a tunnel headend path selection criterion.
Examples
The following example shows how to set attribute flags to 0x0101:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-flags 0x0101
Related Commands
|
|
admin-weight |
Overrides the IGP administrative weight of the link. |
affinity |
Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel. |
attribute-names |
Configures attributes for the interface. |
interface (MPLS-TE) |
Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode. |
mpls traffic-eng |
Enters MPLS-TE configuration mode. |
attribute-names
To configure attributes for the interface, use the attribute-names command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
attribute-names attribute name
no attribute-names attribute name
Syntax Description
attribute name |
Attribute name expressed using alphanumeric or hexidecimal characters. |
Defaults
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note The name-to-value mapping must represent a single bit of a 32-bit value.
Examples
The following example shows how to assign an attribute name (in this case, red) to a TE link:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface pos 0/2/0/1
RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-name red
Related Commands
|
|
affinity |
Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel. |
attribute-flags |
Configures attribute flags for the interface. |
interface (MPLS-TE) |
Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode. |
mpls traffic-eng |
Enters MPLS-TE configuration mode. |
auto-bw (MPLS-TE)
To configure automatic bandwidth on a tunnel interface and to enter MPLS-TE automatic bandwidth interface configuration mode, use the auto-bw command in MPLS-TE interface configuration mode. To disable the automatic bandwidth on that tunnel, use the no form of this command.
auto-bw
no auto-bw
Syntax Description
This command has no arguments or keywords.
Defaults
By default, automatic bandwidth is not enabled.
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the auto-bw command to enter MPLS-TE automatic bandwidth interface configuration mode.
The following automatic bandwidth scenarios are described:
•If you configure the automatic bandwidth on a tunnel, the automatic bandwidth is enabled on that tunnel. If no other configuration is specified, defaults for the various parameters are used, the operation stops.
•The automatic operation (for example, output rate collection) starts as soon as the automatic bandwidth is enabled on one tunnel. If automatic bandwidth is disabled from all tunnels, the operation stops.
•If the output rate collection is already active when the automatic bandwidth is configured on a tunnel, the statistics collection for that tunnel starts at the next collection configuration.
Note Because the collection timer is already running, the first collection event for that tunnel happens in less than C minutes (for example, on an average of C/2 minutes).
Examples
The following example shows how to enter MPLS-TE automatic bandwidth interface configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)#
Related Commands
auto-bw collect frequency (MPLS-TE)
To configure the automatic bandwidth collection frequency use the auto-bw collect frequency command in MPLS-TE configuration mode. To reset the automatic bandwidth frequency to its default value, use the no form of this command.
auto-bw collect frequency minutes
no auto-bw collect frequency minutes
Syntax Description
minutes |
Interval between automatic bandwidth adjustments, in minutes. Range is between 1 to 10080. |
Defaults
The default value is 5 minutes. In addition, the no form of this command resets to the default.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The auto-bw collect frequency command configures the automatic bandwidth collection frequency for all the tunnels.
Modifying the global collection frequency does not restart the tunnel for the current application period. The application period continues with the modified collection frequency.
Examples
The following example configures a tunnel for an automatic bandwidth adjustment of 100 minutes:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# auto-bw collect frequency 100
Related Commands
autoroute announce
To specify that the Interior Gateway Protocol (IGP) should use the tunnel (if the tunnel is up) in its enhanced shortest path first (SPF) calculation, use the autoroute announce command in interface configuration mode. To return to the default behavior, use the no form of this command.
autoroute announce
no autoroute announce
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Currently, the only way to forward traffic over a tunnel is accomplished using the autoroute announce command or static routes command.
When you configure more than one IGP, the tunnel is announced to the IGP used to find the path to the tunnel destination.
By default, the route metric of the tunnel path to the destination equals the route metric of the shortest IGP path to that destination when autoroute announce is configured.
Examples
The following example shows how to configure IGP to use the tunnel in its enhanced SPF calculation when the tunnel is up:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# autoroute announce
Related Commands
autoroute metric
To specify the MPLS-TE tunnel metric that the Interior Gateway Protocol (IGP) enhanced Shortest Path First (SPF) calculation uses, use the autoroute metric command in interface configuration mode. To return to the default behavior, use the no form of this command.
autoroute metric {absolute | relative} value
no autoroute metric {absolute | relative} value
Syntax Description
absolute |
Displays the absolute metric mode; you can enter a positive metric value. |
relative |
Displays the relative metric mode; you can enter a positive, negative, or zero value. |
value |
Metric that the IGP enhanced SPF calculation uses. Relative value range is -10 to 10. Absolute value is 1 to 4294967295. |
Defaults
relative value: 0
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The autoroute metric command overwrites the default tunnel route metric of the shortest IGP path to the destination.
Examples
The following example shows how to configure the IGP enhanced SPF calculation using MPLS-TE tunnel metric as relative negative 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# autoroute metric relative -1
Related Commands
backup-bw
To configure the backup bandwidth for an MPLS-TE backup tunnel (that is used to protect a physical interface), use the backup-bw command in interface configuration mode. To return to the default behavior, use the no form of this command.
backup-bw {backup bandwidth {any-class-type | class-type ct} | global-pool {bandwidth | unlimited} | sub-pool {bandwidth | unlimited} | unlimited {any-class-type | class-type ct}}
no backup-bw {backup bandwidth {any-class-type | class-type ct} | global-pool {bandwidth | unlimited} | sub-pool {bandwidth | unlimited} | unlimited {any-class-type | class-type ct}}
Syntax Description
backup bandwidth |
Backup bandwidth in any-pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second (kbps). Range is 1 to 4294967295. |
any-class-type |
Displays the backup bandwidth assigned to any class-type protected tunnels. |
class-type ct |
Displays the class type of the backup bandwidth. Range is 0 to 1. |
sub-pool bandwidth |
(In Prestandard DS-TE with RDM) Displays the backup bandwidth in sub-pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second. Range bandwidth is 1 to 4294967295. Only label switched paths (LSPs) using bandwidth from the sub-pool can use the backup tunnel. |
global-pool bandwidth |
(In Prestandard DS-TE with RDM) Displays the backup bandwidth in global pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second. Range is 1 to 4294967295. |
unlimited |
Displays the unlimited bandwidth. |
Defaults
Any class-type unlimited.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Release 3.8.4 |
The usage guidelines for the unlimited keyword is updated. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Backup bandwidth can be limited or unlimited or specific to a global pool, sub-pool, or non-specific any-pool. Backup with backup-bw in global-pool protects global-pool LSPs only; backup-bw in sub-pool protects sub-pool LSPs only.
Backup tunnels configured with limited backup bandwidth (from any/global/sub pool) are not assigned to protect LSPs configured with zero signaled bandwidth.
Backup bandwidth provides bandwidth protection for fast reroute (FRR). Bandwidth protection for FRR supports DiffServ-TE with two bandwidth pools (class-types).
Class-type 0 is strictly equivalent to global-pool; class-type 1 is strictly equivalent to sub-pool bandwidth using the Russian Doll Model (RDM).
When using the backup bandwidth unlimited configuration under the backup tunnel interface with multiple backup tunnels, load sharing for the backup assignment uses the primary LSP bandwidth.
Examples
The following example shows how to configure backup tunnel 1 for use only by LSPs that take their bandwidth from the global pool (class-type 0 tunnels). Backup tunnel 1 does not provide bandwidth protection.
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# backup-bw global-pool unlimited
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# backup-bw unlimited class-type 0
In the following example, backup tunnel 2 is used by LSPs that take their bandwidth from the sub-pool (class-type 1 tunnels) only. Backup tunnel 2 provides bandwidth protection for up to 1000 units.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 2
RP/0/RP0/CPU0:router(config-if)# backup-bw sub-pool 1000
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 2
RP/0/RP0/CPU0:router(config-if)# backup-bw 1000 class-type 1
Related Commands
backup-path tunnel-te
To set an MPLS-TE tunnel to protect a physical interface against failure, use the backup-path tunnel-te command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
backup-path tunnel-te tunnel-number
no backup-path tunnel-te tunnel-number
Syntax Description
tunnel-number |
Number of the tunnel protecting the interface. Range is 0 to 65535. |
Defaults
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When the protected interface is down (shut down or removed), the traffic it was carrying (for the other label switched paths [LSPs], referred to as the protected LSPs) is re-routed, using fast reroute (FRR) onto the backup tunnels.
The following guidelines pertain to the FRR process:
•Multiple (backup) tunnels can protect the same interface by entering this command multiple times for different tunnels. The same (backup) tunnel can protect multiple interfaces by entering this command for each interface.
•The backup tunnel used to protect a physical interface must have a valid IP address configured.
•The backup tunnel cannot pass through the same interface that it is protecting.
•TE tunnels that are configured with the FRR option, cannot be used as backup tunnels.
•For the backup tunnel to provide protection to the protected LSP, the backup tunnel must have a terminating-end node in the path of a protected LSP.
•The source IP address of the backup tunnel and the merge point (MP) address (the terminating-end address of the backup tunnel) must be reachable.
Note You must configure record-route on TE tunnels that are protected by multiple backup tunnels merging at a single node.
Examples
The following example shows how to protect PoS interface 0/7/0/0 using tunnel 100 and tunnel 150:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel 100
RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel 150
Related Commands
bw-limit (MPLS-TE)
To configure the minimum and maximum automatic bandwidth to be set on a tunnel, use the bw-limit command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.
bw-limit {min bandwidth} {max bandwidth}
no bw-limit
Syntax Description
min bandwidth |
Configures the minimum automatic bandwidth, in kbps, on a tunnel. Range is from 0 to 4294967295. |
max bandwidth |
Configures the maximum automatic bandwidth, in kbps, on a tunnel. Range is from 0 to 4294967295. |
Defaults
min: 0 kbps
max: 4294967295 kbps
Command Modes
MPLS-TE automatic bandwidth interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Both the min and max keywords must be configured.
The bw-limit command automatically sets the minimum bandwidth to the default value of 0. Or the bw-limit command automatically sets the maximum to the default value of 4294967295 kbps.
If the value of the min keyword is greater than the max keyword, the bw-limit command is rejected. If you configure and modify the minimum or maximum bandwidth while the automatic bandwidth is already running, the next bandwidth application for that tunnel is impacted. For example, if the current tunnel requested bandwidth is 30 Mbps and the minimum bandwidth is modified to 50 Mbps, the next application sets the tunnel bandwidth to 50 Mbps.
Examples
The following example shows how to configure the minimum and maximum bandwidth for the tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# bw-limit min 30 max 80
Related Commands
clear mpls lmp
To clear Link Management Protocol (LMP) management hello settings, use the clear mpls lmp command in EXEC mode.
clear mpls lmp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco XR 12000 Series Router and Cisco CRS-1 |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
This command was moved under cisco-support. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to clear all LMP management hello settings:
RP/0/RP0/CPU0:router# clear mpls lmp
clear mpls traffic-eng auto-bw (MPLS-TE EXEC)
To clear automatic bandwidth sampled output rates and to restart the application period for the specified tunnel, use the clear mpls traffic-eng auto-bw command in EXEC mode.
clear mpls traffic-eng auto-bw {all | internal | tunnel-te tunnel-number}
Syntax Description
all |
Clears the automatic bandwidth sampled output rates for all tunnels. |
internal |
Clears all the automatic bandwidth internal data structures. |
tunnel-te tunnel-number |
Clears the automatic bandwidth sampled output rates for a specific tunnel. The tunnel-number argument is the tunnel ID, for which to clear the sampled output rates. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If no tunnel is specified, the clear mpls traffic-eng auto-bw command clears all the automatic bandwidth enabled tunnels.
For each tunnel in which the automatic bandwidth adjustment is enabled, information is maintained about the sampled output rates and the time remaining until the next bandwidth adjustment. The application period is restarted and values such as the largest collected bandwidth get reset. The tunnel continues to use the current bandwidth until the next application.
Examples
The following example displays the information for the automatic bandwidth for tunnel number 0 from the show mpls traffic-eng tunnels auto-bw brief command:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels 0 auto-bw brief
Tunnel LSP Last appl Requested Signalled Highest Application
Name ID BW(kbps) BW(kbps) BW(kbps) BW(kbps) Time Left
-------------- ------ ---------- ---------- ---------- ---------- --------------
tunnel-te0 278 100 100 100 150 12m 38s
The following example shows how to clear the automatic bandwidth sampled output rates for tunnel number 0:
RP/0/RP0/CPU0:router# clear mpls traffic-eng auto-bw tunnel-te 0
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels 0 auto-bw brief
Tunnel LSP Last appl Requested Signalled Highest Application
Name ID BW(kbps) BW(kbps) BW(kbps) BW(kbps) Time Left
-------------- ------ ---------- ---------- ---------- ---------- --------------
tunnel-te0 278 100 100 100 0 24m 0s
Related Commands
clear mpls traffic-eng counters global
To clear the internal MPLS-TE tunnel counters, use the clear mpls traffic-eng counters global command in EXEC mode.
clear mpls traffic-eng counters global
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to clear the internal MPLS-TE tunnel counters:
RP/0/RP0/CPU0:router# clear mpls traffic-eng counters global
clear mpls traffic-eng counters signaling
To clear (set to zero) the MPLS tunnel signaling counters, use the clear mpls traffic-eng counters signaling command in EXEC mode.
clear mpls traffic-eng counters signaling {all [heads | mids | tails] | name name | summary}
Syntax Description
all |
Clears counters for all MPLS-TE tunnels. |
heads |
(Optional) Displays tunnels with their heads at this router. |
mids |
(Optional) Displays tunnels with their midpoints at this router. |
mids |
(Optional) Displays tunnels with their tails at this router. |
name name |
Clears counters for an MPLS-TE tunnel with the specified name. |
summary |
Clears the counter's summary. |
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1 as clear mpls traffic-eng counters tunnels. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
Support was added for the middles keyword. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The clear mpls traffic-eng counters tunnels command was replaced by clear mpls traffic-eng counters signaling. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the clear mpls traffic-eng counters signaling command to set all MPLS counters to zero so that changes can be seen easily.
Examples
The following example shows how to clear all counters:
RP/0/RP0/CPU0:router# clear mpls traffic-eng counters signaling all
Related Commands
clear mpls traffic-eng fast-reroute log
To clear the log of MPLS Fast Reroute (FRR) events, use the clear mpls traffic-eng fast-reroute log command in EXEC mode.
clear mpls traffic-eng fast-reroute log
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows sample output before clearing the log of FRR events:
RP/0/RP0/CPU0:router# show mpls traffic-eng fast-reroute log
Node Protected LSPs Rewrites When Switching Time
-------- --------- ----- -------- ---------------------- --------------
0/0/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.064000 147
0/1/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.060093 165
0/2/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.063814 129
0/3/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.062861 128
RP/0/RP0/CPU0:router# clear mpls traffic-eng fast-reroute log
clear mpls traffic-eng link-management statistics
To clear all the MPLS-TE admission control statistics, use the clear mpls traffic-eng link-management statistics command in EXEC mode.
clear mpls traffic-eng link-management statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to clear all the MPLS-TE statistics for admission control:
RP/0/RP0/CPU0:router# clear mpls traffic-eng link-management statistics
clear mpls traffic-eng pce
To clear the path computation element (PCE) statistics, use the clear mpls traffic-eng pce command in EXEC mode.
clear mpls traffic-eng pce [peer ipv4 address]
Syntax Description
peer |
(Optional) Clears the statistics for one peer. |
ipv4 address |
(Optional) Configures the IPv4 address for PCE. |
Defaults
Clears statistics for all the PCE peers.
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to clear the statistics for the PCE:
RP/0/RP0/CPU0:router# clear mpls traffic-eng pce
Related Commands
collect-bw-only (MPLS-TE)
To configure only the bandwidth collection without adjusting the automatic bandwidth, use the collect-bw-only command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.
collect-bw-only
no collect-bw-only
Syntax Description
This command has no arguments or keywords.
Defaults
If the automatic bandwidth is not adjusted, the bandwidth collection is disabled.
Command Modes
MPLS-TE automatic bandwidth interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you enable the collect-bw-only command while the automatic bandwidth is already running on a tunnel, the bandwidth application is disabled from that moment. Before you enable the actual bandwidth application, you can get an idea of the automatic bandwidth behavior.
If you disable the collect-bw-only command on a tunnel from which the automatic bandwidth is already running, the actual bandwidth application takes place on the tunnel at the next application period.
It is also possible to manually activate a bandwidth application regardless of the collect bandwidth only flag being specified on a tunnel. To activate the bandwidth application, use the command mpls traffic-eng auto-bw apply (MPLS-TE) command in EXEC mode.
Examples
The following example shows how to enable only the bandwidth collection without adjusting the automatic bandwidth:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# collect-bw-only
Related Commands
destination (MPLS-TE)
To configure the destination address of a TE tunnel, use the destination command in interface configuration mode. To return to the default behavior, use the no form of this command.
destination ip-address
no destination ip-address
Syntax Description
ip-address |
Destination address of the MPLS-TE router ID. |
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note The tunnel destination address must be a unique MPLS-TE router ID; it cannot be an MPLS-TE link address on a node.
Examples
The following example shows how to set the destination address for tunnel-te1 to 10.10.10.10:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te1
RP/0/RP0/CPU0:router(config-if)# destination 10.10.10.10
Related Commands
direction (GMPLS)
To configure a bidirectional optical tunnel for GMPLS, use the direction command in interface tunnel-gte configuration mode. To return to the default behavior, use the no form of this command.
direction bidirectional
no direction bidirectional
Syntax Description
bidirectional |
Enables bidirectional tunneling. |
Defaults
Default is unidirectional.
Command Modes
Interface tunnel-gte configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
GMPLS interfaces were supported under the tunnel-gte interface type. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
There are two types of MPLS-TE tunnels:
•Generic packet MPLS-TE tunnels
•Optical MPLS-TE tunnel (GMPLS tunnel)
At the configuration level, you cannot tell the difference between a packet MPLS or a GMPLS-TE tunnel. Because packet TE tunnels are unidirectional while GMPLS tunnels are bidirectional, you can identify the optical GMPLS tunnel by identifying the bidirectional configuration.
The GMPLS-TE tunnel requires that you specify the endpoint and transit switching capability so that the path computation module can determine the links that the tunnel can traverse.
The transit switching capability describes the switching capability of the LSP region that the tunnel crosses. The endpoint switching capability describes the switching capability and encoding required for the tunnel interface associated with the two ends of the bidirectional tunnel (namely, active and passive side).
Finally, for GMPLS functionality to work, you must configure the direction and switching commands.
Note Bidirectional tunnel support is available on optical (GMPLS) tunnels only.
Examples
The following example shows how to change the tunnel direction from the default (unidirectional) to bidirectional:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 99
RP/0/RP0/CPU0:router(config-if)# direction bidirectional
Related Commands
disable (explicit-path)
To prevent the path from being used by MPLS-TE tunnels while it is configured, use the disable command in explicit path configuration mode. To return to the default behavior, use the no form of this command.
disable
no disable
Syntax Description
This command has no arguments or keywords.
Defaults
Explicit path is enabled.
Command Modes
Explicit path configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to disable explicit path 200:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
RP/0/RP0/CPU0:router(config-expl-path)# disable
Related Commands
ds-te bc-model
To enable a specific bandwidth constraint model (Maximum Allocation Model or Russian Doll Model) on the entire label switched router (LSR), use the ds-te bc-model command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
ds-te bc-model mam
no ds-te bc-model mam
Syntax Description
mam |
Enables the Maximum Allocation Model (MAM) bandwidth constraints model. |
Defaults
RDM is the default bandwidth constraint model.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.7.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You can configure both the MAM and RDM bandwidth values on a single interface before swapping to an alternate global MPLS-TE BC model.
If you configure bandwidth constraints without configuring the corresponding bandwidth constraint values, the router uses default bandwidth constraint values.
MAM is not supported in prestandard DS-TE mode. MAM and RDM are supported in IETF DS-TE mode; RDM is supported in prestandard DS-TE mode.
Note Changing the bandwidth constraints model affects the entire router and may have a major impact on system performance as nonzero-bandwidth tunnels are torn down.
Examples
The following example shows how to enable the MAM bandwidth constraints model:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# ds-te bc-model mam
Related Commands
ds-te mode
To configure standard differentiated-service TE mode (DS-TE), use the ds-te mode command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
ds-te mode ietf
no ds-te mode ietf
Syntax Description
ietf |
Enables IETF standard mode. |
Defaults
Prestandard DS-TE is the default differentiated service mode.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Release 3.8.4 |
The IETF DS-TE migration hitless enhancement was added into the Usage Guidelines section. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The following two DS-TE modes are supported:
•Prestandard mode
–The Cisco proprietary mechanism for IGPs and RSVP signalling are used, and DS-TE does not interoperate with third-party vendor equipment.
•IETF mode
–Standard defined extensions are used for IGPs and RSVP signalling, and DS-TE in this mode interoperates with third-party equipment.
–IETF mode supports two bandwidth constraint models: the Russian Doll Model (RDM) and Maximum Allocation Model (MAM).
–RDM is the default model.
–Router advertises variable-length bandwidth constraints, max-reservable- bandwidth, and unreserved bandwidths in TE-classes.
–tunnels must have valid class-type and priority configured as per TE-class map in use; otherwise, tunnels remain down.
–TE-class map (a set of tunnel priority and class-type values) is enabled to interpret unreserved bandwidth values advertised in IGP; therefore, TE-.class map must be identical on all nodes for TE tunnels to be successfully established.
–If the IETF DS-TE migration is hitless, which means the DS-TE mode is changed to IETF, TE does not flap tunnels when the class type is set to 0. The priority value matches the TE-class index (for example, TE-class map 5 is set to class-type 0 and priority 5) for all TE-class maps.
For DS-TE to function properly, DS-TE modes must be configured identically on all MPLS-TE nodes.
If you need to change the DS-TE mode, you must bring down all tunnel interfaces and, after the change, you should flood the updated bandwidth values through the network.
Note Changing the DS-TE mode affects the entire LSR and can have a major impact on system performance when tunnels are torn down.
Examples
The following example shows how to enable IETF standard mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# ds-te mode ietf
Related Commands
ds-te te-classes
To enter DS-TE te-class map configuration mode, use the ds-te te-classes command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
ds-te te-classes te-class te_class_index {class-type class_type_number {priority pri_number} | unused}
no ds-te te-classes te-class te_class_index {class-type class_type_number {priority pri_number} | unused}
Syntax Description
te-class |
Configures the te-class map. |
te_class_index |
TE class-map index. Range is 0 to 7. |
class-type |
Configures the class type. |
class_type_number |
Class type value in the te-class map. Range is 0 to 1. |
unused |
Marks the TE-class as unused. |
priority |
Configures the TE tunnel priority. |
pri_number |
TE tunnel priority value. Range is 0 to 7. |
Defaults
The following default te-class maps are used in IETF DS-TE mode:
|
|
|
0 |
0 |
7 |
1 |
1 |
7 |
2 |
UNUSED |
|
3 |
UNUSED |
|
4 |
0 |
0 |
5 |
1 |
0 |
6 |
UNUSED |
|
7 |
UNUSED |
|
Note The default mapping has 4 TE-classes used with 2 class-types and 4 TE-classes are unused. TE-class map is not used in prestandard DS-TE mode.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The unused keyword was added. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
In IETF DS-TE mode, modified semantic of the unreserved bandwidth TLV is used. Each of the eight available bandwidth values advertised in the IGP corresponds to a TE class. Because IGP advertises only eight bandwidth values, only eight TE-Classes can be supported in a IETF DS-TE network. The TE-Class mapping must be configured the same way on every router in a DS-TE domain. There is, however, no method by which to automatically detect or enforce this required consistency.
Examples
The following example shows how to configure a TE-class 7 parameter:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te) ds-te te-classes te-class 7 class-type 0 priority 4
Related Commands
explicit-path
To configure an explicit path for an MPLS-TE tunnel, use the explicit-path command in global configuration mode. To return to the default behavior, use the no form of this command.
explicit-path {identifier number | name pathname}
no explicit-path
Syntax Description
identifier number |
Configures an explicit path using a number. |
name pathname |
Configures an explicit path using a pathname. |
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure an explicit path for an MPLS-TE tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
Related Commands
fast-reroute
To enable fast-reroute (FRR) protection for an MPLS-TE tunnel, use the fast-reroute command in interface configuration mode. To return to the default behavior, use the no form of this command.
fast-reroute
no fast-reroute
Syntax Description
This command has no arguments or keywords.
Defaults
FRR is disabled.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When a protected link used by the fast-reroutable label switched path (LSP) fails, the traffic is rerouted to a previously assigned backup tunnel. Configuring FRR on the tunnel informs all the nodes that the LSP is traversing that this LSP desires link/node/bandwidth protection.
You must allow sufficient time after an RP failover before triggering FRR on standby RPs in order to synchronize with the active RP (verified using the show redundancy command). All TE tunnels must be in the recovered state and the database must be in the ready state for all ingress and egress line cards. To verify this information, use the show mpls traffic-eng tunnels and show mpls traffic-eng fast-reroute database commands.
Note Wait approximately 60 seconds before triggering FRR after verifying the database state.
Examples
The following example shows how to enable FRR on an MPLS-TE tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# fast-reroute
Related Commands
fast-reroute protect
To enable node and bandwidth protection for an MPLS-TE tunnel, use the fast-reroute protect command in interface configuration mode. To return to the default behavior, use the no form of this command.
fast-reroute protect {bandwidth | node}
no fast-reroute protect
Syntax Description
bandwidth |
Enables bandwidth protection request. |
node |
Enables node protection request. |
Defaults
FRR is disabled.
Command Modes
Interface configuration
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to enable bandwidth protection for a specified TE tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# fast-reroute protect bandwidth
Related Commands
fast-reroute timers promotion
To configure how often the router considers switching a protected MPLS-TE tunnel to a new backup tunnel if additional backup-bandwidth or a better backup tunnel becomes available, use the fast-reroute timers promotion command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
fast-reroute timers promotion interval
no fast-reroute timers promotion
Syntax Description
interval |
Interval (in seconds) between scans to determine if a label switched path (LSP) should use a new, better backup tunnel. Range is 0 to 604800. A value of 0 disables backup tunnel promotions. |
Defaults
interval: 300 seconds (5 minutes)
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Setting the interval to a low value puts more load on the CPU, because it has to scan all protected LSPs more frequently. It is not recommended that the timer be configured below the default value of 300 seconds.
Pacing mechanisms have been implemented to distribute the load on the CPU when backup promotion is active. Because of this, when a large number of protected LSPs are promoted, some delay is noticeable in backup promotion. If the promotion timer is configured to a very low value (depending on the number of protected LSPs) some protected LSPs may never get promoted.
To disable the timer, set the value to zero.
Examples
The following example shows how to specify that LSPs are scanned every 600 seconds (10 minutes) to determine if they should be promoted to a better backup tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# fast-reroute timers promotion 600
Related Commands
flooding-igp (GMPLS)
To flood the GMPLS Traffic Engineering link into a specific OSPF area and instance, use the flooding-igp command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
flooding-igp ospf instance area area
no flooding-igp ospf instance area area
Syntax Description
ospf |
Floods the interface into an OSPF instance |
instance |
Name of the OSPF instance into which the GMPLS link is to be flooded. |
area area |
Displays the area into which the GMPLS link is to be flooded (where TE is configured). |
Defaults
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
A GMPLS link won't be flooded into any IGP topology unless this command is used.
Note The flooding-igp command is valid for GMPLS-TE only.
Examples
The following example shows how to flood the optical GMPLS link on POS 0/1/0/0 into area 0 of OSPF instance "optical":
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface pos0/1/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding-igp ospf optical area 0
Related Commands
flooding thresholds
To set the reserved bandwidth thresholds for a link, use the flooding thresholds command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
flooding thresholds {down | up} percent [percent1 | percent2 | percent3 | ... percent 15]
no flooding thresholds {down | up}
Syntax Description
down |
Configures the threshold for decreased resource availability. |
up |
Configures the threshold for increased resource availability. |
percent [percent] |
Bandwidth threshold level. Range is 0 to 100 for all 16 levels. |
Defaults
down: 100, 99, 98, 97, 96, 95, 90, 85, 80, 75, 60, 45, 30, 15
up: 5, 30, 45, 60, 75, 80, 85, 90, 95, 97, 98, 99, 100
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You can configure up to sixteen flooding threshold values. The first value is mandatory; the next 15 are optional.
When a threshold is crossed, MPLS-TE link management advertises updated link information. If no thresholds are crossed, changes can be flooded periodically unless periodic flooding was disabled.
Examples
The following example shows how to set the reserved bandwidth threshold for the link for decreased resource availability (down) and for increased resource availability (up) thresholds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding thresholds down 100 75 25
RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding thresholds up 25 50 100
Related Commands
forwarding-adjacency
To configure an MPLS-TE forwarding adjacency, use the forwarding-adjacency command in interface configuration mode. To return to the default behavior, use the no form of this command.
forwarding-adjacency [holdtime time]
no forwarding-adjacency [holdtime time]
Syntax Description
holdtime time |
(Optional) Configures the holdtime value that is associated with each forwarding-adjacency LSP in milliseconds. The default is 0. |
Defaults
holdtime time: 0
Command Modes
Interface configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not specify a holdtime time value, a delay is introduced with the following results:
•When forwarding-adjacency is configured on a tunnel that is up, TE notifies IGP without any additional delay.
•When forwarding-adjacency is not configured on a tunnel, TE notifies IGP without any additional delay.
•When forwarding-adjacency is configured on a tunnel that is down, TE does not notify IGP.
•When a tunnel on which forwarding-adjacency has been configured comes up, TE holds the notification to IGP for the period of holdtime (assuming nonzero holdtime). When the holdtime elapses, TE notifies IGP if the tunnel is still up.
The paths that traffic is taking to the destination can be manipulated by adjusting the forwarding adjacency link metric. To do that, use the bandwidth command. The unit of possible bandwidth values is in kbps.
Examples
The following example shows how to configure forwarding adjacency with a holdtime value of 60 milliseconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 888
RP/0/RP0/CPU0:router(config-if)# forwarding-adjacency holdtime 60
Related Commands
index exclude-address
To exclude an address from a tunnel path entry at a specific index, use the index exclude-address command in explicit path configuration mode. To return to the default behavior, use the no form of this command.
index index-id exclude-address {ipv4 unicast A.B.C.D}
no index index-id
Syntax Description
index-id |
Index number at which the path entry is inserted or modified. Range is 1 to 65535. |
ipv4 unicast A.B.C.D |
Excludes the IPv4 unicast address. |
Defaults
No default behavior or values
Command Modes
Explicit path configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. Support for the ipv4 unicast keyword was added. |
Release 3.3 |
No modification. |
Release 3.4.0 |
The index (explicit path) command was modified to create two separate commands: index exclude-address and index next-address. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You cannot include or exclude addresses from an IP explicit path unless explicitly configured using the exclude-address keyword.
Use the exclude-address keyword only after entering the explicit path configuration mode.
If you use the exclude-address keyword and specify the IP address of a link, the constraint-based routine does not consider that link when it sets up MPLS-TE paths. If the excluded address is a flooded MPLS-TE router ID, the constraint-based shortest path first (SPF) routine does not consider that entire node.
Note The person who performs the configuration must know the IDs of the routers, as it may not be apparent if the value refers to the link or to the node.
MPLS-TE accepts IP explicit paths composed of all excluded addresses configured using the exclude-address keyword.
Examples
The following example shows how to exclude address 192.168.3.2 at index 3 of the explicit path 200:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
RP/0/RP0/CPU0:router(config-expl-path)# index 3 exclude-address ipv4 unicast 192.168.3.2
Related Commands
index next-address
To include a path entry at a specific index, use the index next-address command in explicit path configuration mode. To return to the default behavior, use the no form of this command.
index index-id next-address [loose | strict] ipv4 unicast A.B.C.D
no index index-id
Syntax Description
index-id |
Index number at which the path entry is inserted or modified. Range is 1 to 65535. |
ipv4 unicast A.B.C.D |
Includes the IPv4 unicast address (strict address). |
loose ipv4 unicast A.B.C.D |
(Optional) Specifies the next unicast address in the path as a loose hop. |
strict ipv4 unicast A.B.C.D |
(Optional) Specifies the next unicast address in the path as a strict hop. |
Defaults
No default behavior or values
Command Modes
Explicit path configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. Support for the ipv4 unicast keyword was added. |
Release 3.3 |
No modification. |
Release 3.4.0 |
The index (explicit path) command was added to create two separate commands: index exclude-address and index next-address. Support was added for loose and strict keywords for the index next-address command. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You cannot include addresses from an IP explicit path unless explicitly configured using the next-address keyword.
Use the next-address keyword only after entering the explicit path configuration mode.
Note The person who performs the configuration must know the IDs of the routers, as it may not be apparent if the value refers to the link or to the node.
Examples
The following example shows how to insert the next-address 192.168.3.2 at index 3 of the explicit path 200:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
RP/0/RP0/CPU0:router(config-expl-path)# index 3 next-address ipv4 unicast 192.168.3.2
Related Commands
interface (MPLS-TE)
To enable MPLS-TE on an interface and to enter MPLS-TE interface configuration mode, use the interface command in global configuration mode. To return to the default behavior, use the no form of this command.
interface type interface-path-id
no interface type interface-path-id
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or a virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You must enter MPLS-TE interface mode to configure specific interface parameters on physical interfaces.
Configuring MPLS-TE or Tunnel-TE begins the TE-control process on RP.
Examples
The following example shows how to enter the MPLS-TE interface configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/1
The following example shows how to remove an interface from the MPLS-TE domain:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# no interface POS 0/7/0/1
interface tunnel-gte
To configure an MPLS-TE tunnel interface for GMPLS interfaces, use the interface tunnel-gte command in global configuration mode. To return to the default behavior, use the no form of this command.
interface tunnel-gte tunnel-id
no interface tunnel-gte tunnel-id
Syntax Description
tunnel-id |
Tunnel number. Range is 0 to 65535. |
Defaults
Tunnel interfaces are disabled.
Command Modes
Global configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and use the loopback interface address as the source address of the tunnel.
Configuring MPLS-TE links or a tunnel TE interface begins the TE-control process on RP.
The interface tunnel-gte command indicates that the tunnel interface is for an MPLS-TE tunnel and enables the various tunnel MPLS-TE GMPLS tunnel interface options.
Examples
The following example shows how to configure tunnel-gte interface 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 1
RP/0/RP0/CPU0:router(config-if)#
Related Commands
|
|
direction (GMPLS) |
Configures a bidirectional optical tunnel for GMPLS. |
match (GMPLS) |
Matches an active tunnel to a passive tunnel. |
passive (GMPLS) |
Configures passive GMPLS tunnels. |
switching endpoint (GMPLS) |
Specifies the switching capability and encoding types for all endpoint TE links used to signal the optical tunnel that is mandatory to set up the GMPLS LSP. |
switching transit (GMPLS) |
Specifies the switching capability and encoding types for all transit TE links used to signal the optical tunnel to configure an optical LSP. |
interface tunnel-te
To configure an MPLS-TE tunnel interface, use the interface tunnel-te command in global configuration mode. To return to the default behavior, use the no form of this command.
interface tunnel-te tunnel-id
no interface tunnel-te tunnel-id
Syntax Description
tunnel-id |
Tunnel number. Range is 0 to 65535. |
Defaults
Tunnel interfaces are disabled.
Command Modes
Global configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
Policy-based tunnel selection example was added. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface, and use the loopback interface address as the source address of the tunnel.
Configuring MPLS-TE links or Tunnel-TE interface begins the TE-control process on RP.
The interface tunnel-te command indicates that the tunnel interface is for an MPLS-TE tunnel and enables the various tunnel MPLS configuration options. Use this command to configure these options:
•affinity
•autoroute announce
•autoroute metric
•backup-bw
•signalled-bandwidth
•signalled-name
•fast-reroute
•path-option
•path-selection
•priority
•record-route
•policy-class
Note You must configure record-route on TE tunnels that are protected by multiple backup tunnels merging at a single node.
Examples
The following example shows how to configure tunnel interface 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0
The following example shows how to set the tunnel-class attribute to map the correct traffic class to the tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# policy-class 1
Related Commands
|
|
affinity |
Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel. |
autoroute metric |
Instructs the IGP to use the tunnel in its enhanced SPF calculation, if the tunnel is in an up state. |
backup-bw |
Configures backup bandwidth for FRR. |
fast-reroute |
Enables fast-reroute (FRR) protection for an MPLS-TE tunnel. |
path-option |
Configures a path option for an MPLS tunnel. |
path-selection metric (interface) |
Configures a path selection metric—TE or IGP. |
policy-class |
Configures policy-based tunnel selection (PBTS) to direct traffic into specific TE tunnels. |
priority (MPLS-TE) |
Configures setup and reservation priority for an MPLS-TE tunnel. |
record-route |
Configures record-route on an MPLS-TE tunnel. |
ipcc interface (MPLS-TE)
To configure an interface-bound IP based control channel to a specific LMP neighbor with the option to specify a custom destination address that is useful for GigabitEthernet interfaces, use the ipcc interface command in MPLS-TE neighbor configuration mode. To disable this feature, use the no form of this command.
ipcc interface type interface-path-id [dest ipv4 address]
no ipcc interface type interface-path-id [dest ipv4 address]
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
dest |
(Optional) Configures the remote endpoint address. |
ipv4 address |
(Optional) Configures the IPv4 address. |
Defaults
No default behavior or values
Command Modes
MPLS-TE neighbor configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure the IPCC interface for Loopback0:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor OXC1
RP/0/RP0/CPU0:router(config-mpls-te-nbr-OXC1)# ipcc interface Loopback0
Related Commands
ipcc routed (MPLS-TE)
To configure a routed IP-based control channel for a specific LMP neighbor, use the ipcc routed command in MPLS-TE neighbor configuration mode. To return to the default behavior, use the no form of this command.
ipcc routed
no ipcc routed
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
MPLS-TE neighbor configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure a routed IPCC for neighbor router1 in which the destination IP address is the node ID of the neighbor router1 on an interface determined dynamically by an IP routing protocol:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor router1
RP/0/RP0/CPU0:router(config-mpls-te-nbr-router1)# ipcc routed
Related Commands
ipv4 unnumbered (MPLS)
To specify the MPLS-TE tunnel Internet Protocol Version 4 (IPv4) address, use the ipv4 unnumbered command in interface configuration mode. To return to the default behavior, use the no form of this command.
ipv4 unnumbered type interface-path-id
no ipv4 unnumbered type interface-path-id
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No IP address is set.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Tunnel-te is not signaled until an IP address is configured on the tunnel interface; therefore, the tunnel state stays down without IP address configuration.
Loopback is commonly used as the interface type.
Examples
The following example shows how to configure the MPLS-TE tunnel to use the IPv4 address used on loopback interface 0:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0
link-management timers bandwidth-hold
To set the length of time that bandwidth is held for a Resource Reservation Protocol (RSVP) Path (setup) message to wait for the corresponding RSVP Resv message to return, use the link-management timers bandwidth-hold command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
link-management timers bandwidth-hold holdtime
no link-management timers bandwidth-hold holdtime
Syntax Description
holdtime |
Number of seconds that bandwidth can be held. Range is 1 to 300. Default is 15. |
Defaults
holdtime: 15 seconds
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The link-management timers bandwidth-hold command determines the time allowed for an RSVP message to return from a neighbor RSVP node.
Examples
The following example shows how to set the bandwidth to be held for 10 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# link-management timers bandwidth-hold 10
Related Commands
link-management timers periodic-flooding
To set the length of the interval for periodic flooding, use the link-management timers periodic-flooding command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
link-management timers periodic-flooding interval
no link-management timers periodic-flooding
Syntax Description
interval |
Length of the interval (in seconds) for periodic flooding. Range is 0 to 3600. A value of 0 turns off periodic flooding. The minimum value is 30 seconds. |
Defaults
interval: 180 seconds (3 minutes)
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The link-management timers periodic-flooding command advertises the link state information changes that do not trigger immediate action, such as a change to the allocated bandwidth that does not cross a threshold.
Examples
The following example shows how to set the interval length for periodic flooding to 120 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# link-management timers periodic-flooding 120
Related Commands
link-management timers preemption-delay bundle-capacity
To configure the time that the TE waits before preempting any tunnels due to bundle failures, use the link-management timers preemption-delay bundle-capacity command in MPLS-TE configuration mode. To return to the default behavior of 60 seconds, use the no form of this command.
link-management timers preemption-delay bundle-capacity timer value
no link-management timers preemption-delay bundle-capacity
Syntax Description
timer value |
Delay time before tunnels are preempted because of insufficient bandwidth from bundle failures. Range is 1 to 300 seconds. |
Defaults
60 seconds
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.4 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When member links of a bundle fail successively, the bundle has insufficient RSVP bandwidth to accommodate all admitted tunnels. By default, the TE control waits for 60 seconds for more member failures to occur before preempting the tunnels.
Use the link-management timers preemption-delay bundle-capacity command to override this default.
Examples
The following example shows how to set the tunnel preemption delay timer to 50 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# link-management timers preemption-delay
bundle-capacity 50
Related Commands
load-share
To determine load-sharing balancing parameters for a specified interface, use the load-share command in interface configuration mode. To return to the default behavior, use the no form of this command.
load-share value
no load-share
Syntax Description
value |
Load-share value, equivalent to the bandwidth in Kbps (that is, the same value in configuration). Range is 1 to 4294967295. Default is 0. |
Defaults
The default load-share for tunnels with no explicit configuration is the configured signalled bandwidth.
value: 0 (if no value is assigned)
Command Modes
Interface configuration
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Configuration schemas are supported for load balancing.
To enable the load-share command, you must enable unequal load balancing using the load-share unequal command.
Examples
The following example shows how to configure load-sharing parameters on a specified interface:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 100
RP/0/RP0/CPU0:router(config-if)# load-share 100
Related Commands
load-share unequal
To configure unequal load-sharing for an MPLS-TE tunnel, use the load-share unequal command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
load-share unequal
no load-share unequal
Syntax Description
This command has no arguments or keywords.
Defaults
By default, unequal load-balancing is disabled and equal load-balancing occurs.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to enable unequal load-sharing:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# load-share unequal
Related Commands
lmp hello (GMPLS)
To configure Link Management Protocol (LMP) IPCC management hello settings, use the lmp hello command in MPLS-TE neighbor lmp configuration mode. To return to the default behavior, use the no form of this command.
lmp hello {hello send interval | hello dead interval}
no lmp hello {hello send interval | hello dead interval}
Syntax Description
hello send interval |
Time between sending hello keep alive message. Range is 100 to 21845 milliseconds. |
hello dead interval |
Time to wait without receiving a hello from the neighbor before declaring the IPCC down again. Range is 100 to 21845 milliseconds. |
Defaults
No default behavior or values
Command Modes
MPLS-TE neighbor lmp configuration mode
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You can disable hellos using the lmp static command.
Examples
The following example shows how to configure Link Management Protocol (LMP) IPCC management hello settings:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor lmp
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor gmpls3 lmp hello 400 1200
Related Commands
lmp neighbor (MPLS-TE)
To configure or update an LMP optical neighbor with its associated identifier and enter MPLS-TE neighbor configuration mode, use the lmp neighbor command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
lmp neighbor name
no lmp neighbor name
Syntax Description
name |
Text string representing the name of the LMP neighbor. |
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to enter MPLS-TE neighbor configuration mode for router1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor router1
RP/0/RP0/CPU0:router(config-mpls-te-nbr-router1)#
Related Commands
lmp router-id (MPLS-TE)
To configure the router ID for the optical instance using the LMP protocol, use the lmp router-id command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
lmp router-id {ipv4 address | type interface-path-id}
no lmp router-id {ipv4 address | type interface-path-id}
Syntax Description
ipv4 address |
Router ID expressed as an IPv4 address. |
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how configure the LMP router ID for IPv4 address 172.24.20.164:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp router-id router 127.0.0.1
Related Commands
match (GMPLS)
To match an active tunnel to a passive tunnel, use the match command in interface tunnel-gte configuration mode. To return to the default behavior, use the no form of this command.
match identifier tunnel number
no match identifier tunnel number
Syntax Description
identifier |
Configures the identifier of the active tunnel to match with this passive tunnel. |
tunnel number |
Tunnel number. Range is 0 to 65535. |
Defaults
No default behavior or values
Command Modes
Interface tunnel-gte configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
GMPLS interfaces were supported under the tunnel-gte interface type. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
GMPLS interfaces are used under the tunnel-gte interface type.
You must enter the hostname for the head router then underscore _t, and the tunnel number for the head router. If tunnel-gte1 is configured on the head router with a hostname of gmpls1, CLI is match identifier gmpls1_t1.
Examples
The following example shows how to match the active tunnel ID to the passive tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 1
RP/0/RP0/CPU0:router(config-if)# match identifier gmpls1_t1
Related Commands
maxabs (MPLS-TE)
To specify the maximum number of MPLS-TE tunnels that can be configured, use the maxabs command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
maxabs tunnels tunnel-limit [destinations dest-limit]
no maxabs tunnels tunnel-limit [destinations dest-limit]
Syntax Description
tunnels |
Configures all tunnels for MPLS-TE. |
tunnel-limit |
Maximum number of tunnel TE interfaces. Range is 1 to 65536. |
destinations |
(Optional) Configures all destinations for MPLS-TE. |
dest-limit |
(Optional) Maximum total number of destinations that can be configured. Range is 1 to 65536. |
Defaults
tunnel-limit: 4096
dest-limit: 4096
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to set the tunnel-te configuration limit to 3000:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# maxabs tunnels 1000 destinations 1000
Related Commands
mpls traffic-eng
To enter MPLS-TE configuration mode, use the mpls traffic-eng command in global configuration mode.
mpls traffic-eng
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to enter MPLS-TE configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)#
mpls traffic-eng auto-bw apply (MPLS-TE)
To configure the highest bandwidth collected on a tunnel without waiting for the current application period to end, use the mpls traffic-eng auto-bw apply command in EXEC mode.
mpls traffic-eng auto-bw apply {all | tunnel-te tunnel-number}
Syntax Description
all |
Configures the highest bandwidth collected instantly on all the automatic -bandwidth- enabled tunnels. |
tunnel-te tunnel-number |
Configures the highest bandwidth instantly to the specified tunnel. Range is from 0 to 65535. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The mpls traffic-eng auto-bw apply command can forcefully expire the current application period on a specified tunnel and immediately apply the highest bandwidth recorded so far; instead of waiting for the application period to end on its own.
Note The predefined threshold check still applies on the configuration, and if the delta is not significant enough, the automatic bandwidth functionality overrides this command.
The bandwidth application is performed only if at least one output rate sample has been collected for the current application period.
To guarantee the application of a specific signaled bandwidth value when triggering a manual bandwidth application, follow these steps:
1. Configure the minimum and maximum automatic bandwidth to the bandwidth value that you want to apply by using the bw-limit (MPLS-TE) command.
2. Trigger a manual bandwidth application by using the mpls traffic-eng auto-bw apply command.
3. Revert the minimum and maximum automatic bandwidth value back to their original value.
Examples
The following example configures the highest bandwidth to a specified tunnel:
RP/0/RP0/CPU0:router# mpls traffic-eng auto-bw apply tunnel-te 1
Related Commands
|
|
auto-bw collect frequency (MPLS-TE) |
Configures the automatic bandwidth collection frequency and controls the manner in which the bandwidth for a tunnel collects output rate information, but does not adjust the tunnel bandwidth. |
show mpls traffic-eng tunnels auto-bw brief |
Displays the list of automatic-bandwidth-enabled tunnels, and indicates if the current signaled bandwidth of the tunnel is identical to the bandwidth that is applied by the automatic bandwidth. |
mpls traffic-eng fast-reroute promote
To configure the router to assign new or more efficient backup MPLS-TE tunnels to protected MPLS-TE tunnels, use the mpls traffic-eng fast-reroute promote command in EXEC mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng fast-reroute promote
no mpls traffic-eng fast-reroute promote
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to initiate backup tunnel promote and assignment:
RP/0/RP0/CPU0:router# mpls traffic-eng fast-reroute promote
Related Commands
|
|
fast-reroute |
Enables fast-reroute (FRR) protection for an MPLS-TE tunnel. |
mpls traffic-eng level
To configure a router running Intermediate System-to-System (IS-IS) MPLS-TE at IS-IS Level 1 and Level 2, use the mpls traffic-eng level command in router configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng level isis-level
no mpls traffic-eng level isis-level
Syntax Description
isis-level |
IS-IS level (1, 2, or both) where MPLS-TE is enabled. |
Defaults
No default behavior or values
Command Modes
Router configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
Support was added to enable MPLS Traffic Engineering in both IS-IS Level 1 and Level 2. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The mpls traffic-eng level command is supported for IS-IS and affects the operation of MPLS-TE only if MPLS-TE is enabled for that routing protocol instance.
Examples
The following example shows how to configure a router running IS-IS MPLS to flood TE for IS-IS level 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router isis 1
RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicast
RP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng level 1
RP/0/RP0/CPU0:router(config-isis-af)# metric-style wide
Related Commands
mpls traffic-eng link-management flood
To enable immediate flooding of all the local MPLS-TE links, use the mpls traffic-eng link-management flood command in EXEC mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng link-management flood
no mpls traffic-eng link-management flood
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note If there is no change in the LSA since last flooding, IGP may dampen the advertisement.
Examples
The following example shows how to initiate flooding of the local MPLS-TE links:
RP/0/RP0/CPU0:router# mpls traffic-eng link-management flood
Related Commands
mpls traffic-eng path-protection switchover (GMPLS)
To specify a manual switchover for path protection for a GMPLS optical LSP, use the mpls traffic-eng path-protection switchover command in EXEC mode. To disable this feature, use the no form of this command.
mpls traffic-eng path-protection switchover {tunnel name | number}
no mpls traffic-eng path-protection switchover {tunnel name | number}
Syntax Description
tunnel name |
Name of the tunnel that is used for a switchover. |
number |
Tunnel ID number for the tunnel that is used for a switchover. The range is from 0 to 65535. |
Defaults
No manual path protection is invoked on either the head or tail router.
Command Modes
EXEC
Command History
|
|
Release 3.3.2 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the mpls traffic-eng path-protection switchover command to run on both tunnel head and tunnel tail at the same time. The mpls traffic-eng path-protection switchover command must be issued on both head and tail router of the GMPLS LSP to achieve the complete path switchover at both ends.
Examples
The following example sets the tunnel ID number to 1:
RP/0/RP0/CPU0:router# mpls traffic-eng path-protection switchover 1
Related Commands
|
|
path-option |
Configures a path option for an MPLS-TE tunnel. |
mpls traffic-eng pce activate-pcep
To force idle peers to be reestablished without waiting for a timer, use the mpls traffic-eng pce activate-pcep command in EXEC mode. To disable this feature, use the no form of this command.
mpls traffic-eng pce activate-pcep {address | all}
no mpls traffic-eng pce activate-pcep {address | all}
Syntax Description
address |
Address of the idle peer. |
all |
Activates all the idle peers. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
|
|
mpls-te |
read, write, execute |
Examples
The following example shows how to trigger a path computation client (PCC) or PCE to activate an idle path computation element protocol (PCEP) session:
RP/0/RP0/CPU0:router# mpls traffic-eng pce activate-pcep all
Related Commands
mpls traffic-eng pce reoptimize
To trigger reoptimization manually either for all or a specific PCE-based tunnel, use the mpls traffic-eng pce reoptimize command in EXEC mode. To disable this feature, use the no form of this command.
mpls traffic-eng pce reoptimize [tunnel ID] [force]
no mpls traffic-eng pce reoptimize [tunnel ID] [force]
Syntax Description
tunnel ID |
(Optional) Tunnel ID to be reoptimized. Range is from 0 to 65535. |
force |
(Optional) Forces the router to start using the newly calculated route even if the used path has a better metric. |
Defaults
Reoptimizes all the PCE tunnels.
Command Modes
EXEC
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you do not run the mpls traffic-eng pce reoptimize command, the system tries to reoptimize at an interval of 3600 seconds.
|
|
mpls-te |
read, write, execute |
Examples
The following example shows how to trigger reoptimization for all PCE-based tunnels:
RP/0/RP0/CPU0:router# mpls traffic-eng pce reoptimize
Related Commands
mpls traffic-eng reoptimize (EXEC)
To force immediate reoptimization of all TE tunnels, use the mpls traffic-eng reoptimize command in EXEC mode.
mpls traffic-eng reoptimize [tunnel_id | tunnel_name]
Syntax Description
tunnel_id |
(Optional) MPLS-TE tunnel identification expressed as a number. |
tunnel_name |
(Optional) TE tunnel identification expressed as a name. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to immediately reoptimize all TE tunnels reoptimized:
RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize
The following example shows how to immediately reoptimize TE tunnel-te90:
RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize tunnel-te90
Related Commands
mpls traffic-eng router-id (MPLS-TE router)
To specify that the TE router identifier for the node is the IP address associated with a given interface, use the mpls traffic-eng router-id command in the appropriate mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng router-id type interface-path-id
no mpls traffic-eng no router-id type interface-path-id
Syntax Description
type |
Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
OSPF configuration
IS-IS address family configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
A routers identifier acts as a stable IP address for the TE configuration. This IP address is flooded to all nodes. You must set the destination on the destination node TE router identifier for all affected tunnels. This router ID is the address that the TE topology database at the tunnel head uses for its path calculation.
Note When the mpls traffic-eng router-id command is not configured, global router ID is used by MPLS-TE if there is one configured.
Examples
The following examples show how to specify the TE router identifier as the IP address associated with loopback interface:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# mpls traffic-eng router-id Loopback0
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router isis 1
RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicast
RP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng router-id Loopback0
Related Commands
|
|
mpls traffic-eng level |
Configures a router running OSPF MPLS so that it floods TE for the indicated IS-IS level. |
overflow threshold (MPLS-TE)
To configure the tunnel overflow detection, use the overflow threshold command in MPLS-TE automatic bandwidth interface configuration mode. To disable the overflow detection feature, use the no form of this command.
overflow threshold percentage [min bandwidth] limit limit
no overflow threshold
Syntax Description
percentage |
Bandwidth change percent to trigger an overflow. Range is from 1 to 100 percent. |
limit limit |
Configures the number of consecutive collection intervals that exceeds the threshold. The bandwidth overflow triggers an early tunnel bandwidth update. Range is from 1 to 10 collection periods. The default value is none. |
min bandwidth |
(Optional) Configures the bandwidth change value in kbps to trigger an overflow. Range is from 10 to 4294967295. The default value is 10. |
Defaults
The default value is disabled.
Command Modes
MPLS-TE automatic bandwidth interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you modify the limit keyword, the consecutive overflows counter for the tunnel is also reset.
If you enable or modify the minimum value, the current consecutive overflows counter for the tunnel is also reset, which effectively restarts the overflow detection from scratch.
If a number of consecutive bandwidth samples are greater than the overflow threshold (bandwidth percentage) and the minimum bandwidth configured, then a bandwidth application is updated immediately; instead of waiting for the end of the application period.
Examples
The following example shows how to configure the tunnel overflow detection for tunnel-te 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# overflow threshold 50 limit 3
Related Commands
passive (GMPLS)
To configure a passive GMPLS tunnel, use the passive command in interface tunnel-gte configuration mode. To return to the default behavior, use the no form of this command.
passive
no passive
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface tunnel-gte configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
GMPLS interfaces were supported under the tunnel-gte interface type. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
GMPLS interfaces are used under the tunnel-gte interface type.
Examples
The following example shows how to configure a passive GMPLS virtual interface tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 99
RP/0/RP0/CPU0:router(config-if)# passive
Related Commands
path-option
To configure a path option for an MPLS-TE tunnel, use the path-option command in tunnel-te interface configuration mode. To return to the default behavior, use the no form of this command.
path-option [protecting] preference-priority {dynamic [pce [address ipv4 address] | explicit {name pathname | identifier path-number}} [isis instance name {level level}] [ospf instance name {area area ID}]] [verbatim] [lockdown]
no path-option [protecting] preference-priority {dynamic [pce [address ipv4 address] | explicit {name pathname | path-number}} [isis instance name {level level}] [ospf instance name {area area ID}]] [verbatim] [lockdown]
Syntax Description
number |
Path option number. Range is 1 to 1000. |
protecting number |
Specifies a path setup option to protect a path. The range for the path option number is 1 to 1000. |
dynamic |
Specifies that label switched paths (LSP) are dynamically calculated. |
pce |
(Optional) Specifies that the LSP is computed by a Path Computation Element (PCE). |
address |
(Optional) Configures the address for the PCE. |
ipv4 address |
Configures the IPv4 address for the PCE. |
explicit |
Specifies that LSP paths are IP explicit paths. |
name pathname |
Specifies the path name of the IP explicit path. |
identifier path-number |
Specifies a path number of the IP explicit path. |
verbatim |
(Optional) Bypasses the Topology/CSPF check for explicit paths. |
lockdown |
(Optional) Specifies that the LSP cannot be reoptimized. |
isis instance name |
(Optional) Limits CSPF to a single IS-IS instance and area. |
level level |
Configures the level for IS-IS. The range is from 1 to 2. |
ospf instance name |
(Optional) Limits CSPF to a single OSPF instance and area. |
area area ID |
Configures the area for OSPF. The range is from 0 to 4294967295. |
Defaults
No default behavior or values
Command Modes
Tunnel-te interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.3.2 |
The protecting keyword was added to support GMPLS protection and restoration. |
Release 3.4.0 |
No modification. |
Release 3.4.1 |
Both the verbatim and lockdown keywords can be used together. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
An IGP-area was specified with the path-option command. Both the isis keyword and the ospf keyword were added. |
Release 3.8.0 |
The pce, address, and ipv4 keywords were added. The address argument was added. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You can configure several path options for a single tunnel. For example, there can be several explicit path options and a dynamic option for one tunnel. The path setup preference is for lower (not higher) numbers, so option 1 is preferred.
When the lower number path option fails, the next path option is used to set up a tunnel automatically (unless using the lockdown option).
The protecting keyword specifies that you can configure path-protection for the primary LSP. You specify the backup path for the path-option command in case of the primary path failure.
CSPF areas are configured on a per-path-option basis.
Examples
The following example shows how to configure the tunnel to use a named IPv4 explicit path as verbatim and lockdown options for the tunnel. This tunnel cannot reoptimize when the FRR event goes away; unless, you manually reoptimize it:
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name test verbatim lockdown
The following example shows how to enable path protection on a tunnel to configure an explicit path:
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name po4
RP/0/RP0/CPU0:router(config-if)# path-option protecting 1 explicit name po6
The following example shows how to limit CSPF to a single OSPF instance and area:
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name router1 ospf 3 area 7
verbatim
The following example shows how to limit CSPF to a single IS-IS instance and area:
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# path-option 1 dynamic isis mtbf level 1 lockdown
Related Commands
path-selection ignore overload (MPLS-TE)
To ignore the Intermediate System-to-Intermediate System (IS-IS) overload bit setting for MPLS-TE, use the path-selection ignore overload command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
path-selection ignore overload
no path-selection ignore overload
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the path-selection ignore overload command to ensure that label switched paths (LSPs) are broken because of routers whose IS-IS overload bit is enabled.
Examples
The following example shows how to use the path-selection ignore overload command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection ignore overload
path-selection loose-expansion affinity (MPLS-TE)
To specify the affinity value to be used to expand a path to the next loose hop for a tunnel on an area border router, use the path-selection loose-expansion affinity command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
path-selection loose-expansion affinity affinity-value mask affinity-mask [class-type type]
no path-selection loose-expansion affinity affinity-value mask affinity-mask [class-type type]
Syntax Description
affinity-value |
Attribute values required for links carrying this tunnel. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1. |
mask affinity-mask |
Checks the link attribute, a 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute mask is 0 or 1. |
class-type type |
(Optional) Requests the class-type of the tunnel bandwidth. Range is 0 to 1. |
Defaults
affinity-value: 0X00000000
mask-value: 0X0000FFFF
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When non-defaults loose-path expansion affinity/mask are configured, and the ABR/mid LSR fails to expand the path to the next loose hop (or destination), the ABR/mid does not attempt to route the RSVP path message hop-by-hop. However, when defaults are configured and the ABR/mid LSR fails to expand the path to the next loose hop (or destination), the ABR/mid attempts to route the path to the next loose hop (or destination) using RIB.
Note The new affinity scheme (based on names) is not supported for loose-hop expansion. New configuration does not affect the already up tunnels.
Examples
The following example shows how to configure affinity 0x55 with mask 0xFFFFFFFF:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection loose-expansion affinity 55 mask
FFFFFFFF
Related Commands
path-selection loose-expansion metric (MPLS-TE)
To configure a metric type to be used to expand a path to the next loose hop for a tunnel on an area border router, use the path-selection loose-expansion metric command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
path-selection loose-expansion metric {igp | te} [class-type type]
no path-selection loose-expansion metric {igp | te} [class-type type]
Syntax Description
igp |
Configures an Interior Gateway Protocol (IGP) metric. |
te |
Configures a TE metric. This is the default. |
class-type type |
(Optional) Requests the class type of the tunnel bandwidth. Range is 0 to 1. |
Defaults
The default is TE metric.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note New configurations do not affect tunnels that are already up.
Examples
The following example shows how to set the path-selection metric to use the IGP metric overwriting default:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection loose-expansion metric igp
Related Commands
path-selection metric (MPLS-TE)
To specify the MPLS-TE tunnel path-selection metric, use the path-selection metric command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
path-selection metric {igp | te}
no path-selection metric {igp | te}
Syntax Description
igp |
Configures an Interior Gateway Protocol (IGP) metric. |
te |
Configures a TE metric. This is the default variable. |
Defaults
The default is TE metric.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The metric type to be used for path calculation for a given tunnel is determined as follows:
•If the path-selection metric command was entered to specify a metric type for the tunnel, use that metric type.
•Otherwise, use the default (TE) metric.
Examples
The following example shows how to set the path-selection metric to use the IGP metric overwriting default:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection metric igp
Related Commands
path-selection metric (interface)
To specify an MPLS-TE tunnel path-selection metric type, use the path-selection metric command in interface configuration mode. To return to the default behavior, use the no form of this command.
path-selection metric {igp | te}
no path-selection metric {igp | te}
Syntax Description
igp |
Uses Interior Gateway Protocol (IGP) metrics. |
te |
Uses TE metrics. This is the default. |
Defaults
The default is TE metrics.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The metric type to be used for path calculation for a given tunnel is determined as follows:
•If the path-selection metric command was entered to specify either a metric type for the tunnel or only a metric type, use that metric type.
•Otherwise, use the default (TE) metric.
Examples
The following example shows how to designate that the MPLS-TE tunnel use the IGP metric for path selection:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# path-selection metric igp
Related Commands
pce address (MPLS-TE)
To configure the IPv4 self address for Path Computation Element (PCE), use the pce address command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
pce address ipv4 address
no pce address ipv4 address
Syntax Description
ipv4 address |
Configures the IPv4 address for PCE. |
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The IP address is used in the TCP communication with the other PCEs or PCCs. In addition, this address is advertised using IGP.
Examples
The following example shows how to configure the IPv4 self address for PCE:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce address ipv4 10.10.10.10
Related Commands
pce deadtimer (MPLS-TE)
To configure a path computation element (PCE) deadtimer, use the pce deadtimer command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.
pce deadtimer value
no pce deadtimer value
Syntax Description
value |
Keepalive dead interval, in seconds. The range is 0 to 255 seconds. |
Defaults
The default value is 120 seconds.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When the dead interval is 0, the LSR does not time out a PCEP session to a remote peer.
Examples
The following example shows how to configure a PCE deadtimer:
RP/0/0/CPU0:router# configure
RP/0/0/CPU0:router(config)# mpls traffic-eng
RP/0/0/CPU0:router(config-mpls-te)# pce deadtimer 50
Related Commands
pce keepalive (MPLS-TE)
To configure a path computation element protocol (PCEP) keepalive interval, use the pce keepalive command in MPLS-TE configuration mode. To disable this command, use the no form of this command.
pce keepalive interval
no pce keepalive interval
Syntax Description
interval |
Keepalive interval, in seconds. The range is 0 to 255. |
Defaults
The default value is 30 seconds.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When the keepalive interval is 0, the LSR does not send keepalive messages.
Examples
The following example shows how to configure PCEP keepalive interval for 10 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce keepalive 10
Related Commands
pce peer (MPLS-TE)
To configure an IPv4 self address for a path computation element (PCE) peer, use the pce peer command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
pce peer ipv4 address
no pce peer ipv4 address
Syntax Description
ipv4 address |
Configures the IPv4 address for PCE. |
Defaults
TE metric
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.5.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure an IPv4 self address for a PCE peer:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce peer ipv4 11.11.11.11
Related Commands
pce reoptimize (MPLS-TE)
To configure a periodic reoptimization timer, use the pce reoptimize command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.
pce reoptimize value
no pce reoptimize value
Syntax Description
value |
Periodic reoptimization timer value, in seconds. The range is 60 to 604800. |
Defaults
The default value is 3600 seconds.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When the dead interval is 0, the LSR does not time out a path computation element protocol (PCEP) session to a remote peer.
Examples
The following example shows how to configure a periodic reoptimization timer for 200 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce reoptimize 200
Related Commands
pce request-timeout (MPLS-TE)
To configure a path computation element (PCE) request-timeout, use the pce request-timeout command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.
pce request-timeout value
no pce request-timeout value
Syntax Description
value |
PCE request-timeout, in seconds. The range is 5 to 100. |
Defaults
The default value is 10 seconds.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
PCC or PCE keeps a pending path request only for the request-timeout period.
Examples
The following example shows how to configure a PCE request-timeout for 10 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce request-timeout 10
Related Commands
pce tolerance keepalive (MPLS-TE)
To configure a path computation element (PCE) tolerance keepalive (which is the minimum acceptable peer proposed keepalive), use the pce tolerance keepalive command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.
pce tolerance keepalive value
no pce tolerance keepalive value
Syntax Description
value |
PCE tolerance keepalive value, in seconds. The range is 0 to 255. |
Defaults
The default value is 10 seconds.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure a PCE tolerance keepalive for 10 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce tolerance keepalive 10
Related Commands
policy-class
To configure policy-based tunnel selection (PBTS) to direct traffic into specific TE tunnels, use the policy-class command in interface configuration mode. To disable this feature, use the no form of this command.
policy-class 1 - 7 [default]
no policy-class
Syntax Description
1 - 7 |
Policy-class-attribute to map the correct traffic class to this policy. |
default |
Configures a default class for PBTS. |
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
|
|
Release 3.6.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.7.0 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.8.0 |
No modification. |
Release 3.8.4 |
The default keyword was added. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the policy-class command to enable policy-based tunnel selection (PBTS). See Cisco IOS XR MPLS Configuration Guide for more information on PBTS.
To display the configured PBTS policy-class value, use the show mpls traffic-eng tunnels command.
To display information about PBTS configuration, use the show cef and show cef hardware commands in Cisco IOS XR IP Addresses and Service Command Reference.
The default class is not associated with any of the existing classes from 0 to 7. For a class of traffic that does not have a respective class tunnel, the forwarding place uses the available default tunnels and IGP and LDP paths can carry that class of traffic. The default traffic stream is load balanced over the default tunnels and IGP and LDP paths. Up to eight default tunnels are used to forward default traffic towards the destination.
Examples
The following example shows how to configure a policy class attribute of 7:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# policy-class 7
The following example shows how to configure a default tunnel policy class for PBTS:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# policy-class default
Related Commands
|
|
interface tunnel-te |
Configures an MPLS-TE tunnel interface. |
show cef |
Displays the IPv4 or IPv6 Cisco Express Forwarding table. |
show cef hardware |
Displays Cisco Express Forwarding IPv4 or IPv6 hardware status and configuration information. |
show mpls traffic-eng tunnels |
Displays information about MPLS-TE tunnels. |
priority (MPLS-TE)
To configure the setup and reservation priority for an MPLS-TE tunnel, use the priority command in interface configuration mode. To return to the default behavior, use the no form of this command.
priority setup-priority hold-priority
no priority setup-priority hold-priority
Syntax Description
setup-priority |
Priority used when signaling a label switched path (LSP) for this tunnel to determine which existing tunnels can be preempted. Range is 0 to 7 (in which a lower number indicates a higher priority). Therefore, an LSP with a setup priority of 0 can preempt any LSP with a non-0 priority. |
hold-priority |
Priority associated with an LSP for this tunnel to determine if it should be preempted by other LSPs that are being signaled. Range is 0 to 7 (in which a lower number indicates a higher priority). |
Defaults
setup-priority: 7
hold-priority: 7
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When an LSP is signaled and an interface does not currently have enough bandwidth available for that LSP, the call admission software (if necessary) preempts lower-priority LSPs to admit the new LSP. Accordingly, the new LSP priority is the setup priority and the existing LSP priority is the hold priority. The two priorities make it possible to signal an LSP with a low setup priority (so that the LSP does not preempt other LSPs on setup) and a high hold priority (so that the LSP is not preempted after it is established). Setup priority and hold priority are typically configured to be equal, and setup priority cannot be numerically smaller than the hold priority.
Examples
The following example shows how to configure a tunnel with a setup and hold priority of 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# priority 1 1
Related Commands
record-route
To record the route used by a tunnel, use the record-route command in interface configuration mode. To return to the default behavior, use the no form of this command.
record-route
no record-route
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note You must configure record-route on TE tunnels that are protected by multiple backup tunnels merging at a single node.
Examples
The following example shows how to enable record-route on the TE tunnel:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# record-route
Related Commands
remote (GMPLS)
To configure Link Management Protocol (LMP) Neighbor remote Traffic Engineering (TE) links, use the remote command in MPLS-TE interface LMP data link adjacency configuration mode. To return to the default behavior, use the no form of this command.
remote {interface-id unnum identifier | switching capability {fsc | lsc | psc1} | te-link-id {ipv4 address | unnum identifier}}
no remote {interface-id unnum identifier | switching capability {fsc | lsc | psc1} | te-link-id {ipv4 address | unnum identifier}}
Syntax Description
interface-id |
Configures the LMP neighbor remote interface identifier. |
unnum identifier |
Configures the unnumbered interface identifier. Range is 1 to 4294967295. |
switching-capability |
Configures the remote LMP MPLS-TE interface switching capability. |
fsc | lsc | psc1 |
Configures the capability types: Fiber-Switch Capable, Lambda-Switch Capable, Packet-Switch Capable. |
te-link-id |
Configures the remote LMP MPLS-TE link ID address. |
ipv4 address |
Configures the IPv4 address. |
unnum identifier |
Configures the unnumbered interface and identifier. |
Defaults
No default behavior or values
Command Modes
MPLS-TE interface LMP data link adjacency configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure LMP Neighbor remote TE links for unnumber interface-id 1066:
RP0/0/RP0/CPU0:router# configure
RP0/0/RP0/CPU0:router(config)# mpls traffic-eng
RP0/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/1/0/0
RP0/0/RP0/CPU0:router(config-mpls-te-if)# lmp data-link adjacency
RP0/0/RP0/CPU0:router(config-mpls-te-if-adj)# remote interface-path-id unnnum 1066
Related Commands
reoptimize (MPLS-TE)
To configure the reoptimization interval for all TE tunnels, use the reoptimize command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
reoptimize frequency
no reoptimize frequency
Syntax Description
frequency |
Timer frequency range in seconds. Range is 0 to 604800. |
Defaults
frequency: 3600
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure reoptimization interval to 60 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize 60
Related Commands
reoptimize timers delay (MPLS-TE)
To delay removal or relabeling of the old label switched paths (LSPs) (reoptimized LSP from the forwarding plane) after tunnel reoptimization, use the reoptimize timers delay command in MPLS-TE configuration mode. To restore the default value, use the no form of this command.
reoptimize timers delay {cleanup | installation} delay-time
no reoptimize timers delay {cleanup | installation} delay-time
Syntax Description
cleanup |
Delays removal of the old LSPs after tunnel reoptimization. |
installation |
Delays installation of a new label after tunnel reoptimization. |
delay-time |
Reoptimization delay time in seconds. A value of 0 disables delay. The valid range is from 0 to 300 seconds for cleanup time, and 0 to 3600 seconds for installation time. |
Defaults
delay-time: 20 seconds (for cleanup and installation)
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
A device with Multiprotocol Label Switching traffic engineering (MPLS-TE) tunnels periodically examines tunnels with established LSPs to discover if more efficient LSPs (paths) are available. If a better LSP is available, the device signals the more efficient LSP; if the signaling is successful, the device replaces the older LSP with the new, more efficient LSP.
Sometimes the slower router-point nodes may not yet utilize the new label's forwarding plane. In this case, if the headend node replaces the labels quickly, it can result in brief packet loss. By delaying the cleanup of the old LSP using the reoptimize timers delay cleanup command, packet loss is avoided.
Examples
The following example shows how to set the reoptimization cleanup delay time to 1 minute:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize timer delay cleanup 60
The following example shows how to set the reoptimization installation delay time to 1 hour:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize delay installation 3600
Related Commands
router-id secondary (MPLS-TE)
To configure a secondary TE router identifier in MPLS-TE to be used locally (not advertised through IGP), use the router-id secondary command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
router-id secondary A.B.C.D
no router-id secondary A.B.C.D
Syntax Description
A.B.C.D |
IPv4 address to be used as secondary TE router ID. |
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.4.1 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the router-id secondary command on tail end nodes to terminate verbatim tunnels to secondary TE RIDs as destinations.
You can configure up to 32 IPv4 addresses as TE secondary router IDs.
Examples
The following example shows how to configure a secondary TE router identifier in MPLS-TE:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# router-id secondary 1.1.1.1
RP/0/RP0/CPU0:router(config-mpls-te)# router-id secondary 2.2.2.2
Related Commands
show explicit-paths
To display the configured IP explicit paths, use the show explicit-paths command in EXEC mode.
show explicit-paths [path name | identifier number]
Syntax Description
path name |
(Optional) Displays the name of the explicit path. |
identifier number |
(Optional) Displays the number of the explicit path. Range is 1 to 65535. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
An IP explicit path is a list of IP addresses that represent a node or link in the explicit path.
Examples
The following is sample output from the show explicit-paths command:
RP/0/RP0/CPU0:router# show explicit-paths
0x1: next-address 192.168.1.2
0x2: next-address 10.20.20.20
0x1: next-address 192.168.1.2
0x2: next-address 192.168.2.2
0x3: next-address 10.30.30.30
0x1: next-address 192.168.1.2
0x2: next-address 10.20.20.20
0x1: next-address 192.168.1.2
0x2: next-address 192.168.2.2
0x3: next-address 10.30.30.30
Table 26 describes the significant fields shown in the display.
Table 26 show explicit-paths Field Descriptions
|
|
Path |
Pathname or number, followed by the path status. |
1: next-address |
First IP address in the path. |
2: next-address |
Second IP address in the path. |
The following is sample output from the show explicit-paths command using a specific path name:
RP/0/RP0/CPU0:router# show explicit-paths name ToR3
0x1: next-address 192.168.1.2
0x2: next-address 192.168.2.2
0x3: next-address 10.30.30.30
The following is sample output from the show explicit-paths command using a specific path number:
RP/0/RP0/CPU0:router# show explicit-paths identifier 200
0x1: next-address 192.168.1.2
0x2: next-address 192.168.2.2
0x3: next-address 10.30.30.30
Related Commands
show mpls traffic-eng affinity-map
To display the color name-to-value mappings configured on the router, use the show mpls traffic-eng affinity-map command in EXEC mode.
show mpls traffic-eng affinity-map
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If the affinity value of an affinity associated with an affinity constraint is unknown, the show mpls traffic-eng affinity-map command output displays: "(refers to undefined affinity name)"
Examples
The following is sample output from the show mpls traffic-eng affinity-map command:
RP/0/RP0/CPU0:router# show mpls traffic-eng affinity-map
Affinity Name Affinity Value
----------------- -----------------
Table 27 describes the significant fields shown in the display.
Table 27 show mpls traffic-eng affinity-map Field Descriptions
|
|
Affinity Name |
Displays the affinity name associated with the tunnel affinity constraints. |
Affinity Value |
Displays the affinity value associated with the tunnel affinity constraints. |
Related Commands
|
|
affinity |
Configures an affinity (the properties the tunnel requires in its links) for an MPLS-TE tunnel. |
affinity-map |
Assigns a numerical value to each affinity name. |
show mpls traffic-eng autoroute
To display tunnels that are announced to the Interior Gateway Protocol (IGP), including information about next hop and destinations, use the show mpls traffic-eng autoroute command in EXEC mode.
show mpls traffic-eng autoroute [A.B.C.D]
Syntax Description
A.B.C.D |
(Optional) Displays tunnels leading to this address. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The enhanced shortest path first (SPF) calculation of the IGP has been modified so that it uses traffic-engineering tunnels. The show mpls traffic-eng autoroute command displays those tunnels IGP is currently using in its enhanced SPF calculation (that is, which tunnels are up and have autoroute configured).
Examples
The following is sample output from the show mpls traffic-eng autoroute command:
RP/0/RP0/CPU0:router# show mpls traffic-eng autoroute
Destination 103.0.0.3 has 2 tunnels in OSPF 0 area 0
tunnel-te1 (traffic share 1, nexthop 103.0.0.3)
tunnel-te2 (traffic share 1, nexthop 103.0.0.3)
Table 28 describes the significant fields shown in the display.
Table 28 show mpls traffic-eng autoroute Field Descriptions
|
|
Destination |
Multiprotocol Label Switching (MPLS) TE tail-end router ID. |
traffic share |
A factor based on bandwidth, indicating how much traffic this tunnel should carry, relative to other tunnels, to the same destination. If two tunnels go to a single destination, one with a traffic share of 200 and the other with a traffic share of 100, the first tunnel carries two-thirds of the traffic. |
Nexthop |
Next-hop router ID of the MPLS-TE tunnel. |
absolute metric |
Metric with mode absolute for the MPLS-TE tunnel. |
relative metric |
Metric with mode relative for the MPLS-TE tunnel. |
Related Commands
|
|
autoroute metric |
Specifies the MPLS-TE tunnel metric that the IGP-enhanced SPF calculation will use. |
topology holddown sigerr (MPLS-TE) |
Specifies the time that a router should ignore a link in its TE topology database in tunnel path constrained shortest path first (CSPF) computations following a TE tunnel signalling error on the link. |
show mpls traffic-eng tunnels |
Displays information about MPLS-TE tunnels. |
show mpls traffic-eng counters signaling
To display tunnel signaling statistics, use the show mpls traffic-eng counters signaling command in EXEC mode.
show mpls traffic-eng counters signaling {tunnel number | all [heads | mids | tails] | name tunnel-name | summary}
Syntax Description
tunnel number |
Statistics for the input tunnel number. The range is 0 to 65535. |
all |
Displays statistics for all tunnels. |
heads |
(Optional) Displays statistics for all tunnel heads. |
mids |
(Optional) Displays statistics for all tunnel midpoints. |
tails |
(Optional) Displays statistics for all tunnel tails. |
name |
Displays statistics for a specified tunnel. |
tunnel-name |
Name of the specified tunnel. |
summary |
Displays a summary of signaling statistics. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
Support was added for the middles keyword. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The tunnel-name argument was added and the middles keyword was replaced with the mids keyword. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng counters signaling command, using the all keyword, which displays tunnel signaling statistics for all tunnels:
RP/0/RP0/CPU0:router# show mpls traffic-eng counters signaling all
Tunnel Head: tunnel-te160
Match Resv Create: 5 Sender Create: 4 Path Error: 0
Match Resv Change: 0 Sender Modify: 1 Path Change: 0
Match Resv Delete: 3 Sender Delete: 3 Path Delete: 1
Tunnel Head: tunnel-te170
Match Resv Create: 0 Sender Create: 0 Path Error: 0
Match Resv Change: 0 Sender Modify: 0 Path Change: 0
Match Resv Delete: 0 Sender Delete: 0 Path Delete: 0
The following is sample output from the show mpls traffic-eng counters signaling command using the tunnel number argument, which displays statistics for the input tunnel number:
RP/0/RP0/CPU0:router# show mpls traffic-eng counters signaling 1
Match Resv Create: 1 Sender Create: 1 Path Error: 0
Match Resv Change: 0 Sender Modify: 0 Path Change: 0
Match Resv Delete: 0 Sender Delete: 0 Path Delete: 0
Table 29 describes the significant fields shown in the display.
Table 29 show mpls traffic-eng counters signaling Field Descriptions
|
|
Tunnel Head |
Tunnel head identifier. |
Match Resv Create |
Number of RSVP Reservation create messages received. |
Sender Create |
Number of Sender Create messages sent by TE to RSVP. |
Path Error |
Number of RSVP Path Error messages received. |
Match Resv Change |
Number of RSVP Reservation change messages received. |
Sender Modify |
Number of Sender Modify messages sent by TE to RSVP. |
Path Change |
Number of RSVP Path Change messages received. |
Match Resv Delete |
Number of RSVP Reservation delete messages received. |
Sender Delete |
Number of Sender Delete messages sent by TE to RSVP. |
Path Delete |
Number of RSVP Path Delete messages received. |
Total |
Total signaling messages received from RSVP. |
Unknown |
Unknown messages include fast reroute events and internal messages related to process restart. |
Related Commands
show mpls traffic-eng ds-te te-class
To display the Diff-Serv TE-class map in use, use the show mpls traffic-eng ds-te te-class command in EXEC mode.
show mpls traffic-eng ds-te te-class
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note TE-class is used only in IETF DS-TE mode.
Examples
The following is sample output from the show mpls traffic-eng ds-te te-class command:
RP/0/RP0/CPU0:router# show mpls traffic-eng ds-te te-class
te-class 0: class-type 0 priority 7 status default
te-class 1: class-type 1 priority 7 status default
te-class 4: class-type 0 priority 0 status default
te-class 5: class-type 1 priority 0 status default
Table 30 describes the significant fields shown in the display.
Table 30 show mpls traffic-eng ds-te te-class Field Descriptions
|
|
te-class |
TE-class map, pair of class-type and priority. |
class-type |
class-type of the tunnel. |
status |
Source of the TE-class map, either default or user configured. |
show mpls traffic-eng forwarding
To display forwarding information on tunnels that were admitted locally, use the show mpls traffic-eng forwarding command in EXEC mode.
show mpls traffic-eng forwarding [interface type interface-path-id | detail | p2p]
Syntax Description
interface |
(Optional) Displays information on the specified interface. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or a virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
detail |
(Optional) Displays detailed forwarding information. |
p2p |
(Optional) Displays only Point-to-Point (P2P) information. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The following keywords were added: •detail •p2p |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng forwarding command:
RP/0/RP0/CPU0:router# show mpls traffic-eng forwarding
Bandwidth descriptor legend:
B0 = bw from pool 0, B1 = bw from pool 1, R = bw locked, H = bw held
TUNNEL ID UP IF DOWN IF LOC_LBL OUT_LBL Backup
---------------------- ---------- ------------ -------- -------- ----------
10.10.10.10 1_34 - PO0/2/0/1 0 61 tunnel-te15
10.10.10.10 15_2 - PO0/2/0/2 0 3 unknown
Table 31 describes the significant fields shown in the display.
Table 31 show mpls traffic-eng forwarding Field Descriptions
|
|
Tunnels Count |
Total number of tunnels admitted. |
Tunnels Selected |
Number of tunnels to be displayed. |
Bandwidth descriptor legend |
BW pool type and status displayed with the tunnel entry (see Table 33). |
TUNNEL ID |
Tunnel identification. |
UP IF |
Upstream interface that the tunnel used. |
DOWN IF |
Downstream interface used by the tunnel. |
PRIORITY |
Tunnel setup priority and hold priority. |
STATE |
Tunnel admission status. |
BW (kbps) |
Tunnel bandwidth in kilobits per second. If an R follows the bandwidth number, the bandwidth is reserved. If an H follows the bandwidth number, the bandwidth is temporarily being held for a Path message. If a B0 follows the bandwidth number, the bandwidth is from the global pool/class-type 0. If an B1 follows the bandwidth number the bandwidth is from the sub-pool/class-type 1. |
show mpls traffic-eng forwarding-adjacency
To display forwarding-adjacency information for an IPv4 address, use the show mpls traffic-eng forwarding-adjacency command in EXEC mode.
show mpls traffic-eng forwarding-adjacency [A.B.C.D]
Syntax Description
A.B.C.D |
(Optional) Destination IPv4 address for forwarding adjacency. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng forwarding-adjacency command:
RP/0/RP0/CPU0:router# show mpls traffic-eng forwarding-adjacency
destination 3.3.3.3 has 1 tunnels
tunnel-te1 (traffic share 0, next-hop 3.3.3.3)
(Adjacency Announced: yes, holdtime 0)
Related Commands
show mpls traffic-eng igp-areas
To display MPLS-TE internal area storage, use the show mpls traffic-eng igp-areas command in EXEC mode.
show mpls traffic-eng igp-areas
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
Sample output was modified so that the tunnels and links are not displayed in each area. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng igp-areas command:
RP/0/RP0/CPU0:router# show mpls traffic-eng igp-areas
Global router-id: 0.0.0.0
Global optical router-id: Not available
TE router ID configured: 101.0.0.1
Topology/tunnel connection: up
IGP config for TE: complete
Number of links in this IGP area: 1
Number of tunnel heads running over this IGP area: 0
Number of tunnel loose-hops expanded over this IGP area: 0
IGP config for TE: complete
Number of links in this IGP area: 1
Number of tunnel heads running over this IGP area: 0
Number of tunnel loose-hops expanded over this IGP area: 0
IGP config for TE: complete
Number of links in this IGP area: 1
Number of tunnel heads running over this IGP area: 0
Number of tunnel loose-hops expanded over this IGP area: 0
IGP config for TE: complete
Number of links in this IGP area: 1
Number of tunnel heads running over this IGP area: 0
Number of tunnel loose-hops expanded over this IGP area: 0
IGP config for TE: complete
Number of links in this IGP area: 2
Number of tunnel heads running over this IGP area: 1
Number of tunnel loose-hops expanded over this IGP area: 0
Table 32 describes the significant fields shown in the display.
Table 32 show mpls traffic-eng igp-areas Field Descriptions
|
|
Global router-id |
Global router ID on this node. |
IGP ID |
IGP System ID. |
area |
IGP area. |
TE index |
Internal index in the IGP area table. |
IGP config for TE |
Indicates whether the IGP configuration is complete or missing. |
show mpls traffic-eng link-management admission-control
To display which tunnels were admitted locally and their parameters, use the show mpls traffic-eng link-management admission-control command in EXEC mode.
show mpls traffic-eng link-management admission-control [interface type interface-path-id]
Syntax Description
interface |
(Optional) Displays information on the specified interface. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or a virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
Support was added for the Name-Based Affinity Constraint scheme. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng link-management admission-control command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management admission-control
Bandwidth descriptor legend:
B0 = bw from pool 0, B1 = bw from pool 1, R = bw locked, H = bw held
TUNNEL ID UP IF DOWN IF PRI STATE BW (kbits/sec)
------------------------ ---------- ---------- --- ------------- ---------------
10.10.10.10 1_34 - PO0/2/0/1 7/7 Resv Admitted 100 RB0
10.10.10.10 15_2 - PO0/2/0/2 7/7 Resv Admitted 0 B0
Table 33 describes the significant fields shown in the display.
Table 33 show mpls traffic-eng link-management admission-control Field Descriptions
|
|
Tunnels Count |
Total number of tunnels admitted. |
Tunnels Selected |
Number of tunnels displayed. |
Bandwidth descriptor legend |
BW pool type and status displayed with the tunnel entry. In the sample output above, shown as RG (Locked BW in global pool). |
TUNNEL ID |
Tunnel identification. |
UP IF |
Upstream interface used by the tunnel. |
DOWN IF |
Downstream interface used by the tunnel. |
PRIORITY |
Tunnel setup priority and hold priority. |
STATE |
Tunnel admission status. |
BW (kbps) |
Tunnel bandwidth in kilobits per second. If an R follows the bandwidth number, the bandwidth is reserved. If an H follows the bandwidth number, the bandwidth is temporarily being held for a Path message. If a G follows the bandwidth number, the bandwidth is from the global pool. If an S follows the bandwidth number the bandwidth is from the sub-pool. |
The following is sample output from the show mpls traffic-eng link-management interface command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management int pos 0/2/0/1
Link ID:: POS0/2/0/1 (35.0.0.5)
Link Label Type : PSC (inactive)
Physical BW : 155520 kbits/sec
Max Reservable BW : 0 kbits/sec (reserved: 100% in, 100% out)
BC0 (Res. Global BW): 0 kbits/sec (reserved: 100% in, 100% out)
BC1 (Res. Sub BW) : 0 kbits/sec (reserved: 100% in, 100% out)
MPLS-TE Link State : MPLS-TE on, RSVP on
Inbound Admission : allow-all
Outbound Admission : allow-if-room
Max Res BW (RDM) : 0 kbits/sec
Max Res BW (MAM) : 0 kbits/sec
Admin Weight : 1 (OSPF), 10 (ISIS)
Attributes : 0x5 (name-based)
Flooding Status: (1 area)
IGP Area[1]: ospf 100 area 0, not flooded
(Reason: Interface has been administratively disabled)
Table 34 describes the significant fields shown in the display.
Table 34 show mpls traffic-eng link-management interface Field Descriptions
|
|
Links Count |
Number of links configured for MPLS-TE. |
Link ID |
Index of the link described. |
Local Intf ID |
Local interface ID. |
Link Label Type |
Label type of the link, for instance: PSC1 , TDM2 , FSC3 . |
Physical BW |
Link bandwidth capacity (in kilobits per second). |
BCID |
Bandwidth constraint model ID, RDM, or MAM. |
Max Reservable BW |
Maximum reservable bandwidth on this link. |
BC0 (Res. Global BW) |
Bandwidth constraint value for class-type 0. |
BC1 (Res. Sub BW) |
Bandwidth constraint value for class-type 1. |
MPLS-TE Link State |
Status of the link MPLS-TE-related functions. |
Inbound Admission |
Link admission policy for incoming tunnels. |
Outbound Admission |
Link admission policy for outgoing tunnels. |
IGP Neighbor Count |
IGP neighbors directly reachable over this link. |
Max Res BW (RDM) |
Maximum reservable bandwidth on this link for RDM. |
BC0 (RDM) |
Bandwidth constraint value for RDM. |
BC1 (RDM) |
Bandwidth constraint value for RDM. |
Admin Weight |
Administrative weight associated with this link. |
Attributes |
Interface attributes referring to one or more affinity names. |
IGP Area[1] |
IGP type and area and level used for TE flooding. |
show mpls traffic-eng link-management advertisements
To display local link information that MPLS-TE link management is currently flooding into the global TE topology, use the show mpls traffic-eng link-management advertisements command in EXEC mode.
show mpls traffic-eng link-management advertisements
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
This command was modified to include information specific to MPLS Shared Risk Link Groups (SRLG). |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The show mpls traffic-eng link-management advertisements command has two output formats depending on the Diff-Serv TE Mode: one for prestandard mode and one for IETF mode.
The SRLG values are advertised for the link.
Examples
The following is the sample output from the show mpls traffic-eng link-management advertisements command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link management advertisements
Last Flooding : 50 seconds ago
Last Flooding Trigger : TE Link came Up
Next Periodic Flooding In : 70 seconds
Diff-Serv TE Mode : Not enabled
IGP Area[1]:: IS-IS test level 1
Flooding Protocol : IS-IS
IGP System ID : 0000.0000.0010
MPLS TE Router ID : 192.168.0.145
Link IP Address : 10.3.11.145
Neighbor : ID 0000.0000.0234.00, IP 10.3.11.143
Physical BW : 155520 kbits/sec
Max Reservable BW : 0 kbits/sec
Res Global BW : 0 kbits/sec
Reservable BW[0]: 0 0 kbits/sec
Reservable BW[1]: 0 0 kbits/sec
Reservable BW[2]: 0 0 kbits/sec
Reservable BW[3]: 0 0 kbits/sec
Reservable BW[4]: 0 0 kbits/sec
Reservable BW[5]: 0 0 kbits/sec
Reservable BW[6]: 0 0 kbits/sec
Reservable BW[7]: 0 0 kbits/sec
Attribute Flags: 0x00000000
Table 35 describes the significant fields shown in the display.
Table 35 show mpls traffic-eng link-management advertisements Field Descriptions
|
|
Flooding Status |
Status of the link management flooding system. |
Last Flooding |
Number of seconds since the last flooding occurred. |
Last Flooding Trigger |
Description of last flooding event triggering the flooding. |
Next Periodic Flooding In |
Number of seconds until TE floods the LSA1 . |
Diff-Serv TE Mode |
Diff-Serv TE mode, prestandard or IETF. |
Configured Areas |
Number of the configured IGP2 areas. |
IGP Area [1] ID |
Name of the first IGP area. |
Flooding Protocol |
IGP that is flooding information for this area. |
IGP System ID |
Identification that IGP flooding uses in this area to identify this node. |
MPLS-TE Router ID |
MPLS-TE router ID. |
Flooded Links |
Number of links flooded in this area. |
Link ID |
Index of the link described. |
Link IP Address |
Local IP address of the link. |
Neighbor |
IGP neighbor. |
TE Metric |
Metric value for the TE link configured under MPLS-TE. |
IGP Metric |
Metric value for the TE link configured under IGP. |
Physical BW |
Link bandwidth capacity (in kilobits per second). |
BCID |
ID of the bandwidth constraints model, RDM or MAM. |
Max Reservable BW |
Maximum reservable bandwidth on this link. |
Res Global BW |
Maximum reservable of global pool /BC0 bandwidth on this link. |
Res Sub BW |
Reservable sub-bandwidth for sub-pool /BC1 bandwidth on this link. |
SRLGs3 |
Links that share a common fiber or a common physical attribute. If one link fails, other links in the group may also fail. Links in the group have a shared risk. |
Downstream |
Direction of the LSP path message. |
Reservable BW[x] |
Bandwidth available for reservations in the global TE topology and sub-pools. |
Attribute Flags |
Link attribute flags being flooded. |
BC0 |
Bandwidth constraint value for class-type 0 |
BC1 |
Bandwidth constraint value for class-type 1 |
TE-class [index] |
TE-class configured on this router at given index (mapping of class-type and priority), shows available bandwidth in that class. |
show mpls traffic-eng link-management bandwidth-allocation
To display current local link information, use the show mpls traffic-eng link-management bandwidth-allocation command in EXEC mode.
show mpls traffic-eng link-management bandwidth-allocation [interface type interface-path-id]
Syntax Description
interface |
(Optional) Displays information on the specified interface. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or a virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Advertised and current information may differ depending on how flooding is configured.
Examples
The following is sample output from the show mpls traffic-eng link-management bandwidth-allocation command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link bandwidth-allocation interface POS
0/2/0/1
Bandwidth Hold time : 15 seconds
Link ID:: POS0/2/0/1 (7.2.2.1)
Physical BW : 155520 kbits/sec
Max Reservable BW : 1000 kbits/sec (reserved: 0% in, 0% out)
BC0 : 600 kbits/sec (reserved: 2% in, 2% out)
BC1 : 400 kbits/sec (reserved: 0% in, 0% out)
MPLS-TE Link State : MPLS-TE on, RSVP on, admin-up, flooded
Inbound Admission : allow-all
Outbound Admission : allow-if-room
BW Descriptors : 1 (including 0 BC1 descriptors)
Admin Weight : 1 (OSPF), 10 (ISIS)
Up Thresholds : 15 30 45 60 75 80 85 90 95 96 97 98 99 100 (default)
Down Thresholds : 100 99 98 97 96 95 90 85 80 75 60 45 30 15 (default)
Downstream BC0 (kbits/sec):
KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED
------------- ---------- ------------- ---------- ---------------
Downstream BC1 (kbits/sec):
KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED
------------- ---------- ------------- ---------- ---------------
Table 36 describes the significant fields shown in the display.
Table 36 show mpls traffic-eng link-management bandwidth-allocation Field Descriptions
|
|
Links Count |
Number of links configured for MPLS-TE. |
Bandwidth Hold Time |
Time (in seconds) that bandwidth can be held. |
Link ID |
Interface name and IP address of the link. |
Link Label type |
Label type of the link, for example: •PSC1 •TDM2 •FSC3 |
Physical BW |
Link bandwidth capacity (in bits per second). |
BCID |
Bandwidth constraints model ID, RDM or MAM |
Max Reservable BW |
Maximum reservable bandwidth on this link. |
BC0 |
Maximum RSVP bandwidth in BC0. |
BC1 |
Maximum RSVP bandwidth in BC1. |
BW Descriptors |
Number of bandwidth allocations on this link. |
MPLS-TE Link State |
Status of the link MPLS-TE-related functions. |
Inbound Admission |
Link admission policy for incoming tunnels. |
Outbound Admission |
Link admission policy for outgoing tunnels. |
IGP Neighbor Count |
IGP neighbors directly reachable over this link. |
BW Descriptors |
Internal bandwidth descriptors created when tunnels are admitted. |
Admin Weight |
Administrative weight associated with this link. |
Up Thresholds |
Threshold values used to determine link advertisement when available bandwidth increases. |
Down Thresholds |
Threshold values used to determine link advertisement when available bandwidth decreases. |
show mpls traffic-eng link-management bfd-neighbors
To display TE-enabled Bidirectional Forwarding Detection (BFD) neighbors, use the show mpls traffic-eng link-management bfd-neighbors command in EXEC mode.
show mpls traffic-eng link-management bfd-neighbors [interface type interface-path-id]
Syntax Description
interface |
(Optional) Displays information about the specified interface. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or a virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.2 |
This command was introduced on the Cisco CRS-1. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
The interface keyword was added. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng link-management bfd-neighbors command:
BFD Neighbor Address: 7.3.3.1, State: Up
BFD Neighbor Address: 7.4.4.1, State: Down
Table 37 describes the significant fields shown in the display.
Table 37 show mpls traffic-eng link-management bfd Field Descriptions
|
|
Link ID |
Link by which the neighbor is reached. |
BFD Neighbor Address |
Neighbor address and Up/Down state. |
Related Commands
|
|
bfd fast-detect (MPLS-TE) |
Enables BFD for communication failure detection. |
bfd minimum-interval (MPLS-TE) |
Sets the BFD interval. |
bfd multiplier (MPLS-TE) |
Sets the BFD multiplier. |
show mpls traffic-eng link-management igp-neighbors
To display Interior Gateway Protocol (IGP) neighbors, use the show mpls traffic-eng link-management igp-neighbors command in EXEC mode.
show mpls traffic-eng link-management igp-neighbors [igp-id {isis | ospf ospf-id} | interface type interface-path-id | A.B.C.D]
Syntax Description
igp-id |
(Optional) Displays the IGP neighbors that are using a specified IGP identification. |
isis isis-address |
(Optional) Displays the specified Intermediate System-to-Intermediate System (IS-IS) neighbor when neighbors are displayed by IGP ID. |
ospf ospf-id |
(Optional) Displays the specified Open Shortest Path first (OSPF) neighbor when neighbors are displayed by IGP ID. |
interface |
(Optional) Displays information on the specified interface. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or a virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
A.B.C.D |
(Optional) IGP neighbors that are using a specified IGP IP address. |
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng link-management igp-neighbors command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link igp-neighbors
Neighbor ID: 10.90.90.90 (area: ospf area 0, IP: 10.15.12.2)
Table 38 describes the significant fields shown in the display.
Table 38 show mpls traffic-eng link-management igp-neighbors Field Descriptions
|
|
Link ID |
Link by which the neighbor is reached. |
Neighbor ID |
IGP identification information for the neighbor. |
show mpls traffic-eng link-management interfaces
To display interface resources, or a summary of link management information, use the show mpls traffic-eng link-management interfaces command in EXEC mode.
show mpls traffic-eng link-management interfaces [type interface-path-id]
Syntax Description
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.4.1 |
No more than 100 links can be configured under MPLS-TE/Fast Reroute (FRR). |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
This command was modified to include information specific to MPLS Shared Risk Link Groups (SRLG). |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You cannot configure more than 100 links under MPLS-TE.
SRLG values can be configured for the link.
Examples
The following sample output is from the show mpls traffic-eng link-management interfaces command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management interfaces pos 0/2/0/1
Links Count : 3 (Maximum Links Supported 100)
Link ID:: POS0/6/0/0 (50.2.3.2)
Physical BW : 155520 kbits/sec
Max Reservable BW : 10000 kbits/sec (reserved: 90% in, 90% out)
BC0 (Res. Global BW): 10000 kbits/sec (reserved: 90% in, 90% out)
BC1 (Res. Sub BW) : 0 kbits/sec (reserved: 100% in, 100% out)
MPLS TE Link State : MPLS TE on, RSVP on, admin-up
Inbound Admission : allow-all
Outbound Admission : allow-if-room
Max Res BW (RDM) : 10000 kbits/sec
BC0 (RDM) : 10000 kbits/sec
Max Res BW (MAM) : 0 kbits/sec
Flooding Status: (2 area)
IGP Area[1]: IS-IS 0 level 1, flooded
Nbr: ID 0003.0003.0003.00, IP 50.2.3.3 (Up)
Admin weight: not set (TE), 10 (IGP)
IGP Area[2]: OSPF 0 area 0, flooded
Nbr: ID 10.0.0.3, IP 50.2.3.3 (Up)
Admin weight: not set (TE), 1 (IGP)
Table 39 describes the significant fields shown in the display.
Table 39 show mpls traffic-eng link-management interfaces Field Descriptions
|
|
Links Count |
Number of links configured for MPLS-TE. Maximum number of links supported is 100. |
Link ID |
Link identification index. |
Link Label Type |
Label type assigned to the link. |
Physical Bandwidth |
Link bandwidth capacity (in kilobits per second). |
BCID |
Bandwidth constraint model ID, RDM or MAM. |
Max Reservable BW |
Maximum reservable bandwidth on this link. |
BC0 |
Reservable bandwidth (in kbps) on this link in BC0. |
BC1 |
Reservable bandwidth (in kbps) on this link in BC1. |
SRLGs1 |
Links that share a common fiber or a common physical attribute. If one link fails, other links in the group may also fail. Links in the group have a shared risk. |
MPLS-TE Link State |
Status of the MPLS link. |
Inbound Admission |
Link admission policy for inbound tunnels. |
Outbound Admission |
Link admission policy for outbound tunnels. |
IGP Neighbor Count |
IGP2 neighbors directly reachable over this link. |
Admin. Weight |
Administrative weight associated with this link. |
Neighbors |
Neighbor on this link. |
Flooding Status |
Status for each configured area or Flooding status for the configured area. |
IGP Area |
IGP type and area and level used for TE flooding. |
show mpls traffic-eng link-management statistics
To display interface resources or a summary of link management information, use the show mpls traffic-eng link-management statistics command in EXEC mode.
show mpls traffic-eng link-management statistics [summary | interface type interface-path-id]
Syntax Description
summary |
(Optional) Displays the statistics summary. |
interface |
(Optional) Displays the interface for which information is requested. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The show mpls traffic-eng link-management statistics command displays resource and configuration information for all configured interfaces.
Examples
The following is sample output from the show mpls traffic-eng link-management statistics command using the summary keyword:
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management statistics summary
LSP Admission Statistics:
Setup Setup Setup Setup Tear Tear Tear
Requests Admits Rejects Errors Requests Preempts Errors
-------- -------- -------- -------- -------- -------- --------
Table 40 describes the significant fields shown in the display.
Table 40 show mpls traffic-eng link-management statistics summary Field Descriptions
|
|
Path |
Path information. |
Resv |
Reservation information. |
Setup Requests |
Number of requests for a setup. |
Setup Admits |
Number of admitted setups. |
Setup Rejects |
Number of rejected setups. |
Setup Errors |
Number of setup errors. |
Tear Requests |
Number of tear requests. |
Tear Preempts |
Number of paths torn down due to preemption. |
Tear Errors |
Number of tear errors. |
show mpls traffic-eng link-management summary
To display a summary of link management information, use the show mpls traffic-eng link-management summary command in EXEC mode.
show mpls traffic-eng link-management summary
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.4.1 |
No more than 100 links can be configured for MPLS-TE Fast Reroute (FRR). |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
You cannot configure more than 100 links for MPLS-TE/FRR.
Examples
The following sample output is from the show mpls traffic-eng link-management summary command:
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management summary
Links Count : 6 (Maximum Links Supported 100)
Flooding System : enabled
IGP Area[1]:: isis level-2
Flooding Status : flooded
Periodic Flooding : enabled (every 180 seconds)
IGP System ID : 0000.0000.0002.00
MPLS-TE Router ID : 20.20.20.20
IGP Area[2]:: ospf area 0
Flooding Status : flooded
Periodic Flooding : enabled (every 180 seconds)
IGP System ID : 20.20.20.20
MPLS-TE Router ID : 20.20.20.20
Table 41 describes the significant fields shown in the display.
Table 41 show mpls traffic-eng link-management summary Field Descriptions
|
|
Links Count |
Number of links configured for MPLS-TE. Maximum number of links supported is 100. |
Flooding System |
Enable status of the MPLS-TE flooding system. |
IGP Areas Count |
Number of IGP1 areas described. |
IGP Area |
IGP type and area and level used for TE flooding. |
Flooding Protocol |
IGP flooding information for this area. |
Flooding Status |
Status of flooding for this area. |
Periodic Flooding |
Status of periodic flooding for this area. |
Flooded Links |
Links that were flooded. |
IGP System ID |
IGP for the node associated with this area. |
MPLS-TE Router ID |
MPLS-TE router ID for this node. |
IGP Neighbors |
Number of reachable IGP neighbors associated with this area. |
show mpls traffic-eng lmp
To display operation details about the status of the Link Management Protocol (LMP) instance and neighbor, IPCC, and MPLS-TE links, use the show mpls traffic-eng lmp command in EXEC mode.
show mpls traffic-eng lmp [interface type interface-path-id | ipcc | neighbor [name] | statistics]
Syntax Description
interface |
(Optional) Displays information on the specified interface. |
type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
interface-path-id |
Physical interface or virtual interface. Note Use the show interfaces command to see a list of all interfaces currently configured on the router. For more information about the syntax for the router, use the question mark (?) online help function. |
ipcc |
(Optional) Displays information for LMP Internet Protocol Control Channel (IPCC). |
neighbor [name] |
(Optional) Displays information for the LMP neighbor. |
statistics |
(Optional) Displays information for the statistics. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output shows summary information for the local LMP protocol. One remote LMP neighbor named gmpls4 with the node ID 44.44.44.44. The neighbor has one MPLS-TE link (GigabitEthernet0/5/0/1) that has a local MPLS-TE link ID of 10.5.1.4, a data link ID of 21, and the data link LMP state is "Up Allocated", which means that the LMP state is up and is being used by the GMPLS protocol as part of an optical tunnel.
RP/0/RP0/CPU0:router# show mpls traffic-eng lmp
MPLS TE LMP Node ID: 11.11.11.11
Name: gmpls4, IP: 44.44.44.44, Owner: MPLS TE
LMP Hellos: Enabled by configuration
Known via : Configuration
Destination IP : 44.44.44.44
Data Link I/F | Lcl Data Link ID | Lcl TE Link ID | Data Link LMP state
----------------------+-------------------+----------------+--------------------
GigabitEthernet0/5/0/1 21 10.5.1.4 Up Allocated
The following sample output shows that one routed IPCC to LMP neighbor, gmpls4, is in the up state and has ID of 1:
RP/0/RP0/CPU0:router# show mpls traffic-eng lmp ipcc
ID | Type | IP | Status | Name
-----+---------------+---------------+--------------+---------------
1 Routed 44.44.44.44 Up gmpls4
The following sample output shows the IPCC and MPLS-TE link information for all the configured LMP neighbors:
RP/0/RP0/CPU0:router# show mpls traffic-eng lmp neighbor
Name: gmpls4, IP: 44.44.44.44, Owner: MPLS TE
LMP Hellos: Enabled by configuration
Known via : Configuration
Destination IP : 44.44.44.44
Data Link I/F | Lcl Data Link ID | Lcl TE Link ID | Data Link LMP state
----------------------+-------------------+----------------+--------------------
GigabitEthernet0/5/0/1 21 10.5.1.4 Up Allocated
The following sample output shows IPCC and MPLS-TE link information for a specified LMP neighbor, gmpls4:
RP/0/RP0/CPU0:router# show mpls traffic-eng lmp neighbor gmpls4
Name: gmpls4, IP: 44.44.44.44, Owner: MPLS TE
LMP Hellos: Enabled by configuration
Known via : Configuration
Destination IP : 44.44.44.44
Data Link I/F | Lcl Data Link ID | Lcl TE Link ID | Data Link LMP state
----------------------+-------------------+----------------+--------------------
GigabitEthernet0/5/0/1 21 10.5.1.4 Up Allocated
The following sample output shows detailed information for MPLS-TE, data link, and IPCC properties for a specified local interface that is configured as an LMP MPLS-TE link:
RP/0/RP0/CPU0:router# show mpls traffic-eng lmp interface gigabitEthernet 0/5/0/1
Interface: GigabitEthernet0/5/0/1
LMP Link Summary Last Error(s): None
Local data link ID type: Unnumbered
Local data link ID: Dec = 21, Hex = 0x15
Local TE link ID type: IPv4
Local TE link ID: 10.5.1.4
Local TE link switching capability: Packet-Switch Capable-1 (PSC-1)
Remote neighbor name: gmpls4
Remote neighbor node ID: 44.44.44.44
Remote TE link ID type: IPv4
Remote TE link ID: 10.5.1.1
Remote data link ID type: Unnumbered
Remote data link ID: Dec = 13, Hex = 0xd
Remote TE link switching capability: Packet-Switch Capable-1 (PSC-1)
Data link LMP state: Up/Allocated
Data link allocation status: Allocated
IPCC destination IP address: 44.44.44.44
Local Min Reservable Bandwidth: 125000000 bytes/sec
Local Max Reservable Bandwidth: 125000000 bytes/sec
Nbr Min Reservable Bandwidth: 125000000 bytes/sec
Nbr Max Reservable Bandwidth: 125000000 bytes/sec
Local Link Encoding Type: Ethernet
Nbr Link Encoding Type: Ethernet
VRF ID: Default [0x60000000] (Supported)
The following sample output shows detailed LMP protocol signaling statistics per neighbor and for all MPLS-TE links if LMP is running in nonstatic mode:
RP/0/RP0/CPU0:router# show mpls traffic-eng lmp statistics
Name: gmpls4, IP: 44.44.44.44, Owner: MPLS TE
Link Summ msgs Transmitted: 32
Link Summ msgs Received: 33
Hello Interval: 2000 (msec)
Minimum Acceptable Hello Interval: 100 (msec)
Maximum Acceptable Hello Interval: 21845 (msec)
Hello Dead Interval: 6000 (msec)
Minimum Acceptable Hello Dead Interval: 300 (msec)
Maximum Acceptable Hello Dead Interval: 65535 (msec)
No. of packets transmitted: 380
No. of packets Received: 377
Link Summ msgs Transmitted: 32
Link Summ msgs Received: 33
Data Link I/F | Lcl Data Link ID | Lcl TE Link ID | Rcvd_Msg_Id Xmt_Msg_Id
----------------------+-------------------+----------------+-----------------------
GigabitEthernet0/5/0/1 21 10.5.1.4 33 33
Related Commands
|
|
ipcc interface (MPLS-TE) |
Configures an interface-bounded Internet Protocol Control Channel (IPCC). |
lmp neighbor |
Configure or updates a LMP neighbor and its associated parameters and enters MPLS-TE neighbor configuration mode. |
show mpls traffic-eng maximum tunnels
To display the maximum number of MPLS-TE tunnels that you can configure, use the show mpls traffic-eng maximum tunnels command in EXEC mode.
show mpls traffic-eng maximum tunnels
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
Sample output was modified. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng maximum tunnels command:
RP/0/RP0/CPU0:router# show mpls traffic-eng maximum tunnels
Maximum Global Tunnel Count:
Maximum Global Destination Count:
Table 42 describes the significant fields shown in the display.
Table 42 show mpls traffic-eng maximum tunnels Field Descriptions
|
|
Maximum Global Tunnel Count |
Maximum number of tunnel interfaces (all TE tunnel types, tunnel-te, and tunnel-gte) that can be configured. |
Maximum Global Destination Count |
Maximum number of tunnel destinations that can be configured. |
Maximum |
Table heading for the maximum number in each category. |
Current Count |
Table heading for the current count in each category. |
Related Commands
|
|
maxabs (MPLS-TE) |
Specifies the maximum number of tunnel TE interfaces that can be configured. |
show mpls traffic-eng pce peer
To display the status of the path computation element (PCE) peer address and state, use the show mpls traffic-eng pce peer command in EXEC mode.
show mpls traffic-eng pce peer [address | all]
Syntax Description
address |
(Optional) IPv4 peer address for the PCE. |
all |
(Optional) Displays all the peers for the PCE. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output shows the status of both the PCE peer and state:
RP/0/RP0/CPU0:router# show mpls traffic-eng pce peer
PCEP has been up for: 04:18:31
Time out peer if no KA received for 120 s
Tolerance: Minimum KA 10 s
KA messages rxed 518 txed 517
PCEReq messages rxed 0, txed 0
PCERep messages rxed 0, txed 0
PCEErr messages rxed 0, txed 0
Last error received: None
PCE OPEN messages: rxed 1, txed 2
PCEP session ID: local 0, remote 0
Average reply time from peer: 0 ms
Minimum reply time from peer: 0 ms
Maximum reply time from peer: 0 ms
0 requests timed out with this peer
Transmit TCP buffer: Current 0, Maximum 12
Receive TCP buffer: Current 0, Maximum 12
Table 43 describes the significant fields shown in the display.
Table 43 show mpls traffic-eng pce peer Field Descriptions
|
|
KA |
PCEP keepalive. |
Learned through |
Learned through is how the peer was learned which is either through a static configuration or an IGP. |
Average reply time from peer |
Average reply time for the peer to respond to PCEReq request messages with PCERep response messages. |
Minimum reply time from peer |
Minimum reply time for the peer to respond to PCEReq request messages with PCERep response messages. |
Maximum reply time from peer |
Maximum reply for the peer to respond to PCEReq request messages with PCERep response messages. |
Transmit TCP buffer Receive TCP Buffer |
Number of messages that are in the TCP buffer with the peer waiting to be sent or processed locally. |
0 requests timed out with this peer |
Number of PCEReq messages that timed out waiting for a response from this peer. |
Related Commands
show mpls traffic-eng pce tunnels
To display the status of the path computation element (PCE) tunnels, use the show mpls traffic-eng pce tunnels command in EXEC mode.
show mpls traffic-eng pce tunnels [tunnel ID]
Syntax Description
tunnel ID |
(Optional) Tunnel identifier. The range is 0 to 4294967295. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following sample output shows the status of the PCE tunnels:
RP/0/RP0/CPU0:router# show mpls traffic-eng pce tunnels
Destination : 205.205.10.10
State : down, PCE failed to find path
Current path option: 10, path obtained from dynamically learned PCE 1.2.3.4
Table 44 describes the significant fields shown in the display.
Table 44 show mpls traffic-eng pce tunnels Field Descriptions
|
|
Tunnel |
Tunnel number for the MPLS-TE tunnel interface. |
Destination |
IP address of the destination of the tunnel. |
State |
State of the tunnel. Values are up, down, or admin-down. |
Admin weight |
Administrative weight (cost) of the link. |
Related Commands
show mpls traffic-eng topology
To display the MPLS-TE network topology currently known at this node, use the show mpls traffic-eng topology command in EXEC mode.
show mpls traffic-eng topology [path destination A.B.C.D [affinity number mask number | bandwidth number | priority level] | tunnel tunnel-number] | [isis nsap-address | ospf ospf-address {router | network}] [A.B.C.D] [brief] [model-type {rdm | mam}]
Syntax Description
path destination |
(Optional) Displays the path to a destination from this router. |
A.B.C.D |
(Optional) Node IP address (router identifier to interface address). |
affinity number |
(Optional) Displays the attribute values that are required for links carrying this tunnel. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1. |
mask number |
(Optional) Displays the link attribute to be checked. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute mask is 0 or 1. |
bandwidth number |
(Optional) Displays the bandwidth value that is required by this label switched path (LSP). |
priority level |
(Optional) Displays the priority used when signaling an LSP for this tunnel to determine which existing tunnels can be preempted. |
tunnel tunnel-number |
(Optional) Displays the path of a tunnel from this route. Range is 0 to 65535. |
isis nsap-address |
(Optional) Displays the node router identification, if Intermediate System-to-Intermediate System (IS-IS) is enabled. |
ospf ospf-address |
(Optional) Displays the node router identifier, if Open Shortest Path First (OSPF) is enabled. |
router |
Displays the given OSPF address type of the router node. |
network |
Displays the given OSPF address type of the network node. |
brief |
(Optional) Displays the brief form of the output that provides a less detailed version of the topology. |
model-type {rdm | mam} |
(Optional) Displays the bandwidth constraints model type, RDM or MAM. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
This command was modified to include information specific to MPLS Shared Risk Link Groups (SRLG). |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng topology command specifying the tunnel number in brief form:
RP/0/RP0/CPU0:router# show mpls traffic-eng topology path tunnel 160
Tunnel160 Path Setup to 10.10.10.10: FULL_PATH
bw 100 (CT0), min_bw 0, metric: 10
affinity_bits 0x0, affinity_mask 0xffff
The following is sample output from the show mpls traffic-eng topology command specifying the destination IP address:
RP/0/RP0/CPU0:router# show mpls traffic-eng topology path destination 10.10.10.10
Path Setup to 10.10.10.10:
bw 0 (CT0), min_bw 999900, metric: 10
affinity_bits 0x0, affinity_mask 0xffffffff
The following is sample output from the show mpls traffic-eng topology command in detail form in prestandard DS-TE mode:
RP/0/RP0/CPU0:router# show mpls traffic-eng topology
My_System_id: 0000.0000.0002.00 (isis level-2)
My_System_id: 20.20.20.20 (ospf area 0)
Signalling error holddown: 10 sec Global Link Generation 36
IGP Id: 0000.0000.0002.00, MPLS-TE Id: 20.20.20.20 Router Node (isis level-2)
Link[0]:Point-to-Point, Nbr IGP Id:0000.0000.0003.00, Nbr Node Id:3, gen:36
Frag Id:0, Intf Address:7.3.3.1, Intf Id:0
Nbr Intf Address:7.3.3.2, Nbr Intf Id:0
TE Metric:10, IGP Metric:10, Attribute Flags:0x0
Switching Capability:, Encoding:
Physical BW:155520 (kbps), Max Reservable BW Global:100000 (kbps)
Max Reservable BW Sub:50000 (kbps)
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
The following is sample output from the show mpls traffic-eng topology command in detail form in IETF DS-TE mode.
RP/0/RP0/CPU0:router# show mpls traffic-eng topology
My_System_id: 0000.0000.0001.00 (isis 1 level-2)
My_System_id: 10.10.10.10 (ospf 100 area 0)
Signalling error holddown: 10 sec Global Link Generation 84
IGP Id: 0000.0000.0001.00, MPLS-TE Id: 10.10.10.10 Router Node (isis 1 level-2)
Link[0]:Point-to-Point, Nbr IGP Id:0000.0000.0002.00, Nbr Node Id:6, gen:84
Frag Id:0, Intf Address:7.2.2.1, Intf Id:0
Nbr Intf Address:7.2.2.2, Nbr Intf Id:0
TE Metric:10, IGP Metric:10, Attribute Flags:0x0
Switching Capability:, Encoding:
Physical BW:155520 (kbps), Max Reservable BW:1000 (kbps)
BC0:600 (kbps) BC1:400 (kbps)
Total Allocated Reservable
--------------- -----------
Link[1]:Point-to-Point, Nbr IGP Id:0000.0000.0002.00, Nbr Node Id:6, gen:84
Frag Id:0, Intf Address:7.1.1.1, Intf Id:0
Nbr Intf Address:7.1.1.2, Nbr Intf Id:0
TE Metric:10, IGP Metric:10, Attribute Flags:0x0
Switching Capability:, Encoding:
Physical BW:155520 (kbps), Max Reservable BW:1000 (kbps) BC0:600 (kbps) BC1:400
(kbps)
Total Allocated Reservable
--------------- -----------
The following is sample output for the show mpls traffic-eng topology command in brief form:
RP/0/RP0/CPU0:router# show mpls traffic-eng topology 192.168.0.145 brief
IGP Id: 0000.0000.0010.00, MPLS TE Id: 192.168.0.145 Router Node (ISIS test level-1)
Link[0]:Point-to-Point, Nbr IGP Id:0000.0000.0234.00, Nbr Node Id:4, gen:5
Frag Id:0, Intf Address:10.3.11.145, Intf Id:0
Nbr Intf Address:10.3.11.143, Nbr Intf Id:0
TE Metric:10, IGP Metric:10, Attribute Flags:0x0
Switching Capability:, Encoding:
Physical BW:155520 (kbps), Max Reservable BW Global:0 (kbps)
Max Reservable BW Sub:0 (kbps)
The following is sample output for the show mpls traffic-eng model-type mam command:
RP/0/RP0/CPU0:router# show mpls traffic-eng topology model-type mam
IGP Id: 0000.0000.0001.00, MPLS-TE Id: 10.10.10.10 Router Node (isis 1 level-2)
Link[0]: Intf Address:7.2.2.1, Nbr Intf Address:7.2.2.2
Link[1]: Intf Address:7.1.1.1, Nbr Intf Address:7.1.1.2
IGP Id: 0000.0000.0002.00, MPLS-TE Id: 20.20.20.20 Router Node (isis 1 level-2)
Link[0]: Intf Address:7.2.2.2, Nbr Intf Address:7.2.2.1
Link[1]: Intf Address:7.1.1.2, Nbr Intf Address:7.1.1.1
Link[2]: Intf Address:7.3.3.1, Nbr Intf Address:7.3.3.2
IGP Id: 0000.0000.0003.00, MPLS-TE Id: 30.30.30.30 Router Node (isis 1 level-2)
Link[0]: Intf Address:7.3.3.2, Nbr Intf Address:7.3.3.1
Table 45 describes the significant fields shown in the display.
Table 45 show mpls traffic-eng topology Field Descriptions
|
|
My_System_id |
IGP1 system or IGP router ID. |
Signalling error holddown |
Link hold-down timer configured to handle path error events to exclude link from topology. |
IGP Id |
Identification of the advertising router. |
Link |
MPLS-TE link. |
Frag Id |
GP LSA2 fragment identifier. |
Nbr Intf Address |
Neighbor Interface address of this link. |
TE Metric |
TE cost of link. |
SRLGs |
SRLG3 values that are flooded by IGPs to TE. |
Switching Capability |
Switching capability: packet, optical, lambda. |
Physical BW |
Physical line rate. |
BC Model ID |
Bandwidth Constraints Model ID, RDM or MAM. |
Max Reservable BW |
Maximum bandwidth (in kilobits per second) that you can reserve on a link. |
Max Reservable BW Global |
Maximum bandwidth (in kilobits per second) that you can reserve on a link in global-pool (prestandard and RDM). |
Max Reservable BW Sub |
Maximum bandwidth (in kilobits per second) that you can reserve on a link in sub-pool (prestandard and RDM). |
BC0 |
Maximum bandwidth (in kilobits per second) that you can reserve on a link in BC0. |
BC1 |
Maximum bandwidth (in kilobits per second) that you can reserve on a link in BC1. |
TE-class[index] |
Available bandwidth in TE-class (map of class-type and priority) at given index. |
Total Allocated BW |
Bandwidth (in Kbps) allocated at that priority. |
Global Pool Reservable BW |
Available bandwidth (in kbps) reservable at that priority in global pool (prestandard RDM). |
Sub Pool Reservable BW |
Available bandwidth (in kbps) reservable at that priority in sub-pool (prestandard RDM). |
Related Commands
show mpls traffic-eng tunnels
To display information about MPLS-TE tunnels, use the show mpls traffic-eng tunnels command in EXEC mode.
show mpls traffic-eng tunnels [tunnel-number] [all] [auto-bw] [backup [name tunnel-name | promotion-timer | protected-interface | topology | tunnel-number]] [brief] [destination destination-address] [down] [gmpls] [interface [in | out | inout] interface-id] [name tunnel-name | tunnel-number] [p2p][property [backup-tunnel | fast-reroute]] [protection] [role [all | heads | tails]] [source source-address] [suboptimal constraints [current | max | none]] [summary | up [igp ospf | isis] | [within-last interval] | [reoptimized within-last interval] | [class-type ct]] [detail] [tabular]
Syntax Description
tunnel-number |
(Optional) Tunnel number. Range is from 0 to 65535. |
all |
(Optional) Displays all MPLS-TE tunnels. |
auto-bw |
(Optional) Restricts the display to tunnels when the automatic bandwidth is enabled. |
backup |
(Optional) Displays FRR1 backup tunnels information. The information includes the physical interface protected by the tunnel, the number of TE LSPs2 protected, and the bandwidth protected. |
name tunnel-name |
(Optional) Displays the tunnel with given name. |
promotion-timer promotion-timer |
(Optional) Displays the configured fast-reroute (FRR) backup tunnel promotion timer value in seconds. |
protected-interface |
(Optional) Displays FRR protected interfaces. |
topology |
(Optional) Displays FRR topology. |
tunnel-number |
(Optional) Restricts the display to the specified tunnel number. |
brief |
(Optional) Displays the brief form of the command. |
destination destination-address |
(Optional) Restricts the display to tunnels destined to the specified IP address. |
down |
(Optional) Displays tunnels that are down. |
gmpls |
(Optional) Restricts the display to GMPLS tunnels. |
interface in interface-path-id |
(Optional) Displays tunnels that use the specified input interface. |
interface out interface-path-id |
(Optional) Displays tunnels that use the specified output interface. |
interface inout interface-path-id |
(Optional) Displays tunnels that use the specified interface as an input or output interface. |
name tunnel-name | tunnel number |
(Optional) Displays tunnels of the specified name or tunnel number. |
p2p |
(Optional) Restricts the display to P2P tunnels. |
property backup-tunnel |
(Optional) Displays tunnels with property of backup tunnel. Selects MPLS-TE tunnels used to protect physical interfaces on this router. A tunnel configured to protect a link against failure is a backup tunnel and has the backup tunnel property. |
property fast-reroute |
(Optional) Displays tunnels with property of fast-reroute configured. Selects FRR-protected MPLS-TE tunnels originating on (head), transmitting (router), or terminating (tail) on this router. |
protection |
(Optional) Displays all protected tunnels (configured as fast-reroutable). Displays information about the protection provided to each tunnel selected by other options specified with this command. The information includes whether protection is configured for the tunnel, the protection (if any) provided to the tunnel by this router, and the tunnel bandwidth protected. |
role [all | heads | tails] |
(Optional) •Displays all tunnels. •Displays tunnels with their heads at this router. •Displays tunnels with their tails at this router. |
source source-address |
(Optional) Restricts the display to tunnels with a matching source IP address. |
suboptimal constraints [current | max | none] |
(Optional) Displays tunnels whose path metric is •Greater than the current shortest path constrained by the tunnel's configured options (current) •Greater than the current shortest path, constrained by the configured options for the tunnel, and considering only the network capacity (max) •Greater than the shortest unconstrained path (none) Selected tunnels would have a shorter path if they were reoptimized immediately. |
summary |
(Optional) Displays summary of configured tunnels. |
up [[igp ospf | isis] | within-last interval] | [class-type ct] |
(Optional) •Displays tunnels if the tunnel interface is up. •Display tunnels with path calculated using given IGP type (ospf or isis). •Displays tunnels that came up within-last given time interval. •Displays tunnels using given class-type value config |
reoptimized within-last interval |
(Optional) Displays tunnels reoptimized within-last given time interval. |
detail |
(Optional) Displays detail information about headend tunnels. |
tabular |
(Optional) Displays a table showing TE LSPs, with one entry per line. |
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
Added tabular keyword. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
The command output was updated to support unequal load-balancing parameters. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
If specified, sample output was modified to display the area on its own line after the existing path-option information. |
Release 3.8.0 |
The following items were added: •To support the Automatic Bandwidth feature: –The auto-bw keyword was added. –Sample output and automatic bandwidth fields were added. •The tunnel-number argument, gmpls keyword, and p2p keyword were added. |
Release 3.8.4 |
Sample output was modified to add the Underflow Threshold field for the auto-bw keyword. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the brief form of the show mpls traffic-eng tunnels command to display information specific to a tunnel interface. Use the command form without the brief keyword to display information including the destination address, source ID, role, name, suboptimal constraints, and interface.
Examples
The following sample output is not changed when no area is specified for the active path-option. If the area is specified, it is added on a line of its own after the existing path-option information.
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels 30002
LSP Tunnels Process: running
Periodic reoptimization: every 3600 seconds, next in 650
Periodic FRR Promotion: every 300 seconds, next in 41
Auto-bw enabled tunnels: 7
Name: tunnel-te30002 Destination: 13.254.10.3
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit R1-R4-loose-R3-via-E5 (Basis for
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 0 kbps CT0
Bandwidth: 0 kbps (CT0) Priority: 2 2 Affinity: 0x4/0x4
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Policy class: not set
Loadshare: 0 equal loadshares
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Fast Reroute: Disabled, Protection Desired: None
Tunnel has been up for: 1d08h
Path info (ISIS AUTOBW level-2):
Displayed 0 (of 18) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 0 up, 0 down, 0 recovering, 0 recovered heads
The following is sample output from the show mpls traffic-eng tunnels command using the property keyword:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels property backup interface out pos
0/6/0/0
LSP Tunnels Process: running, not registered with RSVP
RSVP Process: not running
Periodic reoptimization: every 3600 seconds, next in 3595 seconds
Periodic FRR Promotion: every 300 seconds, next in 295 seconds
Periodic auto-bw collection: disabled
Name: tunnel-te1 Destination: 1.1.1.1
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type dynamic (Basis for Setup, path weight 1)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth: 1000 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
Loadshare: 10000 bandwidth-based
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 0
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Backup FRR EXP Demotion: 1 ' 7, 2 ' 1
Class-Attributes: 1, 2, 7
Tunnel has been up for: 00:00:08
Path info (ospf 0 area 0):
Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 0 up, 1 down, 0 recovering, 0 recovered heads
Table 46 describes the significant fields shown in the display.
Table 46 show mpls traffic-eng tunnels Field Descriptions
|
|
LSP Tunnels Process |
Status of the LSP1 tunnels process. |
RSVP Process |
Status of the RSVP process. |
Forwarding |
Status of forwarding (enabled or disabled). |
Periodic reoptimization |
Time until the next periodic reoptimization (in seconds). |
Periodic FRR Promotion |
Time until the next periodic FRR2 promotion (in seconds). |
Periodic auto-bw collection |
Time until the next periodic auto-bw collection (in seconds). |
Name |
Interface configured at the tunnel head. |
Destination |
Tail-end router identifier. |
Admin/STATUS |
Configured up or down. |
Oper/STATE |
Operationally up or down. |
Signalling |
Signaling connected or down or proceeding. |
Config Parameters |
Configuration parameters provided by tunnel mode MPLS traffic-eng, including those specific to unequal load-balancing functionality (bandwidth, load-share, backup FRR EXP demotion, class-attributes, and bandwidth-policer. |
History: Current LSP: Uptime |
Time LSP has been up. |
Path Info |
Hop list of current LSP. |
The following is sample output from the show mpls traffic-eng tunnels command using the protection keyword. This command selects every MPLS-TE tunnel known to the router that was signaled as an FRR-protected LSP (property fast-reroute) and displays information about the protection this router provides to each selected tunnel.
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels protection
LSP Head, Admin: up, Oper: up
Src: 10.20.20.20, Dest: 10.10.10.10, Instance: 28
Fast Reroute Protection: None
LSP Head, Admin: up, Oper: up
Src: 10.20.20.20, Dest: 10.10.10.10, Instance: 945
Fast Reroute Protection: Requested
Backup tunnel160 to LSP nhop
tunnel160: out i/f: POS0/6/0/0
Original: out i/f: POS0/7/0/0, label: 3, nhop: 10.10.10.10
With FRR: out i/f: tunnel160, label: 3
LSP bw: 10 kbps, Backup level: any unlimited, type: CT0
Table 47 describes the significant fields shown in the display.
Table 47 show mpls traffic-eng tunnels protection Field Descriptions
|
|
Tunnel# |
Number of the MPLS-TE backup tunnel. |
LSP Head/router |
If this node is head or router for this LSP1 . |
Instance |
LSP ID. |
Backup tunnel |
If this backup tunnel providing protection is NHOP/NNHOP. |
out if |
Backup tunnel's outgoing interface |
Original |
Outgoing interface, label and next-hop of the LSP when not using backup. |
With FRR |
Outgoing interface and label when using backup tunnel. |
LSP BW |
Signaled bandwidth of the LSP. |
Backup level |
Type of bandwidth protection provided—pool type and limited/unlimited bandwidth. |
The following is sample output from the show mpls traffic-eng tunnels command using the backup keyword. This command selects every MPLS-TE tunnel known to the router and displays information about the FRR protection each selected tunnel provides for interfaces on this route. The command does not generate output for tunnels that do not provide FRR protection of interfaces on this router:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels backup
Src: 10.20.20.20, Dest: 10.10.10.10, Instance: 28
Fast Reroute Backup Provided:
Protected i/fs: POS0/7/0/0
Backup BW: any-class unlimited, Inuse: 0 kbps
Table 48 describes the significant fields shown in the display.
Table 48 show mpls traffic-eng tunnels backup Field Descriptions
|
|
Tunnel# |
Number of the MPLS-TE backup tunnel. |
Dest |
IP address of the destination of the backup tunnel. |
State |
State of the backup tunnel. Values are up, down, or admin-down. |
Instance |
LSP ID of the tunnel. |
Protected i/fs: |
List of interfaces protected by this backup. |
Protected lsps: |
Number of LSPs currently protected by this backup |
Backup BW |
Configured backup bandwidth type and amount. Pool from which bandwidth is acquired. Values are any-class, CT0, and CT1. Amount is either unlimited or a configured limit in kbps. |
Inuse |
Backup bandwidth currently inuse on this backup. |
The following is sample output from the show mpls traffic-eng tunnels command using the backup and protected-interface keywords:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels backup protected-interface
Tunnel100 UNUSED : out i/f: Admin: down Oper: down
Tunnel160 NHOP : out i/f: POS0/6/0/0 Admin: up Oper: up
Table 49 describes the significant fields shown in the display.
Table 49 show mpls traffic-eng tunnels backup protected-interface Field Descriptions
|
|
Interface |
MPLS-TE-enabled FRR protected interface. |
Tunnel# |
FRR protected tunnel on the interface. |
NHOP/NNHOP/UNUSED |
State of Protected tunnel: unused, next hop, next-next hop. |
out i/f |
Outgoing interface of the backup tunnel providing the protection. |
The following is sample output from the show mpls traffic-eng tunnels up command using the igp ospf keywords:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels up igp ospf
LSP Tunnels Process: running
Periodic reoptimization: every 3600 seconds, next in 3381 seconds
Periodic FRR Promotion: every 300 seconds, next in 81 seconds
Periodic auto-bw collection: disabled
Name: tunnel-te11 Destination: 30.30.30.30
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit back (Basis for Setup, path weight 1)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Number of configured name based affinities: 2
Name based affinity constraints in use:
Include bit map : 0x4 (refers to undefined affinity name)
Include-strict bit map: 0x4
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 0
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Tunnel has been up for: 00:00:21
Removal Trigger: tunnel shutdown
Displayed 1 (of 3) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
The following is sample output from the show mpls traffic-eng tunnels command using the up within-last keywords:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels up within-last 200
LSP Tunnels Process: running
Periodic reoptimization: every 3600 seconds, next in 3381 seconds
Periodic FRR Promotion: every 300 seconds, next in 81 seconds
Periodic auto-bw collection: disabled
Name: tunnel-te11 Destination: 30.30.30.30
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit back (Basis for Setup, path weight 1)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Number of configured name based affinities: 2
Name based affinity constraints in use:
Include bit map : 0x4 (refers to undefined affinity name)
Include-strict bit map: 0x4
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 0
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Tunnel has been up for: 00:00:21
Removal Trigger: tunnel shutdown
Displayed 1 (of 3) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
The following is sample output from the show mpls traffic-eng tunnels command using the reoptimized within-last keywords:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels reoptimized within-last 600
LSP Tunnels Process: running
Periodic reoptimization: every 60000 seconds, next in 41137 seconds
Periodic FRR Promotion: every 300 seconds, next in 37 seconds
Periodic auto-bw collection: disabled
Name: tunnel-te1 Destination: 30.30.30.30
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit prot1 (Basis for Setup, path weight 1)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth: 66 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: IGP (global)
AutoRoute: enabled LockDown: disabled Loadshare: 66 bw-based
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 66
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Tunnel has been up for: 00:14:04
Selection: reoptimization
Removal Trigger: reoptimization completed
Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
The following is sample output from the show mpls traffic-eng tunnels command using the detail keyword:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels 1 detail
Name: tunnel-te1 Destination: 24.24.24.24
Working Path: valid Signalling: connected
Protecting Path: valid Protect Signalling: connected
Working LSP is carrying traffic
path option 1, type explicit po4 (Basis for Setup, path weight 1)
G-PID: 0x001d (derived from egress interface properties)
Path protect LSP is present.
path option 1, type explicit po6 (Basis for Setup, path weight 1)
Bandwidth: 10 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (default)
AutoRoute: enabled LockDown: disabled Loadshare: 10 bw-based
Auto-bw: disabled(0/0) 0 Bandwidth Requested: 10
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Tunnel has been up for: 00:04:06
Removal Trigger: path verification failed
Instance: 71, Signaling Area: ospf optical area 0
Incoming Label: explicit-null
Outgoing Interface: POS0/4/0/0, Outgoing Label: implicit-null
Tspec: avg rate=2488320 kbits, burst=1000 bytes, peak rate=2488320 kbits
IPv4 100.0.0.3, flags 0x0
Fspec: avg rate=2488320 kbits, burst=1000 bytes, peak rate=2488320 kbits
Instance: 72, Signaling Area: ospf optical area 0
Incoming Label: explicit-null
Outgoing Interface: POS0/6/0/0, Outgoing Label: implicit-null
Tspec: avg rate=2488320 kbits, burst=1000 bytes, peak rate=2488320 kbits
IPv4 101.0.0.3, flags 0x0
Fspec: avg rate=2488320 kbits, burst=1000 bytes, peak rate=2488320 kbits
The following is sample output from the show mpls traffic-eng tunnels command using the role mid keyword:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels role mid
LSP Tunnels Process: running
Periodic reoptimization: every 3600 seconds, next in 1166 seconds
Periodic FRR Promotion: every 300 seconds, next in 90 seconds
Periodic auto-bw collection: disabled
LSP Tunnel 10.10.10.10 1 [5508] is signalled, connection is up
Tunnel Name: FRR1_t1 Tunnel Role: Mid
OutLabel: POS0/3/0/0, implicit-null
Src 10.10.10.10 Dst 30.30.30.30, Tunnel ID 1, Tunnel Instance 5508
Incoming Address: 7.3.3.1
ospf 100 area 0, Metric 1 (TE), Affinity 0x0, Mask 0xffff, Queries 0
Tspec: avg rate=10 kbits, burst=1000 bytes, peak rate=10 kbits
IPv4 30.30.30.30, flags 0x20
Fspec: avg rate=10 kbits, burst=1000 bytes, peak rate=10 kbits
Displayed 0 (of 1) heads, 1 (of 1) midpoints, 0 (of 1) tails
Displayed 0 up, 0 down, 0 recovering, 0 recovered heads
Table 50 describes the significant fields shown in the display.
Table 50 show mpls traffic-eng tunnels tabular Field Descriptions
|
|
Tunnel Name |
MPLS-TE tunnel name. |
LSP ID |
LSP ID of the tunnel. |
Destination Address |
Destination address of the TE tunnel (identified in Tunnel Name). |
Tunnel State |
State of the tunnel. Values are up, down, or admin-down. |
FRR State |
FRR state identifier. |
LSP Role |
Role identifier. Values are All, Head, or Tail. |
The following sample output shows the MPLS-TE tunnel information only for tunnels in which the automatic bandwidth is enabled using the auto-bw keyword:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels auto-bw
LSP Tunnels Process: running
Periodic reoptimization: every 3600 seconds, next in 160 seconds
Periodic FRR Promotion: every 300 seconds, next in 95 seconds
Auto-bw enabled tunnels: 1
Name: tunnel-te6 Destination: 0.0.0.0
Admin: up Oper: down Path: not valid Signalling: Down
G-PID: 0x0800 (internally specified)
Bandwidth Requested: 0 kbps CT0
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Policy class: not set
Loadshare: 0 equal loadshares
Currently no BW application allowed because: Tunnel is down
Bandwidth Min/Max: 10000-500000 kbps
Application Frequency: 180 min Jitter: 0s Time Left: 2h 59m 0s
Collection Frequency: 5 min
Samples Collected: 0 Next: 3m 55s
Highest BW: 0 kbps Underflow BW: 0 kbps
Adjustment Threshold: 20% 1000 kbps
Overflow Threshold: 50% 1000 kbps Limit: 0/3 Overflow BW Applicatio0
Underflow Threshold: 90% 100 kbps Limit: 0/3 Underflow BW Applicati0
Direction: unidirectional
Endpoint switching capability: unknown, encoding type: unassigned
Transit switching capability: unknown, encoding type: unassigned
Fast Reroute: Disabled, Protection Desired: None
Reason for the tunnel being down: No destination is configured
Displayed 1 (of 1) heads, 0 (of 4) midpoints, 0 (of 0) tails
Displayed 0 up, 1 down, 0 recovering, 0 recovered heads
Table 50 describes the significant fields shown in the display.
Table 51 show mpls traffic-eng tunnels auto-bw Field Descriptions
|
|
collect bw only |
Field displays only if the bandwidth collection is configured in the tunnel automatic bandwidth configuration. |
Last BW Applied |
Last bandwidth change that is requested by the automatic bandwidth for the tunnel. In addition, this field indicates which pool was used for the bandwidth. |
BW Applications |
Total number of bandwidth applications that is requested by the automatic bandwidth that includes the applications triggered by an overflow condition. |
Last Application Trigger |
Following last application options are displayed: •Periodic Application •Overflow Detected •Manual Application |
Bandwidth Min/Max |
Bandwidth configured is either minimum or maximum. |
Application Frequency |
Application frequency configured. The Time Left field indicates the time left before the next application. |
Collection Frequency |
Globally configured collection frequency that is the same value for all the tunnels. Range is 1 to 10 collection intervals, default is 0. |
Samples Collected |
Number of samples that are collected during the current application period. This field is replaced by the Collection Disabled field if no collection frequency is currently configured. |
Highest BW |
Highest bandwidth that is collected for the application period. |
Next |
Time left before the next collection event. |
Overflow Threshold |
Overflow threshold that is configured. The Overflow field appears only if the overflow detection is configured in the tunnel automatic bandwidth configuration. |
Underflow Threshold |
Underflow threshold that is configured. Configures measurement of decrease in tunnel bandwidth. Percentage keyword sets the percentage of bandwidth change (decrease) that triggers tunnel underflow detection. |
Limit |
Consecutive overflow detected or configured limit. |
Early BW Applications |
Number of early bandwidth applications that are triggered by an overflow condition. |
Related Commands
|
|
backup-bw |
Specifies the bandwidth type LSPs can use for a backup tunnel, whether the backup tunnel should provide bandwidth protection, and if so, how much and in which bandwidth pool. |
show mpls traffic-eng tunnels auto-bw brief |
Displays the list of automatic bandwidth enabled tunnels, and indicates if the current signaled bandwidth of the tunnel is identical to the bandwidth that is applied by the automatic bandwidth |
show mpls traffic-eng tunnels auto-bw brief
To display the list of automatic bandwidth enabled tunnels, and to indicate if the current signaled bandwidth of the tunnel is identical to the bandwidth that is applied by the automatic bandwidth, use the show mpls traffic-eng tunnels auto-bw brief command in EXEC mode.
show mpls traffic-eng tunnels auto-bw brief
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the show mpls traffic-eng tunnels auto-bw brief command to determine if the automatic bandwidth application has been applied on a specified tunnel. If a single tunnel is specified, only the information for that tunnel is displayed.
Examples
The following sample output shows the list of automatic bandwidth enabled tunnels:
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels auto-bw brief
Tunnel LSP Last appl Requested Signalled Highest Application
Name ID BW(kbps) BW(kbps) BW(kbps) BW(kbps) Time Left
-------------- ------ ---------- ---------- ---------- ---------- --------------
tunnel-te0 1 10 10 50 2h 5m
tunnel-te1 5 500 300 420 1h 10m
Table 52 describes the significant fields shown in the display.
Table 52 show mpls traffic-eng tunnels auto-bw brief Field Descriptions
|
|
Tunnel Name |
Name for the tunnel. |
LSP ID |
ID of the Label Switched Path that is used by the tunnel. |
Last appl BW (kbps) |
Last bandwidth applied (for example, requested) by the automatic-bandwidth feature for the tunnel. |
Requested BW (kbps) |
Bandwidth that is requested for the tunnel. |
Signalled BW (kbps) |
Bandwidth that is actually signalled for the tunnel. |
Highest BW (kbps) |
Highest bandwidth measured since the last start of the application interval. |
Application Time Left |
Time left until the application period ends for this tunnel. |
Related Commands
signalled-bandwidth
To configure the bandwidth required for an MPLS-TE tunnel, use the signalled-bandwidth command in interface configuration mode. To return to the default behavior, use the no form of this command.
signalled-bandwidth {bandwidth [class-type ct] | sub-pool bandwidth}
no signalled-bandwidth {bandwidth [class-type ct] | sub-pool bandwidth}
Syntax Description
bandwidth |
Bandwidth required for an MPLS-TE tunnel. Bandwidth is specified in kilobits per second. By default, bandwidth is reserved in the global pool. Range is 0 to 4294967295. |
class-type ct |
(Optional) Configures the class type of the tunnel bandwidth request. Range is 0 to 1. Class-type 0 is strictly equivalent to global-pool. Class-type 1 is strictly equivalent to sub-pool. |
sub-pool bandwidth |
Reserves the bandwidth in the sub-pool instead of the global pool. Range is 1 to 4294967295. A sub-pool bandwidth value of 0 is not allowed. |
Defaults
The default is 0 in class-type 0.
Command Modes
Interface configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was introduced on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The signalled-bandwidth command supports two bandwidth pools (class-types) for Diff-Serv Aware TE (DS-TE) feature. This command is also used as the bandwidth startup value to bring up the auto bandwidth enabled tunnels.
Note The Cisco DiffServe Aware TE feature is compliant to IETF standard and will interoperate with third party vendor DS-TE. Both Russian Doll Model and Maximum Allocation Model for bandwidth allocation are supported. We recommended that IETF terminology be used in DS-TE bandwidth configurations, namely, Class-type (CT) and Bandwidth Constraints (BC).
Examples
The following example shows how to set the bandwidth required for an MPLS-TE tunnel to 1000 in the global pool (class-type 0):
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# signalled-bandwidth 1000
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# signalled-bandwidth 1000 class-type 0
The following example shows how to set the bandwidth required for an MPLS-TE tunnel to 1000 in the sub-pool (class-type 1):
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# signalled-bandwidth sub-pool 1000
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# signalled-bandwidth 1000 class-type 1
Related Commands
signalled-name
To configure the name of the tunnel required for an MPLS-TE tunnel, use the signalled-name command in interface configuration mode. To return to the default behavior, use the no form of this command.
signalled-name name
no signalled-bandwidth name
Syntax Description
name |
Name used to signal the tunnel. |
Defaults
Default name is the hostname_tID, where ID is the tunnel interface number.
Command Modes
Interface configuration
Command History
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to set the tunnel name:
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# signalled-name tunnel-from-NY-to-NJ
Related Commands
signalling advertise explicit-null (MPLS-TE)
To specify that tunnels terminating on a router use explicit-null labels, use the signalling advertise explicit-null command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
signalling advertise explicit-null
no signalling advertise explicit-null
Syntax Description
This command has no arguments or keywords.
Defaults
Implicit-null labels are advertised.
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the signalling advertise explicit-null command to specify that tunnels terminating on this router use explicit-null labels. This command applies to tunnel labels advertised to next to last (penultimate) hop.
The explicit label is used to carry quality-of-service (QoS) information up to the terminating-end router of the label switched path (LSP).
Examples
The following example shows how to configure explicit null tunnel labels:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# signalling advertise explicit-null
Related Commands
snmp traps mpls traffic-eng
To enable the router to send MPLS-TE Simple Network Management Protocol (SNMP) notifications or informs, use the snmp traps mpls traffic-eng command in global configuration mode. To return to the default behavior, use the no form of this command.
snmp traps mpls traffic-eng [notification-option]
no snmp traps mpls traffic-eng [notification-option]
Syntax Description
notification-option |
(Optional) Notification option to enable the sending of notifications to indicate changes in the status of MPLS-TE tunnels. Use one of the following values: •up •down •reoptimize •reroute |
Defaults
No default behavior or values
Command Modes
Global configuration
Command Modes
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If the command is entered without the notification-option argument, all MPLS-TE notification types are enabled.
SNMP notifications can be sent as either traps or inform requests.
The snmp-server enable traps mpls traffic-eng command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host command and specify the keyword trap or informs.
If you do not enter the snmp traps mpls traffic-eng command, no MPLS-TE notifications controlled by this command are sent. To configure the router to send these MPLS-TE SNMP notifications, you must enter at least one snmp enable traps mpls traffic-eng command. If you enter the command with no keywords, all MPLS-TE notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of MPLS-TE notifications, you must issue a separate snmp traps mpls traffic-eng command for each notification type and notification option.
The snmp traps mpls traffic-eng command is used in conjunction with the snmp host command. Use the snmp host command to specify which host or hosts receive MPLS-TE SNMP notifications. To send notifications, you must configure at least one snmp host command.
For a host to receive an MPLS-TE notification controlled by this command, both the snmp traps mpls traffic-eng command and the snmp host command for that host must be enabled.
Examples
The following example shows how to configure a router to send MPLS-TE tunnel up SNMP notifications when a configured MPLS-TE tunnel leaves the down state and enters the up state:
RP/0/RP0/CPU0:router(config)# snmp traps mpls traffic-eng up
Related Commands
|
|
snmp-server host |
Specifies the recipient of a Simple Network Management Protocol (SNMP) notification operation. |
srlg (MPLS-TE)
To configure an MPLS traffic engineering shared-risk link group (SRLG) membership for a link on a given interface, use the srlg command in MPLS-TE interface configuration mode. To disable this configuration, use the no form of this command.
srlg membership-number
no srlg membership-number
Syntax Description
membership-number |
Membership number that identifies this SRLG. Range is 0 to 4294967295. |
Defaults
Shared Risk Link Group memberships are not configured.
Command Modes
MPLS-TE interface configuration
Command History
|
|
Release 3.8.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure an SRLG with 10 member links:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/3/0/2
RP/RP0/RP0/CPU0:router(config-mpls-te-if)# srlg 10
Related Commands
switching (GMPLS)
To configure TE-link switching attributes, use the switching command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.
switching {key value | link} [capability switching | encoding encoding type]
no switching {key value | link} [capability switching | encoding encoding type]
Syntax Description
key |
Configures the Interface Switching Capability Key. |
key value |
Local interface switching capability key value. Range is 1 to 99. |
link |
Enables link switching. |
capability switching |
(Optional) Configures switching capability type. |
encoding encoding type |
(Optional) Enables local encoding. Range is 1 to 99. |
Defaults
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command Modes
|
|
Release 3.3 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to configure interface switching key on Packet-over-SONET/SDH (POS) interface 0/7/0/1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/1
RP/0/RP0/CPU0:router(config-mpls-te-if)# switching key 66
Related Commands
switching endpoint (GMPLS)
To specify the switching capability and encoding types for all endpoint TE links used to signal the optical tunnel that is mandatory to set up the GMPLS LSP, use the switching endpoint command in interface tunnel-gte configuration mode. To disable this feature, use the no form of this command.
switching endpoint capability switching type encoding encoding type
no switching endpoint capability switching type encoding encoding type
Syntax Description
capability switching type |
Capability switching type is the optical LSP switching capability descriptor. The following types are used: •psc1—Specifies Packet-Switch Capable-1 that is equivalent to numeric 1. •lsc—Specifies Lambda-Switch Capable that is equivalent to numeric 150. •fsc—Specifies Fiber-Switch Capable that is equivalent to numeric 200. |
encoding encoding type |
Specifies the transport capability of the TE link over which the GMPLS LSP is established. For SONET links, the encoding is specified as sonetsdh. For Ethernet links, the encoding is specified as ethernet. |
Defaults
No default behavior or values
Command Modes
Interface tunnel-gte configuration
Command History
|
|
Release 3.3.2 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
GMPLS interfaces are used under the tunnel-gte interface type. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
GMPLS interfaces are used under the tunnel-gte interface type.
Use the switching endpoint command to configure the optical LSP. The switching and encoding types must match with the configured values at the termination point of the LSP.
Examples
The following example shows how to configure switching capability as psc1 and the encoding type as sonetsdh for the switching endpoint command:
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 99.99.99.2 255.255.255.254
RP/0/RP0/CPU0:router(config-if)# signalled-name tunnel-gte 1
RP/0/RP0/CPU0:router(config-if)# switching endpoint psc1 encoding sonetsdh
RP/0/RP0/CPU0:router(config-if)# priority 22
RP/0/RP0/CPU0:router(config-if)# signalled-bandwidth 2488320
RP/0/RP0/CPU0:router(config-if)# destination 109.109.109.109
RP/0/RP0/CPU0:router(config-if)# direction bidirectional
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name g1-p1-p2
RP/0/RP0/CPU0:router(config-if)# path-option protecting 1 explicit name g2-p1-p2
Related Commands
switching transit (GMPLS)
To specify the switching capability and encoding types for all transit TE links used to signal the optical tunnel to configure an optical LSP, use the switching transit command in interface tunnel-gte configuration mode. To disable this feature, use the no form of this command.
switching transit capability switching type encoding encoding type
no switching transit capability switching type encoding encoding type
Syntax Description
capability switching type |
Capability switching type is the optical LSP switching capability descriptor. The following types are used: •psc1—Specifies Packet-Switch Capable-1 that is equivalent to numeric 1. •lsc—Specifies Lambda-Switch Capable that is equivalent to numeric 150. •fsc—Specifies Fiber-Switch Capable that is equivalent to numeric 200. |
encoding encoding type |
Specifies the transport capability of the TE link over which the GMPLS LSP is established. For SONET links, the encoding is specified as sonetsdh. For Ethernet links, the encoding is specified as ethernet. |
Defaults
No default behavior or values
Command Modes
Interface tunnel-gte configuration
Command History
|
|
Release 3.3.2 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
GMPLS interfaces are used under the tunnel-gte interface type. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
GMPLS interfaces are used under the tunnel-gte interface type.
Use the switching transit command to configure the optical LSP. The switching and encoding types must match with the configured values at the termination point of the LSP.
Examples
The following example shows how to configure switching capability as lsc and the encoding type as sonetsdh for the switching transit command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 99.99.99.2 255.255.255.254
RP/0/RP0/CPU0:router(config-if)# signalled-name tunnel-gte1
RP/0/RP0/CPU0:router(config-if)# switching transit lsc encoding sonetsdh
RP/0/RP0/CPU0:router(config-if)# priority 22
RP/0/RP0/CPU0:router(config-if)# signalled-bandwidth 2488320
RP/0/RP0/CPU0:router(config-if)# destination 109.109.109.109
RP/0/RP0/CPU0:router(config-if)# direction bidirectional
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name g1-p1-p2
RP/0/RP0/CPU0:router(config-if)# path-option protecting 1 explicit name g2-p1-p2
Related Commands
timers loose-path (MPLS-TE)
To configure the period between the headend retries after path errors, use the timers loose-path command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
timers loose-path retry-period value
no timers loose-path retry-period value
Syntax Description
retry-period value |
Configures the time between retries upon a path error. Range is 30 to 600 seconds. |
Defaults
value: 120
Command Modes
MPLS-TE configuration
Command History
|
|
Release 3.4.0 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to the period between retries after path errors to 300 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# timers loose-path retry-period 300
Related Commands
topology holddown sigerr (MPLS-TE)
To specify the time that a router should ignore a link in its TE topology database in tunnel path constrained shortest path first (CSPF) computations following a TE tunnel signaling error on the link, use the topology holddown sigerr command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
topology holddown sigerr seconds
no topology holddown sigerr seconds
Syntax Description
seconds |
Time, in seconds, that the router ignores a link during tunnel path calculations, following a TE tunnel error on the link. Range is 0 to 300. Default is 10. |
Defaults
seconds: 10
Command Modes
MPLS-TE configuration
Command History
|
|
Release 2.0 |
This command was introduced on the Cisco CRS-1. |
Release 3.0 |
No modification. |
Release 3.2 |
This command was supported on the Cisco XR 12000 Series Router. |
Release 3.3 |
No modification. |
Release 3.4.0 |
No modification. |
Release 3.5.0 |
No modification. |
Release 3.6.0 |
No modification. |
Release 3.7.0 |
No modification. |
Release 3.8.0 |
No modification. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
A router at the headend for TE tunnels can receive a Resource Reservation Protocol (RSVP) No Route error message before the router receives a topology update from the IGP routing protocol announcing that the link is down. When this happens, the headend router ignores the link in subsequent tunnel path calculations to avoid generating paths that include the link and are likely to fail when signaled. The link is ignored until the router receives a topology update from its IGP or a link holddown timeout occurs. Use the topology holddown sigerr command to change the link holddown time from its 10-second default value.
Examples
The following example shows how to set the link holddown time for signaling errors at 15 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# topology holddown sigerr 15
Related Commands
underflow threshold (MPLS-TE)
To configure the tunnel underflow detection, use the underflow threshold command in MPLS-TE automatic bandwidth interface configuration mode. To disable the underflow detection feature, use the no form of this command.
underflow threshold percentage [min bandwidth] limit limit
no underflow threshold
Syntax Description
percentage |
Bandwidth change percent to trigger an underflow. Range is from 1 to 100 percent. |
limit limit |
Configures the number of consecutive collection intervals that exceeds the threshold. The bandwidth underflow triggers an early tunnel bandwidth update. Range is from 1 to 10 collection periods. The default value is none. |
min bandwidth |
(Optional) Configures the bandwidth change value in kbps to trigger an underflow. Range is from 10 to 4294967295. If not specified, the default value is 10. |
Defaults
The default value is disabled.
Command Modes
MPLS-TE automatic bandwidth interface configuration
Command History
|
|
Release 3.8.4 |
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router. |
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you modify the limit keyword, the consecutive underflows counter for the tunnel is also reset.
If you enable or modify the minimum value, the current consecutive underflows counter for the tunnel is also reset, which effectively restarts the underflow detection from scratch.
If a number of consecutive bandwidth samples are greater than the underflow threshold (bandwidth percentage) and the minimum bandwidth configured, then a bandwidth application is updated immediately; instead of waiting for the end of the application period.
Examples
The following example shows how to configure the tunnel underflow detection for tunnel-te 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# underflow threshold 90 min 100 limit 3
Related Commands