Abnormal monitoring method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to an exception monitoring method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps that after a border gateway protocol BGP link is established on a target network element, a source port list of a static aggregation group of the target network element is acquired, and the source port list comprises target source ports covering data streams of all interfaces in the static aggregation group; after the target network element issues a VIP route, acquiring first data transceiving information of each interface; and performing abnormity monitoring on each interface according to the first data transceiving information and the source port list, and performing removal processing on the VIP route under the condition that an abnormity monitoring result indicates that abnormity exists. By adopting the method, the efficiency of solving the probabilistic packet loss problem of the service flow is effectively improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an abnormality monitoring method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] Link aggregation usually aggregates multiple physical interfaces into an aggregation group for use, which can effectively improve the bandwidth and reliability of network device links. Link aggregation includes static aggregation and dynamic aggregation. In the static aggregation scenario, since it is impossible to determine the status information of the corresponding interface of the physical interface in the aggregation group on the peer device, the inconsistency of the interface status at both ends will lead to the formation of abnormal links, thus causing the problem of probabilistic packet loss of business flows.

[0003] In the prior art, most of them are based on devices at both ends to monitor abnormal links, thereby avoiding the occurrence of probabilistic packet loss problems in business flows.

[0004] However, since this method needs to rely on devices at both ends to be implemented, it is less efficient in solving the problem of probabilistic packet loss in business flows. Summary of the invention

[0005] Based on this, it is necessary to provide an abnormality monitoring method, device, computer equipment, computer readable storage medium and computer program product to address the above technical problems, which can effectively improve the efficiency of solving the probabilistic packet loss problem of business flows.

[0006] In a first aspect, the present application provides an abnormality monitoring method, comprising:

[0007] After establishing a Border Gateway Protocol (BGP) link at the target network element, obtaining a source port list of a static aggregation group of the target network element, the source port list including target source ports of data flows covering each interface in the static aggregation group;

[0008] After the target network element publishes the VIP route, obtaining the first data receiving and sending information of each interface;

[0009] The interfaces are monitored for abnormalities according to the first data receiving and sending information and the source port list, and the VIP route is removed when the result of the abnormality monitoring indicates that an abnormality exists.

[0010] In one of the embodiments, the source port list of the static aggregation group of the target network element is obtained, including: for each of the interfaces, determining a candidate source port based on a preset port range, and sending test data to the opposite device based on the candidate source port; after sending the test data, determining whether the interface has received or sent data, and if so, using the candidate source port as the target source port corresponding to the interface and storing it in the source port list.

[0011] In one of the embodiments, each interface is monitored for abnormalities based on the first data transceiver information and the source port list, including: determining whether there is a target interface in each interface based on the first data transceiver information, the target interface being an interface that does not transmit or receive data; if the target interface exists, each interface is monitored for abnormalities based on the source port list.

[0012] In one of the embodiments, the abnormality monitoring is performed on each interface according to the source port list, including: sending preset data to the opposite device based on the target source port included in the source port list; if after a preset time, it is detected that there is an interface among the interfaces that has not received data, then determining that the result of the abnormality monitoring is that an abnormality exists.

[0013] In one of the embodiments, after the VIP route is removed, the method further includes: when it is determined that each interface has returned to normal, performing abnormality monitoring on each interface again based on the source port list; when the result of the abnormality monitoring indicates that there is no abnormality, publishing the VIP route again.

[0014] In one of the embodiments, the method also includes: when there is a change in the interface in the static aggregation group, obtaining a new interface and determining whether the target source port can cover the data flow of the new interface; if not, obtaining a new source port list and performing abnormal monitoring on the new interface based on the new source port list.

[0015] In a second aspect, the present application also provides an abnormality monitoring device, comprising:

[0016] A first acquisition module is used to acquire a source port list of a static aggregation group of the target network element after a Border Gateway Protocol BGP link is established in the target network element, the source port list including target source ports of data flows covering each interface in the static aggregation group;

[0017] A second acquisition module is used to acquire the first data receiving and sending information of each interface after the target network element publishes the VIP route;

