KR20040058457A - System and method for processing SNMP packet using index field of distributed routing system - Google Patents

Abstract

PURPOSE: A system for processing an SNMP(Simple Network Management Protocol) packet using an index field of a distributive routing system is provided to supply an index field for destination system information to an SNMP master agent, in order to distinguish overlapped MIB(Management Information Base) objects, thereby smoothly transmitting an SNMP packet. CONSTITUTION: A system A(200) consists of an SNMP master agent(201), an SNMP agent(210), an MIB table(220) related to the system A(200), and an MIB table(202). The MIB table(202) indexes an entry(203) about MIB object lists for other systems. The SNMP master agent(201) performs SNMP packet communication with an EMS(Element Management System)(100) by representing SNMP agents, and is selected by an optional process or an operator. The MIB table(220) consists of an MIB-II(220a) expanded by each vendor and a routing MIB(220b) that satisfies a routing protocol to a destination system.

Description

System and method for processing SNMP packet using index field of distributed routing system

The present invention relates to a distributed routing system, and more particularly, to providing a simple network management protocol (SNMP) master agent with an index field relating to destination system information. The present invention relates to a simple network management protocol packet processing system and method using an index field for facilitating SNMP packet transmission.

Currently, most network related devices including the Internet use a network management protocol based on the Simple Network Management Protocol (SNMP) to manage the network and monitor the operation of each network device. SNMP is the most common network management protocol, and most network systems provide an element management system (EMS) based on a Graphical User Interface (GUI) using the SNMP.

1 is a block diagram illustrating a relationship between an element management system (EMS) and a simple network management protocol (SNMP) agent in a general single system.

Referring to FIG. 1, a network system is composed of an element management system (EMS) 10 and a single system 20. Single system A 20 includes an SNMP agent 21, a Management Information Base (MIB) table 22. The EMS 10 and the SNMP agent 21 communicate with User Datagram Protocol (UDP) using ports 161 and 162. The SNMP agent 21 provides MIB object information of the corresponding system, and the EMS 10 requests the MIB object information from the SNMP agent 21. The MIB table 22 stores all the information necessary for managing the communication network.

The MIB table 22 can be divided into a MIB-II 22a extended by each vendor and a routing MIB 22b that satisfies the routing protocol to the destination system.

Here, the Border Gateway Protocol (BGP) MIB will be described as the routing MIB 22b.

For reference, BGP is a protocol commonly used between gateway hosts on the Internet, and refers to a protocol for exchanging routing information between gateway hosts in a network of an autonomous system. The routing table contains a list of known routers, accessible addresses, and cost information associated with the route to each router to select the best route.

According to the recommendations of RFC 1065, each MIB object has an Object ID (OID) and its value is unique. The OID of every MIB object has a prefix of 1.3.6.1.

When the EMS 10 sets an OID of a desired MIB along with an SNMP request packet to the port 161 of the SNMP agent 21, the SNMP agent 21 retrieves the OID from its MIB table 22 and selects the OID of the corresponding MIB. The value is loaded into the response packet and sent to the EMS (10).

When the EMS 10 requests an object (for example, a bgpPeerIdentfier MIB corresponding to the routing MIB) between the MIB-II 22a and the routing MIB 22b registered in the MIB table 22, the SNMP agent 21 Searches for its own MIB table 22 and sends the OID value (bgp.bgpPeerTable.bgpPeerEntry.bgpPeerIdentifier.0 = 1.3.6.1.2.1.15.3.1.1.0) to EMS 10.

As such, since the conventional SNMP is based on a single system, the MIB object owned by the SNMP agent of the system is also unique, so that the OID of the SNMP is not duplicated. Therefore, there is no difficulty in searching the MIB table 22 for the request of the EMS 10 and obtaining a result value for the search.

On the other hand, in the distributed routing system structure, the system consists of several systems, and the SNMP master agent plays a role of exchanging SNMP packets with EMS on behalf of the SNMP agents distributed in the system.

Here the SNMP master agent is selected by the operator or by any process process.

Each system registers its own list of MIB objects with its OID to the SNMP master agent. If the systems all have BGP MIBs, the SNMP master agent will receive duplicate BGP MIB objects and OID information from each system. Will be.

As a result, EMS encounters bgp.bgpPeerTable.bgpPeerEntry. When bgpPeerIdentifier.0 is requested from the SNMP master agent, the SNMP master agent searches for 1.3.6.1.2.1.15.3.1.1.0, the OID of bgpPeerIdentifier.0, in the MIB table that it manages and sends the EMS request to the system. You must pass it.

However, since the information of the same MIB object registered from the systems is duplicated in the MIB table of the SNMP master agent, the SNMP master agent cannot determine which system the EMS request should be forwarded to by simply retrieving the OID. There is a problem that there are many difficulties.

Of course, a system with an SNMP master delegate has a separate IP address mapping table that allows the incoming packets to the system to be delivered to the destination. Because of the large capacity of the system, the mapping table requires a lot of storage and needs to send packets to the destination address. There is a problem that the value for the destination address has a complicated structure, which makes it difficult to manage.

Accordingly, the present invention has been made to solve the above problems, and by adding an index field to the MIB object, the index field of the distributed routing system to smoothly manage duplicate MIB objects between the systems in the distributed routing system. It is an object of the present invention to provide a simple network management protocol packet processing system and a method thereof.

In addition, the purpose is to enable efficient storage of the storage space used for managing the SNMP MIB object for the entire system in a large-capacity router composed of a distributed routing system.

It also aims to organize the index fields for the destination system so that they can be used in the standard format of the index fields.

1 is a block diagram illustrating a relationship between an element management system (EMS) and a simple network management protocol (SNMP) agent in a general single system.

2 is a block diagram of a simple network management protocol packet processing system using an index field of a distributed routing system according to an embodiment of the present invention;

3 is a view for explaining an index field for system information according to the present invention;

4 is a flowchart illustrating a method of registering a list of management information base (MIB) objects present in each system in the MIB table of the SNMP master agent according to an embodiment of the present invention;

5 is a flowchart illustrating a method for transmitting and receiving SNMP packets between an element management system (EMS) and a simple network management protocol (SNMP) master agent in a distributed routing system according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

100: Element Management System (EMS)

200, 300, Z00: System A, System B, System Z

201: Simple Network Management Protocol (SNMP) Master Agent

202: Management Information Base (MIB) table about system information

203: MIB table entry

210, 310, Z10: SNMP Agent

220, 320, Z20: MIB Table

220a, 320a, Z20a: MIB-II

220b, 320b, Z20b: Routing MIB

A simple network management protocol packet processing system using an index field according to the present invention for achieving the above object comprises: an element management system (EMS) for managing a network using a simple network management protocol (SNMP); Different systems including an SNMP agent and providing a management information base (MIB) table of the system; Any system having an SNMP master agent selected by an operator among different systems, providing a MIB table for that system, and having a separate MIB table providing index information for each different system. It is characterized by.

A simple network management protocol packet processing method using an index field for achieving the above object is a method for managing a management information base (MIB) object existing in each system through a network management protocol (SNMP) agent provided in each system in a distributed routing system. A method of registering a list in an MIB table of an SNMP master agent, comprising: selecting an SNMP master agent; Each SNMP agent sending a list of MIB objects present in each system to the SNMP master agent; And the SNMP master agent configuring the MIB table for the MIB object list.

In addition, a simple network management protocol packet processing method using an index field for achieving the above object is a method for transmitting and receiving SNMP packets between an element management system (EMS) and a simple network management protocol (SNMP) master agent in a distributed routing system. Transmitting, to the SNMP master agent, a request including an index field for the MIB object to be managed by the EMS; The SNMP master agent searching the index field of the MIB table; The SNMP master agent searching for a destination system in a MIB table providing index information using an index value included in a request; Forwarding a request for a MIB object to an SNMP agent of a destination system; The SNMP agent of the destination system sends the requested MIB object value to the SNMP master agent; And setting the information transmitted by the destination system SNMP agent in the index field to the EMS master agent.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention.

2 is a block diagram of a simple network management protocol packet processing system using an index field of a distributed routing system according to an embodiment of the present invention.

Referring to FIG. 2, a network system is composed of an element management system (EMS) 100 and a distributed routing system. The distributed routing system consists of system A 200, system B 300 and system Z (Z00).

System A 200 indexes an entry 203 for an SNMP master agent 201, an SNMP agent 210, a MIB table 220 for System A, and a list of MIB objects for other systems. MIB table 202 provided in an indexable format. Here, the SNMP master agent 201 of the system A 200 performs SNMP packet communication with the EMS 100 on behalf of the SNMP agents, and is selected by any process or operator. The MIB table 220 is divided into a MIB-II 220a extended by each vendor and a routing MIB 220b that satisfies the routing protocol to the destination system.

System B 300 includes an SNMP agent 310 and a MIB table 320 for System B consisting of MIB-II 320a and routing MIB 320b.

System Z (Z00) includes an SNMP agent (Z10) and a MIB table (Z20) for system Z consisting of MIB-II (Z20a) and routing MIB (Z20b).

3 is a view for explaining an index field for system information according to the present invention.

Referring to FIG. 3, the index field structure includes a shelf number, a slot number, a port number, and a hardware number of a device to which a system is connected to contain hardware information on which a system is located. It consists of fields for information.

On the other hand, since the type of equipment is provided in the hardware information, it is not necessary to know the port number when it is not necessary to know the port number according to the type of equipment.

Therefore, if there is no corresponding information on the port number, set it to '0'.

When the index field is configured as described above, when the request including the index field information is sent from the EMS 100 to the SNMP master agent 201, the SNMP master agent has an index field entry 203 of its own MIB table 202. You can easily find the destination system to which you want to forward SNMP requests.

Hereinafter, a method for configuring an index field for a MIB object in the MIB table of the SNMP master agent will be described.

4 is a flowchart illustrating a method of registering a list of management information base (MIB) objects existing in each system in the MIB table of the SNMP master agent according to an embodiment of the present invention.

Referring to FIG. 4, the SNMP master agent 201 is selected among the SNMP agents 210, 310, and Z10 of the respective systems by an operator (or an arbitrary process) in the same manner as the conventional method (S1), and each SNMP agent 210, 310, Z10) transmits an index field representing the MIB object and system information existing in each system to the SNMP master agent (S2).

The SNMP agents 210, 310, and Z10 configure the MIB tables 220, 320, and Z20 for the corresponding MIB object, and the SNMP master agent 201 adds the received index field to the MIB table entry 203 about the system information. (S3).

After the index field for the system information is configured in the MIB table 202 of the SNMP master agent 201 of the distributed routing system, a method of actually transmitting and receiving SNMP packets between the EMS 100 and the SNMP master agent 201 is described. It is done as follows.

5 is a flowchart illustrating a method for transmitting and receiving SNMP packets between an element management system (EMS) and a simple network management protocol (SNMP) master agent in a distributed routing system according to an embodiment of the present invention.

Referring to FIG. 5, when a request including an index field is transmitted to the SNMP master agent 201 for the MIB object to be managed by the EMS 100 (S10), the SNMP master agent 201 may transmit system information. The entry 203 of the MIB table 202 is searched for (S20).

The SNMP master agent 201 finds the destination system in the corresponding entry 203 of the MIB table 202 for the system information by using the index value included in the request (S30).

When the destination system is found, the request for the MIB object is transmitted to the SNMP agent of the destination system (S40), and the SNMP agent of the destination system transmits the requested MIB object value to the SNMP master agent 201 (S50).

The SNMP master agent sets the information transmitted from the destination system SNMP agent to the index field and transmits the information to the EMS 100 (S60).

For example, if system A is on shelf # 5 / slot # 1, system B is on shelf # 5 / slot # 2, and system Z is on shelf # 5 / slot # 3, the index value of each system is As shown in FIG. 3, system A is 50100000, system B is 50200000, and system Z is 50300000.

Here, the calculation of the values displayed in the index field is performed as in Equation 1.

Here, it should be noted that the value entered in the index field is not a definite item, and the size or values of the field may be changed by the operator according to the structure of the system or the difference in hardware.

The above values are configured by including the index field entry of the MIB table 202 in advance when the MIB object of each system is registered with the SNMP master agent.

