A server and component collaboration testing method, device, equipment and medium

Abstract

The present invention provides a server-component collaborative testing method, device, equipment, and medium, belonging to the field of server testing technology. The method comprises the following steps: pre-binding a fixed IP address to the server end, establishing a binding relationship between the test machine where the intelligent network card is located and the server end; selecting one of the bound test machines and the server end as the master test end and the other as the slave test end, and setting a dependency flag according to the dependency relationship between the master test end and the slave test end; after the master test end performs a board scan after starting the test, it interacts with the slave test end through the dependency flag, and after the test is completed, collects the slave test end logs, performs log merging, and displays the logs. The present invention reduces the cost of test tooling, realizes automated control of the test process, saves test time, achieves the effect of centralized display of test results, avoids misunderstandings caused by inconsistent test result displays on both the server and component ends, and ensures the convenience and accuracy of the test process.

Description

Technical Field

[0001] The present invention belongs to the technical field of server testing, and in particular relates to a method, device, equipment and medium for testing collaboration between a server and components. Background Art

[0002] The increase in data center network transmission speed, which currently represents the development of network technology, has led to a relatively lagging growth in CPU computing power. Moreover, under high bandwidth and new transmission systems, network function processing is becoming increasingly complex. Therefore, as network interface bandwidth increases, executing complex network functions places an unbearable load on current CPU resources, leaving little or no CPU resources for running applications. Smart NICs are therefore applied in this form.

[0003] Compared with the fixed-function traffic processing of traditional network cards that cannot adapt to the requirements of SDN, cloud and virtualization deployment, the introduction of smart network cards on the server side can offload high-performance data processing functions in the network, storage and operating system that are not suitable for CPU processing to hardware execution, thereby improving data processing capabilities and releasing CPU computing power.

[0004] Smart NICs, critical server components, must undergo full functional testing after PCBA production. Smart NIC functional testing primarily involves two aspects: internal Smart NIC functionality testing and server-side Smart NIC functionality testing. These two aspects of testing can impact each other, requiring strict testing sequencing.

[0005] Currently, server-side functional testing of smart network cards involves running test programs separately on both ends. When one end relies on the completion of a functional item test on the other end, a pop-up window is used to wait. After the other end's functional item test is completed, the operator is notified that the preceding test item has completed, and then the operator can press the pop-up button to continue execution. This method requires a display and scanner on both the server and the smart network card, which is costly. Furthermore, the need for board scanning on both ends increases testing time and the chance of error. Furthermore, the pop-up window method requires manual control by the tester, resulting in time loss and low testing efficiency. To ensure log integrity, both test ends must continuously confirm whether the other end's logs have been uploaded, increasing network pressure on the network production line.

[0006] Therefore, in view of the above-mentioned defects, it is very necessary to provide a method, device, equipment and medium for testing the collaboration between servers and components. Summary of the Invention

[0007] In view of the above-mentioned defects that the current interaction test between the smart network card and the server side requires the configuration of two sets of displays and scanners for scanning, which is costly, takes a long time to test, has low efficiency in the pop-up window interaction method, requires interactive confirmation of log upload, and increases network pressure, the present invention provides a testing method, device, equipment and medium for the collaboration between servers and components to solve the above-mentioned technical problems.

[0008] In a first aspect, the present invention provides a method for testing collaboration between a server and a component, comprising the following steps:

[0009] S1. Pre-bind a fixed IP address to the server and establish a binding relationship between the test machine where the smart network card is located and the server.

[0010] S2. Select one of the bound test machine and server as the master test end and another as the slave test end, and set the dependency flag according to the dependency relationship between the master test end and the slave test end;

[0011] S3. After starting the test and scanning the boards, the master test end interacts with the slave test end through the dependency flag. After the test is completed, the slave test end logs are collected, merged, and displayed.

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

[0013] S11. Bind the server-side network card to a fixed IP address on the DHCP server on the production line.

[0014] S12. Bind the test machine number to the fixed IP address of the server network card to form a binding file;

[0015] S13. Install the smart network card on the test machine.

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

[0017] S111. Obtain the number of server-side network cards to be tested as a test fixture;