[0018] The execution module is used to perform abnormal monitoring on each interface according to the first data receiving and sending information and the source port list, and remove the VIP route when the result of the abnormal monitoring indicates that an abnormality exists.

[0019] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method described in any embodiment of the first aspect when executing the computer program.

[0020] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in any embodiment of the first aspect above.

[0021] In a fifth aspect, the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the method described in any embodiment of the first aspect above.

[0022] The above-mentioned abnormal monitoring method, device, computer equipment, computer-readable storage medium and computer program product, after the target network element establishes a border gateway protocol BGP link, obtains the source port list of the static aggregation group of the target network element, and the source port list includes the target source port of the data flow covering each interface in the static aggregation group; and after the target network element publishes the VIP route, obtains the first data transceiver information of each interface; then performs abnormal monitoring on each interface according to the first data transceiver information and the source port list, and removes the VIP route when the result of the abnormal monitoring indicates that there is an abnormality. The abnormal monitoring method provided by the present application can realize the abnormal monitoring of each interface through the first transceiver information and the source port list of each interface of the target network element, and in the case of detecting an abnormality, promptly removes the VIP route to avoid the problem of probabilistic packet loss of business flow due to the existence of abnormal links. Due to the abnormal monitoring method provided by the present application, the problem of probabilistic packet loss of business flow can be solved by relying only on the target network element, which can effectively reduce the cost and complexity compared with the prior art that must rely on the two-end equipment, thereby effectively improving the efficiency of solving the problem of probabilistic packet loss of business flow. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 A schematic diagram of a flow chart of an abnormality monitoring method in one embodiment;

[0025] Figure 2 A schematic diagram of a flow chart of a method for obtaining a source port list of a static aggregation group of the target network element in an embodiment;

[0026] Figure 3 It is a flowchart of a method for performing abnormality monitoring on each interface according to the first data receiving and sending information and the source port list in an embodiment;

[0027] Figure 4 It is a flowchart of a method for performing abnormality monitoring on each interface according to the source port list in an embodiment;

[0028] Figure 5 It is a flowchart of a method for removing the VIP route in one embodiment;

[0029] Figure 6 is a flow chart of a method in an embodiment when there is a change in the interface in the static aggregation group;

[0030] Figure 7 A schematic diagram of a flow chart of an abnormality monitoring method in another embodiment;

[0031] Figure 8 is a structural block diagram of an abnormality monitoring device in an embodiment;

[0032] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0034] Link aggregation usually aggregates multiple physical interfaces into an aggregation group for use, which can effectively improve the bandwidth and reliability of network device links. Link aggregation includes static aggregation and dynamic aggregation. In the static aggregation scenario, since it is impossible to determine the status information of the corresponding interface of the physical interface in the aggregation group on the peer device, the inconsistency of the interface status at both ends will lead to the formation of abnormal links, thus causing the problem of probabilistic packet loss of business flows.

[0035] In the prior art, most of them are based on devices at both ends to monitor abnormal links, thereby avoiding the occurrence of probabilistic packet loss problems in business flows.

[0036] However, since this method needs to rely on devices at both ends to be implemented, it is less efficient in solving the problem of probabilistic packet loss in business flows.

[0037] In view of this, the present application provides an abnormality monitoring method, which can solve the problem of probabilistic packet loss of business flows by relying on the target network element. Compared with the existing technology that must rely on the devices at both ends, it can effectively reduce the cost and complexity, thereby effectively improving the efficiency of solving the problem of probabilistic packet loss of business flows.

[0038] The abnormal monitoring method provided in the present application may be executed by a computer device, which may be a network element. In an optional embodiment, the network element may be a network element in a network element cluster in a network architecture, and the network element may be interconnected with a switch in a static aggregation manner.

[0039] In an exemplary embodiment, Figure 1 As shown, a method for abnormal monitoring is provided, the method comprising the following steps:

[0040] Step 101: After a Border Gateway Protocol (BGP) link is established at a target network element, a source port list of a static aggregation group of the target network element is obtained.

[0041] The source port list includes target source ports of data flows covering each interface in the static aggregation group.

[0042] Border Gateway Protocol (BGP) refers to a dynamic routing protocol. The BGP link is established based on a TCP connection. It can establish a connection between two network devices that support BGP and communicate through TCP ports.

[0043] The source port is the port number used on a computer device by the application or process sending data.

[0044] In some exemplary embodiments, as described above, a static aggregation group is formed by static aggregation of multiple interfaces. When the target network element sends and receives data with the peer device, it can send data to the peer device or receive data sent by the peer device through each interface, and different interfaces have different corresponding source ports.

[0045] Furthermore, after the target network element establishes a BGP link with the peer device, the source port list of the static aggregation group of the target network element can be obtained first, and the source port list stores the port number of the source port corresponding to each interface. Specifically, the source port corresponding to each interface can be obtained through the socket interface, and then the source port list is determined according to the source port corresponding to each interface.

[0046] Step 102: After the target network element publishes the VIP route, first data receiving and sending information of each interface is obtained.

[0047] The VIP is also a virtual IP. For example, when data needs to be transmitted in the network, special encapsulation processing is required. At this time, BGP routing can publish a VXLAN VTEIP address, that is, VIP, for encapsulation of the VXLAN tunnel.

[0048] The first data transceiving information can be used to characterize the data transceiving status of each interface, for example, whether each interface has sent data or received data.

[0049] In some exemplary embodiments, after establishing a BGP link with the peer device, the target network element may first obtain a source port list, and after obtaining the source port list, publish a VIP route based on the BGP link, and after publishing the VIP route, obtain the first data transceiver information of each interface. Specifically, the first data transceiver information of each interface may be determined by whether there is traffic on each interface.

[0050] Step 103: perform abnormality monitoring on each interface according to the first data receiving and sending information and the source port list, and remove the VIP route when the abnormality monitoring result indicates that an abnormality exists.

[0051] In some exemplary embodiments, as described above, in a static aggregation scenario, since the state information of the interface corresponding to the interface in the aggregation group in the peer device cannot be determined, the state of the interfaces at both ends is inconsistent, which will lead to the formation of abnormal links, thereby causing the problem of probabilistic packet loss of service flows. That is, since the target network element cannot determine the state of each interface of the peer device, it cannot discover abnormal links in time.

[0052] Furthermore, since each interface of the target network element and each interface of the opposite device will send and receive data, it is possible to monitor the first data sending and receiving information of each interface, and then indirectly determine whether there are abnormalities in each interface of the opposite device, and timely determine the abnormal link to avoid the occurrence of probabilistic packet loss problems in the business flow.

[0053] Therefore, each interface can be monitored for abnormalities according to the first data receiving and sending information and the source port list, and when the result of the abnormal monitoring indicates that an abnormality exists, the VIP route can be removed.

[0054] Specifically, it can be determined whether to perform abnormal monitoring based on the first sent and received information. If it is determined to perform abnormal monitoring, each interface is monitored for abnormalities based on the source port list. If the result of the abnormal monitoring indicates that an abnormality exists, the VIP route is removed.

[0055] The above-mentioned abnormal monitoring method, after the target network element establishes a border gateway protocol BGP link, obtains the source port list of the static aggregation group of the target network element, and the source port list includes the target source port of the data flow covering each interface in the static aggregation group; and after the VIP route published by the target network element, obtains the first data transceiver information of each interface; then performs abnormal monitoring on each interface according to the first data transceiver information and the source port list, and removes the VIP route when the result of the abnormal monitoring indicates that an abnormality exists. The abnormal monitoring method provided by the present application can realize abnormal monitoring of each interface through the first transceiver information and the source port list of each interface of the target network element, and removes the VIP route in time when an abnormality is detected, avoiding the problem of probabilistic packet loss of business flow due to the existence of abnormal links. Due to the abnormal monitoring method provided by the present application, the problem of probabilistic packet loss of business flow can be solved by relying only on the target network element. Compared with the prior art that must rely on the devices at both ends, it can effectively reduce the cost and complexity, thereby effectively improving the efficiency of solving the problem of probabilistic packet loss of business flow.

[0056] In an exemplary embodiment, Figure 2 As shown, obtaining the source port list of the static aggregation group of the target network element includes the following steps:

[0057] Step 201: For each of the interfaces, determine a candidate source port based on a preset port range, and send test data to the opposite device based on the candidate source port.

[0058] Optionally, the preset port range refers to a port number range corresponding to the source port, and the range may be 1024-65535.

[0059] Exemplarily, the port numbers include 0-65535. Since the port numbers in the range of 0 to 1023 are well-known ports and are usually used by some specific, system-level important applications, the preset port range is set to 1024-65535.

[0060] The test data may be data pre-set by a technician according to actual needs.

[0061] In some exemplary embodiments, for each of the interfaces, a port number can be randomly determined within the preset port range, and the source port corresponding to the port number can be determined as a candidate source port, and test data can be sent to the opposite device based on the candidate source port.

[0062] The above source port range is set to 1024-65535 to ensure that there are enough target source ports to perform diversified anomaly monitoring and avoid problems such as port conflicts that affect the monitoring results.

[0063] Step 202: After sending the test data, determine whether the interface has data to send or receive. If so, use the candidate source port as the target source port corresponding to the interface and store it in the source port list.

[0064] In some exemplary embodiments, after sending test data to the peer device based on the candidate source port, it can be determined whether the interface has transceiver data. If so, it can be determined that the source port covers the data flow of the interface. If not, it can be determined that the source port does not cover the data flow of the interface.

[0065] Furthermore, if there is no sending or receiving data, a port number can be randomly determined again within the preset port range, and the source port corresponding to the port number can be determined as a new candidate source port. Test data is sent to the opposite device based on the new candidate source port, and after sending the test data, it is determined again whether there is sending or receiving data on the interface to determine whether the new candidate source port is the target source port corresponding to the interface.

[0066] The above steps are performed for each interface until the corresponding target source port of each interface is determined, and the target source port corresponding to each interface is stored in the source port list.

[0067] In an optional embodiment of the present application, the candidate source ports may be randomly determined within the preset port range, or may be determined according to a preset rule. If the number of interfaces is N, the number of determined target source ports is at least N and at most 2N. Optionally, the determined source port list may be [4596, 6553, 9447, 25698, 45698].

[0068] In an exemplary embodiment, Figure 3 As shown, the abnormality monitoring of each interface according to the first data receiving and sending information and the source port list includes the following steps:

[0069] Step 301: Determine whether there is a target interface among the interfaces according to the first data receiving and sending information.

[0070] The target interface is an interface without any data for transmission or reception. The data for transmission or reception here refers to any one of the data for reception or transmission.

[0071] In some exemplary embodiments, after obtaining the first data transceiving information of each interface, it can be determined whether each interface has transceiving data according to the first data transceiving information, and the target interface can be determined from multiple interfaces according to whether each interface has transceiving data. Specifically, the interface without transceiving data can be determined as the target interface.

[0072] For example, there are four interfaces, namely A1, A2, A3 and A4, and the first data receiving and sending information of the four interfaces is obtained. If it is determined according to the first receiving and sending information that A1, A2 and A3 all have receiving / sending data, and A4 does not have receiving / sending data, then A4 can be determined as the target interface.

[0073] Step 302: If the target interface exists, perform abnormal monitoring on each interface according to the source port list.

[0074] In some exemplary embodiments, when it is determined according to the first data transceiver information that there is a target interface among the interfaces, each interface may be monitored for abnormalities according to the source port list to determine whether there is an abnormal link.

[0075] In an optional embodiment of the present application, when it is determined based on the first data receiving and sending information that there is no target interface among the interfaces, abnormality monitoring may not be performed, or abnormality monitoring may be performed. The specific implementation steps of performing abnormality monitoring may be described as follows.

[0076] In an exemplary embodiment, Figure 4 As shown, the abnormality monitoring of each interface according to the source port list includes the following steps:

[0077] Step 401: Send preset data to the opposite device based on the target source port included in the source port list.

[0078] Optionally, the preset data may be data pre-set by a technician according to actual needs.

[0079] Exemplarily, the preset data may be determined according to the abnormal monitoring configuration information. The abnormal monitoring configuration information includes the local IP, the destination IP of the peer device, the local port, the destination port of the peer device and the protocol type. The above test data may also be determined according to the abnormal monitoring configuration information.

[0080] In some exemplary embodiments, when it is determined that there is a target interface among the interfaces, the target source port corresponding to each interface may be determined according to the source port list, and preset data may be sent to the opposite device through the target source port.

[0081] Step 402: If after a preset time, it is detected that there is an interface among the interfaces that has not received data, it is determined that the result of the abnormality monitoring is that an abnormality exists.

[0082] Optionally, the preset time can be pre-set by a technician according to actual needs.

[0083] In some exemplary embodiments, after sending preset data to the opposite device based on the target source port included in the source port list, wait for a preset time. During the preset time period, if it is detected that there are interfaces among the interfaces that have not received data, it can be directly determined that the result of the abnormal monitoring is that an abnormality exists.

[0084] In an optional embodiment of the present application, after sending preset data to the opposite device based on the target source port included in the source port list, wait for a preset time. During the preset time period, if it is detected that there are interfaces among the interfaces that have not received data, continue to perform abnormal monitoring for a preset number of times according to the above steps. If it is detected that there are interfaces among the interfaces that have not received data for three consecutive times, it is determined that the result of the abnormal monitoring is that an abnormality exists.

[0085] As described above, when it is determined according to the first data transceiver information that there is no target interface among the interfaces, abnormal monitoring may not be performed, or abnormal monitoring may be performed. The abnormal monitoring here may be performed only once, that is, when there is a target interface, a preset number of abnormal monitorings need to be performed, and if the abnormal monitoring results are abnormal for multiple consecutive times, it is determined that there is an abnormal link. If there is no target interface, abnormal monitoring may be performed only once.

[0086] In an exemplary embodiment, Figure 5 As shown, after the VIP route is removed, the method further includes the following steps:

[0087] Step 501: When it is determined that each interface has returned to normal, abnormality monitoring is performed again on each interface based on the source port list.

[0088] In some exemplary embodiments, if the result of abnormal monitoring indicates that an abnormality exists, the VIP route may be removed, and after the VIP route is removed, each interface will be restored.

[0089] Furthermore, when it is determined that all interfaces have returned to normal, each interface can be monitored for abnormalities again based on the source port list. Specifically, each target source port in the source port list first sends preset data to the opposite device, and after the preset event, each interface is detected to see if there is received data, so as to determine the abnormality detection result based on the detection result.

[0090] Step 502: When the result of the abnormality monitoring indicates that there is no abnormality, the VIP route is published again.

[0091] In some exemplary embodiments, if it is detected that all interfaces have received data, it can be determined that the abnormality monitoring result is that there is no abnormality, and the VIP route can be published again.

[0092] In an optional embodiment of the present application, when it is determined that the abnormal monitoring result is that there is no abnormality, each interface can also be continuously monitored for abnormalities for a preset period of time. If the monitoring result that there is no abnormality continues for the preset period of time, the VIP route is published again.

[0093] In an exemplary embodiment, Figure 6 As shown, when there is a change in the interface in the static aggregation group, the method further includes the following steps:

[0094] Step 601: Obtain a new interface and determine whether the target source port can cover the data flow of the new interface.

[0095] In some exemplary embodiments, when the state of a certain interface in the static aggregation group changes from UP to DOWN, it can be determined that there is a change in the interface in the static aggregation group, and a new interface is acquired.

[0096] For example, there are four interfaces, namely A1, A2, A3 and A4. The state of the A4 interface changes from UP to DOWN. Then, it can be determined that the new interfaces are A1, A2 and A3.

[0097] Further, after obtaining the new interface, it can be determined whether the target source port in the source port list can cover the data flow of each new interface.

[0098] Specifically, data may be sent to the opposite device based on each target source port, and each interface may be detected to determine whether there is data being sent or received, and whether the target source port can cover the data flow of the new interface may be determined based on the detection result.

[0099] Step 602: If not, obtain a new source port list, and perform abnormality monitoring on the new interface based on the new source port list.

[0100] In some exemplary embodiments, if it is determined that the target source port cannot cover the data flow of the new interface, a new source port class list is obtained, that is, for each of the new interfaces, a candidate source port is determined based on a preset port range, and test data is sent to the peer device based on the candidate source port. After sending the test data, it is determined whether the interface has transceiver data, and if so, the candidate source port is used as the target source port corresponding to the interface and stored in the new source port list.

[0101] Further, after obtaining the new source port list, the new interface can be monitored for abnormalities based on the new source port list. The specific abnormality monitoring steps can refer to the relevant content of abnormality monitoring above, which will not be repeated here.

[0102] In an exemplary embodiment, Figure 7 As shown, another abnormality monitoring method is provided, the method comprising the following steps:

[0103] Step 701: After a Border Gateway Protocol (BGP) link is established in a target network element, for each interface in a static aggregation group of the target network element, a candidate source port is determined based on a preset port range, and test data is sent to the opposite device based on the candidate source port; after sending the test data, it is determined whether the interface has received and sent data, and if so, the candidate source port is used as the target source port corresponding to the interface and stored in the source port list; the source port list includes target source ports of data flows covering each interface in the static aggregation group;

[0104] Step 702: after the target network element publishes the VIP route, first data transceiving information of each interface is obtained; whether there is a target interface among the interfaces is determined according to the first data transceiving information, and the target interface is an interface without transceiving data; if the target interface exists, preset data is sent to the opposite device based on the target source port included in the source port list; if after a preset time, it is detected that there is an interface among the interfaces that has not received data, it is determined that the result of the abnormality monitoring is that an abnormality exists, and if the result of the abnormality monitoring indicates that an abnormality exists, the VIP route is removed;

[0105] Step 703: When it is determined that each interface has returned to normal, perform abnormal monitoring on each interface again based on the source port list; when the result of the abnormal monitoring indicates that there is no abnormality, publish the VIP route again;

[0106] Step 704: When there is a change in the interface in the static aggregation group, obtain a new interface and determine whether the target source port can cover the data flow of the new interface; if not, obtain a new source port list and perform abnormal monitoring on the new interface based on the new source port list.

[0107] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0108] Based on the same inventive concept, the embodiment of the present application also provides an abnormality monitoring device for implementing the abnormality monitoring method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more abnormality monitoring device embodiments provided below can refer to the limitations of the abnormality monitoring method above, and will not be repeated here.

[0109] In an exemplary embodiment, Figure 8 As shown, an abnormality monitoring device 800 is provided, comprising: a first acquisition module 801, a second acquisition module 802 and an execution module 803, wherein:

[0110] A first acquisition module 801 is used to acquire a source port list of a static aggregation group of the target network element after a Border Gateway Protocol BGP link is established in the target network element, the source port list including target source ports of data flows covering each interface in the static aggregation group;

[0111] The second acquisition module 802 is used to acquire the first data receiving and sending information of each interface after the target network element publishes the VIP route;

[0112] The execution module 803 is used to perform abnormality monitoring on each interface according to the first data receiving and sending information and the source port list, and remove the VIP route when the result of the abnormality monitoring indicates that an abnormality exists.

[0113] In one embodiment, the first acquisition module 801 is specifically used to determine a candidate source port for each of the interfaces based on a preset port range, and send test data to the opposite device based on the candidate source port; after sending the test data, determine whether the interface has receiving and sending data, and if so, use the candidate source port as the target source port corresponding to the interface and store it in the source port list.

[0114] In one embodiment, the execution module 803 is specifically used to determine whether there is a target interface in each interface based on the first data receiving and sending information, and the target interface is an interface that does not receive or send data; if the target interface exists, each interface is monitored for abnormalities based on the source port list.

[0115] In one embodiment, the execution module 803 is specifically used to send preset data to the opposite device based on the target source port included in the source port list; if after the preset time, it is detected that there is an interface among the interfaces that has not received data, the result of the abnormal monitoring is determined to be an abnormality.

[0116] In one embodiment, the execution module 803 is also used to perform abnormality monitoring on each interface again based on the source port list when it is determined that each interface has returned to normal; and to publish the VIP route again when the result of the abnormality monitoring indicates that there is no abnormality.

[0117] In one embodiment, the execution module 803 is also used to obtain a new interface when there is a change in the interface in the static aggregation group, and determine whether the target source port can cover the data flow of the new interface; if not, obtain a new source port list, and perform abnormal monitoring on the new interface based on the new source port list.

[0118] Each module in the above-mentioned abnormal monitoring device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0119] In an exemplary embodiment, a computer device is provided. The computer device may be a network element, and its internal structure diagram may be as shown in FIG. Fig. 9As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an abnormality detection method is implemented.

[0120] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0121] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0122] After establishing a Border Gateway Protocol (BGP) link at the target network element, obtaining a source port list of a static aggregation group of the target network element, the source port list including target source ports of data flows covering each interface in the static aggregation group;

[0123] After the target network element publishes the VIP route, obtaining the first data receiving and sending information of each interface;

[0124] The interfaces are monitored for abnormalities according to the first data receiving and sending information and the source port list, and the VIP route is removed when the result of the abnormality monitoring indicates that an abnormality exists.

[0125] In one embodiment, when the processor executes the computer program, the following steps are also implemented: for each of the interfaces, a candidate source port is determined based on a preset port range, and test data is sent to the opposite device based on the candidate source port; after sending the test data, it is determined whether the interface has received or sent data, and if so, the candidate source port is used as the target source port corresponding to the interface and stored in the source port list.

[0126] In one embodiment, when the processor executes the computer program, the following steps are also implemented: determining whether there is a target interface in each interface based on the first data receiving and sending information, and the target interface is an interface that does not have data for sending and receiving; if the target interface exists, each interface is monitored for abnormalities based on the source port list.

[0127] In one embodiment, when the processor executes the computer program, the following steps are also implemented: preset data is sent to the opposite device based on the target source port included in the source port list; if after a preset time, it is detected that there is an interface among the interfaces that has not received data, then the result of the abnormal monitoring is determined to be an abnormality.

[0128] In one embodiment, when the processor executes the computer program, the following steps are also implemented: when it is determined that each interface has returned to normal, each interface is again monitored for abnormalities based on the source port list; when the result of the abnormal monitoring indicates that there is no abnormality, the VIP route is published again.

[0129] In one embodiment, the processor also implements the following steps when executing the computer program: when there is a change in the interface in the static aggregation group, obtain a new interface and determine whether the target source port can cover the data flow of the new interface; if not, obtain a new source port list and perform abnormal monitoring on the new interface based on the new source port list.

[0130] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0131] After establishing a Border Gateway Protocol (BGP) link at the target network element, obtaining a source port list of a static aggregation group of the target network element, the source port list including target source ports of data flows covering each interface in the static aggregation group;

[0132] After the target network element publishes the VIP route, obtaining the first data receiving and sending information of each interface;

[0133] The interfaces are monitored for abnormalities according to the first data receiving and sending information and the source port list, and the VIP route is removed when the result of the abnormality monitoring indicates that an abnormality exists.

[0134] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: for each of the interfaces, a candidate source port is determined based on a preset port range, and test data is sent to the opposite device based on the candidate source port; after sending the test data, it is determined whether the interface has received or sent data, and if so, the candidate source port is used as the target source port corresponding to the interface and stored in the source port list.

[0135] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining whether there is a target interface in each interface based on the first data receiving and sending information, and the target interface is an interface that does not have data for sending and receiving; if the target interface exists, then performing abnormal monitoring on each interface based on the source port list.

[0136] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: preset data is sent to the opposite device based on the target source port included in the source port list; if after a preset time, it is detected that there is an interface among the interfaces that has not received data, then the result of the abnormal monitoring is determined to be an abnormality.

[0137] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: when it is determined that each interface has returned to normal, each interface is again monitored for abnormalities based on the source port list; when the result of the abnormality monitoring indicates that there is no abnormality, the VIP route is published again.

[0138] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: when there is a change in the interface in the static aggregation group, a new interface is obtained, and it is determined whether the target source port can cover the data flow of the new interface; if not, a new source port list is obtained, and the new interface is monitored for abnormalities based on the new source port list.

[0139] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0140] After establishing a Border Gateway Protocol (BGP) link at the target network element, obtaining a source port list of a static aggregation group of the target network element, the source port list including target source ports of data flows covering each interface in the static aggregation group;

[0141] After the target network element publishes the VIP route, obtaining the first data receiving and sending information of each interface;

[0142] The interfaces are monitored for abnormalities according to the first data receiving and sending information and the source port list, and the VIP route is removed when the result of the abnormality monitoring indicates that an abnormality exists.

[0143] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: for each of the interfaces, a candidate source port is determined based on a preset port range, and test data is sent to the opposite device based on the candidate source port; after sending the test data, it is determined whether the interface has received or sent data, and if so, the candidate source port is used as the target source port corresponding to the interface and stored in the source port list.

[0144] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining whether there is a target interface in each interface based on the first data receiving and sending information, and the target interface is an interface that does not have data for sending and receiving; if the target interface exists, then performing abnormal monitoring on each interface based on the source port list.

[0145] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: preset data is sent to the opposite device based on the target source port included in the source port list; if after a preset time, it is detected that there is an interface among the interfaces that has not received data, then the result of the abnormal monitoring is determined to be an abnormality.

[0146] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: when it is determined that each interface has returned to normal, each interface is again monitored for abnormalities based on the source port list; when the result of the abnormality monitoring indicates that there is no abnormality, the VIP route is published again.

[0147] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: when there is a change in the interface in the static aggregation group, a new interface is obtained, and it is determined whether the target source port can cover the data flow of the new interface; if not, a new source port list is obtained, and the new interface is monitored for abnormalities based on the new source port list.

[0148] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0149] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0150] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. An abnormality monitoring method, characterized in that: The method comprises: After establishing a Border Gateway Protocol (BGP) link in the target network element, obtaining a source port list of a static aggregation group of the target network element, wherein the source port list includes target source ports of data flows covering each interface in the static aggregation group; After the target network element publishes the VIP route, obtaining first data sending and receiving information of each of the interfaces; Each of the interfaces is monitored for abnormalities according to the first data receiving and sending information and the source port list, and when the result of the abnormality monitoring indicates that an abnormality exists, the VIP route is removed.

2. The method according to claim 1, characterized in that The obtaining of the source port list of the static aggregation group of the target network element includes: For each of the interfaces, determining a candidate source port based on a preset port range, and sending test data to a peer device based on the candidate source port; After sending the test data, it is determined whether the interface has transceiver data. If so, the candidate source port is used as the target source port corresponding to the interface and stored in the source port list.

3. The method according to claim 1, characterized in that The performing abnormality monitoring on each of the interfaces according to the first data receiving and sending information and the source port list includes: Determine whether there is a target interface among the interfaces according to the first data receiving and sending information, the target interface being an interface that does not have any data to send or receive; If the target interface exists, abnormality monitoring is performed on each of the interfaces according to the source port list.

4. The method according to claim 3, characterized in that The performing abnormality monitoring on each of the interfaces according to the source port list includes: Sending preset data to the opposite device based on the target source port included in the source port list; If after a preset time, it is detected that there is an interface among the interfaces that has not received data, it is determined that the result of the abnormality monitoring is that an abnormality exists.

5. The method according to claim 1, characterized in that After the VIP route is removed, the method further includes: When it is determined that each of the interfaces has returned to normal, performing abnormality monitoring on each of the interfaces again based on the source port list; When the result of the abnormality monitoring indicates that there is no abnormality, the VIP route is published again.

6. The method according to claim 1, characterized in that The method further comprises: When there is a change in the interface in the static aggregation group, a new interface is acquired, and whether the target source port can cover the data flow of the new interface; If not, a new source port list is obtained, and abnormality monitoring is performed on the new interface based on the new source port list.

7. An abnormality monitoring device, characterized in that: The device comprises: A first acquisition module is used to acquire a source port list of a static aggregation group of the target network element after establishing a Border Gateway Protocol BGP link with the target network element, wherein the source port list includes target source ports of data flows covering each interface in the static aggregation group; A second acquisition module is used to acquire the first data receiving and sending information of each interface after the target network element publishes the VIP route; An execution module is used to perform abnormal monitoring on each of the interfaces according to the first data receiving and sending information and the source port list, and remove the VIP route when the result of the abnormal monitoring indicates that an abnormality exists.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images