Omada Hardware controller oc300 fails to upgrade device connected in different sites

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Omada Hardware controller oc300 fails to upgrade device connected in different sites

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
16 Reply
Re:Omada Hardware controller oc300 fails to upgrade device connected in different sites
2023-02-22 23:53:11 - last edited 2023-02-23 00:33:24

perhaps if i set my "device management" to an external fqdn... have to be careful, the remote device is 400 miles away... have it set for a subnet ip now.

 

 

 

is there a way to get detailed logs out of this equipment?

  0  
  0  
#12
Options
Re:Omada Hardware controller oc300 fails to upgrade device connected in different sites
2023-02-23 14:03:29
I have not found any more detailed logs than what is in the UI which are not very detailed. Maybe the TP-Link support folks can help...
  0  
  0  
#13
Options
Re:Omada Hardware controller oc300 fails to upgrade device connected in different sites
2023-08-04 08:25:19 - last edited 2023-08-04 08:40:29

  @atc 

 

Good morning, 

Exactly the same problem here.

We have 5 sites, all connected over VPN to an OC200 controller. Fantastic system that really does the job. Cannot praise the TPLink people enough.

The only thing that keeps refusing to cooperate is the update. I need to update my remote gateways ER605 from V2.0.0 to V2.1.2 but can't seem to get the job done when the device is controlled by the OC200. 

 

Whilst everything is correctly configured, all ports are open, updates keep failing with the following message:

 

fuckfuckfuck Upgrade over VPN keeps failing

 

 

 

AllPortsOpen All ports open...

 

As you can see above all necessary ports are accessible on the side of the device.

 

 

 

 

 

 

 

 

 

I keep searching for a solution but I hope the support team of TPLink can jump in. They are welcome to log into our system ;-) 

 

All the best,

Stefaan. 

  0  
  0  
#14
Options
Re:Omada Hardware controller oc300 fails to upgrade device connected in different sites
2023-08-07 12:52:31

  @MeninGate I am using the software controller which may have different port requirements.  The solution for me was opening TCP 8043 inbound in addition to 29811-29814 and UDP 29810.  Not sure about the hardware controller.  Good luck.

  1  
  1  
#15
Options
Re:Omada Hardware controller oc300 fails to upgrade device connected in different sites-Solution
2023-10-19 03:37:14 - last edited 2023-10-19 06:09:53

  @kdurigan This actually worked!  I I forwarded the TCP port 443 from the gateway to the controller at the main site, and then was able to update the gateway at the remote site.  The port is definitely listening and when attempting to connect to it, it complains that the request requires TLS.

Recommended Solution
  0  
  0  
#16
Options
Re:Omada Hardware controller oc300 fails to upgrade device connected in different sites
2023-10-19 12:30:08

  @jameslmoser - good to know.  I got a hadrware controller recently and have not yet lived through an upgrade.  I have not made any changes to my firewall config so we will see if the next upgrade fails or not!   Last month I did successfully upgrade the ER7206 router with the hardware controller, and I successfully installed a self-signed certificate so I do not get the silly error that the site may not be safe when opening the web UI.  So far so good with the hardware controller...

  0  
  0  
#17
Options