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?

Hi mxk77, I have exactly the same issue as you. I had to restart my SG3210X-M2 switch every 2-3 days because of a significant slowness in my network. I also reverted back the firmware to previous version (1.0.16).

  @mxk77 

 

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 ?

  @GRL 

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.

  @mxk77 

 

Not sure what else it might be, i switch route on a SG3428X and a SG3218XP-M2 and both are operating normally on the vary latest firmwares.  

 

Have you tried a forget > adopt > reconfigure on that particular switch with the latest build on it?

  @GRL 

Thanks for ideas. I guess it is a SG3210X-M2 specific problem then, since @Karol2026 has the same problem and other switches we discussed don't have it.

 

I think the point here is that switch shouldn't be able to get into this state where it is unstable in predictable intervals with almost no load to the point it needs reset, specially since same configuration worked in previous firmware versions without any problems.

At least I'm not the only one with this problem, so devs might look into it considering most people might not post about it and just revert to previous one. I also want to help so this could be fixed in future versions and I'm not missing on new features due to instability from this version on.

  @mxk77 

 

Do try the forget/readopt/reconfigure and see if it helps, if not, i would stay on previous FW and see what the TP-Link team say