Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • SD-WAN Deployment for MSSPs

    Home FortiGate / FortiOS 6.4.0 SD-WAN Deployment for MSSPs
    6.4.0
    7.4.0
    7.2.0
    7.0.0
    6.4.0

    Configuring Edge devices with SD-WAN

    Configuring Edge devices with SD-WAN

    As can be seen, no configuration change was required on the Edge devices when switching from a single-regional to a multi-regional deployment.

    The Edge devices do not require any configuration related to the remote regions. They only learn the route summaries from the remote regions, which allows them to send traffic via their local Hubs.

    The same is true for SD-WAN configuration. The overlay selection is done locally by the originating Edge device, and the overlay stickiness policy routes on the Hubs ensure that this selection is preserved end-to-end.

    Note

    Depending on the requirements and on the nature of the inter-regional communication, more complex deployments may be possible. These include, but are not limited to:

    • Using SD-WAN rules on the Hubs to select the best path towards the remote Hub, rather than extending the overlay stickiness policy across the regions. This implies that the type of the overlay might change along the path, if the network conditions justify that.
    • Extending ADVPN across the regions to allow direct ADVPN shortcuts between the Edge devices from different regions. Note that this feature significantly complicates the routing design, and hence it must be used with care.

    These types of deployment are outside the scope of this document.
    Previous
    Next

    Configuring Edge devices with SD-WAN

    Configuring Edge devices with SD-WAN

    As can be seen, no configuration change was required on the Edge devices when switching from a single-regional to a multi-regional deployment.

    The Edge devices do not require any configuration related to the remote regions. They only learn the route summaries from the remote regions, which allows them to send traffic via their local Hubs.

    The same is true for SD-WAN configuration. The overlay selection is done locally by the originating Edge device, and the overlay stickiness policy routes on the Hubs ensure that this selection is preserved end-to-end.

    Note

    Depending on the requirements and on the nature of the inter-regional communication, more complex deployments may be possible. These include, but are not limited to:

    • Using SD-WAN rules on the Hubs to select the best path towards the remote Hub, rather than extending the overlay stickiness policy across the regions. This implies that the type of the overlay might change along the path, if the network conditions justify that.
    • Extending ADVPN across the regions to allow direct ADVPN shortcuts between the Edge devices from different regions. Note that this feature significantly complicates the routing design, and hence it must be used with care.

    These types of deployment are outside the scope of this document.
    Previous
    Next