Virtual Switch Configuration Rollback for VM Network Stability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large virtual machine networks, configuration changes to virtual switches often result in disconnections from the management system, leading to labor-intensive and tedious reconnection processes.

Innovation Solution

Implementing a system that saves the active configuration before changes, allowing the network to revert back to a saved configuration if the new configuration causes a disconnection, thereby reestablishing connections efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If configuration changes are made to virtual switches via the management system, then network functionality is improved, but connection stability deteriorates

Engineering Contradiction:
Improvenetwork functionalityVSAvoidconnection stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs a preliminary action by saving the current active configuration before applying any changes. This saved configuration serves as a backup that can be restored if the new configuration causes connection issues, thereby enabling safe configuration changes while maintaining connection stability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by monitoring whether the virtual switch maintains communication with the management system after configuration changes. If communication is lost, the system detects this feedback and automatically reverts to the saved configuration, thus resolving the contradiction between configuration updates and connection stability.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If configuration changes are applied to virtual switches, then system adaptability is improved, but reconnection complexity increases

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidreconnection complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically detecting connection failures after configuration changes and autonomously reverting to the saved configuration without requiring manual intervention. This eliminates the need for complex manual reconnection procedures while maintaining configuration flexibility.

Inventive Principle:
Principle #25Self-service

3Reliability

If manual reconnection procedures are used when configuration changes cause disconnection, then connection stability is restored, but time consumption increases

Engineering Contradiction:
Improveconnection stabilityVSAvoidreconnection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically detects when a virtual switch loses connection to the management system and autonomously reverts to the saved configuration to restore connectivity. This self-service mechanism eliminates manual reconnection tasks, significantly reducing time loss while maintaining connection stability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors communication between the virtual switch and management system. When disconnection is detected through feedback mechanisms, the system automatically triggers configuration rollback, thereby restoring connection stability without time-consuming manual intervention.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11159362B2System and method for managing configuration of virtual switches in a virtual machine network
Publication Date: 2021.10.26 VMWARE INC
  • US11159362B2 patent drawing
  • US11159362B2 patent drawing
  • US11159362B2 patent drawing

AI summary

Techniques for managing configuration of virtual switches in a virtual machine network are disclosed. In an embodiment, a virtual machine network that includes virtual switches is configured to revert back to a saved network configuration if a configuration change causes the connection between the VM management system and a managed node to be lost. For example, before any configuration changes are made, the active configuration is saved. If the new configuration supports a working connection between the managed node and the VM management system, then the saved configuration is no longer needed and can be flushed from memory. If, however, the new configuration causes the managed node to be disconnected from the VM management system, then the system reverts back to the saved configuration that was previously known to work. The saved configuration is used to reestablish the connection so that the network continues to function.