Early Access Omada SDN Controller_V5.13.30 Pre-release (Updated on Apr 10th, 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 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, just wondering if this version has fixed this bug: https://community.tp-link.com/en/business/forum/topic/648526
- Copy Link
- Report Inappropriate Content
Hi @ceejaybassist，
After confirming with Support Engineer, the Public IP refers to the IP through which the device establishes a management channel with Omada Controller. For Local Controller, if it does not span three layers, it will show the same IP address with the IP of the device itself. Thanks all for your valuable feedback, the R&D team will consider the optimization in subsequent versions of the Controller.
- Copy Link
- Report Inappropriate Content
Hi @reynhartono，
I have tested it on the lab controller and no the same issue, please check here:
All clients' MAC addresses are matched correctly when clicking Download by Sort.
- Copy Link
- Report Inappropriate Content
Hi @WM1,
WM1 wrote
Hi @Hank21, yesterday I upgraded my OC200 v1 controller to 'OC200(UN)_V1_1.29.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)'. Since then I notice that some of my access point are shown as clients in the Known Clients overview, once they start in the morning (with PoE Time Range). Please see below surrounded in red. Note the name of the last two access points, 'EAP225-Outdoor-B0-4E-26-E5-2B-B8' and 'EAP230-Wall-84-D8-1B-61-24-12'.
Can you reproduce the issue stably? How long two EAPs keep showing in the Known Clients overview?
Also, surrounded in blue I regularly notice three clients with almost similar MAC addresses showing up, while these clients are not in my network (all clients in my network have IP MAC Binding and DHCP Reservation).
Do you know the MAC Address from which client device specifically?
- Copy Link
- Report Inappropriate Content
@Hank21
Once you changed the order or move to the next page, try to click on one of the client. It will show different item with the clicked one.
This is the original order when I opened the Known Clients page. When I clicked on the first item, it displayed the correct client.
But when I moved to the next page and clicked on the first item, it still shows the first item from the first page. Clicking on the second item will also show the second item from the first page as if the client list is never changed.
- Copy Link
- Report Inappropriate Content
When on a device or log page, the page is refreshing every 10 seconds in a very noticeable way where the data disappears and the mouse indicator spins for 3 seconds and then the data reappears. I'm on an OC200 v1 and the 10 second refresh makes looking through any list excruciating. I'm hoping this is just specific to me, because if this was thought to be "OK", I would be very disappointed. Trying to find a new network device's IP when that page keeps reloading every 10 seconds made me turn to Fing instead. That's a controller usability fail.
Other feedback, I have only managed TP-Link omada wireless and wired switches on this network. When there is some of network loop, ports switch off and the reported information in logs is pretty useless "TL-SG3428 port Gi1/0/10 was blocked." How about... WHY?? for troubleshooting whereas every other brand of switch over 2 decades makes it dead easy to troubleshoot. All switches have "Loopback detection" enabled, but I've observed ports being blocked for what appears to be my laptop having moved from one switch to another (a walk 2-5 minutes away) and most likely roaming across two different AP's with my phone during that 2-5 minute walk. I'll also mention that I've never dealt with a switch in over 2 decades that couldn't handle this scenario without any issues. It gives TP-Link a black eye in terms of enterprise grade quality.
My biggest advice to you is to make sure that your TP-Link developers, support people and customer service people are all on a network using only TP-Link omada devices. This is known as "dog fooding it". This way, you'll have a better idea of how to implement ideas before going through a beta round of feedback. It is TOO slow for development and progress to do first level QA as betas all the time.
- Copy Link
- Report Inappropriate Content
@MaxBlitzer Its not specific to you, the controller doesn't refresh in real time, the download and upload speed of devices is also refreshed in 10 seconds. The mobile app is also horrific.
- Copy Link
- Report Inappropriate Content
Hi Hank,
can you pls add in the thread of the official release which are the differences with the Beta firmware and if it's suggested to downgrade the controller to the official release?
I'm talking in particular about OC300, but I think it's valid in general.
This is because the beta version went out earlier than the official release, but the official release has a version number earlier than the beta version.
Thank you,
Fra
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello @Hank21 ,
I just installed 5.13.30.10 onto an OC300 v1.
When I select a client on "Known Client", it opens the details of a different client. Check the Mac address.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 22515
Replies: 63
Voters 1
