3802i not joining WLC or getting an IP address

[A_Marquez]

We recently received close to 200 3802i's to replace some older APs. I've been able to get over 80 of them configured without issue until this one individual AP. It appears to boot up fine but when it gets to the point that I would expect it to try and discover the WLC (A 5508 on version 8.5.151.0) it simply doesn't and goes to the login prompt. When I try to find the IP address for the AP it doesn't seem to exist. I plugged a different AP into the same port and that one booted up and joined the WLC without issue. Plugged the affected AP to a different switch port and same issue. The only other indicator I get that something is wrong is the alternating green and red lights flashing.

Doing a 'sh ip int brief' displays this:

Interface IP-Address Method Status Protocol Speed Duplex
wired0 unassigned unset up up 1000 half
wired1 n/a n/a down up n/a n/a
bvi1 unassigned unset up up n/a n/a
wifi0 n/a n/a administatively down down n/a n/a
wifi1 n/a n/a administatively down down n/a n/a

Any other ideas? 

[Leo Laohoo]

Console into the AP and post the complete output to the following command: 

sh capwap client rcb

[A_Marquez]

Heres the output for that command: Capwap process not ready yet. Try after few moments.
Error: Socket open failed

[Leo Laohoo]

---

@A_Marquez wrote:

Capwap process not ready yet. Try after few moments.

---

This error message appears when the AP does not get a valid IP address.

If that is the case, what settings is DHCP Option 43?

[Rich R]

- Did you try factory reset?

- Put the complete console log from power on in a txt file and attach here

[keithsauer507]

Did you ever get a resolution to this?
We got 14 of these and 1 out of 14 is experiencing the same problem.  I sent the show tech-support to Cisco.  They immediately RMA'd it.  Next day new one came in, its doing the same thing.  Very suspicious.  So I tried putting the switch port in diffrerent vlans and power cycling the port.  Won't get an IP.  One VLAN is actually a totally different DHCP server, so that rules out our Windows DHCP server.  Then I plugged it into the PoE+ port on a Comcast business cable modem - just to see if it was our switch issue.  Powers up but never gets an IP.   I tried it on two different switch stacks.  Nada.

sh ip int brief
Interface IP-Address Method Status Protocol Speed Duplex
wired0 unassigned unset down up n/a n/a
wired1 unassigned unset down down n/a n/a
auxiliary-client unassigned unset up up n/a n/a
wifi0 n/a n/a administatively down down n/a n/a
wifi1 n/a n/a administatively down down n/a n/a

[Leo Laohoo]

Post the complete output to the command "sh version".