Weird DHCP binding issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2011 09:47 AM - edited 03-07-2019 02:33 AM
Hi there,
I'm having trouble configuring DHCP binding for my LAN.
Although the DHCP pool has been working like a charm for several years, I tried to bind a server to an IP this morning, to no avail.
At first I thought I had misunderstood the client-identifier / MAC distinction, but it appears to be clear in my mind right now.
I followed the advices I gathered from community sites and Cisco guides and tried the following :
- debug ip dhcp server packet : no leasing between the client ID and the IP
- ip dhcp pool "test"
- client-identifier <here goes the mac address prefixed with 01>
- debug ip dhcp server packets
- disable then enable network interface on server
- server still has the same old IP, the debug didn't print anything
- show ip dhcp database returns void
I'm a bit confused, I also checked that there wasn't another DHCP server on the network.
My Cisco device is 877w, the server is connected to the network through ETHERNET (I read somewhere that DHCP binding through wireless LAN had its specific configuration gotchas).
Running conf is attached.
Best regards,
Rémy E.
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2011 11:08 AM
Hi,
I don't see any manual binding pool in your config ?
Regards.
Alain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2011 07:17 AM
Indeed, I had run "no" commands prior to posting this.
I modified my first post accordingly, the attached file now has a dhcp binding.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2011 01:44 AM
The DHCP Server was giving devices the IP they requested in the bootstrap stack of the dhcp request.
Configuring the router to ignore BootP requests fixed the issue, using command : ip dhcp bootp ignore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2011 01:51 AM
The DHCP Server was giving devices the IP they requested in the bootstrap stack of the dhcp request.
Configuring the router to ignore BootP requests fixed the issue, using command : ip dhcp bootp ignore
