Cisco IOS XR MPLS Command Reference for the Cisco CRS Router, Release 4.2.x
MPLS Traffic Engineering Commands
Downloads: This chapterpdf (PDF - 3.13MB) The complete bookPDF (PDF - 6.24MB) | Feedback

MPLS Traffic Engineering Commands

Contents

MPLS Traffic Engineering Commands

This module describes the commands used to configure Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) on the Cisco IOS XR Software.

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, see Cisco IOS XR MPLS Configuration Guide for the Cisco CRS-1 Router.

adjustment-threshold (MPLS-TE)

To configure the tunnel bandwidth change threshold to trigger an adjustment, use the adjustment-threshold command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.

adjustment-threshold percentage [ min minimum bandwidth ]

no adjustment-threshold percentage [ min minimum bandwidth ]

Syntax Description

percentage

Bandwidth change percent threshold to trigger an adjustment if the largest sample percentage is higher or lower than the current tunnel bandwidth. The range is from 1 to 100. The default is 5.

min minimum bandwidth

(Optional) Configures the bandwidth change value to trigger an adjustment. The tunnel bandwidth is changed only if the largest sample is higher or lower than the current tunnel bandwidth, in kbps. The range is from 10 to 4294967295. The default is 10.

Command Default

percentage: 5

minimum bandwidth: 10

Command Modes

MPLS-TE automatic bandwidth interface configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you configure or modify the adjustment threshold while the automatic bandwidth is already running, the next band-aids application is impacted for that tunnel. The new adjustment threshold determines if an actual bandwidth takes place.

Examples

The following example configures the tunnel bandwidth change threshold to trigger an adjustment:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# adjustment-threshold 20 min 500

Related Commands

Command

Description

application (MPLS-TE)

Configures the application frequency, in minutes, for the applicable tunnel.

auto-bw (MPLS-TE)

Configures automatic bandwidth on a tunnel interface and enters MPLS-TE automatic bandwidth interface configuration mode.

bw-limit (MPLS-TE)

Configures the minimum and maximum automatic bandwidth to set on a tunnel.

collect-bw-only (MPLS-TE)

Enables only the bandwidth collection without adjusting the automatic bandwidth.

overflow threshold (MPLS-TE)

Configures tunnel overflow detection.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

admin-weight

To override the Interior Gateway Protocol (IGP) administrative weight (cost) of the link, use the admin-weight command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.

admin-weight weight

no admin-weight weight

Syntax Description

weight

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

Command Default

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.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-selection metric (interface)

Specifies an MPLS-TE tunnel path-selection metric type.

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 disable this behavior, use the no form of this command.

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

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

Syntax Description

affinity-value

Attribute values that are required for links to carry this tunnel. A 32-bit decimal number. Range is from 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 name

Configures the affinity to include in the loose sense.

include-strict name

Configures the affinity to include in the strict sense.

Command Default

affinity-value: 0X00000000

mask-value: 0XFFFFFFFF

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.4.0

Support was added for the Name-Based Affinity Constraint scheme.

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 appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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. These constraints are used to configure affinity constraints for the tunnel:

Include constraint

Specifies that a link is considered for CSPF if it contains all 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 set 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

This 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

This example shows that a link is eligible for CSPF if the color is red.. 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
  

This 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
  

This 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:
  
  

This 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 other 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
  

This 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:
  
  

This 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
  

This 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
  

This 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
  

This 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-names

Configures attribute names for the interface.

interface tunnel-te

Configures an MPLS-TE tunnel 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 { affinity value | bit-position value }

no affinity-map affinity name { affinity value | bit-position value }

Syntax Description

affinity name

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

affinity value

Affinity map value designator. Range is from 1 to 80000000.

bit-position

Configures the value of an affinity map for the bit position of the 32-bit number.

value

Bit position value. Range is from 0 to 31.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Release 3.9.0

The following command syntax was enhanced:

  • The affinity value argument range was changed to 1 to 80000000.
  • The bit-position keyword and value argument were added.
  • Sample output was added to show how to configure the value for the bit position.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


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# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map red 1
RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map blue 2
  

The following example shows how to configure the value of 15 for an affinity map by bit position:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# affinity-map red2 bit-position 15
  

Related Commands

Command

Description

affinity

Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng affinity-map

Displays the color name-to-value mappings configured on the router.

application (MPLS-TE)

To configure the application frequency, in minutes, for the applicable tunnel, use the application command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.

application minutes

no application minutes

Syntax Description

minutes

Frequency, in minutes, for the automatic bandwidth application. The range is from 5 to 10080 (7 days). The default is 1440.

Command Default

minutes : 1440 (24 hours)

Command Modes

MPLS-TE automatic bandwidth interface configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you configure and modify the application frequency, the application period can reset and restart for that tunnel. The next bandwidth application for the tunnel happens within the specified minutes.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure application frequency to 1000 minutes for MPLS-TE interface 1:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# application 1000
  

Related Commands

Command

Description

adjustment-threshold (MPLS-TE)

Configures the tunnel-bandwidth change threshold to trigger an adjustment.

auto-bw (MPLS-TE)

Configures automatic bandwidth on a tunnel interface and enters MPLS-TE automatic bandwidth configuration mode.

bw-limit (MPLS-TE)

Configures the minimum and maximum automatic bandwidth to set on a tunnel.

collect-bw-only (MPLS-TE)

Enables only the bandwidth collection without adjusting the automatic bandwidth.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

overflow threshold (MPLS-TE)

Configures tunnel overflow detection.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

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.

Command Default

attributes : 0x0

Command Modes

MPLS-TE interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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:routerconfigure
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 the attribute names for the interface.

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

attribute-names

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

attribute-names attribute name

no attribute-names attribute name

Syntax Description

attribute name

Attribute name expressed using alphanumeric or hexidecimal characters.

Command Default

No default behavior or values

Command Modes

MPLS-TE interface configuration

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


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# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface pos 0/2/0/1
RP/0/RP0/CPU0:router(config-mpls-te-if)# attribute-name red
  

Related Commands

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.

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

attribute-set

To configure attribute-set for auto-backup tunnels, use the attribute-set command in MPLS-TE configuration mode.

attribute-set auto-backup attribute-set-name { affinity { affinity-value mask mask-value | exclude name | exclude-all | include name | include-strict name } | logging events lsp-status { reoptimize | state } | policy-class { range | default } | priority setup-range hold-range | record-route }

To configure attribute-set for auto-mesh tunnels, use the attribute-set command in MPLS-TE configuration mode.

attribute-set auto-mesh attribute-set-name { affinity { affinity-value mask mask-value | exclude name | exclude-all | include name | include-strict name } | auto-bw collect-bw-only | autoroute announce | bandwidth bandwidth | fast-reroute [ protect { bandwidth node | node bandwidth } ] | logging events lsp-status { insufficient-bandwidth | reoptimize | reroute | state } | policy-class { range | default } | priority setup-range hold-range | record-route | signalled-bandwidth bandwidth [ class-type cl ] | soft-preemption }

To configure attribute-set for a path-option, use the attribute-set command in MPLS-TE configuration mode.

attribute-set path-option attribute-set-name { affinity { affinity-value mask mask-value | exclude name | exclude-all | include name | include-strict name } | signalled-bandwidth bandwidth [ class-type cl ] }

To disable this behavior, use the no form of this command.

no attribute-set

Syntax Description

auto-backup

Specifies the values of an attribute set for the auto-backup group.

auto-mesh

Specifies the values of an attribute set for the auto-mesh group.

path-option

Specifies the values of an attribute set for the path option.

attribute-set-name

A 32-bit character string, specifies the name of the attribute-set template.

affinity-value

Attribute values that are required for links to carry this tunnel. A 32-bit decimal number, representing 32 attributes (bits), where the value of an attribute is 0 or 1. Range is from 0x0 to 0xFFFF.

mask mask-value

Checks the link attribute. A 32-bit decimal number, representing 32 attributes (bits), where the value of an attribute mask is 0 or 1. Range is from 0x0 to 0xFFFF.

exclude name

Configures a specific affinity that is to be excluded.

exclude-all

Excludes all affinities.

include name

Configures the affinity to include in the loose sense.

include-strict name

Configures the affinity to include in the strict sense.

logging

Per-interface logging configuration.

events

Per-interface logging events.

lsp-status

Enables interface LSP state change alarms.

reoptimize

Enables interface LSP REOPT change alarms.

state

Enables interface LSP UP/DOWN change alarms.

policy-class

Specifies class for policy-based tunnel selection.

range

Tunnel policy class range 1 to 7.

default

Default class for policy-based tunnel selection.

priority

Specifies the tunnel priority.

setup-range

Specifies setup priority. Range is 0 to 7.

hold-range

Specifies hold priority. Range is 0 to 7.

record-route

Records the route used by the tunnel.

signalled-bandwidth

Specifies the tunnel bandwidth requirement to be signalled.

bandwidth

Bandwidth required for an MPLS-TE tunnel, specified in kilobits per second. By default, bandwidth is reserved in the global pool. Range is from 0 to 4294967295.

class-type ct

(Optional) Configures the class type of the tunnel bandwidth request. Range is 0 to 1. Class-type 0 is equivalent to global-pool. Class-type 1 is equivalent to subpool.

soft-preemption

Enables the soft-preemption feature on this tunnel.

Command Default

affinity-value: 0x0

mask-value: 0xFFFF

Command Modes

MPLS TE configuration

Command History

Release Modification

Release 4.2.0

This command was introduced. The sub-pool keyword is not supported.

Release 4.2.1

Support for configuring attribute-set for auto-backup tunnels was added.

The policy-class keyword was added for auto-mesh attribute-set.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The values specified for an attribute within a path-option attribute-set does not prevent the configuration of the same attribute at the tunnel level. However, only one level is taken into consideration. The configuration at the path-option level is considered more specific than the one at the level of the tunnel, and is therefore used.

Attributes that are not specified within an attribute-set picks their default values, as usual, from the configuration at the tunnel level, the configuration at the global mpls level, or default values.

An XRO attribute-set can be specified as part of the path-option, if required. An empty XRO attribute set results in the GMPLS tunnel being signaled with no exclusions, and therefore no XRO.

Task ID

Task ID Operation

mpls-te

read, write

Examples

This example shows how to configure an attribute-set to a TE interface for an auto-backup tunnel:

RP/0/RP0/CPU0:router# config
RP/0/RP0/CPU0:router(config)#  mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface GigabitEthernet 0/1/0/3
RP/0/RP0/CPU0:router(config-mpls-te-if)# auto-tunnel backup
RP/0/RP0/CPU0:router(config-mpls-te-if-auto-backup)#  attribute-set ab
RP/0/RP0/CPU0:router(config-mpls-te-if-auto-backup)#

This example shows how to configure an attribute-set to a TE interface for an auto-mesh tunnel:

RP/0/RP0/CPU0:router# config
RP/0/RP0/CPU0:router(config)#  mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)#  auto-tunnel mesh
RP/0/RP0/CPU0:router(config-te-auto-mesh)#  group 1
RP/0/RP0/CPU0:router(config-te-mesh-group)#  attribute-set am1
RP/0/RP0/CPU0:router(config-te-mesh-group)#  destination-list dl1

This example shows how to configure the attribute-set for auto-backup tunnels:

RP/0/RP0/CPU0:router# config
RP/0/RP0/CPU0:router(config)#  mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)#  attribute-set auto-backup ab
RP/0/RP0/CPU0:router(config-te-attribute-set)# affinity 0x1 mask 0x1
RP/0/RP0/CPU0:router(config-te-attribute-set)# priority 3 3
RP/0/RP0/CPU0:router(config-te-attribute-set)# policy-class 6
RP/0/RP0/CPU0:router(config-te-attribute-set)# logging events lsp-status reoptimize
RP/0/RP0/CPU0:router(config-te-attribute-set)# logging events lsp-status state
RP/0/RP0/CPU0:router(config-te-attribute-set)# policy-class default
RP/0/RP0/CPU0:router(config-te-attribute-set)# record-route

This example shows how to configure the attribute-set for auto-mesh tunnels:

RP/0/RP0/CPU0:router# config
RP/0/RP0/CPU0:router(config)#  mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)#  attribute-set auto-mesh mesh1
RP/0/RP0/CPU0:router(config-te-attribute-set)# affinity include red blue
RP/0/RP0/CPU0:router(config-te-attribute-set)# affinity include-strict yellow green
RP/0/RP0/CPU0:router(config-te-attribute-set)# affinity exclude black
RP/0/RP0/CPU0:router(config-te-attribute-set)# affinity exclude-all
RP/0/RP0/CPU0:router(config-te-attribute-set)# policy-class default

This example shows how to configure the tunnel affinity and signalled-bandwidth for a path-option:

RP/0/RP0/CPU0:router# config
RP/0/RP0/CPU0:router(config)#  mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)#  attribute-set path-option myset
RP/0/RP0/CPU0:router(config-te-attribute-set)# affinity 0x3 mask 0x3
RP/0/RP0/CPU0:router(config-te-attribute-set)# signalled-bandwidth 2000

Related Commands

Command

Description

affinity-map

Assigns a numerical value to each affinity name.

attribute-names

Configures attribute names for the interface.

interface tunnel-te

Configures an MPLS-TE tunnel 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.

auto-bw (MPLS-TE)

To configure automatic bandwidth on a tunnel interface and to enter MPLS-TE automatic bandwidth interface configuration mode, use the auto-bw command in MPLS-TE interface configuration mode. To disable the automatic bandwidth on that tunnel, use the no form of this command.

auto-bw

no auto-bw

Syntax Description

This command has no arguments or keywords.

Command Default

By default, automatic bandwidth is not enabled.

Command Modes

MPLS-TE interface configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the auto-bw command to enter MPLS-TE automatic bandwidth interface configuration mode.

The auto-bw and load-share unequal commands should not be used together.

The load-share unequalcommand determines the load-share for a tunnel based on the bandwidth. However, the MPLS-TE automatic bandwidth feature changes the bandwidth around. If you are configuring both the load-share unequal command and the MPLS-TE automatic bandwidth feature, we recommend that you specify an explicit load-share value configuration under each MPLS-TE automatic bandwidth tunnel.

The following automatic bandwidth scenarios are described:

  • If you configure the automatic bandwidth on a tunnel, the automatic bandwidth is enabled on that tunnel. If no other configuration is specified, defaults for the various parameters are used, the operation stops.
  • The automatic operation (for example, output rate collection) starts as soon as the automatic bandwidth is enabled on one tunnel. If automatic bandwidth is disabled from all tunnels, the operation stops.
  • If the output rate collection is already active when the automatic bandwidth is configured on a tunnel, the statistics collection for that tunnel starts at the next collection configuration.

    Note


    Because the collection timer is already running, the first collection event for that tunnel happens in less than C minutes (for example, on an average of C/2 minutes).


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enter MPLS-TE automatic bandwidth interface configuration mode:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:routerinterface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)#
  

Related Commands

Command

Description

adjustment-threshold (MPLS-TE)

Configures the tunnel-bandwidth change threshold to trigger an adjustment.

application (MPLS-TE)

Configures the application frequency, in minutes, for the applicable tunnel.

bw-limit (MPLS-TE)

Configures the minimum and maximum automatic bandwidth to set on a tunnel.

collect-bw-only (MPLS-TE)

Enables only the bandwidth collection without adjusting the automatic bandwidth.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

overflow threshold (MPLS-TE)

Configures tunnel overflow detection.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

auto-bw collect frequency (MPLS-TE)

To configure the automatic bandwidth collection frequency, use the auto-bw collect frequency command in MPLS-TE configuration mode. To reset the automatic bandwidth frequency to its default value, use the no form of this command.

auto-bw collect frequency minutes

no auto-bw collect frequency minutes

Syntax Description

minutes

Interval between automatic bandwidth adjustments, in minutes. The range is from 1 to 10080. The default is 5.

Command Default

minutes: 5

In addition, the no form of this command resets to the default.

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The auto-bw collect frequency command configures the automatic bandwidth collection frequency for all the tunnels.

Modifying the global collection frequency does not restart the tunnel for the current application period. The application period continues with the modified collection frequency.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example configures a tunnel for an automatic bandwidth adjustment of 100 minutes:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng 
RP/0/RP0/CPU0:router(config-mpls-te)# auto-bw collect frequency 100
            

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

mpls traffic-eng auto-bw apply (MPLS-TE)

Configures the highest bandwidth available on a tunnel without waiting for the current application period to end.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

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.

Command Default

No default behavior or values

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Currently, the only way to forward traffic over a tunnel is to use the autoroute announce or static routes commands.

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 the autoroute announce command 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

Displays the absolute metric mode; you can enter a positive metric value.

relative

Displays the relative metric mode; you can enter a positive, negative, or zero value.

value

Metric that the IGP enhanced SPF calculation uses. Relative value range is –10 to 10. Absolute value is 1 to 2147483647.

Command Default

relative value : 0

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.9.0

The absolute value range is from 1 to 2147483647.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

show mpls traffic-eng autoroute

Displays the tunnels announced to the IGP, including interface, destination, and bandwidth.

auto-tunnel backup (MPLS-TE)

To automatically build next-hop (NHOP) and next-next-hop (NNHOP) backup tunnels, and to enter auto-tunnel backup configuration mode, use the auto-tunnel backup command in MPLS-TE configuration mode. To clear the NHOP and NNHOP backup tunnels, use the no form of this command.

auto-tunnel backup

no auto-tunnel backup

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The range of tunnel-ID is required to be mentioned for the auto-tunnel backup tunnels; otherwise, none of the tunnels are created.

The no form of this command deletes both NHOP and NNHOP backup tunnels that are configured using either the auto-tunnel backup command or the nhop-only command.

Task ID

Task ID Operation
mpls-te

read, write

Examples

The following example automatically builds NHOP and NNHOP backup tunnels:

RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# auto-tunnel backup

Related Commands

Command Description

clear mpls traffic-eng auto-tunnel backup unused

Clears the unused automatic backup tunnels.

mpls traffic-eng interface-path-id auto-tunnel backup

Configures the automatic backup tunnel for a specific interface.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

tunnel-id (auto-tunnel backup)

Configures range of tunnel interface numbers for automatic backup tunnels.

backup-bw

To configure the backup bandwidth for an MPLS-TE backup tunnel (that is used to protect a physical interface), use the backup-bw command in interface configuration mode. To return to the default behavior, use the no form of this command.

backup-bw { backup bandwidth { any-class-type | class-type ct } | global-pool { bandwidth | unlimited } | sub-pool { bandwidth | unlimited } | unlimited { any-class-type | class-type ct } }

no backup-bw { backup bandwidth { any-class-type | class-type ct } | global-pool { bandwidth | unlimited } | sub-pool { bandwidth | unlimited } | unlimited { any-class-type | class-type ct } }

Syntax Description

backup bandwidth

Backup bandwidth in any-pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second (kbps). Range is 1 to 4294967295.

any-class-type

Displays the backup bandwidth assigned to any class-type protected tunnels.

class-type ct

Displays the class type of the backup bandwidth. Range is 0 to 1.

global-pool bandwidth

(In Prestandard DS-TE with RDM) Displays the backup bandwidth in global pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second. Range is 1 to 4294967295.

unlimited

Displays the unlimited bandwidth.

sub-pool bandwidth

(In Prestandard DS-TE with RDM) Displays the backup bandwidth in sub-pool provided by an MPLS-TE backup tunnel. Bandwidth is specified in kilobits per second. Range bandwidth is 1 to 4294967295. Only label switched paths (LSPs) using bandwidth from the sub-pool can use the backup tunnel.

Command Default

Any class-type unlimited.

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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 FRR protection for an MPLS-TE tunnel.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

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.

Command Default

No default behavior or values

Command Modes

MPLS-TE interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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 rerouted, 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-te 100
RP/0/RP0/CPU0:router(config-mpls-te-if)# backup-path tunnel-te 150

Related Commands

Command

Description

backup-bw

Configures backup bandwidth for bandwidth protection.

fast-reroute

Enables FRR protection for an MPLS-TE tunnel.

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

bw-limit (MPLS-TE)

To configure the minimum and maximum automatic bandwidth to be set on a tunnel, use the bw-limit command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.

bw-limit min bandwidth { max bandwidth}

no bw-limit

Syntax Description

min bandwidth

Configures the minimum automatic bandwidth, in kbps, on a tunnel. The range is from 0 to 4294967295. The default is 0.

max bandwidth

Configures the maximum automatic bandwidth, in kbps, on a tunnel. The range is from 0 to 4294967295. The default is 4294967295.

Command Default

min: 0

max: 4294967295

Command Modes

MPLS-TE automatic bandwidth interface configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Both the min and max keywords must be configured.

The bw-limit command automatically sets the minimum bandwidth to the default value of 0, or the bw-limit command automatically sets the maximum to the default value of 4294967295 kbps.

If the value of the min keyword is greater than the max keyword, the bw-limit command is rejected. If you configure and modify the minimum or maximum bandwidth while the automatic bandwidth is already running, the next bandwidth application for that tunnel is impacted. For example, if the current tunnel requested bandwidth is 30 Mbps and the minimum bandwidth is modified to 50 Mbps, the next application sets the tunnel bandwidth to 50 Mbps.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure the minimum and maximum bandwidth for the tunnel:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# bw-limit min 30 max 80
  

Related Commands

Command

Description

adjustment-threshold (MPLS-TE)

Configures the tunnel-bandwidth change threshold to trigger an adjustment.

application (MPLS-TE)

Configures the application frequency, in minutes, for the applicable tunnel.

auto-bw (MPLS-TE)

Configures automatic bandwidth on a tunnel interface and enters MPLS-TE automatic bandwidth interface configuration mode.

collect-bw-only (MPLS-TE)

Enables only the bandwidth collection without adjusting the automatic bandwidth.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

overflow threshold (MPLS-TE)

Configures tunnel overflow detection.

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 lmpcommand 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

Release 3.8.0

This command was moved under Cisco support.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


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 auto-bw (MPLS-TE EXEC)

To clear automatic bandwidth sampled output rates and to restart the application period for the specified tunnel, use the clear mpls traffic-eng auto-bw command in EXEC mode.

clear mpls traffic-eng auto-bw { all | internal | tunnel-te tunnel-number }

Syntax Description

all

Clears the automatic bandwidth sampled output rates for all tunnels.

internal

Clears all the automatic bandwidth internal data structures.

tunnel-te tunnel-number

Clears the automatic bandwidth sampled output rates for a specific tunnel. The tunnel-number argument is the tunnel ID used to clear the sampled output rates.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If no tunnel is specified, the clear mpls traffic-eng auto-bw command clears all the automatic bandwidth enabled tunnels.

For each tunnel in which the automatic bandwidth adjustment is enabled, information is maintained about the sampled output rates and the time remaining until the next bandwidth adjustment. The application period is restarted and values such as the largest collected bandwidth get reset. The tunnel continues to use the current bandwidth until the next application.

Task ID

Task ID

Operations

mpls-te

execute

Examples

The following example displays the information for the automatic bandwidth for tunnel number 0 from the show mpls traffic-eng tunnels auto-bw brief command:

 
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels 0 auto-bw brief
  
  Tunnel    LSP  Last appl  Requested  Signalled    Highest    Application
            Name     ID   BW(kbps)   BW(kbps)   BW(kbps)   BW(kbps)      Time Left
  -------------- ------ ---------- ---------- ---------- ---------- --------------
    tunnel-te0     278      100         100        100          150      12m 38s
  

The following example shows how to clear the automatic bandwidth sampled output rates for tunnel number 0:

RP/0/RP0/CPU0:router# clear mpls traffic-eng auto-bw tunnel-te 0
  
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels 0 auto-bw brief
  
  Tunnel    LSP  Last appl  Requested  Signalled    Highest    Application
            Name     ID   BW(kbps)   BW(kbps)   BW(kbps)   BW(kbps)      Time Left
  -------------- ------ ---------- ---------- ---------- ---------- --------------
    tunnel-te0     278      100         100        100          0         24m 0s
  

Related Commands

Command

Description

clear mpls traffic-eng counters signaling

Clears the automatic bandwidth configuration in a tunnel.

show mpls traffic-eng tunnels auto-bw brief

Displays the list of automatic-bandwidth-enabled tunnels, and indicates if the current signaled bandwidth of the tunnel is identical to the bandwidth that is applied by the automatic bandwidth.

clear mpls traffic-eng auto-tunnel backup unused

To remove unused automatic backup tunnels, use the clear mpls traffic-eng auto-tunnel backup unused command in global configuration mode.

clear mpls traffic-eng auto-tunnel backup unused { all | tunnel-te tunnel-number }

Syntax Description

all

Clears all the unused automatic backup tunnels.

tunnel-te tunnel-number

Clears a specific unused automatic backup tunnel.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The unused auto-tunnel backup tunnel is the tunnel that is not assigned to protect any FRR tunnel.

The behavior of this command is the same as the expiration of the timers removal unused command in which, when the timeout value is reached, the automatic backup tunnel is removed.

Task ID

Task ID Operation
mpls-te

execute

Examples

The following example displays the information for the unused backup automatic tunnels from the show mpls traffic-eng tunnels unused command:

RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels unused

The following example shows how to clear the unused backup automatic tunnels:

RP/0/RP0/CPU0:router# clear mpls traffic-eng auto-tunnel backup unused all
RP/0/RP0/CPU0:router# show mpls traffic-eng tunnels unused

Related Commands

Command Description
show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

clear mpls traffic-eng auto-tunnel mesh

To clear all unused auto-tunnel mesh destinations, use the clear mpls traffic-eng auto-tunnel meshcommand in EXEC mode.

clear mpls traffic-eng auto-tunnel mesh unused { all | tunnel-te }

Syntax Description

all

Clears all applicable unused auto-tunnel destinations.

tunnel-te id

Clears an unused auto-tunnel destinations identified by a tunnel identifier.

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

Release 4.1.1

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

execute

Examples

This is sample output from the clear mpls traffic-eng auto-tunnel mesh command:

clear mpls traffic-eng auto-tunnel mesh

clear mpls traffic-eng counters auto-tunnel mesh

To clear all auto-tunnel mesh counters, use the clear mpls traffic-eng counters auto-tunnel mesh command in EXEC mode.

clear mpls traffic-eng counters auto-tunnel mesh

This command has no arguments or keywords.

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

Release 4.1.1

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

execute

Examples

This is sample output from the clear mpls traffic-eng counters auto-tunnel mesh command:

RP/0/RP0/CPU0:routerclear mpls traffic-eng counters auto-tunnel mesh

clear mpls traffic-eng counters auto-tunnel backup

To clear MPLS-TE automatic tunnel backup counters, use the clear mpls traffic-eng counters auto-tunnel backup command in EXEC mode.

clear mpls traffic-eng counters auto-tunnel backup

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID Operation
mpls-te

execute

Examples

The following example removes all counters for the automatic backup tunnels:

RP/0/RP0/CPU0:router# clear mpls traffic-eng counters auto-tunnel backup

Related Commands

Command

Description

show mpls traffic-eng counters auto-tunnel backup

Displays the MPLS-TE automatic tunnel backup counters.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

clear mpls traffic-eng counters global

To clear the internal MPLS-TE tunnel counters, use the clear mpls traffic-eng counters global command in EXEC mode.

clear mpls traffic-eng counters global

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

execute

Examples

The following example shows how to clear the internal MPLS-TE tunnel counters:

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

clear mpls traffic-eng counters signaling

To clear (set to zero) the MPLS tunnel signaling counters, use the clear mpls traffic-eng counters signaling command in EXEC mode.

clear mpls traffic-eng counters signaling { all | [ heads | mids | tails ] | name name | summary }

Syntax Description

all

Clears counters for all MPLS-TE tunnels.

heads

(Optional) Displays tunnels with their heads at this router.

mids

(Optional) Displays tunnels with their midpoints at this router.

tails

(Optional) Displays tunnels with their tails at this router.

name name

Clears counters for an MPLS-TE tunnel with the specified name.

summary

Clears the counter’s summary.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced as clear mpls traffic-eng counters tunnels.

Release 3.5.0

Support was added for the middles keyword.

Release 3.8.0

The clear mpls traffic-eng counters tunnels command was replaced by clear mpls traffic-eng counters signaling command.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the clear mpls traffic-eng counters signaling 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 signaling all
            

Related Commands

Command

Description

show mpls traffic-eng counters signaling

Displays tunnel signaling statistics.

clear mpls traffic-eng counters soft-preemption

To clear (set to zero) the counters for soft-preemption statistics, use the clear mpls traffic-eng counters soft-preemption command in EXEC mode.

clear mpls traffic-eng counters { all | soft-preemption }

Syntax Description

all

Clears counters for all MPLS-TE tunnels.

soft-preemption

Clears the statistics for soft preemption counters.

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

Release 4.2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

When all counters are cleared using the clear mpls traffic-eng counters all command, the counters for soft-preemption statistics are automatically cleared.

Task ID

Task ID

Operations

mpls-te

execute

Examples

This example shows how to clear all counters:

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

Related Commands

Command

Description

show mpls traffic-eng counters signaling

Displays tunnel signaling statistics.

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 Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows sample output before clearing the log of FRR events:

RP/0/RP0/CPU0:router# show mpls traffic-eng fast-reroute log
  
  Node     Protected LSPs  Rewrites When                   Switching Time
           Interface                                           (usec)
  -------- --------- ----- -------- ---------------------- --------------
  0/0/CPU0 PO0/1/0/1 1     1        Feb 27 19:12:29.064000      147
  0/1/CPU0 PO0/1/0/1 1     1        Feb 27 19:12:29.060093      165
  0/2/CPU0 PO0/1/0/1 1     1        Feb 27 19:12:29.063814      129
  0/3/CPU0 PO0/1/0/1 1     1        Feb 27 19:12:29.062861      128
  
RP/0/RP0/CPU0:router# clear mpls traffic-eng fast-reroute log
  

clear mpls traffic-eng link-management statistics

To clear all the MPLS-TE admission control statistics, use the clear mpls traffic-eng link-management statistics command in EXEC mode.

clear mpls traffic-eng link-management statistics

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to clear all the MPLS-TE statistics for admission control:

RP/0/RP0/CPU0:router# clear mpls traffic-eng link-management statistics
         

clear mpls traffic-eng pce

To clear the path computation element (PCE) statistics, use the clear mpls traffic-eng pce command in EXEC mode.

clear mpls traffic-eng pce [ peer ipv4 address ]

Syntax Description

peer

(Optional) Clears the statistics for one peer.

ipv4 address

(Optional) Configures the IPv4 address for PCE.

Command Default

Clears statistics for all the PCE peers.

Command Modes

EXEC

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

execute

Examples

The following example shows how to clear the statistics for the PCE:

RP/0/RP0/CPU0:router# clear mpls traffic-eng pce
            

Related Commands

Command

Description

show mpls traffic-eng pce peer

Displays the status of the PCE peer address and state.

collect-bw-only (MPLS-TE)

To configure only the bandwidth collection without adjusting the bandwidth automatically, use the collect-bw-only command in MPLS-TE automatic bandwidth interface configuration mode. To disable this feature, use the no form of this command.

collect-bw-only

no collect-bw-only

Syntax Description

This command has no arguments or keywords.

Command Default

Bandwidth collection is either enabled or disabled.

Command Modes

MPLS-TE automatic bandwidth interface configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you enable the collect-bw-only command while the automatic bandwidth is already running on a tunnel, the bandwidth application is disabled from that moment. Before you enable the actual bandwidth application, you can get the status of the automatic bandwidth behavior.

If you disable the collect-bw-only command on a tunnel from which the automatic bandwidth is already running, the actual bandwidth application takes place on the tunnel at the next application period.

It is also possible to manually activate a bandwidth application regardless of the collect bandwidth only flag that is being specified on a tunnel. To activate the bandwidth application, use the mpls traffic-eng auto-bw apply (MPLS-TE) command in EXEC mode.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enable only the bandwidth collection without adjusting the automatic bandwidth:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# collect-bw-only
  

Related Commands

Command

Description

adjustment-threshold (MPLS-TE)

Configures the tunnel-bandwidth change threshold to trigger an adjustment.

application (MPLS-TE)

Configures the application frequency, in minutes, for the applicable tunnel.

auto-bw (MPLS-TE)

Configures automatic bandwidth on a tunnel interface and enters MPLS-TE automatic bandwidth interface configuration mode.

bw-limit (MPLS-TE)

Configures the minimum and maximum automatic bandwidth to set on a tunnel.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

overflow threshold (MPLS-TE)

Configures tunnel overflow detection.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

destination (MPLS-TE)

To configure the destination address of a TE tunnel, use the destination command in interface configuration mode. To return to the default behavior, use the no form of this command.

destination ip-address

no destination ip-address

Syntax Description

ip-address

Destination address of the MPLS-TE router ID.

Command Default

No default behavior or values

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.9.0

The Point-to-Multipoint (P2MP) TE tunnel destination configuration was added.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The tunnel destination address must be a unique MPLS-TE router ID; it cannot be an MPLS-TE link address on a node.


Use the interface tunnel-mte command to configure destinations for the Point-to-Multipoint (P2MP) TE tunnel and to enter P2MP destination interface configuration mode. The maximum number of destinations, which are configured under P2MP tunnels, is 500.

For P2MP tunnels, the destination command acts as a configuration mode. The path-option command is under the destination for P2MP; whereas, it is under the tunnel-te interface configuration mode for P2P tunnels.

For Point-to-Point (P2P) tunnels, the destination command is used as a single-line command.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the destination address for tunnel-te1 to 10.10.10.10:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te1
RP/0/RP0/CPU0:router(config-if)# destination 10.10.10.10
            

The following example shows how to set the destination address for tunnel-mte 10 to 150.150.150.150:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-mte10
RP/0/RP0/CPU0:router(config-if)# destination 150.150.150.150
RP/0/RP0/CPU0:router(config-if-p2mp-dest)#

Related Commands

Command

Description

interface tunnel-mte

Configures an MPLS-TE P2MP tunnel interface.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

path-option (P2MP TE)

Configures the primary or fallback path setup option for an P2MP TE tunnel.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

direction (GMPLS)

To configure a bidirectional optical tunnel for GMPLS, use the direction command in interface tunnel-gte configuration mode. To return to the default behavior, use the no form of this command.

direction bidirectional

no direction bidirectional

Syntax Description

bidirectional

Enables bidirectional tunneling.

Command Default

Default is unidirectional.

Command Modes

Interface tunnel-gte configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Release 3.8.0

GMPLS interfaces were supported under the tunnel-gte interface type.

Release 3.9.0

This command was removed.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


There are two types of MPLS-TE tunnels:

  • Generic packet MPLS-TE tunnels
  • Optical MPLS-TE tunnel (GMPLS tunnel)

At the configuration level, you cannot tell the difference between a packet MPLS or a GMPLS-TE tunnel. The packet TE tunnels are unidirectional, whereas GMPLS tunnels are bidirectional; therefore, you can identify the optical GMPLS tunnel by identifying the bidirectional configuration.

The GMPLS-TE tunnel requires that you specify the endpoint and transit switching capability so that the path computation module can determine the links that the tunnel can traverse.

The transit switching capability describes the switching capability of the LSP region that the tunnel crosses. The endpoint switching capability describes the switching capability and encoding required for the tunnel interface associated with the two ends of the bidirectional tunnel (namely, active, and passive side).

Finally, for GMPLS functionality to work, you must configure the direction and switching commands.


Note


Bidirectional tunnel support is available on optical (GMPLS) tunnels only.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to change the tunnel direction from the default (unidirectional) to bidirectional:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 99
RP/0/RP0/CPU0:router(config-if)# direction bidirectional
  

Related Commands

Command

Description

flooding-igp (GMPLS)

Floods selected GMPLS Traffic Engineering links.

interface tunnel-gte

Configures an MPLS-TE tunnel interface for GMPLS interfaces.

lmp hello (GMPLS)

Configures LMP IPCC management hello settings.

match (GMPLS)

Configures or matches active and passive tunnels.

passive (GMPLS)

Configures passive GMPLS tunnels.

remote (GMPLS)

Configures remote TE links.

switching (GMPLS)

Configures TE-link switching attributes.

disable (explicit-path)

To prevent the path from being used by MPLS-TE tunnels while it is configured, use the disable command in explicit path configuration mode. To return to the default behavior, use the no form of this command.

disable

no disable

Syntax Description

This command has no arguments or keywords.

Command Default

Explicit path is enabled.

Command Modes

Explicit path configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to disable explicit path 200:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
RP/0/RP0/CPU0:router(config-expl-path)# disable
  

Related Commands

Command

Description

index exclude-address

Specifies the next IP address to exclude from the explicit path.

index next-address

Specifies path entries at a specific index.

show explicit-paths

Displays the configured IP explicit paths.

disable (P2MP TE)

To disable the given destination for the Point-to-Multipoint (P2MP) tunnel interface, use the disable command in P2MP destination interface configuration mode. To return to the default behavior, use the no form of this command.

disable

no disable

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

P2MP destination interface configuration

Command History

Release

Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If the disable command is not configured, the destination is enabled.

We recommend that you disable those destinations about which you have prior knowledge. This is because those destinations do not have valid MPLS-TE paths; therefore these destinations can be excluded from the P2MP tree computation.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to disable destination 140.140.140.140:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-mte 10
RP/0/RP0/CPU0:router(config-if)# destination 140.140.140.140
RP/0/RP0/CPU0:router(config-if-p2mp-dest)# disable
  

Related Commands

Command

Description

destination (MPLS-TE)

Configures the destination address of a TE tunnel.

interface tunnel-mte

Configures an MPLS-TE P2MP tunnel interface.

ds-te bc-model

To enable a specific bandwidth constraint model (Maximum Allocation Model or Russian Doll Model) on the entire label switched router (LSR), use the ds-te bc-model command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

ds-te bc-model mam

no ds-te bc-model mam

Syntax Description

mam

Enables the Maximum Allocation Model (MAM) bandwidth constraints model.

Command Default

RDM is the default bandwidth constraint model.

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.7.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You can configure both the MAM and RDM bandwidth values on a single interface before swapping to an alternate global MPLS-TE BC model.

If you configure bandwidth constraints without configuring the corresponding bandwidth constraint values, the router uses default bandwidth constraint values.

MAM is not supported in prestandard DS-TE mode. MAM and RDM are supported in IETF DS-TE mode; RDM is supported in prestandard DS-TE mode.


Note


Changing the bandwidth constraints model affects the entire router and may have a major impact on system performance as nonzero-bandwidth tunnels are torn down.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enable the MAM bandwidth constraints model:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# ds-te bc-model mam
  

Related Commands

Command

Description

ds-te mode

Configures standard DS-TE mode.

ds-te te-classes

Enters DS-TE te-class map configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng ds-te te-class

Displays the Diff-Serv TE-class map in use.

ds-te mode

To configure standard differentiated-service TE mode (DS-TE), use the ds-te mode command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

ds-te mode ietf

no ds-te mode ietf

Syntax Description

ietf

Enables IETF standard mode.

Command Default

Prestandard DS-TE is the default differentiated service mode.

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The following two DS-TE modes are supported:

  • Prestandard mode
    • The Cisco proprietary mechanism for IGPs and RSVP signalling are used and DS-TE does not interoperate with third-party vendor equipment.
  • IETF mode
    • Standard defined extensions are used for IGPs and RSVP signalling and DS-TE in this mode interoperates with third-party equipment.
    • IETF mode supports two bandwidth constraint models: the Russian Doll Model (RDM) and Maximum Allocation Model (MAM).
    • RDM is the default model.
    • Router advertises variable-length bandwidth constraints, max-reservable- bandwidth, and unreserved bandwidths in TE-classes.
    • tunnels must have valid class-type and priority configured as per TE-class map in use; otherwise, tunnels remain down.
    • TE-class map (a set of tunnel priority and class-type values) is enabled to interpret unreserved bandwidth values advertised in IGP; therefore, TE-class map must be identical on all nodes for TE tunnels to be successfully established
    For DS-TE to function properly, DS-TE modes must be configured identically on all MPLS-TE nodes. If you need to change the DS-TE mode, you must bring down all tunnel interfaces and after the change, you should flood the updated bandwidth values through the network.

    Note


    Changing the DS-TE mode affects the entire LSR and can have a major impact on system performance when tunnels are torn down.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enable IETF standard mode:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# ds-te mode ietf
  

Related Commands

Command

Description

ds-te bc-model

Enables a specific bandwidth constraint model (Maximum Allocation Model or Russian Doll Model) on the LSR.

ds-te te-classes

Configures MPLS DS-TE TE-class maps.

mpls traffic-eng

Enters MPLS-TE configuration mode.

mpls traffic-eng fast-reroute promote

Configures the router to assign new or more efficient backup MPLS-TE tunnels to protected MPLS-TE tunnels.

show mpls traffic-eng ds-te te-class

Displays the Diff-Serv TE-class map in use.

ds-te te-classes

To enter DS-TE te-class map configuration mode, use the ds-te te-classes command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

ds-te te-classes te-class te_class_index { class-type class_type_number { priority pri_number } | unused }

no ds-te te-classes te-class te_class_index { class-type class_type_number { priority pri_number } | unused }

Syntax Description

te-class

Configures the te-class map.

te_class_index

TE class-map index. Range is 0 to 7.

class-type

Configures the class type.

class_type_number

Class type value in the te-class map. Range is 0 to 1.

priority

Configures the TE tunnel priority.

pri_number

TE tunnel priority value. Range is 0 to 7.

unused

Marks the TE-class as unused.

Command Default

The following default te-class maps are used in IETF DS-TE mode:

te-class index

class-type

priority

0

0

7

1

1

7

2

UNUSED

3

UNUSED

4

0

0

5

1

0

6

UNUSED

7

UNUSED


Note


The default mapping has 4 TE-classes used with 2 class-types and, 4 TE-classes are unused. TE-class map is not used in prestandard DS-TE mode.


Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Release 3.8.0

The unused keyword was added.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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 to automatically detect or enforce this required consistency.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a TE-class 7 parameter:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# ds-te te-classes te-class 7 class-type 0 priority 4
  

Related Commands

Command

Description

ds-te bc-model

Enables a specific bandwidth constraint model (Maximum Allocation Model or Russian Doll Model) on the LSR.

ds-te mode

Configures standard DS-TE mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng ds-te te-class

Displays the Diff-Serv TE-class map in use.

exclude srlg (auto-tunnel backup)

To specify that automatic backup tunnels should avoid Shared Risk Link Groups (SRLGs) of protected interface, use the exclude srlg command in auto-tunnel backup configuration mode. To disable this feature, use the no form of this command.

exclude srlg [preferred]

no exclude srlg [preferred]

Syntax Description

preferred

(Optional) Causes the backup tunnel to avoid SRLGs of its protected interface(s); however, the backup tunnel is created if SRLGs are not avoided.

Command Default

Strict SRLG

Command Modes

Auto-tunnel backup configuration

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Strict SRLG configuration of this command means that the path computed for the backup tunnel that is automatically created, must not contain any links that are part of the excluded SRLG groups. If such a path cannot be found, the backup tunnel does not come up.

Configuration of the preferred option allows the automatic backup tunnel to come up even if a path that excludes SRLGs can not be found.

Task ID

Task ID Operation
mpls-te

read, write

Examples

In the following example, automatic backup tunnels must avoid SRLGs of the protected interface.

RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface pos 0/1/0/1
RP/0/RP0/CPU0:router(config-mpls-te-if)# auto-tunnel backup
RP/0/RP0/CPU0:router(config-mpls-te-if-auto-backup)#  exclude srlg preferred

Related Commands

Command

Description

auto-tunnel backup (MPLS-TE)

Builds automatic next-hop and next-next-hop tunnels, and enters auto-tunnel configuration mode.

explicit-path

To configure an explicit path for an MPLS-TE tunnel, use the explicit-path command in global configuration mode. To return to the default behavior, use the no form of this command.

explicit-path { identifier number | name pathname }

no explicit-path

Syntax Description

identifier number

Configures an explicit path using a number.

name pathname

Configures an explicit path using a pathname.

Command Default

No default behavior or values

Command Modes

Global configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure an explicit path for an MPLS-TE tunnel:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
  

Related Commands

Command

Description

disable (explicit-path)

Prevents a path from being used by MPLS-TE tunnels.

show explicit-paths

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.

Command Default

FRR is disabled.

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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 switchover before triggering FRR on standby RPs to synchronize with the active RP (verified using the show redundancy command). All TE tunnels must be in the recovered state and the database must be in the ready state for all ingress and egress line cards. To verify this information, use the show mpls traffic-eng tunnels and show mpls traffic-eng fast-reroute database commands.


Note


Wait approximately 60 seconds before triggering FRR after verifying the database state.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enable FRR on an MPLS-TE tunnel:

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

Related Commands

Command

Description

fast-reroute protect

Configures node and bandwidth protection for an MPLS-TE tunnel.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

show mpls traffic-eng forwarding

Displays the contents of the FRR database.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

fast-reroute protect

To enable node and bandwidth protection for an MPLS-TE tunnel, use the fast-reroute protect command in interface configuration mode. To return to the default behavior, use the no form of this command.

fast-reroute protect { bandwidth | node }

no fast-reroute protect

Syntax Description

bandwidth

Enables bandwidth protection request.

node

Enables node protection request.

Command Default

FRR is disabled.

Command Modes

Interface configuration

Command History

Release

Modification

Release 3.6.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enable bandwidth protection for a specified TE tunnel:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)#interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# fast-reroute protect bandwidth
  

Related Commands

Command

Description

fast-reroute

Enables FRR protection for an MPLS-TE tunnel.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

fast-reroute timers promotion

To configure how often the router considers switching a protected MPLS-TE tunnel to a new backup tunnel if additional backup-bandwidth or a better backup tunnel becomes available, use the fast-reroute timers promotion command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

fast-reroute timers promotion interval

no fast-reroute timers promotion

Syntax Description

interval

Interval, in seconds, between scans to determine if a label switched path (LSP) should use a new, better backup tunnel. Range is 0 to 604800. A value of 0 disables backup tunnel promotions.

Command Default

interval: 300

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to specify that LSPs are scanned every 600 seconds (10 minutes) to determine if they should be promoted to a better backup tunnel:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# fast-reroute timers promotion 600

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

mpls traffic-eng fast-reroute promote

Configures the router to use a new or more efficient backup MPLS-TE tunnel when a current tunnel is overloaded.

flooding-igp (GMPLS)

To flood the GMPLS Traffic Engineering link into a specific OSPF area and instance, use the flooding-igp command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.

flooding-igp ospf instance area area

no flooding-igp ospf instance area area

Syntax Description

ospf

Floods the interface into an OSPF instance

instance

Name of the OSPF instance into which the GMPLS link is to be flooded.

area area

Displays the area into which the GMPLS link is to be flooded (where TE is configured).

Command Default

No default behavior or values

Command Modes

MPLS-TE interface configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


A GMPLS link won't be flooded into any IGP topology unless this command is used.


Note


The flooding-igp command is valid for GMPLS-TE only.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to flood the optical GMPLS link on POS 0/1/0/0 into area 0 of OSPF instance “optical”:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface pos0/1/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding-igp ospf optical area 0
  

Related Commands

Command

Description

destination (MPLS-TE)

Configures bidirectional optical tunnels.

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

lmp hello (GMPLS)

Configures LMP IPCC management hello settings.

match (GMPLS)

Configures or matches active and passive tunnels.

mpls traffic-eng

Enters MPLS-TE configuration mode.

passive (GMPLS)

Configures passive GMPLS tunnels.

remote (GMPLS)

Configures remote TE links.

switching (GMPLS)

Configures TE-link switching attributes.

flooding thresholds

To set the reserved bandwidth thresholds for a link, use the flooding thresholds command in MPLS-TE interface configuration mode. To return to the default behavior, use the no form of this command.

flooding thresholds { down | up } percent [ percent1 | percent2 | percent3 | ... percent 15 ]

no flooding thresholds { down | up }

Syntax Description

down

Configures the threshold for decreased resource availability.

up

Configures the threshold for increased resource availability.

percent [ percent ]

Bandwidth threshold level. Range is 0 to 100 for all 16 levels.

Command Default

down: 100, 99, 98, 97, 96, 95, 90, 85 , 80, 75 , 60, 45, 30, 15

up: 5, 30, 45, 60, 75, 80, 85, 90, 95, 97 , 98, 99, 100

Command Modes

MPLS-TE interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You can configure up to 16 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

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the reserved bandwidth threshold for the link for decreased resource availability (down) and for increased resource availability (up) thresholds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/7/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding thresholds down 100 75 25
RP/0/RP0/CPU0:router(config-mpls-te-if)# flooding thresholds up 25 50 100
            

Related Commands

Command

Description

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

link-management timers periodic-flooding

Sets the length of the interval used for periodic flooding.

show mpls traffic-eng link-management advertisements

Displays local link information currently being flooded by MPLS-TE link management into the global TE topology.

show mpls traffic-eng link-management bandwidth-allocation

Displays current local link information.

forwarding-adjacency

To configure an MPLS-TE forwarding adjacency, use the forwarding-adjacency command in interface configuration mode. To return to the default behavior, use the no form of this command.

forwarding-adjacency [ holdtime time ]

no forwarding-adjacency [ holdtime time ]

Syntax Description

holdtime time

(Optional) Configures the holdtime value, in milliseconds, that is associated with each forwarding-adjacency LSP. The default is 0.

Command Default

holdtime time: 0

Command Modes

Interface configuration

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you do not specify a holdtime time value, a delay is introduced with the following results:

  • When forwarding-adjacency is configured on a tunnel that is up, TE notifies IGP without any additional delay.
  • When forwarding-adjacency is not configured on a tunnel, TE notifies IGP without any additional delay.
  • When forwarding-adjacency is configured on a tunnel that is down, TE does not notify IGP.
  • When a tunnel on which forwarding-adjacency has been configured comes up, TE holds the notification to IGP for the period of holdtime (assuming nonzero holdtime). When the holdtime elapses, TE notifies IGP if the tunnel is still up.

The paths that traffic is taking to the destination can be manipulated by adjusting the forwarding adjacency link metric. To do that, use the bandwidth command. The unit of possible bandwidth values is in kbps.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure forwarding adjacency with a holdtime value of 60 milliseconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 888
RP/0/RP0/CPU0:router(config-if)# forwarding-adjacency holdtime 60

Related Commands

Command

Description

bandwidth (RSVP)

Configures RSVP bandwidth on an interface using prestandard DS-TE mode.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

show mpls traffic-eng forwarding-adjacency

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 IP address}

no index index-id

Syntax Description

index-id

Index number at which the path entry is inserted or modified. Range is 1 to 65535.

ipv4 unicast IP address

Excludes the IPv4 unicast address.

Command Default

No default behavior or values

Command Modes

Explicit path configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.2

Support for the ipv4 unicast keyword was added.

Release 3.4.0

The index (explicit path) command was modified to create two separate commands: index exclude-address and index next-address.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You cannot include or exclude addresses from an IP explicit path unless explicitly configured using the exclude-address keyword.

Use the exclude-addresskeyword only after entering the explicit path configuration mode.

If you use the exclude-address keyword and specify the IP address of a link, the constraint-based routine does not consider that link when it sets up MPLS-TE paths. If the excluded address is a flooded MPLS-TE router ID, the constraint-based shortest path first (SPF) routine does not consider that entire node.


Note


The person who performs the configuration must know the IDs of the routers, as it may not be apparent if the value refers to the link or to the node.


MPLS-TE accepts IP explicit paths composed of all excluded addresses configured using the exclude-address keyword.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to exclude address 192.168.3.2 at index 3 of the explicit path 200:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
RP/0/RP0/CPU0:router(config-expl-path)# index 3 exclude-address ipv4 unicast 192.168.3.2
  

Related Commands

Command

Description

index next-address

Specifies path entries at a specific index.

show explicit-paths

Displays the configured IP explicit paths.

index exclude-srlg

To exclude an address to get SRLGs from a tunnel path entry at a specific index, use the index exclude-srlg command in explicit path configuration mode. To return to the default behavior, use the no form of this command.

index index-id exclude-srlg ipv4 unicast IP address

no index index-id

Syntax Description

index-id

Index number at which the path entry is inserted or modified. Range is 1 to 65535.

exclude-srlg

Specifies an IP address to get SRLG values from for exclusion.

ipv4 unicast IP address

Excludes the IPv4 unicast address.

Command Default

No default behavior or values

Command Modes

Explicit path configuration

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID Operation
mpls-te

read, write

Examples

The following example shows how to exclude the SRLG values from the IP address 192.168.3.2 at index 1 of the explicit path 100:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 100
RP/0/RP0/CPU0:router(config-expl-path)# index 1 exclude-srlg ipv4 unicast 192.168.3.2

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

no index index-id

Syntax Description

index-id

Index number at which the path entry is inserted or modified. Range is 1 to 65535.

ipv4 unicast IP-address

Includes the IPv4 unicast address (strict address).

loose ipv4 unicast IP-address

(Optional) Specifies the next unicast address in the path as a loose hop.

strict ipv4 unicast IP-address

(Optional) Specifies the next unicast address in the path as a strict hop.

Command Default

No default behavior or values

Command Modes

Explicit path configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.2

Support for the ipv4 unicast keyword was added.

Release 3.4.0

The index (explicit path) command was added to create two separate commands: index exclude-address and index next-address.

Support was added for loose and strict keywords for the index next-address command.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You cannot include addresses from an IP explicit path unless explicitly configured using the next-address keyword.

Use the next-address keyword only after entering the explicit path configuration mode.


Note


The person who performs the configuration must know the IDs of the routers, as it may not be apparent if the value refers to the link or to the node.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to insert the next-address 192.168.3.2 at index 3 of the explicit path 200:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# explicit-path identifier 200
RP/0/RP0/CPU0:router(config-expl-path)# index 3 next-address ipv4 unicast 192.168.3.2
  

Related Commands

Command

Description

index exclude-address

Specifies the next IP address to exclude from the explicit path.

show explicit-paths

Displays the configured IP explicit paths.

interface (MPLS-TE)

To enable MPLS-TE on an interface and to enter MPLS-TE interface configuration mode, use the interface command in global configuration mode. To return to the default behavior, use the no form of this command.

interface type interface-path-id

no interface type interface-path-id

Syntax Description

type

Interface type. For more information, use the question mark (?) online help function.

interface-path-id

Physical interface or virtual interface.

Note   

Use the show interfaces command to see a list of all possible interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

Command Default

No default behavior or values

Command Modes

Global configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You must enter MPLS-TE interface mode to configure specific interface parameters on physical interfaces.

Configuring MPLS-TE links or a tunnel TE interface begins the TE-control process on RP.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enter the MPLS-TE interface configuration mode:

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

The following example shows how to remove an interface from the MPLS-TE domain:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# no interface POS 0/7/0/1
  

interface (SRLG)

To enable Shared Risk Link Groups (SRLGs) on an interface and to enter SRLG interface configuration mode, use the interface command in SRLG configuration mode. To return to the previous configuration mode, use the no form of this command.

interface type interface-path-id

no interface type interface-path-id

Syntax Description

type

Interface type. For more information, use the question mark (?) online help function.

interface-path-id

Physical interface or virtual interface.

Note   

Use the show interfaces command to see a list of all possible interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

Command Default

No default behavior or values

Command Modes

SRLG configuration

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID Operation
mpls-te

read, write

Examples

The following example shows how to enter SRLG interface configuration mode:

RP/0/RP0/CPU0:router(config)# srlg
RP/0/RP0/CPU0:router(config-srlg)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-srlg-if)# value 10
RP/0/RP0/CPU0:router(config-srlg-if)#value 50

Related Commands

Command

Description

interface (MPLS-TE)

Enables MPLS-TE on an interface and enters MPLS-TE interface configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

interface tunnel-gte

To configure an MPLS-TE tunnel interface for GMPLS interfaces, use the interface tunnel-gte command in global configuration mode. To return to the default behavior, use the no form of this command.

interface tunnel-gte tunnel-id

no interface tunnel-gte tunnel-id

Syntax Description

tunnel-id

Tunnel number. Range is 0 to 65535.

Command Default

Tunnel interfaces are disabled.

Command Modes

Global configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced .

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and use the loopback interface address as the source address of the tunnel.

Configuring MPLS-TE links or a tunnel TE interface begins the TE-control process on RP.

The interface tunnel-gte command indicates that the tunnel interface is for an MPLS-TE tunnel and enables the various tunnel MPLS-TE GMPLS tunnel interface options.

Task ID

Task ID

Operations

interface

read, write

Examples

The following example shows how to configure tunnel-gte interface 1:

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

Related Commands

Command

Description

match (GMPLS)

Matches an active tunnel to a passive tunnel.

passive (GMPLS)

Configures passive GMPLS tunnels.

switching endpoint (GMPLS)

Specifies the switching capability and encoding types for all endpoint TE links used to signal the optical tunnel that is mandatory to set up the GMPLS LSP.

switching transit (GMPLS)

Specifies the switching capability and encoding types for all transit TE links used to signal the optical tunnel to configure an optical LSP.

interface tunnel-mte

To configure an MPLS-TE P2MP tunnel interface, use the interface tunnel-mte command in global configuration mode. To return to the default behavior, use the no form of this command.

interface tunnel-mte tunnel-id

no interface tunnel-mte tunnel-id

Syntax Description

tunnel-id

Tunnel number. Range is from 0 to 65535.

Command Default

Tunnel interfaces are disabled.

Command Modes

Global configuration

Command History

Release

Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Configuring MPLS-TE links or tunnel-te, tunnel-gte, or tunnel-mte interfaces begins the TE-control process on route processor (RP).

The interface tunnel-mte command indicates that the tunnel interface is for an MPLS-TE P2MP tunnel and enables these MPLS-TE P2MP configuration options.


Note


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


To use the P2MP tunnels, you must configure a Loopback address and use the ipv4 unnumbered command for the Loopback interface type.

Task ID

Task ID

Operations

interface

read, write

Examples

This example shows how to configure tunnel interface 1:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-mte 1
RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0
  

Related Commands

Command

Description

affinity

Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel.

backup-bw

Configures backup bandwidth for FRR.

fast-reroute

Enables FRR protection for an MPLS-TE tunnel.

path-selection metric (interface)

Configures a path selection metric—TE or IGP.

priority (MPLS-TE)

Configures setup and reservation priority for an MPLS-TE tunnel.

record-route

Configures record-route on an MPLS-TE tunnel.

signalled-bandwidth

Configures the bandwidth required for an MPLS-TE tunnel.

signalled-name

Configures the name of the tunnel required for an MPLS-TE tunnel.

interface tunnel-te

To configure an MPLS-TE tunnel interface, use the interface tunnel-te command in global configuration mode. To return to the default behavior, use the no form of this command.

interface tunnel-te tunnel-id

no interface tunnel-te tunnel-id

Syntax Description

tunnel-id

Tunnel number. Range is 0 to 65535.

Command Default

Tunnel interfaces are disabled.

Command Modes

Global configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.7.0

Policy-based tunnel selection example was added.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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 to 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.


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

interface

read, write

Examples

The following example shows how to configure tunnel interface 1:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0
  

The following example shows how to set the tunnel-class attribute to map the correct traffic class to the tunnel:

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

Related Commands

Command

Description

affinity

Configures affinity (the properties that the tunnel requires in its links) for an MPLS-TE tunnel.

autoroute metric

Instructs the IGP to use the tunnel in its enhanced SPF calculation, if the tunnel is in an up state.

backup-bw

Configures backup bandwidth for FRR.

fast-reroute

Enables FRR protection for an MPLS-TE tunnel.

path-option (MPLS-TE)

Configures a path option for an MPLS tunnel.

path-selection metric (interface)

Configures a path selection metric—TE or IGP.

policy-class

Configures PBTS to direct traffic into specific TE tunnels.

priority (MPLS-TE)

Configures setup and reservation priority for an MPLS-TE tunnel.

record-route

Configures record-route on an MPLS-TE tunnel.

ipcc interface (MPLS-TE)

To configure an interface-bound IP based control channel to a specific LMP neighbor with the option to specify a custom destination address that is useful for GigabitEthernet interfaces, use the ipcc interface command in MPLS-TE neighbor configuration mode. To disable this feature, use the no form of this command.

ipcc interface type interface-path-id [ dest ipv4 address ]

no ipcc interface type interface-path-id [ dest ipv4 address ]

Syntax Description

type

Interface type. For more information, use the question mark (?) online help function.

interface-path-id

Physical interface or virtual interface.

Note   

Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

dest

(Optional) Configures the remote endpoint address.

ipv4 address

(Optional) Configures the IPv4 address.

Command Default

No default behavior or values

Command Modes

MPLS-TE neighbor configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure the IPCC interface for Loopback0:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor OXC1
RP/0/RP0/CPU0:router(config-mpls-te-nbr-OXC1)# ipcc interface Loopback0
  

Related Commands

Command

Description

ipcc routed (MPLS-TE)

Configures an IPCC that is routable.

lmp neighbor (MPLS-TE)

Configures or updates an LMP neighbor and its associated parameters and enters MPLS-TE neighbor configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng lmp

Displays information about the LMP.

ipcc routed (MPLS-TE)

To configure a routed IP-based control channel for a specific LMP neighbor, use the ipcc routed command in MPLS-TE neighbor configuration mode. To return to the default behavior, use the no form of this command.

ipcc routed

no ipcc routed

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

MPLS-TE neighbor configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a routed IPCC for neighbor router1 in which the destination IP address is the node ID of the neighbor router1 on an interface determined dynamically by an IP routing protocol:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor router1
RP/0/RP0/CPU0:router(config-mpls-te-nbr-router1)# ipcc routed
  

Related Commands

Command

Description

ipcc interface (MPLS-TE)

Configures an IPCC.

lmp neighbor (MPLS-TE)

Configures or updates an LMP neighbor and its associated parameters and enters MPLS-TE neighbor configuration mode.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng lmp

Displays information about the LMP.

ipv4 unnumbered (MPLS)

To specify the MPLS-TE tunnel Internet Protocol Version 4 (IPv4) address, use the ipv4 unnumbered command in interface configuration mode. To return to the default behavior, use the no form of this command.

ipv4 unnumbered type interface-path-id

no ipv4 unnumbered type interface-path-id

Syntax Description

type

Interface type. For more information, use the question mark (?) online help function.

interface-path-id

Physical interface or virtual interface.

Note   

Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

Command Default

No IP address is set.

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Tunnel-te is not signaled until an IP address is configured on the tunnel interface; therefore, the tunnel state stays down without IP address configuration.

Loopback is commonly used as the interface type.

Task ID

Task ID

Operations

network

read, write

Examples

The following example shows how to configure the MPLS-TE tunnel to use the IPv4 address used on loopback interface 0:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# ipv4 unnumbered loopback0
  

link-management timers bandwidth-hold

To set the length of time that bandwidth is held for a Resource Reservation Protocol (RSVP) Path (setup) message to wait for the corresponding RSVP Resv message to return, use the link-management timers bandwidth-hold command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

link-management timers bandwidth-hold holdtime

no link-management timers bandwidth-hold holdtime

Syntax Description

holdtime

Number of seconds that bandwidth can be held. Range is 1 to 300. Default is 15.

Command Default

holdtime: 15

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The link-management timers bandwidth-hold command determines the time allowed for an RSVP message to return from a neighbor RSVP node.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the bandwidth to be held for 10 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng 
RP/0/RP0/CPU0:router(config-mpls-te)# link-management timers bandwidth-hold 10
  

Related Commands

Command

Description

link-management timers periodic-flooding

Sets the length of the interval used for periodic flooding.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng link-management bandwidth-allocation

Displays current local link information and bandwidth hold time.

link-management timers periodic-flooding

To set the length of the interval for periodic flooding, use the link-management timers periodic-flooding command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

link-management timers periodic-flooding interval

no link-management timers periodic-flooding

Syntax Description

interval

Length of the interval, in seconds, for periodic flooding. Range is 0 to 3600. A value of 0 turns off periodic flooding. The minimum value is 30.

Command Default

interval: 180

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The link-management timers periodic-flooding command advertises the link state information changes that do not trigger immediate action, such as a change to the allocated bandwidth that does not cross a threshold.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the interval length for periodic flooding to 120 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# link-management timers periodic-flooding 120
  

Related Commands

Command

Description

flooding thresholds

Sets the reserved bandwidth flooding thresholds for a link.

link-management timers bandwidth-hold

Sets the length of time that bandwidth is held for a RSVP Path (setup) message to wait for the corresponding RSVP Resv message to return.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng link-management summary

Displays the current periodic flooding interval.

link-management timers preemption-delay

To set the length of the interval for delaying LSP preemption, use the link-management timers preemption-delay command in MPLS-TE configuration mode. To disable this behavior, use the no form of this command.

link-management timers preemption-delay bundle-capacity sec

Syntax Description

bundle-capacity sec

Specifies the bundle-capacity preemption timer value in seconds.

Command Default

None

Command Modes

MPLS-TE configuration

Command History

Release Modification

Release 4.2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The value 0 as bundle-capacity value in the link-management timers preemption-delay command disables this timer. This means there is no delay before preemption sets in when the bundle capacity goes down.

Task ID

Task ID Operation

mpls-te

read, write

Examples

This example shows how to set the interval length for preemption-delay:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# link-management timers preemption-delay bundle-capacity 180
  

load-share

To determine load-sharing balancing parameters for a specified interface, use the load-share command in interface configuration mode. To return to the default behavior, use the no form of this command.

load-share value

no load-share

Syntax Description

value

Load-share value, equivalent to the bandwidth in kbps (that is, the same value in configuration). Range is 1 to 4294967295. Default is 0.

Command Default

The default load-share for tunnels with no explicit configuration is the configured signalled bandwidth.

value: 0 (if no value is assigned)

Command Modes

Interface configuration

Command History

Release

Modification

Release 3.5.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure load-sharing parameters on a specified interface:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 100
RP/0/RP0/CPU0:router(config-if)# load-share 100
            

Related Commands

Command

Description

load-share unequal

Enables unequal load-sharing.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

signalled-bandwidth

Configures the bandwidth required for an MPLS-TE tunnel.

load-share unequal

To configure unequal load-sharing for an MPLS-TE tunnel, use the load-share unequal command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

load-share unequal

no load-share unequal

Syntax Description

This command has no arguments or keywords.

Command Default

By default, unequal load-balancing is disabled and equal load-balancing occurs.

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.5.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The auto-bw and load-share unequal commands should not be used together.

The load-share unequal command determines the load-share for a tunnel based on the bandwidth. However, the MPLS-TE automatic bandwidth feature changes the bandwidth around. If you are configuring both the load-share unequal command and the MPLS-TE automatic bandwidth feature, we recommend that you specify an explicit load-share value configuration under each MPLS-TE automatic bandwidth tunnel.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enable unequal load-sharing:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# load-share unequal
            

Related Commands

Command

Description

load-share

Configures load-sharing balancing parameters for a specified interface.

mpls traffic-eng

Enters MPLS-TE configuration mode.

signalled-bandwidth

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 global MPLS-TE neighbor lmp configuration mode. To return to the default behavior, use the no form of this command.

lmp hello hello-send -interval hello-dead-interval

no lmp hello hello-send-interval hello-dead-interval

Syntax Description

hello-send-interval

Time, in milliseconds, between sending hello keep alive message. Range is 100 to 21845.

hello-dead-interval

Time, in milliseconds, to wait without receiving a hello from the neighbor before declaring the IPCC down again. Range is 100 to 21845.

Command Default

No default behavior or values

Command Modes

MPLS-TE neighbor lmp configuration mode

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You can disable hellos using the lmp static command.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure Link Management Protocol (LMP) IPCC management hello settings:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor lmp
RP/0/RP0/CPU0:router(config-mpls-te-nbr-lmp)# lmp hello 400 1200
            

Related Commands

Command

Description

destination (MPLS-TE)

Configures bidirectional optical tunnels.

lmp neighbor (MPLS-TE)

Configures or updates an LMP neighbor and its associated parameters and enters MPLS-TE neighbor configuration mode.

match (GMPLS)

Configures or matches active and passive tunnels.

mpls traffic-eng

Enters MPLS-TE configuration mode.

passive (GMPLS)

Configures passive GMPLS tunnels.

remote (GMPLS)

Configures remote TE links.

switching (GMPLS)

Configures TE-link switching attributes.

lmp neighbor (MPLS-TE)

To configure or update an LMP neighbor with its associated identifier and enter MPLS-TE neighbor configuration mode, use the lmp neighbor command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

lmp neighbor name

no lmp neighbor name

Syntax Description

name

Text string representing the name of the LMP neighbor.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enter MPLS-TE neighbor configuration mode for router1:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp neighbor router1
RP/0/RP0/CPU0:router(config-mpls-te-nbr-router1)# 
  

Related Commands

Command

Description

lmp hello (GMPLS)

Configures LMP management hello settings.

mpls traffic-eng

Enters MPLS-TE configuration mode.

show mpls traffic-eng lmp

Displays information about the LMP.

lmp router-id (MPLS-TE)

To configure the router ID for the optical instance using the LMP protocol, use the lmp router-id command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

lmp router-id { ipv4 address | type interface-path-id }

no lmp router-id { ipv4 address | type interface-path-id }

Syntax Description

ipv4 address

Router ID expressed as an IPv4 address.

type

Interface type. For more information, use the question mark (?) online help function.

interface-path-id

Physical interface or virtual interface.

Note   

Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how configure the LMP router ID for IPv4 address 172.24.20.164:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# lmp router-id router 127.0.0.1
  

Related Commands

Command

Description

clear mpls lmp

Clears LMP management hello settings.

mpls traffic-eng

Enters MPLS-TE configuration mode.

logging events link-status (MPLS-TE)

To enable the logging events so that the software sends a log message when a tunnel goes up or goes down, use the logging events link-status command in tunnel-mte interface configuration mode. To disable this feature, use the no form of this command.

logging events link-status

nologging events link-status

Syntax Description

This command has no arguments or keywords.

Command Default

By default, no logs are sent out.

Command Modes

Tunnel-mte interface configuration

Command History

Release Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The logging events link-statuscommand enables the configuration to be notified of tunnel state changes through log messages.

In addition, the logging events link-status command applies to both tunnel-mte and tunnel-te interfaces.

Task ID

Task ID Operation
interface

read, write

Examples

The following example shows how to enable logging events for the interface and line-protocol state change alarms:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-mte 10
RP/0/RP0/CPU0:router(config-if)# logging events link-status

Related Commands

Command

Description

interface tunnel-mte

Configures an MPLS-TE P2MP tunnel interface

logging events lsp-status (MPLS-TE)

Sends out a log message when LSP events occur.

logging events sub-lsp-status state (MPLS-TE)

Sends out a log message when a point-to-multipoint sub-lsp goes up or goes down when the software is enabled.

logging events lsp-status (MPLS-TE)

To send out a log message when LSP events occur, use the logging events lsp-status command in tunnel-mte interface configuration mode. To disable this feature, use the no form of this command.

logging events lsp-status { reoptimize | reroute | state | switchover }

nologging events lsp-status { reoptimize | reroute | state | switchover }

Syntax Description

reoptimize

Sends out the log message when the tunnel LSP is reoptimized when the software is enabled.

reroute

Sends out the log message when the tunnel LSP is rerouted due to an FRR event when the software is enabled.

Note   

Only FRR tunnels are applicable.

state

Sends out the log message when the tunnel LSP goes up or down when the software is enabled.

switchover

Sends out the log message when the tunnel LSP switches to the standby LSP due to a path protection event when the software is enabled.

Note   

Only applicable to path protected tunnels.

Command Default

By default, no logs are sent out.

Command Modes

Tunnel-mte interface configuration

Command History

Release Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The logging events lsp-status command can be configured to notify the various LSP status changes through log messages. One or several of these LSP status changes can be enabled at once.

In addition, the logging events lsp-status command applies to both tunnel-mte and tunnel-te interfaces.

Task ID

Task ID Operation
mpls-te

read, write

Examples

The following example shows how to enable the interface LSP state change alarms for reoptimization:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-mte 10
RP/0/RP0/CPU0:router(config-if)# logging events lsp-status reoptimize

Related Commands

Command

Description

interface tunnel-mte

Configures an MPLS-TE P2MP tunnel interface

logging events link-status (MPLS-TE)

Enables the logging events so that the software sends a log message when a tunnel goes up or goes down.

logging events sub-lsp-status state (MPLS-TE)

Sends out a log message when a point-to-multipoint sub-lsp goes up or goes down when the software is enabled.

logging events sub-lsp-status state (MPLS-TE)

To send out a log message when a point-to-multipoint sub-lsp goes up or goes down when the software is enabled, use the logging events sub-lsp-status state command in tunnel-mte interface configuration mode. To disable this feature, use the no form of this command.

logging events sub-lsp-status state

Syntax Description

This command has no arguments or keywords.

Command Default

By default, no logs are sent out.

Command Modes

Tunnel-mte interface configuration

Command History

Release Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The logging events sub-lsp-status state command can be configured to notify the state changes per-destination for the P2MP tunnel.

logging events sub-lsp-status state command applies only to the tunnel-mte interface.

Task ID

Task ID Operation
mpls-te

read, write

Examples

The following example shows how to enable the console logging for sub-lsp events to change the alarms state:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-mte 10
RP/0/RP0/CPU0:router(config-if)# logging events sub-lsp-status state

Related Commands

Command

Description

interface tunnel-mte

Configures an MPLS-TE P2MP tunnel interface.

logging events link-status (MPLS-TE)

Enables the logging events so that the software sends a log message when a tunnel goes up or goes down.

logging events lsp-status (MPLS-TE)

Sends out a log message when LSP events occur.

match (GMPLS)

To match an active tunnel to a passive tunnel, use the match command in interface tunnel-gte configuration mode. To return to the default behavior, use the no form of this command.

match identifier tunnel-number

no match identifier tunnel-number

Syntax Description

identifier

Configures the identifier of the active tunnel to match with this passive tunnel.

tunnel-number

Tunnel number. Range is 0 to 65535.

Command Default

No default behavior or values

Command Modes

Interface tunnel-gte configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Release 3.8.0

GMPLS interfaces were supported under the tunnel-gte interface type.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


GMPLS interfaces are used under the tunnel-gte interface type.

You must enter the hostname for the head router then underscore _t, and the tunnel number for the head router. If tunnel-gte1 is configured on the head router with a hostname of gmpls1, CLI is match identifier gmpls1_t1.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to match the active tunnel ID to the passive tunnel:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 1
RP/0/RP0/CPU0:router(config-if)# match identifier gmpls1_t1

Related Commands

Command

Description

destination (MPLS-TE)

Configures bidirectional optical tunnels.

interface tunnel-gte

Configures an MPLS-TE tunnel interface for GMPLS interfaces.

lmp hello (GMPLS)

Configures LMP IPCC management hello settings.

passive (GMPLS)

Configures passive GMPLS tunnels.

remote (GMPLS)

Configures remote TE links.

switching (GMPLS)

Configures TE-link switching attributes.

maxabs (MPLS-TE)

To specify the maximum number of MPLS-TE tunnels that can be configured, use the maxabs command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

maxabs tunnels tunnel-limit destinations dest-limit

no maxabs tunnels tunnel-limit destinations dest-limit

Syntax Description

tunnels

Configures all tunnels for MPLS-TE.

tunnel-limit

Maximum number of tunnel TE interfaces. Range is 1 to 65536.

destinations

Configures all destinations for MPLS-TE.

dest-limit

Maximum total number of destinations that can be configured. Range is 1 to 65536.

Command Default

tunnel-limit: 4096

dest-limit: 4096

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Release 3.9.0

This command was removed.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the tunnel-te configuration limit to 1000:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# maxabs tunnels 1000 destinations 1000
  

Related Commands

Command

Description

show mpls traffic-eng maximum tunnels

Displays the configuration of the maximum tunnel-te interfaces allowed.

mpls traffic-eng

To enter MPLS-TE configuration mode, use the mpls traffic-eng command in global configuration mode.

mpls traffic-eng

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

Global configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to enter MPLS-TE configuration mode:

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

mpls traffic-eng auto-bw apply (MPLS-TE)

To apply the highest bandwidth collected on a tunnel without waiting for the current application period to end, use the mpls traffic-eng auto-bw apply command in EXEC mode.

mpls traffic-eng auto-bw apply { all | tunnel-te tunnel-number }

Syntax Description

all

Applies the highest bandwidth collected instantly on all the automatic bandwidth-enabled tunnels.

tunnel-te tunnel-number

Applies the highest bandwidth instantly to the specified tunnel. The range is from 0 to 65535.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The mpls traffic-eng auto-bw apply command can forcefully expire the current application period on a specified tunnel and immediately apply the highest bandwidth recorded so far instead of waiting for the application period to end on its own.


Note


The predefined threshold check still applies on the configuration, and if the delta is not significant enough, the automatic bandwidth functionality overrides this command.


The bandwidth application is performed only if at least one output rate sample has been collected for the current application period.

To guarantee the application of a specific signaled bandwidth value when triggering a manual bandwidth application, follow these steps:

  1. Configure the minimum and maximum automatic bandwidth to the bandwidth value that you want to apply by using the bw-limit (MPLS-TE) command.
  2. Trigger a manual bandwidth application by using the mpls traffic-eng auto-bw apply command.
  3. Revert the minimum and maximum automatic bandwidth value back to their original value.

Task ID

Task ID

Operations

mpls-te

execute

Examples

The following example applies the highest bandwidth to a specified tunnel:

RP/0/RP0/CPU0:router# mpls traffic-eng auto-bw apply tunnel-te 1
  

Related Commands

Command

Description

auto-bw collect frequency (MPLS-TE)

Configures the automatic bandwidth collection frequency and controls the manner in which the bandwidth for a tunnel collects output rate information, but does not adjust the tunnel bandwidth.

show mpls traffic-eng tunnels auto-bw brief

Displays the list of automatic-bandwidth-enabled tunnels, and indicates if the current signaled bandwidth of the tunnel is identical to the bandwidth that is applied by the automatic bandwidth.

mpls traffic-eng fast-reroute promote

To configure the router to assign new or more efficient backup MPLS-TE tunnels to protected MPLS-TE tunnels, use the mpls traffic-eng fast-reroute promote command in EXEC mode. To return to the default behavior, use the no form of this command.

mpls traffic-eng fast-reroute promote

no mpls traffic-eng fast-reroute promote

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to initiate backup tunnel promote and assignment:

RP/0/RP0/CPU0:router# mpls traffic-eng fast-reroute promote
  

Related Commands

Command

Description

fast-reroute

Enables FRR protection for an MPLS-TE tunnel.

mpls traffic-eng level

To configure a router running Intermediate System-to-System (IS-IS) MPLS-TE at IS-IS Level 1 and Level 2, use the mpls traffic-eng level command in router configuration mode. To return to the default behavior, use the no form of this command.

mpls traffic-eng level isis-level

no mpls traffic-eng level isis-level

Syntax Description

isis-level

IS-IS level (1, 2, or both) where MPLS-TE is enabled.

Command Default

No default behavior or values

Command Modes

Router configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.4.0

Support was added to enable MPLS Traffic Engineering in both IS-IS Level 1 and Level 2.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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

Task ID

Operations

isis

read, write

Examples

The following example shows how to configure a router running IS-IS MPLS to flood TE for IS-IS level 1:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router isis 1
RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicast
RP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng level 1
RP/0/RP0/CPU0:router(config-isis-af)# metric-style wide
  

Related Commands

Command

Description

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

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 enable immediate flooding of all the local MPLS-TE links, use the mpls traffic-eng link-management flood command in EXEC mode. To return to the default behavior, use the no form of this command.

mpls traffic-eng link-management flood

no mpls traffic-eng link-management flood

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


If there is no change in the LSA since last flooding, IGP may dampen the advertisement.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to initiate flooding of the local MPLS-TE links:

RP/0/RP0/CPU0:router# mpls traffic-eng link-management flood

Related Commands

Command

Description

show mpls traffic-eng link-management advertisements

Displays MPLS-TE link-management advertisements.

mpls traffic-eng path-protection switchover gmpls

To trigger a manual switchover for path protection for a GMPLS optical LSP, use the mpls traffic-eng path-protection switchover gmpls command in EXEC mode. To disable this feature, use the no form of this command.

mpls traffic-eng path-protection switchover gmpls tunnel name

no mpls traffic-eng path-protection switchover gmpls tunnel name

Syntax Description

tunnel name

Name of the tunnel that is used for a switchover.

Command Default

No manual path protection is invoked on either the head or tail router.

Command Modes

EXEC

Command History

Release

Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The mpls traffic-eng path-protection switchover gmpls command is used for the following functions:

  • Runs on both tunnel head and tunnel tail at the same time.
  • Configures both head and tail router of the GMPLS LSP to achieve the complete path switchover at both ends.

Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


Task ID

Task ID

Operations

mpls-te

execute

Examples

The following example triggers the switchover for path-protection for GMPLS:

RP/0/RP0/CPU0:router# mpls traffic-eng path-protection switchover gmpls

Related Commands

Command

Description

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

mpls traffic-eng pce activate-pcep

To force idle peers to be reestablished without waiting for a timer, use the mpls traffic-eng pce activate-pcep command in EXEC mode. To return to the default behavior, use the no form of this command.

mpls traffic-eng pce activate-pcep { address | all }

no mpls traffic-eng pce activate-pcep { address | all }

Syntax Description

address

Address of the idle peer.

all

Activates all the idle peers.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.5.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write, execute

Examples

The following example shows how to trigger a path computation client (PCC) or PCE to activate an idle path computation element protocol (PCEP) session:

RP/0/RP0/CPU0:router# mpls traffic-eng pce activate-pcep all
  

Related Commands

Command

Description

mpls traffic-eng pce reoptimize

Triggers reoptimization manually either for all tunnels or a specific PCE-based tunnel.

mpls traffic-eng pce reoptimize

To trigger reoptimization manually either for all or a specific PCE-based tunnel, use the mpls traffic-eng pce reoptimize command in EXEC mode. To disable this feature, use the no form of this command.

mpls traffic-eng pce reoptimize [tunnel ID] [force]

no mpls traffic-eng pce reoptimize [tunnel ID] [force]

Syntax Description

tunnel ID

(Optional) Tunnel ID to be reoptimized. Range is from 0 to 65535.

force

(Optional) Forces the router to start using the newly calculated route even if the used path has a better metric.

Command Default

Reoptimizes all the PCE tunnels.

Command Modes

EXEC

Command History

Release

Modification

Release 3.5.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you do not run the mpls traffic-eng pce reoptimize command, the system tries to reoptimize at an interval of 3600 seconds.

Task ID

Task ID

Operations

mpls-te

read, write, execute

Examples

The following example shows how to trigger reoptimization for all PCE-based tunnels:

RP/0/RP0/CPU0:router# mpls traffic-eng pce reoptimize
  

Related Commands

Command

Description

mpls traffic-eng pce activate-pcep

Forces idle peers to be re-established without waiting for a timer.

mpls traffic-eng reoptimize (EXEC)

To trigger the reoptimization interval of all TE tunnels, use the mpls traffic-eng reoptimize command in EXEC mode.

mpls traffic-eng reoptimize [tunnel-id] [tunnel-name] [all] [ p2mp { all | tunnel-id } ] [ p2p { all | tunnel-id } ]

Syntax Description

tunnel-id

(Optional) MPLS-TE tunnel identification expressed as a number. Range is from 0 to 65535.

tunnel-name

(Optional) TE tunnel identification expressed as a name.

all

(Optional) Forces an immediate reoptimization for all P2MP tunnels.

p2mp

(Optional) Forces an immediate reoptimization of all P2MP TE tunnels.

tunnel-id

P2MP TE tunnel identification to be reoptimized. Range is from 0 to 65535.

p2p

(Optional) Forces an immediate reoptimization of all P2P TE tunnels.

all

(Optional) Forces an immediate reoptimization for all P2P tunnels.

tunnel-id

P2P TE tunnel identification to be reoptimized. Range is from 0 to 65535.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.9.0

The following keywords and arguments were added to support the P2MP TE feature and P2P feature:

  • all keyword
  • p2mp keyword, all keyword, and tunnel-id argument
  • p2p keyword, all keyword, and tunnel-id argument

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

execute

Examples

The following example shows how to immediately reoptimize all TE tunnels:

RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize
  

The following example shows how to immediately reoptimize TE tunnel-te90:

RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize tunnel-te90
            

The following example shows how to immediately reoptimize all P2MP TE tunnels that originated from this TE LSR:

RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize p2mp all

The following example shows how to immediately reoptimize all P2P TE tunnels:

RP/0/RP0/CPU0:router# mpls traffic-eng reoptimize p2p all
  

Related Commands

Command

Description

reoptimize (MPLS-TE)

Forces immediate re-optimization of all TE tunnels.

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

To specify that the TE router identifier for the node is the IP address associated with a given interface, use the mpls traffic-eng router-id command in the appropriate mode. To return to the default behavior, use the no form of this command.

mpls traffic-eng router-id type interface-path-id

no mpls traffic-eng router-id type interface-path-id

Syntax Description

type

Interface type. For more information, use the question mark (?) online help function.

interface-path-id

Physical interface or virtual interface.

Note   

Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

Command Default

No default behavior or values

Command Modes

OSPF configuration

IS-IS address family configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.9.1

The Usage Guidelines was updated

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

A routers identifier acts as a stable IP address for the TE configuration. This IP address is flooded to all nodes. You must set the destination on the destination node TE router identifier for all affected tunnels. This router ID is the address that the TE topology database at the tunnel head uses for its path calculation.


Note


When the mpls traffic-eng router-id command is not configured, global router ID is used by MPLS-TE if there is one configured.


We suggest that you configure the mpls traffic-eng router-id command explicitly under the IGP; otherwise, TE uses the default algorithm to pick up the TE router-id, which can be the highest IP address of the loopback interfaces or physical interfaces. When TE uses the algorithm to select a TE router-id dynamically, it can be different from what is configured for the static RPF check on the P2MP tunnel tail . If the static RPF check mismatch happens, the P2MP tail does not pass the incoming P2MP traffic to the egress of P2MP tail router.

A TE router-id configuration is highly recommended to ensure that the tunnel head-end picks up the correct source address, and the configured static RPF address at the tail-end matches the tunnel source which avoids unexpected traffic drops.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following examples show how to specify the TE router identifier as the IP address associated with loopback interface:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf CORE_AS 
RP/0/RP0/CPU0:router(config-ospf)# mpls traffic-eng router-id 7.7.7.7
  
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router isis 811
RP/0/RP0/CPU0:router(config-isis)# address-family ipv4 unicast
RP/0/RP0/CPU0:router(config-isis-af)# mpls traffic-eng router-id 8.8.8.8
  

Related Commands

Command

Description

mpls traffic-eng level

Configures a router running OSPF MPLS so that it floods TE for the indicated IS-IS level.

mpls traffic-eng repotimize mesh group

To reoptimize all tunnels of a mesh group, use the mpls traffic-eng repotimize mesh groupcommand in EXEC mode.

mpls traffic-eng reoptimize auto-tunnel mesh group group_id

Syntax Description

group_id

Defines auto-tunnel mesh group ID that is to be reoptimized. Range is 0 to 4294967295.

Command Default

None

Command Modes

MPLS Transport profile configuration

Command History

Release

Modification

Release 4.1.1

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

execute

Examples

This is sample out from the mpls traffic-eng reoptimize mesh group command:

RP/0/RP0/CPU0:router mpls traffic-eng reoptimize mesh group 10

nhop-only (auto-tunnel backup)

To configure only a next-hop automatic backup tunnel with only link protection, use the nhop-only command in MPLS-TE auto-tunnel backup interface configuration mode. To return to the default configuration setting for automatic backup tunnels, use the no form of this command.

nhop-only

no nhop-only

Syntax Description

This command has no arguments or keywords.

Command Default

Both NHOP and NNHOP protection are enabled.

Command Modes

Auto-tunnel backup configuration

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you configure the nhop-only command, you destroy any next-next-hop (NNHOP) tunnel created to provide node protection for tunnels running over the specified interface.

If you unconfigure the nhop-only command, you trigger a backup assignment on primary tunnels running over that link. The automatic backup tunnel feature attempts to create NNHOP backup tunnnels to provide node protection for the specified tunnels.

Task ID

Task ID Operation
mpls-te

read, write

Examples

In the following example, NNHOP automatic backup tunnels are destroyed and only NHOP tunnels with link protection is configured:

RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface pos 0/1/0/1
RP/0/RP0/CPU0:router(config-mpls-te-if)# auto-tunnel backup
RP/0/RP0/CPU0:router(config-mpls-te-if-auto-backup)# nhop-only 

Related Commands

Command

Description

auto-tunnel backup (MPLS-TE)

Builds automatic NHOP and NNHOP backup tunnels.

overflow threshold (MPLS-TE)

To configure the tunnel overflow detection, use the overflow threshold command in MPLS-TE automatic bandwidth interface configuration mode. To disable the overflow detection feature, use the no form of this command.

overflow threshold percentage [ min bandwidth ] limit limit

no overflow threshold

Syntax Description

percentage

Bandwidth change percent to trigger an overflow. The range is from 1 to 100.

min bandwidth

(Optional) Configures the bandwidth change value, in kbps, to trigger an overflow.

The range is from 10 to 4294967295. The default is 10.

limit limit

Configures the number of consecutive collection intervals that exceeds the threshold. The bandwidth overflow triggers an early tunnel bandwidth update.

The range is from 1 to 10. The default is none.

Command Default

The default value is disabled.

Command Modes

MPLS-TE automatic bandwidth interface configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Release 3.9.0

The Usage Guidelines was updated to describe overflow detection.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

If you modify the limit keyword, the consecutive overflows counter for the tunnel is also reset.

If you enable or modify the minimum value, the current consecutive overflows counter for the tunnel is also reset, which effectively restarts the overflow detection from scratch.

Several number of consecutive bandwidth samples are greater than the overflow threshold (bandwidth percentage) and the minimum bandwidth configured, then a bandwidth application is updated immediately instead of waiting for the end of the application period.

Overflow detection applies only to bandwidth increase. For example, an overflow can not be triggered even if bandwidth decreases by more than the configured overflow threshold.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure the tunnel overflow detection for tunnel-te 1:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# auto-bw
RP/0/RP0/CPU0:router(config-if-tunte-autobw)# overflow threshold 50 limit 3
  

Related Commands

Command

Description

adjustment-threshold (MPLS-TE)

Configures the tunnel bandwidth change threshold to trigger an adjustment.

application (MPLS-TE)

Configures the application frequency in minutes for the applicable tunnel.

auto-bw (MPLS-TE)

Configures automatic bandwidth on a tunnel interface and enters MPLS-TE automatic bandwidth interface configuration mode.

bw-limit (MPLS-TE)

Configures the minimum and maximum automatic bandwidth to set on a tunnel.

collect-bw-only (MPLS-TE)

Enables only the bandwidth collection without adjusting the automatic bandwidth.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

passive (GMPLS)

To configure a passive GMPLS tunnel, use the passive command in interface tunnel-gte configuration mode. To return to the default behavior, use the no form of this command.

passive

no passive

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

Interface tunnel-gte configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Release 3.8.0

GMPLS interfaces were supported under the tunnel-gte interface type.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

GMPLS interfaces are used under the tunnel-gte interface type.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a passive GMPLS virtual interface tunnel:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-gte 99
RP/0/RP0/CPU0:router(config-if)# passive
  

Related Commands

Command

Description

destination (MPLS-TE)

Configures bidirectional optical tunnels.

interface tunnel-gte

Configures an MPLS-TE tunnel interface for GMPLS interfaces.

lmp hello (GMPLS)

Configures LMP IPCC management hello settings.

match (GMPLS)

Configures or matches active and passive tunnels.

remote (GMPLS)

Configures remote TE links.

switching (GMPLS)

Configures TE-link switching attributes.

path-option (MPLS-TE)

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 preference-priority [ protecting number ] { dynamic [ pce [ address ipv4 address ] ] | explicit { name path-name | identifier path-number } [ protected-by path-option-level ] } [attribute-set name] [ isis instance-name level level ] [lockdown] [ ospf instance-name area { value | address } ] [verbatim]

no path-option preference-priority { dynamic [ pce [ address ipv4 address ] ] | explicit { name path-name | identifier path-number } [ protected-by path-option-level ] } [ isis instance-name level level ] [lockdown] [ ospf instance-name area { value | address } ] [verbatim]

Syntax Description

preference-priority

Path option number. Range is from 1 to 1000.

protecting number

Specifies a path setup option to protect a path. The range is from 1 to 1000.

dynamic

Specifies that label switched paths (LSP) are dynamically calculated.

pce

(Optional) Specifies that the LSP is computed by a Path Computation Element (PCE).

address

(Optional) Configures the address for the PCE.

ipv4 address

Configures the IPv4 address for the PCE.

explicit

Specifies that LSP paths are IP explicit paths.

name path-name

Specifies the path name of the IP explicit path.

identifier path-number

Specifies a path number of the IP explicit path.

protected-by path-option-level

(Optional) Configures path protection for an explicit path that is protected by another explicit path.

isis instance-name

(Optional) Limits CSPF to a single IS-IS instance and area.

attribute-set name

(Optional) Specifies the attribute set for the LSP.

level level

Configures the level for IS-IS. The range is from 1 to 2.

lockdown

(Optional) Specifies that the LSP cannot be reoptimized.

ospf instance-name

(Optional) Limits CSPF to a single OSPF instance and area.

area

Configures the area for OSPF.

value

Decimal value for the OSPF area ID.

address

IP address for the OSPF area ID.

verbatim

(Optional) Bypasses the Topology/CSPF check for explicit paths.

Command Default

No default behavior or values

Command Modes

Tunnel-te interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.3.2

The protecting keyword was added to support GMPLS protection and restoration.

Release 3.4.1

Both the verbatim and lockdown keywords can be used together.

Release 3.7.0

An IGP-area was specified with the path-option command. Both the isis and the ospf keywords were added.

Release 3.8.0

The pce, address, and ipv4 keywords were added. The address argument was added.

Release 4.2.0

The attribute-set keyword was added.

Release 4.2.3

The protected-by keyword was added.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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. The protecting keyword is available only for tunnel-gte interfaces.

You specify the backup path for the path-option command in case of the primary path failure.

CSPF areas are configured on a per-path-option basis.

Any primary explicit path on a path protection enabled tunnel can be configured to be protected by an explicit path option level using protected-by keyword. Only one explicit protecting path is supported per path option.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure the tunnel to use a named IPv4 explicit path as verbatim and lockdown options for the tunnel. This tunnel cannot reoptimize when the FRR event goes away, unless you manually reoptimize it:

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name test verbatim lockdown

The following example shows how to enable path protection on a tunnel to configure an explicit path:

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name po4
RP/0/RP0/CPU0:router(config-if)# path-option protecting 1 explicit name po6
  

The following example shows how to limit CSPF to a single OSPF instance and area:

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name router1 ospf 3 area 7 verbatim
  

The following example shows how to limit CSPF to a single IS-IS instance and area:

RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# path-option 1 dynamic isis mtbf level 1 lockdown
            

Related Commands

Command

Description

mpls traffic-eng path-protection switchover gmpls

Specifies a switchover for path protection.

show explicit-paths

Displays the configured IP explicit paths.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

path-option (P2MP TE)

To configure the primary or fallback path setup option for a Point-to-Multipoint (P2MP) TE tunnel, use the path-option command in P2MP destination interface configuration mode. To return to the default behavior, use the no form of this command.

path-option preference-priority { dynamic | explicit { name path-name | identifier path-number } } [verbatim] [lockdown]

no path-option preference-priority { dynamic | explicit { name path-name | identifier path-number } } [verbatim] [lockdown]

Syntax Description

preference-priority

Path option number. Range is from 1 to 1000.

dynamic

Specifies that label switched paths (LSP) are dynamically calculated.

explicit

Specifies that LSP paths are IP explicit paths.

name path-name

Specifies the path name of the IP explicit path.

identifier path-number

Specifies a path number of the IP explicit path.

verbatim

(Optional) Bypasses the Topology/CSPF check for explicit paths.

lockdown

(Optional) Specifies that the LSP cannot be reoptimized.

Command Default

None

Command Modes

P2MP destination interface configuration

Command History

Release

Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You can configure several path options for each destination of a P2MP tunnel. For example, for one tunnel, there can be several explicit path options and a dynamic option. The path preference is for lower (not higher) numbers, so option 1 is preferred over higher options.

When the lower number path option fails, the next path option under the destination is attempted.

Several path-options can be configured for each destination under a tunnel.

When configuring multiple path-options under each destination of a P2MP tunnel, the PCALC on the TE tunnel source attempts to generate the P2MP tree starting from the preferred path-options (lower numbers) for each destination. If some destinations use explicit paths that cause remerges with the dynamic generated paths for other destinations in the P2MP tree, the PCALC source modifies the dynamic paths (for example, optimal path); therefore, it follows the explicit path to correct the remerge problem.

The path-option command is common for both Point-to-Point (P2P) and P2MP tunnels.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

This example shows how to configure a P2MP tunnel with two destinations and several path-options per destination:

RP/0/RP0/CPU0:router(config)# interface tunnel-mte 100
RP/0/RP0/CPU0:router(config-if)#  destination 1.1.1.1
RP/0/RP0/CPU0:router(config-if-p2mp-dest)# path-option 1 explicit name po_dest1
RP/0/RP0/CPU0:router(config-if-p2mp-dest)# path-option 2 dynamic
  

This example shows that the fallback path option is dynamic:

RP/0/RP0/CPU0:router(config)# interface tunnel-mte 100 
RP/0/RP0/CPU0:router(config-if)# destination 2.2.2.2
RP/0/RP0/CPU0:router(config-if-p2mp-dest)# path-option 1 explicit name po_dest2
RP/0/RP0/CPU0:router(config-if-p2mp-dest)# path-option 2 dynamic

Related Commands

Command

Description

destination (MPLS-TE)

Configures the destination address of a TE tunnel.

mpls traffic-eng path-protection switchover gmpls

Specifies a switchover for path protection.

show explicit-paths

Displays the configured IP explicit paths.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

show mrib mpls traffic-eng fast-reroute

Displays information about Multicast Routing Information Base (MRIB) MPLS traffic engineering fast reroute.

path-selection ignore overload (MPLS-TE)

To ignore the Intermediate System-to-Intermediate System (IS-IS) overload bit setting for MPLS-TE, use the path-selection ignore overload command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

path-selection ignore overload {head | mid | tail}

no path-selection ignore overload {head | mid | tail}

Syntax Description

head

The tunnel stays up if set-overload-bit is set by ISIS on the head router. Ignores overload node during CSPF for the head node.

mid

The tunnel stays up if set-overload-bit is set by ISIS on the mid router. Ignores overload node during CSPF for the mid node.

tail

The tunnel stays up if set-overload-bit is set by ISIS on the tail router. Ignores overload node during CSPF for the tail node.

Command Default

None

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Release 4.1.0

The head, mid, and tail keywords were added.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the path-selection ignore overload command to ensure that label switched paths (LSPs) are not broken because of routers that have IS-IS overload bit as enabled.

When the IS-IS overload bit avoidance (OLA) feature is activated, all nodes with the overload bit set, which includes head nodes, mid nodes, and tail nodes, are ignored. This means that they are still available for use with label switched paths (LSPs). This feature allows you to include an overloaded node in constraint-based shortest path first (CSPF).

Task ID

Task ID

Operations

mpls-te

read, write

Examples

This example shows how to use the path-selection ignore overload head command:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection ignore overload
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection ignore overload head
  

path-selection loose-expansion affinity (MPLS-TE)

To specify the affinity value to be used to expand a path to the next loose hop for a tunnel on an area border router, use the path-selection loose-expansion affinity command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

path-selection loose-expansion affinity affinity-value mask affinity-mask [ class-type type ]

no path-selection loose-expansion affinity affinity-value mask affinity-mask [ class-type type ]

Syntax Description

affinity-value

Attribute values required for links carrying this tunnel. A 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1.

mask affinity-mask

Checks the link attribute, a 32-bit decimal number. Range is 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute mask is 0 or 1.

class-type type

(Optional) Requests the class-type of the tunnel bandwidth. Range is 0 to 1.

Command Default

affinity-value : 0X00000000

mask-value : 0XFFFFFFFF

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The new affinity scheme (based on names) is not supported for loose-hop expansion. New configuration does not affect the already up tunnels.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure affinity 0x55 with mask 0xFFFFFFFF:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection loose-expansion affinity 55 mask FFFFFFFF
            

Related Commands

Command

Description

path-selection loose-expansion metric (MPLS-TE)

Configures a metric type to be used to expand a path to the next loose hop for a tunnel on an area border router.

path-selection metric (MPLS-TE)

Configures the MPLS-TE tunnel path-selection metric.

path-selection loose-expansion metric (MPLS-TE)

To configure a metric type to be used to expand a path to the next loose hop for a tunnel on an area border router, use the path-selection loose-expansion metric command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

path-selection loose-expansion metric { igp | te } [ class-type type ]

no path-selection loose-expansion metric { igp | te } [ class-type type ]

Syntax Description

igp

Configures an Interior Gateway Protocol (IGP) metric.

te

Configures a TE metric. This is the default.

class-type type

(Optional) Requests the class type of the tunnel bandwidth. Range is 0 to 1.

Command Default

The default is TE metric.

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


New configurations do not affect tunnels that are already up.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the path-selection metric to use the IGP metric overwriting default:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection loose-expansion metric igp
  

Related Commands

Command

Description

path-selection loose-expansion affinity (MPLS-TE)

Specifies the affinity value to be used to expand a path to the next loose hop for a tunnel on an area border router.

path-selection metric (MPLS-TE)

To specify the MPLS-TE tunnel path-selection metric, use the path-selection metric command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

path-selection metric { igp | te }

no path-selection metric { igp | te }

Syntax Description

igp

Configures an Interior Gateway Protocol (IGP) metric.

te

Configures a TE metric.

Command Default

The default is TE metric.

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The metric type to be used for path calculation for a given tunnel is determined as follows:

  • If the path-selection metric command was entered to specify a metric type for the tunnel, use that metric type.
  • Otherwise, use the default (TE) metric.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the path-selection metric to use the IGP metric overwriting default:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng 
RP/0/RP0/CPU0:router(config-mpls-te)# path-selection metric igp
  

Related Commands

Command

Description

path-selection loose-expansion affinity (MPLS-TE)

Specifies the affinity value to be used to expand a path to the next loose hop for a tunnel on an area border router.

path-selection metric (interface)

To configure an MPLS-TE tunnel path-selection metric type, use the path-selection metric command in interface configuration mode. To return to the default behavior, use the no form of this command.

path-selection metric { igp | te }

no path-selection metric { igp | te }

Syntax Description

igp

Configures Interior Gateway Protocol (IGP) metrics.

te

Configures TE metrics. This is the default.

Command Default

The default is TE metrics.

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The metric type to be used for path calculation for a given tunnel is determined as follows:

  • If the path-selection metric command was entered to either a metric type for the tunnel or only a metric type, use that metric type.
  • Otherwise, use the default (TE) metric.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the path-selection metric to use the IGP metric overwriting default:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1 
RP/0/RP0/CPU0:router(config-if)# path-selection metric igp
            

Related Commands

Command

Description

show mpls traffic-eng topology

Displays the tunnel path used.

pce address (MPLS-TE)

To configure the IPv4 self address for Path Computation Element (PCE), use the pce address command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

pce address ipv4 address

no pce address ipv4 address

Syntax Description

ipv4 address

Configures the IPv4 address for PCE.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.5.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The IP address is used in the TCP communication with the other PCEs or PCCs. In addition, this address is advertised using IGP.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure the IPv4 self address for PCE:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce address ipv4 10.10.10.10
            

Related Commands

Command

Description

pce keepalive (MPLS-TE)

Configures a PCEP keepalive interval.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce peer (MPLS-TE)

Configures an IPv4 self address for a PCE peer.

pce reoptimize (MPLS-TE)

Configures a periodic reoptimization timer.

pce request-timeout (MPLS-TE)

Configures a PCE request-timeout.

pce tolerance keepalive (MPLS-TE)

Configures a PCE tolerance keepalive (which is the minimum acceptable peer proposed keepalive).

pce deadtimer (MPLS-TE)

To configure a path computation element (PCE) deadtimer, use the pce deadtimer command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

pce deadtimer value

no pce deadtimer value

Syntax Description

value

Keepalive dead interval, in seconds. The range is 0 to 255.

Command Default

value: 120

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

When the dead interval is 0, the LSR does not time out a PCEP session to a remote peer.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a PCE deadtimer:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce deadtimer 50
            

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce address (MPLS-TE)

Configures the IPv4 self address for a PCE.

pce keepalive (MPLS-TE)

Configures a PCEP keepalive interval.

pce peer (MPLS-TE)

Configures an IPv4 self address for a PCE peer.

pce reoptimize (MPLS-TE)

Configures a periodic reoptimization timer.

pce request-timeout (MPLS-TE)

Configures a PCE request-timeout.

pce tolerance keepalive (MPLS-TE)

Configures a PCE tolerance keepalive (which is the minimum acceptable peer proposed keepalive).

pce keepalive (MPLS-TE)

To configure a path computation element protocol (PCEP) keepalive interval, use the pce keepalive command in MPLS-TE configuration mode. To disable this command, use the no form of this command.

pce keepalive interval

no pce keepalive interval

Syntax Description

interval

Keepalive interval, in seconds. The range is 0 to 255.

Command Default

interval: 30

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

When the keepalive interval is 0, the LSR does not send keepalive messages.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure PCEP keepalive interval for 10 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router#(config-mpls-te) pce keepalive 10
  

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce address (MPLS-TE)

Configures the IPv4 self address for a PCE.

pce deadtimer (MPLS-TE)

Configures a PCE deadtimer.

pce peer (MPLS-TE)

Configures an IPv4 self address for a PCE peer.

pce reoptimize (MPLS-TE)

Configures a periodic reoptimization timer.

pce request-timeout (MPLS-TE)

Configures a PCE request-timeout.

pce tolerance keepalive (MPLS-TE)

Configures a PCE tolerance keepalive (which is the minimum acceptable peer proposed keepalive).

pce peer (MPLS-TE)

To configure an IPv4 self address for a path computation element (PCE) peer, use the pce peer command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

pce peer ipv4 address

no pce peer ipv4 address

Syntax Description

ipv4 address

Configures the IPv4 address for PCE.

Command Default

TE metric

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.5.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure an IPv4 self address for a PCE peer:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng 
RP/0/RP0/CPU0:router(config-mpls-te)# pce peer ipv4 11.11.11.11
  

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce address (MPLS-TE)

Configures the IPv4 self address for a PCE.

pce deadtimer (MPLS-TE)

Configures a PCE deadtimer.

pce keepalive (MPLS-TE)

Configures a PCEP keepalive interval.

pce reoptimize (MPLS-TE)

Configures a periodic reoptimization timer.

pce request-timeout (MPLS-TE)

Configures a PCE request-timeout.

pce tolerance keepalive (MPLS-TE)

Configures a PCE tolerance keepalive (which is the minimum acceptable peer proposed keepalive).

pce reoptimize (MPLS-TE)

To configure a periodic reoptimization timer, use the pce reoptimize command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.

pce reoptimize value

no pce reoptimize value

Syntax Description

value

Periodic reoptimization timer value, in seconds. The range is 60 to 604800.

Command Default

value: 3600

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

When the dead interval is 0, the LSR does not time out a path computation element protocol (PCEP) session to a remote peer.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a periodic reoptimization timer for 200 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce reoptimize 200
            

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce address (MPLS-TE)

Configures the IPv4 self address for a PCE.

pce deadtimer (MPLS-TE)

Configures a PCE deadtimer.

pce keepalive (MPLS-TE)

Configures a PCEP keepalive interval.

pce peer (MPLS-TE)

Configures an IPv4 self address for a PCE peer.

pce request-timeout (MPLS-TE)

Configures a PCE request-timeout.

pce tolerance keepalive (MPLS-TE)

Configures a PCE tolerance keepalive (which is the minimum acceptable peer proposed keepalive).

pce request-timeout (MPLS-TE)

To configure a path computation element (PCE) request-timeout, use the pce request-timeout command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.

pce request-timeout value

no pce request-timeout value

Syntax Description

value

PCE request-timeout, in seconds. The range is 5 to 100.

Command Default

value: 10

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

PCC or PCE keeps a pending path request only for the request-timeout period.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a PCE request-timeout for 10 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# pce request-timeout 10
            

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce address (MPLS-TE)

Configures the IPv4 self address for a PCE.

pce deadtimer (MPLS-TE)

Configures a PCE deadtimer.

pce keepalive (MPLS-TE)

Configures a PCEP keepalive interval.

pce peer (MPLS-TE)

Configures an IPv4 self address for a PCE peer

pce reoptimize (MPLS-TE)

Configures a periodic reoptimization timer.

pce tolerance keepalive (MPLS-TE)

Configures a PCE tolerance keepalive (which is the minimum acceptable peer proposed keepalive).

pce tolerance keepalive (MPLS-TE)

To configure a path computation element (PCE) tolerance keepalive (which is the minimum acceptable peer proposed keepalive), use the pce tolerance keepalive command in MPLS-TE configuration mode. To disable this feature, use the no form of this command.

pce tolerance keepalive value

no pce tolerance keepalive value

Syntax Description

value

PCE tolerance keepalive value, in seconds. The range is 0 to 255.

Command Default

value: 10

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.8.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a PCE tolerance keepalive for 10 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng 
RP/0/RP0/CPU0:router(config-mpls-te)# pce tolerance keepalive 10
            

Related Commands

Command

Description

mpls traffic-eng

Enters MPLS-TE configuration mode.

path-option (MPLS-TE)

Configures a path option for an MPLS-TE tunnel.

pce address (MPLS-TE)

Configures the IPv4 self-address for a PCE.

pce deadtimer (MPLS-TE)

Configures a PCE deadtimer.

pce keepalive (MPLS-TE)

Configures a PCEP keepalive interval.

pce peer (MPLS-TE)

Configures an IPv4 self address for a PCE peer

pce reoptimize (MPLS-TE)

Configures a periodic reoptimization timer.

pce request-timeout (MPLS-TE)

Configures a PCE request-timeout.

policy-class

To configure policy-based tunnel selection (PBTS) to direct traffic into specific TE tunnels, use the policy-class command in interface configuration mode. To disable this feature, use the no form of this command.

policy-class { 1 - 7 | }

no policy-class

Syntax Description

1 - 7

Policy-class attribute to map the correct traffic class to this policy.

Command Default

Command Modes

Interface configuration

Command History

Release

Modification

Release 3.6.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the policy-class command to enable policy-based tunnel selection (PBTS). See Cisco IOS XR MPLS Configuration Guide for the Cisco CRS-1 Router for more information on PBTS.

To display the configured PBTS policy-class value, use the show mpls traffic-eng tunnels command.

To display information about PBTS configuration, use the show cef and show cef hardware commands in Cisco IOS XR IP Addresses and Services Command Reference for the Cisco CRS-1 Router.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a policy class:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RP0/CPU0:router(config-if)# policy-class 7
            

Related Commands

Command

Description

interface tunnel-te

Configures an MPLS-TE tunnel interface.

show cef

Displays the IPv4 or IPv6 Cisco Express Forwarding table.

show cef hardware

Displays Cisco Express Forwarding IPv4 or IPv6 hardware status and configuration information.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

priority (MPLS-TE)

To configure the setup and reservation priority for an MPLS-TE tunnel, use the priority command in interface configuration mode. To return to the default behavior, use the no form of this command.

priority setup-priority hold-priority

no priority setup-priority hold-priority

Syntax Description

setup-priority

Priority used when signaling a label switched path (LSP) for this tunnel to determine which existing tunnels can be preempted. Range is 0 to 7 (in which a lower number indicates a higher priority). Therefore, an LSP with a setup priority of 0 can preempt any LSP with a non-0 priority.

hold-priority

Priority associated with an LSP for this tunnel to determine if it should be preempted by other LSPs that are being signaled. Range is 0 to 7 (in which a lower number indicates a higher priority).

Command Default

setup-priority: 7

hold-priority: 7

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a tunnel with a setup and hold priority of 1:

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

Related Commands

Command

Description

interface tunnel-te

Configures an MPLS-TE tunnel interface.

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.

Command Default

No default behavior or values

Command Modes

Interface configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


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 enable record-route on the TE tunnel:

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

Related Commands

Command

Description

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

remote (GMPLS)

To configure Link Management Protocol (LMP) Neighbor remote Traffic Engineering (TE) links, use the remote command in MPLS-TE interface LMP data link adjacency configuration mode. To return to the default behavior, use the no form of this command.

remote { interface-id unnum identifier | switching capability | { fsc | lsc | psc1 } | te-link-id | { ipv4 address | unnum identifier } }

no remote { interface-id unnum identifier | switching capability | { fsc | lsc | psc1 } | te-link-id | { ipv4 address | unnum identifier } }

Syntax Description

interface-id

Configures the LMP neighbor remote interface identifier.

unnum identifier

Configures the unnumbered interface identifier. Range is 1 to 4294967295.

switching-capability

Configures the remote LMP MPLS-TE interface switching capability.

fsc | lsc | psc1

Configures the capability types: Fiber-Switch Capable, Lambda-Switch Capable, and Packet-Switch Capable.

te-link-id

Configures the remote LMP MPLS-TE link ID address.

ipv4 address

Configures the IPv4 address.

unnum identifier

Configures the unnumbered interface and identifier.

Command Default

No default behavior or values

Command Modes

MPLS-TE interface LMP data link adjacency configuration

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


The LMP and GMPLS-NNI features are not supported on x86 RPs.


Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure LMP Neighbor remote TE links for unnumber interface-id 1066:

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/1/0/0
RP/0/RP0/CPU0:router(config-mpls-te-if)# lmp data-link adjacency
RP/0/RP0/CPU0:router(config-mpls-te-if-adj)# remote interface-id unnnum 1066
  

Related Commands

Command

Description

destination (MPLS-TE)

Configures bidirectional optical tunnels.

lmp hello (GMPLS)

Configures LMP IPCC management hello settings.

match (GMPLS)

Configures or matches active and passive tunnels.

passive (GMPLS)

Configures passive GMPLS tunnels.

switching (GMPLS)

Configures TE-link switching attributes.

reoptimize (MPLS-TE)

To force the reoptimization interval for all TE tunnels, use the reoptimize command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

reoptimize frequency

no reoptimize frequency

Syntax Description

frequency

Timer frequency range, in seconds. Range is from 0 to 604800.

Note:
  • A value of 0 disables periodic reoptimization.
  • Any value in the range from 1 to 60 results in periodic reoptimization that occurs every 60 seconds.

Command Default

frequency: 3600

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to force the reoptimization interval to 60 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize 60
  

Related Commands

Command

Description

mpls traffic-eng reoptimize (EXEC)

Triggers the reoptimization interval of all TE tunnels.

reoptimize timers delay (MPLS-TE)

To delay removal or relabeling of the old label switched paths (LSPs) (reoptimized LSP from the forwarding plane) after tunnel reoptimization, use the reoptimize timers delay command in MPLS-TE configuration mode. To restore the default value, use the no form of this command.

reoptimize timers delay { after-frr seconds | cleanup delay-time | installation delay-time | path-protection seconds }

no reoptimize timers delay { after-frr seconds | cleanup delay-time | installation delay-time | path-protection seconds }

Syntax Description

after-frr

Delays the LSP reoptimization in the event of the FRR.

seconds

Reoptimization initiation delay time of the tunnel, in seconds, after an FRR event. Range is from 0 to 120.

cleanup

Delays removal of the old LSPs after tunnel reoptimization.

delay-time

Reoptimization delay time, in seconds. A value of 0 disables delay. The valid range is from 0 to 300 for cleanup time.

installation

Delays installation of a new label after tunnel reoptimization.

delay-time

Reoptimization delay time, in seconds. A value of 0 disables delay. The valid range is 0 to 3600 for installation time.

path-protection

Delays the time between path protection switchover event and tunnel reoptimization.

seconds

Time, in seconds, between path protection switchover event and tunnel reoptimization. A value of 0 disables delay. Range is from 0 to 604800.

Command Default

after-frr delay: 0

cleanup delay: 20

delay-time: 20

installation delay: 20

path-protection: 180

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.9.0

The after-frr and path-protection keywords were added.

Usage Guidelines

A device with Multiprotocol Label Switching traffic engineering (MPLS-TE) tunnels periodically examines tunnels with established LSPs to discover whether more efficient LSPs (paths) are available. If a better LSP is available, the device signals the more efficient LSP; if the signaling is successful, the device replaces the older LSP with the new, more efficient LSP.

Sometimes the slower router-point nodes may not yet utilize the new label’s forwarding plane. In this case, if the headend node replaces the labels quickly, it can result in brief packet loss. By delaying the cleanup of the old LSP using the reoptimize timers delay cleanup command, packet loss is avoided.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to set the reoptimization cleanup delay time to 1 minute:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize timers delay cleanup 60
		

The following example shows how to set the reoptimization installation delay time to 40 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize timers delay installation 40 
		

The following example shows how to set the reoptimization delay time after the event of the FRR to 50 seconds:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize timers delay after-frr 50
		

The following example shows how to set the reoptimization delay time between path protection switchover event and tunnel reoptimization to 80:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# reoptimize timers delay path-protection 80
		

Related Commands

Command

Description

reoptimize (MPLS-TE)

Reoptimizes all traffic engineering tunnels immediately.

mpls traffic-eng reoptimize (EXEC)

Configures the reoptimization interval of all TE tunnels.

router-id secondary (MPLS-TE)

To configure a secondary TE router identifier in MPLS-TE to be used locally (not advertised through IGP), use the router-id secondary command in MPLS-TE configuration mode. To return to the default behavior, use the no form of this command.

router-id secondary IP address

no router-id secondary IP address

Syntax Description

IP address

IPv4 address to be used as secondary TE router ID.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

Command History

Release

Modification

Release 3.4.1

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the router-id secondary command on tail end nodes to terminate verbatim tunnels to secondary TE RIDs as destinations.

You can configure up to 32 IPv4 addresses as TE secondary router IDs.

Task ID

Task ID

Operations

mpls-te

read, write

Examples

The following example shows how to configure a secondary TE router identifier in MPLS-TE:

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls traffic-eng 
RP/0/RP0/CPU0:router(config-mpls-te)# router-id secondary 1.1.1.1
RP/0/RP0/CPU0:router(config-mpls-te)# router-id secondary 2.2.2.2
            

Related Commands

Command

Description

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

Specifies that the TE router identifier for the node is the IP address associated with a given interface.

show explicit-paths

To display the configured IP explicit paths, use the show explicit-paths command in EXEC mode.

show explicit-paths [ name path-name | identifier number ]

Syntax Description

name path-name

(Optional) Displays the name of the explicit path.

identifier number

(Optional) Displays the number of the explicit path. Range is 1 to 65535.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

An IP explicit path is a list of IP addresses that represent a node or link in the explicit path.

Task ID

Task ID

Operations

mpls-te

read

Examples

The following shows a sample output from the show explicit-paths command:

RP/0/RP0/CPU0:router# show explicit-paths
  
  Path ToR2    status enabled 
          0x1: next-address 192.168.1.2 
          0x2: next-address 10.20.20.20 
  Path ToR3    status enabled 
          0x1: next-address 192.168.1.2
          0x2: next-address 192.168.2.2 
          0x3: next-address 10.30.30.30
  Path 100    status enabled 
          0x1: next-address 192.168.1.2 
          0x2: next-address 10.20.20.20 
  Path 200    status enabled
          0x1: next-address 192.168.1.2
          0x2: next-address 192.168.2.2 
          0x3: next-address 10.30.30.30
  

This table describes the significant fields shown in the display.



Table 1 show explicit-paths Command Field Descriptions

Field

Description

Path

Pathname or number, followed by the path status.

1: next-address

First IP address in the path.

2: next-address

Second IP address in the path.

The following shows a sample output from the show explicit-paths command using a specific path name:

RP/0/RP0/CPU0:router# show explicit-paths name ToR3
  
  Path ToR3    status enabled 
          0x1:  next-address 192.168.1.2
          0x2:  next-address 192.168.2.2 
          0x3:  next-address 10.30.30.30
  
 

The following shows a sample output from the show explicit-paths command using a specific path number:

RP/0/RP0/CPU0:router# show explicit-paths identifier 200
  
  Path 200    status enabled
          0x1:  next-address 192.168.1.2
          0x2:  next-address 192.168.2.2 
          0x3:  next-address 10.30.30.30
 

Related Commands

Command

Description

index exclude-address

Specifies the next IP address to exclude from the explicit path.

index next-address

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 affinity-map command in EXEC mode.

show mpls traffic-eng affinity-map

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.4.0

This command was introduced.

Release 3.9.0

The Bit Position field was added to the sample output.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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

Task ID

Operations

mpls-te

read

Examples

The following shows a sample output from the show mpls traffic-eng affinity-map command:

RP/0/RP0/CPU0:router# show mpls traffic-eng affinity-map
  
  Affinity Name                            Bit-position     Affinity Value
    ----------------------------------   --------------   ----------------
     bcdefghabcdefghabcdefghabcdefgha                0                  1
                                 red1                1                  2
                                 red2                2                  4
                                 red3                3                  8
                                 red4                4                 10
                                 red5                5                 20
                                 red6                6                 40
                                 red7                7                 80
                                 red8                8                100
                                 red9                9                200
                                red10               10                400
                                red11               11                800
                                red12               12               1000
                                red13               13               2000
                                red14               14               4000
                                red15               15               8000
                                red16               16              10000
     cdefghabcdefghabcdefghabcdefghab               17              20000
                                red18               18              40000
                                red19               19              80000
                                red20               20             100000
                                red21               21             200000
                                red22               22             400000
                                red23               23             800000
                                red24               24            1000000
                                red25               25            2000000
                                red26               26            4000000
                                red27               27            8000000
                              black28               28           10000000
                                red28               29           20000000
                                red30               30           40000000
     abcdefghabcdefghabcdefghabcdefgh               31           80000000
  

Table 1describes the significant fields shown in the display.

Table 2 show mpls traffic-eng affinity-map Field Descriptions

Field

Description

Affinity Name

Affinity name associated with the tunnel affinity constraints.

Bit-position

Bit position set in the 32-bit affinity value

Affinity Value

Affinity value associated with the affinity name.

Related Commands

Command

Description

affinity

Configures an affinity (the properties the tunnel requires in its links) for an MPLS-TE tunnel.

affinity-map

Assigns a numerical value to each affinity name.

show mpls traffic-eng attribute-set

To display the attribute set for MPLS-TE, use the show mpls traffic-eng attribute-set command in EXEC mode.

show mpls traffic-eng attribute-set [ auto-backup | auto-mesh | path-option | [attribute-set-name] ]

Syntax Description

auto-backup

Displays information for the auto-backup attribute type.

auto-mesh

Displays information for the auto-mesh attribute type.

path-option

Displays information for the path-option attribute type.

attribute-set-name

Specifies the name of the attribute set to be displayed.

Command Default

Displays information about all types of attribute sets.

Command Modes

EXEC mode

Command History

Release

Modification

Release 4.2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

To use this command, first enable the MPLS-TE application.

Task ID

Task ID Operation

mpls-te

read

Examples

The following command shows the attribute set for auto-backup attribute type.

RP/0/RP0/CPU0:routershow mpls traffic-eng attribute-set auto-backup auto1

Attribute Set Name: auto1 (Type: auto-backup)
  Affinity: 0x0/0xffff  (Default)
  Priority: 7 7 (Default)
  Record-route: Enabled
  Policy-class: 0 (Not configured)
  Logging: None
  List of protected interfaces (count 0)
  List of tunnel IDs (count 0)

The following command shows the attribute set for auto-mesh attribute type.

RP/0/RP0/CPU0:routershow mpls traffic-eng attribute-set auto-mesh mesh1

Attribute Set Name: mesh1 (Type: auto-mesh)
  Bandwidth: 0 kbps (CT0) (Default)
  Affinity: 0x0/0xffff  (Default)
  Priority: 7 7 (Default)
  Interface Bandwidth: 0 kbps (Default)
  AutoRoute Announce: Disabled
  Auto-bw: Disabled
  Soft Preemption: Disabled
  Fast Reroute: Disabled, Protection Desired: None
  Record-route: Disabled
  Policy-class: 0 (Not configured)
  Logging: None
  List of Mesh Groups (count 0)

The following command shows the attribute set for path-option attribute type.

RP/0/RP0/CPU0:routershow mpls traffic-eng attribute-set path-option path1

Attribute Set Name: path1 (Type: path option)
  Bandwidth: 0 kbps (CT0) (Default)
  Affinity: 0x0/0xffff  (Default)
  List of tunnel IDs (count 0)

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 [IP-address]

Syntax Description

IP-address

(Optional) Tunnel leading to this address.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

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 autoroutecommand displays those tunnels IGP is currently using in its enhanced SPF calculation (that is, which tunnels are up and have autoroute configured).

Tunnels are organized by destination. All tunnels to a destination carry a share of the traffic tunneled to that destination.

Task ID

Task ID

Operations

mpls-te

read

Examples

The following shows a sample output from the show mpls traffic-eng autoroute command:

RP/0/RP0/CPU0:router# show mpls traffic-eng autoroute
  
  Destination 103.0.0.3 has 2 tunnels in OSPF 0 area 0
  tunnel-te1 (traffic share 1, nexthop 103.0.0.3)
  tunnel-te2 (traffic share 1, nexthop 103.0.0.3)
  

This table describes the significant fields shown in the display.



Table 3 show mpls traffic-eng autoroute Command Field Descriptions

Field

Description

Destination

Multiprotocol Label Switching (MPLS) TE tail-end router ID.

traffic share

A factor based on bandwidth, indicating how much traffic this tunnel should carry, relative to other tunnels, to the same destination. If two tunnels go to a single destination, one with a traffic share of 200 and the other with a traffic share of 100, the first tunnel carries two-thirds of the traffic.

Nexthop

Next-hop router ID of the MPLS-TE tunnel.

absolute metric

Metric with mode absolute for the MPLS-TE tunnel.

relative metric

Metric with mode relative for the MPLS-TE tunnel.

Related Commands

Command

Description

autoroute metric

Specifies the MPLS-TE tunnel metric that the IGP-enhanced SPF calculation will use.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.

topology holddown sigerr (MPLS-TE)

Specifies the time that a router should ignore a link in its TE topology database in tunnel path CSPF computations following a TE tunnel signalling error on the link.

show mpls traffic-eng auto-tunnel backup

To display information about automatically build MPLS-TE backup tunnels, use the show mpls traffic-eng auto-tunnel backup command in EXEC mode.

show mpls traffic-eng auto-tunnel { backup [ private | summary | unused ] }

Syntax Description

backup

Displays information about auto-tunnel backup.

private

(Optional) Displays private information about the automatically build MPLS-TE backup tunnels.

summary

(Optional) Displays the automatically build MPLS-TE backup tunnels summary information.

unused

(Optional) Displays only unused MPLS-TE backup tunnels.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release Modification
Release 4.0.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID Operation
mpls-te

read

Examples

This is sample output from the show mpls traffic-eng auto-tunnel backup command:

AutoTunnel Backup Configuration:
    Interfaces count: 4
    Unused removal timeout: 1h 0m 0s
    Configured tunnel number range: 2000-2500

AutoTunnel Backup Summary:
    AutoTunnel Backups:
             1 created, 1 up, 0 down, 0 unused
             1 NHOP, 0 NNHOP, 0 SRLG strict, 0 SRLG preferred
    Protected LSPs:
             1 NHOP, 0 NHOP+SRLG
             0 NNHOP, 0 NNHOP+SRLG
    Protected S2L Sharing Families:
             0 NHOP, 0 NHOP+SRLG
             0 NNHOP, 0 NNHOP+SRLG
    Protected S2Ls:
             0 NHOP, 0 NHOP+SRLG
             0 NNHOP, 0 NNHOP+SRLG

Cumulative Counters (last cleared 05:17:19 ago):
                        Total   NHOP  NNHOP
    Created:                1      1      0
    Connected:              1      1      0
    Removed (down):         0      0      0
    Removed (unused):       0      0      0
    Removed (in use):       0      0      0
    Range exceeded:         0      0      0

AutoTunnel Backups:
        Tunnel   State   Protection   Prot.       Protected   Protected
          Name              Offered  Flows*       Interface    Node
-------------- ------- ------------ ------- --------------- ---------------
 tunnel-te2000      up NHOP               1       Gi0/2/0/2     N/A

*Prot. Flows = Total Protected LSPs, S2Ls and S2L Sharing Families

This is sample output from the show mpls traffic-eng auto-tunnel mesh command:

RP/0/RP0/CPU0:router#show mpls traffic-eng auto-tunnel mesh

Auto-tunnel Mesh Global Configuration: 
  Unused removal timeout: 2h
  Configured tunnel number range: 10000-12000

Auto-tunnel Mesh Groups Summary:
  Mesh Groups count: 5
Mesh Groups Destinations count: 50

Mesh Group 40 (2 Destinations, 1 Up, 1 Down):
  Destination-list: dl-40
  Attribute-set: ta_name 
  Destination: 40.40.40.40, tunnel-id: 10000, State: Up
  Destination: 10.10.10.10, tunnel-id: 10001, State: Down
Mesh Group 41 (3 Destinations, 2 Up, 1 Down):
  Destination-list: dl-40
  Attribute-set: ta_name 
  Destination: 4.4.4.4, tunnel-id: 10005, State: Up
  Destination: 3.3.3.3, tunnel-id: 10006, State: Up
  Destination: 1.1.1.1, tunnel-id: 10007, State: Down
Mesh Group 51 (0 Destinations, 0 Up, 0 Down):
  Destination-list: Not configured
  Attribute-set: Not configured 
Mesh Group 52 (0 Destinations, 0 Up, 0 Down):
  Destination-list: NAME1 (Not defined)
  Attribute-set: NAME2 (Not defined)
Mesh Group 53 (2 Destinations, 1 Up, 1 Down):
  Destination-list: dl-53
  Attribute-set: Not configured 
  Destination: 40.40.40.40, tunnel-id: 10000, State: Up
  Destination: 10.10.10.10, tunnel-id: 10001, State: Down
 

Cumulative Counters (last cleared 7h ago):
                    Total     
  Created:            100
  Connected:           50  
  Removed (unused):    50 
  Removed (in use):     0 
  Range exceeded:       0  

This is sample output from the show mpls traffic-eng auto-tunnel private command:

Auto-tunnel Mesh Private Information:
  ID allocator overall maximum ID: 4096
  ID allocator last allocated ID: 50999
  ID allocator number IDs allocated: 1000

show mpls traffic-eng auto-tunnel mesh

To display information about automatically built MPLS-TE mesh tunnels, use the show mpls traffic-eng auto-tunnel mesh command in EXEC mode.

show mpls traffic-eng auto-tunnel mesh { mesh-value | unused | summary | attribute-set name | destination address | destination-list name | down | up | tunnel { created | not-created } }

Syntax Description

mesh mesh-value

Displays the tunnels that belong to the specified auto-tunnel mesh group. The range of mesh group ID is from 0 to 4294967295.

attribute-set name

Displays mesh-groups configured with a specific attribute set.

destination address

Displays only the destinations with a specified address.

destination-list name

Displays mesh-groups configured with a specified prefix-list.

down

Displays only those tunnels that are down.

up

Displays only those tunnels that are up.

summary

Displays auto-tunnel mesh summary information.

unused

Displays only the down tunnels with no destination in the topology.

tunnel created | not-created

Specifies either created destinations with tunnels, or not-created destinations without tunnels.

Command Default

None

Command Modes

EXEC

Command History

Release Modification

Release 4.1.1

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID Operation

MPLS-TE

read

Examples

This is sample output from the show mpls traffic-eng auto-tunnel mesh command:

RP/0/RP0/CPU0:router show mpls traffic-eng auto-tunnel mesh 

Auto-tunnel Mesh Global Configuration:
  Unused removal timeout: 1h 0m 0s
  Configured tunnel number range: 1000-1200

Auto-tunnel Mesh Groups Summary:
  Mesh Groups count: 1
  Mesh Groups Destinations count: 3
  Mesh Groups Tunnels count:
    3 created, 0 up, 3 down, 0 FRR enabled

Mesh Group: 65 (3 Destinations)
  Status: Enabled
  Attribute-set: am-65
  Destination-list: dl-65 (Not a prefix-list)
  Recreate timer: Not running
       Destination    Tunnel ID    State  Unused timer
  ----------------  -----------  -------  ------------
       192.168.0.2         1000     up   Not running
       192.168.0.3         1001     up   Not running
       192.168.0.4         1002     up   Not running
  Displayed 3 tunnels, 0 up, 3 down, 0 FRR enabled

Auto-mesh Cumulative Counters:
  Last cleared: Wed Nov  9 12:56:37 2011 (02:39:07 ago)
                      Total
  Created:                3
  Connected:              0
  Removed (unused):       0
  Removed (in use):       0
  Range exceeded:         0

This shows how to configure the auto-tunnel mesh command with destination-list and attribute-set keywords:


RP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# auto-tunnel mesh
RP/0/RP0/CPU0:router(config-te-auto-mesh)# group 65
RP/0/RP0/CPU0:router(config-te-mesh-group)# disable
RP/0/RP0/CPU0:router(config-te-mesh-group)# destination-list dl-65
RP/0/RP0/CPU0:router(config-te-mesh-group)# attribute-set am-65

Note


This attribute-set is an optional configuration. Without this configuration, all tunnels use default tunnel attribute values. If you configure an non-existent attribute-set, this mesh group does not create any tunnel.

Note


This destination-list configuration is mandatory. If there is no IPv4 prefix-list by this name on the router, this mesh group create tunnels with all routers in the network.



show mpls traffic-eng collaborator-timers

To display the current status of the MPLS-TE collaborator timers, use the show mpls traffic-eng collaborator-timers command in EXEC mode.

show mpls traffic-eng collaborator-timers

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.9.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The MPLS-TE process maintains the timers for all of the collaborators such as RSVP, LSD, and so forth. The show mpls traffic-eng collaborator-timers command shows the status of these timers.

Task ID

Task ID

Operations

mpls-te

read

Examples

The following sample output shows the current status of the collaborator timers:

RP/0/RP0/CPU0:router# show mpls traffic-eng collaborator-timers
  
Collaborator Timers
-------------------
Timer Name: [LMRIB Restart] Index:[0]
    Duration: [60] Is running: NO
    Last start time:  02/09/2009 11:57:59
    Last stop time:   02/09/2009 11:58:00
    Last expiry time: Never expired
Timer Name: [LMRIB Recovery] Index:[1]
    Duration: [60] Is running: YES
    Last start time:  02/09/2009 11:58:00
    Last stop time:   Never Stopped
    Last expiry time: 19/08/2009 17:45:24
Timer Name: [RSVP Restart] Index:[2]
    Duration: [180] Is running: NO
    Last start time:  26/08/2009 18:59:18
    Last stop time:   26/08/2009 18:59:20
    Last expiry time: Never expired
Timer Name: [RSVP Recovery] Index:[3]
    Duration: [1800] Is running: NO
    Last start time:  26/08/2009 18:59:20
    Last stop time:   26/08/2009 19:03:19
    Last expiry time: 19/08/2009 18:12:39
Timer Name: [LSD Restart] Index:[4]
    Duration: [60] Is running: NO
    Last start time:  19/08/2009 17:44:26
    Last stop time:   19/08/2009 17:44:26
    Last expiry time: Never expired
Timer Name: [LSD Recovery] Index:[5]
    Duration: [600] Is running: NO
    Last start time:  19/08/2009 17:44:26
    Last stop time:   Never Stopped
    Last expiry time: 19/08/2009 17:53:44
Timer Name: [Clearing in progress BW for the whole topology] Index:[6]
    Duration: [60] Is running: YES
    Last start time:  02/09/2009 11:57:50
    Last stop time:   Never Stopped
    Last expiry time: 02/09/2009 11:57:50
  

This table describes the significant fields shown in the display.



Table 4 show mpls traffic-eng collaborator-timers Command Field Descriptions

Field

Description

Timer Name

Timer name that is associated to a collaborator.

Index

Identification number of the timer.

Duration

Expiry delay of the timer, in seconds. For example, the duration indicates the timer interval.

Is running

Timer is running low or not.

Last start time

Last time that the collaborator process for MPLS LSD was restarted.

Last stop time

Time TE was able to reconnect to the MPLS LSD process.

Last expiry time

Time that timer expired.

show mpls traffic-eng counters signaling

To display tunnel signaling statistics, use the show mpls traffic-eng counters signaling command in EXEC mode.

show mpls traffic-eng counters { signaling | soft-preemption } { tunnel -number | all | [ heads | mids | tails ] | name tunnel-name | summary }

Syntax Description

signaling

Displays signaling counters.

soft-preemption

Displays the statistics for the soft-preemption.

tunnel-number

Statistics for the input tunnel number. The range is from 0 to 65535.

all

Displays statistics for all tunnels.

heads

(Optional) Displays statistics for all tunnel heads.

mids

(Optional) Displays statistics for all tunnel midpoints.

tails

(Optional) Displays statistics for all tunnel tails.

name

Displays statistics for a specified tunnel.

tunnel-name

Name of the specified tunnel.

summary

Displays a summary of signaling statistics.

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

Release 2.0

This command was introduced.

Release 3.5.0

Support was added for the middles keyword.

Release 3.8.0

The tunnel-name argument was added and the middles keyword was replaced with the mids keyword.

Release 3.9.0

The sample output for the all keyword was modified to display the tunnel signaling statistics for all tunnels that includes the tunnel-mte interface.

Release 4.2.0

The soft-preemption keyword was added.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Task ID

Task ID

Operations

mpls-te

read

Examples

This is a sample output from the show mpls traffic-eng counters signaling command, using the all keyword, which displays tunnel signaling statistics for all tunnels:

RP/0/RP0/CPU0:router# show mpls traffic-eng counters signaling all
             
  
  Tunnel Head: tunnel-te100
  Cumulative Tunnel Counters:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate             1        1      ResvCreate             1        0
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0       18      ResvTear               0        0
       BackupAssign           0        1      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
  
    Destination 100.0.0.4
    Cumulative counters
      Signalling Events      Recv     Xmit                          Recv     Xmit
         PathCreate             1        1      ResvCreate             1        0
         PathChange             0        0      ResvChange             0        0
         PathError              0        0      ResvError              0        0
         PathTear               0       18      ResvTear               0        0
         BackupAssign           0        1      BackupError            0        0
         PathQuery              0        0      Unknown                0        0
      S2L LSP ID: 2 Sub-Grp ID: 0 Destination: 100.0.0.4
        Signalling Events      Recv     Xmit                          Recv     Xmit
           PathCreate             1        1      ResvCreate             1        0
           PathChange             0        0      ResvChange             0        0
           PathError              0        0      ResvError              0        0
           PathTear               0        0      ResvTear               0        0
           BackupAssign           0        1      BackupError            0        0
           PathQuery              0        0      Unknown                0        0
  
  Tunnel Head: tunnel-mte200
  Cumulative Tunnel Counters:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate             2        2      ResvCreate             2        0
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0       20      ResvTear               0        0
       BackupAssign           0        2      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
  
    Destination 100.0.0.4
    Cumulative counters
      Signalling Events      Recv     Xmit                          Recv     Xmit
         PathCreate             2        2      ResvCreate             2        0
         PathChange             0        0      ResvChange             0        0
         PathError              0        0      ResvError              0        0
         PathTear               0       20      ResvTear               0        0
         BackupAssign           0        2      BackupError            0        0
         PathQuery              0        0      Unknown                0        0
      S2L LSP ID: 10021 Sub-Grp ID: 1 Destination: 100.0.0.4
        Signalling Events      Recv     Xmit                          Recv     Xmit
           PathCreate             1        1      ResvCreate             1        0
           PathChange             0        0      ResvChange             0        0
           PathError              0        0      ResvError              0        0
           PathTear               0        0      ResvTear               0        0
           BackupAssign           0        1      BackupError            0        0
           PathQuery              0        0      Unknown                0        0
  
  Tunnel Mid/Tail: router Source: 100.0.0.1 P2MP ID: 1677721603 Tunnel ID: 1 LSP ID: 21
  Cumulative LSP Counters:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate             2        1      ResvCreate             2        1
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0        0      ResvTear               0        0
       BackupAssign           0        0      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
    S2L LSP ID: 21 Sub-Grp ID: 0 Destination: 100.0.0.3
      Signalling Events      Recv     Xmit                          Recv     Xmit
         PathCreate             2        1      ResvCreate             2        1
         PathChange             0        0      ResvChange             0        0
         PathError              0        0      ResvError              0        0
         PathTear               0        0      ResvTear               0        0
         BackupAssign           0        0      BackupError            0        0
         PathQuery              0        0      Unknown                0        0
  
  Tunnel Mid/Tail: router Source: 100.0.0.1 P2MP ID: 1677721603 Tunnel ID: 2 LSP ID: 21
  Cumulative LSP Counters:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate             2        1      ResvCreate             2        1
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0        0      ResvTear               0        0
       BackupAssign           0        0      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
    S2L LSP ID: 21 Sub-Grp ID: 0 Destination: 100.0.0.3
      Signalling Events      Recv     Xmit                          Recv     Xmit
         PathCreate             2        1      ResvCreate             2        1
         PathChange             0        0      ResvChange             0        0
         PathError              0        0      ResvError              0        0
         PathTear               0        0      ResvTear               0        0
         BackupAssign           0        0      BackupError            0        0
         PathQuery              0        0      Unknown                0        0
  
  Tunnel Mid/Tail: router-1_t3 Source: 100.0.0.1 P2MP ID: 1677721603 Tunnel ID: 3 LSP ID: 18
  Cumulative LSP Counters:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate             2        1      ResvCreate             2        1
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0        0      ResvTear               0        0
       BackupAssign           0        0      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
    S2L LSP ID: 18 Sub-Grp ID: 0 Destination: 100.0.0.3
      Signalling Events      Recv     Xmit                          Recv     Xmit
         PathCreate             2        1      ResvCreate             2        1
         PathChange             0        0      ResvChange             0        0
         PathError              0        0      ResvError              0        0
         PathTear               0        0      ResvTear               0        0
         BackupAssign           0        0      BackupError            0        0
         PathQuery              0        0      Unknown                0        0
  
  Tunnel Mid/Tail: router-3_t33 Source: 100.0.0.3 P2MP ID: 1677721605 Tunnel ID: 33 LSP ID: 2
  Cumulative LSP Counters:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate             2        1      ResvCreate             2        1
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0        0      ResvTear               0        0
       BackupAssign           0        0      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
    S2L LSP ID: 2 Sub-Grp ID: 0 Destination: 100.0.0.5
      Signalling Events      Recv     Xmit                          Recv     Xmit
         PathCreate             2        1      ResvCreate             2        1
         PathChange             0        0      ResvChange             0        0
         PathError              0        0      ResvError              0        0
         PathTear               0        0      ResvTear               0        0
         BackupAssign           0        0      BackupError            0        0
         PathQuery              0        0      Unknown                0        0
  
  Signaling Counter Summary:
    Signalling Events      Recv     Xmit                          Recv     Xmit
       PathCreate            11        7      ResvCreate            11        4
       PathChange             0        0      ResvChange             0        0
       PathError              0        0      ResvError              0        0
       PathTear               0       38      ResvTear               0        0
       BackupAssign           0        3      BackupError            0        0
       PathQuery              0        0      Unknown                0        0
  

This is a sample output from the show mpls traffic-eng counters signaling command using the tunnel number argument, which displays statistics for the input tunnel number:

RP/0/RP0/CPU0:router# show mpls traffic-eng counters signaling 200
            
Tunnel Head: tunnel-te200
Cumulative Tunnel Counters:
  Signalling Events  Recv     Xmit                    Recv     Xmit
     PathCreate        4       4      ResvCreate        4       0
     PathChange        0       0      ResvChange        0       0
     PathError         0       0      ResvError         0       0
     PathTear          0       1      ResvTear          0       0
     BackupAssign      0       4      BackupError       0       0
     PathQuery         0       0      Unknown           0       0
 
  Destination 3.3.3.3
  Cumulative counters
    Signalling Events Recv     Xmit                    Recv    Xmit
       PathCreate      4        4      ResvCreate       4       0
       PathChange      0        0      ResvChange       0       0
       PathError       0        0      ResvError        0       0
       PathTear        0        1      ResvTear         0       0
       BackupAssign    0        4      BackupError      0       0
       PathQuery       0        0      Unknown          0       0
  S2L LSP ID: 3 Sub-Grp ID: 0 Destination: 3.3.3.3
    Signalling Events Recv     Xmit                    Recv    Xmit
       PathCreate       3       3      ResvCreate       3       0
       PathChange       0       0      ResvChange       0       0
       PathError        0       0      ResvError        0       0
       PathTear         0       0      ResvTear         0       0
       BackupAssign     0       3      BackupError      0       0
       PathQuery        0       0      Unknown          0       0

This table describes the significant fields shown in the display.



Table 5 show mpls traffic-eng counters signaling Command Field Descriptions

Field

Description

Tunnel Head

Tunnel head identifier.

Match Resv Create

Number of RSVP Reservation create messages received.

Sender Create

Number of Sender Create messages sent by TE to RSVP.

Path Error

Number of RSVP Path Error messages received.

Match Resv Change

Number of RSVP Reservation change messages received.

Sender Modify

Number of Sender Modify messages sent by TE to RSVP.

Path Change

Number of RSVP Path Change messages received.

Match Resv Delete

Number of RSVP Reservation delete messages received.

Sender Delete

Number of Sender Delete messages sent by TE to RSVP.

Path Delete

Number of RSVP Path Delete messages received.

Total

Total signaling messages received from RSVP.

Unknown

Unknown messages include fast reroute events and internal messages related to process restart.

This is sample output from the show mpls traffic-eng counters soft-preemption command, which displays statistics for the soft preempted LSPs:

RP/0/RP0/CPU0:routershow mpls traffic-eng counters soft-preemption

Soft Preemption Global Counters:
 Last Cleared: Never
 Preemption Node Stats:
   Number of soft preemption events: 1
   Number of soft preempted LSPs: 1
   Number of soft preempted LSPs that timed out: 0
   Number of soft preempted LSPs that were torn down: 0
   Number of soft preempted LSPs that were fast rerouted: 0
   Minimum Time in Soft Preemption Pending State (sec): 0
   Maximum Time in Soft Preemption Pending State (sec): 0
   Average Time in Soft Preemption Pending State (sec): 0
 Headend Stats:
   Number of soft preempted LSPs: 1
   Number of reoptimized soft preempted headend-LSPs: 0
   Number of path protected switchover soft preempted headend-LSPs: 0
   Number of torn down soft preempted headend-LSPs: 0

Related Commands

Command

Description

clear mpls traffic-eng counters signaling

Clears the counters for MPLS-TE tunnels.

clear mpls traffic-eng fast-reroute log

Clears the counters for MPLS-TE tunnels.

soft-preemption

Enables soft-preemption on a head-end for the MPLS TE tunnel.

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 show mpls traffic-eng ds-te te-class

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.3.0

This command was introduced.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.


Note


TE-class is used only in IETF DS-TE mode.


Task ID

Task ID

Operations