nanog mailing list archives

Re: validating reachability via an ISP


From: Alexander Azimov <aa () qrator net>
Date: Thu, 29 Mar 2018 18:09:02 +0300

Hi Andy,

You can use Qrator.Radar API: https://api.radar.qrator.net/.
The get-all-paths method will return the set of active paths for selected
prefix.


2018-03-29 2:22 GMT+03:00 Andy Litzinger <andy.litzinger.lists () gmail com>:

Hi all,
  I have an enterprise network and do not provide transit. In one of our
datacenters we have our own prefixes and rely on two ISPs as BGP neighbors
to provide global reachability for our prefixes.  One is a large regional
provider and the other is a large global provider.

Recently we took our link to the global provider offline to perform
maintenance on our router.  Nearly immediately we were hit with alerts that
our prefix was unreachable and BGPMon alerted that nearly 80 AS's noted our
route had been withdrawn.  We were not unreachable from every AS, but we
certainly were from some of the largest.

The root cause is that the our prefix is not being adequately
re-distributed globally by the regional ISP.  This is unexpected and we are
working through this with them now.

My question is, how can I monitor global reachability for a prefix via this
or any specific provider I use over time?  Are there various route-servers
I can programmatically query for my prefix and get results that include AS
paths? Then I could verify that an "acceptable" number of paths exist that
include the AS of the all the ISPs I rely upon.  And what would an
"acceptable" number of alternate paths be?


thanks in advance,
  -andy




-- 
| Alexander Azimov  | HLL l QRATOR
| tel.: +7 499 241 81 92
| mob.: +7 915 360 08 86
| skype: mitradir
| mailto: aa () qrator net
| visit: www.qrator.net


Current thread: