JP2018169737A - System monitoring method and computer device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To maintain a function of a management controller when a reset occurs in the management controller without duplexing in a hardware level.SOLUTION: A computer device comprises: OS side data acquisition means 102 for acquiring data held by a management controller 101 when the management controller 101 is to be in a reset state; OS side data holding means 103 for holding the data acquired by the OS side data acquisition means 102; OS side monitoring means 104 for executing monitoring processing under OS's management and storing data collected by the monitoring processing in the OS side data holding means 103; and OS side holding data transmission means 105 for transmitting the data held by the OS side data holding means 103 to the management controller 101 when the reset state of the management controller is released.SELECTED DRAWING: Figure 14

Description

  The present invention relates to a system monitoring method related to monitoring in a computer and a computer apparatus including a management controller.

  In many computer apparatuses, a management controller (BMC: Baseboard Management Controller) independent of a CPU (Central Processing Unit) on which an OS (Operating System) operates is mounted. The management controller performs system monitoring in the computer device. As functions on the management controller increase, hardware and firmware control becomes more complex. As a result, for example, the operation of the management controller becomes unstable, and a situation occurs in which the system administrator explicitly resets the management controller or updates the firmware.

  The management controller generally has a self-reset function. The system administrator may explicitly issue a reset when the management controller is not accessible. In addition, a reset may be automatically issued by the watchdog timer function of the management controller itself. A reset is issued when the firmware of the management controller is updated.

  When a reset is issued, various management functions and fault monitoring functions of the management controller are stopped due to initialization processing or the like while the management controller is being reset (for example, for several minutes). As a result, the management controller cannot capture an event that occurs during reset (when in a reset state), and the event information that has occurred may be lost. That is, while the management controller is being reset, it is impossible to record the operation history of the management system, monitor the sensor, and detect and record the occurrence of a failure.

  In addition, there is a possibility that the management controller does not start after resetting (after the reset state is released). Therefore, there is an increasing demand for avoiding the risk associated with reset when operating a computer device. For example, there is a request to continue monitoring during resetting.

  Japanese Patent Application Laid-Open No. 2005-228561 describes a system that enables failure information to be managed by other means even when the management controller cannot manage failure information.

  In the system described in Patent Literature 1, when the failure information generation module responsible for monitoring the management controller detects that the management controller cannot manage the failure information, the failure information is transmitted to the management server. . Then, the management server stores failure information.

JP 2013-109722 A

  As a countermeasure against the above-mentioned problem concerning the reset of the management controller, a method of duplicating the management controller at the hardware level can be considered. In that case, when one management controller is reset, the other management controller in the standby state is activated, and the function of the management controller is maintained.

  However, in this method, it is duplicated at the hardware level. The method is intended for large-scale servers because hardware changes and modifications are required. This method is not suitable for small-scale servers where it is difficult to change the control method.

  Note that the system described in Patent Document 1 also corresponds to a system in which the management controller and the management server have the functions of the management controller duplicated.

  An object of the present invention is to maintain the function of the management controller when a reset occurs in the management controller without duplication at the hardware level.

  A system monitoring method according to the present invention is a system monitoring method that is executed by a computer device that includes an administrative controller that operates an OS and collects and holds data based on monitoring by performing at least peripheral hardware monitoring processing. When the management controller enters the reset state, the data held by the management controller is acquired, the acquired data is stored in the OS-side data holding means, and the monitoring process is executed under the management of the OS. The collected data is stored in the OS-side data holding unit, and when the reset state of the management controller is released, the data held by the OS-side data holding unit is transmitted to the management controller.

  The computer device according to the present invention is a computer device including a management controller that operates an OS and performs at least peripheral hardware monitoring processing, and acquires data held by the management controller when the management controller enters a reset state. OS-side data acquisition means, OS-side data holding means for holding data acquired by the OS-side data acquisition means, monitoring processing is executed under the management of the OS, and data collected by the monitoring processing is stored in the OS-side data And an OS-side monitoring means for storing data stored in the OS-side data holding means to the management controller when the reset state of the management controller is released. Features.

  According to the present invention, the function of the management controller is maintained when a reset occurs in the management controller without duplication at the hardware level.

It is a block diagram which shows a computer apparatus with the terminal for management. It is a block diagram which shows each function inside the management controller firmware which controls a management controller. It is a block diagram which shows the management control process which operate | moves on OS. It is explanatory drawing which shows an example of sensor list information. It is explanatory drawing which shows an example of the event information stored in the event information storage part. It is explanatory drawing which shows an example of the event information stored in the event information temporary storage part. It is explanatory drawing which shows an example of the sensor specification information stored in the sensor specification storage part. It is a flowchart which shows operation | movement by OS side. It is a flowchart which shows operation | movement of a management controller. It is a flowchart which shows operation | movement by the management controller and OS side when a management controller is reset. It is a flowchart which shows the operation | movement by the side of OS when the management controller has stopped. It is a flowchart which shows the operation | movement by the management controller and OS side at the time of recovery from reset of a management controller. It is a flowchart which shows the operation | movement by the management controller and OS side when a management controller stalls. It is a block diagram which shows the principal part of the computer apparatus by this invention. It is a block diagram which shows the principal part of the computer apparatus of the other aspect by this invention. It is a block diagram which shows the principal part of the computer apparatus of the further another aspect by this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

Embodiment 1. FIG.
FIG. 1 is a block diagram showing the computer apparatus 1 together with the management terminal 11. The external management terminal 11 is a terminal for acquiring event information (event data) held by the management controller 6. Examples of the implementation of the computer apparatus 1 include a personal computer and a server.

  In the example shown in FIG. 1, the computer device 1 includes a CPU 2, a memory 3, a chipset controller 4, a disk (for example, hard disk) 5, a management controller 6, a fan sensor 7, a temperature sensor 8, a voltage sensor 9, and a shared LAN. (Shared LAN port) 10 is included.

  The CPU 2 is connected to the chipset controller 4 and the memory 3. The chip set controller 4 is connected with a disk 5 and a shared LAN 10 as I / O. The OS is operating using each component on the CPU 2, the memory 3, the chipset controller 4, the disk 5, and the shared LAN 10.

  A management controller 6 is connected to the chipset controller 4. The management controller 6 periodically polls the sensor values of various sensors connected to the chipset controller 4 such as the fan sensor 7, the temperature sensor 8, and the voltage sensor 9 via a serial bus (for example, I2C bus). get.

  The management controller 6 has a function of recording the sensor value as event information as an internal log when the acquired sensor value is abnormal. The management controller 6 is connected to a shared LAN 10 that is also used on the OS side. The management terminal 11 is configured to access the management controller 6 using, for example, an IPMI (Intelligent Platform Management Interface) over LAN (Local Area Network) function and acquire event information held by the management controller 6. To do.

  FIG. 2 is a block diagram showing functions inside the management controller firmware 12 that controls the management controller 6. FIG. 2 shows an example in which each function is represented as a component. The function of the management controller firmware 12 may be realized by a guest OS (virtual OS) in the virtual machine.

  The management control unit 13 controls the management function of the entire firmware. The management control unit 13 has a function of responding to requests on the OS side and responding to requests from the network control unit 21 using IPMI over LAN. The management control unit 13 also manages an event information storage unit and center information.

  The sensor value collection unit 20 collects sensor information from the fan sensor 7, the temperature sensor 8, and the voltage sensor 9 illustrated in FIG. 1. Data for determining whether or not the sensor value indicated by the sensor information is normal is stored in the sensor specification storage unit 19 (for example, Sensor Data Record: SDR in the IPMI specification). The management control unit 13 compares the sensor value with the data stored in the sensor specification storage unit 19 to determine whether the sensor value is abnormal.

  The management control unit 13 temporarily stores data indicating abnormality of the sensor value of the fan sensor 7 in the event information temporary storage unit 18. Next, when an abnormality in the sensor value of the fan sensor 7 is detected, the management control unit 13 checks the contents of the event information temporary storage unit 18. When the management control unit 13 determines that the same event has occurred again, the management control unit 13 registers data indicating an abnormality in the sensor value in the event information storage unit 17 as the event.

  In addition, when the sensor control abnormality is detected for the temperature sensor 8 and the voltage sensor 9, the management control unit 13 immediately registers data indicating sensor value abnormality as event information in the event information storage unit 17.

  Further, the management controller firmware 12 includes a reset instruction unit 14 that receives a reset instruction of the management controller 6, an interrupt generation unit 16 that generates an interrupt to the OS side to notify the OS side that the reset instruction has been performed, A reset processing unit 15 that resets the management controller 6 in response to a reset instruction from the reset instruction unit 14 is included. The reset processing by the reset processing unit 15 is performed after a time from when the interrupt generation unit 16 issues an interrupt.

  FIG. 3 is a block diagram showing the management control process 22 operating on the OS. The management control process 22 is created by software (program) that operates under the management of the OS. Each component constituting the management control process 22 is configured in the same manner as each component in the management controller firmware 12 illustrated in FIG. 2 and operates in the same manner as each component in the management controller firmware 12.

  That is, the operations of the event information storage unit 25, the event information temporary storage unit 26, the sensor specification storage unit 27, and the sensor value collection unit 28, which acquire sensor values and register event information, correspond to the correspondence shown in FIG. This is the same as the operation of each component. The management control process 22 shown in FIG. 3 includes an event information generation unit 29 that generates event information, but the function may be included in the management control unit 23.

  The network interface (LAN driver) 30 responds to an event acquisition request by IPMI Over LAN from the outside. The management controller interface (IPMI driver) 24 is driver software generally known as an IPMI driver. The management controller interface 24 plays a role of receiving an interrupt issued immediately before the management controller 6 is reset. When receiving the interrupt, the management control unit 23 requests the management controller interface 24 to acquire internal data (that is, event information) for taking over. The management control unit 23 stores the acquired internal data in the event information temporary storage unit 26. Further, the management control unit 23 instructs the sensor value collection unit 28 to start collection.

  FIG. 4 is an explanatory diagram showing an example of sensor list information collected by the sensor value collection unit 28. FIG. 4 illustrates simple table data holding sensor names and sensor values as sensor list information.

  FIG. 5 is an explanatory diagram illustrating an example of event information stored in the event information storage unit 25. FIG. 5 illustrates simple table data that holds a sensor name, an occurrence time, and a sensor value as event information.

  FIG. 6 is an explanatory diagram illustrating an example of event information stored in the event information temporary storage unit 26. FIG. 6 illustrates simple table data that holds a sensor name, an occurrence time, and a sensor value as event information.

  FIG. 7 is an explanatory diagram illustrating an example of sensor specification information (Sensor Data Record: SDR information) stored in the sensor specification storage unit 27. FIG. 7 illustrates simple table data holding sensor names, event registration determination values, and upper and lower threshold values as sensor specification information. In addition, if a sensor value is a value between an upper limit threshold value and a lower limit threshold value, it will determine with a normal value, and in other than that value, it will determine with it being an abnormal value.

  The event registration determination value “2” indicates that the event is temporarily registered in the event information temporary storage unit 26 when an abnormality is detected, and is registered in the event information storage unit 25 when an abnormality is detected again. The event registration determination value “1” indicates that the event is immediately registered in the event information storage unit 25 when an abnormality is detected.

  Next, the operation of the computer apparatus 1 will be described.

  FIG. 8 is a flowchart showing the operation on the OS side. When the computer apparatus 1 is activated (step S11), the OS is activated (step S12). The management control process 22 starts immediately after the OS starts (step S13).

  The management control unit 23 in the management control process 22 confirms whether the management controller 6 is accessible via the management controller interface 24 (step S14). If access to the management controller 6 is not possible, the system waits until access becomes possible (step S17).

  If access to the management controller 6 is possible, the management control unit 23 acquires sensor specification data and network setting data from the management controller 6 (step S15). Then, the management control unit 23 stores the sensor specification data in the sensor specification storage unit 27. The management control unit 23 performs setting for the driver of the network interface 30 based on the network setting data.

  When the initial setting as described above is completed, the management control process 22 is ready and enters a standby state (step S16).

  FIG. 9 is a flowchart showing the operation of the management controller 6. The management controller 6 is activated when standby power supply to the computer apparatus 1 is started (step S21). The management controller 6 provides various functions for realizing system monitoring and management. Hereinafter, operations focusing on sensor monitoring and sensor event generation will be described.

  The sensor value collection unit 20 accesses the fan sensor 7, the temperature sensor 8, and the voltage sensor 9 and collects sensor values (step S22). Assume that the collected values are, for example, the list information shown in FIG.

  The management control unit 13 compares the list information with the data stored in the sensor specification storage unit 19 (see FIG. 7) to determine whether the sensor value exceeds the upper threshold value or the lower threshold value. (Step S23). If not, the process returns to the sensor value collection process (step S22), and the management control unit 13 repeats the sensor check.

  If the sensor value threshold is exceeded, the management control unit 13 checks the event registration determination value (see FIG. 7) of the corresponding sensor (step S24). If the event registration determination value is “1”, the management control unit 13 records event information in the event information storage unit 17 (steps S25 and S26).

  If the event registration determination value is not “1”, the management control unit 13 checks the event data (see FIG. 6) stored in the event information temporary storage unit 18 (step S27), and the event Is registered, the management control unit 13 registers event information in the event information storage unit 17 (steps S28 and S26). If the event is not registered in the event information storage unit 17, the management control unit 13 records the event information in the event information temporary storage unit 18 (step S29). Thereafter, the process proceeds to step S22.

  Next, operations on the management controller 6 and the OS side when the management controller 6 is reset will be described. FIG. 10 is a flowchart showing operations on the management controller 6 and the OS side when the management controller 6 is reset.

  Assume that a reset request is generated from outside or inside the management controller firmware 12 to the reset instruction unit 14 during operation of the management controller 6 (step S31) (step S32). In response, the interrupt generation unit 16 transmits an interrupt to the OS side (step S33).

  On the OS side, the management control process 22 is in a standby state upon completion of preparation (step 41). That is, the management controller interface 24 is in an interrupt standby state from the management controller 6 side (step S42).

  If there is an interruption (step S43), the management controller interface 24 makes IPMI access to the management controller 6 side, and the event data (temporary event storage information) as illustrated in FIG. Is acquired (step S44). Then, the management control unit 23 stores the acquired event data in the event information temporary storage unit 26. As a result, data from the management controller 6 side is taken over by the management control process 22 on the OS side.

  Thereafter, the network interface 30 is activated (step S45), and collection of sensor values by the management control process 22 is started (step S46).

  The management controller 6 responds to a request for event data (step S44) stored in the event information temporary storage unit 18 from the OS side (step S34). Specifically, the management control unit 13 supplies temporary event storage information to the OS side. When the response is completed, the reset processing unit 15 executes a reset process (step S35). While the management controller 6 is being reset, all functions of the management controller 6 are stopped (step S36).

  Next, the operation on the OS side when the management controller 6 is reset and the function is stopped will be described. In the operation on the OS side, there is a part that performs the same processing as the processing of the management controller 6 shown in FIG.

  FIG. 11 is a flowchart showing the operation on the OS side when the management controller 6 is stopped.

  The sensor value collection unit 28 of the management control process 22 accesses the fan sensor 7, the temperature sensor 8 and the voltage sensor 9 to collect sensor values (steps S51 and S52). Assume that the collected values are, for example, the list information shown in FIG.

  The event information generation unit 29 (which may be the management control unit 23) compares the list information with the data stored in the sensor specification storage unit 27 (see FIG. 7), and the sensor value is the upper threshold value or It is determined whether the lower limit threshold is exceeded (step S53). If not, the process returns to the sensor value collection process (step S52), and the management control unit 23 repeats the sensor check.

  When the sensor value threshold value is exceeded, the event information generation unit 29 (which may be the management control unit 23) checks the event registration determination value (see FIG. 7) of the corresponding sensor (step S54). When the event registration determination value is “1”, the management control unit 23 records event information in the event information storage unit 25 (steps S55 and S56).

  When the event registration determination value is a value other than “1”, the event information generation unit 29 (may be the management control unit 23) stores the event data stored in the event information temporary storage unit 26 (see FIG. 6). (Step S57), if the event is registered, the event information generation unit 29 (may be the management control unit 23) registers the event information in the event information storage unit 25 (steps S58 and S57). Step S56). If the event is not stored in the event information storage unit 25, the event information generation unit 29 (may be the management control unit 23) stores the event information in the event information temporary storage unit 26 (step S59). Thereafter, the process proceeds to step S52.

  Next, operations on the management controller side and the OS side at the time of recovery from the reset of the management controller 6 will be described. FIG. 12 is a flowchart showing operations on the management controller 6 and the OS side when the management controller 6 is recovered from the reset.

  It is assumed that the management controller 6 is in a resetting state (step S61). When the reset is completed, the management controller 6 is restarted and each function starts operating (step S62).

  The management control unit 13 instructs the interrupt generation unit 16 to interrupt the OS in order to notify the OS side that the management controller 6 has returned. In response to the instruction, the interrupt generation unit 16 generates an interrupt to the OS (step S63).

  On the OS side, when the management control process 22 is operating (step S71) and the management controller interface 24 receives an interrupt from the management controller 6 side (step S72), the management controller interface 24 Event data (event storage information) in the event information storage unit 25 and event data (temporary event storage information) in the event information temporary storage unit 26 are transmitted by IPMI, and a write request is made (step S73).

  The management controller 6 responds to the write request (step S73) from the OS side (step S64). That is, the management control unit 13 writes the event data transmitted from the OS side in the event information storage unit 17 and the event information temporary storage unit 18. As a result, data from the OS side is taken over by the management controller 6.

  After the takeover is completed, on the OS side, the management control unit 13 invalidates and stops the function of the network interface 30 (step S75). Then, the management control process 22 enters a standby state (step S75).

  On the management controller side, after the takeover is completed, sensor monitoring resumes (step S65).

