SDN Controller Protocol Translation for Network Coexistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud data centers, managing network devices that implement different protocols, such as Open vSwitch Database (OVSDB) and Ethernet Virtual Private Network (EVPN), is challenging due to the need for administrators to consider multiple factors related to network infrastructure and vendor-specific technologies, making it difficult for devices with different protocols to coexist or evolve seamlessly.
Innovation Solution
A Software Defined Networking (SDN) controller translates high-level, protocol-agnostic configuration data into low-level, protocol-specific data, allowing network devices to coexist and evolve by using service provisioning modules that translate configuration data for OVSDB and EVPN protocols, enabling automated management and control of virtualized networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple network devices with different protocols (OVSDB and EVPN) are deployed in the network fabric, then protocol versatility and vendor choice are improved, but device complexity and management difficulty increase
Solution Approach 1:
An SDN controller is introduced as an intermediary between the management plane and diverse network devices. The controller translates high-level, protocol-agnostic configuration data into protocol-specific instructions for OVSDB and EVPN devices, eliminating the need for administrators to manually manage multiple protocols and reducing management complexity while maintaining protocol versatility
Solution Approach 2:
The SDN controller implements a universal configuration interface that works with multiple protocol types (OVSDB, EVPN, and future protocols). This single management point handles diverse network devices through automated translation, providing multi-functional capability that simplifies administration across heterogeneous protocol environments
2Ease of operation
If manual configuration of network devices is performed, then precise control over device settings is achieved, but time consumption and operational efficiency deteriorate
Solution Approach 1:
Configuration templates and high-level policies are prepared in advance at the SDN controller. When network changes are needed, the controller automatically translates these pre-defined configurations into protocol-specific instructions and pushes them to the appropriate devices, eliminating manual configuration steps and significantly reducing configuration time while maintaining precise control
Solution Approach 2:
The SDN controller performs self-service by automatically translating high-level configuration data into protocol-specific instructions without requiring administrator intervention for each device. The system autonomously handles the translation and deployment process, reducing both time consumption and operational complexity
3Manufacturing precision
If protocol-specific configuration data is used for each network device, then precise device control is improved, but system complexity and translation overhead increase
Solution Approach 1:
The configuration system is segmented into two distinct layers: a high-level protocol-agnostic configuration layer for administrators and a low-level protocol-specific implementation layer for devices. The SDN controller handles the translation between these layers, maintaining configuration precision for each device while shielding administrators from protocol complexity through automated segmentation
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques are disclosed for configuring multiple network devices implementing different protocols or techniques. For example, these techniques allow network devices configured with different protocols to co-exist within the same network, or for the network to seamlessly evolve from one protocol to the other. Techniques described herein provide for an SDN controller that may bridge a network system implementing different protocols, e.g., Open vSwitch Database (OVSDB) and Ethernet Virtual Private Network (EVPN), by translating high-level configuration data (e.g., desired state of the network at a high level of abstraction) that are protocol agnostic to low-level configuration data (e.g., desired state of the network at a low level of abstraction) that are protocol specific. That is, SDN controller may provide management, control, and analytics functions of a virtualized network configured to operate specifically within an OVSDB environment and/or an EVPN environment.