KR100440059B1 - Controlling method for network management system using simple network management protocol - Google Patents

Abstract

The present invention relates to a method for controlling a network management system using a simple network management protocol (hereinafter, referred to as 'SNMP (Simple Network Management Protocol)'). A main management step of acquiring predetermined management information through an internal or sub-management subsystem and transferring the acquired management information to the management manager and transitioning to a waiting state for a next command after the process; When the SNMP message is input from the main management subsystem during the command waiting state, the management information obtained through a process of acquiring predetermined management information is transferred to the main management subsystem by transferring the management information acquired through a process of obtaining a predetermined management information to the main management subsystem and transitioning to a state waiting for the next command. By providing a method consisting of sub-management stages, the management system is reconfigured into sub-management subsystems that manage them by coordinating them for each independent system except the information to be commonly managed, and the main management subsystem that manages them consistently. This allows the system to accommodate the existing management areas provided by each system to access basic standard management information of the installed equipment and to access the management information provided separately, and to manage them as an integrated system as a whole. Efficiency of management, etc. There is.

Description

How to control network management system using simple network management protocol {CONTROLLING METHOD FOR NETWORK MANAGEMENT SYSTEM USING SIMPLE NETWORK MANAGEMENT PROTOCOL}

The present invention relates to a method for controlling a network management system using a simple network management protocol, and in particular, to integrate homogeneous network equipment (eg, workstation, printer, file server, router, switching equipment, etc.) SNMP management agent installed in each device when integrating devices (for example, network device and telephone network device) to manage based on simple network management protocol (hereinafter referred to as 'SNMP (Simple Network Management Protocol)') It relates to a network management system control method using SNMP to accommodate the functions and modules of the system.

Conventionally, the management of SNMP-based network equipment is composed of three parts. Firstly, the first is an SNMP management agent embedded in the managed device, and the second is an SNMP API (Application) to perform a management function remotely. As a management manager that includes a program interface and a user interface, these two nodes are connected to each other by an open system interconnect (ie, OSI (Open System Interconnection)) layer 7 of Transmission Control Protocol (TCP) / IP (Internet Protocol). ) Are interconnected using a user data protocol (hereinafter referred to as 'UDP (User Datagram Protocol)').

The third part consists of SNMP packets that carry management information executed by the management manager and flow between two nodes. The management manager and the agent are using a community of passwords to secure the management information between the two nodes. Only when the community is consistent with each other will the management function be performed.

In addition, by registering the address of the management manager to allow access as well as the community to the management agent can be allowed to perform only the management function to access from the registered address.

Currently, the majority of networked devices on the market are equipped with SNMP management agents in their devices, which are related to the Management Information Base (MIB-II) recommended by the Internet Technical Working Group (IETF) 's Internet Disclosure Document (RFC1213). Management information is basically supported, and in addition to the standard management information, each vendor provides additional management information according to the characteristics of the product. Therefore, using the general management manager and the general community that support SNMP, the SNMP management agent can check the basic standard management information of the device equipped with the SNMP management agent, but cannot access the management information provided separately.

In more detail, as shown in FIG. 1, the management manager 10 searches for and adjusts a management agent of the managed device 20, transmits management information to individual management agents, or manages a management object. There is a function that can change the operation of specific elements of the equipment 20, the SNMP management operation to perform such a function using the messages of 'GetReq', 'GetNetReq', 'SetReq' and 'Trap' Do this.

In addition, it includes five items for performing management functions. The first is the user interface, which uses icons, charts, graphs, etc. to quickly identify data trends of network equipment. read), and the second is the management application, which is responsible for interpreting the management information obtained from the management agent. The third is the database, which contains configuration, performance, failure, security, and billing information obtained from the management agent. The fourth is the SNMP engine, which exchanges SNMP messages and allows management agents access to management information, and the fifth is the transport protocol, which acts as a path for data communication over the actual network. do.

The management agent of the management target equipment 20 is a simple element, most of which is passive and is performed only under the control of the remote management manager 10. When only a predetermined failure occurs, the Trap is sent to the management manager as an active measure, and the management configuration is simple because the management configuration is simple by managing only a specific resource among network elements.

The management manager 10 stores an identifier (OID) of management information to be managed and a value to be managed in the SNMP protocol package (that is, the package includes community fields for minimal security). After receiving the packet, the management agent of the management target device 20 grasps the management information identifier, calls the corresponding function to obtain the management information, and then mounts it in the response message and transmits it to the management manager 10. .

