TWI715005B - Monitor method for demand of a bmc - Google Patents

Abstract

A monitor method for demand of a BMC is implemented by a computer device including a processing module and a BMC, the BMC executing a plurality of demand, the method comprising: (A1) the BMC generates a demand execution table, the demand execution table includes a plurality of demand codes corresponding to the resident demand, and a surviving value corresponding to each demand, each surviving value is updated when the corresponding demand is executed. (A2) The processing module determines, according to the demand execution table, whether there is at least one abnormal demand in the demand. (A3) When it is determined that there is at least one abnormal demand, the processing module notifies the BMC to restart the abnormal demand.

Description

Method for monitoring resident program of substrate management controller

The present invention relates to a system detection method, in particular to a method that can automatically distinguish whether the current resident program of the baseboard management controller is normally executed.

At present, the baseboard management controller (BMC, Baseboard management controller) in the computer device may occasionally encounter the situation that important resident programs (demand) cannot operate normally during the startup stage. At this time, although the operating light of the baseboard management controller is Normal, but in fact it has been unable to provide a complete service, making the BMC monitoring function unable to operate reliably. Therefore, after the computer device is completely booted, when the administrator sends a signal through the computer device and finds that the resident program is no longer operating normally, the baseboard management controller can only be restarted to restore the resident program of the baseboard management controller to normal operation.

In view of this, how to provide a method that can effectively monitor whether the resident program executed by the baseboard management controller is operating normally during the booting phase of the computer device and solve the problem of the resident program that cannot operate normally is the primary problem that this author intends to solve.

Therefore, the object of the present invention is to provide a method that can effectively monitor whether the resident program executed by the baseboard management controller is operating normally during the booting phase of the computer device and solve the problem of the resident program not operating normally.

Therefore, the method of the present invention for monitoring the resident program of a substrate management controller is implemented by a computer device, the computer device includes a processing module and a substrate management controller electrically connected to the processing module, the substrate management The controller is used to execute multiple resident programs, and the method for monitoring the resident programs of the baseboard management controller includes one step (A1), one step (A2), and one step (A3).

The step (A1) is to generate a resident program execution table by the baseboard management controller. The resident program execution table includes a plurality of program codes corresponding to the resident programs and a survival value corresponding to each resident program. Each survival value will be updated when the corresponding resident program is normally executed by the baseboard management controller.

This step (A2) uses the processing module to read the survival values corresponding to the resident programs in the resident program execution table, and based on the survival values corresponding to the resident programs read last time and The survival value corresponding to the resident programs currently read determines whether there is at least one resident program with abnormal operation in the resident programs, wherein each resident program with abnormal operation has the same survival value read last time For its survival value currently read.

The step (A3) is that when the processing module determines that there is at least one resident program of the abnormal operation, the processing module informs the baseboard management controller, so that the baseboard management controller restarts each abnormal operation Resident program.

The effect of the present invention is that the computer device executes each resident program in the generated resident program table and its corresponding survival value, and detects whether the status of each resident program is normally executed, and when it is detected When the at least one abnormally operating resident program cannot be executed normally, restart the at least one abnormally operating resident program, effectively achieving the at least one operating without restarting the baseboard management controller The abnormal resident program is re-executed normally, and the baseboard management controller operates normally.

1: computer device

11: baseboard management controller

12: Memory module

121: Basic Input Output Program

13: Processing module

14: Platform Path Controller

91~93: Step

21~23: Steps

31~36: Step

41~45: Steps

51~52: Steps

61~64: Step

71~73: Steps

Other features and effects of the present invention will be clearly presented in the embodiments with reference to the drawings, in which: FIG. 1 is a block diagram illustrating a method for executing the resident program of the present invention for monitoring the baseboard management controller Figure 2 is a flowchart illustrating a data reading procedure of this embodiment; Figure 3 is a flowchart illustrating a resident program restart procedure of this embodiment; Figure 4 is a flowchart illustrating A first baseboard management controller restart program of this embodiment; Fig. 5 is a flowchart illustrating a first abnormal record generation procedure of this embodiment; Fig. 6 is a flowchart illustrating a communication interface restart procedure of this embodiment; Fig. 7 is a flowchart illustrating the procedure of this embodiment A second BMC restart procedure; and FIG. 8 is a flowchart illustrating a second abnormal record generation procedure of this embodiment.

