Re: validating reachability via an ISP

Hi Andy, The root cause was they regional ISP was failing to advertise my prefix due to a mistake in their export policy. While I'm glad we were able to figure out the issue I'm generally more interested in figuring out a way that I can programmatically monitor that my ISPs are providing me with

Re: validating reachability via an ISP

+1 for Route Explorer On Thu, Apr 5, 2018 at 2:49 AM, Andy Davidson wrote: > > > > > > On 29/03/2018, 00:22, Andy Litzinger > wrote: > > > >> 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 > >> wor

Re: validating reachability via an ISP

On 29/03/2018, 00:22, Andy Litzinger wrote: > >> 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. Hi, Andy — Are you failing to advertise it, or are they filter

Re: validating reachability via an ISP

Hi Andrew, thanks for sharing your repo, it looks very relevant and I should be able to get it to do what I want with a slight tweak to the regex's. Hopefully the route-views collectors or some other ones I dig up will be able to adequately show at least 3 AS path hops through my regional provid

Re: validating reachability via an ISP

Hi Alex, Thanks for the link to the qrator API. The get-all-paths is interesting and the output does seem to show exactly the type of data I'm looking for. Is there some place on the site that lists who Qrator peers with to get your data? I searched through the site and couldn't find it. I'm t

Re: validating reachability via an ISP

Hi, If you are fine with a commercial tool, Packet Design Route Explorer product supports peering analysis: BGP-RIB-Visualization-1.png is one among its features. https://www.packetdesign.com/solutions/peering-a

Re: validating reachability via an ISP

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 : > Hi all, > I have an enterprise network and do not provide transit. In one of our > datacenters w

Re: validating reachability via an ISP

On Wed, Mar 28, 2018 at 7:22 PM, Andy Litzinger wrote: > 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 > pro

Re: validating reachability via an ISP

Also the only traffic you will be receiving on the other provider will be from parties that did not pick up the more specific prefix. It should therefore be really obvious. You should not receive any traffic at all, not even from the transit provider. Regards, Baldur Den tor. 29. mar. 2018 10.4

Re: validating reachability via an ISP

If your prefix is larger than /24 you can test with a more specific prefix such as a /24. Announce the test prefix on just one transit provider. Then check with BGP services such as the looking glass service provided by the NLNOG RING network. There will be no interruption in the traffic as it wil

Re: validating reachability via an ISP

On 3/29/2018 2:22 AM, Andy Litzinger wrote: > 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 th