KR20000013259A - Agent management method of the matching device using community field - Google Patents

Abstract

PURPOSE: Agent management method of the matching device using a community field uses a proxy agent if a simple network management protocol version one is used in a network management system, and maintains a proxy agent of SNMPV1 being a matching device by using a community field. CONSTITUTION: In the agent management method, SNMP management system transmits (S1)a data requesting a management of a network element to a matching device. The matching device examines (S2) a community field of the requested data received from the SNMP management system. The matching device obtains (S3) an information of the network element to be managed by an examination result, and manages (S4) an information of the corresponding network element. Then, the management result data made by the matching device is transmitted (S5) to SNMP management system. Thereby, a load of a management system for a large-sized system can be distributed to the matching device.

Description

Agent Management Method of Matching Device Using Community

The present invention relates to the use of a proxy agent when using a simple network management protocol version one in a network management system. In particular, the present invention relates to a method for managing a SNMPV1 proxy agent, which is a matching device, by using a community field in a request data field.

1 is a management model diagram between a conventional SNMP management system 10 and network elements 60, 70, 80 and 90 in which a management information base is mounted. As shown, a standard management information base is used between the SNMP management system 10 and the matching device 110. In order to use a standard management information base, each network element 60, 70, 80, 90 has a matching device processor 60, 70, 80, 90 rotated. Thus, the SNMP management system 10 directly manages each network element.

2 is a management model diagram between a matching device 110 and a network element 120, 130, 140, 150, which implement a conventional SNMP management system 100 and a newly defined management information base. . As shown, a management information base suitable for the system model to be managed between the SNMP management system 100 and the matching device 110 is designed. Then, the matching device 110 is placed to use SNMP or an internal communication protocol between the matching device 110 and the network elements 120, 130, 140, and 150. In addition, the matching device processor 110 is rotated to the matching device. Thus, the SNMP management system 100 indirectly manages each of the network elements 120, 130, 140, and 150.

1 has the advantage of using a standard management information base. However, there are cases where the size of the system to be managed is large. At this time, the number of network elements 60, 70, 80, 90 to be managed increases. Therefore, the number of matching devices 20, 30, 40, 50 that the SNMP management system 10 must manage also increases. Therefore, there is a problem that the system configuration is difficult and efficiency can be reduced.

On the other hand, FIG. 2 is effective in managing a complicated network by using the matching device 110. FIG. In addition, the load of the system can be distributed to the SNMP management system 100 and the matching device (110). However, the request of the SNMP management system 100 should be defined in advance in the management information base. This is because the request data of the protocol data unit (PDU) does not include information on which network element 120, 130, 140, or 150 the matching device 110 manages. . Therefore, there is a problem that the standard management information base cannot be used.

The present invention has been made to solve the problems of the prior art operating as described above, to compensate for the shortcomings of the existing SNMP by enabling the use of a matching device and a standard management information base to reduce the load on the management system It provides a method of managing agents of matching devices using a community by using a community function in the request data and using a matching device and using a standard management information base. It aims to do it.

Other objects and advantages of the present invention will become more apparent from the following detailed description of the invention and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a management model diagram between a network management device in which a conventional SNMP management system and a management information base are mounted.

2 is a management model diagram between a matching device and a network element on which a conventional SNMP management system and a newly defined management information base are mounted;

3 is a management model diagram between a matching device and a network element equipped with an SNMP management system and a standard management information base according to the present invention;

4 is a block diagram illustrating an agent management method of a matching device using a community according to the present invention;

5 is a flowchart illustrating an agent management method of a matching device using a community according to the present invention.

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

10,100,200: Simple Network Management Protocol (SNMP) management system

20,30,40,50,110,210: matching device

60,70,80,90,120,130,140,150,220,230,240,250: network elements

A preferred embodiment of the agent management method of the matching device using the community according to the present invention, which was created to achieve the object as described above, the network elements 220, 230, 240, 250 and a plurality of networks Network devices 220, 230, 240, 250 are managed through the matching device 210, the matching device 210 connecting the devices 220, 230, 240, 250 to the management system. In the SNMP management system 200,

Sending, by the SNMP management system 200, the data requesting management of the network elements 220, 230, 240, 202 to the matching device 210;

Of the request data received from the SNMP management system 200 by the matching device 210 +

Examining the community field;

Obtaining information of network elements 220, 230, 240, 250 to be managed according to the results of the matching device 210;

Managing, by the matching device 210, information of the corresponding network elements 220, 230, 240, 250; And

And sending the management result data generated by the matching device 210 to the SNMP management system 200.

In an embodiment of the present invention, the SNMP management system 200 to send the data requesting the management of the network elements 220, 230, 240, 250 to the matching device, SNMP management system 200 And configuring a community value and a network element 220, 230, 240, 250 information table that holds information of the network managed by the matching device 210 in the matching device 210. ,

When the matching device 210 examines the community field among the request data received from the SNMP management system 200, if the checked value has the same value among the contents of the table owned by the matching device 210, the request is made. Accepting the data as a valid value;

If the examined value does not have the same value among the contents of the table owned by the matching device 210, it is preferable to determine the requested data as an invalid value and to perform no operation.

The step of managing the information of the network elements 220, 230, 240, and 250 by the matching device 210 may be performed when the matching device 210 receives the valid request data. 230 and 240 and 250, it is preferable to perform a proper management action,

In the step of sending the management result data generated by the matching device 210 to the SNMP management system 200, the matching device 210 generates the management result data with a community field of the request data to the SNMP management system 200. It is preferable to make it a sending step.

In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

3 is a management model diagram between a matching device 210 and network elements 220, 230, 240, 250, which are equipped with an SNMP management system 200 and a standard management information base according to the present invention. 4 is a block diagram illustrating an agent management method of a matching device using a community according to the present invention. 5 is a flowchart illustrating an agent management method of a matching device using a community according to the present invention.

The SNMP management system 200 and the matching device 210 form a table having information of the network elements 220, 230, 240, and 250 managed by the matching device 210. Then, management is performed based on the configured information table. The matching device 210 examines the community field from the request data received from the SNMP management system 200. The result of this investigation may be the same in the contents of the owning table. If it is the same, this request data is accepted as a valid value. In addition, appropriate management actions are performed with the corresponding network elements 220, 230, 240, and 250. After administration, there may not be a match in the contents of the table. If no match is found, the request data is considered invalid. And no action is taken. Upon receiving valid request data, the matching device 210 performs appropriate management actions with the corresponding network elements 220, 230, 240 and 250, and then the matching device 210 generates management result data. Then, the management result data to the SNMP management system 200 is informed.

Hereinafter, with reference to the accompanying drawings will be described in detail the operating principle of the preferred embodiment of the present invention.

As shown in FIGS. 4 and 5, the matching device 210 has information of the network elements 220, 230, 240, 250 that need to be managed. This information refers to the Internet Protocol (IP), system information, and system ID (Identifiaction). The matching device 210 has a community value corresponding to the information of the network elements 220, 230, 240, and 250 in the form of a table (S1). When the matching device 210 receives the request data from the SNMP management system 200 (S1), the matching device 210 displays the community field, the community value, and the network elements 220, 230, and 240 in the data field. (250) Compare the information table. The matching device 210 checks the existence of the compared value (S2). If the community value does not exist in the table at this time, the request data is determined to be an invalid value (S2). The matching device 210 discards the request data without performing any operation (S3). On the other hand, if the community value is present in the table, the matching device 210 obtains information about the corresponding network elements 220, 230, 240, 250 (S3). After obtaining the information, appropriate management actions are performed according to the request data of the network elements 220, 230, 240, 250 and the SNMP management system 200 (S4). After the management act, the matching device 210 creates the management result data (S5). Then, the management result data to the SNMP management system 200 is informed (S5).

The present invention can be variously modified and can take various forms and only the specific embodiments thereof are described in the detailed description of the invention. It is to be understood, however, that the present invention is not limited to the specific forms mentioned in the detailed description of the invention, but rather includes all modifications, equivalents, and substitutions within the spirit and scope of the invention as defined by the appended claims. It should be understood to do.

In the present invention operating as described above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

You can also use a standard management information base while implementing proxy matching. In addition, the most effective effect is that the load of the management system managing a large system can be distributed to the matching device by adopting an indirect management method using the matching device. In addition, since the existing well-formed management information base can be easily applied to other systems, it is expected that the recycling of the management information base becomes easy.

Claims (5)

In the matching device connecting the network elements and a plurality of network elements to the management system, SNMP management system for managing the network elements through the matching device, Sending, by the SNMP management system, data for requesting management of the network element to the matching device; Examining, by the matching device, a community field of request data received from the SNMP management system; Obtaining information of a network element to be managed according to the result of the surveying of the matching device; Managing, by the matching device, information of the corresponding network element; And Sending the management result data generated by the matching device to the SNMP management system, Agent management method of the matching device using the community. The method of claim 1, wherein the SNMP management system sends the data requesting management of the network elements to the matching device, wherein the SNMP management system and the matching device have a community value that holds information of a network managed by the matching device. Comprising a step of configuring a network element information table, Agent management method of the matching device using the community. The method of claim 1, wherein the matching device examines a community field among request data received from an SNMP management system, and if the checked value has the same value among the contents of a table owned by the matching device, the request data is valid. Acknowledging the value; If the checked value does not have the same value among the contents of the table owned by the matching device, the method further comprises the step of judging the request data as an invalid value and performing no action. . The method of claim 1, wherein managing the information of the network element by the matching device includes performing proper management action with the corresponding network element when the matching device receives valid request data. Agent management method of matching device. The method of claim 1, wherein the sending of the management result data generated by the matching device to the SNMP management system comprises: generating, by the matching device, a management result data with a community field of request data, and sending the management result data to the SNMP management system. Agent management method of matching device using community.