KR100503826B1 - Xml/snmp gateway for integrated network management - Google Patents

Abstract

The XML / SNMP gateway according to the present invention converts the request and response messages transmitted and received for network management between the SNMP delegate and the XML manager embedded in the existing network management equipment to the MIB defined using SMI in SNMP-based network management. An XML converter for forming an XML schema corresponding to the corresponding XML schema and forming an XML document having the same structure as the MIB tree structure, a request processing module for analyzing the XML request message received from the XML manager and extracting an object node to be accessed; The XML parser extracts the XML schema, the XML document, and the OID information corresponding to the destination node, and the SNMP request message corresponding to the OID information extracted from the XML parser to the SNMP delegate. Receive SNMP response messages for SNMP request messages from delegates and send them to the XML parser It includes SNMP stack.

As described above, in the present invention, by converting MIB information of the SMI format for XML / SNMP gateway into XML schema that can be understood in XML-based network management without loss, the XML-based network management system and SNMP without changing the SNMP delegate It can provide flexibility between agents.

Description

GL / SNMP Gateway for Integrated Network Management {XML / SNMP GATEWAY FOR INTEGRATED NETWORK MANAGEMENT}

The present invention relates to an XML-based network management system, and more particularly, to an XML / SNMP gateway for XML-based network management that can overcome the scalability and efficiency of SNMP-based network management.

The Internet, which began to grow significantly with the development of the World Wide Web (WWW) in the late 1980s, formed a complex network of various network devices produced by various vendors. As a result, the importance of network management This increased.

Most of the network management for managing the Internet is based on the Simple Network Management Protocol (SNMP). SNMP is based on the manager-delegate structure, in which an administrator sends a management request to a delegate, who responds to the manager's request, performs a task on the managed object, and sends the result to the manager. The delegate automatically reports this to the manager when a specific event occurs.

In SNMP, protocols for communication between managers and delegates and methods for defining management information for management targets are defined as standards.

However, such SNMP-based network management has limitations in scalability and efficiency in managing the ever-growing huge network.

Recently, XML-based network management has emerged as an alternative to overcome the limitations of SNMP-based network management. XML-based network management is based on manager-delegate structure like SNMP. In XML-based network management, management information is defined as XML, and XML document format is used for exchanging management information between manager and delegate. For the processing of XML, various standard technologies for XML document processing are applied to suggest a more scalable management system structure. XML-based network management has the following advantages.

First, XML schema used for defining management information in XML-based network management provides more scalable modeling function in data type and structure of management information than SMI used for defining management information in SNMP. .

Second, using widely distributed protocols such as HTTP provides a more efficient and reliable communication method than SNMP.

Third, various management procedures such as analysis, storage, and presentation of management information required by the management system can be applied to XML such as XSLT (eXtensible Stylesheet Language Transformation), XPath or XQuery, and an XML-only database that provides an optimized storage method for XML documents. It can be easily developed using the relevant technology.

Fourth, higher-level management operation by integrating Web Services Description Language (WSDL) based on Simple Object Access Protocol (SOAP) and Universal Description Discovery and Integration (UDDI) system into a web service. The definition of is possible.

However, despite these many advantages, there are limitations in applying realistic XML-based network management. Given that many existing network devices are equipped with SNMP delegates, and most network devices that are produced now also have built-in SNMP delegates, it is necessary to manage all existing devices as XML-based administrators. You need to develop an additional XML-based delegate for your device, which is practically impossible.

SUMMARY OF THE INVENTION An object of the present invention is to solve the problems of the prior art, and provides a specification translation, which is a transformation for defining management information, and an interaction translation for requesting and delivering actual management information. The present invention relates to an XML / SNMP gateway for integrated network management.

In order to achieve the above object, the present invention, in the gateway for converting messages transmitted and received between the XML management unit and the SNMP delegate, storing the respective nodes included in the MIB managed by the SNMP delegate as a table, To form an XML schema having the same structure as that of the management information stored in the table, and to analyze and access an XML request message received from the XML manager and an XML converter for forming an XML document having the same structure as the MIB tree structure. A request processing module for extracting an object node; an XML parser for storing OID information corresponding to the object node; and an SNMP delegate corresponding to the OID information extracted from the XML parser. An SNMP request message to an SNMP request and an SNMP request message from the SNMP delegate. And an SNMP stack for receiving a response message and transmitting it to the XML parser, wherein the XML parser inputs MIB information to the destination node based on the SNMP response message to generate an XML document for the XML request message, and generates the XML message. The sent XML response message to the XML manager through the request processing module.

