Automated Datacenter Network Maintenance via Device Clustering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for automating network device maintenance in datacenters face challenges due to the diversity of devices, hardware models, and the need to minimize disruption to ensure continuous network connectivity, as they require specific knowledge and are prone to human errors.

Innovation Solution

A method and system that identifies and clusters network devices by shared parameters, uses redundancy to limit downtime, and allows for non-simultaneous maintenance, enabling datacenter operators with no specific network knowledge to automate maintenance campaigns through a simple interface, ensuring minimal disruption to network services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automated maintenance is performed on all network devices simultaneously, then productivity is improved, but reliability deteriorates due to increased risk of datacenter unavailability

Engineering Contradiction:
Improvemaintenance execution speedVSAvoiddatacenter availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments network devices into multiple groups based on shared parameters (architecture, role, hardware model, software release, enabled features). Maintenance is executed on one group at a time rather than all devices simultaneously, which maintains productivity through systematic processing while ensuring reliability by keeping other groups operational as backups.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by identifying and clustering devices with redundant functionality before maintenance begins. This allows the system to pre-determine which groups can be maintained without impacting datacenter availability, as redundant groups are already identified and prepared to take over if needed.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If maintenance is performed on diverse network devices with different architectures and hardware models, then adaptability is improved, but device complexity increases making automation difficult

Engineering Contradiction:
Improvesupport for diverse device typesVSAvoidmaintenance system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by creating specific maintenance procedures tailored to each device group's characteristics (architecture, role, hardware model, software release, enabled features). Each cluster receives customized maintenance appropriate to its specific parameters, allowing the system to handle device diversity without requiring a single complex universal procedure.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system achieves universality by establishing a unified automation framework that can handle multiple device types through common parameters and clustering logic. The same automated system manages diverse devices by grouping them according to shared characteristics, making the maintenance process universally applicable across different device architectures while maintaining simplicity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of time

If network devices are maintained without identifying redundancy, then loss of time is reduced, but reliability worsens due to potential service interruption

Engineering Contradiction:
Improvemaintenance durationVSAvoidnetwork connectivity continuity
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system uses feedback by continuously monitoring device parameters and redundancy relationships during the maintenance process. This feedback mechanism allows the system to adjust maintenance execution dynamically, ensuring that devices being maintained have identified redundant counterparts, thus maintaining network connectivity while minimizing total maintenance time through efficient resource allocation.

Inventive Principle:
Principle #23Feedback

4Manufacturing precision

If maintenance requires specific network knowledge and manual procedures, then manufacturing precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvemaintenance accuracyVSAvoidoperator skill requirement
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent implements self-service by creating an automated maintenance system that performs all maintenance operations without requiring operator intervention or specific network knowledge. The system automatically clusters devices, determines maintenance sequences, executes maintenance procedures, and manages redundancy, allowing operators with no specific network knowledge to initiate and monitor maintenance campaigns through a simple interface.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4092963B1Method and system for datacenter network device maintenance
Publication Date: 2024.05.08 OVH
  • EP4092963B1 patent drawingFigure 1
  • EP4092963B1 patent drawingFigure 2
  • EP4092963B1 patent drawingFigure 3a

AI summary

A method and system for maintenance of network devices (109) in a datacenter, involving a Network Upgrade Tool (100) coupled to a CMDB (103), a Rules DB (112), an upgrade Path DB (104) and a Network Configurator (105). The Network Upgrade Tool is configured to collect/fetch information from network devices, remove from automated maintenance those non-conforming network devices, cluster the remaining network devices in groups of redundant network devices, and for all such groups, successively upgrade the network operating system of the network devices present in the group.