Method, device, terminal and medium for optimizing fault diagnosis log collection process

Abstract

The application provides a method, device, terminal and medium for optimizing a fault diagnosis log collection process, and belongs to the technical field of server log collection.The method steps are as follows: S1.BMC pre-maintains a mapping file of a mapping relationship between device asset information and a state register; S2.BMC records downtime after detecting a set error register, informs an ACD tool to collect state register information, and records a collection completion time; S3.BMC informs a BAFI tool to analyze fault device information and error type information, records an analysis completion time after the analysis is completed, and records and informs a user to collect fault diagnosis logs when the fault device information is located.The application realizes accurate acquisition of the time used in each stage in a fault diagnosis process, a simple and fast fault analysis process, and can prompt after the analysis is completed and realize separate collection of fault diagnosis logs.

Description

Technical Field

[0001] This invention belongs to the field of server log collection technology, specifically relating to a method, apparatus, terminal, and medium for optimizing the fault diagnosis log collection process. Background Technology

[0002] ACD is short for Autonomous Crash Dump.

[0003] BAFI is a tool in the Go framework that uses templates to translate common JSON, BSON, YAML, and XML into any format; it is also known as a file parsing tool.

[0004] CAT ERR is short for Conditional Acceptance Error. In CPU terms, CATERR stands for Code Error.

[0005] PECI is short for Platform Environment Control Interface.

[0006] SEL is short for System Event Log.

[0007] When the business operating system crashes due to internal errors, uncorrectable memory errors, or severe bus errors, the BMC automatically collects CPU fault register information via ACD and analyzes the faulty component, module, and cause using the BAFI tool. Existing fault analysis methods utilize native Intel ACD and BAFI programs.

[0008] After introducing the native Intel ACD & BAFI BMC code library, when the system crashes due to an internal error, the CPLD detects that the CPU CAT ERR_N pin is continuously low (generally greater than 160ns) and sets the relevant CPU registers. After the BMC polls the set registers, it calls the internally integrated ACD program to collect register information. The ACD collects all register information by executing the PECI command and generates a crashdump.json file. The BMC then calls the BAFI tool and combines it with a MAP file containing BDF information for all memory and PCIe devices to parse the crashdump.json file and finally generate a bafi debug.json file. Users can download the one-click log to obtain the bafi debug.json file and extract fault information.

[0009] The above method has the following drawbacks: First, when users have time requirements for BMC fault diagnosis, it is impossible to accurately obtain the time from the occurrence of the crash to the ACD completing the collection of fault registers and the BAFI tool completing the parsing; second, the native BAFI program can only provide the final parsed file and cannot transmit information during the parsing process to the BMC. Consequently, after each fault occurs, locating the PCIe device and memory physical location that caused the crash requires collecting one-click logs, finding the BAFI parsed file, and extracting useful information from it, which is quite time-consuming when the BAFI tool parses a large amount of information; third, the BAFI tool does not provide any prompts to the user after parsing, which may cause relevant personnel to overlook the analysis of this fault; finally, log collection requires a full log collection of the BMC and cannot collect fault diagnosis logs separately.

[0010] Therefore, it is essential to provide a method, apparatus, terminal, and medium for optimizing the fault diagnosis log collection process to address the aforementioned shortcomings. Summary of the Invention

[0011] To address the shortcomings of the native ACD and BAFI tools in introducing the BMC code library, which resulted in unclear time consumption at each stage of the fault diagnosis process, time-consuming extraction of useful information from the BAFI tool's file parsing, lack of completion prompts, and inability to collect fault diagnosis logs independently, this invention provides a method, apparatus, terminal, and medium to optimize the fault diagnosis log collection process, thereby solving the aforementioned technical problems.

[0012] In a first aspect, the present invention provides a method for optimizing the fault diagnosis log collection process, comprising the following steps:

[0013] S 1. BMC pre-maintains a mapping file that establishes the mapping relationship between equipment asset information and status registers;

[0014] S 2. After the BMC detects the set error register, it records the downtime, notifies the ACD tool to collect status register information, and records the collection completion time.

[0015] S 3. BMC notifies the BAFI tool to parse faulty device information and error type information, and records the parsing completion time after the parsing is completed. When faulty device information is located, it records and notifies the user to collect fault diagnosis logs.

[0016] Furthermore, the specific steps of step S1 are as follows:

[0017] S11. Configure the Basic Input / Output System to push the server's device asset information to the BMC after POST is completed;

[0018] S12. BMC maintains the mapping relationship between equipment asset information and status registers, and generates a mapping file;

[0019] S13. BMC saves the mapping file to the specified directory. The mapping file is saved in the specified directory of the BMC system.

[0020] Furthermore, server equipment assets include memory and PCIe devices, and equipment asset information includes location information and BDF information. BDF stands for Binary Data File, which is created by data analysis programs and used to identify the health status of unused hard disk space, also known as logical volume status.

[0021] Furthermore, the specific steps of step S2 are as follows:

[0022] S21. BMC checks whether the error register is set;

[0023] If so, proceed to step S22;

[0024] If not, return to step S21;

[0025] S22.BMC records the current time as the downtime;

[0026] S23. BMC notifies the ACD tool to collect all status register information;

[0027] S24.BMC checks for the presence of faulty save files;

[0028] If so, proceed to step S25;

[0029] If not, return to step S24;

[0030] S25. BMC determines that the ACD tool has completed collecting status register information and records the collection completion time. Once the ACD tool has completed collecting status register information, it automatically generates a fault dump file. The downtime and collection completion time are recorded for subsequent statistical analysis of the time taken at each stage.

[0031] Furthermore, the following steps are included before step S21:

[0032] When the business operating system crashes due to an internal error, the CPLD sets the error register. The BMC can determine that an internal server failure has occurred by detecting the error register being set.

[0033] Furthermore, the specific steps of step S3 are as follows:

[0034] S 31.BMC uses the optimized BAFI tool to parse the fault dump file and obtain faulty device information and error type information;

[0035] S 32. Determine whether the faulty device information is located in the fault transfer file;

[0036] If so, proceed to step S33;

[0037] If not, the BAFI tool will analyze the existing faults and generate a parsing and debugging file with empty key information, then the process will end.

[0038] S 33. BMC records the information in the fault diagnosis log and checks whether a parsing debug file exists;

[0039] If so, record the parsing completion time and proceed to step S34;

[0040] If not, return to step S33;

[0041] S 34. Notify users to collect fault diagnosis logs.

[0042] Furthermore, the specific steps of step S 33 are as follows:

[0043] Add a fault diagnosis log register to S 331.BMC;

[0044] After completing the parsing of the fault dump file, the S 332.BAFI tool returns faulty device information and error type information to the BMC;

[0045] The S 333.BAFI tool generates and parses the debug file, sets the fault diagnosis log register, and triggers the SEL log collection.

[0046] S 334.BMC records faulty equipment information and error type information in the fault diagnosis log;

[0047] S 335.BMC checks if a parsing / debugging file exists;

[0048] If so, proceed to step S 336;

[0049] If not, return to step S 332;

[0050] S 336. The BMC determines that the BAFI tool has completed the parsing of the fault transfer file, records the parsing completion time, and proceeds to step S34. During the parsing process, the BAFI tool returns the BDF and error type information of the faulty device to the BMC. The BMC parses the specific device location and error type based on the returned information and records them in the IDL log. Finally, after the BAFI tool completes the parsing and generates the parsing debug file, the BMC records the parsing debug file generation time, which is the parsing completion time.

[0051] Furthermore, step S34 is as follows:

[0052] S 341. The BAFI tool determines whether the time taken for the collection and parsing phases meets the user's requirements based on the recorded downtime, collection completion time, and parsing completion time.

[0053] If so, proceed to step S 343;

[0054] If not, proceed to step S 342;

[0055] S 342. The BAFI tool records the triggered timeout SEL log;

[0056] S 343. The BAFI tool determines whether the user has downloaded the fault diagnosis log;

[0057] If so, proceed to step S 344;

[0058] If not, return to step S 343;

[0059] The S 344.BAFI tool de-sets the fault diagnosis log register and removes the SEL log from log collection. The BMC adds a fault diagnosis log register. After the BAFI tool finishes parsing, it sets the register and records the SEL log that triggered log collection. A dedicated interface is provided for users to download the fault diagnosis log. After downloading, the user de-sets the register and records the SEL log that removed log collection. If the customer has time requirements, the test determines whether the time taken for each stage meets the customer's requirements; if not, it records the SEL log that triggered a timeout.

[0060] Secondly, the present invention provides an apparatus for optimizing the fault diagnosis log collection process, comprising:

[0061] The mapping file maintenance module is used to pre-maintain mapping files that map the relationship between equipment asset information and status registers in the BMC;

[0062] The information collection module is used to record the downtime after the BMC detects a set error register, notify the ACD tool to collect status register information, and record the collection completion time.

[0063] The information parsing and fault notification module is used to notify the BAFI tool to parse faulty device information and error type information in the BMC, record the parsing completion time after the parsing is completed, and record and notify the user to collect fault diagnosis logs when faulty device information is located.

[0064] Furthermore, the mapping file maintenance module includes:

[0065] The device asset information push unit is used to configure BIOS to push the server's device asset information to BMC after POST is completed;

[0066] The mapping file generation unit is used to maintain the mapping relationship between equipment asset information and status registers in the BMC and generate mapping files;

[0067] The mapping file saving unit is used to save mapping files in the BMC to a specified directory.

[0068] Furthermore, the information collection module includes:

[0069] The error register set detection unit is used to detect whether the error register is set in the BMC.

[0070] The downtime recording unit is used to record the current time as the downtime in the BMC when the error register is set;

[0071] The status register information collection unit is used to collect all status register information when the BMC notifies the ACD tool.

[0072] The fault save file existence detection unit is used to detect the existence of fault save files in the BMC.

[0073] The collection completion time recording unit is used to record the collection completion time when the BMC determines that the ACD tool has completed collecting status register information and when there is a faulty transfer file.

[0074] Furthermore, the information parsing and fault notification module includes:

[0075] The fault transfer file parsing unit is used in the BMC to parse the fault transfer file using the optimized BAFI tool to obtain fault device information and error type information;

[0076] The fault equipment information location and judgment unit is used to determine whether fault equipment information is located in the fault transfer file;

[0077] The debug file generation unit is used to parse the existing faults using the BAFI tool when the faulty device information cannot be located, and generate a debug file with empty key information, then ends.

[0078] The existence judgment unit for parsing debugging files is used to record faulty device information in the fault diagnosis log in the BMC when faulty device information is located, and to determine whether a parsing debugging file exists.

[0079] The parsing completion time recording unit is used to record the parsing completion time when a parsing debugging file exists;

[0080] The fault diagnosis log collection notification unit is used to notify users to collect fault diagnosis logs.

[0081] Furthermore, the unit for determining the existence of the debug file includes:

[0082] A sub-unit is added to the fault diagnosis log register to add a fault diagnosis log register to the BMC;

[0083] The parsing information return sub-unit is used to return fault device information and error type information to the BMC after the BAFI tool completes the parsing of the fault transfer file;

[0084] The fault register setting and log collection triggering subunit is used to generate and parse the debug file in the BAFI tool, set the fault diagnosis log register, and trigger the SEL log collection.

[0085] The fault diagnosis log recording subunit is used to record faulty device information and error type information into the fault diagnosis log in the BMC.

[0086] The parsing debug file existence check subunit is used to determine in the BMC whether a parsing debug file exists.

[0087] The parsing completion time recording subunit is used when the BMC determines that the BAFI tool has completed parsing the fault transfer file, and records the parsing completion time when a parsing debug file exists. During the parsing process, the BAFI tool returns the BDF and error type information of the faulty device to the BMC. The BMC parses the specific device location and error type based on the returned information and records them in the IDL log. Finally, after the BAFI tool completes parsing and generates the parsing debug file, the BMC records the parsing debug file generation time, which is the parsing completion time.

[0088] Furthermore, the fault diagnosis log collection and notification unit includes:

[0089] The timing judgment subunit is used by the BAFI tool to determine whether the time taken during the collection and parsing phases meets the user's requirements based on the recorded downtime, collection completion time, and parsing completion time.

[0090] The timeout log recording trigger subunit is used to record a timeout SEL log in the BAFI tool when the time taken during the collection and parsing phases does not meet the user requirements.

[0091] The fault diagnosis log download waiting subunit is used to determine whether the user should download the fault diagnosis log when the time taken during the collection and parsing phases meets the user's requirements in the BAFI tool.

[0092] The log collection deactivation subunit is used to deactivate the fault diagnosis log register in the BAFI tool and deactivate the SEL log for log collection when the user completes the download of the fault diagnosis log. The BMC adds a fault diagnosis log register; after the BAFI tool finishes parsing, it sets this register and records the SEL log that triggered log collection, providing the user with a dedicated interface to download the fault diagnosis log. After the user completes the download, it deactivates the register and records the SEL log for deactivation. If the customer has time requirements, it checks whether the time taken for each stage meets the customer's requirements; if not, it records the SEL log for triggering a timeout.

[0093] Thirdly, the present invention provides a terminal, including a processor and a memory;

[0094] The memory is used to store a computer program, and the processor is used to retrieve and run the computer program from the memory, causing the device to perform the method described in the first aspect above.

[0095] Fourthly, the present invention provides a storage medium.

[0096] The storage medium stores instructions that, when run on a computer, cause the computer to perform the method described in the first aspect above.

[0097] The beneficial effects of this invention are as follows:

[0098] The present invention provides a method, apparatus, terminal and medium for optimizing the fault diagnosis log collection process, which enables the acquisition of accurate data at each stage of fault register information collection and parsing after a server crash. The BAFI tool can transmit the final parsing completed to the BMC, enabling accurate and rapid location of the faulty device that caused the crash. It can also automatically prompt staff when the fault transfer file is parsed, and realize the separate collection of fault diagnosis logs without the need for full log collection of the BMC.

[0099] This invention optimizes the fault diagnosis log collection process, simplifies user operations, and meets user needs.

[0100] Furthermore, the design principle of this invention is reliable, the structure is simple, and it has a very wide range of application prospects.

[0101] Therefore, it is evident that the present invention has outstanding substantive features and significant progress compared with the prior art, and the beneficial effects of its implementation are also obvious. Attached Figure Description

[0102] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0103] Figure 1 This is a flowchart of Embodiment 1 of the method for optimizing the fault diagnosis log collection process of the present invention.

[0104] Figure 2 This is a flowchart of Embodiment 2 of the method for optimizing the fault diagnosis log collection process of the present invention.

[0105] Figure 3 This is a schematic diagram of the fault transfer file parsing process of the present invention.

[0106] Figure 4 This is a schematic diagram of the process by which the present invention notifies users to collect fault diagnosis logs.

[0107] Figure 5 This is a schematic diagram of the device for optimizing the fault diagnosis log collection process according to the present invention. Detailed Implementation

[0108] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this invention.

[0109] Example 1:

[0110] like Figure 1 As shown, the present invention provides a method for optimizing the fault diagnosis log collection process, comprising the following steps:

[0111] S 1. BMC pre-maintains a mapping file that establishes the mapping relationship between equipment asset information and status registers;

[0112] S 2. After the BMC detects the set error register, it records the downtime, notifies the ACD tool to collect status register information, and records the collection completion time.

[0113] S 3. BMC notifies the BAFI tool to parse faulty device information and error type information, and records the parsing completion time after the parsing is completed. When faulty device information is located, it records and notifies the user to collect fault diagnosis logs.

[0114] The method for optimizing the fault diagnosis log collection process provided by this invention enables the acquisition of accurate data at each stage of fault register information collection and parsing after a server crash. The BAFI tool can transmit the final parsing result to the BMC, enabling accurate and rapid location of the faulty device that caused the crash. It can also automatically prompt staff when the fault transfer file is parsed, and achieve separate collection of fault diagnosis logs without the need for full log collection from the BMC.

[0115] Example 2:

[0116] like Figure 2 As shown, the present invention provides a method for optimizing the fault diagnosis log collection process, comprising the following steps:

[0117] S1. The BMC pre-maintains a mapping file that establishes the mapping relationship between equipment asset information and status registers; the specific steps of step S1 are as follows:

[0118] S 11. Configure the BI OS to push the server's device asset information to the BMC after the POST is completed;

[0119] S 12. BMC maintains the mapping relationship between equipment asset information and status registers, and generates a mapping file;

[0120] S 13. BMC saves the mapping file to the specified directory; server equipment assets include memory and PCIe devices, and equipment asset information includes location information and BDF information;

[0121] S2. After the BMC detects the set error register, it records the downtime, notifies the ACD tool to collect status register information, and records the collection completion time; the specific steps of step S2 are as follows:

[0122] S 21. BMC checks whether the error register is set;

[0123] If so, proceed to step S22;

[0124] If not, return to step S 21;

[0125] S 22. BMC records the current time as the downtime;

[0126] S 23. The BMC notifies the ACD tool to collect all status register information;

[0127] S 24. BMC checks for the presence of faulty save files;

[0128] If so, proceed to step S25;

[0129] If not, return to step S24;

[0130] S 25. BMC determines that the ACD tool has completed collecting status register information and records the collection completion time; after the ACD tool completes collecting status register information, it automatically generates a fault transfer file;

[0131] S3. BMC notifies the BAFI tool to parse faulty device information and error type information, and records the parsing completion time after completion. When faulty device information is located, it records and notifies the user to collect fault diagnosis logs. The specific steps of step S3 are as follows:

[0132] S 31.BMC uses the optimized BAFI tool to parse the fault dump file and obtain faulty device information and error type information;

[0133] S 32. Determine whether the faulty device information is located in the fault transfer file;

[0134] If so, proceed to step S33;

[0135] If not, the BAFI tool will analyze the existing faults and generate a parsing and debugging file with empty key information, then the process will end.

[0136] S 33. BMC records the information in the fault diagnosis log and checks whether a parsing debug file exists;

