BMC configuration management method and server system

Abstract

The invention provides a BMC configuration management method and a server system. The method provided by the invention comprises the following steps: a client server sends a configuration information request message to a target server; the target server-side server generates a first configuration file according to specified configuration information returned by the configuration information request message, and returns the first configuration file to the client-side server; the client server receives the first configuration file, uses the first configuration file as a second configuration file, calculates a first check code of the second configuration file, and sends the first check code to the target server; the target server-side server verifies the second configuration file based on the first verification code and the first configuration file, and returns a verification result to the client-side server; and the client server receives a verification result returned by the target server, and configures the BMC on the client server according to the second configuration file when the verification result is successful.

Description

Technical Field

[0001] This application relates to the technical field of servers, and in particular, to a BMC configuration management method and a server system. Background Art

[0002] Due to the high-speed CPU computing power, long-term reliable operation, powerful I / O external data throughput capacity, and better scalability of servers, they are widely used in various scenarios.

[0003] When a server is used for the first time, a large number of initial configurations need to be made for the BMC. Since setting up the BMC is cumbersome and time-consuming, for servers of the same model, after-sales personnel usually use the method of configuration sharing to set up the BMC. Through configuration sharing, the pre-configured BMC settings can be quickly and accurately applied to new servers. However, this method requires a large amount of manual operation and requires the purchase of additional equipment to store configuration files. Summary of the Invention

[0004] In view of this, this application provides a BMC configuration management method and a server system, which realize automatic sharing of configurations between the BMCs of servers without the interference of humans or additional equipment, and reduce costs.

[0005] Specifically, this application is implemented through the following technical solutions: In a first aspect of this application, a BMC configuration management method is provided. The method is applied to a server system, and the server system includes a client server to be configured with the BMC and a server server that has been configured with the BMC. The method includes: The client server sends a configuration information request message to a target server server in the server server; wherein, the first hardware identification information of the target server server is the same as the second hardware identification information of this client server; The target server server generates a first configuration file according to the specified configuration information requested to be returned by the configuration information request message, and returns the first configuration file to the client server; The client server receives the first configuration file returned by the target server server, uses the received first configuration file as a second configuration file, calculates a first checksum of the second configuration file, and sends the first checksum to the target server server; The target server server checks the second configuration file based on the first checksum and the first configuration file, and returns a check result to the client server; The client server receives the verification result returned by the target server, and when the verification result is successful, configures the BMC on the client server according to the second configuration file.

[0006] The second aspect of the present application provides a server system, which includes a client server to be configured with BMC and a server that has been configured with BMC. Among them, The client server is used to send a configuration information request message to the target server in the server; among them, the first hardware identification information of the target server is the same as the second hardware identification information of the client server; The target server is used to generate a first configuration file according to the specified configuration information requested and returned by the configuration information request message, and return the first configuration file to the client server; The client server is further used to receive the first configuration file returned by the target server, use the received first configuration file as the second configuration file, calculate the first checksum of the second configuration file, and send the first checksum to the target server; The target server is further used to verify the second configuration file based on the first checksum and the first configuration file, and return a verification result to the client server; The client server is further used to receive the verification result returned by the target server, and when the verification result is successful, configure the BMC on the client server according to the second configuration file.

[0007] For the BMC configuration management method and server system provided by the present application, the client server and the target server interact with each other. First, the client server sends a configuration information request message to the target server, and the target server returns the first configuration file to the client server; further, the client server uses the received first configuration file as the second configuration file, calculates the first checksum and sends it to the target server, and the target server returns the verification result to the client server; finally, when the verification result is successful, the client server configures the BMC according to the second configuration file. On the one hand, it realizes the automatic configuration sharing between the BMCs of the servers, without the interference of humans or additional devices, reducing costs; on the other hand, the interaction between the client server and the target server is realized through the protocol, without additional management means, improving the transmission efficiency. Description of the Drawings

[0008] Figure 1Flow chart of the first embodiment of the BMC configuration management method provided by this application; Figure 2 Flow chart of the second embodiment of the BMC configuration management method provided by this application; Figure 3 Flow chart of the third embodiment of the BMC configuration management method provided by this application; Figure 4 Flow chart of the fourth embodiment of the BMC configuration management method provided by this application; Figure 5 Flow chart of the fifth embodiment of the BMC configuration management method provided by this application; Figure 6 Schematic structural diagram of the first embodiment of the server system provided by this application. Detailed implementation mode

[0009] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with this application.

[0010] The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The singular forms "a", "the" and "said" used in this application are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0011] It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to a determination".

[0012] Specific embodiments are given below to introduce the technical solutions of this application in detail.

[0013] Figure 1 Flow chart of the first embodiment of the BMC configuration management method provided by this application. Please refer to Figure 1 , the method provided in this embodiment, the method is applied to a server system, the server system includes a client server to be configured with BMC and a server server that has been configured with BMC, and the method includes: S101. The client server sends a configuration information request message to the target server in the server; wherein, the first hardware identification information of the target server is the same as the second hardware identification information of the client server.

[0014] Specifically, the client server is the server to be configured with BMC, and there is no configuration file on it. The server is the server that has been configured with BMC, and there is a configuration file on it. The target server refers to the server in the server whose first hardware identification information is the same as the second hardware identification information of the client server. Among them, the first hardware identification information and the second hardware identification information include the vendor code, device code, and version code. The length of the vendor code is 24 bytes, which represents the vendor ID of the server, and the vendor codes of the servers of the same vendor are the same; the length of the device code is 24 bytes, which represents the device number of the server, and the device codes of the servers of the same model are the same; the length of the version code is 16 bytes, which represents the current BMC version number of the server, and the version codes of the BMCs of the same version are the same.

[0015] In this embodiment, a certain server is determined as the target server by manual designation.

[0016] Further, the configuration information request message includes a transmission option field (option), which indicates the specified configuration information requested to be obtained through the transmission option field, and then generates a first configuration file based on the specified configuration information and returns it to the client server. The length of the transmission option field is 2 bytes, which represents the situation where the client server needs to synchronize various BMC configurations, and the default is that all configurations are synchronized, that is: FFFF. Table 1 is the structure table of the first byte of the transmission option field shown in an exemplary embodiment of the present application, and Table 2 is the structure table of the second byte of the transmission option field shown in an exemplary embodiment of the present application: Table 1

[0017] Table 2

[0018] Please refer to Table 1 and Table 2. When the bit corresponding to an option name is 1, it means that the client server needs to synchronize the configuration of this option; when the bit corresponding to an option name is 0, it means that the client server does not need to synchronize the configuration of this option, and the default value is that all option configurations need to be synchronized.

[0019] It should be noted that in this embodiment, the communication between the client server and the target server is implemented at the TCP (Transmission Control Protocol, a transport layer protocol based on byte streams) layer, and the port number used by the target server is 14,800.

[0020] S102. The target server generates a first configuration file according to the specified configuration information requested and returned in the configuration information request message, and returns the first configuration file to the client server.

[0021] Specifically, in combination with the above description, the first configuration file is generated based on the specified configuration information, and the specified configuration information is determined according to the transmission option field of the configuration information request message. For example, in one embodiment, when the bit positions where the option names in the transmission option field are all 1, it indicates that the specified configuration information includes all options in the transmission option field.

[0022] In specific implementation, when the target server is ready to send the first configuration file to the client server, it will generate only the configuration information that the client server needs to synchronize into the first configuration file according to the situations of each option in the transmission option field of the configuration information request message.

[0023] The method provided in this embodiment only generates the configuration information that the client server needs to synchronize into the first configuration file, which can reduce the data volume of the first configuration file and improve the transmission efficiency.

[0024] S103. The client server receives the first configuration file returned by the target server, uses the received first configuration file as the second configuration file, calculates the first checksum of the second configuration file, and sends the first checksum to the target server.

