Failed to update Omada devices by Omada Controller Online

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

Failed to update Omada devices by Omada Controller Online

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Failed to update Omada devices by Omada Controller Online
Failed to update Omada devices by Omada Controller Online
2022-06-07 12:16:28 - last edited 2022-10-28 01:20:21

This Article Applies to:

SDN 5 (Omada Controller is v5 and the Devices firmware is adapted to Controller v5)

 

Background:

After cloud access is enabled on Omada Controller, the Controller will check whether there is a firmware upgrade for the Omada devices. When there is an upgrade, there will be an upgrade button on the device page, in this situation, the administrator can log in the Controller, and click the upgrade button to upgrade the Omada devices online.

For Controller v4 and before version,  the TCP 29813 port is required for upgrading devices.

Along with the full upgrade of SDN5 (Omada Controller is v5 and the Devices firmware is adapted to Controller v5), the default port that is used for upgrading has been changed from TCP 29813 to TCP 8043 /TCP 443, and this will take effect only when both Controller and Device are upgraded to SDN 5.

To be more clearly, here is a summary table for the Ports that are used for device upgrading and management.

 

 

 

For more details, you may check this article:

Which ports do Omada Controller and EAP Discovery Utility use?

 

Issue Description/Phenomenon:

We received feedback that Controller v5 failed to upgrade EAP firmware either locally or via cloud access. The device just got into the "Upgrading" status but never finished upgrading. After refreshing the page, the device will remain with the old firmware, and there will be a log, saying upgrade failed as shown below.

 


Related post:

Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details

 

Troubleshooting:

After further investigation, TP-Link Team found that it is was actually a Port issue.

Based on the Background provided above, we know that Controller v5 has changed the port for firmware upgrade. Therefore, if you haven’t noticed this port change, and there is NAT or Firewall existed between your Omada Devices and Controller, you may suffer from this issue of upgrade failure.

 

Suggestions:

For the issue that Controller v5 failed to upgrade the device firmware, please check the current device firmware version first.

And confirm its adapting controller version by the firmware released note as the example shown below.

 

If the current device firmware is adapted to Controller v5, you may refer to the following suggestions to troubleshoot and resolve the issue:

Note: The following suggestion is only applied to SDN5 (Omada Controller is v5 and the current Devices firmware is adapted to Controller v5).

 

1. Check the setting of “HTTPS Port for Controller Management”.

 

For SDN5, the Port used for device upgrading is up to the setting of “HTTPS Port for Controller Management”. We can go to Settings -> Controller -> Access Config to find it, see as below.

 

 

For Omada Software Controller v5, the default port is TCP 8043,

For OC200/OC300 with built-in Controller v5, the default port is TCP 443.

 

Note: The port used for device upgrading will change as the setting of “HTTPS Ports for Controller Management changes. For example, if you change the HTTPS Port for Controller Management from 8043 to 8000, the port used for device upgrading will also change from 8043 to 8000 accordingly.

 

2. Confirm the required ports are open.

1) If the NAT device blocks the interaction, please set port forwarding rules pointing to the ports used for device upgrading and management are all open.

Take this topology as an example:

                      EAP adapting to Controller v5----ER605 (1) ----  Internet ---- ER605(2)----Omada Controller v5

Ensure the UDP 29810, TCP29814, and the HTTPS port for Controller Management are all open on the ER605 (2) .

 

2) If the firewall blocks the interaction, please add the HTTPS port for Controller management to the whitelist.

 

------------------------------------------------------------------------------------------------

Feedback:

If there is anything unclear in this solution post, please feel free to comment below.

If the suggestion above doesn’t work for you, your case is probably a different issue. In that case, please feel free to start a new thread with the following information.

1) Device Information - including the Model Number, Hardware and current Firmware Version of your Omada devices.

2) Network Diagram - show how the devices are connected in your network.

3) Goal - which firmware version you were trying to upgrade to?

4) Problem - describe how you are running into this issue, upload screenshots of the error message if there is.

5) Troubleshooting - what you have tried and the results.

 

Thank you for your great cooperation and patience!

2022 TP-Link Wi-Fi 7 Product Launch Event | Watch the Replay at https://www.tp-link.com/us/wifi7/event/.
  4      
  4      
#1
Options
2 Reply
Re:Failed to update Omada devices by Omada Controller Online
2022-06-15 16:53:26

  @Hank21 

 

Solution worked perfectly! Thank you! When do we get a dark/black Omada UI?

  1  
  1  
#2
Options
Re:Failed to update Omada devices by Omada Controller Online
2022-06-16 06:08:15

Ranger-2-Robo wrote

  @Hank21 

 

Solution worked perfectly! Thank you! When do we get a dark/black Omada UI?

Hi  @Ranger-2-Robo 

 

Dark Mode is still under development, currently I don't have a accurate date. Please keep following our official website.

2022 TP-Link Wi-Fi 7 Product Launch Event | Watch the Replay at https://www.tp-link.com/us/wifi7/event/.
  3  
  3  
#3
Options