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.

Command Default

percentage: 5

minimum bandwidth: 10

Command Modes

MPLS-TE automatic bandwidth interface configuration

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.

Related Commands

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.

Command Default

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

Command Modes

MPLS-TE interface configuration

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.

Related Commands

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.

Command Default

affinity-value: 0X00000000

mask-value: 0x0000FFFF

Command Modes

Interface configuration

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.

If there is an affinity failure, a 5 minute timer is started at the LSP headend. If the tunnel is not able to reoptimize within the time frame, it is torn down. However, if you execute the mpls traffic-eng reoptimize disable affinity-failure command, no timer is started and the tunnel is not torn down. Note that, at a subsequent time, other triggers for reoptimization may start the timer for the LSPs with affinity failure.

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

Specifies that a link is considered for constrained shortest path first (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

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

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

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.

Ignore

Ignores affinity attributes while considering links for CSPF.

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.

Related Commands

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.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

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.

Repeat the affinity-map command to define multiple colors up to a maximum of 256 colors.

Related Commands

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.

Command Default

minutes : 1440 (24 hours)

Command Modes

MPLS-TE automatic bandwidth interface configuration

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.

Related Commands

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.

Command Default

attributes : 0x0

Command Modes

MPLS-TE interface configuration

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.

Related Commands

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.

Command Default

No default behavior or values

Command Modes

MPLS-TE interface configuration

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

Related Commands

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

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

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

To specify an attribute set for LSP diversity for GMPLS UNI, use the attribute-set command in MPLS-TE configuration mode.

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

Command Default

affinity-value: 0x0

mask-value: 0xFFFF

Command Modes

MPLS TE configuration

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.

Related Commands

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.

Syntax Description

This command has no arguments or keywords.

Command Default

By default, automatic bandwidth is not enabled.

Command Modes

MPLS-TE interface configuration

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

Related Commands

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.

Command Default

minutes: 5

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

Command Modes

MPLS-TE configuration

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.

Related Commands

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.

Command Default

Announces IPv4 tunnel

Command Modes

Interface configuration

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 more than one IGP is configured, the tunnel is announced as autoroute to the IGP that is used to compute the TE tunnel path.

When the autoroute announce command is configured, the route metric of the tunnel path to the destination equals the route metric of the shortest IGP path to that destination.

The autoroute announce metric configuration overrides the autoroute metric configuration, if present.

Note	IS-IS is the only IGP supporting ipv6 MPLS-TE tunnel announcements.

Related Commands

To install multiple static routes in the routing information base (RIB) per MPLS TE tunnel, use the autoroute destination command in interface TE tunnel configuration mode. To disable autoroute destination, use the no form of this command.

Command Default

Autoroute destination is disabled.

Command Modes

Interface Tunnel TE

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 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. If no specific metric is to be specified, use the no form of this command.

Command Default

The relative value is 0.

Command Modes

Interface configuration

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.

Note	The autoroute announce configuration overrides the autoroute metric configuration, if present.

Related Commands

To enable auto-tunnel stateful PCE client configuration mode, use the auto-tunnel pcc command in MPLS TE configuration mode. To disable auto-tunnel stateful PCE client configuration, use the no form of this command.

This command has no keywords or arguments.

Command Default

Auto-tunnel stateful PCE client mode is disabled.

Command Modes

MPLS TE configuration

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

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

MPLS-TE configuration

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.

Related Commands

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.

Command Default

Any class-type unlimited.

Command Modes

Interface configuration

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

Related Commands

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.

Command Default

No default behavior or values

Command Modes

MPLS-TE interface configuration

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.

Related Commands

To configure a bidirectional LSP for a MPLS TE tunnel and define other parameters for the LSP, use the bidirectional command in the MPLS-TE interface configuration mode.

Command Default

Tunnel interfaces are disabled.

Command Modes

Interface configuration mode

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

Command Default

min: 0

max: 4294967295

Command Modes

MPLS-TE automatic bandwidth interface configuration

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.

Related Commands

To enable stateful PCE capabilities, use the capabilities command in MPLS-TE stateful PCE configuration mode. To disable the stateful PCE capabilities, use the no form of this command.

Command Default

Stateful PCE capabilities are disabled.

Command Modes

MPLS-TE Stateful PCE

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 stateful-client configuration is added to the node, it will close all existing PCEP peer connections, and add the stateful capabilities TLV to the OPEN object it exchanges during PCEP session establishment.

When the stateful-client configuration is removed from the node, it will delete all PCE instantiated tunnels, close all existing PCEP connections, and no longer add the stateful capabilities TLV to the OPEN object it exchanges during PCEP session establishment.

To clear Link Management Protocol (LMP) management hello settings, use the clear mpls lmpcommand in EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

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.

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.

Command Default

No default behavior or values

Command Modes

EXEC

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.

Related Commands

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

Command Default

No default behavior or values

Command Modes

EXEC

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.

Related Commands

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

Command Default

None

Command Modes

EXEC

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 clear all auto-tunnel mesh counters, use the clear mpls traffic-eng counters auto-tunnel mesh command in EXEC mode.

This command has no arguments or keywords.

Command Default

None

Command Modes

EXEC

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 clear MPLS-TE automatic tunnel backup counters, use the clear mpls traffic-eng counters auto-tunnel backup command in EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

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.

Related Commands

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

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

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 clear (set to zero) the MPLS tunnel signaling counters, use the clear mpls traffic-eng counters signaling command in EXEC mode.

Command Default

No default behavior or values

Command Modes

EXEC

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.

Related Commands

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

Command Default

None

Command Modes

EXEC

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.

Related Commands

To clear the log of MPLS fast reroute (FRR) events, use the clear mpls traffic-eng fast-reroute log command in EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

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 clear all the MPLS-TE admission control statistics, use the clear mpls traffic-eng link-management statistics command in EXEC mode.

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

EXEC

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 clear the path computation element (PCE) statistics, use the clear mpls traffic-eng pce command in EXEC mode.

Command Default

Clears statistics for all the PCE peers.

Command Modes

EXEC

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.

Related Commands

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.

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

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.

Related Commands

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.

Command Default

No default behavior or values

Command Modes

Interface configuration

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.

Related Commands

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.

Command Default

Default is unidirectional.

Command Modes

Interface tunnel-gte configuration

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.

Related Commands

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.

Syntax Description

This command has no arguments or keywords.

Command Default

Explicit path is enabled.

Command Modes

Explicit path configuration

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.

Related Commands

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.

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

P2MP destination interface configuration

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.

Related Commands

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.

Command Default

RDM is the default bandwidth constraint model.

Command Modes

MPLS-TE configuration

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.

Related Commands

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.

Command Default

Prestandard DS-TE is the default differentiated service mode.

Command Modes

MPLS-TE configuration

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.

Related Commands

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.

Command Default

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

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

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.

Related Commands

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.

Command Default

Strict SRLG

Command Modes

Auto-tunnel backup configuration

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.

Related Commands

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.

Syntax Description

This command has no arguments or keywords.

Command Default

FRR is disabled.

Command Modes

Interface configuration

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.

Related Commands

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.

Command Default

FRR is disabled.

Command Modes

Interface configuration

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.

Related Commands

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.

Command Default

interval: 300

Command Modes

MPLS-TE configuration

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.

Related Commands

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.

Command Default

No default behavior or values

Command Modes

MPLS-TE interface configuration

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.