Network congestion reason test method and device, equipment, storage medium and computer program product

Abstract

The invention discloses a network congestion reason test method, device and equipment, a storage medium and a computer program product, and the method comprises the steps: starting an ECN marking function in a Spine-Leaf networking architecture of a data center, and carrying out the statistics of the number of ECN messages marked by Spine equipment and Leaf equipment due to congestion; configuring an access control list at the uplink port of the ToR device, and counting the number of messages marked by the ECN of the uplink port of the ToR device; and comparing the number of the ECN messages with the number of the messages marked by the ECN, and determining a network congestion reason according to a comparison result. As the number of the ECN messages marked by the Spine equipment and the Leaf equipment due to congestion is compared with the number of the messages marked by the ECN of the uplink port of the ToR equipment, and the network congestion reason is determined according to the comparison result, compared with the prior art, the efficiency and the accuracy of identifying the congestion reason are improved.

Description

Technical Field

[0001] The present invention relates to the field of network communication technologies, and in particular, to a method, device, equipment, storage medium and computer program product for testing the cause of network congestion. Background Art

[0002] In current society, AI technology has developed rapidly. Especially in the data center network, in order to support distributed AI computing, it is required that the network has no packet loss, low latency, and high bandwidth. Therefore, explicit congestion notification (ECN) is used, and the possibility of packet loss caused by congestion is reduced by pre-marking the packets on the congested link. However, there are many reasons for congestion, and it is impossible to quickly analyze and obtain the specific cause of congestion.

[0003] Therefore, there is an urgent need for a method for testing the cause of network congestion, which can effectively improve the efficiency and accuracy of identifying the cause of congestion. Summary of the Invention

[0004] The main purpose of the present invention is to provide a method, device, equipment, storage medium and computer program product for testing the cause of network congestion, aiming to solve the technical problem that it is difficult to quickly and accurately identify the cause of congestion in the prior art, resulting in low efficiency of network fault troubleshooting.

[0005] To achieve the above object, the present invention provides a method for testing the cause of network congestion, and the method includes the following steps:

[0006] In the Spine-Leaf networking architecture of the data center, enable the ECN marking function, and count the number of ECN packets marked due to congestion on the Spine device and the Leaf device;

[0007] Configure an access control list on the uplink port of the ToR device, and count the number of packets marked with ECN on the uplink port of the ToR device;

[0008] Compare the number of ECN packets with the number of packets marked with ECN, and determine the cause of network congestion according to the comparison result.

[0009] Optionally, the step of comparing the number of ECN packets with the number of packets marked with ECN and determining the cause of network congestion according to the comparison result includes:

[0010] Compare the number of ECN packets with the number of packets marked with ECN to obtain a comparison result;

[0011] If the comparison result is that the number of packets marked with ECN is less than the number of ECN packets, then compare the difference between the number of packets marked with ECN and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a first comparison result;

[0012] If the first comparison result is that the difference between the number of packets marked with ECN and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the cause of network congestion is abnormal packet loss or ECN function failure in the network.

[0013] Optionally, after the step of comparing the number of ECN packets with the number of packets marked with ECN to obtain a comparison result, the following steps are further included:

[0014] If the comparison result is that the number of packets marked with ECN is greater than the number of ECN packets, then compare the difference between the number of packets marked with ECN and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a second comparison result;

[0015] If the second comparison result is that the difference between the number of packets marked with ECN and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the cause of network congestion is packet replication in the network.

[0016] Optionally, the service traffic of the data center is three-layer traffic, and the switches in the Spine layer and Leaf layer of the Spine-Leaf networking architecture of the data center are responsible for east-west traffic forwarding.

[0017] Optionally, the ECN mark is applied to IP unicast packets, the ECN mark remains unchanged during the VXLAN encapsulation or decapsulation process, and each IP unicast packet is marked once.

[0018] Optionally, after the step of comparing the number of ECN packets with the number of packets marked with ECN and determining the cause of network congestion according to the comparison result, the following steps are further included:

[0019] Verify the cause of network congestion to obtain a verification result;

[0020] Analyze the cause of network congestion based on the verification result to obtain an analysis result;

[0021] Generate a warning message according to the analysis result and report the warning message to the network administrator.

[0022] In addition, to achieve the above object, the present invention also proposes a device for testing the cause of network congestion, and the device includes:

[0023] The first quantity statistics module is used to enable the ECN marking function in the Spine-Leaf networking architecture of the data center and count the number of ECN packets marked due to congestion on the Spine devices and Leaf devices;

[0024] The second quantity statistics module is used to configure an access control list on the uplink port of the ToR device and count the number of packets marked with ECN on the uplink port of the ToR device;

[0025] The congestion cause determination module is used to compare the number of ECN packets with the number of packets marked with ECN and determine the network congestion cause according to the comparison result.

[0026] In addition, to achieve the above object, the present invention also provides a network congestion cause testing device, which includes: a memory, a processor, and a network congestion cause testing program stored on the memory and executable on the processor. The network congestion cause testing program is configured to implement the steps of the network congestion cause testing method as described above.

[0027] In addition, to achieve the above object, the present invention also provides a storage medium, on which a network congestion cause testing program is stored. When the network congestion cause testing program is executed by a processor, it implements the steps of the network congestion cause testing method as described above.

[0028] In addition, to achieve the above object, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the network congestion cause testing method as described above.

[0029] The present invention discloses that in the Spine-Leaf networking architecture of the data center, the ECN marking function is enabled to count the number of ECN packets marked due to congestion on the Spine devices and Leaf devices; an access control list is configured on the uplink port of the ToR device to count the number of packets marked with ECN on the uplink port of the ToR device; the number of ECN packets is compared with the number of packets marked with ECN, and the network congestion cause is determined according to the comparison result. Since the present invention compares the number of ECN packets marked due to congestion on the Spine devices and Leaf devices with the number of packets marked with ECN on the uplink port of the ToR device and determines the network congestion cause according to the comparison result, compared with the prior art, the present invention effectively improves the efficiency and accuracy of identifying the cause of congestion, thereby improving the network operation and maintenance efficiency and reliability. Description of the Drawings

[0030] Figure 1 It is a schematic flowchart of the first embodiment of the network congestion cause testing method of the present invention;

[0031] Figure 2 This is an example diagram of the Spine-Leaf networking architecture of the data center in the method for testing the causes of network congestion of the present invention;

[0032] Figure 3 This is a schematic flowchart of the second embodiment of the method for testing the causes of network congestion of the present invention;

[0033] Figure 4 This is a structural block diagram of the first embodiment of the device for testing the causes of network congestion of the present invention;

[0034] Figure 5 This is a schematic structural diagram of the device for testing the causes of network congestion in the hardware operating environment related to the solution of the embodiment of the present invention.

[0035] The realization, functional characteristics and advantages of the object of the present invention will be further described with reference to the embodiments and the accompanying drawings. Specific Embodiments

[0036] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0037] The embodiment of the present invention provides a method for testing the causes of network congestion. Referring to Figure 1 , Figure 1 This is a schematic flowchart of the first embodiment of the method for testing the causes of network congestion of the present invention.

[0038] In this embodiment, the method for testing the causes of network congestion includes steps S10 to S30:

[0039] Step S10: In the Spine-Leaf networking architecture of the data center, enable the ECN marking function and count the number of ECN packets marked due to congestion on the Spine device and the Leaf device.

[0040] It should be noted that the execution subject of this embodiment can be a computer server device with data processing, network communication and program running functions applied to the scenario of testing the causes of network congestion, such as a server, a tablet computer, a smart phone, a vehicle-mounted mobile device, etc., or an electronic device capable of implementing the above functions (for example, a device for testing the causes of network congestion), etc. Hereinafter, a system including a device for testing the causes of network congestion will be taken as an example to illustrate this embodiment and the following embodiments.

[0041] It should be understood that the Spine-Leaf networking architecture is a data center network topology structure, which adopts a flat and non-blocking design and consists of two layers of devices. For example, refer to Figure 2, The Spine-Leaf networking architecture consists of two layers of devices: Spine layer (core layer): Composed of multiple high-performance switches, acting as the network backbone, responsible for the interconnection across Leaf switches. All Spine switches are fully interconnected (Full-Mesh), providing high-bandwidth horizontal expansion capabilities; Leaf layer (access layer): Directly connected to servers or ToR (Top of Rack) switches within the cabinet, responsible for the access and local forwarding of server traffic. Each Leaf switch is connected to all Spine switches to ensure the shortest path forwarding between any two Leafs through the Spine. Among them, the Spine layer focuses on the horizontal traffic across cabinets (such as server A → server B), reducing the number of hops and latency through the full-interconnection design. The Leaf layer processes local traffic (such as communication between servers within the cabinet), avoiding traffic detouring to the Spine layer.

[0042] It can be understood that the above Spine devices and Leaf devices are all Spine devices and Leaf devices in the Spine-Leaf networking architecture, also known as Spine-Leaf layer switches.

[0043] It should be noted that the switches in the Spine layer and Leaf layer of the Spine-Leaf networking architecture in the data center are responsible for east-west traffic forwarding. "East-west traffic forwarding" refers to the process in which network devices (such as switches) handle the horizontal communication between different servers or devices within the data center. For example, when server A needs to send data to server B in the same data center, the data will be uploaded to the Spine switch through the Leaf switch and then downloaded to server B through another Leaf switch. This horizontal transmission process is east-west traffic forwarding.

[0044] It should be understood that ECN (Explicit Congestion Notification) is a network congestion control mechanism designed to reduce the impact of network congestion on performance by actively marking the congestion status instead of relying on traditional packet loss feedback. Its core functions include: Avoiding packet loss: By marking congestion packets, notifying the sender to adjust the sending rate and reducing packet loss caused by congestion; Reducing latency: Triggering congestion control without waiting for packet loss, shortening the response time; Improving throughput: In high-bandwidth, low-latency data center networks, ECN can utilize link resources more efficiently.

[0045] It should be noted that all service traffic in the data center is three-layer traffic. ECN only marks IP unicast packets, and IP unicast packets will not be replicated during the forwarding process unless there is packet replication. Whether there is a VXLAN header or not, the ECN marking of ECN packets is counted as 1, and the number of ECN markings for encapsulation and decapsulation will not change.

[0046] For example, refer toFigure 2 , the number of ECN packets marked due to congestion in the above-mentioned Spine devices and Leaf devices, i.e., the number of packets marked due to congestion in Spine1, Spine2, Leaf1 - Leaf3 in the figure.

[0047] Step S20: Configure an access control list on the uplink port of the ToR device to count the number of packets marked with ECN on the uplink port of the ToR device.

[0048] It should be noted that the full name of the ToR device is Top of Rack Switch (top-of-rack switch), which is a key network device deployed at the top of the server cabinet in the data center network. In the Spine-Leaf networking architecture, the ToR switch (i.e., the ToR device) serves as a component of the Leaf layer and is responsible for the communication between the servers in the cabinet and the upper network (Leaf / Spine switches). The ToR is responsible for forwarding traffic to the ToR. The general convergence ratio of the ToR device is greater than 1 (downlink bandwidth: uplink), and it is mainly responsible for forwarding traffic to each server in the cabinet. Generally, there is no traffic between servers.

[0049] It should be explained that an access control list (ACL) needs to be configured on the uplink port of the ToR device to count the number of packets marked with ECN received. Since the ToR device is a necessary node for traffic from the server to the upper network, counting ECN packets here can more accurately reflect traffic anomalies (such as packet loss, packet replication) in the cabinet.

[0050] It should be understood that ACL stands for Access Control List, which is a mechanism for defining network traffic filtering or resource access permissions through rules. In this embodiment, the ACL is used to identify and count packets carrying the ECN mark, which helps to analyze the cause of network congestion.

[0051] For example, refer to Figure 2 , the number of the above-mentioned ECN-marked packets is the number of ECN-marked packets counted by all the uplink ports of ToR1.1 - ToR3.n in the figure.

[0052] Step S30: Compare the number of ECN packets with the number of packets marked with ECN, and determine the cause of network congestion according to the comparison result.

[0053] It should be noted that the causes of network congestion can include packet loss, ECN failure, link failure, packet replication, or broadcast storm.

[0054] For example, if the number of packets marked with ECN is less than the number of ECN packets, the causes of network congestion are packet loss, ECN failure, or link failure; if the number of packets marked with ECN is greater than the number of ECN packets, the causes of network congestion are packet replication or broadcast storm.

[0055] In a specific implementation, to improve the efficiency and reliability of network operation and maintenance, after the step of comparing the number of ECN packets with the number of packets marked with ECN and determining the cause of network congestion according to the comparison result, the method further includes: verifying the cause of network congestion to obtain a verification result; analyzing the cause of network congestion based on the verification result to obtain an analysis result; generating a warning message according to the analysis result and reporting the warning message to the network administrator.

[0056] This embodiment discloses that in a Spine-Leaf networking architecture of a data center, the ECN marking function is enabled to count the number of ECN packets marked due to congestion on Spine devices and Leaf devices; an access control list is configured on the uplink port of the ToR device to count the number of packets marked with ECN on the uplink port of the ToR device; the number of ECN packets is compared with the number of packets marked with ECN, and the cause of network congestion is determined according to the comparison result. Since this embodiment compares the number of ECN packets marked due to congestion on Spine devices and Leaf devices with the number of packets marked with ECN on the uplink port of the ToR device and determines the cause of network congestion according to the comparison result, compared with the prior art, this embodiment effectively improves the efficiency and accuracy of identifying the cause of congestion, and further improves the efficiency and reliability of network operation and maintenance.

[0057] Reference Figure 3 , Figure 3 is a schematic flowchart of the second embodiment of the method for testing the cause of network congestion of the present invention.

[0058] Based on the above first embodiment, in this embodiment, the step S30 includes steps S301 to S303:

[0059] Step S301: Compare the number of ECN packets with the number of packets marked with ECN to obtain a comparison result.

[0060] Step S302: If the comparison result is that the number of packets marked with ECN is less than the number of ECN packets, compare the difference between the number of packets marked with ECN and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a first comparison result.

[0061] Step S303: If the difference between the number of packets marked with ECN and the number of ECN packets in the first comparison result is greater than the preset threshold of the number of ECN packets, it indicates that the reason for network congestion is abnormal packet loss or ECN function failure in the network.

[0062] It should be noted that after step S301, steps S304 to S305 are further included:

[0063] Step S304: If the comparison result is that the number of packets marked with ECN is greater than the number of ECN packets, compare the difference between the number of packets marked with ECN and the number of ECN packets with the preset threshold of the number of ECN packets to obtain a second comparison result.

[0064] Step S305: If the second comparison result is that the difference between the number of packets marked with ECN and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the reason for network congestion is packet replication in the network.

[0065] It should be understood that the above preset threshold can be custom - set according to the actual situation, and this embodiment does not limit it.

[0066] For example, theoretically, the absolute value of the difference between the number of packets marked with ECN (Count2) and the number of ECN packets (Count1) does not exceed 10% of Count1 (the actual values are different for different devices).

[0067] If Count2 is less than Count1 by more than 10%, it indicates that there is abnormal packet loss in the network (in the presence of ECN, the application layer will slow down sending because of the ECN mark. If there is still congestion - related packet loss, consider ECN failure, link failure, packet loss, etc.).

[0068] If Count2 is greater than Count1 by more than 10%, it indicates that there is a situation of packet replication in the network (such as in a layer - 2 broadcast domain, multicast protocol, etc.).

[0069] This embodiment discloses comparing the number of the ECN packets with the number of the packets marked with ECN to obtain a comparison result; if the comparison result is that the number of the packets marked with ECN is less than the number of the ECN packets, then comparing the difference between the number of the packets marked with ECN and the number of the ECN packets with a preset threshold of the number of the ECN packets to obtain a first comparison result; if the first comparison result is that the difference between the number of the packets marked with ECN and the number of the ECN packets is greater than the preset threshold of the number of the ECN packets, it indicates that the reason for network congestion is abnormal packet loss or ECN function failure in the network. Compared with the prior art, this embodiment discloses the specific implementation steps of comparing the number of ECN packets with the number of the packets marked with ECN to determine the reason for network congestion, further improving the accuracy of identifying the cause of congestion.

[0070] In addition, an embodiment of the present invention further provides a storage medium, on which a network congestion cause test program is stored. When the network congestion cause test program is executed by a processor, the steps of the network congestion cause test method as described above are implemented.

[0071] Refer to Figure 4 , Figure 4 which is a structural block diagram of the first embodiment of the network congestion cause test device of the present invention.

[0072] As Figure 4 shown, the network congestion cause test device proposed by the embodiment of the present invention includes: a first quantity statistics module 501, a second quantity statistics module 502, and a congestion cause determination module 503.

[0073] The first quantity statistics module 501 is configured to enable the ECN marking function in the Spine-Leaf networking architecture of the data center and count the number of ECN packets marked due to congestion by the Spine device and the Leaf device;

[0074] The second quantity statistics module 502 is configured to configure an access control list on the uplink port of the ToR device and count the number of packets marked with ECN on the uplink port of the ToR device;

[0075] The congestion cause determination module 503 is configured to compare the number of the ECN packets with the number of the packets marked with ECN and determine the reason for network congestion according to the comparison result.

[0076] In an embodiment of the present device, in the Spine-Leaf networking architecture of a data center, the ECN marking function is enabled to count the number of ECN packets marked due to congestion on Spine devices and Leaf devices; an access control list is configured on the uplink port of the ToR device to count the number of packets marked with ECN on the uplink port of the ToR device; the number of ECN packets is compared with the number of packets marked with ECN, and the cause of network congestion is determined according to the comparison result. Since in the embodiment of the present device, the number of ECN packets marked due to congestion on Spine devices and Leaf devices is compared with the number of packets marked with ECN on the uplink port of the ToR device, and the cause of network congestion is determined according to the comparison result, compared with the prior art, the embodiment of the present device effectively improves the efficiency and accuracy of identifying the cause of congestion, thereby improving the network operation and maintenance efficiency and reliability.

[0077] Based on the first embodiment of the network congestion cause testing device of the present invention, a second embodiment of the network congestion cause testing device of the present invention is proposed.

[0078] In this embodiment, the congestion cause determination module 503 is further configured to compare the number of ECN packets with the number of packets marked with ECN to obtain a comparison result; if the comparison result is that the number of packets marked with ECN is less than the number of ECN packets, then compare the difference between the number of packets marked with ECN and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a first comparison result; if the first comparison result is that the difference between the number of packets marked with ECN and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the cause of network congestion is abnormal packet loss or ECN function failure in the network.

[0079] The congestion cause determination module 503 is further configured to, if the comparison result is that the number of packets marked with ECN is greater than the number of ECN packets, then compare the difference between the number of packets marked with ECN and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a second comparison result; if the second comparison result is that the difference between the number of packets marked with ECN and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the cause of network congestion is packet replication in the network.

[0080] Other embodiments or specific implementation manners of the network congestion cause testing device of the present invention may refer to the above method embodiments, and will not be elaborated here.

[0081] The present application provides a network congestion cause testing device. The network congestion cause testing device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the network congestion cause testing method in the first embodiment above.

[0082] Reference is made below Figure 5 to FIG., which shows a schematic structural diagram of a network congestion cause testing device suitable for implementing the embodiments of the present application. The network congestion cause testing device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions: tablet computers), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The network congestion cause testing device shown is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0083] As Figure 5 shown, the network congestion cause testing device may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 or a program loaded from a storage device 1003 into a random access memory 1004. In the random access memory 1004, various programs and data required for the operation of the network congestion cause testing device are also stored. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other through a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems may be connected to the input / output interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the network congestion cause testing device to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a network congestion cause testing device having various systems, it should be understood that it is not required to implement or have all the shown systems. More or fewer systems may be alternatively implemented or had.

[0084] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a read-only memory 1002. When the computer program is executed by a processing device 1001, the above functions defined in the methods of the embodiments disclosed in the present application are executed.

[0085] The network congestion cause testing device provided by the present application adopts the network congestion cause testing method in the above embodiments, and can solve the technical problem that it is difficult to quickly and accurately identify the cause of congestion in the prior art, resulting in low efficiency in troubleshooting network failures. Compared with the prior art, the beneficial effects of the network congestion cause testing device provided by the present application are the same as those of the network congestion cause testing method provided by the above embodiments, and other technical features in the network congestion cause testing device are the same as those disclosed in the method of the previous embodiment, and will not be elaborated here.

[0086] It should be understood that each part disclosed in the present application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0087] As described above, the above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present application, and all of them should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0088] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0089] The modules involved in the embodiments described in the present application can be implemented in software or in hardware. In some cases, the name of the module does not constitute a limitation on the unit itself.

[0090] The present application also provides a computer program product, including a computer program, which when executed by a processor implements the steps of the network congestion cause testing method as described above.

[0091] The computer program product provided by the present application can solve the technical problem that it is difficult to quickly and accurately identify the cause of congestion in the prior art, resulting in low efficiency in troubleshooting network failures. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as those of the network congestion cause testing method provided in the above embodiments, and will not be elaborated here.

[0092] It should be noted that in this article, the term "including", "comprising", or any other variant thereof is intended to cover a non-exclusive inclusion, so that a process, method, article, or system including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article, or system. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article, or system including that element.

[0093] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0094] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as a read-only memory / random access memory, magnetic disk, optical disk), and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present invention.

[0095] The above are only the preferred embodiments of the present invention, and do not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present invention, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present invention.

Claims

1. A method for testing the cause of network congestion, characterized in that The method includes: In the Spine-Leaf networking architecture of the data center, enable the ECN marking function and count the number of ECN packets marked due to congestion on Spine devices and Leaf devices; Configure an access control list on the uplink ports of ToR devices and count the number of packets with ECN marking on the uplink ports of the ToR devices; Compare the number of ECN packets with the number of packets with ECN marking, and determine the cause of network congestion according to the comparison result.

2. The network congestion cause testing method according to claim 1, characterized in that The step of comparing the number of ECN packets with the number of packets with ECN marking and determining the cause of network congestion according to the comparison result includes: Compare the number of ECN packets with the number of packets with ECN marking to obtain a comparison result; If the comparison result is that the number of packets with ECN marking is less than the number of ECN packets, then compare the difference between the number of packets with ECN marking and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a first comparison result; If the first comparison result is that the difference between the number of packets with ECN marking and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the cause of network congestion is abnormal packet loss or ECN function failure in the network.

3. The network congestion cause testing method according to claim 2, characterized in that, After the step of comparing the number of ECN packets with the number of packets with ECN marking to obtain a comparison result, it further includes: If the comparison result is that the number of packets with ECN marking is greater than the number of ECN packets, then compare the difference between the number of packets with ECN marking and the number of ECN packets with a preset threshold of the number of ECN packets to obtain a second comparison result; If the second comparison result is that the difference between the number of packets with ECN marking and the number of ECN packets is greater than the preset threshold of the number of ECN packets, it indicates that the cause of network congestion is packet replication in the network.

4. The network congestion cause testing method according to claim 1, wherein The service traffic of the data center is three-layer traffic, and the switches in the Spine layer and Leaf layer of the Spine-Leaf networking architecture of the data center are responsible for east-west traffic forwarding.

5. The network congestion cause testing method according to claim 1, characterized in that The ECN marking is applied to IP unicast packets, and the ECN marking remains unchanged during the VXLAN encapsulation or decapsulation process, and each IP unicast packet is marked once.

6. The network congestion cause testing method according to any one of claims 1-5, characterized in that, After the step of comparing the number of ECN packets with the number of packets with ECN marking and determining the cause of network congestion according to the comparison result, it further includes: Verify the cause of network congestion to obtain a verification result; Analyze the cause of network congestion based on the verification result to obtain an analysis result; Generate a warning message according to the analysis result and report the warning message to the network administrator.

7. A network congestion cause testing device, characterized in that The device includes: A first quantity statistics module, which is used to enable the ECN marking function in the Spine-Leaf networking architecture of the data center and count the number of ECN packets marked due to congestion on Spine devices and Leaf devices; The second quantity statistics module is used to configure an access control list for the uplink port of the ToR device and count the number of packets with ECN markings on the uplink port of the ToR device; The congestion cause determination module is used to compare the number of ECN packets with the number of packets with ECN markings and determine the cause of network congestion according to the comparison result.

8. A network congestion cause testing device, characterized in that, The device includes: a memory, a processor, and a network congestion cause test program stored on the memory and executable on the processor, and the network congestion cause test program is configured to implement the steps of the network congestion cause test method according to any one of claims 1 to 6.

9. A storage medium, characterized in that, A network congestion cause test program is stored on the storage medium, and when the network congestion cause test program is executed by a processor, it implements the steps of the network congestion cause test method according to any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps of the network congestion cause test method according to any one of claims 1 to 6.

Images