Monitoring support device, monitoring support method, and network operation system

Abstract

To facilitate appropriate monitoring settings for a monitoring apparatus which is configured to monitor a connection state of a network device.SOLUTION: A monitoring support apparatus executes: setting change detection processing which acquires a modified device setting value of a network device and a device setting object corresponding to the modified device setting value; and monitoring setting calculation processing which acquires monitoring setting value information generated by associating the device setting object of the network device, the device setting value corresponding to the device setting object, a monitoring service function which is the name of a monitoring type of the network device, and a monitoring setting value, acquires, from the monitoring setting value information, the monitoring service function and the monitoring setting value associated with the modified device setting value of the network device and the device setting object corresponding to the modified device setting value, which are acquired in the setting change detection processing, and generates monitoring setting including the monitoring service function and the monitoring setting value acquired.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a monitoring support device, a monitoring support method, and a network operation system in which a monitoring device that monitors the connection status of network devices generates monitoring settings for monitoring the network devices. [Background technology]

[0002] A variety of devices are connected to a computer network (hereafter referred to as a network). Device monitoring is performed to ensure that the devices connected to the network are operating properly, and there are technologies for monitoring these devices.

[0003] For example, in the technology described in Patent Document 1, agent software is deployed to the computers to monitor the operation status of applications that make up a system built on computers connected to a network and send monitoring information about the operation status of the applications to a monitoring server. When the monitoring server detects that a computer has been changed or added, it deploys agent software to the changed or added computer. This makes it possible to monitor a system of computers connected to a network. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 1015-161954 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, the technology described in Patent Document 1 can monitor the operating status of a computer system, but cannot monitor the connection status of network devices that transmit data over a network. In many cases, computers connected to a network are connected to network devices, and the operating status of the computers may be affected by the connection status of the network devices. Therefore, in order to prevent a decrease in the operating status of computers connected to a network due to an abnormality in the network devices, it is necessary to monitor the connection status of the network devices, and a monitoring device is used to monitor the connection status of the network devices.

[0006] To properly monitor network devices, it is necessary to change the monitoring settings of the monitoring device in response to configuration changes such as changes to the network device settings and addition or removal of devices connected to the network. Network devices have a variety of configuration items, and reducing the amount of work required to change the monitoring settings and preventing configuration errors are challenges. Therefore, there is a demand for technology that makes it easy to set monitoring settings in monitoring devices.

[0007] An object of the present invention is to provide a monitoring support device, a device monitoring setting method, and a network operation system that facilitate the setting of monitoring settings in a monitoring device that monitors the connection status of network devices. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, one aspect of the monitoring support device of the present invention is a monitoring support device that monitors the connection status of network devices that transmit data and are connected to a network, and generates monitoring settings for monitoring the network devices, and the monitoring support device includes a processor. The processor executes a setting change detection process that acquires changed device setting values ​​of the network device and device setting targets for the changed device setting values, and a monitoring setting calculation process that acquires monitoring setting value information that associates the device setting targets of the network device, the device setting values ​​for the device setting targets, and monitoring service functions and monitoring setting values ​​that are names of monitoring types of the network device, acquires from the monitoring setting value information the monitoring service functions and monitoring setting values ​​that are associated with the changed device setting values ​​of the network device and the device setting targets for the changed device setting values ​​acquired in the setting change detection process, and generates the monitoring settings that include the acquired monitoring service functions and monitoring setting values.

[0009] Furthermore, one aspect of the monitoring support method for a monitoring support device of the present invention is a monitoring support method in a monitoring support device that monitors the connection status of network devices that transmit data and are connected to a network, and generates monitoring settings for monitoring the network devices, and executes a setting change detection process that acquires changed device setting values ​​of the network devices and device setting targets for the changed device setting values, and a monitoring setting calculation process that acquires monitoring setting value information that associates the device setting targets of the network devices, the device setting values ​​for the device setting targets, and monitoring service functions and monitoring setting values ​​that are names of monitoring types of the network devices, acquires the monitoring service functions and monitoring setting values ​​that are associated with the changed device setting values ​​of the network devices and the device setting targets for the changed device setting values ​​acquired in the setting change detection process from the monitoring setting value information, and generates the monitoring settings that include the acquired monitoring service functions and monitoring setting values. [Effects of the Invention]

[0010] According to the present invention, it is possible to easily set monitoring settings in a monitoring device that monitors the connection status of network devices. Problems, configurations, and effects other than those described above will become apparent from the following description of the preferred embodiments of the invention. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic system configuration of a network operation system. [Figure 2] FIG. 1 is a diagram illustrating an example of a functional configuration diagram of a network operation system. [Figure 3] FIG. 1 is a diagram showing an example of a hardware and software configuration diagram of a network operation system. [Figure 4] FIG. 10 is a diagram illustrating an example of a target device information table. [Figure 5] FIG. 10 is a diagram illustrating an example of a device setting value table. [Figure 6] FIG. 10 illustrates an example of a monitoring setting item table. [Figure 7] FIG. 10 illustrates an example of a monitoring service information table. [Figure 8] FIG. 10 is a diagram illustrating an example of a pre-change device setting value table. [Figure 9] FIG. 10 is a diagram illustrating an example of a device setting value difference table. [Figure 10] FIG. 10 is a diagram illustrating an example of a setting item relation database. [Figure 11] FIG. 10 illustrates an example of a monitoring setting item summary table. [Figure 12A] FIG. 10 is a diagram illustrating an example of a device configuration information table. [Figure 12B] FIG. 1 illustrates an example of a topology. [Figure 13] FIG. 10 is a diagram illustrating an example of a device configuration relationship table. [Figure 14] FIG. 10 illustrates an example of a monitoring setting script template. [Figure 15] FIG. 10 illustrates an example of a monitoring setting script. [Figure 16]FIG. 10 illustrates an example of a flowchart showing a monitoring setting change process. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments will be described with reference to the drawings. The examples are illustrative of the present invention, and some omissions and simplifications have been made for clarity of explanation. The present invention is not limited to the examples, and the technical scope of the present invention includes all application examples that are consistent with the concept of the present invention.

[0013] In the drawings and the following description, the same parts or parts having similar functions may be given the same reference numerals, may be explained by adding different subscripts to the same reference numerals, or may be explained by omitting the subscripts. Furthermore, unless otherwise specified, each component may be plural or singular.

[0014] To facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0015] In the following description, various types of information may be described using expressions such as "table," "list," and "queue," but the various types of information may be expressed using data structures other than these. Furthermore, to indicate that the various types of information are independent of the data structure, "table" and the like may be referred to as "management information." Identification information may be described using expressions such as "identification information," "identifier," "name," "ID," and "number," but these are interchangeable.

[0016] Processing may also be described using sentences with a "program" or a "functional unit" as the subject. The program or functional unit is executed by a processor, which is a processing unit or computing unit, such as a microprocessor (MP), central processing unit (CPU), or graphics processing unit (GPU), and performs a specified process. The processor performs the process using storage resources (e.g., memory) and communication interface devices (e.g., communication ports). For this reason, the subject of a sentence with a "program" or a "functional unit" as the subject may be replaced with a processor, processing unit, or computing unit. The entity that executes the program and performs the process may be a processor, computing unit, or processing unit, or a controller, device, system, computer, or node that has a processor, or a dedicated circuit that performs a specific process. Here, the dedicated circuit may be, for example, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a complex programmable logic device (CPLD). [Example]

[0017] The network operation system 1 of this embodiment can perform network settings, monitor connection states, and change monitoring settings in response to changes in network settings for the network devices 10 that transmit data over the network.

[0018] <<System Configuration Overview of Network Operation System 1>> FIG. 1 is an example of a schematic system configuration diagram of a network operation system 1. The network operation system 1 operates a network device 10 connected to a network NW1. The network device 10 is connected to a connection device 11 used for information processing. The network operation system 1 includes, for example, a setting device 100 used to set the network device 10, a monitoring device 200 used to monitor the network device 10, and a monitoring support device 300 used to set the monitoring of the monitoring device 200. These are connected together with the network device 10 via networks NW1 and NW2. A monitoring terminal 250 connected to the monitoring device 200 via network NW2 is used to acquire monitoring information from the monitoring device 200.

