CN101478422B - Self negotiation method and system for software version - Google Patents
Self negotiation method and system for software version Download PDFInfo
- Publication number
- CN101478422B CN101478422B CN2008102278389A CN200810227838A CN101478422B CN 101478422 B CN101478422 B CN 101478422B CN 2008102278389 A CN2008102278389 A CN 2008102278389A CN 200810227838 A CN200810227838 A CN 200810227838A CN 101478422 B CN101478422 B CN 101478422B
- Authority
- CN
- China
- Prior art keywords
- software
- equipment
- stack
- indicated release
- version
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 230000005540 biological transmission Effects 0.000 description 15
- 230000008569 process Effects 0.000 description 15
- 238000009434 installation Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 4
- 230000009466 transformation Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000002950 deficient Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000009827 uniform distribution Methods 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a method for conducing auto-negotiation of software versions and a system thereof. The stacking equipment with a specific software version is obtained by acquiring the software versions of all stacking equipment and copies the software corresponding to the specific software version to other stacking equipment; and other stacking equipment replaces the currently running software with the software corresponding to the specific software version. By using the scheme provided by the embodiment of the invention, the stacking equipment can automatically negotiate the software version, so that the software with the specific version can obtain more stable and stronger working capacity. Moreover, the method and the system can simplify the use procedures of the stacking equipment, avoid fussy operation of manually upgrading all the stacking equipment to the same software version, and avoid various problems arising from misoperation of software.
Description
Technical field
The present invention relates to the computer network communication technology field, relate in particular to a kind of software version auto-negotiation method and system.
Background technology
Pile up and refer to a plurality of independently unit combination and become a logical block, stackable switch is that many switches are coupled together each switch (mostly need connect to form pile up) by designated port by cable, like this, the user is used, and many switches are equivalent to an equipment.Separate use with a plurality of equipment and compare, the technology of piling up can be accomplished the simplified apparatus management when having increased network port quantity flexibly, and its effect only is equivalent to manage an equipment.
As shown in Figure 1, but 4 equipment rooms are linked in twos by stack port and circularize (common pile up one of topology), per two equipment rooms all are the links of full duplex (being meant that the communication apparatus two ends also can receive data simultaneously when sending data).Wherein have only one as main equipment, be responsible for the configuration input of process user, and various incident and the messages that need software processes; Other then is a slave unit, only handles the instruction that main equipment is sent, and the various incident of software processes and the messages of needing just are transmitted to main frame.
Owing to support the equipment that piles up to use separately, therefore on every equipment the identical software systems of complete sum are arranged all, judge that by consulting the back own determining positions in topology is to work in host mode or slave mode with miscellaneous equipment.But because equipment vendors always constantly upgrade software version, reason mainly contains two aspects, the one, increase new function, and the 2nd, revise and find software defect.Cause the software version of every equipment correspondence possible different.For example, the equipment of certain same model of unit divides and twice or thrice to buy, and that just occurs the height of last batch of version than former batches easily, even every equipment to occur all be different editions.Each device version difference in the pile system, serious whole pile system will appear and can't operate as normal, light meeting partial function occurs and can not use.For example: system crash (the software inhouse interface that is common between different editions is inconsistent) occurs, or what's new can not come into force at some slave unit, and (software on the main frame is up-to-date, and increased function newly, and slave does not have), or some member device is working properly, and some undesired (the employing highest version software of equipment component is wherein revised some defective, and miscellaneous equipment also is to use defective version).
For the problems that non-uniformity of software versions causes, existing in the industry common practice is that the equipment that the requirement user piles up all participations earlier keeps the software version unanimity.In large-scale pile system, this has increased workload beyond doubt, and mistake appears in complicated operation easily.
Summary of the invention
The embodiment of the invention provides a kind of software version auto-negotiation method and system, make between stack equipment and can consult software version automatically, solve the problem of the pile system cisco unity malfunction that causes owing to software version difference between stack equipment in the prior art, and reduced the workload that the artificial software version of each stack equipment synchronously brings.
A kind of software version auto-negotiation method, this method comprises:
Obtain the software version of all stack equipments, obtain having the stack equipment of indicated release software;
The described stack equipment that has indicated release software duplicates the software of described indicated release correspondence to other stack equipment;
Described other stack equipment is replaced current operating software with the software of described indicated release correspondence.
A kind of software auto-negotiation stack equipment, this stack equipment comprises acquiring unit, updating block and reset unit, wherein,
Described acquiring unit is used to obtain the software version of all stack equipments, obtains having the stack equipment of indicated release software;
Described updating block is used to notify the stack equipment that has indicated release software that the software of described indicated release software correspondence is duplicated to other stack equipment;
Described reset unit is used to notify described other stack equipment to replace current operating software with the software of described indicated release correspondence.
A kind of software version auto-negotiation system, this system comprises some stack equipments, wherein one is main equipment, wherein,
Described main equipment obtains the software version of all stack equipments, obtains having the stack equipment of indicated release software; The stack equipment that notice has indicated release software duplicates the software of described indicated release software correspondence to other stack equipment; And notify described other stack equipment to replace current operating software with the software of described indicated release correspondence;
Stack equipment in the described software version auto-negotiation system except that described main equipment is used for the notice according to main equipment, and software version is sent to main equipment; Duplicate software to other stack equipments or receive the software of other stack equipments and replace current operating software with indicated release software according to the notice of main equipment according to the notice of main equipment.
The embodiment of the invention obtains having the stack equipment of specific software version by obtaining the software version of all stack equipments; The described stack equipment that has a specific software version duplicates the software of described specific software version correspondence to other stack equipment; Described other stack equipment is replaced current operating software with the software of described specific software version correspondence.The scheme that adopts the embodiment of the invention to provide makes between stack equipment and can consult software version automatically, reaches to use indicated release software to obtain more stable more powerful ability to work.Simultaneously, can simplify stack equipment and use step, all stack equipments of avoiding manually upgrading avoid the software operation error to cause the possibility of variety of problems to the troublesome operation of same software version.
Description of drawings
Fig. 1 is a pile system structural representation in the prior art;
Fig. 2 is the main realization principle flow chart of the embodiment of the invention 1;
The stack equipment version process of the obtaining schematic diagram that Fig. 3 provides for the embodiment of the invention;
The main equipment that Fig. 4 provides for the embodiment of the invention 2 obtains software version information and obtains having the flow chart of indicated release software equipment;
The stack equipment that has indicated release software that Fig. 5 provides for the embodiment of the invention 3 duplicates the software of indicated release correspondence to other stack equipment process flow diagram;
The software version update process flow diagram that Fig. 6 provides for the embodiment of the invention 4;
The process flow diagram that software comes into force after the renewal that Fig. 7 provides for the embodiment of the invention 5;
The pile system structural representation that Fig. 8 is provided for the embodiment of the invention 6;
Fig. 9 provides the structural representation of stack equipment for the embodiment of the invention.
Embodiment
Be explained in detail to the main realization principle of embodiment of the invention technical scheme, embodiment and to the beneficial effect that should be able to reach below in conjunction with each accompanying drawing.
As shown in Figure 2, the main realization principle process of the embodiment of the invention 1 is as follows:
Step 10 is obtained the software version of all stack equipments, obtains having the stack equipment of indicated release software.
General pile system all comprises two or more stack equipments, and the software version of every stack equipment may be inconsistent.The software version here indicates that by software version number different software versions possesses different software version number.
In stack equipment, comprise a main equipment, other be slave unit.General, obtain the software version of all stack equipments and finish by main equipment.Main equipment obtains the specific region canned data that software version own just reads storing software version information on this equipment, and for other slave unit, need do and obtain alternately by piling up connectivity port and other slave unit, detailed process is as shown in Figure 3, wherein
A. main equipment sends the message of obtaining version number and arrives equipment n;
B. equipment n receives message, replys response message and gives main equipment, comprising the software version number information of self;
C. after main equipment is received version number information, send again and finish receiving message to equipment n.
Especially, equipment n then sends version number information to main equipment (being the operation of repeating step c) once more as if the message that finishes receiving of not receiving main equipment at certain hour.If equipment n fails to receive the message that finishes receiving of main equipment always, accumulative total sends the certain number of times of version number information, can enter error handler.The main equipment certain hour is not received version number's message of equipment n, the then operation of repeating step a.If failing, accumulative total behind certain number of times, enters error handler.
Especially, error handler, different because of system, can be that certain error event has taken place simple prompting user, perhaps interrupt stacking process, concrete setting is carried out according to actual needs, and can adjust at any time.
After having obtained the version information of all stack equipments, these version informations can be noted, compare, therefrom obtain the software version of indicated release, and obtain having the stack equipment of indicated release software.Here, can be the sign of stack equipment, for example, can be that device number or other can be discerned the sign of stack equipment.
Here, the indicated release of software is meant the software version of specifying all stack equipments to upgrade in advance, can be the software version of the highest software version or other appointment in all stack equipments.
Step 20, the stack equipment that has indicated release software duplicates the software of indicated release correspondence to other stack equipment.
After obtaining the equipment that has indicated release software, main equipment is given notice, and sends the installation file of indicated release software to the equipment of other version by the equipment that has indicated release (not necessarily main equipment).
Preferably, in a pile system, may exist multiple devices to have the software of indicated release simultaneously, also there are multiple devices to be in the lowest version state simultaneously, therefore can allow many indicated release equipment bear the upgrading task of a part respectively to other version equipment, reach further optimization, save the purpose in the processing time of upgrading.For example, 6 equipment stackings, wherein 2 have indicated release, and other 4 are in other release status, can arrange 2 indicated releases to finish 2 device software version updating tasks respectively so, and the software version update time is shortened.
General, indicated release equipment receives after other version device transmission installation file announcement, earlier transmission objectives is added in the formation, according to actual conditions (as the internal memory behaviour in service), offer individual task or a plurality of task and use class TFTP (Trivial File Transport Protocol) agreement, finish the transmission of installation file point-to-point, finish transformation task, or fail because of various reasons and end task, indicated release equipment all needs the result is fed back to main equipment.Main equipment receives that the transmission of each bar as a result after the acknowledgement information, all can upgrade the device version number tabulation of self preserving, and the output information.After waiting to collect all different editions device transmission results messages,, then end task if all transformation tasks all are successes; Otherwise, continue to send the software upgrading announcement to other version equipment, perhaps finish software version update, the prompting failure.If the prompting failure, the user can carry out other operation as required.
Main equipment determines that installation file all behind the end of transmission, gives notice to the equipment that is updated, and replaces the software (or carrying out installation procedure) that is moving, and makes it to come into force.In the general process, main equipment need send information to the equipment of update software version, notifies these device reset to finish the operation of new software version.
Preferably, as shown in Figure 4, the main equipment that provides for the embodiment of the invention 2 obtains software version information and obtains having the flow chart of indicated release software equipment, wherein,
Step 11, original equipment counter (being designated as n) are 1, and total N platform equipment is formed and piled up, and top version number memory cell (being designated as maxnum) initial value is 0;
Here, if indicated release is the highest software version, so, more all be that the software version number of current device and the highest software version number that writes down are before compared at every turn.
Here, be indicated release if the software version of multiple devices is arranged, so, every equipment all can go on record.
Preferably, as shown in Figure 5, the stack equipment that has indicated release software that the embodiment of the invention 3 provides duplicates the software of indicated release correspondence to other stack equipment process flow diagram, and is specific as follows:
Step 21, obtain all devices version number tabulation, and indicated release corresponding equipment number, and initialization apparatus counter (n) is 1, and indicated release unit count device (i) is 0;
Step 22, with indicated release corresponding equipment number subscript as device version number tabulation, promptly obtain indicated release number;
Step 23, relatively whether the version number of current device is indicated release number, finds out the list of devices that has indicated release, if equipment n equals indicated release in version number's list cell, then execution in step 24, otherwise execution in step 25;
Step 24, counter i is added up 1, the device number that will have an indicated release number is recorded in indicated release device number tabulation i in the target unit down;
Step 25, counter n add up 1, and purpose is to judge next version number;
Step 26, judge whether all version numbers' tabulations are all finished dealing with, if do not finish, then execution in step 23, otherwise step 27;
Step 27, the indicated release number of devices that has that will decide are saved among the variable I, and indicated release number of devices counter resets to 1, and version number's tabulation counter resets to 1;
Step 28, find out the equipment of other version, promptly need the equipment that is updated, if the value of the list cell n of version number equals indicated release number, then execution in step 213, otherwise execution in step 29;
Step 29, with the value of counter i subscript as the indicated release tabulation, obtain an indicated release device number, be designated as equipment x, and i adds up 1, purpose is to allow next indicated release device assumes transformation task;
Step 210, send out announcement, require equipment x that installation file is transferred to equipment n to equipment x;
Do you step 211, judge the indicated release circle of whether having rotated? if then execution in step 212, otherwise execution in step 213;
Step 212, i is put 1 again, allow many indicated release equipment enter next round like this and distribute, purpose is to allow in the system many indicated release equipment try one's best share the task of transmission installation file uniformly;
Step 213, the tabulation counter n of version number add up 1;
Step 214, judge whether that the tabulation of whole version number finishes dealing with, if execution in step 215, otherwise execution in step 28;
Step 215, finish, wait for the receipt that these file transmission task are finished to all other version devices advertise file transfer.
As can be seen, this part mainly is made of two parts, the one, step 21 to step 26 is finished the output of indicated release list of devices, the 2nd, step 27 to step 215 is finished and is given highest version equipment with other version equipment uniform distribution, and notice indicated release equipment is to corresponding other version equipment transmission data.These two parts can independently be carried out, that is to say, can not obtain the process of all indicated release software corresponding devices and directly think that with known indicated release equipment miscellaneous equipment transmits version updating information, can not carry out also that all indicated release equipment division of labor transmit the process of software informations and another indicated release equipment is finished.
Preferably, as shown in Figure 6, the software version update process flow diagram that provides for the embodiment of the invention 4, wherein,
The equipment of step 31, other version is received the software upgrading notice of main equipment;
Step 32, notified equipment are understood and are notified, because installation file may be made up of several parts, certain is during upgrading, and differing to establish a capital needs to substitute, and therefore pass through to understand notice, can accomplish the renewal of minimum zone, need to confirm the file of renewal;
Step 33, according to the rapid result of previous step, corresponding file is implemented to substitute operation, main means have the software that will move to rename into backup file (so that follow-up can return to previous release), or directly delete original, the installation file rename with correspondence becomes the system program filename again;
Step 34, execution result is sent to main equipment.Execution result may also may be failed in success, the reason of failure mainly is to damage and can't write as the file storage device, or memory space inadequate causes carrying out operation of duplicating etc., and these failure result information are returned to main equipment, and main equipment carries out follow-up processing as required.
Preferably, as shown in Figure 7, the process flow diagram that software comes into force after the renewal that provides for the embodiment of the invention 5, wherein,
Do you step 43, judge whether acknowledgement information has collected complete? be execution in step 45 then, otherwise execution in step 44;
Here, be not to have only all to reset just can reach the purpose that redaction comes into force by armamentarium, according to circumstances, also can be the reset portion subset, for example, the equipment that those version updating that can only reset are crossed etc.
To sum up, the scheme that the embodiment 2～embodiment 5 is here provided can combine, and constitutes more perfect embodiment.
Accordingly, the pile system that the embodiment of the invention 6 is provided as shown in Figure 8, wherein, main equipment and slave unit 1～3 constitute pile system, when slave unit 4 needs to add pile system, set the different software version of operation on the slave unit 4, concrete software version is as shown in Table 1.
Table one
| Device number | Version number | Transmission is finished | Upgrading is finished |
| 1 | Main equipment version number 1.0 | N | N |
| 2 | |
N | N |
| 3 | Slave unit 2 version numbers 1.0 | N | N |
[0092]?
| 4 | Slave unit 3 version numbers 1.0 | N | N |
| 5 | Slave unit 4 version numbers 2.0 | Y | Y |
As can be seen, the software version that slave unit 4 (device number is 5) is corresponding is the highest.Traversal list one, with each list item and top version number relatively, the corresponding file transfer of sending inequality is announced, as comparing with first list item, drawing needs notification device 5 to equipment 1 transmission installation file, because top version number list of devices has only a member, therefore in the present embodiment, sent the announcement of 4 transmission installation files altogether to equipment 5;
After equipment 5 is handled 4 announcements successively, the result of transmission success is sent to main equipment, promptly equipment 1.Main equipment receives that whenever the transmission of installation file finishes announcement, does sign (transmission is finished to be listed as and is revised as Y) with regard to the corresponding list item of his-and-hers watches 1.After detecting all lowest version list items and all finishing transformation task, send the upgrading announcement to all lowest version equipment; After equipment is received upgrading announcement, the installation file that execution is received, or, replace corresponding file according to system situation.Send upgrading to main equipment after finishing and finish announcement; Main equipment receives that whenever a upgrading finishes announcement, does sign (upgrading is finished row and is revised as Y) with regard to the corresponding list item of his-and-hers watches 1.All finish upgrading when detecting all lowest version equipment, can send the announcement that resets to all devices.Equipment is promptly carried out from reset operation after receiving the announcement that resets; After all devices resets, all reload latest edition software, just finished software version update to this.
Here, all devices is all consulted highest version (default behavior), also can make system can consult into the version of appointment by increasing sign.
Correspondingly, the embodiment of the invention also provides a kind of software version auto-negotiation stack equipment, and as shown in Figure 9, this stack equipment comprises acquiring unit 100, updating block 200 and reset unit 300, wherein,
Acquiring unit 100 is used to obtain the software version of all stack equipments, obtains having the stack equipment of indicated release software.
Updating block 200 is used to notify the stack equipment that has indicated release that the software of indicated release software correspondence is duplicated to other stack equipment.
Here, the indicated release of software is meant the software version of specifying all stack equipments to upgrade in advance, can be the software version of the highest software version or other appointment in all stack equipments.
Preferably, aforesaid equipment also comprises balanced unit 400, is used in the stack equipment quantity that has indicated release software greater than 1 o'clock, specifies wherein an equipment that the software of described indicated release software correspondence is duplicated to other stack equipment; Or specify the stack equipment that has indicated release software of some respectively the software of described indicated release software correspondence to be duplicated to other stack equipment.
Accordingly, the embodiment of the invention also provides a kind of software version auto-negotiation system, and this system comprises some stack equipments, and wherein one is main equipment, wherein,
Main equipment is used to obtain the software version of all stack equipments, obtains having the stack equipment of indicated release software; The stack equipment that notice has an indicated release duplicates the software of described indicated release software correspondence to other stack equipment; And notify described other stack equipment to replace current operating software with the software of described indicated release correspondence;
Other described stack equipment is used for the notice according to main equipment, and software version is sent to main equipment; Duplicate software to other stack equipment or receive the software of other stack equipment and replace current operating software with indicated release software according to the notice of main equipment according to the notice of main equipment.
To sum up, the scheme that the embodiment of the invention provides makes between stack equipment and can consult software version automatically, reaches to use indicated release software to obtain more stable more powerful ability to work.Simultaneously, can simplify stack equipment and use step, all stack equipments of avoiding manually upgrading avoid the software operation error to cause the possibility of variety of problems to the troublesome operation of same software version.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (10)
1. a software version auto-negotiation method is characterized in that, this method comprises:
Obtain the software version of all stack equipments, obtain having the stack equipment of indicated release software;
The described stack equipment that has indicated release software duplicates the software of described indicated release correspondence to other stack equipment;
Described other stack equipment is replaced current operating software with the software of described indicated release correspondence.
2. the method for claim 1 is characterized in that, the described software version that obtains all stack equipments obtains having the stack equipment of indicated release software, comprising:
Main equipment in the stack equipment obtains the software version of all stack equipments, one by one relatively version number obtaining version number's software version identical with indicated release, and the stack equipment of record correspondence number.
3. method as claimed in claim 1 or 2, it is characterized in that, with the operating software version is the highest in the described stack equipment software version as indicated release, the then described software version that obtains all stack equipments, obtain having the stack equipment of indicated release software, comprising:
Main equipment in the stack equipment obtains the software version of all stack equipments, respectively relatively version number obtaining the highest software version of version number, and the corresponding stack equipment of record number.
4. method as claimed in claim 2 is characterized in that, the described stack equipment that has indicated release software duplicates the software of described indicated release correspondence to other stack equipment, comprising:
Main equipment in the stack equipment is according to the software version of stack equipment, and the notice software version is that the stack equipment of indicated release duplicates the software of indicated release correspondence to other stack equipment.
5. as claim 1 or 4 described methods, it is characterized in that, if the stack equipment quantity that has indicated release software greater than 1, then specifies wherein an equipment that the software of described indicated release software correspondence is duplicated to other stack equipment; Or specify wherein that many stack equipments that have indicated release software duplicate the software of described indicated release software correspondence to other stack equipment respectively.
6. the method for claim 1 is characterized in that, described other stack equipment is replaced current operating software with the software of described indicated release correspondence, comprising:
Other stack equipment receives the software of described indicated release correspondence, replaces all or part of corresponding document of current operating software, and the software after the operation replacement.
7. the method for claim 1 is characterized in that, this method further comprises:
After main equipment in the stack equipment determines that the software version of all stack equipments all is updated to indicated release, the stack equipment behind reset all stack equipments or the software version update that resets.
8. a software auto-negotiation stack equipment is characterized in that this stack equipment comprises acquiring unit, updating block and reset unit, wherein,
Described acquiring unit is used to obtain the software version of all stack equipments, obtains having the stack equipment of indicated release software;
Described updating block is used to notify the stack equipment that has indicated release software that the software of described indicated release software correspondence is duplicated to other stack equipment;
Described reset unit is used to notify described other stack equipment to replace current operating software with the software of described indicated release correspondence.
9. stack equipment as claimed in claim 8, it is characterized in that, this equipment also comprises balanced unit, is used in the stack equipment quantity that has indicated release software greater than 1 o'clock, specifies wherein an equipment that the software of described indicated release software correspondence is duplicated to other stack equipment; Or specify the stack equipment that has indicated release software of some respectively the software of described indicated release software correspondence to be duplicated to other stack equipment.
10. a software version auto-negotiation system is characterized in that this system comprises some stack equipments, and wherein one is main equipment, wherein,
Described main equipment obtains the software version of all stack equipments, obtains having the stack equipment of indicated release software; The stack equipment that notice has indicated release software duplicates the software of described indicated release software correspondence to other stack equipment; And notify described other stack equipment to replace current operating software with the software of described indicated release correspondence;
Stack equipment in the described software version auto-negotiation system except that described main equipment is used for the notice according to main equipment, and software version is sent to main equipment; Duplicate software to other stack equipments or receive the software of other stack equipments and replace current operating software with indicated release software according to the notice of main equipment according to the notice of main equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102278389A CN101478422B (en) | 2008-12-01 | 2008-12-01 | Self negotiation method and system for software version |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102278389A CN101478422B (en) | 2008-12-01 | 2008-12-01 | Self negotiation method and system for software version |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101478422A CN101478422A (en) | 2009-07-08 |
| CN101478422B true CN101478422B (en) | 2010-12-22 |
Family
ID=40839057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008102278389A Expired - Fee Related CN101478422B (en) | 2008-12-01 | 2008-12-01 | Self negotiation method and system for software version |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101478422B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012171349A1 (en) * | 2011-06-15 | 2012-12-20 | 中兴通讯股份有限公司 | Method, apparatus and system for implementing distributed auto-incrementing counting |
| CN105763368A (en) * | 2016-02-04 | 2016-07-13 | 杭州华三通信技术有限公司 | Stacking method and device |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101674198B (en) * | 2009-10-23 | 2011-09-28 | 杭州华三通信技术有限公司 | Method and device for realizing stacking |
| CN104503811B (en) * | 2015-01-09 | 2018-04-20 | 烽火通信科技股份有限公司 | Upgrade method for communication device and system based on single memory block |
| CN106028142B (en) * | 2016-05-25 | 2019-05-28 | Oppo广东移动通信有限公司 | A kind of upgrade control method and device of playback equipment |
| CN107426031B (en) * | 2017-08-08 | 2020-06-02 | 迈普通信技术股份有限公司 | Stack configuration method and device |
| CN109379222B (en) * | 2018-10-15 | 2022-02-25 | 视联动力信息技术股份有限公司 | Method and system for comparing versions of core servers |
| CN109981364B (en) * | 2019-03-25 | 2021-05-18 | 联想(北京)有限公司 | Network management method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0279232A2 (en) * | 1987-02-13 | 1988-08-24 | International Business Machines Corporation | A system and method for version level negotiation |
| CN101179430A (en) * | 2007-12-03 | 2008-05-14 | 中兴通讯股份有限公司 | Device and method of controlling distributed system software version updating |
| CN101217411A (en) * | 2008-01-02 | 2008-07-09 | 杭州华三通信技术有限公司 | A method, device and system realizing the upgrading of stacking device software |
-
2008
- 2008-12-01 CN CN2008102278389A patent/CN101478422B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0279232A2 (en) * | 1987-02-13 | 1988-08-24 | International Business Machines Corporation | A system and method for version level negotiation |
| CN101179430A (en) * | 2007-12-03 | 2008-05-14 | 中兴通讯股份有限公司 | Device and method of controlling distributed system software version updating |
| CN101217411A (en) * | 2008-01-02 | 2008-07-09 | 杭州华三通信技术有限公司 | A method, device and system realizing the upgrading of stacking device software |
Non-Patent Citations (1)
| Title |
|---|
| JP特开2006-119750A 2006.05.11 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012171349A1 (en) * | 2011-06-15 | 2012-12-20 | 中兴通讯股份有限公司 | Method, apparatus and system for implementing distributed auto-incrementing counting |
| CN105763368A (en) * | 2016-02-04 | 2016-07-13 | 杭州华三通信技术有限公司 | Stacking method and device |
| CN105763368B (en) * | 2016-02-04 | 2019-04-09 | 新华三技术有限公司 | A kind of stacking method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101478422A (en) | 2009-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101478422B (en) | Self negotiation method and system for software version | |
| CN100470494C (en) | Cluster availability management method and system | |
| CN101217411B (en) | A method, device and system realizing the upgrading of stacking device software | |
| US8892712B2 (en) | Upgrading enterprise managers | |
| CN101110776B (en) | Backup method, backup device and backup system for data business | |
| CN104486394B (en) | In-service Software Upgrade method and device | |
| CN101888304A (en) | Updating method, device and system for routing equipment | |
| WO2024078205A1 (en) | Bus load determination method and apparatus, household appliance device, and storage medium | |
| CN115914139A (en) | Ordered stack formation with reduced human intervention | |
| WO1997049034A1 (en) | Job taking-over system | |
| KR20030051930A (en) | Apparatus and method for embodying high availability in cluster system | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN115499300B (en) | Embedded equipment clustering operation architecture system, construction method and construction device | |
| CN103684720A (en) | Selection method and device for master and slave service unit | |
| CN101420329B (en) | Method for upgrading communication system and communication system therefor | |
| JP4034201B2 (en) | Computer resource utilization method and computer resource utilization method | |
| JP2004112721A (en) | Redundant configuration communication device and system switching method | |
| CN101655812B (en) | Self-adaptive data backup system and method thereof | |
| US11853175B2 (en) | Cluster system and restoration method that performs failover control | |
| CN115378557B (en) | Hot standby implementation method, device, system, electronic equipment and storage medium | |
| CN1722627A (en) | A method and device for realizing switching between main and backup units in communication equipment | |
| CN110855505B (en) | High-availability rule stacking implementation system and method | |
| CN102156685A (en) | Method and device for automatically configuring distributed network system script | |
| JP2001306351A (en) | Fault handling system in computer system | |
| JP2570134B2 (en) | Data broadcast transfer method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C57 | Notification of unclear or unknown address | ||
| DD01 | Delivery of document by public notice |
Addressee: Jing Pengxin Document name: Notice of application for publication of patent for invention and entry into the substantive examination procedure |
|
| DD01 | Delivery of document by public notice |
Addressee: BEIJING STAR-NET RUIJIE NETWORKS Co.,Ltd. Document name: Review of business letter |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20101222 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |