A hardware consistency checking method, system, device and medium of a server

Abstract

This invention discloses a method, system, device, and medium for checking server hardware consistency. The method includes: configuring a hardware configuration list for the server; obtaining the server to be checked and setting up its network environment, and generating a node list based on the server to be checked and its corresponding hardware configuration list; sequentially performing hardware consistency checks on the servers in the node list according to a pre-configured check file, recording check logs, and generating check results. Through this invention, hardware consistency checks can be automatically performed on servers in a network environment, significantly reducing repetitive work, lowering manpower requirements, and improving the efficiency of server hardware consistency checks.

Description

Technical Field

[0001] This invention relates to the field of computer information technology, and in particular to a method, system, device, and medium for checking the hardware consistency of a server. Background Technology

[0002] With the rise of new technologies such as 5G, cloud computing, and the Internet of Things, global IP traffic is growing at a considerable rate. This surge in traffic means a surge in data volume, requiring a large number of servers to support it, thus driving continuous growth in server demand. The explosion of data and traffic is an inevitable result of the current information revolution, and the construction of 5G will continue to drive data volume and thus increase server demand. The basic performance of a server is determined by its hardware, and the large demand for servers also places demands on server hardware.

[0003] Server hardware consists of several components, including power supply, CPU, memory, hard drive, fan, and network interface card (NIC). Hard drives can be further divided into SAS hard drives, SATA hard drives, and solid-state drives (SSDs), while NICs can be categorized by interface, such as RJ-45 NICs and FDDI NICs. These are the differences in hardware device classification for servers. In terms of quantity, a server may have two or more CPUs, one or dozens of memory modules, a dozen or dozens of hard drives, and so on. Server hardware is a very complex hardware system. However, server hardware consistency includes not only these hardware devices but also several firmware components and information such as the actual operating status, link, and bandwidth. Therefore, checking hardware consistency before mass production or deployment of servers is essential, but also a very tedious task. The current method of checking server hardware consistency involves manually performing consistency checks on each server, which is highly repetitive and tedious. Summary of the Invention

[0004] In view of this, the present invention proposes a hardware consistency check method, system, computer device and computer-readable storage medium for servers, which automatically performs hardware consistency checks on different hardware configurations of multiple servers in the same network environment, which can significantly reduce repetitive work, reduce the amount of manpower required, and improve the efficiency of server hardware consistency checks.

[0005] To achieve the above objectives, one aspect of the present invention provides a hardware consistency check method for a server, specifically including the following steps:

[0006] Configure the server's hardware configuration list;

[0007] Obtain the server to be inspected and configure its network environment. Generate a node list based on the server to be inspected and its corresponding hardware configuration list.

[0008] Hardware consistency checks are performed on the servers in the node list sequentially according to the pre-configured check file, and check logs are recorded and check results are generated.

[0009] In some implementations, hardware consistency checks are performed on the servers in the node list sequentially according to a pre-configured check file, and check logs are recorded and check results are generated, including:

[0010] Read the node list and log in to the first server on the node list;

[0011] Create a new folder on the server, and upload the pre-configured check file as a compressed package to the folder;

[0012] Unzip the compressed package and execute the pre-configured check file to perform a hardware consistency check on the server;

[0013] In response to the completion of the server check, the server's check log and check results are obtained, and the check log and check results are generated into a compressed package and sent back to the remote server.

[0014] Read the node list, log in to the next server to perform a consistency check, and return to the step of creating a new folder on the server, until all servers in the node list have been checked.

[0015] In some implementations, the node list includes: server IP, username, login password, and corresponding hardware configuration list.

[0016] In some implementations, logging into the first server on the node list includes:

[0017] Link to the first server IP on the node list, and remotely log in to the server using the username and password.

[0018] In some implementations, the hardware configuration list includes checking expected results;

[0019] After decompressing the compressed package, performing a hardware consistency check on the server using the pre-configured check file includes:

[0020] Read the hardware configuration list of the server and check each piece of hardware of the server according to the hardware configuration list;

[0021] The inspection results are compared with the expected inspection results. If the comparison results are consistent, the inspection item is passed; otherwise, the inspection item is not passed.

[0022] The test results of the hardware are summarized to generate the final inspection results of the server.

[0023] In some implementations, the hardware configuration list also includes hardware check item names and check commands;

[0024] The method further includes:

[0025] The name of the hardware inspection item, the inspection command, the expected inspection result, the inspection result, and whether the inspection passed are recorded in the inspection log.

[0026] In some implementations, the method further includes:

[0027] Filter the information of failed inspection items from the inspection log and record the information of the failed inspection items in the server log.

[0028] Another aspect of this invention provides a hardware consistency check system for a server, the check system comprising:

[0029] A configuration module, wherein the configuration module is configured to configure the hardware configuration list of the server;

[0030] The generation module is configured to acquire the server to be inspected, set the network environment of the server to be inspected, and generate a node list based on the server to be inspected and the hardware configuration list corresponding to the server to be inspected.

[0031] The inspection module is configured to perform hardware consistency checks on the servers in the node list sequentially according to a pre-configured inspection file, record inspection logs, and generate inspection results.

[0032] In another aspect of the present invention, a computer device is provided, comprising: at least one processor; and a memory storing a computer program executable on the processor, the computer program performing the steps of the method described above when executed by the processor.

[0033] In another aspect, the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method steps.

[0034] The present invention has the following beneficial technical effects: by configuring a hardware list for the server and generating a node list of the server to be checked based on the server to be checked and its corresponding hardware list, and automatically performing hardware consistency checks on multiple servers with different configurations based on a pre-configured check file, it can significantly reduce repetitive work, reduce the amount of manpower required, and improve the efficiency of server hardware consistency checks. Attached Figure Description

[0035] 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, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0036] Figure 1 A block diagram of an embodiment of the server hardware consistency check method provided by the present invention;

[0037] Figure 2 A schematic diagram of an embodiment of the server hardware consistency check system provided by the present invention;

[0038] Figure 3 A schematic diagram of the structure of an embodiment of the computer device provided by the present invention;

[0039] Figure 4 This is a schematic diagram of an embodiment of the computer-readable storage medium provided by the present invention. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings.

[0041] It should be noted that all uses of "first" and "second" in the embodiments of the present invention are for the purpose of distinguishing two entities or parameters with the same name but different names. It is clear that "first" and "second" are only for the convenience of expression and should not be construed as limiting the embodiments of the present invention. Subsequent embodiments will not explain this in detail.

[0042] Based on the above objectives, a first aspect of the present invention provides an embodiment of a server hardware consistency check method. For example... Figure 1 As shown, it includes the following steps:

[0043] Step S101: Configure the hardware configuration list of the server;

[0044] Step S103: Obtain the server to be inspected and set the network environment of the server to be inspected, and generate a node list based on the server to be inspected and the hardware configuration list corresponding to the server to be inspected.

[0045] Step S105: Perform hardware consistency checks on the servers in the node list sequentially according to the pre-configured check file, record the check logs, and generate the check results.

[0046] Depending on the usage environment, the types and quantities of hardware installed on the server will vary. Multiple hardware configuration lists should be configured according to the types of hardware installed on the server. The specific contents of the hardware configuration list can include the name of the hardware check item, the check command, and the expected check results. The hardware configuration list should be saved in a pre-designed format.

[0047] Obtain all servers to be inspected, add them to the same network segment, configure the network environment of the servers, generate a node list based on all servers to be inspected and their corresponding hardware configuration lists, and save the node list in a pre-set format.

[0048] Based on a pre-configured check file, such as a check script or batch file, each server on the node list is read sequentially. A consistency check is performed on the hardware of each server, mainly checking whether the server's hardware information is consistent with the check information pre-configured in the check script or batch file. If they are consistent, the check passes; if they are inconsistent, the check fails. The check process and the check results of each piece of hardware are recorded in the log, and the check results of each server are generated. The check results of each server are then summarized and sent to the remote server.

[0049] Optionally, auxiliary devices such as computers used for auxiliary server checks can be added to the same network segment and their network environment can be configured. The hardware configuration list of the auxiliary devices can be pre-configured, and the auxiliary devices can perform consistency checks by executing the check file.

[0050] By configuring a hardware manifest for the server and generating a node list of the server to be checked based on the server to be checked and its corresponding hardware manifest, and automatically performing hardware consistency checks on multiple servers with different configurations based on a pre-configured check file, repetitive work can be significantly reduced, manpower input can be reduced, and the efficiency of server hardware consistency checks can be improved.

[0051] In some implementations, hardware consistency checks are performed on the servers in the node list sequentially according to a pre-configured check file, and check logs are recorded and check results are generated, including:

[0052] Read the node list and log in to the first server on the node list;

[0053] Create a new folder on the server, and upload the pre-configured check file as a compressed package to the folder;

[0054] Unzip the compressed package and execute the pre-configured check file to perform a hardware consistency check on the server;

[0055] In response to the completion of the server check, the server's check log and check results are obtained, and the check log and check results are generated into a compressed package and sent back to the remote server.

[0056] Read the node list, log in to the next server to perform a consistency check, and return to the step of creating a new folder on the server, until all servers in the node list have been checked.

[0057] Read the node list, remotely log in to the first server on the node list (e.g., via SSH), and check the servers on the node list one by one, starting from the first server and stopping at the last server.

[0058] The specific inspection process involves packaging the pre-configured inspection files into a compressed package on the remote server and sending it to a designated folder on the server being inspected. The compressed package is then decompressed in the designated folder to execute the inspection files. After the inspection is completed, the inspection results are compressed and sent back from the server being inspected to the remote server.

[0059] By reading the node list, hardware consistency checks are automatically performed on multiple servers on the node list based on a pre-configured check file, which improves the efficiency of server hardware consistency checks.

[0060] In some implementations, the node list includes: server IP, username, login password, and corresponding hardware configuration list.

[0061] In some implementations, logging into the first server on the node list includes:

[0062] Link to the first server IP on the node list, and remotely log in to the server using the username and password.

[0063] In some implementations, the hardware configuration list includes checking expected results;

[0064] After decompressing the compressed package, performing a hardware consistency check on the server using the pre-configured check file includes:

[0065] Read the hardware configuration list of the server and check each piece of hardware of the server according to the hardware configuration list;

[0066] The inspection results are compared with the expected inspection results. If the comparison results are consistent, the inspection item is passed; otherwise, the inspection item is not passed.

[0067] The test results of the hardware are summarized to generate the final inspection results of the server.

[0068] Specifically, the system reads the hardware configuration list corresponding to the server being inspected, and checks each piece of hardware on the server according to the hardware configuration list. The hardware configuration list contains multiple inspection items for all hardware of the server. For each inspection, the inspection result is compared with the expected result. If the comparison result is consistent, the inspection passes; otherwise, the inspection fails. The inspection process and the inspection result of each piece of hardware are recorded in the log, and a final output result is generated after all hardware of the server has been inspected. Optionally, the final output result includes whether each piece of hardware passed or failed. The inspection results of the hardware are summarized to generate the final inspection result of the server.

[0069] Optionally, the check items can include whether the server is missing a certain hardware component, such as a hard drive not being properly connected, resulting in the hard drive information not being detected; the check items can also include whether the motherboard model matches the preset parameters, which are the motherboard models pre-configured in the check file; the check items can also include whether the number of memory modules is correct and whether the memory module models match the preset parameters; the check items can also include CPU information such as the CPU model, the actual number of physical CPUs in the system, and the number of cores in each physical CPU; corresponding check items can also include server hardware information such as hard drive information, network card information, and all PCI device information.

[0070] By reading the hardware configuration list of the server being inspected, and checking each piece of hardware on the server according to the hardware configuration list, the efficiency of checking server hardware consistency is improved.

[0071] In some implementations, the hardware configuration list also includes hardware check item names and check commands;

[0072] The method further includes:

[0073] The name of the hardware inspection item, the inspection command, the expected inspection result, the inspection result, and whether the inspection passed are recorded in the inspection log.

[0074] In some implementations, the method further includes:

[0075] Filter the information of failed inspection items from the inspection log and record the information of the failed inspection items in the server log.

[0076] Based on the same inventive concept, according to another aspect of the present invention, such as Figure 2 As shown, embodiments of the present invention also provide a server hardware consistency check system, the check system comprising:

[0077] Configuration module 110, configured to configure the hardware configuration list of the server;

[0078] The generation module 120 is configured to acquire the server to be inspected and set the network environment of the server to be inspected, and generate a node list based on the server to be inspected and the hardware configuration list corresponding to the server to be inspected.

[0079] The inspection module 130 is configured to perform hardware consistency checks on the servers on the node list sequentially according to a pre-configured inspection file, record inspection logs, and generate inspection results.

[0080] By configuring a hardware manifest for the server and generating a node list of the server to be checked based on the server to be checked and its corresponding hardware manifest, and automatically performing hardware consistency checks on multiple servers with different configurations based on a pre-configured check file, repetitive work can be significantly reduced, manpower input can be reduced, and the efficiency of server hardware consistency checks can be improved.

[0081] Based on the same inventive concept, according to another aspect of the present invention, such as Figure 3 As shown, an embodiment of the present invention also provides a computer device 20, which includes a processor 210 and a memory 220. The memory 220 stores a computer program 221 that can be run on the processor. When the processor 210 executes the program, it performs the following steps:

[0082] Configure the server's hardware configuration list;

[0083] Obtain the server to be inspected and configure its network environment. Generate a node list based on the server to be inspected and its corresponding hardware configuration list.

[0084] Hardware consistency checks are performed on the servers in the node list sequentially according to the pre-configured check file, and check logs are recorded and check results are generated.

[0085] By configuring a hardware manifest for the server and generating a node list of the server to be checked based on the server to be checked and its corresponding hardware manifest, and automatically performing hardware consistency checks on multiple servers with different configurations based on a pre-configured check file, repetitive work can be significantly reduced, manpower input can be reduced, and the efficiency of server hardware consistency checks can be improved.

[0086] In some implementations, hardware consistency checks are performed on the servers in the node list sequentially according to a pre-configured check file, and check logs are recorded and check results are generated, including:

[0087] Read the node list and log in to the first server on the node list;

[0088] Create a new folder on the server, and upload the pre-configured check file as a compressed package to the folder;

[0089] Unzip the compressed package and execute the pre-configured check file to perform a hardware consistency check on the server;

[0090] In response to the completion of the server check, the server's check log and check results are obtained, and the check log and check results are generated into a compressed package and sent back to the remote server.

[0091] Read the node list, log in to the next server to perform a consistency check, and return to the step of creating a new folder on the server, until all servers in the node list have been checked.

[0092] In some implementations, the node list includes: server IP, username, login password, and corresponding hardware configuration list.

[0093] In some implementations, logging into the first server on the node list includes:

[0094] Link to the first server IP on the node list, and remotely log in to the server using the username and password.

[0095] In some implementations, the hardware configuration list includes checking expected results;

[0096] After decompressing the compressed package, performing a hardware consistency check on the server using the pre-configured check file includes:

[0097] Read the hardware configuration list of the server and check each piece of hardware of the server according to the hardware configuration list;

[0098] The inspection results are compared with the expected inspection results. If the comparison results are consistent, the inspection item is passed; otherwise, the inspection item is not passed.

[0099] The test results of the hardware are summarized to generate the final inspection results of the server.

[0100] In some implementations, the hardware configuration list also includes hardware check item names and check commands;

[0101] The method further includes:

[0102] The name of the hardware inspection item, the inspection command, the expected inspection result, the inspection result, and whether the inspection passed are recorded in the inspection log.

[0103] In some implementations, the method further includes:

[0104] Filter the information of failed inspection items from the inspection log and record the information of the failed inspection items in the server log.

