July 2004 - Ris-int - mailman.ripe.net

FW: [ris-int] Draft minutes from Monday's RIS meeting (apologies for the delay)
by Matthew Williams 28 Jul '04

28 Jul '04

Hi James, > - Recent RRCs have been specified as: > > Dell PowerEdge 1750 (1U server) > 1 GByte RAM > 3 x 73 GByte Disk (configured as RAID5) > 2.4 GHz Xeon CPU Please send me a spec from Dell's web site that's intelligible for MSK-IX folk (should also give us an estimate on price excl BTW). Cheers Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of James Aldridge > Sent: 28 July 2004 16:21 > To: ris-int(a)ripe.net > Subject: [ris-int] Draft minutes from Monday's RIS meeting > (apologies for the delay) > > > RIS Meeting - 26 July 2004 > > Present: Matthew, Shane, Arife, James, Bruce, Ruud, Henk, Vasco > > Scribe: James > > Agenda: > - RRC Status > - RRC Moves/New RRCs > - myASn > - AOB > > RRC Status > > Q. Are there any existing tools to monitor BGP sessions? > A. Not that are directly relevent to the RIS. The current tools > compare BGP sessions against the registered peering > policy (the > AS3333 aut-num object). > > What to monitor? > - percentage of peers up/down? > - peer down for a "long time"? > > Should there be automatic or manual notification of peers when a > session is down? > > Who to contact at peers? > - We mostly use the IRR (RIPE, etc. databases) > - encourage peers to keep their own information up to date > - Current "addpeer" script records contact information > in a log file > - need to keep our own information up to date > - useful for historical data (e.g. who was the > responsible person at > the peer when the peering was first established, etc.) > > Action: monitor peering sessions in Nagios (OPS) > > peering sessions which are neither up nor > administratively > disabled should generate alerts. > > Action: document procedure for handling peering > sessions which are > down. (SED) > > 1. Nagios notifies SED, SED contacts peer > 2. After two weeks (?), session is > administrively disabled > ("neighbor ... shutdown"), (peer is contacted?) > 3. After a peering session is down for a > further period with no > response from the peer then the peering is > removed from the > RRC ("no neighbor ...") > > > RRC Moves/New RRCs > > * RRC08 (MAE West) has very few peers and more networks > are pulling out > of MAE West. We need to investigate alternative > locations for a route > collector on the US West Coast > > - PAIX > - Seattle > - LAIIX (Telehouse) > - ... > > Action: compare member lists of each West Coast exchange point > (Matthew) > > How to move RRC? Simply get MCI to ship box to new > location (or wait > for NCC staff to be in the vicinity of San Jose). > > * RRC06 (DIX-IE (NSPIXP2), Japan) - Not getting any new > peerings. > > Action: Contact George Michaelson (APNIC). Henk and > Shane will be at > IETF and can meet up with him there. > > * RRC13 (new RRC in Moscow) > > - Matthew has been in touch with RIPN (Russian > Institute for Public > Networks). > > - To simplify customs issues, it may be better for the host > organisation to order machine to our specification (see below) > directly from Dell in Russia. We would want to see > the quote before > agreeing to the purchase. > > - We need to know the IP configuration for the box so > we can configure > and ship the installation CD once the box is ordered. > > - Recent RRCs have been specified as: > > Dell PowerEdge 1750 (1U server) > 1 GByte RAM > 3 x 73 GByte Disk (configured as RAID5) > 2.4 GHz Xeon CPU > > myASn > > Meeting with Alexis last week didn't happen (Alexis out > of town?) > > Action: contact Alexis to set up meeting (Arife) > > Matthew's slide "On the road to myASn v.1": > - Automate account creation > - bring together AS3333/K-Root/RIS peering setup and > myASn account > creation > - For each peering confirmation, the peer should be > made aware of > the other RIPE NCC peering opportunities, etc. > where appropriate. > > Action: Check with Dave Knight what, if anything, > is mentioned > about other NCC services when K-Root peering is > established (Bruce) > > - Would be easier if all NCC peerings were handled by the same > group. > - K-Root peerings are more restrictive than RIS peerings. > > AOB > > RIPE49 (Manchester) > > RIS Update presentation > myASn Tutorial > > Action: Speak to Shane and get back to Matthew > et al. (Arife) > [Shane had already left the meeting at > this point] > > Inventory > > Ruud asks for Dell Service Tags for each RRC to > add to the > inventory. > > Ops Interaction > > Reminder to use <ops(a)ripe.net> as first point of contact > instead of sending email to Bruce/James directly. >

1 0

Draft minutes from Monday's RIS meeting (apologies for the delay)
by James Aldridge 28 Jul '04

28 Jul '04

RIS Meeting - 26 July 2004 Present: Matthew, Shane, Arife, James, Bruce, Ruud, Henk, Vasco Scribe: James Agenda: - RRC Status - RRC Moves/New RRCs - myASn - AOB RRC Status Q. Are there any existing tools to monitor BGP sessions? A. Not that are directly relevent to the RIS. The current tools compare BGP sessions against the registered peering policy (the AS3333 aut-num object). What to monitor? - percentage of peers up/down? - peer down for a "long time"? Should there be automatic or manual notification of peers when a session is down? Who to contact at peers? - We mostly use the IRR (RIPE, etc. databases) - encourage peers to keep their own information up to date - Current "addpeer" script records contact information in a log file - need to keep our own information up to date - useful for historical data (e.g. who was the responsible person at the peer when the peering was first established, etc.) Action: monitor peering sessions in Nagios (OPS) peering sessions which are neither up nor administratively disabled should generate alerts. Action: document procedure for handling peering sessions which are down. (SED) 1. Nagios notifies SED, SED contacts peer 2. After two weeks (?), session is administrively disabled ("neighbor ... shutdown"), (peer is contacted?) 3. After a peering session is down for a further period with no response from the peer then the peering is removed from the RRC ("no neighbor ...") RRC Moves/New RRCs * RRC08 (MAE West) has very few peers and more networks are pulling out of MAE West. We need to investigate alternative locations for a route collector on the US West Coast - PAIX - Seattle - LAIIX (Telehouse) - ... Action: compare member lists of each West Coast exchange point (Matthew) How to move RRC? Simply get MCI to ship box to new location (or wait for NCC staff to be in the vicinity of San Jose). * RRC06 (DIX-IE (NSPIXP2), Japan) - Not getting any new peerings. Action: Contact George Michaelson (APNIC). Henk and Shane will be at IETF and can meet up with him there. * RRC13 (new RRC in Moscow) - Matthew has been in touch with RIPN (Russian Institute for Public Networks). - To simplify customs issues, it may be better for the host organisation to order machine to our specification (see below) directly from Dell in Russia. We would want to see the quote before agreeing to the purchase. - We need to know the IP configuration for the box so we can configure and ship the installation CD once the box is ordered. - Recent RRCs have been specified as: Dell PowerEdge 1750 (1U server) 1 GByte RAM 3 x 73 GByte Disk (configured as RAID5) 2.4 GHz Xeon CPU myASn Meeting with Alexis last week didn't happen (Alexis out of town?) Action: contact Alexis to set up meeting (Arife) Matthew's slide "On the road to myASn v.1": - Automate account creation - bring together AS3333/K-Root/RIS peering setup and myASn account creation - For each peering confirmation, the peer should be made aware of the other RIPE NCC peering opportunities, etc. where appropriate. Action: Check with Dave Knight what, if anything, is mentioned about other NCC services when K-Root peering is established (Bruce) - Would be easier if all NCC peerings were handled by the same group. - K-Root peerings are more restrictive than RIS peerings. AOB RIPE49 (Manchester) RIS Update presentation myASn Tutorial Action: Speak to Shane and get back to Matthew et al. (Arife) [Shane had already left the meeting at this point] Inventory Ruud asks for Dell Service Tags for each RRC to add to the inventory. Ops Interaction Reminder to use <ops(a)ripe.net> as first point of contact instead of sending email to Bruce/James directly.

1 0

myASn - Last check list
by Matthew Williams 28 Jul '04

28 Jul '04

