Table Of Contents
mpls traffic-eng administrative-weight
mpls traffic-eng atm cos global-pool
mpls traffic-eng atm cos sub-pool
mpls traffic-eng attribute-flags
mpls traffic-eng auto-bw timers
mpls traffic-eng auto-tunnel backup
mpls traffic-eng auto-tunnel backup config
mpls traffic-eng auto-tunnel backup config affinity
mpls traffic-eng auto-tunnel backup nhop-only
mpls traffic-eng auto-tunnel backup srlg exclude
mpls traffic-eng auto-tunnel backup timers
mpls traffic-eng auto-tunnel backup tunnel-num
mpls traffic-eng auto-tunnel mesh
mpls traffic-eng auto-tunnel mesh tunnel-num
mpls traffic-eng auto-tunnel primary config
mpls traffic-eng auto-tunnel primary config mpls ip
mpls traffic-eng auto-tunnel primary onehop
mpls traffic-eng auto-tunnel primary timers
mpls traffic-eng auto-tunnel primary tunnel-num
mpls traffic-eng backup-path tunnel
mpls traffic-eng ds-te bc-model
mpls traffic-eng fast-reroute backup-prot-preemption
mpls traffic-eng fast-reroute promote
mpls traffic-eng fast-reroute timers
mpls traffic-eng flooding thresholds
mpls traffic-eng link timers bandwidth-hold
mpls traffic-eng link timers periodic-flooding
mpls traffic-eng link-management timers bandwidth-hold
mpls traffic-eng link-management timers periodic-flooding
mpls traffic-eng logging tunnel
mpls static binding ipv4 vrf
To bind a prefix to a local label, use the mpls static binding ipv4 vrf command in global configuration mode. To remove static binding between the prefix and label, use the no form of this command.
mpls static binding ipv4 vrf vpn-name prefix mask {input label | label}
no mpls static binding ipv4 vrf vpn-name prefix mask [input label | label]
Syntax Description
Command Default
Label bindings are dynamically assigned.
Command Modes
Global configuration
Command History
Usage Guidelines
The mpls static binding ipv4 vrf command is used only when you configure input labels.
Depending on how you configure the MPLS LDP VRF-Aware Static Labels feature, static labels are advertised one of the following ways:
•By Label Distribution Protocol (LDP) between provider edge (PE) and customer edge (CE) routers within a VRF instance.
•In VPNv4 Border Gateway Protocol (BGP) in the service provider's backbone.
If you do not specify the input keyword, an input (local) label is assumed.
The no form of the command functions as follows:
•Omitting the prefix and the subsequent parameters removes all static bindings.
•Specifying the prefix and mask but no label parameters removes all static bindings for that prefix or mask.
Examples
The following example binds a prefix to local label 17:
Router(config)# mpls static binding ipv4 vrf vpn100 10.66.0.0 255.255.0.0 input 17Related Commands
mpls static crossconnect
To configure a Label Forwarding Information Base (LFIB) entry for the specified incoming label and outgoing interface, use the mpls static crossconnect command in global configuration mode. To remove the LFIB entry, use the no form of this command.
mpls static crossconnect inlabel out-interface nexthop {outlabel | explicit-null | implicit-null}
no mpls static crossconnect inlabel out-interface nexthop {outlabel | explicit-null | implicit-null}
Syntax Description
Command Default
Cross connects are not created.
Command Modes
Global configuration
Command History
Usage Guidelines
You must specify the nexthop address for multiaccess interfaces.
Examples
In the following example, the mpls static crossconnect command configures a cross connect from incoming label 45 to outgoing label 46 through POS interface POS5/0:
Router(config)# mpls static crossconnect 45 pos5/0 46
Related Commands
mpls tp
To configure Multiprotocol Label Switching (MPLS) transport profile (TP) parameters and enter MPLS-TP configuration mode, use the mpls tp command in global configuration mode. To remove all MPLS-TP forwarding, use the no form of this command.
mpls tp
no mpls tp
Syntax Description
This command has no arguments or keywords.
Command Default
No MPLS-TP parameters are configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command to enter MPLS-TP configuration mode. From that mode, you can configure the following parameters:
Examples
The following example shows how to enter MPLS-TP configuration mode and set the default router ID:
Router(config)# mpls tpRouter(config-mpls-tp)# router-id 10.10.10.10
Router(config-mpls-tp)# exitRelated Commands
Command Descriptionmpls tp lsp
Specifies the parameters for two ends of the MPLS-TP tunnel from the tunnel midpoint.
interface tunnel-tp
Specifies the parameters for the MPLS tunnel.
mpls tp link
To configure Multiprotocol Label Switching (MPLS) transport profile (TP) link parameters, use the mpls tp link command in interface configuration mode.
mpls tp link link-num {ipv4 ip-address | tx-mac mac-address} rx-mac mac-address
no mpls tp link link-num
Syntax Description
Command Default
No MPLS-TP link parameters are configured.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The link number must be unique on the device. Only one link number can be assigned per interface.
MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual interfaces are not supported for MPLS-TP link numbers.
When an MPLS-TP link is configured without an IP address on an Ethernet interface, Cisco uses an IEEE Bridge Group MAC address (0180.c200.0000) for communication by default.
Examples
This example creates an MPLS-TP link without an IP address:
interface e0/0medium p2pmpls tp link 1This example configures the unicast MAC address of the next-hop device:
interface e0/0medium p2pmpls tp link 1 tx-mac 0000.0c00.1234This example configures transmit and receive parameters for a different multicast address:
interface e0/0medium p2pmpls tp link 1 tx-mac 0100.0c99.8877 rx-mac 0100.0c99.8877This example configures a link with an IP adress:
interface e0/0ip address 10.0.0.1 255.255.255.0mpls tp link 1 ipv4 10.0.0.2Related Commands
Command Descriptionmpls tp lsp
Specifies the parameters for forwarding of a MPLS-TP LSP at the tunnel midpoint.
interface tunnel-tp
Specifies the parameters for the MPLS tunnel.
mpls tp lsp
To configure Multiprotocol Label Switching (MPLS) transport profile (TP) midpoint connectivity, use the mpls tp lsp command in global configuration mode.
mpls tp lsp source node-id [global-id num] tunnel-tp num lsp {lsp-num | protect | working} destination node-id [global-id num] tunnel-tp num
Syntax Description
Command Default
No MPLS-TP parameters are configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command on midpoint routers to specify the source and destination parameters of the MPLS-TP tunnel. You can use the mpls trace command from the MPLS-TP endpoint to validate that traffic is traversing the correct tunnel at each midpoint.
This command also enters MPLS-TP LSP configuration mode (config-mpls-tp-lsp). From that mode, you can configure the following parameters:
Examples
The following examples show the configuration of an MPLS-TP LSP midpoint.
The following example configures a midpoint LSP carrying the working LSP of an MPLS-TP tunnel between node 10.10.10.10, tunnel-number 1 and 10.11.11.11, tunnel-number 2, using 1000 kbits/sec bandwidth in both directions:
Router(config)# mpls tp lsp source 10.10.10.10 tunnel-tp 1 lsp working destination 10.11.11.11 tunnel-tp 2Router(config-mpls-tp-lsp)# forward-lspRouter(config-mpls-tp-lsp-forw)# bandwidth 1000Router(config-mpls-tp-lsp-forw)# in-label 20 out-label 40 out-link 10Router(config-mpls-tp-lsp-forw)# exitRouter(config-mpls-tp-lsp)# reverse-lspRouter(config-mpls-tp-lsp-rev)# bandwidth 1000Router(config-mpls-tp-lsp-rev)# in-label 21 out-label 50 out-link 11The following example configures a midpoint LSP on the protect LSP between node 10.10.10.10, tunnel 4 and 10.11.11.11, tunnel 12. No bandwidth is reserved:
Router(config)# mpls tp lsp source 10.10.10.10 global-id 2 tunnel-tp 4 lsp protect destination 10.11.11.11 global-id 14 tunnel-tp 12Router(config-mpls-tp-lsp)# forward-lspRouter(config-mpls-tp-lsp-forw)# in-label 30 out-label 100 out-link 27Router(config-mpls-tp-lsp-forw)# exitRouter(config-mpls-tp-lsp)# reverse-lspRouter(config-mpls-tp-lsp-rev)# in-label 31 out-label 633 out-link 30Related Commands
mpls traffic-eng
To configure a router running Intermediate System-to-Intermediate System (IS-IS) so that it floods Multiprotocol Label Switching (MPLS) traffic engineering (TE) link information into the indicated IS-IS level, use the mpls traffic-eng command in router configuration mode. To disable the flooding of MPLS TE link information into the indicated IS-IS level, use the no form of this command.
mpls traffic-eng {level-1 | level-2}
no mpls traffic-eng {level-1 | level-2}
Syntax Description
level-1
Floods MPLS TE link information into IS-IS level 1.
level-2
Floods MPLS TE link information into IS-IS level 2.
Command Default
Flooding is disabled.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
This command, which is part of the routing protocol tree, causes link resource information (such as available bandwidth) for appropriately configured links to be flooded in the IS-IS link-state database.
Examples
The following example shows how to configure MPLS TE link information flooding for IS-IS level 1:
Router(config-router)# mpls traffic-eng level-1Related Commands
Command Descriptionmpls traffic-eng router-id
Specifies that the traffic engineering router identifier for the node is the IP address associated with a given interface.
mpls traffic-eng administrative-weight
To override the Interior Gateway Protocol (IGP) administrative weight (cost) of the link, use the mpls traffic-eng administrative-weight command in interface configuration mode. To disable the override, use the no form of this command.
mpls traffic-eng administrative-weight weight
no mpls traffic-eng administrative-weight
Syntax Description
Command Default
None
Command Modes
Interface configuration (config-if)
Command History
Examples
The following example shows how to override the IGP cost of the link and set the cost to 20:
Router(config-if)# mpls traffic-eng administrative-weight 20Related Commands
Command Descriptionmpls traffic-eng attribute-flags
Sets the user-specified attribute flags for an interface.
mpls traffic-eng area
To configure a router running Open Shortest Path First (OSPF) Multiprotocol Label Switching (MPLS) so that it floods traffic engineering for the indicated OSPF area, use the mpls traffic-eng area command in router configuration mode. To disable flooding of traffic engineering for the indicated OSPF area, use the no form of this command.
mpls traffic-eng area number
no mpls traffic-eng area number
Syntax Description
Defaults
Flooding is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
This command is in the routing protocol configuration tree and is supported for both OSPF and IS-IS. The command affects the operation of MPLS traffic engineering only if MPLS traffic engineering is enabled for that routing protocol instance. Currently, only a single level can be enabled for traffic engineering.
Examples
The following example shows how to configure a router running OSPF MPLS to flood traffic engineering for OSPF 0:
Router(config-router)# mpls traffic-eng area 0Related Commands
mpls traffic-eng atm cos global-pool
Note Effective with Cisco IOS Release 12.4(20)T, the mpls traffic-eng atm cos global-pool command is not available in Cisco IOS software.
To specify the class of service for all global pools in traffic engineering tunnels traversing XTagATM interfaces on an ATM-label switch router (LSR), use the mpls traffic-eng atm cos global-pool command in global configuration mode.
mpls traffic-eng atm cos global-pool [available | standard | premium | control]
Syntax Description
available | standard | premium | control
(Optional) Four classes of service, ordered from lowest priority (available) to highest priority (control). The default is available.
Defaults
The default class is the lowest, available.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Because this command works at the global rather than at the interface level, it sets the same class of service for global pool traffic engineering (TE) tunnel traffic on all XTagATM interfaces of the device.
Examples
The following example shows how to specify the second-lowest possible priority class of service for the global pool traffic:
Router(config)# mpls traffic-eng atm cos global-pool standardRelated Commands
Command Descriptionmpls traffic-eng atm cos sub-pool
Specifies class of service for subpool traffic traversing XtagATM interfaces.
mpls traffic-eng atm cos sub-pool
Note Effective with Cisco IOS Release 12.4(20)T, the mpls traffic-eng atm cos sub-pool command is not available in Cisco IOS software.
To specify the class of service for all subpools in traffic engineering tunnels traversing XTagATM interfaces on an ATM-label switch router (LSR), use the mpls traffic-eng atm cos sub-pool command in global configuration mode.
mpls traffic-eng atm cos sub-pool [available | standard | premium | control]
Syntax Description
available | standard | premium | control
Four classes of service, ordered from lowest priority (available) to highest priority (control). The default is control.
Defaults
The default class is the highest, control.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Because this command works at the global rather than at the interface level, it sets the same class of service for subpool traffic engineering (TE) tunnel traffic on all XTagATM interfaces of the device.
Examples
The following example shows how to specify the second-highest possible priority class of service for the subpool traffic:
Router(config)# mpls traffic-eng atm cos sub-pool premiumRelated Commands
Command Descriptionmpls traffic-eng atm cos global-pool
Specifies class of service for global-pool traffic traversing XTagATM interfaces.
mpls traffic-eng attribute-flags
To set the user-specified attribute flags for the interface, use the mpls traffic-eng attribute-flags command in interface configuration mode. To disable the user-specified attribute flags for the interface, use the no form of this command.
mpls traffic-eng attribute-flags attributes
no mpls traffic-eng attribute-flags
Syntax Description
Command Default
None
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command assigns attributes to a link so that tunnels with matching attributes (represented by their affinity bits) prefer this link to others that do not match. The interface is flooded globally so that it can be used as a tunnel head-end path selection criterion.
Examples
The following example shows how to set the attribute flags to 0x0101:
Router(config-if)# mpls traffic-eng attribute-flags 0x0101Related Commands
mpls traffic-eng auto-bw timers
To enable automatic bandwidth adjustment for a platform and to start output rate sampling for tunnels configured for automatic bandwidth adjustment, use the mpls traffic-eng auto-bw timers command in global configuration mode. To disable automatic bandwidth adjustment for the platform, use the no form of this command.
mpls traffic-eng auto-bw timers [frequency seconds]
no mpls traffic-eng auto-bw timers
Syntax Description
Command Default
When the optional frequency keyword is not specified, the sampling interval is 300 seconds (5 minutes).
Command Modes
Global configuration
Command History
Usage Guidelines
The mpls traffic-eng auto-bw timers command enables automatic bandwidth adjustment on a platform by causing traffic engineering to periodically sample the output rate for each tunnel configured for bandwidth adjustment.
The no mpls traffic-eng auto-bw timers command disables automatic bandwidth adjustment for a platform by terminating the output rate sampling and bandwidth adjustment for tunnels configured for adjustment. In addition, the no form of the command restores the configured bandwidth for each tunnel where "configured bandwidth" is determined as follows:
•If the tunnel bandwidth was explicitly configured via the tunnel mpls traffic-eng bandwidth command after the running configuration was written (if at all) to the startup configuration, the "configured bandwidth" is the bandwidth specified by that command.
•Otherwise, the "configured bandwidth" is the bandwidth specified for the tunnel in the startup configuration.
Examples
The following example shows how to designate that for each Multiprotocol Label Switching (MPLS) traffic engineering tunnel, the output rate is sampled once every 10 minutes (every 600 seconds):
Router(config)# mpls traffic-eng auto-bw timers frequency 600Related Commands
mpls traffic-eng auto-tunnel backup
To automatically build next-hop (NHOP) and next-next hop (NNHOP) backup tunnels, use the mpls traffic-eng auto-tunnel backup command in global configuration mode. To delete the NHOP and NNHOP backup tunnels, use the no form of this command.
mpls traffic-eng auto-tunnel backup
no mpls traffic-eng auto-tunnel backup
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Global configuration
Command History
Usage Guidelines
The no form of this command deletes both NHOP and NNHOP backup tunnels that were configured using either the mpls traffic-eng auto-tunnel backup command or the mpls traffic-eng auto-tunnel backup nhop-only command.
Examples
The following example automatically builds NHOP and NNHOP backup tunnels:
Router# mpls traffic-eng auto-tunnel backupRelated Commands
mpls traffic-eng auto-tunnel backup config
To configure a specific unnumbered interface for all backup auto-tunnels, use the mpls traffic-eng auto-tunnel backup config command in global configuration mode. To remove the specific interface and resume the default interface for all backup auto-tunnels, use the no form of this command.
mpls traffic-eng auto-tunnel backup config unnumbered-interface interface
no mpls traffic-eng auto-tunnel backup config unnumbered-interface
Syntax Description
Command Default
Loopback0
Command Modes
Global configuration
Command History
Usage Guidelines
In Cisco IOS Release 15.1(1)S, this command changed so that you do not need to specific the interface name when you specify the no form of this command. In release prior to 15.1(1)S, you had to specify the interface name as part of the no form of the command. If you upgrade to Cisco IOS Release 15.1(1)S, check that your configuration does not contain the interface name as part of the no mpls traffic-eng auto-tunnel backup config command.
Examples
The following example assigns interface Ethernet 1/0 to all backup auto-tunnels:
Router# mpls traffic-eng auto-tunnel backup config unnumbered-interface ethernet1/0The following example assigns the default interface of loopback0 to all backup auto-tunnels:
Router# no mpls traffic-eng auto-tunnel backup config unnumbered-interface
Related Commands
mpls traffic-eng auto-tunnel backup config affinity
To specify an affinity on dynamically created Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) backup tunnels, use the mpls traffic-eng auto-tunnel backup config affinity command in global configuration mode. To return to the default values, use the no form of the command.
mpls traffic-eng auto-tunnel backup config affinity affinity-value [mask mask-value]
no mpls traffic-eng auto-tunnel backup config affinity
Syntax Description
Command Default
Affinity: 0x0
mask: 0xFFFFCommand Modes
Global configuration
Command History
Usage Guidelines
This command is used with the mpls traffic-eng attribute-flags command, which specifies attributes for a link so that tunnels with matching affinity bits will use that link.
With the autotunnel backup feature, you can use the mpls traffic-eng attribute-flags and mpls traffic-eng auto-tunnel backup config affinity commands to include or exclude links when calculating a path for a dynamically created backup tunnel.
The affinity determines the attributes of the links that this tunnel will use (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, an attribute value of a link or that bit is irrelevant. If a bit in the mask is 1, the attribute value of a link and the required affinity of the tunnel for that bit must match.
A tunnel can use a link if:
tunnel affinity = the link attributes && the tunnel affinity maskAny properties set to 1 in the affinity should also be 1 in the mask.
Examples
The following example configures all dynamically created backup with affinity 0x22, mask 0x22:
Router (config)# mpls traffic-eng auto-tunnel backup config affinity 0x22 mask 0x22Related Commands
mpls traffic-eng auto-tunnel backup nhop-only
To automatically build next-hop (NHOP) backup tunnels, use the mpls traffic-eng auto-tunnel backup nhop-only command in global configuration mode. To delete the NHOP backup tunnels, use the no form of this command.
mpls traffic-eng auto-tunnel backup nhop-only
no mpls traffic-eng auto-tunnel backup nhop-only
Syntax Description
This command has no arguments or keywords.
Command Default
The dynamically created backup tunnel uses Loopback0.
Command Modes
Global configuration
Command History
Usage Guidelines
This command permits the creation of only NHOP backup tunnels; next-next hop (NNHOP) backup tunnels are not created. The no form of this command deletes only the NHOP backup tunnels; NNHOP backup tunnels are not deleted.
Examples
The following example enables the creation of only dynamic NHOP backup tunnels:
Router# mpls traffic-eng auto-tunnel backup nhop-onlyRelated Commands
mpls traffic-eng auto-tunnel backup srlg exclude
To specify that autocreated backup tunnels should avoid Shared Risk Link Groups (SRLGs) of the protected interface, use the mpls traffic-eng auto-tunnel backup srlg exclude command in global configuration mode. To disable this feature, use the no form of this command.
mpls traffic-eng auto-tunnel backup srlg exclude [force | preferred]
no mpls traffic-eng auto-tunnel backup srlg exclude [force | preferred]
Syntax Description
Command Default
Autocreated backup tunnels are created without regard to SRLGs.
Command Modes
Global configuration (config)
Command History
Release Modification12.0(28)S
This command was introduced.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
If you enter the command with either the force or preferred keyword and then reenter the command with the other keyword, only the last command entered is effective.
Examples
In the following example, backup tunnels must avoid SRLGs of the protected interface:
Router# configure terminalRouter(config)# mpls traffic-eng auto-tunnel backup srlg exclude forceIn the following example, backup tunnels should try to avoid SRLGs of the protected interface:
Router# configure terminalRouter(config)# mpls traffic-eng auto-tunnel backup srlg exclude preferredRelated Commands
mpls traffic-eng auto-tunnel backup timers
To configure how frequently a timer will scan backup autotunnels and remove tunnels that are not being used, use the mpls traffic-eng auto-tunnel backup timers command in global configuration mode. To disable this configuration, use the no form of this command.
mpls traffic-eng auto-tunnel backup timers removal unused [sec]
no mpls traffic-eng auto-tunnel backup timers removal unused [sec]
Syntax Description
removal unused [sec]
Configures how frequently (in seconds) a timer will scan the backup autotunnels and remove tunnels that are not being used. Valid values are 0 to 604,800.
Command Default
The timer scans backup autotunnels and removes tunnels that are not being used every 3600 seconds (60 minutes).
Command Modes
Global configuration
Command History
Examples
The following example shows that a timer will scan backup autotunnels every 80 seconds and remove tunnels that are not being used:
Router# mpls traffic-eng auto-tunnel backup timers removal unused 80
Related Commands
mpls traffic-eng auto-tunnel backup tunnel-num
To configure the range of tunnel interface numbers for backup autotunnels, use the mpls traffic-eng auto-tunnel backup tunnel-num command in global configuration mode. To disable this configuration, use the no form of this command.
mpls traffic-eng auto-tunnel backup tunnel-num [min num] [max num]
no mpls traffic-eng auto-tunnel backup tunnel-num [min num] [max num]
Syntax Description
Command Default
None
Command Modes
Global configuration
Command History
Examples
The following example configures the range of backup autotunnel numbers to be between 1000 and 1100:
Router# mpls traffic-eng auto-tunnel backup tunnel-num min 1000 max 1100Related Commands
mpls traffic-eng auto-tunnel mesh
To enable autotunnel mesh groups globally, use the mpls traffic-eng auto-tunnel mesh command in global configuration mode. To disable autotunnel mesh groups globally, use the no form of this command.
mpls traffic-eng auto-tunnel mesh
no mpls traffic-eng auto-tunnel mesh
Syntax Description
This command has no arguments or keywords.
Command Default
Autotunnel mesh groups are not enabled globally.
Command Modes
Global configuration (config)#
Command History
Examples
The following example shows how to enable autotunnel mesh groups globally:
Router(config)# mpls traffic-eng auto-tunnel meshRelated Commands
mpls traffic-eng auto-tunnel mesh tunnel-num
To configure a range of mesh tunnel interface numbers, use the mpls traffic-eng auto-tunnel mesh tunnel-num command in global configuration mode. To use the default values, use the no form of this command.
mpls traffic-eng auto-tunnel mesh tunnel-num min num max num
no mpls traffic-eng auto-tunnel mesh tunnel-num
Syntax Description
Command Default
The min default is 64336. The max default is 65335.
Command Modes
Global configuration (config)#
Command History
Usage Guidelines
If you change an access control list (ACL) and tunnels are deleted because they no longer match the ACL, tunnels that are re-created might not be numbered sequentially; that is, the range of tunnel numbers might not be sequential.
Examples
The following example shows how to specify 1000 as the beginning number of the mesh tunnel interface and 2000 as the ending number:
Router(config)# mpls traffic-eng auto-tunnel mesh tunnel-num min 1000 max 2000Related Commands
Command Descriptionshow mpls traffic-eng auto-tunnel mesh
Displays the cloned mesh tunnel interfaces of each autotemplate interface and the current range of mesh tunnel interface numbers.
mpls traffic-eng auto-tunnel primary config
To enable IP processing without an explicit address, use the mpls traffic-eng auto-tunnel primary config command in global configuration mode. To disable this capability, use the no form of this command.
mpls traffic-eng auto-tunnel primary config unnumbered interface
no mpls traffic-eng auto-tunnel primary config unnumbered interface
Syntax Description
Command Default
Loopback0
Command Modes
Global configuration
Command History
Examples
The following example enables IP processing on an Ethernet interface:
Router# mpls traffic-eng auto-tunnel primary config unnumbered ethernet1/0Related Commands
mpls traffic-eng auto-tunnel primary config mpls ip
To enable Label Distribution Protocol (LDP) on primary autotunnels, use the mpls traffic-eng auto-tunnel primary config mpls ip command in global configuration mode. To disable LDP on primary autotunnels, use the no form of this command.
mpls traffic-eng auto-tunnel primary config mpls ip
no mpls traffic-eng auto-tunnel primary config mpls ip
Syntax Description
This command has no arguments or keywords.
Command Default
LDP is not enabled.
Command Modes
Global configuration
Command History
Examples
The following example enables LDP on primary autotunnels:
Router# mpls traffic-eng auto-tunnel primary config mpls ipRelated Commands
mpls traffic-eng auto-tunnel primary onehop
To automatically create primary tunnels to all next hops, use the mpls traffic-eng auto-tunnel primary onehop command in global configuration mode. To disable the automatic creation of primary tunnels to all next hops, use the no form of this command.
mpls traffic-eng auto-tunnel primary onehop
no mpls traffic-eng auto-tunnel primary onehop
Syntax Description
This command has no arguments or keywords.
Command Default
The dynamically created one-hop tunnels use Loopback0.
Command Modes
Global configuration
Command History
Examples
The following example automatically creates primary tunnels to all next hops:
Router# mpls traffic-eng auto-tunnel primary onehopRelated Commands
mpls traffic-eng auto-tunnel primary timers
To configure how many seconds after a failure primary autotunnels are removed, use the mpls traffic-eng auto-tunnel primary timers command in global configuration mode. To disable this configuration, use the no form of this command.
mpls traffic-eng auto-tunnel primary timers removal rerouted sec
no mpls traffic-eng auto-tunnel primary timers removal rerouted sec
Syntax Description
removal rerouted sec
Number of seconds after a failure that primary autotunnels are removed. Valid values are 30 to 604,800. Default: 0.
Command Default
None
Command Modes
Global configuration
Command History
Examples
The following example shows that primary autotunnels are removed 100 seconds after a failure:
Router# mpls traffic-eng auto-tunnel primary timers removal rerouted 100Related Commands
mpls traffic-eng auto-tunnel primary tunnel-num
To configure the range of tunnel interface numbers for primary autotunnels, use the mpls traffic-eng auto-tunnel primary tunnel-num command in global configuration mode. To disable this configuration, use the no form of this command.
mpls traffic-eng auto-tunnel primary tunnel-num [min num] [max num]
no mpls traffic-eng auto-tunnel primary tunnel-num [min num] [max num]
Syntax Description
Command Default
None
Command Modes
Global configuration
Command History
Examples
The following example shows that the primary tunnel numbers can be between 2000 and 2100:
Router# mpls traffic-eng auto-tunnel primary tunnel-num min 2000 max 2100Related Commands
mpls traffic-eng backup-path
To assign one or more backup tunnels to a protected interface, use the mpls traffic-eng backup-path command in interface configuration mode.
mpls traffic-eng backup-path tunneltunnel-id
Syntax Description
Command Default
No backup tunnels are used if this interface goes down.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enter this command on the interface to be protected (Link Protection), or on the interface whose downstream node is being protected (Node Protection). You can enter this command multiple times to select multiple backup tunnels for a given protected interface. An unlimited number of backup tunnels can be assigned to protect an interface. The only limitation is memory. By entering this command on a physical interface, LSPs using this interface (sending data out of this interface) can use the indicated backup tunnels if there is a link or node failure.
Examples
The following example assigns backup tunnel 34 to interface POS5/0:
Router(config)# interface pos5/0Router(config-if)# mpls traffic-eng backup-path tunnel34Related Commands
Command Descriptiontunnel mpls traffic-eng fast-reroute
Enables an MPLS traffic engineering tunnel to use a backup tunnel if there is a link or node failure (provided that a backup tunnel exists).
mpls traffic-eng backup-path tunnel
To configure the physical interface to use a backup tunnel in the event of a detected failure on that interface, use the mpls traffic-eng backup-path tunnel command in interface configuration mode.
mpls traffic-eng backup-path tunnel interface
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Interface configuration
Command History
Examples
The following example specifies the traffic engineering backup tunnel with the identifier 1000:
Router(config-if)# mpls traffic-eng backup-path Tunnel 1000Related Commands
mpls traffic-eng ds-te bc-model
To enable a Bandwidth Constraints Model to be used by a router in DiffServ-aware Traffic Engineering, use the mpls traffic-eng ds-te bc-model global configuration command. (Using the no form of this command selects the default model, which is the Russian Dolls Model.)
mpls traffic-eng ds-te bc-model [rdm | mam]
no mpls traffic-eng ds-te bc-model [ rdm | mam ]
Syntax Description
rdm
Russian Dolls Model. (Described in IETF RFC 4127).
mam
Maximum Allocation Model. (Described in IETF RFC 4125).
Defaults
Russian Dolls Model is the default.
Command Modes
Global configuration
Command History
Usage Guidelines
1. The Maximum Allocation Model should be selected when the network administrator needs to ensure isolation across all Class Types without having to use pre-emption, and can afford to risk some QoS degradation of Class Types other than the Preimum Class.
2. The Russian Dolls Model should be selected when the network administrator needs to prevent QoS degradation of all Class Types and can impose pre-emption.
Examples
In the following example,the Maximum Allocation Model is being selected:
Router(config)# mpls traffic-eng ds-te bc-model mammpls traffic-eng ds-te mode
To configure a router to enter DiffServ-aware Traffic Engineering modes which incorporate degrees of the IETF Standard, use the mpls traffic-eng ds-te mode global configuration command. Use the no form of this command to return the router to the pre-IETF-Standard mode.
mpls traffic-eng ds-te mode [migration | ietf]
no mpls traffic-eng ds-te mode [migration | ietf ]
Syntax Description
Defaults
Pre-IETF-Standard mode is the default.
Command Modes
Global configuration
Command History
Usage Guidelines
1. Place the router into Migration Mode only if it is still in the pre-IETF Standard ("Traditional") mode, and you want to begin upgrading its network to operate the IETF-Standard form of DS-TE.
2. Place the router into Liberal-IETF Mode only if its network is already in the Migration Mode, and you want to complete the upgrade of that network so it will operate the IETF-Standard form of DS-TE.
Examples
In the following example, the router is configured to operate in Migration Mode:
Router(config)# mpls traffic-eng ds-te migrationmpls traffic-eng fast-reroute backup-prot-preemption
To change the backup protection preemption algorithm to minimize the amount of bandwidth that is wasted, use the mpls traffic-eng fast-reroute backup-prot-preemption command in global configuration mode. To use the default algorithm of minimizing the number of label-switched paths (LSPs) that are demoted, use the no form of this command.
mpls traffic-eng fast-reroute backup-prot-preemption [optimize-bw]
no mpls traffic-eng fast-reroute backup-prot-preemption
Syntax Description
Command Default
A minimum number of LSPs are preempted.
Command Modes
Global configuration
Command History
Usage Guidelines
The mpls traffic-eng fast-reroute backup-prot-preemption command allows you to determine the criteria the router will use when selecting the LSPs that will be preempted.
If you enter the command with the optimize-bw keyword, the router chooses LSPs that will waste the least amount of bandwidth.
If you do not enter the mpls traffic-eng fast-reroute backup-prot-preemption optimize-bw command, the router preempts as few LSPs as possible.
Each router in the network does not have to use the same algorithm; that is, you can specify optimize-bw for some routers in the network but not for others.
You can enter the mpls traffic-eng fast-re-route backup-prot-preemption command at any time. If you change the algorithm, it does not affect LSPs that already are protected. It only affects the placement of new LSPs signaled after you enter this command. The command can affect LSPs during the next periodic promotion cycle.
Examples
In the following examples, a next-next hop (NNHOP) backup tunnel has the following characteristics:
•Total backup capacity: 240 units
•Used backup bandwidth: 220 units
•Available backup bandwidth: 20 units
The backup tunnel currently is protecting LSP1 through LSP5, which have the following bandwidth, and do not have backup bandwidth protection (that is, the "bandwidth protection desired" bit was not set via the tunnel mpls traffic-eng fast-reroute command):
•LSP1: 10 units
•LSP2: 20 units
•LSP3: 30 units
•LSP4: 60 units
•LSP5: 100 units
As shown, LSP1 through LSP5 use 220 units of bandwidth.
LSP6 has backup bandwidth protection and needs 95 units of bandwidth. Twenty units of bandwidth are available, so 75 more units of bandwidth are needed.
In the following example, backup bandwidth protection is enabled and the amount of wasted bandwidth is minimized:
Router(config)# mpls traffic-eng fast-reroute backup-prot-preemption optimize-bwLSP2 and LS4 are preempted so that the least amount of bandwidth is wasted.
In the following example, backup protection preemption is enabled and the number of preempted LSPs is minimized:
Router(config)# no mpls traffic-eng fast-reroute backup-prot-preemptionThe router selects the LSP whose bandwidth is next-greater than the required bandwidth. Therefore, the router picks LSP5 because it has the next larger amount of bandwidth over 75. One LSP is demoted. and 25 units of bandwidth are wasted.
Related Commands
mpls traffic-eng fast-reroute promote
To configure the router to assign new or more efficient backup Multiprotocol Label Switching traffic engineering (MPLS-TE) tunnels to protect MPLS-TE tunnels, use the mpls traffic-eng fast-reroute promote command in privileged EXEC mode.
mpls traffic-eng fast-reroute promote
Syntax Description
This command has no arguments or keywords.
Command Default
No MPLS-TE backup tunnels are assigned.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
To use the mpls traffic-eng fast-reroute promote command, you must be in a user group associated with a task group.
Examples
The following example shows how to initiate backup tunnel promote and assignment:
Router# mpls traffic-eng fast-reroute promoteRelated Commands
mpls traffic-eng fast-reroute timers
To specify how often the router considers switching a label switched path (LSP) to a new (better) backup tunnel if additional backup bandwidth becomes available, use the mpls traffic-eng fast-reroute timers command in global configuration mode. To disable this timer, set the seconds value to zero or use the no form of this command.
mpls traffic-eng fast-reroute timers [promotion seconds]
no mpls traffic-eng fast-reroute timers
Syntax Description
Command Default
The timer is running and is set to a frequency of every 300 seconds (5 minutes). If you enter the no mpls traffic-eng fast-reroute timers command, the router returns to this default behavior.
Command Modes
Global configuration
Command History
Examples
In the following example, LSPs are scanned every 2 minutes (120 seconds). The router uses this information to consider if the LSPs should be promoted to a better backup tunnel:
Router(config)# mpls traffic-eng fast-reroute timers promotion 120mpls traffic-eng flooding thresholds
To set a reserved bandwidth thresholds for a link, use the mpls traffic-eng flooding thresholds command in interface configuration mode. To return to the default settings, use the no form of this command.
mpls traffic-eng flooding thresholds {down | up} percent [percent ...]
no mpls traffic-eng flooding thresholds {down | up}
Syntax Description
Command Default
None
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
When a threshold is crossed, Multiprotocol Label Switching (MPLS) traffic engineering link management advertises updated link information. If no thresholds are crossed, changes can be flooded periodically unless periodic flooding is disabled.
Examples
The following example shows how to set the reserved bandwidth of the link for decreased (down) and for increased (up) thresholds:
Router(config-if)# mpls traffic-eng flooding thresholds down 100 75 25Router(config-if)# mpls traffic-eng flooding thresholds up 25 50 100Related Commands
mpls traffic-eng interface
To enable Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) link-state advertisement (LSA) for an interface to be advertised into the Open Shortest Path First (OSPF) area 0, use the mpls traffic-eng interface command in router configuration mode. To restore the setting of the MPLS TE LSA to the same area as the router LSA, use the no form of this command.
mpls traffic-eng interface interface area 0
no mpls traffic-eng interface interface area 0
Syntax Description
interface
The interface to be advertised with an MPLS TE LSA into OSPF area 0. The interface may be one or two words.
Defaults
The default is to advertise the area assigned to the interface by the OSPF network configuration.
Command Modes
Router configuration
Command History
Usage Guidelines
Usually, the MPLS TE LSA is advertised into the same area as the router LSA. If a link between two Area Border Routers (ABRs) is in an OSPF area besides area 0, you can advertise the link between ABRs into area 0. This solves for TE the same problem that virtual links solve for IP routing. This command is valid only for OSPF. Issue the command on both ABRs for the interfaces at both ends of the link.
Examples
In the following example, OSPF advertises the MPLS TE LSA for interface pos2/0 to area 0:
Router(config)# router ospf 1
Router(config-router)# mpls traffic-eng interface pos2/0 area 0
Related Commands
Command Descriptionmpls traffic-eng multicast-intact
Enables multicast-intact support from the OSPF routing protocol to maintain and publish the native IP nexthops (paths) for every OSPF route.
mpls traffic-eng link timers bandwidth-hold
To set the length of time that bandwidth is held for a Resource Reservation Protocol (RSVP) PATH (Set Up) message while waiting for the corresponding RSVP RESV message to come back, use the mpls traffic-eng link timers bandwidth-hold command in global configuration mode.
mpls traffic-eng link timers bandwidth-hold hold-time
Syntax Description
Defaults
15 seconds
Command Modes
Global configuration
Command History
Examples
The following example sets the length of time that bandwidth is held to 10 seconds.
Router(config)# mpls traffic-eng link-management timers bandwidth-hold 10Related Commands
Command Descriptionshow mpls traffic-eng link-management bandwidth-allocation
Displays current local link information.
mpls traffic-eng link timers periodic-flooding
To set the length of the interval used for periodic flooding, use the mpls traffic-eng link timers periodic-flooding command in global configuration mode.
mpls traffic-eng link timers periodic-flooding interval
Syntax Description
Defaults
180 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to set the interval for periodic flooding of traffic engineering (TE) topology information.
Changes in the Multiprotocol Label Switching (MPLS) TE topology database are flooded by the link state Interior Gateway Protocol (IGP). Some changes, such as those to link status (up/down) or configured parameters, trigger immediate flooding. Other changes are considered less urgent and are flooded periodically. For example, changes to the amount of link bandwidth allocated to TE tunnels are flooded periodically unless the change causes the bandwidth to cross a configurable threshold.
Examples
The following example sets the interval length for periodic flooding to advertise flooding changes to 120 seconds.
Router(config)# mpls traffic-eng timers periodic-flooding 120Related Commands
Command Descriptionmpls traffic-eng flooding thresholds
Sets the reserved bandwidth thresholds of a link.
mpls traffic-eng link-management timers bandwidth-hold
To set the length of time that bandwidth is held for an RSVP path (setup) message while you wait for the corresponding RSVP Resv message to come back, use the mpls traffic-eng link-management timers bandwidth-hold command in global configuration mode. To disable this function, use the no form of this command.
mpls traffic-eng link-management timers bandwidth-hold hold-time
no mpls traffic-eng link-management timers bandwidth-hold
Syntax Description
Defaults
15 seconds
Command Modes
Global configuration
Command History
Examples
In the following example, bandwidth is set to be held for 10 seconds:
Router(config)# mpls traffic-eng link-management timers bandwidth-hold 10Related Commands
Command Descriptionshow mpls traffic-eng link-management bandwidth-allocation
Displays current local link information.
mpls traffic-eng link-management timers periodic-flooding
To set the length of the interval for periodic flooding, use the mpls traffic-eng link-management timers periodic-flooding command in global configuration mode. To disable the specified interval length for periodic flooding, use the no form of this command.
mpls traffic-eng link-management timers periodic-flooding interval
no mpls traffic-eng link-management timers periodic-flooding
Syntax Description
interval
Length of the interval (in seconds) for periodic flooding. Valid values are from 0 to 3600. A value of 0 turns off periodic flooding. If you set this value from 1 to 29, it is treated as 30.
Defaults
180 seconds (3 minutes)
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to advertise link state information changes that do not trigger immediate action. For example, a change to the amount of allocated bandwidth that does not cross a threshold.
Examples
The following example shows how to set the interval length for periodic flooding to 120 seconds:
Router(config)# mpls traffic-eng link-management timers periodic-flooding 120Related Commands
Command Descriptionmpls traffic-eng flooding thresholds
Sets a link's reserved bandwidth thresholds.
mpls traffic-eng logging lsp
To log certain traffic engineering label switched path (LSP) events, use the mpls traffic-eng logging lsp command in global configuration mode. To disable logging of LSP events, use the no form of this command.
mpls traffic-eng logging lsp {path-errors | reservation-errors | preemption | setups | teardowns} [acl-number]
no mpls traffic-eng logging lsp {path-errors | reservation-errors | preemption | setups | teardowns} [acl-number]
Syntax Description
Defaults
Logging of LSP events is disabled.
Command Modes
Global configuration
Command History
Examples
The following example shows how to log path errors for LSPs that match access list 3:
Router(config)# mpls traffic-eng logging lsp path-errors 3Related Commands
mpls traffic-eng logging tunnel
To log certain traffic engineering tunnel events, use the mpls traffic-eng logging tunnel command in global configuration mode. To disable logging of traffic engineering tunnel events, use the no form of this command.
mpls traffic-eng logging tunnel lsp-selection [acl-number]
no mpls traffic-eng logging tunnel lsp-selection [acl-number]
Syntax Description
Defaults
Logging of tunnel events is disabled.
Command Modes
Global configuration
Command History
Examples
The following example shows how to log traffic engineering tunnel events associated with access list 3:
Router(config)# mpls traffic-eng logging tunnel lsp-selection 3Related Commands