CN101645801A - Software version upgrading method based on cluster management and order exchange board - Google Patents
Software version upgrading method based on cluster management and order exchange board Download PDFInfo
- Publication number
- CN101645801A CN101645801A CN200910167582A CN200910167582A CN101645801A CN 101645801 A CN101645801 A CN 101645801A CN 200910167582 A CN200910167582 A CN 200910167582A CN 200910167582 A CN200910167582 A CN 200910167582A CN 101645801 A CN101645801 A CN 101645801A
- Authority
- CN
- China
- Prior art keywords
- version
- upgraded
- type
- command switch
- software 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000005516 engineering process Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000012790 confirmation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 101100059544 Arabidopsis thaliana CDC5 gene Proteins 0.000 description 1
- 101150115300 MAC1 gene Proteins 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000004044 response Effects 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
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 discloses a software version upgrading method based on cluster management and an order exchange board. In the method, the order exchange board receives the corresponding relationship ofan upgrading device type and software version information from a version server; according to an identification, the order exchange board obtains the information of one or a plurality of non-upgradedmember machines and sends a version upgrading request to one or a plurality of member machines, so that one or a plurality of member machines send the request for downloading an upgrading version to the version server; the order exchange board receives an software version to be upgraded from the version server and sends to the non-upgraded member machines which send the request for downloading anupgrading version to the version server. The technical scheme provided by the invention solves the problems that software version upgrading efficiency is low in the relevant technology and automatic version upgrading function can not be realized, so that the invention can realize automatic software version upgrading and improve the software version upgrading efficiency.
Description
Technical Field
The invention relates to the field of communication, in particular to a software version upgrading method based on cluster management and a command switch.
Background
With the development of ethernet technology, the application of ethernet switches is becoming more and more extensive, but because ethernet switches have more devices (especially low-end devices), the management of the devices becomes a difficult problem, and therefore a solution for cluster management is proposed. The hardware of the switch device may be of different hardware types and therefore the version of software that needs to be installed is different.
In the above cluster management manner, the currently adopted software version upgrading method is as follows: all the software versions which are possibly used are stored in the version server, then the switch is instructed to log in each member machine, and the software matched with the member machine is manually downloaded from the version server to the member machine according to the type of the member machine, so that the software version of the member machine is updated.
The software version upgrading method has the following problems: network management personnel need to know the type of each member machine and manually download the version for software upgrading, and under the condition that the number of the managed member machines is large, the workload of the network management personnel is greatly increased, so that the software version upgrading efficiency is low, and the automatic upgrading function of the version cannot be realized.
Disclosure of Invention
The invention is provided for solving the problems that the software version upgrading efficiency is low and the automatic upgrading function of the version cannot be realized in the related technology, and therefore, the invention mainly aims to provide an improved software version upgrading scheme based on cluster management to solve at least one of the problems.
According to one aspect of the invention, a software version upgrading method based on cluster management is provided.
The software version upgrading method based on cluster management is applied to a system comprising a command switch, a version server and one or more member machines, and comprises the following steps: the command switch receives a corresponding relation between the updated equipment type and the software version information from the version server, wherein the corresponding relation carries an identifier indicating whether each equipment type and each member machine are updated; the command switch acquires information of one or more un-upgraded member machines according to the identification, and sends a version updating request to the one or more un-upgraded member machines so that the one or more un-upgraded member machines send a request for downloading the upgraded version to the version server; the command switch receives the software version to be upgraded from the version server and sends the software version to the un-upgraded member machine which sends a request for downloading the upgraded version to the version server.
According to another aspect of the present invention, a command switch is provided.
The command switch according to the present invention comprises: the system comprises a receiving unit and a updating unit, wherein the receiving unit is used for receiving a corresponding relation between an updated equipment type and software version information from a version server and receiving a software version to be updated from the version server, and the corresponding relation carries an identifier indicating whether each equipment type and each member machine are updated or not; the acquisition unit is used for acquiring information of one or more non-upgraded member machines according to the identification; and the sending unit is used for sending a version updating request to one or more un-upgraded member machines so as to enable the one or more un-upgraded member machines to send a request for downloading the upgraded version to the version server and send the software version to be upgraded to the one or more un-upgraded member machines.
According to the invention, the command switch selects the matched new version according to the equipment type, so that the automatic upgrading function of the software version is realized, the problems that the software version upgrading efficiency is low and the automatic upgrading function of the version cannot be realized in the related technology are solved, the automatic upgrading of the software version can be realized, and the upgrading efficiency of the software version is improved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flowchart of a software version upgrade method based on cluster management according to an embodiment of the present invention;
FIG. 2 is a table of device type and software version matches according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a Group Management Protocol (GMP) message format according to an embodiment of the present invention;
FIG. 4 is a flowchart of a software version upgrade method based on cluster management according to a preferred embodiment of the present invention;
FIG. 5 is a block diagram of a command switch based on cluster management according to an embodiment of the present invention;
fig. 6 is a block diagram of a command switch based on cluster management according to a preferred embodiment of the present invention.
Detailed Description
Overview of the function
In consideration of the problems that the software version upgrading efficiency in the related technology is low and the automatic upgrading function of the version cannot be realized, the embodiment of the invention provides a software version upgrading scheme based on cluster management, and according to the embodiment provided by the invention, a switch is firstly instructed to establish the corresponding relation between the equipment type and the software version information; and then the corresponding relation is sent to a version server for common management. The command switch receives a corresponding relation between the updated equipment type and the software version information from the version server, wherein the corresponding relation carries an identifier indicating whether each equipment type and each member machine are updated; the command switch acquires information of one or more un-upgraded member machines according to the identification, and sends a version updating request to the one or more un-upgraded member machines so that the one or more un-upgraded member machines send a request for downloading the upgraded version to the version server; the command switch receives the software version to be upgraded from the version server and sends the software version to the un-upgraded member machine which sends a request for downloading the upgraded version to the version server.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
Method embodiment
According to the embodiment of the invention, firstly, a software version upgrading method based on cluster management is provided.
Fig. 1 is a flowchart of a software version upgrading method based on cluster management according to an embodiment of the present invention. As shown in fig. 1, the software version upgrading method based on cluster management according to the embodiment of the present invention includes the following processes (step S101-step S105):
the command switch establishes a corresponding relation between the equipment type and the software version information before establishing a cluster relation; and sending the corresponding relation to the version server.
Preferably, before establishing the cluster relationship, the command switch collects the hardware and software version types of each device through the neighbor discovery protocol and the topology collection protocol, creates a device type and software version matching table (corresponding to the corresponding relationship), and sends the table to the version server, where the table is maintained by both the device type and the software version matching table. The matching table adopts a Hash storage mode, and is beneficial to improving the query efficiency of version types. After that, step S101 is executed.
Step S101: the command switch receives a corresponding relation between the updated equipment type and the software version information from the version server, wherein the corresponding relation carries an identifier indicating whether each equipment type and each member machine are updated;
preferably, the correspondence between the device type and the software version information may be updated by: and the network manager adds the equipment type and the software version information corresponding to the software version to be upgraded in the version server into the corresponding relationship.
In a specific implementation process, after a network administrator adds an upgrade version of a certain device type to a version server, the corresponding device type and upgrade version model entry is added into a corresponding relationship (here, taking a matching table as an example), and type and device update flags are respectively set in the corresponding entry (default to no). And when all the table entries needing to be updated are added into the matching table, the server issues the matching table to the command switch.
Specifically, the matching table may refer to fig. 2, and fig. 2 is a table for matching a device type and a software version according to an embodiment of the present invention. As shown in fig. 2, the device type and software version matching table according to the embodiment of the present invention adopts a hash storage manner, and the hash matching table includes: device type, type update flag, Media Access Control (MAC) address, device update flag, running version type, upgrade version type, and so on. For example, the device type shown in the figure is a, the state of type update identification NO (NO) of the type indicates that there is currently a member machine that is not upgraded, and the device type includes the state of device update identification NO (NO) corresponding to the member machine with MAC address MAC1, indicating that the member machine is in a state to be upgraded. The current running version type of the member machine is A, and the version type to be upgraded is A +.
Step S103: the command switch acquires information of one or more un-upgraded member machines according to the identification, and sends a version updating request to the one or more un-upgraded member machines so that the one or more un-upgraded member machines send a request for downloading the upgraded version to the version server;
preferably, the step of the command switch acquiring information of one or more non-upgraded member machines according to the identifier includes the following steps:
(1) the command switch searches for the state of a type update identifier which is corresponding to each equipment type and indicates whether each equipment type is updated or not by taking the equipment type as a keyword;
(2) when the state of the type updating identifier is negative, searching the state of the device updating identifier which indicates whether each member machine is updated or not and corresponds to each member machine contained in the device type;
(3) the command switch determines that one or more member machines of which the status of the device update identification is negative are in an uneupgrade-free state.
Preferably, the command switch encapsulates the MAC address corresponding to the one or more un-upgraded member machines and the software version information to be upgraded in a GMP message, and sends the GMP message to the one or more un-upgraded member machines.
Fig. 3 may refer to the GMP message format, and fig. 3 is a schematic diagram of the GMP message format according to an embodiment of the present invention. As shown in fig. 3, the GMP message format is as follows:
(1) the version number/role occupies one byte, the cluster management version number occupies 4 bits, the role occupies 4 bits, and the value is taken as a command switch, a member machine or a candidate machine;
(2) the master command code and the slave command code are combined to determine a unique message type, for example, the message type set by the master command code is "candidate switch joins the cluster to become a member switch", and the message type set by the slave command code includes operation types such as join request, authentication response, join confirmation, configuration information, join confirmation and the like. The master command code may be uniformly set as a "version download" message type, and the message types set from the command code include "version update request", "version update success", "restart request", "trap", and other operation types.
(3) Message body: and realizing the correct analysis of the message body according to the master command code and the slave command code. In the above steps, after the command switch or the member machine receives the GMP message, the message body is analyzed according to the message types uniquely determined by the master command code and the slave command code, thereby performing the related operation.
In the specific implementation process, after the command switch receives the updated matching table, the command switch firstly checks a type updating mark corresponding to a certain type of equipment, if the type updating mark is 'NO', the command switch indicates that the equipment of the type has the non-updated member machines, and the conflict chains are sequentially searched downwards. If the equipment updating mark corresponding to a certain MAC address is 'YES', the update version of the member machine is successful, otherwise, the information of the MAC address, the upgrade version model and the like of the member machine is packaged in a Group Management Protocol (GMP) message as a message, and the 'version update request' message is forwarded to the member machine in a unicast mode. And after receiving the GMP message, the member machine sends a tFTP or FTP request message for downloading the upgraded version to the version server.
Step S105: the command switch receives the software version to be upgraded from the version server and sends the software version to the un-upgraded member machine which sends a request for downloading the upgraded version to the version server.
In the specific implementation process, after receiving the request message, the version server sends the upgrade version with the matched type to the member machine sending the request message through the command switch.
Preferably, after instructing the switch to send the software version to be upgraded to the non-upgraded member machine that has sent the request for downloading the upgraded version to the version server, the following processing may be further included:
(1) under the condition that the downloading of the software version to be upgraded fails, the command switch receives a message sent by a member machine which is not upgraded, and sends the message to the version server within a preset number of times to request for re-sending, wherein the message is used for indicating the reason of the downloading failure.
For example, if the member machine fails to download the software version to be upgraded, the command switch sends a trap message to the network manager to report the failure reason, and requests the version server to send down again within the preset times until the member machine succeeds in downloading the software version to be upgraded. For example, the number of requests for retransmission may be limited to 3. If the 3 requests are not successfully downloaded, the process ends.
(2) Under the condition that the software version to be upgraded is downloaded successfully, instructing the switch to receive a version updating success message sent by a member machine which is not upgraded, wherein the version updating success message carries an MAC address corresponding to the member machine which is not upgraded;
preferably, after the command switch receives the version update success message sent by the un-upgraded member machine, the command switch sets the device update identifier corresponding to the MAC address to be in a yes state in the corresponding relationship, sets the currently running version type to be the version type to be upgraded, and clears the field included in the upgraded version type;
preferably, when all the non-upgraded member machines included in one device type are completely upgraded, the command switch sets the type update identifier corresponding to the device type to be in a yes state in the corresponding relationship;
preferably, when all the member machines corresponding to the device types included in the correspondence relation are upgraded, the command switch returns the correspondence relation to the version server.
For example, after receiving the message of "version update success", the command switch sets the "equipment update flag" corresponding to the MAC address to "YES", and updates the "running version type" to the "upgrade version type" and clears the "upgrade version type" at the same time; after receiving the restart request message, the command switch issues a restart command to the member machine in a unicast and time-delay manner. And after receiving the command, the member machine restarts the equipment, loads the upgrade version according to the path in the configuration file, and establishes a cluster relation with the command switch after the equipment is started successfully.
Fig. 4 is a flowchart of a software version upgrading method based on cluster management according to a preferred embodiment of the present invention. As shown in fig. 4, the software version upgrading method based on cluster management according to the preferred embodiment of the present invention mainly includes the following processes (steps S401 to S419):
step S401: before establishing a cluster relationship, a command switch collects the hardware and software version types of each device through a neighbor discovery protocol and a topology collection protocol, creates a Hash matching table of the device type and the software version, sends the Hash matching table to a version server, and enters step S403;
step S403: when an upgrade version of a certain device type is added to the version server by a network manager, the corresponding device type and upgrade version model table entry is added into the matching table, and the type and device update flag is set in the corresponding table entry respectively (no by default). When all the items needing to be updated are added into the matching table, the server issues the matching table to the command switch, and the step S405 is executed;
step S405: the software versions corresponding to the devices with the same type are also the same, so that the command switch searches for the version type by taking the device type as a key after receiving the updated matching table. For the same type of equipment, because the corresponding equipment ID and MAC address in the cluster system are different, the state that the 'type updating mark' is 'NO' indicates that the equipment of the type has an unrefreshed member machine, the conflict chain sequentially searches the table entry with the 'equipment updating mark' being 'NO' downwards, and encapsulates the information such as the MAC address, the upgrade version model and the like corresponding to the searched table entry as the message in the GMP message, and forwards the message as the 'version updating request' to the member machine, and the step S407 is entered;
step S407: after receiving the GMP message, the member machine sends a tFTP or FTP request message for downloading the upgrade version to the version server, and then the step S409 is executed;
step S409: after receiving the request message, the version server sends an upgrade version with a matched type to the member machine through the command switch, if the member machine is successfully downloaded, the step S413 is executed, otherwise, the step S411 is executed;
step S411: sending a 'trap' message to the version server by the command switch to report the reason of failure, requesting to be issued again, limiting the number of times of requesting to be retransmitted to 3 times, and entering step S407;
step S413: writing the path saved by the upgrade version into a configuration file, saving the configuration of the path, sending a message of 'version update success' and a request message needing 'restart' to the command switch, and entering step S415;
step S415: after receiving the message of 'version updating success', the command switch sets the 'equipment updating mark' corresponding to the MAC address to 'YES', and simultaneously updates the 'running version type' into the 'upgrading version type' and clears the 'upgrading version type'; after receiving the restart request message, the command switch issues a restart command to the member machine in a unicast and time-delay manner. And after receiving the command, the member machine restarts the equipment, loads the upgrade version according to the path in the configuration file, and establishes a cluster relation with the command switch after the equipment is started successfully. If all member machines of a certain type complete the version upgrading process, step S417 is entered, otherwise step S405 is entered;
step S417: the command exchange will set the "type update flag" corresponding to the type device to "YES", then enter the processing flow of the next type device, if all types of devices are processed, enter step S419, otherwise enter step S403;
step S419: and when all the devices of the whole matching table finish the upgrading process, the command switch feeds the matching table back to the version server to be used as the operation and maintenance reference information of the network management personnel.
Through the embodiment, the software version upgrading method based on cluster management is provided. The automatic upgrading function of the software version can be realized by commanding the switch to select the matched new version according to the equipment type.
Device embodiment
According to the embodiment of the invention, the invention also provides the command switch.
Fig. 5 is a block diagram of a command switch based on cluster management according to an embodiment of the present invention. Fig. 6 is a block diagram of a command switch based on cluster management according to a preferred embodiment of the present invention. As shown in fig. 5, the command switch based on cluster management according to the embodiment of the present invention includes: receiving unit 1, acquiring unit 2, and transmitting unit 3. Described below in conjunction with fig. 6.
The receiving unit 1 is configured to receive a correspondence between an updated device type and software version information from a version server, and receive a software version to be upgraded from the version server, where the correspondence carries an identifier indicating whether each device type and each member machine have been updated;
the acquisition unit 2 is connected with the receiving unit 1 and used for acquiring information of one or more non-upgraded member machines according to the identification;
preferably, as shown in fig. 6, the acquiring unit 2 includes: a first searching module 20, configured to search, by using the device type as a keyword, a state of a type update identifier corresponding to each device type and indicating whether each device type has been updated; the second searching module 22 is configured to, when the state of the type update identifier is negative, search a state of an equipment update identifier, which indicates whether each member machine has been updated, corresponding to each member machine included in the equipment type; and the determining module 24 is configured to determine that one or more member machines with the device update identifier and the status of no are in the non-upgraded status.
And the sending unit 3 is connected with the obtaining unit 2 and is used for sending a version updating request to one or more non-upgraded member machines so as to enable the one or more non-upgraded member machines to send a request for downloading the upgraded version to the version server and send the software version to be upgraded to the one or more non-upgraded member machines.
Preferably, as shown in fig. 6, the command switch further includes: the creating unit 4 is used for creating the corresponding relation between the equipment type and the software version information; the sending unit 3 is further configured to send the corresponding relationship to the version server.
Preferably, the sending unit 3 encapsulates the MAC address and the software version information to be upgraded corresponding to one or more non-upgraded member devices in a GMP message, and sends the GMP message to the one or more non-upgraded member devices.
Preferably, the receiving unit 1 is further configured to receive a version update success message sent by the un-upgraded member machine under the condition that the software version to be upgraded is downloaded successfully, where the version update success message carries an MAC address corresponding to the un-upgraded member machine; or, the receiving unit 1 is further configured to receive a message sent from a member machine that is not upgraded under the condition that the download of the software version to be upgraded fails, and send the message to the version server within a predetermined number of times to request for reissuing, where the message carries information about a reason for the download failure.
Preferably, as shown in fig. 6, the command switch may further include: the setting unit 5 is configured to set the device update identifier corresponding to the MAC address to a yes state in the correspondence under the condition that the software version to be upgraded is downloaded successfully, set the currently running version type to the version type to be upgraded, and clear fields included in the version type to be upgraded; the setting unit 5 is further configured to set, in the correspondence, a type update flag corresponding to a device type to be in a yes state when all the non-upgraded member machines included in the device type are completely upgraded; the sending unit 3 is further configured to return the corresponding relationship to the version server when all the member machines corresponding to the device types included in the corresponding relationship are upgraded.
Through the embodiment, the command switch is provided, and the problems that the software version upgrading efficiency is low and the version automatic upgrading function cannot be realized in the related technology can be solved through the mutual combination of the receiving unit 1, the obtaining unit 2 and the sending unit 3, so that the software version can be automatically upgraded, and the software version upgrading efficiency is improved.
In summary, according to the cluster management-based software version upgrading method and the command switch provided by the embodiments of the present invention, the command switch selects the new version matched with the device type according to the device type, so that the problems that the manual upgrade mode adopted in the related art is inefficient and the automatic version upgrade function cannot be realized can be solved, and thus, the automatic upgrade of the software version can be realized, the software version upgrade efficiency is improved, and the user experience is improved.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (11)
1. A software version upgrading method based on cluster management is applied to a system comprising a command switch, a version server and one or more member machines, and is characterized by comprising the following steps:
the command switch receives a corresponding relation between an updated equipment type and software version information from the version server, wherein the corresponding relation carries an identifier indicating whether each equipment type and each member machine are updated;
the command switch acquires information of one or more uneupgraded member machines according to the identification, and sends a version updating request to the one or more uneupgraded member machines so that the one or more uneupgraded member machines send a request for downloading an upgraded version to the version server;
and the command switch receives the software version to be upgraded from the version server and sends the software version to the un-upgraded member machine which sends a request for downloading the upgraded version to the version server.
2. The method of claim 1, wherein before the command switch receives the updated correspondence of device type and software version information from the version server, the method further comprises:
the command switch establishes a corresponding relation between the equipment type and the software version information;
and the command switch sends the corresponding relation to the version server.
3. The method of claim 1, wherein the instructing the switch to obtain information of one or more non-upgraded member machines according to the identification comprises:
the command switch searches for the state of a type update identifier which is corresponding to each equipment type and indicates whether each equipment type is updated or not by taking the equipment type as a keyword;
when the state of the type updating identifier is negative, searching the state of the device updating identifier which indicates whether each member machine is updated or not and corresponds to each member machine contained in the device type;
and the command switch determines that one or more member machines with the device update identification of which the state is negative are in the non-upgraded state.
4. The method of claim 1, wherein the command switch sends a version update request to the one or more non-upgraded member machines by:
and the command switch encapsulates the media access control MAC addresses corresponding to the one or more un-upgraded member machines and the software version information to be upgraded in a GMP (group management protocol) message and sends the message to the one or more un-upgraded member machines.
5. The method of any of claims 1-4, wherein after the command switch sends the software version to be upgraded to the non-upgraded member machines that have sent a download upgrade version request to the version server, the method further comprises:
under the condition that the software version to be upgraded is downloaded successfully, the command switch receives a version updating success message sent by the un-upgraded member machine, wherein the version updating success message carries an MAC address corresponding to the un-upgraded member machine;
and under the condition that the downloading of the software version to be upgraded fails, the command switch receives a message sent by the un-upgraded member machine, and sends the message to the version server within a preset number of times to request for re-issuing, wherein the message is used for indicating the reason of the downloading failure.
6. The method of claim 5, wherein after the command switch receives a version update success message sent from the unequified member machine, the method further comprises:
the command switch sets the equipment updating identification corresponding to the MAC address to be in a yes state in the corresponding relation, sets the currently running version type to be the version type to be upgraded and clears the field contained in the upgraded version type;
when all the un-upgraded member machines included in one equipment type are completely upgraded, the command switch sets the type updating identification corresponding to the equipment type to be in a yes state in the corresponding relationship;
and when the member machines corresponding to all the equipment types contained in the corresponding relation are upgraded, the command switch returns the corresponding relation to the version server.
7. A command switch, characterized in that the command switch comprises:
a receiving unit, configured to receive a correspondence between an updated device type and software version information from the version server, and receive a software version to be upgraded from the version server, where the correspondence carries an identifier indicating whether each device type and each member machine have been updated;
the acquisition unit is used for acquiring information of one or more non-upgraded member machines according to the identification;
and the sending unit is used for sending a version updating request to the one or more un-upgraded member machines so as to enable the one or more un-upgraded member machines to send a request for downloading an upgraded version to the version server and send the software version to be upgraded to the one or more un-upgraded member machines.
8. The command switch of claim 7,
the command switch further comprises:
the creating unit is used for creating a corresponding relation between the equipment type and the software version information;
the sending unit is further configured to send the correspondence to the version server, and package the MAC address corresponding to the one or more un-upgraded member machines and software version information to be upgraded in a GMP (group management protocol) message to send to the one or more un-upgraded member machines.
9. The command switch of claim 8, wherein the obtaining unit comprises:
the first searching module is used for searching the state of a type updating identifier which is corresponding to each equipment type and indicates whether each equipment type is updated or not by taking the equipment type as a keyword;
a second searching module, configured to search, when the state of the type update identifier is negative, a state of an equipment update identifier indicating whether each member machine has been updated, which is corresponding to each member machine included in the equipment type;
and the determining module is used for determining that one or more member machines with the updated device identifiers in a negative state are in an un-upgraded state.
10. The command switch of any of claims 7-9,
the receiving unit is further configured to receive a version update success message sent by the un-upgraded member machine under the condition that the software version to be upgraded is downloaded successfully, where the version update success message carries an MAC address corresponding to the un-upgraded member machine; or,
the receiving unit is further configured to receive a message sent by the non-upgraded member computer under the condition that the download of the software version to be upgraded fails, and send the message to the version server within a predetermined number of times to request for reissuing, where the message carries reason information of the download failure.
11. The command switch of claim 10, further comprising:
a setting unit, configured to set, in the correspondence, an equipment update identifier corresponding to the MAC address to a yes state, set a currently running version type as the version type to be upgraded, and clear a field included in the upgraded version type when the software version to be upgraded is successfully downloaded;
the setting unit is further configured to set a type update flag corresponding to a device type to a yes state in the correspondence when all the non-upgraded member machines included in the device type are completely upgraded;
the sending unit is further configured to return the corresponding relationship to the version server when all the member machines corresponding to all the device types included in the corresponding relationship are upgraded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101675821A CN101645801B (en) | 2009-08-27 | 2009-08-27 | Software version upgrading method based on cluster management and order exchanger |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101675821A CN101645801B (en) | 2009-08-27 | 2009-08-27 | Software version upgrading method based on cluster management and order exchanger |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101645801A true CN101645801A (en) | 2010-02-10 |
| CN101645801B CN101645801B (en) | 2012-02-08 |
Family
ID=41657526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101675821A Expired - Fee Related CN101645801B (en) | 2009-08-27 | 2009-08-27 | Software version upgrading method based on cluster management and order exchanger |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101645801B (en) |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101873726A (en) * | 2010-07-01 | 2010-10-27 | 华为终端有限公司 | Upgrading method of wireless repeater and wireless access equipment |
| CN102143506A (en) * | 2010-10-20 | 2011-08-03 | 华为终端有限公司 | Management processing method, management processing device and management processing system for wireless repeater |
| CN102300200A (en) * | 2011-09-08 | 2011-12-28 | 中兴通讯股份有限公司 | Software version upgrading method, version publishing equipment and mobile terminal |
| CN102546207A (en) * | 2010-12-23 | 2012-07-04 | 中兴通讯股份有限公司 | Distributed centralized scheduling upgrading method and system for network element software version |
| CN104079631A (en) * | 2014-06-09 | 2014-10-01 | 中国建设银行股份有限公司 | Version management method and related device |
| CN104601622A (en) * | 2013-10-31 | 2015-05-06 | 国际商业机器公司 | Method and system for deploying cluster |
| WO2015127850A1 (en) * | 2014-02-26 | 2015-09-03 | 可牛网络技术（北京）有限公司 | Data upgrading method and central server |
| CN105704241A (en) * | 2016-04-06 | 2016-06-22 | 浪潮电子信息产业股份有限公司 | Client terminal program updating method and system and a service platform |
| CN105915361A (en) * | 2015-11-09 | 2016-08-31 | 乐视致新电子科技（天津）有限公司 | Group upgrading method and device |
| CN106126285A (en) * | 2016-06-22 | 2016-11-16 | 天维尔信息科技股份有限公司 | A kind of method for upgrading software and terminal |
| CN106126286A (en) * | 2016-06-22 | 2016-11-16 | 天维尔信息科技股份有限公司 | A kind of software dispositions method and terminal |
| CN106357771A (en) * | 2016-09-20 | 2017-01-25 | 天脉聚源（北京）科技有限公司 | State synchronization method and device |
| CN107147711A (en) * | 2017-05-04 | 2017-09-08 | 浙江路港互通信息技术有限公司 | Application service update method and device |
| CN107291520A (en) * | 2017-08-14 | 2017-10-24 | 深圳市兆驰数码科技股份有限公司 | A kind of software automatic updating method |
| CN107479877A (en) * | 2017-07-24 | 2017-12-15 | 广东智科电子股份有限公司 | A kind of heat-pump hot-water controller automatically updating method |
| CN108200213A (en) * | 2018-02-13 | 2018-06-22 | 广州云湾信息技术有限公司 | O＆M method, apparatus and system |
| CN108712476A (en) * | 2018-04-27 | 2018-10-26 | 华迪计算机集团有限公司 | A kind of method and system carrying out data update based on push technology |
| CN109299124A (en) * | 2018-09-30 | 2019-02-01 | 北京字节跳动网络技术有限公司 | Method and apparatus for more new model |
| CN109857424A (en) * | 2018-12-20 | 2019-06-07 | 航天信息股份有限公司 | The application upgrade method and device of server cluster |
| US10713032B2 (en) * | 2016-11-14 | 2020-07-14 | Onkyo Corporation | Firmware update system, server, and electronic device |
| CN114531354A (en) * | 2022-04-22 | 2022-05-24 | 北京金山云网络技术有限公司 | Cluster upgrading method and device, cluster controller and server |
| WO2022116450A1 (en) * | 2020-12-03 | 2022-06-09 | 平安科技（深圳）有限公司 | Linux software management method and apparatus, computer device, and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8626146B2 (en) * | 2003-10-29 | 2014-01-07 | Qualcomm Incorporated | Method, software and apparatus for performing actions on a wireless device using action lists and versioning |
| US8151257B2 (en) * | 2007-05-29 | 2012-04-03 | Sap Ag | Managing different versions of server components regarding compatibility with collaborating servers |
| CN101465757B (en) * | 2009-01-15 | 2011-01-12 | 武汉烽火网络有限责任公司 | Method for batch upgrade in cluster network |
| CN101483568B (en) * | 2009-02-04 | 2012-08-22 | 华为终端有限公司 | Upgrading method, control appliance and system for UPnP equipment |
| CN101516047B (en) * | 2009-04-03 | 2011-06-08 | 烽火通信科技股份有限公司 | ONU automatic upgrading method in EPON access system |
-
2009
- 2009-08-27 CN CN2009101675821A patent/CN101645801B/en not_active Expired - Fee Related
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101873726A (en) * | 2010-07-01 | 2010-10-27 | 华为终端有限公司 | Upgrading method of wireless repeater and wireless access equipment |
| CN102143506A (en) * | 2010-10-20 | 2011-08-03 | 华为终端有限公司 | Management processing method, management processing device and management processing system for wireless repeater |
| CN102546207A (en) * | 2010-12-23 | 2012-07-04 | 中兴通讯股份有限公司 | Distributed centralized scheduling upgrading method and system for network element software version |
| CN102546207B (en) * | 2010-12-23 | 2016-04-20 | 中兴通讯股份有限公司 | A kind of method and system of distributed centralization scheduling updating network element software version |
| CN102300200A (en) * | 2011-09-08 | 2011-12-28 | 中兴通讯股份有限公司 | Software version upgrading method, version publishing equipment and mobile terminal |
| CN102300200B (en) * | 2011-09-08 | 2018-04-17 | 中兴通讯股份有限公司 | A kind of method of software release upgrade, version distribution apparatus and mobile terminal |
| CN104601622B (en) * | 2013-10-31 | 2018-04-17 | 国际商业机器公司 | A kind of method and system for disposing cluster |
| CN104601622A (en) * | 2013-10-31 | 2015-05-06 | 国际商业机器公司 | Method and system for deploying cluster |
| WO2015127850A1 (en) * | 2014-02-26 | 2015-09-03 | 可牛网络技术（北京）有限公司 | Data upgrading method and central server |
| CN104079631B (en) * | 2014-06-09 | 2018-10-16 | 中国建设银行股份有限公司 | A kind of method for edition management and relevant apparatus |
| CN104079631A (en) * | 2014-06-09 | 2014-10-01 | 中国建设银行股份有限公司 | Version management method and related device |
| CN105915361A (en) * | 2015-11-09 | 2016-08-31 | 乐视致新电子科技（天津）有限公司 | Group upgrading method and device |
| CN105704241A (en) * | 2016-04-06 | 2016-06-22 | 浪潮电子信息产业股份有限公司 | Client terminal program updating method and system and a service platform |
| CN106126285A (en) * | 2016-06-22 | 2016-11-16 | 天维尔信息科技股份有限公司 | A kind of method for upgrading software and terminal |
| CN106126286A (en) * | 2016-06-22 | 2016-11-16 | 天维尔信息科技股份有限公司 | A kind of software dispositions method and terminal |
| CN106357771A (en) * | 2016-09-20 | 2017-01-25 | 天脉聚源（北京）科技有限公司 | State synchronization method and device |
| CN106357771B (en) * | 2016-09-20 | 2020-03-17 | 天脉聚源（北京）科技有限公司 | State synchronization method and device |
| US10713032B2 (en) * | 2016-11-14 | 2020-07-14 | Onkyo Corporation | Firmware update system, server, and electronic device |
| CN107147711A (en) * | 2017-05-04 | 2017-09-08 | 浙江路港互通信息技术有限公司 | Application service update method and device |
| CN107147711B (en) * | 2017-05-04 | 2020-03-13 | 浙江数链科技有限公司 | Application service updating method and device |
| CN107479877A (en) * | 2017-07-24 | 2017-12-15 | 广东智科电子股份有限公司 | A kind of heat-pump hot-water controller automatically updating method |
| CN107291520A (en) * | 2017-08-14 | 2017-10-24 | 深圳市兆驰数码科技股份有限公司 | A kind of software automatic updating method |
| CN108200213A (en) * | 2018-02-13 | 2018-06-22 | 广州云湾信息技术有限公司 | O＆M method, apparatus and system |
| CN108712476A (en) * | 2018-04-27 | 2018-10-26 | 华迪计算机集团有限公司 | A kind of method and system carrying out data update based on push technology |
| CN109299124A (en) * | 2018-09-30 | 2019-02-01 | 北京字节跳动网络技术有限公司 | Method and apparatus for more new model |
| CN109299124B (en) * | 2018-09-30 | 2021-01-08 | 北京字节跳动网络技术有限公司 | Method and apparatus for updating a model |
| CN109857424A (en) * | 2018-12-20 | 2019-06-07 | 航天信息股份有限公司 | The application upgrade method and device of server cluster |
| WO2022116450A1 (en) * | 2020-12-03 | 2022-06-09 | 平安科技（深圳）有限公司 | Linux software management method and apparatus, computer device, and storage medium |
| CN114531354A (en) * | 2022-04-22 | 2022-05-24 | 北京金山云网络技术有限公司 | Cluster upgrading method and device, cluster controller and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101645801B (en) | 2012-02-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101645801A (en) | Software version upgrading method based on cluster management and order exchange board | |
| CN101552697B (en) | Network access apparatus upgrade system and network access apparatus upgrade method | |
| KR20210057149A (en) | Smart contract-based data processing method, device and storage medium | |
| CN113347225B (en) | OTA (over the air) upgrading method and server for terminal equipment of Internet of things | |
| CN110213359B (en) | Internet of vehicles networking data pushing system and method based on D2D | |
| CN105871568B (en) | Software upgrading method and system | |
| CN101789980A (en) | Batch upgrading method based on cluster network | |
| US20060227790A1 (en) | CSNP cache for efficient periodic CSNP in a router | |
| CN105591796B (en) | Method for configuring network equipment and device | |
| RU2607991C2 (en) | Method and system for service inspection and computer-readable storage medium thereof | |
| CN103517300A (en) | Self-discovery method, device and system of distributed base station | |
| CN103685530A (en) | Automatic upgrade control method and system for WLAN current network APs | |
| CN105656661B (en) | Single board software management method and system | |
| CN109189403B (en) | Operating system OS batch installation method and device and network equipment | |
| CN109428824B (en) | Host topology generation method and system | |
| CN105635286A (en) | Method for synchronous data synchronization of distributed system | |
| WO2022156354A1 (en) | Version configuration method, apparatus, device, system, and storage medium | |
| CN113641375A (en) | Method for automatically upgrading firmware over the air and wireless node | |
| CN113127444A (en) | Data migration method, device, server and storage medium | |
| CN114285692B (en) | Communication control system, identity determination method, distribution method and equipment | |
| CN113992739B (en) | Local area network OTA firmware upgrading device, method and system | |
| CN102629905A (en) | Slave card start control method of network equipment | |
| CN105939259B (en) | Control method, device and the router of router | |
| CN104298750B (en) | Renewal processing method and processing device for real-time system communication | |
| JPH06274432A (en) | System and method for managing distributed computer system |
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 | ||
| 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: 20120208 Termination date: 20190827 |