JP2014186562A - Network device and monitoring device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To have a user of equipment customize an MIB according to one's own needs.SOLUTION: A network equipment is provided with: an analysis means for analyzing a definition file stipulated with a definition of an object to be stored to CPM which is a part of a private MIB and an update procedure or a monitoring procedure of the same, allotting an object ID to the object, as well as generating a script for obtaining an update or observation of the objet; a script execution means for executing the script generated by the analysis means and carrying out the update or monitoring of the object; and an agent means for while giving the object ID to the object and adding to the private MIB, acting as an intermediary for access of the monitoring device for carrying out state monitoring of the network equipment to the object.

Description

  The present invention relates to a technique for monitoring the status of a relay device such as a router and a network device such as a network printer.

  An example of this type of technology is SNMP (Simple Network Management Protocol). In SNMP, a device whose state is monitored is called an SNMP agent, and a device which is monitored is called an SNMP manager. The SNMP agent stratifies various types of information indicating the state of its own device for each category and stores it in a tree-structured database. This database is called MIB (Management Information Base) or MIB tree, and stores information indicating the occurrence of an event such as a change in a predetermined one of the information, in addition to the various information. Information stored in the MIB is called a MIB variable. Each MIB variable or a group of MIB variables is called an object, and an identifier called an object ID is given. The event may be included in the object. The SNMP manager monitors the state of the SNMP agent by referring to the MIB of each SNMP agent. For example, if the SNMP agent is a network printer, the MIB stores MIB variables indicating the remaining amount of ink (or toner) and whether or not the paper is out, and the SNMP manager refers to these MIB variables to specify the ink (or toner). ) Can be detected.

  MIB is divided into standard MIB and private MIB. Standard MIB is defined in RFC. On the other hand, the private MIB is defined by a manufacturer / distributor (hereinafter referred to as a vendor) of a device serving as an SNMP agent. Vendors of network devices such as network printers and routers can realize detailed status monitoring by defining private MIBs for network devices that they manufacture and sell. In other words, the implementation status of the MIB on the network device differs for each network device model and for each vendor.

Table 2004/071014

  As described above, the information indicating the state of the SNMP agent is stored in the MIB, but not all information indicating the state of the SNMP agent is stored, and is defined in the standard MIB and the private MIB. Only information is stored. For this reason, when the information that the user of the network device wants to monitor is not included in the MIB, even if the network device has the information, monitoring using SNMP is not possible. Can not. In such a case, if the user of the network device can freely add information desired to be monitored to the private MIB, no particular problem will occur. However, conventionally, only a vendor can define a private MIB. The user of the device cannot customize the private MIB.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a technique that allows a user of a network device to freely customize an MIB according to his / her needs.

  In order to solve the above-described problem, the present invention analyzes a definition file that defines the definition of an object stored in the MIB and the processing procedure for the object, assigns an object ID to the object, An analysis unit that generates a script for realizing processing, a file generation unit that extracts an object definition from the definition file, generates an MIB file for the object, and the script generated by the analysis unit is executed. A script execution unit that performs processing on the object, and an object ID assigned by the analysis unit is assigned to the object specified in the definition file and added to the MIB, while the state of the network device is monitored Surveillance equipment Providing a network device characterized by having an agent means for arbitrating access to the object by.

  According to the present invention, for example, if a vendor of a network device predefines a private MIB object ID range that the user of the network device can freely define, the user can specify the definition file according to his / her needs. By creating the MIB, the MIB can be freely customized within the range, and an MIB file that facilitates access to the MIB can be automatically generated. Conventionally, a MIB file is generally created by a vendor engineer by coding using a text editor or the like. However, since a MIB file has a unique format, it is used to such work. It was hard to make even a person. However, according to the present invention, since the MIB file for the object newly added to the above range is automatically generated, the work load is greatly reduced. Further, even if the definition of the standard MIB is reviewed in the future and an object is added or deleted, the present invention can flexibly cope with it. As another aspect of the present invention, an aspect of providing a program that causes a computer to function as each of the above means can be considered, and a specific distribution aspect of such a program is a CD-ROM (Compact Disk-Read Only Memory). A mode in which data is written and distributed on a computer-readable recording medium such as the above, and a mode in which data is distributed by downloading via a telecommunication line such as the Internet can be considered.

  Japanese Patent Application Laid-Open No. 2003-228561 discloses a technology that enables an SNMP agent to monitor the status of a device that does not support SNMP by using a proxy response to information on a device that does not support SNMP. The technique disclosed in Patent Document 1 is a technique for dealing with the fact that not all network devices included in a communication network are compatible with SNMP. However, Patent Document 1 does not disclose that the user of the network device freely customizes the MIB according to his / her needs, and the problem solved by the technique disclosed in Patent Document 1 is solved by the present invention. The challenge is completely different. Therefore, the technique disclosed in Patent Document 1 is completely different from the present invention.

  In a more preferred aspect, the network device has user interface means for allowing a user to create the definition file by GUI-based operation. The definition file can be created by coding using a text editor or the like, for example, but it is a difficult task for users who are unfamiliar with coding. In addition, in coding using a text editor or the like, a defect due to a typographical error or the like may occur. According to this aspect, even a user who is unfamiliar with coding can easily create a definition file and customize MIB without mistakes.

  As a more preferable mode, a mode in which at least one of the definition file and the MIB file generated by the file generation unit is transmitted to a predetermined destination is provided in the network device. Here, the predetermined destination may be the monitoring device or a server device accessible by the monitoring device or another network device. According to such an aspect, the monitoring device can acquire the definition file and the MIB file generated based on the definition file directly (or via the server device) from the network device, It is possible to avoid the occurrence of problems due to inconsistencies in MIB files with other network devices. When the predetermined destination is the monitoring device, the management means is notified to the monitoring device that a change has occurred in the MIB, and the definition file is sent in response to a request from the monitoring device. A process for returning at least one of the MIB files may be executed. When the monitoring device uses SNMP to monitor the status of the network device, SNMP may be used to notify that a change has occurred in the MIB and to send a file to the monitoring device. In a further preferred aspect, the management of processing for obtaining at least one of a definition file in which a definition of an object to be stored in the MIB and a processing procedure for the object is defined and an MIB file for the object from the predetermined destination is managed. The means may be executed. According to such an aspect, it becomes possible to cause another network device to acquire a definition file or an MIB file transmitted from a certain network device to the monitoring device or the server device. Alternatively, it can be operated according to the MIB file).

  In another aspect of the present invention, a monitoring device that accesses the MIB of a network device and monitors the status of the network device, and the network device in which the MIB has changed among the monitored network devices, A monitoring apparatus that executes a process of acquiring at least one of a definition file that defines a definition of an object stored in an MIB of the network device and a processing procedure for the object, and an MIB file for the object I will provide a. Also according to such an aspect, it is possible to prevent the occurrence of inconsistency of the MIB file between the network device and the monitoring device that monitors the state thereof.

It is a figure which shows the structural example of the network apparatus 1 of 1st Embodiment of this invention. It is a figure which shows the execution result of the command which displays the number of paths for every protocol on the network apparatus. It is a figure which shows the example of assignment of the object with respect to the execution result of the command. 6 is a diagram illustrating a description example of a definition file 230. FIG. It is a figure which shows the other description example of the definition file. It is a figure which shows the other description example of the definition file. It is a figure which shows an example of the CPM file 240 produced | generated from the definition file 230. FIG. It is a figure for demonstrating 2nd Embodiment of this invention. It is a figure for demonstrating the process which each of the network apparatus 1A and the monitoring apparatus 2 performs. It is a figure for demonstrating the process which each of network apparatus 1A-1 and 1A-2 and the monitoring apparatus 2 performs. It is a figure for demonstrating the process which each of network apparatus 1A-1 and 1A-2 and the monitoring apparatus 2 performs. It is a figure which shows the structural example of the network device 1B of a modification (1). It is a figure which shows an example of the GUI screen displayed on the display part of the user I / F part 300 of the network apparatus 1B. It is a figure for demonstrating the mechanism which shares a MIB file via a server apparatus. It is a figure for demonstrating the mechanism which shares a MIB file peer-to-peer.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(A: 1st Embodiment)
(A-1: Configuration)
FIG. 1 is a diagram illustrating a configuration example of a network device 1 according to an embodiment of the present invention. The control unit 100 includes, for example, a CPU (Central Processing Unit) and a RAM (Random Access).
Memory (not shown in FIG. 1). The control unit 100 functions as a relay control unit 110, a script execution unit 120, and an agent unit 130 by executing firmware (not shown) stored in the nonvolatile memory 200.

  The relay control means 110 is means for performing relay control of a packet received via a LAN (Local Area Network) based on the stored contents of a routing table (not shown) and the transmission destination address of the packet. The script execution unit 120 is a unit that interprets and executes a script described in a predetermined script language (Lua in the present embodiment). Note that Lua is used as the script language in the present embodiment because it has a light processing load and is suitable for application to an embedded device. Of course, other script languages such as Tcl may be used. The script executed by the script execution unit 120 may be a binary execution format file. The agent unit 130 communicates with an SNMP manager device (not shown), which is a monitoring device that monitors the status of the network device 1, in accordance with SNMP, and mediates access to the MIB tree of the network device 1 by the monitoring device. To do. That is, the network device 1 of this embodiment functions as an SNMP agent.

  The control unit 100 functions as the analysis unit 140 and the file generation unit 150 by executing the private MIB customization program 210 stored in the nonvolatile memory 200. The role of each of these means is as follows.

  The analysis unit 140 is a unit that analyzes the definition file 230 stored in the nonvolatile memory 200. Here, the definition file is a definition of an object stored in a range of reservation numbers (hereinafter referred to as Custom Private MIB: CPM) determined by the vendor in the private MIB of the network device 1 and a processing procedure for the object (for example, If the object is a MIB variable, it means a data file that defines the MIB variable update procedure or monitoring procedure). The user of the network device 1 can freely add objects such as MIB variables within the CPM. Details of the definition file will be clarified in an operation example in order to avoid duplication, but in the present embodiment, a text file described in the script language Lua is used as the definition file. The definition file 230 is created by the user of the network device 1 by coding using a text editor or the like, and is stored in a predetermined storage area of the nonvolatile memory 200. In the present embodiment, the case where the definition file 230 is stored in the nonvolatile memory 200 will be described. However, the definition file 230 may be stored in an external memory connected to the network device 1.

  The analysis unit 140 analyzes the definition file 230 and assigns an object ID to an object stored in the CPM. The analysis unit 140 extracts data representing the processing procedure for the object stored in the CPM from the definition file 230, and generates a Lua script to be executed by the script execution unit 120 from the data. Then, the analysis unit 140 provides the script execution unit 120 with a pair of the object ID assigned to the object stored in the CPM and the Lua script representing the processing procedure of the object. The script execution unit 120 functions as a monitoring unit that executes the Lua script generated by the analysis unit 140 and monitors an object.

  For example, when N (arbitrary natural number) sets of object IDs and Lua scripts are given from the analysis unit 140, the script execution unit 120 executes these N Lua scripts to execute the N object IDs. It functions as a monitoring unit n (n = 1 to N) that performs updating and monitoring of the objects indicated by each. The analysis unit 140 also executes a process of notifying the agent unit 130 of the storage location of the CPM file 240 (in this embodiment, a predetermined storage area in the nonvolatile memory 200) via the monitoring unit n. Here, the CPM file refers to an MIB file for an object stored in the CPM, and the CPM file 240 is generated by the file generation unit 150 using the definition file 230 as input data.

  The script execution unit 120 functioning as the monitoring unit n (n = 1 to N) notifies the agent unit 130 of the object ID notified from the analysis unit 140 and the storage location of the CPM file 240, and the object to the MIB tree 220. To add. The script execution unit 120 functioning as the monitoring unit n (n = 1 to N) updates or monitors the object added to the MIB tree 220 and notifies the agent unit 130 of the update result or the monitoring result.

  The file generation unit 150 extracts data representing the definition of the object from the definition file 230 to generate a CPM file 240 and writes it in a predetermined storage area in the nonvolatile memory 200.

  The above is the configuration of the network device 1. In the present embodiment, the case where the network device 1 is a router will be described. However, it may be a switching hub or a network printer. For example, when the network device 1 is a network printer, the relay control unit 110 is replaced with a print control unit that executes print control. In short, any network device that functions as an SNMP agent may be used.

(A-2: Operation)
Next, the operation of this embodiment will be described by taking as an example the case where the number of routes determined based on the routing table of the network device 1 is defined as a new MIB variable. In the operation example described below, “1.3.6.1.4.1.1182” is predetermined as the private MIB object ID for the vendor of the network device 1 and “1.3.6.1.4.1” as the object ID. Up to .1182.2.5 "is already assigned. Note that “1182” at the end of the private MIB object ID is a unique number (Private Enterprise Number: PEN) assigned to the vendor. Hereinafter, in this operation example, a case where an object representing the number of routes is defined below “1.3.6.1.4.1.1182.2.6.2.1” will be described.

In order to display the number of routes for each protocol, show to the control unit 100 of the network device 1
Assume that when the ip route summary command is executed, the result shown in FIG. 2 is obtained. In FIG. 2, “#” is a prompt for prompting a command. In this operation example, an object is defined as shown in FIG. 3 based on the execution result. More specifically, in the present embodiment, the following four objects are defined. First, an object corresponding to the show ip route summary command. To this object, “1.3.6.1.4.1.1182.2.6.2.1” is assigned as an object ID, and “yrcIpRouteSummary” is assigned as an alias of the object ID (a name given so that a person can easily identify it). The second trap is sent when the number of routes is changed. To this object, “1.3.6.1.4.1.1182.2.6.2.1.0.1” is assigned as an object ID, and “yrcIpRouteChangeTrap” is assigned as an alias for the object ID. The reason why “0” is used as the ID of the hierarchy immediately below the object ID indicating the first object is that the object is a trap. Third, there is an MIB variable that represents the total number of valid routes. To this object, “1.3.6.1.4.1.1182.2.6.2.1.1” is assigned as an object ID, and “yrcIpRouteActiveTotal” is assigned as an alias for the object ID. This object is a show
This is an object for displaying a numerical value (7 in the example shown in FIG. 2) displayed at the intersection of “total” and “valid” when the ip route summary command is executed. Fourth, there is an MIB variable that represents the total number of invalid routes. To this object, “1.3.6.1.4.1.1182.2.6.2.1.2” is assigned as an object ID, and “yrcIpRouteHiddenTotal” is assigned as an alias for the object ID. This object is a show
This is an object for displaying a numerical value (0 in the example shown in FIG. 2) displayed at the intersection of “total” and “invalid” when the ip route summary command is executed.

The user of the network device 1 first creates the definition file 230 using a text editor or the like, and stores it in a predetermined storage area of the nonvolatile memory 200 of the network device 1 in the storage area. For example, in this operation example, the definition file 230 shown in FIG. 4 is created and stored in a predetermined storage area of the nonvolatile memory 200. The definition file 230 shown in FIG. 4 is composed of eight blocks B01 to B08. These eight blocks are roughly classified into the following two types. First, the blocks are partitioned by character strings (“-[[” and “]]”) indicating comments in Lua. In the example shown in FIG. 4, blocks B01 to B05 correspond to this. Second, the block is partitioned by a function tag and an end tag. In the example shown in FIG. 4, blocks B06 to B08 correspond to this.
The meaning and description point of each block constituting the definition file 230 are as follows.

  Blocks B01 to B05 in FIG. 4 are blocks related to the definition of the object. More specifically, the block B01 is an object having an alias “yrcIpRouteSummary”, the block B02 is an object having an alias “yrcIpRouteActiveTotal”, the block B03 is an object having an alias “yrcIpRouteHiddenTotal”, and the block B05 is an alias. Corresponds to the "yrcIpRouteChangeTrap" object. Note that the object corresponding to the block B04 does not appear in FIG. 3, but this is an object one level above the object with the alias “yrcIpRouteChangeTrap”, and the trap for the object with the alias “yrcIpRouteSummary” is the object ID. It is determined as defined under “1.3.6.1.4.1.1182.2.6.2.1.0”.

  In the FROM tag included in common with the blocks B01 to B05 in FIG. 4, the object ID of the object one level above is set, and the ID under the object ID of the FROM is set in the ID tag. Then, an alias for the object ID is set in the NAME tag. In FIG. 4, ROOT means “1.3.6.1.4.1.1182.2.6.2”. For example, in the block B01, the alias of the object defined by the block is “yrcIpRouteSummary”, the object ID of the next higher layer is 1.3.6.1.4.1.1182.2.6.2, This means that the ID of the object is “1” (that is, the object ID of the object is “1.3.6.1.4.1.1182.2.6.2.1”). This is consistent with the description of FIG. The same applies to the blocks B02, B03 and B05.

The MIB variable type is set in the SYNTAX tags in the blocks B02 and B03 in FIG. In the example shown in FIG. 4, the 32-bit counter type is set as the type of the object (MIB variable) whose alias is “yrcIpRouteActiveTotal”, and the type of the object (MIB variable) whose alias is “yrcIpRouteHiddenTotal” is also a 32-bit counter. Set to type. In the PERMISSION tag, data indicating whether the MIB variable is read-only or readable / writable is set. In the example shown in FIG. 4, data indicating read only (read-only) is set in each case. The description text of the object is set in the DESCRIPTION tag in the blocks B02, B03, and B05, and the function name indicating the storage method of the value and the function name indicating the trap sending condition is set in the FUNCTION tag. . Note that the substance of these functions (the Lua script describing the processing procedure) is described in blocks (blocks B06 to B08 in the example shown in FIG. 4) partitioned by the function tag and end tag. For example, in the example shown in FIG. 4, the function entity with the function name “yrcIpRouteActiveTotal” is in block B06, the function entity with the function name “yrcIpRouteHiddenTotal” is in block B07, and the function entity with the function name “yrcIpRouteChangeTrap” is It is described in block B08. The OBJECT tag of block B04 describes the alias of the object to be monitored by the trap.
The above is the description point of the definition file 230.

  Various forms of the definition file 230 can be considered. As shown in FIG. 4, the definition of the object stored in the CPM and the processing procedure thereof may all be described in one definition file, distributed in a plurality of files, and the object ID has a small number of digits. It may take the form of being called from a definition file that defines. For example, FIG. 5 illustrates a case where the definition of the object with the alias yrcIpRouteActiveTotal and the definition of the object with the alias yrcIpRouteHiddenTotal are cut out from the definition file of FIG. When adding a new object to a network device to which a definition file has already been added by dividing the definition file into multiple files, the existing definition file is not edited. There is an advantage that it is only necessary to add a definition file, which can reduce operation mistakes and increase convenience. Further, a tabular data file shown in FIG. 6 may be used as the definition file.

  When the definition file 230 created in the above manner is stored in a predetermined storage area of the nonvolatile memory 200, the analysis unit 140 reads and analyzes the definition file 230, starts with a function tag, and ends with an end tag. A block (for example, the blocks B06 to B08 shown in FIG. 4) is extracted, and the description content of the block is a Lua script for monitoring the object. On the other hand, the file generation unit 150 extracts blocks (in the example shown in FIG. 4, blocks B01 to B05) enclosed by comment tags in the definition file 230, and extracts the CPM file 240 based on the description content of the blocks. Generate. For example, a block B10 of the CPM file 240 shown in FIG. 7 is a block related to a setting value defined by RFC or the like, and is determined regardless of the contents of the definition file 230. Block B11 in FIG. 7 contains the description content of block B01 in FIG. 4, block B12 in FIG. 7 contains the setting content in block B02 in FIG. 4, and block B13 in FIG. 7 contains the setting content in block B03 in FIG. Each is reflected, and the setting contents of blocks B04 and B05 in FIG. 4 are reflected in block B14 in FIG.

  The Lua script generated in the above manner is executed by the script execution means 120, and the script execution means 120 functions as the monitoring unit n (n = 1 to N). In response to a notification from the monitoring unit n (n = 1 to N), a process of adding a new object to the MIB tree 220 is executed by the agent unit 130, and storage and monitoring of values in the object are performed by the monitoring unit n (n = 1 to N). Thereafter, when there is an access to the CPM object from the monitoring device, the agent means 130 returns a response in the same manner as an access to another object. Needless to say, the CPM file 240 needs to be stored in the monitoring device prior to the start of monitoring by the monitoring device.

  As described above, according to the present embodiment, even a user who cannot obtain a PEN can freely customize the MIB according to his / her needs within the CPM range. In the present embodiment, an MIB file (CPM file 240) for the object is automatically generated in accordance with the addition of the object to the CPM. When a new object is added to the MIB, it is necessary to install an MIB file for the object in the monitoring apparatus, and the MIB file has been created manually. However, as shown in FIG. 7, the MIB file is described in a unique format, so even a vendor's expert engineer takes time to create it, and there are problems due to typographical errors, etc. There was also a lot to do. On the other hand, according to the present embodiment, the CPM file 240 is automatically generated based on the definition file 230. As is clear from comparison between FIGS. 4 to 6 and FIG. 7, the definition file 230 of this embodiment has a simpler format than the MIB file (CPM file 240). In comparison, the labor required for creation is reduced.

(B: Second embodiment)
(B-1: Ensuring consistency between network devices and monitoring devices that monitor their status)
FIG. 8 is a diagram illustrating a configuration example of the network device 1A according to the second embodiment of this invention.
In FIG. 8, the same components as those in FIG. 1 are denoted by the same reference numerals. As can be seen from a comparison between FIG. 8 and FIG. The management unit 160 is also a software module realized by the control unit 100. The management unit 160 notifies the predetermined destination that a change has occurred in the CPM, and executes processing for transmitting the CPM file 240 to the predetermined destination in response to a request from the predetermined destination. FIG. 9A is a sequence diagram showing operations of the network device 1A and the monitoring device 2 that monitors the status of the network device 1A. In the present embodiment, the monitoring device 2 is the predetermined destination, and the monitoring device 2 of the present embodiment executes a process of acquiring an MIB file from a network device in which a change has occurred in the CPM.

  As illustrated in FIG. 9A, which will be described in more detail, when a change occurs in the CPM by adding an object to the MIB tree 220 based on the definition file 230, the network device 1A changes to the CPM of its own device. Is notified to the monitoring device 2 by the management means 160 (FIG. 9A: SA100). As a communication protocol for this notification, HTTP or FTP may be used, and a dedicated protocol may be newly defined. Upon receiving the notification, the monitoring device 2 transmits a CPM file transmission request to the transmission source of the notification as shown in FIG. 9A (FIG. 9A: SA110). For this transmission request, a well-known communication protocol such as HTTP or FTP may be used, or a dedicated protocol may be newly defined. As shown in FIG. 9A, when the network device 1A receives the transmission request, the network device 1A reads the CPM file 240 (that is, the MIB file generated from the definition file 230 by the file generation unit 150) from the nonvolatile memory 200. And transmitted to the monitoring device 2 (FIG. 9A: SA120). The monitoring device 2 receives the CPM file 240 transmitted from the network device 1A, and monitors the state of the network device 1A using the CPM file 240. It is also possible to cause the monitoring apparatus 2 to acquire the definition file 230 instead of the CPM file 240.

According to the present embodiment, since the CPM file 240 is acquired by the monitoring device 2 in response to a change in the CPM of the network device 1A, the CPM file in the monitoring device 2 and the CPM file in the monitoring target network device 1A are obtained. Inconsistency can be avoided. Note that a new MIB variable for detecting the update of the MIB variable is defined in the network device 1A, and the monitoring device 2 is made to monitor the new MIB variable so that the monitoring device can detect that the CPM has changed. The CPM file transmission request may be transmitted to the monitoring device 2 in response to the detection. Further, by defining the following objects (a) to (c) in the network device 1A, the CPM file 240 generated in the network device 1A can be downloaded to the monitoring device 2 using SNMP. good.
(A) MIB variable for acquiring a CPM file (b) Trap for notifying CPM update (c) MIB variable for controlling a trap for notifying CPM update

  FIG. 9B is a diagram showing a flow of transmission processing of the CPM file 240 from the network device 1A to the monitoring device 2 realized using the above three types of objects. As shown in FIG. 9 (b), when the monitoring device 2 detects the update of the CPM by receiving the trap (b) (FIG. 9 (b): SA200), the monitoring device 2 sends a GET request to the MIB variable (a). (FIG. 9B: SA210) is transmitted. Upon receiving this GET request, the agent means 130 of the network device 1A returns a CPM file 240 in response to the GET request (FIG. 9 (b): SA220). The monitoring device 2 receives the CPM file 240 transmitted from the network device 1A, and monitors the state of the network device 1A using the CPM file 240. Also according to this aspect, it is possible to avoid a mismatch between the CPM file in the monitoring device 2 and the CPM file in the network device 1A to be monitored. Similarly, the monitoring device 2 can acquire the definition file 230 instead of the CPM file 240.

(B-2: Ensuring consistency between multiple network devices)
In addition, a plurality of network devices 1A to be monitored by the monitoring device 2 (in the example shown in FIG. 10, network devices 1A-1 and 1A-2) may share the latest definition file 230 via the monitoring device 2. Is possible. Note that it is preferable that the latest definition file 230 is shared by a plurality of network devices to be monitored by the monitoring device 2 after the acquisition of the CPM file 240 by the monitoring device 2 is completed. In this case, the monitoring device 2 stores the definition file 230 for the network device (in the example illustrated in FIG. 10, the network device 1A-1) in which the CPM has changed among the plurality of network devices to be monitored by the own device. A transmission request (FIG. 10: SA300) is transmitted. At this time, for this transmission request, a well-known communication protocol such as HTTP or FTP may be used, or a dedicated protocol may be defined.

  As illustrated in FIG. 10, the network device 1A-1 that has received the transmission request transmits the definition file 230 (hereinafter referred to as definition file 230A) of the own device to the monitoring device 2 by the management unit 160 (FIG. 10: SA310). For the transmission of the definition file 230A, a known communication protocol such as HTTP or FTP may be used, or a dedicated protocol may be defined. Upon receiving the definition file 230A transmitted from the network device 1A-1, the monitoring device 2 sends the definition file 230A to a network device other than the network device that is the transmission source (in this embodiment, the network device 1A-2). Transmit (FIG. 10: SA320). The network device 1A-2 has the same CPM and CPM file as the network device 1A-1 by updating the CPM and generating the CPM file based on the definition file 230A received from the monitoring device 2.

  Note that the monitoring device 2 may monitor whether the CPM has been updated by causing the monitoring device 2 to monitor the definition of the MIB variables of the network devices 1A-1 and 1A-2. In addition, the network device 1A in which the definition file 230 has been updated is transferred to another network device (which may be a network device at another base regardless of whether or not it is a monitoring target by the monitoring device 2). The definition file 230 may be transmitted. In addition, the management unit 160 of the network device 1A may execute a process of downloading and acquiring the definition file uploaded to the monitoring device 2. Protocols for realizing this download include well-known protocols such as HTTP and FTP. A communication protocol may be used, and a dedicated protocol may be defined.

