The controller loses connection with the access point.
My controller has version 4 and version 5 points. The latest firmware. But since the points are different, I noticed that over time, some points, exclusively version 4, gradually overflow their memory to 98-99 percent. After that, something like a processor load to 100% happens and the point is no longer monitored. At the same time, clients connect to it, there is access via sssh and the point responds to ping. If you delay the time, it may cease to be available, then only a physical reboot. What's the problem??? It happens with different v4 points, but not with all of them. With version 5, there is no memory overflow.My controller has version 4 and version 5 points. The latest firmware. But since the points are different, I noticed that over time, some points, exclusively version 4, gradually overflow their memory to 98-99 percent. After that, something like a processor load to 100% happens and the point is no longer monitored. At the same time, clients connect to it, there is access via sssh and the point responds to ping. If you delay the time, it may cease to be available, then only a physical reboot. What's the problem??? It happens with different v4 points, but not with all of them. With version 5, there is no memory overflow.
@Vincent-TP great if you fix it because for me in 5.1.6 for example the LLDP function is very useful. it's just a pity that it doesn't actually write the name of the device that you specify in the controller, but just the access point model.
Here is an example of a graph of one point after downgrading from 5.1.6 to 5.1.1.
as you can see on version 5.1.1 there are no memory leaks for more than a day. Although on 5.1.6 they were constantly and I had to reboot it so that the controller could see it.
