Greetings,

I have two ER605 (both v2.0) gateways 1200 miles apart.  The primary location also houses the OC200 and each location has an EAP650 AP. The current configuration is scheduled to reboot the OC200 at 1am, the ER605 at 2 am and the EAP650 at 2:10 am and the remote location reboots at 3 am for the ER605 and 3:10 am for the EAP650.  All components are using the latest stable firmware.  

Upon reboot, the equipment at the remote location shows "disconnected" in the Omada interface.  I then have to remote into a desktop at that location to factory reset the ER605 and then re-establish the cloud management of the gateway.  Eventually, the EAP650 becomes adoptable, and then things are fine for another week.  I've tried searches, but either this is not a common issue or I am not using the correct search terms.

This is also an issue when the remote location experiences a power failure.  I established an IPSEC VPN between the locations and the home IP address range is within 192.168.0.x and the remote address range is within 192.168.10.x, if that matters.

Also, the remote location is in an area that gets multiple power failures. When a power failure occurs, it requires a 1200 mile journey to the remote location. I set up the reboot schedule thinking the system would respond better with a prompted reboot rather than having the power abruptly removed. While this is not critical infrastructure and internet activity resumes after power is restored (but the gateway and AP remain disconnected from the OC200), shouldn't the system be able to reconnect to the controller? Is there a setting I have missed?

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. I think my problem may be related the OC200 not being able to find the remote location. Does anyone know where I should be entering the URL of the remote location in the Omada OC200 interface?

I appreciate any suggestions.

Thanks,

Dale