Field replaceable unit (FRU) management method, device and system

Abstract

The present application provides a method, device and system for managing a field replaceable unit (FRU), and relates to the field of computer technology. The method is used for a first device, and on the basis that the first device includes a target FRU, the first device automatically responds to the creation request after receiving a creation request, and automatically creates a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU carried in the creation request, and then manages the target FRU based on the created configuration file of the target FRU. Since the first device can automatically create a configuration file of the target FRU based on the creation request, compared with the related technology that requires the development, testing, version release and other processes of the firmware program before the configuration file of the target FRU can be configured for the first device, it not only helps to reduce the cost of replacing the target FRU, but also helps to improve the efficiency of replacing the target FRU.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device and system for managing a field replaceable unit (FRU). Background Art

[0002] A field replaceable unit (FRU) is a replaceable component on a hardware device. After a hardware device replaces a new FRU, if a management component of the hardware device wants to manage the new FRU, it is necessary to configure a configuration file of the new FRU for the management component.

[0003] In the related art, the way to configure the configuration file of the new FRU for the management component is usually to upgrade the firmware program of the management component, wherein the firmware program of the management component usually needs to go through the processes of development, testing, version release, etc. This results in that when the FRUs on multiple hardware devices are replaced at the same time, the firmware programs of the management components of the multiple hardware devices need to be developed, tested, and released, which is not only extremely costly, but also very inefficient. Summary of the invention

[0004] The embodiments of the present application provide a FRU management method, device, and system, which can automatically create a configuration file for the FRU, which not only helps to reduce the cost of replacing the FRU, but also helps to improve the efficiency of replacing the FRU.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a field replaceable unit (FRU) management method is provided, which is used for a first device, and the first device includes a target FRU; the method includes: receiving a creation request, the creation request is used to request the creation of a configuration file of the target FRU; the creation request includes the configuration content in the configuration file of the target FRU; in response to the creation request, creating the configuration file of the target FRU based on the configuration content in the configuration file of the target FRU; and managing the target FRU based on the configuration file of the target FRU.

[0007] In this embodiment, on the basis that the first device includes the target FRU, after receiving the creation request, since the creation request carries the configuration content in the configuration file of the target FRU, the first device automatically creates the configuration file of the target FRU in response to the creation request based on the configuration content in the configuration file of the target FRU carried in the creation request, and then manages the target FRU based on the created configuration file of the target FRU. Since the first device can automatically create the configuration file of the target FRU based on the creation request and the configuration content in the configuration file of the target FRU carried in the creation request, compared with the related art that requires the development, testing, version release and other processes of the firmware program before the configuration file of the target FRU can be configured for the first device, it not only helps to reduce the cost of replacing the target FRU, but also helps to improve the efficiency of replacing the target FRU.

[0008] In a possible implementation, the creation request is sent by the client device in response to a creation instruction, the creation instruction is used to instruct to send a creation request for a configuration file of the target FRU to the first device, and the client device stores configuration content in the configuration file of the target FRU.

[0009] In this implementation, when the user determines that the first device needs to use the configuration file of the target FRU, a creation instruction is used to instruct the client device to send a creation request to the first device, so that the first device can automatically create the configuration file of the target FRU. This not only saves the time for the first device to obtain the configuration file from other devices, but also helps to increase the necessity of the configuration file of the target FRU created by the first device, and avoids creating a configuration file when the configuration file of the target FRU is not needed.

[0010] In another possible implementation, the method further includes: receiving a query request sent by a client device, the query request being used to request a query of the FRU type supported by the first device; in response to the query request, sending a target FRU type to the client device; wherein the target FRU type is a FRU type supported by the first device.

[0011] In this implementation, by receiving a query request sent by the client and returning the FRU types supported by the first device to the client in response to the query request, the client device can understand the FRU types supported by the first device. This helps to create a configuration file requested by the creation request that matches the supported FRU types of the first device, thereby helping to ensure that the first device can successfully use the created configuration file.

[0012] In another possible implementation, the method also includes: receiving a first start request sent by a client device, the first start request being used to request to start a FRU configuration service of the first device so that the first device supports creating a configuration file for the target FRU; in response to the first start request, setting the FRU configuration management service of the first device to an on state.

[0013] In this implementation, the first device sets the FRU configuration management service of the first device to an on state in response to the received first on request, so that the first device supports the creation of a configuration file for the target FRU. Since the first device supports the creation of a configuration file for the target FRU only when the FRU configuration management service is set to an on state, this helps to avoid the creation of a configuration file without permission, thereby helping to ensure the security of FRU management.

[0014] In another possible implementation, the method further includes: sending an acquisition request to a second device when the first device is not configured with a configuration file of the target FRU; the second device stores the configuration file of the target FRU, and the acquisition request is used to request the configuration content in the configuration file; wherein the creation request is sent by the second device in response to the acquisition request.

[0015] In this implementation, when the first device has not configured the configuration file of the target FRU, the first device actively sends an acquisition request to the second device to request to obtain the configuration content in the configuration file of the target FRU. This helps to improve the convenience and automation of the second device in creating the configuration file of the target FRU.

[0016] In another possible implementation, when the first device is not configured with the configuration file of the target FRU, sending an acquisition request to the second device includes: sending an acquisition request to the second device in response to a received target instruction; the target instruction is used to instruct to obtain the configuration content in the configuration file of the target FRU from the second device, and the target instruction is sent when the first device is not configured with the configuration file of the target FRU.

[0017] In this implementation, the first device sends an acquisition request to the second device in response to receiving the target instruction sent by the client. In this way, when the user determines that the first device needs to use the configuration file of the target FRU, the first device can be instructed to send an acquisition request to the second device. This helps to increase the necessity of obtaining configuration content.

[0018] In another possible implementation, when the first device is not configured with a configuration file of the target FRU, sending an acquisition request to the second device includes: sending an acquisition request to the second device in response to a target scan result; the target scan result includes a configuration file of the target FRU not scanned on the first device.

[0019] In this implementation, the first device automatically sends an acquisition request to the second device in response to the target scanning result without user participation, which helps to improve the convenience and automation of configuration content acquisition.

[0020] In another possible implementation, in response to a creation request, a configuration file for the target FRU is created based on the configuration content in the configuration file of the target FRU, including: if the configuration content in the configuration file meets a preset condition, in response to the creation request, a configuration file for the target FRU is created based on the configuration content in the configuration file.

[0021] In this implementation, by setting up a response to a creation request if the configuration content in the configuration file meets the preset conditions, this helps to avoid creating a configuration file using non-compliant configuration content, which may cause the target FRU to function abnormally when managing the target FRU based on the created configuration file.

[0022] In another possible implementation, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name; wherein the attribute name of the configuration content includes at least one of the manufacturer identification, PN component identification, SN serial number, model, name, FRU type and model identification of the target FRU.

[0023] In this implementation, whether the configuration content meets the preset condition is determined by checking whether the attribute name of the configuration content is the same as the preset attribute name, which helps to ensure the integrity of the configuration content parsed from the configuration file.

[0024] In another possible implementation, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type; wherein the attribute name of the configuration content includes at least one of the manufacturer identifier, PN component identifier, SN serial number, model, and name of the target FRU.

[0025] In this implementation, whether the configuration content meets the preset conditions is determined by whether the attribute name of the configuration content is the same as the preset attribute name, and whether the field type of the configuration content is the same as the preset field type. This helps to ensure the accuracy and completeness of the configuration content parsed from the configuration file.

[0026] In another possible implementation, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the attribute value of the configuration content is the same as the preset attribute value; wherein the attribute name of the configuration content includes the model identification and / or FRU type of the target FRU.

[0027] In this implementation, whether the configuration content meets the preset conditions is determined by whether the attribute name of the configuration content is the same as the preset attribute name, and whether the attribute value of the configuration content is the same as the preset attribute value. This helps to ensure the accuracy and completeness of the configuration content parsed from the configuration file.

[0028] In another possible implementation, the acquisition request includes the name of the target FRU, and the acquisition request is used to request to acquire the configuration content in the configuration file indicated by the name of the target FRU.

[0029] In this implementation, since the name of the FRU configuration file is the same as the name of the FRU, the acquisition request is set to include the name of the target FRU, and a request is made to obtain the configuration content in the configuration file indicated by the name of the target FRU. This helps to ensure the accuracy of the acquired configuration content when it is necessary to obtain the configuration content in the configuration file of a specific FRU.

[0030] In another possible implementation, the acquisition request includes a model identifier of the first device, and the acquisition request is used to request to obtain configuration content in a configuration file supported by the model identifier, and the configuration file of the target FRU is a configuration file supported by the model identifier.

[0031] In this implementation, the acquisition request is set to include the model identification of the first device, and a request is made to obtain the configuration content in the configuration file indicated by the model identification. In this way, when multiple FRUs are replaced in the first device and the configuration content in the configuration files of multiple FRUs needs to be obtained, it helps to improve the efficiency of obtaining the configuration content in the configuration files of multiple FRUs.

[0032] In another possible implementation, when the acquisition request includes the model identification of the first device, the acquisition request may also include a target FRU type, where the target FRU type is a FRU type supported by the first device, and the acquisition request is used to request configuration content in a configuration file belonging to the target FRU type, where the configuration file of the target FRU is a configuration file belonging to the target FRU type.

[0033] In this implementation, the acquisition request is set to include the target FRU type, which is used to indicate that the configuration file requested by the acquisition request should belong to the target FRU type. This helps to ensure that the configuration file of the target FRU obtained by the first device from the second device can match the first device, thereby helping to ensure that the first device can use the obtained configuration file normally.

[0034] In another possible implementation, the configuration content in the configuration file is in JSON format; receiving a creation request includes: receiving a creation request based on a first interface; and the first interface supports transmission of data in JSON format.

[0035] In this implementation, since the configuration file of the FRU is a JSON file and the configuration content in the configuration file of the FRU is in JSON format, the first device receives the configuration content in the configuration file of the target FRU through the first interface, and the first interface supports the transmission of JSON format files. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0036] In another possible implementation, the method further includes: sending a second enable request to the second device, where the second enable request is used to request to enable the FRU configuration management service of the second device so that the second device supports exporting the configuration content in the configuration file.

[0037] In this implementation, by setting the second device to configure the FRU configuration management service, when the FRU configuration management service is in the on state, the second device can export the configuration file of the target FRU. When it is in the off state, the second device cannot export the configuration file of the target FRU. This helps to ensure the security of the configuration file of the FRU in the second device.

[0038] In another possible implementation, the method further includes: setting the FRU configuration management server of the first device to an on state, so that the first device supports creation of a configuration file of the target FRU.

[0039] In this implementation, by setting the FRU configuration management server of the first device to an on state, the first device supports creating a configuration file for the target FRU, which helps avoid creating a configuration file without permission, thereby helping to ensure the security of FRU management.

[0040] In a second aspect, a field replaceable unit (FRU) management method is provided, which is used for a second device, in which a configuration file of a target FRU is stored; the method includes: receiving an acquisition request; the acquisition request is used to request to obtain the configuration content in the configuration file of the target FRU; in response to the acquisition request, sending a creation request to the device that sent the acquisition request; the creation request includes the configuration content in the configuration file of the target FRU, the creation request is used to request to create the configuration file of the target FRU, and the configuration file of the target FRU is used to manage the target FRU on the device that sends the acquisition request; or in response to the acquisition request, sending the configuration content in the configuration file of the target FRU to the device that sends the acquisition request.

[0041] In this solution, when the configuration file of the target FRU is stored in the second device, the second device returns the creation request or the configuration content in the configuration file of the target FRU in response to the received acquisition request, thereby exporting the configuration content in the configuration file of the target FRU, and then other devices can use the configuration content in the configuration file of the target FRU to create the configuration file of the target FRU. Compared with the related technology that requires the development, testing, version release and other processes of the firmware program to configure the configuration file of the target FRU for the first device, it not only helps to reduce the cost of replacing the target FRU, but also helps to improve the efficiency of replacing the target FRU.

[0042] In a possible implementation, the acquisition request is sent by the client device in response to the acquisition instruction.

[0043] In another possible implementation, the acquisition request is sent by the first device when the first device is not configured with a configuration file of the target FRU.

[0044] In another possible implementation, responding to the acquisition request includes: if the configuration content in the configuration file meets a preset condition, responding to the acquisition request.

[0045] In this implementation, when the configuration content in the configuration file meets the preset conditions, the configuration content in the configuration file is sent to the server in response to the acquisition request. This helps to avoid the configuration content belonging to a non-FRU configuration file, thereby improving the accuracy and security of the exported configuration content.

[0046] In another possible implementation, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name; wherein the attribute name of the configuration content includes at least one of the manufacturer identification, PN component identification, SN serial number, model, name, FRU type and model identification of the target FRU.

[0047] In another possible implementation, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type; wherein the attribute name of the configuration content includes at least one of the manufacturer identifier, PN component identifier, SN serial number, model, and name of the target FRU.

[0048] In another possible implementation, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the attribute value of the configuration content is the same as the preset attribute value; wherein the attribute name of the configuration content includes the model identification and / or FRU type of the target FRU.

[0049] In another possible implementation, the acquisition request includes the name of the target FRU, and the acquisition request is used to request to obtain the configuration file indicated by the name of the target FRU.

[0050] In another possible implementation, the acquisition request includes a model identifier of the first device, and the acquisition request is used to request to obtain a configuration file supported by the model identifier, and the configuration files supported by the model identifier include a configuration file of a target FRU.

[0051] In another possible implementation, when the acquisition request includes the model identification of the first device, the acquisition request may also include a target FRU type, where the target FRU type is a FRU type supported by the first device, and the acquisition request is used to request a configuration file belonging to the target FRU type.

[0052] In another possible implementation, the configuration content in the configuration file is in JSON format; in response to the acquisition request, a creation request is sent to the device that sends the acquisition request, including: in response to the acquisition request, based on the second interface, a creation request is sent to the device that sends the acquisition request; the second interface supports the transmission of data in JSON format.

[0053] In this implementation, since the configuration file of the FRU is a JSON file and the configuration content in the configuration file of the FRU is in JSON format, the second device transmits the configuration content in the configuration file of the target FRU through the second interface, and the second interface supports the transmission of JSON format files. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0054] In another possible implementation, the configuration content in the configuration file is in JSON format; in response to the acquisition request, the configuration content in the configuration file of the target FRU is sent to the device that sends the acquisition request, including: in response to the acquisition request, based on the second interface, the configuration content in the configuration file of the target FRU is sent to the device that sends the acquisition request.

[0055] In this implementation, since the configuration file of the FRU is a JSON file and the configuration content in the configuration file of the FRU is in JSON format, the second device transmits the configuration content in the configuration file of the target FRU through the second interface, and the second interface supports the transmission of JSON format files. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0056] In another possible implementation, the method also includes: receiving a second start request sent by the first device, the second start request is used to request to start the FRU configuration management service of the second device so that the second device supports exporting the configuration content in the configuration file; in response to the second start request, setting the FRU configuration management service of the second device to an on state.

[0057] In this implementation, the second device sets the FRU configuration management service of the second device to an on state in response to the received second enable request, thereby enabling the second device to support exporting the configuration content in the configuration file. This helps avoid exporting the configuration content in the configuration file on the second device without permission, thereby helping to ensure the security of the FRU configuration file on the second device.

[0058] In another possible implementation, the method also includes: receiving a third enable request sent by the client device, the second enable request being used to request enabling the FRU configuration management service of the second device so that the second device supports exporting the configuration content in the configuration file; and in response to the second enable request, setting the FRU configuration management service of the second device to an enabled state.

[0059] In this implementation, the second device sets the FRU configuration management service of the second device to an on state in response to the received third creation request, so that the second device supports exporting the configuration content in the configuration file. This helps to avoid exporting the configuration content in the configuration file on the second device without permission, thereby helping to ensure the security of the FRU configuration file on the second device.

[0060] In a third aspect, a field replaceable unit (FRU) management method is provided for a client device, wherein the client device stores configuration content in a configuration file of a target FRU; the method comprises: in response to a creation instruction, sending a creation request to a first device; the creation request is used to request creation of a configuration file of the target FRU; the creation request includes the configuration content in the configuration file.

[0061] In this solution, when the configuration content in the configuration file of the target FRU is stored in the client device, the client device actively sends a creation request to the first device, so that the first device can automatically create the configuration file of the target FRU based on the configuration content in the configuration file of the target FRU. Compared with the related technology that requires the development, testing, version release and other processes of the firmware program to configure the configuration file of the target FRU for the first device, it not only helps to reduce the cost of replacing the target FRU, but also helps to improve the efficiency of replacing the target FRU.

[0062] In a possible implementation, the method further includes: sending an acquisition request to the second device in response to the acquisition instruction; the acquisition request is used to request the configuration content in the configuration file of the target FRU; and receiving the configuration content in the configuration file of the target FRU sent by the second device.

[0063] In this implementation, the client device obtains the configuration content in the configuration file of the target FRU from the second device by sending an acquisition request to the second device, and then can use the configuration content in the configuration file of the target FRU to create the configuration file of the target FRU. Compared with the related technology, it is necessary to develop, test, and release the firmware program in order to obtain the configuration content in the FRU configuration file. This not only helps to reduce the cost of obtaining the configuration content, but also helps to improve the efficiency of obtaining the configuration content.

[0064] In another possible implementation, the acquisition request includes the name of the target FRU, and the acquisition request is used to request to acquire the configuration content in the configuration file indicated by the name of the target FRU.

[0065] In another possible implementation, the acquisition request includes a model identifier of the first device, and the acquisition request is used to request to obtain configuration content in a configuration file supported by the model identifier, and the configuration file of the target FRU is a configuration file supported by the model identifier.

[0066] In another possible implementation, when the acquisition request includes the model identification of the first device, the acquisition request may also include a target FRU type, where the target FRU type is a FRU type supported by the first device, and the acquisition request is used to request configuration content in a configuration file belonging to the target FRU type, where the configuration file of the target FRU is a configuration file belonging to the target FRU type.

[0067] In another possible implementation, in response to a creation instruction, sending a creation request to the first device includes: in response to the creation instruction, sending a creation request to the first device based on a third interface; the third interface supports transmission of data in JSON format.

[0068] In this implementation, since the configuration file of the FRU is a JSON file and the configuration content in the configuration file of the FRU is in JSON format, the client device sends the configuration content in the configuration file of the target FRU to the first device through the third interface, and the third interface supports the transmission of JSON format files. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0069] In another possible implementation, in response to a creation instruction, a creation request is sent to the first device, including: sending a query request to the first device, the query request is used to request a query of the FRU type supported by the first device; receiving a target FRU type sent by the first device, the target FRU type is a FRU type supported by the first device; in response to the creation instruction, based on the target FRU type, a creation request is sent to the first device; wherein the target FRU belongs to the target FRU type.

[0070] In this implementation, a query request is sent to the first device, and based on the FRU type supported by the queried first device, a creation request is sent to the first device. This helps to match the configuration file requested by the creation request with the supported FRU type of the first device, thereby helping to ensure that the first device can successfully use the created configuration file.

[0071] In another possible implementation, the method further includes: sending a first enable request to the first device, where the first enable request is used to request to enable a FRU configuration service of the first device so that the first device supports creation of a configuration file of the target FRU.

[0072] In this implementation, the client device is set to send a first enable request to the first device, so that the first device supports the creation of a configuration file for the target FRU. Since the first device supports the creation of a configuration file for the target FRU only when the FRU configuration management service is set to the enabled state, this helps avoid the creation of configuration files without permission, thereby helping to ensure the security of FRU management.

[0073] In another possible implementation, the method further includes: sending a third enable request to the second device to request enabling of the FRU configuration management service of the second device, so that the second device supports exporting the configuration content in the configuration file.

[0074] In this implementation, a third enable request is sent to the second device so that the second device supports exporting the configuration content in the configuration file. Since the second device supports exporting the configuration content of the configuration file only when the FRU configuration management service is set to the enabled state, this helps avoid exporting the configuration content of the configuration file without permission, thereby helping to ensure the security of the configuration file.

[0075] In a fourth aspect, a field replaceable unit (FRU) management device is provided, the device comprising: a functional unit for executing any one of the methods provided in the first aspect, the actions performed by each functional unit are implemented by hardware or by hardware executing corresponding software implementations. For example, the FRU management device may include: a receiving unit, a creating unit, and a managing unit; the receiving unit is used to receive a creation request, the creation request is used to request the creation of a configuration file of a target FRU; the creation request includes the configuration content in the configuration file of the target FRU; the creation unit is used to create a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU in response to the creation request; the management unit is used to manage the target FRU based on the configuration file of the target FRU.

[0076] In a fifth aspect, a field-replaceable FRU management device is provided, the device comprising: a functional unit for executing any one of the methods provided in the second aspect, the actions performed by each functional unit are implemented by hardware or by hardware executing corresponding software implementations. For example, the FRU management device may include: a receiving unit and a sending unit; the receiving unit is used to receive an acquisition request; the acquisition request is used to request to obtain the configuration content in the configuration file of the target FRU; the sending unit is used to send a creation request to the device that sent the acquisition request in response to the acquisition request; the creation request includes the configuration content in the configuration file of the target FRU, the creation request is used to request to create the configuration file of the target FRU, and the configuration file of the target FRU is used to manage the target FRU on the device that sent the acquisition request; or in response to the acquisition request, send the configuration content in the configuration file of the target FRU to the device that sent the acquisition request.

[0077] In a sixth aspect, a field replaceable unit (FRU) management device is provided, the device comprising: a functional unit for executing any one of the methods provided in the third aspect, the actions performed by each functional unit are implemented by hardware or by hardware executing corresponding software. For example, the FRU management device may include: a sending unit; the sending unit is used to send a creation request to the first device in response to a creation instruction; the creation request is used to request the creation of a configuration file of the target FRU; the creation request includes the configuration content in the configuration file.

[0078] In the seventh aspect, a field-replaceable FRU management system is provided, including: a first device and a second device, the first device being communicatively connected to the second device, and the second device storing a configuration file of a target FRU; the first device being used to send an acquisition request to the second device when the configuration file of the target FRU is not configured on the first device; the acquisition request is used to request to obtain the configuration content in the configuration file; the second device being used to receive the acquisition request sent by the first device; the acquisition request is used to request to obtain the configuration content in the configuration file; the second device being also used to send a creation request to the first device in response to the acquisition request; the creation request is used to request to create a configuration file of the target FRU, and the creation request includes the configuration content in the configuration file; the first device is also used to receive the creation request sent by the second device, and the creation request is used to request to create a configuration file of the target FRU; the first device is also used to create a configuration file of the target FRU based on the configuration content in the configuration file in response to the creation request.

[0079] In an eighth aspect, a field-replaceable FRU management system is provided, comprising: a first device, a second device and a client device; the client device is communicatively connected to the first device and the second device respectively; the second device is used to receive an acquisition request from the client device; the acquisition request is used to request to acquire the configuration content in the configuration file of the target FRU; the second device is also used to send the configuration content in the configuration file of the target FRU to the client device in response to the acquisition request; the client device is used to send a creation request to the first device in response to a creation instruction; the creation request is used to request to create a configuration file of the target FRU; the creation request includes the configuration content in the configuration file; the first device is used to receive the creation request, and in response to the creation request, create the configuration file of the target FRU based on the configuration content in the configuration file; the first device is also used to manage the target FRU based on the configuration file of the target FRU.

[0080] In a ninth aspect, a first computer device is provided, comprising: a processor and a memory, wherein the processor is connected to the memory, the memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, thereby implementing any one of the methods provided in the first aspect.

[0081] In a tenth aspect, a second computer device is provided, comprising: a processor and a memory, wherein the processor is connected to the memory, the memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, thereby implementing any one of the methods provided in the second aspect.

[0082] In an eleventh aspect, a client device is provided, comprising: a processor; the processor and a memory, wherein the processor is connected to the memory. The memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, thereby implementing any one of the methods provided in the third aspect.

[0083] In the twelfth aspect, a chip is provided, comprising: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to run the code instructions to execute any one of the methods provided in the first aspect above.

[0084] In the thirteenth aspect, a chip is provided, comprising: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to run the code instructions to execute any one of the methods provided in the second aspect above.

[0085] In a fourteenth aspect, a chip is provided, comprising: a processor and an interface circuit; the interface circuit is used to receive code instructions and transmit them to the processor; the processor is used to run the code instructions to execute any one of the methods provided in the third aspect above.

[0086] In a fifteenth aspect, a computer-readable storage medium is provided, which stores computer execution instructions. When the computer execution instructions are executed on a computer device, the computer device executes any one of the methods provided in the first aspect.

[0087] In the sixteenth aspect, a computer-readable storage medium is provided, which stores computer execution instructions. When the computer execution instructions are executed on a computer device, the computer device executes any one of the methods provided in the second aspect above.

[0088] In the seventeenth aspect, a computer-readable storage medium is provided, which stores computer execution instructions. When the computer execution instructions are executed on a computer device, the computer device executes any one of the methods provided in the third aspect above.

[0089] In an eighteenth aspect, a computer program product is provided, comprising: computer execution instructions, which, when executed on a computer, cause the computer to execute any one of the methods provided in the first aspect.

[0090] In the nineteenth aspect, a computer program product is provided, comprising: computer execution instructions, which, when executed on a computer, cause the computer to execute any one of the methods provided in the second aspect.

[0091] In the twentieth aspect, a computer program product is provided, comprising: computer execution instructions, which, when executed on a computer, cause the computer to execute any one of the methods provided in the third aspect.

[0092] Among them, the technical effects brought about by any implementation method in the second to twentieth aspects can refer to the technical effects brought about by different implementation methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] Figure 1A A schematic diagram of a system structure provided in an embodiment of the present application;

[0094] Figure 1B A schematic diagram of the structure of a device provided in an embodiment of the present application;

[0095] Figure 2A A schematic diagram of another system architecture provided for an embodiment of the present application;

[0096] Figure 2B A schematic diagram of the structure of another device provided in an embodiment of the present application;

[0097] Figure 3 A flowchart of a FRU management method provided in an embodiment of the present application;

[0098] Figure 4 A schematic diagram of the structure of another device provided in an embodiment of the present application;

[0099] Figure 5 A schematic diagram of the structure of another device provided in an embodiment of the present application;

[0100] Figure 6 A flowchart of another FRU management method provided in an embodiment of the present application;

[0101] Figure 7 A schematic diagram of a FRU management device provided in an embodiment of the present application;

[0102] Figure 8 A schematic diagram of another FRU management device provided in an embodiment of the present application;

[0103] Fig. 9 A schematic diagram of another FRU management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0104] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0105] In the description of this application, unless otherwise specified, " / " indicates that the objects associated with each other are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is merely a description of the association relationship between associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0106] Furthermore, in the description of this application, unless otherwise specified, "plurality" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0107] In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit the differences. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0108] First, the application scenarios of the embodiments of the present application are exemplarily introduced.

[0109] FRU is a replaceable component on a hardware device. After a hardware device replaces a new FRU, if the management component of the hardware device wants to manage the new FRU, it is necessary to configure the configuration file of the new FRU for the management component.

[0110] In the related art, the way to configure the configuration file of the new FRU for the management component is usually to upgrade the firmware program of the management component, wherein the firmware program of the management component usually needs to go through the processes of development, testing, version release, etc. This results in that when the FRUs on multiple hardware devices are replaced at the same time, the firmware programs of the management components of the multiple hardware devices need to be developed, tested, and released, which is not only extremely costly, but also very inefficient.

[0111] In view of this, an embodiment of the present application provides a FRU management method for a first device, where the first device includes a target FRU, and after receiving a creation request, the first device creates a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU carried in the creation request, and then manages the target FRU based on the created configuration file of the target FRU. Since the first device can automatically create a configuration file of the target FRU based on a creation request carrying the configuration content in the configuration file of the target FRU, compared with the related art that requires the development, testing, version release and other processes of the firmware program before the configuration file of the target FRU can be configured for the first device, not only the cost of replacing the target FRU is reduced, but also the efficiency of replacing the target FRU is improved.

[0112] Secondly, the system architecture of the embodiment of the present application is exemplarily introduced.

[0113] like Figure 1A As shown, a system architecture diagram provided in an embodiment of the present application.

[0114] See also Figure 1A The system architecture includes at least one first device and a second device, wherein each first device in the at least one first device is communicatively connected with the second device.

[0115] Exemplarily, the at least one first device includes a first device 1, ..., a first device N, where N is a positive integer greater than 1.

[0116] Optionally, the product form of the first device and the second device may be a terminal device or a network device.

[0117] Terminal devices include mobile phones, augmented reality (AR) devices, virtual reality (VR) devices, personal digital assistants (PDA), ultra-mobile personal computers (UMPC), tablet computers, laptops, netbooks, desktop computers, all-in-one computers, etc.

[0118] The network devices include servers, etc. Among them, the server can be a physical or logical server, or two or more physical or logical servers with different responsibilities can cooperate with each other to realize various functions of the server.

[0119] Optionally, the system architecture may further include a client device, wherein the client device is respectively communicatively connected with each first device in the at least one first device.

[0120] In some embodiments, the client device may be a terminal device. A user may send a target instruction, etc. to the first device through the client device.

[0121] Based on the above, in an application scenario, the first device is a first server, the second device is a second server, and the client device is a terminal device. The user sends a target instruction to the first server through the terminal device to instruct the first server to send a request to the second server to request to obtain the configuration content in the FRU configuration file on the second server.

[0122] Afterwards, the second server sends a creation request to the first device in response to the acquisition request, and the creation request includes the configuration content in the FRU configuration file, so that the first device can create the FRU configuration file based on the configuration content in the FRU configuration file in response to the creation request.

[0123] like Figure 1B As shown, Figure 1A A schematic diagram of the structure of the first device, the second device, and the client device.

[0124] Need to explain, Figure 1B The first device in can be Figure 1A Any first device among the first device 1, ..., first device N.

[0125] Referring to 1B, the first device includes a first out-of-band controller, and the second device includes a second out-of-band controller. The first out-of-band controller is in communication with the second out-of-band controller. The client device includes a central processing unit (CPU).

[0126] The client device is used to run the client of the first out-of-band controller. After the client device logs into the client of the first out-of-band controller, the CPU of the client device and the first out-of-band controller can perform data transmission.

[0127] The out-of-band controller (such as the first out-of-band controller and the second out-of-band controller) is completely independent of the CPU of the computer device (such as the first device and the second device) and can communicate with the CPU through the out-of-band management interface of the computer device. In addition, the out-of-band controller can remotely maintain and manage the computer device through a dedicated data channel.

[0128] Exemplarily, the out-of-band controller may include a monitoring management unit outside the computer device, a management system in a management chip outside the processor, a baseboard management controller (BMC), a system management module (SMM), etc. It should be noted that the embodiments of the present application do not limit the form of the out-of-band controller, and the above is only an exemplary description. In the following embodiments, only the out-of-band controller is taken as an example for description.

[0129] Exemplarily, the firmware program of the BMC is implemented based on the OpenBMC software framework, wherein OpenBMC is an open source baseboard management software framework.

[0130] It should be noted that different computer devices have different names for BMC, for example, some computer devices are called BMC, some computer devices are called iLO, and another computer device is called iDRAC. Whether it is called BMC, iLO or iDRAC, it can be understood as the BMC in the embodiment of the present invention.

[0131] Optionally, the first device and the second device include at least one FRU. Exemplarily, the at least one FRU includes FRU1, ..., FRUk, where k is a positive integer.

[0132] Exemplarily, at least one FRU includes a mainboard, a network card, a redundant arrays of independent disks (RAID) card, a power supply, a hard disk, and other pluggable cards on the hardware device.

[0133] In some embodiments, the first out-of-band controller and the second out-of-band controller are configured with configuration files of the FRUs they contain. The first out-of-band controller and the second out-of-band controller manage the FRUs they contain by loading the configuration files of the FRUs they contain.

[0134] In some embodiments, the first out-of-band controller includes a first flash memory. The configuration file of the FRU configured in the first out-of-band controller can be stored in a data area of ​​the first flash memory. The second out-of-band controller includes a second flash memory. The configuration file of the FRU configured in the second out-of-band controller can be stored in a data area of ​​the second flash memory.

[0135] Optionally, the first out-of-band controller includes a first format parsing unit and a file importing unit.

[0136] The file importing unit is used to import the configuration file of the FRU into the first device, and the first format parsing unit is used to determine whether the configuration file of the FRU imported into the first device meets a preset condition.

[0137] The first format parsing unit complies with the OpenBMC architecture and the Redfish specification. Thus, when the first format parsing unit parses the creation request, it not only helps to ensure that the data format of the parsed configuration content complies with the requirements, but also helps to ensure that the parsed configuration document content is accurate and complete.

[0138] Optionally, the first out-of-band controller includes a first FRU profile set interface (referred to as the first interface for short).

[0139] The first interface supports data in JSON format. Exemplarily, the first interface is a Redfish interface.

[0140] Exemplarily, the URL address of the first FRU configuration file collection interface is redfish / v1 / Manager / {Id} / FRUManagerService / FRUManagers.

[0141] In some embodiments, the first interface is used to receive a creation request (such as a POST request), based on which the first interface supports the transmission of data in JSON format. After the first interface receives the POST request, it enters the file import processing flow, such as the first interface calling the file import unit to receive the configuration content carried by the creation request, and calling the first format parsing unit to determine whether the configuration content meets the preset conditions.

[0142] In some embodiments, the first interface may also be used to receive a query request for querying the number and URL address of configuration files of the FRUs supported by the current model.

[0143] Exemplarily, the first interface includes an attribute name and an attribute value. The format of the first interface is shown in Table 1.

[0144] Table 1

[0145]

[0146] In Table 1, "Members@odata.count" is used to represent the number of configuration files. "1" is used to represent the value of the number of configuration files as 1. "Members" is used to represent the name of the configuration file. @odata.id is a common attribute of the configuration file defined by the open data protocol (OData protocol) in the redfish specification, which is used to indicate the uniform resource locator (URL) of the configuration file. In other words, "@odata.id":" / redfish / v1 / Managers / {Id} / FRUManagerService / FRUManagers / {FRUID}" is used to represent the URL address of the configuration file.

[0147] It is understandable that the URL address of the configuration file is used to indicate the storage address of the configuration file. There is a one-to-one correspondence between the URL address and the configuration file. In other words, one URL address indicates a unique configuration file.

[0148] Optionally, the first out-of-band controller may further include a first FRU configuration service interface.

[0149] The first FRU configuration service interface supports data in JSON format. Exemplarily, the first FRU configuration service interface belongs to the Redfish interface.

[0150] Exemplarily, the URL address of the first FRU configuration service interface is redfish / v1 / Manager / {Id} / FRUManagerService.

[0151] In some embodiments, the first FRU configuration service interface is used to enable or disable a configuration file management service.

[0152] In one example, the first FRU configuration service interface is configured with a ServiceEnable attribute, which includes enable (True) or disable (False). When the ServiceEnable attribute is enabled, it is used to indicate that the configuration file management service is in an on state, and when the ServiceEnable attribute is disabled, it is used to indicate that the configuration file management service is in a off state.

[0153] When the configuration file management service is in the enabled state, the first device supports importing / exporting the configuration file of the FRU. Conversely, when the configuration file management service is in the disabled state, the first device does not support importing / exporting the configuration file of the FRU.

[0154] In some embodiments, the first FRU configuration service interface may also be used to trigger scanning of FRUs.

[0155] In an example, the first FRU configuration service interface is configured with a FRUManager.RescanBuses attribute. The FRUManager.RescanBuses attribute can trigger a specific operation on a corresponding resource based on the Action format of Redfish, that is, can trigger a scanning operation on the FRU.

[0156] In some embodiments, the first FRU configuration service interface may also be used to query the FRU types that can be imported by the current model.

[0157] In one example, the first FRU configuration service interface is configured with a FRUTypeList attribute, and the FRUTypeList attribute is used to query the FRU types that can be imported by the current model to avoid importing invalid configuration files.

[0158] Optionally, the first out-of-band controller also includes a first FRU configuration file interface.

[0159] The first FRU configuration file interface supports data in JSON format. Exemplarily, the first FRU configuration file interface belongs to the Redfish interface.

[0160] It can be understood that the first FRU profile interface can be considered as the interface of a single FRU profile, and the first FRU profile collection interface can be considered as the interface of a collection of single profiles. In other words, the first FRU profile collection interface can be considered as the collection of the first FRU profile interfaces.

[0161] Exemplarily, the URL address of the first FRU configuration file interface is redfish / v1 / Manager / {Id} / FRUManagerService / FRUManagers / {FRUProductName}.

[0162] In some embodiments, the first FRU configuration file interface is used to use the name of the FRU (ProductName) as an index and present the content of the configuration file of the FRU in a form that complies with the Redfish specification.

[0163] In some embodiments, when the configuration file of the FRU needs to be exported, the first FRU configuration file interface can also be used to query the configuration file of the specified FRU and remove the Redfish public attribute (ie, URL address) of the configuration file.

[0164] Optionally, the second out-of-band controller includes a second format parsing unit and a file exporting unit.

[0165] The file export unit is used to export the configuration file of the FRU in the second flash memory, and the second format parsing unit is used to determine whether the configuration file exported by the file export unit meets a preset condition.

[0166] Optionally, the second out-of-band controller also includes a second FRU configuration file interface (referred to as the second interface for short).

[0167] The second interface supports data in JSON format. Exemplarily, the second interface belongs to the Redfish interface.

[0168] In some embodiments, the second interface is used to receive an acquisition request (such as a GET request), based on which the second interface supports the transmission of data in JSON format. After the second interface receives the GET request, it enters the file export processing flow, such as the second interface calling the file export unit to export the configuration file of the FRU in the second flash memory, and calling the second format parsing unit to determine whether the configuration file exported by the file export unit meets the preset conditions, etc.

[0169] Exemplarily, the URL address of the second interface is redfish / v1 / Manager / {Id} / FRUManagerService / FRUManagers / {FRUProductName}.

[0170] In some embodiments, the second interface is used to use the name of the FRU (ProductName) as an index and present the content of the configuration file of the FRU in a form that complies with the Redfish specification.

[0171] In some embodiments, when the configuration file of the FRU needs to be exported, the second interface can be used to query the configuration file of the specified FRU and remove the Redfish public attribute (ie, URL address) of the configuration file. Optionally, the second out-of-band controller includes a second FRU configuration service interface.

[0172] It should be noted that for the relevant description of the second FRU configuration service interface, reference can be made to the relevant description of the first FRU configuration service interface mentioned above. The principles of the two are the same and will not be repeated here.

[0173] Optionally, the second out-of-band controller includes a second FRU profile collection interface.

[0174] It can be understood that the second FRU profile interface can be considered as the interface of a single FRU profile, and the second FRU profile collection interface can be considered as the interface of a collection of single profiles. In other words, the second FRU profile collection interface can be considered as a collection of second FRU profile interfaces.

[0175] It should be noted that for other related descriptions about the second FRU configuration file interface, reference can be made to the related descriptions of the first FRU configuration file interface mentioned above. The principles of the two are the same and will not be repeated here.

[0176] like Figure 2A As shown, it is another system architecture diagram provided in an embodiment of the present application.

[0177] See also Figure 2A The system architecture includes a client device, at least one first device and a second device, wherein the client device is respectively connected to the at least one first device and the second device for communication.

[0178] The client device is used to import the configuration content in the FRU configuration file from the second device, and import the configuration content in the FRU configuration file into the first device.

[0179] like Figure 2B , which is a schematic diagram of the structure of the first device, the second device and the client device provided in an embodiment of the present application.

[0180] See also Figure 2B The client device includes a CPU, wherein the CPU is communicatively connected with a first out-of-band controller of the first device and a second out-of-band controller of the second device.

[0181] Optionally, the client device further includes a storage device, wherein the storage device is used to store configuration content in a configuration file of the FRU obtained by the client device from the second device.

[0182] For the relevant descriptions of the first device and the second device, please refer to the above Figure 1A to Figure 1B The relevant description of the system architecture shown will not be repeated here.

[0183] It should be noted that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0184] For ease of understanding, the FRU management method provided in the present application is exemplarily introduced below with reference to the accompanying drawings.

[0185] The following embodiments of the present application will be divided into two parts to exemplarily introduce the scheme of the FRU management method.

[0186] Part I: Combination Figures 3 to 5, describes a process in which a first device obtains configuration content of a FRU configuration file from a second device.

[0187] Part II: Combination Figure 6 , introduces a process in which a first device obtains configuration content of a FRU configuration file from a client device.

[0188] The following, combined Figures 3 to 5 The first part of the embodiment of the present application is introduced.

[0189] Figure 3 The flowchart of a FRU management method according to an exemplary embodiment is shown. Exemplarily, the method includes the following S301-S308.

[0190] It should be noted that this method is applicable to Figure 1A to Figure 1B The system architecture is shown.

[0191] In some embodiments, the FRU on the second device is replaced with the target FRU, and the second device is configured with a configuration file of the target FRU. In addition, a plurality of FRUs on the first device are also replaced with the target FRU.

[0192] In order to reduce the R&D cost and time of configuring the configuration file of the target FRU for the first device, any first device among the multiple first devices can automatically create the configuration file of the target FRU based on the following S301-S308. In other words, the first device in the following embodiment can be any first device among the multiple first devices.

[0193] S301: When the first device is not configured with a configuration file of a target FRU, the first device sends an acquisition request to the second device.

[0194] The acquisition request is used to request to acquire the configuration content in the configuration file of the target FRU.

[0195] Exemplarily, the acquisition request may be a GET request in a RESTful architecture, in which a GET request may be used to request the return of a requested resource description. In an embodiment of the present application, the GET request is used to request the return of configuration content in a configuration file of a target FRU.

[0196] The target FRU may refer to at least one FRU on the first device that is not configured with a FRU configuration file.

[0197] It should be noted that the embodiment of the present application does not limit the number of target FRUs. In other words, the target FRU can be any one or more FRUs on the first device that are not configured with a FRU configuration file.

[0198] Optionally, obtaining the content of the request includes multiple implementation methods, and two implementation methods are exemplified below.

[0199] In a first implementation, the acquisition request includes the name of the target FRU.

[0200] The acquisition request is used to request to acquire the configuration content in the configuration file indicated by the name of the target FRU.

[0201] The configuration file indicated by the name of the target FRU is the configuration file of the target FRU. Exemplarily, the name of the configuration file of the target FRU is the same as the name of the target FRU.

[0202] like Figure 4 The figure shows a structural diagram of the first device and the second device.

[0203] Figure 1B The first device and the second device shown are installed with FRU1. However, after FRU1 leaves the factory, the manufacturer finds that FRU1 has hardware defects, and revises FRU1 to obtain FRU1', or updates the software function of FRU1 to obtain FRU1'. For example, the software function update may refer to the update of the monitorable information of FRU1', or the update of the hardware function of FRU1 to obtain FRU1'. On this basis, Figure 1B The FRU1 on the first and second devices is replaced with Figure 4 The FRU1' on the first device and the second device is shown.

[0204] It is understandable that after the FRU undergoes hardware upgrade, software upgrade or hardware revision, the configuration file of the FRU also needs to be updated accordingly. In other words, the first out-of-band controller and the second out-of-band controller need to manage the FRU after the hardware upgrade, software upgrade or hardware revision based on the updated configuration file.

[0205] Based on this, after FRU1 on the second device is replaced with FRU1', the user configures a FRU1' configuration file for the second out-of-band controller of the second device, so that the second out-of-band controller can manage FRU1' on the second device based on the FRU1' configuration file.

[0206] It should be noted that the embodiment of the present application does not limit the method of configuring the configuration file FRU1' for the second out-of-band controller, which can be any implementation method in the relevant technology. For example, it can be to configure the configuration file of the target FRU for the second out-of-band controller by upgrading the firmware program of the second out-of-band controller.

[0207] Based on the above, FRU1 on the first device is replaced with FRU1' (i.e., the target FRRU). In the case where the first device is not configured with the configuration file of the target FRU, in order to manage the target FRU, the first device sends an acquisition request (such as a GET request) to the second device to request the configuration file of the target FRRU (i.e., the FRU1' configuration file).

[0208] It can be understood that when the first device needs to obtain the configuration content in the configuration file of any specified FRU (such as the target FRU) from the second device, the acquisition request sent by the first device to the second device may include the name of the specified FRU. In this way, the second device can determine the configuration file to which the configuration content to be obtained by the first device belongs based on the name of the specified FRU.

[0209] In this implementation, since the name of the FRU configuration file is the same as the name of the FRU, the acquisition request is set to include the name of the target FRU, and a request is made to obtain the configuration content in the configuration file indicated by the name of the target FRU. This helps to ensure the accuracy of the acquired configuration content when it is necessary to obtain the configuration content in the configuration file of a specific FRU.

[0210] It should be noted that the target FRRU being the replaced FRU1' is only an exemplary description, and the target FRRU may be any replaced FRU on the first device, for example, the target FRU may also be the replaced FRU2', ..., FRUk-1' or FRUk'.

[0211] In a second implementation manner, the acquisition request includes a model identifier of the first device.

[0212] The acquisition request is specifically used to request to acquire the configuration content in the configuration file supported by the model corresponding to the model identification. The configuration file of the target FRU is the configuration file supported by the model identification.

[0213] Exemplarily, the first device model includes a rack type, a blade type, a tower type, etc. Based on this, the model identifier of the first device includes a rack type identifier, a blade type identifier, a tower type identifier, etc.

[0214] like Figure 5 As shown, it is another structural schematic diagram of the first device and the second device.

[0215] Figure 1B The first device and the second device shown in include FRU1, ..., FRUk. Later, due to hardware defects in FRU1, ..., FRUk, they are revised, or the software functions of FRU1, ..., FRUk are updated, or the hardware functions of FRU1, ..., FRUk are updated, and FRU1', ..., FRUk' are obtained. On this basis, see Figure 5 , Figure 1B The FRU1, ..., FRUk on the first device, the first device on the second device, and the second device are replaced by Figure 5 The first device and the second device are shown as FRU1', ..., FRUk'.

[0216] Based on this, the user configures FRU1' configuration files, ..., FRUk' configuration files for FRU1', ..., FRUk' on the second device so that the second out-of-band controller can manage FRU1', ..., FRUk' on the second device based on the FRU1' configuration files, ..., FRUk' configuration files.

[0217] In some embodiments, FRU1, ..., FRUk on the first device is replaced with FRU1', ..., FRUk'. In the case that the first device is not configured with the configuration files of FRU1', ..., FRUk', in order to manage FRU1', ..., FRUk', the first device sends an acquisition request to the second device to request to acquire the configuration files of FRU1', ..., FRUk'.

[0218] In a second implementation manner, FRU1', ..., FRUk' are target FRUs. In other words, the target FRUs include FRU1', ..., FRUk'.

[0219] It can be understood that when the first device needs to obtain multiple FRU configuration files (such as FRU1' configuration file,..., FRUk' configuration file) from the second device, the acquisition request sent by the first device to the second device may include the model identification of the first device. In this way, the second device can determine the multiple FRU configuration files that can be used by the model of the first device based on the model identification of the first device, and thus return the configuration content in the multiple FRU configuration files that can be used by the first device to the first device, so that the first device can create multiple FRU configuration files based on the creation request and the configuration content in the multiple FRU configuration files.

[0220] In this embodiment, the acquisition request is set to include the model identification of the first device, and a request is made to obtain the configuration content in the configuration file indicated by the model identification. In this way, when multiple FRUs are replaced in the first device and the configuration content in the configuration files of multiple FRUs needs to be obtained, it helps to improve the efficiency of obtaining the configuration content in the configuration files of multiple FRUs.

[0221] Optionally, when the acquisition request includes the model identifier of the first device, the acquisition request may also include the target FRU type.

[0222] The target FRU type is a FRU type supported by the first device, the acquisition request is used to request to obtain configuration content in a configuration file belonging to the target FRU type, and the configuration file of the target FRU is a configuration file belonging to the target FRU type.

[0223] The FRU type refers to the type of the component using the FRU.

[0224] Exemplarily, if the first FRU component is a mainboard (Board), the FRU type of the first FRU is a mainboard. If the second FRU component is a chassis (Chassis), the FRU type of the second FRU is a chassis. If the third FRU component is a backplane (non volatile memory express, NVMe), the FRU type of the third FRU is a backplane. If the fourth FRU component is a power supply (PowerSupply), the FRU type of the fourth FRU is a power supply.

[0225] It is understandable that the target FRU type is not limited in the embodiments of the present application. For example, the target FRU type may be at least one of a mainboard FRU, a frame FRU, a backplane FRU, and a power supply FRU. Among them, the mainboard FRU refers to a FRU applied to a mainboard (Board), the frame FRU refers to a FRU applied to a frame, the backplane FRU refers to a FRU applied to a backplane, and the power supply FRU refers to a FRU applied to a power supply.

