Others have addressed some of the issues, but one easy win for DHCP (which is otherwise a PITA to make redundany in *any* way) is to (a) not
block ICMP anywhere, including on the client devices, and (b) have the DHCP ping before assignment. That’s not always on by default, and it’ll eliminate ~90% of the conflicts you would otherwise encounter if the anycast node isn’t extremely stable. If you
become aware of a distributed DHCP server that actually works well in this environment, that’s worth a post to the list all by itself.
-Adam
Adam Thompson
Consultant, Infrastructure Services
100 - 135 Innovation Drive
Winnipeg, MB R3T 6A8
(204) 977-6824 or 1-800-430-6404 (MB only)
|
|
|
From: NANOG <nanog-bounces+athompson=merlin.mb.ca@nanog.org>
On Behalf Of Javier Gutierrez
Sent: Thursday, February 22, 2024 12:47 PM
To: nanog@nanog.org
Subject: TFTP over anycast
Hi,
I'm working on some DR design and we want to not only have this site as a DR but also performing some active/active for some of the services we hosts and I was wondering if someone had some experience with
using anycast for TFTP or DHCP services?
What are some of the pains/challenges you experienced and things we should lookout for?
Any input is greatly appreciated.
Kind regards,
Javier Gutierrez