Computing Node Firmware Update Recovery via Internal Network Backup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing systems with multiple independent processors often experience corrupt updates and unintended interruptions, leading to processor disablement, which requires technician intervention for recovery.

Innovation Solution

A computing node update system that facilitates automatic recovery of processors without user intervention, utilizing an internal network to retrieve and restore previous firmware versions, thereby avoiding external networking and component replacement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If programmable updates are performed on independent processors, then system functionality is improved, but system reliability deteriorates due to corrupt updates and unintended interruptions

Engineering Contradiction:
Improvesystem functionalityVSAvoidprocessor operational status
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by creating backup images of the original programmable before updating, and by pre-establishing recovery mechanisms. The backup image is stored in a separate storage location, ensuring that if the update fails or corrupts the new programmable, the original functionality can be restored without requiring external intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a recovery mechanism that automatically detects update failures and recovers by restoring the backup programmable image. When an update is interrupted or corrupts the new programmable, the system identifies the failure condition and automatically restores the original programmable from the backup, thereby recovering processor operation without technician intervention.

Inventive Principle:
Principle #34Discarding and recovering

2Reliability

If technician intervention is required for recovery, then update reliability can be ensured, but loss of time increases due to manual recovery procedures

Engineering Contradiction:
Improveupdate integrityVSAvoidprocessor downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs self-diagnosis and self-recovery when update failures occur. The processor automatically detects when a programmable update has failed or been interrupted, retrieves the backup image from internal storage, and restores operation without requiring external technician intervention. This self-service capability eliminates downtime associated with manual recovery procedures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms that monitor the update process and automatically trigger recovery actions when failures are detected. The processor continuously checks the status of the new programmable during and after updates, and upon detecting corruption or interruption, automatically initiates the recovery process by restoring the backup image, thereby minimizing downtime.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If external networking is used for updates, then update capability is enhanced, but system complexity increases due to dependency on external networks

Engineering Contradiction:
Improveupdate capabilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the update functionality into two parts: an initial update capability that may use external networks, and a recovery capability that operates independently using internal storage. The backup image is stored locally in the processor's internal memory or attached storage, allowing the recovery function to operate autonomously without external network dependency, thereby reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary backup storage mechanism that decouples the update process from external network dependency. The backup image serves as an intermediary resource that enables recovery operations to proceed independently of external networks, simplifying the system architecture by removing the mandatory requirement for continuous external network connectivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11582101B2Update of programmable for computing nodes
Publication Date: 2023.02.14 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11582101B2 patent drawing
  • US11582101B2 patent drawing
  • US11582101B2 patent drawing

AI summary

For computing nodes having a first programmable and comprising a first node and a second node, an update of the first node from the first programmable to a second programmable across an external network is initiated. In response to the update being interrupted, the first programmable is automatically reinstated on the first node by retrieving the first programmable from the second node across an internal network. The second node is automatically updated to the second programmable by retrieving the second programmable from the first node across the internal network in response to completion of the update of the first node to the second programmable.