Hi All,
I have an RB960PGS.3 CAPs are connected and powered via POE. Adapter used in this router is 48POW. After upgrading to RouterOS 7.19.4 (routerboard firmware also upgraded) I can see this log messages. Earlier I had no problems. Does anybody any idea why? All cAPs run on latest 7.19.4, all routerboard firmware upgraded .
Please open a support ticket at https://mikrotik.com/support and attach a supout.rif file generated right after the issue occurs so we can investigate.
What RouterOS version did you come from?
Downgrading an option? *)
*) All my switches (including this model) run v6 LTS.
It seems to be rocket science (or a whack-a-mole game) to get the PoE firmware to operate correctly in all cases, there have been issues like that recently.
You can first try to install the 7.20beta on it, that may happen to fix it.
Downgrading is useless, the firmware on the PoE controllers will not be downgraded and the problem remains.
Thanks. I set poe "forced-on" on all ports where CAPSs are connected and it was OK. I've rebooted the hEX POE , and rebooted an wAP ax and no problem.
I've changes the settings only on 1 port connected to wAP ax back to "auto-on" and immediately I got error messages:
from 7.19.3 to 7.19.4 . I always upgrade to the latest. I know this is not the best, but I do.
Try the beta...
On hEX PoE or on CAPs or on all devices?
Only on the hEX PoE... to see if the PoE firmware update fixes it.
You can even downgrade back to 7.19.4 when you feel more comfortable running a "stable" RouterOS.
We recommend waiting for the next beta release, which will include an updated PoE-Out firmware.
OK, I did it, now that unit is on 7.20.beta7. Firmware too. I also set back the Poe to "auto" on all capable interfaces.
Log is clear now:
I come back with results.
As inra already wrote, you may want to try the 7.20beta8 that has now been released.
It has yet another PoE-out firmware upgrade...
