A Novel Mechanism for Resilient Routing Suksant Sae Lor , Raul Landa, - - PowerPoint PPT Presentation

a novel mechanism for resilient routing
SMART_READER_LITE
LIVE PREVIEW

A Novel Mechanism for Resilient Routing Suksant Sae Lor , Raul Landa, - - PowerPoint PPT Presentation

A Novel Mechanism for Resilient Routing Suksant Sae Lor , Raul Landa, and Miguel Rio {s.lor, r.landa, m.rio}@ee.ucl.ac.uk Network & Services Research Laboratory Department of Electronic & Electrical Engineering University College London


slide-1
SLIDE 1

Multi-Service Networks 2010, Cosener's House, Abingdon

A Novel Mechanism for Resilient Routing

Suksant Sae Lor, Raul Landa, and Miguel Rio {s.lor, r.landa, m.rio}@ee.ucl.ac.uk

Network & Services Research Laboratory Department of Electronic & Electrical Engineering University College London

slide-2
SLIDE 2

Introduction & Motivation

  • Network failures cause packet losses
  • Re-convergence is not fast enough
  • Existing approaches are not universal

S D Single failures? Dual failures? Link failures? Node failures? Multiple failures? Shared-risk link group? Speed of convergence: Packet loss rates: Sensitive applications can’t tolerate this!

slide-3
SLIDE 3

Existing Resilient Mechanisms

  • Loop-Free Alternates (LFAs)
  • Not-via addresses
  • Multiple Routing Configurations (MRC)
  • Failure-Insensitive Routing (FIR)
  • SafeGuard
slide-4
SLIDE 4

Existing Resilient Mechanisms

  • Loop-Free Alternates (LFAs)
  • Not-via addresses
  • Multiple Routing Configurations (MRC)
  • Failure-Insensitive Routing (FIR)
  • SafeGuard

Aim to solve only “SINGLE FAILURES”!

  • Failure-Carrying Packets (FCP)
slide-5
SLIDE 5

Existing Resilient Mechanisms

  • Loop-Free Alternates (LFAs)
  • Not-via addresses
  • Multiple Routing Configurations (MRC)
  • Failure-Insensitive Routing (FIR)
  • SafeGuard

Aim to solve only “SINGLE FAILURES”!

  • Failure-Carrying Packets (FCP)

Large overheads Difficult to implement

slide-6
SLIDE 6

Packet Re-cycling (PR) Overview

  • Handles any number of failures
  • Pre-computed paths; hence, fast re-route
  • No major modifications on current routing
  • Minimal packet/memory overheads
  • Shortest path routing under failure-free scenario
  • Routing & cycle following in case of failures
slide-7
SLIDE 7

Cellular Graph Embeddings

  • Draw a network graph, G on a closed surface, S

A D G B E H C F

slide-8
SLIDE 8

Cellular Graph Embeddings

  • Minimum genus embedding: cellular cycle system

A D G B E H C F C1 C2 C3 C4

slide-9
SLIDE 9

Cellular Graph Embeddings

  • Each link is included in exactly 2 cycles

A D G B E H C F C1 C2 C3 C4 Main cycle Complementary Cycle

slide-10
SLIDE 10

Packet Re-cycling (PR) Routing & Cycle Following

  • Routing using normal routing table (no failures)

A D G B E H C F C1 C2 C3 C4

slide-11
SLIDE 11

Packet Re-cycling (PR) Routing & Cycle Following

  • Cycle following when a failure is encountered

A D G B E H C F C1 C2 C3 C4

slide-12
SLIDE 12

Packet Re-cycling (PR) Routing & Cycle Following

  • Only PR bit (1 bit) is used to handle single failures

A D G B E H C F C1 C2 C3 C4

slide-13
SLIDE 13
  • Forwarding loop without termination condition

Packet Re-cycling (PR) Routing & Cycle Following

A D G B E H C F C1 C2 C3 C4

slide-14
SLIDE 14
  • Terminates only if it is closer to the destination!

Packet Re-cycling (PR) Cycle Following Termination Condition

A D G B E H C F C1 C2 C3 C4 4 H 5 G 3 E 6 D 1 C 2 B 7 A

  • No. of hops to F

Node

slide-15
SLIDE 15
  • G detects a failure, it performs cycle following

Packet Re-cycling (PR) Cycle Following Termination Condition

A D G B E H C F C1 C2 C3 C4 4 H 5 G 3 E 6 D 1 C 2 B 7 A

  • No. of hops to F

From

slide-16
SLIDE 16
  • A detects a failure, its performs cycle following

Packet Re-cycling (PR) Cycle Following Termination Condition

A D G B E H C F C1 C2 C3 C4 4 H 5 G 3 E 6 D 1 C 2 B 7 A

  • No. of hops to F

From

slide-17
SLIDE 17
  • B detects a failure, it performs routing

Packet Re-cycling (PR) Cycle Following Termination Condition

A D G B E H C F C1 C2 C3 C4 4 H 5 G 3 E 6 D 1 C 2 B 7 A

  • No. of hops to F

From

slide-18
SLIDE 18

Benefits

  • Minimal overheads while providing full protection:

– Packet header

  • 1 bit for single failure cases
  • Order of log2(d), where d is the network diameter
  • For d 7, pool 2 DSCP can be used

– Memory

  • Additional column in the routing table
  • Cycle following tables (no. of interfaces x 3)
slide-19
SLIDE 19

Incurred Stretch

  • Stretch: cost(re-routing path) / cost(shortest path)

Abilene with 1 failure cases Abilene with 4 failure cases (worst-case scenarios)

slide-20
SLIDE 20

Conclusion

  • Resilience is important
  • Some applications cannot tolerate losses
  • Most mechanisms handle only single failure cases
  • PR provides a full-failure protection with minimal
  • verheads
slide-21
SLIDE 21

Thank you! Q & A