Hyper-Converged Switch Replacement via Configuration Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In hyper-converged infrastructure computing environments, replacing a faulty switch is challenging due to the difficulty in swapping out a configured switch, especially when switches from different manufacturers are involved, and it affects active workloads, making it hard to maintain performance thresholds.

Innovation Solution

A hyper-converged management service dynamically configures a new switch by applying network configurations from a failing switch, allowing for quick and programmatic replacement regardless of the manufacturer, ensuring minimal disruption to workloads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a switch is replaced in a hyper-converged infrastructure, then the faulty switch can be swapped out, but the replacement affects active workloads and requires complex reconfiguration

Engineering Contradiction:
Improveswitch functionalityVSAvoidswitch replacement process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by maintaining a configuration database that stores network configurations before switch failure. When a switch needs replacement, the configuration is retrieved and applied to the new switch beforehand, eliminating manual reconfiguration work and reducing disruption to active workloads.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements copying by creating a digital copy of the failed switch's network configuration from the configuration database and applying it to the replacement switch. This allows the new switch to inherit all necessary settings, VLANs, and network parameters automatically, making the replacement process as simple as swapping hardware without complex reconfiguration.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If a switch from one manufacturer is replaced with a switch from a different manufacturer, then hardware flexibility is improved, but configuration compatibility becomes problematic

Engineering Contradiction:
Improvemanufacturer independenceVSAvoidconfiguration translation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary configuration database that acts as a manufacturer-neutral storage layer. The database stores configurations in a standardized format that can be translated to different vendor-specific formats. This intermediary layer decouples the hardware manufacturer from the configuration management, allowing seamless replacement between different vendors without configuration compatibility issues.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies parameter changes by dynamically translating configuration parameters from the failed switch's vendor format to the replacement switch's vendor format. The system modifies configuration parameters such as command syntax, protocol formats, and device-specific settings to ensure compatibility with the new manufacturer's switch while maintaining the same network functionality.

Inventive Principle:
Principle #35Parameter changes

3Manufacturing precision

If manual reconfiguration is performed on a replacement switch, then configuration accuracy can be ensured, but time consumption and productivity are reduced

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidswitch replacement speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system implements self-service by enabling the replacement switch to automatically obtain its configuration from the configuration database without requiring manual intervention. The switch autonomously receives and applies the configured parameters, VLANs, and network settings, eliminating the need for technicians to manually reconfigure each parameter while ensuring configuration accuracy through automated validation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The configuration is prepared in advance and stored in the configuration database before the switch replacement occurs. This preliminary preparation ensures that when the replacement switch is deployed, the configuration is already validated and ready for automatic application, maintaining both accuracy and speed without requiring post-installation manual configuration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11184434B2Top-of-rack switch replacement for hyper-converged infrastructure computing environments
Publication Date: 2021.11.23 VMWARE INC
  • US11184434B2 patent drawing
  • US11184434B2 patent drawing
  • US11184434B2 patent drawing

AI summary

Disclosed are various examples for top-of-rack (TOR) switch replacement in hyper-converged computing environments. A bring-up network configuration is applied to a network switch to install the network switch in a rack. An active workload within the rack is analyzed to identify a workload network configuration for the active workload. The active workload is reassigned to the network switch from a faulty network switch. The network switch is configured based on the workload network configuration for the active workload.