access point does not receive dhcp

[Sabespnoc]

I have two controllers, one AIR-CT5508-K9 and another Cisco Catalyst 9800-CL, what is happening is the following:

The old access points model AIR-AP1832I-Z-K9 only associate with the new 9800 controller, in the old one it associates but does not receive DHCP, what could it be?

[Daniel Ordóñez Flores]

Hi @Sabespnoc 

There are some possibilities, one is the the AP already have an IP configured; To figure out console the AP and type "show ip inter br"

The other options are relate to DHCP, WLAN, and VLAN. If you're sure that everything in the LAN is working fine, be sure that your switch port where the AP is connected, is working as access if you're working with a local deployment or as trunk with native VLAN is you're working with remote sites.

[Sabespnoc]

Thank you in advance for your attention, the ap came with the factory configuration, the switch is on default vlan 1
Even forcing the ap on the old controller, it does not associate only with the new one.

[Daniel Ordóñez Flores]

Hi again @Sabespnoc 

Be sure that network (switching & routing ) are working fine. Question, if you put your computer in the switch port where the AP is connect it gets an IP address?

Can you share the complete output of AP boot process?

[Sabespnoc]

Good afternoon, switching and routing everything ok
When I put a computer on the door it gets the IP via DHCP but I like to leave it with a fixed IP

P1416.9D50.4F48:capwap ap primary-base WLC_CC4 10.7.8.52

AP1416.9D50.4F48#show capwap ip config
IP Address : 10.7.254.245
IP netmask : 255.255.255.0
Default Gateway : 10.7.254.1
AP1416.9D50.4F48#

AP1416.9D50.4F48#capwap ap primary-base WLC_CC4 10.7.8.52
AP1416.9D50.4F48#[*04/11/2024 23:12:44.0054]
[*04/11/2024 23:12:44.0054] CAPWAP State: Discovery
[*04/11/2024 23:12:44.0054] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:12:44.0054] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:12:44.0154] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
AP1416.9D50.4F48#capwap ap primary-base WLC_CC4 10.7.8.52
AP1416.9D50.4F48#show capwap ip config
IP Address : 10.7.254.245
IP netmask : 255.255.255.0
Default Gateway : 10.7.254.1
AP1416.9D50.4F48#[*04/11/2024 23:13:13.4661]
[*04/11/2024 23:13:13.4661] CAPWAP State: Discovery
[*04/11/2024 23:13:13.4961] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:13:13.4961] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:13:13.4961] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

AP1416.9D50.4F48#[*04/11/2024 23:13:42.5870]
[*04/11/2024 23:13:42.5870] !!!!! {watchdogd} Unable to reach gateway for 300 seconds
[*04/11/2024 23:13:42.9169]
[*04/11/2024 23:13:42.9169] CAPWAP State: Discovery
[*04/11/2024 23:13:42.9169] Discovery failed 5 times. Check Release/Renew DHCP AP CAPWAP MODE:[1] controller previously connected:[0]
[*04/11/2024 23:13:42.9169] CAPWAPd forces DHCP restart.
[*04/11/2024 23:13:42.9269] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:13:42.9269] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:13:42.9269] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/11/2024 23:14:12.3777]
[*04/11/2024 23:14:12.3777] CAPWAP State: Discovery
[*04/11/2024 23:14:12.3877] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:14:12.3877] Discovery Request sent to 10.7.8.52, discovery type STATIC_CONFIG(1)
[*04/11/2024 23:14:12.3877] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[Daniel Ordóñez Flores]

Hi @Sabespnoc 

Because you report "AP don't get an IP Address" the best choice it's to don't use static ip address in your AP to check if is getting an ip address or not.

Now, question, if you ping 10.7.8.52 with source 10.7.254.0/24 did you reach the successful  the WLC?

[Sabespnoc]

10.7.8.52 is the new controller, I set the IP to 10.7.254.245 and it works normally, I'm going to reset the AP and do new tests with it trying to get the DHCP IP.

[Sabespnoc]

Good morning, the AP is getting IP via DHCP but it does not associate with the controller, only with the new one, I left the AP running on the 9800 controller.

[Sabespnoc · Accepted solution]

Good afternoon and sorry for the delay, I did several tests and it didn't work, as the equipment is no longer under warranty I couldn't open Tac on Cisco, I left it working on the new controller.
Thank you very much for the support.