[0105] Based on the same inventive concept, according to another aspect of the present invention, such as Figure 4 As shown, embodiments of the present invention also provide a computer-readable storage medium 30, which stores a computer program 310 that, when executed by a processor, performs the hardware consistency check method for a server as described in the embodiments of this application.

[0106] The memory, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the server hardware conformance check method described in the embodiments of this application. The processor executes various functional applications and data processing of the device by running the non-volatile software programs, instructions, and modules stored in the memory, i.e., the server hardware conformance check method described in the embodiments of this application.

[0107] The memory may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the device, etc. Furthermore, the memory may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory may optionally include memory remotely located relative to the processor, which can be connected to the local module via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0108] The specific steps of the computer program executing the server hardware consistency check method in this embodiment are as follows:

[0109] Configure the server's hardware configuration list;

[0110] Obtain the server to be inspected and configure its network environment. Generate a node list based on the server to be inspected and its corresponding hardware configuration list.

[0111] Hardware consistency checks are performed on the servers in the node list sequentially according to the pre-configured check file, and check logs are recorded and check results are generated.

[0112] In some implementations, hardware consistency checks are performed on the servers in the node list sequentially according to a pre-configured check file, and check logs are recorded and check results are generated, including:

[0113] Read the node list and log in to the first server on the node list;

[0114] Create a new folder on the server, and upload the pre-configured check file as a compressed package to the folder;

[0115] Unzip the compressed package and execute the pre-configured check file to perform a hardware consistency check on the server;

[0116] In response to the completion of the server check, the server's check log and check results are obtained, and the check log and check results are generated into a compressed package and sent back to the remote server.

[0117] Read the node list, log in to the next server to perform a consistency check, and return to the step of creating a new folder on the server, until all servers in the node list have been checked.

[0118] In some implementations, the node list includes: server IP, username, login password, and corresponding hardware configuration list.

[0119] In some implementations, logging into the first server on the node list includes:

[0120] Link to the first server IP on the node list, and remotely log in to the server using the username and password.

[0121] In some implementations, the hardware configuration list includes checking expected results;

[0122] After decompressing the compressed package, performing a hardware consistency check on the server using the pre-configured check file includes:

[0123] Read the hardware configuration list of the server and check each piece of hardware of the server according to the hardware configuration list;

[0124] The inspection results are compared with the expected inspection results. If the comparison results are consistent, the inspection item is passed; otherwise, the inspection item is not passed.

[0125] The test results of the hardware are summarized to generate the final inspection results of the server.

[0126] In some implementations, the hardware configuration list also includes hardware check item names and check commands;

[0127] The method further includes:

[0128] The name of the hardware inspection item, the inspection command, the expected inspection result, the inspection result, and whether the inspection passed are recorded in the inspection log.

[0129] In some implementations, the method further includes:

[0130] Filter the information of failed inspection items from the inspection log and record the information of the failed inspection items in the server log.

[0131] Finally, it should be noted that those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The storage medium for the program can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. The above computer program embodiments can achieve the same or similar effects as any of the corresponding foregoing method embodiments.

[0132] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of various illustrative components, blocks, modules, circuits, and steps has been generally described. Whether this functionality is implemented as software or as hardware depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the functionality in various ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the embodiments disclosed herein.

[0133] The above are exemplary embodiments disclosed in this invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments of this invention as defined by the claims. The functions, steps, and / or actions of the methods according to the disclosed embodiments described herein do not need to be performed in any particular order. Furthermore, although the elements disclosed in the embodiments of this invention may be described or claimed individually, they may be understood as multiple unless explicitly limited to a singular number.

[0134] It should be understood that, as used herein, the singular form “a” is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, “and / or” refers to any and all possible combinations of one or more of the associated listed items.

