Failover state changes

[Steven Carr]

Why are you putting the system into partner-down? You only need to do
this if the partner is actually down.

30 minutes recovery time (RECOVER-WAIT) is because your MCLT value is
1800. This is normal. This is how failover works when recovering from
partner-down (hence why you should avoid using partner-down unless
absolutely necessary).

If you're updating the configuration then just update the config on
both systems and restart them. If you're using canned init scripts
then make sure they aren't doing anything stupid like causing the
systems to go into partner-down.

Highly recommend getting a copy of the DHCP Handbook and reading the
section on DHCP Failover.

Steve




On Fri, 29 Nov 2019 at 07:09, Kraishak Mahtha <kraishak.edu at gmail.com> wrote:
>
>
> Hi
>  I am using the isc dhcp in standalone and it is working fine with that mode, I added the dhcp failover to my existing setup which caused the issue to my setup
>
>  The server is in partner down state for so long time which made me panic. How can I reduce this time and make them in to normal normal state
> FYI: I did some reading and found one param max-unacked-updates which was configured to 10 when i tried for the first time thought it would be the cause and I  increased its value to 5000 because my config contains nearly 800 subnets data which is large but no luck
> Does any one face same issue while adding the failover or any idea or suggestion how to decrease the time taking to recover the failover states into normal normal
>
> on Primary state changes
> cat dhcpd.leases | egrep "my state|partner state"
>   my state partner-down at 5 2019/11/29 06:23:00;
>   partner state recover-done at 5 2019/11/29 06:52:59;
>   my state normal at 5 2019/11/29 06:52:59;
>   partner state recover-done at 5 2019/11/29 06:52:59;
>   my state normal at 5 2019/11/29 06:52:59;
>   partner state normal at 5 2019/11/29 06:53:00;
> On failover state changes
>  cat dhcpd.leases | egrep "my state|partner state"
>   my state recover at 5 2019/11/29 06:22:59;
>   partner state communications-interrupted at 5 2019/11/29 06:23:00;
>   my state recover at 5 2019/11/29 06:22:59;
>   partner state communications-interrupted at 5 2019/11/29 06:23:00;
>   my state recover at 5 2019/11/29 06:22:59;
>   partner state partner-down at 5 2019/11/29 06:23:00;
>   my state recover-wait at 5 2019/11/29 06:22:59;
>   partner state partner-down at 5 2019/11/29 06:23:00;
>   my state recover-done at 5 2019/11/29 06:52:59;
>   partner state partner-down at 5 2019/11/29 06:23:00;
>   my state recover-done at 5 2019/11/29 06:52:59;
>   partner state normal at 5 2019/11/29 06:53:00;
>   my state normal at 5 2019/11/29 06:53:00;
>   partner state normal at 5 2019/11/29 06:53:00;
>
> on Primary Server
> ========================================
> failover peer "peer5" {
>         primary;
>         address YYY.YYY.YY.YYY;
>         port 647;
>         peer address YYY.YYY.YY.YYY;
>         peer port 647;
>         max-response-delay 30;
>         max-unacked-updates 5000;
>         load balance max seconds 3;
>         mclt 1800;
>         split 128;
> }
> on failover server
> ==========================================
> failover peer "peer5" {
>         secondary;
>         address YYY.YYY.YY.YYY;
>         port 647;
>         peer address YYY.YYY.YY.YYY;
>         peer port 647;
>         max-response-delay 30;
>         max-unacked-updates 5000;
>         load balance max seconds 3;
> }
>
> It took nearly 30 minutes which makes issue for my environment, Do we have any tunable parameters
>
> Thanks in Advance
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users