Graceful Shutdown
This presentation is the property of its rightful owner.
Sponsored Links
1 / 7

Zafar Ali ([email protected]) Jean Philippe Vasseur ([email protected]) Anca Zamfir ([email protected]) PowerPoint PPT Presentation


  • 62 Views
  • Uploaded on
  • Presentation posted in: General

Graceful Shutdown in MPLS Traffic Engineering Networks draft-ietf-ccamp-mpls-graceful-shutdown-01.txt. Zafar Ali ([email protected]) Jean Philippe Vasseur ([email protected]) Anca Zamfir ([email protected]). Agenda. Changes from the last version.

Download Presentation

Zafar Ali ([email protected]) Jean Philippe Vasseur ([email protected]) Anca Zamfir ([email protected])

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Zafar ali zali cisco jean philippe vasseur jpv cisco anca zamfir ancaz cisco

Graceful Shutdown in MPLS Traffic Engineering Networksdraft-ietf-ccamp-mpls-graceful-shutdown-01.txt

Zafar Ali ([email protected])

Jean Philippe Vasseur ([email protected])

Anca Zamfir ([email protected])


Agenda

Agenda

  • Changes from the last version.

  • How review comments received on the list are addressed?

67th IETF, San Diego, November 2006


Graceful shutdown and stitched lsp es

Graceful Shutdown and Stitched LSP-es

Area 0

ABR-1

  • Component LSP segments are signaled as distinct TE LSPs in the control plane. In this example, the ABRs are responsible for "cross-connecting" the LSP segments.

  • Ingress LSR of each LSP segment performs make-before-break to move traffic from segment affected by GS of a node/ link, to a new segment avoiding node/ link under GS.

    • In this example, the ABR-1 performs make-before-break operation when GS-1 event is triggered.

Area 1

Area 2

ABR-2

GS-1

LSP Segment 3

LSP Segment 1

LSP Segment 2

67th IETF, San Diego, November 2006


Graceful shutdown and frr segment recovery

Graceful Shutdown and FRR/ Segment Recovery

  • When PLR/ merge node receive a Path Error with Graceful Shutdown indication,

    • It MUST forward the Path Error to the Ingress node.

    • Based on a local decision, PLR/ merge node MAY trigger FRR/ segment recovery.

67th IETF, San Diego, November 2006


Graceful shutdown and bundled links

Graceful Shutdown and Bundled Links

  • Local repair by using a different component link within the bundled TE link is NOT adapted.

    • If the local repair cannot be performed (due to lack of bandwidth), Ingress LSR is needed to move the traffic away from this bundled TE link.

    • It’s always a good practice to deal with exception cases using the same generic framework.

67th IETF, San Diego, November 2006


Overloading error code from loose path reoptimization draft

Overloading error code from Loose Path Reoptimization Draft

  • Expected behavior of the Ingress LSR is exactly in the two drafts.

  • Both drafts require Ingress LSR to trigger Make-before-brake on the LSP affected by a Graceful showdown of a link/ node.

    • This ID inherits the Ingress behavior from draft-ietf-ccamp-loose-path-reopt-02.txt, which says-

      • “Upon receiving an RSVP PERR message with Error code 25 and Error sub- code 7 (Local link maintenance required) or 8 (Local node maintenance required), the Head-end LSR SHOULD perform a TE LSP reoptimization”.

67th IETF, San Diego, November 2006


Next steps

Next Steps

  • Addressed all outstanding comments.

  • Need to decide if this ID should be Informational or Standard’s Track.

  • The ID defines a new error sub-code for PathError. It also defines specific protocol behavior.

    • 9 (TBA) Local component link maintenance required.

  • After finalizing this debate and addressing any further comments, authors will do a quick a re-spin and request WG for the last call.

67th IETF, San Diego, November 2006


  • Login