12-06-2018 08:55 AM
12-10-2018 08:07 AM
Hello Sam,
thanks for your answer. We're using HiveManager 8.2r1 (classic it should be).
So far, the AP is running since the "crash" without any problems.
12-07-2018 04:16 PM
Thank you for your patience, I was looking in to those logs for you, and unfortunately only our engineering team would be certain about what a kernel dump means. I could guess that it's noting issues about the CPU, but without more context I can't be sure. Could you enable CAPWAP debugs and pull tech data directly after you see the issue happen again?
CAPWAP debugs:
_debug capwap info
_debug capwap basic
_debug capwap stat
These will be erased if the AP reboots. You can also manually disable these at any time by adding "no" to the start of the command; for example "no _debug capwap info".
If you could confirm for me which HiveManager platform you are using, I can give you more specific instructions on how to get tech data; HiveManager Classic (myhive.aerohive.com) or HiveManager (formerly NG, cloud.aerohive.com)
Or you can get tech data via the CLI of the AP, this guide will review how to set that up- https://thehivecommunity.aerohive.com/s/article/Collecting-Tech-Data-via-CLI
We'll want to get tech data as soon after the issue happens as possible to have the best chance of seeing the even in the buffered log.