[0137] If so, record the parsing completion time and proceed to step S34;

[0138] If not, return to step S33;

[0139] S 34. Notify users to collect fault diagnosis logs.

[0140] In some embodiments, the following steps are included before step S21:

[0141] When the business operating system crashes due to an internal error, the CPLD sets the error register.

[0142] Example 3:

[0143] like Figure 2 As shown, the present invention provides a method for optimizing the fault diagnosis log collection process, comprising the following steps:

[0144] S1. The BMC pre-maintains a mapping file that establishes the mapping relationship between equipment asset information and status registers; the specific steps of step S1 are as follows:

[0145] S 11. Configure the BI OS to push the server's device asset information to the BMC after the POST is completed;

[0146] S12. BMC maintains the mapping relationship between equipment asset information and status registers, and generates a mapping file;

[0147] S13.BMC saves the mapping file to the specified directory; server equipment assets include memory and PCIe devices, and equipment asset information includes location information and BDF information; BDF is a Binary Data File, which is created by a data analysis program to identify the health status of unused hard disk space, also known as logical volume status;

[0148] S2. After the BMC detects the set error register, it records the downtime, notifies the ACD tool to collect status register information, and records the collection completion time. The specific steps of step S2 are as follows:

[0149] S21. BMC checks whether the error register is set;

[0150] If so, proceed to step S22;

[0151] If not, return to step S21;

[0152] S22.BMC records the current time as the downtime;

[0153] S23. BMC notifies the ACD tool to collect all status register information;

[0154] S24.BMC checks for the presence of faulty save files;

[0155] If so, proceed to step S25;

[0156] If not, return to step S24;

[0157] S25. BMC determines that the ACD tool has completed the collection of status register information and records the collection completion time; after the ACD tool completes the collection of status register information, it automatically generates a fault dump file; after the ACD tool completes the collection of status register information, it automatically generates a fault dump file; it records the downtime and collection completion time to facilitate subsequent statistics on the time taken for each stage;

[0158] S3. BMC notifies the BAFI tool to parse faulty device information and error type information, records the parsing completion time after completion, and records and notifies the user to collect fault diagnosis logs when faulty device information is located; the specific steps of step S3 are as follows:

[0159] S 31.BMC uses the optimized BAFI tool to parse the fault dump file and obtain faulty device information and error type information;

[0160] S 32. Determine whether the faulty device information is located in the fault transfer file;

[0161] If so, proceed to step S33;

[0162] If not, the BAFI tool will analyze the existing faults and generate a parsing and debugging file with empty key information, then the process will end.

[0163] S 33. BMC records the information in the fault diagnosis log and checks whether a parsing debug file exists;

[0164] If so, record the parsing completion time and proceed to step S34;

[0165] If not, return to step S33;

[0166] like Figure 3 As shown, the specific steps of step S33 are as follows:

[0167] Add a fault diagnosis log register to S 331.BMC;

[0168] After completing the parsing of the fault dump file, the S 332.BAFI tool returns faulty device information and error type information to the BMC;

[0169] The S 333.BAFI tool generates and parses the debug file, sets the fault diagnosis log register, and triggers the SEL log collection.

[0170] S 334.BMC records faulty equipment information and error type information in the fault diagnosis log;

[0171] S 335.BMC checks if a parsing / debugging file exists;

[0172] If so, proceed to step S 336;

[0173] If not, return to step S 332;

[0174] S 336. BMC determines that the BAFI tool has completed the parsing of the fault transfer file, records the parsing completion time, and proceeds to step S34; During the parsing process, the BAFI tool returns the BDF and error type information of the faulty device to BMC. BMC parses the specific device location and error type based on the returned information and records them together in the IDL log. Finally, after the BAFI tool completes the parsing and generates the parsing debugging file, BMC records the parsing debugging file generation time, which is the parsing completion time.

[0175] S 34. Notify the user to collect fault diagnosis logs; such as Figure 4 As shown, the specific steps of step S34 are as follows:

[0176] S 341. The BAFI tool determines whether the time taken for the collection and parsing phases meets the user's requirements based on the recorded downtime, collection completion time, and parsing completion time.

[0177] If so, proceed to step S 343;

[0178] If not, proceed to step S 342;

[0179] S 342. The BAFI tool records the triggered timeout SEL log;

[0180] S 343. The BAFI tool determines whether the user has downloaded the fault diagnosis log;

[0181] If so, proceed to step S 344;

[0182] If not, return to step S 343;

[0183] The S 344.BAFI tool de-sets the fault diagnosis log register and removes the SEL log from log collection; the BMC adds a fault diagnosis log register, and after the BAFI tool finishes parsing, it sets the register and records the SEL log that triggers log collection, and provides users with a dedicated interface to download the fault diagnosis log. After the user finishes downloading, the register is de-set and the SEL log that removes log collection is recorded; if the customer has time requirements, the test determines whether the time taken for each stage meets the customer's requirements, and if not, records the SEL log that triggers timeout.

[0184] In some embodiments, the following steps are included before step S21:

[0185] When the business operating system crashes due to an internal error, the CPLD sets the error register; the BMC can determine that an internal server failure has occurred when it detects that the error register is set.

[0186] Example 4:

[0187] like Figure 5 As shown, the present invention provides an apparatus for optimizing the fault diagnosis log collection process, comprising:

[0188] The mapping file maintenance module is used to pre-maintain mapping files that map the relationship between equipment asset information and status registers in the BMC;

[0189] The information collection module is used to record the downtime after the BMC detects a set error register, notify the ACD tool to collect status register information, and record the collection completion time.

[0190] The information parsing and fault notification module is used to notify the BAFI tool to parse faulty device information and error type information in the BMC, record the parsing completion time after the parsing is completed, and record and notify the user to collect fault diagnosis logs when faulty device information is located.

[0191] The device provided by this invention optimizes the fault diagnosis log collection process, enabling the acquisition of accurate data at each stage of fault register information collection and parsing after a server crash. The BAFI tool can transmit the final parsing result to the BMC, enabling accurate and rapid location of the faulty device causing the crash. It can also automatically prompt staff when the fault transfer file is parsed, and achieve separate collection of fault diagnosis logs without the need for full log collection from the BMC.

[0192] Example 5:

[0193] like Figure 5 As shown, the present invention provides an apparatus for optimizing the fault diagnosis log collection process, comprising:

[0194] The mapping file maintenance module is used to pre-maintain mapping files between equipment asset information and status registers in the BMC; the mapping file maintenance module includes:

[0195] The device asset information push unit is used to configure BIOS to push the server's device asset information to BMC after POST is completed;

[0196] The mapping file generation unit is used to maintain the mapping relationship between equipment asset information and status registers in the BMC and generate mapping files;

[0197] The mapping file storage unit is used to save mapping files to a specified directory in the BMC;

[0198] The information collection module is used to record the downtime after the BMC detects a set error register, notify the ACD tool to collect status register information, and record the collection completion time. The information collection module includes:

[0199] The error register set detection unit is used to detect whether the error register is set in the BMC.

[0200] The downtime recording unit is used to record the current time as the downtime in the BMC when the error register is set;

[0201] The status register information collection unit is used to collect all status register information when the BMC notifies the ACD tool.

[0202] The fault save file existence detection unit is used to detect the existence of fault save files in the BMC.

[0203] The collection completion time recording unit is used to record the collection completion time when the BMC determines that the ACD tool has completed collecting status register information when there is a faulty transfer file.

[0204] The information parsing and fault notification module is used to notify the BAFI tool in the BMC to parse faulty device information and error type information, record the parsing completion time after completion, and record and notify the user to collect fault diagnosis logs when faulty device information is located. The information parsing and fault notification module includes:

[0205] The fault transfer file parsing unit is used in the BMC to parse the fault transfer file using the optimized BAFI tool to obtain fault device information and error type information;

[0206] The fault equipment information location and judgment unit is used to determine whether fault equipment information is located in the fault transfer file;

[0207] The debug file generation unit is used to parse the existing faults using the BAFI tool when the faulty device information cannot be located, and generate a debug file with empty key information, then ends.

[0208] The existence judgment unit for parsing debugging files is used to record faulty device information in the fault diagnosis log in the BMC when faulty device information is located, and to determine whether a parsing debugging file exists.

[0209] The parsing completion time recording unit is used to record the parsing completion time when a parsing debugging file exists;

[0210] The fault diagnosis log collection notification unit is used to notify users to collect fault diagnosis logs.

[0211] Example 6:

[0212] like Figure 5 As shown, the present invention provides an apparatus for optimizing the fault diagnosis log collection process, comprising:

[0213] The mapping file maintenance module is used to pre-maintain mapping files between equipment asset information and status registers in the BMC; the mapping file maintenance module includes:

[0214] The device asset information push unit is used to configure BIOS to push the server's device asset information to BMC after POST is completed;

[0215] The mapping file generation unit is used to maintain the mapping relationship between equipment asset information and status registers in the BMC and generate mapping files;

[0216] The mapping file storage unit is used to save mapping files to a specified directory in the BMC;

[0217] The information collection module is used to record the downtime after the BMC detects a set error register, notify the ACD tool to collect status register information, and record the collection completion time. The information collection module includes:

[0218] The error register set detection unit is used to detect whether the error register is set in the BMC.

[0219] The downtime recording unit is used to record the current time as the downtime in the BMC when the error register is set;

[0220] The status register information collection unit is used to collect all status register information when the BMC notifies the ACD tool.

[0221] The fault save file existence detection unit is used to detect the existence of fault save files in the BMC.

[0222] The collection completion time recording unit is used to record the collection completion time when the BMC determines that the ACD tool has completed collecting status register information when there is a faulty transfer file.

[0223] The information parsing and fault notification module is used to notify the BAFI tool in the BMC to parse faulty device information and error type information, record the parsing completion time after completion, and record and notify the user to collect fault diagnosis logs when faulty device information is located. The information parsing and fault notification module includes:

[0224] The fault transfer file parsing unit is used in the BMC to parse the fault transfer file using the optimized BAFI tool to obtain fault device information and error type information;

[0225] The fault equipment information location and judgment unit is used to determine whether fault equipment information is located in the fault transfer file;

[0226] The debug file generation unit is used to parse the existing faults using the BAFI tool when the faulty device information cannot be located, and generate a debug file with empty key information, then ends.

[0227] The existence determination unit for parsing debug files is used to record faulty device information in the fault diagnosis log of the BMC and determine whether a parsing debug file exists when the faulty device information is located. The existence determination unit for parsing debug files includes:

[0228] A sub-unit is added to the fault diagnosis log register to add a fault diagnosis log register to the BMC;

[0229] The parsing information return sub-unit is used to return fault device information and error type information to the BMC after the BAFI tool completes the parsing of the fault transfer file;

[0230] The fault register setting and log collection triggering subunit is used to generate and parse the debug file in the BAFI tool, set the fault diagnosis log register, and trigger the SEL log collection.

[0231] The fault diagnosis log recording subunit is used to record faulty device information and error type information into the fault diagnosis log in the BMC.

[0232] The parsing debug file existence check subunit is used to determine in the BMC whether a parsing debug file exists.

[0233] The parsing completion time recording subunit is used to record the parsing completion time when the BMC determines that the BAFI tool has completed parsing the fault transfer file when a parsing debugging file exists.

[0234] The parsing completion time recording unit is used to record the parsing completion time when a parsing debug file exists. During the parsing process, the BAFI tool returns the BDF and error type information of the faulty device to the BMC. The BMC parses the specific device location and error type based on the returned information and records them together in the IDL log. Finally, after the BAFI tool completes the parsing and generates the parsing debug file, the BMC records the parsing debug file generation time, which is the parsing completion time.

[0235] The fault diagnosis log collection notification unit is used to notify users to collect fault diagnosis logs; the fault diagnosis log collection notification unit includes:

[0236] The timing judgment subunit is used by the BAFI tool to determine whether the time taken during the collection and parsing phases meets the user's requirements based on the recorded downtime, collection completion time, and parsing completion time.

[0237] The timeout log recording trigger subunit is used to record a timeout SEL log in the BAFI tool when the time taken during the collection and parsing phases does not meet the user requirements.

[0238] The fault diagnosis log download waiting subunit is used to determine whether the user should download the fault diagnosis log when the time taken during the collection and parsing phases meets the user's requirements in the BAFI tool.

[0239] The log collection deactivation subunit is used to deactivate the fault diagnosis log register in the BAFI tool and deactivate the SEL log for log collection when the user completes the download of the fault diagnosis log. The BMC adds a fault diagnosis log register; after the BAFI tool finishes parsing, it sets this register and records the SEL log that triggered log collection, providing the user with a dedicated interface to download the fault diagnosis log. After the user completes the download, it deactivates the register and records the SEL log for deactivation. If the customer has time requirements, it checks whether the time taken for each stage meets the customer's requirements; if not, it records the SEL log for triggering a timeout.

[0240] Example 7:

[0241] This invention provides a terminal, including a processor and a memory;

[0242] The memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that the device performs the methods described in Embodiment 1, Embodiment 2 or Embodiment 3 above.

[0243] Example 8:

[0244] This invention provides a storage medium,

[0245] The storage medium stores instructions that, when run on a computer, cause the computer to perform the method described in any one of Embodiments 1, 2, or 3 above.

[0246] Although the present invention has been described in detail with reference to the accompanying drawings and preferred embodiments, the invention is not limited thereto. Various equivalent modifications or substitutions can be made to the embodiments of the invention by those skilled in the art without departing from the spirit and essence of the invention, and such modifications or substitutions should all be within the scope of the invention. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the invention should also be covered within the protection scope of the invention. Therefore, the protection scope of the invention should be determined by the scope of the claims.

Claims

1. A method for optimizing the fault diagnosis log collection process, characterized in that, The steps include the following: S1. The baseboard management controller pre-maintains a mapping file that maps equipment asset information to status registers; S2. After the baseboard management controller detects the set error register, it records the downtime, notifies the automatic fault dump tool to collect status register information, and records the collection completion time. The specific steps of step S2 are as follows: S21. The baseboard management controller checks whether the error register is set; If so, proceed to step S22; If not, return to step S21; S22. The baseboard management controller records the current time as the downtime; S23. The baseboard management controller notifies the automatic fault dump tool to collect all status register information; S24. The baseboard management controller checks for the existence of fault transfer files; If so, proceed to step S25; If not, return to step S24; S25. The baseboard management controller determines that the automatic fault dump tool has completed the collection of status register information and records the collection completion time. S3. The baseboard management controller notification file parsing tool parses faulty device information and error type information, records the parsing completion time after parsing, and records and notifies the user to collect fault diagnosis logs when faulty device information is located. The specific steps of step S3 are as follows: S31. The baseboard management controller parses the fault transfer file using an optimized file parsing tool to obtain faulty device information and error type information; S32. Determine whether faulty device information is located in the fault save file; If so, proceed to step S33; If not, the file parsing tool will analyze the existing faults and generate a parsing debugging file with empty key information, then end; S33. The baseboard management controller records the information in the fault diagnosis log and determines whether a parsing debugging file exists; If so, record the parsing completion time and proceed to step S34; If not, return to step S33; S34. Notify the user to collect fault diagnosis logs; The specific steps of step S34 are as follows: S341. The file parsing tool determines whether the time taken for the collection and parsing phases meets the user's requirements based on the recorded downtime, collection completion time, and parsing completion time. If so, proceed to step S343; If not, proceed to step S342; S342. The file parsing tool records system event logs that trigger timeouts; S343. The file parsing tool determines whether the user has downloaded the fault diagnosis log; If so, proceed to step S344; If not, return to step S343; S344. The file parsing tool removes the fault diagnosis log register from the set position and disables the system event log collection.

2. The method for optimizing the fault diagnosis log collection process as described in claim 1, characterized in that, The specific steps of step S1 are as follows: S11. Configure the basic input / output system to push the server's equipment asset information to the baseboard management controller after the power-on self-test is completed; S12. The baseboard management controller maintains the mapping relationship between equipment asset information and status registers, and generates a mapping file; S13. The substrate management controller saves the mapping file to the specified directory.

3. The method for optimizing the fault diagnosis log collection process as described in claim 1, characterized in that, The following steps are included before step S21: When the business operating system crashes due to an internal error, the complex programmable logic system sets the error register.

4. The method for optimizing the fault diagnosis log collection process as described in claim 1, characterized in that, The specific steps of step S33 are as follows: S331. Add a fault diagnosis log register to the baseboard management controller; S332. After completing the parsing of the fault transfer file, the file parsing tool returns faulty device information and error type information to the baseboard management controller; S333. The file parsing tool generates a parsing debug file, sets the fault diagnosis log register, and triggers the system event log collection. S334. The board management controller records faulty device information and error type information to the fault diagnosis log; S335. The baseboard management controller determines whether a parsing and debugging file exists; If so, proceed to step S336; If not, return to step S332; S336. The baseboard management controller determines that the file parsing tool has completed the parsing of the fault transfer file, recorded the parsing completion time, and proceeds to step S34.

5. An apparatus for optimizing the fault diagnosis log collection process, comprising performing the method according to any one of claims 1-4, characterized in that, include: The mapping file maintenance module is used to pre-maintain mapping files that map the relationship between equipment asset information and status registers in the baseboard management controller; The information collection module is used to record the downtime after the baseboard management controller detects the set error register, notify the automatic fault dump tool to collect status register information, and record the collection completion time. The information parsing and fault notification module is used to parse faulty device information and error type information in the notification file parsing tool of the baseboard management controller, record the parsing completion time after the parsing is completed, and record and notify the user to collect fault diagnosis logs when faulty device information is located.

6. A terminal, characterized in that, Including processor and memory; The memory is used to store a computer program, and the processor is used to retrieve and run the computer program from the memory, causing the device to perform the method described in any one of claims 1-4.

7. A storage medium, characterized in that, The storage medium stores instructions that, when run on a computer, cause the computer to perform the method described in any one of claims 1-4.

Images