1 / 18

Terminology: Segment Protection

Terminology: Segment Protection. M Vinod Kumar Abhay Karandikar. Topology. 1. 3. 4. 5. 2. This port has FDB entry such that the two ESPs to DA=5 egress from the same port. These two ports though have shared forwarding towards DA=5, do not have shared forwarding for traffic from SA= 5.

sanam
Download Presentation

Terminology: Segment 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. Terminology: Segment Protection M Vinod Kumar Abhay Karandikar

  2. Topology 1 3 4 5 2 This port has FDB entry such that the two ESPs to DA=5 egress from the same port These two ports though have shared forwarding towards DA=5, do not have shared forwarding for traffic from SA= 5

  3. Topology 2 1 5 3 4 6 2 This port has FDB entry such that the two ESPs egress from the same port These two ports though have shared forwarding towards node 4, do not have shared forwarding for traffic from node 4 to DA=5 (or 6) and vice-versa on port 43

  4. Infrastructure 1 3 4 5 2 6 Traffic over this Link/LAN can be protected using backup resources comprising of: LAN 3-6, LAN 6-4 and node 6 Backup resources

  5. Infrastructure Segment 1 3 4 5 2 6 Primary Infrastructure Segment (resources shown in violet colour) Protection Domain Backup Infrastructure Segment (resources shown in cream colour)

  6. Infrastructure Segment Protection 1 3 4 5 2 6 Primary Infrastructure Segment (P-IS) has its own fault monitoring mechanism Infrastructure Segment Protection Domain Backup Infrastructure Segment (B-IS) has its own fault monitoring mechanism

  7. ISP OAM 1 3 4 5 2 6 The P-IS fault monitoring is independent of TESI fault-monitoring/OAM Infrastructure Segment Protection Domain The B-IS fault monitoring is independent of TESI fault-monitoring/OAM

  8. P-IS Fault and Protection 1 3 4 5 2 6 Fault here will forward the traffic over backup infrastructure segment Infrastructure Segment Protection Domain TESIs are pre-provisioned along the Backup Infrastructure Segment for sub-50ms protection switching

  9. Data Path Fault 1 3 4 5 2 6 If TESI is misconfigured on node 3 or 4 such that it does not flow over link 3-4, it is data-path fault; it is out-side the scope Infrastructure Segment Protection (ISP) Domain TESI or Data-path mis-configuration is outside the scope of ISP

  10. Example of Data-path Segments 1 3 4 5 2 6 Examples of Data path (DP) segment- It is configuration that enables flow of TESI Infrastructure Segment Protection (ISP) Domain Many Data paths can flow over the same Infrastructure Segment IS fault implies DP fault DP fault does not imply IS fault

  11. Types of Segments There are two types of Segments • Infrastructure Segment • LANs and intervening bridge • Has its own Segment OAM • Data Path Segment • Forwarding information configured on the bridges • Has its own E2E OAM

  12. Types of Segment Protection Therefore we have two types of segment protection • Infrastructure Segment Protection (ISP) • Protection of traffic from failure of LANs and intervening bridges • Data-path Segment Protection (DSP) • Protection from misconfiguration of TESI or Data-path

  13. Example of Unprotected IS 1 3 4 5 2 6 Example of Infrastructure Segment that cannot protect the TESIs

  14. Example of Adjacent ISP Domain- 1 1 3 4 5 2 6 7 • Allow maintenance activities to be performed independently in different infrastructure segment protection domain. • Allow maintenance activities to be performed in one segment of a network without disabling protection in another inf. segment. • Localize changes in traffic distribution due to failure or maintenance actions.

  15. Example of Adjacent ISP Domain- 2 1 3 4 5 2 6 • Allow maintenance activities to be performed independently in different infrastructure segment protection domain. • Allow maintenance activities to be performed in one segment of a network without disabling protection in another inf. segment. • Localize changes in traffic distribution due to failure or maintenance actions.

  16. Example of Adjacent ISP Domain- 3 7 8 1 3 4 5 2 6 • Allow maintenance activities to be performed independently in different infrastructure segment protection domain. • Allow maintenance activities to be performed in one segment of a network without disabling protection in another inf. segment. • Localize changes in traffic distribution due to failure or maintenance actions.

  17. Some Points to be Noted • Segment Protection is not a replacement for e2e TESI protection • Primary reason- infrastructure failure in certain parts of the network • Some links/nodes/LANs are more prone to failure • SPS will be enabled for only these links/nodes/LANs

  18. Questions?

More Related