But I'm not sure if this option makes ECMP possible between static routes and BGP routes.
Probably somebody from FTNT can answer to your question. Or, you just need to test it yourself since these would be simple changes. My guess is still the static default route is preferred over the BGP learned default route when admin distances are the same. Because I vaguely remember the same conversation was in this forum years ago and the conclusion at that time was the poster couldn't make them equal.
I have changed the admin distance and metric for BGP learned default route to match the static route ones so it also gets installed onto the routing table.... The only thing I can seen to figure out is how to configure priority for a BGP learned route like you do with statically configured routes
I have 2x lines from one ISP and another from another ISP, they're running vrrp so with static routes that's my gateway. We have a different VIP range from the ISP, routes for that are injected onto the CE side - so my thinking is we can have BGP configured between my fgt and ISP 1 two CEs, they'll advertise a default route to me and I'll advertise out the VIP range, however the two routes need to appear in the routing table like they would if you have 2x static default routes with different priorities.
The reason I'd have BGP is that I also need to failover the VIP range between sites during a DR instead of having to log a call with the ISP 1 and have them statically failover the ranges.
OK More questions now that I Have a clearer idea of what's going on. For future I will refer to 2x link ISP as "ISP1" and the other as "ISP2".
Does ISP1 use BGP with you today? If not do they even support talking BGP with you?
Does ISP2 use BGP and/or support it?
IS your public range a /24 or larger block that you own? Or is it an ISP block that is provided to you from your ISP? I.e. can you use the same public range on ISP2 when ISP1 is down?
The question of moving the public range to the DR site leads me to believe you are just being given a public block assigned (and owned) by the ISP1 as they are the ones involved in moving it to the DR site.
Have you spoken to your ISP about this? Have they suggested they could use BGP to solve it?
If so and this is all cleared up now is the issue that you want BGP default route to co-exist with static default route to ISP2 for things like load balancing, SD-WAN, etc?
If that is the case have you spoken to ISP2 to see if they support BGP?
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.