Early Access Omada SG_3 Series Pre-Release FW for SDN Controller 6.1.X.X (Released on January 28th, 2026)
Early Access Omada SG_3 Series Pre-Release FW for SDN Controller 6.1.X.X (Released on January 28th, 2026)
This Article Applies to
SG3210(UN) 3.20
SG3210XHP-M2(UN) 3.0
SG3210X-M2(UN) 1.0
SG3218XP-M2(UN) 1.0
SG3428(UN) 2.30
SG3428MP(UN) 6.20
SG3428X(UN) 1.30
SG3428XF(UN) 1.20
SG3428X-M2(UN) 1.20
SG3428XMP(UN) 3.20
SG3428XMPP(UN) 1.0
SG3428XPP-M2(UN) 1.20
SG3452(UN) 1.20
SG3452P(UN) 3.30
SG3452X(UN) 1.20
SG3452XMPP(UN) 1.0
SG3452XP(UN) 2.20
Release Notes
New Features:
1. Add support for Type 8 (PBKDF2 with SHA-256) and Type 9 (Scrypt) password storage encryption type.
2. Add support for CPP (CPU protect policy).
3. Add support for MAC flapping.
4. Add support for packet capture.
5. Add support for ping and traceroute using domain names.
6. Add support for multiple RADIUS servers redundancy.
7. Add support for domain name RADIUS server.
8. Add support for RADIUS CoA & DM.
9. Add support for RADIUS accounting standard attributes Framed-IP-Address and Called-Station-ID.
10. Add support for IGMP auto-elect and TCN flood for IGMP.
11. Add support for Syslog protocol, custom UDP ports, and transmission over UDP/TCP with DTLS or TLS.
12. Add support for LACP fast timeout.
13. Add support for deleting quadruple binding entries by port.
14. Add support for displaying user configuration information based on interface VLAN.
15. Add support for configuring DHCPv6 relay by port.
16. Add support for RadSec in 802.1X authentication.
17. Add support for log filtering based on keywords.
Enhancement:
1. Optimize MAC group.
2. Optimize the initialization process and remove default username and password.
3. Optimize interaction between 802.1X and VLAN.
4. Optimize DDM configuration display.
5. Optimize log display for STP root bridge changes.
6. Improve packet capture functionality.
7. Improve FDB table display.
Bug Fixes:
1. Fixed the issue of QoS anomalies in specific scenarios.
2. Fixed the issue of wired client list display issues in certain scenarios.
3. Fixed some security vulnerabilities related to interaction with Omada Controller.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
(2) You may follow the following guide to upgrade your Omada devices. How to Upgrade/Downgrade Omada Switches
Firmware Download Link
Notes:
(1) The above firmware is applied to matching hardware.
(2) Your device’s configuration won’t be lost after upgrading.
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
If somehow you encounter an issue during or after the upgrade, it's suggested to contact us with the following info:
- Omada Controller version if you have any.
- Device Firmware version with Build number (previous and current)
If your model gets bricked during the firmware upgrade, you may follow the guide below to recover the firmware.
Configuration Guide How to Upgrade/Downgrade Omada Switches
Update Log
January 28th, 2026
Release of this article.
Recommended Threads
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada Router Related Issues [Actively Updated, Post for Subscription]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
First time posting here, but I’m having a really annoying problem with this firmware update.
Using software controller v6.1.0.19 and SG3210X-M2 v1.0 downgraded now to v1.0.16. Important note, this is my “core” switch and is also connecting 2 other buildings and we have around 70 clients connected most of the time.
The problem started after this update. At first, after the update CPU usage dropped from 25-30% (v1.0.16) to around 15% (v1.0.19) and I was like that is really nice. After 2 days my network started choking and packets were dropping all around the network (it is not visible in a graph, but CPU was above 80%). After restart everything was okay, but 2 days later same thing again. At one moment it managed to “fix” itself but soon after went above 80% and I had to reset it again. Since today was the third time, I decided to save devinfo and downgrade to previous version. No extra load was on a switch than usual, even when it was pushed in last year I never had any problems, but only after this update.
Did anyone else notice any CPU usage problems?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Are you switch routing and are the SVIs on this particular switch if you are?
Did you happen to try the earlier beta firmwares (late december) and did the same thing happen then?
Also, Does this happen on any other model switches with the latest late January Betas ?
- Copy Link
- Report Inappropriate Content
Yes, I’m switch routing and having SVIs, but only on this switch.
I did not try any beta firmwares, only stable releases.
I have a few more switches with latest January updates and some without.
SG2008P v3.20 with latest firmware (v3.20.17) and CPU is stable. Another switch is SG2218P v2.0 with latest firmware (v2.0.14) with CPU before and after update at 31%. Both are this latest January stable releases with no problems for more than a week now.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1383
Replies: 14
Voters 0
No one has voted for it yet.