In addition, the present invention, in the gateway for converting messages sent to (received) to and from the SNMP delegate, each node included in the MIB managed by the SNMP delegate is stored in a table, the management information stored in the table An XML converter which forms an XML schema having the same structure as the structure, forms an XML document having the same structure as the MIB tree structure, an XML parser storing the XML schema and the XML document, and the XML parser Sends an SNMP request message to an XML manager that detects OID information of a target node corresponding to an XML request message and an SNMP delegate corresponding to the OID information, and receives an SNMP response message for an SNMP request message from the SNMP delegate. SNMP stacks that send to the parser and trap messages generated by the SNMP delegates according to predefined events A trap processing module configured to receive and reflect the contents of the received trap message in an XML document stored in the XML parser, and input MIB information to the destination node based on the SNMP response message through the XML parser. Generate a response message to the XML request message, and transmit the generated XML response message to the XML manager.

 In addition, the present invention, in the gateway including the HTTP server, in order to deliver a response message for the HTTP request message containing the expression for the query and modification of the XML document from the administrator, included in the MIB managed by the SNMP delegate An XML converter which stores nodes as a table, forms an XML schema having the same structure as that of the management information stored in the table, and forms an XML document having the same structure as the MIB tree structure, and the HTTP server. A request processing module for extracting the expression from the received HTTP request message, an expression processing module for searching for an object node based on the expression, the XML schema and an XML document, and storing OID information corresponding to the object node An XML parser to be extracted and an SNMP delegate corresponding to the OID information extracted from the XML parser. Receives an SNMP stack that transmits an SNMP request message, receives an SNMP response message for the SNMP request message from the SNMP delegate, and sends the SNMP stack, and a trap message generated by the SNMP delegate according to a predefined event occurrence. A trap processing module for reflecting the contents of the received trap message in an XML document stored in the XML parser, an XML document reflecting the contents of the trap message, and receiving the received XML document from the XML parser. And an HTTP client for transmitting to an XML manager, wherein the XML parser inputs MIB information to the destination node based on the SNMP response message to generate a response message for the XML request message, and sends the generated XML response message to the XML node. Send to the XML manager through the request processing module and HTTP server.

In addition, in order to achieve another object of the present invention, the present invention, in a gateway including a SOAP server, is managed by an SNMP delegate to deliver a response message to the SOAP request message for the inquiry and modification of the XML document from the XML manager An XML converter for storing the nodes included in the MIB as a table, forming an XML schema having a structure identical to that of the management information stored in the table, and forming an XML document having the same structure as the MIB tree structure; The SOAP server for analyzing a SOAP request message received from the XML manager, searching for a destination node, and packaging an XML response message for the SOAP request message into a SOAP response message, and the XML schema and an XML document are stored. Extract the OID information corresponding to the target node and send the SOAP request message to the SNMP request message. Sending the SNMP request message to an XML parser for converting the text to an XML parser and an SNMP delegate corresponding to the OID information extracted from the XML parser, receiving an SNMP response message for the SNMP request message from the SNMP delegate, and transmitting the received SNMP response message to the XML parser. A trap processing module for receiving a trap message generated by the SNMP delegate according to an SNMP stack, a predefined event occurrence, and reflecting the trap message to an XML document stored in the XML parser; A SOAP client for packaging the reflected XML document into a SOAP trap message, and an HTTP client for providing the SOAP trap message to the XML manager, and inputs MIB information to the destination node based on the SNMP response message through the XML parser. Generate an XML response message, wherein the generated XML response message is It is packaged into a SOAP response message by a SOAP server and then sent to the XML manager via the HTTP server.

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

1 is a block diagram illustrating the structure of an XML / SNMP gateway according to the present invention. FIG. 2 is a block diagram showing the internal structure of an XML converter in an XML / SNMP gateway according to the present invention.

As shown in FIG. 1, the XML-based network management system according to the present invention includes an XML manager 100, an XML / SNMP gateway 200, and an SNMP manager 300, wherein the XML / SNMP gateway 200 ) Includes an XML translator 210, an XML parser 220, a request processing module 230, an SNMP stack 240, a trap processing module 250, and a trap reporting module 260.

The XML converter 210 is a means for converting management information base (MIB) management information defined based on SNMP in the XML / SNMP gateway 200 into an XML standard, and is based on XML without losing or modifying MIB management information defined in SNMP. To XML schemas and XML documents for implementation in network management. In this case, the XML converter 210 analyzes each syntax of the MIB definition document defined using the Structure of Management Information (SMI), stores each node included in the MIB management information as a table, and corresponds to an XML element. To generate and provide it to the XML parser 220.

The XML schema generated by the XML converter 210 has the same structure as that of the management information stored in the table, and the XML document has the same structure as the tree structure of the MIB.

The XML converter 210 basically preserves the tree structure of the MIB and generates an XML schema document for each SNMP MIB module. First, an XML schema document having a name of the MIB module as the top node of the XML document is generated, and an XML element is generated corresponding to each node of the MIB. At this time, the name of each XML element becomes the name of each node, and the inner clause of the MIB node is converted into an attribute of the XML element. Even in the conversion of data types, SMI's basic data types are converted through basic data types provided by XML schema and extension definitions. Among the data types, various user-defined data types, such as enumeration, string length specification, and data range specification, are converted using the extension and restriction syntax of the data types provided by XML Schema.

This XML translator 210 includes an SMI parser 211, a node table generator 212, an XML schema generator 213, and an XML document generator 214, as shown in FIG. 2.

The SMI parser 211 separates the received SNMP MIB into a series of tokens and analyzes the received SNMP MIBs to determine whether they conform to the syntax of the SMI, generates an error if there is an expression that does not match the syntax, and generates an error. It tells you what is wrong.

The node table generator 212 converts each node into a Java class in the parsed token, stores the node class in a table form, and analyzes correlations between the nodes in the stored table to determine whether there are errors in these relationships.

The XML schema generator 213 generates an XML schema using the structure of management information stored in the node table. In this case, the XML schema is used to verify management information included in the XML document generated by the XML document generator 214.

The XML document generator 214 generates an XML document having the same structure as the SNMP tree structure using management information stored in the node table. In this case, the generated XML document stores basic information necessary for requesting management information through the SNMP MIB structure and the SNMP delegate 300. The XML / SNMP gateway performs a request for corresponding management information by using the XML parser 220 based on the XML document generated by the XML document generator 214.

The request processing module 230 receives and analyzes an XML request message sent from the XML manager 100, and calls a function of an appropriate XML parser to access the destination node specified in the XML request message.

The XML parser 220 is a means for enabling various methods of access and manipulation of the destination node based on the XML document provided from the XML converter 210 and the XML request message provided from the request processing module 230, in particular, an XML document. Extracts the information required for the SNMP request message, such as the object IDentification (OID) of the target node, and provides it to the SNMP stack 240, and from the SNMP response message and trap processing module 250 provided from the SNMP stack 240 Generates an XML response message for the XML request message by inputting an arbitrary value to the destination node using the received trap message, and sends the generated XML response message to the XML manager through the request processing module 230 or the trap reporting module 260. Give 100.

The SNMP stack 240 transmits an SNMP request message to the SNMP delegate 300 of the network management device corresponding to the OID information received from the XML parser 220 as a means for communicating with the SNMP delegate 300.

The trap processing module 250 receives a trap message transmitted from the SNMP delegate 300, and the information included in the trap message is input on the XML document by the XML parser 220. Through this process, the XML document including the trap message is provided to the trap report module 260 by the XML parser 220.

The trap reporting module 260 is a means of communicating with the XML manager 100 to provide an XML documented trap message to the XML manager 100.

The communication model used in the SNMP / XML gateway having the above configuration includes a request / response model and a notification model.

The request / response model is used in a general management structure. When a manager sends a message requesting information required by a delegate, the delegate sends a response message to the manager.

First, the XML manager 100 generates a request message having an XML format and transmits the request message to the request processing module 230 according to the manager's request, and the request processing module 230 sends the request message received from the XML delegate 100. The analysis results are provided to the XML parser 220.

The XML parser 220 inquires the corresponding node in the request message, extracts information required for the SNMP request, such as an OID, and provides the extracted information to the SNMP stack 240.

The SNMP stack 240 sends an SNMP request message to the SNMP delegate 300, receives a response message from the SNMP delegate 300, and provides the response message to the XML parser 220.

The XML parser 220 inputs new MIB information to the corresponding node using the response message and provides the new MIB information to the request processing module 230.

The request processing module 230 transmits the XML documented MIB information to the XML delegate 100.

The notification model is a model of notifying a manager of a trap message generated from the SNMP delegates 300 when a specific event occurs, which is described below.

The SNMP delegate 300 provides a trap message generated when a predefined event occurs to the trap processing module 250 using the SNMP trap.

The trap processing module 250 analyzes the received trap message and fills the portion corresponding to the trap on the XML document with the analyzed content. The XML documented trap message is provided to the XML manager 100 by the trap report module 260 of the SNMP / XML gateway 200.

Next, a method of expressing and transferring data exchanged between the XML manager 100 and the SNMP delegate 300 using the XML / SNMP gateway 200 will be described. In the XML / SNMP gateway 200 proposed by the present invention, a communication method between the gateway 200 and the SNMP delegate 300 uses SNMP, and the gateway 200 and the XML manager 100 provide flexible and scalable interworking. Use XML to provide

3, 4, and 5, the interaction conversion process of the XML / SNMP gateway proposed by the present invention will be described. 3 is a block diagram illustrating an XML transformation-based interaction transformation process according to an embodiment of the present invention.

In the XML parser-based interconversion, the XML / SNMP gateway 200 is an internal gateway integrated in the same system as the XML manager 100. Therefore, the XML / SNMP gateway 200 includes an XML manager 100 and an XML / SNMP gateway. If the request processing module 230 for analyzing and processing messages between the 200 is unnecessary, the XML manager 100 directly calls the XML parser 220 to access and manipulate network management information.

For this purpose, referring to FIG. 3, the XML manager 100 calls the XML parser 220, and the called XML parser 220 obtains an OID for the destination node 1 among various nodes in the XML document having a tree structure. The detection is provided to the SNMP stack 240. After the SNMP stack 240 transmits an SNMP request message to the SNMP delegate 300 corresponding to the received OID information, the SNMP stack 240 receives an SNMP response message from the SNMP delegate 300 according to the request and delivers the SNMP response message to the XML parser 220.

Thereafter, the XML parser 220 reflects the contents of the SNMP response message to the destination node 1 on the XML document, and the XML document included in the destination node as a result value for the XML parser function called from the XML manager 100. 3) is transmitted to the XML manager 100 via the request processing module 230.

In addition, the trap processing module 250 receives a trap message generated by the SNMP delegate 300 according to the occurrence of a preset event, and inputs trap information included in the received trap message on a corresponding XML document. As the trap information is input into the XML document, an event handler predefined by the event interface provided by the DOM is driven. Accordingly, the XML / SNMP gateway 200 transmits the XML documented trap message through the trap report module 260. Deliver to XML manager 100.

HTTP-based interaction transformation process will be described with reference to FIG. 4 is a block diagram illustrating an HTTP-based interaction transformation procedure according to another embodiment of the present invention.

The HTTP-based interaction transformation applies XPath, XQuery, and XUpdate expressions, which provide powerful capabilities for querying and modifying XML documents in generating HTTP request messages. And an HTTP client 272 for transmitting the HTTP-based trap message to the XML manager 100.

For this purpose, referring to FIG. 4, an HTTP request message having an XPath / XUpdate expression in a URI generated by the XML manager 100 is delivered to the request processing module 230 through the HTTP server 270, and the request processing module 230. ) Parses it and passes each expression included in the XML request message to the expression processing module 274. The expression processing module 274 analyzes each expression and retrieves the destination node 1 using an XML parser function. Thereafter, as described above, an SNMP request message is provided to the SNMP delegate 300 through the SNMP stack 240 through the same process as the XML parser-based interconversion process, and the result value thereof is transmitted through the request processing module 230. Provided to the XML manager 100.

In processing the trap message, the XML / SNMP gateway 200 is processed using the DOM event handler in the same manner as that used in the XML parser-based conversion method, and HTTP-based asynchronous trap through the HTTP client 272. Perform message delivery.

The SOAP-based interaction change process will be described with reference to FIG. 5. FIG. 5 is a block diagram illustrating a SOAP-based interapplication conversion procedure according to another embodiment of the present invention. FIG.

SOAP is a protocol developed to deliver structured information in a distributed environment. It is a protocol that provides an XML-based approach independent of implementation language and platform for various services provided on the Internet. Heterogeneous server in a distributed environment Is a communication protocol for Web services proposed for the integration of services, applications, objects, etc.

An XML server / client and a SOAP client / which are interfaces for transmitting and receiving SOAP messages and packaging them with SOAP are provided in the XML / SNMP gateway 200 and the XML manager 100 that transmit and receive SOAP messages with the XML manager 100 based on the SOAP. Provide a server.

As shown in FIG. 5, the XML manager 100 and the XML / SNMP gateway 200 each have SOAP engines 110, 292, SOAP servers 112, 290, and the like. HTTP servers 122 and 280 and HTTP clients 120 and 282 are installed, and using this, the XML / SNMP gateway 200 provides a SOAP-based communication method.

First, the XML request message generated by the management application 105 inside the XML manager 100 is packaged as a SOAP request message in the SOAP client 110 of the XML manager 100 and then XML / SNMP through the HTTP client 120. It is delivered to the HTTP server 280 of the gateway 200, and the HTTP server 280 delivers it to the SOAP server 290.

The SOAP server 290 analyzes the contents included in the SOAP request message and calls a service corresponding thereto. The service to be called is "getrequest" or "setrequest". The processing after the service call is the same as that used in the HTTP-based conversion method, and the SNMP request message is analyzed through the XML parser 220 and the SNMP stack 240 by analyzing the factors included in the SOAP request message. Provide to the delegate 300. The service call result value is packaged as a SOAP response message at the SOAP server 290 and sent to the XML manager 100 via the HTTP server 280.

Also, the XML / SNMP gateway 200 may package an XML trapped trap message for a trap message generated according to a predetermined event in the SNMP delegate 300 into a SAOP trap message by using the SOAP client 292, and then use an XML manager ( 100 to SOAP server 112).

As described above, in the present invention, by converting MIB information in SMI format into XML schema that can be understood in XML-based network management without loss for XML / SNMP gateway, XML-based network management system and SNMP without modification of SNMP delegate It can provide flexibility between agents.

1 is a block diagram showing the structure of an XML / SNMP gateway according to the present invention;

2 is a block diagram illustrating an internal structure of an XML converter in an XML / SNMP gateway according to the present invention;

3 is a block diagram illustrating an XML transformation-based interaction transformation process according to an embodiment of the present invention.

4 is a block diagram illustrating an HTTP-based interaction transformation procedure according to another embodiment of the present invention.

FIG. 5 is a block diagram illustrating a SOAP-based interapplication conversion procedure according to another embodiment of the present invention. FIG.

<Description of the code | symbol about the principal part of drawing>

100: XML Manager 200: XML / SNMP Gateway

210: XML Converter 220: XML Parser

230: request processing module 240: SNMP stack

250: trap processing module 260: trap reporting module

300: SNMP manager

Claims (5)

In the gateway for converting messages sent and received between the XML management unit and the SNMP delegate, Each node included in the MIB managed by the SNMP delegate is stored in a table, an XML schema having the same structure as that of the management information stored in the table is formed, and an XML document having the same structure as the MIB tree structure is formed. An XML converter, A request processing module for extracting an object node to be accessed by analyzing the XML request message received from the XML manager; An XML parser for storing the XML schema and the XML document and extracting OID information corresponding to the destination node; A SNMP stack for transmitting an SNMP request message to an SNMP delegate corresponding to the OID information extracted from the XML parser, receiving an SNMP response message for the SNMP request message from the SNMP delegate, and transmitting the received SNMP response message to the XML parser; The XML parser generates an XML document for the XML request message by inputting MIB information to the destination node based on the SNMP response message, and transmits the generated XML response message to the XML manager through the request processing module. XML / SNMP Gateway. In a gateway that translates messages sent to and received from an SNMP delegate, Each node included in the MIB managed by the SNMP delegate is stored in a table, an XML schema having the same structure as that of the management information stored in the table is formed, and an XML document having the same structure as the MIB tree structure is formed. An XML converter, An XML parser storing the XML schema and the XML document, An XML manager which calls the XML parser and detects OID information of a destination node corresponding to an XML request message; An SNMP stack for transmitting an SNMP request message to an SNMP delegate corresponding to the OID information, receiving an SNMP response message for an SNMP request message from the SNMP delegate, and transmitting the received SNMP response message to the XML parser; Receives a trap message generated in the SNMP delegate in accordance with a predefined event generation, and a trap processing module for reflecting the contents of the received trap message in the XML document stored in the XML parser, For inputting MIB information to the destination node based on the SNMP response message through the XML parser, a response message for the XML request message is generated, and for the network integrated management for transmitting the generated XML response message to the XML manager. XML / SNMP Gateway. In a gateway including an HTTP server, in order to deliver a response message for an HTTP request message including an expression for querying and modifying an XML document from an administrator, Each node included in the MIB managed by the SNMP delegate is stored in a table, and an XML schema having the same structure as that of the management information stored in the table is formed, and an XML document having the same structure as the MIB tree structure is formed. With an XML converter, A request processing module for extracting the expression from an HTTP request message received through the HTTP server; An expression processing module for searching for a destination node based on the expression; An XML parser for storing the XML schema and the XML document and extracting OID information corresponding to the destination node; An SNMP stack transmitting an SNMP request message to an SNMP delegate corresponding to the OID information extracted from the XML parser, receiving an SNMP response message for the SNMP request message from the SNMP delegate, and transmitting the received SNMP response message to the XML parser; A trap processing module configured to receive a trap message generated in the SNMP delegate according to a predefined event occurrence and reflect the contents of the received trap message in an XML document stored in the XML parser; An HTTP client that receives the XML document reflecting the contents of the trap message, receives the received XML document from the XML parser, and transmits the received XML document to the XML manager; The XML parser generates a response message to the XML request message by inputting MIB information to the destination node based on the SNMP response message, and sends the generated XML response message to the XML manager through the request processing module and the HTTP server. XML / SNMP gateway for integrated network management to send to. In a gateway including a SOAP server, to deliver a response message to a SOAP request message for viewing and modifying an XML document from an XML manager, Each node included in the MIB managed by the SNMP delegate is stored in a table, and an XML schema having the same structure as that of the management information stored in the table is formed, and an XML document having the same structure as the MIB tree structure is formed. With an XML converter, The SOAP server analyzing the SOAP request message received from the XML manager, searching for a destination node, and packaging an XML response message for the SOAP request message into a SOAP response message; An XML parser for storing the XML schema and the XML document, extracting OID information corresponding to the destination node, and converting the SOAP request message into an SNMP request message; An SNMP stack for transmitting the SNMP request message to an SNMP delegate corresponding to the OID information extracted from the XML parser, receiving an SNMP response message for the SNMP request message from the SNMP delegate, and transmitting the received SNMP response message to the XML parser; A trap processing module for receiving a trap message generated in the SNMP delegate according to a predefined event occurrence and reflecting the contents of the trap message in an XML document stored in the XML parser; A SOAP client for packaging an XML document reflecting the contents of the trap message into a SOAP trap message; An HTTP client for providing the SOAP trap message to the XML manager; Generates an XML response message by inputting MIB information to the destination node based on the SNMP response message through the XML parser, wherein the generated XML response message is packaged as a SOAP response message by the SOAP server and then the HTTP server. XML / SNMP gateway providing a SOAP-based interaction transformation method is transmitted to the XML manager through. The method according to claim 1, 2, 3, or 4, The XML converter, An SMI parser that separates the SNMP MIB into a set of tokens and checks whether it conforms to the syntax of SMI; A node table generator for converting each node into a Java class in the parsed token, and forming and storing a node table in the converted class; An XML schema generator for generating an XML schema including a structure of the management information by using the management information stored in the node table; And an XML document generator for generating an XML document having the same structure as the SNMP MIB tree structure by using the management information stored in the node table.