Hi all, we've just released some new tools for RIS, which may also benefit you :) The most notable change is the introduction of the AS dashboard and prefix dashboard. These dashboards show an overview of most information RIS has about an AS or prefix. For ASes, think prefixes, age of prefixes, transits, old bogon filters. For prefixes, think visibility and stability. Besides this, we have made improvements to the search, prefixinuse and asinuse tools. - The search can now summarise updates for a clearer view of events - Prefixinuse now also displays prefixes from a block that are 'free' and shows what percentage of space is still unannounced - ASinuse should run faster Focus with these improvements is to improve the presentation of the data, making more data available in a clearer and more attractive way. For example, see the prefix dashboard of the RIPE meeting network prefix, which had some reachability problems: http://www.ris.ripe.net/dashboard/193.0.8.0/22 The prefix graph for 3333, our office network, nicely shows the build- up of our prefixes: http://www.ris.ripe.net/dashboard/3333 It also shows our transits, although this is difficult to estimate and wrong in some cases. The k-root dashboard shows an /28 in the prefix list - seen by two peers. The prefix graph is also quite nice: http://www.ris.ripe.net/ dashboard/25152 If you check/uncheck the "strip prepending" box on the AS path lengths tab, you can clearly see the prepending done by k-root. The dashboards for the k-root anycast prefixes also show something interesting: http://www.ris.ripe.net/dashboard/193.0.14.0/24 http://www.ris.ripe.net/dashboard/193.0.14.0/23 If you look at the "list of peers not seeing the prefix" below the map, you can see 20932 doesn't send the /24, and 26943 doesn't send either. Note that there still is a small bug in the AS dashboard - it shows a prefix has stopped being announced in some cases when it is not. These tools are public now, so feel free to tell others. However, we are not doing an external announcement until the RIPE meeting, to prevent everyone from already knowing most things we'll say in the RIS update. So, don't shout around on lists/websites/etc. yet. Obviously, if you have any ideas, let us know. cheers, -- Erik Romijn RIPE NCC software engineer http://www.ripe.net/ Information Services dept.
Hi Erik, On Fri, 12 Oct 2007 12:17:13 +0200, Erik Romijn <eromijn@ripe.net> wrote:
Hi all,
we've just released some new tools for RIS, which may also benefit you :)
I've had a look from home, and it looks very slick. Nice work! :-) ...
The k-root dashboard shows an /28 in the prefix list - seen by two peers. The prefix graph is also quite nice: http://www.ris.ripe.net/ dashboard/25152 ...
I'm surprised to see 9430-STPI-NOIDA taking such a large piece (33%) of the upstream pie. How should I interpret that ? Maybe as the Dehli global node having better connectivity than the Linx node (7% in pie) ? I would be surprised if that was the case. The expandable explanation doesn't really make it clear to me what the percentages are based on (but maybe it's obvious to network admins). Is it that 33% of all unique routes ending in 25152, seen by all RRCs, end with 9430-25152, regardless of re-announcements ? Or is it just anycast related weirdness ? Anyhow, it's nice to see enhancements like this dashboard. I'm looking forward to more! Thanks, E m i l .
Erik, This is really cool!
Obviously, if you have any ideas, let us know.
1. Move the traffic lights to the top of the page. This is probably the thing people want to see first (green lights, no problem, go do something else). 2. The 'BGPlay' button needs a bit of explanation. 3. http://www.ris.ripe.net/dashboard/193.0.14.0/24 The text betweent the 2 traffic lights says: 1 update in the last 48 hrs. There is a peak of 40 updates on Monday though. Not for this page, but I think it'd be great if we pasted this URL into the messages RS uses when they give out a block. ('You have been allocated 1.2.3.4/5, click www.ris.ripe.net/dashboard 1.2.3.4/5 to see how it is routed once you start using it'). Henk -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Is one of the choices leaving the office open? Alan Greenspan on the next elections
On 24 Oct 2007, at 14:42, Henk Uijterwaal wrote:
Erik,
This is really cool!
This is indeed a very valuable tool!
Obviously, if you have any ideas, let us know.
1. Move the traffic lights to the top of the page. This is probably the thing people want to see first (green lights, no problem, go do something else).
2. The 'BGPlay' button needs a bit of explanation.
3. http://www.ris.ripe.net/dashboard/193.0.14.0/24 The text betweent the 2 traffic lights says: 1 update in the last 48 hrs. There is a peak of 40 updates on Monday though.
Not for this page, but I think it'd be great if we pasted this URL into the messages RS uses when they give out a block. ('You have been allocated 1.2.3.4/5, click www.ris.ripe.net/dashboard 1.2.3.4/5 to see how it is routed once you start using it').
There might be a small interpretation issue with leaked routes, (which is already known btw, and being amended) example, we have our RIPE's IPv6 /42 prefix which is normally routed through surfnet bigger /32. But apparently some parties seem to strip the no-export community which causes the routes to be leaked. http://www.ris.ripe.net/dashboard/2001:610:240::/42 In this particular case, "Visibility" is "Leakage" Regards, Ruben
Henk
-- ---------------------------------------------------------------------- -------- Henk Uijterwaal Email: henk.uijterwaal(at) ripe.net RIPE Network Coordination Centre http:// www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ---------------------------------------------------------------------- --------
Is one of the choices leaving the office open? Alan Greenspan on the next elections
-- Ruben van Staveren RIPE Network Coordination Center Information Services Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 PGP finger print 6501 4389 A675 477E DCE5 53D8 9108 49E2 DAFC 271B
example, we have our RIPE's IPv6 /42 prefix which is normally routed through surfnet bigger /32. But apparently some parties seem to strip the no-export community which causes the routes to be leaked.
which, because of the longest prefix match rule, resulted in quite "interesting" reachability paths for RIPE NCC IPv6 adresses in the past. TTM recorded cases where the /42 made packets originating in Europe first travel to the US (hurricane electric IIRC) before getting back to AMS. Not good for user experience ...
http://www.ris.ripe.net/dashboard/2001:610:240::/42
In this particular case, "Visibility" is "Leakage"
Regards, Ruben
Henk
-- ---------------------------------------------------------------------- -------- Henk Uijterwaal Email: henk.uijterwaal(at) ripe.net RIPE Network Coordination Centre http:// www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ---------------------------------------------------------------------- --------
Is one of the choices leaving the office open? Alan Greenspan on the next elections
-- Ruben van Staveren RIPE Network Coordination Center Information Services Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 PGP finger print 6501 4389 A675 477E DCE5 53D8 9108 49E2 DAFC 271B
[ taken eng and rs-staff out, as this gets a bit too detailed ] [ this might not get through on sg@, as it appears to be subscriber only ] On Oct 24, 2007, at 2:42 PM, Henk Uijterwaal wrote:
3. http://www.ris.ripe.net/dashboard/193.0.14.0/24 The text betweent the 2 traffic lights says: 1 update in the last 48 hrs. There is a peak of 40 updates on Monday though.
As the explanation says, the text gives updates per peer. The graph does total. Besides that, the text has a semi-smart algorithm to try not to blame people of instability when one of the people sending us their prefix is just unstable themselves :) On the traffic lights position: it is important to know whether or not there are more/less specifics - as that makes the difference between "IPs from this prefix are not very visible" and "this specific prefix is not visible, but as there is a less specific this does not affect connectivity". I hope my talk in the routing-wg will get us some more feedback, and will allow us to improve further. This is not a fully finished project yet ;) cheers, -- Erik Romijn RIPE NCC software engineer http://www.ripe.net/ Information Services dept.
participants (5)
-
Emil Gorter -
Erik Romijn -
Henk Uijterwaal -
Rene Wilhelm -
Ruben van Staveren