JP6955937B2 - Management equipment and network system - Google Patents

Description

The present invention relates to a management device and a network system, for example, a technique for identifying a physical connection destination of an abnormal terminal.

For example, Patent Document 1 discloses a failure detection / recovery system capable of monitoring the operating status of a PoE (Power over Ethernet (registered trademark)) power receiving terminal and flexibly executing recovery measures in the event of an abnormality. The system includes a management procedure storage unit that holds procedure information for determining the normality of a PoE power receiving terminal, a port connection information storage unit that holds connection information between a PoE power receiving terminal and a PoE power supply device, and a PoE power supply device. The system includes a power supply stop time storage unit that holds information on the stop time when power supply to the PoE power receiving terminal is stopped.

Japanese Unexamined Patent Publication No. 2011-188072

Usually, in the network system, in order to construct a communication path between various terminals, a switch device that performs processing of layer 2 (L2) of the OSI reference model and layer 3 (L3) in addition to L2 is installed. In addition, a monitoring device for detecting abnormalities of various terminals may be installed in the network system. Such a monitoring device often identifies an abnormal terminal by an IP (Internet Protocol) address.

However, in order to specify the physical connection destination (that is, which port of which switch device is connected) of the abnormal terminal for which the IP address is set, for example, the port connection information storage unit of Patent Document 1 is used. It is necessary to refer to the management information registered in advance by the user. As a result, network management may be complicated. Specifically, for example, as the number of terminals increases, the workload associated with the registration of management information may increase, or it may be necessary to update the management information each time the connection destination of the terminals is changed.

The present invention has been made in view of the above, and one of the objects thereof is to provide a management device and a network system capable of facilitating network management.

The above and other objects and novel features of the present invention will become apparent from the description and accompanying drawings herein.

A brief description of typical embodiments of the inventions disclosed in the present application is as follows.

The management device according to the present embodiment is configured by program processing using a computer, and has a registration information storage unit, a MAC address acquisition unit, and a port information acquisition unit. In the registration information storage unit, the IP address of the core device having the ARP table and the IP address of the switch device that relays the frame from the terminal connected to the port based on the FDB are registered. When the IP address of the abnormal terminal is notified, the MAC address acquisition unit acquires the MAC address corresponding to the IP address of the abnormal terminal from the ARP table of the core device registered in the registration information storage unit. The port information acquisition unit acquires the identifier of the port corresponding to the MAC address acquired by the MAC address acquisition unit from the FDB of the switch device registered in the registration information storage unit.

Briefly explaining the effects obtained by the typical embodiments of the inventions disclosed in the present application makes it possible to facilitate network management.

It is the schematic which shows the structural example of the main part of the network system by Embodiment 1 of this invention. It is a figure which shows an example of the holding contents of the ARP table provided in the core apparatus of FIG. It is a figure which shows an example of the holding contents of FDB provided in the switch device of FIG. It is the schematic which shows the main operation example of the network system of FIG. It is the schematic which shows the modification of the network system of FIG. It is the schematic which shows the structural example of the switch apparatus included in the network system by Embodiment 2 of this invention. It is the schematic which shows the structural example of the management apparatus included in the network system by Embodiment 2 of this invention. It is the schematic which shows the operation example of the power supply command transmission part in FIG. 7. It is a flow chart which shows an example of the processing content of the MAC address acquisition part in FIG. 7. It is a flow chart which shows an example of the processing content of the port information acquisition part in FIG. 7. It is a figure which shows an example of the management information used in the network system which becomes the comparative example of this invention.

In the following embodiments, when necessary for convenience, the description will be divided into a plurality of sections or embodiments, but unless otherwise specified, they are not unrelated to each other, and one is the other. There is a relationship of some or all modifications, details, supplementary explanations, etc. In addition, in the following embodiments, when the number of elements (including the number, numerical value, quantity, range, etc.) is referred to, when it is specified in particular, or when it is clearly limited to a specific number in principle, etc. Except, the number is not limited to the specific number, and may be more than or less than the specific number.

Furthermore, in the following embodiments, the components (including element steps, etc.) are not necessarily essential unless otherwise specified or clearly considered to be essential in principle. Needless to say. Similarly, in the following embodiments, when referring to the shape, positional relationship, etc. of a component or the like, the shape is substantially the same unless otherwise specified or when it is considered that it is not apparent in principle. Etc., etc. shall be included. This also applies to the above numerical values and ranges.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In addition, in all the drawings for explaining the embodiment, in principle, the same members are designated by the same reference numerals, and the repeated description thereof will be omitted.

(Embodiment 1)
<< Outline of network system >>
FIG. 1 is a schematic view showing a configuration example of a main part of a network system according to the first embodiment of the present invention. The network system shown in FIG. 1 includes a plurality of switch devices SW [1] to SW [m], a management device 12, a monitoring device 13, and a core device CSW connected to these devices. The core device CSW is, for example, an L3 switch that performs layer 3 (L3) processing in addition to layer 2 (L2) processing of the OSI reference model, and includes an ARP (Address Resolution Protocol) table 20. The core device CSW is also called a gateway device that mediates between the L2 segment and the L3 segment, and is also connected to a predetermined L3 network 11.

The switch devices SW [1] to SW [m] are, for example, L2 switches that perform L2 processing. Each of the switch devices SW [1] to SW [m] includes a plurality of lower link ports Pd [1] to Pd [n], an upper link port Pu, an FDB (Forwarding DataBase) 31, and a device management unit. 30 and. In this example, terminals 14a and 14b are connected to the lower link ports Pd [1] and Pd [n] of the switch device SW [1] via an Ethernet (registered trademark) cable 15, respectively, and the switch device SW [1] is connected to the terminals 14a and 14b. Terminals 14c and 14d are connected to the lower link ports Pd [1] and Pd [n] of [m], respectively, via the Ethernet cable 15. Further, both the upper link port Pu of the switch devices SW [1] and SW [m] are connected to the core device CSW.

IP addresses IPA1, IPA2, IPA3, IPA4 and MAC (Media Access Control) addresses MA1, MA2, MA3, MA4 are set in the terminals 14a, 14b, 14c, and 14d, respectively. The terminals 14a and 14b and the terminals 14c and 14d may belong to different L2 segments, but in this example, they belong to the same L2 segment. FIG. 2 is a diagram showing an example of the holding contents of the ARP table included in the core device of FIG. 1, and FIG. 3 is a diagram showing an example of the holding contents of the FDB included in the switch device of FIG.

As shown in FIG. 2, the ARP table 20 of the core device CSW holds the correspondence between the IP addresses IPA1, IPA2, IPA3, and IPA4 and the MAC addresses MA1, MA2, MA3, and MA4, respectively. FIG. 3 shows the holding contents of the FDB 31 of the switch device SW [1]. The FDB 31 maintains a correspondence between a port (port identifier (ID)) and a MAC address, and for example, MAC addresses MA1 and MA2 correspond to port IDs {Pd [1]} and {Pd [n]}, respectively. Attach and hold. {Pd [1]} represents the identifier (ID) of the lower link port Pd [1], and similarly, in the specification, {AA} represents the ID of “AA”. Further, the FDB 31 in FIG. 3 holds the MAC addresses MA3 and MA4 in association with the port ID {Pu}.

Returning to FIG. 1, each of the switch devices SW [1] to SW [m] relays the frame from the terminal connected to the port based on the FDB 31 as shown in FIG. The device management unit 30 manages the switch device based on, for example, SNMP (Simple Network Management Protocol) or the like. Specifically, the device management unit 30 is responsible for controlling, for example, when making various settings for the switch device from outside the device, and when transmitting various states and various internal information of the switch device to the outside of the device.

The monitoring device 13 is composed of, for example, program processing using a computer (server, PC (Personal Computer), etc.) and, in some cases, dedicated hardware, and checks for the presence or absence of abnormalities in terminals 14a, 14b, 14c, and 14d. It monitors and notifies the management device 12 of the IP address of the abnormal terminal when an abnormality is detected. At this time, the monitoring device 13 notifies the IP address of the abnormal terminal by using, for example, the POST method of HTTP (Hypertext Transfer Protocol). The management device 12 is configured by, for example, program processing using a computer, and the details will be described later. However, when the monitoring device 13 notifies the IP address of the abnormal terminal, the physical connection destination of the abnormal terminal is specified. do.

<< Outline operation of network system >>
FIG. 4 is a schematic view showing a main operation example of the network system of FIG. In FIG. 4, the monitoring device 13 detects an abnormality in a predetermined terminal (here, the terminal 14a in which the IP address IPA1 is set) (step S101). In response to this, the monitoring device 13 notifies the management device 12 of the IP address (IPA1) of the abnormal terminal (step S102). When the IP address (IPA1) of the abnormal terminal is notified, the management device 12 performs a search process for the core device CSW in which the IP address is registered in advance. Then, the management device 12 acquires the MAC address (MA1) corresponding to the IP address (IPA1) of the abnormal terminal from the ARP table 20 of the core device CSW (step S103).

Specifically, the management device 12 issues an instruction to the core device CSW to search for a MAC address corresponding to the IP address (IPA1) based on, for example, SNMP, and the result (MAC address (MAC address (MAC address)). MA1)) may be received from the core device CSW. Alternatively, the management device 12 may copy the holding information of the ARP table 20 of the core device CSW to itself based on SNMP or the like, and then search from the copy information by itself.

After step S103, the management device 12 performs a search process for the switch devices (here, a plurality of switch devices SW [1] to SW [m]) in which the IP address is registered in advance (step S104). Then, the management device 12 is an identifier of the switch device (here, {SW [1]) corresponding to the MAC address (MA1) acquired in step S103 from the FDB 31 of the switch device (SW [1] to SW [m]). ]}) And the port identifier (here {Pd [1]}) are acquired (step S105). The specific search method at this time is the same as that of the ARP table 20 described above. Further, the identifier of the switch device ({SW [1]}) is, for example, the IP address of the switch device itself.

In this way, the mechanism for specifying the connection destination (lower link port Pd [1] of the switch device SW [1]) of the terminal (14a) having a predetermined IP address (IPA1 in this case) can be used in various situations. It can be utilized. For example, in a network system based on the PoE standard, the port to which the hung terminal is connected can be immediately identified, so that the port can be repowered (that is, the abnormal terminal is restarted) at an early stage. Alternatively, since the port to which the virus-infected terminal is connected can be immediately identified in the immune network system, it is possible to issue an instruction to block communication to the port at an early stage. Alternatively, in the wireless network system, the position of the owner of the wireless terminal having a predetermined IP address can be grasped based on the identifier of the switch device (that is, the installation location thereof) that is the search result.

The management device 12 may belong to any segment as long as it can communicate with the monitoring device 13 and the switch devices SW [1] to SW [m] based on the IP address. The monitoring device 13 may also belong to any segment as long as it can communicate with the management device 12 and the terminals 14a, 14b, 14c, and 14d based on the IP address. Further, the core device CSW registered in advance in the stage prior to step S103 in FIG. 4 may be any device provided with the ARP table 20 for the terminals 14a, 14b, 14c, 14d, and is arbitrarily determined according to the network configuration.

For example, the management device 12 and the monitoring device 13 may be installed in the same L2 segment as the terminals 14a, 14b, 14c, 14d. In this case, communication between the monitoring device 13 and the terminals 14a, 14b, 14c, 14d (for example, packet communication for monitoring with the IP address as the destination) can be performed by using the processing of L2. Then, in this case, since the monitoring device 13 includes the desired ARP table 20, the user may register the IP address of the monitoring device 13 as the core device CSW.

Further, in the example of FIG. 1, the management device 12 and the monitoring device 13 are configured by different devices, but may be commonly configured by one device (for example, a computer). FIG. 5 is a schematic view showing a modified example of the network system of FIG. The network system shown in FIG. 5 includes a management / monitoring device 16 instead of the management device 12 and the monitoring device 13 shown in FIG. The management / monitoring device 16 includes a management unit 12a that realizes the function of the management device 12 of FIG. 1 by program processing, and a monitoring unit 13a that realizes the function of the monitoring device 13 of FIG. 1 by program processing.

<< Main effect of Embodiment 1 >>
FIG. 11 is a diagram showing an example of management information used in a network system as a comparative example of the present invention. In the network system as a comparative example, in order to specify the connection destination of the terminal having a predetermined IP address, the user needs to create the management information 55 as shown in FIG. 11 in advance. The management information 55 in FIG. 11 holds a correspondence relationship between the IP address of the terminal and the switch device and the port to which the terminal is connected. The management device or the user identifies the connection destination of the terminal (for example, an abnormal terminal) having a predetermined IP address by referring to the management information 55.

However, in such a method, the workload associated with the registration of the management information 55 increases as the number of terminals increases. In addition, it becomes necessary to update the management information 55 every time the connection destination of the terminal is changed. As a result, network management may be complicated. On the other hand, when the method of the first embodiment is used, the user only needs to register the IP address of the core device CSW and the IP addresses of the switch devices SW [1] to SW [m] in advance, and connects each terminal. There is no need to register the destination individually. Further, unlike the case of a terminal, the information of the core device and the switch device, once registered, usually does not need to be changed unless the basic configuration of the network is changed. As a result, the workload associated with registration can be reduced as compared with the case where the management information 55 is used, and network management can be facilitated.

Here, the case where one core device CSW is provided is taken as an example, but a plurality of core devices CSW may be provided. That is, a plurality of combinations of the core device and the switch device as shown in FIG. 1 may be provided. In such a case, the user may register in advance the IP addresses of the plurality of core devices and the IP addresses of the switch devices under the control. As a result, in step S103 of FIG. 4, a search is performed on the plurality of core devices, and in step S104, for example, a search is performed on each switch device under the control of the core device that hits the search. ..

(Embodiment 2)
In the second embodiment, the details will be described by taking as an example the case where the network system shown in FIG. 1 is a network system based on the PoE standard. The PoE standard is defined by IEEE802.3af and IEEE802.3at, and defines a power supply system using an Ethernet cable. In this case, the switch devices SW [1] to SW [m] in FIG. 1 are power supply devices corresponding to the PoE standard, and the terminals 14a, 14b, 14c, and 14d are power receiving terminals corresponding to the PoE standard. The power receiving terminal is typically a surveillance camera, a wireless LAN access point, or the like.

<< Details of switch device >>
FIG. 6 is a schematic view showing a configuration example of a switch device included in the network system according to the second embodiment of the present invention. The switch device SW shown in FIG. 6 includes a plurality of lower link ports Pd [1] to Pd [n], an upper link port Pu, a device management unit 30, an interface unit 32, a frame relay unit 33, and the like. A power supply control unit 34 is provided. The lower link ports Pd [1] to Pd [n] transmit or receive frames with and from the lower link terminal (power receiving terminal), respectively. The upper link port Pu transmits or receives frames to and from the L3 switch or the like that is the upper link. The port may be called an interface in the sense of a logical port based on a tag VLAN (Virtual Local Area Network) or the like.

The interface unit 32 mediates the transfer of frames between the plurality of ports (Pd [1] to Pd [n], Pu) and the frame relay unit 33. Further, the interface unit 32 includes a power feeding unit 35. Based on the PoE standard, the power supply unit 35 selectively supplies power to each terminal connected to the lower link ports Pd [1] to Pd [n] via the corresponding port and the Ethernet cable 15.

The frame relay unit 33 includes an FDB 31 as shown in FIG. 3, and relays frames between ports based on the FDB 31. Specifically, when the frame relay unit 33 receives the frame via the port and the interface unit 32, the frame relay unit 33 learns from the FDB 31 by associating the source MAC address of the frame with the reception port ID of the frame. Further, the frame relay unit 33 determines the destination port of the frame by searching the FDB 31 using the destination MAC address of the frame as a search key, and transmits the frame to the interface unit 32 together with the destination port ID. The interface unit 32 relays the frame from the frame relay unit 33 to the port represented by the destination port ID.

The device management unit 30 manages the entire device based on, for example, SNMP. The power supply control unit 34 includes a power supply command receiving unit 36 that receives a power supply command, and controls whether or not power is supplied to each port by the power supply unit 35 based on the power supply command. Here, the device management unit 30 can transfer, for example, a power supply command from the outside to the power supply command receiving unit 36. As a result, the power supply control unit 34 can control whether or not power is supplied to each port based on a power supply command from the outside.

In FIG. 6, the interface unit 32 and the frame relay unit 33 are, for example, ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), CAM (Content Addressable Memory), RAM (Random Access Memory), and ROM (Read Only). It is implemented by hardware that appropriately combines Memory) and the like. The device management unit 30 and the power supply control unit 34 are implemented by, for example, program processing by a CPU (Central Processing Unit). However, the specific mounting form of each part is, of course, not limited to this, and may be appropriately mounted using hardware, software, or a combination thereof.

<< Details of management device >>
FIG. 7 is a schematic view showing a configuration example of a management device included in the network system according to the second embodiment of the present invention. The management device 12 shown in FIG. 7 includes an abnormality notification receiving unit 41, a MAC address acquisition unit 42, a port information acquisition unit 43, a power supply command transmission unit 44, an ARP table information acquisition unit 45, and an FDB information acquisition unit 46. And a registration information storage unit 47 and a copy information storage unit 48. In addition to these, the management device 12 also has, for example, a function of an SNMP manager, although not shown.

As described in the first embodiment, the registration information storage unit 47 has in advance the ID (specifically, the IP address) of the core device CSW provided with the ARP table 20 and the ID (specifically, the IP address) of the switch device SW. IP address) is registered as network configuration registration information 50. At this time, in the example of FIG. 7, information to the effect that the switch devices SW [1] to SW [m] belong under the core device CSW is also registered, taking the network configuration of FIG. 1 as an example. In other words, information that the ARP table 20 for each terminal connected to the switch devices SW [1] to SW [m] exists in the core device CSW is registered.

The abnormality notification receiving unit 41 receives an abnormality notification including the IP address of the abnormal terminal from the outside (that is, the monitoring device 13 in FIG. 1). At this time, the monitoring device 13 typically communicates with each terminal by using an ICMP (Internet Control Message Protocol) packet (for example, ping) to periodically communicate with the abnormal terminal (that is, a hung terminal). Detects the presence or absence. When the error notification receiving unit 41 notifies the IP address of the abnormal terminal, the MAC address acquisition unit 42 communicates with the core device CSW using the IP address of the core device CSW registered in the registration information storage unit 47. , Acquires the MAC address corresponding to the IP address of the abnormal terminal from the ARP table 20 of the core device CSW.

The port information acquisition unit 43 communicates with each switch device using the IP addresses of the switch devices SW [1] to SW [m] registered in the registration information storage unit 47, and MACs from the FDB of each switch device. The port identifier (and the switch device identifier) corresponding to the MAC address acquired by the address acquisition unit 42 is acquired. At this time, the port information acquisition unit 43 excludes the identifier of the excluded port registered in the registration information storage unit 47 from the identifier of the acquired port.

That is, for example, the MAC addresses MA3 and MA4 of the terminals 14c and 14d in FIG. 1 are held in association with the port IDs {Pd [1]} and {Pd [n]} in the FDB 31 of the switch device SW [m], respectively. Will be done. In addition to this, as shown in FIG. 3, the MAC addresses MA3 and MA4 may be held in association with the port ID {Pu} in the FDB 31 of the switch device SW [1]. The ID of such an upper link port Pu is unnecessary for identifying the physical connection destination of the abnormal terminal. Therefore, the user registers the ID of such an upper link port Pu in the registration information storage unit 47 in advance as the exclusion port ID information 53.

