Abnormality monitoring method, device, computer device, readable storage medium and program product

Abstract

The application relates to an abnormality monitoring method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: 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 acquired, the source port list comprising target source ports covering data streams of each interface in the static aggregation group; after a VIP route is published at the target network element, first data transceiving information of each interface is acquired; each interface is subjected to abnormality monitoring according to the first data transceiving information and the source port list, and in the case that the result of the abnormality monitoring indicates that there is an abnormality, the VIP route is subjected to a removal treatment. The method effectively improves the efficiency of solving the problem of probabilistic packet loss of a service flow.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to an exception monitoring method and device, computer equipment, computer readable storage medium and computer program product. BACKGROUND

[0002] Link aggregation usually aggregates multiple physical interfaces to form an aggregation group for use, which can effectively improve the bandwidth and reliability of network device link. Link aggregation includes static aggregation and dynamic aggregation. In the static aggregation scenario, since the state information of the corresponding interface of the physical interface in the aggregation group in the opposite end device cannot be determined, the formation of abnormal link will occur in the case of inconsistent interface states at both ends, thereby causing the problem of probabilistic packet loss of service flow.

[0003] In the prior art, the monitoring of abnormal link is usually realized based on both end devices, so as to avoid the occurrence of the problem of probabilistic packet loss of service flow.

[0004] However, since this method needs to rely on both end devices to realize, the efficiency of solving the problem of probabilistic packet loss of service flow is poor. SUMMARY

[0005] Therefore, it is necessary to provide an exception monitoring method and device, computer equipment, computer readable storage medium and computer program product, which can effectively improve the efficiency of solving the problem of probabilistic packet loss of service flow.

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

[0007] After a target network element establishes a border gateway protocol (BGP) link, a source port list of a static aggregation group of the target network element is obtained, the source port list including target source ports covering data streams of interfaces in the static aggregation group;

[0008] After the target network element publishes a VIP route, first data transceiving information of each interface is obtained;

[0009] According to the first data transceiving information and the source port list, each interface is monitored for exception, and in the case that the result of the exception monitoring indicates that there is an exception, the VIP route is removed.

[0010] In one of the embodiments, the source port list of the static aggregation group of the target network element is obtained by: 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, determining whether there is data transceiving for the interface, if there is, taking the candidate source port as a target source port corresponding to the interface, and storing the target source port into the source port list.

[0011] In one of the embodiments, the abnormal monitoring of each of the interfaces based on the first data transceiving information and the source port list comprises: determining whether there is a target interface in each of the interfaces based on the first data transceiving information, the target interface being an interface without data transceiving; if there is the target interface, performing abnormal monitoring of each of the interfaces based on the source port list.

[0012] In one of the embodiments, the abnormal monitoring of each of the interfaces based on the source port list comprises: sending preset data to the peer device based on the target source port contained in the source port list; if after a preset time, it is detected that there is an interface without receiving data in each of the interfaces, it is determined that the result of the abnormal monitoring is abnormal.

[0013] In one of the embodiments, after the VIP route is removed, the method further comprises: in a case where it is determined that each of the interfaces returns to normal, performing abnormal monitoring of each of the interfaces again based on the source port list; in a case where the result of the abnormal monitoring indicates that there is no abnormality, publishing the VIP route again.

[0014] In one of the embodiments, the method further comprises: in a case where there is a change in the interfaces 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 of the new interface based on the new source port list.

[0015] In a second aspect, the application further provides an abnormal monitoring device, comprising:

[0016] A first obtaining module is configured to, after a border gateway protocol (BGP) link of a target network element is established, obtain a source port list of a static aggregation group of the target network element, the source port list comprising a target source port covering data flow of each interface in the static aggregation group;

[0017] A second obtaining module is configured to, after the target network element publishes a VIP route, obtain first data transceiving information of each of the interfaces;

