130 likes | 155 Views
This document introduces Proxy LSP Ping for optimized network-wide processing of MPLS Echo Requests, enhancing scalability and control while reducing the number of replies needed. The method supports mLDP tracing, PHOP information, and P2MP-TE tracing, improving network efficiency.
E N D
Proxy Remote LSP Ping<draft-swallow-mpls-remote-lsp-ping-00.txt> IETF-67 swallow@cisco.com
Proxy Ping Motivation • Scalability • Control • number of replies • network wide processing of MPLS Echo Requests • Scoping can limit the number of replies but still requires processing at the ‘replying’ node • In some cases, scoping is not desired, but responses are only needed from a small region of the topology • mLDP support • Trace from leaf to route • Previous Hop Information
Mcast LSP Trace Responding Nodes This pass: Total: 5 14 7 21 9 30 2 2 3 5 4 9
Proxy LSP Ping • Proxy Echo Request • Out of band message to a node on the multicast tree • Requests node to insert an inband MPLS Echo Request • Optionally asks for a Proxy Echo Reply • Proxy Echo Reply • Verifies that FEC was valid and that the Echo Reply will be/was sent • Supplies PHOP information (if requested)
Proxy LSP Ping Proxy Echo Request Echo Request
Acknowledgement & PHOP Proxy Echo Request Proxy Echo Reply Echo Request Replies Supressed
P2MP-TE Tracing • Root node usually knows the tree topology • Suppose a few nodes are failing in a very large tree • Fault is likely to be close to those nodes • Proxy Echo Request allows traceroute to proceed in reverse • Greatly limits the number of nodes replying
P2MP-TE Proxy Echo Request Echo Request Note: Echo Replies not shown
Next-Hop Scoping • Requester • Adds the next-hop IP address to the Proxy Echo Parameters Object • Sends Proxy Echo Request to proxy node • Proxy node • Only sends an MPLS Echo Request on the listed interfaces
P2MP-TE Next-Hop Scoping Proxy Echo Request Echo Request
Multicast LDP (mLDP) Tracing • Multicast LDP LSPs are initiated by the leaf nodes • Root node may not know the tree topology • Failure is most likely to be detected at leaf • Leaf is a logical place to begin tracing • Proxy Echo Responses can be used to sequentially learn the PHOPs from a leaf to the route • Tree is traced from leaf to root
mLDP Traceroute (Using Next-Hop Scoping) Proxy Echo Request Proxy Echo Reply Echo Request Echo Reply
Next Steps • Is this a good idea? • Working group draft?