Aerohive Device SLA Compliance over Time?

  • 3
  • Question
  • Updated 4 years ago
  • Answered
I'm unsure of what the Aerohive Device SLA Compliance over Time graph in my dashboard represents. Does this refer to the health of wireless clients connected to my APs or the health of the APs connecting to the cloud controller? Most of the time the graph is entirely red.
Photo of Joel

Joel

  • 9 Posts
  • 0 Reply Likes
  • confused

Posted 5 years ago

  • 3
Photo of Praveen Raghuraman

Praveen Raghuraman

  • 55 Posts
  • 9 Reply Likes
Hi Joel,

The Device SLA Compliance Over Time graph shows the percentage of Aerohive devices that are SLA (service level assurance) compliant, non-compliant, or in danger of becoming non-compliant with SLA agreements.

You can drilldown on the chart to get a list of the APs that are non-compliant along with the specific violation counts.

Btw, which version of HiveManager are your running ?

See below for details on how compliance is established.

Compliant Devices: Devices are SLA-compliant if they did not have to provide a boost of extra airtime tokens to their clients to increase their throughput to meet the targeted minimum throughput level set for them in user policies.

Warning Devices: Devices are categorized as "Warning Devices" if their clients were able to change from being noncompliant to compliant after receiving an increased amount of airtime tokens.

Noncompliant Devices: Devices are not SLA-compliant under any of the following conditions:

CRC errors, dropped Tx frames, dropped Rx, Tx retries, or airtime consumption exceeded specified SLA violation thresholds.

(For information about the SLA violation thresholds, their default values, and how to modify them, see "Noncompliant Device Reports" under the Aerohive help.)
Photo of Joel

Joel

  • 9 Posts
  • 0 Reply Likes
Thanks for the response.

I'm running Hive Manager 6.1r1 in Express mode. Under User Profile>SLA settings, I'm using the default Targeted Minimum Throughput Level, 5,000Kbps, with Action set to log.

Does this mean that all of my APs are failing to provide at least one of clients with 5,000K of throughput?

How would you recommend that I adjust my SLA settings to make this graph more meaningful?
Photo of Praveen Raghuraman

Praveen Raghuraman

  • 55 Posts
  • 9 Reply Likes
Hi Joel,

Looking at the graph showing all red in quite unusual. There is a potential issue (bug?) we have seen in the 6.1r1 release with the SLA compliance graph although entirely certain about the problem.

I would suggest you write up a support ticket so that our team can track and investigate this issue further.

Thanks
Photo of Joel

Joel

  • 9 Posts
  • 0 Reply Likes
Thanks, Praveen. I'll open a ticket.
Photo of Manoah Coenraad

Manoah Coenraad, Champ

  • 72 Posts
  • 67 Reply Likes
Hello Joel,

Can you tell me if this issue is solved?
What was the solution?

Thanks:)
Photo of Joel

Joel

  • 9 Posts
  • 0 Reply Likes
Manoah,

No. I didn't find a solution and just stopped using that graph in the dashboard.
Photo of Praveen Raghuraman

Praveen Raghuraman

  • 55 Posts
  • 9 Reply Likes
This issue is being tracked as a bug and our engineering team is working on devising a fix. We will post an update once we have resolved the issue.

Sorry for the inconvenience.
Photo of Van Jones

Van Jones

  • 75 Posts
  • 4 Reply Likes
Was this fixed in 6.1r2a? We just upgraded to 6.1r2a and I have attached our current SLA graph. Is this normal if my SLA is set to 5000? Should my SLA be set to another number? Should I be using SLA at all since it will take away airtime tokens from other clients if a client's queue is too long?