VXLAN Encapsulation at Network Devices Using VLAN-to-VNI Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The high deployment costs in campus networks due to the need for all access devices to support VXLAN functionality, and the difficulty in selecting a proper VNI for Ethernet frames when implementing VTEP on network devices other than access devices.
Innovation Solution
A network device supporting VXLAN protocol implements VTEP by obtaining a mapping between VLAN IDs and VNIs, adding a VXLAN header to Ethernet frames based on this mapping, and sending VXLAN packets, while access devices do not need to support VXLAN, allowing existing layer 2 switches to be used, thereby reducing costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all access devices are required to support VXLAN functionality, then VXLAN implementation is achieved, but deployment costs become excessively high
Solution Approach 1:
The patent segments the VXLAN implementation requirement from access devices to network devices. Instead of requiring all access devices to support VXLAN, the system divides the functionality so that access devices only need basic Ethernet frame forwarding, while a smaller number of network devices (VTEPs) perform the complex VXLAN encapsulation and decapsulation operations. This segmentation allows widespread use of inexpensive access devices while maintaining VXLAN capabilities through centralized network devices.
Solution Approach 2:
The patent introduces network devices as intermediaries between access devices and the VXLAN network. These intermediary VTEP devices perform the VXLAN encapsulation of Ethernet frames received from access devices, and decapsulation of VXLAN packets before forwarding to terminal devices. This intermediary layer allows access devices to remain simple and inexpensive while still enabling VXLAN functionality in the network.
2Ease of manufacture
If VTEP function is implemented on network devices instead of access devices, then deployment costs are reduced, but it becomes difficult to directly select VNI for Ethernet frames
Solution Approach 1:
The patent applies preliminary action by pre-establishing a mapping relationship between VLAN IDs and VNIs in the network device before actual VXLAN operations. The VTEP device stores this mapping table that automatically translates VLAN IDs from Ethernet frames into corresponding VNIs for VXLAN encapsulation. This preliminary setup eliminates the need for complex real-time VNI selection logic during packet processing, simplifying the device complexity while maintaining cost benefits.
Solution Approach 2:
The patent replaces the mechanical complexity of real-time VNI selection logic with a pre-computed mapping table stored in the network device. Instead of implementing complex algorithms to determine appropriate VNIs during packet processing, the system substitutes this with a simple lookup operation in the pre-established VLAN-to-VNI mapping table, reducing device complexity while maintaining functionality.
3Ease of manufacture
If access devices do not support VXLAN, then deployment costs are reduced, but authentication control becomes more difficult
Solution Approach 1:
The patent uses the network device (VTEP) as an intermediary that performs authentication control functions. Since access devices do not support VXLAN and cannot perform authentication, the network device acts as the intermediary that receives authentication requests from terminal devices, performs authentication verification, and controls access based on authentication results. This maintains authentication control capability while allowing access devices to remain simple and inexpensive.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Disclosed are a VXLAN implementation method, a network device, and a communications system, to reduce overall deployment costs of a VXLAN in a campus network. The method includes: obtaining, by a network device, a mapping from a virtual local area network identifier VLAN ID to a VXLAN network identifier VNI; receiving, by the network device through a port, an Ethernet frame forwarded by an access device, where a VLAN tag field in the Ethernet frame includes the VLAN ID; adding, by the network device, a VXLAN header to the Ethernet frame based on the VLAN ID and the mapping to obtain a VXLAN packet, where a VNI field in the VXLAN header includes the VNI; and sending, by the network device, the VXLAN packet.