CN111475185A - Method and system for stably upgrading BMC (baseboard management controller) image across large versions - Google Patents
Method and system for stably upgrading BMC (baseboard management controller) image across large versions Download PDFInfo
- Publication number
- CN111475185A CN111475185A CN202010167307.6A CN202010167307A CN111475185A CN 111475185 A CN111475185 A CN 111475185A CN 202010167307 A CN202010167307 A CN 202010167307A CN 111475185 A CN111475185 A CN 111475185A
- Authority
- CN
- China
- Prior art keywords
- bmc
- firmware
- upgrading
- version
- script
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 23
- 238000011084 recovery Methods 0.000 claims description 5
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012544 monitoring process 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)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a system for stably upgrading a BMC (baseboard management controller) image across large versions, wherein the method comprises the following steps: s1, setting and starting a BMC firmware upgrading script at a controller node; s2, configuring a BMC firmware upgrading script to obtain a highest-level version image file with a current large version number of the BMC firmware and an image file with a target large version number, and splicing the two image files to generate an image file to be upgraded; and S3, configuring a BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful. According to the method and the system for stably upgrading the BMC image across large versions, the image files of the BMC which are upgraded across large versions are spliced, so that the problem that the upgrading failure probability of BMC firmware is increased due to multiple times of upgrading is avoided, and the upgrading stability of the BMC firmware large versions is improved.
Description
Technical Field
The invention belongs to the technical field of BMC firmware upgrading, and particularly relates to a method and a system for stably upgrading a BMC (baseboard management controller) image across large versions.
Background
The stability of BMC firmware upgrading is related to the whole server monitoring system, after BMC upgrading fails, remote access cannot be achieved, and in-band refreshing or even power failure is needed if recovery is needed.
When the versions are upgraded across large versions, particularly when the versions are upgraded among different clients, because the firmware upgrade cannot span the large versions, the versions can only be upgraded to the highest level of the same large version number, then the upgrade across versions is carried out, the upgrade frequency is high, errors are easy to occur, the upgrade frequency of the existing BMC firmware across large versions is high, the upgrade failure occurs at a high probability, the BMC firmware is unusable after being upgraded, and the problem is brought to a server system.
Therefore, it is desirable to provide a method and system for stably upgrading a BMC image across large versions.
Disclosure of Invention
Aiming at the defects that the existing BMC firmware in the prior art is unavailable after upgrading due to high upgrading failure probability because of high upgrading times across large version numbers, the invention provides a method and a system for stably upgrading a BMC image across large version numbers, so as to solve the technical problems.
In a first aspect, the present invention provides a method for stably upgrading a BMC image across large versions, including the following steps:
s1, setting and starting a BMC firmware upgrading script at a controller node;
s2, configuring a BMC firmware upgrading script to obtain a highest-level version image file with a current large version number of the BMC firmware and an image file with a target large version number, and splicing the two image files to generate an image file to be upgraded;
and S3, configuring a BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful.
Further, the step S2 specifically includes the following steps:
s21, configuring a BMC firmware upgrading script to acquire current version information of the BMC firmware;
s22, configuring a BMC firmware upgrading script to acquire a large version number of the current version according to the current version information of the BMC firmware;
s23, configuring a BMC firmware upgrading script to judge whether the current version of the BMC firmware is the highest version under the large version number;
if yes, configuring the BMC firmware upgrading script to set the image file with the target large version number as the image file to be upgraded, and entering step S3;
if not, the BMC firmware upgrading script is configured to splice the image file of the highest version under the large version number of the current version of the BMC with the image file of the target large version number, and the step S3 is entered. When the current version of the BMC firmware is the highest version of the BMC firmware under the large version number, only one upgrade is needed; and for the BMC firmware, the current version is not the highest version, and the upgrading across version numbers is completed at one time by splicing the two image files of the BMC upgraded across the version numbers.
Further, the step S3 specifically includes the following steps:
s31, configuring a BMC firmware upgrading script to position a BMC of the server system;
s32, configuring a BMC firmware upgrading script to send a mirror image file to be upgraded to the positioning BMC, and upgrading the BMC across large-version firmware;
s33, configuring a BMC firmware upgrading script to judge whether firmware upgrading of the positioned BMC is successful;
if yes, positioning the next BMC and returning to the step S32;
if not, the process returns to step S32. And the BMC firmware upgrading script sequentially carries out cross-version firmware upgrading on each BMC.
Further, in step S33, when the update of the positioning BMC firmware fails, recording the number of times of the update failure of the positioning BMC firmware;
and when the upgrading failure times of the positioning BMC firmware exceed the set threshold, positioning the next BMC, and returning to the step S32. When the upgrading of the firmware of one BMC fails, the firmware can be upgraded again, but when the upgrading failure frequency of the firmware exceeds a threshold value, the upgrading of the firmware of the next BMC is carried out, so that the phenomenon that the upgrading of the firmware of the BMC of the whole server system fails due to the fact that dead circulation is entered is prevented.
Further, in step S32, before configuring the BMC firmware upgrade script to perform BMC large-version firmware upgrade, storing current firmware information of the located BMC;
and when the updating of the positioning BMC firmware fails and the failure frequency exceeds a set threshold value, restoring the original firmware information of the positioning BMC. By storing the firmware information before upgrading the BMC firmware in advance, the original firmware information of the BMC can be quickly recovered when the upgrading of the BMC firmware fails, and the unavailability of the BMC firmware caused by the upgrading failure of the BMC firmware is prevented.
In a second aspect, the present invention provides a system for stably upgrading a BMC image across large versions, including:
the firmware upgrading script setting module is used for setting and starting a BMC firmware upgrading script at the node of the control machine;
the system comprises a to-be-upgraded image file generation module, a BMC firmware upgrading script generation module and a BMC firmware upgrading module, wherein the to-be-upgraded image file generation module is used for configuring the BMC firmware upgrading script to acquire a highest version image file with a current large version number and an image file with a target large version number of the BMC firmware upgrading script, splicing the two image files and generating an image file to be upgraded;
and the firmware upgrading module is used for configuring the BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful.
Further, the image file to be upgraded generating module includes:
the current version information acquisition unit is used for configuring the BMC firmware upgrading script to acquire the current version information of the BMC firmware;
the large version number obtaining unit is used for configuring the BMC firmware upgrading script to obtain the large version number of the current version according to the current version information of the BMC firmware;
the current version judging unit is used for configuring the BMC firmware upgrading script to judge whether the current version of the BMC firmware is the highest version under the large version number;
and the image file generation unit to be upgraded is used for configuring the BMC firmware upgrade script to set the image file of the target large version number as the image file to be upgraded when the current version of the BMC firmware is the highest version under the large version number, and configuring the BMC firmware upgrade script to splice the image file of the highest version under the large version number of the current version of the BMC with the image file of the target large version number when the current version of the BMC firmware deploys the highest version under the large version number.
Further, the firmware upgrade module includes:
the BMC positioning unit is used for configuring a BMC of the BMC firmware upgrading script positioning server system;
the firmware upgrading unit is used for configuring a BMC firmware upgrading script to send a mirror image file to be upgraded to the positioning BMC and upgrading the BMC across large-version firmware;
and the upgrading judgment unit is used for configuring the BMC firmware upgrading script to judge whether the firmware upgrading of the positioned BMC is successful or not and positioning the next BMC when the upgrading is successful.
Further, the firmware upgrade module further includes:
the upgrading failure frequency recording unit is used for recording the upgrading failure frequency of the positioning BMC firmware when the upgrading of the positioning BMC firmware fails;
and the failure frequency judging unit is used for positioning the next BMC when the upgrading failure frequency of the positioning BMC firmware exceeds a set threshold value.
Further, the firmware upgrade module further includes:
the firmware information storage unit is used for storing the current firmware information of the positioned BMC before the BMC firmware upgrading script is configured to carry out the BMC large-version firmware upgrading;
and the firmware information recovery unit is used for recovering the original firmware information of the positioning BMC when the updating of the positioning BMC firmware fails and the failure frequency exceeds a set threshold value.
The beneficial effect of the invention is that,
according to the method and the system for stably upgrading the BMC image across large versions, the image files of the BMC which are upgraded across large versions are spliced, so that the problem that the upgrading failure probability of BMC firmware is increased due to multiple times of upgrading is avoided, and the upgrading stability of the BMC firmware large versions is improved.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Therefore, compared with the prior art, the invention has prominent substantive features and remarkable progress, and the beneficial effects of the implementation are also obvious.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a first schematic flow chart of the method of the present invention;
FIG. 2 is a second schematic flow chart of the method of the present invention;
FIG. 3 is a schematic diagram of the system of the present invention;
in the figure, 1-firmware upgrade script setting module; 2-generating module of mirror image file to be upgraded; 2.1-current version information obtaining unit; 2.2-a large version number obtaining unit; 2.3-current version judging unit; 2.4-generating unit of image file to be upgraded; 3-firmware upgrade module; 3.1-BMC location unit; 3.2-firmware upgrade unit; 3.3-upgrade judging unit; 3.4-upgrade failure times recording unit; 3.5-failure times judging unit; 3.6-firmware information storage unit; 3.7-firmware information recovery unit.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1:
as shown in fig. 1, the present invention provides a method for stably upgrading a BMC image across large versions, which includes the following steps:
s1, setting and starting a BMC firmware upgrading script at a controller node;
s2, configuring a BMC firmware upgrading script to obtain a highest-level version image file with a current large version number of the BMC firmware and an image file with a target large version number, and splicing the two image files to generate an image file to be upgraded;
and S3, configuring a BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful.
Example 2:
as shown in fig. 2, the present invention provides a method for stably upgrading a BMC image across large versions, which includes the following steps:
s1, setting and starting a BMC firmware upgrading script at a controller node;
s2, configuring a BMC firmware upgrading script to obtain a highest-level version image file with a current large version number of the BMC firmware and an image file with a target large version number, and splicing the two image files to generate an image file to be upgraded; the method comprises the following specific steps:
s21, configuring a BMC firmware upgrading script to acquire current version information of the BMC firmware;
s22, configuring a BMC firmware upgrading script to acquire a large version number of the current version according to the current version information of the BMC firmware;
s23, configuring a BMC firmware upgrading script to judge whether the current version of the BMC firmware is the highest version under the large version number;
if yes, configuring the BMC firmware upgrading script to set the image file with the target large version number as the image file to be upgraded, and entering step S3;
if not, configuring a BMC firmware upgrading script to splice the image file of the highest version under the large version number of the current version of the BMC with the image file of the target large version number, and entering step S3;
s3, configuring a BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the firmware of the BMC across large versions, and verifying whether the firmware upgrading of each BMC is successful; the method comprises the following specific steps:
s31, configuring a BMC firmware upgrading script to position a BMC of the server system;
s32, configuring a BMC firmware upgrading script to send a mirror image file to be upgraded to the positioning BMC, and upgrading the BMC across large-version firmware;
s33, configuring a BMC firmware upgrading script to judge whether firmware upgrading of the positioned BMC is successful;
if yes, positioning the next BMC and returning to the step S32;
if not, recording the upgrading failure times of the positioning BMC firmware, positioning the next BMC when the upgrading failure times of the positioning BMC firmware exceeds a set threshold value, and returning to the step S32;
when the current version of the BMC firmware is the highest version of the BMC firmware under the large version number, only one upgrade is needed; for the BMC firmware, the current version is not the highest version, and the upgrading across version numbers is completed once by splicing two image files of the BMC upgraded across the version numbers; the BMC firmware upgrading script sequentially carries out cross-version firmware upgrading on each BMC; when the upgrading of the firmware of one BMC fails, the firmware can be upgraded again, but when the upgrading failure frequency of the firmware exceeds a threshold value, the upgrading of the firmware of the next BMC is carried out, so that the phenomenon that the upgrading of the firmware of the BMC of the whole server system fails due to the fact that dead circulation is entered is prevented.
In the foregoing embodiment 2, in step S23, the two image files are spliced by the following codes: bin image bin > image2 bin
In step S32, firmware upgrade is performed by:
./socflash_x64 if＝image2.bin count＝0x4000000
in step S33, it is determined whether the BMC firmware is successfully updated by the following codes:
ipmitool raw 0x3c 0x03 0x0 0x0
ipmitool raw 0x3c 0x03 0x0 0x01
in step S32, before configuring the BMC firmware upgrade script to perform BMC large-version firmware upgrade, storing current firmware information of the positioning BMC;
when the updating of the positioning BMC firmware fails and the failure frequency exceeds a set threshold value, recovering the original firmware information of the positioning BMC; by storing the firmware information before upgrading the BMC firmware in advance, the original firmware information of the BMC can be quickly recovered when the upgrading of the BMC firmware fails, and the unavailability of the BMC firmware caused by the upgrading failure of the BMC firmware is prevented.
Example 3:
as shown in fig. 3, the present invention provides a system for stably upgrading a BMC image across large versions, including:
the firmware upgrading script setting module 1 is used for setting and starting a BMC firmware upgrading script at a control machine node;
the to-be-upgraded image file generating module 2 is used for configuring a BMC firmware upgrading script to acquire a highest version image file with a current large version number of the BMC firmware and an image file with a target large version number, splicing the two image files and generating an image file to be upgraded; the image file generation module to be upgraded 2 includes:
a current version information obtaining unit 2.1, configured to configure the BMC firmware upgrade script to obtain the current version information of the BMC firmware;
a large version number obtaining unit 2.2, configured to configure the BMC firmware upgrade script to obtain a large version number of the current version according to the current version information of the BMC firmware;
a current version judging unit 2.3, which is configured with a BMC firmware upgrading script to judge whether the current version of the BMC firmware is the highest version under the large version number;
the image file generation unit to be upgraded 2.4 is used for configuring the BMC firmware upgrade script to set the image file of the target large version number as the image file to be upgraded when the current version of the BMC firmware is the highest version under the large version number, and configuring the BMC firmware upgrade script to splice the image file of the highest version under the large version number of the current version of the BMC with the image file of the target large version number when the current version of the BMC firmware deploys the highest version under the large version number;
the firmware upgrading module 3 is used for configuring a BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful; the firmware upgrade module 3 includes:
the BMC positioning unit 3.1 is used for configuring a BMC of the BMC firmware upgrading script positioning server system;
the firmware upgrading unit 3.2 is used for configuring a BMC firmware upgrading script to send a mirror image file to be upgraded to the positioning BMC, and upgrading the BMC across large-version firmware;
the upgrade judging unit 3.3 is used for configuring the BMC firmware upgrade script to judge whether the firmware upgrade of the positioned BMC is successful or not, and positioning the next BMC when the upgrade is successful;
the upgrade failure frequency recording unit 3.4 is used for recording the upgrade failure frequency of the positioning BMC firmware when the upgrade of the positioning BMC firmware fails;
the failure frequency judging unit 3.5 is used for positioning the next BMC when the upgrading failure frequency of the positioning BMC firmware exceeds a set threshold value;
the firmware information storage unit 3.6 is used for storing the current firmware information of the positioned BMC before the BMC firmware upgrading script is configured to carry out the BMC large-version firmware upgrading;
and the firmware information recovery unit 3.7 is used for recovering the original firmware information of the positioning BMC when the updating of the positioning BMC firmware fails and the failure frequency exceeds a set threshold value.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for stably upgrading a BMC (baseboard management controller) image across large versions is characterized by comprising the following steps:
s1, setting and starting a BMC firmware upgrading script at a controller node;
s2, configuring a BMC firmware upgrading script to obtain a highest-level version image file with a current large version number of the BMC firmware and an image file with a target large version number, and splicing the two image files to generate an image file to be upgraded;
and S3, configuring a BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful.
2. The method for stably upgrading the BMC image across large versions according to claim 1, wherein the step S2 specifically includes the following steps:
s21, configuring a BMC firmware upgrading script to acquire current version information of the BMC firmware;
s22, configuring a BMC firmware upgrading script to acquire a large version number of the current version according to the current version information of the BMC firmware;
s23, configuring a BMC firmware upgrading script to judge whether the current version of the BMC firmware is the highest version under the large version number;
if yes, configuring the BMC firmware upgrading script to set the image file with the target large version number as the image file to be upgraded, and entering step S3;
if not, the BMC firmware upgrading script is configured to splice the image file of the highest version under the large version number of the current version of the BMC with the image file of the target large version number, and the step S3 is entered.
3. The method for stably upgrading the BMC image across large versions according to claim 1, wherein the step S3 specifically includes the following steps:
s31, configuring a BMC firmware upgrading script to position a BMC of the server system;
s32, configuring a BMC firmware upgrading script to send a mirror image file to be upgraded to the positioning BMC, and upgrading the BMC across large-version firmware;
s33, configuring a BMC firmware upgrading script to judge whether firmware upgrading of the positioned BMC is successful;
if yes, positioning the next BMC and returning to the step S32;
if not, the process returns to step S32.
4. The method for stably upgrading a BMC image across large versions according to claim 3, wherein in step S33, when the located BMC firmware fails to be upgraded, the number of times of failed upgrade of the located BMC firmware is recorded;
and when the upgrading failure times of the positioning BMC firmware exceed the set threshold, positioning the next BMC, and returning to the step S32.
5. The method for stably upgrading a BMC image across large version according to claim 4, wherein in step S32, the current firmware information of the BMC is saved before the BMC firmware upgrading script is configured to perform the BMC firmware upgrade across large version;
and when the updating of the positioning BMC firmware fails and the failure frequency exceeds a set threshold value, restoring the original firmware information of the positioning BMC.
6. A system for stably upgrading BMC (baseboard management controller) images across large versions is characterized by comprising:
the firmware upgrading script setting module (1) is used for setting and starting a BMC firmware upgrading script at a control machine node;
the system comprises a to-be-upgraded image file generating module (2) for configuring a BMC firmware upgrading script to acquire a highest version image file with a current large version number of the BMC firmware and an image file with a target large version number, splicing the two image files and generating an image file to be upgraded;
and the firmware upgrading module (3) is used for configuring the BMC firmware upgrading script to sequentially send the image files to be upgraded to each BMC of the server system, upgrading the large-version firmware of the BMC, and verifying whether the firmware upgrading of each BMC is successful.
7. The system for stably upgrading the BMC image across large version according to claim 6, wherein the image file to be upgraded generating module (2) comprises:
the current version information acquisition unit (2.1) is used for configuring the BMC firmware upgrading script to acquire the current version information of the BMC firmware;
a large version number obtaining unit (2.2) for configuring the BMC firmware upgrading script to obtain the large version number of the current version according to the current version information of the BMC firmware;
a current version judging unit (2.3) for configuring the BMC firmware upgrading script to judge whether the current version of the BMC firmware is the highest version under the large version number;
and the image file generation unit (2.4) to be upgraded is used for configuring the BMC firmware upgrade script to set the image file with the target large version number as the image file to be upgraded when the current version of the BMC firmware is the highest version under the large version number, and configuring the BMC firmware upgrade script to splice the image file with the target large version number under the large version number of the current version of the BMC when the current version of the BMC firmware deploys the highest version under the large version number.
8. The system for stably upgrading a BMC image across large versions of claim 6, wherein the firmware upgrade module (3) comprises:
the BMC positioning unit (3.1) is used for configuring a BMC of the BMC firmware upgrading script positioning server system;
the firmware upgrading unit (3.2) is used for configuring the BMC firmware upgrading script to send a mirror image file to be upgraded to the positioning BMC so as to upgrade the large-version firmware of the BMC;
and the upgrade judging unit (3.3) is used for configuring the BMC firmware upgrade script to judge whether the firmware upgrade of the positioned BMC is successful or not, and positioning the next BMC when the upgrade is successful.
9. The system for stably upgrading a BMC image across large versions of claim 6, wherein the firmware upgrade module (3) further comprises:
the upgrade failure frequency recording unit (3.4) is used for recording the upgrade failure frequency of the positioning BMC firmware when the upgrade of the positioning BMC firmware fails;
and the failure frequency judging unit (3.5) is used for positioning the next BMC when the upgrading failure frequency of the positioning BMC firmware exceeds a set threshold value.
10. The system for stably upgrading a BMC image across large versions of claim 6, wherein the firmware upgrade module (3) further comprises:
the firmware information storage unit (3.6) is used for storing the current firmware information of the positioned BMC before the BMC firmware upgrading script is configured to carry out the BMC large-version firmware upgrading;
and the firmware information recovery unit (3.7) is used for recovering the original firmware information of the positioning BMC when the updating of the positioning BMC firmware fails and the failure frequency exceeds a set threshold value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010167307.6A CN111475185A (en) | 2020-03-11 | 2020-03-11 | Method and system for stably upgrading BMC (baseboard management controller) image across large versions |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010167307.6A CN111475185A (en) | 2020-03-11 | 2020-03-11 | Method and system for stably upgrading BMC (baseboard management controller) image across large versions |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111475185A true CN111475185A (en) | 2020-07-31 |
Family
ID=71747333
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010167307.6A Pending CN111475185A (en) | 2020-03-11 | 2020-03-11 | Method and system for stably upgrading BMC (baseboard management controller) image across large versions |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111475185A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112579132A (en) * | 2020-12-29 | 2021-03-30 | 苏州风之力网络科技有限公司 | Resource hot updating method based on version number management |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050144616A1 (en) * | 2003-10-27 | 2005-06-30 | Hammond Brad T. | System and method for updating a software program |
| CN101047561A (en) * | 2006-06-28 | 2007-10-03 | 华为技术有限公司 | Method for automatic updating of equipment |
| CN101169719A (en) * | 2007-11-30 | 2008-04-30 | 华为技术有限公司 | Method and system for implementing data upgrading and upgraded client terminal |
| CN101867484A (en) * | 2010-05-18 | 2010-10-20 | 中兴通讯股份有限公司 | Method and system for upgrading equipment |
| CN102264089A (en) * | 2011-06-08 | 2011-11-30 | 中兴通讯股份有限公司 | Method and device for remotely upgrading logic device of base station system |
| CN102520996A (en) * | 2011-12-07 | 2012-06-27 | 上海市共进通信技术有限公司 | Cross-platform common upgrade mirror information generation and upgrade method in embedded apparatus |
| CN103577211A (en) * | 2012-08-08 | 2014-02-12 | 上海赤炫信息科技有限公司 | Novel packaging and burning as well as updating methods for Android ROM (read only memory) system |
| CN104133715A (en) * | 2014-08-13 | 2014-11-05 | 杭州华三通信技术有限公司 | Ethernet power supply equipment firmware upgrade method and device |
| CN104144179A (en) * | 2013-05-07 | 2014-11-12 | 上海斐讯数据通信技术有限公司 | System and method for upgrading ONU devices |
| CN104346209A (en) * | 2013-08-07 | 2015-02-11 | 英业达科技有限公司 | Updating method of substrate management controller |
| CN105022645A (en) * | 2015-06-15 | 2015-11-04 | 山东超越数控电子有限公司 | Implementation method of updating management module firmware in large scale |
| CN105302613A (en) * | 2015-11-23 | 2016-02-03 | 武汉烽火网络有限责任公司 | Method and system for updating EOC software by adopting combined files |
| US20170171029A1 (en) * | 2015-12-15 | 2017-06-15 | Microsoft Technology Licensing, Llc | End-to-end automated servicing model for cloud computing platforms |
| CN108270626A (en) * | 2018-02-01 | 2018-07-10 | 郑州云海信息技术有限公司 | A kind of method, apparatus, equipment and the readable storage medium storing program for executing of upgrade server firmware |
| CN109189442A (en) * | 2018-09-30 | 2019-01-11 | 联想(北京)有限公司 | Update method, system and electronic equipment |
| CN109375934A (en) * | 2018-09-30 | 2019-02-22 | 天津天地伟业电子工业制造有限公司 | A kind of upgrade method of network cluster device systems |
| CN109471646A (en) * | 2018-11-01 | 2019-03-15 | 郑州云海信息技术有限公司 | A kind of upgrade method, device and the storage medium of the BMC version of server |
| CN109634634A (en) * | 2018-12-12 | 2019-04-16 | 浪潮(北京)电子信息产业有限公司 | A kind of BMC firmware upgrade method, device and terminal |
| CN110399148A (en) * | 2019-06-18 | 2019-11-01 | 苏州浪潮智能科技有限公司 | A kind of verification method, device and the computer readable storage medium of BMC upgrading |
| CN110851157A (en) * | 2019-10-28 | 2020-02-28 | 上海旗旌科技有限公司 | Method and equipment for updating vehicle-mounted terminal equipment system |
-
2020
- 2020-03-11 CN CN202010167307.6A patent/CN111475185A/en active Pending
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050144616A1 (en) * | 2003-10-27 | 2005-06-30 | Hammond Brad T. | System and method for updating a software program |
| CN101047561A (en) * | 2006-06-28 | 2007-10-03 | 华为技术有限公司 | Method for automatic updating of equipment |
| CN101169719A (en) * | 2007-11-30 | 2008-04-30 | 华为技术有限公司 | Method and system for implementing data upgrading and upgraded client terminal |
| CN101867484A (en) * | 2010-05-18 | 2010-10-20 | 中兴通讯股份有限公司 | Method and system for upgrading equipment |
| CN102264089A (en) * | 2011-06-08 | 2011-11-30 | 中兴通讯股份有限公司 | Method and device for remotely upgrading logic device of base station system |
| CN102520996A (en) * | 2011-12-07 | 2012-06-27 | 上海市共进通信技术有限公司 | Cross-platform common upgrade mirror information generation and upgrade method in embedded apparatus |
| CN103577211A (en) * | 2012-08-08 | 2014-02-12 | 上海赤炫信息科技有限公司 | Novel packaging and burning as well as updating methods for Android ROM (read only memory) system |
| CN104144179A (en) * | 2013-05-07 | 2014-11-12 | 上海斐讯数据通信技术有限公司 | System and method for upgrading ONU devices |
| CN104346209A (en) * | 2013-08-07 | 2015-02-11 | 英业达科技有限公司 | Updating method of substrate management controller |
| CN104133715A (en) * | 2014-08-13 | 2014-11-05 | 杭州华三通信技术有限公司 | Ethernet power supply equipment firmware upgrade method and device |
| CN105022645A (en) * | 2015-06-15 | 2015-11-04 | 山东超越数控电子有限公司 | Implementation method of updating management module firmware in large scale |
| CN105302613A (en) * | 2015-11-23 | 2016-02-03 | 武汉烽火网络有限责任公司 | Method and system for updating EOC software by adopting combined files |
| US20170171029A1 (en) * | 2015-12-15 | 2017-06-15 | Microsoft Technology Licensing, Llc | End-to-end automated servicing model for cloud computing platforms |
| CN108270626A (en) * | 2018-02-01 | 2018-07-10 | 郑州云海信息技术有限公司 | A kind of method, apparatus, equipment and the readable storage medium storing program for executing of upgrade server firmware |
| CN109189442A (en) * | 2018-09-30 | 2019-01-11 | 联想(北京)有限公司 | Update method, system and electronic equipment |
| CN109375934A (en) * | 2018-09-30 | 2019-02-22 | 天津天地伟业电子工业制造有限公司 | A kind of upgrade method of network cluster device systems |
| CN109471646A (en) * | 2018-11-01 | 2019-03-15 | 郑州云海信息技术有限公司 | A kind of upgrade method, device and the storage medium of the BMC version of server |
| CN109634634A (en) * | 2018-12-12 | 2019-04-16 | 浪潮(北京)电子信息产业有限公司 | A kind of BMC firmware upgrade method, device and terminal |
| CN110399148A (en) * | 2019-06-18 | 2019-11-01 | 苏州浪潮智能科技有限公司 | A kind of verification method, device and the computer readable storage medium of BMC upgrading |
| CN110851157A (en) * | 2019-10-28 | 2020-02-28 | 上海旗旌科技有限公司 | Method and equipment for updating vehicle-mounted terminal equipment system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112579132A (en) * | 2020-12-29 | 2021-03-30 | 苏州风之力网络科技有限公司 | Resource hot updating method based on version number management |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2018374925B2 (en) | Starting method of energy storage system and energy storage device | |
| CN106843957B (en) | System firmware upgrading method and device | |
| CN106488487A (en) | Fault detection method and device | |
| CN106844092B (en) | Method for automatically recovering MariaDB Galera Cluster of power failure | |
| CN111799785B (en) | Method and system for coordinated recovery of power and communication of power distribution network after extreme disasters | |
| US10880153B2 (en) | Method and system for providing service redundancy between a master server and a slave server | |
| CN105072398B (en) | A kind of device updating method and device | |
| CN114095340B (en) | Virtual-real combined network shooting range scene and snapshot construction method | |
| CN112579354A (en) | Method for backup recovery of edge cloud collaborative software | |
| CN111475185A (en) | Method and system for stably upgrading BMC (baseboard management controller) image across large versions | |
| CN113835770B (en) | Online replacement method and system for server management module | |
| CN111190769A (en) | Disaster recovery technology for automatic drilling | |
| CN103150223A (en) | Method for preventing epon terminal equipment from being damaged and epon terminal equipment | |
| CN112650624A (en) | Cluster upgrading method, device and equipment and computer readable storage medium | |
| CN104158843A (en) | Storage unit invalidation detecting method and device for distributed file storage system | |
| CN113064614B (en) | Firmware upgrading method and system for redundant power supply system of server | |
| CN115756304A (en) | Method, device, equipment and readable medium for realizing configuration data consistency | |
| CN116072202A (en) | Storage device management method, system and storage medium | |
| CN109558267B (en) | Storage cluster data recovery verification method and device | |
| CN107438011B (en) | Method and device for determining configuration information, network manager and system | |
| CN114116253A (en) | Message processing method and system for message queue | |
| WO2016180174A1 (en) | Method and apparatus for synchronizing voice files | |
| CN114650211A (en) | Fault repairing method, device, electronic equipment and computer readable storage medium | |
| CN102355365A (en) | Machine frame manager and electrifying method for machine frame manager | |
| CN107907762B (en) | Test method and system for detecting influence of BBU on stability of whole cabinet |
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 |