KR100258220B1 - Enhanced snmp agent/manager scheme in multi module system - Google Patents

Abstract

PURPOSE: A method for embodying an agent/manager of a simple network management protocol in a multiple module system is provided to use a system resource efficiently by distributing a registration information to each module. CONSTITUTION: A network management system is connected to a main module. At this time, the main module plays a role as a routing. The main module playing a role as the routing transmits a request to a master agent of each module. At this time, the request is transmitted by the network management system. Each module has an IP address, the IP address is discriminated through an index of an object ID located at each module. A standard management information base is supported by appointing a fixed port of each module having an only port number without a slot number.

Description

Efficient Simple Network Management Protocol Agent / Manager Implementation on Multi-Module System

The present invention relates to a method for implementing an effective Simple Network Management Protocol (SNMP) agent / manager in a multi-module system, in particular, a master / sub ( Sub) The present invention relates to a method for effectively supporting a simple network management protocol standard (MIB) management information base (MIB) in a system composed of agents.

In general, a network management system (NMS), which is generally used to manage a large network and a network element (NE) on the network, manages information of a network element through a simple network management protocol. Is common.

At this time, the information to be managed is called the management information base, and the network element has standard management information bases (MIB-I, MIB-II, etc.) that standardize the information that universal systems should have.

Currently, network elements that support simple network management protocols support standardized standard management information bases so that network management systems that need to manage many different network elements can manage them efficiently.

However, since the standard management information base is made based on a simple modular system existing on a LAN, it has a problem that is difficult to use in a multi-module system.

1 is a configuration diagram of a system using a conventional master / sub agent. In the case of the system as shown in FIG. 1, an object ID (OID), which is an information unit inside the system, is composed of a slot number and a port number. Index). In addition, as shown in FIG. 1, in a multi-module system using a master / sub agent, the master agent needs to have a slot and a port index in index units to efficiently identify all managed objects.

However, the standard management information base usually has only one index defined, which makes it difficult to support the standard management information base in a multi-module system.

Accordingly, the present invention was devised to solve the above problems, and in order to efficiently support a standard management information base in a multi-module system, a master agent is placed on all modules without using a master / sub agent method. It aims to provide a way to easily support the standard management information base and to make each management method more efficient.

1 is a block diagram of a system using a conventional master / sub agent.

2 is a block diagram illustrating an implementation of an efficient simple network management protocol agent / manager on a multi-module system in accordance with the present invention.

3 is a configuration diagram of a system using only a master agent according to the present invention;

4 is a registration table in the case where the number of slots is fifteen.

5 is a process diagram when a new module is mounted.

An embodiment of an efficient simple network management protocol agent / manager implementation method in a multi-module system according to the present invention, which was devised to achieve the above object,

In order to efficiently implement a simple network management protocol in a multi-module system, each module is equipped with a master agent to operate the master agent in all modules, thereby receiving and processing request information from a network management system.

In the present invention, the network management system is connected only to the main module of the network element, but the main module preferably performs only a role of routing,

By performing the routing function in the main module, it is preferable to send a request from the network management system directly to the master agent existing in each module, and process the received request directly to the network management system.

Since each module has a unique IP address, it is preferable to distinguish the IP address by the index of the object ID located in each module.

It is desirable to support a standard management information base by specifying a specific port for each module with only a port number without a slot number.

According to another embodiment of the present invention, in order to efficiently read the next function in each distributed master agent, management information base registration information is provided in each module to perform the next function between master agents.

In the present invention, the method of using registration,

Registering a management information base used by the module and an IP address of a module using the management information base in the table;

Requesting a next read request for an object ID in its module;

Responding to the management information base of the requested module to complete next-indexing;

Searching the registration table and sending the next read request to the next registered module;

It may be desirable to include a process that enables subsequent read requests across multiple modules,

The information to be registered in the registration table is preferably the same object ID, a table number and an IP address in binary, meaning each slot number.

Each module should use only the data it needs through a masking process.

In order to efficiently read the next function in each distributed master agent, it is desirable to set the management information base property in each module to enable the next function between the master agents.

Another embodiment of the present invention includes a process of creating a basic registration table through a batch file which each module reads at initialization to match the management information registration information held by each module.

In the present invention, when a new module is newly mounted,

New module alive reporting to another existing module;

Sending a registration request to a new module if the other existing module is not a registered management information base;

The new module sending a registration table response to the other existing module.

In the present invention, when a module is dismounted or rescheduled, the main module (or each module) that has received a hardware interrupt generates a module release report to change the masking of the corresponding module to skip the dismounted module at the next function. It is preferable.

In order to implement a simple network management protocol in a multi-module system, instead of using the master / sub agent method, instead, the master agent is put on all modules, and the main module merely plays the role of routing, thereby reducing the number of indexes. One can be reduced.

In order to efficiently perform the Get Next Function in each distributed master agent, management information base registration information is provided in each module to enable the next function between master agents.

We present a method to match the management information properties of each module.

-Use only master agent

The network element is equipped with a master agent in each module to operate the master agent in all modules to receive and process request information from the network management system.

As shown in FIG. 3, the network management system is only connected to the main module of the network element, but by performing a routing function in the main module, a request from the network management system can be directly sent to the master agent present in each module and received. Can be processed and sent directly to the network management system. Each module has a unique IP address, which is an index of an object ID located in each module, which can be distinguished by an IP address instead of a slot number. Having a port number, which requires a slot number and a port number, allows you to specify a specific port for each module, supporting a standard management information base.

-Only support reading next function on master agent

When using a master / sub agent, if each module makes a Get Next Request, when more than one module of the same type exists, the next read request can be made to another module (by changing the slot index). Since only the master agent can be used to change the index and send a request to another module, a method using registration is presented.

Each module has a registration table and registers the management information base that it uses and the IP address of the module that uses that management information base. After indexing, the next read request is made available through several modules by searching the registration table and sending the next read request to the next module.

At this time, the information to be registered in the registration table is shown in FIG. 4. In the case of FIG. 4, the same object ID is registered. If the next read request is requested for this object ID, after responding to the management information base of the requested module, the next read request is sent to other modules registered in the registration table, and the other module receiving the same process proceeds in the same manner. . At this time, each module keeps a few more previous registration information, and when the module ① is no longer used, it can reduce the time required to register the information of the module ② by using the information that it already has.

The numbers in the table represent the slot numbers in binary, and each module can use only the data it needs through a masking process.

Synchronization of the registration table existing on each module

Each module creates a basic registration table through a batch file (Config File) read at initialization. When a new module is newly implemented, the method as shown in FIG. 5 is used.

When a module is detached or reset, the main module (or each module) that has received a hardware interrupt (H / W Interrupt) generates a module release report to change the masking of the module so that it is removed during the next function. The module will be skipped.

The present invention operating as described above can effectively use a standard management information base in a multi-module system, and by distributing the centralized information registered in the master module to each module in the master / sub agent structure (System Resource) There is an effect that can be used efficiently.

Claims (13)

In order to efficiently implement a simple network management protocol in a multi-module system, a master agent is installed in each module to operate the master agent in all modules, thereby receiving and processing request information from a network management system. Efficient Simple Network Management Protocol Agent / Manager Implementation. 2. The method of claim 1 wherein the network management system is only connected to a main module of a network element but the main module only serves as a routing. The multi-module system of claim 1, wherein a request from a network management system is directly sent to a master agent present in each module by performing a routing function in the main module, and the received request is directly processed to a network management system. Implementation of an Efficient Simple Network Management Protocol Agent / Manager on the Internet. 2. The method of claim 1 wherein each module has a unique IP address to distinguish the IP address by an index of an object ID located in each module. 2. The method of claim 1, wherein a specific port of each module is designated with only a port number without a slot number to support a standard management information base. Efficient Simple Network Management Protocol Agent / Manager on Multi-Module Systems, By Putting Management Information Base Properties in Each Module to Perform the Next Function Reading on Each Distributed Master Agent Efficiently Method of implementation. 7. The method of claim 6 wherein the method of using registration is Registering a management information base used by the module and an IP address of a module using the management information base in the table; Requesting a next read request for an object ID in its module; Responding to the management information base of the requested module to complete next-indexing; Searching the registration table and sending the next read request to the next registered module; A method of implementing an efficient simple network management protocol agent / manager on a multi-module system, including the process of enabling subsequent read requests across multiple modules. 8. The efficient simple network management protocol in a multi-module system according to claim 7, wherein the information to be registered in the registration table includes the same object ID, a binary table number and an IP address registered for each slot number. How to implement an agent / manager. 7. The method of claim 6 wherein each module uses only the data it needs through a masking process. 7. The system of claim 6, wherein the next function between master agents is enabled by assigning management information base properties to each module to efficiently perform the next function read in each distributed master agent. How to implement a simple network management protocol agent / manager. An efficient simple network management protocol agent on a multi-module system, including the creation of a basic registration table from a batch file that each module reads at initialization to match the management information properties held by each module. How to implement / administrator. The method of claim 11, wherein when a new module is newly implemented, New module alive reporting to another existing module; Sending a registration request to a new module if the other existing module is not a registered management information base; And the new module sends a registration table response to the other existing module. 12. The module of claim 11, wherein if a module is detached or rescheduled, the main module (or each module) that has received a hardware interrupt generates a module release report to change the masking of that module to skip the module at the next function. A method of implementing an efficient simple network management protocol agent / manager on a multi-module system.

Images