Segment Protection M Vinod Kumar Abhay Karandikar Topology 1 5 4 3 2 This port has FDB entry such that the two ESPs to DA5 egress from the same port These two ports though have shared forwarding towards DA5 do not have shared forwarding for traffic from SA 5 ID: 579940
Download Presentation The PPT/PDF document "1 Terminology:" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
1
Terminology:
Segment Protection
M Vinod Kumar
Abhay KarandikarSlide2
Topology
1
5
4
3
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= 5Slide3
Topology 2
1
5
4
3
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
6Slide4
Infrastructure
1
5
4
3
2
Traffic over this Link/LAN can be protected using backup resources comprising of: LAN 3-6, LAN 6-4 and node 6
6
Backup resourcesSlide5
Infrastructure Segment
1
5
4
3
2
Primary Infrastructure Segment (resources shown in violet
colour
)
6
Protection Domain
Backup Infrastructure Segment (resources shown in cream
colour
)Slide6
Infrastructure Segment Protection
1
5
4
3
2
Primary Infrastructure Segment (P-IS) has its own fault monitoring mechanism
6
Infrastructure Segment Protection Domain
Backup Infrastructure Segment (B-IS) has its own fault monitoring mechanismSlide7
ISP OAM
1
5
4
3
2
The P-IS fault monitoring is independent of TESI fault-monitoring/OAM
6
The B-IS fault monitoring is independent of TESI fault-monitoring/OAM
Infrastructure Segment Protection DomainSlide8
P-IS Fault and Protection
1
5
4
3
2
Fault here will forward the traffic over backup infrastructure segment
6
Infrastructure Segment Protection Domain
TESIs are pre-provisioned along the Backup Infrastructure Segment for sub-50ms protection switchingSlide9
Data Path Fault
1
5
4
3
2
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
6
TESI or Data-path
mis
-configuration is outside the scope of ISP
Infrastructure Segment Protection (ISP) DomainSlide10
Example of Data-path Segments
1
5
4
3
2
Examples of Data path (DP) segment-
It is configuration that enables flow of TESI
6
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 faultSlide11
Types of Segments
There are two types of SegmentsInfrastructure Segment
LANs and intervening bridgeHas its own Segment OAMData Path SegmentForwarding information configured on the bridges
Has its own E2E OAMSlide12
Types of Segment Protection
Therefore we have two types of segment protectionInfrastructure 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-pathSlide13
Example of Unprotected IS
1
5
4
3
2
Example of Infrastructure Segment that cannot protect the TESIs
6Slide14
Example of Adjacent ISP Domain- 1
1
5
4
3
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.Slide15
Example of Adjacent ISP Domain- 2
1
5
4
3
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.Slide16
7
8
Example of Adjacent ISP Domain- 3
1
5
4
3
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.Slide17
TerminologySlide18
Some Points to be Noted
Segment Protection is not a replacement for e2e TESI protectionPrimary reason- infrastructure failure in certain parts of the network
Some links/nodes/LANs are more prone to failureSPS will be enabled for only these links/nodes/LANsSlide19
Questions?