Remote Management Controller Bus Recovery via Status Counters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inoperable device management buses in Information Handling Systems (IHSs) lead to compromised monitoring and management functions, and restarting components can result in significant downtime, making it infeasible to resume bus communications without affecting the entire system.
Innovation Solution
A method is provided for detecting and recovering from an inoperable device management bus by offloading bus transactions using a first protocol to a bus controller, updating bus status counters based on monitored transactions, and processing transactions using a second protocol to determine the bus status and reset the remote management controller if necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If bus transactions are monitored using multiple protocols and status counters are updated, then bus inoperability detection accuracy is improved, but device complexity increases
Solution Approach 1:
The monitoring system is segmented into multiple independent protocol handlers (first protocol and second protocol) that each maintain their own status counters. This allows the system to monitor different protocols independently without requiring complex cross-protocol coordination, thereby improving detection accuracy while managing complexity through modular design.
Solution Approach 2:
Shared memory serves as an intermediary between the protocol handlers and the determination logic. Status counters from both protocols are updated in shared memory, which then provides a unified interface for determining bus inoperability. This intermediary approach allows complex multi-protocol monitoring without proportionally increasing overall system complexity.
2Reliability
If the remote management controller is reset to recover from bus inoperability, then bus functionality is restored, but system downtime increases
Solution Approach 1:
Status counters are updated continuously in the background as transactions are processed, so that by the time bus inoperability is determined, all relevant status information is already captured and ready. This preliminary data collection allows for rapid reset decision-making without requiring additional analysis time, thus minimizing downtime while ensuring accurate functionality restoration.
3Measurement precision
If bus status counters are updated based on monitored transactions, then detection precision is improved, but processing time increases
Solution Approach 1:
The bus controller automatically updates status counters in shared memory as transactions are processed, without requiring external intervention or complex coordination. Each protocol handler self-updates its relevant counters based on transaction outcomes, enabling precise status detection to occur as a natural byproduct of normal transaction processing rather than as a separate time-consuming operation.
Data Source
AI summary
Embodiments are described for detecting and recovering from an inoperable device management bus. A remote management controller is configured to offload device management bus transactions that use a messaging protocol. The messing protocol transactions are offloaded to a bus protocol controller that is responsible for managing bus operations using the messaging protocol. The bus protocol controller updates a set of bus status counters stored in a shared memory based on the processing of the offloaded messaging protocol transactions. The remote management controller processes device management bus transactions that use a bus protocol and updates the bus status counters based on the status of the bus protocol transactions. The remote management controller determines the status of the device management bus based on the bus status counters in shared memory, if the device management bus is inoperable, resets the remote management controller.