Hello all first I'd like to admit I'm not a Cisco guru at all I have limited knowledge of Cisco devices but a customer of ours has a Model 5508 Wireless Controller and he's having an issue with it receiving requests from there DHCP server. Also if this is in the wrong forum I apologize it could go in either wireless or network infrastructure
DHCP is working for everything else across the network including the vMware view environment when new virtual desktops spool up, and there is a location where there is a different wireless controller in place that is not having any issues with handing out DHCP. I can ping the DHCP server from the unit and it responds with 1-2ms ping times with no problem. And if I configure a device to have a static IP address on the vlan it has connectivity and can pass traffic just fine.
The software version on the unit it is 7.2.110.0
As a work around for now I have the unit using it's internal DHCP Scope to hand out ip addresses and everything seems to be working fine for now. But I'd like to get a real solution for this if possible.
I included some logs that I got back when I ran some tests on the DHCP server testing to see what was happening.
*DHCP Socket Task: Oct 27 09:37:00.794: 04:15:52:94:6d:02 DHCP Forwarding DHCP packet (332 octets) -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.150.1
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option: 55 (len 6) - skipping
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option: 57 (len 2) - skipping
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option: lease time = 7776000 seconds
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP option: hostname = hyde13-ipad-180-4 (len 17)
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP options end, len 72, actual 64
*DHCP Socket Task: Oct 27 09:37:00.895: 04:e5:36:c1:2f:88 DHCP Forwarding DHCP packet (332 octets) -- packet received on direct-connect port requires forwarding to external DHCP server. Next-hop is 192.168.43.1
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option: 55 (len 6) - skipping
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option: 57 (len 2) - skipping
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option: lease time = 7776000 seconds
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP option: hostname = Staff13-iPad-dfrantz (len 20)
*DHCP Socket Task: Oct 27 09:37:00.911: 60:fe:c5:67:62:f5 DHCP options end, len 72, actual 64
Any help would be greatly appreciated.
