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. Getting failover: link startup timeout (Kraishak Mahtha)
2. Re: Getting failover: link startup timeout (Glenn Satchell)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Jun 2023 18:24:34 +0530
From: Kraishak Mahtha <kraishak....@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Getting failover: link startup timeout
Message-ID:
<caddat85b-8flmd-1ohehkc7gab7kuikhkzlpndwp7cjwjr3...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi All,
I am using the ISC dhcp failover and I am getting continuous failover:
link startup timeout error on both the appliances, not sure what is the
issue, I checked the following
1)port 647(my failover) is open and I can see the tcpdump traffic between
both servers
2)ntp is in sync
3)Both are able to ping each other
but here I have a bit of a different use case, for some of the subnets I
assigned Server A as primary, and for other subnets, I assigned Server B as
primary.
Server A-- Server B --> Failover f1
Server B --Server A --> Failover f2
Now let's say I have 10 subnets, so for the first 5, I used f1 as a
failover peer, and for the other 5 subnets I used f2 as a failover peer.
so basically in a single server config, we will have two failover peers in
the first section of config server A will be declared as primary, and in
the second section it will declare as failover like
failover peer "peer-1" {
primary;
address 10.1.10.246;
port 647;
peer address 10.1.10.247;
peer port 647;
max-response-delay 30;
max-unacked-updates 30;
load balance max seconds 3;
mclt 1800;
split 128;
}
failover peer "peer-2" {
secondary;
address 10.1.10.246;
port 647;
peer address 10.1.10.247;
peer port 647;
max-response-delay 30;
max-unacked-updates 30;
load balance max seconds 3;
}
Apart from this, the other config is a normal one with few subnets and
basic options.
I think the above config is valid only because nowhere it gave the syntax
error at compile time and also at run time and dhcpd is up and running, but
the failover peer states
for f1 --> it is showing normal-normal but for f2 --> it is showing recover
and unknown-state and sometimes it is showing partner-down and shutdown
I have a doubt
Can we configure the same server as the primary for f1 and failover for f2
for another failover peer? I hope that is a valid one because nowhere do I
see the docs saying that is valid (in my Google search)
Can someone who has familiar with such setups and face similar issue can
guide me
Thanks in Advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20230615/ac744746/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 16 Jun 2023 09:01:35 +1000
From: Glenn Satchell <glenn.satch...@uniq.com.au>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Getting failover: link startup timeout
Message-ID: <862c0bed-7024-4aa0-95f7-c877aec1f...@email.android.com>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20230616/c1f45a80/attachment-0001.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 175, Issue 1
******************************************
