We're in the process of helping a client simplify their network and had a thought during the design phase.
SD-WAN will be used at the main site for their internet circuits - that part's easy. They also have multiple 1Gbit fiber circuits with different carriers that connect to their remote campuses. Normally we would choose one of the following:
[ol]We really like SD-WAN - the abstraction is very helpful and so easy to setup! What if we could leverage SD-WAN for the internal fiber links? I don't see a way to add another SD-WAN (virtual-wan-link) to a Fortigate, so it appears we're limited to just one. We could turn up another VDOM and use SD-WAN there for the fibers, but that adds a layer of complexity to troubleshooting that I don't want to put on the client. Any thoughts? Is this crazy talk? See the diagram for clarity.
As a followup to this for those that want the full picture.
We will have multiple VDOMs on the main Fortigate with matching VDOMs on the branch campus Fortigates (employees, residents, clients). This traffic should remain separated, so we're using EMAC VLANs and assigning each EMAC VLAN to the appropriate VDOM. Then the default route for the branch employee VDOM is the employee VDOM at the main site, the route for the branch resident VDOM is the main resident VDOM, etc. If you've done a design like this before let us know your experience.
