Live! - Deploying MPLS Traffic Engineering

Deploying MPLS Traffic Engineering
BRKMPL-2104
Follow us on Twitter for real time updates of the event:

@ciscoliveeurope, #CLEUR
Housekeeping
 We value your feedback- don't forget to complete your online session

evaluations after each session & the Overall Conference Evaluation
which will be available online from Thursday
 Visit the World of Solutions and Meet the Engineer
 Visit the Cisco Store to purchase your recommended readings
 Please switch off your mobile phones
 After the event don’t forget to visit Cisco Live Virtual:
www.ciscolivevirtual.com
 Follow us on Twitter for real time updates of the event:
@ciscoliveeurope, #CLEUR
BRKMPL-2104 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
Agenda
 Technology Overview
 Bandwidth optimization
 TE for QoS
 Traffic Protection
 Inter-Domain Traffic Engineering
 General Deployment Considerations
Technology Overview
MPLS TE Overview
 Introduces explicit routing

 Supports constraint-
based routing IP/MPLS
 Supports admission control

 Provides protection capabilities
 Uses RSVP-TE to
establish LSPs
 Uses ISIS / OSPF extensions to
advertise link attributes
TE LSP
How MPLS TE Works
Head end
 Link information Distribution*
ISIS-TE
IP/MPLS OSPF-TE
 Path Calculation (CSPF)*
 Path Setup (RSVP-TE)
 Forwarding Traffic
down Tunnel
Auto-route (announce /
destinations)
Static route
PBR
Mid-point Tail end
CBTS / PBTS
TE LSP
Forwarding Adjacency
Tunnel select
Link Information Distribution
 Additional link characteristics

Interface address
IP/MPLS
Neighbor address
Physical bandwidth
Maximum reservable bandwidth
Unreserved bandwidth
(at eight priorities)
TE metric
Administrative group (attribute flags)
 IS-IS or OSPF flood link information

TE
 All TE nodes build a TE topology Topology
database
database
 Not required if using off-line path
computation
Path Calculation
Find shortest
path to R8
with 8Mbps  TE nodes can perform
IP/MPLS constraint-based routing
R1
 Tunnel head end generally
15 5
3 responsible for path
10
R8 calculation
10
10 8  Constraints and topology
database as input to path
10 computation
 Shortest-path-first algorithm
ignores links not meeting
TE constraints
Topology
database  Tunnel can be signaled once
a path is found
 Not required if using offline
path computation
n Link with insufficient bandwidth
n Link with sufficient bandwidth
TE LSP Signaling
 Tunnel signaled with TE

extensions to RSVP
 Soft state maintained with Head end IP/MPLS
downstream PATH messages
 Soft state maintained with
upstream RESV messages
 New RSVP objects L=16
RESV Tail end
LABEL_REQUEST (PATH)
LABEL (RESV) PATH
EXPLICIT_ROUTE
RECORD_ROUTE (PATH/RESV)
SESSION_ATTRIBUTE (PATH) Input Out Label,
Label Interface
 LFIB populated using 17 16, 0
TE LSP
RSVP labels allocated by RESV
messages
Traffic Selection
 Multiple traffic selection options

Head end
Auto-route
IP/MPLS Static routes
Policy Based Routing
Forward Adjacency
Pseudowire Tunnel Selection
Class / Policy Based Tunnel
Selection
 Tunnel path computation
independent of routing decision
injecting traffic into tunnel
 Traffic enters tunnel
TE LSP at head end
Configuring MPLS TE and Link Information
Distribution Using IS-IS (Cisco IOS)
mpls traffic-eng tunnels Enable MPLS TE on this

! node
interface POS0/1/0
ip address 172.16.0.0 255.255.255.254 Enable MPLS TE on this
ip router isis interface
mpls traffic-eng tunnels
Attribute flags
mpls traffic-eng attribute-flags 0xF
mpls traffic-eng administrative-weight 20 TE metric
ip rsvp bandwidth 100000
! Maximum reservable
router isis
bandwidth
net 49.0001.1720.1625.5001.00
is-type level-2-only
Enable wide metric format
metric-style wide and TE extensions (TE Id,
mpls traffic-eng router-id Loopback0 router level)
mpls traffic-eng level-2
passive-interface Loopback0
!
Distribution Using OSPF (Cisco IOS XR)
router ospf DEFAULT Enable TE extensions on

this area
area 0
mpls traffic-eng
TE router Id
interface Loopback0
passive
!
Configuration mode for
RSVP global and interface
interface POS0/3/0/0
commands
!
mpls traffic-eng router-id Loopback0
Maximum reservable
!
bandwidth
rsvp
bandwidth 100000
MPLS TE global and
!
interface commands
!
mpls traffic-eng
TE metric
admin-weight 5
attribute-flags 0x8 Attribute flags
!
!
Distribution Using IS-IS (Cisco NX-OS)
feature isis Enable MPLS TE on this

feature mpls traffic-eng node
Enable MPLS TE on this
interface Ethernet1/1 interface
TE metric
mpls traffic-eng administrative-weight 20
mpls traffic-eng attribute-flags 0xf Attribute flags
mpls traffic-eng bandwidth 10000000
no switchport Maximum reservable
ip address 172.16.0.14/31 bandwidth
ip router isis DEFAULT
no shutdown
router isis DEFAULT Enable TE extensions (TE

mpls traffic-eng level-2 Id, router level)
mpls traffic-eng router-id loopback0
net 49.0001.1720.1625.5202.00
is-type level-2
Configuring Tunnel at Head End
(Cisco IOS)
interface Tunnel1 Destination (tunnel

description FROM-ROUTER-TO-DST1
tail end)
ip unnumbered Loopback0 TE tunnel (as
tunnel destination 172.16.255.3 opposed to GRE or
tunnel mode mpls traffic-eng others)
tunnel mpls traffic-eng priority 5 5
tunnel mpls traffic-eng bandwidth 10000 Setup/hold
tunnel mpls traffic-eng affinity 0x0 mask 0xF priorities
tunnel mpls traffic-eng path-option 5 explicit name PATH1
Signaled
tunnel mpls traffic-eng path-option 10 dynamic bandwidth
!
ip explicit-path name PATH1 enable Consider links with
next-address 172.16.0.1 0x0/0xF as
next-address 172.16.8.0 attribute flags
! Tunnel path
options (PATH1,
otherwise dynamic)
Explicit PATH1
definition
(Cisco IOS XR)
explicit-path name PATH1 Explicit PATH1

index 1 next-address ipv4 unicast 172.16.0.4
definition
index 2 next-address ipv4 unicast 172.16.0.7 MPLS TE P2P
index 3 next-address ipv4 unicast 172.16.4.2 tunnel
!
interface tunnel-te1 Setup/hold
priorities
ipv4 unnumbered Loopback0 Signaled
priority 5 5 bandwidth
signalled-bandwidth 100000
destination 172.16.255.2 Destination (tunnel
path-option 10 explicit name PATH1 tail end)
path-option 20 dynamic
Tunnel path
affinity f mask f options (PATH1,
! otherwise dynamic)
Consider links with

0xF/0xF as
attribute flags
(Cisco NX-OS)
mpls traffic-eng Explicit PATH1

explicit-path name PATH1
definition
index 10 next-address 172.16.0.15 MPLS TE P2P
index 20 next-address 172.16.0.13 tunnel
interface tunnel-te1
description FROM-ROUTER-TO-DST1 Destination (tunnel
ip unnumbered loopback0
tail end)
no shutdown Consider links with
destination 172.16.255.5 0xF/0xF as
affinity 0xf mask 0xf attribute flags
bandwidth 10000 Signaled
path-option 10 explicit name PATH1 bandwidth
Tunnel path
priority 5 5
options (PATH1,
otherwise dynamic)
Setup/hold
priorities
Characteristics of P2MP TE LSP
 Unidirectional
 Explicitly routed
IP/MPLS
 One head end, but one or more
tail ends (destinations)
 Same characteristics
(constraints, protection, etc.) for
all destinations
TE LSP
P2MP TE LSP Terminology
Tail end
IP/MPLS  Head-end/Source: Node where
Head end LSP signaling is initiated
 Mid-point: Transit node where
LSP signaling is processed (not
Mid-point and
branch point a head-end, not a tail-end)
 Tail-end/Leaf/destination: node
where LSP signaling ends
IP/MPLS  Branch point: Node where

packet replication is performed
S2L sub-LSP
 Source-to-leaf (S2L) sub-LSP:
S2L sub-LSP P2MP TE LSP segment that
runs from source to one leaf
TE LSP
P2MP TE LSP Path Computation
 Constrained Shortest Path First (CSPF)
used to compute an adequate tree IP/MPLS R4
 CSPF executed per destination R2

R1
 TE topology database and tunnel
constraints as input for path
computation
R3 R5
 Path constraints may include loose,
included, excluded hops
 Same constraints for all destinations TE
(bandwidth, affinities, priorities, etc.) Topology
database
 Path computation yields explicit path to
each destination
 No changes to OSPF/IS-IS TE CSPF
extensions
 Static paths possible with offline path Path to R4: (R1, R2, R4)
computation
Path to R5: (R1, R2, R5)
P2MP TE LSP Signaling
 Source sends unique PATH

IP/MPLS
PATH
message per destination
PATH  LFIB populated using
PATH RSVP labels allocated by
PATH
RESV messages
 Multicast state built by
reusing sub-LSP labels at
branch points
IP/MPLS
L=17
RESV
L=16
RESV
L=16
RESV
L=18
Input Out Label, RESV
Label Interface
16 17, 0
18, 1
P2MP TE LSP Traffic Selection
IP Multicast
 One or more IP multicast

RSVP-TE groups mapped to a Tunnel
Receiver
IP/MPLS  Groups mapped via static

Source IP IGMP join
PIM
IP  PIM outside of MPLS
Receiver network
PIM
IP  Modified egress RPF check
PIM
against TE LSP and tunnel
Modified RPF
head end (source address)
check
Static IGMP Joins  Egress node may abstract
P2MP Tunnel Multicast Group TE LSP as a virtual interface
(192.168.5.1, 232.0.0.1) (LSPVIF) for RPF purposes
Tunnel1
(192.168.5.1, 232.0.0.2)
Tunnel2 (192.168.5.1, 232.0.0.3)

P2MP TE LSP Traffic Selection
Static P2MP Pseudowires
 Provides a layer-2 multicast

CE4 service with segmentation
T-PE4
(Leaf)
 Multicast forwarding plane from
T-PE3
(Leaf) CE3
root to leaves (all traffic types:
multicast, broadcast, unicast)
T-PE5
CE5 (Root)
 Unicast forwarding plane from
leaves to root
T-PE2
(Leaf)
CE2  Initial implementation supporting
only static pseudowire
T-PE1
(Leaf)
CE1
 Label bindings defined statically
on root and leaves
P2MP PSN
Tunnel  No control plane (targeted LDP)
pseudowire  No context-specific label space
on leaves
Configuring P2MP Tunnel at Head End
(Cisco IOS)
mpls traffic-eng destination list name P2MP-LIST-DST1 Destination list with

ip 172.16.255.1 path-option 10 explicit name PATH1 one path-option
ip 172.16.255.2 path-option 10 dynamic per destination
ip 172.16.255.3 path-option 10 dynamic
ip 172.16.255.4 path-option 10 dynamic
Tunnel as passive
!
PIM interface
interface Tunnel1
(historical)
description FROM-ROUTER-TO-LIST-DST1
ip unnumbered Loopback0 Multicast groups
ip pim passive mapped to tunnel
ip igmp static-group 232.0.0.1 source 192.168.5.1
ip igmp static-group 232.0.0.2 source 192.168.5.1 P2MP TE Tunnel
tunnel mode mpls traffic-eng point-to-multipoint
tunnel destination list mpls traffic-eng name P2MP-LIST-DST1 Destination list
tunnel mpls traffic-eng bandwidth 1000 Setup/hold
! priorities
Signaled
bandwidth
Configuring RPF Check at P2MP Tunnel Tail End
(Cisco IOS)
ip multicast mpls traffic-eng Enable IPv4

ip mroute 192.168.5.1 255.255.255.255 172.16.255.5
multicast over
P2MP TE LSP
!
Tunnel source
(172.16.255.5) as
next-hop for IP
Multicast source
(192.168.5.1) RPF
check
Configuring P2MP Tunnel at Head End
(Cisco IOS XR)
interface tunnel-mte1 MPLS TE P2MP tunnel
ipv4 unnumbered Loopback0
destination 172.16.255.129 Destination with path-
path-option 10 explicit name PATH1
path-option 20 dynamic option list
!
destination 172.16.255.130 Destination with single
!
path-option
priority 0 0
signalled-bandwidth 100000 Setup/hold priorities
!
node-capability label-switched-multicast
multicast-routing
Signaled bandwidth
address-family ipv4
interface tunnel-mte1 Enable MPLS multicast
enable
!
interface all enable
! Enable multicast
! forwarding over tunnel-
router igmp
vrf default
mte1
interface tunnel-mte1
static-group 232.0.0.1 192.168.5.1 Multicast groups mapped
static-group 232.0.0.2 192.168.5.1
! to tunnel-mte1
!
!
Configuring RPF Check at P2MP Tunnel Tail End
(Cisco IOS XR)
multicast-routing
address-family ipv4
core-tree-protocol rsvp-te
static-rpf 192.168.5.1 32 mpls 172.16.255.3 Enable IPv4/v6 multicast
interface all enable over P2MP TE LSP
!
!
Tunnel source
(172.16.255.3) as next-hop
for IP Multicast source
(192.168.5.1) RPF check
MPLS TE Integration with Network
Services
A TE LSP provides transport for different network services
PE PE CE
CE ATM ATM
CE CE
IP/MPLS
PE PE
Frame
CE Ethernet
Relay CE
CE
PE
CE CE
PE PE
CE Ethernet Ethernet CE
TE LSP with IP (VPN)

Low-Latency, BW L2VPN
Reserved BW Service
Protected TE LSP (Pseudowire)
MPLS TE Deployment Models
Bandwidth Optimization Reactive
Planned
R1 IP/MPLS R1 IP/MPLS
R8 R8
R2 R2
Point-to-Point SLA Protection

R8 R8
R2 R2
Bandwidth optimization
Planned Bandwidth Optimization
Physical Topology Tunnel mesh to satisfy

Traffic Matrix traffic matrix
R1 R6 R1 R6
R1 R2 R3 R4 R5 R6
R1 4 7 1 5 4 5
R2 R5 R2 R5
R2 2 2 4 7 2 3
R3 1 2 9 5 5 5
R4 9 1 4 1 3 1
R5 3 7 9 2 7 7
R6 6 3 5 4 9 12
R3 R4 R3 R4
 Tries to optimize underlying physical topology based on traffic matrix

 Key goal is to avoid link over/under utilization
 On-line (CSPF) or off-line path computation
 May result in a significant number of tunnels
 Should not increase your routing adjacencies
Traffic Matrix Measurement
 Interface counters on
unconstrained tunnels
 Interface MIB AS65001 AS65002 AS65003
 MPLS LSR MIB

 NetFlow
NetFlow BGP Next Hop PE PE
P P
MPLS-Aware NetFlow
PE PE
Egress/Output NetFlow
 BGP policy accounting PE P P PE
Communities POP POP

AS path
IP prefix Server Server
Farm Farm
AutoTunnel Mesh
New mesh
 Mesh group: LSRs to mesh group
automatically member
 Membership identified by
Matching TE Router ID
against ACL New mesh
IGP mesh-group group
advertisement member
 Each member automatically

creates tunnel upon
detection of a member
 Tunnels instantiated from
template
 Individual tunnels not
displayed in router
configuration
Auto Bandwidth
Total Bandwidth
bandwidth available to
for all TE other tunnels
tunnels Max
on a path
Tunnel
Min
resized to
measured rate
Time
 Dynamically adjust bandwidth reservation based on measured traffic
 Optional minimum and maximum limits
 Sampling and resizing timers
 Tunnel resized to largest sample since last adjustment
 Actual resizing can be subject to adjustment threshold and overflow
detection
Configuring AutoTunnel Mesh
(Cisco IOS)
mpls traffic-eng tunnels Enable Auto-tunnel Mesh

mpls traffic-eng auto-tunnel mesh
!
Tunnel template
interface Auto-Template1
ip unnumbered Loopback0 Template cloned for each
tunnel destination mesh-group 10 member of mesh group 10
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
Dynamic (CSPF) path to
tunnel mpls traffic-eng path-option 10 dynamic
each mesh group member
tunnel mpls traffic-eng auto-bw frequency 3600
!
router ospf 16 Tunnels will adjust
log-adjacency-changes bandwidth reservation
mpls traffic-eng router-id Loopback0 automatically
mpls traffic-eng area 0
mpls traffic-eng mesh-group 10 Loopback0 area 0 Advertise mesh group 10
membership in area 0
network 172.16.0.0 0.0.255.255 area 0
!
Reactive Bandwidth Optimization
Bandwidth Optimization Reactive
Planned
R8 R8
R2 R2
 Selective deployment of tunnels when highly-utilized links are identified

 Generally, deployed until next upgrade cycle alleviates congested links
TE for QoS
Motivations
 Point-to-point SLAs
 Admission control
PE1 IP/MPLS  Integration with DiffServ
 Increased routing control to
PE3 improve network performance
PE2
MPLS TE and DiffServ Deployment Models
DiffServ-Aware TE and
MPLS TE and no DiffServ MPLS TE and DiffServ DiffServ
Link Class1 Class1
Load Capacity Load Capacity

Load Capacity
Class2
Class2

Capacity Capacity
Class3 Class3
 A solution when:  A solution when:  A solution when:

No differentiation required Differentiation required Strong differentiation required
Optimization required Optimization required Fine optimization required
 Limit link load to actual  Limit class capacity  Limit class capacity to
link capacity to expected class load expected class load
 No notion of traffic classes  Limit class load to actual  Limit class load to actual
class capacity for one class class capacity for at least two
–
classes
BRKMPL-2104
Differentiation / Optimization / Complexity
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public
+ 38
DiffServ-Aware Traffic Engineering
 Enables per-class traffic engineering

PE1 IP/MPLS
 IS-IS or OSPF flood link information (as
usual)
PE3  Per-class unreserved bandwidth on
each link
PE2
 New RSVP object (CLASSTYPE)
 Nodes manages link bandwidth using a
bandwidth constraint model
 Two models defined
- Maximum Allocation Model (MAM)
- Russian Doll Model (RDM)
 Unique class definition and constraint

model throughout network
Bandwidth Constraints  Two classes (class-types) in current

Class-type 1 (voice) 20%
implementations
Class-type 2 (video) 40%
Maximum Allocation Model (MAM)
 BW pool applies
to one class
BC0
 Sum of BW pools may Class0
exceed MRB
Maximum
All
 Sum of total BC1 Class1 Reservable
Classes Bandwidth
reserved BW may (MRB)
not exceed MRB BC2 Class2
 Current implementation
supports BC0 and BC1
Russian Dolls Model (RDM)
 BW pool applies to one

All
or more classes BC0 Classes
 Global BW pool (BC0) (Class0 Maximum
+ Reservable
equals MRB BC1 Class1 Bandwidth
Class1 +
+ Class2) (MRB)
 BC0..BCn used for Class2
BC2 Class2
computing unreserved
BW for class n
 Current implementation
supports BC0 and BC1
Class-Based Tunnel Selection: CBTS
Tunnel1  EXP-based selection between

Tunnel10 Prefix1
Tunnel2
multiple tunnels to same
Tunnel3 destination
Tunnel4 Tunnel20 Prefix2
Tunnel5  Local mechanism at
head-end (no IGP extensions)
Tunnel6
Tunnel7
Tunnel30 Prefix3  Tunnel master bundles tunnel
members
FIB
 Tunnel selection configured on
Prefix1 Tunnel10
Tunnel Bundle tunnel master (auto-route, etc.)
Prefix2 Tunnel20  Bundle members configured
Prefix3 Tunnel30 with EXP values to carry
 Bundle members may be
Master (Tunnel10)
configured as default
 Supports VRF traffic,
Member (Tunnel1)
IP-to-MPLS and MPLS-to-MPLS
Member (Tunnel2)
switching paths
Policy-based Tunnel Selection: PBTS
Tunnel1
Tunnel2
Prefix1  EXP-based selection between
multiple tunnels to same destination
Tunnel3
Tunnel4 Prefix2  Local mechanism at
Tunnel5
head-end
Tunnel6
Tunnel7 Prefix3  Tunnels configured via policy-
class with one EXP value to carry
FIB  Tunnel without policy-class
Prefix1, exp 5 tunnel-te1 acts as default
Prefix1, * tunnel-te2
Prefix2, exp 5 tunnel-te3  No IGP extensions
Prefix2, exp 2 tunnel-te4
 Supports VRF traffic,
IP-to-MPLS and MPLS-to-MPLS
Prefix3, exp 5 tunnel-te6
switching
Tunnel-based Admission Control
IP/MPLS
IP IP
RSVPoDiffServ RSVPoDiffServ
Tunnel
RSVP flows (IPv4)
Aggregation / Aggregation /
De-aggregation De-aggregation
 Tunnel aggregates RSVP (IPv4) flows
 No per-flow state in forwarding plane (only DiffServ)
 No per-flow state in control plane within MPLS TE network
 RSVP enhancements enable end-to-end admission control solution
(Receiver Proxy, Sender Notification, Fast Local Repair)
Traffic Protection
Traffic Protection Using MPLS TE Fast Re-Route
(FRR)
 Sub-second recovery
against node/link failures
IP/MPLS
R1
 Scalable 1:N protection
R8  Greater protection
granularity
R2
 Cost-effective alternative to
1:1 protection
 Bandwidth protection
Primary TE LSP
Backup TE LSP
FRR Link Protection Operation
 Requires pre-signalled next-

hop (NHOP) backup tunnel IP/MPLS
 Point of Local Repair (PLR) 25

R3
swaps label and pushes 22 22
backup label
R1 R2 R6 R7
 Backup terminates
on Merge Point (MP) where
16 22
traffic re-joins primary
 Restoration time expected
under ~50 ms R5
Primary TE LSP
Backup TE LSP
FRR Node Protection Operation
 Requires pre-signalled next-

next-hop (NNHOP) backup IP/MPLS
tunnel R3
25
 Point of Local Repair (PLR) 36 36
swaps next-hop label and

pushes R1 R2 R4 R6 R7
backup label
 Backup terminates on Merge 16 22 36
Point (MP) where traffic re-

joins primary
R5
 Restoration time depends on
failure detection time
Primary TE LSP
Backup TE LSP
Bidirectional Forwarding Detection
Trigger for FRR
 FRR relies on quick PLR

failure detection IP/MPLS
R1
 Some failures may not
produce loss of signal or R8
alarms on a link
R2
 BFD provides light-weight
neighbor connectivity failure
detection
 Preferred over RSVP Hellos
BFD session
Primary TE LSP
Backup TE LSP
Bandwidth Protection
 Backup tunnel with

associated bandwidth IP/MPLS
capacity R3
 Backup tunnel may or may

not actually signal bandwidth
R1 R2 R4 R6 R7
 PLR will decide best backup
to protect primary
(nhop/nnhop, backup-bw,
class-type, node-protection
flag)
R5
Primary TE LSP
Backup TE LSP
AutoTunnel: Primary Tunnels
What’s the Problem?
 FRR can protect

TE Traffic IP/MPLS
R1
 No protection mechanism for
IP or LDP traffic R8
 How to leverage FRR R2

for all traffic?
 What if protection
desired without traffic
engineering?
Primary TE LSP
Backup TE LSP
What’s the Solution?
Forward all traffic through a one-hop protected primary TE tunnel
 Create protected one-hop
tunnels on all TE links
Priority 7/7
IP/MPLS
R1 Bandwidth 0
Affinity 0x0/0xFFFF
R8 Auto-BW OFF
Auto-Route ON
R2 Fast-Reroute ON
Forwarding-Adj OFF
Load-Sharing OFF
 Tunnel interfaces not shown on
router configuration
 Configure desired backup
tunnels (manually or
Primary TE LSP automatically)
Configuring AutoTunnel Primary Tunnels (Cisco
IOS)
mpls traffic-eng tunnels Enable auto-tunnel

mpls traffic-eng auto-tunnel primary onehop primary
mpls traffic-eng auto-tunnel primary tunnel-num min 900 max 999
!
Range for tunnel
interfaces
AutoTunnel: Backup Tunnels
What’s the Problem?
 MPLS FRR requires backup

tunnels to be preconfigured
IP/MPLS
R1
 Automation of backup tunnels is
desirable
R8
R2
Primary TE LSP
Backup TE LSP
What’s the Solution?
Create backup tunnels automatically as needed
 Detect if a primary tunnel
IP/MPLS requires protection and is not
R1
protected
R8  Verify that a backup tunnel
doesn’t already exist
R2
 Compute a backup path to
NHOP and NNHOP
excluding the protected
facility
 Optionally, consider shared
risk link groups during
Primary TE LSP
backup path computation
Backup TE LSP
 Signal the backup tunnels
Configuring AutoTunnel Backup Tunnels (Cisco
IOS)
mpls traffic-eng tunnels Enable auto-tunnel

mpls traffic-eng auto-tunnel backup nhop-only backup (NHOP
mpls traffic-eng auto-tunnel backup tunnel-num min 1900 max 1999 tunnels only)
mpls traffic-eng auto-tunnel backup timers removal unused 7200
mpls traffic-eng auto-tunnel backup srlg exclude preferred
! Range for tunnel
interfaces
Tear down unused

backup tunnels
Consider SRLGs
preferably
Shared Risk Link Group (SRLG)
Layer-3 Plus underlying
Layer-3 Topology
Optical Topology
SRLG 10
IP/MPLS R2-R4
IP/MPLS
R2-R3
R2 R4 R2 R4
R1 R5 R1 R5 SRLG 20
R4-R2
R4-R3
R3 R3
SRLG 30
R3-R2
R3-R4
 Some links may share same physical resource (e.g. fiber, conduit)
 AutoTunnel Backup can force or prefer exclusion of SRLG
to guarantee diversely routed backup tunnels
 IS-IS and OSPF flood SRLG membership as an additional
link attribute
What About Path Protection?
 Primary and standby share head and tail,

but expected to be diversely routed
IP/MPLS
 Generally higher restoration times R1
compared to local protection
 Doubles number of TE LSPs (1:1 R8

protection)
R2
 May be an acceptable solution for restricted
topologies (e.g. rings)
 Cisco IOS
Separate path option sequences for primary
and standby
Explicit paths only
No path diversity
 Cisco IOS XR Primary TE LSP

Single path-option sequence for primary and Backup TE LSP
standby
Explicit and dynamic paths
Automatic path diversity (node-link, node, link)
P2MP TE LSP Traffic Protection
 No new protocol extensions

to support FRR
 Protection requirement IP/MPLS R4
applies to all destinations
R2
 P2P LSP as backup tunnel R1
for a sub-LSP
 No changes to label stacking R3 R5
procedure
 Only link protection
supported
 Head-end protection
Primary TE LSP
requires path redundancy
(live-standby / live-live) Backup TE LSP
Head End Resiliency Models
Live-Standby
PE5 PE6  Redundant TE LSPs with different ingress PEs
Live TE LSP (Live) (Standby)
Standby TE LSP P1 P2  LSPs may or may not be disjoint
 Link failures generally protected via FRR

IP/MPLS
P3 P4
 Several bandwidth options for Standby TE LSP
Same bandwidth reservation as Live path
PE1 PE4 No bandwidth reservation
Adaptive bandwidth reservation (auto-bandwidth)
PE2 PE3
Live-Live PE5 PE6  Redundant P2MP LSPs with different ingress

(Live) (Live)
Live TE LSP P1 P2
and egress PEs
 LSPs are generally disjoint

IP/MPLS
P3 P4  Receiver or near-receiver stream selection and
switchover
PE1 PE4  FRR generally not a requirement
 Same bandwidth reservation on both TE LSPs

PE2 PE3
Inter-Domain Traffic Engineering
Inter-Domain Traffic Engineering: Introduction
 Domain defined as an IGP area or autonomous system

 Head end lacks complete network topology to perform path
computation in both cases
 Two path computation approaches
Per-domain (ERO loose-hop expansion)
Distributed (Path Computation Element)
Per-Domain Path Computation Using ERO Loose-
hop Expansion
Inter-AS TE LSP
IP/MPLS ASBR1 ASBR2 IP/MPLS

R4
R2 R6
R7
R1
R3 ASBR3 ASBR4 R5
ERO ERO ERO ERO

ASBR4 (Loose) expansion R3, ASBR3, ASBR4 R7 (Loose) expansion R5, R7
R7 (Loose) R7 (Loose)
R1 ASBR4
Topology Topology
database database
Distributed Path Computation using Path
Computation Element
Path Computation Request
Backward Recursive PCE-based Path Computation Reply
Computation (BRPC) Path Computation Element
TE LSP
IP/MPLS ABR1 IP/MPLS ABR2 IP/MPLS

R4
R2 R6
R7
R1
R3
ABR3 ABR4 R5
Area 1 Area 0 Area 3
R1 ABR1 ABR2
Path (cost 500): Path1 (cost 400): ABR1, ABR2, R4, R6 R7 Path1 (cost 300): ABR2, R4, R6 R7
R3, ABR3, ABR4, R5, R7
Path2 (cost 300): ABR3, ABR4, R5, R7 Path2 (cost 200): ABR4, R5, R7
Virtual Virtual
Shortest Shortest
Path Tree Path Tree
R1 ABR1 ABR2
Topology Topology Topology
database database database
(area 0) (area 3)
Configuring PCE (Cisco IOS XR)
Headend
interface tunnel-te1 Use discovered
description FROM-ROUTER-TO-DST2 PCEs for path
ipv4 unnumbered Loopback0 computation
destination 172.16.255.1
path-option 10 dynamic pce Static route mapping
! IP traffic to tunnel-
router static te1
address-family ipv4 unicast
172.16.255.1/32 tunnel-te1
!
! Declare peer down if
no keepalive in 30s
PCE
mpls traffic-eng
Advertise PCE
capability with
pce deadtimer 30
address
pce address ipv4 172.16.255.129 172.16.255.129
pce keepalive 10
!
Send per keepalive
every 10s
Inter-Domain TE – Fast Re-route
Primary TE LSP
Backup TE LSP

R4
R2 R6
R7
R1
R3 ASBR3 ASBR4 R5
 Same configuration as single domain scenario

 Support for node-id sub-object required to implement
ABR/ASBR node protection
 Node-id helps point of local repair (PLR) detect a merge point
(MP)
Inter-Domain TE
Take into Account before Implementing
 Semantics of link attributes across domain boundaries

 Semantics of TE-Classes across domain boundaries for DS-
TE
 Auto-route destinations creates a static route to tunnel
destination and facilitates traffic selection
 Auto-route announce not applicable for traffic selection
General Deployment Considerations
Should RSVP-TE and LDP be Used
Simultaneously?
 Guarantees forwarding of VPN traffic if a TE LSP fails

 May be required if full mesh of TE LSPs not in use
 Increased complexity
How Far should Tunnels Span?
56 TE LSP
PE
 PE-to-PE Tunnels
PE
More granular control on traffic
PE PE forwarding
Larger number of TE LSPs
PE PE
 P-to-P Tunnels
PE PE Requires IP tunnels or LDP over
TE tunnels to carry VPN traffic
(deeper label stack)
12 TE LSP Fewer TE LSPs
PE PE May be extended with PE-P
tunnels
P P
PE PE
PE PE
P P
PE PE
MPLS TE on Link Bundles
 Different platforms support

different link bundles
Ethernet
POS
Multilink PPP
R1 R2
 Bundles appear as single link in
topology database
Link Bundle  Same rules for link state
flooding
 Hard TE LSP preemption if
bundle bandwidth becomes
insufficient
 Configurable minimum number
of links to maintain bundle active
 Bundle failure can act as trigger
for FRR
Scaling Signaling (Refresh Reduction)
SRefresh Message
MSG_Id
List
MSG_Id
List
Path Resv
MSG_Id MSG_Id
State State
LSP1 22 … LSP1 43 …
LSP2 62 … LSP2 37 …
: : … : : …
LSPn 94 … LSPn 29 …
 Message Identifier associated with Path/Resv state

 Summary Refresh (SRefresh) message with message_id list
to refresh soft state
 SRefresh only replaces refresh Path/Resv messages
Summary
Summary
 Technology Overview
 Traffic Protection
Explicit and constrained-
based routing Link/node protection
(auto-tunnel)
TE protocol extensions
(OSPF, ISIS and RSVP) Bandwidth protection
P2P and P2MP TE LSP  Inter-Domain Traffic

Engineering
 Bandwidth optimization
Inter-Area
Planned (full mesh, Inter-AS (Authentication,
auto-tunnel) policy control)
Reactive
 General Deployment
 TE for QoS Considerations
DS-TE (MAM, RDM) MPLS TE and LDP
CBTS PE-to-PE vs. P-to-P tunnels
TE over Bundles
Scaling signaling
Recommended Reading
BRKMPL- 2104
Please complete your Session Survey
We value your feedback
 Don't forget to complete your online session evaluations after each session.
Complete 4 session evaluations & the Overall Conference Evaluation
(available from Thursday) to receive your Cisco Live T-shirt.
 All surveys can be found on our onsite portal and mobile website:
www.ciscolivelondon.com/mobile
 You can also access our mobile site and complete

your evaluation from your mobile phone:
1. Scan the Access Code
(See http://tinyurl.com/qrmelist for software,
alternatively type in the access URL)
2. Login
3. Complete and Submit the evaluation http://m.cisco.com/mat/cleu12/
Thank you.
Backup Slides
Distribution Using OSPF (Cisco IOS)
mpls traffic-eng tunnels Enable MPLS TE on this

! node
interface POS0/1/0
ip address 172.16.0.0 255.255.255.254 Enable MPLS TE on this
mpls traffic-eng tunnels interface
Attribute flags
ip rsvp bandwidth 100000 TE metric
!
router ospf 100 Maximum reservable
log-adjacency-changes
bandwidth
network 172.16.0.0 0.0.255.255 area 0 Enable TE extensions (TE
mpls traffic-eng router-id Loopback0 router id and area)
!
Distribution Using IS-IS (Cisco IOS XR)
router isis DEFAULT Enable wide metric format
is-type level-2-only and TE extensions (TE Id,
net 49.0001.1720.1625.5129.00
address-family ipv4 unicast router level)
metric-style wide
mpls traffic-eng level 2
! Configuration mode for
interface Loopback0 RSVP global and interface
passive
address-family ipv4 unicast commands
!
!
interface POS0/3/0/0 Maximum reservable
address-family ipv4 unicast bandwidth
!
!
!
rsvp
interface POS0/3/0/0 MPLS TE global and
bandwidth 100000 interface commands
!
!
mpls traffic-eng
admin-weight 5 TE metric
attribute-flags 0x8
!
! Attribute flags
Per-VRF Tunnel Selection (Cisco IOS)
ip vrf RED Loopback1 advertised

rd 65172:2 as next hop for VRF
route-target export 65172:2 RED
route-target import 65172:2
bgp next-hop Loopback1
!
interface Loopback0
ip address 172.16.255.1 255.255.255.255
!
interface Loopback1
ip address 172.16.255.101 255.255.255.255
!
interface Tunnel1
description FROM-ROUTER-VRF-TO-DST1
ip unnumbered Loopback0
tunnel destination 172.16.255.2 Remote next hop
tunnel mode mpls traffic-eng mapped to Tunnel1
!
ip route 172.16.255.102 255.255.255.255 Tunnel1
!
Network with MPLS TE
Service
Differentiation  A solution when:
- No differentiation required
- Optimization required
 Full mesh or selective

deployment to avoid
over-subscription
TE  Increased network utilization
Resource  Adjust link load to actual
Optimization link capacity
 No notion of traffic classes
Load Capacity
Network with MPLS DiffServ
and MPLS TE
Service
Differentiation
 A solution when:
- Differentiation required
DiffServ - Optimization required
+
TE
 Adjust class capacity
to expected class load
 Adjust class load to actual
class capacity for one class
Resource
Optimization  Alternatively, adjust
link load to actual
Class2 link capacity
Load Capacity
Class1
Load Capacity
Load Capacity
Class3
Network with MPLS DiffServ
and MPLS DS-TE
Service
Differentiation
 A solution when:
DiffServ
+
DS-TE
- Strong differentiation
required
- Fine optimization required
 Control both load and

capacity per class
 Adjust class capacity to
Resource expected class load
Optimization
 Adjust class load to actual
Class2 class capacity
Load Capacity
Class1
Load Capacity
Load Capacity
Class3
Pre-standard DS-TE Implementation
 Only supports Russian Dolls Model (RDM)

for bandwidth constraints
 No changes to RSVP-TE specs to signal desired pool (leverages
ADSPEC object in PATH messages)
- Sub-pool TE LSPs signaled as guaranteed service
- Global pool TE LSPs signaled as controlled-load service
 Modified OSPF-TE and ISIS-TE advertisements

to include two pools at 8 priority levels each
(16 entries per link total)
 Available on IOS and IOS XR
What Is New in IETF DS-TE Implementation?
 Supports both RDM and MAM (Maximum Allocation Model) for

bandwidth constraints
 New CLASSTYPE object in RSVP-TE to signal desired class-
type (unused by “class-type 0” for backward compatibility with
non-DS-TE)
 Minor Changes to OSPF-TE and ISIS-TE bandwidth
advertisements
-Same “unreserved bandwidth” sub-TLV (8 entries)
as non-DS-TE interpreted according to local definition
of TE-Class (class-type/preemption priority)
-New BC sub-TLV
 Operates in migration or IETF mode in Cisco IOS
 Developed simultaneously for IOS and IOS XR
TE-Class Definition Examples
TE-Class definition MUST be consistent throughout the network
Default TE-Class definition
Priority 0 Priority 1 Priority 2 Priority 3 Priority 4 Priority 5 Priority 6 Priority 7
CT0 (Global) TE-Class4 TE-Class0
CT1 (Sub) TE-Class5 TE-Class1
TE-Class definition compatible with non-DS-TE

CT0 (Global) TE-Class0 TE-Class1 TE-Class2 TE-Class3 TE-Class4 TE-Class5 TE-Class5 TE-Class7
CT1 (Sub)
User-defined TE-Classes with no preemption between class-types

CT0 (Global) TE-Class4 TE-Class5 TE-Class6 TE-Class7
CT1 (Sub) TE-Class0 TE-Class1 TE-Class2 TE-Class3
User-defined TE-Classes with preemption between/within class-types

CT0 (Global) TE-Class1 TE-Class3 TE-Class5 TE-Class7
CT1 (Sub) TE-Class0 TE-Class2 TE-Class4 TE-Class6
MAM vs. RDM
MAM RDM
One BC per CT One or more CTs per BC
Sum of all BCs may exceed maximum BC0 always equals to maximum
reservable bandwidth reservable bandwidth
Preemption not required to provide Preemption required to provide bandwidth

bandwidth guarantees per CT guarantees per CT
Bandwidth efficiency and protection Provides bandwidth efficiency and

against QoS degradation are mutually protection against QoS degradation
exclusive simultaneously
Configuring DS-TE Classes and Bandwidth
Constraints (Cisco IOS)
RDM
mpls traffic-eng tunnels Enable IETF DS-
mpls traffic-eng ds-te mode ietf TE
mpls traffic-eng ds-te te-classes
te-class 0 class-type 1 priority 0
te-class 2 class-type 1 priority 2 Explicit TE-Class
te-class 3 class-type 1 priority 3 definition
te-class 6 class-type 0 priority 6 RDM bandwidth
te-class 7 class-type 0 priority 7 constraints
!
interface POS0/1/0
ip address 172.16.0.0 255.255.255.254
mpls traffic-eng tunnels Enable IETF DS-
ip rsvp bandwidth rdm bc0 155000 bc1 55000 TE and use default
!
TE-Class definition
MAM
mpls traffic-eng ds-te mode ietf Enable MAM
mpl traffic-eng ds-te bc-model mam
!
interface POS0/1/0 MAM bandwidth
ip address 172.16.0.0 255.255.255.254 constraints
ip rsvp bandwidth mam max-reservable-bw 155000 bc0 100000 bc1 55000
!
Configuring DS-TE Tunnel (Cisco IOS)
interface Tunnel1 Signal Tunnel1

description FROM-ROUTER-TO-DST1-CT0 with CT0 (priority
ip unnumbered Loopback0 and CT must
no ip directed-broadcast
tunnel destination 172.16.255.3 match valid TE-
tunnel mode mpls traffic-eng Class)
tunnel mpls traffic-eng bandwidth 100000 class-type 0
!
interface Tunnel2
description FROM-ROUTER-TO-DST1-CT1
tunnel destination 172.16.255.3 Signal Tunnel2
with CT1 (priority
tunnel mpls traffic-eng bandwidth 50000 class-type 1 and CT must
tunnel mpls traffic-eng path-option 10 dynamic match valid TE-
! Class)
Configuring DS-TE Classes and Bandwidth
Constraints (Cisco IOS XR)
RDM
rsvp RDM bandwidth
bandwidth rdm bc0 155000 bc1 55000 constraints
!
!
mpls traffic-eng
! Enable IETF DS-
ds-te mode ietf
ds-te te-classes TE
te-class 3 class-type 1 priority 3 Explicit TE-Class
te-class 4 class-type 0 priority 4 definition
te-class 7 class-type 0 priority 7 MAM bandwidth
!
! constraints
MAM
rsvp
interface POS0/3/0/0 Enable IETF DS-
bandwidth mam max-reservable-bw 155000 bc0 100000 bc1 55000 TE and use default
!
! TE-Class definition
mpls traffic-eng
!
ds-te mode ietf
ds-te bc-model mam Enable MAM
!
Configuring DS-TE Tunnels
(Cisco IOS XR)
interface tunnel-te1 Signal tunnel-te1

with CT0 (priority
priority 5 5 and CT must
signalled-bandwidth 100000 class-type 0 match valid TE-
destination 172.16.255.2 Class)
!
priority 0 0 Signal tunnel-te2
signalled-bandwidth 50000 class-type 1 with CT1 (priority
destination 172.16.255.2 and CT must
! match valid TE-
Class)
Configuring CBTS (Cisco IOS)
interface Tunnel1 Tunnel1 will carry
ip unnumbered Loopback0 packets with MPLS
tunnel destination 172.16.255.2 EXP 5
tunnel mpls traffic-eng exp 5 Tunnel2 will carry
! packets with MPLS
interface Tunnel2
ip unnumbered Loopback0 EXP other than 5
tunnel destination 172.16.255.2
tunnel mpls traffic-eng exp default Tunnel10 defined as
! bundle master with
interface Tunnel10 Tunnel2 and Tunnel1
tunnel destination 172.16.255.2 as members
tunnel mpls traffic-eng exp-bundle master
tunnel mpls traffic-eng exp-bundle member Tunnel1
tunnel mpls traffic-eng exp-bundle member Tunnel2
!
ip route 192.168.0.0 255.255.255.0 Tunnel10 CBTS performed on
! prefix 192.168.0.0/24
using Tunnel10
Configuring PBTS (Cisco IOS XR)
interface tunnel-te1 tunnel-te1 will carry
ipv4 unnumbered Loopback0 packets with MPLS
autoroute announce EXP 5
policy-class 5
tunnel-te2 will carry
path-option 20 dynamic packets with MPLS
! EXP other than 5
interface tunnel-te2 (default tunnel)
autoroute announce
!
Configuring Tunnel-based Admission
Control (Cisco IOS)
interface Tunnel1 Signaled bandwidth
tunnel destination 172.16.255.2 RSVP local policy (200
tunnel mode mpls traffic-eng flows max, 1Mbps per flow
tunnel mpls traffic-eng autoroute announce max)
tunnel mpls traffic-eng bandwidth 100000 Maximum reservable
tunnel mpls traffic-eng path-option 10 dynamic bandwidth
ip rsvp policy local default
maximum senders 200 Interface QoS policy
maximum bandwidth single 1000 (DiffServ)
forward all
ip rsvp bandwidth 100000 Maximum reservable
! bandwidth
interface GigabitEthernet3/3/0
ip address 192.168.0.1 255.255.255.254 Act as RSVP receiver
service-policy output OUT-POLICY proxy on this interface
ip rsvp bandwidth percent 10
ip rsvp listener outbound reply No RSVP flow
ip rsvp data-packet classification none
classification
ip rsvp resource-provider none
!
No RSVP flow queuing
ip rsvp qos
! Enable per-flow RSVP
Configuring FRR (Cisco IOS)
Primary Tunnel
interface Tunnel1
description FROM-ROUTER-TO-DST1-FRR
tunnel mpls traffic-eng bandwidth 20000
tunnel mpls traffic-eng path-option 10 dynamic Indicate the desire for
tunnel mpls traffic-eng fast-reroute
! local protection during
signaling
Backup Tunnel
interface Tunnel1 Explicitly routed backup
description NNHOP-BACKUP
to 172.16.255.2 with
tunnel destination 172.16.255.2 zero bandwidth
!
interface POS1/0/0
ip address 172.16.192.5 255.255.255.254 Use Tunnel1 as backup
mpls traffic-eng tunnels for protected LSPs
mpls traffic-eng backup-path Tunnel1 through POS1/0/0
ip rsvp bandwidth
!
Configuring FRR (Cisco IOS XR)
Primary Tunnel
description FROM-ROUTER-TO-DST1-FRR
fast-reroute
path-option 10 dynamic Indicate the desire for local
! protection during signaling
Backup Tunnel
interface tunnel-te1 Explicitly routed backup to
description NHOP-BACKUP 172.16.255.130 with zero
bandwidth
!
mpls traffic-eng
backup-path tunnel-te 1 Use tunnel-te1 as backup
! for protected LSPs through
! POS0/3/0/0
Why One-Hop Tunnels?
 CSPF and SPF yield same