Using the objects (a) to (c) described above and sharing the CPM file 240 using SNMP, the definition file 230 can also be shared. In this case, however, it is necessary to define the following object (d) in addition to the objects (a) to (c).
(D) MIB Variable for Reading / Writing Definition File FIG. 11 is a flowchart showing the flow of operations of the network devices 1A-1, 1A-2 and the monitoring device 2 in this case. Hereinafter, the case where CPM update based on the definition file 230 is performed in the network device 1A-1 will be described.

  As shown in FIG. 11, the monitoring device 2 sends a GET request (FIG. 11: SA400) to the MIB variable (a) for the network device (in this example, the network device 1A-1) in which the CPM has been updated. ) To obtain the definition file 230 from the network device 1A-1 (FIG. 11: SA410). Next, the monitoring device 2 requests a stop (SET) so as not to send a trap to the MIB variable in (c) above with respect to another network device to be monitored (in this example, the network device 1A-2). Request) is transmitted (FIG. 11: SA420). When the monitoring device 2 receives the response to the stop request (FIG. 11: SA430), the monitoring device 2 sends the SET request (FIG. 11: SA440) of the definition file 230 acquired from the network device 1A-1 to the above ( d) Send to the MIB variable. Then, the monitoring device 2 waits for a response (FIG. 11: SA450) from the network device 1A-2, and when receiving the response, the MIB of (c) of the network device 1A-2 restarts the transmission of the trap. A SET request is transmitted to the variable (FIG. 11: SA460). Then, the monitoring device 2 waits for reception of the SET request (FIG. 11: SA470) and completes this operation. In this operation example, the trap transmission is temporarily stopped in order to prevent the trap from being transmitted due to the addition of the object to the CPM based on the definition file 230.

  As described above, according to the present embodiment, as in the first embodiment described above, even a user who cannot obtain a PEN can freely customize the CPM according to his / her needs. In addition, the definition file 230 (or CPM file 240) is inconsistent between the network device 1A and the monitoring device 2 that monitors the status thereof, or between the plurality of network devices 1A to be monitored by the monitoring device 2. Occurrence can be prevented, and the latest definition file 230 (or CPM file 240) can be used by each device.

(C: deformation)
Although one embodiment of the present invention has been described above, it goes without saying that the following modifications may be added to this embodiment.

(1) In the above embodiment, the case where the definition file is created by coding using a text editor has been described. However, when a user I / F unit 300 having a display unit such as a liquid crystal display and an operation unit such as a keyboard or a mouse is provided as in the network device 1B shown in FIG. The user may be allowed to create a definition file. FIG. 13A is a diagram showing an example of a GUI screen for defining MIB variables. A user who visually recognizes this GUI screen inputs the name of the MIB variable in the name column and the description of the MIB variable in the description column by a keyboard operation or the like. In addition, in the script field of FIG. 13A, a script path representing the processing procedure for the MIB variable can be directly input, but a list of paths is displayed by pressing the reference button, and the list of the list is displayed. You can also select and input from home. Similarly, in the type column, it is possible to directly input a character string representing the type of the MIB variable, but when the list button LB1 (or LB2) is pressed, the selection item list ML1 is displayed and the selection item list ML1 is displayed. It is also possible to select a desired one from the molds displayed on the screen. When SEQUENCE is selected as the MIB variable type in the selection item list ML1, the screen is switched to a GUI screen for defining a Table type MIB variable shown in FIG. 13B. FIG. 13C is a GUI screen for defining a trap. The operations for each of the name field, the description field, and the script field in FIG. 13C and the role of each field are the same as those in FIG. The object 1 column, the object 2 column,..., The object 5 column are fields for inputting the name of the object to be monitored by the trap, and can be selected and input by the selection item list ML2 in the same manner as the type column described above. It is. As described above, according to the aspect in which the definition file 230 is created by inputting the MIB variable and the trap definition information by the operation on the GUI screen, the definition file can be further created as compared with the form created by the coding using the text editor. It becomes easy.

