Blade Server Management Module Configuration Redundancy

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In data center environments, particularly in space-constrained blade server systems, managing module redundancy for management modules is challenging due to the complexity of configuring and reconfiguring these modules after failure, often requiring tedious manual intervention and additional hardware resources.

Innovation Solution

A peer-to-peer management module configuration redundancy method that fragments configuration data and distributes it across communicatively connected peer management modules, allowing for automatic reassembly and application in case of a reset condition, thereby eliminating the need for multiple redundant modules within a single server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple redundant management modules are provided within a single server, then reliability is improved, but device complexity and space usage increase

Engineering Contradiction:

Improvemanagement module reliabilityVSAvoidhardware redundancy complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a logical copy of configuration data across peer management modules instead of hardware copying. When a management module fails, its configuration data can be retrieved from peer modules that have received fragments of the configuration data, providing redundancy without additional hardware modules.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

Peer management modules serve dual functions: their primary management function and the secondary function of storing configuration data fragments for other modules. This multi-functionality provides redundancy capabilities without requiring dedicated redundant hardware.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If configuration data is manually reconfigured after management module failure, then reliability is restored, but loss of time increases

Engineering Contradiction:

Improvesystem recoveryVSAvoidreconfiguration time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by distributing configuration data fragments to peer management modules before any failure occurs. This pre-positioning of data eliminates the need for time-consuming manual reconfiguration after failure, as the data is already available in the system.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system enables self-service recovery where the failed management module automatically retrieves its configuration data from peer modules without requiring manual intervention. The redundancy logic and automated data retrieval processes allow the system to restore itself independently.

Inventive Principle:

Principle #25Self-service

3Device complexity

If hardware space is reduced in blade server environment, then device complexity is reduced, but reliability deteriorates

Engineering Contradiction:

Improvehardware footprintVSAvoidmanagement module redundancy

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent transitions from spatial redundancy (multiple physical modules in hardware space) to logical redundancy (configuration data distributed across existing modules). This dimensional shift allows redundancy to be achieved in the data/domain dimension rather than the physical hardware dimension, optimizing space usage while maintaining reliability.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

4Device complexity

If manual reconfiguration is required after management module failure, then ease of operation deteriorates, but device complexity is reduced

Engineering Contradiction:

Improveredundancy architectureVSAvoidreconfiguration process

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The system implements self-service through automated configuration recovery. When a management module fails, the redundancy logic automatically detects the failure, retrieves configuration fragments from peer modules, reassembles the configuration data, and restores the module without requiring manual operator intervention.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS8086705B2Peer-to-peer module configuration redundancy and recovery management

Publication Date: 2011.12.27 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH

AI summary

A method for peer-to-peer management module configuration redundancy and recovery can be provided. The method can include fragmenting configuration data for a specified management module configured to manage systems components in a blade environment. The method also can include identifying peer management modules communicatively connected to the specified management module. The method yet further can include transmitting different ones of the fragmented configuration data to different ones of the peer management modules. In response to a reset condition in the specified management module, the method can provide for the retrieval of the fragmented configuration data from the peer management modules. Thereafter, the method can provide for the re-assembly of the retrieved fragmented configuration data and the application of the re-assembled fragmented configuration data to the specified management module.