Major Alarm

  • 1
  • Question
  • Updated 4 years ago
  • Answered
I've got a major alarm on one of my APs that reads "The current capwap delay time higher than threshold value."  Does anyone have advice on what it means and what can be done to prevent its recurrence?  The message language indicates it's more of an informational alarm than something horrifically wrong with the WAP, but I like to keep my logs clean regardless.  Consider me a member of the clean plate club.

Thanks!
Photo of Todd

Todd

  • 2 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
Which version are you running? I believe this was introduced in 6.2, you can go to the Home tab and select HiveManager Services to increase the capwap threshold...



Best,
BJ
Photo of Todd

Todd

  • 2 Posts
  • 0 Reply Likes
It looks like we're running 6.1.2 and 6.1.6, assuming I'm reading the proper screen properly.  I'm guessing we have a different version than you're running as I don't see the same menu options when I drill down through the administration screens.
Photo of Terence Fleming ThinkWireless

Terence Fleming ThinkWireless, Champ

  • 79 Posts
  • 27 Reply Likes

Looks like the CAPWAP threshold can only be set on HiveManager OnPremise, the option is missing on a HiveManager Online Account:


Photo of LB3

LB3

  • 12 Posts
  • 0 Reply Likes
We see this frequently on a BR200 connecting back to our CVG.  I've found that latency is the main cause of this error.  This error is more informational like you said.  I believe it is displayed when excess latency occurs between the AP/Router and the CVG/or hive.  No anything to be overly concerned with unless you see it all of the time, but I'm like you I would rather not get an alarm if it's not really going to cause any issues.  I'm glad they finally let you change threshold.
Photo of Terence Fleming ThinkWireless

Terence Fleming ThinkWireless, Champ

  • 79 Posts
  • 27 Reply Likes

Observing CAPWAP delay times can be a useful first step in troubleshooting, as it gives an end-to-end view of the quality of the communication path between AP and HiveManager.

We use this as an indicator of all sorts of non-wireless related issues: most commonly problems with the Internet connection (CAPWAP is one of the first things to get hit when the Internet connection is overloaded).

But sometimes one AP or another will be completely at odds with the rest, and I have never been able to work that one out when it only occurs intermittently  ...   :-)