1 / 9

Upstream mapping in Echo Request

This document outlines the enhancements to upstream mapping mechanisms within Multi-Protocol Label Switching (MPLS) networks, specifically addressing the issues encountered with co-routed Label Switched Paths (LSPs). It provides an update on the problem statement, including the lack of responses from MPLS ping and traceroute on downstream paths. The proposed solution incorporates additional upstream information into traceroute packets, aligned with the trace-route mechanism defined in RFC 4379. This aims to ensure effective validation of both Data Structure Mapping (DSMap) and Upstream Mapping (UPMap), ultimately improving network reliability.

alida
Download Presentation

Upstream mapping in Echo Request

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. Upstream mapping in Echo Request draft-ankur-mpls-upstream-mapping-00 AnkurSaxena, Mahesh Jethanandani IETF 89, March 2014, London, UK

  2. Agenda • Problem Statement • Introduction • Update

  3. Problem Statement • Co-routed LSP is not working • MPLS ping – no response • MPLS traceroute – downstream path • Upstream ?

  4. Introduction • Add upstream information to trace-route when trace-route is sent over a co-routed network path.

  5. Updates • Updates trace-route mechanism defined in RFC 4379 • Verify both DSMap and UpStreamMap (UPMap)

  6. UPMap • Similar to DSMap the UPMap TLV will have following information 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MTU | Address Type | DS Flags | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Upstream IP Address (4 or 16 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Upstream Interface Address (4 or 16 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Multipath Type| Depth Limit | Multipath Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . (Multipath Information) . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Upstream Label | Protocol | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Upstream Label | Protocol | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  7. Theory of Ops • LER1 sends packet with DSMap for Label L0 and UPMap for L1 • LSR validates DSMap • If DSMap doesn’t match return DSMapmis-match. • LSR “validates” UPMap • If UPMap does not match return UPMapmis-match • If both UPMap and DSMap do not match return both Maps as mis-match • If both match send UPMap information for L3 L2 L0 LER1 LSR LER2 L1 L3

  8. Theory of Ops (cont.) • LER1 receives the trace-route reply message • - Copies the DSMapfor L2 and UPMap for L3 and sends it to LER2 • LER2 validates DSMap. • - If DSMap doesn’t match return DSMapmis-match. • LER2 “validates” UPMap L2 L0 LER1 LSR LER2 L1 L3

  9. Help • How to truly validate the upstream path? L2 L0 LER1 LSR LER2 L1 L3

More Related