[0018] S112. Bind each server-side network card to a fixed IP address on the DHCP server.

[0019] Furthermore, the specific steps of step S12 are as follows:

[0020] S121. Assign a test machine to each server to be tested;

[0021] S122. Bind the test machine number and the fixed IP address of the server network card according to the correspondence between the server to be tested and the test machine, and generate a binding file.

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

[0023] S21. Select the test machine where the smart network card is located as the main test end, and select the server end with which the test machine is bound as the slave test end;

[0024] S22. Determine the respective dependencies based on the dependency relationship between the server and the intelligent network card test machine, and set a dependency flag for the server on the test machine.

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

[0026] S31. After the test machine is powered on, the server and the test machine where the smart network card is located begin testing in parallel;

[0027] S32. The server executes the test items in order, and when executing the server-side dependency items, it queries whether the dependency flag of the test machine where the smart network card is located is set;

[0028] If yes, go to step S34;

[0029] If not, return to step S32;

[0030] S33. After the intelligent NIC end scans the test machine, the test items are executed in order. At the same time, when the intelligent NIC end dependency item is executed, the test machine will be dependent on the flag position, and the process proceeds to step S35.

[0031] S34. The server continues to execute the remaining test items and returns the log to the Smart NIC after the server test is completed.

[0032] S35. After the Smart NIC completes the test, check whether the server log is returned.

[0033] If yes, go to step S36;

[0034] If not, return to step S35;

[0035] S36. The Smart NIC merges its own test log with the log sent back by the server and displays the test results.

[0036] Furthermore, the specific steps of step S33 are as follows:

[0037] S331. The intelligent network card scans the test machine and obtains the test machine number;

[0038] S332. The Smart NIC executes the test items in sequence. When executing the Smart NIC-side dependency item, it obtains the binding file and searches the binding file for the fixed IP address of the server-side NIC based on the test machine number. It sets the dependency flag for the server and provides the scanned test machine number to the server.

[0039] In step S32, the server side queries whether the dependency flag provided by the corresponding station number tester is set.

[0040] In a second aspect, the present invention provides a server and component collaboration testing device, comprising:

[0041] The server-to-test machine binding module is used to pre-bind a fixed IP address to the server and establish a binding relationship between the test machine where the smart network card is located and the server.

[0042] The master-slave test terminal setting module is used to select one of the bound test machine and server as the master test terminal and the other as the slave test terminal, and set the dependency flag according to the dependency relationship between the master test terminal and the slave test terminal;

[0043] The master-slave test end interaction test module is used for the master test end to perform board scanning after starting the test, and then interact with the slave test end through the dependency flag bit. After the test is completed, the slave test end logs are collected, merged, and displayed.

[0044] Furthermore, the server-side and test machine binding module includes:

[0045] The server-side IP binding unit is used to bind the server-side network card to a fixed IP address at the Dynamic Host Configuration Protocol server on the production line;

[0046] The test machine and server binding unit is used to bind the test machine number with the fixed IP of the server network card to form a binding file;

[0047] The smart network card installation unit is used to install the smart network card on the test machine.

[0048] Furthermore, the server-side IP binding unit includes:

[0049] The server number acquisition subunit to be tested is used to obtain the number of network cards of the server to be tested as a test fixture;

[0050] The IP binding subunit of the network card of the server to be tested is used to bind the network card of each server to be tested to a fixed IP address on the dynamic host configuration protocol server.

[0051] Furthermore, the test machine and server binding unit includes:

[0052] The test machine designation subunit is used to designate a test machine for each server to be tested;

[0053] The binding file generation subunit is used to bind the test machine number and the fixed IP of the server network card according to the corresponding relationship between the server to be tested and the test machine, and generate a binding file.

[0054] Furthermore, the master-slave measurement terminal setting module includes:

[0055] The master test end and slave test end selection unit is used to select the test machine where the intelligent network card is located as the master test end, and select the server end that has a binding relationship with the test machine as the slave test end;

[0056] The dependency item determination and flag setting unit is used to determine the respective dependencies of the server side and the intelligent network card side test machine according to the dependency relationship, and set the dependency flag for the server side at the test machine.

