Dynamic vNIC Trunk Switching for NFV Network Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing NFV specifications do not address how to dynamically manage network connections for virtual machines in a trunk mode, leading to inefficient use of virtual network interface cards (vNICs) and service interruptions due to re-instantiation processes.
Innovation Solution
A network operation method that utilizes dynamic network change flags to manage network connections, allowing for efficient switching between trunk and access ports, and supports dynamic network changes without service interruptions by using management nodes to orchestrate virtualized network function instances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple vNICs are configured for a virtual machine to access multiple networks, then network access capability is improved, but device complexity and service interruption risk increase due to re-instantiation processes
Solution Approach 1:
The patent merges multiple network access functions into a single vNIC by implementing trunk mode support. Instead of requiring separate vNICs for different networks, the virtual switch consolidates multiple network connections through one vNIC interface, allowing the virtual machine to access multiple networks simultaneously without increasing device complexity or triggering re-instantiation processes.
Solution Approach 2:
The vNIC is enhanced with universal functionality to support both access mode and trunk mode operations. In trunk mode, the single vNIC can dynamically handle multiple VLANs and network types, making it a multi-functional interface that replaces the need for multiple dedicated vNICs while maintaining adaptability to various network configurations.
2Adaptability or versatility
If vNIC configuration is changed to add or delete networks, then network adaptability is improved, but service reliability deteriorates due to re-instantiation and restart processes
Solution Approach 1:
The patent implements dynamic network configuration through trunk mode, where the vNIC can dynamically add or remove network connections without requiring re-instantiation. The virtual switch dynamically adjusts VLAN tagging and network path routing in real-time, allowing network configurations to change while the virtual machine remains running and services continue without interruption.
Solution Approach 2:
The system performs preliminary configuration of trunk mode capabilities during virtual machine instantiation, pre-establishing the infrastructure needed for dynamic network changes. By preparing the virtual switch and vNIC with trunk mode support in advance, the system enables future network additions or deletions without requiring service restarts or re-instantiation processes.
3Manufacturing precision
If access ports are used for each VLAN on switches, then network segmentation is improved, but resource utilization deteriorates due to wasted ports
Solution Approach 1:
The virtual switch implements trunk ports that serve multiple VLANs simultaneously, making each physical port universal rather than dedicated to a single VLAN. This allows the same port to handle traffic from multiple VLANs through VLAN tagging, improving port utilization efficiency while maintaining precise network segmentation through software-based VLAN management.
Solution Approach 2:
The virtual switch acts as an intermediary between physical switch ports and virtual machine network interfaces, implementing VLAN routing and trunk mode functionality. This intermediary layer enables efficient port utilization by managing VLAN traffic through software, allowing single ports to serve multiple VLANs while maintaining the segmentation benefits of access ports.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
Provided are a network operation method and apparatus, a device, and a storage medium. The network operation method includes that a management node receives virtualized network function information carrying at least one dynamic network change flag, where the at least one dynamic network change flag is used for indicating whether a dynamic network change is supported; and that the management node operates on a first-type network according to the virtualized network function information.