Hi  @Jollygist 

You can configure the inform URL for the remote site devices.

https://community.tp-link.com/en/business/forum/topic/863244?replyId=1688592

Here is a screenshot:

Hi  @Jollygist 

The URL to be filled in here is not the Controller’s URL.

Instead, it is the domain name you previously assigned to those static IPs.

Additionally, neither location has a static IP address, but I have each location's URL updated via a DNS update service running on a Pi.

Specifically, it is the public IP address/DDNS of the Controller’s site.

Jollygist wrote

  @Vincent-TP 

 

Thanks for the reply.  I had entered the home office URL when I set up the remote gateway in its web interface so it could find the OC200 controller and be adopted, which it did.  I do not know what the underlying operations the remote gateway or OC200 controller perform to re-establish a connection should one of the two locations experience a power failure or reboot.   However, it seems that either the OC200 controller can't find the remote gateway across the internet or the remote gateway can't find the controller across the internet.  In the OC200's browser interface for the remote gateway, the entry for the Inform URL has my internal network's IP address (omada://192.168.x.x?dPort=#####&mPort=#####&omadacId=##################) for the OC200, not the public URL and neither location has a static public IP, so it can't find its way back.

 

Thanks,

Dale

Hi  @Jollygist 

but what is presented in the Omada OC200 interface is my internal network's IP address (the 192.168.x.x) as shared earlier.

You can access via this private network address from the local network. However, remote devices cannot access it directly and must use this site's public IP address or DDNS domain name. So, the inform URL should be configured on the remote gateway's web interface, not the controller's page.

It's this step in the following guide:

How to Manage Omada Devices at Different Sites Using Omada SDN Controller via Port Forwarding (Controller 5.0 or Above)

Hi  @Jollygist 

I understand your question.

If you’ve configured the inform URL correctly, the remote device should automatically reconnect to the controller and resume connection after a power cycle and restart.

If there’s still an issue despite correct configuration, it’s recommended to check whether the local network returns to normal after each power cycle and restart.

Jollygist wrote

  @Vincent-TP 

Hi,

 

When I set up the router at the remote location, I did enter the public facing URL of the home location which resolves to the IP address assigned to my equipment by my Internet Service Provider.  This allowed the remote router to be successfully adopted by the OC200.   Anytime the remote location experiences a power outage or a forced reboot, the remote router won't reconnect to the controller.  This is the root of my problem.  

 

Shouldn't the remote router be able to reconnect to the OC200 on a router reboot or boot after a power outage?

 

Thanks,

 

Dale

Hi  @Jollygist 

Thanks for your reply.

For your case, we recommend sending the following details to the listed Support Email on your region’s support page:

Subject: [Forum Escalation][ID 863692] 
Forum Nickname: 
Thread URL: 
Model & Version: 
Description: 
Any Other Relevant Information (Controller running Logs, Config Files):
 
Once sent, a ticket will be created in our support system, and a team member will follow up to gather more information or troubleshoot the issue. If you would like our team to ensure your ticket is responded to in a timely manner, feel free to reply with your Ticket ID Number. 
 

Jollygist wrote

  @Vincent-TP 

 

Hi, and thanks for working through this with me.  Upon power restoration or reboot, internet activity is restored, however the ability to monitor the remote location via the OC200 is unavailable since the OC200 reports the remote location is disconnected.

 

Thanks,

 

Dale