[a-nsp] tracked static routes in EOS

[Drew Weaver]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/arista-nsp/attachments/20260911/493d129f/attachment.html>