CN118316841A

CN118316841A - Method for determining IFIT EGRESS detection points and node equipment

Info

Publication number: CN118316841A
Application number: CN202410473366.4A
Authority: CN
Inventors: 王宇轩; 杨岚; 戴冰琦
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2024-04-18
Filing date: 2024-04-18
Publication date: 2024-07-09

Abstract

The present specification provides a method and node device for determining IFIT EGRESS probe points, the method comprising: receiving iFIT a first message packaged, acquiring a destination address of the first message, judging whether a destination user corresponding to the destination address belongs to a target node, if so, taking the target node as a IFIT EGRESS detection point, and if not, forwarding the first message according to a forwarding table item corresponding to the destination address. By the method, iFIT stream-following detection can be performed on the IPv 6-only message.

Description

Method for determining IFIT EGRESS detection points and node equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and node device for determining IFIT EGRESS detection points.

Background

IFIT (In-situ Flow Information Telemetry, flow-following detection) is to utilize normal forwarded service flow, insert control information into specified service flow, process the control information through forwarding equipment, report collected information to a controller, detect and identify fine anomalies In a network, accurately detect performance information such as time delay, packet loss, jitter and the like of each service, enable network quality SLA to be visible In real time, and achieve rapid fault delimiting and positioning.

The detection along with the flow needs the network equipment and the controller to complete in a matched way, and the whole detection system comprises the following roles:

Ingress node (Ingress): and the method is responsible for screening the target flow, adding a specific detection data structure for the target flow, collecting the statistical data of the target flow and reporting the statistical data to the controller.

Intermediate node (Transmit): judging whether the message is a detection target stream according to whether the message contains a detection data structure, and determining whether the statistics data of the target stream need to be collected and reported to a controller according to the measurement type carried in the detection data structure for the detection target stream.

Egress node (Egress): judging whether the message is a detection target flow according to whether the message contains a detection data structure, and for the detection target flow, collecting the statistic data of the target flow and reporting the statistic data to the controller, and removing the detection data structure in the message.

Controller (Controller): and the system is responsible for collecting statistical data sent by the input node, the intermediate node and the output node and completing the summarization and calculation of the data.

According to the detection requirements of different application scenes, the stream following detection can be divided into two detection types, namely end-to-end measurement and point-to-point measurement.

Disclosure of Invention

The present specification provides a method and node apparatus for determining IFIT EGRESS probe points, by which the Egress probe point of iFIT probe can be determined independently of SRv6 tunnels.

According to a first aspect of embodiments of the present specification, there is provided a method of determining IFIT EGRESS a probe point, the method being applied to a target node, the method comprising:

receiving iFIT a first message packaged;

acquiring a destination address of the first message, and judging whether a destination user corresponding to the destination address belongs to a destination node;

If the target node belongs to the target node, taking the target node as a IFIT EGRESS detection point;

if not, forwarding the first message according to the forwarding table entry corresponding to the destination address.

The step of obtaining the destination address of the first message and judging whether the destination user corresponding to the destination address belongs to a destination node, includes:

Acquiring a destination address, and judging whether the destination address of the first message is learned by an IPv6 neighbor discovery protocol or not through the routing attribute of the forwarding table item;

If yes, determining that a target user corresponding to the target address belongs to a target node;

if not, determining that the destination user corresponding to the destination address does not belong to the destination node.

When the target node belongs to the target node, the target node is regarded as IFIT EGRESS detection points, and the method comprises the following steps:

Taking the target node as IFIT EGRESS detection points and reporting the detection points to a controller;

And stripping the stream following monitoring information in the first message extension header and sending the stream following monitoring information to the target user.

When the destination user corresponding to the destination address does not belong to the destination node, the method further comprises the following steps:

judging whether the target node is last node equipment governed by a controller;

If yes, taking the target node as IFIT EGRESS detection points and reporting the detection points to the controller;