The power supply command transmission unit 44 generates a power supply command instructing repower supply of the port acquired by the port information acquisition unit 43, and transmits the power supply command to the target switch device. FIG. 8 is a schematic view showing an operation example of the power supply command transmission unit in FIG. 7. For example, after step S105 shown in FIG. 4, the power supply command transmission unit 44 generates a power supply command instructing repower supply of the lower link port Pd [1] as shown in step S106 of FIG. It is transmitted to the switch device SW [1]. The switch device SW [1] receives the power supply command at the power supply command receiving unit 36, and repowers the lower link port Pd [1].

Here, when instructing re-power supply, the power supply command transmission unit 44 first transmits a power supply command for stopping power supply, and then transmits a power supply command for starting power supply after a lapse of a certain period of time. By such re-power supply, the hang-up of the terminal 14a is often eliminated by restarting the terminal 14a connected to the lower link port Pd [1] of the switch device SW [1].

Returning to FIG. 7, the ARP table information acquisition unit 45 periodically acquires the holding information of the ARP table 20 from the core device CSW registered in the registration information storage unit 47, and the copy information storage unit 48 is used as the ARP table information 51. Save to. Similarly, the FDB information acquisition unit 46 periodically acquires the holding information of the FDB 31 from each of the switch devices SW [1] to SW [m] registered in the registration information storage unit 47, and copies the information as the FDB information 52. It is stored in the storage unit 48. In this case, the MAC address acquisition unit 42 can acquire a desired MAC address from the ARP table information 51 of the copy information storage unit 48. Similarly, the port information acquisition unit 43 can acquire a desired port ID from the FDB information 52 of the copy information storage unit 48.

In FIG. 7, the registration information storage unit 47 and the copy information storage unit 48 are composed of, for example, a RAM, a ROM, an HDD (Hard Disk Drive), or the like provided in the computer. The other parts are configured by, for example, program processing using a CPU included in the computer.

FIG. 9 is a flow chart showing an example of the processing content of the MAC address acquisition unit in FIG. 7. In FIG. 9, the MAC address acquisition unit 42 receives the IP address of the abnormal terminal (step S201). Next, the MAC address acquisition unit 42 acquires the ID (IP address) of the core device CSW to be searched from the network configuration registration information 50 (step S202). Subsequently, the MAC address acquisition unit 42 acquires the MAC address corresponding to the IP address by searching the ARP table 20 of the core device CSW to be searched using the IP address of the abnormal terminal as the search key (step S203). ).

Next, the MAC address acquisition unit 42 determines whether or not the MAC address has been acquired (step S204). When the MAC address cannot be acquired, the MAC address acquisition unit 42 acquires the MAC address corresponding to the IP address by searching the ARP table information 51 of the copy information storage unit 48 using the IP address of the abnormal terminal as a search key. (Step S205). On the other hand, if the MAC address acquisition unit 42 can acquire the MAC address in step S204, the process ends.

FIG. 10 is a flow chart showing an example of the processing content of the port information acquisition unit in FIG. 7. In FIG. 10, the port information acquisition unit 43 receives the MAC address of the abnormal terminal (step S301). Next, the port information acquisition unit 43 acquires the ID (IP address) of the switch device SW to be searched from the network configuration registration information 50 (step S302). Subsequently, the port information acquisition unit 43 acquires the port ID (and switch device ID) corresponding to the MAC address of the abnormal terminal by searching the FDB 31 of the switch device SW to be searched using the MAC address of the abnormal terminal as the search key. (Step S303). At this time, as described above, the exclusion port registered in the network configuration registration information 50 is excluded.

Next, the port information acquisition unit 43 determines whether or not the port ID (and the switch device ID) can be acquired (step S304). When the port ID (and the switch device ID) cannot be acquired, the port information acquisition unit 43 corresponds to the MAC address by searching the FDB information 52 of the copy information storage unit 48 using the MAC address of the abnormal terminal as a search key. Acquire the port ID (and switch device ID) (step S305). At this time, as described above, the exclusion port registered in the network configuration registration information 50 is excluded. On the other hand, when the port information acquisition unit 43 can acquire the port ID (and the switch device ID) in step S304, the port information acquisition unit 43 ends the process.

Here, in a situation where an abnormal terminal is detected, for example, since communication from the abnormal terminal to the switch device SW does not occur, there is a possibility that the holding information of the FDB 31 is lost due to aging in step S303. Further, in a situation where an abnormal terminal is detected, there is a possibility that an abnormality has occurred in the switch device SW instead of the terminal in some cases. In such a case, after the abnormal terminal is detected, there is a possibility that desired information cannot be acquired from the FDB 31 of the target switch device SW. Therefore, in order to deal with such a situation, it is beneficial to provide the FDB information acquisition unit 46 and have the port information acquisition unit 43 perform the processing as shown in FIG.

Similarly, with respect to the ARP table 20, it is useful to provide the ARP table information acquisition unit 45 in preparation for an unforeseen situation and have the MAC address acquisition unit 42 perform the processing as shown in FIG.

Further, in the examples of FIGS. 9 and 10, the MAC address acquisition unit 42 and the port information acquisition unit 43 once searched for the target core device CSW and switch device SW after the abnormal terminal was detected. Instead, it can be configured to always search for each piece of information in the copy information storage unit 48. However, in this case, each information may not be the latest depending on the update frequency of the ARP table information acquisition unit 45 and the FDB information acquisition unit 46, and if the update frequency is increased, the processing load of each device and the processing load of each device may increase. An increase in network communication load can occur. Therefore, it is useful to set the update frequency of the ARP table information acquisition unit 45 and the FDB information acquisition unit 46 to a certain degree, and then apply the processes shown in FIGS. 9 and 10.

<< Main effect of Embodiment 2 >>
As described above, by using the method of the second embodiment, it becomes possible to realize the facilitation of network management in the network system based on the PoE standard. Specifically, as in the case of the first embodiment, in addition to being able to reduce the workload associated with the registration of the management information 55, it is possible to automatically recover the abnormal terminal by automatically re-powering the abnormal terminal. Become.

Further, the management device 12 of FIG. 7 can be flexibly applied to various network systems based on the PoE standard. That is, the monitoring device 13 shown in FIG. 1 also functions as, for example, a recording device that acquires and records an image from each terminal (for example, a surveillance camera), and is one device having both the recording function and the monitoring function. In many cases. In such a case, add the management device 12 as shown in FIG. 7 to the network system, or add software for realizing the management device 12 of FIG. 7 to the monitoring device 13 or another existing device (server or PC). By incorporating it, it will be possible to automatically recover abnormal terminals for various network systems.

Although the invention made by the present inventor has been specifically described above based on the embodiment, the present invention is not limited to the embodiment and can be variously modified without departing from the gist thereof. For example, the above-described embodiments have been described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the described configurations. Further, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. .. Further, it is possible to add / delete / replace other configurations with respect to a part of the configurations of each embodiment.

11 L3 network 12 Management device 12a Management unit 13 Monitoring device 13a Monitoring unit 14a to 14d Terminal 15 Ethernet cable 16 Management / monitoring device 20 ARP table 30 Device management unit 31 FDB
32 Interface unit 33 Frame relay unit 34 Power supply control unit 35 Power supply unit 36 Power supply command reception unit 41 Abnormality notification reception unit 42 MAC address acquisition unit 43 Port information acquisition unit 44 Power supply command transmission unit 45 ARP table information acquisition unit 46 FDB information acquisition unit 47 Registration information storage unit 48 Copy information storage unit 50 Network configuration registration information 51 ARP table information 52 FDB information 53 Exclusion port ID information 55 Management information CSW core device Pd [1] to Pd [n] Lower link port Pu Upper link Port SW, SW [1] to SW [m] Switch device

Claims (11)

