VXLAN Encapsulation via VLAN-to-VNI Mapping in Campus Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The high deployment costs of implementing a VXLAN 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 VTEP is implemented by network devices not directly connected to terminal 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, thus reducing deployment costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all access devices are required to support VXLAN functionality, then VXLAN can be implemented in the campus network, 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 solution divides the functionality so that access devices only need basic Ethernet frame forwarding, while a smaller number of network devices (VTEPs) perform the VXLAN encapsulation and decapsulation. This segmentation allows widespread use of simple access devices while maintaining VXLAN capability where needed.
Solution Approach 2:
The patent introduces network devices as intermediaries between terminal devices and the VXLAN network. These network devices act as VTEPs that perform the VXLAN encapsulation function, mediating between the simple access devices and the VXLAN tunnel endpoints. This intermediary approach allows access devices to remain simple while still enabling VXLAN functionality through the intermediate network devices.
2Device complexity
If VTEP is implemented by network devices not directly connected to terminal devices, then deployment costs are reduced, but it becomes difficult to directly select the 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 data transmission. The VTEP (network device) maintains a mapping table that associates VLAN IDs from access devices with corresponding VNIs for VXLAN tunnels. This pre-configured mapping eliminates the real-time complexity of VNI selection during packet forwarding, as the network device can directly look up the VNI from the pre-established mapping based on the VLAN ID in received Ethernet frames.
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.