Logical Router Configuration on Hardware Switches
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Software-Defined Networking (SDN) technologies face challenges in extending virtual networks to physical networks through hardware switches, particularly in configuring logical routers on managed hardware forwarding elements (MHFEs) to enable seamless communication between physical workloads and external networks.
Innovation Solution
A method is introduced where a control plane configures and manages logical networks by defining routing components, assigning IP and MAC addresses, and using open source protocols like OVSDB to propagate database tables on MHFEs, enabling logical routing functionalities and tunnel endpoint locator tables to establish VXLAN tunnels between MHFEs and MFEs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If logical routers are configured on managed hardware forwarding elements (MHFEs) to extend virtual networks to physical networks, then network connectivity and flexibility are enhanced, but device complexity and configuration difficulty increase
Solution Approach 1:
The patent introduces a control plane as an intermediary that manages and configures logical routers on MHFEs. The control plane receives logical router definitions, defines routing components (distributed router and service routers), assigns IP and MAC addresses, and propagates configuration data to MHFEs using protocols like OVSDB. This intermediary approach allows complex routing functionality to be added to hardware switches without requiring direct complex configuration by operators.
Solution Approach 2:
The logical router is segmented into multiple routing components: a distributed routing component and several service routing components. Each component is separately assigned routes and logical interfaces, allowing independent configuration and management. This segmentation enables the complex routing functionality to be broken down into manageable parts that can be configured and deployed systematically on MHFEs.
2Extent of automation
If multiple routing components are defined for logical routers with separate route and interface assignments, then routing functionality and network management capability are improved, but device complexity and operational complexity increase
Solution Approach 1:
The control plane automatically performs multiple configuration tasks including defining routing components, assigning IP and MAC addresses to logical interfaces, propagating database tables to MHFEs, and establishing VXLAN tunnels. This automated self-service approach manages the complexity of multiple routing components without requiring manual intervention for each configuration detail, maintaining operational simplicity despite enhanced management capability.
Solution Approach 2:
The control plane serves multiple functions: it acts as a configuration manager for logical routers, a protocol handler for OVSDB communication, a tunnel establishment controller, and a database propagation mechanism. This multi-functional approach consolidates various network management tasks into a single system, reducing operational complexity despite the sophisticated routing functionality being provided.
3Reliability
If VXLAN tunnels are established between MHFEs and MFEs using tunnel endpoint locator tables, then network data exchange between physical and virtual workloads is enabled, but protocol complexity and implementation difficulty increase
Solution Approach 1:
The control plane acts as an intermediary that automatically establishes VXLAN tunnels between MHFEs and MFEs. It populates tunnel endpoint locator tables with the necessary routing information and configures the forwarding elements to communicate over VXLAN. This intermediary approach handles the protocol complexity of VXLAN tunnel establishment, making the implementation easier while ensuring reliable network data exchange between physical and virtual workloads.
Solution Approach 2:
The control plane performs preliminary configuration actions by pre-populating tunnel endpoint locator tables with routing information before actual data exchange occurs. This preliminary setup includes defining tunnel endpoints, assigning IP addresses, and configuring forwarding rules, which simplifies the subsequent implementation and ensures reliable data exchange from the outset.
Data Source
AI summary
A method for configuring a managed hardware forwarding element (MHFE) to perform packet forwarding operations for a logical network is described. The method receives data for the logical network that defines a logical router and a set of logical switches for logically connecting several end machines that operate on different host machines to several physical machines that are connected to the MHFE. The method defines multiple routing components for the logical router, where each routing component includes a separate set of logical ports. The method then configures a forwarding table on the MHFE by populating the forwarding table with tunnel endpoint data for each logical port of each routing component of the logical router that is associated with a logical port of a logical switch. The tunnel endpoint data populated for logical ports of one routing component indicate that no tunnel should be established for any of the logical ports.