[0226] In some embodiments, when the first device needs to obtain configuration files of multiple FRUs from the second device, the acquisition sent by the first device to the second device may also include the target FRU type, so that the second device can determine the FRU configuration file based on the model identification and the target FRU type of the first device. In this way, the determined configuration file is not only a configuration file that can be used by the model of the first device, but also a FRU type supported by the first device.

[0227] In this embodiment, the acquisition request is set to include the target FRU type, which is used to indicate that the configuration file requested by the acquisition request should belong to the target FRU type. This helps to ensure that the configuration file of the target FRU obtained by the first device from the second device can match the first device, and further helps to ensure that the first device can use the obtained configuration file normally.

[0228] Optionally, S301 includes multiple implementation methods, and the following is exemplified by Method 1 and Method 2.

[0229] Mode 1: In response to receiving a target instruction sent by the client device, sending an acquisition request to the second device.

[0230] The target instruction is used to instruct to obtain the configuration file of the target FRU from the second device, and the target instruction is sent when the first device is not configured with the configuration file of the target FRU.

[0231] In some embodiments, after the first device configures the target FRU, the user sends a target instruction to the first device through the client device to instruct the first device to obtain a configuration file of the target FRU from the second device.

[0232] Exemplarily, the target instruction may include an Internet Protocol (IP) address of the second device, and the first device sends an acquisition request to the second device via the IP address of the second device.

[0233] In method 1, the first device sends an acquisition request to the second device in response to receiving the target instruction sent by the client device. In this way, when the user determines that the first device needs to use the configuration file of the target FRU, the first device can be instructed to send an acquisition request to the second device. This helps to increase the necessity of obtaining configuration content.

[0234] Mode 2: In response to the target scanning result of the first device, sending an acquisition request to the second device.

[0235] The target scanning result includes a configuration file for which the target FRU is not scanned on the first device.

[0236] In some embodiments, after configuring the target FRU, the first device restarts the FRU configuration service, so that the first out-of-band controller scans the target FRU to obtain attribute information of the target FRU from the target FRU, where the attribute information includes the name of the target FRU.

[0237] Afterwards, the first out-of-band controller scans the configuration file in the first flash memory according to the name of the target FRU to load the configuration file of the target FRU. If the first out-of-band controller does not scan the configuration file of the target FRU, the first out-of-band controller sends an acquisition request to the second out-of-band controller of the second device.

[0238] Exemplarily, the first device is preset to store an Internet Protocol (IP) address of the second device, and the first device sends an acquisition request to the second device based on the IP address of the second device in response to the target scanning result.

[0239] In mode 2, the first device automatically sends an acquisition request to the second device in response to the target scanning result without user participation, which helps to improve the convenience and automation of configuration content acquisition.

[0240] Optionally, S301 includes: when the first device is not configured with a configuration file of the target FRU, sending an acquisition request to the second device based on the first interface, wherein the first interface supports the use of JSON format data.

[0241] In this embodiment, since the configuration content in the FRU configuration file is in JSON format, the first device is set to send an acquisition request to the second device based on the first interface, so that the configuration content in the configuration file of the target FRU is transmitted between the first device and the second device through the first port, and the first interface supports the transmission of data in JSON format. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0242] Optionally, S301 includes the following S301a to S301c.

[0243] S301a: When the first device is not configured with a configuration file of the target FRU, send a second enable request to the second device.

[0244] The second enable request is used to request to enable the FRU configuration management service of the second device, so that the second device supports exporting the configuration file of the target FRU.

[0245] In some embodiments, the FRU configuration management service of the second device refers to the FRU configuration management service supported by the second out-of-band controller. The FRU configuration management service of the second device includes an on state and a off state.

[0246] When the FRU configuration management service is in the enabled state, the configuration file of the FRU in the second out-of-band controller supports export, so that the second device can send the configuration content in the exported configuration file to other devices. When the FRU configuration management service is in the disabled state, the configuration file of the FRU in the second out-of-band controller does not support export, so that the second device will not be able to send the configuration content in the configuration file in the second out-of-band controller to other devices.

[0247] Since the initial state of the FRU configuration management service of the second out-of-band controller is closed after it is powered on, before the first device sends the acquisition request to the second device, it first sends an opening request to the second device to request to open the FRU configuration management service of the second device, so that the second device supports exporting the configuration file of the target FRU.

[0248] S301b: The second device starts the FRU configuration management service in response to the received second start request.

[0249] In some embodiments, after receiving the second start request, the second device changes the state of the FRU configuration management service from a closed state to an open state to start the FRU configuration management service.

[0250] Exemplarily, after the second FRU configuration service interface of the second out-of-band controller receives the second start request sent by the first out-of-band controller, the second FRU configuration service interface starts the FRU configuration management service in response to the start request.

[0251] In some embodiments, after the FRU configuration management service of the second device is enabled, the second device returns an enable notification to the first device, where the enable notification is used to notify the first device that the FRU configuration management service of the second device has been enabled.

[0252] Exemplarily, the second out-of-band controller may return a start notification to the first out-of-band controller.

[0253] S301c: When determining that the FRU configuration management server of the second device is turned on, the first device sends an acquisition request to the second device.

[0254] In some embodiments, after receiving the startup notification returned by the second device, the first device determines that the FRU configuration management server of the second device has been started. On this basis, the first device sends an acquisition request to the second device to request the configuration content in the configuration file of the target FRU.

[0255] In this embodiment, by setting the second device to configure the FRU configuration management service, when the FRU configuration management service is in the on state, the second device can export the configuration file of the target FRU. When it is in the off state, the second device cannot export the configuration file of the target FRU. This helps to ensure the security of the configuration file of the FRU in the second device.

[0256] Based on this, by setting up sending an enable request to the second device, the second device can be requested to enable the FRU configuration management service, so that the second device supports exporting the configuration file of the target FRU, which helps to ensure the convenience of exporting the configuration file.

[0257] S302: The second device receives the acquisition request sent by the first device.

[0258] After receiving the acquisition request, the second out-of-band controller of the second device calls the file export unit in response to the acquisition request to export the configuration file of the target FRU from the second flash memory of the second out-of-band controller.

[0259] Exemplarily, after receiving the acquisition request, the second out-of-band controller can export the configuration file of the target FRU from the second flash memory if the FRU configuration file management service is enabled, otherwise, the configuration file of the target FRU cannot be exported from the second flash memory.

[0260] In some embodiments, when the acquisition request includes the name of the target FRU, the second out-of-band controller parses the name of the target FRU from the URL index of the acquisition request and exports the FRU configuration file indicated by the name of the target FRU from the second flash memory.

[0261] In other embodiments, when the acquisition request includes a model identifier of the first device, the second out-of-band controller parses the model identifier of the first device from the URL index of the acquisition request, and based on the model identifier, exports the configuration file indicated by the model identifier (i.e., the configuration file of the target FRU) from the second flash memory.

[0262] In one example, a plurality of first FRU configuration file sets are stored in the second flash memory.

[0263] Different first FRU configuration file sets are applicable to different machine types. For example, the multiple first FRU configuration file sets include a set applicable to rack-type devices, a set applicable to blade-type devices, a set applicable to tower-type devices, and the like.

[0264] It should be noted that the FRU configuration files in different first FRU configuration file sets may be the same, or may be different, and this embodiment of the present application does not impose any limitation on this.

[0265] On this basis, the second out-of-band controller exports the first FRU configuration file set indicated by the model identifier from the second flash memory, in other words, exports the first FRU configuration file set applicable to the model corresponding to the model identifier.

[0266] In some further embodiments, when the acquisition request includes a target FRU type, the second out-of-band controller parses the target FRU type from a URL index of the acquisition request, and based on the target FRU type, exports a configuration file belonging to the target FRU type from the second flash memory.

[0267] In one example, a plurality of second FRU configuration file sets are stored in the second flash memory.

[0268] It can be understood that the FRU configuration files in a second FRU configuration file set belong to the same FRU type.

[0269] Different second FRU configuration file sets belong to different FRU types. For example, the plurality of second FRU configuration file sets include a set belonging to a mainboard type FRU, a set belonging to a frame type FRU, a set belonging to a backplane type FRU, and a set belonging to a power supply type FRU.

[0270] On this basis, the second out-of-band controller exports a second FRU configuration file set indicated by the target FRU type from the second flash memory, in other words, exports a second FRU configuration file set belonging to the target FRU type.

[0271] The second FRU configuration file set belonging to the target FRU type means that the configuration files in the second FRU configuration file set belong to the target FRU type.

[0272] Based on the above, when the acquisition request includes the model identifier and target FRU type of the first device, the configuration file exported by the second out-of-band controller from the second flash memory should belong to the first FRU configuration file set indicated by the model identifier and the second FRU configuration file set indicated by the target FRU type.

[0273] Optionally, S302 includes: the second device receives, based on the second interface, an acquisition request sent by the first device.

[0274] In some embodiments, after receiving the acquisition request, the second interface parses the name of the target FRU from the URL index of the acquisition request, and then calls the file export unit to export the configuration file of the target FRU, the name of the configuration file of the target FRU is the same as the name of the target FRU.

[0275] Optionally, S303: the second device determines whether the configuration content in the configuration file of the target FRU meets a preset condition.

[0276] If the judgment result is yes, then execute S304. If the judgment result is no, then end.

[0277] The preset condition includes at least one of a preset attribute name, a preset field type and a preset attribute value.

[0278] In some embodiments, the configuration content includes multiple attribute information. The configuration content satisfies the preset condition when the attribute name, field type or attribute value of the multiple attribute information included in the configuration content matches the corresponding preset attribute name, preset field type or preset attribute value in the preset condition.

[0279] In some embodiments, when the acquisition request is used to request to obtain configuration content in a configuration file of a FRU, the second device determines whether the configuration content in the configuration file of the FRU meets a preset condition.

[0280] In other embodiments, when the acquisition request is used to request to obtain configuration contents in configuration files of multiple FRUs, the second device determines whether the configuration contents in the configuration files of the multiple FRUs meet preset conditions respectively.

[0281] In this embodiment, when the configuration content in the configuration file meets the preset conditions, the configuration content in the configuration file is sent to the first device. This helps to avoid the configuration content belonging to a non-FRU configuration file, thereby improving the accuracy and security of the exported configuration content and avoiding the second device from generating a FRU configuration file based on the configuration content of the non-FRU configuration file.

[0282] Optionally, S303 includes multiple implementation methods, and the following is exemplified by methods a to c.

[0283] Mode a, S303 includes: the second device determines whether the attribute name of the configuration content is the same as the preset attribute name, and whether the field type of the configuration content is the same as the preset field type.

[0284] If the judgment result is the same, in other words, the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type, it means that the configuration content in the configuration file meets the preset condition, and then S304 is executed. If the judgment result is not the same, in other words, the attribute name of the configuration content is not the same as the preset attribute name, and / or the field type of the configuration content is not the same as the preset field type, it means that the configuration content in the configuration file does not meet the preset condition, and then the process ends.

[0285] The attribute name of the configuration content includes at least one of the manufacturer identification, PN component identification, SN serial number, model, and name of the target FRU; the field type of the configuration content includes a character string. In some embodiments, the second interface calls the second format parsing unit to parse the configuration file of the target FRU, and encapsulates the parsed content to obtain the configuration content in the configuration file. Afterwards, the second format parsing unit obtains the preset attribute name and the preset field type, and compares the attribute name of the configuration content with the preset attribute name and the field type of the configuration content with the preset field type.

[0286] Exemplarily, the acquisition request includes common properties of the configuration file of the target FRU, such as, the common properties may include @odata.context / / FRU configuration resource template file, @odata.id / / unique identifier URL of the FRU configuration resource, @odata.type / / template name and version number of the FRU configuration resource. The second format parsing unit obtains the common properties of the configuration file of the target FRU by parsing the acquisition request, and then obtains the preset property name and preset field type through the common properties.

[0287] In some embodiments, a first template file is stored in the second flash memory, and the template file records a preset attribute name and a preset field type.

[0288] Based on the above, the second format parsing unit obtains the first template file through the public attributes, thereby obtaining the preset attribute name and the preset field type.

[0289] In one example, the first template file may be global.json / / official template document. The preset attribute names include preset manufacturer identification, preset PN component identification, preset SN serial number, preset model, preset name, and the like.

