08-30-2016 10:20 AM - edited 07-05-2021 05:45 AM
We have recently purchased 3802 APs for the first time, having always used 3702s.
I cannot get any of these 3802s to join a WLC. The usual discovery method is via the CAPWAP DNS entry (CISCO-CAPWAP-CONTROLLER.localdomain) and this is working fine for our 3702s so I know its set up right.
But even when deployed into the same VLAN, alongside 3702s the 3802s never seem to get to the DNS lookup.
I've connected a console cable to one of the APs and following boot up and getting an IP it just repeats the following. It never gets as far as trying to join a WLC and I don't understand why.
[*08/30/2016 16:08:53.1291] CAPWAP State: Init
[*08/30/2016 16:08:53.1292] CAPWAP State: Discovery
10-11-2017 12:19 AM
1. In your suggestion, you proposed AP and WLC should be in same subnet
I am saying if we are using option 43, this is not necessary.
2. I am here talking option 43 for cisco plug and play.
AP still does not get the IP address. Do you have any more suggestions?
12-19-2017 06:15 AM
We are experiencing the same problem. We have 1242, 3602 and 3702 access points connecting to our WLC using Option 43 (hex). I also tried using just the IP address, but have had no luck attaching the 3802 APs to our WLC. In our case, we are running 8.0.110.16 on our WLC because our 1242 APs do not support 8.2.
01-16-2018 02:14 PM
I have the same issue.... it gows on and on
[*12/11/2017 11:06:31.4030] CAPWAP State: Discovery
[*12/11/2017 11:06:31.4130] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
01-17-2018 12:40 AM
You can configure the WLC ip address on the Access point side and then AP can join the WLC
03-13-2018 12:43 PM
I have 160 AP's having this same issue configuring the IP on each for the WLC is not really an option.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide