
Image by: Brett Sayles
Table of contents
SD-WAN revolution in modern networking
Did you know 74% of enterprises now prioritize cloud connectivity as their primary WAN objective? Traditional router-centric approaches simply can’t deliver the agility modern businesses require. FortiOS-powered Software-Defined Wide Area Networking (SD-WAN) transforms legacy infrastructure into an intelligent, application-aware fabric. This technical walkthrough guides network administrators through implementing Fortinet’s latest FortiOS SD-WAN capabilities – from initial interface configuration to advanced traffic engineering for SaaS applications. You’ll master the sequence for defining health checks, building performance-based routing rules, and implementing real-time monitoring – all critical for maintaining business continuity as organizations adopt software-defined architectures.
Pre-deployment checklist and topology planning
Before touching the CLI, document your current WAN characteristics. Inventory all physical interfaces (ISP links, MPLS circuits), VPN tunnels, and bandwidth allocations. Determine critical applications needing prioritization – Microsoft 365, Salesforce, or custom SaaS platforms. FortiOS requires:
- Minimum FortiOS 7.0.5 (7.4 recommended for full feature set)
- Dedicated interfaces for each WAN connection
- Public IPs for health-check destinations
- Baseline traffic metrics (peak utilization, latency thresholds)
“Document asymmetric routing paths before implementation to avoid blackhole scenarios during cutover,” advises network architect Jane Ellis of Forrester.
Create a rollout plan with maintenance windows. Test failover behavior using non-production interfaces first. Remember: SD-WAN implementation impacts firewall policies and NAT rules – update them to reference SD-WAN zones instead of physical interfaces.
Configuring interface members and SD-WAN zones
Begin by defining SD-WAN members under Network > SD-WAN > Interface Members. Add each physical or virtual interface participating in your SD-WAN fabric. For dual-WAN FortiGate 100F models:
- Enable “Software Switch” on port1 and port2
- Assign both interfaces to a new SD-WAN zone (e.g., “WAN_Zone”)
- Set cost metrics based on bandwidth (e.g., 50Mbps link = cost 10, 100Mbps = cost 5)
Zones group links with similar properties. Create separate zones for MPLS circuits, broadband links, and LTE failover. Critical note: Interface members must have gateway monitoring enabled for health checks to function. Use this template for zone properties:
| Zone type | Security profiles | Max links active | Use case |
|---|---|---|---|
| Secure_MPLS | Full inspection | 2 | Sensitive financial data |
| Broadband | AV only | 4 | Guest traffic/backups |
| LTE_Failover | No inspection | 1 | Emergency connectivity |
Establishing performance SLAs and health monitoring
Performance SLAs drive intelligent path selection. Navigate to SD-WAN > Performance SLAs to create probes measuring:
- Latency (critical for VoIP)
- Jitter (threshold: 30ms max)
- Packet loss (target: <0.5%)
- MOS scores for voice quality
Best practice: Configure at least three geographically dispersed ITU-compliant servers per SLA. For Microsoft 365 prioritization, use Microsoft’s recommended endpoints:
- Create “O365_SLA” with protocol HTTP
- Target URL: outlook.office365.com
- Set sensitivity to “High” (measurements every 500ms)
Critical parameters include timeout (2000ms), diffserv code (CS6 for priority), and threshold violations required before link demotion (default: 3). Testing methodology matters – ICMP probes suffice for basic health, but HTTP/S mimics actual application behavior.
Advanced traffic shaping for SaaS optimization
With cloud adoption accelerating, shaping SaaS traffic prevents bandwidth starvation. Implement application-aware policies in three stages:
“FortiOS 7.4 introduces AI-driven SaaS identification – use it to auto-classify 8000+ applications without manual signatures,” notes Fortinet Technical Account Manager David Reed.
- Create traffic shaping policy under Policy & Objects > Traffic Shaping
- Set guaranteed bandwidth for critical apps (e.g., Salesforce=15Mbps minimum)
- Apply application control signatures for granular identification
- Enable “Priority Queuing” with DSCP tagging for Teams/Zoom
Leverage per-IP shaping for high-density branches. Combine with SD-WAN rules to route shaped traffic through preferred links. For VoIP, implement LLQ (Low Latency Queuing) to guarantee:
- Voice: 256Kbps guaranteed
- Video conferencing: 1.5Mbps
- Best-effort data: Burstable remainder
Building intelligent SD-WAN rules
SD-WAN rules enforce business intent. Go to SD-WAN > Rules and build policies sequentially:
- High-priority rules first: VoIP and critical SaaS
- Application-based rules: O365, SAP, custom TCP ports
- Default catch-all rule: Balance across all links
For Microsoft 365 traffic:
Source: LAN_Subnets Destination: O365_Microsoft SLA: O365_SLA (require MOS > 4.0) Strategy: Lowest cost + SLA compliance DSCP Tag: CS3
Prioritize active-active topologies for critical apps while using cost-effective links for backups. Test rules using the “diag sys sdwan service” command to verify path selection logic. Remember: Rules higher in the list override lower ones – order matters exponentially.
Operational monitoring and troubleshooting
FortiOS delivers comprehensive analytics via SD-WAN > Performance Monitor. Key metrics to track:
- Per-link SLA compliance rates (target: 99.9%)
- Application-specific latency distribution
- Automatic failover history
- QoE (Quality of Experience) heatmaps
Diagnose issues with command-line tools:
- diag sys sdwan health-check: Verify SLA probe results
- get system performance sla: View real-time path metrics
- diagnose debug application fnbamd -1: Deep-dive session distribution
Integrate with FortiAnalyzer for historical trend analysis. According to Gartner’s latest report, organizations using integrated SD-WAN analytics resolve outages 67% faster. Set SNMP traps for SLA threshold breaches and automate alerts for sustained packet loss >2%.
Frequently asked questions
Can I mix MPLS and internet links in the same SD-WAN zone?
Yes, but define separate SLA metrics for each link type. MPLS typically has lower latency but higher cost – assign appropriate weights using the “Cost” parameter in interface settings.
How many performance SLAs should I configure?
Start with 3-5 strategic SLAs: One for generic internet health, another for key SaaS applications, and specialized probes for VoIP. Excessive SLAs increase overhead – find balance between granularity and system load.
Does SD-WAN work with VPN overlays?
Absolutely. Treat IPsec or SSL VPN tunnels as SD-WAN members. Health checks run over encrypted tunnels to measure true application performance. Configure VPN-specific SLA thresholds compensating for encryption overhead.
How does FortiOS handle asymmetric routing?
FortiGate’s session-aware steering maintains path consistency using session tuples. Enable “Symmetric Routing” in SD-WAN settings and ensure stateful inspection policies are applied consistently across links.
Conclusion
This technical walkthrough demonstrates how FortiOS transforms disparate WAN connections into an intelligent SD-WAN fabric. By methodically implementing interface zones, performance SLAs, traffic shaping, and application-steering rules, network administrators achieve unprecedented control over business-critical traffic. Remember: Continuous monitoring via FortiOS dashboards ensures sustained optimization. To explore advanced SD-WAN capabilities, see our implementation case studies. Begin with non-critical traffic, validate SLA behaviors, and progressively migrate applications – your optimized cloud-ready network awaits.
