System and method to detect and recover from inoperable device management bus
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.
1. A method for detecting and recovering from an inoperable device management bus by a remote access controller, the method comprising:
offloading bus transactions using a first protocol to a bus controller managing device management bus operations using the first protocol;
updating, by the bus controller, bus status counters based on a monitored status of the offloaded first protocol bus transactions;
processing device management bus transactions using a second protocol;
updating the bus status counters based on the status of the second protocol bus transactions;
determining the status of the bus based on the bus status counters in shared memory; and if the bus is inoperable, resetting the remote access controller.
2. The method of claim 1 , wherein the device management bus comprises an I2C bus.
3. The method of claim 2 , wherein the bus protocol controller comprises an I2C co-processor of the remote access controller.
4. The method of claim 2 , wherein the first protocol comprises MCTP (Management Component Transport Protocol) messaging.
5. The method of claim 4 , wherein the second protocol comprises IPMB (Intelligent Platform Management Bus) bus transactions.
6. The method of claim 1 , wherein the status of the device management bus is determined based on the bus status counters indicating consecutive errors in the first protocol bus transactions or the second protocol bus transaction.
7. The method of claim 6 , wherein the status of the device management bus is determined based on the bus status counters indicating stalled progress in the first protocol bus transactions or the second protocol bus transaction.
8. A system for managing a device management bus coupled to a plurality of managed devices, the system comprising:
a shared memory storing bus status counters;
a remote access controller coupled to the plurality of managed devices via the device management bus, the remote access controller configured to:
offload bus transactions that utilize a first protocol to a bus protocol controller;
process device management bus transactions that utilize a second protocol;
update the bus status counters based on a monitored status of the second protocol transactions; and
determine the status of the device management bus based on the bus status counters in shared memory; and
the bus protocol controller configured for managing bus operations using the second protocol, wherein the bus protocol controller comprises an I2C co-processor of the remote access controller, the bus protocol controller further configured to:
process the offloaded transactions using the second protocol;
update bus status counters based on the status of the offloaded second protocol transactions.
9. The system of claim 8 , wherein the first protocol comprises MCTP (Management Component Transport Protocol) messaging.
10. The system of claim 8 , wherein the second protocol comprises IPMB (Intelligent Platform Management Bus) bus transactions.
11. The system of claim 10 , wherein the messaging protocol comprises MCTP (Management Component Transport Protocol) messaging.
12. The system of claim 8 , wherein the status of the device management bus is determined based on the bus status counters indicating consecutive errors in the first protocol bus transactions or the second protocol bus transaction.
13. The system of claim 12 , wherein the status of the device management bus is determined based on the bus status counters indicating stalled progress in the first protocol bus transactions or the second protocol bus transaction.
14. A remote access controller for detecting and recovering from an inoperable device management bus, wherein the remote access controller comprises one or more processors that execute instructions for remote management of a plurality of managed devices of an Information Handling System (IHS) via sideband bus connections with the managed devices, the remote access controller configured to:
offload device management bus transactions using a first protocol to a bus protocol controller managing bus operations using the first protocol;
update bus status counters stored in a shared memory based on the status of the offloaded first protocol transactions;
process device management bus transactions using a second protocol;
updating the bus status counters based on the status of the second protocol transactions;
determine the status of the device management bus based on the bus status counters in shared memory; and
if the device management bus is inoperable, reset the remote management access controller.
15. The remote management access controller of claim 14 , wherein the bus protocol controller comprises an I2C co-processor of the remote management access controller.
16. The remote management access controller of claim 15 , wherein the first protocol comprises MCTP (Management Component Transport Protocol) messaging.
17. The remote access controller of claim 16 , wherein the second protocol comprises IPMB (Intelligent Platform Management Bus) bus transactions.
18. The remote access controller of claim 14 , wherein the status of the device management bus is determined based on the bus status counters indicating consecutive errors in the first protocol bus transactions or the second protocol bus transaction.
19. The remote management access controller of claim 18 , wherein the status of the device management bus is determined based on the bus status counters indicating stalled progress in the first protocol bus transactions or the second protocol bus transaction.