BFD Flapping Down Reason: DETECT TIMER EXPIRED

sebastien3 · ‎08-22-2023

Hello,

I can't understand why I have flap with BFD on EIGRP. Here is the log. Same thing on all routers !

To remove the flapping I had to do a no bfd interval 750 min_rx 750 multiplier 3 on po1.171 and po1.181. It seems to me that this command allowed to stop the flaping... ???

Aug 22 12:33:19: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:120 handle:12,is going Down Reason: DETECT TIMER EXPIRED
Aug 22 12:33:19: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::64 reset (BFD adjacency down)
Aug 22 12:33:19: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:116 neigh proc:EIGRP, handle:8 act

Aug 22 12:33:19: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::64 Down BFD adjacency down
Aug 22 12:33:19: %BGP_SESSION-5-ADJCHANGE: neighbor FD00:1:10:10:1::64 IPv6 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:33:19: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::64 (Port-channel1.171) is down: BFD peer down notified
Aug 22 12:33:20: %BGP-5-NBR_RESET: Neighbor 10.10.1.64 reset (BFD adjacency down)
Aug 22 12:33:20: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.64 (Port-channel1.181) is down: BFD peer down notified
Aug 22 12:33:20: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: BFD peer down notified
Aug 22 12:33:20: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::33 (Port-channel1.171) is down: BFD peer down notified
Aug 22 12:33:20: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: BFD peer down notified
Aug 22 12:33:20: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.33 (Port-channel1.181) is down: BFD peer down notified
Aug 22 12:33:20: %BGP-5-ADJCHANGE: neighbor 10.10.1.64 Down BFD adjacency down

Aug 22 12:33:20: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.64 IPv4 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:33:20: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::65 reset (BFD adjacency down)
Aug 22 12:33:20: %BGP-5-NBR_RESET: Neighbor 10.10.1.65 reset (BFD adjacency down)
Aug 22 12:33:20: %BGP-5-NBR_RESET: Neighbor 10.10.1.33 reset (BFD adjacency down)
Aug 22 12:33:20: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::33 reset (BFD adjacency down)
Aug 22 12:33:22: %BGP-5-ADJCHANGE: neighbor 10.10.1.33 Down BFD adjacency down
Aug 22 12:33:22: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.33 IPv4 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:33:22: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Down BFD adjacency down
Aug 22 12:33:22: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.65 IPv4 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:33:22: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::33 Down BFD adjacency down
Aug 22 12:33:22: %BGP_SESSION-5-ADJCHANGE: neighbor FD00:1:10:10:1::33 IPv6 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:33:22: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::65 Down BFD adjacency down
Aug 22 12:33:22: %BGP_SESSION-5-ADJCHANGE: neighbor FD00:1:10:10:1::65 IPv6 Unicast topology base removed from session  BFD adjacency down

Aug 22 12:33:48: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.33 (Port-channel1.181) is up: new adjacency
Aug 22 12:33:48: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.33 proc:EIGRP, idb:Port-channel1.181 handle:6 act
Aug 22 12:33:48: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::64 (Port-channel1.171) is up: new adjacency
Aug 22 12:33:48: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::33 (Port-channel1.171) is up: new adjacency
Aug 22 12:33:48: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.64 (Port-channel1.181) is up: new adjacency
Aug 22 12:33:49: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency
Aug 22 12:33:49: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency

Aug 22 12:33:49: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:115 handle:7 is going UP
Aug 22 12:33:49: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:120 neigh proc:CEF, handle:12 act

Aug 22 12:33:49: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::33 Up 
Aug 22 12:33:51: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:114 handle:6,is going Down Reason: RX ADMINDOWN
Aug 22 12:33:51: %BGP-5-NBR_RESET: Neighbor 10.10.1.64 active reset (BGP Notification sent)
Aug 22 12:33:51: %BGP-5-ADJCHANGE: neighbor 10.10.1.64 Up 

Aug 22 12:33:52: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: Peer Termination received
Aug 22 12:33:52: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency

Aug 22 12:33:56: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received
Aug 22 12:33:56: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:118 neigh proc:EIGRP, handle:10 act
Aug 22 12:33:56: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:33:56: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FE80:1:10:10:1::65 proc:EIGRP, idb:Port-channel1.171 handle:10 act
Aug 22 12:33:56: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:121 handle:13,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:01: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:BGP, idb:Port-channel1.181 handle:5 act

Aug 22 12:34:01: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Up 

Aug 22 12:34:03: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:118 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:09: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FD00:1:10:10:1::64 proc:BGP, idb:Port-channel1.171 handle:12 act

Aug 22 12:34:09: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::64 Up 
Aug 22 12:34:10: %BGP-5-ADJCHANGE: neighbor 10.10.1.33 Up 

Aug 22 12:34:10: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:113 handle:5,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:12: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:122 handle:12 is going UP

Aug 22 12:34:14: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: Peer Termination received
Aug 22 12:34:14: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:EIGRP, handle:5 act
Aug 22 12:34:15: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency

Aug 22 12:34:15: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:EIGRP, idb:Port-channel1.181 handle:5 act

Aug 22 12:34:17: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::65 Up 

Aug 22 12:34:18: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:113 handle:5,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:18: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received

Aug 22 12:34:19: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:118 neigh proc:CEF, handle:10 act

Aug 22 12:34:22: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:34:22: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FE80:1:10:10:1::65 proc:EIGRP, idb:Port-channel1.171 handle:10 act

Aug 22 12:34:24: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:114 handle:6 is going UP

Aug 22 12:34:25: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:121 handle:13,is going Down Reason: RX ADMINDOWN

Aug 22 12:34:33: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:118 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:37: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: Peer Termination received
Aug 22 12:34:37: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:EIGRP, handle:5 act
Aug 22 12:34:37: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency

Aug 22 12:34:37: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:EIGRP, idb:Port-channel1.181 handle:5 act

Aug 22 12:34:41: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:118 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:41: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received

Aug 22 12:34:43: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::65 passive reset (Peer closed the session)
Aug 22 12:34:43: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:34:43: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FE80:1:10:10:1::65 proc:EIGRP, idb:Port-channel1.171 handle:10 act

Aug 22 12:34:46: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:118 handle:10,is going Down Reason: DETECT TIMER EXPIRED





Aug 22 12:34:52: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:113 handle:5,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:34:58: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:118 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:35:00: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: Peer Termination received
Aug 22 12:35:00: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:EIGRP, handle:5 act
Aug 22 12:35:00: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency

Aug 22 12:35:00: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:EIGRP, idb:Port-channel1.181 handle:5 act

Aug 22 12:35:02: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received
Aug 22 12:35:02: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:35:03: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:113 handle:5,is going Down Reason: DETECT TIMER EXPIRED
Aug 22 12:35:04: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.65 IPv4 Unicast topology base removed from session  NSF peer closed the session
Aug 22 12:35:04: %BGP-5-NBR_RESET: Neighbor 10.10.1.65 reset (NSF peer closed the session)
Aug 22 12:35:04: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Down NSF peer closed the session

Aug 22 12:35:09: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:118 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:35:12: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:BGP, idb:Port-channel1.181 handle:5 act

Aug 22 12:35:12: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Up 

Aug 22 12:35:15: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:119 handle:11,is going Down Reason: DETECT TIMER EXPIRED
Aug 22 12:35:15: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::33 reset (BFD adjacency down)
Aug 22 12:35:15: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::33 Down BFD adjacency down
Aug 22 12:35:15: %BGP_SESSION-5-ADJCHANGE: neighbor FD00:1:10:10:1::33 IPv6 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:35:15: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:119 neigh proc:BGP, handle:11 act

Aug 22 12:35:15: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::64 reset (BFD adjacency down)
Aug 22 12:35:15: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::64 Down BFD adjacency down
Aug 22 12:35:15: %BGP_SESSION-5-ADJCHANGE: neighbor FD00:1:10:10:1::64 IPv6 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:35:15: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::64 (Port-channel1.171) is down: BFD peer down notified
Aug 22 12:35:15: %BGP-5-NBR_RESET: Neighbor 10.10.1.64 reset (BFD adjacency down)
Aug 22 12:35:15: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.64 (Port-channel1.181) is down: BFD peer down notified
Aug 22 12:35:15: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::33 (Port-channel1.171) is down: BFD peer down notified
Aug 22 12:35:15: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.33 (Port-channel1.181) is down: BFD peer down notified
Aug 22 12:35:16: %BGP-5-ADJCHANGE: neighbor 10.10.1.64 Down BFD adjacency down
Aug 22 12:35:16: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.64 IPv4 Unicast topology base removed from session  BFD adjacency down
Aug 22 12:35:16: %BGP-5-NBR_RESET: Neighbor 10.10.1.33 reset (BFD adjacency down)
Aug 22 12:35:16: %BGP-5-ADJCHANGE: neighbor 10.10.1.33 Down BFD adjacency down
Aug 22 12:35:16: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.33 IPv4 Unicast topology base removed from session  BFD adjacency down

Aug 22 12:35:28: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: holding time expired
Aug 22 12:35:28: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:EIGRP, handle:5 act

Aug 22 12:35:28: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: holding time expired

Aug 22 12:35:44: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:122 handle:12,is going Down Reason: RX ADMINDOWN
Aug 22 12:35:44: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.65 IPv4 Unicast topology base removed from session  NSF peer closed the session
Aug 22 12:35:44: %BGP-5-NBR_RESET: Neighbor 10.10.1.65 reset (NSF peer closed the session)
Aug 22 12:35:44: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Down NSF peer closed the session
Aug 22 12:35:44: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:BGP, handle:5 act
Aug 22 12:35:45: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::64 (Port-channel1.171) is up: new adjacency
Aug 22 12:35:45: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::33 (Port-channel1.171) is up: new adjacency
Aug 22 12:35:45: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FE80:1:10:10:1::64 proc:EIGRP, idb:Port-channel1.171 handle:8 act
Aug 22 12:35:45: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:35:46: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.33 (Port-channel1.181) is up: new adjacency
Aug 22 12:35:46: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency
Aug 22 12:35:46: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.64 (Port-channel1.181) is up: new adjacency
Aug 22 12:35:47: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:116 handle:8 is going UP

Aug 22 12:35:47: %BGP_SESSION-5-ADJCHANGE: neighbor FD00:1:10:10:1::65 IPv6 Unicast topology base removed from session  NSF peer closed the session
Aug 22 12:35:47: %BGP-5-NBR_RESET: Neighbor FD00:1:10:10:1::65 reset (NSF peer closed the session)
Aug 22 12:35:47: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::65 Down NSF peer closed the session

Aug 22 12:35:48: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received
Aug 22 12:35:48: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:35:50: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:121 handle:13,is going Down Reason: DETECT TIMER EXPIRED
Aug 22 12:35:51: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: Peer Termination received

Aug 22 12:35:51: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:EIGRP, handle:5 act
Aug 22 12:35:51: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:BGP, idb:Port-channel1.181 handle:5 act
Aug 22 12:35:51: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Up 

Aug 22 12:35:53: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::65 Up 

Aug 22 12:35:56: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:123 handle:10,is going Down Reason: DETECT TIMER EXPIRED
Aug 22 12:35:56: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency

Aug 22 12:35:56: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:EIGRP, idb:Port-channel1.181 handle:5 act
Aug 22 12:35:57: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.65 IPv4 Unicast topology base removed from session  NSF peer closed the session
Aug 22 12:35:57: %BGP-5-NBR_RESET: Neighbor 10.10.1.65 reset (NSF peer closed the session)
Aug 22 12:35:57: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Down NSF peer closed the session
Aug 22 12:35:57: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:BGP, handle:5 act

Aug 22 12:36:01: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:113 handle:5,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:04: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:BGP, idb:Port-channel1.181 handle:5 act

Aug 22 12:36:04: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Up 
Aug 22 12:36:05: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::33 Up 

Aug 22 12:36:07: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:123 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:08: %BGP-5-ADJCHANGE: neighbor FD00:1:10:10:1::64 Up 
Aug 22 12:36:08: %BGP-5-ADJCHANGE: neighbor 10.10.1.64 Up 

Aug 22 12:36:08: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:122 handle:12 is going UP

Aug 22 12:36:10: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.33 proc:BGP, idb:Port-channel1.181 handle:6 act

Aug 22 12:36:10: %BGP-5-ADJCHANGE: neighbor 10.10.1.33 Up 
Aug 22 12:36:10: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.65 IPv4 Unicast topology base removed from session  NSF peer closed the session
Aug 22 12:36:10: %BGP-5-NBR_RESET: Neighbor 10.10.1.65 reset (NSF peer closed the session)
Aug 22 12:36:10: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Down NSF peer closed the session
Aug 22 12:36:10: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:113 neigh proc:BGP, handle:5 act
Aug 22 12:36:11: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received
Aug 22 12:36:12: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:36:13: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:113 handle:5,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:13: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is down: Peer Termination received

Aug 22 12:36:14: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:119 handle:11 is going UP

Aug 22 12:36:18: %DUAL-5-NBRCHANGE: EIGRP-IP4 1: Neighbor 10.10.1.65 (Port-channel1.181) is up: new adjacency
Aug 22 12:36:18: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.65 proc:EIGRP, idb:Port-channel1.181 handle:5 act
Aug 22 12:36:18: %BGP-5-ADJCHANGE: neighbor 10.10.1.65 Up 

Aug 22 12:36:19: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:123 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:22: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.1.33 IPv4 Unicast topology base removed from session  NSF peer closed the session
Aug 22 12:36:22: %BGP-5-NBR_RESET: Neighbor 10.10.1.33 reset (NSF peer closed the session)
Aug 22 12:36:22: %BGP-5-ADJCHANGE: neighbor 10.10.1.33 Down NSF peer closed the session

Aug 22 12:36:22: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:114 neigh proc:BGP, handle:6 act

Aug 22 12:36:25: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:114 handle:6,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:30: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:123 handle:10,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:33: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.10.1.33 proc:BGP, idb:Port-channel1.181 handle:6 act

Aug 22 12:36:33: %BGP-5-ADJCHANGE: neighbor 10.10.1.33 Up 
Aug 22 12:36:34: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received

Aug 22 12:36:34: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:123 neigh proc:EIGRP, handle:10 act

Aug 22 12:36:36: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:114 handle:6,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:40: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:36:40: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FE80:1:10:10:1::65 proc:EIGRP, idb:Port-channel1.171 handle:10 act

Aug 22 12:36:42: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:121 handle:13,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:45: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:114 handle:6 is going UP

Aug 22 12:36:50: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:121 handle:13,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:36:55: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is down: Peer Termination received

Aug 22 12:36:55: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:124 neigh proc:EIGRP, handle:10 act

Aug 22 12:36:58: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:121 handle:13,is going Down Reason: DETECT TIMER EXPIRED

Aug 22 12:37:00: %DUAL-5-NBRCHANGE: EIGRP-IP6 6: Neighbor FE80:1:10:10:1::65 (Port-channel1.171) is up: new adjacency

Aug 22 12:37:00: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh FE80:1:10:10:1::65 proc:EIGRP, idb:Port-channel1.171 handle:10 act

Aug 22 12:37:04: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:125 handle:10,is going Down Reason: DETECT TIMER EXPIRED

What can explain the reason for the flapping ?

Thanks

Flavio Miranda · ‎08-22-2023

Hi @sebastien3

How the topology looks like?

The command you ran, cause the bfd not to be monitored and that can explain the logs stops. But your problem seems to be related to BGP and EIGRP and not BGP itself.

If you ping from one side to another, do you see any packet loss?

sebastien3 · ‎08-22-2023

Hi @Flavio Miranda

Routers are connected via switchs using vlan 171 and 181. No dropped packets when pinging from routers to each other...

Flavio Miranda · ‎08-22-2023

It is weird why BGP and EIGRP is losing adjacency like that, seems some connectivity issue. The BFD seems to be only reacting to the protocols changing.

If you can share the config from routers and switch, maybe anyone can see something you could be missing.

Joseph W. Doherty · ‎09-23-2023

BTW, usually, I believe, it should be the other way around, i.e. a BFD drop would break anything using it for keep alive purposes, like routing protocols.

qruczlevy88 · ‎01-11-2024

Not the BFD issue triggered the routing protocols? Isn't it how it is supposed to work?

balaji.bandi · ‎08-22-2023

After removing that command network stable, i would check the IOS code running any bugs reported.

some troubleshooting tips if you like to enable back :

https://www.cisco.com/c/en/us/support/docs/ip/ip-routing/220364-troubleshoot-bidirectional-forwarding-de.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

sebastien3 · ‎08-22-2023

Hi @balaji.bandi

The IOS is asr1000rp2-adventerprisek9.03.16.10.S.155-3.S10-ext.b. I will look at your link !

balaji.bandi · ‎08-22-2023

i will check any bugs around on that version, can you post show interface pox/x both the side ( see any input drops)

we understand you did not see ping loss when you tested right ?

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

sebastien3 · ‎08-22-2023

can you post show interface pox/x both the side ( see any input drops)

Po1.181 port Ge0/2/4 and Ge0/3/4

Full Duplex, 1000Mbps, link type is auto, media type is ZX
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:25, output 00:00:49, output hang never
Last clearing of "show interface" counters 2y36w
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 404381000 bits/sec, 66149 packets/sec
5 minute output rate 92395000 bits/sec, 12300 packets/sec
102921112774 packets input, 63762462219284 bytes, 0 no buffer
Received 848 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 113207505 multicast, 0 pause input
403455174015 packets output, 371365508016788 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

Keepalive not supported
Full Duplex, 1000Mbps, link type is auto, media type is LX
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:04, output 00:00:46, output hang never
Last clearing of "show interface" counters 2y36w
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 7446000 bits/sec, 831 packets/sec
5 minute output rate 87347000 bits/sec, 11348 packets/sec
156037618042 packets input, 111773725388744 bytes, 0 no buffer
Received 868771 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 63078968 multicast, 0 pause input
362976905774 packets output, 344997782808461 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

interface Port-channel1.181
description - R1 -
encapsulation dot1Q 181
ip address 10.10.1.65 255.255.0.0
no ip redirects
no ip proxy-arp
ip verify unicast source reachable-via any
bfd interval 750 min_rx 750 multiplier 3
no bfd echo

interface Port-channel1.181
description - R2 -
encapsulation dot1Q 181
ip address 10.10.1.64 255.255.0.0
no ip redirects
no ip proxy-arp
ip verify unicast source reachable-via any
bfd interval 750 min_rx 750 multiplier 3
no bfd echo

> we understand you did not see ping loss when you tested right ?

Yes ! No ping loss.