A method for batch modification of BIOS option values based on the Redfish interface

Abstract

The present invention relates to the field of computer application technologies, and discloses a method for batch modification of BIOS option values based on the Redfish interface, including: batch modifying the BIOS configuration information to be modified in the corresponding server group by modifying the BIOS configuration file, sending the pre-configured update script and the BIOS configuration file corresponding to the server group to each server in the server group. When the update script runs, obtaining the current BIOS configuration information of the current server through the Redfish interface, parsing it to obtain each BIOS option value in the current server, constructing an option value modification request to modify the BIOS option values of the current server, generating an update record and sending it to the configuration end. Thus, batch modification of BIOS option values in the production line process of server production lines is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of computer applications, and in particular to a method for batch modifying BIOS option values based on a Redfish interface. Background Art

[0002] The BIOS (Basic Input / Output System) is a set of programs embedded in a ROM chip on the computer's motherboard. It stores the computer's most important basic input / output (BIO) programs, system settings, post-boot self-tests, and system startup routines. Its primary function is to provide the computer with the lowest-level, most direct hardware configuration and control. BIOS parameters are typically stored in a read-write CMOS (Complementary Metal Oxide Semiconductor) RAM (Random Access Memory) chip. When the computer is shut down, a backup battery powers the CMOS RAM to retain the information. Incorrect BIOS configuration information can lead to reduced system performance, component unrecognition, and a range of hardware and software failures.

[0003] The existing method of modifying BIOS option values on factory production lines often has the following technical problems:

[0004] First, to meet the varying BIOS configuration option value requirements of different customers, factory server production currently primarily addresses this by releasing specific BIOS versions to modify the default values of some BIOS options, then importing these specific BIOS versions into the production line process to update the BIOS. This approach is inefficient and requires re-modifying the BIOS code and releasing the version, which must also undergo relevant testing before it can be officially released for use.

[0005] Second, the existing method for determining eligible update records is outdated, making the process of submitting customer customized information complicated;

[0006] Third, when problems arise in the server configuration during BIOS configuration, there are insufficient troubleshooting methods. Summary of the Invention

[0007] This summary is intended to briefly introduce concepts that will be described in detail in the detailed description below. This summary is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0008] The present invention proposes a method for batch modification of BIOS option values based on the Redfish interface to solve one or more of the technical problems mentioned in the above background art section.

[0009] The present invention provides a method for batch modification of BIOS option values based on the Redfish interface, the method comprising:

[0010] Obtain the customer customization information corresponding to the server cluster to be configured, generate a BIOS configuration file group and the configuration quantity corresponding to each BIOS configuration file according to the customer customization information; divide the server cluster to be configured according to the configuration quantity corresponding to each BIOS configuration file to obtain a server group corresponding to each BIOS configuration file, the number of servers included in the server group matching the configuration quantity corresponding to the BIOS configuration file, and the BIOS configuration file includes a plurality of BIOS option names to be modified and the updated value corresponding to each BIOS option name;

[0011] For each server group, send the pre-configured update script and the BIOS configuration file corresponding to the server group to each server in the server group. When the update script runs, obtain the current BIOS configuration information of the current server through the Redfish interface, parse the current BIOS configuration information to obtain the URL path corresponding to each BIOS option name in the current server, and construct an option value modification request according to the URL path corresponding to each BIOS option name and the updated value corresponding to each BIOS option name to modify the BIOS option value of the current server, generate an update record and send the update record to the configuration end.

[0012] Optionally, before obtaining the customer customization information corresponding to the server cluster to be configured, it further includes:

[0013] Obtain a plurality of update records within a historical time period, wherein each update record includes an update timestamp, a customer identifier, an updated BIOS option name and the updated value corresponding to the updated BIOS option name, a customer type, a server order quantity, and a business scenario;

[0014] Divide the plurality of update records into a plurality of update record groups according to the customer type included in each update record, each update record group corresponding to one customer type, and the plurality of update record groups corresponding to a plurality of customer types; divide each update record group according to the business scenario included in the update record to obtain an update record subgroup corresponding to each customer type, each update record subgroup corresponding to one business scenario; and