[0290] In one example, the first template file includes a preset attribute name and a preset field type.

[0291] For example, the content of the first template is as follows:

[0292]

[0293] Among them, "Properties" is used to represent the attribute information, "Manufacturer" is used to represent that the preset attribute name is the manufacturer, and the ""type":"string"" in the third line is used to represent that the preset field type of the manufacturer is a string. "Model" is used to represent that the preset attribute name is the model. "PartNumber" is used to represent that the preset attribute name is the PN part identifier. ""SerialNumber" is used to represent that the preset attribute name is the SN serial number.

[0294] In the above method a, whether the configuration content meets the preset conditions is determined by whether the attribute name of the configuration content is the same as the preset attribute name, and whether the field type of the configuration content is the same as the preset field type. This helps to ensure the accuracy and completeness of the configuration content parsed from the configuration file.

[0295] Mode b: The second device determines whether the attribute name of the configuration content is the same as the preset attribute name, and whether the attribute value of the configuration content is the same as the preset attribute value.

[0296] In mode b, the attribute name of the configuration content includes the model identifier and / or FRU type of the target FRU.

[0297] The model identifier of the target FRU indicates the identifier of the model to which the target FRU is applicable.

[0298] In some embodiments, the second flash memory stores a second template, and the second template records a preset attribute name and a preset attribute value.

[0299] Based on the above, the second format parsing unit obtains the second template through the common attributes, thereby obtaining the preset attribute name and the preset attribute value.

[0300] In one example, the second template file may be oem.json / / custom template document. The preset attribute name includes a preset model identifier and a preset FRU type.

[0301] In one example, the second template file includes a preset attribute name and a preset attribute value.

[0302] For example, the content of the second template is as follows:

[0303]

[0304] Among them, "Type" is used to indicate that the attribute name is type (i.e., FRU type), "title": "ConfigurationType" is used to indicate that the type is configuration type. "enum" is used to indicate that the following are enumerated attribute values, and "Board", "Chassis", "NVME", "PowerSupply"" are used to indicate attribute values. In other words, the preset FRU types include Board, Chassis, NVME, and PowerSupply.

[0305] It should be noted that for other related instructions about method b, please refer to the above method a, which will not be repeated here.

[0306] In the above method b, whether the configuration content meets the preset conditions is determined by whether the attribute name of the configuration content is the same as the preset attribute name, and whether the attribute value of the configuration content is the same as the preset attribute value. This helps to ensure the accuracy and completeness of the configuration content parsed from the configuration file.

[0307] Mode c, S303 includes: the second device determines whether the attribute name of the configuration content is the same as the preset configuration attribute name.

[0308] If the judgment result is the same, it means that the configuration content in the configuration file meets the preset condition, and then S304 is executed. If the judgment result is not the same, it means that the configuration content in the configuration file does not meet the preset condition, and then the process ends.

[0309] In mode c, the attribute name of the configuration content may include at least one of the manufacturer identification, PN component identification, SN serial number, model, name, FRU type and model identification of the FRU.

[0310] It should be noted that for the relevant description of method c, please refer to the above method a, which will not be repeated here.

[0311] In the above method c, whether the configuration content meets the preset condition is determined by checking whether the name of the configuration content is the same as the preset configuration name. This helps to ensure the accuracy and completeness of the configuration content parsed from the configuration file.

[0312] It should be noted that the above-mentioned methods a to c can be used alone or in combination. For example, method a and method b can be used in combination, and method b can be used in combination with method c. The embodiments of the present application do not limit this.

[0313] It should be noted that the above-mentioned methods a to c are only exemplary descriptions, and the specific method of determining whether the configuration content meets the preset conditions in the embodiment of the present application is not limited.

[0314] S304: In response to the acquisition request, the second device sends a creation request to the first device.

[0315] The creation request is used to request the creation of a configuration file of the target FRU. The creation request includes the configuration content in the configuration file of the target FRU.

[0316] Exemplarily, the creation request may be a POST request in a RESTful architecture, in which the POST request may be used to request the creation of a new resource or the execution of a method for a specified resource. In an embodiment of the present application, the POST request is used to request the creation of a new resource (i.e., a configuration file of a target FRU).

[0317] In some embodiments, when the second format parsing unit determines that the configuration content meets the preset condition, it generates a response body message, the response body message (ie, a creation request).

[0318] In some embodiments, when the acquisition request is used to request to acquire configuration content in a configuration file of a FRU, the second device sends a request to create the configuration file of the FRU to the first device.

[0319] In other embodiments, when the acquisition request is used to request to acquire configuration contents in configuration files of multiple FRUs, the second device sends creation requests for the configuration files of the multiple FRUs to the first device respectively.

[0320] Optionally, S304 includes the second device sending a creation request to the first device based on the second interface in response to the acquisition request.

[0321] The second interface transmits data in JSON format.

[0322] In some embodiments, when the second format parsing unit determines that the configuration content meets the preset condition, it calls the second interface and sends a creation request to the first device.

[0323] In this embodiment, since the configuration file of the FRU is a JSON file and the configuration content in the configuration file of the FRU is in JSON format, the configuration content in the configuration file of the target FRU is transmitted between the first device and the second device through the second interface, and the second interface supports the transmission of JSON format files. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0324] S305: The first device receives a creation request sent by the second device.

[0325] Optionally, S305 includes: the first device receives a creation request sent by the second device according to the first interface.

[0326] In some embodiments, the first interface of the first out-of-band controller receives the creation request, and then the first interface calls the file import unit to import the configuration content in the configuration file of the target FRU into the first device.

[0327] Optionally, S306: the first device determines whether the configuration content in the configuration file of the target FRU meets a preset condition.

[0328] If the judgment result is yes, then execute S307. If the judgment result is no, then end.

[0329] In some embodiments, after receiving the creation request, the first interface of the first out-of-band controller calls the format parsing unit, and the format parsing unit parses the configuration content in the configuration file to determine whether the configuration content meets the preset conditions. If the preset conditions are met, it means that the configuration content received by the first device is compliant, otherwise, it is non-compliant configuration content.

[0330] In this embodiment, the configuration file of the target FRU is created based on the configuration content only when the configuration content in the configuration file of the target FRU meets the preset conditions. This helps to ensure the integrity of the configuration content. In other words, the configuration content required to create the configuration file is complete, which in turn helps to avoid using non-compliant configuration content to create the configuration file of the target FRU, resulting in abnormal functions of the target FRU when managing the target FRU based on the created configuration file.

[0331] It should be noted that the implementation process and related instructions of S306 can refer to the above S303 and will not be repeated here.

[0332] S307: The first device creates a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU in response to the creation request.

[0333] In some embodiments, when the first format parsing unit determines that the configuration content meets the preset conditions, the file importing unit is called to create a configuration file of the target FRU in the first flash memory, so that the configuration file of the target FRU is stored in the first flash memory.

[0334] Exemplarily, the file import unit responds to the creation request, creates a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU, and stores the newly created configuration file of the target FRU in the data area of ​​the first flash memory. The newly created configuration file of the target FRU can be a file in JSON format.

[0335] It should be noted that the process of creating a configuration file of a target FRU in response to a creation request may refer to the process of creating a new resource based on a POST request in the related art. The principles of the two are the same and will not be repeated here.

[0336] In some embodiments, when the acquisition request is used to request to acquire configuration content in a configuration file of a FRU, the first device creates the configuration file of the FRU in response to the creation request.

[0337] In other embodiments, when the acquisition request is used to request to obtain configuration contents in configuration files of multiple FRUs, the second device creates configuration files of the multiple FRUs respectively in response to the creation request.

[0338] Optionally, the FRU management method further includes: setting the FRU configuration management server of the first device to an on state.

[0339] In some embodiments, in response to the target scanning result, the first device sets the FRU configuration management server of the first device to an on state, so that the first device supports creation of a configuration file of the target FRU.

[0340] Since the first device supports creating a configuration file for the target FRU when the FRU configuration management service is set to an on state, this helps to avoid creating a configuration file without permission, thereby helping to ensure the security of FRU management.

[0341] S308: The first device manages the target FRU based on the configuration file of the target FRU.

[0342] In some embodiments, when the acquisition request is used to request to obtain configuration content in a configuration file of a FRU, the first device manages the FRU based on the configuration file of the FRU.

[0343] In other embodiments, when the acquisition request is used to request to obtain configuration contents in configuration files of multiple FRUs, the second device manages the multiple FRUs based on the configuration files of the multiple FRUs.

[0344] In some embodiments, after the configuration file of the target FRU is stored in the first flash memory, the first FRU configuration service interface is called to trigger the scanning FRU operation. After that, the first out-of-band controller scans the FRU of the first device, and after scanning the target FRU, obtains the name of the target FRU stored in the target FRU. After that, the first out-of-band controller loads the configuration file of the target FRU in the first flash memory according to the name of the target FRU, thereby managing the FRU.

[0345] In other embodiments, after the configuration file of the target FRU is stored in the first flash memory, the first device performs a restart operation so that the CPU of the first device is powered on again. After the first device is restarted, the first out-of-band controller scans the FRU of the first device, and after scanning the target FRU, obtains the name of the target FRU stored in the target FRU. Afterwards, the first out-of-band controller loads the configuration file of the target FRU in the first flash memory according to the name of the target FRU, and reports the management service of the target FRU to the CPU, thereby managing the FRU.

[0346] Since some functions of the target FRU can only be managed after the CPU of the first device is restarted, after setting the configuration file of the target FRU to be stored in the first flash memory, the first device performs a restart operation and loads the configuration file of the target FRU, so that the management service of the target FRU can be reported to the CPU, which helps to ensure the completeness of the management of the target FRU by the first out-of-band controller.

[0347] In the above embodiment, when the first device has not configured the configuration file of the target FRU, the first device actively sends an acquisition request to the second device to request the configuration content in the configuration file of the target FRU, and after receiving the creation request of the first device, automatically responds to the creation request, automatically creates the configuration file of the target FRU based on the configuration content in the configuration file of the target FRU carried in the creation request, and then manages the target FRU based on the created configuration file of the target FRU. Since the first device can automatically create the configuration file of the target FRU based on the creation request, compared with the related art that requires the development, testing, version release and other processes of the firmware program before the configuration file of the target FRU can be configured for the first device, it not only helps to reduce the cost of replacing the target FRU, but also helps to improve the efficiency of replacing the target FRU.

[0348] Optionally, the FRU management method further includes the following steps 1 to 2.

[0349] Step 1: The client device sends a scan request to the first device.

[0350] The scan request is used to request scanning of a target FRU after the first device is restarted.

[0351] In some embodiments, after storing the configuration file of the target FRU in the first flash memory, in order to enable the first out-of-band controller to manage all functions of the target FRU, the user sends a scan request to the first device through the client device to instruct the first out-of-band controller of the first device to restart and scan the target FRU after restarting.

[0352] Exemplarily, the CPU of the client device sends a scan request to the target link of the first device, which may be a POST request. In this embodiment, a POST request is used to request to execute a method of a specified resource (i.e., scan FRU). The scan request includes the operation name and operation parameters defined in the @Redfish.ActionInfo link.

[0353] The target link is redfish / v1 / Manager / {Id} / FRUManagerService / Actions / FRUManager.RescanBuses. The @Redfish.ActionInfo link is / redfish / v1 / Managers / {Id} / RescanBusesActionInfo. The action name (Name) is RescanBuses (Rescan Buses). The action parameters (AllowableValues) are Rescan.

[0354] Step 2: The first device performs a restart operation in response to the received scan request sent by the client device, and scans the target FRU after restarting.

[0355] In some embodiments, after receiving the scanning request, the first device performs a restart operation so that the CPU of the first device is powered on again. Afterwards, the first out-of-band controller scans the FRU on the first device, thereby scanning the target FRU.

[0356] In this embodiment, the first device is configured to restart in response to a scan request, and scan the FRU on the first device after restarting. In this way, when the user determines that the FRU needs to be scanned, a scan request can be sent to the first device to instruct the first device to scan the FRU, which helps to improve the flexibility of FRU scanning.

[0357] The following, combined Figure 6 The second part of the embodiment of the present application is introduced.

[0358] Figure 6The flowchart of another method for managing a field replaceable unit (FRU) according to an exemplary embodiment is shown. Exemplarily, the method includes the following S601-S612.

[0359] It should be noted that this method is applicable to FIG. 2A to FIG. 2B The system architecture is shown.

[0360] In some embodiments, the configuration content in the configuration file of the target FRU is stored on the client device. In addition, the FRUs on the multiple first devices are also replaced with the target FRUs.

[0361] In order to reduce the R&D cost and time of configuring the configuration file of the target FRU for the first device, any first device among the multiple first devices can automatically create the configuration file of the target FRU based on the following S601-S507. In other words, the first device in the following embodiment can be any first device among the multiple first devices.

[0362] Optionally, S601: the client device sends a query request to the first device in response to the query instruction.

[0363] The query request is used to request a query of the FRU type supported by the first device.

[0364] In some embodiments, after the client device logs into the client of the first out-of-band controller, the CPU of the client device sends a query request to the first out-of-band controller.

[0365] The client device stores multiple FRU configuration files, and illustratively, the multiple FRU configuration files can be stored in a storage device of the client device. In order to ensure that the type of FRU corresponding to the configuration content sent to the first device later is the FRU type supported by the first device, the client device sends a query request to the first device to query the FRU type supported by the first device.

[0366] Optionally, S602: the first device sends a target FRU type to the client device in response to the query request.

[0367] In some embodiments, the first FRU configuration service interface of the first out-of-band controller receives a query request sent by the client device and obtains the FRU type supported by the first device. Afterwards, the first FRU configuration service interface sends the FRU type supported by the first device (ie, the target FRU type) to the client device.

[0368] In this embodiment, the client device queries the FRU type supported by the first device, which helps to ensure that the FRU corresponding to the configuration content sent to the first device is a FRU type supported by the first device.

[0369] Optionally, the FRU management method further includes:

[0370] Step 1: The client device sends a first enable request to the first device; the first enable request is used to request to enable the FRU configuration service of the first device, so that the first device supports importing the configuration content in the configuration file;

[0371] Step 2: In response to the received first enable request, the first device sets the FRU configuration management service of the first device to an enable state.

[0372] It should be noted that for the related descriptions of step 1 to step 2, reference can be made to the related descriptions of S301a to S301c above, which will not be described in detail here.

[0373] S603: The client device sends a creation request to the first device in response to the creation instruction.

[0374] The creation request is used to request the creation of a configuration file of the target FRU. The creation request includes the configuration content in the configuration file of the target FRU.

[0375] The creation instruction is used to instruct to send a creation request for a configuration file of the target FRU to the first device.

[0376] In some embodiments, the user performs a target operation on the client, and the client generates a creation instruction in response to the target operation performed by the user. The target operation may be an operation performed by the user on a command line, or may be an operation performed by the user on the client of the first out-of-band controller.

[0377] In some embodiments, the client device stores configuration content in the configuration file of the target FRU. If the first device is not configured with the configuration file of the target FRU, the client device sends a creation request to the first device so that the first device can automatically create the configuration file of the target FRU.

[0378] In some embodiments, after the client device logs into the client of the first out-of-band controller, the CPU of the client device sends a creation request to the first out-of-band controller.

[0379] In one example, the client device responds to a create instruction and sends a create request to the first device based on the target FRU type, wherein the configuration file of the target FRU belongs to the target FRU type. This helps to ensure that the configuration content in the configuration file of the target FRU received by the first device can be used normally.

[0380] Optionally, S603 includes: in response to the creation instruction, based on a third interface, sending the creation request to the first device; the third interface supports transmission of data in JSON format.

[0381] In this implementation, since the configuration file of the FRU is a JSON file and the configuration content in the configuration file of the FRU is in JSON format, the client device sends the configuration content in the configuration file of the target FRU to the first device through the third interface, and the third interface supports the transmission of JSON format files. In this way, when transmitting the configuration content, there is no need to convert the data format, which helps to ensure the convenience and accuracy of data transmission.

[0382] It should be noted that for other related descriptions of S603, reference can be made to the above-mentioned S304, the principles of the two are the same and will not be repeated here.

[0383] S604: The first device receives a creation request sent by the client device.

[0384] It should be noted that for other related descriptions of S604, reference can be made to the above-mentioned S305, the principles of the two are the same and will not be repeated here.

[0385] Optionally, S605: the first device determines whether the configuration content in the configuration file of the target FRU meets a preset condition.

[0386] It should be noted that for other related descriptions of S605, reference can be made to the above-mentioned S306, the principles of the two are the same and will not be repeated here.

[0387] S606: The first device creates a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU in response to the creation request.

[0388] It should be noted that for other related descriptions of S606, reference can be made to the above-mentioned S307, the principles of the two are the same and will not be repeated here.

[0389] S607: The first device manages the target FRU based on the configuration file of the target FRU.

[0390] It should be noted that for other related descriptions of S607, reference can be made to the above-mentioned S308, the principles of the two are the same and will not be repeated here.

[0391] In the above embodiment, when the user determines that the first device needs to use the configuration file of the target FRU, the user instructs the client device to send a creation request to the first device through a creation instruction, so that the first device can automatically create the configuration file of the target FRU. After receiving the creation request, the first device automatically responds to the creation request, automatically creates the configuration file of the target FRU based on the configuration content in the configuration file of the target FRU carried in the creation request, and then manages the target FRU based on the created configuration file of the target FRU. Since the first device can automatically create the configuration file of the target FRU based on the creation request, compared with the related art that requires the development, testing, version release and other processes of the firmware program to configure the configuration file of the target FRU for the first device, it not only helps to reduce the cost of replacing the target FRU, but also helps to improve the efficiency of replacing the target FRU.

[0392] The following is an exemplary introduction to the process of the client device acquiring the configuration file of the target FRU through S608 to S612.

[0393] S608: The client device sends an acquisition request to the second device in response to the acquisition instruction.

[0394] The acquisition request is used to request to acquire the configuration content in the configuration file of the target FRU.

[0395] In some embodiments, after the client device logs into the client of the second out-of-band controller, the CPU of the client device sends an acquisition request to the second out-of-band controller.

[0396] Optionally, the FRU management method further includes:

[0397] Step 1: The client device sends a third enable request to the second device, where the second enable request is used to request to enable the FRU configuration management service of the second device so that the second device supports exporting the configuration content in the configuration file.

[0398] Step 2: In response to the received third enable request, the second device sets the FRU configuration management service of the second device to an enable state.

[0399] It should be noted that for the related descriptions of step 1 to step 2, reference can be made to the related descriptions of S301a to S301c above, which will not be described in detail here.

[0400] It should be noted that for other related descriptions of S608, reference can be made to the above-mentioned S301, the principles of the two are the same and will not be repeated here.

[0401] S609: The second device receives the acquisition request sent by the client device.

[0402] It should be noted that for other related descriptions of S609, reference can be made to the above-mentioned S302, the principles of the two are the same and will not be repeated here.

[0403] Optionally, S610: the second device determines whether the configuration content in the configuration file of the target FRU meets a preset condition.

[0404] It should be noted that for other related descriptions of S610, reference can be made to the above-mentioned S303, the principles of the two are the same and will not be repeated here.

[0405] S611: The second device sends the configuration content in the configuration file of the target FRU to the client device.

[0406] It should be noted that for the relevant description of S611, reference can be made to the above-mentioned S304, the principles of the two are the same and will not be repeated here.

[0407] S612: The client device receives the configuration content in the configuration file of the target FRU sent by the second device.

[0408] It should be noted that for the relevant description of S612, reference can be made to the above-mentioned S305, and the principles of the two are the same, which will not be repeated here.

[0409] In the above embodiment, the first device responds to the acquisition instruction and sends an acquisition request to the second device to request to obtain the configuration content in the configuration file of the target FRU from the second device, thereby realizing the configuration content in the configuration file of the target FRU. In this way, other devices can generate the configuration file of the target FRU based on the configuration content in the configuration file. Compared with the related technology that requires the development, testing, version release and other processes of the firmware program to determine the configuration content in the configuration file of the target FRU, it not only helps to reduce the cost of determining the configuration content in the configuration file, but also helps to improve the efficiency of the configuration content in the configuration file.

[0410] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to realize the above functions, the field replaceable unit FRU management device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0411] The embodiments of the present application can exemplarily divide the functional modules of the field replaceable unit FRU management device according to the above method. For example, the field replaceable unit FRU management device can include various functional modules corresponding to the various functional divisions, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0412] For example, Figure 7 A possible structural diagram of a field replaceable unit FRU management device (referred to as a field replaceable unit FRU management device 700) involved in the above embodiment is shown, and the FRU management device 700 includes a receiving unit 701, a creating unit 702, and a managing unit 703. The receiving unit 701 is used to receive a creation request, and the creation request is used to request the creation of a configuration file of a target FRU; the creation request includes the configuration content in the configuration file of the target FRU. For example, Figure 3 The S305 shown, Figure 6 S604 shown. The creation unit 702 is used to create a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU in response to the creation request. For example, Figure 3 The S307 shown, Figure 6 S606 shown. The management unit 703 is used to manage the target FRU based on the configuration file of the target FRU. For example, Figure 3 The S308 shown, Figure 6 S607 shown.

[0413] Optionally, the creation request is sent by the client device in response to a creation instruction, and the creation instruction is used to instruct to send a creation request for a configuration file of the target FRU to the first device, and the client device stores configuration content in the configuration file of the target FRU.

[0414] Optionally, the FRU management device 700 further includes a sending unit 704. The sending unit 704 is used to send an acquisition request to the second device when the first device is not configured with a configuration file of the target FRU; the second device stores the configuration file of the target FRU, and the acquisition request is used to request to obtain the configuration content in the configuration file; wherein the creation request is sent by the second device in response to the acquisition request.

[0415] Optionally, the sending unit 704 is specifically used to send an acquisition request to the second device in response to a received target instruction; the target instruction is used to instruct to obtain the configuration content in the configuration file of the target FRU from the second device, and the target instruction is sent when the first device is not configured with the configuration file of the target FRU; or in response to a target scan result, send an acquisition request to the second device; the target scan result includes a configuration file of the target FRU that is not scanned on the first device.

[0416] Optionally, the creation unit 702 is specifically configured to create a configuration file of the target FRU based on the configuration content in the configuration file in response to a creation request if the configuration content in the configuration file meets a preset condition.

[0417] Optionally, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type; wherein the attribute name of the configuration content includes at least one of the manufacturer identifier, PN component identifier, SN serial number, model, and name of the target FRU.

[0418] Optionally, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the attribute value of the configuration content is the same as the preset attribute value; wherein the attribute name of the configuration content includes the model identification and / or FRU type of the target FRU.

[0419] Optionally, the acquisition request includes the name of the target FRU, and the acquisition request is used to request to obtain the configuration content in the configuration file indicated by the name of the target FRU; or the acquisition request includes the model identifier of the first device, and the acquisition request is used to request to obtain the configuration content in the configuration file supported by the model identifier, and the configuration file of the target FRU is a configuration file supported by the model identifier.

[0420] Optionally, when the acquisition request includes the model identification of the first device, the acquisition request may also include a target FRU type, where the target FRU type is a FRU type supported by the first device, and the acquisition request is used to request configuration content in a configuration file belonging to the target FRU type, where the configuration file of the target FRU is a configuration file belonging to the target FRU type.

[0421] Optionally, the configuration content in the configuration file is in JSON format; the receiving unit 701 is specifically used to receive a creation request based on the first interface; the first interface supports the transmission of data in JSON format.

[0422] For the detailed description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. In addition, the explanation and description of the beneficial effects of any of the above field replaceable unit FRU management devices 700 can refer to the above corresponding method embodiments, which will not be repeated here.

[0423] For example, Figure 8 A possible structural diagram of a field replaceable unit FRU management device (referred to as a field replaceable unit FRU management device 800) involved in the above embodiment is shown, and the FRU management device 800 includes a receiving unit 801 and a sending unit 802. The receiving unit 801 is used to receive an acquisition request; the acquisition request is used to request to obtain the configuration content in the configuration file of the target FRU. For example, Figure 3 The S302 shown, Figure 6 S602 shown. The sending unit 802 is used to send a creation request to the device that sent the acquisition request in response to the acquisition request; the creation request includes the configuration content in the configuration file of the target FRU, and the creation request is used to request the creation of the configuration file of the target FRU, and the configuration file of the target FRU is used to manage the target FRU on the device that sent the acquisition request, or the sending unit 802 is used to send the configuration content in the configuration file of the target FRU to the device that sent the acquisition request in response to the acquisition request. For example, Figure 3 S304 as shown, or Figure 6 S611 shown.

[0424] Optionally, the acquisition request is sent by the client device in response to an acquisition instruction; or the acquisition request is sent by the first device when the first device is not configured with a configuration file of the target FRU.

[0425] Optionally, the sending unit is specifically configured to respond to the acquisition request if the configuration content in the configuration file meets a preset condition.

[0426] Optionally, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type; wherein the attribute name of the configuration content includes at least one of the manufacturer identifier, PN component identifier, SN serial number, model, and name of the target FRU.

[0427] Optionally, the configuration content in the configuration file meets preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the attribute value of the configuration content is the same as the preset attribute value; wherein the attribute name of the configuration content includes the model identification and / or FRU type of the target FRU.

[0428] Optionally, the acquisition request includes the name of the target FRU, and the acquisition request is used to request the configuration file indicated by the name of the target FRU; or the acquisition request includes the model identifier of the first device, and the acquisition request is used to request the configuration file supported by the model identifier, and the configuration files supported by the model identifier include the configuration files of the target FRU.

[0429] Optionally, when the acquisition request includes the model identification of the first device, the acquisition request may also include a target FRU type, where the target FRU type is a FRU type supported by the first device, and the acquisition request is used to request a configuration file belonging to the target FRU type.

[0430] Optionally, the configuration content in the configuration file is in JSON format; the sending unit 802 is specifically used to: in response to the acquisition request, based on the second interface, send a creation request to the device that sends the acquisition request; the second interface supports the transmission of data in JSON format.

[0431] Optionally, the configuration content in the configuration file is in JSON format; the sending unit 802 is specifically used to: in response to the acquisition request, send the configuration content in the configuration file of the target FRU to the device that sends the acquisition request, including: in response to the acquisition request, based on the second interface, sending the configuration content in the configuration file of the target FRU to the device that sends the acquisition request.

[0432] For the detailed description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. In addition, the explanation and description of the beneficial effects of any of the above field replaceable unit FRU management devices 800 can refer to the above corresponding method embodiments, which will not be repeated here.

[0433] For example, Fig. 9 A possible structural diagram of a field replaceable unit FRU management device (referred to as a field replaceable unit FRU management device 900) involved in the above embodiment is shown, and the FRU management device 900 includes a sending unit 901. The sending unit 901 is used to send a creation request to the first device in response to a creation instruction; the creation request is used to request the creation of a configuration file of the target FRU; the creation request includes the configuration content in the configuration file. For example, Figure 6 S603 shown.

[0434] Optionally, the FRU management device 900 further includes a receiving unit 902. The sending unit 901 is further configured to send an acquisition request to the second device in response to the acquisition instruction; the acquisition request is used to request to acquire the configuration content in the configuration file of the target FRU; the receiving unit is configured to receive the configuration content in the configuration file of the target FRU sent by the second device.

[0435] Optionally, the acquisition request includes the name of the target FRU, and the acquisition request is used to request to obtain the configuration content in the configuration file indicated by the name of the target FRU; or the acquisition request includes the model identifier of the first device, and the acquisition request is used to request to obtain the configuration content in the configuration file supported by the model identifier, and the configuration file of the target FRU is a configuration file supported by the model identifier.

[0436] Optionally, when the acquisition request includes the model identification of the first device, the acquisition request may also include a target FRU type, where the target FRU type is a FRU type supported by the first device, and the acquisition request is used to request configuration content in a configuration file belonging to the target FRU type, where the configuration file of the target FRU is a configuration file belonging to the target FRU type.

[0437] Optionally, the sending unit 901 is specifically used to: in response to a creation instruction, send a creation request to the first device based on a third interface; the third interface supports transmission of data in JSON format.

[0438] For the detailed description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. In addition, the explanation and description of the beneficial effects of any of the above field replaceable unit FRU management devices 900 can refer to the above corresponding method embodiments, which will not be repeated here.

[0439] The embodiment of the present application also provides a computer device, which includes a processor and a memory, the processor is connected to the memory, the memory stores a computer execution instruction, and the processor implements the data processing method in the above embodiment when executing the computer execution instruction. The embodiment of the present application does not impose any restrictions on the specific form of the computer device. For example, the computer device can be a terminal device or a network device. Among them, the terminal device can be called: terminal, user equipment (user equipment, UE), terminal equipment, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device, etc. The terminal device can be a mobile phone, augmented reality (augmented reality, AR) device, virtual reality (virtual reality, VR) device, tablet computer, laptop computer, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), netbook, personal digital assistant (personal digital assistant, PDA), etc. The network device can be a server, etc. Among them, the server can be a physical or logical server, or it can be two or more physical or logical servers that share different responsibilities and cooperate with each other to realize the functions of the server.

[0440] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed on a computer, the computer is enabled to execute any of the methods executed by the computer devices provided above.

[0441] For the explanation of the relevant contents and description of the beneficial effects of any of the above-mentioned computer-readable storage media, reference may be made to the above-mentioned corresponding embodiments, which will not be repeated here.

[0442] The embodiment of the present application also provides a chip. The chip integrates a control circuit and one or more ports for realizing the functions of the above-mentioned computer device. Optionally, the functions supported by the chip can be referred to above and will not be repeated here. A person of ordinary skill in the art can understand that all or part of the steps of implementing the above-mentioned embodiment can be completed by instructing the relevant hardware through a program. The program can be stored in a computer-readable storage medium. The storage medium mentioned above can be a read-only memory, a random access memory, etc. The above-mentioned processing unit or processor can be a central processing unit, a general-purpose processor, an application specific integrated circuit (ASIC), a microprocessor (digital signal processor, DSP), a field programmable gate array (field programmable gatearray, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.

[0443] The embodiment of the present application also provides a computer program product including instructions, when the instructions are run on a computer, the computer executes any one of the methods in the above embodiments. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more servers that can be integrated with the medium. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., an SSD), etc.

[0444] It should be noted that the above-mentioned devices for storing computer instructions or computer programs provided in the embodiments of the present application, such as but not limited to the above-mentioned memories, computer-readable storage media and communication chips, etc., are all non-transitory.

[0445] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more servers that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0446] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0447] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for managing a field replaceable unit (FRU), characterized in that: An out-of-band controller for a first device; the method comprising: Receiving a creation request sent by a client device or a second device, wherein the creation request includes configuration content in a configuration file of a target FRU; In the case where the FRU on the first device replaces the target FRU, in response to the creation request, creating a configuration file of the target FRU based on the configuration content in the configuration file of the target FRU; the target FRU and the FRU are different FRUs; The target FRU is managed based on the configuration file of the target FRU.

2. The method according to claim 1, characterized in that The creation request is sent by the client device in response to a creation instruction, wherein the creation instruction is used to instruct to send a creation request for the configuration file of the target FRU to the first device, and the client device stores the configuration content in the configuration file of the target FRU; or The method also includes: sending an acquisition request to a second device when the first device is not configured with a configuration file of the target FRU; the second device stores the configuration file of the target FRU, and the acquisition request is used to request to obtain the configuration content in the configuration file; wherein the creation request is sent by the second device in response to the acquisition request.

3. The method according to claim 2, characterized in that The sending of the acquisition request to the second device when the first device is not configured with the configuration file of the target FRU includes: In response to the received target instruction, sending the acquisition request to the second device; the target instruction is used to instruct to obtain the configuration content in the configuration file of the target FRU from the second device, and the target instruction is sent when the first device is not configured with the configuration file of the target FRU; or In response to a target scanning result, sending an acquisition request to the second device; the target scanning result includes a configuration file of the target FRU that is not scanned on the first device.

4. The method according to claim 2 or 3, characterized in that: The step of creating the configuration file of the target FRU based on the configuration content in the configuration file of the target FRU in response to the creation request includes: If the configuration content in the configuration file meets the preset condition, in response to the creation request, a configuration file of the target FRU is created based on the configuration content in the configuration file.

5. The method according to claim 4, characterized in that The configuration content in the configuration file meets the preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type; wherein the attribute name of the configuration content includes at least one of the manufacturer identification, PN component identification, SN serial number, model, and name of the target FRU; and / or The configuration content in the configuration file meets the preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the attribute value of the configuration content is the same as the preset attribute value; wherein the attribute name of the configuration content includes the model identification and / or FRU type of the target FRU.

6. The method according to any one of claims 2, 3 or 5, characterized in that: The acquisition request includes the name of the target FRU, and the acquisition request is used to request to obtain the configuration content in the configuration file indicated by the name of the target FRU; or The acquisition request includes a model identification of the first device, and the acquisition request is used to request to obtain configuration content in a configuration file supported by a model corresponding to the model identification, and the configuration file of the target FRU is a configuration file supported by the model identification.

7. The method according to claim 5, characterized in that In the case where the acquisition request includes the model identification of the first device, the acquisition request also includes a target FRU type, and the target FRU type is a FRU type supported by the first device. The acquisition request is used to request to obtain the configuration content in a configuration file belonging to the target FRU type, and the configuration file of the target FRU is a configuration file belonging to the target FRU type.

8. The method according to any one of claims 1, 2, 3, 5 or 7, characterized in that: The configuration content in the configuration file is in JSON format; the receiving the creation request includes: Based on a first interface, the creation request is received; the first interface supports transmission of data in JSON format.

9. A method for managing a field replaceable unit (FRU), characterized in that: Used for a second device, wherein a configuration file of a target FRU is stored in the second device; the method comprises: In the case where the FRU on the second device replaces the target FRU, receiving an acquisition request; the acquisition request is used to request to obtain the configuration content in the configuration file of the target FRU; the target FRU and the FRU are different FRUs; In response to the acquisition request, sending a creation request to the device that sent the acquisition request; the creation request includes the configuration content in the configuration file of the target FRU, the creation request is used to request the creation of the configuration file of the target FRU, and the configuration file of the target FRU is used to manage the target FRU on the device that sent the acquisition request; or In response to the acquisition request, the configuration content in the configuration file of the target FRU is sent to the device that sends the acquisition request.

10. The method according to claim 9, characterized in that The acquisition request is sent by the client device in response to an acquisition instruction; or The acquisition request is sent by the first device when the first device has not configured a configuration file of the target FRU.

11. The method according to claim 9 or 10, characterized in that: The response to the acquisition request includes: If the configuration content in the configuration file meets the preset conditions, respond to the acquisition request.

12. The method according to claim 11, characterized in that The configuration content in the configuration file meets the preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the field type of the configuration content is the same as the preset field type; wherein the attribute name of the configuration content includes at least one of the manufacturer identification, PN component identification, SN serial number, model, and name of the target FRU; and / or The configuration content in the configuration file meets the preset conditions, including: the attribute name of the configuration content is the same as the preset attribute name, and the attribute value of the configuration content is the same as the preset attribute value; wherein the attribute name of the configuration content includes the model identification and / or FRU type of the target FRU.

13. The method according to claim 10, characterized in that The acquisition request includes the name of the target FRU, and the acquisition request is used to request to obtain the configuration file indicated by the name of the target FRU; or The acquisition request includes a model identification of the first device, and the acquisition request is used to request to obtain a configuration file supported by the model identification, and the configuration files supported by the model identification include a configuration file of the target FRU.

14. The method according to any one of claims 9, 10, 12 or 13, characterized in that The configuration content in the configuration file is in JSON format; In response to the acquisition request, sending a creation request to the device that sent the acquisition request, including: in response to the acquisition request, based on a second interface, sending a creation request to the device that sent the acquisition request; the second interface supports the transmission of data in JSON format; or In response to the acquisition request, sending the configuration content in the configuration file of the target FRU to the device sending the acquisition request, including: in response to the acquisition request, based on the second interface, sending the configuration content in the configuration file of the target FRU to the device sending the acquisition request.

15. A method for managing a field replaceable unit, characterized in that: For a client device, the client device stores configuration content in a configuration file of a target FRU; the method comprises: When the FRU on the first device is replaced with the target FRU, a creation request is sent to the first device in response to a creation instruction; the creation instruction is used to instruct to send a creation request for the configuration file of the target FRU to the first device, and the creation request is used to request to create the configuration file of the target FRU; the creation request includes the configuration content in the configuration file; the target FRU and the FRU are different FRUs.

16. A computing device, characterized in that: include: processor; The processor is connected to a memory, the memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory to enable the computing device to implement the method according to any one of claims 1 to 8.

Images