[0018] The execution module is configured to perform abnormality monitoring on each interface according to the first data transceiving information and the source port list, and perform VIP route removal processing in the case that the result of the abnormality monitoring indicates that there is an abnormality.

[0019] In a third aspect, the present application provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method according to any one of the first aspect when executing the computer program.

[0020] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program implements the steps of the method according to any one of the first aspect when executed by a processor.

[0021] In a fifth aspect, the present application provides a computer program product, comprising a computer program, and the computer program implements the steps of the method according to any one of the first aspect when executed by a processor.

[0022] The abnormality monitoring method, device, computer device, computer readable storage medium and computer program product provided in the present application can obtain a source port list of a static aggregation group of a target network element after the target network element establishes a border gateway protocol (BGP) link, the source port list comprising target source ports covering data streams of each interface in the static aggregation group; can obtain first data transceiving information of each interface after the target network element publishes a VIP route; and can perform abnormality monitoring on each interface according to the first data transceiving information and the source port list, and perform VIP route removal processing in the case that the result of the abnormality monitoring indicates that there is an abnormality. The abnormality monitoring method provided in the present application can realize abnormality monitoring on each interface through the first transceiving information of each interface of the target network element and the source port list, and can timely perform VIP route removal processing in the case that an abnormality is monitored, thereby avoiding the problem that the existence of an abnormal link causes probabilistic packet loss of a service flow. Since the abnormality monitoring method provided in the present application can realize the solution to the problem of probabilistic packet loss of a service flow only by relying on a target network element, compared with the prior art which must rely on two end devices, the cost and complexity can be effectively reduced, and the efficiency of solving the problem of probabilistic packet loss of a service flow can be effectively improved. BRIEF DESCRIPTION OF DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other related drawings can be obtained without creative labor.

[0024] Figure 1 a flowchart of a method for obtaining a source port list of a static aggregation group of the target network element in an embodiment;

[0025] Figure 2 a flowchart 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 a flowchart of a method for performing abnormality monitoring on each interface according to the first data transceiving information and the source port list in an embodiment;

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

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

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

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

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

[0032] Figure 9 an internal structural diagram of a computer device in an embodiment. DETAILED DESCRIPTION

[0033] In order to make the objects, technical solutions and advantages of the present application clearer, further detailed description will be made to the present application with reference to 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 generally aggregates multiple physical interfaces to form an aggregation group for use, which can effectively improve the bandwidth and reliability of the network device link. Link aggregation includes static aggregation and dynamic aggregation. In the static aggregation scenario, since the state information of the corresponding interface of the physical interface in the aggregation group in the opposite end device cannot be determined, abnormal link will be formed in the case of inconsistent interface states at both ends, thereby causing the problem of probabilistic packet loss of service flow.

[0035] In the prior art, abnormal link monitoring is mostly implemented based on both end devices, thereby avoiding the occurrence of the problem of probabilistic packet loss of service flow.

[0036] However, since this method needs to rely on two end devices to be implemented, and further leads to poor efficiency in solving the problem of probabilistic packet loss of service flow.

[0037] Therefore, the present application provides an abnormal monitoring method, which can solve the problem of probabilistic packet loss of service flow by relying on a target network element, and can effectively reduce the cost and complexity compared to the prior art which must rely on two end devices, thereby effectively improving the efficiency of solving the problem of probabilistic packet loss of service flow.

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

[0039] In an exemplary embodiment, as shown in Figure 1 The abnormal monitoring method comprises 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 covering data flows of each interface in the static aggregation group.

[0042] Border gateway protocol (BGP) refers to a dynamic routing protocol, and the BGP link is established based on a TCP connection, which can establish a connection between two network devices supporting BGP and communicate through a TCP port.

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

[0044] In some exemplary embodiments, as described above, the static aggregation group is formed by a plurality of interfaces in a static aggregation manner. In the process of data transmission and reception with a peer device, the target network element can send data to the peer device or receive data sent by the peer device through each interface, and the corresponding source port of each interface is different.

