Table Of Contents

MPLS Traffic Engineering Commands on Cisco IOS XR Software

admin-weight

affinity

affinity-map

attribute-flags

attribute-names

autoroute announce

autoroute metric

backup-bw

backup-path tunnel-te

clear mpls lmp

clear mpls traffic-eng counters tunnels

clear mpls traffic-eng fast-reroute log

clear mpls traffic-eng link-management statistics

destination (MPLS-TE)

direction (GMPLS)

disable (explicit-path)

explicit-path

fast-reroute

fast-reroute protect

flooding-igp (GMPLS)

flooding thresholds

forwarding-adjacency

index exclude-address

index next-address

interface tunnel-te

ipv4 unnumbered (MPLS)

load-share

load-share unequal

lmp hello (GMPLS)

match (GMPLS)

mpls traffic-eng ds-te bc-model

mpls traffic-eng ds-te mode

mpls traffic-eng ds-te te-classes

mpls traffic-eng fast-reroute promote

mpls traffic-eng fast-reroute timers promotion

mpls traffic-eng interface

mpls traffic-eng level

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 ignore overload

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 pce address

mpls traffic-eng pce peer

mpls traffic-eng reoptimize (global)

mpls traffic-eng reoptimize (EXEC)

mpls traffic-eng reoptimize timers delay

mpls traffic-eng router-id (MPLS-TE)

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

passive (GMPLS)

path-option

path-selection metric

policy-class

priority (MPLS-TE)

record-route

remote (GMPLS)

show explicit-paths

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

show mpls traffic-eng tunnels

signalled-bandwidth

signalled-name

snmp traps mpls traffic-eng

switching (GMPLS)

switching endpoint (GMPLS)

switching transit (GMPLS)

MPLS Traffic Engineering Commands on Cisco IOS XR Software

---

This chapter describes the commands that you will use to configure Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) and Generalized MPLS (GMPLS). In this chapter, all GMPLS-specific commands are identified with "(GMPLS)" in the command title.

Your network must support the following Cisco features before you can enable MPLS-TE:

•MPLS

•IP Cisco Express Forwarding (CEF)

•Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF) routing protocol

•Resource Reservation Protocol (RSVP)

MPLS Label Distribution Protocol (LDP), Resource Reservation Protocol (RSVP), and Universal Control Plane (UCP) command descriptions are documented separately.

For detailed information about MPLS concepts, configuration tasks, and examples, refer to 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

weight

The administrative weight (cost) of the link. Range is 0 to 4294967295.

Defaults

weight: IGP Weight (default OSPF 1, ISIS 10)

Command Modes

MPLS-TE interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was introduced on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to override the IGP cost of the link and set the cost to 20:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# mpls traffic-eng

RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0

RP/0/RP0/CPU0:router(config-mpls-te-if)# admin-weight 20

Related Commands

Command	Description
path-selection metric	Select Path Selection Metric as TE or IGP.

affinity

To configure an affinity (the properties the tunnel requires in its links) for an MPLS-TE tunnel, use the affinity command in interface configuration mode. To return to the default behavior, use the no form of this command.

affinity {{affinity-value mask mask-value} | exclude name | exclude-all | include name | include-strict name}

no affinity {{affinity-value mask mask-value} | exclude name | exclude-all | include name | include-strict name}

Syntax Description

affinity-value	Configures the attribute values that are required for links to carry this tunnel. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1.
mask mask-value	Checks the link attribute. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute mask is 0 or 1.
exclude name	Configures a particular affinity to exclude.
exclude-all	Excludes all affinities.
include	Configures the affinity to include in the loose sense.
include-strict	Configures the affinity to include in the strict sense.

Defaults

affinity-value: 0X00000000

mask-value: 0XFFFFFFFF

Command Modes

Interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	Support was added for the Name-Based Affinity Constraint scheme.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	Affinity colors definition for MPLS-TE was added.

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_mask

You can configure up to 16 affinity constraints under a given tunnel. The following constraints are used to configure affinity constraints for the tunnel:

•Include constraint—Specifies that a link is considered for CSPF if it contains all the affinities associated with the include constraint. An acceptable link contains more affinity attributes than those associated with the include statement. You can have multiple include statements under a tunnel configuration.

•Include-strict constraint—Specifies that a link is considered for CSPF if it contains only the colors associated with the include-strict statement. The link cannot have any additional colors. In addition, a link without a color is rejected.

•Exclude constraint—Specifies that a link satisfies an exclude constraint if it does not have all the colors associated with the constraint. In addition, a link that does not have any attribute satisfies an exclude constraint.

•Exclude-all constraint—Specifies that only the links without any attribute are considered for CSPF. An exclude-all constraint is not associated with any color; whereas, all other constraint types are associated with up to 10 colors.

You are setting one bit for each color; however, the sample output shows multiple bits at the same time. For example, you can configure red and black colors on GigabitEthernet0/4/1/3 from the interface command. The sample output from the show mpls traffic-eng link-management interfaces command shows that the Attributes field is set to 0x21, which means that there are 0x20 and 0x1 bits on the link.

Task ID

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to configure the tunnel affinity and mask:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity 0101 mask 303

The following example shows that a link is eligible for CSPF if it has at least red color. The link can have any additional colors.

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity include red

The following example shows that a link is eligible for CSPF if it has at least red and black colors. The link can have any additional colors.

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity include red black

The following sample output shows that the include constraint from the show mpls traffic-eng tunnels command is 0x20 and 0x1:

Name: tunnel-te1 Destination: 0.0.0.0

   Status:

     Admin:    up Oper: down   Path: not valid   Signalling: Down

     G-PID: 0x0800 (internally specified)

   Config Parameters:

     Bandwidth:        0 kbps (CT0) Priority:  7  7

     Number of configured name based affinity constraints: 1

     Name based affinity constraints in use:

        Include bit map       : 0x21

     Metric Type: TE (default)

     AutoRoute:  disabled  LockDown: disabled

     Loadshare:          0 equal loadshares

     Auto-bw: disabled(0/0) 0  Bandwidth Requested:        0

     Direction: unidirectional

     Endpoint switching capability: unknown, encoding type: unassigned

     Transit switching capability: unknown, encoding type: unassigned

   Reason for the tunnel being down: No destination is configured

   History:

The following example shows that a tunnel can go over a link that contains red or black affinity. A link is eligible for CSPF if it has a red color or a black color. Thus, a link with red and any other colors and a link with black and any additional colors must meet the constraint.

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity include red

RP/0/RP0/CPU0:router(config-if)# affinity include black

The following sample output shows that the include constraint from the show mpls traffic-eng tunnels command is 0x20 or 0x1:

Name: tunnel-te1 Destination: 0.0.0.0

   Status:

     Admin:    up Oper: down   Path: not valid   Signalling: Down

     G-PID: 0x0800 (internally specified)

   Config Parameters:

     Bandwidth:        0 kbps (CT0) Priority:  7  7

     Number of configured name based affinity constraints: 2

     Name based affinity constraints in use:

        Include bit map       : 0x1

        Include bit map       : 0x20

     Metric Type: TE (default)

     AutoRoute:  disabled  LockDown: disabled

     Loadshare:          0 equal loadshares

     Auto-bw: disabled(0/0) 0  Bandwidth Requested:        0

     Direction: unidirectional

     Endpoint switching capability: unknown, encoding type: unassigned

     Transit switching capability: unknown, encoding type: unassigned

   Reason for the tunnel being down: No destination is configured

   History:

The following example shows that a link is eligible for CSPF if it has only red color. The link must not have any additional colors.

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity include-strict red

The following example shows that a link is eligible for CSPF if it does not have the red attribute:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity exclude red

The following example shows that a link is eligible for CSPF if it does not have red and blue attributes. Thus, a link that has only a red attribute or only a blue attribute is eligible for CSPF.

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity exclude red blue

The following example shows that a link is eligible for CSPF if it does not have either a red or a blue attribute:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# affinity exclude red

RP/0/RP0/CPU0:router(config-if)# affinity exclude blue

