Beta Software Omada SDN Controller_V5.13 Beta (Updated on Feb 22nd, 2024) [Thread Closed]
Update as of Feb 22nd, 2024:
The 5.12 beta has been updated to official release, and this early access post is locked for further replies.
Omada Software Controller_V5.13.22 (Released on Nov 23rd, 2023)
Omada Hardware Controller_V5.13.24 (Released on Feb 22nd, 2024)
Any further questions or assistance needed with Omada SDN Controller, please feel free to contact TP-Link Tech Support by submitting a support ticket or connect with community by clicking Start a New Thread in the Business Community forums.
This Article Applies to
Omada_SDN_Controller_v5.13.22 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz (Ubuntu 16.04/18.04/20.04, Debian 8/9/10, CentOS 6/7)
Omada_SDN_Controller_v5.13.10_Linux_x64.deb (Ubuntu 16.04/18.04/20.04, Debian 8/9/10)
OC200(UN)_V1_1.28.1_Build 20231117 (Built-in Omada SDN Controller 5.13.24)
OC200(UN)_V2_2.13.1_Build 20231117 (Built-in Omada SDN Controller 5.13.24)
OC300(UN)_V1_1.21.1_Build 20231117 (Built-in Omada SDN Controller 5.13.24)
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. Expanded Language Support: Added language support for Română, Български, Українська, Српски.
2. 2FA: Added support for Two-Factor Authentication (2FA) in Global view > Account Security, all accounts will be asked for extra authentication to log in for higher account security.
3. DPI: Added support for Deep Packet Inspection in Site view > Settings > Network Security > Application Control, which helps you to manage your network traffic through Application Layer. (except the OC200 and OC300)
4. Batch Delete VLAN: Added support for Batch Delete VLAN in Site View > LAN, which allows you to delete mutiple VLAN at once.
5. Remember Device: Added support for remember of devices in Site View > Devices-Sidebar > Config-General, which allows your Controller to remember this device and automatically adopt it after it is reset and being found by your Controller.
6. Application result: Added support for display of application result of devices configuration in Site View > Devcies.
Enhancement
1. Device: Added support for hyperlink of uplink and downlink devices, which will jump to specific devcie page after you click the link. Besides, support more downlink information display in Switch > Details.
2. Sorting Optimization: Optimized sorting for the following locations:
- Firmware Version.
- DHCP Reservation.
- LAN Network.
3. Voucher Groups: Added support for code format of English Letters.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.13 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. 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 Beta 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.22_Windows(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.deb(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz(Beta)
Omada_SDN_Controller_V5.13.22_Windows
Omada_SDN_Controller_v5.13.22_Linux_x64.deb
Omada_SDN_Controller_v5.13.22_Linux_x64.tar.gz
OC200(UN)_V1_1.28.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC200(UN)_V2_2.13.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC300(UN)_V1_1.21.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC200(UN)_V1_1.28.2 Build 20240110 Full Release Note >
OC200(UN)_V2_2.13.2 Build 20240110 Full Release Note >
OC300(UN)_V1_1.21.2 Build 20240110 Full Release Note >
-
Download From TP-Link Global "EN" Website:
Omada Controller_Windows/Linux: https://www.tp-link.com/en/support/download/omada-software-controller
OC200 v1/v1.6: https://www.tp-link.com/en/support/download/oc200/v1/#Firmware
OC200 v2/v2.6: https://www.tp-link.com/en/support/download/oc200/v2/#Firmware
OC300 v1/v1.6: https://www.tp-link.com/en/support/download/oc300/#Firmware
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 22nd, 2024:
Update the OC200 v1/v2 and OC300 v1 beta firmware to official release.
-
Before
OC200(UN)_V1_1.28.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC200(UN)_V2_2.13.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC300(UN)_V1_1.21.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
-
After
OC200(UN)_V1_1.28.2 Build 20240110 (Built-in Omada SDN Controller 5.13.24)
OC200(UN)_V2_2.13.2 Build 20240110 (Built-in Omada SDN Controller 5.13.24 )
OC300(UN)_V1_1.21.2 Build 20240110 (Built-in Omada SDN Controller 5.13.24 )
Nov 23rd, 2023:
Update the Omada Software Controller beta version to official release.
-
Before
Omada_SDN_Controller_V5.13.22_Windows(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.deb(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz(Beta)
-
After
Omada_SDN_Controller_V5.13.22_Windows
Omada_SDN_Controller_v5.13.22_Linux_x64.deb
Omada_SDN_Controller_v5.13.22_Linux_x64.tar.gz
Nov 21st, 2023:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.28.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
- OC200(UN)_V2_2.13.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
- OC300(UN)_V1_1.21.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
Nov 3rd, 2023:
Update the newer Windows Omada Software Controller beta version.
-
Before
Omada_SDN_Controller_V5.13.9_Windows(Beta)
-
After
Omada_SDN_Controller_V5.13.22_Windows(Beta)
Oct 27th, 2023:
Add the following controller firmware for early access.
- Omada_SDN_Controller_v5.13.10_Linux_x64.deb(Beta)
- Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz(Beta)
Oct 8th, 2023:
Provide the following controller firmware for early access.
- Omada_SDN_Controller_V5.13.9_Windows(Beta)
Recommended Threads
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
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @OrangeStreet,
Thanks for your understanding and cooperation, other Forum member and @Clive_A will help you.
- Copy Link
- Report Inappropriate Content
DPI is great but what gateways does it support? I tested the er7206 and the 605 and its a no go.
Edit.: I am an idiot. I didn't verify that my router hasd the latest firmware. I updated and it works great. I am very impressed. Tp-Link give way more details that UNIFI. I like it.
- Copy Link
- Report Inappropriate Content
@lifetechmeda Can you please share some screesshots of the DPI menu?
- Copy Link
- Report Inappropriate Content
OC200 and OC300 will never get the DPI function?
DPI is an absolute core function for us and we would switch from OC300 to a Linux controller
- Copy Link
- Report Inappropriate Content
Hi @PHTP,
Thanks for your valuable feedback.
After confirming with the Support team, the DPI is not supported for hardware controllers due to the hardware limitation.
- Copy Link
- Report Inappropriate Content
I've been using Omada for 2 years now. As usual, I upgrade to 5.13.22 when I saw it this week. Right away, it does not work with my 7206 router and keep adopt, provision, config, connect, just keep changing status. Then I suspect it is my router that's running firmware 1.3 and not 1.4, though 1.4 is not available in Canada or US site, only from the Global site which is not recommended. I then install a new Omada in my PC with 5.12.7 simply to upgrade the firmware to 1.4. Things works like a charm as usual. Then I upgrade this new Omada to 5.13.22 just to try it out, no issue after upgrade.
I try to migrate from this new Omada back to my original Omada in docker, just a restore always fail. Migrate device was shown successful in new Omada but target Omada do not see them. As all devices shown as disconnected, I do factory reset on them in order to adopt back to Omada, adopt either failed, stopped at different stages, just not able to complete most of the time. Even with a successful config restore, devices still not connect properly.
I finally install a new Omada 5.12.7, and with a restore, all devices connect back and the right configuration. Feels like to me 5.13.22 cannot properly adopt my ER7206, EAP660HD or EAP650.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
1. when accessing "Online API Document" on #platformIntegration page, the OC200 freezes, the documentation page is also empty. It starts working few minutes afterwards when I get notification about 'devices are connected' from the omada phone app, so I am assuming some important service restarts.
2. Following endpoint does NOT work when using client with Viewer permissions, even though the client has All sites permission !!!
"${OMADA_URL}/openapi/v1/${CONTROLLER_ID}/sites?pageSize=1&page=1"
I saw this reported on previous beta version feedback, hope you guys won't miss this again.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 39011
Replies: 134