WO2021143524A1 - Procédé de détection de défaut et appareil associé - Google Patents

Procédé de détection de défaut et appareil associé Download PDF

Info

Publication number
WO2021143524A1
WO2021143524A1 PCT/CN2020/141140 CN2020141140W WO2021143524A1 WO 2021143524 A1 WO2021143524 A1 WO 2021143524A1 CN 2020141140 W CN2020141140 W CN 2020141140W WO 2021143524 A1 WO2021143524 A1 WO 2021143524A1
Authority
WO
WIPO (PCT)
Prior art keywords
lsp
network device
bfd
packet
message
Prior art date
Application number
PCT/CN2020/141140
Other languages
English (en)
Chinese (zh)
Inventor
侯大威
邓建玺
李帅
王彬
王明谱
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021143524A1 publication Critical patent/WO2021143524A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • This application relates to the field of communication technology, and in particular to a fault detection method and device used in the label switching path (English: Control Route Label Switched Path, abbreviation: Control Route Label Switched Path, abbreviation: In the CR-LSP scenario, a bidirectional link detection (English: Bidirectional Forwarding Detection, referred to as BFD) mechanism is used to detect whether there is a fault on the LSP.
  • a bidirectional link detection English: Bidirectional Forwarding Detection, referred to as BFD
  • the tunnel may include multiple CR-LSPs from a source node (English: Ingress) to a destination node (English: Egress).
  • BFD a mechanism that can quickly perform end-to-end detection, is usually used to detect whether the CR-LSP is faulty.
  • the process of detecting CR-LSP in the BFD mechanism includes: Ingress sends forward detection packets to Egress through LSP, and requires Egress to feed back reverse detection packets to Ingress, so as to determine whether the LSP is faulty. Since the LSP is a one-way path, the reverse detection message can only be determined by the Internet Protocol (English: Internet Protocol, referred to as: IP) routing method to determine its transmission path, and the IP path determined by the IP routing method is probably not After each label switching node in the LSP (English: Label Switching Router, LSR for short), that is, the forward detection packet and the reverse detection packet do not share the same path. In this way, the detection result reflects the determination of the LSP and the IP routing method The overall failure of the IP path cannot accurately reflect whether the LSP fails.
  • IP Internet Protocol
  • the embodiments of the present application provide a fault detection method and device.
  • a reverse LSP co-path with the LSP to be detected on the destination node side the bidirectionality of the BFD mechanism and the conflict of the unidirectional LSP are overcome, and optimization is achieved.
  • the BFD mechanism can perform more accurate fault detection on LSPs.
  • the embodiments of the present application provide a fault detection method, which is applied to the first network device of the first LSP to be detected in the CR-LSP scenario (that is, the destination node of the first LSP).
  • the fault detection process can be It includes: the second network device (ie, the source node of the first LSP) sends a first packet to the first network device via the first LSP, wherein the first packet carries path information of the first LSP, and
  • the first LSP includes multiple LSRs arranged in sequence; then, after the first network device receives the first message, it can establish a second LSP from the first network device to the second network device according to the path information.
  • the LSRs included in the two LSPs are the same as the LSRs included in the first LSP, and the sequence of multiple LSRs in the second LSP is opposite to the sequence of the multiple LSRs in the first LSP; based on this, the first network device is The first BFD packet may be fed back to the second network device via the second LSP that is in the reverse common path, so that the second network device can determine the failure condition of the first LSP based on the first BFD packet.
  • the source node informs the destination node of the path information of the LSP to be detected, and the destination node establishes an LSP that shares the reverse path with the LSP to be detected based on the path information, using the forward LSP and the established reverse LSP
  • the common path feature makes it possible to transmit forward BFD packets and reverse BFD packets in the same path in BFD detection.
  • the BFD detection result can accurately reflect the failure of the LSP to be detected, which overcomes the bidirectional and unidirectional BFD mechanism.
  • LSP conflicts that is, the current BFD detection of forward BFD packets and reverse BFD packets are likely to not share the same path, causing the detection result to fail to accurately reflect the problem of LSP failures, and achieve faster and more accurate fault detection for LSPs.
  • the first message may be, for example, an LSP-Ping message, specifically an LSP-Ping request message.
  • the path information of the first LSP may use the extended type length value (English: Type Length) in the LSP-Ping message. Value (abbreviated as: TLV) field carried.
  • the path information of the first LSP may be, for example, the IP address of each label switching node (English: Label Switched Router, LSR for short) through which the first LSP passes.
  • LSR Label Switched Router
  • the second network device can also send a second BFD packet to the first network device through the first LSP to meet the characteristics of the two-way detection of the BFD mechanism, and the first network device can also receive the second BFD packet according to whether it can receive the second BFD packet.
  • the second BFD packet sent by the network device via the first LSP determines the fault condition of the first LSP.
  • the embodiment of the present application may also determine at the first network device whether it has the ability to establish a second LSP, and inform the source node of the first LSP (ie, the second network device) of the capability. , So that the second network device determines its specific strategy for fault detection.
  • the first network device determines that it has the ability to establish a second LSP
  • the first network device can not only apply for and cooperate with the second network device to establish the second LSP, but also send the second LSP to the second network device.
  • a message the second message carries capability information, and the capability information is used to characterize that the first network device has the ability to establish a second LSP.
  • the second network device can determine that the BFD mechanism is used for fault detection, that is, based on the first LSP and the second LSP, the first network device and the second network device negotiate the configuration parameters of BFD; According to the configuration parameters, the second network device sends a BFD packet to the first network device via the first LSP.
  • the first network device After receiving the BFD packet via the first LSP, the first network device also sends the BFD packet based on the configuration parameters determined through negotiation. The second network device feeds back the response message.
  • the BFD mechanism provided by the embodiment of the present application can realize rapid and accurate fault detection of the first LSP.
  • the first network device determines that it does not have the ability to establish a second LSP
  • the first network device may not perform the process of applying and cooperating with the second network device to establish the second LSP, but may send the second packet to the second network device by way of IP routing, the capability information carried in the second packet, It is used to characterize that the first network device does not have the ability to establish a second LSP; or, after the first network device receives the first packet sent by the second network device through the first LSP to be detected, the second network device may not The first message is sent in response, and the second network device can also determine that the first network device does not have the ability to establish a second LSP when it does not get a response regarding the first message.
  • the second network device can choose not to use the BFD mechanism to perform fault detection on the first LSP, or, if it can tolerate the error in the detection result obtained by the current BFD mechanism to detect CR-LSP, it can also choose to use the current BFD mechanism to perform fault detection on the first LSP.
  • An LSP performs fault detection.
  • the method provided in the embodiments of the present application can allow the source node to perceive the ability of the destination node to establish the second LSP, so that the source node can configure its mechanism to detect the failure of the first LSP according to requirements, thereby achieving more flexibility for the first LSP Fault detection.
  • the embodiments of the present application also provide a fault detection method, which is applied to the second network device of the first LSP to be detected in the CR-LSP scenario (ie, the source node of the first LSP), and the process of fault detection It may include: the second network device sends a first packet to the first network device (that is, the destination node of the first LSP) through the first LSP to be detected, where the first packet carries path information of the first LSP ,
  • the first LSP includes a plurality of LSRs arranged in sequence; then, the second network device receives the first BFD packet sent by the first network device via the second LSP, where the second LSP is the second network device based on the received
  • the path information is established, the second LSP includes the multiple LSRs, and the sequence of the multiple LSRs in the second LSP is opposite to the sequence of the multiple LSRs in the first LSP; then, the second network The device can then determine the detection result of the first LSP based on the first BFD packet.
  • the source node informs the destination node of the path information of the LSP to be detected, and the destination node establishes an LSP that shares the reverse path with the LSP to be detected based on the path information, using the forward LSP and the established reverse LSP
  • the common path feature makes the forward BFD packets and the reverse BFD packets share the same path in the BFD detection.
  • the BFD detection results can accurately reflect the failure of the LSP to be detected, which overcomes the bidirectionality of the BFD mechanism and the conflict of unidirectional LSPs. That is, in the current BFD detection, the forward BFD packet and the reverse BFD packet are likely not to share the same path, resulting in the problem that the detection result cannot accurately reflect the LSP failure condition, and realizes the faster and more accurate failure detection of the LSP.
  • the first message may be, for example, an LSP-Ping message, specifically an LSP-Ping request message.
  • the path information of the first LSP may be carried by the extended TLV field in the LSP-Ping message.
  • the path information of the first LSP may be, for example, the IP addresses of each LSR passed by the first LSP.
  • the second network device sends the first packet carrying the path information of the first LSP, which is equivalent to providing the first network device with a basis for establishing a second LSP that shares the reverse path with the first LSP, so that the first network device It is possible to establish a second LSP.
  • the second network device can also send a second BFD packet to the first network device through the first LSP to meet the characteristics of the two-way detection of the BFD mechanism, and the first network device can also receive the second BFD packet according to whether it can receive the second BFD packet.
  • the second BFD packet sent by the network device via the first LSP determines the fault condition of the first LSP.
  • the embodiment of the present application may also determine at the first network device whether it has the ability to establish a second LSP, and inform the source node of the first LSP (ie, the second network device) of the capability. , So that the second network device can determine its specific strategy for fault detection.
  • the second network device can not only cooperate with the first network device to establish the second LSP, but also receive the second report sent by the first network device.
  • the second packet carries capability information, and the capability information is used to characterize that the first network device has the ability to establish a second LSP.
  • the second network device can determine that the BFD mechanism is used for fault detection, that is, based on the first LSP and the second LSP, the second network device and the first network device negotiate the BFD configuration parameters; and, based on all the negotiated parameters According to the configuration parameters, the second network device sends a BFD packet to the first network device via the first LSP.
  • the first network device After receiving the BFD packet via the first LSP, the first network device also sends the BFD packet based on the configuration parameters determined through negotiation. The second network device feeds back the response message.
  • the BFD mechanism provided by the embodiment of the present application can realize rapid and accurate fault detection of the first LSP.
  • the second network device can choose not to use the BFD mechanism to detect the failure of the first LSP, or, if the current BFD mechanism can tolerate the detection obtained by the CR-LSP If the result is incorrect, you can also choose to use the current BFD mechanism to perform fault detection on the first LSP.
  • the method provided in the embodiments of the present application can allow the source node to perceive the ability of the destination node to establish the second LSP, so that the source node can configure its mechanism to detect the failure of the first LSP according to requirements, thereby achieving more flexibility for the first LSP Fault detection.
  • the embodiment of the present application may further include: the second network device determines the detection result of the first LSP according to the response message.
  • the second network device determines that the first LSP is not faulty; on the contrary, if the second network device is sending the next BFD message If the response packet corresponding to the BFD packet is not received at the time of writing, it is determined that the first LSP is faulty.
  • a preset duration (for example, 10 milliseconds) can also be set, and the preset duration can be used to indicate the maximum time allowed to elapse between sending a BFD message and receiving its corresponding response message. Then, If the second network device receives the response message corresponding to the BFD message within the preset period of time, it is determined that the first LSP is not faulty; on the contrary, if the second network device has not received the BFD message for the preset period of time after sending it The response packet corresponding to the BFD packet determines that the first LSP is faulty.
  • the second network device may also switch the traffic carried by the first LSP to the backup LSP of the first LSP to ensure the normal transmission of traffic in the network; and
  • the second network device can also report an alarm message above, which is used to inform the control user that the first LSP has failed, so that the technicians can detect and repair it as soon as possible.
  • the second network device will restore the traffic from the backup. Switch back to the first LSP on the LSP.
  • CR-LSP management in MPLS TE tunnel so that traffic can be safely and reliably transmitted in the network.
  • the embodiments of the present application also provide a fault detection method, which is applied to the first network device (that is, the destination node of the first LSP) of the first LSP to be detected in the CR-LSP scenario, and the fault detection process It may include: the second network device (that is, the source node of the first LSP) sends a first packet to the first network device via the first LSP, where the first packet carries path information of the first LSP,
  • the first LSP includes a plurality of LSRs arranged in sequence; at this time, in one case, if the first network device determines that it has the ability to establish a reverse common path second LSP, it executes the establishment of the slave according to the received path information.
  • the second LSP from the second network device to the first network device, so as to subsequently perform BFD detection between the first network device and the second network device based on the first LSP and the second LSP.
  • the first network device determines that it does not have the ability to establish a reverse common path second LSP
  • the first network device can send a second message to the second network device through IP routing to inform the first network device
  • a network device does not have the ability to establish a second LSP, or the first network device does not reply.
  • the second network device does not receive a reply, it sends the first network device to the first network device every preset time period.
  • the source node can perceive the destination node to establish the reverse common-path LSP capability, so that the source node can decide the specific method to be used in subsequent failure detection, thereby enabling the failure detection of the LSP in the CR-LSP scenario More flexible.
  • the embodiments of the present application also provide a fault detection method, which is applied to the second network device of the first LSP to be detected in the CR-LSP scenario (ie, the source node of the first LSP), and the process of fault detection It may include: the second network device sends a first packet to the first network device (that is, the destination node of the first LSP) via the first LSP, where the first packet carries path information of the first LSP,
  • the first LSP includes a plurality of LSRs arranged in sequence; in this case, in one case, the second network device cooperates with the first network device to establish a reverse common-path second LSP, then the first network device and the second network Between devices, BFD detection is performed based on the first LSP and the second LSP.
  • the second network device receives the second packet sent by the first network device, it informs the first network device that it does not have the ability to establish a reverse common path second LSP, or the second network device is in advance. Assuming that no reply to the first message is received for the duration, then the first message is sent to the first network device every preset duration. When the number of consecutively sending the first message reaches the preset number of times, the first message is determined The network device does not have the ability to establish the second LSP; in this way, after the second network device determines that the first network device does not have the ability to establish the second LSP, it can choose to use the current BFD mechanism to detect the first LSP according to the actual detection needs of the user.
  • the failure condition of the LSP or the option to no longer use the BFD mechanism to perform failure detection on the first LSP. It can be seen that, in the embodiment of the present application, by allowing the source node to perceive the ability of the destination node to establish a reverse common-path LSP, the source node can decide the specific method to be used in subsequent failure detection, thereby achieving a more flexible response to the LSP in the CR-LSP scenario. Fault detection.
  • an embodiment of the present application also provides a first network device, which is applied to a label-switched path CR-LSP scenario of a constrained path.
  • the first network device includes a receiving unit, a sending unit, and a processing unit.
  • the receiving unit is configured to receive a first packet sent by the second network device through the first LSP to be detected, the first packet carries path information of the first LSP, and the source node of the first LSP is the first network device ,
  • the destination node of the first LSP is the second network device, and the first LSP includes a plurality of label switching node LSRs arranged in sequence.
  • the processing unit is configured to establish a second LSP from the first network device to the second network device according to the path information.
  • the second LSP includes multiple LSRs, and the sequence of the multiple LSRs in the second LSP is consistent with that of the multiple LSRs.
  • the sequence in the first LSP is reversed.
  • the sending unit is configured to send the first bidirectional link detection BFD packet to the second network device via the second LSP, so that the second network device determines the failure condition of the first LSP based on the first BFD packet.
  • the receiving unit in the first network device is further configured to receive the second BFD packet sent by the second network device via the first LSP.
  • the sending unit in the first network device is also used to send a second message to the second network device.
  • the second message carries capability information, and the capability information is used to characterize the capability of the first network device. The ability to establish a second LSP.
  • the processing unit in the first network device is further configured to, before sending the first bidirectional link detection BFD message to the second network device via the second LSP, based on the first LSP and the second The LSP negotiates BFD configuration parameters with the second network device; then, the sending unit is specifically configured to send the first BFD packet to the second network device via the second LSP based on the configuration parameters determined through the negotiation.
  • the first packet is an LSP-Ping packet
  • the path information is carried by the extended type length value TLV field in the LSP-Ping packet.
  • first network device provided by the fifth aspect is used to perform the related operations mentioned in the first aspect or the third aspect.
  • first aspect and the third aspect please refer to the first aspect and the third aspect. The relevant description of the three aspects will not be repeated here.
  • the embodiments of the present application also provide a second network device, which is applied to a label-switched path CR-LSP scenario of a constrained path.
  • the second network device includes a sending unit, a receiving unit, and a processing unit.
  • the sending unit is configured to send a first packet to the first network device via the first LSP to be detected, the first packet carrying path information of the first LSP, and the source node of the first LSP is the second network device ,
  • the destination node is the first network device, and the first LSP includes a plurality of label switching node LSRs arranged in sequence.
  • the receiving unit is configured to receive a first bidirectional link detection BFD message sent by the first network device via a second LSP, where the second LSP is established by the second network device based on path information, and the second LSP includes multiple LSRs, In addition, the sequence of the multiple LSRs in the second LSP is opposite to the sequence of the multiple LSRs in the first LSP.
  • the processing unit is configured to determine the detection result of the first LSP based on the first BFD packet.
  • the sending unit in the second network device is further configured to send the second BFD packet to the first network device via the first LSP.
  • the receiving unit in the second network device is also used to receive a second packet sent by the first network device, the second packet carries capability information, and the capability information is used to characterize the first network device Have the ability to establish a second LSP.
  • the processing unit in the second network device is further configured to, before receiving the first bidirectional link detection BFD message sent by the first network device via the second LSP, based on the first LSP and the first LSP
  • the second LSP negotiates BFD configuration parameters with the first network device; then, the receiving unit is specifically configured to: receive the first BFD message sent by the first network device via the second LSP based on the negotiated configuration parameters.
  • the processing unit in the second network device is further configured to switch the traffic carried on the first LSP to the third LSP if the detection result indicates that the first LSP is faulty.
  • the source node is the second network device, and the destination node of the third LSP is the first network device.
  • the first packet is an LSP-Ping packet
  • the path information is carried by the extended type length value TLV field in the LSP-Ping packet.
  • the second network device provided by the sixth aspect is used to perform the related operations mentioned in the second aspect or the fourth aspect.
  • the specific implementation and the achieved effects please refer to the second aspect and the first aspect. The description of the four aspects will not be repeated here.
  • an embodiment of the present application also provides a first network device, including: a memory and a processor.
  • the memory is used to store program codes or instructions;
  • the processor is used to run the program codes or instructions, so that the device executes the method provided in the first aspect or the third aspect.
  • an embodiment of the present application also provides a second network device, including: a memory and a processor.
  • the memory is used to store program codes or instructions;
  • the processor is used to run the program codes or instructions, so that the device executes the method provided in the above second or fourth aspect.
  • the embodiments of the present application also provide a network system.
  • the network system includes the first network device provided in the fifth aspect and the second network device provided in the sixth aspect; or, the network system may also include the seventh aspect Provide the first network device and the second network device provided in the eighth aspect.
  • the embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores program codes or instructions, which when run on a computer, cause the computer to execute the first and second aspects above. Aspect, the third aspect, or any one of the methods provided in the fourth aspect.
  • the embodiments of the present application also provide a computer program product.
  • the network device can execute the first aspect, the second aspect, the third aspect, or the fourth aspect.
  • the method provided in any one of the possible implementations.
  • FIG. 1 is a schematic diagram of a network system framework involved in an application scenario in an embodiment of this application;
  • Figure 2 is a signaling flow chart of a method for detecting LSP 1 in an embodiment of this application;
  • FIG. 3 is a signaling flowchart of another method for detecting LSP 1 in an embodiment of this application.
  • FIG. 4 is a signaling flowchart of a fault detection method 100 in an embodiment of the application
  • FIG. 5 is a schematic diagram of a format of a first message in an embodiment of this application.
  • FIG. 6a is a schematic diagram of the format of a TLV extended by a first message in an embodiment of this application.
  • FIG. 6b is a schematic diagram of the format of another TLV extended by the first message in an embodiment of this application.
  • FIG. 7 is a schematic structural diagram of a first network device 700 in an embodiment of this application.
  • FIG. 8 is a schematic structural diagram of a second network device 800 in an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of another first network device 900 in an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of another second network device 1000 in an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a network system 1100 in an embodiment of this application.
  • An MPLS TE tunnel usually includes multiple LSPs with the same source node and destination node. In order to ensure that the MPLS TE tunnel can effectively transmit service streams, it is necessary to perform fault detection on the LSPs and switch the service streams carried on the failed LSP. To other fault-free LSPs, the service flow can be effectively transmitted on the fault-free LSPs.
  • BFD is an end-to-end detection mechanism for quickly sending and receiving packets. It can quickly send BFD packets and receive BFD packets from the opposite end, and determine the fault condition of the link through which forward BFD packets and reverse BFD packets pass. . Since the BFD mechanism can realize the sending and receiving of BFD packets in milliseconds between the source node and the destination node, the BFD mechanism can meet the fast requirements for LSP fault detection in the MPLS TE tunnel.
  • the process of using the BFD mechanism to detect LSP failures can include: the source node sends forward BFD packets to the destination node through the LSP to be detected, and the destination node sends reverse BFD packets to the source node through IP routing. , The source node determines whether the LSP is faulty based on the received reverse BFD packet. Since the LSP is a unidirectional constrained path, the IP path determined by the IP routing method may not be exactly the same as the LSR of the label switching node that the LSP passes through. In this way, the detection result reflects the IP path determined by the LSP and the IP routing method. The overall failure situation, rather than just reflecting whether the LSP has failed.
  • FIG. 1 Take the MPLS TE scenario shown in Figure 1 as an example.
  • This scenario includes network equipment 110, network equipment 120, network equipment 130, network equipment 140, and network equipment 150, where LSP 1 passes through: network equipment 110-> Network equipment 120->network equipment 130; LSP 2 goes through in sequence: network equipment 110->network equipment 150->network equipment 140->network equipment 130. Then, as shown in FIG. 2, in the scenario shown in FIG.
  • the process of performing fault detection on the LSP 1 may specifically include: S11, the network device 110 sends a BFD message 1 to the network device 130 through the LSP 1; S12, Based on the IP routing method, the network device 130 sends the BFD message 2 to the network device 110 through the IP path 1, where the IP path 1 passes through the network device 130->network device 140->network device 150->network device 110 in turn; S13, The network device 110 determines the detection result according to the BFD message 2; S14, if the detection result indicates a failure, it switches the traffic carried on the LSP 1 to the LSP 2.
  • the detection result indicates the failure, which may be caused by the failure of the network equipment or link that LSP 1 passes through, or the link or network equipment that IP path 1 passes through. If IP path 1 passes through the link Or network equipment failure. Since all LSRs included in IP path 1 and LSP 2 are the same, LSP 2 is likely to fail. Then, after S14 is executed, it is likely that traffic will be switched from the normal LSP 1 to the failed LSP 2 by mistake. Therefore, the traffic cannot be effectively transmitted in the MPLS TE tunnel.
  • a fault detection method is provided, which is applied in a CR-LSP scenario.
  • the source node informs the destination node of the path information of the first LSP to be detected .
  • the destination node establishes a second LSP that is in the reverse direction with the first LSP to be detected based on the path information, so that the reverse BFD packet in the BFD detection can pass through the second LSP and the forward BFD packet in the reverse direction.
  • the transmission of the first LSP overcomes the conflict between the bidirectionality of the BFD mechanism and the unidirectionality of the LSP. That is, in the current BFD detection, the BFD message and the response message are likely to not share the same path, which causes the detection result to fail to accurately reflect the LSP failure situation. Problem, to achieve faster and more accurate fault detection for LSP.
  • the specific fault detection process may include: S21, the network device 110 sends an LSP-Ping to the network device 130 through the LSP 1 Message, the LSP-Ping message carries path information of LSP 1, for example: the IP address list of each node included in LSP 1, as shown in Figure 1, on the link from network device 110 to network device 120
  • the IP address corresponding to the device 110 is IP 1
  • the IP address corresponding to the network device 120 on the link from the network device 120 to the network device 130 is IP 3.
  • the path information of the LSP 1 includes: IP 1 and IP 3; S22,
  • the network device 130 establishes an LSP 1'according to the path information of the LSP 1, and the LSP 1'passes through: network device 130->network device 120->network device 110, as shown in Figure 1, from network device 130 to network device 120
  • the IP address corresponding to the network device 130 on the link is IP 4
  • the IP address corresponding to the network device 120 on the link from the network device 120 to the network device 110 is IP 2.
  • the path information of the LSP 1' can include: IP 4 and IP 2; S23, the network device 110 and the network device 130 negotiate to determine the configuration parameters of BFD, for example: BFD detection period; S24, the network device 110 sends a BFD packet to the network device 130 through the LSP 1 based on the configuration parameters determined by the negotiation 1; S25, the network device 130 sends a BFD packet 2 to the network device 110 via the LSP 1'based on the configuration parameters; S26, the network device 110 determines the detection result of the LSP 1 based on the BFD packet 2.
  • BFD detection period for example: BFD detection period
  • S24 the network device 110 sends a BFD packet to the network device 130 through the LSP 1 based on the configuration parameters determined by the negotiation 1
  • S25 the network device 130 sends a BFD packet 2 to the network device 110 via the LSP 1'based on the configuration parameters
  • S26 the network device 110 determines the detection result of the LSP 1 based on the BFD packet 2.
  • the network device 110 informs the network device 130 of the path information of the LSP 1, and the network device 130 can establish an LSP 1'that shares the reverse path with the LSP 1 based on the path information, so that the BFD message and response message in the BFD detection can be Transmission is carried out through the reverse common-path LSP 1 and LSP 1'. After the same LSR, the detection result can accurately reflect the failure detection of LSP 1.
  • network equipment and nodes refer to the same meaning in this application, and can be used interchangeably.
  • the network device may specifically include, but is not limited to, a switch, a router, or a firewall.
  • the LSP may be a CR-LSP determined between the source node and the destination node through constraints such as link costs or labels.
  • the CR-LSP is a unidirectional path and includes multiple Orderly arranged label switching node LSR. Adjacent LSRs can be directly connected or connected through a transit node. In the embodiment of this application, for the LSP to be detected and the established LSP in the reverse direction, only the LSRs included in it are concerned. Including transit nodes and whether the transit nodes are consistent will not be considered.
  • two LSPs are in the reverse common path, which means that all LSRs included in the two LSPs are the same, and the order of the LSRs in one LSP is opposite to the order of the LSRs in the other LSP.
  • the source node in an LSP is the destination node of another LSP
  • the destination node in an LSP is the source node of another LSP
  • the second LSR in an LSP is the penultimate LSR of another LSP, and so on .
  • FIG. 4 is a signaling flowchart of a fault detection method 100 in an embodiment of the application.
  • the method 100 is applied in a CR-LSP scenario, and the embodiment of the present application is introduced with the interaction between the source node and the destination node of the first LSP to be detected.
  • the method 100 may be applied to the network scenario shown in FIG.
  • the method 100 may be to perform fault detection on the LSP 1 from the network device 110 to the network device 130, where LSP 1 and LSP 1'respectively correspond to The first LSP and the second LSP in the method 100, the network device 110 and the network device 130 respectively correspond to the second network device and the first network device in the method 100; as another example, the method 100 can also be used for the network device 130 Perform fault detection on the LSP 1'of the network device 110, where LSP 1'and LSP 1 respectively correspond to the first LSP and the second LSP in the method 100, and the network device 130 and the network device 110 respectively correspond to the first LSP in the method 100.
  • the second network device and the first network device are examples of the LSP 1 from the network device 110 to the network device 130, where LSP 1 and LSP 1'respectively correspond to The first LSP and the second LSP in the method 100, the network device 110 and the network device 130 respectively correspond to the second network device and the first network device in the method 100; as another example, the method 100 can also be used for the
  • the method 100 may include the following S101 to S108, for example:
  • the second network device sends a first packet to the first network device via the first LSP to be detected, where the first packet carries path information of the first LSP, and the source node of the first LSP is the second network device, The destination node of the first LSP is the first network device, and the first LSP includes multiple LSRs arranged in sequence.
  • the first network device receives a first packet sent by the second network device through the first LSP to be detected.
  • the first LSP refers to the LSP created by the second network device from the second network device to the first network device.
  • the first LSP may include multiple LSRs.
  • the positions of the multiple LSRs in the first LSP are fixed, that is, the first LSP includes multiple LSRs arranged in sequence.
  • the first LSP includes a plurality of LSRs arranged in sequence, namely: network device 110, network device 120, and network device 130.
  • the multiple LSRs of the first LSP may also include at least one other LSR, such as: Among the multiple LSRs, the source node is the network device 110, the destination node is the network device 130, and other LSRs only include the network device 120.
  • the embodiment of the present application may further include: S31, the second network device applies to establish a CR-LSP from the second network device to the first network device, and establishes the CR-LSP through cooperation with the first network device The first LSP, and save the path information of the first LSP; S32, if the first LSP needs to be detected for failure, the second network device can enable BFD to trigger the establishment of a BFD session, for example: through configuration commands To enable the BFD capability on the second network device.
  • the path information is used to indicate the LSR experienced by the first LSP and the sequence in which each LSR appears in the first LSP.
  • the path information of the first LSP may be an IP address list composed of the IP addresses of each hop LSR, each The position of the IP address in the IP address list matches the position of the LSR corresponding to the IP address in the first LSP. Assuming that the first LSP is the LSP 1 in the scenario shown in FIG. 1, and the IP address of the network device 110 is IP 1, the IP address of the network device 120 is IP 2, and the IP address of the network device 130 is IP 3. Then, the first The path information of an LSP is as follows: IP 1, IP 2, and IP 3.
  • the second network device can generate a first message based on the configuration information, and send the first message to the first network device to inform the first network device of the first message to be detected.
  • the path information of an LSP provides a data basis for the first network device to establish a second LSP that is in the reverse direction with the first LSP in the subsequent S103.
  • the first message may be an LSP-Ping message.
  • the specific format is shown in Figure 5, and it may specifically include a version number (English: Version Number) field, which is used to identify the version number of the MPLS command, for example:
  • the version number field can be 1; the zero (English: Must Be Zero) field must be filled with all 0s, and this field can be ignored when the message is received;
  • the message type (English: Message Type) field is used to identify the MPLS command
  • the reply mode (English: Reply Mode) field, It is used to indicate the reply mode adopted by the node receiving the message.
  • IPv4 Internet Protocol version 4
  • UDP User Datagram Protocol
  • return subcode English: Return Subcode
  • the sender handle (English: Sender's Handle) field is used to identify a specific MPLS command, and its value can be randomly generated when an MPLS command request is sent;
  • the sequence number (English: Sequence Number) field, the same Used to identify a specific MPLS command, valid in a process;
  • the timestamp (English: Timestamp) field, specifically can use the time format defined by the Network Time Protocol (English: Network Time Protocol, abbreviated as: NTP), which can specifically include the sending time (For example: the field corresponding to the second and the field corresponding to the millisecond) and the receiving time (for example: the field corresponding to the second and the field corresponding to the millisecond); reserved area, the reserved area can be extended with multiple type length values (English: Type Length Value (abbreviation: TLV) field.
  • NTP Network Time Protocol
  • the path information of the first LSP is: IP 1 and IP 3 in order.
  • the first packet can be extended in the LSP-Ping packet
  • a TLV field carries path information.
  • the format of the extended TLV field can be seen in Figure 6a.
  • Type can be 127, which is used to identify that the TLV field carries path information of LSP 1, and the value of Length is equal to the extended TLV.
  • the length of the field; Value can include reserved fields, the number of addresses (English: Hop Num), and specific path information. Specifically, reserved fields can be filled with 0, Hop Num can be 2, and path information can include IP 1 and IP 3.
  • the first message can also extend multiple TLV fields in the LSP-Ping message, and multiple TLV fields collectively carry the path information, and each TLV field carries an IP address in the path information.
  • the format of the extended TLV field can be seen in Figure 6b.
  • the first network device establishes a second LSP from the first network device to the second network device according to the path information, the second LSP includes the multiple LSRs, and the arrangement of the multiple LSRs in the second LSP The sequence is opposite to the sequence of the multiple LSRs in the first LSP.
  • the first network device may first determine whether it has the first packet that carries the path information of the first LSP before performing the following S103. Second, if the LSP has the capability, S103 is executed; if not, S103 to S108 are not executed.
  • S103 may specifically include: the first network device determines, according to the path information, the LSRs that the second LSP that needs to be established in turn needs to pass through; the first network device cooperates with the second network device to create the second network device according to the determined LSR.
  • LSP refers to an LSP that is in the reverse direction of the first LSP created by the first network device, and the source node of the second LSP is the first network device, and the destination node is the second network device.
  • the path information of the second LSP is: IP 4 and IP 2 in order.
  • the first network device may enable BFD to trigger the establishment of a backhaul BFD session, for example, the BFD capability on the first network device may be enabled through a configuration command.
  • the first network device may also send a second packet to the second network device.
  • the second message carries capability information, which is used to characterize that the first network device has the ability to establish a second LSP. It should be noted that the timing for the first network device to send the second message to the second network device can be performed before S103, after S103, or simultaneously with S103, which will not be specified in this embodiment of the application. limited.
  • the first network device determines that it does not have the ability to create a second LSP that shares a reverse path with the first LSP, the first network device can perform different operations according to actual needs, for example: the first network The device may send a second packet to the second network device through IP routing.
  • the second packet carries capability information, and the capability information is used to indicate that the first network device does not have the ability to establish a second LSP, then the second The network device can make specific decisions about fault detection.
  • a preset time interval for example: 1 second
  • the second network device determines that the first network device does not have the ability to establish the second LSP, it can choose not to use the BFD mechanism that cannot accurately detect the failure to perform failure detection on the first LSP according to the actual failure detection requirements of the user; or, You can also choose to use the current BFD mechanism to detect the failure of the first LSP.
  • the current BFD mechanism for detecting the failure of the first LSP may include, for example: S41, the second network device sends an LSP-Ping request message to the first network device, which carries the identifier of the second network device; S42, A network device records the identifier of the second network device, carries both its own identifier and the identifier of the second network device in the LSP-Ping response message, and sends it to the second network device; S43, the second network device Record the identifier of the first network device; S44, the second network device negotiates with the first network device to determine BFD configuration parameters; S45, the second network device sends a forward BFD packet to the first network device through the first LSP; S46, the first network device sends a reverse BFD packet to the second network device via IP routing; S47, the second network device determines the fault condition of the first LSP according to the reverse BFD packet.
  • the unsuccessful establishment of the second LSP may be because the first network device does not support the establishment of the second LSP, or it may be due to other reasons, such as insufficient label resources.
  • the first network device does not have the ability to establish a second LSP in the embodiments of the present application may mean that the first network device does not support the establishment of the second LSP, or it may refer to a situation where the establishment of the second LSP is unsuccessful due to other reasons.
  • the source node can perceive the destination node to establish the reverse common-path LSP capability, so that the source node can decide the specific method used in subsequent failure detection, so that the failure of the LSP in the CR-LSP scenario Detection is more flexible.
  • a second LSP that is in the reverse direction of the first LSP to be detected is established, so that when the BFD mechanism is subsequently used to detect the first LSP, the response message of the BFD message and the BFD The message is transmitted through the reverse common-path LSP, thereby accurately detecting the failure of the first LSP, providing an indispensable data foundation.
  • S104 The second network device sends the first BFD packet to the first network device through the first LSP.
  • the first network device receives the first BFD packet sent by the second network device via the first LSP.
  • the first network device sends a second BFD packet to the second network device through the second LSP.
  • the second network device receives the second BFD packet sent by the first network device via the second LSP.
  • the second network device determines the detection result of the first LSP based on the second BFD packet.
  • the process of using the BFD mechanism to detect the failure of the LSP to be detected includes three parts: the first part is to establish an LSP that shares the reverse path with the LSP to be detected; the second part, The configuration parameters for sending and receiving BFD messages are determined through negotiation; the third part, based on the operation results of the first and second parts, performs fault detection on the LSP to be detected through the BFD message and its corresponding response message.
  • the first part can correspond to the above S101 to S103
  • the specific process implemented in the second part can be: between S103 and S104, based on the first LSP and the second LSP, the first network device and the second network device negotiate the configuration of BFD Parameters, the configuration parameters are used to standardize the parameters for subsequent execution of S104-S107, for example: the period of execution of S104 and S107 (for example: 10 seconds).
  • the third part may be: the second network device sends a forward first BFD packet to the first network device via the first LSP based on the configuration parameters determined through negotiation; and the first network device receives the first BFD packet Then, based on the configuration parameters determined through negotiation, a second reverse BFD packet is sent to the second network device via the second LSP; the second network device receives the second BFD packet to determine the detection result of the first LSP.
  • the detection result may be determined according to a configuration parameter manually set or negotiated in advance. As an example, as long as the second network device receives the second BFD packet, it determines that the first LSP is not faulty; on the contrary, if the second network device does not receive the second BFD packet, it determines that the first LSP is faulty.
  • a preset duration (for example: 30 milliseconds) can also be set, and the preset duration can be manually set, or it can be one of the configuration parameters determined through negotiation to indicate the first network device The longest period allowed to pass the second BFD packet, then, if the second network device receives the next second BFD packet within the preset time interval, it is determined that the first LSP is not faulty; on the contrary, if the second network device If the device does not receive the next second BFD packet within the preset interval, it determines that the first LSP is faulty.
  • the specific value of the preset duration can be flexibly set according to the actual situation.
  • S104-S108 may specifically include: network device 110 sends BFD packets 1 to network device 130 via LSP 1 every 10 milliseconds; network device 130 sends BFD packets 1 via LSP 1'every 20 milliseconds The network device 110 sends a BFD message 2.
  • the network device 110 receives the next BFD message 2 within 60 milliseconds (that is, 3 times of 20 milliseconds, and 3 is a preset multiple) after receiving a BFD message 2, then it determines LSP 1'is fault-free, thus confirming that the common LSP 1 is fault-free; if the network device 110 receives a BFD message 2 after 80 milliseconds before receiving the next BFD message 2, or, after receiving a BFD message If the next BFD message 2 is not received after message 2, it is determined that LSP 1'is faulty, and thus the common LSP 1 is faulty.
  • the network device 130 receives the next BFD message 1 within 40 milliseconds (that is, 4 times of 10 milliseconds, 4 being a preset multiple) after receiving a BFD message 1, then, Make sure that the LSP 1 is not faulty; if the network device 130 receives the next BFD packet 1 after 40 milliseconds after receiving a BFD packet 1, or it has not received the next BFD packet 1 Message 1, then it is determined that LSP 1 is faulty.
  • 10 milliseconds, 20 milliseconds, multiple 3, and multiple 4 may all be the configuration parameters negotiated in the second part.
  • the second network device may also switch the traffic carried by the first LSP to the backup LSP of the first LSP to ensure the normal transmission of traffic in the network; and
  • the second network device can also report an alarm message above, which is used to inform the control user that the first LSP has failed, so that the technicians can detect and repair it as soon as possible.
  • the second network device will restore the traffic from the backup. Switch back to the first LSP on the LSP.
  • the source node can inform the destination node of the path information of the LSP to be detected, and the destination node establishes an LSP that shares the reverse path with the LSP to be detected based on the path information, so that the forward and reverse directions in the BFD detection BFD packets can be transmitted through a common LSP, which overcomes the current BFD mechanism for forward and reverse BFD packets using CR-LSP and IP routing respectively to determine the transmission path transmission, and the transmission determined by the two methods
  • CR-LSP and IP routing respectively to determine the transmission path transmission, and the transmission determined by the two methods
  • the use of the BFD mechanism provided in the embodiments of this application to detect the failure of the LSP not only takes advantage of the feature that the BFD mechanism can quickly complete the detection, but also based on the construction of the reverse common path LSP makes the use of the BFD mechanism to detect the failure of the LSP more accurately .
  • the embodiment of the present application also allows the source node to perceive whether the destination node has the ability to establish a reverse common path LSP, so that the source node can decide the specific method to be used in subsequent failure detection, so as to prevent the failure of the LSP in the CR-LSP scenario. Detection is more flexible.
  • an embodiment of the present application also provides a first network device 700, as shown in FIG. 7.
  • the first network device 700 is applied to a label-switched path CR-LSP scenario where a path is restricted.
  • the first network device 700 includes a receiving unit 701, a sending unit 702, and a processing unit 703.
  • the receiving unit 701 is configured to receive a first packet sent by the second network device through the first LSP to be detected, the first packet carrying path information of the first LSP, and the source node of the first LSP is the first network Device, the destination node of the first LSP is the second network device, and the first LSP includes a plurality of label switching node LSRs arranged in sequence.
  • the processing unit 703 is configured to establish a second LSP from the first network device to the second network device according to the path information.
  • the second LSP includes multiple LSRs, and the arrangement order of the multiple LSRs in the second LSP is consistent with the multiple LSRs. The arrangement order in the first LSP is reversed.
  • the sending unit 702 is configured to send the first bidirectional link detection BFD packet to the second network device via the second LSP, so that the second network device determines the failure condition of the first LSP based on the first BFD packet.
  • the receiving unit 701 in the first network device 700 is further configured to receive the second BFD packet sent by the second network device via the first LSP.
  • the sending unit 702 in the first network device 700 is also used to send a second message to the second network device.
  • the second message carries capability information, and the capability information is used to characterize the capability of the first network device. The ability to establish a second LSP.
  • the processing unit 703 in the first network device 700 is further configured to, before sending the first bidirectional link detection BFD message to the second network device through the second LSP, based on the first LSP and the second The LSP negotiates BFD configuration parameters with the second network device; then, the sending unit 702 is specifically configured to send the first BFD packet to the second network device via the second LSP based on the configuration parameters determined through the negotiation.
  • the first packet is an LSP-Ping packet
  • the path information is carried by the extended type length value TLV field in the LSP-Ping packet.
  • the first network device 700 shown in FIG. 7 may be the network device 130 in the example shown in FIG. 3, or the first network device mentioned in the method 100 shown in FIG. 4. Therefore, for various specific embodiments of the first network device 700, reference may be made to the corresponding embodiment of FIG. 3 and the related introduction of the method 100, which will not be repeated in this embodiment.
  • an embodiment of the present application also provides a second network device 800, as shown in FIG. 8.
  • the second network device 800 is applied to a CR-LSP scenario of a label-switched path with restricted paths.
  • the second network device 800 includes a sending unit 801, a receiving unit 802, and a processing unit 803.
  • the sending unit 801 is configured to send a first packet to the first network device via the first LSP to be detected, the first packet carrying path information of the first LSP, and the source node of the first LSP is the second network Device, the destination node is a first network device, and the first LSP includes a plurality of label switching node LSRs arranged in sequence.
  • the receiving unit 802 is configured to receive a first bidirectional link detection BFD message sent by the first network device via a second LSP, where the second LSP is established by the second network device based on path information, and the second LSP includes multiple LSRs , And the arrangement order of the multiple LSRs in the second LSP is opposite to the arrangement order of the multiple LSRs in the first LSP.
  • the processing unit 803 is configured to determine the detection result of the first LSP based on the first BFD packet.
  • the sending unit 803 in the second network device 800 is further configured to send the second BFD packet to the first network device via the first LSP.
  • the receiving unit 802 in the second network device 800 is further configured to receive a second packet sent by the first network device.
  • the second packet carries capability information, and the capability information is used to characterize the first network device. Have the ability to establish a second LSP.
  • the processing unit 803 in the second network device 800 is further configured to, before receiving the first bidirectional link detection BFD message sent by the first network device via the second LSP, based on the first LSP and the first LSP
  • the second LSP negotiates BFD configuration parameters with the first network device; then, the receiving unit 802 is specifically configured to receive the first BFD message sent by the first network device via the second LSP based on the negotiated configuration parameters.
  • the processing unit 803 in the second network device 800 is further configured to switch the traffic carried on the first LSP to the third LSP if the detection result indicates that the first LSP is faulty.
  • the source node is the second network device, and the destination node of the third LSP is the first network device.
  • the first packet is an LSP-Ping packet
  • the path information is carried by the extended type length value TLV field in the LSP-Ping packet.
  • the second network device 800 shown in FIG. 8 may be the network device 110 in the example shown in FIG. 3, or the second network device mentioned in the method 100 shown in FIG. 4. Therefore, for various specific embodiments of the second network device 800, reference may be made to the corresponding embodiment of FIG. 3 and the related introduction of the method 100, which will not be repeated in this embodiment.
  • an embodiment of the present application provides a first network device 900.
  • the first network device 900 may be the destination node in any of the foregoing embodiments, for example, it may be the network device 130 in the embodiment shown in FIG. 3, or may be the first network device in the embodiment shown in FIG.
  • the first network device 900 includes at least one processor 901, a bus system 902, a memory 903, and at least one transceiver 904.
  • the first network device 900 is a device with a hardware structure, and can be used to implement the functional modules in the first network device 700 shown in FIG. 7.
  • the processing unit 703 in the first network device 700 shown in FIG. 7 can be implemented by calling the code in the memory 903 by the at least one processor 901.
  • the first network device 700 shown in FIG. 7 The receiving unit 701 and the sending unit 702 in can be implemented by the transceiver 904.
  • the first network device 900 may also be used to implement the function of the first network device in any of the foregoing embodiments.
  • processor 901 may be a general-purpose central processing unit (central processing unit, CPU), network processor (NP), microprocessor, application-specific integrated circuit (ASIC) , Or one or more integrated circuits used to control the execution of the program of this application.
  • CPU central processing unit
  • NP network processor
  • ASIC application-specific integrated circuit
  • the above-mentioned bus system 902 may include a path for transferring information between the above-mentioned components.
  • the aforementioned transceiver 904 is used to communicate with other devices or a communication network.
  • the aforementioned memory 903 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), or other types that can store information and instructions.
  • the type of dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disk storage, optical discs Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by Any other medium accessed by the computer, but not limited to this.
  • the memory can exist independently and is connected to the processor through a bus.
  • the memory can also be integrated with the processor.
  • the memory 903 is used to store application program codes for executing the solutions of the present application, and the processor 901 controls the execution.
  • the processor 901 is configured to execute the application program code stored in the memory 903, so as to realize the functions in the method of the present patent.
  • the processor 901 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 9.
  • the first network device 900 may include multiple processors, such as the processor 901 and the processor 907 in FIG. 9. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • an embodiment of the present application provides a second network device 1000.
  • the second network device 1000 may be the source node in any of the foregoing embodiments, for example, it may be the network device 110 in the embodiment shown in FIG. 3, or may be the second network device in the embodiment shown in FIG. 4 .
  • the second network device 1000 includes at least one processor 1001, a bus system 1002, a memory 1003, and at least one transceiver 1004.
  • the second network device 1000 is a device with a hardware structure, and can be used to implement the functional modules in the second network device 800 described in FIG. 8.
  • the processing unit 803 in the second network device 800 shown in FIG. 8 can be implemented by calling the code in the memory 1003 by the at least one processor 1001.
  • the second network device 800 shown in FIG. 8 The receiving unit 802 and the sending unit 801 in can be implemented by the transceiver 1004.
  • the second network device 1000 may also be used to implement the function of the second network device in any of the foregoing embodiments.
  • the aforementioned processor 1001 may be a general-purpose central processing unit (central processing unit, CPU), network processor (network processor, NP), microprocessor, application-specific integrated circuit (ASIC) , Or one or more integrated circuits used to control the execution of the program of this application.
  • CPU central processing unit
  • NP network processor
  • ASIC application-specific integrated circuit
  • the above-mentioned bus system 1002 may include a path for transferring information between the above-mentioned components.
  • the above transceiver 1004 is used to communicate with other devices or communication networks.
  • the above-mentioned memory 1003 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions.
  • the type of dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disk storage, optical discs Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by Any other medium accessed by the computer, but not limited to this.
  • the memory can exist independently and is connected to the processor through a bus.
  • the memory can also be integrated with the processor.
  • the memory 1003 is used to store application program codes for executing the solutions of the present application, and the processor 1001 controls the execution.
  • the processor 1001 is configured to execute application program codes stored in the memory 1003, so as to realize the functions in the method of the present patent.
  • the processor 1001 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 10.
  • the apparatus 1000 may include multiple processors, such as the processor 1001 and the processor 1007 in FIG. 10. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the network system 1100 includes a first network device 1101 and a second network device 1102.
  • the first network device 1101 may specifically be the first network device 700 shown in FIG. 7 or the first network device 900 shown in FIG. 9; the second network device 1102 may specifically be the second network device 800 shown in FIG. Or the second network device 1000 shown in FIG. 10.
  • the first network device 1101 may be the first network device in the embodiment shown in FIG. 4 or the network device 130 in the embodiment shown in FIG. 3, and the second network device 1102 may be the implementation shown in FIG. 4.
  • the second network device in the example or the network device 110 in the embodiment shown in FIG. 3.
  • the embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores program codes or instructions. When it runs on a computer, the computer executes the implementation shown in Figure 3 or Figure 4 above. The method in any implementation mode in the example.
  • embodiments of the present application also provide a computer program product, which when running on a computer, causes the computer to execute any one of the aforementioned methods 100.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé de détection de défaut et un appareil associé. Selon le procédé : un nœud source d'un premier LSP en cours de test envoie, par l'intermédiaire du premier LSP, un premier paquet vers un nœud de destination, le premier paquet transportant des informations de chemin du premier LSP, et le premier LSP comprenant de multiples LSR agencés séquentiellement ; le nœud de destination établit, après réception du premier paquet et selon les informations de chemin, un second LSP ayant une direction qui est l'inverse de celle du premier LSP et partageant un chemin commun avec le premier LSP ; et en conséquence, le nœud de destination renvoie un premier paquet BFD au nœud source par l'intermédiaire du second LSP ayant la direction inverse au premier LSP et partageant le chemin commun avec le premier LSP, de sorte que le nœud source détermine une condition de défaut du premier LSP sur la base du premier paquet BFD. De cette manière, l'invention permet à un nœud de destination d'établir, sur la base d'informations de chemin, un LSP ayant une direction qui est l'inverse de celle d'un LSP en cours de test et partageant un chemin commun avec le LSP en cours de test, et permet ainsi une transmission de chemin commun d'un paquet BFD vers l'avant et d'un paquet BFD inverse dans un test BFD, ce qui permet d'obtenir une détection de défaut rapide et précise des LSP.
PCT/CN2020/141140 2020-01-15 2020-12-30 Procédé de détection de défaut et appareil associé WO2021143524A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010043122.4A CN113132223A (zh) 2020-01-15 2020-01-15 一种故障检测方法及设备
CN202010043122.4 2020-01-15

Publications (1)

Publication Number Publication Date
WO2021143524A1 true WO2021143524A1 (fr) 2021-07-22

Family

ID=76771610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/141140 WO2021143524A1 (fr) 2020-01-15 2020-12-30 Procédé de détection de défaut et appareil associé

Country Status (2)

Country Link
CN (1) CN113132223A (fr)
WO (1) WO2021143524A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114915538A (zh) * 2021-01-29 2022-08-16 华为技术有限公司 一种故障检测方法、网络设备及系统
WO2023197644A1 (fr) * 2022-04-15 2023-10-19 华为技术有限公司 Procédé de détection de défaut de réseau à segmentation croisée, système de communication et appareil associé

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769543A (zh) * 2012-07-20 2012-11-07 杭州华三通信技术有限公司 一种基于lsp的bfd检测方法和设备
CN108768788A (zh) * 2018-06-26 2018-11-06 新华三技术有限公司合肥分公司 路径故障检测方法及装置
WO2019079961A1 (fr) * 2017-10-24 2019-05-02 华为技术有限公司 Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771577B (zh) * 2008-12-31 2012-10-17 华为技术有限公司 一种为双向lsp建立双向转发检测的方法、系统及设备
CN102571601B (zh) * 2012-02-13 2018-05-15 中兴通讯股份有限公司 一种保证双向转发检测可靠性的方法及标记交换路径设备
CN102624609A (zh) * 2012-02-28 2012-08-01 华为技术有限公司 反向bfd报文发送、通知路径的方法及装置
US8964570B2 (en) * 2013-01-11 2015-02-24 Cisco Technology, Inc. Detecting failures of backup label switched paths in a network environment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769543A (zh) * 2012-07-20 2012-11-07 杭州华三通信技术有限公司 一种基于lsp的bfd检测方法和设备
WO2019079961A1 (fr) * 2017-10-24 2019-05-02 华为技术有限公司 Procédé et dispositif de détermination d'un groupe de liaisons à risque partagé
CN108768788A (zh) * 2018-06-26 2018-11-06 新华三技术有限公司合肥分公司 路径故障检测方法及装置

Also Published As

Publication number Publication date
CN113132223A (zh) 2021-07-16

Similar Documents

Publication Publication Date Title
JP4840236B2 (ja) ネットワークシステム及びノード装置
US9860161B2 (en) System and method for computing a backup ingress of a point-to-multipoint label switched path
US9537712B2 (en) Detecting failures of backup label switched paths in a network environment
US8902780B1 (en) Forwarding detection for point-to-multipoint label switched paths
US7746796B2 (en) Directed echo requests and reverse traceroute
US8976682B2 (en) Connection verification for MPLS label switched paths and pseudowires
US7746793B2 (en) Consistency between MPLS forwarding and control planes
EP2761829B1 (fr) Solution de protection locale au moyen d'un protocole de distribution d'étiquettes en multidiffusion point à point
EP1779568B1 (fr) Arret progressif d'un protocole de distribution d'etiquettes (ldp) sur des interfaces specifiques entre des routeurs a commutation d'etiquettes
US8218432B2 (en) Routing method in a label switching network
WO2008148334A1 (fr) Procédé, système et appareil pour détecter la réception anormale d'un message
WO2021143524A1 (fr) Procédé de détection de défaut et appareil associé
US8971195B2 (en) Querying health of full-meshed forwarding planes
US8254271B1 (en) Point-to-multipoint connectivity verification
US10447586B2 (en) Defect detection in IP/MPLS network tunnels
US20080267080A1 (en) Fault Verification for an Unpaired Unidirectional Switched-Path
JP2006033124A (ja) トンネル障害通知装置および方法
WO2017143958A1 (fr) Système, procédé et appareil de mise en œuvre d'un réacheminement rapide (frr)
CN108702321B (zh) 实现快速重路由(frr)的系统、方法和装置
JP6017037B2 (ja) グレースフルリスタート対応のネイバのためにｒｓｖｐｈｅｌｌｏ抑制を使用するシステムおよび方法
JP6017037B6 (ja) グレースフルリスタート対応のネイバのためにｒｓｖｐ ｈｅｌｌｏ抑制を使用するシステムおよび方法
CN115134283A (zh) 一种环网保护方法及装置
JP5734896B2 (ja) 通信システム、通信装置、パス生成制御方法、及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20913490

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20913490

Country of ref document: EP

Kind code of ref document: A1