Getting failover: link startup timeout
Kraishak Mahtha <[email protected]> Thu, 15 Jun 2023 18:24:34 +0530
| Newsgroups | gmane.network.dhcp.isc.dhcp-server |
|---|---|
| Message-ID | <CADDat85B-8fLmd-1OHeHKC7gAb7kuiKHKzLpndWp7CjWJR3CSg__19173.5107380495$1686833709$gmane$org@mail.gmail.com> |
--===============8054387096810400697==
Content-Type: multipart/alternative; boundary="000000000000e0ec7105fe2a92a0"
--000000000000e0ec7105fe2a92a0
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
--000000000000e0ec7105fe2a92a0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi All,=C2=A0<div>I am using the ISC=C2=A0 dhcp failover a=
nd I am getting continuous failover: link startup timeout error on both the=
appliances, not sure what is the issue, I checked the following=C2=A0<br><=
/div><div>1)port 647(my failover) is open and I can see the tcpdump traffic=
between both servers</div><div>2)ntp is in sync=C2=A0</div><div>3)Both are=
able to ping each other=C2=A0</div><div><br></div><div>but here I have a b=
it 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 --> Failover f1</div><div=
>Server B --Server A --> Failover f2</div><div>Now let's say I have =
10 subnets, so for the first 5, I used f1 as a failover peer, and for the o=
ther 5 subnets I used=C2=A0 f2 as a failover peer. so basically=C2=A0in a s=
ingle server config, we will have two failover peers in the first section o=
f config server A will be declared as primary, and in the second section it=
will declare as failover like=C2=A0</div><div><br>failover peer "peer=
-1" {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 primary;<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-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 mc=
lt 1800;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 split 128;<br>}<br><br>failover pee=
r "peer-2" {<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 po=
rt 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-resp=
onse-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>}<br></div><div>=
Apart from this, the other config is a normal one with few subnets and basi=
c options.=C2=A0</div><div><br></div><div>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=C2=A0<br=
></div><div>for f1 --> it is showing normal-normal but for f2 --> it =
is showing=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 have a doubt=C2=A0</div><div>Can we configure the same server as the p=
rimary 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)</div><div><br></div><div>Can someone who has familiar with s=
uch setups and face similar issue can guide me=C2=A0</div><div><br></div><d=
iv>Thanks in Advance=C2=A0</div><div><br></div><div><br></div><div><br></di=
v><div><br></div><div><br></div></div>
--000000000000e0ec7105fe2a92a0--
--===============8054387096810400697==
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
--===============8054387096810400697==--