BMC Boot Log Retrieval Across Volatile and Persistent Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for obtaining BIOS boot logs in servers are inefficient and time-consuming, requiring repeated server restarts and firmware updates, and fail to collect valid logs when abnormalities cannot be reproduced.
Innovation Solution
A method and apparatus for obtaining boot logs that determine the operating state of a server as normal or abnormal, allowing boot logs to be collected from transitory or non-transitory memory devices accordingly, without the need for server restarts or firmware updates, by using BMC systems to transfer logs based on the server's state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If boot logs are obtained by updating firmware and reproducing abnormality, then boot logs can be collected, but resources are wasted and time is consumed due to multiple reproduction operations
Solution Approach 1:
The patent applies preliminary action by having the BMC system proactively monitor and collect boot logs during the normal boot process before any abnormality occurs. The system continuously captures boot log information in both transitory and non-transitory memory devices, so when an abnormality is detected, the logs are already available for immediate analysis without requiring reproduction operations.
Solution Approach 2:
The BMC (Baseboard Management Controller) acts as an intermediary between the server system and the log collection process. It independently monitors boot processes, accesses memory devices, and retrieves logs without requiring server restarts or firmware updates, thereby eliminating the time-consuming reproduction operations while ensuring reliable log collection.
2Reliability
If boot logs are obtained by restarting server and updating firmware, then boot logs can be collected, but resource waste occurs due to repeated operations
Solution Approach 1:
The system applies self-service by enabling the BMC to autonomously collect boot logs directly from memory devices without requiring external intervention such as server restarts or firmware updates. The BMC independently monitors boot processes, detects abnormalities, and retrieves logs from appropriate memory devices, eliminating wasteful reproduction operations and conserving system resources.
Solution Approach 2:
The BMC serves as an intermediary that decouples the log collection process from the server operation cycle. It can access and retrieve logs from both transitory and non-transitory memory devices during normal operation, avoiding the need to restart the server or update firmware, thereby preventing resource waste while ensuring reliable log collection.
3Device complexity
If only transitory memory device is used for boot logs, then log collection is simplified, but logs are lost when server restarts or crashes occur
Solution Approach 1:
The patent applies local quality by differentiating the functions of transitory and non-transitory memory devices. The transitory memory device (e.g., RAM) is used for storing boot logs during active boot processes where quick access is needed, while the non-transitory memory device (e.g., EEPROM, flash memory) is used for preserving logs that must survive system restarts or crashes. The BMC intelligently selects which memory device to access based on the specific logging scenario.
Solution Approach 2:
The system segments the log storage function across two types of memory devices with different characteristics. Transitory memory provides fast write access during boot operations, while non-transitory memory provides persistent storage for critical logs. This segmentation allows the system to leverage the strengths of each memory type, simplifying the overall structure while ensuring log availability through the non-transitory component.
4Reliability
If multiple memory devices are used for boot logs, then log availability is improved, but system complexity increases
Solution Approach 1:
The BMC acts as an intermediary that manages the complexity of multiple memory devices. It implements the logic for determining which memory device to access based on the operating state and logging requirements. This centralizes the management complexity in a dedicated controller rather than requiring complex coordination between multiple memory devices, thereby maintaining reliability while keeping the system manageable.
Solution Approach 2:
The BMC implements self-service by autonomously determining the appropriate memory device to access without external intervention. It monitors system state, identifies whether logs should be stored in transitory or non-transitory memory, and retrieves logs from the appropriate device. This self-managing approach handles the complexity internally while presenting a simplified interface to the rest of the system.
Data Source
AI summary
A method for obtaining boot logs is provided. The method includes: determining an operating state of a target device, where the operating state includes: a normal operation state and an abnormal operation state; and in response to the operating state being the normal operation state, obtaining boot logs from a first target memory device in a BMC system of the target device, where the first target memory device is a transitory memory device, and the boot log is all logs of the target device in a boot process; or in response to the operating state being the abnormal operation state, obtaining the boot logs from a second target memory device in the target device, where the second target memory device is a memory device in the target device. An apparatus for obtaining boot logs and a method for transferring boot logs are further provided.