topic Route convergence when using a Redistribution Profile in General Topics

Route convergence when using a Redistribution Profile

johnsonto — Fri, 02 Feb 2018 01:36:34 GMT

This is my scenario. I have an eBGP relationship from my PA to Vendor A and Vendor B. I have users that traverse this firewall and use their respective applications. I have Vendor C which is a site-to-site vpn. I'm doing a routed vpn with this vendor and I have static routes for Vendor C going across the tunnel interface. The issue I am having is the route was configured in the static route and added to the redistribution profile for Vendor C. When I committed the change users that were working with applications from Vendor A and B dropped. The drop was about 30 seconds and then came back. The PA never lost the bgp peer with either vendor but the applications dropped.

I ran a test by sending a ping to the destination IP in Vendor A's network and about 30 seconds to a minute after the commit change I dropped my ping. What I noticed was that the route went away even though I could see it in the firewall route table.

Has anyone out in the community seen or experienced this? When adding a route to the redistribution profile is there a route re-convergence that happens?

Re: Route convergence when using a Redistribution Profile

LOkazawa — Sat, 07 Oct 2023 07:11:00 GMT

Hi Johnsonto
Hope you are doing well.
I was wondering if you figure out what is the solution to resolve this issue.
Thank you.

Re: Route convergence when using a Redistribution Profile

CCIE11129 — Fri, 29 Nov 2024 09:26:24 GMT

Did you ever find a solution to this? I see something similar but not exact. I have a static route pointing to a host route /32 on the inside interface, so the static route should only advertise via eBGP when the /32 route is seen.on the inside interface. It is a recursive route. It works, but from time to time the eBGP no longer has the static route. I clearly see the route for the /32 host route and the /32 static route that points to it in the routing table of the Palo Alto.