1 / 7

draft- akiya - mpls - lsp -ping-lag-multipath

draft- akiya - mpls - lsp -ping-lag-multipath. IETF 90, Toronto, Canada. Authors: Nobo Akiya (presenter) George Swallow Stephane Litkowski Bruno Decraene John E. Drake. What is this document about …. Topic of this document:

luz
Download Presentation

draft- akiya - mpls - lsp -ping-lag-multipath

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. draft-akiya-mpls-lsp-ping-lag-multipath IETF 90, Toronto, Canada Authors:Nobo Akiya (presenter)George SwallowStephane LitkowskiBruno DecraeneJohn E. Drake

  2. What is this document about … • Topic of this document: • How do we ensure that we are empowered to validate LSPs when the LSPs are traversing LAGs • Why? • There are LAG specific OAM tools: • LACP, BFD on LAG, etc. • But, validating L2/L3 workings on LAG members is not sufficient to say LSPs over the LAG is working. • Unfortunately, no OAM tools are capable of deterministically exercising LSPs over every LAGmember.

  3. For example … • Take an LSP from Router A to Router D Router A Router B Router C Router D InLabel200 OutLabel200 InLabel300 OutLabel300 InLabel100 OutLabel100 LAG In Label 200(problem#2) Out Label 200(problem#1) • LSP Ping/Trace is taking dark red pathand is successful. • Problem#1: Router B has incorrect out label (!=200) in the forwarding table that bottom LAG member is associated with. • Problem#2: Router C has incorrect in label (!=200) in the forwarding table that bottom LAG member is associated with. • Traffic on this LSP over bottom LAG member can black hole

  4. How can such issue happen… • Many “things” exist between the control plane and data plane on a system. • Inconsistencies between the control plane and data plane often causes traffic black hole. • Depending on the nature of the fault that caused the inconsistency, it is possible for the result (problem) to appear on subset of the forwarding tables. Route Processor Card Control Plane Inter-Card Fabric Line Card Line Card Line Card Data Plane

  5. This document … • Introduces a mechanism for LSP trace to: • Discover multipath info per LAG member • Validate traversal over each LAG member • Extends RFC4379: • LAG Interface Info TLV: used by initiator to request this mechanism, used by responder to describe its capabilities • DDMAP TLV extension: used by responder to describe multipath info and interface index per LAG member • Detailed Interface and Label Stack TLV: used by responder to describe interface index of incoming LAG member

  6. Next steps … • Requesting comments from the WG.

  7. Thank you!Questions/Comments?

More Related