VXLAN VTEP OpenFlow Entry Differentiation via VNI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a Software Defined Network (SDN) integrated with Virtual eXtensible Local Area Network (VXLAN), the inability to differentiate between Openflow entries with the same destination addresses and priorities leads to incorrect routing forwarding entries being added to the wrong Virtual Network Identifiers (VNIs), causing data flow forwarding issues.
Innovation Solution
Incorporating an OXM_OF_PBB_ISID field in the Match field of Openflow entries to explicitly include the corresponding VNI, allowing the VTEP to correctly identify and route forwarding entries to their respective VNIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If Openflow entries are distributed to VTEP without VNI information in the Match field, then the forwarding plane can be simplified, but the VTEP cannot differentiate between entries with the same destination addresses and priorities, leading to incorrect routing
Solution Approach 1:
The patent adds a new dimension (VNI field) to the Match field of Openflow entries. This allows entries to be differentiated along a new dimension beyond just destination address and priority, enabling the VTEP to correctly identify which VNI each entry corresponds to without increasing the complexity of the forwarding plane architecture.
2Adaptability or versatility
If the Openflow protocol is used without VNI extension, then compatibility with existing SDN systems is maintained, but VXLAN-specific routing requirements cannot be met
Solution Approach 1:
The VNI information is nested within the existing Openflow entry structure by utilizing an unused or optional field in the Match field. This allows VXLAN-specific routing requirements to be met while maintaining the outer structure and compatibility of the Openflow protocol, effectively embedding one protocol's requirements within another.
Data Source
AI summary
A controller generates a Software Defined Network (SDN) entry for a Virtual eXtensible Local Area Network (VXLAN) Tunnel End Point (VTEP). A Match field in the generated SDN entry contains a VXLAN Network Identifier (VNI) corresponding to the SDN entry. The controller sends the generated SDN entry to the VTEP.