Early Access Omada SDN Controller_V5.14.20 Pre-release (Updated on May 29th, 2024)
This Article Applies to
Omada_SDN_Controller_v5.14.20 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
OC200(UN)_V1_1.31.1_Build20240428(Beta)(Built-in Omada SDN Controller 5.14.20.21)
OC200(UN)_V2_2.16.1_Build20240428(Beta)(Built-in Omada SDN Controller 5.14.20.21)
Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214051.tar
Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214102.deb
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.14.20 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 letting us know about successful upgrades.
Release Notes
New Features
1. Added support for OLT devices: DS-P7001-04(UN) 1.1.0, DS-P7001-08(UN) 1.1.0.
2. Added support for gateways: ER7406(UN) 1.0, ER7206(UN) 2.20.
3. Added support for ES series switches: ES205G(UN) 1.0, ES205GP(UN) 1.0, ES210GP(UN) 1.0.
4. Added support for GPON APs: EAP610GP-Desktop, EAP615GP-Wall.
5. Added support for data statistics of OLT devices in Statistics.
6. Added support for Bandwidth Control and Port VLAN of GPON devices in Device > Properties windows > Port Status.
7. Added support for VoIP function in Site View > Settings, for which OLT devices supporting VoIP are needed.
8. Added support for Print Comments in Voucher: The content of Comments will be printed when printing the Voucher.
Enhancements
1. Optimized the interactive interface and automatic alarm removal in Logs.
2. Optimized channel and power deployment for the wireless network.
3. Optimized the logic of wireless roaming, and increased the stability of connection and experience of roaming.
4. Optimized the logic of topological identification, added support for third-party LLDP clients display as nodes in Site > Map > Topology, and enhanced the accuracy of network topology recognition.
5. Optimized the display of configuration status, and added status notice of configuration result in Devices > Device List.
6. Optimized the interactive interface of Online API Document in Global View > Settings > Platform Integration.
7. Optimized default wireless settings of new-created SSID, enabled 802.11r automatically when user created new SSID.
8. Optimized the logic of displaying Full-Sector DFS and Connectivity Detection, only after Mesh is enabled these functions can be accessible.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.16 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 the Windows version, Java 8 (or OpenJDK-8) and above are required. How to install Java Runtime Environment (JRE) for Omada SDN Controller on Windows?
4. For the Linux version, 64-bit Linux OS is supported and Java 8 (or OpenJDK-8) and above, MongoDB v3 and v4 are necessarily required. How to install Omada SDN controller on Linux system (above Controller 5.0.29)
5. Added a Beta watermark overlay to the interface. (For OC200 only)
6. Cloud firmware updates have been temporarily disabled in this beta version. (For OC200 only)
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 upgrading or downgrading.
(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.14.20_Windows (Pre-release version)
Omada_Controller_Windows_v5.14.20.8 (Pre-release version)
OC200(UN)_V1_1.31.1_Build20240428(Beta)(Built-in Omada SDN Controller 5.14.20.21)
OC200(UN)_V2_2.16.1_Build20240428(Beta)(Built-in Omada SDN Controller 5.14.20.21)
Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214051.tar
Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214102.deb
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 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
May 29th, 2024:
Provide the following controller firmware for early access.
- Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214051.tar
- Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214102.deb
Apr 30th, 2024:
Update the Omada Software Controller (Windows) beta version
- Before
Omada_SDN_Controller_v5.14.20_Windows (Pre-release version)
- After
Omada_Controller_Windows_v5.14.20.8 (Pre-release version)
Provide the following controller firmware for early access.
-
OC200(UN)_V1_1.31.1_Build20240428(Beta)(Built-in Omada SDN Controller 5.14.20.21)
-
OC200(UN)_V2_2.16.1_Build20240428(Beta)(Built-in Omada SDN Controller 5.14.20.21)
Apr 12th, 2024:
Provide the following controller firmware for early access.
-
Omada_SDN_Controller_V5.14.20_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
Bianco8 wrote
Hello @Hank21 , I have no messages in my mail box.
For sake of completeness, I'm using Omada SDN on Linux Debian container (hosted in Proxmox, if it matters).
This is the SSID configuration:
No particular configuration is set, just 3 SSID with WPA2/3 PSK, 1 is providing guest access via VLAN. I had no issues in the last 3 month, using this setup. I might test a rollback to the stable version to verify if that was the root cause.
The controller is connected to the same network via Linux bridge.
Thank you!
Hi @Bianco8
May I confirm the controller version you have tested? And what is the previous version of your controller before upgrading?
Besides, we have tried to send the email to your register email address again. Please kindly check the inbox again.
- Copy Link
- Report Inappropriate Content
mackworth wrote
@Hank21 I noticed something strange with the WLAN Optimization tool. I have 4 APs, 2 650 v1s (1.0.13), a 610-outdoor v1 (1.2.6) and a 650-outdoor (1.1.3). One of my 650s was running an old firmware (1.0.3) because I was trying to diagnose another issue but this morning I updated it back to 1.0.13. May 30 minutes later, I ran the WLAN Optimization tool but it only optimized 3 of my APs, leaving out the 650 that I had updated just before. Any reason why it would exlude that 650? There is nothing in the excluded list of APs.
Hi @mackworth
Will the controller optimize the EAP650 again at present? Have you tried to reboot the EAP or controller? After upgrading, you can go to devices page and reboot the relevant EAP and try again. Please share the screenshots of devices page and the page of optimization if the same issue occurs. And inform us the controller version. Thanks,
- Copy Link
- Report Inappropriate Content
Update Log
May 29th, 2024:
Provide the following controller firmware for early access.
Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214051.tar
- Omada_SDN_Controller_v5.14.20.9_linux_x64_20240522214102.deb
- Copy Link
- Report Inappropriate Content
Hello
I use freedns.afraid.org for my dyndns.
After upgrading my ER706W to 1.1.0 Build 20240523 Rel.71270(4555) AND linux controller to V5.14.20 - ddns is broken, since it is sending out only the real WAN IP (which is IP Adress of Fritzbox) and not the public internet IP as it was before the upgrade.
Does someone have same problem? Unfortunately I upgraded both simultanous so I can not say, is it router upgrade or controller upgrade issue.
ps: before the "upgrade" everything worked well.
ps2: the problem with ER706W that is limited to 100Mbit after reboot on WAN2 port still exists. After rebooting again, 1Gbit is working again.
Thanks
- Copy Link
- Report Inappropriate Content
I solved the issue on my own:
Afraid DNS custom update URL is:
http://[USERNAME]:[PASSWORD]@freedns.afraid.org/nic/update?hostname=[DOMAIN]&myip=[IP]
that was always working.
I deleted everything after [domain]
http://[USERNAME]:[PASSWORD]@freedns.afraid.org/nic/update?hostname=[DOMAIN]
and NOW the public IP is coming correctly.
- Copy Link
- Report Inappropriate Content
@Hank21
What do you mean by online documentation of api? Like is there an online documentation inside the platfrom integration page? We need a new api documentation.
- Copy Link
- Report Inappropriate Content
@Hank21 is this release eliminate as well the portal security issue that chrome and edge triger when trying to connect to the captive portal?
like this maasage client got a lot .
This page is not secure (broken HTTPS).
Certificate - missing
This site is missing a valid, trusted certificate (net::ERR_CERT_AUTHORITY_INVALID).
View certificate
Connection - secure connection settings
The connection to this site is encrypted and authenticated using TLS 1.3, P-256, and AES_128_GCM.
Resources - all served securely
Although the cert still valid.
Issued By
Common Name (CN)
localhost
Organization (O)
TP-Link
Organizational Unit (OU)
TP-Link
Validity Period
Issued On
Thursday, June 20, 2024 at 12:28:25 PM
Expires On
Wednesday, September 23, 2026 at 12:28:25 PM
SHA-256 Fingerprints
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 11689
Replies: 27
Voters 1