cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Choose one of the topics below for SD-WAN Resources to help you on your journey with SD-WAN

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!
We will not comment or assist with your TAC case in these forums.

170
Views
0
Helpful
1
Replies
Highlighted
Beginner

Limiting BFD Session (hub and spoke design)

Hi,

 

I want to limit the number of BFD sessions a router tries to form, because all branch routers are starting to show up as partial connectivity in the Dashboard after deployment, even though from a design point of view, everything is fine.

We're running a hub-spoke topology through a centralized policy and only allow the branches to connect to the hub routers. For this reason, the BFD sessions don't work.

 

Yet, they try to set them up and therefore report partial connectivity. Perhaps the better question would be, how do I prevent the distribution of all the known TLOCs to all other TLOCs?

 

Kind regards,

Axel

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

I figured it out now: my centralized policy was missing a Hub-Spoke topology. The data policy portion of the centralized policy was already configured for hub-spoke, so the traffic could only go this way. However, without a clear hub-spoke topology definition within that same centralized policy, the vManage expects each router to build a bfd session to all other TLOCs.

 

The policy worked already as designed, but I was missing the topology aspect.

View solution in original post

1 REPLY 1
Highlighted
Beginner

I figured it out now: my centralized policy was missing a Hub-Spoke topology. The data policy portion of the centralized policy was already configured for hub-spoke, so the traffic could only go this way. However, without a clear hub-spoke topology definition within that same centralized policy, the vManage expects each router to build a bfd session to all other TLOCs.

 

The policy worked already as designed, but I was missing the topology aspect.

View solution in original post

Content for Community-Ad