With DHCP failover configured correctly should both servers be responding to the same dhcp request? <br><br>I know that the leases db is staying synced as they will both ACK with the same IP. I'm running into the issue with both
3.0.5 and 3.0.6 on Debian 3.1. Just to be sure that it wasn't issues with my dhcpd.leases file dhcpd was stopped on both servers, emptied and started again with the same issue. Running omshell to get the failover state is showing both servers in normal mode once the recovery + MCLT has passed.
<br><br>The reason as to why this might be an issue is that in our production enviroment our routers are setup with 2 ip helper-address statements. One to the primary and one to the secondary server. Option dhcp-server-identifier is set to the local GW for that network. This means that DHCREQUEST packets will be sent to both servers. Normally with both servers sending an identical ACK it should be an issue though I seem to remember Windows Me and 98 clients that would fail an IP renewal due to the almost identical ACK.
<br><br><br>Any ideas or suggestions? So far the DHCP Handbook has been a great help though I think I might have missed something.<br><br><br><br>dhcp-01 is the primary. dhcp-02 is the secondary.<br><br>Here is what I'm seeing in the logs with a Windows XP SP2 client:
<br><br>Sep 5 11:13:20 dhcp-01 dhcpd: DHCPDISCOVER from 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0: load balance to peer dhcp<br>Sep 5 11:13:20 dhcp-01 dhcpd: DHCPREQUEST for <a href="http://10.2.1.128" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.128</a> (<a href="http://10.2.1.203" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.203</a>) from 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0<br>Sep 5 11:13:20 dhcp-02 dhcpd: DHCPDISCOVER from 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0 <br>Sep 5 11:13:20 dhcp-01 dhcpd: DHCPACK on <a href="http://10.2.1.128" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.128</a> to 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0<br>Sep 5 11:13:20 dhcp-02 dhcpd: DHCPOFFER on <a href="http://10.2.1.128" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.128</a>
to 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0 <br>Sep 5 11:13:20 dhcp-02 dhcpd: DHCPREQUEST for
<a href="http://10.2.1.128" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.128</a> (<a href="http://10.2.1.203" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.203
</a>) from 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0 <br>Sep 5 11:13:20 dhcp-02 dhcpd: DHCPACK on <a href="http://10.2.1.128" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.128
</a> to 52:54:00:12:34:56 (noctest-jjmiw1z) via eth0 <br><br><br>Here is my configuration:<br>### dhcpd.conf #This is mirrored on both servers.<br>ddns-update-style none;<br>one-lease-per-client true;<br>authoritative;
<br>
ping-check true;<br>#use-host-decl-names on;<br>omapi-port 7911;<br>key "omapi_key" {<br> algorithm hmac-md5;<br> secret "******";<br>};<br>omapi-key omapi_key;<br><br>log-facility local7;
<br><br>stash-agent-options on;<br>include "/etc/dhcpd.failover.conf";<br>include "/etc/dhcpd.pools.conf";<br>## End dhcpd.conf<br><br>## PRIMARY dhcpd.failover.conf ##<br>failover peer "dhcp" {
<br> primary;<br> address <a href="http://10.2.1.202" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.202</a>;<br> port 847;<br> peer address <a href="http://10.2.1.203" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.203</a>;<br> peer port 647;<br> max-response-delay 60;<br> max-unacked-updates 10;
<br> load balance max seconds 3;<br> mclt 180;<br> split 128;<br>}<br>## End PRIMARY dhcpd.failover.conf ##<br><br>## Secondary dhcpd.failover.conf ##<br>failover peer "dhcp" {<br> secondary;<br> address <a href="http://10.2.1.203" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.203</a>;<br> port 647;<br> peer address <a href="http://10.2.1.202" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.202</a>;<br> peer port 847;<br> max-response-delay 180;<br> load balance max seconds 3;
<br> max-unacked-updates 10;<br>}<br>## End Secondary
dhcpd.failover.conf<br><br>## dhcpd.pools.conf ## Mirrored on both servers.<br>shared-network testing1 {<br> subnet <a href="http://10.2.1.0" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.0
</a> netmask <a href="http://255.255.255.0" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.0</a> {<br> pool {
<br> failover peer "dhcp";<br> option routers <a href="http://10.2.1.254" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.254</a>;<br> option broadcast-address <a href="http://10.2.1.255" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.255</a>;<br> option subnet-mask <a href="http://255.255.255.0" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
255.255.255.0</a>;<br> deny dynamic bootp clients;<br> range <a href="http://10.2.1.0" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.0</a> <a href="http://10.2.1.253" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
10.2.1.253</a>;<br> option domain-name-servers <a href="http://10.2.1.254" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">10.2.1.254
</a>;<br> default-lease-time 7200;<br> max-lease-time 14400;<br> }<br> }<br>} ## End Shared-Network testing1<br>## End dhcpd.pools.conf<br><br><br><br>