10-31-2023 07:25 AM - edited 10-31-2023 07:29 AM
I have Cisco ASR1001 SD-WAN device. Recently there was flap observed in BFD sessions . Most of the BFD sessions were up but 2 BFD sessions are down
When I used the command show platform hardware qfp active feature bfd datapath sdwan summary & I am getting that the state is INIT
Wanted to understand what is the reason for this INIT & how should I identify and troubleshoot it.
Pls help.
10-31-2023 07:30 AM - edited 10-31-2023 07:33 AM
Not able to attach the screen shot due to some reasons.
But the state says that it is in INIT stage
10-31-2023 08:55 AM
Take a look at this TS doc which was uploaded by a memeber of the community - https://community.cisco.com/kxiwq67737/attachments/kxiwq67737/4461-docs-network-infrastructure/5812/1/SDWAN%20BFD%20Troubleshooting.docx
INIT is the starting state where the BFD session first tries to establish communication before it can verify connectivity and become operational. A session stuck in INIT points to a problem in this initial negotiation process that needs to be investigated and rectified.
10-31-2023 05:00 PM
I have gone through the docu, but sitll could not able to figure what is causing this issue ?
Any help or inputs will be helpful.
10-31-2023 05:31 PM
Also wanted to understand what are the reasons the state is in INIT stage ?
What could be the scenarios ?
10-31-2023 05:57 PM
10-31-2023 06:02 PM
10-31-2023 07:21 PM
Thanks. I checked the link. But still not able to sort it out.
When I typed the command show sdwan omp tlocs , the bfd status of that particular link is showing down.
10-31-2023 09:11 PM
10-31-2023 10:20 PM
thanks I do understand your point that it requires logs & the diagram.
Would like to understand that in case there is underlay problem how come some of the bfd sessions using the same underlay is working & only 3 bsd sessions are not working.
I think there is flap in the underlay network, because of that all the BFD sessions went down. Most of the BFD sessions came up, but only 3 bfd sessions didnt come up.
What could be the reasons ? Theoritical reason also I am ok for now as explanation ?
11-05-2023 04:55 PM
After troubleshooting & analyzing it was identified that the issue is due to the transport layer (Metro Ethernet)
One of the interface (Metro Ethernet Interface) Gi0/4 needs to be disabled & enabled to fix it.
Any Idea how to do it ? Has this to be done via CLI or via Templates ?
The SD-WAN model is ASR1001-X
11-06-2023 12:31 AM
The easiest way to do this would be to "shut" then "no shut" the interface from the CLI.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide