I2C Proxy Translating IPMI to PLDM for Unified Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Information Handling Systems (IHSs) face inefficiencies in managing device communications due to the coexistence of IPMI and PLDM messaging protocols, leading to fragmented management tools and potential bus contention, which hinders cohesive management of devices and increases the risk of inoperable bus states.
Innovation Solution
The method involves generating a map of I2C bus endpoints, identifying and configuring virtual PLDM endpoints for IPMI endpoints, and translating messages between PLDM and IPMI protocols to enable unified management by a remote access controller, thereby eliminating the need for the service processor to operate the I2C bus for IPMI endpoints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If both IPMI and PLDM messaging protocols are supported concurrently, then device management versatility is improved, but system complexity and bus contention risk increase
Solution Approach 1:
The service processor acts as an intermediary between the remote access controller and IPMI endpoints. It receives PLDM messages from the remote access controller, translates them to IPMI messages, and forwards them to the appropriate IPMI endpoints. This mediation allows the system to support both PLDM and IPMI protocols without requiring the remote access controller to directly manage IPMI devices, thereby reducing complexity and bus contention risk.
2Reliability
If the service processor operates the I2C bus for IPMI endpoints, then protocol functionality is maintained, but bus contention and inoperable states increase
Solution Approach 1:
The service processor extracts the IPMI message translation and forwarding function from the I2C bus operation. Instead of the service processor directly operating the I2C bus for IPMI communications, it translates PLDM messages to IPMI messages and forwards them through the I2C controller. This separation reduces bus contention and the risk of inoperable bus states while maintaining IPMI protocol functionality.
3Ease of operation
If separate management tools are used for IPMI and PLDM devices, then protocol-specific functionality is preserved, but management efficiency decreases
Solution Approach 1:
The service processor provides universal management capabilities by translating PLDM messages to IPMI messages and managing both PLDM and IPMI endpoints through a single interface. The remote access controller can use unified PLDM-based management tools to manage both PLDM-native devices and IPMI devices, eliminating the need for separate management tools and improving operational efficiency.
Data Source
AI summary
Embodiments provide a proxy between device management messaging protocols that are used to manage devices that are I2C bus endpoints coupled to a remote access controller. A map is generated of the detected I2C bus endpoints. Mapped I2C bus endpoints that support PLDM (Platform Level Data Model) messaging are identified. Next, the mapped I2C bus endpoints that do not correspond to an identified PLDM endpoint are presumed to be IPMI (Intelligent Platform Management Interface) endpoints and are mapped accordingly. A virtual PLDM endpoint for each of the presumed IPMI I2C bus endpoints. A remote access controller is configured for use of PLDM messaging with the virtual PLDM endpoints such that these PLDM messages are translated by the proxy to equivalent IPMI commands and transmitted to the IPMI endpoints. The proxy similarly converts IPMI messages from the IPMI endpoints to equivalent PLDM messages and provided to the remote access controller via the virtual PLDM endpoint.