Re: Getting failover: link startup timeout

--===============2251812882159927402==
Content-Type: multipart/alternative; boundary="00000000000091cb3a05fe60d5c6"

--00000000000091cb3a05fe60d5c6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you  *Glenn Satchell and * *Bob McDonald *for suggestion, will try
that way

On Thu, Jun 15, 2023 at 6:24=E2=80=AFPM Kraishak Mahtha <kraishak.edu@gmail=
.com>
wrote:

> 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 i=
n
> 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, b=
ut
> 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-dow=
n
> and shutdown
>
>
>  I have a doubt
> Can we configure the same server as the primary for f1 and failover for f=
2
> 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
>
>
>
>
>
>

--00000000000091cb3a05fe60d5c6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you=C2=A0

<i style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;;font-s=
ize:medium">Glenn Satchell and=C2=A0</i>

<i style=3D"color:rgb(0,0,0);font-family:&quot;Times New Roman&quot;;font-s=
ize:medium">Bob McDonald </i><span style=3D"color:rgb(0,0,0);font-family:&q=
uot;Times New Roman&quot;;font-size:medium">for suggestion, will try that w=
ay=C2=A0</span><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Thu, Jun 15, 2023 at 6:24=E2=80=AFPM Kraishak Mahtha =
&lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr">Hi All,=C2=A0<div>I am using the ISC=C2=A0 dhcp failover and I am=
 getting continuous failover: link startup timeout error on both the applia=
nces, not sure what is the issue, I checked the following=C2=A0<br></div><d=
iv>1)port 647(my failover) is open and I can see the tcpdump traffic betwee=
n both servers</div><div>2)ntp is in sync=C2=A0</div><div>3)Both are able t=
o ping each other=C2=A0</div><div><br></div><div>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.</div><div>=C2=A0</=
div><div>Server=C2=A0A-- Server=C2=A0B --&gt; Failover f1</div><div>Server =
B --Server A --&gt; Failover f2</div><div>Now let&#39;s say I have 10 subne=
ts, so for the first 5, I used f1 as a failover peer, and for the other 5 s=
ubnets I used=C2=A0 f2 as a failover peer. so basically=C2=A0in a single se=
rver 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 de=
clare as failover like=C2=A0</div><div><br>failover peer &quot;peer-1&quot;=
 {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 primary;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 a=
ddress 10.1.10.246;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 port 647;<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 peer address 10.1.10.247;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
peer port 647;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 max-response-delay 30;<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 max-unacked-updates 30;<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 load balance max seconds 3;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 mclt 1800=
;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 split 128;<br>}<br><br>failover peer &quot=
;peer-2&quot; {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 secondary;<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 address 10.1.10.246;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 port 647;=
<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 peer address 10.1.10.247;<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 peer port 647;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 max-response-de=
lay 30;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 max-unacked-updates 30;<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 load balance max seconds 3;<br>}<br></div><div>Apart f=
rom this, the other config is a normal one with few subnets and basic optio=
ns.=C2=A0</div><div><br></div><div>I think the above config is valid only b=
ecause nowhere it gave the syntax error at compile time and also at run tim=
e and dhcpd is up and running, but the failover peer states=C2=A0<br></div>=
<div>for f1 --&gt; it is showing normal-normal but for f2 --&gt; it is show=
ing=C2=A0recover and=C2=A0unknown-state and sometimes it is showing partner=
-down and shutdown=C2=A0</div><div><br></div><div><br></div><div>=C2=A0I ha=
ve a doubt=C2=A0</div><div>Can we configure the same server as the primary =
for f1 and failover for f2 for another failover peer? I hope that is a vali=
d one because nowhere do I see the docs saying that is valid (in my Google =
search)</div><div><br></div><div>Can someone who has familiar with such set=
ups and face similar issue can guide me=C2=A0</div><div><br></div><div>Than=
ks in Advance=C2=A0</div><div><br></div><div><br></div><div><br></div><div>=
<br></div><div><br></div></div>
</blockquote></div>

--00000000000091cb3a05fe60d5c6--

--===============2251812882159927402==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
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
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users

--===============2251812882159927402==--