[0025] Specifically, when the size of the first configuration file does not exceed the maximum transmission limit (for example, 1500 bytes), in this step, the received first configuration file is directly used as the second configuration file. Further, by performing a hash operation on the content of the second configuration file, that is, calculating the second configuration file using a hash algorithm (such as MD5, SHA-1, SHA-256, etc.), the first checksum is obtained.

[0026] It should be noted that before calculating the first checksum and sending the first checksum to the target server, the first checksum needs to be placed in the file field. The file field is used to store the configuration file data during the transmission of the configuration file, and this field is valid when the target server returns the first configuration file to the client server.

[0027] S104. The target server validates the second configuration file based on the first verification code and the first configuration file, and returns the verification result to the client server.

[0028] Specifically, the verification result includes verification success and verification failure. After obtaining the verification result, the target server places the verification result in the Result field. Here, the Result field represents the verification result returned by the target server to the client server, and this field is valid when the target server returns the verification result to the client server. If the Result field is 1, it indicates verification success; if the Result field is 2, it indicates verification failure.

[0029] In specific implementation Figure 2 This is the flowchart of the second embodiment of the BMC configuration management method provided by this application. Please refer to Figure 2 In this embodiment, based on the above embodiment, the method for the target server to validate the second configuration file based on the first verification code and the first configuration file includes: S201. The target server calculates the second verification code of the first configuration file.

[0030] In specific implementation, in combination with the above description, by performing a hash operation on the content of the first configuration file, that is, using a hash algorithm (such as MD5, SHA-1, SHA-256, etc.) to calculate the first configuration file, the second verification code is obtained.

[0031] S202. The target server compares the first verification code with the second verification code, and when the comparison is consistent, determines that the second configuration file is verified successfully; otherwise, determines that the second configuration file is verified failed.

[0032] In specific implementation, taking the first verification code as a reference, the first verification code stored in the file field is compared with the second verification code of the first configuration file. If the comparison is consistent, it is determined that the second configuration file is verified successfully, that is, the second configuration file is the same as the first configuration file and has not been tampered with; if the comparison is inconsistent, it is determined that the second configuration file is verified failed, that is, the second configuration file is different from the first configuration file, and there may be tampering or errors.

[0033] The method provided in this embodiment can verify the integrity and accuracy of the second configuration file by comparing the first verification code with the second verification code, thereby ensuring that there is no error in the transmission process of the configuration file.

[0034] S105. The client server receives the verification result returned by the target server, and when the verification result is successful, configures the BMC on the client server according to the second configuration file.

[0035] Specifically, in a possible implementation manner in combination with the above description, when the value of the Result field in the verification result received by the client server is 1, it is determined that the verification is successful. At this time, the client server configures the BMC on the client server based on the configuration information recorded in the second configuration file.

[0036] Further, the client server returns a response message indicating successful configuration to the target server. When the target server receives the response message, it disconnects the connection with the client server and deletes the first configuration file.

[0037] Optionally, in another possible implementation manner, when the value of the Result field in the verification result received by the client server is 2, it is determined that the verification fails. At this time, the client server deletes the second configuration file and sends a configuration information request message to the target server again, requesting the target server to return the first configuration file until it receives a verification result indicating successful verification from the target server.

[0038] In the method provided in this embodiment, the client server and the target server interact with each other. First, the client server sends a configuration information request message to the target server, and the target server returns the first configuration file to the client server; further, the client server uses the received first configuration file as the second configuration file and calculates the first verification code to send to the target server, and the target server returns the verification result to the client server; finally, when the verification result is successful, the client server configures the BMC according to the second configuration file. On the one hand, it realizes the automatic configuration sharing between the BMCs of the servers, without the interference of manual or additional devices, reducing costs; on the other hand, the interaction between the client server and the target server is realized through the protocol, without additional management means, improving the transmission efficiency.

[0039] Figure 3 This is the flowchart of the third embodiment of the BMC configuration management method provided by this application. Please refer to Figure 3 In the method provided in this embodiment, the method is applied to a server system, and the server system includes a client server to be configured with BMC and a server that has been configured with BMC. The method includes: S301. The client server determines the target server by broadcasting; wherein, the first hardware identification information of the target server is the same as the second hardware identification information of the client server itself.

[0040] Specifically, the target server refers to the server in the servers whose first hardware identification information is the same as the second hardware identification information of the client server itself.

[0041] In specific implementation Figure 4 is the flowchart of the fourth embodiment of the BMC configuration management method provided by this application. Please refer to Figure 4 , for the method provided in this embodiment, based on the above embodiment, the client server determines the target server by broadcasting, including: S401. The client server broadcasts a discovery message to find a server in its domain through the discovery message and instructs the server to return its own hardware identification information.

[0042] Specifically, the discovery message contains a match type field, which instructs the server to return its own hardware identification information through the match type field (Match Type). Among them, the length of the match type field is 1 byte, which represents the types of manufacturer number, device number, and version number that need to be matched when servers share configurations. When the value of the match type field is 7, it represents that the manufacturer number, device number, and version number need to be matched when servers share configurations; when the value of the match type field is 6, it represents that the manufacturer number and device number need to be matched when servers share configurations; when the value of the match type field is 4, it represents that the manufacturer number needs to be matched when servers share configurations.

[0043] Furthermore, combined with the above description, the hardware identification information includes the manufacturer number, device number, and version number.

[0044] In specific implementation, the client server broadcasts a discovery message in its domain to instruct all servers in the domain that have completed BMC configuration to return their own hardware identification information based on the discovery message.

[0045] S402. After receiving the discovery message, the server in the domain returns a response message to the client server; wherein, the response message carries the first hardware identification information of the server.

[0046] Specifically, the response message carries the first hardware identification information of the server, that is, the manufacturer number, device number, and version number of the server, which is determined according to the value of the match type field in the discovery message.

[0047] When specifically implemented, after the server in the network domain receives the discovery message sent by the client server, it returns a response message carrying the first hardware identification information based on the value of the matching type field in the discovery message.

[0048] For example, in combination with the above example, when the value of the matching type field in the discovery message is 7, the response message returned by the server includes the manufacturer number, device number, and version number of the server.

[0049] S403. The client server searches for the target server in the server based on the response message.

[0050] Specifically, the client server compares the first hardware identification information carried in the received response message with the second hardware identification information on the client server itself. When the comparison result is consistent, it determines the server corresponding to the response message as the target server.

[0051] In the method provided in this embodiment, the client server broadcasts a discovery message to the servers in the same network domain and determines the target server based on the response message returned by the server. Compared with manually specifying the target server, on the one hand, this method does not require manual specification, saving the time and effort of manual operations, reducing human errors, improving the accuracy of finding the target server, and avoiding errors that may be caused by manual specification; on the other hand, this method can easily handle large-scale network environments, quickly locate the target server, be more efficient and fast, and can find the target server in a short time, improving work efficiency.

[0052] S302. The client server sends a configuration information request message to the target server.

[0053] S303. The target server generates a first configuration file based on the specified configuration information requested by the configuration information request message and returns the first configuration file to the client server.

[0054] Specifically, the specific implementation process and principle of steps S302 and S303 can refer to the description in the above embodiment and will not be elaborated here.

[0055] It should be noted that when the size of the first configuration file exceeds the maximum transmission limit, in this step, the first configuration file is split into multiple sub-configuration files and returned to the client server.

[0056] Optionally, the target server returns the first configuration file to the client server, including: Split the first configuration file into multiple sub-configuration files, and sequentially return the multiple sub-configuration files to the client server; wherein, each sub-configuration file carries a transmission status indicator for identifying the current transmission stage of the first configuration file, and the current transmission stage of the first configuration file includes start of transmission, in progress of transmission, and transmission completed.

[0057] Specifically, the sub-configuration file contains part of the configuration information in the first configuration file and carries a transmission status indicator. The length of the transmission status indicator is 1 byte, which is used to identify the current transmission stage of the first configuration file, including the start of transmission stage, in progress of transmission stage, and transmission completed stage. The value of the transmission status indicator is 1, indicating that the first configuration file is currently in the start of transmission stage, that is, the first segment of the first configuration file; the value of the transmission status indicator is 2, indicating that the first configuration file is currently in the in progress of transmission stage; the value of the transmission status indicator is 3, indicating that the first configuration file is currently in the transmission completed stage, that is, the last segment of the first configuration file.

[0058] It should be noted that the sub-configuration file contains a Transmission ID field (Transaction ID), which is 4 bytes in length and is abbreviated as Xid. The Transmission ID field represents a random number selected when the client server initiates a BMC configuration request to the target client server, which is equivalent to a request identifier and is used to identify a BMC configuration request process. In a BMC configuration request, the Xid of all messages is the same, that is, the Xid of each sub-configuration file is the same.

[0059] In specific implementation, split the first configuration file into multiple sub-configuration files according to certain rules (such as by line, by content, by maximum transmission limit, etc.), and use the sequential transmission method (in ascending order of the values of the transmission status indicators) to return these multiple sub-configuration files to the client server one by one, ensuring that the client server receives and processes each sub-configuration file in sequence.

[0060] S304. The client server receives the first configuration file returned by the target server and uses the received first configuration file as the second configuration file, calculates the first checksum of the second configuration file, and sends the first checksum to the target server.

[0061] Specifically, in combination with the above example, in one possible implementation, the client server directly uses the received first configuration file as the second configuration file. In another possible implementation, Figure 5 This is the flowchart of the fifth embodiment of the BMC configuration management method provided by this application. Please refer to Figure 5, based on the above embodiments, the method provided in this embodiment, where the client server receives the first configuration file returned by the target server and uses the received first configuration file as the second configuration file, includes: S501. The client server receives the sub-configuration file returned by the target server.

[0062] In specific implementation, the client server sequentially receives each sub-configuration file returned by the target server.

[0063] For example, in one embodiment, the sub-configuration files received by the client server include sub-configuration file 1, sub-configuration file 2, and sub-configuration file 3. Among them, the value of the transmission status indicator carried by sub-configuration file 1 is 2, the value of the transmission status indicator carried by sub-configuration file 2 is 1, and the value of the transmission status indicator carried by sub-configuration file 3 is 3.

[0064] S502. When the client server determines that the first configuration file is completely transmitted according to the transmission status indicator carried by the currently received sub-configuration file, it combines all the received sub-configuration files into the second configuration file.

[0065] In specific implementation, when the client server finds that the value of the transmission status indicator carried by the received sub-configuration file is 3, it determines that the first configuration file is completely transmitted. Further, the sub-configuration file with the value of the transmission status indicator being 1 is determined as the first sub-file constituting the second configuration file, the sub-configuration file with the value of the transmission status indicator being 2 is determined as the middle sub-file constituting the second configuration file, and the sub-configuration file with the value of the transmission status indicator being 3 is determined as the last sub-file constituting the second configuration file. Then, all the sub-configuration files are combined in the determined order to obtain the second configuration file.

[0066] For example, in combination with the above example, the sub-configuration files received by the client server include sub-configuration file 1, sub-configuration file 2, and sub-configuration file 3. Among them, the value of the transmission status indicator carried by sub-configuration file 1 is 2, the value of the transmission status indicator carried by sub-configuration file 2 is 1, and the value of the transmission status indicator carried by sub-configuration file 3 is 3. In this step, sub-configuration file 2 is used as the first sub-file of the second configuration file, sub-configuration file 1 is used as the second sub-file of the second configuration file, and sub-configuration file 3 is used as the last sub-file of the second configuration file. They are combined in the order of sub-configuration file 2, sub-configuration file 1, and sub-configuration file 3 to obtain the second configuration file.

[0067] In the method provided in this embodiment, the target server splits the first configuration file into multiple sub-configuration files and returns them to the client server. On the one hand, batch transmission is achieved, reducing possible network latency and transmission time during the transmission of the first configuration file, and improving transmission efficiency. In addition, if a certain sub-configuration file fails to be transmitted during the transmission process, only this sub-configuration file needs to be retransmitted, improving fault tolerance. On the other hand, the transmission status indicators carried by each sub-configuration file are different. Based on the transmission status indicators carried by each sub-configuration file, the client server combines these multiple sub-configuration files into a second configuration file. In this way, the client server can receive and process multiple sub-configuration files in parallel, accelerating the combination process of the configuration files, improving processing efficiency, and ensuring the integrity and security of the data as the sub-configuration files will not be lost during the combination process.

[0068] S305. The target server verifies the second configuration file based on the first check code and the first configuration file, and returns the verification result to the client server.

[0069] S306. The client server receives the verification result returned by the target server, and when the verification result is successful, configures the BMC on this client server according to the second configuration file.

[0070] Specifically, for the specific implementation process and implementation principle of steps S305 and S306, reference can be made to the description in the above embodiment, and details will not be elaborated here.

[0071] In the method provided in this embodiment, the client server and the target server interact with each other. First, the client server sends a configuration information request message to the target server, and the target server returns the first configuration file to the client server. Further, the client server takes the received first configuration file as the second configuration file, calculates the first check code and sends it to the target server, and the target server returns the verification result to the client server. Finally, when the verification result is successful, the client server configures the BMC according to the second configuration file. On the one hand, automatic configuration sharing between the BMCs of the servers is achieved, without interference from humans or additional devices, reducing costs. On the other hand, the interaction between the client server and the target server is implemented through a protocol, without additional management means, improving transmission efficiency.

[0072] Figure 6 It is a schematic structural diagram of the first embodiment of the server system provided in this application. Please refer to Figure 6, the server system provided in this embodiment, the server system includes a client server to be configured with BMC and a server server that has been configured with BMC. Among them, The client server is used to send a configuration information request message to the target server server in the server server; among them, the first hardware identification information of the target server server is consistent with the second hardware identification information of this client server; The target server server is used to generate a first configuration file according to the specified configuration information requested and returned by the configuration information request message, and return the first configuration file to the client server; The client server is further used to receive the first configuration file returned by the target server server, use the received first configuration file as the second configuration file, calculate the first checksum of the second configuration file, and send the first checksum to the target server server; The target server server is further used to verify the second configuration file based on the first checksum and the first configuration file, and return a verification result to the client server; The client server is further used to receive the verification result returned by the target server server, and when the verification result is successful verification, configure the BMC on this client server according to the second configuration file.

[0073] In the server system provided in this embodiment, the client server and the target server server interact with each other. First, the client server sends a configuration information request message to the target server server, and the target server server returns a first configuration file to the client server; further, the client server uses the received first configuration file as the second configuration file, calculates the first checksum and sends it to the target server server, and the target server server returns the verification result to the client server; finally, when the verification result is successful verification, the client server configures the BMC according to the second configuration file. On the one hand, it realizes the automatic configuration sharing between the BMCs of the servers, without the interference of humans or additional devices, reducing costs; on the other hand, the interaction between the client server and the target server server is realized through a protocol, without additional management means, improving the transmission efficiency.

[0074] The server system provided in this embodiment can be used to execute Figure 1 the steps of the method embodiment shown, the specific implementation principle and implementation process are similar, and will not be repeated here.

[0075] The above are only the preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A BMC configuration management method, characterized in that, The method is applied to a server system, which includes a client server to be configured with BMC and a server server that has been configured with BMC. The method includes: The client server sends a configuration information request message to a target server server in the server server; wherein, the first hardware identification information of the target server server is the same as the second hardware identification information of the client server itself; The target server server generates a first configuration file according to the specified configuration information requested and returned by the configuration information request message, and returns the first configuration file to the client server; The client server receives the first configuration file returned by the target server server, uses the received first configuration file as a second configuration file, calculates a first checksum of the second configuration file, and sends the first checksum to the target server server; The target server server verifies the second configuration file based on the first checksum and the first configuration file, and returns a verification result to the client server; The client server receives the verification result returned by the target server server, and when the verification result is successful, configures the BMC on the client server itself according to the second configuration file.

2. The method according to claim 1, wherein Before the client server sends a configuration information request message to the target server server, the method further includes: The client server broadcasts a discovery message to find a server server in its domain through the discovery message, and instructs the server server to return its own hardware identification information; The server server in the domain returns a response message to the client server after receiving the discovery message; wherein, the response message carries the first hardware identification information of the server server; The client server finds the target server server from the server servers based on the response message.

3. The method according to claim 1, characterized in that, The target server server returns the first configuration file to the client server, including: Splitting the first configuration file into multiple sub-configuration files, and sequentially returning the multiple sub-configuration files to the client server; wherein, each sub-configuration file carries a transmission status indicator, and the transmission status indicator is used to identify the current transmission stage of the first configuration file. The current transmission stage of the first configuration file includes start of transmission, in transmission, and transmission completed; The client server receives the first configuration file returned by the target server server and uses the received first configuration file as a second configuration file, including: The client server receives the sub-configuration file returned by the target server server; When the client server determines that the first configuration file has been transmitted completely according to the transmission status indicator carried by the currently received sub-configuration file, it combines all the received sub-configuration files into the second configuration file.

4. The method according to claim 1, characterized in that, The target server validates the second configuration file based on the first checksum and the first configuration file, including: The target server calculates a second checksum of the first configuration file; The target server compares the first checksum with the second checksum, and when the comparison is consistent, determines that the second configuration file is successfully validated, otherwise determines that the second configuration file is failed to be validated.

5. The method according to claim 1, wherein The method further includes: When the validation result is a validation failure, the client server deletes the second configuration file and repeats the step of sending a configuration information request message to the target server until the validation result is a validation success.

6. The method according to claim 1, wherein The method further includes: When the validation result is a validation success, the client server returns a successful configuration response message to the target server; When receiving the response message, the target server disconnects the connection with the client server and deletes the first configuration file.

7. The method according to claim 1, characterized in that The configuration information request message includes a transmission option field; the configuration information request message indicates the specified configuration information to be requested through the transmission option field.

8. The method according to claim 2, characterized in that, The discovery message includes a matching type field; the discovery message indicates the hardware identification information to be returned through the matching type field.

9. A server system, characterized in that, The server system includes a client server to be configured with BMC and a server that has been configured with BMC, where The client server is used to send a configuration information request message to a target server in the server; where the first hardware identification information of the target server is the same as the second hardware identification information of this client server; The target server is used to generate a first configuration file according to the specified configuration information requested to be returned by the configuration information request message and return the first configuration file to the client server; The client server is further used to receive the first configuration file returned by the target server, use the received first configuration file as the second configuration file, calculate a first checksum of the second configuration file, and send the first checksum to the target server; The target server is further used to validate the second configuration file based on the first checksum and the first configuration file and return a validation result to the client server; The client server is further used to receive the validation result returned by the target server and configure the BMC on this client server according to the second configuration file when the validation result is a validation success.

10. The server system according to claim 9, characterized in that, Before the client server sends a configuration information request message to the target server, The client server is further used to broadcast a discovery message to find a server in its domain through the discovery message and indicate the server to return its own hardware identification information; After receiving the discovery message, the server in the domain returns a response message to the client server; wherein, the response message carries the first hardware identification information of the server. The client server is further configured to find the target server from the servers based on the response message.

Images