Related Commands

Command	Description
affinity-map	Assigns a numerical value to each affinity name.
attribute-flags	Configures attributes for the interface.
attribute-names	Configures attributes for the interface.
show mpls traffic-eng affinity-map	Displays the color name-to-value mappings configured on the router.
show mpls traffic-eng tunnels	Displays information about MPLS-TE tunnels.

affinity-map

To assign a numerical value to each affinity name, use the affinity-map command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

affinity-map affinity name

no affinity-map affinity name

Syntax Description

affinity name

Affinity map name-to-value designator (in hexadecimal, 0-ffffffff).

DefaultsDefaults

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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 The name-to-value mapping must represent a single bit of a 32-bit value.

---

Task ID

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to assign a numerical value to each affinity name:

RP/0/RP0/CPU0:router# config

RP/0/RP0/CPU0:router(config)# mpls traffic-eng

RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map red 1

RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map blue 2

Related Commands

Command	Description
affinity	Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel.
show mpls traffic-eng affinity-map	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

attribute flags

Links attributes that are compared to the affinity bits of a tunnel during selection of a path. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits) where the value of an attribute is 0 or 1.

DefaultsDefaults

attributes: 0x0

Command Modes

MPLS-TE interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to set attribute flags to 0x0101:

RP/0/RP0/CPU0:router# configure 

RP/0/RP0/CPU0:router(config)# mpls traffic-eng

RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0

RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-flags 0x0101

Related Commands

Command	Description
admin-weight	Overrides the IGP administrative weight of the link.
affinity	Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel.
attribute-names	Configures attributes for the interface.

attribute-names

To configure attributes for the interface, use the attribute-names command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.

attribute-names attribute name

no attribute-names attribute name

Syntax Description

attribute name

Attribute name expressed using alphanumeric or hexidecimal characters.

Defaults

No default behavior or values

Command Modes

MPLS-TE interface configuration

Command History

Release	Modification
Release 3.4.0	This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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 The name-to-value mapping must represent a single bit of a 32-bit value.

---

Task ID

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to assign an attribute name (in this case, red) to a TE link:

RP/0/RP0/CPU0:router# config

RP/0/RP0/CPU0:router(config)# mpls traffic-eng int pos 0/2/0/1

RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-name red

Related Commands

Command	Description
affinity	Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel.
attribute-flags	Configures attribute flags for the interface.

autoroute announce

To specify that the Interior Gateway Protocol (IGP) should use the tunnel (if the tunnel is up) in its enhanced shortest path first (SPF) calculation, use the autoroute announce command in interface configuration mode. To return to the default behavior, use the no form of this command.

autoroute announce

no autoroute announce

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to configure IGP to use the tunnel in its enhanced SPF calculation when the tunnel is up:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1

RP/0/RP0/CPU0:router(config-if)# autoroute announce

Related Commands

Command	Description
interface tunnel-te	Configures an MPLS-TE tunnel interface.

autoroute metric

To specify the MPLS-TE tunnel metric that the Interior Gateway Protocol (IGP) enhanced Shortest Path First (SPF) calculation uses, use the autoroute metric command in interface configuration mode. To return to the default behavior, use the no form of this command.

autoroute metric {absolute | relative} value

no autoroute metric {absolute | relative} value

Syntax Description

absolute	Absolute metric mode; you can enter a positive metric value.
relative	Relative metric mode; you can enter a positive, negative, or zero value.
value	The metric that the IGP enhanced SPF calculation uses. Relative value range is -10 to 10. Absolute value is 1 to 4294967295.

Defaults

relative value: 0

Command Modes

Interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to configure the IGP enhanced SPF calculation using MPLS-TE tunnel metric as relative negative 1:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# autoroute metric relative -1 

Related Commands

Command	Description
autoroute announce	Instructs the IGP to use the tunnel (if it is up) in its enhanced SPF calculation.
show mpls traffic-eng autoroute	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

