proxy remote lsp ping

13
© 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential Presentation_I D 1 Proxy Remote LSP Ping <draft-swallow-mpls-remote-lsp-ping-00.txt> IETF-67 [email protected]

Upload: odessa

Post on 18-Jan-2016

62 views

Category:

Documents


0 download

DESCRIPTION

Proxy Remote LSP Ping . IETF-67 [email protected]. Proxy Ping Motivation. Scalability Control number of replies network wide processing of MPLS Echo Requests - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 1

Proxy Remote LSP Ping

<draft-swallow-mpls-remote-lsp-ping-00.txt>

IETF-67

[email protected]

Page 2: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 2

Proxy Ping Motivation

ScalabilityControl

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 supportTrace from leaf to route

Previous Hop Information

Page 3: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 3

Mcast LSP Trace

Responding Nodes

This pass:

Total:

2

2

3

5

4

9

5

14

7

21

9

30

Page 4: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 4

Proxy LSP Ping

Proxy Echo RequestOut 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 ReplyVerifies that FEC was valid and that the Echo Reply will be/was sent

Supplies PHOP information (if requested)

Page 5: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 5

Proxy LSP Ping

Proxy Echo Request

Echo Request

Page 6: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 6

Acknowledgement & PHOP

Replies SupressedProxy Echo Request

Proxy Echo Reply

Echo Request

Page 7: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 7

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

Page 8: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 8

P2MP-TE

Proxy Echo Request

Echo Request

Note: Echo Replies not shown

Page 9: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 9

Next-Hop Scoping

Requester Adds the next-hop IP address to the Proxy Echo Parameters Object

Sends Proxy Echo Request to proxy node

Proxy nodeOnly sends an MPLS Echo Request on the listed interfaces

Page 10: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 10

P2MP-TE

Proxy Echo Request

Echo Request

Next-Hop Scoping

Page 11: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 11

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

Page 12: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 12

mLDP Traceroute

Proxy Echo Request

Proxy Echo Reply

Echo Request

Echo Reply

(Using Next-Hop Scoping)

Page 13: Proxy Remote LSP Ping

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 13

Next Steps

Is this a good idea?

Working group draft?