Hi  @zebsys 

for recap, the 1st time the update failed but today when I tried again the update was successful. Weird think. Thanks.

I've had this issue on 3 of 5 OC200's I've attempted to upgrade so far.

 

None of them have a USB stick connected. I think that is a red herring.

 

I had success on two OC200 v1.0 which updated no problem on first attempt.

 

I had a failure on Monday on an OC200 v2.0. Unresponsive after the install ran - I disconnected from PoE then it rebooted into 5.15.24.21. I tried upgrading again and it worked.

 

I have two remote sites where the network is functioning but the OC200s are now offline after attempting update. I'll need to visit the sites to power cycle and fingers crossed they come back.

Holding off on upgrading further sites till this is resolved.

 

 

 

 Hello,

 yesterday Omada offered me another update for OC200 New Controller software 1.37.11 Build 20251201 Rel.43290. Has anyone already had experience with this update?

Thank you,

Pavel

 

I've now power cycled one of the failed OC200 controllers that is in the same location as me. When it came back up it was still running 5.15.24.21 - 1.36.7 Build 20250707 Rel.72474.

 

When logging in via the Cloud interface (not local login to OC200) I was offered 6.0.0.36 - 2.22.11 Build 20251201 Rel.43307 (which looks like a new version since the last time I tried). I went ahead with trying the upgrade and started a continuous ping to the local IP address of the OC200 to see what happens. 

 

The cloud interface now says that the device is offline, but there is no drop of pings (suggesting it never restarted as part of any upgrade process).  There is no response to http or https requests to its local IP address.

 

It looks to me like this newer version of the controller has the same issue as the previous one.

 

Also, it would be really useful to have one version number to keep track of and be consistent.  Seeing 5.15.24.21 in one interface and 1.36.7 Build 20250707 Rel.72474 in another really isn't helpful.

Hi, so I finally decided to update the OC200 to version 6.0.0.36, 1.37.11 Build 20251201 Rel.43290. The download went fine, but the reboot indicator was no longer displayed. However, the reboot did occur, everything went smoothly, and all devices were correctly adopted and connected. Pavel

I just had a go on my OC200 v1 at home just now, and it worked fine.  The previous updates also worked without a hitch on my home setup.

 

But I have seen failure on several OC200 v1s and v2s across remote sites I look after, and the only way to restore access has been to physically unplug the OC200 from power and plug it back in.  That isn't easy at remote sites, some of which are on different continents. 

 

None of the sites are particularly large in the number of Omada devices and clients, nor are the configs more complex than what I have at home (probably less in many cases).  I am not using local USB drives to back anything up - the OC200s are just plugged in to PoE network from an Omada switch.

 

I've had one OC200 which was successful to update to 6.0.0.34 on the second attempt, and another that failed and remained on 5.315.24.21 after power cycling, and has now failed to update to 6.0.0.36.  Another remote site running an OC200 v1 upgraded to 6.0.0.34 no problem, but I dare not trigger any update to 6.0.0.36 as it is a very long trip to power cycle it.

 

Since I can ping the OC200s once they stopped responding to https perhaps there is another way to reboot them if I have a VPN connection to the site? Unfortunately once they are managed by the OC200, I can't use Omada switches to power cycle the port connected to the OC200.  Chicken and egg situation.

  @dunxd 

 

If you enable SSH on the site, and the following happens

 

- VPN or some kind of remote access to the remote site is in place

- You can reach the IP of the switch

- The Controller is stuck and not rebooted and therefore devices arent currently adopted

- You can then SSH into the switch and will have the reboot command available, which will power cycle the POE and therefore the OC200

 

IF the switch is in a currently adopted "connected" state, the reboot command over SSH is not available

@GRL my Omada switches are all adopted by an Omada Controller on each site so I don't think this is an option. Unless I misunderstand what you mean? 

 

Is this something I can enable at the sites that currently have a functioning Omada controller for future use, or only if the switch is not managed by a controller at all?

  @dunxd 

 

If the controller isnt "live" ie - not booted, stuck or cant communicate with the switches - say after a failed update - the switches will enable the reboot command in their SSH options.