Embodiment 2. FIG.
In the first embodiment (embodiment 1), the reset is controlled by the management controller firmware 12, and the interrupt generation unit 16 notifies the OS side of the occurrence of reset and also notifies the restart after completion of the reset.

  In the second embodiment (Embodiment 2), the function of the management controller 6 is handed over to the OS side when the management controller 6 stalls (function stop). Note that. The configurations of the computer apparatus 1, the management controller firmware 12, and the management control process 22 may be the same as those in the first embodiment.

  FIG. 13 is a flowchart showing operations on the management controller 6 and the OS side when the management controller 6 is stalled.

  Assume that a failure occurs in the management controller 6 during operation of the management controller 6 (step S81) (step S82), and all functions of the management controller 6 are stopped (step S83).

  On the OS side, the management control process 22 is ready and is in a standby state (step S91). In the second embodiment, in addition to the function of waiting for an interrupt as in the first embodiment, the management controller interface 24 changes the state of the management controller 6 by polling access to the management controller 6. A check function has been added. The management controller interface 24 performs polling access to the management controller 6, for example, periodically (step S92).

  If the management controller interface 24 is able to access the management controller 6 (step S93), the management control process returns to the standby state and continues periodic polling access.

  However, when access to the management controller 6 becomes impossible, the management control unit 23 activates the network interface 30. Then, collection of sensor values by the management control process 22 is started (step S95). That is, the management control process 22 continues monitoring on behalf of the management controller 6 until the management controller 6 is restored.

  As described above, in each of the above embodiments, the process under the management of the OS on the system side (in the configuration example shown in FIG. 1, the system using the CPU 2, the memory 3, and the disk 5), or the virtual OS on the system side However, it takes over the management controller function at the software level. For example, when a reset instruction is issued to the management controller, an interrupt is issued from the management controller 6 to the OS side immediately before the reset. The OS-side management control process 22 detects in advance that the management controller 6 is reset by an interrupt. The management control process 22 acquires the internal information held in the management controller 6 before the management controller 6 is reset, and the management control process 22 takes over the internal information.

  The internal information includes various information that is managed and monitored by the management controller 6. In each of the above embodiments, the temporary event storage information temporarily registered in the event information temporary storage unit when an abnormality is detected in various sensors of the fan / temperature / voltage as peripheral hardware of the computer apparatus 1 is taken as an example. However, event information related to other hardware may be targeted.

  The event information stored in the event information temporary storage unit 18 is stored in the event information storage unit 17 from the event information temporary storage unit 18 when an event of the same sensor is detected next time. . The information stored in the event information temporary storage unit 18 is information that cannot be referred to from outside, but the information stored in the event information storage unit 17 is information that can be referred to from outside. For example, for an event related to a fan sensor, even if it is detected that the number of fan rotations is outside the threshold range, it is not immediately registered as fan event information, and the next event related to the fan sensor is detected. Is registered in the event information storage unit 17.

  After the transfer of the internal information is completed, the management controller 6 is reset and the function of the management controller 6 is stopped. After the management controller 6 stops, the management control process 22 on the OS side performs sensor monitoring on behalf of the management controller 6. The management control process 22 on the OS side detects an abnormality in the sensor value and operates in the same manner as the management controller 6, and stores event information related to the sensor in the event information temporary storage unit 26 or the event information storage unit 25. Register.

  When the management controller 6 is restarted and the management function and the monitoring function are restored, the management controller 6 sends an interrupt again to the OS side to notify the restoration. When the OS side receives an interrupt, the management control process 22 stops monitoring the sensor and transmits event information stored in the event information storage unit 25 and event information temporary storage unit 26 on the OS side to the management controller 6. In the management controller 6, the event information is reflected in the event information storage unit 17 and the event information temporary storage unit 18. That is, data is taken over. After the takeover is completed, the OS-side control program (management control process 22) stops functioning and the management controller 6 resumes monitoring and management.

  In each embodiment described above, the following effects can be obtained.

  In the computer apparatus 1 such as a server in which the management controller 6 is mounted, hardware monitoring and management can be continued during the temporary reset of the management controller 6 or even when the management controller 6 cannot be operated due to a failure or the like. Further, since the replacement of the management controller 6 is realized at the software level, not at the hardware level, it is not necessary to mount hardware having the replacement function of the management controller 6, and the mounting to the small computer apparatus 1 is not necessary. Is easy.

  FIG. 14 is a block diagram showing the main part of the computer apparatus according to the present invention. The computer apparatus 100 shown in FIG. 14 has an OS-side data acquisition unit 102 (in the embodiment, the management controller interface 24 and the management control unit 23) that acquires data held by the management controller 101 when the management controller 101 enters a reset state. And the OS-side data holding unit 103 that holds the data acquired by the OS-side data acquisition unit 102 (in the embodiment, it is realized by the event information storage unit 25 and the event information temporary storage unit 26). And OS-side monitoring means 104 that executes monitoring processing under the management of the OS and stores the data collected by the monitoring processing in the OS-side data holding means 103 (in the embodiment, the sensor value collection unit 20 and the event information generation unit) 29)), and when the reset state of the management controller is released (In the embodiment, is realized by the management controller interface 24.) OS side holding data transmitting means 105 for transmitting data OS-side data holding means 103 holds the management controller 101 and a.

  FIG. 15 is a block diagram showing a main part of a computer apparatus according to another aspect of the present invention. The computer apparatus 100 shown in FIG. 15 includes an interrupt unit 106 that issues an interrupt to the OS side when the management controller enters the reset state and when the reset state is released (in the embodiment, the interrupt generation unit 16). Is realized.)

  FIG. 16 is a block diagram showing a main part of a computer apparatus according to still another aspect of the present invention. A computer apparatus 100 shown in FIG. 16 includes inquiry means 107 (implemented by the management controller interface 24 in the embodiment) for making an inquiry (for example, polling) to the management controller 101 under management of the OS. The OS-side monitoring unit 104 starts the monitoring process when the management controller 101 does not respond to the inquiry.

