Initiator-Based MPLS Data-Plane Validation for Probe Ambiguity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional MPLS OAM functionality in segment routed networks often creates false positives during data-plane connectivity validation due to multiple interface links and load balancing by intermediate nodes, making it difficult to determine the terminating node for validation probes.
Innovation Solution
An initiator-based data-plane validation method where the initiating node queries a PCE for routing data, stores it locally, sends a probe message with specific instructions, and compares received identification and routing data to validate connectivity, issuing positive or negative responses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional MPLS OAM functionality is used for data-plane connectivity validation, then validation can be performed, but false positives occur due to multiple interface links and load balancing
Solution Approach 1:
The validation process is segmented into distinct phases: probe sending, data collection at terminating nodes, and validation execution by the initiating node. This segmentation allows the system to handle multiple interface links and load balancing scenarios by processing validation data in discrete, manageable steps rather than attempting to validate all paths simultaneously.
Solution Approach 2:
The initiating node performs preliminary actions by querying the PCE for routing data and storing it locally before sending validation probes. This preliminary data collection enables the initiating node to later compare expected routing information with actual probe responses, thereby identifying false positives before final validation conclusions are drawn.
2Productivity
If intermediate nodes perform load balancing between multiple downstream terminating nodes, then traffic distribution is improved, but it becomes difficult to determine which terminating node the validation probe should terminate at
Solution Approach 1:
The system implements feedback mechanisms where terminating nodes send response messages back to the initiating node containing identification data. The initiating node uses this feedback information to determine which terminating node actually received and processed the validation probe, thereby resolving the ambiguity created by load balancing while maintaining efficient traffic distribution.
Solution Approach 2:
The PCE acts as an intermediary that provides routing data and validation instructions to the initiating node. This intermediary component enables the initiating node to understand the load balancing configuration and determine the appropriate terminating node for validation probes without interfering with the actual traffic load balancing operations.
3Reliability
If multiple interface links are configured between nodes, then network redundancy is improved, but traditional MPLS OAM creates false positives during validation
Solution Approach 1:
The validation process applies local quality by having each terminating node provide specific identification data about its own interface and routing information. The initiating node then compares this local data with expected values to determine whether validation success is specific to particular interface links or if it applies generally, thereby maintaining network redundancy while improving validation accuracy.
Data Source
AI summary
Techniques for initiator-based data-plane validation of segment routed, multiprotocol label switched (MPLS) networks are described herein. In examples, an initiating node may determine to validate data-plane connectivity associated with a network path of the MPLS network. The initiating node may store validation data in a local memory of the initiating node. In examples, the initiating node may send a probe message that includes a request for identification data associated with a terminating node. The terminating node may send a probe reply message that includes the identification data, as well as, in some examples, a code that instructs the initiating node to perform validation. In examples, the initiating node may use the validation data stored in memory to compare to the identification data received from the terminating node to validate data-plane connectivity. In some examples, the initiating node may indicate a positive or negative response after performing the validation.