JP5309101B2 - Device management system and device management program - Google Patents

Description

  The present invention relates to a technique for managing network devices.

  In recent years, various network services such as an IP telephone service have been provided. In order to provide a network service to a user, it is necessary to register with the customer management system after receiving an application for the service from the user and set the service in a network device such as a router or a server.

  Today's networks are comprised of a wide variety of network devices from a number of device vendors. Network devices (NE: Network Element) are managed by a device management system (EMS: Element Management System). When the service application is accepted, a service order describing the contents of the service application is input to the EMS, and the EMS sets an NE according to the input service order.

  Necessary requirements for managing the NE (configuration of management target, communication means with the apparatus, acquisition procedure of maintenance information, format of maintenance information to be obtained, etc.) vary depending on the NE. Since it is difficult to manage various NEs with one EMS, there is generally a method for creating an EMS that limits management requirements and manages only NEs that meet the conditions.

  In EMS, there is a conversion technology that provides individual interfaces for NEs provided by a plurality of vendors to a higher-level external management system (network management system) or the like as a single interface so as not to show the difference. .

JP 2010-045657 A Japanese Patent No. 4460396

"Service Activation Technology that Supports Network Services", NTT Technology Journal, 2005, Vol. 17, No. 8, p.18-21

  However, when the maintenance interface of the target NE is not limited to CLI (Command Line Interface) and is managed by a single EMS, the NE conversion process assumed in the prior art cannot be used. For example, in the conventional technology, when an EMS that only assumes communication by Telnet is constructed, NE management that allows communication by Telnet can be handled by adding a local function such as addition of a script or a setting file. NE that does not allow communication by Telnet (for example, NE that only allows communication by NETCONF, NE that only allows communication by SNMP, NE that has API such as Java (registered trademark) RMI, JMS, etc., a unique format on TCP / IP For NEs that define and communicate rules, a new communication function for other protocols is newly designed, and for NEs such as communication processing for NEs that communicate with other protocols and command conversion processing on EMS. Logic needs to be added to all functional blocks and is locally There is a problem that it is not possible to achieve the EMS to manage the NE in the Do not function added.

  The present invention has been made in view of the above, and an object of the present invention is to provide a device management system that can manage various types of network devices and can be easily expanded.

  A device management system according to a first aspect of the present invention is a device management system that manages a network device according to order data describing operations for the network device, and can be interpreted by the network device for each network device, communication procedure, and operation. A storage unit that stores a template that is a template of communication contents; and the order data is received, the template corresponding to the order data is read from the storage unit, and a value described in the order data is applied to the template. Conversion means for generating communication data and transmitting an identifier of the network device, the communication procedure, and a command describing the communication data, and a communication module that receives the command and corresponds to the communication procedure described in the command Use the And having a communication means for communicating with the network device based on the communication data according to command.

  The apparatus management system includes a communication module definition storage unit that stores a definition of a communication module, and the communication unit activates the communication module with reference to the definition of the communication module stored in the communication module definition storage unit It is characterized by doing.

  A device management program according to a second aspect of the present invention causes a computer to function as the device management system.

  According to the present invention, it is possible to provide a device management system that can manage various types of network devices and can be easily expanded.

It is a functional block diagram which shows the structure of the apparatus management system in this Embodiment. It is a figure which shows the example of apparatus Request. It is a figure which shows the example of apparatus structure data. It is explanatory drawing which shows a mode that an apparatus Command template is specified from an apparatus Request and apparatus structure data. It is a figure which shows the example of an apparatus Command template. It is explanatory drawing which shows a mode that a communication data is produced | generated by substituting the parameter value of apparatus Request for an apparatus Command template. It is a figure which shows the example of the apparatus Command whose communication procedure is TELNET. It is a figure which shows the example of the apparatus Command whose communication procedure is NETCONF. It is a sequence diagram which shows the flow of the process which receives order data and sets a network apparatus.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a functional block diagram showing the configuration of the device management system in the present embodiment. The apparatus management system 1 shown in FIG. 1 includes an order transmission unit 10, a conversion function unit 20, and a communication function unit 30. Each unit included in the device management system 1 may be configured by a computer including an arithmetic processing device, a storage device, and the like, and the processing of each unit may be executed by a program. This program is stored in a storage device included in the device management system 1, and can be recorded on a recording medium such as a magnetic disk, an optical disk, or a semiconductor memory, or provided through a network. Hereinafter, each part will be described.

  The order transmitting unit 10 includes an order data receiving unit 101, an order data dividing unit 102, a device request generating unit 103, and a device request transmitting unit 104. The order data receiving unit 101 receives order data. The order data dividing unit 102 divides the order data for each network device and for each operation. The device request generation unit 103 converts the divided order data into a device request. The device request transmission unit 104 transmits the device request generated by the device request generation unit 103 to the conversion function unit 20.

  The order data includes an identifier of the network device, an operation content for the network device, and information necessary for the operation. Since some order data has operations for a plurality of network devices, the order data dividing unit 102 divides the order data for each network device and each operation.

  The device Request is an XML document obtained by converting the order data divided for each network device and for each operation, and meaning a parameter value. FIG. 2 shows an example of an apparatus request. The device request shown in the figure includes an order-specific identifier (ORDER_ID), an operation content (OPERATION), a network device identifier (NE_NAME), a physical interface name (INTERFACE_NAME), an IP address (IPADDR), and a netmask (NETMASK). , VLAN ID (VLAN_ID) is included. Other items may be included.

  One device request is one operation to one network device. An operation is one logical command, for example, setting an IP address of an interface.

  The converted device request is transmitted to the conversion function unit 20.

  The conversion function unit 20 includes a device configuration data storage unit 210, a device command template storage unit 220, and a conversion module 230.

  The device configuration data storage unit 210 stores an identifier of a network device, information indicating a storage location of a device command template, and device configuration data having a communication procedure.

  The device command template storage unit 220 stores a device command template that becomes a model of communication data depending on the network device, the communication procedure, and the order for each network device, communication procedure, and operation.

  The conversion module 230 includes a device request reception unit 231 that receives a device request, a conversion parameter generation unit 232 that generates communication data of the device command from the device request and the device command template, and a device that generates the device command including the generated communication data. A command generation unit 233 and a device command transmission unit 234 that transmits the generated device command to the communication function unit 30 are provided.

  The conversion parameter generation unit 232 acquires the storage location of the device command template corresponding to the device request received with reference to the device configuration data storage unit 210, reads out the corresponding device command template from the device command template storage unit 220, and Communication data is generated by applying parameters to the device command template. The communication data is data of communication contents that can be interpreted by the target network device, and depends on the network device, the communication procedure, and the operation content.

  FIG. 3 shows an example of device configuration data. The figure shows the device configuration data for two network devices, "10.0.0.1" and "10.0.0.2". The storage location (TEMPLATE_SET) and communication procedure (PROTOCOL) of the device command template for each network device Is described. By referring to the device configuration data, the device command template corresponding to the received device request can be specified. Specifically, as shown in FIG. 4, the device configuration data is acquired using the identifier of the network device of the device request as a key, and the device command template storage location of the device configuration data, the communication procedure, and the operation content of the device request are used. It is possible to specify the file name of the corresponding device Commnad template.

  FIG. 5 shows an example of an apparatus command template. The device command template is information serving as a model of communication data depending on the network device, communication procedure, and order contents. Communication data is generated by substituting parameter values into <PARAMETER> to </ PARAMETER> in the device command.

  FIG. 6 is an explanatory diagram illustrating a state in which communication data is generated from the device command template and the device request. As shown in the figure, communication data of the device command is generated by substituting the parameter values described in the device request into <PARAMETER> to </ PARAMETER> of the device command template.

  7 and 8 show examples of the device command. FIG. 7 shows an example of an apparatus command whose communication procedure is TELNET, and FIG. 8 shows an example of an apparatus command whose communication procedure is NETCONF. All have the same operation content, but the data to be transmitted / received differs depending on the communication procedure, so the communication data also differs. Even if the operation contents and the communication procedure are the same, if the network device vendors are different, the setting method of the network device may be changed, and the communication data will be different.

  Note that the conversion module 230 can dynamically add and change the conversion logic.

  The communication function unit 30 includes a communication module management unit 310, a module definition storage unit 320, a communication module loader 321, and a session management unit 330. The communication function unit 30 receives the device command, activates a communication module corresponding to the communication procedure described in the device command, and communicates with the network device based on the communication data described in the device command using the communication module. And configure the network device. In the communication function unit 30, a plurality of communication modules having different communication procedures can coexist. In FIG. 1, a TELNET communication module 311 and a NETCONF communication module 312 are shown as examples of the communication module.

  The communication module management unit 310 receives the device command, identifies a communication module corresponding to the communication procedure described in the received device command, and passes the device command to the communication module. The communication module transmits communication data of the device Command to the network device. Communication data of the device command is described in a format corresponding to the communication procedure described in the device command. The TELNET communication module 311 transmits communication data using TELNET, and the NETCONF communication module 312 transmits communication data using NETCONF. Each communication module dynamically acquires data depending on each communication procedure, such as a TELNET account and a password.

  A communication module exists for each communication procedure and is activated by the communication module loader 321. Even when network device vendors are different, the same communication module is used when the same communication procedure is used. When using a communication module corresponding to a new communication method, the communication module loader 321 starts the communication module by storing the definition of the communication module in the module definition storage unit 320. Even when other communication modules are operating, by storing the communication module definitions in the module definition storage unit 320, different communication modules can be dynamically changed, that is, the device management system 1 such as restarting the device management system 1. Can be added without stopping.

  A session between each communication module and the network device is managed by the session management unit 330.

  Next, processing for receiving order data and setting a network device will be described.

  FIG. 9 is a sequence diagram showing a flow of processing in which the device management system according to the present embodiment receives order data and sets a network device.

  Upon receiving the order data (step S101), the order transmitting unit 10 divides the received order data (step S102), generates a device request (step S103), and transmits the generated device request to the conversion function unit 20. (Step S104).

  Upon receiving the device request (step S105), the conversion function unit 20 generates a device command with reference to the device configuration data and the device command template (steps S106 and S107), and transmits the generated device command to the communication function unit 30. (Step S108).

  Upon receiving the device command, the communication function unit 30 activates a communication module corresponding to the communication procedure described in the device command (step S109). The communication module communicates with the network device according to the communication data of the device command, and sets the network device (step S110). The session management unit 330 manages the session between the communication module and the network device (step S111).

  As described above, according to this embodiment, the conversion function unit 20 generates communication data depending on the network device and the communication procedure from the device request converted from the order data using the device command template, and the generated communication. A device command including data, an identifier of a network device, and a communication procedure is transmitted to the communication function unit 30, and the communication function unit 30 communicates with the device Command using a communication module corresponding to the communication procedure described in the received device command. By communicating with the network device according to the data and setting the network device, it is possible to set the network device that communicates with the same communication procedure using a common communication module, thus reducing duplicate development of similar processing and developing Reduce volume, shorten development time, software version It is possible to suppress the effort of development, such as management.

  Further, according to the present embodiment, as described above, the conversion function unit 20 and the communication function unit 30 are explicitly divided, and the conversion process is performed by using the device command that does not depend on the model of the network device or the communication procedure. The communication processing can be individually developed, and the development site can be localized even when a new communication procedure or a new conversion logic is added to the device management system 1.

  According to this embodiment, the communication module loader 321 refers to the definition of the communication module stored in the module definition storage unit 320 and activates the communication module, thereby defining the communication module corresponding to the new communication procedure. By storing in the module definition storage unit 320, the communication function unit 30 can cope with a new communication procedure. Further, even when other communication modules are continuing to operate, different communication modules can be dynamically added.

DESCRIPTION OF SYMBOLS 1 ... Apparatus management system 10 ... Order transmission part 101 ... Order data reception part 102 ... Order data division part 103 ... Generation part 104 ... Transmission part 20 ... Conversion function part 210 ... Apparatus structure data storage part 220 ... Template storage part 230 ... Conversion Module 231 ... Reception unit 232 ... Conversion parameter generation unit 233 ... Generation unit 234 ... Transmission unit 30 ... Communication function unit 310 ... Communication module management unit 311 ... TELNET communication module 312 ... NETCONF communication module 320 ... Module definition storage unit 321 ... Communication module Loader 330 ... Session management section

Claims (3)

A device management system for managing a network device according to order data describing operations for the network device,
Storage means for storing templates that are templates of communication contents that can be interpreted by the network device for each network device, communication procedure, and operation;
The order data is received, the template corresponding to the order data is read from the storage means, communication data is generated by applying the value described in the order data to the template, the identifier of the network device, the communication Conversion means for transmitting a command describing the procedure and the communication data; and
Communication means for receiving the command and communicating with the network device based on communication data described in the command using a communication module corresponding to the communication procedure described in the command;
A device management system comprising: Communication module definition storage means for storing communication module definitions;
2. The apparatus management system according to claim 1, wherein the communication unit activates the communication module with reference to the definition of the communication module stored in the communication module definition storage unit.   A device management program for causing a computer to function as the device management system according to claim 1.

Images