Fault detection method and computing device

By obtaining the operating status data of target components in the server, automatically judge and detecting, the problem of low fault detection efficiency of components in the server is solved, and the automatic detection of fans is realized, and the detection efficiency and accuracy are improved.

CN118939489APending Publication Date: 2024-11-12XFUSION DIGITAL TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410948009.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-15
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

It is difficult to automate the fault detection of components in existing servers, especially the daily maintenance and maintenance of fans require manual manual, resulting in low detection efficiency and easy to ignore minor faults, affecting the cooling capacity, and thus leading to greater losses.

Method used

By obtaining the operating status data of the target components in the server, we determine whether the preset detection trigger conditions are met, and automatically conduct detection, including software operation strategies and hardware implementation functions detection, and use the substrate management controller (BMC) to obtain the fan speed and temperature The data matches the preset speed regulation standard baseline, determines the detection triggering conditions, and performs automatic detection.

Benefits of technology

It improves the detection efficiency of components in the server, realizes the automation of fan software operation strategies and hardware detection, reduces manual intervention, timely discovers abnormalities, reduces the probability of false alarms, and improves operation and maintenance efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939489A_ABST
    Figure CN118939489A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a fault detection method and computing equipment. A specific implementation mode of the method comprises the steps of obtaining running state data of a target component in a server; judging whether a detection triggering condition of the target component is met or not according to the running state data; under the condition that the detection triggering condition is met, detecting a software operation strategy corresponding to the target component; and under the condition that the software operation strategy corresponding to the target component is normal, detecting a hardware implementation function of the target component. Therefore, whether the preset detection triggering condition is met or not can be judged based on the running state data of the target component in the server, and when the detection triggering condition is met, the target component is automatically detected, so that the detection efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of server internal component fault detection, and in particular to a fault detection method and computing device. Background Art

[0002] The server includes many components, such as network cards, cooling systems, and so on. The daily maintenance and inspection of these components are difficult and labor-intensive. Taking the server that uses fan cooling as the main cooling method as an example, the daily maintenance and inspection of the fan is difficult and labor-intensive. For example, fans with minor faults, unsatisfactory rotation speeds, and reduced cooling capacity are not easy to be discovered and exposed in time, which may affect the cooling of the server, and over time will cause greater damage to important components in the server and the fan itself. The existing fan cooling detection usually needs to be manually issued, so it is difficult to complete the detection when a large number of servers need to be tested. In short, how to achieve automatic detection of internal server components is of great significance. Summary of the invention

[0003] The embodiments of the present application provide a fault detection method and computing device, which can determine whether a preset detection trigger condition is met based on the operating status data of the target component in the server, and automatically detect the target component when the detection trigger condition is met, thereby improving detection efficiency.

[0004] In a first aspect, an embodiment of the present application provides a fault detection method, the method comprising: obtaining operating status data of a target component in a server; judging whether a detection trigger condition of the target component is met based on the operating status data; when the detection trigger condition is met, detecting a software operating strategy corresponding to the target component; and when the software operating strategy corresponding to the target component is normal, detecting a hardware implementation function of the target component.

[0005] In this solution, it is possible to determine whether a preset detection trigger condition is met based on the operating status data of the target component in the server. When the detection trigger condition is met, the target component is automatically detected, thereby improving detection efficiency.

[0006] In some possible examples, the target component includes a fan in the server, and the operating status data includes a fan speed and a target temperature at a preset position in the server, wherein the preset position includes an air inlet position and / or a position of a component to be dissipated in the server; and, judging whether a detection trigger condition of the target component is met based on the operating status data, includes: matching the fan speed and target temperature in the operating status data with a preset speed regulation standard baseline corresponding to the fan, wherein the speed regulation standard baseline includes a correspondence between the temperature at a preset position in the server and the expected speed of the fan; and determining that the detection trigger condition of the fan is met when the fan speed and the target temperature do not match the speed regulation standard baseline.

[0007] In this example, whether the detection trigger condition of the fan is met can be determined based on the speed regulation standard baseline corresponding to the fan.

[0008] In some possible examples, determining whether the detection trigger condition of the target component is met based on the operating status data also includes: when the fan speed satisfies a preset first condition, determining that the detection trigger condition of the fan is met, wherein the first condition includes: the fan speed continues to exceed a preset speed threshold for a preset time period, or the difference between the maximum and minimum values ​​of the fan speed exceeds a preset threshold; when the target temperature satisfies a preset second condition, determining that the detection trigger condition of the fan is met, wherein the second condition includes: the target temperature continues to be higher than the preset temperature threshold for a preset time period, or the difference between the maximum and minimum values ​​of the target temperature exceeds the preset threshold.

[0009] In this example, different conditions may be used to determine whether a detection trigger condition of the fan is met.

[0010] In some possible examples, the software operation strategy corresponding to the target component includes a speed control strategy for adjusting the fan speed based on a target temperature; and the detection of the software operation strategy corresponding to the target component includes: based on the speed control standard baseline, verifying the static value in the speed control strategy, wherein the static value includes the target speed corresponding to each temperature and a statistical value of the target speed corresponding to multiple temperatures; if the static value in the speed control strategy fails to be verified, it is determined that the speed control strategy corresponding to the fan is abnormal.

[0011] In this example, some abnormal fan speed regulation strategies may be determined based on verification of static values ​​in the speed regulation strategy.

[0012] In some possible examples, the server includes multiple fans, the preset position includes a target position, and the target position is related to the speed regulation strategy of at least some of the multiple fans; and the software operation strategy corresponding to the target component is detected, which also includes: when the static value in the speed regulation strategy is verified, a number of fan speed test values ​​are sent to the server based on the expected speed corresponding to the target position in the speed regulation standard baseline, and the server sends a speed control signal to at least some of the fans corresponding to the target position based on the fan speed test value and the speed regulation strategy corresponding to the target position; it is determined whether the fan speed test value and the speed control signal match; when the fan speed test value and the speed control signal match, it is determined that the speed regulation strategy corresponding to the target position is normal.

[0013] In this example, if the static value in the speed regulation strategy is verified, it is possible to further verify whether the speed regulation strategy corresponding to the target position is normal, thereby making the verification of the speed regulation strategy more accurate.

[0014] In some possible examples, the server includes multiple fans, the preset position includes a target position, and the target position is related to the software operation policy of at least some of the multiple fans; the detection of the hardware implementation function of the target component includes: sending a number of test temperatures to the server based on the temperature of the target position in the speed regulation standard baseline, and the server sends a speed control signal to at least some of the fans corresponding to the target position based on the number of test temperatures and the speed regulation policy corresponding to the target position; judging whether the expected speeds corresponding to the number of test temperatures in the speed regulation standard baseline match the actual speeds of at least some of the fans; and determining that the hardware of at least some of the fans is abnormal when the expected speeds corresponding to the number of test temperatures do not match the actual speeds of at least some of the fans.

[0015] In this example, it can be determined whether the fan hardware is abnormal, thereby realizing the detection of the fan hardware.

[0016] In some possible examples, the components to be cooled include at least one of the following: a CPU, a memory, a hard disk, and a network card.

[0017] In this example, the temperature of the location of the component to be cooled in the server can be obtained as the running status data of the fan.

[0018] In some possible examples, the method further includes: when the software running strategy corresponding to the target component is abnormal, sending an alarm message for prompting that the software running strategy of the target component is abnormal.

[0019] In this example, detailed alarm information can be sent to the designated device to indicate that an abnormality has occurred in the software operation strategy of the target component.

[0020] In some possible examples, the method further includes: when the hardware implementation function detection of the target component fails, sending an alarm message for prompting a hardware abnormality of the target component.

[0021] In this example, when an abnormality occurs in the hardware of the target component, detailed alarm information for prompting that the abnormality occurs in the hardware of the target component can be sent to the designated device.

[0022] In the second aspect, an embodiment of the present application provides a fault detection device, including: an acquisition unit, configured to acquire operating status data of a target component in a server; a judgment unit, configured to judge whether a detection trigger condition of the target component is met based on the operating status data; a first detection unit, configured to detect a software operating strategy corresponding to the target component when the detection trigger condition is met; and a second detection unit, configured to detect a hardware implementation function of the target component when the software operating strategy corresponding to the target component is normal.

[0023] In a third aspect, an embodiment of the present application provides a computing device, including:

[0024] at least one memory for storing a program;

[0025] At least one processor is used to execute the program stored in the memory. When the program stored in the memory is executed, the processor is used to execute the method described in any possible implementation manner of the first aspect.

[0026] In a fourth aspect, an embodiment of the present application provides a computer storage medium, in which instructions are stored. When the instructions are executed on a computer, the computer executes the method described in any possible implementation of the first aspect.

[0027] In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.

[0029] Figure 1 A schematic diagram showing an application scenario in which the embodiments of this specification can be applied;

[0030] Figure 2 A schematic diagram of a process flow of a fault detection method according to an embodiment is shown;

[0031] Figure 3 A schematic diagram showing how to determine whether a fan detection trigger condition is met according to different conditions;

[0032] Figure 4 A schematic diagram showing an example of a fault detection method using a fan in a server as an example;

[0033] Figure 5 A schematic block diagram of a fault detection device according to an embodiment is shown. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0035] In the description of the embodiments of the present application, any embodiment or design scheme of "exemplary", "for example" or "for example" should not be understood as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0036] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized. "At least one" can be one or more, where a plurality is two or more.

[0037] To facilitate understanding of the technical solutions of the embodiments of the present application, the terms involved in this document are explained below.

[0038] Baseboard management controller: The full English name is Baseboard Management Controller, abbreviated as BMC. The baseboard management controller is a dedicated controller used to monitor and manage servers.

[0039] BMC can be used to achieve a variety of functions. For example, it can be used to manage device information. Specifically, it can record detailed information about the server, including model, manufacturer, date, production and technical information of each component, chassis information, motherboard information, etc., as well as BMC's own information, such as server host name, IP address, BMC firmware version, etc.

[0040] For another example, BMC can also be used to implement server status monitoring and management. Specifically, it can detect the temperature, voltage and other health status of each server component (such as CPU, memory, hard disk, fan, frame, etc.). At the same time, the fan speed is adjusted in real time according to the conditions of each temperature collection point to ensure that the server does not overheat and control the overall power consumption within a reasonable range. If any abnormality occurs in a single board component, BMC will report the information to the upper-level network management in a timely manner through various industry-wide specifications such as SNMP protocol, SMTP protocol, and Redfile protocol.

[0041] For another example, BMC can also be used to implement remote control management of servers, including server power on / off, restart, maintenance, firmware update, system installation and other operations.

[0042] For example, the BMC can also be used for maintenance management, which can specifically include log management, user management, BIOS management, alarm management, etc.

[0043] As mentioned above, how to realize automatic detection of internal components of a server is of great significance. Taking the fans in a server as an example, in some implementations, first, the speed values ​​of all groups of fans can be obtained, and the average speed values ​​of all groups of fans can be calculated. Then, the speed abnormality rate of each group of fans is calculated based on the calculated average speed value and the speed value of each group of fans. Finally, it is determined whether the speed abnormality rate of each group of fans is greater than a first threshold, and an early warning message is issued when it is greater than the first threshold. In the above implementation, the speed of each group of fans is obtained and the average value is calculated as the first threshold, and then the speed of each group of fans is compared with the average speed. Only the fan with the greatest impact can be found, and a more accurate judgment cannot be made.

[0044] In order to realize automatic detection of components in the server, the embodiment of the present application also provides a fault detection method, so as to automatically detect the target components in the server and improve the detection efficiency. Figure 1 As shown, Figure 1 A schematic diagram showing an application scenario in which the embodiments of this specification can be applied is shown. Figure 1In the application scenario shown, taking the fan used for heat dissipation in the server as an example, the baseboard management controller 101 can first obtain the operating status data of the fan 1021 in the server 102. For example, the operating status data of the fan may include but is not limited to the fan speed, the temperature at a preset position in the server, etc. Then, the baseboard management controller 101 can determine whether the detection trigger condition of the fan 1021 is met based on the operating status data of the fan 1021. In the case where the detection trigger condition of the fan 1021 is met, the software operation strategy corresponding to the fan 1021 is detected. If the software operation strategy detection fails, an alarm message for indicating that the software operation strategy is abnormal is sent. If the software operation strategy detection passes, that is, the software operation strategy of the fan 1021 is normal, the fan 1021 itself is detected. If the fan 1021 itself fails to be detected, an alarm message for indicating that the hardware of the fan 1021 is abnormal is sent. Thus, the automatic detection of the fans in the server can be realized, and the detection process includes the detection of the fan software operation strategy and the fan hardware, so as to report refined alarms from the perspectives of software operation strategy, hardware, etc., so that the operation and maintenance personnel can quickly locate the abnormality. In addition, this embodiment does not need to rely on too much hardware, which can reduce the probability of false alarms.

[0045] Continue to see Figure 2 , Figure 2 FIG. 1 is a flow chart of a fault detection method according to an embodiment. The method may be executed by a baseboard management controller (BMC), which may monitor and manage the status of the server, for example, detecting the temperature, voltage and other health status of various components of the server (for example, CPU, memory, hard disk, fan, etc.). Figure 2 As shown, the fault detection method may include the following steps 201 to 204, specifically:

[0046] Step 201, obtaining the operating status data of the target component in the server.

[0047] In this embodiment, the baseboard management controller BMC can obtain the running status data of the target component in the server. Here, the target component can include various components in the server, including but not limited to CPU, memory, hard disk, fan, network card, etc.

[0048] Step 202: determine whether a detection trigger condition of a target component is met based on the operating status data.

[0049] In this embodiment, corresponding detection trigger conditions can be preset for the target component. For example, the corresponding detection trigger conditions can be preset by the R&D personnel according to actual needs. As an example, the detection trigger conditions can be used to specify that automatic detection is triggered when the operating status data of the target component reaches those preset conditions. In this way, based on the acquired operating status data of the target component, it can be determined whether the detection trigger conditions of the target component are met.

[0050] For example, assuming that the target component is a network card, the running status data of the network card may include network speed, fluctuation of network speed, etc. At this time, the detection trigger conditions corresponding to the network card may be set to include but are not limited to: the network speed is lower than a preset threshold for a preset period of time, the fluctuation of the network speed (for example, the difference between the maximum value and the minimum value) exceeds a preset threshold, etc. Therefore, it can be determined whether the detection trigger conditions of the network card are met based on the running status data of the network card.

[0051] In some implementations, the target component may also include a fan in a server, and the operating status data of the fan may include the fan speed and the target temperature at a preset position in the server. Here, the preset position may include the air inlet position and / or the position of the component to be cooled in the server. For example, the component to be cooled in the server may include important components in the server, for example, the component to be cooled may include at least one of the following: CPU, memory, hard disk, network card, etc. In practice, the temperature of the position of the component to be cooled in the server may be collected by a temperature sensor. Based on this, the above step 202 may include the following steps 1) and 2), specifically:

[0052] Step 1) matches the fan speed and target temperature in the operating status data with the preset speed regulation standard baseline corresponding to the fan.

[0053] In this implementation, a speed control standard baseline can be pre-set for the fan, and the speed control standard baseline can include the corresponding relationship between the temperature at a preset position in the server and the expected speed of the fan. Taking the preset position as the position of the CPU as an example, the speed control standard baseline can include the expected speed of the fan corresponding to the position of the CPU at different temperatures. Thus, the fan speed and target temperature in the operating status data can be matched with the speed control standard baseline corresponding to the fan. For example, it can be determined whether the corresponding relationship between the target temperature and the fan speed in the operating status data satisfies the corresponding relationship between the preset temperature and the expected speed in the speed control standard baseline. If so, it indicates a match; if not, it indicates a mismatch.

[0054] Step 2), when the fan speed and the target temperature do not match the speed regulation standard baseline, it is determined that the fan detection trigger condition is met.

[0055] In this implementation, if the fan speed and target temperature in the operating status data do not match the speed control standard baseline, it can be determined that the fan detection trigger condition is met. Through this implementation, it can be determined whether the fan detection trigger condition is met based on the speed control standard baseline corresponding to the fan.

[0056] In some implementations, the above step 202 may also include the following cases a) and b), specifically:

[0057] Case a), when the fan speed meets a preset first condition, it is determined that the fan detection trigger condition is met.

[0058] In case a), the preset first condition may include: the fan speed exceeds the preset speed threshold for a preset time period, or the difference between the maximum and minimum values ​​of the fan speed exceeds the preset threshold. In other words, when the fan speed continues to be high, it can be determined that the fan detection trigger condition is met. And when the fan speed fluctuates greatly, it can be determined that the fan detection trigger condition is met.

[0059] Case b), when the target temperature satisfies a preset second condition, it is determined that the fan detection trigger condition is met.

[0060] In case b), the preset second condition may include: the target temperature is higher than the preset temperature threshold for a preset time period, or the difference between the maximum and minimum values ​​of the target temperature exceeds the preset threshold. In other words, when the target temperature is continuously high, it can be determined that the detection trigger condition of the fan is met. And when the target temperature fluctuates greatly, it can be determined that the detection trigger condition of the fan is met. Through this implementation, it can be determined whether the detection trigger condition of the fan is met through different conditions.

[0061] like Figure 3 As shown, Figure 3 A schematic diagram is shown for determining whether a fan detection trigger condition is met according to different conditions. Figure 3 In the example shown, it is determined whether the detection trigger condition of the fan is met according to different conditions. Figure 3 The situations in which the fan detection trigger conditions are determined to be met may include: the fan speed and target temperature do not match the speed regulation standard baseline, the fan speed continues to be high, the fan speed fluctuates greatly, the target temperature continues to be high, the target temperature fluctuates greatly, etc.

[0062] Step 203: When the detection trigger condition is met, the software operation strategy corresponding to the target component is detected.

[0063] In this embodiment, when the detection trigger condition of the target component is met, the software running policy corresponding to the target component can be detected.

[0064] In some implementations, it is assumed that the target component is a fan in a server, and the operating status data of the fan may include the fan speed and the target temperature at a preset position in the server, where the preset position may include the air inlet position and / or the position of the component to be cooled in the server. At this time, the software operation strategy corresponding to the fan may include a speed regulation strategy for adjusting the fan speed based on the target temperature. Here, the speed regulation strategy of the fan may be configured by a developer who develops the fan control program according to a speed regulation standard baseline corresponding to the fan. Therefore, the information configured by the developer can be verified to verify whether the developer has configured it correctly. Based on this, the speed regulation strategy corresponding to the fan is detected, which may specifically include the following steps S1 and S2, specifically:

[0065] Step S1, verifying the static value in the speed regulation strategy based on the speed regulation standard baseline.

[0066] In this implementation, the static value in the speed control strategy can be verified based on the speed control standard baseline corresponding to the fan. In this example, the static value in the speed control strategy can include the target speed corresponding to each temperature, and the statistical value of the target speed corresponding to multiple temperatures (for example, maximum value, minimum value, etc.). For example, the expected speed corresponding to each temperature in the speed control standard baseline corresponding to the fan can be compared with the static value in the speed control strategy to determine whether the static value in the speed control strategy is correct. If it is correct, it means that the static value verification has passed; if it is incorrect, it means that the static value verification has failed.

[0067] Step S2: if the static value verification in the speed regulation strategy fails, it is determined that the speed regulation strategy corresponding to the fan is abnormal.

[0068] In this implementation, if the static value verification in the speed control strategy fails, it means that the developer's configuration information for the fan speed control strategy is incorrect. Therefore, it can be determined that the speed control strategy corresponding to the fan is abnormal. Through this implementation, some abnormal fan speed control strategies can be determined based on the verification of the static value in the speed control strategy.

[0069] In some implementations, the server may include multiple fans, and the preset position in the server may include a target position, which is related to the speed control strategy of at least some of the multiple fans. For example, assuming that the target position is the position of the CPU, and the temperature of the position of the CPU is related to the speed control strategy of at least some of the fans in the server (for example, several fans closest to the CPU). Based on this, the speed control strategy corresponding to the fan is detected, and the following steps S3-S5 may be specifically included:

[0070] Step S3: When the static value in the speed regulation strategy is verified to be passed, a number of fan speed test values ​​are sent to the server based on the expected speed corresponding to the target position in the speed regulation standard baseline.

[0071] In this implementation, the speed control standard baseline may include the corresponding relationship between the temperature at the target position in the server and the expected speed of the fan. Therefore, when the static value in the speed control strategy of the fan is verified, a number of fan speed test values ​​may be sent to the server based on the expected speed corresponding to the target position in the speed control standard baseline. For example, assuming that the temperature at the target position in the speed control standard baseline includes 15, 20, 30, 40, and 50, and the expected speed corresponding to each temperature is 30%, 35%, 45%, 70%, and 100% of the maximum speed, then part of the expected speed, for example, 35%, 45%, and 70% of the maximum speed may be selected as the fan speed test value and sent to the server. The server sends a speed control signal to at least part of the fans corresponding to the target position based on the fan speed test value and the speed control strategy corresponding to the target position. For example, the speed control signal may be a fan PWM (Pulse Width Modulation, pulse width modulation) value, and the fan PWM value may refer to the duty cycle of the pulse width modulation or the high level duration in the cycle, and PWM may be used to control the speed of the fan motor.

[0072] Step S4, receiving the speed control signal from the server, and determining whether the fan speed test value matches the speed control signal.

[0073] In this implementation, the BMC can obtain the speed control signal sent by the server to the fan, and can determine whether the fan speed test value and the speed control signal match, for example, whether they are equal or similar. If they are equal or similar, it indicates a match; otherwise, it indicates a mismatch.

[0074] Step S5: When the fan speed test value and the speed control signal match, it is determined that the speed regulation strategy corresponding to the target position is normal.

[0075] In this implementation, if the fan speed test value matches the speed control signal, it means that the fan speed control strategy can send a correct control signal to the fan according to the received fan speed test value to control the fan. Therefore, it can be determined that the speed control strategy corresponding to the target position is normal. Conversely, it can be determined that the speed control strategy corresponding to the target position is abnormal. Through this implementation, when the static value verification in the speed control strategy is passed, it is possible to further verify whether the speed control strategy corresponding to the target position is normal, thereby making the verification of the speed control strategy more accurate.

[0076] Step 204: When the software operation strategy corresponding to the target component is normal, the hardware implementation function of the target component is tested.

[0077] In this embodiment, after the software operation strategy of the target component is detected through step 203, if the detection result of the software operation strategy of the target component shows that the software operation strategy is normal, the hardware implementation function of the target component itself can be detected. Here, when the target component is detected, first detect whether the software operation strategy of the target component is normal, and then, when the software operation strategy is normal, further detect whether the hardware implementation function of the target component is normal. In this way, the source of the problem can be isolated. Specifically, by first detecting the software operation strategy of the target component, it can be preliminarily determined whether the problem occurs at the software operation strategy level. If there is an abnormality in the software operation strategy, then directly detecting the hardware implementation function of the target component may mislead the detection result due to the problem of the software operation strategy, thereby making the problem location complicated and difficult. Eliminating the problem of the software operation strategy first can ensure the accuracy of the subsequent hardware implementation function detection results.

[0078] Continuing to take the target component as the network card as an example, the firmware of the network card is the basic program that controls the operation of the network card, and the driver of the network card is the key to enable the network card to run normally in the operating system. Therefore, the firmware version and driver version of the network card are related to the software operation strategy of the network card. When the detection trigger condition of the network card is met, first, it can be detected whether the firmware version and driver version of the network card are consistent with the version of the BMC server. If not, an alarm is reported; if it is consistent, the network card itself can be detected. For example, it can be checked whether there is a large amount of data transmission in the background. If so, wait for the data transmission to complete and check whether the network speed is normal. If it is normal, the detection ends; if it is not normal, further check the CPU usage. If the CPU usage is too high, reduce the CPU usage and observe whether the network speed is normal. If it is normal, stop checking; if it is not normal, report an abnormal alarm.

[0079] In some implementations, the target component may include a fan in a server, and the operating status data of the fan may include the fan speed and the target temperature at a preset position in the server. Here, the preset position may include the air inlet position and / or the position of the component to be cooled in the server. In this example, the server may include multiple fans, and the preset position may include a target position, which is related to the software operation strategy of at least some of the multiple fans. Based on this, in step 204, the hardware implementation function of the target component is detected, which may include the following steps one, two and three, specifically:

