VTEP Local Address Resolution in VXLAN Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-user cloud computing environments, existing address resolution protocols for Virtual Extensible Local Area Networks (VXLAN) face inefficiencies due to the need for broadcasting address resolution requests across entire networks, leading to bandwidth consumption and reduced resolution efficiency.
Innovation Solution
A method and apparatus for a VTEP device to store and synchronize routing information, including IP addresses, MAC addresses, and VXLAN identifiers, allowing local determination and response to address resolution requests without broadcasting, using Type-Length-Value (TLV) units within Link State Protocol Data Units (LSP) messages to efficiently manage and update routing information across interconnected VTEP devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If address resolution requests are broadcast across the entire VXLAN network, then all devices can receive the request and respond, but network bandwidth is consumed and resolution efficiency is reduced
Solution Approach 1:
The patent segments the broadcast domain by introducing VXLAN Virtual Network Identifiers to divide the physical network into multiple isolated virtual networks. Address resolution requests are segmented to be sent only within specific VXLAN segments rather than flooding the entire physical network, reducing unnecessary bandwidth consumption while maintaining complete address resolution within each segment.
Solution Approach 2:
The patent introduces VXLAN Tunnel Endpoints (VTEPs) as intermediary devices that receive, process, and forward address resolution requests. VTEPs act as mediators that can locally resolve addresses within their attached networks and selectively forward requests across VXLAN tunnels only when necessary, reducing overall network bandwidth consumption while ensuring complete address resolution.
2Reliability
If address resolution requests are broadcast across the entire VXLAN network, then all devices can potentially respond, but the time required for resolution increases
Solution Approach 1:
By segmenting the network into VXLAN virtual networks, address resolution requests are confined to smaller broadcast domains. This segmentation reduces the time for requests to propagate and for responses to be received, as fewer devices need to process each request, while still ensuring complete address resolution within each segment.
Solution Approach 2:
The patent implements preliminary action by having VTEPs maintain local address resolution information and routing tables in advance. When an address resolution request arrives, VTEPs can quickly determine whether the target device is locally attached or remote, and immediately forward the request only to the appropriate VXLAN tunnel if needed, eliminating unnecessary propagation delays across the entire network.
3Productivity
If routing information is synchronized across all VTEP devices, then local address resolution is enabled without broadcasting, but device complexity and synchronization overhead increase
Solution Approach 1:
The patent implements copying by having VTEPs maintain local copies of routing information and address resolution tables relevant to their attached networks. Instead of requiring complex real-time synchronization mechanisms, each VTEP stores necessary routing data locally, enabling fast address resolution without broadcasting while keeping device complexity manageable through standardized data structures.
Solution Approach 2:
The patent applies universality by designing VTEPs with multi-functional capabilities to handle both local address resolution and VXLAN tunnel routing using the same routing information structures. This universal approach allows a single routing information synchronization mechanism to serve multiple purposes, reducing overall system complexity despite the distributed nature of the network.
Data Source
AI summary
In an example, a VTEP device may store first routing information acquired by the VTEP device, wherein the first routing information may be routing information of a host device connected with the VTEP device. The VTEP stores second routing information sent from other VTEP devices in a VXLAN, wherein the second routing information may be routing information of a host device connected with the other VTEP devices. The VTEP receives an address resolution request from a source host device, wherein the address resolution request comprises an IP address of a target host device, and a VXLAN identifier of a VXLAN to which the target host device belongs. and in response to a determination that routing information of the target host device may be stored locally, the VTEP sends an address resolution response comprising a MAC address of the target host device to the source host device.