WO2009036705A1

WO2009036705A1 - Method for detecting interface failure and network node equipment

Info

Publication number: WO2009036705A1
Application number: PCT/CN2008/072389
Authority: WO
Inventors: Peng Wang; Yuting Wang; Wei Zhang; Zuliang Wang; Lina Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-18
Filing date: 2008-09-17
Publication date: 2009-03-26
Also published as: CN101132320A; CN101132320B

Abstract

A method for detecting interface failure is disclosed. The method includes: building BFD sessions on every member link and carrying out BFD detection, reporting the faulty state of the link to the interface when a fault of the link is detected, determining whether the interface is failure according to the faulty states of the member links received by the interface. A network node device is also disclosed. Then the efficient detection for various kinds of interface is implemented by detecting the member links of the interface directly.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a method for detecting an interface fault and a network node device. Background technique

With the development of communication technologies, especially the demand for real-time and delay-sensitive services such as NGN and 3G on IP networks, how to protect the quality of data transmission, how to quickly locate faults when data transmission problems occur, and Reducing lost packets through corresponding processing has become an important issue that needs to be solved urgently.

In order to solve the above problems, the industry has proposed an OAM (Operation Administration and Maintenance) technology. OAM technology can automatically detect various faults in the network, and then take corresponding remedial measures to avoid the expansion of faults, eliminate faults, and reduce or eliminate the negative effects of faults. The current OAM technologies mainly include: Multi-Protocol Label Switching (OAM) technology proposed by the International Telecommunication Union (ITU), and Bidirectional Forwarding Detection (BFD) technology.

BFD is gradually developed from the basic transmission technology. It can detect faults at various layers in the network. It can be used to detect multiple types of Ethernet, MPLS path, common route encapsulation, and IPSec (IP network security protocol) tunnels. The correctness of the transmission. The goal of BFD is to provide a low-cost, short-detection failure detection mechanism between adjacent systems, including interfaces, data links, and the detection of the forwarding engine itself.

BFD is similar to the "Hello" protocol. When a BFD session between two systems to be detected is established, the two parties periodically send BFD packets to the peer, and periodically detect the arrival of the other party's packets on the link. If the BFD packet from the peer is not received within a certain interval, the link is considered faulty, so as to quickly discover the link fault.

As shown in Figure 1, the overall application environment of BFD is networked. Router A and Router C have a link AC (routers A and C can be directly adjacent or connected through transmission equipment or other systems). There is a link BC between Router B and Router C, on the link AC and link BC. Apply BFD for link detection. The life cycle of a BFD session mainly includes the following phases:

1. Establish a BFD session:

As shown in Figure 1, BFD is applied to the AC between the routers A and Router C. The BFD session does not automatically discover neighbors (the other end of the BFD session, where Router A and Router C are BFD sessions). The neighboring mechanism needs to be configured statically or depends on other application protocols to obtain the IP address of the neighbor and the BFD session discriminator. After obtaining the information, the BFD starts to send the session negotiation packet periodically until the session is established. Ls.

2. BFD session parameter negotiation:

After a BFD session is established, the BFD session parameters are negotiated to coordinate the speed of sending and receiving BFD packets, the defect confirmation time, and the unified session mode.

3. BFD defect detection:

After the BFD session is established, the neighbors of the BFD session send BFD control packets to the peer at the negotiated interval. This is the same as the function and operation mode of the Hello packets. Is, maybe tens of milliseconds. For the convenience of description, I call this state the fast defect detection phase.

When the router sends a BFD check packet, it also periodically detects the BFD packet sent by the BFD neighbor. If the number of consecutive BFD packets is lost, the link is disconnected ( Down) and the message is sent. Advertise to other applications (such as: routing module, forwarding module, etc.).

The above single page introduces several stages of the life cycle of a BFD session. For detailed techniques, please refer to the IETF: draft-ietf-bfd-base-00 and IETF: draft-ietf-bfd published by the Internet Engineering Task Force (IETF). -mpls-00 and "IETF: draft-ietf-mpls-lsp-ping-05".

In the actual application process, it is generally considered that the state of the application protocol running on the interface depends on the interface state. In order to advertise the upper-layer application protocol on the interface in batches, the BFD session can be configured as the interface association mode. To notify the interface management, the interface management sets all the protocols running on the interface to the IDLE state, so that all protocols running on the interface can quickly detect link faults and achieve fast convergence. The meaning of the convergence is that the upper layer application protocols all run the same, accurate routing information enough to reflect the current network topology structure, and fast convergence is the most desirable feature of the routing protocol. The interface association function of the BFD function enables multiple protocols running on the interface to converge at the same time by using one BFD configured on the interface. This improves the efficiency and saves the efficiency of each BFD detection method. The overhead of the router. However, The interface is a composite concept. The interface may be corresponding to the link. It may also be that multiple logical interfaces share one physical link. It is also possible that one interface consists of multiple physical links. We lower this ratio interface. Hierarchical, the physical link used to form an interface is called the member link of the interface.

In the process of implementing the present invention, the inventor found that, for the BFD interface linkage function, the interface can be multiplexed in a plurality of forms, for example, multiple interfaces multiplex one member link, and one interface includes multiple member links. Be effective. For example, if multiple member interfaces are multiplexed with multiple interfaces, at least one BFD session must be configured for each interface. This is very inefficient. For an interface that contains multiple member links, the current interface association function cannot be effectively supported. Summary of the invention

An object of the embodiments of the present invention is to provide a method for detecting an interface fault and a network node device. By performing BFD detection on the member links of the interface to determine the fault status of the interface, you can perform efficient BFD detection on multiple interfaces.

To this end, an embodiment of the present invention provides a method for detecting an interface fault, which includes:

Establish a BFD session on each member link of the interface and perform BFD detection.

When the member link is faulty, the fault status of the member link is reported to the interface corresponding to the member link.

Determining whether the interface is faulty according to a fault state of the member link.

Correspondingly, an embodiment of the present invention further provides a network node device, including:

The link detection module is configured to establish a BFD session and perform BFD detection on the member links of the interface. The interface management module is configured to determine, according to the fault state of the member link detected by the link detection module, whether the interface corresponding to the member link is malfunction.

According to the method for detecting an interface fault and the technical solution of the network node device, the BFD directly detects the member link status of the interface, and then determines the state of the interface according to the member link status, and implements various forms. The member links of the interface perform efficient BFD detection to detect faults on the interface or link and improve the performance of the network system. BRIEF DESCRIPTION OF THE DRAWINGS The drawings, which are required to be used in the description of the drawings or in the description of the prior art, are described in detail in the drawings. The drawings in the drawings are only some embodiments of the present invention, and those skilled in the art can obtain other drawings according to the drawings without any inventive labor.

Figure 1 is a schematic diagram of the overall application environment of the BFD;

2 is a schematic structural diagram of a network node device according to an embodiment of the present invention;

3 is a schematic structural diagram of a link detecting module according to an embodiment of the present invention;

4 is a schematic structural diagram of an interface management module according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an interface state determining unit illustrated in FIG. 4;

6 is a flowchart of a method for detecting an interface fault according to an embodiment of the present invention;

7 is a schematic diagram of an embodiment in which multiple interfaces share a member link;

Figure 8 is a process flow diagram of the embodiment of Figure 7;

9 is a schematic diagram of an embodiment in which an interface includes multiple member links;

Figure 10 is a process flow diagram of the embodiment of Figure 9. detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

The method for detecting an interface fault and the technical solution of the network node device are provided by the embodiment of the present invention. The BFD directly detects the member link status of the interface, and then determines the state of the interface according to the member link status, so as to implement various forms. Interface member links perform efficient BFD detection.

The technical solutions of the embodiments of the present invention will be specifically described below with reference to the accompanying drawings.

Referring to FIG. 2, a schematic structural diagram of a network node device according to an embodiment of the present invention. According to the figure, the network node device includes:

The link detection module 1 is configured to establish a BFD session, and perform BFD detection on the member links of the interface. The interface management module 2 is configured to determine, according to the fault state of the member link detected by the link detection module 1, the member link. Whether the interface has failed.

As shown in FIG. 3, the link detection module 1 shown in FIG. 2 includes:

The fault detection unit 101 is configured to establish a BFD session for each member link and perform BFD detection. The fault reporting unit 102 reports the fault status of the member link to the interface when the fault detection unit detects that the member link is faulty, specifically:

Sending the fault status of the member link to the physical port corresponding to the member link; the physical port reporting the fault status of the member link to the corresponding interface.

As shown in FIG. 4, the interface management module 2 shown in FIG. 2 includes:

The link state obtaining unit 201 is configured to acquire a fault state of the member link reported by the link detecting module 1;

The interface state determining unit 202 is configured to determine, according to the fault state of the member link acquired by the link state acquiring unit 201, whether an interface corresponding to the member link is faulty.

Preferably, the interface management module 2 may further include an interface status sending unit 203, configured to: when the interface status determining unit 202 determines that the status of the interface is a fault state, send the fault status to an upper application running on the interface. The protocol, the upper layer application protocol converges after receiving the fault state of the interface.

In a specific implementation, as shown in FIG. 5, the interface state determining unit 202 of FIG. 4 includes: a determining unit 2021, configured to determine that the interface includes one of the member links, including at least two member links, and Output the judgment result;

The threshold value determining unit 2022, when the determination result output by the determining unit 2021 is that the interface includes at least two member links, is used to determine whether the number of member links having a fault state exceeds a threshold, and outputs a determination result;

The link state judging unit 2023, when the judgment result output by the judging unit 2021 is that the interface includes a barrier; , ' , , ' , ' ― , ' ' state changing unit 2024, when the judgment result output by the threshold judging unit 2022 is faulty When the number of member links of the state exceeds the threshold, or the result of the determination by the link state determining unit 2023 is that the member link is faulty, the state of the interface is changed to a fault state.

The interface management module further includes:

The interface status sending unit is configured to: when the interface status determining unit determines that the status of the interface is a fault state, send the fault status to an upper layer application protocol running on the interface.

It should be noted that, in an actual network, the network node device is a router or a switching device. The network node device provided by the embodiment of the present invention is described in detail above. A method for detecting an interface failure according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. Referring to FIG. 6, which is a flowchart of a method for detecting an interface failure according to an embodiment of the present invention. The method for detecting an interface failure includes:

Step S1: Establish a BFD session on each member link of the interface, and perform BFD detection. The interface is a composite concept. The interface may correspond to a link, or multiple interfaces may share a physical link. It is also possible that an interface includes a plurality of physical links, and the physical link is referred to as a member link of the interface;

In step S2, when the member link is faulty, the fault status of the member link is reported to the interface corresponding to the member link.

Step S3: Determine whether the interface is faulty according to a fault state of the member link. The steps of the interface are specifically as follows:

A. Send the fault status of the member link to the physical port corresponding to the member link.

B. The physical port reports the fault status of the member link to the corresponding interface.

It is to be noted that, after determining that the state of the interface is a fault state, the method further includes:

Sending the fault status of the interface to an upper layer application protocol running on the interface;

The upper layer application protocol converges after receiving the fault state of the interface.

In the embodiment of the present invention, the BFD is used to directly detect the member link status of the interface, and then determine the state of the interface according to the member link status, thereby implementing efficient BFD detection on various interfaces and member links, and discovering interfaces or links in time. Faults, improve network system performance, and improve QoS (Quality of Service)

The technical solution of the method for detecting interface faults provided by the embodiments of the present invention is described in the foregoing. The specific technical solutions are described in detail below with reference to FIG. 7, FIG. 8, FIG. 9, and FIG.

Referring to FIG. 7, a schematic diagram of an embodiment in which multiple interfaces share a member link, a typical scenario is to carry multiple logical sub-interfaces on a physical port of a member link. As shown in the figure, Router A and Router B are connected by a physical link. The physical ports of the physical link carry four interfaces, namely: logical interface 1, logical interface 2, logical interface 3, and logic. Interface 4, that is, the four logical interfaces share a physical link as their common member link.

In the existing mechanism, a BFD session needs to be established for each logical interface, in this embodiment. In the scenario, four BFD sessions are required to allow the application protocol on the four logical interfaces to converge quickly. However, the method for detecting an interface fault in the embodiment of the present invention is to establish a BFD session on the member link, so that the application protocol on each interface can be quickly converge. The processing procedure is as shown in FIG. 8 and includes:

Step S71: Establish a BFD session on the member links shared by the four logical interfaces to perform BFD detection.

Step S72: When detecting that the member link is faulty, report the fault status to the physical port.

Step S73, the physical port quickly reports the fault status of the member link to each logical interface.

Step S74, the four logical interfaces determine, according to the fault state of the shared member link, that the respective states are fault states (Down state);

In step S75, the four logical interfaces respectively send respective fault states to various upper layer application protocols running on the respective ones, thereby triggering fast convergence of the application protocols.

For the application scenario shown in Figure 7, when there are N (the integers greater than 0) logical interfaces sharing a link, the N-type BFD session needs to be established and N BFD detection packets are transmitted. When N tends to infinity (or when there are hundreds of interfaces multiplexed with one member link), there will be a large number of BFD detection packets in the network, resulting in inefficient transmission of user service data packets, and even loss of service data. With the embodiment of the present invention, no matter how many logical interfaces are provided, only one BFD detection needs to be configured on the member links, and a small amount of BFD detection packets can be detected on the network to detect whether each interface is faulty, thereby improving detection efficiency. It also avoids network congestion caused by the transmission of a large number of detection packets, saves network resources, and improves system performance and QoS.

Referring to Figure 9, a schematic diagram of an embodiment of an interface including multiple member links. As shown in the figure, a trunk interface is bundled with five member links. The trunk interface is a trunk interface or a trunk interface. The physical ports are bundled together and used as a logical interface. Trunk technology is implemented. The internal member links are mutually backup. When a member link fails, the other links are not affected. However, when there are too many member links, the trunk interface and system performance are affected. The method for detecting the fault of the interface provided by the embodiment of the present invention is used to detect the processing flow of the trunk interface in time as shown in FIG. 10, which includes:

Step S81: A BFD session is established on each member link, that is, five BFD sessions are to be established. Then, performing BFD detection on each member link;

Step S82: When detecting a member link failure, reporting the fault status to the physical port corresponding to the member link;

In step S83, the physical port reports the fault status of the member links to the trunk interface. Step S84: After receiving the status information of all member links, the trunk interface determines whether the number of member links with the fault status exceeds a preset threshold (such as: 3), if yes, proceed to step S86, otherwise, perform step S85;

Step S85, continue to perform BFD detection, and then proceeds to step S82;

Step S86, determining that the state is a fault state;

Step S87: Send the fault status of the trunk interface to all upper layer application protocols running on the trunk interface.

Step S88: The upper layer application protocol performs fast convergence after receiving the fault state of the trunk interface. In the embodiment of the present invention, for an interface that includes multiple member links, the current interface linkage mode cannot effectively detect the fault of the interface, and the BFD session is established on the member link by the present invention to perform BFD detection and pass the member chain. In the case of a road failure (the number of member links that have failed), it is determined whether the interface is faulty, and the interface fault is discovered in time to improve system reliability.

It should be noted that those skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments may be completed by a program indicating related hardware, and the program may be stored in a computer readable storage medium. The storage medium includes: a ROM/RAM, a magnetic disk, an optical disk, a flash memory, and the like.

According to the method for detecting an interface fault and the technical solution of the network node device, the BFD directly detects the member link status of the interface, and then determines the state of the interface according to the member link status, and implements various forms. An interface (such as an interface that includes multiple member links or multiple interfaces to share a member link) performs efficient BFD detection to detect faults on interfaces or links and improve network system performance.

A person skilled in the art can understand that all or part of the processes in implementing the embodiments of the present invention can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. The program, when executed, may include the flow of an embodiment of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM). The above is a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. These improvements and retouchings are also considered. It is the scope of protection of the present invention.

Claims

Rights request

A method for detecting an interface fault, which is characterized by comprising:

Performing BFD detection (SI, S71, S81) on each member link of the interface, the interface includes at least one member link, and each member link corresponds to one BFD session.

When the member link is faulty, the fault status of the member link is reported (S2) to the interface corresponding to the member link;

Determining (S3, S74, S86) whether the interface is faulty according to the fault state received by the interface.

2. The method according to claim 1, wherein the step of reporting the fault status of the member link (S2) to the interface corresponding to the member link is specifically:

Sending a fault status of the member link (S72, S82) to a physical port corresponding to the member link;

The physical port reports the fault status of the member link (S73, S83) to the interface corresponding to the member link.

The method according to claim 2, wherein when the interface includes at least two member links, the fault state determination (S3, S74, S86) received according to the interface is The steps for whether the interface is faulty are as follows:

Judging (S84) whether the number of member links having a fault state exceeds a threshold,

When the number of member links having a fault state exceeds the threshold, it is determined (S86) that the interface has failed.

4. A network node device, comprising:

The link detection module (1) is configured to perform BFD detection on each member link of the interface, where the interface includes at least one member link, and each member link corresponds to a BFD session and an interface;

An interface management module (2), configured to detect the link detection module (1) received according to the interface The fault status of the member link to determine whether the interface is faulty,

The network node device according to claim 4, wherein the link detection module (1) comprises:

The fault detection unit (101) is configured to establish a BFD session for each member link and perform BFD detection.

a fault reporting unit (102), when the fault detecting unit (101) detects a member link failure,

J夂 S k 々 ΛΛ +Λ- 1:咅,] Too μ 1⁄2 έ^ ^ ϊ* m ^ S夂 ; ί 1⁄2 interface

The network node device according to claim 4, wherein the interface management unit (2) comprises:

a link state obtaining unit (201), configured to acquire, from the interface, a fault state of a member link reported by the link detecting module (1);

The interface state determining unit (202) is configured to determine whether the interface is faulty according to the fault state of the member link acquired by the link state acquiring unit (201).

The network node device according to claim 6, wherein the interface state determining unit (202) comprises:

The determining unit (2021) is configured to determine whether the interface includes one of the member links, or includes at least two member links, and output a judgment result;

a threshold value determining unit (2022), configured to determine, when the judgment result output by the determining unit (2021) is that the interface includes at least two member links, determine whether the number of member links having a fault state exceeds a threshold, and Output the judgment result;

a state changing unit (2024), configured to: when the determination result output by the threshold determining unit (2022) is that the number of member links having a fault state exceeds the threshold, or the judgment result output by the determining unit (2021) is When the interface includes a member link, the state of the interface is changed to a fault state.

The network node device according to claim 6 or 7, wherein the interface management module further comprises: The interface status sending unit (203) is configured to: when the interface status determining unit (202) determines that the status of the interface is a fault state, send the fault status to an upper layer application protocol running on the interface.

9. The network node device of claim 8, wherein the network node device is a router or a switching device.