Wherein, after the target node is regarded as IFIT EGRESS detection point and reported to the controller, the method further comprises:

and stripping the stream following monitoring information in the first message extension header and sending the stripped stream following monitoring information to next-hop equipment.

The stripping the flow following monitoring information in the first message extension header comprises the following steps:

and querying the FIB table, and if the identification used for representing the IFIT EGRESS field exists in the FIB table, stripping the flow-following monitoring information in the first message extension header.

According to the above embodiments, it can be seen that, by judging whether the destination user corresponding to the destination address of the first packet belongs to the destination node, or judging whether the destination node is the last node device governed by the controller, the node device can automatically determine IFIT EGRESS the detection point and report the controller according to the judgment result, and the additional configuration of SRv tunnel is not needed to determine IFIT EGRESS detection point, thereby saving the manual configuration cost.

According to a second aspect of embodiments of the present specification, there is provided a node apparatus comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the following method when executing the program:

receiving iFIT a first message packaged;

The embodiment of the disclosure also provides a node device, which comprises:

the receiving module is used for receiving iFIT the encapsulated first message;

the acquisition module is used for acquiring the destination address of the first message and judging whether a destination user corresponding to the destination address belongs to a destination node or not;

And the processing module is used for taking the target node as a IFIT EGRESS detection point when judging that the target user corresponding to the target address belongs to the target node or forwarding the first message according to a forwarding table item corresponding to the target address when judging that the target user corresponding to the target address does not belong to the target node.

The acquisition module is specifically configured to acquire a destination address, and determine whether the destination address of the first packet is learned through an IPv6 neighbor discovery protocol according to a routing attribute of the forwarding table entry;

The sending module is used for taking the target node as a IFIT EGRESS detection point and reporting the detection point to the controller when the target user corresponding to the target address belongs to the target node;

The sending module is further configured to strip the flow-following monitoring information in the first packet extension header, and send the flow-following monitoring information to the destination user.

The acquisition module is further configured to determine whether the target node is a last node device governed by the controller when the target user corresponding to the target address does not belong to the target node;

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and together with the description, serve to explain the principles of the specification.

Fig. 1 is a schematic diagram of a network architecture according to an exemplary embodiment of the present description.

Fig. 2 is a flow chart illustrating a method of determining IFIT EGRESS probe points according to an example embodiment.

Fig. 3 is a schematic diagram of a network architecture according to an exemplary embodiment of the present description.

Fig. 4 is a schematic diagram of a network architecture according to an exemplary embodiment of the present description.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present description as detailed in the accompanying claims.

The terminology used in the description presented herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.

In a network architecture diagram as shown in fig. 1, the type of end-to-end measurement may be selected when a user wishes to measure the packet loss and delay performance of the entire network. The end-to-end measurement can measure whether packet loss and time delay parameters exist between equipment (Ingress equipment) entering a network and equipment (Egress equipment) leaving the network, specifically, the Ingress equipment and the Egress equipment inform the controller of own identities through messages respectively, and the controller identifies the Ingress equipment and the Egress equipment according to the received messages so as to calculate the parameters such as packet loss, time delay and the like.

In another example, the segment-by-segment measurement type may be selected when the user wishes to accurately locate the packet loss and latency performance of each network node. When the end-to-end statistics scene is found to have packet loss or the time delay does not meet the service requirement according to the measurement result, the network between the end and the end can be divided into a plurality of smaller measurement sections, whether the packet loss and the time delay value exist between every two network elements or not is measured, and the network element position affecting the network performance is further positioned.

The flow-following detection is based on a real service message, the head node identifies the service message to be detected according to a predefined rule, a fixed format field is inserted into the message header of the service message to carry detection information, and the forwarding node supporting the flow-following detection subsequently identifies the detection information in the message header and carries out corresponding processing.

In the end-to-end working mode, the DOH extension header of IPv6 is utilized to carry stream-following detection information, and the detection information is packaged by adopting different DOHs under SRv BE and Policy two different service scenes.

In the hop-by-hop working mode, for SRv Policy service scenes, DOH is preferably adopted to carry detection information when the service detection requirements can be met through key node delimitation and positioning, otherwise HBH is adopted to carry detection information.

Currently, in IPv6 networks, detected flows that can BE supported by current iFIT must BE forwarded by SRv BE or SRv TE. The iFIT determination of the probe point of the probe is completely dependent on the end point of the tunnel itself carrying the data flow being probed, i.e. the device where the traffic enters the tunnel is the device where the probe point of the probe is located, and the device where the tunnel ends is the device where the probe point of the probe is located, iFIT.

The Egress detection point iFIT is completely dependent on the tunnel carrying the traffic, that is, the detected traffic must be forwarded by the tunnel, and the tunnel encapsulation is added to make iFIT detection.

For the traffic forwarded by IPv6 only (the whole link depends on the destination IPv6 address routing forwarding of the original message), if iFIT detection is to be performed, a SRv tunnel needs to be established for the traffic first, and then the traffic is detected after being introduced into the tunnel. The networking configuration becomes complicated, and besides iFIT packages, the message body also needs to package a layer of package heads for carrying tunnels, which wastes bandwidth.

To solve the above technical problem, an embodiment of the present disclosure provides a method for determining IFIT EGRESS a probe point, as shown in fig. 2, where the method is applied to a target node, and the method includes:

s201, receiving iFIT encapsulated first messages;

s202, acquiring a destination address of the first message, and judging whether a destination user corresponding to the destination address belongs to a destination node;

And S203, if the first message belongs to the target node, the target node is taken as IFIT EGRESS detection point, or if the first message does not belong to the target node, the first message is forwarded according to a forwarding table item corresponding to the target address.

In this embodiment, the node device may be a router, a switch, or a server device. The target node may be any node device within the jurisdiction of the controller (analyzer).

In this embodiment, the tunnel header of SRv BE is not required to BE encapsulated in the iFIT encapsulation process of the IPv6 forwarding packet, and the IPv6 header of the original packet may BE directly followed by the iFIT probe header, and in this embodiment, only the DOH and HBH probe header already applied in iFIT are mentioned, but the present application is not limited thereto, and the type of the special extension header added iFIT for IPv6 is also one of the schemes protected by the present application.

In step S201, the received first packet is an IPv 6-only packet encapsulated iFIT (i.e., an IPv6 packet without encapsulating tunnel information).

In step S202, after receiving the first message, the header of the first message may be parsed to obtain the destination address of the first message.

In this embodiment, after the target node receives the first message, the target node obtains the destination address, and determines, through its own forwarding table entry, whether the destination user corresponding to the destination address belongs to the target node, specifically, whether the target node and the destination user learn and establish a neighbor relationship through an IPv6 neighbor discovery protocol.

For example, as shown in a network architecture diagram of fig. 3, a user a sends an IPv6 message (first message) to a user B, where the IPv6 message is encapsulated iFIT, an a node device is used as an Ingress probe, after receiving the first message, a node B obtains a destination address of the first message, and when it is determined that a destination user of the destination address does not belong to the node B, the first message is sent to a node C.

And when the C node equipment receives the first message and judges that the destination address of the first message corresponds to the user B which establishes a neighbor relation with the C node equipment, the C node equipment takes the C node equipment as an Egress detection point and informs a controller (analyzer) so that the controller carries out iFIT flow following detection according to the A node equipment (Ingress detection point) and the C node equipment (Egress detection point).

In this embodiment, the edge devices of the IPv 6-only forwarding network that can be managed by the controller and the destination user are connected through an unknown network, as shown in fig. 4, there are node devices a, B and C that are managed by the controller between the user a and the user B, and there is an unknown network connection between the node device C and the user B.

In this embodiment, after receiving the first message, the node device a, the node device B, and the node device C find that the destination user (user B) does not establish a neighbor relation with itself according to the destination address of the first message, and at this time, the node device determines whether itself is a last node device governed by the controller, for example, the node device C determines whether itself is a last node device governed by the controller, if so, sets itself as a IFIT EGRESS detection point, and notifies the controller, so that the controller performs iFIT flow-following detection according to the node device a (Ingress detection point) and the node device C (Ingress detection point).

In this embodiment, there is a function that the last node device governed by the controller does not support iFIT, for example, the node device C does not support iFIT, at this time, the last node device (node device B) may be notified as an egr detection point, and the last node device (node device B) may notify the controller itself of the egr detection point.

In this embodiment, when using the DOH header for end-to-end detection or using the HBH header for hop-by-hop detection, a corresponding rule needs to be configured, where if the rule is configured as an Egress detection point, the DOH header or the HBH header needs to be stripped to prevent a message with a iFIT message header from being carried out of the management domain of the controller.

Specifically, the controller determines the Egress probe point iFIT in the network domain that can be managed by itself, and terminates iFIT, so that the message with the header iFIT cannot be carried out of the management domain. A special configuration for iFIT (such as a physical port configured with an identifier denoted as IFIT EGRESS field) may be made on all physical ports to the unknown domain of the network, to identify that the physical port is the endpoint of iFIT detection, and all messages carrying iFIT encapsulation header need to be forwarded after the port has done the ingress termination. For example, when the node device receives the first message by having an identifier in the FIB table for the field denoted IFIT EGRESS, and querying the FIB table to find that the identifier for the field denoted IFIT EGRESS exists, the flow following monitoring information in the first message extension header is stripped.

According to the embodiments, whether the target user corresponding to the target address of the IPv6 message belongs to the target node or not and whether the target node is end node equipment governed by the controller or not are judged, so that the target node is automatically configured as IFIT EGRESS detection points, and the controller is informed of the detection points, the controller can detect the network quality of the flow forwarded by the IPv6 message according to the efficiency detection points, a special SRv BE tunnel is not required to BE established for iFIT detection, complexity of user deployment is simplified, and bandwidth utilization rate is improved.

Based on the above method embodiments, the embodiments of the present disclosure further provide a node device, where the node device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the following method when executing the program:

receiving iFIT a first message packaged;

Based on the above method embodiments, the embodiments of the present disclosure further provide a node device, where the node device includes:

the receiving module is used for receiving iFIT the encapsulated first message;

Wherein the node device further comprises:

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.

It is to be understood that the present description is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

The foregoing description of the preferred embodiments is provided for the purpose of illustration only, and is not intended to limit the scope of the disclosure, since any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the disclosure are intended to be included within the scope of the disclosure.

Claims

1. A method of determining IFIT EGRESS probe points, the method being applied to a target node, the method comprising:

receiving iFIT a first message packaged;

2. The method according to claim 1, wherein the obtaining the destination address of the first message, and determining whether the destination user corresponding to the destination address belongs to the destination node, includes:

3. The method of claim 1, wherein the determining that the target node is the IFIT EGRESS probe point if the target node belongs to the target node comprises:

4. The method of claim 1, wherein when the destination user corresponding to the destination address does not belong to the destination node, the method further comprises:

5. The method of claim 4, wherein after reporting the target node as IFIT EGRESS probe points to the controller, the method further comprises:

6. The method according to claim 3 or 5, wherein stripping the flow-following monitoring information in the first message extension header comprises:

7. A node device, the node device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the following method when executing the program:

receiving iFIT a first message packaged;

8. A node device, the node device comprising:

the receiving module is used for receiving iFIT the encapsulated first message;

9. The node apparatus of claim 8, wherein,

10. The node device of claim 8, wherein the node device further comprises:

11. The node apparatus of claim 8, wherein,

The acquisition module is further used for judging whether the target node is last node equipment governed by the controller or not when the target user corresponding to the target address does not belong to the target node;