DescriptionPerformance issue with 3.6-124 code
ScopeKB ARTICLE TYPE:
Troubleshooting
RELATED PRODUCTS: controller, AP200,
AP300
RELATED SOFTWARE VERSIONS:
3.6-124
KEYWORDS: controller, AP200,
AP300
SolutionWhen I run a ping test I
find that there is lot of latency over the air, and also low throughput.
The issue is on one specific SSID not on the
other.
STEPS
TAKEN FOR TROUBLESHOOTING:
STEP
1: | Created a new ssid called
test with default security profile and connected the client to it and
tested. |
STEP
2: | The client was able to give good
throughput,and there was no
issues. |
STEP
3: | When mapping the existing ssid
configuration to the current ssid test, found that the same station
(static station, connected to same AP) showed up performance
issue. |
STEP
4: | When isolating found that there are
performance issues with the ssid when the ssid broadcast was OFF. The
issue can be isolated using the following step
: --
Disable Rogue-AP detection and mitigation -this should fix the issue but
this is not the core
issue. --
Enable ssid broadcast (if end user doesn’t want to broadcast
the ssid, then need to disable the RogueAP detection and
mitigation. |
RESOLUTION: | Once we disable the
Rogue-AP detection mechanism the issue should be solved, since the issue
persist on one specific ssid but not on the other, finally led to
conclusion that its the hidden ESSID (broadcast OFF) which had some
issues. |
ROOT
CAUSE: | Issue was related to
hidden ESSIDs only. When the ESSID broadcast was disabled, the rogue
scanning got enabled even when there were clients associated and
connected, leading to poor client
experience. |