Before the present invention is described in detail, it should be noted that in the following description, similar elements are represented by the same numbers.

Referring to FIG. 1, a computer device 1 is one of the embodiments of the method for executing a resident program for monitoring a baseboard management controller of the present invention. The computer device 1 includes a baseboard management controller 11 (BMC, Baseboard management controller), a storage There is a basic input/output program 121 (BIOS, Basic Input/Output System) memory module 12, a processing module 13, and an electrical connection to the baseboard management controller 11, the memory module 12 and the processing module 13 Platform path controller 14 (PCH, Platform Controller Hub).

It is worth noting that in this embodiment, the platform path controller 14 is connected to the baseboard management controller 11 through a plurality of general-purpose input/output (GPIO) pins. Any one of these universal input and output pins can be used to restart the corresponding resident program, or to restart the Baseboard management controller 11.

Particularly, in this embodiment, one of the first universal input and output pins of the universal input and output pins is connected to the universal input and output pins of the baseboard management controller 11, and the platform The path controller 14 can transmit a first restart signal indicating that a communication interface needs to be restarted through the first universal input/output pin. One of the general-purpose input and output pins, the second general-purpose input and output pin is connected to the reset pin of the baseboard management controller 11, and the platform path controller 14 can pass through the first Two general-purpose input and output pins transmit a second restart signal indicating that the baseboard management controller 11 needs to be restarted to force the baseboard management controller 11 to restart itself, that is, with the second restart signal The baseboard management controller 11 is triggered to restart itself. In another embodiment, among the universal input and output pins, at least one third universal type other than the first universal input and output pin and the second universal input and output pin The input and output pins are also respectively connected to the general-purpose input and output pins of the baseboard management controller 11. The platform path controller 14 can transmit an indication of the demand through every third general-purpose input and output pins. The restart is related to a third restart signal corresponding to the resident program.

In this embodiment, the processing module 13 passes through the communication interface, for example, an Intelligent Platform Management Interface (IPMI) and communicates with the substrate management interface through the platform path controller 14 The management controller 11 transmits messages, instructions or data, but not limited to this. It is worth noting that the communication interface can also be, for example, a smart platform management interface and keyboard control that can be transmitted through a base circuit bus (I2C, Inter-Integrated Circuit) or a system management bus (SMBus, System Management Bus). Device specification interface (KCS, keyboard controller style), single block transfer interface (BT, block transfer), but not limited to this.

In this embodiment, the implementation aspect of the computer device 1 is, for example, a personal computer, a server, or a cloud host, but it is not limited to this.

In this embodiment, the implementation of the memory module 12 is, for example, a volatile memory, a non-volatile memory or a combination thereof, but it is not limited thereto.

In this embodiment, the implementation of the processing module 13 is, for example, a central processing unit (CPU), but it is not limited to this. The processing module 13 and the platform path controller 14 can also coexist in a system on a chip (SoC) implementation, but not limited to this.

Hereinafter, the baseboard management controller 11, the memory module 12, the processing module 13, and the platform of the computer device 1 will be described by the embodiment of the method for monitoring the resident program of the baseboard management controller of the present invention The operation details of the components of the path controller 14, wherein the relevant program for executing the method for monitoring the resident program of the baseboard management controller is integrated in the basic input and output program 121 and used by the processing module 13 when it is turned on The loaded execution, the present invention is used to monitor the resident of the baseboard management controller The program method includes a data reading program, a resident program restart program, a first BMC restart program, a first abnormal record generation program, a communication interface restart program, and a second BMC restart program, And a second abnormal record generating program.

Referring to FIG. 2, the data reading program reads data related to a resident program execution table, and includes a step 91, a step 92, and a step 93.

In step 91, when the baseboard management controller 11 in the computer device 1 is initialized, the baseboard management controller 11 generates the resident program execution table and stores the resident program execution table. Wherein, the resident program execution table includes a plurality of program codes corresponding to the resident programs, and a heartbeat corresponding to each resident program. Among them, each survival value is periodically updated by the baseboard management controller 11 when the corresponding resident program is executed normally.

In the step 92, the processing module 13 generates a read request related to the resident program execution table, and transmits it to the baseboard management controller 11 through the platform path controller 14.

In the step 93, the processing module 13 determines whether it has received the data related to the resident program execution table sent by the baseboard management controller 11. When the processing module 13 determines that it has received the data related to the resident program execution table sent by the baseboard management controller 11 in response, it performs the resident program restart procedure; when the processing module 13 determines that the resident program execution table has not been received The baseboard management controller 11 responds to the resident For the data in the program execution table, the communication interface restarts the program. The need to restart the communication interface means that the BMC 11 may not be able to correctly receive the read request related to the resident program execution table transmitted through the communication interface or the read request related to the resident program execution table or the communication interface failure. The baseboard management controller 11 cannot correctly send the data related to the resident program execution table through the communication interface. It is worth noting that the processing module 13 periodically transmits the read request related to the resident program execution table and determines whether there is a transmission period related to the baseboard management controller 11 that has been received. The data of the resident program execution table is read, and then the received data related to the resident program execution table is read.

Referring to FIG. 3, the resident program restarting procedure is to restart all resident programs that operate abnormally, and includes a step 21, a step 22, and a step 23.

In the step 21, the processing module 13 reads the data related to the resident program execution table to obtain the survival values corresponding to the resident programs, and according to the resident program values read last time Respectively corresponding to the survival value and the survival value corresponding to the currently read resident programs to determine whether there is at least one resident program with abnormal operation in the resident programs, wherein each resident program with abnormal operation was previously The survival value read is the same as the survival value currently read. When the processing module 13 determines that there is at least one resident program with an abnormal operation, step 22 is performed; when the processing module 13 determines that there is no resident program with an abnormal operation, the process ends. It is worth noting that the processing module 13 periodically reads the relevant The data in the resident program execution table is used to obtain and store the survival values corresponding to the resident programs previously read and the survival values corresponding to the resident programs currently read.

In this step 22, for each resident program of abnormal operation, the processing module 13 generates a notification message indicating the abnormal operation of the resident program and transmits it to the baseboard management controller through the platform path controller 14. 11. It is worth noting that in the step 22 of another embodiment, for each resident program of abnormal operation, the processing module 13 triggers the platform path controller 14 to generate the instruction to restart the resident program of the abnormal operation The third restart signal is transmitted to the baseboard management controller 11 through the third universal input/output pin. Wherein, the processing module 13 generates and transmits a third restart command indicating restarting the resident program of the abnormal operation to the platform path controller 14, so as to trigger the platform path controller 14 to generate and transmit instructions to restart The third restart signal of the resident program that operates abnormally. In addition, the processing module 13 can also directly write a parameter indicating the restart of the resident program of the abnormal operation into a register of the platform path controller 14 indicating the restart of the resident program of the abnormal operation to trigger the The platform path controller 14 generates and transmits the third restart signal indicating restarting the resident program of the abnormal operation.

In the sub-step 23, for each notification message, the baseboard management controller 11 restarts the resident program of the abnormal operation corresponding to the notification message after receiving the notification message. It is worth noting that in another embodiment, step 23 For each third restart signal, after receiving the third restart signal, the BMC 11 restarts the resident program of the abnormal operation corresponding to the third restart signal.

Referring to Figure 4, the first baseboard management controller restart procedure is executed after the resident program restart procedure, if after restarting each abnormal resident program, all the resident programs that are abnormally functioning are still unable to operate normally. To restart the BMC 11, the first BMC restart procedure includes a step 31, a step 32, a step 33, a step 34, a step 35, and a step 36.

In this step 31, for each resident program of abnormal operation, after the processing module 13 transmits the corresponding notification message and a first preset time has elapsed, for each resident program of abnormal operation, the processing module 13 generates a first confirmation request related to the resident program of the abnormal operation and transmits it to the baseboard management controller 11 through the platform path controller 14. In particular, the first predetermined time is a predetermined time required for the restart of the at least one abnormally operating resident program. It is worth noting that in the step 31 of another embodiment, for each resident program with abnormal operation, after the processing module 13 triggers the transmission of the corresponding third restart signal and the first preset time has elapsed For each resident program of abnormal operation, the processing module 13 generates the first confirmation request related to the resident program of the abnormal operation and transmits it to the baseboard management controller 11 through the platform path controller 14.

In this step 32, for each first confirmation request, the substrate management control After receiving the first confirmation request, the controller 11 determines whether the abnormal resident program corresponding to the first confirmation request returns to a normal operating state, wherein the baseboard management controller 11 is based on the first confirmation request. Whether the survival value of the resident program corresponding to the abnormal operation changes over time is used to determine whether its operating state returns to normal operation. When it is determined that the corresponding survival value has changed over time, it means that the first confirmation request corresponds to The resident program with abnormal operation has returned to a normal operating state, otherwise, it has not returned to a normal operating state, that is, an abnormal operating state. When the baseboard management controller 11 determines that the abnormal resident program corresponding to the first confirmation request is operating normally, it proceeds to step 33; when the baseboard management controller 11 determines the operation corresponding to the first confirmation request If the abnormal resident program still operates abnormally, the process ends.

In the step 33, the baseboard management controller 11 generates a first confirmation response related to the abnormal resident program that returns to normal operation in the step 32 and transmits it to the processing module through the platform path controller 14 13.

In the step 34, the processing module 13 determines whether a response from the baseboard management controller 11 is received within a second preset time after the first confirmation request is sent for each first confirmation request A first confirmation reply from. When the processing module 13 determines that the first confirmation reply corresponding to each first confirmation request returned by the baseboard management controller 11 is received within the second preset time, the process ends; when the processing The module 13 determines that the substrate management control is not received within the second preset time For the first confirmation reply corresponding to each first confirmation request returned by the device 11, the process step 35 is performed.

In step 35, the processing module 13 triggers the platform path controller 14 to generate the second restart signal indicating to restart the baseboard management controller 11, and transmits it to the second universal input/output pin The baseboard management controller 11 regards the resident program of the abnormal operation related to each first confirmation request for which there is no corresponding first confirmation reply as a resident program to be observed. The processing module 13 generates and transmits a second restart signal indicating to restart the baseboard management controller 11 to the platform path controller 14 to trigger the platform path controller 14 to generate and transmit the instruction to restart The second restart signal of the baseboard management controller 11. In addition, the processing module 13 can also directly write a parameter indicating restarting the baseboard management controller 11 into a register of the platform path controller 14 indicating restarting the baseboard management controller 11 to trigger the The platform path controller 14 generates and transmits the second restart signal indicating to restart the baseboard management controller 11. Wherein, for each first confirmation request that does not have a corresponding first confirmation reply, the first confirmation request corresponding to the first confirmation reply returned by the baseboard management controller 11 is not received within the second preset time One confirmation request.

In this step 36, the baseboard management controller 11 restarts the baseboard management controller 11 after receiving the second restart signal.

Referring to FIG. 5, the first abnormal record generation program is executed after the first baseboard management controller restart program, if the baseboard management controller 11 is restarted, there is still no When the method makes all the resident programs to be observed operate normally, a first abnormality record related to the resident program to be observed that is still operating abnormally will be generated. The first abnormality record generation procedure includes a step 41, a step 42, and a step 43 , A step 44, and a step 45.

In step 41, after the processing module 13 transmits the second restart signal and a third preset time has elapsed, for each resident program to be observed, the processing module 13 generates a resident program related to the resident program to be observed The second confirmation request is sent to the baseboard management controller 11 through the platform path controller 14. In particular, the third preset time is preset to be the time required to wait for the completion of the restart of the baseboard management controller 11.

In this step 42, for each second confirmation request, after receiving the second confirmation request, the baseboard management controller 11 determines whether the resident program to be observed corresponding to the second confirmation request returns to normal operation. When the baseboard management controller 11 determines that the to-be-observed resident program corresponding to the second confirmation request is back to normal operation, proceed to step 43; when the baseboard management controller 11 determines that the to-be-observed corresponding to the second confirmation request If the resident program still operates abnormally, the process ends.

In the step 43, the baseboard management controller 11 generates a second confirmation response related to the responsive to-be-observed resident program in the step 42 and transmits it to the processing module 13 through the platform path controller 14.

In this step 44, the processing module 13 determines whether a response from the baseboard management controller 11 is received within a fourth preset time after the second confirmation request is sent for each second confirmation request A second confirmation reply from. When the processing module 13 It is determined that the second confirmation response corresponding to each second confirmation request from the baseboard management controller 11 is received within the fourth preset time, and the process ends; when the processing module 13 determines that the If the second confirmation reply corresponding to each second confirmation request returned by the baseboard management controller 11 is not received within the fourth preset time, the process step 45 is performed.

In this step 45, the processing module 13 regards the to-be-observed resident program related to the second confirmation request corresponding to the second confirmation reply that does not exist as a to-be-recorded resident program, and generates an instruction for each to-be-recorded The first exception record (Logfile) of the abnormal operation of the resident program. Wherein, for each second confirmation request that does not have a corresponding second confirmation reply, the first confirmation reply corresponding to the second confirmation reply returned by the baseboard management controller 11 is not received within the fourth preset time 2. Confirm the request.

Referring to FIG. 6, the communication interface restart procedure is to restart the communication interface because it cannot receive data related to the resident program execution table, and includes a step 512 and a step 52.

In step 51, the processing module 13 triggers the platform path controller 14 to generate the first restart signal indicating restart of the communication interface, and transmits it to the substrate management via the first universal input/output pin Controller 11. Wherein, the processing module 13 generates and transmits a first restart command indicating to restart the communication interface to the platform path controller 14, so as to trigger the platform path controller 14 to generate and transmit instructions to restart the communication interface Of the first restart signal. In addition, the processing module 13 It is also possible to directly write a parameter indicating restart of the communication interface into a register of the platform path controller 14 indicating restart of the communication interface to trigger the platform path controller 14 to generate and send instructions to restart the communication The first restart signal of the interface.

In step 52, the baseboard management controller 11 restarts the communication interface after receiving the first restart signal.

Referring to FIG. 7, the second BMC restart procedure is after the communication interface restart procedure is executed, and the data related to the resident program execution table cannot be received, then the BMC 11 is restarted, and includes a step 61 , A step 62, a step 63, and a step 64.

In step 61, after the processing module 13 triggers the platform path controller 14 to generate and transmit the first restart signal and a fifth preset time has elapsed, the processing module 13 generates another signal related to the resident The read request of the program execution table is transmitted to the baseboard management controller 11 through the platform path controller 14. In particular, the fifth preset time is a preset time required to wait for the completion of the restart of the communication interface.

In this step 62, the processing module 13 determines whether it has received the data related to the resident program execution table sent by the baseboard management controller 11. When the processing module 13 determines that it has received the data related to the resident program execution table sent by the substrate management controller 11, it returns to the process step 21; when the processing module 13 determines that the substrate management has not been received The data related to the resident program execution table sent by the controller 11 proceeds to step 63 of the process.

In step 63, the processing module 13 triggers the platform path controller 14 to generate the second restart signal indicating to restart the baseboard management controller 11, and transmits it to the second universal input/output pin The baseboard management controller 11. The processing module 13 generates and transmits a second restart signal indicating to restart the baseboard management controller 11 to the platform path controller 14 to trigger the platform path controller 14 to generate and transmit the instruction to restart The third restart signal of the baseboard management controller 11. In addition, the processing module 13 can also directly write a parameter indicating restarting the baseboard management controller 11 into the register of the platform path controller 14 indicating restarting the baseboard management controller 11 to trigger the The platform path controller 14 generates and transmits the second restart signal indicating to restart the baseboard management controller 11.

In this step 64, the baseboard management controller 11 restarts the baseboard management controller 11 after receiving the second restart signal.

Referring to FIG. 8, the second abnormal record generating program generates a second abnormal record related to the communication interface when the resident program execution table cannot be received after the second baseboard management controller restart program is executed, and includes One step 71, one step 72, and one step 73.

In step 71, after the processing module 13 transmits the second restart signal and a sixth preset time has elapsed, the processing module 13 again generates another read request related to the resident program execution table and transmits The platform path controller 14 is transmitted to the baseboard management controller 11. In particular, the sixth preset time is a preset waiting for the substrate management The time required for the controller 11 to restart.

In this step 72, the processing module 13 determines whether it has received the data related to the resident program execution table sent by the baseboard management controller 11. When the processing module 13 determines that it has received the data related to the resident program execution table sent by the substrate management controller 11, it returns to the process step 21; when the processing module 13 determines that the substrate management has not been received The data related to the resident program execution table sent by the controller 11, that is, to determine whether the data related to the resident program execution table sent by the baseboard management controller 11 is received in the transmission period, then proceed to step 73 .

In the step 73, the processing module 13 generates the second abnormal record related to the abnormal operation of the communication interface.

In summary, the method of the present invention for monitoring the resident program of a baseboard management controller uses the processing module 13 to periodically read information related to the computer device 1 during the boot phase and after the boot is completed. The data of the resident program execution table is used to detect whether the operating status of each resident program is operating normally, and when the at least one abnormally operating resident program is detected, first the at least one abnormally operating resident program The program is restarted, and it is checked again whether the at least one resident program with abnormal operation returns to a normal operating state, and when the at least one resident program still in abnormal operation is detected again, the baseboard management controller 11 is restarted , Through the method for monitoring the resident program of the baseboard management controller, it is effectively achieved that when the at least one abnormal operation of the resident program is detected simply because the at least one resident program The abnormal operation of the resident program itself is not caused by the abnormal operation of the baseboard management controller 11 itself. The resident program cannot be in a normal operating state, so there is no need to directly restart the baseboard management controller 11 to make the At least one resident program that operates abnormally automatically returns to a normal operating state. In addition, it can also automatically determine whether the processing module 13 cannot communicate with the baseboard management controller 11 through the communication interface, causing the baseboard management controller 11 to fail. The operating status of the resident program is monitored, and after confirmation, the communication interface is automatically restarted through the platform path controller 14 so that the processing module 13 can continue to monitor the resident program of the baseboard management controller 11. Therefore, the purpose of the invention can indeed be achieved.

However, the above are only examples of the present invention. When the scope of implementation of the present invention cannot be limited by this, all simple equivalent changes and modifications made in accordance with the scope of the patent application of the present invention and the content of the patent specification still belong to Within the scope of the patent for the present invention.

21~23: Steps

Claims (9)

A method for monitoring the resident program of a substrate management controller is implemented by a computer device. The computer device includes a processing module and a substrate management controller electrically connected to the processing module. The substrate management controller is used for A plurality of resident programs are executed. The method for monitoring the resident programs of a baseboard management controller includes the following steps: (A1) A resident program execution table is generated by the baseboard management controller, and the resident program execution table includes a plurality of pairs It should wait for the program code of the resident program and a survival value corresponding to each resident program. Each survival value will be updated when the corresponding resident program is normally executed by the baseboard management controller; (A2) by this process The module reads the survival values corresponding to the resident programs in the resident program execution table, and based on the survival values corresponding to the resident programs read last time and the resident programs currently read The corresponding survival value determines whether there is at least one abnormally functioning resident program in the resident programs, wherein the survival value of each abnormally functioning resident program in the previous read is the same as its current survival value. Value; and (A3) when the processing module determines that there is at least one resident program with an abnormal operation, the processing module informs the baseboard management controller, so that the baseboard management controller restarts each abnormal operation Resident program. The method for monitoring the resident program of a substrate management controller according to claim 1, wherein the computer device further includes an electrical connection between the processing module and the substrate tube The platform path controller of the management controller, the processing module is electrically connected to the baseboard management controller via the platform path controller, and the processing module also performs signal transmission with the baseboard management controller through a communication interface, wherein, Before this step (A2), it also includes the following steps: (B1) through the processing module, generate a read request related to the resident program execution table and send it to the baseboard management controller through the platform path controller ; (B2) by the processing module, determine whether the baseboard management controller has received the data related to the resident program execution table; and (B3) when the processing module determines that the baseboard management control has been received When the data related to the resident program execution table in the device, perform this step (A2). The method for monitoring the resident program of a baseboard management controller according to claim 2, wherein, after this step (B2), it further includes the following steps: (C1) when the processing module determines that the substrate has not been received When managing data related to the resident program execution table in the controller, the processing module triggers the platform path controller to generate and send a first restart signal indicating restarting the communication interface to the baseboard management controller ; And (C2) through the baseboard management controller, after receiving the first restart signal, restart the communication interface. The method for monitoring the resident program of a baseboard management controller according to claim 3, wherein, after the step (C2), the method further includes the following steps: (D1) using the processing module to generate another related Resident in this The read request of the program execution table is transmitted to the baseboard management controller through the platform path controller; (D2) through the processing module, it is determined whether the execution table related to the resident program in the baseboard management controller is received (D3) When the processing module determines that it has received the data related to the resident program execution table in the baseboard management controller, perform this step (A2). The method for monitoring the resident program of a baseboard management controller as described in claim 4, wherein after this step (D2), it further includes the following steps: (E1) when the processing module again determines that it has not received the When the data in the baseboard management controller is related to the resident program execution table, the processing module triggers the platform path controller to generate and transmit a second restart signal indicating to restart the baseboard management controller to the substrate Management controller; and (E2) through the baseboard management controller, after receiving the second restart signal, restart the baseboard management controller. The method for monitoring the resident program of a baseboard management controller according to claim 5, wherein after this step (E2), it further includes the following steps: (F1) using the processing module to generate another related The read request in the resident program execution table is transmitted to the baseboard management controller through the platform path controller; (F2) through the processing module, it is determined whether the baseboard management controller has received the relevant Data of the program execution table; (F3) When the processing module determines that it has received the data related to the resident program execution table in the baseboard management controller, perform this step (A2); and (F4) when the processing module determines again When the data related to the resident program execution table in the baseboard management controller is not received, the processing module generates a second abnormal record related to the abnormal operation of the communication interface. According to claim 1, the method for monitoring the resident program of a baseboard management controller, the computer device further includes a platform path controller electrically connected to the processing module and the baseboard management controller, and the processing module passes through The platform path controller is electrically connected to the baseboard management controller, wherein the step (A3) further includes the following steps: (A31) when the processing module determines that the at least one abnormal resident program exists, for each The resident program of abnormal operation, through the processing module, generates a notification message indicating the abnormal operation of the resident program, and transmits it to the baseboard management controller through the platform path controller; and (A32) for each The notification message is used by the baseboard management controller to restart the resident program of the abnormal operation corresponding to the notification message after receiving the notification message. The method for monitoring the resident program of a baseboard management controller according to claim 7, wherein, after this step (A32), further includes the following steps: (G1) For each resident program of abnormal operation, by The processing module generates a first confirmation request related to the resident program of the abnormal operation And send to the baseboard management controller through the platform path controller; (G2) through the processing module, determine whether the baseboard management controller responds to each first confirmation within a second preset time Request a first confirmation response; and (G3) when the processing module determines that the response returned by the baseboard management controller is not received within the second preset time for the first confirmation request Upon a confirmation reply, the processing module is used to trigger the platform path controller to generate and transmit a second restart signal indicating to restart the baseboard management controller to the baseboard management controller, and each non-existence corresponds to The abnormal resident program related to the first confirmation request of the first confirmation reply is used as a resident program to be observed; and (G4) through the baseboard management controller, after receiving the second restart signal, restart the Baseboard management controller. The method for monitoring the resident program of a baseboard management controller according to claim 8, wherein, after this step (G4), it further includes the following steps: (H1) For each resident program to be observed, by the processing The module generates a second confirmation request related to the resident program to be observed and transmits it to the baseboard management controller through the platform path controller; (H2) through the processing module, determines a fourth preset time Whether there is a second confirmation reply in response to each second confirmation request sent by the baseboard management controller; and (H3) when the processing module determines that it has not received the response within the fourth preset time When the response returned by the baseboard management controller is to the second confirmation response of each second confirmation request, through the processing module, each missing The resident program to be observed related to the second confirmation request of the corresponding second confirmation reply is used as a resident program to be recorded, and a first abnormal record indicating the abnormal operation of each resident program to be recorded is generated.

Images