WO2016082343A1 - 故障检测方法及装置 - Google Patents

故障检测方法及装置 Download PDF

Info

Publication number
WO2016082343A1
WO2016082343A1 PCT/CN2015/072699 CN2015072699W WO2016082343A1 WO 2016082343 A1 WO2016082343 A1 WO 2016082343A1 CN 2015072699 W CN2015072699 W CN 2015072699W WO 2016082343 A1 WO2016082343 A1 WO 2016082343A1
Authority
WO
WIPO (PCT)
Prior art keywords
bfd session
established
association
communication devices
layer application
Prior art date
Application number
PCT/CN2015/072699
Other languages
English (en)
French (fr)
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 WO2016082343A1 publication Critical patent/WO2016082343A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention relates to the field of communications, and in particular, to a fault detection method and apparatus.
  • BFD Bidirectional Forwarding Detection
  • IETF Internet Engineering Task Force
  • the BFD detection mechanism is a fast fault detection mechanism independent of media and protocols. Compared with other detection mechanisms, BFD can provide a fast fault detection mechanism for the upper layer protocol, which enables fast detection of link faults between two network devices and fast traffic switching to ensure uninterrupted service.
  • the two network devices use the BFD control packet to perform the three-way handshake negotiation.
  • the status of the device is changed from Down to Up in the Down state.
  • the BFD state is changed to Up, the device periodically sends detection packets on the link. If no packet is received from the peer in a long period of time, the link is considered to be faulty. If the backup link exists, the traffic is quickly switched to the standby link to ensure that service traffic is not interrupted.
  • FIG. 1 the first network device A and the second network device B are included, and the first network device and the second network device may be directly connected or may be directly connected.
  • Figure 2 shows the process of normal handshake and detection of BFD, including:
  • Step 201 The first network device A and the second network device B initiate the establishment of a BFD session by the upper-layer application, and the BFD performs a three-way handshake through the control packet according to the standard protocol, and the state is switched.
  • Step 202 After the state of the network device at both ends is switched to the Up state, the BFD notifies the link of the upper-layer protocol that the link state is normal, and periodically sends a detection packet to detect the link.
  • Step 203 When the detection packet is not received within a certain period of time, the link is considered to be faulty, the forwarding traffic is quickly switched, and the upper application link is notified to be faulty, and the upper layer application performs corresponding processing.
  • the current BFD has the following disadvantages:
  • the BFD session fails to be forwarded through the BFD session, the BFD session cannot be forwarded.
  • the link status is detected.
  • the upper-layer application does not have its own keep-alive, the link fault cannot be perceived, and the upper-layer application cannot perform corresponding processing.
  • the main technical problem to be solved by the embodiments of the present invention is to provide a method and device for detecting faults, which at least solves the problem that the link detection of the existing BFD is dependent on the BFD session.
  • an embodiment of the present invention provides a fault detection method, including:
  • An association is established on at least one of the two communication devices that are to establish a BFD session, where the association is to associate a BFD session to be established on the communication device with an upper-layer application on the communication device;
  • the negotiation failure notification is sent to the upper-layer application associated with the BFD session on the communication device on which the association is established.
  • the association is established on both communication devices to be established with a BFD session.
  • determining whether the two communication devices fail to negotiate during the establishment of the BFD session includes:
  • the upper layer application is an upper layer application that does not have a keep alive mechanism.
  • the upper layer application includes at least one of an upper layer static routing protocol, a static PW, and a static tunnel.
  • an embodiment of the present invention further provides a fault detection apparatus, including a configuration module and a detection module;
  • the configuration module is configured to establish an association between the BFD session to be established on the communication device and the upper layer application on the communication device, where the association is established on the communication device.
  • the detecting module is configured to send a negotiation failure notification to the upper layer application associated with the BFD session on the communication device on which the association is established, when the negotiation fails in the process of establishing the BFD session by the two communication devices. .
  • the configuration module includes a first configuration submodule and a second configuration submodule, and the first configuration submodule is configured as one of two communication devices in a BFD session to be established.
  • the association is established; the second configuration submodule is configured to establish the association on another communication device of the two communication devices to be established with the BFD session.
  • the detecting module includes a determining sub-module, configured to determine whether the BFD session between the two communication devices is successfully negotiated within a preset determination time, and if not, determine the two communications. BFD session negotiation between devices failed.
  • the upper layer application is an upper layer application that does not have a keep alive mechanism.
  • the upper layer application includes at least one of an upper layer static routing protocol, a static PW, and a static tunnel.
  • the fault detection method and device provided by the embodiment of the present invention first establish an association on at least one of the two communication devices to be established in the BFD session, where the association is a BFD session to be established on the communication device and the communication device.
  • the negotiation fails in the process of establishing a BFD session between the two communication devices, the negotiation failure notification is sent to the upper-layer application associated with the BFD session on the communication device on which the association is established.
  • the fault detection in the present invention does not depend on the BFD session to be negotiated normally. Even if the BFD session fails to be negotiated normally, the fault detection can be performed, thereby implementing the keepalive of the upper layer application at another level, especially for those There is no upper-level application of the keep-alive mechanism.
  • 1 is a schematic diagram of connection of a conventional communication system
  • FIG. 2 is a schematic diagram of an existing BFD detection process
  • FIG. 3 is a schematic flowchart of a fault detection method according to Embodiment 1 of the present invention.
  • FIG. 4 is a schematic flowchart of another fault detection method according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic structural diagram 1 of a fault detecting apparatus according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic structural diagram 2 of a fault detecting apparatus according to Embodiment 2 of the present invention.
  • FIG. 7 is a schematic structural diagram 3 of a fault detecting apparatus according to Embodiment 2 of the present invention.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the fault detection method provided in this embodiment includes the following steps:
  • Step 301 Establish an association on at least one of the two communication devices that are to be established with the BFD session, where the association is to associate the BFD session to be established on the communication device with the upper-layer application on the communication device.
  • Step 302 When the negotiation fails in the process of establishing a BFD session between the two communication devices, the negotiation failure notification is sent to the upper layer application associated with the BFD session on the communication device on which the association is established.
  • the upper-layer application can know that the link between the two communication devices is faulty and performs corresponding processing, for example, the signal may be unstable, the forwarding of the intermediate device on the link may be problematic, or the link physics may occur. Connection failure and so on.
  • the association may be set on the two communication devices to be established in the BFD session according to the actual application scenario, or the association may be set on one of the communication devices.
  • the present embodiment preferably establishes the association on both communication devices to be established with the BFD session. It can be seen that the fault detection of the upper layer application in the embodiment does not depend on the BFD session to be negotiated normally. Even if the BFD session fails to be negotiated normally, the fault detection can be performed, thereby implementing the keepalive of the upper layer application at another level, especially It is for upper-level applications that do not have a keep-alive mechanism.
  • the association between the BFD session to be established on the communication device and the upper-layer application on the communication device in this embodiment specifically refers to establishing a communication link (interface) between the BFD session and the upper-layer application on the communication device on the communication device, or communicating
  • the BFD session on the device is bound to the upper-layer application on the communication device.
  • the function of sending the negotiation failure notification to the associated upper-layer application is enabled.
  • the upper layer application of the communication device in this embodiment may be an upper layer application with its own keep-alive mechanism, or an upper layer application (generally a static protocol) that does not have its own keep-alive mechanism; for an upper-layer application with its own keep-alive mechanism, It can perform fault detection by its own protection mechanism, or can perform fault detection by the process shown in FIG. 3 above in this embodiment.
  • the fault detection can be directly performed by using the process shown in FIG. 3 above in this embodiment.
  • the upper layer application that does not have its own keep-alive mechanism in this embodiment includes at least one of an upper static routing protocol, a static PW, a static tunnel, and the like.
  • step 302 it is determined whether the negotiation failure of the two communication devices during the establishment of the BFD session includes:
  • the preset determination time in this embodiment may be set according to a specific application, for example, may be set to 300 seconds. It should be understood that when the configuration is performed on both communication devices, the preset determination times set on the two communication devices may be the same or different, preferably set to be the same.
  • the upper-layer application in this example is an upper-layer static routing protocol and is configured on both communication devices. As shown in Figure 4, it has the following:
  • Step 401 Configure a BFD session correctly on the two communication devices.
  • Step 402 Associate respective BFD sessions with respective upper static routing protocols on the two communication devices respectively.
  • Step 403 The BFD negotiation fails to be reported to the upper layer static routing protocol on the two communication devices.
  • Step 404 Set a preset determination time on each of the two communication devices, which is set to 300 seconds in this example;
  • Step 405 Determine whether the BFD session negotiation between the two communication devices is successful in the set 300 seconds, if yes, go to step 406; otherwise, go to step 407;
  • Step 406 After the BFD session is completed through the three-way handshake, the BFD session is normal, and the negotiation is complete. The status of the negotiation is changed to UP. The detection is sent periodically. If the link is faulty, the link is not received within a certain period of time. The detection of the packet determines that the link is faulty and is reported to the associated upper-layer static routing protocol.
  • Step 407 The BFD fails to negotiate the three-way handshake within the preset time, and the negotiation failure notification is sent to the upper-layer static routing protocol.
  • the static routing protocol considers that the link is faulty according to the received notification of the session negotiation failure.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the embodiment provides a fault detecting apparatus 1 including a configuration module 11 and a detecting module 12;
  • the configuration module 11 is configured to establish an association on at least one of the two communication devices to be established with the BFD session, the association is to associate the BFD session to be established on the communication device with the upper application on the communication device;
  • the detecting module 12 is configured to send a negotiation failure notification to the upper-layer application associated with the BFD session on the associated communication device when the negotiation fails in the process of establishing the BFD session.
  • Upper application After the negotiation failure notification, it can be known that the link between the two communication devices is faulty and corresponding processing is performed, for example, the signal may be unstable, the forwarding of the intermediate device on the link may be faulty, or the link may be physically connected. Wait.
  • the configuration module 11 may specifically set the association on the two communication devices to be established in the BFD session according to the actual application scenario, or set the association on one of the communication devices. In order to ensure the success rate of the fault detection as much as possible, the present embodiment preferably establishes the association on both communication devices to be established with the BFD session.
  • the configuration module 11 includes a first configuration sub-module 111 and a second configuration sub-module 112.
  • the first configuration sub-module 111 is configured to establish an association on one of two communication devices to be established with a BFD session.
  • the second configuration sub-module 112 is arranged to establish an association on another of the two communication devices to be established with the BFD session.
  • the fault detection of the upper layer application in the embodiment does not depend on the BFD session to be negotiated normally. Even if the BFD session fails to be negotiated normally, the fault detection can be performed, thereby implementing the keepalive of the upper layer application at another level, especially It is for upper-level applications that do not have a keep-alive mechanism.
  • the association between the BFD session to be established on the communication device and the upper-layer application on the communication device in this embodiment specifically refers to establishing a communication link (interface) between the BFD session and the upper-layer application on the communication device on the communication device, or communicating
  • the BFD session on the device is bound to the upper-layer application on the communication device.
  • the function of sending the negotiation failure notification to the associated upper-layer application is enabled.
  • the upper layer application of the communication device in this embodiment may be an upper layer application with its own keep-alive mechanism, or an upper layer application (generally a static protocol) that does not have its own keep-alive mechanism; for an upper-layer application with its own keep-alive mechanism, It can detect faults through its own protection mechanism, and can also perform fault detection through the scheme of this embodiment.
  • the solution provided in this embodiment can be directly used for fault detection.
  • the upper layer application that does not have its own keep-alive mechanism in this embodiment includes at least one of an upper static routing protocol, a static PW, a static tunnel, and the like.
  • the detecting module 12 in this embodiment includes a determining sub-module 121, configured to determine whether the BFD session between the two communication devices is successfully negotiated within a preset determination time, and if not, determine the two communication devices.
  • the preset determination time in this embodiment may be set according to a specific application, for example, may be set to 300 seconds. It should be understood that when the configuration is performed on both communication devices, the preset determination times set on the two communication devices may be the same or different, preferably set to be the same.
  • the BFD can quickly detect the link fault in the standard protocol, and the link failure is notified by the upper layer application reporting failure failure notification, thereby solving the link failure.
  • the keepalive message protocol such as static routing protocols.
  • a fault detection method and apparatus provided by an embodiment of the present invention have the following beneficial effects: first establishing an association on at least one of two communication devices to be established with a BFD session, the association being the communication device
  • the BFD session to be established is associated with the upper layer application on the communication device; when the negotiation fails in the process of establishing a BFD session between the two communication devices, the negotiation failure notification is sent to the communication device on which the association is established and associated with the BFD session.
  • Upper level application It can be seen that the fault detection in the present invention does not depend on the BFD session to be negotiated normally. Even if the BFD session fails to be negotiated normally, the fault detection can be performed, thereby implementing the keepalive of the upper layer application at another level, especially for those There is no upper-level application of the keep-alive mechanism.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Maintenance And Management Of Digital Transmission (AREA)

