@Pablo_PL Do you have Link Backup or Load Balancing enabled? Is there a reason the second WAN needs to have a private IP address instead of presumably what is a second internet service passing the connection through? 

If you can provide a network diagram for the failing router that would be great.

  @NeilR_M 

hi. my config print

Two internet connections from different providers are connected to the router.
WAN1 receives a public IP address, while the second provider assigns only private IP addresses — this connection is connected to WAN2.

There have never been any issues with this setup before. The only change I made was a modernization in another location that manages this router and the network. Additionally, I added a second OC400 controller so that it operates as a cluster.

In another location, I have the same router with the same configuration, and there are no issues there.

  @Pablo_PL Can you confirm that traffic goes across the second WAN? If you disconnect the first WAN, can you still adopt the router? Also, does the second location have the same set of internet providers as the problem location? 

Any IP pool conflicts between the second provider and any other subnet on the SD-WAN topology? 

  @Pablo_PL 

Hi, I need to apologize, because what I wrote earlier was not entirely accurate. In the meantime, I have figured out a few things on my own.

1. I went to the location and physically disconnected the cable from the WAN2 port — however, the issue still occurs.

2. The first time, I restored the router to factory settings and re-adopted it. When WAN2 was connected, the problem appeared, and based on that I submitted the support ticket.

3. I was able to work around the issue by disconnecting WAN2 — the adoption then worked correctly.

4. After restarting an already adopted device, the problem appears again.

5. I did not mention earlier that I started using a second controller operating in cluster mode — this might be the root cause of the issue.

  @Pablo_PL 

If the site had load balancing enabled, it might be the case that the Omada adoption/control data are sometimes being sent out over WAN 2 - and if you dont have that IP enabled on the incoming side at the controller host site port forward, the controller wont see it