EWC: AP Accessibility Report does not show any values
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-03-2017 06:05 AM
What conditions must be set that the AP Accessibility Report show any data ?
(Something to active or some special AP familiy)
A lot of my installations shows there no values (only zeros) or only 0,x values.
What is the benefit of this report ?? In which szenario can help me this report ?
(Why does Extreme create this report ?)
Manual is very poorly - no answer there regarding this question!
http://documentation.extremenetworks.com/wireless/ug/wireless/user_guide/c_ap_accessibility_report.s...
GTAC KB also.
Hopefully some here can help me.
Regards
(Something to active or some special AP familiy)
A lot of my installations shows there no values (only zeros) or only 0,x values.
What is the benefit of this report ?? In which szenario can help me this report ?
(Why does Extreme create this report ?)
Manual is very poorly - no answer there regarding this question!
http://documentation.extremenetworks.com/wireless/ug/wireless/user_guide/c_ap_accessibility_report.s...
GTAC KB also.
Hopefully some here can help me.
Regards
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-23-2017 12:46 PM
Hi,
FFI
you have the check this screen more often and chekc if really nothing shown.
But here more info's.
Q:
Why does the “cur” value for tx dissasoc show 0.13, should it not be 4 in 1 sec? Equally the peak should stay at 4 until 4 in a sec is exceeded? Similar can be seen in the other columns, Assoc req rx, reassoc req rx etc.
Can we have some details on how these numbers are calculated, I also noted there is a delay probably caused by the controller needing to receive data back from the AP that might skew these counters a bit more.
A:
The stats are collected as simple numbers of assoc, disassoc, etc. from the ap once every 30 seconds and calculated accordingly. The 4 disassoc in 1 sec becomes 4 disassocs in 30 sec which is the 0.13 disassoc/sec current value reported.
Also the algorithm for running average is:
Current average = 0.2 * current value + 0.8 * last average
Old values are overwritten since we are reporting a current and average value on a 30s cycle.
If nothing happanes after 30s it could we that we see only zero's.
Regards
Umut Aydin
FFI
you have the check this screen more often and chekc if really nothing shown.
But here more info's.
Q:
Why does the “cur” value for tx dissasoc show 0.13, should it not be 4 in 1 sec? Equally the peak should stay at 4 until 4 in a sec is exceeded? Similar can be seen in the other columns, Assoc req rx, reassoc req rx etc.
Can we have some details on how these numbers are calculated, I also noted there is a delay probably caused by the controller needing to receive data back from the AP that might skew these counters a bit more.
A:
The stats are collected as simple numbers of assoc, disassoc, etc. from the ap once every 30 seconds and calculated accordingly. The 4 disassoc in 1 sec becomes 4 disassocs in 30 sec which is the 0.13 disassoc/sec current value reported.
Also the algorithm for running average is:
Current average = 0.2 * current value + 0.8 * last average
Old values are overwritten since we are reporting a current and average value on a 30s cycle.
If nothing happanes after 30s it could we that we see only zero's.
Regards
Umut Aydin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-03-2017 10:29 AM
Matthias/Ron
I see the same behaviour in my lab, I will find out about this and let you know.
Regarding the documentation, please leave feedback there as well.
-Gareth
I see the same behaviour in my lab, I will find out about this and let you know.
Regarding the documentation, please leave feedback there as well.
-Gareth
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-03-2017 10:29 AM
Documentation Feedback is given ...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-03-2017 10:29 AM
Hi Gareth,
thanks for taking care.
For tracking this issue - GTAC Case: 01295841
Regards
thanks for taking care.
For tracking this issue - GTAC Case: 01295841
Regards