Abstract

一种故障检测方法及装置，先在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，该关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联(S301)；在两通信设备建立BFD会话的过程中协商失败时，则将协商失败通知发给建立有上述关联的通信设备上与BFD会话关联的上层应用(S302)。可见进行故障检测时并不依赖于BFD会话能够正常协商完成，即使BFD会话没能正常协商完成也能进行故障检测，从而在另一层面实现对上层应用的保活，尤其是对于那些自身不具备保活机制的上层应用。

Description

故障检测方法及装置 技术领域
本发明涉及通信领域，具体涉及一种故障检测方法及装置。
背景技术
BFD(Bidirectional Forwarding Detection，双向转发检测)是互联网工程(Internet Engineering Task Force，简称IETF)发布的用于实现快速检测的国际标准协议，BFD检测机制是一种与介质、协议无关的快速故障检测机制，与其他检测机制相比，BFD可以为上层协议提供快速的故障检测机制，实现两台网络设备之间链路故障的快速检测，流量快速切换，保证业务不中断。
两台网络设备间通过BFD控制报文进行三次握手协商，使其状态由Down经由Init切换到Up，BFD状态切换为Up后在链路上周期性的发送检测报文，如果一端网络设备在足够长的时间内没有收到对端的检测报文，则认为链路的某个部分出现了故障，如果存在备链路，流量快速切换到备链路，保证业务流量不中断。
请参见图1所示的通信系统，包括第一网络设备A和第二网络设备B，第一网络设备和第二网络设备可以直连，也可以非直连。图2是BFD正常握手和检测的过程，主要包括：
步骤201：第一网络设备A和第二网络设备B由上层应用发起BFD会话的建立，BFD根据标准协议通过控制报文进行三次握手，状态进行切换。
步骤202：当两端网络设备会话状态都切换为Up后，BFD通知上层协议链路状态正常，同时周期性的发送检测报文进行链路检测；
步骤203：当一定时间内没有收到检测报文时，认为链路故障，转发流量进行快速切换，同时通知上层应用链路出现故障，上层应用进行相应的处理。
根据图2所示的过程可以看出，当前BFD存在以下的缺点：
BFD进行链路故障的检测依赖于BFD会话能够正常协商完成；当创建BFD会话过程中链路存在问题时，即BFD会话无法通过三次握手状态切换为Up时，BF无法 检测链路状态，此时当上层应用不存在自身保活时，就无法感知链路故障，导致上层应用无法进行相应的处理。
发明内容
本发明实施例要解决的主要技术问题是，提供了一种故障检测方法及装置，至少解决现有BFD进行链路检测依赖于BFD会话能够正常协商完成的问题。
为解决上述技术问题，本发明实施例提供一种故障检测方法,包括：
在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，所述关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；
在所述两通信设备建立所述BFD会话的过程中协商失败时，将协商失败通知发给建立有所述关联的通信设备上与所述BFD会话关联的上层应用。
在本发明的一种实施例中，在待建立BFD会话的两通信设备上都建立所述关联。
在本发明的一种实施例中，判断所述两通信设备建立所述BFD会话的过程中是否协商失败包括：
判断所述两通信设备之间的BFD会话在预设判定时间内是否协商成功，如否，判定所述两通信设备之间的BFD会话协商失败。
在本发明的一种实施例中，所述上层应用为自身不具备保活机制的上层应用。
在本发明的一种实施例中，所述上层应用包括上层静态路由协议，静态PW、静态隧道中的至少一种。
为了解决上述问题，本发明实施例还提供了一种故障检测装置，包括配置模块以及检测模块；
所述配置模块设置为在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，所述关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；
所述检测模块设置为在检测到所述两通信设备建立所述BFD会话的过程中协商失败时，将协商失败通知发给建立有所述关联的通信设备上与所述BFD会话关联的上层应用。
在本发明的一种实施例中，所述配置模块包括第一配置子模块和第二配置子模块，所述第一配置子模块设置为在待建立BFD会话的两通信设备中的一个通信设备上建立所述关联；所述第二配置子模块设置为在待建立BFD会话的两通信设备中的另一个通信设备上建立所述关联。
在本发明的一种实施例中，所述检测模块包括判断子模块，设置为判断所述两通信设备之间的BFD会话在预设判定时间内是否协商成功，如否，判定所述两通信设备之间的BFD会话协商失败。
在本发明的一种实施例中，所述上层应用为自身不具备保活机制的上层应用。
在本发明的一种实施例中，所述上层应用包括上层静态路由协议，静态PW、静态隧道中的至少一种。
本发明实施例的有益效果是：
本发明实施例提供的故障检测方法及装置，先在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，该关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；在两通信设备建立BFD会话的过程中协商失败时，则将协商失败通知发给建立有上述关联的通信设备上与BFD会话关联的上层应用。可见本发明中进行故障检测时并不依赖于BFD会话能够正常协商完成，即使BFD会话没能正常协商完成也能进行故障检测，从而在另一层面实现对上层应用的保活，尤其是对于那些自身不具备保活机制的上层应用。
附图说明
图1为现有通信系统连接示意图；
图2为现有BFD检测流程示意图；
图3为本发明实施例一提供的故障检测方法流程示意图；
图4为本发明实施例一提供的另一故障检测方法流程示意图；
图5为本发明实施例二提供的故障检测装置结构示意图一；
图6为本发明实施例二提供的故障检测装置结构示意图二；
图7为本发明实施例二提供的故障检测装置结构示意图三。
具体实施方式
下面通过具体实施方式结合附图对本发明作进一步详细说明。
实施例一：
请参见图3所示，本实施例提供的故障检测方法包括以下步骤：
步骤301：在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，该关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；
步骤302：在两通信设备建立BFD会话的过程中协商失败时，将协商失败通知发给建立有上述关联的通信设备上与BFD会话关联的上层应用。
上层应用收到协商失败通知后，即可得知两通信设备之间的链路出现了故障并进行对应的处理，例如可能是信号不稳定、链路上中间设备的转发出现问题或链路物理连接故障等等。
应当理解的是，上述步骤301中，具体可以根据实际应用场景选择在待建立BFD会话的两个通信设备上都设置上述关联，或者在其中一个通信设备上设置上述关联。为了尽可能保证故障检测的成功率，本实施例优选在待建立BFD会话的两通信设备上都建立上述关联。可见本实施例中上层应用进行故障检测时并不依赖于BFD会话能够正常协商完成，即使BFD会话没能正常协商完成也能进行故障检测，从而在另一层面实现对上层应用的保活，尤其是对于那些自身不具备保活机制的上层应用。
本实施例中该通信设备上待建立的BFD会话与该通信设备上的上层应用关联具体指在通信设备上建立BFD会话与该通信设备上的上层应用的通信链路(接口)，或将通信设备上BFD会话与该通信设备上的上层应用进行绑定；并使能向关联的上层应用发送协商失败通知的功能。
本实施例中通信设备的上层应用既可以是具有自身保活机制的上层应用，也可以是不具备自身保活机制的上层应用(一般是静态协议)；对于具备自身保活机制的上层应用，其既可通过其自身的保护机制进行故障检测，也可以通过本实施例上述图3所示的过程进行故障检测。对于不具备自身保活机制的上层应用，则可直接利用本实施例上述图3所示的过程进行故障检测。本实施例中不具备自身保活机制的上层应用包括上层静态路由协议，静态PW、静态隧道等中的至少一种。
上述步骤302中，判断两通信设备建立BFD会话的过程中是否协商失败包括：
判断两通信设备之间的BFD会话在预设判定时间内是否协商成功，如否，判定两通信设备之间的BFD会话协商失败。本实施例中的预设判断时间可以根据具体应用选择设定，例如可以设置为300秒。应当理解的是，当在两个通信设备上都进行配置时，两通信设备上设置的预设判定时间可以相同，也可以不同，优选设置为相同。
为了更好的理解本发明，下面以一个具体的示例进行说明。本示例中的上层应用为上层静态路由协议，且在两通信设备上都进行配置，请参见图4所示，其具备包括：
步骤401：分别在两通信设备上正确配置BFD会话；
步骤402：分别在两通信设备上将各自的BFD会话与各自的上层静态路由协议关联；
步骤403：分别在两通信设备上使能BFD协商失败上报上层静态路由协议；
步骤404：分别在两通信设备上设置预设判定时间，该示例中都设置为300秒；
步骤405：判断两通信设备之间的BFD会话协商在设定的300秒内是否协商成功，如是，转至步骤406；否则，转至步骤407；
步骤406：在预设时间内BFD通过三次握手完成协商，表明链路正常，协商完成状态切换为UP，并通过周期性发送检测报文进行检测，如果链路出现故障，一定时间内收到不到检测报文则判定链路故障，上报给关联的上层静态路由协议。
步骤407：在预设时间内BFD通过三次握手协商失败，将协商失败通知发给上层静态路由协议，静态路由协议根据收到的会话协商失败的通知认为链路存在故障进行相应的处理。
实施例二：
请参见图5所示，本实施例提供了一种故障检测装置1，包括配置模块11以及检测模块12；
配置模块11设置为在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，该关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；
检测模块12设置为在检测到两通信设备建立BFD会话的过程中协商失败时，将协商失败通知发给建立有关联的通信设备上与BFD会话关联的上层应用。上层应用收 到协商失败通知后，即可得知两通信设备之间的链路出现了故障并进行对应的处理，例如可能是信号不稳定、链路上中间设备的转发出现问题或链路物理连接故障等等。
应当理解的是，配置模块11具体可以根据实际应用场景选择在待建立BFD会话的两个通信设备上都设置上述关联，或者在其中一个通信设备上设置上述关联。为了尽可能保证故障检测的成功率，本实施例优选在待建立BFD会话的两通信设备上都建立上述关联。请参见图6所示，配置模块11包括第一配置子模块111和第二配置子模块112，第一配置子模块111设置为在待建立BFD会话的两通信设备中的一个通信设备上建立关联；第二配置子模块112设置为在待建立BFD会话的两通信设备中的另一个通信设备上建立关联。
可见本实施例中上层应用进行故障检测时并不依赖于BFD会话能够正常协商完成，即使BFD会话没能正常协商完成也能进行故障检测，从而在另一层面实现对上层应用的保活，尤其是对于那些自身不具备保活机制的上层应用。
本实施例中该通信设备上待建立的BFD会话与该通信设备上的上层应用关联具体指在通信设备上建立BFD会话与该通信设备上的上层应用的通信链路(接口)，或将通信设备上BFD会话与该通信设备上的上层应用进行绑定；并使能向关联的上层应用发送协商失败通知的功能。
本实施例中通信设备的上层应用既可以是具有自身保活机制的上层应用，也可以是不具备自身保活机制的上层应用(一般是静态协议)；对于具备自身保活机制的上层应用，其既可通过其自身的保护机制进行故障检测，也可以通过本实施例的方案进行故障检测。对于不具备自身保活机制的上层应用，则可直接利用本实施例提供的方案进行故障检测。本实施例中不具备自身保活机制的上层应用包括上层静态路由协议，静态PW、静态隧道等中的至少一种。
请参见图7所示，本实施例中的检测模块12包括判断子模块121，设置为判断两通信设备之间的BFD会话在预设判定时间内是否协商成功，如否，判定两通信设备之间的BFD会话协商失败。本实施例中的预设判断时间可以根据具体应用选择设定，例如可以设置为300秒。应当理解的是，当在两个通信设备上都进行配置时，两通信设备上设置的预设判定时间可以相同，也可以不同，优选设置为相同。
可见，本发明实施例与标准协议中BFD快速检测链路故障相比，实现了在链路故障导致BFD无法完成协商的情况下，通过向上层应用上报协商失败通知发现链路故障，从而解决了静态路由协议等没有保活报文协议的收敛问题。
以上内容是结合具体的实施方式对本发明所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。
工业实用性
如上所述，本发明实施例提供的一种故障检测方法及装置，具有以下有益效果：先在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，该关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；在两通信设备建立BFD会话的过程中协商失败时，则将协商失败通知发给建立有上述关联的通信设备上与BFD会话关联的上层应用。可见本发明中进行故障检测时并不依赖于BFD会话能够正常协商完成，即使BFD会话没能正常协商完成也能进行故障检测，从而在另一层面实现对上层应用的保活，尤其是对于那些自身不具备保活机制的上层应用。

