CN110708207A

CN110708207A - Route oscillation positioning method, server and machine readable storage medium

Info

Publication number: CN110708207A
Application number: CN201811585124.5A
Authority: CN
Inventors: 杨帜; 石翔
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2018-12-24
Filing date: 2018-12-24
Publication date: 2020-01-17
Anticipated expiration: 2038-12-24
Also published as: WO2020135445A1; CN110708207B

Abstract

The invention provides a routing oscillation positioning method, a server and a machine readable storage medium, wherein the method comprises the following steps: pre-detecting the equipment to be detected to determine target equipment meeting the detection condition of the oscillation route; performing oscillation route detection on the target equipment to determine whether an oscillation route exists; for any one target device, when an oscillation route exists on the target device, determining an oscillation source of the oscillation route, and determining an oscillation reason. The embodiment of the invention can realize route oscillation positioning.

Description

Route oscillation positioning method, server and machine readable storage medium

Technical Field

The present invention relates to the field of network communication technologies, and in particular, to a routing oscillation positioning method, a server, and a machine-readable storage medium.

Background

The core of the internet for realizing the interconnection of everything lies in that the network equipment realizes message forwarding, and the normal forwarding of the network equipment lies in the stability and integrity of the routing table. If the entries in the routing table vibrate, the problems of packet loss, low speed and the like in the forwarding process from the source device to the destination device can be caused; the traffic is in a state of stagnation, and the loss is difficult to measure.

Therefore, when a routing oscillation occurs, how to implement the routing oscillation positioning becomes an urgent problem to be solved.

Disclosure of Invention

The invention provides a routing oscillation positioning method, a server and a machine readable storage medium, which are used for solving the problem that the routing oscillation positioning cannot be realized at present.

According to a first aspect of the embodiments of the present invention, a method for positioning routing oscillation is provided, including:

pre-detecting the equipment to be detected to determine target equipment meeting the detection condition of the oscillation route;

performing oscillation route detection on the target equipment to determine whether an oscillation route exists;

for any one target device, when an oscillation route exists on the target device, determining an oscillation source of the oscillation route, and determining an oscillation reason.

With reference to the first aspect, in a first possible implementation manner, the pre-detecting the device to be detected to determine the target device meeting the oscillation route detection condition includes:

polling the device to be detected according to the polling time interval of the device to be detected;

for any equipment to be detected, when detecting that the number of the routing table entries of the equipment to be detected changes, subtracting a first preset time from the polling time interval of the equipment to be detected;

and when the polling time interval of the equipment to be detected is equal to the preset trigger detection time, executing the step of performing oscillation route detection on the target equipment.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the polling the device to be detected according to the polling time interval of the device to be detected includes:

subtracting the second preset time from the residual detection time of the equipment to be detected every second preset time;

and when the residual detection time of the equipment to be detected is less than or equal to 0, performing pre-detection on the equipment to be detected, and setting the residual detection time of the equipment to be detected as the polling time interval of the equipment to be detected.

With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner, the initial values of the remaining detection times of different devices to be detected are not completely the same.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the initial value of the remaining detection time of the device to be detected is determined by the following formula:

Ti＝DevIDi％T0

wherein Ti is an initial value of the residual detection time of the equipment i to be detected, i is more than or equal to 1 and less than or equal to N1, N1 is the number of the equipment to be detected, DevIDi is an equipment identifier of the equipment i to be detected, T0 is a maximum polling time interval, and percent is a remainder operation.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, the method further includes:

and for any equipment to be detected, adding a third preset time to the polling time interval of the equipment to be detected when N2 times of continuous detection that the number of the routing table entries of the equipment to be detected is not changed until the polling time interval of the equipment to be detected reaches the maximum polling time interval.

With reference to the first aspect, in a sixth possible implementation manner, the performing oscillation route detection on the target device includes:

and when determining that a plurality of target devices exist, sequentially carrying out oscillation route detection on the target devices.

With reference to the first aspect or the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner, the performing oscillation route detection on the target device includes:

for any target equipment for oscillation route detection, determining whether oscillation routes exist on the target equipment according to the routing information of the target equipment;

wherein the routing information comprises a destination address and a routing table entry occurrence time.

With reference to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner, the determining, according to the route information of the target device, whether an oscillating route exists on the target device includes:

polling the routing table of the target device for N3 times according to the routing information collection time interval to collect the routing information;

for any routing table entry, when the oscillation frequency of the routing table entry is greater than or equal to a first preset oscillation frequency threshold value, executing a step of determining an oscillation source of the oscillation route;

or, when the oscillation times of the routing table entries are smaller than a first preset oscillation time threshold and the total time of the routing table entries is smaller than a first preset time threshold, executing the step of determining the oscillation source of the oscillation route;

when a routing table entry is from the existence to the nonexistence or from the nonexistence to the existence, the oscillation frequency of the routing table entry is added with 1.

With reference to the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner, the route information collection time interval is increased or decreased as the number of times of route information collection that has been completed increases.

With reference to the first aspect, in a tenth possible implementation manner, the determining an oscillation source of the oscillation route includes:

for any oscillation route, judging whether the oscillation route is a direct route of the target equipment;

if so, determining the target equipment as an oscillation source of the oscillation route;

otherwise, determining the oscillation source of the oscillation route according to the routing protocol information corresponding to the oscillation route.

With reference to the tenth possible implementation manner of the first aspect, in an eleventh possible implementation manner, the determining, according to the routing protocol information corresponding to the oscillating route, an oscillating source of the oscillating route includes:

judging whether the routing protocol table entry corresponding to the oscillation route is in an oscillation state;

if so, after the current target equipment completes detection, oscillation route detection is carried out on the publisher equipment included in the route protocol table entry in the oscillation state until an oscillation source of the oscillation route is determined;

if not, executing the step of determining the oscillation reason.

With reference to the eleventh possible implementation manner of the first aspect, in a twelfth possible implementation manner, the method further includes:

for any target device, polling the routing protocol table of the target device for N4 times according to the routing protocol information collection time interval to collect the routing protocol information; the routing protocol information comprises a destination address and the appearance time of an entry of a routing protocol table;

for any routing protocol table entry, when the oscillation frequency of the routing protocol table entry is greater than or equal to a second preset oscillation frequency threshold, executing a step of performing oscillation route detection on publisher equipment included in the routing protocol table entry in an oscillation state after the current target equipment completes detection;

or, when the oscillation times of the routing protocol table entry are smaller than a second preset oscillation times threshold value and the total time of the routing protocol table entry is smaller than a second preset time threshold value, executing a step of performing oscillation route detection on the publisher equipment included in the routing protocol table entry in the oscillation state after the current target equipment completes detection;

when a routing protocol table entry is from the existence to the nonexistence or from the nonexistence to the existence, the oscillation frequency of the routing protocol table entry is added with 1.

With reference to the twelfth possible implementation manner of the first aspect, in a thirteenth possible implementation manner, the routing protocol information collection time interval increases or decreases as the number of completed routing protocol information collections increases.

With reference to the first aspect, in a fourteenth possible implementation manner, the determining a cause of oscillation includes:

collecting the oscillation phenomenon of the oscillation source;

and determining the oscillation reason according to the oscillation phenomenon of the oscillation source.

With reference to the fourteenth possible implementation manner of the first aspect, in a fifteenth possible implementation manner, the determining a cause of oscillation according to an oscillation phenomenon of the oscillation source includes:

and inquiring the corresponding relation between the preset oscillation phenomenon and the oscillation reason according to the oscillation phenomenon of the oscillation source so as to determine the oscillation reason matched with the oscillation phenomenon of the oscillation source.

According to a second aspect of the embodiments of the present invention, there is provided a server, including a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-readable instructions executable by the processor, and the processor is caused by the machine-readable instructions to execute the above-mentioned routing oscillation positioning method.

According to a third aspect of embodiments of the present invention, there is provided a machine-readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to perform the above-mentioned routing shock localization method.

By applying the embodiment of the invention, the target equipment meeting the oscillation route detection condition is determined by pre-detecting the equipment to be detected, the oscillation route detection is carried out on the target equipment, whether the oscillation route exists or not is determined, and for any target equipment, when the oscillation route exists on the target equipment, the oscillation source of the oscillation route is determined, the oscillation reason is determined, and the route oscillation positioning is realized.

Drawings

Fig. 1 is a schematic flow chart illustrating a routing oscillation positioning method according to an embodiment of the present invention;

fig. 2A is a schematic flow chart illustrating another routing oscillation positioning method according to an embodiment of the present invention;

fig. 2B is a schematic flowchart of another routing oscillation positioning method according to an embodiment of the present invention;

fig. 2C is a schematic flow chart of another routing oscillation positioning method according to an embodiment of the present invention;

fig. 2D is a schematic flowchart illustrating a method for positioning an oscillation source according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a route information collection time interval and a route oscillation period according to an embodiment of the present invention;

fig. 4 is a schematic diagram illustrating a correspondence relationship between an oscillation phenomenon and an oscillation reason according to an embodiment of the present invention;

fig. 5 is a schematic flowchart of a routing oscillation positioning method according to an embodiment of the present invention;

fig. 6 is a schematic flowchart of a process of polling a device to be detected by a network management platform according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a wait for detection queue according to an embodiment of the present invention;

fig. 8 is a schematic flow chart illustrating information collection of an oscillation route according to an embodiment of the present invention;

fig. 9 is a schematic hardware structure diagram of a server according to an embodiment of the present invention;

fig. 10 is a functional structure diagram of a routing oscillation positioning control logic according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions in the embodiments of the present invention better understood and make the above objects, features and advantages of the embodiments of the present invention more comprehensible, the technical solutions in the embodiments of the present invention are described in further detail below with reference to the accompanying drawings.

Referring to fig. 1, a flow diagram of a routing oscillation positioning method according to an embodiment of the present invention is provided, where the routing oscillation positioning method may be applied to a network management platform, for example, a server running a specific network management software, and as shown in fig. 1, the routing oscillation positioning method may include:

step 101, pre-detecting the device to be detected to determine a target device meeting the oscillation route detection condition.

In the embodiment of the present invention, it is considered that routing oscillation generally involves more network devices, and routing information on each network device is also generally more, and if routing oscillation occurs, the oscillation route is directly located by analyzing all routing information of all network devices, so that workload is very large and efficiency is very low, and therefore, in order to improve the efficiency of routing oscillation location and reduce workload of routing oscillation, when routing oscillation location is required, pre-detection may be performed on a device to be detected first to screen out a device to be detected (referred to as a target device herein) that meets the detection condition of the oscillation route.

In an embodiment of the present invention, in the step 101, the pre-detecting the device to be detected to determine the target device meeting the oscillation route detection condition, as shown in fig. 2A, may include:

step 1011, polling the equipment to be detected according to the polling time interval of the equipment to be detected;

step 1012, for any device to be detected, when detecting that the number of the routing table entries of the device to be detected changes, subtracting a first preset time from the polling time interval of the device to be detected;

and 1013, when the polling time interval of the device to be detected is equal to the preset trigger detection time, executing the step of performing oscillation route detection on the target device.

Specifically, in this embodiment, the network management platform may perform pre-detection on the device to be detected in a polling manner.

Correspondingly, the polling time interval of each device to be detected can be preset (namely, the corresponding device to be detected is subjected to pre-detection every the polling time interval), and the network management platform can perform pre-detection on the corresponding device to be detected according to the polling time interval of each device to be detected.

Wherein the polling time intervals of different devices to be tested may be different.

Of course, the polling intervals of the devices to be tested can also be the same. For example, the network management platform may perform pre-detection on each device to be detected every 30 seconds (i.e., the polling time interval of each device to be detected is 30 seconds).

In this embodiment, the pre-detecting, by the network management platform, the device to be detected may include obtaining the number of the routing entries of the device to be detected, and determining whether the number of the routing entries of the device to be detected changes, that is, whether the number of the routing entries of the device to be detected obtained this time (not for the first time) is the same as the number of the routing entries to be detected obtained last time, and when the network management platform determines that the number of the routing entries of the device to be detected changes, subtracting a preset time (referred to as a first preset time herein, which may be set according to an actual scene, for example, 3 seconds, 5 seconds, and the like) from the polling time interval of the device to be detected.

When the network management platform acquires the number of the routing entries of a certain device to be detected for the first time, the network management platform can only record the number of the routing entries without judging whether the number of the routing entries of the device to be detected changes.

In this embodiment, for any device to be detected, when the polling time interval of the device to be detected is equal to the preset trigger time detection time (which may be set according to an actual scene, such as 15 seconds, 20 seconds, and the like), the network management platform may determine that the device to be detected meets the oscillation route detection condition, and further, the network management platform may determine that the device to be detected is the target device, and perform step 102, that is, perform the step of performing oscillation route detection on the target device.

It should be appreciated that, in the embodiment of the present invention, the determining whether the device to be detected satisfies the oscillating route detection condition according to the polling time interval of the device to be detected is only a specific example of determining whether the device to be detected satisfies the oscillating route detection condition in the embodiment of the present invention, and is not limited to the scope of the present invention.

Further, in the embodiment of the present invention, in order to avoid that the network management platform constantly monitors whether each device to be detected needs to perform the pre-detection in real time, the network management platform may determine whether each device to be detected needs to perform the pre-detection at regular intervals (referred to as a second preset time herein, which may be set according to an actual scene, such as 3 seconds, 5 seconds, and the like).

Accordingly, in an example, as shown in fig. 2B, the step 1011 polling the device to be detected according to the polling time interval of the device to be detected may include:

10111, subtracting a second preset time from the residual detection time of the device to be detected every second preset time; the initial value of the residual detection time of the equipment to be detected is the initial value of the polling time interval of the equipment to be detected;

step 10112, when the remaining detection time of the device to be detected is less than or equal to 0, performing pre-detection on the device to be detected, and setting the remaining detection time of the device to be detected as the polling time interval of the device to be detected.

For example, assuming that the second preset time is 5 seconds, the network management platform may subtract 5 seconds from the remaining detection time of the device to be detected every 5 seconds.

For any equipment to be detected, when the residual detection time of the equipment to be detected is less than or equal to 0, the equipment to be detected is subjected to pre-detection, and the residual detection time of the equipment to be detected is set as the polling time interval of the equipment to be detected.

For example, taking the device a to be detected as an example, assuming that the initial value of the polling time interval of the device a to be detected is 30 seconds, the remaining detection time is 18 seconds, the first preset time is 5 seconds, the second preset time is 5 seconds, and the preset trigger detection time is 15 seconds, the network management platform may subtract 5 seconds from the remaining detection time of the device a to be detected (sequentially changed to 13 seconds, 8 seconds, 3 seconds, and-2 seconds) every 5 seconds, and when the remaining detection time of the device a to be detected is-2 seconds (less than or equal to 0), the network management platform may perform the pre-detection on the device a to be detected on one hand, and on the other hand, the network management platform may set the remaining detection time of the device a to be detected as the polling time interval of the device a to be detected (30 seconds at this time).

The network management platform may perform pre-detection on the device a to be detected, including: acquiring the number of the routing table entries of the equipment A to be detected, comparing the number of the routing table entries with the number of the routing table entries of the equipment A to be detected acquired last time, and if the number of the routing table entries is the same as the number of the routing table entries of the equipment A to be detected, keeping the polling time interval of the equipment A to be detected unchanged; otherwise, the polling interval of the device a to be tested is subtracted by 5 seconds (i.e. becomes 25 seconds).

Taking the example that the polling time interval of the device a to be detected is changed into 25 seconds, after setting the remaining detection time of the device a to be detected as 30 seconds, the network management platform can subtract 5 seconds from the remaining detection time of the device a to be detected every 5 seconds (sequentially changing into 25 seconds, 15 seconds, 10 seconds, 5 seconds and 0 second); when the remaining detection time of the device a to be detected is 0 (less than or equal to 0) second, the network management platform can set the remaining detection time of the device a to be detected as a polling time interval (i.e., 25 seconds) on one hand, and on the other hand, pre-detect the device a to be detected.

According to the above manner, when the polling time interval of the device a to be detected is 15 seconds, the network management platform may determine that the device a to be detected is the target device, and execute the step of performing oscillation route detection on the target device.

Further, in the embodiment of the present invention, in order to more reasonably utilize the device resources of the network management platform and avoid that the pre-detection of each device to be detected by the network management platform is too concentrated, when the remaining detection time is initially set, the remaining detection time of different devices to be detected may not be completely the same.

For example, the initial value of the remaining detection time of the device to be detected can be determined by the following formula:

Ti＝DevIDi％T0

wherein, Ti is an initial value of the remaining detection time of the device i to be detected, i is greater than or equal to 1 and less than or equal to N1, N1 is the number of the devices to be detected, devidii is a device identifier of the device i to be detected, T0 is a maximum polling time interval (which can be set according to an actual scene, such as 30 seconds), and% is a remainder operation.

It should be noted that, in the embodiment of the present invention, when the initial values of the remaining detection times of the apparatuses to be detected are not completely the same, if the network management platform always determines whether to poll each device to be detected according to the initial value of the remaining detection time of each device to be detected, the frequencies of the pre-detection of the devices to be detected are different, so that the number of times of the pre-detection of the devices to be detected in the same time is more, and the other part of the devices to be detected are detected less times, therefore, in order to avoid the situation that the time for the pre-detection of each device to be detected is too concentrated, the time intervals of the pre-detection of the devices to be detected are kept consistent as much as possible, and the network management platform can set the residual detection time of each device to be detected as a polling time interval after the pre-detection of each device to be detected is carried out according to the initial value of the residual detection time of each device to be detected. The initial values of the polling time intervals of the devices to be detected may be the same, and in the subsequent process, the polling time intervals of the devices to be detected are adjusted according to the change condition of the number of the entries of the routing table of the devices to be detected, and the specific implementation thereof will be described below with reference to specific examples, which are not described herein again in the embodiments of the present invention.

Further, in the embodiment of the present invention, it is considered that the change of the number of routing table entries of the network device is not necessarily caused by the routing oscillation, and may also be caused by a reason configured by a user, for example, the user adds or deletes a route, so that, in order to improve the accuracy of the determined target device meeting the oscillating route detection, for any device to be detected, when the network management platform detects that the number of routing table entries of the device to be detected does not change N2 times continuously, the polling time of the device to be detected is added with a preset time (referred to as a third preset time herein, which may be set according to an actual scenario, for example, 3 seconds, 5 seconds, and the like), until the polling time interval of the device to be detected reaches a preset maximum polling time interval. Wherein the maximum polling interval time can be configured by an administrator according to requirements.

It should be noted that, in the embodiment of the present invention, for any device to be detected, the preset maximum polling time interval may be the same as or different from an initial value of the polling time interval, and this is not limited in the embodiment of the present invention.

Step 102, performing oscillation route detection on the target device to determine whether an oscillation route exists.

In the embodiment of the invention, after the network management platform determines the target equipment meeting the oscillation routing condition by pre-detecting the equipment to be detected, the network management platform can perform oscillation routing detection on the target equipment to determine whether the oscillation routing exists.

In an embodiment of the present invention, as shown in fig. 2C, the step 102 of performing oscillation route detection on the target device may include:

step 1021, for any equipment to be detected, when the equipment to be detected is determined to be target equipment meeting oscillation route detection conditions, adding the target equipment into a waiting detection queue from the tail part;

and step 1022, sequentially performing oscillation route detection on the target devices in the peer-to-peer queue to be detected according to the sequence from the head to the tail of the queue to be detected.

In this embodiment, considering that the number of the routing table entries on one network device may be many, if the network management platform performs oscillation routing detection on multiple network devices at the same time, the network management platform may cause resource pressure overload of the network management platform, and may further cause processing deadlock and even background breakdown, so that, in order to reduce the load of the network management platform and improve the reliability of the network management platform, the network management platform may perform oscillation routing detection on one network device at a time.

Accordingly, in this embodiment, for any device to be detected, when the network management platform determines that the device to be detected is the target device meeting the oscillation route detection condition, the network management platform may add the target device to the waiting detection queue.

When the target device needs to be subjected to oscillation route detection, the network management platform can sequentially take out the target device from the waiting detection queue for oscillation route detection according to the sequence from the head to the tail of the waiting detection queue.

In the embodiment of the present invention, for any target device performing oscillation route detection, the network management platform may determine whether an oscillation route exists on the target device according to the routing information of the target device; the routing information may include a destination address and a routing table entry epoch, among other things.

The destination address is used for identifying the routing table entry, and different destination addresses correspond to different routing table entries.

In an embodiment of the present invention, the determining whether the oscillating route exists on the target device according to the route information of the target device may include:

for any routing table entry, when the oscillation frequency of the routing table entry is greater than or equal to the first preset oscillation frequency threshold, the step of determining the oscillation source of the oscillation route in step 103 is executed.

Or, when the oscillation frequency of the routing table entry is smaller than a first preset oscillation frequency threshold and the total time of the routing table entry is smaller than a first preset time threshold, executing the step of determining the oscillation source of the oscillation route in step 103;

In this embodiment, for any target device, the network management platform may poll the routing table of the target device several times (which may be set according to an actual scenario, for example, N3 times herein) at a certain time interval (referred to as a routing information collection time interval herein and may be set according to an actual scenario) to collect routing information.

In this embodiment, the network management platform may count the oscillation times of each routing table entry on the target device according to the routing information of the target device.

For any routing table entry, when the routing table entry is from the presence to the absence or from the absence to the presence in the routing information of the target device collected twice in the adjacent, the network management platform may add 1 to the oscillation number of the routing table entry.

For example, assume that the network management platform collects routing information of the target device for 5 times, and if the routing table entry a appears from 1 st to 3 th times, does not appear from 4 th time, and appears from 5 th time in the routing information of the target device collected for 5 times, the oscillation frequency of the routing table entry a is 2.

In this embodiment, after determining the oscillation frequency of each routing table entry, the network management platform may determine, as the oscillation route, a route corresponding to the routing table entry whose oscillation frequency is greater than or equal to a preset oscillation frequency threshold (referred to as a first preset oscillation frequency threshold, which may be set according to an actual scene, for example, 2 times, 3 times, and the like), and execute the step of determining the oscillation source of the oscillation route in step 103.

In addition, in this embodiment, considering that when a route oscillation occurs, the time of occurrence of the oscillation route is generally less than a specific time (usually 15 seconds), for a routing table entry whose oscillation frequency is less than the first preset oscillation frequency threshold, it may be further determined whether the corresponding route is the oscillation route according to the time of occurrence of the routing table entry.

Correspondingly, for any routing table entry, when the network management platform determines that the number of oscillations of the routing table entry is smaller than the first preset number threshold of oscillations, the network management platform may further determine a total time of occurrence of the routing table entry, that is, a sum of the occurrence times of the routing table entry in the N3 collected routing information of the target device.

For example, assuming that the route information of the target device is collected 5 times in total, the route table entry b appears in 5 times of collection, and the appearance times of the route table entry b acquired in 5 times of collection are t1 to t5, respectively, the total appearance time of the route table entry b is t1+ t2+ t3+ t4+ t 5.

In this embodiment, when the network management platform determines that the total time of occurrence of the routing table entry is less than a preset time threshold (referred to as a first preset time threshold, which may be set according to an actual scenario), the network management platform may also determine that a route corresponding to the routing table entry is an oscillation route, and perform the step of determining an oscillation source of the oscillation route in step 103.

Further, in the embodiment of the present invention, it is considered that when the route oscillation period is the same as the route information collection time interval, the existing oscillation route may not be detected.

For example, referring to fig. 3, it is assumed that the time length between two square nodes is the route information collection time interval (30 seconds for example), and the time length between the triangle nodes is the route oscillation period (30 seconds for example). At the round node, a certain route disappears due to oscillation, at the triangular node, the route reappears due to oscillation, if the route information collection time interval is always kept to be 30 seconds, because the route oscillation period is the same as the route information collection time interval, the result collected at the node collecting the route information each time is that the route does not exist, and the detected result is that the route does not exist and is not the route oscillation.

To avoid the above problems, the route collection interval may be dynamically changed instead of being kept constant all the time.

Accordingly, in one embodiment of the present invention, the route information collection time interval increases or decreases as the number of route information collections completed increases.

For example, the route information collection interval may be determined by the following equation:

T3＝T2–△T1×N5

wherein, T3 is the currently used route information collection time interval, T2 is the initial route information collection time interval, △ T1 is the first preset decay time, and N5 is the number of completed route information collections.

In this embodiment, a decay time of one routing information collection time interval (referred to as a first preset decay time herein, i.e., the above-mentioned △ T1) may be preset, and when the network management platform performs the routing information collection, the time interval of each routing information collection may be determined according to the preset initial routing information collection time interval and the decay time △ T1.

It should be appreciated that the above implementation manner of updating the routing information collection time interval according to the first preset decay time and the number of times of completed routing information collection is only one specific implementation manner of making the time intervals of multiple times of routing information collection not identical, and is not a limitation to the scope of the present invention, that is, in the embodiment of the present invention, the time intervals of multiple times of routing information collection may not be identical, for example, the routing information collection time interval may be updated according to the preset increase time and the number of times of completed routing information collection (i.e., the routing information collection time interval increases with the increase of the number of times of routing information collection), or a plurality of different routing information collection time intervals may be directly set, and multiple times of routing information collection may be performed according to the plurality of different routing information collection time intervals, the detailed implementation thereof is not described herein.

Step 103, for any target device, when there is an oscillation route on the target device, determining an oscillation source of the oscillation route, and determining an oscillation reason.

In the embodiment of the present invention, it is considered that, under the condition of route oscillation, a plurality of network devices are often in oscillation at the same time, and most of the network devices are in a state of passively causing oscillation. If all the network devices are detected together without priority, the network management device will encounter a bottleneck in performance, and cannot quickly determine the reason causing the route oscillation, so that in order to reduce the load of the network management platform and improve the efficiency of determining the oscillation reason, the detection mode of searching a route oscillation source (namely tracing) can be adopted to realize the route oscillation positioning.

Accordingly, in the embodiment of the present invention, when the network management platform determines that the oscillation route exists, it may determine an oscillation source of the oscillation route, and analyze a cause causing route oscillation from the source.

In an embodiment of the invention, as shown in fig. 2D, the determining the oscillation source of the oscillation route may include:

step 201, for any oscillation route, judging whether the oscillation route is a direct route of the target device; if yes, go to step 202; otherwise, go to step 203.

Step 202, determining the target device as an oscillation source of the oscillation route;

step 203, determining an oscillation source of the oscillation route according to the routing protocol information corresponding to the oscillation route.

The routing Protocol table is a table for recording a route propagated through a certain routing Protocol (e.g., an Open Shortest Path First (OSPF) Protocol, a Border Gateway Protocol (BGP) Protocol, etc.). Specifically, the routing protocol Information may be obtained by collecting a link state database table ospfllsdbtable in an mib (management Information base) of the device to be detected, an externally-introduced link state database table ospfxextlsdbtable, a BGP receive path attribute table BGP4 pathAttribute entry, and the like, and then the oscillation source may be determined according to the routing protocol Information corresponding to the oscillation route.

In this embodiment, when the network management platform determines that an oscillation route exists on a certain target device, for any oscillation route on the target device, the network management platform may determine whether the oscillation route is a direct route of the target device. If so, the network management platform can determine that the target device is an oscillation source of the oscillation route; otherwise, the network management platform may determine an oscillation source of the oscillation route according to the routing protocol information corresponding to the oscillation route.

For any oscillation route, the network management platform may determine whether the oscillation route is a direct route of the target device according to an ipRouteType (route type) field in a route table entry corresponding to the oscillation route.

For example, when the value of ipRouteType is 3, it indicates that the corresponding route is a direct route; otherwise, the route is a non-direct route.

In an example, the determining an oscillation source of the oscillation route according to the routing protocol information corresponding to the oscillation route includes:

if not, the step of determining the oscillation reason in step 103 is executed.

In this example, when the network management platform determines that the oscillation route is not a direct route on the target device, the network management platform may query a routing protocol table entry corresponding to the oscillation route, and determine whether the routing protocol table entry corresponding to the oscillation route is in an oscillation state.

In this example, when the network management platform determines that the routing protocol table entry corresponding to the oscillating route is in an oscillating state, the network management platform may add the publisher device included in the routing protocol table entry of the oscillating state corresponding to the oscillating route to the head of the waiting detection queue.

The detection sequence of the network management platform for the devices in the queue to be detected is from the head to the tail.

After the network management platform completes the detection of the current target device, the oscillation route detection may be performed on the publisher device of the oscillation route until the oscillation source of the oscillation route is determined.

If the oscillation route is a direct connection route of the publisher equipment of the oscillation route, or the routing protocol table entry corresponding to the oscillation route on the publisher equipment of the oscillation route is not in an oscillation state, determining that the publisher equipment of the oscillation route is an oscillation source of the oscillation route; if the oscillation route is not the direct route of the publisher device of the oscillation route, and the routing protocol table entry corresponding to the oscillation route on the publisher device of the oscillation route is in an oscillation state, the publisher device of the oscillation route may be further determined according to the routing protocol table entry information on the publisher device of the oscillation route, and the tracing detection may be continued according to the manner described in the above step 201 to step 203 until the oscillation source of the oscillation route is determined.

For example, assuming that the route corresponding to the routing table entry a on the network device a is an oscillating route, and the routing protocol table entry a corresponding to the routing table entry a is also in an oscillating state, the network management platform may determine, according to the routing protocol table entry a, a publisher device of the oscillating route (assumed to be the network device B), the network management platform may further determine whether a route corresponding to the oscillating route on the network device B (i.e., a route on the network device B that has the same destination address as the oscillating route) is a direct route on the network device B, if the route is not a direct route of the network device B, and the routing protocol table entry B corresponding to the route (i.e., a route corresponding to the oscillating route on the network device B) is in an oscillating state on the network device B, the network management platform may determine, according to the routing protocol table entry B, the publisher device of the oscillating route (assumed to be the network device C), when the route corresponding to the oscillation route on the network device C (i.e., the route on the network device C having the same destination address as the oscillation route) is the direct-connection route of the network device C, or the route corresponding to the oscillation route on the network device C is not the direct-connection route of the network device C and the route protocol table entry C corresponding to the route (i.e., the route corresponding to the oscillation route on the network device C) is not in the oscillation state on the network device C, the network management platform may determine that the oscillation source of the oscillation route is the network device C.

In this example, when the network management platform determines that a routing protocol table entry corresponding to the oscillation route is not in an oscillation state, the network management platform may determine that the target device is an oscillation source of the oscillation route.

It should be noted that, in the embodiment of the present invention, there may be multiple routing Protocol table entries corresponding to one oscillating route, for example, a routing Protocol table entry of a BGP (Border Gateway Protocol) Protocol and a routing Protocol table entry of an OSPF (Open Shortest Path First) Protocol may exist at the same time, when any of the multiple routing Protocol table entries is in an oscillating state, it may be determined that the routing Protocol table entry corresponding to the oscillating route is in an oscillating state, and a publisher of the oscillating route is determined according to the routing Protocol table entry in the oscillating state, which is not described herein in detail.

In one embodiment of the present invention, determining whether there is a routing protocol table entry in a concussion state on the target device may include:

In one example, the routing protocol information collection time interval increases or decreases as the number of completed routing protocol information collections increases.

For example, the routing protocol information collection interval may be determined by the following equation:

T5＝T4–△T2×N6

wherein, T5 is the currently used information collection time interval of the routing protocol, T4 is the initial information collection time interval of the routing protocol, △ T2 is the second preset decay time, and N6 is the number of completed information collection times of the routing protocol.

The specific implementation of the routing protocol table entry for determining whether the target device has the oscillation state by the network management platform is similar to the specific implementation of determining whether the target device has the oscillation route by the network management platform, and details of the embodiment of the present invention are not repeated herein.

It should be noted that, in the embodiment of the present invention, in order to improve the efficiency of routing concussion positioning, the network management platform may perform, in parallel, collection of routing table information (determine whether a concussion route exists) and collection of routing protocol information (determine whether a routing protocol table entry in a concussion state exists), and details of implementation of the collection and the collection are not described herein.

Accordingly, the initial routing information collection time interval and the initial routing protocol information collection interval may be the same, and the routing information collection time interval and the routing protocol information collection interval may be increased or decreased in the same manner, so that the network management platform may complete the collection of the routing information and the collection of the routing protocol information synchronously, and further improve the efficiency of routing oscillation positioning, and specific implementation thereof is not described herein again.

Further, in the embodiment of the present invention, after the network management platform determines the oscillation source of the oscillation route, it may also determine the oscillation reason causing the oscillation route.

In an embodiment of the present invention, the determining the oscillation reason may include:

collecting the oscillation phenomenon of an oscillation source;

In this embodiment, after determining the oscillation source of the oscillation route, the network management platform may collect an oscillation phenomenon of the oscillation source, and determine the oscillation reason according to the oscillation phenomenon of the oscillation source.

Wherein, the oscillation phenomenon can be determined according to the collected routing information and routing protocol information. Specifically, the oscillation phenomenon may include, but is not limited to, an interval occurrence or a continuous refresh of a routing table entry (the continuous refresh of a routing table entry refers to that the routing table entry exists every time routing table information is collected, and a route occurrence time is always a value smaller than or equal to 15 s), whether a publisher device is continuously updated, whether a routing protocol is continuously switched (for example, the same routing table entry, a route corresponding to the same routing table entry appears in a BGP protocol table in one collection, next appears in an OPSF protocol, and next appears in a BGP protocol table, it is considered that the routing protocol is continuously switched), whether a next hop of the routing table is continuously changed, whether there is an oscillation of an entire publisher route (that is, OSPF routes published by publishers corresponding to the same Router ID are all in an oscillation state, which is usually caused by a repeat of Router ID), and the like.

The concussion reasons may include, but are not limited to, connectivity at a physical or protocol level, instability of a physical link, inconsistency of OSPF timers (OSPF timers), mismatching of MTUs (Maximum Transmission units) at two ends, incorrect setting of source priority of an incoming route in the case that routes are introduced into different routing protocols, repeated distribution of routes, repeated distribution of RouterID (router identification) or repeated concussion of unique identifiers, oscillation caused by NQA Network quality analyzer (Network quality analyzer) and static route linkage, etc.

In an example, the determining the oscillation reason according to the oscillation phenomenon of the oscillation source may include:

In this example, the correspondence relationship between the oscillation phenomenon and the oscillation cause may be configured in advance.

For example, the correspondence relationship between the oscillation phenomenon and the oscillation reason can be as shown in fig. 4, wherein the oscillation reason is in the large frame, and the oscillation phenomenon is in the small frame; the solid line small frame is the oscillation phenomenon, and the dotted line small frame is the oscillation phenomenon which does not occur; the left side of the vertical dashed line is for one oscillation route and the right side of the vertical dashed line is for the publisher device as a whole.

In this example, a certain number of bits (matching the number of ringing) may be used to record the correspondence between the ringing and the cause of the ringing.

Taking the correspondence relationship between the oscillation phenomenon and the oscillation reason shown in the second row of fig. 4 as an example, the route mutually introduces the corresponding oscillation phenomenon represented by "011100", where the bit value corresponding to the oscillation phenomenon is 1 and the bit value not corresponding to the oscillation phenomenon is 0. The repeated issuance of the corresponding ringing by the route shown in the third row can be represented by "110100".

After the network management platform determines the oscillation source of the oscillation route, the network management platform may collect the oscillation phenomenon of the oscillation source, and query, according to the oscillation phenomenon of the oscillation source (which may be recorded in the manner of the bit), the correspondence between the preset oscillation phenomenon and the oscillation source, so as to determine the oscillation reason matched with the oscillation phenomenon of the oscillation source.

Wherein, collecting the oscillation phenomenon of the oscillation source refers to collecting the oscillation phenomenon corresponding to the oscillation route; in the process of collecting the oscillation phenomenon of the oscillation route, for the oscillation phenomenon associated with the publisher, it is required to determine whether all OSPF routes published by the publishers corresponding to the same Router ID are in an oscillation state.

It should be noted that, in the embodiment of the present invention, when the matching oscillation reason is not found according to the oscillation phenomenon of the oscillation source, the oscillation phenomenon of the oscillation source may be recorded, and a user (e.g., a network administrator) analyzes the corresponding oscillation reason in a subsequent process, and adds a new correspondence between the oscillation phenomenon and the oscillation reason.

In addition, when there are two different oscillation phenomena corresponding to the oscillation reasons that are completely the same, the set of oscillation phenomena can be expanded, that is, a new oscillation phenomenon is added, and the corresponding relationship between the configured oscillation phenomenon and the oscillation reason is updated, and the specific implementation thereof is not described herein again.

Furthermore, in the embodiment of the present invention, it is considered that when a route on a network device in a network oscillates, multiple routes of multiple network devices may oscillate, and accordingly, when an oscillation source and an oscillation reason of the oscillation are determined and corresponding measures are taken, the oscillations of the multiple routes of the multiple network devices in the network may all return to normal, so that when multiple target devices satisfying the oscillation route detection condition exist, a network management platform may only detect one target device having the oscillation route, perform source tracing detection on one of the oscillation routes on the target device to determine the oscillation source and the oscillation reason, and record the determined oscillation source and the oscillation reason, for example, record in an alarm log, and a user (e.g., a network administrator) takes corresponding measures.

If the user still has the routing oscillation in the network after taking corresponding measures, the network management platform may perform the routing oscillation positioning again according to the above-described manners of pre-detecting, and tracing analysis results, and the specific implementation thereof is not described herein again.

In order to enable those skilled in the art to better understand the technical solutions provided by the embodiments of the present invention, the technical solutions provided by the embodiments of the present invention are described below with reference to specific examples.

Referring to fig. 5, in this embodiment, the method for positioning routing oscillation may include the following steps:

firstly, acquiring a device list

The network management platform reads out the device ID (abbreviated as DevID, wherein the DevID is the unique identifier of the device to be detected on the network management platform (the identifier of the device to be detected i is DevIDi), which is a 32-bit unsigned int (unsigned shaping) type value), and initializes the device ID and adds the device ID into the polling queue.

Polling equipment to be detected

In this embodiment, to implement polling of the device to be tested, the network management platform may maintain the attribute fields shown in table 1:

TABLE 1

In this embodiment, in the initialization process of the network management platform, two initial values, that is, an initialized polling time interval initcycletime and a triggered detection time InitTriggerTime, may be read from the configuration file, and then the polling time interval devcycletime of each device to be detected is assigned as the initialized polling time interval initcycletime (30 s is taken as an example herein).

The initial value of the residual detection time DevLeftTime of each device to be detected is DevID% 30, and the device to be detected is dispersedly polled in the mode, so that excessive devices are prevented from being polled at one time.

Wherein, for the device i to be detected, the initial value of the residual detection time is DevIDi% 30.

Taking the system polling timer time as 5s as an example, namely, subtracting 5s from the remaining detection time of the device to be detected every 5s by the network management platform, dividing the pre-detection of the device to be detected into 6 batches, wherein the initial value of the remaining detection time is one batch of 0-5 s, and the initial value of the remaining detection time is one batch of … of 6-10 s, and the initial value of the remaining detection time is one batch of 26-29 s.

It should be noted that, in order to avoid too large difference between the time intervals of the pre-detection of the devices to be detected, after the pre-detection of the devices to be detected is triggered according to the initial value of the remaining detection time DevLeftTime of the devices to be detected, the value of the remaining detection time DevLeftTime of each device to be detected may be set as the polling time interval of the devices to be detected.

The initial value of the polling time interval of each device to be detected is 30s, and the polling time interval can be updated along with the change condition of the number of the routing table entries in the pre-detection process.

In this embodiment, the system polling timer time is set to 5s, that is, the remaining detection time DevLeftTime of all the devices to be detected is polled every 5 s; and if the equipment to be detected with the DevLeftTime less than or equal to 0 is polled, the equipment to be detected is subjected to pre-detection.

The pre-detection process obtains the number of the routing table entries of the device to be detected in an SNMP (Simple Network Management Protocol) GET (obtaining) manner. For any equipment to be detected, if the number of the routing table entries of the equipment to be detected is found to be changed from the last comparison, the polling time interval DevCyclingtime of the equipment to be detected is reduced by 5s, namely, the pre-detection period of the equipment to be detected is shortened, and the value of the stable remaining number of DevStableLeft is set to be 5 (the number of the routing table entries is not changed from the last comparison every time, namely, the DevStableLeft is reduced by 1, and if the number of the routing table entries for 5 times is not changed continuously, the polling time interval DevCyclingtime is recovered for 5s (namely, the polling time interval is increased for 5s) until the initialized polling time interval is recovered for 30 s).

In this embodiment, for any device to be detected, if the polling time interval devcyclenginitime of the device to be detected is reduced to the trigger detection time InitTriggerTime, for example, 15s, it indicates that the device to be detected has changed the number of entries of the routing table for at least 3 times, and at this time, the device to be detected may be triggered to perform oscillation routing detection.

The implementation process of polling the device to be detected by the network management platform may be as shown in fig. 6.

Third, oscillating route detection

For the device to be detected (i.e. target device) which needs to trigger the oscillation route detection during the pre-detection process, the device to be detected (i.e. target device) can be added into a waiting detection queue (Wait2CheckList), wherein the target devices in the queue to be detected are detected in the sequence from the head to the tail, i.e. when the oscillation route detection is performed each time, one target device is taken out from the head of the waiting detection queue for detection, and the target device newly added into the queue to be detected (the device to be detected which needs to trigger the oscillation route detection is determined through the pre-detection process) is added into the tail of the waiting detection queue.

For example, as shown in fig. 7, it is assumed that the waiting-to-detect queue includes target devices a to E, when the target device F is determined to need to trigger oscillation route detection in the pre-detection process, the target device F may be added to the tail of the waiting-to-detect queue, and when all the target devices a to E in the waiting-to-detect queue complete detection, the target device F may be detected.

In the embodiment, by using the queue, only one device is ensured to be in the detection state at the same time, and the phenomenon that the device resource pressure of the network management platform is overloaded, the processing is blocked if the device resource pressure is overloaded, and the device is crashed if the device resource pressure is heavy due to the detection of multiple devices at the same time when the devices are in the oscillation state at the same time is avoided, so that the reliability of the network management platform is improved.

1. Information collection of oscillation route

In this embodiment, the information collection of the oscillating route may include that two repeated information collection processes (b, c) are performed in parallel, that is, the repeated collection of the routing information and the routing protocol information of the target device is performed, and the oscillating route is determined and the oscillating source of the oscillating route is located according to the collected routing information and the routing protocol information.

As shown in fig. 8, the information collection of the oscillation route may include the following steps:

a. initializing detection parameters

In this embodiment, to implement information collection of the oscillation route, the network management platform may maintain the attribute fields shown in table 2:

TABLE 2

In this embodiment, the initial information collection time interval initintersaltime, the decay time, and the collection times CollectNum may be directly read from the configuration file by the network management platform, where initintersaltime is an initial value of the information collection time interval. CollectNum is the collection times, and in order to achieve the accuracy of information collection, the CollectNum is set to 10 times by default, that is, the routing table and routing protocol information of the device are collected by 10 times by default. Reducitime is the decay time.

In this embodiment, the initial value of the route information collection time interval and the initial value of the route protocol information collection time interval are the same (both initinterval time), the number of times of collecting the route information and the number of times of collecting the route protocol information are the same (both CollectNum), and the first preset attenuation time and the second preset attenuation time are the same (both reduce time).

Taking route information collection as an example, when the network management platform collects the route table information of any target device, the currently used route information collection time interval currintervaltime is the initial interval collection device information time InitIntervalTime-decay time reducitime × the completed route information collection times devroutetblcollectitimes, so as to avoid that no route oscillation is detected due to the condition that the route oscillation period is the same as the route information collection time interval.

b. Route information collection

In this embodiment, a single collection of routing information may be as shown in table 3:

TABLE 3

After the network management platform collects the routing information for 10 times, the network management platform may combine the collected routing information for 10 times, and obtain the information shown in table 4:

TABLE 4

c. Routing protocol information collection

In this embodiment, the network management platform collects routing protocol information similarly to the routing information collection, and merges the collected routing protocol information 10 times to obtain the information shown in table 5:

TABLE 5

Attribute name	Attribute interpretation
		strRouteDest	Destination address
EmergeTime	Routing protocol table entry occurrence statistics
		strRouteAdvID	Publisher route ID
LSDBAgeSum；	Routing protocol table entry epoch summation

2. Screening oscillation route

In this embodiment, the determining the route oscillation mode may mainly include:

checking oscillation times oTurnTimes; for any routing table entry, if oTurnTimes is greater than or equal to 2, determining that the routing corresponding to the routing table entry is in oscillation; and when the oTurnTimes of the routing table entry is less than or equal to 1, checking the total RouteAgeStam of the time of occurrence of the routing, if the RouterAgeStam is more than or equal to GetTimes multiplied by 15s, determining that the routing corresponding to the routing table entry does not vibrate, otherwise, when the oTurnTimes of the routing table entry is less than or equal to 1 and the RouterAgeStam is less than GetTimes multiplied by 15s, determining that the routing does not vibrate.

For the oscillation route, the oscillation route may be placed in a flap routeinfolist (oscillation route information linked list) linked list.

In this embodiment, for any oscillating route, the publisher device of the route may be determined according to the corresponding routing protocol information, and it is determined whether the routing protocol table entry corresponding to the oscillating route is in an oscillating state, and if so, the publisher device of the oscillating route is added to the head of the queue waiting for detection.

In this embodiment, it is considered that, when the route oscillation occurs in the whole network, a plurality of network devices often generate the route oscillation at the same time, and most of the network devices are in a state of passively causing the route oscillation. If all network devices are detected together without priority, the background detection program can encounter a bottleneck in performance, and the problem is effectively solved by a queue (waiting for detection queue).

However, in consideration of the fact that the efficiency of performing the oscillation route positioning may be poor in the manner of performing the oscillation route detection on one network device at a time, the embodiment may implement the positioning of the oscillation route by using the tracing detection manner.

In this embodiment, when the routing protocol table corresponding to the oscillation route is also in the oscillation state, the network management platform may add the publisher device of the oscillation route to the head of the queue waiting for detection, that is, the next publisher device performing oscillation route detection is the oscillation route publisher device.

Because the publisher equipment of the oscillation route is the oscillation source which causes route oscillation theoretically, the next target equipment which carries out oscillation route detection points to the oscillation source, so that the oscillation reason can be found out more quickly, and the efficiency of oscillation route positioning is improved.

In this embodiment, when the network management platform locates to the oscillation route in the above manner, the oscillation reason may be further determined, and a specific implementation thereof is described below; when the network management platform detects that no oscillation route exists, the current process is ended, the target equipment for oscillation route detection is added into the polling queue again, and pre-detection is performed according to the manner described above.

It should be noted that, in this embodiment, for any target device, if an error occurs in the process of performing oscillation route detection on the target device, the oscillation route detection on the target device may be stopped. At this time, the network management platform may generate a corresponding error log so that a user (network administrator) may take corresponding measures.

Fourthly, determining the reason of the oscillation

In this embodiment, the correspondence between the oscillation reason and the oscillation phenomenon as shown in fig. 3 may be configured in advance.

After the network management platform locates the oscillation source according to the above manner, the network management platform may query the correspondence between the oscillation reason and the oscillation phenomenon shown in fig. 3 according to the oscillation phenomenon of the oscillation source, and determine the oscillation reason matched with the oscillation phenomenon of the oscillation source.

In this embodiment, by configuring the correspondence between the oscillation cause and the oscillation phenomenon, and querying the matching oscillation cause in the correspondence according to the oscillation phenomenon of the oscillation source, the positioning of the oscillation cause can be realized only by using a standard MIB (management information Base) library of the SNMP protocol, and the efficiency of positioning the oscillation cause is high and the workload is small.

As can be seen from the above description, in the technical solution provided in the embodiment of the present invention, by performing pre-detection on a device to be detected, determining a target device that meets a detection condition of an oscillation route, performing oscillation route detection on the target device, and determining whether the oscillation route exists, for any target device, when the oscillation route exists on the target device, determining an oscillation source of the oscillation route, and determining an oscillation reason, a route oscillation positioning is implemented.

The method provided by the present invention is described above. The following describes the apparatus provided by the present invention:

fig. 9 is a schematic diagram of a hardware structure of a server according to an embodiment of the present invention. The server may include a processor 901, a machine-readable storage medium 902 having stored thereon machine-executable instructions. The processor 901 and the machine-readable storage medium 902 may communicate via a system bus 903. Moreover, by reading and executing the machine executable instructions corresponding to the routing concussion positioning control logic in the machine readable storage medium 902, the processor 901 may execute the routing concussion positioning method described above.

The machine-readable storage medium 902 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

As shown in fig. 10, functionally, the routing oscillation positioning control logic may include: a pre-detection unit 1001, a detection unit 1002, and a positioning unit 1003; wherein:

a pre-detection unit 1001, configured to perform pre-detection on a device to be detected to determine a target device that meets a detection condition of an oscillation route;

a detecting unit 1002, configured to perform oscillation route detection on the target device to determine whether an oscillation route exists;

a positioning unit 1003, configured to determine, for any one of the target devices, an oscillation source of the oscillation route and determine an oscillation reason when the oscillation route exists on the target device.

In an optional embodiment, the pre-detection unit 1001 is specifically configured to poll the device to be detected according to a polling time interval of the device to be detected; for any equipment to be detected, when detecting that the number of the routing table entries of the equipment to be detected changes, subtracting a first preset time from the polling time interval of the equipment to be detected; and when the polling time interval of the equipment to be detected is equal to the preset trigger detection time, executing the step of performing oscillation route detection on the target equipment.

In an optional embodiment, the pre-detection unit 1001 is specifically configured to subtract, every second preset time, the second preset time from the remaining detection time of the device to be detected; and when the residual detection time of the equipment to be detected is less than or equal to 0, performing pre-detection on the equipment to be detected, and setting the residual detection time of the equipment to be detected as the polling time interval of the equipment to be detected.

In an optional embodiment, the detecting unit 1002 is specifically configured to determine, for any target device performing oscillation route detection, whether an oscillation route exists on the target device according to the routing information of the target device;

In an optional embodiment, the detecting unit 1002 is specifically configured to poll the routing table of the target device N3 times according to the route information collection time interval, so as to collect the route information; for any routing table entry, when the oscillation frequency of the routing table entry is greater than or equal to a first preset oscillation frequency threshold value, executing a step of determining an oscillation source of the oscillation route;

In an alternative embodiment, the route information collection time interval increases or decreases as the number of route information collections completed increases.

In an optional embodiment, the positioning unit 1003 is specifically configured to determine, for any oscillating route, whether the oscillating route is a direct route of the target device; if so, determining the target equipment as an oscillation source of the oscillation route; otherwise, determining the oscillation source of the oscillation route according to the routing protocol information corresponding to the oscillation route.

In an optional embodiment, the positioning unit 1003 is specifically configured to determine whether a routing protocol table entry corresponding to the oscillation route is in an oscillation state; if so, after the current target equipment completes detection, oscillation route detection is carried out on the publisher equipment included in the route protocol table entry in the oscillation state until an oscillation source of the oscillation route is determined; if not, executing the step of determining the oscillation reason.

In an optional embodiment, the positioning unit 1003 is further configured to poll, for any target device, the routing protocol table of the target device N4 times according to the routing protocol information collection time interval to collect routing protocol information; the routing protocol information comprises a destination address and the appearance time of an entry of a routing protocol table;

In an alternative embodiment, the routing protocol information collection time interval increases or decreases as the number of completed routing protocol information collections increases.

In an optional embodiment, the positioning unit 1003 is specifically configured to collect an oscillation phenomenon of the oscillation source; and determining the oscillation reason according to the oscillation phenomenon of the oscillation source.

In an optional embodiment, the positioning unit 1003 is specifically configured to query a preset correspondence between an oscillation phenomenon and an oscillation reason according to the oscillation phenomenon of the oscillation source, so as to determine the oscillation reason matched with the oscillation phenomenon of the oscillation source.

Embodiments of the present invention also provide a machine-readable storage medium, such as the memory 902 in fig. 9, storing computer-executable instructions, which can be executed by the processor 901 in the electronic device shown in fig. 9 to implement the routing oscillation positioning method described above.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A routing oscillation positioning method is characterized by comprising the following steps:

2. The method according to claim 1, wherein the pre-detecting the device to be detected to determine the target device meeting the oscillating route detection condition comprises:

3. The method according to claim 2, wherein polling the device under test at polling intervals of the device under test comprises:

4. The method of claim 1, wherein the performing the oscillating route detection on the target device comprises:

5. The method of claim 4, wherein determining whether the oscillating route exists on the target device according to the routing information of the target device comprises:

6. The method of claim 5, wherein the route information collection time interval increases or decreases as the number of route information collections completed increases.

7. The method of claim 1, wherein the determining an oscillation source of the oscillation route comprises:

8. The method of claim 7, wherein determining the oscillation source of the oscillation route according to the routing protocol information corresponding to the oscillation route comprises: judging whether the routing protocol table entry corresponding to the oscillation route is in an oscillation state;

if not, executing the step of determining the oscillation reason.

9. The method of claim 8, further comprising:

10. The method of claim 9, wherein the routing protocol information collection time interval increases or decreases as the number of completed routing protocol information collections increases.

11. The method of claim 1, wherein the determining the cause of the oscillation comprises:

collecting the oscillation phenomenon of the oscillation source;

12. The method according to claim 11, wherein the determining the cause of the oscillation according to the oscillation phenomenon of the oscillation source comprises:

13. A server comprising a processor and a machine-readable storage medium storing machine-readable instructions executable by the processor, the processor being caused by the machine-readable instructions to perform the routing shock localization method of any one of claims 1-12.

14. A machine-readable storage medium having stored thereon machine-executable instructions that, when invoked and executed by a processor, cause the processor to perform a routing shock localization method according to any one of claims 1-12.