1 / 7

Extensions to RSVP-TE for LSP Ingress Local Protection

Extensions to RSVP-TE for LSP Ingress Local Protection. draft-chen-mpls-p2mp-ingress-protection-09. Huaimo Chen, Raveendra Torvi Ning So, Autumn Liu, Alia Atlas, Yimin Shen Fengman Xu, Mehmet Toy, Lei Liu. Merged the following two drafts into one

jewel
Télécharger la présentation

Extensions to RSVP-TE for LSP Ingress Local Protection

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. Extensions to RSVP-TE for LSP Ingress Local Protection draft-chen-mpls-p2mp-ingress-protection-09 Huaimo Chen, Raveendra Torvi Ning So, Autumn Liu, Alia Atlas, Yimin Shen Fengman Xu, Mehmet Toy, Lei Liu

  2. Merged the following two drafts into one • draft-chen-mpls-p2mp-ingress-protection-08 • draft-torvi-mpls-rsvp-ingress-protection-00 • Some Ingress Failure Detection Modes in details are added • Backup and Source Detect Failure (New) • Backup Detects Failure • Source Detects Failure • Next Hops Detect Failure • Covers On-path (backup ingress on path of LSP) cases (New) Updates from the last version

  3. Backup and Source Detect Failure (1/2) Backup ingress (PE6) and source (CE3) detect ingress (PE5) failure and control the traffic delivery concurrently 1. Ingress PE5 fails Primary LSP BFD Backup LSP P2MP PE1 BFD-1 BFD-2 CE1 Data PE2 PE5 Source CE3 P1 PE6 PE3 Data CE2 PE4 2. Source CE3 detects it by BFD-1 and switches traffic to backup ingress PE6 2. Backup ingress PE6 detects it by BFD-2 and puts traffic into backup LSP to P1 3. Traffic merged into primary LSP at P1 3

  4. Backup and Source Detect Failure (2/2) Link PE5—PE6 fails: Traffic from source CE3 to ingress PE5 is transported by primary LSP to destinations as before, no traffic to backup ingress PE6 from source CE3 BFD 1. Link PE5—PE6 fails Primary LSP Backup LSP P2MP PE1 BFD-1 BFD-2 CE1 Data Source PE2 PE5 CE3 P1 PE6 PE3 Data CE2 PE4 2. Backup ingress PE6 detects it by BFD-2 and puts traffic from source CE3 into backup LSP, but no traffic from source CE3 4

  5. On-path case (1/2) Backup ingress (PE6) is a next hop of ingress (PE5) , i.e., backup ingress (PE6) is on the path of primary LSP Primary LSP 1. Ingress PE5 fails BFD PE1 BFD-1 BFD-2 P2P LSP CE1 Data PE2 P1 PE5 Source CE3 PE6 PE3 2. Source CE3 detects failure and switches traffic to backup ingress PE6 2. Next hop PE6 of primary ingress as backup ingress detects failure and puts traffic into primary LSP 5

  6. On-path case (2/2) Backup ingress (PE6) is a next hop of ingress (PE5), i.e., backup ingress (PE6) is on the path of primary LSP 1. Ingress PE5 fails Primary LSP BFD Backup LSP P2MP LSP PE1 BFD-1 BFD-2 CE1 Data PE7 CE1 PE2 PE5 Source P1 CE3 P2 PE3 Data CE2 P3 PE6 PE4 2. Source CE3 detects failure and switches traffic to backup ingress PE6 2. One next hop PE6 of primary ingress as backup ingress detects failure, multicasts traffic to its next hops (P2, P3) along primary LSP and imports traffic into backup LSP to the other next hops (PE7, P1) of primary ingress PE5 6

  7. Next Step • Welcome comments • Request for working group adoption

More Related