CN101222367A - Method and network guard system used for cluster network element updating version file - Google Patents
Method and network guard system used for cluster network element updating version file Download PDFInfo
- Publication number
- CN101222367A CN101222367A CNA2008100067097A CN200810006709A CN101222367A CN 101222367 A CN101222367 A CN 101222367A CN A2008100067097 A CNA2008100067097 A CN A2008100067097A CN 200810006709 A CN200810006709 A CN 200810006709A CN 101222367 A CN101222367 A CN 101222367A
- Authority
- CN
- China
- Prior art keywords
- network element
- version
- version file
- cluster
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method for a cluster net element updating version files in batch, including the following steps: a network management system in a cluster receives a new version file; the version file is linked to a net element with a suitable net element type in the cluster; and the version file is sent to the net element linked with the version file. The invention also provides a network management system for the cluster net element updating version files in batch. The invention achieves synchronously updating version files of all net elements in batch in the cluster, thereby improving efficiency for the cluster net element maintaining software versions.
Description
Technical field
The present invention relates to the communications field, be specifically related in network management system, the network element in the Ethernet switch group system be carried out the method and the network management system of version file batch updating.
Background technology
Along with the continuous expansion of network size, Ethernet switch relies on its good performance and cost advantage, is applied to network edge in large quantities as access device.Because the enormous amount of this access switch, management maintenance becomes very loaded down with trivial details seriatim; And, will expend a large amount of IP address resources for these access switch configuration of IP address individually respectively.
For this reason, generally adopt trunking mode that this access switch is managed.The set that cluster is made up of one group of switch provides unified management and maintenance channel, and a cluster only uses a three layers of IP address, thereby has simplified the maintenance management of equipment and saved the IP address.
Figure 1 shows that the naive model of trunking mode management access switch, the switch of cluster management is made up of four kinds of roles: command machine, member machine, candidate's machine and backup machine.
Command machine: be the switch of unique configuration public network IP address in the cluster, the management interface of whole cluster is provided.The management maintenance that member in the cluster is carried out all must be undertaken by command switch.
Member machine: the member in the cluster.
Candidate's machine: the switch that does not add any cluster management with clustering capability.
Backup machine: be used for the backup to command switch, when command switch lost efficacy, backup switch will automatically switch to command switch.
In recent years, Network is enriched constantly, and Ethernet switch is as the critical network device of bearer service, and its version updating is also more and more frequent.In engineering reality, often run into the situation that to carry out edition upgrading to hundreds and thousands of switches.These switches often are distributed in different positions, upgrade the NE type that needs during upgrading are checked every switch seriatim, its software version information, and then upgraded edition presents seriatim.Therefore, the maintenance of this device version file often needs to spend great amount of manpower and time (needing a plurality of people to spend many days time usually).
For this reason, efficiently, quickly the version file of switch in enormous quantities is carried out updating maintenance and become more and more important.
Summary of the invention
The present invention aims to provide a kind of method and network management system that is used for cluster network element batch updating version file, the problem that wastes time and energy with the maintenance that solves above-mentioned cluster network element device version file.
According to an aspect of the present invention, provide a kind of method that is used for cluster network element batch updating version file, may further comprise the steps: the network management system in the cluster receives new version file; Version file is associated with the network element that NE type is fit in the cluster; And version file is issued to its associated network element.
According to a further aspect in the invention, provide a kind of network management system that is used for cluster network element batch updating version file, having comprised: receiver module is used to receive new version file; Relating module is used for version file is associated with the network element that the cluster NE type is fit to; And issue module, be used for version file is issued to its associated network element.
Pass through technique scheme, the invention provides the method and the network management system of in the Ethernet switch group system, carrying out software release upgrade in batches, can make the webmaster personnel on patterned interface, carry out the batch of all devices in the cluster, synchronous software version update, improve cluster network element in enormous quantities greatly and carry out the efficient that software version is safeguarded.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 shows the naive model of trunking mode management access switch;
Fig. 2 shows the flow chart according to the method that is used for cluster network element batch updating version file of the embodiment of the invention;
Fig. 3 shows the flow chart according to step S10 among Fig. 2 of the embodiment of the invention;
Fig. 4 shows the flow chart according to step S20 among Fig. 2 of the embodiment of the invention;
Fig. 5 shows the flow chart according to step S30 among Fig. 2 of the embodiment of the invention;
Fig. 6 shows the block diagram according to the network management system that is used for cluster network element batch updating version file of the embodiment of the invention.
Embodiment
Below with reference to the accompanying drawings and in conjunction with the embodiments, describe the present invention in detail.
Fig. 2 shows the flow chart according to the method that is used for cluster network element batch updating version file of the embodiment of the invention, may further comprise the steps:
Step S10, the network management system in the cluster receives new version file;
Step S20 is associated with the network element that NE type is fit in the cluster with version file; And
Step S30 is issued to its associated network element with version file.
In the above-described embodiment, owing to version file is associated with the network element that will upgrade in advance, so just can select these network elements in bulk, the disposable then version file that will upgrade is transferred in these network elements.Obviously, carry out the batch of all devices in the cluster, synchronous software version update, this has improved cluster network element in enormous quantities greatly and has carried out the efficient that software version is safeguarded.
In step S10, receive the version file of uploading; And the NE type information that receives version information and its suitable network element of the version file of importing.
Specifically, the version file that receives is saved in the file server; And the establishment version repository, be a plurality of version files of preserving in the Unit Management Document server with the NE type.
In step S20, the title of version file can be arranged to reflect version information.Specifically, the version updating that creates NE list of schedules, network element version upgrades list of schedules and comprises network element ID field and version file name field; And the title of the sign of the network element of NE type coupling and version file is filled up to respectively in the network element ID field and version file name field of same clauses and subclauses that network element version upgrades list of schedules, thereby set up the corresponding relation of version file and network element.
Like this, can use graphical interfaces to present network element version to the user and upgrade list of schedules, wherein, network element version upgrades list of schedules and also comprises the current version information field, is used to be provided with the version information of the current version file of network element; And upgrade the version information field, be used to be provided with the version information of the version file of NE type coupling; And the reception user upgrades the input and or the selection of each field in the list of schedules to network element version according to current version information field and renewal version information field.
Step S30 specifically can comprise: read the clauses and subclauses that network element version upgrades list of schedules, therefrom obtain sign in the network element ID field and the title in the version file name field; From network management system sign the attribute information of corresponding network element, judge in view of the above whether network element belongs to cluster network element; If judge it is cluster network element, then from network management system, obtain the cluster relevant parameter and judge its role in cluster; If judge that network element is a member machine, then find the command machine of network element correspondence, the visit order machine is to obtain the mapped port of required each agreement of operating network element on command machine, cluster corresponding file transmission server is set on command machine, by command machine the pairing version file of title is transferred to network element from Ftp server, wherein, version file is copied to Ftp server according to network element version renewal list of schedules in advance; If judge that network element is backup machine, candidate's machine or command machine, then direct address by network element is transferred to network element with the pairing version file of title from Ftp server.
Should be noted that version updating upgrades list of schedules according to network element version and carry out, this table is in the version repository on file server, and having specified for network element needs the version file that upgrades.So need to select earlier version file and duplicate portion in the transmission working directory of Ftp server before version is transferred to network element carrying out.File server is used for depositing version repository; Ftp server is used for transmitting version file, needs to support file transfer protocol (FTP).
Wherein, the pairing version file of title is transferred to network element specifically can comprises: the login network element, wherein, if network element is a member machine, then use the address of its command machine and correspondence mappings port thereof to login; The configuration information of backup network elements; From Ftp server copy page presents to the available flash memory space of network element; And after copy finishes, the title that can load automatically when name modifications is restarted for network element next time.
Specify one embodiment of the present of invention below with reference to Fig. 3,4,5.
After the user obtains new network element version, and when prepare upgrading in the cluster in batches the version of network element, can carry out according to following steps:
Step S10, the network management system in the cluster receives new version file.
Can adopt the mode of setting up version repository to carry out, be exactly in the file server of network management service, sets up network element version library (that is, version repository), and the new version file that receives is kept in the network element version library.This can realize network element version library sharing in each client for the network management system that adopts C/S (client/service end) pattern.
For example, the party A-subscriber the A client to uploading of network management system the version file of a T NE type, the party B-subscriber also can see and use the version file of this T NE type in the B client so, has so just realized that many clients of network element version file share.
Because the software version difference of each NE type, the network element of same NE type can use identical version.Manage so the network element version storehouse is unit with the NE type, and organize according to NE type.
After network element version uploaded to version repository, can in the version repository file name, embody version number information, help being used for each version file of identification like this.
Fig. 3 shows the flow chart according to step S10 among Fig. 2 of the embodiment of the invention, may further comprise the steps:
Step S102, in the graphical interfaces that network management system provides, the user selects the version file of local network element;
Step S104 then, selects the described NE type of this version file;
Step S106, and according to information such as prompting input version number, version times;
Step S108, the part file transfer is to Ftp server; And
Step S110 makes version information on the filename band, puts into version repository respective network elements type.
Step S20 is associated with the network element that NE type is fit in the cluster with version file.
On the webmaster graphical interfaces, press version file tabulation and version information thereof in the NE type demonstration network element version storehouse.After the user selects a NE type, tabulation of the type network element and the version information thereof that adds in the network management system will be listed file names with.Be convenient to the relatively version situation of each NE type of user like this, and available version information in the network management system version repository.
The user can choose the network element tabulation that needs upgraded version in network element tabulation, and sets the relevant important parameter of version updating, can will select version file and each network element and carry out relatedly, and related information is added in the network element version renewal list of schedules.
It is the user prepares to carry out version updating to network element in the network management system planning table that so-called network element version upgrades list of schedules, each clauses and subclauses has illustrated the current version information of a network element in the table, the version information that will upgrade, and carrying out the required important parameter explanation of version updating, system can select the version updating operation of network element according to these information.Several fields that specifically can comprise, as shown in table 1.
Table 1 network element version upgrades list of schedules
| Selected network element ID field |
| The version information field of current network version |
| Prepare the version file field of renewal |
| Prepare to upgrade the version information field of version |
| Upgrade operation overtime time field |
| The network managing mode field [in the band/out-band method] |
| File transfer protocol (FTP) field [ftp/tftp/stfp etc.] |
| Selected network element flash memory space indication field |
| Whether network element restarts field automatically |
| Version updating descriptive information field |
Upgrade operation overtime time field, be used to be provided with the time-out time of released version file; When copy page presents in the available flash memory space of network element, if copy time surpasses time-out time, then report failure.
The network managing mode field, the network managing mode that is used to be provided with cluster is in-band method or out-band method; Can be dependent on network managing mode, copy page presents in the available flash memory space of network element.Usually, network managing mode is to have determined well in network construction, for example each operator may use different network managing mode in some areas, the copy of version file upgrades so, need the user to pre-set according to network managing mode, system sets according to different user and carries out version and copy more new element then.
The file transfer protocol (FTP) field is used to be provided with the used host-host protocol of copy page presents; Can utilize these host-host protocols copy page presents in the available flash memory space of network element.
Selected network element quickflashing space indication field is used to be provided with the quickflashing space that network element can be used; Before copy page presents in the available flash memory space of network element, can utilize this field to determine that the available flash memory space of network element is fit to version file earlier.
Whether network element restarts field automatically, is used for whether restarting network element after copy is finished in setting; After copy page presents in the available flash memory space of network element, can determine whether to restart network element according to the indication of this field.
Version updating descriptive information field is used to be provided with the descriptive information about the upgraded edition presents; After copy page presents in the available flash memory space of network element, can be in this field with operation log recording.
For with clustering switch, comprised polytype network element in the possible cluster, can repeat said process so, thereby very easily all network element and upgraded edition presents thereof that need upgrade version in the cluster are associated, and add in the version updating list of schedules.
Follow-uply these network elements are carried out version updating just can realize by operating this version updating list of schedules.
Fig. 4 shows the flow chart according to step S20 among Fig. 2 of the embodiment of the invention, may further comprise the steps:
Step S202 obtains the tabulation of version repository, is presented on the gui interface by NE type;
Step S204, user press the selected version file of NE type;
Step S206 lists the network element of all these NE types in the network management system and the version information of current operation thereof;
Step S208, user therefrom choose a plurality of network elements, and determine to want the upgraded edition presents;
Step S210, it is related with selected network element to select version file, and adds network element version to and upgrade in the list of schedules.
Step S30 is issued to its associated network element with version file.
As previously mentioned, by two steps of above S10, S20, ensuing network element upgraded edition presents is the operation of network element version being upgraded list of schedules in fact.
This process can trigger execution immediately by the user, also can make it regularly carrying out sometime by definition strategy.Situation for the manual triggers execution, the user can upgrade in the list of schedules at network element version according to concrete needs and choose some clauses and subclauses, clicking trigger is carried out version updating immediately then, and the network element in the selected entry will be carried out version updating according to this clauses and subclauses set information so.Certainly, the user also can be by creating regularly version updating strategy, upgrade selected some clauses and subclauses in the list of schedules at network element version, create the version updating strategy then, and set this point of tactful time of implementation, make it to carry out network element version and upgrade operation, can realize that like this network element in the less period renewal of realization version automatically of certain business, reduces because of network element version renewal interrupted service amount as far as possible at user's setting-up time point.
The concrete implementation of each clauses and subclauses (the contained list item of clauses and subclauses is please referring to table 1) corresponding net element version updating plan as shown in Figure 5 in the network element version renewal list of schedules.Fig. 5 shows the flow chart according to step S30 among Fig. 2 of the embodiment of the invention, may further comprise the steps:
Step S302, network element version upgrade the planning chart clauses and subclauses and carry out beginning;
Step S304 at first obtains this network element attribute information according to selected network element ID from network management system;
Step S306 judges in view of the above whether this network element belongs to cluster network element.
Step S316 if be non-cluster network element, then carry out the network element version renewal according to general flow and gets final product.Here will pay close attention to the version updating of cluster network element emphatically handles.
Than general network element, cluster network element need carry out some extra processing.As previously mentioned, cluster network element is divided into four kinds of roles in cluster, respectively by command machine, and member machine, candidate's machine and backup machine are formed.
Step S308 is so for cluster network element, need to obtain earlier the cluster relevant parameter from network management system;
Step S310 judges its role in cluster by relevant parameter;
Step S316, if this network element in cluster as backup machine, then just as the backup of command machine, not as the network element of cluster management; If this network element in cluster as candidate's machine, also not as the network element of cluster management, so in the cluster as the network element of backup machine and candidate's machine, can obtain information such as its IP/ usemame/password from network management system, the such unicast of general network element according to non-cluster gets final product then.
Step S312, if this network element in cluster as command machine, then as unique switch in the cluster with IP address, its processing mode is also similar with general network element, need obtain information such as its IP/ usemame/password from network management system, the such unicast of general network element according to non-cluster gets final product then;
Step S314 is security consideration, need preserve its member machine configuration and get final product before carrying out version updating.
If this network element as member machine, is then handled trouble a little in cluster, because as previously mentioned, member machine does not have the IP address in cluster, for the visit of member machine, need be undertaken by the command machine of cluster under it.
Step S318, in the realization of clustering switch, command machine has distributed mapped port for each member machine.Be that external server can visit this member machine by the IP address of command machine and the mapped port of member machine correspondence.For this reason, for the version file renewal operation of member machine, need find the corresponding cluster command machine of this network element earlier;
Step S322, visit order machine (generally can use snmp protocol) is obtained the mapped port of operation required each agreement of this network element (comprising the Telnet agreement, snmp protocol, each file transfer protocol (FTP) etc.) on its command machine then;
Step S324 also need be provided with cluster respective file transmission server address simultaneously on command machine, this server is exactly file transfer is carried out in the cluster outside by command machine and the inner member machine of cluster a server;
Step S320, after being provided with more than the process, member machine can upgrade version from external file server under the condition that does not have the IP address.
The step as shown in the empty frame of Fig. 5 of operation on network element is subsequently carried out, and each network element is unanimous on the whole.
Step S326 logined network element before this, noticed that member machine need use its command machine IP and correspondence mappings port thereof to login;
Step S328 in order to guarantee successfully to copy version to network element, need detect network element flash memory (flash) space size in advance;
Step S330, for after guaranteeing version updating, configuration information is not lost then, need preserve network element configuration before upgrading version earlier;
Step S332, then, to network element copy page presents, the NE management mode that the user has configured in this process need use network element version renewal list of schedules (in the band/outside being with), reach concrete which kind of file transfer protocol (FTP) parameters such as (being generally common file transfer protocol (FTP) such as ftp/tftp/stfp) of using;
Step S334 after network element copy version completes successfully, makes this document name into network element again and restarts the title that can load automatically next time, and this may need to revise the title of original version file.Network element is restarted next time like this, can load new version file, thereby has realized the renewal of version file.Whether network element restarts also automatically can be provided with in network element version renewal list of schedules by the user;
Step S336 disconnects network and connects when restarting network element;
Step S338, last network management system writes down the Operation Log that network element version upgrades, and execution result is returned the client demonstration.If occur mistake in the implementation, need provide detailed description, so that the user in time handles.
Network element version upgrades Operation Log, and management also has crucial effect to network element version.Upgrading each successful execution network element version upgrades in the list of schedules clauses and subclauses for network element version can be with following mode record:
" in certain time, certain user has carried out version updating to certain network element of certain type, and this network element used certain version originally, upgrades the back and uses certain version.Being illustrated as of this version updating.。。。。。" (this descriptive information upgrades in the list of schedules at network element version and is set by the user, referring to table 1).
The version updating Operation Log is for future reference at any time in system, is convenient to realize the more tracking of new situation of network element version, and this is significant for the long-time maintenance network element version.
From above execution result as can be seen, the execution that network element version upgrades each clauses and subclauses in the list of schedules is mutually independently, even also can carry out synchronously with different mapped port between each member machine by the operation of same command machine execution version updating in the same cluster.Therefore, in the batch updating network element version of reality, can use multi-threaded parallel to carry out synchronously.This version updating for network element in enormous quantities will be raised the efficiency greatly, realize that fast, convenient, traceable version file is new management more.
Fig. 6 shows the block diagram according to the network management system that is used for cluster network element batch updating version file of the embodiment of the invention, comprising:
Relating module 20 is used for version file is associated with the network element that the cluster NE type is fit to; And
This network management system can be used for realizing the method for the foregoing description, the member machine network element in can the batch updating cluster.
The above embodiment of the present invention can make the webmaster personnel on patterned interface, carry out in the cluster all network elements in batches, synchronous software version update, improve cluster network element in enormous quantities greatly and carry out the efficient that software version is safeguarded, realize that fast, convenient, traceable version file is new management more.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.Should be understood that the variation in these concrete enforcements is conspicuous for a person skilled in the art, do not break away from spiritual protection range of the present invention.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a method that is used for cluster network element batch updating version file is characterized in that, may further comprise the steps:
Network management system in the cluster receives new version file;
Described version file is associated with the network element that NE type is fit in the described cluster; And
Described version file is issued to its associated network element.
2. method according to claim 1 is characterized in that, the network management system in the cluster receives new version file and specifically comprises:
The described version file that reception is uploaded; And
Receive the NE type information of version information and its suitable network element of the described version file of importing.
3. method according to claim 2 is characterized in that, the network management system in the cluster receives new version file and specifically also comprises:
The described version file that receives is saved in the file server; And
Creating version repository, is a plurality of described version file of preserving in the described file server of unit management with described NE type.
4. method according to claim 3 is characterized in that, the network management system in the cluster receives new version file and specifically also comprises:
The title of described version file is arranged to reflect described version information.
5. method according to claim 4 is characterized in that, described version file is associated with the network element that NE type is fit in the described cluster specifically comprises:
The version updating that creates NE list of schedules, described network element version are upgraded list of schedules and are comprised network element ID field and version file name field; And
The title of the sign of the network element of NE type coupling and version file is filled up to respectively in the described network element ID field and described version file name field of same clauses and subclauses that described network element version upgrades list of schedules.
6. method according to claim 5 is characterized in that, the network management system in the cluster receives new version file and specifically also comprises:
Use graphical interfaces to present described network element version to the user and upgrade list of schedules, wherein, described network element version upgrades list of schedules and also comprises the current version information field, is used to be provided with the version information of the current version file of described network element; And upgrade the version information field, be used to be provided with the version information of the version file of described NE type coupling; And
Receive the user upgrades each field in the list of schedules to described network element version according to described current version information field and described renewal version information field input and or selection.
7. method according to claim 5 is characterized in that, described version file is issued to its associated network element specifically comprises:
Read the clauses and subclauses that described network element version upgrades list of schedules, therefrom obtain sign in the described network element ID field and the title in the described version file name field;
From sign described in the described network management system the attribute information of corresponding network element, judge in view of the above whether described network element belongs to cluster network element;
If judge it is cluster network element, then from described network management system, obtain the cluster relevant parameter and judge its role in described cluster;
If judging described network element is member machine, then find the command machine of described network element correspondence, visit described command machine to obtain the mapped port of operation required each agreement of described network element on described command machine, described cluster corresponding file transmission server is set on described command machine, by described command machine the pairing version file of described title is transferred to described network element from described Ftp server, wherein, described version file is copied to described Ftp server according to network element version renewal list of schedules in advance;
If judging described network element is backup machine, candidate's machine or command machine, then direct address by described network element is transferred to described network element with the pairing version file of described title from described Ftp server.
8. method according to claim 7 is characterized in that, the pairing version file of described title is transferred to described network element from described Ftp server specifically comprises:
Login described network element, wherein,, then use the address of its command machine and correspondence mappings port thereof to login if described network element is a member machine;
Back up the configuration information of described network element;
To the described available flash memory space of described network element, copy described version file from described Ftp server; And
After copy finishes, be the title that described network element can load when restarting next time automatically with described name modifications.
9. method according to claim 8 is characterized in that, described network element version upgrades list of schedules and also comprises:
Upgrade operation overtime time field, be used to be provided with the time-out time of the described version file of issue; When the described version file of copy in the described available flash memory space of described network element, if copy time surpasses described time-out time, then report failure;
The network managing mode field, the network managing mode that is used to be provided with described cluster is in-band method or out-band method; When the described version file of copy in the described available flash memory space of described network element, utilize described network managing mode to manage;
The file transfer protocol (FTP) field is used to be provided with the used host-host protocol of the described version file of copy; Utilize described host-host protocol in the described available flash memory space of described network element, to copy described version file;
Selected network element quickflashing space indication field is used to be provided with the quickflashing space that described network element can be used; Before the described version file of copy in the described available flash memory space of described network element, utilize this field to determine that the available flash memory space of described network element is fit to described version file earlier;
Whether network element restarts field automatically, is used for whether restarting described network element after copy is finished in setting; After the described version file of copy in the described available flash memory space of described network element, determine whether to restart described network element according to the indication of this field; And
Version updating descriptive information field is used to be provided with about upgrading the descriptive information of described version file; In the described available flash memory space of described network element the copy described version file after, with operation log recording in this field.
10. a network management system that is used for cluster network element batch updating version file is characterized in that, comprising:
Receiver module is used to receive new version file;
Relating module is used for described version file is associated with the network element that the cluster NE type is fit to; And
Issue module, be used for described version file is issued to its associated network element.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100067097A CN101222367B (en) | 2008-01-28 | 2008-01-28 | Method and network guard system used for cluster network element updating version file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100067097A CN101222367B (en) | 2008-01-28 | 2008-01-28 | Method and network guard system used for cluster network element updating version file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101222367A true CN101222367A (en) | 2008-07-16 |
| CN101222367B CN101222367B (en) | 2010-09-29 |
Family
ID=39631958
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100067097A Expired - Fee Related CN101222367B (en) | 2008-01-28 | 2008-01-28 | Method and network guard system used for cluster network element updating version file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101222367B (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101876905A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Client development system based on fore-end business platform and implementation method thereof |
| CN101938765A (en) * | 2009-06-29 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for automatically adapting network manager and network element |
| CN101938470A (en) * | 2010-08-12 | 2011-01-05 | 漳州市顺和达软件有限公司 | Upgrading system and method of client software |
| CN102387204A (en) * | 2011-10-21 | 2012-03-21 | 中国科学院计算技术研究所 | Method and system for maintaining consistency of cluster caching |
| CN102638361A (en) * | 2011-02-14 | 2012-08-15 | 中兴通讯股份有限公司 | Network element upgrading device and method |
| WO2012155642A1 (en) * | 2011-07-21 | 2012-11-22 | 中兴通讯股份有限公司 | Method and device for scheduling batch operation using restricted resources |
| CN102819531A (en) * | 2011-06-10 | 2012-12-12 | 北大方正集团有限公司 | Cloud reading service system, cloud reading service method and device |
| CN102843252A (en) * | 2011-06-23 | 2012-12-26 | 中兴通讯股份有限公司 | Method and device for updating network element through network management |
| CN103209091A (en) * | 2013-01-18 | 2013-07-17 | 中兴通讯股份有限公司 | Hot backup method and system for clustering system |
| WO2013178034A1 (en) * | 2012-05-31 | 2013-12-05 | 中国银联股份有限公司 | Cloud service deployment method and system |
| CN104737519A (en) * | 2012-10-22 | 2015-06-24 | 华为技术有限公司 | System and apparatus of generalized network controller for a software defined network (SDN) |
| CN105912732A (en) * | 2016-05-31 | 2016-08-31 | 深圳市双赢伟业科技股份有限公司 | Web page file loading method and device for exchanger |
| CN106357771A (en) * | 2016-09-20 | 2017-01-25 | 天脉聚源（北京）科技有限公司 | State synchronization method and device |
| CN106803790A (en) * | 2016-12-06 | 2017-06-06 | 浙江大华技术股份有限公司 | The upgrade control method and device of a kind of group system |
| CN107168752A (en) * | 2017-06-20 | 2017-09-15 | 武汉虹信通信技术有限责任公司 | A kind of firmware upgrade method based on Element management system |
| CN107172143A (en) * | 2017-05-12 | 2017-09-15 | 郑州云海信息技术有限公司 | Software synchronizing method and device in a kind of server cluster |
| CN107370626A (en) * | 2017-07-28 | 2017-11-21 | 郑州云海信息技术有限公司 | A kind of group system upgrade method and device |
| CN108282371A (en) * | 2018-02-09 | 2018-07-13 | 烽火通信科技股份有限公司 | A kind of net element business configuration method and system |
| WO2022007908A1 (en) * | 2020-07-09 | 2022-01-13 | 华为技术有限公司 | Method for service collaboration between network element devices, and network element device |
-
2008
- 2008-01-28 CN CN2008100067097A patent/CN101222367B/en not_active Expired - Fee Related
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101938765A (en) * | 2009-06-29 | 2011-01-05 | 中兴通讯股份有限公司 | Method and system for automatically adapting network manager and network element |
| CN101938765B (en) * | 2009-06-29 | 2015-12-16 | 中兴通讯股份有限公司 | The method and system of a kind of webmaster and network element automatic adaptation |
| CN101876905A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Client development system based on fore-end business platform and implementation method thereof |
| CN101938470A (en) * | 2010-08-12 | 2011-01-05 | 漳州市顺和达软件有限公司 | Upgrading system and method of client software |
| CN101938470B (en) * | 2010-08-12 | 2015-08-26 | 厦门市顺和达软件有限公司 | Client terminal software updating system and method |
| CN102638361A (en) * | 2011-02-14 | 2012-08-15 | 中兴通讯股份有限公司 | Network element upgrading device and method |
| CN102819531A (en) * | 2011-06-10 | 2012-12-12 | 北大方正集团有限公司 | Cloud reading service system, cloud reading service method and device |
| CN102843252A (en) * | 2011-06-23 | 2012-12-26 | 中兴通讯股份有限公司 | Method and device for updating network element through network management |
| CN102843252B (en) * | 2011-06-23 | 2018-06-19 | 南京中兴软件有限责任公司 | A kind of method and apparatus by network management upgrading network element |
| WO2012155642A1 (en) * | 2011-07-21 | 2012-11-22 | 中兴通讯股份有限公司 | Method and device for scheduling batch operation using restricted resources |
| CN102891806B (en) * | 2011-07-21 | 2017-03-01 | 天津中兴智联科技有限公司 | A kind of dispatching method to the batch operation using limited resources and device |
| CN102387204B (en) * | 2011-10-21 | 2014-12-10 | 中国科学院计算技术研究所 | Method and system for maintaining consistency of cluster caching |
| CN102387204A (en) * | 2011-10-21 | 2012-03-21 | 中国科学院计算技术研究所 | Method and system for maintaining consistency of cluster caching |
| WO2013178034A1 (en) * | 2012-05-31 | 2013-12-05 | 中国银联股份有限公司 | Cloud service deployment method and system |
| CN103457968A (en) * | 2012-05-31 | 2013-12-18 | 中国银联股份有限公司 | Cloud service deploying method and system |
| CN103457968B (en) * | 2012-05-31 | 2016-09-28 | 中国银联股份有限公司 | A kind of method and system disposing cloud service |
| CN104737519A (en) * | 2012-10-22 | 2015-06-24 | 华为技术有限公司 | System and apparatus of generalized network controller for a software defined network (SDN) |
| CN104737519B (en) * | 2012-10-22 | 2018-04-20 | 华为技术有限公司 | System and equipment for the general network controller of software defined network (SDN) |
| CN103209091A (en) * | 2013-01-18 | 2013-07-17 | 中兴通讯股份有限公司 | Hot backup method and system for clustering system |
| CN103209091B (en) * | 2013-01-18 | 2016-06-29 | 中兴通讯股份有限公司 | The heat backup method of group system and system |
| CN105912732A (en) * | 2016-05-31 | 2016-08-31 | 深圳市双赢伟业科技股份有限公司 | Web page file loading method and device for exchanger |
| CN106357771B (en) * | 2016-09-20 | 2020-03-17 | 天脉聚源（北京）科技有限公司 | State synchronization method and device |
| CN106357771A (en) * | 2016-09-20 | 2017-01-25 | 天脉聚源（北京）科技有限公司 | State synchronization method and device |
| CN106803790A (en) * | 2016-12-06 | 2017-06-06 | 浙江大华技术股份有限公司 | The upgrade control method and device of a kind of group system |
| CN106803790B (en) * | 2016-12-06 | 2019-09-17 | 浙江大华技术股份有限公司 | A kind of upgrade control method and device of group system |
| CN107172143A (en) * | 2017-05-12 | 2017-09-15 | 郑州云海信息技术有限公司 | Software synchronizing method and device in a kind of server cluster |
| CN107168752A (en) * | 2017-06-20 | 2017-09-15 | 武汉虹信通信技术有限责任公司 | A kind of firmware upgrade method based on Element management system |
| CN107370626A (en) * | 2017-07-28 | 2017-11-21 | 郑州云海信息技术有限公司 | A kind of group system upgrade method and device |
| CN108282371A (en) * | 2018-02-09 | 2018-07-13 | 烽火通信科技股份有限公司 | A kind of net element business configuration method and system |
| CN108282371B (en) * | 2018-02-09 | 2021-05-14 | 烽火通信科技股份有限公司 | Network element service configuration method and system |
| WO2022007908A1 (en) * | 2020-07-09 | 2022-01-13 | 华为技术有限公司 | Method for service collaboration between network element devices, and network element device |
| CN113992695A (en) * | 2020-07-09 | 2022-01-28 | 华为技术有限公司 | Method for service collaboration between network element devices and network element device |
| CN113992695B (en) * | 2020-07-09 | 2022-12-27 | 华为技术有限公司 | Method for service cooperation between network element devices and network element device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101222367B (en) | 2010-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101222367B (en) | Method and network guard system used for cluster network element updating version file | |
| CN105373410B (en) | Base station software difference upgrade method and its device | |
| US20120198434A1 (en) | Virtual bundling of remote device firmware upgrade | |
| CN101083557B (en) | SNMP based IP network cluster managerial approach | |
| US8271626B2 (en) | Methods for displaying physical network topology and environmental status by location, organization, or responsible party | |
| US8139509B2 (en) | Installation and management of mobile device [{S]} configuration | |
| CA2555630C (en) | Integrated deployment of software projects | |
| CN101621405B (en) | Distributed type management monitoring system, monitoring method and establishing method thereof | |
| CN100479575C (en) | Method and apparatus for realizing scheduled operation in equipment management | |
| US20070093243A1 (en) | Device management system | |
| EP2955953B1 (en) | Device management server, device management client, and method for locating a target operation object | |
| CN100546254C (en) | The method and apparatus that is used for the configuration of management cluster computer | |
| US7085822B1 (en) | Managing pervasive devices | |
| US20120047244A1 (en) | Distributed Network Management System, Network Element Management Server, and Data Configuration Management Method | |
| EA012550B1 (en) | A method in a network of the delivery of files | |
| CN101217411A (en) | A method, device and system realizing the upgrading of stacking device software | |
| CN101257406B (en) | Method and system for discovering net elements | |
| WO2010124495A1 (en) | System and method for multi-service format file processing | |
| EP1577776B1 (en) | Method and apparatus for data synchronization in a distributed data base system | |
| CN107179977B (en) | Database Full-automatic monitoring system based on mpm models | |
| CN111158711A (en) | Application program deployment method and device for multiple android system terminals | |
| CN102299814A (en) | Method and system for upgrading MIB (management information base) on SNMP (simple network management protocol) agent | |
| CN101212342A (en) | Multi-version network element network management method | |
| CN101080045B (en) | Message filtering distribution system and method | |
| CN101022633A (en) | Allocation data recovering method, system and device |
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: 20100929 Termination date: 20180128 |