The internet is kinda gone for 5 min., suddenly getting up and running again.
The other 19 AP's does not get the problem, and they are not loosing internet doing the time this specific classroom AP does.
What does "The current capwap delay time lower than threshold value" mean in a detailed explanation?
How can i perform fail searching/fix this capwap delay? Why does it appear?
:S Hope you guys can point me in some direction.
Model Number AH-HM-NR-1U
Thats the hive manager information. Its OLDDDDD. But Free :D
We have the Hivemanager locally on the school. No cloud.
There has actually been some some cable errors in that building, that was never fixed for real.
I believe that just a very small disconnect is enough to show the failure?
The AP is "White" all the time, never turning "Blue" or "Green".
What should i check on even more? I did a check on switch, but didnt seem to tell me anything.
Certainly cabling could be a contributing factor. Have you the necessary equipment to check end to end cable continuity? - checking switch ports for errors is also a worth while practice.
I'm having the same issue.
Hivemanager on premise (VM), version 6.8r2. We have over 600 x AP230's running 6.5r4.
Recently noticed a few AP's will timeout connection to HM. Usually around 2 - 4 at a time, they will reconnect anywhere between 5 minutes to an hour later. Isn't always the same AP's, can be random out of the >600 AP's we have. Alarm on HM shows capwap delay time lower than threshold.
Client connectivity is affected to the AP's in question. Connection will just drop out, then re-establish again when AP is OK.
Can ping affected AP's but response time is noticeably higher than normal (20-50ms instead of 1ms). Attempting to SSH onto AP will sometimes work, otherwise times out. When connected via SSH the CLI is very slow and unresponsive. When attempting to run any command (e.g. "show cpu" or even "exit"), more often than not get an error message such as "ERROR: cli ui wait reply timeout".
Rebooting affected AP seems to resolve the issue, but cannot keep rebooting over 600 AP's!
Currently have this logged with our network support who are talking to Aerohive about the issue.
Personally I suspect a firmware problem.