JP6798605B2 - Monitoring processing program, monitoring processing method and monitoring device - Google Patents

Description

The present invention relates to a monitoring processing program, a monitoring processing method, and a monitoring device.

As an example, some products having a network monitoring function use a map in which the connection shape between devices included in the network to be monitored is schematicized to notify the occurrence of a failure. For example, among the port of the device displayed on the map, the failure notification is realized by distinguishing the display form between the port where the failure such as link down has occurred and the port where the link down has not occurred. Will be done.

Japanese Unexamined Patent Publication No. 2003-209683 Japanese Unexamined Patent Publication No. 2009-199387 Japanese Unexamined Patent Publication No. 2010-212762

However, in the above technique, notification of a port that is in a link-down state due to a different cause is uniformly performed. That is, if the port to which the link down status is notified includes a port that has fallen into the link down status due to a setting error or the like, the link down status is due to not being connected to another port. Ports that are marked with are also included. For this reason, the notification of the failure occurrence regarding the port that was linked up is confused with the notification of the failure occurrence regarding the port that is not intended to function as a link.

In one aspect, it is an object of the present invention to provide a monitoring processing program, a monitoring processing method, and a monitoring device capable of suppressing complicated notification of failure occurrence.

In one aspect, in a monitoring processing program executed by a monitoring device that notifies a monitoring device of a failure occurrence regarding a port of a device included in the monitored network, a link is made based on information collected from each device included in the monitored network. The port of the device in which the down occurs is identified, and based on the information collected from each device included in the monitored network, it is determined whether or not the identified port is connected to the port of another device. When it is determined that the port is connected, the notification of the occurrence of a failure is given to the specified port, and when it is not determined that the port is connected, the notification of the occurrence of a failure is not given to the specified port. And.

It is possible to prevent the notification of the occurrence of a failure from becoming complicated.

FIG. 1 is a diagram showing a configuration example of the network management system according to the first embodiment. FIG. 2 is a block diagram showing a functional configuration of the network management device according to the first embodiment. FIG. 3 is a diagram showing an example of a topology map. FIG. 4 is a diagram showing an example of a topology map. FIG. 5 is a flowchart showing the procedure of the monitoring process according to the first embodiment. FIG. 6 is a diagram showing a hardware configuration example of a computer that executes the monitoring processing program according to the first and second embodiments.

The monitoring processing program, monitoring processing method, and monitoring device according to the present application will be described below with reference to the accompanying drawings. It should be noted that this embodiment does not limit the disclosed technology. Then, each embodiment can be appropriately combined as long as the processing contents do not contradict each other.

[System configuration]
FIG. 1 is a diagram showing a configuration example of the network management system according to the first embodiment. The network management system 1 shown in FIG. 1 provides a network management service that realizes various network settings for network devices 30A to 30C that construct a network NW of a monitored system 3 such as a corporate system via a GUI (Graphical User Interface). It is to provide. As a part of this network management service, the network management system 1 realizes a monitoring process that suppresses complicated notification of failure occurrence on a topology map in which the connection shape between devices included in the network NW is schematicized. ..

As shown in FIG. 1, the network management system 1 includes a network management device 10, network devices 30A to 30C, and a client terminal 50. In the following, when the network devices 30A to 30C are generically referred to, they may be referred to as "network device 30". Note that FIG. 1 illustrates the case where the three network devices 30A to 30C are housed in the monitored system 3, but this is just an example, and the monitored system 3 accommodates an arbitrary number of network devices. It goes without saying that you can do it.

The network management device 10 is a computer that provides the above network management service. The network management device 10 is an example of a monitoring device.

As one embodiment, the network management device 10 can be implemented as an SDN (Software-Defined Networking) controller by installing package software or online software that realizes the above network management service on a desired computer. As an example of the network NW, the network management device 10 can perform management including monitoring, setting, and control of carrier Ethernet such as IP-VPN (Internet Protocol Virtual Private Network) and wide area Ethernet (registered trademark). .. The network NW managed by the network management device 10 in this way is not limited to the physical network, and may be a virtual network virtualized by a technique such as SDN or NFV (Network Function Virtualization).

The network device 30 is a communication device for constructing the network NW of the monitored system 3. As an example, a data transfer device such as a router or a switch, a firewall, a load balancer, or the like can be adopted as the network device 30. The network device 30 is an example of the device.

The client terminal 50 is a computer that receives the above network management service. As an example, the client terminal 50 is used by a person concerned such as a network administrator who manages a network NW. Here, by providing the above network management service, the client terminal 50 does not necessarily have to have a telnet operating environment. For example, as the client terminal 50, any computer having a general-purpose browser operating environment can be adopted.

[Configuration of network management device 10]
FIG. 2 is a block diagram showing a functional configuration of the network management device 10 according to the first embodiment. As shown in FIG. 2, the network management device 10 includes a communication I / F (interface) unit 11, a storage unit 13, and a control unit 15. In addition to the functional units shown in FIG. 2, the network management device 10 may have various functional units of a known computer, for example, various functional units such as various input devices and audio output devices.

The communication I / F unit 11 is an interface that controls communication with another device, for example, a network device 30 or a client terminal 50.

As one embodiment, the communication I / F unit 11 can adopt a network interface card such as a LAN (Local Area Network) card. For example, the communication I / F unit 11 transmits various commands to the network device 30, and receives all or a part of the Config information and the MIB (Management Information Base) stored in the network device 30 from the network device 30. Or Further, the communication I / F unit 11 accepts an editing operation for the setting of the network device 30 from the client terminal 50, and transmits a topology map screen or the like in which the connection shape of the network NW is schematicized to the client terminal 50. ..

The storage unit 13 is a storage device that stores data used in various programs such as an OS (Operating System) executed by the control unit 15 and a network management program that realizes the above network management service.

As one embodiment, the storage unit 13 can be implemented as an auxiliary storage device in the network management device 10. For example, an HDD (Hard Disk Drive), an optical disk, an SSD (Solid State Drive), or the like can be adopted as the storage unit 13. The storage unit 13 does not necessarily have to be mounted as an auxiliary storage device, and may be mounted as a main storage device in the network management device 10. In this case, various semiconductor memory elements such as RAM (Random Access Memory) and flash memory can be adopted for the storage unit 13.

The storage unit 13 stores the topology information 13a and the filter information 13b as an example of the data used in the program executed by the control unit 15. In addition to the topology information 13a and the filter information 13b, other electronic data can also be stored together. For example, in order to manage the authority of a user such as a network administrator, the storage unit 13 also contains user authority information in which a group of network devices 30 or network devices 30 that permit setting operations and browsing for each user is defined. Can be remembered.

The topology information 13a is information regarding the connection shape of the network NW. The topology information 13a includes device information 13a1, port information 13a2, link information 13a3, and the like.

Of these, the device information 13a1 defines information about the network device 30. For example, the device information 13a1 can employ data associated with items such as a device ID (IDentification) and a device name. The "device ID" referred to here refers to identification information that identifies the network device 30. Further, the "device name" refers to a name defined in the network device 30. Here, the device name is illustrated as an example of the items that define the network device 30, but other items such as the serial number and the model number can be further included in the device information 13a1.

Further, the port information 13a2 defines information about the port of the network device 30. For example, for the port information 13a2, data associated with items such as a port ID, a device ID, and a port name can be adopted. The "port ID" referred to here refers to identification information that identifies a port possessed by the network device 30. Further, the "device ID" refers to the identification information of the network device 30 like the device ID included in the device information 13a1, but here, it means the network device 30 having a port identified by the port ID. .. The "port name" refers to the name defined for the port. Although the above three items have been illustrated here, other settings related to the port, such as VLAN (Virtual LAN) and LAG (Link Aggregation Group), may be further associated.

Further, the link information 13a3 defines information regarding a link connecting the ports of the network device 30. For example, for the link information 13a3, data associated with items such as a link ID, a device ID1, a port ID1, a device ID2, and a port ID2 can be adopted. The "link ID" referred to here refers to identification information that identifies a link. Further, "port ID 1" and "port ID 2" refer to port identification information like the port ID included in the port information 13a2, but here, of two ports connecting the links identified by the link ID. Means identification information. Further, the "device ID 1" and the "device ID 2" refer to the identification information of the network device 30 as well as the device ID included in the device information 13a1, but here, the network device 30 having the port identified by the port ID 1. It means the identification information of the network device 30 and the identification information of the network device 30 having the port identified by the port ID 2. In this way, among the ports included in the device information 13a1, the connected port or the linked-up port is registered in the link information 13a3.

The filter information 13b is information regarding the range to which the filter is applied. The "filter" referred to here refers to a function of suppressing notification of a link-down state as only one aspect.

For example, the above filter may be applied on the condition that the cause of the link down state is identified as unconnected. As an example, in the filter information 13b, a range of network devices to which the above filter is applied and a range of notification forms to which the above filter is applied are set.

Here, as an example of the applicable range of the network device 30, at least one of the options such as none, individual, whole, and edge switch is set. For example, when "individual" is set, the network device 30 to which the filter is applied can be individually specified among the network devices 30 that construct the network NW. In this case, the device ID of the network device 30 designated by the client terminal 50 is also set. Further, when "whole" is set, the above filter is applied to all network devices 30 that construct the network NW. When the "edge switch" is set, the above filter is applied to the network device 30 to which the user terminal and peripheral devices are connected, that is, the so-called edge switch, among the network devices 30 that construct the network NW. As a matter of course, when "None" is set, the above filter is not applied to all the network devices 30 that construct the network NW. Although the above three examples have been illustrated here as an example of the applicable range of the network device 30, the range to which the filter is applied may be set for each port.

Further, as an example of the applicable range of the notification form, at least one of the options such as the patrol lamp, the device icon, and the patrol lamp + device icon is set. The "patrol lamp" referred to here is a kind of warning light marking displayed on the topology map, and a mark indicating either "normal" or "abnormal" is displayed. That is, when the network device 30 having the port in the link-down state does not exist in the network NW, "normal" is displayed, while at least one network device 30 having the port in the link-down state exists in the network NW. If so, "abnormal" is displayed. Further, the “device icon” refers to an icon in which the network device 30 and the ports of the network device 30 are modeled. For example, when "Patrol Lamp" is set, the above filter is applied to the display of Pat Lamp. When the "device icon" is set, the above filter is applied to the display of the device icon. Further, when "Patrol lamp + device icon" is set, the above filter is applied to the display of the patrol lamp and the device icon.

Further, the filter information 13b can be provided with a determination flag for port connection check. For example, the determination flag can be used to determine whether or not the port connection check is a condition for applying the above filter. As an example, a binary variable such as 0 or 1, false or true can be set in this determination flag. For example, if the judgment flag is set, the result of the connection check determines whether or not the notification of the link down status is suppressed, while if the judgment flag is not set, it is either unconnected or connected. Notification of link down status is suppressed regardless of the presence. In this way, by setting the determination flag to ON or OFF via the client terminal 50 or the like, it is possible to select whether or not to check the connection as a condition for applying the filter.

The control unit 15 is a processing unit that controls the entire network management device 10.

As one embodiment, the control unit 15 can be implemented by a hardware processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). Here, a CPU and an MPU are illustrated as an example of a processor, but it can be implemented by any processor regardless of a general-purpose type or a specialized type. In addition, the control unit 15 may be realized by hard-wired logic such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 15 is a control program that realizes the above-mentioned network management service function on a work area of a RAM such as a DRAM (Dynamic Random Access Memory) or a SRAM (Static Random Access Memory) mounted as a main storage device (not shown). By expanding, the following processing unit is virtually realized.

As shown in FIG. 2, the control unit 15 includes a first collection unit 15a, a display control unit 15b, a second collection unit 15c, a specific unit 15d, a determination unit 15e, and a notification control unit 15f. Have.

The first collection unit 15a is a processing unit that collects information on the topology from the network device 30.

As one embodiment, the first collection unit 15a collects information on the topology from the network device 30 on the network NW at the following timings. As an example of the timing at which such collection is executed, in addition to the case where a predetermined cycle, for example, 5 seconds has elapsed since the last acquisition was executed, the instruction input is performed via the client terminal 50. In this case, the system time stored in the internal memory (not shown) may reach a predetermined regular time, for example, a time such as 6:00, 12:00, or 18:00.

Specifically, the first collecting unit 15a transmits commands such as show running-config and show interfaces status to the network device 30 on the network NW. As a result, the link-up state of the port and the setting of the port, for example, WLAN_ID, can be acquired as the return value of the command. Further, the first collecting unit 15a transmits a command such as show lldp neighbors to the network device 30 on the network NW. As a result, the information advertised via LLDP (Link Layer Discovery Protocol) between the network device 30 to which the command is sent and the network device 30 to which the command is sent is connected to each other, for example, to each other. You can get the interface information of the port as the return value of the command. According to the information collected by using these commands, the first collection unit 15a generates the topology information 13a and newly registers it in the storage unit 13, or updates the topology information 13a stored in the storage unit 13. To do. Here, the case where information is exchanged between devices via LLDP has been illustrated, but a protocol other than LLDP, for example, CDP (Cisco (registered trademark) Discovery Protocol) may be used. In this case, the first collecting unit 15a can collect the interface information by transmitting a command such as show cdp neighbors to the network device 30 on the network NW to the network device 30.

Although the case where the topology information 13a is registered and updated according to the information acquired by the first collecting unit 15a is illustrated here, these registrations and updates can also be realized by other methods. .. For example, the topology information 13a can be registered and updated from the MIB information acquired from the network device 30. Further, the network administrator or the like may be allowed to input via the client terminal 50. In this case, as an example, the topology map can be drawn by accepting the arrangement of the device icon and the drawing of the link connecting the ports via the client terminal 50.

The display control unit 15b is a processing unit that controls the display of the client terminal 50.

As one aspect, the display control unit 15b refers to the topology information 13a stored in the storage unit 13 and causes the client terminal 50 to display a topology map in which the connection shape between devices included in the network NW is schematicized. For example, the display control unit 15b arranges a device icon in which the network device 30 corresponding to the device ID defined in the device information 13a1 of the above topology information 13a is modeled. Further, the display control unit 15b further expands and displays a symbol in which each port of the network device 30 corresponding to the device icon corresponds to the port information 13a2 in the above topology information 13a. Further, the display control unit 15b further draws a line drawing of a link connecting the port symbols of the network device 30 in which the port ID 1 and the port ID 2 are registered in the link information 13a3 of the above topology information 13a. The topology map generated in this way is displayed on the client terminal 50.

The second collecting unit 15c is a processing unit that collects information on a failure from the network device 30.

As one embodiment, the second collecting unit 15c can be implemented by an SNMP (Simple Network Management Protocol) manager or the like. For example, the second collecting unit 15c periodically acquires the MIB information of each network device 30 by transmitting the SNMP command to the SNMP agent operating on the network device 30 at a predetermined interval, for example, 5 minutes. At this time, the second collecting unit 15c can send the SNMP command to the SNMP agent by designating the object ID for acquiring the interface information in the MIB information. In addition, the second collection unit 15c sets the reception of the linkdown trap of the port, so that when a link down occurs in the port of the network device 30, the link down is performed to the SNMP agent operating on the network device 30. You can also be notified. Either one of these SNMP commands and SNMP traps can be used, or both can be used together.

The identification unit 15d is a processing unit that identifies the port of the network device 30 in which the link down has occurred, based on the information collected from each network device 30 included in the network NW.

As one embodiment, the specific unit 15d searches for a port in the link-down state from the ports included in the interface information collected by the second collection unit 15c, so that the port of the network device 30 in which the link-down has occurred is performed. To identify. In addition, the identification unit 15d identifies the port of the network device 30 in which the link down has occurred by the linkdown trap notified from the SNMP agent.

After that, the specific unit 15d refers to the filter information 13b stored in the storage unit 13 to determine whether or not the network device 30 having the port in the link-down state is within the applicable range of the filter. For example, when the applicable range of the network device 30 of the filter information 13b is set to "individual", whether or not the device ID corresponding to the network device 30 having the port in the link down state is registered in the filter information 13b. To judge. At this time, if the device ID is registered in the filter information 13b, the network device 30 having the port in the link-down state is identified as being within the applicable range of the filter. Further, when the applicable range of the network device 30 of the filter information 13b is set to "whole", the network device 30 having the port in the link down state is unconditionally identified as being within the applicable range of the filter. .. Further, when the applicable range of the network device 30 of the filter information 13b is set to "edge switch", when the network device 30 having the port in the link down state is the edge switch, it is within the applicable range of the filter. Be identified. As a matter of course, when the applicable range of the network device 30 of the filter information 13b is set to "None", the network device 30 having the port in the link down state is unconditionally out of the applicable range of the filter. Identified as being.

The determination unit 15e is a processing unit that determines whether or not the specified port is connected to the port of another device based on the information collected from the network device 30 included in the network NW.

As one embodiment, when the network device 30 having the port in the link-down state is identified as being within the applicable range of the filter, the determination unit 15e executes the following processing. That is, the determination unit 15e refers to the link information 13a3 of the topology information 13a stored in the storage unit 13 to determine whether or not the port specified by the specific unit 15d is connected to another port. For example, the determination unit 15e determines whether or not the port ID corresponding to the port specified by the specific unit 15d is registered in the field of the port ID 1 or the port ID 2 defined in the link information 13a3. At this time, if the port ID is registered in the field of the port ID 1 or the port ID 2 of the link information 13a3, it can be identified that the port in the link down state is already connected.

The notification control unit 15f is a processing unit that controls notification of failure occurrence.

As one aspect, when the determination unit 15e determines that the port in the link-down state has already been connected, the notification control unit 15f notifies the port in which the link-down state is specified by the specific unit 15d that a failure has occurred. To give permission. The notification of the occurrence of the failure is carried out according to the applicable range of the notification form of the filter information 13b, for example, "Patrol lamp", "Device icon" or "Patrol lamp + device icon". For example, when the applicable range of the notification form of the filter information 13b is "Patrol lamp" or "Patrol lamp + device icon", the following notification control is implemented. That is, when the display of the patrol lamp is "Normal (normal)", the notification control unit 15f switches the display of the patrol lamp arranged on the topology map from "Normal (normal)" to "Error (abnormal)". Is executed by the display control unit 15b. Further, when the applicable range of the notification form of the filter information 13b is "device icon" or "patrol lamp + device icon", the following notification control is implemented. That is, the notification control unit 15f causes the display control unit 15b to execute display control for distinguishing the display form between the symbol of the port in the link-down state and the symbol of the port not in the link-down state on the topology map. For example, the notification control unit 15f adds a mark indicating link down to the symbol of the port in the link down state on the topology map.

As another aspect, when the determination unit 15e does not determine that the port in the link-down state has already been connected, the notification control unit 15f causes a failure in the port whose link-down state is specified by the specific unit 15d. Suppress notifications.

[Specific examples of failure notification and suppression]
FIG. 3 is a diagram showing an example of a topology map. Although the ports and links related to the two network devices 30 are excerpted and shown in FIG. 3 for convenience of explanation, the form of the network NW constructed in the monitored system 3 is not limited to the illustrated example. Absent. Further, on the left side of FIG. 3, the topology map 300 when Node-1 having the port where the link down occurs is out of the applicable range of the network device 30 of the filter information 13b is shown, while the center of FIG. 3 and the center of FIG. On the right side, topology maps 310 and 320 are shown when Node-1 having a port where link down occurs is within the scope of network device 30 of filter information 13b. Further, in the center and the right side of FIG. 3, topology maps 310 and 320 are shown when the applicable range of the notification form of the filter information 13b is "Patrol lamp + device icon". Further, the topology map 310 of FIG. 3 shows an example in which the port “02” of Node-1 and the port “02” of Node-2 are not connected, while the topology map 320 of FIG. 3 shows a Node. An example is shown in which the port “02” of -1 and the port “02” of Node-2 are already connected.

For example, even if a link down occurs at the port "02" of the Node-1, if the Node-1 is out of the applicable range of the network device 30 of the filter information 13b, the link down is as shown in the topology map 300 of FIG. Notification of occurrence is not suppressed. That is, the patrol lamp 300A displays "Error" by linking down the port "02" of Node-1, and the symbol of port "02" of the device icon of Node-1 indicates the link down state. A mark and a black circle in the figure are added.

On the other hand, when Node-1 is within the applicable range of the network device 30 of the filter information 13b, the notification of the occurrence of link down is suppressed as shown in the topology map 310 of FIG. This is because the port "02" of Node-1 is not connected to other ports. In this case, even if the Patramp 310A has a link down of the port "02" of Node-1, the display of "Normal" remains, and the symbol of the port "02" of the device icon of Node-1 is also displayed. , The mark indicating the link down state is not added. In this way, when the cause of the link down is unconnected, by suppressing the notification of the occurrence of the link down, the notification of the occurrence of the link down is narrowed down to the one whose cause is the failure, and there is no intention to make it function as a link. It is possible to reduce the annoyance of notifying the occurrence of link down related to the port. Therefore, it is possible to suppress the notification of the occurrence of link down from becoming complicated. Furthermore, if Node-1 is not an edge switch, shutting down the unconnected port will have the advantage of notifying the occurrence of a failure in terms of power saving, but if Node-1 is an edge switch, Node-1 will benefit. There is a use case where the unconnected port is not intentionally shut down in order to flexibly change the device connected to the port of -1, for example, the user terminal or the peripheral device. In this case, it is more advantageous to suppress the notification than to notify the occurrence of the link down. In order to deal with such use cases, the applicable range of the network device 30 of the filter information 13b can be narrowed down to the edge switch.

In this way, even if Node-1 is within the applicable range of the network device 30 of the filter information 13b, when the port “02” of Node-1 and the port “02” of Node-2 are connected, the topology of FIG. As shown in Map 320, the occurrence of link down will be notified. That is, the patrol lamp 320A displays "Error" by linking down the port "02" of Node-1, and the symbol of port "02" of the device icon of Node-1 indicates the link down state. A mark and a black circle in the figure are added. In this way, the suppression of the notification of the occurrence of link down can be released according to the change in the connection state from the unconnected to the connected.

FIG. 4 is a diagram showing an example of a topology map. Also in FIG. 4, for convenience of explanation, the ports and links related to the two network devices 30 are shown as excerpts, but the form of the network NW constructed in the monitored system 3 is not limited to the illustrated example. Absent. Further, on the left side of FIG. 4, the topology map 400 when Node-1 having the port where the link down occurs is out of the applicable range of the network device 30 of the filter information 13b is shown, while on the right side of FIG. Shows the topology map 410 when Node-1 having the port where the link down occurs is within the applicable range of the network device 30 of the filter information 13b. Further, on the right side of FIG. 4, a topology map 410 is shown when the applicable range of the notification form of the filter information 13b is “pat lamp + device icon”.

As shown in the topology maps 400 and 410 of FIG. 4, when the link down occurs in the port "01" of the already connected Node-1, even if the Node-1 is within the applicable range of the network device 30 of the filter information 13b. , Even if Node-1 is out of the scope of the network device 30 of the filter information 13b, the notification of the occurrence of link down is not suppressed. That is, "Error" is displayed on the patrol lamps 400A and 410A by linking down the port "01" of Node-1, and the symbol of the port "01" of the device icon of Node-1 is in the link down state. A mark indicating, and a black circle in the figure are added. In this way, since the occurrence of the link down of the connected port is notified, the notification of the occurrence of the failure of the port that has been linked up is not confused with the notification of the occurrence of the link down of the unintended port to function as a link. Therefore, it is possible to prevent the notification of the occurrence of link down from becoming complicated. As a result, it can also help shorten the period from link down to recovery.

[Processing flow]
FIG. 5 is a flowchart showing the procedure of the monitoring process according to the first embodiment. As an example, this process is started on the condition that the occurrence of link down is identified. As shown in FIG. 5, when the port in which the link down has occurred is specified (step S101Yes), the specific unit 15d refers to the filter information 13b stored in the storage unit 13 to select the port in the link down state. It is determined whether or not the network device 30 to be held is within the applicable range of the filter (step S102).

At this time, if the network device 30 having the port in the link-down state is out of the application range of the filter (step S102No), the notification control unit 15f notifies the occurrence of the link-down through the display of the patrol lamp or the device icon on the topology map. (Step S103), and the process is terminated.

On the other hand, when the network device 30 having the port in the link-down state is within the applicable range of the filter (step S102Yes), the specific unit 15d refers to the filter information 13b stored in the storage unit 13 to check the connection. It is further determined whether or not the determination flag is ON, that is, whether or not the filter is applied only to the ports that are not connected (step S104).

At this time, when the filter is applied only to the unconnected ports (step S104Yes), the determination unit 15e is specified in step S101 with reference to the link information 13a3 of the topology information 13a stored in the storage unit 13. It is determined whether or not the port is connected to another port (step S105).

Here, when the port in the link-down state is not connected (step S105No), the notification control unit 15f suppresses the notification of the occurrence of a failure for the port whose link-down state is specified by the specific unit 15d (step S106). , End the process.

Further, when the port in the link down state is already connected (step S105Yes), the notification control unit 15f notifies the occurrence of the link down through the display of the patrol lamp or the device icon on the topology map (step S103), and performs the process. finish.

Further, when the application of the filter is not limited to the unconnected port (step S104No), it is not necessary to perform the connection check of the port in the link-down state in order to suppress the notification of the link-down state. In this case, the notification control unit 15f suppresses the notification of the occurrence of a failure for the port whose link-down state is specified by the specific unit 15d (step S106), and ends the process.

[One aspect of the effect]
As described above, the network management device 10 according to the present embodiment controls whether or not to suppress the notification of the occurrence of the link down depending on whether or not the port in which the link down has occurred is connected to another port. .. Therefore, it is possible to reduce the troublesomeness of notifying the occurrence of a link down regarding a port that is not intended to function as a link. In addition, as a result of being able to narrow down the notification of the occurrence of the link down to the one whose cause is the failure, the notification of the occurrence of the failure regarding the port that was linked up is included in the notification of the occurrence of the link down regarding the unintended port to function as a link. It can also be deterred from being confused with. Therefore, according to the network management device 10 according to the present embodiment, it is possible to suppress the notification of the occurrence of link down from becoming complicated.

Although examples of the disclosed device have been described above, the present invention may be implemented in various different forms other than the above-described examples. Therefore, other examples included in the present invention will be described below.

[Notification form]
In the first embodiment described above, the case where the notification of the occurrence of a failure is realized by the display is illustrated, but the notification form of the occurrence of the failure is not limited to the display. For example, the network management device 10 can realize the notification of the occurrence of a failure by voice, or can realize it by display and voice. In this case as well, if the port where the link down has occurred is not connected, voice notification can be suppressed. In addition, when the notification of the occurrence of a failure is realized by display and voice, if the port where the link down has occurred is not connected, it is possible to suppress only the notification of either display or voice.

[Suppress log output]
In the first embodiment described above, the case of suppressing the notification of the occurrence of a failure has been illustrated, but other processing, for example, the log output of the network device 30 can also be suppressed. For example, if the port where the link down occurred is not connected, the link down log output can be suppressed.

[Failures other than link down]
In the above-described first embodiment, the link down is illustrated as an example of the failure, but the target for performing the notification control is not limited to the link down. For example, the network management device 10 has not notified the other failures such as the power failure of the port of the network device 30 or the network device 30, the temperature abnormality of the network device 30, the component failure of the network device 30, and other failures. It can be suppressed depending on whether or not the connection is made.

[Distributed and integrated]
Further, each component of each of the illustrated devices does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or part of the device is functionally or physically distributed / physically in arbitrary units according to various loads and usage conditions. It can be integrated and configured. For example, the first collection unit 15a, the display control unit 15b, the second collection unit 15c, the specific unit 15d, the determination unit 15e, or the notification control unit 15f are connected via the network as an external device of the network management device 10. May be good. Further, another device has a first collection unit 15a, a display control unit 15b, a second collection unit 15c, a specific unit 15d, a determination unit 15e, or a notification control unit 15f, and is connected to a network to cooperate. Then, the function of the network management device 10 may be realized. Further, another device has all or a part of the topology information 13a and the filter information 13b stored in the storage unit 13, and the functions of the network management device 10 are realized by being connected to a network and cooperating with each other. You can do it.

[Monitoring processing program]
Further, the various processes described in the above-described embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. Therefore, in the following, an example of a computer that executes a monitoring processing program having the same function as that of the above embodiment will be described with reference to FIG.

FIG. 6 is a diagram showing a hardware configuration example of a computer that executes the monitoring processing program according to the first and second embodiments. As shown in FIG. 6, the computer 100 includes an operation unit 110a, a speaker 110b, a camera 110c, a display 120, and a communication unit 130. Further, the computer 100 has a CPU 150, a ROM 160, an HDD 170, and a RAM 180. Each part of these 110 to 180 is connected via a bus 140.

As shown in FIG. 6, the HDD 170 includes a first collection unit 15a, a display control unit 15b, a second collection unit 15c, a specific unit 15d, a determination unit 15e, and a notification control unit 15f shown in the first embodiment. The monitoring processing program 170a that exhibits the same function as the above is stored. The monitoring processing program 170a is similar to the components of the first collection unit 15a, the display control unit 15b, the second collection unit 15c, the specific unit 15d, the determination unit 15e, and the notification control unit 15f shown in FIG. It may be integrated or separated. That is, not all the data shown in the first embodiment may be stored in the HDD 170, and the data used for processing may be stored in the HDD 170.

Under such an environment, the CPU 150 reads the monitoring processing program 170a from the HDD 170 and deploys it to the RAM 180. As a result, the monitoring processing program 170a functions as the monitoring processing process 180a as shown in FIG. The monitoring processing process 180a expands various data read from the HDD 170 in the area allocated to the monitoring processing process 180a in the storage area of the RAM 180, and executes various processes using the expanded various data. For example, as an example of the process executed by the monitoring process process 180a, the process shown in FIG. 5 is included. In the CPU 150, not all the processing units shown in the first embodiment need to operate, and the processing units corresponding to the processes to be executed may be virtually realized.

The monitoring processing program 170a may not necessarily be stored in the HDD 170 or the ROM 160 from the beginning. For example, each program is stored in a "portable physical medium" such as a flexible disk inserted into the computer 100, a so-called FD, CD-ROM, DVD, magneto-optical disk, or IC card. Then, the computer 100 may acquire and execute each program from these portable physical media. Further, each program is stored in another computer or server device connected to the computer 100 via a public line, the Internet, LAN, WAN, etc., so that the computer 100 acquires and executes each program from these. It may be.

1 Network management system 3 Monitored system 10 Network management device 11 Communication I / F unit 13 Storage unit 13a Topology information 13b Filter information 15 Control unit 15a First collection unit 15b Display control unit 15c Second collection unit 15d Specific unit 15e Judgment unit 15f Notification control unit 30A, 30B, 30C Network device 50 Client terminal

Claims (5)

In the monitoring processing program to be executed by the monitoring device that notifies the failure occurrence of the port of the device included in the network to be monitored
Based on the information collected from each device included in the monitored network, the port of the device where the link down occurred is identified.
Based on the information collected from each device included in the network to be monitored, it is determined whether or not the specified port is connected to the port of another device.
Whether or not to notify the occurrence of a failure for the specified port depending on whether or not the connection is made and whether or not the device in which the link down has occurred corresponds to the edge switch on the monitored network. Control,
A monitoring processing program characterized by this. When it is determined that the connection is established, the specified symbol is displayed while displaying a line connecting the symbol corresponding to the specified port and the symbol corresponding to the other device to be connected or the port of the other device. When a failure occurrence notification is displayed corresponding to the symbol corresponding to the port and it is determined that the connection is not established, the symbol corresponding to the specified port is displayed on another device or the port of the other device. The display is not connected to the corresponding symbol by a line, and the notification of the failure occurrence corresponding to the symbol corresponding to the specified port is not displayed.
The monitoring processing program according to claim 1. When it is not determined that the connection is established, and when the device in which the link down occurs corresponds to the edge switch on the monitored network, the specified port is not notified of the occurrence of a failure. The monitoring processing program according to claim 1. In the monitoring processing method in the monitoring device that notifies the occurrence of a failure regarding the port of the device included in the network to be monitored
Based on the information collected from each device included in the monitored network, the port of the device where the link down occurred is identified.
Based on the information collected from each device included in the network to be monitored, it is determined whether or not the specified port is connected to the port of another device.
Whether or not to notify the occurrence of a failure for the specified port depending on whether or not the connection is made and whether or not the device in which the link down has occurred corresponds to the edge switch on the monitored network. Control,
A monitoring processing method characterized by this. In a monitoring device that notifies the occurrence of a failure related to the port of the device included in the network to be monitored
Based on the information collected from each device included in the monitored network, a specific unit that identifies the port of the device where the link down occurred, and
A determination unit that determines whether or not the specified port is connected to a port of another device based on the information collected from each device included in the network to be monitored.
Whether or not to notify the occurrence of a failure for the specified port depending on whether or not the connection is made and whether or not the device in which the link down has occurred corresponds to the edge switch on the monitored network. and the notification control unit for controlling,
A monitoring device characterized by having.

Images