{"id":1398,"date":"2026-09-10T16:01:13","date_gmt":"2026-09-10T10:31:13","guid":{"rendered":"https:\/\/networkfix.in\/uncategorized\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/"},"modified":"2026-09-14T04:31:02","modified_gmt":"2026-09-13T23:01:02","slug":"fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin","status":"publish","type":"post","link":"https:\/\/networkfix.in\/en\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/","title":{"rendered":"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing"},"content":{"rendered":"<p>Single ISP connections introduce a critical single point of failure for enterprise branch offices. When an ISP outage occurs, cloud application access, SaaS tools, and VoIP communications stall instantly. Implementing a proper <strong>FortiGate SD-WAN configuration<\/strong> solves this problem by combining multiple WAN links into a unified virtual interface. This architecture delivers automated link monitoring, dynamic path selection, and graceful failover.<\/p>\n<p>In this comprehensive guide, you will configure a dual-ISP FortiGate SD-WAN deployment. You will set up performance SLA health checks, custom routing rules, and dynamic failover parameters using both FortiOS GUI and CLI methods.<\/p>\n<h2>Real-Life Scenario<\/h2>\n<p>Apex Logistics operates a regional distribution branch. The site depends heavily on cloud ERP applications and cloud-hosted VoIP services. A WAN outage immediately halts warehouse fulfillment operations.<\/p>\n<p>To eliminate single-point-of-failure risks, Apex Logistics contracted two distinct internet service providers:<\/p>\n<ul>\n<li><strong>ISP-1 (Primary Fiber):<\/strong> Dedicated 200 Mbps symmetric fiber connection with low latency.<\/li>\n<li><strong>ISP-2 (Secondary Cable):<\/strong> Asymmetric 500\/50 Mbps broadband connection with variable latency.<\/li>\n<\/ul>\n<p>The business requirements specify:<\/p>\n<ol>\n<li>Business-critical cloud traffic must prefer ISP-1 as long as latency stays under 50ms and packet loss stays below 1%.<\/li>\n<li>If ISP-1 breaches SLA thresholds or fails completely, critical traffic must seamlessly switch to ISP-2.<\/li>\n<li>General web browsing must load balance across both ISP links to optimize total bandwidth utilization.<\/li>\n<\/ol>\n<h2>Lab Topology<\/h2>\n<p>The following ASCII diagram illustrates the physical and logical layout of the branch network.<\/p>\n<pre>\n                        +--------------------+\n                        |  Internet Probes   |\n                        | 203.0.113.1 \/ .2   |\n                        +---------+----------+\n                                  |\n               +------------------+------------------+\n               |                                     |\n        [ Primary ISP-1 ]                     [ Secondary ISP-2 ]\n         GW: 192.0.2.1                         GW: 198.51.100.1\n               |                                     |\n        192.0.2.2\/24                          198.51.100.2\/24\n        +------+-------------------------------------+------+\n        | port1                                       port2 |\n        |                                                   |\n        |              FortiGate Firewall                   |\n        |              (SD-WAN Controller)                  |\n        |                                                   |\n        |                      port3                        |\n        +------------------------+--------------------------+\n                                 |\n                            10.0.1.1\/24\n                                 |\n                        +--------+---------+\n                        |   Branch LAN    |\n                        |  10.0.1.0\/24    |\n                        +-----------------+\n<\/pre>\n<h2>Example Addressing and Objects<\/h2>\n<p>The network parameters below are used throughout this tutorial. All public IPv4 addresses use RFC 5737 test address ranges. Replace these values with your actual production ISP parameters.<\/p>\n<table>\n<thead>\n<tr>\n<th>Object \/ Interface<\/th>\n<th>Identifier \/ Value<\/th>\n<th>Purpose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>ISP-1 Interface<\/td>\n<td><code>port1<\/code><\/td>\n<td>Primary WAN interface (Fiber)<\/td>\n<\/tr>\n<tr>\n<td>ISP-1 IP \/ Gateway<\/td>\n<td><code>192.0.2.2\/24<\/code> \/ <code>192.0.2.1<\/code><\/td>\n<td>LAB\/EXAMPLE Primary WAN addressing<\/td>\n<\/tr>\n<tr>\n<td>ISP-2 Interface<\/td>\n<td><code>port2<\/code><\/td>\n<td>Secondary WAN interface (Cable)<\/td>\n<\/tr>\n<tr>\n<td>ISP-2 IP \/ Gateway<\/td>\n<td><code>198.51.100.2\/24<\/code> \/ <code>198.51.100.1<\/code><\/td>\n<td>LAB\/EXAMPLE Secondary WAN addressing<\/td>\n<\/tr>\n<tr>\n<td>LAN Interface<\/td>\n<td><code>port3<\/code><\/td>\n<td>Branch local network gateway (<code>10.0.1.1\/24<\/code>)<\/td>\n<\/tr>\n<tr>\n<td>SD-WAN Zone<\/td>\n<td><code>Virtual-WAN-Link<\/code> (or <code>Internet-Zone<\/code>)<\/td>\n<td>Logical grouping object for WAN interfaces<\/td>\n<\/tr>\n<tr>\n<td>Health Check Targets<\/td>\n<td><code>203.0.113.1<\/code>, <code>203.0.113.2<\/code><\/td>\n<td>LAB\/EXAMPLE external SLA probe servers<\/td>\n<\/tr>\n<tr>\n<td>LAN Subnet Object<\/td>\n<td><code>LAN_Subnet<\/code> (<code>10.0.1.0\/24<\/code>)<\/td>\n<td>Firewall address object representing internal clients<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Prerequisites<\/h2>\n<p>Before configuring SD-WAN in FortiOS, verify that your environment meets the following conditions:<\/p>\n<ul>\n<li><strong>Interface Disassociation:<\/strong> Egress interfaces (<code>port1<\/code> and <code>port2<\/code>) must not be referenced in existing static routes, security policies, virtual IPs, or IPsec tunnels. FortiOS prevents adding interfaces to an SD-WAN zone if active dependencies exist.<\/li>\n<li><strong>System Version:<\/strong> FortiOS 7.0 or higher is installed. GUI menu paths and CLI structures in this article reflect FortiOS 7.x standards.<\/li>\n<li><strong>Administrative Access:<\/strong> You possess Super Admin privileges via Read-Write CLI and Web UI access.<\/li>\n<\/ul>\n<h2>Step-by-Step GUI FortiGate SD-WAN Configuration<\/h2>\n<h3>Step 1: Create the SD-WAN Zone and Add Members<\/h3>\n<p>In modern FortiOS releases, SD-WAN members reside inside SD-WAN zones. Grouping links into zones simplifies policy creation and centralizes interface management.<\/p>\n<ol>\n<li>Navigate to <strong>Network &gt; SD-WAN<\/strong>.<\/li>\n<li>Select the <strong>SD-WAN Zones<\/strong> tab and click <strong>Create New &gt; SD-WAN Zone<\/strong>.<\/li>\n<li>Enter <code>Internet-Zone<\/code> in the Name field and click <strong>OK<\/strong>.<\/li>\n<li>Select the <strong>SD-WAN Members<\/strong> tab and click <strong>Create New<\/strong>.<\/li>\n<li>Set <strong>Interface<\/strong> to <code>port1<\/code>.<\/li>\n<li>Set <strong>SD-WAN Zone<\/strong> to <code>Internet-Zone<\/code>.<\/li>\n<li>Set <strong>Gateway<\/strong> to <code>192.0.2.1<\/code>.<\/li>\n<li>Click <strong>OK<\/strong>.<\/li>\n<li>Click <strong>Create New<\/strong> again to add the secondary member:\n<ul>\n<li>Set <strong>Interface<\/strong> to <code>port2<\/code>.<\/li>\n<li>Set <strong>SD-WAN Zone<\/strong> to <code>Internet-Zone<\/code>.<\/li>\n<li>Set <strong>Gateway<\/strong> to <code>198.51.100.1<\/code>.<\/li>\n<li>Click <strong>OK<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3>Step 2: Configure Performance SLA (Health Check)<\/h3>\n<p>Performance SLAs send active probe packets to target destinations over all SD-WAN members. The FortiGate measures latency, jitter, and packet loss to determine if a link meets operational requirements.<\/p>\n<ol>\n<li>Navigate to <strong>Network &gt; SD-WAN<\/strong> and select the <strong>Performance SLA<\/strong> tab.<\/li>\n<li>Click <strong>Create New<\/strong>.<\/li>\n<li>Name the SLA object <code>SLA_Internet_Check<\/code>.<\/li>\n<li>Set <strong>Protocol<\/strong> to <code>Ping<\/code> (or <code>HTTP<\/code> based on application requirements).<\/li>\n<li>In the <strong>Server<\/strong> fields, add probe IP addresses: <code>203.0.113.1<\/code> and <code>203.0.113.2<\/code>.<\/li>\n<li>Under <strong>Participants<\/strong>, choose <strong>All SD-WAN Members<\/strong>.<\/li>\n<li>Enable <strong>SLA Targets<\/strong> and click <strong>Create New<\/strong>:\n<ul>\n<li>Set <strong>Latency Threshold<\/strong> to <code>50<\/code> ms.<\/li>\n<li>Set <strong>Jitter Threshold<\/strong> to <code>10<\/code> ms.<\/li>\n<li>Set <strong>Packet Loss Threshold<\/strong> to <code>1<\/code> %.<\/li>\n<\/ul>\n<\/li>\n<li>Enable <strong>Update static route<\/strong>. This setting removes dead links from the routing table automatically when probes fail.<\/li>\n<li>Click <strong>OK<\/strong>.<\/li>\n<\/ol>\n<h3>Step 3: Create SD-WAN Steering Rules<\/h3>\n<p>SD-WAN Rules dictate how FortiOS evaluates outbound network sessions and selects member interfaces.<\/p>\n<ol>\n<li>Navigate to <strong>Network &gt; SD-WAN<\/strong> and select the <strong>SD-WAN Rules<\/strong> tab.<\/li>\n<li>Click <strong>Create New<\/strong> to build the primary SLA-driven rule:\n<ul>\n<li><strong>Rule Name:<\/strong> <code>Critical_SaaS_Traffic<\/code><\/li>\n<li><strong>Source:<\/strong> Address object <code>LAN_Subnet<\/code><\/li>\n<li><strong>Destination:<\/strong> Select specific SaaS addresses or <code>all<\/code><\/li>\n<li><strong>Strategy:<\/strong> Select <strong>Lowest Cost (SLA)<\/strong> or <strong>Best Quality<\/strong><\/li>\n<li><strong>Interface Preference:<\/strong> Select <code>port1<\/code> first, then <code>port2<\/code><\/li>\n<li><strong>Required SLA Target:<\/strong> Select <code>SLA_Internet_Check<\/code> with target <code>#1<\/code><\/li>\n<\/ul>\n<\/li>\n<li>Click <strong>OK<\/strong>.<\/li>\n<\/ol>\n<p><em>Note: FortiOS processes SD-WAN rules from top to bottom. If traffic does not match a custom rule, it falls back to the default implicit strategy rule.<\/em><\/p>\n<h3>Step 4: Configure the Default Static Route<\/h3>\n<p>A static default route must point traffic to the unified SD-WAN Zone instead of individual physical interfaces.<\/p>\n<ol>\n<li>Navigate to <strong>Network &gt; Static Routes<\/strong>.<\/li>\n<li>Click <strong>Create New<\/strong>.<\/li>\n<li>Set <strong>Destination<\/strong> to <code>0.0.0.0\/0<\/code>.<\/li>\n<li>Set <strong>Interface<\/strong> to <code>Internet-Zone<\/code>.<\/li>\n<li>Leave Gateway Address blank (gateways were already defined inside SD-WAN member properties).<\/li>\n<li>Click <strong>OK<\/strong>.<\/li>\n<\/ol>\n<h3>Step 5: Define Egress Firewall Policy<\/h3>\n<p>A single firewall policy handles traffic passing from internal networks out through the SD-WAN zone.<\/p>\n<ol>\n<li>Navigate to <strong>Policy &amp; Objects &gt; Firewall Policy<\/strong>.<\/li>\n<li>Click <strong>Create New<\/strong>.<\/li>\n<li>Name the policy <code>LAN_To_SDWAN_Internet<\/code>.<\/li>\n<li>Set <strong>Incoming Interface<\/strong> to <code>port3<\/code> (LAN).<\/li>\n<li>Set <strong>Outgoing Interface<\/strong> to <code>Internet-Zone<\/code>.<\/li>\n<li>Set <strong>Source<\/strong> to <code>LAN_Subnet<\/code>.<\/li>\n<li>Set <strong>Destination<\/strong> to <code>all<\/code>.<\/li>\n<li>Set <strong>Service<\/strong> to <code>ALL<\/code>.<\/li>\n<li>Ensure <strong>NAT<\/strong> is enabled and set to <strong>Use Outgoing Interface Address<\/strong>.<\/li>\n<li>Click <strong>OK<\/strong>.<\/li>\n<\/ol>\n<h2>FortiOS CLI Configuration<\/h2>\n<p>For automated deployments or CLI-focused administrators, the following commands execute the exact equivalent configuration.<\/p>\n<h3>1. Define SD-WAN Zone and Members<\/h3>\n<pre><code>config system sdwan\n    set status enable\n    config zone\n        edit \"Internet-Zone\"\n    next\n    end\n    config members\n        edit 1\n            set interface \"port1\"\n            set zone \"Internet-Zone\"\n            set gateway 192.0.2.1\n        next\n        edit 2\n            set interface \"port2\"\n            set zone \"Internet-Zone\"\n            set gateway 198.51.100.1\n        next\n    end\nend\n<\/code><\/pre>\n<h3>2. Configure Performance SLA Health Check<\/h3>\n<pre><code>config system sdwan\n    config health-check\n        edit \"SLA_Internet_Check\"\n            set server \"203.0.113.1\" \"203.0.113.2\"\n            set members 1 2\n            config sla\n                edit 1\n                    set latency-threshold 50\n                    set jitter-threshold 10\n                    set packetloss-threshold 1\n                next\n            end\n        next\n    end\nend\n<\/code><\/pre>\n<h3>3. Create Service Rules (Traffic Steering)<\/h3>\n<pre><code>config system sdwan\n    config service\n        edit 1\n            set name \"Critical_SaaS_Traffic\"\n            set mode priority\n            set src \"LAN_Subnet\"\n            set dst \"all\"\n            set health-check \"SLA_Internet_Check\"\n            set sla-compare-method latency\n            set priority-members 1 2\n        next\n    end\nend\n<\/code><\/pre>\n<h3>4. Configure Static Default Route<\/h3>\n<pre><code>config router static\n    edit 1\n        set sdwan-zone \"Internet-Zone\"\n    next\nend\n<\/code><\/pre>\n<h3>5. Configure Firewall Policy and Address Objects<\/h3>\n<pre><code>config firewall address\n    edit \"LAN_Subnet\"\n        set subnet 10.0.1.0 255.255.255.0\n    next\nend\n\nconfig firewall policy\n    edit 1\n        set name \"LAN_To_SDWAN_Internet\"\n        set srcintf \"port3\"\n        set dstintf \"Internet-Zone\"\n        set action accept\n        set srcaddr \"LAN_Subnet\"\n        set dstaddr \"all\"\n        set schedule \"always\"\n        set service \"ALL\"\n        set nat enable\n    next\nend\n<\/code><\/pre>\n<h2>How the Traffic Flows<\/h2>\n<p>Understanding internal packet handling ensures accurate design and efficient troubleshooting. FortiOS processes outbound internet traffic through distinct operational stages:<\/p>\n<ol>\n<li><strong>Ingress Interface Evaluation:<\/strong> A frame arrives on <code>port3<\/code> from an internal IP address (e.g., <code>10.0.1.50<\/code>).<\/li>\n<li><strong>Routing Table Route Lookup:<\/strong> FortiOS inspects its FIB (Forwarding Information Base) and identifies the matching static route <code>0.0.0.0\/0<\/code> pointing to <code>Internet-Zone<\/code>.<\/li>\n<li><strong>SD-WAN Service Rule Evaluation:<\/strong> The firewall scans SD-WAN rules sequentially starting at rule ID 1:\n<ul>\n<li>If parameters match rule criteria (source <code>LAN_Subnet<\/code>, destination <code>all<\/code>), FortiOS evaluates member health.<\/li>\n<li>The SD-WAN engine checks the live state of <code>SLA_Internet_Check<\/code>.<\/li>\n<li>If <code>port1<\/code> meets the latency target (&lt;50ms) and packet loss target (&lt;1%), FortiOS assigns <code>port1<\/code> as the outbound egress interface.<\/li>\n<li>If <code>port1<\/code> violates SLA targets or suffers a link outage, FortiOS automatically routes the session via <code>port2<\/code>.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Firewall Policy Matching:<\/strong> FortiOS matches the session against firewall policy ID 1 (<code>port3<\/code> to <code>Internet-Zone<\/code>).<\/li>\n<li><strong>Source NAT Application:<\/strong> FortiOS translates the source IP from <code>10.0.1.50<\/code> to the public interface IP of the egress member (e.g., <code>192.0.2.2<\/code> for <code>port1<\/code> or <code>198.51.100.2<\/code> for <code>port2<\/code>).<\/li>\n<li><strong>Session Creation:<\/strong> FortiOS writes the connection into the state table. Existing established flows remain anchored until closed, while new sessions immediately follow updated steering decisions.<\/li>\n<\/ol>\n<h2>Verification<\/h2>\n<p>After completing your configuration, execute the following diagnostic commands from the FortiGate CLI to verify operational states.<\/p>\n<h3>1. Verify Member Interface Status<\/h3>\n<p>Check the status and status flag values of physical SD-WAN links:<\/p>\n<pre><code>diagnose sys sdwan member<\/code><\/pre>\n<p><em>Expected Output Proves:<\/em> Confirms whether <code>port1<\/code> and <code>port2<\/code> are logically active, displays gateway health, and validates assigned zone memberships.<\/p>\n<h3>2. Verify Performance SLA State<\/h3>\n<p>Inspect active probing statistics for latency, jitter, packet loss, and SLA pass\/fail status:<\/p>\n<pre><code>diagnose sys sdwan health-check<\/code><\/pre>\n<p><em>Expected Output Proves:<\/em> Verifies probe response times from <code>203.0.113.1<\/code> and displays whether links pass or fail defined SLA criteria.<\/p>\n<h3>3. Verify SD-WAN Rule Steering Decisions<\/h3>\n<p>Confirm which WAN interface is selected for specific rules:<\/p>\n<pre><code>diagnose sys sdwan service<\/code><\/pre>\n<p><em>Expected Output Proves:<\/em> Displays real-time interface rankings for rules, ensuring the primary link receives primary flow assignments.<\/p>\n<h2>Troubleshooting<\/h2>\n<p>Use a structured, repeatable troubleshooting workflow when link failovers do not execute cleanly:<\/p>\n<pre>\n  [ Check Link &amp; Gateway ] ---&gt; [ Inspect Health Check SLA ] ---&gt; [ Debug Packet Flow Engine ]\n<\/pre>\n<h3>Step 1: Check Egress Gateway Reachability<\/h3>\n<p>Determine if physical interface links can ping their respective default gateways directly:<\/p>\n<pre><code>execute ping-options source 192.0.2.2\nexecute ping 192.0.2.1\n\nexecute ping-options source 198.51.100.2\nexecute ping 198.51.100.1\n<\/code><\/pre>\n<h3>Step 2: Trace Active Session Pathing<\/h3>\n<p>When sessions do not pick the proper WAN path, execute packet trace debugging directly within the firewall engine.<\/p>\n<p><strong>CAUTION:<\/strong> Interactive flow traces create CPU overhead. Always set restrictive source address filters and stop trace logs immediately after capturing traffic.<\/p>\n<pre><code>diagnose debug reset\ndiagnose debug flow filter saddr 10.0.1.50\ndiagnose debug flow show function-name enable\ndiagnose debug flow trace start 10\ndiagnose debug enable\n<\/code><\/pre>\n<p>Review the trace output to identify matching policy IDs, SD-WAN rules, and final egress selection.<\/p>\n<p><strong>Cleanup Commands (Required):<\/strong><\/p>\n<pre><code>diagnose debug disable\ndiagnose debug reset\n<\/code><\/pre>\n<h3>Symptom Matrix<\/h3>\n<table>\n<thead>\n<tr>\n<th>Observed Symptom<\/th>\n<th>Likely Cause<\/th>\n<th>Recommended Action<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Traffic uses only <code>port1<\/code> even when <code>port1<\/code> goes down.<\/td>\n<td>A legacy static route bound directly to <code>port1<\/code> remains active in the routing table.<\/td>\n<td>Delete direct interface static routes in <strong>Network &gt; Static Routes<\/strong>. Ensure default route points to the SD-WAN Zone.<\/td>\n<\/tr>\n<tr>\n<td>Traffic drops instantly when <code>port1<\/code> fails.<\/td>\n<td>Firewall policy lists <code>port1<\/code> explicitly as Outgoing Interface instead of the SD-WAN Zone.<\/td>\n<td>Edit Policy ID 1 and set destination interface to <code>Internet-Zone<\/code>.<\/td>\n<\/tr>\n<tr>\n<td>Performance SLA reports 100% loss across all links.<\/td>\n<td>Upstream firewalls or probe targets (<code>203.0.113.1<\/code>) block ICMP pings.<\/td>\n<td>Change SLA probe protocol from Ping to HTTP\/HTTPS or update target IP addresses to public DNS servers.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Common Mistakes<\/h2>\n<ul>\n<li><strong>Leaving Direct Static Routes Active:<\/strong> Retaining old static routes assigned to physical interfaces overrides SD-WAN decisions. Static default routes must target the SD-WAN zone exclusively.<\/li>\n<li><strong>Forgetting Outgoing NAT:<\/strong> Unchecked NAT settings on outgoing firewall policies cause packets with internal private addresses (e.g., <code>10.0.1.50<\/code>) to reach public networks, where upstream ISPs drop them.<\/li>\n<li><strong>Using Unreliable SLA Target Hosts:<\/strong> Using single target targets for health checks risks unnecessary failover if that target host reboots. Always list at least two distinct public probe targets.<\/li>\n<li><strong>Overly Aggressive Probe Thresholds:<\/strong> Setting health check thresholds too tight (e.g., 5ms latency threshold) triggers continuous route flapping during minor network fluctuations.<\/li>\n<\/ul>\n<h2>Production Considerations<\/h2>\n<p>When deploying FortiGate SD-WAN in enterprise environments, account for these critical production practices:<\/p>\n<ul>\n<li><strong>Probing Overhead &amp; Target Choice:<\/strong> Select redundant, highly available public target IP addresses (such as tier-1 DNS providers or enterprise infrastructure hosts). Ensure targets support continuous ICMP or HTTP probes without rate limiting.<\/li>\n<li><strong>Session Bouncing &amp; Hold Down Timers:<\/strong> Configure flap-guard and hold-down timers inside SLA health checks to prevent link instability from cycling sessions back and forth repeatedly.<\/li>\n<li><strong>Overlay Bandwidth Configuration:<\/strong> Enter accurate inbound and outbound bandwidth values under SD-WAN member interface settings to allow proper percentage-based dynamic load balancing.<\/li>\n<li><strong>Adaptation of Values:<\/strong> Public IP addresses, interface names, thresholds, and routing objects shown in tutorials are for lab demonstration. Always adapt IP subnets and physical member designs to your real network landscape.<\/li>\n<\/ul>\n<h2>Related FortiGate Guides<\/h2>\n<ul>\n<li><a href=\"\/tutorials\/fortinet\/fortigate-policy-route-configuration-with-dual-isp-real-life-examples\/\">FortiGate policy routing with dual ISP examples<\/a><\/li>\n<li><a href=\"\/tutorials\/fortinet\/fortigate-high-availability-active-passive-configuration-and-failover\/\">FortiGate HA configuration and failover testing<\/a><\/li>\n<li><a href=\"\/tutorials\/fortinet\/fortigate-session-troubleshooting-with-flow-debug-sessions-and-logs\/\">FortiGate session troubleshooting<\/a><\/li>\n<li><a href=\"\/tutorials\/fortinet\/fortigate-ldap-authentication-with-active-directory-configuration-and\/\">FortiGate LDAP with Active Directory<\/a><\/li>\n<\/ul>\n<h2>Summary<\/h2>\n<p>A properly executed <strong>FortiGate SD-WAN configuration<\/strong> transforms redundant internet connections into an intelligent, high-availability network asset. By placing ISP interfaces inside a single SD-WAN zone, establishing proactive Performance SLAs, and steering application traffic based on latency and loss thresholds, you guarantee link failure resilience and optimize user access to cloud resources.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn FortiGate SD-WAN configuration with a practical real-life example, step-by-step configuration, verification and troubleshooting.<\/p>","protected":false},"author":2,"featured_media":1397,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","rank_math_title":"","rank_math_description":"","rank_math_focus_keyword":"","_dpc-meta-title":"","_dpc-meta-description":"","_dpc-keyword":""},"categories":[4],"tags":[137,29,41,1158,44,43,1159],"class_list":["post-1398","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fortinet","tag-advanced","tag-firewall-tutorial","tag-fortigate","tag-fortigate-sd-wan-configuration","tag-fortinet","tag-fortios","tag-sd-wan"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.2 (Yoast SEO v28.6) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>FortiGate SD-WAN Dual ISP Failover and Load Balancing<\/title>\n<meta name=\"description\" content=\"Configure FortiGate SD-WAN for dual ISP failover and load balancing with health checks, rules, routing verification and troubleshooting.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/networkfix.in\/en\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing\" \/>\n<meta property=\"og:description\" content=\"Configure FortiGate SD-WAN for dual ISP failover and load balancing with health checks, rules, routing verification and troubleshooting.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/networkfix.in\/en\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/\" \/>\n<meta property=\"og:site_name\" content=\"NetworkFix\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-10T10:31:13+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-13T23:01:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/09\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ajay Yadav\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ajay Yadav\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/\"},\"author\":{\"name\":\"Ajay Yadav\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/#\\\/schema\\\/person\\\/dac05d268c126277e74b684c5239d344\"},\"headline\":\"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing\",\"datePublished\":\"2026-09-10T10:31:13+00:00\",\"dateModified\":\"2026-09-13T23:01:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/\"},\"wordCount\":1691,\"publisher\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/#\\\/schema\\\/person\\\/28c6fb08b80eeae506b96250db4f30f0\"},\"image\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg\",\"keywords\":[\"Advanced\",\"Firewall Tutorial\",\"FortiGate\",\"FortiGate SD-WAN configuration\",\"Fortinet\",\"FortiOS\",\"SD-WAN\"],\"articleSection\":[\"FortiGate\"],\"inLanguage\":\"en\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/\",\"url\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/\",\"name\":\"FortiGate SD-WAN Dual ISP Failover and Load Balancing\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg\",\"datePublished\":\"2026-09-10T10:31:13+00:00\",\"dateModified\":\"2026-09-13T23:01:02+00:00\",\"description\":\"Configure FortiGate SD-WAN for dual ISP failover and load balancing with health checks, rules, routing verification and troubleshooting.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#primaryimage\",\"url\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg\",\"contentUrl\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg\",\"width\":1200,\"height\":630,\"caption\":\"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/tutorials\\\/fortinet\\\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/networkfix.in\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/#website\",\"url\":\"https:\\\/\\\/networkfix.in\\\/\",\"name\":\"NetworkFix\",\"description\":\"Practical Network Security &amp; Firewall Guides\",\"publisher\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/#\\\/schema\\\/person\\\/28c6fb08b80eeae506b96250db4f30f0\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/networkfix.in\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/networkfix.in\\\/#\\\/schema\\\/person\\\/28c6fb08b80eeae506b96250db4f30f0\",\"name\":\"networkfix\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png\",\"url\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png\",\"contentUrl\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png\",\"width\":737,\"height\":591,\"caption\":\"networkfix\"},\"logo\":{\"@id\":\"https:\\\/\\\/networkfix.in\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png\"},\"sameAs\":[\"http:\\\/\\\/networkfix.in\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/networkfix.in\\\/#\\\/schema\\\/person\\\/dac05d268c126277e74b684c5239d344\",\"name\":\"Ajay Yadav\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/54c192b947be1e6f455c98ef8939f3bb3eb1a73fc8fd2814579cf29f4c581518?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/54c192b947be1e6f455c98ef8939f3bb3eb1a73fc8fd2814579cf29f4c581518?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/54c192b947be1e6f455c98ef8939f3bb3eb1a73fc8fd2814579cf29f4c581518?s=96&d=mm&r=g\",\"caption\":\"Ajay Yadav\"},\"url\":\"https:\\\/\\\/networkfix.in\\\/en\\\/author\\\/networkfix-news-bot\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"FortiGate SD-WAN Dual ISP Failover and Load Balancing","description":"Configure FortiGate SD-WAN for dual ISP failover and load balancing with health checks, rules, routing verification and troubleshooting.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/networkfix.in\/en\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/","og_locale":"en_US","og_type":"article","og_title":"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing","og_description":"Configure FortiGate SD-WAN for dual ISP failover and load balancing with health checks, rules, routing verification and troubleshooting.","og_url":"https:\/\/networkfix.in\/en\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/","og_site_name":"NetworkFix","article_published_time":"2026-09-10T10:31:13+00:00","article_modified_time":"2026-09-13T23:01:02+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/09\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg","type":"image\/jpeg"}],"author":"Ajay Yadav","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ajay Yadav","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#article","isPartOf":{"@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/"},"author":{"name":"Ajay Yadav","@id":"https:\/\/networkfix.in\/#\/schema\/person\/dac05d268c126277e74b684c5239d344"},"headline":"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing","datePublished":"2026-09-10T10:31:13+00:00","dateModified":"2026-09-13T23:01:02+00:00","mainEntityOfPage":{"@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/"},"wordCount":1691,"publisher":{"@id":"https:\/\/networkfix.in\/#\/schema\/person\/28c6fb08b80eeae506b96250db4f30f0"},"image":{"@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#primaryimage"},"thumbnailUrl":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/09\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg","keywords":["Advanced","Firewall Tutorial","FortiGate","FortiGate SD-WAN configuration","Fortinet","FortiOS","SD-WAN"],"articleSection":["FortiGate"],"inLanguage":"en"},{"@type":"WebPage","@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/","url":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/","name":"FortiGate SD-WAN Dual ISP Failover and Load Balancing","isPartOf":{"@id":"https:\/\/networkfix.in\/#website"},"primaryImageOfPage":{"@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#primaryimage"},"image":{"@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#primaryimage"},"thumbnailUrl":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/09\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg","datePublished":"2026-09-10T10:31:13+00:00","dateModified":"2026-09-13T23:01:02+00:00","description":"Configure FortiGate SD-WAN for dual ISP failover and load balancing with health checks, rules, routing verification and troubleshooting.","breadcrumb":{"@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/"]}]},{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#primaryimage","url":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/09\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg","contentUrl":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/09\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancing-featured.jpg","width":1200,"height":630,"caption":"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing"},{"@type":"BreadcrumbList","@id":"https:\/\/networkfix.in\/tutorials\/fortinet\/fortigate-sd-wan-configuration-for-dual-isp-failover-and-load-balancin\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/networkfix.in\/"},{"@type":"ListItem","position":2,"name":"FortiGate SD-WAN Configuration for Dual ISP Failover and Load Balancing"}]},{"@type":"WebSite","@id":"https:\/\/networkfix.in\/#website","url":"https:\/\/networkfix.in\/","name":"NetworkFix","description":"Practical Network Security &amp; Firewall Guides","publisher":{"@id":"https:\/\/networkfix.in\/#\/schema\/person\/28c6fb08b80eeae506b96250db4f30f0"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/networkfix.in\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":["Person","Organization"],"@id":"https:\/\/networkfix.in\/#\/schema\/person\/28c6fb08b80eeae506b96250db4f30f0","name":"networkfix","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/06\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png","url":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/06\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png","contentUrl":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/06\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png","width":737,"height":591,"caption":"networkfix"},"logo":{"@id":"https:\/\/mlwonxngeomz.i.optimole.com\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/networkfix.in\/wp-content\/uploads\/2026\/06\/cropped-cc164cd4-f7b0-4c85-889e-8a89500fc258-2026-06-25.png"},"sameAs":["http:\/\/networkfix.in"]},{"@type":"Person","@id":"https:\/\/networkfix.in\/#\/schema\/person\/dac05d268c126277e74b684c5239d344","name":"Ajay Yadav","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/secure.gravatar.com\/avatar\/54c192b947be1e6f455c98ef8939f3bb3eb1a73fc8fd2814579cf29f4c581518?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/54c192b947be1e6f455c98ef8939f3bb3eb1a73fc8fd2814579cf29f4c581518?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/54c192b947be1e6f455c98ef8939f3bb3eb1a73fc8fd2814579cf29f4c581518?s=96&d=mm&r=g","caption":"Ajay Yadav"},"url":"https:\/\/networkfix.in\/en\/author\/networkfix-news-bot\/"}]}},"_links":{"self":[{"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/posts\/1398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/comments?post=1398"}],"version-history":[{"count":1,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/posts\/1398\/revisions"}],"predecessor-version":[{"id":1555,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/posts\/1398\/revisions\/1555"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/media\/1397"}],"wp:attachment":[{"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/media?parent=1398"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/categories?post=1398"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/networkfix.in\/en\/wp-json\/wp\/v2\/tags?post=1398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}