[0080] Step 1), sending several test temperatures to the server based on the temperature of the target location in the speed regulation standard baseline.

[0081] In this implementation, several test temperatures can be sent to the server according to the temperature of the target position in the speed control standard baseline. For example, several temperatures can be selected from multiple temperatures corresponding to the target position in the speed control standard baseline as test temperatures and sent to the server. The server sends a speed control signal to at least some fans corresponding to the target position based on the several test temperatures and the speed control strategy corresponding to the target position.

[0082] Step 2) It is determined whether the expected rotation speeds corresponding to the above-mentioned several test temperatures in the speed regulation standard baseline match the actual rotation speeds of at least part of the above-mentioned fans.

[0083] In this implementation, the expected rotational speed matches the actual rotational speed, which may mean that the actual rotational speed is the same as or close to the deadline rotational speed (for example, the difference is less than a preset value).

[0084] Step three): when the expected rotation speeds corresponding to the plurality of test temperatures do not match the actual rotation speeds of at least some of the fans, it is determined that the hardware of at least some of the fans is abnormal.

[0085] In this implementation, since the speed control strategy corresponding to the fan has been detected to be normal, if the expected speed corresponding to the test temperature does not match the actual speed of the fan, it can be said that the fan cannot work normally according to the received speed control signal, so it can be determined that the fan hardware is abnormal. Through this implementation, it can be determined whether the fan hardware is abnormal, thereby realizing the detection of the fan hardware.

[0086] In some implementations, when the software running strategy corresponding to the target component is abnormal, an alarm message for prompting that the software running strategy of the target component is abnormal may be sent.

[0087] In this implementation, if it is detected that the software operation strategy corresponding to the target component is abnormal, an alarm message can be sent to a designated device (for example, a device used by an operation and maintenance personnel), and the alarm message can be used to prompt that the software operation strategy of the target component is abnormal. Through this implementation, detailed alarm information for prompting that the software operation strategy of the target component is abnormal can be sent to the designated device.

[0088] In some implementations, when the hardware implementation function detection of the target component fails, an alarm message for prompting the hardware abnormality of the target component may be sent.

[0089] In this implementation, after the hardware implementation function of the target component itself is detected, if the hardware implementation function of the target component fails to be detected, an alarm message can be sent to the designated device, and the alarm message can be used to prompt that the hardware of the target component is abnormal. Through this implementation, when the hardware of the target component is abnormal, detailed alarm information for prompting that the hardware of the target component is abnormal can be sent to the designated device.

[0090] Reviewing the above process, in the embodiment of the present application, it is possible to determine whether the preset detection trigger condition is met based on the running status data of the target component in the server. When the detection trigger condition is met, the software running strategy corresponding to the target component is automatically detected, and when the software running strategy corresponding to the target component is normal, the hardware of the target component is further detected. In this way, the detection of the target component can be automatically triggered, and there is no need to manually issue a detection instruction, so that the target component with abnormalities can be detected in time. In addition, when detecting the target component, the software running strategy of the target component and the hardware implementation function of the target component can be distinguished for detection, thereby making the detection more precise and facilitating the operation and maintenance personnel to locate the fault.

[0091] like Figure 4 As shown, Figure 4 A schematic diagram of an example of a fault detection method using a fan in a server as an example is shown. Figure 4 In the example shown, the server may include multiple fans, for example, fan 1, fan 2, fan 3, ... fan n, and the model of the fan is X.

[0092] In this example, the BMC periodically obtains that the temperature at the air inlet of the server is 35 degrees and the speed of fan 2 is 59% of the maximum speed. The BMC can also preload data corresponding to the speed control standard baseline corresponding to the air inlet position, for example, data in XML format.

[0093] S401: Assuming that the fan speed error of model X is ±7%, it can be known from the speed control standard baseline that when the air inlet temperature is 35 degrees, the standard fan speed of model X should be 70% of the maximum speed, and the normal speed range is: 63%-77%. Since the fan speed is 59% at this time, which is not within the normal speed range and does not meet the requirements, it is determined that the detection trigger condition of fan 2 is met, and the self-test mechanism for fan 2 is triggered;

[0094] S402: Detect the speed control strategy of Fan 2. Specifically: First, obtain the static value of the speed control strategy corresponding to the air inlet position of the server and compare it with the value in the speed control standard baseline to verify whether the static value of the speed control strategy corresponding to the air inlet position is normal. Secondly, if the static value of the speed control strategy corresponding to the air inlet position is verified to be normal, further verify the speed control strategy corresponding to the air inlet position. For example, set Fan 2 to manual mode, and send fan speed test values ​​of 80%, 90%, and 100% to the server respectively. Then check the fan PWM values ​​one by one and they are 80%, 90%, and 100% respectively. It can be seen that the speed control strategy corresponding to the air inlet position is normal;

[0095] S403: Perform hardware fault detection on fan 2. Specifically, select high temperature points such as 40 degrees, 45 degrees, and 50 degrees for verification, modify the values ​​of the temperature sensor corresponding to the air inlet position to the above three test temperature values, and check whether the actual speed of fan 2 meets the requirements. When the temperature is set to 40 degrees, the expected speed should be 80% of the maximum speed, and the normal speed range is: 73%-87%, while the actual speed of fan 2 is 70% of the maximum speed, which is not within the normal speed range. Therefore, it is determined that the hardware of fan 2 is abnormal, and the hardware alarm information of fan 2 is reported.

[0096] According to an embodiment of another aspect, a fault detection device is provided, wherein the device can be deployed in a baseboard management controller BMC. Figure 5 FIG. 1 shows a schematic block diagram of a fault detection device according to an embodiment. Figure 5 As shown, the fault detection device 500 may include: an acquisition unit 501, configured to acquire the operating status data of the target component in the server; a judgment unit 502, configured to judge whether the detection trigger condition of the target component is met based on the operating status data; a first detection unit 503, configured to detect the software operation strategy corresponding to the target component when the detection trigger condition is met; and a second detection unit 504, configured to detect the hardware implementation function of the target component when the software operation strategy corresponding to the target component is normal.

[0097] In some optional implementations, the target component includes a fan in the server, and the operating status data includes a fan speed and a target temperature at a preset position in the server, wherein the preset position includes an air inlet position and / or a position of a component to be cooled in the server; and the judgment unit 502 is further configured to: match the fan speed and target temperature in the operating status data with a preset speed regulation standard baseline corresponding to the fan, wherein the speed regulation standard baseline includes a correspondence between the temperature at a preset position in the server and the expected speed of the fan; when the fan speed and the target temperature do not match the speed regulation standard baseline, determine that the detection trigger condition of the fan is met.

[0098] In some optional implementations, the judgment unit 502 is further configured to: when the fan speed satisfies a preset first condition, determine that the detection trigger condition of the fan is met, wherein the first condition includes: the fan speed continues to exceed the preset speed threshold for a preset time period, or the difference between the maximum and minimum values ​​of the fan speed exceeds the preset threshold; when the target temperature satisfies a preset second condition, determine that the detection trigger condition of the fan is met, wherein the second condition includes: the target temperature continues to be higher than the preset temperature threshold for a preset time period, or the difference between the maximum and minimum values ​​of the target temperature exceeds the preset threshold.

[0099] In some optional implementations, the software running strategy corresponding to the target component includes a speed control strategy for adjusting the fan speed based on the target temperature; the first detection unit 503 is further configured to: verify the static value in the speed control strategy based on the speed control standard baseline, wherein the static value includes the target speed corresponding to each temperature and the statistical value of the target speed corresponding to multiple temperatures; if the static value in the speed control strategy fails to be verified, it is determined that the speed control strategy corresponding to the fan is abnormal.

[0100] In some optional implementations, the server includes multiple fans, the preset position includes a target position, and the target position is related to the speed regulation strategy of at least some of the multiple fans; and the first detection unit 503 is further configured to: when the static value in the speed regulation strategy is verified, send a number of fan speed test values ​​to the server based on the expected speed corresponding to the target position in the speed regulation standard baseline, and the server sends a speed control signal to at least some of the fans corresponding to the target position based on the fan speed test value and the speed regulation strategy corresponding to the target position; determine whether the fan speed test value and the speed control signal match; when the fan speed test value and the speed control signal match, determine that the speed regulation strategy corresponding to the target position is normal.

[0101] In some optional implementations, the server includes multiple fans, the preset position includes a target position, and the target position is related to the software operation policy of at least some of the multiple fans; the second detection unit 504 is further configured to: send a number of test temperatures to the server based on the temperature of the target position in the speed regulation standard baseline, and the server sends a speed control signal to at least some of the fans corresponding to the target position based on the number of test temperatures and the speed regulation policy corresponding to the target position; determine whether the expected speeds corresponding to the number of test temperatures in the speed regulation standard baseline match the actual speeds of at least some of the fans; when the expected speeds corresponding to the number of test temperatures do not match the actual speeds of at least some of the fans, determine that the hardware of at least some of the fans is abnormal.

[0102] In some optional implementations, the components to be cooled include at least one of the following: a CPU, a memory, a hard disk, and a network card.

[0103] In some optional implementations, the device 500 also includes: a first sending unit (not shown in the figure), configured to send an alarm message indicating that the software running strategy of the target component is abnormal when the software running strategy corresponding to the target component is abnormal.

[0104] In some optional implementations, the device 500 further includes: a second sending unit (not shown in the figure), configured to send an alarm message indicating a hardware abnormality of the target component when the hardware implementation function detection of the target component fails.

[0105] Based on the method in the above embodiment, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program runs on a processor, the processor executes the method in the above embodiment.

[0106] Based on the method in the above embodiment, an embodiment of the present application provides a computer program product, characterized in that when the computer program product runs on a processor, the processor executes the method in the above embodiment.

[0107] Based on the method in the above embodiment, the embodiment of the present application provides a computing device, and the computing device includes a motherboard and a chip. Among them, the chip is integrated on the motherboard, and the chip includes at least one memory for storing programs; at least one processor for executing the program stored in the memory, and when the program stored in the memory is executed, the processor is used to execute the method in the above embodiment. In the embodiment of the present application, the computing device can be a network device such as a server and a host. The method steps in the embodiment of the present application can be implemented by hardware, or by the processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory (random access memory, RAM), flash memory, read-only memory (read-only memory, ROM), programmable read-only memory (programmable rom, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium may reside in an ASIC.

[0108] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions may be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

[0109] It should be understood that the various numerical numbers involved in the embodiments of the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application.

Claims

1. A fault detection method, characterized in that: The method comprises: Obtaining the operating status data of the target component in the server; Determining whether a detection trigger condition of the target component is met according to the operating status data; When the detection trigger condition is met, detecting the software operation strategy corresponding to the target component; When the software operation strategy corresponding to the target component is normal, the hardware implementation function of the target component is detected.

2. The method according to claim 1, characterized in that The target component includes a fan in the server, and the operating status data includes a fan speed and a target temperature at a preset position in the server, wherein the preset position includes an air inlet position and / or a position of a component to be cooled in the server; and The step of judging whether a detection trigger condition of the target component is met according to the operating status data includes: Matching the fan speed and target temperature in the operating status data with a preset speed regulation standard baseline corresponding to the fan, wherein the speed regulation standard baseline includes a corresponding relationship between the temperature at a preset position in the server and the expected speed of the fan; When the fan speed and the target temperature do not match the speed regulation standard baseline, it is determined that a detection trigger condition of the fan is met.

3. The method according to claim 2, characterized in that The step of judging whether a detection trigger condition of the target component is met according to the operating status data further includes: When the fan speed meets a preset first condition, determining that a detection trigger condition of the fan is met, wherein the first condition includes: the fan speed exceeds a preset speed threshold for a preset time period, or the difference between the maximum and minimum values ​​of the fan speed exceeds a preset threshold; When the target temperature satisfies a preset second condition, it is determined that the detection trigger condition of the fan is met, wherein the second condition includes: the target temperature is higher than a preset temperature threshold for a preset period of time, or the difference between the maximum and minimum values ​​of the target temperature exceeds a preset threshold.

4. The method according to claim 2, characterized in that: The software operation strategy corresponding to the target component includes a speed regulation strategy for adjusting the fan speed based on the target temperature; And, the detecting of the software operation strategy corresponding to the target component includes: Based on the speed regulation standard baseline, verifying the static value in the speed regulation strategy, wherein the static value includes the target speed corresponding to each temperature and the statistical value of the target speed corresponding to multiple temperatures; When the static value verification in the speed regulation strategy fails, it is determined that the speed regulation strategy corresponding to the fan is abnormal.

5. The method according to claim 4, wherein: The server includes a plurality of fans, the preset position includes a target position, and the target position is related to a speed regulation strategy of at least some of the plurality of fans; And, detecting the software operation strategy corresponding to the target component also includes: In the case where the static value in the speed regulation strategy is verified, a plurality of fan speed test values ​​are sent to the server based on the expected speed corresponding to the target position in the speed regulation standard baseline, and the server sends speed control signals to at least some fans corresponding to the target position based on the fan speed test values ​​and the speed regulation strategy corresponding to the target position; Determining whether the fan speed test value matches the speed control signal; When the fan speed test value matches the speed control signal, it is determined that the speed regulation strategy corresponding to the target position is normal.

6. The method according to claim 2, characterized in that The server includes a plurality of fans, the preset position includes a target position, and the target position is related to a software operation strategy of at least some of the plurality of fans; The detecting of the hardware implementation function of the target component includes: Sending a plurality of test temperatures to the server based on the temperature of the target position in the speed regulation standard baseline, and the server sending a speed control signal to at least part of the fans corresponding to the target position based on the plurality of test temperatures and the speed regulation strategy corresponding to the target position; Determining whether the expected speeds corresponding to the plurality of test temperatures in the speed regulation standard baseline match the actual speeds of at least some of the fans; When the expected rotation speeds corresponding to the plurality of test temperatures do not match the actual rotation speeds of the at least some of the fans, it is determined that hardware abnormalities occur in the at least some of the fans.

7. The method according to claim 2, characterized in that The components to be cooled include at least one of the following: CPU, memory, hard disk, and network card.

8. The method according to claim 1, characterized in that The method further comprises: When the software running strategy corresponding to the target component is abnormal, an alarm message is sent to prompt that the software running strategy of the target component is abnormal.

9. The method according to claim 1, characterized in that: The method further comprises: When the hardware implementation function detection of the target component fails, an alarm message for prompting the hardware abnormality of the target component is sent.

10. A computing device, characterized in that include: at least one memory for storing a program; At least one processor is used to execute the program stored in the memory, and when the program stored in the memory is executed, the processor is used to execute the method according to any one of claims 1 to 9.

Citation Information

Cited By

  • Component verification method and device, storage medium and program product

    CN120743364A