[a-nsp] tracked static routes in EOS

[Tyler Conrad]

Hi Drew,

I've worked on a couple extensions to do this over the years, and there's
also a built-in way.

Built-in: Connectivity-monitor with an on-logging event-handler can work
for script-less behavior.
PingCheck Extension: https://github.com/arista-eosext/PingCheck - this one
uses a simple ping check.
SynAcktor Extension: https://github.com/etedor/synacktor - adds flexibility
to be able to monitor a tcp service and set an arbitrary next-hop. Useful
for monitoring a path without changing the routing table.

Hope this helps,
-T

On Fri, Sep 11, 2026 at 9:03 AM Drew Weaver via arista-nsp <
arista-nsp at puck.nether.net> wrote:

> Howdy
>
>
>
> Is it true that there really is no way to do tracked static routes in EOS
> without installing a python script that you have to reinstall every time
> the switch reboots?
>
>
>
> By tracked static routes I just mean a route that withdrawals when
> something stops pinging (or another tracking mechanism) would just use BFD
> but the device on the far end of the L2 network doesn’t support it.
>
>
>
> Use case is basically just a L2 network in between the route origin and
> the destination. if the entire network goes down and the physical link
> facing the route originating device disappears then the route is withdrawn
> anyway but if only the portion on the other side of the L2 network goes
> down then you’re null routing traffic unintentionally.
>
>
>
> I’m just wondering.
>
>
>
> Thanks,
>
> -Drew
>
>
> --
> arista-nsp mailing list
> arista-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/arista-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/arista-nsp/attachments/20260911/0df70b88/attachment.html>