I got the complain of disconnecting issue when they have a conference meeting via skype.
So, I started to looking at the AP status in WLC, and I found some interesting result in there.
Basically, I've found that 'noise profile and interference profile is failed' in AP monitoring.
when I googled some document to know what that is.. that it is kind of SNMP alerting from ap to wlc.
we can tune up the threshold in RRM >> General setting, but, it won't be help to address that issue.
What action need when I detect the profile failed? Do I request to find any non 802.11 device around that access point?
I'm wondering what should I do to clear the issue so that those threshold can be resided in configured threshold.
any how way to configure it in individually access point rather than global configuration?
Ok, so you know the AP people are complaining about? Post the complete output to the CLI command of "sh ap auto-rf 802.11b <AP name>".
Good gosh! I can't read that.
Can you put the output in a text file and "attach" to this thread?
More-- or (q)uit
There are more outputs that needed to be added to the file.
Uhhhhh ... What country is this AP installed in? The reason why I'm asking is because ALL the channels for 802.11b are enabled. This is NOT best practice.
Only enable Ch 1, 6 & 11.
I firmly believe this is the reason why the Interference Profile is "Failed".
I reviewed my findings and above post is correct.
The neighbor access-points only use 1,6,11 so DCA is correctly configured. The information for the other channels is generated by the off-channel scanning which is being done by default for all the allowed channels within the specific country. The "failed" is being caused due to the 10% interference on channel 11, this is the default threshold which might be to low depending on the RF environment.
I would start with a site survey to make sure that the 802.11a/n/ac (5Ghz) service is perfect and 802.11b/g/n (2.4Ghz) is as good as possible. Next step is to make sure that your clients actually use 802.11a/n/ac. Also check the other parts of the infrastructure (especially internet access due to using Skype).
Please rate useful posts... :-)
Thanks for your point of view, so, in the matter of channel interference failed, how can I address this issue? is that means there are some wireless device using and conflicting with channel 11? any how to find it?
would it be better to focus on 5G since it's less interference than 2.4G? so, we need to know the poor quality client and check their h/w, and status?
Yes, I would focus on the 802.11a/n/ac by making sure that the coverage for that spectrum is solid and leave the 802.11b/g/n only for clients which do not support 802.11a/n/ac.
Things that might help to limit the interference on 802.11b/g/n are limiting the amount of your SSIDs, disabling radios in case of high density and search for certain non-WiFi interference like bluetooth for example. However, there is a big chance that the interference is being caused by something you don't control or can't fix (for example neighboring networks). Because of this I configure a little higher threshold for 802.11b/g/n most of the times.
Please rate useful posts... :-)