summaryrefslogtreecommitdiffstats
path: root/isisd/isis_bfd.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* bfdd, lib, bgpd: add bfd cbit usagePhilippe Guibert2019-05-141-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | bfd cbit is a value carried out in bfd messages, that permit to keep or not, the independence between control plane and dataplane. In other words, while most of the cases plan to flush entries, when bfd goes down, there are some cases where that bfd event should be ignored. this is the case with non stop forwarding mechanisms where entries may be kept. this is the case for BGP, when graceful restart capability is used. If BFD event down happens, and bgp is in graceful restart mode, it is wished to ignore the BFD event while waiting for the remote router to restart. The changes take into account the following: - add a config flag across zebra layer so that daemon can set or not the cbit capability. - ability for daemons to read the remote bfd capability associated to a bfd notification. - in bfdd, according to the value, the cbit value is set - in bfdd, the received value is retrived and stored in the bfd session context. - by default, the local cbit announced to remote is set to 1 while preservation of the local path is not set. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* bgp, ospfd, ospf6d, pimd, lib, isisd: add bfd_client_sendmsg vrf_idPhilippe Guibert2019-05-071-2/+2
| | | | | | | vrf_id parameter is added to the api of bfd_client_sendmsg(). this permits being registered to bfd from a separate vrf. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* *: use ZAPI_CALLBACK_ARGS macro for zapi handlersQuentin Young2019-05-031-4/+2
| | | | | | | | | | | | This macro: - Marks ZAPI callbacks for readability - Standardizes argument names - Makes it simple to add ZAPI arguments in the future - Ensures proper types - Looks better - Shortens function declarations Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
* isisd: Fix license header of bfd codeChristian Franke2018-10-121-11/+8
|
* isisd: Address code-style warningsChristian Franke2018-10-121-1/+5
|
* isisd: don't add deprecated bfd commandChristian Franke2018-10-091-8/+1
|
* isisd: Track BFD state and take down adjacency on failureChristian Franke2018-10-051-1/+57
| | | | Signed-off-by: Christian Franke <chris@opensourcerouting.org>
* isisd: Add debugging for BFDChristian Franke2018-10-051-0/+61
| | | | Signed-off-by: Christian Franke <chris@opensourcerouting.org>
* isisd: Implement BFD replay functionChristian Franke2018-10-051-0/+12
| | | | Signed-off-by: Christian Franke <chris@opensourcerouting.org>
* isisd: Register/deregister BFD peers for adjacenciesChristian Franke2018-10-051-1/+123
| | | | Signed-off-by: Christian Franke <chris@opensourcerouting.org>
* isisd: Write BFD configChristian Franke2018-10-051-0/+22
| | | | Signed-off-by: Christian Franke <chris@opensourcerouting.org>
* isisd: Add BFD configuration commandsChristian Franke2018-10-051-0/+23
| | | | Signed-off-by: Christian Franke <chris@opensourcerouting.org>
* isisd: Register as BFD clientChristian Franke2018-10-051-0/+60
Signed-off-by: Christian Franke <chris@opensourcerouting.org>