Accordingly, the present invention has been made to solve the above-mentioned conventional problems, and a plurality of sub-management sub-systems for managing the group by performing the grouping for each independent system except the information to be commonly managed, and this sub-management Its purpose is to provide a way to have a main management subsystem that manages the subsystems consistently to accommodate the existing management areas provided by each system and to manage them as a single integrated system.

1 is an exemplary view briefly showing the configuration of a network management system using a conventional simple network management protocol.

Figure 2 is an exemplary view showing a brief configuration of a network management system using a simple network management protocol to apply the present invention.

3 is an exemplary view illustrating an operation process of a main management subsystem in FIG. 2.

4 is an exemplary view illustrating an operation process of a sub-management subsystem in FIG. 2.

********** Explanation of symbols for the main parts of the drawing **********

10: management manager 20: managed equipment

30: main management subsystem 40: sub-management subsystem

In accordance with another aspect of the present invention, a method for controlling a network management system using SNMP includes receiving a management information request from a management manager in a command waiting state, performing a predetermined access right authentication operation, and then performing a predetermined management. A main management step of acquiring the information through the internal or sub-management subsystem, transferring the management information to the management manager, and transitioning to a waiting state for the next command; The sub-administration receives an SNMP message from the main management subsystem in the command waiting state, obtains predetermined management information, transfers the management information to the main management subsystem by transferring the management information in the SNMP response message, and transitions to the state waiting for the next command. Characterized in that it comprises a step.

Preferably, the main management step receives a management information request from the management manager in the command waiting state, stores the SNMP message in a buffer, obtains IP and socket information of the management system from the corresponding message, A first step of performing community and access authority authentication using the header information; A second step of transmitting a non-implementation message to the management system IP or acquiring a destination identifier of management information from SNMP variable binding information according to the authentication result of the first step; A third step of comparing the destination identifier obtained in the second step with a destination identifier managed by the second user; Calling a function accessible to management information according to the comparison result of the third step to obtain management information or to determine which sub-management subsystem is a destination identifier managed by the sub-management subsystem; A fifth step of transmitting an SNMP message to the secondary management subsystem and waiting for a response according to the determination result of the fourth step; And a sixth step of receiving a response message from the sub-management sub-system after performing the fifth step, transmitting the management information contained in the response message to the management manager, and then transitioning to a waiting state for the next command. It is characterized by.

Also preferably, the sub-administration step obtains an SNMP message transmitted from the main management subsystem from the message queue in the command waiting state and stores the SNMP message in a buffer and then obtains a destination identifier of management information from the SNMP variable binding information. A first step; A second step of calling a function corresponding to the destination identifier obtained in the first step and then obtaining management information according to the function; And a third step of embedding the management information obtained in the second step into an SNMP response message, transmitting the internal management module to the main management subsystem through the internal communication module, and transitioning to a waiting state for the next command.

Hereinafter, an operation process of an embodiment according to the present invention will be described with reference to the accompanying drawings.

FIG. 2 is an exemplary view briefly illustrating a configuration of a network management system using SNMP to which the present invention is applied. The configuration is illustrated in FIG. 2 and has a unique interface with the management manager 10 for consistency of system management. A main management subsystem 30 that performs and manages and maintains all management information located on a protocol stack or a device of each sub-management subsystem 40; Except the information to be managed in common, a plurality of sub-management subsystems 40 are managed to perform grouping for each independent system and manage the same.

In addition, the transmission of a message (ie, management information) between the management manager 10 and the main management subsystem 30 uses UDP socket communication, and between the main management subsystem 30 and the sub management subsystem 40. Management information of board uses board-to-board communication module such as 'X-BUS'.

Referring to the operation of the embodiment according to the present invention configured as described above are as follows.

3 is an exemplary view illustrating an operation process of the main management subsystem in FIG. 2, and FIG. 4 is an exemplary diagram illustrating an operation process of the sub management subsystem in FIG. 2. The master management subsystem 30 receives a UDP socket (for example, a well-known port 161) from the management manager 10 and sends a management information request and an SNMP message from the management manager 10 in a command waiting state S10. After receiving the received through the SNMP message in the buffer (not shown in the drawing for convenience of description) (S11), to obtain the IP and socket information of the management system from the stored message (S12) header information of the message Acquire the community information in and performs the access authority accordingly (S13).

As a result of the authentication (S14), if the authentication fails, and transmits a message that can not be performed to the management system IP obtained above (S15), and transitions to the state waiting for the next command (S21), if the authentication is successful In step S16, a destination identifier (OID) of management information is obtained from SNMP variable binding information.

Thereafter, the obtained destination identifier (OID) is compared with the destination identifier (OID) managed by the user (S17). If the result of the comparison is the same, common management information is requested. 30) by calling a function that can access the management information stored in the control to obtain the management information by the function and transmits to the management manager 10 (S18), in other cases to request information to be managed separately By judging and determining which sub-management subsystem 40 is managed by the destination identifier (OID) (S19), when integrating management information for effective determination, grouping the destination identifiers (OID) for each subsystem in succession ( Sequentially, the allocation information is stored in advance in the main management subsystem 30.

According to the determination result, the sub-management subsystem 40 transmits an SNMP message and waits for a response. The sub-management subsystem 40 shows the main management sub in the command waiting state S30 as shown in FIG. 4. After receiving the SNMP message transmitted from the system 30 from the message queue and storing it in a buffer (not shown in the drawing for convenience of description) (S31), the destination identifier (OID) of the management information in the SNMP variable binding information. In this case, the sub-administration subsystem 40 omits a new authentication procedure because the sub-management subsystem 40 has already performed an authentication procedure according to the community in the main management subsystem 30.

Thereafter, after calling the function by the obtained destination identifier (OID), the management information is obtained according to the called function (S33), and the management information is loaded into the SNMP response message to internal communication. After transmitting to the main management subsystem 30 through a module (eg, 'X-BUS') (S34), the process transitions to a waiting state (S35).

Then, the main management subsystem 30 receives the response message from the sub-management subsystem 40 and transmits the management information contained in the response message to the management manager 10 (S20), the next command Transition to the waiting state (S21).

As described above, the method for controlling a network management system using SNMP according to the present invention performs grouping for each independent system except for information to be managed in common, and manages them consistently with sub-management subsystems managing the same. By reconfiguring the management system into management subsystems, the existing management areas provided by each system can be accommodated to identify basic standard management information of the installed equipment and to access management information provided individually, and integrated as a whole. By managing in one system, there is an effect of increasing the efficiency of management.

Claims (3)

After receiving a request for management information from a management manager in a command waiting state, performing a predetermined access authority authentication operation, acquiring predetermined management information through an internal or sub-management subsystem, and transmitting the management information to the corresponding management manager. A main management step of transitioning to a waiting state for a command; In the standby state of the command receives a Simple Network Management Protocol (SNMP) message from the main management subsystem, obtains predetermined management information, transfers the management information in the SNMP response message to the corresponding main management subsystem, and waits for the next command. A method for controlling a network management system using a simple network management protocol comprising a sub-management step of transitioning to a state. The method of claim 1, The main management step receives a management information request from the management manager in the command waiting state, stores the SNMP message in a buffer, obtains IP (Internet Protocol) and socket information of a management system from the message, and A first step of performing community and access authority authentication using the header information; A second step of transmitting a non-implementation message to the management system IP or acquiring a destination identifier of management information from SNMP variable binding information according to the authentication result of the first step; A third step of comparing the destination identifier obtained in the second step with a destination identifier managed by the second user; Calling a function accessible to management information according to the comparison result of the third step to obtain management information or to determine which sub-management subsystem is a destination identifier managed by the sub-management subsystem; A fifth step of transmitting an SNMP message to the secondary management subsystem and waiting for a response according to the determination result of the fourth step; And a sixth step of receiving a response message from the sub-management sub-system after performing the fifth step, transmitting the management information contained in the response message to the management manager, and then transitioning to a waiting state for the next command. Network management system control method using a simple network management protocol, characterized in that. The method of claim 1, The sub-management step may include: a first step of acquiring an SNMP message transmitted from the main management subsystem from a message queue in a command waiting state and storing the SNMP message in a buffer, and then obtaining a destination identifier of management information from SNMP variable binding information; A second step of calling a function corresponding to the destination identifier obtained in the first step and then obtaining management information according to the function; And a third step of embedding the management information obtained in the second step into an SNMP response message to transmit to the main management subsystem through an internal communication module and to transition to a waiting state for the next command. Network management system control method using network management protocol.