It is a management device composed of program processing using a computer.
A registration information storage unit in which the IP address of the core device having an ARP (Address Resolution Protocol) table and the IP address of the switch device that relays frames from terminals connected to the port based on FDB (Forwarding DataBase) are registered. ,
When the IP address of the abnormal terminal is notified, the MAC address acquisition unit that acquires the MAC address corresponding to the IP address of the abnormal terminal from the ARP table of the core device registered in the registration information storage unit. ,
A port information acquisition unit that acquires an identifier of the port corresponding to the MAC address acquired by the MAC address acquisition unit from the FDB of the switch device registered in the registration information storage unit.
Have a,
The identifier of the exclusion port is registered in advance in the registration information storage unit.
The port information acquisition unit excludes the identifier of the exclusion port registered in the registration information storage unit from the acquired identifier of the port.
Management device. In the management device according to claim 1,
The switch device is a device compatible with the PoE (Power over Ethernet) standard.
The management device includes a power supply command transmission unit that generates a power supply command instructing repower supply of the port acquired by the port information acquisition unit and transmits the power supply command to the switch device.
Management device. In the management device according to claim 1 or 2.
The management device has an ARP table information acquisition unit that periodically acquires the holding information of the ARP table from the core device registered in the registration information storage unit and stores it in the copy information storage unit.
The MAC address acquisition unit acquires the MAC address from the copy information storage unit.
Management device. In the management device according to claim 1 or 2.
The management device has an FDB information acquisition unit that periodically acquires the holding information of the FDB from the switch device registered in the registration information storage unit and stores it in the copy information storage unit.
The port information acquisition unit acquires the identifier of the port from the copy information storage unit.
Management device. In the management device according to claim 1 or 2.
The IP addresses of a plurality of the switch devices are registered in the registration information storage unit, and the IP addresses are registered.
The port information acquisition unit searches for the identifier of the port corresponding to the MAC address for the FDBs of the plurality of switch devices, and as the search result, the identifier of the switch device and the identifier of the port To get,
Management device. A switch device that relays frames from terminals connected to the port based on FDB (Forwarding DataBase),
A management device composed of program processing using a computer,
A monitoring device that monitors the presence or absence of an abnormality in the terminal and notifies the management device of the IP address of the abnormal terminal when an abnormality is detected.
It is a network system equipped with
The management device is
A registration information storage unit in which the IP address of the core device having an ARP (Address Resolution Protocol) table and the IP address of the switch device are registered.
When the IP address of the abnormal terminal is notified, the MAC address acquisition that acquires the MAC address corresponding to the IP address of the abnormal terminal from the ARP table of the core device registered in the registration information storage unit. Department and
A port information acquisition unit that acquires an identifier of the port corresponding to the MAC address acquired by the MAC address acquisition unit from the FDB of the switch device registered in the registration information storage unit.
Have a,
The identifier of the exclusion port is registered in advance in the registration information storage unit.
The port information acquisition unit excludes the identifier of the exclusion port registered in the registration information storage unit from the acquired identifier of the port.
Network system. In the network system according to claim 6,
The switch device is a device compatible with the PoE (Power over Ethernet) standard, and has a power supply control unit that controls whether or not power is supplied to the port based on an external power supply command.
The management device includes a power supply command transmission unit that generates the power supply command that instructs the repower supply of the port acquired by the port information acquisition unit and transmits the power supply command to the switch device.
Network system. In the network system according to claim 6 or 7.
The management device has an ARP table information acquisition unit that periodically acquires the holding information of the ARP table from the core device registered in the registration information storage unit and stores it in the copy information storage unit.
The MAC address acquisition unit acquires the MAC address from the copy information storage unit.
Network system. In the network system according to claim 6 or 7.
The management device has an FDB information acquisition unit that periodically acquires the holding information of the FDB from the switch device registered in the registration information storage unit and stores it in the copy information storage unit.
The port information acquisition unit acquires the identifier of the port from the copy information storage unit.
Network system. In the network system according to claim 6 or 7.
The IP addresses of a plurality of the switch devices are registered in the registration information storage unit, and the IP addresses are registered.
The port information acquisition unit searches for the identifier of the port corresponding to the MAC address for the FDBs of the plurality of switch devices, and as the search result, the identifier of the switch device and the identifier of the port To get,
Network system. In the network system according to claim 6 or 7.
The management device and the monitoring device are composed of one common device.
Network system.

Images