Hierarchical EVPN Route Synchronization for VTEP Workload Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Ethernet Virtual Private Network (EVPN) technologies face challenges in managing and synchronizing routes across multiple levels, leading to inefficiencies in resource utilization and workload distribution within complex network architectures.
Innovation Solution
The implementation of a multi-level EVPN networking architecture, where upper-level and lower-level VTEPs establish EVPN and MP-BGP neighbor relationships to synchronize VM addresses and establish VXLAN tunnels, allowing for hierarchical management and resource optimization by forwarding VM route information between levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a flat EVPN architecture is used where all VTEPs synchronize routes with each other, then route synchronization completeness is improved, but device complexity and workload increase significantly
Solution Approach 1:
The patent segments the EVPN network into hierarchical levels (root level and leaf levels) with different route synchronization responsibilities. Root VTEPs synchronize all EVPN routes with child VTEPs, while leaf VTEPs only synchronize routes relevant to their attached VMs. This segmentation reduces the overall synchronization workload while maintaining complete route distribution across the network.
Solution Approach 2:
The patent introduces root VTEPs as intermediary nodes that act as route synchronization mediators between the core EVPN routing information and leaf VTEPs. The root VTEPs receive and process EVPN routes from any source, then selectively distribute them to appropriate child VTEPs, reducing the need for direct peer-to-peer synchronization between all VTEPs.
2Measurement precision
If all VTEPs maintain full EVPN route tables, then route lookup accuracy is improved, but memory usage and processing overhead increase
Solution Approach 1:
The patent applies local quality by allowing different VTEPs to maintain different types of route information based on their hierarchical position and functional requirements. Leaf VTEPs maintain only the route information necessary for their local VMs, while root VTEPs maintain comprehensive route tables. This ensures accurate route lookup for each VTEP's specific needs without requiring all VTEPs to store complete route tables.
3Adaptability or versatility
If EVPN routes are synchronized across multiple hierarchical levels, then network scalability is improved, but synchronization complexity increases
Solution Approach 1:
The patent implements a nested hierarchical structure where leaf EVPNs are nested within parent EVPNs, and multiple parent EVPNs can be nested within a root EVPN. This nested architecture allows routes to be propagated through hierarchical levels in a structured manner, with each level handling synchronization with its direct children, thereby managing complexity through hierarchical decomposition while enabling large-scale network expansion.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
In an example of a method of synchronizing a route, a first VTEP in a first EVPN learns an address of a first VM connected with the first VTEP; sends the learned address to a second VTEP connected with the first VTEP via a first EVPN route, where the second VTEP belongs to any of the first EVPN and a second EVPN of a different level from the first EVPN; receives a second EVPN route carrying an address of a second VM and a destination IP address for establishing a VXLAN tunnel; creates a route entry containing the address of the second VM, and nexthop information contained in the route entry is the destination IP address carried in the second EVPN route; and establishes a VXLAN tunnel between the first VTEP and a VTEP identified by the destination IP address carried in the second EVPN route.