CN113867754A - Firmware maintenance method, system, equipment and medium - Google Patents
Firmware maintenance method, system, equipment and medium Download PDFInfo
- Publication number
- CN113867754A CN113867754A CN202111007697.1A CN202111007697A CN113867754A CN 113867754 A CN113867754 A CN 113867754A CN 202111007697 A CN202111007697 A CN 202111007697A CN 113867754 A CN113867754 A CN 113867754A
- Authority
- CN
- China
- Prior art keywords
- firmware
- server
- file
- files
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 32
- 238000000034 method Methods 0.000 title claims abstract description 25
- 230000004044 response Effects 0.000 claims abstract description 22
- 238000012163 sequencing technique Methods 0.000 claims abstract description 6
- 230000015556 catabolic process Effects 0.000 claims description 24
- 238000006731 degradation reaction Methods 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 8
- 238000007726 management method Methods 0.000 description 49
- 238000010586 diagram Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a firmware maintenance method, which comprises the following steps: acquiring a plurality of firmware files of different components configured in advance and sequencing the firmware files of the different components based on firmware parameters respectively; establishing a connection with a server in response to receiving a request to maintain firmware of a component of the server; acquiring firmware parameters of a current firmware file of each part in the server; and maintaining the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files. The invention also discloses a system, a computer device and a readable storage medium. The technical scheme provided by the invention can support multi-server multi-component automatic FW maintenance without manual operation, saves labor and time, can be used for maintaining and storing FW files, is convenient for storing and taking the FW files, and is not easy to lose.
Description
Technical Field
The invention relates to the field of servers, in particular to a firmware maintenance method, a firmware maintenance system, firmware maintenance equipment and a storage medium.
Background
With the advent of the information age, it has been difficult for various component manufacturers using servers to fully satisfy customer demands at the time of initial design, and more manufacturers have provided users with upgraded FW providing more updated functions as added values. After the product is released, a manufacturer carries out further optimization innovation on FW, and the performance can be improved after upgrading; with the change and update of the environment of the software and the hardware used around, the product is possible to have incompatibility phenomena for a plurality of new hardware and software, and a manufacturer can be compatible with more software and hardware by updating the FW version; the manufacturer can also add new functionality by updating the FW version. For the above reasons, various components used by the server need to be frequently subjected to FW version upgrade operations; the FW upgrading method of each component of the server at present is to copy FW files required by each component on the server to the system, and execute FW upgrading instructions of each component under the system to complete.
Conventionally, most FW files are maintained offline, when upgrading, an FW version and an upgrade tool need to be manually copied to the OS of a server, upgrade is performed for a single component or a single component, and currently, there is no method and system for FW upgrade for multiple components of the server and for multiple servers simultaneously.
Moreover, because there are many FW files of each component of the server, uniform maintenance is not convenient enough, FW information of each component of the server cannot be automatically identified for automatic upgrade, and a plurality of components and a plurality of servers FW cannot be upgraded simultaneously.
Disclosure of Invention
In view of the above, in order to overcome at least one aspect of the above problems, an embodiment of the present invention provides a firmware maintenance method, including the following steps:
acquiring a plurality of firmware files of different components configured in advance and sequencing the firmware files of the different components based on firmware parameters respectively;
establishing a connection with a server in response to receiving a request to maintain firmware of a component of the server;
acquiring firmware parameters of a current firmware file of each part in the server;
and maintaining the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
In some embodiments, obtaining a plurality of firmware files of different components configured in advance and sorting the plurality of firmware files of different components based on firmware parameters, respectively, further comprises:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
In some embodiments, maintaining the firmware of each component in the server according to the request, the firmware parameters of the current firmware file of each component in the server, and the pre-configured plurality of firmware files further comprises:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
In some embodiments, further comprising:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a firmware maintenance system, including:
the first acquisition module is configured to acquire a plurality of firmware files of different pre-configured components and sort the plurality of firmware files of the different components based on firmware parameters respectively;
a connection module configured to establish a connection with a server in response to receiving a request to maintain firmware of a component of the server;
a second obtaining module configured to obtain firmware parameters of a current firmware file of each component in the server;
and the maintenance module is configured to maintain the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
In some embodiments, the first obtaining module is further configured to:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
In some embodiments, the maintenance module is further configured to:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
In some embodiments, the maintenance module is further configured to:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer apparatus, including:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes the program to perform any of the steps of the firmware maintenance method described above.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program which, when executed by a processor, performs the steps of any of the firmware maintenance methods described above.
The invention has the following beneficial technical effects: the scheme provided by the embodiment of the invention can support multi-server multi-component automatic FW maintenance without manual operation, saves labor and time, can be used for maintaining and storing FW files, is convenient for storing and taking the FW files, and is not easy to lose.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
Fig. 1 is a flowchart illustrating a firmware maintenance method according to an embodiment of the present invention;
FIG. 2 is a block flow diagram of a firmware maintenance method according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a firmware maintenance system according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a computer device provided in an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
FW (firmware), in embodiments of the invention, refers to firmware.
According to an aspect of the present invention, an embodiment of the present invention provides a firmware maintenance method, as shown in fig. 1, which may include the steps of:
s1, acquiring a plurality of firmware files of different components which are configured in advance and sequencing the firmware files of the different components based on the firmware parameters respectively;
s2, responding to the request for maintaining the firmware of the server component, establishing connection with the server;
s3, acquiring the firmware parameters of the current firmware file of each part in the server;
s4, maintaining the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
The scheme provided by the embodiment of the invention can support multi-server multi-component automatic FW maintenance without manual operation, saves labor and time, can be used for maintaining and storing FW files, is convenient for storing and taking the FW files, and is not easy to lose.
In some embodiments, obtaining a plurality of firmware files of different components configured in advance and sorting the plurality of firmware files of different components based on firmware parameters, respectively, further comprises:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
In some embodiments, maintaining the firmware of each component in the server according to the request, the firmware parameters of the current firmware file of each component in the server, and the pre-configured plurality of firmware files further comprises:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
In some embodiments, further comprising:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
The following describes the firmware maintenance method according to the embodiment of the present invention in detail with reference to the flowchart shown in fig. 2.
The FW file management method comprises the steps of creating an FW file management module under a system, creating a plurality of sub-modules such as a RAID card-FW file management module, a network card-FW file management module and the like under the module, realizing maintenance of FW version files and upgrade use tools of components such as a hard disk, a RAID card, a memory, a network card, a pmem and the like through different FW file management modules, and saving the name, version number information, the name of the used tool, the original factory model of an applicable specific component (the same component may use different FW files due to different original factory models) and the like when the FW file is uploaded.
Each component FW file management module maintains an FW upgrade instruction corresponding to a component, and sets 'file name' in the upgrade instruction as a variable parameter, such as a RAID card upgrade instruction: storcli/c0 download file is the filename.
Various FW file management submodules realize version-based ordering of FW versions, a system automatically orders the FW versions according to the version numbers (based on version number naming rule ordering, generally, the sizes of all digits are compared from left to right in sequence, the first digit is the same as the second digit, and the like), and the FW files are automatically ordered when being newly added.
And creating a management module of the server to be upgraded, adding an ip address, a port, a user name and a password of the server to be upgraded through the management module, detecting the communication condition between the system and the server to be upgraded, adding a plurality of servers into the management module to automatically perform FW upgrading operation, simultaneously maintaining an FW downgrading instruction, and performing FW automatic downgrading operation based on the judgment of the version number.
When the FW upgrade operation is performed, the component detection can be automatically performed on the server to be upgraded after the server to be upgraded is added: and remotely connecting the server to be upgraded, and executing an instruction (for example, an instruction for acquiring network card information under linux: lspci | grep-i 'ethernet controller') of each component of the network card, the RAID card and the like by the OS to acquire all component information existing on the server to be upgraded, including component types (the network card, the RAID card and the like), original plant models of the components and FW version information.
Based on the acquired component information, matching the FW version number of the same original factory model under the corresponding sub-module in the FW file management module through the component type + the original factory model (such as RAID card: PMC8204), comparing the FW version number with the FW version number of the latest version, and upgrading the FW for the components with inconsistent FW version numbers:
(1) for the components with inconsistent FW version numbers, the latest FW file and upgrade using tools are sent to a server to be upgraded (the files can be transmitted through a file transfer protocol such as FTP);
(2) based on each component, the sent FW file name is transmitted into an FW upgrading instruction, and the FW upgrading instruction is remotely executed on a server to be upgraded;
(3) after the upgrade of all the components on the server to be upgraded is completed, remotely restarting the server to be upgraded (for example, reboot instructions under linux);
(4) after restarting, the FW version inquiry command of each component is remotely executed to be compared with the latest FW version number maintained by each component, if the FW version numbers are consistent, the updated FW version numbers are returned, and if the FW version numbers are inconsistent, FW update failure information is returned.
And aiming at the multiple upgrading requirements of the added server to be upgraded, providing an operable upgrading interface for the user, and selecting the server to be upgraded based on the user requirements for upgrading.
In the development and test process of the server, various components need to be upgraded frequently, FW version files, version numbers, upgrading tools and instructions of all components needing FW upgrading of the server are maintained to corresponding FW management sub-modules, IP addresses, user names and passwords of all server systems needing upgrading are added to a server management module to be upgraded, then the components to be upgraded on each server are automatically judged and searched, FW upgrading of all the components is completed, upgrading success and failure information is returned, manual operation is not needed, full automation of FW upgrading is achieved, and labor and time are saved.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a firmware maintenance system 400, as shown in fig. 3, including:
a first obtaining module 401 configured to obtain a plurality of firmware files of different components configured in advance and sort the plurality of firmware files of the different components based on firmware parameters, respectively;
a connection module 402 configured to establish a connection with a server in response to receiving a request to maintain firmware of a component of the server;
a second obtaining module 403, configured to obtain firmware parameters of a current firmware file of each component in the server;
a maintenance module 404 configured to maintain the firmware of each component in the server according to the request, the firmware parameters of the current firmware file of each component in the server, and a plurality of pre-configured firmware files.
In some embodiments, the first obtaining module 401 is further configured to:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
In some embodiments, the maintenance module 404 is further configured to:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
In some embodiments, the maintenance module 404 is further configured to:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 4, an embodiment of the present invention further provides a computer apparatus 501, including:
at least one processor 520; and
a memory 510, the memory 510 storing a computer program 511 executable on the processor, the processor 520 executing the program to perform the steps of:
s1, acquiring a plurality of firmware files of different components which are configured in advance and sequencing the firmware files of the different components based on the firmware parameters respectively;
s2, responding to the request for maintaining the firmware of the server component, establishing connection with the server;
s3, acquiring the firmware parameters of the current firmware file of each part in the server;
s4, maintaining the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
In some embodiments, obtaining a plurality of firmware files of different components configured in advance and sorting the plurality of firmware files of different components based on firmware parameters, respectively, further comprises:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
In some embodiments, maintaining the firmware of each component in the server according to the request, the firmware parameters of the current firmware file of each component in the server, and the pre-configured plurality of firmware files further comprises:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
In some embodiments, further comprising:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 5, an embodiment of the present invention further provides a computer-readable storage medium 601, where the computer-readable storage medium 601 stores computer program instructions 610, and the computer program instructions 610, when executed by a processor, perform the following steps:
s1, acquiring a plurality of firmware files of different components which are configured in advance and sequencing the firmware files of the different components based on the firmware parameters respectively;
s2, responding to the request for maintaining the firmware of the server component, establishing connection with the server;
s3, acquiring the firmware parameters of the current firmware file of each part in the server;
s4, maintaining the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
In some embodiments, obtaining a plurality of firmware files of different components configured in advance and sorting the plurality of firmware files of different components based on firmware parameters, respectively, further comprises:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
In some embodiments, maintaining the firmware of each component in the server according to the request, the firmware parameters of the current firmware file of each component in the server, and the pre-configured plurality of firmware files further comprises:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
In some embodiments, further comprising:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
Finally, it should be noted that, as will be understood by those skilled in the art, all or part of the processes of the methods of the above embodiments may be implemented by a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A firmware maintenance method, comprising the steps of:
acquiring a plurality of firmware files of different components configured in advance and sequencing the firmware files of the different components based on firmware parameters respectively;
establishing a connection with a server in response to receiving a request to maintain firmware of a component of the server;
acquiring firmware parameters of a current firmware file of each part in the server;
and maintaining the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
2. The method of claim 1, wherein obtaining a plurality of firmware files for different components that are preconfigured and ordering the plurality of firmware files for different components based on firmware parameters, respectively, further comprises:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
3. The method of claim 2, wherein maintaining the firmware of each component in the server based on the request, the firmware parameters of the current firmware file of each component in the server, and a plurality of pre-configured firmware files, further comprises:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
4. The method of claim 3, further comprising:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
5. A firmware maintenance system, comprising:
the first acquisition module is configured to acquire a plurality of firmware files of different pre-configured components and sort the plurality of firmware files of the different components based on firmware parameters respectively;
a connection module configured to establish a connection with a server in response to receiving a request to maintain firmware of a component of the server;
a second obtaining module configured to obtain firmware parameters of a current firmware file of each component in the server;
and the maintenance module is configured to maintain the firmware of each part in the server according to the request, the firmware parameters of the current firmware file of each part in the server and a plurality of pre-configured firmware files.
6. The system of claim 5, wherein the first acquisition module is further configured to:
creating a plurality of firmware file management modules;
respectively acquiring a plurality of firmware files of one part by utilizing each firmware management module, wherein each firmware file comprises a file name, a firmware version number and an applicable part model;
the plurality of firmware files are ordered based on the applicable component model number and the firmware version number.
7. The system of claim 6, wherein the maintenance module is further configured to:
responding to the request as an upgrading request, and respectively determining a firmware file with the highest version in a plurality of firmware files which are the same as the corresponding parts in the server by utilizing each firmware management module;
in response to the version number of the firmware file with the highest version being greater than the version number of the firmware of the corresponding component in the server, sending the firmware file with the highest version to the server;
and generating and sending an upgrading instruction to the server by using the firmware management module based on the file name of the firmware file with the highest version so that the server upgrades the firmware according to the upgrading instruction.
8. The system of claim 7, wherein the maintenance module is further configured to:
in response to the request being a downgrading request, respectively determining a plurality of firmware files which are the same as the model of the corresponding component in the server and have firmware version numbers smaller than the version number of the current firmware file of the corresponding component by using each firmware management module;
determining the firmware files sent to the server in the plurality of firmware files according to the degradation request;
and generating and sending a degradation instruction to the server by using the firmware management module based on the file name of the firmware file sent to the server so as to enable the server to degrade the firmware according to the degradation instruction and the firmware file sent to the server.
9. A computer device, comprising:
at least one processor; and
memory storing a computer program operable on the processor, characterized in that the processor executes the program to perform the steps of the method according to any of claims 1-4.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111007697.1A CN113867754A (en) | 2021-08-30 | 2021-08-30 | Firmware maintenance method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111007697.1A CN113867754A (en) | 2021-08-30 | 2021-08-30 | Firmware maintenance method, system, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113867754A true CN113867754A (en) | 2021-12-31 |
Family
ID=78988746
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111007697.1A Withdrawn CN113867754A (en) | 2021-08-30 | 2021-08-30 | Firmware maintenance method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113867754A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114826909A (en) * | 2022-05-27 | 2022-07-29 | 苏州浪潮智能科技有限公司 | Server production instruction information maintenance system, method, device and storage medium |
-
2021
- 2021-08-30 CN CN202111007697.1A patent/CN113867754A/en not_active Withdrawn
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114826909A (en) * | 2022-05-27 | 2022-07-29 | 苏州浪潮智能科技有限公司 | Server production instruction information maintenance system, method, device and storage medium |
| CN114826909B (en) * | 2022-05-27 | 2023-08-08 | 苏州浪潮智能科技有限公司 | Server production instruction information maintenance system, method, device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170115977A1 (en) | Apparatus and method for automating the installation and configuration of infrastructure | |
| US9075811B2 (en) | Cloud information migration systems and methods | |
| CN112199197B (en) | Server management method and system | |
| CN107193607B (en) | Method and apparatus for updating code file, storage medium, processor, and terminal | |
| WO2017198015A1 (en) | Software upgrading method and apparatus | |
| CN107977223B (en) | Configuration compatibility checking method and device | |
| CN110297808B (en) | File modification method and device for container application, computer equipment and storage medium | |
| CN113867754A (en) | Firmware maintenance method, system, equipment and medium | |
| CN112995806A (en) | Method, device, system and storage medium for upgrading optical network unit | |
| US20180210766A1 (en) | Migration for cloud management systems | |
| CN111683114A (en) | Method and device for upgrading equipment program, terminal equipment and storage medium | |
| CN111324365A (en) | Method and equipment for upgrading super-converged system | |
| CN102882907A (en) | Client configuration system and method | |
| CN112612493A (en) | Software upgrading method, device, equipment and storage medium for software set | |
| US9207928B2 (en) | Computer-readable medium, apparatus, and methods of automatic capability installation | |
| EP4162649A1 (en) | Stable references for network function life cycle management automation | |
| US11886171B2 (en) | Streamlining the commission of network identifiers | |
| CN111324373A (en) | Method and device for uploading multiple project files to code warehouse and computing equipment | |
| CN115629784A (en) | Method, system, equipment and computer readable storage medium for updating machine file | |
| CN114721686A (en) | Configuration data updating method and device, electronic equipment and storage medium | |
| CN109947451B (en) | Cluster application file updating method, system, medium and equipment | |
| US11381448B2 (en) | Systems and methods for cloud resource synchronization | |
| CN112579247A (en) | Method and device for determining task state | |
| CN111338653B (en) | Data processing method, device, computer equipment and storage medium | |
| CN102156685A (en) | Method and device for automatically configuring distributed network system script |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20211231 |
|
| WW01 | Invention patent application withdrawn after publication |