topic This could be a bug in Wireless

3802i access point stuck "waiting for uplink IP address and reachable default gateway"

Justin Kistler — Mon, 05 Jul 2021 14:28:40 GMT

I have several 3802 WAPs getting stuck spamming "waiting for uplink IP address and reachable default gateway" over console. LED is flashing red, green, pause. I am trying to install these 3802s in an existing wireless environment. We use DHCP option 43.

Now the really odd part is that out of a batch of 100+ 3802s, it seems about half of them have this problem. All are new from the vendor. Some of them come right up, get an IP, go into CAPWAP discovery, etc... The other half gets stuck at this point, where it doesn't get an IP, any gateway info, etc. To clarify, on the same switchport, some of them work, some of them don't. This switchport works fine with every 3702 and 3602 I have put on it.

On the switch, the AP shows in the mac address table but not in the arp table. Interface shows up/up.

I cannot see any difference between the WAPs that work and those that don't. Same model number, same IOS code. I tried factory reset by holding mode button during boot for 20+ seconds. Still nothing. I am running out of ideas here. I am hoping some of you can get me pointed in the right direction. I have attached the boot log as well as a few additional commands in a text file.

Thank you much all.

This could be a bug

Rasika Nayanajith — Wed, 02 Aug 2017 20:02:48 GMT

This could be a bug

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

I would go with 8.2.160.0 software version, if current version is different to that.

HTH
Rasika
*** Pls rate all useful responses ***

Rashika,

Justin Kistler — Wed, 02 Aug 2017 20:08:56 GMT

Rashika,

Thanks for the response. I did see this bug report earlier but noticed that it was for IOS version

8.2.111.25 but my APs have 8.2.141.0.

Also, why would some of the 3802's exhibit this behavior and others wouldn't if they are running the same code of IOS?

8.2.111.25 but my APs have 8

Rasika Nayanajith — Wed, 02 Aug 2017 20:26:26 GMT

8.2.111.25 but my APs have 8.2.141.0.

Do not 100% rely on those info available in bug descriptions. It does not clearly stated fixed in 8.2.141.0 , except "no one reported this issue on the latest image of 8.2 throttle"

There are lots of issues with 2800/3800 in all code releases. With 8.2, it is highly recommend to go for 8.2.160.0 as that got most bug fixes specific to 2800/3800 AP model.

Also, why would some of the 3802's exhibit this behavior and others wouldn't if they are running the same code of IOS?

I would check the serial number of affected one and working one & see they came from different batches

HTH

Rasika

Re: 8.2.111.25 but my APs have 8

Amine Nouasri — Wed, 23 Aug 2017 09:05:07 GMT

Did you manage to resolve this is issue by upgradig the software? I have the same problem on a 3802I but the IOS code is 8.3.102.0.

Re: 8.2.111.25 but my APs have 8

kdavison007 — Wed, 20 Sep 2017 19:50:48 GMT

How can you upgrade a 3802 in this state if it's not getting an IP and connected to a WLC?

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

GREG MARTIEN — Tue, 10 Oct 2017 17:38:23 GMT

I have 2802i and just upgraded my test controller to 8.2.161 and having the same issue on about 8 Ap's out of 45 total at one of my sites.

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

GREG MARTIEN — Tue, 10 Oct 2017 18:20:25 GMT

The soulution we found for our issue with the 2802i on this message waiting for uplink IP address and reachable default gateway fix just 2 min ago. Our 4500 is the DHCP server at this site just for the AP's, we had to add a helper addres to the Vlan which the AP's are in and all 8 came back up.

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

Tommy Vindvik — Tue, 06 Mar 2018 14:49:13 GMT

I have the same problem.

Ww are in the progress of expanding our WiFi coverage with around 300 AP's.

Roughly 50% of 3802AP's seems to have a problem with DHCP even running on the same version. These are the two images I have tested on:

Primary Boot Image : 8.5.120.0
Backup Boot Image : 8.2.151.0

8.5 reports "Waiting for uplink IPv4 configuration", and 8.2 "waiting for uplink IP address and reachable default gateway"

---

Brastax001 — Wed, 21 Mar 2018 10:23:22 GMT

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

Brastax001 — Wed, 21 Mar 2018 10:22:25 GMT

Hi Guys... I have experienced the similar issue with the 3800 series APs where few get an IP address and some don't. What I have done to resolve this is to remove the DHCP scope on my core switch and saved the settings. I then added the same config config for the AP DCHP pool. This fixed my issue. I had about 4 sites that experienced this issue and I only resolved them by doing that.

Just to add, the new 3800 series APs comes up as unknown when you connect them for the first time. Nothing is wrong there you just need to point the new APs to the controller (Configure AP vlan on the core) then configure the switchport with a Native vlan so the AP can download the firmware from the WLAN controller...

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

Binish — Fri, 23 Mar 2018 09:01:48 GMT

Hi,

I too have the same problem.

I am running on code 8.3.133.0 and seeing the same error on few of the access point model AP3802i

"waiting for uplink IP address and reachable default gateway"

-- Binish

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

Rasika Nayanajith — Fri, 23 Mar 2018 19:06:57 GMT

Hi Binish,

I have responded to other thread given below, which I believe same issue. Have a look & see.

https://supportforums.cisco.com/t5/other-wireless-mobility-subjects/2820i-ap-5508-wlcs-dhcp-relay-dhcp-not-working/m-p/3353809#M83345

HTH

Rasika

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

ajurekic — Thu, 08 Nov 2018 01:36:31 GMT

Can you please explain what this means: "I then added the same config config for the AP DCHP pool."

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

Brastax001 — Fri, 09 Nov 2018 18:07:57 GMT

Hi Ajurekic, mind my typo with double config...

Basically when you deploy Access Points to a site having a Wireless LAN Controller you need to have an AP management VLAN then create a DHCP Scope for your Access Points. Once you assign the management Access Point (Native VLAN X) to a Swithport then the AP will get an IP address from your DHCP Scope.

In my case I applied a negate statement for my DHCP Scope as the APs I had for the Warehouse to deploy were about 90 but only about 68 access point could join the WLAN Controller. So the DHCP scope stopped assigning the IP addresses to new APs. Removing the DHCP scope and adding it again resolved the issue. My core switch was the Cisco 3850.

DHCP Scope example:

ip dhcp pool AP_POOL_VLAN120
network 10.4.16.0 255.255.255.0
default-router 10.4.16.254
dns-server 10.1.0.50 10.1.0.51
option 43 hex f104.a553.2563

Oh I use Option 43 hex "mac address" for my configs

I hope this helps..

Re: 3802i access point stuck "waiting for uplink IP address and reachable default gateway"

otsileseturumane — Wed, 29 Jul 2020 09:49:47 GMT

good morning Cisco experts i have a problem with AIR-AP1832I-EK9 with the same problem. error "waiting for uplink IP address and reachable default gateway". assist as am new to this environment. please assist