@Clive_A 

 

Thanks for your response. I SSH into one of the VMs of the network with the failed gateway. I performed the following curl command to check for connectivity to the controller (I checked to make sure that ports are forwarded properly on the network where the controller is located).

 

curl -k http://<remote_ip_address>:8088

 

This appears to work. Albeit, curl shows no output, but it did not show a connection error.

 

I can't find a way to reboot the gateway remotely. Here's what I tried:

 

- scheduled a reboot of failed gateway from the Omada software

- manually perform a reboot of failed gateway 

 

I suspect neither worked since the device has not been adopted. 

 

I tried connecting to the gateway using SSH in hopes to reboot from the gateway terminal, but the connection was refused. Telnet yielded the same result.

 

Is there another way to connect to this device remotely? Getting physical access is a challenge so having a way to resolve this remotely is best.

 

I just noticed that the other devices in that network shows a “Controller Connection IP” setting set to the WAN IP address of that network, not the WAN IP address of the remote controller. Is that normal?