Claims (10)

  1. 一种故障检测方法，包括：
    在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，所述关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；
    在所述两通信设备建立所述BFD会话的过程中协商失败时，将协商失败通知发给建立有所述关联的通信设备上与所述BFD会话关联的上层应用。
  2. 如权利要求1所述的故障检测方法，其中，在待建立BFD会话的两通信设备上都建立所述关联。
  3. 如权利要求1所述的故障检测方法，其中，判断所述两通信设备建立所述BFD会话的过程中是否协商失败包括：
    判断所述两通信设备之间的BFD会话在预设判定时间内是否协商成功，如否，判定所述两通信设备之间的BFD会话协商失败。
  4. 如权利要求1-3任一项所述的故障检测方法，其中，所述上层应用为自身不具备保活机制的上层应用。
  5. 如权利要求4所述的故障检测方法，其中，所述上层应用包括上层静态路由协议，静态PW、静态隧道中的至少一种。
  6. 一种故障检测装置，包括配置模块以及检测模块；
    所述配置模块设置为在待建立BFD会话的两通信设备中的至少一个通信设备上建立关联，所述关联为将该通信设备上待建立的BFD会话与该通信设备上的上层应用关联；
    所述检测模块设置为在检测到所述两通信设备建立所述BFD会话的过程中协商失败时，将协商失败通知发给建立有所述关联的通信设备上与所述BFD会话关联的上层应用。
  7. 如权利要求6所述的故障检测装置，其中，所述配置模块包括第一配置子模块和第二配置子模块，所述第一配置子模块设置为在待建立BFD会话的两通信设备中的一个通信设备上建立所述关联；所述第二配置子模块设置为在待建立BFD会话的两通信设备中的另一个通信设备上建立所述关联。
  8. 如权利要求6所述的故障检测装置，其中，所述检测模块包括判断子模块，设置为判断所述两通信设备之间的BFD会话在预设判定时间内是否协商成功，如否，判定所述两通信设备之间的BFD会话协商失败。
  9. 如权利要求6-8任一项所述的故障检测装置，其中，所述上层应用为自身不具备保活机制的上层应用。
  10. 如权利要求9所述的故障检测装置，其中，所述上层应用包括上层静态路由协议，静态PW、静态隧道中的至少一种。
PCT/CN2015/072699 2014-11-24 2015-02-10 故障检测方法及装置 WO2016082343A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410680534.3 2014-11-24
CN201410680534.3A CN105610598A (zh) 2014-11-24 2014-11-24 故障检测方法及装置

Publications (1)

Publication Number Publication Date
WO2016082343A1 true WO2016082343A1 (zh) 2016-06-02

Family

ID=55990144

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072699 WO2016082343A1 (zh) 2014-11-24 2015-02-10 故障检测方法及装置

Country Status (2)

Country Link
CN (1) CN105610598A (zh)
WO (1) WO2016082343A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107666437A (zh) * 2016-07-27 2018-02-06 中兴通讯股份有限公司 一种静态隧道恢复方法、装置及网络节点
CN106972951B (zh) * 2017-02-27 2019-11-08 杭州天宽科技有限公司 一种基于多个相关功能模块异常检测的自动维护实现方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101447900A (zh) * 2008-12-15 2009-06-03 华为技术有限公司 一种建立双向转发检测的方法、系统及设备
CN101465859A (zh) * 2009-01-13 2009-06-24 中兴通讯股份有限公司 一种触发主备用接口板倒换的方法及装置
US20090323520A1 (en) * 2008-06-30 2009-12-31 Cisco Technology, Inc., a coporation of California Bidirectional Forwarding Detection on Multilink Bundled Interfaces
CN101622851A (zh) * 2007-01-12 2010-01-06 艾利森电话股份有限公司 用于为高速环境提供对端活跃度的方法和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102480423B (zh) * 2010-11-30 2016-03-30 中兴通讯股份有限公司 一种l2tp网络的保护方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101622851A (zh) * 2007-01-12 2010-01-06 艾利森电话股份有限公司 用于为高速环境提供对端活跃度的方法和系统
US20090323520A1 (en) * 2008-06-30 2009-12-31 Cisco Technology, Inc., a coporation of California Bidirectional Forwarding Detection on Multilink Bundled Interfaces
CN101447900A (zh) * 2008-12-15 2009-06-03 华为技术有限公司 一种建立双向转发检测的方法、系统及设备
CN101465859A (zh) * 2009-01-13 2009-06-24 中兴通讯股份有限公司 一种触发主备用接口板倒换的方法及装置

Also Published As

Publication number Publication date
CN105610598A (zh) 2016-05-25

Similar Documents

Publication Publication Date Title
JP6491745B2 (ja) 仮想ネットワーク機能プールと制御エンティティとの間におけるインターフェース・エレメントのための方法、およびシステム
US9501371B2 (en) Method and apparatus for indirectly assessing a status of an active entity
KR101706439B1 (ko) 리던던트 네트워크 접속
JP5801175B2 (ja) パケット通信装置および方法
WO2016106743A1 (zh) 对聚合链路进行双向转发检测的方法、设备和系统
WO2012068996A1 (zh) 链路状态检测方法和装置
EP2696542A1 (en) Method, ToR switch, and system for implementing protection switchover based on TRILL network
WO2017054547A1 (zh) 双向转发检测的方法和装置
WO2015184739A1 (zh) 故障检测方法及装置
WO2016082710A1 (zh) 一种呼叫控制方法、Diameter协议转发设备及系统
US11128663B2 (en) Synchronizing link and event detection mechanisms with a secure session associated with the link
WO2015149353A1 (zh) 一种oam报文处理方法、网络设备和网络系统
CN103490951A (zh) 基于bfd的多跳链路中双向转发检测方法
WO2015039574A1 (zh) 网络故障恢复方法、控制服务器及交换机
WO2015139534A1 (zh) 基于ptn的实现链路状态穿通功能的系统、方法及装置
JP2020521409A (ja) Ｎｅｔｃｏｎｆセッション状態の検出方法、装置及びコンピュータ読取可能な記録媒体
WO2017036165A1 (zh) 链路故障检测方法及装置
WO2016082343A1 (zh) 故障检测方法及装置
WO2016106589A1 (zh) 失效对等体检测方法、IPsec对等体和网络设备
JP2008199081A (ja) ファイアウォール装置およびファイアウォールシステム
JP5558436B2 (ja) ネットワークシステムおよびネットワーク故障回避方法
KR20200072941A (ko) 실시간 오류 감지를 통한 vrrp 기반의 네트워크 장애 대응 방법 및 장치
CN106301835B (zh) 一种bfd建链的方法及其装置、路由器
TWI394402B (zh) 網路偵測設備及其主動偵測網路品質的方法
KR101587332B1 (ko) 컨트롤러와 네트워크 장치 간 연결 상태 확인 방법

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: 15864057

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: 15864057

Country of ref document: EP

Kind code of ref document: A1