JP2004213266A - Device management device and device management system using the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a device management device and a device management system using it capable of facilitating countermeasures to the change of a device, and efficiently managing a device on a network. <P>SOLUTION: A definition file 121 in which a command for managing or monitoring a device is described in XML is read by an XML application 123 so as to be performed. The XML makes it possible to freely change tag setting so that when any change is generated in the device or a management system, the command corresponding to the change can be reflected on the definition file 121. The reflected definition file 121 is performed by the XML application 123 so that the device management device can facilitate countermeasures to the change of the device. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a device management apparatus for managing devices such as a printer and a router on a network, and a device management system using the same.
[0002]
[Prior art]
Many devices such as printers and routers are connected to a LAN (Local Area Network) installed in an office or a company. Conventionally, a simple network management protocol (SNMP) has been used to efficiently manage or monitor these devices. A device management device such as a personal computer on a LAN communicates with a device on the LAN using an SNMP protocol to acquire information about the device or to provide a parameter for the device with option information. Or can be set. The information acquired by the device management apparatus includes information indicating the status of the device, and information indicating the model name and configuration of the device.
[0003]
A device capable of performing communication using the SNMP protocol holds a database called MIB (Manager Information Base). The device management apparatus can acquire and set the MIB data of the device by communicating with the device on the LAN using the SNMP protocol. The device management apparatus can know the status of the device and the like from the acquired MIB data, and can freely set the device parameters by setting the MIB data of the device. .
[0004]
Among device management devices that acquire and set MIB data of devices on a LAN, there is a device management device that can simultaneously acquire and set MIB data of a plurality of devices (for example, Patent Document 1). 1).
[0005]
[Patent Document 1]
JP 2000-339247 A
[0006]
[Problems to be solved by the invention]
A program for acquiring and setting MIB data of a device on a network is installed in the device management apparatus, and by executing this program, the device management apparatus can determine the status of the device and the like. And set device parameters.
After such a program is installed in the device management apparatus, for example, a function may be added to a device on the LAN, or a new device may be connected to the LAN. However, as long as the installed program does not support an added function or a new type of device, the device management apparatus obtains or sets MIB data relating to the added function or the new device. Or not.
[0007]
Therefore, an existing program installed in the device management apparatus must be replaced with a program corresponding to a change in device. During this replacement work, the operation of all the other device management devices and devices connected to the LAN must be stopped, and the use of the system using the LAN is greatly restricted. In addition, since the management of devices on the network is performed by individual device management devices on the network, it is necessary to upgrade the version of the program for each device management device, which requires a great deal of labor and time.
[0008]
Therefore, an object of the present invention is to provide a device management apparatus which can easily cope with a change in a device, and a device management system using the same.
It is another object of the present invention to provide a device management apparatus capable of efficiently managing devices on a network, and a device management system using the same.
[0009]
Means for Solving the Problems and Effects of the Invention
The invention according to claim 1 for achieving the above object is a device management apparatus (10) for managing a device (20) connected to a network using an SNMP protocol, the device management apparatus being connected to the network. An editable definition that describes, from a device, information (231) necessary to obtain information about the device and information (232) required to set parameters of the device for the device. A storage unit (115) for storing a file (121), and interpreting a description of a definition file stored in the storage unit to obtain information about the device from a device connected to the network, and Device management means (130, 132, 13) for setting parameters of the device for the device. ) And a device management apparatus which comprises a. It should be noted that the alphanumeric characters in parentheses indicate corresponding components and the like in embodiments described later. Hereinafter, the same applies in this section.
[0010]
According to this configuration, the device management means acquires information about the device by interpreting information (commands and parameters) described in the editable definition file, and sets parameters for the device. It can be carried out. Therefore, when a function is added to a device on the network or a new device is connected to the network, by adding a description for using the additional function or the new device to the definition file, the device management apparatus can perform the following operations. You can also use these additional features and new devices.
[0011]
In addition, during the editing of the definition file, it is not necessary to stop the operation of all management devices and devices of other devices connected to the network, so that the use of the network-based system may be significantly restricted. Absent.
The device management apparatus may include an editing unit for editing the definition file. By the editing means, the definition file can be easily edited. As a result, the device management apparatus can easily respond to a change in the device.
[0012]
Further, a server for controlling a definition file stored in the device management apparatus may be connected to the network. In this server, if the definition file is updated, the device management device connected to the network can acquire the updated definition file. As a result, the time and labor required for managing the definition files used by a plurality of devices can be significantly reduced.
[0013]
The invention according to claim 2, wherein the definition file further describes information (235) defining an operation corresponding to the information on the device by the device management means, and the device management device includes the device management device. 2. The device management device according to claim 1, further comprising: executing means for interpreting the description of the definition file after acquiring information on the device and executing an operation corresponding to the acquired information. Device.
[0014]
According to this configuration, the device management apparatus can execute an operation corresponding to the information acquired from the device. Therefore, for example, when it is known from the information acquired from the device that an error has occurred in the device, the device management apparatus can perform processing for dealing with the error. That is, devices on the network can be managed efficiently.
The invention according to claim 3 is the device management apparatus according to claim 1 or 2, wherein the definition file is created in an XML format.
[0015]
According to this configuration, the definition file is created in XML (Extensible Markup Language). XML is text-based, and individual data is given meaning. Therefore, the operator can easily edit the definition file.
In XML, a file creator can freely set and describe an annotation symbol called a “tag”. Therefore, a definition file that is easy for the operator to use can be created.
[0016]
According to a fourth aspect of the present invention, the device management apparatus according to any one of the first to third aspects is connected to the network, and by using an SNMP protocol, the device management apparatus transmits information about its own device to the device management apparatus. A device having means (210, 213) for transmitting MIB format information (215) including parameters set in the own device.
[0017]
By using this device management system, the effects described in relation to the first aspect of the invention can be achieved.
[0018]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be specifically described with reference to the drawings.
FIG. 1 is a block diagram showing an overall configuration of a device management system according to an embodiment of the present invention.
In this device management system, a device management device such as a personal computer connected to a network can acquire information on a device such as a printer or a router or set parameters of device option information. It has become. The device management apparatus can know the status and configuration of the device from the information acquired from the device.
[0019]
This management system includes a plurality of managers 10 which are device management devices connected to a LAN (Local Area Network), and a plurality of agents 20 which are devices also connected to the LAN. The manager 10 is a personal computer or the like installed in an office or a company, and is communicably connected to the LAN. The agent 20 is also communicably connected to the LAN. Therefore, the manager 10 and the agent 20 can transmit and receive data to and from each other by using the LAN.
[0020]
When the manager 10 transmits a command for acquiring information on the agent 20 to the agent 20 (arrow A1), the agent 20 returns information on its own device to the manager 10 in response to the command. (Arrow A2). The manager 10 can know the state, configuration, and the like of the agent 20 from the received information. Then, for example, when it is revealed that the agent 20 has failed, the manager 10 can transmit a command for responding to the failure to the agent 20 (arrow A3).
[0021]
The manager 10 can further transmit a command for setting parameters provided in the agent 20 to the agent 20 (arrow A4).
By performing such communication between the manager 10 and the agent 20, the manager 10 can acquire information on the agent 20 and set parameters of the agent 20.
[0022]
FIG. 2 is a block diagram illustrating an electrical configuration of the manager 10. The manager 10 includes a CPU 110, a ROM 111, a RAM 112, an input device 113, a display device 114, a storage device 115, and a communication control device 116, which are connected to one another via a bus 117. The CPU 110 controls transmission and reception of data between the ROM 111, the RAM 112, the input device 113, the display device 114, and the storage device 115 based on a program stored in the ROM 111, and controls the input device 113, the display device 114, It controls the device 115 and the communication control device 116, and controls connection with the LAN via the communication control device 116.
[0023]
The input device 113 includes a keyboard, a pointing device, and the like, and an operation signal thereof is provided to the CPU 110. The display device 114 is a CRT, a liquid crystal display panel, or the like, and displays a signal given from the CPU 110.
The storage device 115 includes a hard disk device and the like, and is used as a storage medium for storing data and application programs necessary for the manager 10. The CPU 110 can store data in the storage device 115 or read and use data stored in the storage device 115 as necessary.
[0024]
FIG. 3 is a block diagram for explaining files stored in the storage device 115. The storage device 115 includes a definition file 121 for managing or monitoring the agent 20 connected to the LAN, an XML parser 122, an XML application program 123, a DOM (Document Object Model) file, or a SAX (Simple API for XML) file. 124, and an SNMP communication control program 125.
[0025]
In the definition file 121, a command for managing or monitoring the agent 20 connected to the LAN is described in XML (Extensible Markup Language). The LAN administrator or the like can edit the definition file 121 by performing a predetermined operation of the input device 113 of the manager 10. That is, a command for managing or monitoring the agent 20 can be easily edited.
[0026]
The XML parser 122 can analyze the definition file 121, and the XML application program 123 is an application program that can read and execute the definition file 121, and is, for example, Java (registered trademark) or the like. For this reason, the XML application program 123 can also analyze and execute the definition file 121 edited by the LAN administrator or the like. Therefore, when a new function is added to the agent 20 connected to the LAN or when a new agent 20 is connected to the LAN, it is necessary to change the method of managing or monitoring the agent 20. By performing the predetermined operation of 113, the management method or the monitoring method of the agent 20 can be easily changed only by changing the definition file 121.
[0027]
The DOM file or the SAX file 124 controls data exchange between the definition file 121 and the XML application program 123 when the XML application program 123 interprets and executes the contents described in the definition file 121. It has become. The SNMP communication control program 125 can control communication so that the manager 10 and the agent 20 connected to the LAN can perform communication using the SNMP protocol.
[0028]
FIG. 4 is a block diagram for explaining a functional configuration of the manager 10. The manager 10 is substantially provided with a plurality of function processing units realized by the CPU 110 executing a program stored in the ROM 111 or the storage device 115. More specifically, the manager 10 includes a control unit 130 and an SNMP communication control unit 131 controlled by the control unit 130.
The SNMP communication control unit 131 is realized by the SNMP communication control program 125 being read from the storage device 115 and executed by the CPU 110. The SNMP communication control unit 131 controls communication so that the manager 10 and the agent 20 connected to the LAN can perform communication using the SNMP protocol.
[0029]
The manager 10 further includes a device management / monitoring unit 132 for efficiently managing or monitoring the agent 20 connected to the LAN. The device management / monitoring unit 132 is controlled by the control unit 130. I have.
The device management / monitoring unit 132 includes management software 133. When the device management / monitoring unit 132 reads the XML parser 122 from the storage device 115, the XML parser 122 analyzes the definition file 121. Then, the analyzed result is expanded on the RAM 112, and the DOM file or the SAX file 124 is read from the storage device 115. Thereafter, when the XML application 123 is read from the storage device 115, the management software 133 is started. The management software 133 refers to the definition file 121 expanded on the RAM 112 by using the DOM file or the SAX file 124, and operates based on the definition file 121.
[0030]
FIG. 5 is a block diagram for explaining the configuration of the agent 20. The agent 20 includes a CPU 211 and a ROM 212 and a control unit 210 for controlling the entire agent 20. The agent 20 further includes an SNMP communication control unit 213 and a storage device 214, which are controlled by the control unit 210.
The SNMP communication control unit 213 controls communication so that the manager 10 and the agent 20 connected to the LAN can perform communication using the SNMP protocol.
[0031]
The storage device 214 includes a hard disk device and the like, and is used as a storage medium for storing data and the like necessary for the agent 20. The control unit 210 can store data in the storage device 214 or read and use data stored in the storage device 214 as necessary.
Further, the storage device 214 stores an MIB 215 for the manager 10 to know the state and configuration of the agent 20 and to set parameters of the agent 20. The MIB 215 is a database having a tree-like data structure, and the data structure differs for each agent 20. The data structure also changes when a new function is added to the agent 20 or when some models provided in the agent 20 are deleted. Of course, as new devices are developed, such devices will have different data structures than existing devices.
[0032]
FIG. 6 is a conceptual diagram illustrating an example of the MIB 215, and FIG. 7 is a diagram illustrating an example of the definition file 121. Here, a printer is assumed as the agent 20.
In each node (node) of the MIB 215, an object for holding information about the printer and setting parameters of the printer is set. Each section of the MIB 215 is provided with an object ID (Object ID) for identifying each object, and the object and the object ID are held in the MIB 215 in one-to-one correspondence. Hereinafter, the object ID is referred to as OID.
[0033]
The MIB 215 of the printer holds the object 221 and the object 222 with the object 220 as a vertex. The object 221 holds information on the model name of the printer, and is given an OID “1.3.3.6.1.2.1.25.3.2.2.1.3.1”. The object 222 holds the parameter information set in the printer, and is given an OID of “1.3.3.6.1.2.1.43.18.1.1.7”.
[0034]
The object 221 fixedly holds the printer model name as character information, while the object 222 holds an integer value which is parameter information set for the printer. Therefore, the object 222 does not always hold the same integer value. For example, when an error that requires opening the cover of the printer occurs, the object 222 holds the integer value “3”, and when a paper jam occurs inside the printer, the object 222 holds the integer value “8”. It is supposed to be.
[0035]
The definition file 121 includes a printer information acquisition description section 231 in which a command for acquiring information from an object holding information on the printer is described, and a parameter in which a command for setting parameters of the printer are described. It is composed of a setting description section 232 and the like.
The printer information acquisition description section 231 includes a model name information acquisition description section 233 in which a command for acquiring model name information from an object holding model name information of the printer is described, and a configuration of a paper feeder of the printer. It is composed of a paper feeder configuration information acquisition description section (not shown) that describes a command for acquiring paper feeder configuration information from an object holding information.
[0036]
The model name information acquisition description section 233 is obtained from an object specification description section 234 in which a command for specifying an object holding printer model name information is described, and an object specified by the object specification description section 234. And a corresponding operation description section 235 in which a command for executing an operation corresponding to the information is described.
In the object specification description part 234, an OID “1.3.6.1.1.2.1.25.3.2.3.1.3.1” is described. Therefore, the management software 133 specifies the object 221 associated with the OID from the MIB 215, and acquires the printer model name information from the object 221. The corresponding operation description part 235 is described so that the information of the printer model name acquired from the object 221 is displayed on the display device 114.
[0037]
The parameter setting description section 232 includes a parameter acquisition specification description section 236 in which a command for obtaining a parameter value set in the printer is described, and a parameter setting description section 232 for responding to parameter information obtained by the parameter specification description section 236. It comprises a parameter information response description section 237 in which a command is described, a parameter information change section (not shown) in which a command for changing the value of parameter information set in the printer is described, and the like. .
[0038]
The object identification description part 236 describes an OID “1.3.6.1.2.1.43.18.1.1.1.7”. Therefore, the management software 133 specifies the object 222 associated with this OID from the MIB 215, and acquires parameter information from the object 222. The parameter information response description part 237 has a description for performing a process corresponding to the value of each parameter information. Specifically, when the parameter information has a value of “3”, “cover open” is described in the parameter information. When the information has the value “8”, “paper jam” is described to be displayed on the display device 114.
[0039]
When the manager 10 wants to change the parameter information held in the printer, the manager 10 can change the parameter information held in the printer by interpreting and executing the contents described in the parameter information change unit. .
As described above, by interpreting the definition file 121 described in XML, the management software 133 can acquire information on the agent 20 from the object of the MIB 215 and set parameters of the agent 20.
[0040]
Since the configuration of the MIB 215 of each agent 20 connected to the network is different, a command for managing or monitoring a plurality of agents 20 can be described in one definition file 121. It has become. Therefore, a LAN administrator or the like can easily manage or monitor devices on the LAN.
When a function (option) is added to the agent 20 on the network or a new agent 20 is added to the network, the existing definition file 121 can manage and monitor those agents 20. May disappear. In such a case, the LAN administrator or the like performs a predetermined operation on the input device 113 to change or change the definition file 121 so that the agents 20 can be managed or monitored. Thus, the agent 20 on the LAN can be managed.
[0041]
In the above-described embodiment, the definition file 121 is described in XML, but the language of the definition file 121 is not limited to XML, and the agent 20 can be managed or monitored, and the definition file can be freely edited. The definition file 121 may be described using a command of another language as long as it is possible. Further, the definition file 121 is edited by the LAN administrator or the like performing a predetermined operation of the input device 113, but the server connected to the LAN sends the edited definition file 121 to the manager 10 via the LAN. It may be a configuration to give.
[0042]
In addition, various design changes can be made within the scope of the matters described in the claims.
[Brief description of the drawings]
FIG. 1 is a block diagram showing an overall configuration of a device management system according to an embodiment of the present invention.
FIG. 2 is a block diagram showing an electrical configuration of a manager.
FIG. 3 is a block diagram for explaining files stored in a storage device of a manager.
FIG. 4 is a block diagram illustrating a functional configuration of a manager.
FIG. 5 is a block diagram illustrating a configuration of a device.
FIG. 6 is a conceptual diagram illustrating an example of an MIB.
FIG. 7 is a diagram illustrating an example of a definition file.
[Explanation of symbols]
10 Manager
115 Storage
121 Definition file (XML file)
122 XML parser
123 XML application
124 DOM file or SAX file
130 control unit
132 Device Management / Monitoring Unit
133 management software
20 agents
213 SNMP communication control unit
215 MIB
231 Printer information acquisition description section
232 Parameter setting description section
235 Action description part

Claims (4)

A device management apparatus for managing a device connected to a network using an SNMP protocol,
An editable definition that describes information necessary for obtaining information about the device from a device connected to the network, and information necessary for setting parameters of the device for the device. Storage means for storing a file;
A device that interprets the description of the definition file stored in the storage unit, acquires information about the device from a device connected to the network, and sets parameters of the device for the device A device management apparatus, comprising: a management unit. The definition file further describes information defining an operation corresponding to information on a device by the device management means,
The device management device may further include an execution unit that, after the device management device obtains information about the device, interprets the description of the definition file and executes an operation corresponding to the obtained information. The device management apparatus according to claim 1, wherein: The device management apparatus according to claim 1, wherein the definition file is created in an XML format. A device management apparatus according to any one of claims 1 to 3,
A device connected to the network and having means for transmitting information in MIB format including information on the own device and parameters set in the own device to the device management apparatus by using an SNMP protocol. A device management system characterized by the following.

Images