Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: Failover state changes (kraishak)


----------------------------------------------------------------------

Message: 1
Date: Thu, 19 Dec 2019 11:05:22 -0600 (CST)
From: kraishak <kraishak....@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: Failover state changes
Message-ID: <1576775122031-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii

Hi Chris,

Thanks for your valuable reply and suggestion, I just tried with
max-unacked-updates as 1000 but still it is taking more time will it be any
impact if it be more like 10000 just want to cross check,
And some times my failover peer servers both are getting stuck in the
recovery states Ex: primary in recovery and failover in recover-wait state
for so long time more than 3.5 hours. So i just stopped the dhcpd service on
the failover server and deleted the lease file and restarted it. This time
it took mclt time duration but not sure whether it is a correct way to
approach? Does any of the users face same situation of failover peer getting
stuck in the recover, recover-wait state for so long time?  
If so what would be the best way of fixing them without impacting the
environment for so long time?  



--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/


------------------------------

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 134, Issue 8
******************************************

Reply via email to