DISTINGUISHING BETWEEN CONNECTIVITY VERIFICATION AVAILABILITY AND FORWARDING PROTOCOL FUNCTIONALITY IN A COMPUTER NETWORK

• US 20090046723A1
• Filed: 08/16/2007
• Published: 02/19/2009
• Est. Priority Date: 08/16/2007
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Parker, Jonathan, Masse, Sylvain, Toscano, David P., Rahman, Reshad A., Ward, David D.
• Granted Patent: US 8,437,272 B2
• Time in Patent Office: Days
• US Class Current: 370/395.310
• CPC Class Codes: H04L 41/0695 the faulty arrangement being the maintenance, administration or management system
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

In one embodiment, a local network device may determine an inability to establish a connectivity verification protocol (e.g., Bidirectional Forwarding Detection, “BFD”) session to a remote network device, such as from unreturned control messages. In response, the local network device may send at least one connectivity verification protocol echo message to the remote network device destined to be returned to the local network device and forwarded using a forwarding protocol. In response to receiving or not receiving the echo message, the local network device may thus determine whether the forwarding protocol is functioning between the local and remote network devices. In this manner, the local network device may determine whether an inability to establish a connectivity verification protocol session is due to an inability to forward packets between the devices, or due to the connectivity verification protocol not working (or not being configured) on the remote network device.

Claims

1. A method, comprising:

determining an inability to establish a connectivity verification protocol session from a local network device to a remote network device;

sending at least one connectivity verification protocol echo message from the local network device to the remote network device, the echo message destined to be returned to the local network device and forwarded using a forwarding protocol;

in response to receiving the echo message at the local network device, determining that the forwarding protocol is functioning between the local and remote network devices; and

in response to not receiving the echo message at the local network device, determining that the forwarding protocol is not functioning between the local and remote network devices.

2. The method as in claim 1, wherein determining the inability further comprises:

transmitting a connectivity verification protocol control message from the local network device toward the remote network device; and

determining the inability in response to not receiving a returned connectivity verification protocol control message at the local network device from the remote network device.

3. The method as in claim 2, further comprising:

in response to receiving a returned connectivity verification protocol control message at the local network device from the remote network device, determining that the forwarding protocol is functioning between the local and remote network devices.

4. The method as in claim 1, further comprising:

determining that no echo messages are received at the local network device in response to not receiving a configured number of returned echo messages at the local network device from the remote network device.

5. The method as in claim 1, wherein determining the inability further comprises:

determining the inability in response to determining that the connectivity verification protocol is not configured on at least one of the local network device and the remote network device.

6. The method as in claim 1, wherein the connectivity verification protocol is Bidirectional Forwarding Detection (BFD).

7. The method as in claim 1, further comprising:

in response to receiving the echo message at the local network device and determining an inability to establish the connectivity verification protocol session, determining that the connectivity verification protocol is not operational at the remote network device.

8. The method as in claim 1, wherein determining the inability further comprises:

maintaining an established connectivity verification protocol session between the local and remote network devices with connectivity verification protocol control messages; and

determining the inability in response to determining that the connectivity verification protocol control messages are no longer received at the local network device.

9. The method as in claim 1, wherein determining the inability further comprises:

attempting to establish the connectivity verification protocol session between the local and remote network devices with connectivity verification protocol control messages; and

determining the inability in response to determining that no connectivity verification protocol control messages are received at the local network device.

10. The method as in claim 9, further comprising:

attempting to establish the session in response to receiving routing information at the local network device indicating a connection between the local and remote network devices.

11. The method as in claim 1, further comprising:

receiving a graceful connectivity verification protocol session shutdown at the local network device from the remote network device; and

continuing to send connectivity verification protocol echo messages from the local network device to the remote network device.

12. The method as in claim 1, further comprising:

in response to determining that the forwarding protocol is not functioning between the local and remote network devices, removing a routing adjacency between the local and remote network devices.

