JP2014007666A - Correspondence specification device, correspondence specification method and correspondence specification program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To take an appropriate action at the time of fault occurrence without imposing a burden on a manager of a system.SOLUTION: A correspondence specification device 10 includes: a connection information storage section 12 which stores a connection state between apparatuses at a normal time; a contract storage section 13 which stores a monitoring object apparatus for each monitoring contract; and a correspondence method storage section 14 which stores a plurality of sets of specification information for specifying monitoring contracts and correspondence methods. The correspondence specification device 10 confirms a connection state between adjacent apparatuses in the case that a fault is detected, and generates difference information indicating a difference between the connection state stored in the connection information storage section 12 and the confirmed connection state. The correspondence specification device 10 determines, for each set stored in the correspondence method storage section 14, whether or not there is the difference indicated by the difference information in the connection state of the monitoring object apparatus stored in the contract storage section 13 with respect to the monitoring contract specified by the specification information of the set, and specifies a correspondence method of the set determined that there is the difference as a correspondence method to the detected fault.

Description

  The present invention relates to a technique for specifying a response method when a failure is detected in a network system in which a plurality of devices are connected.

There is a monitoring system that monitors the occurrence of a failure in a network system in which a plurality of devices such as servers, routers, and switches are connected. In this monitoring system, a PING (Packet Internet Grouper) command is executed for each device, and SNMP (Simple Network Management Protocol) information is collected to confirm that each device is operating. . Then, it is assumed that a failure has occurred in the device that could not be confirmed to be operating, and the system administrator or the like is notified that the failure has occurred in the device.
However, in a large-scale network system in which many devices are connected, a certain device may not be operating, and it may not be possible to confirm that another device is operating. In this case, it is assumed that a failure has occurred even in a device that has not actually failed. As a result, a single device is not in operation, and a number of devices are notified that a failure has occurred.

  In Patent Document 1, for each combination of the operating states of each device, a pattern that defines a device in which a failure has occurred is prepared. There is a description about identifying the device that is generating.

JP 2010-232970 A

In Patent Document 1, it is necessary to prepare in advance a pattern that defines a device in which a failure has occurred for each combination of operating states of each device. In the case of a large-scale network system, it is difficult to identify and set a faulty device for all combinations of devices connected in a mesh. In addition, devices may be added or replaced in the network system, and the configuration of the network system is changed as needed. It is difficult to update the pattern each time the configuration of the network system is changed.
An object of the present invention is to take an appropriate response when a failure occurs without imposing a burden on a system administrator.

The correspondence specifying device according to the present invention is:
A response identification device that identifies a response method when a failure is detected in a network system in which multiple devices are connected.
A connection information storage unit for storing connection information indicating a connection state between devices in a normal state in which a failure of the network system has not occurred;
A confirmation unit for confirming the connection state between adjacent devices when a failure is detected;
A difference information generation unit that generates difference information indicating a difference between a connection state indicated by the connection information stored in the connection information storage unit and a connection state confirmed by the confirmation unit;
For each monitoring contract, a contract storage unit that stores the device to be monitored,
A corresponding method storage unit for storing a plurality of sets of specific information for specifying a monitoring contract and a corresponding method;
For each pair stored by the handling method storage unit, the difference information generation unit generates a difference generated by the monitoring target device stored in the contract storage unit with respect to the monitoring contract specified by the pair specific information. A determination unit for determining whether there is a difference indicated by the information;
And a identifying unit that identifies a pair of handling methods determined by the judging unit as having a difference as a handling method for the detected failure.

According to the correspondence specifying apparatus according to the present invention, the connection information storage unit stored in the normal state, the connection state at the time of failure confirmed by the confirmation unit, and the monitoring contract stored in the contract storage unit are appropriately selected. Can be identified.
For example, when the network configuration changes or the monitoring contract changes, it is possible to continue to specify an appropriate response method simply by storing the changed contents in the connection information storage unit or contract storage unit. is there.

1 is a configuration diagram of a correspondence identifying device 10 according to Embodiment 1. FIG. 1 is a configuration diagram of a network system 20 according to a first embodiment. The figure which shows the apparatus information which the apparatus information storage part 11 which concerns on Embodiment 1 memorize | stores. The figure which shows the connection information which the connection information storage part 12 which concerns on Embodiment 1 memorize | stores. The figure which shows the contract information which the contract memory | storage part 13 which concerns on Embodiment 1 memorize | stores. The figure which shows the group which the corresponding | compatible method memory | storage part 14 which concerns on Embodiment 1 memorize | stores. 5 is a flowchart showing the operation of the correspondence specifying apparatus 10 according to the first embodiment. The figure which shows the example of the adjacency matrix at the time of normal. The figure which shows the example of the adjacency matrix at the time of failure occurrence. The figure which shows the example of difference information. The figure which shows the example of a filter. The figure which shows the example of SQL which identifies the apparatus used as the monitoring object. The figure which shows the example of the information extracted from the difference information with the filter. The figure which shows the group which the corresponding | compatible method memory | storage part 14 concerning Embodiment 2 memorize | stores. The figure which shows the example of a filter. The figure which shows the example of SQL which specifies the apparatus used as object. The figure which shows an example of the hardware constitutions of the correspondence specific apparatus 10.

Embodiment 1 FIG.
In the first embodiment, a response specifying apparatus 10 that specifies a response method when a failure is detected in a network system 20 to which a plurality of devices are connected will be described.

FIG. 1 is a configuration diagram of a correspondence identifying apparatus 10 according to the first embodiment.
The correspondence specifying device 10 includes a device information storage unit 11, a connection information storage unit 12, a contract storage unit 13, a response method storage unit 14, a confirmation unit 15, a difference information generation unit 16, a determination unit 17, and a specification unit 18.
The device information storage unit 11 is a storage device that stores information about devices connected to the network system 20. The connection information storage unit 12 is a storage device that stores connection information indicating a connection relationship (in a normal state) between devices connected to the network system 20. The contract storage unit 13 is a storage device that stores contract information indicating devices to be monitored for each monitoring contract. The handling method storage unit 14 is a storage device that stores a plurality of sets of a contract ID (specific information) that is identification information of a monitoring contract and a handling method.
The confirmation unit 15 confirms a connection state between devices for a device to be monitored and an adjacent device among devices connected to the network system 20. The difference information generation unit 16 generates difference information indicating a difference between the connection state indicated by the connection information stored in the connection information storage unit 12 and the connection state confirmed by the confirmation unit 15. For each group stored in the handling method storage unit 14, the determination unit 17 sets the difference information generation unit in the connection state of the monitoring target device stored in the contract storage unit 13 with respect to the monitoring contract specified by the specific information of the group. It is determined whether there is a difference indicated by the difference information generated by 16. The identifying unit 18 identifies the group handling method determined by the determining unit 17 as having a difference as the handling method for the detected failure.

FIG. 2 is a configuration diagram of the network system 20 according to the first embodiment.
Network system 20 includes probe 21, IaaS device 22, monitoring device 23, customer device A24, customer device A25, customer device B26, customer device B27, customer device B28, customer device N29, customer device N30, customer device N31, customer device. N32 is provided.

The probe 21, the IaaS device 22, and the monitoring device 23 are in-house devices of the system operating company. The probe 21 is a server that collects information from each device connected to the network system 20 by PING or SNMP. The IaaS device 22 is a server that provides services to a plurality of customers in a virtual environment. The monitoring device 23 is a server that generates an alarm based on information collected by the probe 21 or information collected directly from the customer device A24 or the like. For example, the monitoring device 23 generates an alarm when the operation of the device to be monitored cannot be confirmed, when the usage rate of the CPU exceeds a threshold, or when the temperature of the CPU exceeds the threshold.
Customer device A24 and customer device A25 are devices of customer A, for example, customer device A24 is a router, and customer device A25 is a switch.
Customer device B26, customer device B27, and customer device B28 are devices of customer B, for example, customer device B26 and customer device B27 are routers, and customer device B28 is a switch.
The customer device N29, the customer device N30, the customer device N31, and the customer device N32 are customer devices other than the customers A and B.

Here, it is assumed that the company's device is its own monitoring range, the customer A's device and the IaaS device 22 are the customer A's monitoring range, and the customer B's device and the IaaS device 22 are the customer B's monitoring range. .
In this case, the failure information acquisition range includes devices included in the monitoring range and devices adjacent to the devices included in the monitoring range. That is, here, the failure information acquisition range includes devices included in the monitoring range (probe 21, IaaS device 22, monitoring device 23, customer device A24, customer device A25, customer device B26, customer device B27, customer device B28. ), Customer equipment N29 adjacent to customer equipment A25, and customer equipment N31 adjacent to customer equipment B28.

FIG. 3 is a diagram illustrating device information stored in the device information storage unit 11 according to the first embodiment.
The device information includes a device ID that is device identification information, a device name that is the name of the device, a device type that indicates the type of device, a level that indicates the monitoring level of the device, and the like.

FIG. 4 is a diagram illustrating connection information stored in the connection information storage unit 12 according to the first embodiment.
The connection information includes a connection ID that is identification information for connection between devices, End1 in which the device ID of one device is stored, End2 in which the device ID of the other device is stored, and the like.

FIG. 5 is a diagram showing contract information stored in the contract storage unit 13 according to the first embodiment.
The contract information includes the contract ID that is identification information of the monitoring contract, the customer name that is the name of the contract partner of the monitoring contract, the contract type that indicates the type of the contract, the monitoring target that stores the device ID of the monitored device, the contract partner How to contact is included.

FIG. 6 is a diagram illustrating pairs stored in the handling method storage unit 14 according to the first embodiment.
Each group includes a group ID, a contract ID, and a contact address, which are group identification information. Here, as a response method when a failure occurs, the customer is contacted.

FIG. 7 is a flowchart showing the operation of the correspondence identifying apparatus 10 according to the first embodiment.
The correspondence identifying device 10 starts operation when the monitoring device 23 generates an alarm.
(S1: Confirmation step)
The confirmation unit 15 confirms the connection state between the devices about the device to be monitored and the adjacent device based on the information collected by the probe 21 and the information collected by the monitoring device 23. The confirmation unit 15 may confirm the connection state using other information or other methods.

(S2: Difference information generation step)
The difference information generation unit 16 generates difference information indicating a difference between the connection state indicated by the connection information stored in the connection information storage unit 12 and the connection state confirmed by the confirmation unit 15.
Specifically, first, the difference information generation unit 16 indicates that connection information is indicated by an adjacency matrix (bit information) representing a connection state between devices, where 1 indicates that the connection is present and 0 indicates that there is no connection. The connection state and the connection state confirmed by the confirmation unit 15 are represented. Then, the exclusive OR of the adjacency matrix indicating the connection state indicated by the connection information (adjacency matrix at normal time) and the adjacency matrix indicating the connection state confirmed by the confirmation unit 15 (adjacency matrix at the time of failure occurrence) is calculated. Thus, the obtained matrix is used as difference information.

FIG. 8 is a diagram illustrating an example of an adjacency matrix in a normal state.
In the adjacency matrix, P is the probe 21, I is the IaaS device 22, M is the monitoring device 23, A1 is the customer device A24, A2 is the customer device A25, B1 is the customer device B26, B2 is the customer device B27, and B3 is the customer device B28. N1 indicates a customer device N29, and N3 indicates a customer device N31.
The adjacency matrix assigns devices included in the failure information acquisition range to rows and columns, and represents the connection state by the values of intersecting elements. For example, since the probe 21 (P) and the IaaS device 22 (I) are connected, the value of the element in the P row and the I column is “1”. Similarly, the value of the element in the I row and the P column is also “1”. In addition, since the probe 21 (P) and the customer device A24 (A1) are not connected, the value of the element in the P row A1 column is “0”. Similarly, the value of the element in the A1 row and P column is also “0”.

FIG. 9 is a diagram illustrating an example of an adjacency matrix when a failure occurs.
FIG. 9 shows an adjacency matrix when a failure occurs in the customer device A24 (A1).
Since a failure has occurred in the customer device A24, the customer device A24 is not connected to the adjacent device. Therefore, the value of the element in the shaded part of the adjacency matrix is “0”.

FIG. 10 is a diagram illustrating an example of difference information.
The exclusive OR of the normal adjacency matrix shown in FIG. 8 and the fault adjacency matrix shown in FIG. 9 is calculated. Then, only the value of an element having a different value between the adjacency matrix at the time of normality and the adjacency matrix at the time of the failure, that is, the value of an element that is connected when normal (but is not connected when a failure occurs) (shaded portion) is “1”.

(S3: Filter generation step)
The determination unit 17 reads one set from the handling method storage unit 14 and generates a filter that extracts some values from the difference information based on the read set information.
Specifically, first, the determination unit 17 reads one set from the handling method storage unit 14, and based on the contract information stored in the contract storage unit 13, the monitoring unit indicates the monitoring target in the monitoring contract indicated by the read set contract ID. Identify the device. Then, the determination unit 17 generates, as a filter, an adjacency matrix indicating that only the identified devices are connected.

FIG. 11 is a diagram illustrating an example of a filter.
FIG. 11 shows a filter when a set of contract ID “001” is read.
As shown in FIG. 5, the contract ID “001” is a contract related to the customer A, and the monitoring targets are the IaaS device 22 (I), the customer device A24 (A1), and the customer device A25 (A2). It is. Therefore, an adjacency matrix indicating that only the IaaS device 22, the customer device A24, and the customer device A25 are connected is generated as a filter.

FIG. 12 is a diagram illustrating an example of SQL that identifies a device to be monitored.
The determination unit 17 can identify a device that is a monitoring target by using the SQL illustrated in FIG.
By substituting the read set of contract IDs into the contract ID value in the SQL shown in FIG. 12, the device ID of the device to be monitored can be specified. That is, by substituting the contract ID “001”, the device IDs of the IaaS device 22, the customer device A24, and the customer device A25 can be specified.

(S4: Difference determination step)
The determination unit 17 extracts information from the difference information with the filter generated in S3, and determines whether there is a difference in the connection state of the devices to be monitored based on the extracted information.
Specifically, the determination unit 17 calculates the logical product of the difference information and the filter, and determines whether or not “1” is included in the value of the obtained matrix element. If the determination unit 17 determines that “1” is included, the determination unit 17 determines that there is a difference in the connection state of the devices to be monitored.

FIG. 13 is a diagram illustrating an example of information extracted from difference information by a filter.
13 shows information extracted from the difference information shown in FIG. 10 by the filter shown in FIG.
As shown in FIG. 13, when the filter shown in FIG. 11 is used, “1” is included in the value of the matrix element. Therefore, it is determined that there is a difference in the connection state of the monitoring target devices with the contract ID “001” that is the source of the filter illustrated in FIG.

(S5: specific step)
When it is determined that there is a difference in S4, the specifying unit 18 specifies the handling method of the set read in S3 as the handling method for the detected failure.
Regarding the set of contract ID “001”, it was determined in S4 that there is a difference. Therefore, the identifying unit 18 identifies “contact customer A”, which is a handling method for the set of the contract ID “001”, as a handling method for the detected failure.
The specifying unit 18 may display the specified handling method on the display device so as to correspond to the administrator or the like of the handling specifying device 10, or send the specified handling method to the device that performs the handling. Alternatively, the response may be performed by the specified response method.

(S6: End determination step)
The determination unit 17 determines whether or not all sets have been read from the handling method storage unit 14 in S3.
The determination unit 17 ends the process when all the pairs are read (S6 is completed), and returns the process to S3 when the set that has not been read remains (S6 is not yet). Process.

  In the case of FIG. 5, there is a contract ID “002” in addition to the contract ID “001”. For this reason, the processing is sequentially executed for the sets after the contract ID “002”. As a result, there may be a plurality of handling methods specified in S5.

In the correspondence specifying apparatus 10 according to the first embodiment, the normal connection state stored in the connection information storage unit 12, the connection state at the time of failure confirmed by the confirmation unit 15, and the monitoring contract stored in the contract storage unit 13. Thus, an appropriate response method can be identified.
For example, when the network configuration changes or the monitoring contract changes, it is possible to continue to specify an appropriate response method simply by storing the changed contents in the connection information storage unit 12 or the contract storage unit 13. Is possible. Information stored in the connection information storage unit 12 and the contract storage unit 13 is information that is generally managed in the network system. Therefore, by storing the changed content in the connection information storage unit 12 or the contract storage unit 13, a new load is not applied to the administrator of the correspondence specifying device 10.

Embodiment 2. FIG.
In the first embodiment, information is extracted from the difference information based on the monitoring contract, and an appropriate handling method is specified. In the second embodiment, description will be given of extracting information from the difference information based on the monitoring contract and other conditions and specifying an appropriate response method.
In the second embodiment, parts different from the first embodiment will be described.

FIG. 14 is a diagram illustrating pairs stored in the handling method storage unit 14 according to the second embodiment.
Each set includes conditions in addition to the contract ID and contact information. Here, the monitoring level of the device is set as the condition.

Operation | movement of the corresponding | compatible identification apparatus 10 which concerns on Embodiment 2 is demonstrated.
The operation of the correspondence identifying device 10 according to the second embodiment is different from the operation of the correspondence identifying device 10 according to the first embodiment in the process of S3.
In S3, first, the determination unit 17 reads one set from the handling method storage unit 14, and based on the contract information stored in the contract storage unit 13, becomes a monitoring target in the monitoring contract specified by the read specific information of the set. Identify the device. Furthermore, the determination unit 17 identifies a device that satisfies the conditions specified by the read set among the devices to be monitored. That is, among the devices to be monitored, the device of the monitoring level specified by the read set is specified. Then, the determination unit 17 generates, as a filter, an adjacency matrix indicating that only the identified devices are connected.

FIG. 15 is a diagram illustrating an example of a filter.
FIG. 15 shows a filter when a set of contract ID “001” is read.
As shown in FIG. 5, the contract ID “001” is a contract related to the customer A, and the monitoring target is the IaaS device 22, the customer device A24, and the customer device A25. In the group with the contract ID “001”, a high monitoring level is designated as a condition. Therefore, with reference to the monitoring level shown in FIG. 3, among the IaaS devices 22, customer devices A 24, and customer devices A 25 that are the monitoring targets, the IaaS device 22 and customer device A 24 with high monitoring levels are the devices that satisfy the conditions. Identified.
Therefore, an adjacency matrix indicating that only the connection between the IaaS device 22 and the customer device A24 is generated as a filter.

FIG. 16 is a diagram illustrating an example of SQL that identifies a target device.
By substituting the read contract ID of the set into the contract ID value in SQL shown in FIG. 16, and substituting the read monitoring level of the set into the monitoring level value, the device ID of the target device. Can be specified.
That is, if the contract ID “001” is substituted and the monitoring level is “high”, the device IDs of the IaaS device 22 and the customer device A24 can be specified.

  As described above, the correspondence specifying apparatus 10 according to the second embodiment can extract information from the difference information based on the monitoring contract and other conditions, and specify an appropriate response method. Therefore, as in the first embodiment, the handling method can be specified more finely than in the first embodiment without imposing a load on the administrator of the handling specifying device 10.

  In the above description, a filter is generated that extracts information about a device to be monitored that satisfies a condition from difference information. However, two filters may be generated separately: a filter that extracts information about devices to be monitored from difference information, and a filter that extracts information about devices that satisfy a condition from difference information. In this case, in S4, after calculating the logical product of the difference information and one of the filters to generate a matrix, the logical product of the generated matrix and the other filter may be calculated.

  In the above description, the monitoring level is set as a condition. However, the condition is not limited to this, and may be specified by other information such as a device type.

  In the above description, the monitoring contract is made for each customer. However, the monitoring contract is not limited to this, and may be made in other units such as for each person in charge of the customer. For example, when a monitoring contract is made for each person in charge of a customer, when a failure occurs in a device to be monitored in the monitoring contract, it can be set to contact the person in charge of the monitoring contract.

FIG. 17 is a diagram illustrating an example of a hardware configuration of the correspondence specifying device 10.
As shown in FIG. 17, the correspondence specifying apparatus 10 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program. The CPU 911 is connected to the ROM 913, the RAM 914, the LCD 901 (Liquid Crystal Display), the keyboard 902 (K / B), the communication board 915, and the magnetic disk device 920 via the bus 912, and controls these hardware devices. Instead of the magnetic disk device 920 (fixed disk device), a storage device such as an optical disk device or a memory card read / write device may be used. The magnetic disk device 920 is connected via a predetermined fixed disk interface.

  An operating system 921 (OS), a window system 922, a program group 923, and a file group 924 are stored in the magnetic disk device 920 or the ROM 913. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 includes software, programs, and other programs that execute the functions described as “confirmation unit 15”, “difference information generation unit 16”, “determination unit 17”, “specification unit 18”, etc. Is remembered. The program is read and executed by the CPU 911.
The file group 924 includes information, data, and signal values stored in the “device information storage unit 11”, “connection information storage unit 12”, “contract storage unit 13”, and “corresponding method storage unit 14” in the above description. And variable values and parameters are stored as each item in the database. The database is stored in a recording medium such as a disk or memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for the operation of the CPU 911 such as calculation / processing / output / printing / display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the operation of the CPU 911 for extraction, search, reference, comparison, calculation, calculation, processing, output, printing, and display. Is remembered.

In the above description, the arrows in the flowchart mainly indicate input / output of data and signals, and the data and signal values are recorded in a memory of the RAM 914, other recording media such as an optical disk, and an IC chip. Data and signals are transmitted online by a bus 912, signal lines, cables, other transmission media, and radio waves.
In addition, what is described as “to part” in the above description may be “to circuit”, “to device”, “to device”, “to means”, and “to function”. It may be “step”, “˜procedure”, “˜processing”. In addition, what is described as “˜device” may be “˜circuit”, “˜device”, “˜means”, “˜function”, and “˜step”, “˜procedure”, “ ~ Process ". That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, only software, hardware such as elements, devices, substrates, and wirings, a combination of software and hardware, or a combination of firmware may be used. Firmware and software are stored in a recording medium such as ROM 913 as a program. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes a computer or the like to function as the “˜unit” described above. Alternatively, the computer or the like is caused to execute the procedures and methods of “to part” described above.

  DESCRIPTION OF SYMBOLS 10 Correspondence specific apparatus, 11 Apparatus information storage part, 12 Connection information storage part, 13 Contract storage part, 14 Corresponding method storage part, 15 Confirmation part, 16 Difference information generation part, 17 Determination part, 18 Identification part, 20 Network system, 21 Probe, 22 IaaS equipment, 23 Monitoring device, 24, 25 Customer equipment A, 26, 27, 28 Customer equipment B, 29, 30, 31, 32 Customer equipment N.

Claims (6)

