KR100706948B1 - MIB Structure and Management in SNMP Manager - Google Patents

Abstract

The present invention distinguishes essential information and optional information among MIB data and manages them in a file format so that MIB configuration and management method can be used in an SNMP management system that MIB data can be commonly used in all applications without a separate compilation process. The present invention relates to a method for managing management information base (MIB) data in a network management system including a simple network management protocol (SNMP) manager system and an SNMP agent. A first step of dividing into optional information and storing each of them in a file form; A second step in which an application of the SNMP manager system opens a MIB data file storing the essential information and sets the first object as a root; Reading a next object, checking a depth of the object included in the essential information and an identifier of a higher object, and then adding an object name at a corresponding position; And a fourth step of repeating the third step for all objects.

SNMP, MIB, Management, Network, Simple, Protocol, Information, Base

Description

Management Information Base Configuration and Management Method in Simple Network Management Protocol System {MIB Structure and Management in SNMP Manager}             

1 is a diagram for explaining a relationship between a general SNMP manager system and an agent.

2 illustrates a structure of a MIB data file containing essential information according to the present invention.

3 illustrates a structure of a MIB data file containing optional information in accordance with the present invention.

4 is a view for explaining the relationship between a MIB data file containing essential information and a MIB data file containing optional information according to the present invention;

The present invention relates to a management information base (MIB) configuration and management method in a Simple Network Management Protocol (SNMP) Manager system, and more particularly, essential information and selection of MIB data. By classifying general information and managing them in a file format, the present invention relates to a MIB configuration and management method in which MIB data can be commonly used in all applications without a separate compilation process.

In general, SNMP is one of network management protocols for managing a communication network. An SNMP network management system, that is, a manager, may control resources in an SNMP network management target system, that is, an agent, through the corresponding SNMP.

1 is a diagram illustrating a relationship between a general SNMP manager system and an agent. The SNMP network management system includes an SNMP manager system, an SNMP agent, and MIB data.

The SNMP manager system provides an interface for network administrators to check the entire network status. SNMP agent is installed in network equipment such as host, router, bridge, and hub which are managed devices, and transmits management information according to the needs of the manager system, or retrieves, changes, creates, and deletes data required by the manager system. And so on. The MIB, which is management information, is a database containing information on the elements to be managed of each managed device in a system based on TCP / IP.

Conventionally, when a manager system is implemented using SNMP, a MIB browser is implemented for user convenience. The MIB browser is the one that shows the MIB tree structure. Such a MIB browser obtains MIB data by compiling a MIB file whose SNMP manager system is composed of Abstract Syntax Notation 1 (ASN.1) using the MIB compiler. The MIB data thus obtained are basic data for constructing the MIB browser. However, these MIB data are eventually configured depending on the MIB compiler or application.

If the MIB data is configured using different compilers (applications), since the MIB data is composed exclusively of each other, there is no common element to construct the MIB tree to be implemented through the MIB browser in different applications. That is, in the conventional MIB configuration, only one application must be used from the compiler to the implementation of the MIB browser, and there is a problem in that the MIB data that is already configured cannot be used in different applications. As a result, in order to use MIB data in other applications, it must be recompiled.

Accordingly, the present invention is to solve the above problems of the prior art, an object of the present invention, by separating the essential information and the optional information of the MIB data, and managing them in a file format, to separate the MIB data in all applications It is to provide MIB configuration and management method in SNMP management system that can be used in common without compiling process.

In order to achieve the above object, the present invention provides a method for managing management information base (MIB) data in a network management system including a simple network management protocol (SNMP) manager system and an SNMP agent. A first step of dividing the information into optional information and storing the information in a file format; A second step in which an application of the SNMP manager system opens a MIB data file storing the essential information and sets the first object as a root; Reading a next object, checking a depth of the object included in the essential information and an identifier of a higher object, and then adding an object name at a corresponding position; And a fourth step of repeating the third step for all objects.

Preferably, the file for storing the essential information and the file for storing the optional information are linked to each other using an object identifier as a key.

Also, preferably, the file storing the essential information may include an object identifier, an object name, an identifier of an upper object, a syntax indicating type information of the object, state information indicating whether the object is an essential element or an optional element, and Access permission information of the object, information indicating the depth of the object on the MIB browser, and whether the table of the object.

Also preferably, the file storing the optional information includes an object identifier, detailed description information about the object, and original data type information of the object.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 2 is a diagram showing a structure of a MIB data file containing essential information according to the present invention, FIG. 3 is a diagram showing a structure of a MIB data file containing optional information according to the present invention, and FIG. 4 is a diagram showing essential information according to the present invention. Is a diagram for explaining a relationship between a MIB data file containing information and a MIB data file containing optional information.

In the present invention, the format of the MIB data is adjusted to the file format. In other words, the basic elements used in the MIB browser are composed into a file, and then the MIB data is configured by reading MIB data for configuring the MIB browser from the file. These files, by default, give read access to any application, making it easy to implement a MIB browser. This will be described in more detail with reference to the accompanying drawings.

As shown in Fig. 2 and Fig. 3, the present invention divides and stores MIB data into a file including essential information and a file including optional information. Essential information in the MIB data refers to information necessary for constructing the MIB browser. Essential information for configuring MIB Browser among MIB data includes OID (Object ID), Object Name, Parent OID, Syntax, Status, Access, and Depth ( Depth), whether there is a table.

The OID is a unique identifier assigned to the object, and the object name is a unique name of the object. The upper OID indicates an identifier of the upper object of the object, and the upper OID corresponds to information for identifying the position of the object.

Syntax is the part that indicates the type of the object. It is information to find out what type of result you want when you want the result of the object. Status includes information for identifying whether the object is an essential element or an optional element. Access rights are information representing the access rights of the object. NA is not accessible and RO is only read. Depth is information representing the depth of the object in the MIB browser. By using the upper OID and the depth, the position of the object can be determined. Whether or not the table is information indicating whether the object is columnar information or scalar information.

Optional information of the MIB data is an item configured to run the MIB browser and provide additional information about the object, and this item includes the OID, description, and base syntax for the MIB object. Description is information containing detailed information about the object, and the base syntax indicates the original data type of the object.

The reason for separating the MIB file containing the essential information and the MIB file containing the optional information is to store only the information for representing the MIB browser in the file containing the essential information so that it can be shared by all applications. The file containing the optional information includes detailed description information about the object. Since the detailed description information has a long actual content, there is a problem in that the file is stored in one file.

Therefore, the MIB manager system divides the MIB data into essential information and optional information, stores them in a file format, and opens a file that stores only essential information to create a MIB browser.

The MIB file storing such essential information and the MIB file storing optional information are matched with each other using OID information as a key value as shown in FIG. That is, after generating a MIB browser using a MIB file storing essential information, if a detailed description of a specific object is requested, the description information of the object is retrieved using the OID information as a key.

A process of generating a MIB browser using such a MIB data file is described below.

First, MIB information delivered from each agent is composed of essential information and optional information and stored in each corresponding file.

The application opens the file that stores the essential information from the file that stores the MIB data and sets the first object as the root. Then, read the following object to check the depth and OID information of the parent object, and add the object name to the location. Read the object information and add the object name to the location for all the objects. The created MIB browser is displayed on the screen.

Although the above has been described with reference to the preferred embodiment according to the present invention, those skilled in the art to which the present invention pertains can be carried out by other specific forms of example without changing the technical spirit or essential features of the present invention. I can understand. Therefore, the embodiments described above are to be understood as illustrative and not restrictive in all aspects. That is, the scope of the present invention is shown by the claims below rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts are included in the scope of the present invention. Should be interpreted.

As described above, the present invention divides MIB data into essential information and optional information, stores them in a file form, and opens a file that stores essential information to generate a MIB browser, thereby sharing MIB data regardless of a compiler and an application. can do.

Claims (4)

A method for managing management information base (MIB) data in a network management system including a simple network management protocol (SNMP) manager system and an SNMP agent, A first step of dividing the generated MIB data into essential information and optional information and storing the generated MIB data in a file format; A second step in which an application of the SNMP manager system opens a MIB data file storing the essential information and sets the first object as a root; Reading a next object, checking a depth of the object included in the essential information and an identifier of a higher object, and then adding an object name at a corresponding position; And And a fourth step of repeating the third step for all objects. The method of claim 1, And the file storing the essential information and the file storing the optional information are linked to each other using an object identifier as a key. The method of claim 2, The file for storing the essential information includes an object identifier, an object name, an identifier of a parent object, a syntax indicating type information of the object, state information indicating whether the object is an essential element or an optional element, and access permission information of the object. , MIB configuration and management method comprising the information indicating the depth of the object on the MIB browser, whether the table of the object; The method of claim 3, wherein And the file storing the optional information includes an object identifier, detailed description information of the object, and original data type information of the object.

Images