3802i access point stuck "waiting for uplink IPv4 configuration"

[MilanVerma17]

I have several 3802 WAPs getting stuck spamming "waiting for uplink IPv4 configuration" over console. LED is flashing red, green, pause. I am trying to install these 3802s in an existing wireless environment

[01/09/2021 16:21:00.2100] wired0 emac 0: link up
[01/09/2021 16:21:00.2600] wired0: link up
[01/09/2021 16:21:00.3100] wired0: started
[*01/09/2021 16:21:00.3576] aptrace_register_sysproc_fn: duplicate registeration for 'wired'
[*01/09/2021 16:21:04.4636] Waiting for uplink IPv4 configuration
[*01/09/2021 16:21:09.4647] Waiting for uplink IPv4 configuration
[*01/09/2021 16:21:14.4659] Waiting for uplink IPv4 configuration
[*01/09/2021 16:21:15.4661] Resetting wired0 and[01/09/2021 16:21:15.5000] wired0: stopped
restart DHCP client
[01/09/2021 16:21:17.5800] wired0 emac 0: link up

[marce1000]

               FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva34879/

 M.

[Leo Laohoo]

---

@MilanVerma17 wrote:

[01/09/2021 16:21:00.2100] wired0 emac 0: link up

---

Look at the time and date of the AP.  They off.  Way off.  

Is DHCP Option 43 enabled?

[Scott Fella]

You should look through the whole console output.  That should have information on why the ap's are not joining.  You can also run some debug commands on the wlc to gather data from that side.  Like what is already mentioned and from what has been mentioned in guides and on various threads:

1. Make sure the ap model is supported on the controller firmware version.  Look at the WLC matrix.
2. Make sure the time is correct on the controller, use ntp if possible
3. Make sure the country code on the AP is enabled or valid on the controller.  You don't want to power up an ap that is manufactured for a different country (regulatory domain)
4. Make sure the ap can discover the controller.  Easiest way is to place the ap on the same vlan as the controller if possible.  Subnet would need dhcp, and the ap should discover the controller.  Once the join is completed, you can move the ap back to whatever vlan the ap's are residing on.

[Rich R]

First: is the AP getting an IP address, in other words is DHCP working?

Then as @Leo Laohoo says do you have DHCP option 43 set correctly for the AP to discover the WLC (or using some other discovery method)?