[0057] Furthermore, the master-slave test end interaction test module includes:

[0058] The parallel testing unit is used to start testing the server and the test machine where the smart network card is located in parallel after the test machine is powered on;

[0059] The server-side test unit is used to execute test items in sequence and, when executing a server-side dependency item, query whether the dependency flag of the test machine where the smart network card is located is set;

[0060] The intelligent network card test unit is used to scan the test machine and execute the test items in order. When executing the intelligent network card dependency item, it sets the test machine dependency flag.

[0061] The server-side return log unit is used to query the dependency flag of the test machine where the smart network card is located, continue to execute the remaining test items, and return the log to the smart network card after the server-side test is completed;

[0062] The smart network card log checking unit is used to check whether the server-side log is returned after the test is completed;

[0063] The smart network card log merging unit is used to check the server-side log return, merge its own test log with the server-side return log, and display the test results.

[0064] Furthermore, the intelligent network card end test unit includes:

[0065] Scan test machine number subunit, used to scan the test machine and obtain the test machine number;

[0066] The test execution and dependency flag position sub-unit is used to execute the test items in sequence, and when executing the smart network card dependency item, obtain the binding file, and search the fixed IP of the corresponding server-side network card from the binding file according to the test machine number, set the dependency flag for the server side, and provide the scanned test machine number to the server side.

[0067] In a third aspect, the present invention provides a device,

[0068] including processor and memory;

[0069] The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device executes the method described in the first aspect above.

[0070] In a fourth aspect, the present invention provides a storage medium,

[0071] The storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method described in the first aspect.

[0072] The beneficial effects of the present invention are:

[0073] The server and component collaboration testing method, device, equipment and medium provided by the present invention replace the multiple scanning test scheme through the collaborative testing of the server and the smart network card as a component, eliminating the need for two sets of displays, keyboards and scanners, and reducing the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0074] In addition, the present invention has a reliable design principle, a simple structure and a very broad application prospect.

[0075] It can be seen that compared with the prior art, the present invention has outstanding substantial features and significant progress, and the beneficial effects of its implementation are also obvious. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0077] Figure 1 This is a flow chart of Example 1 of the server and component collaboration testing method of the present invention.

[0078] Figure 2 This is a flow chart of Example 2 of the server and component collaboration testing method of the present invention.

[0079] Figure 3 It is a schematic diagram of the binding process between the test machine and the server of the present invention.

[0080] Figure 4 This is a flow chart of setting a dependency flag on the intelligent network card side of the present invention.

[0081] Figure 5 It is a schematic diagram of a testing device for collaboration between a server and components of the present invention.

[0082] In the figure, 1-server-side and test machine binding module; 1.1-server-side IP binding unit; 1.2-test machine and server-side binding unit; 1.3-smart network card installation unit; 2-master-slave test terminal setting module; 2.1-master test terminal and slave test terminal selection unit; 2.2-dependency determination and flag setting unit; 3-master-slave test terminal interaction test module; 3.1-parallel test unit; 3.2-server-side test unit; 3.3-smart network card test unit; 3.4-server-side return log unit; 3.5-smart network card log inspection unit; 3.6-smart network card log merging unit. DETAILED DESCRIPTION

[0083] In order to enable those skilled in the art to better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0084] Components are the materials that make up the entire server, such as CPU, memory, and hard disk. The components in this patent mainly refer to smart network cards.

[0085] Smart NICs, also known as intelligent network adapters, not only perform the network transmission functions of standard NICs, but also provide built-in programmable and configurable hardware acceleration engines to improve application performance and significantly reduce CPU consumption in communication, providing more CPU resources for applications.

[0086] DHCP is the abbreviation of Dynamic Host Configuration Protocol.

[0087] Example 1:

[0088] like Figure 1 As shown, the present invention provides a method for testing the collaboration between a server and a component, comprising the following steps:

[0089] S1. Pre-bind a fixed IP address to the server and establish a binding relationship between the test machine where the smart network card is located and the server.

[0090] S2. Select one of the bound test machine and server as the master test end and another as the slave test end, and set the dependency flag according to the dependency relationship between the master test end and the slave test end;

[0091] S3. After starting the test and scanning the boards, the master test end interacts with the slave test end through the dependency flag. After the test is completed, the slave test end logs are collected, merged, and displayed.

[0092] The server and component collaborative testing method provided by the present invention replaces the multiple scan test scheme through the collaborative testing of the server and the smart network card as a component, eliminates the need for two sets of displays, keyboards and scanners, and reduces the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0093] Example 2:

[0094] like Figure 2 As shown, the present invention provides a method for testing the collaboration between a server and a component, comprising the following steps:

[0095] S1. Pre-bind a fixed IP to the server and establish a binding relationship between the test machine and the server where the smart network card is located; the specific steps of step S1 are as follows:

[0096] S11. Bind the server-side network card to a fixed IP address on the DHCP server on the production line.

[0097] S12. Bind the test machine number to the fixed IP address of the server network card to form a binding file;

[0098] S13. Install the Smart NIC on the test machine.

[0099] S2. Select one of the bound test machine and server as the master test end, select another as the slave test end, and set the dependency flag according to the dependency relationship between the master test end and the slave test end; the specific steps of step S2 are as follows:

[0100] S21. Select the test machine where the smart network card is located as the main test end, and select the server end with which the test machine is bound as the slave test end;

[0101] S22. According to the dependency relationship between the server and the intelligent network card test machine, determine their respective dependencies and set the dependency flag for the server at the test machine;

[0102] S3. After starting the test and scanning the board, the master test end interacts with the slave test end through the dependency flag. After the test is completed, the slave test end logs are collected, merged, and displayed. The specific steps of step S3 are as follows:

[0103] S31. After the test machine is powered on, the server and the test machine where the smart network card is located begin testing in parallel;

[0104] S32. The server executes the test items in order, and when executing the server-side dependency items, it queries whether the dependency flag of the test machine where the smart network card is located is set;

[0105] If yes, go to step S34;

[0106] If not, return to step S32;

[0107] S33. After the intelligent NIC end scans the test machine, the test items are executed in order. At the same time, when the intelligent NIC end dependency item is executed, the test machine will be dependent on the flag position, and the process proceeds to step S35.

[0108] S34. The server continues to execute the remaining test items and returns the log to the Smart NIC after the server test is completed.

[0109] S35. After the Smart NIC completes the test, check whether the server log is returned.

[0110] If yes, go to step S36;

[0111] If not, return to step S35;

[0112] S36. The Smart NIC merges its own test log with the log sent back by the server and displays the test results.

[0113] The server and component collaborative testing method provided by the present invention replaces the multiple scan test scheme through the collaborative testing of the server and the smart network card as a component, eliminates the need for two sets of displays, keyboards and scanners, and reduces the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0114] Example 3:

[0115] like Figure 2 、 Figure 3 and Figure 4 As shown, the present invention provides a method for testing the collaboration between a server and a component, comprising the following steps:

[0116] S1. Pre-bind a fixed IP to the server and establish a binding relationship between the test machine and the server where the smart network card is located; the specific steps of step S1 are as follows:

[0117] S11. Bind the server-side network card to a fixed IP address on the DHCP server on the production line. The specific steps of step S11 are as follows:

[0118] S111 obtains the number of server-side network cards to be tested as a test fixture; for example, a DHCP server is bound to five test fixture server-side network cards;

[0119] S112. Bind each server-side network card to a fixed IP address on the DHCP server. For example, the following five fixed IP addresses are used for the five server-side network cards to be tested: 192.168.0.1 / 192.168.0.2 / 192.168.0.3 / 192.168.0.4 / 192.168.0.5

[0120] S12 bind the test machine number and the server-side network card fixed IP, forming a binding file; step S12 specific steps are as follows:

[0121] S121. Assign a test machine to each server to be tested;

[0122] S122. Generate a binding file by binding the test machine number and the server network card's fixed IP address to the server-side network card according to the corresponding relationship between the server and the test machine to be tested;

[0123] Taking five test machines, FCT_01, FCT_02, FCT_03, FCT_04, and FCT_05, as an example, the binding relationships stored in the binding file are as follows:

[0124] FCT_01:192.168.0.1

[0125] FCT_02:192.168.0.2

[0126] FCT_03:192.168.0.3

[0127] FCT_04:192.168.0.4

[0128] FCT_05:192.168.0.5

[0129] S13. Install the Smart NIC on the test machine.

[0130] S2. Select one of the bound test machine and server as the master test end, select another as the slave test end, and set the dependency flag according to the dependency relationship between the master test end and the slave test end; the specific steps of step S2 are as follows:

[0131] S21. Select the test machine where the smart network card is located as the master test end, and select the server end that has a binding relationship with the test machine as the slave test end; the master test end monitors the overall test process and displays the test results;

[0132] S22. According to the dependency relationship between the server and the intelligent network card test machine, determine their respective dependencies and set the dependency flag for the server at the test machine;

[0133] S3. After starting the test and scanning the board, the master test end interacts with the slave test end through the dependency flag. After the test is completed, the slave test end logs are collected, merged, and displayed. The specific steps of step S3 are as follows:

[0134] S31. After the test machine is powered on, the server and the test machine where the smart network card is located begin testing in parallel;

[0135] S32. The server executes the test items in sequence, and when executing the server-side dependency item, it queries whether the dependency flag of the test machine where the smart network card is located is set; taking the seventh server-side test item dependent on the eleventh smart network card test item as an example, the server automatically executes the first to sixth test items without dependencies, and when executing the seventh server-side dependency test item, it enters the waiting state and automatically loops to detect whether the dependency flag is set;

[0136] If yes, go to step S34;

[0137] If not, return to step S32;

[0138] S33. After the intelligent network card end scans the test machine, the test items are executed in order. At the same time, when the intelligent network card end dependency item is executed, the test machine will be dependent on the flag position, and step S35 is entered; the specific steps of S33 are as follows:

[0139] S331. The Smart NIC scans the test machine to obtain the test machine ID. The Smart NIC scans the PN / QN / machine ID, such as FCT_01.

[0140] S332. The Smart NIC executes the test items in sequence. When executing the Smart NIC-side dependency item, it obtains the binding file and searches the binding file for the fixed IP address of the corresponding server-side NIC based on the test machine number. It sets the dependency flag for the server-side NIC and provides the scanned test machine number to the server-side. The Smart NIC executes the first to eleventh test items in sequence. Upon completion, it obtains the server-side fixed IP address, such as 192.168.0.1, from the test machine number fixed IP binding relationship file, sets the server-side dependency flag, and passes the scanned PN / QN / machine number and other information to the server-side.

[0141] In step S32, the server queries whether the dependency flag provided by the corresponding test machine is set;

[0142] S34. The server continues to execute the remaining test items and returns the log to the Smart NIC after the server test is completed. The server scans that the dependency flag has been set and continues to execute the remaining test items 7 to 10. After execution, the test log is returned to the Smart NIC.

[0143] S35. After the Smart NIC completes the test, check whether the server log is returned.

[0144] If yes, go to step S36;

[0145] If not, return to step S35;

[0146] The Smart NIC continues to execute the remaining test items, such as test items 12 to 20. After the Smart NIC test items are completed, check whether the server-side log is successfully uploaded and whether the server-side test log is correct.

[0147] S36. The Smart NIC merges its own test log with the log sent back by the server and displays the test results, thus completing the test.

[0148] The server and component collaborative testing method provided by the present invention replaces the multiple scan test scheme through the collaborative testing of the server and the smart network card as a component, eliminates the need for two sets of displays, keyboards and scanners, and reduces the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0149] Example 4:

[0150] like Figure 5 As shown, the present invention provides a server and component collaborative testing device, comprising:

[0151] The server-to-test machine binding module 1 is used to pre-bind a fixed IP address to the server and establish a binding relationship between the test machine where the smart network card is located and the server.

[0152] The master-slave test terminal setting module 2 is used to select one of the bound test machine and server as the master test terminal and the other as the slave test terminal, and set the dependency flag according to the dependency relationship between the master test terminal and the slave test terminal;

[0153] The master-slave test end interaction test module 3 is used for the master test end to perform board scanning after starting the test, and then interact with the slave test end through the dependency flag bit. After the test is completed, the slave test end logs are collected, merged and displayed.

[0154] The server and component collaborative testing device provided by the present invention replaces the multiple scanning test scheme through the collaborative testing of the server and the smart network card as a component, eliminates the need for two sets of displays, keyboards and scanners, and reduces the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0155] Example 5:

[0156] like Figure 5 As shown, the present invention provides a server and component collaborative testing device, comprising:

[0157] The server-side and test machine binding module 1 is used to pre-bind a fixed IP address to the server-side and establish a binding relationship between the test machine where the smart network card is located and the server-side. The server-side and test machine binding module 1 includes:

[0158] Server-side IP binding unit 1.1, used to bind the server-side network card to a fixed IP address at the DHCP server on the production line;

[0159] The test machine and server binding unit 1.2 is used to bind the test machine number and the fixed IP address of the server network card to form a binding file;

[0160] Smart NIC installation unit 1.3, used to install the Smart NIC on the test machine;

[0161] The master-slave test terminal setting module 2 is used to select one of the bound test machine and server as the master test terminal and the other as the slave test terminal, and set the dependency flag according to the dependency relationship between the master test terminal and the slave test terminal. The master-slave test terminal setting module 2 includes:

[0162] The master test end and slave test end selection unit 2.1 is used to select the test machine where the intelligent network card is located as the master test end and select the server end that has a binding relationship with the test machine as the slave test end;

[0163] Dependency determination and flag setting unit 2.2, configured to determine the dependencies of the server and the iNIC test machine based on their dependency relationships, and set a dependency flag for the server on the test machine;

[0164] The master-slave test end interaction test module 3 is used for the master test end to perform board scanning after starting the test, interact with the slave test end through the dependency flag, and collect the slave test end logs after the test is completed, and perform log merging and display. The master-slave test end interaction test module 3 includes:

[0165] Parallel testing unit 3.1 is used to start testing on the server and the test machine where the smart network card is located in parallel after the test machine is powered on;

[0166] The server-side test unit 3.2 is used to execute test items in sequence and, when executing a server-side dependency item, query whether the dependency flag of the test machine where the smart network card is located is set;

[0167] The Smart NIC test unit 3.3 is configured to scan the test machine and execute the test items in order. When executing the Smart NIC dependency item, the test machine dependency flag is set.

[0168] The server-side return log unit 3.4 is used to continue executing the remaining test items when it finds that the dependency flag of the test machine where the smart network card is located is set, and return the log to the smart network card after the server-side test is completed;

[0169] The iNIC log check unit 3.5 is used to check whether the server log is returned after the test is completed;

[0170] The smart network card-side log merging unit 3.6 is used to check the server-side log return, merge its own test log with the server-side return log, and display the test results.

[0171] The server and component collaborative testing device provided by the present invention replaces the multiple scan test scheme through the collaborative testing of the server and the smart network card as a component, eliminating the need for two sets of displays, keyboards and scanners, and reducing the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0172] Example 6:

[0173] like Figure 5 As shown, the present invention provides a server and component collaborative testing device, comprising:

[0174] The server-side and test machine binding module 1 is used to pre-bind a fixed IP address to the server-side and establish a binding relationship between the test machine where the smart network card is located and the server-side. The server-side and test machine binding module 1 includes:

[0175] The server-side IP binding unit 1.1 is used to bind the server-side network card to a fixed IP address on the DHCP server of the production line. The server-side IP binding unit 1.1 includes:

[0176] The server number acquisition subunit to be tested is used to obtain the number of network cards of the server to be tested as a test fixture;

[0177] The IP binding subunit of the server network card to be tested is used to bind the network card of each server to be tested to a fixed IP address on the DHCP server;

[0178] The test machine and server binding unit 1.2 is used to bind the test machine number to the fixed IP address of the server network card to form a binding file. The test machine and server binding unit 1.2 includes:

[0179] The test machine designation subunit is used to designate a test machine for each server to be tested;

[0180] The binding file generation subunit is used to bind the test machine number and the fixed IP of the server network card according to the corresponding relationship between the server to be tested and the test machine, and generate a binding file;

[0181] Smart NIC installation unit 1.3, used to install the Smart NIC on the test machine;

[0182] The master-slave test terminal setting module 2 is used to select one of the bound test machine and server as the master test terminal and the other as the slave test terminal, and set the dependency flag according to the dependency relationship between the master test terminal and the slave test terminal. The master-slave test terminal setting module 2 includes:

[0183] The master test end and slave test end selection unit 2.1 is used to select the test machine where the intelligent network card is located as the master test end and select the server end that has a binding relationship with the test machine as the slave test end;

[0184] Dependency determination and flag setting unit 2.2, configured to determine the dependencies of the server and the iNIC test machine based on their dependency relationships, and set a dependency flag for the server on the test machine;

[0185] The master-slave test end interaction test module 3 is used for the master test end to perform board scanning after starting the test, interact with the slave test end through the dependency flag, and collect the slave test end logs after the test is completed, and perform log merging and display. The master-slave test end interaction test module 3 includes:

[0186] Parallel testing unit 3.1 is used to start testing on the server and the test machine where the smart network card is located in parallel after the test machine is powered on;

[0187] The server-side test unit 3.2 is used to execute test items in sequence and, when executing a server-side dependency item, query whether the dependency flag of the test machine where the smart network card is located is set;

[0188] The Smart NIC test unit 3.3 is configured to scan the test machine and execute test items in sequence. When executing a Smart NIC dependency item, the test machine dependency flag is set. The Smart NIC test unit 3.3 includes:

[0189] Scan test machine number subunit, used to scan the test machine and obtain the test machine number;

[0190] The test execution and dependency flag position subunit is used to execute test items in sequence. When executing the dependency item on the Smart NIC, it obtains the binding file, searches the binding file for the fixed IP address of the server-side network card according to the test machine number, sets the dependency flag for the server, and provides the scanned test machine number to the server.

[0191] The server-side return log unit 3.4 is used to continue executing the remaining test items when it finds that the dependency flag of the test machine where the smart network card is located is set, and return the log to the smart network card after the server-side test is completed;

[0192] The iNIC log check unit 3.5 is used to check whether the server log is returned after the test is completed;

[0193] The smart network card-side log merging unit 3.6 is used to check the server-side log return, merge its own test log with the server-side return log, and display the test results.

[0194] The server and component collaborative testing device provided by the present invention replaces the multiple scanning test scheme through the collaborative testing of the server and the smart network card as a component, eliminates the need for two sets of displays, keyboards and scanners, and reduces the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0195] Example 7:

[0196] The present invention provides a device including a processor and a memory;

[0197] The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device executes the method described in the above-mentioned embodiment 1, embodiment 2 or embodiment 3.

[0198] The server and component collaborative testing equipment provided by the present invention replaces the multiple scanning test scheme through the collaborative testing of the server and the smart network card as a component, eliminates the need to use two sets of displays, keyboards and scanners, and reduces the cost of test tooling; by setting dependent flags, automatic interactive control of the test process is achieved, without the need for manual control, saving test time; by returning the test log, the test results are displayed in a centralized manner, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0199] Example 8:

[0200] The present invention provides a storage medium having instructions stored therein. When the storage medium is run on a computer, the computer is caused to execute the method described in the above-mentioned embodiment 1, embodiment 2 or embodiment 3.

[0201] The server and component collaborative testing medium provided by the present invention replaces the multiple-scan test scheme through collaborative testing of the server and the smart network card as a component, eliminating the need for two sets of displays, keyboards, and scanners, and reducing the cost of test tooling; by setting dependent flags, automated interactive control of the test process is achieved, eliminating the need for manual control and saving test time; by returning the test log, the test results are centrally displayed, avoiding misunderstandings caused by inconsistent test results displayed on both ends of the server and the component; and by binding a fixed IP address to the test machine, the convenience and accuracy of the test process are guaranteed.

[0202] Although the present invention has been described in detail with reference to the accompanying drawings and in conjunction with preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and such modifications or substitutions shall be within the scope of the present invention. Any person skilled in the art who can easily conceive of changes or substitutions within the technical scope disclosed in the present invention shall be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be based on the scope of protection of the claims.

Claims

1. A server and component collaboration testing method, characterized in that: The steps include: S1 pre-bind fixed IP for the server, establish a binding relationship between the test machine and the server where the smart network card; the specific steps of step S1 are: S11. Bind the server-side network card to a fixed IP address on the DHCP server on the production line. S12. Bind the test machine number to the fixed IP address of the server network card to form a binding file; S13. Install the Smart NIC on the test machine. S2. Select one of the bound test machine and server as the master test end, select another as the slave test end, and set the dependency flag according to the dependency relationship between the master test end and the slave test end; the specific steps of step S2 are: S21. Select the test machine where the smart network card is located as the main test end, and select the server end with which the test machine is bound as the slave test end; S22. According to the dependency relationship between the server and the intelligent network card test machine, determine their respective dependencies and set the dependency flag for the server at the test machine; S3. After starting the test and scanning the boards, the master test end interacts with the slave test end through the dependency flag. After the test is completed, the slave test end logs are collected, merged, and displayed.

2. The server and component collaboration testing method according to claim 1, wherein: The specific steps of step S11 are as follows: S111. Obtain the number of server-side network cards to be tested as a test fixture; S112. Bind each server-side network card to a fixed IP address on the DHCP server.

3. The server and component collaboration testing method according to claim 1, wherein: Step S12 specifically includes the following steps: S121. Assign a test machine to each server to be tested; S122. Bind the test machine number and the fixed IP address of the server network card according to the correspondence between the server to be tested and the test machine, and generate a binding file.

4. The server and component collaboration testing method according to claim 1, wherein: The specific steps of step S3 are as follows: S31. After the test machine is powered on, the server and the test machine where the smart network card is located begin testing in parallel; S32. The server executes the test items in order, and when executing the server-side dependency items, it queries whether the dependency flag of the test machine where the smart network card is located is set; If yes, go to step S34; If not, return to step S32; S33. After the intelligent NIC end scans the test machine, the test items are executed in order. At the same time, when the intelligent NIC end dependency item is executed, the test machine will be dependent on the flag position, and the process proceeds to step S35. S34. The server continues to execute the remaining test items and returns the log to the Smart NIC after the server test is completed. S35. After the Smart NIC completes the test, check whether the server log is returned. If yes, go to step S36; If not, return to step S35; S36. The Smart NIC merges its own test log with the log sent back by the server and displays the test results.

5. The server and component collaboration testing method according to claim 4, wherein: The specific steps of step S33 are as follows: S331. The intelligent network card scans the test machine and obtains the test machine number; S332. The Smart NIC executes the test items in sequence. When executing the Smart NIC-side dependency item, it obtains the binding file and searches the binding file for the fixed IP address of the server-side NIC based on the test machine number. It sets the dependency flag for the server and provides the scanned test machine number to the server. In step S32, the server side queries whether the dependency flag provided by the corresponding station number tester is set.

6. A server and component collaboration testing device, characterized in that: include: The server-to-test machine binding module is used to pre-bind a fixed IP address to the server and establish a binding relationship between the test machine where the smart network card is located and the server. Specifically, it includes: binding the server-side network card to a fixed IP address on the DHCP server on the production line; binding the test machine number to the fixed IP address of the server-side network card to form a binding file; and installing a smart network card on the test machine. The master-slave test end setting module is used to select one of the bound test machine and server end as the master test end and the other as the slave test end, and set the dependency flag bit according to the dependency relationship between the master test end and the slave test end. Specifically, it includes: selecting the test machine where the smart network card is located as the master test end, selecting the server end with which the test machine has a binding relationship as the slave test end; determining the respective dependencies of the server end and the smart network card test machine based on the dependency relationship, and setting the dependency flag bit for the server end on the test machine; The master-slave test end interaction test module is used for the master test end to perform board scanning after starting the test, and then interact with the slave test end through the dependency flag bit. After the test is completed, the slave test end logs are collected, merged, and displayed.

7. A device, characterized in that including processor and memory; The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device executes the method described in any one of claims 1 to 5.

8. A storage medium, characterized in that: The storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 5.

Images