CN116450391A - Fault positioning method, device, equipment and medium - Google Patents

Abstract

The application discloses a fault positioning method, device, equipment and medium, and relates to the technical field of servers. When the firmware update of the baseboard management controller chip fails, establishing communication connection with the baseboard management controller chip; judging whether the updated firmware file meets the preset requirement or not; if yes, confirming that the chip of the baseboard management controller is faulty; if not, confirming that the firmware is updated and failed. Therefore, when the firmware update fails, the reasons of the firmware update failure are accurately judged according to the meeting relation of the firmware file to the preset requirements, the problem that the baseboard management controller chip is positioned rapidly when the baseboard management controller service cannot be started is solved, the failure positioning efficiency is improved, the time cost is saved, and the quick repair of the failure by a tester is facilitated.

Description

A fault location method, device, equipment and medium

technical field

The present application relates to the technical field of servers, in particular to a fault location method, device, equipment and medium.

Background technique

Baseboard Management Controller (BMC) is a small operating system independent of the server system. It can be in the form of a chip integrated on the motherboard, or can be extended through the high-speed serial computer bus standard (Peripheral Component Interconnect Express, PCIE) and other forms are inserted on the motherboard, and the external form is only a standard RJ45 network port, with an independent Internet Protocol (Internet Protocol, IP) firmware system. Server clusters generally use BMC instructions for large-scale unattended operations, including remote management, monitoring, installation, and restart of servers.

The BMC chip has a small shape and fine composition, and a small operating system runs inside. When the BMC firmware is updated, abnormalities such as BMC chip damage or incomplete firmware may occur, causing the BMC system to fail to work normally. However, when the BMC system cannot work normally and the server cannot be turned on, the user cannot determine the cause of the BMC chip failure, and it is impossible to eliminate the BMC chip failure, which greatly affects the efficiency of fault location.

In view of the above problems, how to quickly locate the fault of the BMC chip is an urgent problem to be solved by those skilled in the art.

Contents of the invention

The purpose of this application is to provide a fault location method, device, equipment and medium, so as to realize rapid location of BMC chip faults.

In order to solve the above technical problems, this application provides a fault location method, including:

When the firmware update of the baseboard management controller chip fails, establish a communication connection with the baseboard management controller chip;

Determine whether the updated firmware file meets the preset requirements;

If yes, confirm that the baseboard management controller chip is faulty;

If not, it is confirmed that the firmware update has failed.

Preferably, said judging whether the updated firmware file meets preset requirements includes:

Obtain the firmware file updated in the baseboard management controller chip, and obtain a locally stored backup firmware file;

Judging whether the file size of the firmware file is the same as the file size of the backup firmware file;

If yes, confirm that the baseboard management controller chip is faulty;

If not, it is confirmed that the firmware file is incomplete, and it is confirmed that the firmware update is faulty.

Preferably, said judging whether the updated firmware file meets preset requirements includes:

Obtain the digital signature of the firmware file updated in the baseboard management controller chip, and obtain the digital signature of the locally stored backup firmware file;

Judging whether the digital signature of the firmware file is identical to the digital signature of the backup firmware file;

If yes, confirm that the baseboard management controller chip is faulty;

If not, it is confirmed that the firmware file has been modified, and it is confirmed that the firmware update is faulty.

Preferably, after the confirmation is that the firmware update is faulty, it also includes:

performing firmware update on the baseboard management controller chip according to the backup firmware file.

Preferably, after updating the firmware of the baseboard management controller chip according to the backup firmware file, the method further includes:

disconnecting the communication connection with the baseboard management controller chip.

Preferably, after the confirmation is that the firmware update is faulty, it also includes:

Generate a log containing firmware update failure information.

Preferably, after the confirmation that the baseboard management controller chip is faulty, the method further includes:

Outputting a prompt message indicating that the baseboard management controller chip is faulty;

A log containing failure information of the baseboard management controller chip is generated.

In order to solve the above technical problems, the present application also provides a fault location device, including:

A communication module, configured to establish a communication connection with the baseboard management controller chip when the firmware update of the baseboard management controller chip fails;

A judging module, configured to judge whether the updated firmware file meets the preset requirements; if so, trigger the first confirmation module, and if not, trigger the second confirmation module;

The first confirmation module is configured to confirm that the baseboard management controller chip is faulty;

The second confirming module is configured to confirm that it is a firmware update failure.

Preferably, the judging module includes:

A file obtaining module, configured to obtain the updated firmware file in the baseboard management controller chip, and obtain a locally stored backup firmware file;

The file size judging module is used to judge whether the file size of the firmware file is the same as the file size of the backup firmware file; if yes, then confirm that the baseboard management controller chip is faulty; if not, then confirm that the firmware file Incomplete and confirmed as firmware update failure.

Preferably, the judging module includes:

A digital signature obtaining module, configured to obtain the digital signature of the firmware file updated in the baseboard management controller chip, and obtain the digital signature of the locally stored backup firmware file;

The digital signature judging module is used to judge whether the digital signature of the firmware file is the same as the digital signature of the backup firmware file; if yes, then confirm that the baseboard management controller chip is faulty; if not, then confirm the firmware file has been modified and confirmed to be a firmware update failure.

Preferably, it also includes:

A firmware update module, configured to update the firmware of the baseboard management controller chip according to the backup firmware file after the firmware update failure is confirmed.

Preferably, it also includes:

The communication disconnection module is configured to disconnect the communication connection with the baseboard management controller chip after the firmware update is performed on the baseboard management controller chip according to the backup firmware file.

Preferably, it also includes:

The first log generation module is configured to generate a log containing firmware update failure information after the firmware update failure is confirmed.

Preferably, it also includes:

A prompt information output module, configured to output prompt information of the baseboard management controller chip failure after the confirmation is that the baseboard management controller chip is faulty;

The second log generation module is configured to generate a log containing the fault information of the baseboard management controller chip.

In order to solve the above technical problems, the present application also provides a fault location device, including:

memory for storing computer programs;

A processor, configured to implement the steps of the above fault location method when executing the computer program.

In order to solve the above technical problems, the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned fault location method are realized.

The fault location method provided in this application is to establish a communication connection with the baseboard management controller chip when the firmware update of the baseboard management controller chip fails; to determine whether the updated firmware file meets the preset requirements; The management controller chip is faulty; if not, it is confirmed that the firmware update is faulty. It can be seen that, when the firmware update fails, the above solution accurately determines the cause of the firmware update failure through the satisfaction relationship between the firmware file and the preset requirements, and solves the problem of quickly locating the baseboard management controller chip when the baseboard management controller service cannot be started. It improves the efficiency of fault location, saves time and cost, and helps testers to repair the fault as soon as possible.

In addition, the embodiment of the present application also provides a fault location device, equipment, and medium, and the effect is the same as above.

Description of drawings

In order to illustrate the embodiments of the present application more clearly, the following will briefly introduce the accompanying drawings used in the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. As far as people are concerned, other drawings can also be obtained based on these drawings on the premise of not paying creative work.

FIG. 1 is a flowchart of a fault location method provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of a fault location device provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of a fault location device provided in an embodiment of the present application;

FIG. 4 is a flow chart of the fault location method provided in the embodiment of the present application in an application scenario.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of this application.

The core of the present application is to provide a fault location method, device, equipment and medium, so as to realize rapid location of BMC chip faults.

In order to enable those skilled in the art to better understand the solution of the present application, the present application will be further described in detail below in conjunction with the drawings and specific implementation methods.

Firmware is generally stored in an Electrically Erasable Programmable ROM (EEPROM) or FLASH chip in a device, and is generally a program that can be upgraded by a user through a specific refresh program. Generally speaking, the software that is responsible for the most basic and bottom-level work of a digital product can be called firmware, such as the basic input/output system BIOS (Basic Input/Output System) on the computer motherboard.

Usually, the programs stored in the hardware cannot be directly read or modified by the user. In the past, it was generally not necessary to upgrade the firmware. Even if serious loopholes were found in the firmware, professionals had to bring the programmed chips to replace the chips on the original machine. Early firmware chips generally adopt ROM design, and its firmware code is solidified during the production process and cannot be modified by any means. With the continuous development of technology, it has become an urgent requirement for users to modify the firmware to adapt to the constantly updated hardware environment. Therefore, rewritable programmable erasable read-only memory EPROM (Erasable Programmable ROM), EEPROM and flash appear up. These chips can be flashed repeatedly, allowing the firmware to be modified and upgraded.

Similarly, as a small operating system independent of the server system, the baseboard management controller chip also needs to be updated and upgraded with firmware, so as to meet its remote management, monitoring, installation, restart and other operations on the server. However, when the firmware is updated, if the baseboard management controller is damaged or the firmware is incomplete and other abnormal conditions occur, the baseboard management controller cannot work normally; and when the baseboard management controller cannot work and the server cannot be powered on , the user cannot determine what causes the firmware update failure, and cannot rule out whether it is the hardware of the baseboard management controller chip itself or the firmware. Therefore, the embodiment of the present application provides a fault location method to solve the above problems. It can be understood that, the specific application scenario of the fault location method provided in the embodiment of the present application may be a computer, a server, or a storage medium with a processing function. In this embodiment, there is no limitation on the application scenarios of the fault location method, and it depends on specific implementation conditions.

FIG. 1 is a flowchart of a fault location method provided by an embodiment of the present application. As shown in Figure 1, the methods include:

S10: When the firmware update of the baseboard management controller chip fails, establish a communication connection with the baseboard management controller chip.

Specifically, when the baseboard management controller chip performs firmware update, the firmware update process of the baseboard management controller chip is monitored. When the firmware update of the baseboard management controller chip fails, a communication connection with the baseboard management controller chip is established. It should be noted that in the embodiment of the present application, there is no limitation on the specific manner of the communication connection with the baseboard management controller chip, and the communication connection can be performed through a serial port or wireless communication, depending on the specific implementation situation.

S11: Determine whether the updated firmware file meets the preset requirements; if yes, go to step S12; if not, go to step S13.

S12: Confirm that the baseboard management controller chip is faulty.

S13: It is confirmed that the firmware update is faulty.

Further, it is judged whether the updated firmware file of the baseboard management controller chip meets the preset requirements. It should be noted that there is no limitation on the preset requirements in this embodiment. It may be specifically that the size of the firmware file needs to meet a preset condition. It may be that the firmware file needs to match the baseboard management controller chip. It may also be that the The file is not modified during the process of updating the baseboard management controller chip, depending on the specific implementation.

When it is confirmed that the updated firmware file meets the preset requirements, it is considered that the firmware update of the baseboard management controller chip is normal this time, and it is judged to be a hardware failure of the baseboard management controller chip; and when it is confirmed that the updated firmware file does not meet the preset requirements , it is considered that the firmware update of the baseboard management controller chip is abnormal, and it is determined that the firmware update of the baseboard management controller chip is faulty.

In this embodiment, when the firmware update of the baseboard management controller chip fails, establish a communication connection with the baseboard management controller chip; determine whether the updated firmware file meets the preset requirements; if so, confirm that it is the baseboard management controller chip failure; if not, it is confirmed as a firmware update failure. It can be seen that, when the firmware update fails, the above solution accurately determines the cause of the firmware update failure through the satisfaction relationship between the firmware file and the preset requirements, and solves the problem of quickly locating the baseboard management controller chip when the baseboard management controller service cannot be started. It improves the efficiency of fault location, saves time and cost, and helps testers to repair the fault as soon as possible.

On the basis of the above embodiments, as a preferred embodiment, judging whether the updated firmware file meets the preset requirements includes:

Obtain the updated firmware file in the baseboard management controller chip, and obtain the backup firmware file stored locally;

Determine whether the file size of the firmware file is the same as the file size of the backup firmware file;

If yes, it is confirmed that the baseboard management controller chip is faulty;

If not, confirm that the firmware file is incomplete, and confirm that it is a firmware update failure.

In the foregoing embodiments, there is no limitation on the preset conditions, and it depends on specific implementation conditions. As a preferred embodiment, in this embodiment, in order to determine whether the updated firmware file meets the preset requirements, it is first necessary to obtain the updated firmware file in the baseboard management controller chip, and obtain the locally stored backup firmware file .

It can be understood that, in order to obtain the satisfying relationship of the firmware file to the preset requirement, it is first necessary to obtain the updated firmware file. In the specific implementation, since a communication connection has been established with the BMC chip when it is confirmed that the firmware update failure occurs on the BMC chip, the update information of this update can be directly obtained from the BMC chip through the communication connection. firmware file. At the same time, obtain the backup firmware file stored locally. It can be understood that theoretically, the updated firmware file of the baseboard management controller chip should be the same as the backup firmware file.

It is further judged whether the file size of the firmware file is the same as that of the backup firmware file, that is, comparing the sizes of the two. If the comparison results are inconsistent and the two sizes are different, it is considered that the updated firmware file is incomplete and it can be confirmed as a firmware update failure; if the comparison results are consistent and the two sizes are the same, the updated firmware file is considered complete and can be confirmed as a substrate Management controller chip failure.

In this embodiment, by obtaining the updated firmware file in the baseboard management controller chip and obtaining the locally stored backup firmware file; judging whether the file size of the firmware file is the same as the file size of the backup firmware file; if so, confirming that it is a baseboard management The controller chip is faulty; if not, it is confirmed that the firmware file is incomplete, and it is confirmed that the firmware update is faulty. The judgment of whether the updated firmware file meets the preset requirements is realized, and the fault location is accurately carried out.

On the basis of the above embodiments, as a preferred embodiment, judging whether the updated firmware file meets the preset requirements includes:

obtaining a digital signature of an updated firmware file in the baseboard management controller chip, and obtaining a digital signature of a locally stored backup firmware file;

Determine whether the digital signature of the firmware file is the same as the digital signature of the backup firmware file;

If yes, it is confirmed that the baseboard management controller chip is faulty;

If not, confirm that the firmware file has been modified, and confirm that it is a firmware update failure.

A manner of judging whether the updated firmware file meets the preset requirements is given in the above embodiment. As a preferred embodiment, in a specific implementation, judging whether the updated firmware file meets the preset requirements can also be realized by comparing the digital signature of the firmware file with the locally stored backup firmware file.

