Server Sparing Policy Management Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current management modules for server blade chassis lack a centralized method to configure and manage individual server blades' BIOS and implement sparing policies, leading to system failures and manual remapping when hardware issues occur.

Innovation Solution

A method and system using an advanced management module to centrally manage and configure server blades, including designating a spare server, selecting BIOS and OS, and implementing sparing policies to ensure continuous operation by maintaining the spare server in a powered-off state and automatically remapping resources upon failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized management module is implemented to configure and manage server blades, then ease of operation and management control are improved, but device complexity increases

Engineering Contradiction:
Improvecentralized management capabilityVSAvoidmanagement module complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The management module serves as an intermediary between administrators and server blades, providing centralized configuration and management capabilities. It mediates between the need for simplified administration and the underlying complexity of managing multiple server blades, BIOS settings, and sparing policies across the infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If sparing policies are implemented with automated remapping, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesystem continuityVSAvoidsparing policy management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-configuring spare server blades and establishing sparing policies before failures occur. The management module proactively sets up the spare capacity and remapping rules, so that when a failure occurs, the automated remapping can immediately activate without requiring complex real-time decision-making.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If manual remapping is required upon hardware failure, then device complexity is reduced, but loss of time increases

Engineering Contradiction:
Improvemanagement system simplicityVSAvoidrecovery time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The sparing policy system enables self-service by automatically detecting hardware failures and remapping affected resources to spare server blades without human intervention. The management module autonomously executes the remapping process based on pre-configured policies, eliminating the need for manual administrative actions while maintaining system simplicity.

Inventive Principle:
Principle #25Self-service

4Use of energy by moving object

If spare servers are maintained in powered-off standby state, then use of energy is reduced, but reliability is improved

Engineering Contradiction:
Improveenergy consumptionVSAvoidsystem availability
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The system prepares spare server blades in advance by configuring them with appropriate BIOS settings and allocating resources, but keeps them powered off to conserve energy. When a failure occurs, the management module quickly powers on the pre-configured spare and activates the remapping, providing rapid recovery without requiring continuous energy consumption for standby operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8161315B2Implementation of sparing policies for servers
Publication Date: 2012.04.17 SERVICENOW INC
  • US8161315B2 patent drawing
  • US8161315B2 patent drawing
  • US8161315B2 patent drawing

AI summary

A method for implementing a sparing policy for a server by a management module in communication with the server and a plurality of additional servers is provided. The server is designated as a spare server. The spare server is maintained in a powered-off, standby state. A need for the spare server is determined. At least one of a basic input output system (BIOS) and an operating system (OS) for the spare server is selected. A volume operational on the spare server is selected for a sparing operation.