07-03-2012 04:57 AM
We are deploying a wireless solution with 500+ ap-105. All the access points can find the controller (via DNS) and appear in the ap-configuration section. The problem is that some of them appear directly with ID flag (inactive and dirty/no config). I've tried to provision and assign them to their ap-group (via WEBui) but the provision fails. The access points seems to be not aware of this provision and do not reload to change their config.
The controller is a 6000 with M3. The access points are configured as remote ap.
The question is, could we recover those access points without going to the remote site and do a purgeenv locally?
Solved! Go to Solution.
07-03-2012 05:19 AM
Likely you can recover them... first step is that I would do an audit on the AP-GROUP that the APs are coming up into.
First question: Is this problem affecting only a single AP-GROUP? multiple AP-GROUPs? or ?
07-03-2012 05:38 AM
There are affected multiple ap-groups. Each branch office has an assigned ap-group and the access points with ID flag belong to different ap-groups. And in those ap-groups other access points have been provisioned without problem.
I am wondering why some access points could register themselves in the default ap-group with the I flag (and well-provisioned later) and others appear with the ID flag.
All the access points are new from factory. Could will it be due to the factory firmware release?
07-03-2012 06:03 AM
Is there surplus addressing.. in the VPN address pool. Worth checking how the addressing is doing in there (lots, close to capacity etc).
Are there log messages in 'show log all 50'
09-09-2012 09:29 PM
I don't mean to bring up old/dead threads, but I'm curious as to what fixed this. I have 2 ap's doing this now after a recent power outage and I'm in need of assistance. Addressing is not the issue and I only have one ap group since our current deployment is <30 ap's.