From 8c4f63817a1861adf8dba97849c4ef60b17432bc Mon Sep 17 00:00:00 2001 From: vivek Date: Thu, 8 Sep 2016 10:03:30 -0700 Subject: bgpd: Process directly connected IBGP peers upon interface down When we have a single-hop BFD session for any peering, it really means that the peering is directly connected (maybe over a L2 network), whether it is IBGP or EBGP. In such a case, upon link down, immediately process IBGP peers too (and bring them down), not just EBGP peers. This change eliminates some peculiar state transitions in specific IBGP topologies, thus getting rid of the problem of nexthops remaining inactive in the zebra RIB. Signed-off-by: Vivek Venkatraman Reviewed-by: Donald Sharp Reviewed-by: Daniel Walton Ticket: CM-12390 Reviewed By: CCR-5156 Testing Done: Manual, bgp-smoke --- bgpd/bgp_bfd.h | 3 +++ 1 file changed, 3 insertions(+) (limited to 'bgpd/bgp_bfd.h') diff --git a/bgpd/bgp_bfd.h b/bgpd/bgp_bfd.h index 4e554af69..e872637e3 100644 --- a/bgpd/bgp_bfd.h +++ b/bgpd/bgp_bfd.h @@ -42,4 +42,7 @@ bgp_bfd_peer_config_write(struct vty *vty, struct peer *peer, char *addr); extern void bgp_bfd_show_info(struct vty *vty, struct peer *peer, u_char use_json, json_object *json_neigh); +extern int +bgp_bfd_is_peer_multihop(struct peer *peer); + #endif /* _QUAGGA_BGP_BFD_H */ -- cgit v1.2.3