Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Configuring A-A SD-WAN with internal FortiGate hardware switches

Caution

This setup is not fully compliant with a regular HA configuration. Failover is also unnecessary. Flipping can occur if failover is configured using a ping server interface.

Two FortiGates with internal hardware switches can be configured as an active-active (A-A) HA pair. In the following topology, both FortiGates forward traffic through internal switches connected to service providers. SD-WAN is configured on all upstream interfaces and overlays.

This setup is not fully compliant with a regular HA configuration. In a regular HA configuration, two logical switches are used: one for incoming traffic and one for outgoing traffic. In this example, only incoming traffic has a switch while outgoing traffic uses the internal switch. This means that if FortiGate A loses power, ISP 1 will not be available.

Traffic will flow either through ISP 1 directly or through ISP 2 via a connection between FortiGate A and FortiGate B’s internal switch interface. FortiGate A decides how traffic will go through ISP 1 or ISP 2 based on SD-WAN rules. If ISP 1 is not available, then traffic will go through ISP 2.

Failover is unnecessary in this setup. Because SD-WAN will automatically failover traffic to the accessible ISP, traffic is not blocked so there is no network downtime. Also, the hardware switch interface cannot be monitored as an HA interface. If HA failover is required, a ping server must be used. The ping server monitor interface has to be configured under HA settings. This failover setup, however, results in flipping. FortiGate B will act as the primary after failover and traffic will still flow to the available ISP. Since the broken link to one of the ISPs still fails, HA will start flipping until the link is back up.

To configure the HA A-A cluster with internal hardware switches:
  1. Configure two FortiGates with internal switches in an active-active HA cluster (follow the steps in HA active-active cluster setup), starting by connecting the heartbeat interface.
  2. On the primary FortiGate, remove the existing interface members:
    1. Go to Network > Interfaces.
    2. In the LAN section, double-click the internal interface to edit it.
    3. In the Interface Members box, remove all the interfaces.

    4. Click OK.
  3. On the primary FortiGate, configure the hardware switch interfaces for the two ISPs:
    1. Go to Network > Interfaces.
    2. Click Create New > Interface.
    3. Enter a name (HD_SW1).
    4. For type, select Hardware Switch.
    5. For Interface Members, add two interfaces (internal1 and internal2).
    6. Configure the remaining settings as needed.
    7. Click OK.

    8. Repeat these steps to create a second hardware switch interface (HD_SW2) with two interface members (internal3 and internal4).

  4. On the primary FortiGate, set up SD-WAN:
    Note

    The primary FortiGate makes all the SD-WAN decisions.

    1. Go to Network > SD-WAN Zones.
    2. Click Create New > SD-WAN Member.
    3. In the Interface dropdown, select HD_SW1.
    4. Leave SD-WAN Zone set to virtual-wan-link.
    5. Enter the Gateway address.
    6. Click OK.
    7. Repeat these steps to add the second interface (HD_SW2).
    8. Click Apply.

  5. Connect the devices as shown in the topology:
    1. Connect the incoming interface to the internal switch on both FortiGates.
    2. On FortiGate A, connect ISP 1 to HD_SW1.
    3. On FortiGate B, connect ISP 2 to HD_SW2.
    4. For HD_SW1, connect FortiGate A directly to B.
    5. For HD_SW2, connect FortiGate A directly to B.
Note

The default implicit rule load-balancing algorithm for SD-WAN is the source IP address. For more information about rule types and configurations, see Implicit rule.

Configuring A-A SD-WAN with internal FortiGate hardware switches

Caution

This setup is not fully compliant with a regular HA configuration. Failover is also unnecessary. Flipping can occur if failover is configured using a ping server interface.

Two FortiGates with internal hardware switches can be configured as an active-active (A-A) HA pair. In the following topology, both FortiGates forward traffic through internal switches connected to service providers. SD-WAN is configured on all upstream interfaces and overlays.

This setup is not fully compliant with a regular HA configuration. In a regular HA configuration, two logical switches are used: one for incoming traffic and one for outgoing traffic. In this example, only incoming traffic has a switch while outgoing traffic uses the internal switch. This means that if FortiGate A loses power, ISP 1 will not be available.

Traffic will flow either through ISP 1 directly or through ISP 2 via a connection between FortiGate A and FortiGate B’s internal switch interface. FortiGate A decides how traffic will go through ISP 1 or ISP 2 based on SD-WAN rules. If ISP 1 is not available, then traffic will go through ISP 2.

Failover is unnecessary in this setup. Because SD-WAN will automatically failover traffic to the accessible ISP, traffic is not blocked so there is no network downtime. Also, the hardware switch interface cannot be monitored as an HA interface. If HA failover is required, a ping server must be used. The ping server monitor interface has to be configured under HA settings. This failover setup, however, results in flipping. FortiGate B will act as the primary after failover and traffic will still flow to the available ISP. Since the broken link to one of the ISPs still fails, HA will start flipping until the link is back up.

To configure the HA A-A cluster with internal hardware switches:
  1. Configure two FortiGates with internal switches in an active-active HA cluster (follow the steps in HA active-active cluster setup), starting by connecting the heartbeat interface.
  2. On the primary FortiGate, remove the existing interface members:
    1. Go to Network > Interfaces.
    2. In the LAN section, double-click the internal interface to edit it.
    3. In the Interface Members box, remove all the interfaces.

    4. Click OK.
  3. On the primary FortiGate, configure the hardware switch interfaces for the two ISPs:
    1. Go to Network > Interfaces.
    2. Click Create New > Interface.
    3. Enter a name (HD_SW1).
    4. For type, select Hardware Switch.
    5. For Interface Members, add two interfaces (internal1 and internal2).
    6. Configure the remaining settings as needed.
    7. Click OK.

    8. Repeat these steps to create a second hardware switch interface (HD_SW2) with two interface members (internal3 and internal4).

  4. On the primary FortiGate, set up SD-WAN:
    Note

    The primary FortiGate makes all the SD-WAN decisions.

    1. Go to Network > SD-WAN Zones.
    2. Click Create New > SD-WAN Member.
    3. In the Interface dropdown, select HD_SW1.
    4. Leave SD-WAN Zone set to virtual-wan-link.
    5. Enter the Gateway address.
    6. Click OK.
    7. Repeat these steps to add the second interface (HD_SW2).
    8. Click Apply.

  5. Connect the devices as shown in the topology:
    1. Connect the incoming interface to the internal switch on both FortiGates.
    2. On FortiGate A, connect ISP 1 to HD_SW1.
    3. On FortiGate B, connect ISP 2 to HD_SW2.
    4. For HD_SW1, connect FortiGate A directly to B.
    5. For HD_SW2, connect FortiGate A directly to B.
Note

The default implicit rule load-balancing algorithm for SD-WAN is the source IP address. For more information about rule types and configurations, see Implicit rule.