Wireless Access

Hello,

- In my environment i have a master controller and 7 local controllers.

-  I have run into an issue where the master controller ap database shows access points to be in group A when they are really in group Z (as reported by the local controller ap database).

- The master controller also reports a specific AP to be down where as the local controller reports this AP to be up.

- If I select an AP on the master to reprovision, it has the correct group A selected by default already.

I seem to be having this issue with only 1 of the local controllers. Configurations are synched.

Any tips on where I can look to troubleshoot this issue?  

Thanks,

Matt 

What version of ArubaOS is this?  Are all controllers on this version?

Hi,

The master and all local controllers are running 6.1.3.0_32142

~Matt 

How many APs are on the local controllers and how many SSIDs are in use on each AP?

Depending on where the AP is there will be 2 or 3 SSIDs on the access point.  The affected groups only have 2 SSIDs.

master
=======================================================
Total AP Licenses : 648
AP Licenses Used : 17

LOCAL 1 -- the one with the issue
=======================================================
Total AP Licenses : 512
AP Licenses Used : 198

LOCAL 2
=======================================================
Total AP Licenses : 640
AP Licenses Used : 399

LOCAL 3
=======================================================
Total AP Licenses : 512
AP Licenses Used : 105

LOCAL 4
=======================================================
Total AP Licenses : 512
AP Licenses Used : 227

LOCAL 5
=======================================================
Total AP Licenses : 640
AP Licenses Used : 387

LOCAL 6
=======================================================
Total AP Licenses : 512
AP Licenses Used : 194

LOCAL 7
========================================================
Total AP Licenses : 512
AP Licenses Used : 401

You are under the published limits for the master (assuming it's an M3), so you shouldn't be seeing scalability issues.  I can't say for sure it will fix it, but 6.1.3.3 has a TON of resolved issues, so it might be worth upgrading.  If the problem persists, a TAC case would be the next step.

OR.. you can open a TAC case now and see if they can either fix the issue or give you a definitive answer whether 6.1.3.3 will address this issue.

Thanks for the advice.