Specifications

Table Of Contents
traffic-engineering route
MP-841
Cisco IOS Multiprotocol Label Switching Command Reference
January 2010
traffic-engineering route
To configure a route for a specified filter through a specified tunnel, use the traffic-engineering route
command in router configuration mode. To disable this function, use the no form of this command.
traffic-engineering route f
ilter-number interface [preference number] [loop-prevention
{on | of
f}]
no traffic-engineering route f
ilter-number interface [preference number] [loop-prevention
{on | of
f}]
Syntax Description
Defaults preference: 1
loop-prevention: o
n
Command Modes Router configuration
Command History
Usage Guidelines The traffic engineering process is used to decide if a configured traffic engineering route should be
in
stalled in the forwarding table.
The first step is to determine if the route is up. If the route is enabled, the LSP tunnel interface is up, the
l
oop prevention check is either disabled or passed, and the traffic engineering route is up.
If multiple routes for the same filter are up, a route is selected based on administrative preference.
If loop prevention is enabled, metrics are solicited from the tunnel tail, and the loop prevention algorithm
i
s run on the result. For a discussion of the loop prevention algorithm, see the show ip
traffic-engineering metrics command.
filter-number The number of the traffic engineering filter to be forwarded through the use
o
f this traffic engineering route, if the route is installed.
interface Label switched path (LSP)-encapsulated tunnel on which the traffic-passing
f
ilter should be sent, if this traffic engineering route is installed.
preference num
ber (Optional) This is a number from 1 to 255, with a lower value being more
desirable. The default is 1.
loop-prevention (Optional) A setting of on or
off. The default is on.
Release Modification
11.1 CT This command was introduced.
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX This command is supported in the Cisco IOS Release 12.2SX train. Support
i
n a specific 12.2SX release of this train depends on your feature set,
platform, and platform hardware.