Reducing link state protocol traffic during graceful restart

Patent metadata

Field	Value
Publication number	US-2016269293-A1
Application number	US-201514700025-A
Country	US
Kind code	A1
Filing date	Apr 29, 2015
Priority date	Mar 11, 2015
Publication date	Sep 15, 2016
Grant date	—

Abstract

A routing device coupled to a remote routing device via a link on which a flood reduction technique is used, such as a demand circuit, is configured to store an indication of a link state of the remote routing device and a first sequence number associated with the link state, receive an indication that the remote routing device is performing a graceful restart, and then receive data indicative of a new link state of the remote routing device and a second sequence number. The routing device determines whether the new link state is different than the stored indication of the link state, and if not, avoids requesting the current link state from the remote routing device. In this manner, the routing device may reduce link-state protocol traffic within an autonomous system including the routing device and the remote routing device.

First claim

What is claimed is:

1 . A method comprising:
receiving, by a first routing device that is communicatively coupled to a second routing device via a link on which a flood reduction technique is used, a first set of data from the second routing device indicative of a first link state for the second routing device according to a link-state protocol, wherein the first set of data is associated with a first sequence number; storing, by the first routing device, data representative of the first link state and the first sequence number; after receiving the first set of data, receiving, by the first routing device, a second set of data from the second routing device indicating that the second routing device will be performing a graceful restart; after receiving the second set of data, receiving, by the first routing device, a third set of data from the second routing device representative of a second link state for the second routing device, wherein the third set of data is associated with a second sequence number that is different than the first sequence number; in response to the second set of data and the third set of data, determining, by the first routing device, whether the second link state is the same as the first link state despite the difference between the first sequence number and the second sequence number; and avoiding, by the first routing device, sending a request for a current link state to the second routing device when the second link state is determined to be the same as the first link state despite the difference between the first sequence number and the second sequence number.

2 . The method of claim 1 , wherein the first routing device and the second routing device are members of a common autonomous system.

3 . The method of claim 1 , wherein the first set of data is associated with a first checksum, wherein the third set of data is associated with a second checksum, wherein determining whether the second link state is different than the first link state comprises calculating a third checksum using the stored first link state after replacing the first sequence number with the second sequence number, and wherein avoiding comprises avoiding sending the request when the third checksum is the same as the second checksum.

4 . The method of claim 1 , wherein determining whether the second link state is the same as the first link state comprises determining whether the second link stat is the same as the first link state despite the difference between the first sequence number and the second sequence number and despite any difference between a first age for the first link state and a second age for the second link state.

5 . The method of claim 1 , wherein the first set of data comprises a link state advertisement (LSA).

6 . The method of claim 1 , wherein the second set of data comprises a grace link state advertisement (LSA).

7 . The method of claim 1 , wherein the third set of data comprises a database description (DBD) packet.

8 . The method of claim 1 , further comprising requesting data indicative of the current link state from the second routing device when the second link state is different than the first link state.

9 . The method of claim 1 , further comprising requesting data indicative of the current link state from the second routing device when an age of the stored data representing the first link state is equal to or greater than a predetermined maximum age.

10 . The method of claim 1 , wherein the first routing device comprises a spoke router, and wherein the second routing device comprises a hub router.

11 . The method of claim 1 , wherein the link-state protocol comprises Open Shortest Path First (OSPF).

12 . The method of claim 1 , wherein the link on which the flood reduction technique is used comprises an OSPF demand circuit.

13 . A routing device comprising:
a network interface communicatively coupled to a remote routing device of via a link on which a flood reduction technique is used; and one or more hardware-based processors configured to:
receive, via the network interface, a first set of data from the remote routing device indicative of a first link state for the remote routing device according to a link-state protocol, wherein the first set of data is associated with a first sequence number,
store data representative of the first link state and the first sequence number,
after receiving the first set of data, receive, via the network interface, a second set of data from the remote routing device indicating that the remote routing device will be performing a graceful restart,
after receiving the second set of data, receive, via the network interface, a third set of data from the remote routing device representative of a second link state for the remote routing device, wherein the third set of data is associated with a second sequence number that is different than the first sequence number,
in response to the second set of data and the third set of data, determine whether the second link state is different than the first link state despite the difference between the first sequence number and the second sequence number, and
avoid sending a request for a current link state to the remote routing device when the second link state is determined to be the same as the first link state despite the difference between the first sequence number and the second sequence number.

14 . The routing device of claim 13 , wherein the first routing device and the second routing device are members of a common autonomous system.

15 . The routing device of claim 13 , wherein the first set of data is associated with a first checksum, wherein the third set of data is associated with a second checksum, wherein to determine whether the second link state is different than the first link state, the one or more hardware-based processors are configured to calculate a third checksum using the stored first link state after replacing the first sequence number with the second sequence number, and wherein the one or more processors are configured to avoid sending the request when the third checksum is the same as the second checksum.

16 . The routing device of claim 13 , wherein the first set of data comprises a link state advertisement (LSA).

17 . The routing device of claim 13 , wherein the second set of data comprises a grace link state advertisement (LSA).

18 . The routing device of claim 13 , wherein the third set of data comprises a database description (DBD) packet.

19 . The routing device of claim 13 , wherein the one or more processors are further configured to request data indicative of the current link state from the remote routing device when the second link state is different than the first link state.

20 . The routing device of claim 13 , wherein the one or more processors are further configured to request data indicative of the current link state from the remote routing device when an age of the stored data representing the first link state is equal to or greater than a predetermined maximum age.

21 . The routing device of claim 13 , wherein the routing device comprises a spoke router, and wherein the remote routing device comprises a hub router.

22 . The routing device of claim 13 , wherein the link-state protocol comprises Open Shortest Path First (OSPF).

23 . The routing device of claim 13 , wherein the link on which the flood reduction technique is used comprises an OSPF demand circuit.

Assignees

• Juniper Networks Inc

Inventors

• K A Salih
• Hegde Shraddha

Classifications

• H04L45/32 Primary

  Flooding (denial of service attacks H04L63/1458) · CPC title

• H04L45/26

  Route discovery packet · CPC title

• H04L45/18

  Loop-free operations · CPC title

• H04L45/04

  Interdomain routing, e.g. hierarchical routing · CPC title

• H04L45/026

  Details of "hello" or keep-alive messages · CPC title