MPLS Traffic Engineering Traffic Protection Using Fast Re-Route (FRR)

MPLS Traffic
Engineering
Traffic Protection
using Fast Re-route
(FRR)
Santiago lvarez
August 2008
MPLS TE FRR
saalvare@cisco.com 2007 Cisco Systems, Inc. All rights reserved. 1
MPLS TE Use Cases
Bandwidth Optimization Tactical
Strategic
R1 IP/MPLS R1 IP/MPLS
R8 R8
R2 R2
Protection Point-to-Point SLA
R1 IP/MPLS R1 IP/MPLS
R8 R8
R2 R2
MPLS TE FRR
Traffic Protection Using MPLS TE Fast
Re-Route (FRR)
Subsecond recovery against
node/link failures
IP/MPLS
R1 Scalable 1:N protection
R8
Greater protection granularity
Cost-effective alternative to
R2
1:1 protection
Bandwidth protection
Primary TE LSP
Backup TE LSP
MPLS TE FRR
FRR Link Protection Operation
Requires next-hop (NHOP)
backup tunnel IP/MPLS
Point of Local Repair (PLR) R3
25
25
swaps label and pushes 22
22 22
22
backup label
R1 R2 R6 R7
Backup terminates
on Merge Point (MP) where
traffic rejoins primary 16
16 22
22
Restoration time expected

under
R5
~50 ms
Primary TE LSP
Backup TE LSP
MPLS TE FRR
FRR Node Protection Operation
Requires next-next-hop
(NNHOP) backup tunnel IP/MPLS
Point of Local Repair (PLR) R3
25
25
swaps next-hop label and 36
36 36
36
pushes
backup label R1 R2 R4 R6 R7
Backup terminates on
Merge Point (MP) where 16
16 22
22 36
36
traffic rejoins primary
Restoration time depends
R5
on failure detection time
Primary TE LSP
Backup TE LSP
MPLS TE FRR
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
MPLS TE FRR
Configuring FRR (Cisco IOS)
Primary Tunnel
interface Tunnel1
description FROM-ROUTER-TO-DST1-FRR
ip unnumbered Loopback0
tunnel destination 172.16.255.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng bandwidth 20000
tunnel mpls traffic-eng path-option 10 dynamic Indicate the desire
tunnel mpls traffic-eng fast-reroute for local protection
! during signaling
Backup Tunnel
interface Tunnel1
description NNHOP-BACKUP
Explicitly routed
ip unnumbered Loopback0 backup to
tunnel destination 172.16.255.2 172.16.255.2 with
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name PATH1 zero bandwidth
!
interface POS1/0/0
ip address 172.16.192.5 255.255.255.254 Use Tunnel1 as
mpls traffic-eng tunnels
mpls traffic-eng backup-path Tunnel1 backup for
ip rsvp bandwidth protected LSPs
!
through POS1/0/0
MPLS TE FRR
Configuring FRR (Cisco IOS XR)
Primary Tunnel
interface tunnel-te1
description FROM-ROUTER-TO-DST1-FRR
ipv4 unnumbered Loopback0
signalled-bandwidth 30000
destination 172.16.255.2
fast-reroute Indicate the desire for
path-option 10 dynamic local protection during
! signaling
Backup Tunnel
interface tunnel-te1 Explicitly routed
description NHOP-BACKUP backup to
ipv4 unnumbered Loopback0 172.16.255.130 with
destination 172.16.255.130
zero bandwidth
path-option 10 explicit name PATH1
!
mpls traffic-eng Use tunnel-te1 as
interface POS0/3/0/0
backup-path tunnel-te 1
backup for protected
! LSPs through
! POS0/3/0/0
MPLS TE FRR
AutoTunnel: Primary Tunnels
Whats the Problem?
FRR can protect

TE Traffic IP/MPLS
R1
No protection mechanism
R8
for IP or LDP traffic
R2
How to leverage FRR
for all traffic?
What if protection
desired without traffic
engineering?
Primary TE LSP
Backup TE LSP
MPLS TE FRR
Whats the Solution?
Forward all traffic through a one-
hop protected primary TE tunnel
Create protected one-hop tunnels
IP/MPLS on all TE links
R1
Priority 7/7
Bandwidth 0
R8
Affinity 0x0/0xFFFF
R2 Auto-BW OFF
Auto-Route ON
Fast-Reroute ON
Forwarding-Adj OFF
Load-Sharing OFF
Tunnel interfaces not shown on
router configuration
Primary TE LSP
Configure desired backup tunnels
(manually or automatically)
MPLS TE FRR
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
MPLS TE FRR
Configuring AutoTunnel Primary Tunnels
(Cisco IOS)

Enable auto-
mpls traffic-eng auto-tunnel primary onehop
tunnel primary
mpls traffic-eng auto-tunnel primary tunnel-num min 900 max 999
! Range for tunnel
interfaces
MPLS TE FRR
AutoTunnel: Backup Tunnels
Whats the Problem?
MPLS FRR requires

backup tunnels to be IP/MPLS
R1
preconfigured
Automation of backup R8
tunnels is desirable R2
Primary TE LSP
Backup TE LSP
MPLS TE FRR
Whats the Solution?
Create backup tunnels
automatically as needed
IP/MPLS Detect if a primary tunnel requires
R1
protection and is not protected
R8 Verify that a backup tunnel
doesnt already exist
R2
Compute a backup path to NHOP
and NNHOP excluding the
protected facility
Optionally, consider shared risk
link groups during backup path
computation
Primary TE LSP
Backup TE LSP
Signal the backup tunnels
MPLS TE FRR
Whats the Solution? (Cont.)
Backup tunnels are
preconfigured
IP/MPLS
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
Primary TE LSP
Backup tunnel interfaces and
paths not shown on router
Backup TE LSP
configuration
MPLS TE FRR
Configuring AutoTunnel Backup Tunnels
(Cisco IOS)

Enable auto-
mpls traffic-eng auto-tunnel backup nhop-only
tunnel backup
mpls traffic-eng auto-tunnel backup tunnel-num min 1900 max 1999 (NHOP tunnels
mpls traffic-eng auto-tunnel backup timers removal unused 7200 only)
mpls traffic-eng auto-tunnel backup srlg exclude preferred
! Range for
tunnel
interfaces
Tear down
unused backup
tunnels
Consider
SRLGs
preferably
MPLS TE FRR
Shared Risk Link Group (SRLG)
Layer-3 Plus
Layer-3 Topology
Physical 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
MPLS TE FRR
Configuring SRLG (Cisco IOS)
mpls traffic-eng tunnels Force SRLG

mpls traffic-eng auto-tunnel backup nhop-only exclusion
mpls traffic-eng auto-tunnel backup srlg exclude force during backup
! path
interface POS0/1/0 computation
ip address 172.16.0.0 255.255.255.254
mpls traffic-eng srlg 15 Interface
mpls traffic-eng srlg 25
member of
ip rsvp bandwidth
SRLG 15 and
!
interface POS1/0/0
25
ip address 172.16.0.2 255.255.255.254
mpls traffic-eng srlg 25 Interface
ip rsvp bandwidth member of
!
SRLG 25
MPLS TE FRR
What About Path Protection?
Primary and backup share
head and tail, but diversely
IP/MPLS
routed R1
No dynamically computed
R8
path diversity
R2
Expected to result in
higher restoration times
compared to local
protection
Doubles number of TE
LSPs (1:1 protection)
Primary TE LSP
May be an acceptable
solution for restricted Backup TE LSP
topologies (e.g. rings)
MPLS TE FRR
saalvare@cisco.com 2007 Cisco Systems, Inc. All rights reserved. http://www.cisco.com/go/mpls 19
P2MP TE LSP Traffic Protection
No new protocol extensions to
support FRR
Protection requirement applies R4
to all destinations IP/MPLS
R2
P2P LSP as backup tunnel for a
sub-LSP R1
No changes to label stacking

procedure R3 R5
Only link protection supported
Primary TE LSP
Backup TE LSP
MPLS TE FRR
Inter-Domain TE Fast Re-route
Primary TE LSP
Backup TE LSP
IP/MPLS ASBR1 ASBR2 IP/MPLS

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)
MPLS TE FRR
Bidirectional Forwarding Detection Trigger for
FRR
FRR relies on quick

IP/MPLS
PLR failure detection R1
Some failures may not R8

produce loss of signal
R2
or alarms on a link
BFD provides light-
weight neighbor
connectivity failure
detection BFD session
Primary TE LSP
Backup TE LSP
MPLS TE FRR
References
MPLS TE FRR
Cisco Documentation
MPLS TE: Link and Node Protection, with RSVP Hellos Support
(with Fast Tunnel Interface Down Detection)
http://www.cisco.com/en/US/partner/docs/ios/12_0s/feature/guide/f
slnph30.html
MPLS Traffic Engineering: BFD-triggered Fast Reroute (FRR)
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp
_te_bfd_frr.html
MPLS Traffic Engineering (TE)--AutoTunnel Primary and Backup
http://www.cisco.com/en/US/partner/docs/ios/12_0s/feature/guide/
gsautotn.html
MPLS Traffic Engineering: Shared Risk Link Groups (SRLG)
http://www.cisco.com/en/US/partner/docs/ios/12_0s/feature/guide/f
s29srlg.html
MPLS TE FRR
Standards
Fast Reroute Extensions to RSVP-TE for LSP Tunnels
http://www.ietf.org/rfc/rfc4090
Routing Extensions in Support of GMPLS
OSPF Extensions in Support of GMPLS
IS-IS Extensions in Support of GMPLS
Definition of a Record Route Object (RRO) Node-Id Sub-Object
MPLS TE FRR

MPLS Traffic Engineering Traffic Protection Using Fast Re-Route (FRR)

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

MPLS Traffic Engineering Traffic Protection Using Fast Re-Route (FRR)

Uploaded by

Copyright:

Available Formats

MPLS Traffic

Protection Point-to-Point SLA

Restoration time expected

PLR will decide best

FRR can protect

mpls traffic-eng tunnels

MPLS FRR requires

mpls traffic-eng tunnels

mpls traffic-eng tunnels Force SRLG

No changes to label stacking

Only link protection supported

IP/MPLS ASBR1 ASBR2 IP/MPLS

Same configuration as single domain scenario

FRR relies on quick

Some failures may not R8

You might also like