Aruba Instant & Cloud Wi-Fi

Reply
New Contributor
Posts: 4
Registered: ‎05-22-2014

Channel conflict diagnosis

I see this a bit on our own IAP environment and at customers. It's hard to explain why the IAPs would choose the same channels for radios not too far away from each other. Our office is only 200sqm with three IAP-225's for example.

 

What diagnostic information can I get our of the IAPs or AirWave to determine why it has decided this is the best channel plan?Capture.PNG

Guru Elite
Posts: 20,562
Registered: ‎03-29-2007

Re: Channel conflict diagnosis

What software version is this IAP?  You could be running an older version of IAP where the channel selection is not so good.

What is your regulatory domain?  That will determine how many 80Mhz channels you have.

You are running 80mhz channels (E) in the 5ghz, so your channel choices are limited because you are bonding channels.  You should go to RF> ARM and change "80Mhz Support" to "Disabled".  You would then have 40Mhz channels on 802.11a (+/-) and give access points 20 minutes try to change to another channel.

 

Go to More> Support, then run "AP ARM RF Summary" command on each access point.  Under Channel  Summary, there is an intf_indx column.  The last number in parentheses () says how much interference each access point sees on a channel.  It is possible that your access points see too much interference on channel 11 to put an access point on that channel.

 

A short document on how ARM works is here:  http://community.arubanetworks.com/aruba/attachments/aruba/70/1204/1/ARM+Doc+Supplement.pdf

 

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

New Contributor
Posts: 4
Registered: ‎05-22-2014

Re: Channel conflict diagnosis

Many thanks for the reply Colin.

 

AU regulatory domain and latest early access code.

 

Overnight the APs arranged themselves on non-overlapping 5GHz channels. Curiously they are now all running on the same 2.4GHz channel and power has dropped down to 9. ARM history lists the reason as interference. ARM is working as expected then I guess.

Search Airheads
Showing results for 
Search instead for 
Did you mean: