- Ris-int - mailman.ripe.net

myASn status slide for Mon's meeting
by Matthew Williams 26 Jul '04

26 Jul '04

Hi Gang, Discussion fodder? ;) Cheers, Matthew

3 4

Re: RIS Statistics Report
by Arife Vural 26 Jul '04

26 Jul '04

It looks I missed to update Weekly Report, I will add it. Arife On Mon, Jul 26, 2004 at 08:53:28AM +0200, Henk Uijterwaal (RIPE NCC) wrote: > > I just noticed that RRC12 is not in the table yet. > > Henk > > > On Mon, 26 Jul 2004, Generic RIS account wrote: > > > > > RIS Statistics Report (20040719-20040726) > > > > This report was generated at Mon Jul 26 00:15:01 UTC 2004. It analyses the BGP > > Routing Tables which are collected by RIS Remote Collectors at different locations > > around the world. Check http://www.ris.ripe.net/weekly-report/ for more info. > > > > o Prefix Distribution > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > APNIC 27343 26793 26079 15703 27061 20508 26186 26433 26368 13545 25282 19216 > > ARIN 62135 61390 59038 24057 61836 58807 60725 59804 60640 9111 58800 54355 > > LACNIC 7015 5982 5959 3310 6998 5664 5983 5976 5959 1455 5930 5215 > > RIPE NCC 31065 25503 24552 14214 30629 20246 24976 24851 24651 6889 24454 19356 > > OLD 31546 30909 29342 13460 31184 27157 29943 30174 29430 6630 29076 26023 > > IANA 1733 973 889 601 1714 796 909 882 915 166 881 689 > > RFC1918 4 0 0 0 4 0 0 0 0 0 0 0 > > OTHER 0 0 0 0 0 0 0 0 0 0 0 0 > > TOTAL 160841 151550 145859 71345 159426 133178 148722 148120 147963 37796 144423 124854 > > > > > > AS number distributions wrt RIR and single-homed/multi-homed. > > > > o ASes per RIR region > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 10119 10078 10000 254 10076 9838 10041 10020 9999 2982 9973 9218 > > APNIC 2051 2050 2028 35 2050 1706 2038 2030 2023 1242 2020 1543 > > RIPE NCC 5725 5702 5672 2322 5715 5029 5497 5664 5625 2130 5685 4877 > > LACNIC 62 62 57 7 61 61 62 62 57 25 57 56 > > IANA 1 1 1 0 1 1 1 1 1 1 1 1 > > Private 22 10 6 3 16 2 11 3 5 2 5 6 > > Others 1 0 0 1 1 0 0 0 0 0 0 0 > > Total 17981 17903 17764 2622 17920 16637 17650 17780 17710 6382 17741 15701 > > > > > > o Number of single-homed ASes. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 2948 3675 4762 160 3266 4842 4068 5892 4086 1787 4781 4348 > > APNIC 526 612 706 28 593 673 704 1134 759 610 826 687 > > RIPE NCC 1586 1973 2113 1433 1739 2079 2058 3346 2106 1199 2481 2251 > > LACNIC 30 31 30 7 30 31 32 39 28 18 31 30 > > IANA 1 1 1 0 1 1 1 1 1 1 1 1 > > Private 15 10 6 1 13 2 9 3 5 2 4 6 > > Others 0 0 0 1 0 0 0 0 0 0 0 0 > > Total 5106 6302 7618 1630 5642 7628 6872 10415 6985 3617 8124 7323 > > > > > > o Number of multi-homed ASes. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 7171 6403 5238 94 6810 4996 5973 4128 5913 1195 5192 4870 > > APNIC 1525 1438 1322 7 1457 1033 1334 896 1264 632 1194 856 > > RIPE NCC 4139 3729 3559 889 3976 2950 3439 2318 3519 931 3204 2626 > > LACNIC 32 31 27 0 31 30 30 23 29 7 26 26 > > IANA 0 0 0 0 0 0 0 0 0 0 0 0 > > Private 7 0 0 2 3 0 2 0 0 0 1 0 > > Others 1 0 0 0 1 0 0 0 0 0 0 0 > > Total 12875 11601 10146 992 12278 9009 10778 7365 10725 2765 9617 8378 > > > > IANA : AS65535 > > > > Others: AS65535 > > > > Distribution of AS number wrt Leaf, Transit. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > Leaf 14834 14916 14872 1980 14863 13925 14701 15177 14882 4960 14967 13148 > > Transit 3041 2885 2783 440 2956 2516 2823 2515 2719 927 2681 2293 > > Transit-only 106 102 109 202 101 196 126 88 109 495 93 260 > > Total 17981 17903 17764 2622 17920 16637 17650 17780 17710 6382 17741 15701 > > > > > > o Average ASPATH length. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > Avg 6.14 5.91 5.94 5.68 6.13 6.01 6.23 6.12 6.43 5.89 5.85 6.04 > > Std 2.73 2.65 2.81 3.20 2.76 2.42 2.85 2.37 2.63 2.82 2.44 2.24 > > > > o List of martians appearing throughout the week. > > > > Prefix Origin AS > > 192.168.90.0/24 5417 > > 192.168.91.0/24 5417 > > 192.168.191.0/24 5417 > > > > > > o List of hot-spots during the week. > > > > Prefix Origin AS Number of updates > > 209.182.81.0/24 19071 203706 > > 209.114.254.0/24 14359 157276 > > 195.239.204.0/24 3216 134771 > > 195.218.176.0/24 3216 132598 > > 139.91.40.0/24 8522 121002 > > 139.91.252.0/24 8522 110100 > > 202.140.156.0/22 9910 80133 > > 209.205.84.0/24 15066 73047 > > 209.205.81.0/24 15066 73044 > > 194.133.184.0/21 0 67260 > > > > > > Total number of RIS BGP peering sessions: 416 > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent).

1 0

Re: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Rene Wilhelm 25 Jul '04

25 Jul '04

> > No, but people tend to reply to the last mail they have in their files, > > if you use something like hm-ack(a)r.n it looks as if a human will read > > it. > > We have an address for this, called <unread(a)ripe.net>. Why does the autoresponse have to come from an unread email account? If I were a user and needed to add info to a ticket or query it's status, it would be most convenient if I could reply to the first (auto)reply to my initial message, as that ensures I get the ticket number right. This is how the OPS & TT-OPS ticketing systems work. (ok the tt ticketing system, currently doesn't autoreply, but if it would, it would send one "From: tt-ops") -- Rene

4 3

Re: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Rene Wilhelm 23 Jul '04

23 Jul '04

>> Why does the autoresponse have to come from an unread email account? > For RIPE DBM we do this to avoid mail loops (I think - Oleg knows more about > these mysteries than I do). ah, right! loops should indeed be avoided in automated response systems, mail servers could quickly come to a grinding halt. (IIRC, NCC has had it's shares of loop problems with the hostmaster robot in the past) > For hostmasters, the "From:" is actually <hostmaster(a)ripe.net>. I guess it > makes sense for the "From:" to be <ris(a)ripe.net> in this case. If it cannot create loops, from (or reply-to for that matter) <ris(a)ripe.net> would be great for tickets coming in to ris. -- Rene

1 0

FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Matthew Williams 23 Jul '04

23 Jul '04

Peering requests hasn't worked very well in the past. Good work :) Cheers, Matthew > -----Original Message----- > From: RIPE NCC Acknowledgements [mailto:hm-ack@ripe.net] > Sent: 23 July 2004 14:48 > To: RIS Peering Request > Subject: NCC#2004073298 Re: rrc01:PEERING 8210 > > > Greetings, > > This message has been automatically generated in response to the > e-mail: > > To: RIS Peerings<rispeering(a)ripe.net> > From: RIS Peering Request <risops(a)ripe.net> > Date: Fri, 23 Jul 2004 12:47:44 GMT > Message-ID: <200407231247.i6NCli3U013164(a)halfweg.ripe.net> > Subject: rrc01:PEERING 8210 > > There is no need to reply to this message right now. Your > ticket has been assigned an ID of "NCC#2004073298". Please > include this string in the subject line of any further > correspondence on this matter. > > For more information about the RIPE NCC RIS Project, please > refer to http://www.ripe.net/ris/. > > Thank you, > > RIPE NCC Software Department >

5 6

RIS move status
by Henk Uijterwaal (RIPE NCC) 23 Jul '04

23 Jul '04

Arife, Can I have a few minutes on Monday's agenda to go over the status of the move, see attached MPP file with details? Thx, 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent).

3 2

FW: [ris-int] Re: RRC12 announcement on www.ripe.net
by Matthew Williams 23 Jul '04

23 Jul '04

Hi Adrian, Rene came up with the idea to link announcements to a little RIS intro page with a few links. Is that something you can help us with? Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of RIPE NCC Webmaster > Sent: 23 July 2004 15:49 > To: Matthew Williams > Cc: ris-int(a)ripe.net; 'Rene Wilhelm' > Subject: Re: [ris-int] Re: RRC12 announcement on www.ripe.net > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > * > OK, maybe you, Arife or Matthew can make a page in ris/news > * > with the content of the announcement? We don't really want > * > to link to messages in mail archives.. > * > * Sure, we could do that. Mind you, what is Adrian up to > nowadays? Great opportun > * ity to dig into the RIS aspect of IS... ;) > > Talk to Adrian. BTW, if you want him to change RIS pages, > make sure you add him to the projects group. > > -J > > * > * Cheers, > * Matthew > * > * > -----Original Message----- > * > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > * > On Behalf Of RIPE NCC Webmaster > * > Sent: 23 July 2004 13:25 > * > To: Rene Wilhelm > * > Cc: ris-int(a)ripe.net > * > Subject: [ris-int] Re: RRC12 announcement on www.ripe.net > * > > * > > * > > * > Rene Wilhelm <wilhelm(a)ripe.net> writes: > * > * > * > * I didn't keep track of it myself, but an external user noticed > * > * this announcement on www.ripe.net yesterday, JULY 22. The date > * > * seems wrong :( > * > > * > Damn.. I changed it to 20 July. > * > > * > * > * > * RIPE NCC Announcements > * > * > * > * [22 June 2004] > * > * RIPE NCC Remote Route Collector Deployed at German > * > Internet Exchange (DE-CIX > * > * ) > * > * > * > * > * > * I was also wondering if it wouldn't be better to make the link > * > * point to a page with the announcement that was send out to > * > ris-users, > * > * (copied below) rather than jump deep down into the > RIS web tree. > * > * The announcement puts things more into context with a > paragraph > * > * summarizing the project and pointers to more RIS info > at the end. > * > * The http://www.ripe.net/ris/rrc12.html page seems more > * > * targeted at people who already familiar with RIS and just > * > * want to learn where the box is, what the peering policy and > * > * peering details are. > * > * > * > > * > OK, maybe you, Arife or Matthew can make a page in ris/news > * > with the content of the announcement? We don't really want > * > to link to messages in mail archives.. > * > > * > -J > * > > * > > * > * > * > * -- Rene > * > * > * > * > * > * > From: ris-users-admin(a)ripe.net > * > * > [mailto:ris-users-admin@ripe.net] On Behalf Of > Matthew Williams > * > * > Sent: 07 July 2004 19:11 > * > * > To: ris-users(a)ripe.net > * > * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > * > * > DE-CIX (RRC12) > * > * > > * > * > [Apologies for duplicate mails] > * > * > > * > * > Dear All, > * > * > > * > * > The RIPE NCC is pleased to announce that the RIS Project's > * > * > twelth* Remote Route Collector, RRC12, is now ready to peer > * > * > with members at the German Internet Exchange (DE-CIX). > * > * > > * > * > RRC12 is located at the German Internet Exchange (DE-CIX), > * > * > and has been operational since July 2004. The RRC has an > * > * > interface on the shared DE-CIX fabric, running both > IPv4 and > * > * > IPv6, and collects routing information from all exchange > * > * > members, who are willing to peer with us. > * > * > > * > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is > * > * > supported on all RIS Route Collectors. MD5, however, is not > * > * > supported on IPv6 sessions. > * > * > > * > * > Details: > * > * > -------- > * > * > - Peering address: 80.81.192.152 (IPv4); > * > 2001:7f8::316e:0:1 (IPv6) > * > * > - Autonomous system: 12654 > * > * > - Policy: http://www.ripe.net/ris/rrc12.html > * > * > - Peering requests: > * > * > * Email: rispeering(a)ripe.net > * > * > * Web form at URL: > * > http://www.ris.ripe.net/cgi-bin/peerreg.cgi > * > * > > * > * > The > * > Routing Information Service (RIS), which started as a > * > * > modest RIPE NCC project in 1999, has gradually > grown to over > * > * > 300 IPv4 and IPv6 peers at now twelve* data > collection points > * > * > in Europe, Japan and North America. Our mission is > to collect > * > * > BGP routing information over a function of time, > and make it > * > * > available to the Internet community. In essence, this means > * > * > devising tools that can help ISPs debug problems over time > * > * > without being limited to one BGP view and providing RIS raw > * > * > data regarding the Internet's historical development. > * > * > > * > * > Useful Links: > * > * > ------------- > * > * > RIS Info: http://www.ripe.net/ris/ > * > * > RIS Tools: http://www.ripe.net/ris/query.html > * > * > List of RRC Locations: > * > http://www.ris.ripe.net/cgi-> bin/rrcstatus.cgi > * > * > > * > * > > * > Please send your comments to > * > ris-int(a)ripe.net. > * > * > > * > * > Best regards, > * > * > The RIS Team > * > * > > * > * > *) RRC09 has been decommissioned > * > * > > * > * > --- > * > * > > Matthew Williams (MW243-RIPE) > * > * > > Customer Liaison Engineer > * > * > > RIPE NCC - http://www.ripe.net/np/ > * > * > * > > * >

1 0

RRC12 announcement on www.ripe.net
by Rene Wilhelm 23 Jul '04

23 Jul '04

I didn't keep track of it myself, but an external user noticed this announcement on www.ripe.net yesterday, JULY 22. The date seems wrong :( RIPE NCC Announcements [22 June 2004] RIPE NCC Remote Route Collector Deployed at German Internet Exchange (DE-CIX) I was also wondering if it wouldn't be better to make the link point to a page with the announcement that was send out to ris-users, (copied below) rather than jump deep down into the RIS web tree. The announcement puts things more into context with a paragraph summarizing the project and pointers to more RIS info at the end. The http://www.ripe.net/ris/rrc12.html page seems more targeted at people who already familiar with RIS and just want to learn where the box is, what the peering policy and peering details are. -- Rene > From: ris-users-admin(a)ripe.net > [mailto:ris-users-admin@ripe.net] On Behalf Of Matthew Williams > Sent: 07 July 2004 19:11 > To: ris-users(a)ripe.net > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering(a)ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int(a)ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/

3 3

ris@ripe.net e-mail are ticketized from now on.
by Arife Vural 23 Jul '04

23 Jul '04

Hi guys, ris e-mails are ticketized from now on. ris is staying as mailinglist, and one copy of the e-mail is going to RIS ticketing que. People who are in the ris list will continue get the all ris e-mails. If you do not want, ask OPS to remove your e-mail address. But, please if you like to reply any of those e-mails, use XRTT. Otherwise, we loose control who replied which e-mail and so. Arife

1 0

MSK-IX RRC
by Matthew Williams 23 Jul '04

23 Jul '04

Just thinking out loud: In order to circumvent excessive $$$ at Russian customs, wouldn't it be smarter to have the IXP order a Dell PowerEdge to OPS requirements and ship your nifty little CD instead? Would that work or should we just go down the normal route. I will naturally have to ask the IXP as well. Cheers, Matthew

3 5

Other RIS things ...
by Matthew Williams 23 Jul '04

23 Jul '04

Hi Arife, Mae-West doesn't seem to be picking up in peers (4 - and according to Hong-Wei, no full feeds). It was some time ago since you tried to get their attention (nanog in miami?). After the good experiences at the NYIIX, shall we try LAIX? What do you think? BC thought that we should wait until the end of the year, but that requires giving gebert, bechly and pucik a little push (again). BTW, have you thought about cleaning up active bgp session or it that ops work? If they already have tools to monitor anycast and 3333 sessions then maybe the RIS could just plug into that. Cheers, Matthew +++ RRC00 ----- 195.66.224.112 4 3549 0 0 0 0 0 never Active | 195.69.144.85 4 3257 0 0 0 0 0 never Connect | RRC01 ----- 195.66.224.40 4 15861 0 0 0 0 0 never Active | 195.66.224.41 4 5604 0 0 0 0 0 never Active | 195.66.224.48 4 1299 0 0 0 0 0 never Active | 195.66.224.117 4 12513 0 0 0 0 0 never Active | 195.66.224.168 4 20940 0 10123 0 0 0 never Active | 195.66.226.10 4 2856 86 9 0 0 0 03w5d22h Connect | 195.66.226.11 4 2856 85 9 0 0 0 03w5d22h Connect | 195.66.226.40 4 15861 0 0 0 0 0 never Active | 195.66.226.47 4 8272 0 0 0 0 0 never Active | 195.66.226.103 4 2818 442 299 0 0 0 2d15h56m Active | 195.66.226.119 4 12390 0 0 0 0 0 never Connect | RRC02 ----- 194.68.129.164 4 13237 0 0 0 0 0 never Active | 194.68.129.173 4 6774 0 0 0 0 0 never Connect | 194.68.129.186 4 20766 356 355376 0 0 0 4d15h53m Idle | 194.68.129.225 4 5462 0 0 0 0 0 never Active | 194.68.129.252 4 2686 0 0 0 0 0 never Active | Etc....

4 4

myASN SQL queries
by Arife Vural 22 Jul '04

22 Jul '04

Hi Alexis, Today, when I looked at mySQL logs, I saw the one of myASN query and it returns almost all the entries in table. I do not know that was the intention or not. But, when we meet up for handover, I would like to go over those SQLs with you whether we can do any optimization or not. BTW, I hope tomorrow morning is OK for you. I have not got a reply from you yet. Arife

1 0

myASN transition on Wed, 14.00
by Arife Vural 21 Jul '04

21 Jul '04

Hi guys, What about working myASN transition on Wed, 14.00? Arife

4 6

We need your fb again ;)
by Matthew Williams 21 Jul '04

21 Jul '04

Hi Comms, Please see explanations here: http://www.ripe.net/ris/myasngls.html#50 And then think about alternative terms for below: *Hold Down Time *Hold Down Event: 'Min-Event-Duration' and 'Min-Event-Count' are our current candidates. *Time To Live: We have two lines of thought here. One relates to 'detection' of events building up to an alarm entry in the email sent to the user, while the other follows the line of 'suppression' of further entries once the first entry has been triggered (based on exactly the same events). If we go along with the second concept, then this is a maximum time interval. In the first case, we're talking about a fixed 'window' (time interval). I hope all that made sense ;) Here come some suggestions: "Event-count Window", "Alarm-Suppress-Time", "Max-suppress-time", "Event-Suppress-Time', "max-detect-window", "alarm-detect-window"... Etc etc... We could go on forever and ever. The question is: What works for you? The beta is more or less ready so we need to get this one out of the way once and for all... ;) Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

4 4

Today's RIS meeting minutes
by Arife Vural 21 Jul '04

21 Jul '04

Main points: - RIS budget issue is discussed. New RRC hardware and replacement would be in OPS budget. Arife compiled the needs for RIS server and sent it to Shane. Shane will discuss this with Henk/Andrei. Shane suggest to make an analysis how many RIS servers we like to install and then do the installation at one go, rather than each year putting 2 new RRCs in budget. Matthew mentioned installation of 2 new RRCs (Dubai, Moscow) are in discussion. - This week Arife and Alessandro from SED will sit down with Alexis to talk about myASN transition. - After RIS transition it seems a lot of thing is settle down, because of that there is not much need to do RIS meeting every week. From now on, there will be RIS meeting once in two week. Arife will update the Ctime accordingly. Any correction/addition/comments are welcome. Arife

2 2

myasn xml
by Alexis Yushin 15 Jul '04

15 Jul '04

Hi, I've just added http://www.ris.ripe.net/myasn/xml.html, a page to import myASn configuration as XML... Its not linked into index yet, since it has not been properly tested. Syntax is something like: <alarmgroup name="XML-Import"> <alarm type="origin" mec="1" med="1m" ast="1h"> <prefix>193.0.0.0/16</prefix> <exception>193.0.1.0/24</exception> <exception>193.0.2.0/24</exception> <myasn>12324 2344</myasn> </alarm> <alarm type="customer"> <prefix>193.0.0.0/16</prefix> <exception>193.0.1.0/24</exception> <exception>193.0.2.0/24</exception> <myasn>12324 2344</myasn> <theirasn>12324 2344</theirasn> </alarm> </alarmgroup> You get the idea... Alexis

1 0

Re: [staff] DHL: received goods
by James Aldridge 15 Jul '04

15 Jul '04

Saskia van Gorp wrote: > Hi all, > > Did anybody around end of June - beginning of July receive a package from > Vienna (Austria) > Airway bill: 582 5977511 > Ref: inivie/vix > Sent out from Vienna on June 26. I guess that this was the old RIS Route Collector (rrc05) being returned. James

1 0

FW: ANNOUNCEMENT: New RIS Remote Route Collector at DE-CIX (RRC12)
by Matthew Williams 14 Jul '04

14 Jul '04

Hi Webbies, Would it be possible to link http://www.ripe.net/ris/rrc12.html from http://www.ripe.net/ ? Text something like: "RIPE NCC Remote Route Collector deployed at the German Internet Exchange (DE-CIX)" Many thanks! Cheers, Matthew > -----Original Message----- > From: Matthew Williams [mailto:matthew@ripe.net] > Sent: 07 July 2004 19:11 > To: 'ris-users(a)ripe.net' > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > > > > *** PGP Signature Status: good > *** Signer: Matthew Williams-Bywater <matthew(a)ripe.net> > *** Signed: 07/07/2004 19:11:05 > *** Verified: 14/07/2004 18:50:15 > *** BEGIN PGP VERIFIED MESSAGE *** > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering(a)ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int(a)ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ > > > *** END PGP VERIFIED MESSAGE *** >

1 0

Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
by Rene Wilhelm 14 Jul '04

14 Jul '04

Hi, > ... myASn can use reply-to address forwarded to /dev/null Are we sure we want that? How often does it happen? Shouldn't there be follow by a risopsy when a notification fails to be delivered? (for permanent failures, either try to get in touch with representatives of the AS to correct the address, or deconfigure the alarm???) -- Rene > Hi guys, > > Can we do this? > > Arife > > ----- Forwarded message from Alexis Yushin <alexis(a)ripe.net> ----- > > From: Alexis Yushin <alexis(a)ripe.net> > To: matthew(a)ripe.net (Matthew Williams) > Subject: Re: [MAILER-DAEMON(a)ripe.net: Undelivered Mail Returned to Sender] > Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) > Cc: alexis(a)ripe.net (Alexis Yushin), arife(a)ripe.net (Arife Vural), > ris-int(a)ripe.net > > Arife, > > We need to add risops to the trusted users class in sendmail.cf on weesp. > Something like > > FEATURE(`use_ct_file') dnl > > and > > /etc/mail/trusted-users > uucp > root > daemon > risops > > So myASn can use reply-to address forwarded to /dev/null > > Alexis > > > Once Matthew Williams wrote: > >Hi Alexis, > > > >Working on this? > > > >Cheers, > >Matthew > > > >----- Forwarded message from Mail Delivery System <MAILER-DAEMON(a)ripe.net> ----- > > > >X-Recipient: <risops(a)ripe.net> > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) > >Subject: Undelivered Mail Returned to Sender > >To: risops(a)ripe.net > > > >Content-Description: Notification > >This is the Postfix program at host postman.ripe.net. > > > >I'm sorry to have to inform you that the message returned > >below could not be delivered to one or more destinations. > > > >For further assistance, please send mail to <postmaster> > > > >If you do so, please include this problem report. You can > >delete your own text from the message returned below. > > > > The Postfix program > > > ><asnalarm(a)linkey.ru>: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > > mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Delivery error report > >Reporting-MTA: dns; postman.ripe.net > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > >Final-Recipient: rfc822; asnalarm(a)linkey.ru > >Action: failed > >Status: 5.0.0 > >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > > no mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Undelivered Message > >Date: Tue, 13 Jul 2004 21:43:49 GMT > >From: myASn Notifications <myasn(a)ripe.net> > >To: asnalarm(a)linkey.ru > >Subject: New alarms for 13302 > >X-RIPE-Spam-Level: > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > >Dear myASn contact, > > > >New alarms were detected for 13302. Please find the details below. Depending on your detail > >level settings you might not see all the events. Please use the web interface for further details. > > > >-- myASn System > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. > >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | > >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| > >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | > >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > > > > >----- End forwarded message ----- > > > >-- > >>Matthew Williams > >>Customer Liaison Engineer > >>RIPE - Network Coordination Centre (www.ripe.net) > > > > ----- End forwarded message ----- >

4 4

Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
by Rene Wilhelm 14 Jul '04

14 Jul '04

>> Shouldn't there be follow up by a risopsy when a notification >> fails to be delivered? (for permanent failures, either try > Quite unlikely, if I know that alarm notifications were successfully > sent to my inbox. Sorry, I don't understand your reply. If a mail from the myASn system bounces, someone should in my opinion take action. Either the user made a mistake, typo, entering the e-mail address in the myASn system, or he has left the ISP owning the ASn. risops could try to get in touch with the ASn owner, to get the email address corrrected (remember, we are running a _service_ ) or when that fails remove the address from the alarm system (no point polluting internal an external systems with e-mails you know will bounce back) Also, when the human recipients behind a remote e-mail change, they might reply, querying what the message was about; it's not polite to silently ignore such one-off replies. -- Rene > > We need to add risops to the trusted users class in sendmail.cf on > > weesp. Something like > > So myASn can use reply-to address forwarded to /dev/null > > > > Once Matthew Williams wrote: > > >Hi Alexis, > > > > > >Working on this? > > > > > >Cheers, > > >Matthew > > > > > >----- Forwarded message from Mail Delivery System > > ><MAILER-DAEMON(a)ripe.net> ----- > > > > > >X-Recipient: <risops(a)ripe.net> > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) > > >Subject: Undelivered Mail Returned to Sender > > >To: risops(a)ripe.net

2 2

Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]
by Alexis Yushin 14 Jul '04

14 Jul '04

Arife, We need to add risops to the trusted users class in sendmail.cf on weesp. Something like FEATURE(`use_ct_file') dnl and /etc/mail/trusted-users uucp root daemon risops So myASn can use reply-to address forwarded to /dev/null Alexis Once Matthew Williams wrote: >Hi Alexis, > >Working on this? > >Cheers, >Matthew > >----- Forwarded message from Mail Delivery System <MAILER-DAEMON(a)ripe.net> ----- > >X-Recipient: <risops(a)ripe.net> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops(a)ripe.net > >Content-Description: Notification >This is the Postfix program at host postman.ripe.net. > >I'm sorry to have to inform you that the message returned >below could not be delivered to one or more destinations. > >For further assistance, please send mail to <postmaster> > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > ><asnalarm(a)linkey.ru>: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Delivery error report >Reporting-MTA: dns; postman.ripe.net >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >Final-Recipient: rfc822; asnalarm(a)linkey.ru >Action: failed >Status: 5.0.0 >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > no mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Undelivered Message >Date: Tue, 13 Jul 2004 21:43:49 GMT >From: myASn Notifications <myasn(a)ripe.net> >To: asnalarm(a)linkey.ru >Subject: New alarms for 13302 >X-RIPE-Spam-Level: >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > >Dear myASn contact, > >New alarms were detected for 13302. Please find the details below. Depending on your detail >level settings you might not see all the events. Please use the web interface for further details. > >-- myASn System > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > >----- End forwarded message ----- > >-- >>Matthew Williams >>Customer Liaison Engineer >>RIPE - Network Coordination Centre (www.ripe.net) >

3 4

[alexis@ripe.net: Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]]
by Arife Vural 14 Jul '04

14 Jul '04

Hi guys, Can we do this? Arife ----- Forwarded message from Alexis Yushin <alexis(a)ripe.net> ----- From: Alexis Yushin <alexis(a)ripe.net> To: matthew(a)ripe.net (Matthew Williams) Subject: Re: [MAILER-DAEMON(a)ripe.net: Undelivered Mail Returned to Sender] Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) Cc: alexis(a)ripe.net (Alexis Yushin), arife(a)ripe.net (Arife Vural), ris-int(a)ripe.net Arife, We need to add risops to the trusted users class in sendmail.cf on weesp. Something like FEATURE(`use_ct_file') dnl and /etc/mail/trusted-users uucp root daemon risops So myASn can use reply-to address forwarded to /dev/null Alexis Once Matthew Williams wrote: >Hi Alexis, > >Working on this? > >Cheers, >Matthew > >----- Forwarded message from Mail Delivery System <MAILER-DAEMON(a)ripe.net> ----- > >X-Recipient: <risops(a)ripe.net> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops(a)ripe.net > >Content-Description: Notification >This is the Postfix program at host postman.ripe.net. > >I'm sorry to have to inform you that the message returned >below could not be delivered to one or more destinations. > >For further assistance, please send mail to <postmaster> > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > ><asnalarm(a)linkey.ru>: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Delivery error report >Reporting-MTA: dns; postman.ripe.net >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >Final-Recipient: rfc822; asnalarm(a)linkey.ru >Action: failed >Status: 5.0.0 >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > no mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Undelivered Message >Date: Tue, 13 Jul 2004 21:43:49 GMT >From: myASn Notifications <myasn(a)ripe.net> >To: asnalarm(a)linkey.ru >Subject: New alarms for 13302 >X-RIPE-Spam-Level: >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > >Dear myASn contact, > >New alarms were detected for 13302. Please find the details below. Depending on your detail >level settings you might not see all the events. Please use the web interface for further details. > >-- myASn System > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > >----- End forwarded message ----- > >-- >>Matthew Williams >>Customer Liaison Engineer >>RIPE - Network Coordination Centre (www.ripe.net) > ----- End forwarded message -----

1 0

rrc12
by Matthew Williams 13 Jul '04

13 Jul '04

Hi Arife, Are we ready to announce RRC12? Cheers, Matthew

3 12

Re: FW: [ris-int] Logging on to rrcs
by Rene Wilhelm 13 Jul '04

13 Jul '04

Hi James, > Matthew wrote: > > > > > Please add me to users who can logon to rrcs :) > > > > Please open a ticket using "stt ops" or via the form on iii > > James while I can understand mailto:ops, I still have difficulty seeing any benefit in "stt" or webform. What difference does it make to ops? Do you (yes you're one of "them" now:-) have seperate queues for each (sub)category? Or are these purely administrative, to see how many tickets in which category were handled by which person? Why does the user have to classify his ticket? isn't that better done by ops? -- Rene

1 0

FW: [ris-int] Logging on to rrcs
by Matthew Williams 13 Jul '04

13 Jul '04

Hi there, Please add me to users who can logon to rrcs :) Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of Arife Vural > Sent: 13 July 2004 15:43 > To: Matthew Williams > Cc: ris-int(a)ripe.net > Subject: Re: [ris-int] Logging on to rrcs > > > > Hi Matthew, > > It looks your username is not in /etc/passwd file on RRCs. > Can you send an e-mail to OPS to add? > > Arife > > On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > > > > Hi Matthew, > > > > > I seem to have some probs logging on.... (all rrcs?) > > > > > > > You have to login by your username, and then if you need you > > can run sudo command switch to risops or root user. After > > Linux migration, OPS changed login to RRC boxes from risops > > to individual users. This way it would more easy for OPS to > > keep track who runs which command and so. > > > > BTW, if you need to connect BGPD on RRCs you do not need > > to loging box, you can run, > > > > telnet rrc031 2605 > > > > That connection is open only RIPE NCC prefix. > > > > Arife > > > > > matthew@cow at 15:22:15:~$ ssh rrc031 -l risops > > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > the list of > > > known hosts. Permission denied (publickey,keyboard-interactive). > > > > > > matthew@cow at 15:22:20:~$ ssh rrc021 -l risops > > > Permission denied (publickey,keyboard-interactive). > > > > > > Cheers, > > > Matthew >

2 2