1 / 10

Multiple Routing Configurations IP Fault-Tolerance using Multi-Topology Routing

Multiple Routing Configurations IP Fault-Tolerance using Multi-Topology Routing. Amund Kvalbein, Audun F. Hansen, Tarik Cicic , Stein Gjessing, and Olav Lysne 65th IETF, Dallas, TX, USA March 20 th , 2006. MRC: A Recently Proposed Recovery Scheme.

quinta
Download Presentation

Multiple Routing Configurations IP Fault-Tolerance using Multi-Topology Routing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multiple Routing ConfigurationsIP Fault-Tolerance using Multi-Topology Routing Amund Kvalbein, Audun F. Hansen, Tarik Cicic, Stein Gjessing, and Olav Lysne 65th IETF, Dallas, TX, USA March 20th, 2006

  2. MRC: A Recently Proposed Recovery Scheme • Guarantees single-fault tolerance for both links and nodes (100% coverage) • Supports near-instantaneous, local recovery • Need not the information on whether a link or a node has failed, even if the failed node is the egress

  3. ∞ 2 3 ∞ 1 4 6 5 Multi-Topology Routing • Main idea: use several IP topologies within an IGP cloud to achieve various TE goals: • load balancing • IPv6/Multicast • fault tolerance 2 3 1 4 6 5

  4. MRC Design Summary • An algorithm creates backup configurations • We prohibit forwarding in parts of each backup configuration by two additional levels of link accessibility: • “isolated” links that do not carry traffic • “restricted” links that carry traffic only if no other path available • Description of forwarding functionality • [INFOCOM 2006]

  5. Isolated link: infinite weight Isolated node: all adjacent links at least restricted (wr>|E|wmax) Combinations possible 2 3 1 4 6 5 2 3 1 4 6 5 2 3 1 4 Normal Isolated 6 5 Restricted Isolated Links and Nodes

  6. 1 2 3 4 5 6 7 8 1 2 3 1 2 3 4 5 4 5 6 7 8 6 7 8 Normal + 3 Backup Configurations 1 2 3 4 5 6 7 8 Restricted Normal Isolated

  7. State Implications • Our research shows that only a limited number of configurations is needed, typically 3-6

  8. Generic Forwarding Algorithm Switched configuration before? Packet arrives Yes Drop packet Normal lookup No Lookup in neighbor’s backup configuration Output link failed? Yes Failed link returned? Yes Lookup in own backup configuration No No Forward

  9. Current Research • Load balancing • Multi-fault tolerance (SRG) • Multicast node-fault tolerance • Incremental topology changes • Loop-free convergence

  10. MRC Summary • Guaranteed single-fault tolerance • Covers link and node failures • Need not know the root cause of failure • Rapid, local recovery • No show-stoppers so far, working on • SRG guarantees • Multihoming • Incremental changes • Multicast

More Related