nanog mailing list archives
Re: validating reachability via an ISP
From: Ben Bartsch <uwcableguy () gmail com>
Date: Thu, 5 Apr 2018 06:16:47 -0500
+1 for Route Explorer On Thu, Apr 5, 2018 at 2:49 AM, Andy Davidson <andy () nosignal org> wrote:
On 29/03/2018, 00:22, Andy Litzinger <andy.litzinger.lists () gmail com> wrote:The root cause is that the our prefix is not being adequately re-distributed globally by the regional ISP. This is unexpected and weareworking through this with them now.Hi, Andy — Are you failing to advertise it, or are they filtering it on ingress, or are they failing to send it to their other peers? One configuration mishap which is starting to come along more and more partial or poor reachability caused by route objects which are not correctly published in the IRRDB. It is going to be essential to make sure that you have properly recorded IRR route objects in, for instance, RADB. More BGP speakers properly filter their peers using information that is published there. Avoid future reachability problems by checking this today! Yours, A friendly route-server operator with strict filtering -a -- Andy Davidson Asteroid International BV https://www.asteroidhq.com @asteroidhq @andyd -------------------------------------------------- Local interconnection. Where you need it.
Current thread:
- Re: validating reachability via an ISP Don Thomas Jacob (Apr 04)
- <Possible follow-ups>
- Re: validating reachability via an ISP Andy Litzinger (Apr 04)
- Re: validating reachability via an ISP Andy Litzinger (Apr 04)
- Re: validating reachability via an ISP Andy Davidson (Apr 05)
- Re: validating reachability via an ISP Ben Bartsch (Apr 05)
- Re: validating reachability via an ISP Andy Litzinger (Apr 05)