A flow detection method, network device and storage medium
By acquiring the iFIT header information of traffic through the NP chip and matching it with the mapping table, the problem of locating network traffic packet loss faults is solved, enabling intuitive identification and intelligent processing of fault causes and simplifying the fault diagnosis process.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- NEW H3C TECH CO LTD
- Filing Date
- 2023-04-27
- Publication Date
- 2026-07-07
AI Technical Summary
Existing technologies cannot effectively locate the fault points and causes of network traffic packet loss, resulting in difficulties in troubleshooting, time and effort consumption, and an inability to handle issues intelligently.
The iFIT header information of the traffic is obtained by the NP chip and matched with the flow detection mapping table to obtain the counter address, record the number of lost packets and error codes, and periodically report to the management platform to achieve intuitive discovery of the cause of the fault.
It enables intuitive identification of the causes of network traffic packet loss, simplifies the troubleshooting process, reduces labor costs, and improves the level of intelligence in fault handling.
Smart Images
Figure CN116319259B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a method for detecting traffic, a network device, and a storage medium. Background Technology
[0002] iFIT (in-situ Flow Information Telemetry) is a detection method that directly measures service packets to obtain the actual packet loss rate, latency, and other performance indicators of the IP network. It has outstanding advantages such as convenient deployment and high statistical accuracy.
[0003] like Figure 1 As shown, the iFIT network framework mainly involves three objects: the target flow, the transit network that the target flow traverses, and the statistical system.
[0004] Depending on the detection granularity, the target flow can be generated in the following ways at the Ingress probe point:
[0005] At the granularity of detection based on the five-tuple, the relevant fields in the IP header can be used to uniquely identify the data, including the five-tuple of source IP address, destination IP address, protocol number, source port number, and destination port number, as well as the Differentiated Services Code Point (DSCP). This method is suitable for performance testing of specific flows.
[0006] Within a certain statistical period, the difference between the time when the same service flow enters the network and the time when it leaves the network between two specified network nodes is the network latency within that statistical period.
[0007] This type of traffic detection does detect information such as traffic latency and packet loss rate, but it cannot pinpoint the fault location or determine the cause of the fault. Summary of the Invention
[0008] This disclosure provides a traffic detection method, network device, and storage medium. Through this method, the cause of packet loss and the number of packet loss statistics of NP chip can be detected by traffic flow and sent to the platform, allowing developers, operators, and customers to more intuitively discover the cause of the fault and take corresponding measures based on the cause.
[0009] This disclosure provides a method for detecting traffic flow, the method comprising:
[0010] The NP chip acquires the flow detected by the flow and obtains the iFIT header information of that flow;
[0011] The iFIT header information is matched with the flow detection mapping table, and the counter address corresponding to the flow is obtained based on the matching result.
[0012] The number of lost packets and error codes of the traffic are saved to the counter address, and the information stored in the counter address is periodically reported to the management platform.
[0013] Optionally, the matching based on the iFIT header information and the flow detection mapping table includes:
[0014] If it is determined that there is no flow monitoring mapping table that matches the iFIT header information, the iFIT header information will be reported to the driver.
[0015] The receiving driver sends the flow detection mapping table based on the iFIT header information, and matches it with the flow detection mapping table received from the driver. Based on the matching result, the counter address corresponding to the flow is obtained.
[0016] Optionally, after obtaining the counter address corresponding to the traffic, the method further includes:
[0017] The flow information of the traffic is saved to the counter address.
[0018] Optionally, the step of periodically reporting the information stored in the counter address to the management platform includes:
[0019] The information stored in the counter address during the cycle is saved to the driver software node and reported to the management platform at the end of the cycle.
[0020] As can be seen from the above embodiments, the NP chip can match the iFIT header information with the flow detection mapping table to obtain the counter address in the flow detection process. This counter address is used to record information such as the number of lost packets and error codes. The information in the counter address can be reported to the management platform, enabling developers, operators, and customers to more intuitively discover the cause of packet loss faults through the management platform and take corresponding measures based on the cause of the fault.
[0021] This disclosure also provides a network device, the network device comprising:
[0022] The acquisition module is used to acquire the flow detected by the NP chip and to acquire the iFIT header information of the flow.
[0023] The matching module is used to match the iFIT header information with the flow detection mapping table, and obtain the counter address corresponding to the flow based on the matching result;
[0024] The processing module is used to save the number of lost packets and error codes of the traffic to the counter address, and periodically report the information stored in the counter address to the management platform.
[0025] The matching module is also used to report the iFIT header information to the driver if it is determined that there is no flow monitoring mapping table that matches the iFIT header information.
[0026] The receiving driver sends the flow detection mapping table based on the iFIT header information, and matches it with the flow detection mapping table received from the driver. Based on the matching result, the counter address corresponding to the flow is obtained.
[0027] The processing module is further configured to save the flow information of the traffic to the counter address.
[0028] Specifically, the processing module is used to save the information stored in the counter address within the cycle to the driver software node, and report it to the management platform at the end of the cycle.
[0029] This disclosure also provides a network device, which includes a memory, a processor, and a program stored on the network device and executable on the processor. When the program is executed by the processor, it implements the method steps in any of the above embodiments.
[0030] This disclosure also provides a computer-readable storage medium storing a program that, when executed by a processor, implements the method steps of any of the above embodiments. Attached Figure Description
[0031] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this specification and, together with the description, serve to explain the principles of this specification.
[0032] Figure 1 This is a schematic diagram of an iFIT network framework provided in an embodiment of this disclosure.
[0033] Figure 2 This is a flowchart illustrating a traffic detection method provided in an embodiment of the present disclosure. Detailed Implementation
[0034] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.
[0035] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
[0036] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."
[0037] Because current flow monitoring systems cannot pinpoint the fault location and cause based on information such as latency and packet loss rate, the following problems arise:
[0038] 1. Packet loss failure with unknown cause: The cause is unclear, making further processing difficult.
[0039] 2. Difficulty in locating instantaneous packet loss: Instantaneous or sporadic packet loss makes it difficult to reconstruct the scene and locate the source of the problem.
[0040] 3. Troubleshooting is difficult: It requires senior experts to troubleshoot step by step, which is time-consuming and labor-intensive.
[0041] 4. Impact on future development: In many cases, the only solution is to replace equipment or adjust the path, which is costly; it also prevents intelligent operation.
[0042] To address the aforementioned technical problems, embodiments of this disclosure provide a method for detecting traffic flow, such as... Figure 2 As shown, the method includes:
[0043] The S201NP chip acquires the flow rate detected by the flow and obtains the iFIT header information of that flow rate;
[0044] S202 matches the iFIT header information with the flow detection mapping table and obtains the counter address corresponding to the flow based on the matching result;
[0045] S203 saves the number of lost packets and error codes of the traffic to the counter address, and periodically reports the information stored in the counter address to the management platform.
[0046] In step S201, after the flow rate detected by the flow sensor enters the NP chip from the optical film block, the iFIT header information is obtained.
[0047] In this embodiment, an iFIT mapping table can also be set up. This iFIT mapping table records the counter address corresponding to each iFIT header information. The counter address can be understood as a cache area, which can be used to record counting results and fault codes.
[0048] In step S202, if it is determined that there is no flow monitoring mapping table that matches the iFIT header information, the iFIT header information is reported to the driver.
[0049] The receiving driver sends the flow detection mapping table based on the iFIT header information, and matches it with the flow detection mapping table received from the driver. Based on the matching result, the counter address corresponding to the flow is obtained.
[0050] In step S203, after obtaining the counter address corresponding to the traffic, the flow information of the traffic is saved to the counter address. It should be noted that the counter can not only be used to save fault information and packet loss information, but also to perform traffic statistics for normal traffic.
[0051] In step S203, when the NP chip reports packet loss information to the driver, it saves the information stored in the counter address within the cycle to the driver software node and reports it to the management platform at the end of the cycle.
[0052] To illustrate this embodiment in detail, this disclosure also provides a traffic detection method, wherein the microcode can be understood as an NP chip. When traffic enters the NP from the optical module card, the microcode extracts the iFIT header information of the traffic and matches it with the flow detection mapping table (ifitmapping table) to obtain an address for recording the traffic detection information. Typically, different detection results correspond to different addresses, making it difficult to query all detection information for a specific traffic. By matching the iFIT header information with the flow detection mapping table (ifitmapping table), a normalized counter address can be obtained for storing each detection information.
[0053] Subsequently, the detection information of the traffic can be reported to the driver. This detection information includes information on normal traffic and information on abnormal traffic. If an abnormal traffic occurs, the flow information and error code can be reported to the driver at the same time, so that the driver can report the above information to the management platform.
[0054] When the driver reports information to the management platform, it can store the packet loss information (error codes, etc.) within the driver's soft node during the current period and report it to the management platform periodically. This periodic reporting can be understood as the information stored in the previous period.
[0055] As can be seen from the above embodiments, the method in this disclosure can realize the transmission of packet loss causes and packet loss statistics based on flow-based NP packet loss to the platform, allowing developers, operators, and customers to more intuitively discover the causes of faults and take corresponding measures based on the causes.
[0056] Based on the above method embodiments, this disclosure also provides a network device, which includes:
[0057] The acquisition module is used to acquire the flow detected by the NP chip and to acquire the iFIT header information of the flow.
[0058] The matching module is used to match the iFIT header information with the flow detection mapping table, and obtain the counter address corresponding to the flow based on the matching result;
[0059] The processing module is used to save the number of lost packets and error codes of the traffic to the counter address, and periodically report the information stored in the counter address to the management platform.
[0060] The matching module is also used to report the iFIT header information to the driver if it is determined that there is no flow monitoring mapping table that matches the iFIT header information.
[0061] The receiving driver sends the flow detection mapping table based on the iFIT header information, and matches it with the flow detection mapping table received from the driver. Based on the matching result, the counter address corresponding to the flow is obtained.
[0062] The processing module is also used to save the flow information of the traffic to the counter address.
[0063] The processing module is specifically used to save the information stored in the counter address within the cycle to the driver software node, and report it to the management platform at the end of the cycle.
[0064] This disclosure also provides a network device, which includes a memory, a processor, and a program stored on the network device and executable on the processor. When the program is executed by the processor, it implements the steps in any of the embodiments.
[0065] This disclosure also provides a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of any of the embodiments.
[0066] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0067] Other embodiments of this specification will readily occur to those skilled in the art upon consideration of the specification and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this specification are indicated by the following claims.
[0068] It should be understood that this specification is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the appended claims.
[0069] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.
Claims
1. A method for detecting flow rate, characterized in that, The method includes: The NP chip acquires the flow detected by the flow and obtains the iFIT header information of that flow; The iFIT header information is matched with the flow detection mapping table, and the counter address corresponding to the flow is obtained based on the matching result. The number of lost packets and error codes of the traffic are saved to the counter address, and the information stored in the counter address is periodically reported to the management platform.
2. The method according to claim 1, characterized in that, The matching based on the iFIT header information and the flow detection mapping table includes: If it is determined that there is no flow monitoring mapping table that matches the iFIT header information, the iFIT header information will be reported to the driver. The receiving driver sends the flow detection mapping table based on the iFIT header information, and matches it with the flow detection mapping table received from the driver. Based on the matching result, the counter address corresponding to the flow is obtained.
3. The method according to claim 1, characterized in that, After obtaining the counter address corresponding to the traffic, the method further includes: The flow information of the traffic is saved to the counter address.
4. The method according to claim 1, characterized in that, The process of periodically reporting the information stored in the counter address to the management platform includes: The information stored in the counter address during the cycle is saved to the driver software node and reported to the management platform at the end of the cycle.
5. A network device, characterized in that, The network device includes: The acquisition module is used to acquire the flow detected by the NP chip and to acquire the iFIT header information of the flow. The matching module is used to match the iFIT header information with the flow detection mapping table, and obtain the counter address corresponding to the flow based on the matching result; The processing module is used to save the number of lost packets and error codes of the traffic to the counter address, and periodically report the information stored in the counter address to the management platform.
6. The network device according to claim 5, characterized in that, The matching module is also used to report the iFIT header information to the driver if it is determined that there is no flow monitoring mapping table that matches the iFIT header information. The receiving driver sends the flow detection mapping table based on the iFIT header information, and matches it with the flow detection mapping table received from the driver. Based on the matching result, the counter address corresponding to the flow is obtained.
7. The network device according to claim 5, characterized in that, The processing module is also used to save the flow information of the traffic to the counter address.
8. The network device according to claim 5, characterized in that, The processing module is specifically used to save the information stored in the counter address within the cycle to the driver software node, and report it to the management platform at the end of the cycle.
9. A network device, characterized in that, The network device includes: a memory, a processor, and a program stored on the network device and executable on the processor, wherein the program, when executed by the processor, implements the method steps as described in any one of claims 1 to 4.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program that, when executed by a processor, implements the method steps as described in any one of claims 1 to 4.