Cant get DHCP lease on router in vrf from wifi client.

[sjones7000]

Hi all,

I have a router acting as a DHCP server on a VLAN in a vrf

When I connect a wired client directly to the VLAN it all works fine and I get a DHCP assignment.

The problem is that wifi clients do not get a DHCP assignment

The Cisco WLC has an interface in the VLAN in question (4.4.4.5) and the router can ping the WLC interface.

The WLC is working in proxy mode for DHCP.

DHCP config is..

ip dhcp pool TESTING
 vrf TMD
 network 4.4.4.0 255.255.255.0
 default-router 4.4.4.1
 dns-server 208.67.222.222 208.67.220.220

Interface config is..

interface GigabitEthernet0/1/0.500
 description ** TESTING ONLY **
 encapsulation dot1Q 500
 ip vrf forwarding TMD
 ip address 4.4.4.1 255.255.255.0
 ip nat inside

Debugs on router when the wifi client tries to connect..

Jul 20 14:26:35.870: Option 82 not present
Jul 20 14:26:35.870: DHCPD: Reload workspace interface GigabitEthernet0/1/0.500 tableid 2.
Jul 20 14:26:35.870: DHCPD: tableid for 4.4.4.1 on GigabitEthernet0/1/0.500 is 2
Jul 20 14:26:35.870: DHCPD: client's VPN is .
Jul 20 14:26:35.870: Option 82 not present
Jul 20 14:26:35.870: DHCPD: DHCPDISCOVER received from client 0128.bab5.0dac.e2 through relay 4.4.4.5.
Jul 20 14:26:35.870: Option 82 not present

Jul 20 14:27:07.293: DHCPD: Sending notification of DISCOVER:
Jul 20 14:27:07.293:   DHCPD: htype 1 chaddr 28ba.b50d.ace2
Jul 20 14:27:07.293:   DHCPD: remote id 020a000004040401080001f4
Jul 20 14:27:07.293:   DHCPD: table id 2 = vrf TMD
Jul 20 14:27:07.293:   DHCPD: giaddr = 4.4.4.5
Jul 20 14:27:07.294:   DHCPD: interface = GigabitEthernet0/1/0.500
Jul 20 14:27:07.294:   DHCPD: class id 6468637063642d352e352e36
Jul 20 14:27:07.294: DHCPD: Sending notification of DISCOVER:
Jul 20 14:27:07.294:   DHCPD: htype 1 chaddr 28ba.b50d.ace2
Jul 20 14:27:07.294:   DHCPD: remote id 020a000004040401080001f4
Jul 20 14:27:07.294:   DHCPD: table id 2 = vrf TMD
Jul 20 14:27:07.294:   DHCPD: giaddr = 4.4.4.5
Jul 20 14:27:07.294:   DHCPD: interface = GigabitEthernet0/1/0.500
Jul 20 14:27:07.294:   DHCPD: class id 6468637063642d352e352e36
Jul 20 14:27:07.294: DHCPD: FSM state change INVALID
Jul 20 14:27:07.294: DHCPD: Workspace state changed from INIT to INVALID
Jul 20 14:27:07.294: DHCPD: classname not set in msg
Jul 20 14:27:07.294: DHCPD: there is no address pool for 4.4.4.5.
Jul 20 14:27:07.294: DHCPD: Sending notification of ASSIGNMENT FAILURE:
Jul 20 14:27:07.294:   DHCPD: htype 1 chaddr 28ba.b50d.ace2
Jul 20 14:27:07.294:   DHCPD: remote id 020a000004040401080001f4
Jul 20 14:27:07.294:   DHCPD: table id 2 = vrf TMD
Jul 20 14:27:07.294:   DHCPD: giaddr = 4.4.4.5
Jul 20 14:27:07.294:   DHCPD: interface = GigabitEthernet0/1/0.500
Jul 20 14:27:07.294:   DHCPD: class id 6468637063642d352e352e36
Jul 20 14:27:07.294: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
Jul 20 14:27:07.294:  DHCPD: due to: NO POOL
Jul 20 14:27:07.294:   DHCPD: htype 1 chaddr 28ba.b50d.ace2
Jul 20 14:27:07.294:   DHCPD: remote id 020a000004040401080001f4
Jul 20 14:27:07.294:   DHCPD: table id 2 = vrf TMD
Jul 20 14:27:07.294:   DHCPD: giaddr = 4.4.4.5
Jul 20 14:27:07.294:   DHCPD: interface = GigabitEthernet0/1/0.500
Jul 20 14:27:07.294:   DHCPD: class id 6468637063642d352e352e36

So why is saying there is no address pool when there is?

What have I missed?

Cheer and thanks in advance

Steven

[Georg Pauwen]

Steven,

what do you have configured in the 'DHCP Option 82 Remote ID field format' on the WLC (see attached document with screenshots). AP-MAC is the default I think, try AP-MAC-SSID:

http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/113302-dhcp-option82-00.html#configs

[sjones7000]

Hi Georg,

It is indeed  set to AP-MAC right now.

Why do you think changing that to AP-MAC-SSID will help?

There is a lot of other working WLANs on this WLC so I dont want to impact anything.

Also since I started this thread I have done another test.

I moved the VLAN 500 out of the vrf and into the global routing table and both wifi and wired work. and get DHCP leases.

I move it back to the vrf and only wired works as per my original situation.

Thanks.

Steven.

[Georg Pauwen]

Hello Steven, 

I was under the assumption that none of your wireless clients were getting a DHCP address. So by all means don't change anything on the WLC.

As to your problem, do you have:

ip dhcp use vrf connected

configured on your router ?

[paul driver]

Hello

Possible due to client-id of the hosts and the pool being in VRF,  If applicable remove the vrf out of the dhcp pool

ip dhcp pool TESTING
no  vrf TMD

If this fails, keep the vrf out of the pool and statically configure host, then test once more

ip dhcp pool HOST
Host  4.4.4.100 255.255.255.0
 client-identifier 01xx.xxxx.xxxx.xx
 default-router 4.4.4.1
 dns-server 208.67.222.222 208.67.220.220

res
Paul

[GVD]

Hi Paul,

I know this topic is two years old, but I ran into the same issue, and your solution with removing the vrf from the pool did the trick. But what's the reason it doesn't work with the vrf statement in the pool?

[dontsellmydata]

Hi All,

I would also like to know why removing the vrf statement from the pool works. I just ran into this exact same problem but it still doesn't make sense to me why remove the vrf command would make this work as the SVI is in a different vrf?

I also have these two lines in my configuration:

no ip dhcp use vrf connected
ip dhcp use vrf remote