Domain Border Router Resiliency Using Anycast SID Compaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-domain Segment Routing networks, managing domain border router resiliency with anycast segments is challenging due to the difficulty in tracking and managing numerous anycast prefixes, which complicates segment compaction and path computation.
Innovation Solution
The approach involves performing segment compaction after path computation, identifying domain border routers, and utilizing anycast SIDs for resiliency without requiring specific anycast prefixes to be entered as constraints, allowing the Path Computation Element (PCE) to infer and generate anycast segments dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If anycast segments are used for domain border router resiliency, then reliability is improved, but device complexity increases due to difficulty in tracking and managing numerous anycast prefixes
Solution Approach 1:
The system performs preliminary actions by pre-computing and storing anycast prefix-to-SID mappings in a database before path computation occurs. This allows the PCE to retrieve appropriate anycast SIDs during path computation without manually tracking numerous prefixes, thereby maintaining reliability while reducing operational complexity
Solution Approach 2:
The invention introduces an intermediary mechanism (database storing anycast prefix-SID mappings) that mediates between the path computation process and the anycast prefix management. This intermediary allows automatic resolution of anycast SIDs without requiring direct manual management of numerous prefixes, thus resolving the contradiction between reliability and complexity
2Reliability
If anycast prefixes are entered as constraints during path computation, then domain border router resiliency is achieved, but ease of operation deteriorates due to difficulty in tracking and managing anycast prefixes
Solution Approach 1:
The system implements self-service by automatically resolving anycast SIDs during path computation without requiring manual intervention to track or manage prefixes. The PCE autonomously queries the database for appropriate anycast SIDs based on the computed path, making the operation simple while maintaining resiliency
Solution Approach 2:
The database serves as an intermediary that automatically provides anycast SID information during path computation. This eliminates the need for operators to manually track and manage anycast prefixes, significantly improving ease of operation while preserving domain border router resiliency
3Ease of operation
If segment compaction is performed after path computation, then ease of operation is improved, but device complexity increases due to additional processing steps required
Solution Approach 1:
The system performs preliminary actions by pre-storing anycast prefix-SID mappings in a database before path computation. This allows the segment compaction process to simply query and retrieve pre-computed information rather than performing complex real-time analysis, thereby improving ease of operation while limiting the increase in processing complexity to simple database queries
Data Source
AI summary
Systems and methods for domain Border Router (BR) resiliency with segment compaction in Segment Routing include obtaining a compressed segment list for a calculated path in a Segment Routing network, wherein the Segment Routing network includes a plurality of domains with the calculated path being through at least two domains, wherein the compressed segment list includes a plurality of Segment Identifiers (SID) each SID identifying a segment, and wherein, when expanded, the compressed segment list matches the calculated path; analyzing the compressed segment list for any domain border routers between two domains of the at least two domains to determine associated anycast SID for the any domain border routers; and utilizing the associated anycast SID in the compressed SID list for resiliency between the two domains.