Have an AAISP looking glass, so that I can see the state of the BGP world from AAISP's perspective

There are occasions when routing to a site appears to be completely and utterly insane, and it's not always obvious which ISP is responsible.

A BGP looking glass giving skilled users the chance to interrogate the BGP tables at interesting routers in AAISP's network (the LNS, the Ethernet termination point, any other routers where customer services terminate) would enable users to check whether apparently insane routing is AAISP's fault (in which case we chase support), or another ISP's fault (in which case we chase them).

As an example; at one point, packets from you to Goscomb's UK infrastructure were routed via Amsterdam. It took quite a bit of prodding people to determine that this was because Goscomb weren't peering with you in the UK, were connected via Level 3 in Amsterdam, and were using AS prepending to ensure that Level 3 was the preferred BGP route. A looking glass like http://lg.level3.net/ would let us see that AAISP weren't the ISP preferring passage via Amsterdam, and would let us put pressure on the right ISP to fix it.

Author: Simon Farnsworth, 07.03.2011, 11:56
Idea status: in process

Response from the site administrator

aaisp, 21.04.2015
This is in our engineering team's queue.


Arne, 28.10.2012, 17:34
There is a Open Source looking glass available within rancid http://www.shrubbery.net/rancid/ and the one here ftp://ftp.nordu.net/nordunet/lg.tar.gz
Eugene, 24.12.2012, 16:15
The comment was deleted by the administrator
jrekgvnh, 25.12.2012, 05:21
The comment was deleted by the administrator
fbnwai, 26.12.2012, 11:00
The comment was deleted by the administrator
aoktwp, 28.12.2012, 00:31
The comment was deleted by the administrator
Simon Farnsworth, 08.06.2015, 12:25
Note that this also helps when there are routing issues - if the looking glass lets me ping and traceroute from AAISP's point of view, I can tell quite quickly that (a) BGP tells me the nexthop for an interesting network is 2001:db8:105:106::4 and (b) a traceroute to that nexthop does not get beyond LINX, suggesting LINX issues.
We all love apple, 28.10.2016, 19:20
Any news?

Leave a comment

Copyright - 2017 Informer Technologies, Inc. All Rights Reserved. Feedback system is used Idea.Informer.com