Early Access Omada SDN Controller_V5.13.30 Pre-release (Updated on Feb 28th, 2024)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Update as of Apr 10, 2024:
Thank you all for your valuable feedback on the Beta firmware!
The official firmware has been released, check the following link for details.
Omada_SDN_Controller_v5.13.30.8_Windows
Omada_SDN_Controller_v5.13.30.8_linux_x64.deb
Omada_SDN_Controller_v5.13.30.8_linux_x64.tar.gz
OC200(UN)_V1_1.29.4 Build 20240304
OC200(UN)_V2_2.14.4 Build 20240304
OC300(UN)_V1_1.22.4 Build 20240304
This Article Applies to
Omada_SDN_Controller_v5.13.30.8 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.13.30.8_Linux_x64.tar.gz (Ubuntu 16.04/18.04/20.04, Debian 8/9/10, CentOS 6/7)
Omada_SDN_Controller_v5.13.30.8_Linux_x64.deb (Ubuntu 16.04/18.04/20.04, Debian 8/9/10)
OC200(UN)_V1_1.29.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
OC200(UN)_V2_2.14.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
OC300(UN)_V1_1.22.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
Overview
We hope to offer you with a chance to experience the new features added in the Controller v5.13 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 lettings us know about successful upgrades.
Release Notes
New Feature
1. Added support for Layer-3 Switches: SG6428X, SG6428XHP, SG6654X, SG6654XHP, SX6632YF.
2. Added support for Layer-3 Switch features:
- QoS
- VRRP
- OSPF
- STACK
- STP Extension
Enhancement
1. Optimized the PUBLIC IP ADDRESS column in Devices List.
2. Optimized the validation rules for WAN Static IP address, allowing setting to Static IP with a 31-bit network mask.
3. Optimized the Global View for viewer account, allowing users with Viewer permissions to see the Sites they can access in the Global View.
4. Optimized the name of "AI WLAN Optimization" to "WLAN Optimization", removed the Schedule module.
5. Optimized the PMF mode automatic selection logic and the prompts when PMF/WPA mode changes.
6. Optimized the Controller version number to 4 digits, the Backup files are compatible when the first three digits are identical, improving Site import and migration.
7. Optimized the clarity of some texts and icons in Dark mode.
8. Optimized the logic of the authentication logs update.
Bug Fixed
1. Fixed the issue that configuration can’t be sent to the Router and reports “The configurations of device are different from the configuration from the controller”.
2. Fixed the issue that some models’ firmware can’t be upgraded online, but only through manual upgrade.
3. Fixed the issue that the clients can’t connect the SSID with MAC Filtering under some certain configuration steps.
4. Fixed the issue that Controller takes up a lot of disk space after running for a long time.
5. Fixed the issue that LTE models lose the Internet after changing the Rate Limit via Open API.
6. Fixed the issue that the Tx Power (EIRP) setting of the EAP changes to High after the reboot, although the actual EIRP maintains.
7. Fixed the issue that Batch Config of WLAN Group doesn’t work for EAPs.
8. Fixed the issue of the display error of some models in Device Map.
9. Fixed the issue of failing to create SSID via Open API.
Note
1. As this version optimizes the WAN/LAN port configuration of Omada Gateway, it will cause some WAN ports to be enabled by default and cannot be disabled. This may result in changes to the load balance configuration, you can make the changes manually.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.14 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. For Windows OS, Java 8 (or OpenJDK-8) and above are required. How to install Java Runtime Environment (JRE) for Omada SDN Controller on Windows?
4. For Linux version, 64-bit Linux OS is supported and Java 8 (or OpenJDK-8) and above, MongoDB v3 and v4 are necessary required. How to install Omada SDN controller on Linux system (above Controller 5.0.29)
5. If you are upgrading from controller v3.x, it's highly recommended to upgrade 3.x to v4.1.5 first, then v4.1.5 to the latest 5.x. Please follow the Omada Controller Upgrade Guide in the installation package before upgrading.
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 upgrade or downgrade.
(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_SDN_Controller_V5.13.30.4_Windows(Pre-release version)
Omada_SDN_Controller_v5.13.30.8_Windows
Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)
Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version)
Omada_SDN_Controller_v5.13.30.8_linux_x64.deb
Omada_SDN_Controller_v5.13.30.8_linux_x64.tar.gz
OC200(UN)_V1_1.29.3_Build20240131 (Pre-release version) > Built-in Omada SDN Controller 5.13.30.10
OC200(UN)_V2_2.14.3_Build20240131 (Pre-release version) > Built-in Omada SDN Controller 5.13.30.10
OC300(UN)_V1_1.22.3_Build20240131 (Pre-release version) > Built-in Omada SDN Controller 5.13.30.10
-
Download From TP-Link Global "EN" Website:
Omada Controller_Windows/Linux: https://www.tp-link.com/en/support/download/omada-software-controller/
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 to 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
Feb 28th, 2024:
Update the Omada Software Controller (Linux) beta version to official release.
-
Before
Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)
Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version)
-
After
Omada_SDN_Controller_v5.13.30.8_linux_x64.deb
Omada_SDN_Controller_v5.13.30.8_linux_x64.tar.gz
Feb 7th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.29.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
- OC200(UN)_V2_2.14.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
- OC300(UN)_V1_1.22.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
Update the Omada Software Controller (Windows) beta version to official release.
-
Before
Omada_SDN_Controller_V5.13.30.4_Windows(Pre-release version)
-
After
Omada_SDN_Controller_v5.13.30.8_Windows
Jan 9th, 2024:
Add the following controller firmware for early access.
-
Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)
-
Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version)
Jan 8th, 2024:
Provide the following controller firmware for early access.
-
Omada_SDN_Controller_V5.13.30.4_Windows(Pre-release version)
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
@Hank21 Could you please upgrade the MongoDB dependency to at least 6.0? This is because it is not possible to install MongoDB 3.0 ... 4.5 to Ubuntu 22.04 or later.
MongoDB's current stable version is 7.0, and 6.0 is the oldest one having support for Ubuntu 22.04.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @ceejaybassist，
Sorry that I have no idea when the pre-release version firmware of Hardware controller will be provided. I will update here once it is available.
- Copy Link
- Report Inappropriate Content
Hi @kogan，
Did your customer upgrade the controller in local or on the cloud website?
It may just be caused by a brief fluctuation in the network, after which please keep watching to see if there will be any issues similar to the disconnection.
- Copy Link
- Report Inappropriate Content
Hmm, its linux omada (debian) - didnt knew, it could be upgraded over cloud ;-)
- Copy Link
- Report Inappropriate Content
Hi @kogan，
To better assist your customer, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240132388, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
@ceejaybassist its really a to sad i cant move my windows installation tot the oc200 hardware installation because its still not updated yet, does anyone got any inside news about this
- Copy Link
- Report Inappropriate Content
@ceejaybassist same question here, is it possible to like downgrade the windows version so we can migrate?
- Copy Link
- Report Inappropriate Content
@IIIdefconIII I actually had to move from the OC300 to a Windows Software Controller to get IDS/IPS and I don't believe there is any plan to enable that on the hardware controllers anytime soon. What I was told is that the hardware didn't support that functionality, so maybe the aren't powerful enough. I just got a dedicated desktop for the purpose and set up the controller as a service (which is documented) and updated the BIOS on the PC to always start up after a power loss so it "acts" like a server but was cheap. this has worked just fine for me and now I wish I hadn't bought the OC300 to begin with. IMO they need to release a hardware controller that is more powerful and supports the new advanced features if the OC300/OC200 cannot.
- Copy Link
- Report Inappropriate Content
@OrangeStreet Huh?I have an OC200 and it works fine........ cuts your speed alot yes but it's there, you sure you know what your doing? You need to make sure your running the latest beta or a fairly recent release.
I wouldn't go to a software solution for the simple fact if the VM goes down or whatever, your stuffed. Atleast with the OC200 ....... I can always connect to the network and get in anywhere.......
That said, WHERE IS THE WOL ???....... (Wake On LAN). Lots of things still missing from Omada. Even the Ubiquiti's I love how they tell you what alot of the traffic is on the dashboard like Windows Updates or whatever. TP Link needs a whole lot more refinement.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 15682
Replies: 63
Voters 1
