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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DHCP timeouts issues 7.0.220.0

Keep getting DHCP timeouts 169.254.x.x addressing.  I think that the client laptop is not giving a response to the REQ from the DHCP server.  Am I correct in my interpretation of the debug?

00:21:d7:93:f9:40 from Disassociated to Idle

*apfReceiveTask: Jan 18 13:48:24.162: 58:94:6b:d0:41:08 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [00:21:d7:93:f9:40]

*apfReceiveTask: Jan 18 13:48:24.162: 58:94:6b:d0:41:08 Username entry deleted for mobile

*apfReceiveTask: Jan 18 13:48:24.162: 58:94:6b:d0:41:08 apfMs1xStateDec

*apfReceiveTask: Jan 18 13:48:24.162: 58:94:6b:d0:41:08 Deleting mobile on AP 00:21:d7:93:f9:40(0)

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 29, encap 0xec03)

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP processing DHCP DISCOVER (1)

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP   xid: 0x1c46c058 (474398808), secs: 3328, flags: 0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP   chaddr: 58:94:6b:d0:41:08

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.073: 58:94:6b:d0:41:08 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:37.074: 58:94:6b:d0:41:08 DHCP successfully bridged packet to DS

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.080: 58:94:6b:d0:41:08 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 29, encap 0xec03)

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.080: 58:94:6b:d0:41:08 DHCP processing DHCP DISCOVER (1)

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.080: 58:94:6b:d0:41:08 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.081: 58:94:6b:d0:41:08 DHCP   xid: 0x1c46c058 (474398808), secs: 7168, flags: 0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.081: 58:94:6b:d0:41:08 DHCP   chaddr: 58:94:6b:d0:41:08

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.081: 58:94:6b:d0:41:08 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.081: 58:94:6b:d0:41:08 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.081: 58:94:6b:d0:41:08 DHCP successfully bridged packet to DS

*DHCP Proxy DTL Recv Task: Jan 18 13:48:52.081: 58:94:6b:d0:41:08 Failed to get response for 3 dhcp attempts from client.Total DHCP failed count for the interface vlan 204 : 7

3 REPLIES

DHCP timeouts issues 7.0.220.0

Is this happening to all of your clients or just a few ? Was this always happening or just started ?

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: DHCP timeouts issues 7.0.220.0

We're migrating off of Odyssey Client to the native Windows supplicant. It seems that only a few of them are having this issue. I've updated the drivers for the WLAN card and it still happens. It isn't just on a particular wireless NIC or vendor specific. It does only seem to happen on the older 1230 and 1240 APs and not the 1140 or 3500 APs. The laptops connect via ACS 802.1x through 6 WiSM 1 WLCs and use dynamic vlan redirects in ACS. The rest of the debug shows the discover, offer, request and ACK but no response from the client.

Sent from Cisco Technical Support iPad App

Re: DHCP timeouts issues 7.0.220.0

actually the error you are seeing is the WLC not getting a response from the DHPC server. The packet was bridged three times with no response. So it could be the DHCP is too busy to reply.

you could put a sniffer on the WLC port to see the packet leave and if a response comes back or not.

Steve

Sent from Cisco Technical Support iPad App

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