13. The method as in claim 1, further comprising:

receiving a connectivity verification protocol control message after determining that the forwarding protocol is not functioning between the local and remote network devices; and

in response to not receiving the echo message at the local network device, still determining that the forwarding protocol is not functioning between the local and remote network devices.

14. The method as in claim 1, further comprising:

learning of a routing adjacency between the local and remote network devices; and

in response

attempting to establish the connectivity verification protocol session.

15. The method as in claim 14, further comprising:

determining whether the forwarding protocol is functioning between the local and remote network devices prior to configuring forwarding of packets from the local network device to the remote network device in accordance with the routing adjacency.

16. The method as in claim 1, wherein the local and remote network devices maintain one of either a static routing adjacency with each other or an Intermediate-System-to-Intermediate-System (IS-IS) routing adjacency with each other.

17. The method as in claim 1, wherein the forwarding protocol is an Internet Protocol (IP).

18. The method as in claim 1, wherein determining whether the forwarding protocol is functioning between the local and remote network devices further comprises:

determining whether the forwarding protocol is functioning between the local and remote network devices over a multi-hop forwarding adjacency tunnel between the local and remote network devices.

19. An apparatus, comprising:

one or more network interfaces adapted to communicate with a remote network device;

one or more processors coupled to the network interfaces and adapted to execute one or more processes; and

a memory adapted to store a connectivity verification protocol process executable by each processor, the process when executed operable to;

i) determine an inability to establish a connectivity verification protocol session with a remote network device;

ii) send at least one connectivity verification protocol echo message to the remote network device, the echo message destined to be returned to the apparatus and forwarded using a forwarding protocol;

iii) determine that the forwarding protocol is functioning between the apparatus and the remote network device in response to receiving the echo message at the apparatus; and

iv) determine that the forwarding protocol is not functioning between the apparatus and the remote network device in response to not receiving the echo message at the apparatus.

20. The apparatus as in claim 19, wherein the connectivity verification protocol process when executed is further operable to:

transmit a connectivity verification protocol control message toward the remote network device; and

determine the inability in response to not receiving a returned connectivity verification protocol control message at the apparatus from the remote network device.

21. The apparatus as in claim 20, wherein the connectivity verification protocol process when executed is further operable to:

determine that the forwarding protocol is functioning between the apparatus and the remote network device in response to receiving a returned connectivity verification protocol control message at the apparatus.

22. The apparatus as in claim 19, wherein the connectivity verification protocol process when executed is further operable to:

determine that the connectivity verification protocol is not operational at the remote network device in response to receiving the echo message at the apparatus and determining an inability to establish the connectivity verification protocol session.

23. The apparatus as in claim 19, wherein the connectivity verification protocol process when executed is further operable to:

maintain an established connectivity verification protocol session between the apparatus and the remote network device with connectivity verification protocol control messages; and

determine the inability in response to determining that the connectivity verification protocol control messages are no longer received at the apparatus.

24. The apparatus as in claim 19, wherein the connectivity verification protocol process when executed is further operable to:

remove a routing adjacency between the local and remote network devices in response to determining that the forwarding protocol is not functioning between the apparatus and the remote network device.

25. The apparatus as in claim 19, wherein the connectivity verification protocol process when executed is further operable to:

learn of a routing adjacency between the apparatus and the remote network device; and

in response

attempt to establish the connectivity verification protocol session.

26. An apparatus, comprising:

means for determining an inability to establish a connectivity verification protocol session from a local network device to a remote network device;

means for sending at least one connectivity verification protocol echo message from the local network device to the remote network device, the echo message destined to be returned to the local network device and forwarded using a forwarding protocol;

means for determining that the forwarding protocol is functioning between the local and remote network devices in response to receiving the echo message at the local network device; and

means for determining that the forwarding protocol is not functioning between the local and remote network devices in response to not receiving the echo message at the local network device.