Server monitoring method, substrate controller, medium and system

Abstract

The invention discloses a server monitoring method, a substrate controller, a medium and a system, and relates to the technical field of embedded systems and server management.The method includes the steps that before a server executes service, the substrate controller executes multiple times of maximum scanning, all connected components are comprehensively recognized, and multiple server configuration mapping relations are generated; and the final server configuration mapping relationship is determined based on the plurality of server configuration mapping relationships, so that communication monitoring of the component can be directly performed according to the final server configuration mapping relationship during normal operation without additional scanning, and the monitoring efficiency is improved. Therefore, the problem that the monitoring efficiency of the server is low due to the fact that the monitoring of the substrate controller on the server needs to be executed step by step according to the preset program every time to judge whether components and devices are in place is solved.

Description

Technical Field

[0001] The present application relates to the technical field of embedded systems and server management, and in particular to a server monitoring method, a baseboard controller, a computer-readable storage medium, and a server system. Background Art

[0002] BMC, Baseboard Management Controller, can capture information about various components on the server, monitor the current, voltage and power consumption on the motherboard, provide power on and off services for the server, and manage the entire server. BMC generally monitors the entire server according to a predetermined program. BMC will determine whether certain components and devices are in place based on various conditions. If they are in place, it will perform communication monitoring on the components and devices, and use the returned information for further management processing.

[0003] Currently, BMC monitoring is performed step by step according to a predetermined program to determine whether components and devices are in place. In contrast, it is performed in a loop, and each time a loop test is performed before entering the main monitoring program.

[0004] That is, the existing baseboard controller monitors the server in a manner that requires each execution of a predetermined procedure step by step to determine whether components and devices are in place, resulting in low server monitoring efficiency. Summary of the Invention

[0005] The present application provides a server monitoring method, a baseboard controller, a computer-readable storage medium, and a server system to at least solve the problem that the baseboard controller of the existing solution monitors the server step by step according to a predetermined procedure each time to determine whether the components and devices are in place, thereby resulting in low server monitoring efficiency.

[0006] The present application provides a server monitoring method, which is applied to a baseboard controller in a server system, including: before the server executes a business, multiple identifications are performed on all components connected to the server to generate multiple server configuration mapping relationships, where the server configuration mapping relationships include at least a mapping relationship between a unique identifier of a component and a location and status of the component; based on the multiple server configuration mapping relationships, a final server configuration mapping relationship is determined; and during the process of the server executing the business, the server is monitored based on the final server configuration mapping relationship.

[0007] The present application also provides a baseboard controller, including: a first processing unit, used to identify all components connected to the server multiple times before the server executes the business, and generate multiple server configuration mapping relationships, where the server configuration mapping relationship at least includes a mapping relationship between the unique identifier of the component and the location and status of the component; a second processing unit, used to determine the final server configuration mapping relationship based on the multiple server configuration mapping relationships; and a third processing unit, used to monitor the server based on the final server configuration mapping relationship during the process of the server executing the business.

[0008] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned server monitoring methods are implemented.

[0009] The present application also provides a server system, comprising: a baseboard controller and a server that are communicatively connected, wherein the baseboard controller is used to execute the steps of any of the above-mentioned server monitoring methods.

[0010] Through this application, when a server is first started or when a major hardware change occurs, the baseboard controller (BMC) performs multiple maximum scans to fully identify all connected components, generate multiple server configuration mappings, and then determine the final server configuration mapping based on these multiple server configuration mappings. This step is crucial because it establishes a detailed mapping of the component's unique identifier, location, and status, laying the foundation for subsequent efficient monitoring. During normal server operation, the BMC no longer needs to perform tedious in-place determinations. Instead, it monitors based on the existing final server configuration mapping, quickly identifying any changes without having to recheck all hardware one by one. Because the BMC has "remembered" the system's normal hardware layout, it can identify any deviations from expectations more quickly than existing solutions, which is extremely beneficial for fault detection and alarm response. Therefore, during normal operation, component communication monitoring can be directly performed based on the final server configuration mapping without the need for additional scanning, improving monitoring efficiency. This solves the problem of existing baseboard controller monitoring of servers, which requires each step to determine whether components and devices are in place according to a predetermined procedure, resulting in low server monitoring efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0012] Figure 1 A flow chart of a server monitoring method provided in an embodiment of the present application;

[0013] Figure 2 A schematic diagram of a process for determining a final mapping in another server monitoring method provided in an embodiment of the present application;

[0014] Figure 3 A schematic diagram of a process for generating fault prompt information in another server monitoring method provided in an embodiment of the present application;

[0015] Figure 4 This is a structural block diagram of a substrate controller provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0017] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0018] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0019] The embodiments of the present application provide a server monitoring method. The method is described in detail in conjunction with the execution process of the server monitoring method. (I. Definition of Pre-training: Pre-training is a strategy for training deep learning models. Its core is to use large-scale data sets to perform preliminary training on the model so that the model learns common feature representations. This process is similar to the basic learning stage of humans before learning new knowledge, accumulating experience through extensive reading and observation.

[0020] Patent interpretation recommendation: A pre-trained language model generally refers to a language model training task designed based on a large-scale corpus (including language training materials such as sentences and paragraphs), and training a large-scale neural network algorithm structure to learn and implement it. The final large-scale neural network algorithm structure and parameters are the pre-trained language model. Other tasks can subsequently perform feature extraction or task fine-tuning based on this model to achieve specific task objectives. The idea of pre-training is to first train a task to obtain a set of model parameters, then use this set of model parameters to initialize the network model parameters, and then use the initialized network model to train other tasks to obtain a model adapted for other tasks. By pre-training on a large-scale corpus, the neural language representation model can learn powerful language representation capabilities and can extract rich syntactic and semantic information from the text. The pre-trained language model can provide tokens containing rich semantic information and sentence-level features for use in downstream tasks. It can also be fine-tuned for downstream tasks directly on the pre-trained model to quickly and easily obtain a downstream-specific model.

[0021] The neural network algorithm structure for training the pre-trained language model can be CNN (Convolutional Neural Network, a deep learning model), RNN (Recurrent Neural Network, a neural network model for processing sequence data), LSTM (Long Short-Term Memory, a special recurrent neural network architecture), etc., or it can be a model built on an attention network, such as Transformer (Transformer model, a neural network architecture), BERT (Bidirectional Encoder Representations from Transformers, a pre-training model), GPT (Generative Pre-trained Transformer, a natural language processing model), Clip (Contrastive Language-Image Pretraining, an artificial intelligence model), etc., which is not limited in this application. An attention network refers to a network model that uses an attention mechanism for training. The model extracts more important feature information from the input sequence by assigning different weights to each part of the input sequence, so that the model ultimately obtains a more accurate output.

[0022] 2. Definition of Fine-tuning: Fine-tuning refers to further training a pre-trained model on a task-specific dataset to adjust model parameters and better adapt it to the target task. During fine-tuning, most layers of the pre-trained model are typically frozen, and only newly added layers are trained or a small number of key layers are adjusted. This preserves the useful features learned by the pre-trained model while enabling rapid adaptation to the specific requirements of the new task. Furthermore, choosing an appropriate learning rate and number of training rounds is crucial to successful fine-tuning.

[0023] Patent explanation recommendation: Fine-tuning refers to performing small-scale training on a pre-trained model for specific task objectives (downstream tasks) and task data (downstream data), achieving minor adjustments to the pre-trained model parameters, and ultimately obtaining a model adapted to the specific task and data. (The technical terms involved must be explained.)

[0024] like Figure 1 As shown, a server monitoring method is applied to a baseboard controller in a server system, comprising the following steps:

[0025] Step S101: Before the server executes a service, all components connected to the server are identified multiple times to generate multiple server configuration mapping relationships, where the server configuration mapping relationships include at least mapping relationships between unique identifiers of components and locations and states of the components.

[0026] The BMC begins identifying the location of every possible component in the server, including memory, hard drives, network interface cards, power modules, and so on. It uses a variety of identification protocols and technologies, such as IPMI (Intelligent Platform Management Interface, a standardized hardware monitoring technology), SMBus (System Management Bus, a standard communication protocol), and I2C (Inter-Integrated Circuit, a two-wire serial bus protocol), to discover and read the unique identifier, type, status, and location of each component.

[0027] Step S102: determining a final server configuration mapping relationship based on multiple server configuration mapping relationships;

[0028] The finalized server configuration mapping relationship is solidified, that is, written into the permanent storage area of the BMC as the basis for subsequent monitoring.

[0029] Step S103: During the process of the server executing the service, the server is monitored based on the final server configuration mapping relationship.

[0030] In step S103, when the server starts to execute the business, the BMC starts real-time monitoring based on the final server configuration mapping relationship. According to the location and status of the known components, its health status, such as temperature, voltage, performance indicators, etc., can be quickly located and monitored. During the monitoring process, the current component status is continuously compared with the information in the final server configuration mapping relationship. If it is found that the status of the component does not match the record in the configuration mapping, the alarm mechanism is immediately triggered to prompt a possible fault or configuration change. Different alarm strategies are adopted according to the property of whether the component is hot-swappable. If the insertion or removal of a hot-swappable component is detected during the monitoring period, the server configuration mapping relationship is automatically updated to reflect the latest hardware configuration.

[0031] In the above steps, when a server is first started or a major hardware change occurs, the baseboard controller (BMC) performs multiple, maximal scans to fully identify all connected components, generating multiple server configuration mappings. Based on these mappings, the final server configuration mapping is determined. This step is crucial because it establishes a detailed mapping of component uniqueness, location, and status, laying the foundation for efficient subsequent monitoring. During normal server operation, the BMC no longer needs to perform tedious in-place verification. Instead, it monitors based on the existing final server configuration mapping, quickly identifying any changes without rechecking all hardware. Because the BMC has "remembered" the system's normal hardware layout, it can more quickly identify any deviations from expectations, significantly benefiting fault detection and alarm response. During normal operation, component communication monitoring can be performed directly based on the final server configuration mapping, eliminating the need for additional scanning. This improves monitoring efficiency and addresses the current issue of baseboard controllers monitoring servers, which often requires a pre-defined, step-by-step process to determine component and device presence.

[0032] In one embodiment of the present application, a final server configuration mapping relationship is determined based on multiple server configuration mapping relationships, including: comparing the server configuration mapping relationships obtained for the first time in all the server configuration mapping relationships with the remaining server configuration mapping relationships in all the server configuration mapping relationships; when the status of the components recorded in the remaining server configuration mapping relationships and the server configuration mapping relationships obtained for the first time are the same, determining the final server configuration mapping relationship to be any one of all the server configuration mapping relationships; when there is at least one recorded component in all the remaining server configuration mapping relationships whose status is different from the status of the component recorded in the server configuration mapping relationship obtained for the first time, performing the identification step again until the final server configuration mapping relationship is determined, the identification step including multiple identifications of all components connected to the server, generating multiple server configuration mapping relationships, and comparing the server configuration mapping relationships obtained for the first time in all the server configuration mapping relationships with the remaining server configuration mapping relationships in all the server configuration mapping relationships.

[0033] By generating server configuration mappings multiple times and comparing each result with the initially acquired configuration mapping, multiple rounds of verification can filter out misidentifications caused by transient interference or other uncertainties. This ensures that the final configuration mapping is the closest to the actual state, even in complex server environments. After determining the final server configuration mapping, the BMC can perform targeted monitoring based on this mapping, eliminating the need to repeat the full component identification process during each monitoring cycle. This reduces computational effort, improves monitoring frequency and response speed, and enables faster detection and response to potential hardware failures. In the event of inconsistent component status, an alert is not immediately issued, but re-identification is triggered. Multiple rounds of identification are repeated until all acquired configuration mappings are consistent. This avoids false alarms caused by a single misidentification, reduces the burden on operations and maintenance personnel, and avoids unnecessary inspections and repair costs. The server system can self-repair its configuration mapping when the hardware configuration changes. Even if a component is suddenly offline or newly added, repeated comparisons and identifications automatically update the final server configuration mapping. By establishing the final server configuration mapping relationship, any change in component status will be regarded as an abnormal situation, providing a benchmark for fault diagnosis, accelerating the troubleshooting and repair process, reducing the impact time on business, and further improving server monitoring efficiency.

[0034] In one embodiment of the present application, a server is monitored based on a final server configuration mapping relationship, including: when a preset situation occurs in the server, all components connected to the server are identified again, and the current server configuration mapping relationship is generated and displayed in a visual manner, the preset situation indicating that the server needs to be repaired or reconfigured; when an instruction allowing modification is received, the final server configuration mapping relationship is modified to the current server configuration mapping relationship; and the server is monitored based on the current server configuration mapping relationship.

[0035] In addition to planned repairs and reconfigurations, the default scenarios also include any unplanned hardware changes, such as the insertion or removal of hot-swappable devices, or sudden failure and recovery of hardware devices.

[0036] When a server undergoes repair or reconfiguration, the BMC can sense the occurrence of these preset situations, and proactively re-identify all connected components to generate a new server configuration mapping relationship. Therefore, even if the server hardware structure changes, the monitoring system can quickly adapt and continue to operate normally, maintaining comprehensive monitoring of the server status. The newly generated current server configuration mapping relationship is displayed to users or operation and maintenance personnel in a visual manner, which facilitates intuitive understanding of the server's hardware layout and status, improving user understanding and operational efficiency. In addition, after the identification is completed, it is allowed to directly update the final server configuration mapping relationship to the current server configuration mapping relationship by allowing modification instructions, avoiding monitoring blind spots or false alarms caused by lagging configuration information, effectively reducing the risk of monitoring failure, and ensuring that even in the case of frequent hardware configuration changes, the server's monitoring system can continue to operate accurately, promptly detect and handle hardware problems, and further improve monitoring efficiency.

[0037] In one embodiment of the present application, after determining the final server configuration mapping relationship based on multiple server configuration mapping relationships, the method also includes: when the final server configuration mapping relationship is lost, stopping monitoring the server and controlling the cooling system to cool the server at maximum power.

[0038] When the server configuration mapping is ultimately lost, it becomes impossible to accurately monitor the status of each server component. In this case, monitoring is stopped, avoiding decisions based on incorrect or missing configuration information and preventing failures or data errors that may be caused by improper monitoring. Due to the loss of the configuration mapping, the BMC cannot determine which components require cooling and the degree of cooling. Therefore, maximum power cooling is employed to ensure that all possible heat sources are effectively cooled, preventing hardware damage or system crashes caused by server overheating. The loss of configuration information may cause the server to operate in an unknown configuration, introducing additional system risks. By immediately stopping configuration-based monitoring activities and enabling maximum power cooling, potential overheating risks can be avoided, prioritizing the physical safety of the system and thus improving the stability and reliability of the server system.

[0039] In one embodiment of the present application, controlling the heat dissipation system to cool the server at maximum power includes: executing a first cooling control method or a second cooling control method, wherein the final server configuration mapping relationship is lost, indicating that the final server configuration mapping relationship is incomplete, the first cooling control method indicates directly controlling the heat dissipation system to cool the server at maximum power, and the second cooling control method indicates generating a maximum power cooling instruction and sending the maximum power cooling instruction to a corresponding control device, so that the corresponding control device controls the heat dissipation system to cool the server at maximum power.

[0040] By directly controlling the heat dissipation system to cool the server at maximum power through the first cooling control method or generating a maximum power cooling instruction through the second cooling control method, and sending the maximum power cooling instruction to the corresponding control device, so that the corresponding control device controls the heat dissipation system to cool the server at maximum power, it can ensure that when the final server configuration mapping relationship is lost and the monitoring fails, the maximum power cooling mode is immediately started. This instant response mechanism can quickly reduce the temperature of the server, prevent hardware damage or system failures that may be caused by overheating, and ensure the physical safety of the server. In addition, through the preset cooling control method, the system can automatically perform cooling operations without relying on complex fault analysis or human judgment, which simplifies the fault handling process and speeds up system recovery.

[0041] In one embodiment of the present application, after executing the first cooling control mode or the second cooling control mode, the method also includes: repeatedly performing component identification work on the server multiple times to obtain multiple identification results, and the component identification work represents the identification of all components connected to the server; when there are multiple continuous and data-consistent identification results among all the identification results, the server configuration mapping relationship is modified to a target scanning result, and the target identification result represents multiple continuous and data-consistent identification results among all the scanning results.

[0042] Repeated component identification recollects the server's hardware configuration information and generates new identification results, providing the foundation for resuming monitoring and ensuring continued efficient and accurate operation after the configuration update. By retrying identification multiple times until a stable and consistent set of hardware status data is obtained, accidental identification errors are eliminated, ensuring the final configuration information is highly reliable and accurate. By repeating identification instead of performing extended downtime after configuration information is lost, service interruption can be minimized. Once consistent identification results are obtained and the configuration mapping is updated, the monitoring system can resume normal operations, minimizing the impact on normal service.

[0043] In one embodiment of the present application, the method further includes: in a process of monitoring the server based on the final server configuration mapping relationship, if it is determined that a non-hot-swappable component among the components recorded in the final server configuration mapping relationship cannot operate, generating first fault prompt information to prompt that the non-hot-swappable component is damaged; in a process of monitoring the server based on the final server configuration mapping relationship, if it is determined that a hot-swappable component among the components recorded in the final server configuration mapping relationship cannot operate, or if it is determined that a hot-swappable component among the components recorded in the final server configuration mapping relationship cannot operate, generating second fault prompt information to prompt that the hot-swappable component is damaged or has been normally removed;

[0044] After determining the final server configuration mapping relationship based on multiple server configuration mapping relationships, the method also includes: when it is determined that there is a non-hot-swappable component in the components recorded in the final server configuration mapping relationship that cannot run, generating a third fault prompt information to prompt that the non-hot-swappable component is damaged or abnormally removed.

[0045] In the event that a non-hot-swappable component fails to operate, a first fault prompt message is directly generated, indicating that the component is damaged. For hot-swappable components, a function is designed to distinguish between damage and normal removal. The characteristics of hot-swappable components allow them to be inserted or removed while the system is running. The prompt message can help operation and maintenance personnel quickly determine whether the damaged component needs to be replaced or simply reinserted, saving maintenance time and costs. After the final server configuration mapping relationship is determined, if it is found that the non-hot-swappable component cannot operate, a third fault prompt message is generated, indicating that the component is damaged or abnormally removed. By customizing the fault prompt message according to the component type, false alarms and missed alarms can be significantly reduced, improving the accuracy and stability of the monitoring system. Clear fault prompt messages reduce the pressure of fault diagnosis and improve efficiency.

[0046] like Figure 2 As shown, determining the final mapping in the method of the present application includes:

[0047] The first step is to obtain the first configuration mapping relationship;

[0048] The second step is to traverse the remaining configuration mappings and compare the configuration mapping obtained for the first time with all other configuration mappings;

[0049] The third step is to determine whether the component status recorded in the remaining configuration mapping is the same as the component status recorded in the configuration mapping relationship obtained for the first time. If they are the same, directly select one of them as the final mapping. If they are not the same, all components are identified again, a new configuration mapping is generated, and the third step is executed.

[0050] First, the server hardware configuration is prepared for consistency verification by initiating an automated identification process. An initial scan of the server hardware configuration generates a detailed component list, including the status information of all hardware components. This is known as the first server configuration mapping. The server hardware is then scanned multiple times, each scan generating a new configuration mapping. All configuration mappings except the first are considered the "remaining server configuration mappings." The first configuration mapping is compared with each subsequent mapping to check for component status consistency—that is, whether the component types and status recorded in each mapping are identical. If all remaining mappings match the component status recorded in the first mapping, the server hardware configuration has not changed. If any of the remaining mappings differ from the component status recorded in the first mapping, this indicates a hardware modification or an identification error. If all comparison results are consistent, a single configuration mapping is selected as the final server configuration mapping. In the event of a status inconsistency, a re-identification step is triggered, where all components on the server are identified again, a new configuration mapping list is generated, and the previous comparison process is repeated. In server hardware, hot-swappable components (such as certain types of hard drives and network cards) and non-hot-swappable components (such as CPUs and motherboards) have fundamentally different O&M strategies. This process first distinguishes the hot-swappable characteristics of components, ensuring more targeted fault detection and emergency response strategies and reducing misdiagnosis. For non-hot-swappable components, the system further determines whether they are included in the current "final server configuration mapping." Fault notifications not included in the mapping indicate component damage, while fault notifications included in the mapping may indicate an abnormal removal of the component. For hot-swappable components, fault notifications are directly generated for both damage and normal removal, providing operators with clearer clues to fault location. The BMC can quickly identify hardware anomalies and immediately generate fault notifications without requiring manual intervention, accelerating the O&M team's response time. Whether a hot-swappable component is damaged or a non-hot-swappable component has been abnormally removed, the system immediately notifies the responsible personnel, saving valuable time for repair or replacement. This distinction between hot-swappable and non-hot-swappable components prevents operators from making operational errors due to a lack of understanding of component characteristics. For example, for hot-swappable components that have been properly removed, the system-generated secondary fault alert prevents the operations team from conducting unnecessary on-site inspections, reducing labor costs and operational risks. In the event of a component failure, the process accurately determines the nature of the problem, avoiding overreaction and waste of resources for non-faulty components. For example, for components that are indeed damaged, the system-generated primary or tertiary fault alert prompts the operations team to take swift action rather than blindly inspecting the entire server, conserving operations resources and enhancing the user experience.

[0051] like Figure 3 As shown, the method of the present application for generating fault prompt information includes:

[0052] The first step is to determine whether the component is hot-swappable. If the component is not hot-swappable, the second step is executed. If the component is hot-swappable, the third step is executed.

[0053] The second step is to determine whether the non-hot-swappable component cannot operate. If it operates normally, determine that the non-hot-swappable component operates normally, i.e., there is no fault. If it cannot operate, determine whether it is in the final server configuration mapping relationship. If it is not in the final server configuration mapping relationship, generate a first fault prompt information to prompt that the non-hot-swappable component is damaged. If it is in the final server configuration mapping relationship, generate a third fault prompt information to prompt that the non-hot-swappable component is damaged or abnormally removed;

[0054] The third step is to determine whether the hot-swappable component cannot operate. If it cannot operate, a second fault prompt message is generated to prompt that the hot-swappable component is damaged or has been normally removed.

[0055] First, monitoring is initialized to continuously monitor the server's hardware status. During initial startup, the monitoring system establishes a final server configuration mapping based on multiple identification results. This final server configuration mapping records detailed information about all the server's current hardware components, including their types and operating status. If, during continuous monitoring, a non-hot-swappable component, such as the CPU, recorded in the final server configuration mapping suddenly appears offline or inoperable, the system automatically generates a primary fault message, alerting the administrator that the CPU may be damaged and requiring immediate inspection and repair. The situation is slightly different for hot-swappable components. If the monitoring system detects that a hot-swappable component, such as a hard drive, is in an "inoperable" state, a secondary fault message is generated. While removing a hot-swappable component doesn't immediately cause server operation to malfunction, the monitoring system needs to be notified of this change promptly. Therefore, a secondary fault message is generated to indicate that the component is damaged or that the administrator has safely removed it without interrupting server operations. During the process of determining the final configuration mapping, if the system detects that a non-hot-swappable component, such as a CPU or memory module, suddenly disappears or changes its status to "inoperable," this is often not just a hardware failure; it could also be due to unauthorized or accidental physical intervention, leading to the abnormal removal of hardware. In this case, the monitoring system will generate a third fault message, alerting the administrator that a non-hot-swappable component may have been illegally removed and requiring immediate action to protect server security and data integrity. The first fault message: For non-hot-swappable components, such as the CPU (Graphics Processing Unit) or memory, detecting that these components are inoperable directly indicates a hardware failure, requiring immediate downtime and inspection. The second fault message: For hot-swappable components, such as hard drives or network cards, this indicates both a hardware failure and the possibility of a normal maintenance procedure, such as proactive component removal. The third fault message: Specifically for the abnormal removal of non-hot-swappable components, this indicates not only a hardware failure but also possible sabotage or theft, triggering an immediate security response.

[0056] This application also provides a specific use case for controlling a cooling system to cool a server at maximum power. In cloud computing data centers, the efficient operation of server clusters relies on precise hardware monitoring and management. As a critical component within the server, the BMC is responsible for monitoring the server's health, including key indicators such as temperature, voltage, and fan speed, and making management decisions based on hardware configuration mappings. Stable server operation is essential for ensuring business continuity and data security. When a server experiences a sudden hardware configuration mapping loss or other monitoring system malfunction, it is particularly important to implement a strategy for controlling the cooling system to operate at maximum power. A server in a cloud computing data center experiences a loss of configuration mapping, causing the monitoring system to cease functioning properly. This poses a potential risk of overheating. Without accurate hardware configuration information, the BMC cannot determine which components require cooling and the precise cooling requirements. Upon detecting the configuration loss, the BMC immediately switches to the first cooling control mode, directly controlling the cooling system, such as fans and liquid cooling pumps, to operate at maximum power to ensure that all possible heat sources are covered, preventing hardware damage or system failure due to localized overheating. Alternatively, a maximum power cooling command can be generated and sent to an independent control device, which interprets the command and activates the cooling system at maximum power. This approach is suitable for scenarios where complex communication protocols or physical isolation exist between the BMC and the cooling system, providing a flexible control mechanism. This approach minimizes the risk of data loss and business interruption. Traditional manual emergency response to server configuration loss is time-consuming, especially in large data centers, where manual inspection and adjustment of the cooling system is a massive undertaking. Automated maximum power cooling significantly shortens emergency response times, allowing maintenance teams to focus on the root cause of the problem rather than reactively addressing overheating. Automated maximum power cooling allows maintenance teams to focus on identifying the cause of configuration loss. Furthermore, overheating is a major cause of server hardware failure, especially for critical components without redundant designs. By controlling the cooling system to operate at maximum power, all potential heat sources within the server are effectively cooled immediately, ensuring immediate cooling of the CPU, GPU, hard drives, and power modules. This comprehensive cooling approach significantly reduces the risk of hardware damage caused by localized overheating. It effectively prevents hardware failures caused by overheating, thereby minimizing the possibility of data loss and business interruption. Operations and maintenance personnel no longer need to worry about server overheating, which not only reduces emergency response time but also labor costs. In emergency situations, server stability and data integrity become even more critical. Maximum power cooling ensures that servers can continue to operate in high-temperature environments, buying valuable troubleshooting and repair time for maintenance teams, avoiding sudden business interruptions and maintaining service continuity.

[0057] This application also provides a specific use case for monitoring and updating server hardware after a change. During data center operations and maintenance, servers often need to be repaired or have their hardware upgraded or reconfigured. For example, if a server is repaired after a hardware failure and some memory modules are replaced, the original server configuration mapping no longer accurately reflects the current hardware layout and status. To adapt to the hardware change, the BMC automatically initiates an update process. First, the BMC re-identifies all components on the server, including the CPU, memory, hard drive, network card, and other components, collecting their models, specifications, and status information. This collected hardware information is parsed and compared with a known configuration database to generate a new server configuration mapping. The mapping details the physical location, type, and current status of each piece of hardware, and the newly generated configuration mapping is visually displayed to operations personnel. This step ensures that after a hardware change, the BMC captures the latest component information, including newly added, removed, or replaced hardware components. Next, after receiving the new configuration mapping display, operations personnel need to carefully review the changes and, after confirming that they are correct, issue a command to allow the modification through the BMC management interface. Upon receiving instructions from operations personnel, the BMC updates the current configuration mapping to the final version, ensuring that the data the monitoring system relies on accurately reflects the latest hardware layout and status. This update process is dynamic, allowing the server monitoring system to quickly and accurately adjust its monitoring strategy after any hardware changes. Dynamic updates to the configuration mapping enable the BMC to accurately monitor the true hardware status of each server, avoiding ineffective monitoring of non-existent components, reducing computational overhead, and improving monitoring efficiency. The updated configuration mapping guides the BMC in adjusting its monitoring strategy, eliminating the need to waste resources monitoring removed hardware and focusing on newly added or changed components. For example, after a hardware upgrade, the BMC will strengthen temperature monitoring of the new components to ensure they remain within safe operating ranges. This allows the BMC to more effectively allocate monitoring and management resources based on the actual hardware changes. For example, if hardware is added, the BMC may need to adjust its cooling strategy to ensure the proper operation of the new components. If hardware is removed, unnecessary monitoring frequency can be reduced, reducing the BMC's own load. For example, instead of detecting a removed hard drive or replaced CPU, the BMC focuses on monitoring newly added GPU accelerators or increased RAM (Random Access Memory) capacity. This mechanism quickly adapts to any changes in server hardware, whether during factory settings, routine maintenance, or after emergency troubleshooting. Before an upgrade, the BMC saves the current server configuration mapping as a historical record. After the upgrade is complete, the BMC automatically identifies the newly added GPU accelerator and expanded memory modules and generates a new configuration mapping.It ensures that the monitoring system is always synchronized with the actual hardware, so that it can respond to the monitoring needs brought about by hardware changes in a timely manner. Dynamic updates of configuration mapping relationships enable the BMC to accurately monitor the actual hardware status of each server, avoid invalid monitoring of non-existent components, reduce the computing burden of the BMC, and improve monitoring efficiency. In addition, it can quickly adapt to any changes in server hardware, whether in factory settings, daily operations and maintenance, or after emergency fault repairs, ensuring that the monitoring system is always synchronized with the actual hardware, so that it can respond to the monitoring needs brought about by hardware changes in a timely manner, while also strengthening the security of the system and avoiding potential threats caused by unknown or unverified hardware access. Through BMC's automated component identification and mapping updates, operations and maintenance personnel do not need to manually enter or adjust hardware configuration information, which greatly simplifies the operations and maintenance process and reduces the possibility of human error.

[0058] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0059] The embodiments of the present application further provide a baseboard controller. For descriptions of features in the embodiments corresponding to the baseboard controller, please refer to the relevant descriptions of the embodiments corresponding to the server monitoring method, which will not be repeated here.

[0060] like Figure 4 As shown, the baseboard controller includes:

[0061] The first processing unit 10 is configured to identify all components connected to the server multiple times before the server executes a service, and generate multiple server configuration mapping relationships, wherein the server configuration mapping relationships include at least mapping relationships between unique identifiers of components and locations and states of the components;

[0062] A second processing unit 20 is configured to determine a final server configuration mapping relationship based on the multiple server configuration mapping relationships;

[0063] The third processing unit 30 is configured to monitor the server based on the final server configuration mapping relationship during the process of the server executing the service.

[0064] When a server is first booted or undergoes a major hardware change, the baseboard controller (BMC) performs multiple, maximal scans to fully identify all connected components, generating multiple server configuration mappings. Based on these mappings, the BMC then determines the final server configuration mapping. This step is crucial because it establishes a detailed mapping of component uniqueness, location, and status, laying the foundation for efficient subsequent monitoring. During normal server operation, the BMC no longer requires tedious in-place verification. Instead, it monitors based on the existing final server configuration mapping, quickly identifying any changes without rechecking all hardware. Because the BMC has "remembered" the system's normal hardware layout, it can more quickly identify deviations from expectations, significantly facilitating fault detection and alarm response. During normal operation, component communication monitoring can be performed directly based on the final server configuration mapping, eliminating the need for additional scanning. This improves monitoring efficiency and addresses the current issue of baseboard controllers monitoring servers, which often requires a step-by-step, pre-defined process to determine component and device presence.

