Virtual Machine VLAN Switching for Multi-Method Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual machine systems cannot integrate multiple machine systems utilizing different VLAN methods on a single machine system, leading to increased process steps and potential re-constitution of the VLAN construction when integrating systems with non-compatible methods.
Innovation Solution
A virtual machine system that allows switching between VLAN communication methods based on whether a VLAN ID is set to the virtual network interface card, enabling the simultaneous operation of multiple machine systems using different VLAN methods on a single system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single VLAN constitution method is used in the virtual machine system, then the system can operate stably with one VLAN approach, but multiple machine systems with different VLAN methods cannot be integrated without re-constitution
Solution Approach 1:
The virtual network switch dynamically switches between different VLAN constitution methods (tag VLAN and port VLAN) based on the incoming packet type and configuration. The system can adaptively change its operation mode to handle both tag-based VLANs from external networks and port-based VLANs from virtual machines, resolving the contradiction between stability and adaptability
Solution Approach 2:
The virtual network switch is designed to support multiple VLAN constitution methods simultaneously. It can function as both a tag VLAN switch and a port VLAN switch depending on the operational context, enabling integration of machine systems using different VLAN approaches without requiring re-constitution
2Ease of operation
If VLAN is constituted by utilizing VLAN function of guest OS, then the guest OS can control VLAN configuration, but integration with systems using virtual network switch VLAN control becomes complex
Solution Approach 1:
The virtual network switch acts as an intermediary between the guest OS VLAN control and the physical network. It receives VLAN configuration requests from the guest OS, translates them into appropriate tag or port VLAN configurations, and manages the actual VLAN implementation, thereby simplifying integration while maintaining guest OS control capability
3Extent of automation
If VLAN is constituted by virtual network switch without using guest OS VLAN function, then VLAN control is centralized, but guest OS cannot directly control VLAN configuration
Solution Approach 1:
The VLAN control functionality is segmented into two layers: the virtual network switch handles the complex translation and configuration management (centralized control), while the guest OS maintains a simplified control interface for high-level VLAN configuration requests. This segmentation allows both centralized automation and ease of operation
4Productivity
If multiple machine systems with different VLAN methods are integrated on one machine system, then resource utilization improves, but the number of process steps for integration increases
Solution Approach 1:
The system changes the parameter of VLAN constitution method based on the integration requirements. By dynamically adjusting whether to use tag VLAN or port VLAN depending on the source of the packet and the configuration, the system can integrate multiple machine systems with different VLAN methods without requiring manual re-constitution, thereby reducing integration process steps while maintaining resource utilization efficiency
Data Source
AI summary
A plurality of machine systems constituted by different VLAN constitution methods are integrated on one machine system by using virtual machines. An operation can be switched for virtual network interface cards to VLAN communication corresponding to VLAN ID set to a virtual network interface card or to VLAN communication corresponding to VLAN ID set by OS on a virtual machine using the virtual network interface card depending on whether or not VLAN ID is set.