JP2018073084A - Monitoring device, communication failure automatic recovery system, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To quickly enable communication over a network with a device that does not spontaneously transmit an address even when the device is exchanged.SOLUTION: Communication with a to-be-monitored device corresponding to a registered network address is confirmed. When communication with the to-be-monitored device is carried out, a to-be-monitored device database is created on the basis of an address conversion table of first network equipment and an address port conversion table and port connection state information of second network equipment. When communication with the to-be-monitored device is not carried out, whether or not a device unique address in the address port conversion table has been changed is checked. When the device unique address in the address port conversion table has been changed, whether or not the device unique address in the address conversion table has been changed is checked. When the device unique address in the address conversion table has not been changed, control for rewriting, at the first network equipment, the device unique address of the address conversion table to the device unique address of the to-be-monitored device, is performed.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a monitoring device, a communication failure automatic recovery system, a method, and a program.

  A peripheral device such as a printer or a scanner may be connected to a network such as a LAN (Local Area Network). Peripheral devices may move due to changes in the surrounding environment, or may be replaced due to failure or the like. When a peripheral device is moved or exchanged, it is necessary to manage necessary resources in the peripheral device. For this reason, Patent Document 1 proposes a peripheral device management apparatus that automatically determines the movement and replacement of peripheral devices and makes it possible to keep the resource environment of the peripheral devices on the network constant. ing.

  On the network, there are usually network (NW; network) devices (layer 2 switches, switching hubs, etc.) and gateway network (GWNW; gateway network) devices (layer 3 switches, routers, etc.) that serve as relay devices. The peripheral device is connected to the network device on the network, and a network address such as an IP (Internet Protocol) address and a device unique address such as a MAC (Media Access Control) address are set. Also, the GWNW device registers an ARP (Address Resolution Protocol) table in which an IP address and a MAC address set in the peripheral device are associated, and performs data transfer processing based on the ARP.

JP 2002-108734 A

  The following analysis is given by the inventor.

  When a peripheral device fails, normally, the same IP address as that of the failed peripheral device is set in another peripheral device, and the failed peripheral device is replaced with another peripheral device. However, since the peripheral device does not have a function of spontaneously transmitting an IP address or a MAC address to the network, the ARP table stored in the GWNW device on the network is not immediately updated. In other words, immediately after the replacement of the peripheral device, the ARP table stored in the GWNW device remains associated with the MAC address and IP address of the peripheral device before replacement, and the MAC address and IP address of the peripheral device after replacement. Is not associated with. For this reason, there is a problem that a terminal connected to the network cannot immediately communicate with the replaced peripheral device, resulting in a communication failure.

  Here, in order to communicate with the replaced peripheral device, the GWNW device waits until the ARP table holding time elapses and the ARP table is updated, or when the GWNW device can be stopped, the GWNW device is stopped. It was necessary to restart and update the ARP table.

  However, when waiting until the ARP table is updated, the time during which the peripheral device cannot be used becomes long. For example, the retention time of the ARP table of a standard GWNW device is about 4 hours.

  In addition, when updating and updating the ARP table by stopping and restarting the GWNW device, there is no frequent opportunity to stop the GWNW device, and if the GWNW device is forcibly stopped, other devices on the network Communication may be affected and a communication failure may occur.

  A main object of the present invention is to provide a monitoring device, a communication failure automatic recovery system, a method, and a program that enable early communication with the device even when a device that does not spontaneously transmit an address is replaced. It is.

  The monitoring device according to the first aspect stores a communication unit capable of communicating with the first network device, the second network device, and the monitoring target device on the network, and a monitoring target device database including information on the monitoring target device. A storage unit; and a control unit that controls the communication unit and the storage unit. The first network device stores an address conversion table. The second network device stores an address port conversion table and port connection state information. The monitoring target device stores a network address and a device unique address. In the address conversion table, the network address and the device unique address are associated with each other. In the address port conversion table, the device-specific address is associated with the physical port of the second network device to which the monitoring target device is connected. In the port connection status information, the physical port of the second network device and the connection status of the monitoring target device with respect to the physical port are associated with each other. The control unit performs processing for confirming communication with the monitoring target device corresponding to a registered network address, and when communicating with the monitoring target device, the address conversion table of the first network device, and the first Based on the address port conversion table and the port connection state information of two network devices, the monitoring target device database in which the network address, the device unique address, the physical port, and the connection state are associated with each other is created. If the processing does not communicate with the monitored device, the device unique address of the address port conversion table of the second network device connected to the monitored device and the device unique address of the monitored device database By comparing, the address A process for confirming whether or not the device unique address of the port translation table has been changed, and when the device unique address of the address port translation table has been changed, the first network closest to the monitored device Processing for checking whether or not the device unique address of the address conversion table has been changed by comparing the device unique address of the address translation table of the device with the device unique address of the monitored device database If the device unique address in the address translation table has not been changed, control is performed so that the device unique address in the address translation table is rewritten to the device unique address of the monitoring target device in the first network device. And processing.

  A communication failure automatic recovery system according to a second aspect includes a monitoring device according to a first aspect, the monitoring target device, the first network device, and the second network device.

  A communication failure automatic recovery method according to a third aspect includes a communication unit capable of communicating with a first network device, a second network device, and a monitoring target device on a network, and a monitoring target device database including information on the monitoring target device Is a communication failure recovery method for recovering a communication failure that has occurred in the monitoring target device using a monitoring device that includes a storage unit that stores the communication unit and a control unit that controls the communication unit and the storage unit. The first network device stores an address conversion table. The second network device stores an address port conversion table and port connection state information. The monitoring target device stores a network address and a device unique address. In the address conversion table, the network address and the device unique address are associated with each other. In the address port conversion table, the device-specific address is associated with the physical port of the second network device to which the monitoring target device is connected. In the port connection status information, the physical port of the second network device and the connection status of the monitoring target device with respect to the physical port are associated with each other. In the communication failure recovery method, a step of confirming communication with the monitoring target device corresponding to a registered network address, and when communicating with the monitoring target device, the address conversion table of the first network device, and Based on the address port conversion table and the port connection status information of the second network device, the monitoring target device database in which the network address, the device unique address, the physical port, and the connection status are associated with each other. And the device unique address of the address port conversion table of the second network device connected to the monitored device and the device unique address of the monitored device database when not creating and communicating with the monitored device By comparing with A step of confirming whether or not the device unique address of the address port conversion table has been changed; and when the device unique address of the address port conversion table has been changed, the first closest to the monitored device By comparing the device unique address of the address translation table of the network device with the device unique address of the monitored device database, it is confirmed whether or not the device unique address of the address conversion table has been changed. And when the device unique address of the address conversion table has not been changed, the device unique address of the address translation table is rewritten to the device unique address of the monitoring target device in the first network device. And a step of performing.

  A communication failure automatic recovery program according to a fourth aspect includes a communication unit capable of communicating with a first network device, a second network device, and a monitoring target device on a network, and a monitoring target device database including information on the monitoring target device A communication failure recovery program that recovers a communication failure that has occurred in the monitored device by being executed by a monitoring device that includes a storage unit that stores the communication unit and a control unit that controls the communication unit and the storage unit. is there. The first network device stores an address conversion table. The second network device stores an address port conversion table and port connection state information. The monitoring target device stores a network address and a device unique address. In the address conversion table, the network address and the device unique address are associated with each other. In the address port conversion table, the device-specific address is associated with the physical port of the second network device to which the monitoring target device is connected. In the port connection status information, the physical port of the second network device and the connection status of the monitoring target device with respect to the physical port are associated with each other. The communication failure recovery program includes a step of confirming communication with the monitored device corresponding to a registered network address, and when communicating with the monitored device, the address conversion table of the first network device, and Based on the address port conversion table and the port connection status information of the second network device, the monitoring target device database in which the network address, the device unique address, the physical port, and the connection status are associated with each other. And the device unique address of the address port conversion table of the second network device connected to the monitored device and the device unique address of the monitored device database when not creating and communicating with the monitored device Compare with And confirming whether or not the device unique address of the address port translation table has been changed, and when the device unique address of the address port translation table has been changed, is closest to the monitored device Whether the device unique address of the address translation table has been changed by comparing the device unique address of the address translation table of the first network device with the device unique address of the monitored device database And when the device unique address of the address translation table has not been changed, the device unique address of the address translation table is rewritten to the device unique address of the monitoring target device in the first network device. To control Tsu and up, to the execution.

  According to the first to fourth viewpoints, even if a monitoring target apparatus that does not spontaneously transmit an address is replaced, it is possible to communicate with the monitoring target apparatus at an early stage on the network.

It is the block diagram which showed typically the structure of the communication failure automatic recovery system which concerns on Embodiment 1. FIG. It is the schematic diagram which showed the structure of the monitoring object apparatus database used with the monitoring apparatus in the communication failure automatic recovery system which concerns on Embodiment 1. FIG. It is the schematic diagram which showed the structure of the ARP table used by the GWNW apparatus in the communication failure automatic recovery system which concerns on Embodiment 1, the FDB (Forwarding DataBase) table used by NW apparatus, and link status information. 3 is a flowchart schematically showing the operation of the monitoring device in the communication failure automatic recovery system according to the first embodiment. 5 is a flowchart following FIG. 4 schematically showing the operation of the monitoring device in the communication failure automatic recovery system according to the first embodiment. It is the block diagram which showed typically the structure of the communication failure automatic recovery system which concerns on Embodiment 2. FIG. 6 is a flowchart schematically showing the operation of a monitoring device in the communication failure automatic recovery system according to the second embodiment.

  Hereinafter, embodiments will be described with reference to the drawings. Note that, in the present application, where reference numerals are attached to the drawings, these are only for the purpose of helping understanding, and are not intended to be limited to the illustrated embodiments. In addition, the following embodiment is an illustration to the last and does not limit this invention.

[Embodiment 1]
A communication failure automatic recovery system according to Embodiment 1 will be described with reference to the drawings. FIG. 1 is a block diagram schematically illustrating a configuration of a communication failure automatic recovery system according to the first embodiment. FIG. 2 is a schematic diagram illustrating a configuration of a monitoring target device database used in the monitoring device in the communication failure automatic recovery system according to the first embodiment. FIG. 3 is a schematic diagram illustrating a configuration of an ARP table used in the GWNW device, an FDB table used in the NW device, and link status information in the communication failure automatic recovery system according to the first embodiment.

  The communication failure automatic recovery system 1 is a system having a function of automatically recovering when a communication failure with respect to the monitoring target device 500 occurs on a network (for example, LAN) including the GW NW device 200 and the NW devices 300 and 400 ( (See FIG. 1). The communication failure automatic recovery system 1 includes a monitoring device 100, a GWNW device 200, NW devices 300 and 400, and a monitoring target device 500.

  The monitoring device 100 is a device that monitors the communication state of the monitoring target device 500 connected to the network (see FIG. 1). The monitoring apparatus 100 includes a communication unit 101, an input unit 102, an output unit 103, a control unit 104, and a storage unit 105.

  The communication unit 101 is a functional unit that is communicably connected to the GW NW device 200, the NW devices 300 and 400, and the monitoring target device 500 via a network (see FIG. 1). As the communication unit 101, for example, a LAN interface connectable with a LAN cable can be used. The communication unit 101 is communicably connected to the control unit 104 and is controlled by the control unit 104.

  The input unit 102 is a functional unit that can input information by a user operation (see FIG. 1). As the input unit 102, for example, a keyboard, a mouse, a touch panel, a microphone, or other input means can be used. The input unit 102 is communicably connected to the control unit 104 and transmits the input information to the control unit 104.

  The output unit 103 is a functional unit for outputting information to the outside of the monitoring device 100 (see FIG. 1). As the output unit 103, for example, an output unit such as a display for displaying, a printer for performing printing, a communication device for transmitting to a predetermined terminal or the like can be used. The output unit 103 is communicably connected to the control unit 104 and receives information output from the control unit 104.

  The control unit 104 is a functional unit that controls the communication unit 101, the input unit 102, the output unit 103, and the storage unit 105 (see FIG. 1). The control unit 104 executes programs (including tools) and software stored in the storage unit 105 to control each functional unit and external devices / devices and perform information processing. The control unit 104 controls transmission / reception of information in the communication unit 101. The control unit 104 performs control so that the information input by the input unit 102 is captured. The control unit 104 performs control so that information to be output is output from the output unit 103. The control unit 104 controls reading and writing of data and files in the storage unit 105. The detailed operation when the control unit 104 executes the communication failure automatic recovery program 107 will be described in the description of the operation of the communication failure automatic recovery system.

  The storage unit 105 is a functional unit that stores various data, files, programs, and the like (see FIG. 1). The storage unit 105 stores a monitoring target device database (DB; DataBase) 106 and a communication failure automatic recovery program 107.

  The monitoring target device DB 106 is a database in which device names, IP addresses, MAC addresses, physical ports, and link status corresponding to each other are associated (see FIGS. 1 and 2). The monitoring target device DB 106 is created in time series by executing the data acquisition tool 109 of the communication failure automatic recovery program 107 by the control unit 104, and is added (updated) every predetermined time.

  Here, the “device name” is the name, model number, identifier, and the like of the monitoring target device 500. The “IP address” is a network address set for the monitoring target device 500 that transmits / receives a packet in the IP, and is set later by the user. The “MAC address” is a device unique address set for the monitored device 500 to be controlled for access, and is mainly set in advance by the manufacturer and may be set later by the user. The “physical port” is a physical interface of an NW device to which a device related to the device name is connected via a LAN cable.

  “Link status” is a connection state of a physical port of an NW device to which a device related to the device name is connected via a LAN cable. When the link status is “UP”, the link is normally linked up. For example, in FIG. 1, the monitoring target device 500 is connected to the physical port k of the NW device 400 via the LAN cable. A state in which the device 500 can be recognized and can communicate with the monitoring target device 500 is shown. The link status is “DOWN” when the link is not normally up, for example, in FIG. 1, the monitoring target device 500 is not connected to the physical port of the NW device 400 via the LAN cable, or the monitoring target This shows a state in which the power of the device 500 is off, the monitoring target device 500 cannot be recognized, and communication with the monitoring target device 500 is not possible.

  The communication failure automatic recovery program 107 is a program for automatically recovering when a communication failure with respect to the monitoring target device 500 occurs on the network (see FIG. 1). The communication failure automatic recovery program 107 includes a failure monitoring tool 108, a data acquisition tool 109, an ARP table clear tool 110, and a GWNW device identification tool 111.

  The failure monitoring tool 108 is a program for monitoring a communication failure of the monitoring target device 500 (see FIG. 1). The failure monitoring tool 108 includes a Ping (Packet Internet Groper) command.

  Here, the Ping command is a program that uses the Internet Control Message Protocol (ICMP) echo command, and sends a character string to a specified destination (IP address or host name). A command (command) for confirming the connection.

  The data acquisition tool 109 is a program for acquiring information (for example, MIB (Management Information Base) -2 information) stored in a device on a network by using an SNMP (Simple Network Management Protocol) polling function. (See FIG. 1).

  Here, the SNMP polling function periodically transmits management information (here, the ARP table 201 and the FDB table 401) from the devices (here, the GWNW device 200 and the NW device 400) using a protocol for managing the network by the monitoring apparatus 100. The link status information 402) is read out.

  The MIB-2 information is information defined in RFC (Request for Comments) 1213 of a proposal issued by the Internet Engineering Task Force (IETF), which is a standardization organization for Internet-related technologies.

  The ARP table clear tool 110 is a program for clearing (erasing) the cache of the ARP table of the GWNW device specified by the GWNW device specifying tool 111 (see FIG. 1).

  Here, the ARP table is a table (address conversion table) in which an IP address and a MAC address are associated with each other, and is used to obtain a MAC address on the network from the IP address (see FIG. 3). The ARP table is one piece of MIB-2 information.

  The GWNW device identification tool 111 is a program for executing a route tracking command (Traceroute command) to identify the last recognized device as the GWNW device closest to the monitoring target device 500 (see FIG. 1). .

  The GWNW device 200 is a relay device (first network device) disposed between the NW device 300 and the NW device 400 on the network (see FIG. 1). The GWNW device 200 may be a device that performs data transfer processing between network layers (third layer), such as a layer 3 switch or a router. The GWNW device 200 has a protocol conversion function between the network layer and the data link layer. The GWNW device 200 stores an APR table 201, and has a function of converting an address of a partner to communicate with based on the APR table 201 (see FIG. 3). When the MAC address of the ARP table 201 is cleared and communication with the monitoring target device 500 occurs, the GWNW device 200 reads the IP address and MAC address stored in the monitoring target device 500, and reads the read IP address and MAC It has a function of rewriting the ARP table 201 based on the address.

  The NW device 300 is a relay device arranged between the GW NW device 200 and the monitoring device 100 on the network (see FIG. 1). The NW device 300 may be a device that performs data transfer processing of the data link layer (second layer), such as a layer 2 switch or a switching hub. The NW device 300 stores an FDB table (not shown) and link status information (not shown), and transfers a packet to a communication partner who wants to communicate based on the FDB table and link status information. The NW device 300 is directly or indirectly connected to the GW NW device 200 via a LAN cable. The NW device 300 is connected to the monitoring device 100 via a LAN cable.

  The NW device 400 is a relay device (second network device) disposed between the GW NW device 200 and the monitoring target device 500 on the network (see FIG. 1). The NW device 400 may be a device that performs communication in the data link layer (second layer), such as a layer 2 switch or a switching hub. The NW device 400 stores an FDB table 401 and link status information 402, and transfers a packet to a partner with which communication is desired based on the FDB table 401 and link status information 402 (see FIG. 3). The NW device 400 is connected to the GW NW device 200 via a LAN cable. The NW device 400 has n physical ports 403. The kth physical port 403 is connected to the monitoring target device 500 via a LAN cable. When the monitoring target device 500 connected to any one of the physical ports 403 is replaced or when the monitoring target device 500 is newly connected to any one of the physical ports 403, the NW device 400 spontaneously The MAC address is read from the monitoring target device 500, and the MAC address of the FDB table corresponding to the physical port 403 is rewritten to the read MAC address.

  Here, the FDB table is a table (address port conversion table) in which the MAC address is associated with the physical port (see FIG. 3).

  The link status information is information (port connection status information) indicating the connection status (link status) of the physical port of the NW device 400 to which the monitoring target device 500 is connected (see FIG. 3).

  The monitoring target device 500 is a device monitored by the monitoring device 100 (see FIG. 1). The monitoring target device 500 stores an IP address 501 and a MAC address 502. As the monitoring target device 500, a device that does not spontaneously transmit the IP address 501 and the MAC address 502 to the network, for example, a peripheral device such as a single-function printer or scanner can be used. The monitoring target device 500 is connected to the same segment as the NW device 400 and is connected to the kth physical port 403 of the NW device 400 via a LAN cable. Here, the segment is specifically a unit of a range constituting the network, and in this case, is a range delimited by the GWNW device 200.

  Next, the operation of the communication failure automatic recovery system according to the first embodiment will be described with reference to the drawings. 4 and 5 are flowcharts schematically showing the operation of the monitoring device in the communication failure automatic recovery system according to the first embodiment. Refer to FIG. 1 to FIG. 3 for the configuration of the communication failure automatic recovery system. The following operation of the monitoring device 100 is the operation of the control unit 104 when the communication failure automatic recovery program 107 is executed.

  First, the monitoring device 100 registers the input IP address in the storage unit 105 when the user inputs the same IP address as the IP address 501 stored in the monitoring target device 500 from the input unit 102 (step A1, (See FIG. 4).

  After step A1, or after step A5, or when the MAC addresses match (YES in step A20), the monitoring device 100 is registered in step A1 using the Ping command of the failure monitoring tool 108. It confirms (communication confirmation) whether or not it communicates with the monitoring target device 500 corresponding to the IP address (whether a communication failure to the monitoring target device 500 has been detected; alive monitoring) (see step A2, FIG. 4). When not communicating with the monitoring target device 500 (NO in step A2), the process proceeds to step A6.

  When communicating with the monitoring target device 500 (YES in step A2; when no communication failure to the monitoring target device 500 is detected, when there is a response to the Ping command), the monitoring device 100 uses the SNMP polling function of the data acquisition tool 109. In the MIB-2 information stored in the GWNW device 200 closest to the monitoring target device 500 based on the IP address registered in step A1 (or the IP address of the past monitoring target device DB 106 is acceptable). The ARP table 201 and the FDB table 401 and link status information 402 stored in the NW device 400 to which the monitoring target device 500 is connected are acquired (see step A3 and FIG. 4).

  Here, in the acquisition of the ARP table 201, the FDB table 401, and the link status information 402 in step A3, the monitoring device 100 is based on the IP address registered in step A1 (the IP address of the past monitoring target device DB 106 may be used). The ARP table 201 stored in the GWNW device 200 closest to the monitoring target device 500 is acquired, and the MAC address corresponding to the IP address registered in step A1 is specified based on the acquired ARP table 201, and specified. The FDB table 401 stored in the NW device 400 to which the monitoring target device 500 is connected is acquired based on the specified MAC address, the physical port is specified based on the acquired FDB table 401, and the specified physical port is specified. Based on whether the monitoring target device 500 is connected. Obtaining the link status information 402 stored in the NW device 400, based on the obtained link status information 402, it is possible to identify a link status corresponding to the specified physical port.

  After step A3, the monitoring apparatus 100 identifies the physical port of the NW device 400 to which the monitoring target apparatus 500 is connected based on the acquired ARP table 201, FDP table 401, and link status information 402. The device DB 106 is created, and the created monitoring target device DB 106 is registered (or added) in the storage unit 105 (step A4, see FIG. 4).

  Here, in the creation of the monitoring target device DB 106, the monitoring device 100 includes the IP address registered in Step A1, the MAC address included in the ARP table 201, the FDP table 401, and the link status information 402 acquired in Step A3, The physical port and the link status can be created in association with each other (see FIG. 2).

  After step A4 or when the number of communication confirmations is less than the predetermined number (YES in step A7), the monitoring apparatus 100 waits for a predetermined time (step A5, see FIG. 4), and then returns to step A2.

  When communication with the monitoring target device 500 is not performed (NO at step A2, when a communication failure to the monitoring target device 500 is detected, when there is no response to the Ping command), the monitoring device 100 registers the IP address registered at step A1 ( Based on the past IP address of the monitoring target device DB 106), the monitoring device 100 confirms whether or not the monitoring target device DB 106 created in the past exists (step A6, see FIG. 4). If the monitoring target device DB 106 created in the past does not exist (NO in step A6), the monitoring device 100 cannot identify the physical port 403 of the NW device 400 to which the monitoring target device 500 is connected, so step A7 Proceed to

  Here, the past means the time before the time when the Ping response to the monitoring target device 500 disappears.

  When the monitoring target device DB 106 created in the past does not exist (NO in Step A6), the monitoring device 100 determines whether or not the number of communication confirmations is less than a predetermined number set in advance after starting the communication confirmation in Step A2. (See step A7, FIG. 4). When the number of communication confirmations is less than the predetermined number (YES in step A7), the process proceeds to step A5. When the number of communication confirmations is not less than the predetermined number (NO in step A7), the process proceeds to step A10.

  When the monitoring target device DB 106 created in the past exists (YES in step A6), the monitoring device 100 uses the SNMP polling function of the data acquisition tool 109 from the NW device 400 to which the monitoring target device 500 is connected. The link status information 402 corresponding to the physical port of the monitoring target device DB 106 created in the past (here, the kth physical port 403 of the NW device 400 to which the monitoring target device 500 of FIG. 1 is connected) is acquired ( Step A8, see FIG. 4).

  After step A8, the monitoring apparatus 100 checks whether or not the link status of the link status information 402 acquired in step A8 is UP (step A9, see FIG. 4).

  When the number of communication confirmations is not less than the predetermined number (NO in step A7), or when the link status is not UP (NO in step A9), the monitoring device 100 cannot communicate with the monitoring target device 500 (in the NW device 400). It is determined that the monitoring target device 500 is not connected to the physical port via the LAN cable, or the monitoring target device 500 is powered off, and communication with the monitoring target device 500 is not possible. A message to that effect is output from the output unit 103 (step A10, see FIG. 4), and then the process ends.

  When the link status is UP (YES in step A9), the monitoring apparatus 100 is created in the past from the NW device 400 to which the monitoring target apparatus 500 is connected, using the SNMP polling function of the data acquisition tool 109. The FDB table 401 corresponding to the physical port of the monitoring target apparatus DB 106 (here, the one corresponding to the kth physical port 403 in FIG. 1) is acquired (step A11, see FIG. 4).

  The NW device 400 reads the MAC address 501 stored in the monitoring target device 500 when the monitoring target device 500 is replaced and is normally linked up, and the FDB of the NW device 400 itself (NW device 400). In the table 401, the MAC address corresponding to the physical port 403 (here, the kth physical port 403 in FIG. 1) of the NW device 400 to which the monitoring target device 500 is connected is rewritten to the read MAC address 501.

  After step A11, the monitoring apparatus 100 relates to the physical port of the monitoring target apparatus DB 106 created in the past (here, the one corresponding to the kth physical port 403 in FIG. 1) of the FDB table 401 acquired in step A11. The MAC address and the MAC address of the monitoring target device DB 106 created in the past are compared to determine whether or not the MAC address of the FDB table has been changed (see step A12, FIG. 5). If the MAC address has not been changed (NO in step A12), the process proceeds to step A16.

  If the MAC address has been changed (YES in step A12), the monitoring apparatus 100 determines that the monitoring target apparatus 500 has been replaced, and uses the path tracking command of the GWNW device identification tool 111 for the monitoring target apparatus 500. Then, based on the IP address registered in step A1 (or the IP address of the past monitoring target device DB 106 is acceptable), the GWNW device 200 closest to the monitoring target device 500 is specified (step A13, see FIG. 5).

  Here, when the path tracking command is executed, all GWNW devices existing on the path between the monitoring device 100 and the monitoring target device 500 are recognized, but the GWNW devices closest to the monitoring device 100 are sequentially recognized, Finally, the GWNW device 200 closest to the monitoring target device 500 is recognized, and the last recognized device is identified as the GWNW device closest to the monitoring target device 500.

  After step A13, the monitoring apparatus 100 uses the SNMP polling function of the data acquisition tool 109 for the GWNW device 200 closest to the monitoring target apparatus 500 to register the IP address (past monitoring). The ARP table 201 stored in the GWNW device 200 is acquired based on the IP address of the target device DB 106 (see step A14, FIG. 5).

  After step A14, the monitoring device 100 compares the MAC address of the ARP table acquired in step A14 with the MAC address of the monitoring target device DB 106 created in the past with respect to the IP address registered in step A1. It is determined whether or not the MAC addresses are the same (see step A15, FIG. 5). If the MAC addresses are the same (YES in step A15), the process proceeds to step A17. If the MAC addresses are not the same (NO in step A15), the process proceeds to step A16.

  When the MAC address has not been changed (NO at step A12), when the MAC addresses are not the same (NO at step A15), when not communicated with the monitoring target device 500 (NO at step A18), or between the MAC addresses If they do not match (NO in step A20), the monitoring apparatus 100 determines that there is another failure in the monitoring target apparatus 500, and outputs a message to that effect from the output unit 103 (step A16, see FIG. 5). ,finish.

  If the MAC addresses are the same (YES in step A15), the monitoring apparatus 100 determines that the ARP table 201 of the GWNW device 200 for the IP address 501 stored in the monitoring target apparatus 500 has not been updated, and step A1 Based on the IP address registered in step (or the IP address of the past monitoring target device DB 106 is acceptable), the remote connection is made to the GWNW device 200 closest to the monitoring target device 500 and the ARP cache clear command is used. Then, the MAC address of the ARP table 201 of the corresponding GWNW device 200 is cleared (erased) (step A17, see FIG. 5).

  Here, the GWNW device 200 closest to the monitoring target device 500 receives the IP address stored in the monitoring target device 500 when communication with the monitoring target device 500 occurs after the MAC address of the ARP table 201 is cleared. And the MAC address are read, and the ARP table 201 is rewritten based on the read IP address and MAC address.

  After step A17, the monitoring apparatus 100 communicates with the monitoring target apparatus 500 using the Ping command of the failure monitoring tool 108 to communicate with the monitoring target apparatus 500 corresponding to the IP address registered in step A1. Confirm (see step A18, FIG. 5).

  When not communicating with the monitoring target device 500 (NO in step A18), the process proceeds to step A16.

  When communicating with the monitoring target device 500 (YES in step A18), the monitoring device 100 uses the SNMP polling function of the data acquisition tool 109 to register from the GWNW device 200 closest to the monitoring target device 500 in step A1. The ARP table 201 corresponding to the IP address thus obtained is acquired (step A19, see FIG. 5).

  After step A19, the monitoring apparatus 100 compares the MAC address of the ARP table 201 acquired in step A19 with the MAC address of the FDB table acquired in step A11, and determines whether or not the MAC addresses match. (See step A20, FIG. 5). If the MAC addresses do not match (NO in step A20), the process proceeds to step A16. If the MAC addresses match (YES in step A20), the process returns to step A2. If the MAC addresses match (YES in step A20), the monitoring apparatus 100 may determine that the communication failure recovery has been completed and output a message indicating failure recovery from the output unit 103.

  According to the first embodiment, by registering the IP address set in the monitoring target device 500 in advance, even if a communication failure occurs by replacing the monitoring target device 500 that does not spontaneously transmit an address, It is possible to automatically detect a communication failure, automatically recover from the communication failure without affecting the communication of other devices connected to the network, and communicate with the monitored device 500 after replacement on the network at an early stage. Can be. That is, a communication failure due to the ARP table 201 of the GWNW device 200 on the network not being updated when the monitoring target device 500 is replaced is automatically detected, and the ARP table 201 is automatically updated, so that the monitored target device after replacement It is possible to restore the communication so that it can immediately communicate with 500.

[Embodiment 2]
A communication failure automatic recovery system according to Embodiment 2 will be described with reference to the drawings. FIG. 6 is a block diagram schematically illustrating the configuration of the communication failure automatic recovery system according to the second embodiment.

  The communication failure automatic recovery system 1 is a system having a function of automatically recovering when a communication failure occurs on the monitoring target device 500 on the network including the first network device 200 and the second network device 400 (see FIG. 6). ). The communication failure automatic recovery system 1 includes a monitoring device 100, a first network device 200, a second network device 400, and a monitoring target device 500.

  The monitoring device 100 is a device that monitors the communication state of the monitoring target device 500 connected to the network (see FIG. 6). The monitoring device 100 includes a communication unit 101, a control unit 104, and a storage unit 105.

  The communication unit 101 is a functional unit capable of communicating with the first network device 200, the second network device 400, and the monitoring target device 500 on the network. The control unit 104 is a functional unit that controls the communication unit and the storage unit. The storage unit 105 is a functional unit that stores a monitoring target device DB 106 including information related to the monitoring target device 500. The monitoring target device DB 106 is a database in which network addresses, device unique addresses, physical ports, and connection states are associated with each other. Details of the operation of the control unit 104 will be described later.

  The first network device 200 is a relay device arranged between the monitoring device 100 on the network and the second network device 400 (see FIG. 6). The first network device 200 stores an address conversion table 201. In the address conversion table 201, a network address and a device unique address related to the monitoring target device 500 are associated with each other.

  The second network device 400 is a relay device arranged between the first network device 200 and the monitoring target device 500 on the network (see FIG. 6). The second network device 400 stores an address port conversion table 401 and port connection state information 402 related to the monitoring target device 500. In the address port conversion table 401, a device specific address related to the monitoring target device 500 is associated with a physical port 403 of the second network device 400 to which the monitoring target device 500 is connected. The port connection status information 402 associates the physical port 403 of the second network device 400 with the connection status of the monitoring target device 500 with respect to the physical port 403.

  The monitoring target device 500 is a device monitored by the monitoring device 100 (see FIG. 6). The monitoring target device 500 stores a network address 501 and a device unique address 502. The monitoring target device 500 does not spontaneously transmit the network address and the device unique address 502 to the network.

  Next, the operation of the communication failure automatic recovery system according to the second embodiment will be described with reference to the drawings. FIG. 7 is a flowchart schematically showing the operation of the monitoring device in the communication failure automatic recovery system according to the second embodiment. Refer to FIG. 6 for the configuration of the communication failure automatic recovery system. The following operation of the monitoring device 100 is the operation of the control unit 104.

  First, the monitoring device 100 confirms communication with the monitoring target device 500 corresponding to the registered network address (step B1).

  When communicating with the monitoring target device 500 (YES in step B1), the monitoring device 100, the address conversion table 201 of the first network device 200, the address port conversion table 401 and the port connection state information 402 of the second network device 400 are displayed. The monitoring target device DB 106 in which the network address, device unique address, physical port, and connection state associated with each other are associated is created (step B2), and after a predetermined time has elapsed, the process returns to step B1.

  When the monitoring target device 500 does not communicate (NO in Step B1), the monitoring device 100 stores the device unique address in the address port conversion table 401 of the second network device 400 connected to the monitoring target device 500 and the monitoring target device DB 106. By comparing with the device unique address, it is confirmed whether or not the device unique address in the address port conversion table 401 has been changed (step B3). If the device unique address in the address port conversion table 401 has not been changed (NO in step B3), it is determined that there is another failure in the monitoring target device 500, and the process ends.

  When the device unique address of the address port conversion table 401 is changed (YES in Step B3), the monitoring device 100 includes the device unique address in the address conversion table 201 of the first network device 200 closest to the monitoring target device 500, and By comparing with the device unique address of the monitoring target device DB 106, it is confirmed whether or not the device unique address of the address conversion table 201 has been changed (step B4). If the device unique address in the address conversion table 201 has been changed (YES in step B4), it is determined that there is another failure in the monitoring target device 500, and the process ends.

  When the device unique address of the address conversion table 201 has not been changed (NO in Step B4), the monitoring device 100 uses the device unique address of the address conversion table 201 as the device unique address of the monitoring target device 500 in the first network device 200. Control is performed to rewrite to 502 (step B5), and then the process returns to step B1.

  According to the second embodiment, even if the monitoring target device 500 that does not spontaneously transmit an address is replaced, it is possible to communicate with the monitoring target device 500 at an early stage on the network.

(Appendix)
In the present invention, the monitoring apparatus according to the first aspect is possible.

  In the monitoring device according to the first aspect, when the control unit does not communicate with the monitoring target device, the connection state of the port connection state information of the second network device connected to the monitoring target device is Including the process of confirming whether or not the connection is established, and the process of confirming whether or not the device-specific address in the address port conversion table has been changed is that the connection state of the port connection state information is connected. If you do.

  The monitoring apparatus according to the first aspect includes an output unit that outputs information to the outside and is controlled by the control unit. The control unit further performs a process of controlling the output unit to output a message indicating that communication with the monitoring target device is not possible when the connection state of the port connection state information is not connected. .

  In the monitoring device according to the first aspect, when the control unit does not communicate with the monitoring target device, the control unit further performs a process of confirming whether the monitoring target device database corresponding to the monitoring target device exists. Do. The process of checking whether or not the device unique address of the address port conversion table has been changed is performed when the monitoring target device database corresponding to the monitoring target device exists.

  In the monitoring device according to the first aspect, the monitoring device further includes an output unit that outputs information to the outside and is controlled by the control unit. The control unit further performs a process of controlling the output unit to output a message indicating that communication with the monitoring target device is not possible when the monitoring target device database corresponding to the monitoring target device does not exist. Do.

  In the monitoring device according to the first aspect, in the process of controlling the first network device to rewrite the device unique address of the address conversion table to the device unique address of the device to be monitored, the monitoring target device By erasing the device specific address of the address conversion table of the first network device corresponding to the network address of the database, the device specific address of the address conversion table is stored in the first network device. Control is performed so that the device-specific address is rewritten.

  In the monitoring device according to the first aspect, the monitoring device further includes an output unit that outputs information to the outside and is controlled by the control unit. If the device unique address of the address port translation table has not been changed, or if the device unique address of the address translation table has been changed, the control unit further causes another failure to the monitored device. A process for controlling to output a message to the effect from the output unit is performed.

  In the monitoring device according to the first aspect, the control unit further includes a process of confirming communication with the monitoring target device after rewriting the device unique address, and the monitoring target device after rewriting the device unique address. The device unique address in the address translation table of the first network device is compared with the device unique address in the address port translation table of the second network device. And confirming whether or not the two match.

  In the monitoring device according to the first aspect, the monitoring device further includes an output unit that outputs information to the outside and is controlled by the control unit. When the control unit does not communicate with the monitoring target device after rewriting the device specific address, or when the device specific addresses of the address conversion table and the address port conversion table do not match, the monitoring target device A process for controlling to output from the output unit a message indicating that there is another failure.

  In the monitoring device according to the first aspect, the second network device spontaneously detects the monitoring target when the monitoring target device is replaced or when the monitoring target device is newly connected. The device has a function of reading the device unique address from the device and rewriting the device unique address of its own address port conversion table with the device unique address of the monitoring target device based on the read device unique address.

  In the present invention, the communication failure automatic recovery system according to the second aspect is possible.

  In the present invention, the communication failure automatic recovery method according to the third aspect is possible.

  In the present invention, the communication failure automatic recovery program according to the fourth aspect is possible.

  The disclosure of the above patent document is incorporated herein by reference. Within the scope of the entire disclosure (including claims and drawings) of the present invention, the embodiments can be changed and adjusted based on the basic technical concept. Various combinations or selections of various disclosed elements (including each element of each claim, each element of each embodiment, each element of each drawing, etc.) within the framework of the entire disclosure of the present invention (not selected if necessary) Is possible. That is, the present invention naturally includes various variations and modifications that could be made by those skilled in the art according to the entire disclosure including the claims and the drawings, and the technical idea. Further, regarding numerical values and numerical ranges described in the present application, it is considered that any intermediate value, lower numerical value, and small range are described even if not specified.

DESCRIPTION OF SYMBOLS 1 Communication failure automatic recovery system 100 Monitoring apparatus 101 Communication part 102 Input part 103 Output part 104 Control part 105 Storage part 106 Monitoring object apparatus DB
107 communication failure automatic recovery program 108 failure monitoring tool 109 data acquisition tool 110 ARP table clear tool 111 GWNW device identification tool 200 GWNW device (first network device)
201 ARP table (address conversion table)
300 NW device 400 NW device (second network device)
401 FDB table (address port conversion table)
402 Link status information (port connection status information)
403 Physical port 500 Monitored device 501 IP address (network address)
502 MAC address (device unique address)

Claims (10)

A communication unit capable of communicating with the first network device and the second network device on the network and the monitoring target device;
A storage unit for storing a monitoring target device database including information on the monitoring target device;
A control unit for controlling the communication unit and the storage unit;
With
The first network device stores an address conversion table;
The second network device stores an address port conversion table and port connection state information,
The monitored device stores a network address and a device specific address,
In the address conversion table, the network address and the device unique address are associated,
In the address port conversion table, the device unique address is associated with a physical port of the second network device to which the monitoring target device is connected,
The port connection status information is associated with the physical port of the second network device and the connection status of the monitoring target device with respect to the physical port,
The controller is
Processing for confirming communication with the monitoring target device corresponding to the registered network address;
When communicating with the monitoring target device, based on the address conversion table of the first network device, the address port conversion table of the second network device and the port connection state information, the network addresses related to each other, Processing for creating the monitoring target device database in which the device unique address, the physical port, and the connection state are associated;
When not communicating with the monitoring target device, the device specific address of the address port conversion table of the second network device connected to the monitoring target device is compared with the device specific address of the monitoring target device database. To confirm whether or not the device-specific address of the address port conversion table has been changed,
When the device unique address of the address port translation table is changed, the device unique address of the address translation table of the first network device closest to the monitored device and the device unique of the monitored device database A process of checking whether the device unique address of the address conversion table is changed by comparing the address,
Processing for controlling to rewrite the device unique address of the address translation table to the device unique address of the monitoring target device in the first network device when the device unique address of the address translation table has not been changed; ,
I do,
Monitoring device. When the control unit does not communicate with the monitoring target device, the control unit further checks whether the connection state of the port connection state information of the second network device connected to the monitoring target device is connected. Including
The process of checking whether or not the device unique address of the address port conversion table has been changed is performed when the connection state of the port connection state information is connected.
The monitoring device according to claim 1. Furthermore, an output unit that outputs information to the outside and is controlled by the control unit,
The control unit further performs a process of controlling the output unit to output a message indicating that communication with the monitoring target device is not possible when the connection state of the port connection state information is not connected. ,
The monitoring device according to claim 2. The control unit further performs a process of confirming whether or not the monitoring target device database corresponding to the monitoring target device exists when not communicating with the monitoring target device,
The process of checking whether or not the device unique address of the address port conversion table has been changed is performed when the monitoring target device database corresponding to the monitoring target device exists.
The monitoring device according to claim 1. The monitoring device further includes an output unit that outputs information to the outside and is controlled by the control unit,
The control unit further performs a process of controlling the output unit to output a message indicating that communication with the monitoring target device is not possible when the monitoring target device database corresponding to the monitoring target device does not exist. Do,
The monitoring device according to claim 4. In the process of controlling the first network device to rewrite the device unique address of the address conversion table with the device unique address of the monitoring target device, the first network device corresponds to the network address of the monitoring target device database. By erasing the device unique address of the address translation table of the network device, the first network device is controlled to rewrite the device unique address of the address translation table with the device unique address of the monitoring target device. ,
The monitoring apparatus as described in any one of Claims 1 thru | or 5. The monitoring device further includes an output unit that outputs information to the outside and is controlled by the control unit,
If the device unique address of the address port translation table has not been changed, or if the device unique address of the address translation table has been changed, the control unit further causes another failure to the monitored device. A process of controlling to output a message to the effect from the output unit,
The monitoring device according to claim 1. A monitoring device according to any one of claims 1 to 7,
The monitored device;
The first network device;
The second network device;
Comprising
Communication failure automatic recovery system. A communication unit capable of communicating with the first network device and the second network device on the network and the monitoring target device;
A storage unit for storing a monitoring target device database including information on the monitoring target device;
A control unit for controlling the communication unit and the storage unit;
A communication failure recovery method for recovering a communication failure that has occurred in the monitoring target device using a monitoring device comprising:
The first network device stores an address conversion table;
The second network device stores an address port conversion table and port connection state information,
The monitored device stores a network address and a device specific address,
In the address conversion table, the network address and the device unique address are associated,
In the address port conversion table, the device unique address is associated with a physical port of the second network device to which the monitoring target device is connected,
The port connection status information is associated with the physical port of the second network device and the connection status of the monitoring target device with respect to the physical port,
In the communication failure recovery method,
Confirming communication with the monitoring target device corresponding to the registered network address;
When communicating with the monitoring target device, based on the address conversion table of the first network device, the address port conversion table of the second network device and the port connection state information, the network addresses related to each other, Creating the monitoring target device database in which the device unique address, the physical port, and the connection state are associated;
When not communicating with the monitoring target device, the device specific address of the address port conversion table of the second network device connected to the monitoring target device is compared with the device specific address of the monitoring target device database. The step of checking whether or not the device unique address of the address port conversion table has been changed,
When the device unique address of the address port translation table is changed, the device unique address of the address translation table of the first network device closest to the monitored device and the device unique of the monitored device database Checking whether the device specific address of the address conversion table has been changed by comparing the address,
Controlling the device unique address of the address translation table to be rewritten to the device unique address of the monitoring target device in the first network device when the device unique address of the address translation table has not been changed; ,
including,
Automatic communication failure recovery method. A communication unit capable of communicating with the first network device and the second network device on the network and the monitoring target device;
A storage unit for storing a monitoring target device database including information on the monitoring target device;
A control unit for controlling the communication unit and the storage unit;
A communication failure recovery program that recovers a communication failure that has occurred in the monitored device by being executed by a monitoring device comprising:
The first network device stores an address conversion table;
The second network device stores an address port conversion table and port connection state information,
The monitored device stores a network address and a device specific address,
In the address conversion table, the network address and the device unique address are associated,
In the address port conversion table, the device unique address is associated with a physical port of the second network device to which the monitoring target device is connected,
The port connection status information is associated with the physical port of the second network device and the connection status of the monitoring target device with respect to the physical port,
The communication failure recovery program is
Confirming communication with the monitoring target device corresponding to the registered network address;
When communicating with the monitoring target device, based on the address conversion table of the first network device, the address port conversion table of the second network device and the port connection state information, the network addresses related to each other, Creating the monitoring target device database in which the device unique address, the physical port, and the connection state are associated;
When not communicating with the monitoring target device, the device specific address of the address port conversion table of the second network device connected to the monitoring target device is compared with the device specific address of the monitoring target device database. Confirming whether or not the device-specific address of the address port conversion table is changed,
When the device unique address of the address port translation table is changed, the device unique address of the address translation table of the first network device closest to the monitored device and the device unique of the monitored device database Checking whether the device unique address of the address translation table has been changed by comparing the address,
Controlling to rewrite the device unique address of the address translation table to the device unique address of the monitoring target device in the first network device when the device unique address of the address translation table has not been changed; ,
To execute,
Communication failure automatic recovery program.

Images