[0045] Further, 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 numbers of the source ports corresponding to each interface. Specifically, the source ports corresponding to each interface can be obtained through a socket interface, and the source port list can be determined according to the source ports corresponding to each interface.

[0046] Step 102: After the target network element publishes the VIP route, obtain the first data transmission and reception information of each interface.

[0047] This VIP is also known as a Virtual IP. For example, when data needs to be transmitted over a network, special encapsulation processing is required. In this case, a BGP router can advertise a VXLAN VTEIP address, which is the VIP, for use in the encapsulation of VXLAN tunnels.

[0048] This initial data transmission and reception information can be used to characterize the data transmission and reception status of each interface. For example, it indicates whether each interface is sending or receiving data.

[0049] In some exemplary embodiments, after establishing a BGP link with the peer device, the target network element can first obtain a list of source ports. After obtaining the source port list, it can then publish VIP routes based on the BGP link. After publishing the VIP routes, it can obtain the first data transmission and reception information for each interface. Specifically, the first data transmission and reception information for each interface can be determined by whether traffic exists on each interface.

[0050] Step 103: Perform anomaly monitoring on each interface based on the first data transmission and reception information and the source port list, and remove the VIP route if the anomaly monitoring result indicates that an anomaly exists.

[0051] In some exemplary embodiments, as described above, in static aggregation scenarios, because the status information of the interfaces in the aggregation group corresponding to the interfaces on the peer device cannot be determined, inconsistent interface statuses at both ends can lead to the formation of abnormal links, thereby causing probabilistic packet loss in the service flow. That is, because the target network element cannot determine the status of each interface on the peer device, it cannot detect abnormal links in a timely manner.

[0052] Furthermore, since the various interfaces of the target network element and the various interfaces of the peer device will send and receive data, the first data transmission and reception information of each interface can be monitored to indirectly determine whether there are any abnormalities in the various interfaces of the peer device, so as to identify abnormal links in a timely manner and avoid the occurrence of probabilistic packet loss problems in the service flow.

[0053] Therefore, anomaly monitoring can be performed on each interface based on the first data transmission and reception information and the source port list, and if the anomaly monitoring results indicate that an anomaly exists, the VIP route can be removed.

[0054] Specifically, the first step is to determine whether to perform anomaly monitoring based on the first transmitted and received information. If it is determined that anomaly monitoring should be performed, then anomaly monitoring should be performed on each interface based on the source port list. If the anomaly monitoring results indicate that anomalies exist, the VIP route should be removed.

[0055] The abnormality monitoring method comprises the following steps: obtaining a source port list of a static aggregation group of a target network element after the target network element establishes a border gateway protocol (BGP) link, the source port list comprising target source ports covering data streams of each interface in the static aggregation group; obtaining first data transceiving information of each interface after the target network element publishes a virtual IP (VIP) route; and performing abnormality monitoring on each interface according to the first data transceiving information and the source port list, and performing VIP route removal processing in a case where the abnormality monitoring result indicates that there is an abnormality. The abnormality monitoring method provided in the application can realize abnormality monitoring on each interface through the first transceiving information of each interface of the target network element and the source port list, and can timely perform VIP route removal processing in a case where an abnormality is monitored, thereby avoiding the problem of probabilistic packet loss of a service flow caused by the existence of an abnormal link. The abnormality monitoring method provided in the application can realize the solution to the problem of probabilistic packet loss of a service flow only by relying on a target network element, thereby effectively reducing cost and complexity compared with the prior art which must rely on both end devices, and effectively improving the efficiency of solving the problem of probabilistic packet loss of a service flow.

[0056] In one exemplary embodiment, as shown in Figure 2 The source port list of the static aggregation group of the target network element comprises the following steps:

[0057] Step 201: For each of the interfaces, determining a candidate source port based on a preset port range, and sending test data to the opposite end 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 can be 1024-65535.

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

[0060] The test data can 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 in the preset port range, a source port corresponding to the port number is determined as a candidate source port, and test data is sent to the opposite end device based on the candidate source port.

[0062] The source port range is set to 1024-65535 to ensure that there are enough target source ports for diversified abnormality monitoring, avoiding port conflict and other problems affecting the monitoring results.

[0063] Step 202: After sending the test data, it is determined whether there is data transceiving of the interface. If there is, the candidate source port is taken as the target source port corresponding to the interface and stored 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 there is data transceiving of the interface. If there is data transceiving, it can be determined that the source port covers the data flow of the interface. If there is no data transceiving, it can be determined that the source port does not cover the data flow of the interface.

[0065] Further, if there is no data transceiving, a port number can be randomly determined again in the preset port range, and the source port corresponding to the port number is determined as a new candidate source port. Test data is sent to the peer device based on the new candidate source port, and after sending the test data, it is determined again whether there is data transceiving of 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 target source port corresponding to 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 port can be randomly determined in the preset port range, or the candidate source port can be determined according to a certain preset rule. If the number of interfaces is N, the determined target source port is at least N and at most 2N. Optionally, the determined source port list can be [4596, 6553, 9447, 25698, 45698].

[0068] In an exemplary embodiment, as shown in Figure 3 Abnormality monitoring of each interface according to the first data transceiving information and the source port list includes the following steps:

[0069] Step 301: It is determined according to the first data transceiving information whether there is a target interface in each interface.

[0070] The target interface is an interface without data transceiving. Here, the data transceiving refers to any one of the received data or the transmitted data.

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

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

[0073] Step 302: If the target interface exists, then the source port list is used to perform abnormality monitoring on each interface.

[0074] In some example embodiments, if it is determined according to the first data transceiving information that the target interface exists in each interface, then the source port list can be used to perform abnormality monitoring on each interface to determine whether there is an abnormal link.

[0075] In an optional embodiment of the present application, if it is determined according to the first data transceiving information that the target interface does not exist in each interface, then the abnormality monitoring can not be performed, or the abnormality monitoring can also be performed. The specific implementation steps of performing the abnormality monitoring are described below.

[0076] In an example embodiment, as shown in FIG. 4, the abnormality monitoring on each interface according to the source port list includes the following steps: Figure 4

[0077] Step 401: Based on the target source port included in the source port list, preset data is sent to the opposite device.

[0078] Optionally, the preset data can be data preset by a technician according to actual needs.

[0079] For example, the preset data can be determined according to abnormality monitoring configuration information. The abnormality monitoring configuration information includes a local IP, a destination IP of the opposite device, a local port, a destination port of the opposite device and a protocol type. The test data described above can also be determined according to the abnormality monitoring configuration information.

[0080] In some example embodiments, if it is determined that the target interface exists in each interface, then the target source port corresponding to each interface can be determined according to the source port list, and the preset data can 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 these interfaces that has not received data, then the result of the anomaly monitoring is determined to be an anomaly.

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

[0083] In some exemplary embodiments, after sending preset data to the peer device based on the target source ports included in the source port list, a preset time is waited. If, within the preset time period, 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 anomaly monitoring is that there is an anomaly.

[0084] In an optional embodiment of this application, after sending preset data to the peer device based on the target source ports included in the source port list, a preset time is waited. During the preset time period, if it is detected that there are interfaces that have not received data, the above steps are followed to perform anomaly monitoring for a preset number of times. If it is detected that there are interfaces that have not received data three times in a row, the result of the anomaly monitoring is determined to be an anomaly.

[0085] As mentioned above, if the target interface is not found among the interfaces based on the first data transmission and reception information, anomaly monitoring can be performed either not or performed. Anomaly monitoring can be performed only once; that is, if a target interface exists, a preset number of anomaly monitoring operations must be performed. If multiple consecutive anomaly monitoring results indicate an anomaly, then an abnormal link is confirmed. If no target interface exists, anomaly monitoring can be performed only once.

[0086] In one exemplary embodiment, such as Figure 5 As shown, after removing the VIP route, the method also includes the following steps:

[0087] Step 501: After confirming that each interface has returned to normal, perform anomaly monitoring on each interface again based on the source port list.

[0088] In some exemplary embodiments, if the anomaly monitoring results indicate an anomaly, the VIP route can be removed. After the VIP route is removed, each interface will be restored.

[0089] Furthermore, after confirming that all interfaces have returned to normal, anomaly monitoring can be performed on each interface again based on the source port list. Specifically, based on each target source port in the source port list, preset data is first sent to the peer device, and after a preset event, it is checked whether each interface receives data, so as to determine the anomaly detection result based on the detection result.

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

[0091] In some example embodiments, if it is detected that there is received data in each interface, it can be determined that the result of the abnormality monitoring is that there is no abnormality, and then the VIP route is published again.

[0092] In an optional embodiment of the present application, in the case that it is determined that the result of the abnormality monitoring is that there is no abnormality, the abnormality monitoring of each interface can be continued for a preset time length, and if the result of the abnormality monitoring that there is no abnormality continues for the preset time length, the VIP route is published again.

[0093] In an example embodiment, as shown in FIG. 6, in the case that there is a change in the interfaces in the static aggregation group, the method further includes the following steps: Figure 6

[0094] Step 601, a new interface is acquired, and it is determined whether the target source port can cover the data flow of the new interface.

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

[0096] For example, there are four interfaces in total, which are interfaces A1, A2, A3 and A4, wherein the state of the A4 interface changes from UP to DOWN, and then it can be determined that the new interfaces are A1, A2 and A3.

[0097] Further, after the new interface is acquired, 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, the target source port can send data to the peer device based on each target source port, and it is detected whether there is received and transmitted data in each interface, and it is determined whether the target source port can cover the data flow of the new interface according to the detection result.

[0099] Step 602, if not, a new source port list is acquired, and the new interface is monitored based on the new source port list.

[0100] ​In some example embodiments, if it is determined that the target source port cannot cover the data stream of the new interface, a new source port list is obtained, that is, for each interface in the new interface, 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 there is data transmission and reception for the interface, if there is, the candidate source port is taken 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 abnormally monitored based on the new source port list. The specific abnormal monitoring steps can refer to the related content of the abnormal monitoring described above, which will not be described here.

[0102] In one example embodiment, as shown in Figure 7 Another abnormal monitoring method is provided, which includes the following steps:

[0103] Step 701, after a border gateway protocol (BGP) link is established at 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 peer device based on the candidate source port; after sending the test data, it is determined whether there is data transmission and reception for the interface, if there is, the candidate source port is taken as the target source port corresponding to the interface, and stored in the source port list; the source port list includes target source ports covering data streams of interfaces in the static aggregation group;

[0104] Step 702, after the target network element publishes a VIP route, first data transmission and reception information of each interface is obtained; it is determined whether there is a target interface in each interface according to the first data transmission and reception information, the target interface being an interface without data transmission and reception; if the target interface exists, preset data is sent to the peer device based on the target source port contained in the source port list; if after a preset time, it is detected that there is an interface without receiving data in each interface, it is determined that the result of the abnormal monitoring is abnormal, and in the case that the result of the abnormal monitoring indicates that there is an abnormality, the VIP route is removed;

[0105] Step 703, in the case that each interface is determined to be normal, each interface is again abnormally monitored based on the source port list; in the case that the result of the abnormal monitoring indicates that there is no abnormality, the VIP route is published again;

[0106] Step 704, in the case of a change in the interfaces in the static aggregation group, a new interface is acquired, and it is determined whether the target source port can cover the data stream of the new interface; if not, a new source port list is acquired, and the new interface is abnormally monitored based on the new source port list.

[0107] It should be understood that, although each step in the flowchart involved in each embodiment as described above is shown in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other sequences. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least part of other steps or steps or stages in other steps.

[0108] Based on the same inventive concept, the embodiments of the present application also provide an abnormal monitoring device for implementing the above-mentioned abnormal monitoring method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more abnormal monitoring device embodiments provided below can refer to the limitations of the abnormal monitoring method in the above text, which will not be repeated here.

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

[0110] The first acquisition module 801 is configured to acquire a source port list of a static aggregation group of a target network element after the target network element establishes a border gateway protocol (BGP) link, the source port list including target source ports covering data streams of interfaces in the static aggregation group;

[0111] The second acquisition module 802 is configured to acquire first data transceiving information of each interface after the target network element publishes a VIP route.

[0112] The execution module 803 is configured to abnormally monitor each interface according to the first data transceiving information and the source port list, and to remove the VIP route in the case of an abnormal result of the abnormal monitoring.

[0113] In an embodiment, the first obtaining module 801 is specifically configured to, for each of the interfaces, determine a candidate source port based on a preset port range, and send test data to a peer device based on the candidate source port; after sending the test data, determine whether there is transceiving data for the interface, if there is, take the candidate source port as a target source port corresponding to the interface, and store it into the source port list.

[0114] In an embodiment, the executing module 803 is specifically configured to determine whether there is a target interface in each of the interfaces according to the first data transceiving information, the target interface being an interface without transceiving data; if there is the target interface, perform abnormality monitoring on each of the interfaces according to the source port list.

[0115] In an embodiment, the executing module 803 is specifically configured to send preset data to the peer device based on the target source port contained in the source port list; if after a preset time, it is detected that there is an interface without receiving data in each of the interfaces, it is determined that the result of the abnormality monitoring is abnormal.

[0116] In an embodiment, the executing module 803 is further configured to, in a case where it is determined that each of the interfaces returns to normal, perform abnormality monitoring on each of the interfaces again based on the source port list; in a case where the result of the abnormality monitoring indicates that there is no abnormality, publish the VIP route again.

[0117] In an embodiment, the executing module 803 is further configured to, in a case where there is a change in the interfaces 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 abnormality monitoring on the new interface based on the new source port list.

[0118] Each of the above-mentioned abnormality monitoring apparatuses can be realized by software, hardware and combinations thereof in whole or in part. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a memory in a computer device in software form, so as to be called and executed by a processor to perform operations corresponding to each of the above-mentioned modules.

[0119] In an exemplary embodiment, a computer device is provided, which can be a network element, and an internal structure diagram thereof can be as shown in Figure 9As shown in the figure. 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 the 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 capability. 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 the external device. The communication interface of the computer device is used to communicate with the terminal outside through the network connection. The computer program is executed by the processor to implement an exception detection method.

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

[0121] In one exemplary embodiment, a computer device is provided, including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the following steps:

[0122] After the target network element establishes a border gateway protocol BGP link, a source port list of a static aggregation group of the target network element is obtained, and the source port list includes target source ports covering data streams of interfaces in the static aggregation group;

[0123] After the target network element publishes a VIP route, first data transceiving information of each interface is obtained;

[0124] According to the first data transceiving information and the source port list, each interface is monitored for exceptions, and in the case where the result of the exception monitoring indicates that there is an exception, the VIP route is removed.

[0125] In one embodiment, the processor executing the computer program further implements the following steps: for each of the interfaces, determining a candidate source port based on a preset port range, and sending test data to the peer device based on the candidate source port; after sending the test data, determining whether there is data transceiving for the interface, if so, taking the candidate source port as a target source port corresponding to the interface, and storing it in the source port list.

[0126] In one embodiment, the processor, when executing the computer program, further implements the following steps: determining whether there is a target interface in each of the interfaces according to the first data transceiving information, the target interface being an interface without data transceiving; and if the target interface exists, performing abnormality monitoring on each of the interfaces according to the source port list.

[0127] In one embodiment, the processor, when executing the computer program, further implements the following steps: sending preset data to the peer device based on a target source port included in the source port list; and if after a preset time, it is detected that there is an interface without data reception in each of the interfaces, determining that the result of the abnormality monitoring is abnormality.

[0128] In one embodiment, the processor, when executing the computer program, further implements the following steps: if it is determined that each of the interfaces returns to normal, performing abnormality monitoring on each of the interfaces again based on the source port list; and if the result of the abnormality monitoring indicates that there is no abnormality, issuing the VIP route again.

[0129] In one embodiment, the processor, when executing the computer program, further implements the following steps: if there is a change in the interfaces 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 abnormality monitoring on the new interface based on the new source port list.

[0130] In one embodiment, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the following steps:

[0131] After a target network element establishes a border gateway protocol (BGP) link, obtaining a source port list of a static aggregation group of the target network element, the source port list including a target source port covering data flow of each interface in the static aggregation group;

[0132] After the target network element issues a VIP route, obtaining first data transceiving information of each of the interfaces;

[0133] Performing abnormality monitoring on each of the interfaces according to the first data transceiving information and the source port list, and if the result of the abnormality monitoring indicates that there is abnormality, performing removal processing on the VIP route.

[0134] In one embodiment, the computer program, when executed by the processor, further implements the following steps: for each of the interfaces, determining a candidate source port based on a preset port range, and sending test data to the peer device based on the candidate source port; and after sending the test data, determining whether there is data transceiving in the interface, if there is, taking the candidate source port as a target source port corresponding to the interface, and storing the target source port into the source port list.

[0135] In one embodiment, the computer program, when executed by the processor, further implements the following steps: determining whether there is a target interface in each of the interfaces according to the first data transceiving information, the target interface being an interface without transceiving data; and if the target interface exists, performing abnormality monitoring on each of the interfaces according to the source port list.

[0136] In one embodiment, the computer program, when executed by the processor, further implements the following steps: sending preset data to the peer device based on a target source port included in the source port list; and if after a preset time, it is detected that there is an interface without receiving data in each of the interfaces, determining that the result of the abnormality monitoring is abnormality.

[0137] In one embodiment, the computer program, when executed by the processor, further implements the following steps: in the case that it is determined that each of the interfaces returns to normal, performing abnormality monitoring on each of the interfaces again based on the source port list; and in the case that the result of the abnormality monitoring indicates that there is no abnormality, publishing the VIP route again.

[0138] In one embodiment, the computer program, when executed by the processor, further implements the following steps: in the case that there is a change in the interfaces 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 abnormality monitoring on the new interface 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 a target network element establishes a border gateway protocol (BGP) link, obtaining a source port list of a static aggregation group of the target network element, the source port list including a target source port covering data flow of each interface in the static aggregation group;

[0141] After the target network element publishes a VIP route, obtaining first data transceiving information of each of the interfaces;

[0142] Performing abnormality monitoring on each of the interfaces according to the first data transceiving information and the source port list, and in the case that the result of the abnormality monitoring indicates that there is abnormality, performing removal processing on the VIP route.

[0143] In one embodiment, the computer program, when executed by the processor, further implements the following steps: for each of the interfaces, determining a candidate source port based on a preset port range, and sending test data to the peer device based on the candidate source port; after sending the test data, determining whether there is transceiving data in the interface, and if so, taking the candidate source port as a target source port corresponding to the interface and storing it into the source port list.

[0144] In one embodiment, the computer program, when executed on the processor, further implements the following steps: determining whether there is a target interface in each of the interfaces according to the first data transceiving information, the target interface being an interface in which data is not transmitted or received; and if the target interface exists, performing abnormality monitoring on each of the interfaces according to the source port list.

[0145] In one embodiment, the computer program, when executed on the processor, further implements the following steps: sending preset data to the opposite device based on a target source port included in the source port list; and if, after a preset time, it is detected that there is an interface in each of the interfaces in which data is not received, determining that the result of the abnormality monitoring is abnormality.

[0146] In one embodiment, the computer program, when executed on the processor, further implements the following steps: in a case where it is determined that each of the interfaces returns to normal, performing abnormality monitoring on each of the interfaces again based on the source port list; and in a case where the result of the abnormality monitoring indicates that there is no abnormality, issuing the VIP route again.

[0147] In one embodiment, the computer program, when executed on the processor, further implements the following steps: in a case where there is a change in the interfaces in the static aggregation group, obtaining a new interface and determining whether the target source port can cover a data stream of the new interface; if not, obtaining a new source port list and performing abnormality monitoring on the new interface based on the new source port list.

[0148] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to 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. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0149] The technical features of the above embodiments can be combined in any manner. To make the description concise, not all possible combinations of the technical features in the above embodiments are described, but as long as the combinations of the technical features do not exist contradictions, they should be considered as the scope of the present application.

[0150] The above-described embodiments are merely illustrative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as a limitation on the scope of the patent. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of protection of the present application should be subject to the appended claims.

Claims

1. An anomaly monitoring method characterized by, The method comprises: After a target network element establishes a border gateway protocol (BGP) link, a source port list of a static aggregation group of the target network element is acquired, the source port list comprising target source ports covering data streams of each interface in the static aggregation group; After the target network element publishes a VIP route, first data transceiving information of each interface is acquired; According to the first data transceiving information and the source port list, each interface is monitored for abnormalities, and in a case where the monitoring result indicates an abnormality, the VIP route is removed.

2. The method of claim 1, wherein, The acquisition of the source port list of the static aggregation group of the target network element comprises: For each of the interfaces, a candidate source port is determined based on a preset port range, and test data is sent to a peer device based on the candidate source port; After the test data is sent, it is determined whether the interface transceives data, and if so, the candidate source port is taken as a target source port corresponding to the interface and stored in the source port list.

3. The method of claim 1, wherein, The monitoring of each interface for abnormalities according to the first data transceiving information and the source port list comprises: It is determined whether there is a target interface in each interface according to the first data transceiving information, the target interface being an interface that does not transceive data; If there is the target interface, each interface is monitored for abnormalities according to the source port list.

4. The method of claim 3, wherein, The monitoring of each interface for abnormalities according to the source port list comprises: Preset data is sent to a peer device based on a target source port contained in the source port list; If after a preset time, it is detected that there is an interface that does not receive data in each interface, it is determined that the monitoring result is an abnormality.

5. The method of claim 1, wherein, After the VIP route is removed, the method further comprises: In a case where each interface is determined to be normal, each interface is monitored for abnormalities again based on the source port list; In a case where the monitoring result indicates no abnormality, the VIP route is published again.

6. The method of claim 1, wherein, The method further comprises: In a case where an interface in the static aggregation group changes, a new interface is acquired, and it is determined whether the target source port can cover data streams of the new interface; If not, a new source port list is acquired, and each new interface is monitored for abnormalities based on the new source port list.

7. An anomaly monitoring apparatus characterized by comprising: The device comprises: A first acquisition module is configured to acquire, after a target network element establishes a border gateway protocol (BGP) link, a source port list of a static aggregation group of the target network element, the source port list comprising target source ports covering data streams of each interface in the static aggregation group; A second acquisition module is configured to acquire, after the target network element publishes a VIP route, first data transceiving information of each interface; An execution module is configured to monitor each interface for abnormalities according to the first data transceiving information and the source port list, and in a case where the monitoring result indicates an abnormality, remove the VIP route.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method of any one of claims 1 to 6.

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

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

Images