BGP Site to site VPN learned routes still in table despite the BGP peer down for a week

the hub reset

Hi

I did do a reset of the VNG but this did not resolve the issue, at present I deconfigured the fortigate as we had another issue and wanted to eliminat the new additions of BGP. the current state is that the GBP routes are not imported to the active routing table on the Azure side

Thanks for the help, I will try to get a slot to rest the VPN GW again and will let you know!!

Welcome to Microsoft Q&A!

@Brendan Edward Richardson I hope you are doing well,

Under normal circumstances, when a BGP peer goes down, the hold timer expires (usually within a few minutes) and the Azure VPN Gateway should automatically flush those learned routes from the routing table. If these routes have been stuck for a week after BGP was disabled on your FortiGate, the Azure VPN Gateway's internal routing service has likely encountered a state synchronization issue and failed to clear its cache.

Recommended Next Step: To force the gateway to flush its routing table and rebuild the current routing state, the most effective self-service fix is to perform a Gateway Reset.

In the Azure Portal, navigate to your Virtual Network Gateway.

In the left-hand menu under the Help section, select Reset.

1. Click the Reset button.

Note: Resetting the gateway reboots the underlying infrastructure VMs. This will cause a brief drop in connectivity (usually a couple of minutes) for any other active VPN connections attached to this gateway while it reboots.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution