VM Network Profile Redeployment After Switch Restart
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network management systems face inefficiencies in redeploying network profiles for virtual machines (VMs) after a physical switch restarts, leading to prolonged downtime and increased burden on the switch due to the need to redeploy all VM profiles, which is time-consuming and degrades switch performance.
Innovation Solution
A network management system that detects and records relationships between physical switches and VMs with unsaved network profiles, deploying only unsaved profiles after a restart and periodically instructing switches to save these profiles, reducing the number of deployments and saving burden on the switch.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all VM network profiles are redeployed after a physical switch restarts, then complete network profile restoration is achieved, but deployment time and switch burden increase significantly
Solution Approach 1:
The system performs preliminary actions by detecting VM status changes and recording their relationships with physical switches before restarts occur. Network profiles are pre-configured and staged, so when a switch restarts, only the necessary profiles need to be deployed rather than all profiles, significantly reducing deployment time while ensuring completeness.
Solution Approach 2:
The invention extracts and identifies only the specific network profiles that need to be redeployed after a switch restart, rather than deploying all profiles. By determining which VMs were downstream from the restarted switch and extracting only their associated profiles, the system reduces deployment time and switch burden while maintaining complete restoration.
2Reliability
If all VM network profiles are redeployed after a physical switch restarts, then complete network profile restoration is achieved, but switch performance degrades due to increased workload
Solution Approach 1:
The system extracts only the necessary subset of network profiles that need to be deployed after a switch restart, rather than processing all profiles. This selective approach reduces the switch's workload and processing burden, maintaining switch performance while ensuring complete restoration of necessary network profiles.
Solution Approach 2:
The network management system performs preliminary detection and recording of VM-switch relationships before restarts occur. This preparation allows the system to quickly identify which profiles need deployment without requiring the switch to process unnecessary profiles, thereby reducing the switch's workload and maintaining its performance.
3Reliability
If network profiles are saved frequently to prevent loss, then profile retention after restart is improved, but deployment time increases due to more save operations
Solution Approach 1:
Instead of saving network profiles continuously or at every possible moment, the system implements periodic save operations at strategically chosen intervals. This periodic approach ensures profiles are retained reliably while minimizing the total number of save operations, thereby reducing the cumulative deployment time associated with frequent saving.
Solution Approach 2:
The system performs preliminary detection of VM status changes and records relationships before restarts occur. By having this information prepared in advance, the system can efficiently determine which profiles need to be saved and deployed after a restart, reducing the total deployment time while ensuring reliable profile retention through targeted save operations.
Data Source
AI summary
A network management system deploys a network profile for a virtual machine to a physical switch after a restart of the physical switch when the virtual machine is downstream of the physical switch and the network profile for the virtual machine has been cached but not saved at the physical switch.