Fix errors, addtional features no in wp4. /Matthew - minED - minEC - ADW ++++ Clean out manual/auto - set dbase clean out time in alarm gr page ++++ You'll send email w/ xml example, import/export ++++ Optional: Experimental retromatch (not in wp4!) ++++ Breadcrumbs - Help ++++ Emails - change HDT, HDE, TTL ++++ Customer alarm - alarm 742 - no asns Customer alarm 742 (Default), 217.145.48.0/20 (exceptions not shown), MyASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 .=------+-----------------+--------------+--------------------------+-------------------------=. | RRC | Prefix | Peer | First Seen | Last Seen | |=------+-----------------+--------------+--------------------------+--- |----------------------=| | rrc10 | 217.145.48.0/20 | 217.29.66.65 | Wed Jul 7 02:02:01 2004 | Wed Jul 7 02:02:01 2004 | '=------+-----------------+--------------+--------------------------+-------------------------=' ++++ Add rrc12, tell SED about myasn.conf ++++ Remove alarms in uk.bt account ++++ Delete _all_ alarms in alarm groups ++++ Error handling when importing xml, cancel, fix error, try again --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

1 0

O: I need James or Bruce to come up with specs for PowerEdge 1750 intended as RRC13 at MSK-IX
by Matthew Williams 27 Jul '04

27 Jul '04

Hereby I wish to notify Operations of something uncategorised. Detailed description: --------------------- Pls see subline Cheers, Matthew Regards, Matthew Williams

1 0

Re: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group
by Rene Wilhelm 27 Jul '04

27 Jul '04

> > Matthew, > > > > We're working with Jeroen on updating the RIS pages for the new web server > > now, and I'd prefer not to have multiple people working on the site. > > > > What is the basic idea and/or scope behind this risintro page? > > This came up when the announcement for rrc12 was put online. The text > there assumes that one knows what the RIS is. Somebody then suggested to > have a short 1 page intro to the RIS for people who get the announcement > but haven't heard of the project. Linking the news flash on www to the risintro page is fine with me, better than diving immediately to the RRC12 specific page, but to set the record straight, all I suggested was to have a page with text similar to the announcement that was send out to the ris-users mailing list. Visitors to www.ripe.net see a news flash "Route Collector deployed at xyz-IX" and when they want to read more on this, the link should bring them to a page with relevant information. (which, next to details on deployement at the specific location, could have some words on RIS in general too). As such a page can easily be reused when a next RRC comes online, maybe it's an idea to design some template in the context of the current RIS pages restructuring work? Cheers, -- Rene P.S. All this was triggered by an external user pointing out to me the date on the announcement at www.ripe.net was wrong :)

3 2

RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group
by Matthew Williams 27 Jul '04

27 Jul '04

Hi Henk, I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html Will this do? Basic stuff... Feedback welcome though :) Cheers, Matthew *) VoS only ;) > -----Original Message----- > From: Henk Uijterwaal via RT [mailto:ops@ripe.net] > Sent: 26 July 2004 16:28 > To: matthew(a)ripe.net > Subject: Re: Fwd: Re: FW: [ripe.net #101517] R: please adrian > bedford to the projects group > > > Hi, > > > Otherwise add webmaster to np and/or tt groups. > > That won't allow you to edit RIS files :-) > > Seriously, there is a ris group for RIS, the ris is run by > different department these days, so simply putting the > webmaster in the RIS group and changing ownership of the > files, should solve the problem. > > 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 7

RIS work items
by Henk Uijterwaal (RIPE NCC) 26 Jul '04

26 Jul '04

Hi all, (By popular request in ASCII). Here is the list of to-do-items that are still open in the RIS move. All items that were completed (=80 to 90% of the work) are not on the list. Henk - - - - Integration with OPS (98% done) - Software Sync for RRC01-13 Few hours Bruce Procedures - Maintain operations draft Sep-Dec'04 Arife (background task) Routing Training - Stalled, looking for trainer. Ongoing work - MyASN handover 28/7 Matthew/Arife/Alexis/SED - MyASN documentation Now-R49 Matthew - RRC installation UAE ?? Matthew, Henk Integration with SED - Move III pages out of NP area 1 day Arife/James/Katie/Engin - Review docs on iii 1 week Arife/James/Katie/Engin Software move - Document existing software 4 weeks (50% done) Arife, James - Review documentation 2 weeks Engin, Katie - Prtraceroute with RISwhois 11/2004, 1 wk Katie - Maintain documents All Research Issues - Analysis of Beacon Data Fall'2004 Arife, Henk - BGP Stability Index Fall'2004 James - Website restructuring Summer Matthew, 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).

1 0

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