JP2010147595A - Apparatus and method for management of network - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network management apparatus capable of quickly locating a device causing a network failure. <P>SOLUTION: The network management apparatus monitors fault in a network layer by confirming delivery. The apparatus includes a network configuration DB memory 11 and a network controller 12. The network configuration DB memory associates a device to be managed with a route information indicative of devices to be managed on a route to the apparatus and holds them. If there is no response to delivery confirming for the device to be managed, the network controller extracts the route information for the device to be managed without the response from the held information, and carries out delivery confirming to the device to be managed of the route information. The network controller specifies the device to be managed without response to the delivery confirming as a fault generating device. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a network management apparatus and a network management method for monitoring health at a network layer level.

  A network management device that checks the health of the network using a conventional ping for delivery confirmation does not consider the network configuration and periodically sends a ping to the managed device. To check the soundness of the managed device and the route to the device.

  On the other hand, in the following Patent Document 1, there is a method for specifying a predictive occurrence range and a cause location for a failure that is expected to occur in the future by using network configuration information and performance information of each device constituting the network. It is disclosed.

JP 2002-99469 A

  However, according to the soundness confirmation technique using the conventional Ping, when the sounding confirmation for the management target device cannot be confirmed, the Ping transmission destination management target device cannot be reached. However, it is impossible to determine whether there is a problem with the Ping transmission destination managed device or whether there is a problem with the route (device on the route) from the network management device to the managed device. Therefore, the network management device performs a ping transmission to each device to be managed, so that a certain amount of time is required to isolate the device in which the problem really occurs based on the soundness confirmation result of each management device. In other words, there is a problem in that it takes time from the occurrence of a failure to the identification of the cause device.

  In addition, when viewed from the network management device, not only the cause location but also all delivery confirmations for devices that communicate via the cause location will fail to be confirmed, so a large number of failure states will be detected, and the correct cause location Is difficult to recognize.

  In addition, in the above-described soundness confirmation technology using Ping, delivery confirmation by Ping is performed equally for all managed devices, but the importance of delivery confirmation on the network is the same for each device. is not. Therefore, there is a problem that the soundness is not always checked efficiently.

  The present invention has been made in view of the above, and an object of the present invention is to provide a network management device and a network management method that can quickly isolate a cause device that is the true cause of a network failure.

  In order to solve the above-described problems and achieve the object, the present invention provides a network management apparatus that performs fault monitoring in a network layer based on a result of delivery confirmation, and is a management target apparatus that is a target of the fault monitoring And network configuration information storage means for associating the path information indicating the management target device on the path to the management target device and holding it as network configuration information, and when there is no response to the delivery confirmation Extracts the route information corresponding to the managed device that did not respond from the network configuration information, performs the delivery confirmation for the managed device included in the extracted route information as the failure detection delivery confirmation, and the failure detection delivery confirmation Network management means for identifying a managed device that has not responded to a failure occurrence device as a failure occurrence device. And butterflies.

  According to this invention, the device existing on the route to the management target device as the route information to the management target device is held as the network configuration DB, the delivery confirmation is performed to the management target device stored in the network configuration DB, Confirm delivery to the device included in the route information of the managed device that did not respond, and determine that the device closest to itself among the devices that did not respond to the delivery confirmation failed Therefore, there is an effect that it is possible to quickly isolate the cause device that is the true cause of the network failure.

  Embodiments of a network management apparatus according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram illustrating a functional configuration example of a first embodiment of a network management device according to the present invention. As shown in FIG. 1, the network management device 1 according to the present embodiment stores a network configuration DB for storing, for each device to be managed, a network configuration DB that is information on a device on a communication path to the device. A (Data Base) storage unit 11, a network management unit 12 that performs network management, and a network interface unit 13 are configured.

  When the network management unit 12 checks the soundness of each device by periodically sending a Ping to the management target device registered in the network configuration DB of the network configuration DB storage unit 11, and the Ping response does not return If the Ping response is returned, the device is determined to be normal, and the device is in a normal state. The fault information collecting unit 14 and the fault managing unit 15 that stores the fault information notified from the fault information collecting unit 14 and notifies the operator of the fault information.

  In addition, the network interface unit 13 transmits the Ping transmitted by the failure information collection unit 14 to the network, captures the Ping response from the network, and sends it to the network management unit 15.

  FIG. 2 is a diagram illustrating an example of the structure of the network configuration DB. As shown in FIG. 2, the network configuration DB includes a management target device and route information to the management target device, and the route information includes a device (router) that exists on the route to the corresponding management target device. Is stored.

  FIG. 3 is a diagram illustrating a configuration example of the network system according to the present embodiment. Here, the routers 3-1 to 3-6 will be described as examples of the management target devices. As shown in FIG. 3, the network system according to the present embodiment includes a network management device 1 and a managed network 2, and the managed network includes routers 3-1 to 3-6. Yes. 2 is set based on the configuration example shown in FIG. 3, and R1, R2,..., As identifiers of the routers 3-1, 3-2,. R6 is used respectively.

  The failure information collection unit 14 periodically sends a ping to a device registered in the network configuration DB at a predetermined cycle to confirm delivery. At this time, for example, from the router 3-5 (R5) Suppose the response could not be confirmed. In this case, the failure information collection unit 14 refers to the network configuration DB and exists on the route to the router 3-5 based on the route information corresponding to the identifier R5 of the router 3-5 that has not been able to confirm the response. The routers to be identified are the router 3-1 (R1) and the router 3-4 (R4).

  Then, the failure information collection unit 14 first transmits a Ping to the router 3-1 among the identified routers to confirm delivery. If the response from the router 3-1 is confirmed, it is determined that the soundness of the route to the router 3-1 has been confirmed, and a ping is transmitted to the router 3-4 to confirm delivery. If the response from the router 3-4 can be confirmed, the failure has occurred due to the soundness of the route to the router 3-1 and the route to the router 3-4. The failure management unit 15 is notified of failure information indicating that the router 3-5 is in a failure state.

  Further, the failure information collecting unit 14 determines that a failure has occurred in the router 3-1, when the response from the router 3-1 cannot be confirmed and the response from the router 3-4 is confirmed. If the responses from both the routers 3-1 and 3-4 cannot be confirmed, it is determined that a failure has occurred in the router 3-1, which is a device closer to the network management device 1. The failure information collection unit 14 determines that a failure has occurred in the router 3-4 when the response from the router 3-4 cannot be confirmed and the response from the router 3-1 can be confirmed. As described above, the failure information collection unit 14 determines that a failure has occurred in the router closest to itself among the routers for which no response has been confirmed, and determines that the router that has determined that a failure has occurred is in a failure state. The failure management unit 15 is notified of the failure information shown.

  When the failure management unit 15 recognizes that the router causing the failure is the router 3-5 based on the failure information received from the failure information collection unit 14, the failure management unit 15 notifies the administrator (operator) (for example, voice or With reference to the network configuration DB, the router 3-5 (R5) searches for a management target device included in the route information. In the case of the example of FIG. 2, since the router 3-5 is included in the route information of the router 3-5 and the router 3-6, routers 3-5 and 3-6 are obtained as search results. If this information is used, it can be estimated that the router 3-5 is the cause of the failure even when there is no response in the Ping delivery confirmation of the router 3-6. For example, the failure management unit 15 notifies the failure information collection unit 14 of the search result, and the failure information collection unit 14 does not confirm the delivery of the router 3-6 to the router on the route without using the router 3-6. The cause device that cannot confirm the delivery confirmation response may be determined as the router 3-5, or when it is further confirmed whether there is another cause device that cannot confirm the delivery confirmation response of the router 3-6. May determine the causal device only with the router that is closer to the network management device 1 than the router 3-5 as the target of delivery confirmation.

  As described above, in the present embodiment, the management target device and the devices existing on the route to the management target device as the route information to the management target device are held as the network configuration DB, and the network management unit 12 performs the network configuration. Confirm delivery to the managed device stored in the DB, confirm delivery to the device included in the route information of the managed device that did not respond, and the device closest to itself among the devices that did not respond Judged that a failure occurred. For this reason, it is possible to quickly isolate the location that is an obstacle.

Embodiment 2. FIG.
FIG. 4 is a diagram showing a functional configuration example of the second embodiment of the network management apparatus according to the present invention. As shown in FIG. 4, the network management device 1a of the present embodiment is the same as the network management device 1 of the first embodiment except that a configuration setting interface unit 16 is added to the network management device 1 of the first embodiment. It is. Components having the same functions as those in the first embodiment are given the same reference numerals and description thereof is omitted. Hereinafter, a different part from Embodiment 1 is demonstrated.

  The configuration setting interface unit 16 of the present embodiment is an interface for the administrator to set the structure of the network to be managed in the network configuration DB 11, and accepts registration and change in the network configuration DB 11 by the operation of the administrator. The contents are reflected in the network configuration DB 11. The operations of the present embodiment other than those described above are the same as those of the first embodiment.

  As described above, in the present embodiment, the configuration setting interface unit 16 receives registration and change in the network configuration DB 11 by the operation of the administrator, and reflects the contents in the network configuration DB 11. Therefore, even when the actual configuration of the management target network is changed, the change can be reflected in the contents of the network configuration DB.

Embodiment 3 FIG.
FIG. 5 is a diagram illustrating a functional configuration example of the third embodiment of the network management device according to the present invention. As shown in FIG. 5, the network management device 1b of the present embodiment is the same as the network management device 1 of the first embodiment, except that a network configuration collection unit 17 is added to the network management device 1 of the first embodiment. It is. Components having the same functions as those in the first embodiment are given the same reference numerals and description thereof is omitted. Hereinafter, a different part from Embodiment 1 is demonstrated.

  The network configuration collection unit 17 automatically collects information on the structure of the management target network and reflects it in the network configuration DB 11. As a method for collecting information, any generally used method may be used as long as it is a method capable of knowing the network structure (devices on the route to each device to be managed).

  For example, the network configuration collection unit 17 automatically collects information on the structure of the management target network when the network management device is started up. Further, when there is a possibility that a change is made, the network configuration collection unit 17 may periodically collect information on the structure of the management target network periodically. This information collection is performed by, for example, a traceroute command. The operations of the present embodiment other than those described above are the same as those of the first embodiment.

  Thus, in this embodiment, the network configuration collection unit 17 automatically collects information on the structure of the management target network and reflects it in the network configuration DB 11. Therefore, the network configuration DB can be automatically set when the system is started up without the administrator setting the network configuration DB in advance.

Embodiment 4 FIG.
The network management apparatus according to the fourth embodiment of the present invention will be described next. The network management apparatus according to the present embodiment has the same configuration as the network management apparatus according to the first embodiment. Hereinafter, a different part from Embodiment 1 is demonstrated.

  In a conventional general network management device, soundness is confirmed by transmitting a ping to all managed devices equally. However, in the network management device according to the present embodiment, it is registered in the network configuration DB. As the path information for each managed device, the number of times each managed device appears is calculated, and the transmission frequency is determined for Ping based on the calculation result.

  As described in the first embodiment, when the network configuration shown in FIG. 3 is assumed, data as shown in FIG. 2 is stored in the network configuration DB. According to FIG. 2, the appearance of router 3-1 (R1), router 3-2 (R2), router 3-3 (R3), router 3-4 (R4), and router 3-5 (R5) as route information The number of times is 6, 2 times, 1 time, 2 times and 1 time, respectively.

  Based on the number of appearances, the failure information collection unit 14 determines the Ping transmission frequency for each router. In the conventional confirmation of soundness by general ping transmission, for example, the pings in the order of router 3-1, router 3-2, router 3-3, router 3-4, router 3-5 and router 3-6 Repeat transmission. On the other hand, in the present embodiment, based on the number of appearances described above, the Ping transmission frequency is determined so as to decrease the Ping transmission frequency as the number of appearances increases.

  For example, first, a ping is transmitted to all of the routers 3-1 to 3-6, and in the next period, a ping is transmitted to the routers 3-3 and 3-6 having one appearance. Further, in the next cycle, the routers 3-2 and 3-4 having the appearance count of 2 are added, and Ping is transmitted to the routers 3-2 and 3-4 and the routers 3-3 and 3-6. Then, similarly to the first transmission, the ping is transmitted to all of the routers 3-1 to 3-6, the ping is transmitted to the routers 3-3 and 3-6 in the next cycle, and the next Ping is transmitted to the routers 3-2, 3-3, 3-4, and 3-5, and thereafter the transmission of Ping is repeated with the three transmission cycles as one set. Note that the frequency of the Ping transmission is not limited to this as long as it is determined to decrease the frequency of Ping transmission as the number of appearances increases.

  As described above, in the present embodiment, the failure information collection unit 14 counts the number of appearances, which is the number of times the management target device appears in the path information of the network configuration DB, and determines the transmission frequency of Ping based on the number of appearances. I tried to do it. Therefore, for a management target device having a large number of appearances, that is, a management target device through which a large number of management target devices pass, the ping transmission frequency can be reduced, and soundness can be efficiently checked.

  As described above, the network management device and the network management method according to the present invention are network management in a system that monitors the health at the network layer level, and in particular, monitors the health by using the delivery confirmation of Ping. Suitable for network management.

It is a figure which shows the function structural example of Embodiment 1 of the network management apparatus concerning this invention. It is a figure which shows an example of the structure of network configuration DB. 1 is a diagram illustrating a configuration example of a network system according to a first embodiment. 6 is a diagram illustrating a functional configuration example of a network management device according to a second embodiment. FIG. FIG. 10 is a diagram illustrating a functional configuration example of a network management device according to a third embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1,1a, 1b Network management apparatus 2 Management object network 3-1 to 3-6 Router 11 Network configuration DB memory | storage part 12 Network management part 13 Network interface part 14 Fault information collection part 15 Fault management part 16 Configuration setting interface part 17 Network Configuration collection unit

Claims (8)

A network management device that performs fault monitoring in a network layer based on a result of delivery confirmation,
Network configuration information storage means for associating the managed device that is the target of the fault monitoring with the path information indicating the managed device on the path to the managed device as network configuration information; ,
If there is no response to the delivery confirmation, the route information corresponding to the managed device that did not respond is extracted from the network configuration information, and the delivery confirmation for the managed device included in the extracted route information is the failure detection delivery confirmation. Network management means for identifying as a failure occurrence device a management target device that did not respond to the failure detection delivery confirmation,
A network management apparatus comprising:   2. The network management device according to claim 1, wherein among the management target devices that have not responded to the failure detection and delivery confirmation, a management target device that has the least number of devices that are routed from its own device is identified as the failure generation device. . When there are a plurality of non-response management target devices that are management target devices that have not responded to the delivery confirmation, a failure detection is performed on the initial non-response management target device that is one of the non-response management target devices. When the delivery confirmation is performed and there is no response to the failure detection delivery confirmation, the initial non-response managed device is identified as the failure occurrence device,
Further, route information corresponding to the non-response management target device that has not performed the failure detection delivery confirmation is extracted from the network configuration information, and the failure generation device is included in the extracted route information for each non-response management target device. If a failure occurrence device is included, the failure occurrence device corresponding to the non-response management target device is a failure generation device corresponding to the initial non-response management target device. The network management device according to claim 1 or 2. Configuration setting means for accepting changes to network configuration information from an operator and reflecting the changes to the network configuration information;
The network management device according to claim 1, further comprising: Network configuration means for detecting path information for each managed device and generating the network configuration information based on the detection result;
The network management device according to claim 1, further comprising:   The frequency of the delivery confirmation is determined based on the count result by counting the frequency of storing itself as route information of the network configuration information for each managed device. The network management device according to any one of the above.   The network management according to claim 6, wherein the frequency of delivery confirmation for a management target device having a high count result is lower than the frequency of delivery confirmation for a management target device having a low count result. apparatus. A network management method for performing fault monitoring in a network layer based on a result of delivery confirmation,
A network configuration information storage step for associating and holding as a network configuration information the managed device to be monitored by the failure and the path information indicating the managed device on the path to the managed device; ,
If there is no response to the delivery confirmation, the route information corresponding to the managed device that did not respond is extracted from the network configuration information, and the delivery confirmation for the managed device included in the extracted route information is the failure detection delivery confirmation. A delivery confirmation step carried out as
A failure generating device specifying step of specifying a management target device that has not responded to the failure detection delivery confirmation as a failure generating device;
A network management method comprising:

Images