When the EMS 100 sends an SNMP GetRequest to the SNMP master agent 201 for bgpPeerIdentifier.50200000, the SNMP master agent 201 sees the 50200000 index value and the SNMP for the bgpPeerIdentifier as the SNMP agent 310 of system B 300. Pass GetRequest.

The SNMP agent 310 of the system B 300 sends the value of the requested MIB to the SNMP master agent 201, and the SNMP master agent 201 of the system B 300 before sending the result value to the EMS 100. The index value 50200000 is set in the index field and transmitted.

Therefore, when the EMS transmits the SNMP packet for the MIB object to be managed, the EMS can be easily delivered to the SNMP agent of the destination system by using the index field of the destination system.

Although the preferred embodiments of the present invention have been described in detail above, those skilled in the art will appreciate that the present invention may be modified without departing from the spirit and scope of the invention as defined in the appended claims. It will be appreciated that modifications or variations may be made. Therefore, changes in the future embodiments of the present invention will not be able to escape the technology of the present invention.

As described above, according to the present invention, by adding an index field to the MIB object, it is possible to process duplicate MB objects in the distributed routing system, and facilitate the management of SNMP MIB objects for the entire large-capacity distributed routing system. There is an advantage to this.

Claims (9)

In a distributed routing system, An element management system (EMS) for managing a network using a simple network management protocol (SNMP); A plurality of systems including an SNMP agent and providing a management information base (MIB) table of the system; Any of a plurality of systems, including an SNMP master agent selected by an operator or any process, providing a MIB table for that system, and having a separate MIB table that provides index information for multiple systems from each other. Simple network management protocol packet processing system using the index field, characterized in that consisting of a system. The method of claim 1, wherein the MIB table providing the index information, A shelf number (shelf #) field for indicating the shelf number; A slot number field for indicating a slot number; And A simple network management protocol packet processing system using an index field, characterized by comprising a port # field for indicating a port number. The method of claim 1, wherein the MIB table providing the index information, A shelf number (shelf #) field for indicating the shelf number; A slot number field for indicating a slot number; And A simple network management protocol packet processing system using an index field, characterized in that it comprises a hardware information field for representing hardware information. The method of claim 1, wherein the MIB table providing the index information, A shelf number (shelf #) field for indicating the shelf number; A slot number field for indicating a slot number; Port # field to indicate the port number: and A simple network management protocol packet processing system using an index field, characterized in that it comprises a hardware information field for representing hardware information. The method according to any one of claims 2, 3 and 4, wherein each field of the MIB table that provides the index information, Simple network management protocol packet processing system using the index field, characterized in that the size and value of the field is changed by the operator according to the structure of the system and the type of hardware. The method according to any of claims 2, 3 and 4, wherein the calculation for the values indicated in the index field is Simple network management protocol packet processing system using the index field, characterized in that made as follows. The method of claim 2 or 4, wherein the port number (port #) field, If it is not necessary to know the port number according to the hardware information, it is not necessary to know the port number, so if there is no corresponding information on the port number, the simple network management protocol using the index field, characterized in that set to '0' Packet processing system. In a distributed routing system, a method for registering a list of management information base (MIB) objects existing in each system through a network management protocol (SNMP) agent provided in each system in the MIB table of the SNMP master agent, Selecting an SNMP master agent; Transmitting, by each SNMP agent, the index information representing the MIB object and system information present in each system to the SNMP master agent; And The SNMP agent configures the MIB table for the corresponding MIB object, and the SNMP master agent configures the received index information by adding the received index information to the MIB table entry related to the system information. Protocol packet processing method. A method for transmitting and receiving SNMP packets between an element management system (EMS) and a simple network management protocol (SNMP) master agent in a distributed routing system, Transmitting a request including an index field to the SNMP master agent for the MIB object to be managed by the EMS; The SNMP master agent searching the index field of the MIB table; The SNMP master agent searching for a destination system in a MIB table providing index information using an index value included in a request; Forwarding a request for a MIB object to an SNMP agent of a destination system; The SNMP agent of the destination system sends the requested MIB object value to the SNMP master agent; And And the SNMP master agent sets the information transmitted from the destination system SNMP agent to the index field and transmits the information to the EMS.