[0015] Before obtaining the customer customization information corresponding to the server cluster to be configured, the method further includes: when receiving a configuration page acquisition request sent by a target user through a target user terminal, sending the configuration page to the target user terminal so that the target user submits customer customization information in the configuration page; and

[0016] Obtaining the customer customization information corresponding to the server cluster to be configured includes:

[0017] When receiving the target customer identifier and the target business scenario submitted by the target user in the configuration page, query the target customer identifier in multiple update records. If there is an update record matching the target customer identifier in the multiple update records, determine the matching update record as the target update record;

[0018] Send the target update record to the target user terminal, and control the target user terminal to display a historical configuration information viewing component and a historical configuration viewing prompt message in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page.

[0019] Optionally, obtaining the customer customization information corresponding to the server cluster to be configured further includes:

[0020] If there is no update record matching the target customer identifier in the multiple update records, determine the customer type corresponding to the target customer identifier as the target customer type, and determine the customer type with the highest matching degree with the target customer type from the multiple customer types, and determine the customer type with the highest matching degree as the matching customer type;

[0021] According to the target business scenario, determine the business scenario with the highest matching degree with the target business scenario from the multiple business scenarios corresponding to the matching customer type, and determine it as the matching business scenario;

[0022] Generate recommended configuration information according to the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

[0023] Optionally, obtaining the customer customization information corresponding to the server cluster to be configured further includes:

[0024] If there is no business scenario matching the target business scenario in the multiple business scenarios corresponding to the matching customer type, for each update record subgroup corresponding to each business scenario in the multiple business scenarios, determine the average update timestamp corresponding to each update record subgroup;

[0025] Based on the average update timestamp corresponding to each sub-group of update records and the current time, select the sub-group of update records closest to the current time from multiple business scenarios, and generate recommended configuration information based on the sub-group of update records closest to the current time; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information on the configuration page.

[0026] Optionally, for each server group, send the pre-configured update script and the BIOS configuration file corresponding to the server group to each server in the server group, including:

[0027] According to the manufacturer information of each server, select the update script that matches the manufacturer information of each server from the pre-configured update script library, and send the matching update script to the corresponding server.

[0028] The present invention has the following beneficial effects:

[0029] 1. It realizes the need of different customers for BIOS option configuration in factory server production in batches. Specifically, different customers have different requirements for the BIOS option configuration of the server. On this basis, by generating a BIOS configuration file group and the corresponding configuration quantity for each BIOS configuration file according to the customer customization information, and then dividing the server cluster to be configured to obtain the server group corresponding to each BIOS configuration file, and then performing targeted configuration for each server group, it specifically solves the problem of importing a specific BIOS version into the production line production process to update the BIOS method to meet the needs of customers. Thus, it improves the efficiency of different customers' requirements for BIOS option configuration and ensures timeliness.

[0030] 2. The target user sends a configuration page acquisition request to the background server through the target user terminal, and the background server sends the configuration page to the target user terminal, enabling the target user to submit customer customization information on the configuration page. The background server determines the target update record that matches it, sends the target update record to the target user terminal, and controls the target user terminal to display the historical configuration information viewing component and the historical configuration viewing prompt information on the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record on the configuration page. Thus, it realizes the display of eligible update records on the target user terminal during the submission process of customer customization information, providing reference information for user customization and facilitating the quick submission of customer customization information.

[0031] 3. By statistically analyzing the actual configuration duration of each server in the server cluster to be configured for each BIOS option, the BIOS option to be troubleshot and the server to be troubleshot are determined, thereby optimizing the troubleshooting method and avoiding omission of problems. Brief Description of the Drawings

[0032] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages, and aspects of the various embodiments of the present invention will become more apparent. Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic and the elements and elements are not necessarily drawn to scale.

[0033] Figure 1 is a flowchart of a method for batch modification of BIOS option values based on the redfish interface of the present invention. Detailed Description of the Embodiments

[0034] The present invention will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not used to limit the protection scope of the present invention.

[0035] In addition, it should be noted that for the sake of description, only parts related to the relevant invention are shown in the drawings. Without conflict, the embodiments in the present invention and the features in the embodiments can be combined with each other.

[0036] It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules, or units, and are not used to limit the order of functions performed by these devices, modules, or units or their interdependent relationships.

[0037] It should be noted that the modifications of "one" and "multiple" mentioned in the present invention are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

[0038] The names of the messages or information exchanged between multiple devices of the present invention are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0039] The present invention will be described in detail below with reference to the drawings and in combination with the embodiments.

[0040] Figure 1 is a flowchart of a method for batch modification of BIOS option values based on the redfish interface of the present invention, which specifically includes the following steps:

[0041] Step 101, obtain the customer customization information corresponding to the server cluster to be configured, generate a BIOS configuration file group and the configuration quantity corresponding to each BIOS configuration file according to the customer customization information; divide the server cluster to be configured according to the configuration quantity corresponding to each BIOS configuration file to obtain a server group corresponding to each BIOS configuration file, where the number of servers included in the server group matches the configuration quantity corresponding to the BIOS configuration file, and the BIOS configuration file includes multiple BIOS option names to be modified and the updated value corresponding to each BIOS option name.

[0042] In some embodiments, the execution subject of a method for batch modification of BIOS option values based on the redfish interface of the present invention may be a user terminal. As an example, the user terminal may be a computer, a mobile phone, etc.

[0043] In practice, redfish is a modern, open and standardized remote management and monitoring interface, and uses the JSON or OData format for data exchange. The execution subject establishes a communication connection with the background server through various communication methods. On this basis, obtain the customer customization information corresponding to the server cluster to be configured from the background server through the redfish interface. It can be understood that the background server is different from the servers in the server cluster to be configured. The customer customization information is the customer's requirement for modifying specific BIOS configuration options of the server.

[0044] In practice, batch modify the BIOS option values to be modified in the corresponding server group by modifying the BIOS configuration file. The BIOS configuration file includes multiple BIOS option names to be modified and the updated value corresponding to each BIOS option name. For example, define the first string in each line as the option name, and the first string after the colon as the new value of the option value, and ignore the leading and trailing spaces.

[0045] In practice, a BIOS configuration file group and the corresponding configuration quantity for each BIOS configuration file are generated based on customer customization information; then, according to the corresponding configuration quantity of each BIOS configuration file, the server cluster to be configured is divided to obtain a server group corresponding to each BIOS configuration file, and the number of servers included in the server group matches the corresponding configuration quantity of the BIOS configuration file. As an example, the customer customization information is: the customer ordered 10 servers, among which 3 servers adopt the first configuration file and the other 7 servers adopt the second configuration file. The configuration file group in this example includes two configuration files, the first configuration file and the second configuration file, and the corresponding configuration quantities are 3 servers and 7 servers respectively. According to the corresponding configuration quantities of these two configuration files, the 10 servers to be configured are divided to obtain server group a corresponding to the first configuration file and server group b corresponding to the second configuration file. The corresponding configuration quantity of server group a is 3 servers, and the corresponding configuration quantity of server group b is 7 servers. Up to this point, the two configuration files and their corresponding configuration quantities in the configuration file group in this example correspond one by one to the server groups divided above, and the BIOS configuration information that needs to be modified in the corresponding server group can be modified in batches by modifying the BIOS configuration file.

[0046] Step 102, for each server group, send the pre-configured update script and the BIOS configuration file corresponding to the server group to each server in the server group. When the update script runs, obtain the current BIOS configuration information of the current server through the redfish interface, and parse the current BIOS configuration information to obtain the URL path corresponding to each BIOS option name in the current server. According to the URL path corresponding to each BIOS option name and the update value corresponding to each BIOS option name, construct an option value modification request to modify the BIOS option value of the current server, generate an update record, and send the update record to the configuration end.

[0047] In some embodiments, the execution entity has locally stored a pre-configured update script and the BIOS configuration file corresponding to each server group in the above server cluster. Among them, the script is an extension of a batch file and is a program saved in plain text. Usually, it can be temporarily called and executed by an application. As an example, the BIOS option values of one of the server groups are modified, for example, server group a. The remaining server groups in the above server cluster perform similar operations. Server group a includes servers 1, 2, and 3. For server group a, the pre-configured update script and the first configuration file corresponding to server group a are sent to each server in server group a. The update script is run, the current BIOS configuration information of servers 1, 2, and 3 is obtained through the redfish interface, and the current BIOS configuration information is parsed to obtain the URL path corresponding to each BIOS option name in servers 1, 2, and 3. An option value modification request is constructed through the URL path corresponding to each BIOS option name and the update value corresponding to each BIOS option name to modify the BIOS option values of servers 1, 2, and 3, and an update record is generated and sent to the configuration end.

[0048] In these embodiments, the needs of different customers for BIOS option configuration in factory server production are modified in batches. Specifically, the needs of different customers for the BIOS option configuration of the server are different. On this basis, by generating a BIOS configuration file group and the corresponding configuration quantity for each BIOS configuration file according to customer customization information, and then dividing the server cluster to be configured to obtain the server group corresponding to each BIOS configuration file, and then performing targeted configuration for each server group, it specifically solves the need to import a specific BIOS version into the production line production process to update the BIOS method to meet the needs of customers. Thereby, the efficiency of the needs of different customers for BIOS option configuration is improved, and timeliness is ensured.

[0049] In some embodiments, in order to further solve Technical Problem 2 described in the background art section, that is, "the existing method for determining eligible update records is backward, resulting in a complex process for submitting customer customization information", in some embodiments of the present invention, before obtaining the customer customization information corresponding to the server cluster to be configured, it further includes:

[0050] Step 1, obtain multiple update records within a historical time period. Among them, each update record includes an update timestamp, a customer identifier, an updated BIOS option name and the update value corresponding to the updated BIOS option name, a customer type, a server order quantity, and a business scenario.

[0051] In some embodiments, the executing entity has already stored multiple update records locally. Each update record includes an update timestamp, a customer identifier, an updated BIOS option name and the corresponding updated value of the updated BIOS option name, a customer type, the server order quantity, and a business scenario. The timestamp is used to represent a point in time. The customer identifier is used to uniquely identify the customer. By using the customer identifier, the customer can be better identified, so as to provide personalized products and services for the customer. The customer type can be divided according to different criteria, including: consumer customers, reseller customers, internal customers, and public welfare customers. In addition, according to comprehensive factors such as the value, needs, and preferences of the customer, it can also be divided into VIP customers, important customers, ordinary customers, loyal customers, old customers, new customers, and potential customers. The business scenario is the usage scenario of the server, for example, industrial control scenario, data storage. On this basis, multiple update records within a historical time period are obtained.

[0052] Step 2: According to the customer type included in each update record, divide the multiple update records into multiple update record groups, each update record group corresponding to one customer type, and the multiple update record groups corresponding to multiple customer types; according to the business scenario included in the update record, divide each update record group to obtain an update record subgroup corresponding to each customer type, and each update record subgroup corresponding to one business scenario.

[0053] In some embodiments, multiple update records are divided into multiple update record groups according to the customer types included in each of the above update records, so that each update record group corresponds to one customer type, and multiple update record groups correspond to multiple customer types; each update record group is further divided according to the business scenarios included in the above update records to obtain update record subgroups corresponding to each customer type, and each update record subgroup corresponds to one business scenario. As an example, within a certain historical time period, there are 20 update records. Among them, there are a total of 3 customer types, namely, customer type 1, customer type 2, and customer type 3. Then the corresponding update record groups are update record group 1, update record group 2, and update record group 3. Among them, update record group 1 has 10 update records, update record group 2 has 6 update records, and update record group 3 has 4 update records. The above 3 divided update record groups are further divided by the business scenarios included in each update record to obtain update record subgroups. Among them, in update record group 1, there are business scenarios 1, 2, and 3, corresponding to 5 update records, 3 update records, and 2 update records respectively. Then, the update record subgroups corresponding to business scenarios 1, 2, and 3 are update record subgroup 1, update record subgroup 2, and update record subgroup 3; in update record group 2, there are business scenarios 4 and 5, corresponding to 4 update records and 2 update records respectively. Then, the update record subgroups corresponding to business scenarios 4 and 5 are update record subgroup 4 and update record subgroup 5; in update record group 3, there is business scenario 6, corresponding to 4 update records. Then, the update record subgroup corresponding to business scenario 6 is update record subgroup 6. Finally, update record subgroups corresponding to each customer type are obtained, and each update record subgroup corresponds to one business scenario.

[0054] Step 3: When a configuration page acquisition request sent by a target user through a target user terminal is received, send the configuration page to the target user terminal so that the target user can submit customer customization information in the configuration page.

[0055] In some embodiments, the target user establishes a communication connection with the background server through the target user terminal and sends a configuration page acquisition request to the background server. After the background server receives the request, it sends the configuration page to the target user terminal so that the target user can submit customer customization information in the configuration page.

[0056] On this basis, obtaining the customer customization information corresponding to the server cluster to be configured includes:

[0057] When receiving the target customer identifier and the target business scenario submitted by the target user on the configuration page, query the target customer identifier in multiple update records. If there is an update record in the multiple update records that matches the target customer identifier, determine the matching update record as the target update record;

[0058] Send the target update record to the target user terminal, and control the target user terminal to display a historical configuration information viewing component and a historical configuration viewing prompt message on the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record on the configuration page.

[0059] In some embodiments, when the background server receives the target customer identifier and the target business scenario submitted by the target user on the configuration page, query for matching update records in multiple update records within a historical time period using the target customer identifier, and determine the matching update record as the target update record. Send the target update record to the target user terminal, and control the target user terminal to display a historical configuration information viewing component and a historical configuration viewing prompt message on the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record on the configuration page. As an example, the target user submits the target customer identifier 2 and the target business scenario 4 to the background server on the configuration page. Use the target customer identifier 2 to query in multiple update records within a historical time period to see if there is a target business scenario 4 under the corresponding customer type. If there is, then determine the subgroup of update records corresponding to this target business scenario 4 as the target update record. The background server sends this target update record to the target user terminal, and by controlling the target user terminal, displays a historical configuration information viewing component and a historical configuration viewing prompt message on the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record on the configuration page.

[0060] Obtaining the customer customization information corresponding to the server cluster to be configured further includes:

[0061] If there is no update record in the multiple update records that matches the target customer identifier, then determine the customer type corresponding to the target customer identifier as the target customer type, and determine the customer type with the highest matching degree with the target customer type from multiple customer types, and determine the customer type with the highest matching degree as the matching customer type;

[0062] According to the target business scenario, determine the business scenario with the highest matching degree with the target business scenario from multiple business scenarios corresponding to the matching customer type, and determine it as the matching business scenario;

[0063] Generate recommended configuration information according to the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information on the configuration page.

[0064] In some embodiments, among multiple update records within a historical time period, there is no update record in the server background that matches the target customer identifier and the target business scenario submitted by the target user on the configuration page. Then, the customer type corresponding to the above target customer identifier can be determined as the target customer type, and the customer type with the highest matching degree with the target customer type can be determined from multiple customer types and determined as the matching customer type. Then, through the above target business scenario, the business scenario with the highest matching degree with the above target business scenario can be determined from multiple business scenarios corresponding to the matching customer type and determined as the matching business scenario. Then, generate recommended configuration information from the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information on the configuration page. As an example, the target customer identifier A and the target business scenario a submitted by the target user on the configuration page cannot find a matching target update record in multiple update records within the historical time period of the server background. In the update records within the historical time period of the server background, the customer types are customer type A1, customer type B2, and customer type C3, and the corresponding update record groups are update record group A1, update record group B2, and update record group C3. The business scenarios are business scenario a1, business scenario b1, business scenario c1, and business scenario d1. Through the business scenario, each of the above update record groups is divided. Update record group A1 has business scenarios a1 and d1, which respectively correspond to update record subgroups a1 and d1. Update record group B1 has business scenario b1, and business scenario b1 corresponds to update record subgroup b1. Update record group C1 has business scenario c1, and business scenario c1 corresponds to update record subgroup c1. Determine the customer type corresponding to the target customer identifier A as the target customer type A, and find the customer type A1 with the highest matching degree with the target customer type A among the above customer type A1, customer type B1, and customer type C1, and determine the customer type A1 as the matching customer type; through the target business scenario a, find the business scenario a1 with the highest matching degree with the target business scenario a from the business scenarios a1 and d1 in the matching customer type A1, and determine the business scenario a1 as the matching business scenario; generate recommended configuration information from the update record subgroup a corresponding to the above matching business scenario a1; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information on the configuration page.

[0065] For each server group, send the pre-configured update script and the BIOS configuration file corresponding to the server group to each server in the server group, including:

[0066] According to the manufacturer information of each server, select an update script that matches the manufacturer information of each server from the pre-configured update script library, and send the matching update script to the corresponding server.

[0067] In some embodiments, in practice, servers produced by different manufacturers need to be configured. Then, different manufacturers correspond to different server groups, and the background server will pre-configure matching update scripts for different manufacturers. When needed, just send the matching update scripts to the servers corresponding to different manufacturers.

[0068] In these embodiments, the target user sends a configuration page acquisition request to the background server through the target user terminal. The background server sends the configuration page to the target user terminal, enabling the target user to submit customer customization information in the configuration page. The background server determines the matching target update record, sends the target update record to the target user terminal, and controls the target user terminal to display a historical configuration information viewing component and a historical configuration viewing prompt message in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page. Thus, during the submission process of customer customization information, eligible update records are displayed on the target user terminal, providing reference information for user customization and facilitating the quick submission of customer customization information.

[0069] In some embodiments, in order to further solve Technical Problem 3 described in the background art section, that is, "when there is a problem with the server configuration during the BIOS configuration information process, the troubleshooting method is insufficient", in some embodiments of the present invention,

[0070] Each update record further includes the configuration duration for each BIOS option; on this basis, the method of the present invention further includes:

[0071] Step 1, according to multiple update records, calculate the average configuration duration for the BIOS option.

[0072] In some embodiments, the target user can batch modify the BIOS configuration information to be modified in the corresponding server group by modifying the BIOS configuration file on the target user terminal. Inevitably, there will be problems with the configurations of some servers during the process of BIOS configuration information. Then, it is necessary to find out which server has a configuration problem and solve it in time. A relatively intuitive way to know which server has a configuration problem is to count the average configuration duration for BIOS options. The configuration durations corresponding to the same BIOS option are the same.

[0073] Step 2, during the running of the update script, receive the configuration progress information sent by each server in the server cluster to be configured, and count the actual configuration duration of each server in the server cluster to be configured for each BIOS option.

[0074] In some embodiments, the target user runs the update script on the target user terminal, receives the configuration progress information sent by each background server, and counts the actual configuration duration of each server in the server cluster to be configured for each BIOS option.

[0075] Step 3, if the actual configuration duration is greater than the average configuration duration, determine the corresponding BIOS option as the BIOS option to be troubleshot, and determine the corresponding server as the server to be troubleshot.

[0076] In some embodiments, for the servers in the server cluster to be configured whose actual configuration duration is greater than the average configuration duration, determine the BIOS options corresponding to the servers in the server cluster to be configured as the BIOS options to be troubleshot, and determine the corresponding servers as the servers to be troubleshot.

[0077] Step 4, send the information of the BIOS option to be troubleshot and the server to be troubleshot to the troubleshooting terminal, so that the troubleshooting personnel can troubleshoot the BIOS option to be troubleshot and the server to be troubleshot.

[0078] In some embodiments, the servers in the server cluster to be configured send the information of the BIOS option to be troubleshot and the server to be troubleshot to the troubleshooting terminal, so that the troubleshooting personnel can troubleshoot the BIOS option to be troubleshot and the server to be troubleshot.

[0079] In these embodiments, by counting the actual configuration duration of each server in the server cluster to be configured for each BIOS option, the BIOS option to be troubleshot and the server to be troubleshot are determined, thereby optimizing the troubleshooting method and avoiding omission of problems.

[0080] The above description is only some preferred embodiments of the present invention and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in the present invention is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above inventive concept. For example, the technical solutions formed by mutually replacing the above features with the technical features (but not limited to) disclosed in the present invention that have similar functions.

Claims

1. A method for batch modification of BIOS option values based on the Redfish interface, characterized in that, Including: Obtain customer customization information corresponding to the server cluster to be configured, including: querying for matching update records among multiple update records of the target customer identifier in the historical time period; if there are no matching update records, determining the matching customer type; determining the business scenario with the highest matching degree with the target business scenario from multiple business scenarios corresponding to the matching customer type, and determining it as the matching business scenario; generating recommended configuration information according to the sub-group of update records corresponding to the matching business scenario; if there is no matching business scenario, selecting the sub-group of update records closest to the current time from multiple business scenarios and generating recommended configuration information; each update record group corresponds to a customer type; each update record sub-group corresponds to a business scenario; Generate a BIOS configuration file group and the corresponding configuration quantity for each BIOS configuration file according to the customer customization information; divide the server cluster to be configured to obtain a server group corresponding to each BIOS configuration file; For each server group, select a matching update script from a pre-configured update script library according to the vendor information of each server; send the pre-configured update script and the corresponding BIOS configuration file to each server. When the update script runs, obtain the current BIOS configuration information through the redfish interface, parse to obtain the URL path corresponding to each BIOS option name, construct an option value modification request according to the URL path and update value corresponding to each BIOS option name to modify the BIOS option value, generate an update record and send it to the configuration end; During the running of the update script, receive the configuration progress information sent by each server in the server cluster to be configured; count the actual configuration duration of each server for each BIOS option; if the actual configuration duration is greater than the average configuration duration, determine the BIOS option to be investigated and the server to be investigated.

2. The method for batch modification of BIOS option values based on the Redfish interface according to claim 1, wherein Before obtaining the customer customization information corresponding to the server cluster to be configured, it further includes: Obtain multiple update records in the historical time period, where each update record includes an update timestamp, a customer identifier, an updated BIOS option name and the corresponding update value of the updated BIOS option name, a customer type, a server order quantity, and a business scenario; Divide the multiple update records into multiple update record groups according to the customer type included in each update record, each update record group corresponds to a customer type, and the multiple update record groups correspond to multiple customer types; divide each update record group according to the business scenario included in the update record to obtain an update record sub-group corresponding to each customer type, and each update record sub-group corresponds to a business scenario; and Before obtaining the customer customization information corresponding to the server cluster to be configured, the method further includes: when receiving a configuration page acquisition request sent by a target user through a target user terminal, sending the configuration page to the target user terminal so that the target user submits customer customization information in the configuration page; and The obtaining of the customer customization information corresponding to the server cluster to be configured includes: When receiving the target customer identifier and the target business scenario submitted by the target user in the configuration page, query the target customer identifier in the multiple update records. If there is an update record in the multiple update records that matches the target customer identifier, determine the matching update record as the target update record; Send the target update record to the target user terminal, and control the target user terminal to display a historical configuration information viewing component and a historical configuration viewing prompt message in the configuration page. When the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the target update record in the configuration page.

3. The method for batch modification of BIOS option values based on the redfish interface according to claim 2, wherein, The obtaining of the customer customization information corresponding to the server cluster to be configured further includes: If there is no update record in the multiple update records that matches the target customer identifier, determine the customer type corresponding to the target customer identifier as the target customer type, and determine the customer type with the highest matching degree with the target customer type from the multiple customer types, and determine the customer type with the highest matching degree as the matching customer type; According to the target business scenario, determine the business scenario with the highest matching degree with the target business scenario from the multiple business scenarios corresponding to the matching customer type, and determine it as the matching business scenario; Generate recommended configuration information according to the update record subgroup corresponding to the matching business scenario; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

4. The method for batch modification of BIOS option values based on the redfish interface according to claim 3, characterized in that, The obtaining of the customer customization information corresponding to the server cluster to be configured further includes: If there is no business scenario in the multiple business scenarios corresponding to the matching customer type that matches the target business scenario, for each update record subgroup corresponding to each business scenario in the multiple business scenarios, determine the average update timestamp corresponding to each update record subgroup; According to the average update timestamp corresponding to each update record subgroup and the current time, select the update record subgroup closest to the current time from the multiple business scenarios, and generate recommended configuration information according to the update record subgroup closest to the current time; when the target user performs a preset user operation on the historical configuration information viewing component, the target user terminal displays the recommended configuration information in the configuration page.

Images