Early Access Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
This Article Applies to
Omada_SDN_Controller_v5.14.32.3 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC200(UN)_V2_2.17.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC300(UN)_V1_1.26.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC400(UN)_V1_1.4.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
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 gateways: ER8411 v1.2, ER7412-M2 v1.2, ER706W v1.2, ER605 v2.2.
2. Added support for APs: EAP 772 v2.
3. Added support for Controller IP Access Rules in Global View > Settings > Account Security.
4. Added support for Upgrade Logs, Upgrade Schedules, Beta Firmware Program, Cloud Firmware Pool and other function in Global view > Firmware.
5. Added support for Audit Logs unit in Global View: user’s operations will be recorded to facilitate system maintenance.
6. Added support for configuring following features with Omada APP:
- Bandwidth Control
- Deep Packet Inspection
- IPS/IDS
- IP Group
- MAC Filtering
- Dynamic DNS
- WLAN Optimization
- Load Balancing
Enhancements
1. Optimized Backup, added support of selection of configurations and data.
2. Optimized Restore, data is no longer supported to be kept after restoring backup file, only configurations can be kept.
3. Optimized distribution of Export Data, added support for exporting data in the corresponding features module directly.
4. Optimized adaptability to SSL certificate, added support for importing certificate chain file of PEM format in Global view > Settings > System Settings > HTTPS Certificate.
5. Optimized default settings, enabled Fast Roaming, Gateway LLDP automatically.
6. Optimized the stability when using the terminal of devices.
7. Optimized the performance when managing clients in huge scale.
8. Optimized the Upgrade Schedule, added support to select model for upgrading, not single device anymore.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.17 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. Since version 5.14.32.2, Omada Software Controller no longer supports upgrade from Controller v4.
4. Since version 5.14.32.2, Omada Software Controller(windows) only supports installation on Windows64-bit platform.
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_Controller_Windows_v5.14.32.3
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
Omada_Controller_Windows_v5.14.32.2
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
Omada_SDN_Controller_v5.14.32.2_linux_x64.tar.gz
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
Omada_SDN_Controller_v5.14.32.2_linux_x64.deb
OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
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
Nov 8th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Update the Omada Software Controller pre-release version to the official release.
Oct 30th, 2024:
Remove download links for all the controllers 5.14.32.
Oct 28th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
Update the Omada Software Controller pre-release version to the official release.
Sep 26th, 2024:
Provide the following controller firmware for early access.
- Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
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
- Copy Link
- Report Inappropriate Content
a dark grey font, in a slightly lighter grey box, on a black background
(the server selection dropdown)
- Copy Link
- Report Inappropriate Content
Hi @GRL
To show the server list, we need to click that area one time,
After the list is displayed, the little arrow next to it should be up.
From your picture, it looks like the little arrow is down， which indicates you didn't click the servers.
Please try again.
If that's not the case, don't hesitate to let us know.
- Copy Link
- Report Inappropriate Content
I think you misunderstand
The server is selected. My cursor is in the IP address bx. Simply, the font inside the indicated box, when using dark mode, is dark and unreadable. In all other selection boxes in the interface - every area - it populates with a white font making it easily readable in dark mode. this one does not.
- Copy Link
- Report Inappropriate Content
Hi @RBL
How many gateways is the OC200 managed? Is the issue happening on a local WAN or a remote site WAN settings?
Currently, we received some feedback and all the affected sites are remote, not local.
We look forward to your reply.
- Copy Link
- Report Inappropriate Content
2 sites.
Local site - ER8411 - All OK
Remote Site - ER7206 v2 - Wiped WAN settings
Edit: the remote site effected is a direct WAN IN communication to the main site with NAT port forwarding.
I just turned on my 3rd remote site, that isnt always live, also a 7206v2, but is managed over a site-to-site ipsec VPN to the main site, this one also didnt have any issues.
- Copy Link
- Report Inappropriate Content
Hi @GRL
Thanks for the clarification. Now I understand.
The reason for this is to show that the profile selected here is an existing profile configured from elsewhere, and also to distinguish it from the other options which should be typed directly.
I'll give feedback and see if we can change the color to something more readable!
Thank you for your feedback.
- Copy Link
- Report Inappropriate Content
@Vincent-TP I have two WAN ports in use on a ER707-M2 v1.0 running the latest firmware version.
The OC200 is managing one gateway and only one site. Everything is local. That is why it was easy te setup the WAN settings again.
As I have two WAN connections in use:
- Connection Type: "Dynamic IP" no username and password or other settings besides a customized MAC address
- Connection Type: "PPPoE" with a username and password.
I found out both were missing the configuration as I had in my 1st connection customized the MAC addres and after updating it was gone, which caused the connection to fail. the second connection had lost configuration, but it was still set as a WAN port. As this one did not had its credentials anymore it was failing too.
Also the names of the connections (decriptions) were gone, so the entire config was gone for both WAN ports.
If I had only had one connection via DHCP and did not change the mac address in the settings, I would probably haven't noticed it. As I probably would not check the WAN page (Wired Networks --> Internet).
After configuring both WAN ports they resumed normal operation.
Besides the above:
- The load balancing settings were set to default settings.
- The Online Detection Interval was set to something different, cannot remember what is was.
- The internet capacity settings were empty and needed to be set again.
- Copy Link
- Report Inappropriate Content
Just found out that according to https://www.tp-link.com/nl/support/faq/4143/
I am missing the USER page in the Application Analytics:
This screenshot is from the support page":
this screenshot is from my omada:
- Copy Link
- Report Inappropriate Content
@Vincent-TP If we would downgrade to the latest stable firmware, would we lose all the configurations?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 7031
Replies: 53
Voters 1
