Early Access Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
This Article Applies to
Omada_SDN_Controller_v6.0.0.23_Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.23_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.23_linux_x64.deb
Overview
We hope to offer you a chance to experience the new features added in the Controller v6.0.0.23 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
IMPORTANT NOTE
This version contains watermarks and is not recommended for production environment use.
1. Version Info
This version of the Controller is fully applied to the Omada APP of version 5.0.x or above.
Note: Omada APP 5.0.x has not been released yet. If you usually rely on the app for management, it is not recommended to upgrade your controller to this version.
2. Supported Device Models
For device models Omada Software Controller supports, refer to: Omada Cloud SDN Platform Compatibility List
- Added support for Access Points: EAP 787 v1.0.
- Added support for Gateway: ER701-5G-Outdoor v1.0, DR3650v(EU)1.20、ER706W-4G(EU)2.20、ER706WP-4G(EU) 1.20、ER706WP-4G(US)1.26、ER8411(UN)1.20、DR3220v-4G(EU)1.20、DR3650v-4G(EU)1.20、ER7206(UN)2.30、ER7406(UN)1.20、ER706W(EU/US)1.30、ER706W-4G(US)1.30、ER605(UN)2.30、ER707-M2(UN)1.30、ER7412-M2(UN)1.30
- Added support for OLT: DS-MCUA
3. New Features
- Added support for displaying VLAN information, offline devices, and isolated devices in the topology view in Site View > Dashboard > Topology.
- Optimized the Client list by adding support for offline clients, enhancing the advanced search capabilities for both online and offline clients, and introducing a new unified export feature in the top-right corner of the Client list. Additionally, the Past Connection page has been removed from Insights, and detailed client connection information can now be viewed in the Connection Logs section of the Client details page. The Known Client page has been removed, and all clients can now be directly viewed in Site view > Clients > All.
- Optimized Client detail layout with new Overview, Statistics, Connection Logs, Tools, and Config tabs in Site > Clients > Client Details.
- Added support for a client online-timeline in the Client detail view in Site view > Client > Overview.
- Added support for a Connection Logs timeline in Site view > Client > Connection Logs.
- Added support for Traffic, RSSI, Rate, and Speed trend charts in Site view > Client > Overview, gated by the Data Trend Record toggle.
- Added support for the Data Trend Record switch in Global view > Settings > History Data Retention to control client-level metrics.
- Added support for LAN Isolation configuration, a new VLAN setting designed for networks where an Omada Gateway serves as the DHCP Server Device, enabling segment isolation and editing based on this configuration in Site > Network Config > LAN > Isolation Settings and in Site > Network Config > LAN > VLAN > Add/Edit for Gateway devices running firmware version 5.15.
- Added support for a topology link diagram in Device > Device Details > Overview.
- Added support for an online/offline timeline in Device > Device Details > Overview.
- Optimized device detail layout with new log and tools modules in Device > Device Details.
- Optimized EAP/Bridge AP detail layout with updated config and statistics modules in Device > AP Details, and fixed mesh traffic chart accuracy in Device > AP Details > Statistics.
- Optimized Switch detail layout with expanded statistics and streamlined config access in Device > Switch Details.
- Optimized Gateway detail layout with new network view and config modules, plus added SIM and Transmission settings, in Device > Gateway Details.
- Optimized OLT detail layout with additional data charts in Device > OLT Details; added Management System Interface configuration under Device > OLT Details > Config > System > Central Management and streamlined config entries for ARP table and interface.
- Added support for OUI-Based VLAN on Switch 6.0 firmware in Site > Network Config > Transmission > OUI Based VLAN.
- Added support for custom DHCP Option on Switch 6.0 firmware in Device > Switch Details > Config > VLAN Interface > DHCP Server and Site > Network Config > LAN > VLAN > Add/Edit.
- Added support for advanced Multicast configuration on Switch 6.0 firmware, integrating VLAN, switch, and port associations and enabling IGMP/MLD Snooping options, in Global > Network Config > Network Settings > LAN > Multicast and Device > Ports > Config > Multicast Fast Leave / Device Config > Switch > Switch Ports > Port Profile > Multicast Fast Leave.
- Added support for STP Security on Switch 6.0 firmware in Site > Switch Details > Port Config and Device Config > Switch Ports > Port Settings / Port Profile.
- Added support for /31 subnet masks on VLAN interfaces on Switch 6.0 firmware in Site > Switch Details > VLAN Interface and Site > Network Config > LAN > VLAN > Add/Edit.
- Added support for Storm-Control with ratio configuration on Switch 6.0 firmware in Site > Switch Details > Port Config > Bandwidth Control and Device Config > Switch Ports > Port Profile > Bandwidth Control.
- Added support for Controller hot-standby redundancy in Global > Settings > Cluster > Hot-Standby Backup.
- Optimized LACP behavior so member ports remain blocked until aggregation succeeds, shown in Device > Details > Ports List.
- Added support for adopting and managing the OLT-X2 model in Device > OLT Details > Config > System > Board Control, including board-level upgrade, reboot, and configuration (firmware DS-MCUA1.1.0).
- Added support for multi-channel OLT configuration, removing the restriction that prevented standalone UI access while under Controller management (supported on DS-P7001-04, DS-P7001-08, DS-P8000-X2 with DS-MCUA ≥ 1.1.0).
- Added support for OLT adoption and management in Controller cluster mode (all models, production firmware scheduled for 2025-Q3).
- Added support for Network Check Tools—ping and traceroute—on OLT devices in Site > Network Tools > Network Check and Device > OLT Details > Tools > Network Check (all models and firmware versions).
- Added support for Device Management to configure OLT devices in Global View > Settings > System Settings, compatible with models DS-P7001-04, DS-P7001-08, and DS-P8000-X2 (DS-MCUA) firmware version 1.1.0.
- Added support for configuring Enhanced Open MLO SSID in Site > Network Config > Network Settings > WLAN, allowing MLO to be enabled when the encryption is set to None, effective for WiFi 7 devices.
- Added support for stream-mode packet capture, also known as remote real-time packet capture, in AP Details > Tools > Packet Capture and in Site > Network Tools > Packet Capture. This feature allows users to remotely monitor AP device packet capture interfaces via Wireshark, displaying captured packets in real-time to meet the needs of scenarios requiring live traffic analysis.
- Added support for Probe Response Maximum Retransmission and Probe Response Threshold configurations in Site Setting > Wireless Features > Management Frame Control > Probe Response Maximum Retransmission/Probe Response Threshold(The firmware of AP should support these features).
- Added support for adopting the Gateway 5G ODU model ER701-5G-Outdoor v1.0; configurations for IP-Passthrough mode reside in Device > Details, while standard routing mode settings are in Site View and Device > Device Details.
- Added support for EoGRE Tunnel in Device Config > EAP > EoGRE Tunnel to enable SSID extension across physical locations.
- Added support for custom logo upload in voucher printing in Configuration > Hotspot > Voucher Groups > Create/Edit Voucher Pattern and Voucher Group > Edit Voucher.
- Added support for the “Apply to all portals” option and daily usage limit for local users in Configuration > Hotspot > Local User.
- Added support for overriding default LAN DHCP settings during adoption in Network Config > Network Settings > LAN > Default.
- Added support for 23-language user-invitation emails aligned with user locale.
- Added support for single public-IP cross-NAT device adoption in Linux cluster mode in Settings > Cluster > Cluster Node List > Device Management Port/Device Discovery PORT/DEVICE MONITOR PORT, allowing multiple nodes to use a single public IP for device management by configuring mappings from discovery and management ports to different node IPs.
4. Enhancements
- Reorganized the Settings menu into Network Config and Device Config and added site-level configuration in the Device Details page.
- Optimized UI with refreshed theme colors, tables, forms, icons, and charts.
- Optimized VLAN configuration process in Network Config > Network Settings > LAN. a) Streamlined setup into three steps: Network Parameter, Select Device Port, and Confirm/Apply. b) Adjusted the modification process to align with the new setup steps. c) Enhanced the network display interface with UI improvements.
- Optimized Switch Port configuration by replacing Profile-based Native/Tag/Untag settings with per-port private configuration and introduced cross-device bulk management of Tag, Network, and Profile settings in Device Config > Switch Ports > Port Settings.
- Optimized Dashboard chart library with new Overview, Topology, Client, and Traffic tabs including AP Density & Activity charts in Site View > Dashboard. The original Dashboard custom dashboard function has been moved to Insight > Report.
- Optimized the Statistics menu by relocating Performance to the device details page, Switch Statistics to the Switch details > Port, and Application Analytics to Dashboard > Traffic, Insights > Application Analytics.
The position changes of the original content are as follows:Original Location
New Location
Performance
Device Details
Switch Statistics
Switch Details > Port
Application Analytics
Dashboard > Traffic, Insight > Application Analytics
- Optimized Insights menu by: a) Adjusting the menu structure to separate operational data from statistical chart data. b) Merging statistical charts for a unified display. c) Placing configuration records on their respective settings pages.
The position changes of the original content are as follows:Original Location
New Location
Session Limit
Gateway Details > Network View > Session Limit
Known Clients
Clients
Past Connections
Clients
Past Portal Authorizations
Hotspot > Authorized Clients
Switch Status
Configuration > Device Config > Switch > Switch Ports
Port Forwarding Status
Gateway Details > Network View > Port Forwarding Status
VPN Status
Configuration > Network Config > VPN > VPN Status
Routing Table
Gateway/Switch Details > Network View > Routing Table
Dynamic DNS
Gateway Details > Config > Advanced > DNS
Rogue APs
Network Tools > Interference Detection
Threat Management
Gateway Detail > Config > Network Security > IDS/IPS
QoS Data
Gateway Detail > Network View > QoS Data
- Optimized Reports framework with customizable tabs, card visibility/sort order, and multi-tab export in Site View > Insights > Reports.
- Optimized Report export functionality to support simultaneous packaging and export of multiple tabs in Insights > Reports > Export > Export Report. (For Linux, users are required to manually install Chromium version 120.0.6098.0 or higher).
- Optimized Logs by adding 30-day historical data filters in Logs > Alerts and Logs > Events, and relocating Audit Logs in Logs > Audit Logs, device-type filters in Logs > Settings > Alerts/Events > Content Settings, and Remote Logging in Logs > Settings > Advanced.
- Optimized Rogue AP into Network-wide Interference Detection for batch scans and per-device results in Site > Network Tools > Interference Detection. Currently, only EAP787 devices will display the corresponding rectangular chart of Wi-Fi interference results.
- Optimized wireless routing by displaying accurate maximum associated clients in Device > Wireless Router Details > Config > Wireless > Advanced and adding PPSK scaling in Network Config > Profile > PPSK.
- Optimized table persistence to save user-defined pagination across sessions in Devices, Logs, Clients, and Device Config > Switch Ports > Port Settings.
- Added inline explanations for each role in Account > Role via tool tips displayed when hovering over the icon.
- Added support for VOIP module templating in Site Template > Network Config > VOIP.
- Added display of the public IP for pending devices in Device List > Controller Connection IP.
- Added Device Reconnected log type and offline-duration tracking in Site > Logs > Events > Device.
- Added support for Switch syslog forwarding in Logs > Settings > Advanced when Client Details Logs is enabled.
- Optimized default RSTP and loopback-detection settings in Device > Switch Details > Config > Services > Loopback Control.
- Added edge-port risk warnings on STP configuration in Device > Switch Details > Port Config, in Device Config > Switch Ports > Port Settings, and in Device Config > Switch Ports > Port Profile.
- Optimized Switch onboarding by enabling adoption via custom management VLAN and auto-syncing related VLAN Interface, Port, and Static Route configurations in Device > Switch Details.
- Added Remember Device support for switch stacks in Device > Stack Details > General.
- Added routing table and OSPF neighbor display in Device > Switch Details > Network View.
- Optimized VLAN Interface capacity beyond 16 entries, device-dependent, in Device > Switch Details > VLAN Interface.
- Added support for gateway capability warnings in Network Config > VPN, in Network Config > Security > URL Filtering > Gateway Rules, in Network Config > Security > Firewall > Attack Defense, in Device > Gateway > MAC Filtering, in Device > Gateway > Dynamic DNS, and in Device > Gateway > IPTV.
- Optimized Portal IP auto-refresh behavior with manual input box in Global > Settings > System Settings > Access Config and in Site > Network Config > Authentication > Portal.
- Added support for batch-adopt result pop-ups in Global > Device List > Add Device > Auto Find and in Site > Device List > Batch Action > Batch Adopt.
- Optimized VLAN range expansion to 1-4094 for Switch/third-party devices and restricted to 1-4090 when Gateway or its LAN port is selected in Network Config > Network Settings > LAN.
- Added support for MSP customer limit increase to 500, customizable via omada.properties in MSP > Customer List.
- Added support for site search in Global > Settings > Export Data.
- Optimized temporary user permissions with risk warning in Accounts > User and in Accounts > SAML Role.
Bug Fixed
- Fixed load-balance ratio anomalies by auto-recommending optimal weights on WAN port changes in Network Config > Network Settings > Internet.
- Fixed wired/wireless traffic statistics inaccuracy and added Internet WAN-traffic charts in Reports > Summary > Traffic > All Network, in Dashboard > Traffic > Traffic (All Network), Reports > Summary > Traffic > Internet, and in Dashboard > Activity.( Traffic display may differ before and after controller upgrade)
- Fixed SSID Summary Report missing traffic data for some APs in Report > Wireless > Top 20 SSIDs (Traffic).
- Fixed Dashboard traffic chart inconsistency between “yesterday” and “last 24 h” selections in Report.
- Fixed search functionality for specific module tabs.
- Fixed SSL VPN certificate export failure when site name contains special characters in Settings > VPN > VPN Settings > VPN > SSL VPN.
- Fixed duplicate descriptions on the ALG introduction page in Transmission > NAT > ALG.
- Fixed iOS Omada App overwriting Local User name and phone fields in Hotspot > Local User.
- Fixed Open API documentation mismatch for Get site switch 802.1x setting by removing the “switches” parameter in Online Open API Document > Authentication > Get site switch 802.1x setting.
- Fixed CVE-2025-25193 by upgrading Netty version to mitigate DoS attack risk.
Notes
- Please note that Controllers on different platforms may have some differences in features, even if their first three digits of the version code are the same. For example, the Linux Controller currently supports Cluster Mode but the Windows Controller doesn't support it yet.
- The Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
- Since version 5.14.32, Omada Software Controller no longer supports upgrade from Controller v4.
- To strengthen overall security, we recommend upgrading all devices to the latest firmware.
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_v6.0.0.23 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.23_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.23_linux_x64.deb
Omada_SDN_Controller_v6.0.0.23 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.23_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.23_linux_x64.deb
Omada_SDN_Controller_v6.0.0.19 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.19_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.19_linux_x64.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
Sep 28th, 2025
New update for the following firmware:
Omada_SDN_Controller_v6.0.0.23 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.23_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.23_linux_x64.deb
Sep 19th, 2025
Update the following firmware:
Omada_SDN_Controller_v6.0.0.23 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.23_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.23_linux_x64.deb
Sep 5th, 2025
Provide the following firmware:
Omada_SDN_Controller_v6.0.0.19 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v6.0.0.19_linux_x64.tar.gz
Omada_SDN_Controller_v6.0.0.19_linux_x64.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
Hi @mbentley
Thank you for sharing.
We had located the root cause and have fixed it in the subsequent release. Please stay tuned.
mbentley wrote
I found out what is going on with random people seeing SSL cert errors. Here is a summary that hopefully someone from the development team can help address as while it can be worked around, it could be a problem for random people:
The Problem
Three JARs contain tpKeyStore:
- cloudsdk-1.2.3.jar (934 bytes) - NEW certificate (Feb 2025)
- device-gateway-core-6.0.0.23.jar (846 bytes) - OLD certificate (2018)
- omada-datatrack-6.0.0.23.jar (846 bytes) - OLD certificate (2018)
Non-deterministic JAR loading order: When using
-cp /opt/tplink/EAPController/lib/*, the JVM loads JARs in filesystem order, which varies by:
- Docker filesystem driver (overlay2, aufs, etc.)
- Kernel version
- Filesystem type
- Whether files were extracted, copied, or created fresh
Wrong keystore loaded randomly: ClassLoader.getSystemResourceAsStream("tpKeyStore") returns the FIRST tpKeyStore it finds in the classpath:
- If cloudsdk-1.2.3.jar loads first → Gets NEW cert (Feb 2025) → WORKS!
- If device-gateway-core-6.0.0.23.jar or omada-datatrack-6.0.0.23.jar loads first → Gets OLD cert (2018) → FAILS!
TP-Link rotated their CA in February 2025: Their cloud servers now present certificates signed by the NEW CA, but some users get the OLD CA from the wrong JAR!
Why It's Machine-Specific
- Same Docker image, but filesystem ordering varies
- Persistent data doesn't matter (it's not stored there)
- Copying to a new machine might change the JAR loading order
The Fix
TP-Link needs to:
- Remove duplicate tpKeyStore files from device-gateway-core and omada-datatrack JARs
- OR update all three keystores to contain the same certificate
- OR change code to use CustomSSLContext.class.getResourceAsStream("/tpKeyStore") instead of ClassLoader.getSystemResourceAsStream()
User Workaround
Users can force the correct JAR order by modifying the startup command:
java -server -Xms128m -Xmx1024m ... \ -cp /opt/tplink/EAPController/lib/cloudsdk-1.2.3.jar:/opt/tplink/EAPController/lib/*:/opt/tplink/EAPController/properties: \ com.tplink.smb.omada.starter.OmadaLinuxMain
- Copy Link
- Report Inappropriate Content
@mackworth Yes. It is.
- Copy Link
- Report Inappropriate Content
Failing when configuring a 4-Port Active or Passive LAG on POE Switch TL-SG3428MP.
Tried with regular ethernet ports. Also tried SFP ethernet modules. Tried forgetting/resetting/re-adopting switch. No luck no matter what.
No issues setting up LAG on SG3428 however.
| Succeeded |
CONNECTED |
SG3428 v2.30 |
2.30.9 |
| Failed |
CONNECTED |
TL-SG3428MP v1.0 |
1.1.13 |
| Device Name |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Device Management Hostname/IP |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Daylight Saving Time |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| IP Group (1) |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| IPv6 Group (1) |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Jumbo |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| LED |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Loopback Detection |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Management VLAN |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| LAN Networks (5) |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Port/LAG Name |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| SNMP |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| SSH |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Spanning Tree |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| IP Settings |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Time Zone |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| Device Account |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
|
| VLAN Interface (1) |
Apply | Oct 17, 2025 08:50:44 am |
Device failed to apply configurations. (ErrorCode: switch_100) |
- Copy Link
- Report Inappropriate Content
Interesting, i havent seen this at all on my SG3428X either Static or LACP LAGs, in fact it has 2 of them configured and have been running without issue.
What happens if you click "Apply Again" in the config failures ?
I get lots of Gateway config failures, generally hitting Apply Again sorts them out, sometimes i have to force provision the device. Havent seen any failures on any of my switches at all though
- Copy Link
- Report Inappropriate Content
Unfortunately tried that multiple times. I've actually been troubleshooting this on my own for 1+ week now. Tried literally everything. Commands in Omada LXC console on Proxmox. ChatGPT/Gemini. SSH into switch (although limited when adopted). No matter what I do results in "Failed" until I delete the LAG config. Tried 1 port, 2 ports, 4 ports. SFP, non-SFP. Tried Auto Speed, 1000mbps speed, Full Duplex. Tried reducing settings in Site settings, Port Profile settings, switch settings. Enable POE, disable POE. Settings in Auto, Spanning Tree enabled/disabled. Tried Trunk, Admin, other VLANS. Tried force provisioning, re-apply settings. Tried bare minimum settings. Nothing I do seems to do the trick unfortunately. With my other regular switch no issues though - although some settings will throw an "incompatible" result but after doing some settings tweaks and a force provision, the regular switch is back to "succeeded". I even tried ways to get the regular switch to say "Failed" with no luck haha. Something buggy is hapenning with just the POE switch :(
- Copy Link
- Report Inappropriate Content
Hi - I tried switching that off and the nag is still there along with these damn warning triangles.
It would be appreciated if this can be switched off as it appears when the page is refreshed.
As an aside, the three flagged devices appear to work flawlessly - not seen any issues even though they are "no longer supported".
Thanks
- Copy Link
- Report Inappropriate Content
Hi @iansj7
Thanks for the feedback. Is this only happens after update the controller to the V6? If you don't mind, please install a V5 stable software cotroller and adopt the POE switch with the controller and see if the same situation persist.
iansj7 wrote
Tried 1 port, 2 ports, 4 ports. SFP, non-SFP. Tried Auto Speed, 1000mbps speed, Full Duplex. Tried reducing settings in Site settings, Port Profile settings, switch settings. Enable POE, disable POE. Settings in Auto, Spanning Tree enabled/disabled. Tried Trunk, Admin, other VLANS. Tried force provisioning, re-apply settings. Tried bare minimum settings. Nothing I do seems to do the trick unfortunately.
>>>>To verify, Will these configurations take effect? Only the LAG doesn't take effect, right?
- Copy Link
- Report Inappropriate Content
@Vincent-TP am I missing it or is the Deep Packet Inspection per device gone with the new Omada controller?
- Copy Link
- Report Inappropriate Content
Are you saying OC220?
For hardware controllers, only OC400 support this feature.
Julian2111 wrote
@Vincent-TP am I missing it or is the Deep Packet Inspection per device gone with the new Omada controller?
- Copy Link
- Report Inappropriate Content
@Vincent-TP Hold on now, I have about 20 OC300s in the field doing DPI. Are you talking about just in 6.0? And if that's the case why would they remove it from the OC300 if you have a compatible gateway? The gateway does the scanning and sends the info to the controller for display. Hence why you can see the CPU and memory loads in the gateway and switches and not the controller. The controller doesnt really need monitoring.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 22000
Replies: 112
Voters 1
