DHCPD Error - abandoning ip adress

[Jbrouer]

Hi All

i have an MSM760 mobility controller with firmware version  6.5.2.0-22155 .

Im experiencing problems that guest's cant logon to get a wifi connection, and i can see in the msg log the following errors:

Jun 20 10:37:28 err dhcpd Abandoning IP address 172.16.34.84: declined.

Jun 20 10:37:27 err dhcpd Abandoning IP address 172.16.34.83: declined.

Jun 20 14:44:42 err dhcpd Reclaiming abandoned IP address 172.16.36.150.

Jun 20 14:44:42 err dhcpd Abandoning IP address 172.16.36.124: declined.

Jun 20 14:44:41 err dhcpd Reclaiming abandoned IP address 172.16.36.124.

Jun 20 14:44:41 err dhcpd Abandoning IP address 172.16.37.214: declined.

Jun 20 14:44:40 err dhcpd Reclaiming abandoned IP address 172.16.37.214.

Jun 20 14:44:40 err dhcpd Abandoning IP address 172.16.33.226: declined.

Jun 20 14:44:39 err dhcpd Reclaiming abandoned IP address 172.16.33.226.

Jun 20 14:44:39 err dhcpd Abandoning IP address 172.16.36.218: declined.

Jun 20 14:44:38 err dhcpd Reclaiming abandoned IP address 172.16.36.218.

Jun 20 14:44:38 err dhcpd Abandoning IP address 172.16.38.218: declined.

Jun 20 14:44:37 err dhcpd Reclaiming abandoned IP address 172.16.38.218.

Jun 20 14:44:37 err dhcpd Abandoning IP address 172.16.39.69: declined.

Jun 20 14:44:36 err dhcpd Reclaiming abandoned IP address 172.16.39.69.

Jun 20 14:44:36 err dhcpd Abandoning IP address 172.16.36.53: declined.

Jun 20 14:44:35 err dhcpd Reclaiming abandoned IP address 172.16.36.53.

Jun 20 14:44:35 err dhcpd Abandoning IP address 172.16.39.45: declined.

Jun 20 14:44:34 err dhcpd Reclaiming abandoned IP address 172.16.39.45.

and the list goes on. The DHCP has been set on the controller, and it can give the follwing ip's:

start: 172.16.33.1

end: 172.16.39.254

gateway: 172.16.32.1

hope you can help

thx

[Arimo]

The client thinks this address is in use, and sends a DHCPDECLINE as a response to DHCPOFFER. This isn't an MSM issue, it's related to your client.

I'm sorry but can't help you further with this. I haven't seen this before.

[Vince-Whirlwind]

Try to identify - 

 - all the IP addresses currently leased out on the DHCP service

 - all the IP addresses currently in use on that segment (show arp on the router for that VLAN's subnet maybe)

Compare. 

Perhaps some people have statically-assigned themselves an address they had previously received via DHCP?

[Arimo]

One possibile cause for this would be having multiple DHCP servers in the same subnet. The clients would send the DHCPREQ as a bcast, they receive OFFER and ACK from first DHCP server. Then they receive the OFFER from the second server and since they already have a valid IP, this OFFER will be declined.