CN1909479A - Method for processing collision of gating system configuration management - Google Patents
Method for processing collision of gating system configuration management Download PDFInfo
- Publication number
- CN1909479A CN1909479A CN 200610112714 CN200610112714A CN1909479A CN 1909479 A CN1909479 A CN 1909479A CN 200610112714 CN200610112714 CN 200610112714 CN 200610112714 A CN200610112714 A CN 200610112714A CN 1909479 A CN1909479 A CN 1909479A
- Authority
- CN
- China
- Prior art keywords
- network element
- server
- user interface
- system configuration
- configuration management
- 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
- User Interface Of Digital Computer (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method for managing impacts in network manage system, to be used in multi-GUI multi-SERVER network manage system, wherein it comprises: 1, using globe name to set the network unit mark, which is unique; said server based on said mark to manage themselves network unit; 2, using image user interface to access several servers, and read their network unit information to form one network unit list; 3, said client, via the image user interface, sets synchronous mark on the repeated network unit mark in the list, to generate the server list of said repeated network unit; 4, the client via image user interface processes data operation on the network unit.
Description
Technical field
The present invention relates to the method for avoiding managing conflict in the network management system structure, particularly relate to the method for avoiding managing conflict in the distributed non-tree-like management system structure of many GUI (Graphical User Interface, graphic user interface) multiserver (SERVER) in a kind of webmaster field.
Background technology
In network management system, what user (network management personnel) wished use most is the system of many many SERVER of GUI structures.In many many SERVER of GUI mechanism, a plurality of GUI of different clients can sign in to a SERVER simultaneously managed networks is carried out the webmaster operation, the operating result of each GUI can be synchronized on other the GUI, and simultaneously, each GUI can sign in to simultaneously and carries out webmaster operation among a plurality of SERVER.This mechanism is very convenient concerning the user, can adopt multiple mode to carry out network management anywhere or anytime.Many many SERVER of GUI webmaster architectural frameworks as shown in Figure 1.
In many many SERVER of GUI architectural frameworks,,, then can produce the management conflict if these a plurality of SERVER are just in time managing same network element simultaneously if when GUI signs in to a plurality of SERVER simultaneously.The reason that the management conflict produces is owing to do not have synchronization mechanism between each SERVER, when a GUI signs in to two SERVER and this two SERVER when managing same network element simultaneously, GUI inquiry and two passes is just arranged when data are set on the network element, and two SERVER and the unclear network element of being managed are same network elements, therefore can cause the data of same network element in two SERVER asynchronous, thereby produce the management conflict.Because in this managerial structure no longer is traditional tree-like managerial structure, but the rhombus managerial structure occurred, so the diamond structure that claims this kind to produce the management conflict is " a dead rhombus ", shown in Fig. 2 a, Fig. 2 b.
In the architectural framework shown in Fig. 2 a, a GUI 20 signs in to 202 two SERVER of Server1 201, Server2, and Server1 201, Server2 202 are managing a plurality of network elements separately, because the network element of Server1201, Server2 202 management does not repeat, therefore whole managerial structure is a tree structure, the management conflict can not occur.In the architectural framework shown in Fig. 2 b, a GUI 20 signs in to 202 two SERVER of Server1 201, Server2, and Server1 201, Server2 202 are just in time managing same network element 30 simultaneously, management conflict (dead rhombus) at this moment will occur.
For this reason, the present invention proposes a kind of technical scheme, and the method by NE ID (Identifier, sign) is carried out unified management solves the management collision problem in the dead rhombus.
Summary of the invention
Technical problem to be solved by this invention is to provide a kind of method for processing collision of gating system configuration management, is used for solving the problem that occurs the management conflict in many SERVER of the many GUI of prior art webmaster architectural framework.
To achieve these goals, the invention provides a kind of method for processing collision of gating system configuration management, be applicable to many many SERVER of the GUI framework formula network management systems that comprise multi-client, multiserver, it is characterized in that, comprising:
Step 4, described client are carried out data manipulation by described graphic user interface to network element and are handled.
Described method for processing collision of gating system configuration management wherein, in the described step 3, comprises that also a described client judges the step that whether has the network element of repetition network element ID in the tabulation of described net element information by described graphic user interface.
Described method for processing collision of gating system configuration management wherein, before the described step 4, comprises that also network element that a described client is administered described server by described graphic user interface initiates the step of a data operation request.
Described method for processing collision of gating system configuration management wherein, between described step 3, the step 4, comprises that also a described client judges by described graphic user interface whether network element that described server is administered is provided with the step of sync mark.
Described method for processing collision of gating system configuration management, wherein, when the network element of administering when described server was not provided with sync mark, then described graphic user interface directly carries out data manipulation to this network element by the server that this network element belonged to be handled.
Described method for processing collision of gating system configuration management, wherein, when the network element of administering when described server is provided with sync mark, then described client is put into a first in first out waiting list by described graphic user interface with described data operation request, lock this network element line data operational processes of going forward side by side, finish in the described server list in other servers the data synchronization of this network element again and handle.
Described method for processing collision of gating system configuration management, wherein, also comprise one when described data operation request after described first in first out waiting list comes out, lock the step of this network element.
Described method for processing collision of gating system configuration management wherein, comprises that also one removes the step of this network element locking after described Synchronous Processing is finished.
Beneficial technical effects of the present invention is:
Compared with prior art, the inventive method is by carrying out unified management and name to guarantee the uniqueness of NE ID to the whole network network element, thereby GUI can discern accurately whether the network element of managing among the different SERVER is same network element, data sync by SERVER, solved the management collision problem under the rhombus managerial structure effectively, for the webmaster architectural framework of the many SERVER of many GUI provides sound assurance.
Describe the present invention below in conjunction with the drawings and specific embodiments, but not as a limitation of the invention.
Description of drawings
Fig. 1 is the webmaster architectural framework of the many SERVER of many GUI in the prior art;
Fig. 2 a, 2b are dead rhombus and management conflict schematic diagram in the prior art;
Fig. 3 is a control strategy schematic flow sheet of the present invention;
Fig. 4 is specific embodiments of the invention.
Embodiment
See also shown in Figure 3ly,, Figure 4 shows that specific embodiments of the invention for control strategy schematic flow sheet of the present invention.
Many many SERVER of GUI webmaster architectural framework management conflict processing methods have adopted the control strategy of NE ID global naming among Fig. 3, at the state described in Fig. 4, GUI is carried out the example one of data manipulation to network element 1 by SERVER-1, comprise a corresponding flow process among Fig. 3, concrete steps are as follows:
Step 301 at first uses global naming that all NE ID of the whole network are configured, and guarantees the uniqueness of NE ID, that is, NE ID does not have repetition; Among Fig. 4, the ID of the whole network network element 1, network element 2, network element 3,4 four network elements of network element is configured, is respectively 001,002,003,004;
Step 302, many SERVER start, the SERVER network element that management is administered separately according to NE ID, be specially: when SERVER-1, SERVER-2 and three SERVER startups of SERVER-3, SERVER-1 managed network element 1 and network element 2, the tabulation of the NE ID of its management for 001,002}; SERVER-2 managed network element 2 and network element 3, the tabulation of the NE ID of its management for 002,003}; SERVER-3 managed network element 3 and network element 4, the tabulation of the NE ID of its management for 003,004}.
Step 303 when GUI signs in to SERVER-1, SERVER-2 and SERVER-3 when going up simultaneously, reads net element information, generates original net element information tabulation, the resulting NE ID tabulation of GUI for 001,002,002,003,003,004};
Step 304, GUI judges whether ID has repetition in the resulting network element tabulation, repeats if NE ID occurs, then changes step 305 over to, does not repeat if NE ID occurs, then need not do sync mark to network element, directly execution in step 306;
Step 305, GUI judges the NE ID that repetition is arranged in the network element tabulation: 002 and ID:003, that is, this ID corresponding net element is managed by a plurality of SERVER; The NE ID corresponding net element that repeats is done to go up sync mark, and write down the SERVER tabulation of managing this network element simultaneously, to carry out data sync; Be specially: to NE ID is that 002 network element 2 does to go up sync marks, and the record SERVER tabulation of managed network element 2 simultaneously: { SERVER-1, SERVER-2}; To NE ID is that 003 network element 3 does to go up sync marks, and the record SERVER tabulation of managed network element 3 simultaneously: { SERVER-2, SERVER-3};
Step 306 reads net element information and finishes;
Step 307 when GUI sends data operation request by SERVER-1 to network element 1, comprises data manipulations such as inquiry is provided with;
Step 308, GUI judges whether operated network element 1 has sync mark;
Step 310, when network element 1 no sync mark, GUI carries out data manipulation by SERVER-1 to network element 1;
Step 311, GUI finishes a data manipulation of network element 1 by SERVER-1.
At the state described in Fig. 4, to GUI by SERVER-1 to the example two that network element 2 carries out data manipulation, comprise a corresponding flow process among Fig. 3, concrete steps are as follows:
Step 301 at first uses global naming that all NE ID of the whole network are configured, and guarantees the uniqueness of NE ID, that is, NE ID does not have repetition; Among Fig. 4, the ID of the network element 1 of the whole network, network element 2, network element 3,4 four network elements of network element is configured, is respectively 001,002,003,004;
Step 302, many SERVER start, the SERVER network element that management is administered separately according to NE ID, be specially: when SERVER-1, SERVER-2 and three SERVER startups of SERVER-3, SERVER-1 managed network element 1 and network element 2, the tabulation of the NE ID of its management for 001,002}; SERVER-2 managed network element 2 and network element 3, the tabulation of the NE ID of its management for 002,003}; SERVER-3 managed network element 3 and network element 4, the tabulation of the NE ID of its management for 003,004}.
Step 303 when GUI signs in to SERVER-1, SERVER-2 and SERVER-3 when going up simultaneously, reads net element information, generates original net element information tabulation, the NE ID tabulation that GUI obtains for 001,002,002,003,003,004};
Step 304, GUI judges whether ID has repetition in the resulting network element tabulation, repeats if NE ID occurs, then changes step 305 over to, does not repeat if NE ID occurs, then need not do sync mark to network element, directly execution in step 306;
Step 305, GUI judges the NE ID that repetition is arranged in the network element tabulation: 002 and ID:003, promptly this ID corresponding net element is managed by a plurality of SERVER; The NE ID corresponding net element that repeats is done to go up sync mark, and the SERVER tabulation of this network element managed simultaneously in record, to carry out data sync, be specially: to NE ID is that 002 network element 2 does to go up sync marks, and the record SERVER tabulation of managed network element 2 simultaneously: { SERVER-1, SERVER-2}; To NE ID is that 003 network element 3 does to go up sync marks, and the record SERVER tabulation of managed network element 3 simultaneously: { SERVER-2, SERVER-3};
Step 306 reads net element information and finishes;
Step 307, GUI sends data operation request by SERVER-1 to network element 2, comprises data manipulations such as inquiry is provided with;
Step 308, GUI judges whether operated network element 2 has sync mark;
Step 309, when network element 2 had sync mark, GUI put into first in first out (First In First Out, waiting list FIFO) with this data operation request; After this data operation request was come out from the FIFO waiting list, locking network element 2 was to prevent that other SERVER operates network element 2 in data manipulation and the synchronizing process; By SERVER-1 network element 2 is carried out data manipulation by GUI; After data manipulation is finished, the relevant SERVER of notice carries out synchronously the data of network element 2, to keep the consistency of data, SERVER tabulation relevant with network element 2 among Fig. 4 is { SERVER-1, SERVER-2} carries out Synchronous Processing with the data of network element 2 among the data of network element 2 among the SERVER-2 relevant with SERVER-1 in the SERVER tabulation and the SERVER-1; Synchronously, network element 2 is unlocked;
In this step, the reason of data operation request being put into fifo fifo is: a plurality of SERVER might be arranged simultaneously to a network element transmit operation request, the strategy of service is earlier adopted first in this formation.
Step 311, GUI finishes the data manipulation that network element 2 carries out by SERVER-1.
By above step, just can in many many SERVER of GUI webmaster architectural frameworks, occur under the situation of rhombus managerial structure, solve the problem of management conflict.
The inventive method has adopted the control strategy of NE ID global naming, all NE ID of the whole network are managed and distributes by unified overall NE ID storehouse, guarantees the uniqueness of all NE ID of the whole network.When GUI signs in to a plurality of SERVER, if two situations that (or a plurality of) SERVER manages same network element, then GUI can judge two network elements among the SERVER according to NE ID and be actually same network element, thereby the data among these two SERVER are carried out synchronously, so just can guarantee the data consistency when GUI carries out data query and is provided with from SERVER, avoid the management conflict.
Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art work as can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection range of the appended claim of the present invention.
Claims (8)
1, a kind of method for processing collision of gating system configuration management is applicable to many many SERVER of the GUI framework formula network management systems that comprise multi-client, multiserver, it is characterized in that, comprising:
Step 1 is utilized global naming configuration the whole network network element ID, and described network element ID is unique, the network element that described server is administered separately according to described network element ID management;
Step 2, reads the net element information of network element that described a plurality of server is administered and generates net element information tabulation to a plurality of servers by the graphic user interface login;
Step 3, described client is provided with sync mark by described graphic user interface to the network element that has the repetition network element ID in the described net element information tabulation, and generates the server list of this network element institute attribution server;
Step 4, described client are carried out data manipulation by described graphic user interface to network element and are handled.
2, method for processing collision of gating system configuration management according to claim 1, it is characterized in that, in the described step 3, comprise that also a described client judges the step that whether has the network element of repetition network element ID in the tabulation of described net element information by described graphic user interface.
3, method for processing collision of gating system configuration management according to claim 1 and 2, it is characterized in that, before the described step 4, comprise that also network element that a described client is administered described server by described graphic user interface initiates the step of a data operation request.
4, method for processing collision of gating system configuration management according to claim 3, it is characterized in that, between described step 3, the step 4, comprise that also a described client judges by described graphic user interface whether network element that described server is administered is provided with the step of sync mark.
5, method for processing collision of gating system configuration management according to claim 4, it is characterized in that, when the network element of administering when described server was not provided with sync mark, then described graphic user interface directly carries out data manipulation to this network element by the server that this network element belonged to be handled.
6, according to claim 4 or 5 described method for processing collision of gating system configuration management, it is characterized in that, when the network element of administering when described server is provided with sync mark, then described client is put into a first in first out waiting list by described graphic user interface with described data operation request, lock this network element line data operational processes of going forward side by side, finish in the described server list in other servers the data synchronization of this network element again and handle.
7, method for processing collision of gating system configuration management according to claim 6 is characterized in that, also comprise one when described data operation request after described first in first out waiting list comes out, lock the step of this network element.
8, method for processing collision of gating system configuration management according to claim 7 is characterized in that, comprises that also one removes the step of this network element locking after described Synchronous Processing is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101127147A CN100440808C (en) | 2006-08-30 | 2006-08-30 | Method for processing collision of gating system configuration management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101127147A CN100440808C (en) | 2006-08-30 | 2006-08-30 | Method for processing collision of gating system configuration management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1909479A true CN1909479A (en) | 2007-02-07 |
| CN100440808C CN100440808C (en) | 2008-12-03 |
Family
ID=37700474
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101127147A Expired - Fee Related CN100440808C (en) | 2006-08-30 | 2006-08-30 | Method for processing collision of gating system configuration management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100440808C (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009079855A1 (en) * | 2007-12-24 | 2009-07-02 | Zte Corporation | An implementing method of multilevel network management integration based on gct |
| CN103338121A (en) * | 2013-06-13 | 2013-10-02 | 北京奇虎科技有限公司 | System management server and method, and system for server system management |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7397809B2 (en) * | 2002-12-13 | 2008-07-08 | Conexant Systems, Inc. | Scheduling methods for combined unicast and multicast queuing |
| CN1286331C (en) * | 2003-11-25 | 2006-11-22 | 大唐移动通信设备有限公司 | Network wireless environment based mobile communication positioning method |
| CN1287558C (en) * | 2003-12-29 | 2006-11-29 | 中兴通讯股份有限公司 | Recovering method for optical transmission circular network wrong connection business |
| CN100531445C (en) * | 2004-10-19 | 2009-08-19 | 北京邮电大学 | Controlling method for realizing automatic discovery of resource information based on automatic switched optical network |
| CN1322427C (en) * | 2005-02-25 | 2007-06-20 | 清华大学 | Universal method for dynamical management of storage resource under Windows platform |
-
2006
- 2006-08-30 CN CNB2006101127147A patent/CN100440808C/en not_active Expired - Fee Related
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009079855A1 (en) * | 2007-12-24 | 2009-07-02 | Zte Corporation | An implementing method of multilevel network management integration based on gct |
| CN101803283B (en) * | 2007-12-24 | 2012-03-28 | 中兴通讯股份有限公司 | An implementing method of multilevel network management integration based on GCT |
| CN103338121A (en) * | 2013-06-13 | 2013-10-02 | 北京奇虎科技有限公司 | System management server and method, and system for server system management |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100440808C (en) | 2008-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1251446C (en) | Method of defending network transmission control protocol sync message from overflowing attack | |
| CN1320483C (en) | System and method for implementing journaling in a multi-node environment | |
| CN1859407A (en) | Method for securing special line user access network | |
| EP3594808B1 (en) | Virtual machine migration method, switch, and virtual machine system | |
| Patil et al. | GIGA+ scalable directories for shared file systems | |
| CN106354565B (en) | A kind of distributed lock client and control method | |
| CN101056188A (en) | Method and system for pushing the history records to the specified members in the discussion group | |
| CN1655522A (en) | Pre-configuration realization method for cradle type network apparatus service board | |
| CN101030843A (en) | Method for converting multi-medium conference controlling mode | |
| CN1925416A (en) | Method and device for batch addition of users to group | |
| CN1870551A (en) | Distribution type group communication management system and method for setting group | |
| CN1885858A (en) | Method for carrying out cluster management on network equipment based on SNMP protocol | |
| CN1804831A (en) | Network cache management system and method | |
| CN107688611A (en) | A kind of Redis key assignments management system and method based on saltstack | |
| CN1852160A (en) | Method for realizing data slow synchronization and system thereof | |
| CN1302135A (en) | Capture producing method for controlling simple network management agreement | |
| CN1917512A (en) | Method for establishing direct connected peer-to-peer channel | |
| CN1960304A (en) | Method for realizing cross-domain access by using local domain proxy server | |
| CN1735190A (en) | Centralized management cascade conference method on video operation platform | |
| CN1874357A (en) | Method for generating id symbol | |
| CN1909479A (en) | Method for processing collision of gating system configuration management | |
| CN1917442A (en) | Concentrating type method for managing networked devices based on embedded type TELNET server | |
| CN1878147A (en) | Method for balancing load between multi network cards of network file system server | |
| CN1831782A (en) | Allopatric data image method of network information system | |
| CN101079823A (en) | A method and system for originating and creating virtual discussion group |
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 |
Granted publication date: 20081203 Termination date: 20170830 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |