Early Access Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
This Article Applies to
Omada_SDN_Controller_v5.14.32.3 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC200(UN)_V2_2.17.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC300(UN)_V1_1.26.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC400(UN)_V1_1.4.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.14.20 in advance, and also give us TP-Link the opportunity to fully test the firmware in your real network environment and scenarios before the official release. All feedback is welcome, including letting us know about successful upgrades.
Release Notes
New Features
1. Added support for gateways: ER8411 v1.2, ER7412-M2 v1.2, ER706W v1.2, ER605 v2.2.
2. Added support for APs: EAP 772 v2.
3. Added support for Controller IP Access Rules in Global View > Settings > Account Security.
4. Added support for Upgrade Logs, Upgrade Schedules, Beta Firmware Program, Cloud Firmware Pool and other function in Global view > Firmware.
5. Added support for Audit Logs unit in Global View: user’s operations will be recorded to facilitate system maintenance.
6. Added support for configuring following features with Omada APP:
- Bandwidth Control
- Deep Packet Inspection
- IPS/IDS
- IP Group
- MAC Filtering
- Dynamic DNS
- WLAN Optimization
- Load Balancing
Enhancements
1. Optimized Backup, added support of selection of configurations and data.
2. Optimized Restore, data is no longer supported to be kept after restoring backup file, only configurations can be kept.
3. Optimized distribution of Export Data, added support for exporting data in the corresponding features module directly.
4. Optimized adaptability to SSL certificate, added support for importing certificate chain file of PEM format in Global view > Settings > System Settings > HTTPS Certificate.
5. Optimized default settings, enabled Fast Roaming, Gateway LLDP automatically.
6. Optimized the stability when using the terminal of devices.
7. Optimized the performance when managing clients in huge scale.
8. Optimized the Upgrade Schedule, added support to select model for upgrading, not single device anymore.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.17 or above.
2. Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
3. Since version 5.14.32.2, Omada Software Controller no longer supports upgrade from Controller v4.
4. Since version 5.14.32.2, Omada Software Controller(windows) only supports installation on Windows64-bit platform.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the controller Backup Config file before upgrading or downgrading.
(3) You may follow the following guide to upgrade your Omada Controller. How to Upgrade or Downgrade Omada SDN Controller.
Firmware Download Link
-
Direct Download
Omada_Controller_Windows_v5.14.32.3
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
Omada_Controller_Windows_v5.14.32.2
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
Omada_SDN_Controller_v5.14.32.2_linux_x64.tar.gz
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
Omada_SDN_Controller_v5.14.32.2_linux_x64.deb
OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
Additional Information
If somehow you encounter an issue during or after the controller upgrade, it's suggested to contact us with the following info:
- Omada Controller version (previous and current)
- Device Model(s), Hardware and Firmware versions
- (if possible) A copy of the Log file and Backup Config file
If you decide to downgrade the controller before reporting the issue to TP-Link, it's suggested to save a copy of the current Log file and Backup Config file before you do that, which could help to investigate and address the issue quickly.
>> How to get the Log file and Backup Config file for Omada SDN Controller:
-
If your Windows software controller failed to get launched, please locate the controller installation path for the Log file.
-
If it's not a launch issue, you can export the Log file and Backup Config file in the local network.
-
For Omada Controller v5.8 or later version,
In the Global View, go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.
-
For Omada Controller v5.6 or v5.7,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.
-
For Omada Controller v5.5 or previous version,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file . Go to Settings > Services > Export Data > Running Log to export the Log file.
-
Update Log
Nov 8th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Update the Omada Software Controller pre-release version to the official release.
Oct 30th, 2024:
Remove download links for all the controllers 5.14.32.
Oct 28th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
Update the Omada Software Controller pre-release version to the official release.
Sep 26th, 2024:
Provide the following controller firmware for early access.
- Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
Recommended Threads
TP-Link Early Access Program Is Now Available!
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@ceejaybassist This pre-release version isn't displaying the watermark
- Copy Link
- Report Inappropriate Content
After installing update from 1.25.3 Build 20240620 to 1.26.5_pre-release on my OC300v1 I received startup fail error and was not able to upgrade properly. I've got collected logs and can share If needed. I was also not able to restore previous firmware with current settings. I was forced to factory reset and then restore from backup.
- Copy Link
- Report Inappropriate Content
Thank you so much for your feedback. Please check your mail inbox and find the case ID TKID241063341. Thanks.
- Copy Link
- Report Inappropriate Content
Many thanks to the engineers at TP-Link.
Really!
May God bless you all and the company generously.
I thought they would never implement DPI on the device and it was a surprise to see this pre-release present this and other new tricks.
There was no way to allocate funds to a more robust device. This new firmware management is really cool.
Thank you very much! I just applied it and didn't detect any problems with its operation. Quite the opposite! I loved what you did even more.
Too bad I'm so busy. I wanted to play around with the firmware even more.
OC200 V1.
- Copy Link
- Report Inappropriate Content
Thank you so much for your positive feedback!
- Copy Link
- Report Inappropriate Content
@Vincent-TP One issue wihich has been mentioned already, having a OC200 v1 my WAN settings disappeared too. Not to much of a problem, after setting the WAN settings again WAN was working.
For the rest I have not seen any problems and DPI is working like a charm for me.
- Copy Link
- Report Inappropriate Content
The prerelease on my OC200 v1 had an issue. It manages 2 sites, an ER8411 and an ER7206 v2 which handles the gateway functions for our public networks.
The main site, with the ER8411 updates, reprovisioned and reconfigured just fine, no issues.
The site with the ER7206 v2, it wiped the WAN settings and reset them to dynamic. Unfortunately there is no DHCP on its WAN side so the device is now offline. I have recreated the apropriate settings on the controller for that site but it will have to wait until i am onsite tomorrow to factory reset, give it its initial WAN settings in standalone, then allow it to be readopted again.
Very, Very luckily for me, i am able to modify my policy routing to allow the public WiFi to continue to work through the ER8411s connection for the time being.
I genuinely find it astounding that something like this isnt picked up by internal testing way, WAY before it gets to a prerelease. And its not just my issue, i can see at least one other report of this in this thread. This isnt some tiny bug, some minor thing, it wiped the WAN settings!
Yes, in my case, im aware of the whole "beta isnt stable and stuff happens" - sure - but this exact controller version has just been released as "stable" for windows/linux - today - and people will be applying it to networks en-masse now.
- Copy Link
- Report Inappropriate Content
Hi all,
We hope this message finds you well. This is to inform you that we have decided to temporarily suspend the trial of the Omada software 5.14.32 version that was released recently.
Unfortunately, during the trial process, we have encountered some issues that have a negative impact on the user experience. To ensure that you do not face further inconvenience and to maintain the quality of our services, we have made this decision.
We understand that this may cause some inconvenience to you, and we sincerely apologize for this. At present, we are working hard to find solutions to these problems.
A temporary solution will be provided to you later.
We would like to express our heartfelt gratitude to all of you who have participated in the trial. Your active feedback has been invaluable to us. It has greatly assisted us in our commitment to continuously providing the most optimal software and products. Your insights have enabled us to identify areas for improvement and work towards enhancing the quality of our offerings.
We are working hard to resolve these issues as quickly as possible and will keep you updated on the progress. Once the firmware has been thoroughly tested and improved, we will resume the trial and look forward to your continued participation.
Thank you again for your understanding and support.
Update:
Previously, we informed you about the temporary suspension of the trial due to some issues affecting the user experience. For those of you who have already upgraded the firmware, there is no need to worry about downgrading or upgrading to the trial version again. The potential issues related to the trial version will only be triggered in a specific condition. In all other normal usage scenarios, you will not encounter these problems.
Therefore, you can continue to use the software as usual. Your usage experience and feedback are of great value to us. We welcome you to provide us with your thoughts and any issues you may encounter at any time.
- Copy Link
- Report Inappropriate Content
Hi @GRL
Thank you for your feedback, we are working on this. Once there is any progress, will keep you updated ASAP.
- Copy Link
- Report Inappropriate Content
I have found a visual issue with this version as well, see below screenshot. The indicated area is essentially unreadable in dark mode
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 8385
Replies: 55
Voters 1
