@downtheroad 

In theory config is saved on Controller. SO after FW downgrade the device will be adopted again according to your controller's saved settings :)

I have just done downgrade to my EAP and that's how it worked.

I know that EAP is not the same as Router, but that's the whole idea of having controller. All your settings are there so you shouldn't be woried about reconfiguring the device.

  @Clive_A Thanks for the information.  Thank you to the others as well.  I will try the reset when I get home.  I did roll back the firmware to 1.2.1 and it is much better.  It is down in the mid 20s.  The only thing added as late are the webhooks for all that I can see and they are still there with the roll back.  They are going to an ubuntu server and that is all working well.  I did export the logs and last night the CPU was so busy it had nothing from the 18th.  There were quite a number of java errors that I did see.  

Clive_A wrote

Hi @downtheroad 

Thanks for posting in our business forum.

downtheroad wrote

Super high CPU and a lot of heat (hot) since upgradinig firmware.  90%-97%.  Anyone else seeing this ?  Also, if I downgrade to prior version will I lose any config ?  Controller managed here.

Without touching the config or connecting any new device/cable to the network?

I would not think or believe it becomes like this suddenly.

Do a basic review of your physical connection. It could be the loop.

  @downtheroad This is just the firmware rollback change.

  @downtheroad 

As i indicated, my 8411 runs a pretty complex network with tons of traffic, IDS turned on, DPI turned on, 3 WANs.

Ignore the big spikes, i was configureing some stuff and rebooting - the rest is it sitting at very low CPU the whole time., even when loaded.  5-9% usually

Firmware 1.2.2

However, as i also said, i was getting CPU stats exactly like yours when i went from 1.2.1 to 1.2.2, without any config changes at all - jsut the firmware flash, until i did the GUI based factory reset/readopt which completely resolved it.

  @GRL  When I get home from being out of town on business I am going to do exaclty the process you followed. 9% and lower is much more like original before the 1.2.2 flash.  

I have this ER8411 a 3008 switch and will be adding a couple more switches soon.  Only about 70 clients here.  There are no loops in my network.  The OC300 is connected to my ER8411, my ISP fibre with static IP and then a mini dual port pc running OPNSense.  Only the connection off the transparent bridge leads to the ER8411/3008.  Everything else is off the 3008.  This has not changed.

  @GRL You are correct.  Staying on 1.2.1 and resetting on the device GUI.  Here is what it is now after readoption:

  @downtheroad 

yep!  glad it worked for you

The other thing i noticed when my 8411 got in the same CPU state, was even after a front panel button reset the issue remained......and what was even weirder was when i exported a standalone config back from it, instead of the usual ER8411_blah_blah filename, i got an OpenWRT_blah_blah filename !