[0019] A network device administrator who configures the network device 10 operates the configuration device 100 to configure the network settings of the network device 10. The network device administrator is, for example, one or more persons who manage a corporate system including the network device 10 at a company that has introduced the network device 10.

[0020] An operator who operates the network operation system 1 can operate the network operation system 1 by operating the monitoring terminal 250. The operator is, for example, one or more persons who provide a network operation service.

[0021] The network device 10 is connected to the network NW1 and is a device, such as an L2 switch, an L3 switch, or a router, for transmitting data between computers, such as servers, in the network. The network device 10 is used by a network device administrator, and one or more network devices 10 are installed in the network NW1.

[0022] The connection device 11 is a device used for information processing that is connected to the network device 10. The connection device 11 is, for example, a server, a client, or other device.

[0023] The setting device 100 is a device that creates a parameter list (device setting value table 112, described later) for changing the settings of the network device 10 based on a network device setting request input by a network device administrator, and then changes the settings of the network device 10. Here, the setting change parameter list is a list of parameters that can be set in the network device 10 and their setting values, in order to change the settings of the network device 10 (settings related to data transfer). When the setting device 100 changes the settings of the network device 10, it transmits information to the monitoring support device 300 that the settings have been changed.

[0024] The monitoring device 200 is a device that executes monitoring of the network devices 10. The monitoring device 200 receives input of monitoring service settings, such as whether or not to execute monitoring and the monitoring interval, based on the monitoring service contracted by a user (such as a network device administrator) of the network operation system 1, and executes monitoring of the network devices 10 in accordance with the monitoring service settings.

[0025] The monitoring support device 300 monitors whether the setting device 100 changes the network settings of the network device 10, and detects that the settings have been changed.The monitoring support device 300 then compares the parameter list of the setting device 100 before the setting change with the parameter list after the setting change, and extracts the setting values ​​that have been changed in the parameter list.Furthermore, the monitoring support device 300 detects information about devices whose placement has been changed, that is, devices (network device 10 or connected device 11) that have been deleted or added before and after the setting change.

[0026] Furthermore, the monitoring assistance device 300 calculates changes to the monitoring settings of the monitoring device 200 based on the changed setting values ​​in the parameter list, the monitoring setting rules for those setting values ​​and parameters, information about the device whose placement has been changed, and the monitoring setting rules for the device whose placement has been changed. The monitoring assistance device 300 then notifies the operator of the network operation system 1 of the changes to the monitoring settings by sending the changes to the monitoring settings to the monitoring terminal 250. Furthermore, the monitoring assistance device 300 generates a monitoring setting script from the changes to the monitoring settings that causes the monitoring device 200 to change the monitoring settings. The monitoring assistance device 300 then executes the monitoring setting script to cause the monitoring device 200 to change the monitoring settings of the network device 10.

[0027] The monitoring terminal 250 is an information processing device, such as a smartphone, tablet, laptop, or desktop PC. The monitoring terminal 250 can send and receive information to and from the monitoring device 200 and the monitoring support device 300, and can display a monitoring setting screen and monitoring results. The operator of the network operation system 1 can check the information displayed on the monitoring terminal 250 and grasp the setting work for the monitoring device 200, information on the monitoring status of the network device 10, and changes to the monitoring settings sent from the monitoring support device 300.

[0028] The networks NW1 and NW2 may be wired networks or wireless networks. The network NW1 is, for example, a local area network (LAN). The network NW2 is, for example, a global network such as the Internet.

[0029] <<System configuration of network operation system 1>> Next, the configuration of the network operation system 1 will be described with reference to Figures 2 and 3. Figure 2 is a diagram showing an example of a functional block diagram of the network operation system 1. Figure 3 is a block diagram showing an example of a hardware configuration of the network operation system 1. Note that connection device 11 is not shown in Figures 2 and 3.

[0030] <Configuration of setting device 100> As shown in Fig. 2, the setting device 100 has, as its functional configuration, a setting information management unit 101, a device setting unit 102, and a storage unit 103. As shown in Fig. 3, the setting device 100 has, as its hardware configuration, a processor 121, a main storage unit 122, a secondary storage unit 123, a communication I / F (Interface) 124, and a bus 125 connecting these. The setting device 100 can be realized by an information processing device such as a general server device.

[0031] The processor 121 controls each unit of the setting device 100, reads data and programs stored in the sub-storage device 123 into the main storage device 122, and executes processing defined by the programs. The setting information management unit 101 described above with reference to FIG. 2 is realized by the processor 121 reading a setting information management program 101a stored in the sub-storage device 123 (described later) into the main storage device 122 and executing it. The device setting unit 102 is realized by the processor 121 reading a device setting unit program 102b stored in the sub-storage device 123 (described later) into the main storage device 122 and executing it. In this specification, when describing processing using a sentence with the setting information management unit 101 or the device setting unit 102, which are functional units, as the subject, it indicates that the processor 121 of the setting device 100 is executing the programs 101a and 102a that implement the functional units.

[0032] The main memory device 122 is a RAM or the like, has a volatile memory element, and stores the programs executed by the processor 121 and data.

[0033] The secondary storage device 123 is a device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) that has a non-volatile storage element and stores programs, data, etc. The secondary storage device 123 is the storage unit 103 described above. The secondary storage device 123 stores a setting work information DB 110. The setting work information DB 110 is a database that stores various information managed by the setting device 100. Details will be described later using Figures 4 and 5, but the setting work information DB 110 stores a target device information table 111 and a device setting value table 112.

[0034] Additionally, a setting information management program 101a and a device setting program 102a are installed in the secondary storage device 123. As described above, the setting information management program 101a and the device setting program 102a are programs that are executed by the processor 121 to realize the functions of the setting information management unit 101 and the device setting unit 102.

[0035] The communication I / F 124 is connected to the networks NW1 and NW2 and is an interface (transmitting / receiving device) that can transmit and receive data via the networks NW1 and NW2 with devices such as the network device 10 and the monitoring support device 300. Using the communication I / F 124, the setting device 100 can transmit and receive data via the networks NW1 and NW2 with devices such as the network device 10 and the monitoring support device 300.

[0036] The setting information management unit 101 is a functional unit that acquires and manages a parameter list (device setting value table 112) used to configure the network device 10 from a network device administrator.

[0037] The device setting unit 102 is a functional unit that changes the settings of the network device 10 based on the parameter list (device setting value table 112). The settings are changed automatically, for example, by creating a script for changing the settings.

[0038] The storage unit 103 is a secondary storage device 123, and is a functional unit that stores data such as a target device information table 111 and a parameter list (device setting value table 112).

[0039] <Configuration of monitoring device 200> As shown in Fig. 2, the monitoring device 200 has, as its functional configuration, a device monitoring unit 201, a monitoring setting unit 202, and a storage unit 203. As shown in Fig. 3, the monitoring device 200 has, as its hardware configuration, a processor 221, a main storage device 222, a secondary storage device 223, a communication I / F 224, and a bus 225 connecting these, similar to the setting device 100. The monitoring device 200 can be realized by an information processing device such as a general server device.

[0040] The secondary storage device 223 is the above-mentioned storage unit 203. The secondary storage device 223 stores a monitoring setting information DB 210. The monitoring setting information DB 210 is a database that stores various types of information managed by the monitoring device 200. The monitoring setting information DB 210 stores a monitoring setting item table 211.

[0041] Furthermore, a device monitoring program 201a and a monitoring setting program 202a are installed in the secondary storage device 223. The device monitoring unit 201 and the monitoring setting unit 202 described above with reference to Fig. 2 are realized by the processor 221 reading the device monitoring program 201a and the monitoring setting program 202a stored in the secondary storage device 223 into the main storage device 222 and executing them. In this specification, when a process is described using a sentence with the device monitoring unit 201 and the monitoring setting unit 202, which are functional units, as the subject, it indicates that the processor 221 of the monitoring device 200 is executing the device monitoring program 201a and the monitoring setting program 202a that realize the functional units.

[0042] The device monitoring unit 201 is a functional unit that executes monitoring of the connection status of the network device 10 in a monitoring service, such as alive monitoring and status monitoring of the network device 10. For example, alive monitoring executes confirmation of ping responses, and status monitoring executes confirmation of CPU and memory usage rates using SNMP.

[0043] The monitoring setting unit 202 is a functional unit that sets up monitoring for each monitoring service. The monitoring setting unit 202 saves settings such as whether to perform monitoring and the monitoring interval, which are input using a GUI, CLI, script, etc.

[0044] The storage unit 203 is a secondary storage device 223 and is a functional unit that stores data. As described above, the storage unit 203 stores the monitoring setting information DB 210 that stores the monitoring setting item table 211.

[0045] <Configuration of monitoring support device 300> 2, the monitoring support device 300 has, as its functional configuration, a setting change detection unit 301, a monitoring setting calculation unit 302, and a storage unit 303. As shown in Fig. 3, the monitoring support device 300 also has, as its hardware configuration, a processor 321, a main storage device 322, a secondary storage device 323, a communication I / F (Interface) 324, and a bus 325 connecting these, similar to the setting device 100. The monitoring support device 300 can be realized by an information processing device such as a general server device.

[0046] The secondary storage device 323 is the storage unit 303 described above. The secondary storage device 323 stores a relationship management information DB 310. The relationship management information DB 310 is a database that stores various information managed by the monitoring support device 300. The relationship management information DB 310, details of which will be described later using FIGS. 4 and 7 to 15, stores a target device information table 311, a monitoring service information table 312, a pre-change device setting value table 313, a device setting value difference table 314, a setting item relationship database 315, a monitoring setting item aggregation table 316, a device configuration information table 317, a device configuration relationship table 318, a monitoring setting script template 319, and a monitoring setting script 320.

[0047] 2 is realized by the processor 321 reading the setting change detection program 301a stored in the sub-storage device 323 into the main storage device 322 and executing it. Furthermore, the monitoring setting calculation unit 302 is realized by the processor 321 reading the monitoring setting calculation program 302a stored in the sub-storage device 323 into the main storage device 322 and executing it. In this specification, when a process is described using a sentence with the setting change detection unit 301 or the monitoring setting calculation unit 302, which are functional units, as the subject, it means that the processor 321 of the monitoring support device 300 is executing the setting change detection program 301a and the monitoring setting calculation program 302a that realize the functional units.

[0048] The setting change detection unit 301 is a functional unit that monitors setting changes of the network device 10 made by the setting device 100, detects that a setting change has been made, and extracts the changed parameters and their setting values ​​(device setting value difference table 314) based on the parameter list of the network device 10 before the setting change and the parameter list of the network device 10 after the setting change.

[0049] The monitoring setting calculation unit 302 is a functional unit that determines the required monitoring setting items and setting values ​​based on the changed parameters and their setting values ​​(device setting value difference table 314), the monitoring service information table 312, the relationship rules between network device parameters and multiple monitoring service setting items (setting item relationship database 315), and the monitoring setting rules for the network configuration (device configuration relationship table 318), generates a monitoring setting script based on the monitoring service information and a monitoring setting script template, and changes the settings of the monitoring service provided by the monitoring device 200.

[0050] The memory unit 303 is a secondary storage device 323 and is a functional unit that stores data. The memory unit 303 stores the above-mentioned change work information DB 310. As described above, the change work information DB 310 stores a target device information table 311, a monitoring service information table 312, a pre-change device setting value table 313, a device setting value difference table 314, a setting item relationship database 315, a monitoring setting item summary table 316, a device configuration information table 317, a device configuration relationship table 318, a monitoring setting script template 319, and a monitoring setting script 320.

[0051] The monitoring support device 300 may be configured to function as the monitoring device 200 by adding the configuration of the monitoring device 200. The monitoring support device 300 may be configured to function as both the setting device 100 and the monitoring device 200 by adding the configurations of the setting device 100 and the monitoring device 200.

[0052] <<Data structure of network operation system 1>> Next, the data structures of various data used in the network operation system 1 will be described with reference to FIGS.

[0053] 4 is a diagram showing an example of the data configuration of the target device information table 111. The target device information table 111 manages information about the network devices 10 that are the targets of setting changes and monitoring, and has the following fields: device ID 401, model ID 402, model 403, access information 404, login ID 405, and password 406.

[0054] Device ID 401 is a field that stores, as a value, identification information (device ID) that uniquely identifies the network device 10 used by the network device administrator. Model ID 402 is a field that stores, as a value, identification information (model ID) that uniquely identifies the type of network device 10. Model 403 is a field that stores, as a value, information that describes the model. Access information 404 is a field that stores, as a value, the IP (Internet Protocol) address and port number of the network device 10 that are used for managing the network device 10. Login ID 405 is a field that stores, as a value, user identification information (login ID) for logging in to the network device 10. Password 406 is a field that stores, as a value, a password for logging in to the network device 10.

[0055] The data configuration of the target device information table 111 is the same as that of the target device information table 311 stored in the monitoring assistance device 300 .

[0056] 5 is a diagram showing an example of the data configuration of the device setting value table 112. The device setting value table 112 is a table for managing setting information set in the network device 10 by the setting device 100. The setting device 100 updates the device setting value table 112 every time the settings of the network device 10 are changed.

[0057] The device setting value table 112 has the following fields: device ID 501, device setting target 502, device parameter 503, and device setting value 504. The device ID 501 is a field that stores, as a value, identification information (device ID) that uniquely identifies the network device 10 used by the network device administrator. The device setting target 502 is a field that stores, as a value, a setting target for setting the setting value of a parameter of the network device 10. The device parameter 503 is a field that stores, as a value, the name of a parameter that can be set for the device setting target 502. The device setting value 504 is a field that stores, as a value, the setting value of the device parameter 503.

[0058] FIG. 6 is a diagram showing an example of the data configuration of the monitoring setting item table 211. The monitoring setting item table 211 is a table for managing setting information for monitoring services. The monitoring setting item table 211 has the following fields: a device ID 601, a monitoring service function 602, a contract 603, a monitoring setting item 604, and a monitoring setting value 605. The device ID 601 is a field that stores identification information (device ID) that uniquely identifies the network device 10 that is the target of monitoring by the monitoring service function 602. The monitoring service function 602 is a field that stores, as a value, the name of the monitoring type that uniquely identifies the type of monitoring. The contract 603 is a field that stores, as a value, whether or not there is a contract between the network device administrator and the operator regarding whether or not to execute monitoring of the monitoring service function 602. If there is a contract (currently being executed), the value is "current", and if there is no contract (currently not being executed), the value is "current". That is, the contract existence 603 is a field that stores information on whether or not monitoring of the monitoring service function 602 is being executed. The monitoring setting item 604 is a field that stores, as a value, an item that can be set for the monitoring service function 602 (monitoring type). The monitoring setting value 605 is a field that stores, as a value, the setting value of the monitoring setting item 604.

[0059] The data configuration of the monitoring setting item table 211 is the same as that of the monitoring setting item summary table 316 stored in the monitoring support device 300 .

[0060] The data configuration of the target device information table 311 is the same as that of the target device information table 111 described with reference to FIG. 4, and therefore a description of the target device information table 311 will be omitted.

[0061] 7 is a diagram showing an example of the data configuration of the monitoring service information table 312. The monitoring service information table 312 is a table for managing information on monitoring services that can be provided by the operator and monitoring services to which the network device administrator has made a contract.

[0062] The monitoring service information table 312 has the following fields: service ID 701 , monitoring service function 702 , contract status 703 , access information 704 , login ID 705 , password 706 , monitoring condition item 707 , and monitoring condition value 708 .

[0063] The service ID 701 is associated with the monitoring service function 702 and is a field that stores identification information (service ID) that uniquely identifies the monitoring service function 702. The monitoring service function 702 is a field that stores, as a value, the name of the monitoring type that uniquely identifies the type of monitoring. The contract existence / nonexistence 703 is a field that stores, as a value, whether or not there is a contract between the network device administrator and the operator regarding whether or not monitoring of the monitoring service function 702 will be performed, and the value is "existent" if there is a contract (currently being performed), and the value is "absent" if there is no contract (not currently being performed). In other words, the contract existence / nonexistence 703 is a field that stores information on whether or not monitoring of the monitoring service function 702 is currently being performed.

[0064] The access information 704 is a field that stores, as values, the IP address and port number of the monitoring device 200 used to monitor the network device 10. The login ID 705 is a field that stores, as a value, user identification information (login ID) for logging in to the monitoring device 200. The password 706 is a field that stores, as a value, a password for logging in to the monitoring device 200. The access information 704, login ID 705, and password 706 described above are information necessary for the monitoring support device 300 to access the monitoring device 200.

[0065] The monitoring condition item 707 is a field that stores, as a value, an item of a monitoring condition that can be set for each monitoring service function (monitoring type). The monitoring condition value 708 is a field that stores, as a value, a setting value of the monitoring condition for the monitoring condition item 707.

[0066] 8 is a diagram showing an example of the data configuration of the pre-change device setting value table 313. The pre-change device setting value table 313 is a table for managing setting information of the network device 10 before a setting change. The pre-change device setting value table 313 has the following fields: device ID 801, device setting target 802, device parameter 803, and device setting value 804. The device ID 801 is a field that stores, as a value, identification information (device ID) that uniquely identifies the network device 10 used by the network device administrator. The device setting target 802 is a field that stores, as a value, a setting target for which the setting value of a parameter of the network device 10 is to be set. The device parameter 803 is a field that stores, as a value, the name of a parameter that can be set for the device setting target 802. The device setting value 804 is a field that stores, as a value, the setting value of the device parameter 803.

[0067] 9 is a diagram showing an example of the data configuration of the device setting value difference table 314. The device setting value difference table 314 manages setting information that differs before and after a setting change of the network device 10 (i.e., information about the changed setting). The device setting value difference table 314 has the following fields: device ID 901, device setting target 902, device parameter 903, and device setting value 904. The device ID 901 is a field that stores, as a value, identification information (device ID) that uniquely identifies the network device 10 used by the network device administrator. The device setting target 902 is a field that stores, as a value, a setting target for which a setting value of a parameter of the network device 10 is to be set. The device parameter 903 is a field that stores, as a value, the name of a parameter that can be set for the device setting target 902. The device setting value 904 is a field that stores, as a value, the setting value of the device parameter 903.

[0068] Fig. 10 is a diagram showing an example of the data configuration of the setting item relation database 315 and the setting item relation tables 315a to 315n stored in the setting item relation database 315. The setting item relation database 315 manages the relationship between the parameters of the network device 10 and the monitoring settings. The setting item relation tables 315a to 315n are created for each network device 10. Fig. 10 does not show setting item relation tables other than the setting item relation tables 315a, 315b, and 315n. The setting item relation tables 315a to 315n each have fields including a device setting target ID 1001, a device setting target 1002, a device parameter 1003, a monitoring service function 1004, a monitoring setting item 1005, and a monitoring setting rule 1006.

[0069] The device setting target ID 1001 is a field that stores, as a value, identification information (device setting target ID) that identifies the device setting target 1002. The device setting target 1002 is a field that stores, as a value, a setting target for which a parameter setting value of the network device 10 is to be set. The device parameter 1003 is a field that stores, as a value, the name of a parameter that can be set for the device setting target 1002. The monitoring service function 1004 is a field that stores, as a value, the name of a monitoring type that uniquely identifies the monitoring type. The monitoring setting item 1005 is a field that stores, as a value, an item that can be set for each monitoring type represented in the monitoring service function 1004. The monitoring setting rule 1006 is a field that stores, as a value, a calculation rule that calculates a monitoring setting value based on the value of the device parameter 1003 (device setting value).

[0070] Fig. 11 is a diagram showing an example of the data configuration of the monitoring setting item aggregation table 316. The data configuration of the monitoring setting item aggregation table 316 is the same as that of the monitoring setting item table 211 described using Fig. 6, so a description of the monitoring setting item aggregation table 316 will be omitted.

[0071] 12A is a diagram showing an example of the data configuration of device configuration information table 317. Device configuration information table 317 is a table for managing connection information and type information of devices connected to the network (network device 10, connected device 11 such as server or client). Device configuration information table 317 has fields of IP address 1201, device ID 1202, device type 1203, node ID 1204, and topology 1205. IP address 1201 is a field that stores, as a value, the IP address of network device 10 or connected device 11. Device ID 1202 is a field that stores, as a value, identification information (device ID) that uniquely identifies network device 10 or connected device 11. Device type 1203 is a field that stores, as a value, the type of network device 10 or connected device 11 (network device, server, client, etc.). Node ID 1204 is a field that stores, as a value, identification information (node ​​ID) that uniquely identifies network device 10 or connection device 11. Topology 1205 is a field that stores, as a value, the topology of the network (the connection relationship between network device 10 and connection device 11) in a table. The value of topology 1205 is 1 if the device with the node ID (network device 10 or connection device 11) is connected to the device with the node ID, and null otherwise. Note that topology 1205 only needs to include information about the topology of the network, and may take a form other than that shown in FIG. 12A.

[0072] 12B is an explanatory diagram showing the topology 1205 shown in FIG.

[0073] 13 is a diagram showing an example of the data configuration of the device configuration relationship table 318. The device configuration relationship table 318 is a table that manages the relationship between information on connected devices 11 (devices whose placement has been changed) that have been deleted or added before and after a setting change, and the monitoring settings. The device configuration relationship table 318 has the following fields: changed device type ID 1301, changed device type 1302, change information 1303, monitoring service function 1304, monitoring setting item 1305, and monitoring setting value 1306.

[0074] The changed device type ID 1301 is a field that stores identification information (changed device type ID) that is associated with a pair of changed device type 1302 and change information 1303 as a value and that uniquely identifies the pair of changed device type 1302 and change information 1303.

[0075] Changed device type 1302 is a field that stores, as a value, the type of device whose placement has been changed. Change information 1303 is a field that stores, as a value, the change content (addition or deletion) of the connection relationship of the device whose placement has been changed. Monitoring service function 1304 is a field that stores, as a value, the name of the monitoring type that uniquely identifies the monitoring type. Monitoring setting item 1305 is a field that stores, as a value, an item that can be set for monitoring service function 1304 (monitoring type). Monitoring setting value 1306 is a field that stores, as a value, the setting value of monitoring setting item 1305 based on the value of change information 1303.

[0076] 14 is a diagram showing an example of the data configuration of the monitoring setting script template 319. The monitoring setting script template 319 is a script template used for monitoring settings, which defines templates for commands and variables for changing monitoring settings. The monitoring setting script template 319 includes the following templates: A monitoring service information template for applying monitoring service functions. A setting information template for creating information for setting monitoring conditions. A network device information template for creating information for accessing network devices. A monitoring device information template for creating information for accessing monitoring devices. A monitoring setting command template for creating commands for executing monitoring setting changes.

[0077] 15 is a diagram showing an example of the data configuration of the monitoring setting script 320. The monitoring setting script 320 is a script that defines commands and variables for changing the monitoring settings of the monitoring device 200. The monitoring setting script 320 is a script that is generated by applying various values ​​to the monitoring setting script template 319 and that can be executed by the monitoring support device 300.

[0078] The device setting value table 112 and the monitoring setting item table 211 together constitute monitoring setting value information that associates device setting targets of the network device 10, device setting values ​​for the device setting targets, monitoring service functions that are names of types of monitoring of the network device 10, and monitoring setting values. The monitoring service information table 312 is monitoring service information that associates monitoring service functions with whether or not there is a contract for monitoring related to the monitoring service functions.

[0079] The device setting value table 112 is device setting value information that associates network device identification information (device ID) that identifies the network device 10, device setting targets, and device setting values, and is also device setting value information after change. The pre-change device setting value table 313 is device setting value information before change. The device setting value difference table 314 is device setting value difference information.

[0080] The device configuration relationship table 318 is device configuration relationship information that associates the type of device whose placement has been changed and which has been added or removed from the network, change information including information on whether the device whose placement has been changed has been added or removed, and monitoring service functions and monitoring setting values. The device ID 1202 in the device setting value difference table 314 is device identification information that identifies each device.

[0081] The device configuration information table 317 is topology information before the setting change.

[0082] The monitoring assistance device 300 uses the tables explained above with reference to FIGS. 4 to 15 to execute the monitoring setting change process, which will be explained below.

[0083] <<Processing Procedure of Monitoring Support Device 300>> Next, the processing procedure of the monitoring support device 300 will be described. A network device administrator inputs settings to be changed for the network device 10 into the setting device 100. The setting device 100 then changes the settings of the network device 10 and stores information about the settings of the network device 10 after the settings change in the device setting value table 112. The setting device 100 is also configured to transmit a notification to the monitoring support device 300, for example, via a messaging platform or a Web API (Application Programming Interface), that the settings of the network device 10 have been changed. The monitoring support device 300 constantly monitors whether settings of the network device 10 have been changed by waiting to receive a notification sent from the setting device 100 that the settings of the network device 10 have been changed.

[0084] When the monitoring support device 300 receives a notification from the setting device 100 that the settings of the network device 10 have been changed, the monitoring support device 300 starts a monitoring setting change process to cause the monitoring device 200 to change the monitoring settings for monitoring the network device 10.

[0085] Next, the monitoring setting change processing executed by the setting change detection unit 301 and the monitoring setting calculation unit 302 of the monitoring assistance device 300 will be described using FIG. 16 while referring to FIGS. 4 to 15.

[0086] 16 is a flowchart showing an example of a monitoring setting change process. When the monitoring support device 300 starts the monitoring setting change process, it acquires the target device information table 111 from the setting device 100, overwrites and saves the target device information table 311 in the secondary storage device 323, and updates the target device information table 311.

[0087] The monitoring support device 300 acquires the setting information of the network device 10 before and after the setting change, calculates the difference (the setting change), and updates the setting information of the network device 10 before the setting change (step S1601). Specifically, the monitoring support device 300 acquires the device setting value table 112, which is the setting information of the network device 10 after the setting change, from the setting device 100 and saves it. In addition, the monitoring support device 300 reads the pre-change device setting value table 313, which is the setting information of the network device 10 before the setting change, from the secondary storage device 323. Then, the monitoring support device 300 calculates the difference (the setting information of the setting change) between the device setting value table 112 and the pre-change device setting value table 313, and saves it in the device setting value difference table 314.

[0088] The acquired device setting value table 112 is then saved by overwriting the pre-change device setting value table 313, thereby updating the pre-change device setting value table 313.

[0089] Next, the monitoring support device 300 acquires a monitoring rule for the setting information for the changed setting of the network device 10, and if the acquired monitoring rule has been changed from the monitoring rule before the setting change, stores the monitoring rule and whether or not there is a contract in the monitoring setting item summary table 316 (step S1602). Specifically, the monitoring support device 300 first acquires and stores the monitoring setting item table 211 including the monitoring rule before the setting change from the monitoring device 200. Then, the monitoring support device 300 performs the following steps 1 to 3 for each record in the device setting value difference table 314 in which the setting information for the changed setting is stored.

[0090] 1. Acquisition of monitoring rules after setting change. The monitoring support device 300 acquires, from the setting item relation database 315 (see FIG. 10), a setting item relation table 315i associated with the device ID 901 in the device setting value difference table 314. Then, the monitoring support device 300 acquires, from the setting item relation table 315i, the monitoring service function 1004, the monitoring setting item 1005, and the monitoring setting rule 1006 associated with the device setting target 902 and the device parameter 903 in the device setting value difference table 314.

[0091] The monitoring assistance device 300 then applies the device parameters 903 and device setting values ​​904 in the device setting value difference table 314 to the monitoring setting rules 1006 in the acquired setting item relationship table 315i, and sets the obtained values ​​as monitoring setting values. The three items acquired above, the monitoring service function 1004, the monitoring setting item 1005, and the monitoring setting value, are set as the monitoring rule after the setting change.

[0092] 2. Acquisition of monitoring setting values ​​before the setting change for monitoring rules after the setting change: The monitoring assistance device 300 acquires, as monitoring setting values ​​before the setting change, monitoring setting values ​​associated with the monitoring service functions and monitoring setting items included in the monitoring rules after the setting change from the monitoring setting item table 211 (see FIG. 6 ) that includes the monitoring rules before the setting change.

[0093] 3. If the monitoring setting values ​​differ before and after the setting change, obtain whether or not there is a contract, and save the whether or not there is a contract in the monitoring setting item summary table 316 (see FIG. 11) along with the monitoring rule after the setting change. The monitoring assistance device 300 compares the monitoring setting values ​​included in the monitoring rule after the setting change with the monitoring setting values ​​before the setting change, and if they differ, the monitoring settings will change, so the changed monitoring settings are saved. That is, the monitoring assistance device 300 obtains the contract whether or not there is a contract 703 associated with the monitoring service function included in the monitoring rule after the setting change from the monitoring service information table 312 (see FIG. 7), and associates the obtained whether or not there is a contract with the monitoring rule after the setting change and saves it in the monitoring setting item summary table 316 as monitoring settings.

[0094] In addition, if the monitoring setting values ​​included in the monitoring rule after the setting change are the same as the monitoring setting values ​​before the setting change, the monitoring settings do not change before and after the setting change, so the monitoring support device 300 does not save the monitoring rule and whether or not there is a contract in the monitoring setting item summary table 316.

[0095] By the monitoring support device 300 performing the above steps 1 to 3 for each record in the device setting value difference table 314, the monitoring support device 300 stores the setting information of the monitoring service that changes due to a setting change in the network device 10 in the monitoring setting item summary table 316.

[0096] An example of the above processes 1 to 3 will be described below. For example, in the record of the device setting value difference table 314 shown in Fig. 9, for the device ID 901 "CC9K-1", the device setting target 902 is "GigabitEthernet1 / 0 / 1", the device parameter 903 is "I / F enable", and the device setting value 904 is "enable".

[0097] 1. Obtaining monitoring rules after setting change. The monitoring support device 300 obtains, from the setting item relation database 315 (see FIG. 10), a setting item relation table 315a associated with the device ID 901 "CC9K-1" in the device setting value difference table 314. Then, the monitoring support device 300 obtains from the setting item relation table 315a the monitoring service function 1004 "Port status monitoring," the monitoring setting item 1005 "Enable," and the monitoring setting rule 1006 "If device parameter = enable then monitoring setting value = enable," which are associated with the device setting target 902 "GigabitEthernet1 / 0 / 1" and the device parameter 903 "I / F enable."

[0098] The monitoring assistance device 300 then applies the device parameter 903 "I / F enable" and the device setting value 904 "enable" in the device setting value difference table 314 to the monitoring setting rule 1006 "If device parameter = enable then monitoring setting value = enable" in the acquired setting item relationship table 315a, and sets the obtained value "enable" as the monitoring setting value "enable."The three items acquired from the setting item relationship table 315a in this way - the monitoring service function 1004 "port status monitor," the monitoring setting item 1005 "enable," and the monitoring setting value "enable" - are set as the monitoring rule after the setting change.

[0099] 2. Obtaining the monitoring setting value before the setting change for the monitoring rule after the setting change. The monitoring support device 300 obtains the monitoring setting value "enabled" associated with "port status monitoring" and the monitoring setting item "enabled" included in the monitoring rule after the setting change from the monitoring setting item table 211 (see FIG. 6) that includes the monitoring rule before the setting change, as the monitoring setting value "enabled" before the setting change.

[0100] 3. If the monitoring setting values ​​differ before and after the setting change, the presence or absence of a contract is obtained and saved in the monitoring setting item summary table 316 (see FIG. 11 ) along with the monitoring rule after the setting change. The monitoring support device 300 compares the monitoring setting value "enabled" included in the monitoring rule after the setting change with the monitoring setting value "enabled" before the setting change. The monitoring setting value "enabled" included in the monitoring rule after the setting change and the monitoring setting value "enabled" before the setting change are both "enabled." Therefore, because the monitoring setting values ​​have not changed before and after the setting change, and the monitoring settings have not changed, the monitoring support device 300 does not save the monitoring rule and the presence or absence of a contract in the monitoring setting item summary table 316.

[0101] If the monitoring setting value after the setting change is "enabled" and the monitoring setting value before the setting change is "disabled," and the monitoring setting value changes (is different) before and after the setting change, the monitoring setting will change before and after the setting change, so the changed monitoring setting will be saved. That is, the monitoring support device 300 obtains "Yes" in contract existence / non-existence 703, which is associated with the monitoring service function "port status monitoring" included in the monitoring rule after the setting change, from the monitoring service information table 312 (see FIG. 7), and associates the obtained contract existence / non-existence "Yes" with the monitoring rule after the setting change and saves it as a monitoring setting in the monitoring setting item aggregation table 316 (see FIG. 11).

[0102] Next, the monitoring support device 300 acquires information about the topology after the setting change, compares the topologies before and after the setting change, and acquires information about devices (network devices 10, connected devices 11) that have been relocated and added to or deleted from the network NW1 between before and after the setting change (step S1603). Specifically, the monitoring support device 300 first uses a network discovery tool to detect the topology of the devices connected to the network NW1 (referred to as the topology after the setting change) and collects information about the IP addresses and OS (Operating System) names of each device. The monitoring support device 300 then associates each node ID (see FIG. 12A) in the information about the topology after the setting change with the IP addresses and OS name information, and saves this information together with the information about the topology after the setting change as device configuration topology information after the setting change.

[0103] Then, the monitoring assistance device 300 acquires from the target device information table 311 information associating the IP address (from the access information 404) with the device ID of the network device 10 connected to the network NW1 after the setting change.

[0104] Furthermore, based on the IP address included in the post-setting change equipment configuration topology information, the monitoring support device 300 stores the device ID, IP address, and type "network device" of the acquired network device 10 in association with each other in the post-setting change equipment configuration topology information.

[0105] The monitoring support device 300 calculates the type of a device for an IP address that is not associated with the type "network device" in the post-settings change device configuration topology information from the OS name information associated with the IP address as follows, and stores the calculated type in the post-settings change device configuration topology information in association with the IP address. If the OS is an OS typically used on servers, such as "Windows Server (registered trademark)" or "Linux (registered trademark), the monitoring support device 300 sets the type to "server." If the OS is an OS typically used on clients, such as MacOS or Windows 10 or 11 (registered trademark), the monitoring support device 300 sets the type to "client." In the above, OS name information is stored in association with the IP address, and the type is calculated from the OS. However, other information that can calculate the type may be used instead of the OS name.

[0106] Then, the monitoring assistance device 300 updates the device configuration information table 317 based on the device configuration topology information after the setting change.

[0107] The monitoring support device 300 then compares the topology information between the post-setting change device configuration topology information, which includes information about the topology after the setting change, and the device configuration information table 317, which includes information about the topology before the setting change, and calculates and stores information about the network device 10 and the connected device 11 as follows. That is, the monitoring support device 300 calculates the IP address, device ID, type "network device," and change information (added, deleted, no change) of the network device 10, and stores these in association with each other. The monitoring support device 300 also calculates the IP address, device ID, type (server, etc.), and change information (added, deleted, no change) of the connected device 11, as well as the IP address of the network device 10 connected upstream, and stores these in association with each other. This information about the network device 10 and the connected device 11 is location change device information, which associates the device ID (location change device identification information that identifies the location change device), the type of the location change device, and change information.

[0108] Next, the monitoring support device 300 calculates information on the monitoring settings to be changed for the device whose placement has been changed (monitoring rule and whether or not there is a contract) as shown in A and B below, and saves the information in the monitoring setting item summary table 316 (step S1604). Here, among the network devices 10 to which the connection device whose placement has been changed (the connection device 11 that has been added or deleted) is not connected, there are network devices 10 whose settings have not been changed before and after the setting change, and network devices 10 whose settings have been changed. The monitoring support device 300 does not calculate monitoring settings for these network devices. This is because there is no need to change the monitoring settings for network devices 10 whose settings have not been changed. Furthermore, the changes in the monitoring settings (monitoring rule, whether or not there is a contract) for the network device 10 whose settings have been changed have already been saved in the monitoring setting item summary table 316 in the processing of step S1602 described above.

[0109] A. Setting monitoring to stop for deleted network device 10a. Since the deleted network device 10a does not need to be monitored after the setting change, monitoring is set to "stop." Specifically, the monitoring support device 300 acquires the monitoring rules of the deleted network device 10a and whether or not a contract exists from the monitoring setting item table 211. Then, the monitoring support device 300 associates the monitoring rules of the deleted network device 10a whose monitoring setting values ​​have been changed to "disabled" (monitoring service function, monitoring setting item, monitoring setting value "disabled") with whether or not a contract exists and the device ID, and saves these in the monitoring setting item summary table 316.

[0110] B. Changing the monitoring settings for a network device (location-changed network device) 10b connected downstream of an added or deleted connected device 11 (location-changed connected device). Here, whether the location-changed network device is a network device 10 that was added after the setting change or not, the added connected device 11 is connected downstream of the location-changed network device. As described above, the monitoring support device 300 stores information associating the IP addresses, device IDs, types (e.g., servers), and change information (addition or deletion) of the connected devices that were added or deleted before or after the setting change with the IP addresses of the network devices 10 connected upstream. Based on this information and the post-setting change device configuration topology information, the monitoring support device 300 can acquire, for each network device 10b, information on the IP addresses, device IDs, types (e.g., servers), and change information (addition or deletion) of all connected devices 11 connected downstream of the network device 10b.

[0111] The monitoring support device 300 performs the processes B1 to B4 below for each network device 10b to which the placement-changed connection device is connected downstream.

[0112] B1: Acquisition of monitoring rules for each device whose arrangement has been changed. Specifically, the monitoring support device 300 acquires monitoring rules (monitoring service functions 1304, monitoring setting items 1305, and monitoring setting values ​​1306) associated with the type and change information of the device whose arrangement has been changed from the device configuration relationship table 318 (see FIG. 13).

[0113] B2: Acquisition of monitoring rules for each connected device 11 whose placement has not changed (addition, deletion) before and after the setting change (connected devices 11 other than connected devices whose placement has changed). Specifically, the monitoring support device 300 acquires, from the device configuration relationship table 318, the type of connected device 11 whose placement has not changed and the monitoring rules (monitoring service function 1304, monitoring setting item 1305, monitoring setting value 1306) associated with the change information “addition” (here, the change information for connected device 11 whose placement has not changed is set to “addition”).

[0114] B3: Calculate a consistency monitoring setting value that ensures consistency of monitoring setting values ​​among all connected devices 11 connected to network device 10b to which the location-changed connected device is connected, and acquire whether or not a contract exists. If at least one monitoring setting value associated with the same pair of monitoring service function and monitoring setting item among the monitoring rules of all devices connected to network device 10b (connected devices 11 other than the location-changed connected device of B1 and the location-changed connected device of B2) is "enabled," the monitoring support device 300 sets the consistency monitoring setting value to "enabled." Also, the consistency monitoring rule is set to the pair of monitoring service function and monitoring setting item and the monitoring setting value "enabled."

[0115] On the other hand, if the monitoring setting values ​​associated with the same pair of monitoring service function and monitoring setting item among the monitoring rules of all devices connected to network device 10b (connected devices 11 other than the B1 relocated connected device and the B2 relocated connected device) are all "disabled," the monitoring support device 300 sets the consistency monitoring setting value to "disabled." Also, the consistency monitoring rule is set to the pair of monitoring service function and monitoring setting item and the monitoring setting value "disabled."

[0116] As described above, the monitoring support device 300 calculates consistency monitoring rules for all pairs of monitoring service functions and monitoring setting items. Furthermore, the monitoring support device 300 acquires the contract existence / non-existence 703 associated with the monitoring service functions included in the consistency monitoring rules from the monitoring service information table 312, and stores the acquired contract existence / non-existence 703 in association with the device ID and consistency monitoring rule of the network device 10b.

[0117] B4: Saving the consistency monitoring rule in the monitoring setting item aggregation table 316. The monitoring support device 300 determines whether the pair of the device ID and consistency monitoring rule of the network device 10b is saved in at least one of the monitoring setting item aggregation table 316 and the monitoring setting item table 211. If it is determined that the pair is not saved, the monitoring support device 300 saves the device ID, consistency monitoring rule, and contract status of the relocated network device 10b2 as monitoring settings in the monitoring setting item aggregation table 316.

[0118] By performing the above B1 to B4 for each network device 10b to which a location-changed connection device is connected, the monitoring support device 300 can change the monitoring settings even if the setting change of the network device 10 related to the location-changed connection device is not set by the setting device 100. This allows the monitoring support device 300 to change the monitoring settings more appropriately.

[0119] Next, the monitoring support device 300 uses the monitoring setting item summary table 316 (see FIG. 11) to update the monitoring setting item table 211 (see FIG. 6) stored in the monitoring device 200 (step S1605). Specifically, the monitoring support device 300 acquires the monitoring setting value 605 of the monitoring setting item table 211 stored as described above, which is associated with the device ID 1101, the monitoring service function 1102, and the monitoring setting item 1104 in the monitoring setting item summary table 316, and compares it with the monitoring setting value 1105 of the monitoring setting item summary table 316. Then, if the monitoring setting value 605 of the monitoring setting item table 211 differs from the monitoring setting value 1105 of the monitoring setting item summary table 316, the monitoring support device 300 replaces the monitoring setting value 605 of the stored monitoring setting item table 211 with the monitoring setting value 1105 of the monitoring setting item summary table 316. Here, if the monitoring setting value 1105 in the monitoring setting item summary table 316 is "disabled," the records of device ID 601 to monitoring setting value 605 in the monitoring setting item table 211 that are associated with device ID 1101, monitoring service function 1102, and monitoring setting item 1104 in the monitoring setting item summary table 316 are deleted.

[0120] Furthermore, if a record corresponding to the device ID 1101, monitoring service function 1102, and monitoring setting item 1104 in the monitoring setting item aggregation table 316 does not exist in the saved monitoring setting item table 211, the monitoring support device 300 saves the device ID 1101 to the monitoring setting value 1105 in the monitoring setting item aggregation table 316 in the monitoring setting item table 211.

[0121] Next, monitoring assistance device 300 outputs the data of monitoring setting item summary table 316 to network I / F 324, and causes network I / F 324 to transmit the data of monitoring setting item summary table 316 to monitoring terminal 250 (step S1606). This allows the operator of network operation system 1 to understand the monitoring settings to be changed by operating monitoring terminal 250. Note that monitoring assistance device 300 may output other information, for example, information associating the IP addresses, device IDs, types, and change information (addition, deletion) of network devices 10 and connected devices 11 whose arrangements have been changed (added, deleted) before and after the setting change, to network I / F 324, and causes network I / F 324 to transmit the information to monitoring terminal 250.

[0122] Next, the monitoring support device 300 generates a script for automatically executing changes to the monitoring settings for monitors for which the contract existence field is "existent" (step S1607). Specifically, for each record in the monitoring setting item aggregation table 316 for which the contract existence field 1103 is "existent," the monitoring support device 300 applies various values ​​to the monitoring setting script template 319 (see FIG. 15) as follows to create a monitoring setting script 320.

[0123] The monitoring support device 300 applies the monitoring service function 1102 in the monitoring setting item aggregation table 316 to a template of monitoring service information. The monitoring support device 300 also applies monitoring condition information, such as the monitoring setting value 1105 in the monitoring setting item aggregation table 316 and the monitoring condition value 708 in the monitoring service information table 312 associated with the monitoring service function 1102 in the monitoring setting item aggregation table 316, to the template of setting information.

[0124] In addition, the monitoring support device 300 applies information for accessing the network device 10, such as the device ID 1101 in the monitoring setting item aggregation table 316 and the access information 404, login ID 405, password 406, etc. in the target device information table 311 that is associated with the device ID 1101 in the monitoring setting item aggregation table 316, to a network device information template.

[0125] The monitoring support device 300 also applies information for accessing the monitoring device 200, such as the access information 704, login ID 705, and password 706 in the monitoring service information table 312, which is associated with the monitoring service function 1102 in the monitoring setting item aggregation table 316, to a template for monitoring device information. The monitoring support device 300 also applies the access information 704 in the monitoring service information table 312, which is associated with the monitoring service function 1102 in the monitoring setting item aggregation table 316, to a template for a monitoring setting command.

[0126] Next, the monitoring assistance device 300 executes the script generated in step S1607, changes the monitoring settings of the monitoring device 200, and ends the process (step S1608).

[0127] The process of step S1601 is a setting change detection process executed by the setting change detection unit. The processes of steps S1602 to S1608 are a monitoring setting calculation process executed by the monitoring setting calculation unit. The processes of steps S1603 to S1604 are a topology change monitoring setting calculation process. The process of step S1606 is a monitoring terminal transmission process and a monitoring service function transmission process. The process of step S1607 is a monitoring setting script process.

[0128] As described above, the monitoring support device 300 acquires changed device setting values ​​of the network device 10 and generates monitoring settings for the monitoring device 200 to monitor the network device 10. In this way, the monitoring support device 300 makes it easy to set the monitoring settings of the monitoring device 200 for the network device 10. This reduces the number of steps required for setting the monitoring settings when changing the settings of the network device 10, and also reduces manual work errors. Furthermore, the monitoring support device 300 reduces the energy required to generate the monitoring settings of the monitoring device 200 and the amount of carbon dioxide emissions generated, thereby suppressing global warming.

[0129] The monitoring support device 300 transmits the monitoring service functions and monitoring setting values ​​to the monitoring terminal 250. Upon receiving the monitoring service functions and monitoring setting values, the monitoring terminal 250 can display the monitoring service functions and monitoring setting values. This allows the operator using the monitoring terminal 250 to easily understand the monitoring service functions and monitoring setting values.

[0130] The monitoring assistance device 300 generates a monitoring setting script, thereby making it easier to set the monitoring settings of the monitoring device 200 of the network device 10.

[0131] The monitoring support device 300 generates monitoring settings that include monitoring service functions associated with whether or not a contract exists and their monitoring setting values. This allows the monitoring support device 300 to generate more appropriate monitoring settings. As a result, the monitoring support device 300 can more appropriately monitor the network device 10.

[0132] The monitoring assistance device 300 transmits the monitoring service functions and monitoring setting values ​​that are not contracted or that do not have a contract to the monitoring terminal 250. The monitoring terminal 250 receives the monitoring service functions and monitoring setting values ​​that do not have a contract and can display the monitoring service functions and monitoring setting values ​​that do not have a contract. This allows the operator using the monitoring terminal 250 to easily grasp the monitoring service functions and monitoring setting values ​​that are not being executed and that can be changed to enable execution.

[0133] The monitoring support device 300 acquires the changed device setting values ​​of the network device and the device setting targets for the changed device setting values ​​based on a device setting value difference table (device setting value difference information) 314 that is the difference between the device setting value table (device setting value information at the time of change) 112 and the device setting value table before change (device setting value information before change) 313. This allows the monitoring support device 300 to more easily acquire the changed device setting values ​​of the network device and the device setting targets for the changed device setting values. Consequently, the monitoring support device 300 makes it easier to set the monitoring settings of the monitoring device 200 of the network device 10.

[0134] The monitoring support device 300 acquires the topology of the network and calculates the monitoring settings of the network device 10 by all of the connection devices 11 (devices) connected to the network device 10 before and after the setting change of the network device 10. This allows the monitoring support device 300 to generate more appropriate monitoring settings. As a result, the monitoring support device 300 makes it possible to more appropriately monitor the network device 10.

[0135] It should be noted that the present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added to, deleted from, or replaced with other configurations.

[0136] Furthermore, the aforementioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole in hardware, for example by designing them as integrated circuits, or may be realized in software by having a processor interpret and execute a program that realizes each function.

[0137] Information such as programs, tables, files, etc. that realize each function can be stored in storage devices such as memory, hard disks, SSDs (Solid State Drives), or recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs).

[0138] In addition, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily represent all the control lines and information lines that are necessary for implementation. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0139] 1: Network operation system 10: Network equipment 100: Setting device 101:Setting information management department 101a: Configuration information management program 102:Device setting section 102a: Device setting program 103: Storage section 110: Configuration work information DB 111: Target device information table 112: Device setting value table 121, 221, 321: Processor 122, 222, 322: Main memory 123, 223, 323: Secondary storage device 124, 224, 324: Network I / F 125, 225, 325: Bus 200: Monitoring device 201: Equipment monitoring department 201a: Equipment Monitoring Program 202: Monitoring settings section 202a: Monitoring setting program 210: Monitoring setting information DB 211: Monitoring setting item table 250: Monitoring terminal 300: Monitoring support equipment 301: Setting change detection part 301a: Configuration change detection program 302: Monitoring setting calculation unit 302a: Monitoring setting calculation program 310: Relationship management information DB 311: Target device information table 312: Monitoring service information table 313: Device setting value table before change 314: Device setting value difference table 315: Setting item relation database 316: Monitoring setting item summary table 317: Equipment configuration information table 318: Equipment configuration relationship table 319: Monitoring configuration script template 320: Monitoring configuration script

Claims

1. A monitoring support device for generating monitoring settings for monitoring a network device, the monitoring device monitoring a connection state of the network device that transmits data and is connected to a network, a processor; The processor: A setting change detection process for acquiring changed device setting values ​​of the network device and device setting targets for the changed device setting values; Obtaining monitoring setting value information that associates a device setting target of the network device, a device setting value for the device setting target, a monitoring service function that is the name of a type of monitoring of the network device, and a monitoring setting value; acquires, from the monitoring setting value information, the monitoring service function and the monitoring setting value associated with the changed device setting value of the network device and the device setting target for the changed device setting value, which are acquired in the setting change detection process; a monitoring setting calculation process for generating the monitoring setting including the acquired monitoring service function and the acquired monitoring setting value; Monitoring support equipment.

2. The monitoring support device according to claim 1, the monitoring support device is connected to a monitoring terminal via a network, the processor executes a monitoring terminal transmission process to transmit the monitoring service functions and monitoring setting values ​​generated in the monitoring setting calculation process to the monitoring terminal; Monitoring support equipment.

3. The monitoring support device according to claim 1, Further, the device includes a storage device, the storage device stores a monitoring setting script template associated with the monitoring service function; the processor acquires a monitoring setting script template associated with the monitoring service function acquired in the monitoring setting calculation process; Execute a monitoring setting script process to generate a monitoring setting script for setting monitoring in the monitoring device by applying the monitoring service functions and monitoring setting values ​​generated in the monitoring setting calculation process to the acquired monitoring setting script template. Monitoring support equipment.

4. The monitoring support device according to claim 1, Further, the device includes a storage device, the storage device stores monitoring service information that associates the monitoring service function with whether or not there is a contract for monitoring the monitoring service function; The monitoring setting calculation process includes: generating a monitoring setting including the monitoring service function and the monitoring setting value that are associated with the changed device setting value of the network device and the device setting target for the changed device setting value, which are acquired in the setting change detection process, and that are associated with "contract existence" in the monitoring service information; Monitoring support equipment.

5. The monitoring support device according to claim 4, the monitoring support device is connected to a monitoring terminal via a network, The processor: execute a monitoring service function transmission process to cause the monitoring service function to transmit to the monitoring terminal the monitoring service function and the monitoring setting value that are associated with the changed device setting value of the network device and the device setting target for the changed device setting value, which are acquired in the setting change detection process, and that are associated with "no contract" in the monitoring service information; Monitoring support equipment.

6. The monitoring support device according to claim 1, the network device is configured by a configuration device that generates device setting value information that associates network device identification information that identifies the network device, the device setting target, and the device setting value, based on the device setting value information; In the setting change detection process, the processor acquiring device setting value information generated before the setting change of the network device as pre-change device setting value information; acquiring device setting value information generated when the settings of the network device are changed as changed device setting value information; calculating a difference between the device setting value information after the change and the device setting value information before the change as device setting value difference information; Acquire the changed device setting value of the network device and the device setting target for the changed device setting value based on the device setting value difference information. Monitoring support equipment.

7. The monitoring support device according to claim 1, Further, the device includes a storage device, The storage device storing device configuration relationship information that associates the types of devices whose placement has been changed that have been added to or deleted from the network before or after a setting change of the network device, change information including information on whether the devices whose placement has been changed have been added or deleted, with the monitoring service functions and monitoring setting values; The processor: Acquire topology information that stores device identification information that identifies each device connected to the network, the type of each device, and a topology in association with each other, for each of the cases before and after the setting change of the network device; calculating a difference between the topology information before the setting change and the topology information after the setting change; acquiring device information for which device identification information for identifying the device for which device placement has been changed, the type of the device for which device placement has been changed, and the change information; For each of the location-changed network devices to which the location-changed connection device is connected downstream of the network, For all the location-changed connection devices connected downstream of the location-changed network device, Acquire the type and change information of the connection device whose placement has been changed from the device information about the device whose placement has been changed; The monitoring service function and the monitoring setting value associated with the type of the acquired changed connection device and change information are acquired from the device configuration relationship information, Obtaining a consistency monitoring setting value that is a consistency of the monitoring setting values ​​of all of the changed connection devices connected downstream of the changed network device; and executing a topology change monitoring setting calculation process to generate the monitoring setting including the monitoring service function and the consistency monitoring setting value of the relocated network device. Monitoring support equipment.

8. A network operation system that monitors settings and connection status of network devices, a setting device for setting the network of the network device; a monitoring device that monitors the connection status of the network devices; a monitoring support device that generates monitoring settings for the monitoring device to monitor the network device, The monitoring support device a processor; The processor: A setting change detection process for acquiring changed device setting values ​​of the network device and device setting targets for the changed device setting values; Obtaining monitoring setting value information that associates a device setting target of the network device, a device setting value for the device setting target, a monitoring service function that is the name of a type of monitoring of the network device, and a monitoring setting value; acquires, from the monitoring setting value information, the monitoring service function and the monitoring setting value associated with the changed device setting value of the network device and the device setting target for the changed device setting value, which are acquired in the setting change detection process; a monitoring setting calculation process for generating the monitoring setting including the acquired monitoring service function and the acquired monitoring setting value; Network operation system.

9. 1. A monitoring support method in a monitoring support device in which a monitoring device that monitors a connection state of a network device that transmits data and is connected to a network generates monitoring settings for monitoring the network device, A setting change detection process for acquiring changed device setting values ​​of the network device and device setting targets for the changed device setting values; Obtaining monitoring setting value information that associates a device setting target of the network device, a device setting value for the device setting target, a monitoring service function that is the name of a type of monitoring of the network device, and a monitoring setting value; acquires, from the monitoring setting value information, the monitoring service function and the monitoring setting value associated with the changed device setting value of the network device and the device setting target for the changed device setting value, which are acquired in the setting change detection process; a monitoring setting calculation process for generating the monitoring setting including the acquired monitoring service function and the acquired monitoring setting value; Monitoring support method.

Images