Patent Application
20210334153
This application claims priority of Chinese Invention Patent Application No. 202010332224.8, filed on Apr. 24, 2020.
The disclosure relates to an error detection method, and more particularly to a remote error detection method for an engineer to remotely detect errors of a computer device.
With the development of network technology, the need for data centers with large numbers of service hosts that provide various network services arises. In practice, such a data center may have more than one hundred service hosts. A conventional error detection method is to set various trigger events in advance through the baseboard management controllers (BMCs) of the service hosts in the data center, with the trigger events being, for example, abnormally low fan speed, termination of fan operation, shutting down of service host, excessively high temperature sensed by various temperature sensors, etc. When any of these trigger events occurs, the corresponding BMC will send an alert message to a remote host, such as another service host or a computer host, through a network connection. That is, when one of the service hosts in the data center has an abnormal execution, an engineer in front of the remote host can be informed by the alert message, and then visit the data center physically to perform debugging on the service host that corresponds to the alert message. However, the existing error detection method can only achieve the effect of notification, while the engineer may not be informed of what kind of error has occurred; also, it is inconvenient for the engineer to locate the service host that has the abnormal execution from among a large number of service hosts.
Therefore, an object of the disclosure is to provide a remote error detection method that enables an engineer to debug remotely.
According to the disclosure, the remote error detection method is adapted for a remote computer device to detect errors that occur in a service computer device. The service computer device includes a baseboard management controller (BMC) and a storage unit. The method includes steps of: A) by the service computer device, storing error log collection data that are related to the service computer device in the storage unit; B) by the service computer device, generating an alert signal when the BMC determines that a predetermined trigger event has occurred, and transmitting the alert signal to the remote computer device; and C) by the remote computer device, receiving the error log collection data that are stored in the storage unit after the service computer device sends the alert signal to the remote computer device.
Other features and advantages of the disclosure will become apparent in the following detailed description of the embodiment(s) with reference to the accompanying drawings, of which:
Before the disclosure is described in greater detail, it should be noted that where considered appropriate, reference numerals or terminal portions of reference numerals have been repeated among the figures to indicate corresponding or analogous elements, which may optionally have similar characteristics.
Referring to
The first embodiment includes steps S1 to S4.
In step S1, a central processing unit (CPU, not shown) and/or the BMC 11 of the service computer device 1 generates error log collection (ELC) data that are related to the service computer device 1 during operation thereof (e.g., execution of various tasks, programs, etc.), and stores the ELC data in the storage unit 12. The ELC data may include, for example but not limited to, at least one of output data of an intelligent platform management interface (IPMI) protocol, a boot log of a basic input/output system (BIOS), a runtime log of an embedded system, or internal log data of the BMC 11.
For example, the output data of the IPMI protocol may include, for example but not limited to, “channel_cipher_ipmi”, “channel_cipher_sol”, “channel_info”, “chassis_status”, “firewall_info”, “fru”, “mc_getenables”, “mc_guid”, “mc_info”, “mc_wdt”, “pef_info”, “pef_list”, “sdr_elist”, “sdr_info”, “sel_elist”, “sel_info”, “sensors”, “session_active”, “sol_info”, “user_list”, “user_summary”, etc., which can be used by engineers to learn a status of the service computer device 1. The boot log of the BIOS may include, for example but not limited to, “SOLHostCapture”, “SOLHostCapture.log.1”, etc., which can be used by engineers to analyze error messages, and a root cause and a consequence of relevant errors that are generated during a boot process of the BIOS. The runtime log of the embedded system may include, for example but not limited to, “rt_cpuinfo”, “rt_filesystems”, “rt_ifconfig”, “rt_interrupts”, “rt_iomem”, “rt_locks”, “rt_meminfo”, “rt_mtd”, “rt_pagetypeinfo”, “rt_postcode”, “rt_ps”, “rt_top”, “rt_vmallocinfo”, “rt_vmstat”, “rt_zoneinfo”, etc., which can be used by engineers to learn a status of the BMC 11, so the engineers can know whether the occurrence of errors or abnormalities result from an internal system of the BMC 11. The internal log data of the BMC 11 may be related to records of webpage browsing, and/or editing history of remote log-in authorization, etc.
In step S2, prior to error detection, the remote computer device 2 sends a trigger event setting to the service computer device 1, and the service computer device 1 selects a portion (e.g., one or more or all) of candidate trigger events that are pre-stored in the storage unit 12 according to the trigger event setting, so as to form a trigger event set that includes the selected portion of the candidate trigger events. The candidate trigger events are related to various abnormal operations of the service computer device 1, such as abnormally low fan speed, termination of fan operation, shutting down of service computer device 1, excessively high temperature sensed by various temperature sensors, etc., but this disclosure is not limited in this respect. Any trigger event in the trigger event set is referred to as a predetermined trigger event.
In step S3, upon determining that a predetermined trigger event has occurred, the BMC 11 generates and transmits an alert signal to the remote computer device 2. In some embodiments, the alert signal indicates the predetermined trigger event or otherwise corresponds to the predetermined trigger event, so that the remote computer device 2 is notified of occurrence of the predetermined trigger event. For example, the selected portion of the candidate trigger events includes termination of fan operation, so upon determining that one of the fans of the service computer device 1 has stopped operating, the BMC 11 generates and transmits the alert signal that indicates occurrence of termination of fan operation to the remote computer device 2. The alert signal may be a notification message related to, for example but not limited to, “Broadcast Rsyslog”, “Pre-config IP Rsyslog”, “Redfish Notification” or “IPMI SEL trap”, etc., but this disclosure is not limited in this respect.
In step S4, upon receipt of the alert signal, the remote computer device 2 automatically downloads the ELC data that are stored in the storage unit 12 via the BMC 11. It is noted that, in this embodiment, regardless of whether the predetermined trigger event occurs or not, errors that occur during operation of the CPU and/or the BMC 11 of the service computer device 1 will be continuously collected and recorded in the ELC data, so the ELC data include complete error data that are related to the service computer device 1. Accordingly, when the remote computer device 2 receives the alert signal, the ELC data downloaded by the remote computer device 2 would include all of the error data. The data transmission of the ELC data between the remote computer device 2 and the BMC 11 may be related to, for example but not limited to, “TFTP server”, “Redfish oem schema”, “SFTP”, or “IPMI oem command”, etc., but this disclosure is not limited in this respect.
A second embodiment of the remote error detection method according to this disclosure is similar to the first embodiment, and differs therefrom in that, in the second embodiment, step S2 is omitted, that is, the trigger event set is not determined by the remote computer device 2 sending the trigger event setting to the service computer device 1, but may be predefined in the service computer device 1. For example, an engineer may directly operate the service computer device 1 to select a portion of the candidate trigger events to create the trigger event set.
Referring to
A fourth embodiment of the remote error detection method according to this disclosure is similar to the third embodiment, and differs therefrom in that, in the third embodiment, step S2 is omitted, that is, the trigger event set is not determined by the remote computer device 2 sending the trigger event setting to the service computer device 1, but may be predefined in the service computer device 1. For example, an engineer may directly operate the service computer device 1 to select a portion of the candidate trigger events to create the trigger event set.
In summary, in the embodiments of the remote error detection method according to this disclosure, error information of the service computer device 1 is continuously collected and stored as the ELC data, and, upon determining that the predetermined trigger event has occurred, the BMC 11 generates the alert signal to notify the remote computer device 2 of occurrence of the predetermined trigger event, making the remote computer device 2 automatically acquire the ELC data that are stored in the storage unit 12. As a result, the engineer would become aware of and fix the errors that occurred on the service computer device 1 remotely, and thus would not be required to physically visit the data center at which the service computer device 1 is located in order to fix the errors.
In the description above, for the purposes of explanation, numerous specific details have been set forth in order to provide a thorough understanding of the embodiment(s). It will be apparent, however, to one skilled in the art, that one or more other embodiments may be practiced without some of these specific details. It should also be appreciated that reference throughout this specification to “one embodiment,” “an embodiment,” an embodiment with an indication of an ordinal number and so forth means that a particular feature, structure, or characteristic may be included in the practice of the disclosure. It should be further appreciated that in the description, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of various inventive aspects, and that one or more features or specific details from one embodiment may be practiced together with one or more features or specific details from another embodiment, where appropriate, in the practice of the disclosure.
While the disclosure has been described in connection with what is (are) considered the exemplary embodiment(s), it is understood that this disclosure is not limited to the disclosed embodiment(s) but is intended to cover various arrangements included within the spirit and scope of the broadest interpretation so as to encompass all such modifications and equivalent arrangements.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202010332224.8 | Apr 2020 | CN | national |
