Switch Controller Using Bridge Domain Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data center virtualization systems face challenges in efficiently managing and isolating traffic between virtual machines (VMs) and external hosts, leading to increased complexity and resource usage, particularly in large-scale data centers.
Innovation Solution
The implementation of a private virtual local area network (PVLAN) using Software-Defined Networking (SDN) protocols like OPENFLOW, which separates the control and data planes, and employs virtual switches that adhere to the VEPA standard to manage traffic between VMs and external hosts, allowing for restricted communication based on VLAN rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If traditional virtual switching is used to manage traffic between VMs and external hosts, then traffic management capability is provided, but system complexity and resource usage increase in large-scale data centers
Solution Approach 1:
The patent segments the virtual switching function by introducing a bridge domain concept that divides the network into isolated segments. Each bridge domain acts as an independent virtual switching instance with its own forwarding table, separating traffic management into manageable units rather than a monolithic system. This reduces overall system complexity while maintaining resource efficiency.
Solution Approach 2:
The patent adds a new dimension to virtual switching by implementing isolation levels (isolated, community, hybrid) that create hierarchical layers of traffic management. This multi-dimensional approach allows simultaneous optimization of different traffic patterns without increasing linear complexity, enabling efficient resource usage through layered abstraction.
2Quantity of substance
If VLAN tables are maintained for all VMs in a data center, then traffic forwarding is enabled, but memory usage increases with the number of VMs
Solution Approach 1:
The patent segments the VLAN table into bridge domain-specific forwarding tables. Instead of maintaining a single large VLAN table for all VMs, each bridge domain maintains its own compact forwarding table containing only relevant VMs and VLANs. This segmentation dramatically reduces memory usage while maintaining forwarding speed through localized table lookups.
Solution Approach 2:
The patent applies local quality by making each bridge domain's forwarding table contain only the specific VLAN and VM information relevant to that domain, rather than global VLAN table data. This localized approach minimizes memory consumption per domain while enabling fast forwarding decisions through reduced table sizes.
3Reliability
If all VM traffic is processed through the physical switch (VEPA standard), then traffic supervision is achieved, but forwarding speed decreases due to additional processing hops
Solution Approach 1:
The patent introduces dynamic traffic handling by allowing the virtual switch to operate in hybrid mode, dynamically selecting between local forwarding and physical switch processing based on traffic type and isolation requirements. This dynamic approach maintains supervision for critical traffic while enabling fast local forwarding for routine traffic, optimizing both reliability and speed.
Solution Approach 2:
The patent introduces the bridge domain as an intermediary layer between the virtual switch and physical switch. This intermediary enables intelligent traffic routing where only necessary traffic is sent to the physical switch for supervision, while other traffic is handled locally. This mediator role maintains traffic supervision capabilities while reducing processing hops and improving forwarding speed.
Data Source
AI summary
According to an example, a switch controller is connected to a computer hosting a virtual machine (VM) and a virtual switch to provide packet forwarding for the VM. The switch controller restricts packet forwarding actions on the ports according to the assigned primary VLAN, the assigned secondary VLAN, and the assigned VDS to the ports and the stored rules.