SD-WAN on the FortiGate: what you will learn and the big picture
What you will learn in this module. You will learn how FortiGate SD-WAN bundles several internet or private links into one logical interface, measures their quality, and steers each type of traffic over the best link. You will build members and zones, health checks and SLA targets, SD-WAN rules, and understand the implicit rule, load balancing and failover. These are the SD-WAN objectives of the Fortinet NSE 4 / FortiOS 7.6 Administrator exam.
Note. Honest note about the simulator. The SD-WAN core runs in the simulator labs of this module: zones, members, health checks, SLA targets, rules, failover and diagnose sys sdwan. Try Two ISPs become one SD-WAN zone, A performance SLA and failover when ISP-A degrades and the ticket lab Half the users cannot browse. Overlay IPsec, ADVPN, FortiManager, application-control steering, passive measurement and traffic shaping are reference-only: they are taught in the later fsd modules but are not modelled. The routing parts that SD-WAN builds on (routing table, floating routes, debug flow) are also real labs in nse4-routing. For hands-on policy routing and tracking concepts use enarsi-pbr-vrf-bfd; for Cisco's different SD-WAN architecture see encor-sdwan-sda.
Prerequisites. Finish nse4-routing first: you must be comfortable with the routing table, distance, floating routes and firewall policies per interface.
Analogy: a delivery company with a live traffic app
A floating static route is like telling every driver: "always take the highway; if it is closed, take the village road". It cannot tell that the highway is open but jammed, and it treats an urgent medicine parcel and a catalogue the same. SD-WAN is a dispatcher with a live traffic app. It measures every road all the time (loss, delay, jitter), knows what each parcel is, and says: "medicine over the fastest road, catalogues over the cheap road, and if a road gets bad, switch."
One logical interface (the zone) hides several physical links. Rules decide which member carries which traffic, health checks supply the measurements.
The five building blocks
| Block | What it is |
|---|---|
| Member | One link (interface and gateway) that joins SD-WAN. |
| Zone | A group of members; the object that routes and policies point to. |
| Health check | A probe (ping, DNS and so on) that measures each member. |
| SLA | The thresholds that decide whether a member is good enough. |
| Rule (service) | Which traffic goes over which members and by which strategy. |
Traffic that matches no rule falls to the implicit rule, which uses the normal routing table and a load-balancing mode. The next chapters build each block in order.
Why SD-WAN and not floating routes
- Failover on quality, not only on a dead interface.
- Per-application steering: voice on the best link, backups on the cheap one.
- Use of all links at once instead of leaving the backup idle.
- One policy for the zone instead of one per link.
Common mistake. Believing SD-WAN needs a special licence or a controller. On a FortiGate it is a built-in feature of FortiOS configured on each unit; FortiManager is optional for managing many sites.
Exam trap. SD-WAN is a FortiOS feature configured under config system sdwan. Policies and routes refer to the SD-WAN zone, not to the member interfaces.
The backup link that was never used
A retailer paid for two 100 Mbit links per store but used one; the second sat idle until an outage. After moving to SD-WAN, store cards and cloud tills used the primary while software updates and guest Wi-Fi used the second link. The same money bought double the capacity.
Lesson: SD-WAN turns an idle backup into usable capacity.
"What problem does SD-WAN solve compared with floating static routes?"
A floating route reacts only to interface state and sends everything over one link. SD-WAN measures loss, latency and jitter per link with health checks, steers each application over the best link by rule, can use all links at once, and gives one zone object for routes and policies.
Key takeaways
- SD-WAN bundles links (members) into a zone and steers traffic by measured quality.
- Building blocks: members, zone, health check, SLA, rules, implicit rule.
- This module has three simulator labs: build the zone, add an SLA with failover, and fix a ticket.
- Practise the routing foundations in nse4-routing.