[0135] The embodiment numbers disclosed in the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0136] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0137] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A method for checking the hardware consistency of a server, characterized in that, include: Configure the server's hardware configuration list; Obtain the server to be inspected and configure its network environment. Generate a node list based on the server to be inspected and its corresponding hardware configuration list. The node list includes the hardware configuration list. Based on the hardware consistency check steps, hardware consistency checks are performed on the servers in the node list in sequence, check logs are recorded and check results are generated. The hardware consistency check step includes: reading the node list and logging into the first server on the node list; creating a new folder on the server and uploading a pre-configured check file generated as a compressed package to the folder; decompressing the compressed package to obtain the pre-configured check file; executing the pre-configured check file to read the hardware configuration list of the server from the node list and perform consistency checks on each piece of hardware on the server according to the hardware configuration list; in response to the server check completion, obtaining the server's check log and check results and generating a compressed package of the check log and check results to send back to the remote server; returning to the step of reading the node list to perform consistency checks on the next server in the node list, until all servers in the node list have been checked; The inspection items include whether the server is missing any hardware, whether the motherboard model matches the pre-configured motherboard model in the inspection file, whether the number of memory modules is correct, whether the memory module model matches the preset parameters, CPU information, hard drive information, network card information, and information on all PCI devices. The CPU information includes the CPU model, the actual number of physical CPUs in the system, and the number of cores in each physical CPU.

2. The method according to claim 1, characterized in that, The node list also includes: server IP, username, and login password.

3. The method according to claim 2, characterized in that, Log in to the first server on the node list, including: Link to the first server IP on the node list, and remotely log in to the server using the username and password.

4. The method according to claim 1, characterized in that, The hardware configuration list includes the expected results of the check; Reading the hardware configuration list of the server from the node list and performing consistency checks on each piece of hardware of the server based on the hardware configuration list includes: Read the hardware configuration list of the server and check each piece of hardware of the server according to the hardware configuration list; The inspection results are compared with the expected inspection results. If the comparison results are consistent, the inspection item is passed; otherwise, the inspection item is not passed. The test results of the hardware are summarized to generate the final inspection results of the server.

5. The method according to claim 4, characterized in that, The hardware configuration list also includes hardware check item names and check commands; the method further includes: The name of the hardware inspection item, the inspection command, the expected inspection result, the inspection result, and whether the inspection passed are recorded in the inspection log.

6. The method according to claim 5, characterized in that, Further includes: Filter the information of failed inspection items from the inspection log and record the information of the failed inspection items in the server log.

7. A hardware consistency check system for a server, characterized in that, include: A configuration module, wherein the configuration module is configured to configure the hardware configuration list of the server; The generation module is configured to obtain the server to be inspected and set the network environment of the server to be inspected, and generate a node list based on the server to be inspected and the hardware configuration list corresponding to the server to be inspected. The node list includes server IP, username, login password and corresponding hardware configuration list. The inspection module is configured to perform hardware consistency checks on servers in the node list sequentially according to a pre-configured inspection file based on a hardware consistency check step, record inspection logs, and generate inspection results. The hardware consistency check step includes: reading the node list and logging into the first server in the node list; creating a new folder on the server and uploading a compressed package of the pre-configured inspection file to the folder; decompressing the compressed package to obtain the pre-configured inspection file; executing the pre-configured inspection file to read the hardware configuration list of the server from the node list and perform consistency checks on each piece of hardware on the server according to the hardware configuration list; in response to the completion of the server inspection, obtaining the server's inspection logs and inspection results and sending the compressed package containing the inspection logs and inspection results back to the remote server; returning to the step of reading the server IP, username, and login password of the first server in the node list to perform consistency checks on the next server in the node list, until all servers in the node list have been checked. The inspection items include whether the server is missing any hardware, whether the motherboard model matches the pre-configured motherboard model in the inspection file, whether the number of memory modules is correct, whether the memory module model matches the preset parameters, CPU information, hard drive information, network card information, and information on all PCI devices. The CPU information includes the CPU model, the actual number of physical CPUs in the system, and the number of cores in each physical CPU.

8. A computer device, comprising: At least one processor; as well as A memory storing a computer program executable on the processor, characterized in that the processor executes the steps of the method as described in any one of claims 1-6 when executing the program.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it performs the steps of the method as described in any one of claims 1-6.

Images