1 Computer device 2 CPU
3 Memory 4 Chipset controller 5 Disk 6 Management controller 7 Fan sensor 8 Temperature sensor 9 Voltage sensor 10 shared LAN
DESCRIPTION OF SYMBOLS 11 Management terminal 12 Management controller firmware 13 Management control part 14 Reset instruction | indication part 15 Reset process part 16 Interrupt generation part 17 Event information storage part 18 Event information temporary storage part 19 Sensor specification storage part 20 Sensor value collection part 21 Network control part 22 Management control process 23 Management control unit 24 Management controller interface 25 Event information storage unit 26 Event information temporary storage unit 27 Sensor specification storage unit 28 Sensor value collection unit 29 Event information generation unit 30 Network interface 100 Computer device 101 Management controller 102 OS side data Acquisition means 103 OS-side data holding means 104 OS-side monitoring means 105 OS-side holding data transmission means 106 Interrupt means 107 Inquiry means

Claims (8)

A system monitoring method that is executed by a computer device that includes a management controller that operates an OS and collects and holds data based on monitoring by performing at least peripheral hardware monitoring processing,
When the management controller enters a reset state, obtain data held by the management controller;
Store the acquired data in the OS side data holding means,
Executing the monitoring process under the management of the OS, storing the data collected by the monitoring process in the OS-side data holding means,
When the reset state of the management controller is released, the data held by the OS-side data holding unit is transmitted to the management controller. The system monitoring method according to claim 1, wherein monitoring processing is executed when the management controller is in a reset state by software operating under management of the OS. The system monitoring method according to claim 1 or 2, wherein an interrupt is issued to the OS when the management controller enters a reset state and when the reset state is released. Make an inquiry to the management controller under the management of the OS,
The system monitoring method according to any one of claims 1 to 3, wherein when the management controller does not respond to the inquiry, monitoring processing under management of the OS is started. A computer device including a management controller on which an OS operates and performs at least monitoring processing of peripheral hardware,
OS-side data acquisition means for acquiring data held by the management controller when the management controller enters a reset state;
OS side data holding means for holding data acquired by the OS side data acquisition means;
An OS-side monitoring unit that executes the monitoring process under management of the OS and stores data collected by the monitoring process in the OS-side data holding unit;
A computer apparatus comprising: OS-side retained data transmitting means for transmitting data retained by the OS-side data retaining means to the management controller when the reset state of the management controller is released. The computer apparatus according to claim 5, wherein the OS side monitoring unit executes monitoring processing by software operating under management of the OS. The computer apparatus according to claim 5 or 6, further comprising interrupt means for issuing an interrupt to the OS side when the management controller enters the reset state and when the reset state is released. Inquiry means for making an inquiry to the management controller under the management of the OS,
The computer apparatus according to any one of claims 5 to 7, wherein the OS-side monitoring unit starts monitoring processing when the management controller does not respond to the inquiry.

Images