Hello,
the short version: CAPSMAN forwarding is full of bugs. The "fun" begins if you have ~1000 clients on the CCR controller, doing some traffice (500 Mbps/30000 sessions)...
Long version: No time today to tell you all things today.
So, let´s make it short:
- CCR will crash in certain high load situations
- CCR will disconnect all caps if you configure settings which let´s the CAPSMAN reprovision the CAP devices
=> They will disconnect an reconnect
On cAP ac clients disconnect, because 5 GHz interface is unstable. Some say the driver module crashes and reloads
Until:
Version 6.46beta59 has been released.
*) ccr - improved general system stability;
*) wireless - improved IPQ4019, QCA9984, QCA9888 wireless interface stability;
I don´t know whether this will solve your problems. Btw, do you also seee thousands of ~DHCP offer no lease messages in your logs?
=> Imagine you sit in front of one cAP, you can see.
=> Your notebook connects to the cAP but it doesn´t get any IP.
=> You disconnect and reconnect but your notebooks doesn´t get any IP.
=> You look on the DHCP server within the CCR and you can see the timer from the offer goes down from 30 seconds to 0 until it restarts at 30 seconds again. It stays on "offered" but nothing happens
=> Until you hit the provisioning button for the cAP and guess what happens your notebook gets an IP address immediately afterwars
=> Now you have this problem on 300 cAP device running on the CCR/CAPSMAN. Sometime the clients work without any problems for some hours until there is more load on the CCR. So starting at ~10:30 am each day I see "DHCP offer no lease" within the logs. 6.46beta59 doesn´t help. Noone knows why and I did everything this forum asked me to do.
=> The solution for me: Drop CAPSMAN, use single access points with local management and local forwarding. Sad? Of course.
The load was distributed to all cores on my CCR1036 devices with CAPSMAN based forwarding enabled.