Eash,
I apologize for the delayed response. Please post the output of " show ip dhcp binding" and "show ip dhcp conflict."
Before the router assigns an IP address to a DHCP client, the router which is acting as a DHCP server will ping the IP address that the router is intending to assign to the DHCP client to ensure that nobody is already using it. If the router gets a response then it will not assign this IP address and it will choose another one.
What might be happening here is that the router assigns the address because it did not receive any response and then all of a sudden a station hard coded with the same IP address comes up and tries to send traffic. Then the router will send the error message to the console reporting the conflict and it will try to assign a different IP address to the
DHCP client to avoid the conflict.
Based on the symptoms you described above, one possibility is that the pool was artificially depleted because conflict logging is enabled. That would explain why the PC's could not get addresses. If you do not configure any database agents, the recommended configuration is to disable conflict logging (i.e. "no ip dhcp conflict logging"). This allows the DHCP server to "forget" previously detected conflicts.
clear ip dhcp conflict : Deletes an automatic address binding from the DHCP database.Specifying address clears the automatic binding for a specific (client) IP address,whereas specifying asterisk (*) clears all automatic bindings.
So as far as the router is concerned, you should configure ‘no ip dhcp conflict logging’and ‘clear ip dhcp conflict’.
Let me know if this solves the issue or if you.
