Early Access Omada SDN Controller_V5.13.30 Pre-release (Updated on Apr 10th, 2024)
![](https://static-community.tp-link.com/icon/9315142a471f4c8ca35011ade4feb548.jpeg)
Update as of Apr 10, 2024:
Thank you all for your valuable feedback on the Beta firmware!
The official firmware of 5.13 controller 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.21 Build 20240401
OC200(UN)_V2_2.14.21 Build 20240401
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
Hi @Hank21
Theres a problem on this firmware. I have set all my voucher to have a pause time, and if theres a blackout going on in my area, the customers who have connected the wifi using voucher wont expired. There was 1 customer who purchases 1hr voucher and it didnt expired, he used 29gb of download. And when i check the system settings the time and date was not sync everytime theres a blackout so i need to manually resaved the system date and time settings in order for it to sync. Its a hassle
- Copy Link
- Report Inappropriate Content
@wickedcool13
My OC200 v1 also crashed after firmware update to 5.13.24 yesterday. I will share quick steps I did to recover, maybe it will save time to another users.
After latest upgrade to 5.13.24 from Omada Cloud web interface my OC200 v1 failed. Status was of controller wa Offiline, Clod led was blank, Connection led (Eth1) was blinking.
I did recovery and updated manually to the same version using firmware file from tp-link webpage --> OC200 --> Support page. Shortly reset button 6secs, POE power supply + wire to PC, 192.160.0.253, firmware file --> Update OK. But I believe this step is not required.
After firmware upgrade I loged in to OC200 locally (FallBack IP defined during setup), in my case it was 192.168.8.252 and I found that Cloud access is enabled, but status is Offline in the Setting --> Cloud Access tab.
To resolve the issue I disabled and enable this setting again and controller went up again.
I believe Tp-link engineers should release 200% verified firmware releases so users can do updates ith confidence, without gambling as this is having big impact and affects millions of people. I spent 2 extra hours to resolve the issue and this time is on tp-link engineers who do not fully debug new releases.
- Copy Link
- Report Inappropriate Content
@Hank21 Any idea when OC200(UN)_V2.6 firmware will be available. I am trying to switch from a software controller to hardware controller and since I updated my windows controller last week and now try to move the hardware controller this week I am stuck with incompatible versions.
- Copy Link
- Report Inappropriate Content
![](https://static-community.tp-link.com/icon/9315142a471f4c8ca35011ade4feb548.jpeg)
Information
Helpful: 2
Views: 16168
Replies: 63
Voters 1
![voter's avatar](https://static-community.tp-link.com/icon/c188b9abc4a544f59a7962a438df2174.jpeg)