04-17-2013 12:39 PM - edited 03-07-2019 12:52 PM
I had thought this was working, but it isn't working after all. Turns out that even though I have this configured on the router, the computer hardware-address 01f0.def1.9b01.df it still being assigned a different IP address rathar than the .26 that should be assigned per the config.
I have this in the config:
!
ip dhcp pool bloomberghost1-tmirg
host 192.168.12.26 255.255.255.0
hardware-address 01f0.def1.9b01.df
!
ip dhcp pool data
network 192.168.12.0 255.255.255.0
default-router 192.168.12.1
dns-server 192.168.2.50 192.168.1.50
lease 30
This is what I see on the router:
SF-RTR-01#show ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
192.168.12.7 01f0.def1.03a7.17 May 08 2013 06:35 PM Automatic
192.168.12.8 01f0.def1.356d.43 May 08 2013 03:53 PM Automatic
192.168.12.9 01f0.def1.9b01.df May 08 2013 09:17 PM Automatic
192.168.12.26 01f0.def1.9b01.df Infinite Manual
SF-RTR-01#
You’ll see the last two entries are the same hardware address, which is the user’s mac.
For some reason, it won't assign that address the .26. Rather it gave it an address from dhcp.
I'm researching as to why, but thought I'd post my results.
This location only has a router/switch no servers. Any ideas would be helpful.
Solved! Go to Solution.
04-17-2013 01:27 PM
Hi Raquel,
The value you specify on the hardware-address statement is in fact the client-identifier. The mac address is only 6 bytes long.
Configure the proper mac address on the hardware-address statement or configure
client-identifier 01f0.def1.9b01.df
instead of
hardware-address 01f0.def1.9b01.df
Hope this helps
04-17-2013 01:27 PM
Hi Raquel,
The value you specify on the hardware-address statement is in fact the client-identifier. The mac address is only 6 bytes long.
Configure the proper mac address on the hardware-address statement or configure
client-identifier 01f0.def1.9b01.df
instead of
hardware-address 01f0.def1.9b01.df
Hope this helps
04-18-2013 09:12 AM
Great, I'll give that a try. Funny thing is yesterday, after I left the site for this router, I was thinking that, just had yet to try it.
Would it also make since to exclude that IP address from DHCP so that it's not given to any other client?
Thanks, let me see if that will work.
04-18-2013 09:18 AM
Hi Raquel,
It does indeed make sense to exclude the static addresses from the dynamic pool.
Regards
04-18-2013 09:40 AM
Hi,
It will not be given to another client as it is tied to the client-identifier.
Before doing the manual lease you'll have to clear the dynamic binding though with clear ip dhcp binding x.x.x.x
Regards
Alain
Don't forget to rate helpful posts.
04-26-2013 09:12 AM
Changing it to client-identifier is exactly what the issue was. It was right there in front of me the whole time. Thank you for all your help.
-Rocky
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: