Configure IPSec with SD-WAN and Interaction with OSPF
Hi,
Sorry if the following question is a stupid one. I recently took over the management of our FortiGate's, so all of this is pretty new to me.
We currently have a hub and spoke architecture with our HQ handling the connections between all of our remote sites. We have site-to-site IPSec VPN connections with each of our branch offices. Our HQ has two individual ISP links.
We use OSFP as our primary routing protocol.
We've recently been experiencing an issue with one of the ISP links in our HQ and that is impacting some of these site-to-site connections.
I wanted to introduce redundancy, establishing IPSec connections on both the HQ's WAN interfaces for each branch and I know our previous administrator was looking into implementing IPSec VPN with SDWAN to achieve this. Each branch would have connections back to the HQ on both WAN1 and WAN2 interfaces, so if either is disrupted, the branch site would not lose access.
It should be noted that some sites on a single ISP connection and some have 2+. I will need to deal with these different scenarios.
While reading through the documentation and watching videos, I am getting stuck on a few points, the main one though being the creation of the static routes for the local LANs that are behind the FortiGate at each respective site - Configure IPsec VPN with SD-WAN - Fortinet Community
If we were to go the SDWAN route, are the static routes absolutely required?
If the static routes are required, what is the impact to our underlying OSPF?
And I am assuming I would need to create a ton of static routes to ensure that the sites could probably communicate with one another via HQ?
Is SD-WAN the right solution for what I am trying to accomplish? Is it possible without a major overhaul?
Thank you
