cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
301
Views
1
Helpful
2
Replies

BFDFSM Detect Timer Expired

martynch1
Level 1
Level 1

Morning all, we have a number (57) of site Routers that are experiencing the same problem with BFDFSM Detect Timer Expired.
We've got 17.09.04a on our C1111's

This is from the logs from one of the Routers:
Nov 19 18:54:42.268 GMT: %BFDFSM-6-BFD_SESS_DOWN: BFD-SYSLOG: BFD session ld:4098 handle:3,is going Down Reason: DETECT TIMER EXPIRED

Nov 19 18:54:42.274 GMT: %BGP-5-NBR_RESET: Neighbor 10.0.253.29 reset (BFD adjacency down)

Nov 19 18:54:42.274 GMT: %BGP-5-NBR_RESET: Neighbor 10.0.253.29 reset (BFD adjacency down)

Nov 19 18:54:42.274 GMT: %BGP-5-NBR_RESET: Neighbor 10.0.253.29 reset (BFD adjacency down)

Nov 19 18:54:42.274 GMT: %BGP-5-NBR_RESET: Neighbor 10.0.253.29 reset (BFD adjacency down)

Nov 19 18:54:42.276 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 Down BFD adjacency down

Nov 19 18:54:42.276 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 10.0.253.29 IPv4 Unicast topology base removed from session  BFD adjacency down

Nov 19 18:54:42.276 GMT: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:4097 neigh proc:BGP, idb:GigabitEthernet0/0/0.110 handle:2 active

Nov 19 18:54:42.277 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 vpn vrf CCTV Down BFD adjacency down

Nov 19 18:54:42.277 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 10.0.253.29 IPv4 Unicast vpn vrf CCTV topology base removed from session  BFD adjacency down

Nov 19 18:54:42.279 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 vpn vrf NCi_Data Down BFD adjacency down

Nov 19 18:54:42.279 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 10.0.253.29 IPv4 Unicast vpn vrf Data topology base removed from session  BFD adjacency down

Nov 19 18:54:42.280 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 vpn vrf Public Down BFD adjacency down

Nov 19 18:54:42.281 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 10.0.253.29 IPv4 Unicast vpn vrf Public topology base removed from session  BFD adjacency down

Nov 19 18:55:42.284 GMT: %BFD-6-BFD_SESS_DESTROYED: BFD-SYSLOG: bfd_session_destroyed,  ld:4099 neigh proc:CEF, idb:GigabitEthernet0/0/0.109 handle:4 active

Nov 19 18:56:24.460 GMT: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.0.253.29 proc:BGP, idb:GigabitEthernet0/0/0.108 handle:1 act

Nov 19 18:56:24.460 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 vpn vrf CCTV Up

Nov 19 18:56:25.408 GMT: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:4100 handle:1 is going UP

Nov 19 18:56:26.475 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 Up

Nov 19 18:56:28.569 GMT: %BGP-5-NBR_RESET: Neighbor 10.0.253.29 active reset (Peer closed the session)

Nov 19 18:56:28.569 GMT: %BGP-5-NBR_RESET: Neighbor 10.0.253.29 passive reset (Peer closed the session)

Nov 19 18:56:28.570 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 10.0.253.29 IPv4 Unicast vpn vrf Data topology base removed from session  Peer closed the session

Nov 19 18:56:33.668 GMT: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.0.253.29 proc:BGP, idb:GigabitEthernet0/0/0.109 handle:3 act

Nov 19 18:56:33.668 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 vpn vrf Public Up

Nov 19 18:56:33.683 GMT: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:4098 handle:3 is going UP

Nov 19 18:56:42.114 GMT: %BFD-6-BFD_SESS_CREATED: BFD-SYSLOG: bfd_session_created, neigh 10.0.253.29 proc:BGP, idb:GigabitEthernet0/0/0.101 handle:4 act

Nov 19 18:56:42.114 GMT: %BGP-5-ADJCHANGE: neighbor 10.0.253.29 vpn vrf Data Up

Nov 19 18:56:42.128 GMT: %BFDFSM-6-BFD_SESS_UP: BFD-SYSLOG: BFD session ld:4099 handle:4 is going UP

Our interface configs

interface GigabitEthernet0/0/0.101

description *** L3 Connection to vrf Data ***

encapsulation dot1Q 101

vrf forwarding Data

ip address 10.0.253.28 255.255.255.254

bfd interval 300 min_rx 300 multiplier 3

!        

interface GigabitEthernet0/0/0.102

description *** L3 Connection to vrf VoIP ***

encapsulation dot1Q 102

vrf forwarding NCi_VoIP

ip address 10.0.253.28 255.255.255.254

shutdown

 bfd interval 300 min_rx 300 multiplier 3

!        

interface GigabitEthernet0/0/0.108

description *** L3 Connection to vrf CCTV ***

encapsulation dot1Q 108

vrf forwarding CCTV

ip address 10.0.253.28 255.255.255.254

bfd interval 300 min_rx 300 multiplier 3

!        

interface GigabitEthernet0/0/0.109

description *** L3 Connection to vrf Public ***

encapsulation dot1Q 109

vrf forwarding Public

ip address 10.0.253.28 255.255.255.254

bfd interval 300 min_rx 300 multiplier 3

!        

interface GigabitEthernet0/0/0.110

description *** L3 Connection to vrf Net_Mng ***

encapsulation dot1Q 110

ip address 10.0.253.28 255.255.255.254

bfd interval 300 min_rx 300 multiplier 3


Thank you for any support you may give

2 Replies 2

M02@rt37
VIP
VIP

Hello @martynch1 

The log messages indicate that the BFD sessions on the router are going down and then coming back up. This behavior can be due to various reasons, including intermittent connectivity issues or misconfigurations.

Enable BFD debugging to get more detailed information about the BFD sessions. This can help in identifying the specific cause of the BFD session going down: debug bfd events

Check the cable on GigabitEthernet0/0/0.

Aslo, why same IP address on each sub-interface ?

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

bfd interval 500-900 min_rx 500-900 multiplier 3

This give some time to bgp neighbor to replay.

Review Cisco Networking for a $25 gift card