BMC Server Management via IPMI FRU ID Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current server management technologies, relying on Intelligent Platform Management Interface (IPMI), face incompatibility issues between OEM tools from different manufacturers, making it difficult for users to manage servers from various manufacturers using a single remote management computer, as there are no standard specifications for transmitting custom files.
Innovation Solution
A server management method and system that utilizes a Baseboard Management Controller (BMC) to differentiate between Field Replaceable Unit (FRU) memory and custom files by using FRU identification, allowing the BMC to access and transmit custom files even if the FRU ID does not belong to the FRU memory, thereby enabling compatibility across different manufacturers' servers without the need for additional OEM tools.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If OEM tools from different manufacturers are used to manage servers, then file transmission between servers can be performed, but compatibility between different manufacturers' tools is poor and multiple tools are required
Solution Approach 1:
The patent creates a universal file transmission mechanism that works across different server manufacturers through IPMI standardization. The BMC server enables file transmission between FRU memory and storage devices using standardized IPMI commands (FRU access commands with FRU IDs), eliminating the need for manufacturer-specific OEM tools. This allows a single remote management computer to manage servers from multiple manufacturers using one unified toolset.
Solution Approach 2:
The BMC server acts as an intermediary between the remote management computer and the target servers' FRU memory. It receives FRU access commands from the remote management computer, translates them into appropriate operations, and facilitates file transmission between the FRU memory of one server and the storage device of another server, enabling cross-manufacturer compatibility without requiring direct integration between different OEM tools.
2Quantity of substance
If FRU memory is used to store custom files, then file transmission can be performed, but the FRU memory capacity may be insufficient for larger custom files
Solution Approach 1:
The patent segments the file storage function into two parts: FRU memory for storing small configuration files and FRU identification data, and storage devices (with sufficient capacity) for storing larger custom files. The BMC server manages this segmentation by directing file transmission operations to the appropriate location based on file size and type, allowing adequate capacity while maintaining operational simplicity through automated routing.
Solution Approach 2:
The BMC server serves as an intermediary that manages the complexity of file transmission between FRU memory and storage devices. It handles the determination of whether to access FRU memory or storage devices based on FRU IDs, automatically routing file operations to the appropriate location. This shields the user from the complexity of managing different storage locations while enabling access to large file capacities through storage devices.
3Adaptability or versatility
If multiple OEM tools are used to manage servers from different manufacturers, then server management can be performed, but the risk of virus infection increases
Solution Approach 1:
The patent establishes a universal server management approach using standardized IPMI protocols that work across all server manufacturers. By using the BMC server with FRU access commands and FRU IDs, administrators can manage servers from different manufacturers through a single standardized interface rather than multiple manufacturer-specific OEM tools, thereby reducing the attack surface and virus infection risk associated with using multiple different software tools.
Data Source
AI summary
A server, a server management system and a server management method are disclosed. The server comprises a field replaceable unit (FRU) memory and a baseboard management controller (BMC). The FRU memory stores an FRU data. The BMC receives an FRU access command from a remote management computer via an intelligent platform management interface (IPMI). The FRU access command comprises an FRU identification (ID). The BMC determines whether the FRU ID belongs to the FRU memory. If the FRU ID does not belong to the FRU memory, the BMC accesses a custom file according to the FRU ID. The custom file is different from the FRU data.


