Watchdog Monitoring Custom BMC Firmware Stack

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Custom BMC firmware stacks, developed in uncontrolled environments, can cause IHS malfunctions or damage due to software errors or unmanaged control functions, particularly in systems with limited memory and cooling mechanisms, necessitating a protection mechanism to prevent damage when the BMC becomes unresponsive.

Innovation Solution

A watchdog monitoring system and method that uses a watchdog timer to transmit messages at regular intervals, allowing continued operation if received within a specified time and activating a failsafe mode if not, thereby protecting the IHS from potential damage by restricting write access to memory and controlling fan speeds to prevent overheating.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom BMC firmware stack is executed to provide flexible system management, then adaptability and versatility are improved, but reliability deteriorates due to software errors and uncontrolled development environments

Engineering Contradiction:
Improvecustom firmware flexibilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A watchdog timer is introduced as an intermediary component between the custom BMC firmware and the system it manages. The watchdog timer independently monitors the firmware's operation by receiving periodic heartbeat signals, and can trigger recovery actions if the firmware becomes unresponsive, thus providing reliability without compromising firmware flexibility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system prepares recovery mechanisms in advance by configuring the watchdog timer with predetermined timeout thresholds and recovery actions. If the custom firmware fails, the pre-configured watchdog mechanism automatically triggers recovery procedures, cushioning against potential system damage before it occurs

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Ease of operation

If BMC control functions are expanded to manage more hardware devices, then ease of operation is improved, but object-generated harmful factors worsen due to potential malfunctions and unmanaged control

Engineering Contradiction:
Improvehardware management capabilityVSAvoidsystem damage risk
Core Design Contradiction:
Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The watchdog timer establishes a feedback mechanism where the BMC firmware continuously signals its operational status to the watchdog. This feedback loop allows the system to detect when the firmware has become unresponsive or malicious, triggering automatic recovery actions to prevent harm to the managed hardware devices

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system applies preliminary anti-action by preparing countermeasures in advance through the watchdog timer configuration. When the firmware exhibits harmful behavior or becomes unresponsive, pre-defined recovery actions are automatically executed to neutralize the threat and protect the hardware infrastructure

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS11714696B2Custom baseboard management controller (BMC) firmware stack watchdog system and method
Publication Date: 2023.08.01 DELL PROD LP
  • US11714696B2 patent drawing
  • US11714696B2 patent drawing
  • US11714696B2 patent drawing

AI summary

An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes a first processor for executing a custom BMC firmware stack, and transmitting a watchdog message at an ongoing basis. The BMC also includes a second processor for receiving the watchdog message. When the watchdog message is received within a specified elapsed period of time, allow continued operation of the custom BMC firmware stack, and when not received within the specified elapsed period of time, place the BMC in a failsafe mode of operation.