Specifically, first obtain the digital signature of the updated firmware file in the BMC chip, and obtain the digital signature of the locally stored backup firmware file. A digital signature (also known as a public key digital signature) is a digital string that can only be generated by the sender of the message and cannot be forged by others. This digital string is also an effective proof of the authenticity of the message sent by the sender of the message. It is a method for authenticating digital information similar to an ordinary physical signature written on paper, but implemented using techniques in the field of public key cryptography. A set of digital signatures usually defines two complementary operations, one for signing and the other for verification. Digital signature is the application of asymmetric key encryption technology and digital abstract technology.

Digital signature algorithm relies on public key encryption technology to achieve. In public-key cryptography, each user has a pair of keys: a public key and a private key. The public key can be freely distributed, but the private key is kept secret. Common digital signature algorithms include password generation algorithms, marking algorithms, and verification algorithms. There are also digital signatures and verifications of the hash algorithm. The hash function is a "compression function". Using the hash function, the input of any length can be transformed into a fixed-length output through the hash function algorithm. The hash of the output The value is the message digest, also known as the numeric digest. In a formal digital signature, the sender first applies a hash algorithm to the sent file to obtain a fixed-length message digest (Message Digest); then signs the message digest with its own private key (Secret key, SK) to form a sent Party's digital signature. The digital signature will be sent to the recipient together with the original text as a queue; the recipient first decrypts the digital signature with the sender's public key to obtain the sender's digital digest, and then uses the same hash function to hash the original text to obtain A new message digest, and finally compare the message digest with the received message digest. In the digital signature and verification based on the asymmetric key encryption system, the sender first encrypts the original text with its own private key to obtain a digital signature, and then sends the original text and digital signature to the receiver. The receiver uses the sender's public key to decrypt the digital signature, and finally compares it with the original text. It can be seen that digital signature is an electronic signature method widely used in e-commerce and e-government affairs, with mature technology and strong operability. It adopts standardized procedures and scientific methods to identify the identity of the signer and to approve the content of an electronic data. The use of digital signature technology can verify whether the original text of the document has changed during the transmission process, ensuring the integrity, authenticity and non-repudiation of the transmitted electronic document.

However, in a specific embodiment, if the firmware file has not been modified, theoretically the digital signature of the firmware file should be the same as the digital signature of the backup firmware file. Therefore, by comparing the digital signature of the firmware file with the digital signature of the backup firmware file, if the two are the same, it is considered that the firmware file has not been modified, and it can be confirmed that the baseboard management controller chip is faulty; if the two are different, the firmware file is considered Has been modified and can be confirmed as a firmware update failure.

It should be noted that, in the specific implementation, the fault location is performed by comparing the digital signatures of the firmware file and the backup firmware file, and the fault location is performed by comparing the size of the firmware file and the backup firmware file in the above embodiment, One of these two locating methods can be selected for implementation, or they can be implemented at the same time, so as to achieve a better fault locating effect, which is not limited in this embodiment and depends on specific implementation conditions.

In this embodiment, by obtaining the digital signature of the updated firmware file in the baseboard management controller chip, and obtaining the digital signature of the locally stored backup firmware file; judging whether the digital signature of the firmware file is the same as the digital signature of the backup firmware file; if so , it is confirmed that the baseboard management controller chip is faulty; if not, it is confirmed that the firmware file has been modified, and it is confirmed that the firmware update is faulty. The judgment of whether the updated firmware file meets the preset requirements is realized, and the fault location is accurately carried out.

In order to complete the firmware update of the baseboard management controller chip, on the basis of the above-mentioned embodiments, as a preferred embodiment, after confirming that the firmware update fails, it also includes:

Update the firmware of the baseboard management controller chip according to the backup firmware file.

In the specific implementation, when it is confirmed that the firmware update of the baseboard management controller chip has a firmware update failure, in order to ensure the normal firmware update of the baseboard management controller chip and further ensure the normal operation of the baseboard management controller chip and the server, as a preferred In this embodiment, after confirming that a firmware update failure occurs on the baseboard management controller chip, the firmware update is performed on the baseboard management controller chip according to the backup firmware file, that is, the backup firmware is updated using the correct backup firmware file stored locally. File re-updates the firmware to ensure the normal operation of the baseboard management controller chip.

In this embodiment, after the firmware update failure is confirmed, the firmware update is performed on the baseboard management controller chip according to the backup firmware file. The normal operation of the baseboard management controller chip and the server is guaranteed.

On the basis of the above embodiments, as a preferred embodiment, after updating the firmware of the baseboard management controller chip according to the backup firmware file, it further includes:

Disconnect the communication link with the baseboard management controller chip.

Specifically, after the firmware update of the baseboard management controller chip is performed according to the backup firmware file, the baseboard management controller chip runs normally, and it is no longer necessary to monitor the baseboard management controller chip at this time. At this time, the communication connection with the baseboard management controller chip is disconnected, further saving the power consumption of the system, and the communication connection is waiting for the next firmware update.

On the basis of the above embodiments, as a preferred embodiment, after confirming that the firmware update fails, it also includes:

Generate a log containing firmware update failure information.

In a specific implementation, in order to better record relevant information of a firmware update failure, as a preferred embodiment, in this embodiment, after a firmware update failure is confirmed, a log containing firmware update failure information is generated. Take the content recorded in the above-mentioned embodiments as an example: when checking the integrity of the firmware file, compare the size of the firmware file with the backup firmware file, if the comparison results are inconsistent, it is considered that the updated firmware file is incomplete, and the This result is recorded in the log. When checking whether the firmware file has been modified, compare the digital signature of the firmware file with the backup firmware file, if the signatures are inconsistent, confirm that the firmware file has been modified, and record the result in the log.

It should be noted that generating a log containing firmware update failure information, on the one hand, can record the firmware update failure, so that subsequent staff can audit the failure process; on the other hand, due to the existence of the log, the staff can directly pass the log The content of the firmware to determine the specific cause of the firmware update failure, thereby greatly reducing the troubleshooting time and improving troubleshooting efficiency.

On the basis of the above embodiments, as a preferred embodiment, after confirming that the baseboard management controller chip is faulty, it further includes:

Output the prompt information of the baseboard management controller chip failure;

Generates a log containing information about baseboard management controller chip failures.

In a specific implementation, when it is confirmed that the baseboard management controller chip is faulty, in order to remind the staff to replace the faulty baseboard management controller chip, a prompt message of the faulty baseboard management controller chip is output. It can be understood that in this embodiment, the output mode of the prompt information can be voice broadcast, indicator light alarm or pop-up window prompt. In this embodiment, there is no limit to the output mode of the prompt information, which depends on the specific implementation situation. .

Further, a log containing the fault information of the baseboard management controller chip is generated, so that the staff can evaluate and view the fault condition of the baseboard management controller chip, and at the same time, it can be directly determined that a fault of the baseboard management controller chip has occurred through the content of the log, Therefore, the baseboard management controller chip is replaced, which saves time and cost, and improves the efficiency of troubleshooting.

In the above embodiments, the fault location method is described in detail, and the present application also provides corresponding embodiments of the fault location device.

Fig. 2 is a schematic diagram of a fault location device provided by an embodiment of the present application. As shown in Figure 2, the fault location device includes:

The communication module 10 is configured to establish a communication connection with the baseboard management controller chip when the firmware update of the baseboard management controller chip fails.

The judging module 11 is used for judging whether the updated firmware file meets the preset requirements; if so, trigger the first confirmation module 12 , and if not, trigger the second confirmation module 13 .

The first confirming module 12 is configured to confirm that the baseboard management controller chip is faulty.

The second confirming module 13 is configured to confirm that it is a firmware update failure.

As a preferred embodiment, the judging module includes:

The file obtaining module is used to obtain the firmware file updated in the baseboard management controller chip, and obtain the backup firmware file stored locally;

The file size judging module is used to judge whether the file size of the firmware file is the same as the file size of the backup firmware file; if yes, it is confirmed that the baseboard management controller chip is faulty; if not, it is confirmed that the firmware file is incomplete, and it is confirmed that it is a firmware update Fault.

Specifically, in this embodiment, in order to judge whether the updated firmware file meets the preset requirements, firstly, the updated firmware file in the BMC chip is obtained through the file obtaining module, and the locally stored backup firmware file is obtained.

It can be understood that, in order to obtain the satisfying relationship of the firmware file to the preset requirement, it is first necessary to obtain the updated firmware file. In the specific implementation, since a communication connection has been established with the BMC chip when it is confirmed that the firmware update failure occurs on the BMC chip, the update information of this update can be directly obtained from the BMC chip through the communication connection. firmware file. At the same time, obtain the backup firmware file stored locally. It can be understood that theoretically, the updated firmware file of the baseboard management controller chip should be the same as the backup firmware file.

Further, the file size judging module judges whether the file size of the firmware file is the same as that of the backup firmware file, that is, compares the size of the two. If the comparison results are inconsistent and the two sizes are different, it is considered that the updated firmware file is incomplete and it can be confirmed as a firmware update failure; if the comparison results are consistent and the two sizes are the same, the updated firmware file is considered complete and can be confirmed as a substrate Management controller chip failure.

As a preferred embodiment, the judging module includes:

The digital signature obtaining module is used to obtain the digital signature of the updated firmware file in the baseboard management controller chip, and obtain the digital signature of the locally stored backup firmware file;

The digital signature judging module is used to judge whether the digital signature of the firmware file is the same as the digital signature of the backup firmware file; if yes, it is confirmed that the baseboard management controller chip is faulty; Update failure.

In the above embodiment, the file acquisition module and the file size judgment module can be used to realize judging whether the updated firmware file meets the preset requirements. As a preferred embodiment, in specific implementation, judging whether the updated firmware file meets the preset requirements can also be realized by a digital signature acquisition module and a digital signature judging module.

Specifically, firstly, the digital signature of the updated firmware file in the baseboard management controller chip is obtained through the digital signature obtaining module, and the digital signature of the locally stored backup firmware file is obtained. A digital signature (also known as a public key digital signature) is a digital string that can only be generated by the sender of the message and cannot be forged by others. This digital string is also an effective proof of the authenticity of the message sent by the sender of the message. It is a method for authenticating digital information similar to an ordinary physical signature written on paper, but implemented using techniques in the field of public key cryptography. A set of digital signatures usually defines two complementary operations, one for signing and the other for verification. Digital signature is the application of asymmetric key encryption technology and digital abstract technology.

However, in a specific embodiment, if the firmware file has not been modified, theoretically the digital signature of the firmware file should be the same as the digital signature of the backup firmware file. Therefore, the digital signature of the firmware file is compared with the digital signature of the backup firmware file through the digital signature judgment module. If the two are the same, it is considered that the firmware file has not been modified, and it can be confirmed that the baseboard management controller chip is faulty; if the two are different, If it is considered that the firmware file has been modified, it can be confirmed as a firmware update failure.

It should be noted that, in this embodiment, the fault location is performed by the digital signature acquisition module and the digital signature judgment module, and in the above embodiment, the fault location is performed by the file acquisition module and the file size judgment module. One of the locating methods can be selected, or implemented at the same time, so as to achieve a better fault locating effect, which is not limited in this embodiment and depends on specific implementation conditions.

In this embodiment, the digital signature of the updated firmware file in the baseboard management controller chip is obtained by the digital signature acquisition module, and the digital signature of the locally stored backup firmware file is obtained; the digital signature of the firmware file is judged by the digital signature judgment module. Whether the digital signatures of the firmware files are the same; if yes, it is confirmed that the baseboard management controller chip is faulty; if not, it is confirmed that the firmware file has been modified, and it is confirmed that it is a firmware update fault. The judgment of whether the updated firmware file meets the preset requirements is realized, and the fault location is accurately carried out.

As a preferred embodiment, it also includes:

The firmware update module is configured to update the firmware of the baseboard management controller chip according to the backup firmware file after the firmware update failure is confirmed.

In the specific implementation, when it is confirmed that the firmware update of the baseboard management controller chip has a firmware update failure, in order to ensure the normal firmware update of the baseboard management controller chip and further ensure the normal operation of the baseboard management controller chip and the server, as a preferred In this embodiment, in this embodiment, after confirming that a firmware update failure occurs on the baseboard management controller chip, the firmware update module is used to update the firmware of the baseboard management controller chip according to the backup firmware file, that is, to use the correct backup firmware stored locally The backup firmware file is re-updated by the backup firmware file, so as to ensure the normal operation of the baseboard management controller chip.

As a preferred embodiment, it also includes:

The communication connection disconnection module is used for disconnecting the communication connection with the baseboard management controller chip after performing firmware update on the baseboard management controller chip according to the backup firmware file.

As a preferred embodiment, it also includes:

The first log generation module is configured to generate a log containing firmware update failure information after the firmware update failure is confirmed.

In the specific implementation, in order to better record the relevant information of the firmware update failure, as a preferred embodiment, in this embodiment, the first log generation module can be used to generate a log containing the firmware update after the firmware update failure is confirmed. Log of failure information. Take the content recorded in the above-mentioned embodiments as an example: when checking the integrity of the firmware file, compare the size of the firmware file with the backup firmware file, if the comparison results are inconsistent, it is considered that the updated firmware file is incomplete, use The first log generating module records the result in a log. When checking whether the firmware file has been modified, compare the digital signature of the firmware file with the backup firmware file, if the signature is inconsistent, then confirm that the firmware file has been modified, and record this result in the log by the first log generation module.

It should be noted that, using the first log generating module to generate a log containing firmware update fault information, on the one hand, the firmware update fault can be recorded, so that subsequent staff can audit the fault process; on the other hand, due to the existence of the log, making The staff can directly determine the specific cause of the firmware update failure through the content of the log, thereby greatly reducing the troubleshooting time and improving the troubleshooting efficiency.

As a preferred embodiment, it also includes:

The prompt information output module is used to output the prompt information of the baseboard management controller chip failure after it is confirmed that the baseboard management controller chip is faulty;

The second log generation module is configured to generate a log containing fault information of the baseboard management controller chip.

In this embodiment, the fault location device includes a communication module, a judgment module, a first confirmation module and a second confirmation module. The fault location device can implement all the steps of the fault location method in the above-mentioned embodiments during operation. When the firmware update of the baseboard management controller chip fails, establish a communication connection with the baseboard management controller chip; determine whether the updated firmware file meets the preset requirements; if so, confirm that the baseboard management controller chip is faulty; if not, Then it is confirmed as a firmware update failure. It can be seen that, when the firmware update fails, the above solution accurately determines the cause of the firmware update failure through the satisfaction relationship between the firmware file and the preset requirements, and solves the problem of quickly locating the baseboard management controller chip when the baseboard management controller service cannot be started. It improves the efficiency of fault location, saves time and cost, and helps testers to repair the fault as soon as possible.

Fig. 3 is a schematic diagram of a fault location device provided by an embodiment of the present application. As shown in Figure 3, fault location equipment includes:

The memory 20 is used for storing computer programs.

The processor 21 is configured to implement the steps of the fault location method mentioned in the above embodiments when executing the computer program.

The fault location device provided in this embodiment may include, but not limited to, a smart phone, a tablet computer, a notebook computer or a desktop computer, and the like.

Wherein, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. Processor 21 can adopt at least one hardware form in Digital Signal Processor (Digital Signal Processor, DSP), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), Programmable Logic Array (Programmable LogicArray, PLA) accomplish. The processor 21 may also include a main processor and a coprocessor, the main processor is a processor for processing data in the wake-up state, and is also called a central processing unit (Central Processing Unit, CPU); Low-power processor for processing data in standby state. In some embodiments, the processor 21 may be integrated with a graphics processing unit (Graphics Processing Unit, GPU), and the GPU is used for rendering and drawing the content that needs to be displayed on the display screen. In some embodiments, the processor 21 may also include an artificial intelligence (AI) processor, and the AI processor is used to process calculation operations related to machine learning.

Memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory, and non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 20 is at least used to store the following computer program 201, wherein, after the computer program is loaded and executed by the processor 21, the relevant steps of the fault location method disclosed in any of the foregoing embodiments can be realized. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, etc., and the storage method may be temporary storage or permanent storage. Wherein, the operating system 202 may include Windows, Unix, Linux and so on. The data 203 may include but not limited to the data involved in the fault location method.

In some embodiments, the fault location device may further include a display screen 22 , an input/output interface 23 , a communication interface 24 , a power supply 25 and a communication bus 26 .

Those skilled in the art can understand that the structure shown in FIG. 3 does not constitute a limitation on the fault location device, and may include more or less components than those shown in the figure.

In this embodiment, the fault location device includes a memory and a processor. Memory is used to store computer programs. When the processor is used to execute the computer program, the steps of the method for locating the fault mentioned in the above-mentioned embodiments are realized. When the firmware update of the baseboard management controller chip fails, establish a communication connection with the baseboard management controller chip; determine whether the updated firmware file meets the preset requirements; if so, confirm that the baseboard management controller chip is faulty; if not, Then it is confirmed as a firmware update failure. It can be seen that, when the firmware update fails, the above solution accurately determines the cause of the firmware update failure through the satisfaction relationship between the firmware file and the preset requirements, and solves the problem of quickly locating the baseboard management controller chip when the baseboard management controller service cannot be started. It improves the efficiency of fault location, saves time and cost, and helps testers to repair the fault as soon as possible.

Finally, the present application also provides an embodiment corresponding to a computer-readable storage medium. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the steps described in the above method embodiments are implemented.

It can be understood that if the methods in the above embodiments are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , executing all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

In this embodiment, a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps described in the foregoing method embodiments are implemented. When the firmware update of the baseboard management controller chip fails, establish a communication connection with the baseboard management controller chip; determine whether the updated firmware file meets the preset requirements; if so, confirm that the baseboard management controller chip is faulty; if not, Then it is confirmed as a firmware update failure. It can be seen that, when the firmware update fails, the above solution accurately determines the cause of the firmware update failure through the satisfaction relationship between the firmware file and the preset requirements, and solves the problem of quickly locating the baseboard management controller chip when the baseboard management controller service cannot be started. It improves the efficiency of fault location, saves time and cost, and helps testers to repair the fault as soon as possible.

In order to enable those skilled in the art to better understand the technical solution of the present application, the above-mentioned present application will be further described in detail below in conjunction with FIG. 4 . FIG. 4 is a flow chart of the fault location method provided in the embodiment of the present application in an application scenario. As shown in Figure 4, the method includes:

S20: Monitor firmware update of the baseboard management controller.

S21: Establish a communication connection with the baseboard management controller chip when the update of the baseboard management controller firmware fails.

S22: Check the integrity of the firmware file and generate a log.

S23: Check whether the firmware file has been modified, and generate a log.

S24: When it is confirmed that the firmware file is complete and has not been modified, it is determined that the BMC chip hardware is faulty, and a log is generated.

Specifically, the application scenario of the method of the present application may be a computer, a storage device, or a removable computer-readable storage medium, which may be directly inserted into a server mainboard, and capable of storage and data processing functions. The storage part mainly includes the backup firmware of the baseboard management controller and the fault information record log of the firmware update, and the processing part realizes the firmware recovery function of the baseboard management controller when the computer program is executed by the processor.

In a specific implementation, the update of the firmware of the baseboard management controller is monitored when the baseboard management controller performs firmware update. When the firmware update of the baseboard management controller fails, a communication connection with the baseboard management controller chip is established. It can be understood that the communication connection may be a wired communication connection or a wireless communication connection. After the communication connection is established, check and deal with the following items:

First, check the integrity of the firmware file, specifically obtain the updated firmware file of the baseboard management controller chip, and perform a size comparison with the backup firmware file in the local storage medium; if the comparison results are inconsistent, it is the updated firmware The file is incomplete, the result is recorded in the local log file. Then execute the written baseboard management controller chip update instruction, and use the local backup firmware file to update and start the baseboard management controller chip. After the failure of the firmware of the baseboard management controller chip is recovered, the communication connection with the baseboard management controller chip is disconnected.

Further, check whether the firmware file has been modified, specifically obtain the digital signature of the updated firmware file of the baseboard management controller chip, and compare it with the digital signature of the locally stored backup firmware file; if the signatures are inconsistent, the firmware file has been modified. is modified, the result is recorded in the local log file. Then execute the written baseboard management controller chip update instruction, and use the local backup firmware file to update and start the baseboard management controller chip. After the failure of the firmware of the baseboard management controller chip is recovered, the communication connection with the baseboard management controller chip is disconnected.

The above can realize the judgment of the firmware update failure, and if the checked firmware file is complete and has not been modified, it is judged to be a hardware failure of the baseboard management controller chip, and the result is recorded in the local log file. In this way, the user can determine the cause of the update failure of the baseboard management controller chip directly through the detection result or by viewing the recorded log file. This can greatly reduce the troubleshooting time and improve efficiency.

A fault location method, device, equipment, and medium provided by the present application have been introduced in detail above. Each embodiment in the description is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for relevant details, please refer to the description of the method part. It should be pointed out that those skilled in the art can make some improvements and modifications to the application without departing from the principles of the application, and these improvements and modifications also fall within the protection scope of the claims of the application.

It should also be noted that in this specification, relative terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations There is no such actual relationship or order between the operations. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Claims (10)

1. A fault locating method, comprising:

when the firmware update of the baseboard management controller chip fails, establishing communication connection with the baseboard management controller chip;

judging whether the updated firmware file meets the preset requirement or not;

If yes, confirming that the baseboard management controller chip is faulty;

if not, confirming that the firmware is updated and failed.

2. The fault location method according to claim 1, wherein the determining whether the updated firmware file meets the preset requirement comprises:

acquiring the updated firmware file in the baseboard management controller chip, and acquiring a locally stored backup firmware file;

judging whether the file size of the firmware file is the same as the file size of the backup firmware file;

if yes, confirming that the baseboard management controller chip is faulty;

if not, confirming that the firmware file is incomplete, and confirming that the firmware file is a firmware update fault.

3. The fault location method according to claim 1, wherein the determining whether the updated firmware file meets the preset requirement comprises:

acquiring a digital signature of the firmware file updated in the baseboard management controller chip, and acquiring a digital signature of a locally stored backup firmware file;

judging whether the digital signature of the firmware file is the same as the digital signature of the backup firmware file;

if yes, confirming that the baseboard management controller chip is faulty;

If not, confirming that the firmware file is modified and confirming that the firmware update fails.

4. A fault locating method according to claim 2 or 3, further comprising, after said confirming that the firmware update has failed:

and updating the firmware of the baseboard management controller chip according to the backup firmware file.

5. The fault location method of claim 4, further comprising, after the firmware update of the baseboard management controller chip according to the backup firmware file:

and disconnecting the communication connection with the baseboard management controller chip.

6. The fault location method of claim 4, further comprising, after the validating as a firmware update fault:

a log containing firmware update failure information is generated.

7. The fault location method of claim 1, further comprising, after the identifying that the baseboard management controller chip is faulty:

outputting prompt information of the fault of the baseboard management controller chip;

and generating a log containing fault information of the baseboard management controller chip.

8. A fault locating device, comprising:

The communication module is used for establishing communication connection with the baseboard management controller chip when the firmware update of the baseboard management controller chip fails;

the judging module is used for judging whether the updated firmware file meets the preset requirement; if yes, triggering a first confirmation module, and if not, triggering a second confirmation module;

the first confirming module is used for confirming that the baseboard management controller chip is failed;

and the second confirming module is used for confirming that the firmware update is faulty.

9. A fault locating device, comprising:

a memory for storing a computer program;

a processor for implementing the steps of the fault localization method as claimed in any one of claims 1 to 7 when executing the computer program.

10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the fault localization method according to any of claims 1 to 7.