Path-Ping and ECMP-Traceroute for IPv6 Overlay Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current OAM tools for network virtualization lack effective methods to validate IPv6 overlay paths and reveal equal cost multipath (ECMP) paths in non-MPLS networks, with ICMP ping being unsuitable and brute force techniques being cumbersome and taxing.
Innovation Solution
The development of path-ping and ECMP-traceroute techniques for IPv6 overlay virtualized networks, involving the generation of echo packets with specific headers and payloads to validate VN context and multipath information, leveraging existing MPLS LSP Ping machinery and extending it for non-MPLS environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If ICMP ping is used for path validation, then simplicity is maintained, but it is unsuitable for overlay virtualized networks and cannot validate VN context or reveal ECMP paths
Solution Approach 1:
The patent introduces an intermediary validation mechanism that operates between the ICMP ping layer and the overlay network paths. Echo packets are used as intermediaries to carry validation information through the network path, enabling VN context validation and ECMP path revelation without directly modifying ICMP ping behavior. This intermediary approach allows compatibility with existing simple ping operations while adding overlay-specific validation capabilities.
Solution Approach 2:
The echo packet mechanism serves multiple functions: it validates VN context information, reveals ECMP paths, and provides path validation for overlay virtualized networks. By making the validation mechanism universal and multi-functional, the patent avoids creating separate specialized tools for each validation need, thereby reducing overall system complexity while improving adaptability.
2Loss of information
If brute force techniques are used to reveal ECMP paths, then path information can be obtained, but the process is cumbersome and taxing on the network
Solution Approach 1:
The patent applies preliminary action by pre-configuring echo packets with validation information and VN context data before transmission. This allows the validation process to proceed efficiently without requiring multiple trial transmissions. The preliminary preparation of packets with all necessary information reduces the need for repeated network transmissions that would otherwise be required in brute force approaches.
Solution Approach 2:
The validation mechanism incorporates feedback through echo reply packets that return path information to the source. This feedback loop allows the system to obtain ECMP path information efficiently by using the network's existing reply mechanism, rather than requiring continuous probing and analysis typical of brute force techniques. The feedback reduces network overhead by consolidating information gathering into targeted exchanges.
3Adaptability or versatility
If existing OAM tools are used, then network management capabilities are maintained, but they cannot validate VN context or reveal ECMP paths in non-MPLS networks
Solution Approach 1:
The patent merges existing OAM capabilities with new validation functions by integrating VN context validation and ECMP path revelation into the existing echo packet framework. This merging approach allows the system to maintain familiar OAM tool interfaces while adding advanced capabilities, thereby reducing the perceived complexity for users while expanding functionality.
Solution Approach 2:
The validation mechanism enables self-service by allowing network devices to automatically validate VN context information and reveal ECMP paths using the echo packet infrastructure. This self-service capability reduces the need for complex external management tools, as the network infrastructure itself performs the validation functions, thereby simplifying the overall OAM toolset while enhancing adaptability.
Data Source
AI summary
In one embodiment, an ingress network virtualization edge (NVE) in a computer network generates an echo packet, and sets an indication in the echo packet that the echo packet is for overlay path validation. In addition, the ingress NVE sets a message type of the echo packet to a generic echo request, and includes virtualization network (VN) context information within the echo packet. Once setting a destination address of the echo packet as an egress NVE address and including an indication to the egress NVE that the echo packet is an operations, administration, and management (OAM) message, the ingress NVE may then send the echo packet toward the egress NVE (e.g., to validate the VN context information and/or to reveal multipath traces).