Optimum Implementation of TI-LFA
Optimum Implementation of TI-LFA
ARPANET - 1974
2
https://en.wikipedia.org/wiki/ARPANET
What IGPs Currently Offer?
● Sub-second convergence times (< 1000ms)
● Reactive Approach
○ Fault Recognition
○ Information Flooding
3
Source: T Anji Kumar and MHM Prasad. Enhanced multiple routing configurations for fast ip network recovery from multiple failures.
The Goals of Networks Today
● Real time services
○ VoIP / Video
○ Cloud Software
○ Financial Trading
○ Experimental
Where might virtual reality lead us?
Not good enough David Ramos/Getty Images
4
Network in a Normal State
5
Failure Occurs
6
The Reactive Approach: Step 1
7
The Reactive Approach: Step 2
8
Segment Routing (or SPRING)
● Every node is labelled
○ Node ID
● Every link is labelled
○ Adjacency ID
● MPLS labels
● IGP to distribute Segment IDs (SIDs) creating a full mesh
9
Protective Fast Reroute Solutions
Point of Local
rLFA TI-LFA
Repair 5
(PLR)
5
5
6
5 5 100
11
Link Protection
12
Node Protection
13
Link / Node Protection Summary
14
Fate Sharing
15
16
SURFnet8 Topology
● Interfaces that share the same fate due to:
○ Line card sharing
○ Optical path sharing
● Juniper Routers used that support:
○ TI-LFA
○ SPRING
○ Node Protection
○ Fate Sharing 17
Optical cable sharing
Line card
sharing
18
Research Questions
1. How do different TI-LFA configurations perform when
implementing Node / Link Protection and Fate Sharing?
3. Is fate sharing necessary for all links that share the same
line card or optical layer?
19
Methodology
● Desk research
○ Understand novel concepts
● Define experiments
○ Create topology
● Analyse results
● Draw conclusions
20
Our Test Topology
21
Our Test Topology
22
Our Test Topology
23
Our Test Topology
24
List of Experiments
Experiment Sub Experiment
With TI-LFA
With TI-LFA
Multiple link failures with source as PLR With a single backup path
26
Baseline SR with Extra Hop
● SR without TI-LFA vs SR with TI-LFA (without crosslink)
27
Results
28
Multiple Link Failures 1
29
Multiple Link Failures 2
30
Multiple Link Failures 3
31
Multiple Link Failures 4
32
Multiple Backup Paths
Route output
33
Experiment: Fate Sharing
● TI-LFA with fate sharing
34
Results
35
Multiple Broken Links
Average ~500ms
36
Multiple Broken Links
Average ~500ms
37
Multiple ECMPs
Average ~52ms
38
Fate Sharing Enabled
Average ~30ms
39
Link | Node Protection
Link protection
Node protection
40
41
42
43
Discussion
● TI-LFA works well with ECMPs, so ECMPs should be
implemented on SURFnet8
46
Acknowledgements
● Special thanks:
○ Marijke Kaat and Wouter Huisman
○ SURFnet Team
47
Q&A
48