nanog mailing list archives

Re: FORT monitoring/visibility


From: Jeroen Massar via NANOG <nanog () nanog org>
Date: Wed, 27 Oct 2021 09:39:28 +0200


On 20211027, at 09:26, Lukas Tribus <lukas () ltri eu> wrote:

On Wed, 27 Oct 2021 at 08:47, Mark Tinka <mark@tinka.africa> wrote:

On 10/27/21 01:58, Randy Bush wrote:
my old DRL RP instances produce MRTG graphs etc of the CA
fetching side, though nothing on the rpki-rtr side.

Randy, I actually have an ongoing discussion with the Fort developers
about this after a BGPSec bug left me with stale VRP's for several days,
with no clear indication that Fort had "kind of" crashed and "not fully"
crashed (fair point, I need to work on better internal monitoring of
Fort, as well).

That's the reason I preached about stale RTR servers before:

https://labs.ripe.net/author/lukas_tribus/rpki-rov-about-stale-rtr-servers-and-how-to-monitor-them/
https://github.com/lukastribus/rtrcheck
https://gist.github.com/lukastribus/695c9e780d118755271519d4d3cb54f3
(the latter is a check against IOS XR devices via NETCONF which makes
some sanity checks, absolute and relative)

Lukas, thanks for these, will align my own checks with the details you check for.

Do tag your repo's with a "RPKI" tag and similar so that it is easier to find these kind of tools!


Tooling is severely lacking in the RPKI space, in numbers and quality, thus any tool like this helps.

Greets,
 Jeroen


Current thread: