HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Not geeting DHCPREQUEST and DHCPACK

 
monu_1
Regular Advisor

Not geeting DHCPREQUEST and DHCPACK

Hi All,

DHCP Server is able DHCPOFFER/DHCPDISCOVER but not DHCPREQUEST/DHCPACK.

what could be cause? it could be a client BIOS/bootorder or arp resolution issue?

an 5 23:31:44 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:44 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:45 SERVER1 dhcpd: DHCPOFFER on 192.168.64.117 to 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:45 SERVER1 dhcpd: DHCPOFFER on 192.168.64.123 to 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:46 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:46 SERVER1 dhcpd: DHCPOFFER on 192.168.64.117 to 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:46 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:46 SERVER1 dhcpd: DHCPOFFER on 192.168.64.123 to 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:48 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:48 SERVER1 dhcpd: DHCPOFFER on 192.168.64.117 to 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:48 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:48 SERVER1 dhcpd: DHCPOFFER on 192.168.64.123 to 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:48 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:16 via bond0
Jan 5 23:31:49 SERVER1 dhcpd: DHCPOFFER on 192.168.64.118 to 00:80:42:1f:6a:16 via bond0
Jan 5 23:31:50 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:16 via bond0
Jan 5 23:31:50 SERVER1 dhcpd: DHCPOFFER on 192.168.64.118 to 00:80:42:1f:6a:16 via bond0
Jan 5 23:31:51 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:88 via bond0
Jan 5 23:31:52 SERVER1 dhcpd: DHCPOFFER on 192.168.64.124 to 00:80:42:1f:6a:88 via bond0
Jan 5 23:31:52 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:52 SERVER1 dhcpd: DHCPOFFER on 192.168.64.117 to 00:80:42:1f:6d:c0 via bond0
Jan 5 23:31:52 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:52 SERVER1 dhcpd: DHCPOFFER on 192.168.64.123 to 00:80:42:1f:6a:70 via bond0
Jan 5 23:31:53 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:88 via bond0
Jan 5 23:31:53 SERVER1 dhcpd: DHCPOFFER on 192.168.64.124 to 00:80:42:1f:6a:88 via bond0
Jan 5 23:31:53 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:2b:16:23 via bond0
Jan 5 23:31:54 SERVER1 dhcpd: DHCPOFFER on 192.168.64.105 to 00:80:42:2b:16:23 via bond0
Jan 5 23:31:54 SERVER1 dhcpd: DHCPDISCOVER from 00:80:42:1f:6a:16 via bond0
Jan 5 23:31:54 SERVER1 dhcpd: DHCPOFFER on 192.168.64.118 to 00:80:42:1f:6a:16 via bond0
1 REPLY
Matti_Kurkela
Honored Contributor

Re: Not geeting DHCPREQUEST and DHCPACK

First a client locates the DHCP server using DHCPDISCOVER. You can see it in your log messages: they say "DHCPDISCOVER _from_ ..."
Then the DHCP server responds with DHCPOFFER.

After that, the client analyzes the DHCPOFFER(s) it has received, and then makes a DHCPREQUEST to the server it ranks "the best". If these clients are trying to renew their old leases, they are likely to prefer the server they originally got their address from.

Maybe there is another DHCP server in your network?

Another possibility: DHCPDISCOVER is always a broadcast, but DHCPREQUEST may be unicast at the Ethernet level. If you have a firewall, be sure it is configured to pass through all the traffic modes required by DHCP.

MK
MK