A response identification device that identifies a response method when a failure is detected in a network system in which multiple devices are connected.
A connection information storage unit for storing connection information indicating a connection state between devices in a normal state in which a failure of the network system has not occurred;
A confirmation unit for confirming the connection state between adjacent devices when a failure is detected;
A difference information generation unit that generates difference information indicating a difference between a connection state indicated by the connection information stored in the connection information storage unit and a connection state confirmed by the confirmation unit;
For each monitoring contract, a contract storage unit that stores the device to be monitored,
A corresponding method storage unit for storing a plurality of sets of specific information for specifying a monitoring contract and a corresponding method;
For each pair stored by the handling method storage unit, the difference information generation unit generates a difference generated by the monitoring target device stored in the contract storage unit with respect to the monitoring contract specified by the pair specific information. A determination unit for determining whether there is a difference indicated by the information;
A correspondence identifying apparatus comprising: a identifying unit that identifies a pair of handling methods determined by the determining unit as having a difference as a handling method for a detected failure. The difference information generation unit uses the bit information in which values are arranged in a predetermined order from a connection state between predetermined devices, assuming that one of values 0 and 1 indicates connection and the other indicates no connection. Each of the connection state indicated by the information and the connection state confirmed by the confirmation unit is indicated, and the bit information regarding the connection state indicated by the connection information and the bit information regarding the connection state confirmed by the confirmation unit are exclusive. Calculating a logical sum and generating the obtained bit information as the difference information;
The determination unit generates a filter that extracts only the bits for the monitored device, and when the extracted bits include 1 in the connection state of the monitored device, there is a difference. The correspondence identifying device according to claim 1, wherein the correspondence identifying device is determined. The determination unit generates bit information which is bit information in which values are arranged in the predetermined order, and sets only the bit regarding the connection state of the monitored device as 1, and generates the difference information and the difference information. 3. The response according to claim 2, wherein a logical product with the filter is calculated and it is determined that there is a difference in the connection state of the monitored device when 1 is included in the obtained bit information. Specific device. The handling method storage unit further stores conditions for narrowing down the devices for at least some of the sets,
For the group in which the condition is stored, the determination unit narrows down the devices to be monitored stored by the contract storage unit with respect to the monitoring contract specified by the specific information of the group, by the group condition. The correspondence identifying apparatus according to claim 1, wherein it is determined whether or not the difference information indicates a difference in a connection state of a device. A response specifying method for specifying a response method when a failure is detected in a network system to which a plurality of devices are connected, and indicating a connection state between devices in a normal state in which no failure of the network system has occurred A connection information storage unit that stores information; a contract storage unit that stores a device to be monitored for each monitoring contract; a correspondence method storage unit that stores a plurality of sets of specific information and a corresponding method for specifying a monitoring contract; Is a response identification method using
When the processing device detects a failure, a confirmation process for confirming a connection state between adjacent devices;
A difference information generating step for generating difference information indicating a difference between the connection state indicated by the connection information stored in the connection information storage unit and the connection state confirmed in the confirmation step;
For each set stored in the handling method storage unit by the processing device, the difference information generating step changes to the connection state of the monitoring target device stored in the contract storage unit with respect to the monitoring contract specified by the specific information of the set. A determination step of determining whether there is a difference indicated by the difference information generated in
A handling specifying method, comprising: a specifying step of specifying, as a handling method for a detected fault, a handling method of a set determined in the determining step when the processing apparatus has a difference. A correspondence specifying program for specifying a response method when a failure is detected in a network system to which a plurality of devices are connected, and indicating a connection state between devices in a normal state in which no failure has occurred in the network system A connection information storage unit that stores information; a contract storage unit that stores a device to be monitored for each monitoring contract; a correspondence method storage unit that stores a plurality of sets of specific information and a corresponding method for specifying a monitoring contract; It is a correspondence specific program using
Confirmation process to confirm the connection status between adjacent devices when a failure is detected,
A difference information generation process for generating difference information indicating a difference between the connection state indicated by the connection information stored in the connection information storage unit and the connection state confirmed in the confirmation process;
For each set stored in the handling method storage unit, the difference generated by the difference information generation process in the connection state of the monitoring target device stored in the contract storage unit with respect to the monitoring contract specified by the specific information of the set A determination process for determining whether there is a difference indicated by the information;
A correspondence specifying program that causes a computer to execute a specific process for specifying a correspondence method determined in the determination process as a response method for a detected failure when there is a difference.

Images