Friday, February 1, 2019

Feeling dumb - DHCP with reservations on a Cisco 3850 switch

Long story short, I had to move several DHCP scopes from a Windows server onto my Cisco 3850 switch stack temporarily. Most of these are working fine. However I have a Management VLAN which only needs DHCP for our 3 AP's. When this scope lived on a Windows server, I just set up a network, excluded the entire range, and then added 3 reservations. Those reserved IP's were assigned to the AP's. No sweat. I'm trying to do similar on my switch with a scope built as follows:

!

ip dhcp pool Management

network 10.200.220.0 255.255.255.0

default-router 10.200.220.1

dns-server 192.168.1.20

domain-name domain.net

address 10.200.220.11 hardware-address 01de.adde.adde.ad

address 10.200.220.12 hardware-address 01be.efbe.efbe.ef

address 10.200.220.13 hardware-address 01ba.beba.beba.be

!

I tried the above both with and without putting the "01" before the MAC address. I don't really understand why it's there, but a web page I found online said to use it... and based on the command output below I decided to go with it. I also tried putting the line "reserved-only" in the scope above, the only difference is then it doesn't hand out any IP's at all.

Goofyswitch#sh ip dhcp bind

Bindings from all pools not associated with VRF:

IP address Client-ID/ Lease expiration Type State Interface

 Hardware address/ User name 

10.200.209.115 01ma.cadd.ress.01 Feb 01 2019 04:03 PM Automatic Active Vlan209

10.200.209.116 01ma.cadd.ress.02 Feb 01 2019 04:25 PM Automatic Active Vlan209

10.200.209.121 01ma.cadd.ress.03 Feb 01 2019 09:40 AM Automatic Active Vlan209

10.200.210.117 01ma.cadd.ress.04 Feb 01 2019 04:45 PM Automatic Active Vlan210

10.200.210.123 01ma.cadd.ress.05 Feb 01 2019 07:53 AM Automatic Active Vlan210

10.200.210.128 maca.ddre.ss06 Jan 31 2019 09:11 PM Automatic Active Vlan210

10.200.210.129 01ma.cadd.ress.07 Jan 31 2019 10:26 PM Automatic Active Vlan210

10.200.210.130 01ma.cadd.ress.08 Feb 01 2019 02:06 PM Automatic Active Vlan210

10.200.210.131 01ma.cadd.ress.09 Feb 01 2019 01:53 PM Automatic Active Vlan210

10.200.220.4 01be.efbe.efbe.ef Feb 01 2019 04:32 PM Automatic Active Vlan220

10.200.220.11 01de.adde.adde.ad Infinite Manual Selecting Unknown

10.200.220.12 01be.efbe.efbe.ef Infinite Manual Selecting Unknown

10.200.220.13 01ba.beba.beba.be Infinite Manual Selecting Unknown

Goofyswitch#

So with the reservations I have set up in the scope, why is the switch handing out 10.200.220.4 to my AP? I've only rebooted the one AP so far as a test. The MAC associated with 10.200.220.4 is identical to the MAC I'm trying to hand 10.200.220.12 to.

On an unrelated note, what's with the 01's appearing before the MAC addresses and why doesn't that 10.200.210.128 system have a 01 in front of it? It's the only system which seems to be behaving that way I don't get it.



No comments:

Post a Comment