eth0: not responding (recovering)

[Bill Shirley]

I non-failover DHCP server doesn't have any "failover peer" stanza in the /var/log/dhcpd/dhcpd.leases
file.  A working failover lease file has at the top:
failover peer "dhcp-failover" state {
   my state normal at 4 2019/10/10 05:05:04;
   partner state normal at 5 2011/09/02 23:51:25;
}

Try shutting down both the primary and secondary servers, remove the "failover peer" stanza from
both of their lease files, and then bring up the primary *with the failover configuration*.  Ensure it is
handing out leases, then bring up the secondary *with the failover configuration*.  Then check that
all is working correctly.

Bill

On 10/9/2019 1:32 PM, Surya Teja wrote:
> I am facing weird situation with fail over setup on my lab environment. I am facing issue when the failover dhcp appliance is 
> added to my existing server.
> For the first time when i add failover to primary appliance,  On primary appliance lease file i see the partner state as 
> unknown and in the failover the messages are printing not responding recovery, so i shutdown the failover appliance and 
> removed the failover config section from primary and restarted primary then it was working fine.
> As a trial of second attempt i increased mclt value to 3600 and added the failover section back to primary config and bring up 
> the failover server now.
> The environment became most problematic none of the servers are granting leases to devices On the primary lease file it says
> my state partner-down
> peer state recovery
>
> Why do we get these recovery,partner down, unknown status when i add the failover to my environment?
> Or do we have any best practice steps how to add failover to existing server without causing any outages?
>
> Any help would be appreciated
> Thanks
>
>
>
> On Sun, 6 Oct 2019, 21:04 Surya Teja, <suryateja042 at gmail.com <mailto:suryateja042 at gmail.com>> wrote:
>
>     Hi Bill Thanks for your reply,
>     Yes I see traffic on the peer ports which i mentioned in the fail over section of my configuration file.
>     My mclt value is 1800(30 min).
>     I am seeing these issues on the failover server and some times I see the logs saying peer hold all free leases, but that
>     scope is not completely full with active entries in the dhcpd.lease file of that specified server
>
>     And one more strange thing I observerd in the lease file. In the file I have statements like my status and peer status. In
>     that peer status is saying *unknown*
>     When will this happen? In general scenario it should be normal that is what i got from internet, but the state is not
>     getting updated in the lease file.
>
>     On Sat, 5 Oct 2019, 21:16 Bill Shirley, <bill at c3po.polymerindustries.biz <mailto:bill at c3po.polymerindustries.biz>> wrote:
>
>         Assuming you're referring to DHCP failover, is there any traffic flow on the
>         port and peer port in the failover stanza?
>
>         What is your value for mclt?
>
>         Which server, primary or secondary, is giving the recovering message?
>
>         Bill
>
>         On 10/5/2019 9:33 AM, Surya Teja wrote:
>>         Hi I have an issue in the lease flow with isc dhcp service. In the logs it is printing *eth0: not responding
>>         (recovering) *
>>         My local is set up with active-active mode(splt value as 50-50%) and because of some reason one of the appliance went
>>         down for some duration. I observed this and i bring it up, and duration of down is nearly 15hr.
>>         After i bring it up. I am seeing the logs saying not responding (recovering). Its been more than two hours still I am
>>         getting the same logs
>>         Does any one have any idea about this scenario and how to get the environment stable
>>
>>         _______________________________________________
>>         dhcp-users mailing list
>>         dhcp-users at lists.isc.org  <mailto:dhcp-users at lists.isc.org>
>>         https://lists.isc.org/mailman/listinfo/dhcp-users
>         _______________________________________________
>         dhcp-users mailing list
>         dhcp-users at lists.isc.org <mailto:dhcp-users at lists.isc.org>
>         https://lists.isc.org/mailman/listinfo/dhcp-users
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20191010/1caa4f03/attachment.htm>