-
Cisco IOS XR Multiprotocol Label Switching Command Reference, Release 3.5
-
Preface
-
MPLS Label Distribution Protocol Commands on Cisco IOS XR Software
-
RSVP Infrastructure Commands on Cisco IOS XR Software
-
MPLS Forwarding Commands on Cisco IOS XR Software
-
MPLS Traffic Engineering Commands on Cisco IOS XR Software
-
MPLS OAM Commands on Cisco IOS XR Software
-
MPLS Optical User Network Interface Commands on Cisco IOS XR Software
-
MPLS Virtual Private Network Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
MPLS Traffic Engineering Commands on Cisco IOS XR Software
clear mpls traffic-eng counters tunnels
clear mpls traffic-eng fast-reroute log
clear mpls traffic-eng link-management statistics
mpls traffic-eng ds-te bc-model
mpls traffic-eng ds-te te-classes
mpls traffic-eng fast-reroute promote
mpls traffic-eng fast-reroute timers promotion
mpls traffic-eng link-management flood
mpls traffic-eng link-management timers bandwidth-hold
mpls traffic-eng link-management timers periodic-flooding
mpls traffic-eng lmp router-id
mpls traffic-eng maximum tunnels
mpls traffic-eng path-protection switchover (GMPLS)
mpls traffic-eng path-selection loose-expansion affinity
mpls traffic-eng path-selection loose-expansion metric
mpls traffic-eng path-selection metric
mpls traffic-eng reoptimize (Config)
mpls traffic-eng reoptimize (EXEC)
mpls traffic-eng reoptimize timers delay
mpls traffic-eng router-id secondary
mpls traffic-eng signalling advertise explicit-null
mpls traffic-eng timers loose-path
mpls traffic-eng topology holddown sigerr
show mpls traffic-eng affinity-map
show mpls traffic-eng autoroute
show mpls traffic-eng counters tunnel
show mpls traffic-eng ds-te te-class
show mpls traffic-eng forwarding
show mpls traffic-eng forwarding-adjacency
show mpls traffic-eng igp-areas
show mpls traffic-eng link-management admission-control
show mpls traffic-eng link-management advertisements
show mpls traffic-eng link-management bandwidth-allocation
show mpls traffic-eng link-management bfd-neighbors
show mpls traffic-eng link-management igp-neighbors
show mpls traffic-eng link-management interfaces
show mpls traffic-eng link-management statistics
show mpls traffic-eng link-management summary
show mpls traffic-eng maximum tunnels
show mpls traffic-eng topology
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
•
•
•
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 the
Cisco IOS XR MPLS Configuration Guide.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
Defaults
weight: IGP Weight (default OSPF 1, ISIS 10)
Command Modes
MPLS-TE interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0RP/0/RP0/CPU0:router(config-mpls-te-if)# admin-weight 20Related 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
Defaults
affinity-value: 0X00000000
mask-value: 0XFFFFFFFF
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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_maskTask ID
Examples
The following example shows how to configure the tunnel affinity and mask:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# affinity 0101 mask 303Related Commands
Assigns a numerical value to each affinity name.
Configures attributes for the interface.
affinity-map
To assign a numerical value to each affinity name, use the attribute-map command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
attribute-map affinity name
no attribute-map affinity name
Syntax Description
DefaultsDefaults
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to assign a numerical value to each affinity name:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# affinity-map red 1RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map blue 2Related Commands
Configures an affinity for an MPLS-TE tunnel.
Displays the color name-to-value mappings configured on the router.
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
DefaultsDefaults
attributes: 0x0
Command Modes
MPLS-TE interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to set attribute flags to 0x0101:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-flags 0x0101Related Commands
attribute-names
To assign a numerical value to each affinity name, 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
DefaultsDefaults
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to assign an attribute name (in this case, red) to a TE link:
RP/0/RP0/CPU0:router## configRP/0/RP0/CPU0:router(config)# mpls traffic-eng int pos 0/2/0/1RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-name redRelated 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# autoroute announceRelated Commands
Sets the mode of a tunnel to MPLS for TE, and moves the configuration mode into tunnel mode.
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
Defaults
relative value: 0
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# autoroute metric relative -1Related Commands
Instructs the IGP to use the tunnel (if it is up) in its enhanced SPF calculation.
Displays the tunnels announced to the IGP, including interface, destination, and bandwidth.
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
Defaults
Any class-type unlimited.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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).
Task ID
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 1RP/0/RP0/CPU0:router(config-if)# backup-bw global-pool unlimitedorRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# backup-bw unlimited class-type 0In 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# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 2RP/0/RP0/CPU0:router(config-if)# backup-bw sub-pool 1000orRP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 2RP/0/RP0/CPU0:router(config-if)# backup-bw 1000 class-type 1Related Commands
Assigns one or more backup tunnels to a protected interface.
Configures an LSP to request a protection via backup tunnel.
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
Defaults
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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:
•
•
•
•
•
•
Note
Task ID
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# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel 100RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel 150Related Commands
Configures backup bandwidth for bandwidth protection.
Makes a tunnel a protected LSP.
Displays tunnel information.
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.0
This command was introduced on the on the Cisco XR 12000 Series Router and Cisco CRS-1 router.
Release 3.4.0
No modification.
Release 3.5.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear all LMP management hello settings:
RP/0/RP0/CPU0:router# clear mpls lmpclear mpls traffic-eng counters tunnels
To clear (set to zero) the MPLS tunnel signaling counters, use the clear mpls traffic-eng counters tunnels command in EXEC mode.
clear mpls traffic-eng counters tunnels {all [heads | middles | tails] | name name | summary}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear mpls traffic-eng counters tunnels command to set all MPLS counters to zero so that changes can be seen easily.
Task ID
Examples
The following example shows how to clear all counters:
RP/0/RP0/CPU0:router# clear mpls traffic-eng counters tunnels allThe following example shows how to clear counters for tunnel 1:
RP/0/RP0/CPU0:router# clear mpls traffic-eng counters tunnels name tunnel-te1Related 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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
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 logNode Protected LSPs Rewrites When Switching TimeInterface (usec)-------- --------- ----- -------- ---------------------- --------------0/0/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.064000 1470/1/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.060093 1650/2/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.063814 1290/3/CPU0 PO0/1/0/1 1 1 Feb 27 19:12:29.062861 128RP/0/RP0/CPU0:router# clear mpls traffic-eng fast-reroute logclear 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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
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 statisticsdestination
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 A.B.C.D
no destination A.B.C.D
Syntax Description
Defaults
None
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to set the destination address for tunnel-te1 to 10.10.10.10:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te1RP/0/RP0/CPU0:router(config-if)# destination 10.10.10.10Related Commands
direction (GMPLS)
To configure a bidirectional optical tunnel for GMPLS, use the direction command in interface configuration mode. To return to the default behavior, use the no form of this command.
direction {bidirectional}
no direction {bidirectional}
Syntax Description
Defaults
Default is unidirectional
Command Modes
Interface configuration
Command History
Release 3.3.0
This command was introduced on the Cisco CRS-1and Cisco XR 12000 Series Router.
Release 3.4.0
No modification.
Release 3.5.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
There are two types of MPLS-TE tunnels:
•
•
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
Task ID
Examples
The following example shows how to change the tunnel direction from the default (unidirectional) to bidirectional:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 99RP/0/RP0/CPU0:router(config-if)# direction bidirectionalRelated 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
Syntax Description
This command has no arguments or keywords.
Defaults
Explicit path is enabled
Command Modes
Explicit path configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to disable explicit path 200:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# explicit-path identifier 200RP/0/RP0/CPU0:router(config-expl-path)# disableRelated Commands
Specifies the next IP address to exclude from the explicit path.
Specifies path entries at a specific index.
Displays the configured IP explicit paths.
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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
Task ID
Examples
The following example shows how to enable FRR on an MPLS-TE tunnel:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# fast-rerouteRelated 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
Defaults
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
A GMPLS link won't be flooded into any IGP topology unless this command is used.
Note
Task ID
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# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# interface pos0/1/0/0RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding-igp ospf optical area 0Related 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
Threshold for decreased resource availability.
up
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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding thresholds down 100 75 25RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding thresholds up 25 50 100Related 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) Holdtime value 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not specify a holdtime time value, a delay is introduced with the following results:
•
•
•
•
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.
Task ID
Examples
The following example shows how to configure forwarding adjacency with a holdtime value of 60 milliseconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 888RP/0/RP0/CPU0:router(config-if)# forwarding-adjacency holdtime 60Related Commands
bandwidth (RSVP)
Configures RSVP bandwidth on an interface using prestandard DS-TE mode.
Displays forwarding-adjacency information.
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
Defaults
No default behavior or values
Command Modes
Explicit path configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
MPLS-TE accepts IP explicit paths composed of all excluded addresses configured using the exclude-address keyword.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# explicit-path identifier 200RP/0/RP0/CPU0:router(config-expl-path)# index 3 exclude-address ipv4 unicast 192.168.3.2Related Commands
Specifies path entries at a specific index.
Displays the configured IP explicit paths.
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
Defaults
No default behavior or values
Command Modes
Explicit path configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
Task ID
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# configureRP/0/RP0/CPU0:router(config)# explicit-path identifier 200RP/0/RP0/CPU0:router(config-expl-path)# index 3 next-address ipv4 unicast 192.168.3.2Related Commands
Specifies the next IP address to exclude from the explicit path.
Displays configured IP explicit paths.
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
Defaults
Tunnel interfaces are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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:
•
•
•
•
•
•
•
•
•
•
•
Note
Task ID
Examples
The following example shows how to configure tunnel interface 1:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0Related 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 interface-name
no ipv4 unnumbered interface-name
Syntax Description
Defaults
No IP address is set
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0load-share
To configure 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to configure load-sharing parameters on a specified interface:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 100RP/0/RP0/CPU0:router(config-if)# load-share 100Related Commands
Enables unequal load-sharing.
Configures the bandwidth required for an MPLS TE tunnel.
load-share unequal
To configure unequal load-sharing, 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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to enable unequal load-sharing:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# load-share unequalRelated Commands
Configures load-sharing balancing parameters for a specified interface.
Configures the bandwidth required for an MPLS TE tunnel.
lmp hello (GMPLS)
To configure Link Management Protocol (LMP) IPCC management hello settings, use the lmp hello command in MPLS-TE neighbor lmp configuration submode. 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
Defaults
No default behavior or values
Command Modes
MPLS-TE neighbor lmp configuration submode
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You can disable hellos using the lmp static command.
Task ID
Examples
The following example shows how to configure Link Management Protocol (LMP) IPCC management hello settings:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor lmpRP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor gmpls3 lmp hello 400 1200Related Commands
match (GMPLS)
To match an active tunnel to a passive tunnel, use the match command in interface 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
Id 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 configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You must enter the hostname for the head router then underscore _t, and the tunnel number for the head router. If tunnel-te1 is configured on the head router with a hostname of gmpls1, CLI is match identifier gmpls1_t1.
Task ID
Examples
The following example shows how to match the active tunnel ID to the passive tunnel:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# match identifier gmpls1_t1Related Commands
mpls traffic-eng 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 mpls traffic-eng ds-te bc-model command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng ds-te bc-model mam
no mpls traffic-eng ds-te bc-model mam
Syntax Description
Defaults
RDM is the default bandwidth constraint model.
Command Modes
Global configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
Task ID
Examples
The following example shows how to enable the MAM bandwidth constraints model:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# mpls traffic-eng ds-te bc-model mamRelated Commands
mpls traffic-eng ds-te mode
To configure standard differentiated-service TE mode (DS-TE), use the mpls traffic-eng ds-te mode command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng ds-te mode {ietf}
no mpls traffic-eng ds-te mode {ietf}
Syntax Description
Defaults
Prestandard DS-TE is the default differentiated service mode.
Command Modes
Global configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The following two DS-TE modes are supported:
•
–
•
–
–
–
–
–
–
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
Task ID
Examples
The following example shows how to enable IETF standard mode:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# mpls traffic-eng ds-te mode ietfRelated Commands
Configures MPLS DS-TE TE-class maps.
Displays the Diff-Serv TE-class map in use.
mpls traffic-eng ds-te te-classes
To enter DS-TE te-class map configuration mode, use the mpls traffic-eng ds-te te-classes command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng ds-te te-classes {te-class te_class_index class-type class_type_number priority pri_number}
no mpls traffic-eng ds-te te-classes {te-class te_class_index class-type class_type_number priority pri_number}
Syntax Description
Defaults
The following default te-class maps are used in IETF DS-TE mode
Note
Command Modes
Global configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to configure a TE-class 7 parameter:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# mpls traffic-eng ds-te te-classesRP/0/RP0/CPU0:router(config-te-class)# te-class 7 class-type 0 priority 4Related Commands
Configures MPLS DS-TE TE-class maps.
Displays the Diff-Serv TE-class map in use.
mpls traffic-eng fast-reroute promote
To configure the router to assign a 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.
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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to initiate backup tunnel promote and assignment:
RP/0/RP0/CPU0:router# mpls traffic-eng fast-reroute promoteRelated Commands
Specifies how often the router considers switching a protected MPLS-TE tunnel to a new backup tunnel.
mpls traffic-eng fast-reroute timers promotion
To specify 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 mpls traffic-eng fast-reroute timers promotion command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng fast-reroute timers promotion {interval}
no mpls traffic-eng 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
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configRP/0/RP0/CPU0:router(config)# mpls traffic-eng fast-reroute timers promotion 600Related Commands
Configures the router to use a new or more efficient backup MPLS-TE tunnel when a current tunnel is overloaded.
mpls traffic-eng interface
To enable MPLS-TE on an interface and to enter MPLS-TE interface submode, use the mpls traffic-eng interface command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng interface type instance
no mpls traffic-eng interface type instance
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to enter the MPLS-TE interface configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/1The following example shows how to remove an interface from the MPLS-TE domain:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engRP/0/RP0/CPU0:router(config-mpls-te)# no interface POS 0/7/0/1mpls 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
Defaults
No default behavior or values
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
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# configureRP/0/RP0/CPU0:router(config)# router isis 1RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng level 1RP/0/RP0/CPU0:router(config-isis-af)# metric-style wideRelated Commands
Specifies that the TE router identifier for the node is the IP address associated with a given interface.
mpls traffic-eng link-management flood
To initiate an 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
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
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 floodRelated Commands
mpls traffic-eng 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 mpls traffic-eng link-management timers bandwidth-hold command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng link-management timers bandwidth-hold holdtime
no mpls traffic-eng link-management timers bandwidth-hold holdtime
Syntax Description
Defaults
holdtime: 15 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command determines the time allowed for an RSVP message to return from a neighbor RSVP node.
Task ID
Examples
The following example shows how to set the bandwidth to be held for 10 seconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng link-management timers bandwidth-hold 10Related Commands
mpls traffic-eng link-management timers periodic-flooding
To set the length of the interval for periodic flooding, use the mpls traffic-eng link-management timers periodic-flooding command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng link-management timers periodic-flooding interval
no mpls traffic-eng 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
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the mpls traffic-eng link-management timers periodic-flooding command to advertise link state information changes that do not trigger immediate action, such as a change to the allocated bandwidth that does not cross a threshold.
Task ID
Examples
The following example shows how to set the interval length for periodic flooding to 120 seconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng link-management timers periodic-flooding 120Related Commands
Sets the reserved bandwidth flooding thresholds for a link.
Displays the current periodic flooding interval.
mpls traffic-eng lmp router-id
To configure the router ID for the optical instance using the LMP protocol, use the mpls traffic-eng lmp router-id command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng lmp router-id [ipv4 address | interface-name]
no mpls traffic-eng lmp router-id [ipv4 address | interface-name]
Syntax Description
ipv4 address
(Optional) The router ID expressed as an IPv4 address.
interface-name
(Optional) The router ID expressed as an interface name.
Defaults
No default behavior or values
Command Modes
MPLS-TE configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how configure the LMP router ID for IPv4 address 172.24.20.164:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-engineeringRP/0/RP0/CPU0:router(config-mpls-te)# lmp router-id router 172.24.20.164
Related Commands
mpls traffic-eng maximum tunnels
To specify the maximum number of MPLS-TE tunnels that can be configured, use the mpls traffic-eng maximum tunnels command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng maximum tunnels {tunnel-limit}
no mpls traffic-eng maximum tunnels {tunnel-limit}
Syntax Description
Defaults
tunnel-limit: 2500
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to set the tunnel-te configuration limit to 3000:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng maximum tunnels 3000Related 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 global configuration 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
Global 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example sets the tunnel ID number to 1:
RP/0/RP0/CPU0:router(config)# mpls traffic-eng path-protection switchover 1Related Commands
mpls traffic-eng path-selection loose-expansion affinity
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 mpls traffic-eng path-selection loose-expansion affinity command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng path-selection loose-expansion affinity affinity-value mask affinity-mask [class-type type]
no mpls traffic-eng path-selection loose-expansion affinity affinity-value mask affinity-mask [class-type type]
Syntax Description
Defaults
affinity-value: 0X00000000
mask-value: 0XFFFFFFFF
Command Modes
Global 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to configure affinity 0x55 with mask 0xFFFFFFFF:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng path-selection loose-expansion affinity 55 mask FFFFFFFFRelated Commands
Configures a metric type to be used to expand a path to the next loose hop for a tunnel on an area border router.
Configures the MPLS-TE tunnel path-selection metric.
mpls traffic-eng path-selection loose-expansion metric
To specify 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 mpls traffic-eng path-selection loose-expansion metric command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng path-selection loose-expansion metric {igp | te} [class-type type]
no mpls traffic-eng path-selection loose-expansion metric {igp | te} [class-type type]
Syntax Description
igp
Uses an Interior Gateway Protocol (IGP) metric.
te
Uses a TE metric. This is the default.
class-type type
(Optional) Class-type of the tunnel bandwidth request. Range is 0 to 1.
Defaults
TE Metric
Command Modes
Global 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to set the path-selection metric to use the IGP metric overwriting default:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng path-selection loose-expansion metric igpRelated Commands
mpls traffic-eng path-selection metric
To specify the MPLS-TE tunnel path-selection metric, use the mpls traffic-eng path-selection metric command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng path-selection metric {igp | te}
no mpls traffic-eng path-selection metric {igp | te}
Syntax Description
igp
Uses an Interior Gateway Protocol (IGP) metric.
te
Uses a TE metric. This is the default variable.
Defaults
TE metric
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The metric type to be used for path calculation for a given tunnel is determined as follows:
•
•
•
Task ID
Examples
The following example shows how to set the path-selection metric to use the IGP metric overwriting default:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng path-selection metric igpRelated Commands
mpls traffic-eng pce address
To configure the IPv4 self address for Path Computation Element (PCE), use the mpls traffic-eng pce address command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng pce address ipv4 address
no mpls traffic-eng pce address ipv4 address
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.5.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The IP address is used in the TCP communication with the other PCEs or PCCs. Also, this address is advertised using IGP.
Task ID
Examples
The following example shows how to configure the IPv4 self address for PCE:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng pce address ipv4 10.10.10.10Related Commands
Configures an IPv4 self address for a PCE peer.
Configures a path option for an MPLS-TE tunnel.
mpls traffic-eng pce peer
To configure an IPv4 self address for a PCE peer, use the mpls traffic-eng pce peer command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng pce peer ipv4 address
no mpls traffic-eng pce peer ipv4 address
Syntax Description
Defaults
TE metric
Command Modes
Global configuration
Command History
Release 3.5.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure an IPv4 self address for a PCE peer:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng pce peer ipv4 11.11.11.11Related Commands
Configures the IPv4 self address for PCE.
Configures a path option for an MPLS-TE tunnel.
mpls traffic-eng reoptimize (Config)
To configure the reoptimization interval for all TE tunnels, use the mpls traffic-eng reoptimize command in EXEC mode. To return to the default behavior, use the no form of this command
mpls traffic-eng reoptimize {frequency}
no mpls traffic-eng reoptimize {frequency}
Syntax Description
Defaults
3600 seconds
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure reoptimization interval to 60 seconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router#(config) mpls traffic-eng reoptimize 60Related 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
MPLS-TE tunnel identification expressed as a number.
tunnel_name
TE tunnel identification expressed as a name.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to immediately reoptimize all TE tunnels reoptimized:
RP/0/RP0/CPU0:router# mpls traffic-eng reoptimizeThe following example shows how to immediately reoptimize TE tunnel-te90:
RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize tunnel-te90Related Commands
mpls traffic-eng reoptimize timers delay
To delay removal or relabeling of the old label switched paths (LSPs) (reoptimized LSP from the forwarding plane) after tunnel reoptimization, use the mpls traffic-eng reoptimize timers delay command in global configuration mode. To restore the default value, use the no form of this command.
mpls traffic-eng reoptimize timers delay {cleanup | installation} delay-time
no mpls traffic-eng reoptimize timers delay {cleanup | installation} delay-time
Syntax Description
Defaults
cleanup: 20 seconds
installation: 20 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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 mpls traffic-eng 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# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng reoptimize timer delay cleanup 60The following example shows how to set the reoptimization installation delay time to 1 hour:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng reoptimize delay installation 3600Related Commands
Reoptimizes all traffic engineering tunnels immediately.
Configures the reoptimization interval of all TE tunnels.
mpls traffic-eng router-id
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 router configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng router-id interface-name
no mpls traffic-eng no router-id interface-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
Task ID
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# configureRP/0/RP0/CPU0:router(config)# router ospf 1RP/0/RP0/CPU0:router(config-router)# mpls traffic-eng router-id Loopback0RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router isis 1RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng router-id Loopback0Related Commands
Configures a router running OSPF MPLS so that it floods TE for the indicated IS-IS level.
mpls traffic-eng router-id secondary
To configure a secondary TE router identifier in MPLS-TE to be used locally (not advertised through IGP), use the mpls traffic-eng router-id secondary command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng router-id secondary A.B.C.D
no mpls traffic-eng no router-id secondary A.B.C.D
Syntax Description
Defaults
No default behavior or values
Command Modes
Global 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the mpls traffic-eng 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.
Task ID
Examples
The following example shows how to configure a secondary TE router identifier in MPLS-TE:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng router-id secondary 1.1.1.1RP/0/RP0/CPU0:router(config)# mpls traffic-eng router-id secondary 2.2.2.2Related Commands
Specifies that the TE router identifier for the node is the IP address associated with a given interface.
mpls traffic-eng signalling advertise explicit-null
To specify that tunnels terminating on a router use explicit-null labels, use the mpls traffic-eng signalling advertise explicit-null command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng signalling advertise explicit-null
no mpls traffic-eng signalling advertise explicit-null
Syntax Description
This command has no arguments or keywords.
Defaults
Implicit-null labels are advertised.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the mpls traffic-eng 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).
Task ID
Examples
The following example shows how to configure explicit null tunnel labels:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng signalling advertise explicit-nullRelated Commands
Configures a metric type to be used to expand a path to the next loose hop for a tunnel on an area border router.
mpls traffic-eng timers loose-path
To configure the period between the headend retries after path errors, use the mpls traffic-eng timers loose-path command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng timers loose-path retry-period value
no mpls traffic-eng timers loose-path retry-period value
Syntax Description
Defaults
retry-period value: 120 seconds
Command Modes
Global 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to the period between retries after path errors to 300 seconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng timers loose-path retry-period 300Related Commands
mpls traffic-eng topology holddown sigerr
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 signalling error on the link, use the mpls traffic-eng topology holddown sigerr command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls traffic-eng topology holddown sigerr seconds
no mpls traffic-eng topology holddown sigerr seconds
Syntax Description
seconds
Time 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
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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 mpls traffic-eng topology holddown sigerr command to change the link holddown time from its 10-second default value.
Task ID
Examples
The following example shows how to set the link holddown time for signaling errors at 15 seconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng topology holddown sigerr 15Related Commands
Displays the current MPLS-TE global topology of this node as well as the signaling error holddown time.
passive (GMPLS)
To configure a passive GMPLS tunnel, use the passive command in tunnel-te interface 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-te configuration
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure a passive GMPLS virtual interface tunnel:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 99RP/0/RP0/CPU0:router(config-if)# passiveRelated 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 {number | protecting number} {dynamic | explicit {name pathname | path-number}} [verbatim] [lockdown]
no path-option {number | protecting number} {dynamic | explicit {name pathname | path-number}} [verbatim] [lockdown]
Syntax Description
Defaults
No default behavior or values
Command Modes
Tunnel-te interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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
Task ID
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 1RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name test verbatim lockdownThe 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 1RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name po4RP/0/RP0/CPU0:router(config-if)# path-option protecting 1 explicit name po6Related Commands
Specifies a switchover for path protection.
Displays the configured IP explicit paths.
path-selection metric
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
Defaults
TE metrics
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The metric type to be used for path calculation for a given tunnel is determined as follows:
•
•
•
Task ID
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# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# path-selection metric igpRelated Commands
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
Defaults
setup-priority: 7
hold-priority: 7
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following example shows how to configure a tunnel with a setup and hold priority of 1:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# priority 1 1Related Commands
Sets the mode of a tunnel to MPLS for TE, and enters interface configuration mode.
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
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to enable record-route on the TE tunnel:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-if)# record-routeRelated Commands
remote (GMPLS)
To configure LMP Neighbor remote 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
Defaults
No default behavior or values
Command Modes
LMP data link adjacency configuration mode
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure LMP Neighbor remote TE links for unnumber interface-id 1066:
RP0/0/RP0/CPU0:router# configureRP0/0/RP0/CPU0:router(config)# mpls traffic-engRP0/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/1/0/0RP0/0/RP0/CPU0:router(config-mpls-te-if)# lmp data-link adjacencyRP0/0/RP0/CPU0:router(config-mpls-te-if-adj)# remote interface-id unnnum 1066Related 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) Name of the explicit path.
identifier number
(Optional) Number of the explicit path. Range is 1 to 65535.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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.
Task ID
Examples
The following is sample output from the show explicit-paths command:
RP/0/RP0/CPU0:router# show explicit-pathsPath ToR2 status enabled0x1: next-address 192.168.1.20x2: next-address 10.20.20.20Path ToR3 status enabled0x1: next-address 192.168.1.20x2: next-address 192.168.2.20x3: next-address 10.30.30.30Path 100 status enabled0x1: next-address 192.168.1.20x2: next-address 10.20.20.20Path 200 status enabled0x1: next-address 192.168.1.20x2: next-address 192.168.2.20x3: next-address 10.30.30.30Table 49 describes the significant fields shown in the display.
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 ToR3Path ToR3 status enabled0x1: next-address 192.168.1.20x2: next-address 192.168.2.20x3: next-address 10.30.30.30The following is sample output from the show explicit-paths command using a specific path number:
RP/0/RP0/CPU0:router# show explicit-paths identifier 200Path 200 status enabled0x1: next-address 192.168.1.20x2: next-address 192.168.2.20x3: next-address 10.30.30.30Related Commands
Specifies the next IP address to exclude from the explicit path.
Specifies path entries at a specific index.
show mpls traffic-eng affinity-map
To display the color name-to-value mappings configured on the router, use the show mpls traffic-eng autoroute 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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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)"
Task ID
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-mapAffinity Name Affinity Value----------------- -----------------blue 0x2green 0x4red 0x1Table 50 describes the significant fields shown in the display.
Table 50 show mpls traffic-eng affinity-map Field Descriptions
Affinity Name/Affinity Value
Displays the affinity names and values associated with the tunnel affinity constraints.
Related Commands
Configures an affinity for an MPLS-TE tunnel
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
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the 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).
Task ID
Examples
The following is sample output from the show mpls traffic-eng autoroute command:
RP/0/RP0/CPU0:router# show mpls traffic-eng autorouteDestination 103.0.0.3 has 2 tunnels in OSPF 0 area 0tunnel-te1 (traffic share 1, nexthop 103.0.0.3)tunnel-te2 (traffic share 1, nexthop 103.0.0.3)
Note
Table 51 describes the significant fields shown in the display.
Related Commands
show mpls traffic-eng counters tunnel
To display tunnel signaling statistics, use the show mpls traffic-eng counters tunnel command in EXEC mode.
show mpls traffic-eng counters tunnel {tunnel number | all [heads | middles | tails] | name | summary}
Related Commands
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following is sample output from the show mpls traffic-eng counters tunnel command, using the all keyword, which displays tunnel signaling statistics for all tunnels:
RP/0/RP0/CPU0:router# show mpls traffic-eng counters tunnel allTunnel Head: tunnel-te160Match Resv Create: 5 Sender Create: 4 Path Error: 0Match Resv Change: 0 Sender Modify: 1 Path Change: 0Match Resv Delete: 3 Sender Delete: 3 Path Delete: 1Total: 21 Unknown: 4Tunnel Head: tunnel-te170Match Resv Create: 0 Sender Create: 0 Path Error: 0Match Resv Change: 0 Sender Modify: 0 Path Change: 0Match Resv Delete: 0 Sender Delete: 0 Path Delete: 0Total: 0 Unknown: 0The following is sample output from the show mpls traffic-eng counters tunnel command using the tunnel number argument, which displays statistics for the input tunnel number:
RP/0/RP0/CPU0:router# show mpls traffic-eng counters tunnel 1Tunnel Head: tunnel-te1Match Resv Create: 1 Sender Create: 1 Path Error: 0Match Resv Change: 0 Sender Modify: 0 Path Change: 0Match Resv Delete: 0 Sender Delete: 0 Path Delete: 0Total: 3 Unknown: 0Table 52 describes the significant fields shown in the display.
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.
Command Modes
EXEC
Command History
Release 3.3.0
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.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
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-classte-class 0: class-type 0 priority 7 status defaultte-class 1: class-type 1 priority 7 status defaultte-class 2: unusedte-class 3: unusedte-class 4: class-type 0 priority 0 status defaultte-class 5: class-type 1 priority 0 status defaultte-class 6: unusedte-class 7: unusedTable 53 describes the significant fields shown in the display.
