We have deployed about 40 of these and about half have found the controller. The others have not. I have used option 43 in the past but lately they were able to find the contrller without that. I also took out the lwapp-controller name out of dns as we have 4 buildings of these etc. Should I put the controller name in dns and what is that default name.
In the logs I have a bunch of AP not joined message with the "Number of message retransmission to the AP has reached maximum" message. It has an ip address which I can ping so it is still there.
If the AP's are not on the same subnet as the controller, and you are not using Over the Air Provisioning, then you need to use DHCP Option 43, put your DNS entry back in, or set the controller address manually via the console port on the AP.
The host name for the DNS entry is CISCO-LWAPP-CONTROLLER. If you're adding that entry, then you might want to also add CISCO-CAPWAP-CONTROLLER pointing to the same address. While I believe that all current AP's will try to resolve CISCO-LWAPP-CONTROLLER (even if they are CAPWAP APs), this may not be the case in the future.
We use the DNS feature and then set the AP's appropriate primary/secondary controller after it joins.
Here's a good article about the AP join process:
Here's a good article about troubleshooting AP's that won't join:
thanks for your links. These are in the same subnet and are already mounted in the ceilings. I may try putting the controller at version 4 and letting them get in and then do the upgrade process to 6. Weird that some got in and some 100 feet away did not.
Since these APS are in the same subnet can't I just enable over the air provisioning? I know there is a vulnerability but this is a pretty much self contained building. The DNS trick did not work.
Console into one of the LAPs, and in enable mode, use the command "config ap controller ip address
I would like to console in but they are mounted up in the ceiling. I tried installing older versions of 4 but only 18 APS showed up. When I upgraded back to 6. the 34 I did have came back so nothing lost there. I tried dhcp option 43, I have the controller listed in dns. I have OTAP enabled, I have Master controller enabled. Still nothing. The APS will not let me telnet or web in to them. I'm out of ideas. I may have to open a TAC to get this done.
1 - Try cold booting the troublesome APs?
2 - Try disabling Master Controller mode.
3 - Try to telnet/ssh into the AP's and issue the command that Leo posted
You mention the 1141s (presuming you mean the 1142s). Those are not supported prior to WLC 5.2, so they won't join a 4.x version of the WLC.
Yes I mean the 1142 and I know that they won't go below 5.2. So far I found that the contractor didn't have enough network jacks to plug all the APS into the network so that could be my problem on those. :)
The other thing I'm going to try tomorrow is just to hit the reset button on the AP, unplug its power and repower. I think that sets it back to its native state. Could be a simple fix.
In the end it ended up that the APs were not plugged into the network. Sorry if I had many people trying to figure this out. I do have one that is being cantankerous but it is only one.
In my latest building I have a contingent of aps that tried to join. I can use a web browser to get a web login page but it says it is not remote mode and won't let me. I tried rebooting the controller as the ones that didn't join say they have reached the maximum amount of tries.
It means I'm going to have to physically go there Monday morning.