Beta Software Omada SDN Controller_V5.13 Beta (Updated on Feb 22nd, 2024) [Thread Closed]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
Hi @Shoresy，
The issue mentioned in your initial post is the port displayed issue of the switch, which has been located and will be fixed in the subsequent update of the Controller.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
V5.13.9 does connect to the cloud. You just need to force the controller to recognize it by turning off in "Global View" then on as it comes with the default off. The program may not default to being connected to the cloud. You may need either wait for it to update or force an update refresh by turing off and then back on. This refresh requirement is more of one required by the Java subsystem and not the controller software. I thought about this and I can't come up with a quicker refresh method. Some of the settings may not be updated when first enabled after a controller update, but it should update withing minutes to match the database.
- Copy Link
- Report Inappropriate Content
I can't even turn it off...when I attempt to turn Cloud off in the Global view i get an "invalid request type" error in the web UI. When attempting to launch the controller from anything other than the local PC the Omada software is running on, I get a 404 error. Unless another updated 5.13.9 installer was released...there's no way the 5.13.9 installer I used had Cloud connectivity enabled. I also see watermarks on the background "Confidential Only for Test" on every page.
TP-Link support changed the description for this firmware noting that it will not connect to the Cloud once installed, it can only be accessed locally on the host PC where it is installed.
- Copy Link
- Report Inappropriate Content
@Hank21 in this version the Export of the Heat Map doesn't work fine.
- Copy Link
- Report Inappropriate Content
Hello @RiccardoBertoli,
Thanks for reporting this issue to TP-Link Business Community!
Did you click on the Simulate on the Heat Map page?
What is the error message after you click on the Export?
- Copy Link
- Report Inappropriate Content
@Hank21 Blank screen, and the controller stuck. I need to refresh browser's page.
Yes, I click on simulate on both 2,4 and 5 GHz.
- Copy Link
- Report Inappropriate Content
Hello @RiccardoBertoli,
The Heat Map issue you mentioned has been located by the R&D department and will be fixed in the subsequent update of the Controller.
Update: This Heat Map issue has been fixed here: Omada_SDN_Controller_V5.13.10_Windows
- Copy Link
- Report Inappropriate Content
Hank21 wrote
Update on Oct 23rd , 2023:
Update the Windows Software controller firmware, which fixed some issues.
Before
Omada_SDN_Controller_V5.13.9_Windows
After
what is new apart from adopt/provisioning loop on access points?
applies to all access points at all locations, both local and remote
these access points are affected.
EAP653, EAP670, EAP610-Outdoor, EAP225, EAP225-Outdoor
Upgraded from 5.13.9 which worked to 5.13.10
Tried restarting the power, but that didn't help.
downgraded to 5.13.9 again.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 38909
Replies: 134
Voters 4
