3700-users not getting ip address

[Anjana A]

Hello Team,

AP Model: AIR-AP3802I-D-K9

AP-Mode: Local

WLC ios:8.10.151.0

Users not getting ip address, users struck in dhcp required state.

Ap associated with wlc in local mode.In the same location other users associating with other  AP's same mode(local) with the same model are getting ip address.

Isssue is with the only one AP.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

*Dot1x_NW_MsgTask_4: Dec 26 09:14:26.231: [PA] 90:cc:df:49:ff:15 Processing Access-Challenge for mobile 90:cc:df:49:f7:14
*Dot1x_NW_MsgTask_4: Dec 26 09:14:26.231: [PA] 90:cc:df:49:ff*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:f7:14 DHCP received op BOOTREQUEST (1) (len 308,vlan 200, port 8, encap 0xec03, xid 0x26295dc)
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:ff:14 DHCP (encap type 0xec03) mstype 0ff:ff:ff:ff:ff:ff
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:ff:14 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.10.10.10 VLAN: 200
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:ff:14 DHCP selected relay 1 - 10.10.10.105 (local address 10.79.54.134, gateway 10.10.10.10, VLAN 200, port
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:f7:14 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay:10.10.10.10 VLAN: 200
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:ff:14 DHCP selected relay 2 - NONE (server address 0.0.0.0,local address 10.79.54.134, gateway 10.10.10.10, VLAN 200, port
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:ff:14 Setting DHCP ReasonCode from (226) to (226)
*DHCP Socket Task: Dec 26 09:14:30.663: [PA] 90:cc:df:49:ff:14 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.10.10.10 VLAN: 200

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

Regards,Anjana

[marce1000]

 - Reboot the access point and check if that can help  ,

 M.

[Anjana A]

@marce  yeah tried twice.. but no luck

[marce1000]

 - I ran your original client debugging output through : https://cway.cisco.com/wireless-debug-analyzer/ which gives the output shown below (Show all flag was checked), though I have doubts whether it is relevant because it is rather short. Take a longer client debug session and run it trough the same tool , also check the controller configuration with https://cway.cisco.com/tools/WirelessAnalyzer/ , for that you need the output of the running config with no promts in between :
TimeTaskTranslated

Dec 14 17:11:39.886	*osapiBsnTimer	4-Way PTK Handshake, Client did not respond with M2
Dec 14 17:11:39.886	*osapiBsnTimer	4-Way PTK Handshake, Client did not respond with M2
Dec 14 17:11:39.886	*Dot1x_NW_MsgTask_0	Client has been deauthenticated
Dec 14 17:11:39.886	*Dot1x_NW_MsgTask_0	Client expiration timer code set for 10 seconds. The reason: Roaming failed due to WLAN security policy mismatch between controllers (configuration error). It can also be used to report EAPoL retry errors, and GTK rotation failure (in 8.5)
Dec 14 17:11:49.807	*apfReceiveTask	Client session has timed out

[Harikrishnan C]

remove from WLC and add it again 

[Rich R]

This looks like a duplicate of your post in blogs so I'll link to that for my answer:
https://community.cisco.com/t5/wireless-mobility-blogs/cisco-air-ap3802i-d-k9-user-not-getting-ip-address/bc-p/4747091#M767