results (absence
of tunnel constraints) IP/MPLS
R1
 Auto-route forwards
all traffic through R8
one-hop tunnel
R2
 Traffic logically mapped to
tunnel but no label imposed
(imp-null)
 traffic is forwarded
as if no tunnel was
in place
Primary TE LSP
What’s the Solution? (Cont.)
 Backup tunnels are

IP/MPLS preconfigured
R1
-Priority 7/7
-Bandwidth 0
R8
-Affinity 0x0/0xFFFF
R2 -Auto-BW OFF
-Auto-Route OFF
-Fast-Reroute OFF
-Forwarding-Adj OFF
-Load-Sharing OFF
 Backup tunnel interfaces and

Primary TE LSP
paths not shown on router
Backup TE LSP configuration
Configuring SRLG (Cisco IOS)
mpls traffic-eng tunnels Force SRLG

mpls traffic-eng auto-tunnel backup nhop-only exclusion during
mpls traffic-eng auto-tunnel backup srlg exclude force backup path
! computation
interface POS0/1/0
ip address 172.16.0.0 255.255.255.254
mpls traffic-eng srlg 15
mpls traffic-eng srlg 25 Interface member
ip rsvp bandwidth of SRLG 15 and
! 25
interface POS1/0/0
ip address 172.16.0.2 255.255.255.254
mpls traffic-eng srlg 25
ip rsvp bandwidth Interface member
! of SRLG 25
Configuring Path Protection (Cisco IOS)
interface Tunnel1
tunnel mpls traffic-eng path-option 20 explicit name PATH2 Standby path to be
tunnel mpls traffic-eng path-option protect 10 explicit name PPATH1 used for PATH1
tunnel mpls traffic-eng path-option protect 20 explicit name PPATH2
!
Standby path to be
used for PATH2
Configuring Enhanced Path Protection (Cisco
IOS)
mpls traffic-eng path-option list name PATH-LST List of standby

path-option 10 explicit name PE1-P3-P4-PE2
paths
!
interface Tunnel1
tunnel mpls traffic-eng path-option 10 explicit name PE1-P1-P2-PE2
tunnel mpls traffic-eng path-option protect 10 list name PATH-LST
! Use path list to
protect primary
path
Configuring Path Protection
(Cisco IOS XR)
interface tunnel-te1 Signal an

description FROM-ROUTER-TO-DST1 acceptable (node-
ipv4 unnumbered Loopback0 link, node, link
signalled-bandwidth 100000 diverse) standby
TE LSP based on
path-option
affinity f mask f sequence
path-protection
!
Inter-Domain TE – TE LSP Reoptimization
Inter-AS TE
LSP before
reoptimization
R4
R2 R6 Inter-AS TE
R7
MakeR1 LSP after
before reoptimization
break
R3 ASBR3 ASBR4 R5
PATH
Path re-evaluation PathErr
request Preferable
Path exists
 Reoptimization can be timer/event/admin triggered

 Head end sets ‘path re-evaluation request’ flag
(SESSION_ATTRIBUTE)
 Head end receives PathErr message notification from boundary
router if a preferable path exists
 Make-before-break TE LSP setup can be initiated after PathErr
notification
Configuring Inter-Area Tunnels
(Cisco IOS)

!
interface Tunnel1
ip unnumbered Loopback0 Loose-hop path
tunnel mpls traffic-eng path-option 10 explicit name LOOSE-PATH
! Static route
ip route 172.16.255.7 255.255.255.255 Tunnel1 mapping IP traffic
! to Tunnel1
ip explicit-path name LOOSE-PATH enable
next-address loose 172.16.255.3
!
List of ABRs as
loose hops
Configuring Inter-Area Tunnels with Auto-route
Destinations (Cisco IOS)

!
interface Tunnel1 Generate static
ip unnumbered Loopback0 route for tunnel
no ip directed-broadcast destination pointing
tunnel destination 172.16.255.7 to Tunnel1
tunnel mpls traffic-eng autoroute destination
! Loose-hop path
ip route 172.16.255.7 255.255.255.255 Tunnel1
!
!
List of ABRs as
loose hops
Configuring Inter-Area Tunnels
(Cisco IOS XR)
explicit-path name LOOSE-PATH List of ABRs as

index 1 next-address loose ipv4 unicast 172.16.255.129 loose hops
index 2 next-address loose ipv4 unicast 172.16.255.131
!
destination 172.16.255.2 Loose-hop path
path-option 10 explicit name LOOSE-PATH
!
router static
address-family ipv4 unicast
172.16.255.2/32 tunnel-te1 Static route
! mapping IP traffic
to tunnel-te1
Configuring Inter-AS Tunnels
(Cisco IOS)
mpls traffic-eng tunnels Loose-hop path

!
interface Tunnel1
tunnel destination 172.31.255.5 Static route
tunnel mode mpls traffic-eng mapping IP traffic
tunnel mpls traffic-eng priority 7 7 to Tunnel1
tunnel mpls traffic-eng bandwidth 1000
!
ip route 172.31.255.5 255.255.255.255 Tunnel1
! List of ASBRs as
loose hops
!
Inter-Domain TE – Authentication and Policy
Control

R4
R2 R6
R7
R1
Policy
R3 ASBR3 ASBR4 R5
 Authentication and policy control desirable for Inter-AS

deployments
 ASBR may perform RSVP authentication (MD5/SHA-1)
 ASBR may enforce a local policy for Inter-AS TE LSPs (e.g.
limit bandwidth, message types, protection, etc.)
Configuring Inter-AS TE at ASBR
(Cisco IOS)
mpls traffic-eng tunnels Authentication
! key
key chain A-ASBR1-key
key 1
key-string 7 151E0E18092F222A
!
Add ASBR
interface Serial1/0 link to TE
ip address 192.168.0.1 255.255.255.252 topology
mpls traffic-eng passive-interface nbr-te-id 172.16.255.4 nbr-igp-id ospf 172.16.255.4 database
ip rsvp bandwidth
ip rsvp authentication key-chain A-ASBR1-key
ip rsvp authentication type sha-1 Enable RSVP
ip rsvp authentication authentication
!
router bgp 65024
no synchronization
bgp log-neighbor-changes
Process
neighbor 172.24.255.3 remote-as 65024 signaling
neighbor 172.24.255.3 update-source Loopback0 from AS
neighbor 192.168.0.2 remote-as 65016
no auto-summary
65016 if FRR
! not
ip rsvp policy local origin-as 65016 requested
no fast-reroute
maximum bandwidth single 10000 and 10M or
forward all less
!
Distributed Path Computation with Backward
Recursive PCE-based Computation (BRPC)
 Head-end sends request to a path computation element

(PCE)
 PCE recursively computes virtual shortest path tree (SPT) to
destination
 Head-end receives reply with virtual SPT if a path exists
 Head-end uses topology database and virtual SPT to compute
end-to-end path
 Head-end can discover PCEs dynamically or have them
configured statically
Configuring Inter-Area Tunnels with Autoroute
Destinations (Cisco IOS)
interface Tunnel1 Create static route

ip unnumbered Loopback0 to tunnel
destination
tunnel mpls traffic-eng autoroute destination (172.16.255.7)
!
ip explicit-path name LOOSE-PATH enable Loose-hop path
!
List of ABRs as
loose hops
Configuring MPLS TE and LDP Simultaneously
(Cisco IOS)
mpls label protocol ldp Enable LDP

Enable MPLS TE
!
interface POS0/1/0
ip address 172.16.0.0 255.255.255.254 Enable MPLS TE
mpls traffic-eng tunnels on interface
mpls ip
ip rsvp bandwidth 155000 Enable MPLS
! forwarding for IP
(LDP)
Configuring MPLS TE and LDP Simultaneously
(Cisco IOS XR)
rsvp Configuration mode for

interface POS0/3/0/0 RSVP global and interface
bandwidth 155000 commands
!
!
mpls traffic-eng Configuration mode for
interface POS0/3/0/0 MPLS TE global and
! interface commands
!
mpls ldp
! Configuration mode for
! LDP global and interface
commands
Configuring LDP Over a TE Tunnel
(Cisco IOS)
mpls label protocol ldp Enable LDP

!
interface Tunnel1
mpls ip
Enable MPLS
forwarding for IP
(LDP) on Tunnel1
!
Configuring LDP Over a TE Tunnel (Cisco IOS XR)
priority 0 0
autoroute announce
!
rsvp
bandwidth 155000
!
!
mpls traffic-eng
!
!
mpls ldp
Enable LDP on
!
tunnel-te1
!
!
MPLS TE on Ethernet Bundle (Cisco IOS)
interface Port-channel1 Enable MPLS TE on this

ip address 172.16.0.0 255.255.255.254
interface
mpls traffic-eng tunnels Attribute flags
TE metric
ip rsvp bandwidth percent 100 Maximum reservable
! bandwidth (100% of total
interface GigabitEthernet2/0/0 bundle bandwidth)
no ip address
channel-protocol lacp LACP as channel protocol
channel-group 1 mode active
Associate with Port-
!
channel1 and enable LACP
interface GigabitEthernet2/0/1 (non-passive)
no ip address
channel-protocol lacp LACP as channel protocol
channel-group 1 mode active
Associate with Port-
!
channel1 and enable LACP
(non-passive)
MPLS TE on Ethernet Bundle (Cisco IOS XR)
interface Bundle-Ether1 Interface for bundle id 1

ipv4 address 172.16.0.1 255.255.255.254
!
interface GigabitEthernet0/1/0/0
bundle id 1 mode active Associate with bundle id 1
negotiation auto
!
(Bundle-Ether1) and
interface GigabitEthernet0/1/0/1 enable LACP (non-passive)
bundle id 1 mode active
negotiation auto
!
router ospf 172
area 0 Associate with bundle id 1
mpls traffic-eng (Bundle-Ether1) and
interface Bundle-Ether1
network point-to-point
enable LACP (non-passive)
!
interface Loopback0
passive enable
!
!
Enable OSPF on bundle
!
rsvp Maximum reservable
interface Bundle-Ether1 bandwidth on bundle
bandwidth 2000000
!
!
mpls traffic-eng Enable MPLS TE on
interface Bundle-Ether1
!
bundle
!
Configuring Refresh Reduction
(Cisco IOS)

!
interface POS0/1/0
ip address 172.16.0.0 255.255.255.254
ip rsvp bandwidth 100000
!
router ospf 100
log-adjacency-changes
network 172.16.0.0 0.0.255.255 area 0
Enable refresh
!
reduction
ip rsvp signalling refresh reduction
!
* Enabled by default in Cisco IOS XR

Recommended Reading
Please visit the Cisco Store for suitable reading.

Please complete your Session Survey
We value your feedback
 Don't forget to complete your online session evaluations after each session.
Complete 4 session evaluations & the Overall Conference Evaluation
(available from Thursday) to receive your Cisco Live T-shirt
 Surveys can be found on the Attendee Website at www.ciscolivelondon.com/onsite

which can also be accessed through the screens at the Communication Stations
 Or use the Cisco Live Mobile App to complete the

surveys from your phone, download the app at
www.ciscolivelondon.com/connect/mobile/app.html
1. Scan the QR code

(Go to http://tinyurl.com/qrmelist for QR code reader
software, alternatively type in the access URL above)
2. Download the app or access the mobile site
3. Log in to complete and submit the evaluations
http://m.cisco.com/mat/cleu12/
Thank you.

Live! - Deploying MPLS Traffic Engineering

Uploaded by

Copyright:

Available Formats

Live! - Deploying MPLS Traffic Engineering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Live! - Deploying MPLS Traffic Engineering

Uploaded by

Copyright:

Available Formats

Deploying MPLS Traffic Engineering

Follow us on Twitter for real time updates of the event:

 We value your feedback- don't forget to complete your online session

 Introduces explicit routing

 Supports admission control

 Additional link characteristics

 IS-IS or OSPF flood link information

 Tunnel signaled with TE

 Multiple traffic selection options

mpls traffic-eng tunnels Enable MPLS TE on this

router ospf DEFAULT Enable TE extensions on

feature isis Enable MPLS TE on this

router isis DEFAULT Enable TE extensions (TE

interface Tunnel1 Destination (tunnel

explicit-path name PATH1 Explicit PATH1

Consider links with

mpls traffic-eng Explicit PATH1

IP/MPLS  Branch point: Node where

 CSPF executed per destination R2

 Source sends unique PATH

 One or more IP multicast

IP/MPLS  Groups mapped via static

Tunnel2 (192.168.5.1, 232.0.0.3)

 Provides a layer-2 multicast

mpls traffic-eng destination list name P2MP-LIST-DST1 Destination list with

ip multicast mpls traffic-eng Enable IPv4

TE LSP with IP (VPN)

Point-to-Point SLA Protection

Physical Topology Tunnel mesh to satisfy

 Tries to optimize underlying physical topology based on traffic matrix

 MPLS LSR MIB

Communities POP POP

 Each member automatically

mpls traffic-eng tunnels Enable Auto-tunnel Mesh

 Selective deployment of tunnels when highly-utilized links are identified

Load Capacity Load Capacity

Load Capacity Load Capacity

 A solution when:  A solution when:  A solution when:

 Enables per-class traffic engineering

 Unique class definition and constraint

Bandwidth Constraints  Two classes (class-types) in current

 BW pool applies to one

Tunnel1  EXP-based selection between

RSVP flows (IPv4)

 Requires pre-signalled next-

 Point of Local Repair (PLR) 25

swaps label and pushes 22 22

 Requires pre-signalled next-

swaps next-hop label and

Point (MP) where traffic re-

 FRR relies on quick PLR

 Backup tunnel with

 Backup tunnel may or may

 FRR can protect

 How to leverage FRR R2

mpls traffic-eng tunnels Enable auto-tunnel

 MPLS FRR requires backup

mpls traffic-eng tunnels Enable auto-tunnel

Tear down unused