[0065] In one embodiment of the present application, the second processing unit includes: a comparison module, which is used to compare the server configuration mapping relationship obtained for the first time among all the server configuration mapping relationships with the remaining server configuration mapping relationships among all the server configuration mapping relationships; a determination module, which is used to determine that the final server configuration mapping relationship is any one of all the server configuration mapping relationships when the states of the components recorded in the remaining server configuration mapping relationships and the server configuration mapping relationships obtained for the first time are the same; a first execution module, which is used to, when the state of at least one recorded component in all the remaining server configuration mapping relationships is different from the state of the component recorded in the server configuration mapping relationship obtained for the first time, perform the identification step again until the final server configuration mapping relationship is determined, the identification step including multiple identifications of all components connected to the server, generating multiple server configuration mapping relationships, and comparing the server configuration mapping relationship obtained for the first time among all the server configuration mapping relationships with the remaining server configuration mapping relationships among all the server configuration mapping relationships.

[0066] In one embodiment of the present application, the third processing unit includes: a first identification module, which is used to identify all components connected to the server again when a preset situation occurs in the server, generate and display the current server configuration mapping relationship in a visual manner, and the preset situation indicates that the server needs to be repaired or reconfigured; a first modification module, which is used to modify the final server configuration mapping relationship to the current server configuration mapping relationship when an instruction to allow modification is received; and a monitoring module, which is used to monitor the server based on the current server configuration mapping relationship.

[0067] In one embodiment of the present application, the baseboard controller further includes: a stopping unit, configured to stop monitoring the server and control the cooling system to cool the server at maximum power when the final server configuration mapping relationship is lost.

[0068] In one embodiment of the present application, the stop unit includes: a second execution module, used to execute the first cooling control mode or the second cooling control mode, wherein the loss of the final server configuration mapping relationship indicates that the final server configuration mapping relationship is incomplete, the first cooling control mode indicates that the heat dissipation system is directly controlled to cool the server at maximum power, and the second cooling control mode indicates that a maximum power cooling instruction is generated and the maximum power cooling instruction is sent to the corresponding control device, so that the corresponding control device controls the heat dissipation system to cool the server at maximum power.

[0069] In one embodiment of the present application, the stopping unit also includes: a second identification module, which repeatedly performs component identification work on the server multiple times to obtain multiple identification results, and the component identification work represents the identification of all components connected to the server; a second modification module, which is used to modify the server configuration mapping relationship to a target scanning result when there are multiple continuous and data-consistent identification results among all the identification results, and the target identification result represents multiple continuous and data-consistent identification results among all the scanning results.

[0070] In one embodiment of the present application, the baseboard controller also includes: a first determination unit, which is used to generate a first fault prompt information to indicate that the non-hot-swappable component is damaged when it is determined that there is a non-hot-swappable component that cannot be operated among the components recorded in the final server configuration mapping relationship during the monitoring of the server based on the final server configuration mapping relationship; a second determination unit, which is used to generate a second fault prompt information to indicate that the hot-swappable component is damaged or has been normally removed when it is determined that there is a hot-swappable component that cannot be operated among the components recorded in the final server configuration mapping relationship during the monitoring of the server based on the final server configuration mapping relationship; a third determination unit, which is used to, after determining the final server configuration mapping relationship based on multiple server configuration mapping relationships, the method also includes: a generation unit, which is used to generate a third fault prompt information to indicate that the non-hot-swappable component is damaged or has been abnormally removed when it is determined that there is a non-hot-swappable component that cannot be operated among the components recorded in the final server configuration mapping relationship.

