03-13-2021 12:20 AM - edited 07-05-2021 01:22 PM
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
03-13-2021 01:42 AM
FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva34879/
M.
03-13-2021 02:41 AM
@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?
03-13-2021 10:27 AM
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:
03-14-2021 02:43 PM
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)?
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