RE: Getting failover: link startup timeout

--===============1743482256391946692==
Content-Type: multipart/alternative; boundary="000000000000321c7705fe3e91c9"

--000000000000321c7705fe3e91c9
Content-Type: text/plain; charset="UTF-8"

The split parameter controls client distribution between failover partners.

Theoretically, you could define the failover relationship both ways but
each would require a different TCP port for communication between partners.
(E.G. server a to server b port 647 / server b to server a port 666)

Another thought is to daisy-chain more than two failover servers and then
separate subnets by failover partners.

Don't forget to have the proper DHCP helper addresses listed in the relay
agent.

Remember that as the configuration increases in complexity so does the need
for the configuration to be understood by the support team.

Bob

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

<div dir=3D"auto">The split parameter controls client distribution between =
failover partners.<div dir=3D"auto"><br></div><div dir=3D"auto">Theoretical=
ly, you could define the failover relationship both ways but each would req=
uire a different TCP port for communication between partners. (E.G. server =
a to server b port 647 / server b to server a port 666)</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Another thought is to daisy-chain more than=
 two failover servers and then separate subnets by failover partners.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Don&#39;t forget to have the =
proper DHCP helper addresses listed in the relay agent.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Remember that as the configuration increase=
s in complexity so does the need for the configuration to be understood by =
the support team.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Bob</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div></div>

--000000000000321c7705fe3e91c9--

--===============1743482256391946692==
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

--===============1743482256391946692==--