Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

client not getting ip add via ext. DHCP svr through WLC

Hi,

i am having problem on this set-up. i have made it work on other installation but i am having problem with last night's installation. clients are not getting ip address via external dhcp server. i have pointed the particular interface to the dhcp server (in the same subnet block), checked that dhcp proxy is enabled and it's not working. debug is posted and as i have seen it, dhcp server has replied to the dhcp discovery,

*DHCP Socket Task: Mar 22 20:31:11.719: 34:15:9e:84:76:dd DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:11.719: 34:15:9e:84:76:dd DHCP option: message type = DHCP REQUEST

*DHCP Socket Task: Mar 22 20:31:11.719: 34:15:9e:84:76:dd DHCP option: 55 (len 6) - skipping

*DHCP Socket Task: Mar 22 20:31:11.719: 34:15:9e:84:76:dd DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP option: requested ip = 192.168.0.158

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP option: lease time = 7776000 seconds

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP option: message type = DHCP NAK

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP option: server id = 192.168.249.1

*DHCP Socket Task: Mar 22 20:31:11.720: 34:15:9e:84:76:dd DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:12.848: 34:15:9e:84:76:dd DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:12.848: 34:15:9e:84:76:dd DHCP option: message type = DHCP REQUEST

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: 55 (len 6) - skipping

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: requested ip = 192.168.249.98

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: lease time = 7776000 seconds

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: message type = DHCP ACK

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: 58 (len 4) - skipping

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: 59 (len 4) - skipping

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: lease time = 86400 seconds

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: server id = 192.168.249.1

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: netmask = 255.255.255.0

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: gateway = 192.168.249.40

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: DNS server, cnt = 2, first = 208.67.220.220

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP option: 43 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:31:12.849: 34:15:9e:84:76:dd DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: 116 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: 12 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: vendor class id = MSFT 5.0 (len 8)

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: 55 (len 11) - skipping

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP option: 43 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:21.437: 00:21:5d:cc:98:04 DHCP Forwarding DHCP packet (332 octets)                               -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.249.40

*DHCP Socket Task: Mar 22 20:31:25.436: 00:21:5d:cc:98:04 DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:25.436: 00:21:5d:cc:98:04 DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP option: 116 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP option: 12 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP option: vendor class id = MSFT 5.0 (len 8)

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP option: 55 (len 11) - skipping

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP option: 43 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:25.437: 00:21:5d:cc:98:04 DHCP Forwarding DHCP packet (332 octets)                               -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.249.40

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: 116 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: 12 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: vendor class id = MSFT 5.0 (len 8)

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: 55 (len 11) - skipping

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP option: 43 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:34.436: 00:21:5d:cc:98:04 DHCP Forwarding DHCP packet (332 octets)                               -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.249.40

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: 116 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: 12 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: vendor class id = MSFT 5.0 (len 8)

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: 55 (len 11) - skipping

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP option: 43 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:31:51.434: 00:21:5d:cc:98:04 DHCP Forwarding DHCP packet (332 octets)                               -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.249.40

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP REQUEST

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: requested ip = 192.168.249.150

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: server id = 192.168.249.1

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: vendor class id = dhcpcd 4.0.15 (len 13)

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: 55 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP NAK

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP option: server id = 192.168.249.1

*DHCP Socket Task: Mar 22 20:32:04.172: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP REQUEST

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: requested ip = 192.168.249.150

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: server id = 192.168.249.1

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: vendor class id = dhcpcd 4.0.15 (len 13)

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: 55 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP NAK

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP option: server id = 192.168.249.1

*DHCP Socket Task: Mar 22 20:32:04.281: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:05.733: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:05.733: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:32:05.733: cc:f9:e8:8e:5a:ba DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:05.733: cc:f9:e8:8e:5a:ba DHCP option: vendor class id = dhcpcd 4.0.15 (len 13)

*DHCP Socket Task: Mar 22 20:32:05.733: cc:f9:e8:8e:5a:ba DHCP option: 55 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:05.733: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:08.765: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:08.765: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:32:08.765: cc:f9:e8:8e:5a:ba DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:08.765: cc:f9:e8:8e:5a:ba DHCP option: vendor class id = dhcpcd 4.0.15 (len 13)

*DHCP Socket Task: Mar 22 20:32:08.765: cc:f9:e8:8e:5a:ba DHCP option: 55 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:08.765: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:15.855: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:15.855: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:32:15.855: cc:f9:e8:8e:5a:ba DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:15.855: cc:f9:e8:8e:5a:ba DHCP option: vendor class id = dhcpcd 4.0.15 (len 13)

*DHCP Socket Task: Mar 22 20:32:15.855: cc:f9:e8:8e:5a:ba DHCP option: 55 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:15.855: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*dtlArpTask: Mar 22 20:32:23.473: 00:21:5d:cc:98:04 In apfMsDhcpStateClear for station  ---

*dtlArpTask: Mar 22 20:32:23.837: 00:21:5d:cc:98:04 In apfMsDhcpStateClear for station  ---

*dtlArpTask: Mar 22 20:32:24.837: 00:21:5d:cc:98:04 In apfMsDhcpStateClear for station  ---

*DHCP Socket Task: Mar 22 20:32:27.905: 00:21:5d:cc:98:04 DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: 116 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: 12 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: vendor class id = MSFT 5.0 (len 8)

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: 55 (len 11) - skipping

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP option: 43 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:27.906: 00:21:5d:cc:98:04 DHCP Forwarding DHCP packet (332 octets)                               -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.249.40

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: 116 (len 1) - skipping

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: 61 (len 7) - skipping

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: 12 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: vendor class id = MSFT 5.0 (len 8)

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: 55 (len 11) - skipping

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP option: 43 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:30.907: 00:21:5d:cc:98:04 DHCP options end, len 72, actual 64

*DHCP Socket Task: Mar 22 20:32:30.908: 00:21:5d:cc:98:04 DHCP Forwarding DHCP packet (332 octets)                               -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.249.40

*DHCP Socket Task: Mar 22 20:32:31.383: cc:f9:e8:8e:5a:ba DHCP option len (including the magic cookie) 72

*DHCP Socket Task: Mar 22 20:32:31.383: cc:f9:e8:8e:5a:ba DHCP option: message type = DHCP DISCOVER

*DHCP Socket Task: Mar 22 20:32:31.383: cc:f9:e8:8e:5a:ba DHCP option: 57 (len 2) - skipping

*DHCP Socket Task: Mar 22 20:32:31.383: cc:f9:e8:8e:5a:ba DHCP option: vendor class id = dhcpcd 4.0.15 (len 13)

*DHCP Socket Task: Mar 22 20:32:31.383: cc:f9:e8:8e:5a:ba DHCP option: 55 (len 9) - skipping

*DHCP Socket Task: Mar 22 20:32:31.383: cc:f9:e8:8e:5a:ba DHCP options end, len 72, actual 64

*** IDLE TIMEOUT ***

(Cisco Controller)

User:

4 REPLIES

client not getting ip add via ext. DHCP svr through WLC

Is this DHCP scope working? Can you jump onto the lan and see if you can get a DHCP from the server?

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________
Hall of Fame Super Silver

Re: client not getting ip add via ext. DHCP svr through WLC

Just to add, make sure dhcp proxy is enabled on the wlc and the interface the users are placed on has the wlc management interface. These are required when using the wlc as a dhcp server for wireless clients.

Thanks,

Scott Fella

Sent from my iPhone

-Scott
*** Please rate helpful posts ***
Community Member

Re: client not getting ip add via ext. DHCP svr through WLC

yes, its working for the LAN users

Re: client not getting ip add via ext. DHCP svr through WLC

Hi, I assume that the client is not in the same subnet as the management interface.

Per the best practices guide your DHCP server should not be in the same subnet as any dynamic interface. The WLC does not like ti see responses in the wire for a subnet it is configured for.

To get around this:

Config network mgmt-via-dynamic-interface enable.

You may also need ti issue:

Config network mgmt-via-wireless enable

Steve

Sent from Cisco Technical Support iPhone App

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
1604
Views
0
Helpful
4
Replies
CreatePlease to create content