CN101556542A - Method and equipment for upgrading device in paired redundant structure - Google Patents
Method and equipment for upgrading device in paired redundant structure Download PDFInfo
- Publication number
- CN101556542A CN101556542A CNA2009101416583A CN200910141658A CN101556542A CN 101556542 A CN101556542 A CN 101556542A CN A2009101416583 A CNA2009101416583 A CN A2009101416583A CN 200910141658 A CN200910141658 A CN 200910141658A CN 101556542 A CN101556542 A CN 101556542A
- Authority
- CN
- China
- Prior art keywords
- target devices
- unit
- upgrading
- redundancy unit
- redundancy
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
Abstract
The embodiment of the invention provides a method and an equipment for upgrading a device in a paired redundant structure. The method comprises the steps of: utilizing a second redundant unit in the paired redundant structure to write an upgrading code into a target device of a first redundant unit of a counterpart paired redundant structure and informing the first redundant unit to restart; checking whether the target device of the first redundant unit upgrades successfully; and if the upgrading fails, rewriting a version code into the target device before the target device is upgraded, and restoring the target device. The embodiment of the invention separates business function ascription and maintenance function ascription of the device in the paired redundant structure, thereby not only improving the reliability of the device upgrade, but also increasing no extra cost.
Description
Technical field
The present invention relates to electronic technology field, relate to the upgrade method and the equipment of device in a kind of paired redundant structure particularly.
Background technology
In communication or the field very high such as storage, generally comprise the paired node of redundancy each other in the system that forms by a lot of working nodes to system availability, reliability requirement.Intrasystem working node number is generally even number, and the communication port of supporting user business is arranged between the node.Becoming the low data rate channel that high availability is arranged between two right nodes of redundancy in the system that has, this bottom data channel architecture is simple, and implementation complexity is low, such as common RS-232 serial ports, JTAG debug port etc.
System is in the runtime, may be on hardware the upgrade job node, such as using more high performance veneer to replace the work on hand veneer, this upgrading is called as hard upgrading.Another kind of then be the soft upgrading of node, promptly working node comes into operation the back in its under-stream period, can need the upgrading of code, and the code of upgrading may be the program code of system's operation, also may be the logical code of all kinds of programming devices.What this paper related to is the soft upgrading of node.
To foregoing by the system of a plurality of redundancies to forming, whole if desired upgrade-systems, then paired node can not be upgraded simultaneously in the system, but have successively, this is because in fields such as communication or storage, this redundancy can not at will be interrupted or can not interrupt the customer service of bearing at all.If redundant centering first node upgrading failure, so Section Point just again " risk " upgraded.
Each working node of redundant centering is a micro controller system, generally including but not limited to as the lower part: be used for various storeies, the transceive data of CPU, the storage system operation code of deal with data communication interface, basic input-output system BIOS (Basic Input Output System), with the mutual management interface of user terminal, all kinds of programmable logic device (PLD) (PLD, Programmable Logic Device) that are used for collecting board card information and Treated Base reset interrupt signal etc. etc.
To the node of redundant centering, existing upgrade method is: the user sends CPU to by the management interface used code of will upgrading, and assigns the upgrading order.CPU resolves user command, and code according to the form that can be accepted by concrete device, is write in storage or the logical device by corresponding DLL (dynamic link library).
From then in the process as can be seen, the upgrading of node all is that the CPU by node self finishes.
In above-mentioned node upgrade method, if because certain problem of target devices such as storer, programming device, make CPU confirm that code has write the code that finishes and in fact write and imperfect or contain wrongly, this will cause after a CPU thinks to upgrade normally restarting after finishing this veneer to be hung extremely.And because this type of target devices is being played the part of very important role in system, the key function that powers on, resets etc. that as the PLD device, will take on the whole veneer of control, so the upgrading of this class target devices failure will cause whole veneer can't respond user command once more.
This node upgrading failure causes " risk " upgrading again of redundant another right node, otherwise might cause whole redundancy to interrupt customer service to hanging dead.
For the problem above solving, existing another kind of technology is that veneer has increased a wrong recovery controller.The node upgrade method of this technology is the same with the technology of front, if but having run into when hanging dead problem after node is restarted, the mistake recovery controller will change system over to and repair pattern, refreshes target devices with default value, restarts veneer once more, and system recovery is normal.Run into the problem that the bottom fault can't selfreparing though the prior art has solved single board updating, it has introduced new controller module, has increased the cost of system, the also corresponding complexity that increases system.
Summary of the invention
The invention provides the upgrade method and the equipment of device in a kind of paired redundant structure, can't soft reparation and the high problem of reduction upgrade cost with what exist in the minimizing prior art.
To achieve these goals, the embodiment of the invention provides the upgrade method of device in a kind of paired redundant structure, and this method comprises:
Utilize this redundancy that second redundancy unit in the structure is write upgrade code in the target devices of redundant right first redundancy unit each other, and notify described first redundancy unit to restart;
The success of whether upgrading of the described target devices of checking described first redundancy unit;
If upgrading is unsuccessful, the edition code before the described target devices upgrading is write this target devices again, carry out the recovery of target devices.
The present invention also provides a kind of updating apparatus of target devices, and described target devices lays respectively in redundant right first redundancy unit and second redundancy unit with updating apparatus, and this updating apparatus comprises:
The code writing unit is used for writing upgrade code to described target devices, and notifies described first redundancy unit to restart;
Inspection unit is used to check the success of whether upgrading of described target devices;
Recovery unit is used for when described target devices upgrading is unsuccessful edition code before the described target devices upgrading being write this target devices again, carries out the recovery of target devices.
The embodiment of the invention had both improved the reliability of device upgrading by becoming redundant to upgrade target devices in this redundancy unit of another redundancy unit of structure, had reduced extra upgrade cost again.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, does not constitute limitation of the invention.In the accompanying drawings:
Fig. 1 is the process flow diagram of in the embodiment of the invention 1 device being upgraded;
Fig. 2 is redundant this right plate of the one-tenth of the embodiment of the invention and to the mutual synoptic diagram between the plate;
Fig. 3 is the process flow diagram of in the embodiment of the invention 2 device being upgraded;
Fig. 4 is the structured flowchart of the updating apparatus of target devices in one embodiment of the invention;
Fig. 5 is the structured flowchart of the updating apparatus of target devices in another embodiment of the present invention;
Fig. 6 is the structured flowchart of inspection unit among Fig. 5.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, specific embodiments of the invention are elaborated below in conjunction with accompanying drawing.At this, illustrative examples of the present invention and explanation thereof are used to explain the present invention, but not as a limitation of the invention.
Embodiment one
The embodiment of the invention provides the upgrade method of device in a kind of paired redundant structure.As shown in Figure 1, this method comprises the steps:
Step 110 writes upgrade code to second redundancy unit in the structure by this redundancy, and notifies described first redundancy unit to restart in the target devices of redundant right first redundancy unit each other.
In the embodiment of the invention, first redundancy unit and second redundancy unit are redundant right, and this first redundancy unit and second redundancy unit both can be the veneer that constitutes working node, also can be the redundant each other modules in a veneer or the node.
After second redundancy unit writes the target devices of first redundancy unit with whole upgrade codes, notify described first redundancy unit to restart so that upgrade and come into force.
In the present embodiment, described target devices can be system modules such as BIOS, also can be programmable logic device (PLD) (PLD), and this programmable logic device (PLD) comprises complicated programmable logic device (PLD) (CPLD).
The success of whether upgrading of step 120, the described target devices of checking described first redundancy unit.
Under the normal condition, first redundancy unit is restarted the back and is moved with new version of code.If but exist the code of mentioning in the prior art that writes imperfect or contain problems such as wrong this moment, and will cause second redundancy unit to be thought upgrade successfully and the in fact target devices success of not upgrading, promptly promptly extension is extremely after first redundancy unit is restarted.Therefore, after notifying first redundancy unit to restart, the success of whether upgrading of the described target devices that in setting-up time, check described first redundancy unit, the time of this setting can be the maximum time that system normally restarts, but the present invention is not limited to this.
Step 130, if upgrading is unsuccessful, this target devices that the edition code before utilizing described second redundancy unit with described target devices upgrading writes first redundancy unit again carries out the recovery of target devices.
By upgrade method as above, cut apart the business function ownership and the maintenance function ownership of device in the paired redundant structure to target devices.In the prior art, the business function of device and maintenance function generally all belong to the controller of this redundancy unit in the redundancy unit, and in the embodiment of the invention in each redundancy unit the business function of device ownership at the controller of this redundancy unit, and the maintenance function of this device is belonged on redundant another right redundancy unit, on the controller of concrete example such as this another redundancy unit.The device that is positioned at first redundancy unit so only is the business service of this redundancy unit, if because the soft fault of these devices causes system to occur unusually, that second redundancy unit just can be carried out maintenance function to the device of first redundancy unit.So both improve the reliability of system upgrade, reduced implementation complexity again, and do not increased extra cost.
Embodiment two
Present embodiment proposes the upgrade method of device in a kind of paired redundant structure in addition.In the present embodiment, paired redundant structure is a pair of veneer, is called node A and Node B, and veneer to be upgraded is called this plate, i.e. node A, and another veneer is called plate, i.e. Node B.
Fig. 2 for the redundant centering of present embodiment to the upgrade structural representation of this plate of plate.Data flow when each intra-node and internodal oriented arrow are represented single board updating among Fig. 2, the data stream during normal working of single board do not indicate in the drawings.By among Fig. 2 as can be seen, be positioned at the devices such as BIOS, PLD on the node A, its programming passage is actually by Node B and provides and control, but device such as BIOS, PLD is all served for node A under the normal condition.Therefore from business function, the devices such as PLD on the node A belong to node A, and from soft upgrade function, i.e. maintenance function, and these devices belong to Node B.
As shown in Figure 3, the soft upgrading flow process to target devices among the node A of present embodiment comprises the steps:
When the code data of the target devices to be upgraded that does not store node A on the Node B, carry out this step.At this moment, the user can realize long-range access by the management interface of Node B, wraps and reaches in the Node B by will the upgrade code data of target devices of FTP mode or other modes.
If store the code data of the target devices to be upgraded of node A on the Node B in advance, this step is omitted.
In the present embodiment, described target devices can be system modules such as BIOS, also can be programmable logic device (PLD) (PLD), and this programmable logic device (PLD) comprises complicated programmable logic device (PLD) (CPLD).
When the target devices of node A was upgraded, the user can assign the order of target devices of upgrading A to Node B by management interface, and this order is sent to node A by the communication interface of Node B and node A, notified node A target devices on will upgrade node A.
Node A sends ACK message to Node B, ready before the expression upgrading.
After step 350, Node B are received the ready ACK message of node A, upgrade code is write the target devices of ingress A, and notify node A to restart.
Node B can by with the programming passage of node A, the data layout of accepting according to target devices writes target devices with upgrade code.For example Node B is written to the upgrade code data in the CPLD device of node A according to JTAG predetermined data form by JTAG programming passage.
Node B is after confirming that upgrade code is write the target devices of ingress A fully, and notice node A is restarted so that upgrade and come into force.For example, Node B can be by the programming passage, and as JTAG programming passage, whether the code of verification upgrading writes and finish, and confirms to write the back that finishes and restarts by communication interface command node A so that upgrade and come into force.
Under the normal condition, node A is restarted the back and is moved with new version of code.If but it is imperfect or contain problems such as wrong to run into the upgrade code that writes, then can exist Node B to think that node A has upgraded successfully and the in fact node A success of not upgrading, promptly after node A is restarted, promptly hang dead.Therefore, in the setting-up time after notice node A is restarted, Node B will be checked the node A success of whether upgrading.
Check in setting-up time whether successful step specifically can be in node A upgrading: Node B adopts an overtime timing strategy, promptly start one to plate upgrading overtime timer, for example timing is 5 minutes, and sends the one query order every some seconds to node A, with the state of query node A.If node A is in operation, then node A can be to Node B echo reply (ACK) message after receiving the querying command of Node B.Under the normal condition, node A sends the ACK response message to Node B before can arriving in the time that overtime timer is set, and this just proves upgrades successfully.If the time interior nodes A that sets at overtime timer does not reply, can prove that so node A hangs in the dust after restarting.
Therefore Node B is checked the node A success of whether upgrading in the following way in this step: if receive the response message that node A returns within the time (as 5 minutes) that overtime timer is set, prove the node A success of having upgraded so.If node A does not respond within during this period of time, that proof goes up the not success of upgrading of target devices to node A.The time that overtime timer is set can normally be closed for system, be restarted the maximum time to normal operating conditions.
Step 380 gets nowhere if node A goes up the upgrading of target devices, and the version before Node B is upgraded described target devices is write this target devices of ingress A again, carries out the recovery of target devices.
For example, get nowhere, then directly enter force revert target devices program, the old code before the upgrading is write target devices again, force reset node A then if Node B affirmation node A goes up the upgrading of target devices.
Step 390 alternatively, can adopt overtime timing strategy behind reset node A, promptly start overtime timer, checks whether target devices recovers success.
In abovementioned steps 390, recover successfully if check target devices, then Node B execution in step 350 is once more carried out the upgrading of target devices described in the node A again.Also comprise step 370 this moment before the step 380, to limit the number of times of upgrading.
Step 370 judges that whether the upgrading number of times is greater than setting value, as 2.If greater than 2, expression upgrading 2 times is that all right merit, then illustrative system have can not soft reparation fault, this moment, Node B can send a warning message to the user by management interface, personnel go to maintenance with notification technique.
If node A upgrades successfully, can be according to step upgrade node B same as described above, only this moment, this version was a Node B, then was node A to plate.Do not give unnecessary details at this.
The as above redundant centering of the embodiment of the invention is to the upgrade method of this plate of plate, business function ownership and the maintenance function ownership of having cut apart redundant centering device, usually all two functions that belong to a controller (as the CPU of node A) are belonged to redundant right this plate now respectively and to two of plate independently on the controller (as the CPU that belongs to node A respectively and the controller of Node B), the device that is positioned at this plate only is this plate business service, if because that the soft fault of these devices causes this plate system to occur is unusual, another operate as normal just can carry out maintenance function to the controller on the plate to the device of this plate.Can significantly improve redundant reliability like this, reduce implementation complexity again and do not increased extra cost upgrading.
And, the upgrade method to device of the embodiment of the invention, be not limited only between the redundant right veneer and veneer, also be equally applicable to become redundant right module and the interoperability between the module on the veneer, this will improve the robustness of module and module largely.
One of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method can instruct relevant hardware to finish by program, this program can be stored in the computer read/write memory medium, such as ROM/RAM, magnetic disc, CD etc.
Embodiment 3
Present embodiment provides a kind of updating apparatus of target devices, and described target devices lays respectively in redundant right first redundancy unit and second redundancy unit with updating apparatus, and as shown in Figure 4, this updating apparatus 400 comprises:
In another embodiment of the present invention, as shown in Figure 5, this updating apparatus 400 also comprises:
Acquiring unit 440 is used for edition code and described upgrade code the code writing unit obtains the upgrading of described target devices before described target devices writes upgrade code before.
Transmitting element 450 is used for writing the order that described first redundancy unit of upgrade code forward direction sends the upgrading target devices at the code writing unit to described target devices.
In another embodiment of the present invention, described updating apparatus also comprises:
Call unit 460 is used for calling the recovery that described recovery unit carries out target devices, until the number of times that recovers successfully or recover to reach setting when the recovery of described target devices is unsuccessful;
Alarm unit 470 when being used for after recovering to reach the number of times of setting also success, sends warning information.
In the embodiment of the invention, described alarm unit also can connect first inspection unit, is used for sending warning message when the target devices to first redundancy unit carries out several times upgradings and all gets nowhere.
In another embodiment of the present invention, as shown in Figure 6, described inspection unit 420 comprises:
Query unit 610 is used for after described first redundancy unit is restarted, and regularly sends query messages to first redundancy unit;
Confirmation unit 620 if receive the response message of first redundancy unit in the time of setting, is then confirmed to upgrade successfully, otherwise confirms the upgrading failure.
The updating apparatus to target devices of the embodiment of the invention has been cut apart the business function ownership and the maintenance function ownership of device in the paired redundant structure.In the prior art, the business function of device and maintenance function generally all belong to the controller of this redundancy unit in the redundancy unit, and in the embodiment of the invention in each redundancy unit the business function of device ownership at the controller of this redundancy unit, and the maintenance function of this device is belonged on redundant another right redundancy unit, on the controller of concrete example such as this another redundancy unit.The device that is positioned at first redundancy unit so only is the business service of this redundancy unit, if because the soft fault of these devices causes system to occur unusually, that second redundancy unit just can be carried out maintenance function to the device of first redundancy unit.Can reduce implementation complexity like this, significantly improve redundant reliability and but do not increase extra cost upgrading.
Above-described specific embodiment; purpose of the present invention, technical scheme and beneficial effect are further described; institute is understood that; the above only is specific embodiments of the invention; and be not intended to limit the scope of the invention; within the spirit and principles in the present invention all, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1, the upgrade method of device in a kind of paired redundant structure is characterized in that, comprising:
Utilize second redundancy unit in this paired redundant structure in the target devices of redundant right first redundancy unit each other, to write upgrade code, and notify described first redundancy unit to restart;
The success of whether upgrading of the described target devices of checking described first redundancy unit;
If upgrading is unsuccessful, utilize described second redundancy unit that the preceding edition code of described target devices upgrading is write this target devices again, carry out the recovery of target devices.
2, method according to claim 1 is characterized in that, utilizes this redundancy to comprise second redundancy unit in the structure is write upgrade code in the target devices of redundant right first redundancy unit each other before:
Send the order of its target devices of upgrading to described first redundancy unit.
3, method according to claim 1 is characterized in that, utilizes this redundancy to comprise second redundancy unit in the structure is write upgrade code in the target devices of redundant right first redundancy unit each other before:
Second redundancy unit obtains the preceding edition code and the described upgrade code of upgrading of described target devices.
4, method according to claim 1 is characterized in that, also comprises:
Whether the recovery of checking described target devices is successful;
If unsuccessful, repeat the recovery of target devices, until the number of times that recovers successfully or recover to reach setting;
If recover to reach also success behind the number of times of setting, send warning information by this second redundancy unit.
5. method according to claim 1 is characterized in that, whether the described target devices of checking described first redundancy unit is upgraded and successfully be meant:
After described first redundancy unit is restarted, regularly send query messages to first redundancy unit, if in the time of setting, receive the response message of first redundancy unit, then confirm to upgrade successfully; Otherwise confirm the upgrading failure.
6, a kind of updating apparatus of target devices is characterized in that, described target devices lays respectively in redundant right first redundancy unit and second redundancy unit with updating apparatus, and this updating apparatus comprises:
The code writing unit is used for writing upgrade code to described target devices, and notifies described first redundancy unit to restart;
Inspection unit is used to check the success of whether upgrading of described target devices;
Recovery unit is used for when described target devices upgrading is unsuccessful edition code before the described target devices upgrading being write this target devices again, carries out the recovery of target devices.
7, equipment according to claim 6 is characterized in that, also comprises:
Transmitting element is used for writing the order that described first redundancy unit of upgrade code forward direction sends the upgrading target devices at the code writing unit to described target devices.
8, equipment according to claim 6 is characterized in that, also comprises:
Acquiring unit is used for edition code and described upgrade code the code writing unit obtains the upgrading of described target devices before described target devices writes upgrade code before.
9, equipment according to claim 8 is characterized in that, also comprises:
Call unit is used for calling the recovery that described recovery unit carries out target devices, until the number of times that recovers successfully or recover to reach setting when the recovery of described target devices is unsuccessful;
Alarm unit when being used for after recovering to reach the number of times of setting also success, sends warning information.
10. equipment according to claim 8 is characterized in that, described inspection unit comprises:
Query unit is used for after described first redundancy unit is restarted, and regularly sends query messages to first redundancy unit;
Confirmation unit if receive the response message of first redundancy unit in the time of setting, is then confirmed to upgrade successfully, otherwise confirms the upgrading failure.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910141658A CN101556542B (en) | 2009-05-25 | 2009-05-25 | Method and equipment for upgrading device in paired redundant structure |
| PCT/CN2010/073032 WO2010135966A1 (en) | 2009-05-25 | 2010-05-21 | Upgrade method and device for components in paired redundancy structure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910141658A CN101556542B (en) | 2009-05-25 | 2009-05-25 | Method and equipment for upgrading device in paired redundant structure |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101556542A true CN101556542A (en) | 2009-10-14 |
| CN101556542B CN101556542B (en) | 2012-10-03 |
Family
ID=41174667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910141658A Expired - Fee Related CN101556542B (en) | 2009-05-25 | 2009-05-25 | Method and equipment for upgrading device in paired redundant structure |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101556542B (en) |
| WO (1) | WO2010135966A1 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010135966A1 (en) * | 2009-05-25 | 2010-12-02 | 成都市华为赛门铁克科技有限公司 | Upgrade method and device for components in paired redundancy structure |
| CN102346692A (en) * | 2010-08-03 | 2012-02-08 | 深圳Tcl新技术有限公司 | Verification method of IPTV (Internet Protocol Television) updating files |
| CN103595564A (en) * | 2013-11-12 | 2014-02-19 | 浪潮集团有限公司 | Method for restoring default settings through redundancy management units in cloud system |
| CN106372538A (en) * | 2016-08-30 | 2017-02-01 | 苏州国芯科技有限公司 | Firmware protection method based on SoC (System on Chip) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108762784A (en) * | 2018-05-28 | 2018-11-06 | 青岛海信网络科技股份有限公司 | A kind of traffic signal controlling machine remote upgrade method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7085957B2 (en) * | 2002-11-21 | 2006-08-01 | Texas Instruments Incorporated | Upgrading of firmware with tolerance to failures |
| CN101101553A (en) * | 2006-07-05 | 2008-01-09 | 乐金电子（昆山）电脑有限公司 | Firmware upgrading restoring method |
| CN101114935A (en) * | 2007-07-27 | 2008-01-30 | 华为技术有限公司 | System upgrading method, upgrading system and monitoring entity |
| CN101556542B (en) * | 2009-05-25 | 2012-10-03 | 成都市华为赛门铁克科技有限公司 | Method and equipment for upgrading device in paired redundant structure |
-
2009
- 2009-05-25 CN CN200910141658A patent/CN101556542B/en not_active Expired - Fee Related
-
2010
- 2010-05-21 WO PCT/CN2010/073032 patent/WO2010135966A1/en active Application Filing
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010135966A1 (en) * | 2009-05-25 | 2010-12-02 | 成都市华为赛门铁克科技有限公司 | Upgrade method and device for components in paired redundancy structure |
| CN102346692A (en) * | 2010-08-03 | 2012-02-08 | 深圳Tcl新技术有限公司 | Verification method of IPTV (Internet Protocol Television) updating files |
| CN103595564A (en) * | 2013-11-12 | 2014-02-19 | 浪潮集团有限公司 | Method for restoring default settings through redundancy management units in cloud system |
| CN106372538A (en) * | 2016-08-30 | 2017-02-01 | 苏州国芯科技有限公司 | Firmware protection method based on SoC (System on Chip) |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2010135966A1 (en) | 2010-12-02 |
| CN101556542B (en) | 2012-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101556542B (en) | Method and equipment for upgrading device in paired redundant structure | |
| CN103713925A (en) | Method and device for avoiding service interruption of storage array in upgrading process | |
| CN112199240A (en) | Method for switching nodes during node failure and related equipment | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps | |
| Cisco | Operational Traps |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C56 | Change in the name or address of the patentee |
Owner name: HUAWEI DIGITAL TECHNOLOGY (CHENGDU) CO., LTD. Free format text: FORMER NAME: CHENGDU HUAWEI SYMANTEC TECHNOLOGIES CO., LTD. |
|
| CP01 | Change in the name or title of a patent holder |
Address after: 611731 Chengdu high tech Zone, Sichuan, West Park, Qingshui River Patentee after: Huawei Symantec Technologies Co., Ltd. Address before: 611731 Chengdu high tech Zone, Sichuan, West Park, Qingshui River Patentee before: Chengdu Huawei Symantec Technologies Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20121003 Termination date: 20180525 |