CN101977142B - Simple network management method and device based on multiple routing protocol instances - Google Patents
Simple network management method and device based on multiple routing protocol instances Download PDFInfo
- Publication number
- CN101977142B CN101977142B CN201010508868.4A CN201010508868A CN101977142B CN 101977142 B CN101977142 B CN 101977142B CN 201010508868 A CN201010508868 A CN 201010508868A CN 101977142 B CN101977142 B CN 101977142B
- Authority
- CN
- China
- Prior art keywords
- routing protocol
- identification information
- data object
- mib
- information
- 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.)
- Active
Links
Landscapes
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a simple network management method based on multiple routing protocol instances, comprising the following steps: configuring identification information for each routing protocol instance; carrying identification information of the routing protocol instances to which data objects belong for all data objects in a management information base (MIB); and according to the identification information of the routing protocol instances carried by the data objects in the MIB, acquiring multi-instance information. The invention also discloses a simple network management device based on multiple routing protocol instances, comprising a configuration unit for configuring the identification information for each routing protocol instance and carrying the identification information of the routing protocol instances to which the data objects belong in the MIB, and an acquisition unit for acquiring the multi-instance information in accordance with the identification information of the routing protocol instances to which the data objects belong in the MIB. In the invention, the technical scheme of the invention is simple in realization, thereby preferably guaranteeing routing protocol management under the condition of the multiple routing protocol instances.
Description
Technical field
The present invention relates to the technology that the Routing Protocol based on Simple Network Management Protocol (SNMP, Simple Network MangerProtocol) manages, particularly relate to a kind of simple network management method based on the many examples of Routing Protocol and device.
Background technology
Route technology plays important role in IP network development, affects network routing convergence speed and transmission performance lifting to a great extent.Standard routing protocol of today is all by Internet tissue (IETF, The Internet Engineering Task Force) issue, mainly contain ospf (OSPF, Open Shortest Path First), the routing protocol (IS-IS of Intermediate System-to-Intermediate System, Intermediate System to Intermediate System Routing Protocol) and Border Gateway Protocol (BGP, Border Gateway Protocol) etc., they bear the role of route supplier in a network.All kinds of Routing Protocol entities have self correlation performance parameters, check protocol entity performance, and adjust parameter in time, reach network performance optimum by these parameters.
Simple Network Management Protocol (SNMP, Simple Network Manger Protocol) be a set of NMP defined by Internet tissue, utilize this agreement, management work station can the network equipment of all this agreements of support of telemanagement, comprise monitoring network running status, amendment network operational parameter and receive network time alarm etc., thus reaching the requirement of management equipment.Can effectively manage equally for the Routing Protocol that online equipment is run.Usually, user assigns administration order to the Routing Protocol on managed devices, such as inquire about (get operation) or amendment (set operation), Routing Protocol, after receiving administration order, is inquired about or Update Table in management information bank (MIB, Management Information Base), if query manipulation, these parameters are fed back by Routing Protocol entity, if retouching operation, Routing Protocol entity revises this corresponding data immediately.
How fully effective by MIB operation acquisition or amendment Routing Protocol solid data, will be the key factor determining to realize network routing protocol information monitoring and performance management.Along with the development of Routing Protocol standard, realize day by day complicated, particularly after Routing Protocol multiple example type, reach by MIB operation the object monitored and manage difficult especially.
At present, the mib standard being applied to each network routing protocol mainly contains RFC4750 (OSPFv2), RFC5643 (OSPFv3), RFC4444 (IS-IS) etc.For the above-mentioned standard RFC4444 being applied to the Internet organisations publish of Intermediate System to Intermediate System, carry out basic demand and the flow process following (other Routing Protocols are similar) of MIB get operation:
(1) enable snmp protocol on the router.
(2) configure an IS-IS route entity on the router, make it normally run, and produce necessary Intermediate System to Intermediate System information.
(3) for specific MIB tree node, user assigns query manipulation instruction to IS-IS route entity.Object identity (OID, the Object Identifier) information decoding that SNMP transmits by Intermediate System to Intermediate System is the data object corresponding to agreement inside.The data of correspondence are returned to SNMP and are used for display by Intermediate System to Intermediate System.
User carries out basic demand and the flow process following (other Routing Protocols are similar) of a MIB set operation:
(1) enable snmp protocol on the router.
(2) an enable IS-IS route entity on the router, makes it normally run, and produces necessary Intermediate System to Intermediate System information.
(3) for specific MIB tree node, user assigns retouching operation instruction to IS-IS route entity.User inputs corresponding MIB node numerical value to be modified (this numerical value should in Limit of J-validity), and the OID information decoding that snmp protocol transmits by Intermediate System to Intermediate System is the data object corresponding to agreement inside.The value of the data of correspondence is revised as the numerical value that SNMP transmits by Intermediate System to Intermediate System.
(4) Intermediate System to Intermediate System produces new routing iinformation according to the numerical value after amendment, and user can judge whether to reach requirement according to these information, otherwise can continue to do set operation adjustment, finally reaches customer satisfaction system performance index.
These international standards announced by IETF of comprehensive analysis, each MIB table (MIB leaf node) designs for single instance, there is not many example information, these standards of the information of Multi-instance cannot be realized inquiry and retouching operation yet.That is, for Routing Protocol entity, MIB inquiry or retouching operation can only be carried out for single example, and nowadays answer the requirement of network Development, the many examples of supported protocol, namely an online equipment can configure multiple similar Routing Protocol, reaches thousands of at most.Present Routing Protocol mib standard cannot meet Routing Protocol demand for development.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of simple network management method based on the many examples of Routing Protocol and device.
For achieving the above object, technical scheme of the present invention is achieved in that
Based on a simple network management method for the many examples of Routing Protocol, comprising:
For each Routing Protocol example arranges identification information;
In the data object that MIB comprises, carry the identification information of Routing Protocol example belonging to data object;
Belonging to carrying according to data object in described MIB, the identification information of Routing Protocol example, obtains many example information.
Preferably, the identification information carrying affiliated Routing Protocol example in described data object is specially:
Set up the identification information of this Routing Protocol example in OID in the MIB table of Routing Protocol example, wherein, in the data object transmitted, comprise described OID.
Preferably, the identification information setting up this Routing Protocol example in the OID in the described table of the MIB at Routing Protocol example is specially:
Using the identification information of Routing Protocol example as the new leaf node in the MIB table of Routing Protocol example.
Preferably, using the identification information of Routing Protocol example as Routing Protocol example MIB table in first new leaf node.
Preferably, described method also comprises:
For each leaf node added in the MIB table of new leaf node resets OID, and register in Routing Protocol.
Preferably, described method also comprises:
When Routing Protocol entity receives the snmp management instruction based on data object, the identification information determination data object of the OID information of carrying with supervisory instruction and/or protocol instance, and supervisory instruction is performed to determined data object;
Or, when Routing Protocol entity reports unsolicited message, the data object identified with the identification information of OID information and/or protocol instance is reported SNMP.
Preferably, described snmp management instruction comprises one of following or combination in any: the renewal instruction of the query statement to the data object of route protocol instance, the data object to route protocol instance.
Based on a simple network management device for the many examples of Routing Protocol, comprising:
Setting unit, for arranging identification information for each Routing Protocol example; In the data object that MIB comprises, carry the identification information of Routing Protocol example belonging to data object;
Acquiring unit, belonging to carrying according to data object in described MIB, the identification information of Routing Protocol example, obtains many example information.
Preferably, described setting unit further, sets up the identification information of this Routing Protocol example in the OID in the MIB table of Routing Protocol example; Wherein, described OID is comprised in the data object transmitted.
Preferably, described setting unit further, using the identification information of Routing Protocol example as Routing Protocol example MIB table in new leaf node; A leaf node headed by described new leaf node.
Preferably, described device also comprises receiving element, determining unit and the performance element be located in Routing Protocol entity, wherein,
Receiving element, during for receiving the snmp management instruction based on data object, triggers determining unit;
Determining unit, for the identification information determination data object of the OID information of carrying in supervisory instruction and/or protocol instance;
Performance element, for performing supervisory instruction to determined data object.
Preferably, described device also comprises:
Reporting unit, be located in Routing Protocol entity, for reporting unsolicited message, wherein, reporting SNMP with the data object of the identification information of OID information and/or protocol instance mark.
In the present invention, by upgrading the MIB table of route protocol instance, namely the identification information for identifying the Routing Protocol example belonging to himself is set in MIB table; Concrete, in MIB table, arrange new leaf node, namely this new leaf node is the identification information of the Routing Protocol example belonging to this MIB shows.Again OID is reset to each leaf node in MIB table, make the identification information carrying Routing Protocol example in OID, like this, Routing Protocol entity is when receiving relevant supervisory instruction, the identification to routing instances to be managed can be realized by the identification information of the Routing Protocol example carried in instruction, thus can manage any data object of any Routing Protocol entity; Further, realize the management work to multiple routing instances by a supervisory instruction, greatly facilitate user for the Routing Protocol management work in multirouting agreement situation.Technical solution of the present invention ensure that the Routing Protocol management in multirouting agreement situation well.
Accompanying drawing explanation
Fig. 1 is neighboring router connection diagram;
Fig. 2 is the simple network management device composition structural representation that the present invention is based on the many examples of Routing Protocol.
Embodiment
Basic thought of the present invention is: by upgrading the MIB table of route protocol instance, in MIB table, namely arrange the identification information for identifying the Routing Protocol example belonging to himself; Concrete, in MIB table, arrange new leaf node, namely this new leaf node is the identification information of the Routing Protocol example belonging to this MIB shows.Again OID is reset to each leaf node in MIB table, make the identification information carrying Routing Protocol example in OID, like this, Routing Protocol entity is when receiving relevant supervisory instruction, the identification to routing instances to be managed can be realized by the identification information of the Routing Protocol example carried in instruction, thus can manage any data object of any Routing Protocol entity; Further, by realizing the management work to multiple routing instances in a supervisory instruction, user is greatly facilitated for the Routing Protocol management work in multirouting agreement situation.
For making the object, technical solutions and advantages of the present invention clearly understand, by the following examples also with reference to accompanying drawing, the present invention is described in more detail.
In the present invention, for ensureing the management to multirouting protocol instance, need to carry out relevant configuration to the MIB table of route protocol instance.Concrete, on every platform router, configure multiple Routing Protocol entities (each Routing Protocol entity can be distinguished by different instances number) of Routing Protocol of the same type, two routers be connected to each other mutually set up neighbours respectively on each route entity, and, when setting up neighborhood, do not distinguish IPv4 and IPv6 neighbours.Such formation example Routing Protocol more than running environment.Routing Protocol includes but not limited to OSPF, ISIS and BGP etc.
In the Routing Protocol mib standard issued by IETF such as RFC4750 (OSPFv2), RFC5643 (OSPFv3), RFC4444 (IS-IS) etc., often open MIB table and be not with instance number, also do not have other to can be used to travel through the index of all Routing Protocol examples, which has limited MIB function can only carry out monitor and managment to single particular instance; Can not switch between each example.The Routing Protocol entity that such router runs just cannot be arrived by network manager monitor and managment, is unfavorable for network operation and management.
In the present invention, be each Routing Protocol entity setting up instance number, as long as this instance number energy unique identification routing instances; Certainly, also can be other identification information; Instance number is added to an index of the MIB table of corresponding Routing Protocol example in MIB tree.Mib file is the vital document related in MIB operation, all realizes according to standard.In the present invention, showing for often opening MIB the amendment that interpolation index instance number just must consider mib file, specifically comprising two steps:
(1) instance number is represented for often opening MIB table interpolation leaf node;
(2) index-group for often opening MIB table adds a new index instance number.The position that instance number will affect in No. OID residing for instance number in the position of index-group as index, therefore, is preferably arranged at the position easily distinguished by instance number.In the present invention, it is placed on first index position.Like this, just need to carry out following work: (1) applies for an OID again for each leaf node, and this OID comprises the instance number newly added, in the OID of namely new data object, include the identification information of Routing Protocol example belonging to instruction self; (2) for each leaf node is registered in agreement inside again.
After mib file remodifies, need to recompilate and errorlessly just can to use, can by checking that whether correct MIB tree structure determined the amendment of mib file.Above-mentioned detection is the preparation process that the present invention realizes, and automatically to detect or by manually detecting by detecting application accordingly.
The inside of mib file and Routing Protocol realizes there is close relationship.After mib file adds a new leaf node instance number and index, corresponding amendment also will done to the process of OID information in agreement inside, specifically comprises following aspect:
(1), when Routing Protocol entity is to related management instruction (supervisory instruction for data object) of SNMP transmission for the data object (by data object OID message identification) in Routing Protocol example, the process of regulation how to the instance number of the new Routing Protocol example added is needed; In the present invention, be the instance number information of Routing Protocol example is added in OID go; That is, need to make Routing Protocol entity Exact Solutions separate out the instance number of the Routing Protocol example in OID;
(2) after Routing Protocol entity receives the related management instruction for the data object in Routing Protocol example, according to the OID information of the data object carried in this dependent instruction, the identification information of the Routing Protocol example carried in OID information is parsed as an example number.Routing Protocol entity is according to the instance number of Routing Protocol example, corresponding Routing Protocol example can be determined, again according to the identification information of the leaf node in OID information, accurately can determine the data object of concrete Routing Protocol example, thus the data object corresponding to OID information performs corresponding supervisory instruction.Concrete, the instance number of Routing Protocol example is arranged in the ad-hoc location of OID information.
Fig. 1 is neighboring router connection diagram, and as shown in Figure 1, two routers Router1 and Router2 adjoins each other, and wherein, Router1 is as local terminal router, and all MIB operate on local terminal router and carry out.Local terminal router configures multiple Routing Protocol entity, each Routing Protocol entity corresponds to multiple Routing Protocol example, such as example 1, example 2, example 3 etc., and under each example configuration of IP v4 (or IPv6) interface, make its this Routing Protocol enable, the primary condition setting up the type Routing Protocol neighbours can be met.Router2, as far-end router, does not carry out any MIB operation.Corresponding with multiple route entities that local terminal router configures, far-end router is configured with multiple route entity too; Further, on Router1 and Router2 each correspondence example between set up neighborhood respectively.In the present invention, come to set up neighborhood between local terminal router at far-end router, mainly consider in MIB operation, have the demand that adjacent route-map is inquired about or revised.
Enable snmp protocol on Router1, coordinates Routing Protocol, MIB is inquired about and revises (renewal) environment to use.
Introduce the query manipulation for MIB below in detail, MIB query manipulation realizes being divided into three links, is respectively: inquiry first, again inquiry are got next with category node and exact matching.Perform query manipulation for multirouting entity, specifically set forth realization flow.
(1) inquire about first; Send MIB querying command by SNMP to Routing Protocol entity, carry for multiple MIB querying command in this MIB querying command.Here, owing to being inquire about for the first time, therefore, the index information of data object is not comprised in the OID information of carrying in MIB querying command, only carry the positional information of MIB leaf node last layer node, therefore Routing Protocol entity cannot determine concrete data-object index information according to current MIB querying command, but can be resolved to the information of the Routing Protocol example belonging to leaf node to be checked.Routing Protocol entity receives MIB querying command, is confirmed to be and inquires about first.First Routing Protocol entity locates first Routing Protocol entity to be checked, there is the data object depositing corresponding leaf node information Routing Protocol inside, the first data object that can get is assigned to this leaf node and returns to SNMP, and the index information of the data object simultaneously also comprised by this leaf node together returns to SNMP.After SNMP receives this two parts data message, SNMP carries out exact matching according to these OID information protocol inside.In addition using the index information of leaf node to be checked as the index inquired about next time.
(2) again inquire about; Be limited to volume of transmitted data, if leaf node to be checked also has information in inside, (comprising multiple data object) does not feed back to SNMP, SNMP still sends querying command, the OID packets of information that current MIB querying command carries is containing index information, and Routing Protocol entity parses the entry (data object) of the leaf node that last time, the process of MIB query manipulation was arrived according to the index information in OID information.After navigating to the entry of the leaf node of process last time, then take out the entry of next leaf node of this entry, the information of this leaf node entry and index information are together fed back to SNMP.SNMP carries out exact matching according to these OID information to agreement inside, thus accurately can orient the positional information of data object to be checked.
(3) exact matching; Distinguishing inquiry and the main cause of exact matching is again will pass to SNMP for two parts functional areas of showing separately getting next nodal value index information and this being got mib information, is also easier to understanding.The process of exact matching is same as the process of the location current entries again inquired about, when navigating to entry corresponding to current index, by information feed back to SNMP.
(4) until all information of this leaf node of this example is all fed back complete, the Routing Protocol example belonging to next/to be checked a bit data object is located again by this Routing Protocol instance number, repeat above-mentioned steps, until all leaf node information to be checked are all fed back complete.
In above-mentioned query manipulation, it can be the inquiry carried out for each data object of all Routing Protocol examples, as sent the MIB query statement of acquiescence to Routing Protocol entity, Routing Protocol entity from first Routing Protocol example backward, will feed back the data object corresponding to each leaf node in each Routing Protocol example one by one; Certainly, also can be only for the inquiry that the MIB of wherein certain some Routing Protocol example carries out, Routing Protocol entity is by from indicated Routing Protocol example backward, feed back the data object corresponding to each leaf node in each Routing Protocol example one by one, or, according to the identification information of the Routing Protocol example carried in query statement, by data object information corresponding for each leaf node in the routing instances that carries in query statement, feed back to SNMP one by one; Or the inquiry of the concrete data object for the MIB of a certain Routing Protocol example, now, query manipulation is equivalent to the MIB after exact matching to be inquired about.
Upgrade (amendment) operation to MIB below to describe in detail.Concrete, MIB retouching operation, only for there being the readable leaf node revising authority, can being revised a Routing Protocol example at every turn, also can revise the leaf node of the same type of multiple Routing Protocol example.It should be noted that, can carry out after to MIB query manipulation MIB retouching operation, also after the data object of leaf node determining concrete MIB to be modified, can directly send the amendment order for this data object to be modified.Generally speaking, retouching operation carries out after above-mentioned query manipulation, because only after the specifying information determining each data object, could revise accordingly according to institute's Query Result.
MIB retouching operation specifically comprises the following steps:
(1) first complete above-mentioned query manipulation, obtain the OID information of all leaf nodes to be modified, leave in snmp protocol.
(2) SNMP is according to this leaf node revaluate to be repaired of these OID information and user's input, sends for the amendment order of concrete data object to Routing Protocol entity; As previously mentioned, amendment order can, for some data objects, also can be for data object of the same type in some Routing Protocol example;
(3) after Routing Protocol entity receives the amendment order of SNMP transmission, according to the OID information of carrying in amendment order, an exact matching is carried out to certain data objects in route protocol instance, then by data object that the value assignment to be modified that user inputs is specified to this OID information.Concrete, after the index information of the identification information and concrete leaf node that carry Routing Protocol example in OID information, concrete Routing Protocol example can be found out according to the identification information of Routing Protocol example, data object specifically to be modified is being found out again in Routing Protocol example, and the value assignment to be modified user inputted is to the concrete data object indicated by this OID information, realizes the amendment to this data object.
In the present invention, except carrying out except query manipulation and retouching operation to data object, a class is also had by the unsolicited message (such as Trap message) of Routing Protocol entity active reporting in the middle of MIB, the MIB nodal information corresponding according to the type message resolves this unsolicited message, and analysis result is sent to SNMP.As service layer, after Routing Protocol introduces many examples, the unsolicited message such as Trap message are distinguished Routing Protocol example equally and send, and are embodied in route entity to instance number to encode, and use-case number distinguishes this message jointly with other index informations, and send to SNMP; After SNMP receives this unsolicited message, according to the index information that this unsolicited message is carried, clearly can know that this unsolicited message is from which Routing Protocol example, belongs to the message etc. of which kind.Such SNMP can by the monitoring of these message realization to all Routing Protocol examples.
The present invention can support that webmaster terminal monitors the ruuning situation of the multirouting protocol instance on router simultaneously effectively.No matter the get operation of SNMP, set operation, or the unsolicited message that equipment reports, can deal with for the corresponding data of each example very clearly, feed back to SNMP simultaneously, thoroughly achieve the accurate management to institute's Routing Protocol.
Fig. 2 is the simple network management device composition structural representation that the present invention is based on the many examples of Routing Protocol, as shown in Figure 2, the simple network management device that the present invention is based on the many examples of Routing Protocol comprises setting unit 20 and acquiring unit 21, wherein, setting unit 20 is for arranging identification information for each Routing Protocol example; In the data object that MIB comprises, carry the identification information of Routing Protocol example belonging to data object; Acquiring unit 21, belonging to carrying according to data object in described MIB, the identification information of Routing Protocol example, obtains many example information.
As shown in Figure 2, the simple network management device that the present invention is based on the many examples of Routing Protocol also comprises the receiving element 22 be located in Routing Protocol entity, determining unit 23 and performance element 24, wherein,
Receiving element 22, during for receiving the snmp management instruction based on data object, triggers determining unit 23;
Determining unit 23, for the identification information determination data object of the OID information of carrying with supervisory instruction and/or protocol instance;
Performance element 24, for performing supervisory instruction to determined data object.
The simple network management device that the present invention is based on the many examples of Routing Protocol can also comprise and reports unit (not shown), be located in Routing Protocol entity, for reporting unsolicited message, wherein, the Routing Protocol example belonging to data object reported is identified with the identification information of OID information and/or protocol instance.
Those skilled in the art are to be understood that, above-mentioned receiving element 22, determining unit 23 and performance element 24 arrange for optimizing the simple network management device based on the many examples of Routing Protocol of the present invention, is not the essential features realizing the basic object of the present invention.The above-mentioned unit that reports also is arrange for optimizing the simple network management device based on the many examples of Routing Protocol of the present invention, is not the essential features realizing the basic object of the present invention.
Above-mentioned setting unit 20 further, sets up the identification information of this Routing Protocol example in the OID in the MIB table of Routing Protocol example; Described OID is comprised in the data object transmitted.
Above-mentioned setting unit 20 further, using the identification information of Routing Protocol example as Routing Protocol example MIB table in new leaf node; A leaf node headed by described new leaf node.
The simple network management device based on the many examples of Routing Protocol shown in Fig. 2 designs for realizing the aforesaid simple network management method based on the many examples of Routing Protocol, and the practical function of above-mentioned each unit can refer to the associated description of preceding method and understands.The function of each processing unit in figure realizes by the program run on processor, also realizes by concrete logical circuit.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (7)
1., based on a simple network management method for the many examples of Routing Protocol, it is characterized in that,
For each Routing Protocol example arranges identification information;
In the data object that management information bank (MIB) comprises, carry the identification information of Routing Protocol example belonging to data object;
Belonging to carrying according to data object in described MIB, the identification information of Routing Protocol example, obtains many example information;
Wherein, the identification information carrying affiliated Routing Protocol example in described data object is specially: using the identification information of Routing Protocol example as the new leaf node in the MIB table of Routing Protocol example, object identity (OID) is reset to each leaf node in MIB table, makes the identification information carrying described Routing Protocol example in OID;
Described carry according to data object in described MIB belonging to the identification information of Routing Protocol example, obtain many example information, be specially: after Routing Protocol entity receives the snmp management instruction for the data object in Routing Protocol example, according to the identification information of the Routing Protocol example carried in the OID information of the data object carried in described supervisory instruction, determine corresponding Routing Protocol example, again according to the identification information of the leaf node in OID information, determine the data object of described Routing Protocol example, and supervisory instruction is performed to described data object.
2. method according to claim 1, is characterized in that, using the identification information of Routing Protocol example as the first new leaf node in the MIB table of Routing Protocol example.
3. method according to claim 1 and 2, is characterized in that, described method also comprises:
When Routing Protocol entity reports unsolicited message, the data object identified with the identification information of OID information and/or protocol instance is reported SNMP.
4. method according to claim 3, is characterized in that, described snmp management instruction comprises one of following or combination in any: the renewal instruction of the query statement to the data object of route protocol instance, the data object to route protocol instance.
5. based on a simple network management device for the many examples of Routing Protocol, it is characterized in that, described device comprises:
Setting unit, for arranging identification information for each Routing Protocol example, using the identification information of Routing Protocol example as the new leaf node in management information bank (MIB) table of Routing Protocol example, and object identity (OID) is reset to each leaf node in MIB table, make the identification information carrying described Routing Protocol example in OID;
Acquiring unit, belonging to carrying according to data object in described MIB, the identification information of Routing Protocol example, obtains many example information;
Wherein, described device also comprises receiving element, determining unit and the performance element be located in Routing Protocol entity, wherein,
Receiving element, during for receiving the snmp management instruction for the data object in Routing Protocol example, triggers determining unit;
Determining unit, for the identification information according to the Routing Protocol example carried in the OID information of the data object carried in described supervisory instruction, determines corresponding Routing Protocol example; Also for the identification information according to the leaf node in OID information, determine the data object of described Routing Protocol example;
Performance element, for performing supervisory instruction to determined data object.
6. device according to claim 5, is characterized in that, described setting unit, is further used for the identification information of Routing Protocol example as the first new leaf node in the MIB table of Routing Protocol example.
7. the device according to claim 5 or 6, is characterized in that, described device also comprises:
Reporting unit, be located in Routing Protocol entity, for reporting unsolicited message, wherein, reporting SNMP with the data object of the identification information of OID information and/or protocol instance mark.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010508868.4A CN101977142B (en) | 2010-10-12 | 2010-10-12 | Simple network management method and device based on multiple routing protocol instances |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010508868.4A CN101977142B (en) | 2010-10-12 | 2010-10-12 | Simple network management method and device based on multiple routing protocol instances |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101977142A CN101977142A (en) | 2011-02-16 |
| CN101977142B true CN101977142B (en) | 2014-12-31 |
Family
ID=43576989
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010508868.4A Active CN101977142B (en) | 2010-10-12 | 2010-10-12 | Simple network management method and device based on multiple routing protocol instances |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101977142B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2803648C2 (en) * | 2019-03-11 | 2023-09-19 | Драйвнетс Лтд. | System and method for traffic routing in mpls network |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103368758B (en) * | 2012-03-31 | 2017-05-31 | 中兴通讯股份有限公司 | The method and system of L3 Switching relation between detection and presentation device |
| CN104098604B (en) * | 2013-04-10 | 2016-12-28 | 山东省生物药物研究院 | A kind of method preparing fosaprepitant dimeglumine |
| CN104780072A (en) * | 2015-04-25 | 2015-07-15 | 安徽皖通邮电股份有限公司 | IS-IS protocol multi-case host name setting method |
| CN105357034B (en) * | 2015-10-20 | 2018-11-20 | 广州海格通信集团股份有限公司 | Leaf node creating device and communication means and system based on SNMP |
| CN108616978B (en) * | 2016-12-14 | 2022-04-15 | 中兴通讯股份有限公司 | Method and device for performing stateless processing on network function entity |
| CN109213783A (en) * | 2018-11-15 | 2019-01-15 | 凌云天博光电科技股份有限公司 | A kind of structuralized query method and device based on MIB |
| US12010014B2 (en) * | 2019-03-11 | 2024-06-11 | Drivenets Ltd. | System and a method for routing traffic in an MPLS network |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1400772A (en) * | 2001-08-03 | 2003-03-05 | 华为技术有限公司 | Method for making data layout in communication equipment and its system |
| CN101335756A (en) * | 2007-06-29 | 2008-12-31 | 凹凸电子（武汉）有限公司 | Systems and methods for snmp access |
-
2010
- 2010-10-12 CN CN201010508868.4A patent/CN101977142B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1400772A (en) * | 2001-08-03 | 2003-03-05 | 华为技术有限公司 | Method for making data layout in communication equipment and its system |
| CN101335756A (en) * | 2007-06-29 | 2008-12-31 | 凹凸电子（武汉）有限公司 | Systems and methods for snmp access |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| RU2803648C2 (en) * | 2019-03-11 | 2023-09-19 | Драйвнетс Лтд. | System and method for traffic routing in mpls network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101977142A (en) | 2011-02-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101977142B (en) | Simple network management method and device based on multiple routing protocol instances | |
| US10992543B1 (en) | Automatically generating an intent-based network model of an existing computer network | |
| US10057116B2 (en) | Method and device for configuring and managing network element equipment, and network element equipment | |
| WO2021018155A1 (en) | Routing information monitoring method and apparatus | |
| CN114884873A (en) | Method and device for determining forwarding path | |
| US11902118B2 (en) | Traffic monitoring in a packet-switched communication network | |
| WO2016103069A1 (en) | Service performance monitoring in a virtualized communication network | |
| US20210250295A1 (en) | Route event record event record entry processing method, network device, and control device | |
| CN103905251A (en) | Network topology obtaining method and device | |
| CN104283802A (en) | Neighbor discovery method and device | |
| CN114503524A (en) | Closed loop automation for intent-based networking | |
| CN113114509A (en) | Method and equipment for message forwarding simulation in SDN network environment | |
| CN108924011A (en) | Monitoring system, relevant device, method and medium for OSPF+ Routing Protocol | |
| US11929851B2 (en) | Gateway selection method, device, and system | |
| CN100440796C (en) | Method for obtaining network key property indication and key property indication module | |
| CN105637806A (en) | Method and apparatus for determining network topology, and centralized network state information storage device | |
| CN107566277B (en) | Topology determining method, message response method, controller and switch | |
| CN112333014B (en) | Device management method and communication apparatus | |
| CN107769964B (en) | Special line checking method and system | |
| CN115801674A (en) | Dual-stack SDN control method, device, medium and system | |
| EP4080850A1 (en) | Onboarding virtualized network devices to cloud-based network assurance system | |
| KR102092015B1 (en) | Method, apparatus and computer program for recognizing network equipment in a software defined network | |
| CN110109933A (en) | Information maintenance method, configuration management database system and storage medium | |
| CN100477599C (en) | A network management method aiming at network device | |
| KR102385707B1 (en) | SDN network system by a host abstraction and implemented method therefor |
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 |