(2) In the second embodiment, the network device 1A and the monitoring device 2 that monitors the state thereof share the CPM file 240 (or definition file 230), and a plurality of network devices to be monitored by the monitoring device 2 (In the second embodiment, the aspect in which the network devices 1A-1 and 1A-2) share the CPM file 240 (or the definition file 230) has been described. However, the CPM file 240 can be shared by a plurality of monitoring devices 2 via the server device. Specifically, the CPM file is stored in a server device that can be accessed by each of the plurality of monitoring devices 2 via the communication network. Then, as shown in FIG. 14A, each monitoring device 2 monitors whether or not the CPM file stored in the server device is updated, and executes a process of downloading when an update is detected. At this time, a well-known communication protocol such as HTTP or FTP may be used for checking whether the CPM file has been updated or acquiring (downloading) the CPM file from the server device, and a dedicated protocol may be defined separately. .

  Here, as a specific method of storing the CPM file in the server device, as shown in FIG. 14B, the server device stores the CPM file in the monitoring device 2-1 that has acquired the CPM file from the network device 1A. Can be uploaded to This upload may also be realized using a known communication protocol such as HTTP or FTP, or a dedicated protocol may be defined separately. According to the mode shown in FIG. 14B, when the monitoring device 2-1 uploads the CPM file to the server device, the monitoring device 2-2 receives the CPM file generated at another site via the server device. Can be acquired. Further, as shown in FIG. 14C, the CPM file may be uploaded to the server device by the network device.

(3) As shown in FIG. 15, the CPM file 240 may be transmitted and received between the monitoring device 2-1 and the monitoring device 2-2. Further, by setting the predetermined destination in the second embodiment as a server device that can be accessed by the network device 1A, for example, the definition file 230 of the network device 1A is transferred to the management unit 160 of the network device 1A-1 to the server device. The uploading process is executed, and the management unit 160 of the network device 1A-2 executes the process of downloading the definition file 230 from the server device, thereby defining the plurality of network devices 1A via the server device. The file 230 can be shared.

(4) In the above embodiment, SNMP is used as a protocol for causing the monitoring device to monitor the status of the network device 1. However, any protocol that realizes status monitoring by MIB may be used, and is not limited to SNMP. Absent. In the above embodiment, the definition file 230 is described using Lua. However, the definition file 230 may be described in another script language or may be described in a meta language.

(5) In the above embodiment, the case has been described in which the CPM that is a range predetermined by the vendor in the private MIB is customized. However, the entire private MIB can of course be used as the CPM. Also, for the standard MIB, a new object can be added in terms of mechanism by applying the method of the above embodiment. For this reason, it is expected that the review of the standard MIB (addition of new objects, etc.) can be flexibly dealt with by applying the present invention in the future.

  DESCRIPTION OF SYMBOLS 1,1A, 1B ... Network equipment, 2 ... Monitoring apparatus, 100 ... Control part, 110 ... Relay control means, 120 ... Script execution means, 130 ... Agent means, 140 ... Analysis means, 150 ... File generation means, 160 ... Management Means 200 ... Non-volatile memory 210 ... Private MIB customization program 220 ... MIB tree 230 ... Definition file 240 ... CPM file 300 ... User I / F unit

Claims (6)

Analyzes a definition file that defines the definition of an object stored in the MIB and a processing procedure for the object, assigns an object ID to the object, and generates a script for realizing the process for the object Means,
File generation means for extracting an object definition from the definition file and generating an MIB file for the object;
Script execution means for executing a script generated by the analysis means and processing an object;
An agent that assigns an object ID assigned by the analyzing means to an object specified in the definition file and adds the object ID to the MIB, while mediating access to the object by a monitoring device that monitors the state of the network device Means,
A network device characterized by comprising:   2. The network device according to claim 1, further comprising a management unit that transmits at least one of the MIB file generated by the file generation unit and the definition file to a predetermined destination.   The management means notifies the predetermined destination that a change has occurred in the MIB, and at least one of the MIB file generated by the file generation means and the definition file in response to a request from the predetermined destination The network device according to claim 2, wherein the network device transmits to the predetermined destination.   The management means obtains at least one of a definition file in which a definition of an object stored in the MIB and a processing procedure for the object is defined, and an MIB file for the object from the predetermined destination. The network device according to claim 1, wherein the network device is a device.   5. The network device according to claim 1, further comprising user interface means for allowing a user to create the definition file through a GUI-based operation. 6. A monitoring device that accesses the MIB of a network device and monitors the status of the network device,
A definition file in which the definition of the object stored in the MIB of the network device and the processing procedure for the object are defined from the network device in which the MIB has changed among the network devices to be monitored, and the MIB file for the object A monitoring device that executes a process of acquiring at least one of them.

Images