SDN Controller MAC to VTEP Binding Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software-defined networking (SDN) systems face inefficiencies in determining the location of a source host in a service chaining topology, particularly when periodic broadcasts are used, which are bandwidth-demanding and inefficient.
Innovation Solution
A controller-based approach is implemented to dynamically store and provide 'MAC to VTEP' bindings, allowing SDN controllers or hosts to determine the location of the source host by querying and storing 'MAC to VTEP' bindings for virtual network interfaces and service virtual network identifiers, enabling efficient packet forwarding without periodic broadcasts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If periodic broadcasts or RARP messages are used to learn the location of the source host, then the SVMs can determine the source host location, but the bandwidth consumption increases and the system becomes inefficient
Solution Approach 1:
The system pre-establishes MAC-to-VTEP bindings in the SDN controller before packets need to be routed. When a GVM sends a packet, the binding information is already available in the controller, eliminating the need for periodic broadcasts or RARP messages to discover the source host location. This preliminary setup allows immediate packet forwarding without additional bandwidth consumption.
Solution Approach 2:
The SDN controller acts as an intermediary that maintains and provides MAC-to-VTEP binding information to SVMs. Instead of SVMs directly performing bandwidth-intensive discovery operations, they query the controller which already has the binding information, thus reducing bandwidth consumption while maintaining reliable source host location determination.
2Productivity
If MAC to VTEP bindings are dynamically stored and queried, then packet routing efficiency improves, but the device complexity increases
Solution Approach 1:
The SDN controller serves as a centralized intermediary that manages all MAC-to-VTEP bindings. Individual SVMs and hosts do not need to implement complex binding management logic themselves; instead, they query the controller which maintains the bindings centrally. This distributes the complexity burden to a dedicated control plane element, simplifying the data plane devices while maintaining routing efficiency.
Solution Approach 2:
The SDN controller provides multiple functions: it maintains MAC-to-VTEP bindings, responds to queries from SVMs, and enables efficient packet routing. By consolidating these functions in a single universal control element, the system avoids duplicating binding management logic across multiple devices, reducing overall system complexity while maintaining high routing efficiency.
Data Source
AI summary
In an embodiment, a computer-implemented method provides mechanisms for identifying a source location in a service chaining topology. In an embodiment, a method comprises: receiving a query, from a service plane implementation module executing on a host of a service virtual machine (“SVM”), for a location of a source host implementing a guest virtual machine (“source GVM”) that originated a packet in a computer network and that serviced the packet; in response to receiving the query, performing a search of bindings associated with one or more virtual network identifiers (“VNIs”) or service virtual network identifiers (“SVNIs”) to identify a particular binding that includes a MAC address of the host implementing the source GVM; identifying, in the particular binding, the location of the source host; and providing the location of the source host to the host of the SVM to facilitate forwarding of the packet from the SVM to the GVM.