COMMAND

(config)#mpls traffic-eng tunnels

show mpls traffic-eng tunnels summary
interface Tunnel0

ip unnumbered Loopback0

tunnel mode mpls traffic-eng

tunnel destination destination-ip

tunnel mpls traffic-eng path-option 10 dynamic
router(config-if)#ip rsvp bandwidth[<1-10000000 total-reservable-bandwidth>[per-flowbandwidth]]
show ip rsvp interface

router(config-if)#mpls traffic-eng attribute-flags attributes (0x0-0xFFFFFFFF)

router(config-if)#mpls traffic-eng administrative-weight (0-4294967295)

mpls traffic-eng router-id Loopback0

mpls traffic-eng area 0

MEAN

you need to enable MPLS Traffic Engineering on every router that you want to participate in MPLS TE.Afte
also need to enable it on every interface that might touch a TE tunnel
A quick way to check to make sure everything is configured is with the first three lines of the command

MPLS Traffic Engineering tunnels are represented as tunnel interfaces in the Cisco IOS Software. From this
tunnel is no different from a GRE tunnel or any other kind of tunnel you can configure.

Cisco IOS Software does not forward traffic down an interface without an IP address on it, so you need to as
Engineering tunnel you've just created. However, because TE tunnels are unidirectional and don't have the c
communicate, it's a waste of addresses to put an additional IP address on the interface.

Tells the Cisco IOS Software that this tunnel interface is an MPLS Traffic Engineering tunnel. Other possibl
on.

Tells the Cisco IOS Software what the tunnel's endpoint is. The IP address specified here is the MPLS Traffi
the router to which you want to build a tunnel. The destination-ipin this case is the Loopback0 interface on t

Tells the Cisco IOS Software how to generate the path from the tunnel headend to the tunnel tail. This comm
You configure the amount of reservable bandwidth on a link using the following per-interface command

You can double-check your configuration using the command, The only columns that are relevant to MPLS
IP. pct is the percentage of reservable bandwidth that has actually been reserved across the link. IPis the num
reserved across that link.

Another property of MPLS Traffic Engineering that you can enable is attribute flags. An attribute flag is a 32
existence of up to 32 separate properties on that link.attributescan be 0x0 to 0xFFFFFFFF. It represents a bit
of an attribute is 0 or 1. 0x0 is the default, which means that all 32 attributes in the bitmap are 0.

One of the pieces of information that's flooded about a link is its cost, which the TE path calculation uses as
costs are associated with a linkthe TE cost and the IGP cost. This allows you to present the TE path calcu
the regular IGP SPF sees. The default TE cost on a link is the same as the IGP cost. To change only the TE c
following per-link command:

You need to enter only two commands to enable flooding of MPLS Traffic Engineering info in OSPF:
+ mpls traffic-eng router-id Loopback0sets the TE RID. This can be a different value than the OSPF RID, bu
+ mpls traffic-eng area 0 configures the area in which traffic engineering is enabled. Generally, MPLS Traff
area. This does not have to be Area 0, but it almost always is