CN112787843A - Method for detecting fault node, storage medium and electronic device - Google Patents

Method for detecting fault node, storage medium and electronic device Download PDF

Info

Publication number
CN112787843A
CN112787843A CN202010549771.1A CN202010549771A CN112787843A CN 112787843 A CN112787843 A CN 112787843A CN 202010549771 A CN202010549771 A CN 202010549771A CN 112787843 A CN112787843 A CN 112787843A
Authority
CN
China
Prior art keywords
forwarding node
node
path
jitter
service flow
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010549771.1A
Other languages
Chinese (zh)
Other versions
CN112787843B (en
Inventor
高陈强
喻敬海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN202010549771.1A priority Critical patent/CN112787843B/en
Publication of CN112787843A publication Critical patent/CN112787843A/en
Application granted granted Critical
Publication of CN112787843B publication Critical patent/CN112787843B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0677Localisation of faults
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852Delays
    • H04L43/087Jitter

Abstract

The embodiment of the invention provides a fault node detection method, a storage medium and an electronic device, wherein the method comprises the following steps: sending a target service flow identification and a target fault detection parameter to a target node set, wherein the target service flow identification is used for identifying the target service flow, and the target service flow identification and the target fault detection parameter are used for carrying out jitter detection on the target service flow; acquiring a jitter detection result sent by the target node set; and determining the second forwarding node as a fault node under the condition that the jitter detection result shows that the target service flow has no jitter abnormality on the first forwarding node and the target service flow has jitter abnormality on the second forwarding node. The invention solves the technical problem that the fault node in the service flow forwarding path can not be positioned in the related technology, and achieves the effect of positioning the fault node.

Description

Method for detecting fault node, storage medium and electronic device
Technical Field
The embodiment of the invention relates to the field of communication, in particular to a fault node detection method, a storage medium and an electronic device.
Background
Currently, in the deployment of deterministic traffic flows, centralized configuration is commonly used. A centralized controller collects information from the network and configures the traffic in the network nodes. In deterministic traffic, the key traffic is generally periodic traffic, which is automatically identified, so that the configuration workload can be reduced, and the deployment of deterministic techniques involved in deterministic traffic can be accelerated. However, in the related art, when a failure node exists in a forwarding path for forwarding a traffic flow and jitter of the traffic flow is abnormal, the failure node cannot be located.
Aiming at the technical problem that the fault node in the service flow forwarding path cannot be positioned in the related technology, an effective technical scheme is not provided yet.
Disclosure of Invention
The embodiment of the invention provides a method for detecting a fault node, a storage medium and an electronic device, which are used for at least solving the technical problem that the fault node in a service flow forwarding path cannot be positioned in the related technology.
According to an embodiment of the present invention, there is provided a method for detecting a failed node, including: sending a target service flow identification and a target fault detection parameter to a target node set, wherein the target node set comprises part or all of forwarding nodes through which a target service flow passes from a sending node to a receiving node, the target service flow identification is used for identifying the target service flow, and the target service flow identification and the target fault detection parameter are used for carrying out jitter detection on the target service flow; acquiring a jitter detection result sent by the target node set, wherein the jitter detection result comprises a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used for indicating whether the target service flow has jitter abnormality on the forwarding node in the target node set; and determining that the second forwarding node is a failed node under the condition that the jitter detection result indicates that the target service flow has no jitter abnormality on a first forwarding node and the target service flow has jitter abnormality on a second forwarding node, wherein the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target service flow passes, and the path through which the target service flow passes is a path formed by the forwarding nodes through which the target service flow passes from the sending node to the receiving node.
In an exemplary embodiment, the sending the target traffic flow identifier and the target failure detection parameter to the target node set includes: and sending the target service flow identification and the target fault detection parameter to all forwarding nodes in the path under the condition that the detection mode of the target service flow is a first detection mode, wherein the first detection mode is to perform jitter detection on the target service flow on all forwarding nodes.
In an exemplary embodiment, after obtaining the jitter detection results sent by the target node set, the method further includes: repeatedly executing the following steps until a first forwarding node without jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the last forwarding node on the path: determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a previous forwarding node of the current forwarding node on the path as the current forwarding node when the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path; determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
In an exemplary embodiment, after obtaining the jitter detection results sent by the target node set, the method further includes: repeatedly executing the following steps until a first forwarding node with jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the first forwarding node on the path: determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a next forwarding node of the current forwarding node on the path as the current forwarding node under the condition that the jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path; determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
In an exemplary embodiment, sending the target traffic flow identification and the target failure detection parameter to all forwarding nodes in the path includes: sending the target service flow identification and the target fault detection parameter to all the forwarding nodes at preset time intervals; or sending the target service flow identifier and the target fault detection parameter to all forwarding nodes under the condition of receiving a trigger command sent by the receiving node, wherein the trigger command is used for indicating the detection of the fault node in the path.
In an exemplary embodiment, the sending a target service flow identifier and a target fault detection parameter to a target node set, and the obtaining a jitter detection result sent by the target node set, includes: and under the condition that the detection mode of the target service flow is a second detection mode, performing jitter detection on the target service flow on the forwarding nodes on the path one by one until a first forwarding node on the path without jitter abnormality is determined, or traversing all the forwarding nodes in the path, wherein the second detection mode is to perform jitter detection on the target service flow on the forwarding nodes on the path one by one.
In an exemplary embodiment, when the detection mode of the target service flow is the second detection mode, performing jitter detection on the target service flow on forwarding nodes on the path one by one until a first forwarding node on the path without jitter abnormality is determined, or traversing all forwarding nodes in the path, includes: repeatedly executing the following steps until a first forwarding node without jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the last forwarding node on the path: sending the target service flow identifier and the target fault detection parameter to the current forwarding node, obtaining a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a previous forwarding node of the current forwarding node on the path as the current forwarding node when the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path; determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
In an exemplary embodiment, the sending a target service flow identifier and a target fault detection parameter to a target node set, and the obtaining a jitter detection result sent by the target node set, includes: and under the condition that the detection mode of the target service flow is a second detection mode, performing jitter detection on the target service flow on the forwarding nodes on the path one by one until a first forwarding node with jitter abnormality on the path is determined, or traversing all the forwarding nodes on the path, wherein the second detection mode is to perform jitter detection on the target service flow on the forwarding nodes on the path one by one.
In an exemplary embodiment, when the detection mode of the target service flow is the second detection mode, performing jitter detection on the target service flow on forwarding nodes on the path one by one until a first forwarding node on the path with jitter abnormality is determined, or traversing all the forwarding nodes on the path, includes: repeatedly executing the following steps until a first forwarding node with jitter abnormality on the path is determined, or all forwarding nodes on the path are traversed, wherein the current forwarding node is initialized to be the first forwarding node on the path: sending the target service flow identifier and the target fault detection parameter to the current forwarding node, obtaining a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a next forwarding node of the current forwarding node on the path as the current forwarding node when the jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path; determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the previous forwarding node exists on the path of the current forwarding node; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
In one exemplary embodiment, the repeatedly performing the steps includes: repeatedly executing the steps at preset time intervals; or, in the case of receiving a trigger command sent by the receiving node, the step is repeatedly executed, where the trigger command is used to instruct detection of a failed node in the path.
In one exemplary embodiment, the method further comprises: determining a third forwarding node as a fault node under the condition that the jitter detection result shows that the target service flow has jitter abnormality on the third forwarding node, wherein the third forwarding node is a first forwarding node on a path through which the target service flow passes; and/or determining that the forwarding node in the path has no fault node when the jitter detection result indicates that the target service flow has no jitter abnormality on the fourth forwarding node, wherein the fourth forwarding node is the last forwarding node on the path through which the target service flow passes.
In an exemplary embodiment, the target traffic flow is a periodic traffic flow.
According to a further embodiment of the present invention, there is also provided a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.
According to the invention, a target service flow identification and a target fault detection parameter are sent to a target node set, wherein the target node set comprises part or all of forwarding nodes through which a target service flow passes from a sending node to a receiving node, the target service flow identification is used for identifying the target service flow, and the target service flow identification and the target fault detection parameter are used for carrying out jitter detection on the target service flow; acquiring a jitter detection result sent by the target node set, wherein the jitter detection result comprises a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used for indicating whether the target service flow has jitter abnormality on the forwarding node in the target node set; and determining that the second forwarding node is a failed node under the condition that the jitter detection result indicates that the target service flow has no jitter abnormality on a first forwarding node and the target service flow has jitter abnormality on a second forwarding node, wherein the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target service flow passes, and the path through which the target service flow passes is a path formed by the forwarding nodes through which the target service flow passes from the sending node to the receiving node. Therefore, the technical problem that the fault node in the service flow forwarding path cannot be positioned in the related technology can be solved, and the effect of positioning the fault node is achieved.
Drawings
Fig. 1 is a block diagram of a hardware structure of an electronic apparatus according to a method for detecting a faulty node according to an embodiment of the present invention;
fig. 2 is a network architecture diagram of a method for detecting a failed node according to an embodiment of the present invention;
fig. 3 is a flowchart of a method for detecting a failed node according to an embodiment of the present invention;
FIG. 4 is a flow chart of a method of detecting a failed node according to another embodiment of the present invention;
FIG. 5 is a flow chart of node-by-node delivery detection in an embodiment of the present invention;
FIG. 6 is a flow chart of a full node down detection in an embodiment of the present invention;
fig. 7 is a schematic diagram of a method for detecting a failed node according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a method for detecting a failed node according to another embodiment of the present invention;
fig. 9 is a schematic diagram of a method for detecting a failed node according to yet another embodiment of the present invention;
fig. 10 is a block diagram showing the configuration of a detection apparatus for a failed node according to an embodiment of the present invention;
fig. 11 is a block diagram showing a configuration of a device for detecting a failed node according to another embodiment of the present invention.
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings in conjunction with the embodiments.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
The method embodiments provided in the embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking an electronic device as an example, fig. 1 is a hardware structure block diagram of an electronic device of a method for detecting a failed node according to an embodiment of the present invention. As shown in fig. 1, the electronic apparatus may include one or more processors 102 (only one is shown in fig. 1) (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 104 for storing data, wherein the electronic apparatus may further include a transmission device 106 for communication function and an input-output device 108. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the electronic device may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The memory 104 may be used to store a computer program, for example, a software program and a module of application software, such as a computer program corresponding to the method for detecting a failed node in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, so as to implement the method described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the electronic device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider. In one example, the transmission device 106 includes a Network adapter (NIC) that can be connected to other Network devices to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
The embodiment of the present application may operate on the network architecture shown in fig. 2, as shown in fig. 2, the network architecture includes: the system comprises a controller, a sending node, a forwarding node and a receiving node, wherein the sending node is used for sending a target service flow to the receiving node, the target service flow is forwarded by the forwarding node to reach the receiving node, and the controller is used for configuring the sending node, the forwarding node and the receiving node.
In this embodiment, a method for detecting a faulty node operating in the network architecture is provided, and fig. 3 is a flowchart of a method for detecting a faulty node according to an embodiment of the present invention, as shown in fig. 3, the flowchart includes the following steps:
step S302, a target service flow identifier and a target fault detection parameter are sent to a target node set, wherein the target node set comprises part or all of forwarding nodes through which a target service flow passes from a sending node to a receiving node, the target service flow identifier is used for identifying the target service flow, and the target service flow identifier and the target fault detection parameter are used for carrying out jitter detection on the target service flow;
step S304, obtaining a jitter detection result sent by the target node set, where the jitter detection result includes a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used to indicate whether a jitter abnormality occurs on the forwarding node in the target node set in the target service flow;
step S306, determining that the second forwarding node is a failed node when the jitter detection result indicates that the target service flow has no jitter abnormality on the first forwarding node and the target service flow has jitter abnormality on the second forwarding node, where the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target service flow passes, and the path through which the target service flow passes is a path formed by the forwarding nodes through which the target service flow passes from the sending node to the receiving node.
Through the steps, a target service flow identification and a target fault detection parameter are sent to a target node set, wherein the target node set comprises part or all of forwarding nodes through which the target service flow passes from a sending node to a receiving node, the target service flow identification is used for identifying the target service flow, and the target service flow identification and the target fault detection parameter are used for carrying out jitter detection on the target service flow; acquiring a jitter detection result sent by the target node set, wherein the jitter detection result comprises a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used for indicating whether the target service flow has jitter abnormality on the forwarding node in the target node set; and determining that the second forwarding node is a failed node under the condition that the jitter detection result indicates that the target service flow has no jitter abnormality on a first forwarding node and the target service flow has jitter abnormality on a second forwarding node, wherein the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target service flow passes, and the path through which the target service flow passes is a path formed by the forwarding nodes through which the target service flow passes from the sending node to the receiving node. The technical problem that the fault node in the service flow forwarding path can not be positioned in the related technology is solved, and the effect of positioning the fault node is achieved.
The main body for executing the above steps may be the controller in fig. 2, but is not limited thereto.
In an exemplary embodiment, the sending the target traffic flow identifier and the target failure detection parameter to the target node set includes: and sending the target service flow identification and the target fault detection parameter to all forwarding nodes in the path under the condition that the detection mode of the target service flow is a first detection mode, wherein the first detection mode is to perform jitter detection on the target service flow on all forwarding nodes.
It should be noted that, in an exemplary embodiment, the target traffic flow identifier may include: at least one of a source physical address (also called a source MAC address, i.e. the MAC address of the sending node), a destination MAC address (i.e. the MAC address of the receiving node), a Virtual Local Area Network (VLAN) identifier, and a priority of the target traffic flow. In an exemplary embodiment, the target traffic flow identification may further include at least one of a source network address (also referred to as a source IP address, i.e., the IP address of the sending node), a destination IP address (i.e., the IP address of the receiving node), a port number, and an application layer protocol. In the above embodiment, the target service flow identifier is used to perform flow matching on the target service flow, that is, the forwarding node may match the received packet according to the received target service flow identifier, so as to identify the packet of the target service flow. The target fault detection parameters include a period of the target service flow, a jitter threshold and a determination rule, wherein the determination rule includes that the number of continuously detected messages of the target service flow is greater than or equal to a message number threshold, and the proportion of messages with abnormal jitter in the number of continuously detected messages of the target service flow is less than or equal to an abnormal threshold, wherein the period of the target service flow and the jitter threshold are used for determining whether the jitter of the messages of the target service flow is abnormal.
In an exemplary embodiment, after obtaining the jitter detection results sent by the target node set, the method further includes:
repeatedly executing the following steps until a first forwarding node without jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the last forwarding node on the path:
determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a forwarding node before a current forwarding node on a path as the current forwarding node when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the current forwarding node has the forwarding node before the current forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
In the above embodiment, after the jitter detection results sent by all forwarding nodes are obtained, traversal may be performed from the jitter detection result sent by the last forwarding node on the path, so as to locate a faulty node causing jitter abnormality in the target traffic flow. When the forwarding node a on the path has no jitter abnormality and the next forwarding node B of the forwarding node a on the path has jitter abnormality, it is determined that the forwarding node B is a faulty node causing jitter abnormality of the target service flow. And determining that no fault node exists in the path under the condition that the jitter abnormality does not occur in the last forwarding node on the path.
In an exemplary embodiment, after obtaining the jitter detection results sent by the target node set, the method further includes:
repeatedly executing the following steps until a first forwarding node with jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the first forwarding node on the path:
determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a next forwarding node of the current forwarding node on the path as the current forwarding node under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
In the above embodiment, after the jitter detection results sent by all forwarding nodes are obtained, traversal may be performed from the jitter detection result sent by the first forwarding node on the path, so as to locate a faulty node causing jitter abnormality in the target traffic flow. When the forwarding node B on the path has a jitter abnormality and the previous forwarding node a of the forwarding node B on the path has no jitter abnormality, the forwarding node B is determined to be a faulty node causing the jitter abnormality of the target service flow. And determining that the first forwarding node on the path is a failed node when the jitter abnormality occurs in the first forwarding node on the path.
In an exemplary embodiment, sending the target traffic flow identification and the target failure detection parameter to all forwarding nodes in the path includes:
sending the target service flow identification and the target fault detection parameter to all the forwarding nodes at preset time intervals; or
And under the condition of receiving a trigger command sent by the receiving node, sending the target service flow identifier and the target fault detection parameter to all forwarding nodes, wherein the trigger command is used for indicating the detection of the fault node in the path.
That is, in the above embodiment, when the detection method of the target traffic flow is the first detection method, the target traffic flow identifier and the target failure detection parameter may be sent to all forwarding nodes at preset time intervals, so as to trigger all forwarding nodes to perform jitter detection, or, when a trigger command sent by a receiving node is received, all forwarding nodes may be triggered to perform jitter detection.
In an exemplary embodiment, the sending a target service flow identifier and a target fault detection parameter to a target node set, and the obtaining a jitter detection result sent by the target node set, includes: and under the condition that the detection mode of the target service flow is a second detection mode, performing jitter detection on the target service flow on the forwarding nodes on the path one by one until a first forwarding node on the path without jitter abnormality is determined, or traversing all the forwarding nodes in the path, wherein the second detection mode is to perform jitter detection on the target service flow on the forwarding nodes on the path one by one.
In an exemplary embodiment, when the detection mode of the target service flow is the second detection mode, performing jitter detection on the target service flow on forwarding nodes on the path one by one until a first forwarding node on the path without jitter abnormality is determined, or traversing all forwarding nodes in the path, includes:
repeatedly executing the following steps until a first forwarding node without jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the last forwarding node on the path:
transmitting the target traffic flow identification and the target failure detection parameter to the current forwarding node,
acquiring a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a forwarding node before a current forwarding node on a path as the current forwarding node when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the current forwarding node has the forwarding node before the current forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
It should be noted that, in the above embodiment, when the detection method is the second detection method, jitter detection may be performed sequentially from the last forwarding node of the path, so as to determine a failed node.
In an exemplary embodiment, the sending a target service flow identifier and a target fault detection parameter to a target node set, and the obtaining a jitter detection result sent by the target node set, includes: and under the condition that the detection mode of the target service flow is a second detection mode, performing jitter detection on the target service flow on the forwarding nodes on the path one by one until a first forwarding node with jitter abnormality on the path is determined, or traversing all the forwarding nodes on the path, wherein the second detection mode is to perform jitter detection on the target service flow on the forwarding nodes on the path one by one.
In an exemplary embodiment, when the detection mode of the target service flow is the second detection mode, performing jitter detection on the target service flow on forwarding nodes on the path one by one until a first forwarding node on the path with jitter abnormality is determined, or traversing all the forwarding nodes on the path, includes:
repeatedly executing the following steps until a first forwarding node with jitter abnormality on the path is determined, or all forwarding nodes on the path are traversed, wherein the current forwarding node is initialized to be the first forwarding node on the path:
transmitting the target traffic flow identification and the target failure detection parameter to the current forwarding node,
acquiring a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a next forwarding node of the current forwarding node on the path as the current forwarding node under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the previous forwarding node exists on the path of the current forwarding node;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
In the foregoing embodiment, when the detection manner is the second detection manner, the jitter detection may be performed sequentially from the first forwarding node of the path, so as to determine the failed node.
In one exemplary embodiment, the repeatedly performing the steps includes:
repeatedly executing the steps at preset time intervals; alternatively, the first and second electrodes may be,
and under the condition of receiving a trigger command sent by the receiving node, repeatedly executing the step, wherein the trigger command is used for indicating the detection of the failed node in the path.
That is, in the above embodiment, when the detection mode of the target service flow is the second detection mode, the jitter detection may be performed sequentially from the last forwarding node on the path at preset time intervals, or sequentially from the first forwarding node on the path; alternatively, when receiving a trigger command sent by the receiving node, the method may trigger jitter detection to be performed sequentially from the last forwarding node on the path, or may trigger jitter detection to be performed sequentially from the first forwarding node on the path.
In one exemplary embodiment, the method further comprises:
determining a third forwarding node as a fault node under the condition that the jitter detection result shows that the target service flow has jitter abnormality on the third forwarding node, wherein the third forwarding node is a first forwarding node on a path through which the target service flow passes; and/or
And under the condition that the jitter detection result shows that the target service flow has no jitter abnormality on a fourth forwarding node, determining that the forwarding node in the path has no fault node, wherein the fourth forwarding node is the last forwarding node on the path passed by the target service flow.
In an exemplary embodiment, the target traffic flow is a periodic traffic flow, such as a traffic flow configured by a controller that is periodically transmitted by a transmitting node to a receiving node.
The following explains the method for detecting a failed node in the above embodiment with reference to an example, but is not intended to limit the technical solution of the embodiment of the present invention. In this embodiment, after the service flow is normally deployed, when it is detected that the service flow jitter is abnormal, the jitter abnormality may be detected by a periodic service flow detection method, and a fault point causing the jitter abnormality is located, so that the fault point may be quickly located and the fault may be repaired, thereby ensuring quick recovery of the service flow.
Fig. 4 is a flowchart of a method for detecting a failed node according to another embodiment of the present invention, as shown in fig. 4, the method includes the following steps:
step 1: starting;
step 2: triggering fault detection;
namely, the controller determines to start the detection of the fault node;
and step 3: the controller calculates the network node (i.e., the target node set in the above embodiment) and the detection parameter (i.e., the target failure detection parameter in the above embodiment) based on the flow identifier and the receiving node;
in an exemplary embodiment, the controller stores configuration information of a service flow, for example, a service flow identifier, a sending node, a receiving node, a path and a target fault detection parameter corresponding to the service flow, so that the corresponding path and the target fault detection parameter can be obtained according to the service flow identifier and the receiving node.
In an exemplary embodiment, the acquiring, by the controller, a path node and a probing order (i.e., the first detection manner or the second detection manner in the foregoing embodiment) of a traffic flow from a source end (i.e., the sending node in the foregoing embodiment) to a destination end (i.e., the receiving node in the foregoing embodiment) corresponding to the flow identifier, and detecting a parameter related to a jitter anomaly (i.e., the target failure detection parameter in the foregoing embodiment) according to the traffic flow identifier and the receiving node includes: a period time Tp and a Jitter threshold Jitter, and a decision rule. The decision rule is, for example: and the number (MaxPkt) of the continuously detected messages of the target service flow is more than the specified number, and meanwhile, the proportion (RoAJ) of the messages with abnormal jitter is less than the specified percentage, so that the network node is judged to detect the abnormal jitter of the target service flow. For example, a network node continuously detects m packets of a target service flow, where m > MaxPkt, where the number of abnormal packets is n, and when n/m > RoAJ, the network node is considered to detect a jitter abnormality of the target service flow.
And 4, step 4: the controller issues the flow identifier (also called flow identifier parameter) and the detection parameter to the network node (i.e. the target node set in the above embodiment), i.e. performs the fault detection triggering;
in an exemplary embodiment, the control may issue the flow identifier and the detection parameter to the network node through which the service flow passes according to a certain rule, that is, the failure detection trigger may be divided into the following two methods:
the controller actively detects: the method comprises the steps that a controller sends periodic service flow detection commands to a network node periodically (namely each preset time interval), and the network node returns detection results to the controller, wherein the detection commands comprise target service flow identifications and target fault detection parameters;
passive detection of the controller: when a receiving node of the traffic flow (for example, a receiving node of the deterministic traffic flow) detects that the time jitter of the arrival of the traffic is too large to exceed a tolerable jitter range, the receiving node sends a trigger command to the controller. The controller sends a periodic service flow detection command to the network node according to the trigger command of the receiving node, and the network node returns a detection result to the controller.
The flow identifier may include identification information of one or more receiving nodes, such as a MAC address of a receiving end; when the service flow has a plurality of receiving nodes, the flow identifier may include multicast MAC addresses of the plurality of receiving nodes;
and 5: the network node performs service flow matching, calculates the period and jitter, judges whether the jitter is abnormal or not, and returns the result to the controller;
and the network node matches the service flow according to the flow identification, detects whether the jitter is abnormal according to the detection parameters, and returns the jitter to the controller.
Step 6: the controller calculates a fault node according to the result returned by each network node;
and the controller determines the fault node in the path according to the return result of each network node. In an exemplary embodiment, in a direction from a destination end (i.e., a receiving node) to a source end (i.e., a sending node) of a path, a first network node with jitter abnormality detects that the jitter is normal at a forwarding node before the network node on the path, and determines the network node as a failed node.
And 7: and (6) ending.
In an exemplary embodiment, in step 4, the issuing of the flow identification and detection parameters includes the following steps: and sending the service flow node by node, namely, the controller sequentially sends and detects all the forwarding nodes passing through the forwarding path of the service flow acquired by the receiving node to the forwarding nodes in the direction from the receiving node to the sending node according to the flow identifier and the forwarding nodes. When a forwarding node detects jitter abnormality and a forwarding node before the forwarding node on the path detects jitter normality, the forwarding node is determined as a fault node, so that the fault node is positioned.
Fig. 5 is a flowchart of node-by-node down-sending detection according to an embodiment of the present invention, and as shown in fig. 5, the method includes the following steps:
step 1: the controller takes the previous forwarding node of the receiving node as the current forwarding node;
step 2: sending a detection command to the current forwarding node;
and step 3: determining whether the current forwarding node detects jitter abnormality, if so, executing step 4, otherwise, executing step 7;
and 4, step 4: determining whether the previous forwarding node of the current forwarding node on the path is a sending node, if so, executing step 5; otherwise, executing step 6;
and 5: determining the current forwarding node as a fault node;
step 6: determining the forwarding node which is previous to the forwarding node on the path as the current forwarding node, and executing the step 2;
and 7: and determining that no fault node exists on the path.
The path is formed by forwarding nodes through which the traffic flow passes from the sending node to the receiving node.
In an exemplary embodiment, in step 4, the issuing of the flow identification and detection parameters includes the following steps: and (5) issuing the path full nodes. The controller obtains all forwarding nodes through which the forwarding paths of the service flows pass according to the flow identifiers and the receiving nodes, the controller issues the flow identifiers and the detection parameters to all the forwarding nodes, and all the forwarding nodes return the detection results to the controller. And determining a fault node according to the detection result acquired by the controller. Fig. 6 is a flowchart of a full-node down-sending detection according to an embodiment of the present invention, and as shown in fig. 6, the method includes the following steps:
step 1: the controller issues flow identification and detection parameters to all forwarding nodes on all paths;
step 2: each forwarding node detects whether the jitter is abnormal or not and respectively returns the detection result to the controller.
In the above embodiment, after receiving the stream identifier and the detection parameter, the forwarding node performs target service stream matching and periodic parameter extraction on a subsequently received message, and determines whether jitter abnormality of the target service stream is detected.
In the embodiment of the invention, each forwarding node detects the message of the actual service flow, and judges whether the jitter of the service flow is abnormal or not by detecting the actual service message, so as to position the fault node, wherein the message processing flow of the original service flow is not changed, and the extra specific message and the existing protocol are not required to be added, so that the detection efficiency of the fault node is improved.
Fig. 7 is a schematic diagram of a method for detecting a failed node according to an embodiment of the present invention, in which a controller actively detects and issues detection parameters to all forwarding nodes of a path. The controller has configured a deterministic periodic traffic stream 1(stream1), with the sending node being node1, the receiving node being node2, the period (Tp) being 125us, the Jitter threshold (Jitter) being 5us, MaxPkt being 100, and RoAJ being 1%. The forwarding nodes on the path traversed by traffic stream1 from node1 (i.e. source, also called sending node) to node2 (i.e. receiving node, also called destination) are forwarding node 1(switch1), forwarding node2 and forwarding node3, respectively. As shown in fig. 7, the controller sets a detection cycle, and when the detection time is up, in step (1) in the figure, it actively issues at least one of a traffic flow identification parameter (e.g., Source MAC (SMAC), Destination MAC (DMAC)), VLAN (e.g., VLAN id), and priority (e.g., priority of a target traffic flow) to all nodes (including switch1, switch2, and switch3) on a path that the stream1 passes through from the source end (node1) to the destination end (node2), where, in an exemplary embodiment, the traffic flow identification parameter includes SMAC, DMAC, VLAN, and priority, and a detection parameter (Tp 125us, Jitter 5us, MaxPkt 100, RoAJ 1%), where SMAC is the MAC address of node1 and DMAC is the MAC address of node 2. The switch1, the switch2 and the switch3 respectively perform matching and jitter detection on the periodic traffic flow according to the flow identification parameter and the detection parameter, the switch1 and the switch2 detect that the jitter of the periodic traffic flow is normal, the switch3 detects that the jitter is abnormal, and respectively return the detection results to the controller (i.e. the step (2) in the figure). The controller determines that the forwarding node with the jitter abnormality at the first in the path is switch3, and the forwarding node before the switch3 in the path (i.e., switch2) detects that the jitter is normal, then switch3 is the failed network node.
Fig. 8 is a schematic diagram of a method for detecting a failed node according to another embodiment of the present invention, in this embodiment, a controller passively triggers detection and issues detection parameters node by node to a path, the controller has configured a deterministic periodic traffic stream 1(stream1), a sending node is node1, a receiving node is node2, a period (Tp) is 125us, a Jitter threshold (Jitter) is 5us, MaxPkt is 100, and RoAJ is 1%. The forwarding nodes on the path traversed by traffic stream1 from node1 (i.e. source, also called sending node) to node2 (i.e. receiving node, also called destination) are switch1, switch2 and switch3, respectively. As shown in fig. 8, when the receiving node2 detects that the jitter of the received traffic stream1 is too large and exceeds 5us, it sends a trigger command to the controller, where the trigger command includes stream ID 1 and the receiving node is a parameter such as node2 (as shown in step (1) in the figure). The controller issues traffic stream identification parameters (for example, including SMAC, DMAC, VLAN, priority) and detection parameters (Tp ═ 125us, Jitter ═ 5us, MaxPkt ═ 200, and RoAJ ═ 1%) node by node to the switches 3, 2, and 1 on the path through which the stream1 passes. The controller firstly issues the jitter detection to the switch3, which is the previous forwarding node of the node2 (as shown in step (2) in the figure), the switch3 performs the jitter detection of the periodic service flow according to the service flow identification parameter and the detection parameter, and among 200 detected matching messages, 5 messages have jitter that is too large and exceeds a predetermined percentage, and returns the detection result to the controller (as shown in step (3) in the figure). Then, the controller continues to issue to the previous forwarding node, i.e., switch2 (as shown in step (4) in the figure), the switch2 performs periodic service flow matching according to the service flow identification parameter and the detection parameter, and if no packet jitter is too large in 200 matching packets detected as a result, it is determined that the service flow jitter is normal, and the detection result is returned to the controller (as shown in step (5) in the figure). The controller determines that switch3 is jittered abnormally and switch2 is jittered normally, then determines that switch3 is the failed node.
Fig. 9 is a schematic diagram of a method for detecting a failed node according to another embodiment of the present invention, in this embodiment, a controller passively triggers detection and issues detection parameters node by node to a path, the controller has configured a deterministic periodic traffic stream 1(stream1), a sending node is node1, receiving nodes are node2 and node3, a period (Tp) is 125us, a Jitter threshold (Jitter) is 5us, MaxPkt is 100, and RoAJ is 1%. Forwarding nodes on a path which a traffic stream1 passes from node1 (source end) to node3 (destination end) are switch1, switch2 and switch3 respectively; the forwarding nodes on the path traversed from node1 (the source end) to node2 (the destination end) are switch1 and switch2, respectively. When detecting that the jitter of the received traffic stream1 is too large and exceeds 5us, the receiving node2 sends a trigger command to the controller, wherein the trigger command includes parameters such as stream ID 1 and receiving node 2; when the receiving node3 detects that the jitter of the received traffic stream1 is too large and exceeds 5us, it sends a trigger command to the controller, where the trigger command includes parameters such as stream ID 1 and receiving node3 (as shown in step (1) in the figure). The controller calculates that the forwarding nodes passed by the traffic flow whose receiving node is node2 are switch1 and switch2, and the forwarding nodes passed by the traffic flow whose receiving node is node3 are switch1, switch2 and switch3, and then the controller issues traffic flow identification parameters (for example, including SMAC, DMAC, VLAN, priority) and detection parameters (Tp ═ 125us, Jitter ═ 5us, MaxPkt ═ 100, and RoAJ ═ 1%) to all the forwarding nodes switch1, switch2 and switch3, where DMAC is the multicast MAC addresses of node2 and node3 (as shown in step (2) in the figure). The forwarding nodes switch1, switch2 and switch3 respectively perform jitter detection on the periodic traffic flow according to the traffic flow identification parameter and the detection parameter, where the switch1 detects that the periodic traffic flow is jittered normally, and the switch2 and the switch3 detect that the periodic traffic flow is jittered abnormally, and respectively return detection results to the controller (as shown in step (3) in the figure). The controller respectively determines fault nodes for two forwarding paths of a target service flow, wherein on the forwarding path from node1 to node2, a switch2 is a node with jitter abnormality at the first occurrence, and a previous forwarding node of a switch2 on the forwarding path has normal jitter, and then the switch2 is determined to be a fault node on the forwarding path; on a forwarding path from node1 to node3, switch2 is the first node with jitter abnormality and the previous forwarding node of switch2 on the forwarding path with normal jitter, and then it is determined that switch2 is the failed node on the forwarding path.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
In this embodiment, a device for detecting a failed node is further provided, where the device is used to implement the foregoing embodiments and preferred embodiments, and details are not repeated for what has been described. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 10 is a block diagram of a detection apparatus for a failed node according to an embodiment of the present invention, and as shown in fig. 10, the apparatus includes:
a sending module 101, configured to send a target service flow identifier and a target fault detection parameter to a target node set, where the target node set includes some or all nodes in forwarding nodes through which a target service flow passes from a sending node to a receiving node, the target service flow identifier is used to identify the target service flow, and the target service flow identifier and the target fault detection parameter are used to perform jitter detection on the target service flow;
an obtaining module 103, configured to obtain a jitter detection result sent by the target node set, where the jitter detection result includes a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used to indicate whether a jitter abnormality occurs on the forwarding node in the target node set in the target service flow;
a determining module 105, configured to determine that a second forwarding node is a failed node when the jitter detection result indicates that the target traffic flow has no jitter abnormality on a first forwarding node and the target traffic flow has jitter abnormality on the second forwarding node, where the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target traffic flow passes, and the path through which the target traffic flow passes is a path formed by the forwarding nodes through which the target traffic flow passes from the sending node to the receiving node.
According to the invention, a target service flow identification and a target fault detection parameter are sent to a target node set, wherein the target node set comprises part or all of forwarding nodes through which a target service flow passes from a sending node to a receiving node, the target service flow identification is used for identifying the target service flow, and the target service flow identification and the target fault detection parameter are used for carrying out jitter detection on the target service flow; acquiring a jitter detection result sent by the target node set, wherein the jitter detection result comprises a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used for indicating whether the target service flow has jitter abnormality on the forwarding node in the target node set; and determining that the second forwarding node is a failed node under the condition that the jitter detection result indicates that the target service flow has no jitter abnormality on a first forwarding node and the target service flow has jitter abnormality on a second forwarding node, wherein the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target service flow passes, and the path through which the target service flow passes is a path formed by the forwarding nodes through which the target service flow passes from the sending node to the receiving node. Therefore, the technical problem that the fault node in the service flow forwarding path cannot be positioned in the related technology can be solved, and the effect of positioning the fault node is achieved.
In an exemplary embodiment, the sending module 101 is further configured to: and sending the target service flow identification and the target fault detection parameter to all forwarding nodes in the path under the condition that the detection mode of the target service flow is a first detection mode, wherein the first detection mode is to perform jitter detection on the target service flow on all forwarding nodes.
Fig. 11 is a block diagram of a structure of a device for detecting a failed node according to another embodiment of the present invention, as shown in fig. 11, the device includes, in addition to all modules shown in fig. 10, a processing module 111, configured to repeatedly execute the following steps until a forwarding node without a jitter abnormality on the first forwarding node on the path is determined, or all forwarding nodes in the path are traversed, where a current forwarding node is initialized to be a last forwarding node on the path: determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a previous forwarding node of the current forwarding node on the path as the current forwarding node when the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path; determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
In an exemplary embodiment, the processing module 111 is further configured to repeatedly execute the following steps until a forwarding node with a jitter abnormality on the first forwarding node on the path is determined, or all forwarding nodes in the path are traversed, where a current forwarding node is initialized to be a first forwarding node on the path: determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a next forwarding node of the current forwarding node on the path as the current forwarding node under the condition that the jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path; determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
In an exemplary embodiment, the sending module 101 is further configured to: sending the target service flow identification and the target fault detection parameter to all the forwarding nodes at preset time intervals; or sending the target service flow identifier and the target fault detection parameter to all forwarding nodes under the condition of receiving a trigger command sent by the receiving node, wherein the trigger command is used for indicating the detection of the fault node in the path.
In an exemplary embodiment, the processing module 111 is further configured to, when the detection mode of the target service flow is a second detection mode, repeatedly perform the following steps until a first forwarding node on the path without jitter abnormality is determined, or all forwarding nodes in the path are traversed, where a current forwarding node is initialized to a last forwarding node on the path, and the second detection mode is that jitter detection is performed on the target service flow on the forwarding nodes on the path one by one: sending the target service flow identifier and the target fault detection parameter to the current forwarding node, obtaining a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a previous forwarding node of the current forwarding node on the path as the current forwarding node when the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path; determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
In an exemplary embodiment, the processing module 111 is further configured to, when the detection mode of the target service flow is a second detection mode, repeatedly perform the following steps until a first forwarding node on the path with a jitter abnormality is determined, or all forwarding nodes on the path are traversed, where a current forwarding node is initialized to be the first forwarding node on the path, and the second detection mode is that jitter detection is performed on the target service flow on the forwarding nodes on the path one by one: sending the target service flow identifier and the target fault detection parameter to the current forwarding node, obtaining a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node, and determining a next forwarding node of the current forwarding node on the path as the current forwarding node when the jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path; determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the previous forwarding node exists on the path of the current forwarding node; and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
In an exemplary embodiment, the processing module 111 is further configured to: repeatedly executing the steps at preset time intervals; or, in the case of receiving a trigger command sent by the receiving node, the step is repeatedly executed, where the trigger command is used to instruct detection of a failed node in the path.
In an exemplary embodiment, the processing module 111 is further configured to: determining a third forwarding node as a fault node under the condition that the jitter detection result shows that the target service flow has jitter abnormality on the third forwarding node, wherein the third forwarding node is a first forwarding node on a path through which the target service flow passes; and/or determining that the forwarding node in the path has no fault node when the jitter detection result indicates that the target service flow has no jitter abnormality on the fourth forwarding node, wherein the fourth forwarding node is the last forwarding node on the path through which the target service flow passes.
In an exemplary embodiment, the target traffic flow is a periodic traffic flow.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
Embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above-mentioned method embodiments when executed.
In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.
In an exemplary embodiment, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary embodiments, and details of this embodiment are not repeated herein.
It will be apparent to those skilled in the art that the various modules or steps of the invention described above may be implemented using a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and they may be implemented using program code executable by the computing devices, such that they may be stored in a memory device and executed by the computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into various integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.

Claims (14)

1. A method for detecting a failed node, comprising:
sending a target service flow identification and a target fault detection parameter to a target node set, wherein the target node set comprises part or all of forwarding nodes through which a target service flow passes from a sending node to a receiving node, the target service flow identification is used for identifying the target service flow, and the target service flow identification and the target fault detection parameter are used for carrying out jitter detection on the target service flow;
acquiring a jitter detection result sent by the target node set, wherein the jitter detection result comprises a detection result obtained by a forwarding node in the target node set performing jitter detection on the target service flow according to the target service flow identifier and the target fault detection parameter, and the jitter detection result is used for indicating whether the target service flow has jitter abnormality on the forwarding node in the target node set;
and determining that the second forwarding node is a failed node under the condition that the jitter detection result indicates that the target service flow has no jitter abnormality on a first forwarding node and the target service flow has jitter abnormality on a second forwarding node, wherein the first forwarding node is a forwarding node previous to the second forwarding node on a path through which the target service flow passes, and the path through which the target service flow passes is a path formed by the forwarding nodes through which the target service flow passes from the sending node to the receiving node.
2. The method of claim 1, wherein sending the target traffic flow identification and the target failure detection parameter to the set of target nodes comprises:
and sending the target service flow identification and the target fault detection parameter to all forwarding nodes in the path under the condition that the detection mode of the target service flow is a first detection mode, wherein the first detection mode is to perform jitter detection on the target service flow on all forwarding nodes.
3. The method of claim 2, wherein after obtaining the jitter detection results sent by the set of target nodes, the method further comprises:
repeatedly executing the following steps until a first forwarding node without jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the last forwarding node on the path:
determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a forwarding node before a current forwarding node on a path as the current forwarding node when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the current forwarding node has the forwarding node before the current forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
4. The method of claim 2, wherein after obtaining the jitter detection results sent by the set of target nodes, the method further comprises:
repeatedly executing the following steps until a first forwarding node with jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the first forwarding node on the path:
determining whether a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a next forwarding node of the current forwarding node on the path as the current forwarding node under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node has the previous forwarding node on the path;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
5. The method of claim 2, wherein sending the target traffic flow identification and the target failure detection parameter to all forwarding nodes in the path comprises:
sending the target service flow identification and the target fault detection parameter to all the forwarding nodes at preset time intervals; or
And under the condition of receiving a trigger command sent by the receiving node, sending the target service flow identifier and the target fault detection parameter to all forwarding nodes, wherein the trigger command is used for indicating the detection of the fault node in the path.
6. The method of claim 1, wherein the sending the target service flow identifier and the target failure detection parameter to the target node set and the obtaining the jitter detection result sent by the target node set comprise:
and under the condition that the detection mode of the target service flow is a second detection mode, performing jitter detection on the target service flow on the forwarding nodes on the path one by one until a first forwarding node on the path without jitter abnormality is determined, or traversing all the forwarding nodes in the path, wherein the second detection mode is to perform jitter detection on the target service flow on the forwarding nodes on the path one by one.
7. The method according to claim 6, wherein, when the detection mode of the target traffic flow is the second detection mode, performing jitter detection on the target traffic flow on forwarding nodes on the path one by one until a first forwarding node on the path without jitter abnormality is determined, or traversing all forwarding nodes in the path, includes:
repeatedly executing the following steps until a first forwarding node without jitter abnormality on the path is determined, or all forwarding nodes in the path are traversed, wherein the current forwarding node is initialized to be the last forwarding node on the path:
transmitting the target traffic flow identification and the target failure detection parameter to the current forwarding node,
acquiring a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a forwarding node before a current forwarding node on a path as the current forwarding node when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the current forwarding node has the forwarding node before the current forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path without jitter abnormality when a jitter detection result sent by the current forwarding node indicates that the target service flow does not have jitter abnormality on the current forwarding node and the current forwarding node has a next forwarding node on the path, wherein the first forwarding node is the current forwarding node and the second forwarding node is the next forwarding node on the path of the current forwarding node;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has no next forwarding node on the path, determining the current forwarding node as the first forwarding node without jitter abnormality on the path.
8. The method of claim 1, wherein the sending the target service flow identifier and the target failure detection parameter to the target node set and the obtaining the jitter detection result sent by the target node set comprise:
and under the condition that the detection mode of the target service flow is a second detection mode, performing jitter detection on the target service flow on the forwarding nodes on the path one by one until a first forwarding node with jitter abnormality on the path is determined, or traversing all the forwarding nodes on the path, wherein the second detection mode is to perform jitter detection on the target service flow on the forwarding nodes on the path one by one.
9. The method according to claim 8, wherein, when the detection mode of the target traffic flow is the second detection mode, performing jitter detection on the target traffic flow on forwarding nodes on the path one by one until a first forwarding node on the path with jitter abnormality is determined, or traversing all forwarding nodes on the path, includes:
repeatedly executing the following steps until a first forwarding node with jitter abnormality on the path is determined, or all forwarding nodes on the path are traversed, wherein the current forwarding node is initialized to be the first forwarding node on the path:
transmitting the target traffic flow identification and the target failure detection parameter to the current forwarding node,
acquiring a jitter detection result sent by the current forwarding node, and determining whether the jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node,
determining a next forwarding node of the current forwarding node on the path as the current forwarding node under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has no jitter abnormality on the current forwarding node and the current forwarding node has the next forwarding node on the path;
determining the current forwarding node as a first forwarding node on the path, where the first forwarding node is the previous forwarding node on the path of the current forwarding node, and the second forwarding node is the current forwarding node, when a jitter detection result sent by the current forwarding node indicates that jitter abnormality occurs in the target service flow on the current forwarding node and the previous forwarding node exists on the path of the current forwarding node;
and under the condition that a jitter detection result sent by the current forwarding node indicates that the target service flow has jitter abnormality on the current forwarding node and the current forwarding node does not have a previous forwarding node on the path, determining the current forwarding node as the first forwarding node with jitter abnormality on the path and determining the current forwarding node as a fault node.
10. The method of claim 7 or 9, wherein said repeatedly performing said steps comprises:
repeatedly executing the steps at preset time intervals; alternatively, the first and second electrodes may be,
and under the condition of receiving a trigger command sent by the receiving node, repeatedly executing the step, wherein the trigger command is used for indicating the detection of the failed node in the path.
11. The method of claim 1, further comprising:
determining a third forwarding node as a fault node under the condition that the jitter detection result shows that the target service flow has jitter abnormality on the third forwarding node, wherein the third forwarding node is a first forwarding node on a path through which the target service flow passes; and/or
And under the condition that the jitter detection result shows that the target service flow has no jitter abnormality on a fourth forwarding node, determining that the forwarding node in the path has no fault node, wherein the fourth forwarding node is the last forwarding node on the path passed by the target service flow.
12. The method of claim 1, wherein the target traffic flow is a periodic traffic flow.
13. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 12 when executed.
14. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 12.
CN202010549771.1A 2020-06-16 2020-06-16 Method for detecting fault node, storage medium and electronic device Active CN112787843B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010549771.1A CN112787843B (en) 2020-06-16 2020-06-16 Method for detecting fault node, storage medium and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010549771.1A CN112787843B (en) 2020-06-16 2020-06-16 Method for detecting fault node, storage medium and electronic device

Publications (2)

Publication Number Publication Date
CN112787843A true CN112787843A (en) 2021-05-11
CN112787843B CN112787843B (en) 2022-04-29

Family

ID=75750106

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010549771.1A Active CN112787843B (en) 2020-06-16 2020-06-16 Method for detecting fault node, storage medium and electronic device

Country Status (1)

Country Link
CN (1) CN112787843B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114448785A (en) * 2022-03-18 2022-05-06 新浪网技术(中国)有限公司 Method and device for positioning fault network equipment and electronic equipment
CN116708135A (en) * 2023-08-08 2023-09-05 中国电信股份有限公司 Network service fault monitoring method and device, electronic equipment and storage medium

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101036330A (en) * 2004-12-01 2007-09-12 思科技术公司 System and methods for detecting network failure
CN102035694A (en) * 2010-12-20 2011-04-27 中兴通讯股份有限公司 Link detection device and method
CN105610594A (en) * 2014-11-19 2016-05-25 华为技术有限公司 Service chain fault diagnosis method and service chain fault diagnosis device
WO2016116002A1 (en) * 2015-01-19 2016-07-28 中兴通讯股份有限公司 Method and device for automatically detecting otn network fault node
CN106034045A (en) * 2015-03-20 2016-10-19 中兴通讯股份有限公司 Ethernet link failure positioning method, device and system
EP3151464A1 (en) * 2014-05-26 2017-04-05 Huawei Technologies Co., Ltd. Fault detection method and apparatus for service chain
CN107819594A (en) * 2016-09-12 2018-03-20 中兴通讯股份有限公司 network failure locating method and device
CN109428741A (en) * 2017-08-22 2019-03-05 中兴通讯股份有限公司 A kind of detection method and device of network failure
CN110752952A (en) * 2019-10-25 2020-02-04 腾讯科技(深圳)有限公司 Network fault positioning method and device, network equipment and computer storage medium
CN110932882A (en) * 2019-10-21 2020-03-27 国网上海市电力公司 Network fault positioning method for HSR redundant network system

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101036330A (en) * 2004-12-01 2007-09-12 思科技术公司 System and methods for detecting network failure
CN102035694A (en) * 2010-12-20 2011-04-27 中兴通讯股份有限公司 Link detection device and method
EP3151464A1 (en) * 2014-05-26 2017-04-05 Huawei Technologies Co., Ltd. Fault detection method and apparatus for service chain
CN105610594A (en) * 2014-11-19 2016-05-25 华为技术有限公司 Service chain fault diagnosis method and service chain fault diagnosis device
WO2016116002A1 (en) * 2015-01-19 2016-07-28 中兴通讯股份有限公司 Method and device for automatically detecting otn network fault node
CN106034045A (en) * 2015-03-20 2016-10-19 中兴通讯股份有限公司 Ethernet link failure positioning method, device and system
CN107819594A (en) * 2016-09-12 2018-03-20 中兴通讯股份有限公司 network failure locating method and device
CN109428741A (en) * 2017-08-22 2019-03-05 中兴通讯股份有限公司 A kind of detection method and device of network failure
CN110932882A (en) * 2019-10-21 2020-03-27 国网上海市电力公司 Network fault positioning method for HSR redundant network system
CN110752952A (en) * 2019-10-25 2020-02-04 腾讯科技(深圳)有限公司 Network fault positioning method and device, network equipment and computer storage medium

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114448785A (en) * 2022-03-18 2022-05-06 新浪网技术(中国)有限公司 Method and device for positioning fault network equipment and electronic equipment
CN116708135A (en) * 2023-08-08 2023-09-05 中国电信股份有限公司 Network service fault monitoring method and device, electronic equipment and storage medium
CN116708135B (en) * 2023-08-08 2023-11-07 中国电信股份有限公司 Network service fault monitoring method and device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN112787843B (en) 2022-04-29

Similar Documents

Publication Publication Date Title
CN106605392B (en) System and method for operating on a network using a controller
CN109495322B (en) Network fault positioning method, related equipment and computer storage medium
US10178029B2 (en) Forwarding of adaptive routing notifications
US10826821B2 (en) Flow path detection
US6987726B1 (en) Management of duplicated node identifiers in communication networks
WO2013115177A1 (en) Network system and topology management method
CN113411834B (en) Message processing method, device, equipment and storage medium
WO2011155510A1 (en) Communication system, control apparatus, packet capture method and program
WO2016045098A1 (en) Switch, controller, system and link quality detection method
CN104780095A (en) Path detection method and device in SDN
CN112769632A (en) Method and system for detecting network fault of data center
CN112787843B (en) Method for detecting fault node, storage medium and electronic device
CN108616367B (en) Fault positioning method and network equipment
CN112311580B (en) Message transmission path determining method, device and system and computer storage medium
CN108566336A (en) A kind of network path acquisition methods and equipment
CN106936656B (en) Method, device and system for realizing packet loss detection
CN111614505B (en) Message processing method and gateway equipment
CN106302021B (en) Network flow forwarding abnormity detection method
US11336564B1 (en) Detection of active hosts using parallel redundancy protocol in software defined networks
US20210203591A1 (en) Method for determining route flapping information and related device
CN105743687B (en) Method and device for judging node fault
CN114006806A (en) Message processing method and device, switch equipment and storage medium
EP2858302B1 (en) Connectivity check method of service stream link, related apparatus and system
US20080130503A1 (en) Method and system for forwarding ethernet frames over redundant networks with all links enabled
CN109379239B (en) Method and device for configuring access switch in OpenStack environment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant