EVPN Route Sequence Number Updating for Virtual Endpoint Mobility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Ethernet Virtual Private Networks (EVPN) struggle to support virtual endpoint mobility scenarios where the Layer 2 or Layer 3 route associated with a virtual endpoint changes after migration, as they assume a fixed one-to-one mapping between MAC and IP routes, which is insufficient for cases like MAC Sharing where routes are mapped differently.
Innovation Solution
The implementation of sequence number updating techniques that determine the sequence number for combined MAC+IP routes based on a parent Layer 2 route, allowing the networking devices to unambiguously determine the most recent location of virtual endpoints even when MAC or IP routes change independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional EVPN assumes fixed one-to-one mapping between MAC and IP routes, then routing simplicity is maintained, but support for virtual endpoint mobility with independent route changes is lost
Solution Approach 1:
The patent segments the previously coupled MAC and IP route updates into independent update mechanisms. MAC route updates and IP route updates are handled separately with independent sequence numbers, allowing virtual endpoints to migrate with changing MAC addresses while maintaining separate IP address bindings. This segmentation enables flexible route mappings without requiring fixed one-to-one correspondence.
Solution Approach 2:
The patent introduces sequence numbers as an additional dimension for route tracking. Instead of relying solely on the fixed MAC-IP mapping relationship, the system adds temporal sequencing information that allows routers to track the most recent route bindings independently. This extra dimension enables the system to handle dynamic route changes while maintaining routing simplicity through versioned updates.
2Adaptability or versatility
If sequence numbers are updated independently for MAC and IP routes, then support for independent route changes is achieved, but route update complexity increases
Solution Approach 1:
The patent divides the route update mechanism into separate MAC route updates and IP route updates, each with its own sequence number. This segmentation allows independent tracking of Layer 2 and Layer 3 route changes without requiring complex coordinated updates. Each route type maintains its own version history, simplifying the management of independent route changes.
Solution Approach 2:
The patent uses sequence numbers as intermediary variables that mediate between route changes and routing decisions. Rather than directly complex MAC-IP bindings, the system uses sequence numbers to indicate the most recent valid binding state. This intermediary mechanism simplifies the overall complexity by providing a clear versioning system that routers can use to determine current route validity.
3Measurement precision
If fixed MAC-IP mapping is enforced, then routing table simplicity is maintained, but accuracy of reachability information during migration deteriorates
Solution Approach 1:
The patent transforms the static MAC-IP mapping into a dynamic system where bindings can change over time. Sequence numbers provide temporal information that allows the system to track the most recent valid route bindings. This dynamic approach ensures that reachability information remains accurate during virtual endpoint migration, as routers can identify the latest valid MAC-IP pairing through sequence number comparison.
Solution Approach 2:
The patent implements a feedback mechanism where sequence numbers provide information about the current state of route bindings. Routers use these sequence numbers to determine whether they have the most recent reachability information. This feedback loop ensures accuracy during migration by allowing routers to discard stale bindings and adopt updated ones based on sequence number comparisons.
Data Source
AI summary
Presented herein are techniques that enable Ethernet Virtual Private Networks (EVPNs) to support use cases where either the Layer 2 or Layer 3 route associated with a virtual endpoint is different after the virtual endpoint migrates/moves to a different location. In particular, a networking device running an overlay network detects that a virtual endpoint has migrated on the overlay network from a first computing device to a second computing device. The networking device determines a modified Layer 2/Layer 3 route for the virtual endpoint at the second computing device, as well as a sequence number for association with the modified Layer 2/Layer 3 route. The sequence number is determined based on a sequence number associated with a parent Layer 2 route for the modified Layer 2/Layer 3 route.