Hypervisor vNIC Validation Prevents Virtual Network Loops
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Virtual network topologies with virtual switches and virtual machines are prone to loops when virtual machines forward traffic between multiple virtual network interface cards, as existing methods like MAC pinning and distance vector logic are insufficient, and spanning tree protocol is not effective in preventing loops in such scenarios.
Innovation Solution
A method is implemented where the hypervisor manages virtual machines to prevent the creation or addition of virtual network interface cards (vNICs) that would connect to the same VLAN segment, thereby preventing loops by failing requests that would result in multiple connections to the same VLAN segment, and generating an error message to inform users of potential looping frames.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If virtual machines are allowed to forward traffic between multiple vNICs connected to the same VLAN segment, then network versatility and appliance functionality are improved, but network loops are introduced causing instability
Solution Approach 1:
The hypervisor checks the network topology in advance before allowing vNIC creation or configuration changes. It determines whether adding a vNIC would create a loop by analyzing the existing network graph, and prevents the configuration change before it can be applied, thus avoiding loops proactively while allowing versatile network appliance functionality
Solution Approach 2:
The patent introduces an intermediary validation layer between the user/configuration system and the actual network topology. This intermediary checks proposed configurations against the current network state and only allows changes that maintain loop-free topology, enabling both versatility and reliability
2Reliability
If spanning tree protocol is implemented to prevent loops, then network reliability is improved, but device complexity and protocol overhead increase
Solution Approach 1:
The patent extracts the loop prevention function from complex protocols like spanning tree and implements it directly in the hypervisor's configuration validation logic. This removes the need for running spanning tree protocol while maintaining loop prevention, reducing device complexity and protocol overhead
Solution Approach 2:
The patent replaces the dynamic protocol-based loop prevention mechanism (spanning tree) with a static configuration validation approach. Instead of using protocol messages and dynamic state changes, the system uses deterministic graph analysis during configuration to prevent loops, simplifying the mechanism
3Reliability
If MAC pinning and distance vector logic are used in virtual switches, then loop prevention is improved for endpoint VMs, but adaptability is reduced for network appliance VMs
Solution Approach 1:
The patent creates a universal loop prevention mechanism in the hypervisor that works for all VM types regardless of their network role. The configuration validation approach applies the same loop detection logic whether the VM is an endpoint or a network appliance, making the system universally applicable without needing different mechanisms for different VM types
Data Source
AI summary
A method and apparatus is disclosed for preventing loops on a network topology which includes virtual switches and virtual machines. For example, a virtualization management application may prevent loops from being introduced into a network topology where a virtual machine forwards traffic between any two (or more) virtual network interface cards (vNICs). A method to prevent loops may include receiving a request to create a virtual network interface (vNIC) for a virtual machine (VM) instance on a computing system, and in response to determining that the requested vNIC is to be connected to the same network segment as an existing vNIC of the VM instance, failing the request to generate the requested vNIC.