<div dir="ltr">What was the before/after change that was made?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 April 2013 22:40, Oscar Ricardo Silva <span dir="ltr"><<a href="mailto:oscars@mail.utexas.edu" target="_blank">oscars@mail.utexas.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We have two servers in a failover relationship, both running 4.1-ESV-R7. After a reload of dhcpd on the secondary, it has not come out of the recover state after almost an hour. We've had this happen with 3.1.3 and recently upgraded to this version. The only thing we've been able to do is stop both instances of dhcpd and remove "my state" and "partner state" from dhcpd.leases.<br>
<br>
<br>
Here's the timeline of what happened.<br>
<br>
1. A change was made to the configuration of the primary and dhcpd reloaded at 15:39:14.<br>
2. The primary moved back to a "normal" state at 15:43:42<br>
<br>
Apr 24 15:39:14 primary-dhcp dhcpd: failover peer dhcp: I move from normal to shutdown<br>
Apr 24 15:39:15 primary-dhcp dhcpd: failover peer dhcp: peer moves from normal to partner-down<br>
Apr 24 15:39:15 primary-dhcp dhcpd: failover peer dhcp: I move from shutdown to recover<br>
Apr 24 15:40:18 primary-dhcp dhcpd: failover peer dhcp: I move from recover to startup<br>
Apr 24 15:40:18 primary-dhcp dhcpd: failover peer dhcp: I move from startup to recover<br>
Apr 24 15:43:42 primary-dhcp dhcpd: failover peer dhcp: peer update completed.<br>
Apr 24 15:43:42 primary-dhcp dhcpd: failover peer dhcp: I move from recover to recover-done<br>
Apr 24 15:43:42 primary-dhcp dhcpd: failover peer dhcp: peer moves from partner-down to normal<br>
Apr 24 15:43:42 primary-dhcp dhcpd: failover peer dhcp: I move from recover-done to normal<br>
Apr 24 15:44:53 primary-dhcp dhcpd: failover peer dhcp: peer moves from normal to shutdown<br>
Apr 24 15:44:53 primary-dhcp dhcpd: failover peer dhcp: I move from normal to partner-down<br>
Apr 24 15:44:54 primary-dhcp dhcpd: peer dhcp: disconnected<br>
Apr 24 15:45:59 primary-dhcp dhcpd: failover peer dhcp: peer moves from shutdown to recover<br>
Apr 24 15:45:59 primary-dhcp dhcpd: failover peer dhcp: peer moves from recover to recover<br>
<br>
<br>
<br>
3. The corresponding change was made on the secondary and it was reloaded at 15:44:53<br>
<br>
4. At 15:44:54 it came back up into recover, then moved from recover to startup, then from startup to recover. That's where it's been ever since.<br>
<br>
Apr 24 15:44:53 secondary-dhcp dhcpd: failover peer dhcp: I move from normal to shutdown<br>
Apr 24 15:44:53 secondary-dhcp dhcpd: failover peer dhcp: peer moves from normal to partner-down<br>
Apr 24 15:44:54 secondary-dhcp dhcpd: failover peer dhcp: I move from shutdown to recover<br>
Apr 24 15:45:56 secondary-dhcp dhcpd: failover peer dhcp: I move from recover to startup<br>
Apr 24 15:45:59 secondary-dhcp dhcpd: failover peer dhcp: I move from startup to recover<br>
<br>
<br>
<br>
Here's dhcpd.conf for the primary:<br>
<br>
option domain-name-servers 192.168.50.41, 192.168.50.40 ;<br>
option ntp-servers 192.168.50.40, 192.168.50.41;<br>
default-lease-time 86400;<br>
max-lease-time 86400;<br>
one-lease-per-client true;<br>
ddns-update-style ad-hoc;<br>
ddns-updates off;<br>
authoritative;<br>
if substring (option dhcp-client-identifier, 0, 5) = 01:52:41:53:20 {<br>
deny booting;<br>
}<br>
option voip-tftp-server-address code 150 = array of ip-address ;<br>
set vendor-string = option vendor-class-identifier;<br>
failover peer "dhcp" {<br>
primary;<br>
address 192.168.100.2;<br>
port 520;<br>
peer address 192.168.101.2;<br>
peer port 520;<br>
max-response-delay 60;<br>
max-unacked-updates 10;<br>
mclt 120;<br>
split 255;<br>
load balance max seconds 5;<br>
}<br>
subnet 192.168.100.0 netmask 255.255.255.224 {<br>
}<br>
include "/dhcpd/dhcpd.network.conf";<br>
<br>
<br>
and the /dhcpd/dhcpd.network.conf file holds the scope definitions. Both servers sync time through ntp and have the same exact time.<br>
<br>
<br>
Any information would be appreciated.<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/<u></u>listinfo/dhcp-users</a><br>
</blockquote></div><br></div>