Most likely the APs are getting overloaded and are missing their echo packets. The HiveManager and the APs have a call and response check-in system that allows them to confirm that each side of the connection is still responsive; these call and response packets are called echos. There is a specific time window within which an AP would need to respond to an echo to be considered still responsive. If the AP misses a certain number of echos back to back, it is considered disconnected until it responds again. If an AP is still connected to the internet and passing traffic while missing echos, it's likely due to latency on the network; the AP is unable to process the echo request quickly enough due to the amount of traffic it has to process before responding. To confirm that we are missing echo packets, we'd want to SSH in to an AP to enable CAPWAP debugs and then collect tech data.
This guide reviews how to enable CAPWAP debugs: https://thehivecommunity.aerohive.com/s/article/CAPWAP-debugs
These guides review how to get tech data, depending on which HiveManager platform you are using:
HiveManager Classic-https://thehivecommunity.aerohive.com/s/article/How-to-download-tech-data-in-Classic
HiveManager NG-https://thehivecommunity.aerohive.com/s/article/How-to-download-tech-data-in-HiveManager
Device CLI-https://thehivecommunity.aerohive.com/s/article/Collecting-Tech-Data-via-CLI
If you'd like to send the tech data to me for review, my direct email is communityhelp@aerohive.com.
