Network Forwarding Element Controller Redirection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional OpenFlow network configurations face challenges in efficiently connecting forwarding elements to appropriate controllers, especially when the desired controller is unknown or when load distribution across multiple controllers is needed, leading to delayed connections and inefficient resource utilization.
Innovation Solution
The method involves transmitting a connection request from a forwarding element to a first network controller, receiving a rejection message with an alternative controller's address, and subsequently connecting to that alternative controller, allowing for redirection and efficient load distribution across multiple controllers in the control plane.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a forwarding element connects to a first network controller that rejects the connection, then the connection process is delayed, but the forwarding element eventually connects to an alternative controller
Solution Approach 1:
The system performs preliminary actions by having the forwarding element attempt connection to multiple controllers in a predetermined sequence. The configuration includes a list of alternative controllers that the forwarding element will try in order, eliminating the need to wait for rejection messages and reducing connection time while ensuring reliable connection establishment.
2Productivity
If multiple controllers are used for load distribution, then resource utilization improves, but the complexity of controller management increases
Solution Approach 1:
The forwarding element performs self-service by autonomously attempting connections to multiple controllers in sequence without requiring complex centralized coordination. The element uses its configured list of alternative controllers to independently establish connections, reducing the management complexity while enabling effective load distribution across multiple controllers.
3Adaptability or versatility
If a forwarding element is programmed with multiple controller addresses, then connection flexibility improves, but the configuration complexity increases
Solution Approach 1:
The configuration structure uses a universal multi-functional approach where a single configuration object contains both the primary controller address and an ordered list of alternative controller addresses. This unified configuration provides connection flexibility across multiple controllers while maintaining simple, standardized configuration syntax that reduces complexity.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A method of connecting a network forwarding element may include transmitting a first connection request from the forwarding element to a first network controller. After transmitting the first connection request, a rejection message may be received from the first network controller at the network forwarding element, with the rejection message being responsive to the first connection request and with the rejection message including an address of a second network controller. Responsive to receiving the rejection message, a second connection request may be transmitted from the network forwarding element to the second network controller. Related forwarding elements and controllers are also discussed.