backup bandwidth	Backup bandwidth in any-pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second (kbps). Range is 1 to 4294967295.
any-class-type	Backup bandwidth assigned to any class-type protected tunnels.
class-type ct	Class type of the backup bandwidth. Range is 0 to 1.
sub-pool bandwidth	(In Prestandard DS-TE with RDM) Backup bandwidth in sub-pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second. Range bandwidth is 1 to 4294967295. Only label switched paths (LSPs) using bandwidth from the sub-pool can use the backup tunnel.
global-pool bandwidth	(In Prestandard DS-TE with RDM) Backup bandwidth in global pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second. Range is 1 to 4294967295.
unlimited	Unlimited bandwidth.

Defaults

Any class-type unlimited.

Command Modes

Interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to configure backup tunnel 1 for use only by LSPs that take their bandwidth from the global pool (class-type 0 tunnels). Backup tunnel 1 does not provide bandwidth protection.

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# backup-bw global-pool unlimited 

or

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 

RP/0/RP0/CPU0:router(config-if)# backup-bw unlimited class-type 0

In the following example, backup tunnel 2 is used by LSPs that take their bandwidth from the sub-pool (class-type 1 tunnels) only. Backup tunnel 2 provides bandwidth protection for up to 1000 units.

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 2 

RP/0/RP0/CPU0:router(config-if)# backup-bw sub-pool 1000 

or

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# interface tunnel-te 2 

RP/0/RP0/CPU0:router(config-if)# backup-bw 1000 class-type 1 

Related Commands

Commands	Description
backup-path tunnel-te	Assigns one or more backup tunnels to a protected interface.
fast-reroute	Enables fast-reroute (FRR) protection for an MPLS-TE 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

tunnel-number

Number of the tunnel protecting the interface. Range is 0 to 65535.

Defaults

No default behavior or values

Command Modes

MPLS-TE interface configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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:

•Multiple (backup) tunnels can protect the same interface by entering this command multiple times for different tunnels. The same (backup) tunnel can protect multiple interfaces by entering this command for each interface.

•The backup tunnel used to protect a physical interface must have a valid IP address configured.

•The backup tunnel cannot pass through the same interface that it is protecting.

•TE tunnels that are configured with the FRR option, cannot be used as backup tunnels.

•For the backup tunnel to provide protection to the protected LSP, the backup tunnel must have a terminating-end node in the path of a protected LSP.

•The source IP address of the backup tunnel and the merge point (MP) address (the terminating-end address of the backup tunnel) must be reachable.

---

Note You must configure record-route on TE tunnels that are protected by multiple backup tunnels merging at a single node.

---

Task ID

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to protect PoS interface 0/7/0/0 using tunnel 100 and tunnel 150:

RP/0/RP0/CPU0:router# configure

RP/0/RP0/CPU0:router(config)# mpls traffic-eng

RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0

RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel 100

RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel 150

Related Commands

Command	Description
backup-bw	Configures backup bandwidth for bandwidth protection.
fast-reroute	Enables fast-reroute (FRR) protection for an MPLS-TE tunnel.
show mpls traffic-eng tunnels	Displays information about MPLS-TE tunnels.

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	Modification
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.
Release 3.6.0	No modification.
Release 3.7.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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to clear all LMP management hello settings:

RP/0/RP0/CPU0:router# clear mpls lmp

clear mpls traffic-eng 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

all	Clears counters for all MPLS-TE tunnels.
heads | middles | tails	(Optional) •Displays tunnels with their heads at this router. •Displays tunnels with their midpoints at this router. •Displays tunnels with their tails at this router.
name name	Clears counters for an MPLS-TE tunnel with the specified name.
summary	Clears the counter's summary.

Command Modes

EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	Support was added for the middles keyword.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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

Task ID	Operations
mpls-te	read, write

Examples

The following example shows how to clear all counters:

RP/0/RP0/CPU0:router# clear mpls traffic-eng counters tunnels all

The following example shows how to clear counters for tunnel 1:

RP/0/RP0/CPU0:router# clear mpls traffic-eng counters tunnels name tunnel-te1

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

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was supported on the Cisco XR 12000 Series Router.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.
Release 3.7.0	No modification.

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.