Method and apparatus for determining flow traction results based on loop detection

Abstract

This application relates to the field of network security technology, specifically disclosing a method and apparatus for determining traffic redirection results based on loopback probing. The method involves constructing a Registration Protocol (GARP) message based on the EIP-GARP module of the master device and sending the GARP message to the upstream forwarding device. After detecting successful GARP message transmission, a loopback probing message is constructed based on the master device and sent to the upstream forwarding device. When the master device detects that it has received the loopback probing message from the upstream forwarding device, the traffic redirection result is determined to be complete. This application, by constructing and sending a loopback probing message to the upstream forwarding device and detecting whether the master device receives a loopback probing message returned by the upstream forwarding device, determines that the traffic redirection result is complete. This effectively determines the traffic redirection result and monitors problems occurring during the traffic redirection process of the upstream forwarding device.

Description

Technical Field

[0001] This application relates to the field of network security technology, and in particular to a method, apparatus, computer equipment, and storage medium for determining traffic traction results based on loopback detection. Background Technology

[0002] In cloud network scenarios, under a three-layer underlay architecture, the public gateway carrying north-south traffic typically uses BGP for traffic redirection. Under a two-layer underlay architecture (with fewer than 500 nodes), the public gateway typically uses GARP for traffic redirection. However, GARP is a one-way announcement message, which cannot confirm whether the peer device has received and effectively processed the message, nor can it perform effective monitoring and alarms. Consequently, it is impossible to determine the traffic redirection result and to monitor and alarm for problems. Therefore, how to confirm the traffic redirection result of the peer device, effectively discover problems, and monitor and alarm for them has become an urgent problem to be solved. Summary of the Invention

[0003] This application provides a method, apparatus, computer equipment, and storage medium for determining flow traction results based on loopback detection, in order to confirm the flow traction results of the peer device, effectively identify problems, and monitor and alarm.

[0004] Firstly, this application provides a method for determining flow traction results based on loopback detection, the method comprising:

[0005] The registration protocol GARP message is constructed based on the EIP-GARP module of the master device, and the GARP message is sent to the upstream forwarding device;

[0006] After detecting that the GARP message has been successfully sent, the master device constructs a loopback probe message and sends the loopback probe message to the upstream forwarding device;

[0007] When the master device detects that it has received a loopback probe message sent by the upstream forwarding device, it determines that the traffic traction result has been completed.

[0008] Furthermore, the loopback probe message is a message whose source IP address and destination IP address are both the Elastic Public IP Address (EIP) of the master device.

[0009] Furthermore, before determining that the traffic redirection result is complete when the master device detects that it has received a loopback probe message sent by the upstream forwarding device, the process further includes:

[0010] Based on the upstream forwarding device, learn the GARP packets and obtain Address Resolution Protocol (ARP) entries;

[0011] When the ARP entry is valid, the public network traffic is forwarded to the master device based on the ARP entry, and the loopback probe message is returned to the master device.

[0012] Furthermore, after learning the GARP packets based on the upstream forwarding device and obtaining the Address Resolution Protocol (ARP) entries, the method further includes:

[0013] If the ARP entry is invalid, the loopback probe message is discarded or forwarded to another device that is not the master device.

[0014] Furthermore, after detecting that the GARP message has been successfully sent, constructing a loopback probe message based on the master device and sending the loopback probe message to the upstream forwarding device, the method further includes:

[0015] When the master device detects that it has not received the loopback probe message sent by the upstream forwarding device, it continues to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device has not received the loopback probe message.

[0016] Furthermore, after the step of the master device continuing to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device fails to receive the loopback probe message, the method further includes:

[0017] The number of times the master device failed to receive the loopback probe message is obtained;

[0018] The preset threshold number of times is compared with the number of times the master device has not received the loopback detection message;

[0019] When the number of times the master device fails to receive the loopback probe message is not less than the preset threshold, it reports an EIP connectivity problem to the alarm system and reminds maintenance personnel to perform maintenance based on the alarm system.

[0020] Further, sending the loopback detection message to the upstream forwarding device includes:

[0021] The master device periodically sends and receives the loopback detection messages.

[0022] Secondly, this application also provides a flow traction result determination device based on loopback detection, the device comprising:

[0023] The GARP message sending module is used to construct a registration protocol GARP message based on the EIP-GARP module of the master device, and send the GARP message to the upstream forwarding device;

[0024] The loopback probe message sending module is used to construct a loopback probe message based on the master device after detecting that the GARP message has been successfully sent, and to send the loopback probe message to the upstream forwarding device;

[0025] The traffic traction result determination module is used to determine that the traffic traction result has been completed when the master device detects that it has received a loopback probe message sent by the upstream forwarding device.

[0026] Thirdly, this application also provides a computer device, the computer device including a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program and, when executing the computer program, implement the flow traction result determination method based on loopback detection as described above.

[0027] Fourthly, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement the above-described method for determining flow traction results based on loopback detection.

[0028] This application discloses a method, apparatus, computer device, and storage medium for determining traffic redirection results based on loopback probing. The method involves constructing a Registration Protocol (GARP) message based on the EIP-GARP module of a master device and sending the GARP message to an upstream forwarding device. After successfully sending the GARP message, a loopback probing message is constructed based on the master device and sent to the upstream forwarding device. When the master device receives the loopback probing message from the upstream forwarding device, the traffic redirection result is determined to be complete. This application, by constructing and sending a loopback probing message to the upstream forwarding device and detecting whether the master device receives a loopback probing message returned by the upstream forwarding device, determines that the traffic redirection result is complete if such a message is received. This effectively determines the traffic redirection result and monitors problems occurring during the traffic redirection process of the upstream forwarding device. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a schematic flowchart of a first embodiment of a method for determining flow traction results based on loopback detection provided in this application;

[0031] Figure 2 This is a schematic diagram of a flow traction result determination method based on loopback detection provided in an embodiment of this application;

[0032] Figure 3 This is a schematic diagram of the loopback detection message format of a flow traction result determination method based on loopback detection provided in an embodiment of this application;

[0033] Figure 4 This is a schematic diagram of message interaction between the master device and the upstream forwarding device in a method for determining traffic traction results based on loopback detection, provided in an embodiment of this application.

[0034] Figure 5 This is a schematic flowchart of a second embodiment of a method for determining flow traction results based on loopback detection provided in this application;

[0035] Figure 6 This is a schematic flowchart of a third embodiment of a method for determining flow traction results based on loopback detection provided in this application;

[0036] Figure 7 A schematic block diagram of a flow traction result determination device based on loopback detection provided for embodiments of this application;

[0037] Figure 8 A schematic block diagram of the structure of a computer device provided for an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0039] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0040] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0041] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0042] This application provides a method, apparatus, computer device, and storage medium for determining traffic redirection results based on loopback probing. The method can be applied to a server, effectively determining traffic redirection results through loopback probing messages and monitoring problems occurring during traffic redirection by upstream forwarding devices. The server can be a standalone server or a server cluster.

[0043] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0044] Please see Figure 1 , Figure 1 This is a schematic flowchart illustrating a method for determining traffic redirection results based on loopback probing, provided in an embodiment of this application. This method can be applied to servers to effectively determine traffic redirection results using loopback probing messages and monitor problems occurring during traffic redirection by upstream forwarding devices.

[0045] like Figure 1 As shown, the method for determining the flow traction result based on loop detection specifically includes steps S101 to S103.

[0046] S101. Construct a registration protocol GARP message based on the EIP-GARP module of the master device, and send the GARP message to the upstream forwarding device.

[0047] In one embodiment, such as Figure 2As shown, when a cloud host accesses the public network, the traffic is first tunneled and encapsulated by the VM-HOST (virtual host) before being sent to the public network gateway's primary and backup cluster. The public network gateway then performs EIP (Elastic IP Address) mapping and forwards it to Bleaf (Border Leaf, egress gateway). Return traffic is forwarded by Bleaf to the public network gateway's primary node, and then the public network gateway performs address mapping before forwarding it to the cloud host. Here, EIP stands for Elastic Public IP Address, which is an independent public IP resource. Alibaba Cloud's Elastic Public IP Address (Internet Protocol Address) is an independent public IP resource.

[0048] In an underlay Layer 2 network architecture, after the IGW (Internet Gateway) receives the EIP configuration, the IGW needs to send the EIP's GARP (Generic Attribute Registration Protocol) message to Bleaf. In this way, Bleaf can learn the EIP's ARP (Address Resolution Protocol) and generate forwarding table entries. Thus, traffic coming from the public network can be forwarded normally to the public network gateway master device through Bleaf.

[0049] Underlay refers to the actual physical infrastructure network devices, which form the network of the data center's basic forwarding architecture.

[0050] In one embodiment, taking IGW as the master device and Bleaf as the upstream forwarding device as an example, when IGW is the master device, IGW's EIP-GARP module constructs a GARP message and sends the GARP message to Bleaf.

[0051] S102. After detecting that the GARP message has been successfully sent, a loopback probe message is constructed based on the master device and sent to the upstream forwarding device.

[0052] In one embodiment, the loopback probe message is a message whose source IP address and destination IP address are both the Elastic Public IP Address (EIP) of the master device.

[0053] Furthermore, sending the loopback probe message to the upstream forwarding device includes: periodically sending and receiving the loopback probe message based on the master device.

[0054] In one embodiment, IGW periodically constructs UDP-echo packets (both source and destination IPs are EIPs) and sends them to Bleaf. These UDP-echo packets are loopback probe packets.

[0055] In one embodiment, such as Figure 3 As shown, Figure 3 This diagram illustrates the loopback probe message format for a traffic traction result determination method based on loopback probe, as provided in this application embodiment. The Time to Live (TTL), EIP, and IP-header fields in the diagram are special padding fields used to distinguish the message from customer service messages.

[0056] Furthermore, after detecting that the GARP message has been successfully sent, and after constructing a loopback probe message based on the master device and sending the loopback probe message to the upstream forwarding device, the method further includes: when it is detected that the master device has not received the loopback probe message sent by the upstream forwarding device, the master device continues to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device has not received the loopback probe message.

[0057] In one embodiment, the IGW listens for UDP-echo messages (i.e., loopback probe messages). If Bleaf does not loop back the UDP-echo messages sent by the IGW itself, it means that Bleaf has not processed the GARP messages correctly. In this case, the IGW continues to send GARP messages of the problematic EIPs to drive Bleaf to learn.

[0058] In one embodiment, the number of times the IGW fails to receive the UDP-echo message is recorded. If the message is still not received after reaching a set threshold, an alarm message is sent to the monitoring platform.

[0059] S103. When the master device detects that it has received a loopback probe message sent by the upstream forwarding device, it determines that the traffic traction result has been completed.

[0060] In one embodiment, the IGW listens for UDP-echo messages. If Bleaf loops back the UDP-echo messages sent by the IGW itself, it indicates that the EIP-GARP messages sent by the IGW itself were effectively received and correctly processed by Bleaf, indicating that the traffic redirection result has been completed.

[0061] In one embodiment, such as Figure 4 As shown, Figure 4 This diagram illustrates the message interaction between the master device and the upstream forwarding device in a traffic traction result determination method based on loopback probing, as provided in this application embodiment. EIP-GARP and service messages are existing system message types. The curved arrows indicate the loopback probing message proposed in this application.

[0062] The above embodiments provide a method, apparatus, computer device, and storage medium for determining traffic redirection results based on loopback probing. The method involves constructing a Registration Protocol (GARP) message based on the EIP-GARP module of the master device and sending the GARP message to the upstream forwarding device. After successfully sending the GARP message, a loopback probing message is constructed based on the master device and sent to the upstream forwarding device. When the master device receives the loopback probing message from the upstream forwarding device, the traffic redirection result is determined to be complete. This application, by constructing and sending a loopback probing message to the upstream forwarding device and detecting whether the master device receives a loopback probing message returned by the upstream forwarding device, determines that the traffic redirection result is complete if a loopback probing message is received from the upstream forwarding device. This solves the problem of unreliable notification mechanisms in GARP, effectively determines traffic redirection results, and provides monitoring and alarm methods to monitor problems occurring during traffic redirection by the upstream forwarding device, allowing for problem detection before service operations.

[0063] Please see Figure 5 , Figure 5 This is a schematic flowchart illustrating a method for determining traffic redirection results based on loopback probing, provided in an embodiment of this application. This method can be applied to servers to effectively determine traffic redirection results using loopback probing messages and monitor problems occurring during traffic redirection by upstream forwarding devices.

[0064] like Figure 5 As shown, before step S103 of the flow traction result determination method based on loop detection, steps S201 to S202 are also included.

[0065] S201. Based on the upstream forwarding device, learn the GARP message and obtain the Address Resolution Protocol (ARP) entries;

[0066] S202. When the ARP entry is a valid entry, based on the ARP entry, forward the public network traffic to the master device and return the loopback probe message to the master device.

[0067] Furthermore, after learning the GARP message based on the upstream forwarding device and obtaining the Address Resolution Protocol (ARP) entry, the method further includes: when the ARP entry is invalid, discarding the loopback probe message or forwarding the loopback probe message to another device that is not the master device.

[0068] In one embodiment, after receiving a UDP-echo message, Bleaf learns ARP entries based on EIP-GARP.

[0069] In one embodiment, if the ARP entry is a valid entry, packet forwarding is performed based on the ARP entry to achieve traffic redirection, and the UDP-echo packet is returned to the IGW.

[0070] In one embodiment, if no ARP entry exists or the ARP entry is not valid, Bleaf will discard the udp-echo message or forward it to an unintended destination address, i.e., another device that is not the current IGW.

[0071] Please see Figure 6 , Figure 6 This is a schematic flowchart illustrating a method for determining traffic redirection results based on loopback probing, provided in an embodiment of this application. This method can be applied to servers to effectively determine traffic redirection results using loopback probing messages and monitor problems occurring during traffic redirection by upstream forwarding devices.

[0072] like Figure 6 As shown, the method for determining traffic traction results based on loopback detection includes steps S301 to S303, after the master device continues to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device does not receive the loopback detection message.

[0073] S301. Obtain the number of times the master device has not received the loopback detection message.

[0074] S302. Compare the preset number threshold with the number of times the master device has not received the loopback detection message.

[0075] S303. When the number of times the master device fails to receive the loopback probe message is not less than the preset number threshold, it reports an EIP connectivity problem to the alarm system and reminds maintenance personnel to perform maintenance based on the alarm system.

[0076] In one embodiment, when the number of times the master device fails to receive the UDP-echo message reaches a preset threshold, it reports a connectivity problem in the current EIP to the alarm system to remind maintenance personnel to access and handle the issue and perform maintenance.

[0077] In one embodiment, the preset number of times threshold can be set by the user as needed, either in advance in the system or by changing the threshold during execution.

[0078] In another embodiment, when the number of times the master device fails to receive a UDP-echo message does not reach a preset threshold, it continues to send GARP messages to the upstream forwarding device until the master device receives a UDP-echo message sent by the master device itself from the upstream forwarding device or the number of times the master device fails to receive a UDP-echo message does not reach the preset threshold.

[0079] Please see Figure 7 , Figure 7 This application provides a schematic block diagram of a traffic flow traction result determination device based on loopback detection, which is used to execute the aforementioned traffic flow traction result determination method based on loopback detection. The traffic flow traction result determination device based on loopback detection can be configured on a server.

[0080] like Figure 7 As shown, the flow traction result determination device 400 based on loop detection includes:

[0081] The GARP message sending module 401 is used to construct a registration protocol GARP message based on the EIP-GARP module of the master device, and send the GARP message to the upstream forwarding device;

[0082] The loopback probe message sending module 402 is used to construct a loopback probe message based on the master device after detecting that the GARP message has been successfully sent, and to send the loopback probe message to the upstream forwarding device;

[0083] The traffic traction result determination module 403 is used to determine that the traffic traction result has been completed when the master device detects that it has received a loopback probe message sent by the upstream forwarding device.

[0084] Furthermore, the loopback probe message is a message whose source IP address and destination IP address are both the Elastic Public IP Address (EIP) of the master device.

[0085] Furthermore, the flow traction result determination device 400 based on loopback detection also includes a loopback detection message return module, which includes:

[0086] The ARP entry acquisition unit is used to learn the GARP message from the upstream forwarding device and obtain the Address Resolution Protocol (ARP) entry.

[0087] The loopback probe message return unit is used to forward public network traffic to the master device based on the ARP entry when the ARP entry is a valid entry, and to return the loopback probe message to the master device.

[0088] Furthermore, the loopback detection message return module also includes:

[0089] The loopback probe packet discarding unit is used to discard the loopback probe packet or forward the loopback probe packet to other devices that are not the master device when the ARP entry is invalid.

[0090] Furthermore, the flow traction result determination device 400 based on loopback detection also includes:

[0091] The message retransmission module is used to, when the master device detects that it has not received the loopback probe message sent by the upstream forwarding device, continue to send the GARP message to the upstream forwarding device, so as to drive the upstream forwarding device to learn the GARP message and record the number of times the master device has not received the loopback probe message.

[0092] Furthermore, the message retransmission module also includes:

[0093] The count acquisition unit is used to acquire the number of times the master device has not received the loopback detection message;

[0094] The count comparison unit is used to compare a preset count threshold with the number of times the master device has not received the loopback detection message;

[0095] The problem warning unit is used to report a connectivity problem in the EIP to the alarm system when the number of times the master device fails to receive the loopback probe message is not less than the preset number threshold, and to remind the operation and maintenance personnel to perform maintenance based on the alarm system.

[0096] Furthermore, the loopback detection message sending module 402 includes:

[0097] The loopback probe message sending unit is used to periodically send and receive the loopback probe messages based on the master device.

[0098] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the above-described apparatus and modules can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0099] The aforementioned device can be implemented as a computer program, which can be used in, for example... Figure 8 It runs on the computer device shown.

[0100] Please see Figure 8 , Figure 8 This is a schematic block diagram illustrating the structure of a computer device according to an embodiment of this application. The computer device may be a server.

[0101] See Figure 8 The computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include non-volatile storage media and internal memory.

[0102] The non-volatile storage medium can store an operating system and a computer program. This computer program includes program instructions that, when executed, cause the processor to perform any method for determining flow traction results based on loopback probing.

[0103] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0104] The internal memory provides an environment for the execution of computer programs in non-volatile storage media. When the computer program is executed by the processor, it enables the processor to execute any method for determining flow traction results based on loopback detection.

[0105] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0106] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0107] In one embodiment, the processor is configured to run a computer program stored in memory to perform the following steps:

[0108] The registration protocol GARP message is constructed based on the EIP-GARP module of the master device, and the GARP message is sent to the upstream forwarding device;

[0109] After detecting that the GARP message has been successfully sent, the master device constructs a loopback probe message and sends the loopback probe message to the upstream forwarding device;

[0110] When the master device detects that it has received a loopback probe message sent by the upstream forwarding device, it determines that the traffic traction result has been completed.

[0111] In one embodiment, the loopback probe message is a message whose source IP address and destination IP address are both the Elastic Public IP Address (EIP) of the master device.

[0112] In one embodiment, before the processor determines that the traffic pulling result is complete upon detecting that the master device has received a loopback probe message sent by the upstream forwarding device, it is also configured to:

[0113] Based on the upstream forwarding device, learn the GARP packets and obtain Address Resolution Protocol (ARP) entries;

[0114] When the ARP entry is valid, the public network traffic is forwarded to the master device based on the ARP entry, and the loopback probe message is returned to the master device.

[0115] In one embodiment, after the processor learns the GARP packets based on the upstream forwarding device and obtains the Address Resolution Protocol (ARP) entries, it is further configured to:

[0116] If the ARP entry is invalid, the loopback probe message is discarded or forwarded to another device that is not the master device.

[0117] In one embodiment, after the processor detects that the GARP message has been successfully sent, constructs a loopback probe message based on the master device, and sends the loopback probe message to the upstream forwarding device, it is further configured to:

[0118] When the master device detects that it has not received the loopback probe message sent by the upstream forwarding device, it continues to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device has not received the loopback probe message.

[0119] In one embodiment, after the processor implements sending the GARP message to the upstream forwarding device based on the master device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device fails to receive the loopback probe message, it is further configured to implement:

[0120] The number of times the master device failed to receive the loopback probe message is obtained;

[0121] The preset threshold number of times is compared with the number of times the master device has not received the loopback detection message;

[0122] When the number of times the master device fails to receive the loopback probe message is not less than the preset threshold, it reports an EIP connectivity problem to the alarm system and reminds maintenance personnel to perform maintenance based on the alarm system.

[0123] In one embodiment, sending the loopback probe message to the upstream forwarding device includes:

[0124] The master device periodically sends and receives the loopback detection messages.

[0125] The embodiments of this application also provide a computer-readable storage medium storing a computer program, the computer program including program instructions, and the processor executing the program instructions to implement any of the flow traction result determination methods based on loopback detection provided in the embodiments of this application.

[0126] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device.

[0127] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for determining flow traction results based on loopback detection, characterized in that, include: The master device's EIP-GARP module constructs a General Attribute Registration Protocol (GARP) message and sends the GARP message to the upstream forwarding device; After detecting that the GARP message was successfully sent, the master device constructs a loopback probe message and sends the loopback probe message to the upstream forwarding device. The loopback probe message is a message whose source IP address and destination IP address are both the elastic public IP address (EIP) of the master device. When the master device detects that it has received a loopback probe message sent by the upstream forwarding device, it determines that the traffic traction result has been completed.

2. The method for determining flow traction results based on loopback detection according to claim 1, characterized in that, Before determining that the traffic pulling result is complete when the master device detects that it has received a loopback probe message sent by the upstream forwarding device, the process also includes: The upstream forwarding device learns the GARP message and obtains the Address Resolution Protocol (ARP) entries. When the ARP entry is valid, the public network traffic is forwarded to the master device based on the ARP entry, and the loopback probe message is returned to the master device.

3. The method for determining flow traction results based on loopback detection according to claim 2, characterized in that, After the upstream forwarding device learns the GARP message and obtains the Address Resolution Protocol (ARP) table entry, it also includes: If the ARP entry is invalid, the loopback probe message is discarded or forwarded to another device that is not the master device.

4. The method for determining flow traction results based on loopback detection according to claim 1, characterized in that, After the master device constructs a loopback probe message and sends the loopback probe message to the upstream forwarding device upon detecting that the GARP message has been successfully sent, the process further includes: When the master device detects that it has not received the loopback probe message sent by the upstream forwarding device, the master device continues to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and record the number of times the master device has not received the loopback probe message.

5. The method for determining flow traction results based on loopback detection according to claim 4, characterized in that, After the master device continues to send the GARP message to the upstream forwarding device to drive the upstream forwarding device to learn the GARP message and records the number of times the master device fails to receive the loopback probe message, the process further includes: The number of times the master device failed to receive the loopback probe message is obtained; The preset threshold number of times is compared with the number of times the master device has not received the loopback detection message; When the number of times the master device fails to receive the loopback probe message is not less than the preset threshold, it reports an EIP connectivity problem to the alarm system and reminds maintenance personnel to perform maintenance based on the alarm system.

6. The method for determining flow traction results based on loopback detection according to any one of claims 1 to 5, characterized in that, Sending the loopback detection message to the upstream forwarding device includes: The master device periodically sends and receives the loopback detection messages.

7. A flow traction result determination device based on loop detection, characterized in that, include: The GARP message sending module is used to construct the General Attribute Registration Protocol (GARP) message and send the GARP message to the upstream forwarding device; The loopback probe message sending module is used to construct a loopback probe message after detecting that the GARP message has been successfully sent, and send the loopback probe message to the upstream forwarding device. The loopback probe message is a message whose source IP address and destination IP address are both the elastic public IP address (EIP) of the master device. The traffic traction result determination module is used to determine that the traffic traction result has been completed when it receives a loopback probe message sent by the upstream forwarding device.

8. A computer device, characterized in that, The computer device includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the computer program and, in executing the computer program, implement the flow traction result determination method based on loopback detection as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to implement the flow traction result determination method based on loopback detection as described in any one of claims 1 to 6.

Images