Auto-Partitioning Baseboard Management Controller for Scalable Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional scalable computing systems require manual configuration by trained technicians, leading to complexity, errors, and the need for costly dedicated hardware, as they lack automatic mechanisms to identify and integrate multiple nodes as a single partitioned system.

Innovation Solution

The system employs a baseboard management controller (BMC) to automatically establish connection data, identify a primary node, and transmit partitioning commands to configure other nodes as secondary nodes, using IPMI commands to adjust BIOS settings and power up sequences, enabling auto-partitioning without user intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration by trained technicians is used to integrate and configure each node, then the system can be properly configured as a single partitioned system, but the process becomes complex, error-prone, and requires costly dedicated hardware

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-configuration through automatic node identification and partitioning. When nodes are connected, they automatically exchange identification information and configure themselves as a single partitioned system without requiring manual technician intervention, thereby eliminating configuration errors while reducing complexity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A management interface is introduced as an intermediary that automates the configuration process. This interface receives connection data from connected nodes, determines partitioning information automatically, and configures the nodes as a single partitioned system, eliminating the need for technicians to manually enter configuration data

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual configuration is used to designate primary and secondary nodes, then the system can boot properly as a single entity, but the process requires trained technicians and is prone to errors

Engineering Contradiction:
Improveboot reliabilityVSAvoidconfiguration ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Nodes automatically determine their own roles (primary or secondary) through self-identification when connected. The system autonomously assigns boot responsibilities and partitioning information based on automatic node identification, eliminating the need for technicians to manually designate roles while ensuring reliable boot operation

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary automatic configuration of node roles and partitioning information before the boot process begins. By pre-establishing the primary-secondary relationships and partitioning data during connection establishment, the system ensures reliable booting without requiring manual configuration efforts

Inventive Principle:
Principle #10Preliminary action

3Reliability

If dedicated hardware management interface is used to configure the system, then proper node integration is achieved, but costly hardware is required and preexisting systems must be modified

Engineering Contradiction:
Improvesystem integration reliabilityVSAvoidsystem compatibility
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The management interface is designed to work with existing system hardware and communication protocols without requiring dedicated specialized hardware. The interface can operate with standard network connections and existing node components, making the solution universally applicable to various system configurations without requiring hardware modifications

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

Solution Approach 2:

The system uses software-based management interface that replicates the functionality of dedicated hardware management interfaces. By implementing the configuration capabilities in software rather than requiring specialized hardware, the system achieves proper node integration while maintaining compatibility with preexisting hardware configurations

Inventive Principle:
Principle #26Copying

4Loss of information

If technicians manually enter node data into user interface, then configuration information can be captured, but the process is time-consuming and error-prone

Engineering Contradiction:
Improveconfiguration information accuracyVSAvoidconfiguration time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

Nodes automatically provide their own identification information to the management interface through self-identification protocols. The management interface automatically captures and processes this data without requiring technicians to manually enter node addresses and identifiers, eliminating transcription errors and significantly reducing configuration time

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8023434B2Arrangements for auto-merging and auto-partitioning processing components
Publication Date: 2011.09.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8023434B2 patent drawing
  • US8023434B2 patent drawing
  • US8023434B2 patent drawing

AI summary

In some embodiments, a method for auto-partitioning a scalable processing system is disclosed. The method can include establishing connection data, identifying a primary node and automatically transmitting partitioning commands to other nodes to configure them as secondary nodes. The partitioning commands can adjust the basic input output settings of the secondary nodes such that the system can boot as a single partitioned system. Other embodiments are also disclosed.