We have the following setup in our environment. (Please refer the diagram given below).

 

There are 2 ISPs each with their own Fiber to Copper convertors installed. We have the 2 devices configured with the following network ranges.

ISP 1: 172.16.10.1/24

ISP 2: 172.16.20.1/24

 

The TP-Link ER605 connects to both uplink routers on WAN1 and WAN2 ports with static IP defined for both.

WAN1: 172.16.10.50

WAN2: 172.16.20.50

 

The remaining 3 ports are configured to be LAN with the following network range: 10.10.0.1/16

 

There is a RaspberryPi 4 hosting the Omada Controller v4.4.4 connected to LAN 3 port.

 

LAN port is connected to a TP-Link Switch.

 

On the Omada SDN we have the following configuration defined.

 

Load Balancing Weight: 1:1

Application Optimized Routing: Enable

Link Backup: Enable

Primary WAN: WAN1

Backup WAN: WAN2

 

Primary Active WAN always and switch to secondary if any WAN fails.

 

The problem we're facing is, with the given configuration, we expected the setup to work like a active backup ISP in failover mode.

 

What we observed is, if ISP 1 (primary) goes down with service outage, the router does not failover to the secondary backup ISP. What the ER605 router considers down is when the physical connectivity goes down, either someone pulls the ethernet cable from WAN1 or the uplink router goes power off.

 

Before adopting the ER605 to Omada, the router had an active policy page where we could define either Ping or DNS lookup for active check. I can't see anything of that sort on the Omada SDN Wired Network > Internet setup page.

 

Would like to know what's going wrong or what am I missing. Thanks.