CN100428687C - Method for managing management information base in network management system - Google Patents
Method for managing management information base in network management system Download PDFInfo
- Publication number
- CN100428687C CN100428687C CNB2004800421024A CN200480042102A CN100428687C CN 100428687 C CN100428687 C CN 100428687C CN B2004800421024 A CNB2004800421024 A CN B2004800421024A CN 200480042102 A CN200480042102 A CN 200480042102A CN 100428687 C CN100428687 C CN 100428687C
- Authority
- CN
- China
- Prior art keywords
- mib
- version
- network element
- protocol adapter
- snmp protocol
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Abstract
The invention discloses a method for managing management information base (MIB) in network managing system (NMS), the NMS comprises SNMP protocol adaptive layer as well as managed network, the SNMP protocol adaptive layer includes MIB coordinated management module, the method comprises following steps: defining a MIB version for all MIB information which is defined for managing a network cell of one version from a kind of network cell in managed network; the SNMP protocol adaptive layer will create a MIB version space for each MIB version within the NMS management range, add all MIB information included in each MIB version into the MIB version space created for the MIB version, put all conflicting SNMP objects in MIB version space respectively; the MIB coordinated management module will instantiate and de<->instantiate corresponding MIB version space according to management requirement. In term of scheme of invention, the conflict between new object and old object will be overcame, and because the old version network cell be managed no more, MIB and NMS's maintenance is convenient.
Description
Technical field
The present invention relates to a kind of method that solves SNMP MIB conflict in telecommunication network management system, the particularly a kind of MIB of use version space is supported many versions SNMP MIB and is used MIB coordinated management module according to the regulatory requirement instantiation and the method for removing instantiation MIB version space.
Background technology
Simple Network Management Protocol (SNMP) has become a kind of widely used management agreement in telecommunication network management field.In order to support SNMP, we at first need according to regulatory requirement definition management information bank (MIB), and the mib information with definition is loaded in the network management system (nms) then, just NMS can manage the mutual of information with network element (NE) like this.
Current all snmp stacks and SNMP instrument (such as MG-SOFT MIBBrowser) only allow a MIB space at synchronization, promptly all mib informations all can only be loaded into same aspect, therefore to definitely avoid the MIB conflict, make mistakes otherwise when loading MIB, can point out, thereby can't carry out follow-up processing.
The MIB conflict just is meant that same object has different definition in SNMP MIB definition, thereby mistake occurs when mib information loads.Such as in order to manage the media gateway (MG) in the soft switchcall server, need in its MIB, define object A, and object A is defined as Integer32 in the pairing MIB of MG V1.0, in order to satisfy the demand on the management function, object A was defined as OCTET STRING in the pairing MIB definition of MG V2.0 afterwards.At this moment, if NMS need manage MG V1.0 and MGV2.0 simultaneously, NMS will occur conflict because of the different definition of object A when loading the mib information of MG V1.0 and V2.0.
But from the angle of network management, NMS must can manage dissimilar network elements.For the network element of same kind, because functional requirement and software, hard-wired difference also may cause different versions, this just requires NMS must can adapt to this demand, manages the different editions of same kind network element.
With Fig. 1 is example, has 5 network elements in the flexible exchanging network of soft switch NMS management, and wherein the NE type of network element MG A and MG C is media gateway (MG), and network element version is V2.0; The NE type of network element MG B is MG, and network element version is V1.0; The NE type of network element SG A is SGW (SG), and network element version is V2.0; The NE type of network element SG B is SG, and network element version is V1.0.
For NE type is identical but the network element that version is different, because they provide different business function, meet the different needs, such as MG A among Fig. 1 and MG B, therefore from the angle of network management, NMS also can be different to their management, thus the MIB definition meeting that causes them difference to some extent.When NMS managed them simultaneously, the MIB conflict was also just unavoidable sometimes like this.MIB conflict between the same different network elements type also happens occasionally.
The mode that solves the MIB conflict at present is exactly when definition SNMP MIB the SNMP object definition that conflicts to be become a new object.If but we adopt this mode, whole M IB definition will become very huge and complicated.Simultaneously, because NMS must support the new object of introducing, so the realization of NMS also can become increasingly complex, and owing to have certain similitude between new definition of object and the old object, thereby the also easy generation that leads to errors because of obscuring.In case being NMS, another problem of this solution no longer the network element of early version is managed, many useless information will appear in whole M IB definition, many useless codes also can occur in the realization of same NMS, thereby bring bigger difficulty for the maintenance of MIB and NMS.
Summary of the invention
In order to solve the MIB conflict, we must provide a kind of solution of supporting many versions SNMP MIB.The present invention solves this problem by introducing MIB version space and MIB coordinated management module just.
According to basic design of the present invention, be each version establishment MIB version space separately of every kind of NE type, and all mib informations relevant with this version of this NE type are loaded in its corresponding MIB version space, thereby eliminate the MIB conflict.
According to an aspect of the present invention, a kind of method that in network management system NMS management information bank MIB is managed is provided, described network management system comprises snmp protocol adapter and managed network, described snmp protocol adapter comprises MIB coordinated management module, and described method comprises step:
All mib informations that will define for the network element of a version managing a kind of NE type in the described managed network are defined as a MIB version;
Described snmp protocol adapter will be created a MIB version space for each the MIB version in the described NMS range of management, all mib informations that each MIB version is comprised are loaded in the MIB version space of being created for described MIB version, and the SNMP object of all conflicts is placed in separately the MIB version space;
Described MIB coordinated management module is carried out instantiation and is gone instantiation corresponding M IB version space according to regulatory requirement.
Preferably, described MIB coordinated management module is only MIB version space of instantiation of each MIB version.
According to another aspect of the present invention, a kind of method of handling in network management system NMS from the management request of the TMN of telecommunication management network functional module is provided, described network management system comprises TMN functional module, managed object warehouse MOR, Simple Network Management Protocol snmp protocol adapter, described snmp protocol adapter comprises MIB coordinated management module, and described method comprises step:
(1) described snmp protocol adapter receives the management request from described TMN functional module;
(2) described snmp protocol adapter is inquired about NE type, network element version and the IP address of described network element according to the element name/network element ID that comprises in the management request from described MOR;
(3) described snmp protocol adapter and described MIB coordinated management module is mutual, obtains the pairing MIB version space of described NE type and network element version, and described like this snmp protocol adapter just can be handled this management request by described MIB version space;
(4) described snmp protocol adapter carries out alternately with the MIB version space that inquires in the step (3) according to the information that comprises the management request that comes from described TMN functional module, creates the required SNMP definition of object of SNMP request PDU thereby obtain;
(5) described snmp protocol adapter is created the SNMP request PDU according to the information that is comprised in SNMP object definition of obtaining and the management request from the MIB version space;
(6) the SNMP request PDU that will newly create of described snmp protocol adapter sends to corresponding network element;
(7) the SNMP response PDU that returns from network element is waited for and received to described snmp protocol adapter;
(8) described snmp protocol adapter is resolved SNMP response PDU, and the result is returned to described TMN functional module.
According to a further aspect of the invention, a kind of alarm of sending from network element and method of event notice handled in network management system NMS is provided, described network management system comprises the TMN of telecommunication management network functional module, managed object warehouse MOR, Simple Network Management Protocol snmp protocol adapter, described snmp protocol adapter comprises MIB coordinated management module, and described method comprises step:
(1) described snmp protocol adapter receives alarm or the event notice that sends from network element;
(2) described snmp protocol adapter is inquired about NE type, the network element version of described network element according to the element name/network element ID that obtains from described MOR from alarm or event notice;
(3) described snmp protocol adapter is mutual according to the NE type that obtains in the step (2) and network element version and described MIB coordinated management module, obtains the pairing MIB version space of described NE type and network element version;
(4) the MIB version space that obtains in described snmp protocol adapter and the step (3) is mutual, resolves the alarm or the event notice that receive from network element, described alarm or event notice is translated into the expression mode of alarm among the NMS or incident Common Information Model;
(5) alarm after described snmp protocol adapter will be translated or event information send to the fault management module in the described TMN functional module.
According to technical scheme of the present invention, overcome conflicting between new definition of object and the old object, and owing to no longer the network element of early version is managed, thereby bring convenience for the maintenance of MIB and NMS.
Description of drawings
Fig. 1 shows the flexible exchanging network of being made up of many NE types, many network element versions;
Fig. 2 shows the framework that solves the MIB conflict and support the NMS of many versions SNMP MIB;
Fig. 3 shows the flow process of processing from the next management request of TMN functional module;
Fig. 4 shows the alarm that processing comes from network element and the flow process of event notice;
Fig. 5 shows the tissue of mib file;
Fig. 6 shows the handling process of instantiation MIB version space when creating new network element;
The handling process that Fig. 7 removes instantiation MIB version space when showing the deletion network element.
Embodiment
In the present invention, we provide a kind of MIB of solution conflict and have supported the NMS solution of many versions SNMP MIB.
For the convenience of describing, we introduce the notion of MIB version, all mib informations that will define for the network element of a version managing a kind of NE type are called a MIB version, that is to say the version of a MIB version corresponding to a kind of NE type, promptly the MIB version is only relevant with NE type and network element version.In the present invention, we are each MIB version instantiation and MIB version space of instantiation only.
Fig. 2 has listed the framework that solves the MIB conflict and support the NMS of many versions SNMP MIB.
Managed network is meant the network of being managed by NMS.Have 4 network elements in the managed network shown in Figure 2, they are respectively NE A, NE B, NE C and NE D.
ITU-T has defined 5 management function territories altogether in the Governance framework of telecommunications management network (tmn), be referred to as the TMN functional module, they are respectively fault management (FM), configuration management (CM), accounting management (AM), performance management (PM) and safety management (SM), they are also referred to as FCAPS usually.Detail with reference ITU-T M.3010.
The purpose that NMS introduces managed object warehouse (MOR) is in order to safeguard the details of all managed objects in the NMS range of management, to comprise the attribute of managed object, the operation and the corresponding descriptor of support.MOR also safeguards the inclusion relation between the managed object simultaneously.MOR uses data base management system to carry out the permanent storage of managed object.
MOR provides sequence of operations to supply the TMN functional module to refresh the information of managed object, also allows TMN functional module and snmp protocol adapter to inquire about their needed information simultaneously.
The snmp protocol adapter serves as the role of network adaptation layer in NMS, its major function is to carry out information matches between the general Management Information Model of NMS inside and SNMP MIB, the SNMP request that network element can understand is translated in the request of TMN functional module, simultaneously the alarm of reported by network elements or event notice are translated into the expression mode of alarm among the NMS or incident Common Information Model.
In same managed network, may there be the network element of much being managed, the NE type of these network elements may be identical with network element version, also may be different, simultaneously because the difference of network element on management function of different network elements type and network element version, their MIB definition also can be different, therefore has a plurality of MIB versions in the whole network.In order to manage these network elements, the snmp protocol adapter must can be supported many MIB version, and realizes all MIB relevant with these network elements definition.In order to reach this target, the snmp protocol adapter will be created a MIB version space for each the MIB version in this NMS range of management, and all mib informations that each MIB version is comprised are loaded in the MIB version space of being created for this MIB version, the SNMP object of all conflicts will be placed in separately the MIB version space like this, thereby fundamentally solve the problem of MIB conflict.
The function of MIB coordinated management module is exactly all MIB version spaces of management, comprises according to the regulatory requirement instantiation and removes instantiation corresponding M IB version space.
Basic design of the present invention is, is each MIB version establishment MIB version space separately, and all mib informations that each MIB version is comprised are loaded in the pairing MIB version space of this MIB version.
With Fig. 1 is example, and snmp protocol adapter/MIB coordinated management module needs to create 4 MIB version spaces altogether, because have 4 MIB versions in the whole network:
(1) network element MG A and MG C are MG V2.0, and promptly their NE type is identical with network element version, so they share same MIB version space, this MIB version space called after mibContextMG_V2.0.The naming rule of MIB version space sees also the description of back;
(2) snmp protocol adapter/MIB coordinated management module will be created a MIB version space, this MIB version space called after mibContextMG_V1.0 separately for network element MG B;
(3) snmp protocol adapter/MIB coordinated management module will be created a MIB version space, this MIB version space called after mibContextSG_V2.0 separately for network element SG A;
(4) snmp protocol adapter/MIB coordinated management module will be created a MIB version space, this MIB version space called after mibContextSG_V1.0 separately for network element SG B.
From above-mentioned example as can be known, have the network element of identical NE type and network element version for all, snmp protocol adapter/MIB coordinated management module is only created a MIB version space, because they have identical MIB version.
When NMS started, the snmp protocol adapter need be initialised, and it just can carry out coupling and the translation between inner Common Information Model of NMS and the SNMP MIB like this.The initialized flow process of snmp protocol adapter is as follows:
(1) creates MIB coordinated management module;
(2) from MOR, obtain the NE type and the network element version of all network elements of this NMS management, and remove the information that wherein repeats.With Fig. 1 is example, and the NE type and the network element version that obtain from MOR should comprise: MG/V2.0, and MG/V1.0, SG/V2.0 and SG/V1.0 promptly always have 4 MIB versions;
(3), be each MIB version instantiation MIB version space separately according to the NE type and the network element version that obtain from MOR in the step (2).With Fig. 1 is example, needs 4 MIB version spaces of instantiation altogether, and they are respectively mibContextMG_V2.0, mibContextMG_V1.0, mibContextSG_V2.0 and mibContextSG_V1.0.The step of a MIB version space of instantiation is as follows:
Create a new MIB version space according to given NE type and network element version;
All mib informations with this MIB version from file system are loaded in the MIB version space of new establishment.The tissue of mib file sees also the description of back.
Start and the snmp protocol adapter is initialised after the success at NMS, the snmp protocol adapter just can be handled the management request from the TMN functional module.The snmp protocol adapter is handled from the general flow of the management request of TMN functional module as shown in Figure 3.
(1) the snmp protocol adapter receives from the next management request of TMN functional module;
(2) the snmp protocol adapter is inquired about NE type, network element version and the IP address of this network element according to the element name/network element ID that comprises in the management request from MOR;
(3) snmp protocol adapter and MIB coordinated management module is mutual, obtains the pairing MIB version space of this NE type and network element version, and the snmp protocol adapter just can be handled this management request by this MIB version space like this;
(4) the snmp protocol adapter carries out alternately with the MIB version space that inquires among the step C according to the information that comprises the management request that comes from the TMN functional module, creates the required SNMP definition of object of SNMP request PDU thereby obtain;
(5) the snmp protocol adapter is created the SNMP request PDU according to the information that is comprised in SNMP object definition of obtaining and the management request from the MIB version space;
(6) the SNMP request PDU that will newly create of snmp protocol adapter sends to corresponding network element;
(7) the SNMP response PDU that returns from network element is waited for and received to the snmp protocol adapter;
(8) the snmp protocol adapter is resolved SNMP response PDU, and this result is returned to the TMN functional module.
It is very useful that controlled state is carried out network operation for the user, can allow or forbid that certain resource of being managed provides service by controlled state is set such as the user.Therefore we can illustrate the flow process of snmp protocol adapter processing from the next management request of TMN functional module with this.In this example, the user wishes to forbid that network element MG A provides service, and the controlled state that is about to network element MG A is set to " Locked ", and its flow process is specific as follows:
(1) CM (configuration management) module in the TMN functional module receives the order that the user forbids network element MG A from NMS graphic user interface (GUI);
(2) the CM module sends to the snmp protocol adapter with this request;
(3) snmp protocol adapter and MOR are mutual, obtain NE type and network element version and the IP address of network element MG A, thereby the snmp protocol adapter knows that the NE type of MG A is MG, and network element version is V2.0, and the IP address is 172.19.64.10;
(4) the snmp protocol adapter is mutual according to information that obtains in the step (3) and MIB coordinated management module, learns that the MIB version space corresponding with MG A is mibContextMG_V2.0;
(5) snmp protocol adapter and mibContextMG_V2.0 are mutual, obtain the SNMP object definition of network element MG A controlled state;
(6) the snmp protocol adapter is created the SNMP request PDU according to the value (this value should be Locked) of the MG A controlled state that comprises in MG A controlled state definition that obtains and the management request from step (5);
(7) the snmp protocol adapter sends to network element MG A with this SNMP request PDU;
(8) the snmp protocol adapter is waited for and is received the result who returns from network element MG A, and this result is returned to the CM module.
Start and the snmp protocol adapter is initialised after the success at NMS, the snmp protocol adapter can also be handled alarm and the event notice that sends from network element simultaneously.Managed element is the change that certain fault has taken place in the network element or gone out present condition in order in time to allow NMS know to the purpose that NMS sends alarm and event notice.The flow process that the snmp protocol adapter is handled the alarm of sending from network element and event notice is as shown in Figure 4:
(1) the snmp protocol adapter receives alarm or the event notice that sends from network element;
(2) the snmp protocol adapter is inquired about NE type, the network element version of this network element according to the element name/network element ID that obtains from MOR from alarm or event notice;
(3) the snmp protocol adapter is mutual according to the NE type that obtains in the step (2) and network element version and MIB coordinated management module, obtains the pairing MIB version space of this NE type and network element version;
(4) the MIB version space that obtains in snmp protocol adapter and the step (3) is mutual, resolves the alarm or the event notice that receive from network element, this alarm or event notice is translated into the expression mode of alarm among the NMS or incident Common Information Model;
(5) alarm after the snmp protocol adapter will be translated or event information send to the FM module in the TMN functional module.
Because the type of network element has nothing in common with each other in the managed network, and the version of network element also may vary, thereby has numerous MIB versions, thereby the MIB version space of snmp protocol adapter/MIB coordinated management module instanceization also can be a lot.In order effectively these MIB version spaces to be managed, the present invention need stipulate the naming rule of MIB version space.The naming rule of MIB version space is as follows:
The title of MIB version space=" mibContext "+NE type+" _ "+network element version
In this naming rule, NE type and network element version are used as the keyword of MIB version space name.According to this naming rule, the pairing MIB version space of MG A just should be named as " mibContextMG_V2.0 " among Fig. 1.
When MIB version space of MIB coordinated management module instanceization, it need be loaded into from all mib informations that file system is comprised this MIB version the MIB version space of wanting new instantiation.Therefore the present invention also stipulates the organizational form of mib file simultaneously, and MIB coordinated management module just knows how to read required mib information from file system when instantiation MIB version space like this.Organizing as shown in Figure 5 of mib file.
Mib file is organized by NE type earlier among the present invention, and then presses the network element version tissue, and promptly NE type is that ground floor bibliographic structure, network element version are second layer bibliographic structure.
The snmp protocol adapter need use the MIB version space to finish the mutual of management information between NMS and the managed element, like this MIB coordinated management module just need in real time, all MIB version spaces in the Dynamic Maintenance managed network, if therefore the user is by NMS GUI (graphic user interface) dynamic creation or deletion network element, MIB version space that the instantiation in time of MIB coordinated management module is new or the MIB version space that goes instantiation not re-use.
The handling process of the new MIB version space of instantiation as shown in Figure 6 when creating new network element.
(1) create a new network element when the user passes through NMS GUI, new MIB version space of the CM in the TMN functional module (configuration management) module request snmp protocol adapter instantiation has comprised the NE type and the network element version that newly create NE in this request;
(2) the snmp protocol adapter sends to MIB coordinated management module with this request;
(3) whether MIB coordinates and manages the module check MIB version space corresponding with this NE type and network element version by instantiation;
(4) if MIB coordinated management module finds that this MIB version space by instantiation, then directly jumps to step (5); Otherwise MIB coordinated management module will be created a new MIB version space according to given NE type and network element version, and load all mib informations that this MIB version space comprised to this MIB version space from file system.If MIB coordinated management module can not load mib information, do not exist such as loading the required file of MIB, then this solicit operation failure;
(5) MIB coordinated management module returns to the snmp protocol adapter with the result of instantiation;
(6) the snmp protocol adapter returns to the CM module with the result of instantiation.
The handling process of removing instantiation MIB version space when the user deletes network element as shown in Figure 7.
(1) delete a network element when the user passes through NMS GUI, the CM module request snmp protocol adapter in the TMN functional module removes the pairing MIB version space of this network element of instantiation, has comprised the NE type and the network element version of deleted network element in this request;
(2) snmp protocol adapter and MOR carry out alternately, obtain the NE type and the network element version of all network elements of current NMS management;
(3) whether also have the network element identical with network element version among this NMS of snmp protocol adapter check, promptly check whether also have network element need use this will be removed the MIB version space of instantiation with the NE type of deleted network element.If also have network element need use this MIB version space, then this MIB version space can not be gone instantiation;
(4) if the snmp protocol adapter finds do not have network element need re-use the MIB version space that this will be gone instantiation, the snmp protocol adapter sends to MIB coordinated management module with this request, asks it to remove the pairing MIB version space of the deleted network element of instantiation;
(5) MIB coordinated management module is removed the pairing MIB version space of the deleted network element of instantiation;
(6) the snmp protocol adapter will go the result of instantiation to return to the CM module.
Claims (9)
1. method that in network management system NMS, management information bank MIB is managed, described network management system comprises Simple Network Management Protocol snmp protocol adapter and managed network, described snmp protocol adapter comprises MIB coordinated management module, and described method comprises step:
All mib informations that will define for the network element of a version managing a kind of NE type in the described managed network are defined as a MIB version;
Described snmp protocol adapter will be created a MIB version space for each the MIB version in the described NMS range of management, all mib informations that each MIB version is comprised are loaded in the MIB version space of being created for described MIB version, and the SNMP object of all conflicts is placed in separately the MIB version space;
Described MIB coordinated management module is carried out instantiation and is gone instantiation corresponding M IB version space according to regulatory requirement.
2. method according to claim 1, wherein said MIB coordinated management module is only MIB version space of instantiation of each MIB version.
3. method according to claim 1, wherein when NMS starts, initially may further comprise the steps of snmp protocol adapter:
(1) creates MIB coordinated management module;
(2) from the managed object warehouse, obtain the NE type and the network element version of all network elements of described NMS management, and remove the information that wherein repeats;
(3), be each MIB version instantiation MIB version space separately according to the NE type and the network element version that obtain from described managed object warehouse in the step (2).
4. method according to claim 1, the step of a MIB version space of described instantiation comprises:
Create a new MIB version space according to given NE type and network element version;
All mib informations with described MIB version from file system are loaded in the MIB version space of new establishment.
5. method according to claim 1 also comprises step:
When the user dynamically creates by graphic user interface or deletes network element, MIB version space that the timely instantiation of described MIB coordinated management module is new or the MIB version space that goes instantiation not re-use.
6. method according to claim 5, the new MIB version space of instantiation comprises step when wherein creating new network element:
(1) when the user creates a new network element by graphic user interface, new MIB version space of the described snmp protocol adapter of Configuration Manager request instantiation in the TMN of the telecommunication management network functional module has comprised the NE type and the network element version that newly create NE in the described request;
(2) described snmp protocol adapter sends to described MIB coordinated management module with described request;
(3) whether described MIB coordinates and manages the module check MIB version space corresponding with described NE type and network element version by instantiation;
(4) if described MIB coordinated management module finds that described MIB version space by instantiation, then directly jumps to step (5); Otherwise described MIB coordinated management module will be created a new MIB version space according to given NE type and network element version, and load all mib informations that described MIB version space comprised to described MIB version space from file system; If described MIB coordinated management module can not load described mib information, then the described request operation failure;
(5) described MIB coordinated management module returns to described snmp protocol adapter with the result of instantiation;
(6) described snmp protocol adapter returns to described Configuration Manager with the result of instantiation.
7. method according to claim 5, go instantiation MIB version space to comprise step when wherein the user deletes network element:
(1) when the user deletes a network element by the user images interface, the described snmp protocol adapter of Configuration Manager request in the TMN of the telecommunication management network functional module removes the pairing MIB version space of the described network element of instantiation, has comprised the NE type and the network element version of deleted network element in the described request;
(2) carry out alternately in described snmp protocol adapter and managed object storehouse, obtains the NE type and the network element version of all network elements of current described NMS management;
(3) whether also have the network element identical with network element version among the described NMS of described snmp protocol adapter check, promptly check whether also have network element need use this will be removed the MIB version space of instantiation with the NE type of deleted network element; If also have network element need use described MIB version space, then described MIB version space can not be gone instantiation;
(4) if described snmp protocol adapter finds do not have network element need re-use the described MIB version space that will be gone instantiation, described snmp protocol adapter sends to described MIB coordinated management module with described request, asks it to remove the pairing MIB version space of the described deletion network element of instantiation;
(5) described MIB coordinated management module is removed the pairing MIB version space of the deleted network element of instantiation;
(6) described snmp protocol adapter will go the result of instantiation to return to Configuration Manager.
8. method of in network management system NMS, handling from the management request of the TMN of telecommunication management network functional module, described network management system comprises TMN functional module, managed object warehouse MOR, Simple Network Management Protocol snmp protocol adapter, described snmp protocol adapter comprises MIB coordinated management module, and described method comprises step:
(1) described snmp protocol adapter receives the management request from described TMN functional module;
(2) described snmp protocol adapter is inquired about NE type, network element version and the IP address of described network element according to the element name/network element ID that comprises in the management request from described MOR;
(3) described snmp protocol adapter and described MIB coordinated management module is mutual, obtains the pairing MIB version space of described NE type and network element version, and described like this snmp protocol adapter just can be handled this management request by described MIB version space;
(4) described snmp protocol adapter carries out alternately with the MIB version space that inquires in the step (3) according to the information that comprises the management request that comes from described TMN functional module, creates the required SNMP definition of object of SNMP request PDU thereby obtain;
(5) described snmp protocol adapter is created the SNMP request PDU according to the information that is comprised in SNMP object definition of obtaining and the management request from the MIB version space;
(6) the SNMP request PDU that will newly create of described snmp protocol adapter sends to corresponding network element;
(7) the SNMP response PDU that returns from network element is waited for and received to described snmp protocol adapter;
(8) described snmp protocol adapter is resolved SNMP response PDU, and the result is returned to described TMN functional module.
9. the alarm of in network management system NMS, handling to send from network element and the method for event notice, described network management system comprises the TMN of telecommunication management network functional module, managed object warehouse MOR, Simple Network Management Protocol snmp protocol adapter, described snmp protocol adapter comprises MIB coordinated management module, and described method comprises step:
(1) described snmp protocol adapter receives alarm or the event notice that sends from network element;
(2) described snmp protocol adapter is inquired about NE type, the network element version of described network element according to the element name/network element ID that obtains from described MOR from alarm or event notice;
(3) described snmp protocol adapter is mutual according to the NE type that obtains in the step (2) and network element version and described MIB coordinated management module, obtains the pairing MIB version space of described NE type and network element version;
(4) the MIB version space that obtains in described snmp protocol adapter and the step (3) is mutual, resolves the alarm or the event notice that receive from network element, described alarm or event notice is translated into the expression mode of alarm among the NMS or incident Common Information Model;
(5) alarm after described snmp protocol adapter will be translated or event information send to the fault management module in the described TMN functional module.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2004/000196 WO2005088905A1 (en) | 2004-03-12 | 2004-03-12 | A method for managing management information base in network managing system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1922819A CN1922819A (en) | 2007-02-28 |
| CN100428687C true CN100428687C (en) | 2008-10-22 |
Family
ID=34975958
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004800421024A Expired - Fee Related CN100428687C (en) | 2004-03-12 | 2004-03-12 | Method for managing management information base in network management system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100428687C (en) |
| WO (1) | WO2005088905A1 (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030271B (en) * | 2006-03-03 | 2011-09-28 | 中国电信股份有限公司 | Persistent inquiry method for resource service object |
| EP2645623B1 (en) * | 2011-11-02 | 2019-01-02 | ZTE Corporation | Method, device and system for managing wireless terminal by remote server |
| CN102497286A (en) * | 2011-12-12 | 2012-06-13 | 杭州华三通信技术有限公司 | Method and device for matching management information base (MIB) |
| CN102420707A (en) * | 2011-12-16 | 2012-04-18 | 大唐移动通信设备有限公司 | Method and device for managing network equipment based on management information base (MIB) |
| CN103812688A (en) * | 2012-11-15 | 2014-05-21 | 中国移动通信集团设计院有限公司 | Alarm determining method and device |
| CN107872336B (en) * | 2016-09-26 | 2021-05-14 | 中国电信股份有限公司 | Mounting point identification method and system and identification management equipment |
| CN109391506B (en) * | 2017-08-14 | 2020-08-28 | 大唐移动通信设备有限公司 | Data packet method and device |
| CN110034943B (en) * | 2018-01-12 | 2020-12-04 | 大唐移动通信设备有限公司 | Method and device for deleting Management Information Base (MIB) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6219703B1 (en) * | 1996-10-31 | 2001-04-17 | Motorola, Inc. | Method and apparatus for constructing a device management information base in a network management station |
| JP2002084279A (en) * | 2000-09-08 | 2002-03-22 | Toyo Commun Equip Co Ltd | System and method for managing snmp network |
| CN1445671A (en) * | 2002-03-15 | 2003-10-01 | 联想(北京)有限公司 | Monitoring method for remote alarming information in real time and with accuracy position |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6697970B1 (en) * | 2000-07-14 | 2004-02-24 | Nortel Networks Limited | Generic fault management method and system |
-
2004
- 2004-03-12 CN CNB2004800421024A patent/CN100428687C/en not_active Expired - Fee Related
- 2004-03-12 WO PCT/CN2004/000196 patent/WO2005088905A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6219703B1 (en) * | 1996-10-31 | 2001-04-17 | Motorola, Inc. | Method and apparatus for constructing a device management information base in a network management station |
| JP2002084279A (en) * | 2000-09-08 | 2002-03-22 | Toyo Commun Equip Co Ltd | System and method for managing snmp network |
| CN1445671A (en) * | 2002-03-15 | 2003-10-01 | 联想(北京)有限公司 | Monitoring method for remote alarming information in real time and with accuracy position |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2005088905A1 (en) | 2005-09-22 |
| CN1922819A (en) | 2007-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111796905B (en) | Method and system for realizing Kubernetes container cloud platform VLAN network | |
| US8015319B2 (en) | Method, system, client and server for implementing data sync | |
| US9509588B2 (en) | Switch management system and method | |
| EP2429120A1 (en) | Distributed network management system, network element management server, and data configuration management method | |
| EP1845688A1 (en) | Method, system, client terminal and server for realizing data synchronization | |
| CN102427410B (en) | Method, device and system for processing fiber channel identity, and network equipment | |
| CN101447891B (en) | Service model self-adapting system and method thereof | |
| CN101257406B (en) | Method and system for discovering net elements | |
| CN111901705B (en) | OMCI function virtualization system of OLT equipment | |
| CN103812838A (en) | Service calling method and device and system | |
| CN102394948B (en) | DHCP (dynamic host configuration protocol) address distribution method and DHCP server | |
| CN109936571A (en) | A kind of mass data sharing method, opening and shares platform and electronic equipment | |
| CN100428687C (en) | Method for managing management information base in network management system | |
| CN114281253B (en) | Storage volume management method | |
| US8296307B2 (en) | Contact information querying | |
| CN109962806B (en) | Method and device for managing transmission network sub-slices | |
| CN103036917A (en) | Achievement method of client side platform and client side platform | |
| CN110008006B (en) | Container-based big data tool deployment method and system | |
| EP4050904A1 (en) | Virtualization method and apparatus | |
| US8326933B2 (en) | Appearance package management method, system and device | |
| CN102571418A (en) | Method, terminal, device and system for equipment management | |
| CN114125827B (en) | Terminal management method, device and centralized management system | |
| CN115714781A (en) | Data synchronization method, hybrid cloud architecture, terminal and computer-readable storage medium | |
| CN107493181B (en) | Indication method and device of virtual expansion port | |
| CN100440801C (en) | Method for realizing integration of multi-standard management infor mation library of agent part |
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: 20081022 Termination date: 20160312 |