[0071] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above-mentioned server monitoring method embodiments when running.

[0072] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0073] An embodiment of the present application further provides a server system, which includes a baseboard controller and a server in communication with each other, and the baseboard controller is used to execute the steps in any of the above-mentioned server monitoring method embodiments.

[0074] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0075] The above is a detailed introduction to a server monitoring method, baseboard controller, computer-readable storage medium, and server system provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A server monitoring method, applied to a baseboard controller in a server system, characterized in that: include: Before the server executes a service, all components connected to the server are identified multiple times to generate multiple server configuration mapping relationships, wherein the server configuration mapping relationships at least include mapping relationships between unique identifiers of the components and locations and states of the components; Determining a final server configuration mapping relationship based on the multiple server configuration mapping relationships; During the process of the server executing the service, the server is monitored based on the final server configuration mapping relationship.

2. The server monitoring method according to claim 1, characterized in that: Determining a final server configuration mapping relationship based on the multiple server configuration mapping relationships includes: comparing the server configuration mapping relationships obtained for the first time among all the server configuration mapping relationships with the remaining server configuration mapping relationships among all the server configuration mapping relationships; When the states of the components recorded in the remaining server configuration mapping relationships are the same as those in the first obtained server configuration mapping relationship, determining the final server configuration mapping relationship to be any one of all the server configuration mapping relationships; In the event that the status of at least one component recorded in all the remaining server configuration mapping relationships is different from the status of the component recorded in the server configuration mapping relationship obtained for the first time, the identification step is performed again until the final server configuration mapping relationship is determined. The identification step includes multiple identifications of all the components connected to the server to generate multiple server configuration mapping relationships, and comparing the server configuration mapping relationship obtained for the first time in all the server configuration mapping relationships with the remaining server configuration mapping relationships in all the server configuration mapping relationships.

3. The server monitoring method according to claim 1, wherein: Monitoring the server based on the final server configuration mapping relationship includes: When a preset situation occurs on the server, all the components connected to the server are identified again, and a current server configuration mapping relationship is generated and displayed in a visual manner. The preset situation indicates that the server needs to be repaired or reconfigured. When receiving a modification permission instruction, modifying the final server configuration mapping relationship to the current server configuration mapping relationship; The server is monitored based on the current server configuration mapping relationship.

4. The server monitoring method according to claim 1, wherein: After determining a final server configuration mapping relationship based on the multiple server configuration mapping relationships, the method further includes: In the case that the final server configuration mapping relationship is lost, monitoring of the server is stopped, and the heat dissipation system is controlled to cool the server at maximum power.

5. The server monitoring method according to claim 4, characterized in that: Controlling the heat dissipation system to cool the server at maximum power includes: Execute the first cooling control mode or the second cooling control mode, wherein the loss of the final server configuration mapping relationship indicates that the final server configuration mapping relationship is incomplete, the first cooling control mode indicates directly controlling the heat dissipation system to cool the server at the maximum power, and the second cooling control mode indicates generating a maximum power cooling instruction and sending the maximum power cooling instruction to a corresponding control device, so that the corresponding control device controls the heat dissipation system to cool the server at the maximum power.

6. The server monitoring method according to claim 5, characterized in that: After executing the first temperature reduction control mode or the second temperature reduction control mode, the method further includes: Repeating component identification on the server multiple times to obtain multiple identification results, wherein the component identification represents identification of all components connected to the server; In the case that there are multiple continuous and data-consistent recognition results among all the recognition results, the server configuration mapping relationship is modified to a target scanning result, where the target recognition result represents the multiple continuous and data-consistent recognition results among all the scanning results.

7. The server monitoring method according to any one of claims 1 to 6, characterized in that: The method further comprises: During monitoring of the server based on the final server configuration mapping relationship, if it is determined that a non-hot-swappable component among the components recorded in the final server configuration mapping relationship cannot operate, generating first fault prompt information to prompt that the non-hot-swappable component is damaged; During monitoring of the server based on the final server configuration mapping relationship, if it is determined that a hot-swappable component among the components recorded in the final server configuration mapping relationship is unable to operate, or if it is determined that a hot-swappable component among the components recorded in the final server configuration mapping relationship is unable to operate, generating second fault prompt information to prompt that the hot-swappable component is damaged or has been normally removed; After determining a final server configuration mapping relationship based on the multiple server configuration mapping relationships, the method further includes: When it is determined that a non-hot-swappable component among the components recorded in the final server configuration mapping relationship cannot operate, third fault prompt information is generated to prompt that the non-hot-swappable component is damaged or abnormally removed.

8. A substrate controller, characterized in that: include: A first processing unit is configured to identify all components connected to the server multiple times before the server executes a service, and generate multiple server configuration mapping relationships, wherein the server configuration mapping relationships include at least mapping relationships between unique identifiers of the components and locations and states of the components; A second processing unit, configured to determine a final server configuration mapping relationship based on the multiple server configuration mapping relationships; The third processing unit is configured to monitor the server based on the final server configuration mapping relationship during the process of the server executing the service.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the server monitoring method according to any one of claims 1 to 7 are implemented.

10. A server system, characterized in that: include: A baseboard controller and a server are communicatively connected, wherein the baseboard controller is used to execute the steps of the server monitoring method according to any one of claims 1 to 7.

Images