KR101490316B1 - Fault Detection System For Network Device And Fault Detection Method Using The Same - Google Patents

Abstract

The present invention relates to a fault detection system for a network device and a fault detection method using the same. The system regularly tests and determines whether there is a fault between IP network devices, and performs, in real time, a fault test between devices according to the increase and decrease in traffic to enable the fast and accurate detection of a device with a fault, a section having a fault, and a traffic change according to a fault, and a swift action. The fault detection system for the network device according to the present invention controls the network device so that any one of network devices interconnected in order to enable the fault detection system to form a network performs a test for detecting a fault on another network device connected thereto, collects test results and determines whether there is the fault.

Description

Technical Field [0001] The present invention relates to a fault detection system and a fault detection method using the same,

The present invention relates to a fault detection system for network equipment and a fault detection method using the same. More particularly, the present invention relates to a system and method for periodically testing whether a fault has occurred between IP network equipment to determine a fault occurrence, The present invention relates to a fault detection system of a network equipment and a fault detection method using the same, which enable quick and accurate detection and quick response of traffic fluctuation caused by a faulty device, section and fault.

In recent years, various services have been provided to users using various networks. Specifically, in recent years, the division of wired and wireless networks has become meaningless, and wired and wireless networks are being used in combination. More particularly, the present invention relates to a wireless communication system and a wireless communication system, which are based on a wired data communication network and which are formed by various networks such as a short distance wireless communication network using a Wi-Fi, an ad hoc communication network formed at the end of a wired data communication network, Data services are being provided.

However, data communication using such a network is mainly based on Internet Protocol (IP). To this end, various networks are constructed using various servers, gateways, and routing devices, and the connection relationship has become more complex than in the past.

In addition, various problems have arisen due to the increase in the complexity of the network, and it has become an important issue in the operation of the network to efficiently detect and process the problems.

One of these problems is packet forwarding failure. The packet forwarding failure is that the interface of the IP network equipment performs normal operation but the packet is normally transmitted due to a failure of the lower transmission layer, for example, an optical module failure, a transmission equipment failure, a failure of the router module, or an overload and bug of the IP network equipment It means a phenomenon that can not be done.

Existing networks have used surveillance management systems such as Network Management System (NMS) to detect various failures including packet forwarding failure.

Such a network management system performs management and testing such as traffic processing in the IP network equipment constituting the network and ping test on the IP network equipment, and provides data and test results collected by the management to the manager. The network management by the network management system is advantageous in that the administrator can easily check the status of the traffic processing in each device and the operation confirmation through the ping test. However, it is difficult to accurately detect the section in which the failure occurs, .

Specifically, the existing network management system has a problem in that it can not determine whether the change in traffic is due to a failure or a simple usage decrease. In other words, even if the traffic is reduced due to the failure, there is no way to confirm whether the traffic is degraded due to the failure because the traffic is simply monitored by the equipment, thereby degrading the quality of the service or reducing it due to other reasons.

Korean Unexamined Patent Application Publication No. 10-2005-0001122 (Publication date 2005.01.06.)

Accordingly, it is an object of the present invention to provide a method and apparatus for periodically testing whether or not a fault has occurred between IP network equipment to determine the occurrence of a fault and, in addition, The present invention provides a fault detection system for a network equipment and a fault detection method using the same.

In order to achieve the above object, a fault detection system of a network device according to the present invention is characterized in that a fault detection system is a system in which any one of the network devices connected to each other to form a network is connected to another network device And a failure detection system for controlling the network device to perform a test for failure detection and collecting test results to determine whether a failure has occurred.

And the test is a ping test.

The test may include a real-time test in which at least one of a standard test, a condition, a cycle, a number of times per test, and a test run time is performed according to a predetermined condition or cycle. do.

The fault detection system collects traffic information of the network device to determine whether the traffic has dropped. If it is determined that the traffic of the network device has dropped, the network device performs the real time test.

Wherein the fault detection system comprises: a network management unit for collecting traffic information of the network device; commanding the network device to perform the standard test or the real-time test; collecting the test result to determine occurrence of a fault; To the network management unit.

Wherein the failure detection unit controls the network device so that the host performs the test on the target, with any one of the network devices connected to each other as a host and the other network device as a target.

Wherein the network management unit is a host and performs a ping test on any one of the network devices.

The network device is a router, and the test is performed on the L3 interface of the router.

And the failure detection unit collects connection information of the network device.

A method for detecting a failure of a network device according to the present invention is a method for detecting a failure of any one of network devices connected to each other in order to form a network, Controlling the network device to perform a test; The fault detection system collecting the test result from the network device; And determining whether a fault has occurred by the collected test results.

And the test is a ping test.

Wherein the test is configured to include a real-time test that is performed in accordance with at least one of a standard test, a condition, a cycle, a number of tests per hour, and a test process time, do.

Wherein the step of controlling the network device comprises: collecting traffic information of the network device by the fault detection system; Determining whether the traffic detection system is using the traffic information to determine whether the traffic has plummeted; And controlling the network device to perform the real-time test on the network device in which the traffic has fallen if the failure detection system determines that the traffic has plummeted.

Wherein the step of collecting the traffic information or determining whether the traffic is suddenly dropped comprises: collecting the traffic information by a network management unit of the fault detection system; And transmitting the traffic information to the fault detection unit of the fault detection system.

The step of collecting the test result or the step of discriminating whether or not the fault has occurred may be performed by the fault detecting unit, and the step of determining whether the fault has occurred may further include the step of the fault detecting unit transmitting the determination result to the network managing unit .

Wherein the step of controlling the network device includes the steps of: designating any one of the network devices interconnected by the failure detection unit as a host and designating another network device as a target; And the failure detecting unit controls the host to perform the test on the up-market target so that the test is performed.

The network management unit selecting the network device; And the network management unit is configured to be a host and set the selected network device as a target, and proceeding with the test.

The network device is a router and the test is performed on the L3 interface of the router.

The fault detection system of the network equipment and the fault detection method using the same according to the present invention periodically test whether a fault has occurred between the IP network equipment to judge the occurrence of the fault and, in addition, , It is possible to quickly and accurately detect and respond quickly to traffic fluctuations due to faulty devices, intervals, and faults.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an exemplary diagram showing a relationship between a fault detection system and a network according to the present invention; FIG.
FIG. 2 is a diagram illustrating a configuration of a fault detection unit according to the present invention in more detail; FIG.
3 is an exemplary diagram illustrating a second ping test performed by the present invention;
4 is a flowchart showing a fault detection method using the fault detection system according to the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. It should be noted that the drawings denoted by the same reference numerals in the drawings denote the same reference numerals whenever possible, in other drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. And certain features shown in the drawings are intended to be illustrative, not limiting, or reduced, or simplified, and the drawings and elements thereof are not necessarily drawn to scale. However, those skilled in the art will readily understand these details.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram illustrating the relationship between a fault detection system and a network according to the present invention; FIG.

Referring to FIG. 1, a fault detection system 10 according to the present invention includes a network management unit 11 connected to a network device 90 (90a, 90b, 90c) for acquiring operation information of the equipment, And a fault detection unit 15. The fault detection unit 15 detects a fault.

The failure detection system 10 confirms the operation status of each of the network devices 90 using the obtained operation status information requested by the network device 90 and provides them to the administrator. The failure detection system 10 periodically or non- The network device 90 controls each network device 90 to perform a test or a test for checking the operation status of the network device 90 and determines whether or not a failure has occurred in the network device 90 according to a result of the test. That is, the fault detection system 10 performs a status check, a test for detecting a fault, and a fault determination using a test result. Here, the operation status information includes traffic processing information of each network device 90. [ The failure detection system 10 collects the operation status and performs status monitoring for extracting the amount of traffic per hour whether or not the network device is operating normally. Then, the fault detection system 10 performs a test of the network device 90 through a ping test.

The ping test performed by the fault detection system 10 is based on a first ping test in which the fault detection system 10 targets the network device 90 and a second ping test in which a network device 90 is targeted to another network device 90 As shown in FIG. Particularly, in the case of the second ping test, it is divided into a periodic test and a real-time test. Specifically, the first ping test is performed when the fault detection system 10 becomes the host, and any one of the network devices 90 selected by the fault detection system 10 is targeted and receives a datagram from the fault detection system 10. [ Is delivered to the network device 90, and the target network device 90 responds thereto. On the other hand, the second ping test is performed by the failure detection system 10 remotely controlling one of the network devices 90 as a host and the other as a target to be performed between the devices. Then, the test is performed by receiving the ping test result from the network device 90 designated as the host by the fault detection system 10. This will be described in more detail below.

For this purpose, the fault detection system 10 includes a network management unit 11 and a fault detection unit 15.

The network management unit 11 collects operation state information including traffic information for each network device 90 and provides the traffic information among the collected operation state information to the failure detection unit 15. [ The network management unit 11 receives the failure detection information from the failure detection unit 15 and provides the failure detection information to the manager. The network management unit 11 may perform a test on the network device 90 different from the failure detecting unit 15 and the first ping test may be executed by the network management unit 11. However, The invention is not limited thereto. That is, the network management unit 11 transmits a datagram for ping test to each of the network devices 90 by a predetermined period or condition, receives the response of the network device 90 to the datagram, ) Can be identified and identified.

The failure detection unit 15 performs a test for detecting a failure of the network device 90 and detects the occurrence of a failure of the network device 90 through a test result. To this end, the failure detector 15 performs a second ping test on the network device 90, and determines whether the failure has occurred according to the result of the second ping test. The failure detection unit 15 may perform a standard second ping test performed according to a predetermined period or condition and a real time second ping test performed on a small number of network devices 90. [ In particular, in this process, the failure detector 15 can perform the second ping test in real time based on the traffic information provided from the network management unit 11. [ In addition, the failure detection unit 15 detects connection information between each network device 90, in particular, a device type of a section in which a second ping test is to be performed, , Connection information such as the connection relationship between the device and other devices can be collected.

The failure detection unit 15 selects a connection interval to be tested according to the connection information and specifies a network device 90 of a selected connection interval as a host and a network device 90 as a target of a ping test And transmits the test command to the host network device 90 so that the test command is transmitted. Then, the ping test result transmitted from the host apparatus is received, and the ping test result is compared with a long criterion in advance to determine whether or not a failure has occurred, and the determination result is transmitted to the network management unit 11.

In particular, the failure detection unit 15 receives the traffic information for the network device 90 from the network management unit 11, selects a network device and a section requiring real-time second ping test, and performs a test. That is, when the failure detection unit 15 detects a drop in the operation state that may be caused when a failure occurs, such as a packet forwarding failure such as a traffic decrease in the specific network device 90, a rapid loss rate, The second ping test target device is selected. Then, the failure detector 15 performs a second ping test successively for a predetermined number of times, a time interval, and a test period with respect to the network device 90 as the selected target device, thereby determining whether or not a collection failure has occurred.

This will be described in more detail below with reference to separate drawings.

FIG. 2 is a configuration diagram showing a configuration of a fault detection unit according to the present invention in more detail.

2, the fault detector 15 includes a connection information collection module 151, a test command generation module 152, a traffic drop determination module 153, a result inquiry module 154, An interface module 155, an ENP interworking module 156, and an information storage module 157.

The connection information collection module 151 collects connection information of a target to be detected by the failure detection unit 15. That is, the connection information collection module 151 collects the connection information between the network devices 90, that is, the connection information between the network devices 90 to be subjected to the second ping test. Specifically, in the second ping test, a network device 90 transmits a datagram for ping test to another network device 90 connected to the network device 90 by a test command generated by the test command generation module 152 And another network device 90 responds thereto. Therefore, the connection information collection module 151 collects connection information such as an IP address, a target module to which a second ping test is to be performed, and the like between the network devices 90 in which the second ping test can be performed. This will be described in more detail with reference to FIG.

The test command generation module 152 selects the network device 90 to perform the second ping test and generates a test command for performing the second ping test of the selected network device 90, . Specifically, the test command generation module 152 selects the target network device 90 to perform the second ping test according to a predetermined condition or cycle. The test command generation module 152 generates a test command based on the connection information of the network device 90 connected to the selected network device 90 according to the connection information collected by the connection information collection module 151, And generates a test command to perform a ping test. Then, the test command generation module 152 transmits the created test command to the target network device 90. In particular, the test command generation module 152 generates a command for the real-time second ping test for the designated object, that is, the network device 90, from the traffic drop determination module 153 in addition to the period or condition described above, (90). In particular, the test command for the real-time second ping test is transmitted to the second ping test in accordance with the condition, time, frequency, and period specified by the control of the traffic-drop determination module 153 or the traffic- Different periods, times, and times at which the test is performed are performed differently. The result of the second ping test performed in the network device 152 by the test command generation module 152 is transmitted to the result query module 154. [

The traffic drop determination module 153 determines whether the traffic is rapidly dropped to classify a device that is not detected by the network management unit 11, that is, a device that is likely to fail, such as a packet forwarding failure, And requests the command generation module 152 to proceed with the test. Specifically, the traffic drop determination module 153 confirms packet movement, that is, traffic fluctuation, between each network device 90 based on the connection information collected by the connection information collection module 151. In particular, the traffic drop determination module 153 compares the current traffic with the previous traffic condition using the traffic trend information stored in the network management module 11 or the information storage module 157 to determine whether the traffic has plummeted. Specifically, the traffic drop determination module 153 compares the current traffic with the previous traffic data according to the day of the week, the time zone, and the date, so that the current traffic has significantly decreased, the traffic of the previous few days, Whether or not the amount of traffic has decreased compared to the amount of traffic in the same day of the week or the same time in the past. Also, in this process, the traffic drop determination module 153 may compare the upload packet and the download packet. In other words, the upload traffic is similar to the existing traffic volume, but if the download traffic is greatly reduced, or if the traffic is continuously decelerating, the traffic is determined to be plummeting. If it is determined that the traffic has plummeted due to the above-described comparison, the traffic drop determination module 153 transmits the information on the target device and the device connected to the target device to the test command generation module 152, . At this time, only the identifier such as the network device name or ID to be checked in the real-time second ping test is transmitted to the test command generation module 152 by the traffic drop determination module 153, The IP address of the interface, the interface of the other device connected thereto, and the IP address of the interface. Alternatively, the information may be collected from the connection information collection module 151 and transmitted to the test command generation module 152, but the present invention is not limited thereto.

The result inquiry module 154 collects the test results performed in the network device 90 by the test command generation module 152. [ The command generated by the test command generation module 152 is passed to the network device 90 and the network device 90 performs a second ping test with the other network device 90 connected by the command, . The network device 90 transmits the collected result to the failure detector 15. The failure detector 15 receives a report from the network device 90 that the test is completed and the result is collected, The result inquiry module 154 receives the test result from the network device 90 when the network device 90 intends to deliver the result to the failure detection unit 15. [ Particularly, the result inquiry module 154 determines the presence or absence of data to be preferentially processed, such as the traffic state and the load factor of the network device 90 on which the test has been performed. When the data processing performance is not degraded, ), But the present invention is not limited thereto. The result inquiry module 154 transfers the collected test results to the failure determination module 155 and the information storage module 157.

The failure judgment module 155 judges whether a failure such as a packet forwarding failure has occurred by using the test result collected by the result inquiry module 154. [ For example, the failure determination module 155 determines whether the datagram is transmitted and responded to the ping test and the success rate of the datagram transmission and response based on the test result, The occurrence of a failure in the connection section between the devices is judged. For this, the failure determination module 155 is predetermined by the administrator, and the failure criteria for failure determination such as the lower limit success rate for comparison with the success rate can be stored. In addition, the failure criteria may be stored and managed in the information storage module 157, but the present invention is not limited thereto. The failure determination module 155 transmits the failure determination result to the information storage module 157 and the EMI interlock module 156.

The AMP interworking module 156 transmits the failure determination result provided by the failure determination module 155 to the network management unit 11. [

The information storage module 157 stores the connection information collected by the connection information collection module 151, the test results collected by the result query module 154, the fault determination result generated by the fault determination module 155, Various kinds of information by the operation and the test of the network device 90 are stored as the result of the traffic drop determination made by the module 153, and the information is provided to the required configuration.

3 is an exemplary diagram illustrating a second ping test performed by the present invention.

Referring to FIG. 3, the network device 90 may include devices such as routers and hubs for connecting various servers, servers, and customer's terminal devices.

In particular, a router is a very important component for connection and data transmission between a server and a customer's terminal device, and can be configured in multiple stages such as a backbone router, an edge router, and a customer router. These routers relay data by connecting the customer's router or the customer's equipment with the server, and the connection is made by wire or optical cable. In particular, recently, they are connected through optical modules for high-speed and high-capacity data processing.

3, the first router 91 may be a backbone router, and the second router 92 may be an edge router, for example, two routers of the network device 90. For example, as shown in FIG.

These routers 91 and 92 are composed of an optical module, an L3 module and a switch fabric as shown in the figure. More specifically, the routers 91 and 92 include first optical modules 91b and 92b, a first L3 module 91c and 92c, a switch fabric 91d and 92d, a second L3 module 91e and 92e, And optical modules 91f and 92f. The optical modules 91b, 92b, 91f and 92f are connected to optical cables for connection with other devices and are terminals for inputting or outputting data packets. The data packet input or output through the optical modules 91b, 92b, 91f and 92f is transmitted from the L3 modules 91c, 92c, 91e and 92e at the previous stage to the optical modules 91b, 92b, 91f and 92f, Modules 91b, 92b, 91f, and 92f to the L3 modules 91c, 92c, 91e, and 92e. This data packet includes a switch fabric located between the first optical module and the first L3 modules 91b, 91c, 92b and 92c, the second optical module and the second L3 modules 91e, 91f, 92e and 92f, The data packets are exchanged by the CPUs 91a and 92a, and the processing of these data packets is controlled by the CPUs 91a and 92a.

In the network device 90 configured as described above, in addition to collecting the operation status information of the network device 90 from the network device 90, the network management unit 11 performs a first ping test as described above It is determined whether or not the network device 90 is abnormal. In the first ping test, the network management unit 11 becomes the host, and the network device 90, for example, the routers 91 and 92 becomes the target device, Lt; RTI ID = 0.0 > 91, < / RTI > That is, in the first ping test, if any abnormality occurs in any device, line, or the like between the network management unit 11 and the target device, the normal test is not performed. Accordingly, the network management unit 11 , It is impossible to check which equipment has failed.

On the other hand, the second ping test is performed to check whether there is a failure between the network device 90 specified by the failure detector 15 and the network device 90 connected thereto. 3, when the failure detecting unit 15 commands the first router 91 to perform a second ping test to confirm the connection status with the second router 92, the first router 91 transmits a second ping test And the ping test is performed using the router 92 as a target. In other words, it is possible to accurately detect the section in which the abnormality occurs, by performing the short interval between the first router 91 and the second router 92, and the interval without the intervention of the other apparatus.

Particularly, since the ping test is performed in units of the L3 modules 91c, 91e, 92c and 92e having the IP addresses among the interfaces constituting the routers 91 and 92, it is possible to detect a fault in a specific part. For example, in the case of FIG. 3, a second ping test may be performed between the second L3 module 91e of the first router 91 and the first L3 module 92c of the second router 92. Specifically, when the first router 91 instructs the CPU 91a of the first router 91 to execute the ping test, the failure detection unit 15 detects that the CPU of the first router 91 is the second L3 module The first optical module 92b of the second router 92 and the first optical module 92b of the second router 92. The first optical module 91b transmits the datagram to the second router 91 via the optical network 91e, 92c to the second router 92, and the second lane 92 is responded in the reverse order, and the second ping test is performed.

When a failure is detected in such a test, the administrator can accurately recognize that there is a failure between the first router 91 and the second router 92, thereby enabling quick action. Particularly, when a failure of the module is not reported to the failure detection unit 15 in each of the routers 91 and 92, a failure occurs in the optical cable connecting the second optical module 91f and the second optical module 92b It is possible to compress the cause of the fault by connecting the optical cable and the optical modules 91f and 92b, thereby enabling accurate and quick response.

That is, by performing the ping test of each interface or module of each network device 90, accurate and rapid failure detection and rapid response can be achieved, thereby preventing degradation of service quality.

4 is a flowchart showing a fault detection method using the fault detection system according to the present invention.

Referring to FIG. 4, a fault detection method according to the present invention includes a traffic information collection step S10, a traffic information delivery step S20, a traffic surplus determination step S30 and S40, a network device control step S50, (S60) and a determination result delivering step (S70).

The traffic information collection step (S10) is a step in which traffic information about the network device 90 is collected by the network management unit 11. The traffic information collection step (S10) continues during the operation of the network management unit 11, and traffic information for each network device 90 is collected periodically or in real time. At this time, in addition to the traffic information, information necessary for the progress of the real-time second ping test can be collected as the operation status information, and the present invention is not limited to the traffic information alone.

The traffic information delivery step S20 is a step in which the network management unit 11 delivers the collected traffic information to the traffic drop determination module 153 of the failure detection unit 15. [ The network management unit 11 transmits the collected traffic information to the traffic drop determination module 153 when the collected traffic information is in a real-time or a predetermined period or in a condition consistent with a predetermined condition. In particular, in the traffic information transmission step S20, the network management unit 11 may transmit the operation state information other than the traffic information to the traffic drop determination module 153 together with the traffic information, but the present invention is not limited thereto.

In the steps S30 and S40, the traffic drop determination module 153 receives the operation status information including the traffic information from the network management unit 11, and determines whether the traffic drop has occurred using the traffic information to be. In the traffic sudden drop determination step S30, the traffic drop determination module 153 compares the data with the existing data to determine whether a drop in traffic has occurred. That is, in the traffic sudden drop determination step S30, the traffic drop determination module 153 compares the previous data with a similar situation, for example, the day of the week, the time zone, the holiday, and the month, , Traffic of the uplink or downlink is compared to determine whether the traffic has changed greatly. Specifically, the traffic drop determination module 153 determines that the uplink traffic has little change when compared with the previous data, whereas the downlink is determined to be a traffic fall when the amount of traffic is significantly reduced compared to the amount of traffic identified in the previous traffic data. At this time, in the traffic sudden drop determination step S30, the traffic drop determination module 153 transmits the determination result to the test command generation module 152. [

On the other hand, the connection information collection step precedes the network device control step (S50) for testing. The connection information collection step is a step in which connection information of the network device 90 is collected by the connection information collection module 151 of the failure detection unit 15. [ In this traffic information collection step (S10), information of an object to which a ping test can be performed, that is, an interface of a device or a device, in particular, an object to which an IP address is assigned, is collected. In this traffic information collection step S10, the connection information collection module 151 collects connection information for the network device 90 and transmits the collected connection information to the test command generation module 152 or the information storage module 157 .

The network device control step S50 is a step in which the test command generation module 152 of the failure detection unit 15 selects the network device 90 for failure detection and controls the network device 90 so that the selected network device 90 performs the test . In this network device control step (S50), the test command generation module 152 selects the network device 90 to which the second ping test is to be executed, and causes the selected ping test to execute the second ping test Command. In the network device control step S50, the network device 90 that has received the execution command of the second ping test performs the second ping test according to the instruction.

In particular, the network device control step S50 may include a standard second ping test that is executed periodically or when a certain condition is met, a network device 90 that detects a failure such as a traffic jam by the operation status information, And a real-time second ping test performed on the real-time second ping test. More specifically, if the network device 90 in which a traffic surge has occurred is not detected in a general situation, a standard second ping test execution step S51 is performed. The step S51 of performing the standard second ping test may be performed on the network device 90 at regular intervals. In particular, in this case, it is possible to execute the condition by delaying the second ping test periodically executed when the network device 90 is processing a predetermined amount of traffic or the like. When the second ping test is performed, several tens to several hundreds of datagrams are transmitted, and a response is made. Therefore, when the second ping test is executed, the load of the network device 90 increases, which may affect the traffic processing performance. Therefore, in the standard second ping test execution step S51, the traffic processing status of the network device 90 is checked and the test is performed.

In the case where the amount of traffic processing of the specific network device 90 significantly decreases in the traffic dropping determination steps S30 and S40 or a symptom of a failure occurrence is determined in the process of determining through the operation status information, (S52) proceeds. This real-time second ping test is for detecting the occurrence of a failure, and unlike the standard second ping test, it proceeds irrespective of the traffic processing amount of the network device 90. Also, a test environment such as a time period during which a real-time second ping test is performed, a test period, and a test count may be set differently from a standard second ping test. For example, assuming that the standard second ping test receives 100 datagram transmissions and responses over 10 minutes at 6 hour intervals for a particular network device 90 and measures the loss rate, the real-time second ping test immediately tests And receives 1000 datagram transmissions and responses for 30 minutes, and measures the loss rate and response time. That is, the real-time second ping test can test for a longer time or more times or more frequently than the standard second ping test for accurate fault detection and learn more measurable parameters besides the loss rate, But is not limited to.

The fault occurrence determination step S60 is a step of collecting the results of the test executed in the network device control step S50 and determining whether a failure has occurred in the network device 90 on which the test is performed. To this end, in the fault occurrence determination step S60, the result inquiry module 154 requests the test result to the network device 90 that has been tested, receives the test result, and transmits the received test result to the fault determination module 155 do. Particularly, in the fault occurrence determination step S60, the result inquiry module 154 provides the test result to the information storage module 157, and the information storage module 157 can store and manage the test result, The invention is not limited thereto. The failure determination module 155 provided with the test result determines whether the loss rate of the datagram according to the test result is equal to or higher than a predetermined reference level or whether the time required for the response exceeds the reference level, It is determined that the network device 90 has failed.

In the determination result delivering step S70, the failure determining module 155 receives the failure occurrence discriminated in the failure occurrence determining step S60, and transmits it to the network managing unit 11 . Then, the network management unit 11 outputs the failure occurrence and test information to the user, thereby detecting the failure.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, . ≪ / RTI > Accordingly, such modifications are deemed to be within the scope of the present invention, and the scope of the present invention should be determined by the following claims.

10: Fault detection system 11: Network management unit
15: fault detection unit 90: network device
151: connection information collection module 152: test command generation module
153: Traffic drop determination module 154: Result query module
155: Failure determination module 156: NMP interworking module
157: Information storage module

Claims (18)

A fault detection system for detecting a fault in a network device,
A network management unit for collecting real-time traffic information on a network; And
The network device collects connection information on the network, identifies a connection section in which a traffic plagued based on the collected traffic information and connection information, instructs a network device corresponding to the identified connection section to perform a real- A failure detector for collecting the test result from the network device and determining a failure occurrence in the identified connection section;
And a fault detection system. The method according to claim 1,
Wherein the real-time test is a ping test. 3. The method of claim 2,
Wherein the failure detection system further performs a standard test progressing according to a preset condition or cycle when the traffic plunge does not occur, wherein the real-time test includes at least one of a condition for performing the standard test, a test execution cycle, And at least one of the test progress times is set differently. delete The method according to claim 1,
And the failure detection unit transmits the determination result to the network management unit. 3. The method of claim 2,
The failure detection unit
Wherein the host computer selects one of the network devices included in the identified connection section as a host and controls the selected host to perform the ping test on another network device included in the identified connection section, A fault detection system for transmitting to a selected host. The method of claim 3,
Wherein the network management unit performs a ping test by setting one of the network devices as a target and becoming a host when the traffic drop does not occur. The method of claim 3,
Wherein the network device is a router,
Wherein the standard test and the real-time test are performed on the L3 interface of the router. The method according to claim 6,
The failure detection unit
A result query module for collecting test results for the ping test from the host;
An information storage module for storing the collected test results and failure judgment reference information;
A failure determination module that determines whether a failure has occurred in the connection section based on the collected test result and the failure determination reference information; And
A network management module for transmitting a failure determination result by the failure determination module to the network management module,
And a fault detection system. A method for detecting a fault in a fault detection system coupled to a network device,
Collecting traffic information and connection information on the network;
Identifying a connection interval in which a traffic plunge has occurred based on the collected traffic information and connection information;
Transmitting a command for real-time testing to a network device corresponding to the identified connection section; And
Collecting a test result corresponding to the command from the network device and determining whether a failure has occurred in the identified connection section
/ RTI > 11. The method of claim 10,
Wherein the real-time test is a ping test. 12. The method of claim 11,
Wherein the real-time test is performed in at least one of a standard test, a condition, a cycle, a number of times of testing per time, and a test progress time, and the standard test is performed when the connection interval in which the traffic plunge occurs is not identified Fault detection method. delete delete delete 12. The method of claim 11,
The step of determining whether or not a failure has occurred in the identified connection section
Designating any one of the network devices included in the identified connection section as a host and designating a remaining network device included in the identified connection section as a target;
Controlling the host to perform the real-time test on the target;
Receiving a test result for the real-time test from the host; And
Determining whether a failure has occurred in the identified connection section based on the test result
The fault detection method comprising: 13. The method of claim 12,
Setting a fault detection system as a host and setting a network device connected to the network as a target, and then performing a ping test on the set target if the connection interval in which the traffic drop has occurred is not identified The fault detection method comprising the steps of: 13. The method of claim 12,
Wherein the network device is a router,
Wherein the standard test and the real-time test are performed on the L3 interface of the router.

Images