KR100423634B1 - CORBA-SNMP Trap Server - Google Patents

Abstract

The present invention relates to a CORBA-SNMP trap server to perform efficient network equipment integration management through the CORBA interface (Interface) to handle the failure of heterogeneous network equipment, and to control the operation / control of the equipment An SNMP agent having a local database, which manages the status or history of equipment, collects and manages system faults, and generates a fault message when a fault occurs; An SNMP trap server for assigning data from a failure message received through the SNMP from the SNMP agent to a CORBA object method or variable defined by IDL; By including a user interface for outputting a failure message received through the CORBA interface from the SNMP trap server in a real-time graphic form, to reduce the complexity in interworking between heterogeneous networks can have the advantage of distributed processing In addition, since it can be applied to all network management equipment communicating with CORBA, the time and cost for developing integrated network management service in communication network management and interworking function between different management technologies can be greatly improved.

Description

CIOBA-SNMP Trap Server {CORBA-SNMP Trap Server}

The present invention relates to a CORBA-SNMP trap server, and more particularly to a CORBA-SNMP trap server to perform efficient network equipment integration management through the CORBA interface (Interface) to handle the failure of heterogeneous network equipment.

SNMP is a way to manage the transmission equipment and terminal devices manufactured by various manufacturing companies connected to the network in a standard way and minimize the cost required to implement them.

In addition, network management consists of elements such as failure management, configuration management, account management, performance management, and security management. To satisfy these factors, OSI (Open System Interconnection) proposes the Common Management Information Protocol (CMIP). However, compared to the provision of various functions, the application of SNMP, which reduces functions and costs due to cost, is spreading.

In the related art, only the individual network management through SNMP between the EMS providing the distributed environment and the ATM equipment that does not provide the distributed environment is performed.

In addition, structures currently proposed as communication network management technologies are implemented with various technologies such as TMN (Telecommunication Management Network), SNMP, CORBA, and Web (Web) to manage various information communication networks.

Although these various network management technologies are easy to manage individual network elements individually, the time required for developing comprehensive management services and interworking functions between different management technologies in terms of communication network management of the integrated network in terms of communication network management. And the cost is great.

In addition, as the network environment becomes more complex, it is necessary to implement a management system that integrates communication element devices of different management systems. CORBA has many advantages in this regard. Therefore, the distributed environment in which the majority of people provide the communication foundation between EMS components is based on CORBA standardization in OMG (Object Management Group).

In other words, in order to integrate current heterogeneous network management technology, the work of proposing and standardizing a distributed environment-based system is in progress. One of them is based on CORBA standardized by OMG.

The CORBA interoperates with heterogeneous network management technologies, reducing the complexity of function implementation and having the benefits of distributed processing.

However, since most existing network devices do not provide a distributed environment, therefore, in order to integrate and manage existing network devices in a distributed environment, data from messages received from the existing network management protocols CMIP and SNMP may be stored in methods or methods of CORBA objects. By assigning it to a variable, you need a gateway to pass the data to a remote server.

That is, CORBA-SNMP gateway that can interface with CORBA, middle-ware for interworking existing network equipment that does not provide distributed environment with EMS in distributed environment, that is, middle-ware for managing heterogeneous network equipment. There was a need for additional functionality.

As described above, to solve the conventional needs, the present invention implements a CORBA-SNMP trap server for handling the failure of heterogeneous network equipment, it is possible to efficiently manage the integrated network equipment through CORBA interface in a distributed environment It has a purpose.

In addition, the present invention by applying a CORBA-SNMP trap server, that is, a CORBA interface capable SNMP trap server for effective failure management while having an interworking function between EMS and ATM switching equipment failure of ATM switching equipment managed through SNMP The purpose of this is to manage the management efficiently in terms of integrated network management that provides a distributed environment.

In addition, the present invention is to design and implement a gateway called CORBA-SNMP trap server between EMS and ATM switching equipment in order to manage ATM switching equipment that does not provide a distributed environment in a distributed environment of the integrated network management level, heterogeneous network equipment Its purpose is to ensure efficient and economical management of disability.

In addition, the present invention enables the CORBA interface in terms of integrated network management as well as individual network management through SNMP between the EMS and ATM equipment, thereby enabling heterogeneous management of heterogeneous network equipment in a distributed environment including ATM switching equipment. By doing so, it is not only a trap server for fault management of ATM switching equipment, but also applied to configuration management, account management, performance management, etc. which are main functions of EMS.

1 is a block diagram illustrating a common object request broker architecture (CORBA) -simple network management protocol (SNMP) trap server according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a procedure for creating a connectionless communication program between an SNMP agent and an SNMP trap server in FIG. 1. FIG.

3 is a block diagram showing the structure of an SNMP trap server in FIG.

FIG. 4 illustrates variables obtained from an object instance in FIG. 3 as an example. FIG.

FIG. 5 is a diagram illustrating an Interface Definition Language (IDL) defined in an SNMP trap server in FIG. 3 as an example; FIG.

Explanation of symbols on the main parts of the drawings

10: SNMP Agent 11: Database

12: Trap Sender 20: SNMP Trap Server

21: Trap Handler 21-1: Trap Receiver

21-2: Start Daemon 22: Trap Reporter

22-1: Start Trap Processing

22-2: Trap Processing

23: Trap Processor

23-1: mapping control unit 23-2: packing control unit

23-3: Unpacking control unit 24; FIFO (First In First Out)

30: user interface

31: CORBA Server

32: user interface trap receiver

40: ATM (Asynchronous Transfer Mode) Switching Equipment

41: EMS (Element Management System)

CORBA-SNMP trap server according to an embodiment of the present invention for achieving the object as described above has a local database of variables that affect the operation / control of the equipment, manages the status or history of the equipment and failure of the system An SNMP agent that collects and manages and generates a failure message when a failure occurs; An SNMP trap server for assigning data from a failure message received through the SNMP from the SNMP agent to a CORBA object method or variable defined by IDL; It characterized in that it comprises a user interface for outputting a failure message received through the CORBA interface from the SNMP trap server in real-time graphical form.

The present invention designs and implements a CORBA-SNMP trap server for interfacing with EMS that provides a CORBA interface under effective fault management and distributed environment of ATM switching equipment. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing the overall structure of the CORBA-SNMP trap server between the EMS and ATM switching equipment.

CORBA-SNMP trap server according to an embodiment of the present invention can be divided into three parts, as shown in Figure 1, SNMP agent 10, SNMP trap server 20, the user interface 30 It is made to include.

The SNMP agent 10 is implemented in the ATM switching equipment 40, and has a local database 11 of variables that manage the status or history of the equipment and affect the operation / control of the equipment. The trap transmitter 12 is provided to collect and manage system failures, and generate a failure message when a system failure occurs and transmit the failure message to the SNMP trap server 20 through SNMP.

The SNMP trap server 20 includes a trap handler 21 and a trap reporter 22 in the EMS 50. The SNMP trap server 20 stores a failure message received through the SNMP from the SNMP agent 10 and receives the corresponding message. The data from the fault message is assigned to a CORBA object method or variable defined by IDL and transmitted to the user interface 30 where the CORBA server 31 is located through the CORBA interface.

The user interface 30 is implemented in the EMS 50 with a CORBA server 31 including a user interface trap receiver 32, which provides a real-time fault message received from the SNMP trap server 20 via the CORBA interface. Output in graphical form.

First, looking at the SNMP agent 10 in more detail, it corresponds to the network equipment, that is, ATM switching equipment 40 side and performs communication with the upper EMS system 50 through SNMP, mainly the state of the equipment (B) an agent who manages histories and is equipped with a regional database 11 of variables that affect the operation / control of equipment.

Basically, the communication with the SNMP trap server 20 performs socket communication using the User Datagram Protocol (UDP). The SNMP trap server 20 initially performs a socket daemon while a trap daemon program is executed. Open and send and receive a trap message with the SNMP agent 10 through the socket.

In this case, the SNMP agent 10 performs communication using UDP, which is a connectionless service, and serves as a client in terms of a client and a server.

2 shows a procedure for creating a connectionless communication program between the SNMP agent 10 and the SNMP trap server 20.

As shown in FIG. 2, each of the SNMP agent 10 and the SNMP trap server 20 opens a socket using a socket function (for example, socket ()), which is a function of opening a socket to be connected at the time of data transmission and reception. Connect the network using the bind function (e.g. bind ()), which is a function that connects the socket to the network.

In addition, the SNMP trap server 20 notifies the SNMP agent 10 that it is ready to receive a trap message using a data transmission / reception function (eg, sendto (), recvfrom ()).

Thereafter, the SNMP agent 10 transmits a trap message to the SNMP trap server 20 by using a data transmission / reception function (for example, sendto (), recvfrom ()) when a failure occurs in the equipment.

Secondly, the SNMP trap server 20 serving as a server from the client and server side can be well understood with reference to FIG. 3, which is a block diagram showing the structure of the SNMP trap server 20. to be.

The SNMP trap server 20 receives a trap message from the ATM switching device 40 through SNMP, performs a mapping process, and then packages the message in bytes to record the file as a file. Reads from the corresponding file, and unpacking by byte unit, and assigns a value to the method and parameter defined by IDL to the user interface 30 through the CORBA interface. It comprises a trap reporter 22 for transmitting.

In addition to the trap handler 21 and the trap reporter 22, the SNMP trap server 20 controls to map the trap message received through the corresponding trap handler 21 to a format defined by IDL, and records and reads a file. In order to control packing and unpacking, a FIFO which stores a file recorded by the trap handler 21 on a first-in-first-out basis and outputs it to the trap reporter 22, 24) further comprises. Here, it can be seen that there is a thread unit processor in one daemon processor.

The trap handler 21 monitors whether an input / output change has occurred in a currently open socket, and receives a trap message 21-1 that receives a trap message from the SNMP agent 10 and the received trap message. After the mapping process is performed, the message is packed in bytes and includes a daemon starter 21-2 for recording the file into a file.

The trap reporter 22 is a trap processing starter 22-1 that reads a trap message recorded in the FIFO 24, a method and a parameter defined by IDL after unpacking by byte unit. And a trap processing unit 22-2 which transmits a failure message to the user interface 30 through a CORBA interface by assigning a value to a variable.

The trap processor 23 may include a mapping controller 23-1 for controlling a mapping process of the trap handler 21, a packing controller 23-2 for controlling a packing operation of the trap handler 21, And an unpacking control unit 23-3 for controlling the unpacking operation of the trap reporter 22.

First, the trap handler 21 opens a socket to receive a trap message received from the SNMP agent 10 through SNMP, and includes the returned socket number and the IP address and port number of the EMS 50. Create a socket address structure (for example, sockaddr_in) and associate it with each other by calling a bind function (for example, bind ()).

In this case, the bind function (for example, bind ()) is called because the socket number is a communication window known to the application and the socket address is an address known to the network system. This is because trap messages can be passed between systems.

Then, the trap handler 21 is a signal for notifying that it is ready to receive a trap message from the SNMP agent 10 and sends a transmission function (for example, sendto ()) to the IP address of the EMS 50 and After sending the packet to the SNMP agent 10 by carrying the port number, the trap receiver 21-1 provided therein is driven.

Accordingly, the trap receiver 21-1 monitors whether an I / O change has occurred in a currently open socket using a select function (eg, a select ()) system call. In this case, when the I / O change is detected, the SNMP agent ( Since the trap message is received from 10), the trap message is received using a receiving function (eg, recvfrom ()).

At this time, the trap message is composed of a trap ID (trapid) indicating the type of failure, an object instance (oi) indicating an instance of a specific object managed by the equipment, and an object value (ov) indicating a value of the corresponding instance. have.

Then, the trap message is recorded in a specific byte unit in a file having a FIFO 24 structure, in which a trap ID, an object instance oi, and an object value ov are not directly written to the file. Instead, the object instance (oi) is properly mapped to a form that can identify the fault location in the system.

4 is a diagram showing variables obtained from the object instance oi as an example, and these variables indicate a hardware configuration of the device.

Accordingly, the daemon starter 21-2 of the trap handler 21 packs the message after the mapping process in units of bytes and records the message in a file in the FIFO 24.

The above operation is a task performed by the trap handler 21 which is a daemon processor of the SNMP trap server 20.

Next, the trap reporter 22 generated by the thread from the daemon processor will be described.

In the trap processing starter 22-1 provided in the trap reporter 22, the file is continuously read from the FIFO 24, and a trap message is sent from the trap handler 21 to the FIFO 24. If it is recorded in the trap message, the recorded trap message is read, and the trap processing unit 22-2 provided in the trap reporter 22 transmits the IDL to be transferred to the upper user interface 30 through the CORBA interface. Assign a value to the defined method and variable.

In this case, IDL used in CORBA refers to a language that defines an interface. Here, an interface is a kind of contract between two objects. In other words, if you request a service according to the method described in the interface, it will respond. The interface is purely declarative like JAVA's interface, not the code implemented.

To define these interfaces, CORBA uses IDL, which allows you to declare the services provided by the object and how to connect to them, so that the client knows how to access the server using that IDL. Interfaces declared in IDL can later be implemented by changing to a specific language.

In addition, the IDL is not dependent on a specific computer language or operating system. The IDL can be translated into various languages by using various IDL compilers, and the translated code makes it easy to implement a server and a client.

In summary, using an IDL-defined interface, an object tells its potential customers what methods they provide and how they can be invoked. Define a method and its parameters. 5 shows an IDL defined in the SNMP trap server 20 as an example.

The IDL includes a method and a parameter of the method, and the trap message received from the SNMP agent 10 by assigning a value obtained from the SNMP trap server 20 to the method and the parameter of the method. This can be delivered to the user interface 30 which is a higher interworking unit through the CORBA interface.

Since the present invention was developed around the SNMP agent and the SNMP trap server, the description has been made on the SNMP agent and the SNMP trap server without referring to a user interface that is a higher layer. However, the configuration description will be understood.

As described above, the present invention greatly reduces the time and cost required to develop an integrated network management service in terms of communication network management and the interworking function between different management technologies, rather than to manage individual network unit equipment individually. The developed CORBA-SNMP trap server can be linked in any network management scheme to communicate with CORBA.

As described above, according to the present invention, it is possible to reduce complexity in interworking between heterogeneous networks and to have advantages of distributed processing, and to be applicable to all network management equipment communicating with CORBA, so that the integrated network management service in terms of communication network management The time and cost of development and the development of interlocking functions between different management technologies can be greatly improved.

Claims (3)

An SNMP agent having a local database of variables influencing the operation / control of the equipment, managing the status or history of the equipment, collecting and managing the failures of the system, and generating a failure message when a failure occurs; An SNMP trap server for assigning data from a failure message received through the SNMP from the SNMP agent to a CORBA object method or variable defined by IDL; CB-SMPMP server characterized in that it comprises a user interface for outputting a failure message received from the SNMP trap server via the CORBA interface in real-time graphical form. The method of claim 1, The SNMP agent performs socket communication with the SNMP trap server using UDP, opens a socket using a socket function, connects a network using a bind function, and traps using a data transmission / reception function when a failure occurs. The RS-APN trap server, characterized in that for transmitting a message to the SNMP trap server. The method of claim 1, The SNMP trap server comprises: a trap handler for mapping a failure message received through the SNMP agent from the SNMP agent and packing the message in bytes to record the file as a file; A trap reporter that reads the file and performs unpacking on a byte basis, and then assigns a value to a method and a parameter defined by IDL to transmit a failure message to the user interface through a CORBA interface; A trap processor for controlling a mapping operation of the trap handler and controlling a packing and an unpacking operation for recording and reading a file; And a FIFO for storing the file recorded by the trap handler on a first-in, first-out basis, and outputting the file to the trap reporter.