Service Provider CCIE

Advanced Technology Class

MPLS Traffic Engineering (TE)

http://www.InternetworkExpert.com

Why Traffic Engineering?

• Requirements for Traffic Engineering Over

MPLS - RFC 2702
– A major goal of Internet Traffic Engineering is to
facilitate efficient and reliable network operations
while simultaneously optimizing network resource
utilization and traffic performance. Traffic Engineering
has become an indispensable function in many large
Autonomous Systems because of the high cost of
network assets and the commercial and competitive
nature of the Internet. These factors emphasize the
need for maximal operational efficiency.

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

1
 What problem does TE solve?

• Efficient use of all available bandwidth

• Help ensure the desired path through the
network
• Eliminate or postpone the need for adding
additional physical links

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

IGP Issues (OSPF and ISIS)

• IGPs use the least cost path which may

not be the only path available
• Manipulating the IGP metrics will only
move the problem to other links
• Manipulating the IGP metrics doesn’t scale
• IGP metrics lack the granularity needed to
truly make use of all available bandwidth
• IGPs use destination based routing to
determine the path through the network
Copyright © 2007 Internetwork Expert, Inc
www.InternetworkExpert.com

2
 Traditional Routing Drawbacks

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Resource Reservation Protocol (RSVP)

• RSVP was originally designed as a means for a

host to determine if there is enough bandwidth
available for a particular traffic flow
• RSVP never took off due to the fact it was a
host-to-host protocol
• Used for establishing LSPs in MPLS networks
• RSVP-TE provides support for
– Explicit path configuration
– Path numbering
– Route Recording

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

3
 RSVP-TE Signaling
IGP Path Desired Path

Tunnel Tail Tunnel Head

R7 R8
Resv + Label Path

Path
Resv + Label
R3 R6
Resv + Label
Path

Path Resv + Label

R1 R5
Path

Resv + Label

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Traffic Engineering Path Calculation

• Constrained-Based Shortest Path First

(CSPF)
– Bandwidth
– Affinity
– Administrative weight
– Explicitly defined path
• Path calculation can also be done offline

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

4
 Traffic Engineering and IGP

• TE uses existing link-state routing protocols,

OSPF and ISIS, to disseminate the topology
information
– OSPF uses Type 10 (area-local) Opaque LSAs
– ISIS uses new TLVs
• Normally IGP carries the information about itself,
neighbors, and cost to the neighbors
• TE adds information regarding available
bandwidth to the neighbors
– show mpls traffic-eng topology

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Enabling Basic IGP Support for TE

• Support for TE needs to be enabled under

the routing process for OSPF and IS-IS
• OSPF
– mpls traffic-eng area <area-id>
– mpls traffic-eng router-id <router-id>

• IS-IS
– metric-style wide
– mpls traffic-eng {level-1 | level-2}
– mpls traffic-eng router-id <router-id>

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

5
 CSPF Path Options

• Dynamic
– The router will calculate the best path for the tunnel
– Uses the configured constraints such and bandwidth
and other attributes
• Explicit
– User defined path for the tunnel
– Uses the configured constraints such and bandwidth
and other attributes
• More than one path option can be configured for
a tunnel
• Dynamic and Explicit can be used for the same
tunnel
• TE tunnels are unidirectional
Copyright © 2007 Internetwork Expert, Inc
www.InternetworkExpert.com

CSPF Path Options (cont)

tunnel mpls traffic-eng bandwidth bandwidth

tunnel mpls traffic-eng priority setup-priority hold-priority

tunnel mpls traffic-eng path-option number {dynamic | explicit {name path-

name | id path-number}} [lockdown]

ip explicit-path {name word | identifier number} [{enable | disable}]

append-after Append additional entry after specified index

exclude-address Exclude an address from subsequent partial path segments
index Specify the next entry index to add, edit (or delete)
list Re-list all or part of the explicit path entries
next-address Specify the next (adjacent) address in the path

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

6
 Routing Across the TE Tunnel

• Static routing
• Policy based routing
• Dynamic routing protocol
– tunnel mpls traffic-eng autoroute announce

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

General Configuration Steps for All Routers

• Ensure CEF is enabled

• Enable TE support for the IGP protocol being used
• Enable MPLS TE Tunnels on each router in the path using the mpls
traffic-eng tunnels global configuration command
• Enable MPLS TE Tunnels on each interface in the path using the
mpls traffic-eng tunnels interface level command
• Specify the amount of reservable bandwidth under the interfaces
– Use the ip rsvp bandwidth <total kbps> <per-flow kbps> command
to specify the available bandwidth
– If the ip rsvp bandwidth command is entered without specifying an
amount, the available bandwidth will be 75% of the interface's
bandwidth
– Note that the bandwidth could be different in each direction of the TE
tunnel
– If the ip rsvp bandwidth command is not used the reservable
bandwidth is set to 0 although TE signaling will still occur on the
interface

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

7
 MPLS TE Topology

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Head End Router Configuration

R3:

mpls traffic-eng tunnels

!
interface Tunnel0
ip unnumbered Loopback0
tunnel destination 150.1.5.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
!
interface Serial1/2
mpls traffic-eng tunnels
ip rsvp bandwidth
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

8
Mid-Point Router Configuration
R1:

mpls traffic-eng tunnels

!
interface FastEthernet1/0
mpls traffic-eng tunnels
ip rsvp bandwidth
!
interface Serial2/1
mpls traffic-eng tunnels
ip rsvp bandwidth
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Tail End Router Configuration

R5:

mpls traffic-eng tunnels

!
interface Ethernet0/0
mpls traffic-eng tunnels
ip rsvp bandwidth
!
router ospf 1
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

9
 Head End Verification
Rack1R3#show mpls traffic-eng tunnels tunnel 0

Name: Rack1R3_t0 (Tunnel0) Destination: 150.1.5.5

Status:
Admin: up Oper: up Path: valid Signalling: connected

path option 1, type dynamic (Basis for Setup, path weight 782)

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based
auto-bw: disabled

InLabel : -
OutLabel : Serial1/2, 16
RSVP Signalling Info:
Src 150.1.3.3, Dst 150.1.5.5, Tun_Id 0, Tun_Instance 1
RSVP Path Info:
My Address: 150.1.3.3
Explicit Route: 150.1.13.1 150.1.15.1 150.1.15.5 150.1.5.5
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Shortest Unconstrained Path Info:
Path Weight: 782 (TE)
Explicit Route: 150.1.13.1 150.1.15.1 150.1.15.5 150.1.5.5
History:
Tunnel:
Time since created: 56 minutes, 31 seconds
Time since path change: 41 minutes, 11 seconds
Current LSP:
Uptime: 41 minutes, 11 seconds
Rack1R3#

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Mid-Point Verification
Rack1R1#show mpls traffic-eng tunnels name Rack1R3_t0

LSP Tunnel Rack1R3_t0 is signalled, connection is up

InLabel : Serial2/1, 16
OutLabel : FastEthernet1/0, implicit-null
RSVP Signalling Info:
Src 150.1.3.3, Dst 150.1.5.5, Tun_Id 0, Tun_Instance 1
RSVP Path Info:
My Address: 150.1.15.1
Explicit Route: 150.1.15.5 150.1.5.5
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Rack1R1#show mpls forwarding
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
16 Pop Label 150.1.3.3 0 [1] 126 Fa1/0 150.1.15.5
Rack1R1#

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

10
 Tail End Verification
Rack1R5#show mpls traffic-eng tunnels name Rack1R3_t0

LSP Tunnel Rack1R3_t0 is signalled, connection is up

InLabel : Ethernet0/0, implicit-null
OutLabel : -
RSVP Signalling Info:
Src 150.1.3.3, Dst 150.1.5.5, Tun_Id 0, Tun_Instance 1
RSVP Path Info:
My Address: 150.1.5.5
Explicit Route: NONE
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Rack1R5#show mpls forwarding
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
16 Pop tag 150.1.3.3 1 [5] 612 Se0/0 150.1.45.4
Rack1R5#

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

Traffic Path Verification

Rack1R3#traceroute 150.1.5.5

Type escape sequence to abort.

Tracing the route to 150.1.5.5

1 150.1.13.1 16 msec 12 msec 16 msec

2 150.1.15.5 20 msec * 16 msec
Rack1R3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Rack1R3(config)#ip route 150.1.5.5 255.255.255.255 tu 0
Rack1R3(config)#^Z
Rack1R3#
Rack1R3#traceroute 150.1.5.5

Type escape sequence to abort.

Tracing the route to 150.1.5.5

1 150.1.13.1 [MPLS: Label 16 Exp 0] 32 msec 28 msec 28 msec

2 150.1.15.5 20 msec * 16 msec
Rack1R3#

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

11
 MPLS TE Topology

Copyright © 2007 Internetwork Expert, Inc

www.InternetworkExpert.com

12